1 / 10

2011.10.12 PTIC Oldham

NeTEx (Network Exchange) A Transmodel based XML schema for Public Transport for Europe Networks, Stops, Timetables. 2011.10.12 PTIC Oldham. Nick Knowles Kizoom. CEN Working Group TC 278 WG3 SG9. NeTEx What is it ?

teness
Télécharger la présentation

2011.10.12 PTIC Oldham

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NeTEx(Network Exchange)A Transmodel based XML schema for Public Transport for EuropeNetworks, Stops, Timetables 2011.10.12 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 2

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

  4. 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

  5. Netex Part3 - Boundaries

  6. NeTEx Status Oct 2011

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

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

  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 2Scheduled 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 9

  10. Outline Scope : Part 3 Part 3Fare 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 4.2.2.1) Standard for the exchange of fare information in the context of connection with other modes of transport (TAP-TSI 4.2.22) 10

More Related