Navigation
Navigate Navigate Navigate Navigate Navigate Navigate Navigate Navigate Navigate Navigate Navigate

IFCSHAREDBLDGSERVICEELEMENTS

The data model consists of the following:

30  Entities
Enumerations

The IfcSharedBldgServiceElements schema in the interoperability layer defines basic concepts required for interoperability primarily between Building Service domain extensions, notably IfcHvacDomain, IfcPlumbingFireProtectionDomain, IfcElectricalDomain and IfcBuildingControlsDomain. This schema includes concepts such as basic type and occurrence definitions for flow and distribution systems and fundamental properties commonly used in building service scenarios (such as fluid-flow properties, electrical properties, space thermal properties, etc.)

The IfcSharedBldgServiceElements schema heavily utilizes the concepts of type, occurrence and performance, as shown in Figure 1 below. Types are specializations of IfcDistributionElementType while occurrences are specializations of IfcDistributionElement. Generally, only types are further elaborated in the domain schemas to provide the necessary specificity unique to each type. A third theme, defined in the IfcControlExtension schema, relates to the performance characteristics of an occurrence utilizing instances of the IfcPerformanceHistory entity.

type, occurrence and performance history concepts
Figure 1: A type can have zero or many occurrences. Each occurrence can have many performance history entities associated with it, allowing data that is specific to a certain phase of the lifecycle to be captured and maintained throughout the life of the dataset.

The IfcSharedBldgServiceElements schema specializes building services concepts symmetrically for occurrences and types, with the primary functional role of the entity determining its classification into the following generic concepts:

Refer to the domain schemas where types are further elaborated utilizing the PredefinedType enumerations for examples of the range of supported concepts within these broad classifications. If a new type is needed within this classification, extend using the ElementType attribute. However, if a completely new concept is required that does not fit within this classification, utilize instances of the generic IfcDistributionElementType and IfcDistributionElement entities for the type/occurrence objects as needed.

Occurrences in a distribution system are typically coupled together using instances of IfcDistributionPort. This is also where concepts such as mass-flow properties (using instances of IfcFluidFlowProperties) are applied based on performance characteristics. Refer to the IfcDistributionPort documentation within this schema for further elaboration on coupling together components in a distribution system and tracking the flow characteristics across the port boundaries.

HISTORY This schema has been significantly modified in IFC Release 2x2. Refer to the change log and issues resolution database for details.

Interfaced schemas (15):

REFERENCE FROM IFCACTORRESOURCE
USE FROM IFCCONTROLEXTENSION
REFERENCE FROM IFCDATETIMERESOURCE
REFERENCE FROM IFCEXTERNALREFERENCERESOURCE
REFERENCE FROM IFCGEOMETRICCONSTRAINTRESOURCE
REFERENCE FROM IFCGEOMETRYRESOURCE
( IfcAxis2Placement3D,
IfcCurve,
IfcCircle,
IfcEllipse,
IfcPolyline,
IfcLine,
IfcCompositeCurve,
IfcTrimmedCurve,
IfcBezierCurve);
REFERENCE FROM IFCKERNEL
( IfcRelConnects,
IfcPropertySetDefinition);
REFERENCE FROM IFCMATERIALPROPERTYRESOURCE
REFERENCE FROM IFCMATERIALRESOURCE
( IfcMaterial);
REFERENCE FROM IFCMEASURERESOURCE
( IfcNamedUnit,
IfcElectricVoltageMeasure,
IfcFrequencyMeasure,
IfcElectricCurrentMeasure,
IfcLabel,
IfcPowerMeasure,
IfcPositiveRatioMeasure,
IfcText,
IfcBoolean,
IfcThermodynamicTemperatureMeasure,
IfcIdentifier,
IfcDerivedMeasureValue,
IfcLinearVelocityMeasure,
IfcPressureMeasure);
REFERENCE FROM IFCPRESENTATIONAPPEARANCERESOURCE
( IfcNullStyle);
REFERENCE FROM IFCPRODUCTEXTENSION
( IfcDistributionElement,
IfcPort,
IfcDistributionElementType);
REFERENCE FROM IFCPROFILERESOURCE
REFERENCE FROM IFCPROPERTYRESOURCE
REFERENCE FROM IFCTIMESERIESRESOURCE
( IfcTimeSeries);

Entities (30):

Go to Diagram 1 IfcDistributionChamberElement
Go to Diagram 2 IfcDistributionChamberElementType
Go to Diagram 1 IfcDistributionControlElement
Go to Diagram 2 IfcDistributionControlElementType
Go to Diagram 1 IfcDistributionFlowElement
Go to Diagram 2 IfcDistributionFlowElementType
Go to Diagram 3 IfcDistributionPort
Go to Diagram 5 IfcElectricalBaseProperties
Go to Diagram 1 IfcEnergyConversionDevice
Go to Diagram 2 IfcEnergyConversionDeviceType
Go to Diagram 5 IfcEnergyProperties
Go to Diagram 1 IfcFlowController
Go to Diagram 2 IfcFlowControllerType
Go to Diagram 1 IfcFlowFitting
Go to Diagram 2 IfcFlowFittingType
Go to Diagram 1 IfcFlowMovingDevice
Go to Diagram 2 IfcFlowMovingDeviceType
Go to Diagram 1 IfcFlowSegment
Go to Diagram 2 IfcFlowSegmentType
Go to Diagram 1 IfcFlowStorageDevice
Go to Diagram 2 IfcFlowStorageDeviceType
Go to Diagram 1 IfcFlowTerminal
Go to Diagram 2 IfcFlowTerminalType
Go to Diagram 1 IfcFlowTreatmentDevice
Go to Diagram 2 IfcFlowTreatmentDeviceType
Go to Diagram 4 IfcFluidFlowProperties
Go to Diagram 1 IfcRelFlowControlElements
Go to Diagram 5 IfcSoundProperties
Go to Diagram 5 IfcSoundValue
Go to Diagram 3 IfcSpaceThermalLoadProperties

Enumerations (8):

Go to Diagram 2 IfcDistributionChamberElementTypeEnum
Go to Diagram 5 IfcElectricCurrentEnum
Go to Diagram 5 IfcEnergySequenceEnum
Go to Diagram 3 IfcFlowDirectionEnum
Go to Diagram 4 IfcPropertySourceEnum
Go to Diagram 5 IfcSoundScaleEnum
Go to Diagram 3 IfcThermalLoadSourceEnum
Go to Diagram 3 IfcThermalLoadTypeEnum