System Ueber Sich t

WinCC System Overview ___________________
System Overview 1
2
___________________
SIMATIC WinCC
Application and configuration

___________________
possibilities 3
SIMATIC HMI
4
___________________
How WinCC Works
WinCC V7.0 SP3

WinCC System Overview ___________________
Configuring with WinCC 5
Printout of the Online Help
12/2011
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the relevant information is not taken into account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG Printout of the Online Help Copyright © Siemens AG 2011.

Industry Sector Ⓟ12/2011 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 System Overview....................................................................................................................................... 5
2 SIMATIC WinCC........................................................................................................................................ 7
3 Application and configuration possibilities.................................................................................................. 9
3.1 Positioning in the HMI environment ...............................................................................................9
3.2 System Components....................................................................................................................10
3.3 Integration into the SIMATIC Environment ..................................................................................14
3.4 Integration into Corporate IT Solutions ........................................................................................16
3.5 Openness.....................................................................................................................................17
3.6 Licensing ......................................................................................................................................20
3.7 Typical configurations ..................................................................................................................21
3.7.1 Typical configurations ..................................................................................................................21
3.7.2 Single-User System .....................................................................................................................22
3.7.3 Multi-User System........................................................................................................................23
3.7.4 Distributed System.......................................................................................................................25
3.7.5 Central Archive Server (WinCC CAS) .........................................................................................27
3.7.6 Long-term archive server .............................................................................................................28
3.7.7 Redundant Systems.....................................................................................................................29
3.7.8 Web Client System ......................................................................................................................31
4 How WinCC Works .................................................................................................................................. 33
4.1 How WinCC Works ......................................................................................................................33
4.2 Graphics System..........................................................................................................................35
4.3 Alarm Logging ..............................................................................................................................38
4.4 Archiving System .........................................................................................................................41
4.5 Report System .............................................................................................................................44
4.6 Communication ............................................................................................................................47
4.7 WinCC Function Chart .................................................................................................................51
5 Configuring with WinCC........................................................................................................................... 53
5.1 Configuring with WinCC...............................................................................................................53
5.2 Setting Up and Administering Projects ........................................................................................56
5.3 Visualizing Processes ..................................................................................................................58
5.4 Reacting on Input.........................................................................................................................61
5.5 Accessing Process Values...........................................................................................................63
5.6 Showing Current Process Values ................................................................................................65
5.7 Archiving Process Values ............................................................................................................67
WinCC System Overview

12/2011, Printout of the Online Help 3
Table of contents
5.8 Visualizing Process Value Developments................................................................................... 69

5.9 Creating and Archiving Messages .............................................................................................. 71
5.10 Documenting Processes and Events .......................................................................................... 74
5.11 Preventing Unauthorized Operation............................................................................................ 76
5.12 Setting Up Multilingual Projects .................................................................................................. 78
5.13 Running and Testing Projects ..................................................................................................... 81
5.14 Guide Through Your Projects ..................................................................................................... 84
Index........................................................................................................................................................ 87

4 12/2011, Printout of the Online Help
System Overview 1
Content
This System Overview will help you to come to terms with SIMATIC WinCC and to gain an
understanding of the basic system logic. The following questions will be answered in the
System Overview:
● How can SIMATIC WinCC be meaningfully integrated into your automation solutions?
Which automation tasks can be executed using SIMATIC WinCC?
● Which components of SIMATIC WinCC handle which tasks? How do the individual
components work together?
● Which Editors are used to carry out which configuration tasks?
● In which order should a configuration be executed?

System Overview

SIMATIC WinCC 2
What is WinCC?
WinCC is a powerful HMI system for use under Microsoft Windows 2000 and Windows XP.
HMI stands for "Human Machine Interface", i.e. the interface between the person (the
operator) and the machine (the process). The automation process (AS) retains actual control
over the process. Communication is effected between the WinCC and the operator on the
one hand and WinCC and the automation systems on the other.
WinCC is used to visualize the process and develop the graphic user interface for the
operator.
● WinCC allows the operator to observe the process. The process is displayed graphically
on the screen. The display is updated each time a status in the process changes.
● WinCC allows the operator to control the process. He can, for example, predefine a
setpoint or open a valve from the graphic user interface.
● An alarm will automatically signal in the event of a critical process status. If, for example,
a predefined limit value is exceeded, a message will appear on the screen.
● When working with WinCC, process values can either be printed or electronically
archived. This facilitates the documentation of the process and allows subsequent access
to past production data.

SIMATIC WinCC
The Distinguishing Features of WinCC

WinCC can be optimally integrated into your automation and IT solutions:
● Being a part of the Siemens TIA concept (Totally Integrated Automation), WinCC works
very efficiently with automation systems that belong to the SIMATIC product family.
Automation systems from other producers are also supported.
● WinCC data can be exchanged with other IT solutions through standardized interfaces,
such as with MES and ERP-level applications (a SAP system for example) or with
programs such as Microsoft Excel.
● The open WinCC programming interfaces allow you to connect your own programs and
you will therefore be able to control the process and process data.
● WinCC can be optimally customized to meet the requirements of your process. An
extensive range of configuration possibilities is supported. from single-user systems and
client-server systems right up to redundant, distributed systems with several servers.
● Your WinCC configuration can be modified at any time – even subsequently. This will not
interfere with existing projects.
● WinCC is an Internet-compatible HMI system which facilitates the implementation of web-
based client solutions as well as Thin-client solutions.

Application and configuration possibilities 3
3.1 Positioning in the HMI environment
Different Specifications
SIMATIC-HMI systems are visualization systems. The different products differ with respect to
functionality, performance, hardware platform and openness.
Simple SIMATIC-HMI systems take the form of small key-operated or text-based panels.
These are at the bottom end of the HMI product spectrum. SIMATIC WinCC, on the other
hand, is a high-end visualization system.

Application and configuration possibilities
3.2 System Components
System Structure
WinCC has a modular construction. It consists of the basic WinCC system and can be
supplemented with WinCC options and WinCC add-ons.
WinCC Basis System

The basic WinCC system consists of the following subsystems:
● Graphics System
● Alarm Logging
● Archiving System
● Report system
● Communication
● User Administration
The basic WinCC system consists of Configuration Software (CS) and Runtime Software
(RT):
● You use the Configuration software to create your project.
● The Runtime software is used to execute the project while processing. The project is then
"in runtime".
WinCC Options
WinCC options allow you to extend the functionality of the basic WinCC system. A special
license is required for each option.

Options for scalable configurations
WinCC/Server
Allows a multi-user solution with up to 32 clients which receive data, messages, and pictures
by means of TCP/IP directly from the server. In a distributed system, the application can be
distributed from a functional viewpoint or according to system areas to up to twelve servers.
WinCC/WebNavigator
With the combination of Web Navigator server and client, you have the option, using the
standard facilities of WinCC, of implementing a new type of distribution of operator and
monitor functions for your programmable logic controller over the Internet or intranet.
Options for Increasing Availability
WinCC/Redundancy
WinCC Redundancy is used to configure a redundant system. The availability of WinCC and
the system as a whole are enhanced by parallel operation of two interconnected servers and
automatic switching of the servers in the event of a malfunction.
WinCC/ProAgent
The ProAgent option package lets you configure powerful process diagnostics. The process
diagnostics helps you to detect and eliminate potential malfunctions in a short space of time.
You thus increase the availability of your system, cut down times and lower costs.
Options for Process Instrumentation and Control System
WinCC/Basic Process Control

Contains WinCC basic data and extensions which make a WinCC station suitable for control
engineering applications - and with a minimum of engineering effort at that. Picture Tree
Manager, OS-Project Editor and Lifebeat Monitoring are just some of the functions included.
WinCC/Advanced User Administrator

Supports system-wide management of all users with numerous security mechanisms for the
administrator and users. Time-stamped log flies support extensive evaluation of all actions -
a prerequisite for satisfying FDA requirements

Options for Archiving, Data Evaluation and IT Integration
WinCC/DataMonitor WebEdition
WinCC/Data Monitor is used purely for displaying and evaluating current process statuses
and historical data on Office PCs using standard tool such as Microsoft Internet Explorer or
Microsoft Excel. Operating as a Web client, it is supplied with current and historical process
data from a Web Navigator server.
WinCC/UserArchives
For storing freely structurable data records in the integrated WinCC database. The data
records are displayed by means of a freely configurable ActiveX control as a form or table at
runtime. Includes import/export functions for reading data in and out by means of external
applications such as Excel.
WinCC Configuration Tools
WinCC/IndustrialX
For even simpler and more cost-effective configuration by standardizing the display objects
for similar objects (motor, pump, valve, etc.). IndustrialX uses ActiveX technology for process
visualization. Configuration assistants (wizards) help to keep the creation of standard
displays simple.
WinCC/Open Development Kit

The Open Development Kit describes open-system programming ports, with which data and
functions can be accessed by the configuration and Runtime systems.
WinCC Communication
WinCC/Communication Channels
All important communication channels for connecting to SIMATIC PLCs and inter-PLC
channels (such as OPC) are supplied with WinCC. Furthermore, there are channels as an
option for WinCC.
WinCC/Connectivity Pack
The WinCC/Connectivity Pack encompasses the OPC HDA and OPC A&E server for access
to historical data of the WinCC archive system and for forwarding messages and
acknowledging by means of superimposed control systems.
WinCC can be specifically extended by means of these open and standardized interfaces.

WinCC Add-ons
WinCC Add-ons are developed and marketed by other Siemens departments (such as the
WinCC Competence Center) and external suppliers (such as WinCC Professionals, and
system companies). Support for the WinCC add-ons is provided by the product suppliers
concerned.
WinCC add-ons can solve versatile tasks such as maintenance management (MES
software), energy management, import filters, industrial solution for water management,
communication with PLCs from other manufacturers or the automatic transmission of radio
calls when certain alarms occur in production departments.
Further information about the add-ons and the contact addresses of the manufacturers
concerned will be found in the Add-on Directory on the Internet.

3.3 Integration into the SIMATIC Environment
Totally Integrated Automation (TIA)

In addition to a HMI system like WinCC, a complete automation solution also requires further
components, e.g. an automation system, a process bus and peripheral equipment.
Particularly wide-ranging integration is featured in WinCC with components in the SIMATIC
product family. This integration facilitates:
● global configuration and programming
● global data maintenance
● global communication
The Direct Utilization of STEP 7 Symbols in WinCC

Global configuration and programming facilitates the direct utilization of STEP 7 symbols in
WinCC.
Process tags form a link for communication between the automation system and the HMI
system. Were it not for Totally Integrated Automation, each tag would have to be defined
twice: once for the automation system and once for the HMI system. This would double the
workload and greatly increase the risk of errors.
When working with WinCC, you can gain direct access to the symbol table that is defined in
STEP7. You can access STEP 7 symbols directly by means of:
● the tag selection dialog
● the tag bar in Graphic Designer
If you select the STEP 7 Symbols check box in the Tag Selection dialog box, a list of all the
downloadable STEP 7 symbols is displayed in the data window. These symbols are all
inputs, outputs, and bit memories from the STEP 7 symbol list as well as the global data
blocks.

Simplified Diagnostics
Diagnosis is greatly simplified by global data maintenance and global communication.
● In runtime, you can jump directly from WinCC to the corresponding program editor in
STEP 7 (KOP/FUP/AWL). The focus will automatically lie on the STEP 7 symbol which
belongs to the process tag. This function provides valuable support in the area of fault
diagnosis.
● The WinCC function Hardware Diagnosis can be used to start the STEP 7 function
Diagnose hardware in an S7 automation system directly from a WinCC picture.
● Channel Diagnosis offers diagnostic possibilities for communication between WinCC and
S7 automation systems.
● In WinCC, automatically issued S7 system diagnostic messages from the programmable
logic controller are displayed as multi-line message text by means of tooltips. These
tooltips help to reduce system down times.
● Extensive diagnostic support is provided through the WinCC/ProAgent option. This option
provides extensive process diagnosis for S7 automation systems and does not
necessitate additional configuration.
Integration into SIMATIC PCS7

Global data maintenance and global communication also facilitate integration into SIMATIC
PCS7.
SIMATIC PCS7 is the process control system from Siemens The Engineering Stations (ES)
for configuration and the Operator Stations (OS) for operating and monitoring the process in
runtime are central elements of PCS7.
WinCC is an important constituent of PCS7 and is employed in the Engineering and
Operator stations.

3.4 Integration into Corporate IT Solutions
3.4 Integration into Corporate IT Solutions
Mode of Operation
Within many companies, individual solutions have lead to the development of a
heterogeneous information topology. Individual groups of information-based sectors have
had to be dissolved and the information made available at all times for every application, for
every user at any location.
The flow of information here must not be purely horizontal, available at individual levels, but
also vertically through the various levels: from the automation level (Controls) through the
production level (MES: Manufacturing Execution Systems) and on to the company
management level (ERP: Enterprise Resource Planning).
A decisive influential factor concerning the simplicity and speed with which a consistent IT
integration can be implemented within a company is the development of an application which
enables this through uniform data archiving, integrated standard interfaces and consistent
handling methods for all data.
Based on the functional range specified below, version V7.0 of WinCC provides an ideal
platform for IT integration.
● Consistent scalability, from the smallest single user station solution to client/server
solution.
● Central enterprise-wide archive server (WinCC/Central Archive Server) on the basis of
Microsoft SQL Server 2005 with data compression and integrated long-term archiving.
● Integration in corporate-wide applications by means of open interfaces
- Database interfaces: OLE DB, SQL, ADO
- Programming interfaces: VBS and ANSCI-C with access to API functions
- OPC: OPC DataAccess (DA), OPC Alarms&Events (A&E) and OPC Historical Data
Access (HDA)
● Evaluation options using special tools provided by the WinCC options or WinCC Add-ons.

3.5 Openness
3.5 Openness
Introduction
The open and standardized interfaces of WinCC make specific extensions simple.
ActiveX Controls
ActiveX is a Windows standard for program modules that have their own user interface.
These program modules are known as ActiveX Controls. An ActiveX control can contain a
specific button, for example, or a graphic display element.
A large number of ActiveX Controls are provided with WinCC.
Additional ActiveX Controls can be acquired from other suppliers or can be individually
programmed. The IndustrialX option provides support when creating individual ActiveX
Controls with Visual Basic. To ensure the ability of WinCC to function properly, you should
test these controls at length before using them.
ActiveX Controls can be integrated into your WinCC picture using the Drag&Drop method.

3.5 Openness
OLE
OLE is the acronym for "Object Linking and Embedding" and is a standard for data exchange
between programs used in conjunction with Microsoft Windows. Here, data from one
application are inserted into your own application. A typical example here would be a text
into which a graph is inserted and subsequently edited by double-clicking on it. Here,
Windows opens the original graphics program to allow editing to take place.
This technique can, for example be employed in a WinCC project to integrate an Excel table
into one of your pictures and use the data in the table as recipe data.
OPC
A form of OLE specially developed for the automation technique is "OLE for Process
Control", abbreviated OPC. Using this standard, any OPC-enabled components
communicate with one another. You do not have to go into great detail with the interfaces
during configuration.
WinCC can either be an OPC client or an OPC server. When operating as an OPC client,
WinCC will access the data of other applications.
When WinCC is used as an OPC server, the WinCC data will be made available to other
applications.
The following types of access are possible:
● Access to WinCC tags through the WinCC OPC DA server.
● Access to the archive system through the WinCC OPC HDA server.
● Access to the message system through the WinCC OPC A&E server.

3.5 Openness
SQL
SQL can be used to access the contents of the WinCC databases.
● SQL is the acronym for Structured Query Language, a standardized language for
accessing databases.
The queried data can either be used in other applications or imported into other databases.
It should be remembered in this instance that accessing the databases has a direct effect on
the database and the ability of a WinCC project to work.
API
WinCC has a C-programming interface. Consequently, individual applications can influence
WinCC, can access configuration runtime data or intervene in the process. The ODK option
(Open Development Kit) contains documentation for this interface and numerous examples.
ANSI-C
WinCC supports the use of functions and actions for dynamization of the processes in your
WinCC project. These functions and actions are written in ANSI-C.
VBS
In WinCC, the programming language VBScript is available to you as an application
programmer interface, in addition to C-Script. With VBScript (VBS), provides access to tags
and objects of the graphical runtime system at runtime and enables execution of picture-
independent actions. Apart from the specific WinCC applications, it is also possible to use
the general functionality of VBS for access to the Windows environment.
VBA
The VBA (Visual Basic for Application) interface is another option for customizing WinCC. In
Graphics Designer you can automate frequently recurring work steps with VBA while you are
configuring. Furthermore, you can fall back on products of the Microsoft Office family that
support VBA.
ADO/OLE DB
You can access the archive database of WinCC through the ADO/OLE DB interface.

3.6 Licensing
3.6 Licensing
Modular Licenses
In order to be flexible toward all requirements, not only WinCC software is organized in
modular form but licenses as well. The release of licenses is referred to as licensing. It takes
place within the framework of the WinCC installation by a special license key data carrier.
The license may also be transmitted by the user after the fact using the Automation License
Manager.
Differentiation is made between RC licenses (Runtime and Configuration) and pure RT
licenses (Runtime only). If you wish to operate WinCC on a computer in Runtime only,
without effecting any configurations from it, you will only require an RT license for this
computer.
An additional tier of licenses is based on the maximum number of process tags and archive
tags usable in RT. For example, a maximum of 2,048 process variables can be used in RT
with the "WinCC RC (2048)" license. Generally, these modular license permit the use of 512
archive variables without needing your own archive license.
Missing Licenses
Missing licensing will cause WinCC to run in demo mode.
If WinCC switches into demo mode, all open editors will terminate after one hour. If RT is
activated at this time, WinCC Explorer and the Runtime system will continue to run.
However, if RT is not activated, WinCC Explorer will terminate as well. After an editor restart,
you will be permitted to work for an additional 10 minutes.
Upon the start of Runtime (License RTxxx), a box appears requesting acknowledgment and
acquisition of a valid license. This message will be redisplayed every 10 minutes and must
be acknowledged. If the message window is moved, the window reappears again, centered,
after 30 minutes at the most. As long as you are in Runtime, WinCC Explorer is not
terminated. On exiting from runtime, WinCC Explorer is also closed.
Options are also enabled using special licenses. If a license is missing for an option used in
a project, the demo mode is automatically activated. This happen independent of whether or
not other licenses are available, and it always affects the full functionality of WinCC.
Exceeding the Maximum Number of Tags

If your project exceeds the maximum number of process tags and/or archive tags available
for your license, a switchover into demo mode will take place. You will require an upgrade
license in this case.
With an upgrade license, additional process tags ("PowerTags") or archive tags ("ArchTags")
are enabled.
The number of tags is checked only during server operation. Affected are computers which
function as servers only, or function as server and client simultaneously (single-user
system). On pure clients with an existing license, the maximum number of tags is always
enabled.

3.7 Typical configurations
3.7.1 Typical configurations
Flexibility
Various system configurations can be implemented using WinCC. You are not restricted to a
configuration that has already been selected; single-user applications can be changed to
multi-user applications even at a later point in time. This will facilitate the step by step
expansion of your project.
Configurations
In principle, the following system configurations are possible when working with WinCC:
● Single-user System
● Multi-user systems with one server and several clients
● Distributed system with several servers
● Central Archive Server
● Long-term archive server
● Redundant system for maximum availability
● Web Client system to connect clients via intranet or Internet

3.7.2 Single-User System
Mode of Operation
The simplest configuration is the single-user system. The PC on which WinCC has been
installed also functions as a server for the WinCC databases and as a client which accesses
these databases.
A single-user system is connected to the automation systems over a process bus.
The PC can also be integrated into a LAN.
Areas of Application
Single-user systems are most frequently employed in the area of production but can also
operate and monitor independent subprocesses or plant parts within larger projects.
Software Requirements
In the case of single-user operation, it will be necessary to install a license for the basic
WinCC system on the PC. The maximum number of process tags that are available will
depend on the license.

3.7.3 Multi-User System
Mode of Operation
A multi-user system consists of a server and several operator stations (clients). An individual
server with process driver connection is normally configured in the case of small systems in
which a distribution of the data over several servers is not necessary.
Several operator stations access the project on a server with process driver connection. The
individual operator stations can execute the same or different tasks.
Clients and server are linked via a LAN or ISDN. The standard protocol TCP/IP is used for
communication with the server.
A process bus is used to connect the server to the automation systems.
In the case of a multi-user system, it is not necessary to configure the clients. The server is
responsible for all common functions:
● Connecting the automation systems
● Coordination of the clients
● Providing the clients with process values, archive data, messages, pictures and protocols
The central services of the server are availed off by all clients. Each client increases the
workload of the server.

You require multi-user systems in the following instances:
● You wish to display different information relating to the same process on different
operating consoles. You could, for example use one operating console to display the
process pictures and a second operating console exclusively for the purpose of
displaying and acknowledging messages. The operating consoles may be located side by
side or in totally different locations. The data is provided by the server.
● You wish to operate a process from several locations, e.g. along a production line.
User authorization is issued to define the functions that are available to an operator on a
certain operating console.
Maximum Number of Clients on a Multi-user System

Up to 32 clients can be operated on one server.
In order to operate the client-server mode, the license for the WinCC Basis System, the
WinCC Option server and a Microsoft Windows 2003 server operating system must be
installed. The smallest runtime license (Runtime 128) is sufficient for one client.

3.7.4 Distributed System
Mode of Operation
WinCC can be used to configure distributed systems with clients which have views on
various servers and, therefore, operate and monitor large systems efficiently. As a result of
distributing tasks over several servers, the load applied to individual servers is relieved. This
achieves a better system performance realize larger typical applications.
Distributed systems are used, for example:
● In large systems where several operator and monitoring stations (clients) are required for
the same tasks.
● When you want to distribute different operator and monitor tasks to several operator
stations, such as a central client, for displaying all the messages of one system.

Client/Server Scenarios
Using WinCC you can implement different client-server scenarios depending on the
application:
● Technological distribution: In the case of large systems, technological distribution is
normally used in order to display the system in a structured, realistic way. Each server
takes over a technically restrictable area of a system, e.g. a certain press or dry unit.
● Functional distribution: However, an individual WinCC server assumes only a single
specific task type, such as message processing or archiving.
● Use of a file server in order, for example, to save the system configuration centrally on a
file server and to open this system configuration from a WinCC engineering station via
the network.
● Use of server/server communication: A server accesses the process data of another
server.
Regardless of the scenario, clients have no direct access or link to the process. The clients
access the data of certain servers to operate and observe the process.
Clients in Distributed Systems

Clients can be used in different ways on distributed systems. A client can view one or more
servers. Usage depends on the tasks.
With distributed systems, from the client in WinCC you can e.g.:
● Access data on several servers.
● Remotely configure the server projects from the accessing clients.
● Automatically distribute updated data from the server projects to the relevant computer in
the network.
Maximum Number of Servers and Clients in a Distributed System

You can configure mixed systems with WinCC, i.e. use clients and WebClients together in
your distributed system.
If you only use clients, in a WinCC network up to 32 parallel clients can access a server. In
Runtime, a client may access up to 12 servers/server pairs.
When using WebClients, the limit is up to 51 clients (1 client and 50 WebClients). In such a
system a maximum of 24 servers in the form of 12 redundant server pairs can be used.
In order to operate the client-server mode, the license for the WinCC Basis System, the
WinCC Option server and a Microsoft Windows 2003 server operating system must be
installed. The smallest runtime license (Runtime 128) is sufficient for one client.

3.7.5 Central Archive Server (WinCC CAS)
Mode of Operation
WinCC Central Archive Server (WinCC CAS) is used to centrally archive important process
data of multiple WinCC servers and other data sources. In this way, the process data for
analysis and visualization are made available throughout the company.
WinCC clients have access to the entire data of the system independent of whether these
are located on the WinCC CAS or are still on the WinCC servers. Data access is
transparent. WinCC process images can also display data via WinCC Trend Control or
WinCC Alarm Control.
Data security is thus consistently ensured while transferring data to the central archive. In
case of network failures, data is buffered on the WinCC server. Further, WinCC CAS can
also be maintained redundantly.
The WinCC client or the connectivity station is the central access point to the system. The
connectivity station can function as server for the system data; the WinCC client can also
serve as the Web Navigator Server or Data Monitor Server. The WebCenter included in the
DataMonitor enables comfortable display and evaluation of data.

3.7.6 Long-term archive server
Mode of Operation
A long-term archive server is implemented, for example, to make backup copies of the
database files of process value archives once a month.
A server without process connection is used as a long-term archive server onto which the
servers with process connection transfer their archive backups. There are various methods
with which to access the swapped archive data:
● Remote access (LAN, WAN, Internet) with the browser-based DataView of the
WinCC/DataMonitor WebEdition option
● Access using the WinCC OLE-DB provider
● Copying back the database files on a WinCC runtime system
● Access by using WinCC process screens.

3.7.7 Redundant Systems
Mode of Operation
A second redundant server can be operated for each of the existing servers. All process
values and messages will then be processed and archived on both servers. If one of the
servers fails, the clients that are connected will automatically be rerouted to the other server.
The process can be operated and monitored on the clients almost without interruption.
Redundant systems increase availability. Such systems are always employed when it is
essential to guarantee that the archiving of process data and messages will not be
interrupted in the event of a server failure.
Redundant servers can be integrated into a multi-user system or into a distributed system.

Procedure in the Event of a Fault

If operation is fault-free, both servers run completely parallel. The automation systems pass
on all data to both servers parallel. Each server processes its own data.
If one of the servers fails, the clients that are connected to this server will be rerouted to the
redundant server. The switch of the clients from the default (master) server to the partner
server during a server failure is performed automatically by the system. The following factors
cause a switch of servers:
● Network connection to server failed
● Server failure
● Malfunction of process connection
● The Application Health Check function has detected a faulty application and triggers the
switch.
The switch guarantees that no data are lost and the process can continue to be operated.
When the failed server has been returned to an operational state, WinCC will proceed to
synchronize the server by passing on all the data that was recorded by the redundant server
since the fault occurred.
In the case of redundant servers, it will be necessary to install a license for the WinCC
Redundancy option on each server in addition to the license for the basic WinCC system.

3.7.8 Web Client System
Mode of Operation
When using a Web Client system you will be able to operate and monitor your process via
the Internet or an intranet.
Each web client has to identify himself when accessing the WinCC Web Navigator Server.
The web client will then be able to monitor or control the process in accordance with his
access permissions. The WinCC Web Navigator is based on the standard HTTP protocol
and supports all common security mechanisms.
The web clients will automatically be notified of any changes to the process by the WinCC
Web Navigator Server. The current process values and messages are always displayed on
the web clients.
A web client can simultaneously access up to twelve servers through the WinCC Web
Navigator Server. This means that cross-system evaluations can be performed.
Differentiation is made between Web Navigator control clients (operator and monitor) and
management clients (monitor).
Web clients are used in the following areas:
● Where remote access can only be established over the Internet or intranet.
● To facilitate mobile remote diagnosis and fault correction.
● To establish a large number of clients at low cost.
● In the case of applications that have a decentralized structure or only sporadic access to
process information.
● To implement thin-client solutions using terminal/server technologies such as for mobile
solutions like handhelds, PDAs or rugged on-site operator stations and operator panels.
● To support Excel evaluations by means of WinCC online/archive data on the Internet or
an intranet. The DataMonitor is used for evaluations.
Special Configuration Features

The integrated Web Publishing Wizard automatically converts your pictures into a format
which is suitable for the web.
When configuring, attention must however be paid to some special aspects pertaining to web
access. You will find more information about WinCC Web Navigator in the documentation.

In the case of WinCC Web Navigator server operation, it will be necessary to install a license
for the WinCC Web Navigator option on the server in addition to the license for the basic
WinCC system.
Licenses are available for 3, 10, 25 or 50 clients that can simultaneously access the Web
Server. The Web Navigator clients can access several, different Web Navigator servers
simultaneously.
There is a per seat license especially for remote diagnostics, where web servers are
accessed only sporadically. The Web Navigator license in this case resides on the client
(Web Navigator diagnostic client), which can access up to 12 servers simultaneously. The
license for the basic WinCC system does not have to be installed on the client.
The WinME, WinNT, Win2000, and WinXP operating systems support the web clients.
Internet Explorer 6 or a later version must be installed on the clients. The clients do not have
to be installed separately but fetch essential components over the web from their Web
Navigator server.

How WinCC Works 4
4.1 How WinCC Works
Structure of WinCC
WinCC is a modular system. Its basic components are the Configuration Software (CS) and
Runtime Software (RT)

How WinCC Works
4.1 How WinCC Works
Configuration Software
WinCC Explorer will open immediately after you start WinCC. WinCC Explorer forms the
core of the Configuration software. The entire project structure is displayed in WinCC
Explorer. The project is also administered here.
Special editors which can be called from WinCC Explorer have been provided for
configuration purposes. Each editor is used to configure a special WinCC subsystem.
The most important WinCC subsystems are:
● The Graphics System – the editor that is used to create pictures is known as the Graphics
Designer.
● Alarm Logging System – the editor used for the configuration of messages is referred to
as Alarm Logging.
● The Archiving System – the editor used to identify the data to be archived is referred to as
Tag Logging editor.
● The Report System – the editor that is used to create report layouts is known as the
Report Designer.
● User administration – the editor that is used to administer users is, as the name implies,
known as the User Administrator.
● Communication – this is configured directly in WinCC Explorer.
All configuration data is saved in the CS database.
Runtime Software
The Runtime software allows the user to operate and monitor the process. It is primarily
used to execute the following tasks:
● It reads the data that has been saved in the CS database
● It displays pictures on the screen
● It communicates with the automation systems
● It archives current runtime data, e.g. process values and message events
● It controls the process, e.g. through setpoint input or switching On and OFF
Performance Data
The performance data will be directly determined by the PC hardware that is used and the
manner in which the system is configured. You will find examples of different system
constellations in the WinCC Information System at Performance Data.

How WinCC Works
4.2 Graphics System
4.2 Graphics System
Graphics System Tasks

The screens depicting the process in runtime are created with the graphics system.
The Graphics System handles the following tasks:
● It displays static and operator-controllable picture elements, such as texts, graphics or
buttons
● It updates dynamic picture elements, e.g. modifies the length of a bar graph in relation to
a process value
● It reacts to operator input, e.g. the clicking of a button, or the entry of a text in an input
field
The Components of the Graphics System

The Graphics System is made up of Configuration and Runtime components:
● The Graphics designer is the configuration component of the Graphics System. The
Graphics Designer is the editor that is used to create pictures.
● Graphics Runtime is the runtime component of the Graphics System. Graphics Runtime
displays the pictures on the screen in runtime and administers all inputs and outputs.

How WinCC Works
4.2 Graphics System
Libraries
Module libraries help you to create your pictures in a particularly efficient manner. The
objects in the library can be inserted into your pictures during configuration using the
Drag&Drop method.
● The module libraries that have been provided contain a large selection of precompiled
objects that have been sorted in accordance with themes, such as valves, motors,
cables, display instruments and much more.
● You can store homespun objects on the project library and reuse them as often as you
like.
VBA in Graphics System

With VBA you can customize the functionality of the graphics system.
When you use VBA, you can
● Automate frequently recurring work steps during configuration
● Create user-defined menus and toolbars
● Replace with VBA macros all actions that would otherwise be executed with the mouse.
● React to events that occur in Graphics Designer or in the picture when you wish to create
a new object in the picture
● Dynamize properties and events of pictures and objects.
● Fall back on products of the Microsoft Office family that support VBA. This means that
you have an opportunity to read values from an Excel table and then assign them to
object properties.

How WinCC Works
4.2 Graphics System
Dynamize Process Pictures

WinCC features a wide range of options for dynamizing the graphic objects of a process
picture.
● Dynamizing with the Dynamic Wizard:
When you execute a wizard, preconfigured C actions and trigger events are defined and
transferred to the object properties.
● Dynamizing by means of tag connection:
Thus, for example, the background color of an object can be directly influenced by a tag.
● Dynamizing with a direct connection:
This type of dynamics can be used to react to events.
● Dynamizing with the dynamic dialog box:
The Dynamic dialog box can be used to monitor the state of a tag, for example.
● Dynamizing with a VBS action:
The VBS action can execute when a picture is called, such as opening a login dialog box.
● Dynamizing with a C action:
C actions can be used to dynamize object properties and to react to events such as the
change in color of a display element when a tag limit value is exceeded.

How WinCC Works
4.3 Alarm Logging
4.3 Alarm Logging
Alarm System Tasks

Alarms inform the operator about process malfunctions and errors. They help to detect
critical situations early and to avoid downtimes.
During configuration, define the events which should trigger process messages. An event,
for example, can be that a certain Bit in a PLC is set or that a process value exceeds a
defined limit value.
Components of the Alarm System

The alarm system consists of configuration and runtime components:
● The configuration component of the alarm system is the Alarm Logging editor. Alarm
Logging is used to define when and what type of an alarm is to be displayed with what
content. The Graphic Designer also disposes of a special display object, the WinCC
Alarm Control, which is used to display messages.
● Alarm Logging Runtime is the runtime component of the message system. When in
runtime, Alarm Logging Runtime is responsible for executing the defined monitoring
tasks. It also controls the message output operations and administers the
acknowledgement of these messages.
The messages are displayed in WinCC AlarmControl in tabular form.

How WinCC Works
4.3 Alarm Logging
Message Block
The content of a message is comprised of the message blocks. Each message block
corresponds to one column in the tabular display in WinCC Alarm Control. You can define
which message blocks are contained in your messages.
There are three groups of message blocks:
● System blocks with system data, e.g. date, time, message number and status
● Process value blocks with process values, e.g. current fill levels, temperatures or
rotational speed
● User text blocks with explanatory texts, such as the message text containing information
relating to the location and cause of a fault
Basic Statuses of a Message

A distinction is made between three basic types of message status in WinCC:
● A message will retain its "Active" status until such time as the initiating event no longer
exists, i.e. the cause of the message no longer exists.
● As soon as the cause no longer exists the message will adopt the status "Cleared".
● A message can be configured in such a way that the operator has to acknowledge it. The
message will then adopt the status "Acknowledged".
The current status of each message, "Active", "Cleared" or "Acknowledged", is shown in the
message display. A different color is used for each status.
Group Messages
During configuration, any required number of messages can be summarized in one group
message. The group message will appear as soon as at least one of the assigned single
messages is queued (logical OR). The group message will disappear when none of the
single messages are queuing.
Group messages can be employed to provide operators with a clearer overview of the
system and to simplify certain situations.
Message Classes
During configuration, you will have the option of assigning each message to a message
class. This has the advantage that you can then make numerous default settings for the
entire message class instead of making these settings for each message individually.
Up to 16 message classes can be freely defined within a project.

How WinCC Works
4.3 Alarm Logging
Message Arching
With the Archive Management in WinCC you have the option to archive process values and
messages for the specific documentation of operation and error states. Microsoft SQL Server
is used for archiving.
The messages of so-called message events are archived. A message event describes the
moment at which a message adopts a new status. In accordance with the three basic states
of a message, there are the following message events:
● "Active"
● "Cleared"
● "Acknowledged"
You can save the message events in an archive database and archive as a message report
on paper. The messages archived in the database can e.g. be output in a message window.
Archive Type
To archive messages, WinCC uses short-term archives of configurable size, which you can
configure with or without backup.
You can choose any storage medium for the archive files within your network- for example,
the hard disk of the WinCC server or a separate archive server.

How WinCC Works
4.4 Archiving System
Tasks of the Archiving System

You can display current process values at any time. However, if you want to display the
chronological progression of a process value, e.g. in a diagram or table, you will need
access to past process values. These values are stored in process value archives.
In practice, such temporal displays are very important as they allow problems to be
recognized very early on. lf, for example, the fill level of a tank sinks over this period, this
may be the result of a leak which will have to be attended to immediately to prevent
production stoppages or to eliminate the danger of the machines being damaged.
Having access to individual historic process values also has another advantage. This can,
for example, help to determine how high certain values were at a time when production
problems were experienced.
Aside from process values, it is also possible to archive messages. You will find more
information in the WinCC Information System at "Message system".
Components of the Archiving System

The process value archiving system consists of configuration and runtime components:
● The configuration component of the archiving system is the Tag Logging editor. There,
you can configure process value archives as well as compressed archives, define
acquisition and archiving cycles and select the process values to be archived.
● Tag Logging Runtime is the runtime component of the Archiving System. Tag Logging
Runtime is responsible for writing the process values that have to be archived to the
process value archive in runtime. The Tag Logging Runtime is also responsible for
reading the archived process values from the process value archive when, for example,
these are required for display purposes in one of the controls or for a further evaluation.

How WinCC Works
Output of Process Data

The process data can be displayed in a picture or output as a report.
● You can output the time course of process values in a picture. To do this there are three
controls in the Graphics Designer. WinCC OnlineTrendControl and WinCC
FunctionTrendControl for graphical display and WinCC OnlineTableControl for tabular
display. With the WinCC RulerControl you can display statistical information.
● You can print out process values from the archive database as a report. You can also
choose between tabular and graphical for the output form. In the Report Designer, both
output forms are available as predefined layouts.
The following screenshot shows a WinCC OnlineTrendControl with a WinCC RulerControl
and a WinCC OnlineTableControl in Runtime.

How WinCC Works
Archiving Times
During configuration, you can define:
● which process values are to be archived
● the archive in which the process values are to be written
● the times at which the process values are to be archived
An archiving cycle and events are used to control archiving times. The archiving of process
values can, for example, be effected in constant time cycles or only when a process value
changes by a certain amount or percentage.
Archiving
Process values can be stored either on hard disk in the archive database or in the main
memory of Tag Logging Runtime.
You can use different archiving methods to archive process values. You can therefore e.g.
monitor a single process value at any point in time and make the monitoring dependent on
certain events. You can archive quickly changing process values without increasing the
system load in doing so. You can compress process values already archived to reduce the
data volume.
Swapping Out the Archive

You can swap out process values from the archive database as a backup. All process values
contained in a data puffer are swapped out. The time at which swapping out is performed
depends on your configuration in ArchiveManager.
In the WinCC Basis System, it is possible that 512 archive tags are already configured. For
more archive tags than this, there is another classification of the licenses by the maximum
number that can be configured.

How WinCC Works
4.5 Report System
4.5 Report System
Report System Tasks

The report system features two categories of reports:
● Configuration data in a report
● Runtime data in a report
Reports that relate to project documentation contain overviews of your configuration data,
such as a table of all tags, functions and graphics used in your project.
Reports on runtime documentation document your process. Here are some of the options for
this:
● A message sequence report outputs a chronological list of all messages. Printing is either
effected page by page or on line-oriented printers immediately after the occurrence of the
message event.
● An archive report outputs a list of all messages stored in a certain message archive
● A tag table documents the information and contents of tags in process value and
compressed archives in tabular form
● Data from other applications not originating in WinCC can likewise be logged. There are
various log objects available for integrating this kind of data in a WinCC log.

How WinCC Works
4.5 Report System
Components of the Report System

The report system consists of configuration and runtime components:
● The configuration component of the report system is the Report Designer. The Report
Designer is used to adapt ready-made default layouts to your requirements or to create
new layouts. The Report Designer is also used to create print jobs to initiate the output.
● Report Runtime is the runtime component of the Report System. The report Runtime
fetches the data for printing from the archives or controls, and controls the print output.
The following illustration shows a simple report.

How WinCC Works
4.5 Report System
Print Jobs
The printing of project documentation reports is always effected by the operator using the
Configuration Software.
You control runtime documentation report printing by means of print jobs. A print job
determines:
● whether or not a report is printed and when it is printed
● the layout that is to be used for printing
● on which printer or in which file output is to be effected
Reports can be output in any of the following ways:
● time-driven – e.g. on an hourly or daily basis or at each change of shift
● event-driven – e.g. on exceeding a certain limit value
● on request – e.g. through key operation

How WinCC Works
4.6 Communication
4.6 Communication
Communication Tasks
Communication between WinCC and the automation systems is effected via the respective
process bus, e.g. Ethernet or PROFIBUS. Communication is managed by specialized
communication drivers known as channels. WinCC has channels for the automation systems
SIMATIC S5/S7/505 and manufacturer-independent channels such as PROFIBUS DP and
OPC. Moreover there is a variety of optional channels available for all common controls as
an option or add-on.
Communication with other applications, e.g. Microsoft Excel or SIMATIC ProTool, is effected
with the assistance of the OPC (OLE for Process Control). When the WinCC OPC server is
used, the data will be made available to other applications by WinCC. The data of other OPC
servers can also be received by WinCC via the OPC client.

How WinCC Works
4.6 Communication
Communicating with the Automation Systems

Process tags form the link for data exchange between WinCC and the automation systems.
Each process tag in WinCC corresponds to a certain process value in the memory of one of
the connected automation systems. In runtime, the data area in which this process value is
saved will be read out of the automation system by WinCC thus allowing the value of the
process tags to be ascertained.
WinCC is also able to write data back into the automation system. This data is then
processed by the automation system. In this manner, you can use WinCC to control process.
Communication via OPC

OPC clients can access WinCC data through the integrated OPC servers. The following
types of access are possible:
● Access to WinCC tags through the WinCC OPC DA server.
● Access to the archive system through the WinCC OPC HDA server.
● Access to the message system through the WinCC OPC A&E server.

How WinCC Works
4.6 Communication
Channel Units, Logical Connections and Process Tags

Communication between WinCC and the automation systems is effected via logical
connections. These logical connections are arranged in a hierarchical manner over several
levels. These individual levels are reflected in the hierarchical structure of WinCC Explorer.
The communication drivers can be found at the highest level. These are also referred to as
channels (e.g. the channel SIMATIC S7 PROTOCOL SUITE).
One or more protocols have been provided for communication via a channel. The protocol is
used to determine the channel unit that is to be used (e.g. MPI). This channel unit is then
used together with a certain protocol to access to a certain type of automation system.
A channel unit can be used to establish logical connections to several automation systems
which communicate via this channel unit (e.g. the automation system SPS1). A logical
connection therefore represents the interface to an individual, defined automation system.
The process tags of the automation system are shown to the right of the data window in the
case of each logical connection (e.g. the process tag MyTag1).

How WinCC Works
4.6 Communication
The Communication Process in Runtime

Up-to-date process values are required in runtime. Thanks to the logical connection, WinCC
knows which automation system the process tags are located in and which channel is being
used to process the data traffic. The process values are transferred via the channel. The
data that is read in will be stored in the working memory of the WinCC server.
The necessary communication steps are optimized by the channel in such a way that data
traffic via the process bus is reduced to a minimum.

How WinCC Works
4.7 WinCC Function Chart
Overview
The following graph summarizes the interaction between the WinCC subsystems. This
provides important information relating to the sequence that is employed for configuration.
For example, the Report Designer provides the print jobs for the output of reports and logs.
Data cannot be printed until you configure the corresponding layout in Report Designer.

How WinCC Works
Workflow
You will use the editors in the Configuration software to create your project. All WinCC
editors store their project information in the Configuration database (CS database).
In runtime, the project information is read out of the Configuration database by the Runtime
software and the project is executed. Current process data is temporarily stored in the
Runtime database (RT database)
● The Graphics System displays pictures on the screen. Conversely, it also accepts
operator input, such as when the operator clicks on a button or enters a value.
● Communication between WinCC and the automation systems is effected by means of
communication drivers, or channels. The channels have the task of collecting the process
value requirements of all runtime components, reading the values of the process tags out
of the automation systems and, if necessary, writing new values into the automation
systems.
● The exchange of data between WinCC and other applications might be performed by
means of OPC and OLE.
● The Archiving System saves the process values in the process value archive. The
archived process values are, for example, needed to display the temporal development of
these values in Online Trend Control or in Online Table Control.
● The individual process values are monitored by Alarm Logging. If a limit value is
exceeded, Alarm Logging will generate a message which will be issued in Alarm Control.
The message system also receives the acknowledgements made by the operator and
manages the message states. Alarm Logging saves all messages in the message
archive.
● The process will be documented by the Report System on request or at predefined times.
The Process value archive and the message archive are accessed for this purpose.
You will find more information about WinCC editors and communication in the WinCC
Information System.

Configuring with WinCC 5
5.1 Configuring with WinCC
Configuration
WinCC facilitates the creation of complex projects without having to use a programming
language. Working with WinCC has a visual focus – similar to when working with a drawing
program. Assistants (Wizards) guide you through complex tasks. Precompiled function and
graphics libraries simplify routine work.

Configuring with WinCC
WinCC Explorer
When you open WinCC, WinCC Explorer will immediately appear. This can be seen as a
central tool for project administration.
① Title bar
② Menu bar
③ Toolbar
④ Navigation window
⑤ Data Window
⑥ Status bar
WinCC Explorer consists of three areas:

● All available commands can be accessed via the menu. The commands that are used
most frequently are available as symbols in the toolbar.
● All the components of WinCC can be found in the project navigation window.
● The content of the data window will vary depending on the component that has been
selected in the project navigation window. The data window shows which objects or
definitions belong to this component. In the case of the Graphics Designer this will, for
example, be the screens of your project.

Pop-up Menus
In WinCC, a pop-up menu has been provided for each component in the project navigation
window and for each object in the data window. If, for example, you wish to open the pop-up
menu for the Graphics Designer, click (with the right mouse button) on the component which
bears this name in the project navigation window.
Each pop-up menu contains a list of all the commands that are most frequently used in
conjunction with the selected component or the selected object.

5.2 Setting Up and Administering Projects
Overview
In WinCC Explorer you will be able to set up and administer projects. The Project Assistant
will guide you through the setting up phase.
Configuring with the Project Assistant

The Project Assistant will open automatically when you select the menu item "File > New".
The Assistant asks you for the project type (single-user or multi-user project), the name of
the project and where it is stored.
As soon as the Assistant has set up the project, the basic data of the project that has been
created by the Project Assistant will appear in WinCC Explorer. The project name will appear
in the title bar of WinCC Explorer.

Configuring with WinCC Explorer

You can also use WinCC Explorer to administer your projects.
● The individual operator consoles are configured using the component "Computer". Here,
you also define which runtime components should be started when the project is enabled.
● The connection to the connected automation systems is established under the
component "Tag Management". The tags that are required for data exchange with the
automation systems are also defined here.
● The remaining components have specialized editors for all further configuration tasks.
These editors can be selected from the pop-up menu.

5.3 Visualizing Processes
Overview
The screens serve to visualize the process that is to be controlled and observed. They
display the important process steps or plant parts and present the production process in a
schematic manner.
Each screen is made up of several screen elements:
● Statistical screen elements remain unchanged in runtime.
● Dynamic screen elements will change in accordance with the individual process values. A
bar is an example of a dynamic screen element. The length of the bar will depend on the
current temperature value. Another example would be a pointer instrument with a moving
pointer.
● Controllable screen elements allow the operator to have an active influence on the
process. These could be buttons, sliders or text boxes for entering certain process
parameters.
In the vast majority of cases, a project comprises several screens. Each screen shows a
different process step or displays special process data.
To allow the operator to switch between the various screens as required by the situation on
hand, it is essential that corresponding operator-controllable buttons be inserted in each
screen. Here, buttons should be used that select another screen when they are clicked on.
Alternatively, new screens which are still empty can also be created using the Graphics
Designer or WinCC Explorer. If you wish to process each screen immediately, you will find
that creating screens using the Graphics Designer is much faster. If, however, you wish to
create all required screens before you process them, we recommend that you use WinCC
Explorer.


Click with the right mouse button on the entry "Graphics Designer" in WinCC Explorer to
open the pop-up menu. A new and empty screen can be inserted into the data window by
clicking "New picture".
The subsequent processing steps can also be accessed via the pop-up menu. To access
these steps, simply click the newly created screen with the right mouse button. The most
important menu items are "Rename" and "Open":
● The menu item "Rename" can be used to assign the screen a more meaningful name.
NOTICE
If you rename a screen in WinCC Explorer, the new screen name must not have the
same name as an existing object in the screen. The software does not check whether
the name already exists. Using a name that is already in use can lead to conflicts during
access via VBA or during dynamization.
● The menu item "Open" is used to open the screen for processing in the Graphics
Designer.

Configuring with the Graphics Designer

The structure of the Graphics Designer is similar to a drawing program and it is also
operated in a similar manner. Any required element can be dragged onto your screen using
the mouse. You then position the elements and modify the size, color and other presentation
options if necessary.
Aids
Aside from the standard objects such as rulers, rectangles or circles, WinCC also has an
extensive library of graphical objects, e.g. cables, tanks or motors.
Alternatively, you can import graphs from other external graphics programs.

5.4 Reacting on Input
Overview
It is essential that operator-controllable screen elements be inserted in your screens to allow
the operator to control the process in runtime.
In order to make operation as intuitive and simple as possible, WinCC has ready-made,
standard Windows elements: buttons, check boxes, sliders, I/O fields and more.

Operator-controllable screen elements are inserted into your screen in the same manner as
the normal screen elements using the Graphics Designer.
Once the elements have been added, a configuration dialog will open automatically. This
contains the most important parameters relating to the presentation and behavior of the
inserted element.

Linking special events with actions

In addition to the configuration dialog, another dialog which contains a complete list of all
object properties is available with each element.
The dialog Object Properties can be accessed via the pop-up menu.
The dialog Object Properties allows you to link actions with screen elements. Actions are
triggered by events in runtime. In the case of a button, for example, the mouse click
represents the event. When the specified event takes place, an action, e.g. a screen change,
will be executed.

5.5 Accessing Process Values
Overview
A connection between WinCC and the automation system will have to be configured before
you can access the current process values of the automation system.

As setting up a connection is one of the central tasks for the entire project, WinCC Explorer
will have to be used here.
The first step involves selecting a channel. To do this, select the menu item "Add New
Driver" in the pop-up menu of the component "Tag Management".
You will now be able to select the required channel in a selection box.
A lot of channels support several communication protocols. The supported protocols are
listed below the channels in WinCC Explorer. In the following example, the channel SIMATIC
S7 PROTOCOL SUITE (the channel for the automation system SIMATIC S7) and the
communication protocol MPI were selected. The channel/communication protocol
combination determines the channel unit that will be used by WinCC.
Enter the connection to the automation system below the channel unit.
The connected automation system will then appear in WinCC Explorer as a channel unit
entry.

Creating Process Tags

Process tags can be created in WinCC so that you do not have to work with numerical
addresses in the memory area of the automation system. Each process tag has a unique
name under which it can be addressed throughout the entire system.
The process tags are also created in WinCC Explorer. As each process tag is linked
exclusively to a specific automation system, each of the process tags in WinCC Explorer
appears as an object of this automation system.
Simplification with SIMATIC S7

Configuration is particularly easy if you use a SIMATIC S7 automation system. Here, you will
not have to create the process tags manually in WinCC as you will have direct access to the
symbol table in STEP 7.
Using Process Tags

Screen elements can be used to show the value of a process tag. You can, for example,
display the value in numerical form or in the form of a bar which varies in length depending
on the value. By using suitable screen elements, you can also allow the operator to
determine the value of the tag himself, i.e. to write the tag. You could, for example, provide
an I/O field in which the operator can enter a setpoint.

5.6 Showing Current Process Values
Overview
All dynamizable screen elements can, in principle, be used to visualize process values. If, for
example, you wish to display the current temperature, you can opt for one of several
possibilities:
● If an I/O field with a numerical value is used, the temperature can be output in digital
form.
● You could also draw a simple thermometer and alter the length of a bar object depending
on the temperature value.
● Alternatively, you could use a precompiled OCX Control which, for example, represents a
pointer instrument.


The following applies irrespective of the type of the selected graphic element: The display is
updated automatically as soon as the process value in the automation system changes.
To achieve this, it will be necessary to link the object property which will change dynamically
(e.g. the value displayed in the I/O field) to the process tags which contain the current
process value (the temperature in the above example).
This link is established in the Graphics Designer using the configuration dialog of the
dynamic screen element.
The connected tag determines the displayed value. The update is effected in accordance
with the time interval after which the displayed value is compared to the current value and, if
necessary, updated. In the above example, updating is effected two times a second (time
interval = 500 ms).

5.7 Archiving Process Values
Overview
WinCC allows you to save the process values in the process value archive. The archive can,
for example, be used at a later point in time to display and evaluate the temporal
development of the process values.
Configuring with Tag Logging

Tag Logging is used to create and administer process value archives. Tag Logging is started
via the pop-up menu in WinCC Explorer. As with WinCC Explorer, Tag Logging also has its
own navigation and data window.

Archive Wizard
The Archive Wizard will provide you with valuable assistance when creating the process
value archive. The Archive Wizard can be accessed via the pop-up menu for the entry
Archive in the Tag Logging navigation window.
The Archive Wizard will guide you through the required steps.
Once it has been created successfully, the process value archive will appear in the Tag
Logging data window. The list of process tags which are to be archived in this archive will
appear at the bottom of the pane.
The pop-up menu can be used to make additional settings, e.g. the time interval at which the
values should be saved in the process value archive.

5.8 Visualizing Process Value Developments
Overview
WinCC allows you to visualize the temporal development of process values. Here, it will be
necessary to access historic process values. Process values which are used to show
development must therefore be saved in a process value archive.

Three picture elements have been provided in WinCC specially for the purpose of accessing
the process value archive and displaying data in tabular and in graphical form:
● the WinCC Online Trend Control for graphical display
● the WinCC Function Trend Control for the graphical processing of tags. The Trend
Control function gives you the option of displaying the values of tags as the function of
another tag
● the WinCC Online Table Control for tabular display
The required control can be dragged with the mouse from the object palette in the Graphics
Designer and inserted into one of your screens. The controls can be found in the object
palette of the Graphics Designer on the "Controls" tab.

Connecting with the Archive

Once you have dragged the control into your screen, the configuration dialog of this control
will automatically appear. Enter the process tags that are to be displayed by the control.
Select entry "1 - Archive tags" as the "Data source" and the archive that contains the
recorded process values of the process tags under "Tag name".
When in runtime, the development of the archived process data will appear in the control.

5.9 Creating and Archiving Messages
Overview
Messages serve to provide the operator with information relating to the operating status and
the fault status of the process. The messages are shown in runtime in a special message
view.
Configuring with Alarm Logging

Messages are configured in Alarm Logging. Alarm Logging can be accessed via the pop-up
menu of the component of the same name in WinCC Explorer.

Creating a Message System

Before you create and configure individual messages it will be necessary to create the
message system known as Alarm Logging. Among others, the following criteria will have to
be defined here:
● which message blocks are to be included in your messages
● which message classes are to be set up
The System Wizard provides valuable assistance when setting up Alarm Logging. The
System Wizard can be found in the toolbar in Alarm Logging.
You will be able to create and configure individual messages once Alarm Logging has been
set up by the Wizard.


WinCC includes a preconfigured message view for displaying messages: the WinCC Alarm
Control.
The WinCC Alarm Control can be dragged with the mouse from the object palette in the
Graphics Designer and inserted into one of your screens. The WinCC Alarm Control can be
found in the object palette of the Graphics Designer on the Controls tab.
When in runtime, the Alarm Control will show the operator the messages in tabular form.

5.10 Documenting Processes and Events
Overview
There are various types of reports that can be used depending on the type of data that is to
be documented e.g. process values or messages. When configuring, you perform the same
steps for the most part for all report types.
Configuring with the Report Designer

You create the layout for a report with Report Designer.
Preconfigured reports have already been provided for most application cases. While
configuring, it will only be necessary to link these preconfigured reports to your own archives.
This link to the archive is necessary as, in most cases, a report will also contain historic data
which is no longer in the process tags at the time the report is printed.
The Report Designer can also be used to modify the preconfigured reports. This is usually
much easier and quicker than creating a new report.
The preconfigured reports can be found in the WinCC Explorer navigation window below the
entry "Report Designer". When you select the "Layouts" entry, the available layouts appear
in the data window.
Select "Edit" on the pop-up menu to open a layout in Report Designer. Alternatively, you can
open the Report Designer first and then open the layout by selecting the menu item "File".

Static and dynamic layout elements

Each page layout consists of static and dynamic objects:
● Static layout elements appear on each page of the printout in the same form, e.g. a title
line or your company logo.
● When in runtime, WinCC supplies the dynamic layout elements with up-to-date process
data. When configuring in Report Designer you will only have to create placeholders for
this data.

Print jobs specify the times at which your reports are printed.
Predefined print jobs – which only need to be adapted – have already been provided for
those reports that are most frequently used.
Print jobs are edited in WinCC Explorer.

5.11 Preventing Unauthorized Operation
Overview
The improper operation of a machine or system can have grave consequences. Certain
functions should therefore only be made available to the appropriate authorized operators.
Configuring with the User Administrator

The User Administrator is used to issue and control access authorization. The User
Administrator is started via the pop-up menu in WinCC Explorer
Creating user and user groups

The first step involves the setting up of groups with their respective authorizations. Users are
then set up and subsequently assigned to these groups.
Issuing access authorization

A number of frequently used authorizations have already been predefined in the User
Administrator data window. To assign a user or a user group a certain authorization, simply
click the control box in the right hand column.


The settings that are made in User Administrator are not yet effective. To prevent
unauthorized operation, you will have to go one step further and directly protect the
appropriate screen element. Here, you specify in the Graphics Designer, the authorizations
an operator must have to operate this screen element.
The authorizations form one of the object properties of the screen element.

You now have to define a shortcut which will call up the logon dialog. The operator will use
this shortcut when logging onto the system. This setting can be accessed via the project
properties in WinCC Explorer.

5.12 Setting Up Multilingual Projects
Overview
If you are exporting a system or operators of different nationalities operate the system, you
will need WinCC's foreign language support.
If you were to compile a copy of your original project in each foreign language for translation
purposes, you would subsequently have to modify each version in the event of a change or
changes being made. WinCC's foreign language support facilitates the maintenance of all
languages in your original project.
WinCC has two language levels:
● The user interface language is the language of the WinCC Configuration software, i.e. the
language that will be displayed during the configuration of the WinCC menus, dialogs and
help texts. If required, the user interface language can be changed using the menu item
Extras. The user interface language will not affect your project data in any way. A project
could, for example, be created in the Russian language although the WinCC user
interface may have been set to the German language.
● The runtime language is the language that will later be seen by your plant operator in
runtime. The runtime language can be specified in the dialog Computer properties in
WinCC Explorer.
● You could also add an operator-controllable screen element to your project (e.g. a button
or a selection list) which the operator can use to switch languages in runtime.

Configuring with the Text Library

To guarantee that your texts are displayed in the required language in runtime, it will first be
necessary to save the translations in your project.
WinCC comes with a Text Library which simplifies the translation and maintenance of
multilingual text elements (e.g. messages). Language-dependent text can be collected in the
Text Library and subsequently translated in tabular form. If the translation work is to be
outsourced to a translator that does not use WinCC, the tables can be exported into
alternative programs.
The Text Library can be opened in WinCC Explorer.

Texts in screens and in screen elements (e.g. static texts or button labels) are not translated
in the text Library but directly in the respective screen. The size of the screen element may
have to be adapted. Each element must provide enough space for the language with the
longest terms.
While configuring, you can switch to another language by clicking the menu item View >
language in the Graphics Editor.

Exporting to other applications

You can export text for external translations, translate it external to WinCC and then re-
import it. In the text library you can export the text to a csv file using the File menu and re-
import it.
If you are managing very large quantities of text in the text library, you can alternatively use a
bulk data tool such as the WinCC SmartTool Excel Configuration Tool for importing and
exporting text.

5.13 Running and Testing Projects
Overview
You will require the WinCC Runtime software to run your projects. If the Runtime software
was installed together with the Configuration software you will not have to move to another
workstation to carry out tests.


The runtime properties will have to be specified before you enable your project for the first
time. The dialog Computer properties has been provided for this purpose. This dialog can be
accessed via the pop-up menu of the component Computer in WinCC Explorer.
The Startup tab is used to specify which runtime components should be activated and which
corresponding functions should be available in runtime. If, for example, your project contains
cyclic actions, it will be necessary to activate the component Global Script Runtime.
To achieve maximum performance, it is recommended that you only activate the
components you really require.
The Graphics Runtime tab can be used to define which screen should be displayed first once
your project has been enabled (Start screen). It is also used to define the manner in which
the WinCC project should appear on the screen.

Activate Project
Once you have defined the runtime properties you will be able to enable the project. The
Enable command is located in the File menu in WinCC Explorer. Alternatively, you can use
the button in the toolbar.
When the project has been enabled, the selected components of the Runtime software will
be started. You will now be able to control and test the project.
WinCC Simulator
Using WinCC Simulator, you can test your WinCC project during the development phase
without connecting the process peripherals or with connected process peripherals but
without the process running.
● You will be able to define a fixed value for a tag.
● The value of a tag can also be modified automatically over the period of time, e.g.
ascending, descending, in the form of a sine curve or on the basis of random variation.
The WinCC Simulator can be installed using the WinCC Setup program.
Testing Projects
All projects that are created with WinCC should be subjected to thorough and systematic
checks like any other software. The first step involves testing on a module basis with
simulated tag values. The second step involves testing the entire functionality of the project
with all automation components.
Online Configuration
If a fault is ascertained during the testing phase, this can immediately be rectified in WinCC
without stopping the process. Switch to the configuration software using the shortcut
combination <ALT+TAB> to do so. Make the alteration, save the data and then return to the
Runtime software. The process will run interruption-free with the new data.
Deactivating a Project
In order to deactivate your project, switch to the configuration software using the shortcut
<ALT+TAB>. Click the Deactivate button in WinCC Explorer toolbar to stop runtime.
Alternatively, you can also assign this function to a button in one of your screens.

5.14 Guide Through Your Projects
Optimized Sequence
In WinCC, certain configuration steps supplement configuration steps already effected.
Therefore, some configuration steps can only be effected after other steps have been carried
out.
The following overview serves as a thread which will guide you through the configuration
phase.
Mandatory Tasks

Optional Configuration


Index
Adding new, 63
A E
Action, 61 Event, 61
Operational screen elements, 61 Linking with operating action, 61
ActiveX, 17 Messaging, 38
Controls, 17
Add-on, 10
Licensing, 20 F
Alarm Logging, 71 Function, 33
Configuring messages with, 71 Of WinCC, 33
Runtime, 38 Function chart, 51
ANSI-C, 17 of WinCC, 51
Use of C-API, 17
Archive, 67
Wizard, 67 G
Archive types, 38
for messages, 38 Graphic, 58
Archiving system From other programs, 58
Of WinCC, 33
Archiving System, 33
Area of application, 7 H
of WinCC, 7 HMI system, 9
Positioning of WinCC, 9
C
CAS, 27 I
Central Archive Server, 27 I/O Field, 65
Computer, 81 Configuration, 65
Properties, 81 Import, 58
Configuration, 61 Graphic from other programs, 58
Dialog, 61 Industrial X, 17
Configuring, 58 Option, 17
Pictures, 58 Integration, 7
With the Graphics Designer, 58 Of WinCC in automation solutions, 7
Control, 69 Of WinCC in IT Solutions, 7
WinCC Online Table Control, 69
WinCC Online Trend Control, 69
Current process values, 65 L
Showing, 65
License, 20
Missing, 20
D Modular, 20
Display, 38
Messages, 38
Driver, 63

Index
O W
OLE, 17 WinCC
for Process Control, 17 Central Archive Server, 27
OPC, 47 WinCC CAS, 27
Server, 47 WinCC Central Archive Server, 27
Openness, 17
of WinCC, 17
Operational screen elements, 76
Preventing unauthorized access, 76
Option, 10
DataMonitor, 10
of WinCC, 10
WinCC/Guardian, 10
WinCC/Messenger, 10
WinCC/ProAgent, 10
WinCC/Process Control, 10
WinCC/User Archives, 10
WinCC/Web Navigator, 10
P
Process Control, 10
Process value block, 38
Project, 56
Assistant, 56
Properties, 81
Computer, 81
R
Report, 74
Reporting process value developments, 74
Runtime database, 51
Runtime language, 78
S
SIMATIC WinCC, 7
Software requirements, 21
System components, 10
Add-on, 10
Option, 10
U
User, 76
Administrator, 76
User Archives, 10


System Ueber Sich t

Uploaded by

Copyright:

Available Formats

System Ueber Sich t

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Ueber Sich t

Uploaded by

Copyright:

Available Formats

 WinCC System Overview ___________________

Application and configuration

WinCC V7.0 SP3

Printout of the Online Help

Siemens AG Printout of the Online Help Copyright © Siemens AG 2011.

WinCC System Overview

5.8 Visualizing Process Value Developments................................................................................... 69

WinCC System Overview

WinCC System Overview

WinCC System Overview

WinCC System Overview

The Distinguishing Features of WinCC

WinCC System Overview

WinCC System Overview

3.2 System Components

WinCC Basis System

WinCC System Overview

Options for scalable configurations

Options for Increasing Availability

Options for Process Instrumentation and Control System

WinCC/Basic Process Control

WinCC/Advanced User Administrator

WinCC System Overview

Options for Archiving, Data Evaluation and IT Integration

WinCC Configuration Tools

WinCC/Open Development Kit

WinCC System Overview

WinCC System Overview

3.3 Integration into the SIMATIC Environment

Totally Integrated Automation (TIA)

The Direct Utilization of STEP 7 Symbols in WinCC

WinCC System Overview

Integration into SIMATIC PCS7

WinCC System Overview

3.4 Integration into Corporate IT Solutions

WinCC System Overview

WinCC System Overview

WinCC System Overview

WinCC System Overview

Exceeding the Maximum Number of Tags

WinCC System Overview

3.7 Typical configurations

3.7.1 Typical configurations

WinCC System Overview

3.7.2 Single-User System

WinCC System Overview

3.7.3 Multi-User System

WinCC System Overview

Maximum Number of Clients on a Multi-user System

WinCC System Overview

3.7.4 Distributed System

WinCC System Overview

Clients in Distributed Systems

Maximum Number of Servers and Clients in a Distributed System

WinCC System Overview

3.7.5 Central Archive Server (WinCC CAS)

WinCC System Overview

3.7.6 Long-term archive server

WinCC System Overview

3.7.7 Redundant Systems

WinCC System Overview ___________________