C9 - BIM implementation on Stockholm Bypass Project Using PowerCivil. Trafikplats Akalla och Häggvik, ÅF-URS. Track: Civil Presenter: Mateusz Nettmann
AGENDA 1. Introduction: A. URS Company B. People involved 2. Project description A. FSK06 Contract of Stockholm Bypass project B. Project goals 3. Starting design in MX* and moving over to PowerCivil 4. BIM implementations on the Stockholm Bypass Project: A. Files/models naming convention (chaos system) B. CAD layers and components naming convention (Client BIM system) C. 3D objects level of details and informations D. Headroom and swept path analyses done in 3D E. Using 3D contour plans for checking corridor integrity F. Design workflow chart (from 2D to i-model) 5. What Stockholm Bypass Project requires (more) from the software? 6. Questions Using Bentley s software makes 3D a Work-In-Progress tool, and not only final illustration product
1. INTRODUCTION
1A. URS COMPANY URS - More than 54,000 People in nearly 50 Countries
1A. URS COMPANY URS - More than 54,000 People in nearly 50 Countries URS Continental Europe - Belgium, Finland, France, Germany, Greece, Italy, Kazakhstan, Lithuania, The Netherlands, Poland, Serbia, Spain -1,230 employees in mainland Europe.
1A. URS COMPANY URS - More than 54,000 People in nearly 50 Countries URS Continental Europe - Belgium, Finland, France, Germany, Greece, Italy, Kazakhstan, Lithuania, The Netherlands, Poland, Serbia, Spain -1,230 employees in mainland Europe. URS Poland Gdańsk, Kraków, Łódź, Poznań, Warsaw, Wrocław 330 employees ` URS Poznań office 100 employees
1B. PEOPLE INVOLVED HOW DID WE GET INTO 3D & BIM ANNA LEŚNIEWSKA NOWAK is the Technical Director and Poznan Office Manager with responsibility for international projects across the Infrastructure Division of URS Poland. Anna has 18 years of experience in major road schemes and used to work for many years as a highway designer using MX and Microstation. She is currently managing the Polish input of all disciplines to the Stockholm Bypass project. MIKE CLARKE is based in the UK and works in the Technology & Data Solutions Group. He is the Technical Director with responsibility for ProjectWise development across the Infrastructure & Environment Division of URS. Mike has more than 25 years of experience with Bentley and Autodesk technologies and has worked on many high profile projects across the globe. He is also working with Trafikverket on the implementation of ProjectWise for the Stockholm Bypass. STEFAN HAGMAN works with BIM and Model development for ÅF Infrastructure. He has a background in Civil engineering. Working together with Swedish Transport Administration Engineering Department to defining how to use BIM and models regarding collaboration, reviewing between technical disciplines also how to use data from models. JOHAN ASPLUND works as a BIM specialist at the Swedish Transport Administration Engineering Department for Major projects. He is specialized in object-oriented design and digital project management towards complex infrastructure projects where he has been active in all phases of the design process. Quality and optimization has always been the main focus.
1B. PEOPLE INVOLVED FSK06 ROADS TEAM MATEUSZ NETTMANN FUNCTIONAL MANAGER - URS KENT CEDERHOLM ASSISTANT FUNCTIONAL MANAGER - ÅF MARCIN ABEL ASSISTANT FUNCTIONAL MANAGER - URS MACIEJ KIŚLUK DESIGNER 1 - URS MICHAŁ BIEŃ DESIGNER 1 - URS PAWEŁ ŚLESIŃSKI DESIGNER 2 - URS ŁUKASZ WASIK DESIGNER 2 - URS EMILIA AUGUSTYNIAK DESIGNER 2 - URS MAŁGORZATA PRYSIAŻNA 3D & BIM COORDINATOR, URS
1B. PEOPLE INVOLVED MATEUSZ NETTMANN MATEUSZ NETTMANN TEAM MANAGER is the Road Design Team Manager based in Poznan office of URS Poland with responsibility for international designs. Mateusz has more than 11 years of experience in major road projects in Poland (including 100 km motorway project) and in the UK (both as a designer and site engineer/supervisor). At the moment he is involved in the Stockholm Bypass project as a Functional Manager of Roads for FSK06 contract. Mateusz is highly concentrated around the latest 3D techniques and BIM process In Roads. Working on a similar project and having some issues? Do not hesitate to contact. We will share our experience and try to help you if we can. mateusz.nettmann@urs.com The Bentley LEARNing Conference 2013 BCR2LC15
2. PROJECT DESCRIPTION
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT Project Packages: FSK01 Kings Curve Interchange FSK02 Rock Tunnels FSK03 Lovö Interchange FSK04 Vinsta Interchange FSK05 Hjulsta Interchange FSK06 Akalla and Häggvik Interchanges FSK07 Tunnel Systems FSK08 Installations FSK09 Towers and Stations ÅF Consult / URS Joint Venture For further information of Stockholm Bypass please refer to presentation: BC3LC12 Implementing ProjectWise as a Foundation to BIM on the Stockholm Bypass (BeTogether 2012)
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT 3 main tender documents to be produced: - FSE61 Akalla interchange area (Design and Build) - FSE62 Häggvik interchange area (Client Design) - FSE623 Ex. bridges widening (Client Design, Framework)
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT - 3 km section including 27 road alignments of total length over 22 km
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT - 11 bridges (including 3 tunnels) + number of retaining walls
2A. FSK06 CONTRACT OF STOCKHOLM BYPASS PROJECT - Complex water & drainage and electrical & ducting networks
2B. PROJECT GOALS - Common Data Environment (Project Wise platform and Design Workflows) - Intelligent model base with meta-data (BIM coded and object oriented i-models) - Asset management (using Microstation item set search tool; BIM coded elements) - Eliminate all the interdisciplinary clashes, continuous review and mark-up process (2D multi-disciplinary normal sections and clash detection exercise in 3D, i-model and overlay file in Navigator) -Minimize number of drawings (1:2 000 overview plans only; 3D models take priority) - Quantity take off directly from 3D models (very high level of details in 3D models; using InRoads quantity manager tool)
3. STARTING DESIGN IN MX (WITHOUT USING ROADWAY DESIGNER) AND MOVING OVER TO POWERCIVIL
3. STARTING DESIGN IN MX* ( * WITHOUT USING ROADWAY DESIGNER) AND MOVING OVER TO POWERCIVIL Getting MX models into PowerCivil DTMs
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL Getting MX alignments into PowerCivil ALG Paved width geometry
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL Problem of importing vertical alignment directly from models
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL MX alignment export to XML and import to PoverCivil ALG
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL Using MX strings as DTM point control
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL Getting MX reverse curves into PowerCivil
3. STARTING DESIGN IN MX* AND MOVING OVER TO POWERCIVIL The way we got MX data connected with PowerCivil 1 directly from models 2 via XMLs
4. BIM IMPLEMENTATIONS ON THE STOCKHOLM BYPASS PROJECT
4A. FILES/MODELS NAMING CONVENTION (CHAOS SYSTEM) discipline geographical zone
4A. FILES/MODELS NAMING CONVENTION (CHAOS SYSTEM) structural object technical system
4A. FILES/MODELS NAMING CONVENTION (CHAOS SYSTEM) serial number
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Naming convention is based on documents: BH90 (Part7, Part8) SB11 CAD layers BSAB (Build Parts 96) RESPONSIBLE PARTY List of Art: A Architecture B Rock Engineering K Structures N Envronment T Roads & Traffic W Water & Drainage Z Surveying
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Elements Based on BSAB Build Parts 96 31-- Superstructures 31B- Superstructures for the road (universal code for a hard surface) 31BB Hard Strip 31BC Carriageways 31BD Hard shoulder 31BE Support Strip 31E- Superstructures for slopes 32E- Kerb 32FB Road ditches
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Building Part Type of Elements Examples: 31BC61 Carriageways pavement Type 1 31BC62 Carriageways pavement Type 2 31BC63 Carriageways pavement Type 3 31CG61 Concrete barriers Norrortsleden type 31CG62 Concrete barriers Stockholm Type 31CG63 Steel barriers double sided N1
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Presentation sprcifies how an object is presented in the model Examples: EZ 3D Graphics EJ 2D Graphics EP Profile ES Section ED Details EE Ilustration
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Status Indicates whether the item is: N new E existing
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Location Specifies the exact position of the projected information within an object:
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Construction ID Assed ID
4B. CAD LAYERS AND COMPONENTS NAMING CONVENTION (CLIENT BIM SYSTEM) Construction Stage Usedto devide the project in terms of time
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS BIM CODE AMA CODE BoQ SUB-ZONE CORRIDOR MATERIAL CAD PROPERTIES INFORMATIONS START STATION STOP STATION VOLUME
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS COMPONENT NAME INTO LEVEL NAME
4C. 3D OBJECTS LEVEL OF DETAILS AND INFORMATIONS CUT AND FIL PRESENTED AS 3D COMPONENTS
4D. HEADROOM AND SWEPT PATH ANALYSES DONE IN 3D
4D. HEADROOM AND SWEPT PATH ANALYSES DONE IN 3D
4E. USING 3D CONTOUR PLANS FOR CHECKING CORRIDOR INTEGRITY
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model) T6010444_.3 K6010444_.5 W6010444_.2 G6010444_.3 E6010444_.4
4F. DESIGN WORKFLOW CHART (from 2D to i-model)
4F. DESIGN WORKFLOW CHART (from 2D to i-model), CLASH DETECTION
4F. DESIGN WORKFLOW CHART (from 2D to i-model), CLASH DETECTION
5. WHAT STOCKHOLM BYPASS PROJECT REQIURES MORE FROM THE SOFTWARE
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE A. 3D Cut and Fill representation as components
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE B. Reporting component s properties directly at DTM or DGN level
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE B. Reporting component s properties directly at DTM or DGN level
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE B. Reporting component s properties directly at DTM or DGN level
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE C. Using rounding length with components and alternate surfaces
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE C. Using rounding length with components and alternate surfaces
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE D. Draw slope direction pattern indication at ITL level
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE D. Draw slope direction pattern indication at ITL level
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE E. SS2 (ALG, ITL, IRD) Project Wise and issue of many designers
5. WHAT STOCKHOLM BYPASS REQUIRES (MORE) FROM THE SOFTWARE F. Overlay/Stripping component s properties (Follow lowest/follow lowest)
Using Bentley s software makes 3D a Work-In-Progress tool, and not only final illustration product 6. QUESTIONS mateusz.nettmann@urs.com
THANK YOU FOR YOUR ATTENTION