chief roadway standards & methods engineer - · pdf filemodel-centric design...

Jerry Zogg, P.E.Chief Roadway Standards & Methods Engineer

Wisconsin Dept. of Transportation

1

Model-Centric Design ImplementationBackground & OverviewThings That Have HelpedChallenges so FarLessons LearnedChallenges Going Forward

2

Previously Used Dual PlatformsCAiCE – DesignMicrostation – Plan & Plat Prep

300 – 400 In-House Users

Decentralized Design in 8 Region Offices

3

2007 Select Civil 3D2007-10 Prepare for Deployment

Develop Design Model Work FlowsPrep Work for Civil 3DDevelop Video-Based Training

Jan 2010 Initial Civil 3D Deployment to “Early Adopters”2010 Allow use of AMG Statewide – Contractor OptionFall 2010 Begin Deployment to Remaining Design Staff2011 to Present

AMG Model Sharing Pilots

4

2012 Communicate Inhouse & Consultant GoalsInitial Models focused on AMG SurfacesEstablish July 2014 for Full Implementation

Fall 2013 Confirm AMG Model Reqmts w/ ContractorsSpring 2014 WisDOT/ACEC Develop Delivery ReqmtsSpring 2014 WisDOT Publish Reqmts for Overall Project

Delivery and Design ModelsJuly 2014 Design Policies for Full Implementation Became

EffectiveFall 2014 WisDOT/ACEC Assess Extra Work to Deliver

Design ModelsFall 2014 Conduct Region Outreach

5

Model-Centric Design Implementation Background & OverviewThings That Have HelpedChallenges So FarLessons LearnedChallenges Going Forward

6

1. Department Support for Model-Centric Design2. Team Dedicated to Implementation3. Set & Communicate Initial Statewide Objectives4. WisDOT’s 3D Technologies Implementation Plan5. Two Concurrent Design Model Implementation

Efforts Underway6. Robust Training System

7

Department Support for Model-Centric Design Upper ManagementConvinced Use of Design Models is InevitableActually Encouraged ImplementationSupport has helped weather some storms

Department Provision of both:StaffFunding

8

Team Dedicated to Implementation: WisDOT Methods Development Unit (MDU) Implementation Consultants Software Vendor Professional Services Staff

Combined MDU and Consultant Team consists of: Lead worker 3 to 4 staff: Design development and support 1 to 2 staff: CADD development (plan & plat) and

support 2-3 staff: Primarily support focused

9

Set & Communicate Initial Statewide Objectives: Initial goal for use of Design Models is to provide

surfaces only for AMG. Needed foundation and crucial for determining: Software functionality to implement initially Initial delivery requirements

Provide and get buy-in of 2-yr timeline for full implementation from both: Region Management and Production Staff ACEC - WI

10

• Initial survey • Design• Contracting• Construction• As-built survey• Other applications

in infrastructure lifecycle

WisDOT - 3D Strategic PlanVision:Adoption of 3D methods and seamless data flows throughout:

11

WisDOT’s 2013 3D Technologies Implementation Plan:1. Height Modernization Program (active and passive network)2. LiDAR and Digital Mapping Data Acquisition 3. Utilities4. Information and Technology Infrastructure5. Roadway Lifecycle Uses of LiDAR data6. Statewide 3D Design Process7. Southeast Freeways (SEF) 3D Design Process8. Automated Machine Guidance (AMG)9. Southeast Freeways Field Technology and Inspection

Things That Have Helped

Two Concurrent Design Model Efforts Underway

Southeast Freeway (SEF) Effort Focused on advancing the use of Design Model concepts

beyond AMG surfaces thru the use of other innovative software and devices to assist in delivering SEF’s mega-major projects

Statewide Effort Focused on implementing Civil 3D

and Model-Centric workflows in allRegion offices statewide

13

Construction Field Tablet PCs & Rovers Use Material Test Results w/Geospatial Locations/USB Bar Code Readers Real-time Earthwork Quantities/Earthwork Finals Real-time Critical Clearance, Conflict Detection & Visualization Inspector Field Notes/Photos/Issues ID & Resolution Real-time Locating/Coordinating Utilities Plan Navigation (Location Awareness) Plan/3D Model Verification & Visualization Depth Checks/Critical Clearance Surface/Elevation Checks Verification Survey Sign/Signals Placement Real-time As-Built

14


Southeast Freeway (SEF) Effort Focused on advanced “downstream” use of Design Models in

the latter stages of design and in construction

Statewide Effort Focused on the “upstream” efforts

to create Design Models containing surfaces for use in AMG technologies

15


Southeast Freeway (SEF) Effort “Innovation Incubator” Doing proof of concept efforts of both software and hardware Has helped Statewide Effort to look to the future

Statewide Effort Work to support and enable SEF efforts Determine which SEF practices are appropriate for statewide

use and when to implement

16

Robust Training System Self-paced, Video-Based, Training with Documentation 6 different curriculums Survey Design Plan Prep Plat Prep Project Managers/Supvs Construction Administration

Significant update and expansion being planned Supplemented with monthly region user group visits

17

Model-Centric Design Implementation Background & OverviewThings That Have HelpedChallenges so FarLessons LearnedChallenges Going Forward

18

1. Changing the Culture to Implement Both:a. New Design & CAD Softwareb. New Model – Centric Workflows

2. Changing Software Platforms3. Balancing Software Development with Support &

Training4. Early Adopters Disappeared5. Staying Current with Software6. Determining Extra Work and Costs

for delivering Design Models

19

Changing the Culture Changing the mindset of veteran staff to learn both: New Software (tool) New Deliverable (Design Model)

Traditional 2D PSE is now a byproduct of Design Model, not primary deliverable

Takes awhile for the “AHA Moment” to occur Some staff not completing training to

fully understand workflows for new deliverable

20

Changing SoftwarePlatforms A tremendous amount of

work, especially for CADD Started to deploy without all

CADD standards complete Without all the previous templates & tools, it felt like we

were “taking a step backwards” Took a year to complete everything needed for plan and

plat preparation

21

Balancing Software Developmentwith Support and Training Both efforts very important Both efforts compete for same resources Benefits to development team to provide support Support can be a huge wild card – hard to predict Development plans can be significantly impacted Now, trying to primarily dedicate staff to one or the

other

22

“Early Adopters” Disappeared (Didn’t see that coming...)

Lost “go-to” staff and support within Regions Back to “square one” Needed to prop up staff to deliver projects and keep

implementation going by helping to provide onsite services: Certified trainers – knowledge of tool/software Combined highway design/3D model assistance

23

Staying Current with the Software is aMajor Effort Software is very dynamic and

version upgrades are extensive

As a result, version upgrades: Are very time consuming to test and

implement Create many challenges with projects underway

Upgrading versions every other year

24

Determining Extra Work and Costs forDelivering Design Models Joint Effort with ACEC to develop: Qualitative list of extra work tasks Hourly estimates of each task

Extra work is related to either: Additional/more complete design – majority of cost Mechanics of creating and maintaining the model

during design Providing info to estimating teams & consultants

and assisting with initial negotiations

25


26

1. General Transition2. Switching Software3. Model-Centric Design4. Get and Stay Connected with Contractors

27

General Transition Begin deployment before everything is “perfect”. Need feedback from production areas Can make course corrections along the way.

Can’t effectively develop work plans much beyond 12 month timeframe. “Feeling your way through” implementation Software is dynamic Perspectives/Insights will change Easier to figure out the details when you get closer

28

Switching software Don't focus on replicating old workflows. Analyze the best workflows in the software's

native functionality and use them. The transition learning costs will be far smaller in

the long run than creating and maintaining custom macros and configurations to replicate old workflows.

29

Model–Centric Design Truly designing in 3D (not just attempting to build 3D surfaces at the

end of standard 2D workflows) is necessary/preferable for the following reasons: 3D surfaces ready for automated machine guidance (AMG) are far

more detailed than a merger of cross-sections. If surfaces are going to be a deliverable, workflows with that product in

mind need to be utilized. Timing of surface development is the same as for cross-sections. Surfaces should be started, refined, and completed in the same

timeframes that cross-sections would normally be done. Surfaces must be reviewed to ensure that they are being developed

properly. Like any other design deliverable review,

30

Model–Centric Design Adds to design costs Additional/more complete design – major cost Need to continue to improve software and develop more

efficient workflows Mechanics of creating and maintaining the model during

design Lowers construction costs Thru use of AMG and other

technologies Reduces contractor risk

31

Get and Stay Connected withContractors Coordinate early Conduct model sharing pilots to get their feedback We learned that not all contractors using AMG

technologies the same way: WisDOT will not provide 100% construction ready models Will improve workflows and put more emphasis on breaklines Will put less emphasis on surface refinement

Continue to check-in

32


33

1. Keeping Everyone Informed2. Next Steps Beyond Initial Implementation3. Issues Not Directly Related to Design &

Construction Engineering

34

Keeping Everyone Informed Communicating latest ideas in what is becoming an

increasingly more complex environment Very dynamic environment for software and workflows Insights/Perspectives/Goals/Direction changes PM’s, Supvs, & Managers do not have hands-on experience with: Deliverables Tools Increasing complexities may require greater need for

specialization

Will conduct Outreach in Region offices this fall

35

Next Steps Beyond Initial Implementation Expect to see “pockets” of increased statewide appetite for

further enhancements to and use of the model: Visualization clash detection Scheduling Asset management, etc

Satisfying these increasing appetites while maintaining development and support of our initial/basic functionality for majority of users will be challenging

36

Next Steps Beyond Initial Implementation Integrate engineering reviews of Design Models into our

standard practice Requires software to view and move around in 3D Staff with review roles not familiar with models, design software, or

review software Continued consideration of making Design Models contractual Meeting user expectations in a digital society used to seamless

software operation, instant answers to their questions, etc

Will be doing another round of goal setting for added functionality

37

Issues Not Directly Related to Design &Construction Engineering Many Open Questions What is the role of the Design Model vs. the As-Built

Model for post-construction (asset management) use? Project archival, accessibility, and future usability? Managing and sharing files and data? IT infrastructure, Cloud Services, Storage?

Technology is dynamic, so IT solutions will change

38

WisDOT Model-Centric Design Implementation

For more information contact: Jerry Zogg, [email protected] (608) 266-3350

chief roadway standards & methods engineer - · pdf filemodel-centric design...

Documents