Draft Base IDIQ SOW.pdf

Naval Research Laboratory 4555 Overlook Avenue SW

Washington, DC. 20735-5329 Code 5770

Tactical Combat and Electronic Warfare Systems Research and Development

Statement of Work (SOW)

8 MAY 2024

N0017324RGG04

Contents

1.0. Introduction

1.1. Mission

1.2. Background

1.3. Scope

2.0. General Requirements

2.1 Non-Personal Services

2.2 Contract Overview

2.2.1 Contract Management

2.2.2 Personnel Administration

2.2.3 Contract Administration

2.3 Contractor Furnished Equipment, Materials, Subcontracts and Supplies

2.4 Contractor Personnel, Disciplines, and Specialties

2.5 Location and Hours of Work

2.6 Travel / Temporary Duty (TDY)

3.0. Technical Requirements

3.1 Systems Engineering (Task 1)

3.2 Hardware Development (Task 2)

3.3 Fleet/Live Fire Events (Task 3)

3.4 Computer Modeling and Simulations (Task 4)

3.5 Infrastructure (Task 5)

3.6 Data Collection (Task 6)

3.7 Technical Support (Task 7)

4.0. Special Requirements

4.1 Security

4.2 Government Furnished Property/Equipment

5.0. Contract Data Requirements List (CDRL)

6.0. Acronyms

1.0. Introduction

The Naval Research Laboratory (NRL) Tactical Electronic Warfare Division (TEWD) is seeking contractor assistance in a variety of disciplines related to tactical Electronic Warfare (EW) and Combat Systems (CS) Research and Development (R&D). The areas of interest include systems engineering, combat systems analysis, Electronic Attack (EA) and Electronic Support (ES) systems performance, EW tactics development, test and evaluation (T&E), data collection, and computer modeling and simulation.

1.1. Mission

The mission of the Electronic Warfare Modeling and Simulation (EWM&S) Branch is to develop and utilize simulation and modeling tools for the effectiveness evaluation of present, proposed, and future EW concepts, systems, and configurations for aircraft and ship systems.

TEWD’s work is conducted across several functional areas to include: collection and formulation of basic requirements and determination of EW effectiveness criteria; survey of EW candidate systems for in-service capabilities, state-of-the-art, and R&D technology; development of tools required to conduct effectiveness evaluations; systematic application of tools and procedures in the evaluation of EW systems; and reporting of individual candidate evaluation results to both identify R&D requirements and to permit comparison with other candidates.

a. Electronic Warfare scientists aim to make 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.

b. Testbed (TB) scientists continue Modeling and Simulation (M&S) development and performance analysis of the Integrated Warfare System (IWS) models, which are designed to be an end to end integration of the CS system of systems. The purpose of the TB is to maximize the use of tactical code-based models in conjunction with physics-based models to represent at-sea performance. The TB will be developed to support specific use cases to include Developmental Testing (DT) and Operational Test (OT) of CS Baselines (BL) being fielded in the United States Navy (USN). Additionally, the TB will support the system engineering feedback loop to provide root cause analysis to full life cycle requirements.

c. Application Development scientists will continue to develop multiple M&S tools to include Builder, Simulation Display (SIMDIS), and related applications. Interactive Scenario Builder is a software tool that provides two-dimensional (2-D) and three-dimensional (3-D) interactive graphical display of Radio Frequency (RF), Electro-Optic (EO), and InfraRed (IR) data. Builder has evolved to support missile models with a premier government off the shelf (GOTS) product for Electromagnetic (EM) situational awareness, pre-mission planning, and post event reconstruction. SIMDIS is a certified and accredited tool that provides support for high-fidelity analysis and display of test and training mission data to a growing user base of more than 40,000 users. This highly specialized visualization tool provides unique capability for 2-D and 3-D interactive data analysis and display. The SIMDIS toolset is designed for use on commercial Windows and Linux hardware and provides identical execution and "look and feel" for all supported platforms.

d. NRL is the principal investigator for a series of R&D programs directly related to Electronic Warfare System (EWS) development and improvement to include AN/SLQ-62 system as the In-Service Engineering Agent (ISEA). In support of these efforts, these programs support and assist with engineering and prototype development, program planning, system engineering, development, implementation, and execution; test and evaluation; shipboard installation planning and execution; fielding and maintenance;

program documentation; and engineering integration in support of system development and at sea testing. The engineering and programmatic personnel require extensive experience in R&D project execution, technology transition from lab to operations, advanced technology development, especially experience at sea, and significant shipboard management experience.

1.2. Background

The EW Branch has developed advanced EW modeling, simulation, and visualization capabilities to support NRL R&D, as well as EW Capabilities for Naval Sea Systems. Modeling work focuses on creating software characterizations of existing and developmental EW systems and subsystems. These models are used in concert with simulated EW environments to characterize system and subsystem performance, capabilities, and limitations. Research in the Branch is expected to encompass simulated environments with hardware in the loop, as well as distributed simulations employing the High-Level Architecture Run-Time Infrastructure (HLA/RTI). The Branch also has Visualization and Systems Integration Sections that design, develop, and maintain 2-D and 3-D interactive display software as a apart of the SIMDIS toolset.

The software provides real-time situational awareness of military operations and test and training exercises as well as pre-exercise training, post-exercise debriefing, and visualization of simulation data.

a. Contractor support will concentrate on theoretical research, systems R&D, M&S, and T&E relating to the interactions of various USN platforms, weapons, sensors, and electronic systems.

The selected contractor will provide research, engineering, and execution of M&S in support of NAVSEA’s Program Executive Office (PEO) for IWS Enterprise Modeling, Simulation, and Analysis. This work includes engineering effort to architect, integrate, test and operate a system-of-systems simulation federation on behalf of the PEO IWS TB. The contractor will be responsible for system engineering of the testbeds, and developing and supporting HLA technologies in support of USN combat system analysis through the federation of multiple complex and high-fidelity models, simulators, and tactical hardware and software, including process definition, documentation, and multi-lab team coordination. Engineering, development, and documentation of individual Probability of Raid annihilation (PRA) Testbed simulations are also required.

b. The Tactical Electronic Warfare Special Projects Group continues to be tasked by the Navy to develop, field, and support several EW systems including the AN/SLQ-62 and the Scaled On-Board Electronic Attack (SOEA). NRL has ongoing programs designed to improve and integrate new capabilities into the AN/SLQ-62 platform. These programs are aimed at improving the capabilities of the currently fielded units as well as the new units via technology insertions. The Contractor will provide engineering and technical work to support the development of advanced SLQ-62, Scaled Onboard Electronic Attack (SOEA), and other emerging EW capabilities. Additionally, Code 5775 plans and executes numerous at-sea test events each year. Many of these events require testing newly developed EW technology at sea.

This often requires industrial, network, and software modifications to the host ships. The contractor will execute these ship changes in accordance with established Navy process (IA, SCDs, SIDS, Combat System Element Authorizations, AI-SIT, etc.).

c. NRL develops and maintains computer programs used to evaluate the effectiveness of the EA and ES assets. These programs are used to predict changes in Navy system performance due to the meteorological conditions. NRL performs at sea testing and data collection to validate the performance of and improve these computer programs. The Contractor shall provide subject matter expertise in the execution of Naval Meteorology and Oceanography Command (METOC) data gathering events and analysis of the results.

d. The EW M&S Branch has been tasked by the NAVSEA PEO IWS 1.0 and 2.0 to develop and host efforts for the M&S TBs. An integrated Combat System Testbed (CSTB), developed for IWS 1.0, executes high-fidelity representations of hard kill and EW systems on board naval ships, and directly supports T&E for Aegis BL to include DT and OT. As part of this effort, PEO IWS 1.0 requires comparison of live fire test data with the use of pre-live fire and post-live fire analysis in IWS CSTB. The Enterprise Testbed (ETB), also developed for IWS 1.0, similarly executes high-fidelity representations of hard kill and electronic warfare systems on board naval ships, and directly supports T&E for SSDS based CS ships to include DT and OT. The Electronic Warfare Testbed (EWTB), developed for IWS 2.0, executes high-fidelity representations of electronic warfare systems on board naval ships, and directly supports T&E for the Surface EW Improvement Program (SEWIP) Block 3 system to include DT and OT. TB analysis requires the transfer of data and distribution of simulations across the IWS network. To support the analysis and development of IWS TBs, an interface with other testbed federates in a HLA distributed simulation is required. Support is also sought for systems engineering tasks in defining simulation requirements, establishing standards, providing support for the verification and validation of the TB, designing test plans, and other related systems engineering tasks and integration and simulation network maintenance, to include meeting Information Assurance (IA) requirements, software tools development, operation of the testbeds, and quick look analysis following the completion of simulation runs.

1.3. Scope

The scope of this contract covers a broad range of R&D needed to support TEWD in a variety of disciplines related to EW and computer M&S applications. The Contractor will be required to support unclassified and classified tasks up to and including Top Secret/Sensitive Compartmented Information (TS/SCI). The contractor will provide support to fielded systems and software, R&D, analysis, systems engineering services, and computer programming.

a. The T&E community relies heavily on M&S to aid in systems design and performance analysis. The actions required to support TEWD are focused on the execution of the IWS testbeds in the designated computer environments. The Contractor will be required to support Development and Operational Testing to include verification and validation of testbeds elements. The Contractor will also be required to support Request For Analysis (RFA). RFA is the execution of testbed runs to conduct analysis for Predictive and Post Live Fire comparisons.

b. The scope for this contract will cover a broad range of development processes needed to support Testbed section in a variety of disciplines to development the IWS testbeds in the designated computer environments and support PEO IWS 1.0 M&S Strategy. The Contractor will be required to support element and federation development, integration, testing, verification, validation, and accreditation.

c. TEWD requires support in the development and utilization of M&S tools to evaluate the effectiveness of present and future EW concepts, systems, and configurations for U.S.

aircraft and ships. TEWD requires support that spans the spectrum of R&D for the advancement of Navy EW programs including: applied research of emerging techniques and components, conceptual design and analysis, detailed hardware/software design, M&S, and prototype development. Contractor support will concentrate on theoretical research, systems R&D, M&S, and T&E relating to the interactions of various USN platforms, weapons, sensors, and electronic systems.

2.0. General Requirements

NRL's “Requirements for On-Site Contractors” document provides general instructions for contractors conducting business at/on NRL property. This document is provided as an attachment to the solicitation and will be incorporated into the contract.

2.1 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 37.104, Personal Services Contracting.

The contractor shall notify the KO if any Government requested actions constitute, or are perceived to constitute personal services.

2.2 Contract Overview

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

2.2.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.2.2 Personnel Administration

The contractor shall ensure employees have a suitable office workspace during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions, or when access to Government offices is impractical. The purpose of this workspace is to provide employees the option of working during these times.

The contractor shall complete all Government mandated initial and refresher training. A list of this training will be provided at time of contract award.

The contractor shall make necessary travel arrangements for employees.

2.2.3 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively communicate with the Government during contract administration.

The contractor shall respond to Government requests for contractual actions within five (5) workdays.

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

2.3 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 ‘Technical Requirements,’ below.

The contractor shall be responsible for any subcontract management necessary for performing efforts described in Section 3.0, ‘Technical Requirements’, below.

2.4 Contractor Personnel, Disciplines, and Specialties

The minimum education, training, clearances, and experience required by contractor personnel to perform support tasks identified in this SOW are defined in the “Personnel Qualifications” document provided as an attachment to the solicitation.

2.5 Location and Hours of Work

All or a portion of the effort under this contract will be performed on a Government installation.

The contractor shall perform work at NRL within the normal work hours unless differing hours are specified by the COR. The contractor is not required to maintain the same hours as

Government employees; however, contractor employees performing working at NRL must work during the normal workweek. Contractor personnel working off-site must remain reachable (e.g.

phone, email, Microsoft Teams, etc.) by Government personnel. In the advent of severe weather conditions, the contractor should refer to the top banner of the NRL website for the NRL DC operating status or refer to the Office of Personnel Management website for the operating status of the U.S. Government offices in Washington, DC area and for additional information. In the event that the Government facility where the contractor normally works is closed, the contractor should not report to work until the facility reopens.

2.6 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) in writing for pre-approval to the Government COR. Travel 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) and DoD’s Joint Travel Regulations.

3.0. Technical Requirements

The following section specifies the Technical Requirements for the contract and is divided into seven task areas.

3.1 Systems Engineering (Task 1)

a. The Contractor shall provide systems engineering and management of the M&S TB including technical leadership for the systems engineering, infrastructure, and integration of M&S efforts.

b. The Contractor shall perform technical investigation of M&S issues including architecture, application of technical standards, middleware and support tools, runtime performance, configuration, visualization, security classification, common scenarios definition, and re-use of TB simulations for other IWS and Ship Class applications.

c. The Contractor shall participate in Design activities and meetings, M&S Integrated Product Teams (IPT) and associated working group activities, technical design review and program reviews, and the Configuration Management Board.

d. The Contractor shall manage the configuration baseline for M&S by adhering to industry accepted configuration management processes.

e. The Contractor shall establish documentation requirements for the federation based on M&S instructions and certify documentation adheres to the requirements (CDRL A011).

f. The Contractor shall develop and document the system engineering products including:

Master Requirements; Capabilities Matrix; Federation Object Model; Federation

Agreements Document; Integration and Configuration Management Master Plan; Model Description Documentation; and Risk tracking (CDRL A015).

g. The Contractor shall author white papers and publish peer-reviewed technical papers

(CDRL A002).

h. The Contractor shall conduct research into, and develop for publication, open technical standards supporting distributed simulation systems engineering.

i. The Contractor shall coordinate M&S use between constituent systems programs to ensure that Program Offices are kept appraised of results from simulation studies and to gain concurrence for publication of results.

j. The Contractor shall participate in the integration and continued development that will include M&S IPT and associated focus group meetings (e.g. Threat Representation Working Group meetings, M&S Working Group meetings, and Scenario Working Group meetings).

k. The Contractor shall provide input to M&S standards and guidelines.

3.2 Hardware Development (Task 2)

a. In support of the AN/SLQ-62 (both the fielded version and research versions of the system), SOEA, and other emerging EW hardware programs:

1. The Contractor shall manage the logistical train, including the spare parts inventory and the fabrication/deployment/repair status of all inbound and outbound hardware as they move about the globe (CDRL A003).

2. The Contractor shall also prepare and maintain the flyaway repair kits in support of hardware units under test.

3. The Contractor shall be responsible for coordinating the appropriate ship checks and design updates with the relevant agencies, including the related Program Offices and the class planning yard.

4. The Contractor will perform crew training events on the deployed ships. This task will involve riding ships at sea.

5. The Contractor shall provide engineering and technical support to the development of advanced hardware capabilities. (CDRL A016).

6. The Contractor will provide program support to NRL for USN Fleet exercises include assistance in support NRL with execution of programmatic tasks (CDRL A016).

b. In support of ES system development and support:

1. The Contractor shall design, build, and integrate the digital, analog, RF hardware, and software components required for prototype Electronic Support Measures (ESM) and Electronic Support Measures Environment Simulation (ESMES) systems. This may involve the following engineering tasks: system architecture design; hardware and software development; printed circuit board design, layout, fabrication, and testing; system level integration and testing. Detailed digital designs will encompass the field of signal processing. They will likely commence at the output of an A/D converter, then process through logic circuitry and likely encompass the areas of Field Programmable Gate Array (FPGA) and Digital Signal Processor (DSP) programming. Analog circuitry will typically involve signal conditioning, filtering, amplification, and A/D conversation. RF circuitry involves signal reception, amplification, filtering, and frequency conversion (mixing - typically down conversion to an intermediate or baseband frequency).

The task will require the use of the C (or C++) programming language to support the hardware being built and tested. The contractor will be expected to gain a thorough understanding of existing and developmental ESM receiver and pulse processing systems and use that knowledge to create and maintain hardware as required by Branch employees (CDRL A016).

2. ES System Engineering Support: The Contractor shall maintain, test, evaluate, calibrate, repair and improve existing NRL ESM systems. NRL ESM systems are composed of antenna systems, RF components, analog conditioning circuitry, analog to digital conversion, digital signal processors, embedded personal computers (EPC), graphical user interfaces, and system interfaces (serial, Ethernet, and other communications protocols). These subsystems contain highly sophisticated digital, analog, and RF collection circuitry. Digital circuitry includes FPGA devices, integrated circuits, programmable logic devices, digital signal processors, and microprocessors. The analog circuitry will be mostly composed of high-speed operational amplifiers and digital-to-analog converters. RF components typically used are RF tuners, digitally controlled RF switches, attenuators, and RF filters.

3. The Contractor shall provide analysis for current and projected Threat Emitter signal Environments (CDRL A002).

4. The Contractor shall develop system technical requirements for prototype ESM, EW, and ESMES systems, to include RF, analog and digital signal processing hardware, firmware and software designs.

c. In support of the Hardware Accelerated Threat Simulations (HATS), the following tasks include:

1. The Contractor shall provide engineering and technical support to the development of hardware capabilities. The Contractor shall have experience with the development, integration, and design of FPGA-based systems.

2. The Contractor shall develop signal processing software in C/C++ that integrates with the FPGA hardware system (CDRL A010).

3.3 Fleet/Live Fire Events (Task 3)

a. The Contractor shall support execution of large-scale exercises. Some typical elements involved in executing these events include, but are not limited to:

1. Integrate into the fleet planning process to ensure NRL and other performers can execute the defined at sea objectives. This includes attending planning conferences, attending scheduling meetings, and answering data calls, each with significant interaction with fleet planners.

2. Combat System Certification. The Contractor will support the certification process associated with connecting to a ship’s combat system, from concept development through the final certification issuance. (CDRL A019)

3. Mission Readiness Assessment (MRA). The Contractor will support all aspects of testing associated with the AEGIS MRA process, through issuance of the MRA System Engineering concurrence to test.

4. Combat System Element Certification. The Contractor will support the certification process associated with connecting to a ship’s combat system element, from concept development through the final certification issuance.

(CDRL A019)

5. Information Assurance Interim Authority to Test (IATT), both GENSER and SCI.

The Contractor will support implementing and testing information assurance requirements in support of issuance of an IATT or Information Assurance Interim Authority to Operate (IATO) (as appropriate) for the systems under test. This effort will include both the RMF process for GENSER systems and the NAVINTEL process for SCI systems.

6. NAVSEA Ship Change Document process and approval. The Contractor will ensure that the appropriate NAVSEA process is followed to approve the temporary installations associated with the shipboard demonstrations. The

Contractor may be required to generate A through O Message and Type Commander approval messages for at sea testing.

7. Coordinate with the Government performers and develop a workable installation and at sea test plan to achieve demonstration objectives.

8. Determine the sensors/data required to conduct the demonstration and develop the interfaces to the systems. The Contractor will write the demonstration interface control documents (ICD), which will include interconnect diagrams that document the defined systems (CDRL A014).

9. Manage all logistics issues related to the use of the platform(s), including support for installation requirements and industrial work.

10. Perform checks on the designated test platform(s) and develop the plan to integrate equipment on board the platform. The plan will include the placement of the equipment on the ship, the procedure to move the equipment into position, the procedure to connect power and communications to the equipment, the procedure to secure the equipment, which may include welding, and the procedure to return the ship to its original state.

11. Execute land-based testing to provide assurance that hardware and software is ready prior to integration onto the platform. Develop test plans and write reports as needed to assist in determining readiness to test at sea (CDRL A002).

12. Execute the demo at sea with an appropriate number of ship riders as directed by the government. The Contractor may serve as the at sea test director.

13. The Contractor shall provide an exercise analysis report (CDRL A017) and completed exercise report (CDRL A018).

b. The Contractor shall enable execution of medium scale exercises. In general, medium scale exercise support will entail less certification events, or may include very limited certification, and will typically not require large-scale industrial work to achieve the exercise results. Some typical elements involved in executing these events include, but are not limited to:

1. Integrate into the fleet planning process to ensure NRL and other performers can execute the defined at sea objectives. This includes attending planning conferences, attending scheduling meetings, and answering data calls, each with significant interaction with fleet planners.

2. Combat System Certification. Medium scale events may include connecting to ship’s systems, but typically do not involve using advanced engineering builds or modified ship’s software, therefore the certification requirements are less. The Contractor will support the certification process associated with connecting to a ship’s combat system, from concept development through the final certification issuance. The Contractor should have significant experience with this process, including demonstrated success getting changes approved for testing.

3. MRA. The Contractor will support all aspects of testing associated with the

AEGIS MRA process, through issuance of the MRA System Engineering concurrence to test (CDRL A019).

4. Combat System Element Certification. The Contractor will support the certification process associated with connecting to a ship’s combat system element, from concept development through the final certification issuance.

(CDRL A019)

5. IATT, both GENSER and SCI. The Contractor will support implementing and testing information assurance requirements in support of issuance of an IATT or IATO (as appropriate) for the systems under test. This effort will include both the RMF process for GENSER systems and the NAVINTEL process for SCI systems.

(CDRL A019).

6. NAVSEA Ship Change Document process and approval. The Contractor will ensure that the appropriate NAVSEA process is followed to approve the temporary installations associated with the shipboard demos. The Contractor may be required to generate A through O Message and Type Commander approval messages for at sea testing.

8. Determine the sensors/data required to conduct the demonstration and develop the interfaces to the systems. The Contractor will write the demonstration Interface Control Document (ICD), which will include interconnect diagrams that document the defined systems.

9. Manage all logistics issues related to the use of the platform(s), including support for installation requirements and industrial work.

10. Perform checks on the designated test platform(s) and develop the plan to the equipment on the ship, the procedure to move the equipment into position, the procedure to connect power and communications to the equipment, the procedure

11. Execute land-based testing to provide assurance that hardware and software is as needed to assist in determining readiness to test at sea. Execute the demo at sea with an appropriate number of ship riders as directed by the government.

Document the results as appropriate.

c. The Contractor shall perform at least one small scale exercise during the period of performance. This involves coordinating a data collection test plan, getting approval to ride the ship, and riding the ship to collect the data. There are typically no or limited installation and integration requirements. In general, small scale exercise execution will entail limited or no certification events. Due to the nature of the work and the systems involved, experience with the AN/SLQ-32(V)6 is required. Some typical elements involved in executing these events include, but are not limited to:

1. Coordinate with fleet planners to identify the appropriate ships to ride.

2. Identify data collection requirements, and the appropriate data collection systems to be used.

3. Coordinate and develop the test plan.

4. Identify ship riders and coordinate with fleet staff to approve the ride.

5. Interface with the certification and accreditation organizations to ensure they are aware of the test.

6. NAVSEA Ship Change Document process and approval. When needed the Contractor will ensure that the appropriate NAVSEA process is followed to approve the temporary installations associated with the shipboard demos

8. Manage all logistics issues related to the use of the platform(s), including support for embarkation and debarkation of riders and equipment.

9. Perform checks on the designated test platform(s) and develop the plan to the equipment on the ship, the procedure to move the equipment into position, the procedure to connect power and communications to the equipment, the procedure

10. Execute land-based testing to provide assurance that hardware and software is as needed to assist in determining readiness to test at sea.

11. Execute the ride at sea with an appropriate number of ship riders as directed by the Government. During this event, the contractor will lead teams at sea, interface with ship’s force, and execute test plans at sea.

3.4 Computer Modeling and Simulations (Task 4)

a. Contractors shall manufacture source code to support routing of data packets for recording various system outputs. Contractors will utilize legacy capability to integrate into the designated operating system to support data collection.

b. The Contractor shall perform representative analysis tasks with the IWS testbeds to test the models’ performance against live recorded data to include Pre-Test and Post-Test analysis. The purpose of testing is to shape future development and operational testing of fielded naval warfare system (CDRL A007).

c. The Contractor shall perform analysis of testbeds performance, which will occur at

Government and/or Contractor sites during various build phases of testbed development.

d. Contractor must support analysis of current and future BL configurations for performance analysis. This will require contractor to obtain a matching ship configuration to compare flight test data (CDRL A007).

e. Contractor shall conduct analysis of live fire events provided by Government agencies in

IWS TB environment and compare test results with recorded data to Monte Carlo runs

(CDRL A007).

f. Contractor shall provide analysis results in a written report and/or present results (CDRL

A002).

g. The Contractor shall execute M&S simulations, review and analyze output data, and verify run results. The Contractor shall document the outcome of HLA simulations

(CDRL A002).

h. Contractor shall receive and process data from data collection sites for performance analysis.

i. The Contractor shall assist in the development of high fidelity HLA simulations that accurately represent the performance of EW systems in a complex electromagnetic environment.

j. The Contractor shall develop software enhancements for EW simulations using computer languages such as C++, Visual Basic, JAVA, Shell Programming, Visual C++ and Python.

k. The Contractor shall develop simulations that represent US and foreign platforms, weapons, and sensors at a level of detail such that the final version of the simulation can be accredited by the cognizant testing authority.

l. The Contractor shall draft verification, validation and accreditation plans of hardware and

EW models and simulations in accordance with Navy published guidance.

3.5 Infrastructure (Task 5)

a. The Contractor shall establish and maintain a classified network connection with NRL for the purposes of distributed simulation capability in support of Flight test analysis.

Supporting tasks include, but are not limited to, the following:

1. Installing an encryption device at the Contractor site which complies with Government technical & accreditation guidance as well as the requirements in DoD 5220.22-M.

2. Developing and submitting an accreditation package (for the Contractor site connection node) to relevant Government authorities for approval, in all required formats and via all required submission methodologies.

3. Receiving Authorization to Operate (ATO) from relevant Government authorities prior to conducting any network testing. Provide a copy of ATO to COR within five (5) working days of receipt (CDRL A005).

4. Completing a Memorandum of Understanding (MOU) or Co-User agreements with the Government to establish responsibilities for, and acceptable uses of, the classified network connection (CDRL A004).

b. The Contractor shall comply fully with the Risk Management Framework (RMF) methodology - approved by the Defense Security Service for Contractor’s use - for evaluating and monitoring network security (CDRL A005).

c. The Contractor shall design, develop, enhance and maintain Graphical User Interfaces, Application Programming Interfaces (API) and plug-ins for SIMDIS, Builder, and related applications (CDRL A009).

d. The Contractor shall assist in the development of federated computer EW and Live

Virtual Constructive (LVC) simulation objectives through the development of methods for synchronization and coordination of federated simulations across both local area networks (LAN) and wide area networks (WAN).

e. The Contractor shall monitor the interaction of federated programs to ensure the coordinated functionality and quality of computer simulations and shall develop automated systematic methods and mechanisms for start and initialization of computer simulations for performing batch processes of distributed EW simulations across a WAN in order to run multiple iterations of scenarios.

f. The Contractor shall develop efforts to formulate a comprehensive means to facilitate federation setup and initialization.

g. The Contractor shall perform research into the handling and compartmentalizing of secure or proprietary data for a multi-level security infrastructure to allow for greater interoperability. It is anticipated that the simulations of some future programs will drive the requirement to run the federation at a higher security level and it is desired to maintain the highest level of commonality between different versions of the Testbed.

h. The Contractor shall conduct research into interoperability improvements such as automated distributed simulation coordination and synchronization across multiple sites to increase the number of simulations runs performed in a given period of time, thereby increasing productivity.

i. The Contractor shall develop HLA simulation interface software (CDRL A010).

j. The Contractor shall aid in provisioning end-user and server computer systems to ensure that IA controls are properly configured and enabled.

k. The Contractor shall provide technical support to end users providing services, including but not limited to, user account configuration, user account resets, email troubleshooting, security token support, etc.

l. The Contractor shall ensure that data is properly encrypted and protected according to the Security Classification Guide pertinent to that data.

m. The Contractor shall monitor end-user and network activity as appropriate in order to ensure IA requirements for data protection are being met.

n. The Contractor shall coordinate as appropriate with other IT and IA activities, including but not limited to, other local resources, enclave providers, Navy oversight, DoD oversight, and applicable commercial providers.

o. In support of NRL fielded EW systems, like the AN/SLQ-62, the Contractor shall create supporting operator manuals, installation manuals, qualification cards, operator training videos, repair videos, and support in-person operator training as required by branch personnel (CDRL A014).

3.6 Data Collection (Task 6)

a. The Contractor shall support development of data collection methods of Pulse Descriptor Word (PDW). PDW is designated as the primary messages for EW and will be used for data collection of fleet exercises.

b. The Contractor shall conduct data collection of AEGIS elements in support of M&S development activities.

3.7 Technical Support (Task 7)

a. Information Assurance Support:

1. The Contractor shall provide on-site and remote technical and operational support for Information Technology (IT) and IA activities.

2. The Contractor shall provide expertise in preparing and maintaining cybersecurity documentation, including but not limited to, Concept of Operations (CONOPS), Risk Management Framework (RMF) cybersecurity packages, User Guides, etc.

3. The Contractor shall provide technical support in procuring, configuring, deploying and operating Endpoint Security controls, including but not limited to, anti-virus software, host firewall, application control, credential protections, endpoint detection and response, host intrusion preventions systems, etc.

4. The Contractor shall provide technical support in procuring, configuring, deploying and operating Network Security controls, including but not limited to, network firewalls, network intrusion detection systems, network intrusion prevention systems, web content filters, routers and switches, etc.

5. The Contractor shall conduct periodic security scans of information systems, including but not limited to, end-user desktop and laptop computer systems, computer servers, file servers, network switches and routers, network firewalls, etc.

6. The Contractor shall aid in provisioning end-user and server computer systems to ensure that IA controls are properly configured and enabled.

7. The Contractor shall provide technical support to end users providing services, including but not limited to, user account configuration, user account resets, email troubleshooting, security token support, etc.

8. The Contractor shall ensure that data is properly encrypted and protected according to the Security Classification Guide pertinent to that data.

9. The Contractor shall monitor end-user and network activity as appropriate in order to ensure IA requirements for data protection are being met.

10. The Contractor shall coordinate as appropriate with other IT and IA activities, including but not limited to, other local resources, enclave providers, Navy oversight, DoD oversight, and applicable commercial providers.

b. Fielded System Support:

1. In support of NRL fielded EW systems, like the AN/SLQ-62, the Contractor shall create supporting operator manuals, installation manuals, qualification cards, operator training videos, repair videos, and support in-person operator training as required by branch personnel.

2. In support of operational applications, the Contractor shall support to the coordination and planning for training events to include but not limited to SIMDIS and Builder; performing an initial need assessments, cost estimates, contract estimate, agenda, training package updates, travel plans and on site execution of the training curriculum.

3. In support of operational applications, the Contractor shall develop user specific training material for the user community to include not limited to SIMDIS and Builder. Training material is to be focused based on specific operational objectives employed by the subject application. For example, training material must embed the necessary MetOc subject matter expertise for maintaining an integrated MetOc environment maximizing the effectiveness of forecasted electromagnetic predictions.

4. In support of fielded systems and software, the Contractor shall support answering and resolution of user issues reported either in person or via other electronic means, such as but not limited to email, voice mail, chat or public help desks.

4.0. Special Requirements

This section describes special requirements. The following subsections provide details of various considerations for this effort.

4.1 Security

a. To execute performance of this SOW, collateral SECRET, NATO SECRET, TOP SECRET, and/or TS/SCI clearances will be required for technical personnel.

Administrative support personnel will need Collateral SECRET clearances. Interim- SECRET clearances are allowed on a temporary basis for new-hires.

b. Contractor personnel assigned to this contract who require TS/SCI access must have a favorably adjudicated DoD Tier 5 investigation; a final TS security clearance, with eligibility of SCI prior to proposal submission. Contractor personnel assigned to this contract who require TS access must have a favorably adjudicated DoD Tier 5 investigation; a final TS security clearance prior to proposal submission. Contractor personnel, who require access to Secret information, must have a favorably completed Tier 3 investigation and a final Secret clearance prior to proposal submission.

c. Contractors issued a DoD interim-SECRET security clearance may ONLY work on unclassified tasks as outlined in the SOW. Unclassified IA or IT positions are NOT authorized with a DoD issued interim secret clearance.

d. Contract Facility Security Officers (FSOs), and/or NRL CORs, are required to report immediately to Code 1230 any derogatory information regarding a contractor holding an interim-SECRET clearance, either on-site or off-site. FSOs and NRL CORs shall also notify Code 1230 when a contractor’s interim or final clearance has been declined or revoked.

e. For Contractors working on unclassified task orders and performing at the locations listed in block 13 of the DD 254, a favorably completed suitability determination and a submitted T3 investigation is required prior to the start of work. Individual installation access restrictions may apply. All Contractors (including subcontractors) shall supplement their current security practices by requiring any personnel involved in executing the contract to complete Government sponsored and administered Operations Security (OPSEC) training, OPSE-1301 and any OPSEC guidance that may pertain to the project.

f. Contractors with an Interim SECRET clearance must be escorted at all times in classified spaces. Contractors with an Interim SECRET clearances are prohibited from having any access to the following types of classified information:

• Communications Security (COMSEC)

• Special Compartmented Information (SCI)

• Special Access Program (SAP) Information

• North Atlantic Treaty Organization (NATO) Information

• Critical Nuclear Weapons Design Information (CNWDI)

• Restricted Data (RD) (and Formerly Restricted Data)

• Naval-Nuclear Propulsion Information (NNPI)

• Foreign Government Information (FGI)

4.2 Government Furnished Property/Equipment

The Government may provide materials, equipment, laboratory spaces, and facilities as need to carry out tasking.

5.0. Contract Data Requirements List (CDRL)

Data Item No. Title of Data Item A001 Contractor’s Progress, Status, & Management Report A002 Scientific and Technical Report A003 Government Property Inventory Report A004 Signed Memorandum of Understanding A005 Unsatisfactory RMF/ATO Findings and Plan for Resolution A006 Scientific and Technical Reports A007 Final Report A008 Contractor On-Site Labor Report A009 Software Design Documentation A010 Software Development Plan A011 Computer Software Product A012 Department of Defense (DOD) Modeling and Simulation (M&S) Validation and Verification (V&V) Plan A013 Department of Defense (DOD) Modeling and Simulation (M&S) Validation and Verification (V&V) Report A014 Software User Manual A015 Model Description Data A016 Hardware Design Documentation A017 Exercise Analysis Reports A018 Exercise Reports A019 Exercise Certification Report

6.0. Acronyms

Acronym Meaning ATO Authorization to Operate BL Baselines CE Computing environment CS Combat Systems CSTB Combat System Testbed CSWF Cyber Security Work Force DoD Department of Defense

DSP Digital Signal Processor DT Developmental Testing EA Electronic Attack EM Electromagnetic EO Electro-Optic EPC Embedded personal computers ES Electronic Support ESM Electronic Support Measures ESMES Electronic Support Measures Environment Simulator EW Electronic Warfare EWS Electronic Warfare System FPGA Field Programmable Gate Array GOTS Government off the shelf HLA High-Level Architecture IA Information Assurance IATO Information Assurance Interim Authority to Operate IATT Information Assurance Interim Authority to Test ICD Interface Control Document IPT Integrated Product Teams IR InfraRed ISEA In-Service Engineering Agent IWS Integrated Warfare System LAN Local area networks M&S Modeling and Simulation MOU Memorandum of Understanding MRA Mission Readiness Assessment NACLC National Agency Check with Law and Credit NAVSEA Naval Sea Systems Command NISPOM National Security Program Operating Manual NRL Naval Research Laboratory OPSEC Operations Security OT Operational Test PDW Pulse Descriptor Word PEO Program Executive Office PRA Probability of Raid annihilation PTEWES Portable TEWES R&D Research and Development RF Radio Frequency RFA Request For Analysis RMF Risk Management Framework RTI Run-Time Infrastructure SCI Sensitive Compartmented Information SIMDIS Simulation Display SOEA Scaled On-board Electronic Attack T&E Test and Evaluation TB Testbed

TEWD Tactical Electronic Warfare Division TEWES Tactical Electronic Warfare Environment Simulator TS Top Secret USN United States Navy WAN Wide Area Network