Try out our Laces apps Laces Suite

Time saved using a reference data library

Time saved by using a Reference Data Library


  • Case study
2 minutes

As a grid operator, our client is responsible for a high-voltage network. In the role of the purchaser, you have to deal with various chain partners. We exchange data with all these partners for the construction, expansion, and maintenance of the high-voltage grid. Read how making integral agreements regarding data exchange by using a Reference Data Library, can lead to significant time savings.

Making information usable for humans and computers

To exchange information, it is essential to agree on what something means, its function, and what it consists of. Simple example: what is an electrical cable (a textual definition), what properties does it have (thickness, length, type of material, et cetera), and in what units do we enter it (meters, centimeters, copper, silver, etc.)? If you determine this in an unambiguous way, then all parties in the value chain know what information you need to exchange in what way. This allows humans and computers to apply this information directly to their environments. 

As you can imagine, using these unambiguous conventions is a good idea – especially with large amounts of complex data. 

Reference data Library image

Laces Reference Data Library

Our client is increasingly working with central data, capturing it in a Reference Data Library (RDL). They share and use this centrally captured information across all projects. The major advantage: the meaning and structure of information are known to everyone. This applies to internal employees and the external companies and specialists involved in these projects.

The result: a lot of time saved searching for and exchanging data. The uniformity and high quality of the data greatly reduce the likelihood of errors when using the information.

 “Engineers only spend 30% of their time applying knowledge; the rest is spent searching for information. This is something we want to change”. Gertjan van Drunen, Consultant Energy at Arcadis

Our client is working with consultants from Arcadis and Semmtech, among others, to set up and use a Reference Data Library.

So what makes Laces Reference Data Library so suitable for this?

It is possible to record information unambiguously. Assets, for example, and make it suitable for exchange in various tools. Laces, however, is unique in its accessibility regarding use. Domain experts entering data can immediately exchange it between applications without the need for intervention from data and IT specialists. Laces is also unique in its use of open standards. This makes applying data in any application much easier. 

More detail …

Laces allows to structure and exchange information according to Linked Data standards. Linked Data provides methods and techniques but still leaves the application in different sectors free. NTA 8035 / NEN2660 (Part II) describes the application of Linked Data in the built environment using basic concepts such as physical objects, activity, and events.

Using these standards, Laces allows our client to capture and exchange agreements about meaning in a standardized way. This is done in a Reference Data Library and based on existing electrical engineerings standards, such as IEC/ISO 81346 and IEC 61355-1*.

Our client’s asset requirements are defined in an SPL (Specification Library). With this, Laces makes managing and sharing according to standards for Linked Data easily.

By standardizing and sharing meaning and requirements, there is a solid basis for information exchange between our client and chain partners.

*Explanation of the two electronic standards mentioned:

  • IEC/ISO 81346 (Industrial systems, installations and equipment, and industrial products – structuring principles and reference designations). This standard was used as the basis for the physical object’s structure.
  • IEC 61355-1 (Classification and designation of documents for plants, systems, and equipment). This standard was used as the basis for the document types.
Want to know more? Schedule a 45-minute demo.

Read more
Whitepaper

Case study – Requirements Management for Civil Engineering

Have you ever wondered how you can improve your requirements management process? This white paper is for all Project managers, Tender managers, Requirements managers, Technical managers, or Design engineers who want to know more about: Find out more about how you can structure requirements management and drive value and efficiency. You will also see some […]

Read
Insight
model based approach with laces

Smarter requirements for MBSE [5 steps to a model-based approach]

Systems Engineering is a multidisciplinary and integrative management approach to system development. When we add formal (digital) representations of a system to the approach, we talk about Model-Based Systems Engineering (MBSE). These digital models are made of structured data, preferably interchangeable between software. Although the term model focuses mostly on geometric data and data for […]

Read
Insight

Why to use Laces for Publishing Data

With the infinite number of ways that professional content—such as product information, company standards, metadata, and classification systems—is used today, you need to take control by becoming publishers of high-quality data. It needs to be structured, easily accessible, and reusable by both people and machines. After all, like it or not, professionals are judged not […]

Read