Home
Data Visualization
User interfaces, Trends and Reports for every purpose and device.
Standard Object Library
The WinCC OA Standard Object Library (in short: Stdlib) is a base framework that facilitates the creation and use of WinCC OA Libraries. The Stdlib provides templates for creating WinCC OA Libraries and offers a vast range of functions that make the use of a WinCC OA Library in a WinCC OA project easier.
User Authorization in the StdLib

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.
- User Interfaces
  All the available options for visualizing WinCC OA.
- System Overview
  A panel for the diagnostics of a WinCC OA system.
- Alert and Event Screen (AEScreen)
  The alert and event panel (AEpanel) in WinCC OA is a standard panel and allows displaying alerts and events in table format.
- Variable Trend
  A set of panels and scripts used for the simplified display of trend curves and trend groups (up to 16 trend curves).
- Standard Symbols (STD_Symbols)
  Symbol library consisting of graphics objects for the quick display and design of system diagrams.
- Standard Object Library
  The WinCC OA Standard Object Library (in short: Stdlib) is a base framework that facilitates the creation and use of WinCC OA Libraries. The Stdlib provides templates for creating WinCC OA Libraries and offers a vast range of functions that make the use of a WinCC OA Library in a WinCC OA project easier.
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.

User Authorization in the StdLib

The Stdlib defines whether a value/state of a certain elementary symbol (referenced via a datapoint element) in the faceplate is only visualized for the library user (read access) or if the user can also change this value/state (write access).

The authorizing concept in the Stdlib depends on the authorization that was configured in the WinCC OA user administration (see the WinCC OA online help under System Management -> Authorization levels). The authorizing concept in the Stdlib can de divided up in three levels.

The project HOOK function hook_hasUserAuthorization() is called. It returns 1, if the user has the necessary authorization, 0 if the user has no authorization, or < 0 if the HOOK function was not implemented.
If the HOOK function hook_hasUserAuthorization() was not implemented, the corresponding datapoint element (to which the elementary symbol references) is checked, to see whether the authorization datapoint config _auth is available. If it is available, the corresponding authorization level is checked.
If the authorization datapoint config _auth is not available, the authorization test takes place via the node name of the data point (see table below). This applies to datapoint elements located under the nodes alarm/cmd/command/para/state/. These nodes belong to the StdLib datapoint type structure. For how to create an StdLib datapoint type - see chapter How to Create Datapoint Types for the StdLib.

The user must possess the following authorization levels (bits) in order to access the datapoint elements:


Node Name	Authorization bit	Authorization
ALM or alarm	5	Allows the acknowledgement of alerts.
STA or state	2	Normal operator authorization
CMD or command	2	Normal operator authorization
PAR or para	3	Advanced operator authorization: permits execution of commands, explicit setting of replacement values, input of correction values as well as changes to all value range types.

If the user does not have the necessary authorization bit, then the values/states of the datapoint element in the faceplate are only visualized - the associated elementary symbol is inactive.