4940

Get a Live Demo

You need to see DPS gear in action. Get a live demo with our engineers.

Get the Alarm Fundamentals White Paper

Download our free Monitoring Fundamentals Tutorial.

An introduction to Monitoring Fundamentals strictly from the perspective of telecom network alarm management.

DPS is here to help.

1-800-693-0351

Have a specific question? Ask our team of expert engineers and get a specific answer!

Learn the Easy Way

Sign up for the next DPS Factory Training!

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 Today

How NJ Transit Improved Visibility at Unmanned Rail Sites Using DPS Remote Monitoring

NJ Transit, New Jersey's public transportation corporation, needed dependable alarm visibility across many unmanned rail locations where legacy monitoring could not provide enough detail. By deploying DPS Telecom remote alarm monitoring (NetGuardian remotes and KDAs) with a T/Mon NOC master station, NJ Transit improved near-real-time notifications, centralized alarm visibility, and response coordination for network- and service-affecting issues.


Quick Facts

Industry Public transportation (bus, rail, and light-rail transit)
Company NJ Transit (New Jersey public transportation corporation)
Geography/Coverage New Jersey with links to major points in New Jersey, New York, and Philadelphia
Operational Context Nearly 223 million passenger trips each year on 236 bus routes and 11 rail lines statewide
Primary Challenge Legacy monitoring delivered limited visibility and incomplete alarm detail for unmanned remote locations supporting critical rail communications and SCADA gear
Solution Deployed Distributed alarm collection at remote sites with centralized alarm management and technician notifications
Key Result Improved visibility of field equipment and faster response and repair enabled by detailed alarms and escalation notifications
Products Used T/Mon NOC, NetGuardian 832A, NetGuardian 216, NetGuardian 216T, KDA

Client Overview

NJ Transit is the United States' third largest provider of bus, rail, and light-rail transit. The organization operates at a scale where service reliability depends on continuous awareness of what is happening at field locations, including towers, communications shelters, and rail infrastructure sites that are not staffed around the clock.

"As a transit service provider, we have a lot of unmanned locations. We need to have visibility of all our field equipment."


The Challenge

Nine years ago, at the onset of a new millennium, NJ Transit was at a crossroads. Up to that point, NJ Transit relied on a legacy monitoring system that came with one rail line. As Tom Cantwell, Manager of Radio Systems at NJ Transit, explained: "This system came with one of our rail lines. At that time, it was the only transit line that we had monitoring on."

Critical transit equipment called for more than just "basic" monitoring...

With an embedded, aging monitoring system in place, Cantwell did not have access to complete and detailed alarm information from devices at remote sites. NJ Transit's railroad lines carry mission-critical circuits, including SCADA gear, and the organization needed a more reliable approach than what their legacy system could provide.

From an engineering perspective, rail operations often depend on distributed electronics that must be monitored continuously: communications transport, power, site security, environmental conditions, and specialized compliance equipment. When those systems are spread across unmanned sites, the monitoring system must do two things well:

  • Collect accurate alarms at the edge (from discrete contacts, site controllers, and networked devices).
  • Deliver actionable notifications with enough detail for technicians to triage issues quickly.
Diagram showing T/Mon collecting alarms from KDAs and NetGuardian remotes and sending notifications to technicians.
T/Mon collects alarms from KDAs and NetGuardians at remote sites and sends email notifications to technicians, maximizing visibility of network-affecting issues.

The Solution

DPS Telecom provides NJ Transit with a solution for their unmonitored, unmanned sites...

While evaluating monitoring options, NJ Transit expected high costs and compatibility issues. They needed a monitoring solution that could be deployed broadly at remote, unmanned locations while still integrating alarm information into a centralized view.

"We first hooked up with DPS in 2000," said Cantwell. "We deployed a new DPS system in over 20 locations. Now we have over 50 unmanned locations supported by DPS monitoring equipment."

At a high level, the DPS Telecom architecture used by NJ Transit aligns to a standard best practice for distributed monitoring:

  • Remote site collectors (NetGuardian remotes and KDAs) gather local alarm points and, where applicable, device status for transport back to the center.
  • Central alarm management (T/Mon NOC) correlates alarms and drives notifications so the right people are alerted when issues occur and persist.

"We like to know when T1 are taking hits. We can take a look and repair that before we lose any service going over the T1 lines...,"

NJ Transit discovered DPS equipment that offered near-real-time notifications and detailed alarm data. For example, NJ Transit has two microwave towers with FAA-required lighting. "The KDAs monitor the lights for us," said Cantwell. "They give us real-time information if the lights go on at night and turn off in the day or if a light bulb burns out."

For organizations with similar operational profiles, DPS Telecom remote site monitoring is commonly used to:

  • Convert discrete inputs (open/closed contacts from relays, door switches, power alarms, and other dry contacts) into actionable alarms.
  • Provide centralized alarm notification (email/paging/escalation workflows) when alarms are not acknowledged.
  • Support proactive maintenance by identifying recurring issues before they become outages.

Implementation

NJ Transit deployed 20 KDAs and 20 NetGuardian 832As at various remote sites to improve visibility of transit equipment. They also deployed NetGuardian 216 remotes, which were described as a better fit for some smaller sites.

At locations with T1 service, the NetGuardian 216T proved especially effective. Cantwell explained: "A number of our rail lines have T1 equipment. We like to know when T1 are taking hits, so we can repair that before we lose any service going over T1."

In practice, this kind of deployment enables a field-oriented monitoring approach: install alarm collection at the remote site (power, environmental, transport, lighting, and other critical points), then use a central alarm master to normalize incoming alarms and drive notifications across technicians, supervisors, and management based on acknowledgment rules.


Central Monitoring Upgrade: T/Mon NOC

T/Mon upgrade allows for quicker response time...

NJ Transit improved not only their fleet of alarm remotes, but also their central office monitoring. "Our biggest recent improvement was upgrading our T/Mon," said Cantwell. "Our original T/Mon was installed in 1999, and in 2007 we upgraded to the new T/Mon with dual power supply and backup redundant hard drives."

"The new T/Mon.... it's like going from a Model T up to a Porsche. It's a huge improvement..."

One way Cantwell uses T/Mon at their central office is as a paging system for technicians. With improvements in the newer T/Mon, he no longer worries about missing alarms. "If people in the office don't acknowledge an alarm within a certain length of time, it will notify everybody out in the field - management, supervisors, technicians - to know what's happening in their areas," Cantwell said.

Cantwell highlighted the benefit of LAN connectivity: "The new T/Mon has LAN connection, which allows us to do a lot more." Since upgrading to the T/Mon NOC, Cantwell experienced quicker response and repair time with the help of fast, reliable alarm notification and detailed alarm data. "Response time is a lot better," said Cantwell. "It's easier to service."

He was also enthusiastic about future applications of T/Mon: "In the future, we are looking to take the T/Mon's email functionality and tie it into the company's email system. This would provide notification to all our techs as needed."


Results

  • Expanded monitoring coverage across unmanned sites: NJ Transit grew from limited monitoring on a single rail line to supporting more than 50 unmanned locations with DPS monitoring equipment.
  • Better visibility into field equipment: Detailed alarm data from remote sites gave technicians and operations staff clearer awareness of network- and service-affecting conditions.
  • Earlier awareness of transport degradation: Monitoring for T1 "hits" helped NJ Transit address issues before losing service over T1 lines.
  • Improved response and repair: After the T/Mon NOC upgrade, NJ Transit reported quicker response and easier servicing enabled by reliable alarm notification and escalation.

Key Takeaways

  • Unmanned sites require edge collection plus central escalation: Distributed remotes like NetGuardian devices can capture alarms locally, while T/Mon provides the central workflow for notification, acknowledgment, and escalation.
  • Compliance and safety monitoring belongs in the same alarm view: FAA-required tower lighting monitoring via KDA devices can be integrated into the same operational monitoring strategy as communications and SCADA support equipment.
  • Modernizing the alarm master can be as important as modernizing remotes: Upgrading T/Mon (with redundancy and improved connectivity) supported more consistent alarm handling and better technician response.

Products Used in This Solution

  • T/Mon NOC - Central alarm management for collecting alarms from remote sites and driving notifications and escalation workflows. See T/Mon alarm monitoring.
  • NetGuardian 832A - Remote telemetry unit (RTU) for collecting and reporting alarms from field sites. See NetGuardian 832A and the NetGuardian RTU family.
  • NetGuardian 216 and NetGuardian 216T - Compact remotes used at smaller sites, including sites with T1 monitoring needs. See the NetGuardian RTU family.
  • KDA - Remote alarm monitoring device used to monitor FAA-required tower lighting status (on/off and lamp failure conditions).

Industry & Challenge FAQ

Why is remote alarm monitoring critical for rail and transit systems?

Rail and transit operations depend on distributed field infrastructure and communications. When sites are unmanned, a centralized alarm system is the practical way to detect issues early and coordinate response before service is affected.

What is the role of a NetGuardian remote at an unmanned site?

A NetGuardian remote functions as an RTU that collects local alarm points (often discrete contact closures) and forwards alarms to central monitoring. This supports consistent visibility across many remote locations.

How does a T/Mon NOC help reduce missed alarms?

T/Mon NOC can drive notification and escalation when alarms are not acknowledged in a defined period, helping ensure that persistent issues are seen by technicians, supervisors, and management.

What does it mean to monitor when a T1 is "taking hits"?

In this context, technicians want early warning that a T1 circuit is being impacted (errors or intermittent issues) so repairs can be made before service carried over the T1 is lost.

Can tower lighting alarms be monitored alongside communications alarms?

Yes. NJ Transit used KDAs to monitor FAA-required lighting. This type of compliance monitoring can be handled as part of the same alarm workflow used for other site equipment.


Talk to DPS Telecom

If you support unmanned transit, rail, or critical infrastructure sites and need centralized visibility with escalation, DPS Telecom can help you build a monitoring approach using NetGuardian remotes and T/Mon alarm management. Get a Free Consultation or call 1-800-693-0351 to speak with an expert about your project.