Data Tag Templates

Overview

The Data Tag Template in TilliT provides a no-code solution for interpreting raw values and executing predefined behaviors. These templates help ingest live data, such as order counts, equipment availability, or work order status, impacting key asset metrics like performance, availability, and quality, as well as order completion progress.

Templates are defined on the Edge Data Tag of a Datasource, and each asset or equipment can have only one instance of each template.

Equipment Status Templates (EQUIPMENT_STATUS_*)

These templates expect a digital input where 1 (true) indicates that a specific status is active. Availability metrics are calculated based on these statuses.

Important: Selecting this template does not automatically configure events (e.g., Equipment Stopped, Equipment Running). To trigger events, you must create an edge trigger on the tag.

---

Production Count Templates (COUNT_TOTAL & COUNT_REJECT)

COUNT_TOTAL

• Represents the total number of produced units.

• Every minute, TilliT reads the value, compares it with the previous value, and publishes the difference to the cloud.

• The Order Progress table displays how many units were produced between polling cycles.

COUNT_REJECT

• Tracks the number of rejected units.

• Like COUNT_TOTAL, TilliT reads and calculates the difference every minute.

• This count helps determine the quality metric of Overall Equipment Effectiveness (OEE).

Order Management Templates (ORDER_NUMBER & ORDER_STATUS)

ORDER_NUMBER

• Automatically completes a running order and starts a new one.

• Maps TilliT to a source tag containing the current order number.

• When the order number changes, TilliT closes the previous order and starts the new one.

ORDER_STATUS (after getting ORDER_NUMBER working)

• Works with ORDER_NUMBER to transition an order between the following states:

  • READY

  • NEW

  • RUNNING

  • SUSPENDED

  • COMPLETED

Downtime Classification Template (DOWNTIME_REASON)

• Automates downtime reason classification.

• When selected, an Event Reason Option Group field appears, allowing you to match raw values to human-readable reasons.

• The downtime reason is linked to the Equipment Stopped event and pre-fills activities for operator confirmation.

Example:

1. An Equipment Stopped event is triggered at the edge.

2. The DOWNTIME_REASON tag is populated with a value (e.g., 3001).

3. The recorded reason code is classified (e.g., Operational → Operation → Downstream Machine Issue → 3001).

4. An Enter Stoppage Reason activity is created for operator confirmation.

5. If re-qualified, the event is updated with the correct reason.