
Everything this programme rests on, on one page, taken from the book. Print it and keep it in the folder you take to the project review. An intelligent EPC company begins with a delivery discipline. AI becomes part of that discipline; it does not replace it.
| Framework | What it says |
|---|---|
| The Operating Intelligence Loop | Sense, decide, act and learn: evidence becomes an authorised choice, the work is done, and the outcome returns to the people responsible. |
| The Data Foundation Precondition | Evidence must be adequate for the intended decision. A preliminary quantity can support an early option comparison while being inadequate for a firm fixed-price commitment. |
| The Autonomy Ladder | Retrieval of permitted information, drafting for review, advisory recommendation, then bounded execution as a separate permission. Permission attaches to a task, population, user and environment. |
| The Value versus Risk Map | Estimate the value of a changed decision and examine the consequence of error. Financial benefit cannot offset an unacceptable engineering, legal or safety condition through a weighted average. |
| The Sequencing Discipline | A bounded workflow with an owner, usable evidence and a feasible response; repair the process first; compare with a simpler alternative; shadow mode where consequences justify it; expand only after accepted criteria are met. |
| The Operations Excellence Lens | Measure accepted delivery, cost, cash, quality, safety, reliability and capability. A better model score is evidence about a model, not direct evidence of project profit or client acceptance. |
These frameworks are the author’s synthesis, not official standards.
Every material recommendation identifies the decision requested, evidence cut-off, alternatives, assumptions, uncertainty, constraints, owner, authority, resources, response deadline and outcome review. Keep recommendation, approval, execution and assurance as separate states.
| Item | Review question |
|---|---|
| Problem | Which delivery decision is currently weak or late |
| Population | Which projects, packages, users and records are included |
| Inputs | Which sources are authoritative and sufficiently current |
| Output | Retrieval, draft, forecast, recommendation or defined action |
| Comparator | Existing method and simpler credible alternative |
| Authority | What is permitted and who approves consequential action |
| Exclusions | Which tasks, data and environments remain outside scope |
| Evaluation | Representative, challenge, permission and recovery cases |
| Release gates | Mandatory conditions, owners and evidence |
| Resources | Development, review, support and response capacity |
| Economics | Full cost, counterfactual, benefit ownership and downside |
| Continuity | Manual process, suspension and provider exit |
| Days | What happens |
|---|---|
| 1 to 30 | Map the decision and current workflow; establish the baseline; define population, source cut-off, ownership and permitted authority; reconcile identifiers; select the simpler comparator; agree release conditions, incident response and manual fallback; decide whether development is justified. |
| 31 to 60 | Build the bounded service and test each response stage; operate in shadow mode with actual users; measure reviewer time and whether recommendations arrive while action is possible; update the investment case. |
| 61 to 90 | Prepare the release argument; authorise only the defined use; train users through practical tasks; establish monitoring and change control; review outcomes with finance; retain, narrow, improve, withdraw or expand. |
Scaling is an evidence decision. A decision to repair the process before building is a valid programme outcome.
| # | Session | Plan section |
|---|---|---|
| 1 | The Project That Looks Healthy and the Reader's Toolkit | Section 1 — Our company, the one decision chain we will carry, and where its loop breaks. |
| 2 | The Leadership Mandate | Section 2 — The commitment, the portfolio entry and the board's evidence. |
| 3 | The Nigerian EPC Operating Model | Section 3 — The business specified, the Nigerian conditions modelled and the commitment chain traced. |
| 4 | Project Evidence and Data Architecture | Section 4 — Identities, the state at decision time, reconciliation and the source register. |
| 5 | AI Methods That Fit EPC Decisions | Section 5 — The method that fits our decision and how it would be evaluated. |
| 6 | Authority, Governance and Technical Assurance | Section 6 — The governed use, its approval conditions and its assurance argument. |
| 7 | Opportunity Selection, Tendering and Estimate Integrity | Section 7 — What we agree to carry, the estimate basis, the modelled exposure and the bid record. |
| 8 | Contract Intelligence and Responsibility Boundaries | Section 8 — The agreement, the promise tracked through interfaces and the contract assistant's test. |
| 9 | Front End Definition and the Design Basis | Section 9 — The engineering problem, configuration and bounded surrogate models. |
| 10 | Detailed Engineering and Multidiscipline Coordination | Section 10 — The revision followed, checking versus generation and the engineering output contract. |
| 11 | Constructability, Configuration and Digital Twins | Section 11 — Constructability, the digital model's purpose and its value through intervention. |
| 12 | Procurement Intelligence and Supplier Qualification | Section 12 — The requirement, qualification matched to consequence and the procurement advisory. |
| 13 | Long Lead Equipment and Expediting | Section 13 — The long-lead forecast, the response economics and technical control in recovery. |
| 14 | Fabrication Quality, Traceability, Logistics and Preservation | Section 14 — Traceable identity, executed inspection and arrival tracked to usability. |
| 15 | Nigerian Content and Supplier Capability | Section 15 — Capability by design, observable outputs and evidence that matches the claim. |
| 16 | Work Packaging and Construction Readiness | Section 16 — Executable work, readiness as a conjunction and a bounded release service. |
| 17 | Productivity, Resources and Subcontractor Delivery | Section 17 — Productive output measured, the work system changed and competence preserved. |
| 18 | Schedule Intelligence, Cost Control and the Estimate to Complete | Section 18 — Delivery logic, stated assumptions, a common scope and the forecast of remaining work. |
| 19 | HSEQ and Work at Operating Facilities | Section 19 — Support for the management system, meaningful leading indicators and their limits. |
| 20 | Commissioning, System Completion and Handover | Section 20 — The usable system, accepted completion states and evidence kept with configuration. |
| 21 | Change, Claims and Dispute Evidence | Section 21 — The event preserved, its consequence connected and the review pack specified. |
| 22 | Security, Privacy and Client Information | Section 22 — Information boundaries, retrieved content as data and provider exit. |
| 23 | Model Validation and Operational Release | Section 23 — The claim, the dataset, the response chain and the explicit threshold. |
| 24 | People, Capability and Organisational Learning | Section 24 — Competent owners, demonstrated competence, honest incentives and succession. |
| 25 | Finance, Treasury and Portfolio Exposure | Section 25 — Profit and funding separated, currency exposure and the benefits ledger. |
| 26 | Daily Portal Monitoring and Commercial Readiness | Section 26 — Monitoring with a source basis and a digest that leads to decisions. |
| 27 | PSR Discipline, Completeness and Coaching | Section 27 — The report structure, real completeness and coaching the action. |
| 28 | Quote Preparation and Commercial Completeness | Section 28 — The visible commitment, the requirement-to-quote matrix and complete pricing. |
| 29 | The Intelligent Project Review | Section 29 — The integrated position, the weekly rhythm and a scorecard that leads to decisions. |
| 30 | The Executive Commitment: Your Signed 90-Day Intelligent EPC Programme | The signed 90-Day Intelligent EPC Programme. |
ERW CommandEPC · built on The Intelligent EPC — A Leadership Doctrine for AI in Nigerian Engineering, Procurement and Construction by Ritchie Wingo. Leadership training, not investment, legal or engineering advice. Back to the programme home →