Universal Precision Instrument Interface

One ingress. Every precision instrument.

The Universal Precision Instrument Interface — single ingress, sovereign deployment.

Spectrometers, PLCs, calipers, OCR scanners, cameras, balances, particle counters, environmental sensors — one ingress. Driver-pluggable adapters, binary-safe transport, JSON projection for the LLM, raw frame preserved in storage. Data sovereignty never leaves customer deployment.

Seven adapter protocols, one terminating ingress. The substrate that ingests a polytunnel camera also ingests a 5-axis CNC. Cross-industry by construction, not by integration.

  • 7 protocols
  • Binary-safe ingest
  • Per-instrument crypto identity
  • Twin entity store
  • Sovereign deployment
06.0 Live scene

Three industries, one ingress.

Switch the tab. The substrate underneath does not change. Hover any number to see what NEXUPIRA does at that point in the chain.

06.05 Before / After · What changes when NEXUPIRA plugs in

What you stop doing.

The 3D scenes show what your shop floor looks like today. These cards show what changes the moment NEXUPIRA enters the loop.

Lab spectrometer
Today
With NEXUPIRA
Operator hand-reads CSV / printed report
Spectral data piped straight to the LLM
Anomalies wait for shift handover
Anomalies push to Slack / LINE in real time
Results stuck on local PC, no cross-shift trail
Every run lands in the audit log, replayable
PCB inspection
Today
With NEXUPIRA
Hard-coded thresholds miss new defect classes
YOLO + Vision LLM cross-validation
High false-positive rate, manual re-check
Confidence < 0.8 → human review queue
Defect images archived but never analysed
Auto-feedback loop, model updates weekly
CNC process
Today
With NEXUPIRA
PLC anomalies buried in raw logs
Anomaly → Workflow Engine fires a ticket
Tool change by operator gut feel
Wear trend predicted, change scheduled
Yield drop investigated after the fact
Causal chain intact, root run identified
Time-series log
Today
With NEXUPIRA
Operator stares at multi-channel dashboard
AI continuously compares against historical windows
Anomalies drowned in channel noise
Anomalies auto-flagged with confidence score
Tickets opened by phone / email
MCP → CMMS, ticket fires within seconds
06.1 Protocols · Seven adapter slots

Seven protocols. One spine.

Each protocol has its own adapter, but they all terminate at the same ingress. The ingress writes binary frames to long-term storage, pushes JSON projections to the chat engine, and emits anomaly events to the Event Bus.

01 Modbus

Modbus

TCP / RTU

PLCs · drives · power meters

02 OPC-UA

OPC-UA

binary · TLS

industrial controllers · SCADA

03 MQTT

MQTT

pub/sub · QoS 2

IoT sensors · edge devices

04 REST

REST

HTTPS · JSON

cloud-bridged instruments

05 gRPC

gRPC

HTTP/2 · protobuf

high-throughput streams

06 Serial

Serial

RS-232 / RS-485

calipers · balances · spectrometers

07 USB-HID

USB-HID

HID profile

OCR scanners · readers · particle counters

06.2 Principles · UPII contract · v1

Six principles. Non-negotiable.

These six are patent-claim-level design contracts. Any ingress behaviour that breaks them is a bug, not a feature.

01

Driver-pluggable

One adapter per protocol, schema negotiated on first contact. Plug a new instrument → ingress queries its capability → registers it.

02

Binary-safe

Native frame preserved in storage. The LLM sees a JSON projection — not the frame itself. Same data, two views.

03

Sovereign

Ingress + storage + inference + decision + egress all inside customer deployment. No third-party cloud hops.

04

Crypto identity

One key pair per device. Telemetry signed. Replay-resistant nonce. Audit log pinned to device ID.

05

Zero-trust

Default deny. TLS / mTLS. Per-frame audit log. Any ingress request is replayable, traceable, and verifiable.

06

Versioned

Schema negotiated on first contact, then versioned. Device firmware change → previous data never breaks.

06.3 Ingress flow · Frame → projection → action

One payload, two views.

Binary frame stays for long-term store and replay. JSON projection feeds the LLM for inference. Downstream Workflow Engine consumes both — the LLM writes the condition, the binary supplies the evidence.

NO CLOUD HOPS

Adapter → ingress → twin entity → Event Bus → workflow → audit log. All inside customer deployment. Sovereignty is not a feature flag.

BINARY-SAFE

Original frame is the audit truth. JSON projection is the LLM's view. They never disagree because they're produced from the same signed source.

PER-INSTRUMENT KEY

Each device gets a key pair. Telemetry signed. replay_nonce rejects duplicates. Cryptographic identity, not just IP allowlist.

06.4 Chains · Industrial integration matrix

One Event Bus. Three industrial chains.

Every chain runs on the same Workflow Engine. There is no dedicated "QA system" or "process system" or "lab system" — only DAGs that differ in trigger and steps.

Inspection
OCR scanner
Quality gate fail
Procurement order
Supplier ticket
Process
PLC anomaly
DT state deviation
Workflow inference
Operator notify
Lab
Spectrometer reading
Compute timeseries
Threshold breach
Audit + alert

Plug your instrument. The substrate is ready.

Bring the spectrometer. Bring the PLC. Bring the lab balance. The ingress doesn't care about the brand.