THE INTELLIGENT ASSET LEADERSHIP PROGRAMME
The decision still belongs to you.
15 Sessions · 25 Minutes Per Day · Three Weeks · Free · For the owners and operators of Nigeria’s energy assets
Everything this programme rests on, on one page, taken from the book. Print it and keep it in the folder you take to the asset review. How should leadership decide what to inspect, maintain, repair, replace or retire, and what evidence should justify the decision? The objective is competent ownership: recognising what matters, deciding within authority and completing the required work.
| Framework | What it says |
|---|---|
| The Operating-Intelligence Loop | Sense, decide, act, learn. For an asset owner the loop has a physical ending: a recommendation must reach a work order, an operating restriction, further investigation or another justified disposition, and a repair must return its actual findings to the equipment history. |
| The Data-Foundation Precondition | Choose the decision first, then establish the evidence needed to support it. Separate an absent record from a record showing an acceptable condition. Data readiness is use-specific; a model estimate never quietly becomes an inspection observation. |
| The Autonomy Ladder | Retrieve, draft an interpretation, recommend an action or execute a permitted workflow step — each with a defined boundary. Authorise individual actions, not a vague level of trust. A language model never becomes an informal route for changing a protection setting, accepting a pressure boundary or approving continued operation. |
| The Value-versus-Risk Map | Consider the consequence of an error alongside the expected benefit. Legal conditions, protection requirements and engineering acceptance are necessary gates; a large commercial benefit does not compensate for failing them. Examine the harm of delay too. |
| The Sequencing Discipline | Begin with a bounded operating problem; test the evidence, compare a simpler alternative, validate, rehearse, then use within approved limits. A change of service, data source or model version can invalidate the original test. |
| The Operations-Excellence Lens | Measure the effect on work and decisions. Keep activity separate from outcome: reading more reports is activity; a checked decision pack assembled faster may be an outcome; preventing a particular failure is a counterfactual claim. Do not label all three as savings. |
These frameworks are management tools proposed by the author. They are not statutory tests, engineering standards or evidence of regulatory approval.
| Field | What belongs in the record |
|---|---|
| Decision and boundary | The question, equipment identity, system, service and period covered |
| Required function | What the asset must deliver and the conditions relevant to that duty |
| Current evidence | Source identifiers, dates, methods, revisions and accepted limitations |
| Material uncertainty | What is unknown and which choice it could change |
| Current disposition | The authorised position, conditions, validity and review trigger |
| Eligible options | Options accepted for comparison and their technical basis |
| Recommendation | The preferred next commitment and the reasons for it |
| Authority | Technical acceptance, operating decision and spending approval as applicable |
| Execution | Scope owner, prerequisites, resources, window and acceptance evidence |
| Reassessment | Expiry, operating change, new finding or other trigger requiring review |
| Closure | Evidence of accepted completion and updates returned to controlled records |
One record for a material condition or lifecycle choice, a proposed management tool. Where specialists disagree, state the competing interpretations and the evidence that could resolve them; do not average the opinions into an apparently agreed condition rating.
| Period | Main work |
|---|---|
| Days 1 to 30 | Establish the decision and baseline: write the charter with the users, measure the baseline from actual records where available, and agree the simpler alternative. |
| Days 31 to 60 | Build and rehearse: connect the minimum approved data, test against reviewed examples including difficult cases, rehearse the workflow and its failure, and retain the accepted version and test record. |
| Days 61 to 90 | Evaluate useful work: use the application within approved limits, record corrections and rejections, compare with the baseline and the simpler method, and hold a decision review. |
Ninety days is a useful management period for a bounded proof, not a promise that every integrity or reliability application can be validated in one quarter. The day-ninety review decides: continue within scope, extend evaluation, revise the design, expand under stated conditions or stop.
| Measure | Definition and use |
|---|---|
| Material decisions without a current disposition | Count of in-scope material conditions lacking an accepted current position; review individually |
| Critical work overdue | Count and age against the applicable approved due basis; distinguish categories and consequences |
| Evidence conflicts affecting decisions | Open conflicts that prevent a defined decision, with owner, age and route to resolution |
| Restricted-operation conditions | Current restrictions, their validity, monitoring and approaching review or expiry |
| Critical work readiness | Necessary prerequisites passed for each critical package; show failed gates separately |
| Alert usefulness | Confirmed relevant alerts divided by alerts reviewed, using an agreed event and review definition |
| Missed target events | Defined events not flagged within the useful response window; investigate individually |
| Decision-to-action time | Elapsed time between accepted decision and the specified executable action, with delay causes |
| Accepted intervention completion | Work accepted against stated criteria, distinguished from work merely reported complete |
| Benefit evidence | Forecast, observed operational result and verified cash effect recorded as separate states |
Proposed starting points and the author’s management synthesis. Set asset-specific definitions and escalation rules before collecting them; the book sets no universal targets. Record four clocks — observed, assessed, decided, completed — and keep a benefits ledger in which forecast, observed operational change, financially verified and withdrawn are separate states.
| # | Session | Plan section |
|---|---|---|
| 1 | The Asset Does Not Read the Presentation and the Reader's Toolkit | Section 1 — Our company, the one asset decision we will carry, and where AI could help. |
| 2 | Ownership Is a Continuing Obligation | Section 2 — The required function, who owes the next decision, and the asset verified from field label to board paper. |
| 3 | Integrity Under Uncertainty | Section 3 — The evidence record, the uncertainty that could change the decision and its deadline. |
| 4 | Criticality Before Prediction | Section 4 — Criticality, dependencies, exposure kept apart from readiness, and the gates outside the budget contest. |
| 5 | Inspection Must Resolve a Decision | Section 5 — The inspection the decision needs: method, evidence deliverable and the chain to disposition. |
| 6 | Reliability Begins with the Failure Mode | Section 6 — The target failure mode, the simpler comparator and the response window. |
| 7 | Pipelines and the Responsibility to Contain | Section 7 — Containment traced to location, assessment and disposition, with a response behind the surveillance. |
| 8 | Offshore Integrity and the Cost of Access | Section 8 — Access, evidence and contingency planned together, and the required service followed through its supporting systems. |
| 9 | Repair, Replace or Operate with Restrictions | Section 9 — Eligible options, the accepted technical scope before price, and restrictions with reassessment conditions. |
| 10 | Shutdown Readiness Is More Than a Date | Section 10 — Readiness by evidence: the window's work, its clocks, the critical path and the restart decision. |
| 11 | Life Extension Must Be Earned | Section 11 — The future duty and the end of life: extension gates, obsolescence, retirement obligations and funding. |
| 12 | Govern the Intelligence You Rely On | Section 12 — The application governed: owners, permitted use, review, fallback and the acceptance and change record. |
| 13 | Capital Allocation That Survives the Downside | Section 13 — The capital case: feasible options on a common lifecycle basis, the downside, affordability and the committee checklist. |
| 14 | People, Contractors and the Right to Challenge | Section 14 — People, contractors and the right to challenge, with the board measures we will report. |
| 15 | The Board Review: Your Signed 90-Day Intelligent Asset Plan | The signed 90-Day Intelligent Asset Plan. |
ERW CommandAsset · built on The Intelligent Asset — An Operating Doctrine for AI in Asset Integrity, Reliability and Lifecycle Decisions by Ritchie Wingo. Leadership training, not investment, legal or engineering advice; no design calculation, inspection procedure, fitness-for-service assessment or permission to continue operating equipment. Back to the programme home →