Home
Engineering
Powerful tools for easy or complex engineering tasks.
System Management
The System Management is the central administrative unit for WinCC OA Systems.
Database
NextGen Archiver (NGA)
The NextGenArchive (NGA) for is a archiving solution which extends flexibility while keeping the possibilities and strengths of the current methods. This chapter provides an overview of the NGA feature.
Configuration
Backend
Extended Settings
Backend configuration (database-specific settings)
General configuration for all backends

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.
- Project Administration
  The chapter contains a description of the process monitor as well as the project administration.
- Graphics Editor (GEDI)
  Used for creating and editing panels, provides tools for creating and configuring graphic objects.
- System Management
  The System Management is the central administrative unit for WinCC OA Systems.
  - System management
  - Diagnostics
  - Reports
  - Database
    - Data backup in WinCC OA
    - Supported Database Combinations
      An overview over the possible database combinations within a WinCC OA project.
    - WCCOAtoolCreateDb
    - Estimation of the hard disk space
    - Update an ISO Project to SQLite Project
    - History DB
    - Archive/Export Alerts
    - ASCII Manager
      The ASCII Manager allows you to input and output and thus edit data points and data point types and to configure data points.
    - Archiving and Compression
    - Data Point Groups
      The main purpose of grouping data points is to simplify selection of datapoints and datapoint elements.
    - PowerConfig Editor
    - RDB Archiving
    - RDB Compression
    - RDB Log
    - HDB/RAIMA - RDB Parallel
    - 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.
    - NextGen Archiver (NGA)
      The NextGenArchive (NGA) for is a archiving solution which extends flexibility while keeping the possibilities and strengths of the current methods. This chapter provides an overview of the NGA feature.
      - General Terms and User Model
      - Requirements and Installation
      - Licensing
        This chapter describes the NGA license options and available package sizes.
      - Deployment Scenarios
      - Configuration
        Frontend
        Backend
        Backend List
        General Settings
        Extended Settings
        Database Control
        Buffering Parameters
        Memory Buffering
        Disk Buffering
        Communication
        Database Parameters
        Backend configuration (database-specific settings)
        General configuration for all backends
        PostgreSQL®
        InfluxDB®
        MS SQL®
        Redundant Overview
        Distributed System Settings
        Profile
        General
        Archive Groups
        Data/Segment Management
        Event/Alert Archiving
      - InfluxDB®
      - PostgreSQL® Database Overview
      - MS SQL®
      - Redundancy
      - Using a Remote Backend with Encryption
      - Notes and Restrictions
      - Internal Data Points
      - Database Maintenance
        Overview of the database maintenance chapters for the NGA backends.
      - Estimation of the hard disk space
      - Debug Flags
      - CTRL Functions for NGA Access
      - HDB/RAIMA Migration
      - NGA Importer
      - NextGen Archiver (NGA) - FAQ
    - SQLite®
  - Driver
  - Driver IEC
  - Driver OPC
  - Driver S7
  - SmartSCADA
  - Permission
  - Communication
  - Settings
- Wizard Framework
  Used for easy creation of wizards in a uniform layout style. The key elements "Navigation Bar" and "Bottom Bar" can be customized to fit the needs of the custom wizard.
- XML Panel Format
  The XML (Extensible Markup Language) panel format allows creating WinCC OA panels.
- Simple Symbols, basics
  The "Simple Symbols" functionality is used to simply assign corresponding symbols to data point types and increase the working comfort when working with different symbols.
- ScriptWizard
  Simple wizard for creating graphical user interfaces for users without prior programming knowledge.
- Panel topology/Group alert facility
  Tree structure for process panels with integrated group alert system
- Object-Oriented Panel References
  Reusable objects built with the GEDI tools. Insert them within an existing panel to provide a graphical element.
- Multilingual Projects
  WinCC OA is designed to provide both Native Language Support and Multi Language Support.
- Translator
  The WinCC OA Translator functionality supports you in creating and maintaining multilingual projects. It offers a convenient interface for translation of reusable terms.
- Layout management
  Layouts change the size and position of objects according to parameters previously defined in the GEDI.
- Generic Dialog Framework
  The Generic Dialog Framework is an easy way to generate your own dialogs by adjusting a set of prefabricated panels.
- Simple Configuration
  Simple configuration windows and panels support you in combining events (such as a mouse click) with different actions such as setting data point values, showing panels or changing attributes.
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.
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.
Documentation
Basic information about terms and functions within the documentation.
Support & Services
An experienced team of support agents, consultants and trainers are ready to facilitate active partnerships with our customers, so they can profit from our comprehensive service.
Disclaimer
A brief clarification of liability exclusions or legal notices.

General configuration for all backends

This chapter contains the common settings for the databases PostgreSQL® and MS SQL®.

This list of values are key/value pairs for the configuration of these settings. The names (keys) are predefined by the backend in backend profile - see configuration of the backend profile. The further chapters are database-specific for the three different databases InfluxDB®, PostgreSQL® and MS SQL®.

Figure 1. Database-specific Configuration - Example PostgreSQL®

Logger for PostgreSQL® and MS SQL®

logger.level - the level of the log messages that produce the backend. Possible values are "trace", "debug", and "info", "warn" and "error".

The default value is "info".
logger.logProtobufMessages – Set this flag to 1 for logging protobuf messages from/to frontend.

The default value is 0.
logger.logToStdOut - Set this flag to 1 for logging parameters of the DB queries.

The default value is 0.

logger.logSql - Set this flag to 1 for logging SQL messages to DB. The default value is 0.
logger.logSqlBindedParameters - Set this flag to 1 for logging parameters of the DB queries. The default value is 0

Backend configuration for PostgreSQL® and MS SQL®

backend.readThreadsNumber - size of thread pool for reading threads.

The default is the number of CPU cores running on the computer. The backend splits read requests according to archive groups of requested elements.

Each read request for a given archive group is executed in a separate thread. The size of the thread pool defines maximum threads that might be used simultaneously for handling read requests.

If a value smaller than one is specified, the default value is used.

For new PostgreSQL® databases created via a new project, the entry max_parallel_workers in the file postgresql.conf is set to the number of cores running on the computer.
Once this has been done, the number of read threads in the PostgreSQL® backend (backend.readThreadsNumber) is adjusted to this number. This is only done for the standard backend _NGA_B_PostgreSQLBackend and is neither adjusted for other backends nor for existing projects.

With these settings, the performance is improved for many parallel queries, for example in projects with many data point functions.
backend.writeThreadsNumber - size of thread pool for writing threads. The default value is 50. If a value smaller than one is specified, the default value is used.