You are right about the teams. I was told that each "line" has multiple teams (concept, hardware design, early integration, bench testing, software, etc) and before a product is released, they have already put in at least a year or two on it's successor. In other words, once the hardware design people finished their design on the 7D2, they would start working on the 7D3 hardware design, despite the 7D2 still being a couple years from release.....dilbert said:Orangutan said:dilbert said:A test unit comes very late in the piece - that's what is shipped off to "the select few." At that point it is a done deal.
I think we're using our terminology differently: when a new component is developed it's probably first bench-tested. Then it's put in whatever current body will accept it to see how it does in the real-world. To me that's a test unit. A prototype, to me, is a test unit that is mostly new components, and uses existing components only where new components are not yet available. The "select few" would receive prototypes, not early test units. Maybe this industry has different terminology. My basic point is that R&D occurs continuously, so you can't really say that the next gen product was cancelled unless significant movement toward production had occurred.
I don't know about that. I more or less get the distinct impression that there are "teams" that are responsible for products. e.g there is a "5D team" or a "1DX team" or a "xxD team." Thus the spacing in terms of time and serialization of product releases. So when the 5D team finishes working on the 5DIII and it becomes ready for productization, they start work on the 5DIV (which is also to say that the 5DV planning has likely already started.) Components such as the CPU and sensor would likely come into the cycle from independent sources.
Upvote
0