Basic Info |
The Basic Info tab enables you to set administrative options (such as when error messages display and when information is required) for your transit operation.
Setup options for operations
Property name
The organization's name.
Short name
The abbreviated (shortened) version of the organization's name.
Time allowance (minutes) before trip is considered late
The number of minutes that a train can be late without triggering a status of LATE. For example, if the allowance is set to 4, the train is considered late when it arrives 5 or more minutes past its scheduled destination arrival time. The maximum field length is six characters.
Minutes after midnight to count as part of today
Amount of time in the following day to count as part of the previous day when trains span the midnight hour. Specifying a value enables the Data -> Operations -> Trips screen to account for trips that span the midnight hour and allows trains to leave before midnight and arrive after midnight without triggering time stamp errors. For example, if you specify 60, then stops can go from 23:00 to 01:00 and will be considered part of the same day. The maximum field length is six characters.
Schedule type ID that indicates an extra trip
Identifier of the schedule type that can be used to bypass some of the regular data rules so that an extra trip can be entered and used on an as-needed basis. Extra trains are excluded from the Data -> Operations -> Dispatch Trips screen. This field has a list box. The schedule description displays to the right of the ID.
Schedule type IDs are defined on the Data -> Operations -> Setup -> Schedule Types screen.
Message when total of stop delay minutes does not equal trip delay minutes
A check in this field indicates that when a train is late and the number of minutes late on the Trips screen should equal the sum of minutes late in all the associated delay records, a message states that the stop delay minutes do not equal trip delay minutes.
If the number of minutes does not have to be the same, leave this checkbox blank.
Require one delay designated as the primary reason for a delayed trip
Indicates whether one delay must be designated as the primary delay for a trip.
If this box has a check, the Primary delay field on the Delay tab of the Data -> Incident Management -> Incident Management -> Delays screen is automatically checked when the first trip delay is entered. If a user places a check in the Primary delay field for a subsequent delay, the user is prompted to confirm whether the other delay should be kept as primary or whether the current delay should be designated as primary.
Require consist ID when dispatching trips
If this box has a check, a consist ID must be assigned to create a trip record on the Data -> Operations -> Dispatch Trips screen. If a consist is required, it must be assigned before either the assistant dispatcher or dispatcher can sign off on a trip. Signoff occurs on the Basic Info tab of the Data > Operations > Trips screen.
Note: Does not apply to trips with a status of ANNULLED.
Require actual capacity of consist to be greater than or equal to required capacity for the trip
If this box has a check, the correctly sized consist must to be assigned to the trip record. If short consists are run and that information needs to be on the trip record, leave this checkbox blank.
Note: Does not apply to trips with a status of ANNULLED.
Automatically calculate standee count on trips
If this box has a check, the standee (standing passengers) count on trips is automatically calculated based on passenger counts entered by stop. If the standee count is not required, leave this checkbox blank.
Default trip actuals when dispatching trips
If this box has a check and a trip is dispatched on the Data -> Operations -> Dispatch Trips screen, the trip is automatically assigned a status of ON TIME. The trip actuals (or the equipment cycle actuals, if applicable) for the trips record are based on scheduled information.
Allow consist assignment to overlap on trips not signed off yet
If this field and the Dispatcher Signoff field on the Basic Info tab of the Data -> Operations -> Trips screen have checks, the system permits equipment assignment overlap between trips. Whether the Assistant dispatcher signoff field is checked or blank has no effect. If this field is blank, consist and equipment use are validated on all trips that overlap the existing trip, regardless of sign off status.
Tip: This option defaults to blank (not checked). If you would like to continue operating as you did prior to version 6.4, set this option immediately after you upgrade.