Product · Register

One register. Every difference owned.

Tags, SCADA points, historian assets and maintenance locations reconciled from exports after a merger or a handover. Every difference valued and owned. The point-and-alarm review the inspector asks for, as a signed pack.

In designDesigned from existing building blocks. Not built.
1

Matches tags, points, assets, locations

2

Differences valued: safety, compliance, money

3

Signed pack for the point review

Needs

  • Register exports: points, tags, assets, locations
  • The written alarm plan
  • Valuation rules agreed per site

Is not

  • Not an asset-information system
  • Not a migration project
  • No OT connection
Where it stops
Enters as a service after a merger or a handover. The recurring value is the annual review, as receipts.

Built from

What exists, what does not
The post-merger reconciliation (telecom harness, separate codebase): two networks, one register, a request prefilled from a merger row. The typed adapter bridge with recordings round-trip and conformance suites (prototype). The request model for owners and clocks; signed receipts. Not built: loaders for handover templates, historian asset frames, maintenance functional locations and SCADA point exports; oil and gas valuation rules.

First proof

The experiment
Reconcile two public registers of the same assets already loaded in the spatial layer (a licence register against a GIS pipeline register) plus a synthetic tag list and maintenance export, with the existing engine; publish every difference, valued and owned, as a signed pack. Then one operator's SCADA point export against its written alarm plan, read-only: exactly the review the regulator asks for.
Also
Register — One register. Every difference owned. · OOH