Presentation is loading. Please wait.

Presentation is loading. Please wait.

Dave Adamson. 2009 Design Network launched 2 years ago Had many good ideas Discipline tracks Activity ownership Milestone meetings Promised “Not Static”

Similar presentations


Presentation on theme: "Dave Adamson. 2009 Design Network launched 2 years ago Had many good ideas Discipline tracks Activity ownership Milestone meetings Promised “Not Static”"— Presentation transcript:

1 Dave Adamson

2 2009 Design Network launched 2 years ago Had many good ideas Discipline tracks Activity ownership Milestone meetings Promised “Not Static” Based on project teams feedback, Network need further refinement Dave Adamson

3 Established December 2009 Formalize Delivery Network change process Mission Statement: To Solicit, initiate, advocate, review, prioritize and approve changes to all delivery networks Dave Adamson

4 Paul Egbert – R1 Design Nathan Peterson – R1 PM Dave Schwartz – R2 Preconstruction Matt Zundel – R2 PM Patrick Cowley – R2 Design & QC/QA Brent Schvaneveldt – R3 Preconstruction Bill Townsend – R3 Design Jared Dastrup – R4 Design Daryl Friant – R4 PM Carmen Swanwick – Central Structures Jesse Sweeten – Central Preconstruction Craig Hancock – Central ePM Lori Dabling – Central PM Dave Adamson – Central PM Neil Sharp – Consultant Support Staff (Stanley) Dave Adamson

5 Develop network framework Stages & Milestones Meetings (Major Team) Scoping > Geometry > Plan in Hand > PS&E > Advertising ^ ^ ^ ^ ^ Kickoff Geometry Plan in PS&E Comment Scoping Hand Resolution

6 Then put “meat” on framework Worked with Disciplines Developed Deliverables Attached Deliverables to Activities Fit Activities into Stages Dave Adamson Bottom Up Construction Deliverable 1 Deliverable 2 Deliverable 3 Deliverable 4 Activity 1 Activity 2 Scoping Stage Activity 3

7 Just a Template or Guide Not a true “Dependency Diagram” Documentation details deliverable distribution Best described as a “Work Flow” process Dave Adamson

8 Can skip meetings and/or activities Needs of project come first Warning – understand consequences Key deliverables and QC/QA Network flexibility Just because the network shows that you can start an activity doesn’t mean that you should ROW can start just after Scoping Dave Adamson

9 Fewer network activities! (from 156 to 98) QC/QA (Explained later) Milestones (separate from meetings) Comment Resolution Meeting Design Leader Track Additional discipline tracks ROW parcel submittals tracking Individual structure tracking Dave Adamson

10 Back Separate from Stage Meeting PM designates Milestone completion after: Completion of all stage activities Resolution of issues from “end of stage” meeting Planned and Actual milestone dates will be tracked and reported Dave Adamson

11 Back Dave Adamson

12 Back The Design Leader is primarily responsible for all technical coordination and communication necessary to compile the project Plans, Specifications, & Estimate All other management duties and coordination default to the Project Manager unless assigned to the Design Leader through negotiation with the Project Manager Dave Adamson

13 Back 1 st Submittal 2 nd Submittal 3 rd Submittal 4 th Submittal Dave Adamson

14 Back 10 Bridge Activities 4SA….4SJ 10 Minor Structure Activities 4SM….4SV Dave Adamson

15 Network Diagram fits on one page Activity quick-link Table Deliverables lists for each activity Task lists for each deliverable Customizable Network Diagram Activity Numbering system Dave

16

17

18

19

20 For example - for activity 3G2. “3” - Indicates the activity is to be completed before Plan-in-Hand Stage meeting “G” - Identifies it as Geotechnical discipline track “2” - Is the activity identifier within the stage and discipline track. Some Structures and ROW activities vary from numbering system due to multiple tracks and ePM system constraints Dave

21 Scoping Geometry Plan-in-Hand Plans, Specifications & Estimate (PS&E) Advertising Brent & Bill

22 Project Setup Team selected and organized Review existing information ID additional required information Determine Project Scope, Schedule and Budget Determine the design effort and a strategy Negotiate and Set resource budget and schedule Brent & Bill

23 Develop initial roadway model. Recommended Horizontal and Vertical alignments. Identify preliminary cut/fill lines and initial ROW impacts Disciplines: Coordinate to identify potential impacts. Develop preliminary designs and conduct testing. Compile cost estimates. Environmental identifies resources and conducts research. May begin ROW (if appropriate) Brent & Bill

24 Roadway model is finalized Environmental Categorical Exclusion Document is written and approved Permitting process is started ROW design, appraisals and acquisition in progress Utility Design completed Agreements initiated Disciplines Finalize designs Update Estimates Develop preliminary plan sheets Brent & Bill

25 Design Detail plan sheets developed and finalized Final plans produced Project documents finalized Reports Special provisions Cost estimates Summary sheets, etc. ROW acquisition Complete (in a perfect world) Utilities Agreements complete Plans and documents complete Brent & Bill

26 PS&E revisions completed Comment Resolution meeting Project advertisement package is compiled Certifications & Permits Storm water pollution prevention plan (SWPPP) Structures Acceptance ROW Certification Traffic & Safety Certification Utility Certification Environmental Permits Brent & Bill

27 Questions Documentation is found at: www.udot.utah.gov/go/pdn Dave Adamson

28 QC Policy QC/QA Procedure Project Delivery Network QC Checklists UDOT QC Audits

29

30 Each Deliverable is Checked or Reviewed BEFORE distribution Color Code / Check Print Stamps Documentation - Cover Sheets/Certification QC Checklists Project QA Audits Alternate QC/QA Procedures Form

31 4 Categories of QC Checks Design Calculations Computer Program Input Drawings Project Documents Independent Technical Review Review Comment Resolution Form QA Audits

32

33 Example: Sample Calculation QC Review

34 Cover Sheets Certification

35 Review Comment Resolution Form Each discipline responsible for their comments Initial Disposition – After all comments compiled, provide initial disposition (response) before end of stage. Final Disposition – After comments are incorporated or further evaluation completed. Distributed with next review package. Verify comment resolutions completed before final disposition distribution.

36 Project QA Audit The QA Reviewer verifies the QC documentation is complete. Performed before each Milestone Meeting Submit QA Audit Form

37

38 Questions Documentation is found at: www.udot.utah.gov/go/qcqa Dave Adamson


Download ppt "Dave Adamson. 2009 Design Network launched 2 years ago Had many good ideas Discipline tracks Activity ownership Milestone meetings Promised “Not Static”"

Similar presentations


Ads by Google