I have mixed feelings about the relevance of PLM as defined in the referenced wikipedia page to a hacker/ maker based approach to some notion of product, but also generally as it relates to the kinds of discovery and problem solving this SpaceGAMBIT effort is wanting to encourage. <div>
<br></div><div>As we step towards more and more complex solutions, I think some of the PLM tools will be helpful in managing inventories of parts for projects or solutions. This will be especially useful where the tool can support complex solutions with many thousands of parts, and where distributed, parallel and collaborative solution development will occur, such as multiple teams working in parallel on subsystems as part of a larger product. If a product doesn't readily support that, it's probably of less use to us.<br>
<div><br></div><div>Of course, our SpaceGAMBIT projects - and probably ultimately products and services - will have life cycles, but I think good life-cycle models are largely a reflection of the underlying philosophy and culture or the people involved.</div>
<div><br></div><div>In my view, PLM as described in the referenced Wikipedia article, appears as a cleanly phased, sequential approach, where a product passes through a series of stage gates from concept through to use and finally disposal. Of course, these phases do describe things that happen during the life cycle of a typical product-development effort, however they aren't necessarily relevant as phases. Although the Wikipedia page mentions that LCE is iterative, the PLM defined here doesn't reflect that well. It does briefly refer to "backing up" into earlier phase, but as an experienced method author, I find it kind of sloppy when a method is idealised to a point where it doesn't suitably reflect and support reality, appears to address real world concerns by passing reality off as an exception, and then claims to be practically useful to enact PLM.</div>
<div><div><br class="Apple-interchange-newline">From a method architecture perspective, I think there is little value in having an overarching product lifecycle model that simply reflects the detailed activity that obviously needs to occur: for me, it's equivalent to having a "hammer nail" activity within a "hammer nail" phase. Phases for me need to speak to useful and important strategic goals. But more to the point, I think this type of PLM philosophy doesn't reflect the reality of PLM in exploratory, evolutionary prototyping - the very approach that makes hacker and maker spaces what they are.</div>
<div><br></div></div><div>My closing critique is that the definition here appears to be based predominantly on information drawn from the field of automotive engineering, a context where the basic product is arguably very well understood. I tread with caution when applying methods and practices suitable in one context to different context. How much does the building of cars using standardised assembly line production have relevance to hacker/ maker creation of new products in the context of space exploration?</div>
<div><br></div><div><br></div><div><br>Paul<br> <br>Paul Szymkowiak <br><div><br></div><br><div class="gmail_quote">On 16 September 2012 09:39, Jerry Isdale <span dir="ltr"><<a href="mailto:jerry@mauimakers.com" target="_blank">jerry@mauimakers.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Couple very interesting Project Management talks here at 100YSS relating to this.<div>
One on a product, one on use of general PMBOK to address physics advances.</div><div>more later.</div><div><div class="im"><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
Jerry Isdale<br><a href="http://MauiMakers.com" target="_blank">http://MauiMakers.com</a></div><div style="word-wrap:break-word"><a href="http://www.mauimakers.com/blog/thursday-public-meeting/" target="_blank">http://www.mauimakers.com/blog/thursday-public-meeting/</a></div>
</span></div></span></span>
</div>
<br></div><div><div class="h5"><div><div>On Sep 15, 2012, at 9:20 AM, cole santos wrote:</div><br><blockquote type="cite">Using this as a framework for developing our grant/prize structure would be useful as well. Each project will be responsible for their own management styles, by structuring the contest to support PLM we could encourage success. Stages of competition could be as in the Wikipedia. (i added theoretical prize/grant amounts). Moving up stage wise would require previous success at a lower level to be assessed by the members/peers/backers.<ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px">
<li style="font-family:sans-serif;font-size:13px;line-height:19.200000762939453px;margin-bottom:0.1em">Conceive - Stage 1 (10-100$)<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px">
<li style="margin-bottom:0.1em"><a href="https://en.wikipedia.org/wiki/Specification" title="Specification" style="text-decoration:none;color:rgb(11,0,128);background-image:none;background-repeat:initial initial" target="_blank">Specification</a></li>
<li style="margin-bottom:0.1em">Concept design</li></ul></li><li style="font-family:sans-serif;font-size:13px;line-height:19.200000762939453px;margin-bottom:0.1em">Design - Stage 2 (100-1000$)<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px">
<li style="margin-bottom:0.1em">Detailed design</li><li style="margin-bottom:0.1em">Validation and analysis (simulation)</li><li style="margin-bottom:0.1em">Tool design</li></ul></li><li style="font-family:sans-serif;font-size:13px;line-height:19.200000762939453px;margin-bottom:0.1em">
Realize - Stage 3 (1000-10000$ + outside funding)<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">Plan manufacturing</li><li style="margin-bottom:0.1em">
Manufacture</li><li style="margin-bottom:0.1em">Build/Assemble</li><li style="margin-bottom:0.1em">Test (<a href="https://en.wikipedia.org/w/index.php?title=Quality_check&action=edit&redlink=1" title="Quality check (page does not exist)" style="text-decoration:none;color:rgb(165,88,88);background-image:none;background-repeat:initial initial" target="_blank">quality check</a>)</li>
</ul></li><li style="margin-bottom:0.1em"><font face="sans-serif"><span style="line-height:19.200000762939453px">Service - Stage 4 (</span></font><font face="sans-serif"><span style="line-height:19.196969985961914px">incorporation</span></font><font face="sans-serif"><span style="line-height:19.200000762939453px"> of ideas into GAMBIT superstructure)</span></font><ul style="font-family:sans-serif;font-size:13px;line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px">
<li style="margin-bottom:0.1em">Sell and deliver</li><li style="margin-bottom:0.1em">Use</li><li style="margin-bottom:0.1em"><a href="https://en.wikipedia.org/wiki/Maintenance" title="Maintenance" style="text-decoration:none;color:rgb(11,0,128);background-image:none;background-repeat:initial initial" target="_blank">Maintain</a> and support</li>
<li style="margin-bottom:0.1em">Dispose</li></ul></li></ul><br><div class="gmail_quote">On Sun, Sep 16, 2012 at 8:36 AM, Brent Shambaugh <span dir="ltr"><<a href="mailto:brent.shambaugh@gmail.com" target="_blank">brent.shambaugh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is a bit of a long read, but it gives some idea of what Product<br>
Lifecycle Management is:<br>
<br>
<a href="https://en.wikipedia.org/wiki/Product_lifecycle_management" target="_blank">https://en.wikipedia.org/wiki/Product_lifecycle_management</a><br>
<br>
I think you'll be impressed by what's out there, if you haven't seen<br>
it already. I keep thinking that stuff like this will help out in the<br>
long run. Boeing used it. See Dassault Systemes at<br>
<a href="http://www.3ds.com/" target="_blank">http://www.3ds.com/</a>.<br>
<br>
I've started a group that is into this sort of stuff, but it may be<br>
awhile before anything cool comes out of it. I'll start digging into<br>
it more.<br>
<div><div><br>
On Fri, Sep 14, 2012 at 11:50 PM, Brent Shambaugh<br>
<<a href="mailto:brent.shambaugh@gmail.com" target="_blank">brent.shambaugh@gmail.com</a>> wrote:<br>
> I like Rizzoma's semantic web ideas. I've also found a number of open<br>
> source tools in the Product Lifecycle Management arena. Aras<br>
> (<a href="http://www.aras.com/" target="_blank">http://www.aras.com/</a>) has its own open source license and is<br>
> available for Windows. OpenPLM is available under GPLv3<br>
> (<a href="http://sourceforge.net/projects/open-source-plm/" target="_blank">http://sourceforge.net/projects/open-source-plm/</a>), and Sparta is<br>
> available under AGPL (<a href="https://github.com/scientia/sparta" target="_blank">https://github.com/scientia/sparta</a>).<br>
><br>
><br>
> On Wed, Sep 12, 2012 at 2:28 PM, Bradley Grzesiak <<a href="mailto:listrophy@gmail.com" target="_blank">listrophy@gmail.com</a>> wrote:<br>
>> It's *kinda* open source. You have to ask for the source... which is kinda<br>
>> weird.<br>
>><br>
>> :brad<br>
>><br>
>><br>
>> On Wed, Sep 12, 2012 at 1:35 PM, Jerry Isdale <<a href="mailto:jerry@mauimakers.com" target="_blank">jerry@mauimakers.com</a>> wrote:<br>
>>><br>
>>> "All existing communication and collaboration tools display messages<br>
>>> chronologically and in a linear way making a context fragmented and<br>
>>> difficult to comprehend.... Rizzoma allows communication within a certain<br>
>>> context permitting a chat to instantly become a document where topics of a<br>
>>> discussion organized into branches of mind-map diagram and minor details are<br>
>>> collapsed to avoid distraction."<br>
>>><br>
>>> Free and open source. Hmmm.<br>
>>> Worth watching and checking into deeper.<br>
>>> Not sure about the 'everyone writes everywhere' model. Sometimes you want<br>
>>> a semi-closed project, that others might comment but not edit or be hidden<br>
>>> from view. Might be a way to do that too. Heck it is Open Source.<br>
>>><br>
>>> Jerry Isdale<br>
>>> <a href="http://MauiMakers.com/" target="_blank">http://MauiMakers.com</a><br>
>>> <a href="http://www.mauimakers.com/blog/thursday-public-meeting/" target="_blank">http://www.mauimakers.com/blog/thursday-public-meeting/</a><br>
>>><br>
>>> On Sep 12, 2012, at 7:21 AM, Brent Shambaugh wrote:<br>
>>><br>
>>> > Here's a collaboration tool.<br>
>>> ><br>
>>> > <a href="http://rizzoma.com/" target="_blank">http://rizzoma.com/</a><br>
>>> ><br>
>>> > -Brent<br>
>>> > _______________________________________________<br>
>>> > SpaceProgram mailing list<br>
>>> > <a href="mailto:SpaceProgram@lists.hackerspaces.org" target="_blank">SpaceProgram@lists.hackerspaces.org</a><br>
>>> > <a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
>>><br>
>>> _______________________________________________<br>
>>> SpaceProgram mailing list<br>
>>> <a href="mailto:SpaceProgram@lists.hackerspaces.org" target="_blank">SpaceProgram@lists.hackerspaces.org</a><br>
>>> <a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Bradley Grzesiak<br>
>> co-founder, bendyworks<br>
>> <a href="http://bendyworks.com/" target="_blank">http://bendyworks.com/</a><br>
>><br>
>> _______________________________________________<br>
>> SpaceProgram mailing list<br>
>> <a href="mailto:SpaceProgram@lists.hackerspaces.org" target="_blank">SpaceProgram@lists.hackerspaces.org</a><br>
>> <a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
>><br>
_______________________________________________<br>
SpaceProgram mailing list<br>
<a href="mailto:SpaceProgram@lists.hackerspaces.org" target="_blank">SpaceProgram@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
</div></div></blockquote></div><br>
_______________________________________________<br>SpaceProgram mailing list<br><a href="mailto:SpaceProgram@lists.hackerspaces.org" target="_blank">SpaceProgram@lists.hackerspaces.org</a><br><a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
SpaceProgram mailing list<br>
<a href="mailto:SpaceProgram@lists.hackerspaces.org">SpaceProgram@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/spaceprogram" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/spaceprogram</a><br>
<br></blockquote></div><br></div></div>