Configuring the Default Runtime Startup Screen and Navigation Topology in SIMATIC PCS 7 WinCC

In SIMATIC PCS 7 WinCC (v7.x to v9.x), configuring which process graphic displays automatically on startup is managed either through the WinCC OS Project Editor layout properties or the Picture Tree Manager. When using standard PCS 7 plant navigation, opening Graphics Designer and renaming the startup screen breaks the internal hierarchy. To define or change the startup screen correctly, open the OS Project Editor on the Engineering Station, designate the default start picture in the 'Runtime Window' settings, configure the desired root node in Picture Tree Manager, and perform an OS compile to propagate the navigation topology.

PCS 7 OS Screen Navigation Architecture and Picture Tree Manager

Unlike standalone WinCC projects where a single graphic file is set as the startup picture, SIMATIC PCS 7 uses a standardized multi-monitor layout template (@Screen.pdl, @Overview1.pdl):
* OS Project Editor: Deploys standard PCS 7 screen layouts (e.g. SIMATIC Standard 1920x1080, multi-screen client arrangements). It generates the master frame containing the Overview Area, Working Area, and Button Bar.
* Picture Tree Manager: Manages the hierarchical plant navigation tree. It links pictures (*.pdl) to specific technological areas defined in the SIMATIC Manager Plant Hierarchy.
* Start Screen Logic: When WinCC Runtime activates, the system script @1001.pdl queries the Picture Tree to determine which picture to load into the primary Working Area container (@Area_Top.pdl).

Root Causes of Broken Startup Screens and Topology Errors

When an engineer rearranges equipment or alters the startup display:
1. Directly Renaming Template Pictures: Renaming @Overview1.pdl or manually modifying the WinCC Computer Properties 'Start Picture' field breaks the PCS 7 frame architecture, resulting in empty toolbars or missing alarm banners.
2. Unsynchronized Picture Tree: Creating a new overview picture in Graphics Designer without saving it inside Picture Tree Manager causes runtime to default to the first alphabetical picture or display a gray screen.
3. Plant Hierarchy Overwrite: In PCS 7 projects using Plant Hierarchy mapping, compiling the OS without checking 'Picture Tree' overwrites manual picture tree customizations.

Step-by-Step Startup Screen Configuration Workflow

Follow this procedure to configure the startup screen correctly:

[Phase 1: Configure Plant Hierarchy and Assign Pictures in SIMATIC Manager]
   │  • In SIMATIC Manager Plant View: Navigate to the top-level plant folder
   │  • Right-click -> Insert New Object -> OS (Picture)
   │  • Assign the picture name (e.g. "Plant_Overview.pdl")
   │  • Open the picture in Graphics Designer; construct the plant topology graphic
   │
[Phase 2: Configure Picture Tree Manager in WinCC Explorer]
   │  • In WinCC Explorer, double-click "Picture Tree Manager"
   │  • Ensure "Plant_Overview.pdl" is placed at the very top of the hierarchy tree
   │  • Select menu: Options -> "Recalculate..." -> Save and close
   │
[Phase 3: Verify OS Project Editor Settings]
   │  • In WinCC Explorer, open "OS Project Editor"
   │  • Select tab: "Runtime Window"
   │  • Verify that the primary monitor is configured to display the root node
   │  • Click "OK" to compile screen management scripts
   │
[Phase 4: Compile OS from Engineering Station]
   │  • In SIMATIC Manager: Right-click OS object -> "Compile"
   │  • Select scope: "Tags and messages" and check "Picture Tree"
   │  • Download to target OS -> Runtime launches with the new startup screen!

Screen Configuration and Navigation Methods Matrix

Compare screen configuration approaches in SIMATIC PCS 7:

Configuration ToolPurpose in PCS 7Recommended Modification ScopeRisk if Configured IncorrectlyOS Project EditorManages monitor resolution, frame scriptsInitial station setup and screen resizingOverwrites custom @*.pdl template files.Picture Tree ManagerDefines hierarchical menu and area keysAssigning process pictures to areasBroken navigation buttons; missing area alarms.Plant Hierarchy (ES)Master equipment model and picture creationTechnological picture structureOverwrites offline Picture Tree during compile.WinCC Computer PropertiesBase runtime startup configurationLeave default (@Screen.pdl)Catastrophic: Destroys PCS 7 UI frame.

Verification

To confirm that the startup screen launches properly:
1. In WinCC Explorer, activate Runtime.
2. Verify that the PCS 7 screen shell loads, displaying the top alarm banner, working area, and bottom button bar.
3. Confirm that the primary Working Area container automatically opens the designated Plant_Overview.pdl without requiring operator selection.
4. Verify that clicking sub-area buttons on the overview screen navigates cleanly to unit detail graphics.
5. Confirm that area-specific alarm aggregation works accurately across the top overview row.

Limitations and Operational Precautions

Never change the 'Start Picture' field in WinCC Explorer -> Computer Properties -> Properties -> Graphics Runtime from @Screen.pdl to an individual process picture (Plant_Overview.pdl). Doing so bypasses the entire PCS 7 runtime engine, disabling the alarm line, horn management, user logon dialogs, and loop-in-alarm navigation. Always allow @Screen.pdl to govern layout loading.

Engineer FAQ

Why did my top alarm banner disappear after changing the startup picture?

You set your custom picture directly as the main startup picture in Computer Properties, which bypassed the PCS 7 master template @Screen.pdl. Revert Computer Properties to @Screen.pdl.

How do I configure a multi-monitor client to show different startup screens on each monitor?

In OS Project Editor -> 'Runtime Window' tab, configure Monitor 1 to display the Plant Overview and Monitor 2 to display the Alarm List or secondary process area.

Why does OS Compile reset my Picture Tree changes?

If the Plant Hierarchy option 'Derive picture hierarchy from the plant hierarchy' is enabled, the compiler overwrites manual edits. Perform hierarchy arrangements directly in SIMATIC Manager Plant View.