The following bridge types, based on their structural system, are identified as the most common and widespread across the world. These bridge types are considered to be in scope
for IFC-Bridge. The developed IFC-Bridge extensions were validated using examples of these bridge types.

• Slab Bridge
• Girder Bridge
• Slab-Girder Bridge
• Box-girder bridge
• Frame Bridge
• Rigid Frame Bridge
• Culvert

The following bridges types are also expected to be covered by IFC and the IFC-Bridge extension, however they were not subject to validation tests:

• Truss bridge
• Arch bridge
• Cantilever bridge
• Cable-stayed bridge
• Suspension bridge

From a material viewpoint, the following bridge types are covered:

• Reinforced Concrete bridges
• Prestressed Concrete bridges
• Steel/Concrete Composite bridges
• Steel girder bridges
• Steel bridges

Particular emphasis are placed on realizing the necessary data structures for modelling prestressing systems.

Based on a careful analysis of the benefits of the individual uses cases and the complexity and effort involved with defining the necessary data structures, the project team decided to prioritize the following use cases for explicit consideration when designing the IFC-Bridge extension:

• Initial State Modeling
• Import of major road / railway parameters
• Technical Visualization
• Coordination / Collision Detection
• 4D Construction Sequence Modeling
• Quantity Take-Off
• Progress Monitoring
• As-built vs. as-planned comparison
• Handover to asset management
• Handover to GIS for spatial analysis
• Design to design (reference model)
• Design to Construction

Due to their overly high complexity, the following use cases are out of scope of this fast-track project:

• Design to Design (Full model logic)
• Structural analysis
• Code Compliance Checking
• Drawing generation and exchange
• Prefabrication and manufacturing

It is emphasized that the exclusion from the fast-track project does not mean that these use cases cannot be covered by future extensions of IFC-Bridge. It has to be noted in particular, that the full design-to-design use case which incorporates the model’s design logic, is excluded here as it would require software vendors to adapt modeling functionality, which is not deemed practical for reasons of competitive advantage, compatibility, and cost/benefit. Currently, there is no well-defined industry need that would justify this effort.