Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Daily Plan Service is used to create and to submit orders for a Daily Plan to a any connected Controllers. Controllers. The service is operated in background and acts on a daily basis to plan a number of days ahead.
  • The Daily Plan Service runs existing JS7 - Schedules and generates orders for the given start times. This applies to Schedules that specify a single start time for an order and to Schedules that specify cyclic start times. For each start time in a cycle an individual order is created.
  • The similar functionality is available from the JOC Cockpit GUI the JS7 - Daily Plan for operation by users, however, the service performs this task automatically for a configurable number of days ahead.

Daily Plan

Schedules

Orders are created from Schedules that indicate the workflow and variables to be used as well as the run-time specification, i.e. the rules for what days and start times orders should be created.

...

  • The checkbox "Plan Order automatically" specifies that a Schedule will be applied when running the Daily Plan. Orders created by this step are added with a PLANNED state.
  • The checkbox "Submit Order to Controller when planned" specifies that any PLANNED orders - from the current Daily Plan run or from previous runs - will be submitted to a Controller and will result in a PENDING Order state.
    • Submission of an Order order to a Controller includes that for any Controllers to which the respective Workflow has been deployed an Order is submitted.

...

The submission step includes to forward Orders to any Controllers to which the underlying Workflow has been deployed.

User Intervention

The Daily Plan Service is designed to respect user interventions that include e.g. to manually create Orders for a given date, to modify Order start times or to cancel and to remove Orders from the Daily Plan. If such an intervention occurs then the Daily Plan Service will not consider to generate Orders for the given date.

  • This is intended to prevent conflicts with user interventions: a user can e.g. remove any Orders for a given date and the Daily Plan Service will not try to populate that date with Orders.
  • The Daily Plan Service considers the fact that a Submission has been created for a given date - either by the Daily Plan Service when previously generating Orders or by user intervention. If a Submission is found then no Orders are created for that Daily Plan date by the service.
  • However, users are free to delete Submissions with the Daily Plan View. Deleting a Submission does not remove Orders, it just hides the fact that for the given date the planning has been performed. If no Submission is available for a given date then the Daily Plan Service will check existing Orders for that date and will create additional Orders if required by the underlying Schedules. Practically speaking: if a user drops e.g. 3 Orders out of 10 for a given date and deletes the Submission then the Daily Plan Service will create the supplemental 3 Orders.

At the same time the Daily Plan Service will submit Orders that are in a PLANNED state to a Controller for a number of days ahead. This occurs independently from the fact that an Order was added by the user or by the Daily Plan Service. The functionality is intended to prevent a situation when users generate Orders with a PLANNED state but miss to submit them to a Controller in good time. The Daily Plan Service will pick up such Orders and will submit them for the number of days ahead as specified with the service configuration.

Configuration

Location

  • The "Settings" menu is available from the JOC Cockpit GUI.

...