13-R-0011_Amd_0001.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 Government responses to offerors questions. Additional updates have also been made to the Performance Work Statement (PWS), Section L and Section M.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 52

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

16C. DATE SIGNED

BY 08-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 X is extended, 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

08-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 required response date/time has changed from 31-Oct-2013 04:00 PM to 07-Nov-

2013 03:00 PM.

The following have been added by full text:

Q & A'S - AMENDMENT 01

Questions and Answers

Amendment 01

NOTE: The page numbers referenced below are from the original RFP. This amendment will change the number of pages.

Q. 1 – It is stated on page 79 of the solicitation that the anticipated award date is February 1, 2014. However, the period of performance listed on page 31 states that it will begin January 6, 2014.

A. 1 – Page 31 Period of Performance has been changed to begin 28 January 2014 and the anticipated award date on page 79 has been changed to 28 January 2014.

Q. 2 – On page 93 of the RFP, under 4 – Relevancy, it states that the offeror must identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place. Will the government grade lower those past performances not directly associated with Pt Mugu?

A. 2 – No, the Government will not lower the grade/rating for past performance outside of Pt. Mugu.

Q. 3 - Section L, 4.5.1 ODCS. The total for the travel, material, and other costs equals $2,727,452; however the total reflects $2,072,226. Please confirm that the total reflected in the table should be $2,727,452.

A. 3 - Section L, 4.5.1 ODCs has been changed to reflect the correct amount $2,072,226.

Q. 4 - Section L, 4.5.1 ODCs. For pricing purposes, should the travel, material, and other costs be divided evenly between the five years?

A. 4 – The table has been updated to show the breakout for the five years for Travel and Material/Other Direct Costs (ODCs)

Q. 5 – In reference to PWS paragraph 5.1.3, please provide the anticipated breakout of performance at the Government versus Contractor site facilities.

A. 5 – It is assumed that the contractor site facility would be in close approximation (30 minute drive) to Pt. Mugu and therefore no breakout has been developed. The majority of the work is performed on the Government site.

Q. 6 - In consideration of the very strict numbering requirements in Section L page 81, paragraph 2.3, should the Key Personnel Resumes be included in 2.1.1 or 2.1.2 of our proposal response?

A. 6 – See revised Section L, as resumes are no longer required. Also, the page count has been increased.

Q. 7 - In consideration of the very strict numbering requirements in Section L page 81, paragraph 2.3, does the contractor need to present anything for 2.1.3?

A. 7 – No, you do not need to provide anything with regards to paragraph 2.1.3 (Section 2.0 – Volume 2: Technical).

Paragraph 2.1.3 is providing information regarding the Labor Category Qualifications and Security Clearances that are required for this contract. Also, the page count has been increased.

Q. 8 - Is the Workforce Qualifications Spreadsheet a Table and therefore excluded from the page count?

A. 8 – Yes, it is excluded from the page count (see 3.0 Proposal Content and Volumes, Section 3.4 states that all attachments are not included in the page count).

Q. 9 - In order to be compliant with the page numbering requirements, could the government please confirm that 2.1 LCAT (Labor Categories) Information is also excluded from the page count?

A. 9 – Yes, as this paragraph is for information only and it has been revised to delete the requirement for resumes.

Q. 10 - On page 82 of the RFP, it states that the subcontracting plan is excluded from the page count. Please confirm this includes all of 2.2 and not just 2.2 (2).

A. 10 – Yes, all subcontracting plans as described in all of Section 2.2 of the RFP are excluded from the page count.

Q. 11 - Please confirm “Graphs” on page 81, section 2.1 and the 10 pt. font allowance refers to the font in graphics and tables.

A. 11 – Yes, the 10 point font allowance refers to the font in the graphics and tables.

Q. 12 - Section L, 2.0, Volume 2: Technical, states the volume shall not contain any reference to cost or price aspects of the offer. However Section L, 2.2 (2), references SB Subcontracting Plan which typically contain cost information to be included in the Technical volume. Can the Government confirm: (1) The SB subcontracting plan should be a part of the Volume 4, Cost Proposal and not Volume 2, Technical and (2) Only the SB Strategy shall be included in the Volume 2, Technical?

A. 12 – The subcontracting plan should be included in Volume 4, Cost Proposal if it contains cost information.

Q. 13 – Section C – Descriptions and Specifications Subsection 6.3.2 “Labor Category Qualification’s” Page 24.

The labor category qualifications for “Analyst, Senior” stipulates “at least five (5) years of experience as a Program Analyst”. Program Analyst isn’t defined, what are the qualifications for a Program Analyst?

A. 13 – The “Senior Analyst” in the Labor Category Qualification Section has been updated to add the Program Analyst experience/qualifications.

Q. 14 – Section C - Descriptions and Specifications Subsection 6.3.2 “Labor Category Qualification’s” Page 23 “Security Clearance Requirements” Page 26. Software Engineer, Senior has six man-years provided in the LOE.

The Security Clearance Requirements for this position are 2 X SCA and 2 X Secret. In the Labor Category Qualification’s, two of the six positions are designated as Key Personnel. Are these two key personnel - Software Engineer Senior, the two SCI Positions? (Software Engineer, Senior *[2]) (2-TS/SCI and 4 – Secret)?

A. 14 – One must be TS/SCI cleared while the other can be only Secret cleared.

Q. 15 – Section L, Part B, Subsection 2.1.3.2 Page 86. For non-Key Personnel positions, how are the Security Requirements to be demonstrated/verified?

A. 15 – The contractor shall demonstrate/describe in the management proposal how they will meet this requirement.

Q. 16 – Section M, Page 104. Section M does not have a 4. The numbering goes form 3.0 Past Performance Relevancy Ratings to 5.0 Other Definitions (page 104). Is this Section 4.0 missing or is the misnumbered and Section 4 should be considered “Reserved”?

A. 16 – Past Performance Confidence Assessment Ratings should have been paragraph 4.0. It is now updated to reflect this change.

Q.17 – Section F, Page 31 5252.211-9507; Section L, Page 79 5252.215-9503. Section F States: “POP: 60 Months;

Anticipated POP: 01/06/2014 – 01/05/2019” Section L States: “Anticipated Award Date: 02/01/2014” The award Date is after the beginning of the Period of Performance. Request clarification of POP versus Award Fate for pricing purposes.

A. 17 – See A. 1 above.

Q. 18 - The Key Personnel requirement is unduly restrictive in terms of resumes of individuals required. There are seven key Labor Categories requiring 13 resumes, which is approximately one third of the LOE on this contract, that require very specific qualification descriptions, specific degree and experience requirements, and the requirements for Attachment 3 as described in Section L, paragraph 2.1.1 (RFP - page 84). These very specific requirements make finding an additional 13 people with those exact qualifications exceptionally difficult, if not impossible, in Ventura County -- especially in the few weeks available for proposal preparation.

A. 18 – Section L has been revised to remove resume requirements. The Labor Category Qualifications are from the NAVAIR Standard Labor Category Qualifications

Q. 19 – The intent of this email is to highlight what may lead to a missed opportunity for increased competition and technological innovation at a competitive price. Please let us know as soon as possible whether the solicitation will be amended and/or postponed, so we can meet the 10 October Past Performance Questionnaire delivery date to our Government contracting officers and program managers.

A. 19 – The Past Performance Questionnaire delivery date has been extended. See updated Section L, 3.0 Past Performance, paragraph 3.1.3.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0003

The pricing detail quantity has changed from UNDEFINED to 1.00.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

C-TXT-PWS

PERFORMANCE WORK STATEMENT

FOR

AIRCRAFT ELECTRONIC WARFARE WEAPONS SYSTEMS MODIFICATIONS

07 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 and in-service hardware, software and technical 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 to the extent specified herein. The most current versions will be used. Additional documents may be applicable and will be identified at the TO level. Documents not publically available will be provided upon request.

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 under individual task orders, 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, in accordance with paragraph 2.2. (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. The contractor shall track all program ECPs in accordance with the instructions provided in individual TOs. (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 shall be developed for Government efforts as identified at the TO level, related to development of software prototypes, 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 in accordance with paragraph

2.2 and 2.3 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, as identified in the individual TO. 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) in accordance with paragraph 2.2. (CDRL A001)

3.1.4.1 In accordance with paragraph 2.2 and defined in individual TOs, 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. Coding will be in accordance with paragraph 2.2 and the standards provided in individual TO. Informal unit testing will be in accordance with the applicable Software Test Plan as identified in the individual TO.

3.1.4.3 In accordance with section 2.0, 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, as defined in individual TOs, verify the software by conducting independent testing, code analysis, algorithm analysis, and review of the test procedures and results, in accordance with paragraph 2.2.

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. User training requirements will be identified within each TO.

(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. Briefings shall also include intelligence updates provided from the Navy Information Operations Command (NIOC) and/or Radio Battalion (RADBN). 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 provide Foreign Military Exploitation (FME) to develop jamming techniques. 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. The contractor shall evaluate test plans to ensure consistency with systems specifications, including requirements traceability-and ensure that testing is conducted, as specified in each TO. The contractor shall conduct tests to verify and validate compliance with system specifications. The contractor shall provide Subject Matter Expertise of aircraft systems under test at Development Test and Operational Test (DT/OT) environments. All efforts shall be in accordance with paragraph 2.3. (CDRL A001)

3.3.2 The contractor shall provide, in accordance with individual TO, 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, as defined in individual TOs, 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 in accordance with paragraph 2.3 at the individual TO level. (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 as defined in individual TO.

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, as identified in the individual TO and 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 the following EW related technical systems engineering tasks in the areas of:

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 in accordance with paragraph

2.2. (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 and as defined in individual TOs. Experiments and demonstrations to test the study's conclusions will be defined in individual TOs.

(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, as defined in individual TOs, 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 as defined in individual TOs. 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, as defined in individual TOs, 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…