ProRail object types as the foundation One language for design and management Attributes per object type

Custom OTL Spoor integration

The OTL Spoor is ProRail's Object Type Library: a library of rail infrastructure object types, with their definitions, attributes and relationships. Anyone can consult the OTL without an account. Appfront builds the integration that uses those object types in your own design, BIM or asset software, so that objects have the same name, the same attributes and the same structure as at ProRail from the design stage onwards.

What is an OTL Spoor integration?

An OTL Spoor integration ensures that the objects in your software are classified according to ProRail's object types. According to Spoordata, ProRail's information platform, the purpose of an Object Type Library is to make unambiguous definitions of real-world concepts centrally available, both within and outside a company. Such a concept is called an object type. For each object type, the OTL records the definition, the attributes and the relationships with other object types, as well as document types and value types. These definitions are intended for the entire life cycle of an object: concept, design, realisation, use, maintenance and demolition.

An OTL describes which object types exist, but contains no information about individual objects. You will find the description of a viaduct, but not the data of a specific viaduct. According to ProRail, no account is needed to consult the OTL; access is only required to submit change requests (RFCs). ProRail lists contractors, engineering and consultancy firms for rail infrastructure, asset suppliers, surveying companies and ICT partners among its users. ProRail also has its own facilities for the objects themselves, such as the ProRail Unique Identification Code (PUIC), which links the keys from different source systems for each infrastructure object. Authorisation is required for this.

We build custom integrations because the object types only become valuable once your own software uses them. A design package, a BIM model or a management system has its own object kinds and its own attribute names. The integration maps those onto the OTL, classifies your objects according to ProRail's object types, checks that the attributes belonging to a type have been filled in and shows what changes when the OTL gets a new version. Which submission you make to ProRail, and through which facility, we establish with you in the first step; the integration prepares the data for it.

One language

ProRail object types.

Full

Attributes checked per type.

Up to date

New versions visible.

How we build your OTL Spoor integration

We start with your software and your role: do you create designs, build or maintain, or supply assets, which object types do you currently use and what data do you supply to ProRail. Next, we compare your object types and properties against the OTL and show where they match and where they don't. We first build the typing and checking for one group of objects, such as switches or structures, and let your specialists review the outcome. Other object groups and the preparation of deliveries follow once that works well. After that, we keep the integration up to date whenever the OTL gets a new version.

1
Mapping your role

Software, objects, deliveries.

2
Comparing

Your object types alongside the OTL.

3
First object group

Typed and checked.

4
Go-live and maintenance

Go-live, monitoring and maintenance per OTL version.

What an OTL Spoor integration actually does

The components below feature in almost every OTL Spoor integration. Which ones you need depends on your role in the rail sector and on the software your objects are held in.

Object types

Imported from the OTL.

Typing

Your objects according to the OTL.

Attributes

Mandatory fields checked.

Contacts

Objects linked together.

Versions

Changes made visible.

Log

Every change traceable.

Who we build an OTL Spoor integration for

The integration is intended for parties that create or manage object data for the rail infrastructure and currently work with their own names and separate translation tables. The more objects and projects you have, the more it delivers.

Contractors

Handover according to the OTL.

Engineering firms

Designing with the same types.

Asset suppliers

Products linked to object types.

ICT partners

The OTL in your software package.

Technology and integrations

This page is about using the object types from the OTL Spoor in your own software. If you are building a broader system for models and designs, see our page on BIM software; for managing objects over their lifespan there is asset management software, and for civil engineering and infrastructure projects civil engineering and infrastructure software. If you are an engineering or consultancy firm, also see software for engineering firms. You can read about our approach at custom software development.

OTL Spoor Rail data Object types and properties PUIC RDF and SKOS BIM models Design and management software Version comparison Roles and permissions Log

Why Appfront for your OTL Spoor integration?

A design in which the same object has three names, a handover that is sent back because properties are missing, or a translation table that only one employee understands costs time in every project and produces asset data that nobody trusts. That is what we build on: ProRail's object types as a fixed foundation, checks before data leaves your organisation and a log in which you can see what has changed.

Unambiguous

The same types as ProRail.

Full

Missing properties spotted.

Kept up to date

Keeps pace with new versions.

Security and privacy in an OTL Spoor integration

The OTL itself is public, but the object data in your software usually is not: it concerns infrastructure and projects, and may be confidential under your contract with ProRail. The integration uses the OTL as a reference, keeps your object data in your own environment and records every change with time and user. Personal data is rarely needed for this; where it does appear, such as with users and project members, the GDPR applies.

The integration runs in a European data centre, with encrypted connections and storage. Accounts and keys for ProRail services that require authorisation are kept secured and are not visible to staff. We agree with you in advance who may type objects and who may release a delivery.

Frequently asked questions about an OTL Spoor integration

Questions that contractors, engineering firms and ICT partners in the rail sector ask before they get started.

ProRail's Object Type Library: a library containing ProRail's object structure. It holds unambiguous definitions of object types in the rail infrastructure, with their attributes and relationships, as well as document types and value types.

No. According to ProRail, you don't need an account to consult the OTL. If you want to submit a change request (an RFC), you do need access.

No. An OTL describes which object types exist, but contains no information about individual objects. You'll find the description of an object type such as a viaduct, not the data of a specific viaduct. That data is held in your own systems and in ProRail's systems.

The OTL describes object types. The PUIC, the ProRail Unique Identification Code, is a unique number for an individual infrastructure object, used to link that object's keys across different source systems. Using the PUIC requires authorisation.

To give your objects the same types, attributes and relationships as ProRail uses. That way design, construction, handover and maintenance fit together, and nobody has to maintain a translation table for every delivery.

BIM software is a complete system for models and designs. An OTL Spoor integration is one component of it: making sure the objects in that system are classified according to ProRail's object types and carry the correct attributes. This integration can be built into existing software.

For organisations that regularly create, manage or hand over object data for ProRail, and for IT partners who build software for the railways. If you only occasionally work on a small project, consulting the OTL is often enough.

Your objects according to the OTL Spoor?

Tell us which software your objects are stored in and what data you deliver to ProRail. We'll show you how an integration classifies them according to the OTL.

Edit content