Services / Service line 05
BIM Production
BIM production, powered by our own automation.
02problem
The problem
Outsourced modelling capacity is easy to find and hard to trust. The common failure is not that the model arrives late — it is that it arrives, looks finished, and quietly breaks your standards: parameters half-populated, families rebuilt instead of reused, worksets improvised, a schedule that no longer matches the sheets. The rework lands on your senior people, which is exactly the cost the outsourcing was meant to avoid.
Our production work is run by the same team that writes automation software for Revit and Tekla. That means the quality checks on our output are scripted rather than eyeballed, and standards compliance is verified by a rule engine on every delivery rather than sampled at the end.
03capabilities
What we deliver
Modelling
- Architectural, structural and MEP modelling at LOD 200–400
- Family creation and parametric content libraries
- Template, workset and standards setup
- Scan-to-BIM and point cloud processing
Documentation
- Shop drawings preparation
- Construction documentation sets
- Schedules, quantities and takeoff data
- As-built documentation
Coordination
- Federated coordination models
- Clash detection, prioritisation and reporting
- Cross-discipline coordination support
- 4D phasing and sequencing
Data
- ISO 19650 and client-specific standard compliance
- Model health monitoring and reporting
- BIM-to-ERP data extraction pipelines
04where_it_breaks
Where it breaks
Six ways outsourced production quietly costs more than it saves.
Standards drift
Across a team and a few months, conventions decay. Naming, parameters and worksets diverge slowly enough that nobody notices until coordination. We check standards programmatically on every delivery, using the same rule-engine technology we build for clients.
LOD ambiguity
“LOD 350” means different things to a fabricator and an architect. Where the definition is not written down element by element, the disagreement surfaces at handover. We agree it in writing at scoping.
Reused families
Rebuilding content instead of using your library is the fastest way to poison a model. Your library is the source; additions to it are reviewed and returned to you.
Model health over time
File size, warning counts and purgeable content accumulate. A model that was healthy at month one is unusable at month eight without active monitoring.
Handover fidelity
Native files, IFC exports and coordination formats do not carry identical information. Which format governs, and what is verified after export, is agreed before delivery rather than discovered after it.
Capacity that is actually senior
Scaling a production team by adding junior modellers moves the QA burden to you. We stay small deliberately and use automation for volume instead.
05stack
Stack and coverage
- Platforms
- Revit, Tekla Structures, Navisworks, AutoCAD, ArchiCAD file handling, IFC
- Automation
- Our own plugins for QA, views, numbering, clash workflows and phasing
- Standards
- ISO 19650, client-specific BIM execution plans
- Delivery
- ACC, BIM 360, or the client’s environment
06proof
Proof
The automation we use in production is our own commercial software
The same tools we sell. Teams at Swinerton and Dusty Robotics use tools we built.
White-label
Production capacity is available under a partner’s brand, including partner-branded deliverables and direct participation in the partner’s coordination process.
Case — pending
Format: the client had X. It broke at Y. We built Z. The measurable outcome was W. Two to three per page, anonymised where required.
07engagement
How we work
Scope and LOD are defined in writing before work begins. Pricing is LOD-based and fixed for a defined scope. Ongoing capacity is contracted as a monthly retainer. Deliveries pass automated standards checks before they reach you.
08faq
Frequently asked
Can you work to our standards and templates?
Yes. Your templates, families and naming conventions govern, and we verify compliance programmatically rather than by inspection.
Can you work under our brand for our clients?
Yes. White-label production for partners is a core part of this service line.
What LOD do you deliver?
LOD 200 through 400, defined element by element at scoping so there is no ambiguity at handover.
How is this different from a large offshore modelling provider?
Scale is not our advantage; automation and seniority are. The same engineers who write BIM automation software run the production, so quality control is scripted and repeatable.
09model_viewer
Model viewer
Sheet 07 — 3D model
3D model slot
GLB export from Revit via Blender
orbit · zoom · isolate
The model itself, in the browser, for everyone who does not hold a licence — the same argument the service pages make, made visible.
- Source
- Revit → Blender → GLB
- Interaction
- Orbit · zoom · isolate
- Download
- OBJ + MTL · GLB
- Part naming
- Revit categories preserved
Asset — pendingClient supplies the GLB; the viewer, download and part naming are already specified.
From prototype to production
AI made prototypes cheap. We make them ship.
A Feasibility Review is a 30-minute technical session with the engineers who would build it, followed by a written verdict: what the API actually allows, where it will break at scale, and what production costs. No obligation to proceed.
- Straight answers
- Written verdict
- Senior engineers, not account managers