| Nosaukums | To operate most effectively, public transport systems increasingly need to
exchange information with each other. This integration can be difficult when
systems are provided by different suppliers. This difficulty is usually not for
technical reasons, thanks to the widespread usage of relevant technologies but
rather, because one system will often not understand the meaning of the data
that is used by another.
This is the reason why a Public Transport Reference Data Model has been
developed and was voted as a European Norm (EN 12896, known as Transmodel
V5.1) in 2006, providing a standardised framework for defining and agreeing data
structures for major business areas of Public Transport.
Developments since 2006 have created additional requirements. One of the most
notable is the data model referring to the fixed objects for Public Transport,
known as IFOPT. IFOPT and Transmodel V5.1 have been taken into account in the
elaboration of the TS NeTEx (Network and Timetable Exchange). Transmodel V5.1
with some supplementary requirements has been a building block of the TS SIRI.
These developments have extracted parts of Transmodel and extended them.
It is therefore necessary to issue updated Transmodel documentation fully in line
with the latest requirements, expressed by Transmodel users over the last six
years.
The main objective of this WI is to develop the Public Transport Reference Data
Model, based on:
EN12896, Public Transport Reference Data Model (Transmodel V5.1), CEN TS
28701( IFOPT), CEN TS 15531(SIRI), extensions introduced by the TS NeTEx and
ensure compatibility with NeTEx and SIRI.
Particular attention will be drawn to the data model structure and methodology:
the data model will be described in UML, in a modular form in order to facilitate
the understanding and use of the model.
The following functional domains will be considered:
• Network Description: routes, lines, journey patterns, timing patterns,
service patterns, scheduled stop points and stop places. This part corresponds to
the network description as in Transmodel V5.1 extended by the relevant parts of
IFOPT.
• Vehicle Scheduling (timing information: runtimes, vehicle journeys, day
type-related vehicle schedules)
• Passenger Information (planned and real-time)
• Operations Monitoring and Control: operating day-related data, vehicle
follow-up , control actions
• Fare Management (fare structure, sales, validation, control)
• Management Information and Statistics
• Driver Management: Driver Scheduling (day-type related driver
schedules), Rostering (ordering of driver duties into sequences according to some
chosen methods), Personnel Disposition (assignment of logical drivers to physical
drivers and recording of driver performance)
The data modules dedicated to cover most functions of the above domains will be
specified.
The following transport modes will be considered: bus, metro, tramway,
trolleybus, ferry, coach, rail.
This proposed European Standard will be made up of 8 parts :
Public Transport Reference Data Model - Part 1: Common Concepts
Public Transport Reference Data Model - Part 2: Public Transport Network
Public Transport Reference Data Model - Part 3: Timing Information and Vehicle
Scheduling
Public Transport Reference Data Model - Part 4: Passenger Information
Public Transport Reference Data Model - Part 5: Operations Monitoring and
Control
Public Transport Reference Data Model - Part 6: Fare Management
Public Transport Reference Data Model - Part 7: Management Information and
Statistics
Public Transport Reference Data Model - Part 8: Driver Scheduling- Rostering -
Personnel Disposition |
|---|
| Darbības sfēra | To operate most effectively, public transport systems increasingly need to
exchange information with each other. This integration can be difficult when
systems are provided by different suppliers. This difficulty is usually not for
technical reasons, thanks to the widespread usage of relevant technologies but
rather, because one system will often not understand the meaning of the data
that is used by another.
This is the reason why a Public Transport Reference Data Model has been
developed and was voted as a European Norm (EN 12896, known as Transmodel
V5.1) in 2006, providing a standardised framework for defining and agreeing data
structures for major business areas of Public Transport.
Developments since 2006 have created additional requirements. One of the most
notable is the data model referring to the fixed objects for Public Transport,
known as IFOPT. IFOPT and Transmodel V5.1 have been taken into account in the
elaboration of the TS NeTEx (Network and Timetable Exchange). Transmodel V5.1
with some supplementary requirements has been a building block of the TS SIRI.
These developments have extracted parts of Transmodel and extended them.
It is therefore necessary to issue updated Transmodel documentation fully in line
with the latest requirements, expressed by Transmodel users over the last six
years.
The main objective of this WI is to develop the Public Transport Reference Data
Model, based on:
EN12896, Public Transport Reference Data Model (Transmodel V5.1), CEN TS
28701( IFOPT), CEN TS 15531(SIRI), extensions introduced by the TS NeTEx and
ensure compatibility with NeTEx and SIRI.
Particular attention will be drawn to the data model structure and methodology:
the data model will be described in UML, in a modular form in order to facilitate
the understanding and use of the model.
The following functional domains will be considered:
• Network Description: routes, lines, journey patterns, timing patterns,
service patterns, scheduled stop points and stop places. This part corresponds to
the network description as in Transmodel V5.1 extended by the relevant parts of
IFOPT.
• Vehicle Scheduling (timing information: runtimes, vehicle journeys, day
type-related vehicle schedules)
• Passenger Information (planned and real-time)
• Operations Monitoring and Control: operating day-related data, vehicle
follow-up , control actions
• Fare Management (fare structure, sales, validation, control)
• Management Information and Statistics
• Driver Management: Driver Scheduling (day-type related driver
schedules), Rostering (ordering of driver duties into sequences according to some
chosen methods), Personnel Disposition (assignment of logical drivers to physical
drivers and recording of driver performance)
The data modules dedicated to cover most functions of the above domains will be
specified.
The following transport modes will be considered: bus, metro, tramway,
trolleybus, ferry, coach, rail.
This proposed European Standard will be made up of 8 parts :
Public Transport Reference Data Model - Part 1: Common Concepts
Public Transport Reference Data Model - Part 2: Public Transport Network
Public Transport Reference Data Model - Part 3: Timing Information and Vehicle
Scheduling
Public Transport Reference Data Model - Part 4: Passenger Information
Public Transport Reference Data Model - Part 5: Operations Monitoring and
Control
Public Transport Reference Data Model - Part 6: Fare Management
Public Transport Reference Data Model - Part 7: Management Information and
Statistics
Public Transport Reference Data Model - Part 8: Driver Scheduling- Rostering -
Personnel Disposition |
|---|
