I found an interesting entry on my colleague Todd Biske's blog Finding Value in BPM/Workflow Technology.
Here are some additional thoughts on how the value proposition for the BPM and Work Flow Management tools could be taken to the next level.
1) Ability to incorporate "Rules" or a "Rules Engine Component" into a business process step or a work flow task would be a great addition to these BPM/ Work Flow Engines. These rules can be encoded best practices or they can be regulatory in nature or business algorithms that may be volatile while the process flow or the work flow may not be so.
2) Ability to perform impact analysis for any process flow change prior to releasing the "new process".
3) Availability of analytical tools that could suggest optimization opportunities that could make process improvement suggestions such as the following
a) how switching the steps in the process may benefit the overall process flow
b) how metrics show that there is a ton of waiting in a step that could be made optional based on some criteria
c) how analytics could drive other optimizations such as making suggestions for automation of an information gathering step
4) Ability to subscribe to regulatory bodies that govern the outcome of a particular step of the process flow.
5) Ability to create a business process template for oft used processes within an industry vertical that allow standardization in the overall flow while catering for customizations and competitive advantage optimizations in particular steps of the flow.
Best Regards!!
- surekha,
Practitioners observations and view on the best practices, key learning on the fast changing landscape of technology and architecture. - Strategic User of Information Technology - Cloud Computing - Big Data
Subscribe to:
Post Comments (Atom)
Key Learnings - Using EDA to implement the core SOA principle of "loose-coupling"!!!
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
The purpose of this blog is to get some validation for how I look at Business Processes vs. Business Services. In simple terms, I differen...
-
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
One of the key ingredient for success is clearly defining the roles and responsibilities within IT. There are multiple stake holders in IT w...
4 comments:
I think the ability to manage decisions, using business rules and more, in the context of business process management yet without embedding one within the other is critical. It is not enough to support rules or rules-based specification. The system must also support the effective management of decisions across processes and between processes and other systems.
JT
James Taylor
Blog: JT on EDM
I just blogged that I think “Big SOA is Dead; Little SOA is Thriving” at: http://tinyurl.com/soa-today2 . Ok, maybe Big SOA isn’t “dead”, but certainly struggling to convince companies to invest in BPM, BAM, ESB (Big SOA) in today’s economic climate is a tough, academic sell when they can go Little SOA with positive ROI. Organizations want rapid results– they want SOA Today and not 6-9 months down the line!
Technology has gone to a different level. New thing are been innovated every second.
A very useful blog about thoughts on finding value in BPM/Workflow technology. I was not aware of this topic.. This article has granted me with good knowledge. Thanks for sharing the information with us.
Post a Comment