Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
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 commonSystemProperties / 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 commonSystemProperties / 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 commonSystemProperties / designEfficiency
Namespace No namespace
Annotations
 
Efficiency at design operating conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#efficiency_unit Common_xsd.tmp#efficiency_unitDesc Common_xsd.tmp#efficiency_testCondition Common_xsd.tmp#efficiency
Type efficiency
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
testCondition testConditionEnum 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 efficiencyUnitEnum 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="efficiency" 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 commonSystemProperties / designInput
Namespace No namespace
Annotations
 
(Power) Input at design conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#power_testCondition Common_xsd.tmp#power_unit Common_xsd.tmp#power_unitDesc Common_xsd.tmp#power_fuel Common_xsd.tmp#power_fuelDesc Common_xsd.tmp#power
Type power
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Default Use Annotation
fuel energyClassEnum 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 powerUnitEnum 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="power" 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 commonSystemProperties / designOutput
Namespace No namespace
Annotations
 
(Power) Output at design conditions (typically full load, but not necessarily).
Diagram
Diagram Common_xsd.tmp#power_testCondition Common_xsd.tmp#power_unit Common_xsd.tmp#power_unitDesc Common_xsd.tmp#power_fuel Common_xsd.tmp#power_fuelDesc Common_xsd.tmp#power
Type power
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Default Use Annotation
fuel energyClassEnum 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 powerUnitEnum 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="power" 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 commonSystemProperties / energyConsumption
Namespace No namespace
Annotations
 
This is a placeholder for analysis results.
Diagram
Diagram EnergyConsumption_xsd.tmp#energyRecord_periodStart EnergyConsumption_xsd.tmp#energyRecord_periodUnits EnergyConsumption_xsd.tmp#energyRecord_revenueMeterIdRef EnergyConsumption_xsd.tmp#energyRecord_dataSource EnergyConsumption_xsd.tmp#energyRecord_description EnergyConsumption_xsd.tmp#energyRecord_energyAmountUnits EnergyConsumption_xsd.tmp#energyRecord_energyAmounts EnergyConsumption_xsd.tmp#energyRecord_peakDemands EnergyConsumption_xsd.tmp#energyRecord_energyCosts EnergyConsumption_xsd.tmp#energyRecord
Type energyRecord
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children dataSource, description, energyAmountUnits, energyAmounts, energyCosts, peakDemands
Instance
 
<energyConsumption periodStart="" periodUnits="" revenueMeterIdRef="">
  <dataSource>{0,1}</dataSource>
  <description>{0,1}</description>
  <energyAmountUnits>{1,1}</energyAmountUnits>
  <energyAmounts>{0,1}</energyAmounts>
  <peakDemands>{0,1}</peakDemands>
  <energyCosts>{0,1}</energyCosts>
</energyConsumption>
Attributes
QName Type Use Annotation
periodStart xs:dateTime optional 
Start date of the time period covered by this Energy Consumption record. Use this attribute in conjunction with the PeriodLength attributes of the EnergyAmount elements when defining consecutive billing periods that do not correspond to calendar months. Put the billing days in the PeriodLength attribute.
periodUnits timeUnitEnum optional 
Describes the Units of time for the PeriodLength attribute within the EnergyAmounts.
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="energyRecord" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>This is a placeholder for analysis results.</xs:documentation>
  </xs:annotation>
</xs:element>
Element commonSystemProperties / 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#power_testCondition Common_xsd.tmp#power_unit Common_xsd.tmp#power_unitDesc Common_xsd.tmp#power_fuel Common_xsd.tmp#power_fuelDesc Common_xsd.tmp#power
Type power
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Default Use Annotation
fuel energyClassEnum 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 powerUnitEnum 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="power" 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 commonSystemProperties / operatingScheduleIdRef
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 1
Source
 
<xs:element name="operatingScheduleIdRef" type="xs:IDREF" minOccurs="0" maxOccurs="1">
  <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 commonSystemProperties / zoneLocationIdRef
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="zoneLocationIdRef" 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 commonSystemProperties / revenueMeterIdRef
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="revenueMeterIdRef" 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 commonSystemProperties
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#commonSystemProperties_description CommonSystemProperties_xsd.tmp#commonSystemProperties_annualOperatingHours CommonSystemProperties_xsd.tmp#commonSystemProperties_designEfficiency CommonSystemProperties_xsd.tmp#commonSystemProperties_designInput CommonSystemProperties_xsd.tmp#commonSystemProperties_designOutput CommonSystemProperties_xsd.tmp#commonSystemProperties_energyConsumption CommonSystemProperties_xsd.tmp#commonSystemProperties_maxInput CommonSystemProperties_xsd.tmp#commonSystemProperties_operatingScheduleIdRef CommonSystemProperties_xsd.tmp#commonSystemProperties_zoneLocationIdRef CommonSystemProperties_xsd.tmp#commonSystemProperties_revenueMeterIdRef
Used by
Model
Children annualOperatingHours, description, designEfficiency, designInput, designOutput, energyConsumption, maxInput, operatingScheduleIdRef, revenueMeterIdRef, zoneLocationIdRef
Source
 
<xs:complexType name="commonSystemProperties">
  <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="efficiency" 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="power" 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="power" 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="energyRecord" 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="power" 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="operatingScheduleIdRef" type="xs:IDREF" minOccurs="0" maxOccurs="1">
      <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="zoneLocationIdRef" 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="revenueMeterIdRef" 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>
XML Schema documentation generated by ® XML Editor.