NRP-CAS

= "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 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.

For pool of shareables, the system is composed of :

• spreadsheets for tools and equipment, every spreadsheet representing a category: electronics, photonics, etc.
• a spreadsheet to record spending on tools and equipment for the lab, called "Montreal labonline expenses"
• a spreadsheet called "Stuff for Office-Lab" ."

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

Status

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 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.

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." (http://valuenetwork.referata.com/wiki/NRP-CAS)