Building Information Modeling, and the federated model
A building model in which every element carries data, not just shape: a wall knows what it is made of, what it costs, and what it touches. Discipline models (architecture, structure, mechanical, electrical) are combined into a federated model, where clash detection finds the conflicts digitally, while they still cost hours instead of weeks. BIM changes who can see a problem and when. What it asks of a contract: who authors each model, who coordinates them, what level of development each element must reach, and who is answerable for what the model shows. Treated in depth in its own chapter, Building Information Modeling, with the contract side in Risk Allocation.
Reality capture: laser scanning, photogrammetry, point clouds
Laser scanners (LiDAR) and drone photogrammetry measure the built world as point clouds: millions of verifiable coordinates. Scan-to-BIM turns that record into models; repeated capture turns progress into data. Reality capture replaces “as far as we know” with “as measured.” What it asks of a contract: who owns the captured data, what accuracy it is held to, and whether the measured record or the drawing governs when they disagree. Treated in Information Governance.
Digital twins
A living digital copy of a completed building, fed by its sensors and records, built to answer an operator’s questions: where the energy goes, which spaces are used, what needs maintenance before it fails. The twin is only as good as the information discipline that feeds it. What it asks of a contract: which data must survive handover, in what structure, verified by whom. Treated in Digital Twins, with an applied case at a major airport.
4D and 5D: time and cost in the model
Linking the model to the schedule (4D) lets a team rehearse the build before doing it; linking it to cost (5D) prices design options while they are still options. Both move decisions into the window where changing them is cheap. What it asks of a contract: whether the priced model or the estimate governs, and when the price commitment hardens. Treated in Value Management and Risk Allocation.
Sensors, IoT and wearables
Networked sensors report occupancy, energy, condition and environment from the building; wearables (EMG for muscle load, IMU for motion) read physical strain on the people building it. Together they make performance and safety measurable in real time. What it asks of a contract: who owns telemetry, what may be done with data about workers, and who acts when a reading crosses a threshold. Treated in Digital Twins and AI & Construction 4.0.
Machine learning and natural language processing
Models that learn from site imagery, telemetry and documents: flagging safety risk, predicting equipment failure, classifying defects, reading thousands of pages of specifications and RFIs. They are advisory until someone acts on them, and then they are consequential. What it asks of a contract: whether the algorithm’s output is advisory or determinative, what accuracy standard it is held to, and who carries the loss when it is wrong. Treated in AI & Construction 4.0.
Robotics, drones and autonomous platforms
Machines that patrol, capture, lay out, and increasingly install: drones for progress and volumetrics, ground platforms for scanning and condition assessment, robotic layout and printing on the slab. They produce the data the models above consume. What it asks of a contract: site access and liability for autonomous operation, and ownership of everything the machine records. Treated in AI & Construction 4.0.
Extended reality
Virtual, augmented and mixed reality put a person inside the model: walking a design before it exists, overlaying the plan on the slab, inspecting remotely. Coordination stops being an abstraction. What it asks of a contract: which model state the immersive view certifies, and whether a remote inspection counts as one. Treated in AI & Construction 4.0.
3D printing and industrialized construction
Additive construction prints components and walls directly from the model; prefabrication and design-for-manufacture move work into factories, where quality and sequence are controllable. Both collapse the distance between the digital design and the physical result. What it asks of a contract: who approves the print file or the fabrication model as a construction document, and where design liability sits when the model is the drawing. Treated in Risk Allocation.
Common data environments and open formats
The common data environment is the single controlled place where project information lives, with states and permissions; open formats (IFC for models, COBie for handover data) keep the information usable regardless of vendor. Unglamorous, and decisive: this is the layer where every other technology’s output either survives or dies. What it asks of a contract: everything Chapter 04 exists to answer. Treated in Information Governance.
Every technology on this page produces information faster than traditional project governance can absorb it. That gap, not any single tool, is the subject of this practice: the six chapters take the same questions in order, from what the money must buy to the rules for what is arriving. Start at the beginning.