BC Item Availability by Event versus NAVEKSA ItemPlanning
Sometimes we hear, mostly from BC consultanats, that they are of the opinion that the BC Item Availability by Event produces what is needed.
NAVEKSA has made a thorough investigation on the usability, data content and correctness of results the standard BC Item Availability by Event tool gives you, and compared it with our ItemPlanning solution.
We have made the comparision against the standard BC Item Availability by Event, as this by far is the best (perhaps the only) standard BC tool when working with item availability.
We have found that this Event view fails/are weak in more functional ways, but also lacks useability and intuitiveness for the general user.
In all fairness we must also say that it can produce the right figures, limitations taken into consideration. See below.
Anyway to find of this academic creation, are not a job for ordinary users, who are – just users.
We have made a scenario:
You have a customer inquiring on the earliest delivery date to ship 250 pieces.
- Using BC Item availability by event says part delivery (110 pcs available) is possible on February 1st, 2018
- Using NAVEKSA ItemPlanning says full delivery is possible (260 pcs available) on February 1st, 2018
The natural answer is using NAVEKSA ItemPlanning, as it in an intuitive way offers the precise and correct answer on item availability, and this whatever the date is along the timeline.
We will not dwell on the reason for this deviation as it becomes too technical at this place. Just note that our ItemPlanning produces the correct numbers
The above scenario is a simple one.
It just consist of an open sales order, a purchase order, a safety stock quantity, a firm reservation against stock, a production order, and an inventory on-hand stock balance.
Scenario screen dump using Item Availability by Event:
Scenario screen dump using NAVEKSA ItemPlanning:
Here is a list of some weak spots found using standard BC Item Availability by Event.
- Deleted production forecasts are still shown, but fortunately not used in the planning calculations.
- Do you know exactly what column to be used to find the the best answer? – Projected inventory, Suggested Projected inventory or Remaining base ? And understand the underlying logic?
- No starting dates are shown for orders – released and planned. This date information may be important in certain contexts.
- There are no places where you can see the gross demand figures, i.e. that greater demand figure per forecast period,which drives the planning engine order proposal generation. This figure is an essential one in tracking demand sources.
- Uses purchase order expected receipt date,despite the promised date is filled.
- A term “Plan reverted” in the column Source is used. More correct this should be “Dependent requirement” according to APICS definitions.
- Forecast period figures are not reduced with actual sales orders in the “Forecasted projected inventory” column. This is what we call the greater demand of forecast and sales orders within a forecast period.)
- Risc of overplanning (-producing/buying) when customers are buying less than forecastet. This situation is not reflected in the projected stock.
- The user must every time remember to setup the screen properly when started. In addition, the user must watch out for proper use of the expand/collapse functions.
- Usability seems illogical by showing more data as negative quantities.
So, there are several reasons why we have developed the ItemPlanning solution which, in addition to produce accurate availability, offers several addtional functions – simulation, tracking, sales order where used, bill of material availabilty etc.
Reaktion
Powered by
Hinterlasse einen Kommentar.