Common Central Repository (CCR)

The Common Central Repository is the reference point where the Agency publishes the data that all telematics stakeholders need in order to share data under the Telematics TSI: the semantics of the data, the trust anchors used to secure it, the codes used to identify organisations and places, and the entry points to the reference data managed by the sector.

What the repository contains

Article 8(1) of the Telematics TSI requires the repository to store four categories of information. Each category is expanded in the sections below.

Dates and deadlines

Application of the repository obligations (Article 27)

Deployment milestones for reference data (Appendix G)

Points 1.3 (cybersecurity) and 1.4 (data presentation) carry no separate milestone in Appendix G. They are cross-cutting requirements and apply through the milestone of each function whose data is shared.

Under Article 16, any new telematics application deployed after entry into force must comply immediately; existing applications follow the Appendix G milestones so that they comply in relation to the working timetable for 2030, which applies from 9 December 2029. 

Operators of rail freight service facilities have an additional transitional period of 12 months, and the deadlines may be extended by 12 months where compliance would compromise the viability of putting a subsystem into service.
 

(a) Metadata and data catalogue elements

The Agency ensures semantic versioning of the ERA Ontology and guarantees that it remains compatible with, and includes as subsets, the data catalogue elements listed below. Data, objects and messages shared under the Regulation must be serialised in a format that complies with these subsets. The repository must hold this information from 2 September 2026.

(b) List of PKI certification authorities

Each telematics stakeholder must use a public key infrastructure in accordance with the referenced specifications, alongside cybersecurity risk-management measures under Directives (EU) 2022/2555 and (EU) 2022/2557 and TCP/IP communication protocols. The repository publishes the list of the certification authorities established for that purpose. This is the one Article 8(1) category that applies later than the others: the obligation runs from 2 March 2027.

(c) Common reference data managed by the Agency

The Agency manages and assigns single reference identifiers (‘codes’) used by telematics stakeholders to identify entities, geographical points and ticketing aspects. That function has applied since 15 March 2026 under Article 9(3) to (6); publication through the repository applies from 2 September 2026. Requests are submitted through the Agency's web applications from 2 March 2027, and through the transitional arrangement in Article 26 until then - see Requesting a code.

Organisation and location codes

Common code lists for rail ticketing

The Agency manages the following common code lists for rail ticketing as common reference data, in accordance with the specifications referenced under index [105]. They form part of the repository from 2 September 2026; the corresponding deployment milestone for stakeholders is 10 December 2028.

(d) Link to freight-specific reference data

Freight-specific reference data is not stored in the repository. It is managed by the rail sector in standardised and federated databases, and the repository holds the link to access its source from 2 September 2026. The stakeholders responsible manage assignment, maintenance, storage and access in a transparent, fair, reasonable and non-discriminatory manner, and apply the same data quality requirements.

Using the repository

Notifications

We are working on a feature that will allow stakeholders to subscribe to automated notifications of any update to the information associated with the repository. We thank you for your patience.

Replication

A telematics stakeholder may replicate the data available in the repository for its own operational use. Replicated data must preserve the same quality level as the source.

Data quality

Reference data published through the repository is subject to the five data quality criteria of the Telematics TSI - accuracy, completeness, consistency, timeliness and uniqueness - with a nominal accuracy of 100 % and a tolerance margin of 5 % for each criterion. Deficiencies identified in quality assurance checks must be corrected as soon as possible.

Requesting a code

From 2 March 2027, the Agency provides web applications through which telematics stakeholders submit requests for the assignment of codes and for updating the associated data elements, together with a user manual describing their functions. The procedures and deadlines for handling requests, including the language arrangements under Article 74 of Regulation (EU) 2016/796, are published from 2 September 2026.

Until the web applications are available, codes are assigned through the existing databases managed jointly by infrastructure managers, by operators of rail freight service facilities or by groups of railway undertakings (Article 26).

• Request an organisation code
• Request a location code _{[Available from 2.3.2027]} 
• Transitional route for location code requests _{[Via RNE tools]}
• Procedure for the assignment of organisation codes (under ERA-TD-103)