Skip to main content

Currently Skimming:


Pages 30-43

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 30...
... 30 C H A P T E R 4 This chapter of the report describes the STA case examples that were based on the initial survey results. The follow-up interviews will help other STAs enhance or improve their current as-built procedures.
From page 31...
... Case Examples 31 According to Arizona DOT, the record-drawing process flowchart is one of the most useful aspects of the web page. It provides a step-by-step procedure on how record drawings should be developed and stored.
From page 32...
... 32 Development and Use of As-Built Plans by State Departments of Transportation Figure 32. Stages I and II of Arizona DOT's redlines/record-drawing plans flowchart.
From page 33...
... Case Examples 33 Arizona DOT is also making progress in the transparency of as-built plans. Arizona DOT encourages the public to get information on transportation infrastructure through ROAD.
From page 34...
... 34 Development and Use of As-Built Plans by State Departments of Transportation As-Built Information Received from Third-Party Agencies Third-party agencies can share record drawings in one of two ways. Record drawings can be e-mailed directly to Arizona DOT as PDFs, or as a link to the record drawings from the company site or file-sharing site.
From page 35...
... Case Examples 35 As-Built Information on Warranties, Agreements, and Deployed Technology Colorado DOT does not perform projects with warranties. Its contracts for projects with agreements or deployed technology are the same as all contracts; therefore, as-built development does not differ for these projects.
From page 36...
... 36 Development and Use of As-Built Plans by State Departments of Transportation as-built plans to the appropriate destination and ensuring they are being completed consistently and uniformly. Varying As-Built Procedures According to Project Delivery Method As-built plans are developed by construction personnel at KYTC.
From page 37...
... Case Examples 37 Major Work Product Work Product Components Individual Work Items Required As-Built Information Collection & Recording Method (Current Recommendation) Future Collection & Recording Methods Structures • Concrete Cylinder Breaks • Test and Record in SiteManager Foundation Piles • Pile Tip Elevation/Lengths • Measured Bearing • Direct Measure and Record on Pile Logs Foundation Layout • Bottom of Footer Elevation • Direct Measure and Record on Plans Substructure Abutment/End Bent • Beam Seat Elevations • Beam Seat Layout • Wing Wall Dimensions • Direct Measure and Record on Plans Piers • Beam Seat Elevations • Beam Seat Layout • Direct Measure and Record on Plans Superstructure Bridge Deck • X-Dimensions • Finished Grade • Surveyed and Record as PDF • Direct Measure and Record on Plans Culvert • Culvert Fill Heights • Wing Wall Dimensions • Direct Measure and Record on Plans Foundation Layout • Bottom of Footer Elevations • Surveyed and Record as PDF Roadway Right of Way Completed Project • Actual Roadway Monuments and Lines • Survey and Record on Plans • Picture & GPS and Record on ArcGIS • Google Earth Subgrade Stabilization Method • Cement/Line/Rock Roadbed • Record Method Used as PDF Asphalt/ Concrete Pavement Base Courses • Actual Courses and Thickness • Direct Measure and Record on Plans Permitted Facilities Entrances • Permitted Facilities • Scaled Drawings • Visual Inspection and Record on Plans • GPS/Geographic Information System (GIS)
From page 38...
... 38 Development and Use of As-Built Plans by State Departments of Transportation Incorporation of As-Built Data into Asset Management Currently, as-built data are not being incorporated into asset management and little discussion on asset management was present in interviews. However, as research on as-built procedures continues at KYTC, this is an area for consideration and enhancement.
From page 39...
... Case Examples 39 Currently, Minnesota DOT is tracking let construction projects and as-built usage, communicating District 2018 projects and the status of the data, conducting monthly statewide as-built working group meetings, and compiling special provisions/website changes. Next steps include a case example on utilizing as-built data, adding asset classes to 2011.601, continuing to build contractors' expertise, and improving the business process.
From page 40...
... 40 Development and Use of As-Built Plans by State Departments of Transportation Incorporation of As-Built Data into Asset Management Minnesota DOT's as-built program is directly linked to its asset management. In addition, a statewide asset-grade LiDAR survey was completed in 2017.
From page 41...
... Case Examples 41 Specification and Pay Item. The LiDAR survey collected location information and some asset attributes.
From page 42...
... 42 Development and Use of As-Built Plans by State Departments of Transportation As-Built Information on Warranties, Agreements, and Deployed Technology Projects with warranties, agreements, or deployed technologies do not require additional or different as-built information than any other projects at Virginia DOT. However, as stated previously, contractors are most likely responsible for ITS project as-builts.
From page 43...
... Case Examples 43 Varying As-Built Procedures According to Project Delivery Method Different projects at Wisconsin DOT may have different approaches to as-built development, such as using 3-D models for the megaproject in Milwaukee. However, Wisconsin DOT is only allowed to perform design–bid–build projects; therefore, there is no variation in project delivery method.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.