Sensus SCADA-Xchange™ Interface

Overview Solutions Documentation & Tools
Overview

A Powerful Interface for SCADA Systems

Our SCADA-Xchange™ interface offers an economical way to integrate control and data acquisition functionality into an existing SCADA system or Energy Management System (EMS). It allows a SCADA system to poll data from any of our automation devices as if it were connected directly to your customer’s system.

To a SCADA system, the SCADA-Xchange interface appears as a Front End Processor (FEP) or remote concentrator Remote Telemetry Unit (RTU), with multiple RTUs or Intelligent Electronic Devices (IEDs) behind it. The customer SCADA system polls the SCADA-Xchange server to receive data from the various devices. SCADA-Xchange delivers data from our field devices in DNP3 protocol to your SCADA system over a secure TCP/IP connection. When a change is detected, the event is reported like any other alarm on SCADA.

For outgoing communication, SCADA-Xchange interprets control commands and report requests from the utility’s SCADA system. Then it transfers these messages through  the AutomationControl™ software application to field units using the FlexNet® communication network or cellular networks. These commands are executed like any other message sent to an RTU. Commands include report requests and control commands.

Benefits to you

  • Saves on bandwidth by offering flexible control over the polling model and the amount and type of data polled
  • Provides two-way communication over the FlexNet network or cellular data networks
  • Cost-effectively extends SCADA to distribution assets
  • Communicates through a secure, dedicated MPLS connection or Virtual Private Network (VPN) connection
  • Requires no SCADA protocol development or special interfaces
  • Allows a SCADA system to poll one location to receive data from multiple devices

SCADAbodyimage.jpg

Product Features
  • Three reporting methods: unsolicited or report-by-exception, time scheduled reports, and direct commands or queries
  • Standard DNP3 protocol over TCP/IP or serial
  • Communication to and from field devices can only be initiated and received by the Sensus DA Network Operations Center (NOC)
  • Supports 256-bit SSL encryption
  • Converters are available to support other SCADA protocols

 

Specifications

  • The Sensus DA NOC is supported by a redundant OC48/OC12 connection to the Internet backbone, and the facility maintains a Cisco Seal of Approval, secured card access, security cameras, a fire suppression system and a backup generator.
  • All AutomationControl™ servers and all SCADA-Xchange transactions are protected by hardware and software firewalls. Servers are maintained with the latest security updates and regularly scanned for any security vulnerabilities.
  • AutomationControl servers support 256-bit SSL encryption. Each Web session is secured with a new 256-bit encryption key.
  • Several options to enhance the security of SCADA-Xchange. These options include: a MPLS, VPN, SSL connection and various encryption options

Alternative Protocols

  • Protocol converters are available to support SCADA protocols other than DNP. Since most alternate protocols are based on an RS-232 physical link, the protocol converter will normally be located at the utility’s SCADA facility near the RS-232 ports used for RTU communications.
  • In a typical configuration, the SCADA-Xchange interface will use DNP-TCP/IP to communicate with an RCOM protocol converter from Applied Systems Engineering (ASE) running on a Windows-compatible computer. RCOM translates from DNP to most RTU/IED protocol. Using the standard 8-channel interface, SCADA-Xchange can communicate with multiple systems that may use the same or different protocols.

For more information about this product, please download the data sheet.

Documentation & Tools

Documentation & Tools