How PCS 7 OS Areas and Client Authorizations Follow the Picture Tree
In PCS 7, the OS areas available for client authorization are derived from the Picture Tree Manager hierarchy; the PCS 7 V9.0 manual identifies the second hierarchy level as the OS-area level used for user rights. A client OS Project Editor does not create an independent set of child areas simply by selecting a parent such as CCG. Configure the intended picture hierarchy in the engineering project, then generate and configure the client from that structure.
Table of Contents
- How the area list is derived
- Configure the intended hierarchy
- Avoid editing generated hierarchy by hand
- Authorization is separate from visibility
- Limitations and Operational Precautions
- Verification
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
How the area list is derived
The PCS 7 Operator Station V9.0 Configuration Manual describes the Picture Tree Manager and User Administrator relationship: its second hierarchy level is exposed as OS areas for which user rights can be assigned. The OS Project Editor's visible-area list is likewise based on the configured Picture Tree. Therefore, if the expected CCG subareas are absent in both the OS Project Editor and User Administrator, inspect the engineering hierarchy and compiled OS configuration.
Configure the intended hierarchy
- In the PCS 7 engineering project, inspect the plant hierarchy and the OS picture assignment for CCG and its subareas.
- Confirm that the hierarchy level intended to represent selectable OS areas occupies the supported area level in Picture Tree Manager.
- Recompile/update the OS from the engineering project so the WinCC picture tree and client configuration reflect that source hierarchy.
- In the client OS Project Editor, select or order the areas needed for that client, then configure each user's area-specific rights in User Administrator.
- Confirm the client runtime shows the intended area buttons and that authorization behavior matches the configured rights.
Avoid editing generated hierarchy by hand
The manual warns that subsequent manual changes in Picture Tree Manager can create differences between SIMATIC Manager project data and WinCC Explorer and may be overwritten or not updated on OS recompilation. Treat the PCS 7 engineering hierarchy as the maintained source of the area structure.
Authorization is separate from visibility
Area selection and process-control authorization are different concerns. The OS Project Editor supports choices that affect whether users lacking area rights can select pictures or group displays for monitoring; process controls remain subject to configured operator authorizations. Validate visibility and control permissions separately.
Limitations and Operational Precautions
Confirm version applicability and operational impact before changes to a running control system. Use approved backup, testing, change-control and rollback procedures.
Verification
Verify configuration and observable runtime behavior against the intended process requirements.
Engineer FAQ
Which software version matters? Use the version of the affected product component and its installed update level, not only the parent suite version.
Does administrator access guarantee a feature works? No. Permissions do not establish that the configuration, compatibility, or runtime dependencies are correct.
Can an online forum report establish a universal fix? No. Treat it as an observation unless applicable product documentation confirms the procedure.
What should be recorded before changing configuration? Record the current settings, exact versions, affected station, error text, and event timestamps.
Should configuration be changed on a live system? Use the approved change process and a controlled window when the change can affect process operation.
How can a correction be verified? Check the actual runtime behavior that matters, not only whether a setting was accepted.
Does a feature being visible prove that it is configured correctly? No. Verify the linked object, access rights, and behavior in the intended runtime context.
Should a workaround from another version be copied? No. Confirm it against documentation for the installed release and project configuration first.
What does a needs-review status mean? The article preserves the question and evidence, but its main technical resolution could not be confirmed adequately.
What evidence helps technical support? Provide exact product versions, reproducible steps, relevant logs, screenshots without private data, and a known-good comparison.