ISO/TR 17185-2:2015

Intelligent transport systems - Public transport user information - Part 2: Public transport data and interface standards catalogue and cross references

ISO/TR 17185-2:2015 compares and contrasts public transport standards that were developed by different regions and countries. It uses the CEN Transmodel classes as a reference to compare standard data concept descriptions of public transport user information. The purpose of this Technical Report is to understand the concepts described by existing standards and specifications that cover public transport passenger information.

Systèmes intelligents de transport — Informations destinées aux utilisateurs des transports publics — Partie 2: Données sur les transports publics, et catalogue des normes relatives aux interfaces et références croisées

General Information

• Status: Published
• Publication Date: 17-Nov-2015
• ICS: 03.220.01 - Transport in general
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 8 - Public transport/emergency
• Current Stage: 6060 - International Standard published
• Start Date: 18-Nov-2015
• Due Date: 05-Mar-2018
• Completion Date: 05-Mar-2018

Overview

ISO/TR 17185-2:2015 - Intelligent transport systems - Public transport user information - Part 2 - is a Technical Report that catalogs and cross-references public transport data and interface standards. The report compares standards developed in different regions and uses the CEN Transmodel classes as a common reference to map and explain equivalent data concepts. Its main purpose is to help stakeholders understand the concepts, overlaps and differences among existing specifications for public transport passenger information to promote interoperability and faster deployments.

Key Topics

• Standards comparison and catalogue: Side-by-side mapping of regional and national standards to a Transmodel reference, showing like concepts and terminology differences.
• Data concept definitions: Clear treatment of core data concepts such as class, attribute, data element, data frame, message and object, with equivalences across standards.
• Mapping of artefacts: Mapping of Transmodel artefacts to other standards (e.g., classes, attributes, business areas) and descriptions of conformance.
• Methodology and survey: Business plan, typology of public transport standards, and a documented methodology used to collect and map data.
• Annexed comparisons: Informative annexes with detailed class-attribute comparisons for standards such as GTFS, NeTEx, SIRI, TCIP, Korean ATIS, and Japanese ATIS.
• Assessment and gaps: Analysis of overlaps, missing requirements and opportunities to extend narrower specifications using enterprise-based models.

Applications

• System integration and data translation: Use the catalogue to translate terminology and data between standards (for example, mapping a “trip” in GTFS/TCIP to a “service journey” in Transmodel).
• Interoperability planning: Support transit agencies, operators and vendors in selecting compatible standards and mixing standards from different regions.
• Rapid deployment: Reduce duplication of work by reusing existing standards and interfaces when building passenger information, journey planning, or real-time systems.
• Standards adoption strategy: Help policymakers and procurement teams evaluate which standards or combinations best meet national or regional needs.
• Developer reference: A lookup resource for software developers, system integrators and consultants implementing public transport user information services.

Who Should Use It

• Public transport authorities and operators
• ITS architects, system integrators and software developers
• Standards bodies and technical committees
• Vendors of passenger information and journey-planning systems
• Policy makers and procurement teams focused on cross-border interoperability

Related Standards

• CEN Transmodel (reference data model)
• NeTEx, SIRI (CEN XML-based protocols)
• GTFS (General Transit Feed Specification)
• TCIP (Transit Cooperative Interface Profiles)
• Regional ATIS standards (Korean ATIS, Japanese ATIS)
• IFOPT, APTA references and other ITS documentation

ISO/TR 17185-2:2015 is an essential catalogue for anyone implementing or integrating public transport user information systems who needs to understand and bridge multiple data and interface standards for seamless passenger experiences.

Standards Content (Sample)

TECHNICAL ISO/TR
REPORT 17185-2
First edition
2015-12-01
Intelligent transport systems — Public
transport user information —
Part 2:
Public transport data and interface
standards catalogue and cross
references
Systèmes intelligents de transport — Informations destinées aux
utilisateurs des transports publics —
Partie 2: Données sur les transports publics, et catalogue des normes
relatives aux interfaces et références croisées
Reference number
©
ISO 2015
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO 2015 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Terms and definitions . 1
3 Abbreviated terms . 3
4 Objectives from a data catalogue and cross reference document . 4
5 Methodology . 4
5.1 Business plan and survey . 4
5.2 Public transport standards typology . 4
6 Public transport standard description results . 6
6.1 Public transport standard overview. 6
6.2 Mapping of Transmodel artefacts to regional standards . 6
6.2.1 Areas mapped to Transmodel. 6
6.2.2 General standard information . 7
6.2.3 Mapping of business areas .10
6.2.4 Mapping of data concepts and attributes .13
6.2.5 Description of conformance .13
7 Assessment .14
Annex A (informative) Business plan and survey: Detailed mapping of Transmodel and
regional standards .17
Annex B (informative) US transit communications interface profiles comparison to
Transmodel high level business areas .26
Annex C (informative) Korea ATIS Class-Attribute comparison to Transmodel .32
Annex D (informative) TCIP Class-Attribute comparison to Transmodel .34
Annex E (informative) Japanese ATIS Class-Attribute comparison to Transmodel .39
Annex F (informative) General Transit Feed Specification (GTFS) Class-Attribute
comparison to Transmodel .42
Annex G (informative) NeTEx Class-Attribute comparison to Transmodel .53
Annex H (informative) Service Interface for Realtime Information (SIRI) Class-Attribute
comparison to Transmodel .95
Annex I (informative) Related Transmodel Class definitions .124
Bibliography .143
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received. www.iso.org/patents
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
ISO 17185 consists of the following parts, under the general title Intelligent transport systems — Public
transport user information:
— Part 1: Standards framework for public information
— Part 2: Public transport data and interface standards catalogue and cross references
— Part 3: Use cases for journey planning systems and their inter-operation
iv © ISO 2015 – All rights reserved

Introduction
With the multiple standards that are deployed around the world to provide passenger information,
ISO/TC 204 sees a need to identify the range of information provision available to the public. Some
of the standards comprise messages and/or services that cover the full scope of the public transport
planning and operations enterprise, while others address a narrow scope of passenger information,
such as schedule information or bus arrival time prediction.
ISO/TC 204 saw a need to create a catalogue that shows the range and extent of the collection of
standards and specifications available. Furthermore, the group identified a need to show the similarities
and differences among these standards and specifications for several reasons, for example:
— to match like concepts and messages,
— to understand the overlaps, differences and missing requirements,
— to extend narrow-based standards using the concepts and interfaces developed by the enterprise-
based standards.
This Technical Report will be beneficial for all ISO/CEN member countries, as well as non-member
countries. It will be a valuable catalogue to help understand the content of the currently available
national and regional standards (identified in ISO 17185 Part 1), such as Transmodel, TCIP, Korean ATIS
and Japanese ATIS. The intention is that, by deploying these existing national and regional standards
from other countries or regions, duplication of cost and time in developing new standards and
specifications can be avoided. For those countries that do not have surface public transport information
standards, this approach allows the mix and match of standards from different regions, as well as
rapid development and deployment that can enhance the usability and convenience of public transport
anywhere in the world.
This Technical Report is intended to be fully consistent with those currently available national and
regional standards which may be related to international surface public transport. It is designed
to serve as a look-up table for developers for the terminology used in different regions for the same
concept. For example, the term “trip” in TCIP and GTFS is called “service journey” in Transmodel. This
catalogue will expose the differences in language for developers who need to translate data from one
standard to another. Principally, this Technical Report, and its scope and approach, will help lower the
barriers for developers who need to mix standards; for countries that need to choose the best approach
to deploy public transport systems; and, ultimately, for the public wanting a seamless public transport
experience wherever they travel.
As Andrew S. Tanenbaum said, “The nice thing about standards is that you have so many to choose
1)
from”. This report fully endorses that principle.
1) Computer Networks, 2nd ed., p. 254
TECHNICAL REPORT ISO/TR 17185-2:2015(E)
Intelligent transport systems — Public transport user
information —
Part 2:
Public transport data and interface standards catalogue
and cross references
1 Scope
This Technical Report compares and contrasts public transport standards that were developed by
different regions and countries. It uses the CEN Transmodel classes as a reference to compare standard
data concept descriptions of public transport user information. The purpose of this Technical Report
is to understand the concepts described by existing standards and specifications that cover public
transport passenger information.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
NOTE Equivalent TCIP or Transmodel term is identified for reference.
2.1
attribute
property of an entity
[SOURCE: CEN EN12896; p. 16 (ref 1), modified — Note 1 has been added.]
Note 1 to entry: Equivalent terms in TCIP / Transmodel: data element (TCIP).
2.2
class
concept within [a] system being modelled
[SOURCE: The Unified Modeling Language Reference Manual; p. 185 (ref 3), modified — Notes 1 and 2
have been added.]
Note 1 to entry: Equivalent terms in TCIP / Transmodel: data concept [US TCIP].
Note 2 to entry: Similar to entity, represents a set of objects with similar behaviour and properties.
2.3
data concept
any of a group of data dictionary structures (i.e., object class, property, value domain, data element
concept, data element, data frame, message, interface dialogue, association) referring to abstractions
or things in the natural world that can be identified with explicit boundaries and meaning and whose
properties and behavior [sic]all follow the same rules
[SOURCE: ISO 14817, p. 3 (ref 4), modified — Note 1 has been added.]
Note 1 to entry: Equivalent terms in TCIP / Transmodel: object, class, entity (Transmodel); data element, data
frame (TCIP).
2.4
data element
atomic piece of information related to a person, place, thing, or concept (for example, CPT-
PersonFirstName and CPT-Footnote)
[SOURCE: APTA-TCIP-S-01 3.0.3; p. 32 (ref 2), modified — Note 1 has been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: attribute (Transmodel).
2.5
data frame
grouping of data elements primarily for the purpose of referring to a group with a single name, and
thereby efficiently reusing groups of data elements that commonly appear together (as an ASN.1
SEQUENCE, SEQUENCE OF or CHOICE) in a TCIP message
[SOURCE: APTA-TCIP-S-01 3.0.3; p. 32 (ref 2), modified — Notes 1 and 2 have been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: Sub model (as in a “diagram”) in Transmodel [CEN-
Transmodel].
Note 2 to entry: This data concept type may also be used to specify groups of data elements for other purposes as
well. A data frame may contain other data frames as well as data elements.
2.6
dialog
ordered sequence of message exchanges between two or more entities
[SOURCE: APTA-TCIP-S-01 3.0.3; p. 33 (ref 2), modified — Notes 1 and 2 have been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: no equivalent in Transmodel.
Note 2 to entry: The rules of the exchange are defined by a dialog pattern. Messages specific to the type of
exchange are specified by the dialog.
2.7
entity
object (data) that has its own existence (as opposed to an attribute)
[SOURCE: The Unified Modeling Language Reference Manual; p. 16 (ref 3), modified — Notes 1 and 2
have been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: data concept (TCIP).
Note 2 to entry: Similar to object and class.
2.8
message
grouping of data elements and/or data frames intended to be transmitted as a complete package of
information in one direction
[SOURCE: APTA-TCIP-S-01 3.0.3; p. 39 (ref 2), modified — Note 1 has been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: no equivalent in Transmodel.
2.9
object
discrete entity with a well-defined boundary and identity that encapsulates state and behavior; an
instance of a class
[SOURCE: The Unified Modeling Language Reference Manual; p. 360 (ref 3), modified — Notes 1 and 2
have been added.]
Note 1 to entry: Equivalent Terms in TCIP / Transmodel: data concept (TCIP).
2 © ISO 2015 – All rights reserved

Note 2 to entry: Similar to class and equivalent to an entity.
3 Abbreviated terms
ADPU Application Protocol Data Unit (in the context of smart cards)
APTA American Public Transportation Association
ATIS Advanced Traveller Information System
CEN Comité Européen de Normalization
CFMS Contactless Fare Media System
csv Comma separated values
EU European Union
GTFS General Transit Feed Specification (formally known as the Google Transit Feed
Specification)
ID Identification or identifier
IEC International Electrotechnical Commission
IFOPT Identification of Fixed Objects in Public Transport, a preliminary CEN Technical
Specification, CEN standard, EN 28701:2009, that provides a Reference Data Model
for describing the main fixed objects required for public access to Public transport.
ISO International Organization for Standardization
ISO/TC 204 ISO Technical Committee 204 on Intelligent transport systems
N/I Not included
NeTEx NeTwork and Timetable Exchange. (CEN/TS 16614-, −2, −3). A CEN Technical
Specification in XML, based on Transmodel v6 and IFOPT, providing exchange
messages for space- and fare-, time-related data.
NTCIP National Transportation Communications for Intelligent Transportation System
Protocol (US Intelligent Transportation System standards body)
Pi Passenger information
PICC Proximity Integrated Circuit Card
PICS Profile Implementation Conformance Statement
PRL Profile Requirements List
PT Public Transport
PTV Public Transport Vehicle
SIRI Service Interface for Real Time Information (EN 15531–1 to 3 and TS15531–4
and 5). A CEN protocol in XML, based on Transmodel that specifies services about
public transport real-time services and vehicles, such as vehicle monitoring, stop
monitoring, and more.
SQL Sequential Query Language
TBT Technical Barriers to Trade
TCIP Transit Cooperative Interface Profiles
UML Unified Modelling Language
UTC Coordinated Universal Time
UTFS Universal Transit Fare System
WSDL Web Services Descriptive Language
XML Extensible Markup Language
4 Objectives from a data catalogue and cross reference document
The objectives of this catalogue are to:
— Facilitate and promote international cooperation in the area of world-wide public transport (PT)
standard activities.
— Encourage the PT industry to adopt a coherent and consistent reference data model standard for
PT where PT operators will benefit from a larger market base, lowering costs and enhancing inter-
operability among the systems they procure.
— Enhance economic trade by enabling standards to apply across country boundaries.
— Support PT to build interoperable applications that will work across country boundaries.
In addition, there are many countries that do not have national standards for traveller information. It
is hoped that this catalogue will define the scope of functions that are currently defined, and the areas
needing further work to support PT passengers.
5 Methodology
5.1 Business plan and survey
This Technical Report was conceived in 2006 as part of a business plan and an initial survey (see
Annex A). The business plan included the following:
— Purpose of developing a data catalogue of worldwide standards on public transportation information.
— Benefits to national standards bodies.
— Justification for the data catalogue.
— Project work plan.
— Resources needed.
In addition, a survey for collecting information was attached to the business plan. The survey results
are described in this Technical Report.
5.2 Public transport standards typology
As part of earlier discussions between CEN TC 278 WG 3 and ISO TC 204 (from 2000 to 2002), a set of
criteria was defined to compare the TCIP and Transmodel standards. Three measures were defined:
— Equivalence: implies the elements are the same.
— Similarity: elements are similar, that is they overlap in some areas and differ in others.
— Difference: elements are different and are not reconcilable.
4 © ISO 2015 – All rights reserved

In this context, an element was described as a “data element or attribute, or data concept or entity”.
However, the purpose of the two standards is fundamentally different and, over the ensuing years, they
have moved further apart in terms of their use and application.
In partitioning standards, ISO and other standards bodies are developing “abstract” versus
“implementation” standards. Furthermore, wide adoption of internet standards and information
technology best practices has helped modularize standards into different classes.
Table 1 — Information service standards’ typology
Service invocation (method) Information transfer
Implementation Interface: Encoding:
specifications
TCIP Protocol Interface Compliance Spec- TCIP XML Schema (Volume III)
[how] ification
SIRI XML Schema
(Protocol Requirements List)
NeTEx
(Volume IV) / NTCIP 2306 Center to
GTFS
Center Web Services
SIRI
NeTEx
Korean ATIS
Abstract model Behaviour: Content:
[what] TCIP Building Blocks (patterns) (Volume I) Transmodel
SIRI SIRI
NeTEx NeTEx
TCIP Data Dictionary/ Data Frames/ Data Mes-
sages / Dialogs (Annexes A – D)
Generally, the difference between an abstract model and implementation specification is “what is the
domain?” versus “how is it designed and implemented?” The abstract model describes the content
(semantics), logical relationships and completeness of the business domain, while the implementation
specification documents describe the design for a specific technology based on how a part of the domain
will be implemented. For example, there are several ways of invoking an exchange to acquire data (such
as, SQL, web services and messaging services) and there are several encoding formats to access the
data, including comma separated value file format (csv), XML or protocol buffer.
The reason to segment the standards space into the various categories is to illustrate the differences
between the content, behaviour and implementation approaches of these standards. Transmodel,
which is used as the reference model, is not a standard that can be implemented out of the box. It is
an abstract data model whose data concepts (and the relationships between the data concepts) help
users understand the business rules that apply to implementable standards. Transmodel captures the
domain rules in a logical, consistent manner.
Given this classification framework, Transmodel is positioned as an abstract model that describes the
semantics and business rules. Other standards, like TCIP, are implementation standards that include
syntax (data formats) and some semantics. TCIP also includes behavioural specifications, that is, how
information is exchanged in a business to business messaging environment. Most implementation
standards, like TCIP, do not explicitly define a data model which describes entities/objects, logical
relationships and business rules consistent with data modelling methodology. By mapping the
implementation standards to an abstract standard, the implementation standard achieves the benefits
of the semantic inter-operability of the data model.
The detailed mapping creates a catalogue on several levels of resolution. These include the following:
— typology (abstract/implementation; semantic/behaviour);
— business area;
— data concept;
— data concept attribute.
In addition, some responses of the survey included conformance and testing approaches, approaches to
handling data versioning and measuring data quality. In many cases, conformance statements and tests
are similar since the base standards upon which the public transport standard is based are the same,
for example, XML. For that reason, conformance approaches show the similarities and collaborative
methods that an implementer may use to integrate multiple message standards.
6 Public transport standard description results
6.1 Public transport standard overview
The survey included 10 sections. The sections requested three types of information: general
information on the standards and its lineage; detailed information on the content of the standard with
respect to a reference standard; and conformance and quality/versioning requirements associated
with implementation of the standard. Specifically, the 10 topics addressed were as follows:
1. Name.
2. Standard type (see Table 1).
3. Scope.
4. History and ongoing maintenance schedule.
5. Methodology and approach to development.
6. Business areas covered (mapping to Transmodel and TCIP business areas).
7. Conformance and interoperability with other standards (e.g. XML, IEEE 1512).
8. Conformance provisions.
9. Handling of data version (temporal aspects of data).
10. Handling of data quality (metadata aspects).
The reference standard that was used as the cross reference was Transmodel because it provides a
comprehensive abstract model of the PT data across most business areas, including data semantics and
business rules. Some standards go beyond Transmodel (such as TCIP), however, only in a few areas.
6.2 Mapping of Transmodel artefacts to regional standards
6.2.1 Areas mapped to Transmodel
Although the detailed data concept and attribute mapping only covers PT passenger information,
some standards include many more business areas. This clause includes four areas where elements of
Transmodel are mapped to regional standards:
— General information (no mapping);
— Business areas (includes all business areas beyond the scope of this Technical Report);
— Data concepts and attributes;
— Conformance.
6 © ISO 2015 – All rights reserved

6.2.2 General standard information
The general information related to each standard incorporated in the catalogue included the
following questions.
1. What is the standard name?
2. What type is the standard? Semantics/message/abstract/implementation?
3. What is the scope of the standard?
4. What year was the standard published?
5. Has the standard been implemented?
6. Who published the standard?
7. What was the methodology used to develop the standard?
8. Please list a short history of the development process:
9. Please describe the ongoing maintenance:
China
What is the standard name? Data Bus Interface Communication Specification of Intelligent Service
Terminal for City Bus and Trolley-Bus
Data Communication Protocol between Intelligent Service Terminal for
City Bus and Trolley-Bus and Control Center
What type is the standard? Semantics/message/abstract/imple- Data format, data frame, message frame, public transport information
mentation? gathering/ publishing/ exchanging between intelligent service terminal
and expansion of peripheral as well as control centre.
What is the scope of the standard? Data Bus Interface Communication Specification of Intelligent Service
Terminal for City Bus and Trolley-Bus defines the system construction,
interface specification between intelligent service terminal and expan-
sion of peripheral for city bus and trolley-Bus.
Data Communication Protocol between Intelligent Service Terminal for
City Bus and Trolley-Bus and Control Center defines the communication
protocol, communication connection, message handling, data format,
information gathering/ publishing/ exchanging between intelligent
service terminal on the city/trolley-Bus and control centre.
What year was the standard published? Data Bus Interface Communication Specification of Intelligent Service
Terminal for City Bus and Trolley-Bus: cd
Data Communication Protocol between Intelligent Service Terminal for
City Bus and Trolley-Bus and Control Center: 2012/11/05
Has the standard been implemented? Data Communication Protocol between Intelligent Service Terminal
for City Bus and Trolley-Bus and Control Center: implemented since
2013/04/01
Data Communication Protocol between Intelligent Service Terminal for
City Bus and Trolley-Bus and Control Center: will be implemented in 37
transit cities this year.
Who published the standard? Data Communication Protocol between Intelligent Service Terminal
for City Bus and Trolley-Bus and Control Center: implemented since
2013/04/01
Data Communication Protocol between Intelligent Service Terminal for
City Bus and Trolley-Bus and Control Center: will be implemented in 37
transit cities this year.
What was the methodology used to develop the standard? Defining the public transport information communication and interface
specification between intelligent service terminal and expansion of
peripheral as well as control centre for city bus and trolley-Bus.
Please list a short history of the development process: Proposed in February 2013, started on November 2013, form the draft
in 2014 and now collecting advices.
China
Please describe the ongoing maintenance: Collect advice from the industry to update the standard.
Japan
What is the standard name? Standards for Public Transport Information
What type is the standard? Semantics/message/abstract/imple- Data format for gathering/publishing/exchanging public transport
mentation? information
What is the scope of the standard? Defining the elements and attributes of data format for gathering/
publishing/exchanging public transport information
What year was the standard published? XML1.1ver. 2006
Has the standard been implemented? Approx. 150 high way bus operators have adopted since 2006
Who published the standard? Ministry of Land, Infrastructure and Transport
What was the methodology used to develop the standard? Defining the elements and attributes of data format for static and re-
al-time public transport information
Please list a short history of the development process: Start study data format in 1997
First field trials to provide bus static information in Yokohama (1997)
and Okinawa (2000)
Field trials to provide static and real-time information in Sapporo (2000),
Gifu/Hiroshima (2002), Nagoya (2004), Kyoto (2005) and Fukuoka/
Ooita (2006)
Large scale field trials have been carried out in 150 high way bus op-
erators since 2006
Please describe the ongoing maintenance: Reviewing field trial results and planning for improvements of data format
Korea
What is the standard name? Technical Regulation of Bus Information Exchanges (C2C)
What type is the standard? Semantics/message/abstract/imple- Messages for exchanging between bus information centers
mentation?
What is the scope of the standard? Defining the messages and protocols of information for exchanging bus
manage centers (local governments)
What year was the standard published? “Enacted by MLTM in November 2005
Has the standard been implemented? Revised in March 2010”
Who published the standard? Yes. Approx. 60 bus operators have adopted since 2004
What was the methodology used to develop the standard? Ministry of Land, Transport and Maritime Affairs
Please list a short history of the development process: Consensus
Please describe the ongoing maintenance: “MLTM & standardization organization have been studied interfaces
and data format since 2000.
US – Transit Communications Interface Profiles
What is the standard name? APTA TCIP-S-001 3.0.0, APTA Standard for Transit Communications
Interface Profiles
What type is the standard? Semantics/message/abstract/imple- Semantics and Message
mentation?
What is the scope of the standard?
What year was the standard published? 2006
Has the standard been implemented?
Who published the standard? American Public Transportation Association
What was the methodology used to develop the standard? Consensus
Please list a short history of the development process: Initially developed by NTCIP (1400 Series), Later replaced by APTA
version which incorporated additional material.
8 © ISO 2015 – All rights reserved

US – Transit Communications Interface Profiles
Please describe the ongoing maintenance:
NEPTUNE –AFNOR French Ticketing Codification
What is the standard name? Profil d’echange NEPTUNE – AFNOR French Ticketing Codification
reference NF P 99–506
What type is the standard? Semantics/message/abstract/implementa- data and message format linked to a data model (Transmodel
tion? 4.1 and IFOPT)
What is the scope of the standard? This data exchange profile has the objective to describe precisely
all the data elements necessary for a thorough description of the
public transport offer (space and time-related data) in order to
be able to present this information to the users in a homogeneous
way, independently from the media (internet, paper) and also
to exchange this information between multimodal information
systems.
What year was the standard published? 2009
Has the standard been implemented? yes, around 50 (reference implementation together with the
software CHOUETTE www.chouette.mobi)
Who published the standard? AFNOR
What was the methodology used to develop the standard? standard based on an UML data model and XSD/XML for the data
exchange structure and protocol
Please list a short history of the development process: This standard is based on the European specification TRIDENT
(2002), based on Transmodel V4.1. The current version incorpo-
rates several features of the IFOPT standard (EN 28701) such as
equipment, accessibility and stop typology.
Please describe the ongoing maintenance: maintenance in ensured by the working group in charge of this
particular topic (gt7 of AFNOR CN03)
Service Interface for Realtime Information (SIRI CEN)
What is the standard name? Service Interface for Realtime Information (SIRI)
EN 15531–1 — Business case
EN 15531–2 — Communication
EN 15531–3 — Services
TS 15531–4 - Facility monitoring service
TS 15531–5 - Situation exchange service
What type is the standard? Semantics/message/abstract/implementa- Data and message format linked to a data model (Transmodel 5.1)
tion?
What is the scope of the standard? SIRI is an exchange format for real-time information about PT
services, vehicles, events and facilities.
SIRI defines very broadly the concept of real time as being any
changes to the information introduced after the timetable publi-
cation (SIRI’s information scope being limited to one single day).
The most widely known SIRI service provides the estimated
passing time at a specific stop (Stop Monitoring Service. But SIRI
offers many other services: General Messaging Service, Vehicle
Monitoring Service, Situation Exchange, Facility Monitoring,
Production Timetable Service, Estimated Timetable Service, Stop
Timetable Service, Connection Timetable Service and Connection
Monitoring Service.
What year was the standard published? 2006
Has the standard been implemented? Yes, all over Europe, and also worldwide (US, Israel…)
Who published the standard? CEN TC278/WG3/SG7
What was the methodology used to develop the standard? Conceptual model relying on Transmodel.
SIRI offers a set of Web services (SOAP) for accessing the information.
Initially targeted exchanges are mainly inter-system communi-
cation (AVMS to passenger information system for example), and
SIRI 2 (2014) has completed it with the ability to communicate
with end user’s devices (mainly mobile phones and web browsers).
Service Interface for Realtime Information (SIRI CEN)
Please list a short history of the development process: To provide operators and manufacturers a standard framework to
exchange data concerning public transport real time information,
CEN TC278/WG3/SG7 decided to launch the SIRI project (Service
Interface for Real-time Information) in 2004.
It now replaces national standard like RTIG, VDV453, etc.
Please describe the ongoing maintenance: Maintenance in ensured by CEN TC278/WG3/SG7
Network and Timetable Exchange (NeTEx CEN)
What is the standard name? Network and Timetable Exchange
CEN/TS 16614–1 Network description
CEN/TS 16614–2 Timing information
CEN/TS 16614–3 Fare description
What type is the standard? Semantics/message/abstract/implemen- Data and message format linked to a data model (Transmodel 6)
tation?
What is the scope of the standard? NeTEx is an XML based exchange format and a set of services dedi-
cated to scheduled public transport data. It is based on Transmodel
and IFOPT and designed for most public transport business needs,
covering passenger information systems, planning systems, AVMS
(Automated Vehicle Monitoring Systems) and fare management
systems.
NeTEx is divided into three parts:
• Part 1: network topology (networks, lines, routes, stops, connec-
tions and geographic element, etc.). NeTEx Part 1 also provides a
framework and reusable objects used by all the other parts.
• Part 2: timing information (vehicle journeys passing times, day
types, calendars, etc.).
• Part 3: Description of the tariff offer (fare product, access rights,
usage parameters, prices, etc.).
What year was the standard published? 2014
Has the standard been implemented? Fast starting implementation (France, Italy, Germany, Netherlands,
etc.)
Who published the standard? CEN TC278/WG3/SG9
What was the methodology used to develop the standard? Conceptual mode relying on Transmodel.
NeTEx shares is communication protocol with SIRI and offers a
set of Web services (SOAP) for accessing the information and also
a REST based lite access.
Please list a short history of the development process: To provide operators and manufacturers a European wide standard
framework to exchange data concerning public transport scheduled
information, CEN TC278/WG3/SG7 decided to launch the NeTEx
project in 2009.
Please describe the ongoing maintenance: Maintenance in ensured by CEN TC278/WG3/SG9
6.2.3 Mapping of business areas
The survey included comparison of each regional standard’s business processes relative to Transmodel.
The Transmodel business processes include the following:
— network description;
— versions, validity and layers;
— tactical planning;
— schedules and versions;
— vehicle scheduling;
— driver scheduling;
10 © ISO 2015 – All rights reserved

— personnel disposition;
— rostering;
— passenger information;
— operations monitoring and control;
— fare collection;
— management information;
— multimodal operation in public transport;
— multimodal operators’ environment.
The business area definitions are described in Transmodel [CEN-Transmodel, pp., 18-204].
Most of the standards are narrowly scoped or segmented into many sets of standards. Similar to
Transmodel, TCIP is broadly scoped and provides similar if not of slightly broader scope. Table 2 shows the
relationship of the standards included in this catalogue compared to Transmodel’s business areas. A more
detailed comparison between Transmodel and TCIP detailed business processes is included in Annex C.
12 © ISO 2015 – All rights reserved
Table 2 — Business areas compared to Transmodel
Transmodel business package US-TCIP Japan US-CFMS AFNOR Korea GTFS SIRI NeTEx
network description Spatial Data Management Not Included (N/I) N/I X N/I N/I N/I X
Processes
versions, validity and layers (Limited) Data Configu- N/I N/I X N/I N/I X X
ration
tactical planning Scheduling Process N/I N/I X N/I N/I N/I X
schedules and versions Scheduling Process N/I N/I X N/I N/I X X
vehicle scheduling Scheduling Process N/I N/I N/I N/I N/I N/I X
driver scheduling Personnel and Work As- N/I N/I N/I N/I N/I N/I N/I
signment Process
personnel disposition Personnel and Work As- N/I N/I N/I N/I N/I N/I N/I
signment Process
Rostering Personnel and Work As- N/I N/I N/I N/I N/I N/I N/I
signment Process
passenger information Customer Information YES N/I X X X X X
Process
operations monitoring and control PTV Operations Process YES N/I N/I X X X N/I
fare collection Fare Collection (this por- N/I yes – limited X N/I N/I N/I X
tion not balloted)
management information Data Repository Opera- YES N/I N/I N/I N/I N/I N/I
tions Process (limited)
multimodal operation in public transport Limited (covered in related N/I N/I X N/I N/I X X
business areas)
multimodal operators’ environment Limited (covered in related N/I N/I X N/I N/I X X
business areas)
a
operations management Security and Incident Man- N/I N/I N/I N/I N/I X N/I
agement Process
Onboard Vehicle Systems N/I N/I N/I N/I N/I N/I N/I
Interactions
Transit Signal Priority N/I N/I N/I N/I N/I N/I N/I
a
Incident management is partly included in operations management

6.2.4 Mapping of data concepts and attributes
Data concepts or “classes” are clearly described by Transmodel. They are more difficult to extract from
messaging standards. Topological concepts like STOP POINT are defined by messaging standards in
a manner similar to Transmodel. For example, a stop point is described by Transmodel as “A POINT
where passengers can board or alight from vehicles” [CEN-Transmodel, 247]. Messaging standards use
almost the same description of the topological point. However, there are messages such as Bus Location
Information (BusLocationInfo, Korea TR Message) where the definition is a reflection of attributes
rather than a conceptual description. More specifically, a one to one data concept mapping is difficult
and needs to be defined as a Transmodel Class and Attribute correlation in most cases. To that end,
the mapping between specific Transmodel classes and data concepts are not included in this Technical
Report, but defined as a detailed Class-Attribute mapping.
The attribute mappings are listed in Annex B.
Mapping of each regional standard is included in a separate Annex as follows:
— Annex C: Korean ATIS;
— Annex D: TCIP;
— Annex E: Japanese ATIS;
— Annex F: GTFS;
— Annex G: NeTEx. (Note that NeTEx is entirely based on Transmodel/IFOPT.);
— Annex H: SIRI.
Additionally, Annex I contains definitions of Transmodel classes that are related to the provision of
public transport information. Although many of the concepts are not used by other international
standards, they augment the vocabulary of entities available to describe public transport services.
6.2.5 Description of conformance
Standards conformance testing shows how a system or implementation meets the requirements of the
standard. As illustrated in Table 1, a standard may be based on or constrain another standard, and
may in turn also be constrained. Similarly, many data messaging standards use multiple standards
to describe the semantics, behaviour, coding structure and syntax defined by other standards.
Description of conformance includes the conformance statement which details the requirements for
implementation, and one or more base standards upon which the conformance rests. For example,
many data messaging standards now use web services which are based on XML (XML schema) and
Web Services Descriptive Language (WSDL). For each standard in the catalogue, Table 3 includes the
conformance statement (if available), and the base standard(s) used to specify the data/message.
Table 3 — Conformance
Standard name Conformance statement Base standard
GTFS Meets the requirements in the GTFS files as described by “File Requirements” ObjectType for
https://developers.google.com/transit/gtfs/reference GTFS-realtime
CSV for GTFS
Japan Specification for standard data format for public transport information. XML
Korea Technical Regulation of BUS Information Exchanges (C2C) ASN.1
NEPTUNE http://www.chouette.mobi/wp-content/uploads/CHOUETTE_Validation_re- XML Schema
-AFNOR sume-glossaire-1.pdf
http://www.chouette.mobi/neptune-validation/v20/fr/
...