1 / 26

Implementing a Model Based Approach to Design at Wisconsin DOT August 21, 2012

Implementing a Model Based Approach to Design at Wisconsin DOT August 21, 2012 WisDOT Methods Development. Topics. WisDOT Civil 3D implementation status WisDOT model oriented design workflow Implementing 3D Surface Model Deliverable Future of Roadway Models at Wisconsin DOT

adia
Download Presentation

Implementing a Model Based Approach to Design at Wisconsin DOT August 21, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing a Model Based Approach to Design at Wisconsin DOT August 21, 2012 WisDOT Methods Development

  2. Topics • WisDOT Civil 3D implementation status • WisDOT model oriented design workflow • Implementing 3D Surface Model Deliverable • Future of Roadway Models at Wisconsin DOT • Implementing Civil 3D Specific Delivery Requirements

  3. WisDOT Model Concept Definitions • 3D Surface Model • Produced for projects with Grading work • Includes surfaces for AMG operations of Grading, Base Course, and Paving • Initial model deliverable requirement will be 3D Surface Models • Roadway Model • Evolution of model concept to include information for increased utility in design and construction processes, and ultimately expanded to downstream roadway lifecycle processes

  4. WisDOT Civil 3D Implementation Status • Deployed Civil 3D 2010 in January of 2010 • 281 WisDOT staff have enrolled in Civil 3D New User Training (4-25-2012) • 8 Civil 3D design projects have submitted PSE • WisDOT’s First All-Civil 3D developed plan set delivered Nov 1, 2011

  5. WisDOT C3D Implementation – Upcoming Events • CAiCE Retirement by July 2013 • MicroStation Retirement by July 2014 • Next implementation objective: full utilization of Civil 3D functionality in our workflows • Plans Production workflow training • Survey Data workflow training • Quantity Takeoff functionality • Drainage Analysis

  6. WisDOT’s Current AMG & Model Practices • Develop & Pilot AMG Spec for Grading • Advisory Group, Stakeholder Workshops, Two Construction Seasons with Five Pilots • 3D Model Data Development and Exchange a Major Issue • AMG for Grading is Contractor Option Statewide • Contractors Producing 3D Models

  7. Model-Based Design Part of WisDOT Implementation of 3D Technologies inDesign & Construction Plan with Five Active Initiatives: Statewide Real-Time Kinematic GPS Network. DTM Data Collection. 3D Design. Automated Machine Guidance. Field Technology and Inspection.

  8. Requirements of the Design Workflow • Civil 3D Design Workflow goal to develop construction ready surface models during the design process • Must produce surface models with sufficient detail to support AMG operations • 3D Surface Model output must be synchronized with plan sheets

  9. Model Sharing Pilots 2011 – We’ll discuss in detail later today • Determine Benefits of Providing 3D Roadway Models at Pre-Bid. • Determine Utility of 3D Models for Bid Preparation. • Establish Requirements for “Construction –Ready” 3D Models Flowing from Design Process. • Includes Model Content and Format. • Field Test “Construction Readiness” of 3D Models. • Identify and Implement any Changes to Design Workflows Necessary for Achievement of “Construction Readiness” in 3D Models.

  10. Model Sharing Pilots Results – We’ll discuss in detail later today • Surface Model was used in bid preparation activity • Plan activities to greater level of detail, reducing uncertainties • Identify potential sites for borrow/waste, and communicate with property owners • Surface models were construction ready – validated design workflow • Model content changes • Add longitudinal breaklines as visual aids for operators • Add surfaces for all subbase layers • Staged models not needed for AMG operations

  11. 3D Surface Model Requirement • WisDOT will implement a 3D Surface Model Delivery Requirement on projects starting after July 2014. • Model content requirements and other details will be released Q4 of 2012.

  12. 3D Surface Model Content Concepts

  13. 3D Surface Model Content Concepts

  14. 3D Surface Model Content Concepts

  15. 3D Surface Model Content Concepts

  16. 3D Surface Model Content Concepts • Surfaces Exist Top Finished Base Course Subbases Datum Pavement • Surface model data density will be design speed dependent • Surface models must be synchronized with plan sheets • Additional content • Longitudinal breaklines • Horizontal alignments • Vertical alignments • Superelevation transition information • Fully staged model requirement will be decided on project-by-project basis

  17. Roadway Model Evolution • Ability to increase information included with the 3D Model will grow • Methods of accessing information will become easier • WisDOT looking to expand use of Roadway Models in: • Design • Construction • Integration with GIS • Operations • Maintenance • Planning

  18. WisDOT Goal for Roadway Models • As potential for Roadway Model uses expand, WisDOT will maximize utilization • WisDOT will need access to full function of design data to realize full potential of Roadway Models • WisDOT will ultimately require delivery of design software files pertinent to the final roadway design as delivered in PS&E

  19. Design Data Utilization Requirements • Data import into Civil 3D • Entire object family needed (Survey Data, Points, Alignments, Profiles, Surfaces, Pipes and Pipe Networks, Typical Sections, Sheets For Plans, Roadway Models, etc) • Direct Import process, will not require user manipulation

  20. Design Data Utilization Requirements • Objects, when imported into Civil 3D, will contain all the intelligence and functionality of their Civil 3D counterparts, and will be linked to their graphic representation • Objects will retain their ability to • react to each other like native Civil 3D data does • react to changing terrain conditions • adhere to WisDOT design standards

  21. Design Data Utilization Requirements • Objects will correctly interact with Civil 3D design control tools • Design results in Civil 3D will be identical to design results delivered in the data’s native software

  22. How Can Our Roadway Model Goals Be Met? • To answer this question WisDOT has: • Learned more about how model design software functions & compatibility between software • Monitored “TransXML” Development • Monitored collaborative efforts between Bentley and Autodesk

  23. Roadway Model Design Software • Evolution of roadway design software: • Highly individualized • Each has unique approach to doing the design • Each uses proprietary formats that limits the ability to share design intelligence • Functionality to modify the design is: • Limited in non-native software • Unlikely to significantly improve

  24. Civil 3D Specific Design Delivery Requirements • Performance Base Alternatives considered, but ultimately abandoned • Civil 3D Specific delivery requirements will go into effect for projects solicited after July 2014

  25. Model Based Approach to Roadway Design • Civil 3D Implementation = New Design workflows • 3D Surface Model Delivery Requirements • Evolution of Roadway Model • Civil 3D Specific Project Data Delivery Requirements

  26. Questions??? Model Based Design as WisDOT Wisconsin Dept of Transportation

More Related