ifc5 development strategy - afnet

IFC5 Development Strategy

Christophe CASTAING – Egis Thomas Liebich AEC3

IFC delivery – C.CASTAING /TH. LIEBICH 1

2

Director of the project BIM by EGIS SA/ Director of the digital engineering plan

BIM Task Group Chairman EFCA European Federation of Consulting Associations

Chair the CST Medi@ConstructChairman of Infrastructure room – bSI And standard committee member

Deputy director of the National Project MINnD

Editorial Committee of PTNB

IFC delivery – C.CASTAING /TH. LIEBICH

presentation


Interoperability basement

Data Dictionary

Information delivery manual

Conceptual Model


presentation


Scope of IFC 5 – focus of supporting infrastructure work

Bridges RailwaysIFC-Bridge IFC-Railway

RoadsIFC-Road

AlignmentCommon baseline

TunnellingIFC-Tunnel


A common conceptual model

IFC extension schedule


IFC5 - 2020

IFC4.2 - 2018

&

7

Common schema project

Objectives of Common Schema Project

- Collaboration between the infrastructure domains- Guidance for common schema development principles

Therefore we have the need to have representationof IFC Rail within the Common Schema Project

- One representative (from shared governance), or- One representative per domain?

Other representatives come from IFC Bridge, IFC Road(plus IFC Harbour, Tunnel, Landscape)


Interaction between INFRA Room and RAIL Room

Road Bridge Tunnel

Rail

TrackSignal Energy Telecom

Shared rail

Common all

Alignment

Rail Room Infrastructure RoomEgis


Fork and Merge in upcoming IFC developments


Parallel work

IFC4 building, products IFC4.1 Alignment, Terrain IFC4.x if needed e.g. IFC Bridge IFC5 Infrastructure

IFC42013

2015 2016

Add 1 Add 2

2015IFC Alignment 1.0

IFC Road / IFC Rail PAS

IFC5

Add 3

2017 20192018

2017

MO

U IF

C Ro

ad/R

ail

Common Definitions

2020

10

IFC5 overall project plan

ID Project Start End2015 2016 2017 2018 2019 2020

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

1 30.12.201601.01.2015Alignment (1.0 and 1.1)

2 30.12.201601.01.2016Overall Architecture (Taxonomy, etc.)

3 31.12.201803.07.2017IFC Bridge

4 31.12.201901.01.2018IFC Road

5 31.12.201901.01.2018IFC Rail

6 30.06.202001.01.2018IFC Common Schema

7 31.12.202001.01.2019ISO 16739 Acceptance

Additional projects include IFC Port and Harbours, IFC Tunnel, IFC Landscape (new)


IFC5 will be a formal international standard

IFC4 (today) ISO 16739 : 2013IFC5 (planned) ISO 16739 ed2 : 2020

Coordinated by ISO/TC 59/SC 13 : “Organization and digitization of information about buildings and civil engineering works, including Building information modelling (BIM)”

ISO 16739 EN ISO 16739

Thomas LiebichIFC delivery – C.CASTAING /TH. LIEBICH 13

presentation


Example : domains ( IFC RAIL)


Example : domains IFC Bridge


presentation


Data dictionary and exchange requirementBridge

Concept Model

Bridge Engineering

Concept Model

Preliminary Roadway

Geometry Model

Preliminary Aesthetic

Design Model

Initial Structural Model

Final Roadway Geometry

Model

Final Structural

Model

EM.I/PAL-E EM.S/SE-E EM.PD/TE-SE EM.PD/PAL-SE EM.PD/SE-E-PAL EM.FD/TE-SE EM.FD/D-E

Identification numbers

Names

Over roadway identities

Under roadway identities

Places

Coordinates

Associated stakeholders

Dates

Status

Design data

Design specifications

System of unitsIndicators

Miscellaneous information

Environmental information

Types

Lines

Stations

Azimuths

Lengths

Radii

Types

Lines

Stations

Elevations

Lengths

Grades

Roadway information

Topographies

Geometries

Slopes

Widths

Offsets

Lane information

Shoulder information

Stations

Azimuths

Skew angles

Property

Location

Dimension

Material

Protective sealant

Vertical profile

Horizontal alignment

Project descriptions

Location

Roadway geometry

Bridge control information

Roadway structure

Approach slabs

Cross section

Information Group

Information Items Attribute Set

Project information

Identification

Meta data


Unique ID Name & definition

•Name in international English

•Def. in IE•Name in author language

•Def. in AL•Name in language n

•Def. in language n

Traceability

•Status•Date of creation•Replaces•Replaced by•Date of deactivation

•Date of validation

Links (groups, dependency)

•Group of properties

•Relation between properties

•Relation of the property identifiers in the interconnected dictionaries

Tracking

•Country of use•Subdivision of use

Specification

•Type•Cardinality•Format•Quantity•Expression of the quantity

•List of possible values (English)

•List of possible values (author lang.)

•List of possible values (n lang.)

•Boundary values

A property is defined by a set of attributes (mandatory or not)


presentation


Interoperability basement: use case definition


Example : IFC 4.1 extension for IFC Bridge


Example : IFC 4.1 extension


presentation


Taxonomy

Establish joint vocabulary for all bridge items


presentation


Taxonomy to Conceptual model


The New Silk Road


ifc5 development strategy - afnet

Documents