OpenText Service Manager vs. Oracle BPM Suite

HP Service Manager (HPSM) is well suited for a big company and it does the job that it's intended to do but it's not perfect. It has a fairly large learning curve for searching Knowledge Management (KMs) and it takes time to learn how to be fast at creating/resolving tickets while on calls. I have been using HPSM for about 2 years now and we recently moved from the desk client to the web client and we are seeing a lot more issues than we did with the desk client. They keep coming out with updates for it so eventually most of our issues will hopefully be resolved. Overall the web experience is better as it looks more modern than what we used in the past.

Incentivized

Oracle BPM is well suited to organizations and environments that have a good understanding of their business processes and organizational structures. Trying to introduce a tool such as Oracle BPM into the organization without a good grasp on how the business operates is a recipe for disaster as the implementation will uncover all of the dirty secrets of an organizations business processes and bring them to light. BPM is not to be utilized for smaller service orchestrations or technical service implementations, these should be handled by the Oracle SOA Suite using the BPEL process manager, leaving BPM to handle the organizational business processes, referring to and including lower level services and BPEL processes as needed.

• Capacity management like maintaining CI's and their relations is good.
• Approvals with HPSM is a cake walk and quite logical.
• There is no wait for troubleshooting or help, HPSM tech help is always there.

Incentivized

• Oracle BPM [Suite] can support unlimited number of cases. No limitations in cases raised.
• Oracle Weblogic can handle multiple traffic. [It] can handle lots of heavy load[s].
• Oracle BPM has extensive integration with database[s]. Huge number[s] of customization can be created.

Incentivized

• When you search Knowledge Articles, it is not like Google, and you need to learn how to search for what you need.
• It takes a very long time to close tickets in HPSM. Here are the steps to close a ticket. 1. Add notes. 2. Add KM 3. Click Resolve 4.Click Save 5.Click Close 6.Click Okay to Message (ticket has recently been modified) 7. Click Close.
• It's slow and sometimes crashes/freezes and you lose all the information you may have entered. I usually use notepad++ to gather all my notes and paste them into HPSM.
• When searching previous tickets the preview pane does not allow for sorting by date to have the most recent at the very top every time you pull up previous tickets. Sometimes there are pages and pages of previous tickets and you have to click and scroll to get what you need.
• I click on search KMs and it takes me to a blank page and I have to click the back button which then brings me to the search KM page.

Incentivized

• Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
• To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
• The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
• As with all Oracle products, the price can be an issue for smaller shops.

Incentivized

In many scenarios it should have provided more features. It took a lot of effort while debugging, making it difficult to maintain.

Not easy to debug errors.

Overall satisfactory

[We selected HP Service Manager because] HPSM is reliable.

Incentivized

We evaluated Bonita and found that it might fit a smaller-sized company better; we found that Oracle BPM Suite scaled much more evenly. We almost went with one of the competitors, but in the end chose Oracle BPM Suite after we factored in the cost of VMware licensing. There are literally tons of analytics on the back end which are great for upper management, but not so much for average users, but this fits our business model quite well.

Incentivized

• We take anywhere from between 850-1400 calls a day and overall the whole opening tickets to close process goes pretty smoothly.

Incentivized

• You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
• Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
• For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.

Incentivized