Every plan is a best intention.
A plan assumes every decision is made the same way, by someone who sees everything. In practice, hundreds of recurring decisions are made by different people on different shifts, each with different information, experience and risks to weigh. That is where the gap between the plan and the plant begins.
One decision, made by a different person every shift.
Take one recurring decision: how hard to run the unit. The plan gives one answer. Over a week of shifts, the people making the call give twenty-one different ones, and each makes sense to the person who made it.
- Monday night shift, crew B Holds well back. A trip on nights gets remembered for years; margin left on the table rarely gets noticed.
- Tuesday day shift, crew A A heavier feed arrives mid-shift. Each console reacts on its own, and the unit swings before it settles.
- Thursday day shift, crew C Pushes hard after the morning meeting, with the latest prices in mind. The night shift never saw them.
- Saturday night shift, crew D Follows an old rule: never run it above this line. Nobody remembers why it was set.
On paper, and in practice.
The gaps show up in five places. In each one the plan is sound on paper. What happens in practice depends on who is making the call, and what they know at the time.
- On paper
- A safe operating envelope, and procedures for the abnormal.
- In practice
- Each shift draws its own line inside the envelope, some wide, some tight. When an unexpected disturbance hits, each console reacts on its own.
- Why
- The risks are lopsided. Nobody is rewarded for the margin they could have made, and everyone remembers an incident.
- On paper
- Equipment wears as it works. Run a unit harder and it produces more, and wears faster. The plan balances the two.
- In practice
- Someone once said never run it above a certain point, and the rule outlived the reason. The limit stays fixed while what the plant needs keeps changing.
- Why
- A rule of thumb is safer to repeat than to question.
- On paper
- Weigh the economic and operating tradeoffs, and run close to the constraints that pay.
- In practice
- Each person keeps a cushion from the constraint, and the cushions add up. After an upset, the unit finds its way back slowly.
- Why
- The giveaway cannot be seen from the console. Nobody sees what their own cushion costs.
- On paper
- Environmental and quality limits built into the day-to-day targets.
- In practice
- The limits are run either far inside, to be safe, or close and reactively, pulled back after the alarm.
- Why
- A breach is personal and immediate. The cost of running far inside the limit is spread out and unseen.
- On paper
- Complex operation written down as repeatable procedures.
- In practice
- The best moves live in experienced people's heads, and preferences and opinions vary from crew to crew. As people retire, that judgment leaves with them.
- Why
- Procedures capture the steps, not the judgment behind them.
The gaps are human. Nobody is at fault.
Every call on this page makes sense to the person making it. What differs is what each person can see at the time, what they have lived through, and what they will be held to account for.
Better procedures, more meetings and clearer handovers narrow the spread. They cannot remove it, because the decisions keep coming, every shift and every hour, and a different person makes each one.
One model makes the recurring decisions the same way, every minute.
Imubit learns your plant from its own data, cause and effect included, and makes the key recurring decisions every minute with the whole picture in view. Your experts set the objectives and the limits, and your operators can take over at any time. The judgment of your best people stays with the plant on every shift.