EN 12896:2006

Foreword
Use of the Transmodel standard
Transmodel origins
ENV 12896
Titan
SITP and SITP2
CEN TC 278 WG 3 SG 4
Structure of this European Standard
Conformance
Future developments
Introduction
Rationale for the Transmodel standard
Use of the Transmodel standard
Applicability of the Transmodel standard
Introduction
Specification of information architecture
Specification of a database
Specification of an interface
Status of the Transmodel standard
1 Scope
  1.1 General
  1.2 Overview
  1.3 Network description
  1.4 Versions, validity and layers
  1.5 Tactical planning: Vehicle-Driver Scheduling and Rostering
  1.6 Personnel disposition
  1.7 Operations monitoring and control
  1.8 Passenger information
  1.9 Fare collection
  1.10 Management information
  1.11 Multi-modal operation
  1.12 Multiple operators' environment
2 Terms and definitions
3 Requirements
  3.1 General
  3.2 Description of the Network
  3.3 Versions, Validity and Layers
  3.4 Tactical Planning Components
  3.5 Vehicle Scheduling
  3.6 Driver Scheduling
  3.7 Schedules and Versions
  3.8 Rostering
  3.9 Personnel Disposition
  3.10 Operations monitoring and control
  3.11 Passenger Information
  3.12 Fare Collection
  3.13 Management Information
  3.14 Multi-modal Operation in Public Transport
  3.15 Multiple Operators' Environment
Annex A (normative) Data Definitions and Main Properties
        A.1 This Annex
Annex B (informative) Additional features of the model
        B.1 Consistency and Integrity Conditions
        B.2 Introduction to Data Modelling and the
            Methodology Used
        B.3 Functional Model
Annex C (informative) Changes in this version of Transmodel
        C.1 Changes between ENV 12896 (Transmodel 4.1) and
            Transmodel 5.0
        C.2 Modifications to V5.0 leading to V5.1
Annex D (informative) Transmodel in UML
        D.1 Introduction
        D.2 Class diagrams
        D.3 Class dictionary
        D.4 Generalisations and specialisations
        D.5 Comparison of notations
Bibliography

The European reference data model for public transport is an offer to public transport companies and other providers of services related to the process of passenger transportation and information, to suppliers of software products supporting these processes, and to consultants and other experts acting in the field of public transport in the widest sense.The reference data model can support the development of software applications, their interaction or combination in an integrated information system, and the system‘s organisation and information management which rules the utilisation of the existing telematics environment in a company (or group of companies) running computer applications supporting the different functional areas of public transport.Although primarily designed to document the information needs of a public transport company in a well defined and structured way, the reference data model can also serve as a starting point and reference for the definition of a database schema. A database schema is needed for the physical implementation of data storage systems to be used by applications directly, or for exchange of data between applications via interfaces. Apart from that, such a database will often additionally be used as a source of information for the company management and/or as an information pool for all employees who may need access to the information basis of the company.1.2Overview The data model describes elementary data needed for¾network description;, and¾versions management.that are used in several functional domains as basic concepts.The data model describes the information needs related to the following functional domains:¾tactical planning (vehicle scheduling, driver scheduling, rostering);¾personnel (driver) disposition;¾operations monitoring and control;¾passenger information;¾fare collection;¾management information and statistics.