Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

George Moroses

Infor LX & BPCS Manufacturing Tip: Backward Scheduling

Operations are automatically backward scheduled at shop order release time. The backward scheduling algorithm starts with the shop order due date and schedules each operation based upon the standard move and queue times in the routings and the number of days the job is expected to run at standard. The system calculates and stores the operation scheduled start date. The dates may be modified by the shop order maintenance program. The number of days that a job is expected to run an operation is dependent upon the available capacity for that work center and the total hours scheduled for that operation.

The backward scheduling algorithm also considers the shop calendar for weekends, shutdowns, holidays, and partial days. Backward Scheduling Process The algorithm starts with the due date of the shop order or planned order. The system makes the following calculations for each operation in the reverse sequence:

1. The number of move days is subtracted from the due date (or initial date of the previous operation) to get the due date for this operation. The move days are only used on valid shop calendar days.

2. The system uses the following calculation for the number of clock hours for the operation: Standard run or machine hrs/No. of operators + setup hours

3. The number of clock hours is spread over the available daily capacity of the work center for those given days. The system uses the following calculation for the daily capacity of the work center: Number of shifts x hours per shift x average efficiency/100

4. Each day is checked against the shop calendar; the calculation bypasses inactive days or adjusts for any changes in the work center capacity for that day.

5. Queue time days are subtracted in the same manner as move time days. The resulting date is the operation start date.

The algorithm then goes to the previous operation. When all operations have been included, the resulting date is the scheduled start date of the shop order. Note that MRP uses the item lead time to determine material requirement dates on planned orders.

Backward scheduling is supported in all shop order release programs (SFC500, SFC550, and FAS510). Backward scheduling is recalculated if a shop order is maintained through SFC500 when the due date or the required quantity is changed; however, you cannot enter move and queue times through the maintenance program when adding an operation to the shop order.

Previous Article Infor LX & BPCS Tip: What is IDF and how could it make my life easier?
Next Article Infor LN & Baan Manufacturing Tip: All About Routings
Print
14098 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

Determining whether to use Master Production Schedule (MPS) planning or Material Requirements Planning (MRP) planning for items in Infor LX and BPCS involves understanding the nature of the items and their demand characteristics.

Master Scheduled Items typically encompass finished goods or service items. These items receive their requirements either from Independent demand, Dependent demand, or a combination of both...

1345678910Last

Theme picker

Tips: LN | Baan

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

First147148149150151153155156

Theme picker

Categories