Campaign, Production plan, Batch records — which one is for what?
Three add-ins run production alongside the shift log. Which one fits depends on how the plant works: batch-wise (it produces in campaigns) or continuous (production lines run to a daily plan). Batch records work with either.
In short
Section titled “In short”| Campaign | Production plan | Batch records | |
|---|---|---|---|
| For whom | a batch-wise plant that runs campaigns | a continuous plant with production lines | a plant that produces in batches, with or without campaigns |
| What you plan | one campaign: one product, one time window, one total quantity | up to 6 plan rows per production line and day: product, grade, quantity / day, target tank, changeover time | no plan: you open, run and close the batch |
| State | phases: Planned → Start-up → (Ramp-up) → Production → Shutdown → Closed | no phases: the line’s operating mode and running product | open, closed or voided batch |
| Who writes the operating mode | the campaign phase | the production lines’ periods (Changeover, Stop) | it does not write it, it only reads it (to block opening) |
| Own PDF | campaign PDF | — (the shift log PDF shows the plan of the time) | batch record PDF |
Batch-wise or continuous
Section titled “Batch-wise or continuous”- Batch-wise plant. The plant makes one product for a planned period, then shuts down, and the next campaign has to be started again. This is what Campaign is for: the campaign plan with approval, the start-up checklist, gate signatures and phases. Campaign windows on one plant cannot overlap.
- Continuous plant. The production lines run continuously, and the product changes to plan. This is what the Production plan is for: daily plan rows per line, and the Operating-mode timeline recorded per line (“Record per production line”). “Changeover” and “Stop” write the same line state as the shift log. Day-to-day use and the production-line start-up: Production plan add-in overview.
- Batches. If the plant produces in batches (mixer, reactor), Batch records run the batch: steps or events, lab samples, target grade, release. On a campaign plant the batch is linked to the campaign running when it is opened; elsewhere the batch has no campaign.
The two meanings of “plan”
Section titled “The two meanings of “plan””The word lives in two places, and the two are not connected:
- The campaign plan is a single item: product, planned start and end, planned quantity. After approval, a change is a revision with a reason.
- The Production plan is a daily breakdown per line: which day, which product, how much, into which tank, when it changes over. Every change goes into the change log.
Because a plant runs either campaigns or production lines, only one of the two plans is ever active on one plant.
Where the produced quantity comes from
Section titled “Where the produced quantity comes from”“Actual” means each add-in’s own figure. The system never adds them together, and it always says which one it used.
| Where the figure appears | Where it comes from | Example |
|---|---|---|
| Campaign Progress (and the actual column of Campaign analytics) | The campaign plant’s selected log field (“Actual-quantity field”) over the closed shift logs in the campaign window. If the campaign has no log entry at all, the production sheet’s produced-quantity column. | Three closed shift logs: 38 + 41 + 40 = 119 t. The plan is 600 t, progress is about 20%. A log that is still open is not counted. |
| Production plan, Analytics Actual – quantity | The quantity of the line’s periods on the Operating-mode timeline. | One day on line 1: 06–14 “Product A” 42 t, 14–22 changeover, 22–06 “Product B” 18 t. Actual is 60 t, against the plan’s “Quantity / day”. |
| Batch | The batch’s own steps, events and lab rows. | A batch’s discharged quantity shows on the batch record and in batch analytics; it does not count towards campaign progress. |
When they match and when they don’t. Campaign progress and line actuals never run on the same plant at the same time, so they cannot contradict each other. A batch quantity and the log field, however, can describe the same production. If they differ, it is a recording question (another time, another unit), not a calculation error.
What is shared
Section titled “What is shared”- Products. One product list serves Campaign, the Production plan, Batch records and Quality specifications. If you add or rename a product, it shows that way everywhere.
- Start-up. The same machinery: start-up checklist, completing items, gates, signatures.
- On a campaign plant it is the campaign’s Start-up phase.
- On a production line it is the plan row’s “Start-up before this row” flag, or “Open start-up” by hand.
- On a production line the Production plan add-in is enough; the Campaign start-up add-in is not needed. Its permissions (editing the checklist, gates, opening) are listed with the campaign permissions, because the two start-ups share them.
- The production-line start-up’s base checklist is on the Production plan Settings tab, on the “Start-up base checklist” card, one per plant. Every new start-up opens with a copy of it, and changes for a single start-up are made on that start-up’s page. The campaign base list is a separate list and belongs to the Campaign start-up add-in.
- Quality specifications. The plan row’s grade and the batch’s target grade come from the same source.
Why the two exclude each other on one plant
Section titled “Why the two exclude each other on one plant”A plant’s operating mode has to be written in one place, otherwise two timelines would say different things about the same hour:
- on a campaign plant the campaign phase writes it (according to the phase ↔ operating-mode mapping in Campaign settings), with no manual writing;
- on a plant that records per line the production line periods write it.
So a plant is either a campaign plant or records per line. If you try to switch on both for one plant, the screen stops you:
- in Campaign settings: “This plant records the operating mode per production line — campaign control and per-line recording are mutually exclusive on one plant.”
- in the operating-mode element settings: “Per-line recording cannot be switched on for a campaign-controlled plant.”
One site can have a campaign plant and a production-line plant, as separate plants.
Mixed plant: production lines and batches together
Section titled “Mixed plant: production lines and batches together”If you also run batches on a production-line plant (for example a mixer ahead of the line), this is the situation today:
- batches can be opened and run, without a campaign;
- by default a batch is not linked to a production line — which is right when the batch is made in a mixer or vessel ahead of the line;
- if the batch is made on the line (filling or packing line, continuous line with batch numbering, several parallel lines running the same product), switch on Link batches to a production line for the plant on the Settings tab of Batch records (only possible on a plant recorded per production line). Then pick the line in the Production line field of the “New batch” dialog (optional — “No production line” is also a choice). Prefill: if one line of the plant is producing, that one; if several, the one making the selected product; otherwise empty. The chosen line shows as a badge in the batch list and on the batch sheet, and it cannot be changed after opening. If you switch it off later, batches already linked keep their line, new ones are not linked;
- for a batch linked to a line, the “Batch sheets can’t be opened in these operating modes” block looks at its own line’s operating mode (instead of the plant’s): a line in a blocked mode is shown disabled in the dialog, with the mode’s name. A site-wide block always wins;
- for a batch opened without a line, the block looks at the plant’s and the site’s mode by default, not the lines’. In the same place, the Production lines choice lets you set per plant that opening warns (“Warn if a production line is in a blocked mode”) or is refused (“Block if a production line is in a blocked mode”). If another line can be opened then, the batch can be opened on that line;
- a batch cannot be linked to a Production plan row, and its quantity does not count towards the line’s actuals;
- batches opened before the line field stay without a line (they are not back-filled).