Overview
What is IBM Business Automation Workflow?
IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
Good BPM tool with many features.
One of the pillars of the Digital Transformation, Business Process Manager
IBM BPM Review
IBM BPM - the best commercial BPM software package
Overall a good BPM engine, but use it for what it's meant to be
Should I choose IBM BPM or Pega? How strong is IBM BPM?
Complex tool, but works well.
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
What is IBM Business Automation Workflow?
IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
31 people also want pricing
Alternatives Pricing
What is Quixy?
Enterprises can use Quixy's cloud-based no-code platform to enable their business users (citizen developers) to automate workflows and build simple to complex enterprise-grade applications for their custom needs, according to the vendor up to ten times faster. Quixy helps eliminate manual…
What is Pipefy?
Pipefy headquartered in San Francisco offers their process management and workflow software providing processes for customer success, service desk, sales operations, and other processes.
Product Details
- About
- Competitors
- Tech Details
- FAQs
What is IBM Business Automation Workflow?
IBM Business Automation Workflow Video
IBM Business Automation Workflow Competitors
IBM Business Automation Workflow Technical Details
Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | , |
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(72)Attribute Ratings
Reviews
(1-4 of 4)Good BPM tool with many features.
- It allows us to use mobile development, which most of the other BPM suites do not provide.
- It adapts to new technology faster. Example: They are trying to implement microservices now, which is currently trending.
- It has the whole structure divided into parts like process center and process management, all of which make the tracking and development and monitoring instances easier.
- The system gets crashed when many instances go into the queue stage. The system even crashes and sometimes restarts automatically when the load on the server increases. We had to develop a separate software for this and maintain the same.
- We cannot manipulate the data during run time. It is difficult to develop user-interfaces with complex functionality.
- In order to consume external services that follow HTTP protocol, we need to use IDE for that, and consuming services from IDE takes a lot of time to give a response.
- Process designer
- 80%8.0
- Process simulation
- 80%8.0
- Business rules engine
- 70%7.0
- SOA support
- 50%5.0
- Process player
- 70%7.0
- Support for modeling languages
- 80%8.0
- Form builder
- 80%8.0
- Model execution
- 90%9.0
- Social collaboration tools
- 50%5.0
- Dashboards
- 90%9.0
- Standard reports
- 80%8.0
- Custom reports
- 90%9.0
- Content management
- 80%8.0
- 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.
IBM BPM Review
- 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.
- Performance - due to high I/O with DB some of the times the flow responds slowly to changes.
- Supporting coarse-grained services. Some of the services with nested objects and cyclical references do not generate the types on the BPM side.
- Support a higher number of in flight instances - the system chokes and behaves erratically once the active instances goes above 20K.
- Process designer
- 80%8.0
- Process simulation
- 70%7.0
- Business rules engine
- 40%4.0
- SOA support
- 70%7.0
- Process player
- N/AN/A
- Support for modeling languages
- 70%7.0
- Form builder
- 60%6.0
- Model execution
- 70%7.0
- Social collaboration tools
- 40%4.0
- Dashboards
- 70%7.0
- Standard reports
- 70%7.0
- Custom reports
- 90%9.0
- Content management
- 80%8.0
- It has added value to the upper management to give visibility into what is happening at any time in the enterprise.
- Boosted employee morale because it gives them all the information to work the case/task in a single location.
- Identifies bottlenecks and improves the turnover.
- BPMN diagrams are somewhat easy to read and comprehend for non-technical business users.
- BPM Coaches allow developers to rapidly develop simple User Interfaces.
- BPM allows developers to call basic SOA services easily.
- If you need to develop complex User Interfaces, they are very hard to implement using Coaches.
- If you need to call SOA Services that have complex data structures such as recursively nested objects and anyType objects, the built in service discovery and type generation does not support it and blows up.
- The Process Designer IDE tends to run very slow because of all the chatting it has to do with the server side Process Center.
- We are documenting our business processes using BPMN.
- We are forced to think deeply about our processes and optimize them as a result.
- We are getting rid of manual processes such as mailing paper forms.
- We can monitor our processes and improve them constantly.
- Creating a Coach UI
- Calling a simple Web Service
- Claiming and submitting a task
- Developing a complex UI
- Calling a complex Web Service
- Development can be slow because Process Designer IDE chats with server side Process Center a lot
Should I choose IBM BPM or Pega? How strong is IBM BPM?
- IBM BPM's biggest strength is process modeling. With blueworks its a cake walk to white board processes to stakeholders and chat around.
- IBM BPM Coaches went through a significant improvement with a easy to customize views, rich Dashboards and REST API for building complex portals. This is a game changer when compared with Pega which is little rigid when it comes to displaying BPM tasks on external portals.
- With IBM BPM Advanced there is a way to enforce a clean architecture. Long running system to system level processes can get into BPEL Process Server, short running system to system transactions on WESB and human interactions on the Lombardi Process Server. Basically IBM BPM supports SOA to the core. So bottom line is IBM BPM supports human centric, integration centric BPM methodologies. With CMIS support, document centric capabilities are well supported too. This is a another distinguishing feature from Pega which isn't too integration centric.
- IBM BPM should bring in the Agile methodology and enforce it as a way to build software. If its comes from IBM there is very little chance that vendors can mess around the SDLC, jeopardizing project implementations.
- IBM BPM should enhance the traceability of implementation with requirements. Blueworks to Process Modeling works well for the first time implementation, however when a process needs enhancement or improvements, the modeling represetation gets blurred due to implementation details. This can be currently worked around with stricter goverance around process modeling, but would like IBM to come up with a solution
- Merging of snapshots - something needs to be done on this aspect
- A tool to peek into process data BLOB. Ability to change the process data at runtime - Nice to have.
Its important to first document the process before venturing into BPMS. It will save a lot of pain and heartaches. A BPM tool is no
magic bullet, it merely automates your process. Its upto you to put visibility and tracking on top of it. Provide monitoring so that
you get a chance to improve your process continously.
BPM is not an application
If you are trying to build an application with BPM, chances are that your are alraedy failing. BPM must be a strategic initiative for an
organization. Yes, you build Dashboards, Reports and other software in BPMS, however you do it at a process level not at an application
level.
http://bpmstech.blogspot.com/2011/05/bpm-initiative.html
Know the difference between process data and business data
http://bpmstech.blogspot.com/2011/05/lombardi-best-practices.html
http://bpmstech.blogspot.com/2012/02/bpm-system-architecture.html
- Improved process visibility
- A realistic chance of improving process, continously
- Real time tracking and alerting, empowers managers to take decisions on the fly when error happens, not after something had happened
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.