Home
Northbound Interfaces
Your portal to the cloud or supervising systems.
MQTT Publisher
The MQTT publisher provides a northbound data interface for MQTT clients to data point values within the WinCC OA project.
Notes and Restrictions

Version Information
Release Notes, Update information, Certifications and Frequently Asked Questions.
Concepts
Your first step into modern and powerful process visualization.
Deployment
Topics, you need to know, before using WinCC OA.
Security
Go beyond the norm in cybersecurity.
Engineering
Powerful tools for easy or complex engineering tasks.
Data Management
Classify, structure and archive your data.
Business Logic / Control
Endless possibilities in data processing for your projects.
Data Visualization
User interfaces, Trends and Reports for every purpose and device.
Southbound Interfaces
The process connection to the actual machines/sensors.
Northbound Interfaces
Your portal to the cloud or supervising systems.
- MQTT Publisher
  The MQTT publisher provides a northbound data interface for MQTT clients to data point values within the WinCC OA project.
  - Requirements and Installation
  - Configuration of the MQTT Publisher
  - Data Access for the MQTT Publisher
  - Internal data points of the MQTT Publisher
  - Notes and Restrictions
  - [mqttpub]
    Settings for the MQTT Publisher.
  - How-To
- Node-RED
  Node-RED is a flow-based programming tool that allows the creation of applications in a graphic environment.
- OPC UA Server
  The WinCC OA OPC UA Server provides an OPC UA interface to access WinCC OA data point values, alarms and historical data.
- OPC Server
  The OPC Server enables the communication with OPC clients.
- OPC HDA Server
  The WinCC OA OPC Historical Data Access (HDA) Server is used for the exchanging of archived process data of the WinCC OA project.
- OPC Alarms & Events
  OPC Alarms & Events (brief OPC A&E) is in addition to the Data Access another standard in order to implement a central alert management manufacturer spanning. OPC A&E is used to guarantee the coupling with other control systems as well as to display alerts and events in a hierarchical system
- Modbus/TCP Server
  The Modbus/TCP server provides the possibility for Modbus/TCP clients to query data from a WinCC OA system and arrange the data within a Modbus data model.
- SNMP
  SNMP (Simple Network Management Protocol) is a protocol for monitoring network devices (servers, workstations, routers, switches and hubs etc.) and their functions. It allows you to administer your network.
- OLE DB Provider
  OLE DB is a Microsoft specification for accessing data on different computers. It is based on Microsoft's COM technology and is the successor to the older and limited ODBC technology.
Web Connectivity / Network Interfaces
Data exchange, APIs and web technologies
User Management
All about authorization, authentication and login-customization.
Availability
How to get your system uptime to the maximum.
Reporting
Create state of the art project reports without limits.
Addons
Useful tools and enhancements for special demands.
Reference Tables
Detailed and extensive content for special project adaptation.
Videos & Tutorials
Explore the capabilities of WinCC OA with our carefully selected collection of video tutorials and guides.
WinCC OA Documentation
Basic information about terms and functions within the documentation.
Disclaimer
A brief clarification of liability exclusions or legal notices.

Notes and Restrictions

MQTT Version 5.0

Following information must be considered when using MQTT Version 5:

When using topic aliases with MQTT Version 5 the used broker must support 65535 maximum topic aliases, otherwise the connection will be unstable. If the broker does not support the usage of 65535 topic aliases it is recommended to disable topic aliases in general.
Shared subscriptions are not supported.

Redundancy

Following information must be considered when using the MQTT Publisher in a redundant environment:

Only the MQTT Publisher of the active redundancy partner publishes data to the broker.

CNS Display Name as MQTT Topic Name

By using the config entry [mqttpub] useCnsDisplayPath it can be defined whether the CNS name or the general display name in the active language, is used for MQTT topic names.