Set Up the Commercial TRNSYS Tool

The Commercial TRNSYS Tool is an Excel-based workbook that wraps the TRNSYS simulation engine for commercial AS/NZS 4234 modelling. It manages parameter entry, runs simulations via macros, and produces audit-ready output files.

---

Key sheets

Sheet	Purpose
FAM_COM	Main parameter entry sheet. Contains all HP and system parameters, control settings, zone and load size selections, and CPL results. This is where most modelling work happens.
ComHPdata	EN 14511 performance map entry and export. See Create EN 14511 Performance Map.
Tanks	Tank geometry, insulation, fitting heights, and Appendix E heat loss calculation. See Tank Model Parameters.
Com_Results	Summary of simulation results for all zones: MDT, energy savings %, VEEC/ESC quantities, and CPL. See Review Results.
CPL_[ModelName]	Auto-generated sheet showing the CPL optimisation iterations for each model. Used to verify the Find Loads algorithm found the correct maximum CPL.
Audit	Used to assemble and export the audit file package. Specify model names, file locations, and equivalent models, then run the macro to copy and rename all files.

---

Setting up a new project

The tool is typically copied from a master template or — more often in practice — from a recent project file. In both cases it can carry forward data from the source: performance data, test report numbers, tank model codes, audit-tab entries, file path references, and CPL_* sheet remnants. This is the dominant cause of pre-submission rework. On AE523, the tool submitted for Gate A still referenced the previous project’s Stiebel Eltron HP data and Intertek test report number. AE574 left a TSSI2C1000 tank model code in the tank heat loss spreadsheet.

Always start from the master template and run the initialisation procedure before entering any project data.

1. Copy the master template from SharePoint at /Templates/TRNSYS/Commercial_TRNSYS_Tool_v{Major}.{Minor}.{Patch}.xlsx. Do not copy from a previous project’s tool.
2. Rename the file: AExxx_{ClientShortCode}_Commercial_v1.xlsx.
3. Save to /Projects/AExxx_{ClientShortCode}/02-Modelling/.
4. Set the project number in the FAM_COM sheet. This populates headers throughout the tool and ensures TRNSYS output files are named consistently.
5. Run the Initialise Project macro (see below) before entering any data.

---

Initialisation procedure

The initialisation procedure scrubs all prior-project data from the tool. It must be completed and signed off on the Project Initiation Checklist before any modelling work begins.

Run the Initialise Project macro

The tool includes a macro Initialise Project that performs the scrub automatically. Run it once immediately after copying and renaming the template. The macro:

1. Prompts for project number (AExxx) and client short code.
2. Sets Project_Number and Client_ShortCode cells in FAM_COM.
3. Stamps Tool_Version in FAM_COM from the file metadata.
4. Clears the ComHPdata sheet of all test data rows (preserves headers and instructions).
5. Clears the Tanks sheet of all tank model rows.
6. Clears the Audit tab of all model entries, application folder names, and equivalent-model references.
7. Deletes all CPL_* sheets (auto-regenerated when needed by Find Loads).
8. Clears the macro settings cell storing previous C:\TRNSYS15\Include&weather\AExxx_old_client\ paths and replaces with C:\TRNSYS15\Include&weather\{Project_Number}_{Client_ShortCode}\.
9. Confirms the loaded template uses Type 160 tank (not Type 60). If Type 60 is detected, raises a warning and asks the user to confirm before continuing.
10. Runs a workbook-wide search for any remaining references to known prior-project codes (uses a configurable deny-list); writes results to a _Init_Report sheet.

If the macro has not been built yet, perform the scrub manually using the checklist below.

Manual scrub checklist

For each sheet, confirm the following and tick on the PIC:

• FAM_COM: Project number, client short code, tool version stamped. HP performance map file path uses {Project_Number} placeholder, not a previous project’s number. Refrigerant type and charge cleared. Pump model and c0/c1 cleared. Element capacity per system cleared. Control settings cleared.
• ComHPdata: All test data rows deleted. Headers and instructions preserved.
• Tanks: All tank model rows deleted. Headers preserved. Example row preserved (clearly labelled as example).
• Audit: All model entries, application folder names, equivalent model references cleared. Document filename columns cleared.
• CPL: Delete all CPL_{ModelName} sheets — these are auto-generated by Find Loads.
• All sheets: Find-and-replace search for prior project codes (AE prefix), previous client short codes, and any prior model codes the modeller is aware of. Replace with placeholders or delete.
• Macro settings tab: TRNSYS file output path updated to current project Temp folder. Any cached file paths from previous projects cleared.

---

Confirm Type 160 template

Type 160 is the standing default for VEU modelling. Open the chosen TRNSYS template (.tpf) from /Templates/TRNSYS/Templates/ and confirm the tank component is Type 160. If it is Type 60, convert the template to Type 160 before proceeding.

---

TRNSYS file location

The tool writes TRNSYS files (.dck, .lst, .out) to a local C:\TRNSYS15\Include&weather\AExxx_ClientName\ folder during simulation. Ensure there is sufficient disk space before running large batches of simulations.

C:\TRNSYS15\Include&weather\AExxx_ClientName\
├── FAM_COM\          ← Final annual simulation files (post CPL)
├── CPL_Calibration\  ← Intermediate CPL search files

---

Common issues

• CPL sheet remnants reappear: the Find Loads macro regenerates CPL_* sheets per model. If old sheets reappear, the macro is reading a stale FAM_COM model list — confirm only current models are listed.
• Type 60 / Type 160 confusion: if the tank model in the FAM_COM dropdown does not match the template you opened, you have a template mismatch. Re-confirm the template choice before running simulations.