Project Delivery Management System
Reproducible decision support from governed project records.
PDMS governs capital-project delivery, project controls and portfolio oversight across portfolios, programmes and projects, with project workspaces supporting risk, quality, safety, approvals and completion forecasting.
Where evidence is insufficient, PDMS reports that a conclusion cannot be supported.
Completion forecasts are derived from observed run-rate and reported with best, mean and worst positions. Where available history is insufficient, no forecast is produced.
Forecasts with reproducible assumptions
Completion forecasts report best, mean and worst positions from observed run-rate, with the underlying spread and source history retained for review.
Register-derived answers with traceable figures
Questions are answered from registered domain topics and governed register figures, with traceability to source workspace records. Where no supported answer exists, PDMS does not improvise one.
Decision authority remains human
Gate outcomes are recorded human judgements supported by evidence and audit history. PDMS calculates decision-support information and records the authorised decision.
Register governance is assessed separately from register content
Unrated risks, unowned risks and registers without review cadence are reported explicitly so governance gaps remain visible alongside assessed risk content.
Unrated risks remain visible in risk distributions rather than being omitted from The register view.
- Unrated risks remain countedRisks without an approved rating are reported separately rather than omitted from severity reporting.
- Unowned is namedA risk with no owner is reported as unaccountable, because that is exactly what it is.
- Above project levelProgramme and portfolio risks remain visible in their governing registers even when not represented on individual project pages.
Organisation, portfolio, programme, project and facility hierarchy
Figures aggregate along the organisation, portfolio, programme, project and facility hierarchy, with programme-level risks and unscoreable projects surfaced explicitly.
Gate decisions remain human judgements supported by governed evidence
Thirteen governance workspaces per project retain evidence supporting decisions across engineering, procurement, contracts, cost, schedule, controls, construction, readiness and related disciplines.
- Concept and selection
- Portfolio fit
- Options assessed
- Approval recorded
Gate outcomes remain authorised human judgements with supporting evidence retained.
- Definition
- Engineering scope
- Cost basis
- Schedule baseline
Discipline posture reports the coverage supporting each figure rather than implying complete coverage where evidence is partial.
- Execution
- Progress against baseline
- Risk position
- Interface obligations
A project placed on hold is reported as on hold, with its restart plan identified for confirmation, rather than being misclassified as simply behind schedule.
- Readiness and handover
- Completions position
- Documents issued
- Close-out actions
Projects that cannot be scored are identified explicitly and excluded from aggregate averages.
Supplied is distinct from accepted
Interfaces distinguish supplied, accepted and overdue states so unresolved dependencies are not confused with agreed delivery positions.
- Every workflow transition records who performed it and why
- A slipped interface does not create a cost value on this page. Financial exposure remains governed by cost control.
- Obligations that cannot be resolved against supplier or discipline registers are reported as broken references.

Seven licensed modules across three editions with server-side entitlement enforcement
PDMS navigation reflects licensed capabilities, with server-side entitlement controls determining which modules and seats are available to each organisation.
Portfolio and projects
Organisation, portfolios, programmes, projects and facilities form the delivery hierarchy, with portfolio health assessed across projects and exclusions reported explicitly.
- Organisation
- Portfolio
- Projects
- Portfolio health
The governance workspace
Thirteen governed workspaces cover engineering, procurement, contracts, cost, schedule, planning, controls, construction, readiness and handover, stage gates, actions, issues and decisions.
- Governance
- Stage gates
- Cost
- Schedule
- Controls
- Construction
- Readiness and handover
- Actions and decisions
Delivery
Resources, logistics and inter-party interfaces are governed against the project record rather than retained only in coordination discussions.
- Resources
- Logistics
- Interfaces
Assurance
Risk, quality, health and safety, approvals, documents, lessons and close-out are reported both for current content and for register-governance health.
- Risk
- Quality
- HSE
- Approvals
- Documents
- Lessons and close-out
Analysis and reporting
Metadata-driven reports are produced from governed operational records, with cross-application search and notifications where configured thresholds are reached.
- Reporting
- Report library
- Schedules
- Global search
- Notifications
Administration
Configuration, audit, access review, data protection, control posture, licensed capabilities and data management are governed with server-side entitlement controls.
- Configuration and audit
- Access reviews
- Data protection
- Control posture
- Licensed capabilities
- Data management

Seventeen roles operating across one governed delivery estate
Portfolio directors, executive sponsors, project directors, engineering managers, project-controls teams, commercial teams, construction and commissioning managers, and assurance functions work from the same governed delivery hierarchy.
- Per-project governance workspaces support distinct disciplines rather than one undifferentiated project record
- Portfolio health assessed across projects with exclusions reported explicitly
- Access reviews, control posture and data protection are governed as distinct assurance areas
More of what the application covers
- Stage-gate decisions retain the evidence considered
- Portfolio health with unscoreable projects identified explicitly
- Risk registers are reviewed against their own defined cadence
- Readiness and handover as a project workspace
- Resources and logistics aligned with the delivery plan
- Lessons and close-out held with the project
- Seven licensed modules across three editions with server-side entitlement enforcement
- Queued field changes replay safely after reconnection without duplication
Reproducible from source records
Completion forecasts report best, mean and worst positions based on observed run-rate and available project history. No forecast is produced where history is insufficient.
Answers derived from governed registers
The registered-domain assistant composes answers from governed register figures and provides traceability to source workspace records. Where no supported answer exists, it returns no answer rather than improvising.
Decisions remain human and are recorded
Gate outcomes are recorded human judgements supported by evidence and audit history. PDMS calculates supporting information but does not make the decision.
Database-enforced organisation isolation
Row-level security is enforced on organisation-scoped data using a runtime role without bypass privileges, with automated policy-completeness checks.
Integrated delivery governance connected to specialist applications
- IFMSIFMS: Interface Management SystemIFMS provides dedicated interface governance where inter-party boundaries require their own register and lifecycle.
- BCMSBCMS: Budget & Cost Management SystemBCMS provides dedicated budget, commitment, actual and forecast governance where deeper cost-control capability is required.
- CCMSCCMS: Completion, Commissioning & Handover Management SystemCCMS provides deeper completion and commissioning control through certificate libraries, inspection and test records, punch control and handover evidence.
- LLMSLLMS: Lessons Learned Management SystemLLMS maintains lessons as governed knowledge records for reuse beyond project close-out.
Review PDMS using one of your portfolios.
Bring one portfolio and its project history. The demonstration will show portfolio health, explicit exclusions and the completion forecast where available evidence supports one.

