Master Data Library Templates: Copying APL Typicals and Multi-Instance Synchronization in PCS 7
To standardize templates in SIMATIC PCS 7, copy control module typicals (e.g. MotLean) from the Advanced Process Library (APL) into the project's Master Data Library (MDL) under the 'Templates' folder in Plant View. To modify existing instances across the plant when a template changes, execute 'Plant Hierarchy > Process Tag Types > Update Instances...', which propagates logic modifications while preserving tag-specific parameters.
Table of Contents
- Centralization Principles: Master Data Library and Process Tag Types
- Copying APL Typicals to the Master Data Library
- Modifying Templates and Propagating Changes via Update Instances
- Process Tag Type vs. Standard CFC Instance Matrix
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Centralization Principles: Master Data Library and Process Tag Types
In large-scale process automation projects engineered with SIMATIC PCS 7 (such as water treatment plants, chemical refineries, or pulp mills), plants contain hundreds of identical or similar technological assets: standard fixed-speed pumps, motor-operated valves, and analog transmitters.
Attempting to engineer each motor by creating independent CFC charts from scratch leads to design inconsistency, prolonged commissioning times, and severe maintenance burdens when client specifications change.
To resolve this, Siemens establishes the Master Data Library (MDL) and the Process Tag Type (Messstellentyp) concept:
1. Standard template charts (Control Module Typicals) provided in the Advanced Process Library (APL)—such as MotLean, MotRevL, VlvL—are copied into the project's Master Data Library.
2. The engineering team customizes the template in the Master Data Library to meet site requirements (e.g. adding local safety disconnect interlocks, running hours counters, or specific alarm limits).
3. The customized template is instantiated throughout the Plant Hierarchy.
4. If a client subsequently mandates adding an auxiliary permissive signal across all 150 motors, the modification is made once in the Master Data Library template and automatically propagated to all 150 instances using the Update Instances wizard.
Copying APL Typicals to the Master Data Library
To establish the standardized engineering baseline:
- Open APL Template Library in Plant View:
* In SIMATIC Manager, select File > Open > Libraries.
* Open the PCS 7 AP Library (orAPL_Templates).
* Switch the library window to Plant View. - Open the Project Master Data Library:
* In SIMATIC Manager, open your project multiproject.
* Locate the Master Data Library folder and switch to Plant View. - Copy the Template Chart:
* In the APL Templates library, locate the Templates hierarchy folder.
* Select the desired typical chart (e.g.MotLean,VlvL).
* Press Ctrl + C.
* Select the Templates folder in your Master Data Library and press Ctrl + V. - Customize the Template:
* Open the copied chart inside the Master Data Library.
* Add site-specific blocks (e.g.CountOhfor operating hours,Intlk04for interlocks).
* Define which block pins represent Parameters (values specific to each motor, such as I/O addresses and setpoints) versus Structural Logic (connections identical across all motors).
Modifying Templates and Propagating Changes via Update Instances
When plant requirements evolve and existing multi-instances must be updated:
Step-by-Step Instance Synchronization Workflow:
- Modify the Master Template:
* Open the template chart in the Master Data Library (e.g.Master_MotLean).
* Make the required logic change (for example, insert an auxiliary trip contact into an interlock block).
* Save and close the template chart. - Launch the Update Instances Wizard:
* In SIMATIC Manager Plant View, right-click the modified template in the Master Data Library.
* Select menu Plant Hierarchy > Process Tag Types > Update Instances... (or select the top-level plant hierarchy folder). - Review Differences and Confirmation:
* The wizard scans the entire multiproject, identifies all charts instantiated from this template, and displays a difference dialog.
* The dialog highlights:- Added or deleted blocks.
- Modified interconnections.
- Preserved instance parameters (I/O addresses, device tag names, and setpoints remain untouched).
- Execute Propagation:
* Click Finish. The wizard automatically updates all target CFC charts across the multiproject. - Compile and Download Changes:
* Execute Chart > Compile > Changes only.
* Download changes to the Automation Station in RUN mode (CiR).
Process Tag Type vs. Standard CFC Instance Matrix
TemplatesVerification
- In the Master Data Library, add an
Add_Rcalculation block to templateMaster_MotLean. - Select
Master_MotLean, right-click and choose Plant Hierarchy > Process Tag Types > Update Instances.... - Confirm the wizard lists all 20 motor charts in the plant hierarchy.
- Click Finish; open plant chart
PMP_101and verify that theAdd_Rblock is now present. - Confirm that
PMP_101's hardware addresses and motor tag names were completely preserved. - Execute Chart > Compile > Changes only; confirm clean compilation with 0 Errors.
Limitations and Operational Precautions
- Never Modify APL System Libraries Directly: Always copy templates from the APL library into your project's Master Data Library before modifying. Modifying original Siemens system libraries corrupts future software updates.
- Preserve Parameter Bindings: When altering templates, do not delete and re-insert blocks whose pins are linked to instance data; deleting a block wipes out configured instance parameters on existing field charts during synchronization.
- Online CPU Download Safety: Updating instances in a live running plant updates multiple charts simultaneously. Always perform safety audits before executing online change downloads to running controllers.
Engineer FAQ
Can I use Import-Export Assistant (IEA) with Master Data Library templates?
Yes. Process Tag Types in the Master Data Library are fully integrated with the IEA, allowing mass generation of hundreds of charts from an Excel I/O spreadsheet.
What is the difference between a Process Tag Type and a Control Module Typical?
Process Tag Type (PTT) is the classic PCS 7 terminology. In modern PCS 7 and Plant Automation Accelerator (PAA), they are referred to as Control Module (CM) Typicals in alignment with ISA-88 standards.
Will updating instances overwrite setpoints adjusted by operators in runtime?
No. Instance update algorithms compare structural connections and block types; configured setpoint values stored in instance data blocks are preserved.
Technical References
- SIMATIC Process Control System PCS 7 Compendium Part A - Configuration Guidelines (V8.1)
- SIMATIC Process Control System PCS 7 Engineering System Manual: Process Tag Types
- ISA-88 Batch Control Models and Technological Typicals
- Siemens Industry Online Support: Working with the Master Data Library in PCS 7 (SIOS Entry ID 109780813)
Related Articles
- Standard Best Practices for Creating a New Multiproject in SIMATIC PCS 7
- Understanding 'Generate Module Drivers' in SIMATIC PCS 7
- Interconnecting Technological Blocks (CountOh) to SelFp1 on APL Motors
Related Tags
- Master Data Library
- Templates
- Process Tag Types
- Update Instances
- APL
- MotLean