https://wiki.opensourceecology.org/index.php?action=history&feed=atom&title=Extreme_Manufacturing_Social_Contract 2026-04-07T21:38:39Z Revision history for this page on the wiki MediaWiki 1.39.13 https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278303&oldid=prev 2022-11-22T19:44:40Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:44, 22 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change in the current build.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change in the current build.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. This is not a typical build process where this would  </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td><td colspan="2" class="diff-side-added"></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278267&oldid=prev 2022-11-20T19:03:07Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:03, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change <ins style="font-weight: bold; text-decoration: none;">in the current build</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. This is not a typical build process where this would  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. This is not a typical build process where this would  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278265&oldid=prev 2022-11-20T18:35:01Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:35, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l13">Line 13:</td> <td colspan="2" class="diff-lineno">Line 13:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Understanding requirements and esp Tolerancing requirements is the number one skill affecting one&#039;s speed of build to achieve a predefined level of quality.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Understanding requirements and esp Tolerancing requirements is the number one skill affecting one&#039;s speed of build to achieve a predefined level of quality.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Our requirement is Integrated Performance - not point performance of modules, to break the [[Iron Triangle]] of good-fast-cheap. We add &#039;simple but no simpler&#039; to create the good-fast-cheap-simle quadrangle.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Our requirement is Integrated Performance - not point performance of modules, to break the [[Iron Triangle]] of good-fast-cheap. We add &#039;simple but no simpler&#039; to create the good-fast-cheap-simle quadrangle<ins style="font-weight: bold; text-decoration: none;">. We are squares, not</ins>.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278264&oldid=prev 2022-11-20T18:34:38Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:34, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l12">Line 12:</td> <td colspan="2" class="diff-lineno">Line 12:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#When site built - build closest to point of installation. Build stations can be mobile if these are horses.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#When site built - build closest to point of installation. Build stations can be mobile if these are horses.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Understanding requirements and esp Tolerancing requirements is the number one skill affecting one&#039;s speed of build to achieve a <del style="font-weight: bold; text-decoration: none;">certain </del>level of quality.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Understanding requirements and esp Tolerancing requirements is the number one skill affecting one&#039;s speed of build to achieve a <ins style="font-weight: bold; text-decoration: none;">predefined </ins>level of quality<ins style="font-weight: bold; text-decoration: none;">.</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">#Our requirement is Integrated Performance - not point performance of modules, to break the [[Iron Triangle]] of good-fast-cheap. We add &#039;simple but no simpler&#039; to create the good-fast-cheap-simle quadrangle</ins>.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278263&oldid=prev 2022-11-20T18:32:07Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:32, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l12">Line 12:</td> <td colspan="2" class="diff-lineno">Line 12:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#When site built - build closest to point of installation. Build stations can be mobile if these are horses.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#When site built - build closest to point of installation. Build stations can be mobile if these are horses.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Chinese wise man. If you go to bed with an itchy ass, you&#039;re gonna wake up with smelly fingers. There is cause and effect. Application example: if your modules are 9&#039; 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&#039;t need to plumb-level - modules are adjustable until joists are mounted.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#<ins style="font-weight: bold; text-decoration: none;">Understanding requirements and esp Tolerancing requirements is the number one skill affecting one&#039;s speed of build to achieve a certain level of quality.</ins></div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278262&oldid=prev 2022-11-20T18:29:46Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:29, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l2">Line 2:</td> <td colspan="2" class="diff-lineno">Line 2:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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&#039;t even begin to consider actually making that change.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. This is not a typical build process where this would  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. This is not a typical build process where this would  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>be <del style="font-weight: bold; text-decoration: none;"> </del>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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#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.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278261&oldid=prev 2022-11-20T18:28:55Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:28, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video. And, consider the next guideline:</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video. And, consider the next guideline: <ins style="font-weight: bold; text-decoration: none;">don&#039;t even begin to consider actually making that change.</ins></div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. 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, <del style="font-weight: bold; text-decoration: none;">and even </del>to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed <del style="font-weight: bold; text-decoration: none;">for this because </del>problem-solving <del style="font-weight: bold; text-decoration: none;">takes too much </del>time 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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build<ins style="font-weight: bold; text-decoration: none;">. This is not a typical build process where this would </ins></div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">be  required. Normal build processes do not figure things out ahead of time. Here we did and we already tested it</ins>. 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, <ins style="font-weight: bold; text-decoration: none;">including </ins>to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed <ins style="font-weight: bold; text-decoration: none;">to include </ins>problem-solving time <ins style="font-weight: bold; text-decoration: none;">outside of critical emergencies which leave no other choice </ins>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.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Digital design frees you from thinking so you can focus on execution.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have <ins style="font-weight: bold; text-decoration: none;">unpredictable </ins>downstream consequences in digital design <ins style="font-weight: bold; text-decoration: none;">which would introduce errors in subsequent steps</ins>.</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Digital design frees you from thinking so you can focus on execution<ins style="font-weight: bold; text-decoration: none;">, 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</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Digital design is rare, so you are probably not familiar with it. It&#039;s more rigorous than IKEA as here we are building a system of integrated components, not a single product.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Digital design is rare, so you are probably not familiar with it. It&#039;s more rigorous than IKEA as here we are building a system of integrated components, not a single product.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes. BM notes any proposed design change, to be evaluated for integration into the next build.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes. BM notes any proposed design change, to be evaluated for integration into the next build.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278260&oldid=prev 2022-11-20T18:23:08Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:23, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>#Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>#Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video. <ins style="font-weight: bold; text-decoration: none;">And, consider the next guideline:</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. 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, and even to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed for this because problem-solving takes too much time 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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. 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, and even to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed for this because problem-solving takes too much time 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.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278259&oldid=prev 2022-11-20T18:22:25Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:22, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">#Design change suggestions are welcome. The protocol is that QC person records the suggestions in writing or on video.</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. 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, and even to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed for this because problem-solving takes too much time 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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No design changes during build. 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, and even to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed for this because problem-solving takes too much time 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.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Extreme_Manufacturing_Social_Contract&diff=278258&oldid=prev 2022-11-20T18:21:07Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:21, 20 November 2022</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#No arguing with Build Manager. Build manager will not argue with you, only point out any departures from plans.</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">#No design changes during build. 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, and even to Build Manager. 3. Any change requires downstream problem-solving, and the Extreme Build is not designed for this because problem-solving takes too much time 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.</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Follow plans. If it is not on the plans, notify manager. This is because any change will have downstream consequences in digital design.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Digital design frees you from thinking so you can focus on execution.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>#Digital design frees you from thinking so you can focus on execution.</div></td></tr> </table>

Marcin