Draft_PWS_14-R-0101.doc

PERFORMANCE WORK STATEMENT

NAVY TACTICAL AIRCRAFT ELECTRONIC WARFARE (TACAIR EW)

ELECTRONIC WARFARE (EW) JAMMER

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

23 Apr 2014

1.0 INTRODUCTION

1.1 BACKGROUND

The Naval Air Systems Command (NAVAIR) PMA-272 sponsors the development and production of both the Advanced Self-Protection Jammer (ASPJ), AN/ALQ-165, and the Integrated Defensive Electronic Countermeasures (IDECM), AN/ALQ-214. The AN/ALQ-165 and AN/ALQ-214 are both Radio Frequency (RF) Jammer systems. The TACAIR EW Integrated Product Team at Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, California, executes the Software Support Activity (SSA) and Support Equipment SSA activities for both the AN/ALQ-165 and the AN/ALQ-214.

The contract is to provide engineering services and products required by TACAIR EW for the AN/ALQ-165 and AN/ALQ-214. Services required are investigations of anomalies, software engineering, systems engineering, support tools and facilities maintenance, documentation, and hardware and firmware maintenance and upgrade.

1.2 SCOPE

This Performance Work Statement establishes the requirements for AN/ALQ-165 and AN/ALQ-214 software engineering services to the Tactical Aircraft Electronic Warfare Integrated Program Team (TACAIR EW IPT) at the Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, California. Services will also include engineering services for Foreign Military Sales (FMS) customers at NAWCWD. The primary place of performance is at the contractor’s facility.

2.0 APPLICABLE DOCUMENTS

This section lists the documents that shall provide a basis for the services and products requested herein. As with all programs, these documents may be updated and the Contractor shall check with the Government Technical Point of Contact (TPOC) or the Government Configuration Manager to ensure the latest version is available for use.

2.1 GOVERNMENT DOCUMENTS

The following documents are applicable to this effort and are designated if they are required or provided for guidance only in the execution of the tasks requested herein:

2.2

NON-GOVERNMENT DOCUMENTS

The following documents are applicable to this effort and are designated if they are required or provided for guidance only in the execution of the tasks requested herein:

CMU/SEI-2006-TR-008

ESC-TR-2006-008

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 PWS.

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

It is the Government's responsibility to ensure that any "IT" procurement (hardware/hardware maintenance, software/software maintenance, engineering services, web services, telecommunications, etc.) procured by the Contractor under the scope of this Contract/Task Order that contains "IT" meet the following requirements.

The following paragraphs are for information only:

2.3

RESERVED

2.4

RESERVED

2.5

RESERVED

2.6

RESERVED

2.7

RESERVED

2.8

RESERVED

2.9

RESERVED

3.0 REQUIREMENTS

The contractor shall provide engineering and technical services and products in the execution of the SSA activities for the AN/ALQ-165 and AN/ALQ-214.

3.1 GENERAL REQUIREMENTS

3.1.1 The contractor shall perform engineering services for the AN/ALQ-165 and AN/ALQ-214, as specified in this PWS. These services shall include: anomaly investigations for both hardware and software; design and development of Operational Flight Program (OFP), User Data File (UDF), UDF Generator (UDFG), Mission Data File (MDF), and MDF Generator (MDFG), Flight Line Checkout (FLCO)/Flight Line UDF (FLTLNUDF) software, firmware, and other related software configuration items, documentation, and testing; Government laboratory and flight test support; software, firmware, and hardware tools and facilities maintenance and update; equipment and hardware maintenance and repair; logistics and training. This contract may include engineering services for Foreign Military Sales (FMS). The contractor shall perform all FMS work for the Navy and all deliverables will be provided to the Navy who is then responsible for providing them to the FMS Customer.

3.1.2 The contractor shall produce software products consistent with Software Engineering Institute Capability Maturity Model Integrated (SEI CMMI) Level 3 processes as defined in Capability Maturity Model Integrated, Version 1.3, dated 1 November 2010 or later. If not designated as CMMI Level 3, then the contractor shall demonstrate it has processes consistent with a CMMI Level 3 organization. (CDRLs TBD)

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 technical representative under this contract. The contractor shall produce any and all 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. (CDRLs TBD)

3.1.4 The contractor shall provide a password protected secure website for unclassified deliveries and to which all CDRLs shall be posted. Classified material shall not be posted to the website. Clarification concerning the details of specific tasks set forth in the order will be communicated by the Government TPOC and posted to the contractor’s inbox via this website. The contractor shall provide progress reports and general programmatic documentations to support reviews and projects. (CDRLs TBD)

3.2 TECHNICAL TASKS

The government will provide specific technical documentation, guidelines and delivery requirements under individual task orders. Technical tasking will be outlined on individual task orders.

3.2.1 Project OFP Development and Software Engineering Support

3.2.1.1 Anomaly Investigations

The contractor shall review anomaly reports, test data, test reports, and other written material in an effort to 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 to propose additional investigation, if required. (CDRLs TBD)

3.2.1.2 Systems Engineering

The contractor shall provide systems engineering support in the development of requirements, the translation of requirements into engineering solutions, the implementation of hardware, firmware, and software solutions, integration of the AN/ALQ-214 and AN/ALQ-165 with other EW, avionics, and support equipment systems, and laboratory, ground and flight testing. (CDRLs TBD)

3.2.1.3 Other Software Configuration Items

The contractor shall provide new or update existing software configuration items as specified in Sections 3.1, 3.3.1, 3.3.2, 3.3.3, and 3.3.4 of this PWS. This shall include the development of or update to supporting documentation. All changes shall be approved by the Government before incorporation and be fully documented and tested in accordance with the contractor’s software development processes. The Government will review and provide approval/disapproval of all changes within 30 working days of submission by the contractor. Unless otherwise specified, the software development shall be performed in the contractor’s facilities. The Government may choose to monitor the other software configuration item development to prevent problems and to provide technical guidance in the interpretation of specifications and requirements. (CDRLs TBD).

3.2.1.4 Tools And Facilities Maintenance

The contractor shall provide upgrades to software, firmware, and hardware development, testing tools, and implementation support of the AN/ALQ-165 and AN/ALQ-214 tools. If onsite update is required, the contractor will perform the update at the Government’s facilities. (CDRLs TBD).

3.2.1.5 Laboratory And Flight Test Support

The contractor shall provide engineering services for the preparation of test documentation, conduct of testing, and analysis of test data. This shall include ground testing of the system operation and performance while installed in the host aircraft. Ground testing shall include testing with Navy support equipment. This work may be done at the contractor’s facilities and Government facilities and activities. The Government will coordinate access to laboratories outside of the contractor’s laboratories, on an as-needed basis. 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. (CDRLs TBD)

3.3 SOFTWARE ENGINEERING SUPPORT

3.3.1 Operational Flight Program

The contractor shall incorporate new requirements or fix problems identified in Government-approved System Anomaly Reports (SARs) or Software Trouble Reports (STRs) in the designated OFP baseline. Engineering support shall include OFP requirements development, design, development, verification testing, and confirmation of separate OFP loading using the standard loader, USQ-131, the Memory Loader Verifier Set (MLVS) or other means available to the systems. The OFP shall be delivered in accordance with Government instructed format that is loadable as well as all source code files by classified CD for the US Navy formal release process. All documentation that is impacted by the OFP 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. The Government will review and provide approval/disapproval of the documentation within 30 working days of the contractor’s submission .

The contractor may also be requested to provide technical assistance such as OFP troubleshooting and OFP integration for OFP changes. Unless otherwise specified, the OFP development shall be performed in the contractor’s facilities. (CDRLs TBD)

3.3.2 User Data File (UDF)/Mission Data File (MDF)

The contractor shall incorporate Government-approved SARs/STRs into the UDF/MDF as required. The contractor shall provide engineering support to the Government for Government updates of the UDF. Engineering services shall include requirements and design documentation development support, performance verification testing, and confirmation of separate UDF/MDF loading using the standard loader, USQ-131, MLVS or other means available to the systems. The contractor shall support the test and validation of current ECM techniques in the AN/ALQ-214 and AN/ALQ-165. (CDRLs TBD).

3.3.3 USER DATA FILE GENERATOR

The contractor shall incorporate new requirements or problems identified in Government-approved SARs or STRs in the designated UDFG/MDFG baseline. Engineering services shall include UDFG/MDFG requirements development, design, development, and verification testing. The contractor shall deliver the UDFG/MDFG executables file and all source code files on a classified CD. The OFP source code/files will also be delivered. All documentation that is impacted by the UDFG 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. The Government will review and provide approval/disapproval of the documentation within 30 working days of the contractor’s submission. The contractor may also be requested to provide technical assistance such as UDFG/MDFG troubleshooting and UDFG/MDFG integration for Government UDF/MDFG changes. (CDRLs TBD)

3.3.4 SUPPORT EQUIPMENT SOFTWARE

The contractor shall incorporate new requirements or problems identified in Government-approved SARs or STRs in the designated FLCO and FLTLNUDF baseline. Engineering support shall include FLCO/FLTLNUDF requirements development, design, development, verification testing, and confirmation of separate software loading using the standard loader, USQ-131B. The contractor shall incorporate new requirements to support software loading and verification with the Next Generation Software Loader (NGSL) that will replace the USQ-131B. 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. The Government will review and provide approval/disapproval of the documentation within 30 working days of the Contractor’s submission.

The contractor may also be requested to 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. (CDRLs TBD)

3.3.4.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 TBD).

3.3.4.2 ALQ-214(V)4 Software Support Adapters

The contractor shall produce and deliver ALQ-214(V)4 Software Support Adapters part no. 4104445G002 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 software support adaptors in accordance with 4106736 ATP for the ALQ-214(V)4/(V)5 WRA-1 Rack Adapters prior to delivery. (CDRLs TBD)

3.3.4.3 ALQ-214(V)4 Software Support Adapter Transit Case

The contractor shall provide cases for the ALQ-214(V)4 software support adaptors. The transit case shall be constructed of material strong enough to resist denting, breakage or other failure under the specified environmental and handling exposures. The transit case shall be in accordance with MIL-PRF-28800F paragraph 3.7. The transit case shall include a contents list that illustrates the storage location for ALQ-214(V)4 Software Support Adapter. The transit case shall be limited in weight to permit one person lift. Total weight of the transit case (equipment included) shall not exceed 42 lbs. The maximum dimensions of the case shall not exceed a size capable of passage through hatches 20 inches wide by 38 inches high, reduced further by round corners on a 10 inch radius to comply with Navy shipboard applications. (CDRLs TBD)

3.4 TECHNICAL SERVICES FOR COMPLETED ITEMS

The contractor shall provide technical services support for software, firmware, and hardware troubleshooting, and data analysis. (CDRLs TBD)

3.5 QUALITY ASSURANCE AND CONFIGURATION MANAGEMENT

The contractor shall provide a quality assurance (QA) program consistent with the processes described in ISO 9001. The Government may use on-site Defense Contract Management Agency (DCMA) representatives to maintain insight into the contractor QA program or utilize members of the TACAIR EW IPT to monitor work performed. Configuration Management processes shall be consistent with CMMI, Version 1.3. (CDRLs TBD)

3.6 MEETINGS, TELEPHONE CONFERENCE CALLS, AND VIDEO TELECONFERENCES

As specified in individual orders, the contractor shall host or participate in meetings, , telephone conference calls (TCC), and video teleconferences (VTCs) for the purpose of, at a minimum, exchanging technical information, discussing status, reviewing requirements, and planning. The meetings shall include, but are not limited to Program Management Reviews (PMRs), Software Change Coordination Meetings (SCCMs), Computer Resources Working Group (CRWG) meetings, Technical Review Boards (TRBs), Software Change Review Boards (SCRBs), Test Plan Working Groups (TPWGs), Interface Control Working Groups (ICWGs), and Technical Coordination Meetings (TCMs). For high complexity task orders that reflect 4,500 hours or more, meetings shall include, but not be limited to, program kick-off meeting, requirements review, critical design review, and a test readiness review. For low/medium complexity task orders that reflect less than 4,500 hours, meetings shall include, but not be limited to, program kick-off and critical design reviews. This will allow the contractor to further streamline their engineering efforts as required The contractor shall prepare technical briefs/materials as needed for program reviews and meetings. The contractor shall provide personnel with the appropriate technical expertise and skills, dependent upon the purpose of the meeting, TCC, or VTC. (CDRLs TBD)

4.0 REPORTS, DATA, AND OTHER DELIVERABLES

4.1 CONTRACT DATA LIST REQUIREMENTS

In performance of the support identified in this PWS, the contractor shall deliver reports, data, and other documentation in accordance with the applicable Contract Data Requirements List (CDRL). All software and documentation developed and delivered under this contract shall remain the property of the U.S. Government.

5.0 GOVERNMENT FURNISHED ITEMS AND SERVICES

5.1 LABORATORY ACCESS

The Government will furnish access to TACAIR EW laboratories at Point Mugu, Buildings 36, 3008, 351 or any other facility as deemed by the Government on an as-needed and non-interference basis. The Government reserves the right to control the laboratory schedule and use of documentation required for the performance of this Contract.

5.2 GOVERNMENT FURNISHED PROPERTY

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

5.3 OTHER DIRECT COSTS - MATERIALS

The contractor shall provide materials as directed by the Government in individual task orders for repair of test benches and test systems in the Government laboratory facilities.

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.

6.2 RESERVED

6.3 SECURITY

6.3.1 Security Clearance

The contractor shall provide personnel with the appropriate security clearance levels for the work to be performed. Contractor personnel must have the appropriate clearances on file with the program security coordinator. The contractor must notify the COR or security coordinator when an employee’s clearance level is revoked. The contractor shall provide a list of personnel with the need to know for access to the Document Control Center (DCC) controlled data no later than 14 days after the award of this contract. Upon completion of the contract requirements, the contractor shall return all documents to the Government.

6.3.2 Security Requirements

The contractor shall update and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information in accordance with the National Industrial Security Program Operating Manual (NISPOM) and DoDM 5200.01, Information Security Manual. The DoD Contract Security Classification Specification, DD Form 254 Attachment X, defines program specific security requirements. All contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, classified equipment and materials and other equipment and materials.

6.3.3 Program Protection Implementation Plan (PPIP):

The contractor shall update, as applicable, the PPIP to ensure effective and efficient protection of essential program information, technologies and systems, and in accordance with Operational Security (OPSEC) requirements which will include, at a minimum: (CDRLs TBD) The Security Management structure.

a) The CPI physical locations under the contractor’s or subcontractors’ control.

b) The vulnerability of the CPI under the contractor’s or subcontractors’ 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).

c) 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.

d) 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): RDE&E; production; operations; maintenance; logistics; transportation; training; disposal.

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

f) Procedures for public release of program information.

The contractor shall follow these Security Classification Guides:

1) Countermeasures Set, AN/ALQ-165, Airborne Self-Protection Jammer (ASPJ), OPNAVINST S5513.8B-31 of 13 April 1998

2) Integrated Defensive Electronic Countermeasures (IDECM) Radio Frequency Countermeasures (RFCM) Subsystem AN/ALQ-214 and AN/ALE-55 CD 19 AUG 2010, OPNAVINST S5513.8B of Aug 1999

7.0 TASK ORDER PERFORMANCE STANDARDS AND EVALUATION

7.1. QUALITY ASSURANCE SURVEILLANCE PLAN

A Quality Assurance Surveillance Plan (QASP) is attached for information purposes. Contractor performance will be evaluated on a periodic basis as described in the QASP. (CDRLs TBD)

7.2 INCURRED COST REPORTING

In order to support invoice reviews conducted as part of proper surveillance, the contractor shall report incurred cost and progress in accordance with NAVAIR clause 5252.232-9520, "Incurred Cost and Progress Reporting for Services" and contract attachment number TBD. (CDRLs TBD)