There are many potential ways for passenger transport operations centres to interact. The approach taken by SIRI is for an open-ended set of standard data structures, carried over a communications channel constructed using one of a small number of specific options. Part 2 of this European Standard specifies the communications channel. Part 3 specifies a number of functional modules, based on the \u2018use cases\u2019 identified in Annex B to Part 1: \u2014 Production Timetable (PT): this service enables the provision of information on the planned progress of vehicles operating a specific service, identified by the vehicle time of arrival and departure at specific stops on a planned route for a particular Operational Day. \u2014 Estimated Timetable (ET): this service enables the provision of information on the actual progress of Vehicle Journeys operating specific service lines, detailing expected arrival and departure times at specific stops on a planned route. There will be recorded data for stops which have been passed, and predicted data for stops not yet passed. In addition the Estimated Timetable service allows Vehicle Journeys to be cancelled, added or changed. \u2014 Stop Timetable (ST): this service provides a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. It can be used to reduce the amount of information that needs to be transmitted in real-time to stops and displays, as reference data for a Stop Monitoring Service; and provides a data feed of the static timetables. \u2014 Stop Monitoring (SM): this service provides a stop-centric view of vehicle arrivals and departures at a designated stop. It can be used by displays and other presentation services to provide departure board and other presentations of timetable and real-time journey information both at stops and at a distance. \u2014 Vehicle Monitoring (VM): this service enables the provision of information on the current location and status of a set of vehicles. It provides all the current relevant information from one AVMS relating to all vehicles fulfilling a set of selection criteria. \u2014 Connection Timetable (CT): this service may be used to provide information about the scheduled arrivals of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then plan how to guarantee the connection, either with the expected vehicle or a different vehicle. \u2014 Connection Monitoring (CM): this service is used to provide information about the expected arrival of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then manage the service to guarantee the connection, based on actual vehicle running. \u2014 General Message (GM): the SIRI ‘General Message\u201d service is used to exchange informative messages between identified individuals in free or an arbitrary structured format. It enables messages to be sent and to be revoked. Messages are assigned validity periods in addition to the actual content.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 182<\/td>\n | Contents Page <\/td>\n<\/tr>\n | ||||||
| 186<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 187<\/td>\n | 4 Symbols and abbreviations 5 Production Timetable Service [PT] <\/td>\n<\/tr>\n | ||||||
| 200<\/td>\n | 6 Estimated Timetable Service [ET] <\/td>\n<\/tr>\n | ||||||
| 222<\/td>\n | 7 Stop Timetable Service [ST] <\/td>\n<\/tr>\n | ||||||
| 230<\/td>\n | 8 Stop Monitoring Service [SM] <\/td>\n<\/tr>\n | ||||||
| 261<\/td>\n | 9 Vehicle Monitoring Service [VM] <\/td>\n<\/tr>\n | ||||||
| 276<\/td>\n | 10 Connection Timetable Data Service [CT] <\/td>\n<\/tr>\n | ||||||
| 286<\/td>\n | 11 Connection Monitoring Service [CM] <\/td>\n<\/tr>\n | ||||||
| 301<\/td>\n | 12 General Message Service [GM] <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Public transport. Service interface for real-time information relating to public transport operations – Functional service interfaces<\/b><\/p>\n |