How to Scope Optical Work for a Defense SBIR or STTR
A defense SBIR or STTR optical work package should connect the solicitation objective to measurable optical requirements, a phase-appropriate hypothesis, prioritized risks, bounded tasks, decision milestones, defined deliverables, and a verification method. Phase I should retire a critical uncertainty; Phase II should produce controlled prototype evidence that supports transition evaluation.
Why this decision matters
This choice affects more than nominal optical performance. It changes package volume, tolerance sensitivity, supplier options, alignment effort, calibration, test equipment, production yield, and the evidence required before release. The correct answer therefore comes from the complete operating condition and acceptance method, not from a single catalog value.
Key engineering decisions
- Translate the end-user need into an image, signal, pointing, range, spectral, environmental, or packaging measure.
- Select the smallest analysis or experiment that can resolve the highest-consequence feasibility question within the phase.
- Define the transition recipient, system interfaces, and evidence they will need before choosing a prototype architecture.
- Separate the optical workstream from proposal administration, commercialization, security, contracting, and compliance responsibilities.
These decisions should be captured in a requirement or trade study before the team commits long-lead components. Where requirements conflict, rank the product priorities explicitly so optimization does not hide a business decision.
Specification checklist
- Agency component, topic number, objective, and stated deliverables
- Program phase, period of performance, budget boundary, and review dates
- Optical performance measure and representative operating condition
- Current technology baseline, assumptions, unknowns, and critical risks
- Model, breadboard, prototype, report, and transition-package outputs
Every value should state the condition where it applies and how it will be measured. A specification without a defined test condition is not yet an acceptance requirement.
Common failure mode
The plan lists sophisticated optical activities but never states which solicitation uncertainty each task resolves, what evidence closes the milestone, or how the demonstrated configuration connects to the intended platform and transition customer.
The practical remedy is to compare the nominal model, tolerance prediction, mechanical interfaces, and measured configuration together. Treating the symptom as an isolated lens or component problem often produces another build with the same system-level limitation.
Verification approach
Create an objective-to-evidence matrix. For every task, record the input configuration, method, predicted result, success threshold, uncertainty, delivered artifact, residual risk, and decision enabled for the next phase.
Record the hardware revision, source or scene, wavelength, aperture, field point, focus or alignment state, environmental condition, processing, and measurement uncertainty. This makes the result useful for design iteration and supplier transfer rather than only for a one-time demonstration.
What to send PAO
Send a public or non-sensitive topic reference, program phase, optical objective, current evidence, highest-risk assumption, desired role for PAO, proposal deadline or period of performance, and required deliverables. Do not send classified or controlled data through the website.
Primary references
PAO applies this framework through defense SBIR/STTR optical engineering, from requirements and architecture through detailed design, prototype evidence, and manufacturing transfer.