← Back to Product Nexus
Asset Nexus

Product Nexus · Asset Nexus

The register is wrong. Nobody knows by how much.

A camera-verified asset management system for highway concessions and road authorities.

01 · The Problem

Registers drift. Quietly, and from day one.

  • Nobody reports the small stuff. A contractor replaces a hit sign and tells no one — none of it reaches the register.
  • Inspection is sampled. Walking a corridor is expensive, so it happens rarely and partially.
  • The gap is invisible. A wrong register looks exactly like a right one — until it matters.
Asset Register
Guardrail — KM 12.4Verified
Sign Post — KM 14.0Verified
Culvert — KM 15.8Not on record
Streetlight — KM 16.2Verified
Guardrail — KM 18.6Condition unknown
02 · What It Costs

You cannot defend a budget built on a register nobody has checked.

  • At audit: a concession return is a statement to a regulator — if the count is a guess, so is the statement.
  • At renewal: replacement forecasts multiply a count by a rate, and the count is usually the weaker of the two.
  • At claim: a dated photograph beats a spreadsheet row when a contractor disputes an installation.
  • At acquisition: buying a corridor means inheriting its register sight-unseen — a survey prices what you're actually buying.
Where Unverified Registers Bite
AuditA guessed count makes the whole regulatory statement a guess.
RenewalReplacement forecasts are only as good as the count behind them.
ClaimA dated photograph beats a spreadsheet row in a dispute.
AcquisitionA pre-deal survey prices what you're actually buying.
03 · What We Do

Drive the corridor. Compare it with the register. Show the evidence.

A camera never edits the register. It produces evidence; a person makes the decision.

The Loop
1
Capture

A forward-facing camera records the drive — faces and plates blurred before anything leaves the vehicle.

2
Detect

Objects found across consecutive frames and triangulated to a position, not guessed from one bearing.

3
Reconcile

Matched to the register by position and class, correcting for the survey's own systematic error.

4
Decide

A person accepts or rejects. Only then does the register change — and their name is on it.

04 · Evidence

Every finding carries the frame it came from.

  • Position, class, and a confidence score.
  • The model that produced it.
  • The reviewer who agreed, and when.
  • That's a chain of custody, not a row in a table.
Finding #4471
PositionKM 15.8, RHS
ClassCulvert
Confidence91.4%
Model IDan-detect-v4.2
ReviewerS. Kulkarni
Timestamp2026-08-14 09:12
05 · Why Us

The unusual claim: it tells you when it does not know.

  • Reports unpriced as unpriced — never silently treated as zero.
  • Raises a weak match as "needs a human" instead of resolving it silently.
  • Flags a badly configured survey as suspect, rather than trusting it.
  • Keeps the observation, the conclusion, and the decision as three separate, permanent records.
What Most Systems Do vs Asset Nexus
Most systemsAsset Nexus
Unpriced assetTreated as zeroReported as unpriced
Weak matchResolved silentlyFlagged — needs a human
Detection, conclusion, recordCollapsed into one rowKept as 3 permanent records

06 · The Whole Loop

Not just an inventory

  • ✓Work management — findings become work orders, dispatched by WhatsApp/SMS
  • ✓Planned maintenance — cyclic regimes measured against the plan
  • ✓Forecasting — ageing curves and urgency-based budget planning
  • ✓Compliance — periodic returns, second-person checked, archived
  • ✓Governance — approval thresholds, four-eyes review, full audit trail
  • ✓Documents — as-builts, manuals, certificates, and warranties
07 · Integrations

Speaks to the ERP you already run — SAP or otherwise.

Work orders sync out, status comes back — Asset Nexus stays the system of record for its own approval and completion, so the integration is informational, not a second brain.

  • SAP (OData): a live connector against plant maintenance orders and notifications.
  • Generic webhook: any ERP or CMMS with an HTTP endpoint — Maximo, Oracle, a homegrown system.
  • File exchange: no API? A scheduled CSV or Excel drop does the same job.
Connected Systems
SAP (OData) Generic Webhook CSV / Excel Scheduled Sync Field Mapping

08 · Getting Started

One video survey is enough to start

Step One

Drive one corridor with a forward-facing camera. Upload the video and GPS log through the browser.

Step Two

Compare the result with the existing register. The gap is usually the whole business case.

Then

Add corridors, crews, and a maintenance regime. Move to a calibrated rig when volume justifies it.

Hosted, on-premise, or air-gapped. Licensing verifies offline against a signed key, so a disconnected installation is a supported deployment rather than a redesign.

Give us one corridor and couple of weeks.

One video survey, against a register you already have. The number that comes back is the conversation.

Ask for

One corridor, one nominated engineer, a few hours of their time.

You provide

The pilot deployment, the capture setup, and the reconciliation.

They get

A verified count of that corridor, with photographs, and a real story to work on.

Talk to Us