Showing:

Annotations
Attributes
Diagrams
Instances
Properties
Source
Used by
Included schema DistributionSystem.xsd
Namespace http://www.iepmodel.net
Properties
attribute form default: unqualified
element form default: unqualified
Element DistributionSystemType / Name
Namespace No namespace
Annotations
This is simply a descriptive name, typically a common name used for the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSystemType / Description
Namespace No namespace
Annotations
Place for user to include additional notes/description of the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Place for user to include additional notes/description of the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSystemType / FluidTransported
Namespace No namespace
Annotations
The fluid transported by the distribution system. It may be useful to also indicate the specific gravity of the fluid if it is not a common one.

Examples:
Air
Water
Glycol
Oil, specific gravity = 0.8
Heat Transfer Fluid
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="FluidTransported" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The fluid transported by the distribution system. It may be useful to also indicate the specific gravity of the fluid if it is not a common one. Examples: Air Water Glycol Oil, specific gravity = 0.8 Heat Transfer Fluid</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSystemType / DistributionEquipmentDefinition
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
Type EquipmentDefinitionType
Properties
content: complex
minOccurs: 0
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}
Children Depth, Description, EnclosureMaterial, EnclosureNemaRating, EnergyStarRated, Length, ListingAgency, Manufacturer, ModelNumber, MountingStyle, ProductFamilyName, Warranty, Weight, WhereManufactured, Width
Instance
<DistributionEquipmentDefinition 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>
</DistributionEquipmentDefinition>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID required
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="DistributionEquipmentDefinition" type="EquipmentDefinitionType"/>
Element DistributionSystemType / PrimeMover
Namespace No namespace
Annotations
Any pump or fan that drives the fluid - causes it to flow.
Diagram
Diagram DistributionSystem_xsd.tmp#PrimeMoverSystemType_id DistributionSystem_xsd.tmp#PrimeMoverSystemType_Name DistributionSystem_xsd.tmp#PrimeMoverSystemType_Description DistributionSystem_xsd.tmp#PrimeMoverSystemType_DesignFlow DistributionSystem_xsd.tmp#PrimeMoverSystemType_DesignPressure DistributionSystem_xsd.tmp#PrimeMoverSystemType_DeviceTechnology DistributionSystem_xsd.tmp#PrimeMoverSystemType_FlowControl DistributionSystem_xsd.tmp#PrimeMoverSystemType_SystemProperties DistributionSystem_xsd.tmp#PrimeMoverSystemType_PrimeMoverEquipment DistributionSystem_xsd.tmp#PrimeMoverSystemType_Quantity DistributionSystem_xsd.tmp#PrimeMoverSystemType
Type PrimeMoverSystemType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Name{0,1} , Description{0,1} , DesignFlow{0,1} , DesignPressure{0,1} , DeviceTechnology* , FlowControl* , SystemProperties{0,1} , PrimeMoverEquipment* , Quantity{0,1}
Children Description, DesignFlow, DesignPressure, DeviceTechnology, FlowControl, Name, PrimeMoverEquipment, Quantity, SystemProperties
Instance
<PrimeMover id="">
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <DesignFlow Unit="">{0,1}</DesignFlow>
  <DesignPressure Unit="">{0,1}</DesignPressure>
  <DeviceTechnology>{0,unbounded}</DeviceTechnology>
  <FlowControl>{0,unbounded}</FlowControl>
  <SystemProperties>{0,1}</SystemProperties>
  <PrimeMoverEquipment EquipmentDefinitionIdRef="" id="">{0,unbounded}</PrimeMoverEquipment>
  <Quantity>{0,1}</Quantity>
</PrimeMover>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:element name="PrimeMover" type="PrimeMoverSystemType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Any pump or fan that drives the fluid - causes it to flow.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / Name
Namespace No namespace
Annotations
This is simply a descriptive name, typically a common name used for the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / Description
Namespace No namespace
Annotations
Place for user to include additional notes/description of the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Place for user to include additional notes/description of the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / DesignFlow
Namespace No namespace
Annotations
The volumetric flow that the pump/fan was designed to provide. This correspondes to the Design Pressure.  

Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve. Typically, this is not the maximum flow that the device can provide.
Diagram
Diagram Common_xsd.tmp#FlowType_Unit Common_xsd.tmp#FlowType
Type FlowType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Unit FlowUnitEnumType optional
Unit of measurement.
Source
<xs:element name="DesignFlow" type="FlowType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The volumetric flow that the pump/fan was designed to provide. This correspondes to the Design Pressure. Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve. Typically, this is not the maximum flow that the device can provide.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / DesignPressure
Namespace No namespace
Annotations
The pressure across the pump/fan (P_outlet - P_inlet) that it was designed to provide. This corresponds to the the Design Flow.  

Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve.  Typically, this is not the maximum pressure across the device.
Diagram
Diagram Common_xsd.tmp#PressureType_Unit Common_xsd.tmp#PressureType
Type PressureType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Unit PressureUnitEnumType optional
Unit of measurement.
Source
<xs:element name="DesignPressure" type="PressureType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The pressure across the pump/fan (P_outlet - P_inlet) that it was designed to provide. This corresponds to the the Design Flow. Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve. Typically, this is not the maximum pressure across the device.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / DeviceTechnology
Namespace No namespace
Annotations
The type of pump/fan device. This typically indicates the blade/impeller type.

Examples:
Centrifugal, Forward Curved
Centrifugal, Backward Curved
Centrifugal, Radial Blade
Centrifugal, Airfoil
Centrifugal, Plenum
Axial, Propeller
Axial, Turbine
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element name="DeviceTechnology" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The type of pump/fan device. This typically indicates the blade/impeller type. Examples: Centrifugal, Forward Curved Centrifugal, Backward Curved Centrifugal, Radial Blade Centrifugal, Airfoil Centrifugal, Plenum Axial, Propeller Axial, Turbine</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / FlowControl
Namespace No namespace
Annotations
The method used to control the flow rate through the pump/fan. Note that there may be more than one, since it is not uncommon (though somewhat inefficient) to find a VFD and throttle used.

Examples:
Valve-Manual/Automatic
Damper-Manual/Automatic
Variable Speed 
Variable Pitch Blade
Inlet Guide Vane
Outlet Damper
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element name="FlowControl" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The method used to control the flow rate through the pump/fan. Note that there may be more than one, since it is not uncommon (though somewhat inefficient) to find a VFD and throttle used. Examples: Valve-Manual/Automatic Damper-Manual/Automatic Variable Speed Variable Pitch Blade Inlet Guide Vane Outlet Damper</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / SystemProperties
Namespace No namespace
Annotations
Characteristics of the system are captured here.  Note that this reflects the system (pump/fan, motor, VFD, etc.).  Properties of the individual components may be captured in equipment attributes.
Diagram
Diagram CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_Description CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_AnnualOperatingHours CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_DesignEfficiency CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_DesignInput CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_DesignOutput CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_EnergyConsumption CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_MaxInput CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_OperatingSchedule CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_RefZoneLocationID CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType_RefRevenueMeterID CommonSystemProperties_xsd.tmp#CommonSystemPropertiesType
Type CommonSystemPropertiesType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model Description{0,1} , AnnualOperatingHours{0,1} , DesignEfficiency{0,1} , DesignInput{0,1} , DesignOutput{0,1} , EnergyConsumption{0,1} , MaxInput{0,1} , OperatingSchedule* , RefZoneLocationID{0,1} , RefRevenueMeterID{0,1}
Children AnnualOperatingHours, Description, DesignEfficiency, DesignInput, DesignOutput, EnergyConsumption, MaxInput, OperatingSchedule, RefRevenueMeterID, RefZoneLocationID
Instance
<SystemProperties>
  <Description>{0,1}</Description>
  <AnnualOperatingHours>{0,1}</AnnualOperatingHours>
  <DesignEfficiency TestCondition="" Unit="" UnitDesc="">{0,1}</DesignEfficiency>
  <DesignInput Fuel="Electricity" FuelDesc="Electricity" TestCondition="" Unit="" UnitDesc="kwh">{0,1}</DesignInput>
  <DesignOutput Fuel="Electricity" FuelDesc="Electricity" TestCondition="" Unit="" UnitDesc="kwh">{0,1}</DesignOutput>
  <EnergyConsumption RevenueMeterIdRef="">{0,1}</EnergyConsumption>
  <MaxInput Fuel="Electricity" FuelDesc="Electricity" TestCondition="" Unit="" UnitDesc="kwh">{0,1}</MaxInput>
  <OperatingSchedule>{0,unbounded}</OperatingSchedule>
  <RefZoneLocationID>{0,1}</RefZoneLocationID>
  <RefRevenueMeterID>{0,1}</RefRevenueMeterID>
</SystemProperties>
Source
<xs:element name="SystemProperties" type="CommonSystemPropertiesType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Characteristics of the system are captured here. Note that this reflects the system (pump/fan, motor, VFD, etc.). Properties of the individual components may be captured in equipment attributes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / PrimeMoverEquipment
Namespace No namespace
Annotations
Details of the hardware are captured here.
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
maxOccurs: unbounded
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
<PrimeMoverEquipment 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>
</PrimeMoverEquipment>
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="PrimeMoverEquipment" type="EquipmentInstanceType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Details of the hardware are captured here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PrimeMoverSystemType / Quantity
Namespace No namespace
Annotations
The quantity of these systems (fans/pumps) existing and operating.
Diagram
Diagram
Type xs:int
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Quantity" type="xs:int" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The quantity of these systems (fans/pumps) existing and operating.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSystemType / Segment
Namespace No namespace
Annotations
A segment of the vessel (pipe, duct, etc.) that contains and transports the fluid.
Diagram
Diagram DistributionSystem_xsd.tmp#DistributionSegmentType_id DistributionSystem_xsd.tmp#DistributionSegmentType_Name DistributionSystem_xsd.tmp#DistributionSegmentType_Description DistributionSystem_xsd.tmp#DistributionSegmentType_SegmentEquipment DistributionSystem_xsd.tmp#DistributionSegmentType_Insulation DistributionSystem_xsd.tmp#DistributionSegmentType_Leakage DistributionSystem_xsd.tmp#DistributionSegmentType_PressureRated DistributionSystem_xsd.tmp#DistributionSegmentType_FlowRated DistributionSystem_xsd.tmp#DistributionSegmentType_FlowControl DistributionSystem_xsd.tmp#DistributionSegmentType_RefZoneLocationID DistributionSystem_xsd.tmp#DistributionSegmentType
Type DistributionSegmentType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Name{0,1} , Description{0,1} , SegmentEquipment* , Insulation* , Leakage{0,1} , PressureRated{0,1} , FlowRated{0,1} , FlowControl* , RefZoneLocationID{0,1}
Children Description, FlowControl, FlowRated, Insulation, Leakage, Name, PressureRated, RefZoneLocationID, SegmentEquipment
Instance
<Segment id="">
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <SegmentEquipment EquipmentDefinitionIdRef="" id="">{0,unbounded}</SegmentEquipment>
  <Insulation>{0,unbounded}</Insulation>
  <Leakage>{0,1}</Leakage>
  <PressureRated Unit="">{0,1}</PressureRated>
  <FlowRated Unit="">{0,1}</FlowRated>
  <FlowControl>{0,unbounded}</FlowControl>
  <RefZoneLocationID>{0,1}</RefZoneLocationID>
</Segment>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Segment" type="DistributionSegmentType">
  <xs:annotation>
    <xs:documentation>A segment of the vessel (pipe, duct, etc.) that contains and transports the fluid.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / Name
Namespace No namespace
Annotations
This is simply a descriptive name, typically a common name used for the system.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / Description
Namespace No namespace
Annotations
Place for user to include additional notes and description of this segment.

If a complex system of segments is to be defined, it would be useful to describe the system here.

Other quantities or features may also be described here, such as the loss coefficient (i.e. pressure drop due to fluid friction).
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Place for user to include additional notes and description of this segment. If a complex system of segments is to be defined, it would be useful to describe the system here. Other quantities or features may also be described here, such as the loss coefficient (i.e. pressure drop due to fluid friction).</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / SegmentEquipment
Namespace No namespace
Annotations
Characteristics of the segment (pipe/duct/etc.) hardware are captured here.
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
maxOccurs: unbounded
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
<SegmentEquipment 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>
</SegmentEquipment>
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="SegmentEquipment" type="EquipmentInstanceType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Characteristics of the segment (pipe/duct/etc.) hardware are captured here.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / Insulation
Namespace No namespace
Diagram
Diagram Building_xsd.tmp#InsulationType_Description Building_xsd.tmp#InsulationType_R-Value Building_xsd.tmp#InsulationType_Emissivity Building_xsd.tmp#InsulationType_CoverageFraction Building_xsd.tmp#InsulationType
Type InsulationType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Description{0,1} , R-Value{0,1} , Emissivity{0,1} , CoverageFraction{0,1}
Children CoverageFraction, Description, Emissivity, R-Value
Instance
<Insulation>
  <Description>{0,1}</Description>
  <R-Value>{0,1}</R-Value>
  <Emissivity>{0,1}</Emissivity>
  <CoverageFraction>{0,1}</CoverageFraction>
</Insulation>
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Insulation" type="InsulationType"/>
Element DistributionSegmentType / Leakage
Namespace No namespace
Diagram
Diagram Building_xsd.tmp#LeakageType_Name Building_xsd.tmp#LeakageType_Description Building_xsd.tmp#LeakageType_TestFlow Building_xsd.tmp#LeakageType_TestPressure Building_xsd.tmp#LeakageType_LeakageFlow Building_xsd.tmp#LeakageType_LeakageArea Building_xsd.tmp#LeakageType
Type LeakageType
Properties
content: complex
minOccurs: 0
Model Name{0,1} , Description{0,1} , TestFlow{0,1} , TestPressure{0,1} , LeakageFlow{0,1} , LeakageArea{0,1}
Children Description, LeakageArea, LeakageFlow, Name, TestFlow, TestPressure
Instance
<Leakage>
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <TestFlow Unit="">{0,1}</TestFlow>
  <TestPressure Unit="">{0,1}</TestPressure>
  <LeakageFlow Unit="">{0,1}</LeakageFlow>
  <LeakageArea Unit="SquareMeters">{0,1}</LeakageArea>
</Leakage>
Source
<xs:element minOccurs="0" name="Leakage" type="LeakageType"/>
Element DistributionSegmentType / PressureRated
Namespace No namespace
Annotations
The maximum or design pressure for which the pipe/duct segment is rated.
Diagram
Diagram Common_xsd.tmp#PressureType_Unit Common_xsd.tmp#PressureType
Type PressureType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Unit PressureUnitEnumType optional
Unit of measurement.
Source
<xs:element name="PressureRated" type="PressureType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The maximum or design pressure for which the pipe/duct segment is rated.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / FlowRated
Namespace No namespace
Annotations
The maximum or design flow rate for which the pipe/duct segment is rated.
Diagram
Diagram Common_xsd.tmp#FlowType_Unit Common_xsd.tmp#FlowType
Type FlowType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Unit FlowUnitEnumType optional
Unit of measurement.
Source
<xs:element name="FlowRated" type="FlowType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The maximum or design flow rate for which the pipe/duct segment is rated.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / FlowControl
Namespace No namespace
Annotations
Describe a flow control device here:
Valve - Manual
Valve - Automatic
Damper - Manual
Damper - Automatic
Turning Vanes, loss coefficient 0.24
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="FlowControl" type="xs:string">
  <xs:annotation>
    <xs:documentation>Describe a flow control device here: Valve - Manual Valve - Automatic Damper - Manual Damper - Automatic Turning Vanes, loss coefficient 0.24</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSegmentType / RefZoneLocationID
Namespace No namespace
Annotations
This is the zone where the segment is located. This is for the purpose of capturing the heat lost to or absorbed from the environment by the fluid in the segment.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element maxOccurs="1" minOccurs="0" name="RefZoneLocationID" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This is the zone where the segment is located. This is for the purpose of capturing the heat lost to or absorbed from the environment by the fluid in the segment.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DistributionSystem
Namespace http://www.iepmodel.net
Annotations
A Distribution System describes the mechanical systems and equipment that transport air, water or another fluid. It consists of two components: Prime Mover (pump or fan) and Segment.

A Distribution System (optionally) consists of one or many Prime Movers, which is a pump or fan that causes the fluid to flow.  The Prime Mover has System and Equipment properties.

A Distribution System (optionally) consists of one or many Segments, which is a duct or pipe that transports the fluid.  The Segment has Equipment properties in addition to leakage and insulation properties (referenced from the Building schema).

The Distribution Systems was chosen to stand alone because of how the other systems interact with it and because on distribution system may serve multiple purposes.  It is be referenced by other systems such as an HVAC or WaterHeating system that interact with it.

A Distribution System (particularly air or water) may be referenced by an HVAC system in one of three ways.  A Distribution System may be referenced as the method of delivery of conditioning from the HVAC system (i.e. the ducting or piping that delivers conditioning).  Alternatively, a Distribution System may be referenced as the source of heat or cold (fluid to reject heat to) for a Heating or Cooling system, respectively.

Note that the Distribution System itself does not instance System Properties.  A distribution system can only consume energy through its prime mover and thermal transfer. The Prime Mover object instances System Properties. Thermal transfer to or from the fluid through its segments will affect the system(s) that are connected to (reference) it (such as a Hot Water Heating or HVAC system).  Thus, the thermal energy transferred through the segment surface should be captured by the zone in which the segment is located and the systems that reference it.

Example 1. A water DistributionSystem may serve both space heating as well as domestic hot water for kitchen and bathroom fixtures (i.e. dishwasher, shower). Systems that may reference this DistributionSystem include: a WaterHeating system, a grey-water HeatRecovery system and an HVACSystem.

Example 2
An air DistributionSystem may consist of supply and return ducting and a supply fan.  An HVACSystem such as a furnace or air-source heat-pump would reference the DistributionSystem (through its DeliveryMethod element).  

Example 3
A Whole house fan would be modeled as an HVAC system with a DeliveryMethod that references a Distribution System.  The Distribution System may include segments (inlet and exhaust ducting) and a fan (Prime Mover). The Ventilation properties in HVAC would further describe the rate of air exchange with outside.  The zone(s) referencing the HVAC system would specify the temperature setpoint schedule and any additional thermal loads.  

Alternatively, if the fan is controlled by a time schedule, rather than temperature schedule, the schedule may defined in the Prime Mover system properties.  Then, no HVAC system needs to be defined.

Example 4
A bathroom or kitchen exhaust fan may be modeled as a Distribution System with just a Prime Mover (segments optional).  The schedule in the System Properties of the Primer Mover may define the operating schedule of the fan.
Diagram
Diagram DistributionSystem_xsd.tmp#DistributionSystemType_id DistributionSystem_xsd.tmp#DistributionSystemType_Name DistributionSystem_xsd.tmp#DistributionSystemType_Description DistributionSystem_xsd.tmp#DistributionSystemType_FluidTransported DistributionSystem_xsd.tmp#DistributionSystemType_DistributionEquipmentDefinition DistributionSystem_xsd.tmp#DistributionSystemType_PrimeMover DistributionSystem_xsd.tmp#DistributionSystemType_Segment DistributionSystem_xsd.tmp#DistributionSystemType
Type DistributionSystemType
Properties
content: complex
Model Name{0,1} , Description{0,1} , FluidTransported{0,1} , DistributionEquipmentDefinition* , PrimeMover* , Segment*
Children Description, DistributionEquipmentDefinition, FluidTransported, Name, PrimeMover, Segment
Instance
<DistributionSystem id="" xmlns="http://www.iepmodel.net">
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <FluidTransported>{0,1}</FluidTransported>
  <DistributionEquipmentDefinition id="">{0,unbounded}</DistributionEquipmentDefinition>
  <PrimeMover id="">{0,unbounded}</PrimeMover>
  <Segment id="">{0,unbounded}</Segment>
</DistributionSystem>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:element name="DistributionSystem" type="DistributionSystemType">
  <xs:annotation>
    <xs:documentation>A Distribution System describes the mechanical systems and equipment that transport air, water or another fluid. It consists of two components: Prime Mover (pump or fan) and Segment. A Distribution System (optionally) consists of one or many Prime Movers, which is a pump or fan that causes the fluid to flow. The Prime Mover has System and Equipment properties. A Distribution System (optionally) consists of one or many Segments, which is a duct or pipe that transports the fluid. The Segment has Equipment properties in addition to leakage and insulation properties (referenced from the Building schema). The Distribution Systems was chosen to stand alone because of how the other systems interact with it and because on distribution system may serve multiple purposes. It is be referenced by other systems such as an HVAC or WaterHeating system that interact with it. A Distribution System (particularly air or water) may be referenced by an HVAC system in one of three ways. A Distribution System may be referenced as the method of delivery of conditioning from the HVAC system (i.e. the ducting or piping that delivers conditioning). Alternatively, a Distribution System may be referenced as the source of heat or cold (fluid to reject heat to) for a Heating or Cooling system, respectively. Note that the Distribution System itself does not instance System Properties. A distribution system can only consume energy through its prime mover and thermal transfer. The Prime Mover object instances System Properties. Thermal transfer to or from the fluid through its segments will affect the system(s) that are connected to (reference) it (such as a Hot Water Heating or HVAC system). Thus, the thermal energy transferred through the segment surface should be captured by the zone in which the segment is located and the systems that reference it. Example 1. A water DistributionSystem may serve both space heating as well as domestic hot water for kitchen and bathroom fixtures (i.e. dishwasher, shower). Systems that may reference this DistributionSystem include: a WaterHeating system, a grey-water HeatRecovery system and an HVACSystem. Example 2 An air DistributionSystem may consist of supply and return ducting and a supply fan. An HVACSystem such as a furnace or air-source heat-pump would reference the DistributionSystem (through its DeliveryMethod element). Example 3 A Whole house fan would be modeled as an HVAC system with a DeliveryMethod that references a Distribution System. The Distribution System may include segments (inlet and exhaust ducting) and a fan (Prime Mover). The Ventilation properties in HVAC would further describe the rate of air exchange with outside. The zone(s) referencing the HVAC system would specify the temperature setpoint schedule and any additional thermal loads. Alternatively, if the fan is controlled by a time schedule, rather than temperature schedule, the schedule may defined in the Prime Mover system properties. Then, no HVAC system needs to be defined. Example 4 A bathroom or kitchen exhaust fan may be modeled as a Distribution System with just a Prime Mover (segments optional). The schedule in the System Properties of the Primer Mover may define the operating schedule of the fan.</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type DistributionSystemType
Namespace http://www.iepmodel.net
Annotations
A Distribution System describes the mechanical systems and equipment that transport air, water or another fluid. It consists of two components: Prime Mover (pump or fan) and Segment.

A Distribution System (optionally) consists of one or many Prime Movers, which are pumps or fans that causes the fluid to flow.  The Prime Mover has System and Equipment properties.

A Distribution System (optionally) consists of one or many Segments, which is a duct or pipe that transports the fluid.  The Segment has Equipment properties in addition to leakage and insulation properties (referenced from the Building schema).

The Distribution Systems was chosen to stand alone because of how the other systems interact with it and because one distribution system may serve multiple purposes.  It is be referenced by other systems such as an HVAC or WaterHeating system that interact with it.

A Distribution System (particularly air or water) may be referenced by an HVAC system in one of three ways.  A Distribution System may be referenced as the method of delivery of conditioning from the HVAC system (i.e. the ducting or piping that delivers conditioning).  Alternatively, a Distribution System may be referenced as the source of heat or cold (fluid to reject heat to) for a Heating or Cooling system, respectively.

Note that the Distribution System itself does not instance System Properties.  A distribution system can only consume energy through its prime mover and thermal transfer with the environment. The Prime Mover object instances System Properties. Thermal transfer to or from the fluid through its segments will affect the system(s) that are connected to (reference) it (such as a Hot Water Heating or HVAC system).  Thus, the thermal energy transferred through the segment surface should be captured by the zone in which the segment is located and the systems that reference it.

Example 1. A water DistributionSystem may serve both space heating as well as domestic hot water for kitchen and bathroom fixtures (i.e. dishwasher, shower). Systems that may reference this DistributionSystem include: a WaterHeating system, a grey-water HeatRecovery system and an HVACSystem.

Example 2.
An air DistributionSystem may consist of supply and return ducting and a supply fan.  An HVACSystem such as a furnace or air-source heat-pump would reference the DistributionSystem (through its DeliveryMethod element).  

Example 3.
A whole-house fan would be modeled as an HVAC system with a DeliveryMethod that references a Distribution System.  The Distribution System may include segments (inlet and exhaust ducting) and a fan (Prime Mover). The Ventilation properties in HVAC would further describe the rate of air exchange with outside.  The zone(s) referencing the HVAC system would specify the temperature setpoint schedule and any additional thermal loads.  

Alternatively, if the fan is controlled by a time schedule, rather than temperature schedule, the schedule may defined in the Prime Mover system properties.  Then, no HVAC system needs to be defined.

Example 4.
A bathroom or kitchen exhaust fan may be modeled as a Distribution System with just a Prime Mover (segments optional).  The schedule in the System Properties of the Primer Mover may define the operating schedule of the fan.
Diagram
Diagram DistributionSystem_xsd.tmp#DistributionSystemType_id DistributionSystem_xsd.tmp#DistributionSystemType_Name DistributionSystem_xsd.tmp#DistributionSystemType_Description DistributionSystem_xsd.tmp#DistributionSystemType_FluidTransported DistributionSystem_xsd.tmp#DistributionSystemType_DistributionEquipmentDefinition DistributionSystem_xsd.tmp#DistributionSystemType_PrimeMover DistributionSystem_xsd.tmp#DistributionSystemType_Segment
Used by
Model Name{0,1} , Description{0,1} , FluidTransported{0,1} , DistributionEquipmentDefinition* , PrimeMover* , Segment*
Children Description, DistributionEquipmentDefinition, FluidTransported, Name, PrimeMover, Segment
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:complexType name="DistributionSystemType">
  <xs:annotation>
    <xs:documentation>A Distribution System describes the mechanical systems and equipment that transport air, water or another fluid. It consists of two components: Prime Mover (pump or fan) and Segment. A Distribution System (optionally) consists of one or many Prime Movers, which are pumps or fans that causes the fluid to flow. The Prime Mover has System and Equipment properties. A Distribution System (optionally) consists of one or many Segments, which is a duct or pipe that transports the fluid. The Segment has Equipment properties in addition to leakage and insulation properties (referenced from the Building schema). The Distribution Systems was chosen to stand alone because of how the other systems interact with it and because one distribution system may serve multiple purposes. It is be referenced by other systems such as an HVAC or WaterHeating system that interact with it. A Distribution System (particularly air or water) may be referenced by an HVAC system in one of three ways. A Distribution System may be referenced as the method of delivery of conditioning from the HVAC system (i.e. the ducting or piping that delivers conditioning). Alternatively, a Distribution System may be referenced as the source of heat or cold (fluid to reject heat to) for a Heating or Cooling system, respectively. Note that the Distribution System itself does not instance System Properties. A distribution system can only consume energy through its prime mover and thermal transfer with the environment. The Prime Mover object instances System Properties. Thermal transfer to or from the fluid through its segments will affect the system(s) that are connected to (reference) it (such as a Hot Water Heating or HVAC system). Thus, the thermal energy transferred through the segment surface should be captured by the zone in which the segment is located and the systems that reference it. Example 1. A water DistributionSystem may serve both space heating as well as domestic hot water for kitchen and bathroom fixtures (i.e. dishwasher, shower). Systems that may reference this DistributionSystem include: a WaterHeating system, a grey-water HeatRecovery system and an HVACSystem. Example 2. An air DistributionSystem may consist of supply and return ducting and a supply fan. An HVACSystem such as a furnace or air-source heat-pump would reference the DistributionSystem (through its DeliveryMethod element). Example 3. A whole-house fan would be modeled as an HVAC system with a DeliveryMethod that references a Distribution System. The Distribution System may include segments (inlet and exhaust ducting) and a fan (Prime Mover). The Ventilation properties in HVAC would further describe the rate of air exchange with outside. The zone(s) referencing the HVAC system would specify the temperature setpoint schedule and any additional thermal loads. Alternatively, if the fan is controlled by a time schedule, rather than temperature schedule, the schedule may defined in the Prime Mover system properties. Then, no HVAC system needs to be defined. Example 4. A bathroom or kitchen exhaust fan may be modeled as a Distribution System with just a Prime Mover (segments optional). The schedule in the System Properties of the Primer Mover may define the operating schedule of the fan.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Place for user to include additional notes/description of the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="FluidTransported" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The fluid transported by the distribution system. It may be useful to also indicate the specific gravity of the fluid if it is not a common one. Examples: Air Water Glycol Oil, specific gravity = 0.8 Heat Transfer Fluid</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="DistributionEquipmentDefinition" type="EquipmentDefinitionType"/>
    <xs:element name="PrimeMover" type="PrimeMoverSystemType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Any pump or fan that drives the fluid - causes it to flow.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="Segment" type="DistributionSegmentType">
      <xs:annotation>
        <xs:documentation>A segment of the vessel (pipe, duct, etc.) that contains and transports the fluid.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
Complex Type PrimeMoverSystemType
Namespace http://www.iepmodel.net
Annotations
A prime mover is a device that causes a fluid to flow, i.e. a pump or fan.  The properties of this device are captured here. This object includes System and Equipment properties.
Diagram
Diagram DistributionSystem_xsd.tmp#PrimeMoverSystemType_id DistributionSystem_xsd.tmp#PrimeMoverSystemType_Name DistributionSystem_xsd.tmp#PrimeMoverSystemType_Description DistributionSystem_xsd.tmp#PrimeMoverSystemType_DesignFlow DistributionSystem_xsd.tmp#PrimeMoverSystemType_DesignPressure DistributionSystem_xsd.tmp#PrimeMoverSystemType_DeviceTechnology DistributionSystem_xsd.tmp#PrimeMoverSystemType_FlowControl DistributionSystem_xsd.tmp#PrimeMoverSystemType_SystemProperties DistributionSystem_xsd.tmp#PrimeMoverSystemType_PrimeMoverEquipment DistributionSystem_xsd.tmp#PrimeMoverSystemType_Quantity
Used by
Model Name{0,1} , Description{0,1} , DesignFlow{0,1} , DesignPressure{0,1} , DeviceTechnology* , FlowControl* , SystemProperties{0,1} , PrimeMoverEquipment* , Quantity{0,1}
Children Description, DesignFlow, DesignPressure, DeviceTechnology, FlowControl, Name, PrimeMoverEquipment, Quantity, SystemProperties
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:complexType name="PrimeMoverSystemType">
  <xs:annotation>
    <xs:documentation>A prime mover is a device that causes a fluid to flow, i.e. a pump or fan. The properties of this device are captured here. This object includes System and Equipment properties.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Place for user to include additional notes/description of the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DesignFlow" type="FlowType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The volumetric flow that the pump/fan was designed to provide. This correspondes to the Design Pressure. Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve. Typically, this is not the maximum flow that the device can provide.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DesignPressure" type="PressureType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The pressure across the pump/fan (P_outlet - P_inlet) that it was designed to provide. This corresponds to the the Design Flow. Typically, the design pressure and design flow represent the maximum efficiency point on the manufacturer fan/pump curve. Typically, this is not the maximum pressure across the device.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DeviceTechnology" type="xs:string" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The type of pump/fan device. This typically indicates the blade/impeller type. Examples: Centrifugal, Forward Curved Centrifugal, Backward Curved Centrifugal, Radial Blade Centrifugal, Airfoil Centrifugal, Plenum Axial, Propeller Axial, Turbine</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="FlowControl" type="xs:string" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The method used to control the flow rate through the pump/fan. Note that there may be more than one, since it is not uncommon (though somewhat inefficient) to find a VFD and throttle used. Examples: Valve-Manual/Automatic Damper-Manual/Automatic Variable Speed Variable Pitch Blade Inlet Guide Vane Outlet Damper</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="SystemProperties" type="CommonSystemPropertiesType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Characteristics of the system are captured here. Note that this reflects the system (pump/fan, motor, VFD, etc.). Properties of the individual components may be captured in equipment attributes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="PrimeMoverEquipment" type="EquipmentInstanceType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Details of the hardware are captured here.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Quantity" type="xs:int" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The quantity of these systems (fans/pumps) existing and operating.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
Complex Type DistributionSegmentType
Namespace http://www.iepmodel.net
Annotations
User may define the details of a pipe or duct segment in the distribution system.

One or many segments may defined as necessary to describe the system in detail.
Diagram
Diagram DistributionSystem_xsd.tmp#DistributionSegmentType_id DistributionSystem_xsd.tmp#DistributionSegmentType_Name DistributionSystem_xsd.tmp#DistributionSegmentType_Description DistributionSystem_xsd.tmp#DistributionSegmentType_SegmentEquipment DistributionSystem_xsd.tmp#DistributionSegmentType_Insulation DistributionSystem_xsd.tmp#DistributionSegmentType_Leakage DistributionSystem_xsd.tmp#DistributionSegmentType_PressureRated DistributionSystem_xsd.tmp#DistributionSegmentType_FlowRated DistributionSystem_xsd.tmp#DistributionSegmentType_FlowControl DistributionSystem_xsd.tmp#DistributionSegmentType_RefZoneLocationID
Used by
Model Name{0,1} , Description{0,1} , SegmentEquipment* , Insulation* , Leakage{0,1} , PressureRated{0,1} , FlowRated{0,1} , FlowControl* , RefZoneLocationID{0,1}
Children Description, FlowControl, FlowRated, Insulation, Leakage, Name, PressureRated, RefZoneLocationID, SegmentEquipment
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:complexType name="DistributionSegmentType">
  <xs:annotation>
    <xs:documentation>User may define the details of a pipe or duct segment in the distribution system. One or many segments may defined as necessary to describe the system in detail.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is simply a descriptive name, typically a common name used for the system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Place for user to include additional notes and description of this segment. If a complex system of segments is to be defined, it would be useful to describe the system here. Other quantities or features may also be described here, such as the loss coefficient (i.e. pressure drop due to fluid friction).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="SegmentEquipment" type="EquipmentInstanceType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Characteristics of the segment (pipe/duct/etc.) hardware are captured here.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="Insulation" type="InsulationType"/>
    <xs:element minOccurs="0" name="Leakage" type="LeakageType"/>
    <xs:element name="PressureRated" type="PressureType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The maximum or design pressure for which the pipe/duct segment is rated.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="FlowRated" type="FlowType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The maximum or design flow rate for which the pipe/duct segment is rated.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="FlowControl" type="xs:string">
      <xs:annotation>
        <xs:documentation>Describe a flow control device here: Valve - Manual Valve - Automatic Damper - Manual Damper - Automatic Turning Vanes, loss coefficient 0.24</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="1" minOccurs="0" name="RefZoneLocationID" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This is the zone where the segment is located. This is for the purpose of capturing the heat lost to or absorbed from the environment by the fluid in the segment.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
Attribute PrimeMoverSystemType / @id
Namespace No namespace
Type xs:ID
Properties
content: simple
Used by
Complex Type PrimeMoverSystemType
Source
<xs:attribute name="id" type="xs:ID"/>
Attribute DistributionSegmentType / @id
Namespace No namespace
Type xs:ID
Properties
content: simple
Used by
Source
<xs:attribute name="id" type="xs:ID"/>
Attribute DistributionSystemType / @id
Namespace No namespace
Type xs:ID
Properties
content: simple
Used by
Complex Type DistributionSystemType
Source
<xs:attribute name="id" type="xs:ID"/>