Meta-Process

'Meta' is an abstraction!

A meta-process is a process to build a process. A methodology for identifying, analyzing, and building a BPM solution is a meta-process. A methodology is more than a process. It includes rules and guidelines, for example. Merriam-Webster Unabridged defines "methodology" as (1a): a body of methods, procedures, working concepts, rules, and postulates employed by science, art, or discipline. 

Meta is an abstraction, description, or even orchestration. Meta (from the Greek preposition and prefix meta- (μετά-) meaning "after" or "beyond") is a prefix used in English to indicate a concept which is an abstraction (Wikipedia) ...There could be such a thing as a meta-methodology; a methodology for creating other methodologies. Metadata – data that describes and defines data; meta-process; the process for orchestrating or transforming other processes. Perhaps the "orchestration" is more relevant to the "system of processes" as business processes management has to be more dynamic and adaptive to the accelerated speed of changes.  

Meta-process is a process that describes and defines the process. This means that the managers have a meta-process whether they understand it or not, and decides goals and targets for the target process, normally a key-process. But the more unknown this process and ad-hoc, the less likely that the target process has succeeded. Universal Process is also part of the route into interoperability. Along with relational semantic and meta-rules which are the building blocks to descriptions of the universe. There are two different structures: 
(1) "Larger and smaller" as each the process may have servicing (customer) processes and servant (subordinated) processes; for example, departmental processes and enterprise-wide processes; 
(2) Each cohesive group of processes has related monitoring, operating and governance processes; for example, a governance process for all departmental processes is different from a governance process for all enterprise-wide processes. 

A business process is explicitly-defined coordination for guiding the purposeful enactment of business activities.  The business processes are nested, but each layer of processes has different levels of important values and goals. A process is a combination of mental processes and manifested processes, full of turbulence, obstacles, etc, and that’s why the fluid analogies come better, so that the value pipe, when you apply, should detect the human issues inside the process, regardless of levels. Meta-Processes provide "fully functional, atomic" process components; which can be used to build other processes.

A protocol is a generic process- a meta-process; like metadata defines the data that instantiates the metadata; a protocol defines the components of a process and the sequence that becomes reality when it is instantiated. In other words, a business process is an agreed plan which is followed a defined sequence of activities; the plan may include some variants and will possibly allow for some unplanned or unanticipated changes. Correctly defined Meta business rules are valid in both the natural world and business world, all worlds, are universal. It would not make sense to apply fewer rigors to the concept of the Meta Process. 

 The meta-process can simplify process definition and orchestrate the process interaction. And it is a practical methodology to increase process visibility, sight and control and  improve the process management effectiveness.

.

Posted in: Business Process Management,EA,Systems Wisdom