How SIMATIC PCS 7 Software Updates and Hotfixes Are Released - SIOS Newsletter vs Technical Support Tickets

In SIMATIC PCS 7, software updates are released through a tiered deployment model. Major Service Packs (SPs) and consolidated Update Collections (UCs) are published publicly on Siemens Industry Online Support (SIOS) and announced via the automated 'mySupport' email newsletter. In contrast, intermediate component updates and specific hotfixes (such as CFC V8.1 SP1 Update 5 prior to general consolidation) are managed under restricted delivery. These intermediate updates are distributed exclusively through Siemens Technical Support tickets (Support Requests) to address specific validated anomalies without risking unintended regressions on stable production plants.

The Siemens PCS 7 Software Release Lifecycle

Engineers maintaining SIMATIC PCS 7 systems often inspect the official Siemens Compatibility Tool or release notes and observe references to software versions that do not appear to have public download links on SIOS (for example, finding a reference to CFC V8.1 SP1 Upd 5 when only Upd 2 is publicly listed).

This is not an error or broken link; it is a fundamental aspect of Siemens quality assurance and change management policy for process automation.

In mission-critical industrial automation environments where an unexpected software regression could halt a 24/7 refinery or chemical reactor, Siemens enforces a tiered, risk-mitigated release hierarchy for engineering system components (CFC, SFC, WinCC, TH, Route Control, BATCH).

Public Updates vs Restricted Delivery Hotfixes

Software distributions from Siemens fall into distinct lifecycle categories based on testing depth, deployment scope, and operational risk:

1. General Availability Releases (Public Downloads)

Major Releases & Service Packs (e.g., PCS 7 V8.1, V8.1 SP1): Comprehensive platform distributions tested across all supported hardware and software matrices. Distributed via physical media or OSD.
Consolidated Update Collections (UC) / Rollup Packages: Packages combining multiple component bug fixes that have passed full system regression testing. Published openly on SIOS with an entry ID and downloadable by any registered user.

2. Restricted Delivery Updates (Hotfixes / On-Demand Updates)

Component-Specific Updates (e.g., CFC Upd 5): When a specific customer reports an engineering tool crash, compilation anomaly, or memory leak, Siemens R&D develops an emergency patch.
Restricted Release Mechanism: To prevent plants from installing unneeded patches that could introduce untested interactions into functioning systems, the patch is released only to customers actively experiencing the diagnosed behavior via a Technical Support Request (TIC).
Consolidation: Once the patch has operated in the field without negative side effects and completed broad system validation, it is incorporated into the next public Update Collection.

Comparison Table - PCS 7 Update Release Channels

The following table contrasts the distribution channels, access requirements, and recommended adoption strategies for PCS 7 software releases.

Release LevelExample ComponentDistribution ChannelAccess RequirementRecommended Deployment StrategyMajor Release / SPPCS 7 V8.1 SP1Official Media / OSDPurchased License / ContractPlanned plant turnaround; full project migrationUpdate Collection (UC)PCS 7 V8.1 SP1 UC1Public SIOS PortalFree SIOS Registered AccountRecommended for all systems during maintenanceComponent UpdateCFC V8.1 SP1 Upd 2Public SIOS PortalFree SIOS Registered AccountDeploy if experiencing documented tool anomaliesRestricted HotfixCFC V8.1 SP1 Upd 5Support Ticket (TIC)Active Support Case with SiemensDeploy only when specifically instructed by Support

Configuring SIOS mySupport Newsletters and Notifications

To ensure you are immediately informed whenever critical software updates, security advisories, or consolidated hotfixes are released, configure automated alerts through SIOS:

Register on SIOS:
* Navigate to support.industry.siemens.com and log in with your Siemens ID.
Access mySupport Cockpit:
* Click mySupport in the upper navigation bar.
* Select Newsletter / Notifications.
Configure Product Subscriptions:
* Under Filter by Product, search for:
- SIMATIC PCS 7
- Continuous Function Chart (CFC)
- SIMATIC WinCC
- S7 F-Systems
Select Notification Types:
* Check Updates / Download, Product News, and Security Information (Cert).
* Choose daily or weekly digest delivery to your registered email address.
Requesting Restricted Hotfixes:
* If a specific update listed in the Compatibility Tool is required to resolve a known bug, open Support Request (TIC) on SIOS.
* Cite the exact installed software version, provide your project diagnostics (Diagnostics directory), and request the specific update package.

Verification

Confirm installed software patch levels and compatibility using the following steps:

Verify Installed Component Updates:
* In SIMATIC Manager, select Help -> About SIMATIC Manager.
* Click the Installed Software button.
* Expand the Components list, locate CFC, and verify the exact build string (e.g., CFC V8.1 + SP1 + Upd5).
Validate System Compatibility:
* Open the online Siemens Compatibility Tool (siemens.com/compat-tool).
* Add your operating system, PCS 7 base version, and the target CFC update.
* Confirm that all installed modules show green checkmarks indicating verified compatibility.

Limitations and Operational Precautions

Avoid Blind Patching: Never install a hotfix on a live production Engineering Station simply because a newer version exists. Follow the rule: If the system is running stably and the documented issue does not affect your configuration, do not install intermediate hotfixes.
Synchronize Redundant Nodes: If an update affects WinCC or communications components, the identical update level must be installed on all redundant OS Servers, OS Clients, and Engineering Stations. Mismatched patch levels across a server pair can disable redundancy synchronization.
Full Backup Before Patching: Always create a full disk image or virtual machine snapshot of the Engineering Station prior to applying any component update.

Engineer FAQ

Why can't Siemens put all updates on the public website?

Process automation systems require immense stability. Putting untested intermediate hotfixes into broad public release could lead engineers to patch stable plants unnecessarily, increasing operational risk. Restricted delivery ensures patches are applied only where clinically needed.

Do I have to pay to open a Technical Support ticket for a software hotfix?

No. Standard Siemens technical support cases regarding suspected software defects, bug reports, and delivery of bug-fix updates are handled free of charge under standard product support.

Will installing a CFC update require an AS STOP?

In most cases, installing a CFC engineering update does not affect the AS runtime code. However, if the update alters the block generator or compiler, the subsequent CFC compile may require an AS download. Changes can typically be downloaded in RUN.

How do I know what bugs a specific update fixes?

Every update package includes a 'Readme.wri' or 'Readme.txt' file detailing the exact software anomalies resolved, prerequisites, and special installation instructions.