valueflows

valueflows docs
git clone https://s.sonu.ch/~srfsh/valueflows.git
Log | Files | Refs | README

commit d98bd166bb1baa8b7d5867b2af924d3d5ab4c100
parent d2934cac7a4636f476634e38e30bd8403e305d2f
Author: elf Pavlik <perpetual-tripper@wwelves.org>
Date:   Tue, 17 May 2016 16:51:34 -0500

reorganize use cases

Diffstat:
Ause-cases/3d-printer.md | 34++++++++++++++++++++++++++++++++++
Ause-cases/broken-bike.md | 96+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Duse-cases/circular-economy/broken-bike-give-away.md | 32--------------------------------
Duse-cases/circular-economy/broken-bike-recycle.md | 28----------------------------
Duse-cases/circular-economy/broken-bike-repair.md | 35-----------------------------------
Duse-cases/equipment-repair.md | 10----------
Duse-cases/less-than-truckload-shipping.md | 23-----------------------
Duse-cases/make-3d-printed-part.md | 17-----------------
Duse-cases/potter-1.md | 14--------------
Duse-cases/potter-2.md | 16----------------
Duse-cases/potter-3.md | 13-------------
Ause-cases/potter.md | 47+++++++++++++++++++++++++++++++++++++++++++++++
Duse-cases/sensorica_3d_printer.md | 14--------------
Duse-cases/shipping-1.md | 15---------------
Duse-cases/shipping-2.md | 23-----------------------
Duse-cases/shipping-3.md | 8--------
Ause-cases/shipping.md | 78++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
17 files changed, 255 insertions(+), 248 deletions(-)

diff --git a/use-cases/3d-printer.md b/use-cases/3d-printer.md @@ -0,0 +1,34 @@ +# 3D Printer + +[Sensorica 3D Printer](http://nrp.sensorica.co/accounting/resource/411/) + +This is a case of rights and responsibilities that are aimed at coordination between humans in the use of a valuable piece of shared equipment. + +Sensoricans contributed to a fund to buy a commercial-quality 3D printer. + +The printer requires some training to use and can be damaged by misuse. So a few individuals have designated roles for managing its use, for example: + +* Managers: people who did not contribute to the fund must get permission for use from a manager. +* Trainers and certifiers: before you can use the printer, you must be trained and certified to be competent to do so. Otherwise, you must have a certified technician do your 3D printing work, and if it is for income-producing purposes, pay them. + +Users of the 3D printer for income-producing purposes must pay into a maintenance fee and also distribute some of the income to the people who contributed to the purchase fund. + +Sensorica has plans for more formal scheduling of the 3D printer, and also for digital access cards that would also automatically log use. + +## Make 3D printed part + +(based on Sensorica cases but simplified) + +1. Daniel makes a design for a 3d printed part and uploads it so others can access it. + +2. Jim makes a printed part using Daniel's design. + +* He also uses a 3d printer that lives in the lab. +* He also consumes some 3d printing filament already in the lab. +* After some effort, he creates a 3d printed part. + +This plus some transfers are represented in this cartoon: + +![cartoon1](https://cloud.githubusercontent.com/assets/3776081/15024416/6a801b4c-11fa-11e6-944b-955b7e5cadb9.png) + +![cartoon2](https://cloud.githubusercontent.com/assets/3776081/15024428/70d4e1e4-11fa-11e6-8229-25eb24cc9124.png) diff --git a/use-cases/broken-bike.md b/use-cases/broken-bike.md @@ -0,0 +1,96 @@ +# Broken Bike + +John has a broken bike and is not sure what to do with it. He lives in Haringey, London. + +## Repair + +### Entities + +**Agents** + +* John +* Dave, runs a bike shop that does repairs. + +**ResourceTypes** + +* Bicycle +* Bike shop + +*Resources* +* John’s bike with a dodgy brake +* Dave’s bike shop that provides a repair service + +### Resource flows + +* Exchange + * John gives Dave the bike +* Process + * Dave repairs bike +* Exchange + * Dave gives the bike back to John + * John pays money for the repair. + +### Issues + +* _Is this a process of repair or a temporary exchange?_ +* _Is the repair service a property of the shop or a skill of Dave?_ + +## Notes + +This is another case, like [Guerrilla Translation](https://github.com/valueflows/valueflows/blob/master/use-cases/guerrilla-translation.md), +where the same resource is both an input and an output. + +Inputs | Process | Output +------------- | ------------- | ----------- +Equipment | Repair | Equipment (repaired) +Parts | +Repair work | + +## Give away on local exchange network + +### Entities + +**Agents** + +* John +* Alice who is looking for a cheap bike and can repair it herself +* Haringey Freecycle exchange network + +**ResourceTypes** + +* Bicycle +* Exchange network email list + +**Resources** + +* John’s bike with a dodgy brake +* Local online Freecycle group email list + +### Resource flows + +* John finds the Freecycle group via a local index +* John posts a notice (intent?) about the bike on Freecycle +* Alice replies saying she would like the bike +* They arrange a time/place and John gives the bike to Alice + +## Take to local recycling centre + +### Entities + +**Agents** + +* John + +**ResourceTypes** + +* Bicycle +* Household waste recycling centre + +**Resources** + +* John’s bike with a dodgy brake +* The Haringey Recycling Centre. It takes many forms of waste. Some items suitable for reuse are passed onto other organisations. + +### Resource flows + +* John drops off the bike at the recycling centre. diff --git a/use-cases/circular-economy/broken-bike-give-away.md b/use-cases/circular-economy/broken-bike-give-away.md @@ -1,32 +0,0 @@ -# Bicycle - -John has a broken bike and is not sure what to do with it. He lives in Haringey, London. - - -## Give away on local exchange network - -### Entities - -**Agents** - -* John -* Alice who is looking for a cheap bike and can repair it herself -* Haringey Freecycle exchange network - -**ResourceTypes** - -* Bicycle -* Exchange network email list - -**Resources** - -* John’s bike with a dodgy brake -* Local online Freecycle group email list - -### Resource flows - -* John finds the Freecycle group via a local index -* John posts a notice (intent?) about the bike on Freecycle -* Alice replies saying she would like the bike -* They arrange a time/place and John gives the bike to Alice - diff --git a/use-cases/circular-economy/broken-bike-recycle.md b/use-cases/circular-economy/broken-bike-recycle.md @@ -1,28 +0,0 @@ -# Bicycle - -John has a broken bike and is not sure what to do with it. He lives in Haringey, London. - - -## Take to local recycling centre - -### Entities - -**Agents** - -* John - -**ResourceTypes** - -* Bicycle -* Household waste recycling centre - -**Resources** - -* John’s bike with a dodgy brake -* The Haringey Recycling Centre. It takes many forms of waste. Some items suitable for reuse are passed onto other organisations. - -### Resource flows - -* John drops off the bike at the recycling centre. - - diff --git a/use-cases/circular-economy/broken-bike-repair.md b/use-cases/circular-economy/broken-bike-repair.md @@ -1,35 +0,0 @@ -# Bicycle - -John has a broken bike and is not sure what to do with it. He lives in Haringey, London. - - -### Entities - -**Agents** - -* John -* Dave, runs a bike shop that does repairs. - -**ResourceTypes** - -* Bicycle -* Bike shop - -*Resources* -* John’s bike with a dodgy brake -* Dave’s bike shop that provides a repair service - -### Resource flows - -* Exchange - * John gives Dave the bike -* Process - * Dave repairs bike -* Exchange - * Dave gives the bike back to John - * John pays money for the repair. - -### Issues - -* _Is this a process of repair or a temporary exchange?_ -* _Is the repair service a property of the shop or a skill of Dave?_ diff --git a/use-cases/equipment-repair.md b/use-cases/equipment-repair.md @@ -1,10 +0,0 @@ -#Equipment Repair - -This is another case, like [Guerrilla Translation](https://github.com/valueflows/valueflows/blob/master/use-cases/guerrilla-translation.md), -where the same resource is both an input and an output. - -Inputs | Process | Output -------------- | ------------- | ----------- -Equipment | Repair | Equipment (repaired) -Parts | -Repair work | diff --git a/use-cases/less-than-truckload-shipping.md b/use-cases/less-than-truckload-shipping.md @@ -1,23 +0,0 @@ -#Less-than-truckload shipping (LTL) - -Excerpted from this [wikipedia article](https://en.wikipedia.org/wiki/Less_than_truckload_shipping). - -> Less than truckload shipping (LTL) is the transportation of relatively small freight. -The alternatives to LTL carriers are parcel carriers or full truckload carriers. -Parcel carriers usually handle small packages and freight that can be broken down into units -less than 150 pounds (68 kg). - -> LTL shipments typically weigh between 151 and 20,000 lb (68 and 9,072 kg). -Less than Truckload carriers use "hub and spoke" operations where small local terminals are the spokes -('end of line') and larger more central terminals are the hubs (also called Distribution Centers or DC's). -Spoke terminals collect local freight from various shippers and consolidate that freight onto enclosed -trailers for transporting to the delivering or hub terminal where the freight will be further sorted and -consolidated for additional transporting (also known as linehauling). -In most cases, the end of line terminals employ local drivers who start the day by loading up their trailers -and heading out to make deliveries first. Then when the trailer is empty they begin making pickups and -return to the terminal for sorting and delivery next day. Because of the efficiency of this order of operations -most deliveries are performed in the morning and pickups are made in the afternoon. - -This is another example where the transportation process is very different from the transfer of ownership. -And where the agents involved in the transfer of ownership (e.g. the buyer and the seller) usually know nothing -about the actual logistics involved. diff --git a/use-cases/make-3d-printed-part.md b/use-cases/make-3d-printed-part.md @@ -1,17 +0,0 @@ -### Make 3D printed part - -(based on Sensorica cases but simplified) - -1. Daniel makes a design for a 3d printed part and uploads it so others can access it. - -2. Jim makes a printed part using Daniel's design. - -* He also uses a 3d printer that lives in the lab. -* He also consumes some 3d printing filament already in the lab. -* After some effort, he creates a 3d printed part. - -This plus some transfers are represented in this cartoon: - -![cartoon1](https://cloud.githubusercontent.com/assets/3776081/15024416/6a801b4c-11fa-11e6-944b-955b7e5cadb9.png) - -![cartoon2](https://cloud.githubusercontent.com/assets/3776081/15024428/70d4e1e4-11fa-11e6-8229-25eb24cc9124.png) diff --git a/use-cases/potter-1.md b/use-cases/potter-1.md @@ -1,14 +0,0 @@ -# Potter makes pot and sells it - -* Agent: Potter -* Process: Make pot -* Inputs: - * clay - * potting labor - * pottery wheel -* Output: - * pot -* Exchange: - * Transfer pot, from potter to customer - * Reciprocal transfer money, from customer to potter - diff --git a/use-cases/potter-2.md b/use-cases/potter-2.md @@ -1,16 +0,0 @@ -# Potter makes pot as employee of company - -* Agent: Potter -* Process: Make pot -* Inputs: - * clay - * potting labor - * pottery wheel -* Output: - * pot -* Exchange 1: - * Transfer labor, from potter to company - * Reciprocal transfer money, from company to potter -* Exchange 2: - * Transfer pot, from company to customer - * Reciprocal transfer money, from customer to company diff --git a/use-cases/potter-3.md b/use-cases/potter-3.md @@ -1,13 +0,0 @@ -# Potter makes pot for community kitchen - -* Agent: Potter -* Process: Make pot -* Inputs: - * clay - * potting labor - * pottery wheel -* Output: - * pot -* Exchange? (or do we need a new name for gifts) - * Transfer pot, from potter to community kitchen - * The potter also uses the pot to bake bread, and eats food from the community kitchen, so the potter's reason for making the pot was to improve a shared facility. I don't think this is a reciprocal transfer, but it fits my imaginary redefinition of REA Duality, which we could discuss some time. Nobody understands it, though... diff --git a/use-cases/potter.md b/use-cases/potter.md @@ -0,0 +1,47 @@ +# Potter + +## Potter makes pot and sells it + +* Agent: Potter +* Process: Make pot +* Inputs: + * clay + * potting labor + * pottery wheel +* Output: + * pot +* Exchange: + * Transfer pot, from potter to customer + * Reciprocal transfer money, from customer to potter + + +## Potter makes pot as employee of company + +* Agent: Potter +* Process: Make pot +* Inputs: + * clay + * potting labor + * pottery wheel +* Output: + * pot +* Exchange 1: + * Transfer labor, from potter to company + * Reciprocal transfer money, from company to potter +* Exchange 2: + * Transfer pot, from company to customer + * Reciprocal transfer money, from customer to company + +# Potter makes pot for community kitchen + +* Agent: Potter +* Process: Make pot +* Inputs: + * clay + * potting labor + * pottery wheel +* Output: + * pot +* Exchange? (or do we need a new name for gifts) + * Transfer pot, from potter to community kitchen + * The potter also uses the pot to bake bread, and eats food from the community kitchen, so the potter's reason for making the pot was to improve a shared facility. I don't think this is a reciprocal transfer, but it fits my imaginary redefinition of REA Duality, which we could discuss some time. Nobody understands it, though.. diff --git a/use-cases/sensorica_3d_printer.md b/use-cases/sensorica_3d_printer.md @@ -1,14 +0,0 @@ -# [Sensorica 3D Printer](http://nrp.sensorica.co/accounting/resource/411/) - -This is a case of rights and responsibilities that are aimed at coordination between humans in the use of a valuable piece of shared equipment. - -Sensoricans contributed to a fund to buy a commercial-quality 3D printer. - -The printer requires some training to use and can be damaged by misuse. So a few individuals have designated roles for managing its use, for example: - -* Managers: people who did not contribute to the fund must get permission for use from a manager. -* Trainers and certifiers: before you can use the printer, you must be trained and certified to be competent to do so. Otherwise, you must have a certified technician do your 3D printing work, and if it is for income-producing purposes, pay them. - -Users of the 3D printer for income-producing purposes must pay into a maintenance fee and also distribute some of the income to the people who contributed to the purchase fund. - -Sensorica has plans for more formal scheduling of the 3D printer, and also for digital access cards that would also automatically log use. diff --git a/use-cases/shipping-1.md b/use-cases/shipping-1.md @@ -1,15 +0,0 @@ -A package was shipped to you on 10/28/2015 via U.S. Postal Service Priority Mail, Large Flat Rate Box - -Package ID: 94055102008287813824 - -* Your item was delivered at the front door or porch at 11:03 am on October 31, 2015 in XYZ, WI. -* Out for Delivery, October 31, 2015, 7:54 am, XYZ, WI -* Arrived at Post Office, October 31, 2015, 7:16 am, XYZ, WI -* Departed USPS Facility, October 31, 2015, 4:38 am, SAINT PAUL, MN 55121 -* Arrived at USPS Destination Facility, October 30, 2015, 8:57 pm, SAINT PAUL, MN 55121 -* Arrived at USPS Origin Facility, October 28, 2015, 10:21 pm, SPOKANE, WA 99224 -* Departed Post Office, October 28, 2015, 2:51 pm, MOYIE SPRINGS, ID 83845 -* Picked Up, October 28, 2015, 11:09 am, MOYIE SPRINGS, ID 83845 -* Shipping Label Created, October 28, 2015, 7:14 am, MOYIE SPRINGS, ID 83845 - -Each of the above were events that happened to that package, recorded by barcode readers, and sent to a tracking service. diff --git a/use-cases/shipping-2.md b/use-cases/shipping-2.md @@ -1,23 +0,0 @@ -#[Sensorica 3D Printer](http://nrp.sensorica.co/accounting/exchange/466/) - -* Purchased from ORD Solutions in Waterloo, Ontario -* Tried to get a relative of a friend to bring it to Montreal, but he couldn't do it. -* Requested shipping from ORD Solutions. -* ORD Solutions arranged transportation with another company. -* ORD Solutions invoiced Sensorica for shipping, but the actual transportation process -was conducted by this other company who was not named in the invoice. - -This is a fairly typical scenario, in that three agents are involved: - -1. the agent who provided the goods -2. the agent who received the goods -3. the agent who provided the transportation service - -Except that often the agent who does the actual shipping is named, -and the package can be tracked, as in -[shipping-1](https://github.com/valueflows/valueflows/blob/master/use-cases/shipping-1.md). - -But regardless, many (or in this case all) of the details of the shipping process -happen in the context of the shipping agent. Some details may be published and thus -known to the other agents in the exchange, but mostly they don't know and they -don't care. diff --git a/use-cases/shipping-3.md b/use-cases/shipping-3.md @@ -1,8 +0,0 @@ -# Nova Scotia fish - -Yes, this is insane. - -* Fishing boats catch fish in the ocean near Nova Scotia. -* The fish are packed in coolers and flown to China. -* Chinese workers clean and filet the fish. -* The fish are frozen and flown back to North American grocery stores. diff --git a/use-cases/shipping.md b/use-cases/shipping.md @@ -0,0 +1,78 @@ +# Shipping + +## Package with ID + +A package was shipped to you on 10/28/2015 via U.S. Postal Service Priority Mail, Large Flat Rate Box + +Package ID: 94055102008287813824 + +* Your item was delivered at the front door or porch at 11:03 am on October 31, 2015 in XYZ, WI. +* Out for Delivery, October 31, 2015, 7:54 am, XYZ, WI +* Arrived at Post Office, October 31, 2015, 7:16 am, XYZ, WI +* Departed USPS Facility, October 31, 2015, 4:38 am, SAINT PAUL, MN 55121 +* Arrived at USPS Destination Facility, October 30, 2015, 8:57 pm, SAINT PAUL, MN 55121 +* Arrived at USPS Origin Facility, October 28, 2015, 10:21 pm, SPOKANE, WA 99224 +* Departed Post Office, October 28, 2015, 2:51 pm, MOYIE SPRINGS, ID 83845 +* Picked Up, October 28, 2015, 11:09 am, MOYIE SPRINGS, ID 83845 +* Shipping Label Created, October 28, 2015, 7:14 am, MOYIE SPRINGS, ID 83845 + +Each of the above were events that happened to that package, recorded by barcode readers, and sent to a tracking service. + +## 3D Printer + +[Sensorica 3D Printer](http://nrp.sensorica.co/accounting/exchange/466/) + +* Purchased from ORD Solutions in Waterloo, Ontario +* Tried to get a relative of a friend to bring it to Montreal, but he couldn't do it. +* Requested shipping from ORD Solutions. +* ORD Solutions arranged transportation with another company. +* ORD Solutions invoiced Sensorica for shipping, but the actual transportation process +was conducted by this other company who was not named in the invoice. + +This is a fairly typical scenario, in that three agents are involved: + +1. the agent who provided the goods +2. the agent who received the goods +3. the agent who provided the transportation service + +Except that often the agent who does the actual shipping is named, +and the package can be tracked, as in +[shipping-1](https://github.com/valueflows/valueflows/blob/master/use-cases/shipping-1.md). + +But regardless, many (or in this case all) of the details of the shipping process +happen in the context of the shipping agent. Some details may be published and thus +known to the other agents in the exchange, but mostly they don't know and they +don't care. + +## Nova Scotia fish + +Yes, this is insane. + +* Fishing boats catch fish in the ocean near Nova Scotia. +* The fish are packed in coolers and flown to China. +* Chinese workers clean and filet the fish. +* The fish are frozen and flown back to North American grocery stores. + +## Less-than-truckload shipping (LTL) + +Excerpted from this [wikipedia article](https://en.wikipedia.org/wiki/Less_than_truckload_shipping). + +> Less than truckload shipping (LTL) is the transportation of relatively small freight. +The alternatives to LTL carriers are parcel carriers or full truckload carriers. +Parcel carriers usually handle small packages and freight that can be broken down into units +less than 150 pounds (68 kg). + +> LTL shipments typically weigh between 151 and 20,000 lb (68 and 9,072 kg). +Less than Truckload carriers use "hub and spoke" operations where small local terminals are the spokes +('end of line') and larger more central terminals are the hubs (also called Distribution Centers or DC's). +Spoke terminals collect local freight from various shippers and consolidate that freight onto enclosed +trailers for transporting to the delivering or hub terminal where the freight will be further sorted and +consolidated for additional transporting (also known as linehauling). +In most cases, the end of line terminals employ local drivers who start the day by loading up their trailers +and heading out to make deliveries first. Then when the trailer is empty they begin making pickups and +return to the terminal for sorting and delivery next day. Because of the efficiency of this order of operations +most deliveries are performed in the morning and pickups are made in the afternoon. + +This is another example where the transportation process is very different from the transfer of ownership. +And where the agents involved in the transfer of ownership (e.g. the buyer and the seller) usually know nothing +about the actual logistics involved.