Product & Order

Wire the Current Product, the Order, and the Ordered Products count — the inputs Performance needs.

The Product & Order group of Tag Mapping drives Performance. It tells the OEE engine which product the equipment is currently running, which order it is fulfilling, and how many units that order calls for.

Field	Required	Drives
Product Id	Yes (when Performance is enabled)	The currently running product — used to look up Ideal Cycle Time from the assigned Equipment Products list.
Order Id / Order Start	No	The currently active production order. Display + reporting use; not used by the score calculation directly.
Order End	No, only shown in Event Pair mode	Closes the order interval started by Order Start.
Ordered Products	Yes (when Performance is enabled)	The total number of units this order calls for — drives the "produced vs. ordered" progress and the planning-vs-actual comparison.

---

Product Id

The Product Id tag should emit the product’s Material Number — the same value you use as the Material Number column on the Site’s Products tab. The engine matches the live tag value to a product in the assigned product list and uses that product’s Ideal Cycle Time as the speed reference for Performance.

If the live value doesn’t match any product in the list, Performance uses the equipment’s Default Ideal Cycle Time configured on the Equipment Products tab — Performance is never skipped, the Default is always available.

Product Id is one of the most common candidates for the JSONata Value Parser — many MQTT or OPC payloads carry the active product as one field of a larger object. Open the Single Tag tab, select the parent tag, choose Jsonata, and write an expression like payload.activeProduct.materialNumber.

---

Order tag configuration

The Order tag configuration dropdown chooses how order intervals are reported, mirroring the Error Code modes:

Mode	What the tag emits	Required tag(s)
Single Event (point-in-time)	One event per order change — the new Order Id. The current order is whatever was emitted most recently.	Order Id
Single Event (start & end)	One event carrying the order start and end timestamps in the same payload (typically extracted with JSONata).	Order Id (interval)
Event Pair (start & end)	Two tags — one emits when an order opens, another when it closes.	Order Start + Order End

In Event Pair mode the field labels switch from Order Id to Order Start and an extra Order End field is shown.

---

Ordered Products

Field	Required	Notes
Ordered Products	Yes (when Performance is enabled)	Numeric count of units the order calls for. Emitted with the same timestamp as the order-completion event (see below); can also be sourced via Calculations if the count is computed from other tags.

The engine compares Produced (derived from the Quality counts under Data Quality) against Ordered Products to surface order progress. Performance itself is Produced × Ideal Cycle Time ÷ Run Time — the ordered count doesn’t change the score directly, but it makes the dashboards meaningful.

---

Aligning counts with order completion

Four tags drive the per-order Performance and Quality calculations: Ordered Products (this page) and Products total, Products approved, Products rejected (under Data Quality). The engine pairs each count emission with an order interval by exact timestamp match against the order-completion event, so two rules apply whenever any of these four tags are wired:

1. The Order tag configuration must emit an order-completion event — either Order End in Event Pair mode, or the end-timestamp expression on Order Id in Single Event (start & end) mode. Single Event (point-in-time) doesn’t emit a completion event and is not compatible with these count tags being configured.

2. Each emission of a count tag must carry a timestamp identical to the order-completion event’s timestamp. Counts whose timestamps don’t match an order-completion timestamp aren’t associated with an order interval.

The second rule is satisfied upstream — the PLC, MQTT bridge, or pipeline emits the four counts together with the order-completion event, all stamped with the same instant.

Configuring any of the four count tags without an order-completion event blocks Save. If you don’t track order intervals on this equipment, leave Performance and Quality disabled on the Equipment tab — the count tags then aren’t required.

---

Validation

Condition	Behavior
Performance pillar enabled and Product Id unset	Field flagged required; Product & Order group shows invalid; Save blocked.
Performance pillar enabled and Ordered Products unset	Same.
Order tag configuration is Event Pair but Order End is unset	The field is required to save in Event Pair mode (matching how Error Code Closed behaves).
Any count tag (Ordered Products, Products total/approved/rejected) configured but Order tag configuration is Single Event (point-in-time)	An order-completion event is required to align counts with orders. Switch to Single Event (start & end) or Event Pair. Save blocked.
Source tag missing from the asset hierarchy	Trigger row shows the saved path with no live value; reopen the dialog and pick a current tag.

---

Related

• Site Products — the product list your Product Id values match against.

• Equipment Products — selects which Site Product List this equipment uses, plus the default Ideal Cycle Time.

• Data Quality — the counts that combine with Order data to drive both Performance and Quality.