When you run a schedule there are no checks automatically done to determine whether each block is physically available for scheduling. For example, the previous activity may not have been completed or blocks above it may not have been mined. Checks such as these are done after the schedule has been run, using the Schedule Checker. The logic for the Schedule Checker comes from the block dependencies and the activity precedences.

Block Dependencies

For each scenario you are able to create Dependency Rules Sets. These rules define which blocks must be mined in order to mine other blocks.

The Schedule Checker can identify and report where the block dependencies are not followed in the schedule.

Activity Precedences

When you define your productive activities, you can also specify activity precedences. These precedences define the order in which the activities should be mined within each block and they also control which activity(s) releases which other activity(s) within each block.

The Schedule Checker can identify and report where the activity precedences are not followed in the schedule.