View the file

Other files

File Type Posted
Att 2 - Draft Personnel Qualifications.pdf PDF
Att 4 - Draft DD254.pdf PDF
Att 5 - Requirements for Onsite Contractors.pdf PDF
Att 3 - Draft CDRLs.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment No. 1 Statement of Work

N00173-23-RFI-EN02

Statement of Work (SOW)

DEVELOPMENT, TESTING AND ASSESSMENT OF

ELECTRO-OPTIC/INFRARED (EO/IR) ADVANCED

INTELLIGENCE, SURVEILLANCE, AND

RECONNAISSANCE (ISR) SYSTEMS AND

TECHNOLOGIES

Version No. 1- FEBRUARY 2023

DRAFT

Vision Statement

1.0 Introduction

1.1 Mission

1.2 Background

1.3 Scope

2.0 General Requirements

2.1 Period of Performance

2.2 Non-Personal Services

2.3 Business Relations

2.4 Contract Administration and Management

2.4.1 Contract Management

2.4.2 Personnel Administration

2.4.3 Contract Administration

2.4.4 Contractor's Management Plan (CMP)

2.5 Contractor Furnished Equipment, Materials, Subcontracts and Supplies

2.6 Contractor Personnel, Disciplines, and Specialties

2.7 Location and Hours of Work

2.8 Travel / Temporary Duty (TDY)

3.0 Technical Requirements

Subtask 3.0.1 Technical Interchange Meetings (TIMs)

3.1 Mission Analyses and Sensor Requirements Definition

Subtask 3.1.1 Analysis of Future Naval and Marine Corps Requirements

Subtask 3.1.2 Analyze Existing EO/IR and ISR Systems for Deficiencies

Subtask 3.1.3 Analyze EO/IR, ISR System Emerging Technology

Subtask 3.1.4 Coordinate with DOD and other Intelligence Services

Subtask 3.1.5 Technology Needs Assessment

Subtask 3.1.6 Technology Development

Subtask 3.1.7 Analysis of Alternatives (AOAs)

Subtask 3.1.8 Develop Documentation for Technology Programs

3.2 Develop New ISR, and EO/UV/IR Sensor System Concepts and Implementation Plans . 15

Subtask 3.2.1 System Design and Performance/ Optimization Review

Subtask 3.2.2 Sensor System Analysis and Data Fusion

Subtask 3.2.3 EO/IR Systems Concept of Operations

3.3 System and Technology Evaluations

Subtask 3.3.1 Design and Develop EO/IR System Architectures

Subtask 3.3.2 Hardware Development/Procurement

Subtask 3.3.3 Assemble Prototype Systems

Subtask 3.3.4 Design and Prototype Documentation

Subtask 3.3.5 System Reviews

Subtask 3.3.6 Prototype Troubleshooting and System Repair

3.4 Prototype System Development and Integration

Subtask 3.4.1 Prototype Development, Assembly, and Integration

Subtask 3.4.2 Algorithms and Software Development

Subtask 3.4.3 System Integration

Subtask 3.4.4 Report and Recommendations

3.5 Software Development for EO/IR Sensors and ISR Systems

Subtask 3.5.1 Prototype Software

Subtask 3.5.2 System Software Architecture Design

Subtask 3.5.3 Develop Software Required to Operate Prototype Systems

Subtask 3.5.4 Develop Image Screening and Collection Algorithms

Subtask 3.5.5 Develop Embedded Real Time System Software

Subtask 3.5.6 Software Platform Integration

Subtask 3.5.7 Contractor Developed Software Designs

3.6 Test and Evaluation (T&E) Support

Subtask 3.6.1 Test Support

Subtask 3.6.2 Test Planning Documentation and Preparation

Subtask 3.6.3 Test Preparation and Conduct

Subtask 3.6.4 Data Analysis

Subtask 3.6.5 Final Prototype Sensor System Design, Development, Optimization and Test

Installation

4.0 Special Requirements

4.1 Security

4.1.1 DD Forms 254

4.1.2 Identification (ID) Badges and Vehicle Passes

4.2 Safety

4.3 Transition

4.4 Government Furnished Materials

5.0 Deliverables

6.0 Related Documents

7.0 Definitions and Acronyms

7.1 Definitions

7.2 Acronyms

Development, Testing and Assessment of Electro-

Optic/Infrared(EO/IR) Advanced Intelligence, Surveillance, and Reconnaissance (ISR) Systems and Technologies

Vision Statement

Maintain world class leadership position in research, development, and exploitation of new and advanced optical technologies in solving Naval intelligence, surveillance, and reconnaissance

(ISR) problems.

1.0 Introduction

The Optical Sciences Division (NRL Code 5600) caries out a variety of research, development, and application-oriented activities in the generation, propagation, detection, and use of radiation in the wavelength region between near-ultraviolet and far-infrared wavelengths. The research, both theoretical and experimental, is concerned with discovering and understanding the basic physical principles and mechanisms involved in optical devices, materials, and phenomena.

Development efforts are aimed at extending this understanding in the direction of device engineering and advanced operational techniques.

1.1 Mission

The mission of this procurement is to acquire the expertise of highly skilled personnel, equipment and facilities to support the Optical Sciences Division with a comprehensive, integrated program of systems engineering, technical engineering, engineering analysis, independent assessments, and research activities pertaining to the development, measurement, and evaluation of new and existing ISR systems and avionics. The required engineering efforts and areas of technical investigation will be broad, but will emphasize the development of electronic systems and embedded software to facilitate the operation and optimum use of visible, electro-optic, and infrared (VIS/EO/IR) sensors and systems. While the emphasis is on

VIS/EO/IR technologies, alternative approaches using technologies such as acoustics and radio frequencies may be investigated from time to time to determine if more effective solutions could be achieved using technologies other than VIS/EO/IR. Also, the use of optical technology in areas such as materials development, information processing, bio-engineering, and communications may also be investigated.

1.2 Background

Activities undertaken recently include: (a) research and development of advanced technology concepts, early test and evaluation of prototype systems, and evaluation of advanced concept

Intelligence, Surveillance, and Reconnaissance (ISR) systems, (b) identification of requirements for developing solutions to threat systems, including development of technical specifications to accommodate aircraft, ground, surface, and sub-surface platform requirements, (c) technical insertion of new technologies into current and near-term ISR systems in order to provide solutions to advanced and emerging threat systems, (d) analysis and evaluation of promising technology, including development of one-of-a-kind measurement and evaluation processes, (e) development of algorithms and techniques for implementation in advanced systems, (f) modeling and simulation to aid development programs, and (g) technical management and engineering support to aid the transition of new technologies into System Development and

Demonstration phase for Navy/Marine Corps, and other Service, acquisition programs.

Specific examples include:

(1) Development of a prototype compact hyperspectral imaging (HSI) system to include trade study analysis, requirements definition, and optical and mechanical design development leading toward successful completion of Defense Threat Reduction Agency

(DTRA)-led Critical Design Review (CDR);

(2) Development, prototyping and conduct of initial field testing of active EO sensor technologies supporting through-fog imaging and other imaging systems in highly-scattering environments;

(3) Development, flight-testing, and transitioning (to TRL-7 level of maturity) of the dual-band wide-area persistent surveillance sensor (DB-WAPSS) system which uses a 16.7-megapixel mid-wave infrared (MWIR) focal plane array (FPA) sensors to provide day/night IR surveillance coverage in addition to increased resolution performance at low altitudes in support of the USMC's Angel Fire program;

(4) Development, integration, testing, and field user evaluation (FUE) of multi-sensor, multi-platform command and control coordination and analysis capabilities in support of the Brilliant Effects Employment Shadow (BEES) Joint Capability Technology

Demonstration (JCTD).

1.3 Scope

The purpose of this contract is to provide specialized capability to perform research toward the development and improvement of EW and ISR systems such as High Roller, Low Cost UAV

Swarming Technology (LOCUST), Shipboard Panoramic Electro-Optic Infrared (SPEIR), ANGEL Fire and DB-WAPSS; and new VIS/EO/IR ISR systems for the Optical Sciences

Division (NRL Code 5600) in the areas described below:

Analyze System Alternatives

Analyze VIS/EO/IR Technology in Lab Setting

Design and Develop VIS/EO/IR System Prototypes

Test and Evaluate VIS/EO/IR System Prototypes

Transition VIS/EO/IR System Prototypes to The Naval and Department of

Defense (DoD) Acquisition Processes

Provide Technical Support to Programs

Efforts in support of the tasks delineated in Section 3, Technical Requirements, below will be conducted in coordination with Principal Investigator (PI) led research team(s) that may include

Government scientists and other Contractors. The quality and timeliness of the provider's contribution to the work will be evaluated in terms of its impact on the success of the overall project.

2.0 General Requirements

2.1 Period of Performance

The period of performance is 60 months (base year plus 4 option years).

2.2 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks.

The Government will not assign tasks to, or prepare work schedules for, individual contractor employees.

The Contractor shall be responsible for managing its employees and guarding against any actions that are of the nature of personal services, or give the perception of personal services as defined in FAR-Part 37, Service Contracting, dated 31 May 2011.

The Contractor shall notify the Contracting Officer (KO) if any Government requested actions constitute, or are perceived to constitute personal services.

2.3 Business Relations

The contractor shall integrate and coordinate all activity needed to execute this contract.

2.4 Contract Administration and Management

The following subsections specify requirements for contract management and contractor personnel administration.

2.4.1 Contract Management

The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to this contract.

The contractor shall submit the items included in the Contract Data Requirement List (CDRL), detailed below, in electronic format via email or other secure means, and such electronic documents shall be named:

N00173-23-19CNNNN_AXXX_DATE_TITLE_REV.EXT

where “NNNN” is the contract number, “AXXX” is the CDRL item number, DATE is the date in the format below, TITLE is the descriptive title, REV is the revision level, and EXT is the appropriate file extension. Thus, a monthly cost report could be named:

“N0017319C6999_A001_2019_(01)JAN_MTHLY_COST_RPT_REV0.xlsx”.

Please note that the (01) is not the day, but rather the month number, to force the sort order.

The contractor shall include on the cover pages of documents including technical data an appropriate Distribution Statement, International Trafficking in Arm Regulations (ITAR) paragraph, and Destruction Notice. For Example:

The Contractor shall provide a Monthly Status and Financial Report summarizing the expenditures and balances for each contract line item and/or contract option, sorted by ACRN, in the format defined in Funds and Man-Hour Expenditure Report [CDRL A001].

The Contractor shall provide a Monthly Technical Status/Progress Report summarizing the status of the technical process and status of each major task effort, any significant technical or project-specific problems, and the proposed resolution of the identified problem areas [CDRL

A002]

The Contractor shall provide a Monthly Staffing Chart showing the current staff and related responsibilities defined in [CDRL A003]. Chart may be included as part of the Monthly

Contractor On-Site/Off-Site Labor Report defined in [CDRL A007]

The Contractor shall for each Task Order awarded under this SOW, the contractor shall submit draft test plan(s) and formal test report(s) as defined in [CDRL A004].

The contractor shall provide copies of all software, data developed and provide documentation, as required, to facilitate the efficient use of the research and development under each Task

Order awarded under this SOW as defined in [CDRL A005].

“DISTRIBUTION D. DISTRIBUTION AUTHORIZED TO DOD AND U.S. DOD

CONTRACTORS ONLY (CRITICAL TECHNOLOGY) (31-JANUARY-2019). OTHER

REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO COMMANDING OFFICER,

U.S. NAVAL RESEARCH LABORATORY, ATTN CODE 5663,

4555 OVERLOOK AVE SW WASHINGTON DC 20375”

“WARNING: THIS DOCUMENT CONTAINS TECHNICAL DATA, EXPORT OF WHICH IS

RESTRICTED BY THE INTERNATIONAL TRAFFIC IN ARMS REGULATIONS (ITAR).

DISCLOSURE TOO FOREIGN PERSONS WITHOUT PRIOR U.S. GOVERNMENT

APPROVAL IS PROHIBITED. VIOLATIONS OF THESE EXPORT LAWS AND

REGULATIONS ARE SUBJECT TO SEVERE CIVIL AND CRIMINAL PENALTIES.”

“DESTRUCTION NOTICE For classified documents, follow the procedures in DoD 5220.22-M, Industrial Security Manual, Section 11 -19 or DoD 5200.01, DoD Information Security Program. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

The contractor shall prepare and present formal review material that explains and defends their designs accomplished under this SOW as defined in [CDRL A006].

The Contractor shall deliver a Monthly On-Site/Off-Site Labor Report as defined in [CDRL

A007]. This report may be included with the Chart required by [CDRL A003].

The Contractor shall deliver a Final Technical Report for all work accomplished under this SOW

90 days after the completion of the contract in accordance with DI-MISC-80711A, Scientific and

Technical Reports, as defined in [CDRL A008].

2.4.2 Personnel Administration

The Contractor shall provide for employees during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions.

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the SOW requirements.

The Contractor shall make necessary travel arrangements for employees.

2.4.3 Contract Administration

The Contractor shall establish processes and assign appropriate resources to effectively administer this contract.

The Contractor shall respond to Government requests for contractual actions within five work days.

The Contractor shall assign work effort and maintain proper and accurate time keeping records of personnel assigned to work on this contract.

2.4.4 Contractor's Management Plan (CMP)

The CMP provides the Government insight to the systems, processes, and structure within which the contractor operates. The CMP should include, as applicable and if not defined in a separate plan: quality control, risk management, systems engineering, software development, configuration management, and subcontract management.

The contractor shall submit a Contractor's Management Plan (CMP) defining the contractor's approach to implementing the contract in accordance with DI-MGMT-80004A, Management

Plan with submission of the offeror’s proposal.

2.5 Contractor Furnished Equipment, Materials, Subcontracts and Supplies Equipment and unexpended materials and supplies purchased by the contractor under this contract become the property of the Government at the end of the performance period, including all options, or when the Government asserts ownership.

The Contractor shall provide supplies for contractor personnel.

The Contractor shall provide any other equipment, material, and supplies, not furnished by the

Government, but required to perform the work defined under Paragraph 3, Performance

Requirements, below.

The Contractor shall be responsible for any subcontract management necessary for performing efforts described in Paragraph 3, Technical Requirements, below.

2.6 Contractor Personnel, Disciplines, and Specialties

The minimum education, training, and experience required by contractor personnel to perform support tasks identified in this SOW are defined in the labor category descriptions provided as

Attachment J-2, Personnel Qualifications.

2.7 Location and Hours of Work

Accomplishment of the results contained in this SOW requires work at the Naval Research

Laboratory facilities, 4555 Overlook Ave, SW, Washington, DC 20375-5320. Normal workdays are Monday through Friday except US Federal Holidays. NRL workers typically work eight (8) hours per day, 40 hours per week. Flextime workers start not earlier than 0600 and not later than 1000. Core hours of work are from 1000 to 1500 daily. All employees are expected to be available during core hours. Additional information on work hours is provided in Section 1. (c), NRL HOURS OF OPERATION AND HOLIDAY SCHEDULE, in the NRL ROSC.

2.8 Travel / Temporary Duty (TDY)

Travel to other contractor or government facilities, such as, Naval Air Station (NAS), Naval

Surface Warfare Center (NSWC) – Dahlgren, NRL Chesapeake Bay Detachment (NRL-CBD), Blossom Point Research Field, as well as other Government sites in pursuit of NRL objectives may be required for conduct of experimental research, attendance at government reviews, scientific meetings, and seminars. Additionally, testing of components and prototypes may occur at Government bases and test ranges including, but not limited to, Eglin Air Force Base, FL, Aberdeen Proving Grounds, MD, Marine Corps Air Station Yuma, AZ, and NSWC Crane, IN.

Travel to foreign sites, such as Naval Base Guam, for the same purposes as above, may also be required.

The Contractor shall maintain the capability to arrange the travel of contractor personnel to locations in CONUS/OCONUS, often on short notice.

The Contractor shall bill costs for travel in accordance with FAR 31.205-46 Travel Costs

(subject to local policy & procedures).

3.0 Technical Requirements

Guidance on development of software and hardware technical data packages required to meet requirements of CDRLs A005 and A006 for documenting the design of systems resulting from activities conducted under sections 3.2 and 3.3 is dependent on the specific package, and will be provided as needed.

Subtask 3.0.1 Technical Interchange Meetings (TIMs) The Contractor shall prepare for, conduct, and document Technical Interchange Meetings in accordance with DI-ADMIN-81373, Presentation Material, and DI-ADMIN-81250A, Conference

Minutes as required by the COR.

3.1 Mission Analyses and Sensor Requirements Definition

The subtasks within this task shall be performed on a continuing basis throughout this program to provide periodic updates to the analyses and recommendations and to ensure that any development programs initiated as a result of this effort are optimal. Efforts associated with this task shall include the following Subtasks:

Subtask 3.1.1 Analysis of Future Naval and Marine Corps Requirements

3.1.1.1 The contractor shall review Navy and Marine Corps ground, at sea, undersea, and airborne missions and identify the requirements and capabilities documents supporting the mission areas with regard to ISR system needs and capability gaps. Emphasis will be on situational and battlefield awareness against evolving threats, with detailed reviews on persistent surveillance and rapid/precise targeting. This review shall be conducted with sources up to the Secret/No Foreign level of classification.

3.1.1.2 The contractor shall coordinate the review of requirements based on this capability gap analysis with the appropriate OPNAV Requirements Officers (N94, N95, N96, N98) and

NAVAIR/NAVSEA Program Managers.

3.1.1.3 The contractor shall provide a report of findings after this requirements analysis is completed. The requirements analysis should include EO/IR sensor/sensor system requirements for automated ISR survey and inspection missions, machine vision-based image analysis and exploitation, ISR system survivability and vulnerability, aircrew situational awareness, and utilization of ISR information across the networked distributed operational environment.

Subtask 3.1.2 Analyze Existing EO/IR and ISR Systems for Deficiencies.

3.1.2.1 The contractor shall assess existing EO/IR and ISR Sensor System Capabilities within the Navy, other DoD services, and industry; to identify shortfalls, weaknesses, or capability gaps that require development of advanced technology solutions. The purpose of this review is to completely assess current ISR, EO/IR Sensor Systems, and ISR collection, analysis, and distribution capabilities and, when compared to current/near term operational requirements, to identify shortfalls and/or gaps in capability.

3.1.2.2 The contractor shall examine ISR systems and components at levels of development from Technology Readiness Level (TRL) 4 and higher. Factors such as reliability, maintainability, and cost shall also be examined in addition to performance capabilities.

Information on algorithms and software for such tasks as image classification, target detection, clutter rejection, target tracking, and ISR sensor and system control software shall also be reviewed. The available literature on field testing of components and systems, field and laboratory measurements of target and background properties, and system performance modeling shall be reviewed.

3.1.2.3 The contractor shall identify the specific performance deficiencies, both mission degradation and platform survival, and provide an analysis of the technical potential for upgrades of the existing systems to reduce or eliminate the deficiencies. Advanced concepts to be considered include analysis of their capabilities to “defeat” current and future threats.

3.1.2.4 The contractor shall provide an analysis of the cost, schedule, and performance tradeoffs between these technical alternatives. Analysis and reports shall address deficiencies or shortcomings caused by advancements in fielded/projected threat systems.

3.1.2.5 The contractor shall also assess the impact on existing ISR, EO/IR Sensor System acquisition programs of record (PoRs) of introducing new ISR, EO/IR systems and capabilities.

Subtask 3.1.3 Analyze EO/IR, ISR System Emerging Technology.

3.1.3.1 The contractor shall assess emerging ISR, and EO/UV/IR Sensor system capabilities to discover and characterize the potential capabilities of EO/UV/IR technologies, devices, and systems that are currently in research and development in the defense industry, DoD Service

Advanced Technology Development Centers, or Allied Advanced Technology Development

Centers; and the impact on existing acquisition PORs such as the Navy SPEIR system and the

Marine Corps Future Vertical Lift activity.

3.1.3.2 The contractor shall assess ISR systems in relation to unmanned system integration, test, and development, to include manned/unmanned teaming activities.

3.1.3.3 The contractor shall assess ISR automated decision-making and image understanding.

This includes how to automate understanding of the resulting sensor data as well as how ISR architectures can be modified to better allow for and take advantage of automated decision aids.

3.1.3.4 The contractor will characterize the current Technology Readiness Level (TRL) of ongoing development programs and forecast the date these new technology programs will be ready for Initial Operational Capability (IOC).

Subtask 3.1.4 Coordinate with DOD and other Intelligence Services

3.1.4.1 The contractor, as directed, shall attend conferences, meetings and presentations by

DOD intelligence agencies on active and passive ISR imaging technologies (hyperspectral imaging, digital holography, high-speed imaging), ISR component development (EO/UV/IR detectors and optics), machine vision, remote sensing, and other technologies relevant to ISR systems.

3.1.4.2 The contractor shall participate in the analysis of (a) current capabilities, (b) the shortfalls of existing systems, (c) the documentation of system requirements, and (d) analysis/evaluation of alternatives in pursuit of the NRL Advanced Technology program mission and goals.

3.1.4.3 The contractor shall submit a classified trip report following these events outlining presented material and threat.

Subtask 3.1.5 Technology Needs Assessment

3.1.5.1 The contractor shall identify technology areas that are not being addressed by any ISR, EO/IR Sensor System and/or EO/IR program of record and provide an assessment of the impact on the eventual U.S./Allied military platform vulnerability/survivability if no work is done to improve those technologies.

Subtask 3.1.6 Technology Development

3.1.6.1 The contractor shall develop recommendations for NRL Applied Optics Branch to provide the basis for specifying the initial system for each development cycle. The contractor shall perform tradeoffs among performance levels and physical constraints using factors, such as system weight, required power levels, thermal control, duty cycle, platform capabilities, range performance, resolution, field of view, data volume, processing speed, network bandwidth, and human factors, among the mix considered in the tradeoffs. These specifications may be modified based on subsequent analyses or measurements of the technologies needed or available and the limitations or capabilities of available support systems.

3.1.6.2 The contractor shall identify goals for these programs that would yield technologies that would provide satisfactory performance levels and ensure improved aircraft survivability in a combat theater.

Subtask 3.1.7 Analysis of Alternatives (AOAs)

3.1.7.1 The contractor shall conduct an Analysis of Alternatives (AOA) that addresses alternatives to new ISR, EO/IR sensor/sensor system development, such as enhancement of existing sensor systems, alternative technologies, and/or the use of current technologies coupled with a change in tactical employment.

3.1.7.2 The contractor shall define metrics suitable for rating of various design concepts. In defining the metrics, the contractor shall include factors such as ease of development and deployment, technology readiness level, concept of operations, reliability, maintainability, cost, development schedule, etc., that may not be readily assessed with high confidence for draft designs. The contractor shall develop a priority listing of the concepts based on the metrics established. The contractor shall ensure that the metrics are general enough to be applicable to sensor systems based on other than EO/IR sensors.

3.1.7.3 The contractor shall, in the AOA, provide a technical report covering the design report, evaluation metrics and specifications containing the analyses, studies, tradeoffs performed, and the rationale and conclusions. The contractor shall identify source material used in the reports and provide software source codes and algorithms developed in the study. The contractor shall also identify any commercial, open-source, or otherwise available software used in the analyses.

Subtask 3.1.8 Develop Documentation for Technology Programs

3.1.8.1 Support the development of program/project presentations, proposals, progress reports, test reports and summaries for dissemination to or briefing of NRL officials and/or other government/industry agencies.

3.1.8.2 Assist Government Managers in the development of technology transition plans and support the transition of technology to Navy/USMC Program Managers (PMs), other DOD

Service PMs, other government agency PMs or defense industry partners as required.

3.2 Develop New ISR, and EO/UV/IR Sensor System Concepts and

Implementation Plans One of the NRL goals with new sensor development efforts is to fuse the data from the new sensors with other onboard systems in order to greatly increase the overall situational awareness and targeting capabilities of Naval platforms. The ability to overlay multiple, geo-rectified, data sources in real time is a significant increase in current capabilities where sensor data is reviewed sequentially. Based on the work conducted in Task 3.1, the contractor will assist NRL with the fusion of sensor data as outlined in the sub-tasks below:

Subtask 3.2.1 System Design and Performance/ Optimization Review

3.2.1.1 The Contractor shall develop new generation sensors/sensor system concepts for both manned and unmanned aerial, surface, and sub-surface platforms and plans for how these new concepts will interface with existing Naval Platforms or integrate into emerging Naval Platforms.

3.2.1.2 The contractor will review proposed designs to analyze the sensor/sensor systems performance optimization and to identify opportunities for performance enhancement using sensor fusion techniques.

Subtask 3.2.2 Sensor System Analysis and Data Fusion Currently fielded manned and unmanned aerial, surface and sub-surface platform reconnaissance assets provide EO/IR sensor information for Battle Group Commanders with near real time data flow from sensor to user via data links. In addition to current EO/IR sensor systems, Naval platforms could add additional sensors, such as Synthetic Aperture Radars

(SARs), Laser based (active) sensors, Forest Penetrating Radars (FOPENs), nanotechnology based optical detectors, and passive radio-frequency (RF) sensors, which, when integrated with visible or IR imagery in real time, significantly enhance the usefulness of the intelligence product and lead to concepts such as precision strike or counter-fire solutions requiring highly accurate geo-location of targets.

3.2.2.1 The contractor will develop hardware and software for completing fusion of data products and the transmission of fused data products to afloat and/or ashore end users in near real time.

3.2.2.2 The contractor will determine the stability and pointing accuracy of current and next generation ISR and EO/UV/IR sensor systems and summarize in trade off studies.

3.2.2.3 The contractor will integrate visible or IR imagery from current EO/UV/IR sensor systems with complementary sensor systems such as Synthetic Aperture Radars (SARs), Laser based (active) sensors, Forest Penetrating Radars (FOPENs), nanotechnology based optical detectors, and passive radio-frequency (RF) sensors in real time to enhance intelligence products for precision strike or counter-fire solutions requiring highly accurate geo-location of targets.

3.2.2.4 The contractor shall review concepts for ISR automated image understanding and decision-making. Automated image understanding is to include both traditional approaches as well as examination of emerging machine learning based image analysis approaches. This is to also include development of new ISR architectures to better take advantage of automated decision aids as well as development of the decision aids.

3.2.2.5 The contractor shall include development of concepts related to scheduling and management of ISR services to include automated route re-planning, automated sensor re-tasking, and allocation of limited resources due to multiple, simultaneous, requests for service.

Subtask 3.2.3 EO/IR Systems Concept of Operations.

The objective is to identify cost-effective alternative solutions to performance deficiencies as well as desirable capabilities where technology enhancements could further increase performance. Upon completion of these objectives:

3.2.3.1 The contractor shall work with the users of both manned and unmanned systems and review existing ISR and EO/UV/IR Sensor System Concept of Operations (CONOPS) such as the CA-247 MWIR sensor, the MX-20SW and MX-20SP sensors, the Shipboard Panoramic

EO/IR (SPEIR) system, and the Distributed aperture IR countermeasure (DAIRCM) Engineering

Manufacturing Development (EMD) Missile Warning System.

3.2.3.2 The contractor shall analyze ISR and EO/UV/IR Sensor System payload requirements and develop recommendations for fusing the output data with other onboard EO/UV/IR/RF sensor systems. Additionally, the impacts of introducing new or modified systems into current operational systems or into projected systems will be reported.

3.3 System and Technology Evaluations

Subtask 3.3.1 Design and Develop EO/IR System Architectures.

3.3.1.1 The contractor will design and develop system architectures for ISR and EO/UV/IR

Sensor Systems such as the CA-247 MWIR sensor, the MX-20SW and the MX-20SP sensors, the SPEIR system, and the DAIRCM Engineering Manufacturing Development (EMD) Missile

Warning System.

Subtask 3.3.2 Hardware Development/Procurement.

3.3.2.1 Following approval of the system architecture, the contractor will assemble all components necessary to implement the system architecture. This effort will include the purchase of off-the-shelf or modified off-the-shelf hardware and the design and development of unique components and interfaces.

3.3.2.2 The contractor will interface with defense industry partners/suppliers on component hardware requirements, designs, and development, as required.

3.3.2.3 The contractor will implement firmware changes and modifications necessary to evolve the sensor hardware systems or implement new requirements.

Subtask 3.3.3 Assemble Prototype Systems.

3.3.3.1 Utilizing the system architecture design and components/avionics developed in the previous tasks, the contractor will assemble all hardware components and cables into a functional prototype system which can be powered up and evaluated in the laboratory.

3.3.3.2 The contractor will design and build test data recording system(s) and required interfaces to ensure data and system faults are captured during prototype evaluation.

3.3.3.3 Once the system is powered up and operational, the contractor will evaluate the system and ensure all required functionality is being achieved.

3.3.3.4 Following functional system check out, the contractor will transition the prototype system to air, land, or sea platforms for follow-on evaluation.

Subtask 3.3.4 Design and Prototype Documentation.

3.3.4.1 The Contractor will provide complete documentation, including engineering specifications and drawings for all designs and components developed during the development of the system architecture and prototype system design as defined in CDRLs A005 and A006.

3.3.4.2 The Contractor will provide test plans and results during laboratory and field evaluations of the prototype system as defined in CDRL A004.

Subtask 3.3.5 System Reviews.

3.3.5.1 The Contractor will attend and support prototype component and system development progress reviews at periodic milestones during system design, prototype development and test phases.

3.3.5.2 The Contractor will attend and support test reviews for the purpose of determining prototype system readiness for laboratory, field, and flight evaluation.

3.3.5.3 The Contractor will prepare presentations and reports as required to support System

Reviews.

Subtask 3.3.6 Prototype Troubleshooting and System Repair.

The objective is to ensure costly field testing remains on schedule with minimal impact to program funding.

3.3.6.1 The Contractor will maintain spares for all critical prototype components and will repair or replace failed hardware components as required.

3.3.6.2 The Contractor will be on site during all prototype system evaluations and is responsible for ensuring contractor developed hardware, firmware, and software remains operational.

3.4 Prototype System Development and Integration

Subtask 3.4.1 Prototype Development, Assembly, and Integration.

3.4.1.1 The contractor shall finalize designs for prototype systems using the design approaches developed in earlier tasks. For each prototype system, the contractor shall prepare a hardware development plan with schedules, required funding, risks and proposed mitigations, and labor hours for each task.

3.4.1.2 The contractor shall acquire components, subsystems, and software needed for integration into a prototype system.

3.4.1.3 The contractor shall assemble and integrate components into prototype sensor systems.

3.4.1.4 The contractor shall acquire, develop, and configure network, storage, and computing assets as appropriate to support the systems logical interfaces, data volume requirements, processing speed, and bandwidth.

Subtask 3.4.2 Algorithms and Software Development.

3.4.2.1 The contractor shall acquire necessary software design and development tools, using

Government-owned tools or commercially available tools to the maximum extent possible.

3.4.2.2 The contractor shall develop algorithms and software for developing intelligent agents and algorithms for data analysis and system controls as necessary.

Subtask 3.4.3 System Integration.

3.4.3.1 The contractor shall develop a plan to assemble and integrate the sensor prototype systems. The assembly and integration shall verify the prototype's physical parameters, and the testing shall verify the technical performance parameters.

3.4.3.2 The contractor shall carefully track performance versus the hardware development plan.

3.4.3.3 The contractor shall monitor risk throughout the process to determine whether the mitigation strategies need to be modified.

Subtask 3.4.4 Report and Recommendations.

3.4.4.1 The contractor shall provide a technical report on the issues encountered in assembly, integration, and testing. The report shall include the test plans, an analysis of the test results, and the data from the tests. The report shall include recommendations on any hardware or software modifications and provide a detailed rationale for the recommendations. The report shall review the overall program plan and identify any changes needed in the remaining tasks, particularly the field test plans.

3.5 Software Development for EO/IR Sensors and ISR Systems

Subtask 3.5.1 Prototype Software.

3.5.1.1 The Contractor will support the design, development, integration, and optimization of software required to support advanced prototype system development and evaluation on air, land, or sea-based platforms. The process of software development and coding is essential to the success or failure of imaging and countermeasure systems where events are measured in microseconds.

3.5.1.2 The Contractor shall develop and implement software architectures and solutions using current and development machine vision and machine learning tools sets. The contractor shall develop these applications using tools such as YOLO and TensorFlow.

3.5.1.3 The Contractor shall be efficient at coding different processors such as FPGAs, and

ASICs, and shall be capable of programming in multiple languages such as C, C++, C# (.net), Java, Python, XML, and Matlab scripts.

Subtask 3.5.2 System Software Architecture Design.

During the hardware design phase:

3.5.2.1 The Contractor will initiate the system software architecture design based on the type(s) of processors selected, the network(s) to be implemented, and the system data rates expected.

3.5.2.2 The contractor will evolve the software architecture as the hardware design develops and the system is defined with the goal being to bring hardware and software together during prototype development to achieve system functionality.

3.5.2.3 The contractor will attend all hardware and software design reviews and will prepare and present software updates and engineering expertise during discussions. The software architecture will be documented and placed under configuration control.

Subtask 3.5.3 Develop Software Required to Operate Prototype Systems.

3.5.3.1 The Contractor shall write software necessary to operate each component of the prototype hardware design and will ensure that all required functionality is achieved by installing and testing the software on the prototype system.

3.5.3.2 When the required functionality of the software has been achieved, the Contractor will make sure the software is optimized to ensure the software is as efficient as possible.

Subtask 3.5.4 Develop Image Screening and Collection Algorithms.

3.5.4.1 The contractor shall develop algorithms for effective screening of imagery for real time exploitation and analysis. These algorithms shall be developed only in those cases where commercial products are not available.

3.5.4.2 The contractor shall develop displays that are optimized for ease of use and clarity of presentation to the image analyst. The purpose of these displays shall be to facilitate target detection and identification and to provide simple means of extracting small image sections for rapid image transmission.

3.5.4.3 The contractor will document all algorithms as defined in CDRL A005. The underlying principles of the algorithms shall be fully described in technical reports submitted upon completion of each task.

Subtask 3.5.5 Develop Embedded Real Time System Software.

3.5.5.1 The Contractor shall develop embedded software for the real time operation and control of EO/IR sensor systems, electronic sub-systems and IRCM systems utilizing to the greatest extent possible Commercial-Off-The-Shelf hardware and Real-Time Operating System application development environments.

3.5.5.2 The contractor shall develop applications utilizing VxWorks to control software for the following interfaces and components: MIL-STD-1553; Honeywell Embedded GPS/INERTIAL navigational unit; CA-247/263/270/295 Sensors and the MX-20SW Sensor; Advanced Recce

Compression Hardware (ARCH) suite; Solid State Recorder; and MIDL Common Data Link

(CDL).

Subtask 3.5.6 Software Platform Integration.

3.5.6.1 The contractor shall develop software for integration of ISR and EO/UV/IR systems with Naval platforms, including but not limited to RQ-21A Blackjack, RQ-20 Puma, Nibbler UAS, DDG, developmental/fielded Unmanned Aerial Vehicles/Unmanned Combat Aerial Vehicles

(UAVs/UCAVs) and other developmental sea/air platforms. Integration shall include software development for:

Advanced EO/IR systems for manned combat aircraft and unmanned UAVs/UCAVs

New generation EO/IR systems/subsystems

Integration of digital framing cameras with Reconnaissance Management Systems

(RMS) or Fusion Processor (FP) Systems

Integration of ball gimbal based, digital, step-stare systems with RMS or FP capabilities

Real time autonomous control of digital framing cameras or ball gimbal-based sensor systems.

Custom electronics with very high bandwidths circuits.

Subtask 3.5.7 Contractor Developed Software Designs

3.5.7.1 The Contractor shall provide detailed designs necessary to meet rapid prototyping goals for unique, one-of-a-kind systems.

3.5.7.2 The Contractor shall be responsible for design, development, and prototype of hardware and software and for their testing.

3.5.7.3 As systems reach a level of maturity to support transition of the system to industry or the Fleet, the contractor shall provide engineering support and documentation necessary to support a smooth transition.

3.5.7.4 The contractor shall provide support until transition has reached at a sustaining level and can be considered complete.

3.6 Test and Evaluation (T&E) Support.

Following design and development of new sensor/sensor systems, Test and Evaluation of these systems is critical to further development and the understanding of how the systems perform under relevant conditions and enable assessment operational utility. Tasks will include:

Subtask 3.6.1 Test Support.

3.6.1.1 The contractor shall provide research, development, and testing necessary to evaluate new sensor/sensor systems either on the ground, in laboratory tests, or on sea, air, or ground platforms for which these sensors/systems may be targeted.

3.6.1.2 The contractor shall provide engineering expertise necessary to establish complex tests, measurement and analysis of system parameters in the intended operational environment, and post-test analysis and documentation of the test results with the objective of evolving next generation sensors/sensor systems at NRL.

Subtask 3.6.2 Test Planning Documentation and Preparation

3.6.2.1 The contractor shall develop ISR and EO/IR Sensor System test plans, identify special facilities and equipment required, identify test range requirements if needed, provide coordination with other Government agencies, and identify any unique licensing requirements needed to support the tests.

3.6.2.2 The contractor shall coordinate with other test participants and support organizations on any safety issues that must be addressed and for any training needed or special permits that must be obtained.

3.6.2.3 The contractor shall develop a schedule of tasks that must be accomplished to allow the testing program to proceed without delays due to neglect of any requirements needed to allow the testing to proceed.

3.6.2.4 At the conclusion of test planning and with authorization to proceed, the contractor will assist Government personnel in preparation for executing field and flight testing. This effort will include the survey of suitable test sites, drafting of all required range documentation necessary to receive range clearance and authorization to proceed with the test.

3.6.2.5 The Contractor will prepare and staff a detailed test plan and document all testing in formal reports.

Subtask 3.6.3 Test Preparation and Conduct

3.6.3.1 The contractor shall support the measurement of infrared (IR), visible, and ultraviolet

(UV) monospectral, multi-spectral, and hyperspectral signatures of objects of military relevance to include air, surface and land targets such as unexploded ordinance, tactical military ground vehicles, manned and unmanned aircraft, and missiles. This testing and planning may include incorporation of non-EO/IR sensor technologies and other integrated or interoperable battlefield technologies.

3.6.3.2 The contractor shall support the measurements of non-threat backgrounds to fulfill any identified data needs.

3.6.3.3 The contractor shall plan tests, store and assemble the required instrumentation, calibrate and align the instruments, provide for shipment to the appropriate sites, assemble, test and calibrate the instruments, and support the field tests.

3.6.3.4 The contractor will test and verify the networking capabilities, GPS and IRIG time-tagging functions and remote-control functions of data acquisition computers prior to shipment to test sites. The measurements shall include spatial, spectral, and temporal data.

3.6.3.5 The contractor shall be responsible for the on-site maintenance of the instrumentation used for the measurements, and for data security and transmittal.

3.6.3.6 The contractor will conduct measurements at the Naval Research Laboratory (NRL)

(DC and auxiliary sites), Patuxent Naval Air Station, Blossom Point Research Field, Eglin AFB, Camp Atterbury, Utah Test and Training Range, and at other domestic and foreign sites as directed.

3.6.3.7 When supporting testing, especially at remote test sites, and when requested by the

Government Test Director, the contractor will procure any required lab/field/flight/live fire test equipment/apparatus necessary to ensure that costly test periods are met and that system testing remains on schedule.

3.6.3.8 The contractor shall support necessary laboratory tests by participating in the laboratory setup process, and assisting in the measurements, data reduction and analysis.

3.6.3.9 The contractor shall modify and integrate test hardware into test platforms such as the

P-3C, RQ-21A, RQ-20, DDG, and other platforms as needed. Integration shall include training of Government personnel to install, check out, and operate the equipment.

3.6.3.10 The contractor shall also participate in field tests as onboard technicians when required.

3.6.3.11 The contractor shall integrate, calibrate, and maintain test instrumentation, develop test plans and associated documentation, perform tests and write test reports.

Subtask 3.6.4 Data Analysis

3.6.4.1 The contractor shall reduce, and analyze data gathered during the tests, prepare and organize data for input into models, and prepare reports on the tests.

3.6.4.2 The contractor shall analyze data collected during tests of candidate common and cooperative missile countermeasures systems and estimate the life-cycle costs to evaluate the cost effectiveness of the systems. The evaluation shall include the ability of the systems to meet published operational requirements for candidate naval platforms and to meet other performance objectives.

Subtask 3.6.5 Final Prototype Sensor System Design, Development, Optimization and Test Installation.

To facilitate the development of new EO/IR sensor systems, as well as to provide a means to evaluate new and/or refurbished systems, the following tasks shall be accomplished:

3.6.5.1 For airborne sensing prototypes, the Contractor shall design and construct prototype

EO/IR sensor systems or other system installations for NRL research configured P-3 aircraft, research configured C-12 aircraft and for various podded systems suitable for flight on a variety of tactical Naval aircraft including helicopters and unmanned aircraft.

3.6.5.2 for shipboard and ground prototypes, the contractor shall design and construct prototype EO/IR sensor systems or other system installations for integration onto Navy DDGs, USMC ground vehicles, USMC landing craft, or other ground and afloat platforms as needed.

3.6.5.3 The contractor shall design, fabricate, and install unique one-of-a-kind devices for field testing or ground support.

3.6.5.4 The Contractor shall modify aircraft or pod systems for testing of advanced technology

Vis/EO/IR systems and subsystems.

3.6.5.5 The Contractor shall provide drawings and structural analysis necessary to obtain required Navy or FAA test certifications for platform modifications, payloads, or pod designs.

3.6.5.6 Development, control, and archive of engineering drawings and analysis for fabrication of new designs, modifications, and refurbishment.

4.0 Special Requirements

This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

4.1 Security

All Contractor personnel who require NRL base access or access to NRL unclassified material and/or unclassified systems shall possess a favorably completed DoD National Agency Check with Law and Credit (NACLC). Contractors who require access to Secret material must have, at a minimum, a favorably completed DoD National Agency Check with Law and Credit (NACLC) and final DoD granted Secret security clearance at the time of proposal submission. 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…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .