Extreme Design White Paper

Abstract: here we explore the requirements and deployment of a mass collaborative development process within an open source framework. Motivation and incentives are considered, and rapid design techniques are demonstrated for a replicable design process involving 150+ interdisciplinary designers who produce a working design in one day, and prototype the same on a second day. We explore the role of:

1. open source toolchains for CAD, with the possibility of proprietary toolchains with open format export
2. Open source toolchains for electrical design, CAE, and other analysis
3. Open source
4. Part Libraries and openly accessible part repositories
5. Collaboration role architecture
6. Collaborative literacy on working openly
7. Open Source Product Development knowhow
8. Role of incentive challenges
9. Role of sponsorship and Extreme Build Coopetition
10. Role of Open Design Clubs
11. Administrative requirements
12. Role of productization assistance
13. Mixing Game Engines and OpenModelica into the collaborative process
14. Role of Modularity
15. Role of a Construction Set approach
16. Methods of creating financial feedback loops for livelihoods
17. Creation of supporting apps for design, marketing, sourcing, and deployment
18. Creation of open source supply chains
19. Creation of open source production engineering
20. Creation of distributed quality control methods
21. The role of distributive enterprise
22. Book Sprints for documentation
23. Role of modular breakdown and system engineering breakdown diagram
24. The background first principles, basic physics and engineering of how it works
25. Why it works
26. Role of involving school and university students in a massive collaborative process
27. Study of materials and sourcing for lifecycle analysis
28. The role of open source, Rapid prototyping tools including 3D printers, laser cutters, and cnc mills
29. Low cost prototyping toolchains with open source hardware
30. Open source laboratory and measurement device
31. Open source documentation, video, and publishing toolchains
32. Open source revenue models for public engineering development
33. Investment mechanisms and revenue streams from public enterprise as such
34. Role of open source product licenses consistent with Distributive Enerprise
35. Open source academic communities of interest

We conclude that developers can be incentivized to do public open source product development

References

• Joshua Pearce
• Dan Gelbart
• Extreme Learning Process
• [Extreme Manufacturing]]