<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.opensourceecology.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=David+Lemmer</id>
	<title>Open Source Ecology - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.opensourceecology.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=David+Lemmer"/>
	<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/wiki/Special:Contributions/David_Lemmer"/>
	<updated>2026-05-09T13:38:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.13</generator>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269870</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269870"/>
		<updated>2022-04-30T20:05:50Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
https://wiki.opensourceecology.org/images/c/c9/OSE_Requirements_decomposition_4-30-2022.png&lt;br /&gt;
&lt;br /&gt;
The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements are met(satisfied). Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. As this requirement decomposition is progressed updates will be posted here and Eclipse IDE SysM: 2/0 Script will be posted at the bottom of this post. &lt;br /&gt;
&lt;br /&gt;
The other diagram types in SysML are structural and behavioral diagrams(See https://www.omgsysml.org/what-is-sysml.htm). These structural diagrams enable the sub-systems(organizations, tools, ect [things]) to be described. The behavioral diagrams are all about describing the activities, processes, and states(Verbs) the various structural elements will be engaged in. The combination of a methodology and the SysML language allows for systems to be rigorously and intentionally designed; simultaneously with the validation of business and stakeholder concerns tied back to the analyses conducted based on the parameters and processes of the system being designed.&lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269869</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269869"/>
		<updated>2022-04-30T17:30:31Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
https://wiki.opensourceecology.org/images/c/c9/OSE_Requirements_decomposition_4-30-2022.png&lt;br /&gt;
&lt;br /&gt;
The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. &lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=File:OSE_Requirements_decomposition_4-30-2022.png&amp;diff=269868</id>
		<title>File:OSE Requirements decomposition 4-30-2022.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=File:OSE_Requirements_decomposition_4-30-2022.png&amp;diff=269868"/>
		<updated>2022-04-30T17:28:43Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269867</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269867"/>
		<updated>2022-04-30T17:27:34Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
[[Image:filename.png]]&lt;br /&gt;
&lt;br /&gt;
The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. &lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269866</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269866"/>
		<updated>2022-04-30T17:21:06Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
[[Image:filename.jpg]]&lt;br /&gt;
&lt;br /&gt;
The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. &lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269675</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269675"/>
		<updated>2022-04-26T23:48:10Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;Insert Diagram here&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. &lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269568</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=269568"/>
		<updated>2022-04-25T11:19:36Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
=Mon Apr 25, 2022=&lt;br /&gt;
&lt;br /&gt;
SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).&lt;br /&gt;
&lt;br /&gt;
SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML. &lt;br /&gt;
&lt;br /&gt;
=Mon Jan 25, 2021=&lt;br /&gt;
Hi David,&lt;br /&gt;
I don&#039;t know what you are up to - but if you can, continue logging on your log. &lt;br /&gt;
I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don&#039;t have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it&#039;s not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at&lt;br /&gt;
 https://wiki.opensourceecology.org/wiki/Operations_Manual&lt;br /&gt;
The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.&lt;br /&gt;
I put this on your log.&lt;br /&gt;
MJ&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228608</id>
		<title>Enterprise Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228608"/>
		<updated>2020-07-25T20:14:43Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Tues July 21, 2020 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Tues July 21, 2020=&lt;br /&gt;
Primary goal , &lt;br /&gt;
&lt;br /&gt;
Develop product marketization process. Does anyone have any formal architecture documented on what all the roles included in that are?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Role Architecting Strategies&#039;&#039;&#039;,&lt;br /&gt;
&lt;br /&gt;
1)&lt;br /&gt;
Teams make up is derived by grouping the user stories into logical sets that combine to produce a minimally viable product (module).&lt;br /&gt;
&lt;br /&gt;
Then assigning roles based on the unique skill sets required to deliver the minimally viable product.&lt;br /&gt;
&lt;br /&gt;
2)&lt;br /&gt;
performing modular functional decomposition of a subsystem&lt;br /&gt;
&lt;br /&gt;
Generate role composition requirements for each subsystem by analyzing skillsets needed to instantiate the subsystem.&lt;br /&gt;
&lt;br /&gt;
Roles that need to be understood and integrated into the enterprise system: &lt;br /&gt;
&lt;br /&gt;
Legal: contracts, zoning issues and permits, marketing copy, &lt;br /&gt;
&lt;br /&gt;
Management: product strategy, product management, sourcing, economic analysis, logistics,&lt;br /&gt;
&lt;br /&gt;
Technical: web design, video, documentation, distribution, production, &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Technical Breakdown+Modularization Strategy&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Template development Strategy &lt;br /&gt;
Decompose the target product into a set of Modules such that each module provides a &#039;&#039;&#039;Specific&#039;&#039;&#039; and &#039;&#039;&#039;independent function&#039;&#039;&#039;. Constrain any module components that create functionality with other modules(interfaces) in the template to insure module interchangeability (examples: inputs/outputs, Connectors, fasteners, Signal/language type, and all known spatial constraints.)&lt;br /&gt;
&lt;br /&gt;
Example, Seed Eco-Home&lt;br /&gt;
1: Decide wall module dimensions (because this module logically contains all other modules. Constraining dimensions will enable module interchangability after Extreme Enterprise event.)&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems.&lt;br /&gt;
4: combine these together in a CAD assembly to act as the total product template&lt;br /&gt;
5. Assign performance goals for each module&lt;br /&gt;
&lt;br /&gt;
These templates enable &#039;&#039;&#039;marketing&#039;&#039;&#039; efforts by providing a technical outline of the job. Templates also contribute to &#039;&#039;&#039;value delivery&#039;&#039;&#039; by providing performance goals that will inform designer decision making processes during the XE event.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Value Delivery Breakdown&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Seed Eco-home example:&lt;br /&gt;
the house, builder training, publications, model kits, real kits, etc&lt;br /&gt;
&lt;br /&gt;
each of these provide value to OSE, The end-user, and/or the collaborator&lt;br /&gt;
&lt;br /&gt;
=Thu May 11, 2020=&lt;br /&gt;
Welcome to the Open Source Everything Store. Home of Distributed Quality Control.&lt;br /&gt;
&lt;br /&gt;
=Wed May 10, 2020=&lt;br /&gt;
==Steve Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;280&amp;quot; height=&amp;quot;160&amp;quot; src=&amp;quot;https://www.youtube.com/embed/dKLKupfI5l4&amp;quot; frameborder=&amp;quot;0&amp;quot; allow=&amp;quot;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&amp;quot; allowfullscreen&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Wouldn&#039;t work if distribution is not setup&lt;br /&gt;
*It would fail if products are not QA&#039;d&lt;br /&gt;
*Inconsistency would make it fail. Model would break&lt;br /&gt;
*Love the idea.&lt;br /&gt;
*Love the opportunity&lt;br /&gt;
*Both ego and economic are in&lt;br /&gt;
*Inventing something that never existed before.&lt;br /&gt;
*If I am building a cordless drill that is also a welder - but that would be great.&lt;br /&gt;
*We can fail if we do something that has never been done before. For the higher complexity product, we need full prize money etc.&lt;br /&gt;
*That presupposes the marketing success, viability as a product&lt;br /&gt;
*Market-based partners.&lt;br /&gt;
*Work-from-home opportunities&lt;br /&gt;
*Makers, hobbyists - intro to, semi- to advanced - to extreme enterprise workshops&lt;br /&gt;
*Biz opportunity program.&lt;br /&gt;
*Sign up and pay for event - distribution set up beforehand?&lt;br /&gt;
*Event can come up with more nuanced distribution channels.&lt;br /&gt;
*So say it&#039;s a 3D printed motor.&lt;br /&gt;
*Activate marketing to the site.&lt;br /&gt;
*Amazon store, etc.&lt;br /&gt;
*It&#039;s for both people who have distribution channels, and without distro channels.&lt;br /&gt;
*Orders come in, we distribute them out to people who were involved in the production.&lt;br /&gt;
*70% goes on to producer, 30% goes to OSE. They are not doing the marketing. They are the production effort.&lt;br /&gt;
*Education - it&#039;s not only education; but through marketplace, we educate consumers about open source.&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
This is about Enterprise in a Box - not about 3D Printed Electric Motor. Identify, find, and incentivize, and retain to show up for a 24 Hour &#039;&#039;&#039;Extreme Enterprise Event&#039;&#039;&#039;, and how do you keep them motivated. Architecture must produce product, while keeping them motivated. Product is the reward, but, if they don&#039;t last the 24th hours. Bc it is remote, there is an extra challenge over the on-site hackathon.&lt;br /&gt;
&lt;br /&gt;
#Who are they&lt;br /&gt;
#Where do we find them&lt;br /&gt;
#How do we attract them?&lt;br /&gt;
#How do we structure an event that gets results - playful vs gsd &lt;br /&gt;
&lt;br /&gt;
Assumes a short event for producing a business consisting of one product.&lt;br /&gt;
&lt;br /&gt;
Terminology: producing a business construction set. A method rather than product. Even though there is a product.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Enterprise in a Box Startup Camp&#039;&#039;&#039;. An enterprise generator.&lt;br /&gt;
&lt;br /&gt;
They are creating a kit.&lt;br /&gt;
&lt;br /&gt;
That may not address engineers, so attract them in. A more nerdy way.&lt;br /&gt;
&lt;br /&gt;
We are solving for a motivation, incentive issue. There is discrepancy between attracting and retaining them. With remote, you get extra risk of dropping out.&lt;br /&gt;
&lt;br /&gt;
It&#039;s either 12 hours + 2 hr presentation or weekend.&lt;br /&gt;
&lt;br /&gt;
Either one night or 2 day. Fri Eve to Sun evening.&lt;br /&gt;
&lt;br /&gt;
=May 6, 2020=&lt;br /&gt;
We are solving for Extreme Enterprise: &#039;&#039;&#039;how do we get people who are already in an existing business to collaborate on making better products, while being open to distributing the same enterprise to others.&#039;&#039;&#039; Prerequisite is that they must be collaborative. But more for spinning off new products/business closely related to and synergistic with, but not just their products. The new enterprise must be bigger-faster-stronger - and easier to implement - or otherwise - why bother collaborating? The assumption is that we do more with less (more product, less time required) by collaborating.&lt;br /&gt;
&lt;br /&gt;
Right now the current state is do more with less - by monopolizing industries. This is extractive and win-lose, as it is not inclusive of the environment and others.&lt;br /&gt;
&lt;br /&gt;
And the &#039;bigger-faster-stronger&#039; has several properties enabled by collaboration:&lt;br /&gt;
&lt;br /&gt;
#Reduce number of specialized parts. Part degeneracy, for interoperability - 10x value to customer&lt;br /&gt;
#Modular so we can have multipurpose functiionality&lt;br /&gt;
#&#039;&#039;&#039;Localize supply chain.&#039;&#039;&#039; Such as Made in the USA. Enable local supply chain for supply chain robustness. Local supply chain network of producers - we make partnerships&lt;br /&gt;
#Collaboration along an open source, distributive franchise route - so we guarantee &#039;free&#039; future R&amp;amp;D via collaborative effort.&lt;br /&gt;
#Stop the demise of the American Empire, while leveling the field for everyone.&lt;br /&gt;
&lt;br /&gt;
Summary: development of enterprise with stakeholders:&lt;br /&gt;
#Improves their products&lt;br /&gt;
#Starts competing businesses (free enterprise) - Distributive Enterprise&lt;br /&gt;
#Unleashes innovation towards easy meeting of needs&lt;br /&gt;
#Transforms the world toward self-determination, as people no longer struggle to make a living. This de-fuses political ponerology and post-truthism and polarization - as politics (money) is no longer so controversial.&lt;br /&gt;
&lt;br /&gt;
==Measuring Distributive Enterprise in Companies==&lt;br /&gt;
*How do you know that a business is distributive? You ask - Does a company actively document their business knowhow which enables others to learn from this knowhow? And for what reason?&lt;br /&gt;
**Ideal answer is yes, and reason is for helping others/increasing innovation knowing that we are all in it together. And of course that is part of a value proposition that improves marketing - but marketing is not the primary reason for doing it - but spreading wealth is.&lt;br /&gt;
&lt;br /&gt;
==Sample Companies==&lt;br /&gt;
*Adafruit&lt;br /&gt;
*Gigabot&lt;br /&gt;
*Farmbot&lt;br /&gt;
*PP Bazaar - Guenther&lt;br /&gt;
*Sparkfun&lt;br /&gt;
*Daniele Ingrasia Fab Lab&lt;br /&gt;
*Jens Dyvik Fab Lab&lt;br /&gt;
&lt;br /&gt;
These are all successful ones - but the question is, how do we also involve smaller ones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Prerequisite&#039;&#039;&#039; is familiarity with open source or some form of collaboration - cannot be completely new to the topic as there is too much getting on the same page. There are plenty of people who do understand open. Also, just because they are in an open source project, doesn&#039;t mean that they carry the culture - for example if the project does not vet for formal open culture (documentation and repos). Another is running some sort of business, as that vets for a basic level of market-proven value proposition, as opposed to hobby or academic only.&lt;br /&gt;
&lt;br /&gt;
The only academic exception is those academics who intend to start productive enterprise.&lt;br /&gt;
&lt;br /&gt;
=May 5, 2020=&lt;br /&gt;
Working on clarity for &amp;quot;&#039;&#039;&#039;What problem are we solving?&#039;&#039;&#039;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Yesterday I got insight into &#039;&#039;&#039;[[Extreme Enterprise]]&#039;&#039;&#039; as the last missing frontier in OSE&#039;s package. This means: Efficient development of enterprise on rapid time scale, equivalent to the the development of products with [[Extreme Manufacturing]], such as 1 day, which in turn provides financial feedback loops that allow it to scale. This is like Extreme Manufacturing, but for fully refined machines that displace the central factory in favor of the distributed microfactory.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for the 80/20 transfer - transfer from 80% wealth captured by investors, to 80% captured by producers and workers. It is only just that those who actually produce should be paid for their work. There is less conflict of interest compared to investors dictating production.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;getting people to show up&#039; voluntarily to public [[OSPD]] events such as the 24 hour [[Enterprise Sprints]]. &lt;br /&gt;
&lt;br /&gt;
We have perfected, at least in theory, and tested all of the pieces - of collaboration architecture for product development. &lt;br /&gt;
&lt;br /&gt;
We are solving for Bodies Showing Up - so that all the roles required for a development process can be fulfilled.&lt;br /&gt;
&lt;br /&gt;
But also, the collaboration architecture must be tight in that&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;&#039;&#039;Bodies Showing Up&#039;&#039;&#039;. For example, the Open Source Microfactory STEAM Camp is sparse and Completion Escape Velocity is nowhere near done.&lt;br /&gt;
&lt;br /&gt;
Solution is inviting more people, but what is the incentive for people showing up? Can it be that we invite entrepreneurs who are already into production, and want to expand their product line, AND others who are not producing who want to produce?&lt;br /&gt;
&lt;br /&gt;
Clear assumption is that open source collaboration produces better-faster-stronger results - &#039;&#039;&#039;and distributes access to them&#039;&#039;&#039;. Why are we not creating institutions that do this?&lt;br /&gt;
&lt;br /&gt;
We are solving for just that: mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
The challenge is massive social upheaval (people don&#039;t know what to do with themselves when they have freedom to think) - a condition that people can adjust to readily, but most may not be immediately ready for that. Massive social upheaval arises when consumerism (filling spiritual needs with material items) is abolished via abundance.&lt;br /&gt;
&lt;br /&gt;
We may be solving for the fundamental issue of wealth distribution, and to distribute wealth in the big picture. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039; Small businesses, which account for 99.7% of all companies, generate less than 2/3 of the U.S.’s new jobs – which means that the .03% of companies that are big create one out of every three new jobs, more than pulling their weight.&#039;&#039; - [https://www.factorfinders.com/small-business-job-creation-vs-big]&lt;br /&gt;
&lt;br /&gt;
=Apr 6, 2020=&lt;br /&gt;
&lt;br /&gt;
[[Enterprise Metrics Log]]&lt;br /&gt;
&lt;br /&gt;
=January 1, 2016=&lt;br /&gt;
Explicit pursuit of [[D3D]] as a Distributive Enterprise, along with the Brick Press - see [[Roadmap]].&lt;br /&gt;
&lt;br /&gt;
=Thu July 9, 2015=&lt;br /&gt;
Local CSA enterprise. Local CSA with open source pellet-fired microcar delivery, bread from open source bread oven, aquaponics greenhouse greens, and sprouts from open source sprout machine. Pellets from open source pelletizer. Biochar from open source pelletizer/ winter greenhouse heater. Open source combine harvests wheat. $25/hr revenue projections for Milestone 1. &lt;br /&gt;
&lt;br /&gt;
=Sat Apr 25, 2015=&lt;br /&gt;
History of OSE should be placed on timeline like in [http://www.ros.org/history/]&lt;br /&gt;
&lt;br /&gt;
=April 21, 2015=&lt;br /&gt;
With time, OSE is gaining structure and identity - like a human in development. As of April 2015, we began discussing training OSE volunteers into leadership positions. This is due to [[Jonathan Kocurek]] stepping up to Community Manager, and [[Laura Colcord]] helping directly on the Leadership Training webinar. We are finding that we need to train our people in order to enhance OSE&#039;s development efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category:Logs]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228607</id>
		<title>Enterprise Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228607"/>
		<updated>2020-07-25T20:10:05Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Tues July 21, 2020 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Tues July 21, 2020=&lt;br /&gt;
Primary goal , &lt;br /&gt;
&lt;br /&gt;
Develop product marketization process. Does anyone have any formal architecture documented on what all the roles included in that are?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Role Architecting Strategies&#039;&#039;&#039;,&lt;br /&gt;
&lt;br /&gt;
1)&lt;br /&gt;
Teams make up is derived by grouping the user stories into logical sets that combine to produce a minimally viable product[module].&lt;br /&gt;
&lt;br /&gt;
Then assigning roles based on the unique skill sets required to deliver the minimally viable product.&lt;br /&gt;
&lt;br /&gt;
2)&lt;br /&gt;
performing modular functional decomposition of a subsystem&lt;br /&gt;
&lt;br /&gt;
Generate role composition requirements for each subsystem by analyzing skillsets needed to instantiate the subsystem.&lt;br /&gt;
&lt;br /&gt;
Roles that need to be understood and integrated into the enterprise system: &lt;br /&gt;
&lt;br /&gt;
Legal: contracts, zoning issues and permits, marketing copy, &lt;br /&gt;
&lt;br /&gt;
Management: product strategy, product management, sourcing, economic analysis&lt;br /&gt;
 logistics,&lt;br /&gt;
&lt;br /&gt;
Technical: web design, video, documentation, distribution, production, &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;Technical Breakdown+Modularization Strategy&#039;&#039;&#039;,&lt;br /&gt;
Template development Strategy &lt;br /&gt;
Decompose the target product into a set of Modules such that each module provides a &#039;&#039;&#039;Specific&#039;&#039;&#039; and &#039;&#039;&#039;independent function&#039;&#039;&#039;. Constrain any module components that create functionality with other modules(interfaces) in the template to insure module interchangeability (examples: inputs/outputs, Connectors, fasteners, Signal/language type, and all known spatial constraints.)&lt;br /&gt;
&lt;br /&gt;
Example, Seed Eco-Home&lt;br /&gt;
1: Decide wall module dimensions (because this module logically contains all other modules. Constraining dimensions will enable module interchangability after Extreme Enterprise event.)&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems.&lt;br /&gt;
4: combine these together in a CAD assembly to act as the total product template&lt;br /&gt;
5. Assign performance goals for each module&lt;br /&gt;
&lt;br /&gt;
These templates enable &#039;&#039;&#039;marketing&#039;&#039;&#039; efforts by providing a technical outline of the job. Templates also contribute to &#039;&#039;&#039;value delivery&#039;&#039;&#039; by providing performance goals that will inform designer decision making processes during the XE event.&lt;br /&gt;
&lt;br /&gt;
 Value Delivery Breakdown:&lt;br /&gt;
&lt;br /&gt;
Seed Eco-home example:&lt;br /&gt;
the house, builder training, publications, model kits, real kits, etc&lt;br /&gt;
&lt;br /&gt;
each of these provide value to OSE, The end-user, and/or the collaborator&lt;br /&gt;
&lt;br /&gt;
=Thu May 11, 2020=&lt;br /&gt;
Welcome to the Open Source Everything Store. Home of Distributed Quality Control.&lt;br /&gt;
&lt;br /&gt;
=Wed May 10, 2020=&lt;br /&gt;
==Steve Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;280&amp;quot; height=&amp;quot;160&amp;quot; src=&amp;quot;https://www.youtube.com/embed/dKLKupfI5l4&amp;quot; frameborder=&amp;quot;0&amp;quot; allow=&amp;quot;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&amp;quot; allowfullscreen&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Wouldn&#039;t work if distribution is not setup&lt;br /&gt;
*It would fail if products are not QA&#039;d&lt;br /&gt;
*Inconsistency would make it fail. Model would break&lt;br /&gt;
*Love the idea.&lt;br /&gt;
*Love the opportunity&lt;br /&gt;
*Both ego and economic are in&lt;br /&gt;
*Inventing something that never existed before.&lt;br /&gt;
*If I am building a cordless drill that is also a welder - but that would be great.&lt;br /&gt;
*We can fail if we do something that has never been done before. For the higher complexity product, we need full prize money etc.&lt;br /&gt;
*That presupposes the marketing success, viability as a product&lt;br /&gt;
*Market-based partners.&lt;br /&gt;
*Work-from-home opportunities&lt;br /&gt;
*Makers, hobbyists - intro to, semi- to advanced - to extreme enterprise workshops&lt;br /&gt;
*Biz opportunity program.&lt;br /&gt;
*Sign up and pay for event - distribution set up beforehand?&lt;br /&gt;
*Event can come up with more nuanced distribution channels.&lt;br /&gt;
*So say it&#039;s a 3D printed motor.&lt;br /&gt;
*Activate marketing to the site.&lt;br /&gt;
*Amazon store, etc.&lt;br /&gt;
*It&#039;s for both people who have distribution channels, and without distro channels.&lt;br /&gt;
*Orders come in, we distribute them out to people who were involved in the production.&lt;br /&gt;
*70% goes on to producer, 30% goes to OSE. They are not doing the marketing. They are the production effort.&lt;br /&gt;
*Education - it&#039;s not only education; but through marketplace, we educate consumers about open source.&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
This is about Enterprise in a Box - not about 3D Printed Electric Motor. Identify, find, and incentivize, and retain to show up for a 24 Hour &#039;&#039;&#039;Extreme Enterprise Event&#039;&#039;&#039;, and how do you keep them motivated. Architecture must produce product, while keeping them motivated. Product is the reward, but, if they don&#039;t last the 24th hours. Bc it is remote, there is an extra challenge over the on-site hackathon.&lt;br /&gt;
&lt;br /&gt;
#Who are they&lt;br /&gt;
#Where do we find them&lt;br /&gt;
#How do we attract them?&lt;br /&gt;
#How do we structure an event that gets results - playful vs gsd &lt;br /&gt;
&lt;br /&gt;
Assumes a short event for producing a business consisting of one product.&lt;br /&gt;
&lt;br /&gt;
Terminology: producing a business construction set. A method rather than product. Even though there is a product.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Enterprise in a Box Startup Camp&#039;&#039;&#039;. An enterprise generator.&lt;br /&gt;
&lt;br /&gt;
They are creating a kit.&lt;br /&gt;
&lt;br /&gt;
That may not address engineers, so attract them in. A more nerdy way.&lt;br /&gt;
&lt;br /&gt;
We are solving for a motivation, incentive issue. There is discrepancy between attracting and retaining them. With remote, you get extra risk of dropping out.&lt;br /&gt;
&lt;br /&gt;
It&#039;s either 12 hours + 2 hr presentation or weekend.&lt;br /&gt;
&lt;br /&gt;
Either one night or 2 day. Fri Eve to Sun evening.&lt;br /&gt;
&lt;br /&gt;
=May 6, 2020=&lt;br /&gt;
We are solving for Extreme Enterprise: &#039;&#039;&#039;how do we get people who are already in an existing business to collaborate on making better products, while being open to distributing the same enterprise to others.&#039;&#039;&#039; Prerequisite is that they must be collaborative. But more for spinning off new products/business closely related to and synergistic with, but not just their products. The new enterprise must be bigger-faster-stronger - and easier to implement - or otherwise - why bother collaborating? The assumption is that we do more with less (more product, less time required) by collaborating.&lt;br /&gt;
&lt;br /&gt;
Right now the current state is do more with less - by monopolizing industries. This is extractive and win-lose, as it is not inclusive of the environment and others.&lt;br /&gt;
&lt;br /&gt;
And the &#039;bigger-faster-stronger&#039; has several properties enabled by collaboration:&lt;br /&gt;
&lt;br /&gt;
#Reduce number of specialized parts. Part degeneracy, for interoperability - 10x value to customer&lt;br /&gt;
#Modular so we can have multipurpose functiionality&lt;br /&gt;
#&#039;&#039;&#039;Localize supply chain.&#039;&#039;&#039; Such as Made in the USA. Enable local supply chain for supply chain robustness. Local supply chain network of producers - we make partnerships&lt;br /&gt;
#Collaboration along an open source, distributive franchise route - so we guarantee &#039;free&#039; future R&amp;amp;D via collaborative effort.&lt;br /&gt;
#Stop the demise of the American Empire, while leveling the field for everyone.&lt;br /&gt;
&lt;br /&gt;
Summary: development of enterprise with stakeholders:&lt;br /&gt;
#Improves their products&lt;br /&gt;
#Starts competing businesses (free enterprise) - Distributive Enterprise&lt;br /&gt;
#Unleashes innovation towards easy meeting of needs&lt;br /&gt;
#Transforms the world toward self-determination, as people no longer struggle to make a living. This de-fuses political ponerology and post-truthism and polarization - as politics (money) is no longer so controversial.&lt;br /&gt;
&lt;br /&gt;
==Measuring Distributive Enterprise in Companies==&lt;br /&gt;
*How do you know that a business is distributive? You ask - Does a company actively document their business knowhow which enables others to learn from this knowhow? And for what reason?&lt;br /&gt;
**Ideal answer is yes, and reason is for helping others/increasing innovation knowing that we are all in it together. And of course that is part of a value proposition that improves marketing - but marketing is not the primary reason for doing it - but spreading wealth is.&lt;br /&gt;
&lt;br /&gt;
==Sample Companies==&lt;br /&gt;
*Adafruit&lt;br /&gt;
*Gigabot&lt;br /&gt;
*Farmbot&lt;br /&gt;
*PP Bazaar - Guenther&lt;br /&gt;
*Sparkfun&lt;br /&gt;
*Daniele Ingrasia Fab Lab&lt;br /&gt;
*Jens Dyvik Fab Lab&lt;br /&gt;
&lt;br /&gt;
These are all successful ones - but the question is, how do we also involve smaller ones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Prerequisite&#039;&#039;&#039; is familiarity with open source or some form of collaboration - cannot be completely new to the topic as there is too much getting on the same page. There are plenty of people who do understand open. Also, just because they are in an open source project, doesn&#039;t mean that they carry the culture - for example if the project does not vet for formal open culture (documentation and repos). Another is running some sort of business, as that vets for a basic level of market-proven value proposition, as opposed to hobby or academic only.&lt;br /&gt;
&lt;br /&gt;
The only academic exception is those academics who intend to start productive enterprise.&lt;br /&gt;
&lt;br /&gt;
=May 5, 2020=&lt;br /&gt;
Working on clarity for &amp;quot;&#039;&#039;&#039;What problem are we solving?&#039;&#039;&#039;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Yesterday I got insight into &#039;&#039;&#039;[[Extreme Enterprise]]&#039;&#039;&#039; as the last missing frontier in OSE&#039;s package. This means: Efficient development of enterprise on rapid time scale, equivalent to the the development of products with [[Extreme Manufacturing]], such as 1 day, which in turn provides financial feedback loops that allow it to scale. This is like Extreme Manufacturing, but for fully refined machines that displace the central factory in favor of the distributed microfactory.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for the 80/20 transfer - transfer from 80% wealth captured by investors, to 80% captured by producers and workers. It is only just that those who actually produce should be paid for their work. There is less conflict of interest compared to investors dictating production.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;getting people to show up&#039; voluntarily to public [[OSPD]] events such as the 24 hour [[Enterprise Sprints]]. &lt;br /&gt;
&lt;br /&gt;
We have perfected, at least in theory, and tested all of the pieces - of collaboration architecture for product development. &lt;br /&gt;
&lt;br /&gt;
We are solving for Bodies Showing Up - so that all the roles required for a development process can be fulfilled.&lt;br /&gt;
&lt;br /&gt;
But also, the collaboration architecture must be tight in that&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;&#039;&#039;Bodies Showing Up&#039;&#039;&#039;. For example, the Open Source Microfactory STEAM Camp is sparse and Completion Escape Velocity is nowhere near done.&lt;br /&gt;
&lt;br /&gt;
Solution is inviting more people, but what is the incentive for people showing up? Can it be that we invite entrepreneurs who are already into production, and want to expand their product line, AND others who are not producing who want to produce?&lt;br /&gt;
&lt;br /&gt;
Clear assumption is that open source collaboration produces better-faster-stronger results - &#039;&#039;&#039;and distributes access to them&#039;&#039;&#039;. Why are we not creating institutions that do this?&lt;br /&gt;
&lt;br /&gt;
We are solving for just that: mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
The challenge is massive social upheaval (people don&#039;t know what to do with themselves when they have freedom to think) - a condition that people can adjust to readily, but most may not be immediately ready for that. Massive social upheaval arises when consumerism (filling spiritual needs with material items) is abolished via abundance.&lt;br /&gt;
&lt;br /&gt;
We may be solving for the fundamental issue of wealth distribution, and to distribute wealth in the big picture. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039; Small businesses, which account for 99.7% of all companies, generate less than 2/3 of the U.S.’s new jobs – which means that the .03% of companies that are big create one out of every three new jobs, more than pulling their weight.&#039;&#039; - [https://www.factorfinders.com/small-business-job-creation-vs-big]&lt;br /&gt;
&lt;br /&gt;
=Apr 6, 2020=&lt;br /&gt;
&lt;br /&gt;
[[Enterprise Metrics Log]]&lt;br /&gt;
&lt;br /&gt;
=January 1, 2016=&lt;br /&gt;
Explicit pursuit of [[D3D]] as a Distributive Enterprise, along with the Brick Press - see [[Roadmap]].&lt;br /&gt;
&lt;br /&gt;
=Thu July 9, 2015=&lt;br /&gt;
Local CSA enterprise. Local CSA with open source pellet-fired microcar delivery, bread from open source bread oven, aquaponics greenhouse greens, and sprouts from open source sprout machine. Pellets from open source pelletizer. Biochar from open source pelletizer/ winter greenhouse heater. Open source combine harvests wheat. $25/hr revenue projections for Milestone 1. &lt;br /&gt;
&lt;br /&gt;
=Sat Apr 25, 2015=&lt;br /&gt;
History of OSE should be placed on timeline like in [http://www.ros.org/history/]&lt;br /&gt;
&lt;br /&gt;
=April 21, 2015=&lt;br /&gt;
With time, OSE is gaining structure and identity - like a human in development. As of April 2015, we began discussing training OSE volunteers into leadership positions. This is due to [[Jonathan Kocurek]] stepping up to Community Manager, and [[Laura Colcord]] helping directly on the Leadership Training webinar. We are finding that we need to train our people in order to enhance OSE&#039;s development efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category:Logs]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228181</id>
		<title>Enterprise Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Enterprise_Log&amp;diff=228181"/>
		<updated>2020-07-22T14:21:55Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Tues July 21, 2020=&lt;br /&gt;
{coming soon}&lt;br /&gt;
=Thu May 11, 2020=&lt;br /&gt;
Welcome to the Open Source Everything Store. Home of Distributed Quality Control.&lt;br /&gt;
&lt;br /&gt;
=Wed May 10, 2020=&lt;br /&gt;
==Steve Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;280&amp;quot; height=&amp;quot;160&amp;quot; src=&amp;quot;https://www.youtube.com/embed/dKLKupfI5l4&amp;quot; frameborder=&amp;quot;0&amp;quot; allow=&amp;quot;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&amp;quot; allowfullscreen&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Wouldn&#039;t work if distribution is not setup&lt;br /&gt;
*It would fail if products are not QA&#039;d&lt;br /&gt;
*Inconsistency would make it fail. Model would break&lt;br /&gt;
*Love the idea.&lt;br /&gt;
*Love the opportunity&lt;br /&gt;
*Both ego and economic are in&lt;br /&gt;
*Inventing something that never existed before.&lt;br /&gt;
*If I am building a cordless drill that is also a welder - but that would be great.&lt;br /&gt;
*We can fail if we do something that has never been done before. For the higher complexity product, we need full prize money etc.&lt;br /&gt;
*That presupposes the marketing success, viability as a product&lt;br /&gt;
*Market-based partners.&lt;br /&gt;
*Work-from-home opportunities&lt;br /&gt;
*Makers, hobbyists - intro to, semi- to advanced - to extreme enterprise workshops&lt;br /&gt;
*Biz opportunity program.&lt;br /&gt;
*Sign up and pay for event - distribution set up beforehand?&lt;br /&gt;
*Event can come up with more nuanced distribution channels.&lt;br /&gt;
*So say it&#039;s a 3D printed motor.&lt;br /&gt;
*Activate marketing to the site.&lt;br /&gt;
*Amazon store, etc.&lt;br /&gt;
*It&#039;s for both people who have distribution channels, and without distro channels.&lt;br /&gt;
*Orders come in, we distribute them out to people who were involved in the production.&lt;br /&gt;
*70% goes on to producer, 30% goes to OSE. They are not doing the marketing. They are the production effort.&lt;br /&gt;
*Education - it&#039;s not only education; but through marketplace, we educate consumers about open source.&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
This is about Enterprise in a Box - not about 3D Printed Electric Motor. Identify, find, and incentivize, and retain to show up for a 24 Hour &#039;&#039;&#039;Extreme Enterprise Event&#039;&#039;&#039;, and how do you keep them motivated. Architecture must produce product, while keeping them motivated. Product is the reward, but, if they don&#039;t last the 24th hours. Bc it is remote, there is an extra challenge over the on-site hackathon.&lt;br /&gt;
&lt;br /&gt;
#Who are they&lt;br /&gt;
#Where do we find them&lt;br /&gt;
#How do we attract them?&lt;br /&gt;
#How do we structure an event that gets results - playful vs gsd &lt;br /&gt;
&lt;br /&gt;
Assumes a short event for producing a business consisting of one product.&lt;br /&gt;
&lt;br /&gt;
Terminology: producing a business construction set. A method rather than product. Even though there is a product.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Enterprise in a Box Startup Camp&#039;&#039;&#039;. An enterprise generator.&lt;br /&gt;
&lt;br /&gt;
They are creating a kit.&lt;br /&gt;
&lt;br /&gt;
That may not address engineers, so attract them in. A more nerdy way.&lt;br /&gt;
&lt;br /&gt;
We are solving for a motivation, incentive issue. There is discrepancy between attracting and retaining them. With remote, you get extra risk of dropping out.&lt;br /&gt;
&lt;br /&gt;
It&#039;s either 12 hours + 2 hr presentation or weekend.&lt;br /&gt;
&lt;br /&gt;
Either one night or 2 day. Fri Eve to Sun evening.&lt;br /&gt;
&lt;br /&gt;
=May 6, 2020=&lt;br /&gt;
We are solving for Extreme Enterprise: &#039;&#039;&#039;how do we get people who are already in an existing business to collaborate on making better products, while being open to distributing the same enterprise to others.&#039;&#039;&#039; Prerequisite is that they must be collaborative. But more for spinning off new products/business closely related to and synergistic with, but not just their products. The new enterprise must be bigger-faster-stronger - and easier to implement - or otherwise - why bother collaborating? The assumption is that we do more with less (more product, less time required) by collaborating.&lt;br /&gt;
&lt;br /&gt;
Right now the current state is do more with less - by monopolizing industries. This is extractive and win-lose, as it is not inclusive of the environment and others.&lt;br /&gt;
&lt;br /&gt;
And the &#039;bigger-faster-stronger&#039; has several properties enabled by collaboration:&lt;br /&gt;
&lt;br /&gt;
#Reduce number of specialized parts. Part degeneracy, for interoperability - 10x value to customer&lt;br /&gt;
#Modular so we can have multipurpose functiionality&lt;br /&gt;
#&#039;&#039;&#039;Localize supply chain.&#039;&#039;&#039; Such as Made in the USA. Enable local supply chain for supply chain robustness. Local supply chain network of producers - we make partnerships&lt;br /&gt;
#Collaboration along an open source, distributive franchise route - so we guarantee &#039;free&#039; future R&amp;amp;D via collaborative effort.&lt;br /&gt;
#Stop the demise of the American Empire, while leveling the field for everyone.&lt;br /&gt;
&lt;br /&gt;
Summary: development of enterprise with stakeholders:&lt;br /&gt;
#Improves their products&lt;br /&gt;
#Starts competing businesses (free enterprise) - Distributive Enterprise&lt;br /&gt;
#Unleashes innovation towards easy meeting of needs&lt;br /&gt;
#Transforms the world toward self-determination, as people no longer struggle to make a living. This de-fuses political ponerology and post-truthism and polarization - as politics (money) is no longer so controversial.&lt;br /&gt;
&lt;br /&gt;
==Measuring Distributive Enterprise in Companies==&lt;br /&gt;
*How do you know that a business is distributive? You ask - Does a company actively document their business knowhow which enables others to learn from this knowhow? And for what reason?&lt;br /&gt;
**Ideal answer is yes, and reason is for helping others/increasing innovation knowing that we are all in it together. And of course that is part of a value proposition that improves marketing - but marketing is not the primary reason for doing it - but spreading wealth is.&lt;br /&gt;
&lt;br /&gt;
==Sample Companies==&lt;br /&gt;
*Adafruit&lt;br /&gt;
*Gigabot&lt;br /&gt;
*Farmbot&lt;br /&gt;
*PP Bazaar - Guenther&lt;br /&gt;
*Sparkfun&lt;br /&gt;
*Daniele Ingrasia Fab Lab&lt;br /&gt;
*Jens Dyvik Fab Lab&lt;br /&gt;
&lt;br /&gt;
These are all successful ones - but the question is, how do we also involve smaller ones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Prerequisite&#039;&#039;&#039; is familiarity with open source or some form of collaboration - cannot be completely new to the topic as there is too much getting on the same page. There are plenty of people who do understand open. Also, just because they are in an open source project, doesn&#039;t mean that they carry the culture - for example if the project does not vet for formal open culture (documentation and repos). Another is running some sort of business, as that vets for a basic level of market-proven value proposition, as opposed to hobby or academic only.&lt;br /&gt;
&lt;br /&gt;
The only academic exception is those academics who intend to start productive enterprise.&lt;br /&gt;
&lt;br /&gt;
=May 5, 2020=&lt;br /&gt;
Working on clarity for &amp;quot;&#039;&#039;&#039;What problem are we solving?&#039;&#039;&#039;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Yesterday I got insight into &#039;&#039;&#039;[[Extreme Enterprise]]&#039;&#039;&#039; as the last missing frontier in OSE&#039;s package. This means: Efficient development of enterprise on rapid time scale, equivalent to the the development of products with [[Extreme Manufacturing]], such as 1 day, which in turn provides financial feedback loops that allow it to scale. This is like Extreme Manufacturing, but for fully refined machines that displace the central factory in favor of the distributed microfactory.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for the 80/20 transfer - transfer from 80% wealth captured by investors, to 80% captured by producers and workers. It is only just that those who actually produce should be paid for their work. There is less conflict of interest compared to investors dictating production.&lt;br /&gt;
&lt;br /&gt;
We are definitely solving for mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;getting people to show up&#039; voluntarily to public [[OSPD]] events such as the 24 hour [[Enterprise Sprints]]. &lt;br /&gt;
&lt;br /&gt;
We have perfected, at least in theory, and tested all of the pieces - of collaboration architecture for product development. &lt;br /&gt;
&lt;br /&gt;
We are solving for Bodies Showing Up - so that all the roles required for a development process can be fulfilled.&lt;br /&gt;
&lt;br /&gt;
But also, the collaboration architecture must be tight in that&lt;br /&gt;
&lt;br /&gt;
We are solving for &#039;&#039;&#039;Bodies Showing Up&#039;&#039;&#039;. For example, the Open Source Microfactory STEAM Camp is sparse and Completion Escape Velocity is nowhere near done.&lt;br /&gt;
&lt;br /&gt;
Solution is inviting more people, but what is the incentive for people showing up? Can it be that we invite entrepreneurs who are already into production, and want to expand their product line, AND others who are not producing who want to produce?&lt;br /&gt;
&lt;br /&gt;
Clear assumption is that open source collaboration produces better-faster-stronger results - &#039;&#039;&#039;and distributes access to them&#039;&#039;&#039;. Why are we not creating institutions that do this?&lt;br /&gt;
&lt;br /&gt;
We are solving for just that: mass creation of regenerative livelihood.&lt;br /&gt;
&lt;br /&gt;
The challenge is massive social upheaval (people don&#039;t know what to do with themselves when they have freedom to think) - a condition that people can adjust to readily, but most may not be immediately ready for that. Massive social upheaval arises when consumerism (filling spiritual needs with material items) is abolished via abundance.&lt;br /&gt;
&lt;br /&gt;
We may be solving for the fundamental issue of wealth distribution, and to distribute wealth in the big picture. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039; Small businesses, which account for 99.7% of all companies, generate less than 2/3 of the U.S.’s new jobs – which means that the .03% of companies that are big create one out of every three new jobs, more than pulling their weight.&#039;&#039; - [https://www.factorfinders.com/small-business-job-creation-vs-big]&lt;br /&gt;
&lt;br /&gt;
=Apr 6, 2020=&lt;br /&gt;
&lt;br /&gt;
[[Enterprise Metrics Log]]&lt;br /&gt;
&lt;br /&gt;
=January 1, 2016=&lt;br /&gt;
Explicit pursuit of [[D3D]] as a Distributive Enterprise, along with the Brick Press - see [[Roadmap]].&lt;br /&gt;
&lt;br /&gt;
=Thu July 9, 2015=&lt;br /&gt;
Local CSA enterprise. Local CSA with open source pellet-fired microcar delivery, bread from open source bread oven, aquaponics greenhouse greens, and sprouts from open source sprout machine. Pellets from open source pelletizer. Biochar from open source pelletizer/ winter greenhouse heater. Open source combine harvests wheat. $25/hr revenue projections for Milestone 1. &lt;br /&gt;
&lt;br /&gt;
=Sat Apr 25, 2015=&lt;br /&gt;
History of OSE should be placed on timeline like in [http://www.ros.org/history/]&lt;br /&gt;
&lt;br /&gt;
=April 21, 2015=&lt;br /&gt;
With time, OSE is gaining structure and identity - like a human in development. As of April 2015, we began discussing training OSE volunteers into leadership positions. This is due to [[Jonathan Kocurek]] stepping up to Community Manager, and [[Laura Colcord]] helping directly on the Leadership Training webinar. We are finding that we need to train our people in order to enhance OSE&#039;s development efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category:Logs]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=228107</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=228107"/>
		<updated>2020-07-21T12:38:40Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Tues Jul 21, 2020 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=228106</id>
		<title>David Lemmer Log</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=David_Lemmer_Log&amp;diff=228106"/>
		<updated>2020-07-21T12:36:17Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Mon Jul 20, 2020 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;iframe width=&amp;quot;600&amp;quot; height=&amp;quot;400&amp;quot; src=&amp;quot;https://osedev.org/wiki/David?start=9/1/2019&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Tues Jul 21, 2020=&lt;br /&gt;
&lt;br /&gt;
I think your effort could be best spent in your area of expertise, which is the process part. The design of the house modules is best left to those who have a lot of experience in that area. &lt;br /&gt;
o, do you think I will be able to find the volume and connector information I need in the existing part libraries?&lt;br /&gt;
&lt;br /&gt;
Somewhat, yes, but it has to be interpreted from the point of a design-builder, otherwise it&#039;s not buildable easily and cheaply.&lt;br /&gt;
&lt;br /&gt;
Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;I am hoping to get  a few things out of the modular breakdown, 1) this should be a repeatable process for future projects and helps to ensure interoperability across the enterprise by constraining[standardizing] interfaces. 2) each module can be given their own set of design goals, which should be based on performance goals and the primary value function of the module; This will help to guide design teams decisions during this event and similar breakdowns do the same for future events 3) having each module broken out in this way (interface constraints + performance goals) will help to inform about what technical specialties are ideal for the design team breakdown.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My previous experience here has been that we fit the expertise to the task by understanding the technical domains required to complete the task. These domains should be traceable from performance and functional requirements. So this is actually a part of what I am trying to get from modular breakdown.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market?&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There is  quite a lot of material I&#039;ve seen in my textbooks on this topic, covering tradespace analysis, stakeholder requirements/analysis, end user requirements and more.  I will get after these topics with XE in mind, I think this will likely end up being a set of questions and processes to follow that help in answering &amp;quot;what is the primary value delivered to stakeholders?&amp;quot;, &amp;quot;what is the primary value to the market?&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
It occurs to me that I am resorting to old professional habits by e-mailing. Is there a place on the wiki where I should be performing these correspondences? &lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;One heuristic from the first SE lectures I&#039;d attended comes to mind here : &amp;quot;In SE how do we eat the elephant? One bite at a time&amp;quot;. So with a prioritization I can get after what is most relevant, for us (I think you&#039;d laid that out in the previous sentences).&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;My current perspective is that I&#039;m developing the processes that can be used to enable distributed, short time scale, product development. The ultimate product delivery must happen, but the bite I am chewing right now is the distributed scalable development process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Thoughts?&lt;br /&gt;
&lt;br /&gt;
Also, I put this on your log. Please post your thought process on your log so it&#039;s a public thing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
V/r - David&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Mon Jul 20, 2020=&lt;br /&gt;
&lt;br /&gt;
Hi Marcin,&lt;br /&gt;
&lt;br /&gt;
Seeing the task breakdown timeline I think it makes the most sense for me to shift efforts for the time being to setting up design template models in CAD for each module of the micro house for XE. My thinking is as follows: &lt;br /&gt;
1) Almost all other modules when completed will reside within the volume constrained by the wall module (with few exceptions such as the rain catching gutter and cistern)&lt;br /&gt;
2) Therefore if we can, we should create reserved volumes to represent the space occupied by the other modules; these reserved volumes shall have any connections that allow them to interface with other systems pre defined, and, these volumes should be able to be re-arranged within the wall volume. 2.1) i think the electric (PV/grid), Door, window, bathroom/kitchen , Stove, water hookups, greywater, biodigester, modules will all require portions of the design that pass through the structural modules (walls floor roof)&lt;br /&gt;
&lt;br /&gt;
Based on the above  I want to ask if we should predefine the area of the the wall module? If not, will leaving this area unconstrained still allow for module interchangeability?&lt;br /&gt;
&lt;br /&gt;
Based on the above reasoning I think the next tasks to get after will be as follows &lt;br /&gt;
1: Decide wall module dimensions&lt;br /&gt;
2: Build wall module template in CAD&lt;br /&gt;
3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems&lt;br /&gt;
4: combine these together in a CAD assembly To act as the total project template&lt;br /&gt;
&lt;br /&gt;
I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.&lt;br /&gt;
&lt;br /&gt;
Please let me know if you think this is the right way to spend my efforts. Also, do you think I will be able to find the volume and connector information I need in the existing part libraries? Or is there a better place to look?&lt;br /&gt;
&lt;br /&gt;
Also any feedback you have on the above is welcome and appreciated.&lt;br /&gt;
Does this approach make sense? &lt;br /&gt;
&lt;br /&gt;
V/r David &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MJ sez:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You are focusing on the technical detail. But the enterprise architecture is much broader than that. Role architecture is job one. Technical detail of the actual house is a small part of the actual endeavor. The first thing is to lay out the role architecture, and the house modules fall out of that. Do you think you could do something regarding the larger picture of project management - ie, what does the literature say about the overall process for Product Design and Bringing a Product To Market? We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang. We are not developing a house. We&#039;re developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. &lt;br /&gt;
Thoughts?&lt;br /&gt;
Also, I put this on your log.&lt;br /&gt;
Marcin &lt;br /&gt;
&lt;br /&gt;
=Tue Jul 14, 2020=&lt;br /&gt;
*Discussion notes - [[David Lemmer]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=OSE-Related_Podcasts&amp;diff=228085</id>
		<title>OSE-Related Podcasts</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=OSE-Related_Podcasts&amp;diff=228085"/>
		<updated>2020-07-20T22:00:54Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* By David Lemmer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Hint|Please document at &#039;&#039;Contact Emails&#039;&#039; below so we can learn on best wording.}}&lt;br /&gt;
&lt;br /&gt;
=Wed Jun 17, 2020=&lt;br /&gt;
From [[Josh Log]]:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Podcast criteria spreadsheet:&#039;&#039;&#039; https://docs.google.com/spreadsheets/d/1QUfUTpWQYDJaAyjAoc57vysUbU6XMATHcSkuKImwgl4/edit#gid=62406523&lt;br /&gt;
&lt;br /&gt;
&amp;lt;html&amp;gt;&lt;br /&gt;
&amp;lt;iframe src=&amp;quot;https://docs.google.com/spreadsheets/d/e/2PACX-1vSf9x_ekrR83GCWPKdYkaKs95MK9DyH0Gd9mr_PID5ydWLOFm7zvuf1IGtkV4DINl2ib83TVQEnmN5Q/pubhtml?gid=62406523&amp;amp;amp;single=true&amp;amp;amp;widget=true&amp;amp;amp;headers=false&amp;quot; height=400 width=900&amp;gt;&amp;lt;/iframe&amp;gt;&lt;br /&gt;
&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1QUfUTpWQYDJaAyjAoc57vysUbU6XMATHcSkuKImwgl4/edit#gid=62406523 edit]&lt;br /&gt;
&lt;br /&gt;
Podcast types:&lt;br /&gt;
&lt;br /&gt;
=Permaculture=&lt;br /&gt;
OSE is also in the permaculture space. From the [[Nut Plantout Machines]], [[Aquaponic Greenhouse]], [[Perennial Polyculture]], [[Nut Breeding]], [[Afforestt Workshop]], [[Miracle Orchard]] workshop at Factor e Farm, [[Biodigester]], [[Seed Eco-Home]], [[CEB Press]], and our work on open source farm machines, we have plenty of compelling content. Relevant presentations by Marcin include one at the [[Permaculture Voices]] Conference. Here are relevant podcasts:&lt;br /&gt;
#Paul Wheaton Podcast- known name in USA permaculture - [https://richsoil.com/permaculture/category/podcast]&lt;br /&gt;
&lt;br /&gt;
=Linux=&lt;br /&gt;
OSE uses [[OSE Linux]], an open source operating system. Advocates of open source are typically interested in open source ecology, hardware hacking, and DIY. Anyone who knows or uses Linux is likely to be our friend.&lt;br /&gt;
&lt;br /&gt;
#The Lunduke Show - [https://podcasts.apple.com/us/podcast/the-lunduke-show/id1465523928]&lt;br /&gt;
&lt;br /&gt;
=Community Economic Development=&lt;br /&gt;
OSE work is clearly related to circular economies, local community economic development, relocalization movement, [[Community Supported Agriculture]], [[Community Supported Manufacturing]], and more.&lt;br /&gt;
*Social Innovation Podcast - https://ssir.org/podcasts/category/economic_development&lt;br /&gt;
&lt;br /&gt;
=Contact Emails=&lt;br /&gt;
#[[A Sustainable Mind Podcast]]&lt;br /&gt;
&lt;br /&gt;
=Podcasts with Marcin=&lt;br /&gt;
See [[Podcast Log]]&lt;br /&gt;
&lt;br /&gt;
=Podcasts that Mention Open Source Ecology=&lt;br /&gt;
*PostScarcity.net - OSE mentioned as a realistic route to post-scarcity - [https://www.youtube.com/watch?v=uwP-Z2l7hNE]&lt;br /&gt;
&lt;br /&gt;
=Recommended=&lt;br /&gt;
*By buddhist geeks - follow up&lt;br /&gt;
==By David Lemmer==&lt;br /&gt;
Most of these aren&#039;t &amp;quot;Podcasts&amp;quot; as much as regular youtube content creators. Many of them focus on economics, movements, politics, politicians, and political culture in the US. However, all of them conduct interviews on a fairly regular basis of people who are activists, organizers, thinkers ect.&lt;br /&gt;
&lt;br /&gt;
I think OSE could resonate with their audiences and I think these are also audiences that want to actively contribute to positive change, whether that is in the form of financial support or activism/campaigning. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Status Coup&#039;&#039;&#039; - 81.6k subscribers, approximate average views per video 4,000 , total views 13.7x10^6&lt;br /&gt;
* https://www.youtube.com/channel/UC0pCsHlEEmCfxllZSlRB2Og&lt;br /&gt;
Website&lt;br /&gt;
* https://statuscoup.com/&lt;br /&gt;
For business inquiries:	StatusCoup@ProtonMail.com&lt;br /&gt;
ABOUT US&lt;br /&gt;
&amp;quot;Status Coup gives the microphone back to the people with in-the-field and investigative reporting.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ron Placone&#039;&#039;&#039; - 25.4k subscribers, approximate average views per video 1,000 , total views 2.8x10^6&lt;br /&gt;
* https://www.youtube.com/user/RonPlacone/videos&lt;br /&gt;
&lt;br /&gt;
Website &lt;br /&gt;
* https://www.ronplacone.com/&lt;br /&gt;
* https://www.ronplacone.com/contact&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Graham Elwood&#039;&#039;&#039; - 71k subscribers, approximate average views per video 2,500 , total views 7.1x10^6, &lt;br /&gt;
* https://www.youtube.com/c/GrahamElwoodOfficial/about&lt;br /&gt;
&lt;br /&gt;
Website&lt;br /&gt;
*https://www.grahamelwood.com/&lt;br /&gt;
*https://www.grahamelwood.com/#contact&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[OSE Podcast]]&lt;br /&gt;
*[[Nature Am I]]&lt;br /&gt;
*[[Center for Humane Technology Podcast]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=OSE-Related_Podcasts&amp;diff=228084</id>
		<title>OSE-Related Podcasts</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=OSE-Related_Podcasts&amp;diff=228084"/>
		<updated>2020-07-20T21:36:18Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* By David Lemmer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Hint|Please document at &#039;&#039;Contact Emails&#039;&#039; below so we can learn on best wording.}}&lt;br /&gt;
&lt;br /&gt;
=Wed Jun 17, 2020=&lt;br /&gt;
From [[Josh Log]]:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Podcast criteria spreadsheet:&#039;&#039;&#039; https://docs.google.com/spreadsheets/d/1QUfUTpWQYDJaAyjAoc57vysUbU6XMATHcSkuKImwgl4/edit#gid=62406523&lt;br /&gt;
&lt;br /&gt;
&amp;lt;html&amp;gt;&lt;br /&gt;
&amp;lt;iframe src=&amp;quot;https://docs.google.com/spreadsheets/d/e/2PACX-1vSf9x_ekrR83GCWPKdYkaKs95MK9DyH0Gd9mr_PID5ydWLOFm7zvuf1IGtkV4DINl2ib83TVQEnmN5Q/pubhtml?gid=62406523&amp;amp;amp;single=true&amp;amp;amp;widget=true&amp;amp;amp;headers=false&amp;quot; height=400 width=900&amp;gt;&amp;lt;/iframe&amp;gt;&lt;br /&gt;
&amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1QUfUTpWQYDJaAyjAoc57vysUbU6XMATHcSkuKImwgl4/edit#gid=62406523 edit]&lt;br /&gt;
&lt;br /&gt;
Podcast types:&lt;br /&gt;
&lt;br /&gt;
=Permaculture=&lt;br /&gt;
OSE is also in the permaculture space. From the [[Nut Plantout Machines]], [[Aquaponic Greenhouse]], [[Perennial Polyculture]], [[Nut Breeding]], [[Afforestt Workshop]], [[Miracle Orchard]] workshop at Factor e Farm, [[Biodigester]], [[Seed Eco-Home]], [[CEB Press]], and our work on open source farm machines, we have plenty of compelling content. Relevant presentations by Marcin include one at the [[Permaculture Voices]] Conference. Here are relevant podcasts:&lt;br /&gt;
#Paul Wheaton Podcast- known name in USA permaculture - [https://richsoil.com/permaculture/category/podcast]&lt;br /&gt;
&lt;br /&gt;
=Linux=&lt;br /&gt;
OSE uses [[OSE Linux]], an open source operating system. Advocates of open source are typically interested in open source ecology, hardware hacking, and DIY. Anyone who knows or uses Linux is likely to be our friend.&lt;br /&gt;
&lt;br /&gt;
#The Lunduke Show - [https://podcasts.apple.com/us/podcast/the-lunduke-show/id1465523928]&lt;br /&gt;
&lt;br /&gt;
=Community Economic Development=&lt;br /&gt;
OSE work is clearly related to circular economies, local community economic development, relocalization movement, [[Community Supported Agriculture]], [[Community Supported Manufacturing]], and more.&lt;br /&gt;
*Social Innovation Podcast - https://ssir.org/podcasts/category/economic_development&lt;br /&gt;
&lt;br /&gt;
=Contact Emails=&lt;br /&gt;
#[[A Sustainable Mind Podcast]]&lt;br /&gt;
&lt;br /&gt;
=Podcasts with Marcin=&lt;br /&gt;
See [[Podcast Log]]&lt;br /&gt;
&lt;br /&gt;
=Podcasts that Mention Open Source Ecology=&lt;br /&gt;
*PostScarcity.net - OSE mentioned as a realistic route to post-scarcity - [https://www.youtube.com/watch?v=uwP-Z2l7hNE]&lt;br /&gt;
&lt;br /&gt;
=Recommended=&lt;br /&gt;
*By buddhist geeks - follow up&lt;br /&gt;
==By David Lemmer==&lt;br /&gt;
Most of these aren&#039;t &amp;quot;Podcasts&amp;quot; as much as regular youtube content creators. Many of them focus on economics, movements, politics, politicians, and political culture in the US. However, all of them conduct interviews on a fairly regular basis of people who are activists, organizers, thinkers ect.&lt;br /&gt;
&lt;br /&gt;
I think OSE could resonate with their audiences and I think these are also audiences that want to actively contribute to positive change, whether that is in the form of financial support or activism/campaigning. &lt;br /&gt;
&lt;br /&gt;
Status Coup - 81.6k subscribers, approximate average views per video 4,000&lt;br /&gt;
* https://www.youtube.com/channel/UC0pCsHlEEmCfxllZSlRB2Og&lt;br /&gt;
Website&lt;br /&gt;
* https://statuscoup.com/&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[OSE Podcast]]&lt;br /&gt;
*[[Nature Am I]]&lt;br /&gt;
*[[Center for Humane Technology Podcast]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227463</id>
		<title>Extreme Enterprise Event Design</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227463"/>
		<updated>2020-07-14T00:55:14Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Internet Infrastructure=&lt;br /&gt;
*Wiki - master Dev Template for Extreme Enterprise is synthesized from [[Template:Dev]] and [[Template:Enterprise]] plus many others of [[Extreme Enterprise Task Breakdown]]. Make this palatable on the wiki by using a well-formatted template.&lt;br /&gt;
*Self-managed lightweight Scrum Board for task allocation on wiki ([[Scrumy]] used to be available, now we may want to try Google Presentation as at [[OSE_Kanban_Board#Idea_3.2C_editable_google_drawing]]&lt;br /&gt;
&lt;br /&gt;
=Role Architecture=&lt;br /&gt;
&amp;lt;html&amp;gt; &amp;lt;iframe src=&amp;quot;https://docs.google.com/presentation/d/e/2PACX-1vQ-bQNwSyvQKf3ufpRop8QPyLqdFSaERezdjfhD3iPZzs0uQqSA1H8kGf1uKaiMdrMsiIPAEob8BDXv/embed?start=false&amp;amp;loop=false&amp;amp;delayms=3000&amp;quot; frameborder=&amp;quot;0&amp;quot; width=&amp;quot;480&amp;quot; height=&amp;quot;389&amp;quot; allowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt; &amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1SRURFGytDIooffnPRnV2YD_Sjp3yKKMe0pmCvmcAqfk/edit#slide=id.g5c3be0ce2d_1_28 edit]&lt;br /&gt;
&lt;br /&gt;
=Pre-Preparation=&lt;br /&gt;
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]]&lt;br /&gt;
*High level functional requirements determined by SMEs&lt;br /&gt;
*A “definition of done“ needs to be formulated and agreed to by the SME’s performing the modular decomposition. &lt;br /&gt;
*This will help to focus goals and prevent design creep in this planning phase. &lt;br /&gt;
*The definition of done for this phase should be a general outline that describes the essential goals the SME’s must achieve to build the design template requirements/constraints.&lt;br /&gt;
*The following questions and steps being completed could be the “definition of done”, but this is a flexible item and should be tailored to the needs of the particular design event.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Functional units determined through modular decomposition &lt;br /&gt;
**SMEs will answer generalized and product specific questions. The following questions are a good starting point.&lt;br /&gt;
***Disclaimer: These questions are not law, they are meant to steer design planning/thinking in a coherent direction. When they are insufficient, they should be added to. When they are ill fitting they should not be used. As better questions are identified they should add to or replace the following.&lt;br /&gt;
**What are the sub-units the total product can be broken into such that each maintain a &#039;&#039;&#039;&#039;&#039;specific and independent function&#039;&#039;&#039;&#039;&#039;?&lt;br /&gt;
*** for a simple example, a hand drill might decompose into the following modules : motor module, power storage/delivery module, driver/chuck and bit module, and a handle module. Each of the above has a function of it&#039;s own, however, only when combined together do we see the emergent behavior of a handheld drill.&lt;br /&gt;
**Does OSE GVCS have a design that will interface with this product(or module of the product) in the product ecology map?&lt;br /&gt;
***If yes, what are the interfaces and performance requirements that will maintain product ecology?&lt;br /&gt;
***If no, What are important considerations for how this module will interface with the rest of the system? How much volume can a design occupy? What inputs does it receive? What outputs does it produce? What is the format of these outputs? How well do those outputs generalize across the range of possible recipients?&lt;br /&gt;
**Does a design pattern exist for the product to be developed? &lt;br /&gt;
***If yes, Does the product to be developed replace, modify, or parallel the existing design? &lt;br /&gt;
***If it is to parallel the existing design what are the functional/interface differences that necessitate the redesign? &lt;br /&gt;
****If there are no clear answers to this question consider using the existing pattern instead of redesigning&lt;br /&gt;
***If it is to replace the existing design evaluation should be performed that the new products design requirements fulfill all roles of the design pattern being replaced.&lt;br /&gt;
&lt;br /&gt;
*Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development&lt;br /&gt;
*How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable [[Product Ecologies]]&lt;br /&gt;
*Pattern Diagrams/languages developed for Wiki to track and integrate the products developed&lt;br /&gt;
&lt;br /&gt;
*Metrics also need to be developed and collected once the event goes live to determine how successful the event was. &lt;br /&gt;
*Appropriate metrics can inform on what if anything went wrong. Knowing this enables future XE planning groups to adjust design templates, swarming strategies, and so on to make the events even better! &lt;br /&gt;
**How should we measure collaboration?&lt;br /&gt;
**What is success with respect to XE? &lt;br /&gt;
**How effective were collaborative efforts in group?&lt;br /&gt;
**How well do the designs of different teams swap?e.g. Were the interfacing and design constraints effective at making modules interchangeable?&lt;br /&gt;
**Consider a simple follow up questionnaire for people who signed up but didn&#039;t show&lt;br /&gt;
&lt;br /&gt;
*After the product has been decomposed into module templates consisting of constraints and performance requirements derived from how the module will interface with other product modules the SMEs need to describe the technical backgrounds needed to complete the design. These backgrounds will be the basis for design team make-up during the XE event.&lt;br /&gt;
*The workflow of the design process also needs to be considered such that organizational/management skill sets necessary to keep efforts organized can be baked into the team composition.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Goal:&#039;&#039;&#039; Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for  each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.&lt;br /&gt;
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.&lt;br /&gt;
*Internet search through [[Open Source Hardware Journals]] for contributors&lt;br /&gt;
*Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.&lt;br /&gt;
*Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as [[ArchDaily]] and searching for open source.  EV, Electronics, Power Electronics, ESC, Hacker channels. [[Electric Vehicle Forums]]. [[Electronics Forums]]. [[Electronics YouTube Channels]] - for publicity and collaboration. [[Maker and DIY YouTube Channels]]. [[Hacker Forums]]. [[Hacker Platforms]]. [[Arduino Forums]]. [[3D Printing Forums]]. [[Maker and DIY Forums]]. [[Electrical Engineering Forums]]. [[2000 Fab Labs]]. [[2000 Hackerspaces and Makerspaces]]. [[OSE-Related Podcasts]] - has an example of evaluation points on the [[5-Legged Dog]]. [[OSE Related Facebook Groups]]. [[OSE-Related Reddit Groups]]. [[OSE-Related Linked-In Groups]]. [[OSE-Related Youtube Channels]]. [[OSE-Related Email Lists]]. [[Social Enterprise Channels]]. The above should be done across [[OSE Keywords]].&lt;br /&gt;
*Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, [[SZOIL]], [[GOSH]], [[Open Electonics]], [[GrabCad]], [[HeroX]], etc.&lt;br /&gt;
*Contact all crowd development sites/&lt;br /&gt;
&lt;br /&gt;
=Before=&lt;br /&gt;
#Reach out to candidates with a short, inspiring intro email. See if they are &#039;interested&#039;.&lt;br /&gt;
#Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing [[Media Kits]]&lt;br /&gt;
#For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only &#039;interested&#039; in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=During=&lt;br /&gt;
#Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.&lt;br /&gt;
#Do video, such as Kickstarter and other promos&lt;br /&gt;
#Crowdfund&lt;br /&gt;
#Have a 24-7 access video room.&lt;br /&gt;
#Have ancillary lessons on content from SMEs.&lt;br /&gt;
#Publish website for MOOC on the content&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=After=&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#All assets generated on design and enterprise are open source&lt;br /&gt;
#Anything can be edited mercilessly by anyone, with due respect.&lt;br /&gt;
#Some assets belong to OSE.&lt;br /&gt;
#We do escrow account for funding disbursement - if we don&#039;t get enough presales, we simply give it back. In a conditional sale, this is not an issue.&lt;br /&gt;
#Whoever creates something can start a business, but they must publish all assets.&lt;br /&gt;
#ALL assets are published on the wiki&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227449</id>
		<title>Extreme Enterprise Event Design</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227449"/>
		<updated>2020-07-13T23:57:13Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Internet Infrastructure=&lt;br /&gt;
*Wiki - master Dev Template for Extreme Enterprise is synthesized from [[Template:Dev]] and [[Template:Enterprise]] plus many others of [[Extreme Enterprise Task Breakdown]]. Make this palatable on the wiki by using a well-formatted template.&lt;br /&gt;
*Self-managed lightweight Scrum Board for task allocation on wiki ([[Scrumy]] used to be available, now we may want to try Google Presentation as at [[OSE_Kanban_Board#Idea_3.2C_editable_google_drawing]]&lt;br /&gt;
&lt;br /&gt;
=Role Architecture=&lt;br /&gt;
&amp;lt;html&amp;gt; &amp;lt;iframe src=&amp;quot;https://docs.google.com/presentation/d/e/2PACX-1vQ-bQNwSyvQKf3ufpRop8QPyLqdFSaERezdjfhD3iPZzs0uQqSA1H8kGf1uKaiMdrMsiIPAEob8BDXv/embed?start=false&amp;amp;loop=false&amp;amp;delayms=3000&amp;quot; frameborder=&amp;quot;0&amp;quot; width=&amp;quot;480&amp;quot; height=&amp;quot;389&amp;quot; allowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt; &amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1SRURFGytDIooffnPRnV2YD_Sjp3yKKMe0pmCvmcAqfk/edit#slide=id.g5c3be0ce2d_1_28 edit]&lt;br /&gt;
&lt;br /&gt;
=Pre-Preparation=&lt;br /&gt;
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]]&lt;br /&gt;
*High level functional requirements determined by SMEs&lt;br /&gt;
*A “definition of done“ needs to be formulated and agreed to by the SME’s performing the modular decomposition. &lt;br /&gt;
*This will help to focus goals and prevent design creep in this planning phase. &lt;br /&gt;
*The definition of done for this phase should be a general outline that describes the essential goals the SME’s must achieve to build the design template requirements/constraints.&lt;br /&gt;
*The following questions and steps being completed could be the “definition of done”, but this is a flexible item and should be tailored to the needs of the particular design event.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Functional units determined through modular decomposition &lt;br /&gt;
**SMEs will answer generalized and product specific questions. The following questions are a good starting point.&lt;br /&gt;
***Disclaimer: These questions are not law, they are meant to steer design planning/thinking in a coherent direction. When they are insufficient, they should be added to. When they are ill fitting they should not be used. As better questions are identified they should add to a replace the following.&lt;br /&gt;
**What are the sub-units the total product can be broken into such that each maintain a &#039;&#039;&#039;&#039;&#039;specific and independent function&#039;&#039;&#039;&#039;&#039;?&lt;br /&gt;
*** for a simple example, a hand drill might decompose into the following modules : motor module, power storage/delivery module, driver/chuck and bit module, and a handle module. Each of the above has a function of it&#039;s own, however, only when combined together do we see the emergent behavior of a handheld drill.&lt;br /&gt;
**Does OSE GVCS have a design that will interface with this product(or module of the product) in the product ecology map?&lt;br /&gt;
***If yes, what are the interfaces and performance requirements that will maintain product ecology?&lt;br /&gt;
***If no, What are important considerations for how this module will interface with the rest of the system? How much volume can a design occupy? What inputs does it receive? What outputs does it produce? What is the format of these outputs? How well do those outputs generalize across the range of possible recipients?&lt;br /&gt;
**Does a design pattern exist for the product to be developed? &lt;br /&gt;
***If yes, Does the product to be developed replace, modify, or parallel the existing design? &lt;br /&gt;
***If it is to parallel the existing design what are the functional/interface differences that necessitate the redesign? &lt;br /&gt;
****If there are no clear answers to this question consider using the existing pattern instead of redesigning&lt;br /&gt;
***If it is to replace the existing design evaluation should be performed that the new products design requirements fulfill all roles of the design pattern being replaced.&lt;br /&gt;
&lt;br /&gt;
*Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development&lt;br /&gt;
*How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable [[Product Ecologies]]&lt;br /&gt;
*Pattern Diagrams/languages developed for Wiki to track and integrate the products developed&lt;br /&gt;
&lt;br /&gt;
*Metrics also need to be developed and collected once the event goes live to determine how successful the event was. &lt;br /&gt;
*Appropriate metrics can inform on what if anything went wrong. Knowing this enables future XE planning groups to adjust design templates, swarming strategies, and so on to make the events even better! &lt;br /&gt;
**How should we measure collaboration?&lt;br /&gt;
**What is success with respect to XE? &lt;br /&gt;
**How effective were collaborative efforts in group?&lt;br /&gt;
**How well do the designs of different teams swap?e.g. Were the interfacing and design constraints effective at making modules interchangeable?&lt;br /&gt;
**Consider a simple follow up questionnaire for people who signed up but didn&#039;t show&lt;br /&gt;
&lt;br /&gt;
*After the product has been decomposed into module templates consisting of constraints and performance requirements derived from how the module will interface with other product modules the SMEs need to describe the technical backgrounds needed to complete the design. These backgrounds will be the basis for design team make-up during the XE event.&lt;br /&gt;
*The workflow of the design process also needs to be considered such that organizational/management skill sets necessary to keep efforts organized can be baked into the team composition.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Goal:&#039;&#039;&#039; Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for  each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.&lt;br /&gt;
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.&lt;br /&gt;
*Internet search through [[Open Source Hardware Journals]] for contributors&lt;br /&gt;
*Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.&lt;br /&gt;
*Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as [[ArchDaily]] and searching for open source.  EV, Electronics, Power Electronics, ESC, Hacker channels. [[Electric Vehicle Forums]]. [[Electronics Forums]]. [[Electronics YouTube Channels]] - for publicity and collaboration. [[Maker and DIY YouTube Channels]]. [[Hacker Forums]]. [[Hacker Platforms]]. [[Arduino Forums]]. [[3D Printing Forums]]. [[Maker and DIY Forums]]. [[Electrical Engineering Forums]]. [[2000 Fab Labs]]. [[2000 Hackerspaces and Makerspaces]]. [[OSE-Related Podcasts]] - has an example of evaluation points on the [[5-Legged Dog]]. [[OSE Related Facebook Groups]]. [[OSE-Related Reddit Groups]]. [[OSE-Related Linked-In Groups]]. [[OSE-Related Youtube Channels]]. [[OSE-Related Email Lists]]. [[Social Enterprise Channels]]. The above should be done across [[OSE Keywords]].&lt;br /&gt;
*Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, [[SZOIL]], [[GOSH]], [[Open Electonics]], [[GrabCad]], [[HeroX]], etc.&lt;br /&gt;
*Contact all crowd development sites/&lt;br /&gt;
&lt;br /&gt;
=Before=&lt;br /&gt;
#Reach out to candidates with a short, inspiring intro email. See if they are &#039;interested&#039;.&lt;br /&gt;
#Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing [[Media Kits]]&lt;br /&gt;
#For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only &#039;interested&#039; in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=During=&lt;br /&gt;
#Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.&lt;br /&gt;
#Do video, such as Kickstarter and other promos&lt;br /&gt;
#Crowdfund&lt;br /&gt;
#Have a 24-7 access video room.&lt;br /&gt;
#Have ancillary lessons on content from SMEs.&lt;br /&gt;
#Publish website for MOOC on the content&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=After=&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#All assets generated on design and enterprise are open source&lt;br /&gt;
#Anything can be edited mercilessly by anyone, with due respect.&lt;br /&gt;
#Some assets belong to OSE.&lt;br /&gt;
#We do escrow account for funding disbursement - if we don&#039;t get enough presales, we simply give it back. In a conditional sale, this is not an issue.&lt;br /&gt;
#Whoever creates something can start a business, but they must publish all assets.&lt;br /&gt;
#ALL assets are published on the wiki&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227448</id>
		<title>Extreme Enterprise Event Design</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227448"/>
		<updated>2020-07-13T23:43:25Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Internet Infrastructure=&lt;br /&gt;
*Wiki - master Dev Template for Extreme Enterprise is synthesized from [[Template:Dev]] and [[Template:Enterprise]] plus many others of [[Extreme Enterprise Task Breakdown]]. Make this palatable on the wiki by using a well-formatted template.&lt;br /&gt;
*Self-managed lightweight Scrum Board for task allocation on wiki ([[Scrumy]] used to be available, now we may want to try Google Presentation as at [[OSE_Kanban_Board#Idea_3.2C_editable_google_drawing]]&lt;br /&gt;
&lt;br /&gt;
=Role Architecture=&lt;br /&gt;
&amp;lt;html&amp;gt; &amp;lt;iframe src=&amp;quot;https://docs.google.com/presentation/d/e/2PACX-1vQ-bQNwSyvQKf3ufpRop8QPyLqdFSaERezdjfhD3iPZzs0uQqSA1H8kGf1uKaiMdrMsiIPAEob8BDXv/embed?start=false&amp;amp;loop=false&amp;amp;delayms=3000&amp;quot; frameborder=&amp;quot;0&amp;quot; width=&amp;quot;480&amp;quot; height=&amp;quot;389&amp;quot; allowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt; &amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1SRURFGytDIooffnPRnV2YD_Sjp3yKKMe0pmCvmcAqfk/edit#slide=id.g5c3be0ce2d_1_28 edit]&lt;br /&gt;
&lt;br /&gt;
=Pre-Preparation=&lt;br /&gt;
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]]&lt;br /&gt;
*High level functional requirements determined by SMEs&lt;br /&gt;
*A “definition of done“ needs to be formulated and agreed to by the SME’s performing the modular decomposition. &lt;br /&gt;
*This will help to focus goals and prevent design creep in this planning phase. &lt;br /&gt;
*The definition of done for this phase should be a general outline that describes the essential goals the SME’s must achieve to build the design template requirements/constraints.&lt;br /&gt;
*The following questions and steps being completed could be the “definition of done”, but this is a flexible item and should be tailored to the needs of the particular design event.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Functional units determined through modular decomposition &lt;br /&gt;
**SMEs will answer generalized and product specific questions. The following questions are a good starting point.&lt;br /&gt;
***Disclaimer: These questions are not law, they are meant to steer design planning/thinking in a coherent direction. When they are insufficient, they should be added to. When they are ill fitting they should not be used. As better questions are identified they should add to a replace the following.&lt;br /&gt;
**What are the sub-units the total product can be broken into such that each maintain a &#039;&#039;&#039;&#039;&#039;specific and independent function&#039;&#039;&#039;&#039;&#039;?&lt;br /&gt;
*** for a simple example, a hand drill might decompose into the following modules : motor module, power storage/delivery module, driver/chuck and bit module, and a handle module. Each of the above has a function of it&#039;s own, however, only when combined together do we see the emergent behavior of a handheld drill.&lt;br /&gt;
**Does OSE GVCS have a design that will interface with this product(or module of the product) in the product ecology map?&lt;br /&gt;
***If yes, what are the interfaces and performance requirements that will maintain product ecology?&lt;br /&gt;
***If no, What are important considerations for how this module will interface with the rest of the system? How much volume can a design occupy? What inputs does it receive? What outputs does it produce? What is the format of these outputs? How well do those outputs generalize across the range of possible recipients?&lt;br /&gt;
**Does a design pattern exist for the product to be developed? &lt;br /&gt;
***If yes, Does the product to be developed replace, modify, or parallel the existing design? &lt;br /&gt;
***If it is to parallel the existing design what are the functional/interface differences that necessitate the redesign? &lt;br /&gt;
****If there are no clear answers to this question consider using the existing pattern instead of redesigning&lt;br /&gt;
***If it is to replace the existing design evaluation should be performed that the new products design requirements fulfill all roles of the design pattern being replaced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development&lt;br /&gt;
*How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable [[Product Ecologies]]&lt;br /&gt;
*Pattern Diagrams/languages developed for Wiki to track and integrate the products developed&lt;br /&gt;
* &#039;&#039;&#039;Goal:&#039;&#039;&#039; Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for  each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.&lt;br /&gt;
*After the product has been decomposed into module templates consisting of constraints and performance requirements derived from how the module will interface with other product modules the SMEs need to describe the technical backgrounds needed to complete the design. These backgrounds will be the basis for design team make-up during the XE event.&lt;br /&gt;
*The workflow of the design process also needs to be considered such that organizational/management skill sets necessary to keep efforts organized can be baked into the team composition.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.&lt;br /&gt;
*Internet search through [[Open Source Hardware Journals]] for contributors&lt;br /&gt;
*Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.&lt;br /&gt;
*Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as [[ArchDaily]] and searching for open source.  EV, Electronics, Power Electronics, ESC, Hacker channels. [[Electric Vehicle Forums]]. [[Electronics Forums]]. [[Electronics YouTube Channels]] - for publicity and collaboration. [[Maker and DIY YouTube Channels]]. [[Hacker Forums]]. [[Hacker Platforms]]. [[Arduino Forums]]. [[3D Printing Forums]]. [[Maker and DIY Forums]]. [[Electrical Engineering Forums]]. [[2000 Fab Labs]]. [[2000 Hackerspaces and Makerspaces]]. [[OSE-Related Podcasts]] - has an example of evaluation points on the [[5-Legged Dog]]. [[OSE Related Facebook Groups]]. [[OSE-Related Reddit Groups]]. [[OSE-Related Linked-In Groups]]. [[OSE-Related Youtube Channels]]. [[OSE-Related Email Lists]]. [[Social Enterprise Channels]]. The above should be done across [[OSE Keywords]].&lt;br /&gt;
*Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, [[SZOIL]], [[GOSH]], [[Open Electonics]], [[GrabCad]], [[HeroX]], etc.&lt;br /&gt;
*Contact all crowd development sites/&lt;br /&gt;
&lt;br /&gt;
=Before=&lt;br /&gt;
#Reach out to candidates with a short, inspiring intro email. See if they are &#039;interested&#039;.&lt;br /&gt;
#Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing [[Media Kits]]&lt;br /&gt;
#For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only &#039;interested&#039; in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=During=&lt;br /&gt;
#Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.&lt;br /&gt;
#Do video, such as Kickstarter and other promos&lt;br /&gt;
#Crowdfund&lt;br /&gt;
#Have a 24-7 access video room.&lt;br /&gt;
#Have ancillary lessons on content from SMEs.&lt;br /&gt;
#Publish website for MOOC on the content&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=After=&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#All assets generated on design and enterprise are open source&lt;br /&gt;
#Anything can be edited mercilessly by anyone, with due respect.&lt;br /&gt;
#Some assets belong to OSE.&lt;br /&gt;
#We do escrow account for funding disbursement - if we don&#039;t get enough presales, we simply give it back. In a conditional sale, this is not an issue.&lt;br /&gt;
#Whoever creates something can start a business, but they must publish all assets.&lt;br /&gt;
#ALL assets are published on the wiki&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227447</id>
		<title>Extreme Enterprise Event Design</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227447"/>
		<updated>2020-07-13T23:36:21Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Pre-Preparation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Internet Infrastructure=&lt;br /&gt;
*Wiki - master Dev Template for Extreme Enterprise is synthesized from [[Template:Dev]] and [[Template:Enterprise]] plus many others of [[Extreme Enterprise Task Breakdown]]. Make this palatable on the wiki by using a well-formatted template.&lt;br /&gt;
*Self-managed lightweight Scrum Board for task allocation on wiki ([[Scrumy]] used to be available, now we may want to try Google Presentation as at [[OSE_Kanban_Board#Idea_3.2C_editable_google_drawing]]&lt;br /&gt;
&lt;br /&gt;
=Role Architecture=&lt;br /&gt;
&amp;lt;html&amp;gt; &amp;lt;iframe src=&amp;quot;https://docs.google.com/presentation/d/e/2PACX-1vQ-bQNwSyvQKf3ufpRop8QPyLqdFSaERezdjfhD3iPZzs0uQqSA1H8kGf1uKaiMdrMsiIPAEob8BDXv/embed?start=false&amp;amp;loop=false&amp;amp;delayms=3000&amp;quot; frameborder=&amp;quot;0&amp;quot; width=&amp;quot;480&amp;quot; height=&amp;quot;389&amp;quot; allowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt; &amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1SRURFGytDIooffnPRnV2YD_Sjp3yKKMe0pmCvmcAqfk/edit#slide=id.g5c3be0ce2d_1_28 edit]&lt;br /&gt;
&lt;br /&gt;
=Pre-Preparation=&lt;br /&gt;
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]]&lt;br /&gt;
*High level functional requirements determined by SMEs&lt;br /&gt;
*A “definition of done“ needs to be formulated and agreed to by the SME’s performing the modular decomposition. &lt;br /&gt;
*This will help to focus goals and prevent design creep in this planning phase. &lt;br /&gt;
*The definition of done for this phase should be a general outline that describes the essential goals the SME’s must achieve to build the design template requirements/constraints.&lt;br /&gt;
*The following questions and steps being completed could be the “definition of done”, but this is a flexible item and should be tailored to the needs of the particular design event.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Functional units determined through modular decomposition &lt;br /&gt;
**SMEs will answer generalized and product specific questions. The following questions are a good starting point.&lt;br /&gt;
***Disclaimer: These questions are not law, they are meant to steer design planning/thinking in a coherent direction. When they are insufficient, they should be added to. When they are ill fitting they should not be used. As better questions are identified they should add to a replace the following.&lt;br /&gt;
**What are the sub-units the total product can be broken into such that each maintain a &#039;&#039;&#039;&#039;&#039;specific and independent function&#039;&#039;&#039;&#039;&#039;?&lt;br /&gt;
*** for a simple example, a hand drill might decompose into the following modules : motor module, power storage/delivery module, driver/chuck and bit module, and a handle module. Each of the above has a function of it&#039;s own, however, only when combined together do we see the emergent behavior of a handheld drill.&lt;br /&gt;
**Does OSE GVCS have a design that will interface with this product(or module of the product) in the product ecology map?&lt;br /&gt;
***If yes, what are the interfaces and performance requirements that will maintain product ecology?&lt;br /&gt;
***If no, What are important considerations for how this module will interface with the rest of the system? How much volume can a design occupy? What inputs does it receive? What outputs does it produce? What is the format of these outputs? How well do those outputs generalize across the range of possible recipients?&lt;br /&gt;
&lt;br /&gt;
**Does a design pattern exist for the product to be developed? &lt;br /&gt;
***If yes, Does the product to be developed replace, modify, or parallel the existing design? &lt;br /&gt;
***If it is to parallel the existing design what are the functional/interface differences that necessitate the redesign? &lt;br /&gt;
****If there are no clear answers to this question consider using the existing pattern instead of redesigning&lt;br /&gt;
***If it is to replace the existing design evaluation should be performed that the new products design requirements fulfill all roles of the design pattern being replaced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development&lt;br /&gt;
*How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable [[Product Ecologies]]&lt;br /&gt;
*Pattern Diagrams/languages developed for Wiki to track and integrate the products developed&lt;br /&gt;
* &#039;&#039;&#039;Goal:&#039;&#039;&#039; Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for  each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.&lt;br /&gt;
*After the product has been decomposed into module templates consisting of constraints and performance requirements derived from how the module will interface with other product modules the SMEs need to describe the technical backgrounds needed to complete the design. These backgrounds will be the basis for design team make-up during the XE event.&lt;br /&gt;
*The workflow of the design process also needs to be considered such that organizational/management skill sets necessary to keep efforts organized can be baked into the team composition.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.&lt;br /&gt;
*Internet search through [[Open Source Hardware Journals]] for contributors&lt;br /&gt;
*Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.&lt;br /&gt;
*Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as [[ArchDaily]] and searching for open source.  EV, Electronics, Power Electronics, ESC, Hacker channels. [[Electric Vehicle Forums]]. [[Electronics Forums]]. [[Electronics YouTube Channels]] - for publicity and collaboration. [[Maker and DIY YouTube Channels]]. [[Hacker Forums]]. [[Hacker Platforms]]. [[Arduino Forums]]. [[3D Printing Forums]]. [[Maker and DIY Forums]]. [[Electrical Engineering Forums]]. [[2000 Fab Labs]]. [[2000 Hackerspaces and Makerspaces]]. [[OSE-Related Podcasts]] - has an example of evaluation points on the [[5-Legged Dog]]. [[OSE Related Facebook Groups]]. [[OSE-Related Reddit Groups]]. [[OSE-Related Linked-In Groups]]. [[OSE-Related Youtube Channels]]. [[OSE-Related Email Lists]]. [[Social Enterprise Channels]]. The above should be done across [[OSE Keywords]].&lt;br /&gt;
*Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, [[SZOIL]], [[GOSH]], [[Open Electonics]], [[GrabCad]], [[HeroX]], etc.&lt;br /&gt;
*Contact all crowd development sites/&lt;br /&gt;
&lt;br /&gt;
=Before=&lt;br /&gt;
#Reach out to candidates with a short, inspiring intro email. See if they are &#039;interested&#039;.&lt;br /&gt;
#Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing [[Media Kits]]&lt;br /&gt;
#For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only &#039;interested&#039; in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=During=&lt;br /&gt;
#Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.&lt;br /&gt;
#Do video, such as Kickstarter and other promos&lt;br /&gt;
#Crowdfund&lt;br /&gt;
#Have a 24-7 access video room.&lt;br /&gt;
#Have ancillary lessons on content from SMEs.&lt;br /&gt;
#Publish website for MOOC on the content&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=After=&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#All assets generated on design and enterprise are open source&lt;br /&gt;
#Anything can be edited mercilessly by anyone, with due respect.&lt;br /&gt;
#Some assets belong to OSE.&lt;br /&gt;
#We do escrow account for funding disbursement - if we don&#039;t get enough presales, we simply give it back. In a conditional sale, this is not an issue.&lt;br /&gt;
#Whoever creates something can start a business, but they must publish all assets.&lt;br /&gt;
#ALL assets are published on the wiki&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227011</id>
		<title>Extreme Enterprise Event Design</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Event_Design&amp;diff=227011"/>
		<updated>2020-07-06T01:52:26Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: /* Pre-Preparation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Internet Infrastructure=&lt;br /&gt;
*Wiki - master Dev Template for Extreme Enterprise is synthesized from [[Template:Dev]] and [[Template:Enterprise]] plus many others of [[Extreme Enterprise Task Breakdown]]. Make this palatable on the wiki by using a well-formatted template.&lt;br /&gt;
*Self-managed lightweight Scrum Board for task allocation on wiki ([[Scrumy]] used to be available, now we may want to try Google Presentation as at [[OSE_Kanban_Board#Idea_3.2C_editable_google_drawing]]&lt;br /&gt;
&lt;br /&gt;
=Role Architecture=&lt;br /&gt;
&amp;lt;html&amp;gt; &amp;lt;iframe src=&amp;quot;https://docs.google.com/presentation/d/e/2PACX-1vQ-bQNwSyvQKf3ufpRop8QPyLqdFSaERezdjfhD3iPZzs0uQqSA1H8kGf1uKaiMdrMsiIPAEob8BDXv/embed?start=false&amp;amp;loop=false&amp;amp;delayms=3000&amp;quot; frameborder=&amp;quot;0&amp;quot; width=&amp;quot;480&amp;quot; height=&amp;quot;389&amp;quot; allowfullscreen=&amp;quot;true&amp;quot; mozallowfullscreen=&amp;quot;true&amp;quot; webkitallowfullscreen=&amp;quot;true&amp;quot;&amp;gt;&amp;lt;/iframe&amp;gt; &amp;lt;/html&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1SRURFGytDIooffnPRnV2YD_Sjp3yKKMe0pmCvmcAqfk/edit#slide=id.g5c3be0ce2d_1_28 edit]&lt;br /&gt;
&lt;br /&gt;
=Pre-Preparation=&lt;br /&gt;
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]]&lt;br /&gt;
*High level functional requirements determined by SMEs&lt;br /&gt;
*Functional units determined through modular decomposition [Modular decomposition strategies to be added soon]&lt;br /&gt;
*Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development&lt;br /&gt;
*How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable [[Product Ecologies]]&lt;br /&gt;
*Pattern Diagrams/languages developed for Wiki to track and integrate the products developed&lt;br /&gt;
* &#039;&#039;&#039;Goal:&#039;&#039;&#039; Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for  each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.&lt;br /&gt;
&lt;br /&gt;
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.&lt;br /&gt;
*Internet search through [[Open Source Hardware Journals]] for contributors&lt;br /&gt;
*Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.&lt;br /&gt;
*Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as [[ArchDaily]] and searching for open source.  EV, Electronics, Power Electronics, ESC, Hacker channels. [[Electric Vehicle Forums]]. [[Electronics Forums]]. [[Electronics YouTube Channels]] - for publicity and collaboration. [[Maker and DIY YouTube Channels]]. [[Hacker Forums]]. [[Hacker Platforms]]. [[Arduino Forums]]. [[3D Printing Forums]]. [[Maker and DIY Forums]]. [[Electrical Engineering Forums]]. [[2000 Fab Labs]]. [[2000 Hackerspaces and Makerspaces]]. [[OSE-Related Podcasts]] - has an example of evaluation points on the [[5-Legged Dog]]. [[OSE Related Facebook Groups]]. [[OSE-Related Reddit Groups]]. [[OSE-Related Linked-In Groups]]. [[OSE-Related Youtube Channels]]. [[OSE-Related Email Lists]]. [[Social Enterprise Channels]]. The above should be done across [[OSE Keywords]].&lt;br /&gt;
*Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, [[SZOIL]], [[GOSH]], [[Open Electonics]], [[GrabCad]], [[HeroX]], etc.&lt;br /&gt;
*Contact all crowd development sites/&lt;br /&gt;
&lt;br /&gt;
=Before=&lt;br /&gt;
#Reach out to candidates with a short, inspiring intro email. See if they are &#039;interested&#039;.&lt;br /&gt;
#Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing [[Media Kits]]&lt;br /&gt;
#For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only &#039;interested&#039; in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=During=&lt;br /&gt;
#Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.&lt;br /&gt;
#Do video, such as Kickstarter and other promos&lt;br /&gt;
#Crowdfund&lt;br /&gt;
#Have a 24-7 access video room.&lt;br /&gt;
#Have ancillary lessons on content from SMEs.&lt;br /&gt;
#Publish website for MOOC on the content&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=After=&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#All assets generated on design and enterprise are open source&lt;br /&gt;
#Anything can be edited mercilessly by anyone, with due respect.&lt;br /&gt;
#Some assets belong to OSE.&lt;br /&gt;
#We do escrow account for funding disbursement - if we don&#039;t get enough presales, we simply give it back. In a conditional sale, this is not an issue.&lt;br /&gt;
#Whoever creates something can start a business, but they must publish all assets.&lt;br /&gt;
#ALL assets are published on the wiki&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=User:David_Lemmer&amp;diff=226936</id>
		<title>User:David Lemmer</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=User:David_Lemmer&amp;diff=226936"/>
		<updated>2020-07-05T05:15:03Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: spelling correction&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I am have a 4 year degree in biomedical engineering - instrumentation focus&lt;br /&gt;
Relevant skills associated with this degree:&lt;br /&gt;
 Understanding of basic circuits and electronics. Capable of reading, designing and implementing circuits using the fundamental principle of Ohms law. Familiarity with free circuit CAD software PSPICE (not Open). Familiar and comfortable with basic calculations involving AC power.Familiar and comfortable with basic circuit components, e.g. resistors, capacitors, inductors, sources, semiconductor elements, and transformers. Shaky familiarity with FET, Integrated Circuits,Electromagnetic physics, and Motors.&lt;br /&gt;
&lt;br /&gt;
Basic academic understanding of mechanics. Familiar and comfortable with 2D mechanical diagrams/problems and the fundamental theorems that are used to solve them e.g. equilibrium equations, forces, moments reaction forces, center of mass, and inertia. Familiar and comfortable with basic dynamic mechanic calculations, F=ma, Momentum.&lt;br /&gt;
&lt;br /&gt;
Basic academic understanding of material properties e.g Ceramcis, metalics and polymers.&lt;br /&gt;
&lt;br /&gt;
Moderately proficient with proprietary CAD software, SolidWorks. I Am interested in developing skills and familiarity in Open Source CAD software.&lt;br /&gt;
&lt;br /&gt;
Moderately Proficient with Proprietary programming software : MATLAB. Very rudimentary skills with Python.&lt;br /&gt;
&lt;br /&gt;
Moderately proficient and familiar with ImageJ, Open Source Scientific imaging program. &lt;br /&gt;
&lt;br /&gt;
Moderate understanding of human anatomy and physiology. &lt;br /&gt;
&lt;br /&gt;
Moderate understanding of biological sciences.&lt;br /&gt;
&lt;br /&gt;
I am pursuing a graduate education in systems engineering with a focus on Model Based Systems Engineering.&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Task_Breakdown&amp;diff=226935</id>
		<title>Extreme Enterprise Task Breakdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Extreme_Enterprise_Task_Breakdown&amp;diff=226935"/>
		<updated>2020-07-05T03:38:58Z</updated>

		<summary type="html">&lt;p&gt;David Lemmer: spelling correction&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=About=&lt;br /&gt;
The event develops assets beforehand, for active developemnt, but it also seeds future development- as always, it is only the beginning&lt;br /&gt;
&lt;br /&gt;
80+% Efficient Electrice Motor ? - from appliances to cars&lt;br /&gt;
&lt;br /&gt;
$130B market&lt;br /&gt;
&lt;br /&gt;
Pushing limits of collaborative development.&lt;br /&gt;
&lt;br /&gt;
=Governance=&lt;br /&gt;
#Open Source contract and education. License of event.&lt;br /&gt;
#Distributive Enterprise Contract and Education - &lt;br /&gt;
#Open Collaboration - education on that with Eugene Kim&lt;br /&gt;
#Free Enterprise - business models that do not rely on scarcity&lt;br /&gt;
#Code of Conduct&lt;br /&gt;
#Website - all of our banners/logos for collaborators&lt;br /&gt;
#Crappy Intro Video with distilled message&lt;br /&gt;
#Partnership - with Adam Savage of Red Bull or the like - a high profile personality, preferably in the marketing world such as Vishan Lakhiani or Tony Robbins&lt;br /&gt;
&lt;br /&gt;
=Breakdown Tasks and Comlexity Management=&lt;br /&gt;
The key to rapid velocity in hardware development is experience - and especially experience in prototyping. To add experience, we need to do excessive prototyping. We need to seed as much of the known as possible. This includes:&lt;br /&gt;
#Detailed [[SEBD]] - systems engineering for performance, enterprise, lifecycle, and [[OSE Spec]] integration. [[SEBD]] applies to the technology itself, but since we are developing an enterprise, we need a detailed generic SEBD that includes the enterprise level up to the point of sale in the framework of a distributed enterprise.&lt;br /&gt;
#[[Tech Tree of Choices]] for each component&lt;br /&gt;
#[[Rapid Prototyping Breakdown]] - details of [[TDD]] prototypes that can be started immediately for small partial tests that combined to the finished product.&lt;br /&gt;
#[[Test Driven Design Breakdown]] - a detailed list of specifications to test for - such as heating, power, speed, weight, and other quantities related to [[Calculations]] that can be tested and data-collected. This list can be started immediately upon start of Extreme Enterprise events - with data points collected rigorously throughout.&lt;br /&gt;
#[[Admissible Part List]] - we agree on the components that we are allowed to use - and we put them into FreeCAD as part libraries. 2 deliverables:&lt;br /&gt;
##FreeCAD part library of admissible parts&lt;br /&gt;
##BOM spreadsheet for the [[Approved Vendor List]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Summary&#039;&#039;&#039;: One of the top challenges is prototyping, which would be done from the onset of the XE (Extreme Enterprise) event. Learn from the [[Open_Source_Hardware_Trap]]. And solution for the cost of prototyping is to fund it for the Extreme Enterprise event: [[Rapid_Prototyping_Breakdown]]&lt;br /&gt;
&lt;br /&gt;
=Tech Tasks=&lt;br /&gt;
#&#039;&#039;&#039;FreeCAD Part Library&#039;&#039;&#039; - customizer&lt;br /&gt;
#&#039;&#039;&#039;FreeCAD Part Library&#039;&#039;&#039; - workbench&lt;br /&gt;
#&#039;&#039;&#039;Coil Winding Jig&#039;&#039;&#039; - design&lt;br /&gt;
#&#039;&#039;&#039;3D Printed Bearing Team&#039;&#039;&#039;&#039; - design&lt;br /&gt;
#&#039;&#039;&#039;Air Bearing Version - Design&#039;&#039;&#039; - for high speed applications&lt;br /&gt;
#&#039;&#039;&#039;Scalability Strategy and Design&#039;&#039;&#039; - works closely with Modularity analysis and design&lt;br /&gt;
#&#039;&#039;&#039;Materials Strategy&#039;&#039;&#039; - exploring different material versions&lt;br /&gt;
#&#039;&#039;&#039;Under water version of motor&#039;&#039;&#039;&lt;br /&gt;
#Software - firmware for pulses&lt;br /&gt;
#Feedback - LED or Hall Effect Sensor&lt;br /&gt;
#App - RPM and power measurement app, design EM Simulator Design&#039;&#039;&#039;&lt;br /&gt;
#Students - research Industry Standards&lt;br /&gt;
#Gamers - do a conceptual design of motor in Minecraft?&lt;br /&gt;
#CAD designers - do the design&lt;br /&gt;
#3D printers - do the build&lt;br /&gt;
#Wind turbine people - Kostas&lt;br /&gt;
#Electric generator people - develop the generator side of the motor&lt;br /&gt;
#STEM curriculum writers - Electricity lesson&lt;br /&gt;
#FreeCAD, Blender, OpenSCAD, , LibreCad, KiCad, [[QUCS]], OpenFOAM,  communities - draftspeople&lt;br /&gt;
#[[QElectro Tech]] - open source electric design&lt;br /&gt;
#Also - list all other software projects that may be relevant to this.&lt;br /&gt;
#Sparkfun - kit product interest?&lt;br /&gt;
#Adafruit - kit interest?&lt;br /&gt;
#List all open source technology projects&lt;br /&gt;
#Requirements + Value Proposition	&lt;br /&gt;
#Conceptual Design	&lt;br /&gt;
#Module Breakdown	&lt;br /&gt;
#3D CAD - 12 parts breakdown&lt;br /&gt;
#Calculations - control speed for Arduino&lt;br /&gt;
#Embedded Arduino Design	&lt;br /&gt;
#Electronics Design&lt;br /&gt;
#Wiring and Plumbing	&lt;br /&gt;
#Software	&lt;br /&gt;
#BOM - admissible parts&lt;br /&gt;
#vBOM	&lt;br /&gt;
#CAM Files	&lt;br /&gt;
#Cut List	&lt;br /&gt;
#Build Instructions&lt;br /&gt;
#Fabrication Drawings	&lt;br /&gt;
#Exploded Part Diagram	&lt;br /&gt;
#Production Engineering	&lt;br /&gt;
#Build Pictures and Video	&lt;br /&gt;
#Data Collection	&lt;br /&gt;
#Future Work&lt;br /&gt;
&lt;br /&gt;
=Product Strategy=&lt;br /&gt;
#Course - on a MOOC site - the last word on Electric Motor Rapid Learning. Protocol: research, get names, distill, productize with Video Team.&lt;br /&gt;
#Education Curriculum - for schools&lt;br /&gt;
#Kit - for revenue, onto your website&lt;br /&gt;
#Extreme Event at the End - we build the thing in metal, we  build the thing in plastic, etc.&lt;br /&gt;
#Funding goes to outsource the prototyping of this&lt;br /&gt;
#Revenue from webinars - free access to participants, paid access for outsiders&lt;br /&gt;
&lt;br /&gt;
=Education=&lt;br /&gt;
Throughout the event, there is an ongoing schedule number of presentations by subject matter experts who provide focused information related to problems at hand. This is free for participants, and can be monetized for non-participants. Given proper incentive structure - this attracts people to the learning aspect. This can provide the rapid-learning aspect that is necessary for building [[Integrated Humans]].&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039;FreeCAD Path Workbench&#039;&#039;&#039;&lt;br /&gt;
#&#039;&#039;&#039;FreeCAD FEA&#039;&#039;&#039; - structural deflection.&lt;br /&gt;
#&#039;&#039;&#039;Design Webinar&#039;&#039;&#039; - about motor design - the best video in the world on all motors by a great teacher or teacher set&lt;br /&gt;
#&#039;&#039;&#039;Edu Animations&#039;&#039;&#039; - team of 12 in Blender - specific to Axial Flux - exploring Geometries from Columbia paper&lt;br /&gt;
#&#039;&#039;&#039;Treatment and Script&#039;&#039;&#039; - everything we need to know about motors&lt;br /&gt;
#&#039;&#039;&#039;Learning Site&#039;&#039;&#039; - forums or other venue&lt;br /&gt;
#&#039;&#039;&#039;Arduino Programming&#039;&#039;&#039;&lt;br /&gt;
#&#039;&#039;&#039;How It Works&#039;&#039;&#039; - distilled Animations - Blender - for explaining this&lt;br /&gt;
#&#039;&#039;&#039;PNP Machine for Distributed Production of Arduino Megas&#039;&#039;&#039;&lt;br /&gt;
#&#039;&#039;&#039;PNP Machine for Distributed Production of Beagle Bones&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Website=&lt;br /&gt;
#Product Site - everything about motor&lt;br /&gt;
#Extreme Enterprise site - everything about how to do an Extreme Enterprise event&lt;br /&gt;
&lt;br /&gt;
=QC=&lt;br /&gt;
#CE certification, UL certification. FCC etc&lt;br /&gt;
#[[DQC]] procedures&lt;br /&gt;
#Certification&lt;br /&gt;
#Approval by certifying agencies, such as NIH COVID list. Find these all over the world.&lt;br /&gt;
#Open Source Licensing of tech under OSE umbrella - agreement for duties and prvileges is spelled out explicitly - what you are expected to do&lt;br /&gt;
&lt;br /&gt;
=Supply Chain / BOM=&lt;br /&gt;
#BOM basic parts&lt;br /&gt;
#MOQ 100 BOM&lt;br /&gt;
#MOQ 1000 BOM&lt;br /&gt;
#Technical recursion - selecting one product to open-source&lt;br /&gt;
#Partnership with magnet supplier or copper wire supplier&lt;br /&gt;
&lt;br /&gt;
=Marketing=&lt;br /&gt;
#[[List of All Electric Motor-related Sites]] worldwide. Includes electric cars, e-bikes, &lt;br /&gt;
#[[List of All Maker Webites and Locations Worldwide]] with Quality Control&lt;br /&gt;
#[[List of All Community Economic Development Websites and Locations]]&lt;br /&gt;
#Invitation of All People with Prior Art&lt;br /&gt;
&lt;br /&gt;
=Fundraising=&lt;br /&gt;
#Kickstarter Campaign - delivers capital for development. Participation in event is one reward&lt;br /&gt;
#HeroX campaign - campaign manager. Campaign assets generation.&lt;br /&gt;
#Marketing assets - diagrams, infographics&lt;br /&gt;
#Leader Board - top contributors get rewarded, 100 awards totaling $10k&lt;br /&gt;
#Corporate sponsor to put an enterprise in hands of all job-development Community Development Organizations&lt;br /&gt;
#Corporate Sponsorship Strategy for funding an entrepreneur in every city.&lt;br /&gt;
#Posting on all [[Crowdfunding]] platforms to generate added interest.&lt;br /&gt;
&lt;br /&gt;
=Business/Marketing/Funding Roles=&lt;br /&gt;
#Fundraising - , like Red Bull proposal. Resource Developmnent - involving resource developers to pitch this as an enterprise within their community&lt;br /&gt;
#New Economy - community economic development, alternative business models, open source economy, circular economy.Economists - business models, new business models&lt;br /&gt;
#Electric motor business - someone in the field who could propose value&lt;br /&gt;
#Kit product - for education&lt;br /&gt;
#Industrial product - for  real work&lt;br /&gt;
#Distribution &lt;br /&gt;
#PR - Ben&lt;br /&gt;
#Video production&lt;br /&gt;
#Special effects&lt;br /&gt;
#Legal - license and usage contract&lt;br /&gt;
#Unique Value Proposition&lt;br /&gt;
#Business Plan	&lt;br /&gt;
#Open Source Franchise	&lt;br /&gt;
#Training and Management	&lt;br /&gt;
#Facility Design	&lt;br /&gt;
#Supply Chain Development	&lt;br /&gt;
#Production	&lt;br /&gt;
#Quality Control	&lt;br /&gt;
#Product Marketing Assets&lt;br /&gt;
#Marketing Strategy	&lt;br /&gt;
#Marketing Plan	&lt;br /&gt;
#Product Webpage&lt;br /&gt;
#Sales Strategy	&lt;br /&gt;
#Customer Support	&lt;br /&gt;
#Shipping	&lt;br /&gt;
#Open Source Everything Store	&lt;br /&gt;
#Marketing and Sales Data	&lt;br /&gt;
#Customer Feedback	&lt;br /&gt;
#Continuing Improvement	&lt;br /&gt;
#Future Work&lt;br /&gt;
#Logo - for Extreme Enterprise and for Universal Motor Construction Set&lt;br /&gt;
#Branding and byline&lt;br /&gt;
&lt;br /&gt;
=Production Engineering=&lt;br /&gt;
PE includes improving the open source machines involved, and designing specific production engineering for these machines. For this, we source capable machines, improve them. Needs a 24 person team for each machine, for 5 machines: CNC circuit mill, PNP machine, 3D printer, coil winder. Contingency plan: if these tasks are not specified enough, we reduce to high performance 3DP, CNC mill, coil winder only, no PNP.&lt;br /&gt;
&lt;br /&gt;
#This means: 4 teams of 24 people to design machines&lt;br /&gt;
#4 teams of 12 people to develop specific production engineering - toolpaths, software mods, etc.&lt;br /&gt;
&lt;br /&gt;
=Distribution=&lt;br /&gt;
#Website- website itself; Kickstarter rewards; &lt;br /&gt;
#Contract purchase - presale by schools - for $99&lt;br /&gt;
#In-game purchases of real product&lt;br /&gt;
#Game - where you build the engine and operate it to see how much torque it has.&lt;br /&gt;
#Collaborating with existing STEM companies to add to their product line&lt;br /&gt;
#Distribution on Amazon - Amazon Store Assets&lt;br /&gt;
#Etsy Store Assets&lt;br /&gt;
#Crowd Supply distribution&lt;br /&gt;
#Kickstarter Distribution - we ship you a boatload of materials&lt;br /&gt;
&lt;br /&gt;
=Shipping=&lt;br /&gt;
#Inventory Control - platform&lt;br /&gt;
#Packaging&lt;br /&gt;
#Labeling&lt;br /&gt;
#Approved Shipping Company List&lt;br /&gt;
&lt;br /&gt;
=Documentation/Marketing/Graphics/Concepts=&lt;br /&gt;
#Graphics designer - product brochure&lt;br /&gt;
#Logo design - brand logo registered by OSE. Or public domain registry.&lt;br /&gt;
#Copywriter - &lt;br /&gt;
#30 second video&lt;br /&gt;
#1 minute product video&lt;br /&gt;
#Infographic&lt;br /&gt;
#Website&lt;br /&gt;
#Buy Basket&lt;br /&gt;
#Distribution - Spakfun, Adafruit, etc&lt;br /&gt;
&lt;br /&gt;
=Video/Media/Social Media=&lt;br /&gt;
#Realtime video produced at the same time - with collaborative video protocol. Documentary on the event, with video footage. Remote video protocol for uplaods is explicit. To participate - write a protocol for how you collaborate.&lt;br /&gt;
#Music composition - compose music about this&lt;br /&gt;
#Realtime social media campaign&lt;br /&gt;
#&#039;&#039;&#039;Video Product&#039;&#039;&#039; - on post-scarcity economics and business models. Interview with MJ, Doughnut Economics, Others.&lt;br /&gt;
&lt;br /&gt;
=Community Building/HR=&lt;br /&gt;
#Finding a person in each major population center - coupling an entrepreneur and funder and community economic development organization., Fin&lt;br /&gt;
#Community Economic Dev org - find a person, provide a workspace, find a funder in the local community - do it.&lt;br /&gt;
#Incentive Element - prize given to the best startup entrepreneur? $1k reward or such&lt;br /&gt;
#STEM nonprofits - funnel this to their email lists. Get people to participate.&lt;br /&gt;
#Community Manager&lt;br /&gt;
#Map of all contributors&lt;br /&gt;
&lt;br /&gt;
=Links=&lt;br /&gt;
*[[Extreme Enterprise]]&lt;br /&gt;
*[[Extreme Enterprise Event Planning]]&lt;/div&gt;</summary>
		<author><name>David Lemmer</name></author>
	</entry>
</feed>