Parameter Health issues¶
Notifications → Parameter Health is the live queue: every parameter currently outside its healthy range, worst first, with somewhere to record what you did about it.
This is distinct from the Excursions register in Digital Twin, which is the historical record. This page is the work queue; that one is the audit trail.
What you see¶
| Card | Meaning |
|---|---|
| Needs acknowledgement | Open issues nobody has taken responsibility for yet |
| CCPs deviating | Critical control points currently out of specification |
| Open issues | Everything currently open |
Issues are ordered worst first: unacknowledged before acknowledged, then by how critical the parameter is, then by severity, then oldest first — so the thing that has been wrong longest rises to the top of its tier.
Each entry shows the parameter, the machine it belongs to (if any), the reading and the range it should have been in, how long ago it started, and whether it is escalating.
Some issues aren't about a machine
A monitored parameter doesn't have to belong to a machine — a cold store, a compressed-air header or a standalone sensor can all be monitored. Those appear here without a machine name.
You may also see a single entry for an edge device that stopped reporting. When that happens none of its parameters are being recorded, so Enture raises one issue for the device rather than one per parameter.
Acknowledging an issue¶
Acknowledging is how a deviation gets explained. Enture deliberately doesn't try to work out by itself whether a reading mattered — a cold store warming up during a planned defrost and one warming up because the door was left open look identical to a sensor. Only a person can tell them apart, so acknowledging asks you to say which it was.
- Click Acknowledge on the issue.
- Choose a reason — Planned Maintenance, Cleaning / CIP, Changeover, Sensor Fault, Genuine Deviation, or Other.
- Optionally add remarks. Anything worth knowing during a later investigation belongs here.
- Confirm.
A reason is required. That's what makes "show me only the genuine deviations from last quarter" a filter rather than an afternoon of reading notes.
Acknowledging stops the escalation — it does not close the issue
Acknowledging records that a person has taken responsibility and stops the reminders. The issue stays open until the parameter actually returns to its healthy range, at which point Enture closes it automatically.
If a parameter is still out of range after you acknowledge it, that's correct and expected.
If you can't acknowledge something¶
Where an issue is governed by an escalation matrix, only members of the groups on that matrix can acknowledge it. Those issues show Not yours to acknowledge instead of a button — someone in the responsible group needs to handle it.
Seeing what's already been dealt with¶
Show acknowledged includes issues someone has already explained but which are still open — useful for checking whether a known problem is being worked on before raising it again.
If nobody acknowledges¶
Issues with an escalation matrix escalate on a timer. Each level notifies a wider group until somebody acknowledges. The entry shows which level it has reached, so you can see whether anyone has been told yet.
See Escalation Matrix for configuring the levels.
Where these issues also appear¶
| Where | What it gives you |
|---|---|
| Notifications → Parameter Health | The live queue, with acknowledgement — this page |
| Notifications → Machine Issues | Alongside trigger, VFD, CNC and maintenance issues, for a single fleet-wide picture |
| Digital Twin → Parameters → Health → Excursions | The full history, filterable by cause, with CSV export |
| A machine's own detail page | That machine's open issues, in its Active Alarms card |