New Murabba digital twin construction is a useful case study for planners because it shows how a megaproject can treat data infrastructure as part of delivery rather than as a reporting add-on. New Murabba’s own website says AI and digital twins are intended to reduce waste, accelerate construction and optimize daily operations. That ambition matters for project controls because the value of a digital twin depends on whether schedule, design, progress, cost and asset data are connected to the same controlled decisions.

New Murabba digital twin construction in context

New Murabba is being developed by a Public Investment Fund company in north-west Riyadh. At MIPIM 2026, the developer described a destination covering more than 14 million square metres, with more than 90,000 residential units planned for more than 280,000 residents. The masterplan also highlights 25% dedicated green space, multimodal mobility and a 15-minute downtown concept.

The Mukaab remains the development’s signature landmark. New Murabba describes the structure as approximately 400 metres by 400 metres by 400 metres and positions it as a technology-enabled destination using systems such as AI, robotics and immersive digital experiences. Those figures describe the current official vision; they should not be read as evidence that every component is already operational or complete.

Digital twins are already more than a future concept

One of the strongest signals is not a rendering of the future city, but New Murabba’s own headquarters. In November 2025 the company said its Riyadh headquarters had achieved SmartScore Platinum with a perfect 100/100 score and included what it described as the Kingdom’s first operational digital twin. Developed in-house and powered by Autodesk Tandem, the system is used for real-time monitoring, simulation and optimization of building systems and technology infrastructure.

For project-controls teams, that distinction is important. A digital twin becomes useful when it has live or regularly synchronized data, clear ownership and a purpose. A static 3D model may support coordination, but a true operational twin should connect the asset to changing information so teams can test scenarios, detect anomalies and trace decisions.

From 3D coordination to a controlled delivery model

The project-controls opportunity is to connect digital-twin information to the work breakdown structure. Design packages, construction zones, assets, inspections and commissioning systems should map to schedule activities and milestones. Without that mapping, a model can be visually impressive but difficult to use for delay analysis or management action.

A practical delivery chain could be: design object → package or location code → schedule activity → responsible contractor → progress evidence → inspection status → commissioning record. The objective is traceability. If a planner sees a delayed activity, the team should be able to identify which physical assets or areas are affected. If the twin highlights a stalled system or inaccessible zone, the schedule should show the consequence.

Technology partnerships point toward integrated construction intelligence

New Murabba has continued building its technology ecosystem. In June 2025 it signed a three-year MoU with NAVER Cloud to explore robotics, autonomous vehicles, a smart-city platform and digital solutions for monitoring construction progress. In July 2025 it signed an MoU with Honeywell covering automation, digital transformation and smart infrastructure. These are agreements to explore and enable capabilities, not proof that all systems have already been deployed across the development.

For planning engineers, the lesson is to separate announced capability from implemented control. A technology roadmap should therefore have measurable delivery gates: requirements agreed, platform architecture approved, data interfaces tested, pilot completed, production use accepted and benefits verified.

Phase 1 infrastructure needs the same digital discipline

New Murabba announced in January 2026 that Parsons had been appointed Infrastructure Lead Design Consultant for Phase 1. The scope covers design and integration of core utilities, mobility systems and transportation networks, translating concept designs into detailed constructible solutions. Infrastructure is exactly where digital coordination can prevent late interface failures because utilities, roads, structures and future development plots all compete for physical space and sequence.

A digital-twin strategy can support constructability reviews, but the planning baseline still has to contain the interface milestones. Utility diversions, enabling works, design freezes, procurement lead times and access handovers must appear in the schedule with accountable owners. A model cannot compensate for missing logic.

Four project-controls uses that matter

1. Progress validation by location

Location-based progress is often more actionable than one overall percentage. If model objects or zones can be associated with verified installation and inspection states, planners can compare the physical picture with the reported activity status. Differences become exception lists rather than arguments at the end of the month.

2. Interface and access management

Large mixed-use developments have many contractors sharing constrained work fronts. A digital environment can visualize upcoming conflicts, but the control process must still record who owns the clearance, when it is required and what successor activity depends on it.

3. Change impact analysis

When a design object changes, the team should be able to identify affected quantities, procurement packages, installed work and schedule activities. That traceability strengthens change control because the impact can be assessed using the same coding structure rather than reconstructed manually weeks later.

4. Handover readiness

At handover, the most valuable twin is not the most photorealistic. It is the one connected to approved asset information, testing records, warranties, O&M documentation and accepted as-built status. The transition from construction twin to operational twin should therefore be planned as a deliverable, not left to the final months.

What planners should not automate blindly

AI can help classify risks, detect anomalies and prioritize reviews, but project teams should be cautious about treating algorithmic output as a contractual conclusion. A predicted delay is a risk signal, not automatically an entitlement. Critical path, contemporaneous records, causation and contract provisions still determine how delay is assessed.

The same caution applies to progress. Computer vision, sensors or object status can support evidence, but the approved measurement methodology remains the basis of reporting. If a contract defines progress through inspected quantities or accepted deliverables, a model should feed that system rather than replace it.

An illustrative digital-twin control workflow

Illustrative — not official New Murabba project data: imagine a utility corridor scheduled for completion by a month-end data date. The schedule reports 80% complete, while model-linked inspection records show only 65% of installed assets accepted. The planner should not simply overwrite the schedule with 65%. Instead, the team reconciles quantities, inspection status, rejected work, measurement rules and late updates. The result may reveal a reporting cut-off issue, a quality hold point or genuine overstatement.

That reconciliation is where digital twins create value: they provide another controlled evidence layer and make inconsistencies visible earlier.

New Murabba digital twin construction lessons for project controls

The most important lesson is that digital transformation should be designed around decisions. New Murabba’s public strategy combines smart-city infrastructure, AI, digital twins, robotics and integrated mobility, while its headquarters already demonstrates an operational digital-twin use case. For planners, the opportunity is to connect these capabilities to the fundamentals: WBS, schedule logic, data dates, responsibilities, progress evidence and change control.

A megaproject becomes digitally mature when technology reduces the time between a physical event and a management decision without weakening traceability. If an access constraint appears, the schedule consequence should be visible. If an asset changes, the affected package should be identifiable. If progress is disputed, evidence should be retrievable. If handover is approaching, readiness should be measurable.

Digital twins can make that control environment faster and more transparent, but they work best when the underlying project-controls system is disciplined first.

Verified references

Current project facts in this article were checked against New Murabba’s official website and press releases covering its MIPIM 2026 presentation, operational headquarters digital twin, NAVER Cloud technology MoU, Honeywell collaboration and Parsons Phase 1 infrastructure appointment. Updated 31 August 2026.

Construction S-curve reporting is one of the clearest ways to show whether a project is progressing broadly in line with its approved plan. The familiar cumulative curve can make a complex programme understandable in seconds, but that simplicity can also be dangerous. A polished chart is not evidence of a healthy project unless its schedule logic, progress measurement, weighting and data date are credible.

What a construction S-curve actually measures

An S-curve plots a cumulative quantity against time. In project controls, the vertical axis may represent weighted progress, labour hours, quantities, cost or earned value. The horizontal axis represents time. Many projects develop an S-like profile because progress starts slowly during mobilization and engineering, accelerates during peak construction, and flattens as testing, snagging and handover reduce the remaining volume of work.

For earned value management, the Project Management Institute describes Planned Value (PV) as the time-phased budget baseline and notes that a graph of cumulative PV is commonly referred to as an S-curve. Earned Value (EV) represents the budgeted value of work actually accomplished, while Actual Cost (AC) records what was spent to accomplish that work. These measures allow the chart to become more than a visual progress line.

Build the curve from a defensible baseline

The planned curve should come from an approved, time-phased baseline rather than percentages typed manually into a reporting sheet. Activities need sensible durations, calendars, relationships, constraints and resource or cost assignments. The WBS should also correspond to how the project will actually be measured.

A baseline with excessive constraints, open ends, unrealistic productivity or poorly distributed weights can generate a smooth curve while hiding weak planning assumptions. Before management relies on the graph, the planning team should be able to trace a point on the curve back to the underlying activities and explain why that amount of progress was planned by the reporting date.

Choose a progress basis and keep it consistent

Different packages may require different measurement rules. Engineering can be weighted by deliverables and approval stages. Procurement may use milestones such as purchase order, manufacturing, inspection, shipment and delivery. Construction is often better measured through installed quantities or weighted physical steps. Testing and commissioning may use system-based milestones.

The important control is consistency. Mixing cost expenditure, physical quantity and subjective percent complete without a controlled weighting structure can distort the overall result. A project can appear advanced simply because a heavily weighted activity has been credited too early.

Planned versus actual is not enough

A common progress report shows only planned percent and actual percent. That comparison is useful, but it does not automatically distinguish work accomplished from money spent. Earned value adds a stronger performance framework by comparing PV, EV and AC on a common basis.

PMI defines Schedule Variance as EV minus PV and the Schedule Performance Index as EV divided by PV. An SPI of 1.00 means the value of completed work equals the value planned by that date; below 1.00 indicates less work has been earned than planned. Cost Performance Index is EV divided by AC. These indices are valuable signals, but they should not be treated as substitutes for schedule analysis.

In particular, an S-curve cannot tell management which delayed activity is driving the completion date. A project may be behind its cumulative plan because of non-critical work while its contractual milestone remains protected, or it may look close to plan while a small but critical sequence has slipped. The curve therefore belongs beside critical-path, float, milestone and look-ahead analysis.

Use the data date as the control line

Every monthly S-curve should have a clear status or data date. Actual and earned progress should stop at that date. Future values belong to the forecast. This sounds basic, yet reporting errors often arise when progress from different cut-off dates is combined, late information is backfilled inconsistently, or the schedule and cost systems close on different dates.

A disciplined reporting cycle freezes the cut-off, validates site quantities, updates schedule status, checks cost information, reconciles exceptions and only then publishes the cumulative curves. If late data is accepted after the cut-off, the report should state the rule clearly.

Read the shape, not just the variance

The gap between planned and earned curves matters, but so does the trend. A widening gap suggests that the project is losing ground. A stable gap may indicate that production has recovered to the planned rate but has not recovered the earlier delay. A narrowing gap suggests catch-up, although planners should confirm that the improvement comes from genuine production rather than changed weights or retrospective progress.

The monthly incremental values behind the cumulative chart are often even more revealing. Because cumulative curves naturally smooth volatility, a separate monthly histogram can expose declining production, a delayed ramp-up or an unrealistic future peak. Management should ask whether the remaining monthly output is physically achievable with the available work fronts, crews, materials and logistics.

Forecasting and recovery plans

When actual progress falls behind, simply drawing a steeper future line is not a recovery plan. The forecast should be rebuilt from remaining scope, realistic productivity, access dates, procurement constraints and current logic. If acceleration is proposed, the schedule should show where additional crews, shifts, work fronts or resequencing create the required gain.

For a credible recovery S-curve, the revised monthly production profile must reconcile with the updated programme. If the curve requires twice the historical installation rate, the team should identify the resources and work fronts that make that increase possible. Otherwise the recovery curve is only a target.

Five controls that make S-curves reliable

First, control the baseline. Changes to the planned curve should follow the project’s approved change-control process. Do not quietly rewrite history to make current performance look better.

Second, control weighting. The total weight should reconcile to 100 percent or to the approved budget basis, and package-level weights should reflect the agreed measurement method.

Third, validate physical progress. Progress should be supported by quantities, inspections, deliverables or other objective evidence appropriate to the scope.

Fourth, reconcile schedule and reporting systems. WBS codes, activity identifiers, cost codes and reporting periods should align sufficiently to explain variances without manual guesswork.

Fifth, preserve an audit trail. Retain prior-period values, approved baseline versions and explanations for corrections. A good report should allow another planner to reproduce the curve.

Illustrative example: interpreting a monthly variance

Assume an illustrative project planned to reach 60% weighted progress by the August data date but had earned 54%. The simple progress variance is -6 percentage points and the corresponding SPI is 54/60 = 0.90. This example is illustrative and is not official data from any project.

The number alone does not establish a six-point delay to completion. The planner should identify which WBS elements caused the gap, whether they are critical, how much float remains, whether successor work can proceed, and what production is required over the remaining periods. If most of the shortfall is on a critical façade sequence, the completion risk may be substantial. If it is on non-critical landscaping with available float, the milestone effect may be different.

What management should see each month

A strong dashboard normally combines the cumulative S-curve with current planned and earned percentages, monthly incremental progress, SPI where the EVM basis is valid, milestone variance, critical-path narrative, major constraints and a short forecast. The chart should answer three questions: Where should we be? Where are we now? What has to happen next?

The most useful commentary is specific. Instead of saying “progress is delayed,” identify the responsible work package, the cause, the effect on the near-term sequence, the mitigation action and the decision needed from management. That turns the S-curve from a presentation graphic into a control instrument.

Construction S-curve lessons for planning engineers

A construction S-curve is powerful because it compresses a large schedule into a recognizable trend. It is weak when used in isolation. Reliable reporting requires a controlled baseline, objective progress measurement, consistent weighting, a fixed data date and direct reconciliation with the schedule.

The best planning engineers use the curve as an entry point for investigation. When the line moves, they ask what changed in the underlying WBS. When it does not move as expected, they investigate access, resources, procurement, productivity and logic. And when a recovery curve is proposed, they test whether the programme can actually deliver it.

That discipline is what makes an S-curve useful for decisions rather than decoration.

Verified references

Project-controls definitions and formulas in this article were checked against the Project Management Institute’s earned-value guidance and PMI material on monitoring performance against the baseline. Updated 30 August 2026.