Siemens HMI Alarm History: Export & Archive Configuration Guide

Overview: Alarm Archiving Across Siemens HMI Families

Alarm history collection is a fundamental requirement for production traceability, root-cause analysis, and regulatory compliance. Siemens distributes this capability unevenly across its HMI portfolio, and the wrong panel choice can silently block an entire archiving project. This reference documents the supported mechanisms for logging alarms on the legacy TP Basic panel line, the TP Comfort family (TP700/900/1200/1500/1900/2200 Comfort), the Multi Panel (MP) 277/377 series, and the current Unified Comfort / Unified Basic (MTP) devices. Each family uses a different combination of license entitlements, storage media, network paths, and TIA Portal / WinCC configuration objects, so the engineering decision must be made at the panel selection stage, not at commissioning.

Key conclusions at a glance:

• TP Basic (TP1500 Basic, TP700 Basic, etc.): No alarm archiving. Cannot be licensed for it. Replace the panel or accept that alarms are lost on power-down.
• TP Comfort: Alarm logging is included in firmware; no option license is required. Logs to local flash, SD card, USB storage, or network paths.
• MP 277 / MP 377: Archiving is supported but requires an Archive option license per panel. Use the WinCC flexible 2008 SP5 / TIA Portal archive path.
• Unified Comfort (MTP700/1000/1200/1500/1900/2200): Alarm history view supported in TIA Portal V17 onward; persistent logging requires an SQL-backed data store configured via the Logs editor in V19.
• Unified Basic (MTP1000 Basic, MTP700 Basic, MTP1200 Basic): Alarm buffer is volatile; persistent alarm history is not supported on internal memory. External storage or an external historian is required.

For the official Siemens position on alarm persistence differences between Basic and Comfort-class Unified panels, see the SiePortal thread "How to Configure Alarm History in Unified Basic Panels MTP1000 Basic" and the operational manual Alarm History View Operation Manual.

Capability Matrix: Alarm Archiving by Panel Class

The following matrix summarizes alarm archiving capabilities. Verify the catalog number against the live Siemens product catalog before sizing storage, because firmware revisions occasionally change behavior.

TP Comfort Panels: Built-In Alarm Logging

The Comfort line (6AV2 124-1MC01-0AX0 family and the newer 6AV2 124-… V2 variants) implements the alarm logger as a runtime subsystem. No runtime option is required to activate it. Three storage locations are exposed through the Historical view configuration in TIA Portal:

1. Local flash: Used as a fast ring buffer. Size depends on panel variant; typical values are 2 MB on TP700 Comfort and 12 MB on TP2200 Comfort. Data is lost on firmware download or panel reset.
2. SD card / USB mass storage: Inserted media is detected automatically. Recommended for persistent storage. Use Siemens-approved SD cards (6AV2 181-2AM10-0AX0 or 6ES7 644-8AA10-0AA0) to avoid wear-leveling problems with consumer cards.
3. Network path (SMB / NFS / FTP): Configured under Runtime settings → Alarms → History. The panel writes CSV files on each session boundary.

The following screenshot path shows the configuration entry points in TIA Portal V18/V19:

1. In the project tree, expand Devices & Networks → [HMI device] → Screens → Screens <n>.
2. Open HMI tags → Alarm logs, or directly open Alarms → Alarm classes / Alarm groups.
3. Navigate to Runtime settings → Alarms → History.
4. Set the storage location and the maximum log size, then assign the alarm classes that participate in the history.

Configuring the Alarm History View on TP Comfort

Insert an Alarm view object on the desired screen. In the properties pane, set:

MP 277 / MP 377 Panels: License-Enabled Archiving

The Multi Panel family (MP 277 10" Touch 6AV6 643-0CD01-0AX0, MP 377 15" Touch 6AV6 644-1AB02-0AX0, and similar catalog numbers) was the workhorse of WinCC flexible 2008 projects. Archiving requires the Archive runtime option (formerly "Logging" option, licensed under the "WinCC flexible ES" umbrella). One license per panel; per-device part numbers are visible in the Siemens License Web License Manager.

Configuration is performed in WinCC flexible 2008 SP5 or via TIA Portal (for migrated projects). The relevant editors are:

• Logs editor — defines the archive, its storage path, and its segmentation scheme.
• Alarm logging editor — connects alarm events to the log.
• Scheduled tasks — flushes the archive to network storage on a schedule.

Storage path configuration supports local CF card, SD card, and UNC network paths (\\server\share\folder). FTP-based retrieval is also exposed: enable the FTP server in the panel's runtime settings and connect on port 21 (default). The MP series does not expose a webserver for log retrieval.

MP Series "SmartService" Option

The SmartService option (separate license from Archive) enables the integrated webserver. With SmartService enabled, the panel exposes its logged archives over HTTP/HTTPS, allowing remote retrieval of log files using any browser. This is the recommended path when the central historian cannot mount the panel via SMB/CIFS due to network segmentation or firewall rules.

Unified Comfort Panels (V17 / V18 / V19)

Siemens introduced the Unified Comfort line with TIA Portal V17. The runtime architecture is fundamentally different from the WinCC Comfort / WinCC flexible engine — alarms are stored as rows in an SQLite database on the panel, optionally replicated to an external Microsoft SQL Server (or to PostgreSQL with WinCC Unified V18+). For the live status of the alarm history feature in V19, see the SiePortal thread "Alarm history in Unified V19".

Configuring Alarm History in Unified Comfort

1. Open the Unified project in TIA Portal V18 or V19.
2. Select the Unified HMI device and open the Logs editor.
3. Create a new log of type Alarm log. Assign it a name (e.g., AlarmHistory_MTP1500) and select a storage location. Options are:
   • Local file system (SD card / internal flash) — fine for short retention.
   • SQLite database on SD card — recommended for plants without a central SQL server.
   • Remote SQL Server — used for plant-wide historian; the panel pushes records to the SQL instance via OPC UA or the WinCC Unified connector.
4. Define a logging cycle. Alarm events are written immediately (event-driven), so no polling interval is required.
5. In the Alarms editor, ensure each alarm is bound to the log created in step 3. Default bindings are inherited from the alarm class but can be overridden per alarm.
6. Insert an Alarm History Line control or an Alarm History View on the screen. Configure its filter to match the log name from step 3.

SQL Server Connection Details

When connecting a Unified Comfort panel to Microsoft SQL Server (typical historian: WinCC Unified Historian, or an external MES / OSIsoft PI bridge), use the following parameters as a baseline:

Unified Basic Panels (MTP700 / MTP1000 / MTP1200 Basic)

Unified Basic panels are the cost-optimized successor of the TP Basic line. They run the Unified runtime but at reduced capability. Alarm history as a persistent on-device buffer is not supported — the alarm buffer is volatile. To capture alarms, the panel must push events to an external database in real time via OPC UA Pub/Sub or via a WinCC Unified connector on the engineering station. The official Siemens position is documented in the SiePortal thread "How to Configure Alarm History in Unified Basic Panels MTP1000 Basic". The answer confirms that the internal memory alone cannot satisfy an alarm history requirement; engineering must budget an external historian.

Recommended Pattern for Unified Basic

1. Configure OPC UA Pub/Sub on the Unified Basic panel as publisher.
2. Configure an external OPC UA broker (e.g., Siemens Industrial Edge, Kepware, or the WinCC Unified server runtime) as subscriber.
3. Map the alarm events into an SQL table using the broker's historian connector.

Export Mechanisms Compared

The three practical ways to get alarm data out of a Siemens panel into a central database are FTP pull, SMB mount, and direct SQL write. The right choice depends on plant network topology and the panel class.

FTP Pull Reference Script (PowerShell)

This script demonstrates a CSV file pull from a TP Comfort panel. It runs on the historian server, schedules every 5 minutes, and writes the alarm dump into a staging directory. Adjust $panelList for the actual plant device count.

$panelList = @(
  @{IP="10.10.20.51"; Name="Line1_TP1500"},
  @{IP="10.10.20.52"; Name="Line2_TP1500"}
)
$ftpUser   = "Anonymous"
$ftpPass   = "anonymous@"
$stagingDir = "D:\AlarmStaging"

foreach ($p in $panelList) {
  $uri = "ftp://$($p.IP)/Logs/AlarmHistory.csv"
  try {
    $ftpReq = [System.Net.FtpWebRequest]::Create($uri)
    $ftpReq.Credentials = New-Object System.Net.NetworkCredential($ftpUser, $ftpPass)
    $ftpReq.Method = [System.Net.WebRequestMethods+Ftp]::DownloadFile
    $ftpReq.UseBinary = $true
    $resp = $ftpReq.GetResponse()
    $out  = Join-Path $stagingDir ($p.Name + "_" + (Get-Date -Format "yyyyMMdd_HHmmss") + ".csv")
    $stream = $resp.GetResponseStream()
    $file   = [System.IO.File]::Create($out)
    $stream.CopyTo($file)
    $file.Close(); $stream.Close(); $resp.Close()
    Write-Host "Pulled $($p.Name)"
  } catch {
    Write-Warning "Failed $($p.Name): $_"
  }
}

Reading SQLite Logs Directly

On Unified Comfort, the alarm log written to the SD card is a SQLite database file at /media/sd-card/Logs/AlarmHistory.sqlite (path may vary by firmware). To query it from the historian:

-- Example: most recent 100 unacknowledged alarms
SELECT ID, TimeStamp, AlarmClass, AlarmText, State, Acknowledge
FROM AlarmHistory
WHERE State = 1   -- 1 = active, 2 = cleared, 3 = acknowledged
ORDER BY TimeStamp DESC
LIMIT 100;

Licensing Summary

Mis-sizing the licensing on a project is the single most common source of "alarm logging silently disabled" complaints. Use this summary as a checklist during procurement:

Verification Procedures

After commissioning any alarm archiving solution, run the following verification sequence on every panel before sign-off:

1. Generate a test alarm: Force an alarm trigger from the PLC (write a fault tag in STEP 7 / TIA Portal watch table).
2. Confirm ring buffer: Open the panel's Alarm history view and verify the entry appears with the expected timestamp, class, and text.
3. Confirm persistent storage: Reboot the panel and re-open the history view. The entry must still be present.
4. Confirm export path: Trigger an export (FTP pull, SMB copy, or SQL query) and verify the entry reaches the central database within the defined latency SLO.
5. Confirm retention policy: Fill the storage medium to its capacity threshold and verify that the panel rolls over according to the configured policy (oldest first).
6. Confirm failover: Disconnect the network drive and verify that the panel falls back to local buffering without losing events.

Troubleshooting Matrix

Migration Notes: WinCC flexible → TIA Portal → Unified

If the project has long-lived MP 277 / MP 377 panels but the new plant specification calls for Unified Comfort, plan the migration in three steps to avoid losing historical data:

1. Capture: Pull all CSV archives from the legacy MP panels before decommissioning.
2. Transform: Normalize the legacy CSV schema (typically Date;Time;Number;State;Text;Class) to the Unified alarm history schema (TimeStamp;AlarmClass;AlarmText;State). PowerShell or Python with pandas handles the conversion cleanly.
3. Load: Bulk-insert into the Unified historian via SQL bulk copy, preserving the original timestamps so the history view remains continuous across the cutover.

Design Recommendations

• Always choose Comfort over Basic for any site that requires alarm traceability. The price delta is minor compared to the cost of a regulatory audit finding.
• Specify industrial-grade SD cards (e.g., Siemens 6AV2 181-2AM10-0AX0) for any panel that writes alarms to removable media. Consumer cards fail within 6–12 months under constant write load.
• Configure NTP on every panel so timestamps align across the fleet. Siemens panels support NTP client operation natively; point them at a plant NTP server.
• Use SQL as the central export target whenever possible — it is the only mechanism that supports real-time push, structured queries, and per-event timestamps with sub-second precision.
• Document the export SLO in the Functional Specification. Typical values are 5 s for SQL, 60 s for SMB, and 300 s for FTP pull.
• For multi-panel sites (8+ panels as in the original query): standardize on Unified Comfort V19 + central SQL historian. The CSV-per-panel approach scales poorly beyond five panels.

FAQ