Step 01
The design is read
An architect's file arrives. The system reads every element and works out what the drawings never say: which parts carry which, and what has to happen first.
Automated Construction Engineering
Design tools end at the model. Bulrix runs everything after it.
Machines, crews and deliveries on one plan. Each task goes to whatever holds the capability it needs, machine or crew. Nothing behind a gate goes out until what it stands on has been measured and passed.
The constraint
The limit on automated construction is not the machine. A machine cannot ask a question, judge a vague drawing, or notice that something looks wrong. Give it the information construction produces today and it builds the error faster and more precisely than a person would.
Projects lose time and money after the model, not before it. Design hands over to estimating, estimating to procurement, procurement to the field, and every handover drops something nobody writes down. Bulrix holds all of it.
1System, model to handover
5Disconnected tools it replaces
0Commitments made without a person
3Rules bound every schedule
Design to delivery
How a design becomes a building.
The intelligence layer
One connected model. One schedule.
One connected model. One schedule.
One record of what was built.
A project normally lives as drawings in one system, a schedule in another, orders in a third and progress in someone's photographs. Bulrix holds them as one model, so a change anywhere is traceable to everything it touches, and the schedule is computed instead of maintained by hand.
The plan is bound to reality
The schedule names the crew, the machine and the product, and recalculates the moment one of them changes. A late delivery or a failed inspection is followed through to its consequences on every job, not just the one it happened on.
It learns from its own corrections
A duration is a rate against something the design measures, so it is an estimate about this building from the first day. What the work actually takes corrects the rate, and the correction carries how many completions stand behind it. The engineering figures, what a wall carries and how fast it may rise while it is still soft, start as published models and are replaced by measurements from this pour.
It proposes. A person decides.
The system prepares, ranks and explains, inside the options the constraints allow. It commits the organisation to nothing on its own. That is deliberate and permanent: an advisor that occasionally acts unasked is one nobody can rely on.
Scope
One trade now. The architecture is sized for the rest.
Which part is automated, and which part is only coordinated.
01
Now
Printed structure
A printer makes the walls: a fifth of the building by work content on the house this was measured against. Conventional trades build the rest.
02
Next
Trade by trade
Work is described by the capability it requires, never by who performs it. So the next machine arrives as a profile and an adapter, not a rewrite.
03
Then
The automated job site
We are building the operating layer now, before the machines arrive.
The platform
One system, from the model to the finished building.
Five stages between the design and the keys. One model runs through all of them.
Stage 01
The design is read
A design arrives from the architect. The system reads every element and its geometry, then derives the relationships no drawing carries: what bears on what, what has to precede what, what has to be coordinated with what. None of it is typed in.
Stage 02
Buildability goes back
What the machine, the mix and the approval allow goes back to the design team while they are still drawing. Every finding names the nearest buildable alternative and what the difference costs. A stated reason can be argued with; a bare refusal gets switched off.
Stage 03
Work is derived
Elements become operations. A wall expands into the work that produces it, with dependencies, durations and the capability each piece needs. This is the step that makes a model executable.
Stage 04
The build is scheduled
Crews, machines and material deliveries are scheduled across the whole portfolio at once, not one job at a time, then recomputed the moment the site stops matching the plan.
Stage 05
It is built and handed over
Machine parameters reach the operator, work orders reach the trade crews. Progress is measured on the ground, and the home is delivered with a record of how it was built, not how it was drawn.
Capabilities
One workflow across the machines and the trades.
Scheduling
Dynamic site scheduling
Everything that has to be in the same place at the same time moves on one plan, recomputed whenever the site says otherwise. Anything that moves a date somebody else has committed to leaves as a proposal to them, never an instruction.
Dispatch
Capability-based dispatch
Every task carries the capabilities it demands; every executor carries a profile. A machine and a trade crew are matched the same way, because work is never described by who performs it.
Field
Field-driven operations
Contractors, operators and suppliers are reached directly. A work order carries the setting-out and the variance it asks them to absorb. Acceptance is a signed link: every agreement is attributable and there is no portal to learn.
Verification
Real-time verification
A measurement taken in the field becomes the truth for that element, and everything downstream re-derives from it. It releases the work standing behind it, and it is the record the home is handed over with. Verification is a gate, not a dashboard.
The principles
Every schedule is optimised in this order.
The objective is completed work per unit of labour, machine time and material, measured across the whole operation and not one job. Three rules bound every schedule it produces.
1
Quality is never traded
An absolute limit, not a preference. The schedule may not propose anything that breaks a constraint: no shortened print, no work begun before a cure has elapsed, no crew or machine without approval for it.
2
Committed dates hold
Every home carries its own committed date, and the system only optimises within plans that hold all of them. Where no such plan exists it says so, names the date that has to move, and prices the alternatives.
3
Then cost is minimised
Cheaper is better only once quality is protected and the dates are held. Productivity is measured across the whole operation, because idle time and repeated mobilisation are where it actually goes.
Careers
Work on the system that runs the build.
The work is software and hardware: the models that describe a home, the schedulers that plan it, the machines that build it. Tell us what you have built.
Contact
If you are building with a printer or funding the people who will, we should talk.
Tell us what you are building and what you need to know. A technical question gets a technical answer, from a person.