
R2P = RU-RU Partner Communication
Replacement of the part of the communication between railway undertakings, managed in the past by SBB Infrastructure, by gateways and interfaces extending the TAF/TAP TSI Standard in the context of the introduction of TMS.
Overview
R2P basically covers the communication between railway undertakings (RU) in the context of the TAF/TAP TSI Standard

Expectations
Interoperability
- openess: business and technical concept as well as specifications are freely available
- separation of logical and technical model allows different technical implementations
- adapter and gateway functions translate between various implementations
- modular approach enables acceptance and spread through step-by-step introduction
- scalability for small, medium and large enterprises
Sustainability
- future oriented approach
- expandable
- scalable
Architecture
The concept and the architecture consider the elements of the TAF/TAP TSI Standards but go beyond.
The concept considers
- the Identification
- the Objects
- the Data Elements
- the Master Data
R2P is based on modules and consists of four major elements:
- Interfaces
- Web-Interface
- Gateway to TAF-compatible world
- Administration module

Roadmap
R2P Release 1
Release 1 of R2P introduces the basic elements of R2P and allow the cooperation between RUs and their partners.
It provides the following objects:
- the Reference Train Object
- the Train Object
- the Route Object
- the Service Object
R2P Subsequent Releases
Subsequent releases of R2P introduce further objects like
- Load
- Shipment