11:08
EM.411 System Engineering Eric Rebentisch meeting
Transition to manufacturing
Tom Toner
Concept to launch process typically 3-5 years
Integrated Development Teams
Project organization structure
Design for X strategies
Design for manufacturing, sourcing, etc
Keeping head count minimal seems relevant to this problem
As with all organizational problems
Mythical man month
Designers should be the integrators
As opposed to the partners / suppliers handling any integration
System engineering vs supply chain management
Seems to be an extension of Product development process
Or he says sticking to pdp is the best bet
IP risk
Ideally, you outsource the high IP risk equipment and processes less
key role for the system engineer to make these decisions
What percent of your effort was for protecting IP?
collapsed:: true
For new tech, maybe 5%, up to 10%
Possible government could have a role in this
Is there some way to remove the need for companies to worry about protecting IP ?
Seems like this would require a strong intellectual property conception from government
At first right, this seems difficult and perhaps unproductive
Maybe some new social conception of property
Society owns everything?
Aren’t patents supposed to manage this? Why are they insufficient?
Maybe a new type of patent that is lower barrier but offers some protection
An org defines what they are doing, and has some gradually expiring right to make money of anyone doing something similar
This could even be cumulative
Every new tech and process builds off of this history of IP and divided up revenue into a tree of technology history
Kind of like sampling songs that sample other songs
Everyone in the chains gets a piece of the pie
Interesting idea, give it a name
There should be a global graph of organizational processes and technologies
Every organization publishes their technologies and processes and references other technologies and processes
Revenue should flow up this tree of references, with some expiring function
This should take care of IP risk
Government may need to provide some processes for free
Andy Grove INTEL
Only the paranoid survive
The decisions here are similar to how software companies integrate as well
eg
White box vs black box sdks
Seems like everything needs to have a clear interface to lubricants this transition
Atomicizing to
protect IP risk,
simplify sourcing,
make redundant sourcing possible
Simplify integration
Teaching this detached from a specific context feels hard to really digest
Good that Tom Toner is presenting from his experience, at least