Triggers

Triggers (data triggers) monitor a device’s machine data and react automatically once a defined condition is met — such as a threshold being exceeded or an unusual trend. In response, they create a case or a work order.

You find triggers in the Device Data area under the Data Trigger tab.

Scope

Triggers can be defined at two levels:

• Per device — applies to a single device
• Per device model — applies to all devices of a model

Condition (expression)

A trigger condition is built from a data source and a metric of the device data:

Part	Description
Data Source	Which device data to evaluate — Scalar Values (numeric readings), Errors, or Orders (missions)
Metric	Which data value is evaluated (Scalar Values only, via the device’s chart selection)
Operator	Comparison, e.g. greater than, less than
Threshold	The comparison value (fixed or relative)
Time window	The period over which the condition is evaluated
Evaluation rate	How often the condition is checked (e.g. every 5 minutes)

For Errors and Orders, the trigger always counts how many events occurred in the time window — there’s no metric or transform to choose. Scalar Values support the full range of aggregations (average, max, sum, …) and can also evaluate the derivative (rate of change) instead of the raw value, optionally with a transform applied.

Presets

Instead of building the condition from scratch, you can choose from predefined presets that capture common patterns:

• Peak — short-term spikes
• Trend — sustained movement in one direction
• Usage-Based — usage-based thresholds
• Deviation — deviation from usual behavior
• Threshold Zone — leaving an allowed range
• Dynamic — dynamic, data-dependent threshold
• Custom — fully custom configuration

Action on trigger

When the condition is met, the trigger performs one of the following actions:

Action	Result
Create case	Creates a case, optionally from a case template
Work order	Creates a work order, optionally with a work template

In addition, a responsible user can be set, who is assigned to the created case or work order.

Note

Triggers require connected devices that send data. Without a data integration there are no metrics to evaluate. See Data Sources.

Usage-based and anomaly-based maintenance

Triggers are how you automate usage-based and anomaly-based maintenance:

• Usage-based — Use the Step Threshold source (or the Usage-Based preset) to fire every time a count or reading crosses a multiple of a threshold. On the Orders data source this counts missions, e.g. every 1,000 missions. On Scalar Values it can track any cumulative counter, e.g. every 1,000 rotations of a robot arm.
• Anomaly-based — Use the Errors data source to fire when the error count in the time window spikes, or use Scalar Values with a preset such as Peak, Trend, Deviation, Threshold Zone, or Dynamic to fire on abnormal sensor readings.

Set the trigger’s action to Work order to have WAKU Care generate maintenance automatically, the same way a Strategy would.

Related

• Strategies — scheduled work order creation
• Machine Data
• Insights