How Southeast Nebraska Communications Centralized Discrete Alarms With T/Mon And NetGuardian RTUs

Southeast Nebraska Communications (SNC) needed to retire a Nortel DMS 10 that was still acting as the only way to monitor critical contact-closure (discrete) alarms during an FTTH upgrade. By deploying DPS Telecom NetGuardian and TempDefender RTUs and later adding a T/Mon master station, SNC centralized alarm collection and simplified how technicians receive actionable alarm details.

Client Overview

Southeast Nebraska Communications (SNC) is a third-generation, privately owned communications company that has provided local telephone services in Falls City and the surrounding area since 1906. The company offers local voice, long distance, internet services, Skitter TV, and bundle packages to customers in Falls City, Rulo, Stella, Shubert, Verdon, Salem, and surrounding rural areas.

Contact closure alarms that were previously monitored by a Nortel DMS 10 are now collected by NetGuardian & TempDefender RTUs reporting to a T/Mon master station.

Gary Cornely is the NOC Administrator at SNC.

"I'm in charge of all network systems in Falls City, Nebraska," Cornely said. "They hired me to do Fiber to the Home (FTTH) and upgrade their systems. I do anything IP. I'm also a tech, so I take calls and fix things that break."

The Challenge

When Cornely started at SNC, he faced a common telecom operations problem: an aging central office switch that could not be decommissioned because it was still performing a critical monitoring function.

"Originally, all our discretes were handled by a central office switch, the Nortel DMS 10," Cornely recalled. "As part of the FTTH project, we did not have a solution to effectively manage those discrete contact closures. We couldn't dismantle the switch until we had a solution."

In addition to blocking decommissioning plans, the DMS 10 provided limited alarm context. The team often had to take extra steps to understand what was happening and where to dispatch.

"When we were using the DMS 10. we got a phone call that said you had an alarm," he explained. "But you didn't get any detail until you actually dialed in."

The Solution

SNC evaluated options for a monitoring approach that could handle a broad range of equipment and protocols and provide actionable alarm details to technicians. Their search led them to DPS Telecom.

"My boss had done a lot of research and DPS had come up," Cornely remembers. "That was my first project when I was hired. I looked at the DPS website and talked to (sales engineer) Ron Stover a couple of times. I became convinced pretty quickly that DPS was the only solution that brought it all together. This was what we needed to do."

At a technical level, SNC needed two capabilities:

• Reliable collection of discrete contact closures from legacy and facility equipment (door, power, plant, and other alarm points), using purpose-built remote telemetry units (RTUs).
• Centralized alarm management so notifications are consistent, scalable, and easier to maintain during staffing changes.

DPS Telecom is designed for exactly this kind of transition - using RTUs such as NetGuardian and TempDefender to collect discrete inputs (and other telemetry where needed) and forwarding alarms to a central master station. This approach lets telecom operators retire legacy switch dependencies while improving alarm detail and visibility.

Cornely was particularly interested in a monitoring system that could consolidate equipment and protocols into a single operational picture.

"The number of different devices DPS equipment could talk to, collect from, figure out what to do with, and then send alerts and information," he said. "It just made a lot of sense."

Implementation

SNC started its deployment with NetGuardian and TempDefender RTUs, configuring them to send notifications directly to technicians. Later, they expanded the system with a T/Mon master station to collect alarms from more equipment and centralize control over alarm notifications.

This phased approach is common when replacing legacy alarm paths:

• Phase 1 - Standalone RTU alarming: RTUs collect discrete inputs (contact closures) and send email or other local notifications while the organization validates alarm mappings and response workflows.
• Phase 2 - Centralized master station: A T/Mon master station consolidates alarms, standardizes escalation rules, and simplifies ongoing changes (for example, updating notification lists when staff responsibilities change).

For teams modernizing monitoring during network upgrades like FTTH, DPS Telecom typically reduces operational friction by making alarm points readable and actionable at the moment the alarm occurs, rather than requiring technicians to "dial in" to retrieve details after the fact.

Training And Operational Continuity

The SNC team encountered a common operational risk: staff turnover can leave monitoring configurations hard to understand or maintain if knowledge is not documented and transferred.

"Unfortunately, the guy that got the most out of T/Mon left the company before he could show me how it all worked together," Cornely said. "That's why I came for a week of DPS training."

Free factory training at DPS HQ gave him a solid understanding of both T/Mon and his NetGuardian and TempDefender RTUs. This helped SNC rebuild internal knowledge of how alarms are collected, normalized, and routed to the right responders.

Results

With a complete monitoring system now up and running, Cornely has confidence the solution can withstand future changes, including staffing transitions and unexpected equipment issues.

Key outcomes SNC achieved with DPS Telecom included:

• Freedom to retire the DMS 10 monitoring dependency by migrating discrete contact-closure monitoring to dedicated RTUs.
• Improved alarm clarity compared to the prior workflow that depended on basic phone-call alerts and additional steps to pull details.
• Simplified, centralized monitoring operations after adding a T/Mon master station to manage collection and notification logic.
• Greater resilience to staff changes supported by DPS factory training and accessible technical support.

Support Experience

For telecom NOCs, support quality matters most when a rare or high-impact alarm occurs. Cornely highlighted DPS Telecom's engineering-led support model.

To keep monitoring stable over time, SNC plans to continue using support from DPS HQ engineers when configurations need adjustment or when recovering from unexpected events.

Key Takeaways

• Do not let a legacy switch dictate your monitoring architecture. Dedicated RTUs can take over discrete alarm collection so the switch can be retired on your timeline.
• Start simple, then centralize. Standalone RTU notifications can work initially, but a T/Mon master station simplifies long-term operations as the alarm footprint grows.
• Design for people changes. Factory training and clear alarm ownership reduce risk when responsibilities shift.

Products Used In This Solution

• NetGuardian RTU family - Collects discrete contact closures and other site telemetry and reports alarms for remote visibility.
• TempDefender RTUs - Used by SNC for monitoring and alerting alongside NetGuardian units.
• T/Mon alarm master - Centralizes alarm collection, correlation, and notification control across sites and devices.

Industry And Challenge FAQ

What is a contact closure (discrete) alarm?

A contact closure is a simple on/off electrical state (open/closed) used to represent alarms such as door open, generator run, high water, breaker trip, rectifier fail, or similar plant conditions. RTUs like NetGuardian are designed to collect these discrete points reliably.

Why did the Nortel DMS 10 block decommissioning?

In SNC's environment, the DMS 10 was still the only monitoring gear handling discrete alarm points. Until those alarm paths were migrated to an RTU-based monitoring approach, the switch could not be removed without losing visibility.

Why add a T/Mon master station if RTUs can send emails directly?

Standalone notifications can be effective at first, but a master station centralizes alarm routing rules, escalation policies, and maintenance. This helps reduce configuration sprawl as sites and alarm points expand.

How do DPS RTUs typically connect into a monitoring architecture?

RTUs collect alarms locally (discretes and other telemetry depending on configuration) and forward them to a central system for unified viewing and notification. In this project, SNC used RTUs first for direct alerting, then expanded to centralized alarm management through T/Mon.

How can a team reduce monitoring risk during staff turnover?

Choose a system with clear configuration tools, maintainable alarm documentation, and strong vendor training and support. SNC addressed a knowledge gap by attending a week of DPS factory training.

Talk To DPS Telecom