Version 16 (modified by gordonrachar, 14 years ago)

--

Benefits of Using ISO 15926

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

  1. Abstract
  2. ISO 15926 is the Babel Fish
  3. Benefits
    1. What ISO 15926 is For
    2. What ISO 15926 Standardizes
    3. New Plant Contracts, Commissioning and Handover Data
    4. Handover Data in a Consistent Form
    5. Handover Data Cross-Referenced Against Assets
    6. Handover Data in a Standard Form

Abstract

[Enter abstract]


ISO 15926 is the Babel Fish

* [Diagram simlar to last one on previous page, but now each player has a facade. (Would have to show the connection from one player's facade to another player's database is a machine operation and not a manual operation. Otherwise there won't be much difference) ]

When exchanging information with someone, all you will need to ask is "What is the URL of your facade?".

Internally, you will publish to your companie's facade.  The facade will contain all the data your company wants to expose publicly. Once published, say from a 3D model, an instrument application can read it without having to know that the data started life as a piping model.

Benefits

ISO 15926 addresses the key business issues for asset information through a well-developed and robust technical infrastructure. The ISO 15926 framework allows information to be created once, managed between organizations and across systems, and made available to all authorized users as required to improve timely decision making. Utilizing IS0 15926 enables organizations to meet their asset information requirements while reducing the costs associated with defining, collecting, transforming, deploying and sustaining this information over the lifecycle of assets and facilities.

Engineering Business Audience:

  • Reduce cost and increase quality of handover.
  • Reduce turnaround time for procurement information requests.
  • Streamline interactions with engineering subcontractors.

OEM Audience:

  • Publish information in a searchable form selectively and on a project by project basis.
  • Maintain control of data.
  • Reap benefits of customer use and reliability data.

Owner Operators:

  • Obviate need to develop enterprise-wide classification system (internalize RDS/WIP instead)
  • Be able to make accurate costings from front-end engineering designs.
  • Better evaluate EPC bids.
  • Lower new plant opportunity costs with better organized handover data and commissioning outputs.

Information Management Audience:

  • A solution to data interoperability.
  • Distinct from business method interoperability (but can be used in support of it).

Modelers' Paradise Audience:

  • Uses ontological foundation.
  • Supports modern tools for validation and expression of logical constraints.
  • Provides published methodologies for arriving at definitions.

Geek Vision Audience:

  • Has a semantic web representation (OWL/RDF).
  • Utilizes semantic web technologies for access (SPARQL).
  • Will utilize Web Services (WSDL, SOAP).
  • Can be modelled as a form of data-centric SOA.

What ISO 15926 is For

ISO 15926 can be applied to many different problems, but in practice today, it is a suite of standards that supports interoperability for data about the equipment and systems used in industrial processes, over the lifecycle of those objects. Some of typical scenarios for use of ISO 15926 are: sharing information between engineering contractors and their subcontractors, acquiring information from equipment vendors, handing over data to the operators of a new industrial plant and harmonizing the information across an enterprise that owns many plants.

What ISO 15926 Standardizes

ISO 15926 achieves its interoperability ends by standardizing all of the elements required for information transfer between systems: a temporal data model that defines and classifies information in space and time (part 2); geometry and topology definitions (part 3); a reference data library for contributed classifications (part 4); a layer for concisely expressing relationships, bindings to a serialization format for exchange and bindings to protocols for query and transfer (all in part 7).

New Plant Contracts, Commissioning and Handover Data

When a new plant is commissioned, information is typically handed over to the plant operator in a highly disorganized manner - the data will have many different sources with no attempt at harmonization. In many cases there will be nothing to tie the data back to the installed assets and it must be collated manually to be of any use. Specifying the requirements for handover data at the outset of a contract for the design and construction of a new plant can dramatically reduce the costs of collating that data against the installed asset base.

Handover Data in a Consistent Form

By ensuring information is in a consistent, known form, it can be imported into the enterprise information systems far more rapidly and with less cost and error. The speed of the import is increased by being able to plan in advance for the expected form of the information, eliminating some opportunity costs by allowing the plant to operate at full capacity earlier. The information management costs of providing import facilities are reduced because only a single form of import need be supported.

Handover Data Cross-Referenced Against Assets

Ensuring the data is cross-referenced against the installed assets at handover avoids the substantial costs of manual collation. Cross-referenced data also reduces the likelihood of errors that are typical in a manual process. The cost of errors in cross-referencing handover data against the correct assets can be prohibitive. Consider the case where the wrong recommended spares sheet is associated with a critical asset - this can lead to inapplicable spares being ordered, paid for and stocked in warehouses. An incident of unplanned maintenance on the critical asset would then reveal that the parts that are needed to ensure maximum uptime of the asset are not available on hand, resulting in a loss of production.

Handover Data in a Standard Form

The cost of specifying the requirements for any kind of sophisticated data exchange, such as handover data for a large capital project, can be high. The vast bulk of that cost is in the definition of the classifications and formats that underpin those requirements. Fortunately, those classifications and formats can be re-used from project to project. Typically, they are also equally applicable from one enterprise to another. Even further, the costs to the EPC that actually supplies the data will be lower if these elements of the requirements are already familiar to them, already part of their internal processes. This in turn decreases the overall cost of the project and also lowers the likelihood of misinterpretation of the data. ISO 15926 was designed to address this exact issue.


Discussion

You have no rights to see this discussion.

Home
About PCA
Reference Data Services
Projects
Workgroups