Schedule Import Properties
Schedule Import properties are OPS system (or context) properties that affect schedule import.
| Property | Description |
|---|---|
| If selected, the system will process Import OPSLineStopLabel. This includes applicable defined UserString supplementary data. |
|
| If selected, the system will process Import OPS StopTimes. | |
| If selected, when using Schedule Import or Import into an existing Sign-Up period, a dialog is displayed before starting the import with information about the runs and rosters (if any) being imported. This provides the user the opportunity to cancel the import if necessary. | |
| Specifies the FX Source to populate the OPSTravels during import: Travel, DeadHead, or DeadHead & Travel. | |
| If selected, all scenarios (service groups) are imported for the selected division. | |
| If selected, extra run pieces can be imported. | |
| If selected, the field mapping file is enabled in the BlockBuster import. | |
|
Specifies the sign-off location to use for a pull-in in the middle of a block. It can be Relief Node (the end location of the relief run), Travel Node (the location at which the operator ends his travel from the vehicle), or Block Pull In Node (the garage the block ends at). |
|
| Specifies the sign-off location to use for an extra run piece. It can be To Node (the end location of the extra run) or Travel Node (the location at which the operator ends his travel from the vehicle). | |
|
Specifies the sign-off location to use for pull in. It can be Block Pull In Node (the garage the block ends at) or Travel Node (the location at which the operator ends his travel from the vehicle). |
|
| Specifies the sign-off location to use for street relief work. It can be Relief Node (the end location of the relief run) or Travel Node (the location at which the operator ends his travel from the vehicle). | |
|
Specifies the sign-on location to use for a pull out in the middle of a block. It can be Relief Node (the starting location of the relief run), Travel Node (the location from which the operator starts his travel to the vehicle), or Block Pull Out Node (the garage the block begins from). |
|
| Specifies the sign-on location to use for an extra run piece. It can be From Node (the starting location of the extra run) or Travel Node (the location from which the operator starts his travel to the vehicle). | |
|
Specifies the sign-on location to use for pull out. It can be Block Pull Out Node (the garage the block begins from) or Travel Node (the location from which the operator starts his travel to the vehicle). |
|
| Specifies the sign-on location to use for street relief work. It can be Relief Node (the starting location of the relief run) or Travel Node (the location from which the operator starts his travel to the vehicle). | |
|
Specifies the sign-off location to use for a pull-in in the middle of a block. It can be Relief Node (the end location of the relief run), Travel Node (the location at which the operator ends his travel from the vehicle), or Block Pull In Node (the garage the block ends at). |
|
|
Specifies the sign-off location to use for pull in. It can be Block Pull In Node (the garage the block ends at) or Travel Node (the location at which the operator ends his travel from the vehicle). |
|
| Specifies the sign-off location to use for street relief work. It can be Relief Node (the end location of the relief run) or Travel Node (the location at which the operator ends his travel from the vehicle). | |
|
Specifies the sign-on location to use for a pull out in the middle of a block. It can be Relief Node (the starting location of the relief run), Travel Node (the location from which the operator starts his travel to the vehicle), or Block Pull Out Node (the garage the block begins from). |
|
|
Specifies the sign-on location to use for pull out. It can be Block Pull Out Node (the garage the block begins from) or Travel Node (the location from which the operator starts his travel to the vehicle). |
|
| Specifies the sign-on location to use for street relief work. It can be Relief Node (the starting location of the relief run) or Travel Node (the location from which the operator starts his travel to the vehicle). | |
| Specifies the SignId for loading FX Rosters when the bid is active. SignIds are separated by commas. | |
| If selected, only non-posted days are resolved in the TkWork table when resolving FxRuns. | |
| Specifies the date for starting signups that is used by the integrity checker. Past signups are not considered. | |
| If selected, in order to reduce data storage, system will remove trips and blocks zone segment after import. | |
| If selected, mid sign-up imports can begin on any day of the week. | |
| If selected, perform a check on schedule import to confirm the sign-up period date range is valid. | |
| Select a default holiday day to type to be added when importing holidays without a day type. | |
| If selected, data is checked when reimporting a schedule or importing into a schedule. | |
| Specify the number of minutes Pay Time can change for a run before generating a warning message. | |
| Specify the number of minutes the first SignOff time can change for a run before generating a warning message. | |
| Specify the number of minutes the first SignOn time can change for a run before generating a warning message | |
| If selected, check for divisions which have no opsdailyschedleruns or opsdailyschedule blocks for a given date in the import period. | |
| Specifies the demand response work source. Please reset ancillary/OPS cache data after making changes. | |
| Specifies demand response run types that are excluded. Please reset ancillary/OPS cache data after making changes. | |
Specifies the fixed route work source:
Please reset ancillary/OPS cache data after making changes. |