If you were talking to someone whose organization is considering IBM Blueworks Live, what would you say?
How would you rate it and why? Any other tips or advice?
It's on the cloud so it automatically gets upgraded to the latest version. My advice to others always ask questions, which is what I always tell my clients. You should be very observant, especially of why you are looking for processing. If your requirements are completely different from what the tool has to offer, then it will not be a good match and you will be setting up a recipe for a disaster. Look into IBM Blueworks. It is an active light tool and is it a proper architecture tool, which can do a lot of analysis. If you are looking for such a tool then this product is for you. It is cost-effective compared to any tool on the market. I would rate this solution an eight out of ten.
Unless you really want a simple solution for process discovery only and value simplicity over the ability to exploit more functionality, I see Signavio as a much better option. Of course, IBM may develop Blueworks.
We use the cloud deployment model with IBM as the provider. If you are planning to use the tool wisely, it's a good idea to name conventions, terminology, and structures around doing so right at the beginning. Considering how you will use the tool will help ensure it won't get too messy. During the discovery phase, it's a good idea to create discovery tables. It will help keep you organized. I'd rate the solution seven out of ten.
We use the on-premises deployment model. I'd advise users that they need to look at how relevant the discovery process is, and how quickly you can maintain it or its life cycle as things change. They should also note how it interfaces with other platforms that are integrated into their automation robotics. It's important users know what they are doing and what problems the solution will solve for them. I'd rate the solution seven out of ten. It's a competitive field, so there's always somebody who's better in some aspects.
Try it out. It is clear once you start using the solution that it is a different type of application. There is no direct competition to the tool. I don't think that there is another product out there quite like it. There are some competitors certainly, but they are either more complex, costly, or too simplistic and not geared towards process documentation. The integration process is pretty open-ended. You need to be fairly technical to make it work, but we have seen success in integrating it with QuickBooks and Salesforce. Now, we are looking at other systems to integrate it with, as well. I learned the best approach to adopting process improvement across an organization from using this solution.
I would recommend starting small when using this product. We are using IBM BAW. We are also using Automation Anywhere throughout the organization, so the sky is the limit. We are planning to expand automation in our organization. We have several onboarding processes and still have a plethora of manual processes that we have yet to automate. Therefore, the platform is only growing. From the IBM DBA portfolio, we are using: BAW, ODM, RPA, FileNet, and Datacap. The solution helps us indirectly with compliance or governance issues. I attended the business track and client success track at the IBM event, tackling one of each. The biggest take away for me was the focus on journey maps and design thinking.
My first process model had 142 activities. This is humongous from a single process perspective. To model, it took us three days to complete. It helped with our process version control issues. When we are working with one of our financial clients every quarter to do their financial reporting, the process changes. They had a lot of material weaknesses, so there are process changes. We keep on creating snapshots, so it helps us to to move them from a BPM implementation tool and put a governance structure around it. Creating snapshots helps us form a governance perspective. We use a document repository. There are multiple places for how we upload documents, either by going to dashboard interface or by taking pictures/screenshots that can be put in the documentation tab. It goes into the file management of Blueworks Live. You can review them later, clean them out later. You have one single source where you have lot of documents which are used across multiple processes. Everything's stored there. It helps in that way, making it lean and having your documentation updated.