David Lemmer Log: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 25: Line 25:


V/r David  
V/r David  
'''
 
MJ sez:'''
'''MJ sez:'''
 
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're developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. 
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're developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former. 
Thoughts?
Thoughts?
Also, I put this on your log.
Also, I put this on your log.
Marcin 
Marcin 


=Tue Jul 14, 2020=
=Tue Jul 14, 2020=
*Discussion notes - [[David Lemmer]]
*Discussion notes - [[David Lemmer]]

Revision as of 02:25, 21 July 2020

Mon Jul 20, 2020

Hi Marcin,

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: 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) 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)

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?

Based on the above reasoning I think the next tasks to get after will be as follows 1: Decide wall module dimensions 2: Build wall module template in CAD 3: Build other module templates in CAD that will define volume constraints and include all connectors that will allow interoperability with other systems 4: combine these together in a CAD assembly To act as the total project template

I think having this model would be a great tool for explaining the concept and also as something to approach crowdfunders with.

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?

Also any feedback you have on the above is welcome and appreciated. Does this approach make sense?

V/r David

MJ sez:

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're developing an enterprise that delivers the house to customers. Those are 2 very different things. The latter includes the former.  Thoughts? Also, I put this on your log. Marcin 

Tue Jul 14, 2020