Post Match Remediation Framework

At Australian Cricket - We all have a responsibility to ensure that match analysis data through the Data Warehouse is to the highest of quality - This ensures that we have consistent and reliability in what we provide our stakeholders.

As we work in a federated model - it is important to outline and understand the different responsibilities we have in creating a rich & reliable data ecosystem.

Preparation - Pre Match

There are two critical things that you can do to ensure that your database is in top condition for matches

1. Analyzer Updates - It is important to ensure you have updated to the most recent version of analyzer prior to importing matches that you are responsible for. Database conversions get done periodically to clean player profile information (eg - merging duplicate players) and exporting data to the cloud with a locally outdated version of Analyzer can overwrite fixes already in place in the data warehouse.
2. Sync with Cloud
   • In addition to the above, it is important to sync your local database with the cloud for any minor changes to all reference tables - in particular players
   • This can be done within the Reference > Players function and clicking the "include cloud" toggle once refresh you can scroll across to the local vs cloud comparison and multiple click will bring all the differences to your database to the top of the table.

Yellow - Specifies that you do not have the player in your database and should import where relevant

Orange - Indicates there is a difference between local v cloud - use the local vs cloud comparison to understand the difference, then import where relevant

White - suggests player is local to your database but not the cloud - consider is this player within the player database already before using.

• Rule of thumb before creating a player profile - reflect whether the player has been part of a performance pathways (eg. U19s or U17s Championships) as this is an indicator that they will be in the system.

If you are unsure on any of the steps, please reach out to Trent or Dene.

Post Match Remediation

1. Process

It is important to understand the timings are important for these changes, as deadlines are real, however we do not want to rush quality assuring data.

Before initiating in data remediation please keep in mind the below.

• Is the coding status of the match final?

• Has more than 48 hours passed since the match commencement?

If the following criteria is met follow the framework below should be used to help with the remediation process.

2, Monitoring & Review

In addition to the above processes, CA Performance Data & Tech staff will be reviewing series as part of the Decade of Data project - this will be done periodically to ensure that data is better maintained and consistent throughout.