Windows Control Center
SIEMENS
PRODUCT FAMILY:
WinCC RT
WinCC
WinCC RC (Developer
Configuration Complete
PackageGUI)
STEP 7
FEATURES
- SCADA system , HMI
- Powerful Graphic User Interface system
- Connectivity & communication standards &
interfaces, opennes
- Client/server architecture
- Redundancy
- Powerful Designer GUI
Examples of applications
SCADA
Manufacturing Execution System
Enterprise Resource Planning
WinCC architecture and functionality
WinCC IDE
Tag editor (channels)
Graph editor
Alarm/Log editor
User editor
Global/Local script editor
Report editor
Picture Editor
DDE,NATIVE,
Configurable RT KERNEL
(TCP/IP,
CHANNELS
SQL server (SQL ANYWHERE)
WIN API
Client/server architecture
SINGLE (server=client) architecture – SINGLE USER
Client/server architecture - MULTIUSER
Client/server architecture - MULTICLIENT
WinCC Multi Client
WinCC
Server1
WinCC
Server2
Client/server architecture – MULTICLIENT/DISTRIBUTED
SERVER
Multi Client
Trend Server
Alarm Server
Visualization
Server
Client/server architecture - MULTICLIENT
The Multi Client takes an important part in a distributed system
A Multi Client provides a common view of
 the process data of distributed servers in one picture
 all the measured value archives, e.g. in one curve window
 all the message archives
 the pictures/picture windows of different servers
The Multi Client has its own
project including additional
pictures, e.g. for a common
WinCC Multi Client plant-wide alarm
Standard
view. Client
WinCC
Server2
Client/server architecture - MULTICLIENT
The Multi Client has its own project
The server data is loaded on the Multi Client
The view of the different servers is based on a
new property: the server prefix ServerName::TagName
Server1::Tag1
Server2::Tag2
Client/server architecture - MULTICLIENT
WinCC Multi Client
I/O field linked to
“Server1::Tag1”
WinCC
Server1
I/O field linked to
“Server2::Tag2”
WinCC
Server2
Client/server architecture – WEB CLIENT
Web Client
Firewall
Web Server
WinCC Data Source
Web Server
Client-PC
HTTP Request
HTTP Result
Browser
Client/server architecture – WEB CLIENT
Plant visualization and operation across the Interne /
Intranet
 Web Navigator Client is a thin client (up to 50 clients)
 View of the plant or manufacturing information for Managers
 Direct plant control by remote diagnostics for example
Safety by several levels of security
 User-specific password
 Firewall technology
 Support of encoded communication
Minimal installation at client side (no entire WinCC system)
Direct use of WinCC pictures for the web
Optimized communications and performance


Optimization of WinCC pictures
Pictures can be transferred directly
Client/server architecture – WEB CLIENT
Web Navigator Server
 Communication to the WinCC Server
 Administration of Access Rights
WinCC Goes Web
Operation and monitoring
of the plant via the
Worldwide Web
Web Navigator Client
 Operation and Monitoring Over the Web
 Limited operator inputs or purely view only function depending
on the access rights
 Minimum installation including WinCC ActiveX controls via
network too
Client/server architecture – SERVER REDUNDANCY
WinCC Clients
WinCC Redundancy:
a Global Concept
Redundant WinCC Server
Redundant
Profibus or
Industrial Ethernet
S7-400-H
WinCC communication
Client/server architecture – communication, OPC
Enhancement of OPC capability by adding functions of
the current V2.0 specification
 Support for Automation and Customer Interface
 Direct access to the Automation Interface via VBA (e.g.
Excel)
OPC Client
OPC Automation Interfaces
OPC Custom Interfaces
OPC Server
WINCC RC
Cross-Reference List
 Listing in table form of tags, pictures, functions ...
 Selective lists
 Central rewiring
 Jump from the cross-reference list to the tags' place of
use
Display of all the dynamic properties of a picture
Dragging and dropping of tags
Rapid rewiring of tags in pictures
WINCC RC