[[TracNav(TracNav/IdsAdi)]]

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

= IDS-ADI Matrix 2 =	
== Multi (3+) 3d vendor exchange … at Dictionary (WIP) level & contribute content to WIP & BIDG. ==
First step, team to define a scope / plan / deliverables for such a proposed project.

= IDS-ADI Matrix 3 =	
== Multi (3+) 2D to 3d vendor exchange … at Dictionary (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 ===    

[source:projects/IDS-ADI/MatrixSubProjects All Matrix documents]

[source:projects/IDS-ADI/ComplianceSpecification/ISO_15926_Compliance_Specification.doc ISO 15926 Compliancy Spec (MS Word)]

=== Matrix 1 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.

=== Matrix 2 Scope ===    

 * Data exchange of the information in intelligent 3D Models. 
   * The tag numbers, equipment numbers, line numbers etc.
   * All connectivity the 3d model represents expressed as relationships
   * Meta data of the P&ID itself.

=== Matrix 3 Scope ===    

 * Data exchange of the information between intelligent 2D and 3D Models. 
   * The tag numbers, equipment numbers, line numbers etc.
   * All connectivity the 3d model 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 Dictionary Level compliance category to ISO 15926. That means the exchange is by XML file with the classification of the symbols and properties as per the ISO15926 RDS/WIP terms.

=== History of the project ===

After the kickoff meeting for Matrix 1, Matrix 2 and Matrix 3 projects it was decided to join these initiatives, as the scope of each was complimentary and the data was orthogonal.

The Matrix 1,2,3 project culminated in a demonstration at the April 2009 FIATECH conference in Las Vegas by 9 vendors showing exchange of data using an XML file transport that satisfied all 3 data exchanges. During the Matrix 1,2,3 project several items were acknowledged as being necessary to provide commercial, robust software solutions to the Process and Power industries but were shelved due to the time constraint of the conference.See [wiki:IdsAdiProject/IdsAdiProteusProject IDS-ADI Proteus Project]

Project completed in April 2009

== NOTE: Several Software Vendors now have commercially available fully supported Dictionary Level compliant ISO15926 Products ==