310 likes | 647 Views
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.
E N D
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
SCADA Manufacturing Execution System Enterprise Resource Planning
WinCC IDE Tag editor (channels) Alarm/Log editor User editor Report editor Graph editor Global/Local script editor Picture Editor DDE,NATIVE, (TCP/IP, Configurable RT KERNEL WINAPI through DLL DDE OLE ACTIVE X OPC CHANNELS SQL server (SQL ANYWHERE) WIN API
Client/server architecture - MULTICLIENT WinCC Multi Client WinCCServer1 WinCCServer2
Client/server architecture – MULTICLIENT/DISTRIBUTED SERVER Multi Client Visualization Server Trend Server Alarm 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 plant-wide alarm view. WinCC Multi Client Standard Client WinCCServer2
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” I/O field linked to “Server2::Tag2” WinCCServer1 WinCCServer2
Client/server architecture – WEB CLIENT Firewall Web Client 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 WinCC Goes Web Operation and monitoring of the plant via the Worldwide Web • Web Navigator Server • Communication to the WinCC Server • Administration of Access Rights • 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
OPC Client OPC Automation Interfaces OPC Custom Interfaces OPC Server 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)
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