Camunda is a process orchestration tool designed to help organizations design, automate, and improve any process. Built for business and IT collaboration using BPMN and DMN standards, Camunda aims to enable seamless integration across endpoints to transform mission-critical processes.
N/A
IBM Business Automation Workflow
Score 9.6 out of 10
N/A
IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
N/A
Pricing
Camunda
IBM Business Automation Workflow
Editions & Modules
Self-Managed Enterprise
Contact Sales
per year
SaaS Enterprise
Contact Sales
per year
No answers on this topic
Offerings
Pricing Offerings
Camunda
IBM Business Automation Workflow
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Camunda
IBM Business Automation Workflow
Features
Camunda
IBM Business Automation Workflow
Customization
Comparison of Customization features of Product A and Product B
Camunda
9.0
1 Ratings
36% above category average
IBM Business Automation Workflow
-
Ratings
API for custom integration
9.01 Ratings
00 Ratings
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Camunda
8.0
1 Ratings
1% above category average
IBM Business Automation Workflow
10.0
4 Ratings
23% above category average
Dashboards
8.01 Ratings
10.04 Ratings
Standard reports
7.01 Ratings
10.04 Ratings
Custom reports
9.01 Ratings
10.04 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Camunda
8.5
2 Ratings
17% above category average
IBM Business Automation Workflow
10.0
4 Ratings
18% above category average
Process designer
9.02 Ratings
10.04 Ratings
Process simulation
9.01 Ratings
10.03 Ratings
Business rules engine
7.02 Ratings
10.04 Ratings
SOA support
9.02 Ratings
10.04 Ratings
Process player
9.02 Ratings
10.03 Ratings
Form builder
5.02 Ratings
10.04 Ratings
Model execution
10.02 Ratings
10.04 Ratings
Support for modeling languages
00 Ratings
10.04 Ratings
Business Process Automation
Comparison of Business Process Automation features of Product A and Product B
Camunda
9.0
1 Ratings
28% above category average
IBM Business Automation Workflow
-
Ratings
Business Process Modeling
9.01 Ratings
00 Ratings
Decision Modeling
9.01 Ratings
00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Camunda
-
Ratings
IBM Business Automation Workflow
10.0
3 Ratings
18% above category average
Social collaboration tools
00 Ratings
10.03 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.
Have your process first on paper 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.htmlKnow the difference between process data and business datahttp://bpmstech.blogspot.com/2011/05/lombardi-best-practices.htmlhttp://bpmstech.blogspot.com/2012/02/bpm-system-architecture.html
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
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.
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.
• 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
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.
• 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 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)
Lacks good documentation. Training and documentation is geared towards those who are already technically adept. Does not have as many data integrations as other full fledged products. Paid version of Camunda is not as fully fledged as other products.
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
The positive impact is that we are able to ensure the business process is being followed and that results in orders getting processed successfully leading to customer satisfaction and revenue
Another positive impact is that we are able to track any anomalies and any errors in the order flow and retry them so that users don't have a negative experience.
A negative point is that it is an overhead to maintain so there is significant engineering effort getting invested there