Skip to content

Switching on batch records per plant: switch, shift group calendar, permissions

The batch record is the technology sheet of batch production: a batch can run across several shifts and calendar days, yet it has one sheet. The diary belongs to the shift, the batch record to the process: closing the diary does not close the batch. The feature is switched on per plant; it works without campaigns, on continuous plants too.

  • Two add-ins are needed: Batch records and Rolling data series. The platform operator switches both on for the company; until both are there the page says so.
  • Permission: batch:configure for the switch and the calendar. By default it belongs to the Production manager.
  • The Batch records menu item shows for anyone who may view them. For the person who configures, it shows even when no plant is switched on yet.
  1. Open the Batch records page and choose the Settings tab.
  2. On the plant’s row switch on Batch production (batch record) (Switch on). A plant with an open batch cannot be switched off.
  3. Enter the Shift group calendar (28 days): the date of the first line, the shift slots (name and start, comma separated) and the lines for the 28 days, one day per line, one group letter per slot in the line, separated by spaces. Save calendar.
  4. If no new batch may start in some operating modes of the plant (for example during a shutdown or maintenance), expand the Batch sheets can’t be opened in these operating modes row, tick the modes and Save operating modes. The choice is the company’s operating-mode list (Control panel → Lists). Empty means no limit. On a plant recorded per production line, the Production lines choice decides whether opening also looks at the lines’ operating mode: by default it does not, but it can warn or block when a line is in a blocked mode. This applies to batches opened without a line: for a batch linked to a line, its own line decides. In the plant’s row, on a plant recorded per line: Link batches to a production line (off by default) — when on, “New batch” also asks for the line. Use it when the batch is made on the line (filling or packing line); not for batches made in a mixer or vessel.
  5. If shift staff should also record batch events from the diary, set the Diary timeline: batch events row (see below).
  6. On the Permissions tab check which action needs which permission, and whether you have it. Roles get their permissions in the control panel’s permission matrix.
  7. Continue with the batch template: a batch can only be opened on a published template.

The Diary timeline: batch events row in the plant’s line opens the setting (off by default). Here you tick which event types appear on the diary’s operating-mode timeline and in the shift PDF’s operating-mode block, and which of them change the operating mode.

  1. Open the plant’s line and tick the types under Diary timeline: batch events. The choices are the event types of the plant’s published templates, each marked time span or point in time.
  2. In the Operating-mode change list choose the mode the plant switches to for the event, or leave Does not change the mode.
  3. Save timeline setting.
  • Only a time-span event can change the mode, a point event cannot.
  • On campaign plants only the campaign’s interruption reasons can be chosen as the mode, because the campaign writes the mode there.
  • The mode list is edited in the control panel → Lists tab; a mode that is not on the list is dropped on save.

The box of an open batch (the home page Open batches block, the diary Batch record element, the Batches tab Vessels board and the shift PDF) shows at most three bands. By default the template structure decides:

  • on an event-based template: Target · Last event · Measurements;
  • on a step-list template: Steps (how many steps are done and which section is running) · Measurements · Last step (if the template asks for a target grade, Target comes first).

A band the template cannot provide (e.g. Last event without an event section) is not shown; a band that applies but has no data yet says so (“no measurement yet”, “no step recorded yet”).

You can override this per plant: in the plant row, under Box bands, choose Custom order and pick up to three bands. The Shown as preview lists, per template kind, what will be shown, and says when a chosen band does not appear on a template. Save bands. Automatic restores the template-based assignment.

Action Permission By default
View batch records and templates batch:view Board and outside operators, Shift leader, Production manager, Site manager
Open a batch, record steps and hourly rows batch:record the same
Close a batch batch:close Shift leader, Production manager
Reopen a closed batch, void a faulty one batch:reopen Production manager
Edit and publish templates batch:template Production manager
Switch batch production on or off, calendar, blocked modes batch:configure Production manager
Correct a recorded step with a reason batch:correct Production manager; Shift leader and Site manager by their diary-edit scope

Recording a lab result needs the Data series: record permission, because the lab result is the same data on the Data series page and on the batch record.

The plant’s row reads Switched on, the New batch button on the Batches tab is available (once a template is published), and the Batch sheet box appears in the shift diary.

What you see Why What to do
“Batch records are not switched on” One of the add-ins is missing for the company. Contact OPEREX.
“No plant uses batch production” No plant is switched on yet. Switch one on in the Settings tab.
Switching off does not work The plant has an open batch. Close or void every open batch.
“the plant is in “Shutdown” mode” next to New batch The plant’s open period in the diary is a blocked mode. If the plant runs again, close the period in the diary and open one with the real mode. On a campaign plant the campaign phase writes the mode: advance the phase there. If the limit is wrong, untick the mode on the Settings tab.
“(no longer on the list)” next to a mode, and a warning on the Settings tab The mode was removed from the operating-mode list (or a list save before 2026-11-09 rewrote its key); the limit still stores the old key, new periods cannot use it, so the block has no effect. Untick it, tick the mode that is on the list, and save. Renaming a mode on the Lists tab no longer changes its key.

Last updated: