vf-apps-planning issueshttps://lab.allmende.io/valueflows/vf-app-specs/vf-apps-planning/-/issues2021-08-14T19:21:29Zhttps://lab.allmende.io/valueflows/vf-app-specs/vf-apps-planning/-/issues/1starting to document planning logic2021-08-14T19:21:29ZBob Haugenstarting to document planning logicI'm going through the NRP code and my memories of planning in several previous projects to surface issues and quirks that might be interesting and/or useful for ValueFlows. I'll write up these in separate comments in this thread as I fin...I'm going through the NRP code and my memories of planning in several previous projects to surface issues and quirks that might be interesting and/or useful for ValueFlows. I'll write up these in separate comments in this thread as I find or remember them. The order will be random.
Some of the techniques and terms will be from [Material Requirements Planning (MRP)](https://en.wikipedia.org/wiki/Material_requirements_planning), [Capacity Requirements Planning (CRP)](https://en.wikipedia.org/wiki/Capacity_planning), and [Finite Capacity Scheduling (FCS)](https://www.ifm.eng.cam.ac.uk/research/dstools/finite-capacity-scheduling/).
Many of the topics below will be sub-topics of [dependent demand explosions](https://valueflo.ws/appendix/dependent-demand.html). "Explosion" means to generate a process to satisfy the demand, guided by a recipe, which will generate dependent demands for the inputs to the process, which then may also need to be exploded, recursively until all generated demands are satisfied or no additional information can be found about how to satisfy a demand.
The stories and techniques will be examples from past practice but not necessarily what a vf-planning app should do. However, a vf-planning app would most likely encounter all of these problems and quirks.