ETSI TS 103 410-3 V1.1.1 (2017-01)

SmartM2M; Smart Appliances Extension to SAREF; Part 3: Building Domain

DTS/SmartM2M-103410-3-SAREF4BL

General Information

• Status: Published
• Publication Date: 26-Jan-2017
• Technical Committee: SmartM2M - Smart M2M
• Current Stage: 12 - Completion
• Due Date: 01-Feb-2017
• Completion Date: 27-Jan-2017

Standards Content (Sample)

ETSI TS 103 410-3 V1.1.1 (2017-01)






TECHNICAL SPECIFICATION
SmartM2M;
Smart Appliances Extension to SAREF;
Part 3: Building Domain

---------------------- Page: 1 ----------------------
2 ETSI TS 103 410-3 V1.1.1 (2017-01)



Reference
DTS/SmartM2M-103410-3-SAREF4BL
Keywords
data sharing, IoT, M2M, ontology, SAREF,
Smart Appliance
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 410-3 V1.1.1 (2017-01)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 SAREF4BLDG ontology and semantics . 6
4.1 Introduction . 6
4.2 SAREF4BLDG . 7
4.2.1 General overview . 7
4.2.2 Device Taxonomy . 9
4.2.3 Measurements . 12
4.2.4 Device Properties . 13
4.3 Observations about S4BLDG . 20
Annex A (informative): Approach . 21
Annex B (informative): Bibliography . 23
History . 24

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 410-3 V1.1.1 (2017-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
The present document is part 3 of a multi-part deliverable covering SmartM2M; Smart Appliances Extension to
SAREF, as identified below:
Part 1: "Energy Domain";
Part 2: "Environment Domain";
Part 3: "Building Domain".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 410-3 V1.1.1 (2017-01)
1 Scope
The present document presents the SAREF extension for the building domain, based on the ISO 16739 [i.2]
standard (IFC).
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 411: "SmartM2M; Smart Appliances; SAREF extension investigation".
[i.2] ISO 16739:2013: "Industry Foundation Classes (IFC) for data sharing in the construction and
facility management industries".
NOTE: Available at http://www.iso.org/iso/catalogue_detail.htm?csnumber=51622.
[i.3] Industry Foundation Classes (IFC) - Version 4 - Addendum 1. buildingSMART.
NOTE: Available at http://www.buildingsmart-tech.org/ifc/IFC4/Add1/html/.
[i.4] Villazón-Terrazas, B. Method for Reusing and Re-engineering Non-ontological Resources for
Building. Ph.D. Dissertation. Universidad Politécnica de Madrid. 2011.
NOTE: Available at http://oa.upm.es/6338/.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 410-3 V1.1.1 (2017-01)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality
smart appliances: devices, which are used in the household, e.g. for performing domestic work, and which have the
ability to communicate with each other and which can be controlled via Internet
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
HTML Hyper Text Markup Language
IFC Industry Foundation Classes
ISO International Standardization Organisation
OWL Web Ontology Language
OWL-DL Web Ontology Language Description Logic
PROV-O The PROV Ontology RDF Resource Description Format
SAREF Smart Appliances REFerence ontology
TR Technical Report
TS Technical Specification
URI Uniform Resource Identifier
W3C World Wide Web Consortium
WGS84 World Geodetic System 1984
4 SAREF4BLDG ontology and semantics
4.1 Introduction
The present document is a technical specification of SAREF4BLDG, an extension of the SAREF ontology that was
created based on the Industry Foundation Classes (IFC) standard for building information. It should be noted that not
the whole standard has been transformed since it exceeds the scope of this extension, which is limited to devices and
appliances within the building domain.
The IFC specification is developed and maintained by buildingSMART International as its "Data standard" and, since
its version IFC4, it is published as the ISO 16739 [i.2] standard. SAREF4BLDG is meant to enable the (currently
missing) interoperability among various actors (architects, engineers, consultants, contractors, and product component
manufacturers, among others) and applications managing building information involved in the different phases of the
building life cycle (Planning and Design, Construction, Commissioning, Operation,
Retrofitting/Refurbishment/Reconfiguration, and Demolition/Recycling). By using SAREF4BLDG, smart appliances
from manufacturers that support the IFC data model will easily communicate with each other. Towards this aim,
SAREF4BLDG should be used to annotate (or generate) neutral device descriptions to be shared among various
stakeholders.
SAREF4BLDG is an OWL-DL ontology that extends SAREF with 72 classes (67 defined in SAREF4EBLDG and
5 reused from the SAREF and geo ontologies), 179 object properties (177 defined in SAREF4EBLDG and 2 reused
from the SAREF and geo ontologies), and 83 data type properties (82 defined in SAREF4EBLDG and 1 reused from
the SAREF ontology).
SAREF4BLDG focuses on extending the SAREF ontology to include those devices defined by the IFC version 4 -
Addendum 1 [i.3] and to enable the representation of such devices and other physical objects in building spaces.
The prefixes and namespaces used in SAREF4BLDG and along the present document are listed in Table 1.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 410-3 V1.1.1 (2017-01)
Table 1: Prefixes and namespaces used within the SAREF4BLDG ontology
Prefix Namespace
base (s4bldg) https://w3id.org/def/saref4bldg
saref https://w3id.org/saref
geo http://www.w3.org/2003/01/geo/wgs84_pos
owl http://www.w3.org/2002/07/owl
prov http://www.w3.org/ns/prov
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns
rdfs http://www.w3.org/2000/01/rdf-schema
xsd http://www.w3.org/2001/XMLSchema

4.2 SAREF4BLDG
4.2.1 General overview
Figure 1 presents an overview of the classes (only the top levels of the hierarchy) and the properties included in the
SAREF4BLDG extension. As it can be observed the classes s4bldg:Building, s4bldg:BuildingSpace and
s4bldg:PhysicalObject have been declared as subclasses of the class geo:SpatialThing in order to reuse
the conceptualization for locations already proposed by the geo ontology. The modelling of building objects and
building spaces has been adapted from the SAREF ontology; in this sense, the new classes deprecate the
saref:BuildingObject and saref:BuildingSpace classes. In addition, a new class has been created, the
s4bldg:Building class, to represent buildings.
The concepts s4bldg:Building and s4bldg:BuildingSpace are related to each other by means of the
properties s4bldg:hasSpace and s4bldg:isSpaceOf; such properties are defined as inverse properties among
them. These properties might also be used to declare that a s4bldg:BuildingSpace has other spaces belonging to
the class s4bldg:BuildingSpace.
The relationship between building spaces and devices and building objects has also been transferred and generalized
from the SAREF ontology. In this regard, a s4bldg:BuildingSpace can contain (represented by the property
s4bldg:contains) individuals belonging to the class s4bldg:PhysicalObject. This generalization has been
implemented in order to support building spaces to contain both building objects and devices. Accordingly, the classes
s4bldg:BuildingObject and saref:Device are declared as subclasses of s4bldg:PhysicalObject.
Finally, the class representing building devices, namely s4bldg:BuildingDevice, is defined as a subclass of both
saref:Device and s4bldg:BuildingObject. This class is a candidate for replacing the
saref:BuildingRelated class.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 410-3 V1.1.1 (2017-01)

Figure 1: General overview of the top levels of the SAREF4BLDG extension
Table 2 summarizes the restrictions that characterize a s4bldg:Building.
Table 2: Restrictions of the s4bldg:Building class
Property Definition
geo:location only geo:SpatialThing The location of a building is represented only by instances
of geo:SpatialThing.
s4bldg:hasSpace only s4bldg:BuildingSpace
A building has spaces represented only by instances of
s4bldg:BuildingSpace.

Table 3 summarizes the restrictions that characterize a s4bldg:BuildingSpace.
Table 3: Restrictions of the s4bldg:BuildingSpace class
Property Definition
s4bldg:contains only s4bldg:PhysicalObject
A building space contains entities represented only by
instances of s4bldg:PhysicalObject.
s4bldg:hasSpace only s4bldg:BuildingSpace
A building has spaces represented only by instances of
s4bldg:BuildingSpace.
s4bldg:isSpaceOf only (s4bldg:Building or A building is spaces of entities represented only by
s4bldg:BuildingSpace) instances of the classes s4bldg:Building or
s4bldg:BuildingSpace.

Table 4 summarizes the restrictions that characterize a s4bldg:PhysicalObject.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 410-3 V1.1.1 (2017-01)
Table 4: Restrictions of the s4bldg:PhysicalObject class
Property Definition
s4bldg:contains only s4bldg:PhysicalObject
A physical object contains entities represented only by
instances of s4bldg:PhysicalObject.
geo:location only geo:SpatialThing The location of a physical object is represented only by
instances of geo:SpatialThing.
s4bldg:isContained only (s4bldg:Building or A physical object is contained in entities represented only
s4bldg:BuildingSpace) by instances of the classes s4bldg:Building or
s4bldg:BuildingSpace.

4.2.2 Device Taxonomy
The main contribution of this extension is the representation of the devices defined in the IFC standard and their
connections to SAREF. In this sense, a hierarchy consisting in 62 classes has been created taking into account the subset
of the IFC hierarchy related to devices, as defined in the buildingSMART documentation (http://www.buildingsmart-
tech.org/ifc/IFC4/Add1/html/annex/annex-c/common-use-definitions/all.htm), and adding several classes to clarify its
categorization. The device classes are organized into 6 hierarchical levels that, for the sake of clarity, will be displayed
in Figure 2 and Figure 3.
Figure 2 shows the first five levels of the hierarchy. Since transport elements (s4bldg:TransportElement) and
vibration isolations (s4bldg:VibrationIsolation) are not classified under IFC elements, they belong directly
to the class s4bldg:Device. The building elements are divided into s4bldg:ShadingDevice and
s4bldg:DistributionDevice. In fact, most of the device types included in IFC belong to the distribution
device category which contains the classes s4bldg:DistributionControlDevice and
s4bldg:DistributionFlowDevice. The hierarchy under the s4bldg:DistributionFlowDevice is
depicted in Figure 3.
As can be observed in Figure 2, some classes defined in SAREF4BLDG are also defined in the SAREF ontology. More
precisely, this occurs in the classes s4bldg:Actuator and s4bldg:Sensor that extend the classes
saref:Actuator and saref:Sensor, respectively. This decision has been taken because in the SAREF4BLDG
extension these concepts refer to specific sensors and actuators that are placed in or related to buildings.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 410-3 V1.1.1 (2017-01)


Figure 2: Device hierarchy in SAREF4BLDG (Part 1)
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 410-3 V1.1.1 (2017-01)


Figure 3: Device hierarchy in SAREF4BLDG (Part 2)
For each class extracted from the IFC specification, rdfs:label and rdfs:comment annotations have been
generated including the identifier and an excerpt of the definition provided in the IFC online documentation. In
addition, provenance information has been included using the PROV-O ontology (https://www.w3.org/TR/prov-o/),
which has been published by the W3C as recommendation. In our case, the property prov:hadPrimarySource is
used to link each class with:
(a) the online document in IFC describing the concept; and
(b) the online document in IFC describing the properties defined for such concept.
It should be noted that properties are not specified in IFC for all the concepts but just for those representing particular
devices. That is, there is no description of properties for the following general classes:
- s4bldg:EnergyConversionDevice, s4bldg:FlowController, s4bldg:FlowMovingDevice,
s4bldg:FlowStorageDevice, s4bldg:FlowTerminal, and s4bldg:FlowTreatmentDevice.

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 410-3 V1.1.1 (2017-01)
In addition, the classes created in this extension have been related to the ifcOWL ontology
(https://w3id.org/ifc/IFC4_ADD1) when possible. This relation has been declared by means of the annotation property
rdfs:seeAlso from the SAREF4BLDG classes to the ifcOWL ones.
Listing 1 includes an excerpt of the ontology in the Turtle syntax that shows an example of a class including the
annotations from the IFC specification, provenance references to the IFC class and property definition, and the mapping
to the corresponding ifcOWL concept.
### Class definition
s4bldg:Compressor rdf:type owl:Class ;
rdfs:label "Compressor"@en ;
rdfs:subClassOf s4bldg:FlowMovingDevice ;
rdfs:comment "A compressor is a device that compresses a fluid typically used
in a refrigeration circuit."@en ;
### Provenance information for class definition
prov:hadPrimarySource schema/ifchvacdomain/lexical/ifccompressor.htm> ;
### Provenance information for class properties
prov:hadPrimarySource schema/ifchvacdomain/pset/pset_compressortypecommon.htm> ;
### Mapping to ifcOWL classes
 rdfs:seeAlso .

Listing 1: Class definition example including documentation, mappings and provenance information
4.2.3 Measurements
Measurements are depicted in Figure 4. This model represents an n-ary pattern that allows users to relate measurements
for different properties that are measured in different units. That is, the saref:Measurement class aims at
describing a measurement of a physical quantity (using the saref:hasValue property) for a given
saref:Property and according to a given saref:UnitOfMeasure.
This pattern enables to differentiate between properties and the measurements made for such properties and to store
measurements for a concrete property in different units of measurement.
Furthermore, it allows adding a timestamp (using the saref:hasTimeStamp property) to identify when the
measurement applies to the property, which can be used either for single measurements or for series of measurements
(e.g. measurement streams).
It is worth noting that this modelling was included in SAREF2.0 after the SAREF4BLDG extension was developed.
This pattern was first included in the SAREF4ENVI and SAREF4BLDG extensions and then proposed to be
extrapolated to SAREF 2.0; this explains why the prefix used for this part of the model refers to SAREF instead of to
SAREF4BLDG. However, as its origin is the SAREF4ENVI and SAREF4BLDG extensions requirements and
modellings, the explanations are kept in the present document.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 410-3 V1.1.1 (2017-01)

Figure 4: Measurement model
Table 5 summarizes the restrictions that characterize a saref:Measurement.
Table 5: Restrictions of the saref:Measurement class
Property Definition
saref:hasTimestamp only xsd:dateTime The timestamp of a measurement is represented only by
xsd:dateTime.
saref:hasValue exactly 1 xsd:float A measurement should have exactly one value represented using
xsd:float.
saref:hasValue only xsd:float The value of a measurement is represented only by xsd:float.
saref:isMeasuredIn exactly 1 saref:UnitOfMeasure A measurement should have exactly one unit of measurement
which should be instance of saref:UnitOfMeasure.
saref:isMeasuredIn only saref:UnitOfMeasure The unit of measurement of a measurement is represented only
by instances of the class saref:UnitOfMeasure.
saref:relatesToProperty exactly 1 saref:Property A measurement should be related exactly to one property which
should be instance of saref:Property.
saref:relatesToProperty only saref:Property
The property to which a measurement is related to is represented
only by instances of the class saref:Property.

4.2.4 Device Properties
In the SAREF4BLDG extension 179 object properties (177 defined in SAREF4EBLDG and 2 reused from the SAREF
and geo ontologies) and 83 datatype properties (82 defined in SAREF4EBLDG and 1 reused from the SAREF
ontology) have been included. 172 out the 179 object properties and 81 out of the 83 datatype properties have been
created according to the IFC specification of properties for devices.
For each of the created object and datatype properties, their documentation from IFC has been attached as
documentation, including information about their use, such as the expected units of measurement.
The naming of the created object and datatype properties is consistent with the naming used in IFC. More precisely, the
names of the properties in the ontology are the names assigned in IFC transformed into Camel Case starting with
lowercase. For example, the property "IdealShaftPower" (extracted from http://www.buildingsmart-
tech.org/ifc/IFC4/Add1/html/schema/ifchvacdomain/pset/pset_compressortypecommon.htm) has been transformed into
the object property s4bldg:idealShaftPower.
Listing 2 includes an excerpt of the ontology in the Turtle syntax that shows an example of an object property and a
datatype property including the annotations from the IFC specification.
ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 410-3 V1.1.1 (2017-01)
### Object property definition example
s4bldg:idealShaftPower rdf:type owl:ObjectProperty ;
 rdfs:comment "Compressor shaft power under ideal conditions. Usually measured
in Watts (W, J/s)."@en ;
 rdfs:label "ideal shaft power"@en .
### Datatype property definition example
s4bldg:hasHotGasBypass rdf:type owl:DatatypeProperty ;
 rdfs:range xsd:boolean ;
 rdfs:comment "Whether or not hot gas bypass is provided for the compressor. TRUE
= Yes, FALSE = No."@en ;
 rdfs:label "has hot gas bypass"@en .

Listing 2: Property definition example including documentation
Table 6 shows the list of object properties extracted from IFC and the classes for which each property might be applied.
Table 6: List of object properties extracted from IFC and
the classes for which the properties are defined
Object property Class(es)
s4bldg:airFlowRateRangeMax s4bldg:DuctSilencer
s4bldg:Coil
s4bldg:airFlowRateRangeMin s4bldg:DuctSilencer
s4bldg:Coil
s4bldg:ambientDesignDryBulbTemperature s4bldg:CoolingTower
s4bldg:ambientDesignWetBulbTemperature s4bldg:CoolingTower
s4bldg:audioVolume s4bldg:AudioVisualAppliance
s4bldg:basinReserveVolume s4bldg:CoolingTower
s4bldg:bladeThickness s4bldg:Damper
s4bldg:bodyMass s4bldg:SpaceHeater
s4bldg:capacityWeight s4bldg:TransportElement
s4bldg:closeOffRating s4bldg:Damper
s4bldg:Valve
s4bldg:coilLength s4bldg:CooledBeam
s4bldg:coilWidth s4bldg:CooledBeam
s4bldg:colorTempeature s4bldg:Lamp
s4bldg:compressorSpeed s4bldg:Compressor
s4bldg:connectionSize s4bldg:Pump
s4bldg:contributedLuminousFlux s4bldg:Lamp
s4bldg:coverLength s4bldg:Interceptor
s4bldg:coverWidth s4bldg:Interceptor
s4bldg:effectiveCapacity s4bldg:Tank
s4bldg:electricGeneratorEfficiency s4bldg:ElectricGenerator
s4bldg:electricMotorEfficiency s4bldg:ElectricMotor
s4bldg:externalSurfaceArea s4bldg:Evaporator
s4bldg:Condenser
s4bldg:faceArea s4bldg:Damper
s4bldg:finalResistance s4bldg:Filter
s4bldg:firstCurvatureRadius s4bldg:Tank
s4bldg:flowCoefficient s4bldg:Valve
s4bldg:flowRateRangeMax s4bldg:Pump
s4bldg:Filter
s4bldg:flowRateRangeMin s4bldg:Pump
s4bldg:Filter
s4bldg:flowResistanceRangeMax s4bldg:Pump
s4bldg:flowResistanceRangeMin s4bldg:Pump
s4bldg:foulingFactor s4bldg:TubeBundle
ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 103 410-3 V1.1.1 (2017-01)
Object property Class(es)
s4bldg:frameDepth s4bldg:Damper
s4bldg:frameThickness s4bldg:Damper
s4bldg:heatExchangeArea s4bldg:EvaporativeCooler
s4bldg:heatTransferSurfaceArea s4bldg:Boiler
s4bldg:height s4bldg:VibrationIsolator
s4bldg:horizontalSpacing s4bldg:TubeBundle
s4bldg:hydraulicDiameter s4bldg:DuctSilencer
s4bldg:idealCapacity s4bldg:Compressor
s4bldg:idealShaftPower s4bldg:Compressor
s4bldg:imaginaryImpedanceRatio s4bldg:Transformer
s4bldg:impellerDiameter s4bldg:Compressor
s4bldg:initialResistance s4bldg:Filter
s4bldg:inletConnectionSize s4bldg:Interceptor
s4bldg:inLineRowSpacing s4bldg:TubeBundle
s4bldg:insideDiameter s4bldg:TubeBundle
s4bldg:internalRefrigerantVolume s4bldg:Evaporator
s4bldg:Condenser
s4bldg:internalSurfaceArea s4bldg:Evaporator
s4bldg:Condenser
s4bldg:internalWaterVolume s4bldg:Evaporator
s4bldg:Condenser
s4bldg:isolatorCompressibility s4bldg:VibrationIsolator
s4bldg:isolatorStaticDeflection s4bldg:VibrationIsolator
s4bldg:lampMaintenanceFactor s4bldg:Lamp
s4bldg:leakageFullyClosed s4bldg:Damper
s4bldg:length s4bldg:DuctSilencer
s4bldg:TubeBundle
s4bldg:liftElevationDifference s4bldg:CoolingTower
s4bldg:lightEmitterNominalPower s4bldg:Lamp
s4bldg:limitingTerminalSize s4bldg:ProtectiveDeviceTrippingUnit
s4bldg:lockedRotorCurrent s4bldg:ElectricMotor
s4bldg:maximumAirFlowRate s4bldg:Damper
s4bldg:maximumApparentPower s4bldg:Transformer
s4bldg:maximumPartLoadRatio s4bldg:Compressor
s4bldg:maximumPowerOutput s4bldg:ElectricGenerator
s4bldg:ElectricMotor
s4bldg:maximumSupportedWeight s4bldg:VibrationIsolator
s4bldg:maximumWorkingPressure s4bldg:Damper
s4bldg:minimunPartLoadRatio s4bldg:Compressor
s4bldg:netPositiveSuctionHead s4bldg:Pump
s4bldg:nominalAirFlowRate s4bldg:Humidifier
s4bldg:Fan
s4bldg:Damper
s4bldg:nominalBodyDepth s4bldg:Interceptor
s4bldg:nominalBodyLength s4bldg:Interceptor
s4bldg:nominalBodyWidth s4bldg:Interceptor
s4bldg:nominalCapacity s4bldg:Tank
s4bldg:Chiller
...