If this is your first time creating a Scorecard then read our Steps to Creating a Scorecard.
Understanding scorecard metrics
View a sample scorecard here and find out more about what each of the key metrics mean below:
An overall Disruption Management score is an average created by taking the Journey Times Slower and Below Delay Limit to create an overall score (see full calculation example below)
Journey times - journey times through occupation were slower compared to baseline. % slower journey time is the average % change in time when compared to the baseline period over occupation hours
Below delay limit - The percentage of time that the project journey time stayed below the Delay limit. % time KPI achieved is the % of occupation hours in which no routes are in breach of KPIs set on routes
Potential Occupation - There was potential for a further Xhrs/wk of occupation or X hrs in total. Potential occupation hours is the period around the working window in which there was little delay according to the planning view, multiplied by days in the scorecard
Incidents - The number of incidents recorded in annotations. Mooven annotations that have recorded incidents are totalled for that period.
Delay peaks against baseline - delay peaks are the average max journey time over defined peak windows (e.g. AM 7-10am, PM 3-6pm) and the difference between that and the average max during the baseline period
Overall Disruption Management score calculation
The overall Disruption Management score is created by taking the Journey Times Slower and Below Delay Limit to create an overall score.
Journey time - Journey times through occupation were slower compared to baseline
Below delay limit - The percentage of time that the project journey time stayed below the Delay limit
How this is calculated:
This is similar to a weighted average disruption score. A perfect score of 100 would occur when 0% of times the journey times have been slower than baseline and 100% of the time the project journey time stayed below the Delay limit.
Each of these two measures is equally weighted. For example, a 10% change in either metric would take 5 points off the total Disruption Management score.
An example in practice is
Journey times through occupation were 15% slower compared to the baseline
The project journey time stayed below the Delay limit 97.4% of the time.
Disruption Management score = ((100 - %slower*100) + (100 * below_delay_limit_%))/2
So in the example below: ((100 - 15) + (100 * 0.974))/2 = (85 + 97.4)/2 = 91.2%
Reach out if you would like a regular scorecard sent to your inbox either weekly or monthly, we are happy to send this through to you.
As a note, our scorecard is still in beta and will be looking for ways to improve upon it and automate the workflow and report features even further. Any feedback you have along the journey we would appreciate.
Mooven’s customers use Scorecards to gain:
Unified information about the impact a worksite is having: bring together all KPIs and data sources from your Mooven platform site.
Measurement of the KPIs that matter. Your scorecard reflects the specific key performance indicators (KPIs) that matter most to your infrastructure delivery. See a definition below of what each of these are.
The ability to easily identify trends, outliers, and areas for improvement at a glance and generate a meaningful customized synopsis at the end of the report highlighting deeper context, key trends and exceptions in the data.
User-friendly Interface: Mooven's software provides a step-through process to generate a scorecard report.