Role of the Reviewer

Pre Match

• Updating Match shell with named squads to cloud (within 24 hours of matches)
• Include pitch number that the match is being played on

Within 45 mins of match

• Provide Teamsheets & M3u8 Link to coder
• Confirm connection of Receiver

Before first delivery

• Confirm which end (North/South) the Striker is stand for first over and communicate to Coder

During Match

• Analyst to monitor coding standards and accuracy as the match and coding progresses and advise change required or edit the detail as required.  The Reviewer should communicate if sub-standard coding or errors are persisting via WhatsApp.

Using Collaborative Coding

• During the match the reviewer has the ability to effect downstream workflow to reciever computers by the ability to fix the below

Batting

- Beehive, Pitch Impact, Shot Quality, Striker Intent+ Movement, Stroke

Bowling

- Ball Revolutions, Ball Speed, Bowler Variation

Fielding

- Grading of Catches, Runout, Stumping attempts, Fielding layouts

Other

- Special Buttons enabling up to 16 specific areas for given team

Post Match

• Once final txt file is received from coder, review should
• Ensure that Clean Health Check has been completed
• Check all dismissals and all details are correctly coded as well as all attempted catches, run outs & stumpings for grading evaluation
• Ingest both Opta and Hawkeye overlay where required.
• Change status of game to final and export to cloud