CWA 14838-3:2003

Facilitating Smart Card Technology for Electronic Ticketing and Seamless Travel - Part 3: Catalogue of Technical and Business Process Requirements CWA 14838-3:2003

Scope

This Part of CWA 14838 should be read after Parts 1 and 2. It is intended for readers who require guidance and stimulation for drafting specifications for business and technical processes for smart card based ticketing schemes that are intended to be interoperable with other schemes according to the multi-operator scenarios and fare product types proposed in CWA 14838-1 and -2. It is therefore assumed in this Part that the reader will not require any further guidance on the motivation or rationale of such schemes. If they do, they should look again at the earlier parts of the CWA.
The process requirements are identified and defined on the basis of a role model, in which each role accounts for an indivisible collection of responsibilities towards other roles of the model. The implementation of this role model is denoted in the text as a smart card based electronic ticketing (or e-ticketing) scheme (or simply ‘scheme’). Legal entities that assume the roles identified in the model are denoted as actors.
The standardisation work that is taking place in CEN TC 278/WG3/SG5 on the Interoperable Public Transport Fare Management System Architecture (IOPT FMSA) is mainly dealing with the identification of roles within an Interoperable Fare Management (IFM) system, the interactions between them and the definition of the relevant system use cases. The IFM system drafted by WG3 has provided the basis for the role model presented here, though the FASTEST Workshop has adapted the currently available version of the system to suit its own needs.
In particular, the FASTEST Workshop has recognised that before describing system use cases, and thus the functionality of a system, there is a prior need for the definition of model business strategies and business use cases related to the fare product life-cycle, rather than to the system life-cycle. The business use cases will lead to the identification of business processes and then be interrelated to the system’s functionality.