Diary at startup: the campaign plant's diary

On a campaign plant the diary follows the campaign: a phase indicator is always shown under the header, during the startup phase (Startup, Ramp-up) only the elements marked visible appear, and the operating mode is written by the campaign. Which elements are visible at startup is set on the Diary at startup tab of the campaign drawer.

Before you start

• The Campaign add-in is switched on and the plant is a campaign plant (Campaign settings page → Campaign plants).
• Permission: to change the setting campaign:configure; viewing needs campaign:view.

Steps

1. Open the campaign. On the Campaigns page click the campaign, then the Diary at startup tab in the drawer.
2. Tick the visible elements. The plant’s diary elements are listed; ticked = Visible, empty = Hidden. Without an own setting the plant’s previous campaign setting applies (if there is none, everything is visible).
3. Save. After Save view the setting takes effect in the diary during the startup phase. Hiding events or the handover shows a warning (not a block): about half of incidents happen during startup or shutdown.

What the shift leader sees in the diary

• Phase indicator under the diary header, e.g. “Startup · Acid chloride · KMP-2026-0014 · list 18/24”; in Production the planned end, between campaigns “Idle · next campaign: …”. Clicking opens the campaign drawer (without the right it is text).
• Hidden elements during startup: not shown and not editable, their data is kept; a line at the top of the diary says how many elements are hidden. When the campaign enters Production the normal diary view returns.
• The operating-mode element is replaced by the timeline written by the campaign, read-only (“the campaign controls the operating mode”).
• Unqualified employee marker in the attendance block — only if the Shift scheduler module is also on: an employee selected on the campaign’s training items who has not passed yet is marked “not qualified (campaign training)”.

Closing the diary

Closing checks the visible elements on the server: a hidden required field, description (handover), attendance post or out-of-range value does not count, a visible one does. If the attendance element is hidden, closing does not ask for attendance confirmation (and the closing record does not claim one). At closing the diary gets a snapshot of the view, in the same step as the closing:

• The archived diary uses it — it shows the view that was visible then.
• The shift PDF is the full record: the stored data of hidden elements is included too. Only the header’s phase line comes from the snapshot (e.g. “Campaign phase: Startup · Acid chloride …”) — the phase at closing, not the current one.

Common problems

What you see	Why	What to do
The ticks are greyed out	You lack campaign:configure, or the campaign is closed / withdrawn.	Ask the production manager.
The hidden element still shows in the diary	The campaign is already in Production (hiding only applies at startup).	This is expected.
Closing: “required field missing” on an element hidden at startup	The campaign moved to Production meanwhile; the element is visible again.	Fill in the field.