Saudi Arabia Construction ERP: 7 Real-Time Controls for Giga-Project Contractors

Saudi Arabia’s giga-project environment raises the standard for project control.

 

For large contractors, having an accounting ERP, Oracle Primavera P6, spreadsheets and individual construction applications does not automatically create real-time control. Enterprise contractors need a project operating model that connects scope, schedule, cost, procurement, subcontractors, resources, change and actual site execution.

 

The objective is not simply to record what happened.

 

It is to identify deviations early enough to act on them.

 

For DANAOS Projects, this starts by connecting the project’s principal control dimensions:

 

 

and continuously comparing the project baseline against operational reality.

 

Why Is Real-Time Project Control Particularly Important in Saudi Arabia?

 

Saudi Arabia is moving into a different phase of its economic transformation.

 

The Public Investment Fund’s 2026–2030 strategy describes a shift from rapid growth toward sustained value creation. Among its strategic objectives, PIF specifically identifies cost-efficient operations, effective controls, agile execution and advanced AI supported by strong data foundations.

 

That matters to contractors.

 

Saudi Arabia’s project environment includes highly complex developments, infrastructure, industrial projects and major PIF-backed programs involving large contractor, subcontractor and supplier ecosystems.

 

The management question is therefore increasingly not:

 

“Do we have the necessary software?”

 

It is:

 

“Can our systems tell us where the project is deviating while there is still time to respond?”

 

That requires much more than month-end financial reporting.

 

It requires operational project control.

 

1. Cost Control Must Start with the Project Baseline

 

The first requirement for real-time control is not a dashboard.

 

It is a reliable baseline.

 

For a contractor, the project baseline should establish:

 

• what is being delivered;
• in what quantities;
• when the work should be executed;
• which resources should be consumed;
• how those resources are costed;
• what revenue or commercial value is associated with the work.

 

DANAOS Projects has examined this in its article on integrated project performance baselines where cost and schedule must remain connected rather than operating as isolated control structures.

 

For ProjectVIEW ERP, the core relationship is:

 

• BoQ = scope, quantity and commercial dimension
• WBS = execution and time dimension
• Cost Codes = internal cost-control dimension

 

The ProjectVIEW ERP Cost Control Module is designed around the association:

 

BoQ ↔ WBS ↔ Cost Codes

 

The point is not that every organization must use identical terminology.

 

The point is that scope, execution and cost must refer to the same project reality.

 

2. Procurement Must Respond to the Project Schedule

 

Procurement on a giga-project should not operate as an independent purchasing department responding to isolated requisitions.

 

The project should drive procurement.

 

That means answering questions such as:

 

• Which work package requires the material or service?
• What quantity was budgeted?
• When is it needed according to the schedule?
• Has the requisition been approved?
• Has an RFQ been issued?
• Has a supplier been selected?
• What amount has already been committed?
• When is delivery expected?
• Will the material arrive before the corresponding activity starts?

 

DANAOS Projects’ BoQ-centric estimating approach is important here because procurement demand should ultimately originate from what the project was estimated and budgeted to consume.

 

Saudi Arabia adds another dimension.

 

Government procurement policy places significant emphasis on local content and local industry, while the new Government Tenders and Procurement Law approved in August 2026 was presented by the Ministry of Finance as strengthening governance, transparency, planning and implementation efficiency.

 

For contractors operating on large Saudi programs, procurement therefore needs to be both project-driven and auditable.

 

3. Contractors Need to See Committed Cost Before the Invoice Arrives

 

Accounting is indispensable.

 

But an invoice is often a late signal from an operational project-control perspective.

 

Consider what happens before the invoice:

 

A material requisition is approved.

 

An RFQ is issued.

 

A supplier is selected.

 

A purchase order is created.

 

A subcontract is awarded.

 

At that point, the contractor may already be economically committed even though no supplier invoice has yet reached accounting.

 

Real-time cost control should therefore distinguish between:

 

• Budgeted Cost
• Committed Cost
• Actual Cost
• Accrued Cost
• Forecast Cost-to-Complete
• Estimate at Completion

 

 

The better project-control question is not:

 

“How much have we spent?”

 

It is:

 

“Based on what we have completed, already committed and still need to execute, where is the final project cost heading?”

 

4. Subcontractor Progress Must Reconcile Physical and Commercial Reality

 

Saudi giga-projects can involve large subcontractor ecosystems.

 

That creates a difficult control problem.

 

A subcontractor may report a percentage of completion.

 

The planning team may calculate progress against WBS activities.

 

The site team may measure different physical quantities.

 

The commercial department may certify a different amount.

 

Accounting may only see the transaction once the certificate becomes payable.

 

These different views must eventually reconcile.

 

For each subcontract package, enterprise project control should relate:

 

Subcontract scope

 

→ WBS / Work Package

 

→ Physical Progress

 

→ Certified Quantity

 

→ Commercial Value

 

→ Retention / Deduction

 

→ Cost

 

→ Payment

 

ProjectVIEW ERP’s current SaaS framework includes subcontract lifecycle management, progress measurement and certification, variations, claims and retention tracking.

 

For contractors operating across multiple giga-project packages, that traceability is not simply an administrative convenience.

 

It is a cost-control requirement.

 

5. Productivity Must Connect Physical Output, Resources, Time and Cost

 

A project can appear to be progressing while margin is quietly deteriorating.

 

Consider a construction activity where the estimate assumes that one measurable unit requires:

 

• X labour hours
• Y material quantity
• Z machinery hours

 

If the project starts consuming more labour or machinery to produce the same quantity, productivity is declining.

 

That can become visible operationally long before accounting reveals the financial consequence.

 

This is why productivity should not be measured only as:

 

hours worked

 

or only as:

 

percentage complete

 

It should connect:

 

Physical Output ↔ Effort ↔ Resources ↔ Time ↔ Cost

 

The same logic applies to heavy equipment.

 

A contractor does not only need to know that an excavator, crane or concrete pump operated for eight hours.

 

Management needs to know:

 

• Where was it allocated?
• Which activity did it support?
• What quantity was produced?
• What was budgeted?
• Was the machine productive or idle?

 

This turns resource management into project performance management.

 

6. Change Must Update Scope, Schedule, Cost and Revenue Together

 

Change is unavoidable on major projects.

 

The control problem is not that variations occur.

 

The control problem appears when the same variation creates multiple disconnected versions of reality.

 

Engineering may revise the scope.

 

Planning may update the schedule.

 

Procurement may order additional material.

 

Commercial teams may prepare a claim.

 

Cost Control may revise the forecast.

 

Finance may wait for approved contractual recognition.

 

All of these events relate to the same change.

 

A controlled variation should therefore preserve the relationship between:

 

Original Scope

 

→ Changed Scope

 

→ BoQ / Quantity Impact

 

→ WBS / Schedule Impact

 

→ Resource Requirement

 

→ Cost Impact

 

→ Revenue / Claim

 

→ Forecast

 

ProjectVIEW’s architecture supports multiple BoQ and WBS versions, claims and variations within project cost control.

 

The management objective should be:

 

Baseline → Change → Approval → Revised Forecast → Commercial Recovery

 

—not five disconnected spreadsheets describing the same event.

 

7. Site Reality Must Connect with Corporate Finance

 

Many enterprise Saudi contractors already operate Oracle, SAP or another corporate financial ERP.

 

That does not necessarily mean the corporate ERP should be replaced.

 

The more important question is architectural:

 

How does granular operational project reality reach corporate finance without losing its project context?

 

ProjectVIEW ERP is designed to operate as the project-centric layer, while integrating with systems used elsewhere in the enterprise.

 

 

A practical enterprise architecture may therefore include:

 

ProjectVIEW ERP — granular project execution and cost-control processes

 

Oracle Primavera P6 / Microsoft Project — detailed planning and scheduling

 

BIM / IFC environment — digital representation of the physical asset

 

Oracle / SAP / Corporate ERP — consolidated financial and corporate processes

 

The objective is not to introduce another software silo.

 

It is to preserve project context as information flows between systems.

 

Why Does AI Make Structured Project Data Even More Important?

 

Saudi Arabia’s PIF strategy explicitly associates advanced AI with strong data foundations.

 

That is important for construction digitalization.

 

AI can identify patterns, summarize information, predict possible outcomes and automate selected processes.

 

But the reliability of those outputs depends heavily on the quality and structure of the underlying data.

 

DANAOS Projects has discussed this in Walk Before You Run: Why ERP Comes Before AI

 

The principle is simple:

 

If procurement, cost, schedule, progress and resource data use inconsistent structures across projects, adding AI does not automatically solve the underlying control problem.

 

First structure the processes.

 

Then connect the project dimensions.

 

Then use AI to extract intelligence from them.

 

What Should Saudi Giga-Project Contractors Ask Their ERP Vendors?

 

For an enterprise contractor, the procurement process for ERP should go beyond feature checklists.

 

Ask whether the architecture can answer these questions:

 

1. Can BoQ, WBS and Cost Codes remain associated throughout the project lifecycle?
2. Can actual quantities be compared against budgeted quantities?
3. Can labour and machinery productivity be measured against physical output?
4. Can committed cost be identified before supplier invoices arrive?
5. Can procurement requirements be driven by project schedule need dates?
6. Can subcontractor progress be reconciled with physical progress and certification?
7. Can variations update scope, schedule, resources, cost and revenue consistently?
8. Can management forecast cost-to-complete and Estimate at Completion?
9. Can executives drill from a portfolio-level KPI into the underlying project transaction?
10. Can the project platform integrate with Primavera P6, BIM and the corporate ERP?
11. Is the operational data sufficiently structured to support reliable analytics and AI?

 

If several answers are no, the problem may not be a missing dashboard.

 

The problem may be the underlying project-control architecture.

 

Conclusion: Real-Time Control Is About Connecting Project Reality

 

Saudi Arabia’s construction opportunity is enormous.

 

But scale also magnifies the cost of fragmented information.

 

DANAOS Projects’ view is that real-time project control does not come from producing more reports.

 

It comes from maintaining the relationships between:

 

• Scope
• Quantity
• WBS
• Schedule
• Cost Codes
• Resources
• Procurement
• Subcontractors
• Change
• Actual Execution
• Financials

 

—and continuously comparing that reality against the project baseline.

 

For Saudi giga-project contractors, that is a more useful definition of construction ERP:

 

not simply software that records what happened, but a project operating environment that helps management understand what is happening now, why it is happening and what it means for the final project outcome.

 

---

 

Written by Christos Emmanouilidis, Civil Engineer and Chief Customer and Commercial Officer, DANAOS Projects Software Solutions LLC.