Tiefbau Element - Typ | |
Civil Element Type |
Item | SPF | XML | Change | Description | IFC2x3 to IFC4 |
---|---|---|---|---|
IfcCivilElementType | ADDED |
An IfcCivilElementType is used to define an element specification of an element used within civil engineering works. Civil element types include for different types of element that may be used to represent information for construction works external to a building. IfcCivilElementType's may include:
The specification of the specific types is provided by the inherited attribute IfcElementType.ElementType given as an IfcLabel.
NOTE This is due to the range of choices of element type that are available and their expression in different languages. It is not considered possible to create a reasonably full list of types within an enumeration. It is suggested that selection of the relevant type be drawn from an available 'feature catalog'.
NOTE The IfcCivilElementType has been intruduced as a stub for future extensions of this specification to include an object model for civil engineering works.
HISTORY New entity in IFC4.
# | Attribute | Type | Cardinality | Description | B |
---|---|---|---|---|---|
IfcRoot | |||||
1 | GlobalId | IfcGloballyUniqueId | [1:1] | Assignment of a globally unique identifier within the entire software world. | X |
2 | OwnerHistory | IfcOwnerHistory | [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 |
3 | Name | IfcLabel | [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 |
4 | Description | IfcText | [0:1] | Optional description, provided for exchanging informative comments. | X |
IfcObjectDefinition | |||||
HasAssignments | IfcRelAssigns @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 | |
Nests | IfcRelNests @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). | ||
IsNestedBy | IfcRelNests @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 | |
HasContext | IfcRelDeclares @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. | ||
IsDecomposedBy | IfcRelAggregates @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 | |
Decomposes | IfcRelAggregates @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 | |
HasAssociations | IfcRelAssociates @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 | |
IfcTypeObject | |||||
5 | ApplicableOccurrence | - | This attribute is out of scope for this model view definition and shall not be set. | ||
6 | HasPropertySets | IfcPropertySetDefinition | S[1:?] |
Set | X |
Types | IfcRelDefinesByType @RelatingType | S[0:1] | Reference to the relationship IfcRelDefinedByType and thus to those occurrence objects, which are defined by this type. | ||
IfcTypeProduct | |||||
7 | RepresentationMaps | IfcRepresentationMap | ~L[1:?] | List of unique representation maps. Each representation map describes a block definition of the shape of the product style. By providing more than one representation map, a multi-view block definition can be given. | X |
8 | Tag | - | This attribute is out of scope for this model view definition and shall not be set. | ||
ReferencedBy | IfcRelAssignsToProduct @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 type. | ||
IfcElementType | |||||
9 | ElementType | - | This attribute is out of scope for this model view definition and shall not be set. | ||
IfcCivilElementType |
This element captures re-usable definitions for piers and abutments. Such definitions may be fixed or parametric.
Piers are typically decomposed into piles, footings, and columns, where each may have rebar embedded. Each component may be connected using an element connection relationship, which is required for structural analysis, construction sequencing, and parametric layout.
Parametric layout may be accomplished by using one or more decomposed elements of variable shape connected to other elements of fixed shape.
For components of a single material filling parametric constraints, material definitions may be used. For multiple components, connectivity relationships may be used to anchor elements such that if a dimension changes on one component, any connected components are repositioned and resized accordingly.
In addition to implicit parametric behavior, explicit parameters and formulas may be defined using constraint relationships.
Figure 65 — Bridge pier components |
Type Element Aggregation
The Type Element Aggregation concept applies to this entity as shown in Table 13.
| |||||||||||||||
Table 13 — IfcCivilElementType Type Element Aggregation |
Exchange | ||||
---|---|---|---|---|
Import | O | O | ||
Export | O | O |
Type Axis Geometry
The Type Axis Geometry concept applies to this entity.
For bridge elements that may be parametrically positioned, the Axis representation indicates the path and boundary of how the component may be stretched. To support dynamic layout, either a parametric material association must be defined such as IfcMaterialProfileSet, or an aggregated element must exist having such parametric association and connected to other components along the Axis curve.
Exchange | ||||
---|---|---|---|---|
Import | O | O | ||
Export | O | O |
# | Concept | Model View |
---|---|---|
IfcRoot | ||
Software Identity | Bridge View | |
User Identity | Bridge View | |
Object Ownership | Bridge View | |
IfcTypeObject | ||
Property Sets for Types | Bridge View | |
IfcCivilElementType | ||
Type Element Aggregation | Bridge View | |
Type Axis Geometry | Bridge View |
<xs:element name="IfcCivilElementType" type="ifc:IfcCivilElementType" substitutionGroup="ifc:IfcElementType" nillable="true"/>
<xs:complexType name="IfcCivilElementType">
<xs:complexContent>
<xs:extension base="ifc:IfcElementType"/>
</xs:complexContent>
</xs:complexType>
ENTITY IfcCivilElementType
SUBTYPE OF (IfcElementType);
END_ENTITY;