Binocs documentation
Binocs website

How the algorithm uses the demand dates

Tracking items (requires follow up)

Requested start in the past

  • Demand line will be planned starting from the horizon start

remark: by not setting tracking items in progress, backlog is created. These demandlines will be re planned completely

Requested start in the past - status: In progress (actual start in the past)

  • Demand line planned from the actual start
  • All weeks in the past are planned unconstrained, but aren’t shown in the analyzer

2 possible cases:

  1. All weeks in the past (e.g. actual start 3 weeks in the past and the service has a leadtime of 2 weeks)  demand line is planned in the past and not shown in the analyzers
  2. A number of weeks in the past (e.g. actual start 1 week in the past and the service has a leadtime of 3 weeks)  last 2 weeks will be planned

Requested start in the horizon start week or further in the future

  • Demand line planned from the requested start

Forecast items

Requested start in the past

  • Demand line planned from the requested start
  • All weeks in the past are planned unconstrained, but aren’t shown in the analyzer

remark: the weeks in the past are automatically consumed

Requested start in the past and Requested finish in the past

  • Demand line is not planned (it’s consumed)
  • No workload in the workload analyzer

Requested start in the horizon start week or further in the future

  • Demand line planned from the requested start