Showing:

Annotations
Attributes
Diagrams
Instances
Properties
Source
Used by
Included schema HVACSystem.xsd
Namespace http://www.iepmodel.net
Annotations
This schema defines the parameters associated with an HVAC system.  

An HVAC system may contain any combination of the following: a heating system, a cooling system and ventilation system. Ventilation is defined here as a system that exchanges air in a conditioned zone with air outside the building.

An HVAC system may also contain an instance of a distribution system, which is used to condition (transfer heat to or from) a space.  The distribution system consists (optionally) of prime movers (pumps or fans) and segments (segments of duct or pipe, etc.).  Note that there can be only one space-serving distribution system per instance of an HVAC system.  Therefore, if multiple distribution systems serve a space, multiple HVAC systems must be defined.

An HVAC system serves a zone, however, zones reference the HVAC systems that serve them.

Note that parameters associated with the transport and movement of air and water are captured in a Distribution System.
Properties
attribute form default: unqualified
element form default: unqualified
Element HVACSystemType / 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 HVACSystemType / 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 HVACSystemType / CoolingSystem
Namespace No namespace
Annotations
This is to capture details relating to the operation and energy consumption of the cooling system.
Diagram
Diagram HVACSystem_xsd.tmp#CoolingSystemType_Name HVACSystem_xsd.tmp#CoolingSystemType_Description HVACSystem_xsd.tmp#CoolingSystemType_CoolingMethod HVACSystem_xsd.tmp#CoolingSystemType_SystemProperties HVACSystem_xsd.tmp#CoolingSystemType_RefDistributionSystemCoolSource HVACSystem_xsd.tmp#CoolingSystemType_CoolingInstance HVACSystem_xsd.tmp#CoolingSystemType
Type CoolingSystemType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model Name{0,1} , Description{0,1} , CoolingMethod{0,1} , SystemProperties{0,1} , RefDistributionSystemCoolSource{0,1} , CoolingInstance*
Children CoolingInstance, CoolingMethod, Description, Name, RefDistributionSystemCoolSource, SystemProperties
Instance
<CoolingSystem>
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <CoolingMethod>{0,1}</CoolingMethod>
  <SystemProperties>{0,1}</SystemProperties>
  <RefDistributionSystemCoolSource>{0,1}</RefDistributionSystemCoolSource>
  <CoolingInstance EquipmentDefinitionIdRef="" id="">{0,unbounded}</CoolingInstance>
</CoolingSystem>
Source
<xs:element name="CoolingSystem" type="CoolingSystemType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is to capture details relating to the operation and energy consumption of the cooling system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CoolingSystemType / 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 CoolingSystemType / 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 CoolingSystemType / CoolingMethod
Namespace No namespace
Annotations
This defines the method/way in which the cooling system makes cold (removes heat).
Examples:
Absorption
Evaporative
Refrigeration – Air Rejection
Refrigeration – Water Rejection
Hydronic Coils
Refrigerant (Direct Expansion, DX) Coils
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="CoolingMethod" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This defines the method/way in which the cooling system makes cold (removes heat). Examples: Absorption Evaporative Refrigeration – Air Rejection Refrigeration – Water Rejection Hydronic Coils Refrigerant (Direct Expansion, DX) Coils</xs:documentation>
  </xs:annotation>
</xs:element>
Element CoolingSystemType / SystemProperties
Namespace No namespace
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
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"/>
Element CoolingSystemType / RefDistributionSystemCoolSource
Namespace No namespace
Annotations
This is an optional reference to the distribution system to which heat is rejected (the cooling source). 
Examples:
- A geothermal heat pump may reference a water loop that cycles to a pond or to piping in the ground.
- An air handler with chilled water coils would reference the chilled water loop that serves the coils.
- A water-cooled chiller or condenser would reference a condenser water loop.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystemCoolSource" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This is an optional reference to the distribution system to which heat is rejected (the cooling source). Examples: - A geothermal heat pump may reference a water loop that cycles to a pond or to piping in the ground. - An air handler with chilled water coils would reference the chilled water loop that serves the coils. - A water-cooled chiller or condenser would reference a condenser water loop.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CoolingSystemType / CoolingInstance
Namespace No namespace
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType
Type EquipmentInstanceType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
nillable: false
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
<CoolingInstance 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>
</CoolingInstance>
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 maxOccurs="unbounded" minOccurs="0" name="CoolingInstance" nillable="false" type="EquipmentInstanceType"/>
Element HVACSystemType / HeatingSystem
Namespace No namespace
Annotations
This is to capture details relating to the operation and energy consumption of the heating system.
Diagram
Diagram HVACSystem_xsd.tmp#HeatingSystemType_Name HVACSystem_xsd.tmp#HeatingSystemType_Description HVACSystem_xsd.tmp#HeatingSystemType_HeatingMethod HVACSystem_xsd.tmp#HeatingSystemType_SystemProperties HVACSystem_xsd.tmp#HeatingSystemType_RefDistributionSystemHeatSource HVACSystem_xsd.tmp#HeatingSystemType_HeatingEquipment HVACSystem_xsd.tmp#HeatingSystemType
Type HeatingSystemType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model Name{0,1} , Description{0,1} , HeatingMethod{0,1} , SystemProperties{0,1} , RefDistributionSystemHeatSource{0,1} , HeatingEquipment*
Children Description, HeatingEquipment, HeatingMethod, Name, RefDistributionSystemHeatSource, SystemProperties
Instance
<HeatingSystem>
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <HeatingMethod>{0,1}</HeatingMethod>
  <SystemProperties>{0,1}</SystemProperties>
  <RefDistributionSystemHeatSource>{0,1}</RefDistributionSystemHeatSource>
  <HeatingEquipment EquipmentDefinitionIdRef="" id="">{0,unbounded}</HeatingEquipment>
</HeatingSystem>
Source
<xs:element name="HeatingSystem" type="HeatingSystemType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is to capture details relating to the operation and energy consumption of the heating system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element HeatingSystemType / 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 HeatingSystemType / 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 HeatingSystemType / HeatingMethod
Namespace No namespace
Annotations
This defines the method/way in which the heating system makes heat.
Examples:
Fuel Burning
Electric Resistance
Refrigeration – Air-Source
Refrigeration – Water-Source
Hydronic Coils
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="HeatingMethod" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This defines the method/way in which the heating system makes heat. Examples: Fuel Burning Electric Resistance Refrigeration – Air-Source Refrigeration – Water-Source Hydronic Coils</xs:documentation>
  </xs:annotation>
</xs:element>
Element HeatingSystemType / SystemProperties
Namespace No namespace
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
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"/>
Element HeatingSystemType / RefDistributionSystemHeatSource
Namespace No namespace
Annotations
This is an optional reference to the distribution system, which is the source of heat.
Examples:
- A radiant heating system may consist of "radiators" and this references the hot water loop that serves it.
- An air handler with hot water coils may reference the hot water loop that serves the coils.
- A heat pump would reference the water loop from which it absorbs heat when it is in heating mode.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystemHeatSource" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This is an optional reference to the distribution system, which is the source of heat. Examples: - A radiant heating system may consist of "radiators" and this references the hot water loop that serves it. - An air handler with hot water coils may reference the hot water loop that serves the coils. - A heat pump would reference the water loop from which it absorbs heat when it is in heating mode.</xs:documentation>
  </xs:annotation>
</xs:element>
Element HeatingSystemType / HeatingEquipment
Namespace No namespace
Diagram
Diagram Common_xsd.tmp#EquipmentInstanceType_id Common_xsd.tmp#EquipmentInstanceType_EquipmentDefinitionIdRef Common_xsd.tmp#EquipmentInstanceType_Name Common_xsd.tmp#EquipmentInstanceType_SerialNumber Common_xsd.tmp#EquipmentInstanceType_DateManufactured Common_xsd.tmp#EquipmentInstanceType_Location Common_xsd.tmp#EquipmentInstanceType_Condition Common_xsd.tmp#EquipmentInstanceType_LastServiced Common_xsd.tmp#EquipmentInstanceType_UsefulLife Common_xsd.tmp#EquipmentInstanceType
Type EquipmentInstanceType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
nillable: false
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
<HeatingEquipment 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>
</HeatingEquipment>
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="HeatingEquipment" maxOccurs="unbounded" minOccurs="0" nillable="false" type="EquipmentInstanceType"/>
Element HVACSystemType / HVACEquipmentDefinition
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
<HVACEquipmentDefinition 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>
</HVACEquipmentDefinition>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID required
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="HVACEquipmentDefinition" type="EquipmentDefinitionType"/>
Element HVACSystemType / DeliverySystem
Namespace No namespace
Annotations
This describes the details of the way in which the HVAC system delivers conditioning to the space it conditions. This allows the user to define ducting or piping etc. This includes an optional reference to a distribution system.
Diagram
Diagram HVACSystem_xsd.tmp#DeliverySystemType_Name HVACSystem_xsd.tmp#DeliverySystemType_Description HVACSystem_xsd.tmp#DeliverySystemType_DeliveryMethod HVACSystem_xsd.tmp#DeliverySystemType_RefDistributionSystem HVACSystem_xsd.tmp#DeliverySystemType
Type DeliverySystemType
Properties
content: complex
minOccurs: 0
Model Name{0,1} , Description{0,1} , DeliveryMethod{0,1} , RefDistributionSystem{0,1}
Children DeliveryMethod, Description, Name, RefDistributionSystem
Instance
<DeliverySystem>
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <DeliveryMethod>{0,1}</DeliveryMethod>
  <RefDistributionSystem>{0,1}</RefDistributionSystem>
</DeliverySystem>
Source
<xs:element minOccurs="0" name="DeliverySystem" type="DeliverySystemType">
  <xs:annotation>
    <xs:documentation>This describes the details of the way in which the HVAC system delivers conditioning to the space it conditions. This allows the user to define ducting or piping etc. This includes an optional reference to a distribution system.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DeliverySystemType / 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 DeliverySystemType / 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 DeliverySystemType / DeliveryMethod
Namespace No namespace
Annotations
This defines the way in which the HVAC system delivers conditioning to the space.
Examples:
Radiant
Natural Convection
Forced Convection
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="DeliveryMethod" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This defines the way in which the HVAC system delivers conditioning to the space. Examples: Radiant Natural Convection Forced Convection</xs:documentation>
  </xs:annotation>
</xs:element>
Element DeliverySystemType / RefDistributionSystem
Namespace No namespace
Annotations
This is an (optional) reference to the distribution system that the HVAC system uses to provide conditioning to the space.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystem" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This is an (optional) reference to the distribution system that the HVAC system uses to provide conditioning to the space.</xs:documentation>
  </xs:annotation>
</xs:element>
Element HVACSystemType / VentilationProperties
Namespace No namespace
Diagram
Diagram HVACSystem_xsd.tmp#VentilationPropertiesType_Name HVACSystem_xsd.tmp#VentilationPropertiesType_Description HVACSystem_xsd.tmp#VentilationPropertiesType_VentilationControlSchedule HVACSystem_xsd.tmp#VentilationPropertiesType
Type VentilationPropertiesType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Name{0,1} , Description{0,1} , VentilationControlSchedule{0,1}
Children Description, Name, VentilationControlSchedule
Instance
<VentilationProperties>
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <VentilationControlSchedule>{0,1}</VentilationControlSchedule>
</VentilationProperties>
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="VentilationProperties" type="VentilationPropertiesType"/>
Element VentilationPropertiesType / 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 VentilationPropertiesType / Description
Namespace No namespace
Annotations
Place for user to include additional notes and descriptions. 
Examples:
- Inlet, 100% outside air, fixed/variable damper
- Exhaust, fixed/variable damper
- Outside air economizer system
- Natural: Windows, manual/auto control
- Exhaust, relief vent
- Whole house fan

It may be appropriate to define the nominal (maximum, 100%) outside air flow rate, particularly when the Ventilation Control Schedule is a fraction schedule type. This would be useful when the ventilation type is natural or if no Delivery System is defined.

It may be appropriate to define the flow rate units (cubic-feet per minute) if the Ventilation Control Schedule type is a value schedule.
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 descriptions. Examples: - Inlet, 100% outside air, fixed/variable damper - Exhaust, fixed/variable damper - Outside air economizer system - Natural: Windows, manual/auto control - Exhaust, relief vent - Whole house fan It may be appropriate to define the nominal (maximum, 100%) outside air flow rate, particularly when the Ventilation Control Schedule is a fraction schedule type. This would be useful when the ventilation type is natural or if no Delivery System is defined. It may be appropriate to define the flow rate units (cubic-feet per minute) if the Ventilation Control Schedule type is a value schedule.</xs:documentation>
  </xs:annotation>
</xs:element>
Element VentilationPropertiesType / VentilationControlSchedule
Namespace No namespace
Annotations
This schedule defines when and what fraction of air is exchanged with outside. A fraction schedule type is most appropriate. The nominal (100%) flow rate would reflect the Delivery System flow rate at the given conditions.

Alternatively, if the ventilation type is natural, the user may define the maximum flow rate in the Description.

Another option would be to define a value schedule and indicate in the description what the units of the schedule values represent (i.e. cubic-feet per minute).
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="VentilationControlSchedule" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This schedule defines when and what fraction of air is exchanged with outside. A fraction schedule type is most appropriate. The nominal (100%) flow rate would reflect the Delivery System flow rate at the given conditions. Alternatively, if the ventilation type is natural, the user may define the maximum flow rate in the Description. Another option would be to define a value schedule and indicate in the description what the units of the schedule values represent (i.e. cubic-feet per minute).</xs:documentation>
  </xs:annotation>
</xs:element>
Element HVACSystem
Namespace http://www.iepmodel.net
Annotations
This schema defines the parameters associated with an HVAC system.  

An HVAC system may contain any combination of the following: a heating system, a cooling system and ventilation properties. Ventilation is defined here as the exchange of air in the space/zone with air outside.

An HVAC system references Distribution systems that serve one of three purposes:
- deliver conditioning to a space/zone.
- provide heat.
- provide cold (a fluid to reject heat to).

An HVAC system serves a zone, however, zones reference the HVAC systems that serve them.

Note that parameters associated with the transport and movement of air and water are captured in a Distribution System.
Diagram
Diagram HVACSystem_xsd.tmp#HVACSystemType_id HVACSystem_xsd.tmp#HVACSystemType_Name HVACSystem_xsd.tmp#HVACSystemType_Description HVACSystem_xsd.tmp#HVACSystemType_CoolingSystem HVACSystem_xsd.tmp#HVACSystemType_HeatingSystem HVACSystem_xsd.tmp#HVACSystemType_HVACEquipmentDefinition HVACSystem_xsd.tmp#HVACSystemType_DeliverySystem HVACSystem_xsd.tmp#HVACSystemType_VentilationProperties HVACSystem_xsd.tmp#HVACSystemType
Type HVACSystemType
Properties
content: complex
Model Name{0,1} , Description{0,1} , CoolingSystem{0,1} , HeatingSystem{0,1} , HVACEquipmentDefinition* , DeliverySystem{0,1} , VentilationProperties*
Children CoolingSystem, DeliverySystem, Description, HVACEquipmentDefinition, HeatingSystem, Name, VentilationProperties
Instance
<HVACSystem id="" xmlns="http://www.iepmodel.net">
  <Name>{0,1}</Name>
  <Description>{0,1}</Description>
  <CoolingSystem>{0,1}</CoolingSystem>
  <HeatingSystem>{0,1}</HeatingSystem>
  <HVACEquipmentDefinition id="">{0,unbounded}</HVACEquipmentDefinition>
  <DeliverySystem>{0,1}</DeliverySystem>
  <VentilationProperties>{0,unbounded}</VentilationProperties>
</HVACSystem>
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:element name="HVACSystem" type="HVACSystemType">
  <xs:annotation>
    <xs:documentation>This schema defines the parameters associated with an HVAC system. An HVAC system may contain any combination of the following: a heating system, a cooling system and ventilation properties. Ventilation is defined here as the exchange of air in the space/zone with air outside. An HVAC system references Distribution systems that serve one of three purposes: - deliver conditioning to a space/zone. - provide heat. - provide cold (a fluid to reject heat to). An HVAC system serves a zone, however, zones reference the HVAC systems that serve them. Note that parameters associated with the transport and movement of air and water are captured in a Distribution System.</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type HVACSystemType
Namespace http://www.iepmodel.net
Annotations
This schema defines the parameters associated with an HVAC system.  

An HVAC system may contain any combination of the following: a heating system, a cooling system and ventilation properties. Ventilation is defined here as the exchange of air in the space/zone with air outside.

An HVAC system references Distribution systems that serve one of three purposes:
- deliver conditioning to a space/zone.
- provide heat.
- provide cold (a fluid to reject heat to).

An HVAC system serves a zone, however, zones reference the HVAC systems that serve them.

Note that parameters associated with the transport and movement of air and water are captured in a Distribution System.
Diagram
Diagram HVACSystem_xsd.tmp#HVACSystemType_id HVACSystem_xsd.tmp#HVACSystemType_Name HVACSystem_xsd.tmp#HVACSystemType_Description HVACSystem_xsd.tmp#HVACSystemType_CoolingSystem HVACSystem_xsd.tmp#HVACSystemType_HeatingSystem HVACSystem_xsd.tmp#HVACSystemType_HVACEquipmentDefinition HVACSystem_xsd.tmp#HVACSystemType_DeliverySystem HVACSystem_xsd.tmp#HVACSystemType_VentilationProperties
Used by
Model Name{0,1} , Description{0,1} , CoolingSystem{0,1} , HeatingSystem{0,1} , HVACEquipmentDefinition* , DeliverySystem{0,1} , VentilationProperties*
Children CoolingSystem, DeliverySystem, Description, HVACEquipmentDefinition, HeatingSystem, Name, VentilationProperties
Attributes
QName Type Fixed Default Use Annotation
id xs:ID optional
Source
<xs:complexType name="HVACSystemType">
  <xs:annotation>
    <xs:documentation>This schema defines the parameters associated with an HVAC system. An HVAC system may contain any combination of the following: a heating system, a cooling system and ventilation properties. Ventilation is defined here as the exchange of air in the space/zone with air outside. An HVAC system references Distribution systems that serve one of three purposes: - deliver conditioning to a space/zone. - provide heat. - provide cold (a fluid to reject heat to). An HVAC system serves a zone, however, zones reference the HVAC systems that serve them. Note that parameters associated with the transport and movement of air and water are captured in a Distribution System.</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="CoolingSystem" type="CoolingSystemType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is to capture details relating to the operation and energy consumption of the cooling system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="HeatingSystem" type="HeatingSystemType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is to capture details relating to the operation and energy consumption of the heating system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="HVACEquipmentDefinition" type="EquipmentDefinitionType"/>
    <xs:element minOccurs="0" name="DeliverySystem" type="DeliverySystemType">
      <xs:annotation>
        <xs:documentation>This describes the details of the way in which the HVAC system delivers conditioning to the space it conditions. This allows the user to define ducting or piping etc. This includes an optional reference to a distribution system.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="VentilationProperties" type="VentilationPropertiesType"/>
  </xs:sequence>
  <xs:attribute form="unqualified" name="id" type="xs:ID"/>
</xs:complexType>
Complex Type CoolingSystemType
Namespace http://www.iepmodel.net
Annotations
This describes the details of the cooling system, which may be one of many or the only component of the HVAC system. System properties are contained here.
Diagram
Diagram HVACSystem_xsd.tmp#CoolingSystemType_Name HVACSystem_xsd.tmp#CoolingSystemType_Description HVACSystem_xsd.tmp#CoolingSystemType_CoolingMethod HVACSystem_xsd.tmp#CoolingSystemType_SystemProperties HVACSystem_xsd.tmp#CoolingSystemType_RefDistributionSystemCoolSource HVACSystem_xsd.tmp#CoolingSystemType_CoolingInstance
Used by
Model Name{0,1} , Description{0,1} , CoolingMethod{0,1} , SystemProperties{0,1} , RefDistributionSystemCoolSource{0,1} , CoolingInstance*
Children CoolingInstance, CoolingMethod, Description, Name, RefDistributionSystemCoolSource, SystemProperties
Source
<xs:complexType name="CoolingSystemType">
  <xs:annotation>
    <xs:documentation>This describes the details of the cooling system, which may be one of many or the only component of the HVAC system. System properties are contained here.</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="CoolingMethod" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This defines the method/way in which the cooling system makes cold (removes heat). Examples: Absorption Evaporative Refrigeration – Air Rejection Refrigeration – Water Rejection Hydronic Coils Refrigerant (Direct Expansion, DX) Coils</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="SystemProperties" type="CommonSystemPropertiesType" minOccurs="0"/>
    <xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystemCoolSource" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This is an optional reference to the distribution system to which heat is rejected (the cooling source). Examples: - A geothermal heat pump may reference a water loop that cycles to a pond or to piping in the ground. - An air handler with chilled water coils would reference the chilled water loop that serves the coils. - A water-cooled chiller or condenser would reference a condenser water loop.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="CoolingInstance" nillable="false" type="EquipmentInstanceType"/>
  </xs:sequence>
</xs:complexType>
Complex Type HeatingSystemType
Namespace http://www.iepmodel.net
Annotations
This describes the details of the heating system, which may be one of many or the only component of the HVAC system. System properties are contained here.
Diagram
Diagram HVACSystem_xsd.tmp#HeatingSystemType_Name HVACSystem_xsd.tmp#HeatingSystemType_Description HVACSystem_xsd.tmp#HeatingSystemType_HeatingMethod HVACSystem_xsd.tmp#HeatingSystemType_SystemProperties HVACSystem_xsd.tmp#HeatingSystemType_RefDistributionSystemHeatSource HVACSystem_xsd.tmp#HeatingSystemType_HeatingEquipment
Used by
Model Name{0,1} , Description{0,1} , HeatingMethod{0,1} , SystemProperties{0,1} , RefDistributionSystemHeatSource{0,1} , HeatingEquipment*
Children Description, HeatingEquipment, HeatingMethod, Name, RefDistributionSystemHeatSource, SystemProperties
Source
<xs:complexType name="HeatingSystemType">
  <xs:annotation>
    <xs:documentation>This describes the details of the heating system, which may be one of many or the only component of the HVAC system. System properties are contained here.</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="HeatingMethod" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This defines the method/way in which the heating system makes heat. Examples: Fuel Burning Electric Resistance Refrigeration – Air-Source Refrigeration – Water-Source Hydronic Coils</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="SystemProperties" type="CommonSystemPropertiesType" minOccurs="0"/>
    <xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystemHeatSource" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This is an optional reference to the distribution system, which is the source of heat. Examples: - A radiant heating system may consist of "radiators" and this references the hot water loop that serves it. - An air handler with hot water coils may reference the hot water loop that serves the coils. - A heat pump would reference the water loop from which it absorbs heat when it is in heating mode.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="HeatingEquipment" maxOccurs="unbounded" minOccurs="0" nillable="false" type="EquipmentInstanceType"/>
  </xs:sequence>
</xs:complexType>
Complex Type DeliverySystemType
Namespace http://www.iepmodel.net
Annotations
This describes the details of the way in which the HVAC system delivers conditioning to the space it conditions. This allows the user to define ducting or piping etc. This includes an optional reference to a distribution system.
Diagram
Diagram HVACSystem_xsd.tmp#DeliverySystemType_Name HVACSystem_xsd.tmp#DeliverySystemType_Description HVACSystem_xsd.tmp#DeliverySystemType_DeliveryMethod HVACSystem_xsd.tmp#DeliverySystemType_RefDistributionSystem
Used by
Model Name{0,1} , Description{0,1} , DeliveryMethod{0,1} , RefDistributionSystem{0,1}
Children DeliveryMethod, Description, Name, RefDistributionSystem
Source
<xs:complexType name="DeliverySystemType">
  <xs:annotation>
    <xs:documentation>This describes the details of the way in which the HVAC system delivers conditioning to the space it conditions. This allows the user to define ducting or piping etc. This includes an optional reference to a distribution system.</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="DeliveryMethod" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This defines the way in which the HVAC system delivers conditioning to the space. Examples: Radiant Natural Convection Forced Convection</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="1" minOccurs="0" name="RefDistributionSystem" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This is an (optional) reference to the distribution system that the HVAC system uses to provide conditioning to the space.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type VentilationPropertiesType
Namespace http://www.iepmodel.net
Annotations
This describes the properties of ventilation. 

Ventilation in the IEP model is defined as the exchange (inlet or exhaust) of air with the environment outside of the building. Since Delivery System defines the way in which air is transported, this object simply defines how, when and what portion of that air is inlet from or exhausted to outside.

It is not necessary to define a Delivery System in order to define ventilation. This is particularly true when the ventilation type is natural.

Ventilation should not be confused with "venting". This is not where one describes the ducting that provides conditioned air to the space/zone. This is done in the DeliverySystem.
Diagram
Diagram HVACSystem_xsd.tmp#VentilationPropertiesType_Name HVACSystem_xsd.tmp#VentilationPropertiesType_Description HVACSystem_xsd.tmp#VentilationPropertiesType_VentilationControlSchedule
Used by
Model Name{0,1} , Description{0,1} , VentilationControlSchedule{0,1}
Children Description, Name, VentilationControlSchedule
Source
<xs:complexType name="VentilationPropertiesType">
  <xs:annotation>
    <xs:documentation>This describes the properties of ventilation. Ventilation in the IEP model is defined as the exchange (inlet or exhaust) of air with the environment outside of the building. Since Delivery System defines the way in which air is transported, this object simply defines how, when and what portion of that air is inlet from or exhausted to outside. It is not necessary to define a Delivery System in order to define ventilation. This is particularly true when the ventilation type is natural. Ventilation should not be confused with "venting". This is not where one describes the ducting that provides conditioned air to the space/zone. This is done in the DeliverySystem.</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 descriptions. Examples: - Inlet, 100% outside air, fixed/variable damper - Exhaust, fixed/variable damper - Outside air economizer system - Natural: Windows, manual/auto control - Exhaust, relief vent - Whole house fan It may be appropriate to define the nominal (maximum, 100%) outside air flow rate, particularly when the Ventilation Control Schedule is a fraction schedule type. This would be useful when the ventilation type is natural or if no Delivery System is defined. It may be appropriate to define the flow rate units (cubic-feet per minute) if the Ventilation Control Schedule type is a value schedule.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="VentilationControlSchedule" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This schedule defines when and what fraction of air is exchanged with outside. A fraction schedule type is most appropriate. The nominal (100%) flow rate would reflect the Delivery System flow rate at the given conditions. Alternatively, if the ventilation type is natural, the user may define the maximum flow rate in the Description. Another option would be to define a value schedule and indicate in the description what the units of the schedule values represent (i.e. cubic-feet per minute).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Attribute HVACSystemType / @id
Namespace No namespace
Type xs:ID
Properties
content: simple
Used by
Complex Type HVACSystemType
Source
<xs:attribute form="unqualified" name="id" type="xs:ID"/>