Analyst firms predict the Business Process Management (BPM) market growth rate at 15 percent to 20 percent, which far outpaces the 3 percent to 4 percent growth rate predicted for ERP and CRM markets. BPM is rapidly growing and becoming the technology for modeling, optimizing and automating business processes. A number of research reports also show that BPM yields impressive bottom-line and top-line benefits to organizations trying to compete in a global economy. These reports and case studies provide significant justification to support the continued and rapid adoption of BPM. BPM will continue to accelerate this momentum by expanding its ability to model, manage and optimize the business process flow in correlation with systems, employees, customers and partners within and beyond corporate boundaries.
Beyond enjoying inherent advantages, companies that realign their organizational structure to exploit BPM’s new cross-functional capabilities benefit as well. BPM bridges application and enterprise silos, driving companies to operate around a set of business processes as opposed to business functions or specific applications. BPM allows this to occur incrementally rather than starting from scratch – it is not an “all or nothing” approach. The ability to incrementally deploy is based on business needs, not traditional release or upgrade cycles. More importantly, ROI can be delivered and measured throughout the implementation.
Technology and business drivers for enterprise application development should focus on providing an environment where better business applications can be developed with less effort. Business applications should closely align to business processes that can be readily adapted to the changing nature of business processes.
The newest and best approaches to this interoperability and integration challenge are Service Oriented Architecture (SOA) and the Web services technologies. The bottom-up view of SOA sees different business applications exposing their functionalities through Web services. SOA creates standard, consumable services that are mapped to business processes. Further, SOA enables rapid BPM as each atomic business process will call a service or human activity.
However, developing Web services and exposing functionalities are not sufficient alone. A way to compose functionalities in the correct order and define processes to make use of exposed functionalities is needed. The obvious preference is a relatively simple and straightforward way to define such processes, particularly because we know that business processes change often and need to be modified easily.
-1-