AssetFirst
Asset identity and status for equipment that was never connected.
AssetFirst brings existing assets onto the platform with an identity, a location context and a status, without modifying the equipment itself.
Why it exists
Most industrial assets already in service were never designed to report anything. Their condition lives in spreadsheets, inspection rounds and individual memory.
- ·Assign a durable identity to physical assets
- ·Report status and context to the platform
- ·Integrate with existing site infrastructure
- ·Managed through the same registry and console
Attached to or wired alongside the asset being tracked.
Security- · Distinct device identity
- · Authenticated platform connection
- · Encrypted transport
- · Signed firmware images
- · Access-controlled remote sessions
How it fits the stack
Assets appear in the registry with history and audit alongside connected devices.
About SPIEngineHardware detail
Published values are confirmed. Anything hardware-dependent that has not been verified by engineering is marked rather than estimated.
- Device framework
- C3F
- Power
- Pending verification
- Enclosure
- Pending verification
- Operating temperature
- Pending verification
Highlighted entries are hardware-dependent values awaiting engineering confirmation. They are published only once verified — ask for the current datasheet during evaluation.
Where it is applied
Asset registers
Maintenance visibility
Utilisation tracking
Evaluating AssetFirst?
Ask for the current datasheet, lead time and integration detail. Anything not yet verified will be identified as such.