ISO/TS 15926-7:2011

TECHNICAL ISO/TS
SPECIFICATION 15926-7
First edition
2011-10-15
Industrial automation systems and
integration — Integration of life-cycle
data for process plants including oil and
gas production facilities —
Part 7:
Implementation methods for the
integration of distributed systems:
Template methodology
Systèmes d'automatisation industrielle et intégration — Intégration de
données de cycle de vie pour les industries de «process», y compris les
usines de production de pétrole et de gaz —
Partie 7: Méthodes de mise en œuvre pour l'intégration de systèmes
distribués: Méthodologie de modèle

Reference number
©
ISO 2011
©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2011 – All rights reserved

Contents Page
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Terms, definitions, and abbreviated terms . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.1 Terms and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.2 Abbreviated terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Fundamental concepts and assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Concepts and models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.1 ISO 15926-2 data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.2 ISO/TS 15926-4 reference data . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.3 User-defined taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.4 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 Modelling basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1 ISO 15926-2 data model in first-order logic . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Logical template definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Proto-templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3.1 entityTriple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 Template specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 Requirements on template, general . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2 Template signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3 Template specialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.4 Verification of compliance with ISO 15926-2 . . . . . . . . . . . . . . . . . . . . . . 15
6 Templates for individuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Reference items needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Initial set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.1 Template ClassificationOfIndividual . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.2 Template ClassificationOfRelationship . . . . . . . . . . . . . . . . . . . . . . 16
6.3.3 Template InstanceOfRelation . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3.4 Template IdentificationByNumber . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.5 Template ClassifiedIdentification . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.3.6 Template LocationOfActivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3.7 Template BeginningOfIndividual . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.8 Template BeginningEndOfIndividual . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.9 Template BeginningOfTemporalPart . . . . . . . . . . . . . . . . . . . . . . . . 22
6.3.10 Template BeginningEndLocationOfActivity . . . . . . . . . . . . . . . . . . . . 22
6.3.11 Template InstanceOfIndirectProperty . . . . . . . . . . . . . . . . . . . . . . . 23
6.3.12 Template RealMagnitudeOfProperty . . . . . . . . . . . . . . . . . . . . . . . . 23
6.3.13 Template IndirectPropertyScaleReal . . . . . . . . . . . . . . . . . . . . . . . . 24
6.3.14 Template StatusApproval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.3.15 Template ClassifiedInvolvement . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.3.16 Template InvolvementStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.3.17 Template InvolvementStatusBeginning . . . . . . . . . . . . . . . . . . . . . . 26

c ISO 2011 — All rights reserved iii

6.3.18 Template SuccessionOfInvolvementByReference . . . . . . . . . . . . . . . . . 27
6.3.19 Template SuccessionOfInvolvementInActivity . . . . . . . . . . . . . . . . . . 27
7 Templates for classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2 Reference data items needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.1 Reference classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.2 Reference relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3 Representing complex classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.4 Relation constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.4.1 Relations: Domain and co-domain . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.4.2 Existential and universal constraints . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4.3 At-most n subrelation constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.5 Initial set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.5.1 Template ClassificationOfClass . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.5.2 Template ClassificationOfClassOfIndividual . . . . . . . . . . . . . . . . . . . 37
7.5.3 Template ClassificationOfClassOfRelationship . . . . . . . . . . . . . . . . . . 38
7.5.4 Template RelationOfIndividualsToIndividuals . . . . . . . . . . . . . . . . . . . 39
7.5.5 Template SpecializationOfIndividualRelation . . . . . . . . . . . . . . . . . . . 40
7.5.6 Template EnumeratedSetOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . 41
7.5.7 Template EnumeratedSetOf3Classes . . . . . . . . . . . . . . . . . . . . . . . . 42
7.5.8 Template UnionOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.5.9 Template IntersectionOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.5.10 Template DierenceOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.5.11 Template RelativeComplementOf2Classes . . . . . . . . . . . . . . . . . . . . 44
7.5.12 Template DisjointnessOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.5.13 Templates6pecializationAsEnd1UniversalRestriction,6Secializa-
tionAsEnd2UniversalRestriction. . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.5.14 Templates CardinalityMin, CardinalityMax, CardinalityMinMax . . . . . . . . . 47
7.5.15 Cardinality Assignment Templates . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.5.16 Template TimeRepresentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.5.17 Template MagnitudeOfProperty . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.5.18 Template LowerUpperOfNumberRange . . . . . . . . . . . . . . . . . . . . . . 52
7.5.19 Template LowerUpperOfPropertyRange . . . . . . . . . . . . . . . . . . . . . . 53
7.5.20 Template LowerUpperMagnitudeOfPropertyRange . . . . . . . . . . . . . . . . 54
7.5.21 Template PropertyRangeRestrictionOfClass . . . . . . . . . . . . . . . . . . . . 56
7.5.22 Template PropertyRangeMagnitudeRestrictionOfClass . . . . . . . . . . . . . . 56
7.5.23 Template SymbolOfScale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.5.24 Template DimensionUnitNumberRangeOfScale . . . . . . . . . . . . . . . . . 59
7.5.25 Template ClassInvolvementStatusBeginning . . . . . . . . . . . . . . . . . . . 60
7.5.26 Template ClassInvolvementSuccession . . . . . . . . . . . . . . . . . . . . . . 61
8 Templates as reference data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.1 Template signatures and template axioms . . . . . . . . . . . . . . . . . . . . . . . . 62
8.2 Representation as class of multidimensional object . . . . . . . . . . . . . . . . . . . 63
8.2.1 Roles constrained by RDL constructs . . . . . . . . . . . . . . . . . . . . . . . 63
8.2.2 Roles constrained by entity type only . . . . . . . . . . . . . . . . . . . . . . . 63
Annex A (normative) Information object registration . . . . . . . . . . . . . . . . . . . . . . . . 64
A.1 Document identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Annex B (normative) Listing: ISO 15926-2 in first-order logic . . . . . . . . . . . . . . . . . . . 65
B.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
iv
c ISO 2011 — All rights reserved

B.2 Universe axiom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
B.3 Subtype axioms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
B.4 Abstract axioms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B.5 Disjoint axioms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B.6 Role axioms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
B.7 Additional range restriction axioms . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Annex C (normative) Listing: proto-templates . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
C.1 Proto-templates for relational entity types . . . . . . . . . . . . . . . . . . . . . . . . 84
C.2 Proto-templates for subtypes of relational entity types . . . . . . . . . . . . . . . . . . 86
C.3 entityTriple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Annex D (informative) Table: proto-templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Annex E (informative) Recursive vs. non-recursive template expansion . . . . . . . . . . . . . . 96
E.1 Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
E.2 Recursion or not? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
E.3 Further technical issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Annex F (informative) Template expansion: example . . . . . . . . . . . . . . . . . . . . . . . . 99
F.1 Example of template expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
F.2 Result of expansion according to template axioms . . . . . . . . . . . . . . . . . . . . 99
F.3 Instantiating existential quantifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
F.4 Verification of consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Annex G (informative) Consistency checking via coherent logic . . . . . . . . . . . . . . . . . . 104
Annex H (informative) Formal constraints beyond templates . . . . . . . . . . . . . . . . . . . . 107
Annex J (normative) Semantics of templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
J.1 Rewrite rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
J.2 Pattern rewriting system corresponding to a template set . . . . . . . . . . . . . . . . 108
J.3 Template expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Annex K (normative) Properties of template expansion . . . . . . . . . . . . . . . . . . . . . . . 110
K.1 Logical readings of template definitions . . . . . . . . . . . . . . . . . . . . . . . . . 110
K.2 Decidability of consistency with ISO 15926-2 . . . . . . . . . . . . . . . . . . . . . . 110
K.2.1 Translation of ISO 15926-2 language into description logic . . . . . . . . . . . 111
K.2.2 Consistency Check for Template Expansion . . . . . . . . . . . . . . . . . . . . 112
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figures
Figure 1 — An overview of the integration architecture of ISO/TS 18876-1 . . . . . . . . . . . . 6
Figure 2 — Diagram of a class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 3 — Diagram of a relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 4 — Diagram of a relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 5 — Diagram showing relation roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 6 — Diagram showing cardinalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 7 — Diagram of specialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 8 — Diagram of classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

c ISO 2011 — All rights reserved v

Figure 9 — Example template ClassificationOfIndividual . . . . . . . . . . . . . . . . . . . . . . 17
Figure 10 — Example template ClassificationOfRelationship . . . . . . . . . . . . . . . . . . . . 17
Figure 11 — Example template InstanceOfRelation . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 12 — Example template IdentificationByNumber . . . . . . . . . . . . . . . . . . . . . . 19
Figure 13 — Example template ClassifiedIdentification . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 14 — Example template LocationOfActivity . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 15 — Example template BeginningEndOfIndividual . . . . . . . . . . . . . . . . . . . . . 22
Figure 16 — Use of EmptyClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 17 — Relation: Permitted Ambient Temperature . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 18 — Relation: Celsius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 19 — Existential constraint: Permitted Ambient Temperature . . . . . . . . . . . . . . . . 33
Figure 20 — Precisely-one constraint: Permitted Ambient Temperature . . . . . . . . . . . . . . 34
Figure 21 — Classification for universal constraint . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 22 — Universal constraint pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 23 — Universal constraint: Equipment, Temperature . . . . . . . . . . . . . . . . . . . . . 35
Figure 24 — Example for at most constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 25 — Combining universal constraints and cardinalities . . . . . . . . . . . . . . . . . . . 36
Figure 26 — Example template ClassificationOfClass . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 27 — Example template ClassificationOfClassOfIndividual . . . . . . . . . . . . . . . . . 38
Figure 28 — Example template ClassificationOfClassOfRelationship . . . . . . . . . . . . . . . . 39
Figure 29 — Example template RelationOfIndividualsToIndividuals . . . . . . . . . . . . . . . . 40
Figure 30 — Example template SpecializationOfIndividualRelation . . . . . . . . . . . . . . . . 41
Figure 31 — Example template EnumeratedSetOf2Classes . . . . . . . . . . . . . . . . . . . . . 42
Figure 32 — Example template UnionOf2Classes . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 33 — Example template RelativeComplementOf2Classes . . . . . . . . . . . . . . . . . . 45
Figure 34 — Example template DisjointnessOf2Classes . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 35 — Example template SpecializationAsEnd2UniversalRestriction . . . . . . . . . . . . . 47
Figure 36 — Example template CardinalityMinMax . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 37 — Example template CardinalityEnd1MinMax . . . . . . . . . . . . . . . . . . . . . . 51
Figure 38 — Example template MagnitudeOfProperty . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 39 — Example template LowerUpperOfNumberRange . . . . . . . . . . . . . . . . . . . 53
Figure 40 — Example template LowerUpperOfPropertyRange . . . . . . . . . . . . . . . . . . . 54
Figure 41 — Example template LowerUpperMagnitudeOfPropertyRange . . . . . . . . . . . . . 55
Figure 42 — Example template PropertyRangeRestrictionOfClass . . . . . . . . . . . . . . . . . 56
Figure 43 — Example template PropertyRangeMagnitudeRestrictionOfClass . . . . . . . . . . . 58
Figure 44 — Example template SymbolOfScale . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 45 — Example template DimensionUnitNumberRangeOfScale . . . . . . . . . . . . . . . 60
Tables
Table 1 — Reference items: Templates for individuals . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2 — Reference items: Templates for classes . . . . . . . . . . . . . . . . . . . . . . . . . . 28
TableD.1—CompactlistingofProto-templates. . . . . . . . . . . . . . . . . . . . . . . . . . . 9
vi
c ISO 2011 — All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical com-
mittee has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates
closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical stan-
dardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Stan-
dards adopted by the technical committees are circulated to the member bodies for voting. Publication
as an International Standard requires approval by at least 75% of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
— an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical ex-
perts in an ISO working group and is accepted for publication if it is approved by more than 50%
of the members of the parent committee casting a vote;
— an ISO Technical Specification (ISO/TS) represents an agreement between the members of a tech-
nical committee and is accepted for publication if it is approved by 2/3 of the members of the
committee casting a vote.
An ISO/PAS or ISO/TS is reviewed every three years with a view to deciding whether it can be trans-
formed into an International Standard.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 15926-7 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 4, Industrial data.
ISO 15926 is organized as a series of parts, each published separately. The structure of ISO 15926 is
described in ISO 15926-1.
Each part of ISO 15926 is a member of the following series: data model, reference data, implementa-
tion methods, conformance testing methodology and framework, characterization methods, abstract test
suites. This part of ISO 15926 is a member of the implementation methods series.
A complete list of parts of ISO 15926 is available from the following URL:
http://www.tc184-sc4.org/titles/OIL_GAS_Titles.htm

c ISO 2011 — All rights reserved vii

Introduction
ISO 15926 is an International Standard for the representation of process plant life-cycle information.
This representation is specified by a generic, conceptual data model that is suitable as the basis for
implementation in a shared database or data warehouse. The data model is designed to be used in
conjunction with reference data: standard instances that represent information common to a number
of users, process plants, or both. The support for a specific life-cycle activity depends on the use of
appropriate reference data in conjunction with the data model.
ISO 15926 is organized as a number of parts, each published separately. This part of ISO 15926 specifies
the template methodology and is independent of implementation methodologies and computer languages.
This part of ISO 15926 deals with the template methodology, which defines strict models of ISO 15926-2
conceptual model elements which can be used in data modelling, integration and interoperability meth-
ods. This part of ISO 15926 is independent of implementation languages, implementation infrastructure
and test methods.
This part of ISO 15926 serves as the basis for implementation languages, implementation infrastructure
and test methods.
This part of ISO 15926 addresses:
— the method of first-order logic used;
— template syntax;
— the semantics of templates;
— the method of template expansion;
— the definition of proto templates;
— the initial set of templates.
Readers of this part of ISO 15926 require an understanding of conceptual data models and of ISO 15926-2.
The target audiences for this part of ISO 15926 are as follows:
— technical managers wishing to determine whether ISO 15926 is appropriate for their business needs;
— implementers.
In this part of ISO 15926, the same English language word might be used to refer to a real world thing, to
an EXPRESS representation of the real world thing, or to an RDF/XML representation of the real-world
thing. These uses are distinguished by the following typographic conventions:
— if a word or phrase occurs in the same typeface as the surrounding narrative text, the word or phrase
refers to the real-world thing;
— if the word or phrase occurs in bold typeface, it refers to the EXPRESS representation from the
ISO 15926-2 data model;
viii
c ISO 2011 — All rights reserved

EXAMPLE 1 class of inanimate physical object
— if the word or phrase occurs in bold camel case typeface, it refers to a term in the ISO 15926-2
language, as specified in 4.1;
EXAMPLE 2 ClassOfApprovalByStatus
— if the word or phrase occurs in italic camel case typeface, it refers to a template name.
EXAMPLE 3 RTriple(z, x, y)
References to identifiers in examples are fictitious.
In this part of ISO 15926, diagrams are occasionally used to illustrate ISO 15926-2 modelling patterns.
The symbols used in instance diagrams are a minor modification of the symbols used in ISO 15926-2.

c ISO 2011 — All rights reserved ix

TECHNICAL SPECIFICATION ISO/TS 15926-7:2011(E)

Industrial automation systems and integration — Integration of
life-cycle data for process plants including oil and gas
production facilities —
Part 7:
Implementation methods for the integration of distributed
systems: Template methodology
1 Scope
This part of ISO 15926 is a specification for data exchange and life-cycle information integration using
templates based on the data model of ISO 15926-2. This part of ISO 15926 provides a methodology for data
integration of ontologies using mathematical first-order logic, which makes it independent of computer
languages.
The following are within the scope of this part of ISO 15926:
— representation of the ISO 15926-2 EXPRESS model in formal logic;
— criteria for template definitions;
— methods of template expansion and verification;
— initial set of template definitions.
NOTE Forpracticalguidelinestoinformationrepresentationusingtemplates,see5HIHUHQFH[17].
The following are outside the scope of this part of ISO 15926:
— implementation in computer-interpretable languages;
— storage and retrieval;
— security.
2 Terms, definitions, and abbreviated terms
2.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1.1
base template
template with only entity types in the expansion of its template axiom
2.1.2
class
category or division of things based on one or more critera for inclusion and exclusion
NOTE 1 A class need not have any known members (things that satisfy its criteria for membership).
NOTE2 Becauseofthespatio-temporalparadigmusedtodefineindividualsinISO15926,allclassesarenon-well-founded
sets.
c ISO 2011 — All rights reserved 1

NOTE 3 Adapted from ISO 15926-1:2004, definition 3.1.1.
2.1.3
class template
template for making statements about classes
2.1.4
conceptual data model
datamodelinthethreHschemaarchitecturedefined LQISO/TR9007,inwhichthestructureofdatais
representedinaformindependentofanyphysicalstorageorexternalpresentationformat
2.1.5
core class
class that is a commonly used subdivision corresponding to terms used in common language
NOTE The conditions for membership are often not formally defined; understanding of the class may be conveyed by exam-
ple.
EXAMPLE Pipe, floor, pump, and light bulb are all core classes.
[ISO 15926-1:2004, definition 3.1.4]
2.1.6
core template
RDL template for which all reference data items in the expansion of its template axiom are core classes
2.1.7
data store
computer system that allows data to be stored for future reference
[ISO 15926-1:2004, definition 3.1.6]
2.1.8
data type
domain of values
[ISO 10303-11:2004, definition 3.3.5]
2.1.9
data warehouse
data store in which related data are merged to provide an integrated set of data containing no duplication
or redundancy of information, and which supports many dierent application viewpoints
[ISO 15926-1:2004, definition 3.1.7]
2.1.10
document
thing serving as a representation of information by means of symbolic marks
NOTE Theword“document”isusedinawidersense.Nexttotheinformationcontentofcustomary(paper)documents(not
apaperdocumentitself,becausethatisaninstanceofPhysicalObject),suchasequipmentdatasheetsorpurchaseorders,it
canalsobeusedforothersetsofdata,likethetransactiondatathatareinputtoanengineeringprogramordatasetsthatare
exchangedbetweensystemsofbusinesspartners
c ISO 2011 — All rights reserved

2.1.11
entity
class of information defined by common properties
[ISO 10303-11:2004, definition 3.3.6]
2.1.12
entity instance
named unit of data which represents a unit of information within the class defined by an entity
NOTE 1 It is a member of the domain established by an entity data type.
NOTE 2 Adapted from ISO 10303-11:2004, definition 3.3.8.
2.1.13
first-order logic
symbolized reasoning in which each sentence, or statement, is broken down into a subject and a predicate
NOTE 1 The predicate modifies or defines the properties of the subject. In first-order logic, a predicate can only refer to a
single subject.
NOTE 2 First-order logic is also known as first-order predicate calculus or first-order functional calculus.
2.1.14
individual template
template for making statements about individuals
2.1.15
instance
named value
[ISO 10303-11:2004, definition 3.3.10]
2.1.16
ISO 15926-2 language
first-order language in which the ISO 15926-2 data model is expressed
NOTE The ISO 15926-2 language is specified in 4.1.
2.1.17
life-cycle information
informationaboutapossibleindividual,collectedatanypointintimeduringthelife-cycleofthatindi-
vidual
NOTE InISO15926-2:2003,definition3.1.6,³individual´isdefinedas:“thingthatexistsinspaceandtime”.
2.1.18
RDL template
template with at least one reference data item in the expansion of its template axiom

c ISO 2011 — All rights reserved 3

2.1.19
reference data
process plant life-cycle data that represents information about classes or individuals which are common
to many process plants or of interest to many users
[ISO 15926-1:2004, definition 3.1.18]
2.1.20
reference data library
RDL
managed collection of reference data
[ISO 15926-1:2004, definition 3.1.19]
NOTE In ISO/TS 15926-8 “RDL” and “ontology” are used interchangeably. An alternative term is “information model”.
2.1.21
reification
modelling style in which a relationship is expressed as an object class
EXAMPLE TherelationEmployed-byisreifiedbytheobjectEmploymentwhichisconnectedtotheobjectsEmployeeand
Organization.Themeaningoftherelationwithcardinalitiesatbothendsis“anorganizationhaszeroormoreemployees”.
ThereifiedEmploymentobjectcanbesubjectinotherrelations,definingit.
NOTE The relational entity types of ISO 15926 are all the entity types which have exactly two attributes, except
class of relationship.
2.1.22
template
set comprising of a first-order logic predicate for which a definition is stated as an axiom, a template
signature and a template axiom expansion
2.1.23
template expansion
template axiom expansion
statement expressed in ISO 15926-2 entity data types, equivalent to a template axiom
NOTE The expansion of a template axiom refers to a typically complex, biconditional in the ISO 15926-2 language. It is
obtained by repeated application of template biconditionals until the template’s interpretation is expressed directly in terms of
simple ISO 15926-2 language constructions.
2.1.24
template instance expansion
set of simple statements in the ISO 15926-2 language, obtained by instantiating variables in the expanded
template axiom with entity instances
2.1.25
template axiom
axiom in the template language defining the interpretation of template statements
2.1.26
template instance
ordered list of entity instances of which a template is true
c ISO 2011 — All rights reserved

2.1.27
template language
axioms in first-order logic extending the ISO 15926-2 data model
2.1.28
template role
named and numbered argument in a template with required type given as entity type, data type, or
reference data class
EXAMPLE TemplateInstanceOfIndirectProperty(a,b,c)meansthataisaClassOfIndirectProperty,ba(temporalpartof)
PossibleIndividualtowhichtherelationappliesandctheinstanceofProperty. bhasaQatypeofClassOfIndirectProperty,
whichhasDcinstanceofProperty.Ithasthefollowingroles:
a) role name: Property type;
b) role name: Property possessor;
c) role name: Property.
2.1.29
template signature
named, ordered and typed list of template roles
EXAMPLE TemplateInstanceOfIndirectProperty(a,b,c)meansthataisaClassOfIndirectProperty,ba(temporalpartof)
PossibleIndividualtowhichtherelationappliesandctheinstanceofProperty. bhasaQatypeofClassOfIndirectProperty,
whichhasDcinstanceofProperty.Thetemplatesignatureis:
a) role name: Property type, role type: ClassOfIndirectProperty;
b) role name: Property possessor, role type: PossibleIndividual;
c) role name: Property, role type: Property.
2.1.30
template statement
statement made by instantiating the roles of a template with entity instances
2.1.31
value
unit of data
[ISO 10303-11:2004, definition 3.3.22]
2.2 Abbreviated terms
FOL first order logic
DL description logic
RDL reference data library
c ISO 2011 — All rights reserved 5

3 Fundamental concepts and assumptions
3.1 General
The ISO 15926-2 data model is generic and highly normalized. Whilst this enables considerable flexi-
bility in what can be said, it can also give rise to complexity in how it is said. This part of ISO 15926
specifies templates that are expressions of predefined units of semantics allowing the use of the model in
a convenient way. The approach taken in this part of ISO 15926 is based on the architecture described in
ISO/TS 18876-1 and is illustrated in Figure 1.
3.2 Concepts and models
The concepts and models shown in Figure 1 are implemented in this part of ISO 15926.
Figure 1 — An overview of the integration architecture of ISO/TS 18876-1
3.2.1 ISO 15926-2 data model
The foundation concepts are represented in ISO 15926-2 by a generic, conceptual data model that is
suitable as the basis for implementation in a shared database or data warehouse. The data model is
designed to be used in conjunction with reference data. The support for a specific life-cycle activity
depends on the use of appropriate reference data in conjunction with the data model (see 4.1).
The ISO 15926-2 EXPRESS model is translated in this part of ISO 15926 into first order logic (FOL),
with each entity type translated into an unary predicate, and each attribute translated into a binary predi-
cate (see 4.1).
c ISO 2011 — All rights reserved

3.2.2 ISO/TS 15926-4 reference data
ISO/TS 15926-4 provides reference data that defines a taxonomy of core classes representing the entity
data types defined in ISO 15926-2.
For this part of ISO 15926, reference data is treated as constant terms in the sense of first order logic. The
notion of reference data instantiating the entity types of the data model is thereby reduced to truth of first
order representations of ISO 15926-2 entity types about constant reference terms, or, for ISO 15926-2
attributes, ordered pairs of terms.
EXAMPLE 1 A template makes a relation between an instance of PUMP, an identifying string “PU101” and an identification
type TAG NUMBER.
ClassifiedIdentification(myPump; “PU101 ; TagNumber)
These three terms are reference data, and the template is defined in first order logic.
When an implementation verifies the template, the entity types of the reference data are checked by lifting the template, and
these reference data are treated as constants while testing this verification to be true or false.
3.2.3 User-defined taxonomy
Where the ISO/TS 15926-4 taxonomy defines the general concepts in Figure 1, a user organization often
needs to define discipline-specific concepts. These are defined in the form of specializations of the
general concepts in the ISO/TS 15926-4 taxonomy.
EXAMPLE CP-834833 (‘Model AK/150 pump’) is a specialized class in the supplier catalog of the XYZ Corporation. This
supplier-owned class resides in the RDL of the supplier, but the class must be a specialization of another class, following the
taxonomy up the tree until inside the ISO/TS 15926-4 taxonomy.
3.2.4 Templates
Templates (see Clauses 4 and 5), defined in this part of ISO 15926 and in user-defined specializations
form the “derived concepts” in Figure 1.
4 Modelling basics
4.1 ISO 15926-2 data model in first-order logic
This clause defines the ISO 15926-2 language, a formulation of ISO 15926-2, as standardized in EX-
PRESS format, in first order logic. This language serves for this part of ISO 15926 as the expression of
the ISO 15926 data model.
In ISO 15926-2 EXPRESS, names of entity types and attributes are written in lower case with the
character dividing the words in names. For the ISO 15926-2 language, entity type and attribute names
shall be written in upper camel case, with attributes given an additional prefix “has”. For example, the
entity typeclass of class of relationship is named ClassOfClassOfRelationship, and the attribute
shape dimension is named hasShapeDimension in this part of ISO 15926.
In the ISO 15926-2 language, entity types are represented as unary first-order predicates. Let a be an
EXPRESS entity type. This shall be represented in the ISO 15926-2 language as
A(x)
where A(c) is true i (if and only if) c is an instance of a.

c ISO 2011 — All rights reserved 7

Attributes shall be represented in the ISO 15926-2 language as binary predicates: with r an EXPRESS
attribute, this becomes
hasR(x; y)
with the interpretation that hasR(c; d) is true i the value of the attribute of r of the entity instance c is d.
NOTE 1 The reason for adding the prefix has to attributes is that some names in the EXPRESS implementation of ISO 15926-
2 are used for both entity types and attributes. The prefix is needed because entities and attributes occupy dierent namespaces
in EXPRESS, but the same namespace in the ISO 15926-2 language. Use of this convention allowes a consistent mapping to
be used while avoiding collisions.
In EXPRESS models the native datatypes are usually written in upper case, e.g., INTEGER. In the
ISO 15926-2 language these datatypes shall also be written in upper case, e.g., INTEGER. All EX-
PRESS native datatypes except LIST shall be represented as unary predicates. If A is an EXPRESS
datatype, write
A(x)
with the interpretation that A(c) is true i c is of datatypeA.
The use of LIST in ISO 15926-2 is limited to the definition of the entity types
multidimensional object and class of multidimensional object. In this part of ISO 15926,
these types are considered part of the definition of the template language. Therefore LIST is not itself a
predicate of the ISO 15926-2 language.
Subtyping among entity types in EXPRESS shall be represented in the ISO 15926-2 language by condi-
tionals. If a is a subtype of b, the ISO 15926-2 language states that allas arebs:
A(x)! B(x)
TheABSTRACT entity types of ISO 15926-2 are represented in the ISO 15926-2 language by stating that
every instance of an abstract entity type also instantiates at least one of the immediate subtypes of the
abstract entity type. If the entity typea isABSTRACT andb,c andd are all the immediate subtypes of a,
then the fact thata is abstract is represented in FOL as follows.
A(x)! (B(x)_ C(x)_ D(x))
^(B(x)! A(x))
^(C(x)! A(x))
^(D(x)! A(x))
ISO 10303-11 describesONEOF statements as follows.
The ONEOF constraint states that the populations of the operands in the ONEOF list are mu-
tually exclusive; no instance of any of the populations of the operands in the ONEOF list shall
appear in the population of any other operand in the ONEOF list. The ONEOF constraint may
be combined with the other supertype constraints to enable the writing of complex constraints.
When an ONEOF constraint occurs as an operand in another constraint, it represents the set of
entity instances that is the union of the populations of the operands in the ONEOF list.
[ISO 10303-11:2004, 9.2.5.2]
ONEOF statements are represented as disjointness axioms in the ISO 15926-2 language. The EXPRESS
c ISO 2011 — All rights reserved

statementONEOF(a, b, c) is represented with the following formula.
:(A(x)^ (B(x))
^:(A(x)^ (C(x))
^:(B(x)^ (C(x))
EXPRESS attributes are represented as binary predicates in FOL. The set of allowable values in the first
position of a binary predicate is called the domain and the set of allowable values in the second position
the range.
NOTE 2 EXPRESS attributes are often called “roles”.
The set of ISO 15926-2 entity types to which an attribute applies is represented in the ISO 15926-2
language by a restriction on the domain of the binary predicate representing the attribute. If the attribute
r is defined for the entity typesa andb, write
hasR(x; y)! (A(x)_ B(x)):
The set of allowable values of an attribute is represented in the ISO 15926-2 language by restricting
the range of the binary predicate representing the attribute. In EXPRESS, attribute values are always
restricted with respect to a given entity type. These restrictions are represented by local range restrictions
in the ISO 15926-2 language, meaning that a range restriction always includes a domain restriction of
the binary predicate.
Suppose r is an attribute, for which values are limited to entity type f for the entity type a, and to g for
entity typeb. In the ISO 15926-2 language this shall be written as follows:
A(x)^ hasR(x; y)! F(y)
B(x)^ hasR(x; y)! G(y)
Every attribute in the EXPRESS implementation of ISO 15926-2 has a cardinality constraint [0; 1] or
[1; 1]. Cardinality constraints for attributes are given per entity type, as for range restrictions. Cardinality
constraints on binary predicates are represented using two axioms. Suppose that the attribute r has
cardinality constraint [1; 1] for the entity type a. In the ISO 15926-2 language this shall be written as a
pair of axioms:
A(x)!9y(hasR(x; y)) (1)
A(x)^ hasR(x; y)^ hasR(x; z)! y = z (2)
Formula (1) represents the cardinality constraint [1;). The second axiom represents the cardinality
constraint [0; 1]. Together they express the cardinality constraint [1; 1]. A cardinality constraint [0; 1] is
represented by a formula of the form (2) only.
Where an attribute is restricted by an EXPRESSUNIQUE rule, this shall be represented in the ISO 15926-
2 language by requiring that the predicate is inverse functional. If attribute r is UNIQUE for the entity
typeA write:
A(x)^ A(y)^ hasR(x; z)^ hasR(y; z)! x = y:
The set of axioms of the ISO 15926-2 language is listed in Annex B.
NOTE 3 The set of axioms has been proven to be logically consistent by the use of an FOL model checker.

c ISO 2011 — All rights reserved 9

4.2 Logical template definition
This clause defines logical templates. Templates as defined in Clause 5 additionally have signatures,
which will not be discussed here.
Given a first-order formula  which uses the predicate names of the ISO 15926-2 language axiomati-
sation for a basic language, a logical template definition over  is a formula of first order logic of the
form:
N(x; y;:::)$
where N <  is a predicate symbol called the name of the template, x; y;::: are pairwise dierent vari-
ables called the formal arguments, and is a^-_-9-formula over symbols in  and containing only the
formal arguments x; y;::: as free variables, and which is called the body of the template.
The Set TS ( ) of logical template sets over  is inductively defined as the least set such that
0 0
— ;2 TS ( ) is a logical template set over  .
0 0
— If S 2 TS ( ) is a logical template set over  , and d is a logical template definition over  [
0 0 0
names(S ), then S[fdg2 TS ( ) is also a logical template set over 
0 0
where names(S ) :=fNj N(:::)$2 Sg is the set of names of templates defined in S .
NOTE The intuition behind template sets is as follows: To ensure that template expansion terminates, we want to forbid
sets of cyclic template definitions, e.g. where a template A gets expanded to a formula containing a template B, which in turn
gets expanded to a formula containing A. Our definition ensures that a template definition N(:::)$  can only be added to a
template set if all templates named in have previously been defined without reference to N.
EXAMPLE The set of definitions
f A(x) $ 9y:( B(y)^ R(x; y) );
B(x) $ C(x)_ D(x) g
is a valid template set, but
f A(x) $ 9y:( B(y)^ R(x; y) );
B(x) $ C(x)_ A(x) g
is not.
4.3 Proto-templates
Proto-templates are a very basic form of templates. They provide a layer of abstraction immediately
above the relational entity types of ISO 15926-2 by hiding the reifi
...