BS EN 61970-301:2011
$215.11
Energy management system application program interface (EMS-API) – Common information model (CIM) base
Published By | Publication Date | Number of Pages |
BSI | 2011 | 266 |
This part of IEC 61970 deals with the common information model (CIM), an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations.
The object classes represented in the CIM are abstract in nature and may be used in a wide variety of applications. The use of the CIM goes far beyond its application in an EMS. This standard should be understood as a tool to enable integration in any domain where a common power system model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation.
By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of energy management system (EMS) applications developed independently by different vendors, between entire EMS systems developed independently, or between an EMS system and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA (supervisory control and data acquisition) is modeled to the extent necessary to support power system simulation and inter-control center communication. The CIM facilitates integration by defining a common language (i.e., semantics and syntax) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally.
Due to the size of the complete CIM, the object classes contained in the CIM are grouped into a number of logical packages, each of which represents a certain part of the overall power system being modeled. Collections of these packages are progressed as separate International Standards. This particular International Standard specifies a base set of packages which provide a logical view of the functional aspects of energy management system (EMS) information within the electric utility enterprise that is shared between all applications. Other standards specify more specific parts of the model that are needed by only certain applications. Subclause 4.2 provides the current grouping of packages into standard documents.
PDF Catalog
PDF Pages | PDF Title |
---|---|
7 | English CONTENTS |
17 | INTRODUCTION |
19 | 1 Scope 2 Normative references |
20 | 3 Terms and definitions 4 CIM specification 4.1 CIM modeling notation 4.2 CIM packages |
22 | Figures Figure 1 – CIM IEC 61970-301 package diagram |
24 | 4.3 CIM classes and relationships |
26 | Figure 2 – Example of generalization Figure 3 – Example of simple association |
27 | 4.4 CIM model concepts and examples Figure 4 – Example of aggregation |
29 | Figure 5 – Equipment containers |
30 | Figure 6 – Connectivity model |
31 | Figure 7 – Simple network example |
32 | Figure 8 – Simple network connectivity modeled with CIM topology |
33 | Figure 9 – Equipment inheritance hierarchy |
34 | Figure 10 – Transformer model |
36 | Figure 11 – Navigating from PSR to MeasurementValue |
37 | Table 1 – MeasurementType naming conventions |
38 | Figure 12 – Measurement placement Table 2 – MeasurementValueSource naming conventions |
39 | 4.5 Modeling guidelines Figure 13 – Regulating control models |
41 | 4.6 Modeling tools 4.7 User implementation conventions 4.8 CIM modeling examples |
42 | 5 Detailed model 5.1 Overview 5.2 Context Figure 14 – CIM top level packages |
44 | 6 Package architecture (normative) 6.1 IEC 61970 Figure 15 – Main |
45 | 6.2 Domain Figure 16 – CombinedDatatypes Figure 17 – BasicDatatypes |
46 | Figure 18 – ElectricityDatatypes |
47 | Figure 19 – EnumeratedUnitDatatypes |
48 | Figure 20 – GeneralDatatypes Figure 21 – MonetaryDatatypes |
49 | Figure 22 – TimeDatatypes |
60 | 6.3 Core |
61 | Figure 23 – Reporting |
62 | Figure 24 – Main |
63 | Figure 25 – CurveSchedule Figure 26 – Datatypes |
64 | Figure 27 – DocumentationExampleAggregation Figure 28 – DocumentationExampleAssociation Figure 29 – Ownership |
85 | 6.4 OperationalLimits Figure 30 – OperationalLimits |
86 | Figure 31 – BranchGroup |
91 | 6.5 Topology Figure 32 – TopologicalNodeTerminal |
92 | Figure 33 – TopologyMeasRelations |
93 | Figure 34 – TopologyReporting |
94 | Figure 35 – Main |
97 | 6.6 Wires |
98 | Figure 36 – DocumentationExampleInheritance |
99 | Figure 37 – MutualCoupling |
100 | Figure 38 – Datatypes |
101 | Figure 39 – InheritanceHierarchy |
102 | Figure 40 – LineModel |
103 | Figure 41 – NamingHierarchyPart1 |
104 | Figure 42 – NamingHierarchyPart2 |
105 | Figure 43 – RegulatingEquipment |
106 | Figure 44 – TransformerModel |
107 | Figure 45 – VoltageControl |
148 | 6.7 Generation ‒ Generation package summary 6.8 Production Figure 46 – Main |
149 | Figure 47 – Nuclear |
150 | Figure 48 – Main |
151 | Figure 49 – Datatypes |
152 | Figure 50 – Hydro |
153 | Figure 51 – Thermal |
188 | 6.9 GenerationDynamics Figure 52 – Main Figure 53 – Datatypes |
202 | 6.10 LoadModel |
203 | Figure 54 – Main Figure 55 – Datatypes |
217 | 6.11 Outage Figure 56 – Datatypes |
218 | Figure 57 – Main |
221 | 6.12 Protection Figure 58 – Main |
225 | 6.13 Equivalents |
226 | Figure 59 – Main |
230 | 6.14 Meas Figure 60 – Datatypes |
231 | Figure 61 – Control |
232 | Figure 62 – InheritanceStructure |
233 | Figure 63 – Measurement |
234 | Figure 64 – Quality |
250 | 6.15 SCADA Figure 65 – Datatypes |
251 | Figure 66 – Main |
255 | 6.16 ControlArea Figure 67 – ControlArea |
256 | Figure 68 – ControlAreaInheritance Figure 69 – Datatypes |
259 | 6.17 Contingency |
260 | Figure 70 – Contingency |
263 | Bibliography |