BPM and DPM: What’s the Difference?

Since its birth in the early part of the century, BPM (Business Process Management) technology has become widely deployed and a key part of large-enterprise IT infrastructure. Traditional BPM deals specifically with predictable, structured processes with well defined steps that lead to understood conclusions. DPM (Document Process Modeling) is a subset of business process management dealing specifically with the automation of document generation processes.

Take, for example, a contract origination workflow, which could be triggered out of, for example, a CRM. A dataset stored in the CRM could be passed into the workflow for the purpose of generating a contract, along with collateral documentation, and then routed to various knowledge workers for approval, modification, or rejection. However, depending on the complexity of the documentation, most BPM suites simply lack the automation sophistication to generate the documents within the larger business process. That’s where DPM comes into service.

Enterprise-grade document process modeling takes a document-first approach, meaning that business rules are coded into the text of the document(s), accounting for all relevant permutations. Simple variables are inserted with point-specific formatting attributes added. Computed variables are also built and inserted at necessary merge points. Optional text blocks are defined with conditional logic, etc. Then, a sequence of interactive forms (an interview) is created to gather all the variable information necessary to generate the document(s).

With the document generation process fully modeled, it can run independently as a document generation workflow, or it can be incorporated as a component into the larger workflow. To see a document process running inside a larger workflow, check out Thomson Reuter’s Interactive Decision Tools on Checkpoint. Built on HotDocs, the industry leading DPM, the recently released TR product helps tax lawyers and accountants navigate complex legal statutes and regulations to arrive at legally valid opinions for their clients. The HotDocs-based system then generates necessary documentation, such as formal opinion documents and correspondence.

In the contract origination workflow mentioned above, the CRM dataset could be passed directly into the document process interview and would appear in the context of the interview as “answered questions.” The interview would present all other questions necessary to complete the documentation set.

Enterprise-grade DPM systems are designed to handle any documentation set, no matter how large or complex. Such systems should have platforms for both on-premises and cloud-based deployment, and should have highly evolved APIs that will allow for integration into any automated process. Furthermore, a DPM system should work equally well in ad hoc and unstructured-process environments, such as those provided by today’s highly sophisticated adaptive case management systems.