13-R-0011_Amd_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to provide response to offeror questions, as w ell as update Sections C, L and M (changes to the paragraph or specific sentence are highlighed in yellow ). Paragraph 5.1.7 of the PWS w as deleted in its entirety. Also, paragraph 3.5 in Section M w as deleted in its entirety. Additional updates, additions and deletions to clauses have also been made, as show n herein.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 50

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 18-Oct-2013

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N68936-13-R-0011

X 9B. DATED (SEE ITEM 11)

26-Sep-2013

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

18-Oct-2013

CODE

CDR NAWCWD CODE 254300D

ATTN: D. MCKELLAR

(760) 939-9661

429 E BOWEN RD - STOP 4015

CHINA LAKE CA 93555

N68936 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N68936-13-R-0011

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

Q & A'S - AMENDMENT 02

1. Offeror Question: In Section B of the solicitation, the Level of Effort (LOE) estimated to be ordered is 487,200 total man-hours of direct labor by classification and LOE composition. It is our interpretation that offerors are required to propose the full 487,200 hours in accordance with Section B and Section L, 4.5.2 to allow for reasonable cost comparison amongst all bidders. Please confirm that offerors are required to propose all 487,200 hours in accordance with the LOE composition provided in the RFP.

Government Response: Yes, all offerors are expected to propose 487,200 hours in accordance with the LOE provided in the RFP.

2. Offeror Question: As the requirement for resumed personnel has been removed in Amendment 1, please clarify if offerors will be allowed to provide key personnel names after contract award, thereby allowing non-incumbent contractors the opportunity to hire incumbent staff into these key positions.

Government Response: Names of Key personnel can be provided after award.

3. Offeror Question: In PWS Section 2.2 Instructions and Guides, the Government lists AEA IPT Processes and Procedures, September 2013 (located at: AEA SharePoint Program Team Collaboration Tool and Repository (ProTeCTR) web site. As only the incumbent contractor has access to this internal Sharepoint site, could the Government please provide a copy of the AEA IPT Process and Procedures for all competitors?

Government Response: Offerors do not need access at this time and access does not provide the incumbent with a competitive advantage.

The following have been deleted:

Q & A'S - AMENDMENT 01

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

C-TXT-PWS

PERFORMANCE WORK STATEMENT

FOR

AIRCRAFT ELECTRONIC WARFARE WEAPONS SYSTEMS MODIFICATIONS

16 October 2013

1.0 SCOPE

The objective of this Performance Work Statement (PWS) is to identify and understand emerging Electro-Magnetic threats and to outpace those threats by delivering advanced fully integrated Electronic Warfare (EW) capabilities to the Fleet. This PWS satisfies this objective by establishing the requirements to conduct EW weapons systems modifications to include weapon system software, on-call field engineering analysis, test and evaluation, studies and analysis, threat analysis and sensor intelligence mission data files, jammer techniques development and logistics for distribution of Operational Flight Programs (OFPs) to the Fleet. EW systems to be modified under this contract are for Fleet requirements and Foreign Military Sales (FMS) and include: EA-6B, EA-18G, E-2C, MH-60R, BAMS, P- 8A, Unmanned Air Systems, flight simulators, training systems, other advanced electronic attack derivatives and initiatives These requirements will be provided within the Airborne Electronic Attack Integrated Product Team (AEA IPT) located at the Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, California.

As identified in each Task Order (TO), the contractor shall provide systems engineering, in-service hardware and software engineering, intelligence data analysis, test and evaluation, EW systems development, threat analysis, threat defeat, mission planning, and EW data development to include:

Electronic Warfare Data Systems (EWDS) including the retrieval and modification of intelligence data for Order of Battle, Characteristics and Performance, library data, and tactical data that is sensor engineered for Naval Aviation Enterprise tactical receiver systems

Electronic Warfare Information and Report Management System (ETIRMS) Unique Planning Component (UPC) for the Naval Aviation Enterprise

Jammer Technique Optimization (JATO) including threat analysis, ALQ-99 jamming technique modifications, JATO Tactics Analysis Technique (JTAT) development, Fleet deployment and schoolhouse briefings, in addition to laboratory and open air range test events

Electronic Warfare Laboratory Simulations ALQ-231 Intrepid Tiger Pod EA-18G and EA-6B AEA Unique Planning Component (UPC) and related Electronic Warfare planning components Next Generation Jammer (NGJ) Electronic Warfare Battle Management (EWBM) HAWKTool Unique Planning Component AEA Expendable Stand in Jammers

1.1 BACKGROUND

1.1.1 The NAWCWD has been designated as the Weapon System Support Activity (WSSA) providing direct Fleet services through design and development of updates to the EA-6B avionics/weapons systems. The EA-6B WSSA is assigned the responsibility to perform analysis, design, development, integration, test, and distribution of all OFPs to the Fleet, to perform final system integration for all improvements, to develop mission data capabilities as required by OFP changes, and to provide independent technical evaluation and testing.

1.1.2 PMA-234 and PMA-265 have chartered the WSSA to provide the development of the Navy's new AEA platform, the EA-18G. PMA-265 has designated the AEA IPT as the Software Support Activity (SSA) for the Electronic Attack Unit (AEU) software, including the responsibility to analyze, design, develop, integrate, test and distribute all OFP and mission data capabilities required by OFP changes, to perform final system integration for all improvements and to provide independent technical evaluation and testing of changes.

1.1.3 The AEA IPT is a Capability Maturity Model Integration (CMMI) accredited NAWCWD government and contractor team consisting of over 250 personnel stationed at Point Mugu, California. The team provides complete Electronic Attack (EA) and Electronic Surveillance (ES) Joint Mission Planning System (JMPS) Mission Planning systems and software modifications for EA-6B, EA-18G, E-2C and MH-60R, plus future naval platforms such as F- 35 (JSF), P-8A Multi-mission Maritime Aircraft (MMA) and Broad Area Maritime Surveillance (BAMS). The team serves as the EA-6B Prowler WSSA, producing OFP and conducting systems engineering and integration of avionics and weapon system upgrades. The team serves as the EA-18G Growler AEA SSA, producing OFP and conducting systems engineering and integration of avionics and weapon system upgrades. The team also provides jamming techniques optimization and world emitter databases to enable naval airborne Electronic Attack and Electronic Support implementation around the world. The teams are principally focused on EW for the Naval Aviation Enterprise (NAE).

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to this PWS. The most current versions will be used. Additional documents may be specified and will be identified at the TO level. Documents not publically available will be provided.

2.1 MILITARY STANDARDS

ANSI/EIA-649-B 2011 National Consensus Standard for Configuration Management GEIA-STD-0007 Version 1.0, August 2007, Logistics Product Data MIL-HDBK-61A, 7 February 2001, Configuration Management Guidance MIL-STD-464C, 01 December 2010, Department of Defense Interface Standard: Electromagnetic Environmental Effects, Requirements for Systems.

MIL-STD-961E (w/Change 1), 2 April 2008, Standard Practice for Defense and Program-Unique Specifications, Format and Content MIL-STD-1553B, 15 January 1996, Interface Standard for Digital Time Division Command/Response Multiplex Data Bus.

MIL-STD-1806, 12 June 1995, Marking Technical Data Prepared by or for the Department of Defense.

MIL-STD-6016E (w/Change 1), 2 April 2008, Department of Defense Interface Standard Tactical Digital Information Link J Message Standard

2.2 INSTRUCTIONS AND GUIDES

NAWCWDINST 5500.1, 13 February 2012, Command Security Program Regulation.

Naval Systems Engineering Guide – October 2004; located at https://acc.dau.mil/adl/en- US/25837/file/55165/NAVAL_SYSTEMS_ENGINEERING_GUIDE_OCT2004.pdf.

National Telecommunications and Information Administration (NTIA) Manual of Regulations and Procedures for Federal Radio Frequency Management, “Radar Spectrum Engineering Criteria (RSEC)”, May 2011.

AEA IPT Processes and Procedures, September 2013 (located at: AEA SharePoint Program Team Collaboration Tool and Repository (ProTeCTR) web site.), https://share.navair.navy.mil/aeaipt/Pages/IPTHome.aspx.)

2.3 INDUSTRY STANDARDS

Software Development and Documentation, IEEE/EIA 12207.0, (1998), IEEE/EIA 12207.1, (1998), AND IEEE/EIA 12207.2, (1998). CMU/SEI-2002-TR-O 12, March 2002, Capability Maturity Model Integration (CMMI), -Version 1.3 CMMI for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing (CMMI-SE/SW IIPPD/SS, V 1.1) -Staged Representation, Carnegie Mellon University

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.

2.4 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 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. DoDD 5000.01 “The Defense Acquisition System,” 12 May 2003, Certified Current as of 20 November 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” 8 December 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” 8 March 2002

d. SECNAVINST 5000.2E, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” 1 September 2011

2.5 INFORMATION ASSURANCE (IA)

NAVAIR’s Information Assurance (IA) 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. IA is required operationally throughout the DON. DON CIO (Chief Information Officer) is responsible for 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 IA shall be in compliance with the following listed instructions to include those referenced within the below listing:

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

b. Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3170.01 (series), “Joint Capabilities Integration and Development System”, 10 January 2012

c. CJCSI 6211.02 (series) – “Defense Information System Network (DISN): Policy and Responsibilities,” 24 January 2012

d. CJCSI 6212.01 (series) – “Interoperability and Supportability of Information Technology and National Security Systems,”21 March 2012

e. CJCSI 6250.01 (series) – “Satellite Communications,” 30 November 2012

f. CJCSI 6510.01 (series), “Information Assurance (IA) and Computer Network Defense (CND),” 9

February 2011

g. Chairman of the Joint Chiefs of Staff (CJCSM) 6510.01 (series) – “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. DoD 5220.22-M, “National Industrial Security Program Operating Manual,” February 28, 2006

(NISPOM)

k. DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, 19 Dec 2005 (Incorporating Change 2, Feb 25, 2010)

l. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” February 10,

m. DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April

n. DoDD 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

o. DoDD 8570.01 “Information Assurance Training, Certification, and Workforce Management,” August 15, 2004, Certified Current as of April 23, 2007

p. DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

q. DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

r. DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP),”

November 28, 2007

s. DoDI 8520.02, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 24 May 2011

t. DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

u. DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

v. DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the Department of

Defense,” June 8, 2010

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

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

y. Federal Information Processing Standards Publications (FIPS PUB)

[http://www.itl.nist.gov/fipspubs/by-num.htm]

z. (National Security Telecommunications and Information Systems Security Policy) NSTISSP No. 11, “Revised Fact Sheet National Information Assurance Acquisition Policy,” July 2003.

For more information on determining the applicability of these documents to the specific requirements of your program, contact your local information assurance point of contact for assistance. An IA POC is available via the NAVAIR National Help Desk at https://nhd.navair.navy.mil or 1-888-292-5919

2.6 ENTERPRISE ARCHITECTURE

Contractor Networks and connections: Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided VPN Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

IT Approval: The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

3.0 REQUIREMENTS

The Government will provide the specific technical documentation, guidelines and delivery requirements under individual TOs. When ordered and as specified under individual TOs, the contractor shall provide the following technical services:

3.1 WEAPON SYSTEMS SOFTWARE

3.1.1 Systems Engineering. The contractor shall provide systems engineering, in accordance with the Naval Systems Engineering Guide. Systems engineering shall include analysis, design, development, fabrication of new and existing EW laboratories, prototyping, integration, test, evaluation, repair, maintenance, and documentation of hardware, development and installation of physical laboratory assets, software and firmware. The contractor shall develop Engineering Change Proposal (ECP) activities to include updating and creating new engineering drawings, and technical/programmatic activities for the laboratory, test networks and avionics systems. (CDRLs A001, A003, A00C, A00P)

3.1.1.1 The contractor shall (1) conduct studies and analyses to develop system concepts, including functionality and performance requirements for existing, upgraded, and new systems; (2) identify life cycle requirements; (3) define interface requirements; and (4) prepare requirement and functional baseline specifications, plans and documents. (CDRL A001)

3.1.1.2 The contractor shall develop or evaluate ECPs and Technical Directives (TDs) to establish requirements, testability, and technical merit. The contractor's evaluation shall include risk assessment and recommendations for acceptance or rejection. (CDRLs A00C, A00J)

3.1.2 Tactical Data Links. The contractor shall design and develop software and engineering tools to enable the integration and maintenance of data, voice, and image link communication systems (to include the Multi-Mission Advanced Tactical Terminal (MATT) and Link-16 Tactical Terminals) and tactical data broadcasts. Link protocols shall include Link 16, Variable Message Format, Distributed Common Ground System – Navy, Cooperative Engagement Capability, Network Centric Collaborative Targeting, Global Command and Control System – Maritime and the Joint Area Layer Network that includes the Maritime Area Layer Network and Battle Force Tactical Network. Tactical data broadcasts shall also include the Integrated Broadcast Service. (CDRLs A00B, A00R)

3.1.3 Software Development. The Contractor shall provide systems software development to include analysis, research, development, integration, test, evaluation, proof of concept development, and software tools. Software prototypes shall be developed for Government efforts to evaluate alternative solutions and implementations for specific intelligence, information, imagery, EW and mission support systems and equipment, or to create environments based on mission requirements or manage the data necessary to model, simulate or evaluate test results. (CDRLs A001, A008, A009)

3.1.3.1 Included in software modifications are EW platform avionics simulations, distributed testing including Test and Training Enabling Architecture (TENA), Distributed Interactive Simulation (DIS), High Level Architecture (HLA) protocols, single processor and parallel processor systems, High Performance Computing (HPC), analytical tools for Fleet support activities such as post flight analysis, self-jamming analysis, math modeling, and Jammer Threat Analysis (JTA). The contractor shall participate as a member of the Statement of Requirement (SOR) Government Task Team, Defect Control Review Board (DCRB), Test Integration Team, and the Operational Software Review Board (OSRB), as a EW subject matter expert (SME) in the EW field. The Contractor shall integrate the developed software into the specified systems’ environment, including delivery of necessary hardware

(or modified hardware), to support execution of that software, into the appropriate laboratory. The Contractor shall follow software development guidelines using applicable Government or industry standards specified by the Government. (CDRL A00R)

3.1.3.2 Process Improvement: The contractor shall optimize software development to improve AEA IPT software processes where applicable.

3.1.3.2.1 The contractor shall gather requirements, design, develop, code, integrate and test SharePoint software and other third party software add-ons to increase the functionality of the baseline AEA SharePoint Program Team Collaboration Tool and Repository (ProTeCTR) site. Increased functionality includes integration of Navy Enterprise Resource Planning (ERP) financial data, Earned Value Management (EVM) and reporting; collection and reporting of resource metrics required by the IPT's process improvement initiatives; and collection and reporting of metrics required to respond to programmatic data calls; etc. The contractor shall investigate, analyze, recommend, and upon government approval execute corrective action for any SharePoint site deficiencies, software bugs and software change proposals for the AEA ProTeCTR.

3.1.3.2.2 The contractor shall collect software development measurements in accordance with the TO Measurement Analysis Plan (MAP) retained within the AEA SharePoint Program Team Collaboration Tool and Repository (ProTeCTR) web site. The contractor shall collect the metric data using the IPT's established processes/procedures.

(CDRL A001).

3.1.4 Software Requirements: The contractor shall perform Software Requirements Analyses that define and analyze a complete set of functional, performance, interface, operators, and qualification requirements for each Computer Software Configuration Item (CSCI). (CDRL A001)

3.1.4.1 The contractor shall develop requirements at a top-level, detailed, and/or lower level modular design for each Computer System Configuration Item CSCI. A detailed design of each CSCI shall be generated. (CDRL A009)

3.1.4.2 The contractor shall code, integrate and test each software unit within the detailed design. Informal unit testing will be in accordance with the applicable Software Test Plan.

3.1.4.3 The contractor shall: (1) verify designated computer software requirements and computer program/hardware interface requirements against the existing hardware and software requirements and any hardware and software modifications that occur throughout the period of performance; (2) evaluate computer program design as it develops; (3) verify coding to ensure that any changes do not adversely affect performance; (4) perform independent CSCI level tests in accordance with test plans as approved or generated by the Government for each CSCI; (5) evaluate the software test programs in order to ensure that they meet the current software configuration;

and (6) provide post test analyses. The contractor shall identify conflicting, not testable, ambiguous requirements affecting software functions, as well as inadequate software data requirements. (CDRLs A008, A009, A00A)

3.1.4.4 The contractor shall verify the software by conducting independent testing, code analysis, algorithm analysis, and review of the test procedures and results. Software portions may include functional areas to be verified include critical to safety, equipment selection, mission critical performance, development schedule, software reuse, and sustainability and supportability.

3.1.5 Software Life Cycle Maintenance: The contractor shall provide enhancements and corrections to developed software through the use of Software Trouble Reports (STRs), Software Change Requests (SCRs), Software Change

Proposals (SCPs), and Discrepancy Reports (DRs) that have been generated by the Fleet. These artifacts are maintained by the government tracking system within the AEA SharePoint Program Team Collaboration Tool and Repository (ProTeCTR) web site. (CDRL A00A) The contractor shall participate in software design reviews, test readiness reviews, audits, code walk-through, working group meetings, and monitor qualification tests. (CDRL A002)

3.1.5.1 The contractor shall enter STRs, SCRs, SCPs, and DRs into the government tracking system and update status throughout the investigation and resolution process. The contractor shall process these reports by conducting a preliminary engineering investigation to: (1) confirm that a change request is truly a new requirement or a result of a software deficiency and is not merely a symptom of a hardware malfunction, improper operation procedure or maintenance action; (2) confirm the problem has not been previously reported; (3) determine technical approaches to solving the problem or implementing the enhancement; and (4) provide impact analyses for each approach. Based on the results of the preliminary engineering investigation, the contractor shall prepare a preliminary SCP for SCRs and STRs to be processed through internal review, Operational Software Review Board (OSRB), Technical Review Board (TRB), Software Change Review Board (SCRB) and the SCP Review. (CDRL A00A)

3.1.5.2 The contractor shall develop the correction for a DR or approved software change proposed in the SCP.

Developing the correction or approved software change shall include requirements review, detailed software design, coding, debugging, integration and testing. The SCP shall be implemented with marked-up requirements documents, specifications, and software design documentation. (CDRL A00A)

3.1.5.3 The contractor shall conduct the testing of SCPs by developing test procedures, conducting the test, and documenting the results. (CDRL A008, A009)

3.1.5.4 The contractor shall code and debug software changes to implement the approved engineering solutions, and shall deliver software, including source and load files. Software languages may include CMS-2M, TDY -43 assembly, 8080 family assembly, FORTRAN, PLM, PASCAL, C++, ADA, Visual Basic, C-Sharp and .NET. The contractor shall provide redlined change pages for specifications and user documentation impacted by each engineering solution. (CDRLs A00B, A00C, A00R)

3.1.5.5 The contractor shall conduct problem investigation and analysis on OFPs, Mission Support Programs (MSPs), Mission planning activities associated with UPCs, and databases to identify deficiencies and coordinate block related activities. The contractor shall provide the results of the analysis and the proposed engineering solutions in written problem investigation reports. (CDRL A00l)

3.2 ON-CALL FIELD TECHNICAL SERVICES

3.2.1 The contractor shall provide field technical services on an "on call" basis for the purpose of Fleet system installation, maintenance, troubleshooting and repair, training and test event and technical systems and subsystems testing. The contractor shall submit a trip report documenting the results of on-call technical efforts. (CDRL A001)

3.2.2 The contractor shall provide JATO Fleet Liaison Team (FLT) mission analysis to include Pre-deployment Briefings (PDBs), Schoolhouse (EAWS, MAWTS-1, NSAWC) Briefings, and Subject Matter Expertise (SME) to the war fighter. (CDRLs A00K, A00L)

3.2.3 The contractor shall provide training to the Fleet by providing training and preparing training material in specialized and advanced EW technical areas. (CDRLs A00K, A00L)

3.2.4 The contractor shall provide military theatre specific briefings that look at the threats and Techniques, Tactics, and Procedures (TTPs) (JTAT review) that a squadron of EA-6B's or EA-18G's might encounter. The contractor shall attend briefings on intelligence updates provided from the Navy Information Operations Command (NIOC) and/or Radio Battalion (RADBN). The military theatre specific briefings shall summarize the analysis of optimized TTPs for a specific geo-political area (theatre), tailored to target categories that include Radar, Communications, Force Protection, and Advisory Jammers. (CDRLs A00K, A00L)

3.2.5 The contractor shall provide mission analysis that leverages TTPs and technology knowledge and experience to provide guidance and recommendations to proposed, new, and mature system development programs through evaluation of changes/improvements to a given jammer weapons system, assisting with risk identification, and developing risk mitigation strategies for identified risks. This shall include analysis of effectiveness, system limitations, and any interoperability guidelines. One-vs-Many techniques shall be generated to cover multiple threats with a single jamming technique. (CDRL A001)

3.2.6 The contractor shall include new or updated jamming techniques in Rapid-Reaction Files (RRF) or database transaction files developed and released by the government led Electronic Warfare Data Systems team. The data update shall be tested through installation on mission planner, aircraft load, and operation in aircraft system to RF output. Verification shall be performed on all applicable aircraft configurations within the AEA laboratories.

3.2.7 The contractor shall develop jamming techniques provided from Foreign Military Exploitation (FME). Test data shall be collected from similar threat systems if no direct FME is available. Modeling and Simulation and laboratory testing shall also be used to investigate possible Electronic Attack strategies.

3.3 TEST AND EVALUATION

3.3.1 The contractor shall plan, prepare and upon written Government approval conduct tests, experiments, system simulations, and demonstrations in support of Integrated Systems/Subsystems Testing, Developmental Flight Testing and Operational Flight Testing. The contractor shall evaluate test plans to ensure consistency with systems specifications, including requirements traceability-and ensure that testing is conducted. The contractor shall conduct tests to verify and validate compliance with system specifications. (CDRL A001)

3.3.2 The contractor shall provide technical development and initial testing of radar transmitter, receiver, antenna, and signal processors using Commercial-off-the-Shelf (COTS) hardware such as digital waveform generators, single shot digitizers, time interval frequency analyzers, electronic counters, and advanced signal processing software.

3.3.2.1 The contractor shall test receiver, transmitter and antenna system components, preprocessors and signal processors using commercial hardware and advanced signal processing software. Testing may be required early in the program development cycle and continued at selected milestones during the program. The contractor shall test and evaluate EW systems to quantify:

Emitter Detection Performance Threat Classification Classification and ID Capabilities Receiver Characteristics Signal Sorting Beam Forming Protection of Self Jamming Global Positioning System (GPS) Self Jamming Communication Measurement of Jamming Performance

Expected System Performance

3.3.2.2 The Contractor shall provide testing operations to include: On-site, coordination, scheduling, planning, briefing, evaluation, and de-briefing between aircrew and external test organizations, flight test planning and logistics, and Fleet exercise experimentation.

3.4 STUDIES AND ANALYSIS

3.4.1 The contractor shall provide design trade-off and risk assessment studies. (CDRL A001) System analysis will include time and sensitivity analyses. The contractor shall provide recommendations on the most cost-effective approach to systems development and maintenance through its life cycle. Those areas for application of state-of-the-art methodologies, including COTS and Non-Developmental Item (NDI) will be identified which will provide the highest payoff in system performance, cost, reliability, and maintainability.

3.4.1.1 The contractor shall review, evaluate, and verify that developed system, subsystem, configuration item, and support equipment specifications meet the required technical adequacy.

3.4.1.2 The contractor shall perform analytical studies and evaluate defense system safety, survivability and vulnerability in a man-made hostile environment. The environments to be considered may include conventional, electronic, directed energy, and asymmetric warfare.

3.4.1.3 The contractor shall provide technical reviews, analyses, and recommendations to ensure equipment and subsystems are electromagnetically compatible with the external environment in accordance with MIL-STD-464C and NTIA RSEC.

3.4.1.4 The contractor shall perform technical analyses and evaluations, review documentation, and provide recommendations in the areas of:

System Safety Antenna Technology Digital Signal Processing Solid State Module Technology Pulse Compression Techniques Situation Displays Electronic Countermeasures and Counter-countermeasure Techniques State-of-the-Art Digital and Analog Communications

3.4.1.5 The contractor shall perform EW related technical systems engineering tasks such as:

Preemptive Assignment- On-Sight Coordination of jamming assignments Test Jamming Techniques Development Responding to Fleet Personnel on EA Technical Content Providing Real Time Operational and Technical Electronic Intelligence (ELINT) Expertise Providing EA Technique Recommendation Researching Threat Systems Using Multiple Intelligence Gathering Sources

3.4.1.6 The contractor shall develop JTATs to document analysis of optimized AEA TTPs for a specific geo-political area, tailored to target category, i.e., Radar, Communications, Force Protection, and other Navy identified target categories.

3.5 DOCUMENTATION

3.5.1 The contractor shall develop and maintain systems software documentation. (CDRLs A006, A007, A008, A009, A00B, A00D, A00E, A00F, A00G, A00H). The contractor shall revise or update documentation in the same format as the existing document including the following:

Functional Operational Specification (FOS) Independent Verification & Validation (IV&V) Plans Interface Design Specification (IDS) Test Plans and Procedures Program Performance Specification (PPS) Configuration Management Plans Program Design Specification (PDS) Software Development Plans Software Design Document (SDD) System Requirements Specifications (SRS) Interface Design Document (IDD) Systems/Segment Specification (SSS) Software Requirements Analysis (SRA) Test Reports Software Support Requirements Analysis (SSRA) Training Plans

Individual TOs will provide technical requirements and CDRL item development and submittal instructions.

3.6 THREAT ANALYSIS AND SENSOR DATA MODIFICATIONS

3.6.1 The contractor shall conduct threat analyses to identify the potential vulnerabilities of coherent and non-coherent standoff jamming techniques. (CDRL A001) These analyses shall be performed independently of current technique repertoire so as not to limit the definition of exploitable threat vulnerabilities. The contractor shall update analytical models of threat ECCMs and signal processing techniques to characterize threat vulnerability to various ECM techniques using models and simulation, and perform functions including Good/Fair/Poor Analysis and updates to the updates to the Information Operations Joint Munitions Effects Manuals (IO JMEM). The output of this task shall be a list of candidate ECM techniques for early warning, search, acquisition, and target tracking radars.

3.6.2 The contractor shall perform analyses and studies of the evolutionary development of existing Intelligence and Analysis (I&A) and tactical warning and assessment systems (Terrestrial and Space) as they relate to avionics integration into Command and Control Warfare (C2W) aircraft such as the EA-6B, EA-18G, as well as experiments and demonstrations to test the conclusions of the studies. (CDRLs A008, A009)

3.6.2.1 The contractor shall perform EW Intelligence Analysis (EWIA) to model and characterize red, blue and white Weapon, Platform, Radar and Communication systems for updates to the EW Data Systems databases and for use in the ETIRMS Mission Planning Applications within the Naval Aviation Enterprise. The contractor shall review various intelligence data and tailor the parametric data for the required products including databases, phone conversations, messages, and correspondences. The contractor shall make use of the following tools during this analysis; (1) Modernized Integrated Database (MIDB); (2) Electronic Intelligence (ELINT) Parametric List (EPL);

(3) Electronic Warfare Integration and Reprogramming (EWIR) databases (including the Next Generation EWIR System); and (4) Generic Area Limitation Environment-Lite (GALE-Lite).

3.6.2.2 The contractor shall perform analyses to evaluate the impacts of the proposed utilization of the AN/ALQ-99 universal exciter system, Universal Exciter Upgrade (UEU), coherent jamming and target systems in the EA-6B and EA-18G tactical jamming system, and that of other platforms evolved to cover the EW capability gaps of the Fleet user. (CDRL A001)

3.6.2.3 The contractor shall research, analyze, identify, describe, review, and coordinate the development of interoperability and standardization requirements for C2W intelligence, and EW systems. The contractor shall update the system documentation. (CDRL A003)

3.6.2.4 The contractor shall, in coordination with government activities, develop and deliver weekly Transaction File Updates and periodic Rapid Reaction Data Updates to Integrated Test and Evaluation activities in addition to the Fleet squadrons. Efforts shall include Database development using Access and Oracle applications. (CDRL A001)

3.6.2.5 The contractor shall review updates from the following weapon systems and update associated EW Data Systems:

HARM and AARGM seeker receiver interfaces and performance characteristics.

Post-flight data analysis from EA-6B, EA-18G, MH-60R, E-2C/D, P-3, P-8A, BAMS mission recordings.

ALQ-99, ALQ-210, ALQ-214, ALQ-217, ALQ-218, ALQ-227, ALQ-231, and USQ-113 Receiver

Interfaces and performance characteristics.

ALQ-99, ALQ-227, ALQ-231 and USQ-113 Jammer Interfaces and performance characteristics.

APG-65, APG-71, APG-73 and APG-79 Radar Interfaces and performance characteristics.

3.7 JAMMER TECHNIQUES DEVELOPMENT

3.7.1 The contractor shall collect radar waveform signature measurements, conduct advanced signal processing and perform analysis by exploiting unintentional frequency modulation, amplitude modulation, and/or phase modulation for waveform identification. (CDRL A001)

3.7.1.1 The contractor shall develop Electronic Support Measurement (ESM), Electronic Counter Measure (ECM) and intelligence receivers, preprocessors, classification and identification processors to handle modern and complex phase coded, frequency coded, and electronic parameter controlled radar waveforms including the AN/ALQ-218, and other EW weapons systems trainers. New system architecture's and receivers, specialized signature extraction units, and high quality signal processing algorithms shall be developed and employed.

3.7.1.2 The contractor shall develop technical, tactical, operational, and programmatic measures of effectiveness for EW systems and recommend performance criterion for operational test and evaluation scenarios. Tasks may include utilization of the High Performance Computer for effectiveness studies involving complex threat emitter avoidance route planning and jammer optimization, mission rehearsals of tactics, techniques and procedures, strike effectiveness assessments.

3.7.1.3 The contractor shall design and develop a database of applicable ECM techniques. The data will incorporate the ECM system parameters of current and planned ECM systems. These parameters may include but are not limited to: RF range, angular coverage, jammer effective radiated power/repeater gain, ECM receiver sensitivity, ECM technique repertoire and waveform characteristics, and system resource/power management rules. Existing threat system databases will be updated to incorporate the most recent intelligence information. The contractor shall develop comprehensive databases for early warning, search, acquisition, and terminal threat target tracking radars and communication systems operating within the RF coverage of the AN/ALQ-99 tactical jamming system, and the coverage of other specified system’s AEA components.

3.7.1.4 The contractor shall design and develop Threat Simulation Tools, by using Advanced Mission Environment Simulator (AMES), Electro-Magnetic Environment (EME), commercial waveform generators.

3.7.2 Communications Jamming. The contractor shall design and develop software and engineering tools to enable the EA-6B USQ-113, EA-18G ALQ-227 and AN/ALQ-231 jamming of threat communication systems.

(CDRLs A00B, A00C, A00R)

3.8 LOGISTICS

3.8.1 Technical Publications. The contractor shall prepare technical publication revisions and new technical publications including technical drawings, lists, and instructions. (CDRLs A003 and A00J)

3.8.2 Review of Logistics Data. The contractor shall review and comment on logistics documentation, technical publications, data and reports to ensure that they accurately represent the updated software and data products defined herein. (CDRL A001)

3.8.3 The contractor shall provide recommendations on best practices to manage the configuration of software requirements. The contractor shall develop, update, and implement the plans, procedures, and actions for identifying, controlling, and verifying the engineering artifacts of acquisitions. The contractor shall establish procedures to: (1) identify and assure the integrity of documentation for the functional and physical characteristics of each Hardware Configuration Item (HWCI) and CSCI; (2) control the changes to the HWCI and CSCI characteristics; and (3) record and report the processing of changes and the status of their implementation. Efforts shall be as detailed within the following sub-paragraphs. (CDRL A001)

3.8.3.1 The contractor shall: (1) assess the impact of changes to system configuration item specification; (2) ensure that configuration items are physically and logically compatible; (3) assess the impact of changes; and (4) perform documentation traceability.

3.8.3.2 The contractor shall upgrade and maintain an automated configuration management and tracking database as defined in individual TOs.

3.8.4 Configuration Data: The contractor shall provide weapon system modification configuration data that includes the identification and control of programmatic documents. This involves the identification, coordination, collation, validation, integration, control of data requirements, support the Government with planning for the Government’s timely and economical acquisition of data, ensuring the adequacy of acquired data for its intended use, and management of data assets after receipt. Efforts shall as detailed within the following sub-paragraphs.

(CDRLs A001, A00J)

3.8.4.1 The contractor shall check the data for completeness, verify page count, and provide quality assurance review of the format. The contractor shall distribute the data (including change pages), monitor storage, retrieval, and disposal of data.

3.8.4.2 The contractor shall enter data elements into the government’s automated Data Management tracking system and maintain the associated database and generate reports using ClearCase, ClearQuest, and Dynamic Object Oriented Requirements System (DOORS).

4.0 DATA DELIVERABLES

Specific items of reports, test plans, procedures, technical support documents, meeting minutes, and progress reports will be provided in accordance with the applicable Contract Data Requirements Lists (CDRLs).

CDRL ITEM DESCRIPTION

A001 Technical Reports – Study/Services A002 Presentation Material A003 Revisions to Existing Government Documents A004 Contractor’s Progress, Status and Management Report (Monthly)

Contractor’s Progress, Status and Management report (Weekly) A005 Funds and Man-hour Expenditure Report (Financial and Cost Graphs)

Funds and Man-hour Expenditure Report (Contract Summary Report) A006 System/Subsystem Specification (SSS) A007 Software Design Description (SDD) A008 Software Test Plan (Plan, Procedures and Reports) A009 Software Test Report (STR)) A00A Technical Reports – Study/Services (STRs, SCRs, SCPs, and DRs) A00B Computer Program End Item Documentation A00C Engineering Changes (ECP, NOR, RFD, TD) A00D System/Subsystem Design Description (Software Documentation) A00E Interface Design Description A00F Contractor’s Configuration Management Plan A00G Software Development Plan (SDP) A00H Software Requirements Specification (SRS) A00J Technical Reports – Study/Services (Technical Publications) A00K Conference Agenda A00L Conference Minutes A00M Operations Security (OPSEC) Plan A00N Incurred Cost and Progress Reporting Invoice Support Report A00P Engineering Drawings A00R Computer Software Product

5.0 SPECIAL CONSIDERATIONS

5.1.1 Travel. During performance of a TO, the contractor may be required to perform local and non-local travel to support the tasking. The contractor shall submit a request for travel in support of this contract. Each request shall be submitted in advance (a minimum of 1 week) to the Government Contracting Officer's Representative (COR) for approval. The estimated travel for the performance period of Five (5) year is documented below:

Total estimated # of trips

Estimated # of personnel per trip

Estimated # of days per trip From To

30 4 4 Point Mugu, CA Whidbey Island, WA 17 1 4 Point Mugu, CA Washington DC 6 1 5 Point Mugu, CA PAX River, MD

33 2 4 Point Mugu, CA China Lake, CA 15 3 4 Point Mugu, CA Irvine, CA 40 4 5 Point Mugu, CA Nellis AFB, NV 20 2 4 Point Mugu, CA Fallon, NV 10 1 5 Point Mugu, CA Tonopah, NV

Total estimated # of trips

Estimated # of personnel per trip

Estimated # of days per trip From To

15 1 4 Point Mugu, CA Lexington, MD 16 1 4 Point Mugu, CA Baltimore, MD 2 1 3 Point Mugu, CA St. Louis, MO

10 2 4 Point Mugu, CA Cherry Point, NC 20 2 4 Point Mugu, CA Yuma, AZ 7 2 5 Point Mugu, CA Eglin AFB, FL 6 1 2 Point Mugu, CA El Paso, TX

10 2 8 Point Mugu, CA Slovakia 10 1 8 Point Mugu, CA Milan, Italy 5 1 4 Point Mugu, CA Indianapolis, IN 5 3 10 Point Mugu, CA Iraklion, Greece 5 1 8 Point Mugu, CA Brussels, Belgium

10 2 5 Point Mugu, CA Elmendorf AFB, AK 4 1 10 Point Mugu, CA Atsugi, Japan

Each travel request will minimally consist of:

Date of Request TO 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 Approval signatures

Upon completion of each trip, the contractor shall submit a trip report (CDRL A001)

5.1.2 Security. During performance of this contractor, the contractor may need access to material up to and including Top Secret/Sensitive Compartmented Information (TS/SCI) level. Access will be limited to the individual contractor employee’s security clearance level and need to know. The contractor may need to attend briefings/conferences at the SCI level. The contractor shall comply with all Security provisions of the basic Security Classification Specification, DD Form 254.

5.1.3 Place of Performance. Approximately 90% of performance is expected to take place at Pt. Mugu, CA at a Government facility or the contractor’s facility. The other 10% may take place at other Government installations identified at the Task Order level. Including anticipated requirements for at least one employee each at both Naval Air Station Whidbey Island and Nellis Air Force Base to provide On-Call Field Technical Services directly to military personnel. Support for multiple sites, including direct Fleet services that require SECRET clearance will be required. The specific sites are provided in Section 5.1.1.

5.1.4 Access to…