IBM Decision Manager Open Edition vs. Oracle BPM Suite

Red Hat Decision Manager is well suited for developing a microservices-based application architecture where reusable components / APIs can be used across different end-user applications. It however may not be well suited for use cases where business users need low code / no-code environment to maintain business rules themselves without any developer / IT team support

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.

• Business rule management for filtering the candidate
• Automate the possible decision making which reduces the time and increase the productivity
• Whenever business rule changes based on the client requirement.

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

• It should be easy to use because it needs more knowledge
• You should be trained to your partner well
• Well Documentations are needed

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

Red Hat Decision Manager can be scaled and adapted to meet the automation needs of the organization as it grows by reusing the components and business rules data which provides a high ROI on the renewal costs.

Incentivized

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

Implementation phase is very difficult .Of course ,you need to know bunch of things about cloud,container,automatization

Incentivized

Not easy to debug errors.

The support for Red Hat decision Manager can be improved to be more omnichannel with better response times for the customers.

Incentivized

For high volume and / or complex set of legacy business rules, plan for adequate time for data migration activities.

Incentivized

Overall satisfactory

If you have a low budget to invest probably JBoss BRMS is the option for you, if your budget is not restricted you'll probably like to consider Bizagi

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

• Quickly write business rules
• Computers can take decision
• Complex event processing

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