24Flow Customer Documentation
24Flow Customer Documentation
Breadcrumbs

Production Order Scheduling


  • Schedule Offset (min): Can be considered as a safety margin or buffer, i.e. it is an additional time taken into account when scheduling, beyond the touch time and non touch time for the operations.

  • Batch Size Schedule Production Orders: This parameters avoids hitting some Salesforce platform limitations when scheduling a large number of orders. If in doubt, set this parameter to 200 as a starting point.

  • Workhours Base Timezone Id: This parameter is required only in case the automated process user is in a different time zone than the time zone your plant is located in.

  • Schedule Sequence Logic: There are three sequence logic options the scheduler can take in to consideration.

    • Sequence: scheduling according to the sequence numbers given on the operation in ascending order.

    • Sequence grouping: same as sequence but if sequence numbers are equal they are considered a grouping. Behaviour for forward scheduling, the start of the next operation is the latest end of the previous sequence group. Behaviour for backward scheduling, the calculation for the previous operation starts from the earliest startdate of the next grouping.

    • Predecessor: scheduling according to the predecessor lookup in operation.
      When nothing is set, sequence is taken.

  • Schedule Rebounce: If the scheduling type is backwards, the calculation can suggest a planned start date that lies in the past, which is impossible. In this case, the calculation of the production order happens with scheduling type forward. In case a production order was ‘rebounced’, a flag will be set on the production order and its associated operations. In addition, a platform event is raised.

  • Schedule Begin Of Day Forward: When Scheduling with type forward, it will set the startdate to the beginning of the workday.

  • Schedule Begin Of Day Backward: When Scheduling with type backward, it will set the startdate to the beginning of the workday.

  • Operation - Touch Time Field (min.): defines the field to use as touch time for an operation. 24Flow is by default using the field sfy24__TouchTimeQrmMinutes__c. Note that the touch time should be expressed in minutes.

  • Operation - NonTouch Time Field(min.): defines the field to use as non-touch time for an operation. 24Flow is by default using the field sfy24__NonTouchTimeQrmMinutes__c. Non-touch time is the buffer time between operations. Note that the non-touch time should be expressed in minutes.

  • Prod. Ord. - NonTouch Time Field (min.): In the case you work with main- and sub-production orders, there can be buffer time between a sub order and its parent. The Prod. Ord. NonTouch Time Field contains API name of the field on the Production Order that contains this buffer value (expressed in minutes).

  • Schedule - Run Equipment Capacity: After Scheduling the production orders, the capacities will be calculated on equipment level.

  • Schedule - Run Team Capacity: After Scheduling the production orders the capacities will be calculated on team level.

  • Schedule - Publ. 24Planner Event: Launch a Salesforce Platform Event to 24Planning when the production order scheduling is finished.