Customizing SIMATIC BATCH Report Templates Using Microsoft Report Builder in PCS 7 V9.x

Microsoft Report Builder remains fully supported and integrated in SIMATIC PCS 7 V9.0 and V9.1 for designing and customizing SIMATIC BATCH report templates (.rdl files). Because SIMATIC BATCH utilizes Microsoft SQL Server Reporting Services (SSRS) as its underlying reporting engine, engineers can launch Microsoft Report Builder (or Visual Studio with SQL Server Data Tools) to modify batch layout templates, insert corporate branding, adjust tabular data sets, and bind recipe execution parameters. Modified .rdl templates are imported into BatchCC via the Report Template Manager and assigned to recipes for automated runtime printouts and PDF archiving.

Executive Summary

Regulatory compliance and quality assurance in batch process industries (such as pharmaceuticals, specialty chemicals, and food manufacturing) require exhaustive electronic batch reporting conforming to FDA 21 CFR Part 11. In SIMATIC PCS 7, SIMATIC BATCH delivers standardized batch logs documenting recipe setpoints, operator interventions, trend curves, and step transitions. Engineers upgrading from PCS 7 V8.2 to V9.x frequently ask whether Microsoft Report Builder is still supported and how custom report templates can be developed. Microsoft Report Builder remains the standard tool for SIMATIC BATCH 9.x reporting. This article details the reporting architecture, explains the SSRS database connection model, and provides a verified template customization procedure.

Architecture and Fundamental Mechanics

SIMATIC BATCH Reporting Architecture, SQL Server Reporting Services (SSRS), and RDL Schema Integration:

The Reporting Engine Architecture:
SIMATIC BATCH stores active and historical batch records inside its Microsoft SQL Server database (SBDatabase and BATCH_ARCHIVE).
For report generation, BATCH leverages Microsoft SQL Server Reporting Services (SSRS) installed alongside the WinCC SQL engine.
Standard report definitions are stored as XML-based Report Definition Language (.rdl) files in:
C:\Program Files (x86)\Siemens\BATCH\Report\Templates\.
Microsoft Report Builder Integration in PCS 7 V9.x:
Microsoft Report Builder (or SQL Server Data Tools - SSDT in Microsoft Visual Studio) is an intuitive, standalone report authoring tool designed for SSRS.
It connects directly to the BATCH reporting data sources, allowing engineers to visual edit headers, footers, data tables, and dynamic charts without modifying underlying SQL queries.
The data sources expose standardized database views and stored procedures (e.g. sp_Batch_GetRecipeHeader, sp_Batch_GetSteps, sp_Batch_GetMessages) that retrieve chronologically organized batch events.
Template Deployment and BatchCC Registration:
Creating an .rdl template does not make it immediately visible to operators.
The customized template must be registered inside Batch Control Center (BatchCC) via the Report Template Manager.
Once registered, templates can be bound to specific Master Recipes or configured as the default plant-wide print layout.

Step-by-Step Implementation Procedure

Locate and Back Up Standard SIMATIC BATCH Templates:
* Navigate to the default template directory on the BATCH Server:
C:\Program Files (x86)\Siemens\BATCH\Report\Templates\.
* Create a backup copy of standard templates (e.g. BatchReport_Standard.rdl).
* Copy the template to a dedicated working folder (e.g. D:\Custom_Batch_Reports\).
Open and Edit the Template in Microsoft Report Builder:
* Launch Microsoft Report Builder from the Windows Start menu.
* Open the copied .rdl file.
* Connect to the local SQL Server Reporting Services instance (http://localhost/ReportServer).
* Customize report elements: insert corporate logo images, adjust column widths, modify font families, and configure header text.
* Verify that existing parameter bindings (@BatchID, @LanguageID) remain intact.
Save the Customized Report Template:
* Save the file under a distinctive technological name (e.g. BatchReport_Pharma_V1.rdl).
* Ensure the file is saved in UTF-8 format.
Register Template in Batch Control Center (BatchCC):
* Launch BatchCC with administrative rights.
* Select menu Options > Report Templates.
* Click Import; browse to your customized .rdl file and import it into the BATCH database.
* Assign the template to the relevant Unit Recipes or Master Recipes under Recipe Properties.
Generate and Verify Batch Report:
* Select a completed batch from the BatchCC project tree.
* Click Print Preview or Create Report.
* Verify that the newly customized layout renders with complete process data, correct page numbering, and proper electronic signatures.

Verification

In BatchCC, select an archived batch record and select Preview Report.
Verify that the report compiles within 5 seconds and renders all corporate branding, logos, and custom tables cleanly.
Confirm that recipe setpoints, actual measured values, and operator messages match the physical process history.
Export the report to PDF; confirm that formatting, pagination, and vector graphics remain crisp.

Limitations and Operational Precautions

Do not modify or delete built-in SQL stored procedure parameters inside standard .rdl datasets; removing required input parameters (such as @BatchID) will cause BatchCC report generation to abort with runtime database binding exceptions.