Skip to content

Intruder detection · RISCO

It was born thinking about seeing what set the alarm off.

RISCO carries verification by image inside the intruder detection system, not stuck on the side. What that means in practice and what the price is of depending on a manufacturer's cloud.

What it is and where you'll find it.

An intruder detection house that bet early on putting the alarm and the image together.

RISCO makes intruder detection control panels, detectors and the services that go with them. Its professional hybrid line is ProSYS, with models that grow by bus and take cabled and radio zones in the same system. What sets it apart from most of this list is not the panel: it is that verification by image and the app are part of the product from the start.

You find it in retail, offices, clinics, warehouses, residents' associations and branch offices. The typical profile is the client with between five and fifty sites, with no security department, who needs to know from their phone what has happened at the branch in a small town at four in the morning. There an alert with no image is not information: it is a bet.

How it's built.

The base is the classic: a panel with its zones, a bus off which hang keypads and expanders, zones supervised with an end-of-line resistor to tell alarm, tamper and cut apart, partitions with their own arming and schedules, and a supervised power supply with calculated batteries. The radio is two-way, so the panel knows whether each device is alive, with how much battery and with what signal.

The part that is its own is the image. The system takes detectors with a built-in camera, which send a sequence of what has just gone past them when they fire, and network cameras associated with the alarm installation. It is not a video system: it does not record for investigating later. It is what matters at four in the morning — knowing whether what crossed in front of the detector was a person or a bag.

All of that reaches the user and the installer through a cloud service from the manufacturer itself, which is what makes the app, the phone alerts, the remote video and the remote maintenance work. To the receiving centre it transmits over the network with mobile network backup, supervised.

The manufacturer's cloud: what it gives and what it costs.

It is a client's decision, not a technical detail, and it is told in full.

What it costs has to be said just as plainly. Dependency: if the line to the premises or the manufacturer's service goes down, the panel carries on detecting and carries on transmitting to the receiving centre over its route, but the app, the remote video and remote arming stop being there. People usually imagine the opposite, so it is worth saying what never depends on the internet: the local detection and the alert over the supervised route.

And data. There are images from inside premises passing through a third party, and the one who answers to the Spanish data protection authority is the client. Before signing, you ask in writing for the hosting region, the processor contract with its sub-processors and the mechanism covering transfers outside the European Union. Plus the notice sign and who may view the images. And the recurring cost, which is compared over five years and not by the price of the box.

How it behaves with false alarms.

Here it has a structural advantage. When a detector goes off, all you know is that something has crossed in front of it, and whoever is on duty has two bad options: sending somebody out blind every time —which costs money and is therefore abandoned— or sending nobody. With an image attached to the trigger that becomes ten seconds of looking: thirty alerts a month become thirty quick dismissals and the one real one becomes an immediate phone call.

What it does not fix is the fitting, which is where most false alarms come from. An infrared facing a west-facing metal shutter: it fires at dusk when the sheet cools. A detector in the blast from the air conditioning: it fires when the machine starts, at the same time every day. An indoor detector covering a yard: cat, tarpaulin, wind. A masking fault every morning at the same time: a pallet parked in front of it. With an image, all of that is diagnosed faster, and that is an advantage not usually mentioned: instead of arguing about why zone 12 goes off, you look at the last five triggers and you see. What is not done is lowering the sensitivity; and the zone under building work is isolated on paper and with a date for coming back.

The grade, and the alarm receiving centre.

The European standards classify alarm systems into security grades according to risk, and each grade demands things of the equipment, the cabling, the power supply, the tamper detection and the supervision of the transmission. It is set by the activity, very often by the insurance and sometimes by a specification. Which grade each model is certified for is in its certificate, with a date; which grade an installation meets depends on the whole build and is signed by whoever hands it over. They are two different things and quotations mix them up. On the receiving centre there is a check of its own here: in Spain it is obliged to verify the alert before passing it to the State security forces, and a system born with the image inside it fits that well — but you have to confirm beforehand exactly what the receiving centre that is going to look after the installation receives and whether it can see that image, because it depends on their platform and not only on the panel.

Who it fits, and who it doesn't.

It fits beautifully the client with several small or medium sites, with no guard and no security department, who needs to know what is happening without going: shop chains, clinics, branches, industrial units on their own. It fits when the stated problem is «it went off and we didn't know whether to go», and when the client is going to live with the system from their phone.

It does not fit if the company's policy forbids images from inside going out to a third party's service, or if there is a sector obligation preventing it: there the conversation ends before it starts, and better beforehand. Nor in the very large installation with a supervised ring bus and dozens of areas. And there is a misunderstanding worth cutting off in the first meeting: this is not video surveillance. It serves to verify an alarm, not to record a whole shift or to meet a recording requirement; if real video is also needed, it is designed separately.

What we do with it.

  • The design, with a visit at the hour the protection is for, and thinking about the field of view: an image you cannot make sense of verifies nothing, so you have to look at the light and the field of every camera or camera detector, not just hang the unit up.
  • The commissioning setting the alarms off on purpose: every detector tested by walking in front of it, every contact opened, a lens covered, a battery removed, the main route cut and a call to the receiving centre to find out whether it noticed and whether the image arrived. A certificate written beforehand and filled in as you go, with the time and the result for each element.
  • The maintenance with a battery calendar, a report per element and a review of the last triggers with their video to catch noisy zones. And the accounts in the client's name: in a system with a cloud, who the account holder is matters more than it looks on the day you change supplier.

Who runs it once we leave.

Of the eleven, one of the ones the client can run alone the most. With two clear limits.

The day-to-day belongs to the client and the app is built for it: users and codes, who arms which partition, arming and disarming remotely, schedules, one-off isolation of a zone, alerts to whom and when, the log, battery status and a review of the images from the last triggers. In a chain with twenty premises, the operations manager can run that without calling anyone.

The two limits are not technical. Who holds the administrator account, which should be the client, with named users and not one code shared by the whole shop. And who may view the images, which is a data protection decision and not a convenience: giving fifteen people access to a shop's video because it is easier is a problem waiting for a date. What needs the installer is the layer underneath —expanders and zones, pairing devices, times and confirmation logic, partitions, what is transmitted to the receiving centre, the cameras associated with each zone and the versions—, and if it was handed over with a grade, every change means the documentation has to be reviewed. With training by role and a folder saying which camera verifies which zone, the client governs this.

Get started

«It went off and we didn't know whether to go.»

If that sentence sounds familiar, the problem is not the detector: it is that the alert arrives with no information. Tell us how many sites you have, what is fitted and how many alerts come in a month, and we will tell you what is needed for whoever receives the alarm to be able to decide in ten seconds.