-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R3
-
Component/s: None
-
Labels:
-
Sprint:CFAMX 2020R3 SA Sprint 2, CFAMX 2020R3 SA Sprint 3
-
SCRUM Team:Globogym Purple Cobras
-
Story Points:8
-
SOW (Time Tracking) Project:45076
-
Work Type Classification:Sustaining
As an operator I want processing time to be taken into account when I create an order so that I can account for products that require preparation
Notes
- When creating an order, to determine if processing time should be account for, check:
- Vendor Setting -
CFAMX-8907 - Configuration Setting -
CFAMX-8912 - Processing Time for a particular item -
CFAMX-8891/CFAMX-8896
- Vendor Setting -
- Save the Processing Time as a part of the order for items where Processing Time != zero
Why and how?
- Why is this being done?
- There are products used in restaurants that need to be processed, prior to being available for use. For example chicken needs to be thawed for 28 hours before it can be used.
- When a suggested order is created, the forecast takes into account all sales between the time that the order is created and the Cover Until date & time.
- What is does not account for, is sales that are being made after the Cover Until Date & Time that need to be prepared
- How does this work?
- Lets say a store has a large catering order for Friday morning and another for Friday lunchtime
- The store places an order on Tuesday morning, for delivery on Wednesday, with a Cover Until of Thursday morning
- In this case, the Suggested Order will be generated, with a forecast for Tuesday morning thru to Thursday morning. However, the product needed to fulfill the catering orders on Friday will not be included in that order, even though the product needs to be available on Thursday so that it can thawed in time for Friday.
- The goal of this Feature Request is to adjust the times used by the Suggested Order algorithm to try to accommodate large, future catering orders
- For example:
- Current State - Forecast = 69 units
- Future state, including catering orders on Friday morning and lunchtime, = 103 units
Suggested Order Algorithm
- The suggested order algorithm is as follows:
- Suggested Quantity = Forecast Usage + Safety Stock - On-Hand - On-Order
- There are more details here: https://cfacorp.atlassian.net/l/c/858CmV64 IN-SuggestedOrdering-UseTimestampswhengeneratingaSuggestedOrder-010420-1215.pdf
- Note: When calculating the Forecast Usage, the start time, is the Order Create time, rounded down to the last 15 minute interval. For example is an order is place at 7:12 am, we go back to 7:00 am as the start time.
- The reason for this is because the forecast is stored in 15 minute intervals, and using these aggregated tables to provides improved performance.
Offsetting times to take into account Processing Time
- With the introduction of Processing Time, at the item level, each item needs to be analyzed when creating an order, to determine if a Processing Time Shift has to occur or not, and if by how much.
- Once an item has been identified as needing a Processing Time Shift, the time used to determine the Forecast Usage and Safety Stock need to be shifted in the following manner.
- Forecast Usage = Usage BETWEEN Create Order Time + Processing Time AND Cover Until Time + Processing Time
- Order created at 7:12am Monday - Gets rounded back to 7am
- Cover Until 8:00am Wednesday
- Processing Time = 30 hours
- Forecast Usage = Usage BETWEEN (Monday 7am + 30 hrs) AND (Wednesday 8am + 30 hrs) = Usages between Tuesday 1pm AND Thursday 2pm
- Forecast Usage = Usage BETWEEN Create Order Time + Processing Time AND Cover Until Time + Processing Time
- Safety Stock
- SS = Percentage
- Percentage represents a percentage of the Forecast Usage, when there is a Processing Time Shift, this should be a percentage of the Shifted Forecast Usage
- SS= Days
- Days represents the number of days worth of the daily projected quantity calculated (forecast usage divided by 'Real days'). When there is a Processing Time Shift, this should be a percentage of the Shifted Forecast Usage.
- Note: In calculation the "Real Days" for the safety stock, not only are closed days excluded from the calculations, but days without forecasts (Manager transaction count needs to be greater than 0 in the forecast header table, forecasting.forecast)
- A Processing Time Shift may results in a Sunday being included or excluded from the calculation
- Inventory Units - No change as this is a fixed number
- SS = Percentage
- On Hand
- There should be no change to the on Hand calculation for either UPT items or regular (depletion) items
- On Order
- There should be no change to the on Hand calculation for either UPT items or regular (depletion) items
Acceptance Criteria
Confirm when the Vendor is configured to account for Processing Time AND the Store is configured to account for Processing Time
- Confirm when a UPT item has Processing Time = zero, the Forecast Usage and Safety Stock should not be Shifted
- Confirm when a Regular item has Processing Time = zero, the Forecast Usage and Safety Stock should not be Shifted
- Confirm when a UPT item has Processing Time != zero, the Forecast Usage and Safety Stock should be Shifted, based on the configured Processing Time for that item
- Confirm when a Regular item has Processing Time != zero, the Forecast Usage and Safety Stock should be Shifted, based on the configured Processing Time for that item
- Confirm that there is no impact to the calculated On Hand for a UPT item when the Processing Time = zero
- Confirm that there is no impact to the calculated On Hand for a Regular item when the Processing Time = zero
- Confirm that there is no impact to the calculated On Hand for a UPT item when the Processing Time != zero
- Confirm that there is no impact to the calculated On Hand for a Regular item when the Processing Time != zero
- Confirm that there is no impact to the calculated On Order quantity for a UPT item when the Processing Time = zero
- Confirm that there is no impact to the calculated On Order quantity for a Regular item when the Processing Time = zero
- Confirm that there is no impact to the calculated On Order quantity for a UPT item when the Processing Time != zero
- Confirm that there is no impact to the calculated On Order quantity for a Regular item when the Processing Time != zero
Suggested Quantity
- Confirm that the Suggested Quantity calculation is accurate for items where the Processing Time = zero
- Confirm that the Suggested Quantity calculation is accurate for items where the Processing Time != zero
- Confirm when an item is on Allocation, and the Suggested Quantity exceeds the Remaining Allocation, the Suggested Quantity is capped by the allocation
- Confirm when an item is on Allocation, and the Suggested Quantity is less than the Remaining Allocation, the Suggested Quantity is used allocation
- Confirm when there is no Allocation and there is a User Default Quantity configured for an item, this (UDQ) value is still used in place of the Suggested Quantity
- Confirm when there is an Allocation in place and there is a User Default Quantity configured for an item, and the User Default Quantity exceeds the Allocation, the quantity is capped by the allocation
- Confirm when there is an Allocation in place and there is a User Default Quantity configured for an item, and the User Default Quantity is less than the Allocation, the User Default Quantity is used
Processing Time
- Confirm that the Processing Time is preserved as a part of the order for those items where the Processing Time != zero, as it will be used in later stories
Forecast Column
- Confirm that the data displayed in the Forecast column (Manage Columns) accurately reflects the forecast when the Processing Time = zero
- Confirm that the data displayed in the Forecast column (Manage Columns) accurately reflects the forecast when the Processing Time != zero
- implements
-
CFAMX-8154 Add Attribute: Processing Time for Suggested Items
- Closed
There are no Sub-Tasks for this issue.