Importing Formulas into SIMATIC BATCH Recipe System from Excel and External Formats

SIMATIC BATCH V8.2 and V9.0 natively import and export recipes and formulas exclusively using its proprietary XML-based archive format (.sbx) to maintain ISA-88 compliance and FDA 21 CFR Part 11 electronic data integrity. BatchCC does not provide a direct Microsoft Excel (.xlsx/.csv) import wizard in its GUI. To import formula parameters from Excel, you must either transform Excel tabular data into the valid SIMATIC BATCH XML schema (.sbx) via an external script or XSLT macro, utilize the SIMATIC BATCH Open API (.NET/COM programming interface), or transfer formulas through an integrated MES like Siemens Opcenter Execution (SIMATIC IT) via standard B2MML.

SIMATIC BATCH Recipe and Formula Architecture (ISA-88)

SIMATIC BATCH implements batch control conforming strictly to the international standard ISA-88 (IEC 61512). In this architecture, recipe procedures (hierarchical structures of Recipe Unit Procedures, Recipe Operations, and Recipe Phases) are decoupled from specific formula parameter sets:

Master Recipes: Define the procedural sequence of operations and phases across equipment entities.
Formula Categories and Formulas: Define specific bill-of-materials setpoints (e.g. ingredient quantities, temperatures, blend durations, and agitator speeds) that instantiate into a Master Recipe to form a Control Recipe.

The Role of *.sbx Recipe Archive Files and Integrity Checksums

Within Batch Control Center (BatchCC), recipes and formula categories are exported and imported as .sbx files (SIMATIC BATCH XML). An .sbx file is a structured XML package containing:

Exact equipment allocation strings matching the SIMATIC Manager Plant Hierarchy.
Typed parameter definitions matching SFC type characteristics (REAL, DINT, STRING, BOOL) with defined physical units.
Upper and lower operational limits.
Cryptographic checksums and audit metadata satisfying regulatory requirements (FDA 21 CFR Part 11) for recipe traceability.

Why Direct Excel Import is Omitted from BatchCC GUI

Siemens intentionally omits a direct, unconstrained Excel import button in BatchCC. In pharmaceutical, biotechnology, and chemical batch processes, importing unverified spreadsheet cells without schema validation, type checking, or audit trail logging poses severe product contamination and safety risks. Furthermore, Excel files do not encode the structural ISA-88 object dependencies required by the SIMATIC BATCH database.

Integration Workflow 1: XML Transformation (.xlsx to .sbx)

For customers maintaining extensive product catalogs in Excel who require bulk formula generation, the standard engineering solution is an XML transformation pipeline:

Generate Reference Schema:
- In BatchCC, create a reference formula manually with all parameters populated.
- Export the formula category to an .sbx file via BatchCC > Recipes > Export.
- Open the .sbx file in an XML editor to inspect the XML tags (<Formula>, <Parameter>, <Value>, <Unit>).
Construct Excel Export Tool:
- Develop an Excel VBA macro or Python script (openpyxl / xml.etree) that reads columns from Excel and populates the target XML schema elements.
- Ensure numeric data types format correctly (e.g. decimal points rather than commas).
Import into BatchCC:
- In BatchCC, select Recipes > Import..., select the generated .sbx file, and execute validation.
- Resolve any parameter unit or range discrepancies highlighted by the BatchCC import validation report.

Integration Workflow 2: SIMATIC BATCH Open Interface (API)

For automated enterprise integration without manual file handling:

SIMATIC BATCH API: Siemens provides a COM and .NET programmatic application programming interface (API). External C# or VB.NET applications can read recipe data from databases or spreadsheets and create formulas programmatically inside the SIMATIC BATCH database engine.
MES B2MML Interface: In enterprise environments, Siemens Opcenter Execution Process (formerly SIMATIC IT) sends production orders and master recipes directly to SIMATIC BATCH via Business to Manufacturing Markup Language (B2MML).

Comparison of SIMATIC BATCH Formula Import Methodologies

The table below contrasts methods for loading formulas into SIMATIC BATCH:

Import MethodologyImplementation ToolDevelopment EffortRegulatory Audit TrailBest Suited Operational ScopeStandard BatchCC GUINative Export/Import (.sbx)Zero (Built-in)Full 21 CFR Part 11 audit loggingDay-to-day routine recipe managementExcel-to-SBX XML ScriptPython / Excel VBA macroLow to MediumRequires post-import release in BatchCCBulk initial commissioning of formulasSIMATIC BATCH Open APICustom .NET/C# applicationHighProgrammatic validation & loggingAutomated ERP/LIMS formula syncSiemens Opcenter (MES)Standard B2MML ConnectorsEnterprise IntegrationCertified automated electronic batch recordsFully automated multi-plant production

Verification

Verify formula integrity after importing into BatchCC:

Open Batch Control Center (BatchCC) and expand the Formulas folder.
Verify that the imported formula category and formula names appear in the tree.
Double-click the imported formula; inspect parameter values against the original Excel source spreadsheet.
Check that parameter units of measurement (e.g. kg, degC, rpm) align correctly with the plant equipment.
Right-click the formula and select Release for production; confirm that BatchCC validates the formula without syntax errors.

Limitations and Operational Precautions

Adhere to the following regulatory and technical precautions:

Post-Import Validation Mandatory: Every formula imported via external scripts must be reviewed, verified, and officially released by authorized personnel within BatchCC before scheduling in a production batch.
Decimal Separator Formatting: In multinational environments, ensure the XML export script converts localized comma decimals (12,5) to standardized point decimals (12.5) to prevent parameter corruption.
Version Management: Avoid modifying existing released formulas externally; always increment formula version numbers to preserve electronic batch record traceability.

Engineer FAQ

Does Siemens provide an official Excel Add-In to import formulas into BatchCC?

No standard out-of-the-box Excel Add-In is included in SIMATIC BATCH. External tools must format formula data into the official SIMATIC BATCH XML format (.sbx) or utilize the SIMATIC BATCH API.

Can an .sbx file be edited directly in a standard text editor?

While an .sbx file is human-readable XML, modifying it in a text editor must preserve the exact XML hierarchy and schema tags. Any schema violation will cause BatchCC to reject the file during import.

What happens if an imported formula parameter is outside the SFC type limits?

BatchCC executes a validation check upon import. If a parameter value violates the min/max limits configured on the corresponding SFC type in SIMATIC Manager, the formula import fails with an out-of-bounds error.