Concrete Benefits in Using QPR during Process Consulting Assignments
With the use of QPR during Process Consulting Assignments, the entire focus shifts to delivering the process models and recommending benefits, and removes the overhead of managing the process repository and associated attributes of the process such as job descriptions and responsibility matrices.
The following is an example of deploying a process consulting assignment using QPR and associated benefits.
Setup Phase
- The first step will involve creating a template on QPR ProcessGuide which contains the relevant process framework for the assignment. This will consist of the following:
- Existing Organizational Hierarchy (these will be displayed as swim lanes on the process map)
- Process Hierarchy
- Standard Modeling Notation to be used in the assignment
Benefits:
- This template may be used for other similar consulting assignments as QPR ProcessGuide allows new models to be used based on existing templates/models.
-
QPR ProcessGuide security options, ensures that Team Members will work within this process framework and this will lead to a uniform delivery. For e.g., as the hierarchy is already defined, Team Members will find the reporting structure easily available. There will not be inaccuracies due to misspellings or abbreviations (e.g. Mktg. Manager instead of Marketing Manager).
- Enforcing a standard modeling notation ensures that even new team members will be able to quickly understand the modeling framework.
- This template is then used as a base model to which all process model models to be built are linked as child models.
-
- Setting user rights for process modeling - QPR ProcessGuide can be used to plan a rapid deployment. Using the advanced user rights, different team members can be:
-
- Assigned the rights to modify or view different main processes and sub process structures.
- Sensitive processes can be protected with rights being assigned to selected team members and other members having no access.
Benefits:-
-
- Sensitive information is protected through user rights, although with appropriate permissions, this can be viewed along with the entire model.
- Team members can work on their allotted sections, and if provided view access to others work, will be able to get a “big picture” view of the processes very quickly. This will lead to better documentation of the processes and process alignment.
- Executing the assignment - At the team level the following would be the steps taken on QPR ProcessGuide to complete the assignment.
-
Execution is usually very quick as the time is spent on creating process structures and QPR ProcessGuide generates other associated information which would otherwise need to be created.
a) The Process diagrams are first created by placing the responsible “organisation elements” onto the process map.
b) Sub Processes and activities are then arranged based on inputs from the Process Owner.
c) Existing documentation and procedures can be attached to the process maps creating a front end repository.
d) Processes can be version controlled based on revisions and discussions with the customer.
e) Full audit trail logging at the process model level and the individual sub process level enable accountability for changes made to the process model.
f) Process Models can be “checked out” for use offline from the server, enabling full process modelling capabilities while at the customer’s site. Once the team members are back in office, the process model will be “checked in” to the server and changes made will be replicated.
g) Team leaders and Project Managers get to view the latest available process model on the server with all associated linked documents and other details.
h) Model versions can be created to manage changes and archiving easily.
i) Attaching document templates. It is relevant to attach all document templates to a process step, or even add policy documents to main or sub processes. This is done using the Information Items functionality, which ensures that the process repository is enriched with the correct and latest versions of the documents, which may be linked from existing document repositories such as Microsoft Sharepoint. These can then be listed as a hierarchy.
j) Identifying and documenting risks. It is also possible to layer different attributes on the process map, such as risks and control points to make the process maps multi-dimensional as shown below.