The capital project ends at handover. The operating organisation lives with the procurement decision for years afterwards.
The Week 6 slides deliberately extend procurement planning beyond design and construction into operations and maintenance. They refer to O&M contracts, critical spares, inventory management, repair, testing, fabrication, machining, calibration, engineering services and software support.
This broadens the procurement objective.
The enterprise is not buying only an asset or completed project deliverable. It is buying the future ability to operate, maintain and support that outcome.
The Strategic Context
Project teams are often incentivised around capital delivery.
They focus on purchase price, installation and commissioning.
Operating teams inherit:
- spare-parts availability;
- proprietary tools;
- licensing;
- maintenance obligations;
- support response times;
- calibration needs;
- specialist labour requirements;
- documentation quality.
A procurement can therefore meet the capital budget while creating a high-cost or fragile operating model.
What Leaders Commonly Misread
The first mistake is assuming whole-life value means only adding projected maintenance cost to purchase price.
Lifecycle procurement is also about capability, availability and dependency.
The second is leaving spares and support decisions until commissioning.
The third is accepting proprietary dependencies without understanding future bargaining power.
The fourth is assuming the supplier that builds the asset should automatically provide long-term support. That may be appropriate, but it should be a deliberate sourcing decision.
Reframing the Issue
The stronger question is:
What must remain true after handover for the asset or service to keep creating value?
That includes:
- maintainability;
- parts availability;
- technical knowledge;
- software access;
- service capacity;
- repair pathways;
- data;
- training.
The procurement requirement should therefore describe not only delivery, but sustainment.
Strategic Analysis: Handover Can Transfer Hidden Dependency
Hypothetical engineering example: A plant buys a specialised machine at a competitive price. Two years later, a proprietary control component fails. Only the original supplier can configure the replacement, and support lead time is eight weeks.
The original project may have been reported as successful.
The operating system is not resilient.
A lifecycle procurement strategy might have considered spare controls, source access, local service capability, training or alternative support arrangements before award.
The point is not to eliminate supplier dependence. Some specialised systems justify it. The point is to understand and price the dependence deliberately.
Decision Framework
Evaluate lifecycle procurement across six dimensions.
Availability
What support is required to keep the asset or service operational?
Spares
Which parts are critical, long-lead or obsolete-prone?
Skills
What capability must remain inside the organisation?
Supplier dependence
Which activities can only the original supplier perform?
Data and documentation
What information is required for safe operation and maintenance?
Commercial model
Should support be bundled with acquisition or sourced separately?
These questions belong in procurement planning rather than post-project recovery.
From Strategy to Execution
Immediate action: add operations and maintenance representation to significant procurement planning.
Medium-term capability building: require lifecycle support plans for critical assets and systems before contract award.
Long-term strategic positioning: use operating data to improve future procurement decisions. Failure rates, support responsiveness, spare usage and lifecycle cost should influence supplier strategy.
This closes the loop between project procurement and operational excellence.
Governance Implication
Lifecycle planning also changes the evaluation model. A supplier with the lowest acquisition price may require expensive proprietary support, while a higher-priced alternative may have broader service coverage, better documentation or more accessible spare parts. These differences should be visible before award if they are material to the operating model.
Operations teams can contribute evidence that project teams do not yet possess: failure modes, maintenance intervals, critical-spare usage, technician availability and practical support expectations. Their involvement should therefore begin during requirement definition rather than during handover.
For strategic assets, leadership may also need an obsolescence view. Components, software versions and specialist skills can become unavailable long before the physical asset reaches the end of its economic life. Procurement planning should ask what the organisation will do if the supplier exits the market, changes technology or withdraws support. That is a resilience question, not merely a maintenance question.
A further lifecycle question is commercial exit. If maintenance support is bundled for many years, the buyer should understand renewal, transition and data-return arrangements before award. Long-term support can create continuity, but it can also create switching cost. That trade-off belongs in the acquisition decision, not at the end of the first support term.
Signals to Monitor
Watch for assets entering service without critical spares, maintenance manuals arriving after handover, reliance on one overseas technician, software licences or subscriptions not budgeted beyond project completion and operating teams discovering proprietary restrictions after award.
Questions for the Leadership Team
- What must be available for this asset to remain operational after handover?
- Which dependencies will sit with the original supplier?
- What critical spares should exist before commissioning?
- What knowledge must be transferred to the operating organisation?
- Should support be bundled with acquisition or competed separately?
- Are lifecycle outcomes influencing future supplier selection?
Closing Perspective
A procurement is not complete when the asset arrives.
It is successful when the enterprise can operate, maintain and adapt the outcome reliably over its useful life.
That requires leaders to procure the lifecycle capability, not just the initial deliverable.
Related article: From Lowest Price to Best Value: The Economics Leaders Miss in Procurement
Related article: Outsourcing Without Hollowing Out the Organisation
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.