N00024-20-R-5500-0002 2020-06-05.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 updates to the Section C SOW, Section L, and Section M.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 72

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

16C. DATE SIGNED

BY 05-Jun-2020

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 N0002420R5500

X 9B. DATED (SEE ITEM 11)

24-Apr-2020

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

05-Jun-2020

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002420R5500

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been added by full text:

C-204-H002 IMPLEMENTATION OF ENHANCED SECURITY CONTROLS ON SELECT DEFENSE

INDUSTRIAL BASE PARTNER NETWORKS (NAVSEA) (JAN 2020)

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

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

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

POAM.

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

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

2. Compliance to NIST 800-171

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

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

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

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

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

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e.

FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

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

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

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

3. Cyber Incident Response

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

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

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

The contracting officer will approve or disapprove the request after coordination with DC3.

4. Naval Criminal Investigative Service (NCIS) Outreach

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

5. NCIS/Industry Monitoring

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

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

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

d) Recommended Number (IAW FAR 52.1 and DFARS 252.103):

(End of Text)

The following have been modified:

STATEMENT OF WORK

1 SCOPE

This Statement of Work (SOW) defines the effort required for production, assembly, inspection, testing, delivery and sustainment of AN/SPY-6(V) Radar Systems and supporting equipment.

This effort is to build AN/SPY-6(V) systems in accordance with the Technical Data Package (TDP), provided as Government Furnished Information (GFI) and as referenced in Section J.

The efforts defined by this SOW are in support of Hardware Production and Sustainment.

1.1 Background

The scope of this effort is divided between two Contractor roles that may be awarded as two contracts by the Government: a “Leader” role and “Challenger” role. Each role is responsible for production, assembly, inspection, testing, and delivery of its assigned AN/SPY-6(V) quantities (defined in Section B of the contract). The Leader additionally is responsible for RMA Line Replaceable Units (LRUs) sustainment support of all fielded (post-delivery) AN/SPY-6(V) systems.

AN/SPY-6(V) is a Family of Radars (FoRs) which are designed to be scalable and adaptable across multiple ship classes and mission requirements.

Developed under the AMDR program, the AN/SPY-6(V)1 is the Navy’s next generation radar system that will address Ballistic Missile Defense (BMD) and Air Defense (AD) capability gaps identified in the Maritime Air and Missile Defense of Joint Forces (MAMDJF) Initial Capabilities Document (ICD). The MAMDJF ICD was reviewed and validated by the Joint Requirements Oversight Council (JROC) on 1 May 2006, culminating in the designation of the Navy as the lead component. The Under Secretary of Defense for Acquisition, Technology, and Logistics (USD(AT&L)) directed the Navy to proceed with an Analysis of Alternatives (AoA) for MAMDJF on 16 June 2006. The Director of Program Analysis and Evaluation endorsed the radar portion (Phase I) of the AoA on 27 Oct 2008, finding the AoA sufficient. The AMDR Capability Production Document (CPD) was approved by the JROC in March 2018. AN/SPY- 6(V)1 is an Integrated Air and Missile Defense (IAMD) radar providing sensitivity for long range detection and engagement of advanced threats. The AN/SPY-6(V)1 is currently planned to be deployed on the DDG 51 FLT III with four arrays each populated with 37 Radar Modular Assemblies (RMAs).

A variant of the AN/SPY-6(V) is currently planned to replace the AN/SPY-1D(V) radar on existing DDG 51 FLT IIA ships. This variant includes four arrays each populated with 24 RMAs. The nomenclature has not yet been assigned, but the program anticipates it being designated as AN/SPY-6(V)4. The U.S. Navy is proceeding with the modernization of DDG 51 FLT IIA ships by replacing the existing AN/SPY-1D(V) with a scaled AN/SPY-6(V) radar to increase IAMD performance against raids of air and ballistic missile threats in adverse environments. The goal of this radar back fit is to significantly improve operational capability, while taking into account the constraints imposed by the existing FLT IIA hull (e.g., power, weight, and equipment space). The back fit of the scaled AN/SPY-6(V) will be installed during planned FLT IIA shipyard availabilities in order to minimize cost. The Navy plans to capitalize on the Aegis Weapons System Baseline 10 (BL10) and integrate with the AN/SPY-6(V)4.

Enterprise Air Surveillance Radar (EASR) is two scaled variants of AN/SPY-6(V) for non-DDG platforms. Two array configurations will be fielded. The configurations are a single rotating array with 9 RMAs (AN/SPY-6(V)2) and three arrays each populated with 9 RMAs (AN/SPY- 6(V)3 and, notionally, AN/SPY-6(V)5). EASR is one sensor in a new sensor suite that is designed to meet the performance needs contained in the Battlespace Awareness ICD. The specific system performance requirements are documented in the Enterprise Radar Suite Naval Capabilities Document (ERS NCD). EASR variants utilize AN/SPY-6(V) radar technology to meet the air surveillance requirements of multiple ship classes. AN/SPY-6(V)2 radars are planned to replace the AN/SPS-48 and AN/SPS-49 radars aboard CVN (Nimitz), Landing Helicopter Assault (LHA) hulls, and Landing Platform/Dock (LPD) hulls with Ship Self-Defense System (SSDS) ACB20. AN/SPY-6(V)3 replace Dual Band Radar (DBR) on CVN(Ford) class platforms and are the primary surveillance and fire control radars for FFG(X) class platforms with the Frigate Weapon System (FWS) (FFG(X) variants may become AN/SPY-6(V)5). The architecture for EASR is intended to drive a lower recurring cost by utilizing the same core technology for variants on multiple ship classes.

2 APPLICABLE DOCUMENTS

The following documents of issue in effect on the execution date of the contract are applicable to this Statement of Work and attached appendices to the extent specified herein or as modified under the contract.

2.1 Mandatory Documents

The following documents form a basis for the work to be performed under this SOW:

a. Air and Missile Defense Radar External (Logical) Interface Requirements Specification (IRS)

b. Enterprise Air Surveillance Radar (Logical) Interface Requirements Specification

(IRS)

c. Department of Defense Security Classification Specification (DD-254), included as Attachment J-01.

d. Air and Missile Defense Radar Hull, Mechanical, and Electrical (HM&E) Interface Requirements Document, included as Attachment J-15.

e. Air and Missile Defense Radar Back Fit Hull, Mechanical, and Electrical (HM&E) Interface Requirements Document, included as Attachment J-16.

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

g. DoD Instruction (DoDI) 8500.01 Cybersecurity, dated 13 March 2014

h. DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), dated 28 June 2017

i. NSTISSAM COMPUSEC/1-99, dated 11 March 1999

j. Air and Missile Defense Radar (AMDR) Program Protection Plan (PPP), Tailored

Contract Version, included as Attachment J-17

k. MIL-STD-31000B – Technical Data Packages, dated 31 October 2018

l. IEEE 12207.2017 – Standard for Systems and Software Engineering - Software Life Cycle Processes, dated 28 Sept 2017

m. MIL-STD-882E Safety, dated 11 May 2012

n. NAVSEA S9310-AQ-SAF-010, Technical Manual for Batteries, Navy Lithium

Safety Program and Procedures, dated 19 Aug 2004

o. NAVSEAINST 9310.1B, Naval Lithium Battery Safety Program, dated 13 Jun

p. MIL-HDBK-189C, Reliability Growth Management, dated 14 June 2011

q. GEIA-STD-0009 - Reliability Program Standard For Systems Design, Development And Manufacturing, dated 13 Nov 2008

r. ASQC Q9001-2008, Quality Systems-Model for Quality Assurance In-Depth, Development, Production, Installation, and Servicing, dated 15 Nov 2008

s. Air and Missile Defense Radar (AMDR) Life Cycle Sustainment Plan (LCSP) included as Attachment J-11

t. Cost and Software Data Reporting (CSDR) Plan - Leader, included as Attachment J-04

u. AN/SPY-6(V) Resource Distribution Table, included as Attachment J-05

v. Cost and Software Data Reporting (CSDR) Plan - Challenger, included as

Attachment J-09

w. AN/SPY-6(V) Systems Engineering Plan (SEP), Tailored Contract Version, included as Attachment J-19

x. PEO IWS / Naval Sea Systems Command Research & System Engineering Warfare System Engineering and Human Systems Integration Directorate Technical Review Manual (TRM), Version 2, dated 18 December 2009

y. OPNAVINST 5100.24B, Navy System Safety Program Policy, dated 06 Feb 2007

z. NAVSEAINST 5100.12B, Requirements For Naval Sea Systems Command System Safety Program For Ships, Shipborne Systems And Equipment, dated 03 Aug 2011

aa. Executive Order (EO) 12856, 03 Aug 1993

bb. Executive Order (EO) 13148, 21 April 2000

cc. National Aerospace Standard (NAS) 411, dated July 1993

dd. SAE-GEIA-STD-0007B - Logistics Product Data, dated 01 May 2013

ee. MIL-STD-1472G, Change 1 – Human Engineering, dated 17 Jan 2019

ff. ASTM F1166-07(2013), Marine Systems, Equipment and Facilities, Human

Engineering Design for, dated 2013

gg. MIL-STD-130N, Change 1, Identification Marking of U.S. Military Property, dated 16 November 2012

hh. OPNAVINST 1500.57B, Surface Warfare Training Strategy, 26 September 2011

ii. ANSI/EIA-748, Earned Value Management ?Systems, dated 17 Aug 1999

jj. CSDR Manual DoD 5000.04, Change 1, dated 18 April 2018

kk. MIL-STD-881D – Work Breakdown Structures for Defense Materiel Items, dated 09 April 2018

ll. USD(AT&L) Memorandum, Use of Acquisition Program Transition Workshops, dated 01 April 2011

mm. NFPA70E, Standard for Electrical Safety in the Workplace, 2018 Edition.

nn. Technical Data Package (TDP), Attachment J-02

oo. MIL-STD-1568D - Materials And Processes for Corrosion Prevention And Control In Aerospace Weapons Systems, date 31 Aug 2015

pp. Government Furnished Material List (Leader Only), attached as J-12

2.2 Guidance Publications

The following publications are available as guidance:

a. AN/SPY-6(V)1 System Requirements Document

b. AN/SPY-6(V)2&3 System Requirements Document

c. Air and Missile Defense Radar (AMDR) Programmatic, Environmental, Safety and Health Evaluation (PESHE) Plan

d. SAE-GEIA-HB-0007A: Handbook For GEIA-STD-0007- Logistic Product Data, dated 10 Feb 2014

e. PEO IWS 2.0 Risk Management Policy

f. Naval SYSCOM Risk Management Policy, NAVSEAINST 5000.8, dated 21 Jul

g. Risk Management Guide for DoD Acquisition, Version 1.0, dated August 2006

h. DoD Directive 5200.39, Change 2, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), 15 Oct 2018

i. NAVSEAINST 9400.2, Implementation of Naval Sea Systems Command (NAVSEA) Afloat IA Governance and Guidance, dated 18 Aug 2010

j. MIL-DTL-901E – Shock Tests, H.I. (High-Impact) Shipboard Machinery, Equipment, and Systems, Requirements for, dated 20 June 2017

k. MIL-HDBK-2155, Failure Reporting, Analysis and Corrective Action Taken, 11 Dec 1995

l. NAVSEAINST 8020.6E - Department of the Navy Weapon Systems Explosive Safety Review Board, dated 11 March 2008

m. NAVSEA SW020-AH-SAF-010, Weapons System Safety Guidelines Handbook, 01 Feb 2006

n. DoDI 5000.02, Change 4, dated 31 Aug 2018

o. MIL-HDBK-217F-2 – Reliability Prediction of Electronic Equipment, dated 28 Feb 1995

p. MIL-HDBK-472-1 – Maintainability Prediction, dated 12 Jan 1984

q. MIL-HDBK-61A, Configuration Management Guidance, dated 07 Feb 2001

r. ANSI/EIA 649B, National Consensus Standard for Configuration Management, dated 01 Apr 2011

s. SAE-GEIA-HB-649A, Configuration Management Standard Implementation

Guide, 01 March 2016

t. PEO IWS 2.0 Above Water Sensors Configuration Management Plan/Procedures

u. NAVSEA A Program Manager’s Guide to the Application of Performance Based

Logistics (PBL), Revision A, dated 08 October 2008

v. Under Secretary of Defense for Acquisition, Technology and Logistics (USD (AT&L)) Corrosion and Prevention Control Planning Guidebook of September

w. DoD Diminishing Manufacturing Sources and Material Shortages (DMSMS) Guidebook: A Guidebook of Best Practices for Implementing a Robust DMSMS Management Program (SD-22A), 01 Jan 2016

x. DoN Automatic Identification Technology (AIT) Implementation Manual, dated June 2006

y. RAMSC Plan

z. HP&S Configuration Management Process Document, attached as J-10

2.3 Precedence

In the event of a conflict between the documents listed in Section 2.1, Mandatory Documents, and Section 2.2, Guidance Publications, the documents in Section 2.1 shall take precedence.

3 Requirements In the following subparagraphs of Section C paragraph 3, scope applies to both Leader and Challenger contractors, unless denoted as “LEADER ONLY” or “CHALLENGER ONLY” in the subparagraph header. Subparagraph headers also denote which CLINs scope is included within.

3.1 General Requirements (CLINs 0001, 0004, 1001-1004, 2001-2004, 3001-3004, 4001- 4004)

3.1.1 Post Award Conference (CLIN 0001 only) (LEADER ONLY)

A post award conference shall take place at the contractor’s facility no later than 30 days after award of the contract. The purpose of this conference is to review the initial production plans.

The contractor shall deliver a conference Agenda (CDRL A010) no later than one week before the date of the post award conference. The contractor shall deliver Presentation Materials (CDRL A011) and Meeting Minutes/Actions (CDRL A012) no later than one week after completion of the post award conference.

3.1.2 Technical Data Package

The Contractor shall support the maintenance of the Technical Data Package (TDP) (initial HW Product Baseline included in Attachment J-2) in accordance with the configuration management processes in Section 3.1.6. The TDP will be maintained in the Government’s Product Data Management (PDM) system during execution of this contract (description of this system is provided in Attachment J-10).

Any required updates to the TDP for producibility and obsolescence shall be accounted for underneath the AN/SPY-6(V) production CLINs. No further costs of design changes are authorized.

The Contractor shall prepare and deliver updates to the TDP sufficient to detail the as-built product baseline at a production level (Level 3) in accordance with MIL-STD-31000B. The Contractors’ as-built TDP updates shall describe any and all subsequent changes to the baseline product including revisions up to the time of Government acceptance to reflect the final as-built configuration. The Contractors’ as-built TDP updates shall include any software products, including source code necessary for diagnostic and troubleshooting purposes and source code for any other software and firmware developed for the radar under this contract. The Contractor shall submit updates to the Contractors’ as-built TDP in accordance with CDRLs A001 through A008:

A001 HW Interface Design Description (IDD)

A002 Interactive Computer Aided Provisioning System (ICAPS) Data File Exchange

A003 Interface Control Document (ICD)

A004 Logistics Product Data (LPD)

A005 Product Drawings/Models and Associated Lists

A006 Second Source Lowest Replacement Unit (LRU) Description Document

A007 Special Packaging Instructions

A008 Software and Firmware

3.1.3 Plan Execution

The Contractor shall generate, maintain, and execute the System Engineering Management Plan (SEMP) (CDRL A009). The SEMP shall address all efforts within the HP&S contract. The SEMP shall describe how a fully integrated production and sustainment effort will be managed and conducted. The Contractor shall generate, maintain, and execute the Risk Management Plan (RMP) as part of the SEMP. The Contractor shall implement and maintain a risk management program in accordance with the approved RMP to identify and manage risks associated with achievement of the program’s technical (including performance), cost, and schedule requirements. Risks shall be reported to the Government during IPT/WG meetings as well as In- Progress Reviews (IPRs). PEO IWS 2.0 Risk Management Policy, NAVSEAINST 5000.8 (Naval SYSCOM Risk Management Policy), and Risk Management Guide for DoD Acquisition, Version 1.0, dated August 2006, are available as guidance.

The Contractor shall form Integrated Product Teams (IPTs) and Working Groups (WGs) to support an integrated product development process. The Contractor shall generate the organizational structure and document it in the SEMP. The Government will assign representatives to participate in IPT/WG meetings as necessary. Government participation will be coordinated through the COR.

The Contractor shall attend IPT/WG meetings and Technical Interchange Meetings (TIMs), and coordinate meetings with the Government. The Contractor shall post Presentation Materials (CDRL A011) and Action Items (CDRL A012) on the Government IDE. The Contractor shall perform analysis and respond to Action Items resulting from IPT/WG meetings.

The Contractor shall participate in the following Government / Industry Teams established by the Government.

a) Radar/Ship Integration Working Group (RSIWG) is established to manage and maintain the interfaces with the Ship Hull, Mechanical, and Electrical (HM&E) systems. The RSIWG is anticipated to meet monthly in the Washington, DC area.

b) System Safety Working Group (SSWG) is established to study and manage system and software safety issues. The Government will identify an AMDR Principal For Safety (PFS), who will co-chair the SSWG. The SSWG will also interface with the CMS PFS.

During this phase, the SSWG is anticipated to meet quarterly in the Washington, DC area.

c) Waterfront IPT is established to manage and resolve issues related to delivery and installation of equipment at HP&S delivery destinations. The Waterfront IPT is anticipated to meet monthly in the Washington, DC area.

d) Sustainment IPT is established to study and manage issues related to sustainment of AN/SPY-6(V) systems, including cross-impacts from production status and decisions.

The Sustainment IPT is anticipated to meet monthly in the Washington, DC area.

These Government / Industry Teams will include members from Navy and other industry partners.

The Contractor shall generate and execute a Program Protection Implementation Plan (PPIP) (CDRL A013) in accordance with the AMDR Program Protection Plan (PPP). DoDI 5000.02, DoDI 5200.39 and the Deputy Assistant Secretary of Defense, Systems Engineering PPP Outline and Guidance Template are available as guidance. The PPIP shall cover production for both Leader and Challenger as well as sustainment for the Leader.

The PPIP shall be prepared in order to ensure effective and efficient protection of essential program information, technologies and systems. The PPIP is derived from the PPP and will not only restate what is written in the PPP. The PPIP shall include:

a. Description of the security management structure;

b. Description of the Contractor’s Information Security Program (ISP) as a part of their PPIP. As an integral part of the ISP, describe the Contractor and subcontractors procedures for identifying, reporting and resolution of Facility Security Breaches;

Classified Information Compromises, and Spillages including notification of DSS, DCMA, and Government Program Security Manager

c. Describe how the contractor’s Defense Industrial Base (DIB) Cyber Security is addressed in the contractor’s facility and addressed in subcontracts and how incidents are addressed and reported to DSS / DCMA

d. Identification of CPI physical locations under the Contractor’s or Subcontractors’ control;

e. Assessment of the vulnerability of the CPI to intelligence collection in the following areas: Human Intelligence (HUMINT); Open Source Intelligence (OSINT); Signals Intelligence (SIGINT); Imagery Intelligence (IMINT); Computer Network Operations

(CNO);

f. Identification of the countermeasures to be implemented at each site where CPI is held;

g. Special handling procedures required for CPI, and procedures for recovering CPI in the event of a mishap;

h. Identification of risk mitigation techniques to counter threats and counterfeit parts to the Contractor’s supply chain; and

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

The Contractor shall generate a Manufacturing Plan (CDRL A014). The Manufacturing Plan documents methods by which the design is to be built. The Manufacturing Plan contains sequence and schedule of events at contractor and subcontractor levels that define use of materials, fabrications flow, test equipment, tools, facilities, and personnel. It reflects consideration and incorporation of manufacturing requirements in the design process and includes identification and assessment of design facilities.

In addition, the Manufacturing Plan shall identify production metrics for the key subsystems.

Key subsystems include the Transmit/Receive channels and other array and Receiver/Exciter LRUs of costs greater than 10% of the total system production cost per shipset.

The Contractor shall generate, implement and maintain a Hazardous Material Management Program (HMMP) Plan (CDRL A015). The Contractor shall document that consideration has been given to eliminating and reducing the use of Hazardous Materials (HM) in processes and products consistent with the requirements of EO 12856, EO 13148 and NAS 411. The HMMP shall address requirements for hazardous materials and elimination, minimization, substitution and handling of hazardous materials and potentially hazardous materials. The HMMP shall describe the HM analysis that will be used to identify HM risks, the strategy for integrating HM considerations into the systems engineering process, HM responsibilities and the method for tracking progress of the HM analysis. The Contractor shall manage the selection, use, and disposal of hazardous materials so that the DoD incurs the lowest cost necessary to protect human health and the environment over the life cycle. The Contractor shall generate HMMP Reports (CDRL A016) that identify the characteristics, quantity and location of all hazardous materials.

The Contractor shall generate, implement, maintain a QA Program that is integral to the overall production process. The Contactor shall generate a QA Program Plan (CDRL A017). The QA Program shall be comprised of management, technical resources, plans, procedures, schedules and controls necessary to ensure conformance to contractual requirements. The QA Program shall address the requirements of ASQC Q9001-2008. The QA Program shall also address the software and firmware quality provisions of IEEE 12207. The software and firmware design, documentation and review process shall be in accordance with current standard business practices that represent the approved processes for the Software Engineering Institute (SEI) level IV. For validation of 3D Model Data, MIL-STD-31000B, Appendix C, is available for guidance.

The Contractor shall generate and implement a Corrosion Prevention and Control Plan (CDRL A018) IAW MIL-STD-1568D and using the DoD Corrosion and Prevention Control Planning Guidebook of September 2007 as guidance. The Contractor shall ensure that corrosion prevention and management are included in the AN/SPY-6(V) design. The Contractor shall report corrosion activity at IPTs/WGs and SETRs.

3.1.4 Cybersecurity Requirements – See Section C Text C-204-H002

3.1.5 Production Progress

The Contractor shall conduct IPRs to review progress of the subsystem, software, and system builds, integration and testing efforts. IPRs shall be scheduled quarterly. The first IPR shall address readiness of manufacturing processes, quality systems, and production planning. The Contractor shall host the IPRs, and coordinate meetings with the Government. The Contractor shall coordinate and post Meeting Agendas (CDRL A010) on the Government IDE prior to meetings. The Contractor shall post Presentation Materials (CDRL A011) and Minutes/Action Items (CDRL A012) on the Government IDE.

The Contractor shall generate a Production Status Report (CDRL A022) for the period from option exercise through delivery of final unit. The reports shall include the production metrics identified in the Manufacturing Plan (CDRL A014). The reports shall address production metrics, including components procured, assembly and testing. The reports shall address labor efforts and facility utilization. The reports shall address material efforts, including procurement, inventory, expenditures, and quality control data. The Contractor shall provide a consistent format for the reporting of metrics for the radar.

3.1.6 Configuration Management (CM)

The Contractor shall generate and execute an AN/SPY-6(V) CM Plan (CDRL A023) that follows the requirements in this section, using the HP&S Configuration Management Process Document (Attachment J-10), MIL-HDBK-61A, SAE EIA 649C, SAE-GEIA-HB-649A and PEO IWS 2.0 Above Water Sensors Configuration Management Plan/Procedures as guidance. The CM Plan shall address interactions and roles of the Contractor, other HP&S Contractor, Design Agent, and Government.

3.1.6.1 Configuration Boards

The Government will conduct and chair the HP&S Local Configuration Control Board (LCCB), SPY-6 Design Agent LCCB, and PEO IWS 2.0 Configuration Control Board (CCB). See Figure 3.1.6-1 for the configuration board overview.

Figure 3.1.6-1: Configuration Boards

The HP&S LCCB is responsible for configuration management of the HW Product Baseline TDP for all AN/SPY-6(V) variants, which defines the current baseline for production and sustainment within HP&S CLINs. The SPY-6 Design Agent (DA) LCCB is responsible for configuration management of the System Product Baseline TDP, which defines the system and software baseline for Design Agent efforts on separate contract(s).

The HP&S LCCB will have approval authority of Class II ECPs, Minor RFDs, RFWs, NORs and SCNs. The HP&S LCCB will review and recommend approval/disapproval of Class I ECPs and Major/Critical RFD/RFWs to the PEO IWS 2.0 CCB. The PEO IWS 2.0 CCB will have approval authority of Class I ECPs and Major/Critical RFD/RFWs.

Approval of formal Class I ECPs, if any, will be accomplished via the changes clause of the Contract.

The Contractor shall attend the monthly HP&S LCCBs in the Washington, DC area. Scope for HP&S LCCB participation is provided in paragraph 3.1.6.2. The Contractor shall participate in the monthly Design Agent LCCB and provide Problem Reports and change documentation in that forum. The Contractor shall participate in the monthly IWS 2.0 CCB when invited by the Government and provide Problem Reports and change documentation in that forum.

3.1.6.2 HP&S LCCB TDP Configuration Management

The Government will maintain and manage the HW Product Baseline TDP on its Government-hosted PDM system. The initial HW Product Baseline is the TDP, Attachment J-02. All updated TDP materials shall be submitted via the Government’s PDM system in accordance with the HP&S LCCB approved change documentation. At all times, the official HW Product Baseline for production and sustainment will be that reflected in the Government’s PDM system.

In the event that the Contractor determines a path forward that would cause its as-built configuration to vary in any way from the HW Product Baseline, the Contract shall propose the changes to the HP&S LCCB. In the event that the Government approves TDP changes for one HP&S contractor and not the other, identification of this difference in as-built configuration will be identified in the PDM system and be viewable to all contractors.

The Contractor shall identify all hardware, software, and documentation issues related to the HW Product Baseline TDP and submit them as a Problem Report (CDRL A024) via the Government’s PDM system. In addition, the Government, other HP&S Contractor, and Design Agent Contractor may identify and submit Problem Reports via the Government’s PDM system.

Each HP&S contractor shall assess all submitted Problem Reports and submit responses via Problem Report (linked within the PDM system) with impact assessments for cost, schedule, and scope to the Government’s PDM system. The HP&S LCCB will assign resolution of all Problem Reports to the Leader, the Challenger, the Design Agent, or any combination of the three.

The Contractor shall correct all issues and change requests associated with Problem Reports assigned to it by the HP&S LCCB. The Contractor shall conduct sufficient regression testing to ensure that any changes made appropriately correct the issues without introducing additional issues. The Contractor shall specifically address how each change affects B2 Specification, Internal IRS, or HM&E IRS requirements in the Problem Reports, including proposed changes to those requirements. The Contractor shall also specifically address any impacts to sustainment efforts in the Problem Reports. Proposed changes to any specification will be decided within the SPY-6 DA LCCB. The Design Agent will assess impacts to requirements flowdown from the System Requirements Documents (SRDs), the Interface Requirements Documents (IRDs) (included as J-15 and J-16), and other materials contained in the System Product Baseline TDP.

The Leader shall assess all Problem Reports for impacts to sustainment efforts and cost and submit comments and proposed alternatives (when applicable) to the HP&S LCCB and DA

LCCB.

The Contractor shall update and submit Problem Reports with the proposed corrective actions, proposed schedule, and associated cost estimates to the HP&S LCCB. The HP&S LCCB will approve and determine the required change documentation, and will assign part or all required change documentation generation to the Leader, the Challenger, the Design Agent, or any combination of the three. The Contractor shall perform all necessary work needed to prepare the required change documentation assigned to it by the HP&S LCCB. The Contractor shall submit the required change documentation via change requests in the Government’s PDM system.

Change documentation includes, but is not limited to Engineering Change Proposals (ECPs) (CDRL A025), Requests for Variance (RFVs) (CDRL A026), Notice of Revisions (NORs) (CDRL A027) and/or Specification Change Notices (SCNs) (CDRL A028). The Contractor shall submit Engineering Change Proposal System Safety Reports (ECPSSRs) (CDRL A029) in conjunction with ECPs. The Contractor shall submit Variance System Safety Reports (VSSRs) (CDRL A030) in conjunction with RFVs to the HP&S LCCB. The Contractor shall submit change documentation to the HP&S LCCB for classification and final approval.

3.1.6.3 Trade Studies and Analysis

Prior to submission of a Class I ECP, the Contractor shall perform trade studies and analysis.

This includes all proposed Class I ECPs from the Leader, Challenger, Design Agent, and the Government. These efforts will include cost estimates, scope estimates, technical investigations, industry surveys, and technical trade-off studies. All results of such trade studies and analysis shall be delivered in the Engineering Design Notebook (EDN) (CDRL A031).

3.1.7 As-Built Configuration Bill of Material List

The Contractor shall generate an As-Built Configuration List (ABCL) (CDRL A032) and Priced Bill of Materials (PBOM) (CDRL A033) for each the AN/SPY-6(V) production unit, reflecting the delivered the AN/SPY-6(V) production unit hardware and software.

3.1.8 Factory Acceptance Testing

3.1.8.1 Testing

The Contractor shall generate the Factory Acceptance Test (FAT) Plan (CDRL A034) and Factory Acceptance Test (FAT) Procedures (CDRL A035). The OEM Plan and Procedures and the TDP are available as guidance. The Contractor shall conduct Factory Acceptance Testing on each AN/SPY-6(V) Unit in accordance with Contractor-developed, Government-approved Acceptance Test Plan and Procedures. The Contractor shall submit Problem Reports (CDRL A024) for any tests that do not pass. The Contractor shall perform correction actions for any testing that does not pass.

The Contractor shall document the results of Factory Acceptance Testing including the as run, redlined, and marked up procedures in a Factory Acceptance Test (FAT) Report (CDRL A036).

Any marked up procedures shall be reflected in updated Factory Acceptance Test Procedures.

The Contractor shall provide all Factory Acceptance Test (FAT) Data (CDRL A037), evaluation tools (including simulations) and results to the Government for independent evaluation of performance. The Contractor shall notify the Government of planned test events not later than 21 calendar days prior to testing to support Government participation. The Contractor shall notify the Government of any changes to planned test events not later than seven (7) calendar days before the test. In the event that the Government is not able to witness a test that requires Government attendance and/or approval, a representative from the Contractor’s Quality Engineering organization shall represent the Government’s interest with authority to grant any required approvals. The Contractor shall conduct meetings to review test results with the Government.

3.1.9 Safety

The Contractor shall maintain and execute its System Safety Program in accordance with MIL- STD-882E in accordance with Task 102. NAVSEA SW020-AH-SAF-010, Weapons System Safety Guidelines Handbook and DoD Joint Software Systems Safety Engineering Handbook and the AMDR PESHE Plan are available as guidance.

The Contractor shall provide a System Safety Lead with education, safety experience, and certifications sufficient to answer the recommended qualifications for a SSL as delineated in OPNAVINST 5100.24B, Enclosure (3), table 1 for a program complexity of high.

The Contractor shall provide in the EDN (CDRL A031) an Environment Safety and Occupational Health (ESOH) assessment that includes data, studies, and reports necessary to demonstrate full compliance with all Federal, State, and Local environmental laws including any known potential compliance issues associated with the system manufacturing, testing, operations, and disposal. In addition, the Contractor shall generate and provide safety documentation in accordance with Task 210, Environmental Hazard Analysis (EHA), of MIL- STD-882E in the EDN.

The Contractor shall generate and execute the System Safety Program Plan (CDRL A038). The Contractor shall generate System Safety Program Progress Reports (SSPPR) (CDRL A039) which are to be used to cover periodic reviews of safety activities and to monitor progress of contractor system safety efforts.

The Contractor shall, in accordance with MIL-STD-882E Task 106, update and maintain the Closed Loop Hazard Tracking Database (CDRL A040) to meet the requirements found in MIL- STD-882E and OPNAVINST 5100.24B, Paragraph 8.d.

The Contractor shall, in accordance with MIL-STD-882E Task 301, update and provide the Safety Assessment Report (CDRL A041).

The Contractor shall support one WSESRB. The Contractor shall provide Presentation Material (CDRL A011) in support of the WSESRB. The Contractor shall support two (2) one-day dry runs with Government participation for each WSESRB review. The Contractor shall participate in the WSESRB and present the contractor's system design, policies, and procedures, and respond to all Actions (CDRL A012) from the WSESRB within 30 days. NAVSEAINST 8020.6E is available for guidance.

3.1.10 Diminishing Manufacturing Sources and Material Shortage

The Contractor shall support and resolve all LRU, subassembly, or piece part Diminishing Manufacturing Sources/Material Shortages (obsolescence) issues necessary to execute the requirements of this contract. The Contractor shall achieve this by identifying, reporting, recommending, and executing government-approved resolution DMSMS issues in order to meet the requirements of this contract. Efforts under CLIN 4001-4004 shall additionally address any items that require resolution within 24 months.

The Contractor shall generate and execute a Diminishing Manufacturing Sources and Material Shortage (DMSMS) Implementation Plan (CDRL A042) using DoD DMSMS Guidebook: A Guidebook of Best Practices for Implementing a Robust DMSMS Management Program (SD- 22A) as guidance.

The Contractor shall conduct DMSMS Forecasting and propose solutions in Problem Reports (CDRL A024). Proposed solutions shall include analysis of alternatives and impacts to both production and sustainment. In addition, the Contractor shall generate DMSMS Life Cycle Management Data (CDRL A043). Summaries of DMSMS Problem Reports, data and reports shall be reported at IPRs. The Source Data for Forecasting DMSMS shall reference parts, part numbers, and drawing numbers based upon the TDP (as defined in Section 3.1.2).

3.1.11 Failure Analysis and Corrective Action Report(FACAR)

The Contractor shall maintain a Failure Analysis and Corrective Action Report (FACAR). All hardware failures and the equivalent software interrupts/failures shall be reported and monitored in the FACAR. The Contractor shall document and maintain the FACAR summaries in the FACAR report (CDRL A044). MIL-HDBK-2155 is available for guidance. The Contractor shall participate in Government chaired Failure Event Review Boards (FERBs), presenting FACAR events’ status, root cause, corrective action, verification, and implementation. The Leader shall coordinate and host a bi-monthly FERB. The Contractor shall consolidate and summarize FACAR events, and provide in the Presentation Materials (CRDL A011) for each FERB.

3.1.12 Warranties and Licenses

The Contractor shall deliver and maintain all Warranties and Licenses (CDRL A045) associated with the AN/SPY-6(V) COTS equipment. The Contractor shall provide access to these Warranties and Licenses to the Government. At Government acceptance of the AN/SPY-6(V) production units, the Contactor shall transition Warranties and Licenses to the Government.

3.1.13 Program Management

3.1.13.1 Program Management Support

The Contractor shall assign a Program Manager (PM) who shall have complete responsibility for the planning, execution, control and reporting of all aspects of the program, and for directing in-house and subcontractor efforts. The PM shall ensure that all requirements are applicable to the components/parts as specified herein for all items procured. The PM shall ensure that sub Contractors’, suppliers’ or vendors’ procedures are compliant with all contract requirements.

3.1.13.2 Progress, Status, and Management Report

The Contractor shall generate a monthly Contractor’s Progress, Status and Management Report (CDRL A046). The Contractor’s Progress, Status and Management Report shall contain the following:

a. Planned and actual staffing by IPT/WG;

b. Planned and actual material purchases;

c. Planned and actual use of Non-Developmental Items (NDI)/Non-Developmental Software (NDS);

d. CDRLs submitted v. CDRLs accepted during reporting period; and

e. Cost Chart: A cost chart depicting, by month, the estimated Program spend forecast (entire option period of performance) with actuals (up to reporting month).

3.1.13.3 Earned Value Management System

The Contractor shall establish, maintain, and use in the performance of this contract, an Earned Value Management System (EVMS) in accordance with DFARS 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in American National Standards Institute/Electronic Industries Alliance (ANSI/EIA)-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the Contractor’s management processes and systems to include the integrated master schedule, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement. The Contractor shall report program cost, schedule and earned value status in an Integrated Program Management Report (IPMR) (CDRL A047). Each IPMR submission shall also include a Control Account Plan (CAP) file, providing a mapping of IPMR cost, schedule and earned value metrics by CLIN.