You can use Current RMS to record test and inspection results for your assets – great for things like PAT, Test and Tag, and LOLER.
Get an overview: How does testing and inspection work in Current RMS?
When you allocate, prep, or book out an asset that should be inspected on an opportunity, Current RMS will check to make sure that the asset:
- has passed any inspections.
- is not due an inspection during or before the end of the opportunity.
If the asset hasn’t passed or its inspection expires before the end date of the opportunity, Current will either prevent you from taking that action, or warn you.
From the warning, you may hop into a test and record the result directly from the opportunity page. We’ve designed it for companies who have electronic testers in the warehouse, so it’s easy to quickly test something as you’re prepping.
Where an asset is overdue an inspection that’s mandatory, Current will prevent you from allocating, prepping, or booking out that asset.
Use the Inspect now button to launch the “Inspection Result” popup and test the asset straight from the opportunity. Once inspected, it will be allocated, prepped
The fields here mirror those that you’d find when completing a test in Resources > Testing & Inspections. Check out: See upcoming asset tests and start testing
Where an asset is overdue an inspection that isn’t mandatory, Current will allocate, prep, or book out the asset but warn you to let you know.
As with mandatory inspections, you may use the Inspect now button to test the asset there and then.
Where do I choose whether my inspection is mandatory or not?
You can set this when you create your inspections. Head to System Setup > Inspections to check which of your inspections are mandatory. You may edit your inspections here, too.
What happens when I auto-allocate?
With auto-allocate, Current RMS can check to see which assets are available and allocate them to the opportunity for you – all you need to do is go find those assets and start prepping.
Where an asset is due a mandatory inspection before the end of the opportunity, we won’t allocate it as part of auto-allocation.
How does it work for serialized containers?
We don’t check to see if container components are overdue a check when taking actions on the opportunity. What do you think about this? Would you rather we checked container components? Let us know using the green help bubble ↘️