Get Premium for free!
8 months ago
VSS migrated their CAT Fleet Summary API from Current Gen to Next Gen
AMP team found that AMP was processing data at a delayed pace
AMP team sent an email saying that Harvester was providing a larger amount of data than normal. * Also it was mentioned that FleetSummary API was suspicious in having more assets without Telematics data blocks.
Kiewit had already raised tickets w.r.t delayed data visibility
Kiewit raised tickets and reached out directly to us saying that all their Assets were showing Source as VisionLink
VSS had found the Root Cause of the issue - CAT FleetSummary API in Next Gen space was looping back all the assets that were posted to by AMP.
VSS fixed the issue on their Next Gen feed so that Telematics data wasn't looping back into AMP for all Non CAT assets
It was around 26 hours after the fix was done, AMP was able to process the right data coming in from CAT Fleet Summary.By the time, the fix was done, all of 10K odd assets reporting assets had their ELP data screwed. AMP team put in a Partial fix for assets - assets which did not have a 2nd Telematics device fitted on them were getting proper data into AMP.
Kiewit raised tickets and reached out directly to us saying that some of the assets were still not getting data from external feeds while the external feeds were working fine.
AMP team did a complete fix of the screwed up ELP data which fixed all the assets once for all.
Kiewit raised tickets and reached out directly to us saying that they still had issues with 70 odd assets - but they were only CAT assets.
VSS validated that there was an issue with Master data Asset provisioning in Next Gen space. In NG space for these 70 assets (and 230+ assets), there were duplicate entries. AMP was sending a MAKE CODE that wasn't matching with their legacy MAKE CODES.
It was decided to rollback the CAT Fleet Summary API to Current Gen endpoint. Revert was completed by Harvester team.
AMP team raised concerns about other CAT feeds (Diagnostics, Events and Engine Parameters) also having issues w.r.t CAT assets.
VSS team said that reverting these Bookmark based feeds will not work. Instead, they mapped the right AssetUID with the Subscriptions and the feeds started to work fine again for the 70 odd reporting CAT assets.
VSS team has provided the valid MAKE CODE and AssetUID for the 239 Stopped reporting assets that had the master data issue to AMP team. AMP team is supposed to Delete the existing Subscriptions for these and create AssetDevice Mapping and create Subscriptions with the new AssetUIDs.
AMP team has completed the fix for 230 odd assets.
Issue to end customer (Kiewit)
Share on Google+
Share on Facebook
Submit to Reddit
Share on LinkedIn
Post to Tumblr