Extreme Manufacturing Social Contract

From Open Source Ecology
Jump to: navigation, search
  1. No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.
  2. Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video. And, consider the next guideline: don't even begin to consider actually making that change in the current build.
  3. No design changes during build. This is not a typical build process where this would be required. Normal build processes do not figure things out ahead of time. Here we did and we already tested it. All design is as-is for the build. This is for 4 reasons. 1. Data collection on this specific execution path. 2. Changes propagate downstream in an unpredictable way for builders, including to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed to include problem-solving time outside of critical emergencies which leave no other choice 4. It is very expensive to problemsolve during a build because many people can be slowed down. Problem-solving time is effectively downtime in an extreme build.
  4. Follow plans. If it is not on the plans, notify manager. This is because any change will have unpredictable downstream consequences in digital design which would introduce errors in subsequent steps.
  5. Digital design frees you from thinking so you can focus on execution, quality, and downstream improvement. If it is not digital (ie, carefully documented), you have little basis for downstream improvement as improvements would not be recorded and would likely rely only on your memory. This does not scale to a large collaborative process.
  6. Digital design is rare, so you are probably not familiar with it. It's more rigorous than IKEA as here we are building a system of integrated components, not a single product.
  7. No design changes. BM notes any proposed design change, to be evaluated for integration into the next build.
  8. With that said - understand Design For Tolerancing, and understand which tolerances matter - at which point in time. Such as - loosely fixed wall vs wall after final nail-off.
  9. Pre-QC modules are screwed in , only sufficiently to prevent shifting, but not structurally. Final nail-off follows QC, is structural, and marks the point of a qc'd module ready for installation.
  10. Modules need to be built, and if transported, loaded onto trailer in a specific order. Otherwise you may have the first module you need that requires unloading of entire trailer prior to install.
  11. When site built - build closest to point of installation. Build stations can be mobile if these are horses.
  12. Chinese wise man. If you go to bed with an itchy ass, you're gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9' and sill plate is level, your walls will be level and correct as long as you put one module next to another. As long as each module was quality controlled for square. Implications: couple minutes per module. Don't need to plumb-level - modules are adjustable until joists are mounted.
  13. Understanding requirements and esp Tolerancing requirements is the number one skill affecting one's speed of build to achieve a predefined level of quality.
  14. Our requirement is Integrated Performance - not point performance of modules, to break the Iron Triangle of good-fast-cheap. We add 'simple but no simpler' to create the good-fast-cheap-simle quadrangle. We are squares, not.