nkSRPS EN 12896-4:2024

Public transport - Reference data model - Part 4: Operations monitoring and control

Scope

1.1 General scope of the standard
1.1.1 Functional domains
Transmodel V6.2, as already in the previous version, is structured into 10 parts (of which Part 9 consists of informative information). In terms of functional coverage, Transmodel provides data structures required by most of the functions of the following domains of Public Transport:
- public transport network definition: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places, but also parking (Part 2);
- timing information and vehicle scheduling: runtimes, vehicle journeys, day type-related vehicle schedules (Part 3);
- operations monitoring and control: operating day-related data, vehicle follow-up, control actions (Part 4);
- fare management: fare structure and access rights definition, sales, validation, control (Part 5);
- passenger information (planned and real-time) (Part 6);
- driver management (Part 7) split into:
- driver scheduling (day-type related driver schedules);
- rostering (ordering of driver duties into sequences according to some chosen methods);
- driving personnel disposition (assignment of logical drivers to physical drivers and recording of driver performance);
- management information and statistics (including data dedicated to service performance indicators) (Part 8);
- management of the alternative modes of operation: vehicle pooling, vehicle sharing, vehicle rental, taxi (Part 10).
The data modules dedicated to cover most functions of the above domains are specified.
Several concepts are shared by the different functional domains. This data domain is called 'Common Concepts' (Part 1, see EN 12896-1, Public transport - Reference data model - Part 1: Common concepts).
The different parts are related to the implementations NeTEx, SIRI, OpRa, OJP as shown in Figure 1 below.
(...)
1.4 Particular scope of this document
The present document is composed of the following data packages:
- Dated Production Components;
- Call;
- Dated Call;
- Production Plan;
- Detecting & Monitoring;
- Situation;
- Messaging;
- Control Action;
- Operational Event & Incident;
- Facility Monitoring & Availability;
- Occupancy.
This document itself is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
- Annex B presenting the model evolution (informative);
- Annex C detailing the mapping to DATEX-II and SIRI.
(...)

Related directives

NOTE: If the word "harmonized" (marked in green) is not found in the field with the name of the directive, it means that the European standard is not cited in the OJEU.