Check out our White Paper Series!
A complete library of helpful advice and survival guides for every aspect of system monitoring and control.
1-800-693-0351
Have a specific question? Ask our team of expert engineers and get a specific answer!
Sign up for the next DPS Factory Training!
Whether you're new to our equipment or you've used it for years, DPS factory training is the best way to get more from your monitoring.
Reserve Your Seat TodaySprint PCS relied on a DPS Telecom monitoring system for years to track tower light status and other critical cell site conditions, even before IP connectivity was available at sites. As the network expanded, additional DPS master stations were added and a backup NOC capability supported operations during tornado warnings.
| Industry | Wireless telecommunications |
|---|---|
| Company | Sprint PCS |
| Geography / Coverage | Based in Kansas; cell sites monitored across the network (tornado-prone region referenced) |
| Primary Challenge | Monitor tower lights and cell site infrastructure reliably during buildout and growth, including readiness to operate from a backup NOC during severe weather |
| Solution Deployed | DPS Telecom master station monitoring (including T/MonXM) with expansion to additional master stations and a standby monitoring system for backup NOC operations |
| Key Result | Long-term, dependable alarm monitoring that scaled with expansion and enabled rapid return to polling/monitoring from a backup location |
| Products Used | T/MonXM |
This success story captures an interview between DPS Telecom Director of Technical Sales Eric Storm and Steve Smith of Sprint PCS. The discussion focuses on practical monitoring requirements in a fast-growing wireless buildout: tower light monitoring, generator and site security alarming, ongoing scalability, and disaster readiness in a region that experiences tornado warnings.
During early buildout, remote sites may not yet have consistent network connectivity, but operational risk is already present. Sprint PCS needed dependable visibility into key cell site conditions, including:
As expansion continued, the monitoring system also had to scale - adding additional master capacity without disrupting existing operations. Finally, because Kansas is in tornado alley, the NOC required a workable plan to maintain monitoring capability when evacuations and severe weather required moving operations to a backup location.
Sprint PCS deployed DPS Telecom monitoring and alarm master equipment, using DPS as the first monitoring system during buildout. In the interview, Smith specifically references using DPS Telecom's T/MonXM and describes adding additional DPS master stations as growth required it.
At a high level, this approach reflects a common DPS Telecom monitoring architecture: a centralized alarm master system consolidates site alarms and presents operators with clear, actionable alarm states. In many networks, the alarm master can ingest remote site points via discrete inputs (contact closures), telemetry, serial protocols, and SNMP - enabling a single view of diverse assets. For teams modernizing or expanding alarm management today, DPS Telecom recommends reviewing the current T/Mon Alarm Master solutions for centralized fault management and operator workflows.
The interview excerpts below are preserved to reflect Sprint PCS' real-world experience with DPS Telecom monitoring, including longevity, scalability, and support responsiveness.
Monitoring system in use for years
Storm: "How long have you had the DPS system?"
Smith: "It's been 4 years. DPS was the first system we've had since we started our buildout. That is, before we had network connectivity at the sites, we had towers out there and we used the DPS system primarily to monitor our tower lights but we also use DPS equipment to monitor cell site generators, doors, on-site equipment cabinets, etc."
Deploying additional DPS master stations
Storm: "Over the years you've been adding additional masters so it looks like you've been expanding quite a lot."
Smith: "Absolutely. After our first buildout, it took about 1-1/2 years, but afterward as we expanded, we realized we needed additional DPS boxes."
Tech support response
Storm: "During that time have you ever had the need for tech support?"
Smith: "Yes, absolutely. On occasion we've been assisted by John Maldonado. He's always been very helpful, courteous and always solved our problem. We were experiencing a memory fault error. We called DPS and within 2 minutes we had the problem solved, so we were very happy about that."
A backup NOC in an underground bunker
Storm: "You mentioned that you had a back up system as well. Was that part of a disaster recovery plan?"
Smith: "Absolutely. Since we are based in Kansas we are in tornado alley, so any time they issue a tornado warning, we will usually evacuate the NOC to a back up NOC, which is an underground bunker to protect the equipment from the elements. Generally, 3 or 4 times a year we will end up in the back up NOC, at which time all we have to do is fire up the system and we are ready to start polling again. In the beginning when we first brought it in, it was intended to be our transitional system, that is something to get us where we needed to be until such time as we had a permanent fault management system in place. But because it was so dependable and worked so well it stayed. I don't think there will ever be a time when we won't have DPS monitor our tower lights."
Based on the interview, Sprint PCS achieved practical, operations-focused outcomes:
The sections below summarize general engineering takeaways aligned to the themes in the interview. They are provided for readers evaluating monitoring architectures and vendor selection for long-lived telecom infrastructure.
How long a monitoring system lasts matters because replacement involves planning, cutover risk, and staff retraining. For critical infrastructure monitoring, 5 years is often treated as a minimum acceptable standard, while 10 years is a stronger target when you factor in expansion and steady-state operations.
When evaluating alarm monitoring hardware and platforms, prioritize proven build quality and serviceability (for example: durable chassis, minimal moving parts, and appropriate temperature tolerances for telecom environments). Also evaluate whether the solution is built around standards-based integration rather than fragile, proprietary dependency chains that limit future procurement options.
For organizations standardizing fault management, DPS Telecom recommends an alarm master approach that can consolidate multi-vendor site alarms and present them in a consistent operator workflow. To compare current options, start with DPS Telecom T/Mon Alarm Master.
As Sprint PCS described, growth can force monitoring teams to expand master station capacity. A practical planning guideline is to select a master station solution with meaningful excess capacity so new sites can be added without immediately forcing a forklift upgrade.
At the remote-site layer, scaling often depends on having the right fit of endpoint capacity for the job. In many telecom environments, teams use RTUs to bring discrete points (tower lights, door contacts, generator run/fail, fuel level alarms, cabinet open, HVAC alarms) into centralized monitoring. If you are modernizing remote alarming, DPS Telecom recommends reviewing the DPS Telecom RTU product line, especially those in the NetGuardian RTU family, for SNMP-centric monitoring architectures.
Remote monitoring can look simple at first: wire alarm points, define thresholds, and send notifications. In practice, high-quality monitoring requires alarm logic, escalation schedules, and clear operator displays that reduce noise while preserving critical events.
Sprint PCS highlighted the value of responsive DPS Telecom technical support when troubleshooting a reported memory fault error. For organizations deploying alarm masters and RTUs at scale, access to knowledgeable engineering support can materially reduce time-to-resolution and help keep the monitoring system aligned with operational procedures as the network evolves.
When weather or local emergencies disrupt a primary NOC, the monitoring system must support continuity of operations. Sprint PCS described evacuating to a backup NOC (an underground bunker) several times per year during tornado warnings, then bringing the system online to resume polling.
In general, a strong continuity plan includes a defined backup location, tested procedures, and monitoring software and hardware that can be brought online quickly. For teams designing new NOC architectures, DPS Telecom alarm master solutions are commonly evaluated for centralized alarm handling and clear operator workflows. See T/Mon Alarm Master for current options.
An RTU typically terminates and normalizes remote points at the site (discrete alarms, analog telemetry, and sometimes SNMP), while an alarm master centralizes alarms, applies notification/escalation, and provides operator screens for the NOC.
Many teams start with non-IP alarm transport options and direct alarming of critical points (such as tower lights), then migrate to IP/SNMP workflows as network connectivity becomes available. The key is choosing monitoring hardware that can evolve with the site.
Common points include generator run/fail and alarms, door contacts, cabinet open, high temperature, loss of HVAC, battery and power alarms, and other physical security and environmental conditions.
A backup NOC provides continuity when the primary NOC is disrupted (severe weather, facility issues, or extended power events). Having a tested procedure to resume polling and alarm handling from a secondary location reduces operational risk.
If you are building or expanding cell site monitoring, consolidating tower light alarms, or planning a backup NOC capability, DPS Telecom can help you design a practical alarm strategy with the right mix of alarm master and remote monitoring equipment.
Get a Free Consultation or call 1-800-693-0351 to speak with a DPS Telecom expert about your project.
