The hottest business process management past, pres

  • Detail

Business process management: in the past, now and in the future, information technology has changed the business processes within and between enterprises. More and more workflow operations depend on information systems driven by process models, such as workflow management system Staffware, enterprise resource planning system sap and ban, and there are also special information systems in many fields

it is difficult to imagine an enterprise information system that has nothing to do with the process. Although the use of information technology to help business process management has long been hyped by consultants and software developers, a more basic method has been ignored. Until the 1990s, researchers began to study the basis of business process management system. As a result, there are many problems to be solved. In addition, the development of new technologies such as web services has also led to new problems


to discuss workflow management in a suitable environment, first look at its development trends. In the 1960s, information systems were based on small operating systems with limited functions. Since there is neither general nor domain related software, these systems are mainly composed of specific application programs. Since then, software products with new functions have appeared every year. Today's operating system provides more functions than the 1960s, and the database management system provides the function of customized applications

this trend leads to a shift from program design to the integration of complex software systems. The challenge is no longer to program a single module, but to connect the four layers of software modules to make them work together. Another trend is the shift from data to processes. In the 1970s and 1980s, data-driven methods dominated. Information technology was mainly used to access information. As a result, data modeling became the starting point of information system construction

business process modeling is often ignored, and the process has to adapt to information technology. The development of management theories such as business process reengineering reflects the emphasis on process, which makes system engineers tend to be process driven. The recent trend worth mentioning is the shift from careful planning and design to redesign and organizational growth. Due to the ubiquity of Internet and its standards, information systems are constantly changing. Few systems are built from scratch. Some existing applications are often used in new systems, making software development more dynamic

business process management system is a process oriented information system, that is, a system that goes beyond the automation of a single task. Such as workflow management system Staffware, MQSeries and cosa, and case processing system flower. It is worth noting that the main ERP system also provides a workflow management module. The workflow engines of sap, Baan, PeopleSoft, Oracle and JD Edwards can be regarded as integrated business process management systems

the idea of independent business process management into a single component is consistent with the above three trends. Business process management system can avoid solidifying workflow in customized applications and support the transformation from program design to application assembly. It also supports process oriented, process redesign, and organizational growth. The current workflow management system can be used to integrate the existing applications, and can only change the flow of the flow chart to match the human bone; It can improve the physiological compatibility between the composite and human body

workflow management system

although WFMC has made great efforts, workflow management systems based on different paradigms still use many languages and concepts. Most products use a proprietary language rather than a tool independent language. Some workflow management systems are based on Petri s, but add product related extensions and restrictions. Other systems use a completely different mechanism. For example, IBM's MQSeries workflow uses active and passive threads instead of token delivery. The difference between different tools is obvious. One of the reasons why workflow specifications can not reach a consensus is the diversity of business process description methods

the lack of general organization "theory" and standard business process modeling concepts explains the rationality of the differences between workflow languages. More importantly, the comparison of different workflow products promotes the release of products rather than criticizing the language ability of workflow. With the joint efforts of Eindhoven University of technology and Queensland University of technology, a new system for comparing and evaluating workflows has been developed. This framework is based on a comprehensive set of patterns and considers a more objective evaluation of workflow management systems

we have collected about 30 workflow patterns and compared 15 workflow management systems (COSA, visual workflow, Staffware, verve workflow, i-flow, concert, changengine, SAP r/3 workflow, Eastman and flower) with 20 of them. If you need more information, please visit

composition languages

two trends have emerged in the field of e-commerce at the same time, which have triggered opportunities and pressures to realize cross organizational business process automation. One trend is the driving force of technology, which has achieved the goal of gradual improvement of the industrial system. It is derived from XML based standards and Internet enabled technologies. Another trend is the need to improve process efficiency from a business perspective. After the foam, it became urgent to take full advantage of the potential of Internet technology by automating cross enterprise business processes. The goal of Web services is to use XML and Internet integration to publish, locate and invoke applications on the web

a typical example of a network service is the Galieo system, which connects more than 42000 travel agents to 37 car rental companies, 47000 hotels and 350 travel contractors at each startup. In order to truly integrate cross enterprise processes, using standard messages and protocols to support simple communication can no longer meet the requirements. Business communication requires a long-running interactive process driven by an intuitive process model. This requires web services component languages such as BPEL4WS, wsfl, XLANG, WSCI, and BPML

the development using network service component language is mainly driven by software providers such as IBM, Microsoft, sun, BEA, sap and intalio. As a result, there are many standards with duplicate functions. When you consider this more carefully "When our partners are very satisfied with the prototype parts produced, they are obviously based on existing products. For example, wsfl is basically a replica of IBM's flowmark/mq series workflow language. The standards involved by many software suppliers are often a compromise of different views. Such standards lead to imprecision and unnecessary complexity. For example, XPDL of Workflow Management Alliance enables software suppliers to have their own interpretation standards To make a standard useless. BPEL4WS incorporates wsfl and XLANG standards, which makes the language very complex

through these observations, it is useful to find some objective measures to compare network service component languages. For the control flow of these languages, some results of workflow research can be used. One way to compare standards such as BPEL4WS, BPML, WSCI, XLANG, and wsfl is to use the workflow pattern on. Recently, on the basis of 20 basic workflow patterns, this site has added comments on BPEL4WS, BPML, WSCI, XLANG, wsfl and other languages


bpmi is one of the organizations that put forward network service component standards. Open specifications such as business process modeling language (BPML) and business process query language (BPQL) are defined. They use the upcoming enterprise process management system (BPMS) to promote the standardized management of e-commerce processes, just as SQL uses the existing database management system to realize the standardized management of enterprise data

network service standards similar to SQL are ambitious goals. As history shows, such standards will not appear in the process of manufacturers promoting their products. The entity relationship model proposed by Chen and the relational model of Codd promoted the production of SQL and other languages. Although there are process modeling technologies (compare.Petri and process algebra) that integrate representation, simplicity, and formal semantics (Petri and process algebra), the software industry ignores these technologies. As a result, the world faces too many standards, which are mainly driven by specific products and/or commercial interests. The only way to end this situation is to ignore standard proposals that do not use existing process modeling techniques. This makes software providers focus on practical problems rather than new ones

original author: wil M.P. van der Aalst, famous workflow expert and Professor

Copyright © 2011 JIN SHI