For power utilities managing critical infrastructure (like distant substations), a robust remote monitoring system is essential. You need accurate visibility into equipment status, environmental conditions, and security. Otherwise, operational efficiency and safety can both suffer.

I recently discussed this with a power utility engineer working on an island in the Caribbean. Together, we walked through the process of determining his monitoring needs, selecting the appropriate RTUs (Remote Terminal Units), and ensuring long-term scalability.

Here's the practical approach we worked through. You can use it to guide your own decision-making.

Step 1: Identify What You Need to Monitor

Start by listing all the key points you want to oversee. As I explained to the utility engineer:

"First, decide what you want to monitor - generator, temperature, door sensors - and then we'll add those up. The total determines which RTU you need."

To simplify this, use a survey worksheet (DPS has one, so just ask!) to capture every alarm and sensor. Consider these major categories:

• Environmental Conditions: Temperature, humidity, and leak detectors.
• Equipment Alarms: Generators, HVAC units, battery voltage and current.
• Security and Access: Door sensors, access codes, and motion detectors.

The Importance of Customized Monitoring for Your Specific Site Type(s)

Every remote site has unique requirements based on its location, function, and infrastructure. For example, in tourist-heavy regions like the one discussed during my meeting:

"If the power grid goes down, it's not just about equipment damage - it could mean a loss of tourist dollars and even safety risks."

To address this, prioritize monitoring critical systems that align with the operational goals of each site.

In general, monitoring costs so little compared to the potential threats it mitigates that you should invest as much as required. There is a limit, however.

Understanding the real risks involved will help you set a reasonable budget limit for remote monitoring and get that budget approved internally.

Addressing Environmental Challenges

During my meeting, my client next asked me about whether our RTUs can survive temperature extremes. Remote sites often face extreme environmental conditions, which can impact equipment performance.

As I explained, we test all RTU designs thoroughly:

"We test our equipment for both high and low temperatures, ensuring it can operate in boiling Texas summers or freezing Canadian winters."

Of course, a rugged RTU does no good if more sensitive equipment can't survive. For good environmental monitoring, consider including sensors for:

• Temperature and Humidity: Protect sensitive equipment from overheating or corrosion.
• Airflow Monitoring: Ensure HVAC systems are maintaining proper circulation.
• Flooding / Water on Floor: Quickly detect and respond to water leaks or pooling.

Proactively addressing these environmental factors reduces downtime and extends the life of your infrastructure.

Step 2: Translate Your Needs into I/O Requirements

Once you know what to monitor, count how many discrete and analog inputs you need. For example:

• Generator Alarms: 4 discrete inputs
• Temperature/Humidity: 2 analog inputs
• Door Sensor Monitoring: 1 discrete input

As a rule of thumb, add about 15% capacity to cover future needs. This avoids the hassle of upgrading sooner than you'd like.

"If your generator has four contact closures, you'll need four discrete inputs," I advised. "Add that to other monitoring needs, and soon you'll know your total."

In the above example, we have a total of 4+1 = 5 discrete inputs required. An RTU with perhaps 8 inputs will cover this without having so many that it becomes wasteful "overkill".

Repeat this counting process for analogs, control relays, and any similar I/O types.

Simplify Your Expansion for Easy Future Growth

One common concern with monitoring systems is scalability. I always recommend building for current needs with room to grow:

"Our RTUs allow for easy expansion. You can use modular designs like the NetGuardian DX to add more discrete or analog inputs as your network grows."

One major example is the NetGuardian DX series of expansion shelves. These let you expand monitoring capacity without overhauling the entire system. That ensures flexibility without sacrificing cost-efficiency. Planning for growth now can save significant time and resources later.

Step 3: Match the Right RTU to Your Requirements

With your I/O list now in hand, choose an RTU that can comfortably handle them. Size it correctly, but don't go overboard.

"You'll want an RTU that has close to the right capacity - maybe with 10-20% extra - but avoid one that's five times larger than necessary," I suggested.

DPS offers a range of RTUs to cover your different site sizes:

• Small Sites: NetGuardian 216 G6 (16 discretes, 6 analogs)
• Medium Sites: NetGuardian 420 G6 (20 discretes, 8 analogs)
• Large Sites: NetGuardian 864 G6 (64 discretes, 8 analogs)

Step 4: Centralize Monitoring with a Master Station

If you'll manage multiple RTUs spread across your utility's network, a master station is needed if you have more than about 10 RTUs.

The DPS T/Mon master station consolidates alarms from dozens, hundreds, or even thousands of RTUs into a single, intuitive interface.

"Our T/Mon master station can handle huge networks, displaying alarms on one screen," I noted on my call.

T/Mon's capabilities include:

• Flexible Views: See alarms as lists, maps, or dashboards.
• User Management: Assign access levels so operators see only what's relevant.
• Automated Responses: Configure actions for critical alarms. This includes sending notifications or escalating issues.

Use T/Mon for Proactive Management

The T/Mon master station is not just a centralized dashboard. It's a proactive management tool. Some of its advanced features include:

• Derived Alarms: Automate responses, such as activating backup power when thresholds are crossed.
• Customized Notifications: Configure alerts to reach the right person via email, SMS, or system dashboards.
• Historical Reporting: Generate detailed logs of alarm activity for audits and performance reviews.

As I explained during the meeting:

"You can set thresholds and even group alarms for focused views, ensuring your team can prioritize effectively."

Step 5: Partner with a Knowledgeable Manufacturer

Because monitoring is so important, working with a good partner makes all the difference. You need someone who will guide and support you during system design, installation, and ongoing use.

At DPS, we provide:

• Custom Designs: Solutions tailored to your unique requirements.
• Expert Support: Free technical support, plus training sessions on-site or online.
• Detailed Documentation: Proposals, drawings, and support materials to help justify your budget and implementation plan.
• Pre-Sale Support: Detailed information and best practices to justify the purchase internally.

As my client in the Caribbean said:

"The information you've provided, along with the support materials, will help me convince others about the value of this solution."

Ready to Build Your Monitoring System?

Remember, just follow the steps: defining what you need to monitor, translating those needs into I/O counts, choosing the right RTU, centralizing with a master station, and tapping into expert guidance.

By doing this, you'll build a monitoring network that protects your infrastructure and is adaptable to future challenges.

Contact DPS Telecom at 1-800-693-0351 or email sales@dpstele.com to discuss your project and get advice for your own situation.