Business Process Management and the Web
Taking BPM to the Web
Now that the acceptance of the need for business process management (BPM) software is becoming mainstream, the demand for the technology has reached the critical mass required to force software vendors to heed their customer’s demands for “zero latency” access to information.
BPM is rapidly headed to the web and the timing couldn’t be better. There aren’t many CEO or CFOs left who are willing to go to jail for the sins of omission and, if it did nothing else, an investment in BPM would be worth it just to stay ahead of the requirements of Basel II and Sarbanes-Oxley.
In reality there are any number of reasons why BPM makes sense in a competitive environment where sales are being squeezed by imports, labor costs are rising, and every business process is finally starting to get a real price tag attached to it.
Web-enabled BPM software offers the first real promise of seamless integration with existing ERP systems and the great hordes of legacy data that most organizations have hiding in their electronic closets.
One of the most pressing issues facing developers of BPM software is finding a standard and sticking with it. In a flurry of confusion, reminiscent of the Betamax vs. VHS conflicts of years ago, various vendors are circling their wagons around different standards.
J2EE (Java™ Platform, Enterprise Edition) is a strong contender because of its widespread availability and reputation for compatibility with XML, EJB, JSP, XML and the rest of the usual acronym suspects including the lowly JavaScript.
XML is enjoying wide acceptance as a genuinely platform independent standard for data representation.
Web Services and Service Oriented Architectures, based upon SOAP and WDSL are fully supported by major players including BEA, IBM, Sun and Oracle.
And, of course, Microsoft is a player with their .Net initiative which also embraces XML, SOAP and WSDL.
All of this not withstanding, many industry watchers have their eyes on an emerging standard known as Business Process Execution Language (BPEL4WS), an XML-based language which is specifically designed to handle task-sharing in a distributed environment by utilizing a variety of Web services. Although not available in any shipping products, it is garnering strong support within the industry.
Another contender in the race to be the preferred platform is the Business Process Modeling Language (BPML). This is a meta-language, along the same lines of XML, which is specially designed to model business processes.
Two “Soon to be thought about more deeply” standards wanna-bees are the Business Process Modeling Notation (BPMN), which offers a graphical method of defining business processes using a Business Process Diagram (BPD), and the Business Process Query Language (BPQL) which utilizes a business process server and a process repository to execute and deploy queries.
If all of these emerging and soon-to-be-emerging standards are too much for you to keep track of, you’ll be happy to know that an organization exists which is championing the cause on your behalf.
According to their web site, the Business Process Management Initiative “embraces existing standards where appropriate, working with complementary standards bodies such as the OMG, WfMC and OASIS. In areas where standards are lacking, BPMI focuses on standards development to support the entire life-cycle of business process management - from process design, through deployment, execution, maintenance, and optimization”.
While it may be fun to keep track of all the three and four letter acronyms, making the wrong standards decision won’t bring as many chuckles from the boardroom. IT executives and managers need to make strategic decisions now while depending upon standards which are subject to change in the future. The cost of making the wrong decision can be high, but the cost of making no decision at all is even higher.
There is nothing more powerful than an idea whose time is come and this is the time for business process management software to integrate with the web.