A manufacturing assembly rising from a dark field, solid at the left and wireframe at the right, with one red utility route running through it
V/N

Visual Normality · SyntaGraph

One object. Every scale around it.

Follow a single vial from the component to the campus, and the evidence that keeps its context connected at every scale.

or scroll to explore

The problem

Physical operations have no shortage of data.

The problem

The problem is knowing which of it is true, current and connected to the rest.

01 Component

Start with one object.

One vial, drawn at real scale. The drawing, the specification, the scan and the field observation each describe it a little differently.

01 Component

Every fact should know where it came from.

SyntaGraph reconciles drawings, documents, scans and field observation into grounded context for the object. When the sources agree, the object is confirmed.

02 Asset

Context gives the object meaning.

The vial enters a decontamination module. Geometry alone is not context.

02 Asset

One object becomes part of an asset.

SyntaGraph connects what something is, where it is, what it depends on and the evidence behind each of those facts.

03 Line

Context becomes a system.

Decontamination, inspection, cartoning and serialisation. Machines do not operate in isolation.

03 Line

The line is a network of physical and engineering dependencies.

SyntaGraph makes those relationships queryable.

03 Line

The graph is the context. The 3D world is one view of it.

The evidence layer can feed the visualisation environment a site already uses.

04 Area

Decisions happen in space.

The line stands in a bay with its air supply, its extract, its service zone and its material route.

04 Area

Design intent is not always physical reality.

A scan over the design finds one duct where it was built, and the model is corrected to what was found.

04 Area

If this containment enclosure changes, what else is affected?

Change one thing and the consequences rarely stop there. SyntaGraph gives engineering teams the context to understand those consequences.

05 Building

Changes propagate.

A line is part of a building, and a building is another connected system.

05 Building

Engineering decisions cross room boundaries and disciplines.

Each layer of evidence is kept apart and can be shown on its own.

06 Campus

From one object to the physical enterprise.

The bay stays locatable, the line stays connected and the vial keeps its lineage.

06 Campus

Take the world away and the context remains.

SyntaGraph is the context underneath the visualisation. The 3D scene is one way to look at it.

Visual Normality · SyntaGraph

From component to campus, one evidence-backed context layer.

Visual Normality gives engineers a trustworthy model of physical reality, so they can understand it and change it, and so intelligence can later be built on it. In time, the same grounded context can become the substrate for engineering agents and increasingly autonomous physical systems.

Bring us the question. We build the evidence required to answer it.

We do the engineering work a plant buys across its life, starting at the front end.

Feasibility, pre-tender baselines, handover verification, change-control assessments, turnaround readiness and due diligence. Each study starts from a model of the site that our engineers build from the drawings, scans, photographs and records the site already holds, reconciled against what they find on the walk.

Where the drawing and the plant disagree, the study says so before the tender goes out. Design on the verified plant is the next rung. Today the deliverables are studies, registers and verdicts, and the site's engineer of record signs them.

The plant you can ask what happens if.

Every study starts from the site as evidenced. The same site can be asked what a change does to the air, the heat and the utilities around it: whether the new line creates a hotspot in the bay, whether the extract holds the pressure cascade, whether the utility headroom is really there.

Each boundary condition points to its evidence, and each result is labelled screened, verified, measured or signed. What your product does inside the machine stays with your process engineer, and the study says so.

How the physics layer works

This capability is being built into SyntaGraph. Until it exists, a proposal states which questions are answered by declared hand calculation and which are Not Demonstrated.

Three engraved plates stacked on steel pins, the middle one red, each carrying a different drawing of the same site

One bay, drawn by code to show the method. The session is scripted and shows no real result.

SyntaGraph · Bay 4

The record outlives the project.

A verdict keeps its evidence, its conditions and the approval that followed. The discrepancy register from a handover check is the one the site would otherwise carry for years. Every later question on that site starts from the record, which is why the second study costs less than the first.

  1. ObservedPhysical state
  2. AttachedEvidence
  3. FoundConstraints
  4. SignedThe engineer's decision
  5. DoneAction
  6. MeasuredOutcome

When the evidence cannot carry a conclusion, the verdict says Not Demonstrated and names the evidence that would close it. We price and deliver that answer like any other.

Tell us about the project.

Written for project engineers and project managers with a line, a building or a placement in front of them, for supply chain and site leads with a capacity question, and for AI teams that need a harder physical test.