Excel Report Generation and Scripting Limitations in SIMATIC PCS 7 SMART

In SIMATIC PCS 7 SMART, automated Excel report generation using background Global Scripts is intentionally blocked because the PCS 7 SMART platform enforces read-only restrictions on the WinCC Global Script editor. PCS 7 SMART is a cost-optimized, region-specific package with reduced software capabilities that omits open scripting, Information Server, and OpenPCS 7. To generate periodic reports within PCS 7 SMART, engineers must utilize the native WinCC Report Designer with print-to-file CSV/PDF jobs, trigger local graphic picture scripts on user events, or upgrade to standard SIMATIC PCS 7 to unlock full VBA, C-scripting, and Information Server reporting.

Architectural Constraints of SIMATIC PCS 7 SMART

SIMATIC PCS 7 SMART is a specialized, entry-level distributed control system package released by Siemens for designated emerging markets (primarily India and parts of Asia-Pacific). It is tailored for small-to-medium process applications, typically scaled between a few hundred to a couple thousand I/O points.

To maintain commercial segregation from the flagship international PCS 7 platform, Siemens delivers PCS 7 SMART with deliberate functional boundaries:
* Dedicated Controller Hardware: Operates strictly with SMART-branded controllers (such as CPU 410 SMART).
* Restricted OS Software: Uses a customized edition of WinCC where advanced modular packages are removed or locked.
* Locked Scripting Framework: The Global Script editor (both C-Editor and VBS-Editor) in WinCC Explorer is locked in Read-Only mode.

When engineers attempt to deploy custom Visual Basic for Applications (VBA) or C-scripts to automate Microsoft Excel logging (e.g., logging 100 process tags hourly into a timestamped spreadsheet), they find the global script triggers cannot be created or modified.

Why Global Scripting is Restricted in PCS 7 SMART

The restriction on Global Scripts is not an installation defect or software corruption; it is a designed licensing boundary:
1. Preventing Workarounds for Unlicensed Add-ons: In standard PCS 7, enterprise reporting is handled by SIMATIC Information Server or Process Historian. Locking Global Scripts in PCS 7 SMART prevents developers from recreating complex historian engines and reporting servers using free unmonitored background scripts.
2. System Stability Assurance: PCS 7 SMART systems are typically deployed on standard commercial workstations with limited memory and processing resources. Blocking unmanaged cyclic background scripts prevents CPU thrashing and memory leaks that could destabilize real-time operator screens.
3. No OpenPCS 7 / OPC UA Access: External client connectivity through OpenPCS 7 is not supported, preventing third-party reporting tools from querying WinCC runtime tags across the network.

Comparison Table - PCS 7 SMART vs Standard PCS 7 Reporting

The following table contrasts reporting capabilities, scripting permissions, and expansion options between PCS 7 SMART and Standard PCS 7.

Capability / FeatureSIMATIC PCS 7 SMARTStandard SIMATIC PCS 7WinCC Global Scripts (C / VBS)Locked (Read-Only)Fully customizable with cyclic triggersWinCC Report DesignerAvailable (Static and runtime layouts)Available (Fully integrated)SIMATIC Information ServerUnsupportedSupported (Web, Excel, Word, PDF)SIMATIC Process HistorianUnsupportedSupported (Central enterprise archive)Local Graphic Object ActionsSupported (Picture-level C/VBS)SupportedOpenPCS 7 / OPC DA/UAUnsupportedSupported (Licensed runtime interface)Target Controller PlatformCPU 410 SMARTCPU 410-5H, S7-400H, S7-400 standard

Workarounds for Generating Reports within PCS 7 SMART

If your facility operates PCS 7 SMART and requires automated process data reporting, implement one of the three following strategies:

Strategy 1: Native WinCC Report Designer with PDF/CSV Print Jobs

Use the built-in Report Designer in WinCC Explorer.
Create a Page Layout containing a runtime archive table object bound to Tag Logging archives.
Create a Print Job scheduled to execute daily at 23:59:00.
Configure the default printer in Windows as a virtual PDF printer (e.g., Microsoft Print to PDF) configured to save output automatically to a network directory.

Strategy 2: Local Picture-Level Event Actions

While the central Global Script editor is read-only, local event actions inside graphic pictures (.pdl) remain functional:
* In a hidden background process picture or permanent overview screen, configure an object event (e.g., triggered on screen cycle or timer).
* Write a local Visual Basic script utilizing the Windows Scripting.FileSystemObject to append comma-separated values (CSV) into a text file:
vbscript Dim fso, f, tagVal Set fso = CreateObject("Scripting.FileSystemObject") Set f = fso.OpenTextFile("D:\Reports\DailyLog.csv", 8, True) tagVal = HMIRuntime.Tags("TI101.PV_Out#Value").Read f.WriteLine Now & "," & tagVal f.Close
* Open the resulting CSV file directly in Microsoft Excel.

Strategy 3: Upgrading to Standard PCS 7

If compliance mandates validated automated reporting (such as 21 CFR Part 11 electronic batch records), upgrade the engineering and runtime licenses to standard SIMATIC PCS 7, enabling SIMATIC Information Server.

Verification

Confirm that reporting within PCS 7 SMART operates reliably:

Verify Report Generation:
* Trigger the Report Designer print job manually or wait for the scheduled cycle.
* Confirm that the PDF document or CSV file is created in the designated folder.
Inspect Process Data Accuracy:
* Open the generated file in Microsoft Excel.
* Confirm that all 100 process variables display valid numerical values and consistent hourly timestamps without missing records.
Check WinCC Script Diagnostics:
* Open the WinCC apdiag.exe tool or check C:\Program Files (x86)\SIEMENS\WinCC\Diagnose\WinCC_Sys_01.log.
* Confirm zero script syntax errors or access violation faults.

Limitations and Operational Precautions

Regional Hardware Binding: PCS 7 SMART licenses and software are restricted to specific geographical regions. They cannot be installed on standard international CPU 410-5H hardware.
File I/O Bottlenecks: Avoid executing high-frequency disk write operations (e.g., every second) using local VBScript inside process pictures; frequent file writes can cause screen freezes.
Commercial Accuracy Disclaimer: Verify upgrade paths from PCS 7 SMART to standard PCS 7 and validate software MLFBs with an authorized regional Siemens distributor.

Engineer FAQ

Can I install Microsoft Excel directly on the PCS 7 SMART OS station?

While possible, Siemens advises against running Microsoft Excel directly on active operator stations to avoid software conflicts and Windows updates disrupting process control runtime.

Can PCS 7 SMART communicate with third-party software via Modbus TCP?

Yes. PCS 7 SMART supports industrial communications such as Modbus TCP and standard industrial Ethernet for controller-to-device interfacing.

Why did Siemens make Global Scripts read-only in PCS 7 SMART?

It is a product differentiation strategy to protect the market tier of the standard international PCS 7 platform while providing a low-cost, stable package for basic applications.