01
Package delivery
A defined scope with a fixed deliverable list and programme — a discipline model, a coordination package, a drawing set. Priced against the deliverable.
Engineering depth is what makes the intelligence defensible
MEP engineering, BIM delivery and automation, defined by what is produced and issued rather than by which software is opened. Every line carries its capability status.
Service architecture
Three categories, not a list of twenty services
Automation sits alongside engineering and BIM as a category of its own, because that is how it is scoped and priced here — not as a paragraph at the end of a modelling proposal.
CATEGORY 01
Engineering
Building services engineering with real discipline depth. This is the layer that makes the rest defensible.
- MEP engineering Live
- HVAC and ductwork Live
- Public health and drainage Live
- Fire protection Live
- Electrical distribution Live
- Engineering calculations Live
- Equipment selection Live
- System analysis Live
CATEGORY 02
BIM
Model authoring, coordination and documentation — structured so the data inside is usable, not only viewable.
- BIM modelling Live
- BIM coordination Live
- Clash detection Live
- Model QA / QC Live
- Documentation Live
- Quantity extraction Live
- Revit and IFC exchange Live
- CDE and delivery Live
CATEGORY 03
Intelligence
The layer we are building. Automation is a service category here, not a footnote on a modelling proposal.
- Design automation In development
- Engineering automation Live
- Model intelligence In development
- Automated QA rule sets Live
- AI engineering agents In development
- Generative workflows Roadmap
- Digital twin Roadmap
- Predictive engineering Roadmap
Scope detail
What is actually produced and issued
Every capability below lists its deliverables. Any of them can be appointed on their own or combined; nothing here depends on buying the intelligence layer.
Capability 01BIM Modelling & DocumentationLive
Discipline models authored to an agreed level of information need, with drawings and schedules derived from the model rather than drafted separately. Model setup, templates, shared coordinates and naming conventions are established before authoring starts — which is what makes the data usable later.
- Architectural modelling
- Structural modelling
- MEP modelling
- General arrangement drawings
- Sections, elevations and details
- Door, room and equipment schedules
- Family and content creation
- Model templates and standards setup
Capability 02MEP EngineeringLive
Building services modelled as connected systems, routed against the spatial and access constraints they must satisfy. Sizing and performance data are held on the elements, so the model can be interrogated rather than only viewed — this is the discipline depth the intelligence layer depends on.
- HVAC and ductwork distribution
- Plant room layouts
- Electrical distribution and containment
- Lighting and small power
- Public health and drainage
- Domestic water services
- Fire protection and sprinklers
- Equipment schedules and data
Capability 03BIM CoordinationLive
Federated models assembled from all contributing disciplines, with clashes tracked to closure and each decision recorded. The output is a resolved model and an auditable issue history, not a raw clash count — a number nobody can act on.
- Federated model assembly
- Clash detection and rule sets
- Clash resolution and re-testing
- Coordination issue tracking
- Services zoning strategy
- Clearance and maintenance access checks
- Coordination reports
- Coordination workshop support
Capability 04Design & Engineering AutomationLive
Automation applied to repetitive production and checking, and model data managed as a deliverable in its own right. This is a service category rather than an add-on: it is quoted, scoped and delivered as work, and it is where the intelligence stack meets an appointment.
- Parametric and computational workflows
- Automated model checking routines
- Parameter and data management
- Model auditing and health checks
- Data export and reporting
- Common data environment structure
- Naming and classification automation
- Digital delivery packaging
Capability 05Construction SupportLive
Model-derived output produced for the people installing the work, at the detail and tolerance installation actually requires rather than at the level a design model happens to hold.
- Shop and fabrication drawings
- Spool and prefabrication drawings
- Builders work and penetration drawings
- Bracket and support layouts
- As-built and record models
- Quantity take-off and schedules
- Site query support
- Handover information packaging
Appointment models
How engagements are usually structured
02
Team extension
Modelling and engineering capacity inside your team and your environment, working to your standards and your BEP, for a defined period.
03
Coordination appointment
Federation, clash resolution and coordination management across contributing disciplines, with the issue history as a deliverable in its own right.
04
Automation engagement
A defined workflow automated for your team — a QA rule set, a quantity routine, a documentation pipeline — delivered as tooling plus the engineering behind it.
Tooling
Deliverables are defined by the information required, not by an application
Where a project mandates a toolchain, we work in it.
AuthoringModel production
Revit · AutoCAD · discipline-specific MEP authoring tools
CoordinationFederation and review
Navisworks · federated model review and clash workflows
AutomationRoutines and checking
Dynamo · scripted routines · custom checking and data tools built
in-house
ExchangeInteroperability
IFC · COBie-style data exports · common data environments
Software names are the property of their respective owners and are listed to describe working practice. No partnership, certification or endorsement is implied.