24
Local Failure Task 12: Bridge Data Exchange Protocols for Interoperability: Work-in-Progress Overview Stuart S. Chen, Ph.D., P.E., Hanjin Hu, M.S., S. Gokhan Karaman, Ph.D., & Najaf Ali, M.S. July 2012

Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Local Failure

Task 12: Bridge Data Exchange Protocols for

Interoperability: Work-in-Progress Overview

Stuart S. Chen, Ph.D., P.E.,

Hanjin Hu, M.S.,

S. Gokhan Karaman, Ph.D.,

& Najaf Ali, M.S.

July 2012

Page 2: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

1. Mission

2. Research Objectives

3. Research Tasks

• Literature and Practice Review

• Multi-Year Implementation Roadmap

• Analysis of Bridge Activities

• Identifying Information Items

4. Summary and Follow-up Actions

Outline

Page 3: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Mission

To facilitate development of bridge industry consensus standards for data description, modeling, and interoperability for integrated design, construction, and lifecycle management of bridges.

Page 4: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Research Objectives

This research is intended to develop, implement and demonstrate an efficient and robust digital data exchange protocol (file format) that could be used to automate the exchange of bridge information

• During project delivery and asset management including design, detailing, fabrication, construction, inspection, and evaluation

• “Workhorse” steel and concrete bridges

• In public domain and software neutral

• Collaboration of relevant software vendors for them to write “translators” to facilitate automated transfer of data

• Increasing stakeholders awareness via various means (webinars, workshops, etc.)

Page 5: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Research Tasks

• Subtask 12.1: Literature and Practice Review

• Subtask 12.2: Multi-Year Implementation Roadmap

• Subtask 12.3: Analysis of Bridge Activities

• Subtask 12.4: Identifying Information Items

• Subtask 12.5: Prototype 3D Viewer/Modeler

• Subtask 12.6: “Manual of Translator Development”

• Subtask 12.7: Demonstration Project

• Subtask 12.8: Training Materials and Reporting

Page 6: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Research Schedule

Page 7: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.1: Literature and Practice Review

Mission:

Extensive literature search and information collection to acquire/update various stakeholders’ practices and directions

Work Accomplished:

• Initial bridge suite assembled

• Initial representative steel and concrete bridges analyzed

• Initial survey of stakeholders re representative workflow / data exchange practice

• Survey of data model schemas and approaches

• Several state DOTs contacted to re technical developments in their bridge data management practices

Page 8: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.1: Literature and Practice Review

Work Accomplished:

• Survey of data model schemas and approaches, e.g.,

Page 9: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.1: Literature and Practice Review

Work Accomplished:

• Definition of workhorse bridges (based on inventory)

Page 10: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.1: Literature and Practice Review

Issues Encountered:

• Descriptive vs. Prescriptive

• Current (fragmented) vs. Envisioned (integrated)

Anticipated Upcoming

• Summarize initial survey results

• Survey additional stakeholders (Owners, Engineers, Fabricators, AASHTO, etc.)

• Monitor, interact with and influence related BIM/BrIM efforts (OpenInfra, IFC, ISM, etc.)

• Definition of workhorse bridges (current/anticipated practice)

Page 11: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.2: Multi-Year Implementation Roadmap

Mission:

A multi-year implementation roadmap for bridge information modeling in the national level will be developed.

Work Accomplished:

• Draft outline of objectives, methods, and outcomes was prepared

• Draft survey to engage software solution providers was developed

• Stakeholder meetings for possible co-located workshops were identified

Page 12: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.2: Multi-Year Implementation Roadmap

Issues Encountered:

• Cacophony of extant constituencies

• Need to host a ”home base” for communication (can use TG-15’s for some)

Anticipated Upcoming:

• Revised/expanded draft white paper(s)

• Tally results of survey of commercial bridge software solution providers

• Tally results & implications of various stakeholder engagements, e.g., AASHTO/NSBA TG-15, ABJ50, IBC June 11-13, AASHTO HSCOBS, IABMAS July 8-12, PCI/NCBC, OpenInfra (re IFC for bridges, int’l), ACI Committee 131), etc

Page 13: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.3: Analysis of Bridge Activities

Mission:

Understanding of data exchange requirements in various stages of project delivery and asset management

Work Accomplished:

• Initial steel and concrete bridge case study suite collected

• Process Maps developed for workhorse steel and concrete bridges

• several case study bridges delivery process examined and characterized

Page 14: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.3: Analysis of Bridge Activities

Work Accomplished:

• Process Maps developed for workhorse bridges (upper left portion shown)

Page 15: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.3: Analysis of Bridge Activities

Work Accomplished:

• Exchange Model Description

Page 16: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.3: Analysis of Bridge Activities

Work Accomplished:

• Exchange Model Specification

Page 17: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.3: Analysis of Bridge Activities

Issues Encountered:

• Synonyms, homonyms

Anticipated Upcoming:

• Enhancement/generalization via additional cases

• Vetting via expanded stakeholder engagement

Detailing Erection Procedure

Page 18: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.4: Identifying Information Items

Mission:

Collecting and classifying information items for each stage of data exchange, which provides the basis for data exchange (file) protocols

Work Accomplished:

• Data items ID’d for initial workhorse steel and concrete bridges

• Several “gap analyses” undertaken (e.g., IFC, ISM, O/V, etc.)

• Commercial software solution providers ”in the loop”

Page 19: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.4: Identifying Information Items

Work Accomplished:

• Data items ID’d for initial workhorse steel and concrete bridges

Steel Case Study Bridge

Concrete Case Study Bridge

Page 20: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.4: Identifying Information Items

Work Accomplished:

• “gap analysis” of ISM

Page 21: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.4: Identifying Information Items

Work Accomplished:

• “gap analysis” of ISM, IFC and Opis/Virtis

Page 22: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Subtask 12.4: Identifying Information Items

Issues Encountered:

• Several genres of gaps (e.g., bridge vs. non-bridge, analysis vs. physical, file format-specific vs. not, etc.)

Anticipated Upcoming:

• Analyze/abstract additional bridge cases

• Description of data protocol with digital file formats (options short list)

More Case Study Bridges

Page 23: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Summary and Follow up Actions

• Review/Critique EM exchange models in sample projects

• Review/Critique high priority use cases

- Roadway to structure

- Engineer to fabricator

- As fabricated geometry to support virtual assembly

- As-built construction handoff to operation and maintenance

Stakeholder Engagement re the above…

Page 24: Task 12: Bridge Data Exchange Protocols for Local Failure ...sp.bridges.transportation.org/Documents/SCOBS presentations 2012… · and robust digital data exchange protocol (file

Acknowledgements

• Federal Highway Administration through ATLSS

• University at Buffalo

• University of Engineering and Technology

• Istanbul Technical University

• Association for Bridge Construction and Design

• Bentley Systems and other Bridge Software Solution Providers

• etc