Platform overview
Every module. One equipment identity.
RelyentX is a multi-tenant EAM and CMMS for oilfield-services firms, equipment manufacturers and project operators. It is the system of record, and it runs with no ERP at all.
Core
Where the product is meant to win. Each of these has its own page.
Root, the AI assistant
An agent with real tools over your records, a scope it cannot widen, and an approval in front of every change.
ExploreAsset registry
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.
ExploreMaintenance & work orders
A job card is the unit of work. What makes it useful later is that the close date is stamped by the system, the repair duration is derived rather than typed, and the costs are captured on the card itself.
ExploreInspection & certification
This is the module that answers an auditor. It owns the certificates, the tests that produce them, and the daily signal that moves an asset from valid to expiring to expired.
ExploreReliability & analytics
This module holds no data of its own. Every figure is computed from the events that maintenance, certification and the registry record, which is why a number can always be walked back to the record that produced it.
ExploreSupporting and platform
Needed to run the business, described here rather than on pages of their own.
Projects, packages & mobilization
Projects contain packages, and a package is the location that holds equipment. Moving an asset between packages raises an equipment movement request, and editing a package’s membership raises the matching one, the two stay in step. A mobilization report shows what is where.
Inventory & spare parts
Valuation, economic order quantity and reorder point, computed on the Wilson formulae. Parts are classified by usage and tagged for criticality on a tenant-defined scale, and stock is issued behind an approval gate where the requester cannot be the approver. Swapping the formulae per tenant is planned and not available yet.
Knowledge & documents
Engineering specifications with an optional approval step, standard operating and maintenance procedures with publishing, a downloads registry for software and manuals, and attachments against equipment, job cards and certificates.
Workforce & competency
An employee directory with the personal record, held certifications, fit-to-work status and its restrictions, and training completion.
Supplier management
A supplier register with location, what each supplier is approved to supply, and the equipment and spare parts they have provided, moving through create, active and disqualified with a recorded reason.
Notifications & scheduling
A feed of overdue work, preventive maintenance due, certificates expiring and specifications awaiting approval, plus a schedule view grouped by business unit.
Tenancy, identity & access
Each tenant is created as one unit, with its own sign-in organisation, search index and equipment knowledge graph. People sign in once, hold an additive set of roles, and are scoped to the tenant’s own country, business unit, project and package layers.
Reports and search
A filter-driven report engine with Excel export (equipment list, certificate expiry, maintenance due, maintenance history, ready-to-go and mobilization), and one search box across every record.
The knowledge layer
Every entity is searchable, because every entity is ingested.
Every record is added to the tenant’s search index and equipment knowledge graph when it is written, and removed when it is deleted. What each person sees is filtered by their permissions and scope at the moment they ask, never by leaving data out. That is what lets Root answer across modules instead of only over documents.
ERP
Optional integration, never a dependency.
The legacy systems this product was modelled on pulled equipment and financial data from Epicor iScala and SAP. RelyentX runs standalone as the system of record, so no ERP is required and nothing in the core depends on one being present. Syncing with iScala, SAP or another ERP is planned and not available yet.
See it against your own equipment data.
A walkthrough on your asset classes, your certificate disciplines, your job cards, not a canned demo.