Archeon Global Private Limited
Engineering a more certain tomorrow.
We build engineering software whose numbers carry their own evidence: the formula as implemented, the values actually substituted into it, the clause it answers to, and who chose what.
The problem
A number nobody can trace is a number nobody can defend.
Storage-tank, pressure-vessel and piping teams run design work through chains of interlinked spreadsheets. Shell thickness feeds foundation loads. Shell weight feeds seismic. Seismic moments feed anchorage.
Every hand-off is re-typed. Every revision quietly invalidates something downstream. And when a package is issued, nobody can say which of its numbers are still current.
The answer
Calculations that link, and refuse to drift.
Data flows between calculations through explicit, locked links. No re-entry, no transcription. When an upstream result changes, everything downstream becomes derivably stale, never silently updated.
Freshness is recomputed from content hashes at read time rather than stored as a flag, so it propagates through the whole chain and a stale result is structurally incapable of rendering as current.
Products
One company, one standard of proof.
Each product is named for itself and endorsed by Archeon Global. Each owns one accent colour; the navy belongs to the parent.
-
TankLogic
LiveAPI 650 storage-tank design, out of Excel.
Twelve linked calculation modules (data sheet, shell, bottom and annular plate, fixed roof, wind girder, nozzle reinforcement, foundation, wind overturning, seismic, anchorage and floating roofs), with derived freshness, provenance on every value, and signed, issue-ready calculation packages.
- Storage tank design
- Tank analysis
- Design verification
- Calculation packages
tanklogic.archeonglobal.com · access on request
-
Archeon Engineering
ServicesThe practice behind the software.
Design, analysis and verification work carried out by engineers, using the same calculation discipline the products enforce.
-
Pressure Vessel Engineering
In planningThe next standard, the same architecture.
A separate engine named for the code it implements, sharing the link graph, the freshness model and the package format.
-
Piping Engineering
In planningWhere the chain of spreadsheets is longest.
Line sizing, stress and support design, linked into the same tank and vessel models rather than re-entered beside them.
How we build
Five rules, and none of them bend.
These are not values on a wall. Each one is enforced in code, and each exists because its absence has cost somebody a re-issued drawing.
-
01
Traceable, or it does not ship.
Every calculated value carries the formula as implemented, the values actually substituted, the clause it cites, and the engine version that produced it. Click any number and walk upstream to the values that were entered.
-
02
Refuse, don't substitute.
When the software cannot be sure, it stops and says so. A quarantined module halts everything downstream; two modules disagreeing about the same physical property block sign-off. A plausible number is worse than no number.
-
03
Nothing changes silently.
Recalculation is a human act. Change an input and the software names how many calculations it invalidated, then recomputes them in dependency order on one confirmation, halting at the first failure rather than pressing on.
-
04
A choice is recorded as a choice.
A value the code leaves to judgement is an input with a computed default, not a number the engine picked and labelled arithmetic. Engineering decisions are attributed. A value below the code minimum is refused, not warned about.
-
05
The standard is not ours to rename.
We name our products. We never rename the codes they implement. A clause reference in a calculation package becomes a fabrication drawing and then a steel order, so “API 650” stays API 650, in every string that means the standard.