Services
24/7 Remote Site Monitoring Service
Sentor can monitor your sites for you, around the clock, and notify the right people the moment something changes — so the alarm still reaches someone at three in the morning, on a public holiday, or while your own team is asleep.
What the service does
Installing monitoring equipment answers the question what is happening at the site. It does not, by itself, answer the second question: who is watching, right now?
Under a Sentor monitoring service, that second question is ours. Your sites report into Sentor continuously. We watch the device readings, the equipment alarms and the security alarms they raise, and when something happens we notify the appropriate person according to the escalation arrangement agreed with you.
It is the same platform either way. The difference is that the monitoring seat is staffed by Sentor rather than by you.
What is watched
- Device readings — voltages, temperatures, levels, pressures, transmit power and the rest of the analogue picture, watched against the thresholds set for your site.
- Equipment alarms — mains failure, generator state, battery condition, plant faults and any digital input configured to raise an alarm.
- Security alarms — door and gate contacts, motion detection, enclosure tamper and access events at the reader or keypad.
Why hand it over
The cost of monitoring is not the equipment. It is the roster.
A site that matters at 2 pm on a Tuesday matters just as much at 2 am on a Sunday. Covering that continuously in-house means a roster, a handover process, holiday cover and someone competent enough to tell a real fault from a nuisance alarm at every hour of it.
Continuous cover
Monitoring continues through nights, weekends, holidays and your own staff turnover. Nothing depends on one person remembering to check a dashboard.
No monitoring roster to staff
You keep the people who fix things and lose the requirement to also employ people who watch for things.
Fewer nuisance call-outs
Alarms are assessed before they are escalated, so your technicians are called for conditions that actually warrant a response.
A capital purchase becomes an ongoing relationship
Someone at Sentor knows your network, your normal readings and your escalation list — rather than meeting your site for the first time on the day it fails.
It scales without re-staffing
Adding the tenth site, or the hundredth, does not change your internal headcount. The controller and the polling handle the volume.
Your own visibility is unchanged
The service sits alongside your access, not instead of it. SitePRO, SenTrend and SentorCloud continue to work exactly as they would if you were monitoring the network yourself.
How it works
The same platform, with the watching done for you.
There is no separate technology stack for the monitoring service. It runs on the equipment described across the rest of this site.
Step 1
The site decides locally
Scenario logic stored on the controller evaluates every reading on site. A site keeps behaving correctly even while its link back to base is down.
Step 2
The site reports in
Readings, alarms and events reach Sentor over whatever the site uses — cellular, ethernet, radio, satellite or landline.
Step 3
Sentor assesses it
An alarm is read against the site’s normal behaviour and its history, not in isolation.
Step 4
The right person is notified
Notification goes to the person nominated for that alarm at that site, by SMS, email, pager or voice call.
Who this suits
The service is worth most where the gap between an event happening and someone noticing it is expensive — and where covering that gap in-house is disproportionate to the size of the team.
- Operators with sites spread across a region, where no depot is close to all of them.
- Organisations without a staffed night shift, where an overnight fault currently waits until morning.
- Small technical teams responsible for a large number of unmanned sites.
- Sites where the consequence of a slow response is regulatory, contractual or safety-related rather than merely inconvenient.
- Networks already running Sentor hardware, where the equipment is in place and only the watching is missing.
What it does not replace
Being straightforward about this saves a difficult conversation later.
The service watches and notifies. It does not repair. When a fault needs hands on site, those hands are yours or your contractor’s — the service makes sure they are called early and called with the relevant readings, rather than finding out at the next scheduled visit.
It also does not remove the value of the on-site logic. Anything the controller can resolve on its own — restarting equipment, switching to a backup, closing a gate — is still better resolved in the milliseconds the controller takes than in the minutes a human escalation takes. The service is the layer above that, for everything the site cannot fix by itself.
Common questions
Questions about the monitoring service
Does the monitoring service require Sentor hardware?
Yes. The service monitors sites reporting through Sentor controllers, because it is those controllers that produce the readings, alarms and event logs being watched.
If you have existing equipment at a site, in most cases it can be brought in rather than replaced — anything that produces a contact closure, a voltage, a current loop or a temperature output can be wired to a Sentor input directly.
Can I still monitor my own sites if Sentor is monitoring them?
Yes. The service runs alongside your own access rather than replacing it.
SitePRO, SenTrend and SentorCloud continue to work as normal, so your team can view live readings, pull history and change scenario logic whether or not the monitoring service is engaged.
How are alarms escalated to my team?
By SMS, email, pager or voice call, to the person nominated for that alarm at that site.
Routing is set up with you rather than fixed — a single alarm can notify one person or many, and different alarm types at the same site can go to different people. With an ST330 telephone card fitted, the system can place a voice call that announces the alarm and the device reading, and offers keypad options so the recipient can respond from a phone.
What happens if a site loses its connection?
The site keeps running. Its scenario logic is stored in the controller’s own memory and continues to evaluate readings, operate relays and log events while the link is down.
The loss of communication is itself a monitored condition, so a site that stops reporting is noticed rather than silently assumed to be healthy. Logged events are collected when the link returns.
How many sites can be covered?
There is no practical limit set by the platform. SenTrend polls sites on a schedule and collects each controller’s logs in turn, so the arrangement scales with the number of sites rather than requiring more people to watch them.
Coverage, escalation and reporting are agreed per network. Tell us how many sites you run and what a slow response costs you, and we will scope it against that.
Tell us what your sites cost you when nobody is watching.
We will scope a monitoring arrangement against your actual network, escalation requirements and hours — not a standard package.