Capacity Use by Planned Order (cprrp2100m000)

	Capacity Use by Planned Order (cprrp2100m000) Use this session to list the capacity use by resource or by planned order. For every operation, LN displays the capacity use in a separate line. Therefore, if a plan item requires one resource for two separate operations, two lines appear for the order. In the details session, you can find the lead time and the general settings for each order line. You can list the capacity data in three ways: By resource, in order of date (default). By resource/order number combination, sorted on operation. By order number, sorted on operation. If you list the capacity data by resource, LN displays all the planned orders that require resource capacity. You can double-click a specific order to view the details about the capacity it demands of the resource. For a more general overview about capacity requirements for a specific resource, select the Resource option from the appropriate menu, and next the View Resource Order Plan option. Subsequently, LN starts the Resource Order Plan (cprrp0530m000) session in which LN can display all the orders that require resource capacity for a definable time bucket. If you started this session by zooming, you can only find and select a record. Note The data in the current session is updated if you run the Generate Order Planning (cprrp1210m000) session or the Confirm Planned Orders (cprrp1200m000) session. For each planned order, the capacity use is only generated in the order item's fixed lead-time horizon and the resource storage horizon. Note The Capacity Use by Planned Order (cprrp2100m000) session does not contain data about the critical capacity requirements, but only the capacity use for planned orders. LN stores the data about the critical capacity requirements in the Critical Capacity Requirements (cprmp3560m000) session from where it serves as input for the resource master plan. Related topics Rough Requirement Planning run, an overview RRP run, basic calculation for one item Scenario The identification of an overall planning solution. Each scenario represents one overall planning solution, and involves particular settings for the planning of items and resources. You can use scenarios to analyze and compare various planning options and to find the best planning solution. For example, you can vary demand forecasts or sourcing strategies. One of the scenarios is the actual scenario, which corresponds with the actual planning situation. You can only transfer planned orders and production plans from the actual scenario to the execution level of LN. Related topics Scenarios in Enterprise Planning Plan Level The level within a hierarchical planning structure. When you plan on a higher plan level, plans are general and less detailed. Example Plan level 1 is the highest plan level; the higher the number, the lower the plan level. Related topics Plan levels and product families Order Type The order type for which you want to display the resource capacity use. Planned Order The planned order number. Operation The operation that requires resource capacity. Plan Item The ordered plan item for which resource capacity is required. Total Order Quantity The order quantity that you defined in the Planned Orders (cprrp1100m000) session. Quantity Planned Input The quantity for which LN actually plans the production. The Quantity Planned Input of an operation can be greater than the operation's Quantity Planned Output, in order to account for material losses because of scrap and yield. The scrap quantity and the yield percentage are defined in the Routing Operations (tirou1102m000) session. Quantity Planned Output The quantity of the main item that you expect to be output by the operation. LN takes scrap and yield into account. General Details General Resource The resource for which LN displays the capacity use. Machine The machine at the resource of which capacity is required. Transfer Lot Size The number of items for which an operation must be finished before you can start with the next operation. Even though an operation is not yet finished for all items in a production order, you can start the next operation for the items that are already finished. The transfer-lot quantity concept replaces the previously used concept of overlap percentage on operation. Scrap Quantity A fixed quantity of unusable material, for example, faulty components, or material lost in cutting or sawing operations. The gross material requirements must be increased to account for anticipated scrap. Yield Type Determines if and how lost products come out of production if the yield percentage is below 100%. Two yield types are available: Discrete Lost products come out of production as rejected products. Continuous Lost products disappear completely, for example, through evaporation. Yield Percentage The usable output from a process expressed as a percentage of its input. Example 1 A certain production process for light bulbs has a yield of 98%. So, out of every 100 light bulbs produced, 98 are good on average. The remaining light bulbs are faulty, and will therefore be rejected. Example 2 Steel wires are twisted together to produce a steel cable. Due to the twisting, the cable is 10% shorter than the wires from which it is produced. So, the yield is set to 90%. Fixed Duration If this check box is selected, the cycle time has a fixed duration. Capacity Use Capacity Use The sum of the average setup time and the total cycle time for the ordered item quantity in hours. Man Capacity Setup The man capacity in hours required to set up for a production order. LN calculates the value of this field by multiplying the value of the Man Occupation for Production of the Routing Operations (tirou1102m000) session by the value of the Production Cycle Time field. Man Capacity Production The man capacity in hours required to produce the quantity planned input. LN calculates the value of this field by multiplying the value of the Man Occupation for Production of the Routing Operations (tirou1102m000) session by the value of the Production Cycle Time field. Machine Capacity Production The machine capacity in hours required to produce the quantity planned input. LN calculates the value of this field by multiplying the value of the Mach. Occupation of the Routing Operations (tirou1102m000) session by the value of the Production Cycle Time field. Machine Capacity Setup The machine capacity in hours required to set up for a production order. LN calculates the value of this field by multiplying the value of the Mach. Occupation of the Routing Operations (tirou1102m000) session by the value of the Production Cycle Time field. Miscellaneous Data Subcontracting Subassembly Type The type of subassembly being planned for. Allowed values Subassembly An intermediary product in a production process that is not stored or sold as an end product, but that is passed on to the next operation. For subcontracting purposes, a manufacturer can send a subassembly to a subcontractor to carry out work on the subassembly. This subassembly has its own item code defined in the Item Base Data. After work is finished, the subcontractor sends the subassembly back to the manufacturer. Also this reworked subassembly has its own item code defined in the Item Base Data. Subassembly Warehouse The warehouse from which the subassembly is sent or in which the subassembly is received. Production Cycle Time The resource capacity required to produce the quantity planned input. LN calculates the production cycle time by multiplying the value of the Quantity Planned Input field by the value of the Cycle Time field. Lead Times Queue Time The queue time for the specified operation. Average Setup Time The average setup time for the operation as defined in the Routing Operations (tirou1102m000) session. Fixed Setup Time The time that is needed to adjust a machine before an operation can start. This time is independent of the operation sequence. Cycle Time The cycle time for the production of a single item. Wait Time The time that an order remains at a work center after an operation is completed until it is moved to the next operation. LN does not plan wait times according to a specific calendar. Planning of the wait time is based on a 7 * 24 hours week schedule. A typical example is the time required for drying after the application of paint. Move Time The move time at the end of the operation. Time Unit Queue Time The time unit that LN uses to express the queue time. Earliest Start Date The date and time on which the material is needed to be able to start the production on time. Planned Start Date The start time of the operation. If you simulate an order plan, LN determines the start times and finish times of the operations by backward planning. LN plans backward based on the extra lead-time, the safety time, and the routing of the plan item. LN starts planning backward from the requirement date of the planned order. LN first calculates the sum of the safety time and the extra lead-time. This results in a number of days. After the above calculation, LN takes the date, that is the calculated number of days before the requirement date, as the finish date of the order. From the finish date, LN plans the start times and finish times of the operations backward according to the routing. The last planned operation must be ready on the finish date of the order. The length of the period between start time and finish time equals the sum of the setup time and the production time. LN retrieves the extra lead-time of the plan item from the Items - Planning (cprpd1100m000) session and the safety time of the plan item from the Item - Ordering (tcibd2100s000) session. Note You can manually change the way an order is planned in the Planning Method field of the Planned Orders (cprrp1100m000) session. Related topics To replan planned orders. Planned Finish Date The finish time of the operation. If you simulate an order plan, LN determines the start times and finish times of the operations by backward planning. LN plans backward based on the extra lead-time, the safety time, and the routing of the plan item. LN starts planning backward from the requirement date of the planned order. LN first calculates the sum of the safety time and the extra lead-time. This results in a number of days. After the above calculation, LN takes the date, that is the calculated number of days before the requirement date, as the finish date of the order. From the finish date LN plans the start times and finish times of the operations backward according to the routing. The last planned operation must be ready on the finish date of the order. The length of the period between start time and finish time equals the sum of the setup time and the production time. LN retrieves the extra lead-time of the plan item from the Items - Planning (cprpd1100m000) session and the safety time of the plan item from the Item - Ordering (tcibd2100s000) session. Note You can manually change the way an order is planned in the Planning Method field of the Planned Orders (cprrp1100m000) session. See To replan planned orders. Queue Start (Next Operation) The exact time and date of the earliest start date of the next operation. LN calculates the queue start by adding up the value of the Wait Time field and the Move Time field to the value of the Wait Start Date field. Material Warehouse This field is only used if the order is planned by a planner, in which case LN displays the warehouse that the planner uses to pick up materials.