Appearance
Engineered Templates — Overview
A Level-1 drawing template that also carries its own engineering: a plant model, generated control logic, an I/O schedule, an alarm schedule, a calculation sheet and a control philosophy — plus a workspace where the placed unit can be run.
Which "simulation" this section is about
ErgoPlanner contains two different things called simulation, and this section documents only one of them. Read this once; every page in this section repeats the short version.
| Process simulation (the other one) | The unit scan simulation (this section) | |
|---|---|---|
| Where it runs | On the server | In your browser |
| What it models | Biokinetics and settling of a flowsheet — ASM1, ASM2d, ASM3, ADM1, Anammox, the Takács layered clarifier | The control logic and physics of one placed unit — a PLC-style scan over the unit's generated control graphs, with a plant model integrating alongside it |
| Subject | A whole process model you built | A single engineered template instance you dropped on a drawing |
| What comes out | Effluent quality, mass balance closure, scenario comparison | Levels, flows, pressures, equipment states, alarms, trends and run metrics for that one unit |
| Where in the product | Simulation and Process Units | The Simulate view of the template workspace, described on The Template Workspace |
They do not share a solver, a model library, a page or a data store. A unit scan simulation says nothing about effluent quality; a process simulation says nothing about whether a duty/standby selector behaves when a float sticks closed.
Throughout this section, "the simulation" always means the client-side, single-unit, PLC-style scan simulation that runs in the browser.
What an engineered template is
An ordinary drawing template — the ones described under Drawing Templates — is parametric geometry. You answer its parameters, and it draws a correct, pre-solved P&ID arrangement: symbols, connections, tags, instruments. That is the whole of its job, and for most arrangements it is enough.
An engineered template is an ordinary Level-1 template plus one more thing: an engineering block. Because that block exists, the template knows things about itself that geometry alone cannot express:
| It carries | Which means |
|---|---|
| A design basis | The derivations behind the drawing — flows from a population equivalent, a design storm from a rainfall intensity, air demand from a load — rather than numbers you typed |
| A plant model | Physics the unit can be stepped through: a level that rises and falls, a header that pressurises, an aperture that passes flow at a head |
| Generated control graphs | The control logic as executable graphs — level bands, duty/standby selectors, PID loops, sequencers, hardwired protection — derived from your configuration, not drawn by hand |
| An I/O schedule | Every signal the configuration implies, with its card and channel, and the panel sized from the totals |
| An alarm schedule | Each alarm with its priority and its action |
| A calculation sheet | Every design figure with its formula, its value, and the rule set it is checked against |
| A control philosophy | Prose generated from the same model the loops and the schedules come from |
| Published port values | Process values at its interface points, not just a connection size — so a neighbour can read what this unit hands it |
| A fault catalogue | Named single failures that can be injected while it runs |
The practical difference is this: change the number of pumps on an ordinary template and the drawing changes. Change the number of pumps on an engineered template and the drawing, the control graphs, the I/O schedule, the alarm schedule, the calculation sheet and the control philosophy all change together — because they are all generated from one resolved model.
How to tell them apart in the app
| Ordinary Level-1 template | Engineered template | |
|---|---|---|
| Category | Process Units/… | Process Units/engineered |
| Name in the library | e.g. Chemical Dosing Skid | suffixed (Engineered Unit) — e.g. Storm Tank (Engineered Unit) |
| On drop | Places immediately with its defaults | Intercepted — a Confirm key parameters panel opens first (Placing an Engineered Template) |
| After placing | A group of drawn elements | A group of drawn elements plus a registered template instance |
| Double-click | Edits the element label | Opens the template workspace (The Template Workspace) |
| Properties panel | Standard element properties | Adds a Template instance section with inputs, published outputs and a workspace link |
What ships today
Seven engineered units are seeded. All seven are published and visible to everyone who passes the other gates.
| Unit | Slug | Seeded version / maturity | Page |
|---|---|---|---|
| Wastewater Pumping Station | ww-pumping-station | 0.6.0 · published | Wastewater Pumping Station |
| Flow Balancing Tank | flow-balancing-tank | 0.1.0 · published | Flow Balancing Tank |
| Aeration Blower Set | aeration-blower-set | 0.1.0 · published | Aeration Blower Set |
| Flow to Full Treatment Control | fft-flow-control | 0.1.0 · published | Flow to Full Treatment Control |
| Storm Tank | storm-tank | 0.1.0 · published | Storm Tank |
| Chemical Dosing | chemical-dosing | 0.1.0 · published | Chemical Dosing |
| Storm Overflow Chamber | storm-overflow-chamber | 0.1.0 · published | Storm Overflow Chamber |
All seven are published. Chemical Dosing and Storm Overflow Chamber were promoted from draft on 2026-10-24 once their configuration matrices passed and the reviewer sign-off was given (by default answer, on the owner's instruction).
Chemical Dosing (engineered) is a different template from the ordinary Level-1 Chemical Dosing Skid (chemical-dosing-skid, published). The skid places geometry only and has no workspace. See the unit index.
Why you may not see them in the stencil yet
Template visibility is decided by four gates, all applied on the server:
- Maturity. Only
publishedtemplates are visible to everyone.draft,review,approvedanddeprecatedtemplates are visible only to a company Admin or Owner, or to a SuperAdmin. All seven engineered units are published and pass this gate. - Plan. Engineered templates (category
Process Units/engineered) require the engineering suite on your plan; ordinary system templates require the standard template library. - Tenant enablement. An Admin can enable or disable individual engineered templates for the company.
- User allocation. An Admin can allocate an engineered template to specific users or roles. With no allocation rows for a template, everyone in the company who passes the other three gates may place it.
A template you may not use returns a 404 rather than a 403, so the stencil simply does not list it.
Demo-review tenants. On a tenant that carries a demo-feature list, the template workspace route sits behind feature F3 (Templates). A tenant with no such list — everyone but the demo review tenants — is unaffected.
Where to go next
| I want to | Page |
|---|---|
| Put one on a drawing and answer its parameters | Placing an Engineered Template |
| Open the workspace and understand the nine views | The Template Workspace |
| Read about a particular unit | The seven units |
| Understand the ordinary template system | Drawing Templates Overview |
| Run a biokinetic process model instead | Simulation Overview |