Appian vs. IBM Business Automation Workflow

Appian is well suited for the areas which involve a workflow. For Example: Consider there is a task and 3 teams are required to work on the task, with Appian we can create tasks for each team and monitor the comments and completion. Together with the integration capabilities, this tool can function in many areas. In our firm, we are using it to automate the workflows for our business teams and help them in capturing the OLA's and SLA's.

Incentivized

It is best suited for streamlining business processes in our enterprise. It acts as middleware and allows to use of mobile development

Incentivized

• 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.

Incentivized

• Case management - provides flexibility for dynamic processing.
• Smarter process - streamlines repeatable activities and does work distributions.
• Advanced integration - makes integration with other systems very easy.

Incentivized

• 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.

Incentivized

• Installation is (typically) a bit painful out of the box and requires expert help.
• Following installation, initial projects require outside consulting expertise to be successful. Projects without importing BPM expertise tend to have much higher failure rates. Though individually the technologies involved are widely available and not complicated, combined and collectively BPM solutions require a flexible, creative, technical talent to help deliver. It takes time to learn the judgment and craft required.
• The out-of-the-box UI controls (widgets) are not terribly inspiring- on desktop or mobile. Use of third party toolkits (e.g. Brazos) is recommended. Silver lining: those third party toolkits are quite good.

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

This particular decision will be made by other people. Overall IBM BPM is the best BPM engine that I have worked with. It is implemented at our company and IT and business are already somewhat familiar with it. Therefore if asked I will recommend renewal as long as the price is reasonable.

There are many differences between using Appian and using other programming languages. Additionally, there are many trade offs that have to be made and that have to be accepted for using Appian. In some cases, you give up control of one small area, but in others, it may open settings that are unavailable to a developer when using other program languages.

Incentivized

Building complex UIs can be cumbersome. Calling complex SOA services that have a lot of objects, types, anyType attributes, recursive object references, etc can be cumbersome. The Process Designer IDE communicates with the server side Process Center a lot and as a result it is pretty slow. The IDE is also Eclipse based which doesn't make it faster.

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.

Incentivized

Issues can be raised through tickets and it works based on the priority of the issue. The Support Team response is also good and the solution is provided in a short span of time. In a case where the issue is serious, they try to find out the root cause and provide an alternative for it.

Incentivized

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.

Incentivized

• Attended on premise sysadmin training for 4 days, 8 hours per day. Although further follow-up training was available, I never felt the need to go back. Training was very hands-on with real modeling (rather than just following a manual). Very effective.

Very boring; hard to get through quickly, but rather effective in demonstrating the use of the platform.

Incentivized

It was really seamless. SaaS in the true definition of the word. We logged on and started using the product. Very easy.

Incentivized

• Very satisfied – not too difficult at all.
• We had a consultant available as part of our contract, but we didn’t really need to use (except for some advice on ActiveDirectory and single sign-on)

Appian compares favorably with other vendors in the space. It is strongest with business workflow automation and to create custom business applications. The tool base for coding is extremely straightforward and allows for faster coding and deployment. Handles very complex process flows and has the ability to discover new opportunities for automation.

Incentivized

Pega Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product. However Pega, falls short on integration centric capabilities and very rigid to customize. On the other hand IBM comes with array of products which suits needs of varying degree. Advanced integration is solved by BPEL Process Server which has support for state based patterns and mediation. Dynamic rules and event management can be solved with WODM, Cloud to on-premise connectivity with Cast Iron, Enterprise gateway and security usecases with DataPower, Social BPM with IBM BPM , WODM, mobify with Worklight. Pega has a little bit of eveything here and there. It solves the dynamic rule management, brings out the flavor of Social BPM and mobility with Antenna ( I guess) and predictive analytics as well in one single suite. There are certain usecases which needs to have a little bit of everything, however this little bits and pieces of functionality when its blows, Pega would have problems to scale. With IBM its a bit nightmare to maintain a variety of technologies, however you can wish to go for one without the other and go for something only when you truly need it. Pega vs IBM Its difficult to pick a winner. In nutshell when you want a full scale BPM with rich integration capabilities go for IBM BPM. On the other hand if you hava mature integration capability already, Pega can yield quick results for you as well. Pega's strength is its methodology. IBM BPM's strength is integration. Actually you can't go wrong with both in terms of implementation. My strong recommendation is to invest time to process analysis and pick a good vendor to support consulting and implementation.

It scales from small team interactions to business processes serving thousands of employees, as well as straight-through-processing needs that go well beyond. Of course, scale is always in the eye of the beholder, but IBM BPM does a good job of giving you all of the hooks, APIs, and data that you need to take on whatever scaling approaches you need to meet the load

• Our IT automated procurement process has sped up time to get paid by a few days on every transaction
• Our approvals are more organized as a result of being put in digitally
• Managing our own tenant requires more than we have available, given the quarterly updates
• Since we have business-critical functions running in the platform, we have to thoroughly review every note of every update. Because of this we skip half of the updates since we don't have enough time to review these changes four times a year.

Incentivized

• Easier to implement and does not take much effort to work on it.
• Versioning made easy. We can even degrade to the previous version in case of any issue, which is not easier to do in other BPM suites, thereby, saving a good amount of time.
• Helped in achieving client requirements faster, which results in a higher return of investment.

Incentivized