The Signalling Programme Fjernbane Infrastructure East/West BAFO Tender Document Appendix 3.5 – Interface Requirements Banedanmark The Signalling Programme Amerika Plads 15 DK-2100 Copenhagen E Denmark Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Author: Fjernbane Signalling System Project Mail: Fjernbane@bane.dk Phone: +45 8234 0000 www.banedanmark.dk Appendix 3.5 – Interface Requirements Page 2 of 98 Appendix 3.5 – Interface Requirements Table of Contents Page 1 Change Log 6 2 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.3 Introduction Purpose and Contents Purpose Contents Relationship to other appendices Reader’s Instructions Notes for the Suppliers Tenderer’s deliveries Major Changes 7 7 7 7 8 8 8 9 9 3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.1.9 3.1.10 3.1.11 3.1.12 3.1.13 3.1.14 3.1.15 3.1.16 3.1.17 3.1.18 3.1.19 3.1.20 3.1.21 3.1.22 3.1.23 3.1.24 3.1.25 System Context External Systems Bascule Bridges, IF 001 Catenary Management System, IF 002 Civil Works, IF 003 Closed Circuit TV Systems, IF 004 Common Interface, IF 005 Control Systems of Depots and stabling Tracks, IF 006 Customer Back-office Systems, IF 007 TOC Driver Guidance Tool, IF 008 Electrical Power Supply, IF 009 Emergency Services (AlarmCentralen 112), IF 010 ERTMS fitted Trains, IF 011 File System, IF 013 Fixed Transmission Network, IF 014 Foreign Key Management Centre, IF 015 GSM-R, IF 016 Sund & Bælt Detectors, IF 017 Identity Management System, IF 018 Interlocking System – Existing Fjernbane, IF 019 Interlocking System – Foreign Railway, IF 020 Interlocking System – Neighbouring Fjernbane Infrastructure, IF 021 Interlocking Systems – Private Lines, IF 022 Interlocking System – S-bane, IF 023 Other Infrastructure Elements, IF 024 Neighbouring Key Management System, IF 025 Passenger Information System, IF 026 Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 10 10 12 12 12 12 12 12 13 13 13 13 14 14 14 14 14 14 15 15 15 15 15 16 17 17 17 Appendix 3.5 – Interface Requirements Page 3 of 98 3.1.26 3.1.27 3.1.28 3.1.29 3.1.30 3.1.31 3.1.32 3.1.33 3.1.34 3.1.35 3.1.36 3.1.37 3.1.38 3.1.39 3.1.40 3.1.41 3.1.42 3.1.43 3.1.44 3.1.45 3.1.46 3.1.47 3.1.48 3.1.49 3.1.50 3.2 4 4.1 4.2 4.2.1 4.2.2 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.3.7 4.3.8 4.3.9 4.3.10 4.3.11 4.3.12 4.3.13 4.3.14 4.3.15 4.3.16 Permanent Magnets, IF 027 Point Heating Control System, IF 028 Points, IF 029 Possession Planning System, IF 030 Punctuality/Delay reporting system, IF 031 RBC – Neighbouring Fjernbane Infrastructure, IF 032 RBC – Foreign Railway, IF 033 Road Signalling System, IF 034 Road Vehicle Detection Systems, IF 035 Sidings not in Stations, IF 036 SCADA (SRO) Systems, IF 037 Telephone Exchange/Switchboard, IF 038 Time Reference, IF 039 Offline Production Plan, IF 040 TMS_Existing Fjernbane, IF 041 TMS_Foreign Railways, IF 042 TMS_Neighbouring Fjernbane Infrastructure, IF 043 TMS_Private Lines, IF 044 TCC Building Control System, IF 045 Train Operating Companies’ Management Systems, IF 046 Unfitted and closed Lines, IF 047 UT Circular System, IF 048 Failurement Management Tool, IF060 SAP PM, IF061 Train Status, IF 101 Users 17 17 17 17 18 18 18 18 18 18 19 19 19 19 19 20 20 20 21 21 22 22 22 22 22 23 Interface Requirements 24 Interface Overview Diagram 26 Integration Architecture and Response Times 29 Communication and integration types 29 Estimated response times 32 Interface Definitions 34 Interlocking Existing Fjernbane, Foreign Railway, Neighbouring Fjernbane Infrastructure, Private lines, S-bane 36 RBC Foreign Railway and RBC Neighbouring Fjernbane Infrastructure 38 Bascule Bridge 39 Catenary Management System 40 TCC building 41 Train Operating Companies management systems (TOC MS), Train Status 41 ERTMS Fitted Train 50 File System 53 Neighbouring Key Management Centre 54 Foreign Key Management Centre 54 GSM-R 55 Identity Management System 57 Passenger Information System 57 Point Heating Control System 60 Possession Planning System 60 Punctuality / Delay Reporting System 60 Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 4 of 98 4.3.17 4.3.18 4.3.19 4.3.20 4.3.21 4.3.22 4.3.23 4.3.24 4.3.25 4.3.26 4.3.27 4.3.28 4.3.29 4.3.30 4.3.31 4.4 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.5.8 4.5.9 4.6 Road Signalling System Tunnel and Bridge SCADA (SRO) Systems and Detectors Telephone Exchange/Switchboard Time Reference Offline Production Plan TMS Existing Fjernbane TMS Foreign Railway TMS Neighbouring Fjernbane Infrastructure TMS Private lines UT Circular System Emergency Services (Alarmcentralen 112) Customer Back-office systems CCTV Failure Management Tool SAP PM System-Users Interface Definitions Interface Design Constraints Fjernbane Infrastructure System - Internal Adjacent Signalling Systems BDK Legacy Assets and Equipment Civils Infrastructure Concurrency Resiliency and robustness Common Interface Data representation User Interaction User–Interface Design Constraints 61 61 63 64 64 65 65 67 70 72 72 73 74 75 76 78 78 78 79 80 88 88 89 89 90 92 92 5 Internal Interfaces – BDK Owned 96 6 References 97 7 Attachments 98 Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 5 of 98 1 Change Log Made by Version Commented by Approved by Status XRZL/ 13. 2.0 Issued to Tenderers 3.0 Updated version issued 4.0 Issued to Tenderers for 07.2010 LGRN/ 30. 09.2010 XHRJ/ 30.6.2011 Fjernbane Infrastructure East/West Document1 BAFO BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 6 of 98 2 Introduction 2.1 Purpose and Contents Purpose 2.1.1 This document forms part of the range of documents that make up the overall Invitationto-Tender package, prepared by the Customer’s project team. This package consists of the Contract and Appendices to the Contract. This document represents Appendix 3.5 of the Contract – dealing with the Interface Requirements of the Fjernbane Infrastructure System of Banedanmark. It provides detailed interface definitions as well as the Requirements for the Delivery to adapt to them. Rather than attempt to offer a complete and comprehensive record of all possible interface Requirements, the main strength of this document is to identify the peer systems and users that the Fjernbane Infrastructure system shall interface to. This document at the same time provides a structured approach capturing as much information as is currently known by the Customer about such interfaces. This is instrumental in allowing the Supplier to reach fair conclusions for the purpose of making an offer to the Customer. Thereafter, it is the Customer’s intention that through close collaboration with the Supplier, especially by means of a joint design phase, the range, depth, accuracy, consistency and sustainability of the information captured for specific interfaces will increase in proportion to system development and maturity. Contents 2.1.2 The contents of this document are laid out in the following way: Chapter 2: Introduction, Purpose, Structure of the document and its relation with other Appendices of the Contract. Chapter 3: Description of the System’s context, covering the System users as well as the range of external systems. These two groups by definition give rise to the need to capture the Interface Requirements. Chapter 4: General background to the topic of Interface Requirements and introduction of the “Interface Overview Diagram” - leading to the tabular presentation of the Interface Requirements set, collated for the Fjernbane Infrastructure System. Chapter 5 refers to the concept of “BDK Owned” as applied to interfaces. Please be advised that due to detailed diagrams and tabular content, this document is composed of both A4 and A3 page formats. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 7 of 98 2.1.3 Relationship to other appendices Interface Requirements depend heavily upon Functional Requirements being fulfilled on either side of the interface. There is also reliance on non-functional and process Requirements in order to capture the complete behaviour of the System within its operating context. Therefore this Appendix is closely related to the following appendices: Appendix 3.2 – Fjernbane Infrastructure System Functional Requirements Attachment 3 to Appendix 3.2 – TMS concept Appendix 3.3 – Fjernbane Infrastructure System Non-Functional Requirements Appendix 16 – Processes To gain a clearer understanding of the System Context, Appendix 3.1 provides a summary of the Delivery, including a graphical representation of the scope-of-supply requested from the Supplier. Attachment 5 to Appendix 3.1 introduces the Candidate Architecture used as a framework of understanding in order to develop the range of Requirements. More specialised types of non-functional Requirements can also be found within the following appendices: Appendix 3.4 Security Requirements Appendix 3.7 Training Requirements Appendix 5 Maintenance Appendix 6 Service Level Goals Appendix 14.1 Installation Appendix 14.2 Testing and Commissioning Appendix 14.3 Decommissioning Note that Appendix 3.8 contains Requirements specific to Options to the Contract Scope. 2.2 Reader’s Instructions 2.2.1 Notes for the Suppliers This section presently contains reader’s instructions to the Supplier. In the contract version this section will however be modified. Each section (from section 3 onwards) may contain: Guides in italics (Examples and/or explanatory text to support some requirements) Instructions for the Tenderer in brackets using bold red letters ((…)). Example: ((The Tenderer shall make sure that the Tenderer’s added text in the tender is clearly marked and can be easily distinguished from the text that the Customer has provided.)). Figures and Tables References are referred to as [x], where x is the reference number. A list of references is provided in section 6. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 8 of 98 Attachments are referred to as {x}, where x is the attachment number. A list of attachments is provided in section 7. This appendix does not include definitions and abbreviations, for these refer to Appendix 17 - Glossary. 2.2.2 Tenderer’s deliveries This Appendix does not require the Tenderer to provide any specific deliverables. 2.3 Major Changes This section contains a summary of the major changes in this version for BAFO compared with the version issued for the First Negotiation Tender. This section will be deleted in the final version for the Contract. The major changes are: All drawings/figures have been updated though not visible via track changes. An Enterprise Service Bus (ESB) is introduced between the Fjernbane Infrastructure System and selected systems to interface with. Interface requirements from the TMS Concept (Appendix 3.2, attachment 3) have been included in this document, so all requirements regarding external interfaces are congregated here. Detailed system user interfaces descriptions have been deleted to be replaced by more general requirements to the HMIs. In ‘First Negotiation Tender’ it was section 4.3, in this BAFO version it is section 4.4. It is noted that more changes are made. It is also noted that in some sections the change markings are omitted since the changes are so substantial that it does not make the section reader friendly if the change markings are maintained. In such situations the following is stated at the beginning of the section: “((The changes in this section are so substantial that the Customer has chosen not to show the change markings))” Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 9 of 98 3 System Context Within its operating context, the System interfaces both to other systems as well as to users of the System. The following subsections contain context diagrams representing these interactions as well as a brief and individual summary of the relationship between the Fjernbane Infrastructure System and other (i.e. external) systems as well as the relationship between the Fjernbane infrastructure System and the system users. 3.1 External Systems The figure below shows the context of the Fjernbane Infrastructure System in regard to the External Systems. “External Systems” means that these systems are not in the scope of the Delivery. To aid cross referencing, each External System Interface carries an individual number starting with ‘IF’, for instance IF016 is the interface for GSM-R. Please note that within in a given interface, such as IF016, a number of messages can be exchanged and each of these messages are named FbIS.I.nnn. Using the external system GSM-R as the example, it can be seen from Figure 4 that the following messages belong to IF016 (GSM-R): FbIS.I.436 FbIS.I.437 FbIS.I.438 FbIS.I.439 FbIS.I.440 ((Figure 1 has been updated to ensure consistency with the changes made to the document.)) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 10 of 98 Bascule Bridges Catenary Management System Closed Circuit TV Systems Civil Works Control Systems of Depots and stabling Tracks Train Status Customer Back-office Systems TOC Driver Guidance Tool Electrical Power Supply Emergency Services (Alarmcentralen 112) ERTMS fitted Trains UT Circular System File System 00 IF IF 08 IF 0 IF 00 IF 006 60 1 IF 04 TCC Building control system 2 IF 10 IF 0 00 04 IF 0 IF 3 Train Operating Companies’ Management Systems 1 00 IF 0 00 0 IF IF IF Unfitted and closed Lines 9 SAP PM 7 Failure Management Tool 01 0 IF 01 0 IF 48 61 0 IF 47 Fixed Transmission Network 1 13 IF 0 6 Foreign Key Management Center 14 1 IF 0 IF 045 GSM-R 5 IF 016 Sund & Bælt Detectors TMS_Private Lines IF 044 TMS_Neighbouring Fjernbane Infrastructure IF 017 BDK Fjernbane Infrastructure System Context IF 043 IF 042 TMS_Foreign Railway IF 04 IF 019 1 4 IF 0 TMS_Existing Fjernbane IF 02 0 IF 0 2 39 IF 0 38 IF 02 IF 030 1 IF 03 32 IF 6 IF 0 03 4 02 IF 03 IF 6 28 IF 03 3 37 9 IF 0 0 IF 0 IF Time Reference IF 0 IF 0 IF Offline Production Plan Identity Management System IF 018 IF 02 02 Interlocking_Existing Fjernbane 0 1 Interlocking_Foreign Railway 22 Interlocking_Neighbouring Fjernbane Infrastructure 23 4 5 Interlocking_Private lines Telephone Exchange/ Switchboard Interlocking_S-Bane SCADA (SRO) Systems Sidings not in Stations Other Infrastructure Elements Road Signalling Systems RBC_Foreign Railway RBC_Neighbouring Fjernbane Infrastructure Punctuality/Delay reporting system Possession Planning System Points Point Heating Control System Passenger Information System Neighbouring Key Management System Figure 1 The Fjernbane Infrastructure System’s Context Diagram. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 11 of 98 3.1.1 Bascule Bridges, IF 001 The Fjernbane Infrastructure System has to interface to the control system of some Bascule bridges as given in the table below. The Bascule bridges are operated locally, however they are interlocked with the Fjernbane Infrastructure System. Fjernbane Infrastructure East contract Masnedsundbro (Vordingborg) Frederik IX bro (Nykøbing Falster) 3.1.2 Fjernbane Infrastructure West contract Limfjordsbro (Ålborg) Oddesundbro (Struer) Catenary Management System, IF 002 The Catenary Management System is used to monitor and control the field elements of the traction power system, especially to switch power on and off on Catenary Sections. The Catenary Management System exchanges relevant data with the Traffic Management System that is part of the Delivery. 3.1.3 Civil Works, IF 003 For each site of a Technical Object Building, the Customer provides an access road or access by train, a prepared work site, parking facilities, exterior lighting as well as fencing where the securityRequirements make it necessary. 3.1.4 Closed Circuit TV Systems, IF 004 CCTV systems currently exist at a few stations to monitor station and platform areas. Viewing the platforms could be useful for Signal Operators to take decisions on train operation. Therefore, the Fjernbane Infrastructure System is expected to allow for viewing CCTV pictures on the TMS displays. 3.1.5 Common Interface, IF 005 Deleted. 3.1.6 Control Systems of Depots and stabling Tracks, IF 006 The Fjernbane Infrastructure System Delivery shall ensure that it is possible for trains to continue into the depots and stabling tracks. On an number of stations Shunting Interlocking Equipment is placed outside the physical limit of the existing interlocking, but either have an interface to the existing Interlocking or is operated by the existing Interlocking. Some of the equipment is not owned by Banedanmark, but by DSB or other stakeholders. Appendix 3.1, Attachment {7} [5] and Appendix 3.1, Attachment {8} [6] contains lists of all Shunting Interlocking Equipment outside the physical limit of the existing interlockings, including the ownership to each one and a brief description of the Interface to the Interlocking. Shunting Interlocking Equipment placed outside the physical limit of the existing interlocking with no technical interface to the Interlocking is out of scope of the Delivery. Possible Operational Interfaces are handled by the Customer. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 12 of 98 Shunting Interlocking Equipment placed outside the physical limit of the existing interlocking with technical interface to the Interlocking or integrated in the Interlocking is part of the delivery as described in Appendix 3.1 [4]. 3.1.7 Customer Back-office Systems, IF 007 The Customer uses different types of back-office systems to handle commercial and organisational aspects of his business including office programs. It must be possible to use these back-office systems within the Fjernbane Infrastructure System Delivery. Typical examples of such back-office systems are: Billing system Staff rostering tool Training and competence database. 3.1.8 TOC Driver Guidance Tool, IF 008 In the future, Driver Guidance Tools will provide the Driver with an in-cab advice to follow most efficient driving profiles combined with precise adherence to the Online Production Plan. The Traffic Management System (TMS) which is part of the Fjernbane Infrastructure System will provide the Driver guidance tool with dynamic input, so as to obtain a full control loop in the train operation. This means that Online Production Plan data transmitted to the TOC has a much higher precision and density of data than in the current situation. For more information on the Online Production Plan please refer to Ref. 1. Furthermore the Driver will be able to provide feedback to TMS of the Fjernbane Infrastructure System to inform on reason for delays etc. This aims at improving punctuality and capacity. Equal treatment of all Train Operating Companies has to be ensured. This interface also includes communication to and from the Guard to be able to advise on delays as well as enabling the guard to provide feedback to TMS. From the perspective of the Fjernbane Infrastructure System, the information both for Driver and Guard will be made available to the TOC system who in turn distribute it to the remote clients. DSB for example is currently implementing a Driver Guidance Tool called “Greenspeed” by 2011. 3.1.9 Electrical Power Supply, IF 009 The Customer draws non-traction power supplies from the public power suppliers around the country. The Customer provides a power feed at every location of a Technical Object Building. It is the Supplier’s responsibility to route the power feed into the Technical Object Building, to terminate the cable and to build up the power supply for the Delivery from these power feeds. 3.1.10 Emergency Services (AlarmCentralen 112), IF 010 The Supplier must provide the TMS workplaces with an interface to the emergency services i.e. Alarmcentralen – in such a way as to provide data automatically over the interface to save time with regard to authentication and accident location details etc. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 13 of 98 3.1.11 ERTMS fitted Trains, IF 011 All Danish trains expected to use the lines that are within the scope of fitment are fitted with ETCS Level 2 capability by means of On-board GSM-R and ETCS equipment. The latter is being procured through the Fjernbane On-board contract. Most of these trains are expected to be fitted with a specific transmission module allowing them to run over lines fitted with the existing Danish ATP system. Note, the Fjernbane Infrastructure System does not provide ETCS Level 1, therefore this interface is based on ETCS L2. Note also that ERTMS Fitted Danish trains are foreseen to communicate over GSM-R making use of both Circuit Switched as well as Packet switched (GPRS) communications. In line with the Interoperability standards, foreign ERTMS fitted trains (With ETCS Level 2 capability) are expected to run over the lines that are in scope of fitment. As their equipment may be provided by other suppliers than the equipment of the Danish ERTMS fitted trains, additional integration tests will be necessary. Again note, the Fjernbane Infrastructure System does not provide ETCS Level 1, therefore this interface is also based on ETCS L2. 3.1.12 File System, IF 013 The “File System” is the arrangement of servers that make up the Customer’s office IT system to which all the Customer’s employees have controlled access. The Fjernbane Infrastructure System will allow Users to take soft copies of the outputs of certain logs and the Telegramjournalen for offline analysis, such soft copies will need to be saved to the Customer’s “File System”. 3.1.13 Fixed Transmission Network, IF 014 The Fixed Transmission Network is operated by the Customer and used for a wide range of communication services. The Customer intends to make the Fixed Transmission Network available to the Supplier to use it as a part of the Delivery . 3.1.14 Foreign Key Management Centre, IF 015 Foreign Key Management Centres (from Sweden and ultimately the rest of Europe) manage the creation and distribution of cryptographic keys in conjunction with the Danish Key Management Centres to allow foreign vehicles to operate on the Danish railway infrastructure, and Danish trains to operate abroad. 3.1.15 GSM-R, IF 016 The Customer provides the GSM-R data network that is necessary to operate ETCS level 2. To ensure the necessary radio capacity on heavily trafficked lines and nodes, GPRS and possibly EDGE will be used. On the other hand, to ensure Interoperability, the circuit switched mode that is part of the ERTMS standard has still to be supported. Thus the Delivery of the Fjernbane Infrastructure contracts as well as the On-board equipment purchased through the Fjernbane On-board contract needs to support both modes to the full extent. 3.1.16 Sund & Bælt Detectors, IF 017 Hot Axle Box Detectors are located close to the Storebælt tunnel and the Øresund link. They send alarms to the Delivery of the Fjernbane Infrastructure System East contract in order to stop trains or change train movements. Systems associated to the Hot Axle Box Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 14 of 98 Detectors check for other defects of rolling stock like derailment and out of gauge. Similarly alarms are sent if a derailment or out of gauge is detected. The Hot Axle Box Detectors and the detectors for derailment and out of gauge are monitored by Sund & Bælt and the information is propagated to the Fjernbane Infrastructure System regardless of alarms. 3.1.17 Identity Management System, IF 018 The Fjernbane Infrastructure System shall interface with the Customer’s Identity Management System (IdM). The Customer operates the IdM system to administer all user accounts within the Customer environment. This is done to ensure consistency between staff roles and the respective profile on the IT systems with due regard for safety, security, confidentiality, etc. Please refer to Appendix 3.4 for further information on this topic. 3.1.18 Interlocking System – Existing Fjernbane, IF 019 This interface results from the need to migrate existing Interlocking Systems to the new Interlocking Systems. Attachment {3} to this document provides an overview, while Appendix 14.1 provides further details on the migration plan. 3.1.19 Interlocking System – Foreign Railway, IF 020 The Signalling System on lines that are in scope of fitment interfaces with the Signalling System of different foreign railway infrastructure managers. The interface consists of an interlocking interface at the following border locations: Fjernbane Infrastructure East Contract Peberholm (to Trafikverket) Ref. to attachments – permanent interfaces ETCS level 2 Padborg (to DB Netze) Ref. to attachments – permanent interfaces att 2 fig 2 Tønder (to NEG Niebüll) att 2 fig 3 Fjernbane Infrastructure West Contract 3.1.20 021 Interlocking System – Neighbouring Fjernbane Infrastructure, IF The Signalling System that is in the scope of fitment of the Fjernbane Infrastructure East Contract interfaces with the Signalling System of the Fjernbane Infrastructure West Contract and vice-versa. The interface is situated between Middelfart and Snoghøj on the Lillebælt Bridge and involves an interlocking interface. 3.1.21 Interlocking Systems – Private Lines, IF 022 The Signalling System on lines that are in scope of fitment interfaces with the Signalling System of different Danish private railways. The interface consists of an interlocking interface in all cases. The interfaces are situated at the following locations: Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 15 of 98 Fjernbane Infrastructure East Contract Helsingør (Lokalbanen A/S) Permanent interface type Ref. to description Not interlocked - Køge (Regionstog A/S) Line block type E80 att 2 fig 3 Holbæk (Regionstog A/S) Line block type E80 att 2 fig 3 Nykøbing Falster Vest (Regionstog A/S) Line block type E80 att 2 fig 3 Slagelse (Regionstog A/S) Line block type E80 att 2 fig 3 Snekkersten (Lokalbanen A/S) Line block type E80 att 2 fig 3 Tølløse (Regionstog A/S) Station interlocking type E80 att 2 fig 4 Fjernbane Infrastructure West Contract Århus H (Midtjyske Jernbaner A/S) Permanent interface type Ref. to description Line block type BS 1991 att 2 fig 3 Frederikshavn (Nordjyske Jernbanen A/S) Line block type E80 att 2 fig 3 Hjørring (Nordjyske Jernbanen A/S) Line block type E80 att 2 fig 3 Varde (Vestbanen A/S, operated by Arriva) Line block type BS 1991 att 2 fig 3 Vemb (Midtjyske Jernbaner A/S) Line block type BS 1991 att 2 fig 3 The interfaces will be more or less individual at each place, as different types of interlockings are used and railways not using ERTMS level 2 will continue using the existing SR75 operational rules. 3.1.22 Interlocking System – S-bane, IF 023 The Signalling System that is in the scope of fitment of the Fjernbane Infrastructure East Contract interfaces with the Signalling System of the S-bane at the following locations: Fjernbane Infrastructure East Contract Hellerup Høje Taastrup København H Køge Ny Ellebjerg (Vigerslev) Østerport TIB 7 Østerport – Lersøen Ref. to attachments – temporary interfaces (legacy Sbane) att 1 fig 3 not applicable not applicable att 1 fig 3 att 1 fig 3 not interlocked att 2 fig 3 Ref. to attachments – permanent interfaces (CBTC Sbane) att 1 fig 5 att 1 fig 5 att 1 fig 5 att 1 fig 5 att 1 fig 5 not interlocked att 1 fig 5 These interfaces are intended to be very basic, as they are only used for occasional works and freight trains. Note however, that the S-bane Interlocking Systems are also being modernised. The implication is that these interfaces must be retained and made available both for the existing S-bane Interlocking Systems as well as to the new Interlocking Systems Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 16 of 98 depending on project time schedules and corresponding progress. Therefore this interface must also be retained through the migration phase between old and new systems. Attachment {1} describes this in more detail. 3.1.23 Other Infrastructure Elements, IF 024 In addition to infrastructure elements expressly mentioned like Point Heaters and Hot Axle Box Detectors, other infrastructure elements may be interfaced to and monitored through the Fjernbane Infrastructure System. Examples could be Pumps, Flat wheel detectors etc. The field elements and transmission equipment necessary for this are a Customer Delivery. ((Sections deleted)) 3.1.24 Neighbouring Key Management System, IF 025 The Key Management System which is part of the Delivery of the Fjernbane Infrastructure East Contract interfaces to the Key Management System of the Fjernbane Infrastructure West Contract and vice-versa. The main goal of this interface is that a given train can use the same key on the entire Danish railway network. This interface is also subject to the outcome of the Option to provide a Key Management Solution for both East and West infrastructure. Please refer to Appendix 3.8 for further information. 3.1.25 Passenger Information System, IF 026 The Passenger Information System is used to provide passengers with information on the planned and actual train operation inside and outside the railway premises. The Traffic Management System which is part of the Fjernbane Infrastructure System provides the Passenger Information System with the necessary data on current and expected train operation. Hence this interface results in interfacing to the existing Passenger Information System – or the new Passenger Information System (Which is currently an Option. See Appendix 3.8 for further details) – if it is exercised. 3.1.26 Permanent Magnets, IF 027 ((Section deleted as there is no system interaction with the Fjernbane Infrastructure System.)) 3.1.27 Point Heating Control System, IF 028 The Point Heating Control System is monitored from the Fjernbane Infrastructure System. The field elements and transmission equipment necessary for this are a Customer Delivery. 3.1.28 Points, IF 029 The new Point machines, keylocks, derailers and point indicators that are part of the Fjernbane Infrastructure System must fit into the existing Points. There is no intention to replace points because of the fitment with new Point machines. 3.1.29 Possession Planning System, IF 030 The Possession planning system is used by the Customer to plan Possessions of specific track sections. The Possession planning system provides Possession information to the Fjernbane Infrastructure System so that Possessions can be invoked and revoked by the Signal Operator or the PICOP. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 17 of 98 3.1.30 Punctuality/Delay reporting system, IF 031 The Customer uses the so-called “Regularitets- og Driftsstatistiksystem” (RDS) to monitor delays and their causes, assign them to the responsible contractual party and ensure correct documentation and follow-up. This data will include trains runs history and reasons for delays. This system may either be modified or replaced. The Traffic Management System which is part of the Delivery provides data to the RDS or its successor. The Swedish equivalent of RDS, the so-called TTRAF, is currently only interfacing to the Danish RDS and not to the TMS. 3.1.31 RBC – Neighbouring Fjernbane Infrastructure, IF 032 The Signalling System that is in the scope of fitment of the Fjernbane Infrastructure East Contract interfaces with the Signalling System of the Fjernbane Infrastructure West Contract and vice-versa. The interface is situated between Middelfart and Snoghøj on the Lillebælt Bridge and involves an RBC-RBC interface. 3.1.32 RBC – Foreign Railway, IF 033 The Signalling System on lines that are in scope of fitment interfaces with the Signalling System of different foreign railway infrastructure managers. Currently, the scope only entails interface to Sweden (for the Fjernbane Infrastructure East contract) that will contain an RBC-RBC interface, however the Fehmarn option entails a new RBC – Foreign Railway interface with Germany. 3.1.33 Road Signalling System, IF 034 If road traffic lights are present in the vicinity of a Level Crossing, the Level Crossing equipment that is part of the Fjernbane Infrastructure System has to interface to the road signalling system, so that both systems operate in a coordinated manner. 3.1.34 Road Vehicle Detection Systems, IF 035 ((Deleted, since Road Vehicle Detection Systems are part of the Fjernbane Infrastructure System delivery no external interfaces exists.)) 3.1.35 Sidings not in Stations, IF 036 The following Sidings interface with BDK lines between stations: Fjernbane Infrastructure East Contract: TIB 1 Between Stations Høje Taastrup – Roskilde Km 23,9, 24,9 Status Km 23,9 active* Km 24,9 closure anticipated *point released from the TMS and operated locally Fjernbane Infrastructure West Contract TIB 23 24 Between Stations Hørning – Århus Svenstrup – Randers Fjernbane Infrastructure East/West Document1 Km 98,7 166,7 BAFOTenderDocumentAppendix Version 4.0 Status Out of use Active* 3.5–Interface Requirements Page 18 of 98 25 30 31 31 32 Hjørring – Sindal Bredebro – Tønder Esbjerg – Guldager Esbjerg – Guldager Skive – Rønbjerg 299,3 61,7 57,6 60,4 70,4 Closure anticipated Closure anticipated Closure anticipated Closure anticipated Closure anticipated *point released from the TMS and operated locally 3.1.36 SCADA (SRO) Systems, IF 037 SCADA systems interact with the Delivery of the Fjernbane Infrastructure East contract at the Storebælt tunnel, the Øresund link and Sydhavnsgade Tunnel and if Fehmarn coastto-coast is exercised, with the Fehrmarn SCADA. The information provided from the SCADA systems to the Fjernbane Infrastructure System aims at preventing more trains from entering the tunnel due to causes like train stopped in the tunnel, vessel collision with bridge, high winds on bridge. The SCADA systems and the Fjernbane Infrastructure System also exchange data regardless of alarms. 3.1.37 Telephone Exchange/Switchboard, IF 038 The Customer will adapt his telephone system to the new conditions given by the new Signalling System and move the exchanges/switchboards into the new TCCs. The user interface of the telephone system is expected to be integrated into the TMS user interface. 3.1.38 Time Reference, IF 039 To allow for an accurate railway operation, the Fjernbane Infrastructure System needs to be synchronised to an accurate time source. It is expected that the Customer’s fixed transmission network provides this time synchronisation, thus ensuring that the railway operation in the whole of Denmark is based on the same time source. Supplier shall be able to make use of the customer provided Network Time Protocol (NTP) for time synchronisation. 3.1.39 Offline Production Plan, IF 040 The timetable planning system is used to generate long-term timetables. The Traffic Management System which is part of the Delivery downloads the long-term timetable as a working basis at regular intervals. During the migration phase and as long as the current TMSs are still in use, the Delivery must interface to the P-Base System. The PBase System is used to transfer Timetable information to the existing TMSs. 3.1.40 TMS_Existing Fjernbane, IF 041 Prior to commencing the act of migrating the Existing Fjernbane TMS functionality to the new TMS System, the Supplier shall have reached agreement with the Customer on the migration plan and methods. The following aspects are considered essential for the migration process: the conversion of data from the format used by an existing TMS to the format stipulated by the new TMS; the change of data source from the existing TMS to the new TMS. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 19 of 98 Further details can be found within the TMS Concept document [1]. 3.1.41 TMS_Foreign Railways, IF 042 The Traffic Management System which is part of the Delivery interfaces with the traffic management systems of different foreign infrastructure managers, to exchange all relevant operational data. The foreign infrastructure managers are the following: Fjernbane Infrastructure East Contract Trafikverket (Sweden) 3.1.42 Fjernbane Infrastructure West Contract DB Netze (Germany) TMS_Neighbouring Fjernbane Infrastructure, IF 043 The Traffic Management System which is part of the Fjernbane Infrastructure East Contract Delivery interfaces to the Traffic Management System of the Fjernbane Infrastructure West Contract and vice-versa. For Traffic Management the interaction between the deliveries is expected to be organised similar as if it was an adjacent TMS. Nevertheless it is required that A) Control Room Users in either Control Rooms can visualise the full information about the entire Fjernbane network B) External interfacing systems can receive the full information about the entire Fjernbane network irrespective of whether it is sourced in the East or the West contract area. As a consequence both TMS databases need to be synchronised on the full TMS data set. 3.1.43 TMS_Private Lines, IF 044 The Traffic Management System which is part of the Delivery interfaces with the different Traffic Management Systems of the Danish Private Railways, to exchange all relevant operational data. Some private railways have centralised their traffic management for several lines into one system. The tables below (East and West respectively), provide the currently available information but highlights those railway companies that are “OUT-OF-SCOPE” in orange. For all in-scope interfaces, the Supplier is required to prepare and ready their part of the Interface but no process is yet in place to oblige the other side of the interface (namely the Private Railways), to do the same. Therefore no testing or full (end-to-end) implementation of the interface is presently foreseen. TMS interfaces for the Fjernbane Infrastructure East Contract Railway Company Interface TMS Type and Stations to Description BDK Lokalbanen A/S Helsingør, Cactus TMS, electronic Snekkersten TMS with timetable based automated operation. Regionstog A/S Køge Operated by Lokalbanen A/S using the Cactus TMS. Regionstog A/S Holbæk, EB 80, electronic TMS Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 Interface to BDK as for today No data transfer, contact via telephone only No data transfer, contact via telephone only No data transfer, 3.5–Interface Requirements Page 20 of 98 Slagelse, Tølløse Regionstog A/S Nykøbing Falster Vest without automated operation. Some automation at interlocking level. EbiScreen 2000, electronic TMS with timetable based automated operation. contact via telephone only No data transfer, contact via telephone only TMS interfaces for the Fjernbane Infrastructure West Contract Railway Company Interface TMS Type and Stations to Description BDK Nordjyske Frederikshavn EbiScreen 2000, Jernbaner A/S electronic TMS without automated operation. Some automation at interlocking level. Midtjyske Jernbaner Vemb RMS 2000, electronic A/S TMS without automated operation. Some automation at interlocking level. Midtjyske Jernbaner Århus VICOS, electronic TMS A/S with simple automation based on time and track circuit operation. Vestbanen A/S Varde RMS 2000, electronic (operated by TMS without any Arriva) automation. 3.1.44 Interface to BDK as for today No data transfer, contact via telephone only No data transfer, contact via telephone only Operated by BDK from the Århus TCC No data transfer, contact via telephone only TCC Building Control System, IF 045 The Customer provides main TCC buildings in Copenhagen and Fredericia as well as satellite TCC buildings in Århus and Aalborg. The customer provides server rooms in raw building condition, control rooms in finished building condition, as well as overall power supply and HVAC. It is up to the Supplier to build up the power supply and local HVAC for the Delivery in the server room. 3.1.45 Train Operating Companies’ Management Systems, IF 046 The TOCs’ management systems contain data that is relevant for planning, train operation and ressource management and they exchange data with the Traffic Management System that is part of the Fjernbane Infrastructure System. Both the railway infrastructure manager and the Train Operating Companies must have accurate train data available at all times to perform their business. DSB is currently operating rolling stock management and staff management systems. To support this DSB has a time table datawarehouse containing a copy of the actual timetable based on updates from the P-base system of Banedanmark. Furthermore DSB operates a train positioning system using GPS to track the position of all trains and report this to its own system and the train status system of Banedanmark. In addition DSB operates traffic information system to inform passengers and staff.. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 21 of 98 3.1.46 Unfitted and closed Lines, IF 047 The Signalling System on lines that are in scope of fitment interfaces with a number of freight lines, heritage lines and closed lines (so-called “restbaner”). The interfaces are situated at the following locations: Fjernbane Infrastructure East Contract Næstved (restbane) Ringe (restbane) Slagelse (restbane) Tommerup (restbane) Fjernbane Infrastructure West Contract Ålborg (heritage railway) Bramming (BDK freight line, closure anticipated) Fårup (heritage railway) Rødekro (restbane) Tinglev (restbane) Tønder (restbane) Vojens (restbane) These lines are not equipped with any Signalling- or Train Protection System. In the case of Ålborg, the interfacing point is operated from the TMS, whereas in Fårup the interfacing point is operated locally after being released from the TMS. In all other cases, the interfacing point is clamped. Further information can be found in the site information given in Appendix 2 [3]. 3.1.47 UT Circular System, IF 048 Unusual Transport (UT) Circular is a permission for a wagon that is outside the standard envelope (weight, size/gauge, type, loading) to be transported in a train. The UT circular is identified by a unique 7 digit number, and contains all restrictions to be adhered to for the journey. UT Circulars are issued by the Infrastructure Manager following a request from the Train Operating Company (TOC) concerned. Information on Trains carrying UTs is distributed to Drivers, Signal Operators and other relevant staff by referencing a Train Running Number to the unique 7 digit number identifying the applicable UT circular. 3.1.48 Failurement Management Tool, IF060 Failure management system used for dispatching of personnel and spare parts. Currently this interface is manual, however in the future the TMS of the Fjernbane Infrastructure System shall be able to interface this system. Therefore the TMS shall be prepared for such an interface, that for instance will enable the Failure Management Team to report to TMS estimates on time to repair. 3.1.49 SAP PM, IF061 SAP PM, the asset management system of the customer, must be updated with information regarding infrastructure usage and failure occurremces. 3.1.50 Train Status, IF 101 The Train Status system collects data about running trains from the TMS, TOCs GPSbased systems and in some cases manual data entry, calculates the “official truth” about position and delays and distributes this data to passenger information system, RDS and TOCs’ systems. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 22 of 98 3.2 Users For a comprehensive description of how System users are employed within specific roles and how roles are allocated for operational activities, please refer to the Traffic Management System Concept [1] – provided as attachment {3} to Appendix 3.2 and to the Operational Concept [2] provided as attachment {1} to Appendix 3.2. ((Description of Interfacing Roles removed to avoid repetition of information provided elsewhere)) Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 23 of 98 4 Interface Requirements A System is built to provide tangible benefits to its users and to operate successfully within a specific context over its lifetime. To satisfy this high level goal, many interfaces facilitating the timely flow of information are required. The flow of information may be required internally to the system and / or out of the system and exchanged with another system or user. Information flow across and between interfaces is used to coordinate and control how and when the system offers the functionality it is designed for. Such flows may be stimulated or triggered either from a functional state of the system or a condition being met in the environmental context of the system that depends on evaluating a non-functional characteristic of the system. In either case, there is an intimate correlation between Interface Requirements and Functional Requirements. There is also a close correlation between non-functional conditions (e.g. rise in ambient temperature), leading to a stimulus for the System across an interface and thereby actuating a system function (e.g. activate cooling and ventilation unit). The same may also apply for functionality that is triggered or terminated by a User interacting with the System through a User Interface. Because of this, interface Requirements can be analysed from the point of view of triggering and destination entities making up the interface and furthermore the interface Requirement can be linked to functions that initiate or respond to the information flow across the interface. The level of detail associated with an interface increases with the depth of abstraction of the System. This appendix focuses on the interfaces visible at the System level. Referring to the figure below, depicting the system as a “grey box” – the corresponding level of focus is represented by the green lines. A B C Figure 2 The System depicted as a “Grey Box” with visible Subsystems and Products. At the system level, there may not be the full range of detail (pending detailed design) readily available for an interface, however all information currently available regarding the interfaces to external systems has been taken into account and forms the basis for the requirements specified in the Interface Definitions. The interface definitions for the Fjernbane Infrastructure System are collected in section 4.3 below, and corresponds to the Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 24 of 98 external system interfaces shown in green in Figure 2. Please note that all requirements stated in the Interface Definitions are minimum requirements. The details used to define and develop the interface are, from the customer’s perspective, constraints on how that interface has been or will be designed. This situation applies to subsystem interfaces (Shown in Red in the figure above), as well as product level interfaces within specific subsystems. These are displayed in Black within subsystem B in the figure above. Regarding interfaces, the right level of detail on the data content, structure, format etc, will be settled in the Design Phase. The design phase may also reveal that specific interfaces shall be synchronous instead of asynchronous or vice versa. It can also confirm if the required protocol is the best one to use. The requirements and information in the following sections provide the best possible input to the design and setup of the data model and data exchange protocols. Each Interface definition has been given an identification number and a title for easy reference. The identification number is unique preceeded by FbIS.I. (e.g. FbIS.I.429). The requirements and information on each interface definition are represented within the Interface Identification Tables (See section 4.3) and are all specified as minimum requirements. The Interface Identification Tables are complimented by an ‘Interface Overview Diagram’ (See section 4.1 below). The Interface Overview Diagram captures graphically the details of the Fjernbane Infrastructure System interfaces with external systems. In this way, the Interface Overview Diagram builds further on the System Context Diagram presented in Section 3.1 above. Like for the Functional and Non-Functional Requirements sets, interface Requirements for the Fjernbane Infrastructure System also carry a specific naming convention and are identified as FbIS.IR. Interface Requirements are also written to satisfy the ‘SMART’ acronym. Therefore Interface Requirements are set out to be: Specific, Measurable, Achievable, Realistic and Testable Because of their nature, Interface Definitions and therefore Interface Requirements, will evolve in detail to match the design steps and overall progress of delivering the System. Therefore at this stage, the Customer intends that the Requirement set within this appendix, clearly demonstrates the scope and potential complexity the interfacing effort will cover. Furthermore, the Customer intends to work with the Suppliers and 3rd parties by means of a joint design mechanism, to support the successful integration of all required interfaces to the System. Readers are also instructed to make full use of the following attachments to this appendix – provided for additional clarity on issues specific to the Customer’s environment. The attachments deal with: Transition zones to the S-bane – Attachment {1}. Fjernbane Transition Zones – Attachment {2}. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 25 of 98 4.1 Interfaces to Legacy Interlockings – Attachment {3}. Interface between Denmark and Sweden – Attachment{4}. Interface Overview Diagram Compared to the System Context Diagram (Figure 1) the Interface Overview Diagram (Figure 4) only includes external systems that exchange data electronically with the Fjernbane Infrastructure System or external systems that hold programs that must be executable within the Fjernbane Infrastructure System. The latter relates to back-office software (refer to section 3.1.7). Therefore a system like ‘Fixed Transmission Network’ is not part of the Interface Overview Diagram, since no data is exchanged with this system. Note that the Fixed Transmission Network is only used to transport data, no information is exchanged between the Fjernbane Infrastructure System and the Fixed Transmission Network itself. Notice that the external system CCTV is included in the Interface Overview Diagram, though it doesn’t exchange data with the Fjernbane Infrastructure System. The reason for including CCTV in the diagram is that it provides data (motion picture) from the surveillance cameras that must be presented within the Fjernbane Infrastructure System. By naming the interface as well as capturing the identification number of the applicable Interface Definition, the Interface Overview Diagram below, provides further clarity on the System interfaces. Please note that all numbers stated on the Interface Overview Diagram refer to the Interface Definition Identity, i.e. of the type FbIS.I.nnn, where nnn is the stated number. In addition, the Diagram also provides more specific details compared to the System Context Diagram (Figure 1) regarding the external interfaces. As depicted in the Interface Overview Diagram (Figure 4) an Enterprise Service Bus will be available for the Fjernbane Infrastructure System to interface to selected systems. The diagram indicates to which systems the Fjernbane Infrastructure System shall interface directly and which systems shall be interfaced via the depicted Enterprise Service Bus (ESB), however this partitioning is subject to verification of characteristics of the external systems in the joint design phase. The Diagram is organised such that to the right, the reader will find the Train Operating Company’s (TOCs) type of systems, which are interfacing the Fjernbane Infrastructure System via the depicted Enterprise Service Bus (ESB). To the left in the diagram are the systems (e.g. foreign and neighbouring interlocking systems) that the Fjernbane Infrastructure System is to interface directly. The arrows flowing between the System and external entities represent identified interfaces. An arrow indicates which way the data flows and can include one or more “messages” in that direction, where the term message is used for a given FbIS.I.nnn. The “messages” as explained above are the basis of Interface Definitions and are referenced by title and ID (the “FbIS.I.” part of the ID is dropped for reasons of space). Note that FbIS.I.27, FbIS.I.37 and FbIS.I.254 are of the type request/response, however in Figure 4 only an arrow in one direction is shown due to limited space. This means that for these 3 messages only the arrow for “flow of response” is depicted. Details for the Interface Definitions can be found in the Interface Identification Tables in section 4.3. These details are to be verified, completed, adapted if required, and finalised in the Design Phase. Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 26 of 98 ((Figure 4 has been updated for consistency with the changes implemented in document.)) Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 27 of 98 RBC Neighbouring Fjernbane Infrastructure Receive train (475) Handover train (476) Interlocking Private lines Handover train (276,279) Receive train (278,429) Handover train (276,279) Fai lu Mi l r e Ma e st que one nagem e Co Re st Fa nfir nt Pla que ilur ma st u e M tion n (63 pda ana ( 63 6 ) te o gem 7) e n nt P TC mi l e st lan C o ( Bu ne (63 638) ild 9) ing ro om dia gn os tic s( 43 0) Re Accident Information (614) Train Positions (174) Stop trains (590) Catenary Status (176) Revoke catenary shut off (237) Operations Monitoring Systems Guard Device TOC Systems Failure Management Tool 2) Planned possessions (99) Planned Cat. Shutoff (173) Driver Guidance Tool 2 (6 Point heating monitoring (442) Traffic Information System o Mapping of signalman to area (43) de Train positions (589) Changes to Online Production Plan (630) vi Stop/resume trains (230) SCADA Alarms (629) Cat. Mgmt. Operator(628) e Catenary Management System nc Possession Planning System illa Point Heating Control System ve Telephone Exchange/ Switchboard Dispatching System Staff 6) SCADA(SRO) Systems Dispatching System Rolling Stock r Su Customer Backoffice Systems Online timetable (44 Time Reference Sund & Bælt Hot Axel Box and Derailment Detector Planning systems tes Time synchronisation (264) ircula Coordinate railway and road signalling (456) a ) pd ( 20 lan u ta da n p lity ctio tua du n c e p ro Pu n i l On 7) r (22 Bridge release (241) Point positions (351) Stop Stop due to h o due to de t axle (46 railm 9 ent ( ) Office 470) applic ation user in p u t (6 Office 16) applica tion HM informa I tion (61 7) Enterprise Service Bus (ESB) UT c Road Signalling System Train data from TOC (192) Change Online Production Plan (492) Reject/Accept offered changes (624) Driver (499) Driver Feedback (611) Guard Feedback (640) Vehicle and staff roster (646) Handover train (276,279) Receive train (278,429) Bridge position (606) Bascule Bridge Te L o l e g ra Pr g Ou mjou o Ex duc tput rnale po tion (27 rt o ) n Ou tpu f P Plan lay t (2 e b a xp o 54 ck rt ( ) Se 38 ss ) ion In ( 62 In fras 7) fra tr st u ct ru u ct r e ur u e sa fa ge ilu re (64 (6 4) 45 ) * Fjernbane Infrastructure System (FbIS) Receive train (278,429) Emergency Services (Alarmcentralen 112) User Authentication (517) Online Production Plan (45) * Offer Changes to Online Production Plan or Service Intention (623) Confirm Changes (625) Impose Changes (626) Predicted Delays (46) * Train positions (80) * Infrastructure status (87) Report booking status (405) Planned Temp. Speed Restriction (482) Temp & Emerg. Speed (483) * Planned Temp. Possess. (484) Possessions (485) * Low adhesion (486) * Catenaries (487) * Cancel Online Production Plan (493) * New trains (494) * Changing stopping patterns (495) * Production Plan information (497) Arrivals/departures (503) * Train route (504) * Handover train (276,279) Receive train (278,429) Interlocking Existing Fjernbane SAP PM TOC Systems Enterprise Service Bus (ESB) Handover train (276,279) Receive train (278,429) Interlocking Foreign Railway File System Train Status Interlocking Neighbouring Fjernbane Infrastructure Interlocking S-bane (existing and new) Identity Management System Update train path (577) Delete train path (578) Arrival (579) Departure (580) Delay (581) Platform changes (631) New committed conn. (632) Current Train Position (633) Online Production Plan (634) Production Plan import (37) Receive train (475) Handover train (476) Passenger Information System Offline Production Plan Train Traffic on Non migrated tracks (444) ad ( 477 ) K (4 78) Train Traffic on Migrated tracks (445) in D Private Line Status (157) Receive train (599) a b ro Railway status (158) Handover train (598) ins TMS Existing fjernbane TMS private lines Receive train from Sweden (465) Receive train from Germany (467) ins Handover train to Sweden (464) Handover train to Germany (466) n tra Routing of voice calls to Control Room users (436) Routing of voice calls to train (437) Area group calls (438) h tra ERTMS radio message (159) re i g ERTMS balise message (261) ERTMS radio message (32) KMAC Key (582) of fo anis SMS in (440) for d SMS out (439) Key s KMC data for countrywide synchronization (619) RBC Foreign Railway Key s KMC data for countrywide synchronization (620) Foreign Key Management Centre TMS Foreign Railway GSM-R Received Online Production Plan (383) Received Railway status (201) Received Train position and delay (508) Neighbouring Key Management Centre TMS Neighbouring Fjernbane Infrastructure Send Online Production Plan (68) Send Railway status (202) Send Train positions and delay (509) ERTMS Fitted Train (Level 0, 2-DK, 2, STM) UT circular System Punctuality/Delay Reporting System CCTV TCC Building control system Figure 4. The System’s Interface Overview Diagram Fjernbane Infrastructure East/West Document1 BAFOTenderDocumentAppendix Version 4.0 3.5–Interface Requirements Page 28 of 98 4.2 Integration Architecture and Response Times ((The changes in this section are so substantial that the Customer has chosen not to show the change markings)) In aiming for a robust integration architecture with centralized governance and operation of interfaces the Enterprise Service Bus (ESB) has been chosen as the integration pattern to use where appropriate within the Signalling Programme. Using an ESB ensures that the different systems to interact are decoupled via the ESB, which implies that changes to one system will have a minimum impact on the rest of the system. The ESB also facilitates the task of integrating the Fjernbane Infrastructure System to the many external systems, since the integraton task is then reduced to use the set of proposed integration types in stead of having to integrate to each of the different external systems directly. The external systems that the Fjernbane Infrastructure System is to integrate to have all been assessed in regards to whether an integration to the Fjernbane Infrastructure System is best done via the ESB or using point-to-point integration. Due to safety and time critical issues a large number of systems must be integrated to the Fjernbane Infrastructure System using a traditional point-to-point integration pattern. The introduction of an ESB significantly reduces the range of protocols to be used and the systems to be interfaced directly. 4.2.1 Communication and integration types The way that the Fjernbane Infrastructure System communicates with external systems is divided into the following 3 types of communication: Push Data is broadcast from the Fjernbane Infrastructure System to the receiving system. Pull One system requests information from another system. The request (pull) can originate both at the Fjernbane Infrastructure System or at an external system. Data flows are bidirectional: request and response. FbIS.I.37 is an example of the Fjernbane Infrastructure System pulling information from an external system. Receiving a push Data is broadcast to the Fjernbane Infrastructure System from an external system, i.e. the Fjernbane Infrastructure System “receives a push”. Table 1 Communication types Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 29 of 98 Figure 5 below shows for each of the data flows from the System’s Interface Overview Diagram, whether it is Push, Pull or Receiving a push. The drawing also shows whether data is exchanged via the Enterprise Service Bus or directly between the Fjernbane Infrastructure System and the external system. The external systems are in this figure divided into either BDK owned systems or Non-BDK owned systems. Performance responsible V Y X Y Non-BDK system 159 276 279 32 261 278 429 456 469 470 475 478 BDK systems 476 477 582 614 Fjernbane Infrastructure System (FbIS) 201 264 276 279 383 20 38 43 45 46 80 87 158 174 405 430 436 437 438 445 446 464 37 27 254 466 482 483 484 485 486 487 493 494 495 497 503 504 577 578 579 580 440 475 508 606 620 581 589 598 616 623 625 626 627 630 631 632 633 634 638 639 644 645 Z 429 439 476 509 619 37 467 38 492 99 499 157 517 158 590 173 599 176 611 192 617 227 622 230 624 237 628 440 629 442 636 444 637 445 640 465 646 Interface point Interface point Interface point 68 202 241 278 351 Seen from the FbIS point of view Push Pull (Request response) Receiving a push X Y Z FbIS processing time V External system processing time Network time ESB transaction time The shown numbers refers to the IDs on the Interface Overview Diagram F-bane ESB Y V Non-BDK systems BDK systems Figure 5 Types of communication applied for each Interface Definiction (FbIS.I.nnn) Please note that interface definitions FbIS.I.276, FbIS.I.278, FbIS.I.279, FbIS.I.429, FbIS.I.475 and FbIS.I.476 are shown twice in Figure 5, since these messages are exchanged both with BDK systems and non-BDK systems. For communication taking place via the ESB the following set of integration types are deemed adequate, and for each interface going via the ESB, an integration type is indicated in the Interface Definition table (Refer to section 4.3). The use of open standards and protocols is preferred therefore the integration types listed below are based on SOAP or SOAP MTOM. However if performance tests show that performance for any specific interfaces cannot be met due to the use of the SOAP protocol the Customer will consider to allow the use binary message formats. Interfaces that the Customer acknowledges may be critical with regards to performance requirements are marked with ‘RMI’ in the Interface Definition tables in section 4.3. Name Fjernbane Infrastructure East/West Document1 Standard BAFO Tender Document Version 4.0 Explanation Appendix 3.5 – Interface Requirements Page 30 of 98 Push-O2O-GD HTTP bound SOAP Web Services with Reliable Messaging (WS-RM) Push-PS-GD Message-oriented Middleware bound SOAP Web Services (WS) Stream-O2O-GD Message-oriented Middleware (MOM) bound SOAP WS with TCP KeepAlive Stream-PS-GD Message-oriented Middleware (MoM) bound SOAP WS Pull-NB HTTP bound SOAP WS (two sockets) RMI Open, widely adopted and recognised binary message formats/protocols. Push, One-to-One, Guaranteed Delivery. The messages are pushed from the sender to one receiver with guaranteed delivery. Push, Publish/Subscribe, Guaranteed Delivery. The messages are pushed from the sender and are intended for multiple receivers. This is done using publish/subscribe messaging. Streaming One-to-One connection with Guaranteed Delivery. The messages are pushed from the sender to one receiver, where transport channel is kept open due to high usage. In other words the communication channel is used so often that the time to close down and established the connection again will be too long compared to the time between messages sent. Streaming, Publish/Subscribe, Guaranteed Delivery. The messages are pushed from the sender and are intended for multiple receivers. The transport channel is kept open due to high usage. Pull Non-blocking. The message is a requests and the requester expects a response from the producer. Non-blocking meaning that the requester is able to continue with other matters while waiting for a response, i.e. asynchronous. In situations where an open, widely adopted and recognised binary message protol already exists, an exception can be made from the SOAP protocol. This could for example be video streaming, voice streaming, etc. Table 2 Integration types Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 31 of 98 Messages send via the ESB intended for multiple receivers shall use Publish/Subscribe, ie. the integration type Push-PS-GD or Stream-PS-GD. However it shall be emphasised that the Fjernbane Infrastructure System shall only deliver such a message to the ESB, and the ESB is then responsible for transferring the message to the multiple receivers. Note that One-to-One (O2O) stated in Tabel 2 is communication between two entities via the ESB, as oppossed to Publish/Subscribe which is used for communication between multiple entities via the ESB. The use of stream is advantageous when data is exchanged frequently and the communication channel is used so often that the time to close down and established the connection again will be too long compared to the time between messages sent. 4.2.2 Estimated response times In order to estimate the required response times, data that flows via the Enterprise Service Bus (ESB) has been evaluated against the decision tree in Figure 6. Accordingly each interface FbIS.I.nnn listed in the Interface Definition table (Section 4.3) that goes via the ESB has been given a response time requirement in the last column (named Perf: ) of the table. Note that selected non-ESB interfaces have also had their performance estimated in the Interface Definition table. The specifed performance requirements are to be interpreted as follows. As exemplified below, a letter in the performance column indicates the message size as well as the frequency, i.e. the expected number of messages transferred per second on that interface. The first digit specifies the overall performance requirement, i.e. the maximum time in seconds allowed from an event occurs to the receivers of the associated information are informed. The digit in square brackets indicates the maximum number of seconds that the Fjernbane Infrastructure System is allowed to use of the overall performance requirement. For instance a performance requirement B5[4] indicates that the overall performance requirement is 5 seconds and that the Fjernbane Infrastructure System is allocated 4 seconds. The letter B indicates that the message frequency is estimated to more than 3 messages per second and the message size is less than or equal to 10 kb. B5[4] X+Y+Z X X Y Z FbIS processing time Network time ESB transaction time Relating the performance requirement B5[4] to Figure 5, then ‘X’ the processing time for the Fjernbane Infrastructure System corresponds to 4 seconds and the sum of X, Y and Z corresponds to the response time of 5 seconds, where Y and Z denotes the network time and ESB transaction time respectively. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 32 of 98 Note that selected non-ESB interfaces have also had their performance estimated in the Interface Definition table by stating the required response times in seconds corresponding to X+Y in Figure 5 – therefore only one digit is indicated for non-ESB interfaces. No requirements are stated towards the processing time of the interfaced systems (In figure 5 depicted as V). In the decision tree below note that for A1, A2 and F2 the response times indicated are for 99,9% of the messages exchanged, i.e. these interfaces are crucial to maintain a true picture of the state of the railway. In order to verify the performance of an interface classified as A1, A2 or F1 a test must include at least 10.000 messages. Figure 6 Decision tree for estimating response times For a push operation the response time within the square brackets indicates the number of seconds allowed from the triggering event occuring within the Fjernbane Infrastructure System to the moment, when information regarding the event is ready to be announced to the outside world. An example of this is FbIS.I.493, where the Fjernbane Infrastructure System must inform of a cancellation of Online Production Plan, which has a performance requirement of H2[1.5]. This means that the Fjernbane Infrastructure System has 1.5 seconds from the moment it becomes aware of the need to cancel the online Production Plan to the moment in time when a message is ready to pushed out to potential receivers. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 33 of 98 For a request response operation, i.e. a scenario where an external system pulls the Fjernbane Infrastructure System for information, the response time indicated is the number of seconds that the Fjernbane Infrastructure System have from the moment it receives the request till a response shall be available at the interface point. An example of this is FbIS.I.27, where an application belonging to the File system pulls the Fjernbane Infrastructure System, which has a performance requirement of E300[250]. This means that the Fjernbane Infrastructure System must be able to deliver a full response within 250 seconds out of the total performance requirement of 300 seconds. For the operation called ‘receiving a push’ the time indicated is the number of seconds from the information is available to the Fjernbane Infrastructure System till the Fjernbane Infrastructure System has reacted upon the information. An example of this is FbIS.I.176, which has a performance requirement of D5[4]. This means that the Fjernbane Infrastructure System has 4 seconds from when the Catenary Management System makes the information available to the Fjernbane Infrastructure System until the Fjernbane Infrastructure System has registered the status information it received. 4.3 Interface Definitions The requirements regarding the exchange of data between the Fjernbane Infratructure System and the external systems it interacts with are defined in the Interface Definitions in this section. The Interface Definitions are minimum requirements. The following table represents the Fjernbane Infrastructure Interface Definitions with regards to external Systems. The table is organized into 16 columns with each column serving the following purpose: ID: Identification of interface – the number is helpful in cross referencing to the Interface Overview Diagram. Title: The title of the interface From: The system from which the information flows To: The system to which the information flows Content: The information flowing on the interface at a logical and overall level Context diagram reference: Reference number to the Context Diagram entity in section 3.1 above Purpose: The purpose of the interface (in one sentence) Interface type: Public (defined by international standards), BDK owned (BDK have the rights to use the interface for other suppliers), Prop. (Proprietary to the supplier). See also Appendix 16 for further details on Interface types. Design constraint: Non functional Requirements to the design of the interface Internal Requirements: Reference to associated System functional requirements Triggering function: The function which initiates the interface Consequence function: The function which is initiated as a consequence of the interface in the accepting system Supplementary info: Additional information to the Supplier Impl: Implementation scope for the Supplier (end to end or end to interface (in case a third party is expected to implement the other part of the interface as is the case with interface via ESB)). Test: Test scope for the Supplier (typically end to end) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 34 of 98 Perf: Indicating Performance criteria. The response time in seconds for the Supplier’s implementation responsibility. Please refer to section 4.2.2 to understand the requirement annotation used in the Perf. column. Also note that the performance requirement is a major requirement just as much as the “Minimum Content” of the interface. Further terms used in describing the Interface Definitions are defined below to further aid understanding: Real time: The interface is activated as a consequence of changed data in real time (i.e. event based). Point to point: Implementation is a direct point to point implementation between two systems. Streaming: Data is flowing as a stream due to high usage or heavy load. GSM-R in the context of the interface diagram and interface definition: GSM-R network and dispatcher system. RS: Rolling Stock ((These Interfaces have been removed since the First Negotiation version of this document: - Fixed Transmission network - Key Lock and Similar Equipment)) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 35 of 98 4.3.1 Interlocking Existing Fjernbane, Foreign Railway, Neighbouring Fjernbane Infrastructure, Private lines, S-bane ID Title From To Minimum Content FbIS.I.429 Permit Entry into Fjernbane Infrastructure Fjernbane Infrastructure System (IL) - Interlocking Neighbouring Fjernbane Infrastructure - Interlocking Foreign Railway - Interlocking Private lines - Interlocking S-bane Entry point Route MA FbIS.I.278 Route Status Fjernbane Infrastructure System (IL) Interlocking Neighbouring Fjernbane Infrastructure. Interlocking Existing Fjernbane. Interlocking Foreign Railway. Interlocking Private lines. Interlocking S-bane. Route Locked|Unlocked Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF019 IF020 IF021 IF022 IF023 Purpose Interface Type To facilitate smooth transfer of trains across the border BDK owned IF019 IF020 IF021 IF022 IF023 To facilitate smooth transfer of trains across the border BDK owned Design Constrai nt Real time, Point-topoint Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.1786 Part of Receiving/handover a train into the Fjernbane infrastructure Part of Receiving/han dover a train into the Fjernbane infrastructure End to end End to end 1 Real time, Point-topoint FbIS.F.1249 Part of Receiving/handover a train into/from the Fjernbane infrastructure Part of Receiving/han dover a train into/from the Fjernbane infrastructure I.276, I.277, I. 278, I.279 and I.429 are used to transfer or receive trains across an IL border Private lines: LBtypes: E80 Existing Fjernbane: Station IL-types: E80, 1972, 1912/1946, 1953/1954, 1964, 1990. LB-types: 1954, 1960, 1977, 1991, 1951, 1994 S-bane: Existing system: station IL-types: 1969. New system: CBTC Foreign railway: Padborg to DB (Alcatel MC L84 N ,DB line block) I.276, I.277, I. 278, I.279 and I.429 are used to transfer or receive trains across an IL border Private lines: LBtypes: E80 Existing Fjernbane: Station IL-types: E80, 1972, 1912/1946, 1953/1954, 1964, 1990. LB-types: End to end End to end 1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 36 of 98 FbIS.I.279 Permit Entry To Adjacent Area Interlocking Neighbouring Fjernbane Infrastructure. Interlocking Existing Fjernbane. Interlocking Foreign Railway. Interlocking Private lines. Interlocking S-bane. Fjernbane Infrastructure System (IL) MA permission IF019 IF020 IF021 IF022 IF023 To facilitate smooth transfer of trains across the border BDK owned Real time, Point-topoint FbIS.F.1250 FbIS.F.1251 Part of Receiving/handover a train from the Fjernbane infrastructure Part of Receiving/han dover a train from the Fjernbane infrastructure FbIS.I.276 Route Can Be Locked Interlocking Neighbouring Fjernbane Infrastructure. Interlocking Existing Fjernbane. Interlocking Foreign Fjernbane Infrastructure System (IL) Route IF019 IF020 IF021 IF022 IF023 To facilitate smooth transfer of trains across the border BDK owned Real time, Point-topoint FbIS.F.1248 Part of Receiving/handover a train from the Fjernbane infrastructure Part of Receiving/han dover a train from the Fjernbane infrastructure Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 1954, 1960, 1977, 1991, 1951, 1994 S-bane:Existing system: station IL-types: 1969. New system: CBTC Foreign railway: Padborg to DB (Alcatel MC L84 N ,DB line block) I.276, I.277, I. 278, I.279 and I.429 are used to transfer or receive trains across an IL border Private lines: LBtypes: E80 Existing Fjernbane: Station IL-types: E80, 1972, 1912/1946, 1953/1954, 1964, 1990. LB-types: 1954, 1960, 1977, 1991, 1951, 1994 S-bane:Existing system: station IL-types: 1969. New system: CBTC Foreign railway: Padborg to DB (Alcatel MC L84 N ,DB line block) I.276, I.277, I. 278, I.279 and I.429 are used to transfer or receive trains across an IL border Private lines: LBtypes: E80 Existing End to end End to end 1 End to end End to end 1 Appendix 3.5 – Interface Requirements Page 37 of 98 Railway. Interlocking Private lines. Interlocking S-bane. 4.3.2 Fjernbane: Station IL-types: E80, 1972, 1912/1946, 1953/1954, 1964, 1990. LB-types: 1954, 1960, 1977, 1991, 1951, 1994 S-bane:Existing system: station IL-types: 1969. New system: CBTC Foreign railway: Padborg to DB (Alcatel MC L84 N ,DB line block) RBC Foreign Railway and RBC Neighbouring Fjernbane Infrastructure ID Title From To Minimum Content FbIS.I.476 Handover train Fjernbane Infrastructure System (RBC) RBC Foreign railway RBC Neighbouring Fjernbane infrastructure ERTMS data FbIS.I.475 Receive train RBC Foreign railway RBC Neighbouring Fjernbane Fjernbane Infrastructure System (RBC) ERTMS data Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF032 IF033 Purpose Interface Type Handove r of train Public IF032 IF033 Receive train Public Design Constrai nt ERTMS level 2, baseline 3 standards + Circuit switched and GPRS/E DGE+wi th and without authentic ation (KMC). Point-toPoint. ERTMS level 2, baseline 3 standards BAFO Tender Document Version 4.0 Internal Reqs Triggering Function Consequence Function ERTMS function ERTMS function Supplementary Info Impl. Test Perf. ERTMS function End to end End to end Accor ding to std. ERTMS function End to end End to end Accor ding to std. Appendix 3.5 – Interface Requirements Page 38 of 98 infrastructure 4.3.3 + Circuit switched and GPRS/E DGE+wi th and without authentic ation (KMC). Point-toPoint. Bascule Bridge ID Title From To Minimum Content FbIS.I.241 Bridge Release Fjernbane Infrastructure System (IL) Bascule Bridge Released/Not released FbIS.I.351 Point Positions Fjernbane Infrastructure System (IL) Bascule Bridge Point ID, Position IF001 FbIS.I.606 Bridge Position Bascule Bridge Fjernbane Infrastructure System (IL) Normal, Not Normal IF001 Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF001 Purpose Interface Type Design Constrai nt Real time, Point-topoint Internal Reqs Triggering Function Consequence Function To inform the bridge about the locking status of the tracks across the bridge To inform bridge if it can move. To detect the position of the bridge. BDK owned FbIS.F.441 FbIS.F.442 Control Room User requests release. BDK owned Real time, Point-topoint FbIS.F.1196 BDK owned Real time, Point-topoint FbIS.F.442 BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. The bridge is updated by the status End to end End to end 1 State Change Record Point Position End to end End to end 1 Status Change Record Bridge Position End to end End to end 1 Appendix 3.5 – Interface Requirements Page 39 of 98 4.3.4 Catenary Management System ID Title From To Minimum Content FbIS.I.174 Catenary Powered Train Positions Fjernbane Infrastructure System (TMS) Catenary Management System Train number, position (related to catenary sections) FbIS.I.176 Catenary Status Catenary Management System Fjernbane Infrastructure System (TMS) FbIS.I.237 Revoke Catenary Shut Off Catenary Management System Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF002 Purpose Interface Type Enable the catenary planner to execute power shut offs BDK owned The ID and status of all catenary sections: Powered|Un-Powered IF002 BDK owned Catenary Shut-Off ID IF002 To reschedul e, as well as being able to see which tracks have overhead power, and which do not have it. Allowing Fjernban e Infrastru cture System to schedule train moveme nts into previousl y unpower ed BDK owned Design Constrai nt Real time, Push, PushO2O-GD IP protocol, IEC 60870 Real time, Receivin g a push, PushO2OGD, IP protocol, IEC 60870 Internal Reqs Triggering Function Consequence Function FbIS.F.302 Changes in train positions for catenary powered trains triggers transfer of information to the Catenary Management System. FbIS.F.77 FbIS.F.377 Real time, Receivin g a push, PushO2OGD, IP protocol, IEC 60870 FbIS.F.438 BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. Updated train position overview End to if End to end B5[4] Change of catenary status Reschedule End to end End to end D5[4] Shut Off Over The protection data is modified according to the associated shutoff End to end End to end C5[4] Planned Shut-off are received from off-line. Appendix 3.5 – Interface Requirements Page 40 of 98 FbIS.I.590 4.3.5 Stop Trains Catenary Management System Fjernbane Infrastructure System (TMS) Catenary Section ID IF002 Context Diagram Reference IF045 Title From To Minimum Content FbIS.I.430 TCC Building Room Diagnostics Fjernbane Infrastructure System TCC Building Control System Alarms, Status, Diagnostics ID Real time, Receivin g a push, PushO2OGD, IP protocol, IEC 60870 FbIS.F.304 Stop command Stop Trains in vicinity End to end End to end D5[4] Purpose Interface Type Internal Reqs Triggering Function Consequence Function To facilitate building manage ment. BDK Owned Design Constrai nt Real Time, Push, PushO2O-GD Supplementary Info Impl. Test Perf. FbIS.F.1789 Change of Status Report and Log Alarm Information from Fire detection systems, Automatic room fire extinguishing systems, Automatic gas detection systems etc, which are part of the Fjernbane Infrastructure System delivery, is to be propagated to Facility Management, i.e. the personnel managing the TCC building. End to if End to End D5[4] Design Constrai nt Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Train Operating Companies management systems (TOC MS), Train Status Title From Fjernbane Infrastructure East/West Document1 BDK owned TCC building ID 4.3.6 catenary To stop Trains from entering an unpower ed Catenary Section To Minimum Content Context Diagram Reference Purpose Interface Type BAFO Tender Document Version 4.0 Test Perf. Appendix 3.5 – Interface Requirements Page 41 of 98 ID Title From To Minimum Content FbIS.I.503 Arrivals/ departures Fjernbane Infrastructure System (TMS) Dispatch RS, Dispatch Staff, Traffic Information System, Operations Monitoring System, Driver guidance. Train status Train number, station, arr/dep, time of arrival/departure FbIS.I.611 Driver feedback Driver Guidance Tool Fjernbane Infrastructure System (TMS) Driver feedback: Train number, message number, message code number, free text. IF008 FbIS.I.640 Guard Feedback Guard Device Fjernbane Infrastructure System (TMS) Guard Feedback: Train number, message number, message code number, free text. IF008 FbIS.I.646 Vehicle and staff roster Dispatch RS, Dispatch Staff, Fjernbane Infrastructure System (TMS) Vehicle and staff roster constraints IF046 Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF008 IF046 IF101 Purpose Interface Type Design Constrai nt Real time, RMI Internal Reqs Triggering Function Consequence Function BDK "Train status" uses data from the signallin g system to measure arrival/de parture times and delay, and pass this informati on on to other systems. Enable driver to provide feedback e.g. reason for delay Enable guard to provide feedback e.g. reason for delay Enable reschedul ing to respect vehicle and staff roster constrain ts BDK owned FbIS.F.1913 When a train arrives or depart a station BDK owned Real time, Receivin g a push, RMI FbIS.F.1726 BDK owned Real time, Receivin g a push, RMI FbIS.F.1726 BDK owned Real time, Receivin g a push, RMI BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. Receiving system is updated End to if End to end H2[1.5] Driver wants to give feedback about divergences Feedback associated with divergence. End to if End to end H2[1.5] Guard wants to give feedback about divergences Feedback associated with divergence. End to if End to end H2[1.5] TOC changes constraints Constraints incorporated in the Online Production Plan End to if End to end I2[1.5] Related to MFUN.001 (Refer to secton 6.9, subclause 13) Appendix 3.5 – Interface Requirements Page 42 of 98 ID Title From To Minimum Content FbIS.I.493 Cancel online Production Plan Fjernbane Infrastructure System (TMS) Train number(s), date(s), route being cancelled - or partly cancelled FbIS.I.487 Catenaries Fjernbane Infrastructure System (TMS) FbIS.I.495 Changing stopping patterns Fjernbane Infrastructure System (TMS) FbIS.I.87 Infrastructure status Fjernbane Infrastructure System (TMS) TOC online timetable, Dispatch RS, Dispatch Staff, Traffic Information System, Operations Monitoring System, driver guidance. Train status TOC online timetable, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC online Production Plan, Dispatch RS, Dispatch Staff, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC online timetable Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF046 IF008 IF101 Purpose Interface Type Design Constrai nt Real time, Push. RMI Internal Reqs Triggering Function Consequence Function To cancel or partly cancel of one or more trains in the online Producti on Plan BDK owned FbIS.F.121 Cancellations in online Production Plan Track number, starting and end points of track section with-/without power IF008 IF046 IF101 For giving fleet managers an overview over possible traffic BDK owned Real time, Push, RMI FbIS.F.1912 Train numbers, dates(s), stations, Service intention IF008 IF046 IF101 Changin g the stopping pattern of one or more trains BDK owned Real time, Push, RMI Planned Temporary and Emergency Speed Restrictions (Location, Value, Reason, Start Time, End Time). IF046 To resynchr onise the ITsystems of TOC BDK owned Push, Push-PSGD BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. Allowing TOC to advice all its ITsystems consuming Online Production Plan data of the change End to if End to end H2[1.5] Change in catenary status Update infrastructure status End to if End to end I2[1.5] FbIS.F.121 Changed stopping patterns Allowing TOC to advice all its ITsystem consuming Online Production Plan data of the change End to if End to end H2[1.5] FbIS.F.196 FbIS.F.197 FbIS.F.198 FbIS.F.1912 Request from TOC Resync TOC IT system End to if End to end H30[27 ] Appendix 3.5 – Interface Requirements Page 43 of 98 ID Title From FbIS.I.486 Low adhesion Fjernbane Infrastructure System (TMS) FbIS.I.494 New trains Fjernbane Infrastructure System (TMS) FbIS.I.45 Online Production Plan Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 To TOC online Production Plan, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC online Production Plan, Dispatch RS, Dispatch Staff, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC systems, Train Status Minimum Content Active Temporary and Emergency Speed Restrictions (Location, Value, Reason, End Time). Planned Possessions (Location, Other data). Active Possessions (Location, Other data). Low Adhesion (Location). Current power status. Areas of low adhesion Context Diagram Reference Purpose Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. with the current status of the infrastruc ture IF008 IF046 IF101 For giving fleet managers an overview over possible traffic. BDK owned Real time, Push, RMI FbIS.F.198 Change in low adhesion status Update infrastructure status End to if End to end H2[1.5] Train number(s), date(s), train route IF008 IF046 IF101 New trains to the online time table BDK owned Real time, Push, RMI FbIS.F.121 New special trains in online Production Plan Allowing TOC to advice all its ITsystem consuming Online Production Plan data of the change End to if End to end H2[1.5] Online Production Plan and Changes, including Case Numbers and IF008 IF046 IF101 To keep the receiving systems BDK owned Real time, Push, RMI FbIS.F.121 Changes in the online production plan Online Production Plans in the receiving End to if End to end H2[1.5] BAFO Tender Document Version 4.0 An upload of the online production plan will initially require a bulk Appendix 3.5 – Interface Requirements Page 44 of 98 ID Title From To Minimum Content Context Diagram Reference optimum train path. FbIS.I.623 Offer Changes to Online Production Plan or Service Intention Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 TOC systems An offer to change online production plan or Service Intention. The offered changes to the online production plan/Service Intention. Transaction number. IF046 Purpose updated. The dataowne r shall filter out the relevant info/chan ges based on (subscrip tion condition ) TOC Id for each TOC to get relevant data Offering a change in the online productio n plan or Service Intention. Can either be as a result of occurred events or as a result of the request from TOC via the FbIS.I.49 2 Interface Type BDK owned Design Constrai nt Real time, Push, RMI BAFO Tender Document Version 4.0 Internal Reqs FbIS.F.583 FbIS.F.1727 Triggering Function Occurred events or FbIS.I.492 Consequence Function Supplementary Info systems are updated transfer of data (estimated to performance J300[250]) whereas the realtime changes to the online production plan is estimated to performance requirement of H2[1.5] Offer transmitted to TOC Impl. Test Perf. End to if End to end H2[1.5] Appendix 3.5 – Interface Requirements Page 45 of 98 ID Title From To Minimum Content FbIS.I.624 Reject/Accept offered changes TOC Fjernbane Infrastructure System (TMS) Acceptance/Rejection of the offered changes. Transaction number. FbIS.I.625 Confirm Changes Fjernbane Infrastructure System (TMS) TOC Confirmation that accepted changes will be implemented. Transaction number IF046 FbIS.I.626 Impose Changes Fjernbane Infrastructure System (TMS) TOC Changes to the online production plan or Service Intention. Transaction number. IF046 FbIS.I.482 Planned Temporary Speed Restriction. Fjernbane Infrastructure System (TMS) TOC planning systems Track number, starting and end points, max velocity, validity period IF046 Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF046 Purpose Interface Type Design Constrai nt Real time, Receivin g a push, RMI Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. Enabling the TOC to accept or reject an offered change in Online Producti on Plan/Ser vice Intention s. Confirmi ng to the TOC that accepted changes will be impleme nted Impose temporar y online productio n plan or changes to Service Intention BDK owned FbIS.F.669 TOC acceptes or rejects offered changes FbIS is updated about decision from TOC. The TOC can accept or reject the offered changes. End to if End to end H2[1.5] BDK owned Real time, Push, RMI FbIS.F.669 Acceptance received (FbIS.I.624) Online Production Plan status changed to accepted. FbIS confirms to the TOC that the changes, they have accepted, will be implemented. End to if End to end H2[1.5] BDK owned Real time, Push, RMI TUSI lapsed. TOC updated. It can be necessary to enforce changes without the acceptance of the TOC. Related to Interface Definition FbIS.I.1727 End to if End to end H2[1.5] Enabling TOC time table planner system to reschedul e the time table for BDK owned Real time, Push, RMI Change in planned Temporary Speed Restriction. Reschedule trains on the said line End to if End to end H2[1.5] BAFO Tender Document Version 4.0 FbIS.F.196 Appendix 3.5 – Interface Requirements Page 46 of 98 ID Title From To Minimum Content Context Diagram Reference Purpose the trains on the said line For planning special Producti on Plans for traffic on a reduced infrastruc ture For giving fleet managers an overview over possible traffic Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function Impl. Test Perf. BDK owned Real time, Push, RMI FbIS.F.197 Change in planned Temporary Possessions Update Production Plans End to if End to end I2[1.5] BDK owned Real time, Push, RMI FbIS.F.197 Change in possessions Update infrastructure status End to if End to end I2[1.5] End to if End to end F2[1.5] End to if End to end I2[1.5] FbIS.I.484 Planned Temporary Possessions Fjernbane Infrastructure System (TMS) TOC planning systems Track number, starting and end points, validity period IF046 FbIS.I.485 Possessions Fjernbane Infrastructure System (TMS) Track number, starting and end points, On/Off IF008 IF046 IF101 FbIS.I.46 Predicted Delays Fjernbane Infrastructure System (TMS) TOC online timetable, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC: Dispatch RS, Dispatch Staff, Traffic Information System,Operat ions Monitoring System, Driver guidance. Train status Train Running Numbers, Predicted delays IF008 IF046 IF101 To inform of predicted delay BDK owned Real time, Push, RMI FbIS.F.143 FbIS.F.145 Changed status Updated systems can use predicted delays. FbIS.I.405 Report Booking Status Fjernbane Infrastructure System (TMS) TOC online Production Plan, Dispatch Booking Status ("booked", "rescheduled", IF046 Response to a previous BDK owned Real time, Push, FbIS.F.1729 Decision from Control Room User TOC system update Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Supplementary Info The performance requirement is estimated to F2[1.5] for the transition period. When the system is fully rolled out and the rescheduling function is working the performance requirement is estimated to H2[1.5]. Appendix 3.5 – Interface Requirements Page 47 of 98 ID Title From FbIS.I.483 Temporary and Emergency Speed Restrictions. Fjernbane Infrastructure System (TMS) FbIS.I.497 Production Plan information Fjernbane Infrastructure System (TMS) FbIS.I.80 Train Positions Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 To Minimum Content Context Diagram Reference RS "cancelled") TOC online Production Plan, Traffic Information System, Operations Monitoring System, Driver guidance. Train status TOC online Production Plan Track number, starting and end points, max velocity IF008 IF046 IF101 Production Plan information including changes compared to the previously agreed Production Plan IF046 TOC: Dispatch RS, Dispatch Staff, Traffic Information System,Operat ions Monitoring System, Driver guidance. Train status, Train Running Numbers, Onboard ETCS Identities, Positions, Consists, Time stamp, Train velocity IF008 IF046 IF101 Purpose Interface Type Design Constrai nt RMI Internal Reqs Triggering Function Consequence Function BDK owned Real time, Push, RMI FbIS.F.196 Change in Temporary and Emergency Speed Restrictions. To resynchr onise the ITsystems of TOC BDK owned Push, Push-PSGD FbIS.F.144 Request from TOC BDK "Train status" uses data from the signallin g system and other sources to calculate train position, BDK owned Real time, Push, RMI FbIS.F.164 Periodic sampling TOC fleet manager proposal of a change to one or more trains Enabling ITsystems to calculate a revised forecast for train running times BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. Recalculate train running times End to if End to end I2[1.5] To resynchronise the IT-systems of TOC with the current status of the online Production Plan Updated view on train positions End to if End to end J300[25 0] End to if End to end F2[1.5] Appendix 3.5 – Interface Requirements Page 48 of 98 ID Title From To Minimum Content Context Diagram Reference FbIS.I.504 Train Route Fjernbane Infrastructure System (TMS) TOC Traffic Information System, Driver guidance. Train status The route (track numbers or similar) of a train IF008 IF046 IF101 FbIS.I.499 Driver TOC Dispatch Staff Fjernbane Infrastructure System (TMS) Driver id, name and mobile phone number IF046 FbIS.I.192 TOC Train Data TOC Dispatch RS Fjernbane Infrastructure System (TMS) As per MFUN.001 (Refer to section 4.1.3 Vehicle properties) IF046 Fjernbane Infrastructure East/West Document1 Purpose delay, velocity and pass this informati on on to other systems. BDK "Train status" uses data on train routes (platform tracks) from the signallin g system and pass this informati on on to other systems. To provide driver name and mobile phone number Keep the infrastruc ture up to date about train informati on and allocatio Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function BDK owned Real time, Push, RMI FbIS.F.1914 When a MA is issued BDK owned Real time, Receivin g a push, RMI FbIS.F.343 BDK owned Real time, Receivin g a push, RMI FbIS.F.343 FbIS.F.578 FbIS.F.698 When a driver identify himself to the train by entering his driver ID, the signalling system requests information of the driver identity at the staff management system of TOC TOC knows data with reasonable confidence. BAFO Tender Document Version 4.0 Impl. Test Perf. Receiving system is updated End to if End to end G2[1.5] Driver information is updated in TMS End to if End to end D2[1.5] End-to-if End-toEnd A2[1.5] Data is recorded Supplementary Info The use of this interface is expected to grow over time as more vehicle data becomes available real-time from the TOCs and the schedulers Appendix 3.5 – Interface Requirements Page 49 of 98 ID FbIS.I.492 4.3.7 Title Change Online Production Plan From TOC online Production Plan, Dispatch RS To Minimum Content Fjernbane Infrastructure System (TMS) Production Plan data, Train Paths, Service Intentions IF046 Context Diagram Reference IF011 IF011 Purpose n of rolling stock to a specific train The fleet manager of TOC sends a proposal of a change of one or more trains Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. End to if End to end H2[1.5] become able to make use of the data. BDK owned Real time, Receivin g a push, RMI FbIS.F.583 Request from TOC Propose to Control Room User Purpose Interface Type Internal Reqs Triggering Function Consequence Function Run the train Public FbIS.F.1080 FbIS.F.1081 FbIS.F.1083 FbIS.F.1734 ERTMS function Run the train. Public Design Constrai nt ERTMS level 2, baseline 3 standards + Circuit switched and GPRS/E DGE+wi th and without authentic ation (KMC). Point-toPoint ERTMS level 2, FbIS.F.75 FbIS.F.105 ERTMS function ERTMS Fitted Train ID Title From To Minimum Content FbIS.I.261 ERTMS Balise Message Fjernbane Infrastructure System (balise) ERTMS Fitted train As defined by ETCS SRS. FbIS.I.32 ERTMS Radio Message Fjernbane Infrastructure ERTMS Fitted train As defined by ETCS SRS. Fjernbane Infrastructure East/West Document1 Context Diagram Reference BAFO Tender Document Version 4.0 Supplementary Info Impl. Test Perf. ERTMS function End to if End to end Accor ding to std. ERTMS function End to if End to end Accor ding Appendix 3.5 – Interface Requirements Page 50 of 98 ID Title From System (RBC) Fjernbane Infrastructure East/West Document1 To Minimum Content Context Diagram Reference Purpose Includes transition s to and from ERTMS Level 1,0 and NTC. Even though Level 1 is not part of the current fitment scope the Custome r expects the functions to be available and tested. Interface Type Design Constrai nt baseline 3 standards + Circuit switched and GPRS/E DGE+wi th and without authentic ation (KMC). Point-toPoint BAFO Tender Document Version 4.0 Internal Reqs FbIS.F.108 FbIS.F.128 FbIS.F.137 FbIS.F.138 FbIS.F.140 FbIS.F.146 FbIS.F.153 FbIS.F.165 FbIS.F.166 FbIS.F.167 FbIS.F.170 FbIS.F.180 FbIS.F.189 FbIS.F.194 FbIS.F.227 FbIS.F.228 FbIS.F.246 FbIS.F.262 FbIS.F.283 FbIS.F.284 FbIS.F.292 FbIS.F.293 FbIS.F.297 FbIS.F.298 FbIS.F.304 FbIS.F.307 FbIS.F.308 FbIS.F.312 FbIS.F.313 FbIS.F.326 FbIS.F.330 FbIS.F.345 FbIS.F.350 FbIS.F.351 FbIS.F.355 FbIS.F.356 FbIS.F.359 FbIS.F.387 FbIS.F.388 FbIS.F.389 FbIS.F.395 FbIS.F.396 Triggering Function Consequence Function Supplementary Info Impl. Test Perf. to std. Appendix 3.5 – Interface Requirements Page 51 of 98 ID Title From To Minimum Content Context Diagram Reference Purpose Interface Type Design Constrai nt FbIS.I.159 ERTMS Radio Message ERTMS Fitted train Fjernbane Infrastructure System (RBC) As defined by ETCS SRS. ERTMS Fitted Train Run the train Public ERTMS level 2, baseline 3 standards + Circuit switched and GPRS/E DGE+wi th and without authentic ation (KMC) FbIS.I.582 KMAC Key Fjernbane ERTMS Fitted KMAC key Fjernbane Receive BDK Real Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Internal Reqs FbIS.F.397 FbIS.F.406 FbIS.F.411 FbIS.F.412 FbIS.F.418 FbIS.F.420 FbIS.F.422 FbIS.F.433 FbIS.F.458 FbIS.F.1106 FbIS.F.1160 FbIS.F.1170 FbIS.F.1177 FbIS.F.1262 FbIS.F.1264 FbIS.F.1693 FbIS.F.1698 FbIS.F.1701 FbIS.F.1703 FbIS.F.1705 FbIS.F.1706 FbIS.F.1734 FbIS.F.1742 FbIS.F.1776 FbIS.F.295 FbIS.F.342 FbIS.F.346 FbIS.F.351 FbIS.F.352 FbIS.F.355 FbIS.F.356 FbIS.F.388 FbIS.F.389 FbIS.F.395 FbIS.F.396 FbIS.F.455 FbIS.F.458 FbIS.F.698 FbIS.F.1092 FbIS.F.1262 FbIS.F.1264 FbIS.F.1915 Triggering Function Consequence Function ERTMS function The train enter start of Supplementary Info Impl. Test Perf. ERTMS function End to if End to end Accor ding to std. The train uses End to if End to 30 Appendix 3.5 – Interface Requirements Page 52 of 98 ID 4.3.8 Title From To Infrastructure System (KMC) Train Minimum Content Context Diagram Reference Infrastruct ure System Purpose Interface Type KMAC key for RBC communi cation owned Context Diagram Reference IF013 Purpose Interface Type To archive logs BDK owned Internal Reqs Triggering Function Consequence Function mission and requests keys for the mission the KMAC key to establish communicatio n with RBC's along the mission Design Constrai nt Std. Fileform at - open format, Response to a pull operation from an external system, Pull-NB Std. Fileform at - open format, Response to a pull operation from an external system, Pull-NB On request, Push, PushO2O-GD On Internal Reqs Triggering Function Consequence Function FbIS.F.80 FbIS.F.81 Export function FbIS.F.70 Supplementary Info Impl. Test Perf. end secon ds Impl. Test Perf. The records are stored as a file End to end End to end O300[ 250] Export function The records are stored as a file End to end End to end M300[ 250] FbIS.F.115 Export function The offline production plan is stored. End to end End to end E300[ 250] FbIS.F.1926 Export function The file is End to if End to E300[ File System ID Title From To Minimum Content FbIS.I.27 Log Output Fjernbane Infrastructure System (TMS) File System Log records FbIS.I.254 Telegramjournale n Output Fjernbane Infrastructure System (TMS) File System Telegramjournalen records IF013 To export Telegram journalen records BDK owned FbIS.I.38 Production Plan Export Fjernbane Infrastructure System (TMS) File System Offline Production Plan IF013 Export for analysis BDK Owned FbIS.I.627 Export of Fjernbane File System Video file containing IF013 To BDK Fjernbane Infrastructure East/West Document1 Design Constrai nt time, point to point BAFO Tender Document Version 4.0 Supplementary Info Enabling Control Appendix 3.5 – Interface Requirements Page 53 of 98 playback session 4.3.9 Infrastructure System (TMS) playback session of a given screen capture. Title From To Minimum Content FbIS.I.619 KMC data for countrywide synchronization Fjernbane Infrastructure System (KMC) KMC of neighbouring Fjernbane Infrastructure. Cryptographic keys Context Diagram Reference IF025 FbIS.I.620 KMC data for countrywide synchronization KMC of neighbouring Fjernbane Infrastructure. Fjernbane Infrastructure System (KMC) Cryptographic keys IF025 request, Push, PushO2O-GD Purpose Interface Type Design Constrai nt Exchang e keys to facilitate train/infr astructur e communi cation Exchang e keys to facilitate train/infr astructur e communi cation Purpose Interface Type Exchang e keys to facilitate BDK owned stored in the file system Room Users in the Control Centre and O&M Co-ordinators in the Control Centre to screen capture the content of any window for a period of time as a video file. end 250] Perf. Context Diagram Reference IF015 Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test BDK owned FbIS.F.1916 FbIS.F.1923 Planning a train crossing the border between Fjernbane Infrastructure System EAST and Fjernbane Infrastructure System WEST Key available for neighboring KMC. Only if option 10 is not invoked End to if End to end BDK owned FbIS.F.1916 FbIS.F.1923 Planning a train crossing the border between Fjernbane Infrastructure System EAST and Fjernbane Infrastructure System WEST Key available for KMC of Fjernbane Inftrastructure System. Only if option 10 is not invoked End to if End to end Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test FbIS.F.1916 Planning a Danish train for travelling abroad Key available for foreign KMC. End to if End to end Foreign Key Management Centre ID Title From To Minimum Content FbIS.I.477 Keys for Danish trains abroad Fjernbane Infrastructure System Foreign KMC Cryptographic keys Fjernbane Infrastructure East/West Document1 Owned Neighbouring Key Management Centre ID 4.3.10 export any recorded file Design Constrai nt BAFO Tender Document Version 4.0 Perf. Appendix 3.5 – Interface Requirements Page 54 of 98 (KMC) FbIS.I.478 4.3.11 Keys of foreign trains in DK Foreign KMC Fjernbane Infrastructure System (KMC) Cryptographic keys IF015 Context Diagram Reference IF016 BDK owned FbIS.F.1916 Planning a foreign train for travelling to DK Key available for KMC of Fjernbane Inftrastructure System. End to if End to end Design Constrai nt Real time, Push, PushO2O-GD Internal Reqs Triggering Function Consequence Function Impl. Test Perf. FbIS.F.1791 A TMS user requests a GSM-R voice call to a number of trains. The TMS returns the associated GSM-R numbers GSM-R voice calls are established to the affected trains End to if End to end I5[4] Real time, Point-topoint, PushO2O-GD FbIS.F.1791 GSM-R call from driver The train number is converted to a train location in the TMS, which in turn is converted to a Signalman id or other role (depending on function code) and physical End to if End to end I2[1.5 ] GSM-R ID Title From To Minimum Content FbIS.I.438 Area Group calls Fjernbane Infrastructure System (TMS) GSM-R Area, function code FbIS.I.436 Routing of voice calls to Control Room Users Fjernbane Infrastructure System (TMS) GSM-R Train number, function code Fjernbane Infrastructure East/West Document1 train/infr astructur e communi cation (Danish trains abroad) Exchang e keys to facilitate train/infr astructur e communi cation (foreign trains in DK) IF016 Purpose Interface Type To route group calls to trains within a geograph ical area Routing of voice call from driver to relevant Control Room Users BDK owned BDK owned BAFO Tender Document Version 4.0 Supplementary Info Appendix 3.5 – Interface Requirements Page 55 of 98 ID Title From To Minimum Content Context Diagram Reference FbIS.I.437 Routing of voice calls to train Fjernbane Infrastructure System (TMS) GSM-R Train number, function code IF016 FbIS.I.439 SMS out Fjernbane Infrastructure System (TMS) GSM-R Train number(s), function code, SMS IF016 FbIS.I.440 SMS in GSM-R Fjernbane Infrastructure System (TMS) Train number, function code, SMS IF016 Fjernbane Infrastructure East/West Document1 Purpose Interface Type Design Constrai nt Internal Reqs Triggering Function To route a call from Control Room User to a train (function code might tell to whom (e.g. driver, public, Train guide) in the train, the call is) To send SMS to train(s) BDK owned Real time, Point-topoint FbIS.F.1791 GSM-R voice call from Control Room User. The TMS look up the GSM-R number associated to the train number, and pass it to the GSM-R BDK owned Real time, Point-topoint FbIS.F.1791 To receive SMS from train BDK owned Real time, Point-topoint FbIS.F.1791 A TMS user start sending an SMS to one or more train number. The TMS look up the GSM-R number associated to the train numbers, and pass them to the GSM-R A train driver start sending an SMS to a TMS user (function code). The TMS look up the GSM-R number associated to the train number, and pass it to BAFO Tender Document Version 4.0 Consequence Function Impl. Test Perf. End to if End to end I2[1.5 ] The SMS is send to the received GSM-R numbers End to if End to end The SMS is send to the received GSM-R number End to if End to end workplace for the area where the train is currently. The call is transferred to the Signalman or other role GSM-R voice call is established to the GSM-R number received Supplementary Info Appendix 3.5 – Interface Requirements Page 56 of 98 ID Title From To Minimum Content Context Diagram Reference Purpose Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. the GSM-R 4.3.12 Identity Management System ID Title From To Minimum Content FbIS.I.517 User Authentication Identity Management System Fjernbane Infrastructure System (TMS, building access and all other IT components using user login) User information, authentication information 4.3.13 Purpose Interface Type Common user access control system BDK owned Context Diagram Reference IF026 Purpose Interface Type To inform the PIS about an arriving train BDK owned IF026 To inform PIS BDK owned Design Constrai nt Real time, Receivin g a push, Push-PSGD Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.1918 Change of user configuration Update user configuration in access control system of Fjernbane Infrastructure System The current system is called "HURIT" End to end End to end D2[1. 5] Design Constrai nt Real time, Push, RMI Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.1913 A train arrives to a platform on a station The PIS is updated VICOS from Siemens - not interface to loudspeakers. If existing VICOS is not being changed (PISoption), reuse the existing interface to VICOS (point to point) otherwise an internal interface. End to if End to end D2[1. 5] Real time, Push, FbIS.F.121 A change in platform. The PIS is updated End to if End to end D2[1. 5] Passenger Information System ID Title From To Minimum Content FbIS.I.579 Arrival Fjernbane Infrastructure System (TMS) Passenger Information System Train number, station, platform, arrived FbIS.I.631 Platform Changes Fjernbane Infrastructure System (TMS) Passenger Information System Train number, station, the new platform the train is Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF018 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 57 of 98 arriving at FbIS.I.581 Delay Fjernbane Infrastructure System (TMS) Passenger Information System Train number, station(s), delay IF026 FbIS.I.578 Delete Train Path Fjernbane Infrastructure System (TMS) Passenger Information System Offline Production Plan record for a train IF026 FbIS.I.580 Departure Fjernbane Infrastructure System (TMS) Passenger Information System Train number, station, platform, departed IF026 Fjernbane Infrastructure East/West Document1 about a change in the platform that the indicated train will arrive at To inform the PIS about a delayed train RMI BDK owned Real time, Push, RMI FbIS.F.143 FbIS.F.145 A train departs a platform on a station (and a delay is calculated) The PIS is updated Delete an offline productio n plan record(s) for a train BDK owned Real time, Push, RMI FbIS.F.121 An online production plan record is deleted The PIS is updated To inform the PIS about a departing train BDK owned Real time, Push, RMI FbIS.F.1913 A train departs a platform on a station The PIS is updated BAFO Tender Document Version 4.0 VICOS from Siemens - not interface to loudspeakers. If existing VICOS is not being changed (PISoption), reuse the existing interface to VICOS (point to point) otherwise an internal interface. VICOS from Siemens - not interface to loudspeakers. If existing VICOS is not being changed (PISoption), reuse the existing interface to VICOS (point to point) otherwise an internal interface. VICOS from Siemens - not interface to loudspeakers. If existing VICOS is not being changed (PISoption), reuse the existing interface to VICOS (point to point) - End to if End to end D2[1. 5] End to if End to end D2[1. 5] End to if End to end D2[1. 5] Appendix 3.5 – Interface Requirements Page 58 of 98 FbIS.I.577 Update Train Path(s) Fjernbane Infrastructure System (TMS) Passenger Information System Online Production Plan record(s) for train(s). Standard Text Code. Free Text IF026 Update/c reate Online Producti on Plan record(s) for one train(s) BDK owned Real time, Push, RMI FbIS.F.121 FbIS.F.1925 Changes in the online Production Plan The PIS is updated with transmitted Online Production Plan record(s) FbIS.I.632 New committed connections Fjernbane Infrastructure System (TMS) Passenger Information System New committed connections IF026 BDK owned Real time, Push, RMI FbIS.F.121 Changes in the online Production Plan FbIS.I.633 Current Train position Fjernbane Infrastructure System (TMS) Passenger Information System Position of train, Train Number, Onboard ETCS Identities IF026 BDK owned Real time, Push, RMI FbIS.F.164 Position changed FbIS.I.634 Online Production Plan Fjernbane Infrastructure System (TMS) Passenger Information System Online Production Plan or changes to the online production plan IF026 To update the PIS on new committe d connecti ons To inform PIS of current train positions. The PIS shall be informed of the current Online Producti on Plan and of any changes made to it. BDK owned Real time, Push, RMI FbIS.F.121 Initiation of system or changes to Online Production Plan Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 otherwise an internal interface. VICOS from Siemens - not interface to loudspeakers. If existing VICOS is not being changed (PISoption), reuse the existing interface to VICOS (point to point) otherwise an internal interface. End to if End to end C2[1. 5] The PIS is updated with transmitted Online Production Plan record(s) End to if End to end C2[1. 5] The PIS is updated with transmitted Online Production Plan record(s) The PIS is updated with transmitted Online Production Plan record(s) End to if End to end C2[1. 5] End to if End to end C5[4] The online production plan is published to the PIS. When appropriate only changes to the online production plan are sent from TMS to the PIS in order to minimize the amount of data sent. Appendix 3.5 – Interface Requirements Page 59 of 98 4.3.14 Point Heating Control System ID Title From To Minimum Content FbIS.I.442 Point heating monitoring Point heating System Fjernbane Infrastructure System (TMS) Point heating area, On/ off/automatic. 4.3.15 Context Diagram Reference IF028 Purpose Interface Type To monitor status of point heating BDK owned Context Diagram Reference IF030 Purpose Interface Type Avoid schedulin g of train moveme nts into unpower ed catenary sections. BDK owned Title From To Minimum Content FbIS.I.173 Planned Catenary Shut Offs Possession planning system Fjernbane Infrastructure System (TMS) Track number, starting and end points of track section without power, valid date & time interval FbIS.I.99 Planned Possessions Possession planning system Fjernbane Infrastructure System (TMS) Possession, date/time interval, the details of which tracks/routes and points must be blocked, any restrictions on the position of Trains. IF030 To prepare planned possessio ns in the signallin g system BDK owned Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.77 Change of status Read the status of point heating for a specific point heating area Only System 2000 in scope If to end If to end I5[4] Design Constrai nt Real time, Receivin g a push, PushO2OGD, IP protocol, IEC 60870 Real time, Receivin g a push, PushO2O-GD Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.300 Changes in the planned catenary shut offs Reschedule Online Production Plan if necessary End to end End to end C5[4] FbIS.F.206 FbIS.F.409 Request by Fjernbane Infrastructure System The planned possession is implemented or simulated in signalling system Possessions are approved for use by the O&M Coordinator using the Fjernbane Infrastructure System and not the Possession management System. End to end End to end C5[4] Context Diagram Reference IF031 Purpose Interface Type Design Constrai nt Real Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. To pass BDK FbIS.F.121 A change in the online The Online End to if End to C5[4] Punctuality / Delay Reporting System ID Title From To Minimum Content FbIS.I.446 Online production Fjernbane Punctuality/De Online Production Fjernbane Infrastructure East/West Document1 Internal Reqs Possession Planning System ID 4.3.16 Design Constrai nt Real time, Receivin g a push, PushO2O-GD BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 60 of 98 FbIS.I.20 4.3.17 plan updates Infrastructure System (TMS) lay reporting system Plan changes. Punctuality Data Fjernbane Infrastructure System (TMS) Punctuality/De lay reporting system Online Production Plan. Offline Production Plan. Change history. Changes according to the common root cause associated with the divergence. Root cause. IF031 Title From To Minimum Content FbIS.I.456 Co-ordinate railway and road signalling Fjernbane Infrastructure System (IL) Road signalling system "Train programme" ("togprogram"); "Level crossing activated" and "Level Crossing not activated". time, Push, PushO2O-GD FbIS.F.687 Production Plan occurs Production Plan is overwritten BDK owned Real time, Push, PushO2O-GD FbIS.F.103 FbIS.F.687 FbIS.F.1726 The delay criteria for a train is not met The delay information is used to calculate delay report Context Diagram Reference IF034 Purpose Interface Type Internal Reqs Triggering Function Consequence Function To coordinate level crossing and road signallin g BDK owned Design Constrai nt Real time, point to point FbIS.F.1807 A train is approaching a level crossing with road signalling close by. The road signalling is co-ordinated according to the railway signalling Context Diagram Reference IF037 Purpose Interface Type Internal Reqs Triggering Function Consequence Function Manage ment of Train positions on crossing BDK owned Design Constrai nt Real time, Push, streamin g, RMI FbIS.F.164 Periodic sampling Updated view on train positions end End to if End to end C5[4] Impl. Test Perf. End to end End to end 1 Supplementary Info Impl. Test Perf. The existing SCADA systems at Storebælt and Øresund are planned to be renewed before End to if End to end C5[4] Supplementary Info Tunnel and Bridge SCADA (SRO) Systems and Detectors ID Title From To Minimum Content FbIS.I.589 Train Positions Fjernbane Infrastructure System (TMS) SCADA (SRO) systems Train Running Numbers, Onboard ETCS Identities, Train Position(s), Train Direction(s), Fjernbane Infrastructure East/West Document1 owned Road Signalling System ID 4.3.18 on online productio n plan changes to RDStype system To pass on delay informati on to RDStype system BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 61 of 98 Track blocked for trains, Consists, Time measured, Train velocity FbIS.I.230 Stop/resume Trains SCADA (SRO) systems Fjernbane Infrastructure System (TMS) Bridge/Tunnel Entrance ID, Stop/resume IF037 FbIS.I.629 SCADA alarms SCADA (SRO) systems Fjernbane Infrastructure System (TMS) IF037 FbIS.I.630 Changes to online production plan Fjernbane Infrastructure System (TMS) SCADA (SRO) systems Train stopped in tunnel. Ventilation. Water tank for fire fighting. Escape doors. Light in Tunnel. Escape route signs. Central and local SCADA. Radio communication between TCC and yellow fleet. Radio communication between TCC and yellow fleet and emergency telephones. Pushbutton for fire alarm and emergency telephone. Gas Detector in pump sump. Changes to online production plan. Fjernbane Infrastructure East/West Document1 IF037 Stop/resu me trains from entering bridge/tu nnel To inform TMS that no trains can run via the tunnel. When the tunnel is available for usage again the alarm(s) is cleared. BDK owned Real time, Receivin g a push, RMI FbIS.F.420 FbIS.F.421 SCADA alarm or similar - or user input to SCADA Stop trains resume trains BDK owned Real time, Receivin g a push, RMI FbIS.F.420 FbIS.F.421 The criteria/threshold for one the listed alarms is violated, for instance train is halted in tunnel or ventilation is not working properly. To inform the SCADA system of BDK owned Real time, push, RMI FbIS.F.420 FbIS.F.421 Occurred events. BAFO Tender Document Version 4.0 the Roll-out of the new Signalling System. Because of this the final requirements to the interfaces to the SCADA systems are not known at present. Great Bælt bridge/tunnel Øresund bridge/tunnel End to if End to end D2[1. 5] Signal oprator is advised and rescheduling is triggered. End to if End to end D2[1. 5] SCADA is updated. End to if End to end H2[1. 5] Appendix 3.5 – Interface Requirements Page 62 of 98 FbIS.I.470 Stop Trains Due To Derailment Derailment detector Fjernbane Infrastructure System (IL) Derailment alarm IF037 FbIS.I.469 Stop Trains Due To Hot axle Hot axle box detector Fjernbane Infrastructure System (IL) Hot axle alarm IF037 Context Diagram Reference IF038 4.3.19 BDK owned Real time, point to point FbIS.F.420 FbIS.F.421 Derailment has been detected Train will be stopped Great Bælt bridge and tunnel. Øresund bridge and tunnel End to end End to end 1 BDK owned Real time, point to point FbIS.F.420 FbIS.F.421 Hot axle has been detected Train will be stopped Great Bælt bridge and tunnel. Øresund bridge and tunnel End to end End to end 1 Purpose Interface Type Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. Mapping of control room user identity to area of control in order to route telephon BDK Owned Design Constrai nt Real Time, Push, PushO2O-GD FbIS.F.58 External Phone Call Call Routed to Control Room User End to End End to End D5[4] Telephone Exchange/Switchboard ID Title From To Minimum Content FbIS.I.43 Mapping of Signalman to Area Fjernbane Infrastructure System (TMS) Telephone Exchange/Swi tchboard To be developed by Supplier. Fjernbane Infrastructure East/West Document1 changes to the online productio n plan. To make the IL aware of a derailme nt and thereby prevent trains from entering the area To make the IL aware of a hot axle and thereby prevent trains from entering the area BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 63 of 98 e calls (includin g from emergen cy telephon es in tunnels and other GSM-R routed calls). 4.3.20 Time Reference ID Title From To Minimum Content FbIS.I.264 Time Synchronisation Time Reference Fjernbane Infrastructure System Correct date and time 4.3.21 Purpose Interface Type To synchron ise time against official time Public Context Diagram Reference IF040 Purpose Interface Type Create an online Producti on Plan BDK Owned Design Constrai nt Rel. Standard s Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.646 Accepted time difference is about to be exceeded Time is updated Supplier shall be able to make use of the customer provided Network Time Protocol (NTP). The clock generating the time reference will reside on a dedicated server or on a selected router of the Fixed Transmission Network (FTN). End to end End to End Max. Differ ence to be agreed during design Design Constrai nt On request, Pull, Pull-NB Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.115 Request from TMS To be converted to an online Production Supplier shall provide facilities for implementing custom imports End to end End to End O300[ 250] Offline Production Plan ID Title From To Minimum Content FbIS.I.37 Production Plan Import Offline Production Plan Fjernbane Infrastructure System (TMS) Offline Production Plan Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF039 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 64 of 98 4.3.22 Title From To Minimum Content FbIS.I.445 Train Traffic on Migrated Tracks Fjernbane Infrastructure System (TMS) TMS Existing Fjernbane Train number, delays and train sequences. FbIS.I.444 Train Traffic on Non Migrated Tracks TMS Existing Fjernbane Fjernbane Infrastructure System (TMS) Train number, delays and train sequences. IF041 Context Diagram Reference IF041 Context Diagram Reference IF042 Purpose Interface Type Design Constrai nt Real time, Push, RMI Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. Display train data from migrated network Display train data from non migrated network BDK owned FbIS.N.1020 Change of train position data in new TMS Display train position data in existing TMS Interface only used during migration period End to end End to end G1[0. 5] BDK owned Real time, Receivin g a push, RMI FbIS.N.1020 Change of train position data in existing TMS Display train position data in new TMS Interface only used during migration period End to end End to end G1[0. 5] Purpose Interface Type Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. To handover trains to Germany BDK owned Design Constrai nt Real time, Push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on Fjernbane. Padborg (DB Netze) only Tønder and Fehmarn are out of scope End to if End to end D1[0. 5] TMS Foreign Railway ID Title From To Minimum Content FbIS.I.466 Handover Train To Germany Fjernbane Infrastructure System (TMS) German TMS Actual running times, predictions, service info, changes to Online Production Plan, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Train Telephone Fjernbane Infrastructure East/West Document1 through a flexible text transformation facility to meet future text formats. The facility shall be demonstrated to work with CSV, XML and JSONformatted timetable data. TMS Existing Fjernbane ID 4.3.23 Plan BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 65 of 98 FbIS.I.464 Handover Train To Sweden Fjernbane Infrastructure System (TMS) Swedish TMS FbIS.I.467 Receive Train From Germany German TMS Fjernbane Infrastructure System (TMS) FbIS.I.465 Receive Train From Sweden Swedish TMS Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 Number, Trains With UT Code Reuse spec. for existing interface (actual running times, predictions, service info, changes to Online Production Plan, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Train Telephone Number, Trains With UT Code) Actual running times, predictions, service info, changes to Online Production Plan, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Train Telephone Number, Trains With UT Code Reuse spec. for existing interface (actual running times, predictions, service info, changes to Online Production Plan, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Train Telephone Number, Trains With UT Code) IF042 To handover trains to Sweden BDK owned Existing interface spec. , Push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on Fjernbane. IF042 To receive trains from Germany BDK owned Real time, receiving a push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on foreign railway IF042 To receive trains from Sweden BDK owned Existing interface spec., receiving a push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on foreign railway BAFO Tender Document Version 4.0 Padborg (DB Netze) only Tønder and Fehmarn are out of scope End to if End to end D1[0. 5] End to if End to end D1[0. 5] End to if End to end D1[0. 5] Appendix 3.5 – Interface Requirements Page 66 of 98 4.3.24 TMS Neighbouring Fjernbane Infrastructure ID Title From To Minimum Content FbIS.I.68 Send Online Production Plan Fjernbane Infrastructure System (TMS) TMS neighbouring Fjernbane Infrastructure Online production plan & changes FbIS.I.202 Send Railway Status Fjernbane Infrastructure System (TMS) TMS neighbouring Fjernbane Infrastructure Blocks, Catenary Powered Trains, Catenary Status, Clamped Points, Deviation from Online Production Plan, Drivers Telephone Numbers, Emergency Speed Restrictions, Failed Trains, Fitted Trains, Great Belt Bridge Closed, Level Crossing Status, Movement Authorities, Lock status of points, Lock status of lockable elements, Marker Boards, Network Topology, Fjernbane Infrastructure East/West Document1 Context Diagram Reference IF043 Purpose Interface Type To keep the two TMS's in sync BDK owned IF043 To keep the two TMS's in sync BDK owned Design Constrai nt Real time, Push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP Real time, Push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP BAFO Tender Document Version 4.0 Internal Reqs Triggering Function Consequence Function FbIS.F.151 FbIS.F.663 Status Changed or Periodically FbIS.F.377 Changed data Supplementary Info Impl. Test Perf. Update online production plan End to if End to end C1 Show status to users in control room End to if End to end A1 Appendix 3.5 – Interface Requirements Page 67 of 98 FbIS.I.509 Send Train position and delay Fjernbane Infrastructure System (TMS) TMS neighbouring Fjernbane Infrastructure FbIS.I.383 Receive Online Production Plan TMS neighbouring Fjernbane Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 Point Positions, Points that must not be clamped by a Driver, Points without detection or Trailed, Radio Hole, RID Class 1 trains, Set routes, Shunt Areas, Source of Train Running Numbers (Train or Signalman), Temporary Speed Restrictions, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Train Telephone Number, Trains With UT Code, Work Site Speed Restrictions. Actual running time Predictions Service information Online production plan & changes IF043 To prepare for handing over trains across the border BDK owned IF043 To keep the two TMS's in BDK owned Real time, Push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP Real time, receiving BAFO Tender Document Version 4.0 FbIS.F.377 Changed status Update status FbIS.F.1785 Status Changed or Periodically Update online production plan This message flow is only relevant during migration period. When the Fjernbane Infrastructure System is fully in place this FbIS.1.509 is replaced by FbIS.I.202 End to if End to end A1 End to if End to end C1 Appendix 3.5 – Interface Requirements Page 68 of 98 Infrastructure FbIS.I.201 Receive Railway Status TMS neighbouring Fjernbane Infrastructure Fjernbane Infrastructure East/West Document1 sync Fjernbane Infrastructure System (TMS) Blocks, Catenary Powered Trains, Catenary Status, Clamped Points, Deviation from Online Production Plan, Drivers Telephone Numbers, Emergency Speed Restrictions, Failed Trains, Fitted Trains, Great Belt Bridge Closed, Level Crossing Status, Movement Authorities, Marker Boards, Network Topology, Point Heating Status, Point Positions, Points that must not be clamped by a Driver, Radio Hole, RID Class 1 trains, Set routes, Shunt Areas, Source of Train IF043 To keep the two TMS's in sync BDK owned a push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP Real time, Receivin g a push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP BAFO Tender Document Version 4.0 FbIS.F.74 FbIS.F.77 Changed data Show status to users in control room End to if End to end A1 Appendix 3.5 – Interface Requirements Page 69 of 98 FbIS.I.508 4.3.25 Receive Train position and delay TMS neighbouring Fjernbane Infrastructure Fjernbane Infrastructure System (TMS) Running Numbers (Train or Signalman), Temporary Speed Restrictions, Track Occupancy, Trailed Points, Train Characterisation, Train Positions, Train Running Numbers, Trains With UT Code, Work Site Speed Restrictions Actual running time Predictions Service information To prepare for receiving trains across the border BDK owned Real time, Receivin g a push, Point-toPoint, IP protocol, IEC 60870, XML, UIC 407.1, TSI TAF, TSI TAP FbIS.F.74 FbIS.F.77 Changed status Update status Context Diagram Reference IF044 Purpose Interface Type Internal Reqs Triggering Function Consequence Function To handover trains to Private Line BDK owned Design Constrai nt Existing interface spec., Push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on Fjernbane. End to if End to end A1 Impl. Test Perf. End to if End to end D1[0. 5] TMS Private lines ID Title From To Minimum Content FbIS.I.598 Handover Train To Private Line Fjernbane Infrastructure System (TMS) TMS Private Lines Reuse spec. for existing interface (actual running times, predictions, service info, changes to Online Production Plan) Fjernbane Infrastructure East/West Document1 IF043 BAFO Tender Document Version 4.0 Supplementary Info Appendix 3.5 – Interface Requirements Page 70 of 98 FbIS.I.158 Railway Status Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 TMS Private Lines Blocks, Catenary Powered Trains, Catenary Status, Clamped Points, Deviation from Online Production Plan, Drivers Telephone Numbers, Emergency Speed Restrictions, Failed Trains, Fitted Trains, Level Crossing Status, Movement Authorities, Lock status of points, Lock status of lockable elements, Marker Boards, Network Topology, Point Positions, Points that must not be clamped by a Driver, Points without detection or Trailed, Radio Hole, RID Class 1 trains, Set routes, Shunt Areas, Source of Train Running Numbers (Train or Signalman), Temporary Speed Restrictions, Track Occupancy, Train Characterisation, Train Positions, Train Running Numbers, Trains With UT IF044 To facilitate smooth transfer of trains across the border BDK owned Real time, Push, RMI BAFO Tender Document Version 4.0 FbIS.F.273 FbIS.F.1920 Change of status View status on Fjernbane Scope: Helsingør, Snekkersten (TMS: Cactus);Køge (TMS: Cactus); Nykøbing Falster Vest (TMS: EbiScreen 2000);Frederiksha vn (TMS: EbiScreen 2000); Develop interface but will not be integration tested and put into operation N/A A1[0. 5] Appendix 3.5 – Interface Requirements Page 71 of 98 FbIS.I.599 Receive Train From Private Line TMS Private Lines Fjernbane Infrastructure System (TMS) FbIS.I.157 Private Lines Status TMS Private Lines Fjernbane Infrastructure System (TMS) Code, Work Site Speed Restrictions. Reuse spec. for existing interface (actual running times, predictions, service info, changes to Online Production Plan) Track Occupancy, Lineside Signal Indications 4.3.26 Title From To Minimum Content FbIS.I.227 UT Circular UT Circular System Fjernbane Infrastructure System (TMS) UT Code, Speed Restrictions, Tracks not allowed. BDK owned Existing interface spec., Receivin g a push, RMI FbIS.F.1920 FbIS.IR.62 Change of status View status on Private Line railway End to if End to end D1[0. 5] IF044 To facilitate smooth transfer of trains across the border BDK owned Real time, Receivin g a push, RMI FbIS.F.271 FbIS.F.1920 Change of status View status on adjacent lines Scope: Helsingør, Snekkersten (TMS: Cactus);Køge (TMS: Cactus); Nykøbing Falster Vest (TMS: EbiScreen 2000);Frederiksha vn (TMS: EbiScreen 2000); Develop interface but will not be integration tested and put into operation N/A A1[0. 5] Context Diagram Reference IF048 Purpose Interface Type Internal Reqs Triggering Function To facilitate planning of trains with special requirem ents BDK owned Design Constrai nt Real time, Receivin g a push, PushO2O-GD Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.105 FbIS.F.165 FbIS.F.166 FbIS.F.414 FbIS.F.418 FbIS.F.1776 UT codes are changed Online Production Plan is updated The Fjernbane Infrastructure System shall take into account all UT codes regarding Out of Gauge and Dangerous Goods. End to end End to end C5[4] Context Diagram Reference IF010 Purpose Interface Type Internal Reqs Alarmce BDK Design Constrai nt Real Triggering Function Consequence Function Supplementary Info Impl. Test Perf. An accident occurs Alarmcentrale Related to End to end End to Emergency Services (Alarmcentralen 112) ID Title From To Minimum Content FbIS.I.614 Accident Fjernbane Emergency - Location of accident Fjernbane Infrastructure East/West Document1 To receive trains from Private Line UT Circular System ID 4.3.27 IF044 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 72 of 98 information 4.3.28 Infrastructure System (TMS) Services (Alarmcentral en 112) precise to 10m - If the accident is related to a train, the location must include track position - If the accident involves freight trains, data on e.g. dangerous goods must be transmitted owned time, point-topoint Purpose Interface Type Enabling the use of backoffice applicati ons within the Fjernban e Infrastru cture System, e.g. allowing a user to use and enter data into the backoffice BDK owned Design Constrai nt Real time, point-topoint, StreamO2O-GD n is notified MFUN.001 (Refer to section 3.2.1) end Triggering Function Consequence Function Supplementary Info Impl. Test Perf. Usage of back-office appliations/functionalit y The backoffice application is executed Related to MFUN.001. There is no need to exchange data between the Fjernbane Infrastructure System and the back-office systems. The important thing is that the backoffice applications can be displayed in the TMS display surface and controlled via the TMS keyboard/mouse. The back-office End to if End to end C2[1.5] Customer Back-office systems ID Title From To Minimum Content FbIS.I.616 Office application user input Fjernbane Infrastructure System (TMS) Customer Back-office Systems Data used in office appliations Fjernbane Infrastructure East/West Document1 ntralen (the emergen cy services) is notified promptly if an accident occurs including train position, possible dangerou s goods Context Diagram Reference IF007 BAFO Tender Document Version 4.0 Internal Reqs Appendix 3.5 – Interface Requirements Page 73 of 98 systems FbIS.I.617 4.3.29 Office application HMI information Customer Back-office Systems Fjernbane Infrastructure System (TMS) Data used in office appliations IF007 Enabling the use of backoffice applicati ons within the Fjernban e Infrastru cture System, e.g. allowing the backoffice systems to display informati on to the user within the Fjernban e Infrastru cture System. BDK owned Real time, point-topoint, StreamO2O-GD Context Diagram Reference IF004 Purpose Interface Type Enabling BDK Design Constrai nt Real Usage of back-office appliations/functionalit y End to if End to end C2[1.5] CCTV ID Title From To Minimum Content FbIS.I.622 Surveillance CCTV Fjernbane Motion picture Fjernbane Infrastructure East/West Document1 applications should rather run on a separate network that does not interfere with the signalling system. Related to MFUN.001. There is no need to exchange data between the Fjernbane Infrastructure System and the back-office systems. The important thing is that the backoffice applications can be displayed in the TMS display surface and controlled via the TMS keyboard/mouse. The back-office applications should rather run on a separate network that does not interfere with the signalling system. BAFO Tender Document Version 4.0 Internal Reqs Triggering Function Consequence Function Supplementary Info Impl. Test Perf. Image requested. Image visible Related to End to end End to A2[1. Appendix 3.5 – Interface Requirements Page 74 of 98 video 4.3.30 Infrastructure System (TMS) owned time, Push, , RMI to authorised Control Room User. MFUN.001. There is no need to exchange data between the Fjernbane Infrastructure System and the CCTV. The important thing is that the data from the CCTV can be displayed in the TMS display surface and the controlled via the TMS keyboard/mouse. The CCTV data should rather run on a separate network that does not interfere with the signalling system. Purpose Interface Type Internal Reqs Enabling the Failure Manage ment Tool to transfer the plan for failure manage ment Enabling the BDK owned Design Constrai nt Real time, Receivin g a push, PushO2O-GD Real time, end 5] Triggering Function Consequence Function Supplementary Info Impl. Test Perf. FbIS.F.745 Request Failure Management Plan (FbIS.I.638). Failure Management Plan integrated into Online Production Plan. End to If End to end C5[4] FbIS.F.1725 Milestone due. Milestone confirmed. End to If End to end C5[4] Failure Management Tool ID Title From To Minimum Content FbIS.I.636 Failure Management Plan Failure Management Tool Fjernbane Infrastructure System (TMS) Failure Mangement Plan FbIS.I.637 Milestone confirmation Failure Management Fjernbane Infrastructure Milestone confirmation Fjernbane Infrastructure East/West Document1 presentat ion of surveilla nce video within the Fjernban e Infrastru cture System. Context Diagram Reference IF060 IF060 BDK owned BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 75 of 98 Tool System (TMS) FbIS.I.638 Request Failure Management Plan Fjernbane Infrastructure System (TMS) Failure Mangement Tool A request on receiving Failure Management Plan IF060 FbIS.I.639 Request update on milestone Fjernbane Infrastructure System (TMS) Failure Mangement Tool A request for an update on milestone IF060 Context Diagram Reference IF061 4.3.31 Receivin g a push, PushO2O-GD BDK owned Real time, Push, PushO2O-GD FbIS.F.745 FbIS.F.1726 Divergence detected. Failure management is requested. End to If End to end C5[4] BDK owned Real time, Push, PushO2O-GD FbIS.F.733 Milestone lapsed. Failure management is requested. End to If End to end C5[4] Purpose Interface Type Design Constrai nt Internal Reqs Triggering Function Consequence Function Impl. Test Perf. To enable planning BDK owned FbIS.F.80 Request from SAP PM Data provided. End to If End to end E300[ 240] SAP PM ID Title From To Minimum Content FbIS.I.644 Infrastructure usage Fjernbane Infrastructure System (TMS) SAP PM Usage of infrastructure, e.g. - the number of Fjernbane Infrastructure East/West Document1 Failure Manage mentToo l to provide status on a given mileston e. Enabling the Fjernban e Infrastru cture System to request the Failure Manage ment Plan Enabling the Fjernban e Infrastru cture System to request a status on a given mileston e BAFO Tender Document Version 4.0 Supplementary Info Appendix 3.5 – Interface Requirements Page 76 of 98 times different part of the infrastructure is used - traffic quantities that have passed any infrastructure element during the element’s lifetime FbIS.I.645 Infrastructure failure Fjernbane Infrastructure System (TMS) Fjernbane Infrastructure East/West Document1 SAP PM Infrastructure element errors, e.g. - number of errors from an infrastructure element of maintena nce accordin g to usage ( instead of time based maintena nce) IF061 BDK owned FbIS.F.80 BAFO Tender Document Version 4.0 Request from SAP PM Data provided. End to If End to end E300[ 240] Appendix 3.5 – Interface Requirements Page 77 of 98 4.4 System-Users Interface Definitions ((The changes in this section are so substantial that the Customer has chosen not to show the change markings – The Section has been deleted)) 4.5 Interface Design Constraints The following Interface Requirements apply low level constraints as to how the System shall handle specific interfaces. The Customer intends that these Requirements will be appropriately applied in forming the design of the overall solution. Note, further information regarding the rationale for low level constraints on interfaces is also presented in Appendix 16. 4.5.1 Fjernbane Infrastructure System - Internal Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: FbIS.IR.42 The Traffic Management System as part of the Fjernbane Infrastructure System shall conform to the Technical Specifications for Interoperability for Telematic Applications for Passenger (TSI TAP) and the Technical Specifications for Interoperability for Telematic Applications for Freight (TSI TAF) on all interfaces that support these standards. TAF TSI is published and TAP TSI is(454/2011) expectedwas published during 2010May 2011, so the customer expects the suppliers to provide a complying system. Minimum E&W FbIS.IR.131 The Fjernbane Infrastructure System shall conform to EN50190.Deleted Minimum E&W FbIS.IR.45 The Traffic Management System as part of the Fjernbane Infrastructure System shall interface to the Shunter Hand Held Terminal for the transfer of shunting requests and confirmations and information on shunting times. The Supplier should review draft standards such as EETROP and seek approval for the methodology and data to be used during the preliminary design phase. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 78 of 98 Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: 4.5.2 The Traffic Management System as part of the Fjernbane Infrastructure System shall interface to the PICOP Hand Held Terminal for the transfer of possession requests, possession confirmations and service information. The Supplier should review draft standards such as EETROP and seek approval for the methodology and data to be used during the preliminary design phase. Minimum E&W FbIS.IR.140 The Traffic Management System as part of the Fjernbane Infrastructure System shall interface to the Watchman Hand Held Terminal for the transfer of shunting requests for Temporary Speed Restrictions and confirmation of presence and location. The Supplier should seek approval for the methodology and data to be used during the preliminary design phase. Minimum E&W Adjacent Signalling Systems Identifier: Requirement: Guidance: FbIS.IR.46 FbIS.IR.123 The Fjernbane Infrastructure System shall include an interface to each Adjacent Signalling System using a design which is accepted by the Systemsystem Responsibleresponsible for the Adjacent Signalling System to enable the passage of Trains to and from the Adjacent Signalling System. In this context and Adjacent Signalling System is any Signalling System, controlling the movement of Trains on tracks connected directly to tracks controlled by the Fjernbane Infrastructure System. As such an Adjacent Signalling System may be a conventional Fjernbane system during migration. Adjacent Signalling Systems will include Foreign Signalling Systems, Private Line Signalling Systems, the neighbouring Fjernebane Infrastructure System as well as the old and new Sbane Signalling Systems. Type: Area: The Customer will identify the Systemsystem Responsiblesresponsibles. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 79 of 98 Identifier: Requirement: Guidance: Type: Area: 4.5.3 The Fjernbane Infrastructure System shall conform to UIC CODE 407-1 for all data exchanges with neighbouringexisting, foreign and private Traffic Management Systems that support this Standard. Minimum E&W BDK Legacy Assets and Equipment Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: FbIS.IR.62 FbIS.IR.30 The Fjernbane infrastructure system shall provide the necessary interface to support operation of key-lock and similar equipment. This applies to each generic locking device including Bascule Bridges. Minimum E&W FbIS.IR.33 The point machines of The Fjernbane Infrastructure System shall be able to be mounted on either side of the point. This also applies to key-locked or similar hand-operatingoperated mechanismmechanisms. This requirement does not apply to built in point machines. Minimum E&W FbIS.IR.34 The point machines, bars, external locks , etc. of The Fjernbane Infrastructure System shall fit the moveable track elements of BaneDanmark. This includes, but is not limited, to: - fixing elements onto sleepers, - fixing elements onto rails, - fixing elements onto blades. This also applies to key-locked or similar hand-operatingoperated mechanism. Movable element types are specified separately. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 80 of 98 Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: FbIS.IR.35 Point machines, bars, external locks , etc. of The Fjernbane Infrastructure System shall not interfere with existing point heaters of BaneDanmark. This also applies to key-locked or similar hand-operatingoperated mechanism. Point heater is specified separately. Non-Minimum E&W FbIS.IR.36 The point machines of The Fjernbane Infrastructure System shall have suitable throw length for the moveableMoveable elementsElements ofso BaneDanmarkas to avoid twisting the blades. This also applies to key-locked or similar hand-operatingoperated mechanism. ExistingThe throwrequirements lengthswith areregards specifiedto separatelythe clearance between blade and stock rail have to be respected. Please refer to FbIS.IR.39, FbIS.IR.40 and FbIS.IR.41. Minimum E&W FbIS.IR.37 The point machine locks (internal or external) of The Fjernbane Infrastructure System shall accept mounting tolerances of +/- 25 mm. This also applies to key-locked or similar hand-operatingoperated mechanism. Minimum E&W FbIS.IR.39 For the point machines of The Fjernbane Infrastructure System the open switch blade rail shall have at least 150mm clearance from the stock rail for motor 1. This also applies to key-locked hand-operating mechanism. The stated minimum value also apply to position proving mechanism. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 81 of 98 Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: FbIS.IR.40 For the point machines of The Fjernbane Infrastructure System the open switch blade rail shall have at least 60mm clearance from the stock rail for motor 2. The stated minimum value also apply to position proving mechanism. Minimum E&W FbIS.IR.41 For the point machines of the Fjernbane Infrastructure System the open switch blade rail shall have at least 60mm clearance from the stock rail for motor 3 The stated minimum value also apply to position proving mechanism. Minimum E&W FbIS.IR.105 For the Early Deployment lines, the Fjernbane Infrastructure System shall provide a Changeover System enabling elements and interfaces to be controlled/accessed by either - the existing interlocking and CTC system, or - the Fjernbane Infrastructure System. This does not exclude feeding state information in parallel to the existing interlocking/CTC system and the Fjernbane Infrastructure System, if feasible and safe to do so. Minimum E&W FbIS.IR.106 The Changeover System for the Fjernbane Infrastructure System shall support control of - new elements/equipment with existing interlocking and CTC system, or - old elements/equipment with the Fjernbane Infrastructure System, or - both, depending on the Supplier's preferred commissioning strategy for Early Deployment lines. Either solution is expected to call for adaptations to existing interfaces. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 82 of 98 Identifier: Requirement: Guidance: FbIS.IR.107 The Changeover System for the Fjernbane Infrastructure System shall cover up to 100% ofall relevant elements of the Early Deployment lines. Certain (new) elements may not need to be controlled by the existing interlocking and CTC system. Certain (old) elements may not need to be controlled by the Fjernbane Infrastructure System. In this context, "relevant elements" implies that there shall be sufficient coverage of - element types, and - track topologies to support test and demonstration of the system. The elements covered by the changeover system may be confined to one or more sub-sections of the Early Deployment Lines. (Refer to appendix 14.1) Type: Area: This does not exclude a more complete coverage of the Early Deployment Lines, if feasible. Minimum E&W Identifier: Requirement: FbIS.IR.108 Guidance: The sectioning may be governed by topology of existing interlocking and CTC systems and/or the Supplier's commissioning and test strategyDeleted. Minimum E&W Type: Area: The Changeover System for the Fjernbane Infrastructure System shall be able to operate selectively on certain sub-sections of the Early Deployment linesDeleted. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 83 of 98 Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: FbIS.IR.109 The Changeover System for the Fjernbane Infrastructure System shall support testing of - entry to ETCS area, - exit from ETCS area, where such transition interfaces exist at the borders of the Early Deployment linesDeleted. For temporary transition interface locations within Early Deployment lines, (including sub-sectioning) this need only be fulfilled if required by the testing strategyDeleted. Minimum E&W FbIS.IR.110 The Changeover System for the Fjernbane Infrastructure System shall be able to change over these element types: - point machines - locking devices (key-locks) - staff crossing signals - passenger warning systems - level crossing systems (road signals & barriers) - interfaces to conventional infrastructure (interlocking and line blocks) within the Early Deployment lines. By "be able to" it is meant that the Fjernbane Infrastructure System shall support this solution where required for the test operation. Existing - main signals, - distant signals, - shunting signals, - level crossing signals (rail) - train detection - LEUs - balises are intentionally excluded from change-over scope. New train detection is expected to be installed in parallel to the existing train detection. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 84 of 98 Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: FbIS.IR.111 The Changeover System for the Fjernbane Infrastructure System shall be able to change over these element types: - bascule bridge system within the Early Deployment lines. By "be able to" it is meant that the Fjernbane Infrastructure System shall support this solution where demanded for the test operation. Non-Minimum W FbIS.IR.112 The Changeover System for the Fjernbane Infrastructure System shall be able to switch off these element types: - main signals, - distant signals, - shunting signals, - level crossing signals (rail) within the Early Deployment lines. MostBy main"be able to" it is meant that the Fjernbane Infrastructure System shall support this solution where demanded for the test operation. Shunting signals and other "white aspect" signals need not be switched off, distantbecause they can produce a special "cancelled" signal aspect with the same purpose. Most main and shuntingdistant signals are fed from centralised interlocking rooms. Type: Area: Block signals and level crossing signals (rail) are fed from distributed cabinets. Minimum E&W Identifier: Requirement: FbIS.IR.113 Guidance: Existing point machines are often "coupled", meaning that 2 machines of a cross-over share one control circuit. This configuration is not transferable to the new systemDeleted. Minimum E&W Type: Area: The Changeover System for the Fjernbane Infrastructure System shall change over point machines / locking devices at the individual point machine / locking device cable level. This in order to become fully detached from circuits of the existing interlocking and CTC systemDeleted. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 85 of 98 Identifier: Requirement: Guidance: Type: Area: FbIS.IR.114 The Changeover System for the Fjernbane Infrastructure System shall change over barrier machines / lights at the individual barrier machine / light cable level. This in order to become fully detached from circuits of the existing level crossing systemDeleted. Minimum E&W Identifier: Requirement: FbIS.IR.115 Guidance: This does not exclude feeding state information in parallel to the existing interlocking/CTC system and the Fjernbane Infrastructure System, if feasible and safe to do soDeleted. Minimum E&W Type: Area: The Changeover System for the Fjernbane Infrastructure System shall change over staff crossing signals, passenger crossing signals and level crossing signals (road) at the individual signal cable level. This in order to become fully detached from circuits of the existing staff crossing / PWS / level crossing systemDeleted. Identifier: Requirement: FbIS.IR.116 Guidance: Type: Area: Deleted. Minimum E&W The Changeover System for the Fjernbane Infrastructure System shall change over passenger crossing loudspeakers, level crossing bells, etc. at the individual device cable level. This in order to become fully detached from circuits of the existing PWS / level crossing systemDeleted. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 86 of 98 Identifier: Requirement: FbIS.IR.117 Guidance: Type: Area: Deleted. Minimum E&W Identifier: Requirement: FbIS.IR.118 Guidance: Type: Area: The Changeover System for the Fjernbane Infrastructure System shall change over relay interfaces at the individual relay circuit level. This in order to become fully detached from circuits of the existing interlocking and line block systems (as applicable)Deleted. The Changeover System for the Fjernbane Infrastructure System shall switch off main signals, distant signals, shunt signals and level crossing signals (rail) at the individual main fuse levelDeleted. Minimum E&W Identifier: Requirement: FbIS.IR.119 Guidance: Example - existing interlocking systems: When detaching point machines, they must be re-attached in the same lie to avoid trailing being detected. Type: Area: The Changeover System for the Fjernbane Infrastructure System shall ensure proper operation of the system not in control of elements / equipment. This includes, but is not limited to: - dummy loads - command blocking - alarm blocking - specific procedures as necessary for affected sub-sections of Early Deployment lines, in order to avoid malfunction during changeover. This applies to the existing interlocking and CTC systems as well as the Fjernbane Infrastructure System. Example - new system: When detaching point machines, useless and confusing alarms should be avoided. Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 87 of 98 4.5.4 Civils Infrastructure Identifier: Requirement: Guidance: Type: Area: Identifier: Requirement: Guidance: Type: Area: Guidance: Type: Area: FbIS.IR.57 The Supplier shall at the preliminary design phase provide all signalling and communication interfacing requirements from the Fjernbane Infrastructure System to the fibreFixed transmissionTransmission networkNetwork FbIS.IR.58 The Supplier shall interface with the Building Supplier to ensure adequate space, power and trunking is provided for their equipment at the Traffic Control Centre BuildingDeleted. Minimum E&W Concurrency Identifier: Requirement: Guidance: Type: Area: The Supplier shall at the preliminary design phase provide all power supply load requirements and the rating of the highest rated fuse or circuit breaker for their equipment installed at each specific location. This is so that the Customer can provide a power supply of sufficient capacity and with the correct discrimination between fuses and circuit breakers. Minimum E&W Minimum E&W Identifier: Requirement: 4.5.5 FbIS.IR.56 FbIS.IR.135 The TMS supplier must document that the system supports concurrency when acting as the receiving part in data communication (multiple clients pushing data to the TMS and/or multiple clients pulling data from the TMS). Any derogation from this must be documented and accepted by the signaling program Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 88 of 98 4.5.6 Resiliency and robustness Identifier: Requirement: Guidance: Type: Area: 4.5.7 FbIS.IR.142 The design and associated specification and documentation of interfaces shall define precisely what constitute legal operations in each interface and any operation deviating from this shall not impair the operation or data integrity of the Fjernbane Infrastructure System in any way. The Customer wishes that interfaces of the Fjernbane Infrastructure System exhibit resilience and robustness. Modernisations in Fjernbane Infrastructure System or externally interfacing systems as well as new systems introduced externally in the future (e.g. new TOCs) do not introduce any risk to the data and operational integrity of the Fjernbane Infrastructure System. The Customer envisions a robust-by-design approach as exemplified (without exclusion of other approaches) by whitelisting of functional interface calls and precise definitions of valid parameters of data passed on the interfaces. Minimum E&W Common Interface ((This section has been deleted)) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 89 of 98 4.5.8 Data representation Identifier: Requirement: FbIS.IR.137 The Fjernbane Infrastructure System shall provide at least the following data representations State of the Railway 1. Detailed view to interact with information on the state of the railway which can be safety critical 2. Area view to interact with information on the state of the railway which can be safety critical 3. Overview of the state of the railway (with less detail) 4. Adjacent TMS: Detailed State of the railway on adjacent sections Online Production Plan 5. Train graph for status 6. Transfer connection matrix 7. Platform/Track occupancy graph 8. Advice on revised Online Production Plan 9. Adjacent TMS: Overview of incoming traffic TOC Constraints 10. TOC train data (including consist) 11. Rolling stock roster (just displaying related constraints as far as required for BDK) 12. Staff roster (just displaying related constraints as far as required for BDK) Planning 13. Train graph for planning 14. Platform graph for planning 15. Possession planning 16. Catenary isolation planning 17. Temporary Speed Restriction planning 18. Train handover to/from areas outside control System Administration 19. User administration 20. Control Room Configuration Knowledge Data 21. Rule book 22. Help 23. Detailed information about elements of the railway 24. Suggested measures (context sensitive) Service Intention 25. Service Intention (Time slice/Place) 26. Service Intention (Geographical) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 90 of 98 Alarms 27. Alarm Overview 28. Failure Management 29. Control room log (Telegrammjournalen) 30. System Diagnostics 31. SCADA/Detection systems Logon 32. Area Logon 33. Area Handover Communications 34. Telephone/GSM-R voice CCTV 35. CCTV Office Applications 36. Office applications Guidance: Type: Area: Passenger Information 37. Passenger Information device selection 38. Passenger Information management The precise content and appearance of the representations are to be agreed in the design phase Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 91 of 98 4.5.9 User Interaction Identifier: Requirement: FbIS.IR.139 The Fjernbane Infrastructure System shall provide at least the following Option for User Interaction Input Options 1. Macro/batch file edit 2. Text edit 3. Internal Message exchange 4. Short cut keys 5. Pointing input (mouse/pad/touch screen) 6. Drag & drop 7. For every entry, two input technology options shall be provided Viewing Options 8. Structured windows 9. No overlap between windows 10. Any user to customise views within constraints 11. HMI surface to be configurable for viewing anything anywhere 12. Information displayed in lists or graphics 13. Graphical Objects configurable by authorised user 14. Scrolling, Scaling, Zooming Help 15. Contextual, graphical guidance 16. Online manuals and links to tutorials Guidance: Type: Area: 4.6 Minimum E&W User–Interface Design Constraints ((The changes in this section are so substantial that the Customer has chosen not to show the change markings)) The following Requirement constrains how a user interface may evolve within the System Solution: Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 92 of 98 Identifier: Requirement: FbIS.IR.120 The Fjernbane Infrastructure System shall be designed such that only the User interfaces related to the following functions are considered to be related to safety tasks: Request Control Of Area (FbIS.F.55, FbIS.F.56, FbIS.F.68, FbIS.F.1028) Control Of Area Requested (FbIS.F.55) Acknowledge Transfer of Area of Control (FbIS.F.55) Control Of Area Taken In Emergency (FbIS.F.56) Telegramjournalen Inputs (FbIS.F.55, FbIS.F.56, FbIS.F.60, FbIS.F.61, FbIS.F.62, FbIS.F.66, FbIS.F.68, FbIS.F.98, FbIS.F.375) Telegramjournalen Outputs (FbIS.F.60, FbIS.F.61, FbIS.F.62, FbIS.F.66, FbIS.F.68, FbIS.F.98, FbIS.F.100, FbIS.F.375) Manual Routing (FbIS.F.108, FbIS.F.128, FbIS.F.146, FbIS.F.147, FbIS.F.166, FbIS.F.167, FbIS.F.170, FbIS.F.226, FbIS.F.228, FbIS.F.261, FbIS.F.262, FbIS.F.282, FbIS.F.284, FbIS.F.333, FbIS.F.334, FbIS.F.411, FbIS.F.1219) Emergency Stop Train (FbIS.F.137) Emergency Stop All Trains In Area Of Control (FbIS.F.138) Emergency Stop All Trains In Area (FbIS.F.140) Request Movement Authority Shortening (FbIS.F.153) Movement Authority Shortening (FbIS.F.153, FbIS.F.155, FbIS.F.257) Stop Automatic Route Setting (FbIS.F.156, FbIS.F.178, FbIS.F.179, FbIS.F.410) Automatic Route Setting Stopped (FbIS.F.156, FbIS.F.178, FbIS.F.179, FbIS.F.393, FbIS.F.410, FbIS.F.421, FbIS.F.1772) Block (FbIS.F.250, FbIS.F.252, FbIS.F.255, FbIS.F.332, FbIS.F.1201) Request Acknowledgement of Temporary Speed Restriction Start (FbIS.F.199) Acknowledgement of Temporary Speed Restriction Start (FbIS.F.199) Temporary Speed Restriction End (FbIS.F.200) Acknowledgement of Temporary Speed Restriction End Emergency Speed Restrictions For Approval (FbIS.F.193) Emergency Speed Restrictions Approval (FbIS.F.193) End of Emergency Speed Restriction (FbIS.F.195) Request Possession Start Approval (FbIS.F.209) Approve Possession Start (FbIS.F.210) Possession Started (FbIS.F.211, FbIS.F.212) Start Planned Possession (FbIS.F.212) Redefine Possession Inputs (FbIS.F.213) Redefine Possession Outputs (FbIS.F.213) Train Routed Into Possession Without Active Handheld Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 93 of 98 Fjernbane Infrastructure East/West Document1 Terminal Acknowledgement Request (FbIS.F.228) Swing Points (FbIS.F.230, FbIS.F.232, FbIS.F.263, FbIS.F.1748) Possession Split (FbIS.F.239) Request For Acknowledgement Of Possession Hand Back (FbIS.F.219, FbIS.F.220) Acknowledgement Of Possession Hand Back (FbIS.F.219, FbIS.F.220, FbIS.F.1149) Hand Back Possession (FbIS.F.220) Emergency Possession (FbIS.F.222) Possession Plan Inputs (FbIS.F.207) Possession Plan Outputs (FbIS.F.207) Repeated Manual Routing (FbIS.F.180) Route Without Movement Authority (FbIS.F.261) Points Manually Clamped (FbIS.F.266, FbIS.F.267, FbIS.F.1202) Points Set As Locked By Maintainer (FbIS.F.268) Request Approval Of Train Movement Into A Shunt Area As There Is No Handheld Terminal (FbIS.F.284) Approval Of Train Movement Into A Shunt Area (FbIS.F.284) Establish Predefined Temporary Shunt Area (FbIS.F.287) Establish Temporary Shunt Area (FbIS.F.288) Train Too Long For Route (FbIS.F.295, FbIS.F.432) Great Belt Bridge Closed (FbIS.F.298) Implement Planned Catenary Shut Off (FbIS.F.301) Trains Emergency Stopped By Catenary System (FbIS.F.304) Protect Private Crossing (FbIS.F.307, FbIS.F.308) Train Stalled (FbIS.F.309) Override Detector Locking (FbIS.F.320, FbIS.F.1200) Treat Level Crossing As Failed Emergency Route Release (FbIS.F.330, FbIS.F.1268, FbIS.F.1693) Release Train (FbIS.F.347) Train Has Requested MA But No MA Can Be Given. (FbIS.F.351) Train Tripped (FbIS.F.357) Unexpected Track Occupancy (FbIS.F.358) Current Area Of Control (FbIS.F.365) Request Temporary Shunt Area Authorisation (FbIS.F.289, FbIS.F.290) Grant Temporary Shunt Area Authorisation (FbIS.F.289, FbIS.F.290) Edit Train Data Inputs (FbIS.F.392) Edit Train Data Outputs (FbIS.F.392) Request Acknowledge Manual Routing Against Restrictions (FbIS.F.394, FbIS.F.416, FbIS.F.427, FbIS.F.434, FbIS.F.435, FbIS.F.455) Acknowledge Manual Routing Against Restrictions (FbIS.F.394, FbIS.F.416, FbIS.F.427, FbIS.F.434, BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 94 of 98 FbIS.F.435, FbIS.F.455) Unexpected Train Number (FbIS.F.396) Partially Cancel Trains in Online Timetable (FbIS.F.399) Emergency Stop All Trains Near Another Train (FbIS.F.406) Emergency Stop (FbIS.F.137, FbIS.F.138, FbIS.F.140, FbIS.F.406, FbIS.F.1769) Request Shunt Route Acknowledgement (FbIS.F.412) Shunt Route Acknowledgement (FbIS.F.412) Reopen Bridge/Tunnel (FbIS.F.422) One Train In Tunnel Bore (FbIS.F.431) Planned Catenary Shut Off Implemented (FbIS.F.301, FbIS.F.437, FbIS.F.438) Revoke Planned Catenary Shut Off (FbIS.F.437) Bridge Release Request (FbIS.F.440) Bridge Release Request (FbIS.F.441) Bridge Released (FbIS.F.441, FbIS.F.442) Train Cannot Be Routed According to Online Timetable (FbIS.F.447) Train Routed Into Possession Without Active Handheld Terminal Acknowledgement (FbIS.F.228) Handheld Terminal Unavailable for Remainder of Possession (FbIS.F.457) Point Swing In Possession or Shunt Area Without Active Handheld Terminal Acknowledgement Request (FbIS.F.232, FbIS.F.1748) Point Swing In Possession Without Active Handheld Terminal Acknowledgement (FbIS.F.232, FbIS.F.1748) Reset Axle Counter (FbIS.F.337) Manual Level Crossing Control (FbIS.F.1165) Text Message Definition (FbIS.F.75) Guidance: Note that the final list of safety relevant interfaces is to be updated upon a renewed harzard analysis. If the proposed solution invokes additions to or removals from the list these changes are to be agreed during the design phase. Type: Area: Minimum E&W Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 95 of 98 5 Internal Interfaces – BDK Owned There are interfaces that allthough they are internal to the System solution provided by the Supplier, the Customer requires to have comprehensive documented information about – in order to support the independent right to use the interface as well as, if BDK so wishes, to disclose to other parties. 6 For a list of these interfaces please refer to Requirement R16.055 from Appendix 16. Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 96 of 98 6 References Ref. no. 1 2 3 4 5 6 7 Ref. ID SP-12-021350-103.023 – Appendix 3.2 Attachment 3. (Traffic Management System Concept). SP-12-021353-103.021 Appendix 3.2 Attachment 1. (SP-15-010521 Fjernbane Operational Concept) SP-12-021370-102.000 Appendix 2 (Customer’s Environment) SP-12-018420-103.010 Appendix 3.1 (Delivery Description) SP-12-022574-103.017 Appendix 3.1, Attachment 7 (Depots and Stabling Tracks East) SP-12-022575-103.018 Appendix 3.1, Attachment 8 (Depots and Stabling Tracks East) SP-12-021337-103.032 Appendix 3.3, Attachment 2 (List BDK Standards and Codes) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 97 of 98 7 Attachments Att. no. 1 2 3 4 5 Att. ID Transition zones to the S-bane. Fjernbane Transition Zones. Interfaces to Legacy Interlockings. Interface between Denmark and Sweden. SP-12-027897-103.055 App 3.5 Attachment 5 (Interface DK – DE) Fjernbane Infrastructure East/West Document1 BAFO Tender Document Version 4.0 Appendix 3.5 – Interface Requirements Page 98 of 98