There are a lot of tools you could use if the reach is low. At the lower end of the scope scale, the case for a throwaway DIY software app build can also become appealing. However, I would generally advise against this; there are many low-cost BPM tools you can use instead, and having less code that needs to be maintained is a good thing, unless you're a contract developer.For a big and complicated project, your platform will need a lot of pre-built connections, reports that are specific to the field, data migration tools, and process models or templates that you can use right away. In this size range, SAP and Oracle sell solutions for specific industries. I would have to ask an expert if you're really in BPM land or if you're working with complicated apps built on top of old code and hiding behind a nice front end.
If you are going anywhere with these guys, get a new checkbook from your bank manager
I have my doubts.Case management is another area you might want to look into more closely. It's a part of business process management (BPM) and is usually easier to set up and solve problems faster. For example, an application for a new product is an example of a "case" that is a user-defined set of organized and unstructured data. The steps you take to handle that case are called "management."Do some study to see if you can find a BPM/Case Management tool that is only used in your field and not sold by any of the big companies.If so, could you talk to someone from the client side and someone on the execution team from the vendor or integrator? If that's not how the technology has been used before, that's not always a bad thing—BPM platforms are often all-purpose toolkits after all—but you need to see how it would be used to solve your problem.Talking to someone who has dealt with a similar issue before could also help you figure out the total cost of ownership over an acceptable time frame, like 5 years. It is clear that learning from others' mistakes is a good way to lower risk and costs.I met the CIO of an Australian energy utility company who didn't trust his own employees to figure out what the core processes of his customer service department should be. At the time, the company was putting out a BPM platform. A lot of the time, big businesses spend money on BPM projects. Google how much the UK government lost on Universal Credit or how Scotland's "NHS 24" cost more than planned by GBP £50 million.
Even though top companies are working on these big, complicated business process problems they still don't get solved
If you're sure that your team knows how to do all of this or that the developer and product you chose are a good match for you, that's fine. No matter what, you should manage risk from the start and divide your job into small parts with regular due dates. When resources are limited, I'm not a big fan of "going agile." Instead, I like using user stories to spell out needs.Instead of using a technical metaphor, if your team has never done this before, a tool that lets you set up processes as you go (i.e. while they are running) is a more realistic option. You'll be in good shape if that platform also comes with subject knowledge in the form of process models that are already set up. When you change the definition of a process model on this kind of platform, you need to make sure that process instances that have already run or are in flight are treated gracefully. You should poke a stick at that tricky part.Good luck if you do. When you're done with your exercise, your needs will have changed. Simulations aren't always bad; sometimes they're necessary, like when you need to plan a new road network. But I'm not sure if it works in the real world of business process management (BPM).
Another broad statement glad to learn more
It's much better if your BPM platform has great tools for checking service levels on time- or resource-sensitive tasks within certain processes or process steps, or tools that can report on staff utilization so you can see when staffing is tight and plan ahead."Volatile" means that it can change often, and often means every day. Even though the change might not happen every day in your system, it could happen very quickly in the real world. Change is needed because of things like rules, new competitors, new business prospects, and new ideas within the company.The tool you choose should be able to quickly change how processes work if your processes are unstable but you still need to run them in a live system. This checks how well the tool can model, test, and release. Focus on this during any lesson and use a range of situations.You might benefit from a case management tool if your processes need to be active on demand, meaning that you only know about them when they are carried out. You could also check out how well the platform can learn. Does it have the analytical power to make live, changing decisions? It's the holy grail of BPM, but you might not need it. You should have seen the word "adaptive" in your study, so ask your vendor to explain what they mean by that.
Comments
Post a Comment