| 13 | | In the previous section we read that the Proteus project successfully exchanged data between intelligent P&ID systems, between intelligent P&IDs and a 3D model, and between two 3D models. During this project a number of other items were acknowledged as being necessary to provide commercial, robust software solutions to the Process and Power industries. |
| 14 | | |
| 15 | | The continuation of the Proteus project intends to solve these items to enable true round-trip exchange of intelligent data, and to encourage software vendors to upgrade their systems to support them. The 12 items to solve are: |
| 16 | | |
| 17 | | 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.) |
| 18 | | 1. Graphical Symbols – inline or in symbol library? Maybe can only establish best practices |
| 19 | | 1. Symbol libraries, Cats and specs, and their inter-relationship |
| 20 | | 1. Do we want to switch to receiving company’s standards on import and re-configure diagram? |
| 21 | | 1. Validate class names in payload (files or others) against RDS/WIP on export and/or import. High value, avoid finger-pointing between e.g., EPC and owner |
| 22 | | 1. Multi-document import and export – is this one file with many data sets or many files with one dataset each? |
| 23 | | 1. Loosen the link between the model and the drawing. |
| 24 | | 1. Status management |
| 25 | | 1. Deletion |
| 26 | | 1. Standardized methodology for mapping between ISO 15926 and other standards |
| 27 | | 1. Methodology for mapping the XML representation of ISO15926 to iRing and vice versa |
| 28 | | 1. Preserving multiple products system data during a round-trip of payload |
| 29 | | |
| 30 | | 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” |
| 31 | | |
| 32 | | == iRING User Group == |
| 33 | | |
| 34 | | After the demonstration in the spring of 2009, the iRING Users Group was formed to continue the development of iRING. |
| 35 | | |
| 36 | | * http://www.iringug.org |
| 37 | | |
| 38 | | From its website: The "iRINGUserGroup is an open online community of users, companies, and organizations who use, are considering using, or are developing or deploying iRING protocols. The iRINGUserGroup is also responsible for the management, enhancement, and maintenance of iRINGTools and iRINGSandbox." |
| 39 | | |
| 40 | | The purpose of the iRING User Group is to develop software products and reference data content and services that provide seamless interoperability using the ISO 15926, Part 7, 8, & 9 standards. |
| 41 | | |
| 42 | | The iRING User Group website contains the latest version of the iRING tools software, a forum where new users can set support, and software to set up a sandbox for experimenting with external information exchanges. |
| 43 | | |
| 44 | | Membership and participation in the iRING User Group is open to anyone interested in learning, using, developing, or promoting iRING. There are no formal requirements for membership, only participation. There is no fees for dues. |
| 45 | | |
| 46 | | == BIDG (Building Information Definition Guide) == |
| 47 | | |
| 48 | | * The BIDG is being developed. It will include suggested RDS/WIP terms to aid business partners to agree on common mapping. |
| 49 | | |
| 50 | | |
| 51 | | == POSC/Caesar and FIATECH to Fund Commercial-Scale Deployment of the RDS/WIP == |
| 52 | | |
| 53 | | * POSC/Caesar and FIATECH are writing cooperative business plans to provide an industrial-strength site for the RDS/WIP. |
| 54 | | |
| 55 | | == Next == |
| 56 | | |
| 57 | | * [wiki:ISO15926Primer_GettingStarted Primer: Getting Started With ISO 15926] |
| 58 | | |
| 59 | | ---- |
| | 13 | * [wiki:ISO15926Primer An Introduction to ISO 15926] |
