Plan granularity

[fosterlynn]

This might need some discussion, at least we all need to understand it.

Right now in OCP, there is process, there is work order (and customer order, but never mind that now). A process has commitments (tasks). A work order can have any number of deliverables that are not connected through one process flow. Those deliverables are output commitments, and each can have a whole process flow behind it.

In the new kamasi UI, there is one page (which I love) with one series of connected processes, resulting in a deliverable from the last process. (Or could be more than one deliverable, but still from the same series of processes.)

Also there is the "resource type list" feature in OCP, which allows bundling more than one recipe, so that planning can be done for a lot of things at once. I think FC will make a lot of use of resource type lists because they have a lot of miscellaneous tasks/processes to do each month in an ongoing way, and this will make it really easy to plan them. In OCP, those become one work order.

In VF, there is nothing yet in the whole area of bundling processes that are not related through resource flows into something that is bigger, but not yet a project in the context agent sense. It might become a parent process.

In any case, we have created something called a Plan in Kamasi that right now I have coded as equivalent to OCP work order in the api, but which really is not. It more corresponds in OCP to one committed deliverable in a work order. I don't see how to represent a whole work order with many deliverables on that new UI page. So I have had in mind to change the api so that one deliverable in a work order will be a Plan, especially since I have started working with the users on recipes and remembered the resource type list. But I haven't done it yet, and I have had some feeling I needed to see what the UI ends up looking like as we work through it.

Thus opening up this discussion.