Digital twin

Build the world. Bring the data to life.

Combine open mapping and terrain with private scans and engineering models to build a 3D world twin. Tessara connects that spatial foundation to your governed records, so you can see the operation, explore it with Tessara Assistant and test a modelled decision before you make it. Follow one scenario, Harbour Watch, from the moment a vessel's track lands to the moment an operator decides what to do about it. Every object still carries its provenance; every view is still bound by the caller's clearance.

Rendered inside the enclave — the picture never leaves your perimeter
The model

Harbour Watch, as a site model.

A 3D model of the terminal with the live data in place.

Drag to pan, right-drag to orbit, scroll to zoom. P for plan view, Home to frame the terminal. The scenario plays on its own until you take the controls.

01 · Live operational picture

Kestrel comes up the channel — and the picture draws itself.

Watch the picture update as new information arrives.

Her AIS track lands record by record and the twin draws it: up the approach channel, past the anchorage where Aldora waits, towards Berth 12. The berths, the inspection shed, customs and the Berth 12 sensors are all governed objects in their real places. Nobody is querying a table; the operation is simply visible.

Positions, tracks and dwell drawn straight from fused feeds — AIS, port systems, sensor, manifest
Every marker resolves back to the object, its links and its lineage — Kestrel to TXN-88412 to Okafor
Rendered inside the enclave — the picture never leaves your perimeter
Show me in the model →
MV KESTREL · INBOUND MV ALDORA · ANCHORAGE BERTH 10 BERTH 12 BERTH 14 INSPECTION SHED CUSTOMS SENSOR APPROACH CHANNEL
02 · Spatial twin

The terminal as a model — with the data standing on it.

Every berth, building and sensor is a real record you can open.

Berths, yard blocks, the inspection shed and the gate as governed objects with geometry. Kestrel's assigned berth is lit; so is the yard slot her consignment is booked into. Crane moves, gate transactions and sensor events rise from the places they happen — so the question becomes what is happening at Berth 12, not what is in the table.

Sites, assets and zones as ontology objects with geometry — the estate is part of the model
Live readings and events surface at their physical location, with lineage back to the feed
Same access policy — you see the parts of the terminal you're cleared to see
Show me in the model →
03 · Scenario & what-if

What if we hold Kestrel at anchor?

Test a decision and see its consequences before you make it.

Because every object is linked, the decision is never local. Propose it against a versioned snapshot and watch the consequences travel: Berth 12 frees, so Aldora comes forward. TXN-88412 is held, so Okafor's collection slot is cancelled and Meridex's haulage booking is void. Customs is dispatched and Berth 14's sensor coverage is raised. Nothing has been written — yet you can already see what the decision costs and who it touches.

Propose a change against a versioned snapshot — nothing is written
Downstream objects light up as the change reaches them along their links
Commit as a governed action, with the modelled outcome in the audit trail
Show me in the model →
MV KESTREL BERTH 12 MV ALDORA TXN-88412 D. OKAFOR MERIDEX LTD CUSTOMS ▪ HOLD AT ANCHOR · WHAT IF?
04 · Build the world twin

Open context. Private detail. One site frame.

Public map data and your own private data, combined in one view.

No single source describes the whole site. Open mapping supplies buildings, roads and wider context; national LiDAR supplies terrain and surface heights. Private LiDAR scans and photogrammetry add surveyed detail. CAD drawings and IFC/BIM models contribute engineering geometry, spaces and levels. Align the inputs to a common coordinate frame, then bind the resulting places and assets to the operational data they represent.

Start with OS OpenMap Local and Environment Agency LiDAR where coverage is available
Add private scans, captured meshes and IFC/BIM; CAD drawings may need tracing or conversion before import
Prepare geometry in Site Builder, validate its provenance and permitted use, then import the package through the Airlock
From sources to a shared world

Keep the evidence behind the geometry.

Every part of the 3D model keeps a record of where it came from.

A building footprint, a measured height and a design drawing tell different stories. Keep their origins visible as you combine them. Where detail is missing, use declared fallbacks; where a survey and a design differ, review the alignment rather than treating the model as measured truth.

Open-source data and private inputs are selected for the site and checked for permitted use. The connected-side builder prepares the package; Tessara imports the validated result and renders the operational picture locally.

05 · Tessara Assistant

Talk to the data. Navigate the world.

Ask questions in plain English and move around the site by asking.

Tessara Assistant runs completely air-gapped in your environment. Ask it to find a dataset, explain its fields, inspect permitted records or focus the 3D viewer on an existing site entity. Show and hide layers, explore available history, and inspect the configured flows that connect the operation.

With explicit site-change permission, it can update supported entity states, tags and attributes, configure data bindings and modelled flows, or fork an existing what-if draft. Validation and preview tools do the checking and calculation; the assistant reports their outcomes and source references.

Tessara Assistant, bounded tools and the operator's existing access controls
Read-only by default; supported edits carry a reason and a before-and-after receipt
What-if previews are simulated and unqualified; drafting does not publish or operate equipment
Explore Tessara Assistant →
06 · The model under the picture

Everything in the twin is an object you can question.

Behind every shape in the twin is a record you can inspect.

Kestrel, Berth 12, the inspection shed and CNT-4471 aren't drawings; they're governed objects in Tessara's model, mapped from your source systems, traced to the row they came from and kept through time. The twin is one view of that model. See how it's built.

Explore the data model →
Object · VesselMV KESTREL
LINKSBerth 12 · CNT-4471 · PC-2026-1187
ETA14:20 · eta-reconcile v1.8.2
SOURCEBerth schedule · row 812
HISTORY6 states in last 24 h

See it on your operation

Harbour Watch is our scenario; the twin runs on yours. Bring your open data, private surveys and engineering models. See how a shared 3D world, Tessara Assistant and checked scenario previews could support your operation.

Get a demo