Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Oracle BPM Suite
Score 8.6 out of 10
N/A
The Oracle Business Process Management Suite is an integrated environment for developing, administering, and using business applications centered around business processes.
N/A
Pricing
Appian
Oracle BPM Suite
Editions & Modules
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Personally, I feel Appian is a more focused and tightly integrated product. Our time to delivery was shorter, while actually delivering more. The fact that apps are natively mobile out the box, can not be overstated.
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
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.
Allows at a glance workflow documentation which assists in the need we have for information readiation.
Drag and drop interface for workflow development greatly speeds our apps time to market.
Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.
Search issues when type ahead and database search are used in the same field.
Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.
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.
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
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.
I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.
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.
