• We Are Professional Because We Are Dedicated
  • Overall Solutions Of Automation And Energy Efficiency
  • Practitioner Of The Industry IT
  • Focus On Technology Innovation In Industry
  • Remarkable And Guaranteed Performance
  • Industrial Automation Training
  • We Are Professional Because We Are Dedicated
  • Overall Solutions Of Automation And Energy Efficiency
  • Practitioner Of The Industry IT
  • Focus On Technology Innovation In Industry
  • Remarkable And Guaranteed Performance
  • Industrial Automation Training

Home

Products & Systems > SCADA Systems > PVSS > SIMATIC WinCC Open Architecture >

MOORE

INDUSTRIALAUTOMATION

[ Favorite ]
[ Print ]

SIMATIC WinCC Open Architecture

POSTTIME: 2012-09-10 04:31




SIMATIC WinCC Open Architecture is a SCADA system for visualizing and operating processes, production flows, machines and plants in all industrial sectors.

Distributed systems enable the connection of up to 2048 autonomous SIMATIC WinCC Open Architecture systems via one network. Each subsystem can be configured either as single-user or multi-user system, each of which may be redundant or non-redundant.

SIMATIC WinCC Open Architecture relies throughout on object orientation in the case of process screens and the database structure. By means of the object-oriented properties and their consistent and considered use, the engineering process of SIMATIC WinCC Open Architecture customers changes. This means that high engineering cost savings can be achieved.

  • Current version: SIMATIC WinCC Open Architecture V3.11
    Runs on:
    • Windows 7 Ultimate/Enterprise SP1 (32/64-bit)
    • Windows XP SP2/SP3 (32-bit)
    • Windows Server 2008 R2 (64-bit)
    • Red Hat Linux 5 (32/64-bit)
    • Open Suse 12.1 (32/64-bit)
    • Sun Solaris 10
    • VMWare ESXi Server 4


    • Efficient engineering and flexible plant expansion
      • Object orientation
      • Unlimited number of data points
      • Mass engineering
      • Multilingual with UTF-8 support
    • Object-oriented data model
      • Mapping of setpoint values and measured values for a physical plant object onto a structured data point
      • Data point comprises a tree structure with data point elements
      • The individual process values are mapped onto the data point elements
      • Any number of data points can be instanced from one defined data point structure (data point type), e.g. 20 pumps of the same type.
      • Data point types can be embedded in other data point types, which enables more complex plant objects to be generated (e.g. one pump station comprises 2 pumps).
      • Graphical plant symbols can reference a data point of a specific type, in which case they only need to be drawn once, but can be used for all instances of the type.
      • Savings in engineering outlay.
    • Freely scalable
      • From a small single-user system up to a networked, redundant high-end system
      • Distributed systems of up to 2048 servers
    • Platform-independent
      • Available for Windows, Linux and Solaris
    • Native 64-bit support
      • More system memory is usable, due to native 64-bit support
      • This means that larger data quantity structures per server can be processed
    • Maximum fail-safety and availability
      • Hot standby redundancy
      • Disaster recovery system
      • SIL3 certification according to IEC 61508
    • Platform for customized solutions
      • Quick and easy implementation of new processes
      • Swift adaptation of the control and visualization of the plant to current market requirements
      • Company-internal programming and in-house developments enable independence and protection of intellectual property
      • Structure of standardized solutions permits continuous use
      • Support of brand-labeling
      • Individual brand names for OEM developments
    • Openness thanks to comprehensive driver and interface options:
      • Modbus serial, Modbus Plus / RS485, RK512, TLS, Teleperm M, SSI driver, IEC 60870-5-101, -104, DNP3, SINAUT, PROFIBUS DP, PROFIBUS S7 + MPI, S7 TCP/IP, Modbus TCP/IP, Ethernet/IP, OPC DA Client & Server, OPC A&E Client & Server, OPC UA Client & Server (DA, AC), SNMP, BACnet, API, Cerberus
    • Seamless traceability of system states by means of high-performance archiving:
      • Data archiving in value archives (internal database format)
      • Data archiving in an Oracle database
    • Expandable by means of options and solution frameworks:
      • Options for quick and easy engineering
      • Options for increasing the availability
      • Options for clarity in distributed systems
      • Options for efficient maintenance management
      • Options for mobile operability
      • Options for efficient building automation technology
      • Framework for the integration of video management



The SCADA system SIMATIC WinCC Open Architecture addresses applications with high demand for customer-specific adaptations, large and/or complex applications, as well as projects that demand special system requirements and functions.

SIMATIC WinCC Open Architecture demonstrates its high performance in networked and redundant high-end control systems in particular. From the field level to the control station, from the machine to the company headquarters – integrated, high-performance communication is guaranteed. In every situation, a high level of availability, reliable information, fast interaction and user friendliness are guaranteed. Applications can also be changed without interrupting the process. Profitability, efficiency and safety are therefore always in equilibrium. SIMATIC WinCC Open Architecture displays its reliability in a wide range of business-critical applications.

With SIMATIC WinCC Open Architecture, ideas can be quickly and easily converted into new applications. SIMATIC WinCC Open Architecture is open for independent in-house developments and also enables own product branding.

Thanks to its special system properties, SIMATIC WinCC Open Architecture meets the highest demands especially in the case of traffic solutions, building management systems and supply systems (power, water, oil and gas, etc.).




SIMATIC WinCC Open Architecture is available as a single-user runtime license, multi-user runtime license, Web Client license, and parameterization and development license. With SIMATIC WinCC Open Architecture the required license is determined, among other things, according to the number of inputs and outputs (I/O).

An "I/O" refers to a data point element (DPE) whose content is exchanged either by means of drivers (e.g. S7 driver communicates with a PLC), with other SIMATIC WinCC Open Architecture servers (distributed systems), or with other software systems. Internal data point elements, i.e. DPEs without communication to the outside, are not counted for the licensing. The licenses are available either with unlimited number of I/Os or with limitations of 300 I/Os, 1000 I/Os, 5000 I/Os or 100000 I/Os.

A multi-user license can be installed on several PCs – only the number of simultaneously active clients is counted The Web Client enables the visualization and operation of process pictures over an exclusively HTTP connection between the server and the web client. The parameterization and development licenses extend a runtime license with the option of configuration and parameterization. They each require a server license.




SIMATIC WinCC Open Architecture is a very modular SCADA system. The required functionalities are realized by specific, functional entities created for various tasks. In SIMATIC WinCC Open Architecture these units are called "Managers" - they are also distinct processes in software terms.

WinCC OA Manager

Task

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.



A WinCC OA System consists of function-specific units, the managers

For special tasks such as redundancy, management for distributed systems, web server, reporting, simulation, COM etc., further managers are available.

The powerful configuration functions contribute to a reduction of engineering and training overheads and lead to increased flexibility and operational reliability.


Special functions

Task

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.
In 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.

Encryption of panels and CTRL scripts/libraries

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

Script Wizard

Easy-to-use tool that simplifies the creation of animated, graphical plant symbols, which saves time during engineering.

Simple Symbols

Basic package of plant symbols that have been created using the script wizard. These can be adapted quickly and easily to the specific requirements of the customer.

Easy Faceplates

Simple parameter assignment of predefined pop-up windows that display details of the associated plant symbol. Without any additional drawing outlay, several standard functions per object can be activated for the detail view (alarm display, trend display, measured value table, setpoint value table, address table, notes).

Drag and Draw

Several representative graphical objects can be defined and configured for each plant object in the data model (data point type). These are pre-configured and need only be moved to the panel via drag-and-drop when the plant pictures are drawn. This saves valuable time during engineering.

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.



The diagram shows a detailed representation of the two computers Server 1 and Server 2. Server 1 is in the management mode (active) and Server 2 is in hot standby mode (passive).
In the case of redundant operation, the UIs of both operator stations are connected to both Event Managers, however only the data of the active system is displayed on both UIs. The Event Manager of the passive system is restricted exclusively to communication with the Event Manager of the active system for comparison of the process data (it sends no data to the connected UIs or it discards messages from the drivers – this can be seen in the figure with the switches on the UIs or on the passive Event Manager).



Distributed systems with WinCC OA

Add-ons

Task

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.
Text message and email 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.

Ultralight Client

A "thin client" that supports access to the plant via a mobile device (such as a mobile telephone or tablet) in addition to a PC workstation. Access is possible via a standard Web browser using native Web technologies (Javascript, SVG) without the need for any additional installations. It provides a user interface even at those locations with Internet connections offering very low bandwidth, as only the most essential data is transferred.

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.



Network topology Video



Integration in automation solutions

SIMATIC WinCC Open Architecture is an open SCADA system with comprehensive drivers and flexible options for connection to other external systems.

Depending on the communications protocol and the bus physics used, specific drivers are used in each case:

  • Serial protocols: RK512, 3964R, etc.
  • Ethernet: Industrial Ethernet (S7), Modbus TCP (OpenModbus), Ethernet IP (AB), etc.
  • Telecontrol systems: SINAUT, SSI (Ethernet), IEC 60870-5-101, IEC 60870-5-104, etc.
  • Vendor-independent interfaces: OPC UA, etc.

In SIMATIC WinCC Open Architecture, several drivers can be operated in parallel. These can be of the same type or also of different types. It is possible in a SIMATIC WinCC Open Architecture system to establish connections via the S7 protocol to a SIMATIC controller, via IEC 60870-5-104 to a telecontrol system, and via OPC DA to any OPC server at the same time.






Other Product:

SIMATIC WinCC Open ArchitectureSIMATIC WinCC Open