Validation Reference Codes

Service Validations

Data Fields
Ref Code Validation
REF-001
Stop point is more than 20m from route path

The stop location is too far away from the route. Please either move the stop point or the route path to within 20m.

REF-002
Point type school/depot/non-public is not allowed. Use bus stop point type only

Point types of "bus stop" must only be used on the route stopping pattern and timetable. Shift bats can be used to define driver relief points or dead-run segments to depot locations.

REF-003
Arrival time is before the departure time of the previous stop

Update the arrival time of the stop or the departure time of the previous stop in time chronological order

REF-004
Departure time is after the arrival time of the next stop

Update the departure time of the stop or the arrivate time of the next stop in time chronological order

REF-005
Departure time is before the arrival time

Update the arrival or departure time of the stop to time chronological order

REF-006
Speed exceeds 120km/hr departing from previous stop

Update the stop times to the minimum travel in minutes as specified. Speed excess validation calculations are based on the route path distance between stops and not using a straight line distance.


This validation will only be triggered if the (minimum travel time) minus (duration between stop times on the timetable) is greater than 1 minute.

REF-007
Stop point has not been verified

Stop points must be verified in Planable > Points before the service can be published to customers

REF-008
Point is a duplicate

Identical stop points in sequence on the route service are not allowed. Remove duplicate stop points from the route service.

REF-009
Route must start with a bus stop point type with no leading waypoints

Select the first stop point and use "Trim start of route" in the route edit control panel.

REF-010
Route must end with a bus stop point type with no trailing waypoints

Select the last stop point and use "Trim end of route" in the route edit control panel

REF-011
Published routes must have at least one service timetable

Add an operating calendar and timetable to the route service

REF-012
Published routes must have at least two bus stop points

Ensure all route services have a starting and terminating stop point

REF-013
Published routes must only contain bus stop types

Remove all non bus stop types such as Depot, School and Non-Public stop points from the route service. You may add non bus stop point types to shift bats in Rosterable > Shift Bats.

REF-014
Published routes must have at least 2 stop times

Stop arrival and departure times cannot be empty for published route services.

REF-015
The first and last stop of a published route must be a timing point

Update the first and last stop of all service timetables to be a timing point.

REF-016
First stop point must be a timing point

Update the first stop point on all timetables to be a timing point

REF-017
Last stop point must be a timing point

Update the last stop point on all timetables to be a timing point

REF-018
Route name cannot be empty

Enter a route name. Route name is customer facing and will appear on customer journey planners and 3rd party apps if published.

REF-019
Route number cannot be empty

Enter a route number. Route number is customer facing and will appear on customer journey planners and 3rd party apps if published.

REF-020
Timetable operating calendar is missing or expired

Each service must have an active operating calendar. Update or add an active operating calender.

REF-021
Duplicate route variant

A route variant must not have the same route path and stopping pattern. Delete duplicate route variants

REF-022
Stop time validation warnings

The timetables contain stop time validation warnings. Load each timetable and resolve each stop time validation. More detailed validation messages will be displayed against each stop time.

REF-023
Stop point is out of sequence

The stop point is out of sequence the route service direction of travel. Update the stop point to the correct sequence number

Driver Duty (Shift Bat) Validations

Data Fields
Ref Code Validation
REF-024
Service row is invalid

There are services in the shift bat that has been invalidated. This could be caused by the service being deleted. Please delete the invalid service row and re-add the latest service.

REF-025
Point row is invalid

There are point loactions in the shift bat that has been invalidated. This could be caused by the point being deleted. Please delete the invalid point row and re-add the latest point.

Transfer Validations

Data Fields
Ref Code Validation
REF-026
The transfer cannot be mapped to a setdown service

TODO

REF-027
The transfer cannot be mapped to a pickup service

TODO.

REF-028
Missed transfer time

TODO.

TODIS Export Validations

Data Fields
Ref Code Validation
REF-400
Accreditation ID missing for one or more operator data regions

For each operator data region, ensure accreditation ID exists in Settings > Account > Accredition ID

REF-401
Source ID code is missing from stop point

Enter a TfNSW issued transit stop number into the "Source ID" field in the stop point

REF-402
Duplicate Source ID code

Every point must have a unique TfNSW issued transit stop number. Merge the stop point with the duplicate soure ID or raise an OTConnect to create a new TfNSW transit stop number

REF-403
Stop point is more than 15m

Stop point location is more than 15m from the TfNSW stop point location. Merge stop point to the TfNSW point or request an OTConnect to update the stop point location in TfNSW systems

REF-404
Route number must not be empty

All services must have a TfNSW issued route number. E.g. S123

REF-405
Route name must not be empty

All services must have a TfNSW issued route name E.g. Parramatta to Olympic Park

REF-406
Drive Duty shift number invalid

Driver duty shift numbers must only contain alphanumeric values and start with a alphabet character followed by numbers only. E.g AM0102 is valid. However, the following are invalid: AM01AM02 or AM01-02 or AM01/02