Geotab in Ontario offers their fleet management system, consisting of MyGeotab cloud platform for managing driver and vehicle information, driver tracking and route optimization, as well as driver and vehicle efficiency (e.g. fueling, maintenance, MPG benchmarking) analysis capabilities for cost-control and fleet expansion. Additionally, Geotab offers GO8, a hardware tracking device that integrates with the platform.
N/A
ServiceMax
Score 7.9 out of 10
N/A
ServiceMax’s mission is to help customers with asset-centric field service management software. ServiceMax’s mobile apps and cloud-based software provide an overview of assets to field service teams. By optimizing field service operations, customers across all industries can better manage the complexities of service, support faster growth and run more profitable, outcome-centric businesses.
Geotab is a good product. I think ultimately it falls short in the clunky-ness of the program. If you are not intending to have users utilize the website and instead are going to feed data into a BI tool I think it would be a great product. I think if you are aiming to have the website utilized by your users and are looking for a one-stop-shop to drive your end-users to for reporting and data and are aiming to manage the program out of the program itself—I would not recommend it. I think the UI and UX clunky-ness is a hindrance and will lead to a lot of training because the learning curve is so steep. If you have a large Training team owning this and can swing that, it would be fine. However, if you are scrappy and looking for minimal need to train and re-train and want something intuitive and with a low learning curve, this is not it.
Small deployments, where you have some specific need for ServiceMax and absolutely need offline capabilities, and are willing to deal with the problems. Otherwise, you may be better off looking at the built-in Work Orders and field service module that Salesforce is now providing. Their app is direct competition for ServiceMax and integrates much better with cases and knowledge articles.
I think ultimately the product itself is good, however, the other competitors in the space have much better UIs and they almost all seem more intuitive. The reporting is easier to create and not just based in Excel and they feel more developed. I think that if Geotab were to focus on their UI and UX and really develop it more, there would be a significant bump in customer satisfaction for Geotab and they would be a huge force in the enterprise space.
ServiceMax has an offline capability, and also integrates with our Salesforce side of business. At the time, Salesforce did not have a field service application so we could not consider it, but if we could now, we would probably go with that instead. ServiceMax is also expensive. But at the time, ServiceMax was the only offering out there that integrated with Salesforce, had mobile offline capability, and could operate at the scale we needed.
Tracking has allowed us to recover assets from exited employees saving us about $500k.
While we could have had a dent in our fuel costs from idling or speeding some of the mechanisms used in the system haven't allowed that to come to fruition.
ROI for ServiceMax is mostly dependent on how in depth the organization wants the software. Our ROI is expected within the second year of operation due to the complexity of integration and the initial training requirements for in-house programmers.
Inventory control ROI is expected within year three or four due to the number of technicians and creating the foundation of information to import into ServiceMax. Expectations are the front end programming will be complete and our programmers will be better acquainted with the modules and architecture to make the inventory integration smoother than the initial integration.
Our organization has been working with ServiceMax for ten months and beginning to incorporate the financials to the work orders. This process has not been as seamless as once projected and the root causes are under investigation. It appears the original fields available to track time between employees were not in depth nor segregated sufficiently for granularity.
