Migrating Projects with Control Module Types (CMT) from PCS 7 V9.0 SP1 to V9.0 SP3

To migrate a SIMATIC PCS 7 project utilizing Control Module Types (CMT) and the Advanced Process Library (APL) from V9.0 SP1 to V9.0 SP3, follow the standard library update procedure: 1. Update the Master Data Library (MDL) block types with the latest V9.0 SP3 APL and Basis Library blocks; 2. Synchronize CMT definitions within the Master Data Library to propagate modified block interfaces; 3. Execute 'Type-Instance Synchronization' to update plant hierarchy CMT instances; and 4. Compile CFC changes and download to the AS in RUN mode. If copying a single CMT-based CFC from a V9.0 SP1 project into an existing V9.0 SP3 project, migrating the entire project is not required; simply update the imported block types to match the target Master Data Library.

Executive Summary

Service pack modernization within the SIMATIC PCS 7 V9.0 lifecycle (such as migrating from V9.0 SP1 to V9.0 SP3) delivers important library optimizations, security patches, and Update Collection enhancements. When projects employ technological engineering architectures based on Control Module Types (CMT), engineers frequently seek guidance on the precise migration sequence to avoid breaking type-instance synchronization. Additionally, engineering teams collaborating across multi-site projects often need to import individual CMT-based CFC charts created in older service packs into newer systems without triggering full project re-migrations. This article details the certified CMT migration workflow between V9.0 service packs and explains the rules governing modular chart exchange.

Architecture and Fundamental Mechanics

Technological Type-Instance Architecture, Master Data Library Role, and Intra-Version Library Upgrades:

The Role of the Master Data Library (MDL) in CMT Engineering:
In PCS 7, Control Module Types (CMT) are defined exclusively inside the Master Data Library.
A CMT encapsulates APL function blocks (e.g. MotL, VlvL), channel drivers, interlocks, and technological attributes (messages, parameters, signals).
Instantiated Control Modules (CM) in the Plant Hierarchy maintain a dynamic parent-child link to the CMT template in the MDL.
The Mechanism of Intra-Version Service Pack Migration (V9.0 SP1 -> SP3):
Between SP1 and SP3, Siemens updates the underlying Advanced Process Library (APL) and PCS 7 Basis Library, introducing refined internal algorithms, updated diagnostic structures, and bug fixes.
Step 1: Library Ingestion: Updating the block types inside the Master Data Library replaces older block versions (e.g. MotL V9.0.1) with SP3 equivalents (e.g. MotL V9.0.3).
Step 2: CMT Template Alignment: Opening the CMT templates in the MDL allows the type editor to detect modified block interfaces and realign technological attributes.
Step 3: Type-Instance Synchronization: The Plant Automation synchronization engine propagates template updates to all instantiated CM charts across the multiproject.
Modular Chart Exchange Across Service Packs:
If an engineer copies a single CFC chart containing CMT instances from a V9.0 SP1 project into a V9.0 SP3 project:
- The target project does NOT need a global re-migration.
- The copied chart initially carries the older block type headers (SP1).
- In the target project, opening the chart and selecting Options > Block Types > New Version harmonizes the imported chart's blocks with the target project's Master Data Library (SP3), establishing complete type consistency.

Step-by-Step Implementation Procedure

Create Baseline Backup and Install Updates:
* In SIMATIC Manager on the V9.0 SP1 Engineering Station, create a full ZIP archive via File > Archive.
* Ensure the target engineering station has PCS 7 V9.0 SP3 and the latest Update Collection (e.g. UC02) installed.
* Retrieve the project archive onto the V9.0 SP3 workstation.
Update Block Types in the Master Data Library:
* In SIMATIC Manager, navigate to the Master Data Library > S7 Program > Blocks folder.
* Select menu File > Open, switch to the Libraries tab, and open the official PCS 7 AP Library V90 (SP3).
* Copy the updated APL blocks (MotL, VlvL, MonAnL, etc.) from the system library and paste them into the Master Data Library Blocks folder, choosing 'Overwrite all'.
* Repeat for the PCS 7 Basis Library V90.
Update Block Types in CFC and User Projects:
* Open any CFC chart in the project.
* Select menu Options > Block Types.
* In the left pane (Master Data Library), select all updated blocks and click New Version.
* Allow the wizard to update all block instances across all CFC charts in the user project.
Synchronize Control Module Types (Type-Instance Synchronization):
* In the Master Data Library, open the CMT templates under the Technological Objects folder.
* In the Plant View, select the project root folder.
* Select menu Options > Plant Types > Synchronize....
* In the synchronization wizard, verify that all CMT templates match the target instances; click Synchronize to commit changes.
Compile CFC Charts and Download Changes in RUN:
* Execute a CFC Changes compilation.
* In SIMATIC Manager, download changes to the AS in RUN mode.
* Compile and download changes to the OS.

Verification

Open an instantiated CM chart in CFC; confirm that block headers display the updated V9.0 SP3 version numbers.
Open the Technological List Editor (TLE); verify that all CM instances populate without type mismatch warnings.
Confirm that CFC Changes download completed successfully without requiring an AS CPU STOP.

Limitations and Operational Precautions

If migrating with utilization of new functions involves blocks whose interface signatures changed significantly, verify that the CPU has sufficient spare memory to execute the online delta download without memory fragmentation.

Engineer FAQ

Do I need to migrate the whole project if I copy a CMT-based CFC from SP1 to SP3?

No. Simply update the block types of the copied chart via 'Options > Block Types > New Version' to match the target project's Master Data Library.

Where are Control Module Types (CMT) updated?

Always inside the Master Data Library first, followed by Type-Instance Synchronization to the user project.

Can CMT migration between V9.0 SP1 and SP3 be downloaded in RUN mode?

Yes, intra-version service pack updates are designed to support online Changes download without stopping the CPU.

What is the difference between updating with and without utilization of new functions?

Updating without new functions retains older block versions; updating with new functions updates APL blocks to gain new features and bug fixes.

Which update collection is recommended for PCS 7 V9.0 SP3?

Always install the latest Update Collection (such as Update Collection 2 or higher) available on Siemens Industry Online Support.

Technical References

Control Module Type

CMT

Type-Instance Synchronization

20 respuestas

Migrating Projects with Control Module Types (CMT) from PCS 7 V9.0 SP1 to V9.0 SP3