Extreme Collaboration

Meta

There are many tasks that go into an integrated Design/development infrastructure, and because of the numerous dependencies, they are hard to execute because of these dependencies: one part depends on the knowledge of another. To assist, we define physical interface design, but what about interface design to other areas, such as different machines or product ecosystems? To address this, we can create part libraries that contain all the dependencies, and if these are to be modified, modifications follow Design Rules.

Part libraries would allow us to move between tractor construction set, heavy machining, materials handling, materials processing, fuel and power, construction, and other areas. In the minimum form, precision machining and metal work, up to rolling and hot metal work, can all be built upon basic Tractor Construction Set infrastructures.

The key is to define tasks and processes that are scalable to wide participation. OSE is working on leveraging hundreds to thousands of contributors in realtime design. Its Summer X and other swarm events aim to optimize for wide collaboration. This is because of the premise that any complex productization involves significant resources on the order of $1M a pop, or about 10 people working full time for a year 20,000 development hours. This can be facilitated with AI these days.