In general, the configuration tools of the underlying platform let you set up an abstract model of a process that BPM apps run. You might be able to change solution-specific templates that come with the platform. It should also have "non-process" features like the ability to send an email, change a user's rights, or set a service level. But at their core, business process management (BPM) tools use models that are set up in a platform.This is important because when you run a model, you work closer to the end user because you're moving up the software stack. You'll have less code to manage, and it will be easier and cheaper to make changes to apps. When you change a process model and then release it, the process that is running changes how it acts. It is thought that the BPM tool will make this process of change less risky.
When you look at individual tools, it's worth a thorough investigation
There are standard ways to model a process, like BPMN, which you can learn, and there are also custom ways. I agree with standards, but they make it harder to come up with new ideas. Because of this, companies are always trying to make new features that break the standards. For instance, how do you make a special form and lay it out? As long as you think about tools too much at this level, you might never decide what to do. Keep in mind that software doesn't last forever, and look for something that fits your skills and process challenges.When you run a model, it should also be easier for the platform to record and measure behavior across all of your processes in the same way. This is important again if you want to see how well your system, people, and business rules work in real life. It's not that you can't collect metrics in other ways, like apps, but this is one of the benefits of having a separate platform.Some business process management (BPM) tools don't do technical modeling because the company that makes them thinks that it's one of the reasons why BPM projects cost so much and take so long. If you have a subject expert or someone who knows how your business works like a "sausage machine,"
that vendor will have thought that all you need to do is give them the tools they need to make a solution
Some people have called this a "low-code" way to do BPM, but it should be called "lower-code." It is hard to avoid writing code in some way when working on BPM solutions... read on.Just so you know, Microsoft Dynamics and Salesforce are not BPM systems, even though I've seen them sold that way. The systems come with application code that you can add to with more application code. From what I can tell, there is no idea of a plan there. These can both be made better with add-ons that do some kind of BPM.When you need to use developer tools to do something very specific, like figure out risk based on your own business logic or connect to a tricky internal system with a bad API, the languages and tools available become important. It costs a lot to train employees in proprietary languages, and they aren't very productive at first. Day rates are also high. It's pretty easy to learn JavaScript and.NET/Java. Look for these or related skills and maybe check market day rates as part of your research into a platform.Take a look at the OMG's Process Maturity Model and rate yourself. Even though it's a little old, I still think it's true and that you can learn something from it.
Not all of your business processes will be at the same level of growth at this point
BPM technology will help you right away, but it will take a long time to learn how to use it. The more developed your processes are, the better you will be able to use the technology, so the money you spend is more justified.If you are in the Initial stage, it might be smart to do something cheap to learn more about the process before you spend a lot of money. You might not need to go big after all. It's possible for home-grown software to run a business process well without being a BPM platform. That makes a lot of groups happy because it means they don't have to do anything else all the time. I've also seen expensive systems with bad BPM solutions that were put in place, mostly because of poor analysis at the start.I guess what I'm saying is that you shouldn't just throw a BPM tool at a problem without fully understanding how you want to solve it or what benefits you want to get from it. Buy something cheap that you plan to throw away if you are in the Initial stage. When you don't have extra money or time, you should really think about the business case and how you'll use the tool.
Comments
Post a Comment