Version 1 (modified by jbourne, 16 years ago)

--

IDS-ADI Matrix 1

Multi (3+) P&ID vendor exchange … at Yellow (WIP) level & contribute content to WIP & BIDG. First step, team to define a scope / plan / deliverables for such a proposed project.

Matrix leader: Phil Robins (AVEVA) - timezone UK.

References

All Matrix documents

ISO 15926 Compliancy Spec (MS Word)

Scope

  • Data exchange of the information in intelligent P&ID’s.
    • The tag numbers, equipment numbers, line numbers etc.
    • The schematic information e.g. the exchanged P&ID must look exactly the same
    • All connectivity the P&ID represents expressed as relationships
    • Meta data of the P&ID itself.
  • The scope of the data exchange requirements will be as per the BIDG (Business Interface Definition Guide). This is a guide that will be made by FIATECH. It has a requirements specification software tool, with which the scope of a data exchange can be defined in WIP terms. The tool outputs a spreadsheet which will be used as input to filter the object types of the data exchange.

NOT in scope are, for example:

  • The design data and process data of the represented equipment/lines/instruments
  • Process data propagation rules e.g. the two lines behind a pipe line junction share temperature and pressure but have different flows. This requires a stream number system and stream breaks (similar to pipe spec breaks). Stream number systems taking care for process data is a standard ISO 15926 modeling aspect.
  • The Meta data of represented objects, e.g. status, ownership, revision, responsible engineer etc.

Level of implementation

Production grade software scalable to large engineering projects.

Level of compliancy

The exchange is at compliance category Yellow. That means the middleware for the exchange is non-compliant to ISO 15926, but the classification of the symbols and properties will be as per the WIP terms.

Home
About PCA
Reference Data Services
Projects
Workgroups