OSE Specifications for Product Design - Revision history

Marcin: /* Process Design */

2013-08-09T04:44:15Z

Process Design

← Older revision		Revision as of 04:44, 9 August 2013
Line 18:		Line 18:
	The development process itself follows:		The development process itself follows:

	#'''Lifetime Design''' - allows for constant and permanent development and evolution of ~~products~~		#'''Lifetime Design''' - allows for constant and permanent development and evolution of process
	#'''Scalability of Development''' - allows many modules to be developed at one time under the guidance of a development team		#'''Scalability of Development''' - allows many modules to be developed at one time under the guidance of a development team
	#'''Scalability of Projects''' - Ability to create new development projects readily		#'''Scalability of Projects''' - Ability to create new development projects readily

Marcin: /* Process Design */

2013-08-09T02:41:27Z

Process Design

← Older revision		Revision as of 02:41, 9 August 2013
Line 30:		Line 30:
	#'''Agility 2'''. Ability to course-correct pending new developments (agile development)		#'''Agility 2'''. Ability to course-correct pending new developments (agile development)
	#'''Process Interoperability''' Equivalent of Interface Design for hardware ([[Contract-First Manufacturing]]) - but for processes. This means that the various aspects of the development process are integrated with others (development per se works with recruiting process, works with documentation process, works with resource acquisition, etc)		#'''Process Interoperability''' Equivalent of Interface Design for hardware ([[Contract-First Manufacturing]]) - but for processes. This means that the various aspects of the development process are integrated with others (development per se works with recruiting process, works with documentation process, works with resource acquisition, etc)

			In general, when designing machines - one must ask - is a process critical to successful deployment of a technology - consistent with [product ecology - modularity - simplicity] - focusing on [radical collaboration - transparency - review - strategic collaboration] - while documenting [BOM - CAD file - Overview Fab Drawings - Fab Drawings - Fabrication Diagram + Master Index + Fab Procedure Pictures + Fab Video + Quality Control Checklist + Hydraulic Diagrams + Electrical Diagrams + Code] towards perfecting the GVCS within 2 years - while creating a methodology for this development?

	=Protocol=		=Protocol=

Marcin: /* Links */

2013-08-09T00:51:18Z

Links

← Older revision		Revision as of 00:51, 9 August 2013
Line 35:		Line 35:
	=Links=		=Links=
	*[[OSE Specifications]]		*[[OSE Specifications]]
	*[[Analysis of Industry Standards ~~Template~~]]		*[[Analysis of Industry Standards Protocol]]

Marcin: /* Links */

2013-08-09T00:51:03Z

Links

← Older revision		Revision as of 00:51, 9 August 2013
Line 35:		Line 35:
	=Links=		=Links=
	*[[OSE Specifications]]		*[[OSE Specifications]]
			*[[Analysis of Industry Standards Template]]

Marcin: /* Process Design */

2013-08-08T18:33:32Z

Process Design

← Older revision		Revision as of 18:33, 8 August 2013
Line 11:		Line 11:
	#'''Efficiency'''. OSE efficiency is measured on global performance (based on regenerative economic development as the goal) as opposed to point performance		#'''Efficiency'''. OSE efficiency is measured on global performance (based on regenerative economic development as the goal) as opposed to point performance
	#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.		#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.


			Each of the above will be rated from 1-10 and the result summed to get an overall % score.

	=Process Design=		=Process Design=
Line 16:		Line 19:

	#'''Lifetime Design''' - allows for constant and permanent development and evolution of products		#'''Lifetime Design''' - allows for constant and permanent development and evolution of products
	#'''Scalability of ~~project~~''' - allows many modules to be developed at one time under the guidance of a development team		#'''Scalability of Development''' - allows many modules to be developed at one time under the guidance of a development team
			#'''Scalability of Projects''' - Ability to create new development projects readily
	#'''Parallel Development''' - allows different steps in a given product or module to be taken on at the same time (in parallel)		#'''Parallel Development''' - allows different steps in a given product or module to be taken on at the same time (in parallel)
	#'''[[Test-Driven Design]]'''		#'''[[Test-Driven Design]]'''
Line 23:		Line 27:
	#'''Ability to update development readily		#'''Ability to update development readily
	#'''Trackability''' - Organization of project enables the stakeholder team track development to make this development efficient.		#'''Trackability''' - Organization of project enables the stakeholder team track development to make this development efficient.
	#~~Ability to create new development projects readily~~		#'''Agility 1'''. Ability to absorb new developers and expand as resources allow (agility)
	#Ability to absorb new developers and expand as resources allow (agility)		#'''Agility 2'''. Ability to course-correct pending new developments (agile development)
	#Ability to course-correct pending new developments (agile development)		#'''Process Interoperability''' Equivalent of Interface Design for hardware ([[Contract-First Manufacturing]]) - but for processes. This means that the various aspects of the development process are integrated with others (development per se works with recruiting process, works with documentation process, works with resource acquisition, etc)
	#Interface Design ([[Contract-First Manufacturing]]) - ~~defines how modules fit together~~

	~~Each~~ of the ~~above will be rated from 1-10 and the result summed to get an overall % score.~~

	=Protocol=		=Protocol=

Marcin: /* Process Design */

2013-08-08T18:29:21Z

Process Design

← Older revision		Revision as of 18:29, 8 August 2013
Line 22:		Line 22:
	#'''Module-Based Design 2''' - Ability to handle Modules and Machines as units of development		#'''Module-Based Design 2''' - Ability to handle Modules and Machines as units of development
	#'''Ability to update development readily		#'''Ability to update development readily
	#~~Ability~~ to ~~track~~ development		#'''Trackability''' - Organization of project enables the stakeholder team track development to make this development efficient.
	#Ability to create new development projects readily		#Ability to create new development projects readily
	#Ability to absorb new developers and expand as resources allow (agility)		#Ability to absorb new developers and expand as resources allow (agility)
Line 28:		Line 28:
	#Interface Design ([[Contract-First Manufacturing]]) - defines how modules fit together		#Interface Design ([[Contract-First Manufacturing]]) - defines how modules fit together

	Each of the above will be rated from 1-10 and the result summed to get an overall % score ~~of the maximum 140 points~~.		Each of the above will be rated from 1-10 and the result summed to get an overall % score.

	=Protocol=		=Protocol=

Marcin: /* Product Design */

2013-08-08T18:27:18Z

Product Design

← Older revision		Revision as of 18:27, 8 August 2013
Line 9:		Line 9:
	#'''Low cost.''' Off-shelf parts. Minimum machining.		#'''Low cost.''' Off-shelf parts. Minimum machining.
	#'''High Performance'''. Meeting or exceeding industry standards - as defined in [[GVCS Comparison to Industry Standards]]. Overbuild with Space Frames.		#'''High Performance'''. Meeting or exceeding industry standards - as defined in [[GVCS Comparison to Industry Standards]]. Overbuild with Space Frames.
	#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.		#'''Efficiency'''. OSE efficiency is measured on global performance (based on regenerative economic development as the goal) as opposed to point performance
			#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.

	=Process Design=		=Process Design=

Marcin: /* Process Design */

2013-08-08T18:25:56Z

Process Design

← Older revision		Revision as of 18:25, 8 August 2013
Line 14:		Line 14:
	The development process itself follows:		The development process itself follows:

	#Scalability of project - to many modules ~~being~~ developed at one time		#'''Lifetime Design''' - allows for constant and permanent development and evolution of products
	#Parallel Development - different steps in a given module ~~may~~ be taken on at the same time		#'''Scalability of project''' - allows many modules to be developed at one time under the guidance of a development team
	#[[Test-Driven Design]]		#'''Parallel Development''' - allows different steps in a given product or module to be taken on at the same time (in parallel)
	#Module-Based Design - for scalability and parallel development		#'''[[Test-Driven Design]]'''
	#Ability to handle Modules and Machines as units of development		#'''Module-Based Design''' - Breakdown into bitesize chunks is possible. This can be done by starting new development pages for each submodule. Promotes scalability and parallel development
	#Ability to update development readily		#'''Module-Based Design 2''' - Ability to handle Modules and Machines as units of development
			#'''Ability to update development readily
	#Ability to track development		#Ability to track development
	#Ability to create new development projects readily		#Ability to create new development projects readily

Marcin: /* Introduction */

2013-08-08T18:22:26Z

Introduction

← Older revision		Revision as of 18:22, 8 August 2013
Line 1:		Line 1:
	=~~Introduction~~=		=Product Design=

	To assess the technological design features of [[OSE Specifications]], these are the most important:		To assess the technological design features of [[OSE Specifications]], these are the most important:
	#'''Designed as a Product Ecology''' - at the component, module, and machine level. This means any single machine is being design with consideration of fitting in the overall set, not as a single machine. The intent here is that we are testing the feasibility of the entire package being managed (capable of being built from scrap steel in 50 days with 4 skilled people and 12 apprentices and repaired/maintained at no more than 300 hours per year). This is a serious quantitative milestone that will be developed as the set grows.		#'''Designed as a Product Ecology''' - at the component, module, and machine level. This means any single machine is being design with consideration of fitting in the overall set, not as a single machine. The intent here is that we are testing the feasibility of the entire package being managed (capable of being built from scrap steel in 50 days with 4 skilled people and 12 apprentices and repaired/maintained at no more than 300 hours per year). This is a serious quantitative milestone that will be developed as the set grows.
Line 12:		Line 11:
	#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.		#'''Product Ecology''' - Machine fit as part of a greater product ecology - on the component level, module level, and machine level.

			=Process Design=
	The development process itself follows:		The development process itself follows:

Marcin: /* Introduction */

2013-08-08T18:20:36Z

Introduction

← Older revision		Revision as of 18:20, 8 August 2013
Line 15:		Line 15:

	#Scalability of project - to many modules being developed at one time		#Scalability of project - to many modules being developed at one time
	#Parallel Development		#Parallel Development - different steps in a given module may be taken on at the same time
	#[[Test-Driven Design]]		#[[Test-Driven Design]]
	#Module-Based Design - for scalability and parallel development		#Module-Based Design - for scalability and parallel development
Line 22:		Line 22:
	#Ability to track development		#Ability to track development
	#Ability to create new development projects readily		#Ability to create new development projects readily
			#Ability to absorb new developers and expand as resources allow (agility)
			#Ability to course-correct pending new developments (agile development)
	#Interface Design ([[Contract-First Manufacturing]]) - defines how modules fit together		#Interface Design ([[Contract-First Manufacturing]]) - defines how modules fit together