... | ... | @@ -2,7 +2,7 @@ Manufacturing and ERP (Enterprise Resource Planning) systems typically document |
|
|
|
|
|
Computerized BOMs and Routings came from Material Requirements Planning (MRP), which was one of the first business computer systems that did something that could not have been done practically by manual methods. Here's some of the [history](https://en.wikipedia.org/wiki/Material_requirements_planning#History).
|
|
|
|
|
|
Value Flows uses a combination of Bills of Material and Routings that we call Recipes.
|
|
|
Valueflows uses a combination of Bills of Material and Routings that we call Recipes.
|
|
|
|
|
|
# Why?
|
|
|
|
... | ... | @@ -41,7 +41,7 @@ Recipes can handle all the problems mentioned above: |
|
|
|
|
|
# Separate BOMs and Routings do not work for resource flows. Recipes do.
|
|
|
|
|
|
Value Flows are another name for resource or material flows. Such flows are usually represented by [Input-Process-Output models](https://en.wikipedia.org/wiki/IPO_model). See https://en.wikipedia.org/wiki/Material_flow_analysis
|
|
|
Valueflows are another name for resource or material flows. Such flows are usually represented by [Input-Process-Output models](https://en.wikipedia.org/wiki/IPO_model). See https://en.wikipedia.org/wiki/Material_flow_analysis
|
|
|
|
|
|
A Recipe is an input-process-output model, where the Processes are connected when an output from one Process becomes an input to another Process.
|
|
|
|
... | ... | @@ -53,7 +53,7 @@ The Processes that have resource flow dependencies can also live in different sy |
|
|
|
|
|
Because all of the relevant information lives in the same structure, material and capacity and workflow requirements can all be planned together, at the same time, and synchronized with each other.
|
|
|
|
|
|
Requirements for inputs from other Agents can be sent as Value Flows Intent messages to the other Agent, who can schedule their own related production and respond with a Commitment to a delivery time.
|
|
|
Requirements for inputs from other Agents can be sent as Valueflows Intent messages to the other Agent, who can schedule their own related production and respond with a Commitment to a delivery time.
|
|
|
|
|
|
Moreover, all of the related schedule changes, new requirements, etc., can be scheduled or rescheduled event-by-event, so no massive overnight planning program ever needs to be run.
|
|
|
|
... | ... | @@ -67,7 +67,7 @@ Or https://valueflo.ws/examples/ex-planning.html#simple-plan-from-recipe |
|
|
|
|
|
Most economic activity involves more than one Agent (where an Agent is an individual person or organization like a company or a cooperative). Many manufactured products include components made by different Agents.
|
|
|
|
|
|
The Agents might be organized in a supply chain (usually an upside down tree with maybe several tiers of suppliers producing inputs to components made by the next tier and tier-by-tier arriving at a final product). Automobile manufacturing is organized like that. ValueFlows evolved from some supply chain software conversations around the year 2000 (among other influences). See for example [REA, a semantic model for supply chain collaboration](http://mikorizal.org/REA_+A+Semantic+Model+for+Internet+Supply+Chain+Collaboration_2000.pdf).
|
|
|
The Agents might be organized in a supply chain (usually an upside down tree with maybe several tiers of suppliers producing inputs to components made by the next tier and tier-by-tier arriving at a final product). Automobile manufacturing is organized like that. Valueflows evolved from some supply chain software conversations around the year 2000 (among other influences). See for example [REA, a semantic model for supply chain collaboration](http://mikorizal.org/REA_+A+Semantic+Model+for+Internet+Supply+Chain+Collaboration_2000.pdf).
|
|
|
|
|
|
Other forms of economic networks include [economic ecosystems](https://www.academia.edu/10252910/The_uneasy_transition_from_supply_chains_to_ecosystems_The_value-creation_value-capture_dilemma), which don't necessarily have a "head" Agent like auto supply chains, and are organized in a loose network instead of a tree. Android phones are an example, where Google is a dominant Agent but not the only important one: Samsung probably sells more phones, and here's a list of [36 Android phone manufacturers](https://phandroid.com/manufacturers/).
|
|
|
|
... | ... | |