-
Notifications
You must be signed in to change notification settings - Fork 4
Expand file tree
/
Copy pathCommonElectrical.xsd
More file actions
936 lines (935 loc) · 56.9 KB
/
CommonElectrical.xsd
File metadata and controls
936 lines (935 loc) · 56.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
<?xml version="1.0" encoding="UTF-8"?>
<!--**************************************************************************
schema: CommonElectrical.xsd v 2.0
Author(s):
v 2.0 Michael Palmquist, SolarNexus Inc
v 1.x Michael Palmquist, SolarNexus Inc
Description: Schema includes elements for defining an electrical system on a site. Includes elements that describe the distribution of circuits, such as electric panels, wiring, wireways (conduit), over-current protection devices (OCPD), and disconnects.
**************************************************************************** -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.iepmodel.net"
targetNamespace="http://www.iepmodel.net" version="1.0" elementFormDefault="qualified">
<xs:include schemaLocation="Common.xsd"/>
<xs:simpleType name="wireTypeEnum">
<xs:annotation>
<xs:documentation>Types of wire material, such as "stranded Cu," "solid Cu," "stranded Al," etc.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="STRANDED_CU"/>
<xs:enumeration value="SOLID_CU"/>
<xs:enumeration value="STRANDED_AL"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="wireGaugeEnum">
<xs:annotation>
<xs:documentation>Standard wire sizes in AWG or kcmil.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="14"/>
<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>
<xs:simpleType name="wireJacketTypeEnum">
<xs:annotation>
<xs:documentation>ISSUE: May need additional jacket types</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="BARE"/>
<xs:enumeration value="USE"/>
<xs:enumeration value="USE-2"/>
<xs:enumeration value="THWN"/>
<xs:enumeration value="THWN-2"/>
<xs:enumeration value="THHN"/>
<xs:enumeration value="THHW"/>
<xs:enumeration value="XHHW-2"/>
<xs:enumeration value="RHW-2"/>
<xs:enumeration value="PV_WIRE"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="conductorRoleEnum">
<xs:restriction base="xs:string">
<xs:enumeration value="LINE"/>
<xs:enumeration value="NEUTRAL"/>
<xs:enumeration value="POSITIVE"/>
<xs:enumeration value="NEGATIVE"/>
<xs:enumeration value="EGC"/>
<xs:enumeration value="GEC"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="conduitDiameterEnum">
<xs:annotation>
<xs:documentation>List of industry standard electrical conduit diameters in inches.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0.5"/>
<xs:enumeration value="0.75"/>
<xs:enumeration value="1"/>
<xs:enumeration value="1.25"/>
<xs:enumeration value="1.5"/>
<xs:enumeration value="2"/>
<xs:enumeration value="2.5"/>
<xs:enumeration value="3"/>
<xs:enumeration value="3.5"/>
<xs:enumeration value="4"/>
<xs:enumeration value="5"/>
<xs:enumeration value="6"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="conduitTypeEnum">
<xs:annotation>
<xs:documentation>Standard types of electrical conduit.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="EMT"/>
<xs:enumeration value="PVC"/>
<xs:enumeration value="PVC_40"/>
<xs:enumeration value="PVC_80"/>
<xs:enumeration value="RIGID"/>
<xs:enumeration value="FMC"/>
<xs:enumeration value="LFMC"/>
<xs:enumeration value="LFNC"/>
<xs:enumeration value="FREE_AIR"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="overCurrentProtectionDeviceEnum">
<xs:annotation>
<xs:documentation>Types of over current protection devices</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="CIRCUIT_BREAKER"/>
<xs:enumeration value="FUSE"/>
<xs:enumeration value="NONE"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="switchContactActionEnum">
<xs:annotation>
<xs:documentation>Variations of switch contact operation.
- SPST = single pole, single throw
- DPST = double pole, single throw
- 3PST = triple pole, single throw
- SPDT = single pole, double throw (aka "changover switch")</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="SPST"/>
<xs:enumeration value="DPST"/>
<xs:enumeration value="3PST"/>
<xs:enumeration value="SPDT"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="switchDutyEnum">
<xs:restriction base="xs:string">
<xs:enumeration value="GENERAL_DUTY"/>
<xs:enumeration value="HEAVY_DUTY"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="currentEnum">
<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>
<xs:simpleType name="serviceConfigurationVoltageEnum">
<xs:annotation>
<xs:documentation>Options for electrical service configuration and voltage.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="240_120_SPLIT_PHASE"/>
<xs:enumeration value="240_DELTA_3_PHASE"/>
<xs:enumeration value="240_SPLIT_PHASE_DELTA_3_PHASE"/>
<xs:enumeration value="208_DELTA_3_PHASE"/>
<xs:enumeration value="208_DELTA_120_WYE_3_PHASE"/>
<xs:enumeration value="480_DELTA_277_WYE_3_PHASE"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="sideOfPanelOcpdWhereConnectedEnum">
<xs:annotation>
<xs:documentation>When an interconnection is made on an electrical panel with a breaker separating the supply side and load side of the panel, these list the two sides.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="SUPPLY_SIDE"/>
<xs:enumeration value="LOAD_SIDE"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="distributionRoleEnum">
<xs:annotation>
<xs:documentation>Role that an electrical panel plays in the distribution system.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="MAIN_PANEL"/>
<xs:pattern value=""/>
<xs:enumeration value="SUB_PANEL"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="electricalPanelDefinition">
<xs:annotation>
<xs:documentation>A description of an electrical distribution device. Typically also known as "load centers" that house multiple circuit breakers. A switch can also be modeled.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="equipmentDefinition">
<xs:sequence>
<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>
<xs:element name="busbarFeedLocation" minOccurs="0">
<xs:annotation>
<xs:documentation>Describes the busbar point of connection. Busbars can be either top-, center-, or bottom-fed.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="TOP"/>
<xs:enumeration value="CENTER"/>
<xs:enumeration value="BOTTOM"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="electricalPanelDefinitions">
<xs:annotation>
<xs:documentation>A collection of the electrical panel equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="electricalPanelDefinition"
type="electricalPanelDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="electricalPanel">
<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="equipmentInstance">
<xs:sequence>
<xs:element minOccurs="0" name="distributionRole" type="distributionRoleEnum"/>
<xs:element minOccurs="0" name="serviceConfigurationVoltage"
type="serviceConfigurationVoltageEnum"/>
<xs:element minOccurs="0" name="energizingSourceCircuitConnectionIdRef"
type="xs:IDREF">
<xs:annotation>
<xs:documentation>Reference to the circuitConnection energizing the panel. The circuitConnection will reference the OCPD / disco at the energizing source's end.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="mainBreaker" type="circuitBreakerDefinition"
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="buildingIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>Optional reference to the building that this electrical panel services.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="includedMeterIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>If the panel is an "All in One", it has a meter socket. This element references 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="groundingElectrodeConductor">
<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:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="electricalPanels">
<xs:annotation>
<xs:documentation>A collection of the electrical panels in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="electricalPanel" type="electricalPanel"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="wirewaySegment" 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:element minOccurs="0" name="elevationAboveRoof" type="xs:double">
<xs:annotation>
<xs:documentation>If located on a rooftop, the segments elevation above the surface. This affects the temperature.</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>
<xs:complexType name="wirewayBox">
<xs:annotation>
<xs:documentation>A WirewayBox is an abstract way to describe instances of junction boxes and disconnect switches. What differentiates them from conduit segments is the ability for circuitConnections to start or end in them, as well as for multiple circuitConnections to exit from them. An electrical box through which CircuitConnections travel as a transition from one ConduitSegment to another. Wireway boxes cannot change the current or voltage characteristics of any CircuitConnections starting, ending, or passing through it. They may not combine or distribute current like a DcCombiner or electricalPanel. They may not change voltage characteristics such as a stringInverter. A wirewayBox may contain 1:1 wire splices or a disconnect switch (based on its instance type). Note that a WirewayBox may or may not refer to a defined piece of Equipment (e.g. a JunctionBoxDefintion, DisconnectSwitchDefinition, StandAloneMeterSocketDefintion). It may instead contain a free text name.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="wirewaySegment">
<xs:sequence>
<xs:element maxOccurs="1" minOccurs="0" name="circuitConnections">
<xs:annotation>
<xs:documentation>A wireway box may have multiple circuits entering it, therefore it must have multiple circuits leaving it as well. No combining of circuits occurs at wireway boxes. This is a collection of circuitConnections leaving the wirewayBox.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="circuitConnectionIdRef"
type="xs:IDREF"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="conduitSegments" minOccurs="0">
<xs:annotation>
<xs:documentation>A collection of the conduit segments connected to this box.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="conduitSegmentIdRef"
type="xs:IDREF" minOccurs="1">
<xs:annotation>
<xs:documentation>The ID Ref for a conduitSegment. Boxes can have many conduitSegment 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>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="junctionBoxDefinition">
<xs:annotation>
<xs:documentation>A definition for a piece of electrical equipment used to join pieces of conduit together or to act as a location for making splices. In the model, specific instances of junction boxes are modeled as WirewayBoxes. Note that a JunctionBox may not combine any circuits, a separate DcCombiner element is defined for that purpose in PvSystems.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="equipmentDefinition"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="junctionBoxDefinitions">
<xs:annotation>
<xs:documentation>A collection of the junction box equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="junctionBoxDefinition"
type="junctionBoxDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="junctionBox">
<xs:annotation>
<xs:documentation>A junctionBox is used to splice different circuitConnections together, as in the case of string wiring transitioning from free air to wire in conduit. circuitConnections may also pass through a junction box like it is a conduit segment. A junctionBox cannot change the current or voltage characteristics of any circuits. They may not combine or distribute current like a DcCombiner or ElectricalPanel. They may not change voltage characteristics such as a StringInverter. Note that a juntionBox may or may not refer to a defined piece of Equipment (e.g. a JunctionBoxDefintion, DisconnectSwitchDefinition, StandAloneMeterSocketDefintion). It may instead contain a free text name.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="wirewayBox"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="junctionBoxes">
<xs:annotation>
<xs:documentation>A collection of the junction boxes in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="junctionBox" type="junctionBox">
<xs:annotation>
<xs:documentation>A junction box used in this design. circuitConnections may start/end at a junctionBox, or they may pass through. Multiple circuitConnections may pass through a junctionBox.
Note that if the pvSystem is used in an IEPM Project file, the junctionBox does not reference any existingWirewaySegments or ProposedWirewaySegments defined in the Site element. Those elements are used for site survey data collection, not system definition.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="disconnectSwitchDefinition">
<xs:annotation>
<xs:documentation>A definition for a piece of equipment that can disconnect a CircuitConnection. In the model, specific instances of Disconnect switches are modeled as WirewayBoxes.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="equipmentDefinition">
<xs:sequence>
<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>
<xs:element minOccurs="0" name="acVoltageRating" type="xs:integer"/>
<xs:element minOccurs="0" name="dcVoltageRating" type="xs:integer"/>
<xs:element name="switchContact" minOccurs="0" type="switchContactActionEnum">
<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>
<xs:element minOccurs="0" name="duty" type="switchDutyEnum"/>
<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>
<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>
<xs:element minOccurs="0" name="fuse" type="fuseDefinition">
<xs:annotation>
<xs:documentation>If the switch includes fuses, this describes the fuses.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="disconnectSwitchDefinitions">
<xs:annotation>
<xs:documentation>A collection of the disconnect switch equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="disconnectSwitchDefinition"
type="disconnectSwitchDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="disconnectSwitch">
<xs:annotation>
<xs:documentation>A disconnectBox can provide a break between circuitConnections via its disconnect switch. Disconnect boxes cannot change the current or voltage characteristics of any circuits. circuitConnections may start/end at a disconnect box, where circuit conductors are switched. circuitConnections may also pass through a disconnect box like it is a conduit segment. A disconnectBox may not combine or distribute current like a DcCombiner or ElectricalPanel. They may not change voltage characteristics such as a StringInverter. Note that a disconnectBox may or may not refer to a defined piece of Equipment (e.g. a JunctionBoxDefintion, DisconnectSwitchDefinition, StandAloneMeterSocketDefintion). It may instead contain a free text name.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="wirewayBox"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="disconnectSwitches">
<xs:annotation>
<xs:documentation>A collection of the disconnect boxes in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="disconnectSwitch" type="disconnectSwitch">
<xs:annotation>
<xs:documentation>A standalone disconnect box used in the design. circuitConnections may start/end at the disconnect switch, or they may pass through.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="meterDefinition">
<xs:annotation>
<xs:documentation>A device that records the quantity of energy units consumed by the customer.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="equipmentDefinition">
<xs:sequence>
<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>
<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>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="meterDefinitions">
<xs:annotation>
<xs:documentation>A collection of the meter equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element form="unqualified" maxOccurs="unbounded" name="meterDefinition"
type="meterDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="meter">
<xs:complexContent>
<xs:extension base="equipmentInstance"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="meters">
<xs:annotation>
<xs:documentation>A collection of the meters in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="meters" type="meter">
<xs:annotation>
<xs:documentation>A electrical measurement meter.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="meterBoxDefintion">
<xs:annotation>
<xs:documentation>A stand alone meter box.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="equipmentDefinition"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="meterBoxDefinitions">
<xs:annotation>
<xs:documentation>A collection of the stand alone meter box equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="meterBoxDefinition" type="meterBoxDefintion"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="meterBox">
<xs:annotation>
<xs:documentation>An instance of a stand alone meter box. Note that "all in one" electrical panels that incorporate meters are NOT considered meter boxes.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="wirewayBox"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="meterBoxes">
<xs:annotation>
<xs:documentation>A collection of the stand alone meter boxes in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="meterBox" type="meterBox"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="overCurrentProtectionDevice" abstract="true">
<xs:annotation>
<xs:documentation>Over current protection device (commonly called "OCPD"). Fuses and circuit breakers are OCPDs.
Note that this type does not extend EquipmentDefinition nor EquipmentInstance. It 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; knowing the type and rating is required.</xs:documentation>
</xs:annotation>
<xs:sequence>
<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>
<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>
<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>
<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>
<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>
</xs:sequence>
<xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
<xs:complexType name="circuitBreakerDefinition">
<xs:annotation>
<xs:documentation>A circuit breaker is a re-usable OCPD which can also act as a disconnecting means.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="overCurrentProtectionDevice">
<xs:sequence>
<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>
<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>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="circuitBreakerDefinitions">
<xs:annotation>
<xs:documentation>A collection of the circuit breaker equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="circuitBreakerDefinition"
type="circuitBreakerDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="circuitBreaker">
<xs:complexContent>
<xs:extension base="equipmentInstance">
<xs:sequence>
<xs:element minOccurs="0" name="equipmentWhereHousedIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>The equipment instance where this circuit breaker is located. Refers to the equipment instance's ID within the XML instance document.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="circuitBreakers">
<xs:annotation>
<xs:documentation>A collection of the circuit breakers in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="circuitBreaker" type="circuitBreaker"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="fuseDefinition">
<xs:annotation>
<xs:documentation>A fuse is a disposable, one time use OCPD lacking any disconnect means.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="overCurrentProtectionDevice">
<xs:sequence>
<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>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="fuseDefinitions">
<xs:annotation>
<xs:documentation>A collection of the fuse equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="fuseDefinition" type="fuseDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="fuse">
<xs:complexContent>
<xs:extension base="equipmentInstance">
<xs:sequence>
<xs:element minOccurs="0" name="equipmentWhereHousedIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>The equipment instance where this fuse is located. Refers to the equipment instance's ID within the XML instance document.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="fuses">
<xs:annotation>
<xs:documentation>A collection of the fuses in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="fuse" type="fuse"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="conduitDefinition">
<xs:sequence>
<xs:element name="type" type="conduitTypeEnum" minOccurs="0" maxOccurs="1"/>
<xs:element name="diameter" type="conduitDiameterEnum" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
<xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
<xs:complexType name="conduitDefinitions">
<xs:annotation>
<xs:documentation>A collection of the conduit equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="conduitDefinition" type="conduitDefinition"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="conduitSegment">
<xs:annotation>
<xs:documentation>A ConduitSegment is any continuous section of electrical conduit of a consistent type.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="wirewaySegment">
<xs:sequence>
<xs:element name="length" 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>
<xs:element minOccurs="0" name="segmentConnections">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="2" name="segmentConnectionIdRef"
type="xs:IDREF" minOccurs="2">
<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>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="conduitSegments">
<xs:annotation>
<xs:documentation>A collection of the conduit segments in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="conduitSegment" type="conduitSegment"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="conductorDefinition">
<xs:annotation>
<xs:documentation>Specifications of a single type of conductor.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" name="wireType" type="wireTypeEnum">
<xs:annotation>
<xs:documentation>Types of conductor material, such as "stranded Cu," "solid Cu," "stranded Al," etc.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="1" name="jacketType" type="wireJacketTypeEnum">
<xs:annotation>
<xs:documentation>Type of jacketing on the conductor.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="wireGauge" type="wireGaugeEnum">
<xs:annotation>
<xs:documentation>Wire diameter, given in American Wire Gauge (AWG), or kcmil.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="id" use="required" type="xs:ID"/>
</xs:complexType>
<xs:complexType name="conductorDefinitions">
<xs:annotation>
<xs:documentation>A collection of the conductor equipment definitions in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="conductorDefinition" type="conductorDefinition"
/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="conductor">
<xs:annotation>
<xs:documentation>A single conductor instance in a circuit.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" name="role" type="conductorRoleEnum">
<xs:annotation>
<xs:documentation>Identifier of this conductor's role in the circuit.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="jacketColor" type="xs:string"/>
<xs:element minOccurs="0" name="grounded" type="xs:boolean">
<xs:annotation>
<xs:documentation>Is this conductor grounded?</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="ocpdIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>If this conductor protected by an overcurrent protection device (OCPD) such as a fuse or circuit breaker, this provides the reference to the OCPD instance in the XML document.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="id" use="required" type="xs:ID"/>
<xs:attribute name="conductorDefinitionIdRef" type="xs:IDREF" use="optional">
<xs:annotation>
<xs:documentation>Reference to the conductor specifications.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="cable">
<xs:sequence>
<xs:element name="cableName"/>
<xs:element name="conductors"/>
</xs:sequence>
</xs:complexType>
<xs:complexType abstract="false" name="groundingElectrodeConductor">
<xs:annotation>
<xs:documentation>The conductor that serves as the main ground path for either an AC or DC system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="conductor" type="conductor"/>
<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>
</xs:sequence>
</xs:complexType>
<xs:complexType name="circuitConnection">
<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 default="1" minOccurs="0" name="instances" type="xs:integer">
<xs:annotation>
<xs:documentation>A single circuitConnection element may be used to represent a set of multiple identical circuit connection instances. For example, from a dcStringSet element.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="currentType" minOccurs="0" type="currentEnum">
<xs:annotation>
<xs:documentation>AC or DC</xs:documentation>
</xs:annotation>
</xs:element>
<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>
<xs:element minOccurs="0" name="conductors">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="conductor" type="conductor"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="maximumWireTemperature"/>
<xs:element default="LOAD_SIDE" minOccurs="0" name="sideOfPanelOcpdWhereConnected"
type="sideOfPanelOcpdWhereConnectedEnum">
<xs:annotation>
<xs:documentation>When a circuit connection's targetComponent is an ElectricalPanel, this describes which side of a the panel's main breaker (if present) that the interconnection is 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="wirewaySegments">
<xs:annotation>
<xs:documentation>The collection of 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:complexType>
<xs:sequence>
<xs:element name="wirewaySegmentIdRef" type="xs:IDREF" minOccurs="1"
maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>A single wireway segment through which this circuit connection runs. A wireway segment may be a conduit segment or a wireway box. Note that the circuitConnection can also 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:complexType>
</xs:element>
<xs:element minOccurs="0" name="includedDisconnect" type="xs:IDREF">
<xs:annotation>
<xs:documentation>If the CircuitConnection has a disconnect switch in it, this calls it out.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="includedStandAloneMeter" type="xs:IDREF">
<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:element>
<xs:element minOccurs="0" name="sourceComponentIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>The component (an equipmentInstance) where this circuitConnection originates. Refers to the ID of that equipmentInstance within the XML document instance.
Circuit connections have two ends. One is the equipment defined by this ID, the other is defined by the targetComponentIdRef.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="targetComponentIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>The component (an equipmentInstance) where this circuitConnection terminates. Refers to the ID of that equipmentInstance within the XML document instance.
Circuit connections have two ends. One is defined by the sourceComponentIdRef, the other is the equipment defined by this ID.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="continuingCircuitIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>If the circuit connection terminates within a Junction box or Disconnect, and then transitions to another circuitConnection, this identifies the circuitConnection where it continues.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
<xs:complexType name="circuitConnections">
<xs:annotation>
<xs:documentation>A collection of the circuitConnections in the associated system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="circuitConnection" type="circuitConnection"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="electricDistributionSystem">
<xs:annotation>
<xs:documentation>Definition of a physical electric service distribution system.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" name="utilityServiceIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>Reference to a defined utilityService element.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="junctionBoxDefinitions" type="junctionBoxDefinitions"/>
<xs:element minOccurs="0" name="disconnectSwitchDefinitions"
type="disconnectSwitchDefinitions"/>
<xs:element minOccurs="0" name="meterDefinitions" type="meterDefinitions"/>
<xs:element minOccurs="0" name="meterBoxDefinitions" type="meterBoxDefinitions"/>
<xs:element minOccurs="0" name="electricalPanelDefinitions"
type="electricalPanelDefinitions"/>
<xs:element minOccurs="0" name="circuitBreakerDefinitions"
type="circuitBreakerDefinitions"/>
<xs:element minOccurs="0" name="fuseDefinitions" type="fuseDefinitions"/>
<xs:element minOccurs="0" name="conductorDefinitions" type="conductorDefinitions"/>
<xs:element minOccurs="0" name="conduitDefinitions" type="conduitDefinitions"/>
<xs:element minOccurs="1" name="electricServiceEntryEquipmentIdRef" type="xs:IDREF">
<xs:annotation>
<xs:documentation>The initial component in the electric distribution system where the electric service enters. This is the start of the distribution tree.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="junctionBoxes" type="junctionBoxes"/>
<xs:element minOccurs="0" name="disconnectSwitches" type="disconnectSwitches"> </xs:element>
<xs:element minOccurs="0" name="meterBoxes" type="meterBoxes"> </xs:element>
<xs:element minOccurs="0" name="meters" type="meters"/>
<xs:element minOccurs="0" name="electricalPanels" type="electricalPanels"> </xs:element>
<xs:element minOccurs="0" name="circuitBreakers" type="circuitBreakers"> </xs:element>
<xs:element minOccurs="0" name="fuses" type="fuses"> </xs:element>
<xs:element minOccurs="0" name="circuitConnections" type="circuitConnections"> </xs:element>
<xs:element minOccurs="0" name="conduitSegments" type="conduitSegments"> </xs:element>
</xs:sequence>
<xs:attribute name="id" use="required"/>
</xs:complexType>
</xs:schema>