As-built Data Collection Methods - States present on progress and best practices

Committee on Right of Way, Utilities and Outdoor Advertising Control 2019 Annual Meeting Chattanooga, Tennessee April 28–May 2, 2019

As-built Data Collection Methods States present on progress and best practices

As-Built Data Collection Overview

1. Current Research and Proof of Concept Projects (SHRP2 R01A) 2. Mobile Application As-built for Permitted Utilities 3. Colorado Department of Transportation • Permitted Utility Installation As-builts • Construction Management of As-built data

SHRP2 R01A 3D Utility Location Data Repository (R01A) Locating, protecting, and relocating underground utilities can create significant delays to construction and utility services. Reliable and accurate data on the location and depth of utilities, and a storage system from which to retrieve the data, is necessary for efficient and cost-effective project delivery. Utility data is frequently not stored in accessible formats so that it can be saved and reused for future projects, causing agencies to recreate the data. A system is needed to store and retrieve utility data using enterprise technology that works with existing agency databases and systems.

Benefits of Data Management •The attribute data about each utility enables more efficient and productive coordination with utility owners.

•Knowing the location and depth of utilities enables designers to change designs to avoid costly utility relocation and delays in project delivery.

•During construction, contractors can pull up mapping systems that accurately display the location and depth of the utilities, so the utilities can be avoided and delays prevented.

•The ability to store data in a single platform can minimize the cost of data collection on future projects as well.

Colorado Department of Transportation

CDOT Utility Permitting

ďƒ˜ CDOT’s Utility Accommodation Code and how it applies to the as-built data collection process

CDOT Utility Permitting 3.3.4.6 Required Documentation As-Constructed Plan. The Department shall require the utility to submit “As-Constructed� plans within forty-five (45) days of completion of the work, shows actual final location, alignment, profile, details and dimensions. Such plans shall be of an electronic format compatible with Department software. The plans shall be in electronic PDF file format, 300 dpi, page aligned, searchable, compressed, and compliant with ISO PDF/A-1b or 1a. Additionally, geodetic datum information of each structure shall be provided and include the depth of underground utilities, as specified in the Special Provisions of each Permit. Exceptions to this electronic submission requirement must be agreed upon by the Department in writing.

CDOT Utility Permitting Examples of permit specific data requested by the Department prior to closing the permit are as follows: •

The electronic data shall be submitted to the Department in shapefile format.

• The standard horizontal datum shall be North American Datum 1983 (NAD 83) and standard projections shall be the Colorado State Plane Coordinate System (NAD '83 (2011)).

• The standard vertical datum shall be the North American Vertical Datum 1988 (NAVD 88).

• The preferred data exchange is CDOT's utility mobile application with direct upload into CDOT's data repository.

• The utility location information shall be tied to Department Survey Control Network, referenced to highway mileposts, and certified by a professional land surveyor, unless the Department provides a waiver to this requirement.

• Metadata, or “attribute data” shall be submitted with each utility’s as built electronic file and shall include: 1. Region Utility Permit Number 2. Name, address and phone number of the person responsible for the survey data 3. Date of completion of survey 4. Equipment used to conduct the survey 5. Utility Owner, type, and size....etc.

6. Elevation shall be provided every 50 feet, beginning and ending at the intersection point of the CDOT Right of Way line for each utility installation. The elevations shall be collected at the top of the highest utility in each installation.

Permitted Design Typical telecom design level plan sheet.

Permit PDF As-built Telecom as-built plan sheet provides very little information related to size, quantity, and geospatial locations.

Permit GIS Data Utility supplied geospatial as-built location. Final inspection did not support this information. CDOT requested independent survey with locates.

Permit GIS Data Example of Emery Telcom’s as-built survey data summited to CDOT required by the permit.

Blue Line CDOT Survey

Permit GIS Data Example of CDOT’s requirement to submit GIS asbuilt data.

Mobile Application

Example of CDOT’s mobile application, data from desk top also available in the filed.

Mobile Application

Valuable attribute data (Metadata) available in the filed

Mobile Application Meta Data

Valuable attribute data (Meta Data) available in within mobile application.

Mobile Application Collection Record

Valuable attribute data (Meta Data) available in the filed

CDOT Permits Construction Management

CDOT Standard Provision language 3.3.4.6 Required Documentation As-Constructed Plan. The Department shall require the utility to submit “As-Constructed� plans within forty-five (45) days of completion of the work, shows actual final location, alignment, profile, details and dimensions. Such plans shall be of an electronic format compatible with Department software. The plans shall be in electronic PDF file format, 300 dpi, page aligned, searchable, compressed, and compliant with ISO PDF/A-1b or 1a.

Additionally, geodetic datum information of each structure shall be provided and include the depth of underground utilities, as specified in the Special Provisions of each Permit.

Exceptions to this electronic submission requirement must be agreed upon by the Department in writing.

RAILROAD UTILITY PERMIT VS DOT UTILITY PERMIT

AGREEMENTS What is the UPRR doing with utility construction management?

RAILROAD LICENSE SPECIAL PROVISION

AGREEMENTS Article V. Special Provision – Onsite Observation Licensor requires Contractor to provide monitoring of tracks and on-site observation through Licensor approved observer named below during all construction and installation work. The Licensee is to directly coordinate and contract services with the named observer: RailPros Field Services Email: RP.Utility@railpros.com Phone (682) 223-5271

RAILROAD LICENSE SPECIAL PROVISION

AGREEMENTS

RailPros is a third party utility inspection consultant

RAILROAD LICENSE SPECIAL PROVISION REPORTING

AGREEMENTS

CDOT Data Management Requirements

Transparent Earth (GIS)

PointMan

Utility Permitted As-built data Required Permitted data in NAD 83/WGS 84 automatic upload into TE (Lat/Long/Height only)

Data Collection with PointMan GPS (Survey and Sub meter accuracy)

CDOT will require the utility permitee to utilize PointMan mobile application for all installations.

CDOT’s DATA WORKFLOW Transparent Earth (GIS)

Data Collection with PointMan GPS (Survey and Sub meter accuracy)

Trimble Data Collector Trimble Survey Design Data into TBC

Data Collection with Trimble GPS, Total Station, and Robotic

Project design Data including Project Control Calibration (LL/H & N,E,El.)

0-30% Design Stage QL-B - 10% design goal

SHP file output from TE into MS PointMan (Summer 2019) Site Calibration

MicroStation (SUDA)

SHP file output from TE into TBC for Site Calibration

Required Permitted data in NAD 83/WGS 84 automatic upload into TE (Lat/Long/Height only)

SHP File output from TBC into TE

PointMan

SHP File output from TBC into MS With Site Calibrated to Project Control Datum

Trimble Business Center (TBC) Survey Data Interface

CDOT’s DATA WORKFLOW

Mapping shapefiles into MicroStation utilizing ModelBuilder

SHAPEFILE DATA INTEGRATION

DGN FILES TO SHAPEFILE MODEL

DGN FILES TO SHAPEFILE MODEL

QUESTIONS?