NeTEx (Network Exchange) A Transmodel based XML schema for Public Transport for Europe Networks, Stops, Timetables PTIC Oldham Nick Knowles Kizoom

2 CEN Working Group TC 278 WG3 SG9 NeTEx  What is it ? New CEN standard for XML Public Transport data exchange - for Passenger Information (timetables + fares) Approach: Model Driven Design  Transmodel UML  Physical UML  XML  Who are active participants? Austria, Germany, France, Hungary, Italy, Netherlands, Sweden, Switzerland, ERA/UIC, UK,  Timescales Three phases: Part 1 : Part 2: Part 3: 2012  Inputs CEN: Transmodel, IFOPT National: VDV 452, TransXChange, Trident /Choutte, UIC ++  Deliverables CEN specification document, NeTEx XML schema as reusable packages XML Examples National Mapping tables

NeTEx Stages CEN NeTEx 1.0 Part1 UIC leaflets SIRI Transmodel VDV452 Trident/ NEPTUNE TransXChange, etc IFOPT Transmodel CEN NeTEx 1.0 Part2 Transmodel NaPTAN, etc CEN NeTEx 1.0 Part3 Bison, Noptis, etc TAP TSI, Rail Fares FareXChange, etc IOPTA requirements

NeTEx Fare Use cases Provide information on fare products and their rules and restrictions to passengers  Handoff to ticket purchase for a given journey  Distributing fare product information for publication  Distributing fares information to online systems  Provide information on fare products and their rules and restrictions for a specific journey,  Identify time schedules and conditions for the lowest fares  Show fare zones on topographical and schematic maps,  Exchange of fare information between long distance (i.e. heavy rail) and local public transport  Provide a price calculator with up to date fare information  Submitting a fare scheme for approval  Provisioning of ticket vending machines with fare information  Provisioning of ticket checking devices 4

Netex Part3 - Boundaries 5

NeTEx Status Oct Common Framework Part 1Part 2Part 3 Use casesRev Draft In Progress UML Conceptual Rev Draft Prelim Draft UML PhysicalRev Draft Draft1 XML SchemaRev Draft Draft1 CEN Specification Partial DraftIn Progress To do ExamplesRev Draft Draft1 UK Profile-Draft NaPTAN3.0 To do UK Mapping-Examples Using NaPTAN data To do TXC 2.4 examples & ATCO.CIF? ? FXC

NeTEx – UK Equivalences 7 PART1 – Framework = NPTG + Operator ++ PART 1 - Stops NAPTAN +++ Extended ( NAPTAN 3.0V PART 3 – Fares = “FareExchange” PART 2 – TimetablesT = TRANSXCHANGE ++ Extended Calendar,

Network Links Lines, Routes Fare Products Accessibility Stop Places Travel Documents Operational Data Tariff Structure Points Of Interest Fare Pricing Parameters Schedules, (Fixed & DRT) Topography Part 1 Part 2 Part 3 Core & Generic: Versioning, Frames NetEx Module layers Common Service Patterns Timing Patterns Operators & Authorities Calendars Network Restrictions Interchanges Coupled Journeys, Train Composition Parking for PT Stops, Connections NPTG Naptan TXC FXC Vehicle Types Equipment & Facilities Responsibility

9 Outline Scope: Part 1 & 2 Focuses on objects and information required for passenger information and exchange between transit scheduling systems and AVMS Part 1 Public transport Network Topology exchange format Infrastructure, infrastructure constraints, routes, etc. Stop Places, Accessibility, paths Garages, Crew points, Beacon Points for Vehicle Management & AVMS Part 2 Scheduled Timetables exchange format Part 2A : Basic time related data (shared by all the domains): journey patterns, journey times, service patterns, operating days, interchanges, etc. Multimodal Part 2B : Passenger information specific objects: trip patterns, trip duration (passing times, origin/destination places of passenger trips, etc.: additional data related to passenger information functions Part 2C : Data used specifically in the exchanges between the scheduling & vehicle monitoring systems (blocks and related concepts) Part 2D : Data used in and/or defined by the vehicle monitoring systems, data linked to vehicle equipment and necessary for passenger information systems for AVMS/passenger information

10 Outline Scope : Part 3 Part 3 Fare information exchange format.  Multimodal information systems providing planned passenger information  Planned tariff information exchanged between service operators, service operators and product owners (i.e. authorities, etc.) Includes  Different Tariff Structures (Spatial, Time based, Yield managed)  Fare Pricing Parameters Excludes  Management of fare product and applications  Certification, registration and identification  Purchasing and fulfillment  (Actual Price calculation) Provide inputs for ERA–TAP/TSI open points to be solved by 2012  Technical document on the process and the information used for it in respect of tariff data intended for domestic sales (TAP-TSI )  Standard for the exchange of fare information in the context of connection with other modes of transport (TAP-TSI )