Evaluating Compatibility of SIMATIC PCS 7 V9.0 SP1 with Advanced Process Functions (APF) V2.1 Upd1

In the Siemens Compatibility Tool, a grey field indicating 'no compatibility statement' between SIMATIC PCS 7 V9.0 SP1 and Advanced Process Functions (APF) V2.1 Upd1 means the specific software combination has not been formally tested or officially released for commercial production. It does not indicate proven incompatibility, but Siemens provides no technical support or warranty for unreleased configurations. APF is deeply integrated with WinCC User Archives and SQL Server database schemas; deploying it on an unreleased Service Pack risks database script failures and recipe corruption. Facilities requiring APF on PCS 7 V9.0 must remain on PCS 7 V9.0 without SP1 until an official APF update or compatibility release note is published.

Understanding Siemens Compatibility Tool Status Indicators

When planning system upgrades or service pack installations for SIMATIC PCS 7, automation architects rely on the online Siemens Compatibility Tool (Kompatibilitäts-Tool). The compatibility matrix uses standardized status indicators to define supported software combinations:

Matrix Status IndicatorMeaning in Siemens Quality PolicyVendor Support LevelPermitted Plant UsageGreen Checkmark (Compatible)Formally tested and released by product developmentFull 24/7 technical hotline and warranty supportApproved for commercial production and validated facilitiesRed Cross (Incompatible)Formally tested and proven functionally incompatibleBlocked; installation prevented or unsupportedProhibited; known system crashes or data lossGrey Square (No Statement)Not tested / testing in progress / pending releaseZero manufacturer warranty or official hotline supportProhibited in production; restricted to non-critical test labs

A grey status field is frequently misunderstood as a tacit approval or low-risk omission. In Siemens industrial software governance, 'no compatibility statement' explicitly signifies that product management has not completed regression testing, and no engineering sign-off exists for that combination.

Architectural Dependencies Between APF and PCS 7 Service Packs

Advanced Process Functions (APF) is a specialized PCS 7 software package engineered for recipe management, material tracking, and dosing/parameter archiving in process industries (food and beverage, pharmaceuticals, fine chemicals). APF is not an isolated block library; it features profound architectural integration with core PCS 7 subsystems:

WinCC User Archive Coupling: APF relies on tightly defined database schemas inside WinCC User Archives. Upgrading PCS 7 from V9.0 base to V9.0 SP1 updates the underlying WinCC component from V7.4 to V7.4 SP1 and introduces updated Microsoft SQL Server hotfixes. Any internal schema or API changes can break APF database queries.
APF Engineering and Runtime Scripts: APF deploys extensive C-scripts (.pas), VBScript modules (.bmo), and WinCC OCX controls. Service Packs frequently update script execution libraries, potentially causing runtime script aborts during recipe transfers.
AS-OS Communication Blocks: APF utilizes dedicated AS communication function blocks (FB_APF_*) that synchronize material tables between the S7-400 controller and WinCC. Unaligned block interfaces cause OS compilation errors or parameter mismatch during runtime.

Upgrade Strategy and Risk Mitigation for APF Installations

For industrial facilities operating APF V2.1 Upd 1, engineers must follow a structured management-of-change procedure before applying PCS 7 service packs:

Maintain Validated Baseline: If the production plant is operating on SIMATIC PCS 7 V9.0 base release with APF V2.1 Upd 1, freeze the software baseline. Do not apply PCS 7 V9.0 SP1 to production Engineering Stations or OS Servers.
Monitor Siemens Industry Online Support (SIOS): Check the SIOS portal for APF product releases. Siemens releases updates (such as APF V2.1 SP1 or APF V2.1 Update 2) that officially certify compatibility with PCS 7 V9.0 SP1.
Submit Official Support Request (SR): If project requirements mandate installing PCS 7 V9.0 SP1 (e.g., to support new ET 200SP HA hardware), submit an official Support Request to Siemens Technical Support. In specific cases, Siemens can provide pre-release hotfixes, interim release statements, or targeted patch files.
Execute Sandbox Validation: Deploy the proposed combination (PCS 7 V9.0 SP1 + APF V2.1 Upd1 + patches) on an isolated test bench or virtual machine. Verify recipe creation, material batch allocation, and archive archiving cycles before executing plant-wide rollouts.

Verification

Document software compatibility and validate APF functionality through these verification steps:

Compatibility Tool Certification: Generate a certified compatibility report PDF from the Siemens Compatibility Tool confirming that the exact versions (e.g., PCS 7 V9.0 SP1 and APF V2.1 SP1) display green 'Compatible' status.
Installed Software Audit: In SIMATIC Manager, select Help -> About -> Installed Software -> Display. Verify that APF Engineering, WinCC, STEP 7, and CFC versions match the certified release document.
Functional APF Runtime Test: In a test runtime environment, create a test recipe, execute a batch dosing sequence, and verify that material archive tables log process data cleanly into the SQL Server database without WinCC script errors.

Limitations and Operational Precautions

When evaluating compatibility for process automation packages, observe these regulatory and contractual precautions:

Regulatory Compliance (GMP / FDA 21 CFR Part 11): In validated pharmaceutical or food manufacturing environments, deploying software marked 'no compatibility statement' violates validation protocols (GAMP 5) and voids system validation certificates.
Hotline Escalation Boundaries: Siemens Technical Support reserves the right to decline troubleshooting or bug resolution requests if the customer plant is running software marked unreleased or untested in the Compatibility Tool.
Commercial Accuracy Notice: Software licenses, version upgrades, and support agreements (SUS) are subject to Siemens commercial licensing terms. Always confirm required upgrade part numbers (MLFBs) and software maintenance entitlements with an authorized Siemens distributor before procuring or installing software updates.

Engineer FAQ

Does 'no compatibility statement' mean the software will crash immediately upon installation?

Not necessarily. The software setup might install and launch, but unreleased combinations often suffer subtle failures, such as broken SQL database triggers, script compilation errors, or corrupted archive logging during long-term runtime operation.

How often does Siemens update the Compatibility Tool?

The Compatibility Tool database is updated continuously as testing concludes for newly released service packs, hotfixes, and option packages.

Can Siemens Technical Support give permission to use an untested version?

Through an official Support Request (SR), Siemens product management can issue a 'project-specific clearance' if internal testing shows no critical incompatibilities, or provide private hotfixes to resolve known gaps.