Trip Cycles - Segments Detail
Previous  Top  Next


Description:
Displays the time it took between specified events at specified stations between a specified time period. 

Step by step instructions:
1. From the Management Reports tree branch on the Home window, double-click Trip Cycles - Segments Detail
2. The Filter Builder will display that will allow you to select some simple filters. Because the filters required for this report are so extensive, RMS offers to save the required filter elements for you to make running the report in the future much easier. These saved filter settings may be retrieved from the Stored Segment Filters drop-down text box at the top of the Filter Builder window. For unlimited filtering capabilities, copy this report and edit it in the Custom Report Creator and Editor. Click on the Show an pre-existing filters button to see if there are any saved filters associated with this report.
3. Once the report has displayed on the screen, print it by clicking on the Print command button on the Report Viewer toolbar.

Note:  Both starting and ending event dates for each cycle segment, to be displayed, must fall between the Start / Origin Date and the End / Destination Date.  The Segment Criteria can be deleted by clicking the Delete command button; it also can be updated by first selecting the segment criteria record, making any needed changes, and then clicking the OK command button.

This report is based on one-way trips, so the two events used must happen during a one-way trip. For example, for a loaded shipment, the one way trip would start with a release load event and end with a release empty event. This is different than RMS 3.X versions because the trip cycles are now stored as one-way trips in RMS 4.X and higher. The advantage is that this report runs much faster. If you need to understand the time between a release load event and a arrival empty event for the return empty trip, you will need to run two reports: one showing the time between the release load event and the release empty event and one showing the time between the release empty event and arrival empty event. This shouldn't be too large of an impact since these reports run so much more quickly.