UNIHH-IOTUNIHH-IOT
Home
Guide
Manual
  • 简体中文
  • English
GitHub
Home
Guide
Manual
  • 简体中文
  • English
GitHub
  • Manual

    • Operation Manual
    • Dashboard
    • Driver Management
    • Device Management
    • Thing Models
    • Data Monitor
    • Rule Engine
    • Alarm Center
    • Log Audit
    • System Management

Rule Engine

The rule engine evaluates point data in real time and fires linked actions — a device write-back or a log entry — when conditions are met. It is what makes unattended operation possible.

Rules

Finding Rules

FilterDescription
KeywordFuzzy match on rule ID, name, monitored point or linked command
DeviceFilter by bound device
StateEnabled / disabled

Creating a Rule

Basics

FieldDescription
Rule IDUnique (e.g. RULE_101)
Rule nameSpell out the scenario, e.g. "fan 1 bearing over-temperature: auto fan + slow-down"
Monitored deviceThe device under watch
Point / eventA property point or thing-model event of that device

Condition

FieldDescription
Condition typeOne of single-point threshold, in-range, out-of-range
OperatorFor thresholds: >, >=, <, <=, ==, !=
ThresholdTarget value for single-point conditions
Min / MaxBounds for range conditions, e.g. 20.0 <= point <= 80.0

Trigger mode

Controls when the condition is evaluated, complementing the point's sampling mode: PERIODIC points are evaluated each acquisition cycle; COV points are evaluated when the value changes.

Linked Actions

Each rule carries multiple actions, each with its own on/off switch:

FieldDescription
Action typeSERVICE (write-back) / LOG (record)
Action nameHuman label (e.g. "auto-start cooling fan")
Config / command payloadFor SERVICE: target point/service and value; for LOG: the message template

A typical pairing for over-temperature: a SERVICE action to start the cooling fan plus a LOG action. Even rules without a write-back feed the Alarm Center with events.

Enabling and Testing

  • Create rules disabled first; enable them once the point data is verified;
  • Before enabling a SERVICE rule, confirm point quality on Data Monitor to avoid false triggers;
  • Command executions triggered by rules show up in Log Audit.

Worked Examples

Bearing over-temperature slow-down

SettingValue
PointBearingTemp bearing temperature (RW)
ConditionThreshold: > 80.0 °C
Action 1SERVICE: start cooling fan
Action 2SERVICE: set frequency to 30 Hz
Action 3LOG: "bearing temperature above 80 °C"

Pressure envelope

SettingValue
PointTankPress tank pressure
ConditionOut-of-range: < 0.2 or > 0.8 MPa
ActionLOG: record the violation with the live value snapshot
Edit this page on GitHub
Last Updated: 11/13/26, 3:34 AM
Contributors: sunqi
Prev
Data Monitor
Next
Alarm Center