Merge Workflow - Revision history

Marcin: /* General */

2021-12-08T12:13:26Z

General

← Older revision		Revision as of 12:13, 8 December 2021
Line 6:		Line 6:

	This concept is general: it refers to any process where people can work independently with zero barriers to entry and without reconciliation of contributions until the very end, as in the 'excessive prototyping' concept of the [[Second Toyota Paradox]]. This allows for casting a wide net for contributions from many people, without the time-intensive reconciliation process (commits). In this way, relevant contributions can be collected - under the assumption that any work of genius is 1% inspiration, and 99% perspiration. To refine the contributions, various mechanisms can be implemented. These mechanisms must involve [[Subject Matter Experts]], [[Artificial Intelligence]], or another process which evaluates and refines the contributions into products.		This concept is general: it refers to any process where people can work independently with zero barriers to entry and without reconciliation of contributions until the very end, as in the 'excessive prototyping' concept of the [[Second Toyota Paradox]]. This allows for casting a wide net for contributions from many people, without the time-intensive reconciliation process (commits). In this way, relevant contributions can be collected - under the assumption that any work of genius is 1% inspiration, and 99% perspiration. To refine the contributions, various mechanisms can be implemented. These mechanisms must involve [[Subject Matter Experts]], [[Artificial Intelligence]], or another process which evaluates and refines the contributions into products.

			The [[Swarm Build]] technique pioneered by OSE for developing and building products involves modular design for large-scale, parallel builds - where the modules are 'assembled rapidly into place' at the end - allowing for rapid build timeframes of [[Extreme Manufacturing]]. This 'rapid assembly' process is one specific instance of 'merge workflow.'

	==FreeCAD Case==		==FreeCAD Case==

Marcin: /* Summary */

2021-12-08T12:09:48Z

Summary

← Older revision		Revision as of 12:09, 8 December 2021
Line 2:		Line 2:

	=Summary=		=Summary=
	Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench, nor Git as version control. Version control is done using the wiki, just as Wikipedia has scaled to become the largest information project in the world. OSE's [[Public Development]] may be compared to Wikipedia more than to Linux in terms of how it manages information. We use [[Set-Based Concurrent Engineering]] with design reconciliation / integration / quality control as late in the process as possible in order to maximize the number of prototypes that feed into any hardware build. We consider that [[Every Hardware Build is a Fork]], for which reason a Git-based workflow is not adequate.		==General==
			'''Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people.'''

			This concept is general: it refers to any process where people can work independently with zero barriers to entry and without reconciliation of contributions until the very end, as in the 'excessive prototyping' concept of the [[Second Toyota Paradox]]. This allows for casting a wide net for contributions from many people, without the time-intensive reconciliation process (commits). In this way, relevant contributions can be collected - under the assumption that any work of genius is 1% inspiration, and 99% perspiration. To refine the contributions, various mechanisms can be implemented. These mechanisms must involve [[Subject Matter Experts]], [[Artificial Intelligence]], or another process which evaluates and refines the contributions into products.

			==FreeCAD Case==
			The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench, nor Git as version control. Version control is done using the wiki, just as Wikipedia has scaled to become the largest information project in the world. OSE's [[Public Development]] may be compared to Wikipedia more than to Linux in terms of how it manages information. We use [[Set-Based Concurrent Engineering]] with design reconciliation / integration / quality control as late in the process as possible in order to maximize the number of prototypes that feed into any hardware build. We consider that [[Every Hardware Build is a Fork]], for which reason a Git-based workflow is not adequate.

	Part location is an important topic, but this workflow does not require positionally-correct files - parts can be moved into the correct position iterativelly.		Part location is an important topic, but this workflow does not require positionally-correct files - parts can be moved into the correct position iterativelly.

Marcin: /* Summary */

2021-07-15T15:50:48Z

Summary

← Older revision		Revision as of 15:50, 15 July 2021
Line 2:		Line 2:

	=Summary=		=Summary=
	Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench.		Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench, nor Git as version control. Version control is done using the wiki, just as Wikipedia has scaled to become the largest information project in the world. OSE's [[Public Development]] may be compared to Wikipedia more than to Linux in terms of how it manages information. We use [[Set-Based Concurrent Engineering]] with design reconciliation / integration / quality control as late in the process as possible in order to maximize the number of prototypes that feed into any hardware build. We consider that [[Every Hardware Build is a Fork]], for which reason a Git-based workflow is not adequate.

	Part location is an important topic, but this workflow does not require positionally-correct files - parts can be moved into the correct position iterativelly.		Part location is an important topic, but this workflow does not require positionally-correct files - parts can be moved into the correct position iterativelly.

Marcin: /* Philosophical Point */

2021-06-29T22:02:47Z

Philosophical Point

← Older revision		Revision as of 22:02, 29 June 2021
Line 9:		Line 9:

	==Philosophical Point==		==Philosophical Point==
	MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life. The practical advantage at OSE is not requiring the CAD artist to use Assembly workflows - moving and rotating things is simpler conceptually - and novices can learn move-rotate immediately. Move-rotate corresponds to real life - so it's a good reality check for buildability. Maybe there are so many unreachable bolts in engines because the designers used Assembly workflows to create the designs?		MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability because it forces the designer to move things, and while moving things, part interference can be observed. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design (in most cases). It is important to understand what level of detail is important in real life. The practical advantage at OSE is not requiring the CAD artist to use Assembly workflows - moving and rotating things is simpler conceptually - and novices can learn move-rotate immediately. Move-rotate corresponds to real life - so it's a good reality check for buildability. Maybe there are so many unreachable bolts in engines because the designers used Assembly workflows to create the designs?

	=Intro=		=Intro=

Marcin: /* Philosophical Point */

2021-06-25T19:06:49Z

Philosophical Point

← Older revision		Revision as of 19:06, 25 June 2021
Line 9:		Line 9:

	==Philosophical Point==		==Philosophical Point==
	MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life. The practical advantage at OSE is not requiring the CAD artist to use Assembly workflows - moving and rotating things is simpler conceptually - and can ~~be learned~~ immediately.		MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life. The practical advantage at OSE is not requiring the CAD artist to use Assembly workflows - moving and rotating things is simpler conceptually - and novices can learn move-rotate immediately. Move-rotate corresponds to real life - so it's a good reality check for buildability. Maybe there are so many unreachable bolts in engines because the designers used Assembly workflows to create the designs?

	=Intro=		=Intro=

Marcin: /* Philosophical Point */

2021-06-25T19:05:38Z

Philosophical Point

← Older revision		Revision as of 19:05, 25 June 2021
Line 9:		Line 9:

	==Philosophical Point==		==Philosophical Point==
	MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life.		MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life. The practical advantage at OSE is not requiring the CAD artist to use Assembly workflows - moving and rotating things is simpler conceptually - and can be learned immediately.

	=Intro=		=Intro=

Marcin: /* Philosophical Point */

2021-06-25T19:03:59Z

Philosophical Point

← Older revision		Revision as of 19:03, 25 June 2021
Line 9:		Line 9:

	==Philosophical Point==		==Philosophical Point==
	MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect.		MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect. Thus, no need to create a perfect design. It is important to understand what level of detail is important in real life.

	=Intro=		=Intro=

Marcin: /* Summary */

2021-06-25T19:03:06Z

Summary

← Older revision		Revision as of 19:03, 25 June 2021
Line 4:		Line 4:
	Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench.		Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench.

	To address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.		Part location is an important topic, but this workflow does not require positionally-correct files - parts can be moved into the correct position iterativelly.

			For positional-correctness of inserted parts - to address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.

			==Philosophical Point==
			MJ sez: Constraints are misleading. It makes teh CAD artist shun further responsibility of buildability. Because no 2 parts are ever perfectly aligned in real life (if you dig deep enough). So why design perfect alignment in CAD? Approximating alignment by manual placement provides a reality check regarding actual build conditions. It makes the CAD artist consider buildability. In our view, constraintless design has merits of accountability. Constraints mislead the author into a feeling of absolute power and control over their design - "it's a perfect design". Wake up Neo, swallow a whole packet of red tablets. The reality is never as perfect.

	=Intro=		=Intro=

Marcin: /* Summary */

2021-06-15T17:03:53Z

Summary

← Older revision		Revision as of 17:03, 15 June 2021
Line 2:		Line 2:

	=Summary=		=Summary=
	Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents in positionally-correct locations. To address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.		Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents, and files can also be joined in positionally-correct locations. This does not require the more advanced functionality of using constrains in the Assembly workbench.

			To address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.

	=Intro=		=Intro=

Marcin: /* Summary */

2020-06-17T16:39:14Z

Summary

← Older revision		Revision as of 16:39, 17 June 2020
Line 3:		Line 3:
	=Summary=		=Summary=
	Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents in positionally-correct locations. To address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.		Merge Workflow is a technique where, without locking down design files, collaboration can occur on a single CAD design with an unlimited number of people. The workflow relies on merging parts into working documents in positionally-correct locations. To address the issue or correct part location, part placeholders are started in an assembly document - in a positionally correct location. These parts can subsequently be edited in separate documents. Source files are uploaded on an ongoing basis. For onboarding of additional designers, uplaods incude [[Visual Version History]], and live-editable Working Docs support the design process. Because nothing is locked down and ongoing communication between developers occurs via video in realtime or via work docs asynchronously, this process can leverage the input of large teams, using common off-the-shelf software, FreeCAD.


	=Intro=		=Intro=