Distributed Collaboration - Revision history

Matt Maier: /* Using the OSE Wiki */

2012-04-07T00:40:06Z

Using the OSE Wiki

← Older revision		Revision as of 00:40, 7 April 2012
Line 115:		Line 115:
	7) In another tab (or window) navigate to the page where you are going to post the definition.		7) In another tab (or window) navigate to the page where you are going to post the definition.

	8) In the appropriate section, type "<gallery> image: </gallery>" except you can put each word on a different line.		8) In the appropriate section, type "< gallery> image: < /gallery>" except you can put each word on a different line and don't include those spaces after the carrots.

	9) Paste the file name after the "image:" word.		9) Paste the file name after the "image:" word.

Matt Maier at 00:39, 7 April 2012

2012-04-07T00:39:12Z

@@ Line 97: / Line 97: @@
 ==LifeTrac Example==
 [[Media:LifeTrac Fabrication Report 25FEB2012.pdf]] This is a report that was generated from the project file and definitions detailed previously. Open Office was used to create several files, which were incorporated into a master document. The master document was then exported as a pdf. There are a few formatting issues, but the entire report is pretty much just a really long table, so that keeps things clearly organized.
 =Credentials=

Matt Maier: /* LifeTrac Example */

2012-02-26T15:50:56Z

LifeTrac Example

← Older revision		Revision as of 15:50, 26 February 2012
Line 76:		Line 76:

	==LifeTrac Example==		==LifeTrac Example==
	[[Media:OSE LifeTrac Fabrication.pod]] This is the LifeTrac OpenProj file. You can download OpenProj or free here. [http://sourceforge.net/projects/openproj/ OpenProj on Sourceforge]		[[Media:OSE LifeTrac Fabrication.pod]] This is the LifeTrac OpenProj file. You can download OpenProj for free here. [http://sourceforge.net/projects/openproj/ OpenProj on Sourceforge]

	After the definitions exist, they can be used as references for project steps. The frame member example you saw higher up on the page could be broken into two steps. The first step would be "cut to length" and would be assigned resources. This is where I tracked tools and materials for the Bill of Materials (more on that later). If you assign the piece of stock material necessary then the program tracks it for you. The second step could be "drill holes" and would also be assigned resources. In this case it's stuff like drill bits of the appropriate size. This makes it really easy to build up a list of the stuff you'll need because you can capture the information right when you're thinking about it and it's tracked forever. [[Media:Lifetrac steps in openproj.jpg]] here is a screen capture of the program so you can see what I mean.		After the definitions exist, they can be used as references for project steps. The frame member example you saw higher up on the page could be broken into two steps. The first step would be "cut to length" and would be assigned resources. This is where I tracked tools and materials for the Bill of Materials (more on that later). If you assign the piece of stock material necessary then the program tracks it for you. The second step could be "drill holes" and would also be assigned resources. In this case it's stuff like drill bits of the appropriate size. This makes it really easy to build up a list of the stuff you'll need because you can capture the information right when you're thinking about it and it's tracked forever. [[Media:Lifetrac steps in openproj.jpg]] here is a screen capture of the program so you can see what I mean.

	The best part is that when someone wants to actually replicate the LifeTrac they can use the project file to organize their work. For example, by tracking what they do, and in what order, and how long it takes them, and any extra resources they needed, they can edit the file into a perfect record of what they did (or will do, if they did that ahead of time). Then they can send a copy of their file back to the documenters and prototypers so they get exactly the feedback they need to improve the machine and the documentation.		The best part is that when someone wants to actually replicate the LifeTrac they can use the project file to organize their work. For example, by tracking what they do, and in what order, and how long it takes them, and any extra resources they needed, they can edit the file into a perfect record of what they did (or will do, if they did that ahead of time). Then they can send a copy of their file back to the documenters and prototypers so they get exactly the feedback they need to improve the machine and the documentation.

	=Reports=		=Reports=

Matt Maier at 15:50, 26 February 2012

2012-02-26T15:50:40Z

← Older revision		Revision as of 15:50, 26 February 2012
Line 76:		Line 76:

	==LifeTrac Example==		==LifeTrac Example==
	After the definitions exist, they can be used as references for project steps~~. I'll upload the OpenProj file whenever someone tells me how to do that~~. The ~~gist of it is that the~~ frame member example you saw higher up on the page could be broken into two steps. The first step would be "cut to length" and would be assigned resources. This is where I tracked tools and materials for the Bill of Materials (more on that later). If you assign the piece of stock material necessary then the program tracks it for you. The second step could be "drill holes" and would also be assigned resources. In this case it's stuff like drill bits of the appropriate size. This makes it really easy to build up a list of the stuff you'll need because you can capture the information right when you're thinking about it and it's tracked forever. [[Media:Lifetrac steps in openproj.jpg]] here is a screen capture of the program so you can see what I mean.		[[Media:OSE LifeTrac Fabrication.pod]] This is the LifeTrac OpenProj file. You can download OpenProj or free here. [http://sourceforge.net/projects/openproj/ OpenProj on Sourceforge]

			After the definitions exist, they can be used as references for project steps. The frame member example you saw higher up on the page could be broken into two steps. The first step would be "cut to length" and would be assigned resources. This is where I tracked tools and materials for the Bill of Materials (more on that later). If you assign the piece of stock material necessary then the program tracks it for you. The second step could be "drill holes" and would also be assigned resources. In this case it's stuff like drill bits of the appropriate size. This makes it really easy to build up a list of the stuff you'll need because you can capture the information right when you're thinking about it and it's tracked forever. [[Media:Lifetrac steps in openproj.jpg]] here is a screen capture of the program so you can see what I mean.

	The best part is that when someone wants to actually replicate the LifeTrac they can use the project file to organize their work. For example, by tracking what they do, and in what order, and how long it takes them, and any extra resources they needed, they can edit the file into a perfect record of what they did (or will do, if they did that ahead of time). Then they can send a copy of their file back to the documenters and prototypers so they get exactly the feedback they need to improve the machine and the documentation.		The best part is that when someone wants to actually replicate the LifeTrac they can use the project file to organize their work. For example, by tracking what they do, and in what order, and how long it takes them, and any extra resources they needed, they can edit the file into a perfect record of what they did (or will do, if they did that ahead of time). Then they can send a copy of their file back to the documenters and prototypers so they get exactly the feedback they need to improve the machine and the documentation.

Matt Maier at 17:24, 25 February 2012

2012-02-25T17:24:58Z

← Older revision		Revision as of 17:24, 25 February 2012
Line 14:		Line 14:
	* Every step which can practically be done over the internet has a method for doing that.		* Every step which can practically be done over the internet has a method for doing that.
	* Each step is flexible enough to allow people to come and go as necessary without crippling the process.		* Each step is flexible enough to allow people to come and go as necessary without crippling the process.

			=Lessons Learned=
			* The definitions > project > report process would be straight-forward to automate. The key is the "self-evident" steps. When the machine is broken down into little units, each one is simple enough to understand on its own. As long as you accomplish each individual step, you will eventually end up with a complete machine. Changes are compartmentalized so they only affect one or a few discrete steps.
			* Definitions should be created in a content library. People would upload working files, like CAD. Then, images and dimensions would be pulled out of those working files and uploaded with a descriptive title.
			* Projects should be created in whatever program works best and then that becomes a working file.
			* Reports should be compiled only after the machine has reached a point of stability. Also, there should be some sort of standardized format so that they're easy to read and important information isn't left out.
			* The entire process could be incorporated into a single tool. Or, at worst, a single workflow tool that guides the use of different tools. Each definition becomes at least on step, and each step becomes at least one line in the report. Along the way each definition/step can accumulate comments that are incorporated into the final report.

	=Concepts=		=Concepts=

Matt Maier at 17:15, 25 February 2012

2012-02-25T17:15:27Z

← Older revision		Revision as of 17:15, 25 February 2012
Line 87:		Line 87:

	==LifeTrac Example==		==LifeTrac Example==
			[[Media:LifeTrac Fabrication Report 25FEB2012.pdf]] This is a report that was generated from the project file and definitions detailed previously. Open Office was used to create several files, which were incorporated into a master document. The master document was then exported as a pdf. There are a few formatting issues, but the entire report is pretty much just a really long table, so that keeps things clearly organized.

	=Credentials=		=Credentials=

Matt Maier at 17:09, 25 February 2012

2012-02-25T17:09:35Z

← Older revision		Revision as of 17:09, 25 February 2012
Line 67:		Line 67:
	* Fourth, create any other steps necessary to shape the part. If holes are necessary, you could create <drill hole using 13/16" bit and drill>. The best thing to do is refer to a definition image that shows the correct hole locations, their dimensions, and how to locate them on the part.		* Fourth, create any other steps necessary to shape the part. If holes are necessary, you could create <drill hole using 13/16" bit and drill>. The best thing to do is refer to a definition image that shows the correct hole locations, their dimensions, and how to locate them on the part.
	* NOTE: create a different resource for every individual piece that uses different overall dimensions. It is not necessary to make two entries for parts that are both <4" x 4" x 1/4" by 3' angle>. It is necessary to make two separate entries for a parts that are <4" x 4" x 1/4" by 3' angle> and <4" x 4" x 1/4" by 4' angle>. This will ensure that the BOM is both complete and intuitive. You don't know how the replicator is going to want to obtain the correct amount of raw material. Providing them with exactly the outside dimensions of all the parts allows them the most flexibility in sourcing. For example, if there are 12 square tubes of various lengths, all under 8 feet, do not list <12 x 8' square tube> in the BOM. That is misleading. Instead, list <2 x 8'> and <4 x 7.5'> and <6 x 6.75'> so the replicator can figure out for themselves how to combine the parts to minimize waste or maximize efficiency or whatever.		* NOTE: create a different resource for every individual piece that uses different overall dimensions. It is not necessary to make two entries for parts that are both <4" x 4" x 1/4" by 3' angle>. It is necessary to make two separate entries for a parts that are <4" x 4" x 1/4" by 3' angle> and <4" x 4" x 1/4" by 4' angle>. This will ensure that the BOM is both complete and intuitive. You don't know how the replicator is going to want to obtain the correct amount of raw material. Providing them with exactly the outside dimensions of all the parts allows them the most flexibility in sourcing. For example, if there are 12 square tubes of various lengths, all under 8 feet, do not list <12 x 8' square tube> in the BOM. That is misleading. Instead, list <2 x 8'> and <4 x 7.5'> and <6 x 6.75'> so the replicator can figure out for themselves how to combine the parts to minimize waste or maximize efficiency or whatever.

			==LifeTrac Example==
			After the definitions exist, they can be used as references for project steps. I'll upload the OpenProj file whenever someone tells me how to do that. The gist of it is that the frame member example you saw higher up on the page could be broken into two steps. The first step would be "cut to length" and would be assigned resources. This is where I tracked tools and materials for the Bill of Materials (more on that later). If you assign the piece of stock material necessary then the program tracks it for you. The second step could be "drill holes" and would also be assigned resources. In this case it's stuff like drill bits of the appropriate size. This makes it really easy to build up a list of the stuff you'll need because you can capture the information right when you're thinking about it and it's tracked forever. [[Media:Lifetrac steps in openproj.jpg]] here is a screen capture of the program so you can see what I mean.

			The best part is that when someone wants to actually replicate the LifeTrac they can use the project file to organize their work. For example, by tracking what they do, and in what order, and how long it takes them, and any extra resources they needed, they can edit the file into a perfect record of what they did (or will do, if they did that ahead of time). Then they can send a copy of their file back to the documenters and prototypers so they get exactly the feedback they need to improve the machine and the documentation.

	=Reports=		=Reports=
Line 80:		Line 85:

	3) They must grant the world permission to obtain, utilize, copy and distribute the report freely.		3) They must grant the world permission to obtain, utilize, copy and distribute the report freely.

			==LifeTrac Example==


	=Credentials=		=Credentials=

Matt Maier at 16:41, 25 February 2012

2012-02-25T16:41:27Z

← Older revision		Revision as of 16:41, 25 February 2012
Line 4:		Line 4:

	The following process attempts to achieve that goal. Each step is well defined and really only a small part of the process depends on a core team of employees. The rest of the process is a way for volunteers to expand a small piece of crucial work into a diverse array of useful tools.		The following process attempts to achieve that goal. Each step is well defined and really only a small part of the process depends on a core team of employees. The rest of the process is a way for volunteers to expand a small piece of crucial work into a diverse array of useful tools.

			I developed this process while working on the [[LifeTrac]] fabrication instructions. So, since that is the only example of the full process, I'll use it as an illustration.

	=Benefits=		=Benefits=
Line 32:		Line 34:

	3) They must remain available for, and responsive to, requests for additional or rephrased definitions.		3) They must remain available for, and responsive to, requests for additional or rephrased definitions.

			==LifeTrac Example==
			[[Media:Frame outer base measurements.jpg]] This is an image created by taking a screen capture of the LifeTrac 3 CAD file. It was imported into Open Office and labels were added. The result is an illustration that should be mostly self-evident. Any details not included in the illustration would be added as an introduction to a related group of illustrations or as a caption.
			[[Media:LifeTrac 3 definitions.odt]] This is a table created by taking a lot of those illustrations, putting them in a list, then adding headings and explanations. In Open Office, if you use the styles & formatting menu to assign "heading 1" to some text, that text can be automatically incorporated into an index, making the large document easier to navigate.

			It turns out there are a lot of man-hours involved in this stuff. Since I was working on my own, I used my hard drive as a content library. There is no reason an online file library couldn't be used instead.

	=Projects=		=Projects=

Matt Maier at 02:06, 21 February 2012

2012-02-21T02:06:06Z

← Older revision		Revision as of 02:06, 21 February 2012
Line 79:		Line 79:

	=References=		=References=
	"The data of the GVCS truly constitutes its value, and as such cannot be trusted to a single, centralized source. An additional hurdle is the disconnected, intermittent and limited (DIL) connectivity of some users of the global SoS" - [http://gvcs.heroku.com/file/Bollweg2011.pdf N Bollweg, A System of Systems Analysis of the Global Village Construction Set]		"The data of the GVCS truly constitutes its value, and as such cannot be trusted to a single, centralized source. An additional hurdle is the disconnected, intermittent and limited (DIL) connectivity of some users of the global SoS."

			"A distributed version control system could assist tremendously in decentralizing the GVCS workflow, as well as protect the critical data assets of the GVCS global knowledge store through distributed duplication...Making distributed version control more user-friendly represents a significant task in its own right."
			- [http://gvcs.heroku.com/file/Bollweg2011.pdf N Bollweg, A System of Systems Analysis of the Global Village Construction Set]

Matt Maier at 01:57, 21 February 2012

2012-02-21T01:57:35Z

← Older revision		Revision as of 01:57, 21 February 2012
Line 77:		Line 77:

	I graduated from the Air Force Academy with a degree in Systems Engineering Management. Now I work as a satellite ground system engineer.		I graduated from the Air Force Academy with a degree in Systems Engineering Management. Now I work as a satellite ground system engineer.

			=References=
			"The data of the GVCS truly constitutes its value, and as such cannot be trusted to a single, centralized source. An additional hurdle is the disconnected, intermittent and limited (DIL) connectivity of some users of the global SoS" - [http://gvcs.heroku.com/file/Bollweg2011.pdf N Bollweg, A System of Systems Analysis of the Global Village Construction Set]