Statistical Soil Modelling
Borehole data turned into probabilistic layer models rather than one conservative profile, so a design can be evaluated against the ground as it was actually measured.
Services
Software That Knows What a Pile Does
We build the calculation and optimization tools geotechnical practices work in, from statistical soil models through to design output that satisfies EA Pfähle and Eurocode 7.
Get Started
What we build
Geotechnical software fails on the details. The soil model, the partial factors, the annex that applies in one country and not the next.
Generic engineering tools treat geotechnics as one more load case. The result is software that cannot express what a borehole log actually says, or that produces numbers an engineer has to redo by hand before signing anything. We build in this field, so the details that decide whether a tool is usable are the ones we start from.
Design Optimization
Engines that evaluate thousands of configurations against structural requirements and return the leanest one that holds, with the reasoning attached.
Code Compliant Output
Calculations that follow EA Pfähle and Eurocode 7 with the relevant national annexes, and documentation an engineer can put their name to.
* On pilot projects in Germany, optimized designs have come in around 25 percent lighter on material. What a given project achieves depends on ground conditions and design constraints.
How we work on it
-
Start From the Calculation
Before any interface exists we work through the engineering with your team: which standard governs, which partial factors apply, what the tool must never be allowed to output. This is where geotechnical software is won or lost, and it is the part a generic development team cannot do for you. We come out of it with a specification an engineer has checked.
-
Build It Where Your Work Already Is
The tool has to fit the practice. That means the file formats your projects arrive in, the reporting your clients expect, and the systems you already run, whether that is a desktop application, a plugin inside an authoring environment, or a service your other tools call.
-
Validate Against Real Projects
Every calculation path is tested against projects you have already delivered, where the answer is known. Your engineers review the output and sign it off before anything is used in anger. We iterate until the numbers hold up, then we keep maintaining them as the standards move.
We work in this field, which is why the software behaves like it.
Our own practice designs foundations, and piledesigner.io came out of that work. That is the difference you feel in the details: what the tool refuses to do, what it asks you to confirm, and what it hands you at the end. Not a demo of what geotechnical software could be, but the thing engineers use to get projects out.
- Engineering decided first and the interface built around it, never the reverse
- Validated against completed projects, not against synthetic test cases
- Maintained as the standards and national annexes change
Have a calculation your current tools cannot express?
Tell us what you are trying to model and where the software you have gets in the way. We will come back with an honest read on what is worth building.
