WYRMMEP
Agentic MEP engineering. A structured studio of agents drafts your specifications, builds your schedules and coordinates every discipline — sitting above an integral suite of calculation engines that handle thermal modelling, CFD airflow, daylighting, BS 7671 electrical and the design-stage BRUKL / EPC build-up. Rule-based logic trees do the engineering; your engineer signs. WYRM gives your engineers their time back.
New here? What is agentic MEP?
What WYRM MEP is
A studio of agents over an integral calculation suite
WYRM MEP is agentic MEP engineering: a structured team of agents that plan, draft and coordinate like a real design office, sitting on top of an integral suite of calculation engines. The agents organise the job; rule-based logic trees do the engineering; your named engineer signs. Not a chatbot bolted onto a drawing — a coordinated design system.
Auto spec + schedule, reconciled
Drop your ERs and outline spec on the canvas. WYRM extracts and locks the design constraints — each traced back to the paragraph it came from — then drafts the specifications and the schedules and continuously checks one against the other, so the spec and the schedule never drift apart.
Nothing sized in isolation
The Project Terminal holds the whole job together on a rule-based logic tree. Move an MFSD and WYRM walks the engineering chain it sits in — the realigned power supplies, the breaker that has to be uprated, the volt-drop re-check, the drawings affected — and surfaces every consequence with a suggested action. The interdependencies are the job, and they are mapped, not remembered.
Computed, never guessed
Every figure comes from an integral suite of calculation engines — rule-based logic trees, not a language model. Design-stage thermal modelling and energy (Design Stage EPC and the SBEM / BRUKL build-up), CFD airflow, daylighting and BS 7671 cable sizing are all computed deterministically: the same inputs return the same result, each number cited to the standard and the line of working behind it. The agents organise the work; the engines do the maths.
Advisory, never authority
Two independent QA gates check the join, then everything stays a draft until your named engineer reviews and signs — and nothing keeps its signed status once the basis underneath it moves. Every output carries a full calculation pack: inputs, rule versions, sources and an audit hash. Your engineer stays responsible throughout.
The Project Terminal
Auto spec, checked against auto schedule — every change tracked
The consolidated panel where untracked changes surface with suggested actions. Toggle Manager ↔ Engineer: the manager sees what was promoted; the engineer sees the recommended regulation fix, the consequential items from every other discipline, and the itemised tasks. Click any glowing element in the 3D model for the reasoning behind the recommendation.
Project Terminal
Slough DC · Stage 3 · Demo
Draft-only. Nothing is applied until your named engineer reviews and signs. Every change carries a calculation pack with sources and an audit hash.
Auto-generated specifications
Specifications written from the locked spec — every clause cited
From the same locked design constraints, WYRM drafts the particular specification clause by clause. Each clause is classified by Uniclass, costed by NRM2, and grounded in a citable standard — the model can only assemble clauses returned by typed tools, never invent one. A compliance gate re-checks every output before your engineer ever sees it.
01 · Standards database
Typed clause graph
Every BS EN, CIBSE TM, IET regulation and Approved Document parsed once into a structured graph. Clauses are typed by discipline, classified by Uniclass, costed by NRM2, and linked to the equipment schedules that satisfy them.
02 · Grounded generation
Tool-bound language models
Generation runs at temperature 0 with a fixed seed. The model cannot write a clause; it can only call typed tools that return clauses retrieved from the database. Every numeric value, threshold and scheme name is grounded in a citable source.
03 · Compliance gate
Validate before it reaches you
Every output is re-parsed and checked: cross-reference integrity, mandatory citations, scheme conflicts, discipline coverage. A failed validation rolls the document back. Your engineer never sees an unchecked clause.
CL-Y50-MEC-001.docx
Generating
References
Live mock. Every clause is anchored to a citable reference — no hallucinated standards, no invented clause numbers. Switch tabs to change discipline.
28 MCP tools across 11 disciplines
Disciplines covered
Heating · Cooling · Ventilation · Hot & cold water · Drainage · Gas · LV electrical · HV electrical · Lighting · Data · Fire detection
The calculation suite
WYRM never lets a language model size a cable
Behind the agents is an integral build of calculation engines — rule-based logic trees, not a model writing numbers. Inputs auto-populate from the live model, the engines compute (the same inputs always return the same result, cited and versioned), and results write back to the same families and schedules. One source of truth, no rekeying, no drift.
Electrical distribution
BS 7671:2018+A2:2022 · IET
Cable sizing from installation method, grouping and ambient; protective-device coordination, volt-drop and Zs / earth-fault loop.
Ventilation & CFD airflow
CIBSE · Approved Document F
Fresh-air rates, duct sizing to Δp/L limits, and CFD airflow studies for hot/cold-aisle and plantroom strategies.
Thermal modelling & energy
Design Stage EPC · SBEM / BRUKL
Design-stage heat balance and energy screening — the calculation build-up behind a design-stage BRUKL / EPC submission, not a lodged certificate.
Lighting & daylighting
SLL · BS EN 12464-1
Illuminance and uniformity to task, daylight factor and glare — luminaire schedules written back to the model.
Public health & pipework
BS EN 806 · BS 8558
Hot and cold water demand, pipe sizing to velocity limits, and clash-aware routing of building services.
Compliance & QA rules
Approved Docs · CIBSE · IET
Deterministic checks on every computed design — limits, coverage and standards conflicts — flagged before your engineer signs.
See one engine run — BS 7671 cable sizing, live
Sample calculation
LPHW flow — diameter from heat load
Source
Revit · Space + Mechanical Equipment
Calc engine
deterministic · cited · versioned
Target
Revit · Pipe Type + Pipe Segment
Inputs auto-populate from the live drawing · results write back to the same families and schedules · single source of truth with zero information loss.
Heat load
← Revit · Space.HeatingDesignLoad
Loop ΔT
← Revit · MechSystem.DeltaT_K
Water density
← Project · Fluid Library @ 70 °C
Specific heat
← Project · Fluid Library @ 70 °C
Max velocity
← Standards · CIBSE Guide C §4.1
Mass flow ṁ
Q·1000 / (cp·ΔT)
Volume flow V̇
ṁ / ρ × 1000
Required area
V̇ / vmax
Required bore
√(4A/π)
Pipe size
round-up next listed DN
→ Revit · PipeType.NominalDiameter
Velocity actual
within ±10% commissioning band
→ Revit · Pipe.FlowVelocity (calc param)
Governing
velocity ≤ 1.2 m/s · BS 5970 insulation per loop temp
MEP Advisor · £20/seat
“Can I swap this for that?” — answered against the spec and the standards
The fastest way to put WYRM in front of your engineers — a QA surface for the questions that come up mid-design. Ask whether a substitution still works, whether a cable or duct is OK instead of the specified one, or anything from the standards, and the Advisor answers from WYRM's standards-grounded repository — BS 7671, the CIBSE guides, the Approved Documents — with clause-level citations and a confidence score. It flags when it's unsure instead of inventing.
Try another question
How it works
From scoping documents to signed deliverables
Tracked to the RIBA Plan of Work. A layer above the tools you already own — Autodesk, Amtech, IES, Aconex, Office — not another island.
Lock the spec
WYRM reads the ERs, outline spec and drawings, then extracts and locks the design constraints as one cited source of truth.
Generate + reconcile
Specifications and schedules auto-generate from the locked spec and are checked against each other. Deltas surface on the Project Terminal — never silently applied.
Coordinate the cascade
Every change fans out across disciplines on a rules-based graph. Consequential items and itemised tasks are tracked to the RIBA Plan of Work.
Review, sign, write back
Your engineer reviews the calc pack and signs. WYRM writes back to Revit / AutoCAD with genuine manufacturer data. Advisory throughout — your engineer submits.
Roadmap
Roadmap · where WYRM MEP is going
Delivered as phased pilot releases. The destination is an advanced RIBA Stage 3/4 MEP design and coordination package — populated Revit models, coordinated specifications and schedules, design-stage energy screening, CFD and the full compliance pack — built to the structure the industry already works to. The aim is to take up to 90% of the manual workload off your engineers without ever taking the authority off them.
90%
target reduction in the manual workload carried by MEP engineers — the judgement stays with them.
The destination
An advanced RIBA Stage 3/4 MEP design package.
Built to the structure the industry already works to — RIBA Plan of Work and BSRIA BG6 — so the output drops straight into a real submission workflow rather than living in a silo.
What a release will help produce
Populated Revit model
Real MEP geometry — ducts, pipework, cable containment and plant placed with manufacturer families and connectors, coordinated and clash-aware. The model the team draws from, not block placeholders.
Coordinated specifications
Discipline specifications written from the design data and kept in lock-step with the model as it moves. Every clause anchored to a citable standard.
Schedules
Equipment, valve, cable and load schedules pulled live from the coordinated model — no re-keying, no drift between drawing and table.
Design-stage EPC / BRUKL
Part L energy screening (SBEM-equivalent) produced alongside the design — the calculation build-up behind a design-stage submission, not a lodged certificate.
CFD airflow + thermal modelling
Ventilation, cooling and thermal-comfort screening across the design — an integral calculation build, IES-equivalent, sized to the systems WYRM has already specified.
Compliance pack
BS 7671 cable calculations, regulation-applicability and self-healing reg-watch — every output stays bound to the live standard, and nothing stays signed once the basis moves.
The advance pilot programme is open
WYRM MEP is already running live pilots with UK MEP consultancies. We're enlisting the next cohort now — a small number of practices who shape the product around their own standards, templates and house style while their engineers keep full sign-off authority. Phase 1 is documents-first; metered drawing automation follows. You join as a build partner, not a test subject.
Built around your standards
We load your spec library, templates and house style so the output reads like your office wrote it.
A direct line to the build team
Weekly working sessions. Your feedback lands in the product — pilots steer the roadmap.
Fixed pilot fee, fast start
A simple fixed monthly pilot, live in weeks on the work you already have in flight. Limited seats this quarter.
Pricing
Start small, scale to the team
Minimum 5-seat team licence. Automatic drawing population (Revit / AutoCAD write-back) is billed as metered usage on top of the full tier.
MEP Advisor
On-the-job QA: 'can I swap this for that?' answered against the spec and the standards — cited and confidence-scored. The fastest way to try WYRM.
- 'Can I swap X for Y?' substitution checks
- BS 7671 / CIBSE / Approved Docs Q&A
- Clause-level citations on every answer
- Confidence scores — flags when unsure
WYRM MEP
Most teamsThe full agentic studio: auto spec + schedule, the Project Terminal, algorithmic engines and QA gates.
- Auto spec + schedule generation, reconciled
- Project Terminal change-cascade + suggested actions
- BS 7671, ventilation, Design Stage EPC engines
- Metered Revit / AutoCAD drawing automation