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.
$100
per month
Simpro
Score 8.3 out of 10
N/A
Simpro, headquartered in Brisbane, provides business management software for the trades and services industry. The solution combines field service management with asset tracking and maintenance, project management features with resource scheduling, and invoicing. For enterprises, Simpro helps manage business complexity such as franchises, multiple companies or multiple locations with a tailored Simpro framework that aims to handle complexity while maintaining the simplicity of working with one…
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.
Simpro is well suited for job and team management, tracking inventory and the workflow is very logical. The mobile app for our field technicians works very well to clock on and off and then being in a position to report to a customer based on factual information has made invoicing a breeze! Reporting can be a bit frustrating especially on materials used on different cost centre numbers as you can only specify a job number, but not a cost centre number.
As mentioned before, materials reporting could use some work as one cannot report by cost centre number, only by job number. It makes it difficult with large jobs with multiple cost centre numbers to easily extract information for reporting. Other than that the system is user friendly and easy to understand.
It is a great option for solar project management. It needs some improvements for real-time one-page reports, inventory management, scheduling and custom views. I believe these will come because they listen to their customers. I would also like to see some better training and not be expected to pay out of pocket for it.
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.
monday.com was easier to set up and you can create boards with loads of subtasks which helps manage a project. Also, the ability to integrate with google was much better as we could link it to the calendar and also store documents that the engineers could see easier onsite. Overall we could make monday.com work better for our business based on how we are set up but simPRO will be great for other businesses with more specific needs.
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.
