N0017325R0007 - Attachment 13_Task Order 002 SOW.pdf

Naval Research Laboratory 4555 Overlook Avenue SW

Washington DC, 20375-5329 Code 8140

Statement of Work (SOW) For

Focused Radio Frequency Optimized Signal Transference (FROST)

Task Order 002

CONTRACT: N00173-25-D-xxxx

TASK ORDER: 002

Table of Contents

1.0 Task Order Scope

2.0 Requirements

2.1 Technical Requirements (CDRL A001, A004)

3.1.1 RF Engineering and Technical Development (CDRL A001, A004)

3.1.2 Hardware (CDRL A001, A004)

3.1.3 Electronics (CDRL A001, A004, A006)

3.1.4 Software Design, Development, Test and Integration (CDRL A001, A004)

3.1.5 Networks and Accreditation (CDRL A001, A004)

3.1.6 RF Mobile Communications (CDRL A001, A004)

3.1.7 Optical (CDRL A001, A004) ..................................... Error! Bookmark not defined.

3.1.8 System Plans and Documentation (CDRL A001, A004)

3.1.9 Interface Control Documents (ICD) (CDRL A001, A004)

3.1.10 Operations Documentation Development (CDRL A001, A004)

3.1.11 Testing and Training (CDRL A001, A004)

2.2 Travel (CDRL A001, A002)

2.3 Meetings and Reviews (CDRL A001, A004)

2.4 Security (CDRL A001, A007)

3.0 Deliverables

3.1 Technical Status Report

3.2 Contract Status and Labor Report

3.3 Financial Program Management Report

3.4 Technical Data and Documentation

3.5 Patent Report

3.6 System Safety Hazard Analysis Report

3.7 Accident Incident Report

3.8 Final Report

1.0 Task Order Scope

The specific objectives for Task Order 002 will be focused on advancing the RF research and development of specialized RF systems for use within mobile platforms (IE: helicopters and ground vehicles).

Period of performance for this Task Order 002 is 36 months consisting of one base year with two option years.

Labor Categories

TO-2

Base

TO-2

OY1

TO-1

OY2 Total Hours

Labor Hrs.

Labor Hrs. Labor Hrs.

SR FIELD ENGINEER 1,920 1,920 1,920 5,760

MID COMPUTER SCIENTIST 960 960 960 2,880

SR TEST ENGINEER 1,920 1,920 1,920 5,760

SR PROJECT SPECIALIST 960 960 960 2,880

SR NETWORK ENGINEER 1,920 1,920 1,920 5,760

23,040

The anticipated ODC support includes:

ODC Support Categories

TO-1

Base

TO-1

OY1

TO-1

OY2

Total

Materials $50,000 $50,000 $50,000 $150,000 Travel $5,000 $5,000 $5,000 $15,000 Total ODC Value $55,000 $55,000 $55,000 $165,000

2.0 Requirements

The Government will provide facilities, and will also consider the use of contractor provided facilities, either owned or procured for this contract, when needed, for field or laboratory experiments, and for assembling, testing and using hardware developed or purchased under this SOW. Government facilities may also include US military or government installations.

The Contractor shall perform work assignments and provide all necessary personnel to accomplish the technical actives detailed within this SOW (CDRLs A001, A002).

The contractor shall provide management oversight to deliver the science and engineering expertise and products described herein (CDRLs A002, A003, A006, A007 and A008). The contractor shall provide the logistics, procurement resources, and facilities necessary to purchase, house, control, and report on the equipment, materials, supplies, and software required for the performance of the efforts defined herein.

Because the successful performance of this SOW requires close coordination, meetings, and interaction with NRL, other Government, military, and private sector organizations, the contractor shall establish the appropriate non-disclosure agreements as needed to ensure acceptable and continuous interface support.

The contractor shall provide personnel and material resources to support technical exchange meetings and system reviews which many include but are not limited to:

• System Requirement Reviews (SRRs)

• Preliminary Design Reviews (PDRs)

• Critical Design Reviews (CDRs)

• Test Readiness Reviews (TRRs)

• Scientific or Engineering conferences.

The contractor shall present technical results and other conclusions at these meetings. The contractor shall also participate in periodic and informal working group meetings and discussions related the technical activities detailed within this SOW (CDRL A004).

The performance of this contract may result in achievements worthy of publication via scientific and/or technical periodicals. All publications resulting from these tasks, as well as presentations to entities other than NRL shall be approved for released through the NRL information pre-release approval process. All publications resulting from these tasks which also involve external research sponsors funding, personnel or equipment shall also be approved through the relevant sponsor’s pre-release approval process. The Contractor must receive all requested and required approvals prior to the release of any publication submissions or drafts. Achievements worthy of patent consideration shall also be identified (CDRL A005).

2.1 Technical Requirements (CDRL A001, A004)

The Contractor shall perform advanced RF engineering tasks to research specialized RF systems in mobile platforms (IE: helicopters and ground vehicles). These RF generation systems provide transmission and receive capability and support multiple user platforms..

The Contractor shall make the modifications and test the hardware and software developed to accommodate technical advances and meet the requirements of engineering change orders (ECO’s). These changes may include hardware, software and documentation. Tests may include but are not limited to:

Environmental Qualifications Testing (EQT) Electromagnetic Interference (EMI) Electromagnetic Compatibility (EMC) TEMPEST (Telecommunications Electronics Materials Protection from Emanating Spurious

Transmissions) Testing.

3.1.1 RF Engineering and Technical Development (CDRL A001, A004) The Contractor shall recommend and develop specialized mobile RF systems. System performance modeling may include mathematical transformations or other innovative techniques.

Mobile RF antenna systems have been developed for this ongoing effort. The contractor shall ensure backwards compatibility and perform regression testing to ensure current developments move the research forward without negatively impacting current capabilities.

The Contractor shall evaluate the condition of legacy or existing equipment. This R&D effort has progressed beyond lifecycle expectancy of many individual components while technology and cyber security requirements have evolved. The Contractor shall advise the government of equipment that may be insecure, no longer be technically adequate or serviceable and recommend options, updates or upgrades. With government concurrence and approval, equipment refreshes or replacements shall be incorporated into the design and scheduled to coincide with FROST development, installation and integration testing to maximize efficiency.

The Contractor shall inform NRL of changes and proposed changes to frequency spectrum allocations administered by the Federal Communications Commission (FCC) and the National Telecommunications and Information Administration (NTIA) in accordance with the “Manual of Regulations and Procedures for Federal Radio Frequency Management” (September 2017, as amended) and “Naval Telecommunications Procedures, Navy Electromagnetic Spectrum (EMS) Guide”, NTP 6E (April 2011) . The Contractor shall test for potential interference with U.S.

Navy space systems by proposed frequency spectrum allocation changes or shared spectrum using advanced RF techniques.

3.1.2 Hardware (CDRL A001, A004)

The Contractor shall design, develop, test and integrate hardware for RF mobile systems.

RF mobile systems may be in any stage of the system lifecycle. The Contractor shall provide solutions and recommendations for upgrading existing components and infrastructure to ensure the successful integration of FROST systems.

In some instances, the hardware design exists. In this scenario the Contractor shall implement NRL-provided hardware designs and complete the development effort through test and integration.

3.1.3 Electronics (CDRL A001, A004, A006)

The Contractor shall develop the electronic designs given a set of design specifications.

Many designs will require functional and operational compatibility with the current power and environmental limitations.

The Contractor shall apply knowledge of the frequency spectrum to RF anomaly system design, to include, but not limited to, system safety to mitigate RF energy hazards per MIL-STD-882E.

The Contractor shall incorporate safety restrictions including but not limited to those identified in FCC OET Bulletin 65 into the system design.

In some instances the electronics design exists. In this scenario the Contractor shall implement NRL-provided electronics designs and complete the development effort through test and integration.

3.1.4 Software Design, Development, Test and Integration (CDRL A001, A004) The Contractor shall design develop and maintain software for RF mobile systems to ensure the generation and measurement of precise, accurate signals.

The required software may be used in new, modified, or upgraded mobile systems. Software shall be designed using industry standards and best practices to ensure software maintainability and reliability.

The Contractor shall conduct object-oriented analysis and design of instrument control systems.

The Contractor shall create or update software development specifications to integrate ECO’s.

New and modified software shall comply with provided system and design documents to ensure interoperability with existing software and legacy hardware.

The Contractor shall implement NRL-provided software designs and complete the development effort through test and integration.

3.1.5 Networks and Accreditation (CDRL A001, A004)

The Contractor shall design, develop, and maintain digital networks used as part of the RF systems. These networks may connect RF systems and devices using uncommon protocols and complex configurations.

Some of these networks provide high to low communications. The Contractor shall comply with and conform to information and cyber security regulations and limitations including security classifications and those concerning high to low communication restrictions.

3.1.6 RF Mobile Communications (CDRL A001, A004)

The Contractor shall design and develop or modify specialized, secure RF mobile communication systems. Some mobile RF system hardware may be dictated by the specific project and some may be developed or recommended by the Contractor.

The Contractor may be asked to retrofit designed systems to previously procured units. The Contractor shall present solutions and recommendations for the retrofit design. With government concurrence and approval, the contractor shall develop, test and integrate the retrofit design.

The Contractor shall develop secure communication and interface software for RF mobile communication systems. These systems work in conjunction with the above-mentioned new and retrofit systems.

3.1.8 System Plans and Documentation (CDRL A001, A004)

The Contractor shall develop and modify system plans and documentation. Documentation may include drawings (I.E. Visio, AutoCAD) to ensure clarity of design and to aid technical understanding.

The Contractor shall utilize industry accepted formatting for the technical documentation type as appropriate. Common documentation types may include but are not limited to:

• Memo for the Record

• System Specifications

• Project Schedules

• Test Plans and Test Reports

• Drawings o Architectural o Electrical o Interconnect (Rack and elevation detail)

• Accreditation documentation o System Security Plan o PPS (Ports, Protocols and Services)

The Contractor shall comply with local configuration control (CM) processes and procedures when introducing new documents to the baseline and when modifying existing, controlled document artifacts.

Documents and drawings may be modified and delivered iteratively during a development lifecycle.

3.1.9 Interface Control Documents (ICD) (CDRL A001, A004)

The Contractor shall develop, update and maintain internal and external Interface Control Documents (ICD’s) which specify interface requirements for designed hardware and software.

The Contractor shall participate, when invited by the government, in technical exchanges with internal or external customers to coordinate potential additions or changes to interconnection.

Additionally, the Contractor shall assist internal and external customers utilizing the ICD data to create approved interconnections via the published interconnection points.

The Contractor shall comply with local CM policies and procedures when introducing or updating ICDs including submitting draft documents for stakeholder reviews and Configuration Control Board (CCB) approvals.

3.1.10 Operations Documentation Development (CDRL A001, A004) The Contractor shall develop, update and maintain engineering, logistics, and operations documentation for operators and maintainers of all systems developed. Updates and modifications of published documents shall comply with local CM policies and procedures.

3.1.11 Testing and Training (CDRL A001, A004)

The Contractor shall develop and execute test plans to ensure smooth integration of system additions, upgrades or modifications while adhering to local CM policies and procedures. The depth and detail of the testing plan (I.E. full system, sample, or regression testing) shall commensurate with the current milestone.

The Contractor shall analyze and forecast the performance of existing and future systems.

The Contractor shall provide end-user training for systems incorporated into an operational baseline. Training materials required include are but not limited to:

• System User Guide

• Concept of Operations (ConOp)

The Contractor’s onsite personnel shall complete required training prior to published due dates.

This training may include but is not limited to:

• OPSE-1301 Operations Security (OPSEC)

• RF Safety Hazards

• Security related training

• Local training requirements

2.2 Travel (CDRL A001, A002)

Travel to CONUS sites for comparative analysis is required to perform research tasks including but not limited to: configure, observe, analyze and record research testing and results. CONUS travel is required for members of the research team to be physically present to conduct precision testing, to monitor results, ensure accurate outputs, and verify data for future analysis.

The Contractor personnel and management shall coordinate all travel with the Government PM to ensure all required travel requests and documentation are submitted within the required timelines prior to travel.

The Contractor shall verify that all pre-shipped hardware and materials necessary to perform the prescribed activities have arrived at the travel location prior to executing the related leg of a travel itinerary.

Contractor personnel shall participate in any travel related training programs which may include but are not limited to:

• Motor Vehicle Operation (when required by host country laws)

• Anti-Terrorism Level One

2.3 Meetings and Reviews (CDRL A001, A004)

The Contractor shall provide the appropriate personnel to participate in requirements reviews, design reviews, and technical interchange meetings for each development program.

The Contractor shall record minutes of key meetings, reviews and technical interchanges which include government approvals including but not limited to design, schedule, milestone acceptance and action items.

2.4 Security (CDRL A001, A007)

Access to classified Top Secret/SCI technical data may be required in the performance of the contract. The number and type of clearances required will be described in the contract DD254.

Contractor Key Personnel who require access to TS/SCI material shall possess a final DoD granted Top Secret security clearance with the eligibility of SCI at time of proposal submission in order to ensure the ability to minimally staff a cleared transition team.

Detailed security requirements are delineated in the issued DD254 relevant to this contract. The Contractor shall ensure that all classified material is handled in accordance with the issued DD 254, the National Security program Operating Manual (NISPOM) (DoD 5220.22M and all NRL and applicable Security Program Guides/Directives.

Contractor personnel providing access control and security related tasking must have a favorably adjudicated DoD Tier 5 investigation, a final Top Secret security clearance and written approval of the MRC Security Manager.

Contractor personnel that require elevated system privileges (i.e. root or administrator level access) will also be required to meet IAT Level II or Level III training and certification requirements IAW DoDM 8140.03. Privileged User (PU) accounts can only be authorized for those meeting the associated DoDD 8140.01 requirements.

3.0 Deliverables

The Contractor shall provide NRL with the following deliverable items in accordance with the relevant Contract Data Requirements List (CDRL) items.

3.1 Technical Status Report

The Contractor shall provide a Technical Status Report (CDRL A001). The Contractor shall provide highlights of significant actions that occurred during the reporting period relative to contract performance. Significant actions include any that will impact, or have impacted, the projected performance, cost or schedule of the program effort.

The Contractor shall provide information on planned technical deliveries, meetings and schedules versus actual activities performed. Actual and projected schedule changes shall be reported along with their actual and projected impact on overall contract performance. The Contractor shall provide details on the progress of each contract task or item including hardware and software design, development, configuration management, quality control, integration and test and/or other actions needed to fulfill contract requirements. The status of materials, data items, and subcontracting must also be reported. Government Furnished Equipment (GFE) inventory changes (added to or removed from the contract) during the reporting period shall be identified.

The Contractor shall advise of all travel performed in support of the SOW. Travel completed during the report period will be included as well as requested or required travel projected for the next four reporting periods.

The Contractor shall identify any technical or contractual problems and issues. Proposed resolution(s) shall be presented. Each subsequent report shall include an update of any previously reported unresolved problems until final resolution is presented as a completed task.

3.2 Contract Status and Labor Report

The Contractor shall provide a Contract Status and Labor Report (CDRL A002). The Contractor shall provide contract and sub-contracts status and labor levels. Labor hours expended during the reporting period shall be reported per person (as identified by name rather than employee or billet number), per WBS activity by the contractor an all sub-contractors. Labor hours expended per labor category during the reporting period shall also be provided. In the case where that there exists a one-to-one correlation between the by-name labor and related labor category these data items may be combined as one table or report item as long as all required items are clearly identified and included in the Monthly Contract Status and Labor Report.

The Contractor shall summarize all contract maintenance tasks including contract modifications completed during the reporting period.

The Contractor shall provide a single line stating the discrete, total number of contractors and sub-contractors performing on the contract for any number of labor hours greater than zero during the reporting period.

The Contractor shall identify contractual or labor problems and issues. Proposed resolution(s) shall be presented. Each subsequent report shall include an update of any previously reported unresolved problems until final resolution is presented as a completed task.

3.3 Financial Program Management Report

The Contractor shall provide a Financial Program Management Report (CDRL A003). The Contractor shall provide information on contract and sub-contracts financial and funding levels.

The cost data shall include current month as well as cumulative totals for funding, invoiced expenditures, commitments and balances.

The Contractor shall provide a breakdown of costs relative to each Accounting Classification Reference Number (ACRN), Work Breakdown Structure (WBS) and completed for all Contract Line Items (CLIN) including labor, material, Other Direct Charges (ODCs), and travel.

3.4 Technical Data and Documentation

The Contractor shall provide a Technical Data and Documentation Deliverable (CDRL A004).

The Contractor shall provide all technical data and documentation developed pursuant to the SOW. The data and documentation shall be delivered no later than 15 days following the conclusion of the relevant milestone to include but limited to:

• Design Reviews.

• Acceptance or Integration Tests.

• Military Exercise Events.

• Baseline Upgrades.

Where DoD, NRL or sponsor policy differ from the CDRL submission dates the DoD, NRL or sponsor policies will take precedence. In the instance that the above policies are vague, imprecise or extend beyond the end of the contract period of performance the CDRL A004 deliverable deadlines remain in place. I.E. The NCST Configuration Management Plan (CMP) may require design documents to be delivered at the time of a Change Request (CR) submittal in order to facilitate a Configuration Control Board (CCB) review necessary to achieve the required approval to implement. Meanwhile CDRL A004 would require design documents to be delivered no later than 15 days following the implementation milestone. The CMP requirement for delivery takes precedence.

The Contractor shall deliver all outstanding technical data and documents within 15 days of the end of the contract. The end of the contact period of performance shall be considered the final project milestone for the purpose of CDRL A004.

3.5 Patent Report

The Contractor shall perform internal, quarterly reviews to evaluate the research and development activities for potential patent opportunities. The Contractor shall provide a Patent

Report (CDRL A005) that documents and summarizes any research product that is eligible for patent submission or consideration.

3.6 System Safety Hazard Analysis Report

The Contractor shall provide a System Safety Hazard Analysis Report (CDRL A006) that Identifies potential safety hazards specific to a project or deployment.

3.7 Accident Incident Report

The Contractor shall provide an Accident Incident Report (CDRL A007) to report the occurrence of incidents resulting in any one or more of the following:

• personnel injury.

• property damage.

• security violation.

• other significant incidents.

The Contractor shall provide a summary of what happened in the incident in accordance with DI- MGMT-82118. The distribution of reports concerning security violation incidents shall include the Security Manger. The distribution of reports concerning safety incidents (personal injury, property damage and other significant incidents) shall include the Safety Officer.

The Contractor shall include actions and corrective actions that have been or will be taken to prevent re-occurrence of the incident or accident, the timeline for performing all actions and corrective actions, as well as associated work orders that will be used to track the cost.

3.8 Final Report

The Contractor shall provide a Final Report (CDRL A008) at the end of the contract performance period. The Contractor shall provide a comprehensive final report that summaries all the scientific objectives, findings, and recommendations, research development, and other efforts performed and the results.

The Contractor shall include a final GFE inventory. The disposition (returned, transferred, disposal or lost/stolen) and condition of each inventoried item shall be recorded.

This RF research and development program has been a multi-year effort consisting of several iterations of follow-on contracts. In the event that there is any incomplete research or development at the end of the contract period of performance the Contractor shall provide the detailed status to include but not limited to the work completed, progress to date, specific tasks incomplete, obstacles or technical issues encountered and recommended next steps.