Skip to main content
TrustRadius
IBM Business Automation Workflow

IBM Business Automation Workflow

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.

Read more
Recent Reviews
Read all reviews

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

Return to navigation

Pricing

View all pricing
N/A
Unavailable

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.

Return to navigation

Product Details

What is IBM Business Automation Workflow?

IBM Business Automation Workflow Video

Overview of Workplace from IBM Business Automation Workflow

IBM Business Automation Workflow Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating Systems,
Mobile ApplicationNo

Frequently Asked Questions

IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.

Appian, OpenText MBPM, and Oracle BPM Suite are common alternatives for IBM Business Automation Workflow.

Reviewers rate Dashboards and Standard reports and Custom reports highest, with a score of 10.

The most common users of IBM Business Automation Workflow are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(72)

Attribute Ratings

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
IBM BPM is used as middleware in our organization. It is used in the Banking and Finance sector of our organization. It allows us to customize the flow and we can even have a track of all the activities done. When it comes to user interfaces most of the other technologies use scripting and HTML tags but we do not have a track of all the activities done. In IBM, this problem is facilitated and it saves our time as a developer in tracking the issue faster.
  • 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.
IBM BPM is recommended wherever it requires the organization to develop in multiple platforms IBM supports like mobile, cloud, and web-based development. It is recommended for processes that require complex structures. It is not recommended where the UI structures are complex and when the business requirement has more load on the server.
Process Engine (8)
75%
7.5
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
Collaboration (1)
50%
5.0
Social collaboration tools
50%
5.0
Reporting & Analytics (3)
86.66666666666666%
8.7
Dashboards
90%
9.0
Standard reports
80%
8.0
Custom reports
90%
9.0
Content Management Capabilties (1)
80%
8.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 makes development easier, which is faster when compared to the others. IBM's customer support is good. Easy for the user to learn while providing powerful integration. More secure when compared to others. It provides the reusability of components. Monitoring and report capability is also high in IBM BPM.
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.
Score 10 out of 10
Vetted Review
Verified User
  • System does a great job normalizing business process and automating order processing tasks. Before TeamWorks, the process was much more manual and more expensive staff ($65k to $70K) were required to manage the process. Since implementing TeamWorks, we need much lower-skilled workers to manage order processing.
  • System ensures that we have consistent data across all systems.
  • Rules engine is really the “company playbook” – it is the heart and soul of how the company works. It handles thousands of orders per day
  • Related to the importance of the system to the company, it represents a single point of failure. Company is totally dependent on the system to enable to company to function.
  • A complete order cycle might take two weeks. If a rule is modified during this cycle, the system may break (e.g. looking for a data object which is required to make a decision but which is no longer available). A new rule must be manually constructed based on the old one, and then used to replace the old rule. There is no real version control management for rules. This is something that is available on the latest version of the software.
  • Data consistency. Data in SFDC is not kept updated automatically without requiring salespeople or others to manually keep the system up to date.
  • Automation means that order processing is much easier for staff – less skilled people needed.
30
Mainly used by Support and Finance – perhaps 30 people total.
1.5
  • Order management. Sales orders are entered in SFDC by salespeople and all of the processing and business rules for order management are handled by the TeamWorks business rules engine. Integration with SFDC is extremely important.
  • Implemented in-house
• 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)
  • In-person training
• 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.
This software is, by definition, heavily customized. It does not come out-of-the-box ready to go. The rules engine must be built and configured to support business rules specific to the business. Some advice: • Follow the documentation closely – it is very accurate and helpful. • Configuration mainly consisted of changing configuration files / domain names • We modified the documentation somewhat in an internal wiki to reflect our internal process but would be prepared to share with other similar businesses.
No
• Always get a response to a support ticket in less than 2 hours • Urgent tickets are usually responded to within 15 minutes • Support staff generally are familiar with our setup and it’s not necessary to explain things multiple times – frequently talk to the same person who is very familiar with our setup.
• The system is easy enough to use but, by definition, is a complex tool. However, they have done a good job generally balancing tool complexity / capability with usability. When comparing to MS Biz Talk, for example, Biz Talk has less functionality but is actually harder to use. • Software is very flexible. For somebody with the right technical background, it’s quite easy to write some Java code to overcome any hurdles or make the product do what is needed.
NA
  • SFDC / Great Plains / Customer Portal (home grown)
• All integrations are XML / web services based and were fairly simple to build. SFDC needed its own middleware.
Return to navigation