TIA Portal and PCS 7 Co-Installation Order Compatibility Guide

TIA Portal and PCS 7 Co-Installation: Order, Compatibility, and Verification

Engineering stations in process automation frequently host both TIA Portal (for SIMATIC S7-1500, S7-1200, ET 200, HMI Panels, and SINAMICS drives) and SIMATIC PCS 7 (for AS 410 / AS 400 automation systems, WinCC V7.x runtime, and the COMOS / PCS 7 engineering toolchain). Installing both products on a single image is supported by Siemens when the versions are explicitly released as compatible, but several hard constraints apply: overlapping WinCC products are mutually exclusive, the Windows version must be approved for both products, and the install order affects how Microsoft redistributables (.NET Framework, SQL Server, Message Queuing) are staged on the machine.

This reference consolidates the field-tested installation order, the official compatibility verification procedure, the WinCC conflict matrix, and the post-install validation steps required to commission a dual-tool engineering workstation.

1. Why Installation Order Matters

Both TIA Portal and PCS 7 share the same registry hive, the same Siemens Automation License Manager service, the same WinCC Explorer shell, and overlapping .NET runtime components. When two major Siemens software families share a workstation, the order determines which installer writes the canonical references for these shared components.

If PCS 7 is installed first, the SIMATIC Manager shell registers itself as the default editor for .s7p, .s7l, .s7f, and .s7k project files. Installing TIA Portal afterward rewrites several of these associations to point at the TIA Portal Openness / Startdrive path. Reverse-order installs typically yield fewer conflicts because the newer TIA Portal installer fully replaces legacy shell mappings, but the safest canonical practice is the order documented below.

2. Verifying Compatibility with the Siemens Compatibility Tool

Before any installation, verify the combination using the official Siemens Compatibility Tool. The tool is the authoritative arbiter for which PCS 7 service packs and TIA Portal updates may legally coexist on a single PC. It cross-references Windows editions, .NET Framework prerequisites, SQL Server versions, WinCC component overlap, and Service Pack dependencies.

Procedure:

1. Download the Compatibility Tool from the official Siemens Industry Online Support portal. The executable and documentation bundle is published at the Siemens support domain.
2. Launch CompatibilityTool.exe and select the working mode Engineering Software.
3. Add the two products to compare. Typical inputs:
   • SIMATIC PCS 7 V9.1 SP2 (or your exact service pack)
   • TIA Portal V17 Update 4 (or your exact update level)
4. Choose the target operating system from the dropdown (e.g., Windows 10 IoT Enterprise LTSC 2021 64-bit).
5. Click Check Compatibility. The tool produces a matrix with traffic-light status and a downloadable PDF report.
6. Open the generated PDF; it lists every prerequisite (Windows, .NET, SQL, MSMQ) and flags known incompatibilities.

Reference: Siemens Compatibility Tool (Industry Online Support).

Example confirmed combination (illustrative only — always recheck against the tool):

3. Hard Constraints: WinCC Product Conflicts

The most common cause of failed dual installations is the simultaneous presence of overlapping WinCC editors. Siemens documentation explicitly states that the following products are mutually exclusive on a single Windows installation:

For engineering stations that must program both PCS 7 OS panels (WinCC V7.x) and SIMATIC Comfort Panels (TP / KP / KTP series), the only supported combination is:

• PCS 7 V9.1 SPx with WinCC V7.x +
• TIA Portal V17 with WinCC Comfort / Advanced (NOT Professional, NOT Unified).

If the engineer also needs to program a SIMATIC WinCC Professional / Unified PC Runtime, that machine must be physically separate from the PCS 7 engineering station. Mixing them on one PC is not supported and typically surfaces as file-locking errors during install or runtime 0x... fault codes after commissioning.

4. Installation Prerequisites

Before running either setup, complete the following prerequisites on the engineering workstation:

Confirm the Microsoft Message Queuing feature is installed:

If the output shows Available rather than Installed, run from an elevated PowerShell:

5. Recommended Installation Order

Siemens officially documents the install order in the TIA Portal installation manual and the PCS 7 readme. The canonical sequence is:

1. Install TIA Portal first, including any optional WinCC Comfort/Advanced add-ons.
2. Apply the latest TIA Portal Update / Hotfix.
3. Reboot.
4. Install PCS 7 second.
5. Apply the latest PCS 7 Service Pack / Hotfix.
6. Reboot.
7. Run both engineering shells once to confirm registration.

Why this order:

• The TIA Portal installer is the newer of the two and writes the most current Microsoft .NET, MSBuild, and SQL Native Client versions. Subsequent PCS 7 setup reuses those components without downgrade attempts.
• TIA Portal registers the modern Siemens.Automation.Portal.exe shell and the Openness API. PCS 7 only needs to attach legacy SIMATIC Manager handlers on top.
• If PCS 7 is installed first, the older setup may pin .NET 4.5.x, which then must be repaired by the TIA Portal installer anyway, leaving a dirty upgrade state.

6. Step-by-Step: Installing TIA Portal First

The TIA Portal setup is documented at Starting installation - TIA Portal. The condensed procedure:

1. Insert the TIA Portal installation medium (DVD, USB, or mounted ISO). The setup program starts automatically. If autorun is disabled, browse to the root and run Start.exe.
2. If a newer Siemens Setup Launcher version is detected, allow it to update.
3. Choose language and target directory. The default path is C:\Program Files\Siemens\Automation\. Avoid mapped network drives.
4. Select products to install:
   • SIMATIC STEP 7 (TIA Portal) Basic / Professional
   • SIMATIC WinCC Basic / Comfort / Advanced (only if Panel programming is required)
   • SIMATIC Startdrive (for SINAMICS G120, S120)
   • SIMATIC Visualization Architect (optional)
5. Accept the license agreement and supply the Automation License Manager key (local or remote).
6. Click Install. Typical duration: 35–60 minutes.
7. When prompted, select Restart now.
8. After reboot, apply the latest TIA Portal Update by double-clicking the .exe update package.

Verify the install:

• Start TIA Portal V17 from the desktop. Create a new project; the wizard must complete without errors.
• Open SIMATIC Automation Tool and confirm the network adapter discovery works.
• Check Windows Programs and Features: Totally Integrated Automation Portal V17 should be listed.

7. Step-by-Step: Installing PCS 7 After TIA Portal

1. Insert the PCS 7 installation medium. If the autorun conflicts with TIA Portal, run Setup.exe from the root manually.
2. The PCS 7 setup first installs prerequisites (Microsoft Visual C++ redistributables, SQL Server 2019 Express for WinCC, MSMQ validation, ALM).
3. Accept the license. The installer prompts for an installation scope:
   • Engineering Station (ES) — full SIMATIC Manager, CFC, SFC, WinCC Explorer, SCL editor, PCS 7 Library.
   • Operator Station (OS) — runtime WinCC V7.x only; do not select on an engineering machine.
4. Choose the install path. Default: C:\Program Files\Siemens\Automation\PCS7\.
5. Select components. For a typical engineering image:
   • SIMATIC PCS 7 Engineering
   • SIMATIC PCS 7 Library
   • WinCC V7.x
   • SIMATIC PDM (for field device integration)
   • SIMATIC S7-PCT (already present from TIA Portal — confirm the setup recognizes the existing version).
6. Provide the Automation License Manager host name. If the ALM is local, leave as localhost.
7. Click Install. Duration: 45–90 minutes.
8. Reboot when prompted.
9. Apply PCS 7 Service Pack / Hotfix if not already on the latest image.

Verify the install:

• Start SIMATIC Manager from Start > Siemens Automation > SIMATIC Manager. Create a new PCS 7 project using the wizard.
• Open CFC Editor and confirm chart creation works.
• Open WinCC Explorer. Confirm no license error dialog appears.
• Re-open TIA Portal. Verify that a TIA Portal project still opens and compiles cleanly; PCS 7 must not have rolled back TIA Portal components.

8. Post-Installation Verification

After both products are installed, run a coordinated verification pass:

A quick smoke test for the S7 communication stack:

(PLC must respond — confirms ISO-on-TCP path through the same stack used by both tools.)

Then from SIMATIC Manager: Options > Set PG/PC Interface → S7ONLINE (TCP/IP) → confirm the same adapter is selected. Then from TIA Portal: Online > Accessible nodes → confirm the same CPU appears. If one tool sees the CPU and the other does not, the most likely cause is a stuck PC interface selection; reset via Windows Control Panel > Set PG/PC Interface.

9. Engineering Workflow Considerations

Beyond pure installation, the order and compatibility also affect day-to-day engineering:

• Project file location. Keep TIA Portal projects under D:\Projects\TIA\ and PCS 7 multiprojects under D:\Projects\PCS7\. Different file locking models can corrupt each other's .LDB lock files if they share a folder.
• Symbol export / import. TIA Portal V17 can export a SCL-based symbol list that PCS 7 can import as a control module type (CMT) tag source. Ensure both tools reference the same source CSV if you chain them.
• Versioning. TIA Portal updates occasionally invalidate the TIA Portal version that a PCS 7 component expects for the HMI proxy device (e.g., ET 200SP IM 155-6 PN HA proxy in a PCS 7 library). Re-running the Compatibility Tool after each TIA Portal Update is mandatory.
• Backup. SQL Server VSS writers must be enabled for both WinCC V7 and any TIA Portal archive instance before the plant's backup software (e.g., Veeam, Acronis) takes VSS snapshots; otherwise, restoring a snapshot returns the SQL databases to a non-recovered state.

10. Troubleshooting Matrix

11. Safety, Licensing, and Audit Notes

• License binding. Each Siemens product requires its own License Key on the ALM. A single key cannot run both PCS 7 and TIA Portal. Floating licenses from a network ALM must be counted so the engineering image can acquire both concurrently.
• Audit trail. PCS 7's Audit option (in the project properties) logs every change to CFC, SFC, and SCL. If your TIA Portal project is later imported into a PCS 7 plant project, the audit chain must be unbroken — keep the TIA Portal project inside a documented change request.
• Plant safety. The engineering station itself does not perform safety-rated logic; safety functions are implemented in the F-CPU of the AS 410 / S7-1500F. Ensure that Distributed Safety (for S7-300F) or Safety Integrated (for S7-1500F) is selected only in the appropriate toolchain; mixing versions across TIA Portal and PCS 7 in a single F-library is not permitted.
• Cybersecurity. Engineering stations should be on a segregated VLAN per IEC 62443-3-2. The combined install footprint increases the attack surface; ensure Siemens Security Service is enabled and Windows Defender or the corporate AV is configured to scan C:\Program Files\Siemens nightly but excluded from real-time scans.

12. Quick Reference: Order and Conflict Summary

1. Verify compatibility with the Siemens Compatibility Tool before installing.
2. Resolve WinCC overlap — pick exactly one of {V7.x, Professional, Unified} for the runtime; Comfort/Advanced for Panels is additive.
3. Install TIA Portal first, then apply updates.
4. Reboot.
5. Install PCS 7 second, then apply service packs.
6. Reboot.
7. Verify both shells, share PG/PC interface, and confirm ALM sees both license sets.