I need to map specific customers to local DCs in a region. Rather than a 1-to-1 relationship, each customer could be serviced by multiple DCs.
A) I've created a Customer Forecast module that contains customer demand data by customer, product, week.
B) I need a mapping module that allows the end-user to make local DC selections (using a Boolean) by customer.
C) I've created a Local DC Forecast module that should bucket demand by specific customers into their assigned local DCs dimensioned by local DC, product, week.
NOTE: if a customer is serviced by two local DCs, I'd like the demand from that customer to be a simple proportion of 50/50% into each local DC. My issues is getting from point A to C. The current mapping module I've created (by local DC, customer) doesn't do the trick. I am unable to SUM or LOOKUP using it.
Quick question, why does it have to be a Boolean? My thinking is to create a module with customers in the rows, products in the columns and having a line item for the DC, which is formatted as the DC list. That way, you can do sums and/or lookups, as well as having multiple customers going to the same DC. Does this get you home?
I think this is the approach I want to go down; however, each customer also needs to be able to be fulfilled from multiple DCs. For example Customer A may have demand of 1,000 units that gets fulfilled from Charlotte, Atlanta, and Jacksonville (333 units each; simple split 33%). Customer B may have demand of 1,000 units that gets fulfilled from Jacksonville only.
Here's a little more context if it helps. We're receiving demand data as a file and planning upstream from a supply perspective (so in reverse). I've attached a picture. Essentially, I'm trying to aggregate the volume on the DC end.
Here's a little more context if it helps. We're receiving demand data as a file and planning upstream from a supply perspective (so in reverse). I've attached a picture. Essentially, I'm trying to aggregate the volume on the DC end. Sorry, not sure which thread to reply on. My apologies.
One last question. If Customer Demand module is modeled by Time, then I probably wouldn't want the DC Proximity module to also contain the calculation of demand by DC since this is where users will select allocations in general (not each week). That said, would you envision 4 modules to accomplish aggregation of DC Demand? I.e., 1) Customer Demand - by Customer, Product, Time; 2) DC Proximity - by Customer, DC; 3) Demand Disaggregation - by Customer, Product, DC, Time; and 4) Local DC Demand - by Product, DC, Time? Ideally, I'd like to by pass module 3 Demand Disaggregation, but it seems that there may not be an efficient way to allocate the demand appropriately due to the many:many condition...
FYI - the steps you've outlined were successful (THANK YOU!) in getting from A to C, but now I'm wondering if I can cut that passthrough module (3 Demand Disaggregation).