From Open Source Ecology
Jump to: navigation, search

Executive Summary

Open Source Ecology is soliciting Reqeusts for Bids for curriculum. The curriculum involves development prototypes related to the Open Source Microfactory STEAM Camp. The STEAM Camp is a hands-on immersion training opportunity for people interested in creating the open source economy, with the curriculum shown at STEAM Camp 9 Day Curriculum. We are planning 12 STEAM Camp events to be held in 12 different locations worldwide in early 2020, with a 50/50 revenue share with instructors.


We are looking for several curriculum modules. Each module contains working physical prototypes and documentation. Each module requires some technology development that integrates that technology with the rest of the OSE product ecosystem. The 3 main deliverables are (1) Technology development, (2), documentation, and the (3), the actual curriculum. The curriculum needs to include all the materials that a teacher would need to present a lesson on this topic in the time frame specified for each lesson. The lesson includes a build of the actual technology from scratch. This means that the design must be as simple as possible, and that the build must be designed to be easy and quick, so it could fit within a specific lesson's time frame.

We also pay a lot of attention to replicable production engineering. Thus, we require design using widely available, common, off-the-shelf, consumer and industrial parts. We require that only common tooling (such as the D3D Bootstrap Universal Fabricator 3-in-1 CNC machine, discussed below, and other simple tools) be required for the builds, to maintain access to production in a small microfactory. At the same time, we are developing well-refined production engineering with an end goal of producing marketable products.

The technology RFPs include:

STEAM Camp RFP Specfications.

Specific Deliverable Requirements

Each item has a wiki link associated with it. Work product for that item must be put at that link. All work product is open source, and enters the public domain as soon as it is entered.

Instructions to Bidders

To bid on any of the items, or parts of items: select a project for bid. To do this, fill out this Proposal Form with links of the project. The link of the project is the wiki link to the Requirement for that project - and there are multiple projects people can bid on - so we are asking for the link to identify the preject. If you can only do specific parts of a bid request - that also works for us - but please indicate which parts you can and cannot deliver (that's in the Proposal Form as well). Projects have many dependencies (for fit into the overall project), so make sure that you read all the dependencies outlined for each bid item. When you fill out the Proposal Form, an email is sent automatically to notify OSE of your submission.

All work product will be linked to the development spreadsheets - which link to wiki pages for specific deliverables (which we will set up once you get going).

Review all dependencies information, and submit any questions regarding bids through the Proposal Form. The Proposal Form is open access for other bidders to review, so you can collaborate with other bidders at any time.

All bids are open for inspection by anyone including other bidders. Bidders may submit as many bids as they like, and they are encourage to cooperate with one another on delivering work product. The person doing a bid can subcontract any of the work, but the bid submitter is the only official contact and authorized agent.

More Information and Intellectual Property

The RFP that is submitted is not a contract and OSE responding to it does not guarantee selection. Selection of a bid is marked by an acceptance in writing. Payment is made at the end of the specified work period. Partial payment shall be made if tasks are not completed according to the conditions of satisfaction. Conditions of satisfaction are typically the replicability of a certain build or experiment to predefined quality standards, which will be made explicit prior to any bid being accepted. Result Requirements will be defined before the projecgt, and are part of Test-Driven Design.

Evaluation of work should happen openly, as our goal is to create a collaborative process. We encourage bidders to upload material on an ongoing basis to facilitate constructive feedback.

All the content created or intellectual property is assigned to OSE as the legal holder of the IP. OSE publishes all of its content under OSHWA and OSI compliant licenses for the benefit of all humankind.

By submitting your work to OSE, you agree to have your work shared openly, to benefit all of humankind, without being appropriated or enclosed by special interests.

You are required to submit all work on an ongoing basis as links to results published on your work log on the Wiki. This means that all your work becomes public as soon as it's generated. Payment is based on results, and any incomplete results still move the work forward as they are published openly on the wiki.

When submitting results, you are required to ask regarding public content only - content that you place on the wiki. This allows for feedback by any other team member, as we work openly and collaboratively. That means that we will not necessarily respond to results that are help privately (such as in your emails) - please publish all results on the wiki when discussing them. Only results on the wiki are admissible for discussion, so that all work happens in the bublic.

Work Product Submissions

Content shall be placed on the wiki, according to the specific instructions and How-Tos provided for the various developments.

Once you are done, please let us know by filling out the Work Product Submission Form.

Describe the Selection Process

Include your invitation to bid with a few paragraphs regarding the selection process. Let the vendors know whether or not they will be notified if they do not get the job as well as what to expect if they are selected for the job.