Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Included schema CommonElectrical.xsd
Namespace http://www.iepmodel.net
Properties
attribute form default: unqualified
element form default: unqualified
version: 1.0
Element WirewaySegmentType / Name
Namespace No namespace
Annotations
A name given in context to the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element name="Name" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>A name given in context to the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element WirewaySegmentType / LocationDescription
Namespace No namespace
Annotations
Description of where the segment is, or through which locations it traverses.  Include descriptions such as attic, interior, exterior, roof, or trench.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="LocationDescription" type="xs:string">
  <xs:annotation>
    <xs:documentation>Description of where the segment is, or through which locations it traverses. Include descriptions such as attic, interior, exterior, roof, or trench.</xs:documentation>
  </xs:annotation>
</xs:element>
Element WirewaySegmentType / HighTempExposure
Namespace No namespace
Annotations
Is the conduit exposed to high temperatures?  For example, sitting on a roof in direct sun.  If so, any conductors contained within the segment may have to have their rated current carrying capacity derated.
Diagram
Diagram
Type xs:boolean
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="HighTempExposure" type="xs:boolean" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Is the conduit exposed to high temperatures? For example, sitting on a roof in direct sun. If so, any conductors contained within the segment may have to have their rated current carrying capacity derated.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalDistributionHierarchyType / ElectricalDistributionPanel
Namespace No namespace
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType CommonElectrical_xsd.tmp#ElectricalPanelType_EnergizingSourceCircuitConnection CommonElectrical_xsd.tmp#ElectricalPanelType_MainBreaker CommonElectrical_xsd.tmp#ElectricalPanelType_Existence CommonElectrical_xsd.tmp#ElectricalPanelType_IncludedMeter CommonElectrical_xsd.tmp#ElectricalPanelType_SumOfExistingFeederBreakerAmps CommonElectrical_xsd.tmp#ElectricalPanelType_UnusedBreakerSlotQuantity CommonElectrical_xsd.tmp#ElectricalPanelType_SupplySideLugHolesAvailable CommonElectrical_xsd.tmp#ElectricalPanelType_AcGroundingElectrodeConductor CommonElectrical_xsd.tmp#ElectricalPanelType_SubPanel CommonElectrical_xsd.tmp#ElectricalPanelType
Type ElectricalPanelType
Type hierarchy
Properties
content: complex
Model Name{0,1} , SerialNumber{0,1} , DateManufactured{0,1} , Location{0,1} , Condition{0,1} , LastServiced{0,1} , UsefulLife{0,1} , EnergizingSourceCircuitConnection{0,1} , MainBreaker{0,1} , Existence{0,1} , IncludedMeter{0,1} , SumOfExistingFeederBreakerAmps{0,1} , UnusedBreakerSlotQuantity{0,1} , SupplySideLugHolesAvailable{0,1} , AcGroundingElectrodeConductor{0,1} , SubPanel{0,1}
Children AcGroundingElectrodeConductor, Condition, DateManufactured, EnergizingSourceCircuitConnection, Existence, IncludedMeter, LastServiced, Location, MainBreaker, Name, SerialNumber, SubPanel, SumOfExistingFeederBreakerAmps, SupplySideLugHolesAvailable, UnusedBreakerSlotQuantity, UsefulLife
Instance
<ElectricalDistributionPanel EquipmentDefinitionIdRef="" id="">
  <Name>{0,1}</Name>
  <SerialNumber>{0,1}</SerialNumber>
  <DateManufactured>{0,1}</DateManufactured>
  <Location>{0,1}</Location>
  <Condition>{0,1}</Condition>
  <LastServiced>{0,1}</LastServiced>
  <UsefulLife>{0,1}</UsefulLife>
  <EnergizingSourceCircuitConnection EquipmentWhereConnectedIdRef="">{0,1}</EnergizingSourceCircuitConnection>
  <MainBreaker>{0,1}</MainBreaker>
  <Existence>{0,1}</Existence>
  <IncludedMeter EquipmentDefinitionIdRef="" id="">{0,1}</IncludedMeter>
  <SumOfExistingFeederBreakerAmps>{0,1}</SumOfExistingFeederBreakerAmps>
  <UnusedBreakerSlotQuantity>{0,1}</UnusedBreakerSlotQuantity>
  <SupplySideLugHolesAvailable>{0,1}</SupplySideLugHolesAvailable>
  <AcGroundingElectrodeConductor>{0,1}</AcGroundingElectrodeConductor>
  <SubPanel EquipmentDefinitionIdRef="" id="">{0,1}</SubPanel>
</ElectricalDistributionPanel>
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF required
ID Ref of the associated equipment definition for this equipment instance.  For example, in case of a PVModule, this would be the ID of the PvModuleDefinition element that describes this particular PV module instance.
id xs:ID required
Source
<xs:element name="ElectricalDistributionPanel" type="ElectricalPanelType"/>
Element ElectricalPanelType / EnergizingSourceCircuitConnection
Namespace No namespace
Annotations
Description of the conductor energizing the panel.  Should include description of OCPD / disco at source end.
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentWhereConnectedIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_Name CommonElectrical_xsd.tmp#CircuitConnectionType_CurrentType CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConductors CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesDisconnect CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesStandAloneMeter CommonElectrical_xsd.tmp#CircuitConnectionType_Ocpd CommonElectrical_xsd.tmp#CircuitConnectionType_SideOfPanelOcpdWhereConnected CommonElectrical_xsd.tmp#CircuitConnectionType_ConductorConnectionMechanism CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentGroundingConductor CommonElectrical_xsd.tmp#CircuitConnectionType_WirewaySegmentIdRef CommonElectrical_xsd.tmp#CircuitConnectionType
Type CircuitConnectionType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model Name{0,1} , CurrentType{0,1} , CircuitConductors , IncludesDisconnect{0,1} , IncludesStandAloneMeter{0,1} , Ocpd{0,1} , SideOfPanelOcpdWhereConnected{0,1} , ConductorConnectionMechanism{0,1} , EquipmentGroundingConductor{0,1} , WirewaySegmentIdRef*
Children CircuitConductors, ConductorConnectionMechanism, CurrentType, EquipmentGroundingConductor, IncludesDisconnect, IncludesStandAloneMeter, Name, Ocpd, SideOfPanelOcpdWhereConnected, WirewaySegmentIdRef
Instance
<EnergizingSourceCircuitConnection EquipmentWhereConnectedIdRef="">
  <Name>{0,1}</Name>
  <CurrentType>{0,1}</CurrentType>
  <CircuitConductors>{1,1}</CircuitConductors>
  <IncludesDisconnect ConductorSegmentIdRef="" WirewayBoxIdRef="">{0,1}</IncludesDisconnect>
  <IncludesStandAloneMeter ConductorSegmentIdRef="">{0,1}</IncludesStandAloneMeter>
  <Ocpd EquipmentWhereLocatedIdRef="">{0,1}</Ocpd>
  <SideOfPanelOcpdWhereConnected>{0,1}</SideOfPanelOcpdWhereConnected>
  <ConductorConnectionMechanism>{0,1}</ConductorConnectionMechanism>
  <EquipmentGroundingConductor>{0,1}</EquipmentGroundingConductor>
  <WirewaySegmentIdRef>{0,unbounded}</WirewaySegmentIdRef>
</EnergizingSourceCircuitConnection>
Attributes
QName Type Fixed Default Use Annotation
EquipmentWhereConnectedIdRef xs:IDREF optional
In cases where the CircuitConnection element is used within an EquipmentInstance that does not have a parent element to which the CircuitConnection is assumed to connect, a reference ID can be used to associate this CircuitConnection to another EquipmentInstance elsewhere in a document instance.  For example, a PvSystem may have an AcPointOfConnection that uses a new ElectricalPanel as an AC combiner for more than one Inverter.  The new electrical panel can be described by an  ElectricalPanel element in the PvDesign (which in turn refers to an ElectricalPanelDefinition element).

in the AcPointOfConnection's EquipmentWhereConnected element.  That ElectricPanel's EnergizingCircuitConnection element may reference another ElectricPanel in an instance of the Project's ExistingElectricalHierarchy element.
Source
<xs:element minOccurs="0" name="EnergizingSourceCircuitConnection" type="CircuitConnectionType" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Description of the conductor energizing the panel. Should include description of OCPD / disco at source end.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / Name
Namespace No namespace
Annotations
An optional free text identifier.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="Name" type="xs:string">
  <xs:annotation>
    <xs:documentation>An optional free text identifier.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / CurrentType
Namespace No namespace
Annotations
AC or DC
Diagram
Diagram CommonElectrical_xsd.tmp#CurrentEnumType
Type CurrentEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration AC
enumeration DC
Source
<xs:element name="CurrentType" minOccurs="0" type="CurrentEnumType">
  <xs:annotation>
    <xs:documentation>AC or DC</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / CircuitConductors
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionConductorType_ConductorSize CommonElectrical_xsd.tmp#CircuitConnectionConductorType_ConductorQuantity CommonElectrical_xsd.tmp#CircuitConnectionConductorType_PrimaryConductorSegment CommonElectrical_xsd.tmp#CircuitConnectionConductorType_SecondaryConductorSegment CommonElectrical_xsd.tmp#CircuitConnectionConductorType
Type CircuitConnectionConductorType
Properties
content: complex
Model ConductorSize , ConductorQuantity , PrimaryConductorSegment{0,1} , SecondaryConductorSegment*
Children ConductorQuantity, ConductorSize, PrimaryConductorSegment, SecondaryConductorSegment
Instance
<CircuitConductors>
  <ConductorSize>{1,1}</ConductorSize>
  <ConductorQuantity>{1,1}</ConductorQuantity>
  <PrimaryConductorSegment id="">{0,1}</PrimaryConductorSegment>
  <SecondaryConductorSegment ConnectsToConductorSegmentId="" id="" WirewaySegmentWhereConnectedId="">{0,unbounded}</SecondaryConductorSegment>
</CircuitConductors>
Source
<xs:element name="CircuitConductors" type="CircuitConnectionConductorType"/>
Element CircuitConnectionConductorType / ConductorSize
Namespace No namespace
Annotations
Wire diameter, given in American Wire Gauge (AWG), or kcmil.  The entire circuit connection conductor is assumed to be the same size conductor, even if it is physically made up of multiple conductor segments that are different kinds of wire.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSizeEnumType
Type ConductorSizeEnumType
Properties
content: simple
Facets
enumeration 12
enumeration 10
enumeration 8
enumeration 6
enumeration 4
enumeration 3
enumeration 2
enumeration 1/0
enumeration 2/0
enumeration 3/0
enumeration 4/0
enumeration 250
enumeration 350
enumeration 400
enumeration 500
Source
<xs:element name="ConductorSize" type="ConductorSizeEnumType">
  <xs:annotation>
    <xs:documentation>Wire diameter, given in American Wire Gauge (AWG), or kcmil. The entire circuit connection conductor is assumed to be the same size conductor, even if it is physically made up of multiple conductor segments that are different kinds of wire.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionConductorType / ConductorQuantity
Namespace No namespace
Annotations
Number of conductors used to connect the circuit. Residential 120V uses 2 conductors, whereas 240V typically uses three conductors, and commercial three phase typically is 4 conductors.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 1
Source
<xs:element minOccurs="1" name="ConductorQuantity" type="xs:integer">
  <xs:annotation>
    <xs:documentation>Number of conductors used to connect the circuit. Residential 120V uses 2 conductors, whereas 240V typically uses three conductors, and commercial three phase typically is 4 conductors.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionConductorType / PrimaryConductorSegment
Namespace No namespace
Annotations
This is the segment of the CircuitConductor that is connected directly to the electrical component that this CircuitConnection belongs to.  For example, let's assume that this ConductorSegment is part of a CircuitConnection for a PvString. The PvString typically starts out as USE-2 wire from the PV Modules and may transition to THWN-2 wire once inside a J-box (modeled as a Wireway box in this schema).  The USE-2 segment of the conductor is the Primary segment, while the THWN-2 wire is a secondary segment.  All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSegmentType_id CommonElectrical_xsd.tmp#ConductorSegmentType_Material CommonElectrical_xsd.tmp#ConductorSegmentType_Jacket CommonElectrical_xsd.tmp#ConductorSegmentType_JacketColor CommonElectrical_xsd.tmp#ConductorSegmentType_Length CommonElectrical_xsd.tmp#ConductorSegmentType
Type ConductorSegmentType
Properties
content: complex
minOccurs: 0
Model Material{0,1} , Jacket , JacketColor{0,1} , Length{0,1}
Children Jacket, JacketColor, Length, Material
Instance
<PrimaryConductorSegment id="">
  <Material>{0,1}</Material>
  <Jacket>{1,1}</Jacket>
  <JacketColor>{0,1}</JacketColor>
  <Length>{0,1}</Length>
</PrimaryConductorSegment>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID required
Source
<xs:element minOccurs="0" name="PrimaryConductorSegment" type="ConductorSegmentType">
  <xs:annotation>
    <xs:documentation>This is the segment of the CircuitConductor that is connected directly to the electrical component that this CircuitConnection belongs to. For example, let's assume that this ConductorSegment is part of a CircuitConnection for a PvString. The PvString typically starts out as USE-2 wire from the PV Modules and may transition to THWN-2 wire once inside a J-box (modeled as a Wireway box in this schema). The USE-2 segment of the conductor is the Primary segment, while the THWN-2 wire is a secondary segment. All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ConductorSegmentType / Material
Namespace No namespace
Annotations
Types of conductor material, such as "stranded Cu," "solid Cu," "stranded Al," etc.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorMaterialEnumType
Type ConductorMaterialEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration Stranded Cu
enumeration Solid Cu
enumeration Stranded Al
Source
<xs:element minOccurs="0" name="Material" type="ConductorMaterialEnumType">
  <xs:annotation>
    <xs:documentation>Types of conductor material, such as "stranded Cu," "solid Cu," "stranded Al," etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ConductorSegmentType / Jacket
Namespace No namespace
Annotations
Type of jacketing on the conductor.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorJacketEnumType
Type ConductorJacketEnumType
Properties
content: simple
minOccurs: 1
Facets
enumeration bare
enumeration USE
enumeration USE-2
enumeration THWN
enumeration THWN-2
enumeration THHN
enumeration THHW
enumeration XHHW-2
enumeration RHW-2
enumeration PV Wire
Source
<xs:element minOccurs="1" name="Jacket" type="ConductorJacketEnumType">
  <xs:annotation>
    <xs:documentation>Type of jacketing on the conductor.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ConductorSegmentType / JacketColor
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="JacketColor" type="xs:string"/>
Element ConductorSegmentType / Length
Namespace No namespace
Annotations
Length of this conductor connection, in feet.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Length" type="xs:double" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Length of this conductor connection, in feet.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionConductorType / SecondaryConductorSegment
Namespace No namespace
Annotations
A portion of a CircuitConnectionConductor that is of a different type of wire than the Primary.  All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSegmentType_id CommonElectrical_xsd.tmp#ConductorSegmentType_Material CommonElectrical_xsd.tmp#ConductorSegmentType_Jacket CommonElectrical_xsd.tmp#ConductorSegmentType_JacketColor CommonElectrical_xsd.tmp#ConductorSegmentType_Length CommonElectrical_xsd.tmp#ConductorSegmentType CommonElectrical_xsd.tmp#CircuitConnectionConductorType_CircuitConnectionConductorType_SecondaryConductorSegment_ConnectsToConductorSegmentId CommonElectrical_xsd.tmp#CircuitConnectionConductorType_CircuitConnectionConductorType_SecondaryConductorSegment_WirewaySegmentWhereConnectedId
Type extension of ConductorSegmentType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Material{0,1} , Jacket , JacketColor{0,1} , Length{0,1}
Children Jacket, JacketColor, Length, Material
Instance
<SecondaryConductorSegment ConnectsToConductorSegmentId="" id="" WirewaySegmentWhereConnectedId="">
  <Material>{0,1}</Material>
  <Jacket>{1,1}</Jacket>
  <JacketColor>{0,1}</JacketColor>
  <Length>{0,1}</Length>
</SecondaryConductorSegment>
Attributes
QName Type Fixed Default Use Annotation
ConnectsToConductorSegmentId xs:IDREF required
WirewaySegmentWhereConnectedId xs:IDREF required
id xs:ID required
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="SecondaryConductorSegment">
  <xs:annotation>
    <xs:documentation>A portion of a CircuitConnectionConductor that is of a different type of wire than the Primary. All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="ConductorSegmentType">
        <xs:attribute name="ConnectsToConductorSegmentId" type="xs:IDREF" use="required"/>
        <xs:attribute name="WirewaySegmentWhereConnectedId" type="xs:IDREF" use="required"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Element CircuitConnectionType / IncludesDisconnect
Namespace No namespace
Annotations
If the CircuitConnection has a disconnect switch in it, this calls it out.
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_IncludesDisconnect_WirewayBoxIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_IncludesDisconnect_ConductorSegmentIdRef
Properties
content: complex
minOccurs: 0
Attributes
QName Type Fixed Default Use Annotation
ConductorSegmentIdRef xs:IDREF required
ConductorSegment that contains the disconnect switch.
WirewayBoxIdRef xs:IDREF required
Reference to an instance of the DisconnectSwitch modeled generally as a WirewayBox. A disconnect switch can switch more than one CircuitConnection, so it is defined external to the CircuitConnection.
Source
<xs:element minOccurs="0" name="IncludesDisconnect">
  <xs:annotation>
    <xs:documentation>If the CircuitConnection has a disconnect switch in it, this calls it out.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="WirewayBoxIdRef" type="xs:IDREF" use="required">
      <xs:annotation>
        <xs:documentation>Reference to an instance of the DisconnectSwitch modeled generally as a WirewayBox. A disconnect switch can switch more than one CircuitConnection, so it is defined external to the CircuitConnection.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="ConductorSegmentIdRef" type="xs:IDREF" use="required">
      <xs:annotation>
        <xs:documentation>ConductorSegment that contains the disconnect switch.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element CircuitConnectionType / IncludesStandAloneMeter
Namespace No namespace
Annotations
If the CircuitConnection is metered (for example the utility's revenue meter), this element describes the meter socket and meter.  The meter and socket are individual entities. The MeterSocket is modeled as a simple WirewayBox.
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_IncludesStandAloneMeter_ConductorSegmentIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_IncludesStandAloneMeter_MeterSocket CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_IncludesStandAloneMeter_Meter
Properties
content: complex
minOccurs: 0
Model MeterSocket , Meter
Children Meter, MeterSocket
Instance
<IncludesStandAloneMeter ConductorSegmentIdRef="">
  <MeterSocket EquipmentDefinitionIdRef="" id="">{1,1}</MeterSocket>
  <Meter EquipmentDefinitionIdRef="" id="">{1,1}</Meter>
</IncludesStandAloneMeter>
Attributes
QName Type Fixed Default Use Annotation
ConductorSegmentIdRef xs:IDREF optional
Source
<xs:element minOccurs="0" name="IncludesStandAloneMeter">
  <xs:annotation>
    <xs:documentation>If the CircuitConnection is metered (for example the utility's revenue meter), this element describes the meter socket and meter. The meter and socket are individual entities. The MeterSocket is modeled as a simple WirewayBox.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="MeterSocket" type="WirewayBoxType"/>
      <xs:element name="Meter" type="EquipmentInstanceType"/>
    </xs:sequence>
    <xs:attribute name="ConductorSegmentIdRef" type="xs:IDREF"/>
  </xs:complexType>
</xs:element>
Element CircuitConnectionType / IncludesStandAloneMeter / MeterSocket
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#WirewaySegmentType_id CommonElectrical_xsd.tmp#WirewaySegmentType_EquipmentDefinitionIdRef CommonElectrical_xsd.tmp#WirewaySegmentType_Name CommonElectrical_xsd.tmp#WirewaySegmentType_LocationDescription CommonElectrical_xsd.tmp#WirewaySegmentType_HighTempExposure CommonElectrical_xsd.tmp#WirewaySegmentType CommonElectrical_xsd.tmp#WirewayBoxType_SegmentConnection CommonElectrical_xsd.tmp#WirewayBoxType
Type WirewayBoxType
Type hierarchy
Properties
content: complex
Model Name{0,1} , LocationDescription{0,1} , HighTempExposure{0,1} , SegmentConnection+
Children HighTempExposure, LocationDescription, Name, SegmentConnection
Instance
<MeterSocket EquipmentDefinitionIdRef="" id="">
  <Name>{0,1}</Name>
  <LocationDescription>{0,1}</LocationDescription>
  <HighTempExposure>{0,1}</HighTempExposure>
  <SegmentConnection>{1,unbounded}</SegmentConnection>
</MeterSocket>
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF optional
If the WirewaySegment is a junction box or disconnect switch, this refers to its EquipmentDefinition. A WirewayBox may be a pass through where multiple ConduitSegments are combined into a single ConduitSegment for example.  A disconnect switch box may also be modeled as a WirewayBox, provided that the circuit(s) involved are simply disoconnected and not combined in any way. DO NOT use WirewayBox to represent a combiner, or distribution panel.
id xs:ID required
Source
<xs:element name="MeterSocket" type="WirewayBoxType"/>
Element WirewayBoxType / SegmentConnection
Namespace No namespace
Annotations
The ID Ref for another WirewaySegment.  Boxes can have many WirewaySegment connections (e.g. multiple conduit segments can terminate at a box). Conduit is a pipe with 2 ends, so it has a maximum of two WirewaySegments to which it connects.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 1
maxOccurs: unbounded
Source
<xs:element maxOccurs="unbounded" name="SegmentConnection" type="xs:IDREF" minOccurs="1">
  <xs:annotation>
    <xs:documentation>The ID Ref for another WirewaySegment. Boxes can have many WirewaySegment connections (e.g. multiple conduit segments can terminate at a box). Conduit is a pipe with 2 ends, so it has a maximum of two WirewaySegments to which it connects.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / IncludesStandAloneMeter / Meter
Namespace No namespace
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType
Type EquipmentInstanceType
Properties
content: complex
Model Name{0,1} , SerialNumber{0,1} , DateManufactured{0,1} , Location{0,1} , Condition{0,1} , LastServiced{0,1} , UsefulLife{0,1}
Children Condition, DateManufactured, LastServiced, Location, Name, SerialNumber, UsefulLife
Instance
<Meter EquipmentDefinitionIdRef="" id="">
  <Name>{0,1}</Name>
  <SerialNumber>{0,1}</SerialNumber>
  <DateManufactured>{0,1}</DateManufactured>
  <Location>{0,1}</Location>
  <Condition>{0,1}</Condition>
  <LastServiced>{0,1}</LastServiced>
  <UsefulLife>{0,1}</UsefulLife>
</Meter>
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF required
ID Ref of the associated equipment definition for this equipment instance.  For example, in case of a PVModule, this would be the ID of the PvModuleDefinition element that describes this particular PV module instance.
id xs:ID required
Source
<xs:element name="Meter" type="EquipmentInstanceType"/>
Element CircuitConnectionType / Ocpd
Namespace No namespace
Annotations
Over current protection device (OCPD). A device that protects the conductor from too much current by breaking the circuit. Fuses and circuit breakers are OCPDs.  In this schema, an OCPD is not a piece of equipment, but rather a component within a piece of equipment.  It is not necessary to include a mfr and model in most cases, but knowing the type and rating is required.
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_Ocpd_EquipmentWhereLocatedIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_Ocpd_Fuse CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConnectionType_Ocpd_CircuitBreaker
Properties
content: complex
minOccurs: 0
Model Fuse | CircuitBreaker
Children CircuitBreaker, Fuse
Instance
<Ocpd EquipmentWhereLocatedIdRef="">
  <Fuse>{1,1}</Fuse>
  <CircuitBreaker>{1,1}</CircuitBreaker>
</Ocpd>
Attributes
QName Type Fixed Default Use Annotation
EquipmentWhereLocatedIdRef optional
The ID referring to the equipment in which the OCPD is installed.  In most cases, it is the parent Equipment of the CircuitConnection's immediate parent element.  For example, if the CircuitConnection is within a StringInverter element, then the circuit breaker within the ElectricalPanel to which the Inverter connects will most like be the referenced OCPD.
Source
<xs:element name="Ocpd" minOccurs="0" form="unqualified">
  <xs:annotation>
    <xs:documentation>Over current protection device (OCPD). A device that protects the conductor from too much current by breaking the circuit. Fuses and circuit breakers are OCPDs. In this schema, an OCPD is not a piece of equipment, but rather a component within a piece of equipment. It is not necessary to include a mfr and model in most cases, but knowing the type and rating is required.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="Fuse" type="FuseType"/>
      <xs:element name="CircuitBreaker" type="CircuitBreakerType"/>
    </xs:choice>
    <xs:attribute name="EquipmentWhereLocatedIdRef">
      <xs:annotation>
        <xs:documentation>The ID referring to the equipment in which the OCPD is installed. In most cases, it is the parent Equipment of the CircuitConnection's immediate parent element. For example, if the CircuitConnection is within a StringInverter element, then the circuit breaker within the ElectricalPanel to which the Inverter connects will most like be the referenced OCPD.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element CircuitConnectionType / Ocpd / Fuse
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_CurrentRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_AcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_DcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_Manufacturer CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_ModelNumber CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType CommonElectrical_xsd.tmp#FuseType_FuseClass CommonElectrical_xsd.tmp#FuseType
Type FuseType
Type hierarchy
Properties
content: complex
Model CurrentRating , AcVoltageRating{0,1} , DcVoltageRating{0,1} , Manufacturer{0,1} , ModelNumber{0,1} , FuseClass{0,1}
Children AcVoltageRating, CurrentRating, DcVoltageRating, FuseClass, Manufacturer, ModelNumber
Instance
<Fuse>
  <CurrentRating>{1,1}</CurrentRating>
  <AcVoltageRating>{0,1}</AcVoltageRating>
  <DcVoltageRating>{0,1}</DcVoltageRating>
  <Manufacturer>{0,1}</Manufacturer>
  <ModelNumber>{0,1}</ModelNumber>
  <FuseClass>{0,1}</FuseClass>
</Fuse>
Source
<xs:element name="Fuse" type="FuseType"/>
Element OverCurrentProtectionDeviceType / CurrentRating
Namespace No namespace
Annotations
The maximum rating in amps at which the OCPD is rated for operation.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 1
maxOccurs: 1
Source
<xs:element name="CurrentRating" type="xs:integer" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The maximum rating in amps at which the OCPD is rated for operation.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OverCurrentProtectionDeviceType / AcVoltageRating
Namespace No namespace
Annotations
Maximum AC voltage at which the OCPD is rated for use.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
Source
<xs:element name="AcVoltageRating" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximum AC voltage at which the OCPD is rated for use.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OverCurrentProtectionDeviceType / DcVoltageRating
Namespace No namespace
Annotations
Maximum DC voltage (if any) at which the OCPD is rated for use.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="DcVoltageRating" type="xs:integer">
  <xs:annotation>
    <xs:documentation>Maximum DC voltage (if any) at which the OCPD is rated for use.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OverCurrentProtectionDeviceType / Manufacturer
Namespace No namespace
Annotations
Optional name of the manufacturer.  May be helpful to know if replacing the current with something compatible, example.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="Manufacturer" type="xs:string">
  <xs:annotation>
    <xs:documentation>Optional name of the manufacturer. May be helpful to know if replacing the current with something compatible, example.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OverCurrentProtectionDeviceType / ModelNumber
Namespace No namespace
Annotations
Optional manufacturer model number.  May be helpful to know if replacing the current with something compatible, example.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="ModelNumber" type="xs:string">
  <xs:annotation>
    <xs:documentation>Optional manufacturer model number. May be helpful to know if replacing the current with something compatible, example.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FuseType / FuseClass
Namespace No namespace
Annotations
This describes the form factor of the fuse body.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="FuseClass" type="xs:string">
  <xs:annotation>
    <xs:documentation>This describes the form factor of the fuse body.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / Ocpd / CircuitBreaker
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_CurrentRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_AcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_DcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_Manufacturer CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_ModelNumber CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType CommonElectrical_xsd.tmp#CircuitBreakerType_DisconnectInterruptRating CommonElectrical_xsd.tmp#CircuitBreakerType_IncludesGFPDevice CommonElectrical_xsd.tmp#CircuitBreakerType
Type CircuitBreakerType
Type hierarchy
Properties
content: complex
Model CurrentRating , AcVoltageRating{0,1} , DcVoltageRating{0,1} , Manufacturer{0,1} , ModelNumber{0,1} , DisconnectInterruptRating{0,1} , IncludesGFPDevice{0,1}
Children AcVoltageRating, CurrentRating, DcVoltageRating, DisconnectInterruptRating, IncludesGFPDevice, Manufacturer, ModelNumber
Instance
<CircuitBreaker>
  <CurrentRating>{1,1}</CurrentRating>
  <AcVoltageRating>{0,1}</AcVoltageRating>
  <DcVoltageRating>{0,1}</DcVoltageRating>
  <Manufacturer>{0,1}</Manufacturer>
  <ModelNumber>{0,1}</ModelNumber>
  <DisconnectInterruptRating>{0,1}</DisconnectInterruptRating>
  <IncludesGFPDevice>{0,1}</IncludesGFPDevice>
</CircuitBreaker>
Source
<xs:element name="CircuitBreaker" type="CircuitBreakerType"/>
Element CircuitBreakerType / DisconnectInterruptRating
Namespace No namespace
Annotations
Circuit breakers have disconnect interrupt ratings in Amps. Typical ratings include: 5000, 10000, 23000, 42000.  Typically if rating is not listed on a breaker, it is 5000.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element minOccurs="0" name="DisconnectInterruptRating" type="xs:integer" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Circuit breakers have disconnect interrupt ratings in Amps. Typical ratings include: 5000, 10000, 23000, 42000. Typically if rating is not listed on a breaker, it is 5000.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitBreakerType / IncludesGFPDevice
Namespace No namespace
Annotations
Commercial only. Does the OCPD include a Ground Fault Protection (GFP) device?
Diagram
Diagram
Type xs:boolean
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element minOccurs="0" name="IncludesGFPDevice" type="xs:boolean" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Commercial only. Does the OCPD include a Ground Fault Protection (GFP) device?</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / SideOfPanelOcpdWhereConnected
Namespace No namespace
Annotations
When a circuit connection is made on an ElectricalPanel, which side of a the panel's main breaker (if present) is the interconnection made (supply or load side)?
This is a very important consideration, as the NEC dictates the maximum allowable interconnected current, and it is very different for each side of the OCPD.  For example, when tied to the load side of a panel's bus, the total of all circuits amperage can sum to 120% of the bus's current rating when using a backfed breaker.  If tied to the supply side, the allowable PV circuit amperage can go up to the maximum rated amperage of the bus (as the main breaker protects the load side).  Note that this also differs between residential and commercial systems. Most residential systems are interconnected on the load side. Conversely, most commercial systems are interconnected on the supply side because NEC 690 currently has no 120% rule on commercial load side tie-in (significantly limiting possible size), and also commercial system equipment is more likely to have connections available on the supply side (e.g. lugs).
Diagram
Diagram CommonElectrical_xsd.tmp#SideOfPanelOcpdWhereConnectedEnumType
Type SideOfPanelOcpdWhereConnectedEnumType
Properties
content: simple
minOccurs: 0
default: load-side
Facets
enumeration supply-side
enumeration load-side
Source
<xs:element default="load-side" minOccurs="0" name="SideOfPanelOcpdWhereConnected" type="SideOfPanelOcpdWhereConnectedEnumType">
  <xs:annotation>
    <xs:documentation>When a circuit connection is made on an ElectricalPanel, which side of a the panel's main breaker (if present) is the interconnection made (supply or load side)? This is a very important consideration, as the NEC dictates the maximum allowable interconnected current, and it is very different for each side of the OCPD. For example, when tied to the load side of a panel's bus, the total of all circuits amperage can sum to 120% of the bus's current rating when using a backfed breaker. If tied to the supply side, the allowable PV circuit amperage can go up to the maximum rated amperage of the bus (as the main breaker protects the load side). Note that this also differs between residential and commercial systems. Most residential systems are interconnected on the load side. Conversely, most commercial systems are interconnected on the supply side because NEC 690 currently has no 120% rule on commercial load side tie-in (significantly limiting possible size), and also commercial system equipment is more likely to have connections available on the supply side (e.g. lugs).</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / ConductorConnectionMechanism
Namespace No namespace
Annotations
Optional description of how the conductors are phyisically connected. Examples:
-Dedicated circuit breaker (typical of load side, but breaker-can also be on service side if hot-bussed panel has breaker slot on the service side)
-lugs (supply side typical)
-wire taps (supply side typical)
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="ConductorConnectionMechanism" type="xs:string">
  <xs:annotation>
    <xs:documentation>Optional description of how the conductors are phyisically connected. Examples: -Dedicated circuit breaker (typical of load side, but breaker-can also be on service side if hot-bussed panel has breaker slot on the service side) -lugs (supply side typical) -wire taps (supply side typical)</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / EquipmentGroundingConductor
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#EquipmentGroundingConductorType_Egc CommonElectrical_xsd.tmp#EquipmentGroundingConductorType_EgcSize CommonElectrical_xsd.tmp#EquipmentGroundingConductorType_EgcJacket CommonElectrical_xsd.tmp#EquipmentGroundingConductorType_EgcJacketColor CommonElectrical_xsd.tmp#EquipmentGroundingConductorType_GroundingNotes CommonElectrical_xsd.tmp#EquipmentGroundingConductorType
Type EquipmentGroundingConductorType
Properties
content: complex
minOccurs: 0
Model Egc{0,1} , EgcSize , EgcJacket{0,1} , EgcJacketColor{0,1} , GroundingNotes{0,1}
Children Egc, EgcJacket, EgcJacketColor, EgcSize, GroundingNotes
Instance
<EquipmentGroundingConductor>
  <Egc>{0,1}</Egc>
  <EgcSize>{1,1}</EgcSize>
  <EgcJacket>{0,1}</EgcJacket>
  <EgcJacketColor>{0,1}</EgcJacketColor>
  <GroundingNotes>{0,1}</GroundingNotes>
</EquipmentGroundingConductor>
Source
<xs:element minOccurs="0" name="EquipmentGroundingConductor" type="EquipmentGroundingConductorType"/>
Element EquipmentGroundingConductorType / Egc
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorMaterialEnumType
Type ConductorMaterialEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration Stranded Cu
enumeration Solid Cu
enumeration Stranded Al
Source
<xs:element minOccurs="0" name="Egc" type="ConductorMaterialEnumType"/>
Element EquipmentGroundingConductorType / EgcSize
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSizeEnumType
Type ConductorSizeEnumType
Properties
content: simple
Facets
enumeration 12
enumeration 10
enumeration 8
enumeration 6
enumeration 4
enumeration 3
enumeration 2
enumeration 1/0
enumeration 2/0
enumeration 3/0
enumeration 4/0
enumeration 250
enumeration 350
enumeration 400
enumeration 500
Source
<xs:element name="EgcSize" type="ConductorSizeEnumType"/>
Element EquipmentGroundingConductorType / EgcJacket
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorJacketEnumType
Type ConductorJacketEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration bare
enumeration USE
enumeration USE-2
enumeration THWN
enumeration THWN-2
enumeration THHN
enumeration THHW
enumeration XHHW-2
enumeration RHW-2
enumeration PV Wire
Source
<xs:element minOccurs="0" name="EgcJacket" type="ConductorJacketEnumType"/>
Element EquipmentGroundingConductorType / EgcJacketColor
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
default: green
Source
<xs:element default="green" minOccurs="0" name="EgcJacketColor" type="xs:string"/>
Element EquipmentGroundingConductorType / GroundingNotes
Namespace No namespace
Annotations
Use to describe details on connection methods between grounding conductor and equipment.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="GroundingNotes" type="xs:string">
  <xs:annotation>
    <xs:documentation>Use to describe details on connection methods between grounding conductor and equipment.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnectionType / WirewaySegmentIdRef
Namespace No namespace
Annotations
The Wireway Segments through which this circuit connection runs. Can include ConduitSegments, WirewayBoxes, or both. Note that the CircuitConnection can be routed through a DisconnectSwitch or StandAloneMeterSocket without actually being switched or metered.  If the CircuitConnection is disconnected or metered, it should be called out in a separate Disconnect or StandAloneMeter element within the CircuitConnection.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element name="WirewaySegmentIdRef" type="xs:IDREF" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The Wireway Segments through which this circuit connection runs. Can include ConduitSegments, WirewayBoxes, or both. Note that the CircuitConnection can be routed through a DisconnectSwitch or StandAloneMeterSocket without actually being switched or metered. If the CircuitConnection is disconnected or metered, it should be called out in a separate Disconnect or StandAloneMeter element within the CircuitConnection.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / MainBreaker
Namespace No namespace
Annotations
Describes an internal circuit breaker, if any, that serves as the main OCPD and power disconnect to this panel's bus.  Note that the ElectricPanel may or may not have an internal main breaker.  Panels with or without a main internal breaker may also have an OCPD on the ElectricPanel's CircuitConnection element which serves as the energizing source for this panel.
Diagram
Diagram CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_CurrentRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_AcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_DcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_Manufacturer CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_ModelNumber CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType CommonElectrical_xsd.tmp#CircuitBreakerType_DisconnectInterruptRating CommonElectrical_xsd.tmp#CircuitBreakerType_IncludesGFPDevice CommonElectrical_xsd.tmp#CircuitBreakerType
Type CircuitBreakerType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model CurrentRating , AcVoltageRating{0,1} , DcVoltageRating{0,1} , Manufacturer{0,1} , ModelNumber{0,1} , DisconnectInterruptRating{0,1} , IncludesGFPDevice{0,1}
Children AcVoltageRating, CurrentRating, DcVoltageRating, DisconnectInterruptRating, IncludesGFPDevice, Manufacturer, ModelNumber
Instance
<MainBreaker>
  <CurrentRating>{1,1}</CurrentRating>
  <AcVoltageRating>{0,1}</AcVoltageRating>
  <DcVoltageRating>{0,1}</DcVoltageRating>
  <Manufacturer>{0,1}</Manufacturer>
  <ModelNumber>{0,1}</ModelNumber>
  <DisconnectInterruptRating>{0,1}</DisconnectInterruptRating>
  <IncludesGFPDevice>{0,1}</IncludesGFPDevice>
</MainBreaker>
Source
<xs:element minOccurs="0" name="MainBreaker" type="CircuitBreakerType" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Describes an internal circuit breaker, if any, that serves as the main OCPD and power disconnect to this panel's bus. Note that the ElectricPanel may or may not have an internal main breaker. Panels with or without a main internal breaker may also have an OCPD on the ElectricPanel's CircuitConnection element which serves as the energizing source for this panel.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / Existence
Namespace No namespace
Annotations
Is this panel existing or new (proposed)?  When the ElectricalPanel is used within the ExistingElectricalSystem element inside of a Project's Site element, this is assumed to be an existing panel.  However, if the panel is just being defined within a PvDesign's AcTie-InPanel element, then its important to know if the panel being described already exists or is new (and therefore part of the scope of work).
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="Existence" type="xs:string">
  <xs:annotation>
    <xs:documentation>Is this panel existing or new (proposed)? When the ElectricalPanel is used within the ExistingElectricalSystem element inside of a Project's Site element, this is assumed to be an existing panel. However, if the panel is just being defined within a PvDesign's AcTie-InPanel element, then its important to know if the panel being described already exists or is new (and therefore part of the scope of work).</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / IncludedMeter
Namespace No namespace
Annotations
If the panel is an "All in One", it has a meter socket.  This element describes the meter in that socket.
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType
Type EquipmentInstanceType
Properties
content: complex
minOccurs: 0
Model Name{0,1} , SerialNumber{0,1} , DateManufactured{0,1} , Location{0,1} , Condition{0,1} , LastServiced{0,1} , UsefulLife{0,1}
Children Condition, DateManufactured, LastServiced, Location, Name, SerialNumber, UsefulLife
Instance
<IncludedMeter EquipmentDefinitionIdRef="" id="">
  <Name>{0,1}</Name>
  <SerialNumber>{0,1}</SerialNumber>
  <DateManufactured>{0,1}</DateManufactured>
  <Location>{0,1}</Location>
  <Condition>{0,1}</Condition>
  <LastServiced>{0,1}</LastServiced>
  <UsefulLife>{0,1}</UsefulLife>
</IncludedMeter>
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF required
ID Ref of the associated equipment definition for this equipment instance.  For example, in case of a PVModule, this would be the ID of the PvModuleDefinition element that describes this particular PV module instance.
id xs:ID required
Source
<xs:element minOccurs="0" name="IncludedMeter" type="EquipmentInstanceType">
  <xs:annotation>
    <xs:documentation>If the panel is an "All in One", it has a meter socket. This element describes the meter in that socket.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / SumOfExistingFeederBreakerAmps
Namespace No namespace
Annotations
Integer quantity in Amps.  Add up the ratings for all existing breakers on the panel.  This is used to determine if existing panel configuration meets code, and if additional breakers can be added.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element maxOccurs="1" minOccurs="0" name="SumOfExistingFeederBreakerAmps" type="xs:integer">
  <xs:annotation>
    <xs:documentation>Integer quantity in Amps. Add up the ratings for all existing breakers on the panel. This is used to determine if existing panel configuration meets code, and if additional breakers can be added.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / UnusedBreakerSlotQuantity
Namespace No namespace
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element minOccurs="0" name="UnusedBreakerSlotQuantity" type="xs:integer" maxOccurs="1"/>
Element ElectricalPanelType / SupplySideLugHolesAvailable
Namespace No namespace
Annotations
Does the energizing (supply side) bus bar have pre-drilled holes suitable for adding a new supply side lug?
Diagram
Diagram
Type xs:boolean
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="SupplySideLugHolesAvailable" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Does the energizing (supply side) bus bar have pre-drilled holes suitable for adding a new supply side lug?</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / AcGroundingElectrodeConductor
Namespace No namespace
Annotations
The main service panel should have an AC system grounding conductor that runs from the grounding bus to the grounding electrode.  The grounding electrode is a ground rod, or U-fer, for example.
Diagram
Diagram CommonElectrical_xsd.tmp#GroundingElectrodeConductorType_Material CommonElectrical_xsd.tmp#GroundingElectrodeConductorType_Size CommonElectrical_xsd.tmp#GroundingElectrodeConductorType_Jacket CommonElectrical_xsd.tmp#GroundingElectrodeConductorType_GroundingElectrode CommonElectrical_xsd.tmp#GroundingElectrodeConductorType
Type GroundingElectrodeConductorType
Properties
content: complex
minOccurs: 0
Model Material , Size , Jacket , GroundingElectrode{0,1}
Children GroundingElectrode, Jacket, Material, Size
Instance
<AcGroundingElectrodeConductor>
  <Material>{1,1}</Material>
  <Size>{1,1}</Size>
  <Jacket>{1,1}</Jacket>
  <GroundingElectrode>{0,1}</GroundingElectrode>
</AcGroundingElectrodeConductor>
Source
<xs:element minOccurs="0" name="AcGroundingElectrodeConductor" type="GroundingElectrodeConductorType">
  <xs:annotation>
    <xs:documentation>The main service panel should have an AC system grounding conductor that runs from the grounding bus to the grounding electrode. The grounding electrode is a ground rod, or U-fer, for example.</xs:documentation>
  </xs:annotation>
</xs:element>
Element GroundingElectrodeConductorType / Material
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorMaterialEnumType
Type ConductorMaterialEnumType
Properties
content: simple
default: Solid Cu
Facets
enumeration Stranded Cu
enumeration Solid Cu
enumeration Stranded Al
Source
<xs:element default="Solid Cu" name="Material" type="ConductorMaterialEnumType"/>
Element GroundingElectrodeConductorType / Size
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSizeEnumType
Type ConductorSizeEnumType
Properties
content: simple
Facets
enumeration 12
enumeration 10
enumeration 8
enumeration 6
enumeration 4
enumeration 3
enumeration 2
enumeration 1/0
enumeration 2/0
enumeration 3/0
enumeration 4/0
enumeration 250
enumeration 350
enumeration 400
enumeration 500
Source
<xs:element name="Size" type="ConductorSizeEnumType"/>
Element GroundingElectrodeConductorType / Jacket
Namespace No namespace
Annotations
Should be "bare."
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorJacketEnumType
Type ConductorJacketEnumType
Properties
content: simple
default: bare
Facets
enumeration bare
enumeration USE
enumeration USE-2
enumeration THWN
enumeration THWN-2
enumeration THHN
enumeration THHW
enumeration XHHW-2
enumeration RHW-2
enumeration PV Wire
Source
<xs:element default="bare" name="Jacket" type="ConductorJacketEnumType">
  <xs:annotation>
    <xs:documentation>Should be "bare."</xs:documentation>
  </xs:annotation>
</xs:element>
Element GroundingElectrodeConductorType / GroundingElectrode
Namespace No namespace
Annotations
Grounding electrode is typically a ground rod or U-fer.  This element should include the grounding electrode's size. For example "3/4 in ground rod."
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="GroundingElectrode" type="xs:string">
  <xs:annotation>
    <xs:documentation>Grounding electrode is typically a ground rod or U-fer. This element should include the grounding electrode's size. For example "3/4 in ground rod."</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalPanelType / SubPanel
Namespace No namespace
Annotations
An electrical distribution panel downstream from the parent panel.  It has the same data structure.
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType CommonElectrical_xsd.tmp#ElectricalPanelType_EnergizingSourceCircuitConnection CommonElectrical_xsd.tmp#ElectricalPanelType_MainBreaker CommonElectrical_xsd.tmp#ElectricalPanelType_Existence CommonElectrical_xsd.tmp#ElectricalPanelType_IncludedMeter CommonElectrical_xsd.tmp#ElectricalPanelType_SumOfExistingFeederBreakerAmps CommonElectrical_xsd.tmp#ElectricalPanelType_UnusedBreakerSlotQuantity CommonElectrical_xsd.tmp#ElectricalPanelType_SupplySideLugHolesAvailable CommonElectrical_xsd.tmp#ElectricalPanelType_AcGroundingElectrodeConductor CommonElectrical_xsd.tmp#ElectricalPanelType_SubPanel CommonElectrical_xsd.tmp#ElectricalPanelType
Type ElectricalPanelType
Type hierarchy
Properties
content: complex
minOccurs: 0
Model Name{0,1} , SerialNumber{0,1} , DateManufactured{0,1} , Location{0,1} , Condition{0,1} , LastServiced{0,1} , UsefulLife{0,1} , EnergizingSourceCircuitConnection{0,1} , MainBreaker{0,1} , Existence{0,1} , IncludedMeter{0,1} , SumOfExistingFeederBreakerAmps{0,1} , UnusedBreakerSlotQuantity{0,1} , SupplySideLugHolesAvailable{0,1} , AcGroundingElectrodeConductor{0,1} , SubPanel{0,1}
Children AcGroundingElectrodeConductor, Condition, DateManufactured, EnergizingSourceCircuitConnection, Existence, IncludedMeter, LastServiced, Location, MainBreaker, Name, SerialNumber, SubPanel, SumOfExistingFeederBreakerAmps, SupplySideLugHolesAvailable, UnusedBreakerSlotQuantity, UsefulLife
Instance
<SubPanel EquipmentDefinitionIdRef="" id="">
  <Name>{0,1}</Name>
  <SerialNumber>{0,1}</SerialNumber>
  <DateManufactured>{0,1}</DateManufactured>
  <Location>{0,1}</Location>
  <Condition>{0,1}</Condition>
  <LastServiced>{0,1}</LastServiced>
  <UsefulLife>{0,1}</UsefulLife>
  <EnergizingSourceCircuitConnection EquipmentWhereConnectedIdRef="">{0,1}</EnergizingSourceCircuitConnection>
  <MainBreaker>{0,1}</MainBreaker>
  <Existence>{0,1}</Existence>
  <IncludedMeter EquipmentDefinitionIdRef="" id="">{0,1}</IncludedMeter>
  <SumOfExistingFeederBreakerAmps>{0,1}</SumOfExistingFeederBreakerAmps>
  <UnusedBreakerSlotQuantity>{0,1}</UnusedBreakerSlotQuantity>
  <SupplySideLugHolesAvailable>{0,1}</SupplySideLugHolesAvailable>
  <AcGroundingElectrodeConductor>{0,1}</AcGroundingElectrodeConductor>
  <SubPanel EquipmentDefinitionIdRef="" id="">{0,1}</SubPanel>
</SubPanel>
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF required
ID Ref of the associated equipment definition for this equipment instance.  For example, in case of a PVModule, this would be the ID of the PvModuleDefinition element that describes this particular PV module instance.
id xs:ID required
Source
<xs:element minOccurs="0" name="SubPanel" type="ElectricalPanelType">
  <xs:annotation>
    <xs:documentation>An electrical distribution panel downstream from the parent panel. It has the same data structure.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalDistributionHierarchyType / BuildingID
Namespace No namespace
Annotations
Describes the building(s) that the electrical distribution system services.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="BuildingID" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>Describes the building(s) that the electrical distribution system services.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ElectricalDistributionHierarchyType / ElectricalDistributionPanelDefinition
Namespace No namespace
Diagram
Diagram Common_xsd.tmp#EquipmentDefinitionType_id Common_xsd.tmp#EquipmentDefinitionType_Manufacturer Common_xsd.tmp#EquipmentDefinitionType_ModelNumber Common_xsd.tmp#EquipmentDefinitionType_ProductFamilyName Common_xsd.tmp#EquipmentDefinitionType_Description Common_xsd.tmp#EquipmentDefinitionType_MountingStyle Common_xsd.tmp#EquipmentDefinitionType_Length Common_xsd.tmp#EquipmentDefinitionType_Width Common_xsd.tmp#EquipmentDefinitionType_Depth Common_xsd.tmp#EquipmentDefinitionType_Weight Common_xsd.tmp#EquipmentDefinitionType_EnclosureMaterial Common_xsd.tmp#EquipmentDefinitionType_EnclosureNemaRating Common_xsd.tmp#EquipmentDefinitionType_ListingAgency Common_xsd.tmp#EquipmentDefinitionType_Warranty Common_xsd.tmp#EquipmentDefinitionType_EnergyStarRated Common_xsd.tmp#EquipmentDefinitionType_WhereManufactured Common_xsd.tmp#EquipmentDefinitionType CommonElectrical_xsd.tmp#ElectricalPanelDefinitionType_RatedCurrent CommonElectrical_xsd.tmp#ElectricalPanelDefinitionType
Type ElectricalPanelDefinitionType
Type hierarchy
Properties
content: complex
maxOccurs: unbounded
Model Manufacturer , ModelNumber , ProductFamilyName{0,1} , Description{0,1} , MountingStyle{0,1} , Length{0,1} , Width{0,1} , Depth{0,1} , Weight{0,1} , EnclosureMaterial{0,1} , EnclosureNemaRating{0,1} , ListingAgency{0,1} , Warranty{0,1} , EnergyStarRated{0,1} , WhereManufactured{0,1} , RatedCurrent
Children Depth, Description, EnclosureMaterial, EnclosureNemaRating, EnergyStarRated, Length, ListingAgency, Manufacturer, ModelNumber, MountingStyle, ProductFamilyName, RatedCurrent, Warranty, Weight, WhereManufactured, Width
Instance
<ElectricalDistributionPanelDefinition id="">
  <Manufacturer>{1,1}</Manufacturer>
  <ModelNumber>{1,1}</ModelNumber>
  <ProductFamilyName>{0,1}</ProductFamilyName>
  <Description>{0,1}</Description>
  <MountingStyle>{0,1}</MountingStyle>
  <Length>{0,1}</Length>
  <Width>{0,1}</Width>
  <Depth>{0,1}</Depth>
  <Weight>{0,1}</Weight>
  <EnclosureMaterial>{0,1}</EnclosureMaterial>
  <EnclosureNemaRating>{0,1}</EnclosureNemaRating>
  <ListingAgency>{0,1}</ListingAgency>
  <Warranty>{0,1}</Warranty>
  <EnergyStarRated>{0,1}</EnergyStarRated>
  <WhereManufactured>{0,1}</WhereManufactured>
  <RatedCurrent>{1,1}</RatedCurrent>
</ElectricalDistributionPanelDefinition>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID required
Source
<xs:element maxOccurs="unbounded" name="ElectricalDistributionPanelDefinition" type="ElectricalPanelDefinitionType"/>
Element ElectricalPanelDefinitionType / RatedCurrent
Namespace No namespace
Annotations
Rating of the bus, in Amps.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 1
maxOccurs: 1
Source
<xs:element name="RatedCurrent" type="xs:integer" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Rating of the bus, in Amps.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DisconnectSwitchDefinitionType / DiscoRating
Namespace No namespace
Annotations
Rating in amps for disconnecting an AC or DC circuit.
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 1
Source
<xs:element minOccurs="1" name="DiscoRating" type="xs:integer">
  <xs:annotation>
    <xs:documentation>Rating in amps for disconnecting an AC or DC circuit.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DisconnectSwitchDefinitionType / AcVoltageRating
Namespace No namespace
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="AcVoltageRating" type="xs:integer"/>
Element DisconnectSwitchDefinitionType / DcVoltageRating
Namespace No namespace
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="DcVoltageRating" type="xs:integer"/>
Element DisconnectSwitchDefinitionType / SwitchContact
Namespace No namespace
Annotations
The terms pole and throw are also used to describe switch contact variations. The number of "poles" is the number of separate circuits which are controlled by a switch. For example, a "2-pole" switch has two separate identical sets of contacts controlled by the same knob. The number of "throws" is the number of separate positions that the switch can adopt. A single-throw switch has one pair of contacts that can either be closed or open. A double-throw switch has a contact that can be connected to either of two other contacts, a triple-throw has a contact which can be connected to one of three other contacts, etc
Diagram
Diagram CommonElectrical_xsd.tmp#SwitchContactActionEnumType
Type SwitchContactActionEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration SPST
enumeration DPST
enumeration 3PST
enumeration SPDT
Source
<xs:element name="SwitchContact" minOccurs="0" type="SwitchContactActionEnumType">
  <xs:annotation>
    <xs:documentation>The terms pole and throw are also used to describe switch contact variations. The number of "poles" is the number of separate circuits which are controlled by a switch. For example, a "2-pole" switch has two separate identical sets of contacts controlled by the same knob. The number of "throws" is the number of separate positions that the switch can adopt. A single-throw switch has one pair of contacts that can either be closed or open. A double-throw switch has a contact that can be connected to either of two other contacts, a triple-throw has a contact which can be connected to one of three other contacts, etc</xs:documentation>
  </xs:annotation>
</xs:element>
Element DisconnectSwitchDefinitionType / Duty
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#SwitchDutyEnumType
Type SwitchDutyEnumType
Properties
content: simple
minOccurs: 0
Facets
enumeration General-Duty
enumeration Heavy-Duty
Source
<xs:element minOccurs="0" name="Duty" type="SwitchDutyEnumType"/>
Element DisconnectSwitchDefinitionType / VisibleLock
Namespace No namespace
Annotations
Does the switch have a visible locking mechnism?
Diagram
Diagram
Type xs:boolean
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="VisibleLock" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Does the switch have a visible locking mechnism?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DisconnectSwitchDefinitionType / Fusible
Namespace No namespace
Annotations
Do the switch circuits include fuses?
Diagram
Diagram
Type xs:boolean
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="Fusible" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Do the switch circuits include fuses?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DisconnectSwitchDefinitionType / Fuse
Namespace No namespace
Annotations
If the switch includes fuses, this describes the fuses.
Diagram
Diagram CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_CurrentRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_AcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_DcVoltageRating CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_Manufacturer CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType_ModelNumber CommonElectrical_xsd.tmp#OverCurrentProtectionDeviceType CommonElectrical_xsd.tmp#FuseType_FuseClass CommonElectrical_xsd.tmp#FuseType
Type FuseType
Type hierarchy
Properties
content: complex
minOccurs: 0
Model CurrentRating , AcVoltageRating{0,1} , DcVoltageRating{0,1} , Manufacturer{0,1} , ModelNumber{0,1} , FuseClass{0,1}
Children AcVoltageRating, CurrentRating, DcVoltageRating, FuseClass, Manufacturer, ModelNumber
Instance
<Fuse>
  <CurrentRating>{1,1}</CurrentRating>
  <AcVoltageRating>{0,1}</AcVoltageRating>
  <DcVoltageRating>{0,1}</DcVoltageRating>
  <Manufacturer>{0,1}</Manufacturer>
  <ModelNumber>{0,1}</ModelNumber>
  <FuseClass>{0,1}</FuseClass>
</Fuse>
Source
<xs:element minOccurs="0" name="Fuse" type="FuseType">
  <xs:annotation>
    <xs:documentation>If the switch includes fuses, this describes the fuses.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ConduitSegmentType / ConduitType
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#TypeOfConduitEnumType
Type TypeOfConduitEnumType
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
enumeration EMT
enumeration PVC
enumeration Rigid
Source
<xs:element name="ConduitType" type="TypeOfConduitEnumType" minOccurs="0" maxOccurs="1"/>
Element ConduitSegmentType / ConduitDiameter
Namespace No namespace
Diagram
Diagram CommonElectrical_xsd.tmp#ConduitDiameterEnumType
Type ConduitDiameterEnumType
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
enumeration 1/2
enumeration 3/4
enumeration 1
enumeration 1 1/4
enumeration 1 1/2
enumeration 2
Source
<xs:element name="ConduitDiameter" type="ConduitDiameterEnumType" minOccurs="0" maxOccurs="1"/>
Element ConduitSegmentType / ConduitLength
Namespace No namespace
Annotations
The length in feet of the conduit segment.  Values should be rounded up to nearest foot.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
Source
<xs:element name="ConduitLength" type="xs:double" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The length in feet of the conduit segment. Values should be rounded up to nearest foot.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ConduitSegmentType / SegmentConnection
Namespace No namespace
Annotations
The ID Ref for another WirewaySegment or Equipment to which the Coduit segment connects.  Conduit is a pipe with 2 ends, so it has a maximum of two WirewaySegments or Equipment to which it connects.  Boxes can have many WirewaySegment connections.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 2
Source
<xs:element maxOccurs="2" name="SegmentConnection" type="xs:IDREF" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The ID Ref for another WirewaySegment or Equipment to which the Coduit segment connects. Conduit is a pipe with 2 ends, so it has a maximum of two WirewaySegments or Equipment to which it connects. Boxes can have many WirewaySegment connections.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CircuitConnection
Namespace http://www.iepmodel.net
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentWhereConnectedIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_Name CommonElectrical_xsd.tmp#CircuitConnectionType_CurrentType CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConductors CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesDisconnect CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesStandAloneMeter CommonElectrical_xsd.tmp#CircuitConnectionType_Ocpd CommonElectrical_xsd.tmp#CircuitConnectionType_SideOfPanelOcpdWhereConnected CommonElectrical_xsd.tmp#CircuitConnectionType_ConductorConnectionMechanism CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentGroundingConductor CommonElectrical_xsd.tmp#CircuitConnectionType_WirewaySegmentIdRef CommonElectrical_xsd.tmp#CircuitConnectionType
Type CircuitConnectionType
Properties
content: complex
Model Name{0,1} , CurrentType{0,1} , CircuitConductors , IncludesDisconnect{0,1} , IncludesStandAloneMeter{0,1} , Ocpd{0,1} , SideOfPanelOcpdWhereConnected{0,1} , ConductorConnectionMechanism{0,1} , EquipmentGroundingConductor{0,1} , WirewaySegmentIdRef*
Children CircuitConductors, ConductorConnectionMechanism, CurrentType, EquipmentGroundingConductor, IncludesDisconnect, IncludesStandAloneMeter, Name, Ocpd, SideOfPanelOcpdWhereConnected, WirewaySegmentIdRef
Instance
<CircuitConnection EquipmentWhereConnectedIdRef="" xmlns="http://www.iepmodel.net">
  <Name>{0,1}</Name>
  <CurrentType>{0,1}</CurrentType>
  <CircuitConductors>{1,1}</CircuitConductors>
  <IncludesDisconnect ConductorSegmentIdRef="" WirewayBoxIdRef="">{0,1}</IncludesDisconnect>
  <IncludesStandAloneMeter ConductorSegmentIdRef="">{0,1}</IncludesStandAloneMeter>
  <Ocpd EquipmentWhereLocatedIdRef="">{0,1}</Ocpd>
  <SideOfPanelOcpdWhereConnected>{0,1}</SideOfPanelOcpdWhereConnected>
  <ConductorConnectionMechanism>{0,1}</ConductorConnectionMechanism>
  <EquipmentGroundingConductor>{0,1}</EquipmentGroundingConductor>
  <WirewaySegmentIdRef>{0,unbounded}</WirewaySegmentIdRef>
</CircuitConnection>
Attributes
QName Type Fixed Default Use Annotation
EquipmentWhereConnectedIdRef xs:IDREF optional
In cases where the CircuitConnection element is used within an EquipmentInstance that does not have a parent element to which the CircuitConnection is assumed to connect, a reference ID can be used to associate this CircuitConnection to another EquipmentInstance elsewhere in a document instance.  For example, a PvSystem may have an AcPointOfConnection that uses a new ElectricalPanel as an AC combiner for more than one Inverter.  The new electrical panel can be described by an  ElectricalPanel element in the PvDesign (which in turn refers to an ElectricalPanelDefinition element).

in the AcPointOfConnection's EquipmentWhereConnected element.  That ElectricPanel's EnergizingCircuitConnection element may reference another ElectricPanel in an instance of the Project's ExistingElectricalHierarchy element.
Source
<xs:element name="CircuitConnection" type="CircuitConnectionType"/>
Element ElectricalDistributionHierarchy
Namespace http://www.iepmodel.net
Annotations
Diagram
Diagram CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_ElectricalDistributionPanel CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_BuildingID CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_ElectricalDistributionPanelDefinition CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType
Type ElectricalDistributionHierarchyType
Properties
content: complex
Model ElectricalDistributionPanel , BuildingID* , ElectricalDistributionPanelDefinition+
Children BuildingID, ElectricalDistributionPanel, ElectricalDistributionPanelDefinition
Instance
<ElectricalDistributionHierarchy xmlns="http://www.iepmodel.net">
  <ElectricalDistributionPanel EquipmentDefinitionIdRef="" id="">{1,1}</ElectricalDistributionPanel>
  <BuildingID>{0,unbounded}</BuildingID>
  <ElectricalDistributionPanelDefinition id="">{1,unbounded}</ElectricalDistributionPanelDefinition>
</ElectricalDistributionHierarchy>
Source
<xs:element name="ElectricalDistributionHierarchy" type="ElectricalDistributionHierarchyType">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
</xs:element>
Element MeterDefinitionType / Directionality
Namespace No namespace
Annotations
Is the meter mono or bi-directional?
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="Directionality" type="xs:string">
  <xs:annotation>
    <xs:documentation>Is the meter mono or bi-directional?</xs:documentation>
  </xs:annotation>
</xs:element>
Element MeterDefinitionType / MeasurementMechanism
Namespace No namespace
Annotations
What type of measurement mechanism does the meter employ? For example, "current transducer" or "inline electro-mechanical"
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="MeasurementMechanism" type="xs:string">
  <xs:annotation>
    <xs:documentation>What type of measurement mechanism does the meter employ? For example, "current transducer" or "inline electro-mechanical"</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type WirewaySegmentType
Namespace http://www.iepmodel.net
Annotations
Base definition of a WirewaySegment, which is a distinct piece of wireway through which electrical wiring is housed for its prtotection and the protection of people and property. Wireway segments can be either electrical conduit or boxes. Multiple segments are connected to form a single continuous path for one or more CircuitConnections. Each segment is distinct by its characteristics.
Diagram
Diagram CommonElectrical_xsd.tmp#WirewaySegmentType_id CommonElectrical_xsd.tmp#WirewaySegmentType_EquipmentDefinitionIdRef CommonElectrical_xsd.tmp#WirewaySegmentType_Name CommonElectrical_xsd.tmp#WirewaySegmentType_LocationDescription CommonElectrical_xsd.tmp#WirewaySegmentType_HighTempExposure
Properties
abstract: true
Used by
Model Name{0,1} , LocationDescription{0,1} , HighTempExposure{0,1}
Children HighTempExposure, LocationDescription, Name
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF optional
If the WirewaySegment is a junction box or disconnect switch, this refers to its EquipmentDefinition. A WirewayBox may be a pass through where multiple ConduitSegments are combined into a single ConduitSegment for example.  A disconnect switch box may also be modeled as a WirewayBox, provided that the circuit(s) involved are simply disoconnected and not combined in any way. DO NOT use WirewayBox to represent a combiner, or distribution panel.
id xs:ID required
Source
<xs:complexType name="WirewaySegmentType" abstract="true">
  <xs:annotation>
    <xs:documentation>Base definition of a WirewaySegment, which is a distinct piece of wireway through which electrical wiring is housed for its prtotection and the protection of people and property. Wireway segments can be either electrical conduit or boxes. Multiple segments are connected to form a single continuous path for one or more CircuitConnections. Each segment is distinct by its characteristics.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Name" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>A name given in context to the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="LocationDescription" type="xs:string">
      <xs:annotation>
        <xs:documentation>Description of where the segment is, or through which locations it traverses. Include descriptions such as attic, interior, exterior, roof, or trench.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="HighTempExposure" type="xs:boolean" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Is the conduit exposed to high temperatures? For example, sitting on a roof in direct sun. If so, any conductors contained within the segment may have to have their rated current carrying capacity derated.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
  <xs:attribute name="EquipmentDefinitionIdRef" type="xs:IDREF">
    <xs:annotation>
      <xs:documentation>If the WirewaySegment is a junction box or disconnect switch, this refers to its EquipmentDefinition. A WirewayBox may be a pass through where multiple ConduitSegments are combined into a single ConduitSegment for example. A disconnect switch box may also be modeled as a WirewayBox, provided that the circuit(s) involved are simply disoconnected and not combined in any way. DO NOT use WirewayBox to represent a combiner, or distribution panel.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type ElectricalDistributionHierarchyType
Namespace http://www.iepmodel.net
Annotations
Describes a part of, or an entire electrical distribution system composed of one or more panels/load centers/fuse boxes in a hierarchical tree arrangement.
Diagram
Diagram CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_ElectricalDistributionPanel CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_BuildingID CommonElectrical_xsd.tmp#ElectricalDistributionHierarchyType_ElectricalDistributionPanelDefinition
Used by
Model ElectricalDistributionPanel , BuildingID* , ElectricalDistributionPanelDefinition+
Children BuildingID, ElectricalDistributionPanel, ElectricalDistributionPanelDefinition
Source
<xs:complexType name="ElectricalDistributionHierarchyType">
  <xs:annotation>
    <xs:documentation>Describes a part of, or an entire electrical distribution system composed of one or more panels/load centers/fuse boxes in a hierarchical tree arrangement.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="ElectricalDistributionPanel" type="ElectricalPanelType"/>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="BuildingID" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>Describes the building(s) that the electrical distribution system services.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" name="ElectricalDistributionPanelDefinition" type="ElectricalPanelDefinitionType"/>
  </xs:sequence>
</xs:complexType>
Complex Type ElectricalPanelType
Namespace http://www.iepmodel.net
Annotations
Describes any sort of electrical distribution panel, for example a fused panel, a breaker panel, etc.  Can be a main or sub-panel.
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType CommonElectrical_xsd.tmp#ElectricalPanelType_EnergizingSourceCircuitConnection CommonElectrical_xsd.tmp#ElectricalPanelType_MainBreaker CommonElectrical_xsd.tmp#ElectricalPanelType_Existence CommonElectrical_xsd.tmp#ElectricalPanelType_IncludedMeter CommonElectrical_xsd.tmp#ElectricalPanelType_SumOfExistingFeederBreakerAmps CommonElectrical_xsd.tmp#ElectricalPanelType_UnusedBreakerSlotQuantity CommonElectrical_xsd.tmp#ElectricalPanelType_SupplySideLugHolesAvailable CommonElectrical_xsd.tmp#ElectricalPanelType_AcGroundingElectrodeConductor CommonElectrical_xsd.tmp#ElectricalPanelType_SubPanel
Type extension of EquipmentInstanceType
Type hierarchy
Used by
Model Name{0,1} , SerialNumber{0,1} , DateManufactured{0,1} , Location{0,1} , Condition{0,1} , LastServiced{0,1} , UsefulLife{0,1} , EnergizingSourceCircuitConnection{0,1} , MainBreaker{0,1} , Existence{0,1} , IncludedMeter{0,1} , SumOfExistingFeederBreakerAmps{0,1} , UnusedBreakerSlotQuantity{0,1} , SupplySideLugHolesAvailable{0,1} , AcGroundingElectrodeConductor{0,1} , SubPanel{0,1}
Children AcGroundingElectrodeConductor, Condition, DateManufactured, EnergizingSourceCircuitConnection, Existence, IncludedMeter, LastServiced, Location, MainBreaker, Name, SerialNumber, SubPanel, SumOfExistingFeederBreakerAmps, SupplySideLugHolesAvailable, UnusedBreakerSlotQuantity, UsefulLife
Attributes
QName Type Fixed Default Use Annotation
EquipmentDefinitionIdRef xs:IDREF required
ID Ref of the associated equipment definition for this equipment instance.  For example, in case of a PVModule, this would be the ID of the PvModuleDefinition element that describes this particular PV module instance.
id xs:ID required
Source
<xs:complexType name="ElectricalPanelType">
  <xs:annotation>
    <xs:documentation>Describes any sort of electrical distribution panel, for example a fused panel, a breaker panel, etc. Can be a main or sub-panel.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="EquipmentInstanceType">
      <xs:sequence>
        <xs:element minOccurs="0" name="EnergizingSourceCircuitConnection" type="CircuitConnectionType" maxOccurs="1">
          <xs:annotation>
            <xs:documentation>Description of the conductor energizing the panel. Should include description of OCPD / disco at source end.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="MainBreaker" type="CircuitBreakerType" maxOccurs="1">
          <xs:annotation>
            <xs:documentation>Describes an internal circuit breaker, if any, that serves as the main OCPD and power disconnect to this panel's bus. Note that the ElectricPanel may or may not have an internal main breaker. Panels with or without a main internal breaker may also have an OCPD on the ElectricPanel's CircuitConnection element which serves as the energizing source for this panel.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Existence" type="xs:string">
          <xs:annotation>
            <xs:documentation>Is this panel existing or new (proposed)? When the ElectricalPanel is used within the ExistingElectricalSystem element inside of a Project's Site element, this is assumed to be an existing panel. However, if the panel is just being defined within a PvDesign's AcTie-InPanel element, then its important to know if the panel being described already exists or is new (and therefore part of the scope of work).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="IncludedMeter" type="EquipmentInstanceType">
          <xs:annotation>
            <xs:documentation>If the panel is an "All in One", it has a meter socket. This element describes the meter in that socket.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="SumOfExistingFeederBreakerAmps" type="xs:integer">
          <xs:annotation>
            <xs:documentation>Integer quantity in Amps. Add up the ratings for all existing breakers on the panel. This is used to determine if existing panel configuration meets code, and if additional breakers can be added.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="UnusedBreakerSlotQuantity" type="xs:integer" maxOccurs="1"/>
        <xs:element minOccurs="0" name="SupplySideLugHolesAvailable" type="xs:boolean">
          <xs:annotation>
            <xs:documentation>Does the energizing (supply side) bus bar have pre-drilled holes suitable for adding a new supply side lug?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="AcGroundingElectrodeConductor" type="GroundingElectrodeConductorType">
          <xs:annotation>
            <xs:documentation>The main service panel should have an AC system grounding conductor that runs from the grounding bus to the grounding electrode. The grounding electrode is a ground rod, or U-fer, for example.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="SubPanel" type="ElectricalPanelType">
          <xs:annotation>
            <xs:documentation>An electrical distribution panel downstream from the parent panel. It has the same data structure.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type CircuitConnectionType
Namespace http://www.iepmodel.net
Annotations
A CircuitConnection defines a portion of an electrical circuit connecting two distinct components of an electrical system (for example, the connection of a PV String to a CombinerBox).  A CircuitConnection is made by conductors. One end of the CircuitConnection is the element in which the CircuitConnection exists, and the other end is typically the parent element of the element in which the CircuitConnection element resides. For example, a CombinerBox element can have multiple PvString elements within it.  Each PvString element contains a CircuitConnection element which defines its connection to the CombinerBox.  A CombinerBox has a CircuitConnection element which defines its connection to an InverterDcInput, for example.

Optionally, the CircuitConnectionType contains an optional EquipmentWhereConnectedIdRef attribute which can be used to reference another electrical equipment element in another part of a document.  For example, a PvDesign's Inverter has no parent element.  Instead, it's AcTie-InCircuitConnection uses the EquipmentWhereConnectedIdRef attribute to reference either an ElectricalPanel within the PvDesign, or an ElectricalPanel within a Project's ExistingElectricalDistributionHierarchy element may exist.
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentWhereConnectedIdRef CommonElectrical_xsd.tmp#CircuitConnectionType_Name CommonElectrical_xsd.tmp#CircuitConnectionType_CurrentType CommonElectrical_xsd.tmp#CircuitConnectionType_CircuitConductors CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesDisconnect CommonElectrical_xsd.tmp#CircuitConnectionType_IncludesStandAloneMeter CommonElectrical_xsd.tmp#CircuitConnectionType_Ocpd CommonElectrical_xsd.tmp#CircuitConnectionType_SideOfPanelOcpdWhereConnected CommonElectrical_xsd.tmp#CircuitConnectionType_ConductorConnectionMechanism CommonElectrical_xsd.tmp#CircuitConnectionType_EquipmentGroundingConductor CommonElectrical_xsd.tmp#CircuitConnectionType_WirewaySegmentIdRef
Used by
Model Name{0,1} , CurrentType{0,1} , CircuitConductors , IncludesDisconnect{0,1} , IncludesStandAloneMeter{0,1} , Ocpd{0,1} , SideOfPanelOcpdWhereConnected{0,1} , ConductorConnectionMechanism{0,1} , EquipmentGroundingConductor{0,1} , WirewaySegmentIdRef*
Children CircuitConductors, ConductorConnectionMechanism, CurrentType, EquipmentGroundingConductor, IncludesDisconnect, IncludesStandAloneMeter, Name, Ocpd, SideOfPanelOcpdWhereConnected, WirewaySegmentIdRef
Attributes
QName Type Fixed Default Use Annotation
EquipmentWhereConnectedIdRef xs:IDREF optional
In cases where the CircuitConnection element is used within an EquipmentInstance that does not have a parent element to which the CircuitConnection is assumed to connect, a reference ID can be used to associate this CircuitConnection to another EquipmentInstance elsewhere in a document instance.  For example, a PvSystem may have an AcPointOfConnection that uses a new ElectricalPanel as an AC combiner for more than one Inverter.  The new electrical panel can be described by an  ElectricalPanel element in the PvDesign (which in turn refers to an ElectricalPanelDefinition element).

in the AcPointOfConnection's EquipmentWhereConnected element.  That ElectricPanel's EnergizingCircuitConnection element may reference another ElectricPanel in an instance of the Project's ExistingElectricalHierarchy element.
Source
<xs:complexType name="CircuitConnectionType">
  <xs:annotation>
    <xs:documentation>A CircuitConnection defines a portion of an electrical circuit connecting two distinct components of an electrical system (for example, the connection of a PV String to a CombinerBox). A CircuitConnection is made by conductors. One end of the CircuitConnection is the element in which the CircuitConnection exists, and the other end is typically the parent element of the element in which the CircuitConnection element resides. For example, a CombinerBox element can have multiple PvString elements within it. Each PvString element contains a CircuitConnection element which defines its connection to the CombinerBox. A CombinerBox has a CircuitConnection element which defines its connection to an InverterDcInput, for example. Optionally, the CircuitConnectionType contains an optional EquipmentWhereConnectedIdRef attribute which can be used to reference another electrical equipment element in another part of a document. For example, a PvDesign's Inverter has no parent element. Instead, it's AcTie-InCircuitConnection uses the EquipmentWhereConnectedIdRef attribute to reference either an ElectricalPanel within the PvDesign, or an ElectricalPanel within a Project's ExistingElectricalDistributionHierarchy element may exist.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element minOccurs="0" name="Name" type="xs:string">
      <xs:annotation>
        <xs:documentation>An optional free text identifier.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="CurrentType" minOccurs="0" type="CurrentEnumType">
      <xs:annotation>
        <xs:documentation>AC or DC</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="CircuitConductors" type="CircuitConnectionConductorType"/>
    <xs:element minOccurs="0" name="IncludesDisconnect">
      <xs:annotation>
        <xs:documentation>If the CircuitConnection has a disconnect switch in it, this calls it out.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:attribute name="WirewayBoxIdRef" type="xs:IDREF" use="required">
          <xs:annotation>
            <xs:documentation>Reference to an instance of the DisconnectSwitch modeled generally as a WirewayBox. A disconnect switch can switch more than one CircuitConnection, so it is defined external to the CircuitConnection.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="ConductorSegmentIdRef" type="xs:IDREF" use="required">
          <xs:annotation>
            <xs:documentation>ConductorSegment that contains the disconnect switch.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
    <xs:element minOccurs="0" name="IncludesStandAloneMeter">
      <xs:annotation>
        <xs:documentation>If the CircuitConnection is metered (for example the utility's revenue meter), this element describes the meter socket and meter. The meter and socket are individual entities. The MeterSocket is modeled as a simple WirewayBox.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="MeterSocket" type="WirewayBoxType"/>
          <xs:element name="Meter" type="EquipmentInstanceType"/>
        </xs:sequence>
        <xs:attribute name="ConductorSegmentIdRef" type="xs:IDREF"/>
      </xs:complexType>
    </xs:element>
    <xs:element name="Ocpd" minOccurs="0" form="unqualified">
      <xs:annotation>
        <xs:documentation>Over current protection device (OCPD). A device that protects the conductor from too much current by breaking the circuit. Fuses and circuit breakers are OCPDs. In this schema, an OCPD is not a piece of equipment, but rather a component within a piece of equipment. It is not necessary to include a mfr and model in most cases, but knowing the type and rating is required.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:choice>
          <xs:element name="Fuse" type="FuseType"/>
          <xs:element name="CircuitBreaker" type="CircuitBreakerType"/>
        </xs:choice>
        <xs:attribute name="EquipmentWhereLocatedIdRef">
          <xs:annotation>
            <xs:documentation>The ID referring to the equipment in which the OCPD is installed. In most cases, it is the parent Equipment of the CircuitConnection's immediate parent element. For example, if the CircuitConnection is within a StringInverter element, then the circuit breaker within the ElectricalPanel to which the Inverter connects will most like be the referenced OCPD.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
    <xs:element default="load-side" minOccurs="0" name="SideOfPanelOcpdWhereConnected" type="SideOfPanelOcpdWhereConnectedEnumType">
      <xs:annotation>
        <xs:documentation>When a circuit connection is made on an ElectricalPanel, which side of a the panel's main breaker (if present) is the interconnection made (supply or load side)? This is a very important consideration, as the NEC dictates the maximum allowable interconnected current, and it is very different for each side of the OCPD. For example, when tied to the load side of a panel's bus, the total of all circuits amperage can sum to 120% of the bus's current rating when using a backfed breaker. If tied to the supply side, the allowable PV circuit amperage can go up to the maximum rated amperage of the bus (as the main breaker protects the load side). Note that this also differs between residential and commercial systems. Most residential systems are interconnected on the load side. Conversely, most commercial systems are interconnected on the supply side because NEC 690 currently has no 120% rule on commercial load side tie-in (significantly limiting possible size), and also commercial system equipment is more likely to have connections available on the supply side (e.g. lugs).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="ConductorConnectionMechanism" type="xs:string">
      <xs:annotation>
        <xs:documentation>Optional description of how the conductors are phyisically connected. Examples: -Dedicated circuit breaker (typical of load side, but breaker-can also be on service side if hot-bussed panel has breaker slot on the service side) -lugs (supply side typical) -wire taps (supply side typical)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="EquipmentGroundingConductor" type="EquipmentGroundingConductorType"/>
    <xs:element name="WirewaySegmentIdRef" type="xs:IDREF" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The Wireway Segments through which this circuit connection runs. Can include ConduitSegments, WirewayBoxes, or both. Note that the CircuitConnection can be routed through a DisconnectSwitch or StandAloneMeterSocket without actually being switched or metered. If the CircuitConnection is disconnected or metered, it should be called out in a separate Disconnect or StandAloneMeter element within the CircuitConnection.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="EquipmentWhereConnectedIdRef" type="xs:IDREF">
    <xs:annotation>
      <xs:documentation>In cases where the CircuitConnection element is used within an EquipmentInstance that does not have a parent element to which the CircuitConnection is assumed to connect, a reference ID can be used to associate this CircuitConnection to another EquipmentInstance elsewhere in a document instance. For example, a PvSystem may have an AcPointOfConnection that uses a new ElectricalPanel as an AC combiner for more than one Inverter. The new electrical panel can be described by an ElectricalPanel element in the PvDesign (which in turn refers to an ElectricalPanelDefinition element). in the AcPointOfConnection's EquipmentWhereConnected element. That ElectricPanel's EnergizingCircuitConnection element may reference another ElectricPanel in an instance of the Project's ExistingElectricalHierarchy element.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Simple Type CurrentEnumType
Namespace http://www.iepmodel.net
Annotations
Types of electrical current.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration AC
enumeration DC
Used by
Source
<xs:simpleType name="CurrentEnumType">
  <xs:annotation>
    <xs:documentation>Types of electrical current.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="AC"/>
    <xs:enumeration value="DC"/>
  </xs:restriction>
</xs:simpleType>
Complex Type CircuitConnectionConductorType
Namespace http://www.iepmodel.net
Annotations
A CircuitConnectionConductor can be made up of multiple segments of wire, as long as they share the same current carrying capacity, defined by its ConductorSize.  In PV Systems, for example, its common for an array's wiring to transition from wire outside of conduit into wire inside conduit.  The wire is spliced together within a box (e.g. WirewayBox).
Diagram
Diagram CommonElectrical_xsd.tmp#CircuitConnectionConductorType_ConductorSize CommonElectrical_xsd.tmp#CircuitConnectionConductorType_ConductorQuantity CommonElectrical_xsd.tmp#CircuitConnectionConductorType_PrimaryConductorSegment CommonElectrical_xsd.tmp#CircuitConnectionConductorType_SecondaryConductorSegment
Used by
Model ConductorSize , ConductorQuantity , PrimaryConductorSegment{0,1} , SecondaryConductorSegment*
Children ConductorQuantity, ConductorSize, PrimaryConductorSegment, SecondaryConductorSegment
Source
<xs:complexType name="CircuitConnectionConductorType">
  <xs:annotation>
    <xs:documentation>A CircuitConnectionConductor can be made up of multiple segments of wire, as long as they share the same current carrying capacity, defined by its ConductorSize. In PV Systems, for example, its common for an array's wiring to transition from wire outside of conduit into wire inside conduit. The wire is spliced together within a box (e.g. WirewayBox).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="ConductorSize" type="ConductorSizeEnumType">
      <xs:annotation>
        <xs:documentation>Wire diameter, given in American Wire Gauge (AWG), or kcmil. The entire circuit connection conductor is assumed to be the same size conductor, even if it is physically made up of multiple conductor segments that are different kinds of wire.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="1" name="ConductorQuantity" type="xs:integer">
      <xs:annotation>
        <xs:documentation>Number of conductors used to connect the circuit. Residential 120V uses 2 conductors, whereas 240V typically uses three conductors, and commercial three phase typically is 4 conductors.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="PrimaryConductorSegment" type="ConductorSegmentType">
      <xs:annotation>
        <xs:documentation>This is the segment of the CircuitConductor that is connected directly to the electrical component that this CircuitConnection belongs to. For example, let's assume that this ConductorSegment is part of a CircuitConnection for a PvString. The PvString typically starts out as USE-2 wire from the PV Modules and may transition to THWN-2 wire once inside a J-box (modeled as a Wireway box in this schema). The USE-2 segment of the conductor is the Primary segment, while the THWN-2 wire is a secondary segment. All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="SecondaryConductorSegment">
      <xs:annotation>
        <xs:documentation>A portion of a CircuitConnectionConductor that is of a different type of wire than the Primary. All CircuitConnectionConductors have a primary segment, only some have any secondary instances. If there are more than one, then the splices made beween them are described by the ConnectsToConductorSegmentId and the WirewaySegmentWhereConnectedId attributes.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:complexContent>
          <xs:extension base="ConductorSegmentType">
            <xs:attribute name="ConnectsToConductorSegmentId" type="xs:IDREF" use="required"/>
            <xs:attribute name="WirewaySegmentWhereConnectedId" type="xs:IDREF" use="required"/>
          </xs:extension>
        </xs:complexContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Simple Type ConductorSizeEnumType
Namespace http://www.iepmodel.net
Annotations
Standard wire sizes in AWG or kcmil.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration 12
enumeration 10
enumeration 8
enumeration 6
enumeration 4
enumeration 3
enumeration 2
enumeration 1/0
enumeration 2/0
enumeration 3/0
enumeration 4/0
enumeration 250
enumeration 350
enumeration 400
enumeration 500
Used by
Source
<xs:simpleType name="ConductorSizeEnumType">
  <xs:annotation>
    <xs:documentation>Standard wire sizes in AWG or kcmil.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="12"/>
    <xs:enumeration value="10"/>
    <xs:enumeration value="8"/>
    <xs:enumeration value="6"/>
    <xs:enumeration value="4"/>
    <xs:enumeration value="3"/>
    <xs:enumeration value="2"/>
    <xs:enumeration value="1/0"/>
    <xs:enumeration value="2/0"/>
    <xs:enumeration value="3/0"/>
    <xs:enumeration value="4/0"/>
    <xs:enumeration value="250"/>
    <xs:enumeration value="350"/>
    <xs:enumeration value="400"/>
    <xs:enumeration value="500"/>
  </xs:restriction>
</xs:simpleType>
Complex Type ConductorSegmentType
Namespace http://www.iepmodel.net
Annotations
A specific portion of a circuit's wiring.  This element allows for definition of multiple segments of different wire types within a single CircuitConnectionConductor.
Diagram
Diagram CommonElectrical_xsd.tmp#ConductorSegmentType_id