Solicitation N6893625R0014.docx

N6893625R0014

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

A-TXT-01 FOR YOUR INFORMATION – CHINA LAKE (NAWCWD) (JUL 2024)

The following addresses and points of contact are provided:

Contract Specialist Name: Adam Rockwell Phone: (760) 793-4268 Email address: adam.r.rockwell.civ@us.navy.mil

Contracting Officer Name: Tara Brandt Phone: (760) 793-1157 Email address: tara.m.brandt.civ@us.navy.mil

U.S. Postal Service Mailing Address:

Direct Delivery Address (UPS, FedEx, etc.):

Section B - Supplies or Services and Prices

Sea Range Safety Surveillance

CPFF

The Contractor shall provide critical Sea Range Safety Surveillance in accordance with the Statement of Work (SOW) in Section C.

FOB: Destination

PSC CD: AC33

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

ODCs: Materials and Travel

COST

The Contractor shall provide material and travel in support of the Statement of Work (SOW) in Section C. G&A may be applied to materials and travel cost, however the material and travel costs are not fee bearing.

FOB: Destination

PSC CD: AC33

ESTIMATED COST

NSP

The Contractor shall provide the CDRLs as specified in Section C.

NSP

The contractor shall deliver Contractor Acquired Property (CAP) in accordance with clause ETXT.246-9512.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Totals

* denotes Key Personnel labor categories

Level Of Effort (LOE) Orders will be issued under this contract using the following streamlined ordering procedures:

(1) For each proposed order, the contracting officer will provide the contractor with a Statement of Work (SOW) and an Independent Government Cost Estimate (IGCE). The IGCE is an estimate of labor hours by labor category utilizing the estimated and negotiated Composite Labor rates table below to calculate the total estimated cost for the proposed Task Order (TO). The TO fixed fee is calculated using HTXT.232-9510 PAYMENT OF FIXED FEE (NAVAIR).

(2) These composite labor rates are estimates, and invoicing will be based upon actual costs incurred. Ceiling for Other Direct Costs (ODC) will be priced in accordance with the Government estimate. TOs crossing multiple years will be estimated by the Government using the composite rates for each year in proportion to the period of performance of the TO.

(3) Within three (3) working days of receipt of the SOW and IGCE, the contractor will respond:

(i) If the contractor agrees that it can perform the TO within the parameters of the SOW/IGCE, they will notify the contracting officer within three (3) working days of receipt of the SOW and IGCE. If the requirement remains valid, a priced order will be issued to the contractor.

(ii) If the contractor does not agree with the SOW or IGCE the contractor shall submit a proposal to the contracting officer within five (5) working days of receipt of the SOW and IGCE, addressing only the specific areas of difference in labor categories and/or hours in the IGCE. Once the differences are resolved between the contracting officer and the contractor, and the requirement remains valid, a priced order will be issued to the contractor.

(iii) If the contractor fails to respond to the proposed order within five (5) working days of receipt of the TO, the contracting officer may unilaterally issue the TO or extend the deadlines above when in the best interest of the Government.

11/26/2025 – 11/25/2026 11/26/2026 – 11/25/2027 11/26/2027 – 11/25/2028 11/26/2028 – 11/25/2029 11/26/2029 – 11/25/2030

Senior Manager

Configuration Management Analyst (Senior)

Acquisition Specialist (Senior)

Acquisition Specialist (Journeyman)

Software QA Analyst and Tester (Junior)

Software QA Analyst and Tester (Senior)

Software Developer (Junior)

Software Developer (Journeyman)

Software Developer (Senior)

Computer and Information System Manager (Senior)

Administrator (Senior)

Operation Logistics Manager (Senior)

Financial Manager (Senior)

Financial Analyst (Senior)

Aerospace Engineering and Operations Tech /Journeyman

Aerospace Engineering and Operations Tech /Senior

Production Control Clerk (Senior)

Editor (Junior)

Editor (Senior)

To Be Completed at time of award by the Government based on the information provided by Peraton, Inc. in the Microsoft Office Excel Spreadsheet Attachment 3 (see Section J).

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

NAVAL AIR WARFARE CENTER WEAPONS DIVISION (NAWCWD)

MISSILE DEFENSE AGENCY / SEA-BASED WEAPON SYSTEMS (MDA/AB)

SEA RANGE SAFETY SURVEILLANCE SERVICES

Rev1

1.0 INTRODUCTION

1.1 BACKGROUND

The mission of the Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, CA, is to be the Navy’s full-spectrum Research, Development, Test and Evaluation (RDT&E), and In-service Engineering Center for weapons systems associated with Naval warfare, missiles and missile subsystems and supporting systems, weapons integration, and assigned electronic warfare systems. This responsibility includes performing Developmental and Operational Testing and Evaluation (DOT&E); full operational support and planning for each operation; coordination of post-exercise analysis; and support for Naval Surface Weapons Anti- Air Warfare (AAW) T&E operations and fleet exercises throughout the United States.

1.2 MISSION

The mission of the Missile Defense Agency (MDA) is to develop and deploy a layered Missile Defense System (MDS) to defend the United States and its deployed forces, allies, and friends from missile attacks in all phases of flight. Sea-Based Weapon Systems (SBWS), formerly Aegis Ballistic Missile Defense (BMD), is one of the weapon systems in the layered defense and MDA is responsible for research, development, testing and evaluation. Using complementary interceptors, sensors, and Battle Management Command and Control Systems, the planned missile defense system will be able to engage all classes and ranges of ballistic missile threats. Missile defense elements being developed and tested by MDA will destroy ballistic missiles using either the force of a direct collision, called ‘hit-to-kill’ technology, or an explosive blast fragmentation warhead.

MDA is responsible for fulfilling the goals set out in the National Missile Defense Act of 1999 to “deploy as soon as technologically possible a National Missile Defense (NMD) system capable of defending United States territory against limited ballistic missile attack”. In support of this goal the SBWS program needs to conduct long-range missile intercept testing in the Pacific. To ensure an acceptable level of range safety during the tests, MDA requires adequate situational awareness over a wide enough area to support tests with ballistic missiles. Radar surveillance systems currently in use at the various missile-testing sites are inadequate to conduct range safety surveillance over such a large area.

To extend the situational awareness beyond the sensors associated with a single missile defense site, data from a combination of sources including National Technical Means, Integrated Broadcast System (IBS), Embedded National Tactical Receiver (ENTR), the Global Command and Control System (GCCS) Common Operational Picture (COP), Fleet radar/Electronics Intelligence (ELINT)/Electronic Support Measures (ESM)/infrared (IR)/sonar sensors, the United States Coast Guard (USCG) Data Fusion Center, Unmanned Aerial Vehicles (UAV), Navy P-8 surveillance aircraft via Secure Internet Protocol Router (SIPR) chat, and others will be used. For this data to provide meaningful situational awareness, it must be correlated, fused, and displayed in real time as quickly and automatically as possible. All sites participating in long range missile intercept exercises need to use a common tool that is capable of processing and fusing the data from all available sources.

The Intelligence Situation Awareness Tool (ISAT) is a system that is capable of processing and fusing the data from all available sources to provide a common situational awareness picture. The ISAT system is comprised of software, hardware, multiple communication interfaces, and a validated and thoroughly tested software program certified by the Pacific Missile Range Facility (PMRF) range safety for providing real time situational awareness of surface contacts in missile/target keep out hazard areas. The primary sources of ocean surveillance data currently in use at PMRF are the IBS and the GCCS COP. The IBS data can be obtained via a receiver, such as the Embedded National Tactical Receiver (ENTR) installed at PMRF, or via the IBS-Network broadcast over SIPRNET. The GCCS COP data is also received over SIPRNET. ISAT’s ability to fuse the information from the GCCS with the timely positional information from IBS provides more complete situational awareness than with either individual data source. The ISAT has been successfully used to support PMRF range safety during missile intercept testing to detect vessels in violation of the Notice to Mariners (NOTMAR) zones in time to divert the vessels and allow the launch to proceed.

With limited air surveillance capability stationed at PMRF, when the range is supporting national interest strategic SBWS testing, aircraft must be deployed from CONUS at significant cost, including flight hour costs and aircrew and maintenance crew travel costs. Therefore, PMRF and MDA desire to utilize USCG HC‑130J aircraft based at the Coast Guard Air Station Barbers Point, located at the Kalaeloa Airport on Oahu, HI, to perform surveillance and clearance of NOTMAR areas, and to direct range foulers in the area to depart the established NOTMAR area in effect during SBWS testing conducted in the Hawaiian operating areas.

1.3 SCOPE

This Statement of Work (SOW) covers engineering services to be provided to NAWCWD, Point Mugu, CA. Services are in support of Test and Evaluation and systems engineering activities related to SBWS and NAWCWD. The outcome to be achieved is improved range safety during missile tests utilizing the ISAT software program that collects the data to perform the tasking. Tasking includes range surveillance using ISAT to provide situational awareness; Systems Engineering Support; Systems Integration including ISAT Software Updates and maintenance to the internal source code; Mission Support including Pre-Test Site Surveys; Test Planning Support including test Monitoring and Real-Time Mission Support to improve range safety during missile intercept tests; Training; Management Support; and Reporting. Support shall be provided primarily at PMRF, but may be required at the Point Mugu Sea Range (PMSR) at Point Mugu, CA, and other test ranges as well.

This SOW also covers the personnel to plan, manage, and implement the support provided by the USCG District 14 (D14) Maritime Domain Awareness and the USCG HC-130J aircraft to perform range surveillance and clearance during SBWS test events conducted at PMRF and other test ranges. A Memorandum of Agreement (MOA) between the USCG and PMRF has been signed and covers additional details of this support. The purpose of this agreement provides the terms and procedures by which the USCG will support PMRF during missile operations in the Hawaiian area and other test ranges. This Agreement facilitates Homeland Security Maritime Domain Awareness, National Defense readiness, as well as SBWS testing and thus is in the best interest of the Government. The contractor will be assigned to and operationally tasked by the USCG D14.

1.4 GOVERNMENT FACILITY ACCESS

The Contractor will require access to Naval Base Ventura County (NBVC) restricted areas of the Industrial Areas at Point Mugu, CA. The Contractor will also require access to PMRF at Barking Sands, Kauai, HI; Hawaii Air National Guard (HI-ANG) on Oahu, HI; Joint Base Pearl Harbor Hickam (JBPHH) on Oahu, HI; USCG in Honolulu, HI; Coast Guard Air Station Barbers Point on Oahu, HI; Vandenberg Space Force Base (SFB) in CA; National Aeronautics and Space Administration (NASA) in Wallops, VA; and additional locations where the NAWCWD may request support. After-hours access may be required.

2.0 APPLICABLE DOCUMENTS

The following list of documents will be made available by the Government, if required by the Contractor, to perform the tasks defined in this contract. This list is not intended to be all-inclusive but is given as a point of reference. Additional applicable documents will be provided as required.

a. System Specification Navy Area, Theater Ballistic Missile Defense (TBMD) Systems Requirements Document (U), dated 13 March 1999.

b. TEMP 1459-1 Test & Evaluation Master Plan Number 1459-1 for the Navy Theater Wide (NTW) TBMD, dated Sep 1998.

c. DoDI 3224.03 Physical Security Enterprise and Analysis Program (PSEAP), dated 04 Jun 2020.

d. DoDI 2015.4 Defense Research, Development, Test and Evaluation (RDT&E) Information Exchange Program (IEP), dated 7 February 2002.

e. MDA Integrated Master Test Plan (IMTP), latest version.

f. Sea-Based Weapon Systems Mission-Specific Flight Test Plans.

g. Information Technology Information.

The Government will provide all necessary reference documents, not generally available to the Contractor, as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any Information Technology (IT) equipment on behalf of the Naval Air Systems Command (NAVAIR) in support of this Contract without a NAVAIR Command Information Officer (CIO) signed IT approval. See Section 7.0 Material.

2.1 Clinger-Cohen Act

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain, and dispose of information technology. In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including National Security Systems (NSS). NSS are defined in National Institute of Standards and Technology (NIST) Special Publication (SSP) 800-59. Six factors are used to identify NSS, one of which is IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT)

a. . DoDI 5000.02, Operation of the Adaptive Acquisition Framework, 23 Jan2020.

b. OSD Memo, Clinger-Cohen Act Compliance Policy, 08 Mar 2002.

c. SECNAVINST 5000.2G, Department of the Navy Implementation of the Defense Acquisition System and the Adaptive Acquisition Framework, 08 Apr 2022.

2.2 System Software / Application Compliance

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON) / NAVAIR Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates.

2.3 Cybersecurity

NAVAIR’s Cybersecurity Program is a unified approach to protect unclassified, sensitive, or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. Cybersecurity is required operationally throughout the DON. The DON CIO is responsible for Information Technology (IT) within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002.

All Cybersecurity shall be in compliance with the following listed instructions.

d. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, 31 July 2009.

e. CJCSI 6211.02D – Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012.

f. CJCSI 6510.01F, Information Assurance (IA) and Computer Network Defense (CND), 09 Feb 2011

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Cyber Incident Handling Program 10 July 2012.

h. Chief of Naval Operations/Headquarters, United States Marine Corps CNO N614/HQMC C4 – Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0, 31 October 2002.

i. Defense Acquisition Guidebook – Chapter 7 Acquiring Information Technology, Including National Security Systems, Section 7.5 Information Assurance (IA).

j. DoDD 8000.01 Management of the Department of Defense Information Enterprise (DoDIF), 17 Mar 2016.

k. DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004.

l. DoDI 8330.01, Interoperability of Information Technology (IT) Including National Security Systems (NSS), 27 Sep 22.

m. DoDI 8500.01, Cybersecurity, 14 March 2014.

n. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 19 Jul 22

o. DoDI 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 18 May 23.

p. DoDI 8551.01, Ports, Protocols, and Services Management (PPSM), 31 May 23.

q. DoDI 8580.1, Information Assurance in the Defense Acquisition System, 09 Jul 2004.

r. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 8 June 2010.

s. DON CIO Memo 02-10, Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology, 26 April 2010.

t. DON ltr 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy.

u. Federal Information Processing Standards Publications (FIPS PUB) http://www.nist.gov/itl/fips.cfm.

v. National Security Telecommunications and Information Systems Security Policy NSTISSP No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003.

w. Office of the Chief of Naval Operations OPNAV INST 5239.1C, Navy Information Assurance (IA) Program, 20 Aug 08.

x. SECNAV M-5239.1, Department of the Navy IE Cybersecurity Program 17 Nov 23

y. SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software, 10 April 2009.

z. Department of the Navy Cybersecurity Manual (22 Apr 2022).

aa. SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and Reporting Requirements, 04 Sep 2019.

ab. The National Security Act of 1947.

ac. Title 40/Clinger-Cohen Act.

ad. Title 44/Federal Information Security Management Act.

All IT procured in support of this contract shall meet all DoD/DON and NAVAIR IA polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD, and Joint Networks. These IA policies are standard across the Department and ensure IA compatibility and interoperability.

IT systems and/or networks operated by contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the instructions listed above in this section.

Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.2 Cybersecurity Controls, is subject to validation scanning, and is approved by the NAVAIR site IA Manager prior to connection.

The following specific criteria must be met before any contractor owned equipment may be connected to any DoD or NAVAIR network in support of this contract. Requirements include:

a. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD networks The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection of the system to the networks; results of approvals shall be documented via Memorandum of Agreement with the Facility Security Officer and the Defense Security Service Representative for that contractor;

b. Extent of Validation Scanning. To prevent scanning of corporate assets, all such networks, equipment and connections shall be physically segregated from any government/contractor corporate networks that are not in direct support of DoD contracts;

c. Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense Information Security Agency and comply with CJCSI 6211.02C (series), Defense Information System Network (DISN): Policy and Responsibilities, 9 July 2008;

d. Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor-owned systems, located at any NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the Command via the Outreach Services identified in Section 7, Enterprise Architecture;

e. Memorandum of Agreement and Inter-connection Agreements. An Information Assurance MOA between the contractor owning the equipment and AIR-7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks. Failure to comply with the signed MOA shall be grounds for disconnection from the network.

2.4 Enterprise Architecture

a. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any NAVAIR facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

b. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR- 7.2.3) prior to build out.

c. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

3.0 REQUIREMENTS

The Government will provide the Government Furnished Information (GFI) including test schedules, test scenarios, range safety requirements, and tasking due dates via the Mission Execution schedule and Systems Engineering Performance Test and Evaluation Team (SEPTET) Flight/Ground Mission Support Schedule. All GFI including SEPTET will be provided to the Contractor via e-mail message. Any changes or updates in schedule will be provided via e-mail message by the Government. The Contractor shall support, on average, up to seven missions at PMRF per year and up to eight mission per year at other sites. For contractor personnel permanently assigned to Government facilities, the Government will provide a workspace with systems and equipment necessary to perform daily activities and any required training.

3.1 Systems Engineering Support

3.1.1 The Contractor shall perform a detailed study for each test event of the sensor data available from the IBS, GCCS, Automatic Identification System (AIS), Imagery, Predator UAV, United States Coast Guard Maritime Intelligence Fusion Center (MIFC), Large Area Tracking Range (LATR), and other sources available from USINDOPACOM and other Combatant Commands (COCOMs) to determine their applicability to range safety. The Contractor shall attend the annual IBS Worldwide Producer and Consumer Symposium, ENTR Forum, and other mission-related events to maintain awareness of enhancements to the IBS data and emerging sensor technology. If a source of sensor data is deemed beneficial, the Contractor shall perform the requirements analysis to specify how to best integrate the sensor data into the ISAT system. Communication architectures will be explored for ingesting other sensor source contact info into ISAT including Instrumentation Network (INET) interfaces at PMRF. (CDRL A001)

3.1.2 The Contractor shall serve as a USCG project officer for testing and implementing new technologies that enhance situational awareness in the USCG D14 Maritime Domain Awareness, liaise with other Government agencies to increase operation awareness of the Maritime Domain Awareness, and assist with the development and implementation of formal policies and procedures for watchstanders.

3.1.3 The Contractor shall perform and support the USCG D14 Maritime Domain Awareness watchstander duties including but not limited to:

3.1.3.1 Maintain awareness of all active operations and status of resources in support of homeland security (HLS), maritime law enforcement (MLE), marine safety (MS), marine environmental protection (MEP), aids to navigation (ATON), and defense operations throughout the Area of Responsibility (AOR).

3.1.3.2 Develop and evaluate the Local Tactical Picture (LTP), monitors classified, unclassified, and sensor data; and makes recommendations to the Operations Unit and Command Duty Officer (CDO).

3.1.3.3 Evaluate the impact of changing weather conditions and makes recommendations to the Operations Unit and CDO.

3.1.3.4 Monitors/tracks movements of vessels of interest.

3.1.3.5 Continuously monitors maritime activities to identify anomalies in the AOR.

3.1.3.6 Identify and track vessels of interest or suspicious activity and alerts the Operations Unit and CDO.

3.1.3.7 Deliver mission/situational awareness briefs to appropriate D14 Response Division staff elements.

3.1.3.8 Maintain existing systems in accordance with standard operating procedures.

3.1.3.9 Develop basic standard operating procedures to verify logic of new or modified technical procedures.

3.1.3.10 Input boarding results for international fishing boats, sighting reports, and mission data into the Coast Guard Marine Information for Safety and Law Enforcement (MISLE) database to support USCG missions.

3.2 Systems Integration

3.2.1 The Contractor shall conduct requirements analysis and develop input to the INET interface design specification and Concept of Operations (CONOPS) for pushing operator-selected tracks from ISAT onto INET at PMRF and other ranges as required by specific task orders. (CDRL A001)

3.2.2 The Contractor shall perform preliminary site surveys to determine the requirements for the individual site. The Contractor shall make recommendations pertaining to the best configuration of equipment for the site. (CDRL A001)

3.2.3 The Contractor shall provide software updates/upgrades for the ISAT, as well as install and configure the required software at the site. The Contractor shall implement any software enhancements or modifications as directed by the Government or Government sponsor.

3.2.4 If testing at additional sites is determined to be in the best interest of the Government, the contractor shall install ISAT systems at MDA/AB sites including PMSR at Point Mugu, CA; Vandenberg AFB, CA; NASA Wallops Flight Facility (WFF) at Wallops Island, VA; and other locations requested by NAVAIR.\

3.2.5 The Contractor shall provide technical support either remotely or on-site at PMRF to comply with cybersecurity requirements related to the ISAT software, computer systems, communication equipment, and Tactical SIPRNET in the Battle Management Interoperability Center (BMIC).

3.3 Mission Support

3.3.1 Pre-test Site Survey

3.3.1.1 During each pre-test site survey, the Contractor shall verify the version of the ISAT software to be used during the scheduled test event and ensure the ISAT software has been updated to the most recent build. The Contractor shall perform software testing and validation at the Contractor’s facility prior to delivery to PMRF, and any additional locations if testing is occurring at locations other than PMRF.

3.3.1.2 During each pre-test site survey, the Contractor shall configure the ISAT to display all required mission-related data such as the Notice to Mariners (NOTMAR) and exclusion areas.

3.3.1.3 During each pre-test site survey, the Contractor shall verify the availability of IBS data through the ENTR and/or Tactical SIPRNET.

3.3.1.4 During each pre-test site survey, the Contractor shall verify IBS configuration to make sure the current broadcast contains data from the designated sensors. The designated sensors will be in accordance with specific missions as provided by the Government.

3.3.1.5 During each pre-test site survey, the Contractor shall verify the availability of GCCS data via SIPRNET.

3.3.1.6 During each pre-test site survey, the Contractor shall verify the availability of USCG AIS data. This Sensitive but Unclassified data is received on an unclassified system that can be copied to the classified system to be fused with the classified track picture.

3.3.2 Test Plan Support

3.3.2.1 Not less than five (5) days prior to each scheduled test event, the Contractor shall deliver input for a test plan, indicating the available system configuration, the data sources to be used and archived, and the schedule for on-site support as required by specific task orders. (CDRL A001)

3.3.3 Mission Test Support

3.3.3.1 The Contractor shall provide on-site (PMRF) and remote-site support for open ocean surveillance to the Range Facilities Control Office (RFCO) and/or D14 of the USCG.

3.3.3.2 Beginning not less than seventy-two (72) hours prior to each scheduled test event, the Contractor shall provide an on-site team of skilled ISAT operators to monitor the ISAT and ensure 24-hour operation for each SBWS mission at PMRF. The on-site team shall be responsible for coordinating with the range safety personnel at the site. The contractor shall integrate data input from SIRPNet, USCG, and ENTR into ISAT in preparation for mission support.

3.3.3.3 The Contractor shall also provide support to monitor the broadcasts and capture data during real time missions/exercises.

3.3.3.4 The Contractor shall coordinate the planning and operation of the USCG HC-130J aircraft to conduct range surveillance and range clearance to support range safety. The aircraft will fly under the direction of the PMRF RFCO. The USCG maintains the right to preempt or divert HC-130J flight support if an emergency occurs that require the aircraft such as Search and Rescue (SAR) or disaster relief.

3.3.3.5 The Contractor shall coordinate range surveillance with aircraft flying surveillance during SBWS flight test missions including the USCG HC-130J aircraft. This effort includes performing communication testing between surveillance aircraft and ISAT located in PMRF Battle Management Interoperability Center (BMIC) during real time missions/exercises.

3.3.3.6 Following each scheduled test event, the Contractor shall analyze mission situational awareness data collected and archived during the exercise and review such data for any anomalies in processing or in data content. The contractor shall verify that contact reports were received from all requested data sources. Mission data shall be archived and stored in the Contractor’s facility at the appropriate classification level for use at a future date. The archived data shall be retained at the Contractor’s facility for up to 10 years from the completion of the test event. Post-mission analysis of the archived data will be performed as required by specific task orders.

3.3.3.7 Not more than 45 days after each scheduled test event, the Contractor shall generate a final post mission test report, describe the detections that occurred during the exercise, and include the analysis of all archived data as required by specific task orders. (CDRL A002)

3.3.3.8 The Contractor shall have a backup capability to conduct mission support similar to the PMRF BMIC at a separate location as required by specific task orders. This backup can enhance or replace the range surveillance capabilities if the systems in the PMRF BMIC are degraded or become inoperable.

3.4 Training

3.4.1 The Contractor shall provide training for PMRF/SBWS site personnel to allow them to operate the ISAT during exercises if determined necessary by the SBWS Government Lead Test Engineer.

3.4.2 The Contractor shall conduct onside ISAT training during a mission at PMRF for Contractor personnel at least once a year to ensure the Contractor maintains a team of skilled ISAT operators.

3.5 Program Management Support

3.5.1 The Contractor shall provide program management support to include planning, coordination, and control of all activities within this SOW. This task shall include the elements of cost, schedule, and technical management. The program management support shall include generating the Monthly Progress Reports. (CDRL A003)

3.5.2 The Contractor shall attend an annual meeting with the SBWS Government Lead Test Engineer (LTE) and NAWCWD Contracting Officer’s Representative (COR) to conduct a program management review of the contract.

3.6 Management Reports and Briefing Preparation

3.6.1 The Contractor shall attend and provide technical and engineering support at engineering reviews, T&E engineering planning and coordination meetings, T&E operational planning, and coordination meetings at various locations relevant to the planning and conduct of SBWS events. The contractor shall provide reviews and minutes of meetings attended.

3.6.2 The Contractor shall deliver Monthly Progress and Status Reports to the LTE and the COR by the 15th of each month. (CDRL A003)

4.0 DATA DELIVERABLES

Specific items of reports, test plans, procedures, technical support documentation, presentation materials, meeting minutes, and progress reports will be provided in accordance with the applicable Contract Data Requirements List.

5.0 SPECIAL CONSIDERATIONS

5.1 Security

The contractor shall provide personnel with the appropriate Personnel Security Clearance (PCL) levels for the work to be performed. Access to [SECRET] information is required in the performance of this contract and shall be in accordance with the DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), incorporating change 2, 18 May 2016, applicable DoD personnel security regulations, and DoD Contract Security Classification Specification (DD Form 254). The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW IAW the DD Form 254 and the contract. All contractor personnel shall possess the requisite security clearance, accesses, and need-to-know commensurate with the requirements of their positions. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable Tier 3 (T3) investigation.

5.2 No Determination Made, Revocation or Denial of Interim PCL The contractor shall notify the NAWCWD Command Security Manager (CSM) upon notification of on-site contractor support service personnel receiving a no determination made, revocation or denial of an interim personnel security clearance or a final denial of security clearance eligibility. Contractor personnel who are determined to be ineligible for Classified Material Information (CMI) access or whose access is suspended or interim clearance is revoked shall be removed immediately from sensitive duties and shall not be permitted to have access to CMI or any Controlled Unclassified Information (CUI). Contractor personnel who lose their eligibility for CMI or CUI access shall have their IT user accounts disabled immediately for IT systems that process CUI or CMI and will not have access to any NAWCWD restricted areas, facilities, or IT systems.

5.3 Information Security. CUI

Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36 (series). The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of CUI and to control distribution of CUI in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36. All contractor facilities shall provide an appropriate means of storage for controlled information and materials.

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.48, Controlled Unclassified Information (CUI). Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption. All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only, [insert reason and date of determination]. Other requests for this document shall be referred to [insert controlling DoD office].

5.4 Communications Security (COMSEC)

The contractor will require access to COMSEC at government/contractor locations. United States cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is CUI. Publication or release of any related COMSEC information by any means, by the contractor, without prior written approval of the contracting officer is prohibited. The contractor must be a United States citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to-know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The contractor shall adhere to the DD Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime contractor to grant COMSEC access to a subcontractor.

5.5 Reporting Requirements

Contractor personnel working on a federal installation in support of this contract shall report to the NAWCWD CSM any adverse information or circumstances of which they are aware pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

5.6 Preliminary Inquiry – Loss, Compromise, or Suspected Compromise of CMI On-site contractor personnel shall cooperate with any preliminary inquiries conducted by CSM regarding loss, compromise, or suspected compromise of CMI or inquiry into significant command security weaknesses. NAWCWD CSM will notify the appropriate company Facility Security Officer (FSO) and/or Program Manager if a contractor is involved in an inquiry and questioning from the contractor employee is required.

5.7 Base Identification/Credentials

Contractors requiring access to federal installations shall obtain, with Government sponsorship, the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s). The contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials, Common Access Card (CAC) and any other secondary area access badges/identification for any employee who no longer requires access to the work site(s). Upon separation, resignation, firing, completion, or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes to include CACs and any other secondary area access badges/identification issued to contractor employees are returned to the appropriate component issuing office.

5.8 Entry Procedures to Controlled/Restricted Areas

Contractor employees shall comply with local base procedures for entry into any federal installation controlled and restricted areas. If contractor employees require unescorted entry to controlled or restricted areas, the contractor shall comply with the appropriate federal installations command physical security plan and DoD Personnel Security Program, DoD 5200.2-R.

5.9 Public Release

Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. Concerning subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain, e.g. via Distribution Statement A, and does not include information in the public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the contractor must seek specific approval from the Contracting Officer, with approval from the NAWCWD Public Affairs Office (PAO). Any CUI pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate United States Government authority. Proposed public releases shall be submitted for approval prior to release through Commander, Naval Air Warfare Center Weapons Division, Command Communications Department, 1 Administration Circle, Mail Stop 1013, China Lake, California 93555-6100

5.10 Operations Security (OPSEC) Plan: NAWCWD, the requiring organization, has made a determination that basic Operations Security (OPSEC) measures are sufficient to protect the contract related critical information associated with this contract. The NAVAIR DD 254 OPSEC annex shall be included as an attachment in the DD Form 254. When basic OPSEC measures are prescribed, there shall be no required OPSEC CDRLs associated with this contract. However, contractor shall comply with the OPSEC requirements outlined within the DD Form 254. The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements for this contract. The OPSEC program shall be in accordance with DoD and DON OPSEC requirements, to include: 1) Assignment of responsibility for OPSEC direction and implementation; 2) Planning guidance for the use of the OPSEC Process to identify vulnerabilities and apply applicable countermeasures (Contact NAWCWD Industrial Security Office for a current OPSEC Annex and CI Guide); 3) Establishment of OPSEC education and awareness training; 4) Provisions for management, annual review, and evaluation of OPSEC programs and 5) Oversight for accountability of OPSEC requirements to subcontractors. While performing at NAVAIR or NAVAIR sites, the contractor shall comply with the provisions of OPNAVINST 3432.1 and the local command/facility 3432 instruction series for operations security as well as any procedures identified in program-specific operations security plans and Program Protection Plans (PPP) as applicable.

6.0 Travel

6.1 The Contractor shall travel to test sites and other locations to support test events or to attend program planning or technical meetings.

6.2 Non-local/long distance travel from contractor facility to Washington, DC; Oahu, HI; Kauai, HI; Vandenberg AFB, CA; Point Mugu, CA; Fort Meade, MD; Chantilly, VA; and other sites, may be required in the performance of this contract and shall be approved in advance by the Contracting Officer Representative (COR).

6.3 Travel is anticipated as follows:

7.0 Quality Surveillance and Performance Standards

A Surveillance Activity Checklist (SAC) will be used by the Government to perform surveillance of contractor performance.