Days of Supply = Recommended Procurement Quantity / Average Daily Usage |
Field | Description |
|---|---|
Procurement | The procurement order quantity recommended by Servigistics to be procured for the selected part/location SKU. Reported in number of Days of Supply (Days) and number of units (Units). This field only appears if the part is a procurement part. |
Repair | The quantity of on hand bad parts recommended by Servigistics to be repaired for the selected part/location SKU. Reported in number of Days of Supply (Days) and number of units (Units). This field only appears if the part is a repairable part. |
Replenishment | The quantity of parts recommended by Servigistics to be replenished or balanced for the part/location SKU. Reported in number of Days of Supply (Days) and number of units (Units). |
Critical Shortage | The shortage quantity of parts that are understocked for the selected part/location SKU. Reported in number of Days of Supply (Days) and number of units (Units). Click here for more information about critical shortages. |
Excess | The excess quantity of parts that are overstocked for the selected part/location SKU. Reported in number of Days of Supply (Days) and number of units (Units). Click here for more information about excesses. |
Field | Description |
|---|---|
Measure of Effectiveness Used | The measure of effectiveness used to calculate the optimal levels for the SKU. |
Values that appear in brackets in this section were calculated from the Stock Level Generation AutoPilot process. |
Field | Description |
|---|---|
EOQ | The Economic Order Quantity for parts for the selected SKU. |
Safety Stock | The Safety Stock for parts for the selected SKU. |
Minimum Safety Stock | The minimum value (in days and units) of Safety Stock. The Safety Stock value cannot go below this amount. Note that the original calculated Minimum Safety Stock value comes from planning parameters. When calculated Safety Stock is less than Minimum Safety Stock, a review type (review type 222) record is generated and posted to the Review Board. |
Maximum Safety Stock | The maximum value (in days and units) of Safety Stock. The Safety Stock value cannot go over this amount. Note that the original calculated Maximum Safety Stock value comes from planning parameters. When calculated Safety Stock is greater than Maximum Safety Stock, a review type (review type 223) record is generated and posted to the Review Board. |
Effective Pipeline Length | When stock is en route to the location via multiple pipelines, such as Repair, Replenishment, and/or Procurement, the Effective Pipeline Length is weighted according to the number of units in each pipeline multiplied by the individual pipeline lengths and normalized over the total number of units. For example, given a Replenishment Pipeline of 10 days and a Repair Pipeline length of 15 days, if 3 units are coming from the Replenishment Pipeline and 2 units are coming from the Repair Pipeline, the Effective Pipeline Length is: Effective Pipeline Length = ((3 * 10) + (2 * 15))/(3+2) = 12 |
Pipeline Consumption | If sales orders are netted against forecast: Equals max (Forecast Quantity, Sales Orders) over the pipeline length. If sales orders are not netted against forecast: Equals the sum of forecast over pipeline length* plus sales orders. Sales orders might also be limited to those due to be shipped within the pipeline time period. * Pipeline length includes order period time. |
Pipeline Supply | Procurement: On Hand New + On Order within effective pipeline length - Backorder - Allocated Repair: On Hand New + In-Repair Due within effective pipeline length - Backorder - Allocated Replenishment: On Hand New + On Order within effective replenishment pipeline length - Backorder - Allocated |
HistorySD/ Forecast Error | Displays History Standard Deviation value when the forecast parameter Std Deviation - Use forecast error is set to No. It displays the Forecast Error Standard Deviation value when the forecast parameter Std Deviation - Use forecast error is set to Yes. History Standard Deviation: a measure of historical demand variability over a specified number of time slices, calculated from either the raw demand history as downloaded from the host system or after being de-seasonalized/de-trended. Forecast Error Standard Deviation: a measure of forecast error variability over a specified number of time slices, calculated from raw demand history and forecast history. |
Values that appear in brackets in this section were calculated from the Stock Level Generation AutoPilot process. |
Field | Description |
|---|---|
Repair Balance | Inventory position for repair parts is the current On Hand Good amount plus the quantities of any approved actions. Repair Balance = On Hand Good + In Repair - Allocated - Backordered |
Repair Max | The Repair Stock Maximum for parts for the selected SKU. |
Repair ROP | The Repair ROP for parts for the selected SKU. |
Repair EOQ | The Economic Order Quantity for parts for the selected SKU. |
Values that appear in brackets in this section were calculated from the Stock Level Generation AutoPilot process. |
Field | Description |
|---|---|
Replenishment Balance | Inventory position for replenishment parts is the current On Hand Good amount plus the quantities of all actions (not just approved actions). Procurement/Replenishment Balance = On Hand Good + On Order + In Repair + In Return * (1 - NFF Rate) * (1 - RepWR) + In Return * NFF + OHB * (1 - RepWR) - Allocated - Backordered |
Replenishment Maximum | The Stock Maximum for parts for the selected SKU. |
Replenishment Order Point | The Reorder Point for parts for the selected SKU. |
Minimum Replenishment Order Point | The minimum value (in days and units) of Reorder Point. The ROP value cannot go below this amount. Note that the original calculated Minimum ROP value comes from planning parameters. When calculated ROP is less than Minimum ROP, a review type (review type 224) record is generated and posted to the Review Board. |
Maximum Replenishment Order Point | The maximum value (in days and units) of Reorder Point. The ROP value cannot go over this amount. Note that the original calculated Maximum ROP value comes from planning parameters. When calculated ROP is greater than Maximum ROP, a review type (review type 225) record is generated and posted to the Review Board. |
Replenishment EOQ | The Economic Order Quantity for parts for the selected SKU. |
Replenishment Pipeline Forecast | The effective forecast quantity within the effective replenishment pipeline length. |
Repair Pipeline Forecast | The effective forecast quantity within the effective repair pipeline length. |
Return Pipeline Forecast | The effective forecast quantity within the effective return pipeline length. |
Safety Stock | The Safety Stock for parts for the selected SKU. |
Minimum Safety Stock | The minimum value (in days and units) of Safety Stock. The Safety Stock value cannot go below this amount. Note that the original calculated Minimum Safety Stock value comes from planning parameters. When calculated Safety Stock is less than Minimum Safety Stock, a review type (review type 222) record is generated and posted to the Review Board. |
Maximum Safety Stock | The maximum value (in days and units) of Safety Stock. The Safety Stock value cannot go over this amount. Note that the original calculated Maximum Safety Stock value comes from planning parameters. When calculated Safety Stock is greater than Maximum Safety Stock, a review type (review type 223) record is generated and posted to the Review Board. |
HistorySD/ Forecast Error | Displays History Standard Deviation value when the forecast parameter Std Deviation - Use forecast error is set to No. It displays the Forecast Error Standard Deviation value when the forecast parameter Std Deviation - Use forecast error is set to Yes. History Standard Deviation: a measure of historical demand variability over a specified number of time slices, calculated from either the raw demand history as downloaded from the host system or after being de-seasonalized/de-trended. Forecast Error Standard Deviation: a measure of forecast error variability over a specified number of time slices, calculated from raw demand history and forecast history. |
Field | Description |
|---|---|
Pallet Size | Size of the pallet in units for this part at both the vendor location and stocking location. |
Packaging Size | Size of the packaging in units for this part at both the vendor location and stocking location. |
Sales Size | The smallest quantity to order when there is a need for at least one unit. If there is no value for Sales Size, then Lot Size and Lot Size Round are used to determine the smallest quantity to order when there is a need for at least one part. |
Fixed Order Size | The order quantity of this part is always set to this amount. |
Is ASL Item | Yes indicates that the part is on the Authorized Stock List for the location being viewed; No indicates that the part is NOT on the Authorized Stocking List for the location being viewed. |
Date Added | The date the part was added to the Authorized Stock List (if applicable). |
Date Deleted | The date the part was removed from the Authorized Stock List (if applicable). |
ASL Source | Indicates the method used to remove the part from the location's authorized stocking list. Valid options are: • Blank (not removed) • Manually • AutoPilot |
Part Cost | The amount paid to acquire the part. |
Repair Cost | The cost to repair the part. |
Repair All | Yes indicates that Repair All is enabled for the part. No indicates that Repair All is disabled for the part. Repair All generates a repair action for the selected part at all locations with On Hand Bad quantities of the part. Repair All repairs all the bad parts, and it is triggered only when Order Plan finds requirement. |
Minimum Order Quantity | The smallest quantity of this part that may be ordered at a time. |
Lot Size | The increments in which order quantities must be increased for compatibility with vendor packaging. |
Last Time Buy | If the part will no longer be manufactured, indicates the last opportunity available to a service parts manager to procure the part. |
Days Between Demand | A measure of the average number of days per demand occurrence over a one year period for the selected part and at the selected location plus all locations beneath it in the location tree over the same one year period. It is calculated as: # of slices in a year / number of demand history records for the year Note that the number of records in demand history is the count of records in IPCS_DEMAND_HISTORY per demand stream (excluding any non-valid records). This value is calculated per demand stream and the minimum number becomes the Days Between Demand value. |
First History Date | Date of first demand history record in Servigistics for the selected part/location SKU. |
Need By Date | The expected out of stock date, considering both on hand and on-order quantities. Assumes previous orders will arrive at their average lead time and that usage will be as forecasted. Calculated as Today + (30 * (On Order + In Repair + In Return - Backorder + On Hand Good - Allocated + Proc Req Amount + On Hand Bad) / Forecast) |
Expected Date | The date an order is expected to be received if the procurement order is placed today. Expected Date = Today's Date + Pipeline Length |
Cushion Time | The difference in days between the Need By Date and the Expected Date. A negative Cushion Time means you will need stock before you are scheduled to receive it. Cushion Time = Need By Date - Expected Date |
Out Of Stock Date | The date when On Hand Good will be zero at the current demand rate. Out Of Stock Date = Today + (30 * (On Hand Good) / Forecast) |
Days on Hand | This is calculated based on the GENERATE_OP_SL_OUTSTOCK_DAYS global setting. • When the global setting is set to false, the Days On Hand value is calculated by Stock Levels process as (On Hand New + On Hand Fixed)/ Average Daily Demand Rate) • When the global setting is set to true, the Days on Hand value is calculated as follows: ◦ For customers using Stock Levels process, Interactive Plan will still calculate the Days On Hand value as: (On Hand New + On Hand Fixed)/ Average Daily Demand Rate) ◦ For Time Phased SKUs: Days on Hand is based on when the planned on hand Good goes below zero. It relies on the Planned On Hand Good goes below 0 review reason. ◦ For Trigger SKUs, Days On Hand is calculated as: (On Hand New + On Hand Fixed)/ Average Daily Demand Rate) When Forecast is zero, then Days on Hand is displayed as a blank • Where Average Daily Demand Rate is defined as: ◦ If level source is MEO/SIO (Inventory Optimization) then the Average Daily Demand Rate is equal to IPCS_STOCK_LEVEL.OptDailyDmdRate ◦ If level source is Levels then the Average Daily Demand Rate is equal to IPCS_STOCK_LEVEL.SLDemandPerDay |
ASL Chain Removal | Yes indicates that the part has been removed from the ASL due to demand burn-off. |
ASL Chain Removal Part | When ASL Chain Removal is set to Yes, indicates the new top most part for the part chain. |
Mid-Slice ASL Adjustment | Yes indicates that this SKU has been added to the ASL through the mid-slice ASL adjustment process which is implemented through the ASL Generation AutoPilot process. |
Last Order Date | The date for the most recent order for selected parts at the selected location. |
Last Order Quantity | The count of selected parts ordered for the selected location on the Last Order Date. |
Usage Rate | Set in the Part record as the first factor in Leading Indicators forecasting - it is the failure (or demand) percentage rate currently in use for this part. This rate may have been calculated based on the install base and demand history of this part (or its Like Part reference), or may have been set by the user through the Usage Rate Override Amount and Date Updated fields. If "Calculated Usage Rate" flag is set to "yes", Servigistics calculates the Usage Rate by dividing the global demand for that part during the forecast slice period just ended by the Average Install Base of that part during that period (Effective Part Population) plus the average install base of previous periods where there was no demand, even though wear continued on the parts (Accumulated Part Population). For example, if the part population was 5000, and there were 10 demands that period at locations where that part was forecasted with leading indicators, then the usage rate would be (10/5000). This result is multiplied by 100 to convert to percentage, so in this example, .2% of the Install Base is predicted to fail during each forecast period. If both "Calculated Usage Rate" and "Smooth Usage Rate" fields are set to Yes, then this rate is calculated as a weighted average between the Previous Usage Rate (defaults to 80% weight) and the Previous Slice Usage Rate (defaults to 20% weight). For example, Calculated Usage Rate will be .96 (just under 1% of the part population) if Previous Usage rate = 1.00 and Previous Slice Usage Rate = .80. |
Usage Rate Standard Deviation | If Usage Rate is being used, Usage Rate Standard Deviation indicates the standard deviation of the Usage Rate. This is a measure of the variance of the Usage Rate over time. |
Field | Description | ||
|---|---|---|---|
Optimized | A yes/no indicator. Yes indicates that the SKU was optimized by the inventory optimization calculation process. | ||
Average Order Size | The effective quantity in which customers use SKU in an Inventory Optimization model that has Use Line Fill Rate enabled for the scenario. Customer Order Size incorporates Customer Order Size Average, Customer Order Size Standard Deviation, Line Safety Factor and configurable logic for resupply locations. When Use Line Fill Rate is enabled for the scenario, performance is measured by the ability to satisfy complete orders instead of single units.
| ||
Order Size Standard Deviation | The variation for the order size. This value is used to convert the optimal stock level of orders to that of units.
| ||
Made Production Date | The date the record was made production. |
To hide this section, click View on the toolbar and click Hide Graphs. |
Graph | Description | ||
|---|---|---|---|
Forecasted Demand | This graph shows the forecasted demand by time slice over the period represented by the sum of the EOQ, Safety Stock, and Pipeline Demand quantities expressed in days of supply for the selected part/location SKU. | ||
Days to Units Conversion | This graph converts units to days and vice-versa. It is a graphical representation of how forecasted demand is consumed with time. For example, assume your monthly forecast is 100 and your system date is May 1. Then, for this graph 100 units might be converted to 31 days. The conversion is done using the IPCS_FORECASTED_DATA table. | ||
Depletion Graph | This graph shows the projected depletion of on hand quantities over time during the pipeline length for the part/location SKU. It considers Sales Orders and Forecast when calculating inventory depletion. • If the LEVELS_NETTED_FCST_DEPL_GRAPH global setting is set to true, the total Sales Order quantity for the time slice is added to the slice Forecast quantity, and the netted sum is divided by the number of days in the slice to produce the daily depletion rate. • If the LEVELS_NETTED_FCST_DEPL_GRAPH global setting is false, the slice Forecast quantity alone is divided by the number of days in the slice to produce the daily depletion rate. The resulting daily depletion rate is then applied to the On Hand Quantity over time to produce the depletion graph. The blue bars represent the projected On Hand quantity. The green line represents the Trigger-Based ROP, and the purple line represents the Safety Stock. | ||
Orders Per Year | This graph shows the carrying cost versus the number of orders per year (blue line), the order cost versus the number of orders per year (red line), and the sum of the carrying cost and ordering cost versus the number of orders per year (green line). It illustrates the advantage of EOQ, the point where the sum ordering cost and carrying cost is minimized and the cost of deviating from it. | ||
Safety Stock Units | This graph shows the Safety Stock required to achieve the corresponding Demand Satisfaction value for the selected part/location SKU.
|
Values that appear in brackets in this section this page were calculated from the Stock Level Generation AutoPilot process. |
Field | Description |
|---|---|
Procurement Repair Replenishment | Pipeline data is expressed in both length and standard deviation: Length: The number of days (0-365) in the pipeline. Standard Deviation: The standard deviation of the pipeline length. Effects of adjustment: Raising a pipeline's standard deviation will raise inventory levels by raising Safety Stock (since variability in the supply chain increases risk). |
Processing Time | The time it takes a vendor to turn around an order at a vendor location. Measured from the time the order is taken to the time the items are ready for the shipping provider to pick them up. |
Transport Time | The time it takes for the shipment of the items. Measured from the time the items are picked up at the vendor to the time the items are received at the stocking location. |
Putaway Time | The time it takes to have an item ready for use. Measured from the time the items are delivered to the stocking location to the time the items are on the shelf. |
Values that appear in brackets in this section this page were calculated from the Stock Level Generation AutoPilot process. |
Field | Description | ||
|---|---|---|---|
Demand Satisfaction | The probability the part will be in stock at the location when demand for it occurs. Effects of adjustment: Raising Demand Satisfaction raises inventory levels by raising the Safety Stock, as the risk of not having the part at that location is reduced. | ||
Demand Accommodation | Indicates the probability the part will be on the Authorized Stocking List (ASL) for the location when demand for it occurs. | ||
Service Level | The probability the part will be available at the location when needed. | ||
Order Cost Reference Order Cost Override Reference Order Cost Override Currency | The cost to place a procurement, replenishment, or repair order for the part at the location. Reference Order Cost/Currency is the Order Cost in the reference value/currency. Click here for more information about local and reference currency. | ||
Carrying Cost | The percentage of part value equaling the annual cost to hold that part in inventory, including the costs of depreciation, insurance, facilities, time value of money, etc. This is normally between 25% and 35% per year, but can be higher for parts in the high-tech industry that are prone to obsolescence and depreciate quickly. Also known as holding cost. Effects of adjustment: Raising Carrying Cost lowers the EOQ, thereby lowering the Stock Maximum. | ||
Return Wash Rate | The percentage of parts that are removed from inoperable equipment, yet never arrive at a repair facility. If a forecasted need persists, both return and repair loss must be compensated for by additional procurement. The Return Wash Rate is used to forecast returns, which are used in time-phased planning to project the On Hand Bad Quantity. Calculated as Forecast * (1 - Return Wash Rate)
| ||
Repair Wash Rate | The percentage of units in repair that are not be able to be repaired. For example: • Repair Wash Rate = 10% • 10 good units are required to meet demand The repair recommended quantity will be 11 units of On Hand Bad, as the calculation will assume that one unit (10%) will wash out during the repair process. | ||
NFF Rate | The percentage of returned material that is determined to not need repair and therefore is available for immediate use as good inventory. | ||
Min EOQ (slices) | Sets EOQ equal to forecasted demand for a given number of slices. Lower limit for EOQ. | ||
Max EOQ (slices) | The Maximum EOQ. Expressed in number of slices worth of Servigistics forecasted demand. Allows a user-imposed upper limit to be placed on the Servigistics-calculated EOQ, as it is used to calculate Stock Max. For example, you might want to set Max EOQ for order recommendations for epoxy to 5 time slices because it will go bad in that time.
| ||
Max REOQ (slices) | The Repair Maximum EOQ. Expressed in number of slices worth of Servigistics forecasted demand. Allows a user-imposed upper limit to be placed on the Servigistics-calculated repair EOQ. | ||
Set EOQ (slices) | Lets you override the Servigistics calculated EOQ and force the EOQ to equal some number of slices of Servigistics-forecasted demand. For example, if the Servigistics forecast predicts demand for 20 parts per slice for the next two slices, and Set EOQ is specified as 1.25 slices of forecast, then the EOQ will be 25 units. There may be any number of reasons for overriding an EOQ, such as the material is difficult to store (size, lack of room) or it may have a short shelf life (chemicals). Set EOQ impacts the value of Stock Max by overriding the calculated EOQ value. | ||
Set REOQ (slices) | Lets you override the Servigistics calculated Repair Economic Order Quantity and force the Repair EOQ to equal some number of slices of Servigistics-forecasted demand. | ||
EOQ Override | Overrides the calculated EOQ for the selected part/location SKU. | ||
Minimum Stock Max | The minimum Stock Maximum value to be used. For example, if you enter 3 for Minimum Stock Max, Stock Max will never be under 3 for the SKU. This value is set through AutoPilot parameters. | ||
Minimum ROP | The minimum ROP (ROP) value to be used. For example, if you enter 3 for Minimum ROP, ROP will never be under 3 for the SKU. This value is set through AutoPilot parameters. | ||
Phase In Date | The start date in the past from where demand is used in Servigistics for this part. | ||
Phase Out Date | The future date when the forecasts stops in Servigistics for this part. | ||
Variance to Mean Ratio | A ratio of the lead time demand variance to its mean, and is a normalized measure of the dispersion of a probability distribution. The default value is one (1). When the VMR is equal to one it is assumed that the demand variance is equal to the mean of the demand. When using a VMR of less than 1, the underlying spares model assumes that the variability of demand relative to its mean is smaller (i.e. less volatility in demand). The end result is that there is less volatility in demand and less spares are needed to compensate for uncertainty. When using a VMR greater than 1, the underlying spares model assumes that there is a great deal of variability of demand relative to its mean (i.e. lots of volatility in demand). The end result is that there is more uncertainly in the projected demand and more spares may be needed to compensate for this uncertainty. | ||
Procurement Order Period Repair Order Period Replenishment Order Period | The minimum number of days between orders for the procurement, repair, or replenishment pipeline.
|
Field | Description |
|---|---|
On Hand Good | Available good stock. Generally a healthy amount of On Hand Good is between Safety Stock and Safety Stock + EOQ. |
On Hand Bad | The number of bad parts in stock at this location that are awaiting a repair order. This is separate stock from In Repair, for which a repair order is in progress. |
Backorder | The number of parts on backorder. |
On Order | The number of parts that have been ordered but not received yet. |
Allocated | The quantity of parts on hand that is already committed and unavailable. |
In Repair | The number of parts currently being repaired. |
Backorder Date | Used as an input during Fair Share Priority to establish priority. This value can be edited. If you edit the value, click to save your changes. |
On Order In Repair Lead Time | The aggregated amount of those orders which are on their way (not received) and would come within repair lead time + repair order period. |
Average Part Cost | The average cost of the part. |
Field | Description |
|---|---|
Custom Level (1-5) | Custom fields for levels derived from the IPCS_STOCK_LEVEL table. |
Field | Description |
|---|---|
Average Part Cost | The average cost of the part. |
Date Due | The date the order is due to be received. |
Date Placed | The date the order was placed. |
Date Promised | The date the order is promised if different from the Date Due. |
Date Received | The date the order or portion of the order was received. |
Host Open Order ID | Unique ID for this order, derived from the host system. |
Is ASL Item | Yes indicates that the part is on the Authorized Stock List; No indicates that the part is NOT on the Authorized Stock List. |
Location Name | The name of the location that placed the order. |
Open Order ID | System-driven integer identification number for the open order record. |
Open Quantity | The amount remaining on a partially filled order. |
Order Buyer | The person responsible for placing the order. |
Order Quantity | The quantity of the part included in the order. |
Part Active | Yes indicates that the part is active; No indicates that the part is inactive. |
Part Name (1-5) | The name of the part. Note that more than one field is provided to use for different languages. |
Part Number | The number of the part. |
Planner Code | The planner code (or type of planner) responsible for planning this part. |
Planner Code Name | The name of the planner code who placed the order. |
Reference ID | The order number that is used in the system to reference the order even after it is closed. |
Shipper | The carrier for the order (for example, UPS). |
SKU Custom (1-15) | Custom fields for SKUs derived from the IPCS_SKU table. |
Shipper | The carrier for the order (for example, UPS). |
Status | The status of an order, where: Plannedmeans part of the order has shipped. Orderedmeans no part of the order has shipped. Closed means all of the order has shipped and the item will be removed from the Order History page at the end of its pipeline period. |
Tracking Number | The carrier's tracking number for the order. |
Type | Indicates the type of order where: Procure = Procurement order Repair = Repair order c = Custom order |
Unit of Measure | Indicates how Weight per Unit is measured (i.e., pounds, grams, liters, etc.). |
Vendor Name | The name of the vendor processing the order. |
Weight Per Unit | The weight of one unit in the selected Unit of Measure (pounds, grams, liters, etc.). |