1. Purpose of the gate
A sensor opportunity is accepted and a team is funded to define what the sensor must measure, for which applications and at what cost.
This gate commits only to definition, not to development. Its job is to stop weak opportunities early and to give strong ones a clear charter: which applications the sensor is for, which kind of sensing it involves, what the business expects in broad terms, and what the requirements stage must produce before more money is spent.
For sensors, the gate should also confirm that the opportunity is understood physically as well as commercially. A request for a smaller microphone, a more stable motion sensor or a new gas sensing capability can mean a new transduction principle or process, with a much longer path than an update of an existing family. Reviewers judge whether the team understands which it is.
Reviewers should also look at what the requirements stage itself will cost and how long it will take. A sensor whose customers cannot yet describe their environment, or whose principle has never been built on an available platform, needs a longer and better resourced definition, and saying so at this gate avoids a rushed baseline later.
10 more sections for registered members.