Process Mapping and Modelling Standards
Common “Levelling” Terminology
Generally only the 4 levels previously described should be required, however different projects and initiatives may wish to express processes in different ways in order to aid audience understanding or facilitate analysis.
- There should however be a common understanding of each level. i.e. Level 2 only ever means process model.
- The level number and name of the process should always be referenced in the title to allow ease of identification and understanding.
Level 0 = Organisation level. The organisational structure of different functions and services within the University.
- Level 0 diagrams illustrate organisational relationships.
- If required sub levels may be used.
- g. Level 0.1 may indicate how teams are aligned within a specific Level 0 Business area such as Schools within a Faculty.
Level 1 = Process Map. The dependencies between different processes upon each other.
- Level 1 maps illustrate dependency NOT flow.
- If required sub-levels may be used.
- g. Level 1.1 may indicate inter-dependent sub-processes within a large Level 1 process such as “receive application”, “assess application”, “communicate decision” etc.. in the Level 1 Application process.
Level 2 = Process Model. The flow of tasks which join in sequence to form the process.
- Level 2 models illustrate process flow.
- If required an infinite number of sub-levels may be used.
- g. Level 2.1 may indicate “sub-activity” within a task element on the process model. This may be used when the sub-activity is particularly complicated or made up of a number of small individual tasks.
Level 3 = Task Level. The lowest level of detail.
- Level 3 describes the detail of the task as a set of actions or if required as a process model.
- As a task can only be done by one person, in one place at one time, this is the lowest level of detail and cannot be broken down further.
- Rules, decisions and control points should be documented.