Demand and fulfillment

这是一篇关于Demand and fulfillment的思维导图。对Demand and fulfillment感兴趣的小伙伴点赞加收藏。

JDA

• Hierarchy Overview
  • DFU
    • Primary key ID （U_LEVEL）
      • Demand Units
      • Demand Group
      • Location
    • Key dates
      • Until more systematic solution is available, DP will have to zero out the unnecessary forecast (for this case F20) manually and lock it. Carrie recommends to do so from D360如果跨度F17，F18，F21， 中间的时间F19，S20，S21也会有forecast, 因为DFU的effective date是从产品被tick的那一刻开始的，也就是说产品的effective date是F17的该产品的FOD, 那么这种情况下我们需要手动去zero outF19，S20,S21的forecast，并且lock住，因为如果不Lock的话sys interface还是会把之前的override覆盖掉。建议通过D360来处理这个zero out & lock
      • Effective date
        • Beginning of the season ticked in PDM (Automatically)
      • Discontinue date
        • Automatically
          • WS - SS 6/30, FW 12/31
          • RT - WS date + 9 weeks
          • ECOM - WS date + 13 weeks
        • Manual Update
          • Genealogies may be amended or deleted after an initial upload. To trigger the delete functionality, use the text DEL (all capitals) in the GenMaterialStyle column in the upload sheet. 
    • DFU Creation
      • NPI Process
        • Key gate of process
          • Line plan kickoff
          • Final Adopt
          • Drop to color
        • Reasons
          • New style / color
          • Assortment change
        • Type to apply
          • Pattern after materials -10 digital
          • Genealogy - 7 digital
            • Genealogies may be amended or deleted after an initial upload. To trigger the delete functionality, use the text DEL (all capitals) in the GenMaterialStyle column in the upload sheet. 
        • Key Elements
          • Mean
            • Average units
              • DTC - Weekly
              • WS - Monthly
            • Seasonal volume
              • DTC - 26 Weeks
              • WS - 6 Month
          • Scaling factor
        • Execution step
          • File location where these report lives - "Need" genealogy & pattern after
          • Tool (Pattern after selection tool)- define the the like style / patter after materials
          • Upload
            • Pattern - 10 digital - \\ush-p-df-azr1\FileShare\SrcFiles\PAST_Uploads\genealogy
            • Genealogy - 7 digital - \\ush-p-df-azr1\FileShare\SrcFiles\PAST_Uploads\genealogy
          • Upload fail notification
        • Batch timing
          • Upload template could be upload any time , process only run on each Wed night and weekend
      • Attributes
        • Global attributes
        • Regional attributes
          • Demand - CSC_DFU_ATTRIBUTE (7 & 10 digital)
            • Flex 1
              • Local product category
            • Flex 2
              • Lineplan (assortment)
            • Flex 3
              • Priority
            • U_KEYSTYLE
              • AD/AI
          • Fulfillment - CSC_U_MATERIAL_ATTRIBUTE (10 digital only)
            • GSP Signal code (FF Only)
              • GSP 1GSP 2U4/E/F*/BlankB4/F/BlankD4/F/BlankO4/BlankL4/BlankBlank (Was N)4/Blank* F inGSP 2 is OutletU - Made to order(used to be in ABC Primary), Solver logicNormally GSP does not touch the buy plan if U coded 2 stepsprocess to apply SMU code in FulfilmentAfter a new color DFU iscreated in Blue Yonder Demand, it requires 2 Fulfillment batch jobs to set up Ucode (for MTO logic) in Fulfilment.1. 1st Fulfilmentjob following a new DFU creation in Demand will generate item record and SKUsin Fulfillment module2. Demand Planner adds 10digit material number to CSC_U_Material_Attribute page and applies U code inU_GSPSIGAL1 file3. Next Fulfilment job following step 2 will generate item record and SKU with Iteration TBD in Fulfilment module4. Demand Planner adds material number with TBD iteration to CSC_U_Material_Attribute page and applies U code in U_GSPSIGAL1 field Fulfilment job occurs only on Monday, Thursday and FridayIn order to carry the GSPSignal 1 Code “U” into the Solver and PPR, U code must be applied at the TBDiteration as well as the ultimate PDM iteration.  B - Book toavailability (used to be in ABC Primary), 也就是说我forecast是有的，但是你不要买，就是为了book capacity而已。我们之前都是把forecast是48/102以下的order放成B code.  Solver logicB code items do not flow into the solver run (= don't show up in PPR), Logility will use the mark to make them as "buy to availability", meaning that we don't load the forecast and plan buy for themD - Dropped(Used to be in ABC Primary), Solver logic O - APAC，LIC的产品都放这个code, 意味着这些款会出现在plan arrival里面，但是进去Logilty之后，因为这个code, 不会被plan在PPR里面locally sourced styles (Used to be Primary), Solver logic L - L4L forChina L4L (Used to be in Alt.3) does systematically round to Min, Solver logic4 - GSPlogic (Used to be IP code), No solver logicE - Excessmaterial (Used to be Alt 1), No Solver logicF - Outlet (Usedto be Alt 1), No solver logicP – Placeholder (Used to be Alt 1), Nosolver logic 
              • GSP sigal 1
              • GSP Sigal 2
            • Flex 1
              • Local product category
            • Flex 2
              • Lineplan (assortment)
            • Flex 3
              • Priority
            • U_PRODCAT ( e.g. FTW for SS presentation calculation)
    • Qualification to stay in DFUVIEW / Fulfillment
      • DFU will be dropped out from DFUVIEW if no any sales history happen till the season end
      • SKUs not carrying over to future season will be eliminated from fulfillment page even the DFUs are still in system because we have history
  • Forecast Hierarchy
    • WS
      • L1 & L2
    • DTC
      • L1 & L2
• Demand
  • Statistical forecast( automatically generated for 2 years)
    • Model
      • Sales history
        • Data source
          • WS
            • Previous month shipment based on actual shipment (MKT, Free goods e.g. included in WS)
          • DTC
            • POS history by weekly
        • Data Cleansing/adjustment
          • Systematic process
            • Cleanse history due to curve fitting
              • CurveFitting:Maximum Percentage Zeros = 10 Minimum History Duration = 180 Maximum Percentage Below Mean = 90 Window Size = 12Outlier Factor = 2
          • Manual process (4 methods)
            • CSC-HIST
              • Original data source from outside ERP sys
            • CSC_DEMAND WORKBENCH
              • History override
              • Change history start date through Algorithm properties
                • DTC- Always set the History Start to a Monday
                • WS - The 1st of a month
            • D360 Worksheet
              • L2 DFU adjustment show up in the "Override > WKSHT" in demand workbench
              • L1 DFU adjustment show up in the "Impact of reconciliation" once L2 push to L1
            • CSC_FLEXIBLE_ALLOCATION
              • Purpose 1 - View forecast or history data
              • Purpose 2 - Run and validate the result of the reconciliation process to view the result
      • Algorithms- Lewandowski
        • DMI & FTC
        • DDE
        • Seasonality
        • Mean
        • Profile capability of PBF
          • Create a NEW seasonality profile or select from current profile liabrary - CSC_SEASONALITY MANAGER
          • Attach the profile to a DFU
            • CSC_SEASONALITY MANAGER
            • CSC_DEMAND WORKBENCH>seasonality>attach profile
    • Batch Jobs
      • Daily (9pm China time)
        • Fcst Reconciliation
          • WS
            • Order fence set up
              • CSC_ORDERFENCEDATE > U_ENDDATE
            • Order fence impact
              • Outside order fence
                • Style fcst push down to color based on color % of total fcst
              • Within order fence
                • Style fcst push down to color based on color % of order
          • DTC
        • Reload of future order from ERP sys
      • Weekly_Sunday (8AM Saturday )
        • Sales history
        • Recalculate the forecast
  • Consensus Forecast (Adjusted forecast)
    • Demand Shaping
      • CSC_DEMAND WORKBENCH
        • Override Fcst manually
        • Adjust Algorism properties - DMI & FTC
          • Dynamic mean impact - 0.5~2Higher the value, the system will put more weight on recent historyFTC = Forecast trend combination - 5~9Higher the value the trend line is flatter
        • Adjust seasonality impact
        • Create DDE
        • Adjust mean value
      • D360
        • Forecast override in orange colored fields
          • Lock the forecast - CSC_FLEXIBLE ALLOCATION
        • Adjust mean value
    • Review & Consensus
      • Style level after final adoption
      • Color level after assortment download
      • Order book after OTS
  • Exception management
    • Review exception
      • CSC_DFUEXCEPTION
      • CSC_NPI_EXCEPTIONS
        • U_PLANNER ID managed outside of the BY
    • Exception resolve
      • Refer to appendix
• Fulfillment_Buy plan for 18 month
  • Size
    • WS-P3 size curve in logility
    • Use Lift %
    • DTC - DTC sizing tool in JDA - CSC_DFUTOSKU
      • Come from POS - 3 years and grouped per sub-region/Brand/Product Class/Store Type
        • Size Management- Power BI_ DTC Child Variance Report
        • Batch Job _ Noon time at Tuesday, Thursday, Friday before the DP PASS
  • Rule
    • Rule basis - customer order duration
      • Set Up Page - CSC_CUSTORDERDATE_INPUT
      • Review and check - CSC_SKUDEMANDPARAM
      • Effective Time - the next day after FF batch job runs (9pm on Mon, Thu and Fri)
    • Rule Classfication
      • Forecast adjustment rule - 2 - Within the customer order duration use the customer order only
        • Forecast Adjustment ruleOne of the 3 rules is applied during the"Customer Order Duration" (setting is in the UDT)Rule 1: Use the forecast only. Does not considercustomer orders.Rule 2: Within the customer order duration, usecustomer orders only.Rule 4: Within the customer order duration use thegreater of the forecast or customer orders. And reallocates any excessforecast according to the demand pattern (Forecast adjustment weight)
      • Forecast consumption rule - 4 -Beyond customer order duration, customer order consume fcst backward, then forward
        • This rule applies to periods beyond the Customer OrderDuration dateConsumption logic can be applied perChannel DC (reference 3 layers of fulfilment aggregation: Store > Channel DC> OMNI DC) Rule 0: Customer Orders do not consume the forecast(Forecast only).Rule 1: Forecast consume customer orders forward, thenbackward.Rule 2: Forecast consume customer orders backward,then forward.Rule 3: Customer orders consume forecast forward, thenbackward.Rule 4: Customer orders consume forecast backward,then forward.
    • Rule Management
      • PARAMETER WORKBENCH
  • Calendars
    • Types
      • Master calendar_4
        • Holiday Calendar
        • Store Calendar
      • Ship/Arrival Calendar_6
      • Allocation Calendar_7
        • Attention call outs
          • Utilize the weight of 0 to skip a day of the week
          • Allocation weight must total 100 for a given week
          • Must always end with a repeat option
    • Management
      • Calendar creation
        • CALENDAR MANAGER
          • Add New Calendar through FE page
          • Copy existing calendar - "Go to" > "Copy Calendar"
        • CSC_CAL & CSC_CALDATA
          • Add CAL shell and fill the content in Caldata one by one
          • Specified in the CSC_SKUDEMANDPARAM
      • Edit existing Calendars call outs
        • Make sure to re-open the calendar after a holiday closure
        • Always start the allocation weight on Monday for DTC
        • The allocation weights exclu major holidays but can add additional records for specific holiday is allowed (e.g. CNY)
      • Layering master calendar to ship/arrival calendars
        • CSC_CAL > type Master Calendar name in master column
        • CALENDAR MANAGER > "Edit calendar" and specify master calendar wanna layer
      • Apply calendar to SKUs
        • Apply ship/arrival calendar to SKUs
          • CSC_NETWORK & CSC_SOURCING
        • Apply Allocation calendar to SKUs
          • CSC_SKUDEMANDPARAM > Edit multiple
          • PARAMETER WORKBENCH> create the group and rule then apply to SKUs based on the hierarchy
          • APAC allocation adjustment
            • S22 example
              • remove the allocation weight on 1/1 and 1/2/22 for Wholesale DC location will prevent the Wholesale Plan Arrival being generated on 1/1/22 and going up to OMNI DC. It will be planned on 1/3/22 instead. (1/1 &1/2 was the weekend)
            • Reason behind - To address 2 issues
              • 1) FF generates Plan Arrival on 12/31/21 because DC is closed on 1/1/22 CSC_CHN_WS_ALLOC
              • 2) To address TM1 data misalignment for DTC – Forecast allocated to 1/31/22 is not considered as S22 demand (Feb-Aug) in TM1 CSC_CHN_BRANDED_ALLOC
            • Call out to keep SS template to be aligned with the calendar
  • Safety Stock
    • SS Overview
      • Set up at sku size & location level
      • Time phased_ Presentation & Display Qty only
        • Time phase point
          • Eff. Date
          • Disc. Date
        • Maintenance FE
          • CSC_U_SSPRES_INPUT
            • Export / Import
        • Cases need to adjust
          • Order / Contract in
            • End the disc. Date
            • Extend the Eff. date to next season
          • Presentation increase/decrease - Add Pres Qty together
      • SS can apply to DTC store & omni DC level but not Channel DC level
    • SS Types
      • Presentation Qty
        • Step 1 -  Check total statistics forecast vs LYa:  Does the SOB% match with LY / our expectation? b: Does the sell amount generated from statistics forecast match with our sales forecast? if not, use the D360 to adjust the total sales forecastStep 2 - Compare vs. China OTB to calculate the presentation QTYOTB - Sales forecast amount after adjustment = Presentation amount
      • Display Qty
      • SSCov
      • Max SS
      • Min SS
    • SS Management
      • Presentation Qty & Display Qty
        • CSC_SSPRESENTATION
        • CSC_U_SSPRES_INPUT_Hign Level
          • Mass Import_Once per season
            • Export & Import
          • Manual Update_for new skus
            • Step- Add & ActiveSW Y/N
            • Check Method- SKUCOUNT in CSC_U_SSPRES_INPUT
      • SSCov , Max SS, Min SS
        • CSC_SKUSAFETYSTOCKPARAM
          • Edit Multiple
          • CSC_SSTEMPLATE & CSC_SSTEMPLATEDATA apply_ SSCov ONLY
        • PARAMETER WORKBENCH
          • Add parameter Group & rule then apply
      • CSC_SKUWORKSPACE
  • Supplemental Order - CSC_SUPORDERSKU
    • Reason to use Supplemental order
      • Below MOQ
      • Special Projects (i.e. Disney)
      • Executive overrides
    • Call outs
      • Delete date needed when creating the order
      • Status change
        • 1- Planned
        • 2- Fulfill , Once PO issued, change the status to fulfill by planner
      • Type always be "Forced"
  • Exception management - FF
    • CSC_SKUEXCEPTION
      • Critical
      • Action
      • Informational
  • Demand flow to fulfillment validation
    • DTC - DFUTOSKUFCST FE
    • WS - SKUEXTERNALFCST FE
  • Batch Job
    • SAP Order deadline pass to BY
      • cutoff for SAP Orders to make it into BY Demand – Orderbook line
        • 12:00am Friday Morning (Pacific Time)
      • cutoff for SAP Orders to make it into BY Fulfillment if Customer Order Duration is on
        • 12:00am Friday Morning (Pacific Time)
      • cutoff for SAP Orders to make it into the Solver run
        • 3:00pm Friday Afternoon (Pacific Time)
    • Fulfillment Batch Job _ Noon time at Monday, Thursday, Friday before the DP PASS

中心主题