This function has as its objective the definition of the parameterisation the elements that impact on the production scheduling process, notably the definition of the periods in the scheduling horizon.

It is possible to specify the load division by production site or set a load division common to all sites.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The entry of scheduling parameters takes place on a single screen:

Header

The production site where these parameters are to be applied is specified in the header.

Production site (field MFGFCY)

The production site associated with the user is proposed by default. It can be modified by another site authorized for the operator, depending on its authorizations.

Tab Parameter Definitions

 

The parameter automatic forward re-scheduling : this parameter is used during the scheduling batch processes. In the case where the backward scheduling calculates a production start date as a date that falls before the process date, this parameter is used to determine if a forward re-scheduling must be carried out from the process date, this impacts the chosen WO end date, or if it is necessary to maintain the end date and thus have a start date in the past.

In the case of scheduling runs carried out in real time, this parameter is not used: the system issues a message to the user "The backward scheduling takes place in the past - Forward re-schedule?" which allows the user to make their choice for each occurrence.

 The reinitialise the forced date in the past field is used to ignore these dates in the scheduling process.

It is necessary to define the period division (days, weeks, months) for the load horizon that will be scheduled.

The horizon defined in this way cannot exceed 2000 days, and the division of this horizon cannot exceed 1000 periods.

  Automatic adjustment : This parameter makes it possible for the user to indicate whether the period division commences at the start of a week (as a function of the first day of the week defined by the FIRWRKDAY general parameter) and a start of the month.

Last calculation date : this field is filled by the system.

 Hours : This section is used to manage the scheduling and the scheduling module in parallel. For a capacity of between 0 and 10 hours the system uses the activity start 1. Between 10h and 20h the system takes the activity start 2. Beyond that the start is midnight.

Scheduling parameters

Automatic reschedule of arrears (field AUTFRWSCD)

This setup makes it possible to define a default behavior
for the scheduling engine in the automatic processings in
the case where an upstream scheduling request takes place in the past.

If this setup is active, downstream scheduling from today's
date is systematically carried out.
Resetting the forced dates in the past (field AUTFRCSCD)
Reset the dates for the materials under process (field AUTWIPSCD)

If this setup is active, the dates of the material requirement being consumed can be re-adjusted by the scheduling.

Period breakdown

Day periods (field WKLDAYNBR)

These values represent the Groupings (days, weeks, months) of the horizon over which the load will be scheduled. As is the case for the Groupings defined in the Requirements Parameters, these numbers should be interpreted as the number of daily periods, the number of weekly periods, and the number of monthly periods.

For example: a 30 day/4 week/12 month grouping will result in:

1 grouping per day for the first 30 days

1 grouping per week for the next four weeks (after the 30 days)

1 grouping per month for the next twelve months (after the 30 days and the four weeks)

The horizon defined in this way cannot exceed 2,000 days, and cannot have more than 1,000 periods over the horizon.

Note: It is advised to have the Groupings for the Requirements Parameters and the Scheduling Parameters set equal to one another, even though you might choose to define them independently.
No. per. weeks (field WKLWEENBR)
No. periods months (field WKLMONNBR)
Automatic adjustment (field WKLBUCCOR)

Select this check box to adjust the schedule automatically to conform to the following rules:

  • A week starts with the first working day: Monday in Europe (defined by the FIRWRKDAY - First work day of week parameter (STO chapter, SCH group)).
  • A month starts on the first day of the month.

The following rules are applied:

  • If a number of days and a number of weeks are defined, the number of days will be increased so the first week starts on a Monday (according to the FIRWRKDAY - First work day of week parameter).
  • If a number of weeks and a number of months are defined, the number of weeks will be increased so the last month is complete.
  • If a number of days, a number of weeks and a number of months are defined, the first two rules are applied sequentially.

For example:

  • If the "days" period ends in the middle of the week, the system will add as many days as required so the next period starts on the first working day of the week.
  • If the "weeks" period does not end at the end of the month, the system will add as many weeks and days as required so the next period can start on the first day of the following month.

Last calculation

Date (field CUTSTRDAT)

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Site XX : Record non-existent

The site that has been entered is not defined.

A value must be entered in at least one of the three fields

No period division has be made in the scheduling horizon.

The total number of periods corresponds to a number of days greater than 2000

Total number of periods exceeds 1000

Tables used

SEEREFERTTO Refer to documentation Implementation