Data exchange for ticket check and after sales operations with electronic information (barcodes, other security certificates)
A ticket contains information about the contract between the customer(s) and the carrier(s). This ticket can hold additional information, indicating a modification of the contract (or its status). E.g. when a train staff member marks the ticket as being used, he puts a stamp or a punch on it.If the ticket can be physically copied or reprinted (e.g. home-printed tickets) or if there is no physical ticket at all (paperless mechanisms, sms-tickets, ...), printing a stamp or punching a hole is useless. In that case, an electronic equivalent has to be defined. These electronic equivalents are messages, containing all necessary information to be shared with all necessary parties.This standard defines the necessary data in the messages, in case of: - a ticket check (ticket is used or partially used),- an endorsement/annotation (if the carrier was not able to fulfil a part of the contract),- an after sales operation (when the ticket is cancelled/modified at a desk).Since some data can be optional, bilateral agreements have to be made, defining which info of the list, defined in the standard as being optional, needs to be shared.
Author | UIC |
ISBN | 978-2-7461-1990-1 |
Pages | 35 |
Data sheet
- Language
- English
- Edition
- Ed. no.1
- Edition date
- 01/08/2011
- Publication date
- 01/08/2011
- Page number
- 35
- sku
- 918-4/E/1-PDF
- uic_only
- Reference
- 918-4