The asset register is the ledger. Everything else is commentary.
Milestone sign-off and governance structure across energy-sector programs. What makes this sector distinct is weight: capital projects that run for years, an asset base that dominates the balance sheet, and maintenance systems the ERP does not own but depends on completely. Walk the five decisions, find your seat, then run the two-minute check.
Five calls that decide an energy program
Made at design, judged at the first capital close and the first outage. Pick a decision.
Asset hierarchy, work order types and capitalization rules get designed by finance, while the people who create the work are in maintenance and operations.
Design the asset and work structure with maintenance, operations and finance in the same room, before conversion.
This structure decides what can be capitalized, what gets expensed, how maintenance cost is analyzed and what regulatory reporting can be produced. Designed by finance alone, it will be internally coherent and disconnected from how work gets raised, which produces misclassification at volume rather than in exceptions.
Who from maintenance and operations signed off the asset and work order structure?
The maintenance management system already runs. Work orders, asset condition and materials consumption originate there, and the ERP receives them.
Name a client-side owner for the interface itself, and agree what the master is for each shared record before design.
Two systems each holding an asset record with neither being definitively master is the recurring failure here, and it produces a reconciliation that becomes a permanent manual task. In an asset-heavy business that reconciliation is not a nuisance, it is the integrity of the balance sheet.
Which system is master for the asset record, and where is that written down?
The plan looks for a quiet period. In an operating environment the only genuine windows are planned outages, and they are scheduled for reasons that have nothing to do with your program.
Sequence cutover around planned outage and turnaround schedules, and treat those dates as fixed inputs rather than as negotiable constraints.
Outage schedules are set by safety, regulatory and commercial requirements and they do not move for a systems program. Attempting to cut over outside one means doing it while the asset base is running, which raises the stakes on every rollback decision.
Which planned outage windows are we sequencing around, and who confirmed the dates?
Capital projects run for years and will straddle the cutover. Conversion planning treats them as open balances rather than as in-flight records with history that matters.
Design the conversion of in-flight capital projects deliberately, including how history and commitments carry, and reconcile before and after.
A capital project that loses its cost history at conversion cannot be audited, cannot support a regulatory filing, and cannot be closed correctly when it finishes. Because these projects run for years, the damage from a poor conversion arrives long after the program has been declared successful.
How will in-flight capital projects reconcile before and after cutover?
Field competency, qualification and safety training records get scoped as standard HR data.
Treat qualification and safety records as controlled data that must migrate with history and stay in sync with what people are permitted to do.
Qualification status governs who is allowed to perform work. If that record is wrong or loses history at conversion, the exposure is not administrative, it is operational and regulatory. It also drives scheduling eligibility, so an error surfaces as an inability to staff work rather than as a data issue.
Do qualification and safety records migrate with full history, and who verified that?
What those five mean for the chair you sit in
Energy programs get judged by regulators and by operations, on long horizons. Each seat's exposure, the early sign, and the question worth asking this quarter.
Work originates outside the ERP
Work orders, asset condition and materials consumption are created in the maintenance system by people whose job is keeping plant running. If the structure does not match how work gets raised, misclassification happens at volume. Outage windows are also the only genuine cutover opportunities, and they are set by safety and regulation.
The asset and work order structure was signed off without maintenance in the room.
Does the work order structure match how our crews raise work?
The asset register is the balance sheet
Capitalization decisions, work-in-progress and the asset register dominate the financial position in this sector. A conversion that treats them as reference data produces plausible and wrong numbers, and in-flight capital projects that lose history cannot support an audit or a regulatory filing years later.
In-flight capital project conversion is scoped as opening balances only.
How do we prove capital work in progress reconciles across cutover?
Qualification governs who can work
Competency, qualification and safety training records determine who may perform which work. Treated as standard HR data, they migrate without history and drift out of sync with scheduling eligibility, which surfaces as an inability to staff work safely rather than as a reporting problem.
Qualification records are scoped with no retention or history requirement stated.
Do qualification records migrate with history, and who has verified a sample?
Four points where the damage arrives late
Decision four, drawn out. Capital work runs for years, which means a conversion error here is not discovered during hypercare. It is discovered during an audit or at project close.
This is the sector where a conversion decision outlives everyone who made it. Design the reconciliation evidence in, and retain it.
Four items already on the calendar
None of these are energy-specific, and all four land on an asset-heavy program. Verify each against your own estate before the next steering meeting.
Engineering stopped at the end of 2025. Moving off it is a reimplementation rather than an upgrade, and any shift-based workforce is in scope.
Extended maintenance runs to 2030 for a fee. If the target platform is a lift and shift of ECC, it arrives with a published expiry date attached.
Oracle support runs past 2036. When an integrator sells urgency on that basis, the pressure is customization debt and scarce skills, not vendor abandonment. Knowing the difference is a negotiating position.
Not a deadline, a treadmill. Two mandatory regression cycles annually, permanently, and the item most reliably missing from a post-go-live staffing plan.
Five questions worth more than a readiness assessment
Answerable from memory, scored on this page, nothing captured and nothing emailed.
These five are the start of the instrument. A full review also covers regulatory reporting lineage, materials and inventory design, the EAM interface inventory and hypercare exit criteria. Or skip the tooling and book the program review.
Running an asset-heavy program?
Pre-SOW, mid-build, or preparing for a capital close on a new platform. I sell no software and staff no builds, so these questions get asked out loud. Tell me where the program is and I will tell you what I see.