OSE Credit - Revision history

Marcin at 22:26, 26 December 2014

2014-12-26T22:26:34Z

← Older revision		Revision as of 22:26, 26 December 2014
Line 1:		Line 1:
	OSE Credit measures commits to the OSE GVCS Development Boards for any of the 50 GVCS Projects.		OSE Credit - or '''OSE Cred''' - measures commits to the OSE GVCS Development Boards for any of the 50 GVCS Projects.

	OSE uses Module Based Design - to break down complex products, machines, and [[Product Service Systems]] into many components - such that projects can be developed in bite-sized chunks.		OSE uses Module Based Design - to break down complex products, machines, and [[Product Service Systems]] into many components - such that projects can be developed in bite-sized chunks.
Line 14:		Line 14:
	#As progress occurs, development techniques are refined, resulting in more efficient development. This is because the overall development technique has high complexity, and it takes time for organizational learning to happen.		#As progress occurs, development techniques are refined, resulting in more efficient development. This is because the overall development technique has high complexity, and it takes time for organizational learning to happen.
	#OSE is developing revenue models associated with the production and use of products and [[Product Service Systems]] based on the [[GVCS]]. For this reason, we are expecting that more people will begin to participate as full-time developers, based on bootsrapping revenue from the project. We do understand that this is not easy, for which we will be piloting specific immersion training for entrepreneurs starting in 2015.		#OSE is developing revenue models associated with the production and use of products and [[Product Service Systems]] based on the [[GVCS]]. For this reason, we are expecting that more people will begin to participate as full-time developers, based on bootsrapping revenue from the project. We do understand that this is not easy, for which we will be piloting specific immersion training for entrepreneurs starting in 2015.

			OSE should consider ways in which contributors are rewarded for their Credit.

Marcin at 21:44, 26 December 2014

2014-12-26T21:44:22Z

← Older revision		Revision as of 21:44, 26 December 2014
Line 13:		Line 13:
	#Development of a module for one machine or system is relevant to other machine modules. With minor modification, a certain module may be utilized in another part of the GVCS		#Development of a module for one machine or system is relevant to other machine modules. With minor modification, a certain module may be utilized in another part of the GVCS
	#As progress occurs, development techniques are refined, resulting in more efficient development. This is because the overall development technique has high complexity, and it takes time for organizational learning to happen.		#As progress occurs, development techniques are refined, resulting in more efficient development. This is because the overall development technique has high complexity, and it takes time for organizational learning to happen.
			#OSE is developing revenue models associated with the production and use of products and [[Product Service Systems]] based on the [[GVCS]]. For this reason, we are expecting that more people will begin to participate as full-time developers, based on bootsrapping revenue from the project. We do understand that this is not easy, for which we will be piloting specific immersion training for entrepreneurs starting in 2015.

Marcin at 21:42, 26 December 2014

2014-12-26T21:42:17Z

← Older revision		Revision as of 21:42, 26 December 2014
Line 5:		Line 5:
	In order for this to happen, careful attention has to be paid to identifying and understanding Interfaces between the components and parts. When there is no clear fit between 2 parts - in order to make modular design applicable universally - [[Wrapper]]s may be used.		In order for this to happen, careful attention has to be paid to identifying and understanding Interfaces between the components and parts. When there is no clear fit between 2 parts - in order to make modular design applicable universally - [[Wrapper]]s may be used.

	Every project is broken down into about a dozen modules, and 100 development items		Every project is broken down into about a dozen modules (or more), and each module contains 100+ development items. Each Development template has a scale of completion ranging from 0-10.

			Therefore, there are 50 GVCS machines x 12 x 100 x 10 points in the overall GVCS burndown - for a total of about 500,000 points of credit. Each machine contains about 50,000 points of credit. 10 points of credit corresponds to one Development Template item - and its general time requirement is 10 hours for completion - or one full day of work.

			The specific nature of the work required for the completion of one item may vary, and as the GVCS completion expand, exponential acceleration of development rate is expected to happen for 3 reasons:

			#Development of a module for one machine or system is relevant to other machine modules. With minor modification, a certain module may be utilized in another part of the GVCS
			#As progress occurs, development techniques are refined, resulting in more efficient development. This is because the overall development technique has high complexity, and it takes time for organizational learning to happen.

Marcin at 21:33, 26 December 2014

2014-12-26T21:33:58Z

← Older revision		Revision as of 21:33, 26 December 2014
Line 3:		Line 3:
	OSE uses Module Based Design - to break down complex products, machines, and [[Product Service Systems]] into many components - such that projects can be developed in bite-sized chunks.		OSE uses Module Based Design - to break down complex products, machines, and [[Product Service Systems]] into many components - such that projects can be developed in bite-sized chunks.

	In order for this to happen, careful attention has to be paid to identifying and understanding Interfaces between the components and parts. When there is no clear fit between 2 parts - in order to make modular design applicable universally - ~~wrappers may be created for the components or parts. See~~ [[Wrapper]].		In order for this to happen, careful attention has to be paid to identifying and understanding Interfaces between the components and parts. When there is no clear fit between 2 parts - in order to make modular design applicable universally - [[Wrapper]]s may be used.

	Every project is broken down into about a dozen modules, and 100 development items		Every project is broken down into about a dozen modules, and 100 development items

Marcin: Created page with "OSE Credit measures commits to the OSE GVCS Development Boards for any of the 50 GVCS Projects. OSE uses Module Based Design - to break down complex products, machines, and [..."

2014-12-26T21:27:02Z

Created page with "OSE Credit measures commits to the OSE GVCS Development Boards for any of the 50 GVCS Projects. OSE uses Module Based Design - to break down complex products, machines, and [..."

New page

OSE Credit measures commits to the OSE GVCS Development Boards for any of the 50 GVCS Projects.

OSE uses Module Based Design - to break down complex products, machines, and [[Product Service Systems]] into many components - such that projects can be developed in bite-sized chunks.

In order for this to happen, careful attention has to be paid to identifying and understanding Interfaces between the components and parts. When there is no clear fit between 2 parts - in order to make modular design applicable universally - wrappers may be created for the components or parts. See [[Wrapper]].

Every project is broken down into about a dozen modules, and 100 development items