# [OSHS] Colaborative notes fifth seminar (14.06.2023)

For each of the groups:
1. What is your specific motivation to document hardware and for whom?
Motivation: Making the Orbita accessible and affordable for a wider audience, as well as for education purposes. By providing an open-source hardware approach
For whom: teachers for building it at school with pupils, parents with children, makers interested in rebuilding it in a low budget way, musicians willing to use it to create new sounds or sequences for their audio projects.
2. How do you plan to document your hardware in terms of:

- Contents:
- Index of product documentation
- Introduction & Motivation
- BOM
- Step-by-Step Assembly Instructions
- Operation Introductions
- ...
- Formats: Manual, CAD model, Video, physical model
- Dissemination channel: GitHub, Playtronica Website, Youtube tutorial

3. When are you planning to work on documentation and how?
After deciding for a design and developing the detailed CAD model, we want to start with the documentation

# [OSHS] Colaborative notes second seminar

## Group 1
Students:
* Pongpanoch Chongpatiyutt
* Hans-Martin Schlesier
* Kim-Sarah Nowak

Practice partner: Sasha Pas (Playtronica)

### 1. What is your project goal?
Implement an open source hardware approach for the Playtronica Orbita. Develop a manual / documentation of how to implement the electronic components provided by Playtronica into a music interface designed by us. The criteria are to make it accessible for education and more affordable in a way that everyone can rebuild it easily with a limited number of pieces.
Components provided by Playtronica: sensors, raspberry pi, motor, motor belt, magnets, usb-media, usb-power

### 2. Which steps are you going to take to achieve it?
A. Research and understand the product as well as elaborate an Open Source Hardware approach.
B. Collect ideas of a different design approach.
C. Develop and design our open-source version. This will involve selecting the necessary hardware components and designing the user-friendly physical product.
D. Create a working prototype and test it to ensure that it functions as expected and delivers a user experience similar to the original product.
E. Documentation of all required steps to produce an Instrument as well as giving a manual for the production of each component and its assembly.

### 3. How are you going to engage with the practice partner?
We plan on feedback rounds to Iterate through designs and then coordinate the prototype making in a theoretical and practical hands-on manner.
Sascha will coordinate with us, as well as providing above mentioned components and if needed time in his workshop.

### 4. What deliverables will you provide by the end of the project?
We want to deliver a build prototype and the related manual ready for sharing to the Open Source Hardware community for a more economic version of the Orbita that can be rebuild.

## Group 2
Students:
* Shreeya Nemade
* Virendra Nicht
* Zhen Hui

Practice partner: Lars Zimmermann

### 1. What is your project goal?
The project goal is to design and develop innovative hardware solution for Mifactori that can be freely shared, modified and built upon by the community. We are focusing on creating a new product with the existing or new parts. Technical documentation will be created to guide the community.

### 2. Which steps are you going to take to achieve it?
The following steps we are going to take to achieve our project goals
1) Idea generation: This is the initial phase where ideas for new products are generated. It can come from various sources such as market research, feedback from people, brainstorming sessions, etc.
2) Idea Screening: Once ideas are generated, they need to be evaluated and screened to determine their feasibility, potential market demand, and alignment with our goals and resources (Open-source hardware).
3) Design and Development: In this phase, the chosen ideas are further refined and developed into product concepts. This stage involves creating detailed product specifications, engineering the product, and building prototypes for testing and refinement.
4) Testing and Validation: Prototypes or early versions of the product are tested to identify any flaws, usability issues, or potential improvements. Feedback from testing helps refine the product design and ensures it meets the desired standards and customer requirements.
5) Documentation: Documenting the all process like hardware specifications, BOM, any testing reports, manual, licensing and legal considerations, etc.

### 3. How are you going to engage with the practice partner?
We plan to visit the studio space in coming weeks, get to know about their existing products and scope of creativity to ideate a new product. Through the whole process Lars will be guiding us with his knowledge and experience and also the necessary parts. We will have internal discussions for the project and also have Lars' feedback to see if we are on the right path.

### 4. What deliverables will you provide by the end of the project?
We plan to come out with a new product with existing parts and thus document the whole process for the user community to see openly.

# [OSHS] Colaborative notes fifth seminar (14.06.2023)

What is your specific motivation to document hardware and for whom?

Motivation: To try and be sustainable by using already exciting household parts in as many ways as possible. Even if the parts are not available at home, the parts of the product should be available for everyone at a very afordable price. By encourage replicabilty and knowledge sharing among the communities.
For whom: For private households as well as commercial spaces who need to decorate their spaces with greener alternatives.

How do you plan to document your hardware in terms of:
Contents: 1) Index of product documenation
2) BOM
3) Architecture
4) Assembly instruction
5) Design files
Formats: Reports, pictures, CAD model
Dissemination channel: Hackaday.io/ wikifactory

When are you planning to work on documentation and how?
We plan to document as soon as a first prototype is ready, we intend to make changes in the document as we further proceed in our project. We intend to record the process while making it for the first time too.