IBM Business Automation Workflow vs. TIBCO® BPM Enterprise

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

The scenario where TIBCO ActiveMatrix is well suited is in the scenario where there are more long-term business processes and in a complex corporate organization where there are many users with different privileges to perform actions on the same processes. It's less appropriate where there are no complex business process especially if the resubmit of the task in error is not required.

Incentivized

• 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

• TIBCO offers multiple ways to implement the sophisticated forms of event-driven BPM. It also balances the combination of business rules and AMX BPM for a different variety of IT Applications
• It depends on the Enterprise service bus which is message oriented middleware
• The integration of Spotfire with AMXBPM and BusinessEvents is a unique advantage

Incentivized

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

Incentivized

• A little bit too conservative. Not really anything leading edge. [Tibco] has plenty of customers, and that means they will probably be around forever, but [product enhancements] seem to be more [abundant in competitor product offerings].
• It would be great to have some pre-defined themes. Pie chart labels - it would be great to get more options for sizing and placement.
• I find it hard to trust the online portal too much. I doubt the security that is offered by this software.

Incentivized

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

Such a BPM sw is amazing and usefull. You have a gret visibility in design and development phase.

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

Because our support team is always available also for development suggestions.

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 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)

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.

For BPM we looked at some IBM products suites, BPM Online, Oracle products and Pega Systems. The decision to go with AMX BPM was based on the evaluation by the software architect team and the cost of acquiring the TIBCO suites.

Incentivized

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

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

Incentivized

• In order to create a BPM management, you need to make a very solid data management model, which becomes very important in its reuse
• The business process is very often unconnected with the implementation logic and therefore plays in favor of the re-usability of the software
• Large customization at log level for which managing these tools can be handled minimizing effort

Incentivized