IfcCivilElement

Natural language names
deTiefbau Element
enCivil Element
Change log
ItemSPFXMLChangeDescription
IFC2x3 to IFC4
    IfcCivilElementADDED
IFC4 to IFC4 ADD1
    IfcCivilElement
      HasCoveringsADDED
IFC4x1 to IFC4x2
    IfcCivilElement
      PositionedFromADDED
Semantic definitions at the entity
Entity definition

An IfcCivilElement is a generalization of all elements within a civil engineering works. It includes in particular all occurrences of typical linear construction works, such as road segments, bridge segments, pavements, etc. Depending on the context of the construction project, included building work, such as buildings or factories, are represented as a collection of IfcBuildingElement's, distribution systems, such as piping or drainage, are represented as a collection of IfcDistributionElement's, and other geographic elements, such as trees, light posts, traffic signs etc. are represented as IfcGeographicElement's.

NOTE  The IfcCivilElement has been intruduced as a stub for future extensions of this specification to include an object model for civil engineering works.

Civil elements are typically horizontally organized using a spatial structure expressed by spatial zones, therefore IfcCivilElement is spatially contained by default within an IfcSpatialZone.

HISTORY  New entity in IFC4.
Inherited definitions from supertypes
Entity inheritance IfcElement IfcProduct IfcObject IfcObjectDefinition IfcRoot
Attribute inheritance
#AttributeTypeCardinalityDescriptionB
IfcRoot
1GlobalIdIfcGloballyUniqueId[1:1] Assignment of a globally unique identifier within the entire software world. X
2OwnerHistoryIfcOwnerHistory[0:1] Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,
NOTE  only the last modification in stored - either as addition, deletion or modification.
X
3NameIfcLabel[0:1] Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule. X
4DescriptionIfcText[0:1] Optional description, provided for exchanging informative comments.X
IfcObjectDefinition
HasAssignmentsIfcRelAssigns
@RelatedObjects
S[0:?]Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups.X
NestsIfcRelNests
@RelatedObjects
S[0:1]References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only).
IsNestedByIfcRelNests
@RelatingObject
S[0:?]References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types). X
HasContextIfcRelDeclares
@RelatedDefinitions
S[0:1]References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object.
IsDecomposedByIfcRelAggregates
@RelatingObject
S[0:?]References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts). X
DecomposesIfcRelAggregates
@RelatedObjects
S[0:1]References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only). X
HasAssociationsIfcRelAssociates
@RelatedObjects
S[0:?]Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification.X
IfcObject
5ObjectType- This attribute is out of scope for this model view definition and shall not be set.
IsTypedByIfcRelDefinesByType
@RelatedObjects
S[0:1]Set of relationships to the object type that provides the type definitions for this object occurrence. The then associated IfcTypeObject, or its subtypes, contains the specific information (or type, or style), that is common to all instances of IfcObject, or its subtypes, referring to the same type. X
IsDefinedByIfcRelDefinesByProperties
@RelatedObjects
S[0:?]Set of relationships to property set definitions attached to this object. Those statically or dynamically defined properties contain alphanumeric information content that further defines the object. X
IfcProduct
6ObjectPlacementIfcObjectPlacement[0:1] Placement of the product in space, the placement can either be absolute (relative to the world coordinate system), relative (relative to the object placement of another product), or constraint (e.g. relative to grid axes). It is determined by the various subtypes of IfcObjectPlacement, which includes the axis placement information to determine the transformation for the object coordinate system.X
7RepresentationIfcProductRepresentation[0:1] Reference to the representations of the product, being either a representation (IfcProductRepresentation) or as a special case a shape representations (IfcProductDefinitionShape). The product definition shape provides for multiple geometric representations of the shape property of the object within the same object coordinate system, defined by the object placement.X
ReferencedByIfcRelAssignsToProduct
@RelatingProduct
S[0:?]Reference to the IfcRelAssignsToProduct relationship, by which other products, processes, controls, resources or actors (as subtypes of IfcObjectDefinition) can be related to this product.X
IfcElement
8TagIfcIdentifier[0:1] The tag (or label) identifier at the particular instance of a product, e.g. the serial number, or the position number. It is the identifier at the occurrence level.X
ConnectedToIfcRelConnectsElements
@RelatingElement
S[0:?]Reference to the element connection relationship. The relationship then refers to the other element to which this element is connected to.
HasOpeningsIfcRelVoidsElement
@RelatingBuildingElement
S[0:?]Reference to the IfcRelVoidsElement relationship that creates an opening in an element. An element can incorporate zero-to-many openings. For each opening, that voids the element, a new relationship IfcRelVoidsElement is generated. X
ConnectedFromIfcRelConnectsElements
@RelatedElement
S[0:?]Reference to the element connection relationship. The relationship then refers to the other element that is connected to this element. X
ContainedInStructureIfcRelContainedInSpatialStructure
@RelatedElements
S[0:1]Containment relationship to the spatial structure element, to which the element is primarily associated. This containment relationship has to be hierachical, i.e. an element may only be assigned directly to zero or one spatial structure.
PositionedFromIfcRelPositions
@RelatingElement
S[0:1]Indicates a constrained placement, where the ObjectPosition must match positioning defined according to the referenced positioning element.X
IfcCivilElement
Definitions applying to Bridge View

 Instance diagram


For bridges, this entity is used to represent supporting ground structures that perform multiple functions, including abutments and piers. Elements are decomposed according to connectivity, including construction joints. Reinforcing may be indicated within inner elements such as footings, columns, members, and walls (see documentation at corresponding elements for usage), but not directly within IfcCivilElement; such reinforcing should reflect how it is to be placed at time of construction such that rebar connecting between elements is projected out of the element where it is initially placed.

Abutments and piers are placed relative to the horizontal alignment curve (NOT the vertical alignment curve), with components placed according to Cartesian placement within. This reflects the positioning indicated on the plans, where all dimension lines are based on Cartesian positioning relative to the position and orientation of the station along the horizontal alignment curve.

Bridge abutment plans

Figure 1 — Bridge abutment plans

For the abutment shown in Figure 1, the wing walls and cheek walls are modeled using IfcWall (an arbitrarily shaped wall), with geometry represented by IfcExtrudedAreaSolidTapered, and interconnected with construction joints using IfcRelConnectsElements.

The foundation of the abutment shown consists of a single IfcFooting with shape defined by IfcExtrudedAreaSolid of an IfcArbitraryClosedProfileDef extruded upwards. Each pile is modeled using a separate IfcPile with shape defined using IfcExtrudedAreaSolid of an IfcIShapeProfileDef extruded upwards, and is connected to the footing using IfcRelConnectsElements where RelatingElement refers to the pile. The footing connects to each wall using IfcRelConnectsElements where RelatingElement refers to the footing.

Drainage piping is modeled using IfcPipeSegment assigned to IfcDistributionSystem of type DRAINAGE with geometry using IfcSweptAreaSolid of IfcCircleHollowProfileDef. Conduit for wire is modeled using IfcCableCarrierSegment with geometry using IfcSweptAreaSolid of IfcCircleHollowProfileDef.

Bridge abutment model

Figure 2 — Bridge abutment model

Figure 2 illustrates a 3D rendering of an abutment.

While it is possible to represent such abutment in other ways (e.g. a single unified object with BREP or tessellated geometry), the particular composition used was chosen to indicate detail required for construction.

Bridge pier plans

Figure 3 — Bridge pier plans

As shown in Figure 3, Piers are modelled as a combination of interconnected components, typically comprising IfcPile, IfcFooting, IfcColumn, and IfcMember. Each of these components are connected to the next using IfcRelConnectsElements or a subtype, where RelatingElement refers to the anchoring component and RelatedElement refers to component attached, which also implies the order of construction. The IfcRelConnectsElements relationship implies construction joints (no specific fasteners or adhesion other than rebar); otherwise specific connectivity is indicated using the IfcRelConnectsWithRealizingElements subtype instead

Bridge pier model

Figure 4 — Bridge pier model

For this particular example, the each pile is modeled using IfcPile. The concrete geometry is represented by IfcExtrudedAreaSolid extruded upwards (in the +Z direction) with the cross-section defined by IfcCircleProfileDef. The footing is modeled using IfcFooting. The concrete geometry is represented by IfcExtrudedAreaSolid extruded towards the alignment curve with the cross-section defined by IfcArbitraryClosedProfileDef to accommodate the notch used for the construction joint.

The column (the section above the footing between construction joints) is modeled using IfcColumn (as an axial compression member). The concrete geometry is represented by IfcExtrudedAreaSolid extruded towards the alignment curve with the cross-section defined by IfcArbitraryClosedProfileDef to accommodate the notches for construction joint, consisting of IfcIndexedPolyCurve.

The top section is modeled using IfcMember (as an arbitrary load-carrying member) and with its base at a vertical offset (+Z) and zero horizontal offset. The concrete geometry is represented by IfcExtrudedAreaSolid extruded towards the alignment curve with the cross-section defined by IfcArbitraryClosedProfileDef to accommodate the irregular shape, consisting of IfcIndexedPolyCurve.

The architectural treatment is modeled using IfcCovering, with IfcExtrudedAreaSolid of IfcRectangleProfileDef indicating the shape and the rock texture indicated using IfcStyledItem, IfcSurfaceStyle, IfcSurfaceStyleWithTextures, and IfcImageTexture.

The drainage pipes are modeled using IfcPipeSegment, with IfcExtrudedAreaSolid of IfcCircleHollowProfileDef indicating the shape. The drain above is modeled using IfcWasteTerminal. All piping components belong to an IfcDistributionSystem of predefined type STORMWATER, and have ports at each end indicating connectivity using IfcDistributionPort. Ports are connected according to flow using IfcRelConnectsPorts.

This separate modeling associated with the construction joints facilitates connectivity of the supported elements in fashion similar to that used for structural analysis and construction sequencing.

Concept usage

Object Typing

The Object Typing concept applies to this entity as shown in Table 8.

Type
IfcCivilElementType

Table 8 — IfcCivilElement Object Typing

Exchange
Import O
Export O


Element Decomposition

The Element Decomposition concept applies to this entity as shown in Table 9.

RelatedObjectsDescription
IfcWallCheek walls and wing walls of abutments
IfcMemberTop segments of piers supporting bridge girder(s)
IfcColumnVertical segments of piers separated by construction joints
IfcFootingFootings of piers and abutments
IfcPilePiles of piers and abutments
IfcPipeSegmentPipe segments to support drainage or de-icing
IfcPipeFittingPipe fittings to support drainage or de-icing
IfcCableCarrierSegmentConduit segments to support lighting or signage
IfcCableCarrierFittingConduit fittings to support lighting or signage
IfcCoveringArchitectural panels

Table 9 — IfcCivilElement Element Decomposition

Abutments are typically decomposed into piles, footings, walls (outer cheek wall and wing walls), and mechanical fasteners (bearings).

Piers are typically decomposed into piles, footings, columns (separate instances according to construction joints), a member (for top portion that spans out to support the bridge deck), and mechanical fasteners (bearings).

In addition to structural elements, such elements may contain pipe segments and fittings for piping used for drainage or de-icing chemicals, and cable carrier segments and fittings for electrical conduit.

Bridge abutment components

Figure 157 — Bridge abutment components

Exchange
Import R
Export R


Element Positioning

The Element Positioning concept applies to this entity as shown in Table 10.

PlacementTransformDescription
HORIZONTALPLACEPiers and abutments are always placed relative to the horizontal alignment curve and are not transformed.

Table 10 — IfcCivilElement Element Positioning

Exchange
Import O
Export O


Path Connectivity

The Path Connectivity concept applies to this entity as shown in Table 11.

RelatedElementDescription
IfcMechanicalFastenerConnection from pier or abutment to bearing(s)

Table 11 — IfcCivilElement Path Connectivity

Exchange
Import O
Export O


Product Assignment

The Product Assignment concept applies to this entity as shown in Table 12.

TypeDescription
IfcStructuralCurveMemberIdealized representation(s) of element for structural analysis of piers with constant cross-section.
IfcStructuralSurfaceMemberVaryingIdealized representation(s) of element for structural analysis of piers with varying cross-section.
IfcTaskTasks assigned to bridge components indicating applicable construction phases

Table 12 — IfcCivilElement Product Assignment

Exchange
Import O R
Export O R


Concept inheritance

#ConceptModel View
IfcRoot
Software IdentityBridge View
User IdentityBridge View
Object OwnershipBridge View
IfcObject
Property Sets for ObjectsBridge View
IfcElement
Element Occurrence AttributesBridge View
Product Local PlacementBridge View
IfcCivilElement
Object TypingBridge View
Element DecompositionBridge View
Element PositioningBridge View
Path ConnectivityBridge View
Product AssignmentBridge View
Formal representations
XSD Specification
 <xs:element name="IfcCivilElement" type="ifc:IfcCivilElement" substitutionGroup="ifc:IfcElement" nillable="true"/>
 <xs:complexType name="IfcCivilElement">
  <xs:complexContent>
   <xs:extension base="ifc:IfcElement"/>
  </xs:complexContent>
 </xs:complexType>
EXPRESS Specification
ENTITY IfcCivilElement
 SUBTYPE OF (IfcElement);
END_ENTITY;

Link to EXPRESS-G diagram EXPRESS-G diagram

Link to this page  Link to this page