MAC-PAC Homecontact ussupport login 

Menu

Documentation > MAC-PAC Reference Library > Manufacturing > Master Scheduling > Key Concepts and Procedures > Master Scheduled Parts, Requirements Planning Parts, and Service Parts

Master Scheduled Parts, Requirements Planning Parts, and Service Parts

 

Parts must be planned by either Master Scheduling or Requirements Planning.  End-item parts are generally planned by Master Scheduling, and lower-level parts are generally planned by Requirements Planning.  However, service parts and other lower-level parts that may be critical in scheduling cannot be categorized as easily.

One of four demand codes may be used to define the method to be used for planning a part:

M - Standard Master Scheduled part

D - Daily Master Scheduled part

R - Requirements Planning part

S - Service part

Daily master scheduled parts, requirements planning parts, and service parts will be planned by Requirements Planning; standard master scheduled parts will be planned by Master Scheduling.  Service parts, daily master scheduled parts, and standard master scheduled parts are included in key facility load reporting; requirements planning parts are not included.  The following table illustrates the features that are handled by requirements planning parts, service parts, daily master scheduled parts, and standard master scheduled parts.

 

 

RP Part

Service Part

Daily MS Part

Standard MS Part

 

Forecast

Y

Y

Y

Y

 

Tentative Schedule

N

N

N

Y

 

Key Facility

N

Y

Y

Y

 

Available to Promise

N

N

Y

Y

 

RP Generation

Y

Y

Y

N

 

*Requirements Review

Y

Y

Y

Y

 

*Planning Action Review

Y

Y

Y

N

 

*Simulation Maintenance

Y

Y

Y

N

 

Focus Forecasting

N

Y

Y

Y

 

Consumption Code Logic

Y

Y

Y

Y

 

Multi-Level Forecast Generation

Y

Y

Y

Y

 

*RP Firm Horizon

Y

Y

Y

N

 

*  These features are found in the Requirements Planning module only.
                           

 

Features of standard master scheduled parts, daily master scheduled parts, requirements planning parts, and service parts are presented below to describe the parts for which each of the demand codes is most advantageous.

Features of Standard Master Scheduled Parts

·     The part will be planned by Master Scheduling through Tentative Master Scheduling and the MS Rollover.

·     Forecast may be entered for the part itself, or for a product family.

·     Consumable demand is "netted" against forecast in calculating total demand.

·     The schedule for the part will be included in the load against a key facility.

Features of Daily Master Scheduled Parts

·     The part will be planned by Requirements Planning.

·     Forecast may be entered for the part itself, but forecast entered at the product family level will be ignored.

·     Consumable demand is "netted" against forecast in calculating total demand.

·     The schedule for the part will be included in the load against a key facility.

Features of Requirements Planning Parts

·     The part will be planned by Requirements Planning.

·     Forecasts may be entered for the part, but a forecast entered at the product family level will be ignored.

·     Consumable demand is "netted" against forecast in calculating total demand.

·     Independent demand will be excluded from the calculation of load against a key facility.

Features of Service Parts

·     The part will be planned by Requirements Planning.

·     Forecasts may be entered for the part, but a forecast entered at the product family level will be ignored.

·     Consumable demand is "netted" against forecast in calculating total demand.

·     Independent demand for a part will be included in the calculation of load against a key facility.

End Items

The schedule of end items drives the scheduling of all lower-level items.  By defining end items as standard or daily master scheduled parts, the planner can work with a manageable number of parts until an acceptable plan is defined, and can then use Requirements Planning to schedule all lower-level parts.  However, if demand for an end item is only occasional, defining it as a standard or daily master scheduled part unnecessarily adds to the volume of master schedule information and computer resource requirements.