Public transport as a subject of regulation by international standards

Public transport is used in every city of every country. Innovation does not stop in its development and therefore does not bypass this industry either. Since the market for transport technologies is globalizing every day, the processes of the regulator are becoming more unified. In order to comply with all established security measures in the field of public transport, there are a number of regulatory legal acts, one of which are international standards, with the main of which we will acquaint you today.

Public transport - Network and Timetable Exchange (NeTEx)

There is a separate set of standards for the exchange of information and the establishment of a clear timetable for public transport. Since the variety of vehicles is quite extensive, the specificity of each individual type and technology requires separate regulation. One of the main standards is CEN / TS 16614–1: 2020. A feature of this standard is that it includes several parts that characterize the various types of technologies and actions used. That is why we recommend that you familiarize yourself in more detail with the technical characteristics of each part of this standard.

Part 1: Public transport network topology exchange format

CEN/TS 16614–1:2020

NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6 (EN 12896 series) and SIRI (CEN/TS 15531–4/-5 and EN 15531–1/-2/-3) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS). NOTE Many NeTEx concepts are taken directly from Transmodel; the definitions and explanation of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptions in order to fit the NeTEx context.

Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS with data from transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.

1.2 Transport modes All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.

1.3 Compatibility with existing standards and recommendations Concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train composition and facilities; planned passing times; timetable versions and validity conditions.

In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) - TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.

As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (The Netherlands) and NOPTIS (Nordic Public Transport Interface Standard). The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

Since this document has a large number of profile characteristics, for a clearer understanding of the possibility of its application for your business, we recommend that you contact the iTeh team for advice.

Part 2: Public transport scheduled timetables exchange format

CEN/TS 16614–2:2020

NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V5.1 (EN 12986), IFOPT (CEN/TS 28701) and SIRI (CEN/TS 15531–4/5 and EN 15531–1/2/3 ) and supports information exchange of relevance to public transport services for passenger information and AVMS systems. NOTE Many NeTEx concepts are taken directly from Transmodel and IFOPT; the definitions and explanation of these concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in order to fit the NETEx context.

The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and also for data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). However it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases for transport exchange.

1.2 Transport modes Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tram-way, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional provisions that apply especially to air transport.

1.3 Compatibility with existing standards and recommendations The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train com-position and facilities; planned passing times; timetable versions and validity conditions.

As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface Standard). The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

This standard does not have a large number of differences from the first part, nevertheless, the omission of certain outlines when building a clear system can significantly degrade the quality of the final result. Therefore, it is worthwhile to familiarize yourself in more detail with the more detailed details of the standard.

Part 3: Public transport fares exchange format

CEN/TS 16614–3:2020

NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V5.1 (EN 12986), IFOPT (EN 28701) and SIRI (CEN/TS 15531–4/5 and EN 15531–1/2/3 ) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS).

NOTE NeTEx is a refinement and an implementation of Transmodel and IFOPT; the definitions and explanations of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptations in order to fit the NeTEx context. Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS with data from transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.

1.2 Fares scope This Part3 of NeTEx, is specifically concerned with the exchange of fare structures and fare data, using data models that relate to the underlying network and timetable models defined in Part1 and Part2 and the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope of Part3. In summary, it is concerned with data for the following purposes: To describe the many various possible fare structures that arise in public transport (for example, flat fares, zonal fares, time dependent fares, distance-based fares, stage fares, pay as you go fares, season passes, etc., etc.).

To describe the fare products that may be purchased having these fare structures and to describe the conditions that may attach to particular fares, for example if restricted to specific groups of users, or subject to temporal restrictions. These conditions may be complex.

To allow actual price data to be exchanged. Note however that NeTEx does not itself specify pricing algorithms or how fares should be calculated. This is the concern of Fare Management Systems. It may be used may be used to exchange various parameters required for pricing calculations that are needed to explain or justify a fare.To include the attributes and the text descriptions necessary to present fares and their conditions of sale and use to the public.

NeTEx should be regarded as being 'upstream' of retail systems and allows fare data to be managed and integrated with journey planning and network data in public facing information systems. It is complementary to and distinct from the 'downstream' ticketing and retail systems that sell fares and of the control systems that validate their use. See 'Excluded Use Cases' below for further information on the boundaries of NeTEx with Fare Management Systems.

1.3 Transport modes All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports, air journeys, and air fares, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.

Since this part of the standard describes in more detail the norms for air transport modes, we strongly recommend that companies that in one way or another come into contact with this industry in the course of their activities, familiarize themselves with it.

Part 4: Passenger Information European Profile

CEN/TS 16614–4:2020

This technical specification is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information. NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531–4/5 and EN 15531–1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.

As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.

Passenger transportation is a very responsible and laborious process that requires a structured system and streamlined process. Since international standards are created even for this part of the concept of public transport, we recommend that you have this document available for complete confidence in compliance with international standards and the ability to operate on the international market.

Electronic fee collection - Secure monitoring for autonomous toll systems

The issue of security monitoring is relevant not only in the information technology industry, but also in the field of public transport. Technologies such as automatic toll payments, inspection and security systems are present in almost every country in the world. The International System of Standards is being created to facilitate the control of all the above-mentioned processes, as well as to minimize losses and risks. Consequently, the presence of these standards in the regulatory legal framework of the organization will significantly structure the process of carrying out activities and obtain clearer results during control. One of the key standards in this area is CEN / TS 16702: 2020. This document, like the previous one, has several parts, which we recommend to read further.

Part 1: Compliance checking

CEN/TS 16702–1:2020

This document specifies transactions and data for Compliance Checking - Secure Monitoring. The Scope of this document consists of: - - the concept and involved processes for Secure Monitoring; the definition of transactions and data; the use of the OBE compliance checking transaction as specified in EN ISO 12813, for the purpose of Compliance Checking - Secure Monitoring; the use of back end transactions as specified in EN ISO 12855, for the purpose of Compliance Checking - Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes; a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework; the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.

NOTE Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records. Since this standard is closely related to informational parameters, the technical parameters described in it can be quite narrow-profile. Perhaps if your company operates in the field of transport technologies, you may need more global standards, which you can find in our previous article or on the website.

Part 2: Trusted recorder

CEN/TS 16702–2:2020

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM: trusted recorder, for use inside an OBE; verification SAM, for use in other EFC system entities.

This document describes terms and definitions used to describe the two Secure Application Module configurations; operation of the two Secure Application Modules in the secure monitoring compliance checking concept; functional requirements for the two Secure Application Modules configurations, including a classification of different security levels; the interface, by means of transactions, messages and data elements, between an OBE or front end and the trusted recorder; requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.

This document is consistent with the EFC architecture as defined in EN ISO 17573–1 and the derived suite of standards and Technical Specifications, especially CEN/TS 16702–1 and CEN ISO/TS 19299. The following is outside the scope of this document:

The life cycle of a Secure Application Module and the way in which this is managed;
The interface commands needed to get a Secure Application Module in an operational state;
The interface definition of the verification SAM;
Definition of a hardware platform for the implementation of a Secure Application Module. The specifications of this standard are special details that need to be clarified before purchasing the document. If the general subject matter and characteristics of the standard suit your type of activity, we recommend that you contact our team to select the most suitable standard for you.

Transport technology requires safety and a structured approach to the organization.

As already noted, the innovative pace of development does not stand still. Thus, the rate of regulation of the complex of interaction is updated. In order not only to occupy a leading position in the global market, but also to be confident in the quality of the activities carried out, as well as the safety of the structure being established, it is necessary to comply with the requirements of the international system of standards. If you have not yet applied the standards in your activities or you need to update the database, you can contact the iTeh team who will help you choose the most suitable document.