FileHeaderProfile The package describes the profile for the exchange of power system model data according to IEC 61970-552. It contains extensions used for data exchanges based on IEC 61970-600. Statements It represent a set of Definition and/or Description elements. Compound rdf subject Statement subject. String A string consisting of a sequence of characters. The character encoding is UTF-8. The string length is unspecified and unlimited. Primitive predicate Statement predicate. object Statement object. DifferenceModel It represents the difference model header. The content is described by the Model class, the association role forwardDifferences and association role reverseDifferences. Both association roles may have one set of Statements. dm preconditions A property of the difference model whose value is the collection of precondition statements. reverseDifferences A property of the difference model whose value is the collection of reverse difference statements. forwardDifferences A property of the difference model whose value is a collection of statements (i.e., resources of type rdf:Statement) representing the forward difference statements. FullModel It represents the full model header and its contents is described by the Model class. md Model A Model is a collection of data describing instances, objects or entities, real or computed. In the context of CIM the semantics of the data is defined by profiles. Hence a model can contain equipment data, power flow initial values, power flow results etc. The Model class describes the header content that is the same for the FullModel and the DifferenceModel. A Model is identified by an rdf:about attribute. The rdf:about attribute uniquely describe the model data and not the CIMXML document. A new rdf:about identification is generated for created documents only when the model data has changed. A repeated creation of documents from unchanged model data shall have the same rdf:about identification as previous document generated from the same model data. md created The date and time when the model was created. It is the time of the serialization. The format is an extended format according to the ISO 8601-2005. European exchanges shall refer to UTC, e.g. <md:Model.created>2014-05-15T17:48:31.474Z</md:Model.created>. DateTime Date and time as "yyyy-mm-ddThh:mm:ss.sss", which conforms with ISO 8601. UTC time zone is specified as "yyyy-mm-ddThh:mm:ss.sssZ". A local timezone relative UTC is specified as "yyyy-mm-ddThh:mm:ss.sss-hh:mm". The second component (shown here as "ss.sss") could have any number of digits in its fractional part to allow any kind of precision beyond seconds. Primitive description A description of the model, e.g. the name of person that created the model and for what purpose. The number of UTF-8 characters is limited to 2000. modelingAuthoritySet A URN/URI referring to the organisation role / model authority set reference. The organization role is the source of the model. It is the same for all profiles part of a model exchange. URI URI is a string following the rules defined by the W3C/IETF URI Planning Interest Group in a set of RFCs of which one is RFC 3305. Primitive European scenarioTime The date and time that this model represents, i.e. for which the model is valid. The format is an extended format according to the ISO 8601-2005. European exchanges shall refer to UTC, e.g. <md:Model.scenarioTime>2030-01-15T17:00:00.000Z</md:Model.scenarioTime>. profile URN/URI describing the profiles that governs this model. It uniquely identifies the profiles and its version, e.g. http://iec.ch/TC57/61970-456/SteadyStateHypothesis/2/0. version The version of the model. If the instance file is imported and exported with no change the version number is the kept same. The version changes only if the content of the file changes. It is the same logic as for the header id. The version is the human readable id. Integer An integer number. The range is unspecified and not limited. Primitive DependentOn A reference to the model documents that the model described by this document depends on. In general there can be 0 or many Model.DependentOn depending on the profile and the content of the instance file. For instance: – A load flow solution depends on the topology model it was computed from – A topology model computed by a topology processor depends on the network model it was computed from. The referenced models are identified by the FullModel rdf:about attribute for full model documents and by DifferenceModel rdf:about attribute for difference model documents. The references are maintained by the producer of the CIMXML document and the references are valid for the model with version and identifier for which the document was created. Yes Depending All documents depending on the model described by this document. This role is not intended to be included in any document exchanging instance data. No Supersedes When a model is updated the resulting model supersedes the models that were used as basis for the update. Hence this is a reference to the CIMXML documents which are superseded by this model. A model (or instance file) can supersede 1 or more models, e.g. a difference model or a full model supersede multiple models (difference or full). In this case more than one Model.Supersedes are included in the header. The referenced document(s) is (are) identified by the URN/MRID/UUID in the FullModel rdf:about attribute when full model(s) is (are) referenced and by the URN/MRID/UUID in the DifferenceModel rdf:about attribute when difference model(s) is (are) referenced. Yes SupersededBy All models superseding this model. This role is not intended to be included in any document exchanging instance data. No