Requirements Planning Process Overview

Managing inventory is like balancing a seesaw—too little inventory and you’re unable to fill orders in a timely manner, which could lead to customer dissatisfaction. Too much inventory and items sit on shelves, adding to your costs. You’d be able to solve these inventory problems, if only you could see them coming.

The Requirements Planning (RP) application for Traverse helps you balance future supply with demand so that you can solve inventory problems before they happen. Requirements Planning helps you plan accurately so that you can anticipate surplus or shortage, determine purchase or production requirements, manage inventory to retain less product on the shelves, increase customer satisfaction via better service, and institute cost-effective buying plans.

RP requires the Traverse Inventory application, and optionally interfaces with the Purchase Order, Sales Order, Project Costing, MFG Production, and Bills of Material/Kitting. You get the best use (and most accurate forecasting) when you interface RP with all available applications. When you interface RP with Purchase Order, Sales Order, Project Costing, and MFG Production or Bills of Material/Kitting, RP can access the purchase, sales, project usage, and work order information in those applications to accurately forecast inventory needs. In addition, RP can automatically enter purchase requisitions and work orders into Purchase Order and MFG Production or Bills of Material/Kitting when inventory shortages are identified. Alternately, you can use RP’s planning reports to manually enter purchase requisitions and work orders.

Definitions

  • Period: the time frame that Requirements Planning considers at one time. If a period is 'Weekly', RP will look at one week.
  • Period Definition: A period definition is the time frame the system considers when calculating demand or supply quantities. The period definition establishes the number of periods into the future the system will plan for. For example, a period definition of 10 weekly periods means the system will look at demand/supply requirements from now through 10 weeks from now.
  • Time Fence: A time fence is an artificial way to divide requirements into two sections based on time (time periods within the time fence and time periods after the time fence). The number you enter is the number of periods you want to include within the time fence. Time fences are important when you’re looking at orders vs. forecasts. The system uses actual orders vs. forecasts within the time fence and the greater of the two beyond the time fence. Imagine that the sales forecast for next March is 300 units, while actual sales are 275. If March lies within the time fence, the system uses the actual sales number of 275 on reports. If March is beyond the time fence, the system assumes 300 (the greater of the two) to be correct.

    For example, you might set the Demand Time Fence Periods to 3, and define 8 periods in total. This means that the first three periods in the period definition are included in the time fence (and actual numbers are used) while the remaining five periods are outside the fence (and the greater of forecasts vs. actual is used).
  • Procurement Method: For an inventory item, the procurement method is the manner in which you acquire the item to put into inventory. If the procurement method is 'make', the item exists on a bill of material (MFG BOM or BM). When a MFG Production Order or BM Work Order is created for a 'make' item, it is considered 'Demand'. If the procurement method is 'buy', the item is a component you purchase from a vendor, and is considered 'Supply', since components are required to build 'make' items. If the inventory item is a service or kitted item for which quantity is not tracked, the procurement method is 'none'.
  • Single-Pass mode: Determined by the RP Period Definition Horizon, Single-Pass mode allows the system to calculate the demand/supply through multiple layers in one pass. In multi-pass (normal) mode, you would generate RP data and then create MFG production orders/BM work orders for the forecast demand. Then you would generate RP data again to create purchase transactions to satisfy the forecast demand from those production orders/work orders. If a stocked subassembly is used, another RP data generation cycle is needed to create purchase transactions to satisfy demand.

    In Single-Pass mode, the system will create virtual production orders/work orders to calculate the supply requirements, then create virtual purchase transactions to satisfy the supply requirements, and repeat the process as necessary in one pass, using the period definition horizon as the time frame.

  • Forecasts: The Forecasts function allows you to manually enter demand/supply quantities for a period definition. This can be a way to consolidate regular or routine demand/supply into one place. For instance, if you have a set of items that are always ordered or made at the same time, you can create a forecast that includes those items. Requirements Planning includes forecasts when it generates data.

Back to top of page

Setup

Requirements planning uses the demand and supply that exists in the system to calculate what items should be made or bought and when. To facilitate the calculations, there are some items to set up before you start generating requirements planning data.

  • Create Period Definitions.
  • Determine whether you want to utilize Single-pass mode (RP Business Rules).
  • Create Forecasts as needed.
  • Ensure all items have an appropriate Procurement Method assigned. The system will, by default, assign a method of 'Make' to items for which there is a MFG BOM or BM BOM, and a method of 'Buy' to items that do not have a BOM. Kitted and service items will have a method of 'None'.

Back to top of page

Process Flow

Once you have period definitions and forecasts set up, you can utilize the requirements planning processes.

Requirements planning data is stored in an RP data table. Every time you run the Generate RP Data function, this table is cleared and reloaded. The other RP functions work with the data in this table.

See the main topics in the Help for details on each function.

First, on the RP Processing menu, open and run the Generate RP Data function. This will clear the RP data tables and reload them with updated data. You can use the Standard RP Report, Daily Detail RP Report, and the Component Pegging Report to view the data in the RP data table.

On the RP Processing menu, open the Requirements Planner. This screen is the primary way you interface with the RP data. This allows you to create purchase transactions, MFG production orders, BM work orders, or location transfers to ensure you have required inventory when you need it.

Use the Requirements Planner screen to view demand, open orders, and to create orders or location transfers to satisfy the demand. You can filter the RP data to work with specific subsets, such as items with a procurement method of 'make', items at a specific inventory location, or items assigned to a particular buyer/planner. You can also choose the types of recommendations the system will offer, such as a certain purchase type or select vendor method. You can also choose the period definition and time fence periods you want to work with.

Back to top of page