DNP3 Tutorial Part 6: 8 Important Considerations In DNP3 SCADA Systems

Using DNP3 in a contemporary SCADA system is an easy decision. DNP3 is a standard protocol that has wide acceptance in the industry and is flexible enough for almost any application. DNP3 certainly has its place in an effective monitoring solution, but this doesn't mean that any off-the-shelf DNP3 Master or Remote will be a best fit for you.

Before you commit to an SCADA monitoring solution for either your operating center or your remote sites, you need to consider a multitude of factors.

Before you buy, check for these 8 important features:

  1. Masters should provide concise alarm information
    Masters sometimes present data in such an attractive, graphical interface that you can't see the forest for the trees. Make sure that you have access to a list view that provides a good presentation of event and alarm detail for more than a single site or region. Sometimes, summary graphical presentation can make detail an inconvenient click or two away when a decision needs to be made.
  2. Masters should be able to identify cleared alarms
    If you will be relying on Unsolicited Messages in your system, make sure there is a clear event for each alarm. Creating this association can involve expensive custom development on your Master system.
  3. Masters should maintain a history of standing alarms
    Avoid the allure of maintaining only an event log of newly reported Unsolicited Messages and a history log of acknowledged Unsolicited Messages. If an Unsolicited Message represents an alarm condition, there should be continuing visibility to the alarm even if the Unsolicited Message is acknowledged. Imagine what might happen to your network if a system operator acknowledges an alarm message, and then, for whatever reason, fails to correct the alarm condition. Who would know the alarm is still standing?
  4. Remotes should support redundant power
    If your remote is powered from a single source, then your critical monitoring is vulnerable to a single event. Losing that single source of power effectively compromises the continuous monitoring of your revenue generating equipment. If your installation does not have dual power sources, make sure the equipment is compatible with an external uninterruptable power supply. Also insure that the primary power is one of the points monitored at each location.
  5. Remotes should provide local SCADA
    If a network failure compromises the collection of data, your remote equipment should provide for local visibility. Turn the worst case of having to dispatch techs to critical remote sites into a much better case by insuring that they will be able to browse to your remote units and have local SCADA until the network is restored.
  6. Masters should sort and filter alarms
    Masters should support organizing alarms by a wide variety of characteristics. Location, equipment type and severity are just a few possibilities that may make sense for organizing your alarms. The same alarm should be able to be posted to multiple categories. The presentation of sorted and filtered alarms should depend on the user logged on; the team responsible for generator maintenance doesn't need to wade through lists looking for generator events and alarms.
  7. Masters should support flexible and powerful notification
    Make sure your master support the advanced features necessary for premium status monitoring, such as notification escalation, nuisance alarm silencing, automatic control relay operation, and automatic notifications by e-mail, text or pager.
  8. Masters should not be limited to DNP3
    If you're like most companies, you have a variety of equipment of different ages and technologies. Integrating this diversity into a SCADA Master can sometimes involve surprisingly expensive customization or additional modules.

    It is always difficult and uncomfortable to justify significant development costs after purchasing an already expensive SCADA Master. Why take the time, trouble, and expense to recreate capabilities that are already present in a high-quality, multi-protocol Master that is DNP3-capable?

DNP3 Tutorial: What to Do Next

Before you make a decision about your SCADA DNP3 monitoring, there's a lot more you need to know. There are dangers you want to avoid - and there are also opportunities to improve your remote site maintenance that you don't want to miss.

DPS Telecom Guarantees Your Success - or Your Money Back

When you're choosing a network monitoring vendor, don't take chances. Be skeptical. Ask the hard questions. Above all, look for experience. Don't take a sales rep's word that his company can do custom development. Ask how many systems they've worked with, how many protocols they can integrate with DNP3, and check for client testimonials. DPS Telecom has created hundreds of successful monitoring implementations for telecoms, utilities, and transportation companies. (Check out for some examples.) DPS Telecom monitoring solutions are proven performers under real-world conditions. You're never taking any risk when you work with DPS Telecom. Your SCADA monitoring solution is backed by a 30-day, no-risk, money-back guarantee. Test your DPS monitoring solution at your site for 30 days. If you're dissatisfied for any reason, just send it back for a full refund.

Get the information you need. Send an e-mail to for "A Practical, Step-by-Step Guide" on how to implement SCADA monitoring in your network. You can also call us today at 1-800-622-3314 to schedule your free Web demo of SCADA monitoring solutions, or register on the Web at