AVEVA Work Tasks vs. Oracle BPM Suite

Anything where form input is required, data presentation and custom interface screens, connected to a database or API backend. Also good at process orchestration, where tasks need to be allocated and completed as part of a workflow, it supports delegation and escalation. It does fit well tieing together other AVEVA products.

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.

• Wysiwyg form editor
• Desktop and mobile display
• Extensibility with JavaScript and c#
• Web API calls

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

• Workflow editor user interface, a little clunky and has a learning curve
• Permissions model is complex
• Themes and corporate branding requires detailed css
• Upgrades require very thorough testing of developed artefacts

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.

The features and capability is very good, but there is a learning curve to develop within it. It does take some effort to become proficient and build forms and workflows, however once deployed and running they are extremely reliable. The mobile application is quite good but best suited to be on an on-prem network rather than internet facing.

Incentivized

Not easy to debug errors.

Overall satisfactory

Power Apps is good for microsoft, and basic forms, Work Tasks is more powerful. Other middleware is better for pure data integration but doesnt enable user interaction. There are some other options, Redhat has a similar product as well but it wasnt as mature when we were evaluating.

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 have built our entire EOM reconciliation process for production management, this is not possible without Work Tasks
• We have complete standalone processes and applications built in Work Tasks, where complex steps and integrations are required. It is faster and cheaper than multiple bespoke products
• The API integration has allowed us to tie applications together where user input is required and middleware doesnt quite work

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