33
Edwin Elmendorp – Kinsmen Group Robert Ridgell – VDOT

0 Edwin Elmendorp Kinsmen Group Robert Ridgell VDOTiheep2018.com/docs/Presentations/E-Construction Confessions from... · Design Builder Portal For Review Project Private Portal Design

Embed Size (px)

Citation preview

0

Edwin Elmendorp – Kinsmen Group

Robert Ridgell – VDOT

• Introductions

• e-Construction why?

• Solution Framework

• e-Construction on the RRC Project

• Independent service provider for Engineering Information Management

• Wide range of services• EIM Strategy & Consulting

• Document Control & Onboarding

• Software Implementations & Support

• 20+ Senior Professionals

• Virginia has the third-largest state-maintained highway system in the country, behind Texas and North Carolina.

• 7500 Employees

• 57,867 Miles maintained by the state

• 14 Active PPP projects

• 271 projects in development

• 221 projects in delivery

Source: http://www.virginiadot.org/dashboard/projects.asp

Keeping track

e-Construction is the collection, review, approval, and distribution of highway construction contract documents in a paperless environment

• Source: McKinsey research 2017

• Less than 25 percent of construction firms matched the productivity growth achieved in the overall economies, averaged at 1 percent, compared to 2.8 for total world labor productivity over the last 2 decades

• One third of the opportunity is in the United States, where, since 1945, productivityin manufacturing, retail, and agriculture has grown by as much as 1,500 percent, but productivity in construction has barely increased at all.

• Source: McKinsey research 2017

• Examples of innovative firms and regions suggest that acting in seven areas simultaneously could boost productivity by 50 to 60 percent.• reshape regulation;

• rewire the contractual framework to reshape industry dynamics;

• rethink design and engineering processes;

• improve procurement and supply-chain management;

• improve on-site execution;

• infuse digital technology, new materials, and advanced automation;

• reskill the workforce.

• Source: FHWA Roi e-Construction PennDot - FHWA-HRT-16-068 – 2016

Let Technology do the heavy lifting

1. How do I know who is doing what, why and the deadline?

2. How do I share and collaborate information?

EXCEL HELL

• One drive

• Google drive

• We-Transfer

• Box

• Dropbox

• Dropmark

• TransferBigFiles

SendThisFile

OneHub

EgNyte

4Shared

• Sugar sync

• Hightail

• Dropcanvas

• Minus

• Dropsend

• FTP

Send Space

Itrnsf

DropLr

CloudApp

Gett

MediaFire

• Clearly define business requirements upfront

• Define solution architecture and roadmap

• Don’t be blinded by a single vendor

• Assess your current needs and capability• FHWA self assessment

• Kinsmen EIM maturity assessment

• Resources:

https://www.fhwa.dot.gov/construction/econstruction/library.cfm

Design Builder Portal Project Private PortalFor ReviewDesign Builder Portal

Shared Portal

Submit / Respond

Approved / FinalFor Information

• The Design Build PM group adopted a standard filing structure across all DB projects

• Standardized reports

• Extensive comment and review workflow

• Setup and training efforts:• New project – about 1 day of setup

• New PM training – about half a day

• New Reviewer training – about 1 hour

• New Design Builder training – about 1 hour

Project Fast Facts• The project seeks to reduce I-95 congestion by:

• doubling I-95 southbound capacity in the Fredericksburg area between approx. MM135 to 129

• dividing traffic into separate lanes for the Route 3 and Route 17 interchanges, and general purpose lanes

• Adds three additional lanes of I-95 southbound in the existing I-95 median beginning just north of Route 17 and ending just south of Route 3, including new Rappahannock River Crossing

• Includes interchange ramp modifications at Route 3 and Route 17

• Replaces two existing structurally deficient SB and NB I-95 bridges over Route 17 and improves height restrictions on Route 17 under I-95

• Contract Value: $101.6 Million; Overall Budget $131,851,099.42

Project Challenges• Project team consisting of 6 plus parties including:

Project Challenges• Large (30+) person review staff spread across various disciplines

• 4 Separate Bridge Plan Packages

• Multiple Roadway Plan Iterations

• Early Works Packages

• Complex Maintenance of Traffic Planning for busiest corridor in the Nation

• Compressed Schedule

• Approximately 5 mile long project area

• Significant amount of night work

• 3 level of testing and inspection, Quality Control, Quality Assurance, Owner IV

Project Mitigations• Communication, Communication, Communication

• Partnering

• Thorough Record Keeping

• Document Management

• Clear Workflows

How CADAC Fit the Need• CADAC worked with VDOT Construction staff to develop workflows that fit our

process.

• Trainings and workshops provided feedback to improve the system.

• Allowed review comment aggregation in a relatively familiar format.

• Allowed timestamping and recording of transmittals.

• Used existing Department resources such as Sharepoint

• Allowed for compilation of final records set and transfer to Department systems for record retention

Typical Submittal

Final Documents

Lessons Learned• User involvement in development

• Continued development of field accessibility and use

• Flexibility to submit various document types and adapt to project needs while maintaining file structure integrity

• Speed and reducing waiting time for better efficiency

• Handling of final documents

• Accessibility for read only executive users who may quickly need certain information

• Browser Compatibility and Sharepoint Versions

• Dashboards, metrics, and performance

Recommendations• An electronic system can’t improve bad project communication, ensure

interpersonal communications are good to start with.

• Don’t assume experience levels or comfort with software solutions. Foster a collaborative team approach to facilitate making each user a trainer.

• Avoid dumbing down to the lowest common denominator.

• Ensure that the workflow is compatible with electronic documentation, look for new efficiencies and eliminate waste.

• If something isn’t working say something and be part of the solution.

• Build a solution starting with the end user and work up.