Difference between revisions of "Planning"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* Retrieve processing parameter values - user-defined parameters (see in [[Parameter]]) are evaluated; specifically the parameters their value is defined by a database query. Only parameters used by a scenario tasks are evaluated, e.g. parameters not used by the scenario are not evaluated. | * Retrieve processing parameter values - user-defined parameters (see in [[Parameter]]) are evaluated; specifically the parameters their value is defined by a database query. Only parameters used by a scenario tasks are evaluated, e.g. parameters not used by the scenario are not evaluated. | ||
* Schedule tasks for execution - all valid tasks (for task validity see [[Task]]) are scheduled in the resulting [[Processing]] waiting to start their execution. Until the planning activity is finished, no task is started | * Schedule tasks for execution - all valid tasks (for task validity see [[Task]]) are scheduled in the resulting [[Processing]] waiting to start their execution. Until the planning activity is finished, no task is started | ||
| + | * Notify operators - if Start scenario operator is selected, notification is sent | ||
== Time-based planning == | == Time-based planning == | ||
| − | Scenarios set to Daily planning mode uses a time-based events as a planning driver. This planning mode | + | Scenarios set to Daily planning mode uses a time-based events as a planning driver. This planning mode uses time-based planning trigger with the following conditions: |
| + | * all previous instances (dates) finished | ||
| + | * if based on previous processing, trying to run for a date next to the last finished | ||
| + | * if based on calendar processing, trying to run for current day | ||
| + | * consider holiday based on internal calendar information (see [[Calendar]]) | ||
| + | * consider Lag setting - for example a Lag setting of 1 means the processing of 2.1.2025 will start no sooner than on 3.1.2025 | ||
| + | * consider Scenario validity based on validity dates | ||
Revision as of 15:25, 6 March 2025
Planning is an activity to prepare a processing based on a scenario definition.
Planning consists of several steps:
- Waiting for planning event - planning event is defined by Scenario planning mode setting; it can be time-based, file-based or other types, see in Scenario
- Retrieve processing parameter values - user-defined parameters (see in Parameter) are evaluated; specifically the parameters their value is defined by a database query. Only parameters used by a scenario tasks are evaluated, e.g. parameters not used by the scenario are not evaluated.
- Schedule tasks for execution - all valid tasks (for task validity see Task) are scheduled in the resulting Processing waiting to start their execution. Until the planning activity is finished, no task is started
- Notify operators - if Start scenario operator is selected, notification is sent
Time-based planning
Scenarios set to Daily planning mode uses a time-based events as a planning driver. This planning mode uses time-based planning trigger with the following conditions:
- all previous instances (dates) finished
- if based on previous processing, trying to run for a date next to the last finished
- if based on calendar processing, trying to run for current day
- consider holiday based on internal calendar information (see Calendar)
- consider Lag setting - for example a Lag setting of 1 means the processing of 2.1.2025 will start no sooner than on 3.1.2025
- consider Scenario validity based on validity dates
