Casino Door And Panic Button Monitoring With Scalable NetGuardian Expansion

An Iowa casino surveillance team needed a door and panic button alarm monitoring system that could start at about 60 active points and scale to roughly 80. DPS Telecom recommended a NetGuardian RTU solution centered on the NetGuardian 420 with NetGuardian DX discrete-input expansion to support growth while keeping the operator experience familiar.

Quick Facts

Client Overview

DPS Telecom frequently supports casinos and similar facilities where surveillance teams need immediate visibility into safety and security events. In this project, a Surveillance Technician at an Iowa casino (referred to here as "Adam") reached out after working with DPS equipment at a previous property.

Adam was already using Surveillus at the casino and had previously used Surveillus with DPS Telecom alarm systems. His request was straightforward: pricing and a practical design for door and panic alarms that could grow over time.

The Challenge

The casino had about 60 active alarms made up of door contacts and panic buttons, with plans to expand to around 80 total. The monitoring system needed to handle dry contact inputs (simple open/closed circuits typical of doors and emergency buttons) and present alarms in a way that surveillance staff could quickly interpret and act on.

In addition to capacity, the project had two real-world constraints:

• Operator familiarity: Adam had used a NetGuardian M16 at a prior property and wanted an interface that would feel similar.
• Budget: The target budget was under $2.5K.

When these constraints combine, a common pitfall is selecting a device that works for the initial point count but forces a forklift upgrade (or multiple devices) once expansion begins. DPS Telecom's goal was to recommend a design that would meet current needs while keeping expansion simple and predictable.

The Solution

DPS Telecom recommended the NetGuardian 420 as the primary RTU because it fits the size of the project while providing a clear path to expand input capacity without deploying multiple independent base units.

On its own, the NetGuardian 420 provides:

• 20 discrete inputs for dry contacts (ideal for door switches and panic buttons)
• Up to 6 analog inputs for additional monitoring needs if required later

More importantly for this casino, the NetGuardian 420 supports add-on expansion to increase discrete point count as needs grow. When combined with expansions, it can monitor up to 164 discrete points.

The NetGuardian DX Extension is designed to be used with an existing RTU to double, triple, or quadruple the input capacity of your NetGuardians.

To add discrete alarm points at low cost and with straightforward wiring, DPS Telecom also recommended a NetGuardian DX expansion unit - specifically the NetGuardian 832 DX G5. This self-contained expansion chassis adds more discrete alarm points and provides additional relays and analog capacity per chassis.

The recommended approach was to size the base RTU for the initial deployment, then add DX expansions only as the point count grows. DX expansions can be daisy chained (up to three) to support future growth without changing the core monitoring workflow.

This diagram demonstrates the kind of setup recommended for this project. It includes a NetGuardian 420 RTU with DX Extensions added as needed.

Why this matters operationally: expanding a single RTU with DX units keeps alarm presentation consolidated and avoids splitting alarms across multiple independent devices, IP addresses, and configuration sets. That consolidation is especially valuable for surveillance and security teams that need fast recognition and response during an incident.

Proposal Summary

Two days after the discovery call, DPS Telecom sent a proposal that documented the casino's requirements and mapped them to a scalable device plan. The proposal emphasized:

• Adam's existing familiarity with the NetGuardian M16 and the desire for a similar operator experience
• Support for up to 80 dry contact inputs for door contacts and panic alarms, with room to expand further
• NetGuardian 420 as the base RTU, plus DX expansion to add 64 dry contact inputs per expansion unit

DPS Telecom also highlighted a practical benefit for operations and maintenance: a telco-grade, US-manufactured RTU designed for high reliability monitoring in long-lived deployments.

Addressing UI Concerns and Designing for Growth

After reviewing the proposal, Adam raised a reasonable concern: the NetGuardian 420 interface is not identical to the NetGuardian M16 interface he had used before. While one of DPS Telecom's other sales engineers discussed the quote with him during a brief scheduling gap, the core technical guidance remained consistent - use an expandable RTU so the casino can scale point counts without multiplying devices.

DPS Telecom clarified that the NetGuardian 420 interface is similar enough to keep the learning curve small, and that the 420 is better suited to the project because it starts with more inputs and supports expansions. In contrast, the NetGuardian M16 is often a better fit for smaller projects because it has 16 inputs and cannot be used with expansions.

For the casino's goal of monitoring around 80 sensors, using only NetGuardian M16 hardware would require five separate M16 units. The proposed alternative - one NetGuardian 420 (20 dry contact inputs) with two DX expansions (adding 64 dry contact inputs each) - would provide the needed capacity with additional spare inputs available for growth.

To make adoption easier, DPS Telecom offered a demo of the NetGuardian 420 interface to review day-to-day alarm use and explain the minor differences versus the M16.

Just because "Adam" is in the casino business, does not mean he should take risks with the casino's security alarm system.

Results

The outcome of this engagement was a clear, scalable monitoring plan for door contacts and panic buttons that aligned with the casino's point-count growth targets and operator preferences. The recommended design minimized complexity by keeping alarms consolidated on a single expandable RTU rather than distributing points across multiple standalone units.

For similar surveillance projects, this architecture typically supports better standardization: fewer base devices to configure, a consistent alarm presentation for operators, and a straightforward expansion path as additional doors or panic locations are added.

Key Takeaways

• Design for expansion early: If you know your alarm point count will grow, an expandable RTU like the NetGuardian 420 helps avoid deploying multiple small devices.
• Keep the operator workflow simple: Consolidating alarms reduces the risk of missed events during high-pressure security situations.
• Use modular I/O expansion: NetGuardian DX expansion makes it possible to add discrete inputs in larger blocks as new doors and panic buttons come online.

Products Used in This Solution

• NetGuardian 420 - Expandable RTU used as the core alarm monitoring device.
• NetGuardian 832 DX G5 - DX discrete input expansion chassis used to add additional dry contact alarm points.
• NetGuardian RTU Product Family - Overview of RTUs and expansion options for remote alarm monitoring.

Industry And Challenge FAQ

What is a "dry contact" input for door and panic monitoring?
A dry contact is a simple open/closed circuit from a switch or relay. Door contacts and panic buttons commonly present as dry contacts, making discrete inputs on a NetGuardian RTU a direct fit.

How does a casino surveillance team typically use alarm monitoring alongside video?
Many facilities pair alarm monitoring with surveillance software so operators can see an alarm event (door forced, panic pressed) and then quickly verify conditions using cameras and procedures. In this project, the surveillance technician noted prior experience using Surveillus with DPS alarm systems.

Why not just use multiple small RTUs instead of one expandable RTU?
Multiple devices can increase configuration and maintenance overhead. A single expandable RTU can keep alarm points more centralized, which can simplify day-to-day operations and future growth.

How do DX expansions increase input capacity?
DX expansion units add additional discrete points in a separate chassis and connect back to the base RTU. For the NetGuardian 420, DX expansions can be daisy chained (up to three) as point counts increase.

What should I consider when planning for 60 to 80 alarm points?
Account for growth, spare capacity, wiring topology, and how operators will acknowledge and track alarms. DPS Telecom RTUs are designed to make it practical to start at a smaller point count and add inputs later without replacing the core system.

Talk With DPS Telecom

If you are planning a door and panic button monitoring project for a casino or other security-sensitive facility, DPS Telecom can help you choose the right NetGuardian RTU and expansion approach. Get a Free Consultation or call 1-800-693-0351 to speak with an expert about your project. You can also email sales@dpstele.com or call 559-454-1600.

Andrew Erickson

Andrew Erickson is an Application Engineer at DPS Telecom, a manufacturer of semi-custom remote alarm monitoring systems based in Fresno, California. Andrew brings more than 19 years of experience building site monitoring solutions, developing intuitive user interfaces and documentation, and opt...