Skip to content

TwinEdge / Operations Intelligence · The asset registerOperations Intelligence

The asset register

Start with an asset everyone recognizes.

Give equipment one identity across hierarchy, location, measurements, documents, and maintenance history.

Request a demoAsset life

From source to shared context01 / SYSTEM VIEW
EquipmentHistoryDocuments
TwinEdgeShared asset context
Digital twinsAI agentsApps + APIs
01Connect02Map03Model04Publish
One asset model, reused across every consuming workflow.
Six levels, from the company to the sensor
LevelFor example
CompanyAcme Water
SiteManila treatment works 3
BuildingPump house B
SystemRaw water intake
MachinePump P-201A
SensorBearing vibration, drive end

§ 01

Why six levels, and not a flat list.

A flat list of equipment cannot answer the questions people actually ask. Which site is worst? Is it the pump or the system it sits in? If this intake goes down, what stops?

Structure answers those without anyone building a report. It also means a setting made once at the top — who maintains this, which rules apply, what time zone it is in — reaches every machine beneath it.

The sensor is part of the structure, not an afterthought. A vibration reading belongs to a bearing, which belongs to a pump, which belongs to an intake. That chain is what turns a number into something a person can act on.

§ 02

What makes it bearable to keep up to date.

A register is only useful if it stays true. Everything below exists to reduce the amount of typing between reality and the record.

  • 01Load hundreds at once

    Upload a spreadsheet and provision a whole site in one go. Check it first: the system shows exactly what it would create before anything is saved.

  • 02Start from a known machine

    Ready-made setups for pumps, chillers, compressors, generators, and more. Copy one, change what is different, and move on.

  • 03Set it once, high up

    Time zone, the crew responsible, and which rules apply are set at the site and inherited by everything beneath it. You do not set them a thousand times.

  • 04Forty kinds of equipment, already understood

    Each type arrives knowing which sensors it should have, what its alarm limits usually are, and which physics applies to it.

  • 05Add your own fields

    Anything you already track — a cost centre, a permit number, a contract — can hang off any record, and you can search and report on it everywhere.

  • 06One company cannot see another

    Separation is enforced in the database, not in the screen. Larger customers get their own database entirely.

Bring a spreadsheet of your equipment.

Whatever list you have today, however untidy, we will load it, show you what it would create, and let you see your own site in the structure before anything is committed.

Request a demoAdding equipment in the field