Define Scheduling

Explanation

Use this activity to define the execution schedule for the different jobs the server can automatically perform. The jobs from which you can select are:

• Qualify: Fills the forecast part register with parts that qualify as forecast parts, and deletes forecast parts that no longer qualify as parts. (Forecast parts are parts that are going to have forecasts generated for them.)
• Aggregate Daily: This job also aggregates the present period so you can see how much demand is used up to the current day.
• Create Forecast: Aggregates demand by period through the end of the previous period, and then creates a forecast starting with the present period. Should be scheduled to run once in the beginning of each forecast period. See Period Version
• Refresh DP Data: Syncs the Demand Plan Server with the database, parts that have been deleted from the overview forecast parts window in IFS EE will after this job be removed from the DP Server / Client. Parts that are added will be visible.
• Writeback DP data to file : Writes back the server forecast to the hard drive.
• Lock Write back: Locks the forecast server to prevent updates. The server is unlocked after the next forecast run. The server also can be unlocked from the server menu.
• Refresh IPR Data: Reads all changes done in the IPR planning hierarchy, will also fetch new inventory parts that have planning method B, and remove the ones that have got another planning method set.
• Send Auto Trolleys: Send out a Trolley for all trolleys that are defined as automatic.
• Complete DP Data Refresh: Empties the entire DP Server and loads all the data from scratch. (will take much longer time than the Refresh DP Data job)
• External Export: Performs the external export command defined in the Only External Import / Export field.
• External Import: Imports records put in FORECAST_DAY_IMPORT view. See Import.
• Recalculate Historical Forecast: Runs a job that recalculates the historical demand with the current selected forecast model and season profiles. This is used during implementation after the forecast parts have been assigned their models and profiles. It sets more accurate forecast error measures for the parts.
• Shut Down - This will automatically shut down the DP Server. Note: when the DP Server is running as a Window Service, DP Server will automatically start up after the server shut down based on the Response to Service Failure option selected for the particular service in windows. This job is only used in rare occasions, so its normally not scheduled. 

The different time intervals between job executions are:

• Disabled - The job will never start. 
• Minute - The job will run at the specified minute interval.
• Daily - The job is started every day; the first day is the Scheduled Date and Scheduled Time. 
• Weekly - The job is started once a week; the first day is the Scheduled Date and Scheduled Time. 
• Fortnight - The job is started every two weeks, starting on the Scheduled Date and Scheduled Time.
• Monthly - The job is started every month; the first day is the Scheduled Date and Scheduled Time. 
• Quarterly - The job is started every quarter of a year; the first day is the Scheduled Date and Scheduled Time. 
• Half-Year - The job is started every half year; the first day is the Scheduled Date and Scheduled Time. 
• Periodically - The job is started every time the period version of this forecast server ID changes from one period to the next.

Prerequisites

This activity requires that the Demand Planning Server General parameters be defined.

System Effects

There are no system effects until the forecast server is started.

Window

Demand Plan Server Setup

Related Window Descriptions

Demand Plan Server Setup/Scheduling

Procedure

1. Fill in the desired start date.
2. Fill in the desired start time.
3. Fill in the desired intervals.
4. Fill in the job parameters. For job 1, Qualify, you must enter the following parameters:

• The number of periods in which to look for the transactions.
• The number of transactions to be approved as a forecast part.
• The number of transactions you must exceed so that you do not get deleted as a forecast part.

These jobs also can be performed one time from the server's menu. See Server GUI.