Skip to content
Our workPlatformsApplication briefing

Construction Operating Platform

From fragmented project systems to one shared project context.

Workflow illustration

Workflow illustration of a designed platform, not real projects or documents. Project and client master data, the existing BMS and document structures, operational, commercial and finance workflows and roles and permissions come into one shared context. The context switches from the business to a selected project, which has one project record and one document record. Six modules, drawings, RAMS, programme, tenders, commercial and finance, each connect to that same context rather than keeping their own copy. When a document moves from revision A to revision B, the drawings, RAMS and tender records that use it stay linked to the new revision. In a site team view, permissions hide the commercial and finance modules. Global and project dashboards surface approvals, exceptions and priorities; accountable people make the commercial, safety and finance decisions, which stay visible and attributable, and management sees priorities across projects.

People stay in control

Project context and permissions act as hard data boundaries. Commercial, safety and finance decisions stay visible, attributable and auditable, and accountable people keep approval authority.

The challenge

Contractors often run projects through an established BMS alongside folders, spreadsheets and specialist tools. The same project information is entered again and again, related evidence becomes fragmented and different teams can end up working from different versions of the truth.

What we designed

A platform in PRISM organised around two contexts: the business and the selected project. Global and project dashboards, documents, drawings, RAMS, programmes, site diaries, tenders, procurement, commercial workflows, finance and management information all use the same project context, document model and permissions.

A designed operating platform, organised around one authoritative project record and one authoritative document record.

What it connects

  • Project and client master data
  • Existing BMS and document structures
  • Commercial, finance and operational workflows
  • Roles, permissions and system integrations

The difference it makes

  • Documents, workflows and applications work from the same project record rather than rebuilding context in separate systems.
  • Evidence captured once can support operational, commercial, compliance and finance work without another isolated tool.
  • Project and functional boundaries control what each person can see, while authorised work shares the right context.
  • New applications and modules use the same project and document model instead of becoming separate point solutions.

Business profile

Sector
Construction
Team
Operations, commercial and finance
Workflow
Project-centred operating environment

One project and document context shared by operational, commercial and finance work, with permissions and approvals designed into the architecture.

Inputs and outputs

Inputs

  • Project and client master data
  • Existing BMS and document structures
  • Commercial, finance and operational workflows
  • Roles, permissions and system integrations

Outputs

  • Global and project dashboards
  • Single project and document records
  • Context-aware applications and approvals
  • Cross-project priorities, audit and management information