All of ORB's reasoning lives in one engine — plain, verifiable and free of vendor lock-in. Every judgement it returns can be traced back to the measurement, the standard and the phase it was built from.
A cable, a tree, a manhole, a project, an inspection, a permit — each is an object with the same universal metadata (id, version, status, who made it, when) plus its own properties. Every property is itself first-class: it carries its value · unit · source · reliability · validity. Geometry is explicit too — point, line, polygon, mesh, volume, BIM and voxel all speak one language.
Tenant · Programme · Organisation · Team
Asset · Spatial · Temporary · Analysis
Document · Issue · Inspection · Task · Event · Calculation
Point · Line · Polygon · Mesh · Volume · BIM · Voxel
Between objects run typed edges: CROSSES · LOCATED_IN · PART_OF · FEEDS · ABOVE · APPROVED_BY. Together they form a graph you can walk — neighbours, traversal to any depth, the shortest path between two objects. A digital twin, in ORB, is exactly this: objects + relations + events.
Ask the graph which cable crosses which sewer, in which work area, under which project — where, what, what happens, and why.
The engine evaluates declarative rules over the network and materialises findings as issues. The spatial engine computes the geometry first — so the chain geometry → crossings → rules → conflict runs with no hand-drawn relations. Findings are idempotent: the same situation never doubles, and once it is resolved — a permit added, the cover raised — the issue simply disappears.
Add your own rule and it becomes part of the reasoning — the rulebook is data, not code, per country and per domain.
Beside the spatial rules runs one temporal core. It lays a time-axis under a place — a satellite archive back to 2015 — and tests the value series for real change with a statistical toets (Pettitt), rather than comparing two pictures. Watch-dossiers pin an area, a cadence and a fixed check and run it repeatably — honest about cloud and missing passes.
One core, many forms: the same historian surfaces as settlement in foundations, erosion on a coast, condition over an asset — a different product per domain.
Every create, update and delete writes an immutable event — who, what, when, the old value, the new value and the reason. The audit trail is produced by the workflow, not written after it. That is how a figure years from now still points back to where it came from.
Role-based and enforced: municipality, network operator, contractor, inspector, work planner, viewer — who may view, change, approve, export or close.
Runs client-side today; the same contract-API maps one-to-one onto a PostgreSQL / PostGIS backend later — without rebuilding the modules.
The kernel runs headless end to end — CRUD, metadata, audit trail, rights, relations, rules and export. 28 / 28 checks green, zero errors.
For each initiative the engine runs a growing set of versioned assessment modules across the relevant domains. Each returns not a bare number but a substantiated judgement — carrying its source, its standard, its margin and the investigation phase it belongs to. And where a norm cannot yet be met honestly, it reports a gap rather than an unfounded “pass”.
Every figure back to its source, standard and phase — gaps shown, not hidden. See the domains resolved on a real crossing: the HDD screening in Projects →
The Intelligence Engine is one face of a single platform — see how it fits together, or talk to us about your own ORB.
