Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Included schema CommonSystemProperties.xsd
Namespace http://www.iepmodel.net
Annotations
This schema defines the common attributes used by all systems.

System contains "Design_____" quantities to refer to the level of performance that the "system" was design to operate at.  Generally when doing an analysis, the design range of performance is considered. However, a particular equipment may have a different constraint on its capacity or output.
Properties
attribute form default: unqualified
element form default: unqualified
Element CommonSystemPropertiesType / Description
Namespace No namespace
Annotations
The name or description of the system, i.e. "Attic DX cooling unit".
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>The name or description of the system, i.e. "Attic DX cooling unit".</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / AnnualOperatingHours
Namespace No namespace
Annotations
The annual operating hours of the system.
Diagram
Diagram
Type restriction of xs:int
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
minInclusive 0
Source
<xs:element name="AnnualOperatingHours" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The annual operating hours of the system.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:int">
      <xs:minInclusive value="0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element CommonSystemPropertiesType / DesignEfficiency
Namespace No namespace
Annotations
Efficiency at design operating conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#EfficiencyType_Unit Common_xsd.tmp#EfficiencyType_UnitDesc Common_xsd.tmp#EfficiencyType_TestCondition Common_xsd.tmp#EfficiencyType
Type EfficiencyType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
TestCondition TestConditionEnumType optional
This represents the operating conditions (typically certified test conditons or full load) at which the efficiency is realized.  Note that at other conditions, the efficiency may be a different value.
Unit EfficiencyUnitEnumType optional
Unit of measurement specified as a string This should be used for defining the type value's units if the proper enum is not listed in Unit. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
UnitDesc xs:string optional
Unit of measurement specified as a string This should be used for defining the type value's units if the proper enum is not listed in Unit. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
Source
<xs:element name="DesignEfficiency" type="EfficiencyType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Efficiency at design operating conditions (typically full load, but not necessarily).</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / DesignInput
Namespace No namespace
Annotations
(Power) Input at design conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#PowerType_TestCondition Common_xsd.tmp#PowerType_Unit Common_xsd.tmp#PowerType_UnitDesc Common_xsd.tmp#PowerType_Fuel Common_xsd.tmp#PowerType_FuelDesc Common_xsd.tmp#PowerType
Type PowerType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Fuel EnergyClassEnumType Electricity optional
Fuel type specified as an enum. This should be used for defining the type value's fuel. If the proper enum is not listed, please use the FuelDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
FuelDesc xs:string Electricity optional
FuelType specified as a string. This should be used for defining the type value's fuel if the proper enum is not listed in Fuel. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
TestCondition xs:string optional
The "rating" or list of conditions at which the power was tested.
Unit PowerUnitEnumType optional
Unit of measurement specified as an enum. This should be used for defining the type value's units. If the proper enum is not listed, please use the UnitDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
UnitDesc xs:string kwh optional
Unit of measurement specified as a string This should be used for defining the type value's units if the proper enum is not listed in Unit. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
Source
<xs:element name="DesignInput" type="PowerType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>(Power) Input at design conditions (typically full load, but not necessarily).</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / DesignOutput
Namespace No namespace
Annotations
(Power) Output at design conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#PowerType_TestCondition Common_xsd.tmp#PowerType_Unit Common_xsd.tmp#PowerType_UnitDesc Common_xsd.tmp#PowerType_Fuel Common_xsd.tmp#PowerType_FuelDesc Common_xsd.tmp#PowerType
Type PowerType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Fuel EnergyClassEnumType Electricity optional
Fuel type specified as an enum. This should be used for defining the type value's fuel. If the proper enum is not listed, please use the FuelDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
FuelDesc xs:string Electricity optional
FuelType specified as a string. This should be used for defining the type value's fuel if the proper enum is not listed in Fuel. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
TestCondition xs:string optional
The "rating" or list of conditions at which the power was tested.
Unit PowerUnitEnumType optional
Unit of measurement specified as an enum. This should be used for defining the type value's units. If the proper enum is not listed, please use the UnitDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
UnitDesc xs:string kwh optional
Unit of measurement specified as a string This should be used for defining the type value's units if the proper enum is not listed in Unit. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
Source
<xs:element name="DesignOutput" type="PowerType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>(Power) Output at design conditions (typically full load, but not necessarily).</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / EnergyConsumption
Namespace No namespace
Annotations
This is a placeholder for analysis results.
Diagram
Diagram EnergyConsumption_xsd.tmp#EnergyConsumptionType_RevenueMeterIdRef EnergyConsumption_xsd.tmp#EnergyConsumptionType_DataSource EnergyConsumption_xsd.tmp#EnergyConsumptionType_Description EnergyConsumption_xsd.tmp#EnergyConsumptionType_EnergyConsumptionRecord EnergyConsumption_xsd.tmp#EnergyConsumptionType
Type EnergyConsumptionType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model DataSource{0,1} , Description{0,1} , EnergyConsumptionRecord+
Children DataSource, Description, EnergyConsumptionRecord
Instance
<EnergyConsumption RevenueMeterIdRef="">
  <DataSource>{0,1}</DataSource>
  <Description>{0,1}</Description>
  <EnergyConsumptionRecord>{1,unbounded}</EnergyConsumptionRecord>
</EnergyConsumption>
Attributes
QName Type Fixed Default Use Annotation
RevenueMeterIdRef xs:IDREF optional
A reference to a an optionally defined meter in the UtilityService XSD.  When benchmarking, a consumed quantity of energy must be associated to a defined revenue meter.
Source
<xs:element name="EnergyConsumption" type="EnergyConsumptionType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is a placeholder for analysis results.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / MaxInput
Namespace No namespace
Annotations
Maximum (Power) Input. Note that many systems are oversized when designed. This represents the absolute maximum power consumption of the equipment.
Diagram
Diagram Common_xsd.tmp#PowerType_TestCondition Common_xsd.tmp#PowerType_Unit Common_xsd.tmp#PowerType_UnitDesc Common_xsd.tmp#PowerType_Fuel Common_xsd.tmp#PowerType_FuelDesc Common_xsd.tmp#PowerType
Type PowerType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
Fuel EnergyClassEnumType Electricity optional
Fuel type specified as an enum. This should be used for defining the type value's fuel. If the proper enum is not listed, please use the FuelDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
FuelDesc xs:string Electricity optional
FuelType specified as a string. This should be used for defining the type value's fuel if the proper enum is not listed in Fuel. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the FuelDesc may contain a default type.
TestCondition xs:string optional
The "rating" or list of conditions at which the power was tested.
Unit PowerUnitEnumType optional
Unit of measurement specified as an enum. This should be used for defining the type value's units. If the proper enum is not listed, please use the UnitDesc field to specify the units. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
UnitDesc xs:string kwh optional
Unit of measurement specified as a string This should be used for defining the type value's units if the proper enum is not listed in Unit. These are all optional attributes in order to allow for a simplified value descriptions since these are used throughout the IEP schemas. Additionally the UnitDesc may contain a default type.
Source
<xs:element name="MaxInput" type="PowerType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Maximum (Power) Input. Note that many systems are oversized when designed. This represents the absolute maximum power consumption of the equipment.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / OperatingSchedule
Namespace No namespace
Annotations
The operating schedule of the system. This is likely to be a fraction schedule and represent the time-dependent capacity of the system. Note that particular systems, such as HVAC system, have additional schedules such as temperature schedules.

This references the IDREF of a complete Schedules element at the Project level
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xs:element name="OperatingSchedule" type="xs:IDREF" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The operating schedule of the system. This is likely to be a fraction schedule and represent the time-dependent capacity of the system. Note that particular systems, such as HVAC system, have additional schedules such as temperature schedules. This references the IDREF of a complete Schedules element at the Project level</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / RefZoneLocationID
Namespace No namespace
Annotations
This is the zone where the system is located. This is for the purpose of capturing the heat load that  the system introduces to its environment.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<xs:element name="RefZoneLocationID" type="xs:IDREF" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is the zone where the system is located. This is for the purpose of capturing the heat load that the system introduces to its environment.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CommonSystemPropertiesType / RefRevenueMeterID
Namespace No namespace
Annotations
This is used to reference the meter attached to the particular system.

Generator of this ID needs to create the RevenueMeter first in the UtilityService schema in order to link back here.
Diagram
Diagram
Type xs:IDREF
Properties
content: simple
minOccurs: 0
Source
<xs:element minOccurs="0" name="RefRevenueMeterID" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>This is used to reference the meter attached to the particular system. Generator of this ID needs to create the RevenueMeter first in the UtilityService schema in order to link back here.</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type CommonSystemPropertiesType
Namespace http://www.iepmodel.net
Annotations
These are common attributes of a system that are shared by the various system types used in this model.  The idea is to capture here, high-level properties related to the operation and energy consumption of various systems.  

Details of actual hardware not required for a 1st level analysis are not included here (these are located in CommonEquipmentAttributes).
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
Used by
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
Source
<xs:complexType name="CommonSystemPropertiesType">
  <xs:annotation>
    <xs:documentation>These are common attributes of a system that are shared by the various system types used in this model. The idea is to capture here, high-level properties related to the operation and energy consumption of various systems. Details of actual hardware not required for a 1st level analysis are not included here (these are located in CommonEquipmentAttributes).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Description" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The name or description of the system, i.e. "Attic DX cooling unit".</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="AnnualOperatingHours" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The annual operating hours of the system.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:int">
          <xs:minInclusive value="0"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="DesignEfficiency" type="EfficiencyType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Efficiency at design operating conditions (typically full load, but not necessarily).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DesignInput" type="PowerType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>(Power) Input at design conditions (typically full load, but not necessarily).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="DesignOutput" type="PowerType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>(Power) Output at design conditions (typically full load, but not necessarily).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="EnergyConsumption" type="EnergyConsumptionType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is a placeholder for analysis results.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="MaxInput" type="PowerType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Maximum (Power) Input. Note that many systems are oversized when designed. This represents the absolute maximum power consumption of the equipment.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="OperatingSchedule" type="xs:IDREF" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The operating schedule of the system. This is likely to be a fraction schedule and represent the time-dependent capacity of the system. Note that particular systems, such as HVAC system, have additional schedules such as temperature schedules. This references the IDREF of a complete Schedules element at the Project level</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="RefZoneLocationID" type="xs:IDREF" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>This is the zone where the system is located. This is for the purpose of capturing the heat load that the system introduces to its environment.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" name="RefRevenueMeterID" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>This is used to reference the meter attached to the particular system. Generator of this ID needs to create the RevenueMeter first in the UtilityService schema in order to link back here.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>