Benchling vs. Oracle BPM Suite

Benchling is especially well suited to groups or contexts where there are many users who do not have a coding background but need a seamless and structured approach to data. Benchling is particularly useful in cases where there are data flows from instruments and other devices where the data can be deposited in an automated fashion. It is likely less appropriate or useful to users who are just looking for a general data warehouse solution.

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.

• Excellent easy to use and beautiful UI
• Great customer support and training
• Has no code ways of retrieving and depositing data

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

• Some of the integrations can be a bit spotty so it depends on what kind of data source you are integrating
• Sometimes new users are not always aware of all the various functionality that Benchling has - can do better to provide more user awareness of more complex features

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

Benchling was much more of a full stack solution and provide much more features that were relevant to the group. Airtable was more of a generic way to manage large amounts of data, but the complexity was still high for the types of data that would be need to be managed and there would need to be some workarounds. Overall Benchling was selected since it also had an electronic lab notebook feature which was very useful to associates in addition to its data workflows.

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

• It had a positive ROI in terms of reducing the amount of time spent on data movement and curation by associates
• It had a positive ROI in terms of increasing the number of insights from structured data
• It reduced the number of data entry and analysis errors by associates which led to a positive ROI in terms of efficiency and reducing time wasted by tracking down errors in data

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