One equipment record every other module points at.
The registry owns what an asset is and how it is organised. Maintenance, certification, reliability, projects and inventory all reference it by the same identifier instead of keeping their own copy.
What it does
A five-level classification taxonomy
Family → Class → Type → Model → Sub Type, for example rotating equipment → pump → centrifugal → multi-stage. Class binds the property schema; Model binds the FMEA file.
Property sets that differ by class
A separator carries orientation, weight, maximum working pressure and skid dimensions. A pump carries running-hours tracking. The schema extends as classes are created.
Identifiers on your own numbering scheme
The receiver enters the equipment id against the tenant’s scheme. The form shows the last id issued in that category and offers the next value, and a duplicate is rejected in the form as well as at the API.
Parent and child composition
Assets reference children by id, never by nesting, and an asset has a single parent. A separator references its turbine flow meters; a trailer references its mounted pumps.
Status and lifecycle held apart
The day-to-day operational state and the position in an asset’s service life are two different fields, because conflating them is how a fleet loses track of what is actually available.
Country and department dimensions
Every asset is stamped with an asset book (the country-wise grouping) and a business unit (the department-wise grouping within it).
Search and export
Search across the registry within your scope, and extract the equipment-list report when you hold the extract capability.
No ERP required
The registry is the system of record on its own, so nothing in it depends on an ERP being present. Syncing with Epicor iScala, SAP or another ERP on a tenant-defined match key is part of the committed model and is not yet on the shipped surface.
How it fits the rest of the platform
The registry is the hub. It publishes equipment identity and the taxonomy; maintenance opens job cards against it, certification attaches certificates to it, projects move it between packages, and reliability aggregates its events. Change the taxonomy and every downstream module follows, because none of them holds a second copy.
Questions about the registry
Do we have to adopt your equipment numbering?
No. Ids are entered against your own scheme; the registry enforces uniqueness and shows the last id issued in the category so the scheme stays consistent.
Does RelyentX need an ERP to work?
No. It is a standalone system of record and runs with no ERP at all. An optional two-way sync with iScala, SAP or another ERP is part of the committed model and is not yet on the shipped surface.
Can lifting gear be tracked here?
Yes. A sling is equipment of its own class in the registry, and it is certified through the same certification path as any other asset.
See it against your own equipment data.
A walkthrough on your asset classes, your certificate disciplines, your job cards, not a canned demo.