SIST-TS CEN/TS 15531-6:2024
(Main)Public transport - Service interface for real-time information relating to public transport operations - Part 6: Functional service interfaces: Control Actions
Public transport - Service interface for real-time information relating to public transport operations - Part 6: Functional service interfaces: Control Actions
The CONTROL ACTIONs in SIRI are, of course, expected to be fully based on Transmodel.
Transmodel describes all the necessary scheduled information (exchanged using NeTEx) that may be variously referenced by CONTROL ACTIONs, such as VEHICLE JOURNEYs, VEHICLE ASSIGNMENTs, TIMING POINTs, RUN TIMEs, BLOCKs and VEHICLE SERVICEs, DUTies and DUTY STRETCHs, etc. and more generally the detailed production plan.
The SIRI CONTROL ACTION Service will complement this with real-time information, mainly based on the concepts described by Transmodel.
Transmodel identifies four main groups of CONTROL ACTIONs, as summarised in the following lines:
• Vehicle Control Actions
• Elementary Journey Control Actions
• Composite Control Actions
• Interchange Control Actions
• Vehicle Detection
The CONTROL ACTION description will, of course, need to be articulated with other SIRI services. For example, CONTROL ACTIONs will have to be referenced by Situations provided by SIRI SX in order to complement the cause of the Situation (a CONTROL ACTION may even be the only cause of a Situation).
It will also be useful to be able to reference CONTROL ACTION from a service like Estimated Timetable (and more generally all descriptions of Monitored Journeys) in order to provide a list of control actions currently applied on specific Journeys.
The SIRI CONTROL ACTION Service shall be consistent with NeTEx whenever this is possible. As a natural complement to the network topology and that timetables, a specific care should be taken to properly relate to relevant elements in NeTEx.
• TimingPoint
• RunTime
• Block and VehicleService for operation.
• Duty and DutyStretch describing the driver work assignments.
The TS will take into account existing work (will be referenced in the bibliography. The TS will however not be based on it). E.g.
Organization name: NOPTIS (Nordic Public Transport Interface Standard)
Document reference: NOPTIS IS-PT_I_RII_2
Publication date: 2012-10-04
Öffentlicher Verkehr - Dienstschnittstelle für Echtzeitinformationen bezogen auf Operationen im Öffentlichen Verkehr - Teil 6: Funktionale Dienstschnittstelle - Steuerungsaktion
No scope available
Transport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 6 : Interfaces des services fonctionnels - Actions de régulation
No scope available
Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza - 6. del: Vmesniki funkcionalnih storitev: Nadzorni ukrepi
Ta dokument določa dodatno funkcionalno storitev vmesnika za informiranje v realnem času (SIRI) za izmenjavo informacij o nadzornih ukrepih med nadzornimi sistemi in strežniki, ki vsebujejo podatke o vozilu javnega prevoza ali času potovanja v realnem času. To vključuje nadzorne centre izvajalcev prevoza in informacijske sisteme, ki zagotavljajo potovalne informacije za potnike. V okviru podatkovnega modela Transmodel načini javnega prevoza
vključujejo nove načine prevoza (souporaba vozil, sopotništvo itd.).
Ta dokument opisuje storitev nadzornih ukrepov vmesnika za informiranje v realnem času (SIRI-CA), ki je del modularnega nabora storitev za izmenjavo informacij v realnem času. Storitev nadzornih ukrepov vmesnika za informiranje v realnem času zajema izmenjavo informacij o sprejemu odločitve v zvezi z upravljanjem delovanja sistema prevoza v realnem času s strani upravljavcev med izvajanjem storitev.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-oktober-2024
Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja
javnega prevoza - 6. del: Vmesniki funkcionalnih storitev: Nadzorni ukrepi
Public transport - Service interface for real-time information relating to public transport
operations - Part 6: Functional service interfaces: Control Actions
Öffentlicher Verkehr - Dienstschnittstelle für Echtzeitinformationen bezogen auf
Operationen im Öffentlichen Verkehr - Teil 6: Funktionale Dienstschnittstelle -
Steuerungsaktion
Transport public - Interface de service pour les informations en temps réel relatives aux
opérations de transport public - Partie 6 : Interfaces des services fonctionnels - Actions
de régulation
Ta slovenski standard je istoveten z: CEN/TS 15531-6:2024
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
CEN/TS 15531-6
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
June 2024
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Public transport - Service interface for real-time
information relating to public transport operations -
Part 6: Functional service interfaces: Control Actions
Transport public - Interface de service pour les Öffentlicher Verkehr - Dienstschnittstelle für
informations en temps réel relatives aux opérations de Echtzeitinformationen bezogen auf Operationen im
transport public - Partie 6 : Interfaces des services öffentlichen Verkehr - Teil 6: Funktionale
fonctionnels - Actions de régulation Dienstschnittstelle - Steuerungsaktion
This Technical Specification (CEN/TS) was approved by CEN on 15 April 2024 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATIO N
EUROPÄISCHES KOMITEE FÜR NORMUN G
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 15531-6:2024 E
worldwide for CEN national Members.
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 8
4 Symbols and abbreviations . 8
5 Business Context . 8
5.1 General. 8
5.2 Main use cases and needs . 9
5.3 System overview and dataflow . 9
6 Relation with Transmodel Concepts . 12
6.1 General. 12
6.2 Vehicle Control Actions . 13
6.3 Elementary Journey Control Actions . 14
6.4 Composite Control Actions . 15
6.5 Interchange Control Actions . 16
6.6 Vehicle Detection . 17
7 Communication Infrastructure . 17
7.1 General. 17
7.2 SIRI Service Request table . 17
7.3 Communications Bandwidth . 19
8 Control Action Service [CA] . 19
8.1 Description . 19
8.2 Reference Data . 20
8.3 Capability and Permission Matrices . 20
8.3.1 Capability Matrix . 20
8.3.2 Permission Matrix . 22
8.4 ControlActionRequest . 22
8.4.1 ControlActionRequest Definition . 22
8.4.2 ControlActionRequest Example . 23
8.5 ControlActionSubscriptionRequest . 24
8.5.1 ControlActionSubscriptionRequest Definition . 24
8.6 ControlActionDelivery . 24
8.6.1 General. 24
8.6.2 ControlActionHeaderStructure. 24
8.6.3 Header and management of CONTROL ACTIONS. 25
8.6.4 VehicleControlAction. 30
8.6.5 JourneyControlAction . 31
8.6.6 NetworkControlAction . 39
8.6.7 Interchange Control Action . 40
8.6.8 DriverMessage . 41
8.6.9 VehicleDetecting . 43
8.7 Example of Control Action Delivery . 44
9 Integration with other SIRI services . 45
9.1 Integration with SIRI Situation Exchange . 45
9.2 Integration with SIRI Estimated Timetable . 46
9.3 Examples of possible relations between SIRI services related to Control Actions . 46
10 Further improvements to Transmodel . 48
10.1 General . 48
10.2 Concept of CHANGE OF STOP POINT STATUS . 48
10.3 Concept of GROUP OF CONTROL ACTIONS . 49
Bibliography . 51
European foreword
This document (CEN/TS 15531-6:2024) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a standardization request addressed to CEN by the European
Commission. The Standing Committee of the EFTA States subsequently approves these requests for its
Member States.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Introduction
Public transport services rely increasingly on information systems to ensure reliable, efficient operation
and widely accessible, accurate passenger information. These systems are used for a range of specific
purposes: setting schedules and timetables; managing vehicle fleets; issuing tickets and receipts;
providing real-time information on service running, and so on.
SIRI (CEN/TS 15531-1:2006) has been a CEN Technical Specification since 2007 and a European
normative standard since 2013 and has been widely used in Europe and elsewhere and proven its
usefulness.
This document describes the SIRI Control Action (SIRI-CA) is an additional service, part 6, based on the
European normative standard known as “SIRI” − Service Interface for Real-time Information. SIRI
provides a framework for specifying communications and data exchange protocols for organisations
wishing to exchange Real-time Information (RTI) relating to public transport operations
The SIRI European Standard is presented in three normative standard parts:
— context and framework, including background, scope and role, normative references, terms and
definitions, symbols and abbreviations, business context and use cases (EN 15531-1);
— the mechanisms to be adopted for data exchange communications links (EN 15531-2);
— data structures for a series of individual application interface modules PT, ET, ST, SM, VM, CT, CM,
GM (EN 15531-3).
Three additional parts define additional functional services as CEN Technical Specifications:
— additional data structures for additional application interface module FM (CEN/TS 15531-4);
— additional data structures for additional application interface module SX (CEN/TS 15531-5);
— additional data structures for additional application interface module CA (CEN/TS 15531-6).
It is recognized that SIRI is not complete as it stands, and from time to time will need to continue to be
enhanced to add additional capabilities. It is therefore intended that a SIRI Management Group should
continue to exist, at European level, based on the composition of SG7.
This document specifies a Service Interface for Real-time Information (SIRI) about Public Transport. It is
intended to be used to exchange information between ser
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.