B_EXHIBIT_PWS-13-R-RK03.pdf

Solicitation No.: N00173-14-R-RK01 Exhibit B

Performance Work Statement (PWS)

Electronic Support Measures (ESM) Branch Digital Signal Processing (DSP) and Software Development Support Services

Vision Statement

1 Introduction

1.1 Mission

1.2 Background

1.3 Scope

2 General Requirements

2.1 Period of Performance

2.2 Non-Personal Services

2.3 Business Relations

2.3.1 Data Rights

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 Management Plan (CMP)

2.4.5 Quality Assurance Surveillance Plan (QASP)

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 Performance Requirements

3.1 RF Analog-to-Digital (ADC) Hardware Integration

3.2 Digital Signal Processing (DSP) Software Development

3.3 Electronic Support (ES) Software Development

3.4 Software Subsystem and System Testing

3.5 Configuration Management and Control

4 Special Requirements

4.1 Security

4.1.1 DD Forms 254

4.1.2 Visitor Group Security Agreement (VGSA)

4.1.3 Identification (ID) Badges and Vehicle Passes

4.1.4 Information Systems Security

4.2 Safety

4.3 Transition

4.4 Government Furnished Materials

5 Deliverables

6 Performance Requirement Summary (PRS)

Performance Work Statement (PWS)

Electronic Support Measures (ESM) Branch Digital Signal Processing (DSP) and Software Development Support Services

Vision Statement

Provide immediate and long-range contributions to the advancement of Navy Electronic Warfare (EW) programs to allow rapid deployment of emerging high-speed analog and digital signal processing components and techniques for use in current Surface Electronic Warfare Improvement Program (SEWIP) efforts and future Electronic Support Measures (ESM) systems.

1 Introduction The Electronic Warfare Support Measures (ESM) Branch at the Naval Research Laboratory (NRL) is engaged in the research and development (R&D) of advanced passive electronic warfare systems. ESM branch employees conduct R&D, prototype design, and operational testing of ESM systems/subsystems associated with all disciplines of modern ESM systems. Research activity areas include:

o Digital Receiver Design and Implementation o Advanced Digital Signal Processing (DSP) o Precision Direction Finding (PDF) Techniques o Precision Passive Geolocation Techniques o Miniaturized Electronic Support (ES) Payloads for Unmanned Platforms o RF Design (Board and System Level) o RF ASIC Design

The ESM Branch at NRL has a long history of directly supporting the warfighter through a combination of long term system developments as well as the delivery of quick reaction capabilities (QRC). The ESM Branch also provides support to the Intelligence Community, particularly in the area of special signal collection.

1.1 Mission

NRL ESM Branch scientists aim to make both immediate and long-range contributions to the advancement of Navy EW programs. These R&D programs apply state-of-the-art techniques and system concepts to optimally achieve program objectives. These development efforts encompass all related phases of engineering including applied research of emerging techniques and components, conceptual design and analysis, detailed hardware/software design, modeling and simulation, and prototype development.

1.2 Background

Utilizing a proprietary development environment from Annapolis Micro Systems, Inc., called CoreFire, the NRL ESM Branch has rapidly prototyped DSP algorithms for EW applications. Over the course of many years, NRL has developed functional code libraries that permit rapid reuse of tried and tested techniques within the CoreFire design environment.

NRL has successfully built and deployed over 15 systems utilizing the CoreFire rapid implementation process.

Annapolis Micro Systems maintains and continually updates products and support for the CoreFire environment, permitting NRL immediate access to emerging and cutting edge technologies. The coupling of software, hardware, and streamlined/dedicated support make CoreFire and Annapolis Micro Systems the development platform of choice for NRL rapid prototyping.

1.3 Scope

The purpose of this contract is to provide personnel to perform research for the ESM Branch in the following areas:

o RF Analog-to-Digital Conversion (ADC) Hardware Integration o Digital Signal Processing (DSP) Software Development o Electronic Support (ES) Software Development o Software Validation and Verification o Configuration Management and Control

DSP is concerned with the practical aspects of representing information bearing signals in digital form, and with using computers or special purpose digital hardware to extract that information (amplitude, RF, BW, PW, FM, and AM) or to transform the signals in useful ways.

Efforts in support of the tasks delineated in Section 3, Performance Requirements, below will be conducted in coordination with Principal Investigator (PI) led research teams that may include Government scientists and other Contractors. In the performance of some of the tasks listed in Section 3, contract personnel may occasionally travel to support system installation, maintenance, or testing aboard Navy platforms. Government assessment of 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 General Requirements The Naval Research Laboratory (NRL) Requirements for On-Site Contractors (ROSC) dated 8 December 2008 provides general instructions for Contractors conducting business at/on NRL property. Compliance with specific paragraphs of the NRL ROSC cited in the Section 2 - General Requirement and Section 4 - Special Requirements is mandatory, other requirements in the NRL ROSC are provided for information purposes only.

2.1 Period of Performance

The effective period of this contract during which delivery orders/task orders may be issued is from date of contract award through three (3) 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 (CO) if any Government requested actions constitute, or are perceived to constitute personal services prior to taking any actions to implement the subject request.

2.3 Business Relations

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

2.3.1 Data Rights

The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract will be Government owned and the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials can not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government will be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

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.

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 PWS 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 in a timely fashion.

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 Management Plan (CMP)

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

The contractor shall submit a Contractor's Management Plan (CMP) defining the contractor's approach to implementing the contract.

The Contractor shall receive the CO’s acceptance in writing prior to implementing any proposed change to his management plan once the CMP has been accepted by the Government.

The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective risk management program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective systems engineering program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective software development program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective configuration management program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective earned value management program to ensure services are performed in accordance with this PWS.

The contractor shall develop and maintain an effective subcontract management program to ensure services are performed in accordance with this PWS.

2.4.5 Quality Assurance Surveillance Plan (QASP)

The Government will evaluate the contractors performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP) provided as an attachment to this proposal. The QASP is focused on what the Government will do to ensure that the contractor has performed in accordance with the performance standards as defined in the QASP. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

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.

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,Performance 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 PWS are defined in the labor category descriptions provided herein.

DSP Hardware/Software Engineer (KEY PERSONNEL)

Education: BS in Electrical Engineering (minimum) from an accredited, 4-yr institution with specialization in digital signal processing software, firmware, and hardware.

Experience: 5 years (minimum) experience in digital signal processing algorithm (including FFT, convolution, digital filter, number system conversions, vector algebra, trigonometry, and other more esoteric DSP techniques) development and implementation of signal acquisition systems based on the Annapolis Microsystems Wildstar Platform, in particular experience using the CoreFire FPGA programming environment. A Master’s Degree in Electrical Engineering can be substituted for 2 years of experience.

Clearance: Current (or eligible for immediate adjudication to) Top Secret (TS)/Special Compartmented Information (SCI)

Senior Software Engineer (KEY PERSONNEL)

Education: MS in Electrical Engineering (minimum) from an accredited, 5-year institution.

Experience: 5 years (minimum) experience in DSP algorithm development in a research and development environment, programming with MATLAB and Visual C++ platforms, implementing graphic user interfaces (GUIs), real-time DSP boards, and analog-to-digital interface hardware, development of system level software for real-time processing of RF emitter (PW measurement, PRF/PRI measurement, Transmit Frequency, RF modulation characteristics, RF scan modulation characteristics, emitter scan rate, etc.)

data. An additional 2 years of experience can be substituted for a MSEE, however, at least a BS degree is mandatory.

Clearance: Current (or eligible for immediate adjudication to) Top Secret (TS)/Special Compartmented Information (SCI)

Software Engineer

Education: BS in Electrical or Computer Engineering (minimum) from an accredited, 4-year institution.

Experience: 2 years experience in DSP algorithm development in a research and development environment, programming with MATLAB and Visual C++ platforms, implementing graphic user interfaces (GUIs), real-time DSP, and analog-to-digital interface hardware.

Clearance: Current (or eligible for immediate adjudication to) Top Secret (TS)/Special Compartmented Information (SCI)

2.7 Location and Hours of Work

Accomplishment of the results contained in this PWS 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 0900. Core hours of work are from 0900 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 government facilities or contractor facilities may be required for conduct of experimental research or attendance at government reviews or scientific meetings and seminars.

The Contractor shall submit all travel requirements (including plans, agenda, itinerary and dates) for pre-approval to the Government and is on a strictly cost reimbursable basis.

The Contractor shall bill costs for travel in accordance with FAR 31.205-46 Travel Costs (subject to local policy & procedures).

3 Performance Requirements The following section specifies the Performance Objectives and Performance Elements for the contract.

DSP applications are ever changing and commercial-off-the-shelf (COTS) products that have proven performance will be used to satisfy these requirements when applicable and within budgetary constraints.

3.1 RF Analog-to-Digital (ADC) Hardware Integration

3.1.1 The Contractor shall conduct research and development to integrate high-speed Analog-to- Digital Converter (ADC) boards with state-of-the art DSP boards for extraction of RF emitter characteristics from a dense analog RF signal environment.

Data transfer rates under study exceed 100 Gbps and may be implemented in numerous bus technologies including RACEway, PCI, Compact-PCI, PCIExpress, PXI. VME, VXI, VPX and other state-of-the art serial electronic or optical bus technologies. DSP processor boards under investigation include Annapolis Micro System's Wildstar platform as well as other COTS products with similar performance.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 60 days after the end of an annual period of performance

d) STD: Comprehensive AQL: Addresses key issues associated with integrating high-speed ADC boards to state-of-the DSP boards.

Deliverables

A001 Monthly Progress and Status Report - STDs a, b A002 Contractor Summary Technical Report – STDs c, d

3.1.2 The Contractor shall use VHDL and Verilog programming environments to program firmware for implementing ADC to DSP board hardware interfaces.

Performance Standards

a) STD: Timely AQL: 30 days after completion of verification and validation of firmware source code

b) STD: Comprehensive AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

Deliverables A003 Version Description Document

3.2 Digital Signal Processing (DSP) Software Development

3.2.1 The Contractor shall conduct research and development to implement DSP software techniques in state-of-the-art FPGA hardware for identifying specific emitter characteristics in a high-density RF signal environment.

Techniques to be implemented include Fast Fourier Transforms (FFTs), convolution, digital filters, number system conversions, vector algebra, trigonometry, and other more esoteric, mathematically based algorithms that take advantage of the increased throughput of the integrated FPGA based DSP boards.

Emitter characteristics to be determined include technical parameters of the emitter signal (e.g. Pulse Width, PRF, PRI, Frequency, Modulation Type, Scan Rate, Antenna Beam Width, etc.) as well as positional or geo-location parameters (e.g. angle of arrival, line of bearing, depression angle, etc.).

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 30 days after completion of verification and validation of a specific algorithm source code

d) STD: Comprehensive AQL: Addresses key issues associated with developing and implementing a specific DSP software technique/algorithm in state-of-the art FPGAs.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A005 Technical Studies Reports – STD’s c, d

3.2.2 The Contractor shall use Annapolis Micro System's CoreFire software development environment to develop and optimize FPGA based DSP algorithms for use with Annapolis Micro System's Windstar hardware platform.

Performance Standards

a) STD: Timely AQL: 30 days after completion of verification and validation of a specific algorithm source code

b) STD: Comprehensive AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

Deliverables A003 Version Description Document

3.3 Electronic Support (ES) Software Development

Electronic support involves actions taken to search for, intercept, identify and locate radiated electromagnetic energy for the purpose of immediate threat recognition. It provides a source of information required for immediate decisions involving electronic countermeasures (ECM), electronic countercountermeasures (ECCM) and other tactical actions such as avoidance, targeting and homing.

Some initial algorithm development under this task may be accomplished using test code developed on a desktop workstation or on any of several commercially available mathematical packages such as The Mathworks product, MatLab. Integration of third party mathematics packages may be required as part of this task.

In addition to advanced algorithm development for automatic analysis techniques and real-time process control, this task includes development of custom software to be used for engineering development integration and test purposes but not necessarily delivered in production versions of these EW systems.

3.3.1 The Contractor shall develop electronic support software to perform automated processing and analysis of emitter data provided by state-of-the-art DSP boards for assisting shipboard operators in identifying and locating threat emitters.

The current and projected emitter environment requires emphasis on advanced EW support systems that can simultaneously detect and process a large number of emitters. State-of-the-art DSP boards being developed for the Shipboard Electronic Warfare Improvement Program (SEWIP) provide a significant upgrade in the amount of emitter data that can be obtained from the threat environment and, hence, requires new capabilities in the electronic support software to handle the increased throughput.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 60 days after the end of an annual period of performance

d) STD: Comprehensive AQL: Addresses key issues associated with processing and analysis of increased volume of emitter data provided by state-of-the-art DSP boards.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A002 Contractor Summary Technical Report – STD’s a, b

3.3.2 The Contractor shall develop and integrate GUI software to provide real-time, interactive process control, and display of threat emitter data for review, analysis, and response by a EW system operator.

In addition to the automated functions of identifying and locating threat emitters, electronic support software provides a Graphical User Interface (GUI) to display emitter data and allow operator interaction with processing routines to assist an operator to make decisions on how and when to respond to threats.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 60 days after the completion of a specific system integration effort.

d) STD: Comprehensive AQL: Fully describes architecture and implementation of integration of subject Graphical User Interface (GUI) to front-end electronics support hardware and software.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A006 Software Design Description – STD’s c, d

3.4 Software Subsystem and System Testing

In specifying this task the following definitions will be used:

Validation: The process of evaluating software to determine whether the systems and subsystems satisfy the conditions imposed by the government or research sponsor i.e. does it perform as required in its operational environment.

Verification: The process of evaluating software to determine whether it satisfies the specified requirements i.e. was it built correctly.

3.4.1 The Contractor shall conduct software tests to validate that software subsystems and systems meet their software specifications in the environment for which the systems/subsystems were designed to operate.

Testing in the operational environment requires contractor personnel to travel to NRL offsite locations with the NRL developers of the systems/subsystems. Test documentation forms will be provided by the government or research sponsors of the specific systems/subsystems under test.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 30 days after completion of a specific test

d) STD: Identify test engineer conducting the test

e) STD: Identify requirement to be satisfied

f) STD: Identify the module(s) that satisfy the requirement

g) STD: Identify any discrepancies

h) STD: Timely AQL: 5 days after completion of test

i) STD: Comprehensive AQL: Provides all information needed to describe software discrepancies, if they occur during field testing.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A007 Software Test Report – STD’s c, d, e, f, g A008 Software Discrepancy Report – STD’s h, i

3.4.2 The Contractor shall coordinate with NRL developers in developing software modifications to systems and subsystems for resolving software discrepancy reports (SDRs) resulting from field testing.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Timely AQL: 30 days after completion of verification and validation software fix

d) STD: Completeness AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A003 Version Description Document – STD’s c, d

3.4.3 The Contractor shall develop automated test software for verifying that delivered software baselines perform as specified.

It is intended that the test software developed under this task (once validated) be maintained with the relevant software baseline in the CMS described in task 3.5.1 below.

Performance Standards

a) STD: Timely AQL: 5 days after last day of month in which work was accomplished

b) STD: Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) STD: Automatically generates a Verification Report

d) STD: Identifies the System/Subsystem being verified

e) STD: Identifies baseline specification requirements satisfied

f) STD: Identifies any errors

g) STD: Timely AQL: 30 days after completion of verification and validation automatic test software

h) STD: Completeness AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

Deliverables A001 Monthly Progress and Status Report – STD’s a, b A003 Version Description Document – STD – g, h A004 Verification Report – STD’s c, d, e, f

3.5 Configuration Management and Control

3.5.1 The Contractor shall use a Government provided automated configuration management system (CMS) to document new and current software baselines and modifications thereto for all firmware and software development and testing tasks.

The CMS provides a repository of all current software baselines, new software developments, baseline upgrades, maintenance patches, test results, Software Discrepancy Report (SDR) fixes, and generates automated reports necessary to document the results of all configuration management and control efforts.

Performance Standards

a) STD: Timely AQL: Agreed upon timeline determined by the COR

b) STD: Baseline all new developed software

c) STD: Release software baseline upgrades

d) STD: Release maintenance patches e.g. when change does not required baseline update

e) STD: Release SDR fixes

Deliverables A001 Monthly Progress and Status Report

4 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

US Intelligence collection methods, analysis, sharing, cataloging and dissemination methods are sensitive and frequently require knowledge or access to systems and data operating at the SCI classification level.

This work typically requires SI/TK caveats.

All Contractor personnel shall possess a favorably completed DoD investigation and a final DoD granted Top Secret security clearance with eligibility of SCI access at time of proposal submission. Detailed security requirements are delineated in the issued DD 254s 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.

4.1.1 DD Forms 254

The Contractor shall be granted access to classified information necessary for performance of this contract upon contract award as specified in the basic DD Form 254.

4.1.2 Visitor Group Security Agreement (VGSA)

The VGSA outlines responsibilities in the following areas: Contractor security supervision; Standard Practice Procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection; protection of government resources; DD Forms 254; periodic security reviews; and other responsibilities, as required.

The Contractor shall sign a Contractor Visitor Group Security Agreement to protect classified information involved in performance under this contract.

4.1.3 Identification (ID) Badges and Vehicle Passes

The Government will issue ID badges and vehicle passes to Contractor personnel working at NRL in accordance with the requirements of Paragraph 1(b) BADGES AND VEHICLE PASSES of the NRL ROSC. A favorable trustworthiness determination is required in order for nominated contractor personnel to be granted access to NRL facilities and issued an NRL badge. NRL issued Contractor badges will be worn and readily visible at all times while contractor personnel are on NRL facilities.

The Contractor shall provide all requested information required to facilitate the use and possession of badges and vehicle passes.

The Contractor shall ensure the immediately return all ID badges issued to Contractor employees under any of the following conditions: completion of contract, relocation or termination of an employee, or upon request of the Contracting Officer or Contracting Officer's Representative.

4.1.4 Information Systems Security

The Contractor shall perform work in accordance with all NRL security policies and procedures, with specific regard to information systems security and compliance.

4.2 Safety

RESERVED

4.3 Transition

The Contractor shall follow the transition plan submitted as part of the Contractor's Management Plan (CMP) and keep the Government fully informed of status throughout the transition period.

This plan describes the Contractor's transition into service at the beginning of the contract, and how work will be transitioned to a different contractor or contract vehicle at the end of the contract. It includes a staffing and training plan for new personnel and plans for the transfer of work control and information, addressing any security issues, transfer and accountability of GFE, inspections and acceptance, and delineates the method for processing and assigning tasks during the phase-in/phase-out periods. The plan addresses how the Contractor will implement adequate measures to coordinate communications with the incumbent contractor and NRL staff in order to ensure uninterrupted workflow and minimal mission impact during the transition process.

4.4 Government Furnished Materials

The Contractor shall perform this effort at the U.S. Naval Research Laboratory, Washington D.C.

government furnished facilities.

The Contractor shall perform all work on only NRL GFE in accordance with NRL security policies and procedures.

5 Deliverables The contractor shall provide deliverables with the schedule and format as described in section 3.0 of this contract and outlined in the CDRL's listed below.

IDENTIFIER NAME DESCRIPTION

A001 Monthly Progress and Status Report

A002 Contractor Summary Technical Report

A003 Version Description Document

A004 Verification Report

A005 Technical Studies Reports

A006 Software Design Description

A007 Software Test Report

A008 Software Discrepancy Report

Performance Requirement Summary (PRS)

STATEMENTS STANDARDS/AQLS

3.1 RF Analog-to-Digital (ADC)

Hardware Integration

3.1.1 The Contractor shall conduct

research and development to integrate high-speed Analog-to-Digital Converter (ADC) boards with state-of-the art DSP boards for extraction of RF emitter characteristics from a dense analog RF signal environment.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 60 days after the end of an annual period of performance

d) Comprehensive AQL: Addresses key issues associated with integrating high-speed ADC boards to state-of-the DSP boards.

3.1.2 The Contractor shall use

VHDL and Verilog programming environments to program firmware for implementing ADC to DSP board hardware interfaces.

a) Timely AQL: 30 days after completion of verification and validation of firmware source code

b) Comprehensive AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

3.2 Digital Signal Processing

(DSP) Software Development

3.2.1 The Contractor shall conduct

research and development to implement DSP software techniques in state-of-the-art FPGA hardware for identifying specific emitter characteristics in a high-density RF signal environment.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 30 days after completion of verification and validation of a specific algorithm source code

d) Comprehensive AQL: Addresses key issues associated with developing and implementing a specific DSP software technique/algorithm in state-of-the art FPGAs.

3.2.2 The Contractor shall use

Annapolis Micro System's

a) Timely AQL: 30 days after completion of verification and validation

CoreFire software development environment to develop and optimize FPGA based DSP algorithms for use with Annapolis Micro System's Windstar hardware platform.

of a specific algorithm source code

b) Comprehensive AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

3.3 Electronic Support (ES)

Software Development

3.3.1 The Contractor shall develop

electronic support software to perform automated processing and analysis of emitter data provided by state-of-the-art DSP boards for assisting shipboard operators in identifying and locating threat emitters.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 60 days after the end of an annual period of performance

d) Comprehensive AQL: Addresses key issues associated with processing and analysis of increased volume of emitter data provided by state-of-the-art DSP boards.

3.3.2 The Contractor shall develop

and integrate GUI software to provide real-time, interactive process control, and display of threat emitter data for review, analysis, and response by a EW system operator.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 60 days after the completion of a specific system integration effort.

d) Comprehensive AQL: Fully describes architecture and implementation of integration of subject Graphical User Interface (GUI) to front-end electronics support hardware and software.

3.4 Software Subsystem and

System Testing

3.4.1 The Contractor shall conduct

software tests to validate that software subsystems and

a) Timely AQL: 5 days after last day of month in which work was systems meet their software specifications in the environment for which the systems/subsystems were designed to operate.

accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 30 days after completion of a specific test

d) Identify test engineer conducting the test

e) Identify requirement to be satisfied

f) Identify the module(s) that satisfy the requirement

g) Identify any discrepancies

h) Timely AQL: 5 days after completion of test

i) Comprehensive AQL: Provides all information needed to describe software discrepancies, if they occur during field testing.

3.4.2 The Contractor shall

coordinate with NRL developers in developing software modifications to systems and subsystems for resolving software discrepancy reports (SDRs) resulting from field testing.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Timely AQL: 30 days after completion of verification and validation software fix

d) Completeness AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

3.4.3 The Contractor shall develop

automated test software for verifying that delivered software baselines perform as specified.

a) Timely AQL: 5 days after last day of month in which work was accomplished

b) Comprehensive AQL: Include: hours expended on tasks, resources assigned to tasks, meeting/reviews attended, problems or issues encountered

c) Automatically generates a Verification Report

d) Identifies the System/Subsystem being verified

e) Identifies baseline specification requirements satisfied

f) Identifies any errors

g) Timely AQL: 30 days after completion of verification and validation automatic test software

h) Completeness AQL: Meets 100% of the requirements listed in the VDD Guide data description provided in the DD1423 Contract Requirements Data List (CDRL) attached.

3.5 Configuration Management

and Control

3.5.1 The Contractor shall use a

Government provided automated configuration management system (CMS) to document new and current software baselines and modifications thereto for all firmware and software development and testing tasks.

a) Timely AQL: Agreed upon timeline determined by the COR

b) Baseline all new developed software

c) Release software baseline upgrades

d) Release maintenance patches e.g. when change does not required baseline update

e) Release SDR fixes