BMC Helix ITSM replaces Remedy. It is a broad suite of ITSM, tools with strong integrations to other BMC tools and in-built ITAM. The product is used mainly by global brands and is offered in on-premise and SaaS configurations.
N/A
ServiceMax
Score 5.1 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.
Large complex organisation, with complex technology that needs to manage Technology Services. It is very flexible and able to manage a large complex environment but the knowledge required to set this up correctly (foundation data and configuration) is the key factor for success. It can integrate with many other systems and tools and integrate data from many sources - whether that be AWS cloud, or an on premises bespoke system. I would not recommend for a Small Organisation without the resources to set up and maintain the underlying foundation data and configuration.
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.
Integration with monitoring software like SolarWinds. where Remedy can transform notifications to work orders and assign to respective teams.
Detailed Customization capability to fit the exact needs of the organization.
Change management calendar, which integrates change orders from all organization departments and facilitates the scheduling process of project managers.
It can be offered as a cloud-based service, where you don't need to worry about server maintenance or database backup.
The interface (ironically). My company has made an attempt to replace the "classic" Remedy interface with some more functional, modern, but Remedy set to a particular look and feel (and consequently, functionality)
The API is hidden from the user: There exists an API for Remedy, that would make my job TONS easier, as I like to perform actions on Remedy in bulk (and therefore - programmatically). Exposing a user API is very much mainstream these days, so Remedy relying on its interface to perform ITIL is very limiting
By extension- the result of Remedy's interface is that it becomes very "click-happy": little buttons, and links stuffed into every corner of the screen, with options API logically together. API is old, but it still feels very rushed.
The primary tool for most of my ITIL operations is: searching. API of searching goes into finding assets, checking in equipment, finding users, tickets, etc. What Remedy could very much benefit from a "Google" -like interface
At least Remedy is all contained in a single platform, so the interface is consistent. Also, the most heavily performed functions are generally usable. However, to use some of the more advanced modules can be a bit more cumbersome (such as Change Management and CMDB (Not Including ADDM)). So, overall BMC Remedy ITSM is better than some applications like CA SDM or HP SM, but not quite on par with ServiceNow.
The support is good in overall resolving the issues and even in the deployment phase. We are able to use it in production without any trained in-house engineer as the support team gets the job done. We can say that experts completed the deployment for us, and now it is functional.
The decision to select BMC Remedy was made prior to my employment. We did conduct an RFC process for a new ITSM platform and BMC was considered but not selected. We looked at several platforms and ended up choosing Ivanti Service Desk (previously LANDESK) due to the features, ease of customization and price.
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.
When I was in Management discussion calls, and all the team is happy while using BMC Remedy so I don't find any specific negative impact on our organization.
I really enjoy Smart IT as the tool of choice for our incident management team.
Visibility of tickets is key. All support staff users can see tickets in consoles they have access to.
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.
