So what is the difference modelling and mapping a process? Many people use these terms interchangeably without realising the subtle differences. My definition of process mapping is simple; it’s a diagramatic representation of the flow of tasks within a process. Within the context of Analyzer Direct, the process map is created using Microsoft Visio as the drawing tool. The addition of resources and timings to each of the tasks within the process create the model.

If we take a simple process which has four tasks, the process map drawn using Business Process Modelling Notation (BPMN) would have a start shape, four task shapes and an end shape. Each task would be given a name and the map could be quickly generated using Microsoft Visio. This may be fine to include in a document describing a simple processes within a department, where additional text could be included to further descibe each task. But in terms of Analyzer, the addition of resouce information to each of the tasks such as who carries out the task and how long it takes to complete the task enables a true process model to be created.

Now, if you know how long each task takes to complete and who is responsible for performing that task, the next logical step is to calculate the total process time, for each resource, based on the the number of times the process is completed. We refer to this number in Analyzer as the process volume. As you build a process model using Analyzer, the software automatically calculates the total resources required, based on your process volume. 

Before you can use a resource with a process model you need to provide Analyzer with information about the resource, including unit costs. So as Analyzer calculates the resources required it can also determine the total cost for the process, and for each individual resource. To understand how this works in practice, why not review video 3 from the tutorial programme, Cost and Resource Allocation.