Quantify a Process in Skore

Quantify a Process in Skore

Why cost a process

Understanding the cost of a process helps you make decisions about what and how to change it. For example, if you are looking at automating a part of a process you can use this feature to understand the opportunity cost saving that could be made by automating. This can then be used against the cost of implementing the technology to ensure there is sufficient return on investment.

The Quantify module also helps analyst to understand where bottlenecks exist in the process, how delays impact the efficacy of the process and what is the impact of changes to roles and other costs.

How does this work

Step 1 : map process activities

You first need a good understanding of your process to be measured. 


Note on RACI or RATSI

To calculate the total cost of a process, only the first role of an activity box is taken into account.

If you would like to have several roles taken into account you need to enable RACI or RATSI.

When using RACI, all roles with an "R" will be taken into account for the cost of an activity.
When using RATSI, all roles with a "T" will be taken into account for the cost of an activity.

Step 2: assign volumes & durations

  • Open the quantification on a process box by clicking on the paperclip
  • Fill the values
    • Volume: how many items are processed every day
    • Duration: how long, in seconds, does it take to process an item
    • Lead time: how long, in seconds, does an item "waits" before being processes. This
Units: it is not yet possible to change the units for the activity based costing.

Step 3: assign cost to roles

In the role manager, enter the cost for each role.

Step 4: Review costs

The cost is based on 7h working day 
Skore will crunch the data of your process and display various reports helping to better understand the cost involved in a process.

    • Related Articles

    • Manage Process Stylesheets in Skore

      Feature available to: Admin (Create stylesheet), Editor (Select stylesheet to use on a process) Stylesheets are one of the tool to create consistency in your process map. Stylesheet will apply to boxes and lines of a process. The define the look of ...

    • Decision boxes / diamonds in Skore

      Introduction Users that are new to Skore may ask how they draw, or represent, a decision diamond commonly found in other types of process mapping. Skore is based on the Universal Process Notation (UPN) which doesn’t use decision diamonds but does ...

    • Process Owner

      What is a Process Owner? In Skore, processes can have a Process Owner. This is not mandatory but a recommended practice to ensure the right ownership of the processes. Setting a Process Owner also helps to organise your processes and maintain them ...

    • How to group activities in Skore

      What is it? In Skore you can group activities, this lets users visually see that some activities have a different context and may need to be interpreted differently compared to the wider process. Below is an example of how to use grouping in a ...

    • Process Revision History

      Feature available to: Member • Editor • Admin What is process revision history? Let's start by defining what we mean by a revision in Skore. A revision in Skore is a snapshot, or back-up, of a Skore process at a point in time. Revisions are created ...