What If a Construction Project Had an Operating System?

Computers have operating systems.

Factories have operating systems, whether formally described that way or not.

Airlines, hospitals and high-performing logistics networks have deeply designed operating models that define how decisions, information, resources and work move through the system.

What is the equivalent on a construction project?

We have project-management systems. We have contracts. We have schedules. We have Lean methods. We have BIM. We have procurement procedures. We have safety systems. We have cost controls.

But these are often separate layers.

Imagine instead that a project began by deliberately designing its operating system.

The project would define the value it was trying to create. Its commercial model would reinforce the behaviours required to create that value. Governance would establish clear decision rights. Design would be treated as a production flow. Procurement and logistics would be configured around production demand. Work would be structured to create flow. Constraints would be removed before commitments were made. Reliability would be measured as a leading indicator. Learning would occur continuously.

Technology would then support that system rather than dictate it.

We have been calling this emerging idea PPOS: the Project Production Operating System.

It is not intended to replace project management, Lean Construction, Last Planner, Takt, BIM/VDC, Project Production Management or collaborative contracting.

Those disciplines contain enormous value.

The question is whether we can create an architecture that allows them to operate together.

An operating system should answer three questions.

First: what must be true for this project to operate reliably?

Second: how do the different project systems interact?

Third: how do we know early enough when the operating system is beginning to fail?

We are deliberately not pretending those questions have simple answers.

Different projects have different products, supply chains, risk profiles, delivery models and production characteristics.

The goal therefore should not be a rigid manual.

It should be a configurable operating architecture built on sound principles.

That is the idea we are exploring.

Not another tool for the project.

A way of making the project itself operate as a system.

We are inviting a small number of organisations into a confidential PPOS founding-project discussion—get in touch if you’d like to help shape it early.