| Version 8 (modified by gordonrachar, 14 years ago) |
|---|
TracNav menu
Case Studies
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
Abstract
[Enter abstract]
Owner/Operator
These case studies focus on the information asset that was developed along with the physical plant. Emphasis is on how much of the information asset used ISO 15926 and which parts.
Shell - Oman LNG
| Owner | Shell |
| EPC | Chaioda, Foster Wheeler |
| Detail Engineering | 1996 |
Owner Requirements for the Information Asset:
- A data warehouse in which to store certain information about plant objects.
- The data warehouse was to be standardized against STEP. (Later, standardized against ISO 15926.)
- The data warehouse was to be in a neutral format, not optimized for any vendor's software.
- The prime purpose of the database was to be able to validate that the handover information was complete.
- A secondary purpose was to be able to query information about plant objects outside of any engineering software or document retreival system.
Included in the data warehouse:
- Engineering data about equipment attributes.
- Schematic data including P&IDs, Line Lists, Wiring & Control Schematics, Cable Schedules.
Not included:
- 3D data
Q. What is value of standardizing a data warehouse against a standard?
Q. How does one go about standardizing a data warehouse against something like STEP?
Shell envisioned a big repository where all the suppliers could post information. None of the production engineering tools of the day had any provision for using a data warehouse, so the purpose of the data store was simply easy access to plant information.
The first step was to figure out how to make the data warehouse inderstand the Part 2 data model. It required a different kind of data model than a normal relational database. (As an aside, one result is that Oracle Corp. spun off a seperate project, called "Synergy", to develop software along these lines.)
Q. If this project started before ISO 15926 was born, how could there be a Part 2?
ISO 15926 Part 2 data objects are very fine grained. Definitions of atomic concepts that can be assembled together in various combinations to make pretty well anything. But understanding how to work with Part 2 objects directly, was, and still is, very specialized. But whatever the fine grained Part 2 object was being represented, there was a more business-friendly view. This spawned the concept of a Business Object which was later called Usage Factors, and today called a Template.
The database that was eventually handed over was built in Microsoft Access. It did not, nor was it ever intended to, replicate all the information about the plant objects. A good metephor is a 4"x6" card containing the most used information. Up to about two dozen attributes of plant objects were tracked. For further information, references were made to data sheets and vendor information.
Q. If the database that was turned over was Access, what happened to Prism?
Benefits to ISO 15926:
- This project started at about the time people were talking about STEP AP221 (a.k.a ISO 10303 Application Protocol 221), and were thinking there should be something more. It was out of these ideas, and on this project, that ISO 15926 was probably born.
- Development of the concept of Templates to make it easier to use Part 2 data types.
To be continued...
Shell/CNPC - Nanhai Petrochem
| Owner | Shell, Chinese National Petroleum Company |
| EPC | ?? |
| Detail Engineering | 2003-2004 |
EPC Company
Original Equipment Manufacturer
Software Developer
AVEVA
Bentley Systems
Intergraph
General
Attachments
- AVEVA_Interop_Strategy.pdf (2.7 MB) - added by gordonrachar 14 years ago.
- Bentley_ISO15926.pdf (1.2 MB) - added by gordonrachar 14 years ago.
- Intergraph_Interop.pdf (1.1 MB) - added by gordonrachar 14 years ago.
