Skip to main content

Production Planning

  • February 24, 2026
  • 2 replies
  • 31 views

aaron-whipps
Forum|alt.badge.img+2

Hello

I’m currently working on a Production Planning base, which is essentially a way for us to communicate with factories on the projected production they can expect from us for the forthcoming months. Currently there are two sets of data:

  • Projected Units 
    • Quantity attached to a “Launch” or a “Deal”. 
  • Confirmed Units.
    • Quantity of confirmed units which have Purchase Orders attached

As an example, we have a deal across “P6 & P7” (period/phase) with a customer and projected around 500k units. The problem is that the factory is not going to produce all 500k units at the same time and this deal stretches over a period of time - which based on the customers sales calendar is Feb-Mar-Apr. That is their sales window, so we need to work backwards around 10 weeks for shipping and then an additional 30 days for production.

I’m currently trying to figure out the best way to disperse the 500k units realistically across the full period span so we can give the factory an idea of when we expect these units to fall into their production. My problem is they’re attached to a single deal, and I’m not entirely sure the best way to split them out. I’d welcome any suggestions!

2 replies

TheTimeSavingCo
Forum|alt.badge.img+31

Hm, and so with reference to your example of Feb - Apr, production would start Oct-ish and run to Jan?

If so, perhaps we could create a new table called ‘Production Planning’ or something where each record represented a single time period that you want to disperse production by for a single PO.  So if that was months then we’d have the following records:

  1. Oct - PO001
  2. Nov - PO001
  3. Dec - PO001
  4. Jan - PO001

And we’d set the amount to produce for each month as well as update it with the amount actually produced for logging

If you could let me know what issues you think this setup might face we can see what we can do to fix it!


aaron-whipps
Forum|alt.badge.img+2
  • Author
  • New Participant
  • February 25, 2026

Hm, and so with reference to your example of Feb - Apr, production would start Oct-ish and run to Jan?

If so, perhaps we could create a new table called ‘Production Planning’ or something where each record represented a single time period that you want to disperse production by for a single PO.  So if that was months then we’d have the following records:

  1. Oct - PO001
  2. Nov - PO001
  3. Dec - PO001
  4. Jan - PO001

And we’d set the amount to produce for each month as well as update it with the amount actually produced for logging

If you could let me know what issues you think this setup might face we can see what we can do to fix it!

 

Hey Adam! Thanks for your reply! I’ve done some more investigating today and have created a Junction Table which distributes every deal across production months - still testing but will let you know if it works out!