To make sure overdue tests are tracked correctly, there are two key things to consider:
- Consistent Asset IDs – When an asset is retested, the same Asset ID needs to be used each time. This allows the system to recognise that the new test relates to an existing asset and update its test history correctly.
- Correct retest periods – Each asset needs to have the appropriate retest period configured. The system calculates the expected Next Test Date based on the asset’s most recent test date and its configured retest period. If the latest test is still within that period, the asset should not appear as overdue.
When importing data, if any assets that did not have a newer test date included, then those will remain overdue.
For assets that no longer need to be tracked, these can either be deleted or moved to another client, site or location as appropriate. Importing new test data will update existing assets where matching data is found, but it will not automatically remove assets that are already in the system.