Ricotta Alarm Systems: Comprehensive Hardware and Software Guide

Core Advantages: New Alarms vs. Classic Systems

Local Arming and Disarming: A primary advantage of new alarms is the ability to arm and disarm locally. Classic systems performed these actions entirely in the cloud, which created high risk during network outages.
Centralized Processing: New systems use a main brain (panel) for local operations, whereas classic systems lacked a local central brain, making them non-functional if connectivity was lost.
Rip and Replace: New alarms are designed for easy replacement. While classic systems were primarily $PUE$ -based, new alarms are primarily two-wire or four-wire, which are more common in traditional security environments.
Detect and Respond: The core purpose of the system is twofold: detect activity via sensors, cameras, and access control, and respond by notifying parties or contacting law enforcement for intrusion deterrence.

The BP52 Wired Alarm Panel: The Central Brain

The $BP52$ is the foundational component for a fully blown-out ricotta alarm system. It acts as the central brain for all system operations.
Power Specifications: The unit includes a power cable and features a $100$ to $240\,\text{volt AC}$ power slot.
Auxiliary Inputs: It supports $32$ aux inputs for wired sensors. These are configurable as either dry (no power) or wet (powered) sensors. * Wiring: Supports two-wire or four-wire configurations. * Power Budget: Each rail on the panel (splitting the $32$ inputs into groups of $16$ ) has a maximum power budget of $12\,\text{volts}$ and $1\,\text{amp}$ . * Sensor Types: Connections ( $z$ , $z$ , $com$ , $+$ , $-$ ) can be configured via software as normally open ( $NO$ ) or normally closed ( $NC$ ).
RS-485 Ports: There are $4$ $RS-485$ slots on the bottom of the panel for ricotta-specific peripheral devices like expanders, hubs, or keypads. Third-party $RS-485$ devices are not supported.
Output Relays: Features $2$ dry or wet output relays for sirens or strobes. These are configurable to $12\,\text{volts}$ , $24\,\text{volts}$ , or none (dry).
Cellular Backup: This is a separate add-on device that connects to the cloud via carriers like Rogers or TELUS in Canada if the local $LAN$ fails. This requires a specific license due to the data plan cost.
Battery Backup System: * The panel itself can house $2$ batteries. * Using two additional trunk cases, the system can support up to $6$ backup batteries. * Calculation: Users are encouraged to refer to specific health articles to calculate battery needs based on the amount of wired sensors and peripheral power draw.
Built-in PoE Switch: The $BP52$ has a built-in switch with $4$ $PoE$ ports and a power budget of $60\,\text{watts}$ . There is $1$ $LAN$ port for network connectivity. Connecting devices (like keypads) directly to this switch ensures they remain on the same local network as the panel.
Wireless Transceiver: Includes an $SMA$ sub-gigahertz transceiver antenna. While the panel can act as a wireless hub without the antenna, the range will be significantly impacted.

The BP32 Wireless Alarm Panel: Compact and Dedicated

The $BP32$ is a smaller, compact panel designed for smaller businesses or deployments that do not require extensive wired sensor inputs.
Power: Powered via $PoE$ or $PoE+$ . If peripheral devices are connected to the $RS-485$ out slot, $PoE+$ is required.
Integrated Components: Unlike the $BP52$ , the $BP32$ has the cellular backup (with two $LTE$ antennas) and the backup battery built directly into the device.
Battery Life: The built-in battery provides approximately $30\,\text{hours}$ of operation. It is rechargeable but cannot be expanded with external batteries.
Connectivity: It features an $RS-485$ output module and a $PoE$ port for network and power. It primarily supports wireless deployments but can use zone expanders for a limited number of wired inputs.

Expansion and Peripheral Devices

BE32 Zone Expander: * Connects via $RS-485$ to the alarm panel. * Purpose: Expands the number of wired zones. It provides $8$ additional wired inputs (two-wire or four-wire, wet or dry) and $1$ output relay. * Wireless Capability: Acts as a wireless hub supporting up to $160$ cauta wireless sensors. * Daisy-Chaining: Up to $4$ $BE32$ units can be daisy-chained on a single $RS-485$ slot of the $BP52$ . Theoretically, with $16$ expanders attached (across $4$ slots), the system could support thousands of sensors ( $16 \times 160 = 2560$ ). * For the $BP32$ (wireless panel), it is recommended to limit daisy-chaining to $2$ units in real-world environments.
BK22 Alarm Keypad: * Functions: Used for arming and disarming via key codes. It can display footage from alarm-trigger cameras when connected via $PoE$ . * Connectivity: Can be home-run via $RS-485$ or connected via $PoE$ on the same local network as the panel. * Wireless Hub: Also contains a built-in hub supporting up to $160$ wireless devices.
W52 / WH32 Wireless Hub and Repeater: * Hub Mode: Connected via $PoE$ or $RS-485$ ; supports $160$ wireless sensors. * Repeater Mode: Connected via a $DC$ barrel jack ( $10$ to $36\,\text{volts DC}$ ). It boosts the signal from an existing hub to reach sensors farther away. * Limitation: Repeaters cannot be daisy-chained for wireless signals (Hub -> Repeater -> Sensor is the only supported path).

Sensor Generations and Capabilities

New alarms support only cauta wireless sensors for their hubs.
VR Series (First Generation): * BR33: Mounted panic button. In new systems, these must be mounted (to a desk or wall) to avoid connectivity and logging issues found in classic “mobile” versions. * Water Leak Sensor: Used in high-sensitivity areas like data centers.
Q Series (New Generation): Released around January-February and recommended for all new deployments. * QC11: Wireless door and window contact. * QM11: Wireless motion sensor. * QT11: Wireless transmitter. This allows users to make a wired sensor wireless by wiring the physical sensor to the $QT11$ , which then transmits the signal to the hub.
Wireless Range: Line-of-sight range is $300$ to $500\,\text{feet}$ . In a typical office environment with obstructions, the range is roughly $50$ to $100\,\text{feet}$ . Verification via field testing is always recommended.

Deterrence and Audio Output Devices

BC11 Intercom/Speaker: A $PoE$ device that can be used for agent talk-down, $AI$ deterrence, or playing audio files during an alarm. It requires a separate license.
BZ32 Siren/Strobe: * Manual Mode: Wired to the output relay. Volume and color are set physically on the device via switches. No software-based configuration is possible. * Smart Mode: Connected via $RS-485$ , $DC$ power, or wireless ( $V-Link$ with batteries). Allows color and volume to be changed via the Command software. * Warning: The device is extremely loud (up to $100\%$ volume is piercing even in large warehouses).

The Alarms Upgrade Program (Migration)

Hardware Replacement: One-to-one replacement of classic hardware with new hardware.
Firmware Upgrades: Original hubs (like the $BC61$ ) can be upgraded via firmware to work with new alarms without physical replacement.
Wireless Migration Tool: Facilitates the moving of $VR$ series sensors from classic to new systems.
License Conversion: Free conversion that preserves the original renewal date.
Installation Costs: Ricardo covers some costs based on hourly rates and estimated timeframes (e.g., $3\,\text{hours}$ for a panel install). This is a guideline, and specific details should be discussed with the migration team.

Licensing Models and Device Caps

Basic Alarms License: * No device cap for sensors. * Supports sensors only. * No video verification, no monitoring team, and no context cameras.
Advanced Video Alarms License: * Supports both sensors and camera triggers. * Includes video verification by professional monitoring agents. * Limits: $15$ camera triggers per alarm site. To exceed this (e.g., $30$ cameras), you must stack multiple licenses.

Alarm Enforcement Limits and False Positive Policy

Threshold: Each alarm site is limited to $15$ alarms per month that involve the professional monitoring team.
Three-Month Rolling Policy: * Month 1 and 2: If the site exceed $15$ alarms, there is no penalty; all events are sent to monitoring. * Month 3: If the limit is exceeded again, the $16\text{th}$ event and beyond will be throttled. They will generate an $SMS$ or email to the user but will not be sent to the monitoring team. * Resetting: If the site falls below the limit for a single month, the three-month counter resets to Month 1.
Self-Monitoring Exception: Alarms set to "Self Monitoring" do not count toward this limit because they do not utilize the professional monitoring team.

User Roles, Permissions, and Contacts

Site Admin: Full permissions to add/remove devices and edit all settings. Inherited from camera site admin permissions.
Arm/Disarm: A dedicated permission for employees to toggles the state of the alarm without accessing settings.
Site Viewer: Can only view alarm history or reports.
Alarm Response Contacts: * Internal Contacts: Command users who receive notifications and can resolve alarms in the app. * External Contacts: Phone numbers added to the response list. They receive an automated $SMS$ upon being added and receive calls during alarms. They cannot log into Command. * Recommendation: Always have at least $3$ contacts to ensure someone is reached.

Native Integrations: Video, Access Control, and Intercom

Video Alarms: Ricotta cameras can act as triggers without an alarm panel. * Supported triggers: Person Detection, Loitering ( $10\,\text{seconds}$ to $2\,\text{minutes}$ ), Line Crossing, and Vehicle Detection. * Motion detection is excluded as a trigger to prevent excessive false positives. * $PTZ$ cameras can only use whole-frame person detection because digital lines/zones would move with the camera.
Access Control: Requires a local network connection between the access controller and the alarm panel. * Triggers: Door Forced Open, Door Held Open, and Door Open. These require a $DPI$ . Door Forced Open requires an established Request to Exit ( $REX$ ) toggle in Command. * Disarming: Valid badge-ins or double-badging (triggering within $5\,\text{seconds}$ ) can arm/disarm the site. Bluetooth and remote unlocks are not supported for arming/disarming.

AI Deterrence: Multi-Stage Warnings

Function: Uses camera analytics to play audio warnings through intercoms or speakers before an alarm is officially raised.
Three-Stage Warning Example (San Mateo Incident): 1. Initial Message: "Please don't loiter in front of the garage entrance. This area is actively monitored." 2. Secondary Specific Message (if loitering continues): "You in the dark blue hooded jacket with a backpack. I already told you this area is closed… I will take immediate action." 3. Final Warning: "You in the dark blue puffer jacket with a backpack. Final warning, leave the garage entrance area now."
Execution: The system uses different voices for each instance to sound human and includes specific visual descriptors (clothing, backpack) to create the impression of a live guard.

Software Logic: Partitions and Arming Modes

Partitions: Logical groups of devices typically covering a specific area that can be armed independently. * Example (Bank): Partition 1: Exterior (low priority); Partition 2: ATM Lobby; Partition 3: Office Spaces; Partition 4: Bank Vault (high priority).
Arming Modes: * Manual: Arm and disarm manually via app or keypad. * Schedule: Automatically arms/disarms at set times. * Always Armed: For high-security areas (like vaults) or panic buttons that should never be disarmed.
Smart Schedules: A feature that delays scheduled arming if a camera sees a person inside the building in the $30\text{-minute}$ window before the arm time. This prevents employees working late from triggering false alarms.

Professional Monitoring and Response Flow

Trigger: A sensor or camera detects an event.
Monitoring Agent (Stage 1): Receives the footage. They only verify if a person is present. They do not judge behavior or clothing.
Escalation: If a person is confirmed, outputs (strobes/sirens) trigger.
Response Agent (Stage 2): Contacts the site's listed contacts in order. Descriptions are provided (e.g., "An individual jumped the fence at the North Gate").
Standard Response: If the contact asks to dispatch or does not pick up, the agent calls law enforcement.
Immediate Dispatch: Agent calls law enforcement immediately upon person verification.
Resolution: The alarm is logged in Command, showing who viewed it, when law enforcement was called, and the literal transcript of the conversation with the police dispatcher.