Electronic Bus Service Registration
source url Electronic Bus Service Registration (EBSR) is planned to replace the current paper based registration process, where operators physically produce registrations for VOSA and Local Authorities. EBSR provides the information required for a registration, including the timetable element, in a TransXChange XML format file. The route must be sufficiently detailed to enable it to be electronically mapped and details of the registration (with service and operator information) need to be included.
As a part of Omnibus TransXChange software, the EBSR module is designed to provide an efficient answer to the provision of Electronic Bus Service Registrations. Once a user has input details of the operator, service and registration, the module will extract all registration journeys from OmniTIMES data and mapping details from OmniMAP to create TransXChange format registration documents ready to be sent to VOSA.
In addition to this, the module runs various validation checks and allows users to edit the registration document once it has been created. To help organisations keep a track of service changes electronically, a stored history of previous registrations is held centrally, and can be recalled easily.
EBSR has a significant impact for local authorities who already use OmniTIMES. The time consuming business of interpreting and manually inputting registrations will disappear at a stroke. Using the timetable data currently held for Traveline the modification or creation of timetables for the EBSR process is simple, streamlining this function.
For operators, the move to EBSR, with data fed directly from the scheduling system, will remove the need for the paperwork associated with changes in registrations. This speeds up the process significantly and will ensure the accurate interpretation of registrations by those who receive and use them.
- Works with OmniTIMES and OmniMAP data to produce results for VOSA
- Simple to use and efficient in operation – significantly aids the registration process
- Validation checks to ensure conformity
- Support for split registrations
- Include geographic tracks from OmniMAP data
- Maintain a history of registrations that may be recalled easily
- Be prepared for the wider use of EBSR
- Eliminates potential transcription errors
- Stay at the leading edge of data integration