IEC 61970-401:2022描述了如何构建和创建IEC 61970-450（所有部件）、IEC 61970-600（所有部件）配置文件规范。配置文件规范描述了专用于特定数据交换的规范CIM的子集。IEC 61970 300（所有部分）以及IEC 61968-11中描述了规范CIM。 创建或扩展规范CIM的规则超出了本文档的范围。 本文档指定了配置文件规范的结构以及从规范CIM中选择信息子集的规则。它标准化了用于从规范CIM创建概要文件元素的操作。由于规范CIM是在UML中描述的，操作是根据UML类、属性和角色来描述的。 可以将UML映射到RDFS或OWL，因此可以使用UML、RDFS或OWL中的任何一种语言来描述创建的概要文件。用于描述概要文件的语言（UML、RDFS或OWL）的规范以及如何在用户界面中呈现和编辑概要文件超出了本文档的范围。用于描述简档的语言在其他规范中指定。相关质量标准参见第2条。 UML支持添加自由文本来描述对UML构造的进一步限制，例如类、属性值、关联角色和基数。OCL和SHACL等语言致力于描述约束。OCL用于描述UML中描述的对象数据的约束，而SHACL用于描述RDFS或OWL描述的图形数据的约束。OCL在本文档的范围内，但SHACL不在。 本文档支持描述作为CIMXML数据集或消息交换的数据的概要文件。范围内的交换格式符合IEC 61970-552，但其他格式也是可能的。 工具互操作性和序列化格式超出了本文档的范围。 第一版取消并取代了2005年发布的IEC TS IEC 61970-401。本版构成技术修订版。 与上一版相比，此版本包括以下重大技术变更: a)先前版本的IEC TS 61970-401:2005提供了组件接口规范(CI)IEC 61970-402、IEC 61970-403、IEC 61970-404、IEC 61970-405和IEC 61970-407的概述。IEC 61970-402至IEC 61970-407是OPC基金会现有OPC接口和OMG DAIS/HDA接口的副本。因此，IEC 61970-402至IEC 61970-407已被撤回，IEC TS 61970-401:2005不再有用。 b)IEC 61970-401(本文档)不包含组件接口规范(CI)的概述，而是描述如何创建描述数据集内容(或消息内容)的简档规范。因此，它被重新命名为“配置文件框架”。配置文件规范IEC 61970-450（所有部分）和IEC 61970-600（所有部分）描述了数据集内容。本文档的目的是定义在创建配置文件规范的过程中要遵循的规则。

IEC 61970-401:2022 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.
This first edition cancels and replaces IEC TS IEC 61970-401 published in 2005. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) The previous edition of IEC TS 61970-401:2005 provided an overview of the Component Interface Specifications (CIS) IEC 61970-402, IEC 61970-403, IEC 61970-404, IEC 61970-405, and IEC 61970-407. IEC 61970-402 to IEC 61970-407 are duplicates of existing OPC interfaces from OPC Foundation and the DAIS/HDA interfaces from OMG. Hence IEC 61970-402 to IEC 61970-407 have been withdrawn and IEC TS 61970-401:2005 no longer serves a purpose.
b) IEC 61970-401 (this document) does not contain an overview of Component Interface Specifications (CIS) but instead a description of how to create profile specifications that describes dataset contents (or message contents). Hence it has been renamed "Profile framework". The profile specifications IEC 61970-450 (all parts) and IEC 61970-600 (all parts) describe dataset contents. The purpose of this document is to define the rules to be followed in the process of creating profile specifications.