DARPA-PS-26-126_RAAPTR_Attachment_H_Task_Description_Document.docx

DARPA-PS-26-126: RAAPTR

Instructions:

Please fill in the blue instructional text to the best of your ability. Once complete, change the blue text to black and delete the instructional text. Do not modify any other part of the document.

Delete these instructions before signing.

ATTACHMENT H

TASK DESCRIPTION DOCUMENT

FOR

(INSERT PERFORMER’S RESEARCH AND DEVELOPMENT TITLE AND ACRONYM)

BY

(INSERT PERFORMER NAME AND ADDRESS)

DATE

1. Program Background The RAAPTR program seeks to develop RF system architectures that exploit an optical timing backbone that generates and maintains low phase noise and timing deviation in form factors and ruggedness traceable to compact mobile defense platforms. The program will also study the utility of additional optical device functionality such as time transfer and high-bandwidth data movement based on proposer-identified use cases. The program will rapidly develop the required componentry and system architectures necessary to take advantage of the optical timing backbone, culminating in an on-platform demonstration.

At the component level, the program aims to demonstrate photonic microwave oscillators with:

· Phase noise < -120 dBc/Hz at 100 Hz offset (referenced for a 10 GHz carrier),

· Phase noise < -150 dBc/Hz at 10 kHz offset (referenced for a 10 GHz carrier),

· Relative timing error < 1 picosecond for 1–100 second intervals, and

· Volume < 300 cc.

At the system architecture level, RAAPTR aims to demonstrate not only the optical components necessary for such a backbone, but also the ancillary analog-RF and digital-RF capacity sufficient to maintain the performance provided by optics throughout the system architecture. Optical technologies disrupt separate assumptions at the heart of RF system design, from individual devices, through system topology, to the nature of signal processing, and so the RF system architectures themselves must be developed in tandem with the component-level development to determine a path for future transition. Key objectives at the architecture level include:

· Maintaining oscillator performance within 3 dB across a full analog-RF transceiver chain composed of ancillary components necessary to enable a proposer-defined use case,

· Developing the digital signal processing architectures and algorithm methods necessary to translate oscillator performance to relevant scenarios for mission partner transition, and

· Maintain performance under temperature variation -40 to 85 °C and 7.7 grms vibration, providing a path to endow the most constraining of tactical platforms with advanced RF capabilities.

2. Project Overview

This section is focused on defining the specific project and should include a description that aligns with the technical proposal. Though not mean to be extensive (usually two to three paragraphs will suffice), it should capture: (1) what is the project about; (2) why it matters; (3) goals and objectives; (4) Government and performer defined metrics.

3. Technical Tasks & Deliverables

This section must clearly and accurately identify the technical tasks associated with the proposed effort, organized by Phase. Task must be delineated by Phase, and deliverables clearly tied to each task. Avoid copying and pasting charts or images in this section—only textual descriptions should be included.

For each defined task and any applicable subtasks, provide:

· Objective – A concise statement of the task’s purpose or intended outcome.

· Approach – A detailed explanation of the methods, tools, and processes to be employed to accomplish the task or subtask.

· Deliverable or Milestone – A measurable output, demonstration, or event that signifies completion or achievement of the task.

Include details on deliverable format and specific content within this section rather than in the Milestone Plan Document.

Note: Not all tasks require subtasks. Include as many subtasks as applicable. Do not include proprietary or sensitive information in this section.

Example: Build a rowboat that floats.

Task: [Detailed approach to accomplish Task 1.] Subtask 1.A: [Description of subtask] Subtask 1.B: [Description of subtask] Subtask 1.C: [Description of subtask]

Example: Build a rowboat that floats.

Task: [Detailed approach to accomplish Task 2.] Subtask 2.A: [Description of subtask] Subtask 2.B: [Description of subtask] Subtask 2.C: [Description of subtask]

Example: Build a rowboat that floats.

Task: [Detailed approach to accomplish Task 3.] Subtask 3.A: [Description of subtask] Subtask 3.B: [Description of subtask] Subtask 3.C: [Description of subtask]

Insert as applicable

4. Program Management

This section must describe how the proposed effort will be effectively managed across all phases of execution. Include all applicable program management activities that support the success of the technical effort. At a minimum, address the following: program oversight and coordination, communication with the government, subcontractor or partner management, schedule and cost control, reporting requirements (e.g. status updates, technical and financial reports) risk and issue management.

5. Meeting & Travel Requirements

This Section can be utilized for any required meeting and travel requirements from the Program Solicitation.

6. Government Furnished Information (GFI)/Government Furnished Property (GFP)

This Section can be utilized to capture any assumptions regarding GFI/GFP. Anything contained here would need to be reconciled with the GFP Article in the final Agreement. See section E of the Program Solicitation.