Let’s think about the aesthetics of a vast network of connected assets and equipment, proactively communicating with your workforce. How overwhelming do you find a network of 1,323 trucks sending GPS, routing, dispatch, compliance, safety, billing and work order data over complex cellular and satellite networks, seamlessly and in real, or near real-time? How about monitoring the consumption rate, current levels and projected days-of-inventory for 872 fixed and mobile bulk tank sites, across different grades of petroleum and chemicals, in a six state area? Or the tracking of 723 trailers, of which 422 are refrigeration units needing to be monitored for quality, cold-chain assurance, chiller diagnostic information and logistic coordination?
Machine-to-machine SaaS (software as a service) providers should be able to seamlessly bring this information to you in a comprehensive and user-friendly solution. Forget manual data retrieval and the accompanying inaccuracies.
But what happens when one of those connected assets doesn’t ‘report in’? Can you ask your connected fork-lift to, “Call me back on a land line. You’re cutting in and out on me and you still need to give me your location and engine hours.”? Or “Can you hear me now, mobile generator 3? I was trying to run a diagnostic report and then schedule maintenance but you hung up on me.” Do you or your IT team really know how to speak back to this new workforce of connected assets and machines? Do you have the time and resources to become an expert?
With the myriad of software service providers out there, how do you evaluate which one is right for your business?
At its core, if something does go wrong, you shouldn’t be calling your software provider, they should be calling you. If they value your business, if they understand the costs of your operations, if they have made an effort to understand how this technology will ultimately transform the way you do things, and if they have designed their technology to deal with these important demands, then they will know that system and network downtime, bad devices, and ineffective, poorly developed software is not acceptable.
Until next time,
Alex

