Workshop Collaborator Survey

Technical

• Brief description of hardware that has already been built and tested. What it includes and doesn't.
• Can you organize around a version freeze of the existing build, or are you aiming to make improvements as a result of this workshop?
• If we have the space, how many people can build the hardware in a workshop setting? The best outcome would be if everyone goes home with a working product.

Organizational and Logistics

• Are you available to participate in a DPV to document/develop/shake down your workshop, 3-4 weeks prior to the workshop?
• If you can't make it for a DPV, can you make a site visit to assess logistics and make necessary preparations for the workshop? This allows you to test our tools and infrastructure as it will be used in the workshop.
• The target audience size is 24 people for the workshop. Do you think this is reasonable? What would be your ideal number of participants?

Open Source

• What is your hardware license?
• What is your software license?
• What off-shelf components are you using, and which ones are you building yourself?

Documentation

• Bill of materials? Is the BOM comprehensive to cover the entire build?
• What tools are required?
• Link to 3D CAD?
• CAM files?
• Source code?
• Diagrams, schematics?
• Build instructional?
• Would it be useful if you use documentation/dev support from 24 Summer interns? We will have about 24 people on site throughout the summer, and we can commit our people to help in some aspects of documentation/build procedure preparation.

Responsibilities

• OSE will set up registration on Eventbrite. Can you organize signup and send out logistics emails to participants prior to the event.
• Can you coordinate with our Hospitality Manager on working out logistics and food for participants? OSE will cook.
• Can you prepare the full CAD, BOM, and Instructional and Crash Course on the workshop of interest? Typical schedule is 2 hour intro/presentation on OSE Dev and Documentation. Then 2 hours of Crash Course on the design/systems engineering of your work. Then 2 hours on workshop preparation - hands-on skills. This should cover manipulating design files, accessing all source files, doing file conversions, etc.
• Based on the number of participants, can you create an 8-hpur work flow document for the build day?
• Can you prepare a Curriculum for Testing/Data Collection/Documentation on the third day? We will hold a Documentation Sprint on the third day to produce a Developer's Manual for the Industrial Robot.
• Are you willing to organize a documentation strategy with our Summer Interns, so they document while the build happens?
• Can you order all of the parts required?
• Are you comfortable with a 50/50 revenue share of workshop revenue after all materials/infrastructure costs are covered? Any infrastructure built for the event becomes property of OSE to further its educational mission.
• Are you comfortable with running a workshop for about 24-36 participants, including a documentation team consisting of OSE Summer DPVs?