@prefix rdf: . @prefix owl: . @prefix rdfs: . @prefix xml: . @prefix xsd: . a owl:Ontology; "file://CIM17-2_CGMES31v01_PROF-20v03_NC25v25_MS10v12_DES10v01.eap", "urn:iso:std:iec:61970-600-2:ed-1", "file://iec61970cim17v40_iec61968cim13v13a_iec62325cim03v17a.eap", "urn:iso:std:iec:61970-301:ed-7:amd1", "urn:iso:std:iec:61970-501:draft:ed-2", "urn:iso:std:iec:61970-401:draft:ed-1"; "ENTSO-E CIM WG NC project"@en; "This vocabulary is describing the availability schedule profile."@en; "14c6b492-885e-4444-8123-2f649178d06c"; "AS"; "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; "Availability schedule vocabulary"@en; owl:versionIRI ; owl:versionInfo "2.4.0"@en . a ; rdfs:comment "Function is in service."; rdfs:label "inService"@en; "enum" . a ; rdfs:comment "Function is out-of-service."; rdfs:label "outOfService"@en; "enum" . a ; rdfs:comment "Function is under testing and need to expect unscheduled availability."; rdfs:label "underTesting"@en; "enum" . a ; rdfs:comment "The cause is due to a commissioning."; rdfs:label "commissioning"@en; "enum" . a ; rdfs:comment "The cause is due to a decommissioning."; rdfs:label "decommissioning"@en; "enum" . a ; rdfs:comment "The cause is due to an environmental condition. This can lead to exceptional margin and limits."; rdfs:label "environmentalCondition"@en; "enum" . a ; rdfs:comment "The cause is due to a functional control (in & out)."; rdfs:label "functionalControl"@en; "enum" . a ; rdfs:comment "The cause is due to a maintenance."; rdfs:label "maintenance"@en; "enum" . a ; rdfs:comment "The cause is of other kind."; rdfs:label "other"@en; "enum" . a ; rdfs:comment "The cause is due to a refurbishment, either upgrade or downgrade."; rdfs:label "refurbishment"@en; "enum" . a ; rdfs:comment "The cause is due to a works in proximity."; rdfs:label "worksInProximity"@en; "enum" . a ; rdfs:comment "Time series is actual data. The values represent measured or calculated values that represent the actual behaviour. "; rdfs:label "actual"@en; "enum" . a ; rdfs:comment "Time series is schedule data. The values represent the result of a committed and plan forecast data that has been through a quality control and could incur penalty when not followed."; rdfs:label "schedule"@en; "enum" . a rdfs:Class; ; rdfs:comment """Assessed element is a network element for which the electrical state is evaluated in the regional or cross-regional process and which value is expected to fulfil regional rules function of the operational security limits. The measurements and limits are as defined in the steady state hypothesis."""; rdfs:label "AssessedElement"@en; "NC" . a rdfs:Class; ; rdfs:comment "Availability container serves for associating an equipment container with an availability schedule. For instance, putting in or out of service all the equipment inside a Line or a Bay in combination with other availability functions with the same availability schedule."; rdfs:label "AvailabilityContainer"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Availability enabled is enabling or disabling grid state alteration (e.g. tap position action) or assessed element that is related to the availability schedule. For instance, the cancellation of availability schedule can lead to changes in the assessed element. This is done by enabling one assessment and disabling another."; rdfs:label "AvailabilityEnabled"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Availability equipment serves for associating an equipment with an availability schedule. For instance, putting in or out of service an ACLineSegment in combination with other availability functions with the same availability schedule."; rdfs:label "AvailabilityEquipment"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Availability exceptional limit serves for associating an operational limit restriction with an availability schedule. For instance, enabling or disabling the current limit on ACLineSegment terminal in combination with other availability functions with the same availability schedule or de-rating due to fault."; rdfs:label "AvailabilityExceptionalLimit"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Kind of availability that is affecting the function."; rdfs:label "AvailabilityFunctionKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "Container to link relevant equipment that is affected by (un)availability schedule across availability coordinator (e.g. TSO-TSO, TSO-DSO or DSO-DSO)."; rdfs:label "AvailabilityGroup"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Availability power system function describes the power system function that has a non-normal availability in the associated availability schedule. The availability of the function is needed as part of a power flow solution. This function is the cause and not the effect of the availability, if the effect can be calculated through power flow. For instance if only the step-up transformer for a generator is not available, the power flow will calculate that the generator is de-energized (outage). If both are tagged as not available it will not be possible to investigate remedial action for connecting the generator. It is expected that the power flow function is able to perform simple topology changes affected by a function taken out of service, e.g. open switches on both end of a ACLineSegment when the ACLineSegment is taken out of service. More complex changes, like change regulation set point, must be described in the linked GridStateAlterationCollection."; rdfs:label "AvailabilityPowerSystemFunction"@en; "NC"; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Availability remedial action is a remedial action that cancels or reschedules an availability schedule."; rdfs:label "AvailabilityRemedialAction"@en; "NC" . a rdfs:Class; ; rdfs:comment "Availability remedial action scheme serves for associating a remedial action scheme with an availability schedule. For instance, taking in or out of service a SIPS / SPS due to communication issue, in combination with other availability functions with the same availability schedule."; rdfs:label "AvailabilityRemedialActionScheme"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "A given (un)availability schedule with a given status and cause that include multiple equipment that need to follow the same scheduling periods."; rdfs:label "AvailabilitySchedule"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "The kinds of cause of the (un)availability schedule."; rdfs:label "AvailabilityScheduleCauseKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment """A consolidated plan established by a System Operator that groups the AvailabilitySchedules applicable to a defined period and operational scope. Note: An AvailabilityPlan provides the system-level view of resource availability used for outage coordination and operational planning. It may be divided into subordinate AvailabilityPlans and may be subject to approval by an Outage Coordinator."""; rdfs:label "AvailablityPlan"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment """A formal response provided by an affected Outage Coordinator to a specific AvailabilityPlanVersion. Note: The response records the coordinator’s position on the proposed plan, such as acceptance, refusal, acceptance with conditions, an alternative proposal, acknowledgement, or absence of a response within the applicable time limit."""; rdfs:label "AvailablityPlanResponse"@en; "NC", . a rdfs:Class; ; rdfs:comment "Time series that has irregular points in time."; rdfs:label "BaseIrregularTimeSeries"@en; "NC"; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Time series of values at points in time."; rdfs:label "BaseTimeSeries"@en; "NC"; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Kind of time series. "; rdfs:label "BaseTimeSeriesKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "A type with the value space \"true\" and \"false\"."; rdfs:label "Boolean"@en; "Primitive" . 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 kind of dependency constraint defined between the dependee and dependent peer objects. Note: The dependee is the peer object upon which another peer object depends. The dependent is the peer object whose temporal or operational behaviour is constrained by the dependee. Although dependee is not a commonly used English term, it is used here to distinguish this relationship from a parent-child hierarchy, as both objects are peer instances of the same class."""; rdfs:label "DependencyConstraintKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "Duration as \"PnYnMnDTnHnMnS\" which conforms to ISO 8601, where nY expresses a number of years, nM a number of months, nD a number of days. The letter T separates the date expression from the time expression and, after it, nH identifies a number of hours, nM a number of minutes and nS a number of seconds. The number of seconds could be expressed as a decimal number, but all other numbers are integers."; rdfs:label "Duration"@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 "A modelling construct to provide a root class for containing equipment. "; rdfs:label "EquipmentContainer"@en . a rdfs:Class; ; rdfs:comment "Time series represent irregular event described by event points in time."; rdfs:label "EventSchedule"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Event valid for a given point in time."; rdfs:label "EventTimePoint"@en; "NC", . 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 "Grid state alteration is a change of values describing state (operating point) of one element in the grid model compared to the base case."; rdfs:label "GridStateAlteration"@en; "NC" . a rdfs:Class; ; rdfs:comment "A collection of grid state alterations."; rdfs:label "GridStateAlterationCollection"@en; "NC" . 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 "An integer number. The range is unspecified and not limited."; rdfs:label "Integer"@en; "Primitive" . a rdfs:Class; ; rdfs:comment """A value and normal value associated with a specific kind of limit. The sub class value and normalValue attributes vary inversely to the associated OperationalLimitType.acceptableDuration (acceptableDuration for short). If a particular piece of equipment has multiple operational limits of the same kind (apparent power, current, etc.), the limit with the greatest acceptableDuration shall have the smallest limit value and the limit with the smallest acceptableDuration shall have the largest limit value. Note: A large current can only be allowed to flow through a piece of equipment for a short duration without causing damage, but a lesser current can be allowed to flow for a longer duration. """; rdfs:label "OperationalLimit"@en . a rdfs:Class; ; rdfs:comment """Relationship between an OutageRequest and an AvailabilitySchedule, indicating that the outage request is one of the inputs or constraints used to establish that availability schedule. Multiple outage requests may contribute to a single availability schedule, and a single outage request may be reflected in multiple availability schedules issued by the system operator."""; rdfs:label "OutageAvailability"@en; "NC", . a rdfs:Class; ; rdfs:comment "A post that coordinates the planned availability status of relevant power system equipment to meet the need by the asset owner or operator and the security of the power system."; rdfs:label "OutageCoordinator"@en; "NC" . a rdfs:Class; ; rdfs:comment """A peer temporal dependency that defines temporal or operational constraints between two outage requests. Note: The dependency constrains the start or end of the dependent outage relative to the start or end of the dependee outage. Lag constraints are evaluated using the latest applicable transition of the dependee. This supports sequencing and coordination of related outages without implying a hierarchical relationship between the outage requests. Example: - startToStartLag = 1H, startToStartLagKind = minimum: the dependent outage may start no earlier than one hour after the dependee outage starts. - finishToStartLag = 20M, finishToStartLagKind = exact: the dependent outage starts exactly 20 minutes after the dependee outage ends, for example to allow a defined switching or restoration sequence between the outages. - finishToFinishLag = 30M, finishToFinishLagKind = maximum: the dependent outage shall end no later than 30 minutes after the dependee outage ends."""; rdfs:label "OutageDependency"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "An entity with the task of planning the availability status of a relevant power generating module, a relevant demand facility or a relevant grid element."; rdfs:label "OutagePlanningAgent"@en; "NC" . a rdfs:Class; ; rdfs:comment "Represents the initial business intent to take one or more resources out of service during a specified period, as submitted by an Outage Planning Agent."; rdfs:label "OutageRequest"@en; "NC", ; rdfs:subClassOf . a rdfs:Class; ; rdfs:comment "Associates an OutageRequest with a PowerSystemResource affected by the requested outage."; rdfs:label "OutageRequestResource"@en; "NC", . a rdfs:Class; ; rdfs:comment "Represents the formal response provided by an affected agent or the outage coordinator to a specific OutageRequestVersion."; rdfs:label "OutageResponse"@en; "NC", . a rdfs:Class; ; rdfs:comment """An abstract directed dependency between two peer instances of the same domain class that defines temporal and operational constraints governing their relative execution or operation. Note: Temporal lag constraints relate the next applicable transition of the dependent to the latest applicable transition of the dependee. A dependee transition remains applicable while the dependee remains in the state resulting from that transition. If the dependee subsequently changes state before the corresponding transition of the dependent occurs, the previous transition is superseded and the constraint is evaluated from the next applicable transition. Once the corresponding transition of the dependent has occurred, the lag constraint is satisfied for that operating cycle. Each lag is qualified by its corresponding ReferenceValueKind, which specifies whether the lag represents an exact, minimum, or maximum temporal constraint."""; rdfs:label "PeerTemporalDependency"@en; "NC" . a rdfs:Class; ; rdfs:comment "A power system resource (PSR) can be an item of equipment such as a switch, an equipment container containing many individual items of equipment such as a substation, or an organisational entity such as sub-control area. Power system resources can have measurements associated."; rdfs:label "PowerSystemResource"@en . a rdfs:Class; ; rdfs:comment "Enumeration indicating the lifecycle status of a business record."; rdfs:label "RecordStatusKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "Kind of reference value."; rdfs:label "ReferenceValueKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment """Remedial Action Scheme (RAS), Special Protection Schemes (SPS), System Protection Schemes (SPS) or System Integrity Protection Schemes (SIPS). A Remedial Action Scheme consists of one or more stages that can trigger and execute a protection action."""; rdfs:label "RemedialActionScheme"@en; "NC" . a rdfs:Class; ; rdfs:comment "Classification of the response to a request. "; rdfs:label "RequestResponseKind"@en; , "NC" . a rdfs:Class; ; rdfs:comment "Time, in seconds."; rdfs:label "Seconds"@en; "CIMDatatype" . 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 "Time as \"hh:mm:ss.sss\", which conforms with ISO 8601. UTC time zone is specified as \"hh:mm:ss.sssZ\". A local timezone relative UTC is specified as \"hh: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 "Time"@en; "Primitive" . a rdfs:Class; ; rdfs:comment "Kinds of interpolation of values between two time point. "; rdfs:label "TimeSeriesInterpolationKind"@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 the availability plan profile."; rdfs:label "AvailabilityScheduleProfile"@en . a ; rdfs:comment "This package contains datatypes used only in the RDFS header."; rdfs:label "DocAvailabilityScheduleProfile"@en . a ; rdfs:comment "The dependee and dependent shall not both be active or effective at the same time."; rdfs:label "exclusive"@en; "enum" . a ; rdfs:comment "The dependent shall only be active or effective while the dependee is active or effective."; rdfs:label "inclusive"@en; "enum" . a ; rdfs:comment """The dependee constrains the dependent without requiring the dependent to become active or effective. Note: A restrictive dependency defines temporal or operational constraints on the behaviour of the dependent while leaving its activation or operation optional."""; rdfs:label "restrictive"@en; "enum" . a rdf:Property; "No"; rdfs:comment "Availability enabled describes the enabling or disabling of this assessed element."; rdfs:domain ; ; rdfs:label "AvailabilityEnabled"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Equipment container that is affected by the availability given by this availability container."; rdfs:domain ; ; rdfs:label "EquipmentContainer"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Assessed element that is affected by the availability given by this availability enabling."; rdfs:domain ; ; rdfs:label "AssessedElement"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Grid state alteration that is affected by the availability given by this availability enabling."; rdfs:domain ; ; rdfs:label "GridStateAlteration"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Instruction to enable or disable alteration and assessment."; ; rdfs:domain ; rdfs:label "enabled"@en; ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "Equipment that is affected by the availability given by this availability equipment."; rdfs:domain ; ; rdfs:label "Equipment"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Operational limit that is constrained by this availability exceptional limit."; rdfs:domain ; ; rdfs:label "OperationalLimit"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Value for the referred operational limit."; ; rdfs:domain ; rdfs:label "value"@en; ; , "NC" . a rdf:Property; "No"; rdfs:comment "All availability power system functions linked through mutual dependency with other availability power system functions controlled by other system operators."; rdfs:domain ; ; rdfs:label "AvailabilityPowerSystemFunction"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Grouping for all availability power system functions (controlled by all relevant system operators) that have the same availability schedule."; rdfs:domain ; ; rdfs:label "AvailabilityGroup"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Availability schedule for this availability power system function."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Kind of availability that affect the power system function."; rdfs:domain ; rdfs:label "kind"@en; ; rdfs:range ; , "NC" . a rdf:Property; "No"; rdfs:comment "Availability schedule that is part of the remedial action."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Remedial action scheme that is affected by the availability given by this availability remedial action scheme."; rdfs:domain ; ; rdfs:label "RemedialActionScheme"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Actual schedule that relates to this availability schedule; used for ex-post reporting and analysis (e.g., to compare planned vs. actual)."; rdfs:domain ; ; rdfs:label "ActualSchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Alternative schedule. The priority in regards to multiple alternatives is given by the priority attribute. This schedule is only relevant if all the alternatives with higher priority are cancelled."; rdfs:domain ; ; rdfs:label "AlternativeSchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "All the couplings that associate one concrete function (e.g., equipment or container, SIPS/SPSs, grid state alteration, exceptional operational limits) with the same availability schedule."; rdfs:domain ; ; rdfs:label "AvailabilityPowerSystemFunction"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Availability schedule that has a dependent availability schedule."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The AvailabilityPlan of which this AvailabilitySchedule is a component."; rdfs:domain ; ; rdfs:label "AvailablityPlan"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "(Un)availability schedule requested by one operator may require another operator to request their (un)availability schedule. This association is linking the schedules so that the dependency is clear. "; rdfs:domain ; ; rdfs:label "DependentOnSchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The grid state alteration collection that has this availability schedule."; rdfs:domain ; ; rdfs:label "GridStateAlterationCollection"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "All outage requests that contribute to the formation of this availability schedule."; rdfs:domain ; ; rdfs:label "OutageAvailability"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Planned schedule that relates to this availability schedule used for planning availability (e.g., to compare planned vs. actual)."; rdfs:domain ; ; rdfs:label "PlannedSchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Priority schedule. This is the schedule that has the highest priority and the only valid if not cancelled."; rdfs:domain ; ; rdfs:label "PrioritySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Remedial action that is cancelling this availability schedule."; rdfs:domain ; ; rdfs:label "RemedialAction"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "The date and time the (un)availability schedule were cancelled ."; ; rdfs:domain ; rdfs:label "cancelledDateTime"@en; ; , "NC" . a rdf:Property; rdfs:comment "A cause description for a cause kind. In case of CauseKind equals other, description or a reference of the cause of the (un)availability schedule."; ; rdfs:domain ; rdfs:label "causeDescription"@en; ; , "NC" . a rdf:Property; rdfs:comment "Kind of cause for the availability schedule."; rdfs:domain ; rdfs:label "causeKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service during daytime. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "daytimeRestitutionDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service after office hours. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "eveningRestitutionDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "Defines the cancelling of the availability schedule. True means that is cancelling, False means that it is not cancelling."; ; rdfs:domain ; rdfs:label "isCancelled"@en; ; , "NC" . a rdf:Property; rdfs:comment "The maximum time required to take the out-of-service equipment back into service. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "maxRestitutionDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "Value 0 means ignore priority. 1 means the highest priority, 2 is the second highest priority."; ; rdfs:domain ; rdfs:label "priority"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service in the weekend or during bank holidays. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "weekendRestitutionDuration"@en; ; , "NC" . a rdf:Property; "No"; rdfs:comment "The AvailabilitySchedules included in this AvailabilityPlan."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The Outage Coordinator responsible for approving the AvailabilityPlan."; rdfs:domain ; ; rdfs:label "AvailablityPlanApprover"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "The versions created for this AvailabilityPlan."; rdfs:domain ; ; rdfs:label "AvailablityPlanVersion"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "The subordinate AvailabilityPlans that form part of this AvailabilityPlan."; rdfs:domain ; ; rdfs:label "HasPart"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The parent AvailabilityPlan of which this AvailabilityPlan forms a part."; rdfs:domain ; ; rdfs:label "PartOf"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The System Operator responsible for establishing and maintaining the AvailabilityPlan."; rdfs:domain ; ; rdfs:label "SystemOperator"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "The date and time the start of the availability plan."; ; rdfs:domain ; rdfs:label "validFrom"@en; ; , "NC" . a rdf:Property; rdfs:comment "The date and time the end of the availability plan."; ; rdfs:domain ; rdfs:label "validTo"@en; ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "The affected Outage Coordinator that provides the response to the AvailabilityPlanVersion."; rdfs:domain ; ; rdfs:label "AffectedCoordinator"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The version of the AvailabilityPlan to which this response applies."; rdfs:domain ; ; rdfs:label "AvailablityPlanVersion"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Free-text explanation, justification or additional information provided with the response to the outage request version."; ; rdfs:domain ; rdfs:label "comment"@en; ; , "NC" . 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; ; , "NC" . a rdf:Property; rdfs:comment "Outcome of the response to the outage request version, indicating the decision or position of the responding party."; rdfs:domain ; rdfs:label "status"@en; ; rdfs:range ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "The AvailabilityPlan represented by this version."; rdfs:domain ; ; rdfs:label "AvailablityPlan"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "The responses provided for this version of the AvailabilityPlan."; rdfs:domain ; ; rdfs:label "AvailablityPlanResponse"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Kind of interpolation done between time point."; rdfs:domain ; rdfs:label "interpolationKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "Kind of base time series."; rdfs:domain ; rdfs:label "timeSeriesKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; "No"; rdfs:comment "Availability equipment describe the availabilty that affect this equipment."; rdfs:domain ; ; rdfs:label "AvailabilityEquipment"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Availability container describe the availabiltiy that affect this equipment container."; rdfs:domain ; ; rdfs:label "AvailabilityContainer"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Actual availability schedule that has this irregular interval schedule."; rdfs:domain ; ; rdfs:label "ActualAvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Value for the point in time."; rdfs:domain ; ; rdfs:label "EventTimePoint"@en; ; rdfs:range ; "NC", . a rdf:Property; "No"; rdfs:comment "Planned availability schedule that has this irregular interval schedule."; rdfs:domain ; ; rdfs:label "PlannedAvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "Time series the time point values belongs to."; rdfs:domain ; ; rdfs:label "EventSchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "The time the data is valid for."; ; rdfs:domain ; rdfs:label "atTime"@en; ; , "NC" . a rdf:Property; rdfs:comment "True, if the event is occurring (Active) at this time point. Otherwise false."; ; rdfs:domain ; rdfs:label "isActive"@en; ; , "NC" . a rdf:Property; "No"; rdfs:comment "Availability enabled describes the enabling or disabling of this grid state alteration."; rdfs:domain ; ; rdfs:label "AvailabilityEnabled"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Availability schedule that require the a collection of grid state alteration to provide a valid power flow solution. For instance, a set of switching plans."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@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; "No"; rdfs:comment "Availability exceptional limit that constrain this operational limit."; rdfs:domain ; ; rdfs:label "AvailabilityExceptionalLimit"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The availability schedule derived in part from this outage request."; rdfs:domain ; ; rdfs:label "AvailabilitySchedule"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The outage request that contributes to or influences the resulting availability schedule."; rdfs:domain ; ; rdfs:label "OutageRequest"@en; ; rdfs:range ; "NC" . 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; ; , "NC" . "No"; rdfs:comment "The AvailabilityPlans for which this Outage Coordinator is responsible for approval."; rdfs:domain ; ; rdfs:label "AvailablityPlan"@en; ; rdfs:range ; a rdf:Property; "NC" . a rdf:Property; "No"; rdfs:comment "The AvailabilityPlan responses provided by this Outage Coordinator."; rdfs:domain ; ; rdfs:label "AvailablityPlanResponse"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Responses issued by the coordinator as part of the outage coordination process."; rdfs:domain ; ; rdfs:label "OutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Responses issued by the coordinator as part of the outage coordination process."; rdfs:domain ; ; rdfs:label "OutageResponse"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The outage request upon which the dependent outage request depends."; rdfs:domain ; ; rdfs:label "DependeeOutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The outage request whose timing or execution is constrained by the dependee outage request."; rdfs:domain ; ; rdfs:label "DependentOutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Outage requests initiated by this planning agent."; rdfs:domain ; ; rdfs:label "OutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Responses issued by this planning agent to outage requests submitted by other actors."; rdfs:domain ; ; rdfs:label "OutageResponse"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "The outage dependency in which this outage request is the dependee."; rdfs:domain ; ; rdfs:label "DependencyAsDependee"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "The outage dependency in which this outage request is the dependent."; rdfs:domain ; ; rdfs:label "DependencyAsDependent"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "All availability relationships in which this outage request is used as an input to determine system availability."; rdfs:domain ; ; rdfs:label "OutageAvailability"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The coordinator responsible for approving the final version of the outage request."; rdfs:domain ; ; rdfs:label "OutageRequestApprover"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Outage request resource entries referencing the resource."; rdfs:domain ; ; rdfs:label "OutageRequestResource"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "All version instances associated with this OutageRequest."; rdfs:domain ; ; rdfs:label "OutageRequestVersion"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The agent responsible for creating and submitting the outage request."; rdfs:domain ; ; rdfs:label "RequestedBy"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "A cause description for a cause kind. In case of CauseKind equals other, description or a reference of the cause of the (un)availability schedule."; ; rdfs:domain ; rdfs:label "causeDescription"@en; ; , "NC" . a rdf:Property; rdfs:comment "Kind of cause for the availability schedule."; rdfs:domain ; rdfs:label "causeKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "True, when no work is planned for the weekend or public holidays and the equipment can be reinstated."; ; rdfs:domain ; rdfs:label "daytimeReinstatement"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service during daytime. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "daytimeReinstatementDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "Earliest possible start time/date of the work."; ; rdfs:domain ; rdfs:label "earlyStart"@en; ; , "NC" . a rdf:Property; rdfs:comment "True, when no work is planned for the weekend or public holidays and the equipment can be reinstated."; ; rdfs:domain ; rdfs:label "eveningReinstatement"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service after office hours. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "eveningReinstatementDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The expected planned work duration."; ; rdfs:domain ; rdfs:label "expectedWorkDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The latest time/date the work can start."; ; rdfs:domain ; rdfs:label "lateStart"@en; ; , "NC" . a rdf:Property; rdfs:comment "The maximum time required to take the out-of-service equipment back into service after office hours. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "maxReinstatementDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The maximum work duration taken into account risk mitigation with less resources available. If like that assessment is done on this duration to avoid re-planning on a later stage. "; ; rdfs:domain ; rdfs:label "maxWorkDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The minimum work duration that can be achieved when extra resources are allocated."; ; rdfs:domain ; rdfs:label "minWorkDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "0 means ignore priority. 1 means the highest priority, 2 is the second highest priority."; ; rdfs:domain ; rdfs:label "priority"@en; ; , "NC" . a rdf:Property; rdfs:comment "Requested start time/date."; ; rdfs:domain ; rdfs:label "requestedStart"@en; ; , "NC" . a rdf:Property; rdfs:comment "True, when no work is planned for the weekend or public holidays and the equipment can be reinstated."; ; rdfs:domain ; rdfs:label "weekendReinstatement"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time required to take the out-of-service equipment back into service in the weekend or during bank holidays. This includes the start-up time for generating units."; ; rdfs:domain ; rdfs:label "weekendReinstatementDuration"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time in a normal work day that equipment can be reinstated."; ; rdfs:domain ; rdfs:label "workDayEndTime"@en; ; , "NC" . a rdf:Property; rdfs:comment "The time in a normal work day that equipment would be taken out of service in case of reinstatement later in the working day."; ; rdfs:domain ; rdfs:label "workDayStartTime"@en; ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "The outage request that includes this specific affected resource."; rdfs:domain ; ; rdfs:label "OutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The specific power system resource that is affected by the outage request."; rdfs:domain ; ; rdfs:label "PowerSystemResource"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "The requested operational availability function of the associated PowerSystemResource. This value is used as input when determining the resulting AvailabilitySchedule."; rdfs:domain ; rdfs:label "kind"@en; ; rdfs:range ; , "NC" . 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; ; , "NC" . a rdf:Property; "Yes"; rdfs:comment "The OutageRequest for which this object represents a specific version used during coordination."; rdfs:domain ; ; rdfs:label "OutageRequest"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "All formal responses received for this version of the outage request."; rdfs:domain ; ; rdfs:label "OutageResponseRecord"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The agent that issued the response."; rdfs:domain ; ; rdfs:label "AffectedAgent"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The system operator acting as outage coordinator who issued the response."; rdfs:domain ; ; rdfs:label "AffectedCoordinator"@en; ; rdfs:range ; "NC" . a rdf:Property; "Yes"; rdfs:comment "The version of the outage request to which this response applies."; rdfs:domain ; ; rdfs:label "OutageRequestVersion"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:comment "Free-text explanation, justification or additional information provided with the response to the outage request version."; ; rdfs:domain ; rdfs:label "comment"@en; ; , "NC" . 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; ; , "NC" . a rdf:Property; rdfs:comment "Outcome of the response to the outage request version, indicating the decision or position of the responding party."; rdfs:domain ; rdfs:label "status"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment """The kind of temporal or operational constraint defined between the dependee and the dependent. Note: Certain dependency constraint kinds may require or prohibit the use of temporal constraint attributes, depending on the semantics of the specialization."""; rdfs:domain ; rdfs:label "constraintKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "The duration constraining the next finish or deactivation of the dependent relative to the latest applicable finish or deactivation of the dependee."; ; rdfs:domain ; rdfs:label "finishToFinishLag"@en; ; , "NC" . a rdf:Property; rdfs:comment """Specifies whether finishToFinishLag is an exact, minimum, or maximum temporal constraint. Note: This attribute shall be specified when finishToFinishLag is provided. Example: finishToFinishLag = 2D1H30M is interpreted together with finishToFinishLagKind: - exact: the dependent finishes exactly 2 days, 1 hour and 30 minutes after the latest applicable finish of the dependee. - minimum: the dependent may finish no earlier than 2 days, 1 hour and 30 minutes after the latest applicable finish of the dependee. - maximum: the dependent shall finish no later than 2 days, 1 hour and 30 minutes after the latest applicable finish of the dependee. In all cases, the dependee finish remains applicable only while the dependee remains in the state resulting from that finish. If the dependee subsequently changes state before the dependent finishes, the applicability of the previous finish is re-evaluated."""; rdfs:domain ; rdfs:label "finishToFinishLagKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "The duration constraining the next start or activation of the dependent relative to the latest applicable finish or deactivation of the dependee."; ; rdfs:domain ; rdfs:label "finishToStartLag"@en; ; , "NC" . a rdf:Property; rdfs:comment """Specifies whether finishToStartLag is an exact, minimum, or maximum temporal constraint. Note: This attribute shall be specified when finishToStartLag is provided. Example: finishToStartLag = 20M is interpreted together with finishToStartLagKind: - exact: the dependent starts exactly 20 minutes after the latest applicable finish of the dependee. - minimum: the dependent may start no earlier than 20 minutes after the latest applicable finish of the dependee. - maximum: the dependent shall start no later than 20 minutes after the latest applicable finish of the dependee. In all cases, the dependee finish remains applicable only while the dependee remains in the state resulting from that finish. If the dependee subsequently changes state before the dependent starts, the constraint is evaluated from the next applicable finish of the dependee."""; rdfs:domain ; rdfs:label "finishToStartLagKind"@en; ; rdfs:range ; , "NC" . 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; ; , "NC" . a rdf:Property; rdfs:comment "The duration constraining the period for which the dependee and dependent are simultaneously active or effective."; ; rdfs:domain ; rdfs:label "overlap"@en; ; , "NC" . a rdf:Property; rdfs:comment """Specifies whether overlap is an exact, minimum, or maximum duration of simultaneous activity or effectiveness. Note: This attribute shall be specified when overlap is provided. Example: overlap = 1H28M45S is interpreted together with overlapKind: - exact: the dependee and dependent are simultaneously active or effective for exactly 1 hour, 28 minutes, and 45 seconds. - minimum: the dependee and dependent shall be simultaneously active or effective for at least 1 hour, 28 minutes, and 45 seconds. - maximum: the dependee and dependent shall be simultaneously active or effective for no more than 1 hour, 28 minutes, and 45 seconds. Unlike the lag attributes, overlap constrains the duration of a simultaneous state rather than the temporal separation between two state transitions."""; rdfs:domain ; rdfs:label "overlapKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; rdfs:comment "The duration constraining the next start or activation of the dependent relative to the latest applicable start or activation of the dependee."; ; rdfs:domain ; rdfs:label "startToStartLag"@en; ; , "NC" . a rdf:Property; rdfs:comment """Specifies whether startToStartLag is an exact, minimum, or maximum temporal constraint. Note: This attribute shall be specified when startToStartLag is provided. Example: startToStartLag = 2H is interpreted together with startToStartLagKind: - exact: the dependent starts exactly 2 hours after the latest applicable start of the dependee. - minimum: the dependent may start no earlier than 2 hours after the latest applicable start of the dependee. - maximum: the dependent shall start no later than 2 hours after the latest applicable start of the dependee. In all cases, the dependee start remains applicable only while the dependee remains in the state resulting from that start. If the dependee subsequently changes state before the dependent starts, the constraint is evaluated from the next applicable start of the dependee."""; rdfs:domain ; rdfs:label "startToStartLagKind"@en; ; rdfs:range ; , "NC" . a rdf:Property; "No"; rdfs:comment "Outage request resource entries referencing the resource."; rdfs:domain ; ; rdfs:label "OutageRequestResource"@en; ; rdfs:range ; "NC" . a rdf:Property; "No"; rdfs:comment "Availability remedial action scheme describe the availabiltiy that affect this remedial action scheme."; rdfs:domain ; ; rdfs:label "AvailabilityRemedialActionScheme"@en; ; rdfs:range ; "NC" . a rdf:Property; rdfs:domain ; "none"; rdfs:label "multiplier"@en; ; rdfs:range ; . a rdf:Property; rdfs:domain ; "s"; rdfs:label "unit"@en; ; rdfs:range ; . a rdf:Property; rdfs:comment "Time, in seconds"; ; rdfs:domain ; rdfs:label "value"@en; ; . a rdf:Property; "No"; rdfs:comment "The AvailabilityPlans established or maintained by this System Operator."; rdfs:domain ; ; rdfs:label "AvailablityPlan"@en; ; rdfs:range ; "NC" . a ; rdfs:comment "Indicates that the record version has been reviewed and formally accepted by the responsible entity."; rdfs:label "approved"@en; "enum" . a ; rdfs:comment "Indicates that the record version has been withdrawn and is no longer valid for coordination. A cancelled record is retained only for audit and traceability."; rdfs:label "cancelled"@en; "enum" . a ; rdfs:comment "Indicates that the record version has completed its lifecycle and no further action is required. The record remains available for reference but is not active in any process."; rdfs:label "closed"@en; "enum" . a ; rdfs:comment "Indicates that the record version is actively being processed, updated, or evaluated as part of any coordination workflow."; rdfs:label "inProgress"@en; "enum" . a ; rdfs:comment "Indicates that the record version has been created but not yet submitted for review or coordination. It represents an initial draft state."; rdfs:label "new"@en; "enum" . a ; rdfs:comment "Indicates that the record version has been submitted and is awaiting responses or decisions from assigned agents."; rdfs:label "pending"@en; "enum" . a ; rdfs:comment "Indicates that the record version represents a final outcome or result of any coordination process, typically summarising the consolidated decision or approved plan."; rdfs:label "result"@en; "enum" . a ; rdfs:comment "The referenced value is to be met exactly."; rdfs:label "exact"@en; "enum" . a ; rdfs:comment "The referenced value establishes a upper bound."; rdfs:label "maximum"@en; "enum" . a ; rdfs:comment "The referenced value establishes a lower bound."; rdfs:label "minimum"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent agrees and accept the request version as submitted."; rdfs:label "accepted"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent can accept the request version only if specific conditions, modifications, or mitigations are met."; rdfs:label "acceptedWithConditions"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent has received and reviewed the request version, but has not yet provided an approval or objection."; rdfs:label "acknowledged"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent proposes alternative timing, duration, scope, or other adjustments to the request version."; rdfs:label "alternativeProposal"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent did not provide a response within the required timeframe, and the coordination process proceeded using a timeout rule."; rdfs:label "noResponseTimeout"@en; "enum" . a ; rdfs:comment "Indicates that the responding agent does not accept the request version due to operational, technical, or regulatory constraints."; rdfs:label "refused"@en; "enum" . a ; rdfs:comment "The value between two time points is set to previous value."; rdfs:label "previous"@en; "enum" . a ; rdfs:comment "No multiplier or equivalently multiply by 1."; rdfs:label "none"@en; "enum" . a ; rdfs:comment "Time in seconds."; rdfs:label "s"@en; "enum" .