Remote monitoring is valuable when it tells the site what to protect, gives engineers usable evidence, defines when to stop or attend and records how the issue was closed.
What the project should produce
Teams coordinating multiple mine units, remote sites and service regions.
Prevent alarm floods with no ownership and critical alarms with no evidence.
Produce a point list, alarm matrix, event pack and closeout record.
Every alarm needs a source, priority, owner, response, field action and escalation trigger. The system must also alarm on loss of communications while local protection remains independent.
01
Define points and data quality
Signals need source, unit, validity and timestamp.
- Separate controller and external sensor data
- Record sampling, time sync and link state
- Flag frozen, missing and invalid values
02
Prioritize by consequence
Trips, derates, planned maintenance and information need different workflows.
- Define critical, important and advisory levels
- Assign field action and owner
- Suppress duplicate symptoms without hiding root alarms
03
Give engineers the event context
A code alone is not a cause; pre- and post-event trends matter.
- Save timeline and critical trends
- Attach history, photos and site observations
- Record reset, transfer and manual intervention
04
Keep local protection when communications fail
Network loss must not remove trips or make a silent unit appear healthy.
- Keep protection independent of cloud and link
- Alarm on stale data and time faults
- Provide field inspection and backup communications
05
Feed each event back into maintenance and spares
Closeout needs cause, containment, permanent repair and verification.
- Assign issue ID and closeout owner
- Link parts, labour and downtime
- Update thresholds, inspections and safety stock
Project review matrix
| Define points and data quality | Separate controller and external sensor data；Record sampling, time sync and link state |
|---|---|
| Prioritize by consequence | Define critical, important and advisory levels；Assign field action and owner |
| Give engineers the event context | Save timeline and critical trends；Attach history, photos and site observations |
| Keep local protection when communications fail | Keep protection independent of cloud and link；Alarm on stale data and time faults |
| Feed each event back into maintenance and spares | Assign issue ID and closeout owner；Link parts, labour and downtime |
Three common mistakes
Adding points without ownership
Poor data and no action create alarm fatigue.
Using remote reset instead of field verification
Evidence may be erased and mechanical damage may continue.
Assuming a live link means healthy equipment
Data can be stale or distorted despite connectivity.
Information to prepare for engineering review
- Controller and sensor point list
- Alarm priority and owner matrix
- Stop and reset authority
- Network and loss-of-data alarms
- Standard event evidence pack
- Closeout, maintenance and spares feedback