Overview
It can be a complex task to monitor the training load from multiple parameters across multiple athletes at the same time. In many cases, a practitioner might want to know simply 'how much' or 'how hard' did their athletes work on a given day. To simplify this process, we can combine several parameters and express them as a percentage of a matchday (MD) reference load in various forms.
In the Reporting section of the OpenField cloud, the 'Volume', 'Overall', and 'Intensity' gauge charts will display the percentage load scores of a selected activity(s) output compared to the athlete or team's matchday benchmark (average) data. Other tagged training days (MD-2, MD-1 etc.) can also be selected for comparison, allowing the practitioner to assess the current activity's outputs relative to training benchmarks over time. In total there are 33 average sets with a comparison per activity tag from MD-5 to MD+5 and averages for team, position and athlete.
Selecting different reference values will result in the gauges showing load scores of the current activity compared to the selection.
Within individual athlete charts and tables, the aim is to provide a measure of how hard the activity was for an individual athlete. This means the volume, intensity, overall and percentage scores are calculated as follows in the example of MD-1:
-
If an athlete has completed a “full”, ”MD-1” activity then they will be compared vs their own average for MD-1.
-
If not, but there is another athlete in the team who has completed a “full”, “MD-1” activity in the same position then the athlete will be compared to their positional average.
-
If no positional average, but there has been any single athlete that completed a “full”, “MD-1” activity then the athlete is compared to the team average.
-
If none of the above, then they will revert to the Initial Benchmark described above.
How are these scores calculated?
Multi-Mechanical Modelling
To calculate these scores, we utilise Catapult's Vector Core multi-mechanical model which has been adapted from the Owens, 2017 model and is similar to that of former Aston Villa Sports Scientist Jack Sharkey's model, explained in this video here.
The model takes multiple parameters and groups them based on their application to volume or intensity. To normalize the data and make it digestible to coaches all parameters are divided by matchday loads and represented as percentages.
Calculations
Volume
Average((Distance/ Benchmark Average Distance), (HS Distance/ Benchmark Average HS Distance),(Accel+Decel Efforts/ Benchmark Average Accel+Decel Efforts))
| Parameter Name | Calculation |
| Distance | Distance |
| HS Distance | HI Distance + Sprint Distance |
| Accel+Decel Efforts | Acceleration Efforts + Deceleration Efforts |
Intensity
Average((Dist Per Minute/Benchmark Average Dist Per Minute), (HS Dist Per Minute/Benchmark HS Dist Per Minute), (Accel+Decel Eff Per Minute/ Benchmark Average Accel+Decel Eff Per Minute))
| Parameter Name | Calculation |
| Dist Per Minute | Distance / Duration |
|
HS Dist Per Minute |
(HI Distance + Sprint Distance) / Duration |
| Accel+Decel Eff/Minute | (Acceleration Efforts + Deceleration Efforts) / Duration |
Overall
Volume x IntensityHow to include or exclude athletes in activities from the comparison?
In order to ensure the ability to derive accurate matchday and training average values, consistent tagging is needed. Therefore, for an athlete to be included in the model calculations, there must be a 'Full' and 'Day Type' tag applied.
For example, if an athlete has been tagged as 'Full' participation on matchday -1 (Day code = MD-1), the athlete's data will be included in calculating the benchmark values for said day. If the athlete is tagged as 'Part' or 'Rehab', this data will not be included in order to maintain integrity across the wider benchmarking data set.
See below for detailed breakdown of tag options:
Activity Participation Definitions
|
FULL |
Athlete completed the whole activity and should be included in averages | REHAB | Separate activity for the purpose of recovering from injury |
| PART | Player completed part of the activity be it finishing early or as a substitute who did not complete full match/activity | INJURY | Athlete injured in this day |
| MODIFIED | Was involved in the full training activity but had modified loading | OTHER | Catch all for any other reason someone may want to rule out an athlete of an average set (eg Device errors) |
Day Codes
| MD | MD+1 | MD+2 | MD+3 | MD+4 | MD+5 | Number of days leading to a game. User has discretion to decide if days from or days to is more important for any given activity | |||
| MD-1 | MD-2 | MD-3 | MD-4 | MD-5 | |||||
Summary
Multi-mechanical analysis combines parameters to provide greater insights of activity volume and intensity relative to benchmarks or matchday averages. The charts are available in all areas of the platform and by default compare team data to the team benchmark for all areas apart from the athlete charts and tables.
Related articles