Skip to content

Running a batch: opening, steps, hourly rows, closing

A batch lives on one sheet across shifts: its steps, hourly readings and lab results gather in the same batch. You can run it from the shift diary (quick actions) and from the batch record (full view); both write the same data.

  • Permission: batch:record to open and record, batch:close to close, batch:reopen to reopen and void.
  • Batch production is switched on for the plant, and the product has a published template (Batch template).
  • On a campaign plant a new batch can be opened in the campaign’s Ramp-up and Production phases. In Shutdown only running batches can be finished and closed; on interruption a running batch stays open and writable. On a continuous plant (no campaign) opening does not depend on a phase.
  1. Open. On the Batches tab of the Batch records page choose New batch, or use New batch in the Batch sheet box of the shift diary. Pick the plant and the product (if “Link batches to a production line” is on for the plant, also the Production line — prefilled, “No production line” is also a choice). The batch number is a suggestion (format NNN/YY, e.g. 256/26) and can be changed; the recording time and your account are automatic. Open batch. Several batches can be open at once.
  2. Steps from the diary. In the Batch sheet box, at the next step use Start now, Done now or Record value. The button records the moment you click. The box marks rows from the previous shift.
  3. Steps on the batch record. Click the batch in the list to open its sheet. Open a step and enter the actual value, the from–to time (with two dates; the sheet marks crossing midnight), the operator(s) (several with a slash: AB/CD), optionally Entered by (on a shared account: who typed it; your account is recorded anyway) and a note. Now enters the current time.
  4. Hourly row. New row (or Record row now in the diary): the time and the template’s columns. A value outside its limit is marked.
  5. Correct. A filled-in field can only be changed as a correction, with a reason (at least 5 characters); the old and the new value stay in the chain. Your own fresh entry can be corrected without a reason for 15 minutes. Correcting someone else’s row needs the Data series: correct permission.
  6. Close. Close batch. If a required step is missing, the sheet lists it; a pending lab does not block closing. After closing, the steps and hourly rows are read-only and the content gets a seal (hash).
  7. If it has to be reopened: Reopen, with a reason. The previous seal stays in the chain; the next closing computes a new one. Faulty opening or scrap: Void, with a reason. It is final: the batch is not deleted, its number stays taken, and it can no longer be written.

If Diary timeline: batch events is on for the plant (see Switching on batch records), shift staff can record a batch event from the diary’s operating-mode timeline (Record batch event), and on campaign plants start an interruption from there (Record breakdown / interruption). Such an event also appears on the batch sheet’s Events timeline among the other events; the On batch sheet link in the diary leads here. Steps: Record the operating mode in the diary.

The batch is Closed, the top of the sheet shows the start of the content seal, and the Events timeline has the opening and the closing. A lab result can still arrive after closing; the seal does not include it.

What you see Why What to do
“The batch number format is NNN/YY” The format is different. Fix it, e.g. 256/26.
“The year in the batch number isn’t this year” The year comes from the plant’s current year. Check the number.
“This batch number is already taken for this product” Numbers are unique per product. Pick another.
“A new batch can’t be opened in the campaign’s current phase” Start-up or Shutdown in the campaign. Wait for Ramp-up, or carry on with the running batches.
“This field is already filled in” A filled field can only be corrected. Use Correct with a reason.
“You can’t record for a time this far in the past” / “A future time can’t be recorded” The time is outside the allowed window. Fix the time.

Last updated: