By combining ARIS for business modeling with webMethods for BPM execution, it is finally possible to transform organizations in even more strategic ways, while closely aligning business and IT departments around common, achievable business goals:
• Establish efficient processes that align business and IT around organizational goals
• Define role-based workflows that address who should do what and when
• Implement new processes within your enterprise or across specific IT environments
• Manage your architecture and enable it for SOA for faster creation of new processes
• Resolve problems by real-time process monitoring before they impact the customer
Tight integration with CentraSite and webMethods BPMS makes it easy to take business processes from a strategy and design point of view and transform them into models for process automation. This ensures that business requirements are not lost when handing over a BPM project to IT.
With ARIS and webMethods it is possible for the first time to work collaboratively on one process model, on the same KPIs and in line with corporate strategy. It brings together two product suites with the result that change management works precisely through the whole organisation.
A shared model with multiple views results in business-IT alignment. M2E brings two worlds together: Process Documentation & Analysis and Process Automation.
What problems does Model-to-Execute solve?
M2E closes the gap between corporate strategy, business-driven process design and IT. Business and IT speak one language and share a common vision about processes and their KPIs.
More efficient business operations with transparent, optimized and automated processes
Reduced project cycles with efficient business & IT collaboration
Provides the basis for continuous business improvement
concerning M2E I've a lot of questions but this is the main conceptional one:
Given an enterprise where the decision was made to go the COTS-way meaning that the COTS-
products already implement big chunks of the overall system behaviour including the UI:
Then we most probably don't need an overall controlling process-engine - is that right ?
But what we need is some kind of passive process control feeded by the COTS-product with businnes related events like "order created" / "oder successfully executed". I mean the steps in the process are not really executed (because this is done in the products). The engine would be some kind of state machine showing the current state of an activity in the IT landscape triggered by a business events engine.
I mean an overall process like "order to execute" will most probably not really be *controlled* by a process-engine in this situation but of course we want to know at which step we are.
Is that thinking ok ? / Anybody thought about that or having the same problem ?
That means: We don't really need the way of model 2 execute like it is described here which is some kind of greenfield approach but another one - right?
Thanks for your comment! Let me try to answer it or publish my opinion to it.
With regards to your statement on M2E in the context of COTS I would disagree. An overall controlling process engine is in fact of enormous importance when it comes to business processes that span across your diverse landscape of COTS. (Frankly, these so called end-to-end processes are often the most value-adding ones for your organization.) Using BPMS you can leverage existing functionality in your COTS and invoke them services along your higher-level process. We call this the agility layer. The overall goals are
to maintain a consistent view on your business processes along their lifecycles
to harmonize your IT landscape with BPM,
to allow your processes and IT to adapt to change and
to increase transparency within your organization.
Last but not least, the entire process that is behind M2E is inherently not limited to green-field projects, simply because it's a revolving circle. So taking into account what is already there, is a fundamental concept of M2E. Therefore the tooling offers a lot of functionality on a technical but also organizational level.
We would like to understand better, what made you think M2E is limited to green-field / no-COTS projects. Please share your thoughts with us.
