RDS/WIP: An Introduction

This page is written to hopefully introduce the uninitiated to what the IDS-ADI team call the RDS/WIP.

What the RDS/WIP Stands for

The RDS/WIP stands for "Reference Data System" and "Work in Progress", essentially combining the PCA IDS project's original reference data library system with the FIATECH ADI project's reference data library system, and using much of the ground work laid out in the drafts of ISO 15926 part 7.

What the RDS/WIP is

The RDS/WIP is several things:

• a library of reference data for ISO 15926
• a means of publishing core ISO 15926 definitions
• a platform for developing new ISO 15926 definitions
• a workspace for harmonizing other standards with ISO 15926 (or each other)

Why Reference Data is Needed

ISO 15926's brief is to act as a interoperability framework for engineering data.

The Same Data Suited to Many Different Tasks

The standard needs to accommodate typical activities related to that data. The breadth of these activities is very wide - the data must pass through design, procurement, installation, operations, maintenance and planning activities.

As the data passes between systems used in these different activities, it must retain its fidelity and precision, and still be meaningful and task-oriented to the users. That is to say, that the best way to present data for one task might be quite different to the best way for another task, and a standard must accomodate this.

Making Data Precise and Neutral

ISO 15926 data is built from a rigid, onotological-style data model - this comprises many small pieces of information used to build up the complex relationships of real-life data.

Using very small pieces of information (what we call "binary relationships") allows extremely precise expressions, but those small pieces of information are not intelligible to users of the data - information systems are typically built at a much coarser level that reflect the way their users think of the data. The way a user thinks of their data is usually task-specific, not a neutral form of the data suitable for other tasks.

Making Data Concise and Meaningful

So this brings any interoperability standard to the problem of how to make the data neutral, but at the same time concise and meaningful. The approach that ISO 15926 takes is to find the repeating patterns of small pieces of information that are useful in many contexts, identify how those clusters relate to the rest of the data, and to wrap up each cluster into a larger unit.

Once repeating patterns have been identified and named, they can be re-used without having to remember how they look "inside" - a user can just take the named pattern and use that, plugging values into the external relations only.

This process can be repeated, taking the larger patterns of identified patterns and building up even bigger repeating chunks. By repeating this process we ultimately reach data at the level of meaning that humans are used to dealing with, such as "the average energy use of the pump identified by tag TF1034 in this installation is 4kW".

Making Useful Patterns of Data into Reference Data

It is much better if multiple parties can re-use the general pattern "the average energy use of <installed-equipment-specification> is <energy-value>" to exchange data, rather having to pass around many tiny pieces of information that fit that pattern.

This is the reason why the RDS/WIP exists, to register and define these patterns, so that people from different companies can exchange concise, meaningful data, without having to understand the complex details of how it is made up.

It is analagous to saying "this is a blue sapphire" versus saying something like "this is an occlusion free crystal in a trigonal Bravais lattice, made of a compound of two aluminium atoms in a valence bond with three oxygen atoms; with an admixture of trace iron contaminants".

How Contribution and Standardization Will Work

TBD

What the RDS/WIP Is Built of

TBD