Statement of Work.docx

STATEMENT OF WORK

MULTI-SPECTRAL ELECTROMAGNETIC WARFARE SYSTEM SUPPORT ACTIVITY

INTEGRATED PRODUCT TEAM (MDEWSSA IPT)

ELECTROMAGETIC WARFARE (EW) JAMMER

AN/ALQ-165 AND AN/ALQ-214 SOFTWARE ENGINEERING SERVICES

29 Oct 2024

1.0 INTRODUCTION

1.1 BACKGROUND

The Naval Air Warfare Center, Weapons Division (NAWCWD) Point Mugu, CA has been designated the System Support Activity (SSA) for Navy Multi-Spectral Electronic Warfare System Support Activity Integrated Product Team (MDEWSSA IPT) systems and has the responsibility for integrating the Advanced Self-Protection Jammer (ASPJ) AN/ALQ-165, the Integrated Defensive Electronic Countermeasures (IDECM) AN/ALQ-214, and Aircraft Self Protection Optimization (ASPO) with other EW systems already under their cognizance.

The AN/ALQ-165 and AN/ALQ-214 are both Radio Frequency (RF) Jammer systems, and ASPO is a software upgrade to the AN/ALQ-214. The MDEWSSA IPT at NAWCWD, Point Mugu, California, executes the Software Support Activity (SSA) for both the AN/ALQ-165 and the AN/ALQ-214.

1.2 SCOPE

The NAWCWD MDEWSSA IPT has a follow-on requirement for engineering services and software support equipment products for the ASPJ AN/ALQ-165 and the IDECM AN/ALQ-214. This Statement of Work (SOW) establishes the requirements for software development of products within the MDEWSSA IPT located at the NAWCWD, Point Mugu, CA as identified in each Task Order (TO) issued by the Government. This contract includes the following support for AN/ALQ-165 and the AN/ALQ-214:

· General requirements

· Software Development (Software, firmware, tools and algorithms)

· Anomaly Investigations and Tracking

· Laboratory and Flight Test Support

· On-site Consultant

· Familiarization Workshop and Materials (including syllabus and presentation material)

· Support Equipment

· Presentation Material

· Source Data Generation

· Engineering Services and Hardware Support for Lab Maintenance, Upgrade, and Repair

· Meetings, and Teleconferences

The contract requirements include: enhancing the Operational Flight Program (OFP), the Mission Data File (MDF), the Mission Data File Generator (MDFG), the User Data File (UDF), and the User Data File Generator (UDFG) firmware; developing tools when applicable to support the AN/ALQ-165 and the AN/ALQ-214 systems currently in the Navy’s fleet on the FA-18A through F aircraft and on Foreign FA-18A through D and FA-18E/F aircraft; and providing products and services for Foreign Military Sales (FMS) (Australia, Finland, South Korea, Switzerland, Canada, Kuwait, Belgium, and Germany). This is a non-performance based requirement.

2.0 APPLICABLE DOCUMENTS

2.1 This section lists all applicable documents that shall provide a basis for the services and products requested in this SOW.

2.1.1 GOVERNMENT DOCUMENTS

The following documents are applicable to this effort and are required or designated as guidance in the support of the execution of the tasks requested in this SOW:

Incorporating Change 1, effective 28 April 2016

2.1.2 NON-GOVERNMENT DOCUMENTS

The following documents are applicable to this effort and in the execution of the efforts requested herein:

CMU/SEI-2006-TR-008

ESC-TR-2006-008

2.2 SECURITY REQUIREMENTS

2.2.1 The contractor shall provide personnel with the appropriate personnel security clearance levels for the work to be performed. Access to unclassified 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.

Overarching contract security requirements, and Contractor access to classified information, shall be as specified in the basic DD Form 254 for this task order. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable Tier 3 (T3) investigation.

ACCESS TO CUI, FOUO, AND/OR GOVERNMENT IT SYSTEMS:

Information Security. 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 controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36 For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01, Information Security Program Manual (Volume 4). 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.

2.2.2 OPSEC: The contractor shall adhere to all OPSEC requirements specified in the DD Form 254. The contractor shall develop, implement, and maintain an OPSEC program to protect Critical Information (CI) e.g., controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the TO. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

• Assignment of responsibility for OPSEC direction and implementation.

• Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

• Establishment of OPSEC education and awareness training.

• Provisions for management, annual review, and evaluation of OPSEC programs.

• Flow down of OPSEC requirements to subcontractors when applicable.

• The contractor shall prepare an OPSEC Plan in accordance with MIL-HDBK-254D for Government review.

2.2.3 Communications Security (COMSEC): The contractor will require access to COMSEC and will require a COMSEC account for the work being performed under this contract. U.S. cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is for official use only. 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 U.S. 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.

2.2.4 Public Release: Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract, the contractor must seek specific approval for disclosure of controlled unclassified information even if the information already exists within the public domain.

2.2.5 All Cybersecurity shall be in compliance with the following listed instructions:

All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR cybersecurity 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 cybersecurity policies are standard across the Department and ensure cybersecurity 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 NISPOM.

Approved 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.1 Cybersecurity is subject to validation scanning and must be approved by the NAVAIR site Cybersecurity Manager prior to connection.

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

2.2.6 System Security Plan

2.2.6.1 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

a. Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government's review of the SSPs at the Contractor's facility.

b. lf the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c. Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor's facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d. The Government may, in its sole discretion, conduct subsequent reviews at the Contractor's site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days' notice to the Contractor.

2.2.6.2 Compliance to NIST 800-171

a. The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a SSP(s) and POAMs that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b. Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POAM their plans to implement the following, at a minimum:

1. Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC, equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

2. Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

3. Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

4. Audit user privileges on at least an annual basis;

5. Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

6. Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

7. Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

2.2.6.3 Cyber Incident Response:

a. The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b. Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions _for_Submitting_Media.docx, In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c. If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

2.2.6.4 Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

2.2.6.5 NCIS/Industry Monitoring

a. In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor sl1all cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b. If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor 1s information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c. In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non US law.

3.0 REQUIREMENTS

The contractor shall provide engineering/technical services, and product support in the execution of the SSA activities for the AN/ALQ-165, AN/ALQ-214, and ASPO as further described below.

3.1 GENERAL REQUIREMENTS

3.1.1 The contractor shall perform engineering services for the AN/ALQ-165, AN/ALQ-214, and ASPO in support of the U.S. Navy and FMS customers, as specified in this SOW. These services shall include: integrating ALQ-165 and ALQ-214 software developed by NAWCWD Point Mugu with contractor-developed ALQ-165 and ALQ-214 software solutions; providing support for software design, development, integration, and testing at NAWCWD Point Mugu for ALQ-165 and ALQ-214 software solutions; system engineering; configuration management; new product user guidance; testing; and maintenance and repair of hardware and software developed and produced under this contract. Software includes OFP, UDF, MDF, UDFG, MDFG, firmware, Flight Line Checkout (FLCO)/Flight Line UDF (FLTLNUDF) software and development tools when applicable. Work shall primarily be accomplished at the contractor’s facility, with design, development, integration, and test support at Point Mugu, CA; and test support at China Lake, CA; and FMS destinations listed in Section 6.2. The contractor shall provide a monthly summary of expenditures itemized for total labor costs, materials other direct cost (ODC), and travel ODC. Technical progress shall be summarized to include accomplishments, compliance to schedules, issues, problems and risks to completion of the contract effort. The contractor shall provide this information in one consolidated Monthly Status Report. (CDRL A001)

3.1.1.1 The contractor shall conduct EW threat investigations, perform EW threat criticality analysis, and perform EW threat assessment and EW threat vulnerability assessments for the AN/ALQ-165, AN/ALQ-214, and ASPO to define understanding of EW threat behaviors and its interaction with the IDECM suite performance. All findings and recommendations shall be reported to the government in technical reviews and submitted as written reports or documents as listed in Contract Data Requirements Lists (CDRL A002).

3.1.2 Technical Approach: The contractor shall integrate and produce OFP, UDF, MDF, UDFG, MDFG, Flight Line Checkout (FLCO)/Flight Line UDF (FLTLNUDF) software and firmware changes in a systems engineering environment as outlined in the Software Development Plan (SDP). The software integration process outlined in the SDP shall be capable of inclusion of software and firmware designed, developed, and tested by NAWCWD Point Mugu personnel. The contractor shall provide support, via availability for consultation as needed, to the Government laboratory at NAWCWD Point Mugu for the design, development, integration, test, and production of OFP, UDF, MDF, UDFG, MDFG, Flight Line Checkout (FLCO)/Flight Line UDF (FLTLNUDF) software and firmware changes performed at NAWCWD Point Mugu. The SDP shall include process and configuration management guidelines (as an Appendix) to meet customer requirements. The contractor shall maintain TO specific schedules and include them in Monthly Progress Reports. (CDRLs A001, A003, A004, A005)

3.1.2.1 The Contractor shall follow the SDP that they develop and submit in accordance with CDRL A005. The SDP shall define the contractor’s proposed life cycle model and the processes used as a part of that model. The term “life cycle model” is defined in Institute for Electrical and Electronics Engineers (IEEE)/Electronic Industries Alliance (EIA) Std. 12207. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes, based on the work content of this SOW. In accordance with the framework defined in IEEE/EIA Std. 12207, the SDP shall define the processes, activities to be performed as a part of the processes, tasks that support the activities, and techniques and tools used to perform the tasks in detail. IEEE/EIA Std. 12207 does not prescribe how to accomplish the task, the contractor must provide detailed information so the Government can assess whether the contractor’s approach is viable. The plan shall include software design tools, source code control, time accounting, compiler or Integrated Development Environment (IDE), debugging aids, and defect tracking, to support best software development practices and design methodologies. (CDRLs A004, A005)

3.1.2.2 The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, at minimum, specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification. (CDRLs A004, A005)

3.1.3 The contractor shall identify a Program/Project Manager to provide overall direction and coordination of multiple engineering and technical tasks, and serve as the primary liaison with the Government’s technical representative under this contract. The contractor shall produce shall produce PM documents relative program management documents (i.e. project plans, projects status briefs, etc.) relative to the engineering and technical tasks being managed by the Program/Project Manager. (CDRL A001)

3.2 SOFTWARE DEVELOPMENT

3.2.1 General: The contractor shall comply with the SDP and shall produce ALQ-165 an ALQ-214 software products consistent with Government approved processes. Work shall be performed in accordance with Software Engineering Institute Capability Maturity Model Integration (SEI CMMI) Level 3 or higher processes as defined in CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development/Supplier Sourcing, Version 1.3, dated 01 November 2010. If not designated as SEI CMM or CMMI Level 3 or higher, then the contractor shall demonstrate they have processes consistent with a SEI CMM or CMMI Level 3 or higher organization. (CDRL A003)

3.2.2 OFP/UDFG/MDFG: The contractor shall integrate and generate production OFP/UDFG/MDFG/firmware software deliveries and software tools, if applicable, for U.S. Navy and specific FMS customers. The contractor shall support at NAWCWD Pt. Mugu the integration and generation of production OFP/UDFG/MDFG/firmware software deliveries for U.S. Navy and specific FMS customers. To the maximum extent possible, all software deliverables must be on the same common baseline. The contents shall be only those System Anomaly Reports (SAR’s) or Software Trouble Reports (STR’s) approved by the SSA Software Change Review Board (SCRB). The SCRB shall designate the baseline OFP/UDFG/MDFG into which the approved SAR’s or STR’s will be incorporated. The Government will provide input to the contractor on proposed solutions resulting from anomaly investigations that will require demonstration to the Navy using ALQ-165 and ALQ-214 hardware. Solutions for the ALQ-165 and ALQ-214 and future versions shall be maintained within synchronization as much as possible. The software used to demonstrate proposed solutions shall be engineering test loads. The contractor development shall include assessment of threat data effectiveness in providing accurate and timely Electronic Countermeasure (ECM) techniques in the AN/ALQ-214 and AN/ALQ-165. The contractor shall provide change pages for the software documentation impacted by Government-approved changes. (CDRLs A002, A003, A004, A005)

3.2.3 Software Deliverables and Formats: Delivered ALQ-165 and ALQ-214 software builds shall include OFP/UDF/MDF/UDFG/MDFG/firmware source code object code files, binary files, Memory Loader files, and any support files necessary to assemble, compile, link, build and execute the software. OFP/UDFG/MDFG software shall be delivered in the format compatible with the USQ-131 Memory Loader Verifier Set (MLVS) and the Program Loader Set (PLS). UDFG/MDFG software, firmware, and other system software configuration items such as development tools shall be delivered in the format compatible with the system they operate within. The contractor shall provide software products and shall also provide a Version Description Document (VDD) that identifies and describes all changes made to the software/firmware. The VDD shall also include complete configuration identification information to include what is displayed on the cockpit displays and what is stored in the software code itself. (CDRLs A003, A004, & A005)

3.2.4 Software Acceptance Criteria: Final acceptance shall be in accordance with the Acceptance Test Plan (ATP) and shall be evidenced by Government execution of a Material Inspection and Receiving Report, DD Form 250, submitted through the Wide Area Workflow (WAWF) system. The ATP shall be submitted to the Government in accordance with CDRL A005 prior to ATP execution. (CDRLs A004, A006)

3.2.5 Software Installation: The contractor shall install and provide installation instructions for the USN and FMS UDFG/MDFG software and validate the installation is functional. (CDRL A004)

3.3 ANOMALY INVESTIGATIONS AND TRACKING

3.3.1 Investigations: The contractor shall review anomaly reports, test data, test reports, and other written material, and shall provide a report to the Government on the suspected cause of the anomaly, the hardware and/or software unit suspected to be non-compliant with specifications, the recommended course of action, and recommend additional investigation, or corrective action for the U.S. Navy and specific FMS customers, if required in individual TOs. Analysis of the anomaly may require additional laboratory or flight-testing. If requested by the Government, the contractor shall present the results of the analysis in the Anomaly Investigation Technical Report. Anomalies shall be provided in increments to fit within defined build cycle. (CDRL A002)

3.3.2 Tracking: The contractor shall document and provide the Government a copy of any System Problem Report (SPR), SAR or STR that applies to the ALQ-165, ALQ-214 and future version’s computer software and/or firmware developed in parallel, to be entered in the Government anomaly reporting system. The anomaly shall be provided in XML and/or standard Microsoft Office formats (including forms) such as Word, Excel, or PowerPoint. The .pdf format shall not be used unless requested by the Government. (CDRLs A002, A004, A005)

3.4 LABORATORY AND FLIGHT TEST SUPPORT

3.4.1 The contractor shall provide test documentation of final contractor testing and the analysis of test data for all final delivered software products to include OFP, UDF, MDF, UDFG, MDFG, and firmware updates. (CDRL A007)

3.4.2 The contractor shall provide support, via availability for consultation, to Government laboratory and flight test events of the software delivered. This support shall include test planning, test execution, test analysis and test reporting. The contractor shall conduct primary testing at the contractor’s laboratory and test support at Government laboratories at Point Mugu, CA and China Lake, CA. The contractor shall perform aircraft ground testing to verify system operation and performance. Ground testing shall include testing with Navy support equipment. The contractor shall assist with anomaly investigation in the laboratory and at technical interchange meetings and provide technical analysis as to the root cause of the anomaly. (CDRLs A002, A008)

3.5 ON-SITE CONSULTANT

The contractor shall provide on-site technical assistance to specific ALQ-165 and ALQ-214 U.S. Navy and FMS customers. This shall include setting up laboratories, troubleshooting system operation and laboratory assets, providing installation support and instructions on UDFG/MDFG and software tools, and presenting technical briefings at Technical Coordination Meetings (TCMs), Program Management Reviews (PMRs), and Technical Working Groups (TWGs). (CDRLs A008, A009)

3.6 ALQ-165 & ALQ-214 OFP/UDFG FAMILIARIZATION WORKSHOP AND MATERIALS

3.6.1 The contractor shall prepare ALQ-165 & ALQ-214 OFP/UDFG new product user guidance that describes the operation of new/updated OFP and UDFG/MDFG, and syllabus and materials in support of ALQ-165 and ALQ-214 familiarization workshops as specified at the TO level. Upon Government approval via email or letter of formal approval, the contractor shall produce and deliver the final familiarization workshop syllabus and materials, which may include but are not limited to software files, User Manual, and familiarization workshop materials in hard copy, and/or electronic media. (CDRLs A009, A00A)

3.6.2 The contractor shall prepare and conduct the familiarization workshop as specified at the TO level. Upon completion of the familiarization workshop, the contractor will provide to the Government a report to document the accomplishments of the familiarization workshop. (CDRL A008)

3.7 SUPPORT EQUIPMENT

The contractor shall incorporate new requirements or problems identified in Government-approved SARs or STRs in the designated FLCO and FLTLNUDF baseline of the Navy support equipment. Engineering support shall include FLCO/FLTLNUDF requirements development, design, development, verification testing, and confirmation of separate software loading using the MLVS and/or PLS. The contractor shall incorporate new requirements to support software loading and verification with the Program Loader Set AN/USQ-203. The contractor shall incorporate new requirements or correct anomalies/trouble related to the software support adapters that are used with the USM-670 to conduct flight line maintenance. All documentation that is impacted by FLCO/FLTLNUDF changes shall be updated and provided to the Government for approval and shall be provided in a format to be specified by the TPOC or Government Configuration Manager. (CDRLs A003, A004, A005, A007)

The contractor shall provide technical assistance such as FLCO/FLTLNUDF troubleshooting and integration for Government FLCO/FLTLNUDF changes. Unless otherwise specified, the FLCO/FLTLNUDF development shall be performed in the contractor’s facilities. (CDRL A002)

3.7.1 Support Equipment Logistics

The contractor shall provide an Item Unique Identification (IUID) Plan, a Maintenance Plan (MAPL) Report, and a Provisioning Parts List (PPL) for the ALQ-214(V)4 and (V)5 software support adapters. (CDRLs A00B A00C, A00D)

3.7.2 ALQ-214(V)4/5 Software Support Adapters

The contractor shall produce and deliver ALQ-214(V)4/5 Software Support Adapters in accordance with PS410 Performance Specification for the ALQ-214(V)4/5 Software Support Adaptors. The contractor shall conduct an acceptance test procedure on each ALQ-214(V)4/5 software support adaptors in accordance with 4106736 ATP for the ALQ-214(V)4/(V)5 WRA-1 Rack Adapters prior to delivery. (CDRLs A003, A004, A005, A007)

3.7.3 ALQ-214(V)4/5 Software Support Adapter Transit Case

The contractor shall provide lined cases for the ALQ-214(V)4/5 software support adaptors. The transit case shall be constructed of material strong enough to resist denting, breakage or other failure under harsh environmental and handling exposures in accordance with MIL-PRF-28800F. The transit case shall include a contents list that illustrates the storage location for ALQ-214(V)4/5 Software Support Adapter, name plate and external labels. The transit case shall be limited in weight to permit one-person lift per MIL-STD-1472G. (CDRL A00D)

3.8 PRESENTATION MATERIAL

The contractor shall prepare presentation materials as specified at the TO level. (CDRL A009)

3.9 SOURCE DATA GENERATION

The contractor shall provide documentation that details all changes to aircraft cockpit displays and Built In Test (BIT) as a result of changes made to OFP, MDFG, UDFG, and algorithms. (CDRL A002)

3.10 ENGINEERING SERVICES AND HARDWARE SUPPORT FOR LAB MAINTENANCE, UPGRADE AND REPAIR

The contractor shall provide support for hardware and software maintenance and repair of all equipment of the system including, but not limited to: test benches, Prime Mission Equipment (PME), simulators, and associated calibration activities. The contractor shall perform upgrades if the equipment is not in the latest configuration, as directed in the TOs.

3.11 MEETINGS AND TELECONFERENCES

The contractor shall provide support to attend meetings, telephone conference calls, and video teleconferences for the purpose of: exchanging technical information with customers, discussing status, reviewing requirements, and planning. The contractor shall provide personnel with the appropriate technical expertise and skills, dependent upon the purpose of the discussion. The contractor shall document meetings by minutes and/or presentations to record the technical issues, solutions, agreements and decisions that occurred. (CDRL’s A009, A00E)

3.12 SECURITY REQUIREMENTS

3.12.1 INFORMATION SECURITY MARKINGS AND SAFEGUARDING:

FOUO information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01, Information Security Program Manual (Volume 4) and DoD 5400.7-R, Freedom of Information Program, Chapter 3 (pages 31-42). Contractor shall not store or transmit CUI on personal IT systems or via personal e-mail.

3.12.2 PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP):

The contractor shall update as necessary the PPIP to ensure effective and efficient protection of essential program information, technologies and systems, and in accordance with OPSEC requirements, which will include, at a minimum:

• The Security Management structure.

• The Critical Program Information (CPI) physical locations under the contractor’s or subcontractor’s control.

• The vulnerability of the CPI under the contractor’s or subcontractor’s control to intelligence collection in the following areas: Human Intelligence (HUMINT); Open Source Intelligence (OSINT); Signals Intelligence (SIGINT); Imagery Intelligence (IMINT); Computer Network Operations (CNO).

• Countermeasures at each site where CPI is held, from the following security domains (as applicable); physical security; personnel security; telecom and network security; application/systems development; cryptography; security architectures; operational security; network and IT access control.

• Any special handling procedures required for CPI, and procedures for recovering CPI in the event of a mishap. The contractor shall address these procedures for all phases of the program, including (but not limited to): Research Development Test and Evaluation (RDT&E); production; operations maintenance; logistics; transportation; training; disposal.

• Procedures for ensuring compliance with U.S. Government export statutes and regulations.

• Procedures for public release of program information. (CDRL A00F)

3.12.3 OPERATIONAL SECURITY (OPSEC)

The contractor shall prepare an OPSEC Plan in accordance with MIL-HDBK-254D for Government review. (CDRL A00G)

3.12.4 IT PERSONNEL SECURITY REPORT:

The contractor shall submit a status report that includes all employees requiring access to Government IT systems. (CDRL A00H)

4.0 REPORTS, DATA, AND OTHER DELIVERABLES

4.1 CONTRACT DATA REQUIREMENTS LIST (CDRL)

In performance of the support identified in this SOW, the contractor shall deliver reports, data, and other documentation in accordance with the applicable CDRLs. All software and documentation developed and delivered under this contract shall remain the property of the U.S. Government.

The contractor shall email the unclassified Contractor’s Monthly Progress and Management Status Report (CDRL A001), on a monthly basis, to the COR and Government Project Lead (GPL) who is identified in each individual task order. Classified material shall be mailed in accordance with approved means as indicated by the Government, or via SIPRnet. Clarification concerning the details of specific tasks will be communicated by the Government COR and/or TPOC during bi-weekly meetings, status meetings, and/or via email. The contractor shall provide progress reports and general programmatic documentations to support reviews and projects.

5.0 MATERIALS AND PURCHASING / SUBCONTRACTOR CONSENT

5.1 The contractor shall manage material and consumable supplies at levels to meet mission requirements. The contractor must obtain prior approval from the COR for any supply purchases valued over $10,000, and services valued over $3,500. All COR-approved purchases shall be submitted, documented, and filed for Contracting Officer post action review. The contractor must obtain prior approval from the Contracting Officer for any purchases valued over $25,000. To receive approval for the purchases, the contractor shall submit a material purchase request package providing a description, price, evidence of adequate price competition, or if unavailable, a justification for use of a single source and a determination that the price is fair and reasonable.

5.2 Consent to subcontract is required and the contractor shall follow the procedures in Clause 52.244-2 Subcontracts Alt I and notify the Contracting Officer reasonably in advance of entering into any subcontracts that exceeds either simplified acquisition threshold or 5 percent of the total estimated cost of this contract.

6.0 OTHER INFORMATION

6.1 PLACE OF PERFORMANCE

The majority of work will be conducted at the contractor’s facility. The Government will provide visitor’s badges for access to the Pt. Mugu facility as required.

7.0 TRAVEL

7.1 During performance of individual TOs, the contractor shall be required to perform travel to support the tasking as determined by the Government Contracting Officer’s Representative (COR) or Technical Point of Contact (TPOC). The contractor shall submit a request 10 days prior to the Government COR for approval. Each travel request will minimally consist of:

• Date of Request

• Delivery order number

• Employee(s)

• Date and duration of proposed travel

• Purpose of travel

• Destination

• Cost estimate (airfare, per diem, car rental, miscellaneous expenses)

• Total travel allowance on the TO

• Total travel cost expended to date

7.2 The contractor shall be required to perform CONUS and International travel to accomplish the requirements of this contract throughout the period of performance, as estimated below:

Point Mugu, CA

Nashua, NH

St. Louis, MO

Goleta, CA

Seosan, South Korea

Seoul, South Korea

Daegu, South Korea

Tikkakoski, Finland

Tampere, Finland

Adelaide, Australia

Interlaken, Switzerland

Ottawa, Canada

Ali Salem Air Force Base, Kuwait

Patuxent River (PAX), MD

Upon completion of each trip the contractor shall submit a trip report. (CDRL A008)

8.0 GOVERNMENT FURNISHED PROPERTY

8.1 Government Furnished Property

Government Furnished Property (GFP), include Government Furnished Information (GFI), and Government Furnished Equipment (GFE) may be provided to the contractor to accomplish contract requirements as specified in individual orders. The contractor shall inventory all GFP and it shall be dispositional by the Government at the completion of this contract.

8.2 Laboratory Access

The Government will furnish access to Government laboratories to accomplish tasking described in Section 3.4 of this SOW. Laboratories available for use are the Electronic Combat Simulation Laboratory (ECSEL), the Software Development Lab, and Support Equipment Lab at NAWCWD Point Mugu, CA plus the Advanced Weapons Laboratory (AWL) at NAWCWD China Lake, CA. The Government reserves the right to control laboratory schedule and use of documentation and information required for the performance of this contract. The Government will supply the contractor with information on where and how to send contractor personnel security clearances when visiting these laboratories. Should there be additional forms for the use of contractor equipment in the laboratory; the Government will provide the procedures and forms to the contractor.

9.0 QUALITY ASSURANCE (QA)

9.1 QA Program

The contractor shall provide a QA program consistent with the processes described in ISO 9001 and consistent with Capability Maturity Model Integration for Development (CMMI-DEV), Version 1.3, dated 01 November 2010. The Government may use the on-site Defense Contract Management Agency representatives to maintain insight into the contractor’s QA program or utilize members of the MDESSWA EW IPT to monitor work performed. Configuration Management processes shall be consistent with CMMI-DEV Version 1.3, dated 01 November 2010. (CDRL A005)

9.2 Quality Performance Standards

A Surveillance Activity Checklist (SAC) will be used by the Government to perform surveillance. A copy of the SAC will be provided as an attachment in Section J at award time, for informational purposes only.

NAVY Multi Spectral Defensive…