Skip to content

Production plan add-in overview

The Production plan is a Shift log add-in for continuous plants with production lines: the lines keep running, and the product changes according to the plan. You write plan rows per line and per day (which product, which grade, how much, into which tank), and the shift records what actually runs. The add-in also runs the start-up of a production line: start-up checklist, gates, signatures, and then starting production.

If your plant produces in campaigns, the Campaign is likely the better fit. The difference, and how Batch records relate: Campaign, Production plan, Batch records — which one is for what?

The plan lives per plant and per production line. A day can have at most 6 plan rows; the fields of a row:

Field What it means
Product From the shared product list (the Campaign, Batch records and the Quality bank use the same one).
Grade The product’s grade from the Quality bank. Without the Quality bank, the row has no grade.
Quantity / day The planned daily quantity, in the product’s unit (e.g. t).
Target tank Which tank the product goes into (free text).
From this time Only on further rows of a day: the local time of the changeover. “The day’s first row applies to the whole day.”
Reason for the change Optional; it goes into the change log.

The plan is a suggestion: the running product is not set by the plan but by what the shift records (Changeover, Stop).

  • The Production plan page in the header’s Shift log menu. It has three tabs: Plan (opens first), Overview and Settings. With several plants, you pick the plant at the top of the page.
  • The Current production block on the home page shows per line what is running now, today’s plan and the next changeover. It is read-only; clicking the line name takes you to the Production plan page.
  • The Production plan block in the diary shows today’s and the next days’ plan of the lines with the running product. It appears only on plants that have a production line.

The Overview tab has one box per production line, every box in the same order:

  • the line name and its state: “Running” or “Stopped” (with an icon and a label, not only a colour);
  • the running product and grade, and since when;
  • Today’s plan: the day’s plan rows, the one valid now highlighted;
  • Next changeover: the first product change in the next 7 days;
  • the plan’s suggestion, e.g. “The changeover opens prefilled from the plan: Product A”;
  • the buttons, if your permissions allow.
  • Changeover (or Start, when nothing runs on the line): the dialog opens with the plan’s suggestion (“Product and grade are the plan’s suggestion; you can change them.”). The changeover closes the running product and starts the chosen product at the same instant.
  • Stop: the dialog asks in the New state field which state the line goes into. Its default can be set in the operating-mode element settings.
  • Time: site local time. With per-line recording it can go back at most to the start of the current shift, not into the future.

Changeover and Stop write the same line state that the diary’s Operating-mode timeline element shows. So the plant needs a shift log for the current shift.

In the box’s ⋮ menu:

  • Correct start: corrects the start time of the running product. With the changeover permission you can correct your own latest record; with the settings permission, any record.
  • Void (settings permission only): the run becomes void, its time is freed, the record stays with the reason. “Nothing is deleted.”

You can also correct a stretch of the line on the diary’s Operating-mode timeline (Correct), together with the stretch’s quantity.

On the Plan tab the grid has the production lines as rows and the days of the week as columns; you can page through the weeks. Click a plan row to edit it; “+” adds a new row for that day.

  • Repeat on the following days: copies the row ahead for 1–62 days. Days where a row with that number already exists (or where the day’s order does not allow it) are skipped and listed.
  • Change log: every change to the week’s plan (who, when, what and why). Read-only; a removed plan row can be brought back here with Restore.
  • Start-up before this row: the flag on a plan row. The start-up checklist opens before the planned start. Details below, in the Production-line start-up section.

Plan versus actual: where the produced quantity comes from

Section titled “Plan versus actual: where the produced quantity comes from”

The plan is the Quantity / day value. The actual is the quantity of the line’s stretches (periods) on the diary’s Operating-mode timeline. The system compares the two per line and per product: the Analytics Plan – quantity and Actual – quantity metrics are calculated from this.

An actual only exists if:

  • the plant records in “Record per production line” mode in the diary’s operating-mode element, and
  • “Record a quantity per stretch” is on: then, when a stretch closes, the diary asks for the “Quantity of the closing stretch”.

Example (neutral numbers). Line 1’s plan row for Wednesday: all day “Product A”, 80 t / day, target tank “Tank 1”. The diary’s Operating-mode timeline shows:

Stretch State Quantity
06:00–11:00 “Product A” 30 t
11:00–12:00 stopped, no product —
12:00–22:00 “Product A” 45 t

The actual is 75 t, the plan 80 t, about 94% fulfilled. The stopped stretch has no product and does not count towards the quantity.

When it counts, and when not.

  • An open stretch does not count. If you look at 18:00, the stretch that started at 12:00 is still running: the actual is then 30 t, not 30 + 0. The gap shows as no record, not as zero.
  • A stretch without a quantity does not count either. If the quantity was left empty, add it later with the diary’s Correct button.
  • The Production plan’s Changeover button does not ask for a quantity. If you record the changeover there, enter the closed stretch’s quantity in the diary.
  • It does not mix with Campaign progress. A plant is either a campaign plant or records per production line, so the two sources of the actual never run on the same plant at the same time.

On a production line, the start-up is part of the Production plan: the Campaign start-up add-in is not needed for it. The mechanism is the same as the campaign’s (start-up checklist, gates, signatures), and its permissions are listed on the Permissions page among the Campaign start-up permissions.

Plan-row flagStart-up before this rowManualOpen start-upPlannedlead time: 24 h by defaultIn progresschecklist + two gates signedDone“Start production”Production gate while the start-up is in progressOff: production may go · Warn: only with a reasonBlock: production starts only after the start-up is done
  • The start-up band on the Overview appears only if the plant records in “Record per production line” mode.
  • On a campaign-controlled plant, per-line recording cannot be switched on; there the Campaign runs the start-up.
  • A production line can have one open start-up at a time.

On the Settings tab, the Start-up base checklist card keeps one checklist per plant: “On this plant every new start-up opens with a copy of this checklist.” If there is none yet, the card says “This plant has no start-up base checklist yet: new start-ups open with an empty checklist.”, and you create it with Create base checklist.

  • The checklist editor is the same as the campaign’s: sections, items, required and optional items.
  • Training items are not available for a production-line start-up yet.
  • The campaign base checklist is a separate list and belongs to the Campaign start-up add-in.

In the same place, on the Production-line start-up card, you set the production gate and the lead time (below).

A start-up opens in two ways:

  • From the plan. In the plan-row editor you tick “Start-up before this row”. The grid shows the same label next to the row. This creates a planned start-up, which opens by itself before the planned start, by the lead time in hours (24 by default). The planned start is the row’s day and its “From this time” time (for the day’s first row, the start of the day).
    • If you move the row or change its product, the planned start-up moves with it.
    • If you remove the flag or remove the row, a start-up that has not opened yet is cancelled. An open one stays: “An open start-up remains on the line: finish or cancel it on the start-up page.”
    • A row’s start-up happens once: after a done or manually cancelled start-up, editing the row does not open a new one.
  • Manually. On the Overview box, Open start-up gives an open start-up straight away, without a plan (for a restart after a breakdown or maintenance). The product is then the plan’s suggestion.

With an open start-up, the Overview band shows “Start-up in progress: 14/20”, with the next step below (the start-up checklist items, the “Ready to start” gate, then the “Start approved” gate). The Start-up checklist link takes you to the start-up page:

  • Header: product, planned start (“From the plan” or “Unplanned start-up”), the required items done, later “Production started”.
  • The start-up checklist: the shift completes the items the same way as on a campaign start-up checklist (tick, check, measurement, N/A with a reason).
  • This start-up’s checklist: with Edit checklist you can tailor the checklist to this one start-up. “Changes apply to this start-up only; the plant base checklist stays as it is.” If a gate is already signed, the change needs a reason, and the signed gates become invalid (“Gate invalidated”). The checklist of a finished or cancelled start-up is read-only.
  • Gates: “Ready to start”, then “Start approved”, both with the Sign button. You can sign only with a finished checklist, and the second gate must be signed by someone other than the first. Both gates are on by default; turning them on or off comes from the Campaign settings policy. “Without gates, a finished checklist completes the start-up.”
  • Timeline: every step with time, actor and reason. Below it: “The chain is intact”. If it says “The chain is broken — tell your administrator”, the order of the entries has been damaged.
  • Cancel start-up: on a planned or in-progress start-up, with a reason (at least 5 characters).

When the start-up is done, the Overview band says “The start-up is done” and “Starts Product A from the plan.” The Start production button records the line’s new state in one click; this is the same as a Changeover. The product is the start-up’s (from the plan row or the manual opening), otherwise the plan’s suggestion. Without a product: “No product is linked to this start-up: start production with Changeover.”

The start of the first producing stretch is written back to the start-up (“Production started”), and the button disappears from the band.

On the Settings tab, on the Production-line start-up card, “Production before the start-up is done” decides what happens when a start-up is open on the line and someone records the line with a product (Changeover, Start, or the diary’s Operating-mode timeline):

Setting What happens
Off (default) Nothing: production may go.
Warn, ask for a reason Recording asks for a reason: “A start-up is open on this line: give a reason for starting production before it is done.” The reason goes on the timeline, and the start-up shows “Production started before the start-up was done, with a reason”. It asks for a reason only once per start-up.
Block “A start-up is open on this line: production starts only after it is done.” The band has no Start production button.
  • Open before the planned start (hours): the lead time, between 0 and 720 hours, 24 by default.
  • Relaxing the gate (Block → Warn → Off) needs a reason. A plant cannot be looser than its site: “A plant cannot relax the site setting.”
  • When turning it on, the page recommends Warn: “blocking tends to make operators skip recording.”
  • Diary. With an open start-up, the diary’s Line start-up element (switchable in the diary settings) shows the start-up checklist: done / total, the next item, and the Open the start-up link. You can record an open item and a new measurement on a red item from the diary too (photo, comment, dictation). N/A, undo and signing the gates are on the start-up’s page. A closed diary and the shift PDF show the state at closing.
  • My to-dos. In the home page’s My to-dos block, the Line start-up items assigned to me group lists the items you are the named owner of and that are waiting for you now. The item takes you to the start-up page.

Defaults (changeable on the Permissions page):

Permission What it allows Default
Production plan: view the plan, the Overview, the diary and home page blocks Site manager, Production manager, Shift leader, board and outside operator
Production plan: planning writing and flagging plan rows, new product Production manager
Production plan: changeover Changeover, Stop, Start production, correcting your own latest record Shift leader
Production plan: settings production lines, correcting and voiding any run Production manager
Start-up: open on a production line manual opening and cancelling Production manager, Shift leader
Campaign: view the start-up page, the diary block Site manager, Production manager, Shift leader, board and outside operator
Campaign: complete checklist completing items (if the item’s responsible role is theirs too) Site manager, Shift leader, board and outside operator
Campaign: edit checklist a start-up’s own checklist Production manager
Campaign: settings the base checklist, the production gate and the lead time Production manager
Campaign: “Ready to start” gate the first gate Shift leader
Campaign: start approval the second gate Production manager
What you see Why What to do
“The plant has no shift log for the current shift. Open the shift diary first: the line state is recorded in the log.” The Changeover writes to the diary’s Operating-mode timeline. Open the plant’s diary, then record again.
“Per-line recording is not switched on for this plant. …” The plant does not record per production line. Turn on “Record per production line” in the diary’s operating mode element settings.
“Campaign-controlled plant: the line state is written by the campaign and cannot be recorded by hand.” The plant is a campaign plant. There the campaign phase writes the operating mode; the Production plan is for plants with production lines.
“You can only correct your own latest record.” With the changeover permission, Correct start works only on your own latest record. Ask a colleague with the settings permission.
“There is already an open start-up on this line.” A line can have one open start-up at a time. Finish or cancel the existing one on the start-up page.
“The “Ready to start” gate must be signed first.” The second gate comes only after the first. The shift leader signs the first gate.
“The second gate must be signed by someone other than the first.” Two people sign the two gates. Someone else signs the approval.
“The checklist is not done: every required item must pass or be N/A.” A gate can be signed only on a finished checklist. Complete the missing items, or mark them N/A with a reason.

Last updated: