Deploying Mobile Construction Inspection Forms as a Case Study for Technology Adoption

IPC2016-64637Brett Vogt, P.E.

Inspection Forms• Regulatory Importance• Construction Management Data Point• ~80% of documentation produced

during construction• Managed with archaic systems and

processes• Reporting errors• Systematic issues

Inspection Reporting• Reporting Errors

• Missing data• Typos/errors• Incorrect reports

• Systemic Weaknesses• Disaster recovery• Overwriting data• Transmission over email• Handwriting• Scanning

Barriers to Adoption• Pipeline construction culture• Perceptions of performance

improvements• Effort required to use a system• Technical support• Upper management support• Individual resistance to change

Addressing the Barriers• Fundamental improvement in data

collection and reporting• Core requirements gathering from

field and office stakeholders• Agile development process with pilot

releases to actual users• Automating workflow portions• Simple, familiar interface for field

users (paper-like)• Management support with higher

data quality, access, and aggregation

Case Study Details

Project Maximum Users

Operator State

1 32 A WY

2 42 B PA

• Two projects• 13,542 Inspection Reports

Case Study Implementation

Deployment Process• Pre-configure system for

inspectors with project data from project management

• Provide on-site training for inspectors

• Customize report review workflow to inspection team

• Provide on-site support resources and access to developers for code-level bugs identified

Deployment Results• Decreased time and effort authoring

and reviewing reports• Inspector: “from 2 hours to 20 minutes”

• Decreased time and effort for building inspection reports

• 98% positive system reviews from survey regarding system deployment

• 67% reduction in time to properly file inspection reports

• Increased time performing inspection activities

• Reduce office manager data completeness review to almost zero

Forecasting Results• Quantitative Predictions Forecast Average

ErrorStandard Deviation

Trailing 7 Day

4.5 days 3.5 days

Trailing 14 Day

2.7 days 2.1 days

Trailing 30 Day

0.7 days 0.5 days

• Graph depicts mainline firing line forecast error to 95% completion over time

Elements for Technology Adoption Success• User-focused design• Responsive support by pipeline Professionals• Planning for culture change

Thank youBrett Vogt, P.E.

Traceability & Records Management ManagerProject Consulting Services, Inc.