1. Executive Overview
IntrusionIQ™ is a data-verified intrusion detection platform designed to bridge modern AI video analytics with traditional burglary alarm panels—without transmitting video off-premises, without requiring a VMS or NVR, and without altering established central station workflows.
IntrusionIQ operates as an on-premises intrusion intelligence receiver. It ingests analytic event data generated at the camera edge, applies deterministic logic locally, and converts verified events into standard alarm zone activations recognizable by legacy intrusion panels and central monitoring stations.
The result is a system that delivers true intrusion verification, dramatically reduces false alarms, and maintains compliance with existing alarm signaling standards—while remaining simple to wire, program, and deploy.
2. Core Design Principles
IntrusionIQ was engineered around five foundational principles:
-
Verification at the Edge
All detection and verification occur on-premises, inside the camera and IntrusionIQ device. -
No Video Transmission
No live or recorded video is sent to the central station or cloud. -
Panel-Native Integration
Events are delivered to the alarm panel as conventional zone activations. -
Minimal Wiring & Familiar Programming
Integrators use the same wiring methods and zone programming they already know. -
Vendor-Agnostic Architecture
Compatible with major intrusion panels and AI cameras capable of analytic event output.
3. System Architecture Overview
3.1 Major Components
An IntrusionIQ system consists of:
-
AI-Enabled IP Cameras
Cameras perform analytics at the edge (e.g., human detection, line crossing, loitering). -
IntrusionIQ Receiver
A dedicated on-premises device that receives analytic event data via Ethernet. -
Existing Intrusion Alarm Panel
Honeywell, DSC, Bosch, Napco, DMP, and others. -
Central Monitoring Station
Receives standard alarm signals (Contact ID, SIA, etc.)—no changes required.
3.2 Data Flow (High Level)
-
Camera detects an analytic event (e.g., human presence).
-
Camera sends a data event (HTTP, TCP, or webhook) over Ethernet.
-
IntrusionIQ validates, maps, and processes the event locally.
-
IntrusionIQ activates a corresponding physical alarm zone output.
-
The intrusion panel reports the event to the central station as a standard alarm.
4. Edge Analytics and Event Verification
4.1 Analytics Performed at the Camera
IntrusionIQ leverages camera-resident analytics, including but not limited to:
-
Human / person detection
-
Line crossing (directional)
-
Region intrusion
-
Loitering
-
Time-of-day or schedule enforcement
Because analytics run on the camera itself:
-
There is no latency from cloud processing.
-
No video leaves the premises.
-
Privacy exposure is materially reduced.
4.2 Event Qualification Logic
IntrusionIQ does not blindly convert every analytic event into an alarm.
The receiver can apply logic such as:
-
Single-analytic triggers (e.g., human detected)
-
Multi-analytic confirmation (e.g., human + line crossing)
-
Temporal filtering (minimum duration, dwell time)
-
Zone-specific rules
Only validated events result in alarm zone activation.
5. IntrusionIQ Receiver Functionality
5.1 Event Intake
IntrusionIQ listens on the local network for analytic event messages generated by cameras. These are data-only packets—not video streams.
Supported characteristics:
-
Ethernet-based communication
-
Local subnet operation
-
Deterministic, low-latency processing
5.2 Zone Mapping
Each camera or analytic condition is mapped to a discrete alarm zone.
A single IntrusionIQ receiver can support:
-
Up to 16 independent zones
-
One-to-one mapping of camera → zone
-
One-to-many logic (multiple analytics per zone if desired)
From the panel’s perspective, these zones are indistinguishable from traditional intrusion devices.
6. Wiring Overview (Emphasis on Simplicity)
6.1 Power
IntrusionIQ can be powered in one of two ways:
-
PoE / PoE+ via Ethernet
-
12VDC from the alarm panel (less than 1A total draw)
No external power supply is required in most installations.
6.2 Camera Wiring
-
Cameras connect via standard PoE Ethernet
-
No alarm wiring is run to the camera
-
No relays, no dry contacts at the camera
6.3 Panel Connectivity Options
Honeywell (Vista / VPlex)
-
Two-wire VPlex polling loop
-
Up to 16 virtual zones over a single loop
-
No individual zone wiring per camera
DSC, Bosch, Napco, DMP
-
Standard keypad or expansion bus
-
Typically 4 conductors total
-
All zones carried digitally over the bus
IntrusionIQ presents itself as a familiar zone expansion device to the panel.
7. Panel Programming
7.1 Zone Definition
Each IntrusionIQ output is programmed as a standard zone:
-
Burglary perimeter or interior
-
Instant or delayed
-
Followed by existing system arming logic
No special panel firmware or custom drivers are required.
7.2 Reporting Codes
Zones can be assigned:
-
Standard burglary codes
-
Verified burglary codes (where supported)
-
Custom Contact ID or SIA identifiers
From the central station’s standpoint, these are conventional alarm signals.
7.3 Central Station Compatibility
Because IntrusionIQ outputs traditional zone activations:
-
No changes are required at the central station
-
No new automation software
-
No operator retraining
-
No video handling policies required
8. No NVR, No VMS, No Cloud Dependency
IntrusionIQ does not require:
-
Network Video Recorders
-
Video Management Systems
-
Cloud subscriptions
-
Off-site servers
If video recording is desired, it may exist independently, but it is not part of the alarm decision path.
9. Reliability, Privacy, and Compliance
9.1 Privacy by Design
-
No live video transmission
-
No stored video off-premises
-
No operator video review
-
Reduced exposure under privacy and surveillance laws
9.2 Deterministic Alarm Behavior
Unlike human-reviewed video verification:
-
Events are evaluated consistently
-
No subjective interpretation
-
No staffing delays
-
No operator discretion risk
10. Deployment Summary
From an installer’s perspective, deploying IntrusionIQ involves:
-
Install AI cameras (PoE).
-
Connect cameras and IntrusionIQ to the same local network.
-
Power IntrusionIQ (PoE or panel power).
-
Connect IntrusionIQ to the panel bus or polling loop.
-
Program zones as standard burglary inputs.
That is the entirety of the workflow.
11. Conclusion
IntrusionIQ represents a fundamental shift in intrusion detection—moving verification to the premises, preserving the simplicity of traditional alarm systems, and eliminating the privacy, liability, and operational burdens associated with video transmission.
It allows integrators to deploy advanced AI-verified intrusion detection using the tools, wiring, and programming methods they already trust.
No video. No complexity. No disruption. Just verified intrusion signals.