OSE Systems and Processes - Revision history

Chris F at 16:27, 11 September 2011

2011-09-11T16:27:22Z

← Older revision		Revision as of 16:27, 11 September 2011
Line 1:		Line 1:
			{{NoTOC}}

			==Overview==
	A system is the method by which you achieve the purpose. This document shows how the various systems at OSE fit together and lists the many processes used to get the daily work done. This is based on the existing organization and should not be considered final or an impediment to improvement. In fact, all processes should be subject to continual improvement--just be sure to update the documentation to match.		A system is the method by which you achieve the purpose. This document shows how the various systems at OSE fit together and lists the many processes used to get the daily work done. This is based on the existing organization and should not be considered final or an impediment to improvement. In fact, all processes should be subject to continual improvement--just be sure to update the documentation to match.

Marcin: /* Roles/Jobs */

2011-09-06T02:36:06Z

Roles/Jobs

← Older revision		Revision as of 02:36, 6 September 2011
Line 263:		Line 263:

	[[Category:Open Source Product Development Pipeline]]		[[Category:Open Source Product Development Pipeline]]
			[[Category:GVCS Rollout Plan]]

Marcin at 02:35, 6 September 2011

2011-09-06T02:35:15Z

← Older revision		Revision as of 02:35, 6 September 2011
Line 261:		Line 261:

	See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]		See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]

			[[Category:Open Source Product Development Pipeline]]

Ryan Lutz: /* Support systems */

2011-08-07T04:51:42Z

Support systems

← Older revision		Revision as of 04:51, 7 August 2011
Line 64:		Line 64:

	===Support systems===		===Support systems===
	These systems support and serve the Gemba. Before any changes are made ask: how will this change affect the ~~Gimba.~~		These systems support and serve the Gemba. Before any changes are made ask: how will this change affect the Gemba?
	====Management====		====Management====
	*Organization Management		*Organization Management

Marshall Smith: /* Roles/Jobs */

2011-08-03T21:22:14Z

Roles/Jobs

← Older revision		Revision as of 21:22, 3 August 2011
Line 259:		Line 259:
	==Roles/Jobs==		==Roles/Jobs==
	See [[Development Team]]		See [[Development Team]]

	See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]		See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]

Marshall Smith: /* Roles/Jobs */

2011-08-03T21:21:59Z

Roles/Jobs

← Older revision		Revision as of 21:21, 3 August 2011
Line 258:		Line 258:

	==Roles/Jobs==		==Roles/Jobs==
			See [[Development Team]]
	See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]		See [http://blog.opensourceecology.org/2011/07/dream-team-sixteen/ Dream Team 16]

Marshall Smith: /* Functions and Capabilities Required */

2011-08-03T03:00:21Z

Functions and Capabilities Required

← Older revision		Revision as of 03:00, 3 August 2011
Line 238:		Line 238:
	**Chemistry		**Chemistry
	**Agriculture		**Agriculture
			**[[Subject matter experts\|more]]
	*Research		*Research
	*Networking		*Networking

Marshall Smith: /* Find experts (Personnel system) */

2011-08-03T02:59:46Z

Find experts (Personnel system)

← Older revision		Revision as of 02:59, 3 August 2011
Line 151:		Line 151:
	See [[Bid Process]]		See [[Bid Process]]
	===Find experts (Personnel system)===		===Find experts (Personnel system)===
			(see [[Subject matter experts]] for list of needed experts)
	*requires contact db with network contacts listed with expertise		*requires contact db with network contacts listed with expertise
	*if not an existing contact then call Viviek and others		*if not an existing contact then call Viviek and others

Marshall Smith: /* Inputs */

2011-08-03T02:58:53Z

Inputs

← Older revision		Revision as of 02:58, 3 August 2011
Line 15:		Line 15:
	*Manpower:		*Manpower:
	**Project manager		**Project manager
	**Subject Experts		**Subject Experts (see [[Subject matter experts]])
	**Designer		**Designer
	**CAD Draftsman		**CAD Draftsman
Line 23:		Line 23:
	*Building material		*Building material
	*Tools		*Tools

	====Design====		====Design====
	*Research user needs, open source prior art, and industry best practices		*Research user needs, open source prior art, and industry best practices

Marshall Smith: /* Systems */

2011-07-29T16:08:24Z

Systems

← Older revision		Revision as of 16:08, 29 July 2011
Line 10:		Line 10:
	===Gemba (core) System===		===Gemba (core) System===
	This is the system for developing the [[GVCS 50]]. Each tool can be developed using this process with the output of the system being the complete set of 50 tools ready for use by the [[OSE Village Experiment]]. Other systems, while important, exist to support the Gemba.		This is the system for developing the [[GVCS 50]]. Each tool can be developed using this process with the output of the system being the complete set of 50 tools ready for use by the [[OSE Village Experiment]]. Other systems, while important, exist to support the Gemba.

			(Based on [[GVCS Development Template]])
	====Inputs====		====Inputs====
	*Manpower: ~~Skilled designers and builders~~		*Manpower:
			**Project manager
			**Subject Experts
			**Designer
			**CAD Draftsman
			**Use case researcher
			**Documenter
			**Fabricators
	*Building material		*Building material
	*Tools		*Tools
	====Design====		====Design====
	~~This process is as follows:~~		*Research user needs, open source prior art, and industry best practices
	*Specifications and requirements defined (see [[OSE Specifications]] for general specs)		*Specifications and requirements defined (see [[OSE Specifications]] for general specs)
	*Design		*Conceptual Design in the form of [[Systems Engineering Breakdown Diagrams]]
			*Estimate Costs
	*Engineer for assembly		*Engineer for assembly
	*Produce working drawings and CNC files (CAD)		*Produce working drawings and CNC files (CAD)
			*Produce design rationale document
			*Failure mode analysis
			*Post for peer review and refactor as necessary
	*Produce BOM		*Produce BOM
	*Calculate ~~costs~~		*Calculate Costs and performance and verify they meet targets
	====Prototype====		====Prototype====
	(Inputs: Design documents, CAD drawings, CNC files, BOM with costs)		(Inputs: Design documents, CAD drawings, CNC files, BOM with costs)
Line 27:		Line 40:
	*Gather tools and prepare workspace		*Gather tools and prepare workspace
	*Build		*Build
			*Video Document Build process
	====Test/Iterate====		====Test/Iterate====
	(Input: prototype unit)		(Input: prototype unit)
	Put the machine to work on site and evaluate it's capabilities. Test interface with other GVCS equipment. Adjust if needed documenting changes.		*Put the machine to work on site and evaluate it's capabilities in real conditions.
			*Test interface with other GVCS equipment.
			*Adjust if needed, documenting changes.
	====Document====		====Document====
	*Check drawings and BOM for changes against the reference implementation.		*Check drawings and BOM for changes against the reference implementation.
	*~~Collect and take~~ pictures and video		*Edit pictures and video
	*Upload material to wiki (see [[Fabrication Procedure Standards]])		*Upload and organize material on wiki (see [[Fabrication Procedure Standards]])
			*Compile and publish User Manual (How it Works, Operation Procedures, Safety, Maintenance, Troubleshooting, Repair)
	====Deploy/Replicate====		====Deploy/Replicate====
	With documentation available to the community machines can be built off site. As problems with the documentation are found or improvements are made the documentation should be revised on the wiki using a process similar to source code management. After a tool achieves release status further development will come from the community as FeF will be focusing on developing other tools.		With documentation available to the community machines can be built off site. As problems with the documentation are found or improvements are made the documentation should be revised on the wiki using a process similar to source code management. After a tool achieves release status further development will come from the community as FeF will be focusing on developing other tools.
			*Fabrication Optimization
			*User Network Development
	====Output====		====Output====
	By year-end 2012 documentation and working reference implementation for all 50 GVCS tools		By year-end 2012 documentation and working reference implementation for all 50 GVCS tools