What is Being Done Now With 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. Proteus
3. Avalon
4. BIDG (Building Information Definition Guide)
5. POSC/Caeser, FIATECH Meeting in Kaula Lumpur
6. Next

Abstract

[Enter abstract]

---

Proteus

The Proteus project is the next phase of the original Matrix 1,2,3 project to provide ISO15926 data exchange of intelligent P&ID data between vendor systems, exchange of data between different vendors P&IDs and 3D models and exchange of data between different vendors 3D models. 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. The Proteus project aims to solve these shelved items, either by changes/additions to the XML exchange schema or Technical specifications detailing the features that must be supported in software vendors systems to enable true round-trip exchange of intelligent data and to encourage software vendors to upgrade their available commercial systems to support them. The 12 items to solve are:

1 Handling User Defined Attributes in the source and target systems – how to reconcile these, what are limitations (what can we allow and not allow, what are rules of engagement, etc) 1 Graphical Symbols – inline or in symbol library? Maybe can only establish best practices 1 Symbol libraries, Cats and specs, and their inter-relationship 1 Do we want to switch to receiving company’s standards on import and re-configure diagram? 1 Validate class names in payload (files or others) against RDS/WIP on export and/or import. High value, avoid finger-pointing between eg EPC and owner 1 Multi-document import and export – is this one file with many data sets or many files with one dataset each? 1 Loosen the link between the model and the drawing. 1 Status management 1 Deletion 1 Standardized methodology for mapping between ISO 15926 and other standards 1 Methodology for mapping the XML representation of ISO15926 to iRing and vice versa 1 Preserving multiple products system data during a round-trip of payload

The full intent is to provide a path for vendors towards the ability to do multiple data exchanges during a project life cycle, editing data in either system and exchanging it back with full fidelity and no degradation of intelligence”

Avalon

Purpose:

• Provide a long-term location for the RDS/WIP

• Provide means of cataloguing the ISO 15926 source code

• Provide a central forum for new ISO 15926 implementers to collaborate

BIDG (Building Information Definition Guide)

...

POSC/Caeser, FIATECH Meeting in Kaula Lumpur

...

Next

• Getting Started With ISO 15926

---

Discussion

You have no rights to see this discussion.