Planning with the vf:Vocabulary
Issue to discuss https://github.com/valueflows/valueflows/wiki/Planning-with-the-vf:Vocabulary
- First check for onhand and available vf:Resources, or previously scheduled vf:PlannedOutputs, that are not yet allocated to any demand.
- Allocate any that you find to the highest priority demand (where highest priority usually means earliest delivery date). (In terms of some of our discussions here, those are soft allocations, known only in the computer system.)
We discuss allocating resources in https://github.com/valueflows/resource/issues/22 Do we also need to have a way to allocate rea:Event/rea:Commitment? I understand that you use vf:PlannedOutput to describe planned output event.
- For demands that find no or insufficient available inventory or previously planned outputs, look for a vf:ProcessType that can create some. If you can't find a vf:ProcessType, suggest a purchase.
It looks like we can distinguish 6 sources for allocating resources as inputs for the process:
- 'internal'
- resources (observed) in the inventory
- events (planned) outputs of planned processes
- events (possible) outputs of known process recipes but not planned yet
- 'external'
- resources (observed) in someone else's inventory
- events (planned) outputs of planned processes
- events (possible) outputs of known process recipes but not planned yet
The 'internal' and 'external' seem to differ only that it may require a vf:Transfer, while internal we can do allocation without any transfers. The observed, planned, possible distinction seems to apply the same way for 'internal' and 'external'. With description of processes and resources shared across inventories, the 'internal' and 'external' line might blur even further. Especially if some individuals and groups offer services needed for those processes to many of the agents who have capacity to execute same processes recipes.