Create Recipes Setup Resource Types Recipes can be part of setup. But if you are doing R&D work, you will be creating recipes as the result of that work. Recipes are just what they sound like, but….. Recipes fit into the NRP here... Distribute Income Exchange Resources Create Resources
Plan Recipe Input Event Output Event Resource Input Event Resource Process Planned Input Planned Output Planned Input Process Process Type Input Type Output Type Resource Type Input Type Resource Type Process Type The recipes create a context to plan and log the work of the network.
◦ Processes ◦ Materials ◦ Equipment ◦ Designs ◦ Work ◦ Etc. In ERP terms, it’s a combination of bills of material and routings and suppliers. Here are a few examples to give you some ideas….. What’s in a Recipe
resources into different output resources, for example: ◦ Assemble a robot from metal, wires, computer chips, software, etc. ◦ Bake bread from flour, yeast, water, etc., using an oven. • Workflow Recipes: change the same resource into a different stage of the same resource, for example: ◦ Translate a source document, edit the translation, format for publication, and publish. ◦ Harvest, dry and garble (refine) batches of herbs. • Abstract Recipes: ◦ Could be either of those types. ◦ Can be used to define more general business processes and methods that produce any kind of output. ◦ The output can be tangible or intangible. ◦ Likewise the inputs. ◦ What we are trying to say here: ▪ Recipes are a very general concept that can be used in a lot of different ways. ▪ Imagine! • Resource Type Lists: A recipe creates one type of resource. But you can also group recipes into a list, so that multiple related outputs that can be created in parallel can be planned together.
C Process Type 1 Resource Type D Resource Type B Resource Type A Source (Agent) output input (consume, use, cite, work) output input Manufacturing recipes contain all the information required to manufacture a product from components. They are combinations of bills of material, processing instructions (routings), other inputs like labor and equipment requirements, and possible suppliers for the inputs. They are structured like an upside down tree. Manufacturing recipes are recursive structures. In other words, if an input component has a recipe itself, that recipe will be incorporated into its parent, so you can view a processing tree from parents through children unto many generations. A typical manufacturing recipe would be for making some raw materials into components and then assembling the components into an end product. But they are not limited to typical hard goods. Anything that is created out of other resources of any type can use this type of recipe.
3 Process Type 2 Resource Type X Resource Type X Resource Type Y create change change Workflow recipes describe a sequence of processes used to complete work on one resource. They create a series of stages that one resource will go through until it is finished. A typical workflow recipe would be creating, editing, formatting and publishing a document. After it has been created, the same document goes through changes to reach its final form. This type of recipe can also be used to define business process steps.
process flows. - Outputs must be different Resource Types from inputs. Workflow recipes + Inputs and outputs may be the same Resource Type, just changed. - Only one changeable Resource may appear in a workflow. - Process chains must be sequential: no branching. The two styles may be combined in overall value streams, where a workflow product goes into an manufacturing process, or vice versa. You can also include both types into a Resource Type List, which groups recipes that can be planned together. Tradeoffs between Types of Recipes
from inventory. Examples: raw materials to be shaped into something else, components to be attached to an output product. Use: the used resource will still exist after it is used. Examples: equipment, space. Cite: like a scientific citation, giving credit for ideas, designs, etc. No direct effect on the cited resource. Work: as the word suggests, work on the process. Manufacturing recipes only: Outputs: Produce: create a new Resource. Workflow recipes only: Inputs: To be changed: the input Resource will also be changed as an output. Outputs: Create changeable: create a new Resource that will subsequently be changed in the rest of the workflow. Change: the Resource that was to be changed, has now been changed as an output. Recipe Inputs and Outputs
end items and a due date, generate the plan from the end item to its inputs, to the outputs leading the inputs, to their inputs, etc. • Forward-scheduling from a Recipe: ◦ Start with the inputs with no predecessors and a start date, generate the plan from the inputs to their outputs, to the inputs that want the outputs, etc. • Forward-scheduling from a Resource: ◦ Start with a Resource and generate the plan based on its recipe. ▪ Translation: start with a source document ▪ Auto repair: start with an auto that needs repair. Recipes generate plans like this...
the Resource Types page from the menu, then select the Resource Type that represents the final output. From the Resource Type page, select the Create Manufacturing Recipe button. On the Manufacturing Recipe page: • First, add a process type to create the output resource type. • Then, create inputs: materials, labor, equipment, etc. • For each input, create either a source or a process type. • If the input is labor, no need to create a source. • If the input is material, the source will be who can you get it from. • If it's a process type, restart from the top.
the Resource Types page from the menu, then select the Resource Type that represents the final output. From the Resource Type page, select the Create Workflow Recipe button. On the Workflow Recipe page: Add steps in the workflow as process types as needed, starting from the earliest. The actions will be created automatically based on the pattern. You can also add additional inputs such as work.
commoning or peer production processes...by those involved in other projects… ...an online depository of peer production process maps might allow collaboration between networks and projects… ...it would contribute to the production of better commons… ...this way of interlinked collaboration can also be seen as collective work on the development of the commons knowledge… ...[expertise as a pool resource]...” - Fragments from an idea by Örsan Şenalp