STEAM Camp RFPs: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 12: Line 12:
[[STEAM Camp RFP Specfications]].
[[STEAM Camp RFP Specfications]].
==Specific Deliverable Requirements==
==Specific Deliverable Requirements==
Each item in the [[Development_Spreadsheet_Template#Simple_Template]] has concrete requirements embodied in the Protocol for that development step. Click on the specific development step to see additional information about that step and the protocol for executing that step. The protocols may be found in the green Hint box.
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=
=Instructions to Bidders=

Revision as of 21:21, 27 September 2019

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.

Specifications

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: list the Bid Links (1-50) for the microtasks that you can deliver. To do this, fill out this Proposal Form with links of the tasks that you can handle. The tasks are granular in nature, and bids are being created at the level of these microtasks. Microtasks 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.

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.

Include the Boilerplate

Explain that the RFP is not a contract and that responding to it does not guarantee selection. Make sure to include information that will make a vendor’s response worth the vendor’s time. Lay out details on the budget, the contract, the form of payments and the evaluation of work while the project is active.

Include any legal, copyright, insurance and ethical considerations for the vendors to consider. This includes, but is not limited to, confidentiality agreements, minority vendor requirements, local regulations, safety considerations and business practices.

Give Additional Instructions

Specify any distinct instructions on how the responses should be formatted. Instruct the vendors on how you want to see their proposal numbers, what information they should include with their proposals, such as copies of insurance information or business licenses.

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.