The Doctrine Card

Everything this programme rests on, on one page, taken from the book. Print it and keep it in the folder you take to the operating review. Begin with a decision that matters. Establish the evidence and the simpler alternative. Bound the application’s authority. Test the response and reconcile the result. Expand when the operating routine earns that decision.

The six frameworks

Framework	What it says
The Operating-Intelligence Loop	Sense, decide, act and learn. Draw the loop around a single decision: its information source, decision owner, action route and result record. The loop fails when an alert has no owner or when an action has no feedback.
The Data-Foundation Precondition	Useful intelligence needs traceable evidence. Start with the evidence necessary for the chosen decision and keep absences visible: an estimated value must not acquire the status of an approved measurement. Separate event time from posting time.
The Autonomy Ladder	Explain or summarise; recommend; prepare an action for approval; perform a narrowly authorised administrative action. Each step requires a separate permission decision, and consequences determine the control required. Physical equipment control, emergency functions and operating safeguards require their own engineered assurance.
The Value-versus-Risk Map	Compare the value of a better decision with the consequence of error, and keep the categories separate. Ask what happens when the recommendation is wrong, when it arrives late, when none arrives and when staff treat it as authoritative.
The Sequencing Discipline	Establish the baseline, improve essential evidence, test a bounded application, evaluate the response and decide whether to expand. Include cases in which the system should decline to recommend, and define the conditions for stopping before the pilot starts.
The Operations-Excellence Lens	The business measures saleable product, reliable movements, dependable deliveries, safe operation and cash. Measure whether the recommendation reached a person who could act, then whether the action changed the outcome.

These are author frameworks used across the Intelligent Series, not official technical standards.

The four ledgers

Ledger	What it describes
Physical	Stock and movements
Ownership	Entitlement, commitments and restrictions
Movement	Authorisation, execution and handovers
Financial	Value, liabilities, invoices and receipts

A tank can be full while the operator owns little of its contents. Product can be owned while it is unavailable for dispatch. A delivery can be complete while its invoice is disputed. Link the ledgers through controlled movement identifiers; when they disagree, record the issue, evidence version, responsible person, next action and review date.

The ninety days

Period	Main work	What leadership should hold
Days 1 to 30 Establish the operating truth	Select a product, facility and decision; map the four ledgers and handovers; agree the baseline and how economics will be valued; compare the application with a simpler alternative	A signed pilot charter, defined evidence sources, accountable owners, evaluation cases and an agreed stop condition
Days 31 to 60 Test the decision and response	Run in a bounded mode with human review and the existing authorised route; test incomplete data, changed instructions and disruption; review evidence and workflow weekly	Where the system helps, where it fails, whether the response is practical, and the recurring cost
Days 61 to 90 Decide, do not merely extend	Reconcile operational results and finance-approved benefits; review control issues, workload, training and support; test recovery	A decision to scale, revise, continue within a bounded scope or stop

The first 90 days are a management sequence, not a guarantee of a fully transformed terminal. Approval at one site is not approval for every terminal archetype.

Twelve leadership priorities

Establish one controlled product and movement identity.
Reconcile physical stock at an agreed boundary and basis.
Keep ownership and release restrictions visible.
Close custody evidence before it becomes an invoice problem.
Investigate loss without turning a prediction into a verdict.
Schedule using confirmed constraints and explicit forecast ranges.
Coordinate ship and shore readiness through accountable handovers.
Improve dispatch readiness across the whole journey.
Keep equipment integrity within competent engineering authority.
Bound data access and autonomy by action and consequence.
Reconcile service, working capital and reported benefits.
Build a local team that can challenge and sustain the routine.

The terminal board scorecard

Area	What the board should see
Inventory	Gross unresolved residuals, cause status and age, with boundary, basis and denominator; confirmed physical loss shown separately from timing and record corrections
Custody and quality	Movements awaiting accepted evidence, unresolved claims and stock subject to release restrictions
Scheduling and service	Commitments met, avoidable conflicts, readiness failures and changes after approval
Equipment	Constrained availability, overdue integrity actions, recurring failures and resources required for an approved response
Distribution	Delivery against commitment, failed receiving events and unresolved acceptance evidence
Capital and cash	Usable owned inventory, restricted capital, receivable duration, unbilled completed movements and funding need
AI control and capability	Applications, owners, authority levels, significant changes, incidents and unresolved support needs, including systems restricted or stopped

For every red or amber issue, state the decision required, options, consequence of delay and accountable owner. The acceptance gates — input readiness, technical performance, workflow readiness, authority, safety and security, economics and capability — are recorded separately, each with its reviewer and unresolved action. Do not combine them into an average that lets an attractive financial return cancel an unacceptable authority or safety problem.

The 10 sessions and the plan they build

#	Session	Plan section
1	The Product Has Left the Refinery and the Reader's Toolkit	Section 1 — Our company, its terminal archetype, the one decision we will carry, and where its loop breaks.
2	From Product to Value: The Intelligent Terminal Company	Section 2 — The value map for our decision, the operating model behind it and the review that will own it.
3	The AI-Ready Tank Farm and the Four Ledgers	Section 3 — The evidence our decision needs and the four ledgers that must reconcile around it.
4	Custody Transfer, Commercial Trust and Exception Investigation	Section 4 — Our custody evidence and the route by which an exception becomes a supported finding.
5	Tank Allocation, Storage Scheduling and Berth Coordination	Section 5 — Our schedule and readiness plan: confirmed constraints, forecast ranges and accountable handovers.
6	Loading Gantries, Dispatch Performance and Equipment Integrity	Section 6 — The real dispatch constraint and the integrity authority our decision must respect.
7	Product Distribution, Quality Release and Process Safety	Section 7 — From release to accepted delivery: our quality authority and the safeguards AI will not replace.
8	AI Governance, Cybersecurity and Controlled Autonomy	Section 8 — The governance record and permission by action for our application.
9	Working Capital, Terminal Economics and Local Capability	Section 9 — The economics of our decision without double counting, and the team that sustains it.
10	The Terminal Game Plan	The assembled, signed Terminal Game Plan.

ERW CommandTerminal · built on The Intelligent Terminal — An Operating Doctrine for AI in Petroleum Storage, Logistics and Distribution by Ritchie Wingo. Leadership training, not legal, investment or engineering advice. Back to the programme home →

THE INTELLIGENT TERMINAL LEADERSHIP PROGRAMME

From released product to collected value.