Typical use cases
- Creating the assets (a tank farm with tanks as sub-assets) so everyone can navigate to them with Google Maps
- Keeping the current work pack on each job page with real-time notification when it changes
- Scanning an asset's QR code for the history of past jobs, reports and who did them
- Tracking working-at-heights, confined-space and calibration documents with one-month expiry flags
- Grouping all shutdown jobs in a job group and reading statuses per asset
- Comparing shutdown performance, cost and time allocation in Power BI
The problem
A shutdown puts multiple teams, assets and jobs on one site at the same time with a hard deadline. The case study lists the recurring failures: nobody can find the asset, documents are re-sent endlessly, past reports are scattered, certificates and calibrations are unknown, jobs are not organised and performance is not measured.
How AMPS runs a shutdown
Create the assets first, for example a tank farm with five tanks as sub-assets, so everyone can navigate to them with Google Maps. Keep the work pack on each job page; updates notify everyone in real time and reports uploaded to the job inform supervisor, client and stakeholders instantly. Scan an asset’s QR code for its history: past jobs, who did them, how long they took, related documents. Track personnel and equipment documents on their page with the one-month expiry flag. Group the jobs in a job group and read statuses per asset.
Afterwards
All AMPS data is available to Power BI, which is how customers compare job or shutdown performance, costs and time allocation.