61970-301©1EC:2003 -12- 3.2 Application Program Interface (API) The set of public functions provided by an executable application component for use by other executable application components. 4 CIM Specification 4.1 CIM Modeling Notation The CIM is defined using object-oriented modeling techniques.Specifically,the CIM specification uses the Unified Modeling Language (UML)notation,which defines the CIM as a group of packages Each package in the CIM contains one or more class diagrams showing graphically all the classes in that package and their relationships.Each class is then defined in text in terms of its attributes and relationships to other classes. The UML notation is described in Object Management Group (OMG)documents and several published textbooks. 4.2 CIM Packages The CIM is partitioned into a set of packages.A package is a general purpose means of grouping related model elements.There is no specific semantic meaning.The packages have been chosen to make the model easier to design,understand and review.The Common Information Model consists of the complete set of packages.Entities may have associations that cross many package boundaries.Each application will use information represented in several packages The comprehensive CIM is partitioned into the following packages for convenience,where packagages are grouped to be handled as a single standard document as shown: IEC 61970 Part 301(this document) ·Core ●Domain Generation Generation Dynamics ·LoadMode ·Meas ·Outage 。Production 。Protection ·Topology ·Vires IEC 61970 Part 302 ·Energy Scheduling 。Financial ●Reservation 1EC61970Part303 ·SCADA61970-301  IEC:2003 – 12 – 3.2 Application Program Interface (API) The set of public functions provided by an executable application component for use by other executable application components. 4 CIM Specification 4.1 CIM Modeling Notation The CIM is defined using object-oriented modeling techniques. Specifically, the CIM specification uses the Unified Modeling Language (UML) notation, which defines the CIM as a group of packages. Each package in the CIM contains one or more class diagrams showing graphically all the classes in that package and their relationships. Each class is then defined in text in terms of its attributes and relationships to other classes. The UML notation is described in Object Management Group (OMG) documents and several published textbooks. 4.2 CIM Packages The CIM is partitioned into a set of packages. A package is a general purpose means of grouping related model elements. There is no specific semantic meaning. The packages have been chosen to make the model easier to design, understand and review. The Common Information Model consists of the complete set of packages. Entities may have associations that cross many package boundaries. Each application will use information represented in several packages. The comprehensive CIM is partitioned into the following packages for convenience, where packagages are grouped to be handled as a single standard document as shown: IEC 61970 Part 301 (this document)  Core  Domain  Generation  Generation Dynamics  LoadModel  Meas  Outage  Production  Protection  Topology  Wires IEC 61970 Part 302  Energy Scheduling  Financial  Reservation IEC 61970 Part 303  SCADA