Configuring Pop-Up Process Screens with Automated Block Icon Generation in PCS 7 OS

In SIMATIC PCS 7 OS, moving operating block icons into a pop-up window while retaining the automated 'Create/update block icons' functionality during OS compilation requires structuring the Plant Hierarchy. Create a dedicated sub-hierarchy folder under the plant unit, assign the pop-up picture (@Sub_Popup.pdl) as its OS picture, and place the target CFC charts inside that sub-folder. During OS compilation, block icons are automatically generated and updated inside the pop-up picture, which can then be opened dynamically via a button script.

Architecture of Plant Hierarchy-Driven Block Icon Placement

In SIMATIC PCS 7 Operator Stations, standard operating practice dictates that process overview screens should not be overcrowded with dense clusters of secondary analog indicators or auxiliary manual control blocks. Automation engineers frequently need to place auxiliary operating blocks (such as manual valve overrides, secondary temperature indicators, or tuning parameters) into a small, floating Pop-Up screen (.pdl) that appears only when the operator clicks a dedicated button.

However, an engineering dilemma arises:
* If the engineer manually cuts block icons from the main process screen and pastes them into a custom pop-up picture, the next Compile OS sweep with Picture Tree enabled will detect that the icons reside in an unauthorized screen, deleting them or re-instantiating them back onto the main screen.
* If the engineer disables block icon creation on the CFC blocks, the icons decouple from the master library (@PCS7TypicalsAPL.pdl), losing automatic tag updating and style inheritance.

To preserve 100% automated block icon creation and lifecycle updates, the pop-up window must be formally integrated into the Plant Hierarchy (PH) as a subordinate child node.

Screen Hierarchy and Pop-Up Window Design Matrix

Evaluate how the Plant Hierarchy determines block icon placement across main screens and pop-up dialogs:

Hierarchy LevelTechnological DesignationAssigned OS Graphic PictureContained CFC ChartsOS Compiler BehaviorLevel 2 (Parent)Area_01 / Reactor_UnitReactor_Overview.pdlMain technological equipment (Pumps, Valves, Agitator)Automatically generates primary block icons into overview screenLevel 3 (Child)Area_01 / Reactor_Unit / Aux_ControlsReactor_Aux_Popup.pdlAuxiliary sensors, secondary manual valves, tuning blocksAutomatically generates auxiliary block icons into pop-up screenStandalone PDLUnassigned pictureCustom_Window.pdlNoneIgnored by OS Compiler; manual icon placement required

Design standard: Subordinate hierarchy folders allow automated icon management for modular screen designs.

Configuring Plant Hierarchy Subfolders for Pop-Up Pictures

Follow this verified configuration sequence in SIMATIC Manager:

Create Sub-Hierarchy Folder in Plant View:
* Open the project in Plant View.
* Locate the technological unit folder (e.g., Reactor_1).
* Right-click Reactor_1, select Insert New Object > Hierarchy Folder.
* Name the folder Auxiliary_Popup (or Manual_Controls).
Assign OS Picture to the Subfolder:
* Right-click Auxiliary_Popup, select Insert New Object > Picture.
* Name the picture Reactor_Aux_Popup.pdl.
* Open the picture properties and verify that OCM Possible is checked.
Move Target CFC Charts:
* Drag the auxiliary analog and digital monitoring CFC charts (e.g., MonAnL, OpDi01) from the parent folder into the new Auxiliary_Popup folder.
Configure Pop-Up Window Canvas Dimensions:
* Open Reactor_Aux_Popup.pdl in Graphics Designer.
* In Object Properties, set the canvas geometry to compact pop-up dimensions (e.g., Width = 600, Height = 400).
* Save and close the picture.
Execute OS Compilation:
* Run Compile OS with Picture Tree checked (Scope: Changes only).
* The compiler opens Reactor_Aux_Popup.pdl and automatically instantiates and aligns the block icons inside the pop-up canvas.

Implementing Button-Triggered Modal Pop-Up Windows in WinCC

To open the compiled pop-up picture from the main process screen:

Place a Command Button on the Main Overview Screen:
* Open Reactor_Overview.pdl in Graphics Designer.
* From the Windows Objects palette, drag a Button onto the canvas.
* Label the button: Auxiliary Controls (or More...).
Configure Button Mouse-Click Action:
* Use the Dynamic Wizard > Picture Functions > Open Picture in Picture Window, or attach a standard C-Action:
c #include "apdefap.h" void OnClick(char* lpszPictureName, char* lpszObjectName, char* lpszPropertyName) { // Configure and display floating picture window SetVisible(lpszPictureName, "PicWindow_Aux", TRUE); SetPictureName(lpszPictureName, "PicWindow_Aux", "Reactor_Aux_Popup.pdl"); }
Configure Close Button in Pop-Up:
* In Reactor_Aux_Popup.pdl, add a small close button (X) in the top right corner with C-Action:
c SetVisible(lpszPictureName, lpszObjectName, FALSE);

Verification

Verify automated generation and runtime pop-up execution:
1. Make a tag or range modification to an auxiliary CFC block in SIMATIC Manager.
2. Run Compile OS: Confirm that compilation updates Reactor_Aux_Popup.pdl without errors.
3. Activate WinCC Runtime and navigate to Reactor_Overview.pdl.
4. Click the Auxiliary Controls button:
* Confirm that the compact pop-up window immediately opens centered on screen.
* Verify that all auxiliary block icons display live, updating process values.
* Click an icon inside the pop-up: Confirm that the standard APL faceplate opens properly.

Limitations and Operational Precautions

In the Plant Hierarchy, ensure the sub-folder is configured so that it does not generate an unwanted top-level navigation button in @Overview1.pdl if navigation should be restricted to the button click.
Picture windows used as pop-ups must have their property Adapt Picture enabled to prevent scrollbars from obscuring block icons.
Do not exceed 20 to 30 dynamic block icons per pop-up window to maintain near-instantaneous pop-up display times (< 200 ms).

Engineer FAQ

Will running OS compilation overwrite my button on the main screen?

No. The OS Compiler only updates block icons and picture tree navigation; custom buttons, pipes, and static graphics placed by the engineer are preserved.

Can multiple main screens share the same pop-up window?

Yes, but if the pop-up contains compiler-generated block icons, those icons belong strictly to the CFC charts located in that specific Plant Hierarchy folder.

How do I prevent the sub-hierarchy folder from appearing in the Picture Tree overview bar?

In the Plant Hierarchy properties of the folder, uncheck the option 'Derive picture hierarchy from the plant hierarchy' or hide the node from runtime navigation.