About ABAXES

A civil engineering perspective on automation.

ABAXES started from engineering work, not from software marketing. It is a bridge between traditional engineering expertise and modern automation, AI and digital workflows.

Why ABAXES exists

Useful engineering systems — not AI gimmicks.

Structural engineering depends on judgement, checking and clear communication. Much of the work around it — re-entering geometry, transferring loads, updating schedules, assembling reports — is repetitive and easy to get wrong.

ABAXES explores how that surrounding work can be automated carefully: through each program’s official API, with explicit assumptions, and with results an engineer can verify. It is created by a civil engineer who works with these tools and wants them to work together better.

The measure of success is simple: the engineering becomes clearer, faster and easier to check — never less transparent.

The intersection

Five disciplines, one reference line.

An axis is the line a structure is set out from. ABAXES takes the same idea to the tools around engineering: a shared reference where structures, data and decisions align.

01

Structural engineering

Load paths, analysis and design checks — the discipline everything else has to serve.

02

BIM

Models as structured, queryable information rather than drawings alone.

03

Engineering software

Revit, ETABS, SAFE and CAD tools, driven through their official APIs.

04

Automation

Removing repetitive, error-prone steps while keeping each step visible.

05

Artificial intelligence

Applied where it genuinely helps, behind defined tools and engineer review.

Principles

Precision, clarity and progress — with the engineer in the loop.

Precision

Evidence-led work. Numbers are traceable to their source.

Clarity

Understandable outputs. If a step cannot be explained, it is not finished.

Progress

Future-ready thinking, tested on real engineering problems first.

Engineer in the loop

Software assists. Judgement and responsibility stay with the engineer.

Start a conversation

Have an engineering workflow worth automating?

Describe the workflow, the software involved and where the time goes. Every message is read personally.