Project Material Requirements Planning

Project MRP (PMRP) totals the demand for all the parts within a specific program, project, sub project, and activity. The calculation is based on the existing project inventory balance, project shop orders, and project purchase orders. Planning methods control the planning data you enter for a part.

PMRP is a clone of MRP. Like MRP, PMRP calculates the demand in the entire product structure, making sure that the demand  is met on every level. The major difference is that MRP considers all non-project specific requirements, while PMRP only considers activity specific requirements.

The purpose of PMRP is to calculate the demand for the parts based on shop orders, material requisitions, project miscellaneous demands, and part structures, to ensure that the demand is met. PMRP results in a proposal for parts that need to be manufactured and purchased, and in what quantities. It also generates suggestions on how to plan shop orders and purchase orders to best meet the demand for new shop orders and purchase requisitions.

PMRP can be performed with netting per activity, netting per project or netting per PNG. Netting is the process of calculating net requirements for a part.  When executing PMRP, you can specify values such as site, project ID, planned netting group (PNG), and the run date. The values that you are allowed to enter depends on the type of netting you choose to perform. You may refrain from entering a value in the permitted fields or you may enter the wild card symbol (%). In the Perform PMRP per Activity window for instance, if you do not enter a project ID or if you enter the wild card symbol (%) in the Project ID field, it indicates that all open project IDs will be considered in the calculation. PMRP starts by calculating the lowest level on which parts exist, on the structures in which they are included. A part that is not a component of another structure, but is only a parent part, has the lowest level zero (0). Zero-level parts are usually sales parts. A part that is a component of a parent part is at level two, a component of a component is at level three, and so on. This level coding is necessary for PMRP, estimates, and accurate calculations of product families and product codes. Then before PMRP calculation takes place, existing supplies (purchase requisitions and shop proposals) that were created by PMRP in a previous run will be deleted. The PMRP process will re-generate all the necessary supplies after the calculation.

When PMRP is performed with netting per activity, it calculates requirements only by specific activities within a project. In other words, if one activity in the project has excess stock, and a second activity in the same project needs the stock, PMRP does not automatically allocate the material from the first activity to the second. If you want to automatically move stock between activities (and even between projects), you can do this using PNGs. This is accomplished by performing PMRP with netting per project or with netting per PNG. See the topic description on Planned Netting Group for more details about PNGs.

When PMRP is performed with netting per project, it calculates requirements by considering supply and demand of all the activities in the project. Therefore any excess supply belonging to an activity can be used to meet the demand arising from another activity in the same project.

Similarly, when PMRP is performed with netting per PNG, the netting process considers supply and demand of all the activities in the specified PNG. If it is a project PNG, then the process is the same as that of netting per project. If the PNG consists of activities from different projects, it will be possible to move stocks between projects. This is called multi-project material requirements planning (MPMRP).

PMRP considers customer-owned inventory for the project as on-hand stock. MPMRP can use customer-owned inventory only in projects that have the same customer. If there are different customers within the PNG, then the customer-owned inventory should be excluded from the PNG.

MRP Source Description MRP Usage PMRP Usage
MRP Internal exploded MRP demand Yes Yes
MS Child Master schedule component demand Yes Yes
Order Entry Demand from customer order line Yes. No project specific orders are considered Yes
Material Requisition Demand material requisition line Yes. No project specific orders are considered. Yes
Purchase Order Supply from the purchase order line demand from the purchase order lines Yes. No project specific supply or demand is considered. Includes PMRP and Umbrella PO orders.
Shop Order Supply from the shop order demand from the Shop Order component Yes. No project specific supply or demand is considered. It will consider PMRP and Umbrella SO orders.
Work Order (Maintenance) Demand from the work order Yes Not in this phase
Dynamic Order (DOP) Demand from unpegged DOP order Yes Will not be considered. Demand and supply for PPSA DOP orders are managed by DOP.
Reorder Point Demand of components to an open requisition, created from the re-ordering point calculation. Yes No, because the reordering point calculation only considers standard inventory.
Production Schedules Demand from production schedule components. Supply from production schedule Yes No, because the production schedule only considers standard inventory
Request Quote Supply from purchase requisition in the Request For Quotation status Yes. Only standard planned items Includes PMRP and umbrella purchase requisition lines.
Spare Part MRP spares Yes No
Customer Schedules Demand from customer schedule Yes Not in this phase.
Project Delivery Demand from project delivery. Yes. Only standard planned items Yes. Only when the supply option is PMRP.
Customer Quotation Demand from customer quotation Yes Not in this phase.
Project Misc Demand Demand from project misc demand. Only standard planned items are considered. Yes. PPSA included. Only where supply option is PMRP.
Request Manual Supply from manually entered purchase requisition No It will consider PMRP and umbrella purchase requisition lines.