How to Configure Unique Startup Process Pictures and Multi-Screen Layouts on PCS 7 OS Clients

To configure distinct startup process pictures on different SIMATIC PCS 7 OS Clients (e.g., Client 1 opening Area X, Client 2 opening Area Y) and manage multi-monitor arrangements (Monitors 1 through 4), engineers can utilize either user-specific Screen Compositions or computer-name script dispatching. For standard independent OS Clients, the recommended non-programming approach is creating a unique Windows/WinCC user for each client, arranging the desired screens across all monitors, saving the layout as a Screen Composition named 'Default', and enabling WinCC Silent Login. For Referenced Clients (which share a common project configuration), the solution requires scripting: executing a C-action in @Welcome.pdl that reads @LocalMachineName and triggers SSMChangeWorkField to open workstation-specific pictures.

Operational Requirement: Tailored Operator Workstation Displays

In control rooms operating across multiple functional units (e.g., Raw Materials, Kiln, Packing, Utilities):
* Each physical operator console is dedicated to a specific plant section.
* When workstations boot following power interruptions or shift handovers, operators expect their console to immediately render their specific operational overview screens without requiring manual picture navigation.
* Furthermore, multi-monitor workstations (2 to 4 screens) require distinct pictures on each display (e.g., Screen 1 on Monitor 1, Screen 2 on Monitor 2).

Achieving this behavior depends on whether the workstations are configured as Standard OS Clients or Referenced OS Clients.

Method 1: Screen Compositions ('Default') and Silent Autologon

For standard independent OS Clients, PCS 7 Split Screen Manager (SSM) provides native layout persistence without custom scripting:

1. Create Workstation-Specific Users

In WinCC User Administrator, create dedicated operator accounts corresponding to plant consoles (e.g., Operator_Kiln, Operator_Mill).

2. Save the 'Default' Screen Composition

On the physical client workstation, activate WinCC Runtime and log in as Operator_Kiln.
Navigate to and arrange the desired process pictures across all connected monitors (e.g., Monitor 1: Overview, Monitor 2: Trend Group).
In the PCS 7 bottom toolbar, click Screen Composition -> Save As.
Name the composition: Default (exact string, case-sensitive).
When WinCC Runtime launches in the future under this user, Split Screen Manager automatically detects and loads the Default screen composition.

3. Enable Silent Autologon

Configure Windows autologon and WinCC silent login (via SilentLogin.fct or Pass-Through authentication) so the client logs in automatically upon system reboot.

Method 2: Script-Based Startup Dispatching for Referenced Clients

In modern centralized architectures, engineering teams frequently deploy Referenced OS Clients (Ref Clients). Referenced clients share a single, read-only master client project across the network. Because project files are identical, user compositions saved locally cannot distinguish between machines.

The solution is implementing host-based script routing in the startup picture:

In WinCC Graphics Designer, open the base startup picture (e.g., @Welcome.pdl or @Screen.pdl).
In the picture's OnOpen event, add a C-action:
```c
#include "apdefap.h"
void OnOpen() {
char szComputerName[MAX_COMPUTERNAME_LENGTH + 1];
DWORD dwSize = sizeof(szComputerName);
GetComputerName(szComputerName, &dwSize);

// Route startup screens based on physical workstation hostname
if (strcmp(szComputerName, "OSCLIENT01") == 0) {
SSMChangeWorkField(SSMGetScreen("@Screen"), 1, "Area_Boiler_Overview.pdl");
} else if (strcmp(szComputerName, "OSCLIENT02") == 0) {
SSMChangeWorkField(SSMGetScreen("@Screen"), 1, "Area_Reactor_Overview.pdl");
} else if (strcmp(szComputerName, "OSCLIENT03") == 0) {
SSMChangeWorkField(SSMGetScreen("@Screen"), 1, "Area_Utilities_Overview.pdl");
}
}
```
3. This guarantees that each physical workstation opens its designated operational picture while sharing a single centralized project.

Multi-Monitor Positioning via Split Screen Manager (SSM)

For clients utilizing multi-monitor graphics cards (up to 4 screens):

OS Project Editor Layout:
In WinCC Explorer, open the OS Project Editor. On the Layout tab, select the multi-monitor configuration matching the physical display arrangement (e.g., Multi-VGA 2x1 or Multi-VGA 4x1).
Addressing Monitor Workfields:
The function SSMChangeWorkField accepts a monitor index:
* Screen Index 1: Primary monitor.
* Screen Index 2: Secondary monitor.
* Screen Index 3 & 4: Tertiary and quaternary monitors.
This allows script actions to target specific physical displays simultaneously during startup.

Startup Screen Configuration Method Comparison Matrix

The following table compares the two primary startup screen deployment strategies:

Evaluation CriterionScreen Composition ('Default')Script-Based Host DispatchingClient TypeStandard Independent ClientsReferenced Clients & Standard ClientsEngineering EffortLow (Zero scripting)Low (Single C/VBS script)Multi-Monitor SupportNatively preserved in layoutScript parameter specifies monitor indexFlexibilityTied to Windows/WinCC usernameTied to physical workstation hostnameMaintenanceRe-save composition if layout changesModify script when screens are added

Selecting script routing for referenced clients ensures centralized administrative control.

Verification

To verify that client startup pictures function correctly:
1. Power cycle or restart WinCC Runtime on OS Client 1; confirm that it automatically boots directly into Area_Boiler_Overview.pdl.
2. Restart OS Client 2; confirm that it boots directly into Area_Reactor_Overview.pdl.
3. On a multi-screen workstation, confirm that Monitor 1 renders the process overview while Monitor 2 renders the alarm sequence view.
4. Verify that Split Screen Manager navigation buttons remain responsive and allow normal picture hierarchy traversal.

Limitations and Operational Precautions

Do not rename base process pictures without updating corresponding C-script routing strings.
Ensure all client monitors operate at the native resolution configured in the OS Project Editor layout.
In Referenced Client architectures, verify that the master client project is compiled and shared before launching dependent clients.
Always validate final license quantities, client packs, and MLFBs against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why did my 'Default' Screen Composition not load after reboot?

Screen Compositions are stored per user account. If the client logged on under a different username (e.g., Administrator instead of Operator_Kiln), the Default composition for that user does not exist.

Can an operator modify their startup screen layout in Runtime?

Yes, if using Screen Compositions. An operator can rearrange pictures and click 'Save As -> Default', updating their personal startup layout immediately.

What is the difference between SSMChangeWorkField and OpenPicture?

OpenPicture replaces the entire graphic canvas, potentially overwriting title and alarm banners. SSMChangeWorkField opens the picture strictly within the active PCS 7 workfield, preserving top and bottom navigation bars.