An asset management maturity assessment identifies where improvement is needed. Real value depends on organising findings around business capabilities, assigning clear ownership and building a programme the organisation can realistically deliver.
Our earlier guidance on getting practical value from a maturity assessment covered preparation: building a shared understanding of what asset management is intended to achieve, and having senior leaders consider the value sought from assets before becoming absorbed in clauses and process gaps. This article covers what comes after.
How should an organisation turn assessment findings into a coherent and deliverable improvement programme?
Transferring every finding into an action register is rarely the right answer. Findings often overlap, several may arise from the same capability gap, and some may already be addressed through existing initiatives. Without further design, the result can be a fragmented collection of actions competing for the same resources.
A credible improvement programme needs to:
Integrate with existing priorities
Organise the response around capabilities
Match the response to the scale of change
Assign delivery and enduring ownership
Maintain traceability without creating bureaucracy
Aim for competence, not perfection
Sequence for dependencies and capacity
Plan early for certification, where it is intended
Integrate with existing priorities
The assessment is a significant source of evidence, but will rarely represent all the programme inputs. Consider its findings alongside:
Asset management objectives
Existing business and asset management plans
Current improvement and technology initiatives
Regulatory and statutory commitments and how these are forecast to change
Available resources and delivery constraints
This avoids creating a separate “ISO programme” that competes with other work. Conformance requirements and business priorities should reinforce each other within one programme.
Organise the response around capabilities
A common mistake is to create projects the level of individual assessment criteria or clauses of ISO 55001. This keeps a surface-level link to the assessment but splits related work across separate projects.
A better organising principle is the business capability that needs to be established or improved, such as risk and criticality, asset information governance, planning, fleet strategies, maintenance work management or assurance. This allows one project to address several findings while remaining connected to the processes and owners that will sustain the capability.
Each project should describe what the organisation will be able to do when the work is complete, rather than merely naming a deliverable.
Develop an Asset Management Planning Standard.
The organisation has an approved and operating asset management planning process that applies value- and risk-based decision-making proportionately and maintains traceability from an identified need, risk or opportunity through treatment selection and investment planning.
In this example the Asset Management Planning Standard may be important, but the document is not a capability. The organisation must implement the process, establish ownership and demonstrate that it works.
A well-defined capability outcome also gives the project a clearer boundary. It helps identify the people who need to participate, the evidence required for closure and the person who should own the resulting capability.
Organisations need not develop every method independently. Peers may provide useful templates, risk methods, maintenance approaches, information practices and assurance techniques. This is particularly valuable for smaller organisations with fewer internal specialists but strong sector relationships. Peer material must still be adapted to the organisation’s assets, systems, risks and competencies. The capability lies in understanding, approving and maintaining it, not simply adopting another organisation’s procedure.
Match the response to the scale of change
Not every finding requires a project. A project suits work that needs coordinated design, implementation or organisational change. Proportionate governance applies enough control for reliable delivery without unnecessary administration. A programme may therefore use three types of response:
Standard Capability Project
Used where the change is material, cross-functional, novel or involves significant implementation effort.
Small Capability Project
Used where the improvement is contained, with clear ownership and manageable interfaces.
Business-as-usual action
Used where the activity operates, maintains, communicates or progressively rolls out an established capability.
Standard and Small Capability Projects apply the same disciplines at different scales.
For example, developing an asset criticality methodology, supporting tools and an initial application may require a Capability Project. Applying the approved method to future commissioned assets should become a business-as-usual responsibility.
Similarly, establishing a Fleet Strategy Standard, developing a template and completing a representative pilot may warrant a project. Producing the remaining Fleet Strategies over time may then become a governed rollout programme.
Every Capability Project should define its outcome, scope, deliverables, ownership, implementation evidence and closure requirements.
Assign delivery and enduring ownership
A Capability Project needs two accountabilities: a Project Lead who delivers the change, and a BAU Owner who sustains the capability after closure.
Project Lead
Delivers the change
- Forms the project and coordinates participants
- Manages scope, dependencies and delivery
- Produces the agreed deliverables
- Assembles implementation evidence
BAU Owner
Sustains the capability
- Accepts the implemented capability
- Operates and maintains the process or system
- Keeps controlled requirements current
- Monitors performance and improvement
The same person may hold both roles, but the accountabilities should still be distinguished.
The BAU Owner should be involved from the start. Otherwise, the project may produce a sound solution that does not fit normal business arrangements or have a committed organisational home.
A useful test is:
Who will be accountable two years after the project closes if the capability is no longer current or operating effectively?
Project closure should include BAU Owner acceptance, confirming that the capability is implemented and resourced and that remaining actions have moved into controlled business arrangements.
Maintain traceability without creating bureaucracy
The programme needs a clear connection to the findings that prompted it. Otherwise, it is difficult to demonstrate that gaps are addressed or findings can be closed.
A lean Traceability Register has three core elements:
Source findings and other programme requirements
Approved projects and business-as-usual actions
Relationships between them
Each material finding should have one programme item accountable for leading the response. Contributors should be recorded only where another item must provide a distinct deliverable, control or evidence required for closure.
Against each finding, the register also records the response and the evidence required for closure.
The asset management system is not yet fully defined
Asset Management System Framework project
Approved framework, defined process interactions, agreed ownership and evidence of implementation
Project completion does not automatically close every linked finding. A project may establish and approve a process, while the related finding remains open until the process has operated, generated records and demonstrated effectiveness.
Aim for competence, not perfection
For competent operation or ISO 55001 readiness, maximum maturity across every asset management subject is unnecessary.
For example, an organisation may establish asset information standards and data governance, and remediate its most critical asset classes first, without achieving complete data quality across the whole register.
Remaining gaps must be understood, risk-assessed and governed, but not necessarily eliminated. This prevents programmes becoming unnecessarily broad or consuming resources better used elsewhere.
The target should be a management system that is appropriate to the organisation’s context, capable of delivering its objectives and able to improve over time.
Sequence for dependencies and capacity
Some capabilities provide foundations for others. Scope and direction may precede common frameworks and core processes, while evaluation and assurance follow once capabilities are operating.
Technical logic alone does not make a programme deliverable. Projects may require the same specialists, systems or approval forums, and new processes need time to generate evidence before audit or review.
The programme should therefore consider:
Hard dependencies between projects
Shared specialist and leadership resources
Business, regulatory and technology cycles
Time required for implementation and operating evidence
Discovery and design for later projects can overlap with delivery of earlier ones. A credible schedule balances logical sequencing with the organisation’s capacity to lead, contribute, approve and embed the work.
Dates should initially be treated as a planning hypothesis. They should be tested with the proposed Project Leads and BAU Owners and refined as project boundaries become clearer.
Plan early for certification
An improvement programme establishes capability. Certification readiness demonstrates that the capability operates across the defined scope and can withstand independent assessment.
The GFMAM Guidance for an Asset Management System Scheme for Accredited Certification to ISO 55001 highlights the need for a clear scope, current Asset Management Policy and SAMP, controlled boundaries and evidence that the system operates effectively.
The programme should reserve time after implementation for capabilities to operate and generate records. The organisation should then:
Complete a full asset management system internal audit
Address material findings and verify corrective-action effectiveness
Conduct management review before presenting the system for certification
Early engagement with an accredited certification body can help confirm scope, audit stages and evidence expectations.
Certification should result from demonstrated operating capability, not a deadline that forces an immature system into audit.
A final programme check
Before approving the programme, confirm:
Existing priorities and initiatives are incorporated
Findings are grouped around coherent capabilities
Each project defines an operating capability outcome
Each response is matched to the scale of change
Project Leads and BAU Owners are identified
Each material finding has one accountable lead item and defined closure evidence
Remaining gaps are understood, risk-assessed and governed
Dependencies and resource conflicts are visible
There is enough time to implement, operate, audit and improve the capability
Conclusion
A maturity assessment does not automatically provide an implementable programme.
Meaningful change comes from integrating findings with existing priorities, grouping them around capabilities and assigning clear delivery and enduring ownership. Traceability must not become so complex that maintaining it competes with delivery.
For organisations seeking certification, the final test is whether the resulting capabilities operate, produce evidence and support the value sought from assets.
Turn assessment findings into sustained improvement Asset Dynamics helps infrastructure organisations translate asset management maturity and conformance findings into practical improvement programmes with coherent capability outcomes, clear ownership, proportionate governance, traceability and realistic sequencing.
Get in touch