This document describes how IEC 61970-450 (all parts), IEC 61970-600 (all parts) profile specifications are structured and created. Profile specifications describe a subset of the Canonical CIM dedicated to a specific data exchange. The Canonical CIM is described in IEC 61970-300 (all parts) as well as in IEC 61968-11. Rules for creation or extension of Canonical CIM are outside the scope of this document. This document specifies the structure of a profile specification and the rules for selecting subsets of information from the Canonical CIM. It standardizes the operations used to create the profile elements from the Canonical CIM. As Canonical CIM is described in UML the operations are described in terms of UML classes, attributes, and roles. It is possible to map UML to RDFS or OWL, so any of the languages UML, RDFS or OWL can be used to describe the created profiles. Specification of languages (UML, RDFS or OWL) used to describe profiles as well as how profiles are presented and edited in user interfaces are outside the scope of this document. Languages used to describe profiles are specified in other specifications. Relevant specifications are referenced in Clause 2. UML supports adding free text that describes further restrictions on UML constructs, e.g. classes, attribute values, association roles and cardinalities. Languages such as OCL and SHACL are dedicated to describing constraints. OCL is used to describe constraints for object data described in UML while SHACL is used to describe constraints on graph data described by RDFS or OWL. OCL is within the scope of this document, but SHACL is not. This document supports profiles describing data exchanged as CIMXML datasets or messages. The exchange format within the scope is in accordance with IEC 61970-552 but other formats are possible. Tool interoperability and serialisation formats are outside the scope of this document.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 5<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4 Overview 4.1 Profiles and profiling Tables Table 1 \u2013 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Figures Figure 1 \u2013 Relations between standards and profiling <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 4.2 Relations between Canonical CIM, profiles and datasets Figure 2 \u2013 Relation between Canonical CIM, profiles and datasets <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.3 Profiles and business processes <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5 Profile document structure 6 Profiling Use cases 6.1 Overview <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.2 Class in different profiles with no overlap Figure 3 \u2013 Class in different profiles with no overlap <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.3 Include overlapping sets of attributes and roles from the same class in different profiles 6.4 Include a base class with different sets of attributes or roles 6.5 Extending an existing class Figure 4 \u2013 Class in different profiles with overlap Figure 5 \u2013 Same base class with different sets of attributes or roles <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.6 Extending an existing class used differently in different profiles 6.7 Different cardinalities Figure 6 \u2013 Extending a class the same way in all applicable profiles Figure 7 \u2013 Extending an existing class used differently in different profiles <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.8 Add a new datatype 7 Profiling rules 7.1 Overview 7.2 R0101 Information model class, attribute, role and datatype names 7.3 Class rules for classes without stereotype 7.3.1 R0201 Including a class 7.3.2 R0202 Adding a new class 7.3.3 R0203 The description of a class 7.3.4 R0204 Name of a class 7.3.5 R0205 Cardinality of a class <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.3.6 R0206 Concrete class 7.4 Attribute rules 7.4.1 R0301 Including an attribute 7.4.2 R0302 Adding a new attribute 7.4.3 R0303 The description of an attribute 7.4.4 R0304 The name of an attribute 7.4.5 R0305 The cardinality of an attribute 7.4.6 R0306 The datatype of an attribute 7.4.7 R0307 Initial value of an attribute <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.5 Datatypes 7.5.1 R0401 Including a datatype 7.5.2 R0402 Adding a new datatype 7.5.3 R0403 Primitive datatype 7.5.4 R0405 CIMDatatype 7.5.5 R0405 Compound datatype 7.5.6 R0406 Enumeration 7.5.7 R0407 The description of a datatype 7.5.8 R0408 The name of a datatype <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.6 Association rules 7.6.1 R0501 Including an association 7.6.2 R0502 Adding a new association 7.6.3 R0503 The names of the two roles in an association 7.6.4 R0504 The cardinality of an association role 7.6.5 R0505 Association navigability 7.6.6 R0506 The description of an association 7.7 Attribute and association restrictions 7.7.1 R0601 Overlap between profiles <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 7.7.2 R0602 Same base class with different sets of attributes and associations in different profiles 7.8 R0701 Inheritance structure 7.9 R0801 Constraints <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 8 Extending Canonical CIM 9 Requirements for a profiling tool 9.1 Minimum requirements <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 9.2 Extended requirements for OCL rules <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Annex A (informative) A.1 Mapping of UML to OWL A.2 Units and multipliers issue A.2.1 Description of issue Table A.1 \u2013 UML and ontology languages <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Figure A.1 \u2013 CIMDatatype example in Canonical CIM and SSH profile <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Figure A.2 \u2013 ActivePower from IEC 61970-452:2021 (CIM16) Figure A.3 \u2013 Profile for ActivePower including CIMDatatype attributes <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Figure A.4 \u2013 CIMXML example with an ActivePower instance as an identified node Figure A.5 \u2013 CIMXML example with an ActivePower blank node serialisation example Figure A.6 \u2013 Profile for ActivePower based on CIM version 9 (CIM9) Figure A.7 \u2013 CIMXML example with an ActivePower instanceaccording to the original serialisation <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | A.2.2 Long term solution A.2.3 Medium term solution <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | A.2.4 Temporary solution by flattening the profiles A.2.5 Temporary solution by fattening the CIMXML data Figure A.8 \u2013 Example of Flattened profile for ActivePower <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | A.2.6 Maintaining information for a flattened profile <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Energy management system application program interface (EMS-API) – Profile framework<\/b><\/p>\n |