Dave: Mike I can see that you have released few production orders for this week. I’m afraid we wouldn’t be able to produce these orders as there is capacity overload. Also the orders are not scheduled correctly.
Mike: What do you mean Dave? I have released the orders from MRP.
Dave: Yes, but MRP is based on infinite capacity model
Mike: Infinite Capacity model? Could you please help me understand what that is ?
Dave: Basically MRP ignores any capacity constraints which means MRP only focuses on the quantity of the material to be produced. MRP only suggests the dates on which the material is to be produced.
Mike: Does this mean that results from MRP are incorrect? What can we do to prevent such situation in future ?
Dave: As I said earlier MRP executes on the principle of infinite capacity. Thus as per Best practice we should run Capacity Planning and Leveling after MRP run.
The above discussion is a transcript of a daily production stand-up meeting. Dave is production supervisor who is discussing production schedule with Mike who is a new production planner. Mike converted the planned order from MRP to production orders without considering capacity constraints. This resulted in capacity overload which means orders couldn’t be produced on time which would eventually result in delivery delays to the customer. That’s why it is extremely important to run capacity requirement planning. Once the planned orders from MRP are converted to production orders then capacity planning and evaluation should be carried out as MRP runs on the principle of Infinite capacity.
In this blog we’ll discuss some details of capacity requirement planning.
First thing first, the objective of Capacity Requirement Planning is to understand:
- Which work centers are required for Production?
- How much capacity of a work center is needed for Production?
- When is the capacity of the work center needed?
- Analyze capacity overload/underload situation
All the capacity relevant data is maintained in ‘Capacity’ tab in work center which is used to calculate the available capacity of the work center. Also, you could assign Factory Calendar to the work center so that capacity is only generated for working days while production on non-working days/holidays is not considered.
In the below screenshot you can see that SAP has offered many transactions in the capacity planning module. Each transaction code is designed for a specific use-case for example CM01 is designed to evaluate load at work center while CM21 is for leveling capacity requirements.
Personally I don’t think most of these transactions are really useful from an end-user point of view. I rather prefer CM25 as a one-stop shop which can be used for capacity leveling in a graphical format.
But before that we need to understand how capacity load is generated on a work center.
In Routing we maintain operating time for each activity on a work center. These operating times are used for calculating
load on the work center for a given production order. However ‘Control Key’ plays a very vital role here. Only the operations on work centers with control keys which have ‘Detailed Capacity Requirements’ activated generates capacity load.
Now let’s have a look at CM25 which can be used for capacity leveling.
Below screenshot displays production orders converted from planned orders after the MRP run. However these orders are not dispatched.
In the Order (pool) you can see multiple orders scheduled to run at the same time on work center. However it is practically not possible to product multiple orders at the same time on a single operation.
Now, select the orders and dispatch. Orders are dispatched on the work centers.
Now, the orders are dispatched. In the below screenshot you can see that only 1 operation/order is scheduled to run on a work center at a time. You can display this information in two different formats like work center view and order (dispatched) view.
Order Dispatch means capacity requirement planning is performed on the orders which means system calculates required capacity from the Routing and schedules the orders/operations to be executed on a work center. Time is calculated to the exact requirement of hour/minutes/seconds based on the order quantity & time maintained for each operation in the routing and accordingly operations are scheduled on the work center. CRP makes sure that only one operation/order is loaded on a work center.
CM25 offers some very interesting features. Here are some of my favorite features:
- Time Profile: you can choose the planning time horizon for which you want to run the capacity requirement planning.
- Time Scales: CM25 offers the option of changing the scale on planning table as per user preference. The Time axis of the planning board can be displayed in Hourly/Daily/Weekly scales. This gives flexibility to evaluate planning situation from short term to long term planning horizon.
- Strategy Profile:
You can use Strategy profile to control the dispatching of operations. If gives you a flexibility to select various parameters like:
- Parameters to control scheduling, that is, the dispatching of individual operations. You can control the parameters like Finite scheduling or Planning direction forwards or Dispatch at earliest point in time etc
- Parameters to control data like Period Split and Queue Time.
- Parameters to control Dispatching like:
- The following functions are available:
- Sorting of operations to be dispatched
- Consider operation sequence in the order
- Operation date check
- Change production version in event of an error
- Midpoint scheduling
Conclusion: MRP run is executed based on Infinite Capacity Model thus it is extremely important to use Capacity Requirement Planning. This will help to improve the utilization of available capacity and ensure on-time production.