Introduction

The JS7 - Daily Plan Service runs on a daily basis to create orders and projections for the daily plan. Inconsistencies between inventory objects and objects deployed to a Controller can prevent orders from being submitted. Such problems are logged by JOC Cockpit, however, they might slip a user's attention. Checks are intended to be executed at an ongoing basis to detect inconsistencies in the daily plan as early as possible.

Checks

Settings

The JS7 - Daily Plan Service creates submissions of orders based on JS7 - Settings for the Daily Plan

  • to set the time zone for the Daily Plan (Default: Etc/UTC),
  • to set the number of days for which orders will be planned ahead (Default: 5),
  • to set the number of days for which orders will be submitted ahead (Default: 3).

Users should not use the UTC default time zone but should use their local time zone.

This check verifies if Daily Plan settings have been changed to reasonable values.


WorkflowSeverity
Self-Test-Daily-Plan-SettingsWarning

Submissions

The JS7 - Daily Plan Service creates submissions of orders on a daily basis. In case of inventory inconsistencies the Daily Plan Service will not be able to submit orders to the Controller, for example if objects such as related job resources are missing in the Controller's journal.

This check makes use of JS7 - Settings for the days ahead for which orders will be planned and will be submitted. It compares settings with planned and submitted orders in the daily plan.

In addition, the check can be parameterized with threshold values for the number of planned and submitted orders per day of week. More information is available from the JS7 - How to check consistency of the Daily Plan article.

This check offers to parameterize a user's expectation about the number of submitted orders per day of week. Users make use of the below arguments to specify the minimum number of orders expected per day of week.


WorkflowSeverity
Self-Test-Daily-Plan-SubmissionsWarning



ArgumentDefaultPurpose
dpl_max_planned_orders0Specifies the expected number of planned orders for the number of days ahead for which the Daily Plan is calculated. Frequently zero planned orders are expected.
dpl_min_submitted_orders0Specifies the expected number of submitted orders for the number of days ahead for which the Daily Plan is calculated. This is not the number of daily orders but the number of all orders during the period for which the daily plan is calculated. Users can specify their expectation about the number of submitted orders.
dpl_min_orders_monday
dpl_min_orders_tuesday
dpl_min_orders_wednesday
dpl_min_orders_thursday
dpl_min_orders_friday
dpl_min_orders_saturday
dpl_min_orders_sunday
0Specifies the expected number of submitted orders for the related day of week. Users can specify their expectation about the number of submitted orders.
dpl_except_days''Specifies a list of days that will not be considered when checking the Daily Plan, for example non-working days or public holidays.
The list is created from the format: <yyyy-mm-dd[,yyyy-mm-dd]> or from an empty string indicated by two single quotes, for example:
  • 2025-07-14
  • 2025-07-14,2025-12-25
  • ''
dpl_run_daily_plan_servicetrue

Specifies that the JS7 - Daily Plan Service should be started before checking the Daily Plan. Can be set to false if the Daily Plan Service was executed before the check of the Daily Plan is performed..

dpl_wait_for_daily_plan_service60

If the Daily Plan Service is started by this workflow (run_daily_plan_service = true), then the argument specifies the duration in seconds of the period for which the workflow will wait for the Daily Plan Service to complete. A period of 60s should be sufficient for the Daily Plan Service creating some 3000 orders.

Projections

The JS7 - Daily Plan Service creates the Daily Plan and creates JS7 - Daily Plan Projections.

  • The Daily Plan holds orders that have been planned and submitted to Controllers and Agents for a number of days ahead.
  • Projections are used for the period beyond Daily Plan calculation. They hold assumptions about orders that will be executed in a wider future. In addition, projections hold dates and orders that are known to the Daily Plan.

This check verifies if the dates and number of orders in Projections matches the Daily Plan.


WorkflowSeverity
Self-Test-Daily-Plan-ProjectionsWarning



  • No labels