Using standards for easy integration

SIMATIC WinCC all times stands for a high level of openness and integration capability because it is consequently based on standard technologies and software tools.
Starting with its first version SIMATIC WinCC relies on the market leader in the operating system area. It doesn’t matter if you use Microsoft Windows 2008/2012 Server, Windows 7 or Windows 8.1 you can track updates in the operating system. At last for you that offers additionally investment security.
The powerful SQL Server 2008 R2 SP1 (32 Bit) is integrated within the WinCC basis system. Using open interfaces helps you to automatize the engineering as well as the runtime and the access to archive data.


Individual adjustments

Extensions of the runtime system
Using WinCC it is possible to realize connections and dynamic sequences without programming only by the use of standard dialogues. To realize more complex functions it is possible at any time to write scripts using VB or ANSI-C. Examples for such scripts are the conversion of values or the automatic start of reports or of individual messages.
When programming VB scripts you are supported by the use of a proprietary, comfortable editor with debugging support.
When using scripts you have full access to the properties of all WinCC graphical objects and to the controls as well as to the object model of WinCC and the applications of other manufacturers.

Enhancements of the engineering system
Furthermore the comfortable configuration tool Visual Basic for Applications (VBA) is integrated in the WinCC Graphics Designer. This is very helpful for writing custom specific enhancements including debugging. By using this functionality engineers and users can make full use of their Visual Basic-knowledge. VBA can be used to realize own standards, to handle recurring tasks, to create menu entries or configuration dialogues. This saves time and money.

Open programming interfaces

The WinCC function modules are exposed using interfaces which allow access to the data and the functions of the configuration environment as well as to the runtime system itself. Using this interface you are able to apply WinCC-projecting functionality and runtime functions to your scripts or to write autonomous applications with direct access to the WinCC system..

The WinCC/Open Development Kit (ODK) describes the open interfaces which are provided as C-Application Programming Interface (C-API). Starting with WinCC V7.2 the ancient option WinCC/IndustrialX is included in ODK.
Also numerous additional ActiveX-elements and a configuration toolset containing Visual Basic Templates is included for the simple creation of ActiveX-Controls. The development of individual controls supports the creation of industry- and technological functions as protected and standardized modules. This reusable controls shorten your time-to-market and protect your know-how.
Besides of the integration of ActiveX-Controls using the WinCC Media Control (.NET Framework 3.5 & 4.0 Container) the integration of user specific XAML and .NET controls is also supported.



Bidirectional flow of information from shop floor to top floor

WinCC/IndustrialDataBridge is the flexible information hub between automation and the IT world. It reduces the complexity of interfaces and data formats.


Cross vendor communication using OPC (OLE for Process Control)

OPC is used as a communication standard for a secure and authentic data exchange between applications within the industrial automation environment. It describes a series of specifications which are used manufacturer independent as an interface between different clients and servers as well as between different servers only. These include amongst other topics direct access to real-time data, the monitoring of messages and events as well as access to historical data.

Originally the OPC standard only was available on Windows operating systems. This standard was developed from OLE (Object linking and embedding) for Process Control. The new OPC UA spec which was introduced in 2009 describes a real universal connection. This standard is based on a secure, simple technology-independent platform which is future-assured and scalable as well as expandable for all challenges of the different company levels.

SIMATIC WinCC offers by default: an OPC DA-client 2.05a/V3.0 providing access to process data e.g. to connect the system to third-party PLCs or -systems.


WinCC/Connectivity Pack and WinCC/Connectivity Station

The Connectivity options open a series of additional communication possibilities using WinCC OLE-DB Provider OPC.
The option package WinCC/Connectivity Pack every time is used in combination with a WinCC system.
The WinCC/ConnectivityStation  is used with autarchic PCs (without WinCC installation).

  • WinCC OLE-DB Provider
    For direct access to process values and message archives
    It is possible to write individual applications using WinCC OLE DB to get access to the databases. For the communication with the WinCC OLE DB-Provider ADO DB /ADO.NET can be used within applications, which for example are build using Visual Basic, VBScript or VB.NET.

  • OPC XML DA 1.01-Client
    Web based and platform-independent access to process values for example to integrate third-party PLCs or -systems.

  • OPC UA Client 1.02
    Access to process data according to the OPC Unified-Architecture specification.

  • OPC HDA 1.20-Server (Historical Data Access)
    Access to historical data of WinCC for example to share the data for your own proprietary reporting system.

  • OPC A&E 1.10-Server
    Forwarding of WinCC process alarms and events

  • OPC XML DA 1.0-Server
    Platform independent data exchange via web between WinCC and Office-applications, ERP/PPS-systems (e.g. SAP/R3) or Business-to-Business-portals.

  • OPC UA Server 1.02
    Transfer of process values, archive data and messages of WinCC under the terms of the OPC UA specification 1.02  In addition to that a separate licensed OPC UA Server for the connection to the SIMATIC Process Historian is available.