DLS – An ‘Aide Memoire’

The Play Cricket App can be downloaded here

http://www.play-cricket.com/updates2

 

These notes are intended as guidance for umpires in checking DLS calculations. It is recommended that umpires unfamiliar with the App, print this document and the screen shots attached and take them to each game.

As per Moore & Smalley Palace Shield Appendix E, in Premier and Division 1 the home team is responsible for ensuring the Play Cricket Scorer App is available, for all calculations and for displaying the ‘Par Score’ at the end of the forthcoming over and for adjusting this should a wicket fall.

As DL Standard is not designed to work with matches of different length innings. Where, due to a team being bowled out or declaring in the first innings, the team batting second inherits additional overs these are ignored for the purposes of the DL APP calculation. A new target score is obtained and the team batting second then have the overs on the APP plus the additional overs to achieve this score if the time left allows for these additional over to be bowled. Should the game be abandoned, a minimum of 20 overs having been bowled in the 2nd innings, then the final revised target score is again calculated using the APP and ignoring the additional overs inherited.

1^st Innings

During the 1^st innings there is no need to enter anything into the App you just need to note for later use the following factual information if any stoppages occur:

1. The time play stopped, the time play resumed and the adjusted number of overs per team (you would have done this before DLS was introduced anyway)
2. How many overs (and part overs) had been bowled when play was interrupted.

• What was the score (runs/wickets) when play was interrupted.

1. How many overs and part overs remain when play is restarted (derived from i) and ii) above).

Then during the interval between innings you should check that Screen A and B below have been entered correctly.

 SCREEN A 1^st INNINGS (note blue line under ‘1^st Innings’)

1. Ensure the number of overs in the box marked A1 on the attached is the number of overs agreed for each side at the start of the game. This will normally be 45 unless there is a delayed START in which case it will be the number of overs agreed for each innings

ONCE THIS IS SET IT SHOULD NOT BE CHANGED

 

2. At the end of the 1^st innings check the final innings score is entered in the box marked A2 on the attached screenshot.

AGAIN ONCE ENTERED THIS SHOULD NOT BE CHANGED.

Note: The number of overs shown at A2’ will be automatically adjusted by the App should a ‘Suspension Period’ have been entered (see Screen B below).

SCREEN B SUSPENSION PERIODS

1. For every interruption that occurred in the 1^st innings a ‘Suspension Period’ is entered.

2. This information input is factual and is always:
   1. ‘After Over’ – after which over did the suspension in play start (from ii) above).
   2. ‘Runs’ – what was the score at this point (from iii) above).
   3. Wickets’ – how many wickets at fallen at this point (also from iii) above).
   4. ‘Overs Remaining After Suspension’ – how many overs remain in the innings once play resumes (calculated at iv) above).

3. If another interruption in play occurs which results in a loss of further overs, a further ‘Suspension Period’ screen is opened and the relevant information at that point as detailed above is input.

2^nd INNINGS

In the 2^nd innings for each interruption in play the process is the same except that the number of over remaining will be calculated by working back from 8pm.

As both teams will want to know the revised target before play resumes after a second innings interruption, you will need to check the Suspension Period details have been entered correctly  BEFORE play recommences. The details required and the screen input are exactly the same as detailed for the first innings above.

SCREEN C 2ND INNINGS (note blue line under ’2^nd Innings’)

1. The ‘Target’ overs and score will have been calculated by the App (note this may be higher, lower or the same as the 1^st innings score actually entered).

2. If any interruptions in play leading to a loss of overs in the 2^nd innings occurs, check that a ‘Suspension Period’ had been entered. This is done in exactly the same way as outlined above (Screen B Suspension Periods).

3. Again should further interruptions leading to a loss of overs occur further ‘Suspension Periods will need to be entered.

Note: The Target Score will be recalculated automatically after each interruption is entered.

PAR SCORE

 

As play continues in the 2^nd innings, particularly if weather threatens an abandonment, it is likely that both teams will want to know how they stand in relation to the Par Score (i.e. is the team batting second ahead or behind where they need to be).

Clubs have been reminded that it is their responsibility to display the Par Score on the scoreboard over by over and so the umpire should not be required to use the App while on the field.

If the game is abandoned after 20 overs and you need to check the Par Score at the end of the game to determine the result:

At Screen C3 enter the number of overs completed and the wickets that have fallen. The APP will then calculate the Par Score.

Note:

To win the team batting second must have scored at least 1 more than ‘Par’.

If they score exactly the same as ‘Par’ it is a tie.

If the team batting second score less than ‘Par’ the team batting first have won.