Project/Service

A. General Information

1. Title

ORFEUS (Open Railway Freight EDI User System)- European electronic information exchange system for railway freight

2. Status of the project/service
Operating
3. Implementation period of the project/service:
From
2016
To
--
5. Geographical coverage
Regional: Europe
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
RailData (special group of International groups of Railways) which develops and runs IT services for European rail freight undertakings.
Other participating agencies/entities
--
b. Operational stage
Lead agencies/entities (op)
RailData (special group of International groups of Railways) which develops and runs IT services for European rail freight undertakings.
Other participating agencies/entities (op)
--
7. Main stakeholders/beneficiaries of the project/services
Customs
Railway operators
8. Business process category of the project/service
Regulatory/official control

B. Lessons Learned

9. Summary description of the project/service
a. Objective(s)

ORFEUS is an information system developed and operated by Raildata, for development and production of central information and data exchange systems for European rail freight transport. ORFEUS system provides exchange of CIM consignment notes and CUV wagon notes data between railway operators using a Central Data System (CDS).

ORFEUS Components:

• Central part CDS (Central Data-management System). It acts as a message broker for collection and distribution of information, including specific logic and verifications.

• National Information Systems (NISes) of connected railway operators.

The ORFEUS technology is used by railway companies in Czech Republic, Luxembourg, Sweden, Croatia, Austria, Germany, Denmark, Netherlands, Spain, Switzerland, Belgium, France, Italy.

b. Business need for the project/service (background)

The need for railways to restructure their technological and management practices to respond to market demand for highly reliable and flexible freight transportation services.

Efficientdata exchange with authorities (customs).

c. Business process covered*

Railway Undertakings send data content of the consignment/wagon notes to ORFEUS, which distributes these data to other carriers involved in the transport. The CIM/CUV notes in paper form exist and accompany the wagons still.
ELECTRONIC NOTES

Data Exchange is performed as above, but the data fulfil the role of the Electronic Consignment Note (ECN). There is no paper note issued nor transported anymore.

d. Overall architecture and functionalities*

5

e. Relevant document/figure
--
10. Documents and data exchanged via the project/service

CIM consignment notes and CUV wagon notes

11. Data models/databases, proprietary solutions, hybrid approaches
--
12. Main challenges faced during the project/service

Incompatibility of data standards

Challenges related to electronic exchange between railways and customs.

Incompatibility of codification of goods.

13. Lessons learned from the project/service
--
14. Main benefit(s) of the project/service
Enhanced regulatory compliance*
Transaction Cost savings*
Simplified process
14A. Elaborations/detailed description on benefits gained:

-Single communication system for all business cases an operator can find

• Improved communication and process coordination between railway operators and infrastructure managers (in terms of quality and speed)

• Single standardized way of working, providing cost savings through better management quality system; establishment of homogeneous procedures; reduction in system maintenance costs

• Standardized and interoperable communication interface

15. Technical/financial/capacity building/other assistance
--
16. Future plan for expansion of the project and service

Solve the shortcomings identified during the project implementation

Using new TAF location code structures

Simplifies integrity and acceptance rules for processing of received messages.

Adds new customs procedures codes of the CIM consignment note.

17. Other information or relevant references on the project and service

Electronic Information Exchange System for Railway Freight.pdf (unescap.org)

18. Relevant document regarding the project/service
--

C. Relevant Standards

20. Electronic message standard
20A. Electronic message standard supporting the project/service:
EDI:
- UNEDIFACT
20B. Type of standard for electronic message applied for the project/service
Proprietary solution
Please refer to:https://www.unescap.org/sites/default/files/Electronic%20Information%20Exchange%20System%20for%20Railway%20Freig
 
Proprietary solution was applied because:
- No relevant international standard
21. Technical communication standard
21A. Technical communication standard supporting the project/service
N/A
21B. Type of technical communication standard applied for the project/service
--
22. Security-related standards*
22A. Security-related standard supporting the project/service
--
22B. Type of security-related standard applied for the project/service
--
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
--
23B. Other technical implementation information
--