Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD ISO/TR 17185 โ Intelligent Transport Systems Public Transport User Information Standard Series
Intelligent Transport Systems โ Public Transport User Information โ Technical Report Series Overview
๐ PD ISO/TR 17185 is a BSI Published Document series adopting ISO technical reports on intelligent transport systems (ITS), focused on public transport user information data and interoperability. The series was prepared by BSI technical committee EPL/278 (Intelligent transport systems) and carries ICS 03.220.01 (transport in general) and 35.240.60 (IT applications in transport). Its purpose is to standardise the data structures and standard interfaces of public transport information and to promote interoperability among journey planning systems, creating a unified information ecosystem for operators, system developers and mobility service providers.
๐ก The value of passenger information systems lies in “usable data, interoperable interfaces”. The series compiles a catalogue of public transport data and interface standards, and demonstrates how cross-system, cross-operator journey planning can interoperate through use cases.
1. Series Structure and Scope ๐
This batch comprises two technical reports supporting the public transport passenger information ecosystem from two angles โ a standards catalogue and interoperability use cases:
| Part | Document | Subject | Main Content |
|---|---|---|---|
| Data & interface catalogue | PD ISO/TR 17185-2:2015 (ISO/TR 17185-2:2015) | Public transport data and interface standards catalogue and cross references | Objectives, methodology, business plan and survey, data standard list, interface cross references |
| Interoperability use cases | PD ISO/TR 17185-3:2015 (ISO/TR 17185-3:2015) | Use cases for journey planning systems and their interoperation | Importance of user information, objectives of ISO 17185, journey planning use cases and interoperability requirements |
โ ๏ธ The series is a technical report focused on frameworks and methodology rather than software implementation specifics; actual integration still needs to be grounded in regional standards (e.g., European NeTEx, SIRI) and local data sources.
2. Public Transport Data and Interface Standards Catalogue ๐
The core objective of Part 2 is to establish a “data catalogue and cross reference document” so stakeholders can map the standards landscape of public transport passenger information:
- Catalogue objectives: identify data standards relevant to passenger information and clarify each standard’s scope and relationships.
- Methodology: gather industry usage and needs through a business plan and survey.
- Standard list and cross references: systematically organise standards for timetables, real-time vehicle location, fares, network data, and give the reference relationships among them.
- Evolution mechanism: suggest mechanisms for continuous updating so the catalogue follows technology and business development.
โ
A standards catalogue is like a “map” of the passenger information domain: listing plus cross references helps system designers quickly locate which standard to use and how it links to others, reducing selection errors.
3. Journey Planning System Interoperability Objectives ๐บ๏ธ
Part 3 addresses the importance of passenger information and sets out the needs and use cases for journey planning interoperability:
- Importance of user information: high-quality, timely and accessible travel information significantly improves the attractiveness of public transport and passenger satisfaction.
- Objectives of ISO 17185: establish unified information semantics and interface requirements for multimodal journey planning, supporting cross-region, cross-operator itineraries.
- Interoperability use cases: describe typical scenarios such as multimodal journey queries, real-time transfer connections and personalised travel advice.
- Interoperability requirements: define the data exchange, capability negotiation and exception handling needs between use cases to support interoperability validation.
โ ๏ธ The biggest barrier to journey planning interoperability is often not technology but inconsistent data semantics and fragmented interfaces: the same “line/stop” encoded differently across systems distorts planning results. The use cases aim to remove such ambiguity.
4. Typical Application Scenarios ๐ง
| Scenario | Data Involved | Typical Interface/Standard Domain | Series Support |
|---|---|---|---|
| Multimodal journey query | Network, timetable, real-time vehicle location | Journey planning data exchange | Part 2 catalogue, Part 3 use cases |
| Real-time transfer connection | Real-time arrivals/departures, delay prediction | Real-time information interface | Part 3 interoperability requirements |
| Fares and ticketing information | Fare structure, payment options | Fare data standards | Part 2 cross references |
| Personalised travel advice | User preferences, accessibility information | Information service interfaces | Part 3 use case analysis |
5. Engineering Practice Essentials ๐ ๏ธ
- ๐ System design: when developing travel apps or passenger information services, first review available data standards using the Part 2 catalogue, then clarify interoperability scenarios against Part 3 use cases.
- ๐ง Data governance: build data dictionaries and semantic mapping to unify the coding of lines, stops and vehicles, ensuring cross-system data consistency.
- ๐ Interoperability testing: construct test scenarios from the use cases to verify correct fusion of data from different sources in the journey planning engine.
- ๐ Ecosystem collaboration: operators, data providers and software developers should work from common standards, push open data interfaces and reduce integration costs.
6. Frequently Asked Questions โ
โ Q: How does ISO 17185 relate to European NeTEx / SIRI?
A: ISO 17185 is a framework-level technical report on public transport user information, while NeTEx and SIRI are concrete data-exchange standards; the series aligns with them at the framework level, and implementation typically uses such regional standards.
A: ISO 17185 is a framework-level technical report on public transport user information, while NeTEx and SIRI are concrete data-exchange standards; the series aligns with them at the framework level, and implementation typically uses such regional standards.
โ Q: Why is a “standards catalogue” document needed?
A: Transport IT standards are numerous and frequently updated; a catalogue with cross references helps practitioners quickly identify applicable standards and their relationships, reducing wrong choices.
A: Transport IT standards are numerous and frequently updated; a catalogue with cross references helps practitioners quickly identify applicable standards and their relationships, reducing wrong choices.
โ Q: What is the value of interoperability use cases?
A: Use cases convert abstract requirements into executable, verifiable scenarios, providing a common language for development, acceptance and interoperability testing โ key to practical deployment.
A: Use cases convert abstract requirements into executable, verifiable scenarios, providing a common language for development, acceptance and interoperability testing โ key to practical deployment.
๐ Q: Do the technical reports require specific system features?
A: No. They provide a reference framework and methodology; actual functional choices are decided by operators and developers based on business needs, regulation and investment.
A: No. They provide a reference framework and methodology; actual functional choices are decided by operators and developers based on business needs, regulation and investment.