TIA Portal Versions and Updates: V16 to V20 Reference Guide

1. Overview

Siemens Totally Integrated Automation Portal (TIA Portal) is the integrated engineering framework used to configure, program, commission, and diagnose SIMATIC controllers, HMI panels, SINAMICS drives, and the surrounding PROFINET/PROFIBUS network. The engineering environment folds STEP 7 (controller programming in LAD/FBD/SCL/GRAPH), WinCC (HMI and SCADA configuration), SINAMICS Startdrive (drive parameterization), and SIMOTION Scout integration into a single project tree with a unified tag database. Symbol changes propagate from the PLC program into HMI screens and drive references without manual cross-referencing.

This technical reference documents the current TIA Portal release line from V16 forward, the update delivery mechanism (software updates and Hardware Support Packages), the automated online update check built into TIA Administrator, and the standard installation sequence that an engineering station operator follows when new firmware or device descriptions become available. Operators moving from V13/V14/V15 environments will find the migration impact notes in section 7 and the licensing model change points in section 8.

For the official product overview, see the Siemens TIA Portal product page. The canonical installation procedure is documented in the TIA Portal V20 Installation Manual — Checking availability of updates and support packages.

2. TIA Portal Release Lineage and Version Marking

TIA Portal ships as a major version (V16, V17, V18, V19, V20) with one or more updates within each major. Each update is identified by the major version and an update index, for example "V16 Update 3" or "V17 Update 9". Service packs deliver incremental fixes between updates and are installed through the same TIA Administrator mechanism as updates. The complete update register for V16 is published in Siemens Industry Online Support entry 109775861, and each subsequent major follows the same convention with a fresh support entry at release.

The table below lists the documented major releases relevant to current engineering environments. Dates reflect the public release windows and should be confirmed against the latest Siemens Industry Online Support entries before relying on them for project planning.

3. Update and Support Package Architecture

TIA Portal separates "updates" — bug fixes, functional enhancements, and security patches applied to the installed major version — from "support packages" — device descriptions, firmware support, and library content that the engineering framework consumes without modifying the core TIA Portal binaries. Both are delivered through the same TIA Administrator package manager.

Three package categories exist:

• Software Updates — versioned installers that update the TIA Portal installation itself (STEP 7, WinCC, Startdrive, SIMOTION components). Identified by major version plus update index, e.g., "TIA Portal V18 Update 4".
• Hardware Support Packages (HSPs) — ZIP packages containing GSD/GSDML device descriptions, module catalogs, and family trees that teach TIA Portal about new SIMATIC CPUs, ET 200 stations, SINAMICS drives, and third-party PROFIBUS/PROFINET devices. HSPs do not modify the TIA Portal binaries; they extend the catalog.
• Software Support Packages (SSPs) — library blocks, faceplates, and example projects that extend the engineering libraries without changing the core installation. SSPs are delivered through the TIA Portal help system and the global library import workflow.

When TIA Administrator opens (Start → Siemens Automation → TIA Administrator), the installed packages are listed with their version, release date, and component reference. Pending updates and HSPs are highlighted when a connection to the Siemens update server is available. The package manager is also the single pane of glass for license administration (delegated to the Automation License Manager), service configuration, and multi-user server registration.

4. Checking for Available Updates and Support Packages

TIA Portal automatically checks the Siemens update server for new packages each time the engineering station is connected to the internet. The check interval is configurable through TIA Administrator's settings dialog. The official procedure is documented in the TIA Portal V20 documentation — Checking availability of updates and support packages.

4.1 Prerequisites

• Local administrator privileges on the engineering station.
• Outbound HTTPS (TCP 443) to *.siemens.com and the Siemens update server endpoints.
• TIA Portal of any major version V16 or later installed.
• At least 15 GB of free disk space for update staging (a typical V-major update expands the installation footprint).
• Microsoft .NET Framework 4.8 and the Visual C++ redistributables required by the target major.

4.2 Manual Update Check Procedure

1. Open TIA Administrator from the Start menu (Siemens Automation → TIA Administrator).
2. Select Installed Software in the navigation pane.
3. Click Check for Updates in the toolbar. The dialog returns a list of available updates for the installed major version.
4. Switch to Support Packages to view pending HSPs and SSPs not yet installed.
5. Mark the packages you want to install and click Download and Install. TIA Administrator fetches the package, verifies the digital signature, and stages it for installation.
6. Reboot if prompted. Some TIA Portal updates require a system restart to complete file replacement and COM re-registration.

5. Installing Hardware Support Packages (HSPs)

Hardware Support Packages extend the device catalog without requiring a TIA Portal update. They are the recommended path for adding support for new SIMATIC CPUs, ET 200SP HA modules, SINAMICS S120 firmware revisions, or third-party PROFINET devices that were released after the major version's catalog lock-down.

5.1 Online HSP Installation

1. Launch TIA Portal with administrator privileges (right-click → Run as administrator).
2. Open the target project or create a new project.
3. From the project tree, right-click the device placeholder and select Hardware detection, or open the device catalog and click the HSP icon at the top of the catalog pane.
4. TIA Portal contacts the Siemens update server and lists available HSPs.
5. Select the matching HSP and confirm the download.
6. Restart TIA Portal if prompted. The new device appears in the catalog under the appropriate family (PLC, HMI, Drive, Switch, etc.).

5.2 Offline HSP Installation

For engineering stations without internet access (typical in plant-floor segregated networks, classified environments, or air-gapped commissioning rigs), download the HSP ZIP on an internet-connected machine and transfer it via approved removable media.

1. From Siemens Industry Online Support, search for the target device order number (e.g., "6ES7 516-3AN02-0AB0") and locate the matching HSP entry.
2. Download the HSP_.zip file. Verify the SHA256 checksum against the value published in the support entry.
3. Transfer the ZIP to the engineering station via approved media.
4. In TIA Portal, open the Options → Support Packages menu.
5. Click Install from file system and browse to the HSP ZIP.
6. Confirm installation. The new device appears in the catalog under the appropriate family.

5.3 HSP Deployment in Multi-User Projects

Multi-user engineering requires every team member to install the same set of HSPs. If workstation A has HSP for the S7-1518-4 PN/DP FW 3.0 installed and workstation B does not, the project opens on A but fails on B with a catalog-mismatch diagnostic. Maintain a project README or engineering station configuration document that enumerates the installed HSP set, and add the HSP inventory to the project's engineering change log.

6. Software Update Installation Procedure

Software updates modify the TIA Portal installation itself. The installation is a multi-step process that closes all TIA Portal instances, stops the TIA Portal background services, stages the update files, applies binary replacements, and re-registers COM/ActiveX components used by the engineering tools.

6.1 In-Place Update Workflow

1. Close all TIA Portal instances and stop any TIA Portal background services (TIA Portal Helper, TIA Portal Multiuser Server, ALM Helper).
2. Open TIA Administrator → Installed Software.
3. Select the TIA Portal installation entry and click Check for Updates.
4. Select the target update (e.g., "V18 Update 4") and click Download.
5. Once downloaded, click Install. The installer prompts for a system restart if required.
6. Verify the update by reopening TIA Administrator — the installed version should reflect the new update index.

6.2 Manual Update via Download Manager

For large updates where bandwidth is constrained or the engineering station is offline, use the Siemens download manager to fetch the update package on a separate machine and transfer the staged files to the engineering station.

1. From Siemens Industry Online Support, locate the target TIA Portal update entry (search by major version + update number).
2. Download using the Siemens download manager or direct HTTPS link. The download is staged to a folder of your choice.
3. Copy the staged installer folder to the engineering station.
4. Run the setup.exe from the staged folder. The installer detects the existing TIA Portal installation and applies the update in place.
5. Reboot when prompted. Verify the new update index in TIA Administrator.

7. Version Compatibility and Migration

Each TIA Portal major version supports a defined range of SIMATIC firmware. The compatibility matrix is asymmetric — newer TIA Portal majors typically support older firmware, but older majors do not support newer firmware. Projects compiled in a newer major cannot be opened in an older major.

Project migration from one major to the next is performed by opening the .ap16/.ap17/.ap18/.ap19 project file directly in the new major. The migration wizard flags blocks, instructions, and library references that are deprecated in the target version. Multi-user projects require all team members to run the same major version; mixed-version teams cannot connect to the same multi-user server.

7.1 Pre-Migration Checklist

• Archive the project (Project → Archive) before opening it in the new major.
• Compile the project in the source major to confirm it builds cleanly. Migration of a project with pre-existing compile errors produces unreliable migration diagnostics.
• Document the HSP set installed on the source workstation.
• Verify the Automation License Manager (ALM) has licenses valid for the target major (subscription or perpetual with valid maintenance contract).
• Confirm the multi-user server (if used) is upgraded to the new major before any client attempts to connect.

8. Licensing Model Evolution

TIA Portal transitioned from perpetual-only licensing (V14–V16) to a tiered licensing model beginning with V17. The model exposes five license types that map to deployment pattern:

• Subscription License — time-bounded license (6/12/24 months), renewable. Includes all updates released within the active subscription window.
• Rental License — short-term usage (days to weeks), targeted at commissioning teams that need the full engineering suite for a bounded migration window.
• Perpetual License — traditional buy-once license carried over from V14–V16 environments. Perpetual users receive major version upgrades only while an active Software Update Service (SUS) contract is in place.
• TIA Portal Cloud — browser-based engineering hosted by Siemens, billed per usage hour or per session. Requires a valid Siemens ID and a Customer ID bound to the subscription.
• VM Platform License — license bound to a virtual machine identifier for centralized deployment in virtual desktop infrastructure (VDI) environments.

Subscriptions deliver a single license key that unlocks the full TIA Portal engineering suite (STEP 7 Professional, WinCC Comfort/Advanced/Professional, SINAMICS Startdrive, S7-PLCSIM). The Automation License Manager (ALM) handles key storage on a local USB dongle, on the hard disk, or in a network license server. Existing projects remain binary-compatible when transitioning between licensing models — license-bound features (e.g., S7-SCL, S7-GRAPH, SIMATIC Safe Kinematics) are tagged per-block in the project; the ALM check runs at compile and download time.

9. Multi-User Engineering Considerations

Multi-user projects in TIA Portal require a TIA Portal Multiuser Server (a Windows service) that mediates concurrent edit sessions. Each client workstation connects to the server, checks out object trees, edits them locally, and checks them back in. The server enforces serialization to prevent simultaneous edits of the same object.

Update implications for multi-user projects:

• Server version dictates client compatibility. All clients connecting to the multi-user server must run the same major version as the server.
• HSP parity is mandatory. A client missing an HSP that the server has will fail to open project trees that reference that HSP's devices.
• Session reservations lock the project tree. Before applying a major update, force-check-in or release all session reservations to avoid orphan locks that block subsequent commits.
• Database reset is required on major upgrade. The multi-user server's local project cache is migrated in place, but a backup of the project database is mandatory before the upgrade.

10. Field Commissioning Scenarios

10.1 Commissioning a New Plant Floor Workstation

Greenfield commissioning typically follows this sequence:

1. Install the target TIA Portal major (e.g., V20) and required updates via TIA Administrator.
2. Install HSPs for every device order number referenced by the project (CPUs, ET 200 stations, drives, HMI panels).
3. Configure the Automation License Manager to point at the local license server or insert the USB dongle.
4. Open the commissioning project and run a full compile to verify the toolchain.
5. Establish an online connection to each CPU and perform a download to the target hardware.

10.2 Updating an Existing Brownfield Station

Brownfield updates require more caution — running controllers may depend on a specific major version:

1. Verify the controller firmware versions of every online CPU on the station.
2. Cross-check each firmware version against the compatibility matrix for the candidate TIA Portal major.
3. If the candidate major does not support the controller firmware, retain the existing major on that workstation or plan a controller firmware upgrade in coordination with production.
4. Archive every open project on the workstation before applying the major update.
5. Apply the major update during a maintenance window. Validate the toolchain by recompiling one representative project and downloading to a test CPU before resuming production work.

11. Security and Network Considerations

TIA Portal update delivery uses HTTPS to the Siemens update server. Engineering stations on plant-floor networks typically operate under restrictive firewall policies that block outbound internet by default. The recommended deployment pattern is:

• Designate a single engineering station in the control network as the update source.
• Allow that station outbound HTTPS (TCP 443) to *.siemens.com and the Siemens update server endpoints.
• Stage updates and HSPs on that station, then distribute the staged installers to peer workstations via approved internal transfer mechanisms.
• Maintain a read-only copy of the HSP inventory in version control so the engineering team can verify which workstations have which device support.

12. Troubleshooting Update Failures

13. Engineering Station Best Practices

• Maintain a TIA Portal version registry. Track which engineering stations run which major and update index. Multi-user projects require unanimous alignment.
• Stage updates on a test station first. Apply major updates to a non-production engineering station, recompile a representative project, and validate before rolling out to commissioning teams.
• Back up projects before each update. The migration step rewrites project files. Use the built-in project archiving (Project → Archive) and store the .zap16/.zap17/.zap18/.zap19 file externally.
• Document installed HSPs per station. A project that references an HSP installed on one station but not another will fail to open on the second station.
• Schedule updates around maintenance windows. Major updates can require 30–90 minutes including the staged download; minor updates take 10–20 minutes.
• Verify ALM license validity before commissioning. Expired subscriptions block downloads and online diagnostics.
• Snapshot engineering stations before major upgrades. Use a system image (VHDX, Acronis, or platform-native) so that a failed upgrade can be reverted in minutes rather than reinstalled from media.
• Centralize HSP storage. Maintain a network share containing the canonical HSP set per project so peer workstations can be reconciled quickly.

14. FAQ