Manually set the last calibration date on assets
Completed
When adding a new asset to the system it might not be a brand new or recently calibrated asset. Therefore, it would be convenient if it was possible to change the last calibration date.
This might also be true for maintenance, running count, and/or total count. These values might be know for a particular asset and it would be useful to be able to set them for the asset.
-
Hi,
With the rest API you can use PUT api/Asset to create an asset and set lastCalibrationDate, lastMaintenanceDate, totalCount and runningCount to their initial values.
With the WATS Client API you can create an asset, and then call AssetHandler.Calibration and AssetHandler.Maintenance with the dateTime parameter set to the actual previous calibration/maintenance date. To set total count and running count to their correct values, first use AssetHandler.IncrementAssetUsageCount with the usageCount parameter set to 'actual total count' minus 'actual running count', then call AssetHandler.ResetRunningCount (only available in WATS Client 6.1 in beta now, releasing soon), and finally call AssetHandler.IncrementAssetUsageCount again with actual running count (increasing usage count increases both running count and total count, so to get it right initially requires some fiddling).
In the Asset Manager you can create an asset, but Last calibration date will be now. The Reset calibration/maintenance buttons don't let you specify the date the calibration or maintenance happened, so you can't get around it that way. Setting total count and running count can be done in the same manner as in the WATS Client API using the Increase count and Reset buttons under running count.
Is it in the Asset Manager you want to be able to do this?
Please sign in to leave a comment.
Comments
2 comments