Configuring WinCC User Archive Control Column Persistence and User Authorization in SIMATIC PCS 7

In SIMATIC PCS 7 and WinCC, User Archive Control column selections and view configurations fail to persist when the active Windows or WinCC user lacks explicit authorization levels defined in the User Archive Editor, or when runtime grid customization is discarded upon picture reload. To resolve this, configure the user's authorization level (e.g., Level 5 'Process Operations' or Level 6 'Higher Process Operations') under both Archive Properties and individual Field Properties in the User Archive Editor, and ensure the UserArchiveControl properties in Graphics Designer have 'Save Configuration on Exit' or persistent grid template definitions enabled.

WinCC User Archive Control Architecture and Access Rights

The SIMATIC WinCC User Archive option provides relational recipe and batch parameter storage directly within the WinCC Microsoft SQL Server database. In SIMATIC PCS 7 V8.2 and WinCC V7.4, operators interact with these datasets via the WinCC UserArchiveControl ActiveX or .NET control embedded in graphic pictures (.pdl).

A common engineering problem arises when specific operator accounts log into WinCC Runtime and view the User Archive screen: the control appears blank or completely devoid of columns, giving the false impression that recipes have vanished. Meanwhile, administrator accounts on the exact same client display all archive data and columns perfectly. Even when the operator manually selects columns in the runtime properties dialog and clicks 'Apply', the columns immediately deselect and vanish.

Diagnosing Empty Columns and De-selected Grid Views

This behavior is governed by a two-tiered security mechanism in WinCC:

User Archive Editor Field-Level Authorization: Within WinCC Explorer > User Archive, every archive has general 'Read right' and 'Write right' attributes. Crucially, every individual column (field) within the archive also possesses independent 'Read right' and 'Write right' properties. If an operator has authorization for the archive itself but lacks the authorization level assigned to the fields, the control loads the archive container but strips all fields from the view.
Runtime View Persistence Mechanism: Runtime adjustments made through the control configuration dialog are user-specific and temporary unless the control's properties allow runtime persistence, or unless the user has administrative permission to update the underlying WinCC picture layout.

Configuring User Administrator and Field-Level Security

To establish proper authorization hierarchy in WinCC User Administrator:

Audit User Rights in User Administrator: Verify which authorization numbers (e.g., Right 1 'User Administration', Right 5 'Process Operations', Right 6 'Higher Process Operations', Right 1000 'Recipe Management') are granted to the operator's group.
Audit User Archive General Rights: In User Archive Editor, right-click the target archive, select Properties, and inspect the Authorization tab. If 'Read right' is set to an authorization number not possessed by the operator, access is blocked.
Audit Field-Level Rights: Expand the archive in the tree, select each field (column), open its properties, and check the Read right and Write right. Often, an engineer creates new recipe fields and assigns them to authorization level 6 or a custom right, while the operator only possesses level 5.

Step-by-Step Resolution and Persistence Setup

Follow this procedure to permanently resolve column visibility and persistence:

Align Authorization Levels: In WinCC Explorer, open User Administrator. Assign the required authorization right (e.g., Right 5 or a dedicated 'User Archive' right) to the operator user group.
Update Field Permissions: Open User Archive Editor. For each archive and every constituent field, ensure the 'Read right' and 'Write right' match the operator's group permission.
Configure Control in Graphics Designer: Open the recipe picture (.pdl) in Graphics Designer. Select the WinCC UserArchiveControl.
Define Default Columns: In the control properties, navigate to Columns. Add all required fields to the visible columns list in the design environment. Do not rely on operators adding columns at runtime.
Enable Toolbar Restrictions: In Toolbar Properties, ensure operators can sort, filter, or edit records as permitted, but disable the column selection dialog if operators should adhere to a standardized corporate recipe format.
Save and Deploy: Save the graphic picture and compile OS / download to clients or servers.

User Archive Control Configuration Matrix

The following table details authorization parameters and runtime behaviors in WinCC User Archive:

Configuration ParameterLocation in WinCCDefault SettingImpact on Operator ViewRecommended PracticeArchive Read RightUser Archive Editor > Archive Properties0 (No authorization required)If non-zero, blocks entire archive visibilitySet to operator authorization level (e.g., Level 5)Archive Write RightUser Archive Editor > Archive Properties0 (No authorization required)Blocks recipe creation, edit, and deletionSet to supervisor authorization level (e.g., Level 6)Field Read RightUser Archive Editor > Field Properties0 (Inherit / Open)Strips column from grid if operator lacks rightSet to 0 or match Archive Read RightField Write RightUser Archive Editor > Field Properties0 (Inherit / Open)Makes column read-only in table gridProtect setpoints while allowing batch note entryVisible ColumnsGraphics Designer > Control PropertiesEmpty / AllDefines baseline layout across all clientsHardcode standardized columns in .pdl

Verification

Verify the User Archive configuration using the following steps:

Log into WinCC Runtime on an OS Client using the operator credentials.
Open the recipe screen containing the User Archive Control. Verify that all expected columns (e.g., Recipe ID, Batch Name, Setpoint 1..N) appear immediately with values populated.
Test modifying an editable field and verify that the data persists to the SQL database upon pressing Enter or clicking Save.
Switch users to another account and back to the operator account; confirm that the column widths and visibility remain stable and intact.

Limitations and Operational Precautions

Consider these operational rules when managing User Archives:

In a redundant OS server configuration, always edit User Archives on the Engineering Station and download the project. Never edit the SQL tables directly via SQL Server Management Studio on runtime servers, as this bypasses the WinCC redundancy synchronization triggers.
User Archive licenses are capacity-based (e.g., 500 archive tags); ensure your WinCC User Archives license covers the total count of active fields configured across all archives.
Changes to archive structure (adding/deleting columns) require closing all active client pictures to prevent schema lock collisions in SQL Server.

Engineer FAQ

What happens if a client loses network connection while editing a recipe in User Archive Control?

The edit transaction is aborted, and uncommitted edits are discarded. The database retains the last committed values, preventing partial or corrupted recipe states.

Can User Archive records be exported to CSV directly from the runtime control?

Yes, the WinCC UserArchiveControl toolbar includes an Export button that outputs the current archive or filtered view to a CSV or text file on the local station.

How do I backup User Archive data independently of OS runtime archives?

Use the User Archive Editor export utility in WinCC Explorer, or execute the standard WinCC C-script function uaArchiveExport() to save records into an ASCII file on a scheduled basis.