Modular Breakdown - Revision history

Marcin: /* About */

2022-06-01T14:58:48Z

About

← Older revision		Revision as of 14:58, 1 June 2022
Line 14:		Line 14:
	To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented.		To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented.

	'''While we discuss point product development here - modular breakdown is a more general term. It refers to the breakdown of a problem into parts that are as small as possible, so that the largest possible team can engage in parallel - to produce rapid development, or to achieve things never before possible due to the effort or coordination required. Now coordination is an issue that must be resolved - and its resulution starts with a shared culture of understanding of the nature of modular breakdown and its capacity to solve large problems.'''		'''While we discuss point product development here - modular breakdown is a more general term. It refers to the breakdown of a problem into parts that are as small as possible, so that the largest possible team can engage in parallel - to produce rapid development, or to achieve things never before possible due to the effort or coordination required. Now coordination is an issue that must be resolved - and its resulution starts with a shared culture of understanding of the nature of modular breakdown and its capacity to solve large problems.''' The ultimate challenge is emergent phenomena which cannot be predicted at the stage of organizing a swarm, as in [[General Principles of Swarm Development]]. The ultimate solution is the ability of individuals to problemsolve - based on a shared understanding of collaborative development.

	=Modular Breakdown as Technical Design=		=Modular Breakdown as Technical Design=

	Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Upon sufficient refinement, there is sufficient information to manifest the technical design in the form of [[3D CAD]]. The [[Modular Breakdown]] step is where the concept can be refined further by examining the constituent modules. The Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility. All of these steps can be done at various levels of product-service system organization: the system, machine, module, and submodule (part) levels.		Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Upon sufficient refinement, there is sufficient information to manifest the technical design in the form of [[3D CAD]]. The [[Modular Breakdown]] step is where the concept can be refined further by examining the constituent modules. The Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility. All of these steps can be done at various levels of product-service system organization: the system, machine, module, and submodule (part) levels.

Marcin at 14:57, 1 June 2022

2022-06-01T14:57:13Z

← Older revision		Revision as of 14:57, 1 June 2022
Line 8:		Line 8:

	=About=		=About=
	OSE follows [[Module Based Design]]		OSE follows [[Module Based Design]].

	This allows multiple parts of an artifact to be developed in parallel, and it allows these parts to be produced in parallel via a 'barnraising'-style social production model.		This allows multiple parts of an artifact to be developed in parallel, and it allows these parts to be produced in parallel via a 'barnraising'-style social production model.

	To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented.		To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented.

			'''While we discuss point product development here - modular breakdown is a more general term. It refers to the breakdown of a problem into parts that are as small as possible, so that the largest possible team can engage in parallel - to produce rapid development, or to achieve things never before possible due to the effort or coordination required. Now coordination is an issue that must be resolved - and its resulution starts with a shared culture of understanding of the nature of modular breakdown and its capacity to solve large problems.'''

	=Modular Breakdown as Technical Design=		=Modular Breakdown as Technical Design=

	Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Upon sufficient refinement, there is sufficient information to manifest the technical design in the form of [[3D CAD]]. The [[Modular Breakdown]] step is where the concept can be refined further by examining the constituent modules. The Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility. All of these steps can be done at various levels of product-service system organization: the system, machine, module, and submodule (part) levels.		Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Upon sufficient refinement, there is sufficient information to manifest the technical design in the form of [[3D CAD]]. The [[Modular Breakdown]] step is where the concept can be refined further by examining the constituent modules. The Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility. All of these steps can be done at various levels of product-service system organization: the system, machine, module, and submodule (part) levels.

Marcin: /* Modular Breakdown as Technical Design */

2020-09-16T20:40:39Z

Modular Breakdown as Technical Design

← Older revision		Revision as of 20:40, 16 September 2020
Line 16:		Line 16:
	=Modular Breakdown as Technical Design=		=Modular Breakdown as Technical Design=

	Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. ~~Then~~ there is sufficient information to manifest the technical design in the form of [[3D CAD]]. ~~Thus,~~ the Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility.		Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Upon sufficient refinement, there is sufficient information to manifest the technical design in the form of [[3D CAD]]. The [[Modular Breakdown]] step is where the concept can be refined further by examining the constituent modules. The Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility. All of these steps can be done at various levels of product-service system organization: the system, machine, module, and submodule (part) levels.

Marcin: /* Modular Breakdown as Technical Design */

2020-09-16T20:30:31Z

Modular Breakdown as Technical Design

← Older revision		Revision as of 20:30, 16 September 2020
Line 16:		Line 16:
	=Modular Breakdown as Technical Design=		=Modular Breakdown as Technical Design=

	Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Then there is sufficient information to manifest the technical design in the form of [[3D CAD]]. Thus, the Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and ~~magnetic~~.		Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Then there is sufficient information to manifest the technical design in the form of [[3D CAD]]. Thus, the Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and electromagnetic. Partial calculations can be made at the phase of conceptual design - with ''back of the envelope'' calculations just to get an idea of basic feasibility.

Marcin: /* Modular Breakdown as Technical Design */

2020-09-16T20:29:43Z

Modular Breakdown as Technical Design

← Older revision		Revision as of 20:29, 16 September 2020
Line 16:		Line 16:
	=Modular Breakdown as Technical Design=		=Modular Breakdown as Technical Design=

	Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Then there is sufficient information to manifest the technical design in the form of [[3D CAD]].		Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Then there is sufficient information to manifest the technical design in the form of [[3D CAD]]. Thus, the Modular Breakdown is the best place to capture the transition from concept to the actual design. Once the actual design (3D CAD) is produced - we can do full Calculations including structural, thermal, fluid, and magnetic.

Marcin: /* About */

2020-09-16T20:28:24Z

About

← Older revision		Revision as of 20:28, 16 September 2020
Line 12:		Line 12:
	This allows multiple parts of an artifact to be developed in parallel, and it allows these parts to be produced in parallel via a 'barnraising'-style social production model.		This allows multiple parts of an artifact to be developed in parallel, and it allows these parts to be produced in parallel via a 'barnraising'-style social production model.

	To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented ~~(next step~~ in ~~Development Process)~~.		To achieve Module Based Design - a machine/artifact first needs to be broken down into modules. These modules must be designed such that they fit together with other modules. For this to happen, a clear interface design must be presented.

			=Modular Breakdown as Technical Design=

			Once we have defined [[Conceptual Design]], we can proceed to further refinement of concept towards a technical design. Then there is sufficient information to manifest the technical design in the form of [[3D CAD]].

Marcin at 16:09, 7 May 2020

2020-05-07T16:09:14Z

← Older revision		Revision as of 16:09, 7 May 2020
Line 3:		Line 3:
	#Break the machine down into components by studying History, Prior Art, and Industry Standards.		#Break the machine down into components by studying History, Prior Art, and Industry Standards.
	#Write down salient notes on the modules as necessary to explain importance of module from standpoint of [[OSE Specifications]]		#Write down salient notes on the modules as necessary to explain importance of module from standpoint of [[OSE Specifications]]
	#Draw these components and make notes in the Drawing		#Draw these components and make notes in the Drawing. '''Better yet, use [[Icons]] for the 500 universal modules to represent the breakdown, thus adding to the level of integration of the project.'''
	#Publish to wiki. See [[Embedding Google Docs]]. This allows document to update automatically in the wiki whenever changes are made.		#Publish to wiki. See [[Embedding Google Docs]]. This allows document to update automatically in the wiki whenever changes are made.
	#Link to your Module Breakdown in the Development Board for the particular machine/artifact.}}		#Link to your Module Breakdown in the Development Board for the particular machine/artifact.}}

Marcin at 20:18, 27 October 2019

2019-10-27T20:18:33Z

← Older revision		Revision as of 20:18, 27 October 2019
Line 2:		Line 2:
	{{Hint\|#Use [[Presentation Template]] for generating your diagram.		{{Hint\|#Use [[Presentation Template]] for generating your diagram.
	#Break the machine down into components by studying History, Prior Art, and Industry Standards.		#Break the machine down into components by studying History, Prior Art, and Industry Standards.
	#Write down salient notes on the modules as necessary to explain importance of module from standpoint of OSE Specifications		#Write down salient notes on the modules as necessary to explain importance of module from standpoint of [[OSE Specifications]]
	#Draw these components and make notes in the Drawing		#Draw these components and make notes in the Drawing
	#Publish to wiki. See [[Embedding Google Docs]]. This allows document to update automatically in the wiki whenever changes are made.		#Publish to wiki. See [[Embedding Google Docs]]. This allows document to update automatically in the wiki whenever changes are made.

Marcin: Marcin moved page Modules Breakdown to Modular Breakdown

2019-09-27T22:32:13Z

Marcin moved page Modules Breakdown to Modular Breakdown

← Older revision	Revision as of 22:32, 27 September 2019
(No difference)

Marcin: /* Protocol */

2019-09-26T20:24:09Z

Protocol

← Older revision		Revision as of 20:24, 26 September 2019
Line 1:		Line 1:
	=Protocol=		=Protocol=
	{{~~HInt~~\|#Use [[Presentation Template]] for generating your diagram.		{{Hint\|#Use [[Presentation Template]] for generating your diagram.
	#Break the machine down into components by studying History, Prior Art, and Industry Standards.		#Break the machine down into components by studying History, Prior Art, and Industry Standards.
	#Write down salient notes on the modules as necessary to explain importance of module from standpoint of OSE Specifications		#Write down salient notes on the modules as necessary to explain importance of module from standpoint of OSE Specifications