Maintaining as-built information is critical throughout the lifecycle of a facility project. As-built information contains pertinent data to support maintaining operations and project decision–making. Since it provides a method of comparing the intended and actual, project stakeholders can see how their decisions were integral to the final product. Therefore, it is essential that accurate as-built data must be maintained to document changes that occur throughout a facility project.
What is an As-Built Drawing?
An as-built drawing, or “record drawing,” is a type of technical drawing representing a facility’s final and actual physical configuration or component within the facility post–construction or installation. The main elements included in as-built drawings are:
- Shop drawing changes
- Added scope
- Field changes
- Design changes
- Modifications
- Labels and dates
- Locations and dimensions
Architects and engineers of record are often contractually required to provide a final “as-built” set of records that incorporate all permitted design modifications incurred during the project’s construction phase (e.g., incorporating all scope of work redlines completed in the construction phase).
What is the purpose of Redlines?
Whether projects are large or small, changes to engineering and architectural drawings are inevitable. During an on-site survey or simply when proofing a drawing, the architect, engineer, or builder notices an error with the current version of the drawing. The observer typically annotates the paper drawing using a red pen (e.g., mark up shop or design drawings to display field changes). Drawings that show these changes are often called “redline drawings” or “redline markups.” Redline drawings help to illustrate deviations from the original design.
Strategies on How to Track Redline Changes
Throughout a project, these design drawings may be utilized by different trades whose scope depends on one another. Typically, either the General Contractor and/or Project Manager keeps and maintains a compiled set of redline drawings throughout a project.
Engineering and design drawing verifications are dependent on the project phase. Different strategies can be utilized to help manage, and are listed below:
- Defining and documenting the “System Boundaries” by marking on design drawings can help distinguish systems from one another; this should include all components and piping to logically define what is and what is not included within the system.
- Develop “System Risk Assessments” for any direct impact system to identify critical and procedural design controls.
Implementing “Design Reviews” to evaluate deliverables against standards and requirements, identify problems, and propose required corrective actions throughout the project lifecycle. - Schedule “System Walkdowns” and record current system status results before completing any critical scope of work (i.e., ceiling closures, Air Balancing, etc.). The Factory Acceptance Test (FAT) or construction walkdown is likely the first opportunity to perform these verifications, and resources should be spent to ensure drawings are as accurate as possible at this early stage.
- Maintain a “Discrepancy Log” of any issues with the architect, engineer, or builder. Discovered. These discrepancies should be evaluated, and corrective actions should be taken.
- Perform and document a “Pre-Functional Testing Checklist” to ensure that items critical to design are completed before any System Start-Up.
Benefits of Proper Resource Allocation for Maintaining As-Built Data
Facility managers, owners, surveyors, and contractors may reference these drawing sets at various project phases. Ensuring that proper resources are allocated to the maintenance of these records, it can help ease the transition from design to construction, construction to validation, and validation to system acceptance. Tracking redline drawings throughout a project can reduce errors, increase efficiency, and improve quality control (QC). Utilizing redline drawings as a real-time project record decreases the probability of error and improves project efficiency.
