Importing Standalone WinCC Projects into SIMATIC PCS 7 Multiprojects

Integrating an independently created standalone WinCC project (containing custom process pictures, internal tags, user scripts, and global settings) into a SIMATIC PCS 7 Multiproject is natively supported using the "OS Import" function in SIMATIC Manager. Rather than manually copying graphic files or recreating project settings, selecting "Options -> OS Import..." allows engineers to browse to the standalone WinCC project file (.mcp) and import it directly into the Multiproject as a fully managed Operator Station. Once imported, the PC Station can be integrated with the S7-400 automation station in NetPro using Named Connections, preserving all pre-engineered graphic pictures and internal tag dictionaries.

Standalone WinCC vs Integrated PCS 7 OS Architecture

In engineering projects where electrical contractors or third-party integrators develop human-machine interface (HMI) screens independently of the controller program, teams frequently end up with two separate artifacts:
1. A SIMATIC PCS 7 Multiproject managing the S7-400 / CPU 410 controller logic, Plant Hierarchy, and fieldbus I/O.
2. A Standalone WinCC Project containing customized process screens (.pdl), user archives, complex C/VBS scripts, navigation headers, and internal tags.

Simply copying .pdl files into a newly created PCS 7 OS project fails because graphic screens rely on the standalone project's internal tag management tables, global script modules (.fct / .bmt), and security user accounts.

To unify these environments, SIMATIC Manager provides the native OS Import utility, which encapsulates the entire standalone WinCC project directory into the PCS 7 Multiproject structure.

Prerequisites for Importing Standalone WinCC Projects

Before executing the import into SIMATIC Manager:

Validation AreaRequirement / CheckRisk if IgnoredSoftware Version CompatibilityStandalone WinCC version must match PCS 7 integrated WinCC version (e.g., WinCC V7.4 SP1 for PCS 7 V9.0)Project cannot open; database conversion errorProject StateStandalone project must be fully closed; WinCC Runtime deactivatedFile copy collisions; database lock errorsPC Station Name AlignmentComputer name configured in standalone WinCC must be updated to target PC stationCommunication channel cannot resolve local hostExisting OS StationsExisting OS stations in Multiproject do not need to be deleted; Multiproject supports multiple OS objectsOverwriting existing valid engineering

If the standalone project was built in an older version of WinCC (e.g., WinCC V7.2 imported into PCS 7 V8.2), migrate the standalone project using the WinCC Project Migrator tool before performing the import into SIMATIC Manager.

Step-by-Step OS Import Procedure in SIMATIC Manager

To import the standalone WinCC project:

Close Standalone WinCC: Ensure WinCC Explorer is closed on both the source and engineering stations.
Execute OS Import in SIMATIC Manager:
- Open SIMATIC Manager and open the target Multiproject.
- Select the top-level Multiproject or target user project folder.
- Navigate to the menu: Options -> OS Import....
- In the file selection dialog, browse to the directory containing the standalone project and select the project file: <ProjectName>.mcp.
- Click Open.
Automated Directory Duplication:
- SIMATIC Manager duplicates the entire WinCC project folder into the Multiproject file structure on disk (<Multiproject_Path>\<OS_Name>\).
- A new Operator Station object (represented by a PC Station icon with a WinCC monitor) is created in the Component View.
Rename and Reassign:
- Rename the imported OS object to match the planned physical computer name (e.g., OS_CLIENT_02 or OS_SRV_SINGLE).

Configuring NetPro Named Connections and OS Project Editor

To enable the imported OS to communicate with the S7-400 controller:

Establish Communication in NetPro:
- Open NetPro in SIMATIC Manager.
- Select the imported WinCC PC Station.
- In the connection table, insert an S7 Connection (or Named Connection) pointing to the S7-400 CPU.
- Save and Compile NetPro.
Handle OS Project Editor:
- Open WinCC Explorer on the imported OS.
- Critical Decision: If the project consists of non-APL custom screens (buttons and direct DB tags), running OS Project Editor will overwrite custom screen frames. If custom screen layouts are used, do NOT run OS Project Editor with default settings; configure the Basic Data tab to preserve custom pictures.
- In WinCC Tag Management, create an S7 Named Connections channel pointing to the connection configured in NetPro to link the imported screens to controller Data Blocks.

Verification

To verify successful OS integration:
1. In SIMATIC Manager Component View, confirm that the imported OS appears under the PC Station with a valid WinCC Application.
2. Open the imported project in WinCC Explorer; confirm that all graphic pictures, internal tags, and script libraries are present.
3. Start WinCC Runtime; verify that buttons toggle Data Block tags in the controller and that live status animations function accurately.
4. Download the OS project to the target operator machine; confirm that runtime launches without project path errors.

Limitations and Operational Precautions

Importing a standalone WinCC project does not automatically convert its custom screens into PCS 7 Advanced Process Library (APL) faceplates. If the standalone project used direct DB addressing (e.g., DB10.DBX0.0) rather than PCS 7 tag naming conventions, those tags must continue to be mapped to manual S7 connection channels rather than relying on automated OS compile.

Engineer FAQ

Does importing a WinCC project delete existing OS stations in the Multiproject?

No. A SIMATIC PCS 7 Multiproject can host multiple independent OS Servers, OS Clients, and Single Stations simultaneously. The imported project is added as an additional OS object.

Can a WinCC project created in TIA Portal be imported via 'OS Import'?

No. 'OS Import' only supports classic SIMATIC WinCC V6.x and V7.x projects (.mcp). TIA Portal WinCC Comfort/Advanced/Professional projects cannot be imported into STEP 7 V5.x.

Why must the computer name be updated after importing?

WinCC projects store the authoring computer name in their local database. If the computer name in WinCC does not match the Windows hostname, WinCC Runtime will refuse to activate.