To err is human. Multiple reasons range from a lack of experience to an over-optimistic perception of a current situation. To make decisions 100% fool-proof a review and approval management (DAM) shall be implemented.
In conventional project management, the price of DAM is huge: roughly 50% more resources and time shall be allocated to the project execution.
Contrary to expectations, digitization raises the criticality of DAM as rise in complexity of the decisions left for the human being sees no decline.
DAM is not a platform for multiple stakeholders to give feedback or discuss suggestions. Its task is safeguarding the project against catastrophic decisions. The DAM's closest engineering analogy is SIS - a safety instrumented system. It takes automated action to keep a plant in a safe state or to put it into a safe state when abnormal conditions are present.
DAM's implementation by crenger.com is focused on the following points.
- mapping topics to reviewers and approvers
- auto-assigning reviewers and approvers to the project tasks
- monitoring and controlling task approvals
- providing review and approval metrics
The topics of the first point include engineering, procurement, the project schedule tasks, and file submission. Once the topic is mapped to a project team member and the business rule is created, the software applies it when conditions are met.
Engineering topics include P&ID and item groups, general documentation (specification, engineering guidelines, etc.), and document types included in the project handover packages. The engineering approvals interface is shown below.
If the same project team executes a series of projects, all the approval rules from the first project to the next may be copied by a button's click.
Procurement approval rules work similarly except for one point. They are initially auto-created using the procurement role assignments built before the project commencement as approval is part of an assignment. An example of the roles tree is shown below.
An interface for the schedule's task approval (shown below) maps a team member to a work package (WP) of Work Breakdown Structure (WBS). The software broadcasts the mapping on actual tasks of the schedule.
