Short range Wide field of view Extremely agile Electronically steered Photonic EmitteR (SWEEPER) | Apply Online

SWEEPER (DARPA BAA 09-66) - Frequently Asked Questions (FAQs)

1) What is the SWEEPER opportunity?

SWEEPER stands for Short range Wide field of view Extremely agile Electronically steered Photonic EmitteR. It was a DARPA Microsystems Technology Office (MTO) Broad Agency Announcement (BAA 09-66) focused on advancing active optical beam steering and sensing by moving away from bulky opto-mechanical steering (for example, moving mirrors and gimbals) toward chip-scale integrated photonics.

2) What problem was DARPA trying to solve with SWEEPER?

The program targeted the limitations of traditional optical steering approaches, which are often constrained by mechanical motion, slower response times, and size/weight/power (SWaP) burdens. SWEEPER aimed to enable a step-change in how quickly and flexibly an optical system can point and shape its beam, while staying compatible with SWaP-constrained deployed platforms.

3) What technical approach did SWEEPER emphasize?

The core approach was integrated photonic coherent beamforming using photonic integrated circuits (PICs). In practical terms, this means building chip-scale photonic emitters that can steer optical beams electronically (rather than physically moving components), enabling faster and potentially more robust steering architectures.

4) What does "electronically steered photonic emitter" mean in this context?

It refers to an optical emitter whose beam direction (and potentially beam shape) can be controlled electronically through integrated photonic structures, instead of using opto-mechanical mechanisms or conventional electro-optic steering systems that may be larger or slower.

5) What were the key performance themes mentioned for SWEEPER?

The synopsis emphasized extremely agile beam steering at video frame rate speeds, wide field of view, and short-range operational relevance. Another highlighted target was the ability to generate multiple simultaneous beams with a combined output power on the order of 10 watts.

6) Did SWEEPER focus on single-beam steering or multi-beam operation?

The description explicitly highlighted multi-beam operation as a notable goal, referencing the ability to generate multiple simultaneous beams with combined output power around 10 watts. This suggests interest in more than just a single low-power steered beam.

7) What was notable about the "10 watts" figure mentioned?

The synopsis pointed to multiple simultaneous beams with combined output power on the order of 10 watts. That is notable because it implies meaningful power levels (not just low-power demonstrations) while still using an integrated photonics approach and maintaining agile steering behavior.

8) What kinds of applications did SWEEPER imply?

The solicitation framed the effort as enabling a paradigm shift for active optical sensing and emission. It implied applications where rapid pointing, scanning, and/or multi-direction illumination matter, and where traditional gimbals or moving parts limit speed, robustness, or SWaP. The synopsis tied this to practical defense-relevant platforms.

9) Which DARPA office ran this BAA?

SWEEPER was associated with DARPA's Microsystems Technology Office (MTO).

10) What is the BAA number for this opportunity?

The opportunity was issued under DARPA BAA 09-66.

11) What type of federal funding opportunity was this?

It was described as a discretionary federal R&D funding opportunity under CFDA 12.910 (Research and Technology Development).

12) What award instruments were mentioned as possible under this opportunity?

The announcement indicated multiple possible award instruments, including cooperative agreements, grants, other transactions/arrangements (as applicable in DARPA contexts), and procurement contracts. This signaled flexibility in how DARPA could structure awards depending on the work and the performer relationship.

13) Who was eligible to apply?

Eligibility was listed as unrestricted, meaning it was broadly open to qualified entities. The synopsis referenced typical categories such as industry, universities, nonprofits, and (where permitted) federally funded research and development centers, subject to any conditions in the full BAA.

14) Were award minimums or maximums specified in the synopsis?

The listing showed award floor and ceiling values as 0. This typically indicates the public synopsis did not specify explicit minimum or maximum award amounts in the summary fields, and that details would be handled in the full solicitation and DARPA selection decisions.

15) When was the opportunity originally posted?

The synopsis states it was originally posted on June 24, 2009.

16) What were the abstract and proposal due dates?

The submission process evolved through amendments, and the synopsis reflects shifting due dates over time. The later schedule information included an abstract due date listed as August 21, 2009 and a first-round proposal due date listed as December 11, 2009.

17) Was the BAA later closed?

Yes. Amendment 05 formally closed the BAA effective May 28, 2010, and the archive date listed was May 30, 2010.

18) Where were applicants directed for full details and instructions?

The synopsis referenced the full DARPA BAA 09-66 document for complete instructions, requirements, and technical scope. It also pointed to the MTO solicitations page for additional context.

19) How were administrative questions handled, and what email was provided?

Administrative questions were directed to DARPA via darpa_baa_09_66@darpa.mil.

20) Was a point of contact named for access issues?

Yes. The synopsis named Michael Haney as Program Manager/BAA Coordinator and referenced him in connection with access issues.