scope:

The IEC 61970-401 document describes how the IEC 61970-450 to -499, IEC TS 61970-600 and IEC 61970-600 profile standards as well as any other CIM based profile specifications are structured and created. Profile documents describe a subset of the canonical CIM dedicated to a specific data exchange, the canonical CIM is described in the IEC 61970-300 series documents as well as the IEC 61968-11. Rules for creation of canonical CIM is outside the scope of this document. The IEC 61970-401 document specifies the structure of a profile specification and the rules for creating the subsets from the canonical CIM. The guiding principle for the profiling method is that the information described by a profile is a true subset of the canonical CIM and retain class, role and attribute names from the canonical CIM. The data types in CIM are described by classes stereotyped Primitive or CIMDatatype that is a composition of three attributes value, unit and multiplier. The main objective being that different datasets (see section 3) exchanged using different profiles based on canonical CIM solely rely on the definitions and basic principles of the canonical CIM which is a key to make interoperability efforts feasible. This also enables different profiles to relate data between them by using the canonical CIM as a hub and supports a reader of a data set or a message to easily find descriptions of elements in both the profile and the canonical CIM. The support for relating data in different data sets or messages described by different profiles is required when data is divided across different data sets governed by different profiles. Such use cases are defined for network models where the network description is separated from the operational conditions of the network (seen as an input) and the results. There are several languages that can describe profiles, e.g. UML (serialized as XMI), RDFS, Ecore or OWL. UML includes a graphical language that is implemented by UML editors. OWL ...