Intruder detection · Honeywell Galaxy
It is fitted in half the country. And that is almost the whole argument.
Galaxy is one of the most widely installed intruder detection panels in Europe. What it brings, what inheriting one programmed by somebody else means and when the sensible decision is to carry on with it.
What it is and where you'll find it.
A family of professional panels with an enormous installed base, and that has consequences that are not technical.
Galaxy is Honeywell's intruder detection line for professional installation, with families covering everything from a shop to a building with hundreds of points, including a larger range that also controls doors. They are all programmed with the same logic, and that explains half of its success: a technician who knows Galaxy knows Galaxy at any size.
You find it everywhere: shops, offices, schools, warehouses, bank branches, whole industrial estates. If you have walked into a building with an alarm keypad in the lobby in the last twenty years, there is a fair chance it was one of these. That is why, when somebody calls us to change installer, what is fitted is often one of these, and the real question is not which panel to buy but whether to buy one at all.
How it's built.
The classic architecture, and it is the reason it lasts so long. The panel has its zones and it grows with expansion modules spread through the building, hanging off a two-wire bus plus power; each module provides inputs and outputs and is put close to the detectors, so the cable that gets pulled is short. In large installations several bus lines are used, and splitting well what hangs off each is what stops a fault taking the building with it.
The building is divided into independent groups with their own arming, schedule and users, with part-arming for the night, and with arming by keypad, by key, by schedule or by an exit terminator button, which is the decent way of finishing the walk round instead of trusting a timer. The larger range also controls a handful of doors: it is not an access control platform, and for a dozen doors with schedules it is what is needed without building a second system. Outwards, transmission over the network with mobile network backup and remote maintenance, which changes the contract more than any feature of the panel.
How it behaves with false alarms.
As standard it brings what is needed: alarm confirmation, requiring two different zones to detect something within a time window before treating it as a confirmed intrusion; automatic omission of the zone that fires repeatedly in the same period, so that a faulty detector does not bury whoever is on duty; entry times and routes properly defined by group; and double balancing, which separates alarm from tamper and from fault. With dual-technology and anti-masking detectors, the whole is a match for anything on this list.
And now the part that makes us unpopular. In the installations of this kind we have inherited, the false alarm almost never came from the panel. It came from three things: detectors put where the cable suited rather than where the detection was needed; sensitivities halved so it would stop being a nuisance, which fixes nothing and leaves the zone deaf; and zones omitted for months without anybody knowing, because omitting is free and barely shows. A building with five omitted zones has five holes, and the keypad says so every night to somebody who no longer reads it.
Inheriting one somebody else programmed.
It is the most frequent scenario with this family, and it has its own order of work.
- The engineer code and the access. If the previous installer does not hand it over, that is the client's problem before it is a technical one and it is worth knowing on day one. Whoever does not have the keys does not have a system: they have a dependency.
- And the transmission, checked by cutting it and asking the receiving centre whether it noticed. There are installations transmitting to a destination that no longer exists, with the client paying the connection fee.
The grade, and the alarm receiving centre.
The word «grade» appears in almost every intruder detection quotation and is documented in very few. It means something specific: 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 policy and sometimes by a specification. Hence the distinction that always has to be made: equipment certified for a grade is not an installation that meets that grade. What grade is handed over is stated by the design and signed by whoever hands it over; and if the grade you need does not fit the budget you have, that is said before signing.
The alarm receiving centre goes its own way: another contract, other regulations and the obligation to verify the alert before calling out the police. That is why verification is not a pretty add-on: it is what makes an alert worth something.
Who it fits, and who it doesn't.
It fits the ordinary building that actually exists: a large shop, a school, an office over several floors, an industrial unit with a store and an office block, a branch network with the same programming repeated. It fits very well when a few doors have to be controlled as well as the alarm. And it fits when one is already fitted, because continuity is worth money: spares, technicians who know it and a client who does not have to learn another keypad.
It does not fit if what you want is a modern phone app as the main way of living with the system. You can have one and it works, but this family was born before the phone and it shows: its centre of gravity is the keypad and the installer software. There are wireless systems on this list that are a generation ahead on that, and if the client wants to arm from their pocket and see a photograph, that has to be said. And it does not fit either if nobody is going to do the maintenance: the difference between the ones still serving after fifteen years and the ones that are switched on and serving nothing is not the model, it is whether somebody has walked in front of every detector once a year.
What we do with it.
- The design, with a visit at the hour the protection is for: which detector at each point, at what height, looking where, what is on the other side of that wall and what moves there at night. And the split into groups discussed with whoever arms it each day, who is the person who decides whether the system gets used or left disarmed.
- The commissioning setting the alarms off on purpose: every detector tested by walking in front of it, every contact opened, a lens covered to see whether the masking alert comes up, the main route cut and a call to the receiving centre to find out whether it noticed. A certificate written beforehand and filled in as you go, with the time and the result for each element.
- The maintenance with a report per element, the log reviewed to catch noisy zones, batteries measured and a check on what is still omitted and why — using the remote access to diagnose before travelling, which brings the contract price down instead of putting it up.
Who runs it once we leave.
The split is fairly clear, and it is worth writing into the contract.
The client runs what is theirs: users and codes, who can arm which group, the part-arming at night, the automatic arming schedules, the one-off isolation of a zone for building work or a fault, and reading the log. The user levels let a shop manager add a sales assistant without being able to touch the configuration, and that is the split to set up on day one. The classic mistake is everybody using the same code: when the log says that at 22:14 «user 1» disarmed, it says nothing.
What needs the installer is the layer underneath, and part of that is not our decision but the standard's and the design's: adding or removing modules and zones, changing times, entry routes or the confirmation logic, redoing groups, touching what is transmitted to the receiving centre and changing versions. If the installation was handed over with a grade, on top of that, any of those changes means the documentation has to be reviewed: a system whose paperwork no longer describes what is installed is a system with no paperwork.
And two things are needed that are handed over and charged for. Separate training by role —whoever arms each day, whoever manages users, whoever decides in the small hours— and documentation worth having: a drawing with every detector and its zone, groups and schedules exactly as they ended up, the resistors used, and who receives which alert and in what order.
The other ten in this group.
None is better than another. What changes is the architecture, what they bring against the false alarm and how much the client can govern afterwards.
Get started
Have you got a Galaxy and no idea how it is programmed?
It is the most normal thing in the world and it can be sorted out. Tell us what is fitted, how many alerts come in a month and whether you have the engineer code, and we will tell you what can be reused, which zones have been omitted for years and what it costs to leave it documented.