valueflows

commit c2bbd8ca42f81c2c2c9ccf63acb712d2e2ba935d
parent 619cb32cb977327455cc904e9bc27452dc5f584a
Author: Bob Haugen <bob.haugen@gmail.com>
Date:   Fri, 29 Mar 2019 08:06:36 -0500

first commit
Diffstat:
A
use-cases/planning-scenario-wind-turbine.md
 | 
11
+++++++++++

1 file changed, 11 insertions(+), 0 deletions(-)
diff --git a/use-cases/planning-scenario-wind-turbine.md b/use-cases/planning-scenario-wind-turbine.md
@@ -0,0 +1,11 @@
+# Demand-driven example: $30 wind turbine electrical generator
+
+![wind turbine](https://cdn.instructables.com/FWE/4XVX/HSVGHLJZ/FWE4XVXHSVGHLJZ.LARGE.jpg)
+
+One interesting feature of this example is an open-source recipe that was published on the Web: http://www.opensourcelowtech.org/wind_turbine.html
+
+In order to implement it, we [copied and pasted the recipe into NRP](http://nrp.webfactional.com/accounting/xbomfg/16/). But that is because NRP was not able to plan from recipes from the Web, and also because doing so will require recipes published in some shared vocabulary (VF maybe?)
+
+If that happens (recipes published in repositories using common vocabularies) then open source hardware can become like open source software: reusable, collaborative, forkable, etc.
+
+Here's the [plan generated from the recipe](http://nrp.webfactional.com/accounting/order-timeline/7/)