Skip to content

Parameter Health

Parameter Health watches a parameter against the range — or the set of values — it is supposed to be in, and keeps a permanent record of every time it wasn't.

Where a trigger tells you the moment something crosses a line, Parameter Health answers the questions that come afterwards:

  • Was this tank inside its temperature range all of last month, and what percentage of the time?
  • How many times did the filler leave spec, for how long, and why each time?
  • Is this critical control point capable of holding its specification, or is it only just scraping through?
  • Which parameters are deviating right now, and has anyone taken responsibility for them?

Navigate to Digital Twin → Parameters → Health.

When to use Parameter Health instead of a trigger

Both can watch the same parameter, and they can be used together. They answer different questions.

Use a trigger when Use Parameter Health when
You want something to happen — write a value, fire an action You want a state recorded and auditable
The condition is a one-off threshold The condition is "inside or outside a normal operating range"
It's an equipment-protection alert It's a process or quality parameter — especially a critical control point

They can overlap

If a parameter has both a health configuration and threshold triggers, you may receive two notifications for the same physical event. That's expected — they're separate features. Turn off whichever you don't need.

What it can watch

Parameters that report a number — a temperature, a pressure, a flow rate. You give it a healthy range, and optionally an outer range that counts as a severe deviation.

Parameters that report text or a status code — RUNNING, FAULT, E-STOP, or a numeric state code. You list which values are healthy and which aren't.

Text parameters could not be monitored before

Parameters that report text rather than numbers cannot be watched by triggers at all. Parameter Health is the only way to monitor them.

The five states

At any moment, a monitored parameter is in exactly one state.

State Meaning
Healthy Inside its healthy range, or reporting a value you've marked healthy
Unhealthy Outside the healthy range — out of specification
Critical Beyond the outer limits — severely out of specification
Offline Its edge device has stopped reporting, so nothing is being measured
Unknown Not yet graded, or reporting a value no rule covers

Unknown is not the same as healthy. A parameter that has never reported, or that is reporting a value you haven't accounted for, shows as Unknown rather than being quietly assumed fine.

How important is this parameter?

Separately from how bad a reading is, you tell Enture how much the parameter matters:

Criticality Typical use
Critical Control Point A parameter that quality or safety depends on. Always raises a high-severity issue
Major An important process parameter
Minor Monitored and recorded, but doesn't raise alerts by default

Keeping these separate is what lets a minor parameter drift badly without paging anyone, while a critical control point raises a serious issue on even a mild deviation.

Where to go next