Skip to content

Production Tracking Overview ​

Last updated

The Production pages record how a machine is performing: how long it was planned to run, how long it was down and why, how many parts it made, how many were bad, and who worked on it. They live under Monitor in the sidebar (Andon and SPC under Visualize).

PageSidebarWhat it is forLicensed feature
OEE TrackingMonitor > OEEAvailability, Performance, Quality and OEE per deviceOEE Tracking (oee)
Downtime TrackingMonitor > DowntimeReason codes, downtime events, ParetoDowntime Tracking (downtime_tracking)
Quality TrackingMonitor > QualityReject, scrap and rework eventsQuality Tracking (quality_tracking)
Shift SchedulingMonitor > ShiftsShift times, breaks, takt targets, calendarShift Scheduling (shift_scheduling), licensed on every appliance
Andon DisplaysVisualize > AndonShop-floor scoreboard on a TVAndon Display (andon)
Labor EfficiencyMonitor > Labor EfficiencyOperator clock-in/out against labor standardsLabor Efficiency (labor_efficiency)
Statistical Process ControlVisualize > SPCControl charts and Cp/Cpkpage access; rules need Enhanced SPC (spc_enhanced), licensed on every appliance

Turning the pages on ​

Every production feature ships switched off, even when your license includes it.

  1. Sign in as an admin.
  2. Go to System > Settings and open Feature Toggles.
  3. Under Production, switch on the features you need. Only licensed features can be enabled.
  4. Refresh the browser. The pages appear in the sidebar.

A feature is usable only when it is licensed, switched on, and not restricted for the user (per-user feature restrictions hide the sidebar item and the API refuses the calls). See System Settings and Users.

How data gets in — read this first ​

The production pages are record-keeping tools. Very little is collected automatically from the PLC.

DataHow it is captured today
Part counts for OEEAutomatic when Good Count Tag / Reject Count Tag are bound on the OEE configuration — the engine watches those tags and accumulates counts itself. Otherwise, posted to POST /api/oee/snapshot by something you build (custom page, external system).
Downtime eventsOpened and closed automatically from the OEE form's Run Status Tag when one is set; otherwise started and ended by a person with Log Downtime / End, or by the API.
Quality eventsLogged by a person with Log Quality Event, or the API. On a device without a Reject Count tag they are also its OEE rejects.
Work order countsThe +1 / +5 / +10 buttons on the Work Orders page, or the API.
Labor timeClock In / Clock Out buttons.
SPC samplesAutomatic: each new non-zero value on the trigger tag stores the measurement tag's value.
Shift in effectAutomatic, from the shift table, the production calendar and the appliance clock.

For counters the tag binding can't handle (not monotonic, needs extra logic), or for downtime automation from a run-status signal, see Feeding OEE counts and downtime for the custom-page pattern.

Roles ​

The pages show their buttons to everyone; the API enforces the role and returns 403 Insufficient permissions when the user's role is too low. Roles are ranked admin > editor > operator > viewer.

ActionMinimum role
View any production page or historyviewer
Start/end downtime, log quality events, post OEE snapshots, clock in/outoperator
Shifts, calendar entries, OEE configuration, reason codes, Andon displays, labor standardseditor
Delete downtime or quality eventseditor
Delete labor entries or labor standardsadmin

Time zones ​

Everything on these pages follows the appliance's local time zone: which shift is running, where "today" starts for OEE, downtime and Andon totals, and the From and To days on Labor Efficiency. Set the time zone on the appliance (see System Settings); the change takes effect straight away, without a restart. Times are still stored as UTC and shown in your browser's local time.

See also ​

Scada.Ink Help Center