| | 2 | 21/22 June 2012[[br]] |
| | 3 | Fluor Haarlem, The Netherlands [[br]] |
| | 4 | Present: |
| | 5 | * Ian Glendinning |
| | 6 | * Mange Valen-Sendstad |
| | 7 | * Hans Teijgeler |
| | 8 | * Onno Paap |
| | 9 | |
| | 10 | === Summary of the Meeting === |
| | 11 | '''Plant Lifecycle Model''' |
| | 12 | * Hans diagrams (http://15926.org/publications/general-discussions/ ) are an overview. They can always be extended in scope and detail, detail that is implied or omitted, but this is not intended to be the ISO15926 Instance diagram for implementation. The latter is driven by template selection (e.g. using patterns in the JORD Methodology, which has had the agreed lifecycle model embedded since IDS/ADI version. |
| | 13 | * Main omission from JORD methodology so far is explicit use of temporal parts and therefore adding of temporal whole-part relations necessary |
| | 14 | * Implicitly defaulting to all being temporal parts (for same as-installed steady-state operation case. Pragmatic adoption rule will be incorporated – e.g.: where planned / significant to the facility lifecycle business process – not all circumstantial changes and additions to known information.) |
| | 15 | |
| | 16 | '''Class Lifecycle Model ''' |
| | 17 | * Hans diagrams not contentious. Essentially about specializing at the right level for the life of the item classified. |
| | 18 | * E.g. Ur-Class for long life objects, specialized leaf where applicable to the temporal part. Already supported by intended modelling and methodology. |
| | 19 | |
| | 20 | '''Power Sets''' |
| | 21 | * Unusual to go back to set-theory approach, but not contentious. This Individual, Class and Class_of_Class model is already supported by intended modeling and methodology (Appendix E of JORD mapping methodology). |
| | 22 | |
| | 23 | '''Other topics discussed''' |
| | 24 | * Progress with JORD Methodology, Template Graph documentation format, and federated RDL scopes / ID schemes, etc. |
| | 25 | * Format of diagrams. |
| | 26 | * Use Magne’s instance diagram format for patterns and the implementable set of templates derived. Use Hans’ style for the overview model of how the patterns fit into the overall business scope & lifecycle model. |
| | 27 | |
| | 28 | '''No significant discussion''' – Part 8 & Part 3 RDL representation [[br]] |
| | 29 | |
| | 30 | The MoM for from the meeting can be found at this link |
| | 31 | |
| | 32 | |
| | 33 | |
