1. Purpose of the gate
A system is built from technology the team does not fully control: standard chips and modules on a supplier's roadmap, perhaps a custom chip still to be designed, power and cooling that must fit a given size, and software and security technology that must be ready when the system ships. TR1 asks, before development is committed, whether that technology can meet the system's targets on the system's schedule.
The review does not require every answer to be known. It requires each dependency to be named, assessed and either shown feasible or carried as a gap with a plan to close it. A system committed on technology that turns out to be unavailable or immature is the costliest kind of late surprise, because the board, enclosure and software are all built around it.
The criteria are: key chips and modules available, or on a credible roadmap, for the targets and the schedule; the power, thermal and size budget shown feasible by analysis; the software and security technology assessed, with gaps planned; and open technology risks tracked. The gating work product is the technology feasibility assessment, at final maturity, produced by system architecture and partitioning from the market requirements.
11 more sections for registered members.