Home

SCADA plugin overview

This SCADA plugin cannot be run without JMP software, in fact it runs "on top" of JMP just like other plugins for JMP.
The page on [JMP plugins] gives a motivation behind JMP plugins.
The main requirement for the plugin deployment is to have Java classes of both JMP software and the plugin on every machine involved in communication. SCADA plugin then must be started on every machine. The plugin checks if JMP node is running on the machine and tries to start the node if it is not running.
The downloaded .jar already contains all the classes including JMP classes.
The scheme below shows a possible set-up for the plugin.

Main features

• Data on the lower/field-level PCs are acquired from PLCs via Modbus protocol.
• If a request with proper credentials is received by a PC, it sends data "upwards" to a higher-level PC. Communication between PCs is implemented using Java RMI with custom encryption.
• SCADA polling settings and SCADA graphical output are set via a web-interface: /view page shows the output, whereas /edit page shows the settings.
• In its full (paid) version the plugin offers nested graphical output meaning a region on SCADA output can be made clickable (e.g. site 2). A click will open up a new browser tab with detailed view for the region in question.
• Due to a scalable design, site 2 on the scheme above can be added to the output on a PC in the HQ with a few clicks.
• A user interacts with the plugin (SCADA host) through a browser which makes it possible to use the plugin even from a PC where JMP node and SCADA plugin are not installed.

Quick start

The plugin can be tested even in demo version with 3 emulated signals coming from 2 emulated PLCs. [Example] page describes how to set-up the system for the test. See [SCADA output] for an explanation how to set-up a graphical output.