NRP-CAS: Difference between revisions

From P2P Foundation
Jump to navigation Jump to search
No edit summary
unknown (talk)
(Major restructuring...)
Line 1: Line 1:
'''= "stands for network resource planning and contribution accounting. Network Resource Planning (NRP) replaces Enterprise Resource Planning (ERP)".'''
'''= "stands for network resource planning and contribution accounting. Network Resource Planning (NRP) replaces Enterprise Resource Planning (ERP)".'''


Line 6: Line 5:
=Description=
=Description=


"The system allows a network of agents to create a pool of shared physical resources that takes into consideration different property regimes and access rules. Every time an agent uses or consumes a resource in a process and logs that event for the process in the NRP-CAS, a contribution event is created for the owner of the resource. ... The inventory is presented as a long list of items that can be filtered by deliverable, domain, source, etc. The inventory is updated from a process, which can add new items to the inventory, subtract items, augment or diminish quantity. Processes have outputs that can be material resources kept in inventory, like new prototypes or products for example. They can also consume and use resources. The inventory can also be updated by purchasing.
"The system allows a network of agents to use a pool of shared ''resources'', material or virtual, under different property regimes and access rules, to engage in [[peer production]]. The use or consumption of a ''resource'' in a ''process'' by an ''agent'' constitutes an ''event''. ''Events'' and recorded in the NRP-CAS associated with ''processes'', which belong to ''projects''. The NRP-CAS uses the REA ontology (Resources, Events, Agents) which was first proposed by [[Bill McCharthy]], an accounting professor from Michigan State University.  


The first version of the NRP-CAS was developed in the context of [[Sensorica]], an open network engaged in open source hardware production. It was implemented by [[Bob Haugen]] as an embedded software developer with the Sensorica community.


For pool of shareables, the system is composed of :
You can find more about the NRP-CAS on [https://github.com/bhaugen/valuenetwork Github]. Also find more on [http://valuenetwork.referata.com/wiki/NRP-CAS the OVN wiki]
The NRP-CAS has been forked by other organisations. The effort evolved into the [https://valueflo.ws/ ValueFlows] initiative and [[HoloREA]]


* spreadsheets for tools and equipment, every spreadsheet representing a category: electronics, photonics, etc.
==Features==
* a spreadsheet to record spending on tools and equipment for the lab, called "Montreal labonline expenses"
* '''Inventory''': / resource management - is presented as a long list of items that can be filtered by deliverable, domain, source, etc. The inventory is updated from a process, which can add new items to the inventory, subtract items, augment or diminish quantity. Processes have outputs that can be material resources kept in inventory, like new prototypes or products for example. They can also consume and use resources. The inventory can also be updated by purchasing.
* a spreadsheet called "Stuff for Office-Lab" ."
* Project and process management
** '''Planning''': the use of recipes to plan collaborative work
** '''Resource allocation''': in processes, plan or log the use of resources.  
* '''Contribution accounting''': build a ledger of various type of contributions
* '''Benefit redistribution''': feed on the ledger of contributions to compute access to benefits, in redistribution of benefits, access to governance processes, access to use resources, etc.
* '''Transactions''': transfers of resources, exchanges of tokens, etc..


(http://valuenetwork.referata.com/wiki/NRP-CAS)


=History=


=Status=
[[Tiberius Brastaviceanu]] (Tibi) started, in early 2011, a spreadsheet-based resource planning system for Sensorica.


Tibi:
"I like the fact that everyone can see what's needed. We use a Google Spreadsheet to manage purchasing, and one can subscribe to changes. Every time someone adds items to it, or modifies an item, every one else who subscribed to this doc gets notified by email. The comment function also gets used a lot. Some of us would ask questions in context about a specific product or about some of its features, or even give some advice.


"I like the fact that everyone can see what's needed. We use a Google Spreadsheet to manage purchasing, and one can subscribe to changes. Every time someone adds items to it, or modifies an item, every one else who subscribed to this doc get's notified by email. The comment function also gets used a lot. Some of us would ask questions in context about a specific product or about some of its features, or even give some advice.
The spreadsheet also makes it possible for [[Sensorica]] members to cluster orders together to save on shipment and even on cost. Someone has the habit of sending an email to the group every time he orders something, in case someone else needs something form the same supplier. I find the spreadsheet much more convenient, because this issue can be resolved in there, without adding more noise to the mailing system.
 
The spreadsheet also makes it possible for SENSORICA members to cluster orders together to save on shipment and even on cost. Someone has the habit of sending an email to the group every time he orders something, in case someone else needs something form the same supplier. I find the spreadsheet much more convenient, because this issue can be resolved in there, without adding more noise to the mailing system.


I also like to have the links to the supplier right next to the item to order.
I also like to have the links to the supplier right next to the item to order.


I suppose in the future we'll have a list of things to buy, with filters on it, by type of product, supplier, etc. This list would be populated manually, one item at the time, or from Recipes. Every product will have suppliers associated with them, which are rated by the community in for lead time, quality, distance, etc. Members will be able to cluster items together. Optimizations can be made for cost, environmental concerns, etc. Users would and press a PURCHASE button and orders will be sent, if a relation is already established with the supplier, or by email... The PURCHASE action would also update the value accounting system with a financial contribution. This supposes that every item in the list of things to buy are already associated with projects, which would be the normal procedure of entering things to buy in the system."
I suppose in the future we'll have a list of things to buy, with filters on it, by type of product, supplier, etc. This list would be populated manually, one item at the time, or from Recipes. Every product will have suppliers associated with them, which are rated by the community in for lead time, quality, distance, etc. Members will be able to cluster items together. Optimizations can be made for cost, environmental concerns, etc. Users would and press a PURCHASE button and orders will be sent, if a relation is already established with the supplier, or by email... The PURCHASE action would also update the value accounting system with a financial contribution. This supposes that every item in the list of things to buy are already associated with projects, which would be the normal procedure of entering things to buy in the system."
(http://valuenetwork.referata.com/wiki/NRP-CAS)


[[Bob Haugen]] discovered Tibi's efforts from a post on G+ (social media app from Google, now extinct) and asked if he wants to transfer the spreadsheet management system on a more robust application, using the REA ontology (see above).


[[Category:Mutual Coordination]]
[[Category:Mutual Coordination]]
[[Category:P2P Accounting]]
[[Category:P2P Accounting]]

Revision as of 00:08, 13 January 2021

= "stands for network resource planning and contribution accounting. Network Resource Planning (NRP) replaces Enterprise Resource Planning (ERP)".

URL = http://valuenetwork.referata.com/wiki/NRP-CAS

Description

"The system allows a network of agents to use a pool of shared resources, material or virtual, under different property regimes and access rules, to engage in peer production. The use or consumption of a resource in a process by an agent constitutes an event. Events and recorded in the NRP-CAS associated with processes, which belong to projects. The NRP-CAS uses the REA ontology (Resources, Events, Agents) which was first proposed by Bill McCharthy, an accounting professor from Michigan State University.

The first version of the NRP-CAS was developed in the context of Sensorica, an open network engaged in open source hardware production. It was implemented by Bob Haugen as an embedded software developer with the Sensorica community.

You can find more about the NRP-CAS on Github. Also find more on the OVN wiki The NRP-CAS has been forked by other organisations. The effort evolved into the ValueFlows initiative and HoloREA

Features

  • Inventory: / resource management - is presented as a long list of items that can be filtered by deliverable, domain, source, etc. The inventory is updated from a process, which can add new items to the inventory, subtract items, augment or diminish quantity. Processes have outputs that can be material resources kept in inventory, like new prototypes or products for example. They can also consume and use resources. The inventory can also be updated by purchasing.
  • Project and process management
    • Planning: the use of recipes to plan collaborative work
    • Resource allocation: in processes, plan or log the use of resources.
  • Contribution accounting: build a ledger of various type of contributions
  • Benefit redistribution: feed on the ledger of contributions to compute access to benefits, in redistribution of benefits, access to governance processes, access to use resources, etc.
  • Transactions: transfers of resources, exchanges of tokens, etc..


History

Tiberius Brastaviceanu (Tibi) started, in early 2011, a spreadsheet-based resource planning system for Sensorica.

"I like the fact that everyone can see what's needed. We use a Google Spreadsheet to manage purchasing, and one can subscribe to changes. Every time someone adds items to it, or modifies an item, every one else who subscribed to this doc gets notified by email. The comment function also gets used a lot. Some of us would ask questions in context about a specific product or about some of its features, or even give some advice.

The spreadsheet also makes it possible for Sensorica members to cluster orders together to save on shipment and even on cost. Someone has the habit of sending an email to the group every time he orders something, in case someone else needs something form the same supplier. I find the spreadsheet much more convenient, because this issue can be resolved in there, without adding more noise to the mailing system.

I also like to have the links to the supplier right next to the item to order.

I suppose in the future we'll have a list of things to buy, with filters on it, by type of product, supplier, etc. This list would be populated manually, one item at the time, or from Recipes. Every product will have suppliers associated with them, which are rated by the community in for lead time, quality, distance, etc. Members will be able to cluster items together. Optimizations can be made for cost, environmental concerns, etc. Users would and press a PURCHASE button and orders will be sent, if a relation is already established with the supplier, or by email... The PURCHASE action would also update the value accounting system with a financial contribution. This supposes that every item in the list of things to buy are already associated with projects, which would be the normal procedure of entering things to buy in the system."

Bob Haugen discovered Tibi's efforts from a post on G+ (social media app from Google, now extinct) and asked if he wants to transfer the spreadsheet management system on a more robust application, using the REA ontology (see above).

Retrieved from "https://wiki.p2pfoundation.net/index.php?title=NRP-CAS&oldid=126649"