Introduction and legend

8 Dec. 2010, rev. 13 Feb. 2011, 26 Feb. 2011


Introduction

ISO 15926-2 can, in a way, be compared with a natural language. It has 201 entity types ("characters"). From that we can build templates ("words"), and from linked templates we can build a "story", that of what happened in our plant during its lifetime ("cradle to grave").

In this site you will find the list of the 201 entity types, a growing number of templates, and some (partial) "stories".

Application models

The topics on this website intend to show how certain situations in the lifetime of a plant can be expressed in application models, using ISO 15926-2 entity types throughout. These can be used to design "lowered" (shorthand) templates. The things that shall be in the "signature" of such  a template are marked in yellow.

The way these application models are expressed is, with some exceptions, as is done in ISO 15926-2 ("Part 2"), with some additions, as shown in the legend below.

Instance models

For larger application models, like the one here, instance models are being used, simply because the full analysis model would become too complex. See the legend below.

Legend for analysis diagrams

Entity type, as defined in ISO 15926 part 2

ID of an instance

ID of an instance that belongs to the signature of the derived shorthand template

A Relationship that is not a classification or a specialization

A ClassOfRelationship or a local, contextual, subtype of Relationship, with identifier

A subtyping or specialization relationship, the circle indicates the subtype or subclass. Subtypes are between Part 2 entity data types, subclass between instances thereof, where applicable.

An instantiation of classification relationship, the arrow head indicates the instance respectively member of the class. Instantiation means to indicate what the instance is in essence, whereas classification means to indicate membership that can change.

A relationship between Part 2 entity data types, that is illegal in EXPRESS

The list of elements of a multidimensional object, the numbers 1,2,3 etc indicate their order

An instance of the TemporalWholePart relationship, where P is a temporal part of W

Reference to a separate application model that expresses the temporal bounding (either 'beginning' or 'ending') of a temporal part. This is used in order to save space. Based on that date-time the temporal part is declared. [see diagram below]

 

Legend for instance models

Entity type, as defined in ISO 15926 part 2, mimicked in Part 4, being the top of the hierarchy for instances of (in this example) class_of_inanimate_physical_object. The annotation indicates the applicable Part 2 entity data type. For the mnemonics refer to https://www.posccaesar.org/wiki/SigMmt/Templates/Acronyms . A link to Part 2 definitions is given here.

Instance of some Part 4 class (NOTE: not necessarily a Part 2 Class), annotated with the applicable Part 2 entity data type. For the mnemonics refer to https://www.posccaesar.org/wiki/SigMmt/Templates/Acronyms . A link to Part 2 definitions is given here.

ID of an instance that is only of interest for lifted templates.

ID of an instance that belongs to the signature of the derived shorthand template

The other symbols, where used, are as shown in the above Legend for Analysis diagrams