Version 27 (modified by gordonrachar, 14 years ago) |
---|
TracNav menu
- Back to Avalon Collaboration Page
-
Introduction
- Overview
- Entry Points to Learning About ISO 15926
- Case Studies
- Principles of Interoperability
- Building a Business Case
-
Using ISO 15926 Tools
- Discovering the Right Class
- TC 184 SC 4 WG 3
- Using the RDS/WIP (RDL Façade)
- POSC/CAESER RDS
-
Tutorials
- Mapping to ISO 15926-4
- Using Templates
- Diagnostic Page
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.
Contents
- Setting the Scenario
- Mapping to ISO 15926 Part 4 Using the RDS/WIP
- Introduction to Templates
- Something Else
Setting the Scenario
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.
Create Database Scripts
The first step is to get a description of the database columns involved in the exchange. In our example, we will assume that a database administrator 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.
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.)
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 With the RDS/WIP
Basically, your task here is to search for ISO 15926-4 class that most closely matches the meaning of each of the column names in your three databases. The first thing you will notice is that the best choice is not immediately apparent. In the sample spreadsheet below, some of the data rows have more than one choice. Look at a few of them to see what the differences are.
Discovering the Right Class
Here are some guidelines for selecting the best class:
The sample spreadsheet below has had the duplicates removed, with the best choice left.
Sample Spreadsheet
Resolving Differences
Some ideas for resolving differences.
Introduction to Templates
... ... ...
Something Else
... ... ...
Attachments
- MappingSpreadsheet_Blank.xls (63.5 kB) - added by gordonrachar 14 years ago.
- MappingSpreadsheet_First.xls (63.5 kB) - added by gordonrachar 14 years ago.
- MappingSpreadsheet_Second.xls (63.5 kB) - added by gordonrachar 14 years ago.
- MappingSpreadsheet_Third.xls (63.5 kB) - added by gordonrachar 14 years ago.
- MappingSpreadsheet_Columns.xls (63.5 kB) - added by gordonrachar 14 years ago.