Version 2 (modified by gordonrachar, 15 years ago)


ISO 15926 Tutorials

Status of this document: Working Draft

This document is open for feedback, please post questions and comments in the forum at the bottom of this page. You will need a login to post in the forum.


  1. Mapping to ISO 15926 Part 4 Using the RDS/WIP
    1. Scenario
    2. Practice Files
    3. Creating a Mapping Spreadsheet
  2. Using Templates
  3. Something Else

Mapping to ISO 15926 Part 4 Using the RDS/WIP

Mapping databases together is the entry level for using ISO 15926. The basic task is to examine each attribute to determine what it means, then find the appropriate class in the RDS/WIP, which is ISO 15926 part 4 (15926-4).

Benefits of using ISO 15926-4:

  • It's already there. (Creating a taxonomy of terms for something as complex as a petrochemical plant or refinery is not trivial.)
  • It's there next time too. (You don't have to keep reinvent it next time. Re-use is easier every time you use it.)
  • Other use it too. (When you share information with a partner that has used ISO 15926-4 before, the infrastructure is already in place. Both of you will have less adjusting to do.)


In this scenario we will imagine an owner, an engineer, and a constructor exchanging information. The owner wants early information about each pipe line to populate its line list, the engineer is designing the plant with a 3D design tool, and the constructor wants to feed the piping components to a purchasing application. Each tool has its own database. It is your job to map the information to common ISO 15926-4 classes.

Each participant requires two tables, one for pipe lines and one for valves.

Practice Files

The first step is to get a description of the dtabase columns involved in the exchange. In our example, we will assume that a database adiministrator in each of the three organizations gives you a SQL script that will create the tables at that organization, and another script to load a couple rows of sample data.

We prefer the script that creates the tables (rather than CSV file or spreadsheet) because the column names are sometimes ambiguous and the data types and sizes give valuable clues. We want the sample data for the same reason; when the column names are ambiguous, looking at some sample data will give a clue. We prefer the data dumps in the form of a script that will create the data rows because we invariably need to create and delete test data.

Assumption: That you know enough of SQL databases to read the scripts and data dumps. This will be necessary in the real world becuase you may have to build the database loading scripts from a printed data dump if the database cannot generate it for you.

You will only need to download one set of files. We have provided the files in three forms, for Oracle, SQL Server, and SQL Server 2005 Express, because that is the systems the authors of this page used.

3D design system database

Owner Line List database

Constructor Material Control database

Creating a Mapping Spreadsheet

The first step is to look at the three sets of data and create a cross-reference list for each table. We want to be able to show equivalent database rows in the same row of the list. A spreadsheet is an excellent medium.

  • Mapping to ISO 15926-4 using the RDS/WIP
  • Dealing with all the class choices in the RDS/WIP
  • Resolving Differences with Business Partners

Using Templates

... ... ...

Something Else

... ... ...


You have no rights to see this discussion.


About PCA
Reference Data Services