Smart Hands & iMACD

Introduction to As-built documentation,

The final stages of an Install, Move, Add, Change, or Deletion (IMACD) project in a data centre are heavily dependent on the quality of the documentation handed over to the client.

As-built records, redline drawings, and adherence to drawing standards provide the client with a transparent record of what has been delivered, where it has been installed, and how the infrastructure aligns with both the original design and any field changes. Without these deliverables, operational teams are left without reliable reference points, introducing risks to ongoing maintenance, capacity planning, and future change requests.

This section explores the discipline of managing as-built documentation, applying redlines consistently, and maintaining drawing standards. T

hese processes are not optional; they form part of contractual obligations, compliance requirements, and quality assurance frameworks such as ISO 9001 (quality management) and ISO/IEC 27001 (information security).

For SmartHands engineers, producing accurate records is not just about closing out a project. It is about protecting the operational integrity of the client’s environment, enabling seamless handovers, and ensuring that the work completed becomes part of a living system of record.

In the previous section we examined the broader scope of handover preparation.

This section now focuses specifically on the foundational documentation elements. The aim is to equip SmartHands engineers with a detailed understanding of what must be recorded, how it should be formatted, and why accuracy is critical.

This lays the groundwork for the next topic, asset registers and serial capture, where the same discipline of precision and control will be applied to inventory management.

‍

9.1.1 Defining As-built Documentation

As-built documentation refers to the final set of drawings and records that reflect the installation exactly as delivered on site, including any changes made during execution. These records are more than simple drawings; they are the official point of reference for all future work in that environment.

Key elements include:

• Floor plans and rack layouts that reflect the actual installation, not just the design intent.
  
• Cable schedules that show final routes, labelling, and terminations.
  
• Power distribution records with breaker assignments, load values, and final cable routing.
  
• Network topologies adjusted to capture installed ports, patching layouts, and fibre distribution.
  

The purpose of as-built records is threefold. First, they act as a compliance and legal deliverable, ensuring the contractor has fulfilled the specification. Second, they provide operational clarity for the client’s facilities and IT teams, reducing risks during live changes. Third, they allow benchmarking against design intent, enabling post-project reviews and lessons learned exercises.

To achieve accuracy, SmartHands engineers must validate installations against the drawings during walkdowns, record every deviation, and work with design teams to issue updated drawings. The process is iterative, requiring coordination between field teams, drafters, and quality control. Poorly prepared as-builts can lead to significant risks, including incorrect patching during outages, unbalanced loads on power systems, or lost traceability of circuits.

‍

9.1.2 Redline Processes and Change Control

Redlines are the annotated changes made to drawings or design documents during installation to record deviations from the approved design. They capture the reality of what was delivered in the field and provide the raw data for updated as-built drawings.

Effective redlining requires discipline and a standardised approach. SmartHands engineers must:

• Use client-approved templates or drawing sets.
  
• Annotate changes with clear, legible handwriting or digital mark-up tools.
  
• Record the reason for each deviation (e.g., obstruction, client-requested change, unavailable pathway).
  
• Date and initial each change for accountability.
  

In practice, redlines are often captured on-site using printed drawings or tablets with mark-up software. These updates must be logged in daily site records and reviewed by project managers to ensure they are transferred into the official as-built documentation.

Without structured redline processes, critical deviations may be lost. For example, a fibre cable re-routed around an obstruction may never be captured, leaving future engineers to rely on outdated designs. This not only creates inefficiency but could also result in downtime if engineers attempt to follow a non-existent route.

It is important to link redline processes to formal change control procedures. Any change should be reviewed and approved by the appropriate authority, logged in the Change Management Database (CMDB), and referenced in the project’s issue log. This ensures that the as-built documentation remains authoritative and contractually valid.

‍

9.1.3 Drawing Standards and Compliance Requirements

Maintaining drawing standards is essential to ensuring consistency across multiple projects, contractors, and sites. Standards such as ISO 128 (technical product documentation) and BS 1192 (collaborative production of architectural and engineering information) provide frameworks for how drawings should be structured, annotated, and formatted.

In a data centre IMACD context, standards must cover:

• Title blocks that include project identifiers, revision history, and approver details.
  
• Layering conventions within Computer-Aided Design (CAD) software to separate mechanical, electrical, and cabling elements.
  
• Line styles, symbols, and colour codes for power circuits, fibre routes, copper cabling, and containment.
  
• Version control protocols, ensuring only the latest approved drawing is in circulation.
  

SmartHands engineers are not typically responsible for producing full CAD deliverables, but they must understand and comply with these standards when marking redlines or submitting field updates. For example, using the wrong symbol for a fibre splice enclosure may seem trivial, but it creates confusion for drafters and can delay the production of as-builts.

Compliance is also contractual. Many clients will specify in the tender documents that as-built deliverables must adhere to their corporate CAD standards or naming conventions. Failure to meet these requirements may result in rejection of deliverables, delayed payments, or contractual disputes.

Note: All photographs taken within a data centre must be pre-approved by the client due to security restrictions.

‍

9.1.4 Integration with Digital Platforms and Future Use

Modern data centres increasingly demand digital deliverables that can integrate into Building Information Modelling (BIM) platforms, asset management systems, and digital twins. As-built documentation is therefore not static; it becomes a living dataset used to manage the lifecycle of the facility.

SmartHands engineers must ensure that records:

• Are delivered in formats compatible with the client’s systems, such as DWG (AutoCAD), PDF, or IFC (Industry Foundation Classes for BIM).
  
• Include metadata such as cable IDs, port labels, and rack positions that can be uploaded into asset registers.
  
• Follow structured file naming conventions for easy retrieval.
  

This forward-looking integration reduces duplication, ensures consistency across projects, and supports predictive maintenance by linking physical records to digital monitoring systems. It also future-proofs the facility, allowing owners to scale and modify infrastructure with confidence.

‍

As-built documentation, redlines, and drawing standards are the foundation upon which all other handover deliverables are built.

Without accurate drawings and compliant records, asset registers and configuration data lose context, making it impossible to manage a facility with confidence. 

In the next lesson, we move from the graphical and record-keeping discipline of as-builts into the structured world of asset registers, serial capture, and Configuration Management Database (CMDB) reconciliation.