Annex E

Examples

This annex contains examples that implement this specification. Due to ongoing changes in the base IFC4.3 specification, alignment examples could contain errors. Please let us know and we will attempt to fix them.

Sprint 1.1

Prerequisities

• none.

Duration

Usages

1. Project Unit Assignment
   1. at least two units
   2. a LENGTHUNIT and a PLANEANGLEUNIT (regardless of SI unit or conversion based)
2. Project Representation Context
   1. at least one of these should be defined:
      1. Model in 3D
      2. Plan in 2D
3. Project Declaration
   1. at least one of these should be declared:
      1. IfcProjectLibrary
      2. IfcPropertySetTemplate
      3. IfcTypeObject
      4. IfcActor
      5. IfcControl
      6. IfcGroup
      7. IfcProcess
      8. IfcResource

• Project Units Table 12
• Project Representation Context Table 13
• Project Declaration Table 14

Sprint 1.2

Prerequisities

• Sprint 1.1

Duration

Usages

1. Project Classification Information
   1. The IfcProject shall associate IfcClassification with non-empty Source and Name attributes (content of the attributes is irrelevant to the check at this stage)
2. Spatial Decomposition
   1. There shall be either an IfcSite or an IfcFacility (with subtypes irrelevant to the check) aggregated in the IfcProject. Observe the NOTE in the documentation.

1. Project Global Positioning - scenario Georef_A
   1. IfcMapConversion or IfcMapConversionScaled is used (attributes' values are irrelevant).
   2. one of these shall be true:
      1. IfcProjectedCRS.Name shall begin with EPSG: and be followed by 4 or 5 digits (actual numbers are irrelevant to the checker).
      2. IfcProjectedCRS.HasWellKnownTextRepresentation.WellKnownText shall be non-empty.
2. Project Global Positioning Geographic - scenario Georef_B
   1. IfcRigidOperation is used
      1. 3rd and 4th attributes' type shall be IfcPlaneAngleMeasure
   2. one of these shall be true:
      1. IfcGeographicCRS.Name shall begin with EPSG: and be followed by 4 or 5 digits (actual numbers are irrelevant to the checker).
      2. IfcGeographicCRS.HasWellKnownTextRepresentation.WellKnownText shall be non-empty.
3. Project Global Positioning Mapped - scenario Georef_C
   1. IfcRigidOperation is used
      1. 3rd and 4th attributes' type shall be IfcLengthMeasure
   2. one of these shall be true:
      1. IfcProjectedCRS.Name shall begin with EPSG: and be followed by 4 or 5 digits (actual numbers are irrelevant to the checker).
      2. IfcProjectedCRS.HasWellKnownTextRepresentation.WellKnownText shall be non-empty.

Sprint 1.3

Prerequisities

• Sprint 1.1 and
• Sprint 1.2.

Duration

Usages

1. Project Document Information
   1. The IfcProject shall associate IfcDocumentInformation with;
      1. non-empty Identification, Name and Location attributes (content of the attributes is irrelevant to the check at this stage); as well as
      2. ElectronicFormat shall be application/pdf to denote the format of the "virtually" attached file; (you are not required to attach any such file for the test) and
      3. Editor of the file being yourself or any other actor - do not forget to declare it using Project Declaration usage from Sprint 1.1.
2. Project Dataset Information
   1. The IfcProject shall associate IfcDatasetInformation with:
      1. non-empty Identification, Name and Location attributes (content of the attributes is irrelevant to the check at this stage); as well as
      2. ElectronicFormat shall be text/xml to denote the format of the "virtually" attached file; (You are not required to attach any such file for the test) and
      3. SchemaReference being equal to http://geosciml.org/geosciml/2.0/xsd/geosciml.xsd.
3. Project Library Information
   1. The IfcProject shall associate IfcLibraryInformation with:
      1. non-empty Location, Version, VersionDate and Publisher attributes (content of the attributes is irrelevant to the check at this stage).
4. Project Type Definitions
   1. The IfcProject shall declare an IfcArchElementType.
5. Project Template Definitions
   1. The IfcProject shall declare an IfcPropertySetTemplate with the following structure:
      • Name : 'Pset_GeoObsBoreholeConstruction'
      • TemplateType : .PSET_TYPEDRIVENOVERRIDE.
      • ApplicableEntity : 'IfcBorehole'
      • HasPropertyTemplates :
        • IfcSimplePropertyTemplate :
          • Name : 'DrillingDiameter'
          • TemplateType : .P_SINGLEVALUE.
          • PrimaryMeasureType : 'IfcPositiveLengthMeasure'

Sprint 2.1

Prerequisities

• Sprint 1.1,
• Sprint 1.2, and
• Sprint 1.3.

Duration

Usages

1. Spatial Composition
   1. All IfcTunnelPart shall be aggregated in an IfcTunnel or IfcTunnelPart.
   2. All IfcTunnel shall be aggregated in either an IfcTunnel, IfcSite or IfcProject.
   3. All IfcSite shall be aggregated in IfcProject.
2. Spatial Decomposition
   1. Each IfcTunnel may only be decomposed by IfcTunnel or IfcTunnelPart.
   2. There shall be at least one IfcTunnel in the file with non-empty Name.
3. Linear Composition
   1. There shall be one IfcAlignment in the file with non-empty Name.
4. Alignment Layout
   1. There shall be at least one LINE, at least one CIRCULARARC and at least one CLOTHOID segments nested in the horizontal layout (see IfcAlignmentHorizontalSegment.PredefinedType).
   2. There shall be at least one CONSTANTGRADIENT and either at least one CIRCULARARC or at least one PARABOLICARC segments nested in the vertical layout (see IfcAlignmentVerticalSegment.PredefinedType).
5. Object Nesting
   1. There shall be at least one IfcReferent on IfcAlignment with non-empty Name.
   2. All IfcReferent shall be nested in any IfcAlignment. The IfcRelNests relationship nesting instances of IfcReferent shall only nest instances of IfcReferent.
6. Group Assignment
   1. There shall be at least one IfcGroup (or any of the subtypes) declared in IfcProject with at least one element grouped.

Sprint 2.2

Prerequisities

• Sprint 1.1,
• Sprint 1.2,
• Sprint 1.3, and
• Sprint 2.1.

Duration

Usages

1. Product Local Placement
   1. The IfcTunnelPart.ObjectPlacement.PlacementRelTo shall point to the IfcTunnelPart.Decomposes.RelatingObject.ObjectPlacement (i.e., the IfcTunnel or IfcTunnelPart it is part of).
   2. If IfcTunnel is aggregated in IfcSite or IfcTunnel, then the IfcTunnel.ObjectPlacement.PlacementRelTo shall point to the IfcTunnel.Decomposes.RelatingObject.ObjectPlacement (i.e., the IfcSite or IfcTunnel it is part of).
2. Alignment Geometry
   1. Any IfcAlignment nested by only an IfcAligmentHorizontal and an IfcAlignmentVertical shall be represented according to concept template Alignment Geometry Gradient:
      • RepresentationIdentifier = 'Axis'
      • RepresentationType = 'Curve3D'
      • representation is IfcGradientCurve
   2. Any IfcAlignment nested by an IfcAligmentHorizontal and an IfcAlignmentVertical and an IfcAlignmentCant shall be represented according to concept template Alignment Geometry Cant:
      • RepresentationIdentifier = 'Axis'
      • RepresentationType = 'Curve3D'
      • representation is IfcSegmentedReferenceCurve
   3. All IfcAlignment instances shall have an additional 2D representation (documentation):
      • RepresentationIdentifier = 'Axis'
      • RepresentationType = 'Curve2D'
      • representation is IfcCompositeCurve (the same instance used as IfcGradientCurve.BaseCurve or IfcSegmentedReferenceCurve.BaseCurve.BaseCurve above),
3. Element Nesting
   1. All IfcReferent instances shall be linearly placed according to the Product Linear Placement concept template:
      • IfcReferent.ObjectPlacement shall be IfcLinearPlacement.
      • IfcReferent.ObjectPlacement.PlacementRelTo shall point to IfcReferent.Nests.RelatingObject.ObjectPlacement.
4. Linear Composition
   1. All IfcAlignment instances shall be aggregated in IfcProject. It shall use its own IfcRelAggregates instance and not share it with the Spatial Decomposition usage from Sprint 1.2.

Sprint 2.3

Prerequisities

• Sprint 1.1,
• Sprint 1.2,
• Sprint 1.3,
• Sprint 2.1, and
• Sprint 2.2.

Duration

Usages

1. Product Relative Positioning and Product Linear Placement
   1. The IfcSite (defined in Sprint 2.1) should be placed using the above concepts:
      1. either along the IfcAlignment (defined in Sprint 2.1)
      2. or relative to an IfcReferent (defined in Sprint 2.1, which is nested according to Sprint 2.2).
   • In other words: IfcSite.ObjectPlacement.PlacementRelTo shall point to IfcSite.PositionedRelativeTo.RelatingPositioningElement.ObjectPlacement. (IfcSite.PositionedRelativeTo.RelatingPositioningElement is the IfcAlignment or IfcReferent above.)
2. Product Geometric Representation
   1. We encourage to provide examples for IfcGeoScienceModel (other IfcElement are allowed).
   2. Provide at least one of the listed alternatives for the volumetric or surfaic representation:
      1. Body Tesselation Geometry or
      2. Body Brep Geometry or
      3. Body SweptSolid Geometry or
      4. Body Sectioned Solid Horizontal or
      5. Body Surface Model Geometry or
      6. Voxel Geometry - in progress or
      7. Surface Tessellation Geometry with IfcTriangulatedIrregularNetwork.
3. Property Sets with Override
   1. The IfcSite shall have the property set Pset_LandRegistration assigned with:
      1. the property LandID provided with non-empty value (the exact value is arbitrary),
      2. the property IsPermanentID provided with value .T. (i.e. true) and
      3. the property LandTitleID provided with non-empty value (the exact value is arbitrary).
4. Classification Association
   1. At least one instance of IfcProduct shall be associated with an IfcClassificationReference where:
      1. Identification and Name shall exist, and
      2. ReferencedSource shall reference the IfcClassification occurrence associated with the IfcProject in Sprint 1.2.

1. Library Association (optional)
   1. The Pset_LandRegistration from above shall associate an IfcLibraryReference where:
      1. Location shall be a URI value pointing to the computer interpretable listing for the Tunnel - 1.0 [Deliverables] specification (you need to find it yourself in the specification),
      2. Identification being "#3540", and
      3. Name being "Pset_LandRegistration".

Sprint 3.exc

Prerequisities

• Sprint 1.1,
• Sprint 1.2,
• Sprint 1.3,
• Sprint 2.1,
• Sprint 2.2, and
• Sprint 2.3.

Duration

Concepts

New concepts

1. Spatial containment
2. Element Decomposition
3. Element Composition
4. Material single
5. Material Layer Set Usage
6. Assigning properties to material
7. Excavation Cuttings
8. Body Sectioned SolidHorizontal
9. Guide Curves
10. Product Span Positioning

Usages

Excavation

1. IfcUndergroundExcavation or IfcEarthworksCut
   1. body geometry
      1. Body Sectioned SolidHorizontal and Guide Curves or
      2. any other body geometry
   2. local placement
   3. properties with Pset_ExcavationCommon
   4. excavation cuttings and thus no containment
      1. The excavation shall void (IfcRelVoidsElements) the IfcGeoScienceModel below
2. IfcGeoScienceModel/GEOTECHMODEL
   1. see geotechnics, book B
3. IfcGeoSciencefeature/GEOTECHNICALUNIT
   1. see geotechnics, book B

Waterproofing

1. IfcCovering/MEMBRANE
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry or surface tesselation geometry
   3. local placement
   4. properties with Pset_CoveringTypeMembrane
   5. material layer set (see also Table 157) with at least 2 layers:
      1. Layer
         1. LayerThickness being 2 mm
         2. Name being 'Front'
         3. Material.Name = 'Synthetic'
      2. Layer
         1. LayerThickness being 0.5 mm
         2. Name being 'Fill'
         3. Material.Name = 'GeoTextile'
2. IfcDiscreteAccessory/WATER_BARRIER
   1. contained in IfcTunnel or IfcTunnelPart
   2. Geometry: WIP
   3. local placement
   4. properties with Pset_DiscreteAccessoryTypeWaterBarrier
3. IfcSpatialZone/COMPARTMENT
   1. aggregated in IfcTunnel or IfcTunnelPart
   2. body geometry
   3. local placement
   4. properties with Pset_SpatialZoneTypeCompartment
4. IfcBuiltSystem/WATERPROOFING
   1. declared by IfcProject
   2. groups elements IfcCovering/MEMBRANE, IfcDiscreteAccessory/WATER_BARRIER and IfcSpatialZone/COMPARTMENT
   3. properties with Pset_BuiltSystemTypeWaterproofing

Support

1. IfcElementAssembly/ARCH
   1. contained in IfcTunnel or IfcTunnelPart
   2. decomposed by IfcArchElement/SEGMENT below
   3. local placement
   4. properties with WIP
2. IfcArchElement/SEGMENT
   1. part of IfcElementAssembly/ARCH above
   2. body geometry
   3. local placement
   4. properties with Pset_ArchElementCommon
   5. single material
      1. properties with Pset_MaterialConcrete
3. IfcTunnelTypicalSection/EXCAVATIONSUPPORT
   1. contained in IfcTunnel or IfcTunnelPart
   2. positioned between two IfcReferent
   3. properties with WIP
4. IfcBuiltSystem/TUNNEL_SUPPORT
   1. declared by IfcProject
   2. groups elements IfcElementAssembly/ARCH and IfcTunnelTypicalSection/EXCAVATIONSUPPORT
   3. properties with WIP

Lining

1. IfcArchElement/LINING
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry
   3. local placement
   4. properties with Pset_ArchElementCommon
   5. single material
      1. properties with Pset_MaterialConcrete
2. IfcBuiltSystem/TUNNEL_LINING
   1. declared by IfcProject
   2. groups elements IfcArchElement/LINING
   3. properties with WIP

Sprint 3.geo

Prerequisities

• Sprint 1.1,
• Sprint 1.2,
• Sprint 1.3,
• Sprint 2.1,
• Sprint 2.2, and
• Sprint 2.3.

Duration

Concepts

New concepts

1. Spatial containment
2. Element Decomposition
3. Element Composition
4. Product Assignment
5. Dataset Association
6. Product Span Positioning
7. Assignment to Product

Usages

Book A

1. IfcBorehole
   1. contained in IfcSite
   2. Geometry: See IfcBorehole here.
   3. local placement
   4. properties with Pset_SpatialGeoObsBorehole
2. IfcGeoScienceObservation/BOREHOLELOG
   1. if not as part of a composition - assigned to IfcBorehole above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/BOREHOLELOG
   3. if not as part of a composition - declared in IfcProject
   4. if not further decomposed - properties with Pset_GeoObsBoreholeGeoLogInterval
3. IfcDatasetInformation
   1. declared in IfcProject
   2. associated to IfcGeoScienceObservation/BOREHOLELOG
4. IfcSpatialZone/MAPPEDZONE
   1. aggregated in IfcSite
   2. Geometry: See IfcSpatialZone/MAPPEDZONE here.
   3. local placement
   4. properties with Pset_SpatialGeoObsMappedZoneCommon
5. IfcGeoScienceObservation/MAPPEDFEATURE
   1. if not as part of a composition - assigned to IfcSpatialZone/MAPPEDZONE above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/MAPPEDFEATURE
   3. if not as part of a composition - declared in IfcProject
   4. Geometry: See IfcGeoScienceObservation/MAPPEDFEATURE here.
   5. local placement
   6. if not further decomposed - properties with Pset_GeoObsMappedUnit
6. IfcGeoScienceObservation/LOCALINFORMATION
   1. if not as part of a composition - assigned to IfcSpatialZone/MAPPEDZONE above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/LOCALINFORMATION
   3. if not as part of a composition - declared in IfcProject
   4. assigned to IfcSpatialZone/MAPPEDZONE above
   5. declared in IfcProject
   6. Geometry: See IfcGeoScienceObservation/LOCALINFORMATION here.
   7. local placement
   8. if not further decomposed - properties with Pset_GeoObsPtObservationCommon
7. IfcGeoScienceObservation/INSITUTESTRESULT
   1. if not as part of a composition - assigned to IfcSpatialZone/MAPPEDZONE or IfcBorehole above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/INSITUTESTRESULT
   3. if not as part of a composition - declared in IfcProject
   4. assigned to IfcSpatialZone/MAPPEDZONE above
   5. declared in IfcProject
   6. Geometry: See IfcGeoScienceObservation/INSITUTESTRESULT here.
   7. local placement
   8. if not further decomposed - properties with Pset_InSituTestCommon
8. IfcGeoScienceObservation/LABTESTRESULT
   1. if not as part of a composition - assigned to IfcSpatialZone/MAPPEDZONE or IfcBorehole above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/LABTESTRESULT
   3. if not as part of a composition - declared in IfcProject
   4. Geometry: See IfcGeoScienceObservation/LABTESTRESULT here.
   5. local placement
   6. if not further decomposed - properties with Pset_LabTestCommon
9. IfcGeoScienceObservation/GEOPHYSICALSURVEYRESULT
   1. if not as part of a composition - assigned to IfcSpatialZone/MAPPEDZONE or IfcBorehole above
   2. if part of a composition - RelatingObject shall be of type IfcGeoScienceObservation/GEOPHYSICALSURVEYRESULT
   3. if not as part of a composition - declared in IfcProject
   4. Geometry: See IfcGeoScienceObservation/GEOPHYSICALSURVEYRESULT here.
   5. local placement
   6. if not further decomposed - properties with Pset_GeophysicalSurveyCommon

Book B

1. IfcGeoScienceModel
   1. PredefinedType is depending on decomposition (valid pairs: WIP)
   2. contained in IfcSite
   3. decomposed by IfcGeoScienceFeature/* below
   4. local placement
   5. properties with Pset_GeoScienceModelCommon
2. IfcGeoScienceFeature
   1. part of IfcGeoScienceModel above
   2. PredefinedType - at least one of:
   3. PHYSICALPROPERTYDISTRIBUTION
      1. body geometry
         1. if geometry is IfcVoxelGrid an associated instance of IfcVoxelData is required
         2. otherwise any other body geometry from Sprint 2.3 is required
      2. local placement
      3. properties with Pset_GeoScienceFeatureCommon
   4. GEOLOGICALUNIT
      1. body geometry
         1. if geometry is IfcVoxelGrid an associated instance of IfcVoxelData is required
         2. otherwise any other body geometry from Sprint 2.3 is required
      2. local placement
      3. properties with Pset_GeoScienceFeatureTypeGeologicalUnit
   5. FAULT
      1. body geometry
         1. if geometry is IfcVoxelGrid an associated instance of IfcVoxelData is required
         2. otherwise any other body geometry from Sprint 2.3 is required
      2. local placement
      3. properties with Pset_GeoScienceFeatureTypeFault
   6. CONTACT
      1. surface geometry
      2. local placement
      3. properties with Pset_GeoScienceFeatureTypeContact
   7. GEOTECHNICALUNIT
      1. body geometry
         1. if geometry is IfcVoxelGrid an associated instance of IfcVoxelData is required
         2. otherwise any other body geometry from Sprint 2.3 is required
      2. local placement
      3. properties with Pset_GeoScienceFeatureCommon
   8. HAZARDAREA
      1. body geometry
         1. if geometry is IfcVoxelGrid an associated instance of IfcVoxelData is required
         2. otherwise any other body geometry from Sprint 2.3 is required
      2. local placement
      3. properties with Pset_GeoScienceFeatureTypeGeoHazard

Book C

1. IfcTunnelTypicalSection/GEOTECH
   1. contained in IfcTunnel
   2. positioned between two IfcReferent
   3. properties with Pset_GeoAspects

Other example

Geometric representations

Sprint 3.sys

Prerequisities

• Sprint 1.1,
• Sprint 1.2,
• Sprint 1.3,
• Sprint 2.1,
• Sprint 2.2, and
• Sprint 2.3.

Duration

Concepts

New concepts

1. Spatial containment
2. Material Layer Set
3. Port connectivity
4. Port nesting
5. Component to Distribution system
6. Port to Distribution system
7. Control flow
8. Body SweptSolid Geometry
9. Body AdvancedSwept DiskSolid Polycurve Geometry

Usages

Example on fire protection

1. IfcPipeSegment
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry, e.g. see geometry concepts listed above, or any volumetric representation from sprint 2.3
   3. local placement
   4. associates material, e.g. steel
   5. properties with Pset_PipeSegmentTypeCommon
   6. nesting ports: see also Table 599
2. IfcPipeFitting
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry
   3. local placement
   4. associates material, e.g. Casing is steel
   5. properties with Pset_PipeFittingTypeCommon
   6. nesting ports: see also Table 594 here
3. IfcFireSuppressionTerminal/SPRINKLER
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry
   3. local placement
   4. nesting ports: see also Table 640 here
4. IfcSensor
   1. contained in IfcTunnel or IfcTunnelPart
   2. body geometry
   3. local placement
   4. nesting ports: see also Table 318 here
   5. flow control to the IfcFireSuppressionTerminal/SPRINKLER above: see also Table 319 here
5. IfcDistributionPort
   1. connected to other IfcDistributionPort
      1. one side shall be SOURCE and the other a SINK as per documentation
   2. nested to all elements listed above
   3. no geometry
   4. no containment
   5. properties with Pset_DistributionPortTypePipe
6. IfcDistributionSystem/FIREPROTECTION
   1. declared in IfcProject
   2. groups all elements listed above

Other example

  Link to this page