Setting up Parameter Health¶
Health monitoring is configured per parameter, and is off until you turn it on.
Open Digital Twin → Parameters, click the parameter you want to monitor, and choose the Parameter health tab.
Engineering access required
Changing a health configuration needs engineering access. Anyone with parameter access can view the results.
Step 1 — how is this parameter graded?¶
Enture preselects this based on what the parameter has actually been reporting, and tells you what it found. You can override it.
Numeric range — the parameter reports a measurement, and you define the range it should stay within.
Value rules — the parameter reports text or a status code, and you list what each value means.
Step 2a — defining a numeric range¶
You set up to four limits. All are optional, so a one-sided specification ("must not exceed 8 °C") works without inventing a lower bound.
Critical low Lower spec Upper spec Critical high
───────┼─────────────────┼─────────────────┼─────────────────┼───────
Critical │ Unhealthy │ Healthy │ Unhealthy │ Critical
| Field | Meaning |
|---|---|
| Lower / Upper spec limit | The specification. Outside these, the parameter is Unhealthy |
| Critical low / high | Beyond these, the deviation is severe |
| Target | The nominal value. Used for capability reporting and chart annotation |
The spec limits are what capability reporting uses
The lower and upper spec limits are the ones Cp and Cpk are calculated against. Critical limits mark a severe deviation — they are not a statistical control limit, and they don't affect capability figures.
Bands also appear on the chart
Once saved, these limits are drawn directly on the parameter's Live Data chart at the top of the
page — shaded zones mark unhealthy/critical territory on either side, and a dashed line marks the
target. This is numeric-range parameters only; a value-rules parameter has no chart overlay, since
there's no line chart of FAULT.
Step 2b — defining value rules¶
Each rule maps a reported value to a state, for example:
| Condition | Value | State |
|---|---|---|
| Equals | RUNNING |
Healthy |
| Equals | WARNING |
Unhealthy |
| Equals | FAULT |
Critical |
| Bit high | 3 |
Critical |
Use the discovered values list. Below the rules, Enture shows every value this parameter has actually reported in the last 30 days, with how often. Click one to turn it into a rule. This matters more than it sounds — nobody remembers that a particular drive reports S_OFF3, and a rule set that misses a fault value will never flag that fault.
Values that have been reported but aren't covered by any rule are highlighted.
Rule order doesn't matter
Every rule is checked, and the most severe match wins. You can't accidentally hide a critical rule by listing a milder one above it.
Capitalisation and spaces¶
By default, capitalisation is ignored — RUNNING, Running and running are treated as the same value. Extra spaces are always ignored, because many devices pad text to a fixed width.
Switch to Match capitalisation exactly only if upper and lower case genuinely mean different things on your device.
Changing to exact matching clears your text rules
Values are stored without their original capitalisation, so switching to exact matching means re-entering the text rules for that parameter. Enture tells you when this happens.
When no rule matches¶
A value you haven't accounted for has to mean something. By default:
- On a Critical Control Point, it counts as Unhealthy — an unrecognised state on a CCP is treated as a deviation until someone confirms otherwise.
- On any other parameter, it counts as Unknown — visible on the timeline, but not raised as an issue.
You can override this per parameter.
Save a critical control point with care
If you mark a parameter as a Critical Control Point and some of its recently reported values aren't covered by a rule, Enture warns you before saving. Those values will be treated as deviations and will raise alerts. Add rules for them first unless you genuinely intend that.
Step 3 — settling behaviour¶
Real readings sit right on limits and wobble across them. Two settings stop that generating a stream of issues.
| Setting | What it does |
|---|---|
| Hold for (seconds) | A state only changes once the condition has held this long. Default 60 seconds |
| Hold for, when critical | Optional. Lets a severe deviation be acted on faster than a mild one |
| Recovery margin | How far back inside the range a reading must come before it counts as recovered |
The recovery margin applies only to numeric ranges, and only to recovering. A parameter getting worse is never delayed.
Start with the defaults
60 seconds hold and no recovery margin is a sensible starting point. If you see a parameter flipping in and out repeatedly, increase the hold time first, then add a small recovery margin.
Step 4 — who gets told¶
| Setting | Effect |
|---|---|
| Escalation matrix | Leave as None and issues are recorded and visible, but nobody is notified. Choose a matrix and unacknowledged issues escalate through it |
| Report when this parameter stops reporting | Leave on unless the parameter legitimately reports only occasionally |
Start without an escalation matrix
When setting up a parameter for the first time, leave the escalation matrix as None until you've watched it for a day or two and are happy the limits are right. You'll still see everything in Enture — you just won't send anyone an email about a limit that turns out to need adjusting.
See Escalation Matrix for how escalation levels work.
Turning it off¶
The Disable health monitoring button at the bottom of the tab stops monitoring and removes the configuration. Historical records of past deviations are kept.