EAM and CMMS for oil & gas
Know every asset you run.
RelyentX brings the equipment master, job cards, certification and reliability analytics into one system of record for oil & gas, in English and Arabic, with Root, an AI assistant that cites its sources.
See the one-month register pilot
Why RelyentX
A certificate, a job card and a reliability figure all point at the same piece of equipment, by the same id. So whether an asset is fit to run is answered in one place.
Platform
Every module your field operations run on.
One equipment identity across the registry, maintenance, certification, reliability, inventory, projects, people and suppliers.
Asset registry
The equipment master: a five-level taxonomy, class-specific property sets, parent and child composition, asset status and lifecycle.
ExploreMaintenance & work orders
Job cards in three work types, a system-stamped close date, derived MTTR, and the cost inputs that feed the analytics.
ExploreInspection & certification
Certificates by upload or generated in-app, a closed set of inspection disciplines, calibration against a traceable test device, model-level FMEA.
ExploreReliability & analytics
MTBF, MTTR, MTTF and availability per equipment type, backlog and overdue, cost Pareto and failure trend.
ExploreInventory & spare parts
Valuation, EOQ and economic reorder point on the Wilson formulae, usage classification, and issuing behind an approval gate.
ExploreProjects, people & suppliers
Projects and packages with equipment movement requests, an employee directory with certifications and fit-to-work, and a supplier register.
ExploreReliability
Reliability you can trace to the job card.
MTBF, MTTR, MTTF and availability per equipment type, with backlog, overdue work, cost Pareto and failure trend, computed from the job cards your teams close. Correct a close date and every figure that depended on it moves with it.
Root, the AI assistant
Root cites its sources.
Ask in plain language. It searches your own records and equipment knowledge graph, shows the records it drew on, and can only act inside your scope.
Nothing runs without approval
It proposes only actions your role allows, and nothing changes until you approve each one.
You approve every action
It proposes from a fixed allow-list. Nothing runs until you approve that specific action.
One set of rules
An approved action goes through the same permission-checked path the dashboard uses.
Drafts, not authority
Answers, extracts and checklists download as documents built from your own records, always as a draft for review.
Why did P-1042-A fail twice this quarter?
Built for oil & gas
It already knows what a separator is.
The taxonomy, the property sets and the inspection disciplines are the ones a rotating-equipment and pressure-vessel fleet actually uses.
Five-level classification
Family → Class → Type → Model → Sub Type. Class binds the property schema; Model binds the FMEA.
Class-specific properties
A separator carries orientation, weight, maximum working pressure and skid dimensions. A pump carries running-hours tracking.
The disciplines you certify against
Hydro test, load test, MPI, UTI, visual, SRV calibration and thickness, one closed set, validated when a certificate is entered rather than left as free text.
Certificates produced in-app
Calibration certificates are generated from entered readings against a traceable master test device, on a fixed nine-point DKD-9 scheme or a custom one.
Security
Isolated by design, plain about the AI.
The questions an operations lead asks before a pilot, answered on one page.
Tenant isolation
Each tenant gets its own sign-in organisation, search index and knowledge graph, and the database enforces isolation on every row.
Roles checked on the server
People sign in once and hold an additive set of roles, checked on the server rather than hidden in the interface.
Bilingual, both directions
English and Arabic are first-class, with a full right-to-left layout and an Arabic type face, not a translated overlay.
Where the AI runs
Three AI features run at third-party providers, and each receives your data. To make records searchable, the text of every record and document is sent as it is written. To read documents, the page images and extracted text of a certificate imported from a chat, and the page images of a chat file our own text extraction could not read, are sent, up to a daily limit per workspace. The page images and extracted text of other scans our own extraction is not confident about, such as a file saved to a record, are sent only in a workspace where reading has been switched on, and it is off by default. To answer a question to Root, the question, the records retrieved for it and the text of any file attached to the chat are sent. Root answers and document reading are routed only to providers whose published policy is not to train on the request; the search-indexing provider states it never trains on API data. How long each provider keeps a request follows its own terms. This processing is not limited to where the platform is hosted. We name each provider in writing in the security review.
See it against your own equipment data.
A walkthrough on your asset classes, your certificate disciplines, your job cards, not a canned demo.