Material Requirements Planning for Production
Production BOMs can contain finished products (products with their own production BOM) or assembled components (products with their own Assembly BOM). Material Requirements Planning (MRP) can be performed with or without BOM explosion. In this article we will explain the recommended workflow for MRP for production.
MRP requires an add-on to your base subscription. Add the MRP module from the My subscription page. Users whose subscription dates from before 1 February 2024 will continue to have the same level of access to MRP as they previously held.
Note: Production BOMs and Production Orders are an advanced manufacturing feature. You will need to add the advanced manufacturing module and MRP module to your Cin7 Core base subscription to use this feature. See Getting Started with the Advanced Manufacturing module for more information.
Prerequisites
Set General Settings → Minimum Before Reorder to Each location to use MRP module.
-
Set up Products
Configure product suppliers
-
Set up Locations
Set up Low stock reorder levels
Set supply rules
Get familiar with Material Requirements Planning (MRP) (required)
-
Get familiar with Get Started with the Advanced Manufacturing Module(required)
Nested Production Orders (Production BOM explosions) (recommended)
Advanced Manufacturing module subscription required.
MRP module subscription required.
-
Permissions:
Users will need the Run - MR Ppermission to perform MRP runs and change MRP run settings.
MRP Supply Setting: BOM explosion
A bill of materials (BOM) explosion displays the highest level of a production or assembly broken down into components at its lowest level. If the parent production or assembly contains components that also have a production or assembly BOM, the nested BOMs are also broken down into components.
If BOM explosion is not checked, Cin7 Core will not execute any decomposition or a production BOM or assembly BOM. Suggested supply orders will suggest production orders to meet demand, but no suggested supply orders will be created to meet demand for components and nested products.
Note: BOMs with auto-assembly/disassembly will generate suggested supply orders for the BOM components delivered to the assembly location. Suggested supply orders will not generate assembly order suggestions for products with auto-assemble/disassemble enabled.
If BOM explosion is checked, Cin7 Core will decompose a production BOM or assembly BOM to calculate the demand for nested products and components.
Recommended workflow to plan Production Orders
We recommend conducting MRP planning for manufacturing as a two step process in order to properly schedule orders around available production resource capacity.
In Step One, the user creates a master production schedule by running MRP without BOM explosion. Net, the user runs MRP with BOM explosion to meet demand for the production components.
Step One: Create Master Production Schedule
Open MRP by going to Inventory → MRP.
Make sure that MRP Supply Settings: BOM explosion is NOT checked. Select any other MRP parameters required for the run, and click Run to begin.
Suggested supply orders will generate production order suggestions. This pure production demand, without demand for components and nested orders.
Create these orders in Planned status.
Use the Capacity Planner to rearrange the planned orders so resource allocation is optimized.
We recommend to NOT release the production orders yet.
Step Two: Execute MRP for components
After all planned orders are correctly scheduled, return to Inventory → MRP to execute a run for components.
Make sure that MRP Supply Settings: BOM explosion is checked. Planned Production Orders should be selected as demand sourceand click Run to begin.
MRP Run will be executed and generate suggested supply orders for nested products and components.
Confirm the suggested supply orders for nested products and components to create purchase, transfer, and production orders in draft, planned, or authorized status.
(Optional) Consolidate production orders and nested orders for convenience.
Release production orders.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB