EnglishРусскийУкраїнська

Functional characteristics and demands of OpenSCADA system

1. The employment area of system OpenSCADA

OpenSCADA system\'s roles (62 Кб)
Fig. 1. OpenSCADA system's roles

1.1. SCADA system's server:

  • The visual control and management by means of the interfaces:
    • Remote visualization server grounded on visualization and control area (VCA) engine VCAEngine. The module UI.Vision local starting and connecting to the visualization server.
    • Remote WEB interface. By means of a Web-browser, the visualization module WebVision and the module of a kernel of visual control area VCAEngine.
    • Simple remote Web-interfaces of user. By mean Web-browser and UI-module WebUser.
  • Data acquisition (DAQ) from sources:
    • Information about a platform (hardware-software) on which the server works. By means of the DAQ-module System.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition from controllers of firm Siemens of S7 series. By means of the DAQ-module Siemens.
    • Data acquisition of industrial controllers under the protocol ModBus. By means of the DAQ-module ModBus.
    • Data acquisition of industrial controllers under the protocol DCON. By means of the DAQ-module DCON.
    • Formation of derivative structures of parameters on the basis of templates of parameters and data from other sources. By means of the DAQ-module LogicLev.
    • Data acquisition from other servers and PLC, based on OpenSCADA, possibly for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sound controller's input channels. By means of the DAQ-module SoundCard.
    • Data acquisition from hardware of firm ICP DAS. By means of the DAQ-module ICP_DAS.
    • Data acquisition from sources which support protocol OPC_UA. By means of the DAQ-module OPC UA (RU).
    • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Made by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also transport-protocol-module User Protocol.
  • Providing data to upper-level systems:
    • By means of interfaces:
      • Serial interface (RS232, RS485, Modem, ...), by helps of transport module Serial.
      • IP-networks sockets and network levels protocols TCP, UDP and Unix, by helps of transport module Sockets.
      • Security sockets layer (SSL), by helps of transport module SSL.
    • By means of protocols:
      • Self OpenSCADA protocol, by helps of transport's protocol module SelfSystem.
      • ModBUS family protocol (TCP, RTU and ASCII), by helps of transport's protocol module ModBUS.
      • "OPC UA" protocol, by helps of transport's protocol module OPC UA (RU).
      • Simple special protocols, developed by users by helps of transport's protocol module User Protocol.
  • Implementation of user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving messages, conducting reports on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
    • In plans. On other server, it is possible to the allocated archiving server, based on OpenSCADA.
  • Archiving values of the collected data by means of mechanisms:
    • Files with double packing: consecutive and standard archiver gzip. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
  • Configuration and management of a server through:
    • The WEB-interface. By means of a Web-browser and the UI-module WebCfgD and WebCfg.
    • From the remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol SelfSystem.
  • Data storage of a server in a DB of types:
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module FireBird.
    • In plans. DB accessible on other server based on OpenSCADA.
    • In plans. DB working through ODBC.
    • In plans. PostgresSQL.
    • In plans. LDAP.


1.2. Station of the operator of technological process, the board of the dispatcher, the panel of monitoring, etc.:

  • The visual control and management by means of the interfaces:
    • The local (fast) interface based on QT library. By means of the visualization module Vision and the module of a kernel of the visual control area VCAEngine include ability of visualization from remote engine of VCA, visualization server.
    • Remote WEB interface. By means of a Web-browser, the visualization module WebVision and the module of a kernel of visual control area VCAEngine.
    • Simple remote Web-interfaces of user. By mean Web-browser and UI-module WebUser.
  • Data acquisition (DAQ) from sources:
    • Data acquisition from other servers and PLC, based on OpenSCADA, for data transportation and for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition from sources which support protocol OPC_UA. By means of the DAQ-module OPC UA (RU).
  • Implementation of the user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving messages, conducting reports on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
    • In plans. On other server, it is possible to the allocated archiving server, based on OpenSCADA.
  • Configuration and management of station through:
    • The WEB-interface. By means of a Web-browser and the UI-module WebCfgD or WebCfg.
    • The QT-interface. By means of the UI-module QTCfg.
    • From the remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol SelfSystem.
  • Data storage of station in a DB of types:
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module FireBird.
    • In plans. DB accessible on other server based on OpenSCADA.
    • In plans. DB working through ODBC.
    • In plans. PostgresSQL.
    • In plans. LDAP.


1.3. The environment of execution of controllers (PLC):

  • Data acquisition (DAQ) from sources:
    • Cards of data acquisition of firm Diamond Systems. By means of the DAQ-module DiamondBoards.
    • Information on a platform (hardware-software) on which the server works. By means of the DAQ-module System.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition of industrial controllers under the protocol ModBus. By means of the DAQ-module ModBus.
    • Data acquisition of industrial controllers under the protocol DCON. By means of the DAQ-module DCON.
    • Formation of derivative structures of parameters on the basis of templates of parameters and data from other sources. By means of the DAQ-module LogicLev.
    • Data acquisition from other servers and PLC, based on OpenSCADA, possibly for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sound controller's input channels. By means of the DAQ-module SoundCard.
    • Data acquisition from hardware of firm ICP DAS. By means of the DAQ-module ICP_DAS.
    • Data acquisition from sources which support protocol OPC_UA. By means of the DAQ-module OPC UA (RU).
    • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Made by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also transport-protocol-module User Protocol.
  • Providing data to upper-level systems:
    • By means of interfaces:
      • Serial interface (RS232, RS485, Modem, ...), by helps of transport module Serial.
      • IP-networks sockets and network levels protocols TCP, UDP and Unix, by helps of transport module Sockets.
      • Security sockets layer (SSL), by helps of transport module SSL.
    • By means of protocols:
      • Self OpenSCADA protocol, by helps of transport's protocol module SelfSystem.
      • ModBUS family protocol (TCP, RTU and ASCII), by helps of transport's protocol module ModBUS.
      • "OPC UA" protocol, by helps of transport's protocol module OPC UA (RU).
      • Simple special protocols, developed by users by helps of transport's protocol module User Protocol.
  • Management, regulation and performance of other user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving messages, conducting reports on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
    • In plans. On other server, it is possible to the allocated archiving server, based on OpenSCADA.
  • Archiving of values of the collected data by means of mechanisms:
    • Buffers in memory of the setting depth. By means of the built in archiving mechanism of the values of kernel OpenSCADA.
    • Files with double packing: consecutive and standard archiver gzip. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
  • Configuration and management PLC through:
    • The WEB-interface. By means of a Web-browser and the UI-module WebCfgD or WebCfg.
    • From the remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol SelfSystem.
  • Data storage PLC in a DB of types:
    • All data in a configuration file (fixed).
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module FireBird.
    • In plans. DB accessible on other server based on OpenSCADA.
    • In plans. DB working through ODBC.
    • In plans. PostgresSQL.
    • In plans. LDAP.

2. Requirements for OpenSCADA

2.1. Execution

The demands to apparatus for OpenSCADA system execution at different roles viewed into table 1. The demands to programs for OpenSCADA system execution and it модулеs allow into table 2.

Table 1. The demands to apparatus for OpenSCADA system and it modules.

Role

Demands

SCADA system's server

CPU: x86_32 (more than i586) or x86_64, with frequency more 500 MHz
MEM: 128 MB
HDD: 10 GB include OS and place for archives

Station of the operator of technological process, the board of the dispatcher, the panel of monitoring, etc.

CPU: x86_32 (more than i586) or x86_64, with frequency more 1 GHz
MEM: 512 MB
HDD: 4 GB include OS without archives place

The environment of execution of controllers (PLC)

CPU: x86_32 (more than i586) or x86_64, with frequency more 133 MHz
MEM: 32 MB
HDD: 32 MB include OS without archives place.


Table 2. Dependences of performance of OpenSCADA system and its modules.

Component

Description

Dependences of OpenSCADA system's kernel

OS Linux

The distribution kit of operating system Linux (ALTLinux, SuSELinux, Mandriva, ASPLinux, Fedora, Debian, Ubuntu ...)

"Standard libraries"

Standard set of libraries: linux-gate, libstdc++, libgcc_s, libc, libdl, librt, libcrypt, libm, libpthread. Certainly this already allow into installed distribution. Special demand is using native thread library NPTL, already used for all modern distributions of the Linux.

libgd

Graphic library GD version 2, it is desirable that it will be without XPM support (dependence on library of a X-server is excluded) and support of FontConfig.

libexpat

Library of XML-parser.

DB.MySQL module

libMySQL

Library for access to MySQL DBMS.

DB.SQLite module

libsqlite3

Library for access to built in DB SQLite version 3.

DB.FireBird module

FirebirdSS

FireBird DBMS version 2. Often is absent in distribution kits of Linux and demands individual loading from an official site (http://www.firebirdsql.org)!

Transport.SSL module

libssl

Library for codifying OpenSSL.

DAQ.SNMP module

libsnmp

Library for access to data of network devices under SNMP protocol.

DAQ.System module

libsensors

Hardware sensors' library versions 2 and 3.

DAQ.SoundCard module

libportaudio

Multiplatform library for access to sound controller version 19 and higher.

DAQ.OPC_UA module

libssl

Library for codifying OpenSSL.

Modules: UI.Vision, UI.WebVision, Special.FLibSYS

libfftw3

Library for fast Fourie transfer of signals.

Modules: UI.QTStarter, UI.QTCfg, UI.Vision

libQT4(libQtCore,libQtGui)

Library for construction of user graphic interface QT version 4.3 and higher.

2.2. Building

Dependences of system OpenSCADA for building of the OpenSCADA kernel and its modules are tabulated bellow.

Table 3. Dependences of building of OpenSCADA system and its modules.

Component

Description

The general requirements for building OpenSCADA

OS Linux

The distribution kit of operating system Linux (ALTLinux, SuSELinux, Mandriva, ASPLinux, Fedora, Debian, Ubuntu ...)

g++

The compiler of language C++ from a collection of compilers GCC, including library GLibC

autotools(automake, autoconf, libtool)

Tools for formation of building environment of OpenSCADA. They are necessary only in the case of changing building environment of OpenSCADA, for example for addition of the new module or change of the fixed parameters of building.

gettext

Group of utilities for preparation and compilations of translations of the interface of programs on various languages in conformity with internationalization standard I18N.

libgd(devel)

Graphic library GD version 2, a package for development, it is desirable that it will be without XPM support (dependence on library of a X-server is excluded) and support of FontConfig. It is used for construction of trends and other images in PNG format.

libexpat(devel)

Library of XML-parser, package for development. The interface of management of OpenSCADA and other components are constructed on the basis of language XML.

DB.MySQL module

libMySQL(devel)

Library for access to MySQL DBMS, a package for development on language C.

DB.SQLite module

libsqlite3(devel)

Library for access to built in DB SQLite version 3, a package for development.

DB.FireBird module

FirebirdSS

FireBird DBMS version 2, a package for development. Often is absent in distribution kits of Linux and demands individual loading from an official site (http://www.firebirdsql.org)!

Transport.SSL module

libssl(devel)

Library for codifying OpenSSL, a package for development.

DAQ.JavaLikeCalc module

bison

The program of generation of parsers on the basis of grammar of language.

DAQ.SNMP module

libsnmp(devel)

Library for access to data of network devices under SNMP protocol, a package for development.

DAQ.System module

libsensors(devel)

Hardware sensors' library versions 2 and 3, a package for development.

DAQ.Siemens module

glibc-kernheaders

Linux-kernel headers by library GLibC.

DAQ.SoundCard module

libportaudio(devel)

Multiplatform library for access to sound controller, a package for development version 19 and higher.

DAQ.OPC_UA module

libssl(devel)

Library for codifying OpenSSL, a package for development.

Modules: UI.Vision, UI.WebVision, Special.FLibSYS

libfftw3(devel)

Library for fast Fourie transfer of signals, package for development.

Modules: UI.QTStarter, UI.QTCfg, UI.Vision

libQT4(devel)

Library for construction of user graphic interface QT version 4.3 and higher, package for development.