I read the proposal and presentation materials from Kevin and find this
project/requirement essential to advanced process automation. Not only is
this essential to inter-communication and processing among like product
families (i.e. same vendor), this is also essential to accommodating large
organizations which may be required to operate/support multiple solutions
across a common set of functions with different vendor solutions. In other
words, I can integrate and interoperate across two diverse instances of a
Problem/Bug Tracking Tool while achieving a common process outcome.
I am very interested in the establishment of a common or base set of
events, states, rules, properties, and information points for the
fundamental aspects of (ITIL) process management. I strongly believe that
we must define the base in terms that are common and shared at the lowest
denominator, enabling those that need to "get along" to inter-operate in
like and consistent ways across the life cycle.
As an IT industry, with many years of life cycle process and automation
experience, the time is right to normalize, standardize, and build from a
common architecture.
The other aspect of this that intrigues me is the ability to add
intelligence to the process automation arena. Rules that drive common or
best practice conditions and assist in process management by moving things
forward, escalating when necessary, or even making certain decisions when
the appropriate criteria has been met, will allow the real advancements to
take hold.