NRP = Network Resource Planning: operational software for open value networks and other next-economy organizations. This tutorial explains exchanging resources with other networks or external organizations.
outside your network. This may all be triggered by a customer order, which generated a plan, which got completed. Or you may be selling or trading things created without a customer order. Or you may be exchanging within the network between people or projects as part of the creation of value. Exchanging outgoing or internal resources fits here... Setup Organization Plan Work Purchase Inputs Contribute Funds Coordinate Work Create Recipes Setup Resource Types Distribute Income Exchange Resources Create Resources Setup Exchange Types
Giving event | Receiving event Receiving event | Giving event Exchange com pens ation Exchanging resources is a matter of give and receive. Two silly-looking agents exchange resources. In the first resource transfer, the agent on the left gives a resource to the agent on the right, who receives it. Then, in compensation, the agent on the left gives a different resource to the agent on the right, who receives it. Note from the perspective of the network, you will not always have both a Give and a Receive.
addressed in the Planning tutorial.) Here you can select a type of outgoing exchange and create it. Or, if you create a customer order, it will automatically create the outgoing exchange. The Exchange List shows all outgoing exchanges. Demand
usually something that was created inside the network. In the case of this sale example, the network or other agent gives one or more products or services and receives some sort of payment. The network can define any number of specific types of outgoing exchanges besides typical sales. Outgoing exchange example Sale Exchange Payment Transfer Product or Service (Resource) Shipment Transfer Cash (Resource) Note: Even though it looks like it above, an outgoing exchange doesn’t have to involve money (dominant or alternate currencies). It could be barter, time bank exchange, etc. We haven’t had a requirement to support payment in something other than money, but the underlying model will easily support that, and we can make it so, if anyone needs it. give receive
order. In fact, creating a customer order creates the plan for a corresponding exchange behind the scenes, in addition to any processes needed to produce what was ordered. (The system assumes you will ship or deliver what the customer ordered.) Outgoing exchanges and Orders Customer Order Exchange Process Planned Output Planned Shipment Actual Output Actual Shipment
an order. Of course in the real world, many are made without customer orders. The selection in the dropdown is all the outgoing exchange types configured for the network. Outgoing exchanges Without Orders
context agent’s page, selected from the Organization page. The selection in the dropdown is all the internal exchange types configured for the network. Internal exchanges will always have both a Give and Receive event on the transfers because the whole scope of the exchange is inside the network. Internal Exchanges
information is on the left, the transfers related to the exchange on the right. Here a deliverable is made to a sponsor in exchange for a sponsorship payment. Work that was done to make the exchange happen can also be logged here. Exchanges
are completely configurable for the network. This happens through Exchange Types (see that setup tutorial). The title at the top reflects the name of the exchange type. The rest of this side is the same for all types of exchanges. Context and date are required, the rest are optional. The exchange must be saved here before anything can be entered on the right side of the page. This can then be modified at any time.
is divided into Transfers and Reciprocal transfers. Each section is named after the Transfer Type defined in Exchange Type setup. All exchanges also have a Work section so you can record work done just for this exchange. You can add a commitment (promise, plan) or an actual transfer. You can also edit or delete transfers and commitments. For a commitment, you can create the actual transfer based on that commitment. In this case the membership fee has been committed to, but not paid yet.
promise to make a transfer. Here is the information that can be entered for a transfer commitment. You may see Transfer From or Transfer To, or both, depending on the type of transfer. The Resource Type list is configured for the exchange type. If you don’t see what you want, an admin can re- configure that. Description, Value, and Unit of Value are optional. Value fields will only appear if the transfer is currency.
is variable, based on the configuration done for the Transfer Type. The date is always there and is required. You will see “Transferred from”, “Transferred to”, or both, depending on the configuration. If not showing, this will default will be the context agent. The list is governed by configuration. “Quantity” and “Resource type” are always there and are required. The “Resource” and “Description” are optional. Value fields will only show if currency is not being transferred.
rewarded in a value equation”, you have a choice if you would like this included as your contribution. If you uncheck it, it will not be considered for income to you. If you see “Can be distributed in a value equation”, this transfer will show as an option for source of a distribution to people or projects using a value equation. “Event reference” will only show for currency related transfers, and is freeform for anything useful to refer to the real world transfer, such as check number.
configured to allow creation of a new resource, you will see this resource information. You would add to an existing resource if you already had some of the same type, for example here you are adding to an existing virtual account or wallet. For a new resource, you need to enter all the resource information. Identifier is required, others are optional. The locations and resource access role lists are pre-configured for the network. For a virtual account, the owner role should be set.