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.
- Archiving
  Overview of the archiving solutions currently available in WinCC OA
- Module PARA
  Graphical interface for editing datapoints and datapoint types.
- Common Name Service (CNS)
  The plantmodel editor can be used for building and modifying data structures such as views and trees based on CNS and use them within projects easily.
- Mass configuration
  Mass configuration in WinCC OA redefines the fundamental principles of setting up a project and subsequent configuration of the huge range of data points.
- SQL Panel
  The SQL panel allows you to enter SQL statements to perform queries on current and archive data in the WinCC OA database.
- 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.
- Correction Values and Laboratory Values
  These panels can be used to change existing values (=correct), query values from and add new values too the HistoryDB and RDB.
- Data Point Groups
  The main purpose of grouping data points is to simplify selection of datapoints and datapoint elements.
- Delayed Alerts
  An alert delay can be configured with delayed alerts. This allows short range changes to be filtered out.
- Relational Databases with Control-ADO
  The DB interfaces in WinCC OA offer the possibility of an access to external databases.
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.
WinCC OA Documentation
Basic information about terms and functions within the documentation.
Disclaimer
A brief clarification of liability exclusions or legal notices.

_lock (Locking)

This config allows you to assign configs of data point elements "write protection". A config thus locked can only be modified by authorized users.

Double-clicking on the "_lock" config opens the "Data point locks" panel. All configs of the respective data point element and its current status are displayed in the column "locked". The appropriate attributes can be found in the Appendix.

When you copy a data point, the _lock config will be copied. The settings of the config will, however, not be copied.

Figure 1. Data point locks panel

Data point lock panel

The combo box at the top contains the data point name and its description or alias.
In order to lock a config click on the column Locked on No for the respective config, the entry changes to Yes and the other columns in the line are filled in.
The name of the manager that ordered the lock (Manager ), its number (Man Num ), and the ID and name of the user who asked for the lock are automatically filled in.
To complete configuration, press Close.

If a config is locked, only the locking manager may write to its attributes, while any manager may still read them. If a manager is stopped, all its locks are cancelled. Locks are not stored in the database and cannot be inherited in the data point. The _lock config cannot be deleted.

Example

You can also set a lock using a dpSet() The config to be locked is specified as the Detail:

dpSet("dp.:_lock.Detail._locked",1)

To cancel the lock:

dpSet("dp.:_lock.Detail._locked",0)

Detail is the name of the config which shall be locked or unlocked. For example:

dpSet("dp.:_lock._original._locked", 0);

dpSet("dp.:_lock._corr._locked", 0);

The _lock config exists if you create a data point and must not be created manually.

In case of redundant systems, please note that if e.g. WCCOActrl -num 1 locks a config on the first host, WCCOActrl -num 2 cannot unlock the config on the other host.