How Everything Is Connected in NRP

Explanation of the logical data model. If you want to work with the code, you need to understand this. Might even help if you are using the code...

Transcript

1. Everything in NRP is connected to everything else.
2. NRP has 3 levels...and they are connected like so Actuals 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 Plan level depends on Recipes and prepares for Actuals.
3. This the core model, which you need to understand to work on the software. Sorry about that, but it’s as simple as possible - but no simpler.
4. In NRP, you are an Economic Agent.
5. You may be connected to other Agents by means of Agent Associations.
6. You are connected to all of the Economic Events you have participated in. They may be many types of Events: Work, Production, Consumption, etc.
7. Economic Events change Economic Resources. They may create, consume, use, cite, provide, or transfer Resources.
8. You may own or have custody or have some other responsibility for Economic Resources
9. Economic Events may be connected to Processes. They may be inputs to, or outputs from, Processes.
10. If the same Resource is an output from one Process and then an input to another Process, then those Processes are connected by a resource flow.
11. Economic Events may also Transfer Resources from one Agent to another by means of Exchanges.
12. If the same Resource is transferred in an Exchange and then becomes an input to a Process, then the Exchange and the Process are connected.
13. Likewise if the same Resource is an output from a Process and then transferred in an Exchange.
14. And likewise if the same Resource is transferred in one Exchange and then transferred again in another.
15. Processes and Exchanges may be planned by means of Commitments.
16. Commitments are plans for Economic Events that have not happened yet.
17. Commitments may be parts of Orders: “Customer/Purchase” Orders (planned trades) are groups of Exchange Commitments.
18. “Work Orders” (planned production) are groups of Process Commitments.
19. Everything has a Type.
20. Types are for configuring the system, setting policies, and modeling repeatable Process/Exchange flows.
21. Repeatable Process/Exchange flows are called Recipes.
22. A food processing recipe
23. Here’s how it all fits together in a flow again Actuals 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
24. Actuals: Salsa Events Plan: Order for 12 jars of Salsa Salsa Recipe for 1 lb of Salsa (fills 2 jars) Consumed 6 lb Diced Tomato Lot 234 Produced 6 lb Salsa - Bulk Lot 456 Salsa - Bulk Lot 456 Consumed 6 lb Salsa -Bulk Lot 456 Diced Tomato Lot 234 Package Salsa Today 6 lb Diced Tomato Today 6 lb Salsa - Bulk Today 6 lb Salsa - Bulk Today Cook Salsa Today Package Salsa 1 lb Diced Tomato 1 lb Salsa - Bulk Salsa - Bulk 1 lb Salsa - Bulk Diced Tomato Cook Salsa Here’s the Salsa flow
25. Process Input Event Output Event Resource Input Event Resource Value Flows - forward and backward Process Product Collaboration Reputation Income Resource Input Event Output Event Resource Output Event Resource Input Event Process Resource Input Event
26. The end