SCADA System WinCC Open Architecture производства Siemens

Operating system

• Windows 7 Ultimate/Enterprise (32/64-bit)
• Windows XP SP2/SP3 (32-bit)
• Windows Server 2003 (32-bit)
• Windows Server 2008 R2 (64-bit)
• Red Hat Linux 5 (32/64-bit)
• Open Suse 11.3
• Sun Solaris 10
• VMWare ESXi Server 4

PC hardware requirements ¹⁾

Processor type

Intel Pentium or equivalent

Minimum

Intel Pentium IV 1.6 GHz (or better) ^{2) 3)}

Recommended

• Client: Intel Pentium IV/Core2/i3, 2 GHz ^{2) 3)}
• Server: Intel Core i3 CPU Dual, 3 GHz ²⁾
• Server large system ⁴⁾: Intel(R) Core(TM) i5/i7 CPU Dual / Quad, 3 GHz ^{2) 3)}

RAM

Minimum

512 MB ²⁾

Recommended

• Client: 1 GB ^{2) 3)}
• Server: 2 GB ^{2) 3)}
• Server large system: 8 GB ²⁾

Hard disk
(available memory for installation)

Minimum

HD with 500 MB available ²⁾

Recommended

Server large system with local logging: SCSI LVD Controller, WIDE SCSI / LVD HDD or comparable storage system with at least 500 MB of available space ²⁾

Screen and graphics card (TrueColor)

Minimum

1024 x 768 ²⁾

Recommended

At least 1280 x 1024 ²⁾

Mouse and keyboard

3-button mouse, German keyboard

DVD drive

for software installation

Local power user rights

• for installation
• for operation

Functionality/quantity structure

Number of alarms

150,000 ²⁾

Alarm text (number of characters)

System-limited ¹⁾

Alarm log

System-limited ¹⁾

Process values per alarm

1 process value + up to 32 alarm associated values per alarm

Constant load of alarms, max.

500/s ²⁾

Message burst, max.

15,000/10 s every 5 min ²⁾

Logs

Log data points

Max. 250,000 per server ²⁾

Log types

< 20 parallel logs, different retention period for each log

Data storage format

Oracle or file system

Measured values per second, max.

Server/single-user station: 7,000/s ^{2) 3)}

User log

Logs

System-limited ¹⁾

Type

SIMATIC WinCC Open Architecture

Table size

System-limited by ORACLE database

Graphics system

Number of screens

System-limited ¹⁾

Number of objects per screen

System-limited ¹⁾

Number of controllable fields per screen

System-limited ¹⁾

PowerTags

< 750,000 per server ²⁾

User management

User accounts

< 4096

Configuration languages

2 (De, En)

Runtime languages

40 (of which 8 Asian)

Multi-user system

Server

< 2048 ^{2) 4)}

Number of clients

< 244 per server ^{2) 5)}

Event Manager (EV)

The Event Manager (EV) is the processing center in WinCC OA. This unit provides a constantly updated image of all PowerTags in the memory. Each other functional unit (Manager) that wants to access the data receives it from the process image of the Event Manager and does not have to communicate directly with a controller. Conversely, a command from an operator station is initially set only as a value change in the process image of the Event Manager. The associated driver then forwards it to the corresponding target device (e.g. PLC) automatically.
The Event Manager is a kind of central data distributor, in effect the communication center for WinCC OA. Furthermore, this Manager also carries out the alarm handling and can execute various arithmetic functions autonomously.

Driver Manager (D)

The lowest level in a WinCC OA System is represented by the process connections, referred to in WinCC OA as drivers (D). These are special programs that handle the communication with the control and field level. Since numerous and very different forms of communication are possible with the PLCs or telecontrol nodes, there are several different drivers that can be selected. In very simple terms, the driver is a unit for converting a particular protocol into the internal communication form of WinCC OA. The driver reads the current states, measurement or counter values from the field and in the opposite direction it forwards commands and setpoints to the lower-level controllers (= the term "control" should be used here and below to represent all possible devices of the basic automation (PLC, DDC, telecontrol system, etc.)).

Data Manager (DB)

The Data Manager (DB) represents the link to database. On one hand, it involves the parameterization data of an application that is to be stored in such a database. On the other hand, it involves the historical recording of changes in values or alarms. If a user wishes to query historical data at a later date, then the Data Manager completes this request and not the database itself.

Control Manager (CTRL)

WinCC OA has numerous options for implementing your own algorithms and processing. The two most important are the internal language control (CTRL) and the general application programming interface (API).
Control is an extremely powerful scripting language. The processing is interpretative, so that no compilation is required. The syntax is almost identical with ANSI-C, with some modifications for simplification. This is a fully developed, procedural high-level language with multi-threading (= quasi-parallel processing of individual programs; the system itself carries out the processing check). The language offers a comprehensive function library for tasks of the control and visualization technology. Control can be used as a stand-alone process (Control Manager), for animation and user interface design or for standardized, data object-oriented processing functions.
The API (WinCC OA API) represents the most powerful form of functional expansion. It is configured as a C++ class library and allows the software developer to implement individual functions as an independent, additional manager (forecast system, simulation, tools, proprietary databases, etc. ).

User Interface Manager (UI)

The interface to the user is created by the User Interface Manager (UI). This comprises a graphics editor (GEDI), a database editor (PARA) or the general user interface of the application (Vision module). The User Interface serves to display values, issue commands or track alarms in the alarm list. Trends and reports are also usually part of the UI. From a programming viewpoint, the user interaction in WinCC OA is completely isolated from the background processing – this is merely a view of the data of the current process image or the history.

Access to external databases

The database interfaces offer the possibility of access to external databases.
Under Windows, the link is established via the ADO Standard. ADO (ActiveX Data Objects) is an interface developed by Microsoft for vendor-independent access to data sources of all types, primarily databases. The data source for ADO is an OLE DB Provider, although ODBC-compatible databases can also be addressed via an internal wrapper.
Under Linux, the Qt library is used as an interface to relational databases. Access in this case is either direct via the native DB-API or via ODBC.

Application Programming Interface (API)

The API offers a series of functions that enable WinCC OA to be extended with special managers. A manager means a program that communicates with the system by via a protocol defined by WinCC OA.

COM (Component Object Model)

This is a specification for the development of modular software components that can be used by each COM-compatible application. COM components can easily be integrated into such applications and can even be removed from an application during runtime. COM components can be programmed in a host of different languages, even though C++ is usually used for this purpose. The specifications OLE, ActiveX and DirectX are based on the COM technology.

Control expansion

Expansion that allows C++ functions to be added to the programming language.

Panel topology/summation signal

Generation of panel hierarchies/topologies in existing or new projects and automatic creation of summation signals of the alarm data points that are located in the panels of the topology.

Redundancy
(see figure below)

The failure safety in a redundant system is implemented by means of hot standby. Hot standby is a hardware-independent solution for high availability. This is a safety concept that consists of two interconnected server systems. Both servers are constantly in operation and are subject to the same functional loading (but only one server is ever active; the second compares the data with the primary unit at runtime). On the failure of one unit, an "on-the-fly changeover" takes place and the previously passive server assumes the leading role. This guarantees access to data or functions at all times.

SMS

Allows the sending and receiving of text messages with WinCC OA.

Voice output

Offers the user a further option for obtaining interactive information relating to process states.

Encryption of panels and CTRL scripts/libraries

Allows your panels or scripts to be encrypted, thereby protecting your knowledge and work.

Distributed systems
(see the diagram below)

Permits the coupling of two or more autonomous WinCC OA systems via a network. Each subsystem of a distributed system can be configured either as a single-user or multi-user system, each of which may be redundant or non-redundant. A sub-system in this context means a server on which an Event Manager is running, whereby in case of redundancy both redundantly operating servers are considered as one system.

ETool

The engineering tool ETool offers significant benefits in engineering in the case of combined WinCC OA and SIMATIC STEP7/PCS7 projects. It provides a user-friendly engineering environment that permits easy, integrated and fast configuration on the basis of the WinCC OA mass parameterization.

BACnet

BACnet provides an integrated BACnet-compliant online/offline engineering solution for building automation technology, including object library. Designed for heating, ventilation and air-conditioning, lighting control and safety systems.

S7 AdvancedLib object library

The S7 AdvancedLib (AdvS7) is an industry-independent object library that permits the use and visualization of objects from the process control system (e.g. drives, valves, regulators, motors, etc.) in a project with WinCC OA and S7. In addition to the WinCC OA and AdvS7 license, the use of S7 AdvancedLib requires the use of the relevant library on the SIMATIC side.

Maintenance package

Includes the following functions: Operating hours counter, operating cycle counter and maintenance log.

Scheduler

Permits the creation, parameterization and management of time programs that allow the time and event-driven triggering of specific actions.

Recipes

WinCC OA recipes allow setpoints or commands for certain data point elements to be sent simultaneously. Based on "recipe types", which define the quantity of the data point elements concerned, recipes are created that send their values to the data point elements upon activation.

GIS Viewer

With the help of this viewer, standardized cards of a geo-information system (GIS) can be fully integrated in WinCC OA. Furthermore, it is possible to display all WinCC OA objects in the cards.

Excel report

Powerful report generator directly in Microsoft Excel. Templates can be created easily and directly in Excel. If a report has to be created over a defined period of time, the system accesses the template and automatically completes it with data from the WinCC OA process database. Reports can also be created, printed and saved on a time-controlled basis, without any need for user access. The Excel Report fully supports compression structures (AC - archive compression) of WinCC OA.

Communication Center

Stands for modern alarm management/remote alerting and communication using the latest standards and various media. The Communication Center creates synergies by using the various interfaces for remote alerting via the control system.
The voice output, text message and e-mail media are covered with the Communication Center.

Video
(see figure below)

Enables the integration of a video management system in WinCC OA. Through the combination of SCADA and video monitoring in one system, the costs for separate video interfaces and the additional expense of maintenance and operation can be saved, and the period of training for operating personnel can also be reduced.

HTTP server

For displaying WinCC OA data via Intranet and Web.

Authentication via Kerberos

A WinCC OA System can be exposed to a variety of attacks. An unauthorized WinCC OA System could set up a connection to the distribution manager or hackers could try to manipulate WinCC OA messages. In order to prevent espionage or other attacks, safe authentication was developed. The authentication based on Kerberos enables each WinCC OA component to verify the identity of another component. WinCC OA servers can verify the identity of the clients and clients can verify the identity of the servers. In addition, Kerberos ensures that messages are not modified during their transmission (capture-replay attacks are prevented). Furthermore, it is also possible to send messages in encrypted form.

AMS (Advanced Maintenance Suite)

For the effective planning, administration, implementation and monitoring of maintenance work and faults. The processes are evaluated by means of statistics and reports are communicated.

Disaster Recovery System
(see figure below)

This system expands the simple redundancy to include a second redundant system, to which the system can switch over in the event of a fault (e.g. fire or explosion in the building of the primary system). By means of this additional local redundancy, the highest level of system stability is obtained.

Pocket Client

A "thin client" that is also suitable for the remote access via a mobile telephone or a PDA. Access is via a Web browser without any installation and provides a user interface even at those locations whose Internet connections offer very little bandwidth, as only the most essential data is transferred.

SIMATIC S7

via TCP/IP and MPI

OPC Client (Data Access)

• Compatibility with the specifications DA 1.0 and 2.05a
• Connection to inproc, local or remote server
• Connection with up to 20 servers at the same time
• Monitoring of the connection to the server and automatic reconnection if the connection is interrupted.
• Address browsing if supported by the server.
• Benefits of the CALL-R functionality for CALL-R servers (simplified parameter assignment)

OPC Server (Data Access)

• Corresponds to Data Access 2.05a specification (reading/writing of online values).
• Is to be started as a manager just like other drivers.
• By means of data point groups, the items (DPEs) made available to other clients by the server can be defined.
• DPEs can be declared as readable (read-only access is permitted; Group OPCRead) or as writable items (Group OPCWrite).
• Clients can browse the WinCC OA OPC Server hierarchically.

OPC Alarms & Events

OPC Alarms & Events (abbreviated to OPC A&E) is, in addition to Data Access, a further standard for performing central alarm management on a cross-vendor basis. OPC A&E is used to ensure the link to other control systems and the display of alarms/events in a hierarchical system.

OPC UA (Unified Architecture)

• The OPC UA client supports the OPC UA standards Data Access and Alarms & Conditions.
• The OPC UA Server supports the OPC UA standards Data Access and Alarms & Conditions.

Modbus TCP

Modbus/TCP is based on the serial Modbus protocol, which was adapted for TCP/IP. The Modbus/TCP driver can be used simultaneously for Modbus/TCP or UNICOS.

Serial: RK512/3964R

Is used for interfacing a PLC via the 3964R/RK512 protocol

Cerberus

Cerberus is a fire, intrusion and gas alarm system. The Cerberus driver guarantees communication to and from the central fire alarm systems and building security facilities in the event a fire, gas or intruder alarm.

SSI

Is used for the interfacing of SAT remote control systems. The data is exchanged via the LAN (Ethernet, IEEE 802.3); the frame formats used are the SSI formats defined by SAT. The SK 1703 telecontrol components with a suitable communication card (KE/ET) are supported.

IEC 60870-5-101, -104

IEC drivers are standardized telecontrol drivers that can contain proprietary frames. IEC stands for International Electrotechnical Commission, the international standardization committee for electrical engineering.

• IEC 60870-5-104 for data exchange via TCP/IP
• IEC 60870-5-101 for serial connection

DNP3

The DNP3 (Distributed Network Protocol 3) driver is an open, rugged and modern protocol which exhibits characteristics and strengths similar to the IEC driver. The transfer of any number of frames with different data types takes place between the WinCC OA System (Master) and the remote stations (Slave).

SINAUT

SINAUT (SIemens Network AUTomation) is a communication protocol for automated monitoring and control of remote process stations on the basis of SIMATIC S7. Communication takes place via TCP/IP.

SNMP Manager & Agent

SNMP (Simple Network Management Protocol) is a protocol for monitoring network elements (servers, workstations, routers, switches, hubs, etc.) and their functions.

• SNMP Manager supports SNMP V1, V2, and V3
• SNMP Agent supports SNMP V1 and V2

BACnet over IP – driver

BACnet (Building Automation and Control Networks) is a standardized protocol for building automation and has been set by the ASHRAE (American Society of Heating, Refrigerating and Air-conditioning Engineers) as a guideline to provide a uniform and cross-company standard for data communication within and between building automation systems.

The BACnet Standard 2004 is supported in accordance with the PIC list (see product documentation)

Dynamic Logic – driver

The Dynamic Logic driver communicates with different Dynamic Logic devices via the "FSK outstation protocol".

Applicom General Interface

Applicom is, among other things, a manufacturer of I/O cards and software tools, with a wide range of applications in automation engineering. The Applicom products are compatible with many common fieldbus systems and communications components.

Further drivers on request or via C++ API