Optimizing WinCC Fast Tag Logging Archive Sizes and Segment Configuration in SIMATIC PCS 7

In SIMATIC PCS 7 OS stations, observing excessively large Fast Tag Logging archives (such as 600-650 MB per day for 300 tags compared to 20 MB on standalone WinCC) is caused by SQL Server pre-allocating fixed segment database sizes, combined with high-frequency cyclic acquisition lacking deadband smoothing. In PCS 7, cyclic logging intervals of 1 minute or less automatically route to 'Tag Logging Fast'. By default, PCS 7 Archive Configuration sets large total archive limits (e.g., 100 GB over 12 weeks) with pre-allocated minimum segment file sizes (e.g., 512 MB). If 280 tags are acquired cyclically every 500 ms to 1 second without deadband filtering, millions of raw values are committed daily. To reduce archive volume, configure percent deadband smoothing (e.g., 0.5% to 1.0%) on analog tags, transition slow-moving tags to Tag Logging Slow, and tune individual archive segment sizes in WinCC Archive Configuration.

Executive Summary

Historical process trending and regulatory archiving are core responsibilities of SIMATIC PCS 7 Operator Stations. However, system administrators frequently notice that PCS 7 OS Single Stations generate massive database footprints—hundreds of megabytes daily for relatively modest tag counts—far exceeding equivalent standalone WinCC installations. This divergence stems from PCS 7's standardized, high-integrity default template settings. WinCC Tag Logging operates through two distinct database engines: Tag Logging Fast and Tag Logging Slow. When hundreds of process values are acquired cyclically at sub-second rates without data compression or deadband filtering, Microsoft SQL Server creates large pre-allocated segment files. Reconciling acquisition cycles, implementing swinging-door or deadband smoothing, and right-sizing segment parameters optimizes storage efficiency without compromising data fidelity.

Architecture and Fundamental Mechanics

The WinCC Tag Logging subsystem in PCS 7 employs a segmented Microsoft SQL Server database architecture designed for continuous real-time writing:

Tag Logging Fast vs. Tag Logging Slow:
* Tag Logging Fast: Automatically manages all process tags with cyclic acquisition intervals of 1 minute or less. Data is stored in compressed binary chunks within time-stamped SQL segment databases (<ProjectName>_TLG_F_YYYYMMDD_HHMM.mdf).
* Tag Logging Slow: Manages tags with acquisition cycles greater than 1 minute or event-driven archiving (<ProjectName>_TLG_S_*.mdf).
The SQL Segment Pre-Allocation Mechanism:
* In WinCC Tag Logging under Archive Configuration > Fast / Slow Tag Logging > Properties, administrators specify:
- Time period covered by a single segment (e.g., 1 day or 1 week).
- Maximum size of a single segment (e.g., 512 MB or 1024 MB).
- Total size of all segments (e.g., 100 GB) and Time period of all segments (e.g., 12 weeks).
- When SQL Server initiates a new segment, it can pre-allocate file space on disk according to SQL growth parameters. Even if the actual data points only occupy 50 MB, the file on disk may report hundreds of megabytes immediately upon creation.
Data Throughput Calculation:
* Consider 300 tags:
- 60 tags at 500 ms = 120 samples/second
- 200 tags at 1 sec = 200 samples/second
- 20 tags at 2 sec = 10 samples/second
- Total = 330 samples/second = 28.5 million samples per day!
- Without deadband compression, every single cyclic sample (timestamp, quality code, value) is written to the database, generating hundreds of megabytes of raw SQL records daily.
Deadband Smoothing vs. Standalone WinCC:
* Standalone WinCC projects often default to 'On change' logging or incorporate deadbands.
* PCS 7 process control templates default to cyclic continuous logging to ensure unbroken trend histories. Implementing deadband smoothing filters out noise within a tolerance band, dramatically reducing write cycles.

Step-by-Step Implementation Procedure

Follow these procedures to optimize Tag Logging archive sizes and configure proper database segmentation in PCS 7:

Inspect Archive Configuration in WinCC Explorer:
* Open the OS project in WinCC Explorer.
* Expand Tag Logging.
* Right-click Archive Configuration > Fast Tag Logging and select Properties.
* Review the parameters:
- Time period covered by a single segment: Set appropriately for your plant (e.g., 1 Day or 3 Days).
- Max. size of a single segment: Adjust from default (e.g., set to 100 MB or 200 MB for smaller tag counts).
- Total size of all segments: Set to align with available storage drive capacity.
- Perform the same inspection for Slow Tag Logging.
Implement Deadband Smoothing on Analog Process Tags:
* In the Tag Logging editor, select the analog process tags.
* Under the tag properties, locate Smoothing / Deadband.
* Select Percentage or Absolute deadband.
* Enter a reasonable deadband tolerance (e.g., 0.5% or 1.0% of the measurement range).
* When deadband smoothing is active, WinCC only writes a new archive record if the value deviates beyond the deadband threshold since the last recorded value, eliminating sensor noise writes.
Re-evaluate Acquisition and Archiving Cycles:
* Review whether tags truly require sub-second logging:
- Fast-acting loops (flow, pressure): 1 second is typically sufficient.
- Slow-acting thermal processes (tank temperatures, ambient readings): Reassign acquisition cycles to 5, 10, or 30 seconds, or move to Tag Logging Slow (> 1 minute).
- Adjust the Archiving cycle independently of the Acquisition cycle (e.g., acquire every 1s, but archive the average over 5s).
Purge and Reinitialize Fragmented Archives (If Testing):
* If testing in a staging environment, deactivate WinCC Runtime.
* Reset the archive databases using WinCC Explorer > Tag Logging > Archive Configuration > Reset (or manually detach old test segments).
Monitor Disk Space Consumption:
* Activate WinCC Runtime.
* Observe the size of newly generated .mdf and .ldf files in the project's ArchiveManager directory over a 24-hour period.

Verification

After applying deadband smoothing and adjusting segment sizes, monitor the ArchiveManager/TagLoggingFast folder over 24 hours. Confirm that the daily archive growth decreases from 600 MB to under 50-100 MB. Open WinCC runtime trends (WinCC Online Trend Control); verify that process curves remain smooth, responsive, and accurate without missing data points.

Limitations and Operational Precautions

Do not apply excessive deadbands (> 2-5%) to critical safety or regulatory parameters (e.g., emissions monitoring or custody transfer), as regulatory compliance mandates high-resolution uncompressed records. Ensure that the OS storage drive maintains at least 20% free disk space to prevent SQL Server database locking.

Engineer FAQ

What is the difference between Tag Logging Fast and Tag Logging Slow?

Tag Logging Fast stores high-frequency tags with cycle times of 1 minute or less; Tag Logging Slow stores low-frequency tags with cycle times greater than 1 minute.