Bridge B id Information I f i Modeling: M d li Towards BIM/BrIM for the Bridge g Lifecycle Stuart S. Chen, Ph.D., P.E. Dept. of Civil, Structural, and Environmental Engineering University at Buffalo

What’s Happening in (A)EC?

Outline • • • • •

Case Study Bridge: Quincy Ave BrIM: What and Why; Potential Benefits Glimpses of Streamlined Workflows Summary & Results A k Acknowledgements l d t

Q i Quincy Ave A As-Built A B il

Bridge Information Modeling (BrIM): What/Why? • Parametric 3D Product Modeling (≠ yet not independent from Process Modeling) • Leveraging of automation and communication technologies for managing bridges through their lifecycle • Fluid and seamless electronic data exchange, management and access • Improved communication of information to efficiently manage bridge related data among stakeholders ((design, g , construction,, operations and lifecycle asset management)

A View of the Life Cycle Process

Project Background Piecemeal Progress in the Industry •

Parametric design tools and TransXML omit detailing for fabrication and construction

•

3D pre-cast pre cast concrete modeling tools are not (yet) bridge-oriented

•

Bridge inspection or design/rating (e.g.) apps each h require i th their i own d data t ((re)entry ) t

•

3D geometry created (e.g.) for visualization is not also leveraged for fabrication & construction

Overview of Project Vision •

Develop a prototype integrated system illustrating data exchanges and applications

•

Address entire bridge life cycle

•

Utilize 3-D bridge information modeling (BrIM) as a technology to accelerate bridge project delivery and enhance life cycle management

•

Demonstrate the viability, efficiencies and b benefits fit off the th integrated i t t d bridge b id project j td delivery li and life cycle management concept

ting

ad erlo

XM L

Sup

GIS M

Per mitt Rou ting ,

ode l Dat & aT able

ing

ridg e

dB Ope rate

ge Brid

zation Visuali g Stagin

ge

d cte stru Con

Brid

BI

del

ine d

ing / N

s

3D M o

Report

Variou

g tin ma

Data T able & Diagra m

XM

X ML

le ab

BR IDG (Po EWar e ntis )

mm ing

ti Es

BR ID

Tekla

Da ta Ta ble

Ma inta

X ML XM CS L V

BrIM Data Pool

GE Wa AP re I

ng ati tim k Es -Lin

PRODUCTS

T EN EM G A N A M

APPLICATIONS

og ra

re

V XML CS T TX

Pr

a EW IDG PI R B A

a re EW IDG BR API

ge Brid

ble Ta ta Da & ram ag Di on c ti c e p e an I n s n t en i Ma

a re EW ) IDG BR Pontis (

e m ent

able Data T & m Diagra

M anag

PRESENTATION TYPE OF MODEL / DATA

d ine inta Ma

INVOLVED SOFTWARE/ TOOLS

are EW ID G tis ) R r B (V i

T ta

LINKAGE TYPE / FORMAT

e

Da

BrIM DATA POOL

abl

N O

ta T Da

Con stru cte dB ridg Fabric e ation & Manufa Co cturing n Sc stru 3D M o he cti de l du on lin & g CNC F 4D ile Di Mod ag ram el Tekla o r Geopa k Te Rebar MS kla P r (4D ) o je ct

3D M odel Archite

L

kla Te ap L e CA D th Ma l de M o in g 3 D Dr a w 2D ry in a im ig n l e Pr Des

cture

B ed ign Des

e ridg

D ES IG N

Ra

e

T BR XT Wa IDG / re EAP CSV I SA BR P ID 200 GE 0 (O W E-Link / pis are ) MS 3D Projecct Da Mo d ta Dia Ta el gra ble De Data Ta m ble & C sign Diagram om Ana p u l ys tat is ion Bid / Aw ard d Job D es i gn ed Br id ge

O PE R A TI O N

e

g Brid

TI C U R ST N O C

Op

d r a te

V

XM L

L XM

CS

TXT

Information Workflow

CS

V

L XM

V CS

SV /C L XM SV L/C XM

BA RS

/LA RS

Information Workflow Concrete Alternate InRoads XML

Highway Geometry Data

Cost Estimating & Bidding

BridgeWare/ Opis Superstructure design

Virtis

XM L

Pontis XM

LEAP Bridge GEOMATH Alignment

CS V

L XM

LandXML

Estimating Link

MS Project CSV

Project Scheduling

V CS

BridgeWare Pontis

V CS

L

SAP2000

TEKLA

Seismic Analysis

3D Model 4D (Construction Scheduling)

TXT

BridgeWare Virtis XML

L/ C XM

SV

SV L/C M X

Maintenance Opis

Virtis

Rating

CONSPAN RC-PIER

Opis

Pontis

BA RS /L

AR S Superload

Routing & Permitting

METHOD OF DATA EXCHANGE TXT – TEXT FILE XML – EXTENSIBLE MARKUP LANGUAGE LANDXML – LAND EXTENSIBLE MARKUP LANGUAGE VBA – VISUAL BASIC FOR APPLICATIONS CSV – COMMA SEPARATED VALUES BARS/LARS – AASHTOWARE AND BENTLEY SOFTWARE

Benefits: In general, the benefits of an integrated system come from accomplishing tasks better, faster and more economically.

Description p

Better

Avoid error-prone manual data re-entry

X

Avoid errors due to inconsistent information

X

Leverage g design g data into construction and beyond

X

Can avoid physical pre-assembly Accelerated construction via prefabrication

X

Faster Economical i l

X X X

X

X

X

X

X

Types of Benefits cited by Other Industries • Tangible Benefits: • Faster F t project j t delivery d li • cost savings

• Intangible Benefits: • Process and work-flow re-engineering g g • supply-chain integration • risk management and claims mitigation

Types of Benefits cited by Other Industries (cont’d) (cont d) • Quasi-tangible Benefits:  Improved I d data d t availability il bilit  complete audit trail  reduced data entryy and improved p information management  reduced rework  improved timely design and construction decision making  improved quality of construction

Model Developed: Concrete

M d l Developed: Model D l d Steel S l Alternate Al

The Conundrum  Electronic Data Transfer/Translation among the th various i “i “islands l d off automation” (stovepipes) 

“If there th is i an industry i d t - wide id standard t d d ffor electronic data exchange of (life-cycle) bridge data that is non-proprietary, p p y, we will gladly g y write translators for it” – a software solution provider

Commercial Software: Linkage Approaches • • • • • • • •

DLLs (e.g. WSFL – QCONBRIDGE) VBA (e.g. Bentley, MS Office (Excel)) C#/ NET/API (e.g. C#/.NET/API (e g Tekla Tekla, BridgeWare CSI/SAP2000, CSI/SAP2000 Bentley BrIM Apps) C/MDL (e.g. Bentley) CIS/2 (e.g. (e g Fabtrol) XML (e.g. Access, MathCad, LEAP, AASHTOWare Opis/Virtis/Pontis) IFC (e.g. (e g Timberline Estimating) Direct (e.g. SAP – Tekla, EstimatingLink – MSProject, etc.)

Fundamental Principles p  The 3D – centric approach conceptually boils down to two distinct principles that must be enforced consistently and according to appropriate standards:  Nobody drafts anything (model it in parametrically in 3D instead). )  Enter each given data entry item only once.

 Thus:  Drawings, if needed, can be generated from the 3D model whenever possible, and  Electronic data exchange is required between current “islands of automation” (a.k.a. “stovepipes”).

Preliminary Design

Preliminary Design (cont’d) e.g., parametric design inputs (MathCAD Calculation Sheet for Preliminary Design)

e.g., 2D view generated from inputs

Final Design

Final Design, cont’d 3D model (Bridge Deck Modeling in Tekla )

(A Drawing Created by Tekla )

2D dwgs

Construction (Estimating/Scheduling)

Construction (Estimating/Scheduling) cont’d “4D” 4D Schedule Control

Estimates Model Quantities

Construction (Fabrication/Erection) Co Sc nstr he uc du tio lin n g 4D Di M o ag de ra l m

M

XM CS L V

Te k S la (4 Pr D oje ) ct

Construction (Fabrication/Erection) cont’d Fully detailed model

CNC Export

Bridge Operations (Load Rating)

Bridge Operations (Load Rating) cont’d Check beam definition Detailed Spec Computations  Load Rating reports

Bridge Operations (Routing/Permits)

Bridge Operations (Routing/Permits) cont’d Permit Appl. R ti Routing

Bridge Management (Inspections)

Manag

e tain

dB

ridg

e

ble Ta ta Da & ram ag Di on cti ce pe an Ins nten i Ma

in Ma

e me n t

able Data T & am Diagra

a re EW ) IDG BR Pontis (

are EW IDG BR API

BrIM Data Pool

Inspection Data: Girder Section Loss • Section loss data can be attached in Pontis:

Girder Section Loss Data Inputs in Virtis

1. The program is developed by C# in Visual Studio; 2. It calls BRIDGEWare APIs to update the section loss data

Bridge Management (Programming)

BrIM Data Pool

BR

Da ta Pr og

ram

IDG EW a re AP I

BR IDG (Po EWar e ntis )

Ta b

le

Data T able & Diagra m

mi ng

Report in Ma

inta ine

dB ridg

e

g / NB

I

V

XM L

L XM

CS

TXT

S01 InRoads to MathCAD

CS

V

L XM

V CS

SV L/ C M X SV L/C M X

BA RS

/LA RS

36

S01 InRoads to MathCAD Loading alg file: 6 pairs of horizontal and vertical alignments

37

S01 InRoads to MathCAD This picture shows 6 horizontal alignments

38

S01 InRoads to MathCAD Details of horizontal and vertical alignments

39

S01 InRoads to MathCAD Save alignments data as txt files

Text file

40

S01 InRoads to MathCAD Sample text file

41

SB-LRT NB-LRT

Quincy Ave SB I-25 to NB I-225 SB25

NB25

42

S01 InRoads to MathCAD The MathCAD file used for alignments d i design

43

S01 InRoads to MathCAD Highway Inputs: input text files

The input text files here are all exported from InRoads. 44

S01 InRoads to MathCAD Details of MathCAD files Some basic parameter inputs of the project. project

45

S01 InRoads to MathCAD Details of MathCAD files Shows th Sh thatt the alignment files from InRoads are all imported correctly.

46

From MathCAD to Tekla

47

Substructure Location Inputs:

Superstructure Design Inputs:

After import the alignment data, we can input the design parameters of bridge itself. 48

Girder Design Inputs:

49

Export XML Linkage File

Export data into XML file  in MathCAD …

This xml exporting functionality is developed.

50

Import Xml File into Tekla

This program is developed by C# in Visual Studio. It reads the bridge data in xml linkage file just exported from MathCAD sheet and calls Tekla’s APIs to build 3D model automatically.

Choose the XML file just  Choose the XML file just exported…

51

The Tekla 3D Model Automatically Generated

Output model snapshot from Tekla Structure:

52

The Tekla 3D Model Automatically Generated ((cont.’d))

Output model snapshot from Tekla Structure:

53

Concrete Alternate InRoads XML

Highway Geometry Data

Cost Estimating & Bidding

BridgeWare/ Opis Superstructure design

Virtis

XM L

Pontis XM

LEAP Bridge GEOMATH Alignment

CS V

L XM

LandXML

Estimating Link

MS Project CSV

Project Scheduling

V CS

BridgeWare Pontis

V CS

L

SAP2000

TEKLA

Seismic Analysis

3D Model 4D (Construction Scheduling)

TXT

BridgeWare Virtis XML

L/ C XM

SV

SV L/C M X

Maintenance Opis

Virtis

Rating

CONSPAN Opis

RC-PIER

Pontis

BA RS /L

AR S Superload

Routing & Permitting

METHOD OF DATA EXCHANGE TXT – TEXT FILE XML – EXTENSIBLE MARKUP LANGUAGE LANDXML – LAND EXTENSIBLE MARKUP LANGUAGE VBA – VISUAL BASIC FOR APPLICATIONS CSV – COMMA SEPARATED VALUES BARS/LARS – AASHTOWARE AND BENTLEY SOFTWARE

C09 LEAP to MicroStation 3D

Project profile fil iin LEAP Bridge

3D view of Quincy Avenue Bridge model d l

2D view of superstructure: Plan view, side id view i and section view

2D and 3D views of substructure

Export 3D model to MicroStation file: * d fil *.dgn file

Open MicroStation and load dgn file fil

Views from LEAP: plan view, side view, front view i and d 3D view

MicroStation 2D Drawing Generation

C16 MicroStation Drawings

Microstation drawings exported f from LEAP: LEAP plan view, side view, front view and 3D view

Plan view off Quincy Q i Avenue Bridge exported from LEAP. Base on this draft draft, user can make some modificatio ns

Modification step t 1: 1 delete some unnecessary lines

Modification step t 2: 2

Modification step t 3: 3

Modification step t 4: 4

C16 MicroStation Drawings Superstructure C Cross S Section ti of Quincy Avenue Bridge exported from LEAP

C16 MicroStation Drawings Modification step t 1: 1

C16 MicroStation Drawings Modification step t 2: 2

C16 MicroStation Drawings

Modification step t 3: 3

Summary/Overview • Developed prototype illustrating data exchanges h ffor entire ti bridge b id lif life cycle l • Utilized 3D bridge information modeling (B IM) to (BrIM) t accelerate l t project j t delivery d li and d enhance life cycle management • Demonstrating viability, viability efficiencies efficiencies, and benefits of integrated bridge project delivery and life cycle management concept through one-half-day and two-day presentations

Acknowledgements  NCHRP, Mr. D. Beal, P.E., and Dr. I. Jawed, Program Officers; FHWA FHWA, Dr Dr. P P. Yen and Mr Mr. K K. Verma, Verma P.E., PE COTR’s (the latter for Current FHWA Contract: Integrated Bridge Project Delivery & Life Cycle Management DTFH61-06-D-00037)  Collaborators: A. M. Shirole’, T. Riordan, J. Puckett, Q. Gao H. Gao, H Hu., Hu I.-S. I -S Ahn, Ahn R. R Patil, Patil K. K Potturi, Potturi N. N Kannan, Kannan J.JW. Li, V. Tangirala  Bentley Systems, Inc.  Various Academic Software Discounts and Tech Support

Q1: Which of the following g is true? A. Software interoperability is key to realizing the potential benefits of BrIM. B. “Who owns the model?” liability y concerns have been solved. C Bridge owners are at the mercy of C. commercial software providers.

Q2. Which data format(s) are used in the described work? • • • • • •

XML CSV Plain text DGN All off th the above b None of the above

Q3-6: T/F T/F: BrIM is another name for 3D CAD. T/F: Generation of contract plan sheets from the model is automatic. T/F: Engineers are no longer needed, since software can automate data transfers transfers. T/F: Building Oriented BIM software can be used “as as is” is for bridges