Annex 3: Traffic data to the railway undertaking

1 Introduction

Traffic data and other information in connection with train operation pursuant to this annx are data that are linked to the railway undertaking's operational operation of trains and which Bane NOR must deliver to the railway undertaking. Bane NOR shall deliver such data to the railway undertaking so that the railway undertaking can operate trains in accordance with the route charter. In the event of deviations, Bane NOR shall deliver in such a way that the railway undertaking can resume normal operations in accordance with the route as soon as possible.

Traffic data and other information pursuant to this annex also include data in Bane NOR's possession and which the railway undertaking shall use further in relation to its customers or as a basis for its information to its customers, and Bane NOR shall deliver such data to the railway undertaking.

1.2 Contact points for mercantile matters

Enquiries about delivery, data type, etc. should be directed to Customer and Passenger Traffic: marked@banenor.no

Changes in the way traffic data and other information are exchanged are regulated in Section 16.4, third paragraph, of the AST.

2 Service Descriptions

Bane NOR offers external users the opportunity to use parts of the content for traffic information on the website. This means that information about train traffic can be made available in external services without paying for this. This is data that shows timetables and real-time information about train traffic. Possibilities to receive open data over the internet or as downloadable files.

Detailed descriptions on banenor.no.

Table 1 SIRI real-time data

* Train position is given as passing time (with approx. +/- 5 seconds uncertainty) at defined points in the infrastructure (e.g.: station entry/exit signal, block post, siding signal, etc.).

Real-time information includes actual arrival and departure times at relevant stations. Real-time information also includes information about train cancellations at stations or routes. Format: SIRI 2.0/Proprietary XML. Description is available on request.

2.2 Route information and TIOS

2.2.1 Access to data in the TIOS Web application

Bane NOR will make data from the TIOS database available to the railway undertaking on-line via the TIOS Web Application.

Access meets the following criteria:

1. Scheduled and actual arrival and departure data data: All data for all trains at all stations shall be displayed immediately.
2. Data regarding reason codes: All reason codes for all trains at all stations must be displayed immediately as they are available in the TIOS database at the time of on-line lookup.
3. Event Log Message Data: All messages with all content received from the Event Log to TIO shall be displayed immediately as they are in the TIOS database at the time of on-line lookup and as the Access Control and Web Modules provide.

2.2.2 Cause codes, arrival and departure times, and HL messages via WebSphere MQ

Bane NOR shall send data from the TIOS database to the railway undertaking via WebSphere MQ, which meets the following criteria:

1. Scheduled and actual arrival and departure time data: All data for all trains at all stations must be sent immediately.
2. Reason code data: All reason codes for all trains at all stations must be sent after three working days.
3. Event Log Message Data: All messages with all content received from the Event Log to TIOS should be sent immediately. Specifications are sent on request.

Table 2 shows which data must be submitted.

Table 2: Data from Bane NOR: Timetable and real-time data

TogID is a unique identifier for trains that run in accordance with the Norwegian timetable within the relevant timetable.

Format: RailML 2.2
A description is sent on request.
Reference: railML.org(opens in a new tab)

Timetable information is timetables for the train in question in accordance with the Norwegian timetable within the relevant route period.
Format: RailML 2.2, also in format: CSV-file.
A description is sent on request.
Reference: railML.org(opens in a new tab)

2.3 Terminal Operating System TOS

Traffic data from Bane NOR relating to the carriage of goods. This section only applies to railway undertakings that transport goods on Bane NOR's railway network and that use Bane NOR's intermodal freight terminals.

In order to receive status messages from Bane NOR's TOS, the railway undertaking must have established a user interface for receiving XML data, as well as have submitted data to the TOS as specified in Appendix 2.

Table 3: Data from Bane NOR: Freight of goods; data to the railway undertaking from Bane NOR's TOS

2.4 FIDO

FIDO FIDOBane NOR's electronic system for distribution of routes and other announcements is Bane NOR's distribution system for information regarding train operation, shunting and work on tracks.

The system consists of a registration module for the train controller and operational route planner, as well as a distribution module for receivers.

FIDO has three different public APs, available as a REST API:

• Announcements. All announcements received from the timetable system. Results of queries are sent as Base64 encoded RailML.
• Routes. Results on queries are sent as Base64 encoded RailML, wrapped in Json.
• Attendance, for the types of announcements: Creation of construction site and Allocation of line section/station for work. Results of queries are sent as Json format.

Specifications are sent on request.

2.5 The Customer portal and DRAGE

2.5.1 Manual access to data in DRAGE

Bane NOR shall make data from the data warehouse DRAGE's database available to the railway undertaking on-line via the Customer Portal, which meets the following criteria:

1. Data on planned and actual arrival and departure times for the company's own trains at all stations.
2. Data on reason codes. Data is shown to the company after three working days. This data is shown: All reason codes for own trains, (i.e. reason codes (81-85) that are linked to specific train numbers belonging to the enterprise. All reason codes related to Bane NOR and external conditions (Codes 1-7 and 9).

2.5.2 Bane NOR's customer portal

On Bane NOR's customer portal , you can access to signed agreements, invoices, reported cases, minutes of meetings, ordered services, complaints about reason codes and links to tools and systems in Bane NOR.

2.6 Infrastructure data – Route description and route

The route description for the railway network contains an overview of the railway lines, and is an encyclopedia with information for operational staff. It describes the individual line sections, instructions for the operation of technical equipment, special provisions, special conditions, etc.

TRASÉ (traffic-related line section information) provides access to information about the infrastructure that is relevant for traffic purposes.

2.7 Capacity Planning – BEST

Systems for ordering track access.

2.7.1 BEST-L for booking capacity for next year's schedule;

BEST-L BEST-LBane NOR's elektronic system for infrastructure capacity application (routes) in the yearly capacity allocation process. is Bane NOR's application portal for the railway undertakings' applications for routes in the annual capacity allocation capacity allocationA collective term referring to the infrastructure manager's planning and allocation of infrastructure capacity as well as access to service facilities and the services in these. process. Responsibility for the execution of the process has been assigned to the Traffic Division, Timetable in Bane NOR.

The principles of the capacity allocation process remain unchanged, cf. the description in the Network Statement.

2.7.2 BEST-K for ordering capacity within the long-term plan

BEST-K BEST-KBane NOR's electronic system for infratsructure capacity application (routes and work on tracks) in the current timetable period (operative capacity allocation). is a booking portal for applications for short-term track access, normally in the current route period.

It can be used to apply for routes for extra trains, cancellation of trains, routes for work trains and disposition with work trains, disposition for work – including construction area – railways as well as cancellations/cancellations of work/work trains.

2.8 Digital payment service for parking a car (Parking app)

This section only applies to railway undertakings that are to offer Bane NOR's digital parking solution. The application service is based on the "Digital Permit" Agent Access API.

2.9 ARBIS – Working in tracks

This section applies to railway undertakings that wish to retrieve data on infrastructure works to display in their interfaces. Tools to see up-to-date information, have a better user interface, and easier accessibility of planned infrastructure works. Retrieval of data directly from ARBIS ARBISBane NOR's electronic overview of railway technical planning requirements. tools will provide a better overview by making the activities for infrastructure works available at railway undertakings.

Specifications are sent on request.

3 Quality of service

3.1 Availability and deviation management for SIRI Real-time information

3.1.1 Availability

Service uptime: 99.5%

Operating hours for the services are 24/7, 365 days a year.

3.1.2 Error categories

Table 4: Error codes

Table 5: Service level for fault categories

3.1.3 Deviation management

Enquiry for reporting errors to the National Operations Center (NOS).

The following procedure is followed:

• The fault should be reported to opm.brukerstotte@banenor.no or tel.: 73 41 01 10 Availability: 24 hours/365 days a year.
• When the case is registered, the notifier will receive a reference number as a receipt for the case. This number will be used as a reference and will be used in further dialogue for handling the case.

3.2 Availability and deviation management for other services

3.2.1 Service level

Table 6: Service opening hours and availability

Table 7: Service level for the services in the agreement

*TIOS' operating platform is delivered at service level B

Table 8: Error categories

Table 9: Service level for the fault categories