@prefix cim: . @prefix rdf: . @prefix rdfs: . @prefix sh: . @prefix xsd: . cim:ACDCTerminal a sh:NodeShape ; rdfs:comment "An electrical connection point (AC or DC) to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes." ; sh:closed true ; sh:ignoredProperties ( rdf:type cim:ConductingEquipment ) ; sh:property [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:IdentifiedObject.mRID ] ; sh:targetClass cim:ACDCTerminal . cim:Conductor a sh:NodeShape ; rdfs:comment "Combination of conducting material with consistent electrical characteristics, building a single electrical system, used to carry current between points in the power system. " ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ] ; sh:targetClass cim:Conductor . cim:ContingencyElement a sh:NodeShape ; 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. " ; sh:closed false ; sh:ignoredProperties ( rdf:type cim:Equipment ) ; sh:property [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description "A contingency element belongs to one contingency." ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:ContingencyElement.Contingency ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ] ; sh:targetClass cim:ContingencyElement . cim:ContingencyEquipment a sh:NodeShape ; rdfs:comment "Equipment whose in service status is to change, such as a power transformer or AC line segment." ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:class cim:ACLineSegment ; sh:description "The single piece of equipment to which to apply the contingency." ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:IRI ; sh:order 0 ; sh:path cim:ContingencyEquipment.Equipment ], [ sh:datatype xsd:string ; sh:description "A contingency element belongs to one contingency." ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:ContingencyElement.Contingency ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 4 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.mRID ] ; sh:targetClass cim:ContingencyEquipment . cim:EnergyConnection a sh:NodeShape ; rdfs:comment "A connection of energy generation or consumption on the power system model." ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ] ; sh:targetClass cim:EnergyConnection . cim:IdentifiedObject a sh:NodeShape ; rdfs:comment "This is a root class to provide common identification for all classes needing identification and naming attributes." ; sh:closed true ; sh:ignoredProperties ( cim:Equipment cim:ContingencyElement.Contingency rdf:type cim:Terminal cim:ConductingEquipment cim:Equipment.aggregate ) ; sh:property [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.name ] ; sh:targetClass cim:IdentifiedObject . cim:PowerSystemResource a sh:NodeShape ; 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." ; sh:closed true ; sh:ignoredProperties ( rdf:type cim:Equipment.aggregate ) ; sh:property [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.name ] ; sh:targetClass cim:PowerSystemResource . cim:TopologicalNode a sh:NodeShape ; rdfs:comment """For a detailed substation model a topological node is a set of connectivity nodes that, in the current network state, are connected together through any type of closed switches, including jumpers. Topological nodes change as the current network state changes (i.e., switches, breakers, etc. change state). For a planning model, switch statuses are not used to form topological nodes. Instead they are manually created or deleted in a model builder tool. Topological nodes maintained this way are also called _busses_.""" ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description "The terminals associated with the topological node. This can be used as an alternative to the connectivity node path to terminal, thus making it unnecessary to model connectivity nodes in some cases. Note that if connectivity nodes are in the model, this association would probably not be used as an input specification." ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:TopologicalNode.Terminal ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ] ; sh:targetClass cim:TopologicalNode . cim:EnergyConsumer a sh:NodeShape ; rdfs:comment """Generic user of energy - a point of consumption on the power system model.\r EnergyConsumer.pfixed, .qfixed, .pfixedPct and .qfixedPct have meaning only if there is no LoadResponseCharacteristic associated with EnergyConsumer or if LoadResponseCharacteristic.exponentModel is set to False.""" ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ] ; sh:targetClass cim:EnergyConsumer . cim:Terminal a sh:NodeShape ; rdfs:comment "An AC electrical connection point to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes." ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:description "The conducting equipment of the terminal. Conducting equipment have terminals that may be connected to other conducting equipment terminals via connectivity nodes or topological nodes." ; sh:maxCount 1 ; sh:minCount 1 ; sh:or ( [ sh:class cim:EnergyConsumer ] [ sh:class cim:ACLineSegment ] ) ; sh:order 0 ; sh:path cim:Terminal.ConductingEquipment ] ; sh:targetClass cim:Terminal . cim:ACLineSegment a sh:NodeShape ; rdfs:comment """A wire or combination of wires, with consistent electrical characteristics, building a single electrical system, used to carry alternating current between points in the power system.\r For symmetrical, transposed three phase lines, it is sufficient to use attributes of the line segment, which describe impedances and admittances for the entire length of the segment. Additionally impedances can be computed by using length and associated per length impedances.\r The BaseVoltage at the two ends of ACLineSegments in a Line shall have the same BaseVoltage.nominalVoltage. However, boundary lines may have slightly different BaseVoltage.nominalVoltages and variation is allowed. Larger voltage difference in general requires use of an equivalent branch.""" ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ], [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ] ; sh:targetClass cim:ACLineSegment . cim:ConductingEquipment a sh:NodeShape ; rdfs:comment "The parts of the AC power system that are designed to carry current or that are conductively connected through terminals." ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ] ; sh:targetClass cim:ConductingEquipment . cim:Equipment a sh:NodeShape ; rdfs:comment "The parts of a power system that are physical devices, electronic or mechanical." ; sh:closed true ; sh:ignoredProperties ( rdf:type ) ; sh:property [ sh:datatype xsd:string ; sh:description "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." ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 2 ; sh:path cim:IdentifiedObject.description ], [ sh:datatype xsd:string ; sh:description """The name is any free human readable and possibly non unique text naming the object.\r """ ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 3 ; sh:path cim:IdentifiedObject.name ], [ sh:datatype xsd:string ; sh:description """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.\r 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.""" ; sh:maxCount 1 ; sh:minCount 1 ; sh:nodeKind sh:Literal ; sh:order 1 ; sh:path cim:IdentifiedObject.mRID ], [ sh:datatype xsd:boolean ; sh:description """The aggregate flag provides an alternative way of representing an aggregated (equivalent) element. It is applicable in cases when the dedicated classes for equivalent equipment do not have all of the attributes necessary to represent the required level of detail. In case the flag is set to “true” the single instance of equipment represents multiple pieces of equipment that have been modelled together as an aggregate equivalent obtained by a network reduction procedure. Examples would be power transformers or synchronous machines operating in parallel modelled as a single aggregate power transformer or aggregate synchronous machine. \r The attribute is not used for EquivalentBranch, EquivalentShunt and EquivalentInjection.""" ; sh:maxCount 1 ; sh:nodeKind sh:Literal ; sh:order 0 ; sh:path cim:Equipment.aggregate ] ; sh:targetClass cim:Equipment .