Have you got "line of sight" on your asset enhancement value chain?
Consider the moment an enhancement transfers into service and the operations team registers nothing unusual, because the new asset behaves precisely as the network expected. Its data populates the correct systems, its maintenance regime is already resourced, and customers experience continuity rather than change. That outcome is attainable, and it rests less on engineering excellence than on a single organisational discipline: maintaining an unbroken line of sight between your strategic objectives and every decision taken on the enhancement.
Most network owners recognise the alternative. Enhancement teams optimise for completion, operations teams optimise for availability, and the two collide at an outage or possession window where each discovers the assumptions the other had been making. So can you trace the line of sight on your current enhancement? Where a delivery decision cannot be linked to what your network must achieve, you are probably carrying a risk that nobody has priced.
Discover: what line of sight actually means
Line of sight is the traceable alignment, articulated across ISO 55000 and ISO 55001, that connects organisational objectives to the asset management policy, the strategic asset management plan and the asset management objectives, and ultimately to the plans and activities affecting each asset. It is not a diagram but a chain of decisions in which each link explains and justifies the next.
For the owner of a live network, that chain must extend further than conventional practice assumes. It has to encompass the incumbent asset in service, the enhancement under development, and the interface between them. Because all three draw upon the same people, the same investment envelope and the same operational windows, a weakness in any one link becomes a binding constraint on the others.
Diagnose: where the line breaks on a live network
Root cause analysis across enhancement programmes tends to converge on three fracture points.
Objectives diverge. The business case promises additional capacity while availability and safety objectives are established elsewhere, so no single forum weighs one against the other when the programme slips.
Information arrives late or in an unusable form. Asset data generated during design and construction does not reach operations and maintenance in the format, system or timeframe they require.
Accountability shifts at handover. The individuals who understood the trade-offs depart precisely when the decisions become more difficult.
Each fracture carries a commercial consequence: extended outages, rework inside the commissioning window, maintenance regimes that begin late, and benefits that materialise after the business case said they would. The asset owner ultimately bears that cost, irrespective of which party caused the break. Behaviour underlies all three. People raise a conflict between programme and operations early only where psychological safety exists, and every week of silence compounds the eventual expense.
Design: construct the line of sight before the asset
Treat the line of sight as a deliverable in its own right, and make three commitments before procurement begins. PAS 4010 sets the framework for this step: it asks asset owners to embed productivity from the outset, by shaping how work is packaged, how the market is engaged, and how value chain members are appointed and commercially aligned, so that integration is designed in rather than discovered at handover.
Establish shared objectives. Combine enhancement objectives and network service objectives into a single set, accompanied by an agreed method for trading them off against one another.
Specify the asset information requirements. State what operations must receive, in what format and by when, then embed that requirement in every relevant appointment.
Plan integration as work rather than as an event. Assign outage planning, commissioning and operational readiness to named owners with defined budgets and dates.
Then test each appointment against a single question: does this individual understand both the construction risk and the operating risk?
Where the answer is no, pair them with someone who does.
Deliver: integrate without interrupting service
Integration performs best as a sequence of small, rehearsed transitions rather than a single large cutover. Stage the change, rehearse it thoroughly, and verify each step against agreed service measures before committing to the next. Retain operations and maintenance colleagues in design reviews and commissioning, so that their tacit knowledge informs the project early rather than surfacing as defects after handover.
The return is straightforward to describe even where it is difficult to forecast. Each outage window that holds protects service performance and avoids contractual penalties, and fewer defects at handover translate into reduced early-life maintenance expenditure. When the lessons return through the asset management system, continuous improvement ensures that the next enhancement begins with a shorter and stronger line of sight.
Your next step
Select one enhancement that is currently in development. Take its next outage or closure window and trace it upward through the asset management plan, the strategic asset management plan and your organisational objectives. Where the chain breaks, name an owner and repair that link first.
Stop handing over. Start integrating.
Comments