Difference between revisions of "Functions and demands"

Revision as of 20:25, 13 September 2017

The page contains information allowing to receive general representation about functions which OpenSCADA can carry out by the current moment. Functions are grouped on main spheres of application of OpenSCADA. For receiving a picture as a whole of functions planned or make now their are included also. The page also have demands of OpenSCADA for it building and execution.

1 The employment areas of OpenSCADA

Separating to the employment areas was made to simplify perception of the system functionality in light of traditional area for the project OpenSCADA — automation of technological processes. But also there possible mixed and specialized configuring systems for real-time data operation, for example into areas: ERP, Billing, Smart House and etc.

Fig. 1. Roles of the OpenSCADA system.

1.1 System server of SCADA

• Visual control and management by means of the interfaces:
  • Remote visualization server grounded on visualization and control area (VCA) engine VCAEngine. Module UI.Vision local starting and connecting to the visualization server.
  • Remote WEB interface. By means of a Web-browser, a visualization module WebVision and a module of the core of visual control area VCAEngine.
  • Simple remote Web-interfaces of user. By means of a Web-browser and the 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.
  • Data acquisition from automation of "Big Dutchman" company. By means of the DAQ-module BFN.
  • Data acquisition from sources DAQ-boars on buses ISA, PCI, PCMCIA and USB by means library of the project Comedi and the DAQ-module Comedi.
  • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Making by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also the transport's protocol module User Protocol. Most known protocols implementing on the Users Protocols: SMS, SMTP, Elemer TM510x, EDWARDS TURBOMOLECULAR PUMPS (SCU750), Heat counter computer VKT7, Sycon Multi Drop Protocol, Power supply for turbomolecular pumps (TMP-xx03), Temperature measurement IT-3, OWEN, IVE-452HS-02, OPTRIS CT/CTL, CTR 100-101, IEC-60870-104, I2C Chips (PCF8591, PCF8574, DS3231, AT24CXX), 1Wire Chips by adapters DS9097 and DS9097U (DS1820, DS1820/DS18S20/DS1920, DS1822, DS2413, DS2408, DS2450, DS2438), Low level devices by GPIO (DHT, 1602A), etc.
• Providing data to upper-level systems:
  • By means of interfaces:
    • Serial interface (RS232, RS485, Modem, ...), by means of the transport module Serial.
    • IP-networks sockets and network level protocols TCP, UDP and Unix, by means of the transport module Sockets.
    • Security sockets layer (SSL), by means of the transport module SSL.
  • By means of protocols:
    • Self OpenSCADA protocol, by means of transport's protocol module SelfSystem.
    • ModBUS family protocols (TCP, RTU and ASCII), by means of the transport's protocol module ModBUS.
    • "OPC-UA" protocol, by means of the transport's protocol module OPC-UA.
    • Simple special protocols, developed by users by means of the 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 of messages 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 for an 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 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.
  • PostgreSQL. By means of the DB-module PostgreSQL.
  • DBF. By means of the DB-module DBF.
  • FireBird. By means of the DB-module [Special:MyLanguage/Modules/FireBird|FireBird]].
  • Directories by LDAP. By means of the DB-module LDAP.
  • In plans. DB accessible on other server based on OpenSCADA.

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

• Visual control and management by means of the interfaces:
  • Local (fast) interface based on Qt library. By means of the visualization module Vision and the module of a core 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 core of visual control area VCAEngine.
  • Simple remote Web-interfaces of user. By means of a Web-browser and the 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.
• 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 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 an allocated archiving server, based on OpenSCADA.
• Configuration and management of a station through:
  • WEB-interface. By means of a Web-browser and the UI-module WebCfgD or WebCfg.
  • Qt-interface. By means of the UI-module QTCfg.
  • From 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 station in a DB of types:
  • MySQL. By means of the DB-module MySQL.
  • SQLite. By means of the DB-module SQLite.
  • PostgreSQL. By means of the DB-module PostgreSQL.
  • DBF. By means of the DB-module DBF.
  • FireBird. By means of the DB-module FireBird.
  • Directories by LDAP. By means of the DB-module LDAP
  • In plans. DB accessible on other server based on OpenSCADA.

1.3 Environment of execution of the controllers (PLC)

• Data acquisition (DAQ) from sources:
  • Cards of data acquisition of firm Diamond Systems. By means of the DAQ-module DiamondBoards.
  • 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 of industrial controllers under the protocol ModBus. By means of the DAQ-module [[Special:MyLanguage/Modules/ModBus|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.
  • Data acquisition from sources DAQ-boars on buses ISA, PCI, PCMCIA and USB by means library of the project Comedi and the DAQ-module Comedi.
  • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Making by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also the transport's protocol module User Protocol. Most known protocols implementing on the Users Protocols: SMS, SMTP, Elemer TM510x, EDWARDS TURBOMOLECULAR PUMPS (SCU750), Heat counter computer VKT7, Sycon Multi Drop Protocol, Power supply for turbomolecular pumps (TMP-xx03), Temperature measurement IT-3, OWEN, IVE-452HS-02, OPTRIS CT/CTL, CTR 100-101, IEC-60870-104, I2C Chips (PCF8591, PCF8574, DS3231, AT24CXX), 1Wire Chips by adapters DS9097 and DS9097U (DS1820, DS1820/DS18S20/DS1920, DS1822, DS2413, DS2408, DS2450, DS2438), Low level devices by GPIO (DHT, 1602A), etc.
• Providing data to upper-level systems:
  • By means of interfaces:
    • Serial interface (RS232, RS485, Modem, ...), by means of the transport module Serial.
    • IP-networks sockets and network level protocols TCP, UDP and Unix, by means of the transport module Sockets.
    • Security sockets layer (SSL), by means of the transport module SSL.
  • By means of protocols:
    • Self OpenSCADA protocol, by means of the transport's protocol module SelfSystem.
    • ModBUS family protocols (TCP, RTU and ASCII), by means of the transport's protocol module ModBUS.
    • "OPC-UA" protocol, by means of the transport's protocol module OPC-UA.
    • Simple special protocols, developed by users by means of the 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 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 [Special:MyLanguage/Modules/DBArch|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 core 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 [Special:MyLanguage/Modules/SelfSystem|SelfSystem]].
• Data storage PLC in a DB of types:
  • All data in a configuration file.
  • MySQL. By means of the DB-module MySQL.
  • SQLite. By means of the DB-module SQLite.
  • PostgreSQL. By means of the DB-module PostgreSQL.
  • DBF. By means of the DB-module DBF.
  • FireBird. By means of the DB-module FireBird.
  • Directories by LDAP. By means of the DB-module LDAP
  • In plans. DB accessible on other server based on OpenSCADA.

1.4 Universal OPC-UA server

Due implementation of the protocol OPC-UA into agent mode, OpenSCADA can provide a popular function of the OPC-server to client's protocols, which supports and direct implemented into OpenSCADA. The function common uses on platform MS Windows®, and many SCADA-systems on the platform work exclusively with OPC—servers, as the data sources. Thus OpenSCADA can act as an universal OPC-server on Linux platform (Fig.2).

In plans. With adapting OpenSCADA for work on MS Windows® platform and implementing work with OPC-DA by system DCOM, there will appear possibility for applying OpenSCADA into gate OPC-DA -> OPC-UA role, which means free integration of old systems to the new or accumulation systems.

Fig. 2. OpenSCADA system role as "OPC-UA Server".

The data sources and protocols, which accessible by the unified OPC-UA server:

• Industrial controllers of firm Siemens GMBH series S7, DAQ.Siemens.
• Hardware of firm ICP DAS, DAQ.ICP_DAS.
• Data acquisition boards of firm Diamond Systems, DAQ.DiamondBoards.
• Wide range of DAQ-boards Devices Object Interface (DOI) of different producers at buses ISA, PCI, PCMCIA and USB by a library of project Comedi, DAQ.Comedi.
• Wide range of industrial controllers and other data sources by protocol ModBus, DAQ.ModBus.
• Wide range of industrial controllers and other data sources by protocol DCON, DAQ.DCON.
• Wide range of data of the network hardware by protocol "Simple Network Management Protocol (SNMP)", DAQ.SNMP.
• Data sources which supports protocol OPC_UA (gating "OPC-UA") or wide range of data sources accessible for all sort OPC, by proper gate to OPC-UA, DAQ.OPC_UA.
• Wide range of industrial controllers and other data sources by protocol MMS(IEC-9506), DAQ.MMS.
• Data of other servers and PLC based at OpenSCADA, DAQ.DAQGate.
• Working into the PLC SMH 2Gi of firm Segnetics, with its DOI, DAQ.SMH2Gi.
• Automatic of poultry farming by Big Dutchman, DAQ.BFN.
• Data of commercial counting and simple resources counting with the complex enough interaction protocol, DAQ.AMRDevs.
• Sensors of platform (software-hardware) on that the server running, DAQ.System.
• Data of inputs of sound controllers of PC, DAQ.SoundCard.
• Calculated, internal or intermediate data by high level internal programming language (DAQ.JavaLikeCalc) and language of blocks schemes (DAQ.BlockCalc).
• Derivative structures of parameters-objects based at the parameter's templates and other sources data, DAQ.LogicLev.
• Data sources of different types, which have console utilities for the data access or accessible by simple specialized network protocols. Performed by writing some procedure of getting the data at the language of user-level programming (DAQ.JavaLikeCalc), and also the module of transport protocols (Protocol.UserProtocol), see the library.

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 modules allow into table 2.

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

Table 2. Dependencies of execution of OpenSCADA system and its modules.

* "opt: auto" — provides for disable of using the library at building time on it absence.

2.2 Building

Dependencies of the system OpenSCADA for OpenSCADA core and its modules building are tabulated bellow.

Table 3. Dependencies to build OpenSCADA and its modules.

* "opt: auto" — provides for disable of using the library at build time on it absence.