One of the more common phrases in corporate life is: "Close the loop." This mantra refers to completing an improvement cycle by putting into play the insights gained by analytical processes.

Mantras are words that the Indian religions believed are ‘considered capable of creating a transformation. Closing the loop today is more possible than ever, in part due to the convergence of two enterprise disciplines: Business Intelligence (BI) and Business Process Management (BPM).  This is happening since they both originate from the same source – the business architecture and/or engineering.

A unified approach or architecture often outputs an integrated system – take for instance Business Model integration.  The Business Model (or architecture if you will) generates both the process model and the data model.  It being the origin point, they will both integrate at the lower points. The process model has the ‘business-ezze’ and pseudo-code of the business rules (usually implemented as applications).  The Data Model is also the sourced by the Business Model and outputs the logical / physical and metadata associated with each data attribute or element.
The Business Model is a framework for creating tremendous value in an organization. It lowers the cost incurred in the modification of business logic, creates a ‘single source of truth’, rules are externalized and easily shared with multiple applications (changes can be made faster and with less risk), and shortens development time while improving efficiency.
Together, these disciplines grew independently with tool-sets engineered to cater to each – but they still retained their common starting point.  It would only be natural to see then that the convergence of these separate disciplines would eventually happen – just as the convergence of Services Based Architectures [SOA, EDA] and Business Intelligence [BI].
The systems engineering of business processes is an art with an associative language that all must speak in order for understanding – we are slowing approaching this phase of growth. I prefer a simple approach that has a lot of teeth to it (meat on the bones so to speak).
The Business Process Management lifecycle consists of: Requirements Capture (current state), Design (current and future state), Modeling, Execution, Monitoring, Optimization and back again. It is a circular path just like Business Intelligence provides information that in turn provides insight for future changes.
This lifecycle requires governance and one should never separate the two – for without the governance (management and upkeep of the assets), they will lose their value.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access