Is this asset in date, and can you prove it?
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.
What it does
A closed set of disciplines
Hydro test, load test, MPI, UTI, visual, SRV calibration and thickness, one closed set, validated when a certificate is entered, so the discipline on a certificate is never free text a reader has to interpret. Binding a specific discipline set to each equipment class is part of the committed model and is not yet on the shipped surface.
Upload an existing certificate, or generate one
Third-party certificates are uploaded and recorded against the asset. Calibration certificates are produced in the application from the readings you enter.
Calibration with traceability
Reading parameters, SRV set pressure, and DKD-9 or custom inspection points, referenced to a master test device, with a warning if that device’s own certificate had expired on the test date.
One certificate across several assets
A single certificate record can cover multiple pieces of equipment, each carrying its own expiry.
Acceptance forms, e-signed
The tenant admin authors the yes / no / remarks question set. On receipt the responsible manager completes and signs it, and the PDF is stored in the equipment’s attachments.
FMEA at the Model level
Failure modes are held against the equipment Model with a computed risk priority number, so they are shared by every asset of that model rather than re-entered per asset.
Expiry that finds you
A daily scheduled job moves each asset’s certification through valid, expiring and expired and emits the signal, which surfaces in the notifications feed and the certificate-expiry report.
History and downloads
The equipment page shows certification history with a per-row download, and a certificate summary that rolls up the due dates of child assets.
How it fits the rest of the platform
Certificates hang off equipment identity published by the asset registry, and each one records its discipline from the closed set. Expiry events feed notifications and the readiness view used when mobilising a package. Certificate creation lives on the job card, so the paperwork is raised where the work happened.
Questions about certification
Can RelyentX produce a certificate, or only store one?
Both. Third-party certificates are uploaded; calibration certificates and acceptance forms are generated in the application as PDFs.
What happens when a certificate is about to expire?
A daily job moves it to expiring and then expired, and emits a signal that appears in the notifications feed and the certificate-expiry report.
Is vessel thickness surveying included?
Thickness is one of the closed set of disciplines. Inspection points are recorded on the calibration itself, on a DKD-9 or custom scheme, rather than templated per equipment class. Recording a full survey with deltas against previous readings is part of the committed model and is not yet on the shipped surface.
See it against your own equipment data.
A walkthrough on your asset classes, your certificate disciplines, your job cards, not a canned demo.