Popular industry terms frequently lose their exact definitions over time. Specific, niche technical concepts are often hijacked or coined by software providers to fit their own use cases, creating widespread confusion. Our new ‘frequently asked questions’ series tackles these issues. We spoke to our experts and addressed common misunderstandings to provide clear, actionable insights.

In this blog, we will clarify the critical relationships between Object Type Libraries (OTL), and Systems Engineering (SE) tools. 

If you’d like to read this article in Dutch, you can find it here!

Part two of this blog post will be shared next month. Make sure you keep an eye on our LinkedIn when we share it!

What is an OTL intended for?

An Object type Library is best explained as an agreement for data exchange, but the term is used indiscriminately for other purposes.

In the Netherlands, the term OTL primarily refers to a library of asset types that describes the exchange of data between multiple parties across various phases of an asset’s lifecycle. Such an OTL serves as a common denominator for exchanging data between different organizations and/or software systems.

The Object Type Library (OTL) is a Dutch concept originating from the infrastructure sector. In the (rest of the) world, an OTL is called a Reference Data Library (RDL) and functions as a classification system: for each ‘object type’, it is indicated which data regarding a designed or built system must be recorded and exchanged.

In Systems Engineering, we distinguish between ‘OTLs’ used as dictionaries and thesauri, manufacturer catalogs, and libraries for geometric descriptions (CAD), geographic (GIS), and more. And all of this in many different formats. OTLs for Systems Engineering are as diverse as their intended use.

Want to know more? See ‘Toward Mature Object Type Libraries’.

Is an Object Type Library intended for the reuse of information in Systems Engineering?

The primary use of an OTL in Systems Engineering is not just information reuse. An OTL serves as a collection of object types (the ‘much broader definition’ of OTL) that can be used repeatedly in projects when there is a lot of repetition. An example is an ‘OTL’ in which object types are divided in a standardized way (system decomposition).

In Systems Engineering, we distinguish between standard divisions of systems into subsystems and aspect systems, in terms of form, operation (functions), and abstraction (logical and physical), depending on the intended use and level of aggregation of a system. Semmtech trains modelers in creating OTLs for various uses and in various applications.

In Summary

There is no such thing as ‘the’ or ‘one’ OTL. Each use imposes different conditions on the structure of an OTL. This applies to both end users and software.

Here are key takeaways!

• An OTL defines how data is exchanged between parties or systems.
• In Systems Engineering, OTLs can support repeated use of standardized object types but are not primarily intended for reuse.
• Data should be published in an application-neutral form for flexible use. 

Come back next time, when we will answer: ‘What is the relationship between an OTL and a requirements library?’

For more information, reach out to us!