Visibility should lead to action.
A measurement needs an identity, a timestamp and an agreed meaning. Monitoring design starts with the decisions people need to make, then works back to the signals, thresholds and escalation paths that support them.
Scope the right work.
- Machine state and condition monitoring
- Environmental measurements and trends
- Alert thresholds and escalation requirements
- Remote access and operational visibility
Technical scope
A signal, an owner, a response.
Specify how measurements become operational information, and how people should respond when conditions change.
| Area | Define together | Example evidence |
|---|---|---|
| Data quality | Define units, sample timing and how stale or unavailable values are identified. | A signal register and demonstrations of missing-data conditions. |
| Alert lifecycle | Define thresholds, delays, escalation and what acknowledgement means. | A walkthrough from condition detection through response and return to normal. |
| Access | Identify who needs to view, acknowledge or change each part of the system. | An access matrix reviewed with operations and site IT. |
Useful review artefacts
- Signal and threshold register
- Alert ownership and response matrix
- Trend, retention and access requirements
A planning framework, not a confirmed feature or compatibility list. Deliverables and acceptance criteria are agreed for the application.
Questions worth answering early.
- Who owns the response to each type of alert?
- How should missing, stale or unreliable data be presented?
- What access is permitted by the site’s IT and operations teams?
The starting point
A monitoring brief that connects each important condition to an owner, a response and the information needed to investigate it.