Plan, start-up, actual: the path of production in the shift log
The plan lives in a spreadsheet that gets emailed round, the start-up on a printed checklist, the actual in the shift log — and at the end of the week someone pieces together by hand where things stand. Production plan and Campaign start-up are two Shift log add-ins for exactly this: the plan turns into a start-up checked with signed gates, and the actual comes from the shift log. Which one you need depends on how your plant runs.
In short
- Two add-ins, two kinds of plant: the Production plan is for continuous production lines, Campaign start-up for batch plants that produce in campaigns. They are ordered separately, and either works without the other.
- One shared mechanism: the same product list, the same start-up (start-up checklist, signed gates, timeline) and the same Quality specifications.
- The actual comes from the shift log: on a line from the quantities of its periods, in a campaign from the designated diary field of closed logs. The system never adds the two together, and always says which one it used.
- The plan suggests, the shift decides: the product actually running is recorded by the shift.
What is wrong today?
Plan and actual are two separate worlds. The plan is a spreadsheet the production manager sends round; the product actually running, the changeover time and the quantity are in the shift log or in people’s heads. Plan vs actual is manual work, and by the time it is done, next week’s plan is already being written.
Start-up is the riskiest moment. On paper the checklist can be ticked, but afterwards nobody can see who ticked it and when, who released production, and whether production started before the list was complete.
Which one does your plant need?
Both add-ins solve the same question for two different kinds of plant. They are ordered separately; one site can run both, on separate plants.
Production plan
Continuous production lines — the lines run, and the product changes according to plan.
- Up to 6 plan rows per line and day: product, grade, quantity per day, target tank, changeover time; the plan can be repeated to the following days.
- An Overview per line: running or stopped, the running product and since when, today’s plan, the next changeover.
- Changeover, Start and Stop with the plan’s suggestion; a change log with restore.
- Start-up on a production line: flag a plan row “Start-up before this row”, or open one by hand.
- Actual: the quantities of the shift log’s line periods.
Campaign start-up
Batch plants — one product for a planned period, then shutdown and a new start-up.
- Campaign plan: product, time window, total quantity; approval, after which a change is a revision with a reason.
- Phases: Planned → Start-up → (Ramp-up) → Production → Shutdown → Closed; the phase writes the operating mode.
- Signed gates at phase changes; some steps can advance automatically.
- A start-up checklist and, with the Training module, who takes which exam.
- Actual: the campaign plant’s designated diary field from closed logs; a campaign PDF with QR verification.
On one plant the two exclude each other, because the operating mode has to be written in one place: on a campaign plant by the campaign phase, on a line-recording plant by the line periods. If you try to switch on both, the interface stops you and says why.
The path: from plan to actual
In both add-ins the steps follow each other like this; what differs is the shape of the plan and the source of the actual.
Plan
Daily plan rows on a line, an approved campaign plan in a campaign. Every change leaves a trace: a plan row’s in the change log, a campaign plan’s as a revision with a reason.
Start-up
A start-up checklist from the plant’s base list; the shift completes the items (tick, check, measurement, N/A with a reason). On a line, a planned start-up opens by itself before the start, 24 hours ahead by default.
Signed gates
“Ready for start-up”, then “Start-up approved”, only on a complete list; on a line the second gate is signed by someone other than the first. Every step with time, actor and reason on the timeline.
Production
On a line, “Start production” is one click; the production gate is configurable (off, warn with a reason, block). In a campaign, the Production phase.
Actual
The shift log provides it: the quantities of the line’s periods, or the campaign plant’s designated diary field. Open periods and periods without a quantity do not count: a gap is “not recorded”, not zero.
What the plant sees
The production manager plans, the shift records — and both see the same thing.
- Home page
- The Current production block shows per line what is running now, today’s plan and the next changeover; the Campaigns block shows progress and the expected end. Items or gates waiting for you appear under My to-dos.
- Shift log
- The Production plan block with today’s and the next day’s plan; with an open start-up, the state of the checklist. In a campaign, the phase indicator in the log header and in the shift PDF.
- Produced-quantity helper
- Next to a period’s quantity, “Calculate” suggests a value from a formula using the period’s data; taking it over only fills the field, the operator decides.
- Analysis (with Analytics)
- A plan vs actual grid and Plan – quantity / Actual – quantity metrics per line and product; campaign analytics.
- Campaign PDF
- The path of a campaign in one document, with QR verification.
Product A · Standard · since 06:00
- Today’s plan
- all day Product A · 80 t / day · Tank 1
- Next changeover
- tomorrow 14:00 · Product B
no product running
- Today’s plan
- from 14:00 Product B · 40 t / day
- Next changeover
- —
Start-up in progress: 14 / 20 items
Ordering: two separate add-ins
- Production plan and Campaign start-up are two separately orderable add-ins; either works without the other. Both are Shift log add-ins and part of a custom quote: request them on the Add-ins tab of the Control panel, and OPEREX switches them on.
- For start-up on a production line, the Production plan is enough; Campaign start-up is not needed.
- Plan vs actual needs the “Record per production line” mode of the shift log’s operating-mode element and per-period quantity recording — the plant switches these on.
- The plan row’s grade needs Quality specifications, the plan vs actual grid the Analytics module, and assigning exams the Training module.
What it does not do
So you know what to expect — and what not.
- The plan does not switch production over: it suggests, and the shift records the running product.
- It does not schedule or optimise: the production manager writes the plan; the system does not calculate capacity or sequence.
- The campaign plan and the Production plan are not connected, and they never run on the same plant.
- There is no live ERP or process-control connection: you write the plan in the interface, and the shift log provides the actual.
- A Training-type start-up item cannot be used on a production-line start-up.
Further reading
Frequently asked questions
What is the difference between the Production plan and Campaign start-up?
The Production plan is for continuous production lines: daily plan rows per line, and the actual is the quantity of the line periods. Campaign start-up is for batch plants: a campaign with one product, a time window and a total quantity, with phases and signed gates, and the actual is a designated diary field. One plant runs one of them.
Can the two be ordered separately?
Yes. They are two separate add-ins, and either works without the other. For start-up on a production line, the Production plan is enough; Campaign start-up is not needed.
Where does the produced quantity come from?
From the shift log. On a line from the quantities of its periods (open periods and periods without a quantity do not count), in a campaign from the campaign plant’s designated diary field in closed logs. Batch quantities count towards neither, and the system always says which source it used.
Let's start a pilot
We'll show you OPEREX on your own operational processes — no strings attached.
Request a demo