1. WG3 Presentation to TC184/SC 4 Closing Plenary Baltimore, USA 23 Oct 2015 WG3 Oil, Gas, Process and Power Paul van Exel, Convener Nils Sandsmark, Deputy Convener 23 Oct 2015ISO TC184/SC4/WG3 Baltimore Closing Plenary1

2. WG 3 – Accomplishments in Baltimore & Plans for Sapporo WG 3 Planning & Organization –Teleconferences planned. Convener to decide on dates –We had problems with the Internet on Monday. Must be improved in future meetings –Business Plan for WG 3 for 2015-2018 will be discussed in the first teleconference Cooperation with TC184/WG 6 –Will continue to participate in TC184/WG6 work including: Review ISO 18101-1 CD draft MIMOSA and Fiatech project on International Standard Data sheet Definitions (ISDD) Work by USPI on deepening OGI use cases 223 Oct 2015ISO TC184/SC4/WG3 Baltimore Closing Plenary

3. WG 3 – Accomplishments in Baltimore & Plans for Sapporo ISO 15926-3 Shapes –Agreed to investigate the requirements and support for Part 3e2 Formal OWL representation of Part 2 exists (Part 12) PCA and Fiatech has done work to improve and extend Part 3 We should harvest good solutions in AP221 before the standard is withdrawn Cooperation with AP242 ISO 15926-4 Terms, definitions, taxonomy –Systematic Review started 2015-10-15 and closes 2016-03-16 323 Oct 2015ISO TC184/SC4/WG3 Baltimore Closing Plenary

4. WG 3 – Accomplishments in Baltimore & Plans for Sapporo ISO 15926-6e2 Rules for reference data –The combined NWI-CD proposal to add OWL representation to Part 6 has been submitted for 2 months ballot. Ballot end 2015-12-16 ISO 15926-12 OWL representation of ISO 15926-2 –The combined NWI-CD proposal has been submitted for 2 months ballot. Ballot end 2015-12-16 ISO 15926-13 Integrated lifecycle asset planning –The combined NWI-CD proposal has been submitted for 2 months ballot. Ballot end 2015-12-16 423 Oct 2015ISO TC184/SC4/WG3 Baltimore Closing Plenary

5. TC184/SC4/WG22 - SC4 Reference Data Closing Plenary, Baltimore 23 October 2015 Nils Sandsmark 2015-10-23 ISO TC184/SC4/WG22 Baltimore

6. WG22 – SC4 Reference Data Accomplishments in Baltimore and plans for Sapporo: Common reference data for ISO 10303-239, ISO 10303-242 and ISO 15926 - Joint meeting WG3/12/22 –The architecture for common reference was presented and discussed, see slides –We will investigate if this architecture can be extended to include IEC CDD –A draft document on artefact and artefact roles has been written. This document will extended to include properties –A demonstrator for the use of ISO 15926 reference data in ISO 10303- 239 has been planed to be ready by the Sapporo meeting Joint meeting between WG3, WG12 and WG22 will be held in Sapporo Tuesday, 08:00 – 12:00 6 2015-10-23 ISO TC184/SC4/WG22 Baltimore

7. WG22 – SC4 Reference Data Accomplishments in Baltimore and plans for Sapporo: CR0001 for ISO 15926-4 – UoM alignment to ISO 80000 –The proposal is available in the WG22 Drop-box –Will be presented and discussed in a MT web meeting within 3 week –Send the proposal to VT for ballot CR0006 - Enrichment from PCA experiences –The plan for completion was presented and discussed –Comments due by two weeks –Comments will be incorporated and then presented and discussed in a MT web meeting. If approved the plan will be executed CR0007 - CFIHOS items missing in P4 –A descriptive document had not added to the WG22 Drop-box –CFIHOS will be presented in a web meeting as soon as the document is ready 7 2015-10-23 ISO TC184/SC4/WG22 Baltimore

8. CR0006 Update of ISO 15926-4 20 October 2015 Lillian Hella lillian.hella@posccaesar.org

9. Background Current Part 4 spreadsheets developed by merging PCA RDL and STEPlib RDL Later Part 4 has been extended with rotating equipment spreadsheet Since merge, there has also been updates, corrections and additions to the PCA RDL Part 6 did not exist at the time of creation of Part 4

10. Objective and scope Prepare an updated version of Part 4 spreadsheets that is aligned with the PCA RDL 1) Start from the existing Part 4 spreadsheets 2) Find the corresponding items in the PCA RDL 3) Update the spreadsheets with additional data In addition updates after the introduction of Part 6 and required improvements

11. Proposed options 1. Select naming profile of classes and definitions 2. Reference to other RDIs in text definition 3. Align reference to source where applicable 4. Specialization and classification relationships need to be aligned between PCA RDL and Part 4 5. Check consistency of naming and definitions 6. Check entity type 7. Update of RDIs requiring domain and range

12. 1. Naming profile of classes and definitions (1) Check consistency of naming both in the Part 4 and PCA RDL (pipe vs piping, electric vs electrical) Document rules for naming Add alternative name when it makes sense to write in different order

13. 1. Naming profile of classes and definitions (1) PCA definitions will be used unless found insufficient We propose the following from Part 6: that. Remove leading “A”/”An” which is widely used in both sources

14. 2. Reference to other RDIs in text definition Propose to use “ ” Enables automatic processing of data and definitions Easy to automatically find RDI and transform to alternative representations for display, e.g. displaying it in bold, adding hyperlinks. Example: Coaxial jack (unique number: 2585; RDS5764412) - that is designed to attach to free end of.

15. 3. Align reference to source where applicable Mismatch between notes and source in Part 4 spreadsheets and the PCA RDL Check and align so that they are identical Example: (unique number: 2586, RDS960569) has source in Part 4: IEC 845-07-27, while PCA RDL hasNote: IEC 50-845-07-27, meanwhile IEC used IEV 845- 07-27. (unique number: 8498, RDS13048460) has a reference put in Notes (Part 4), and nothing in the PCA RDL.

16. 4. Specialization and classification relationships Classification is, in most cases, missing in Part 4 spreadsheets Mismatch in specialization relationships Update according to PCA RDL, also see item 7.

17. 5. Alignment naming and definitions Some RDIs are named differently in Part 4 and the PCA RDL Example: “outlet port” in Part 4 and “outlet” in the PCA RDL Naming and definitions must correspond in both Part 4 and PCA RDL The PCA RDL is considered to be the master source

18. 6. Entity types There are inconsistencies regarding the use of some of the entity types Suggest that entity types are reviewed and that a strategy and rules for use of entity types in a consistent manner is proposed (e.g. for how to distinguish between intent and function).

19. 7. Domain and range Properties do not have domain and range in the spreadsheets Propose to assign domain and range to properties Coordinate with CR0001 for UoM