Typical use cases
- Pressure vessels, storage tanks, piping circuits and exchangers modelled as assets and sub-assets with a job history each
- API 510, API 570 and API 653 inspection intervals carried as due dates with a one-month advance flag
- Thickness readings, corrosion mapping and weld inspection reports produced from your own Word templates
- Technician certifications per method tracked against expiry so nobody is sent to site out of ticket
- Instrument calibration certificates held on the equipment page with the same expiry warning
- Turnaround and shutdown scopes grouped as job groups with status per asset
- Non-conformance records and their close-out held against the equipment they were raised on
- Cost, hours and completion rates pushed to Power BI for client and internal reporting
The record, not the reading
Taking a thickness reading is the easy part. Producing, two years later, the reading plus the report it went into, the technician’s Level II certificate valid on that date, the calibration certificate of the gauge and the close-out of the finding, is where inspection programs come apart. Oil and gas inspection is a record-keeping discipline that happens to involve instruments, and the codes are explicit about it: API 510, API 570 and API 653 all require the inspection to be documented, performed by qualified personnel, and the deficiency corrected before the equipment goes back into service.
AMPS is built around that record. The job, the report, the photos, the hours, the certificate that was valid on the day and the instrument that was in calibration are one object attached to one asset.
Modelling the plant
Assets nest as deep as the plant does. A site holds units; a unit holds vessels, exchangers and piping circuits; a tank farm holds tanks; a pipeline holds sections. General documents such as site induction and access instructions live on the site asset. Equipment-specific documents, the U-1 form, the last external inspection, the corrosion-rate history, live on the item itself.
Every asset gets a QR code. Scan the tag at the vessel and the asset page opens on a phone with every job ever done on it and every document the user is permitted to see, which removes the most common time sink on a plant: finding out what was done last time.
Inspections that announce themselves
Scheduled inspections carry a due date and the flag system raises them a month before they fall due. The same flag covers two things that cause more audit findings than late inspections: technician certifications that lapsed quietly, and instruments whose calibration certificate expired between jobs. All three appear on one flag list, so a supervisor planning next month’s work sees what is expiring alongside what is due.
Reports your client already accepts
Report templates in AMPS are your own Word documents. That matters more in oil and gas than anywhere else, because the client’s document control group has already approved a format and will reject a new one. AMPS fills the job data in automatically, PO number, client, equipment serial numbers, location, dates, lets a technician copy a previous report for repeat work and refill only what changed, offers an AI writing assistant for the narrative, takes the signature in AMPS and files the result in the job folder in your own cloud storage.
Because the template is yours, every method is covered: ultrasonic thickness, phased array, TOFD, radiography, magnetic particle, penetrant, eddy current, positive material identification and visual.
Turnarounds
A turnaround scope becomes a job group against the unit or the plant, with one job per asset. Status per asset is visible as the work runs, hours and costs accumulate against the group, and Power BI compares this turnaround to the last one on duration, cost and completion rate. The same structure works for a tank farm inspection campaign or an annual pipeline program.
Where AMPS stops
AMPS is not an EH&S suite and does not pretend to be. There is no incident reporting, no permit to work, no emissions module, and no remaining-life or fitness-for-service calculation. It is not an offline application. What it does is hold the inspection and integrity evidence in a form that survives an audit and a change of vendor, since the documents themselves are written into your own OneDrive, SharePoint or Google Drive rather than to AMPS servers.