Rapid Prototyping Approach

OSE rapid prototyping refers to 1-day builds and rapid 1-2 day prototyping runs that follow weeks of preparation. This is a technique that we follow at OSE pending complete preparation of designs and fabrication procedures. We have demonstrated proof of concept on the 1 day build with the 1 Day Build of the CEB Press, and we have demonstrated the 1-2 day build of a machine with the Ironworker Prototype 3.

We have learned over the years that we can either spend the time building or designing for a rapid build. Because we are dealing with heavy machinery, it is easier to prepare everything on paper prior to a build, up to language agnostic instructionals. This level of preparation allows builds to happen once, and only once - instead of parts being assembled and reassembled repeatedly.

This is feasible because we are simplifying the build stock and build procedures to the simplest possible design which still allows for peak performance.

Then after a build - we can iterate rapidly to make improvement - because our working materials make up a reconfigurable Construction Set.

The key to the above is module-based design. While it is much more difficult to build an entire device, it is much more tractable to build a module (or component of that machine). Only in the absence of skill or under time pressure do we not go through the full design process on paper, when we attain a lower level of quality, while still achieving a proof-of-concept.

Because we are working on many proofs-of-concept that have never before been attempted, it is more important to have something done rather than having something done perfectly. That is - done is better than perfect. This approach is taken because the thing at hand may not work - so it is important to determine early on whether something works or not - in order to take mid-course correction. This way, innovation happens in the span of days, not months.

Wikispeed has attained a 100 mpg car proof-of-concept in 3 months, as opposed to the years of typical development cycles. See Wikispeed.

OSE has attained a 12 hour build of the Ironworker Machine Prototype 3, compared to the 6 month build of Prototype 2 - by radically shifting the design approach.

And this is only the beginning...

It is important to point out that the GVCS is being designed as a Set, not as individual machines. That means that a product ecology must be considered.

Numerous people have commented Why don't we build something right the first time instead of rushing? Our response is that the essence of rapid prototyping is to fail more to learn more - or otherwise spend months instead of days learning something new. Our response is further - yes, we would gladly do that if our timeline was 100 years - however - our criterion for success is attaining robust functionality of the entire set by the end of 2015. This calls for a velocity that most people cannot wrap their head around.