19650 review: the major project perspective part 2
15 April 2026
19650 review: the major project perspective part 3
16 April 2026
In the third and final part of his review of the 19650 revisions, Lawrence Chapman details the missed opportunity: converging information management and project controls.
There is a lost opportunity in the revised standard that deserves to be named plainly, because it is arguably the most consequential gap of all, not for what it gets wrong, but for what it declines to attempt.
Every major programme operates with two parallel information disciplines that rarely speak to one another. On one side sits information management: the ISO 19650 world of information models, CDE workflows, status codes and information production schedules. On the other side is project controls: the schedule, the cost model, the earned value analysis, the risk register, the change control log.
Both disciplines have mature standards bodies. Both have professional communities, competency frameworks and best-practice guides. ISO 19650 governs the first. The AACE International Total Cost Management framework, the APM Body of Knowledge, and the emerging ISO 21508 (project, programme and portfolio management – earned value management) and ISO 21511 (work breakdown structures for project and programme management) standards govern the second. And the two worlds almost never formally intersect.
The consequence for every major programme is what practitioners call the integration problem. The design model says one thing, the programme says another; the cost plan reflects a third reality; and the risk register was last updated when the design was two iterations old.
Reconciling these parallel information environments consumes enormous resources, introduces latency into every decision, and generates precisely the kind of information error that the Get It Right Initiative (GIRI) has documented as the primary driver of avoidable rework. The Infrastructure and Project Authority’s (IPA) project data analytics work has identified the inability to correlate design maturity with cost and schedule performance as a fundamental obstacle to benchmarking and improving major programme delivery.
The Infrastructure Client Group’s Project 13 enterprise model, which the IPA actively promoted as the framework for next-generation infrastructure delivery, is built on precisely this premise: that the separation of design information from project controls data is an organisational dysfunction, not a natural state, and that integrated data environments – in which the model, the schedule, the cost and the risk are facets of a single managed information environment – are both achievable and necessary.
The Major Projects Association’s (MPA) work on programme data and analytics makes the same case from a different angle: that the decisions made on major programmes are only as good as the information that informs them, and that fragmented information disciplines produce fragmented decisions.
The scope and the opportunity
The revised ISO 19650 had the scope, the moment and the conceptual foundation to address this. The standard’s new emphasis on information purposes, on the decisions that information must support, creates a natural bridge to project controls, where every cost forecast, every schedule update and every risk assessment is precisely a decision-support activity.
The information production requirements framework in clause 5.4.2 – with its structured approach to defining what information is needed, at what level of granularity, against what acceptance criteria, and by what dates – is directly applicable to the specification of project controls data as a managed information deliverable. The asset information model, properly conceived, should be the repository not just of design geometry and technical data, but of the configuration baseline against which programme performance is measured.
None of this is present in the revised standard. The words ‘project controls’, ‘earned value’, ‘schedule’, ‘cost’ and ‘risk register’ do not appear. The linked enterprise systems concept in Part 1 gestures towards integration with ‘work planning and scheduling systems’ and ‘enterprise resource planning systems’, but this is listed as an optional capability of enabling technologies rather than a governance requirement of information management.
The opportunity to formally position the integrated project information model – in which design information and project controls data share a common information architecture, naming conventions, status codes and governance framework – as the target state for major programme information management has been declined.
This is not a criticism that a note or an annex could address. It would require a fundamental reconception of what the standard is for: not merely the governance of design and asset information, but the governance of all programme-critical information, including the information that drives delivery decisions. That reconception is work for a future edition, for a joint working group between ISO/TC 59/SC 13 and the project management standards community, or for a UK-specific supplementary standard developed under BSI auspices. But it should be on the record – through the MPA’s B/555 submission, and through industry commentary, that the opportunity existed, was visible, and was not taken.
The final verdict
The revised ISO 19650 is a better standard than its predecessor. The purpose-led information framework, the whole-lifecycle scope, the activity-level accountability model, and the structured information production requirements process are all genuine improvements that, properly implemented, have the potential to reduce the information-related waste that GIRI has quantified and the IPA has flagged as a systemic programme delivery risk.
But ‘properly implemented’ is doing a lot of work in that sentence. The standard is written for a world of single appointing parties, sequential projects, and conventional procurement hierarchies. The major projects community increasingly operates in a world of alliance contracts, concurrent programmes, regulated hold points, and federated information environments. The gap between those two worlds is wider than the revised standard acknowledges.
The MPA’s engagement with the BSI B/555 mirror committee before the 2 June voting deadline is therefore not merely a procedural exercise. It is an opportunity to put on record, on behalf of the major projects community, the specific structural adaptations that the standard must acknowledge if it is to serve the programmes on which the UK’s infrastructure future depends. The commenting deadline is approaching. The case for substantive comment is strong.
The opinions expressed are the author’s own and do not necessarily reflect the views of his employer.
The deadline for feedback on the 19650 review is 3 May. Read the draft of the revised Part 1. Read the draft of the revised Part 2.
Keep up to date with DC+: sign up for the midweek newsletter.
Story for Digital Construction Plus? Get in touch via email:
[email protected]
