@prefix rdf: . @prefix owl: . @prefix rdfs: . @prefix xml: . @prefix xsd: . a owl:Ontology; "urn:iso:std:iec:61970-501:draft:ed-2", "urn:iso:std:iec:61970-301:ed-7:amd1", "urn:iso:std:iec:61970-401:draft:ed-1", "file://iec61970cim17v40_iec61968cim13v13a_iec62325cim03v17a.eap", "file://CIM17-2_CGMES31v01_PROF-20v03_NC25v25_MS10v12_DES10v01.eap", "urn:iso:std:iec:61970-600-2:ed-1"; "ENTSO-E CIM WG NC project"@en; "This vocabulary is describing the contingency profile."@en; "cedb9de6-01a3-45aa-95e7-2331dce2d4de"; "CO"; "en-GB"; "https://www.apache.org/licenses/LICENSE-2.0"@en; "2026-08-05"^^xsd:date; owl:priorVersion ; "ENTSO-E"@en; "ENTSO-E"@en; "vocabulary"@en; "Contingency Vocabulary"@en; owl:versionIRI ; owl:versionInfo "2.3.5"@en . a rdfs:Class; ; rdfs:comment "A type with the value space \"true\" and \"false\"."; rdfs:label "Boolean"@en; "Primitive" . a rdfs:Class; ; rdfs:comment "An event threatening system reliability, consisting of one or more contingency elements."; rdfs:label "Contingency"@en; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Kinds of occurrence criteria of application."; rdfs:label "ContingencyConditionKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "An element of a system event to be studied by contingency analysis, representing a change in status of a single piece of equipment. "; rdfs:label "ContingencyElement"@en; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Equipment whose in service status is to change, such as a power transformer or AC line segment."; rdfs:label "ContingencyEquipment"@en; ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Indicates the state which the contingency equipment is to be in when the contingency is applied."; rdfs:label "ContingencyEquipmentStatusKind"@en; . a rdfs:Class; ; rdfs:comment "Date as \"yyyy-mm-dd\", which conforms with ISO 8601. UTC time zone is specified as \"yyyy-mm-ddZ\". A local timezone relative UTC is specified as \"yyyy-mm-dd(+/-)hh:mm\"."; rdfs:label "Date"@en; "Primitive" . a rdfs:Class; ; rdfs:comment "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."; rdfs:label "DateTime"@en; "Primitive" . a rdfs:Class; ; rdfs:comment "The parts of a power system that are physical devices, electronic or mechanical."; rdfs:label "Equipment"@en . a rdfs:Class; ; rdfs:comment "Exceptional contingency means the simultaneous occurrence of multiple contingencies with a common cause."; rdfs:label "ExceptionalContingency"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "A floating point number. The range is unspecified and not limited."; rdfs:label "Float"@en; "Primitive" . a rdfs:Class; ; rdfs:comment """An IRI (Internationalized Resource Identifier) within an RDF graph is a Unicode string that conforms to the syntax defined in RFC 3987. The primitive is serialized as rdf:resource in RDFXML. IRIs in the RDF abstract syntax must be absolute, and may contain a fragment identifier. IRI equality: Two IRIs are equal if and only if they are equivalent under Simple String Comparison according to section 5.1 of [RFC3987]. Further normalization must not be performed when comparing IRIs for equality. IRIs are a generalization of URIs [RFC3986] that permits a wider range of Unicode characters. Every absolute URI and URL is an IRI, but not every IRI is an URI. When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in section 3.1 of [RFC3987]. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names."""; rdfs:label "IRI"@en; "Primitive", "profcim" . a rdfs:Class; ; rdfs:comment "This is a root class to provide common identification for all classes needing identification and naming attributes."; rdfs:label "IdentifiedObject"@en . a rdfs:Class; ; rdfs:comment "Ordinary contingency means the occurrence of a contingency of a single branch or injection."; rdfs:label "OrdinaryContingency"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Out of range means the simultaneous occurrence of multiple contingencies without a common cause, or a loss of power generating modules with a total loss of generation capacity exceeding the reference incident."; rdfs:label "OutOfRangeContingency"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Percentage on a defined base. For example, specify as 100 to indicate at the defined base."; rdfs:label "PerCent"@en; "CIMDatatype" . a rdfs:Class; ; rdfs:comment "A configuration or a set of events executed during a simulation."; rdfs:label "SimulationEvents"@en . a rdfs:Class; ; rdfs:comment "A string consisting of a sequence of characters. The character encoding is UTF-8. The string length is unspecified and unlimited."; rdfs:label "String"@en; "Primitive" . a rdfs:Class; ; rdfs:comment """A string consisting of a sequence of characters. The character encoding is UTF-8. The string length is unspecified and unlimited. The primitive is serialized as literal without language support."""; rdfs:label "StringFixedLanguage"@en; "Primitive", "profcim" . a rdfs:Class; ; rdfs:comment """An IRI (Internationalized Resource Identifier) within an RDF graph is a Unicode string that conforms to the syntax defined in RFC 3987. The primitive is serialized as literal without language support. IRIs in the RDF abstract syntax must be absolute, and may contain a fragment identifier. IRI equality: Two IRIs are equal if and only if they are equivalent under Simple String Comparison according to section 5.1 of [RFC3987]. Further normalization must not be performed when comparing IRIs for equality. IRIs are a generalization of URIs [RFC3986] that permits a wider range of Unicode characters. Every absolute URI and URL is an IRI, but not every IRI is an URI. When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in section 3.1 of [RFC3987]. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names."""; rdfs:label "StringIRI"@en; "Primitive", "profcim" . a rdfs:Class; ; rdfs:comment """A power system operation post responsible for performing and coordinating the real-time and planning functions required to maintain the secure, reliable, and efficient operation of the power system within a defined operational scope. Note: SystemOperator represents the execution of power system operational responsibilities in practice. While the operational post exists independently at the ecosystem level, SystemOperator identifies the specific agent fulfilling that responsibility at a given time. The operational scope may correspond to a control area, network, voltage domain, or other defined boundary."""; rdfs:label "SystemOperator"@en; "NC" . a rdfs:Class; ; rdfs:comment "A Uniform Resource Locator (URL), colloquially termed a web address, is a reference to a web resource that specifies its location on a computer network and a mechanism for retrieving it. A URL is a specific type of Uniform Resource Identifier (URI), although many people use the two terms interchangeably.URLs occur most commonly to reference web pages (http), but are also used for file transfer (ftp), email (mailto), database access (JDBC), and many other applications."; rdfs:label "URL"@en; "Primitive", "profcim" . a rdfs:Class; ; rdfs:comment """The unit multipliers defined for the CIM. When applied to unit symbols, the unit symbol is treated as a derived unit. Regardless of the contents of the unit symbol text, the unit symbol shall be treated as if it were a single-character unit symbol. Unit symbols should not contain multipliers, and it should be left to the multiplier to define the multiple for an entire data type. For example, if a unit symbol is \"m2Pers\" and the multiplier is \"k\", then the value is k(m**2/s), and the multiplier applies to the entire final value, not to any individual part of the value. This can be conceptualized by substituting a derived unit symbol for the unit type. If one imagines that the symbol \"Þ\" represents the derived unit \"m2Pers\", then applying the multiplier \"k\" can be conceptualized simply as \"kÞ\". For example, the SI unit for mass is \"kg\" and not \"g\". If the unit symbol is defined as \"kg\", then the multiplier is applied to \"kg\" as a whole and does not replace the \"k\" in front of the \"g\". In this case, the multiplier of \"m\" would be used with the unit symbol of \"kg\" to represent one gram. As a text string, this violates the instructions in IEC 80000-1. However, because the unit symbol in CIM is treated as a derived unit instead of as an SI unit, it makes more sense to conceptualize the \"kg\" as if it were replaced by one of the proposed replacements for the SI mass symbol. If one imagines that the \"kg\" were replaced by a symbol \"Þ\", then it is easier to conceptualize the multiplier \"m\" as creating the proper unit \"mÞ\", and not the forbidden unit \"mkg\"."""; rdfs:label "UnitMultiplier"@en; . a rdfs:Class; ; rdfs:comment """The derived units defined for usage in the CIM. In some cases, the derived unit is equal to an SI unit. Whenever possible, the standard derived symbol is used instead of the formula for the derived unit. For example, the unit symbol Farad is defined as \"F\" instead of \"CPerV\". In cases where a standard symbol does not exist for a derived unit, the formula for the unit is used as the unit symbol. For example, density does not have a standard symbol and so it is represented as \"kgPerm3\". With the exception of the \"kg\", which is an SI unit, the unit symbols do not contain multipliers and therefore represent the base derived unit to which a multiplier can be applied as a whole. Every unit symbol is treated as an unparseable text as if it were a single-letter symbol. The meaning of each unit symbol is defined by the accompanying descriptive text and not by the text contents of the unit symbol. To allow the widest possible range of serializations without requiring special character handling, several substitutions are made which deviate from the format described in IEC 80000-1. The division symbol \"/\" is replaced by the letters \"Per\". Exponents are written in plain text after the unit as \"m3\" instead of being formatted as \"m\" with a superscript of 3 or introducing a symbol as in \"m^3\". The degree symbol \"°\" is replaced with the letters \"deg\". Any clarification of the meaning for a substitution is included in the description for the unit symbol. Non-SI units are included in list of unit symbols to allow sources of data to be correctly labelled with their non-SI units (for example, a GPS sensor that is reporting numbers that represent feet instead of meters). This allows software to use the unit symbol information correctly convert and scale the raw data of those sources into SI-based units. The integer values are used for harmonization with IEC 61850."""; rdfs:label "UnitSymbol"@en; . a ; rdfs:comment "This package contains contingency profile."; rdfs:label "ContingencyProfile"@en . a ; rdfs:comment "This package contains datatypes used only in the RDFS header."; rdfs:label "DocContingencyProfile"@en . a ; rdfs:comment "Permanent occurrence factor which is design condition."; rdfs:label "design"@en; "enum" . a ; rdfs:comment "Temporary occurrence factor which is weather or environmental condition (e.g. storm)."; rdfs:label "environmental"@en; "enum" . a ; rdfs:comment "Permanent occurrence factor which is specific geographical location."; rdfs:label "geographicalLocation"@en; "enum" . a ; rdfs:comment "Temporary occurrence factor which is life time or generic malfunction affecting the risk of failure condition."; rdfs:label "malfunction"@en; "enum" . a ; rdfs:comment "Temporary occurrence factor which is operational condition."; rdfs:label "operational"@en; "enum" . a ; rdfs:comment "The equipment is to be put into service."; rdfs:label "inService"@en; "enum" . a ; rdfs:comment "The equipment is to be taken out of service."; rdfs:label "outOfService"@en; "enum" . a rdf:Property; "No"; rdfs:comment "A contingency can have any number of contingency elements."; rdfs:domain ; ; rdfs:label "ContingencyElement"@en; ; rdfs:range ; . a rdf:Property; "Yes"; rdfs:comment "System operator that is operating the equipment that is being run a contingency on."; rdfs:domain ; ; rdfs:label "EquipmentOperator"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Simulation event for a contingency."; rdfs:domain ; ; rdfs:label "SimulationEvents"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Specifies the requirement of study the contingency under normal operating conditions. True means the contingency must be study in a normal scenario. False means that the contingency does not need to be included in the scenario. This is the default value if mustStudy is missing."; ; rdfs:domain ; rdfs:label "normalMustStudy"@en; ; , "NC" . a rdf:Property; rdfs:comment """Normal probability of the occurrence of the contingency based on normal operational condition. The value is used as the default if the probability is missing. The allowed value range is [0,100]."""; ; rdfs:domain ; rdfs:label "normalProbability"@en; ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "A contingency element belongs to one contingency."; rdfs:domain ; ; rdfs:label "Contingency"@en; ; rdfs:range . a rdf:Property; "Yes"; rdfs:comment "The single piece of equipment to which to apply the contingency."; rdfs:domain ; ; rdfs:label "Equipment"@en; ; rdfs:range . a rdf:Property; rdfs:comment "The status for the associated equipment when in the contingency state. This status is independent of the case to which the contingency is originally applied, but defines the equipment status when the contingency is applied."; rdfs:domain ; rdfs:label "contingentStatus"@en; ; rdfs:range ; . a rdf:Property; "No"; rdfs:comment "The contingency equipments in which this equipment participates."; rdfs:domain ; ; rdfs:label "ContingencyEquipment"@en; ; rdfs:range . a rdf:Property; rdfs:comment "Defines the kind of relevance and criteria of application of the exceptional contingency."; rdfs:domain ; rdfs:label "kind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy."; ; rdfs:domain ; rdfs:label "description"@en; ; . a rdf:Property; rdfs:comment """Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements."""; ; rdfs:domain ; rdfs:label "mRID"@en; ; . a rdf:Property; rdfs:comment "The name is any free human readable and possibly non unique text naming the object."; ; rdfs:domain ; rdfs:label "name"@en; ; . a rdf:Property; rdfs:domain ; "none"; rdfs:label "multiplier"@en; ; rdfs:range ; . a rdf:Property; rdfs:domain ; "none"; rdfs:label "unit"@en; ; rdfs:range ; . a rdf:Property; rdfs:comment "Normally 0 to 100 on a defined base."; ; rdfs:domain ; rdfs:label "value"@en; ; . a rdf:Property; "No"; rdfs:comment "Contingency part of this simulation event."; rdfs:domain ; ; rdfs:label "Contingency"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Contingency for the equipment that is operated by the system operator."; rdfs:domain ; ; rdfs:label "Contingency"@en; ; rdfs:range ; "NC" . a ; rdfs:comment "No multiplier or equivalently multiply by 1."; rdfs:label "none"@en; "enum" . a ; rdfs:comment "Dimension less quantity, e.g. count, per unit, etc."; rdfs:label "none"@en; "enum" .