BSI PD CEN/TR 17370:2019
$215.11
Public transport. Operating raw data and statistics exchange
Published By | Publication Date | Number of Pages |
BSI | 2019 | 134 |
1.1 Introduction
The OpRa work scope is the definition of a minimum set of Public Transport raw data needed as PT quantitative analysis enabling factor. To obtain this considering all the several aspects involved in this complex domain, the work has been conducted through the following phases:
-
assessment;
-
use cases definition and classification;
-
indicators definition;
-
raw data identification.
OpRa work does not go into the field of service quality measurement and reporting: service quality analysis will of course use data provided by OpRa, but quality definition remains a contractual level issue between a Public Transport Authority and a Public Transport Operator or an operator’s internal choice for a purely private service. OpRa mainly only reports unbiased actual data (i.e. measured or observed), described and aggregated in a shared and understandable way.
The OpRa work documented in detail in this document is coherent with EU Directive 2010/40. In particular, it relates to the Article 42 of the Delegated Regulation EU 2017/1926 [33], as regards the historic data. OpRa proposes to complement NeTEx (dedicated to the static scheduled information), for the historic data based on the underlying conceptual data reference model Transmodel EN 12896, similarly to the requirement of the Delegated Regulation EU 2017/1926 referring to the static scheduled information3.
1.2 Assessment phase
The assessment phase has been conducted studying the following aspects:
-
national scenarios for public transport raw data and statistics exchange, to identify indicators needs and usage;
-
public transport KPI definition in research projects to consider what has been already done in literature and research;
-
relations with public transport EU norms, to be coherent with already existent PT norms.
Moreover, involved actors and stakeholders have been identified like: Public Transport Authority (PTA), Public Transport Agencies, Public Transport Operator (PTO), system integrators and passengers, analysing public transportation Planning and Operation process, that have been divided into five main stages to group all the activates that characterize the Public Transport Service:
-
strategic planning: definition of network elements (lines, stops), main service parameters (vehicles sizes, operation intervals, service intervals for important time demand types), and guaranteed interchanges are planned;
-
tactical planning: operators plan their resource usage (vehicles, rolling stock, personnel), with detailed timetables for each resource unit;
-
before travel: all planned networks and timetables are published. Passengers and other types of clients can plan their use of the offered transportation services via printed and electronic media, and make their reservations as needed;
-
in-travel: the transportation service is conducted. Real-time information exchange is available while this takes place and can be recorded;
-
study and control: in this stage, operators and authorities review the history of actual operations, which could lead to improvements through operational changes, or an optimization of strategic and tactical planning.
The PTA and PTO are interested in all the defined stages, meanwhile from the passenger point of view; only the last three stages are relevant (all the preparation work being hidden).
Figure 3 Public Transport Service phases
During the assessment the most relevant research projects results have been considered and a deep analysis of the roles and usage of Public Transport Standards have been completed to guarantee a coherent approach of OpRa.
The first four stages are under the scope of NeTEx (Network Timetable Exchange) and SIRI (Service Interface for Real Time Information) and the last stage is the additional scope to be covered by OpRa. All these standards are compliant with the European Public Transport Reference Data Model (Transmodel).
NeTEx supports data exchange for the Strategic Planning and Tactical Planning stages, with data more than 24 h before validity date. In the Before Travel stage, NeTEx can be used to publish all planned data to client systems. Meanwhile SIRI supports “in-travel / in-operation” data exchange.
The OpRa scope is mainly concentrated to support data exchange for the Study and Control stage and it mainly focus on actual and measured information, i.e. information that cannot be changed anymore in the future. The OpRa covered concepts are based on following Transmodel domains:
-
operations monitoring and control (Part 4);
-
management information and statistics (Part 8).
1.3 Use cases definition and classification phase
To identify the set of raw data, a clear definition of use cases that, based on the assessment phase results, describes the indicators definition and usage to satisfy the Public Transport Study and Control phase is needed.
In this complex and articulate scenario, the work bring to a definition of several use cases this led to the needs to aggregate them and classify accordingly.
1.4 Indicators definition phase
For each defined use case an indicator has been formally defined, including its formulae. It has been advised that some indicators could have particular importance in for the Quantitative Analysis and in this perspective they could be considered Key Process indicators (KPI), for the purpose of this OpRa work, indicators and KPI are used as synonyms.
1.5 Raw data identification phase
After use cases and indicators have been defined, the work enter in the phase of raw data identification for the calculation of the indicators included all use cases. Due to the high level of complexity of the results, a traceability matrix has been identified.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
12 | 1 Scope 1.1 Introduction 1.2 Assessment phase |
14 | 1.3 Use cases definition and classification phase 1.4 Indicators definition phase 1.5 Raw data identification phase 2 Normative references 3 Terms and definitions |
17 | 4 Symbols and abbreviations |
18 | 5 National scenarios for Public Transport raw data and statistics exchange 5.1 General 5.2 France 5.2.1 General 5.2.2 Rail reporting |
19 | 5.2.3 Local public transport reporting |
20 | 5.2.4 Quality, economic and sociologic management 5.2.5 Security analysis |
21 | 5.3 Hungary |
22 | 5.4 Italy |
23 | 5.5 The Netherlands 5.5.1 General |
24 | 5.5.2 Monitoring |
25 | 5.5.3 Reporting |
26 | 5.6 Slovenia 5.6.1 General 5.6.2 Collecting and reporting of Public Transport raw data (operational statistics) |
28 | 5.7 Slovakia |
30 | 5.8 Spain |
33 | 6 Public Transport KPI definition in research projects 6.1 General |
34 | 6.2 EBSF — European Bus System of the Future (2008 to 2013) 6.3 KPI description |
37 | 6.4 MEDIATE — Methodology for describing the Accessibility of Transport in Europe (2008 to 2010) 6.4.1 General 6.4.2 KPI description |
39 | 6.5 CONDUITS — Coordination of Network Descriptors for Urban Intelligent Transportation Systems (2009 to 2011) 6.5.1 General 6.5.2 KPI description 6.5.2.1 General |
40 | 6.5.2.2 Traffic efficiency 6.5.2.3 Traffic safety 6.5.2.4 Indices for pollution reduction 6.5.2.5 Index for public transport usage of special groups |
41 | 6.6 METPEX — a MEasurement Tool to determine the quality of Passenger Experience (2012 to 2015) 6.6.1 General |
42 | 6.6.2 KPI description 6.6.2.1 General |
43 | 6.6.2.2 Mode-specific indicators |
44 | 6.6.2.3 User group-specific indicators |
46 | 6.6.2.4 Indicators for special users groups riding public transport |
47 | 6.6.2.5 Example of bus service indicator computation |
48 | 6.7 TIDE — Transport Innovation Deployment for Europe (2012-2015) 6.7.1 General |
49 | 6.7.2 KPI description |
51 | 6.8 D3IMPACT — Data-driven decisions for intelligent management of public transportation (2015 to 2016) 6.8.1 General |
52 | 6.8.2 KPI description 6.9 CELSO — Low-cost and high-performance pocket Automated Vehicle Monitoring system for Public Transport (2016) 6.9.1 General |
53 | 6.9.2 KPI description 6.10 MOP — Mobility Operation Platform: an Italian research and development project 6.10.1 General |
54 | 6.10.2 Operation Monitoring Control: Status and Process KPI in PT Systems |
55 | 6.10.3 Evaluation standards of the PT service |
56 | 6.10.4 MOP Outline: indicators and methodologies for monitoring public transport services 7 Use cases 7.1 Purpose |
57 | 7.2 Actors and use case categories 7.2.1 Actors 7.2.2 Use case categories |
58 | 7.2.3 Collection of use cases 7.2.3.1 General |
62 | 7.2.3.2 High Level Generic use cases |
65 | 7.2.3.3 Service Offer use cases |
76 | 7.2.3.4 Service Demand use cases |
85 | 7.2.3.5 Service Externality use cases |
88 | 7.2.3.6 Service Economy use cases |
99 | 7.2.3.7 Service Efficiency use cases |
107 | 8 Compatibility with existing standards and recommendations 8.1 Compatibility with Transmodel 8.1.1 General |
108 | 8.1.2 Raw data and indicators 8.1.3 Data structure representation 8.1.3.1 Generic Loggable Object model |
110 | 8.1.3.2 Loggable Object model applied to boarding-based Demand Dimensions |
111 | 8.1.3.3 Loggable Object model applied to device-based Demand Dimensions 8.1.3.4 Loggable Object model applied to ticketing-based Demand Dimensions |
113 | 8.2 Compatibility with EN 13816:2002 — Service Quality Definition, Targeting and Measurement |
114 | 8.3 Compatibility with EN 15140:2006 — Basic requirements and recommendations for systems that measure delivered service quality |
115 | 9 OpRa Generic Physical Model and XSD early draft 9.1 General 9.2 What is a physical model |
116 | 9.3 First input toward an XML (XSD) model implementation |
118 | Annex A (informative)Data Dictionary A.1 Introduction A.2 DAY TYPE A.3 DRIVER INCIDENT A.4 JOURNEY ACCOUNTING A.5 LINE A.6 SCHEDULED STOP POINT |
119 | A.7 ROUTE A.8 SERVICE JOURNEY A.9 SERVICE LINK A.10 SERVICE JOURNEY PATTERN A.11 VEHICLE INCIDENT A.12 VEHICLE JOURNEY A.13 VEHICLE TYPE |
120 | A.14 VEHICLE MONITORING A.15 TARGET PASSING TIME |
121 | Annex B (informative)Research Projects vs. OpRa KPI B.1 General B.2 Comparison between EBSF and OpRa KPI |
122 | B.3 Comparison between MEDIATE and OpRa KPI |
125 | B.4 Comparison between CONDUITS and OpRa KPI |
126 | B.5 Comparison between METPEX and OpRa KPI |
129 | B.6 Comparison between TIDE and OpRa KPI |
130 | B.7 Comparison between D3IMPACT and OpRa KPI |
131 | B.8 Comparison between CELSO and OpRa KPI |