An intrusion alarm system is not one detector or one siren. It is a chain of responsibilities: devices detect a possible intrusion, a hub interprets the event, warning and reporting paths carry the result, and people decide what happens next.
Before choosing equipment, define three things: the risks to detect, the zones to protect and the response expected from each alarm. That simple map prevents a project from becoming a device list without a clear operating purpose.
Start with the risk, not the catalogue
The same building can need different protection at different times. A front entrance may need an entry delay during opening hours. A stockroom or rear door may need a different zone and response. A house may protect the perimeter at night while occupants remain inside.
Begin by marking:
• the doors, windows and other routes that could be used to enter;
• the internal paths a person would likely take after entry;
• areas containing people, stock or other priority assets;
• the times when each area is occupied, vacant or restricted;
• who should receive information and who is expected to act.
This risk map becomes the basis for zones, device categories and response rules.
The five layers of an intrusion alarm system
1. Detection
Door and window contacts identify an opening. Motion detectors identify movement within a protected area. Other detector types can address different physical events, but each device should have one clear job within the risk map.
For example, an entrance contact can identify that a protected door has opened, while a motion detector can provide a second layer along the likely route inside. For a deeper look at motion detection, use the PIR sensor guide.
2. Control
The control panel or security hub receives device events and applies the system’s armed state, zone settings and configured rules. This layer turns a device signal into a system event.
The hub also connects the detection layer to user controls, local warning devices and any configured reporting path. Its role is therefore broader than simply relaying a radio message.
3. User operation
Keypads, keyfobs and an App or management interface allow authorised users to arm, disarm and review the system. The project should define who may operate which areas and what should happen when people arrive, leave or work in a partly armed building.
4. Local warning
Sirens or other warning devices make an alarm visible or audible at the premises. Their job is immediate local signalling. Their placement and behaviour should match the site’s occupancy and response plan.
5. Reporting and response
A configured system may notify authorised users or report events to an Alarm Receiving Centre. These are different response models with different responsibilities. If professional monitoring is required, define the receiver, event path and service conditions before installation. The ARC integration planning guide covers that decision in detail.
How an alarm event moves through the system
Consider a shop after closing. A rear door opens while its zone is armed:
1. The door contact identifies the opening.
2. The hub receives the event and checks the armed zone and configured rule.
3. The system activates the assigned local warning and reporting actions.
4. The authorised user or monitoring service receives the information available through its configured path.
5. The responsible person follows the agreed response procedure.
This sequence shows why a professional design must define more than detection. A detector can identify a condition, but the complete project also needs control logic, warning, reporting and human responsibility.
The same chain can look different in different projects:
• A home at night: perimeter doors and selected windows may remain armed while people move inside. The design must separate entry routes from occupied areas and define who can disarm the system in the morning.
• A small office or workshop: staff areas, storage rooms and restricted rooms may need separate zones. An event outside working hours may require local warning first and a different reporting path when the site is vacant.
These examples do not create different system principles. They show why the risk map, occupancy pattern and response agreement must come before the equipment list.
Choose the architecture around the premises
Wired, wireless and hybrid are project architecture choices. Start with the required protection points, then consider existing cabling, restrictions on building work and the connections that can be validated at those points. In a professional wireless intrusion alarm, radio connects compatible field devices to the hub while the system retains its detection, control and response responsibilities.
For the comparison and site conditions that change this choice, use the wireless alarm architecture guide. The wireless alarm communication guide covers the local radio link in detail.
Define the response model before final selection
Ask what should happen when the system detects an event:
• Should the premises receive a local audible warning?
• Should authorised users receive information remotely?
• Is professional monitoring part of the project?
• Who verifies an event and who is authorised to respond?
• What must still work if an external network path is unavailable?
These answers influence the hub, communication path, user roles, commissioning evidence and service arrangement. They should be requirements at the start, not late additions after products have been selected.
Project-start checklist
Before moving into detailed design, confirm that the project can answer:
• Risk: What intrusion events must be detected?
• Zones: Which areas operate together, and which need separate control?
• Occupancy: How do people enter, leave and use the premises?
• Detection: Which functional device category addresses each risk point?
• Control: How should the hub interpret each zone while armed?
• Warning: What local indication is required?
• Reporting: Who receives the event, through which configured path?
• Response: Who acts, and under what procedure or service agreement?
• Delivery: What installation, testing, handover and maintenance evidence is required?
Once this map is agreed, detailed work can move to the correct specialist page rather than overloading one document. Use the installation guide when the project is ready to move from system design into execution.
A professional intrusion alarm system works because its layers support one clear outcome. Define the risk, zones and response path first; then choose and commission the components that make that outcome possible.