Resolving WinCC Cannot Open Integrated Project Errors and Resetting TIA-Flag for Remote OS Deployments in PCS 7

In SIMATIC PCS 7, when an Operator Station (OS) project file is copied manually from an Engineering Station (ES) to an intermediate storage media or target computer and fails to open directly in WinCC Explorer with an error stating the project is integrated in SIMATIC Manager, the cause is an active TIA-Flag within the WinCC project configuration database. In standard PCS 7 architectures, the ES Target OS Download mechanism automatically clears this integration flag upon transfer. To resolve the error when transferring projects out-of-band without direct network loading, use the WinCC Project Duplicator tool (Save As / Duplicate) on the ES, or clear the TIA integration flag in the project SQL database using Microsoft SQL Server Management Studio or Siemens Reset scripts.

Executive Summary

In distributed SIMATIC PCS 7 environments, Operator Station runtime projects are centrally managed and engineered within SIMATIC Manager on the Engineering Station. To maintain architectural synchronization and prevent unauthorized standalone edits, PCS 7 marks the internal WinCC configuration database (.mdf) with an integration indicator known as the 'TIA-Flag' (or STEP 7 Integration Flag). When commissioning remote or air-gapped OS stations where direct network downloads over the Terminal Bus are unavailable, engineers often attempt to copy project folders manually. However, opening a raw copied project in standalone WinCC Explorer triggers an access refusal. Understanding how the TIA-Flag functions enables engineers to stage, duplicate, and deploy remote OS runtimes safely without database corruption.

Architecture and Fundamental Mechanics

The integration mechanics between SIMATIC Manager and WinCC Explorer rely on specific metadata flags stored within the project database:

The STEP 7 / TIA Integration Flag:
* When a WinCC project is created or managed within SIMATIC Manager, the configuration database sets internal parameters indicating that the master data repository resides in STEP 7.
* Specifically, the project configuration table (CC_PRJ_... or database settings table MCPRJCONFIG) maintains an integration attribute (the TIA-Flag). As long as this flag is set (1), standalone WinCC Explorer refuses to open the project independently, requiring execution from SIMATIC Manager.
The Target OS Download Process (PLC > Download):
* During a standard network download from the ES to the target OS over the Terminal Bus, SIMATIC Manager establishes a handshake via the Station Configurator and WinCC Project Loader.
* Upon transferring the database and runtime files, the download engine executes an automated database maintenance script on the target OS that resets the TIA-Flag to 0.
* This enables the target station to run autonomously as a dedicated runtime operator station without requiring SIMATIC Manager.
Manual Folder Copy Pitfalls:
* Copying the project directory directly from the ES storage path via Windows Explorer bypasses the WinCC deployment engine.
* The target database retains the active TIA-Flag. When double-clicking <Project_Name>.mcp in WinCC Explorer, the software detects the integrated state but cannot establish a connection to a local SIMATIC Manager multiproject, producing a persistent initialization error.

Step-by-Step Implementation Procedure

Follow these procedures to prepare and deploy an OS project to a remote or air-gapped machine without triggering integration errors:

Method 1: Use WinCC Project Duplicator (Recommended):
* On the Engineering Station, close WinCC Explorer for the target OS.
* Open Windows Start Menu and launch Siemens Automation > SIMATIC > WinCC > Project Duplicator.
* In the Project Duplicator dialog, select the source .mcp file of the OS project from the ES multiproject path.
* Set the target folder path (e.g., an external drive or dedicated staging directory).
* Click Duplicate. The Duplicator generates a complete, clean standalone project copy with the TIA integration flag stripped.
* Transfer the duplicated folder to the target OS station and open <Project_Name>.mcp directly in WinCC Explorer.
Method 2: Use SIMATIC Manager Target OS Download to Network Share:
* If the target computer is on a reachable network subnet, share the destination OS project folder with full read/write rights for the SIMATIC HMI group.
* In SIMATIC Manager Component View, right-click the OS object and select Object Properties.
* In the Target OS and Standby OS Computer path, enter the UNC path of the target share (e.g., //TargetOS_PC/WinCC_Project).
* Right-click the OS object and select PLC > Download. SIMATIC Manager performs the official deployment, clearing the TIA-Flag automatically.
Method 3: Resetting the TIA-Flag via SQL Server Management Studio (Recovery):
* If an unstripped project has already been transferred to the target OS and cannot be re-duplicated from the ES:
* Open Microsoft SQL Server Management Studio (SSMS) on the target OS as a local Windows Administrator.
* Connect to the local WinCC SQL Server instance (named WINCC or localhost/WINCC).
* Locate the attached configuration database (CC_<ProjectName>_<Date>).
* Open table dbo.MCPRJCONFIG or execute the Siemens TIA-flag removal SQL statement to update the integration state: set the integration parameter value to 0.
* Detach and re-attach the database, or restart the WinCC CCProjectMgr service.

Verification

On the target OS computer, launch WinCC Explorer and open the <Project_Name>.mcp file. Verify that WinCC Explorer loads without displaying the 'Project is integrated in STEP 7' modal warning. Confirm that the Graphics Designer, Tag Management, and Alarm Logging editors open normally. Activate WinCC Runtime and verify communication connectivity to the AS controllers via the configured named connections.

Limitations and Operational Precautions

Directly modifying WinCC SQL tables via SSMS should only be performed as an emergency field workaround; always maintain an unedited backup copy of the database before running SQL update statements. When using duplicated standalone projects, changes cannot be incrementally synchronized back into the master ES multiproject; all future engineering modifications must originate on the ES and be re-deployed.

Engineer FAQ

What is the exact purpose of the TIA-Flag in PCS 7 WinCC projects?

The TIA-Flag denotes that the WinCC project is part of a SIMATIC Manager multiproject, preventing unauthorized standalone edits that would desynchronize the OS database from the CFC and AS engineering.

Why does 'PLC > Download' from SIMATIC Manager work while manual copying fails?

The SIMATIC Manager download engine executes automated post-transfer scripts on the target station that strip the TIA-Flag and register the database on the target SQL instance.

Can I remove the TIA-Flag directly inside SIMATIC Manager?

Yes, by archiving the project or using WinCC Project Duplicator, or by selecting Options > Project > Remove Integration if available in standalone WinCC tools.

Does clearing the TIA-Flag affect WinCC Runtime communication tags?

No. Named connections, AS-OS compiled tags, and graphic pictures remain intact; clearing the flag only removes the restriction against standalone WinCC Explorer opening.