Likelihood to Recommend Although the tool was developed locally in South Korea, it is still a good tool and is already validated in a number of industries. The problem is, no one seems to know the future of the product. It is okay to use it as a pilot tool for any non-commercial purpose, but to be used in a professional or enterprise setting, maintenance, licensing, and other things need to be guaranteed by HandySoft.
Read full review Read full review Pros BizFlow has a long history of development and implementation in a variety of industries. Its modeling tool is well-designed and user-friendly. BizFlow supports seamless integration with backend services like MySQL databases and web services. Since it is an enterprise-wide BPM tool, system performance was stable and robust. It supports modern m-health requirements, with social BPM functions and mobile support. Mobile integration especially was good, with the provider's secure messaging functions. Read full review 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 Read full review Cons It's not even clear that BizFlow is still managed by the company. It was a good tool before, but it looks like it's been fading out. Although this was an R&D project in an academic institute, business support was extremely poor. We had no idea how to resolve issues; there were no online communities, documentation, or anyone who knew this product. Few references in healthcare and clinical settings. We tried this for a proof-of-concept though, so it didn't matter. Read full review 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. Read full review Likelihood to Renew 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.
Read full review Usability • 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
Read full review Support Rating 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.
Read full review 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.
Read full review Implementation Rating • 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)
Read full review Alternatives Considered At the beginning of the project, we considered popular tools for the modeling and execution of business processes: jBPM, Activity, Tibco, etc. jBPM is the tool we liked because of its strong support of BPMN 2.0 and strong online community and support. We had different expectations for BizFlow, like professional and business supports. In the end, although haven't decided yet, most likely we will move forward with jBPM instead of BizFlow. Unless things change, the tool will fade out from the market silently.
Read full review 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.
Read full review Scalability 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
Read full review Return on Investment We ended up deciding to not use BizFlow for future projects. The main reason wasn't due to ROI or cost, but was due to our uncertainty of the management and future direction of the tool by the company. Besides the business issue, as far as reasonably priced software goes, it is a good tool. Adopting BizFlow into a healthcare industry may come with additional expense due to its lack of references in the industry, which should be additionally considered. Read full review 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. Read full review ScreenShots