N00024-22-R-6427-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

See Summary of Changes.

1. CONTRACT ID CODE PAGE OF PAGES

1 22

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

16C. DATE SIGNED

BY 28-Apr-2022

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 N0002422R6427

X 9B. DATED (SEE ITEM 11)

04-Apr-2022

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

28-Apr-2022

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002422R6427

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

The following questions are hrereby answered:

# Date Document Page # Section / Paragraph Question Answer

1 4/13/2022 RFP pg. 51 SOW Section 1.0

Section 1.0 SCOPE notes that "The delivered systems shall include any hardware, firmware, software, shipping containers, batteries, and all the components necessary to operate the system and any other support equipment necessary to achieve the requirements defined in the respective TDPs, provided as GFI."

Please clarify the above referenced statement with respect to "any other support equipment necessary to achieve the requirements defined in the respective TDPs." It is not anticipated that the TDP includes requirements. Should this have referenced the Performance Specification instead?

The TDP is properly referenced.

2 4/13/2022 RFP pg. 119 Section I - Contract

Clauses

Section I of the RFP is inclusive of FAR clause

52.217-7 VAR I

OPTION FOR

INCREASED

QUANTITY-

SEPARATELY

PRICED LINE ITEM

(MAR 1989)

(NAVSEA

VARIATION I) (OCT

2018). The clause provides a breakdown of latest option exercise dates by CLIN. From the table, it is unclear if USG can place orders against all listed CLINs during the entire period

The government my exercise CLINs up to the latest option exercise date listed as per the clause.

prior to the end date or whether the intent is to have non-overlapping consecutive ordering periods. Can you more clearly define the ordering periods?

3 4/13/2022 RFP

pg. 54-

SOW Sections 3.2.1 and 3.2.2

Should the Production Readiness Review (Section 3.2.1) and the Physical Configuration Audit (Section 3.2.2) be included in CLIN 2000 along with First Article Qualification Test (Section 3.1)?

The Statement of Work specifies in Section

3.2.2 that "The PCA shall be held after the first production unit has successfully completed First Article Qualification Testing."

If the government were to waive the FAQT, then would that logically lead to a waiver for PCA as well?

See Amendment

4 4/12/2022 RFP pg. 168 Paragraph 1

Page 168 of the RFP documentation notes that the Attachment L-4

(MICROSOFT EXCEL

TEMPLATE FOR

COST AND PRICING)

has been uploaded with the solicitation and Section J Attachments on sam.gov. In reviewing the uploaded Section J Attachments, Attachment L-4 is not included. Can the Government please

Attachment uploaded to beta.sam provide access to this required file?

5 4/25/2022 RFP pg. 151 Section L; 1.1

Solicitation Response Requirements

Where can we find the provision entitled “Restrictions on Disclosure and Use in Proposals”?

See Amendment

6 4/25/2022 RFP

pg. 54 and pg.

Section C, Statement of Work, Section 3.2 and

Section 3.2.7.2

SOW Section 3.2 Manufacture, Assembly, and Test applies to CLINs 0001- 0009, which is inclusive of jammer core spares.

Section 3.2.7.2 Production Reliability Acceptance Test (PRAT) testing specifies that each "system" produced shall be subject to PRAT testing. Jammer core spares are not a "system." Please clarify if it is the Government's intention to have PRAT testing on jammer cores spares.

The Government does not intend for Jammer Cores to go through PRAT testing.

7 4/25/2022 RFP pg. 51 Section C, Statement of

Work, Section 1.0

Statement of Work Section 1.0 SCOPE notes that "In performance of the Build-to-Print (BTP) effort, the Contractor shall build the JCREW I1B1 and DRAKE systems in accordance with their respective Technical Data Package (TDP), provided as Government Furnished Information (GFI) listed in Section J, Attachments 3 and 4, and tested in accordance with the Performance Specification, provided as GFI listed in Section J, Attachment 2." Are the testing requirements the only elements of the contract that are performance specification and all other elements are build-to-print?

The sentence in question specifies how the units will be tested. It does not specify which sections of the requirement are build to print or are performance specification.

8 4/25/2022 Solicitation

Package N/A N/A

Due to the complexities in the proposal we would like to request an extension to the RF of 30 Days

See Amendment

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 04-May-2022 02:00 PM to 19-May-2022 02:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) describes the tasks required to manufacture and deliver the Joint Counter Radio- Controlled Improvised Explosive Device Electronic Warfare (JCREW) I1B1 System of Systems (SoS). The JCREW I1B1 System of Systems (SoS) and DRAKE includes four (4) distinct systems that utilize common components, software/firmware, and hardware solutions for an open, flexible and compatible system design approach that is modular, interoperable and affordable to upgrade. These systems are: dismounted system (man-portable), mounted system (ground), fixed site system (semi-permanent geographical area and fixed), and a dismounted variant referred to as DRAKE. DRAKE provides a Counter-Unmanned Aircraft System (C-UAS) capability to afloat and ashore forces. In performance of the Build-to-Print (BTP) effort, the Contractor shall build the JCREW I1B1 and DRAKE systems in accordance with their respective Technical Data Package (TDP), provided as Government Furnished Information (GFI) listed in Section J, Attachments 3 and 4, and tested in accordance with the Performance Specification, provided as GFI listed in Section J, Attachment 2. The Contractor shall provide engineering support services, systems, support equipment, and spares necessary to support the production and sustainment of JCREW I1B1 and DRAKE systems as detailed below. This effort will also include options for Foreign Military Sales (FMS).

The delivered systems shall include any hardware, firmware, software, shipping containers, batteries, and all the components necessary to operate the system and any other support equipment necessary to achieve the requirements defined in the respective TDPs, provided as GFI.

1.1 BACKGROUND

The JCREW I1B1 and DRAKE programs provide the military services with a software defined radio system with broad Radio Frequency (RF) capabilities. The current mission requirements include electronic warfare capabilities to counter the threat from Radio-Controlled Improvised Explosive Devices (RCIED) and small Unmanned Aircraft Systems (s- UAS). The JCREW I1B1 systems will provide RCIED protection to the members of the military services operating world-wide and C-UAS capability to afloat and ashore forces.

1.2 PROGRAM DESCRIPTION

The JCREW I1B1 SoS and DRAKE will operate worldwide, supporting United States (U.S.) Forces’ dominance over the electromagnetic spectrum, and will not require new or unique communication systems, but will operate within the bandwidth and quality of service of current and future systems. JCREW I1B1 SoS and DRAKE are capable of functioning in a stand-alone mode and will be network capable. JCREW I1B1 and DRAKE utilize an open architecture and well defined, common standards to support an incremental development approach which assures the JCREW I1B1 SoS and DRAKE will pace or remain ahead of future threats and be capable of performing new RF functions and missions when warfighter requirements change. Operating as part of a Family of Systems (e.g., airborne CREW devices or legacy ground-based CREW devices), the JCREW I1B1 SoS will provide commanders of the Joint Forces, U.S. Marine Corps, U.S. Navy, U.S. Air Force, U.S. Army, Special Operations Command, other Department of Defense (DoD) components, and non-DoD agencies with a capability to counter RCIEDs. DRAKE will provide ship and submarine commanders with a capability to counter UAS threats.

2.0 APPLICABLE DOCUMENTS

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense ASSIST database at https://assist.dla.mil/. Joint Chiefs of Staff, DoD Directives (DoDD), DoD Instructions (DoDI) and Publications documents can be found on the Acquisition, Technology, and Logistics (AT&L) Acquisition Knowledge Sharing System (AKSS) at or at the DoD Issuances website at: https://www.esd.whs.mil/dd/dod-issuances/. Non-Government documents should be obtained from commercial sources.

The following documents of issue in effect as of 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 MILITARY STANDARDS, SPECIFICATIONS AND HANDBOOKS

Document Title Date Guidance/Requirement

MIL-HDBK-61B DoD Configuration Management Handbook, 7 April 2020 Guidance

MIL-HDBK-781A

NOT1

Reliability Test Methods, Plans, and Environments for Engineering, 30 Jan 2015 Guidance

Development, Qualification, and Production

MIL-STD-1568D

NOT 1

Department of Defense Defense Design Criteria Standard: Materials and Processes for Corrosion Prevention and Control in Aerospace Weapons Systems

4 Aug 2021 Requirement

MIL-HDBK-2155

NOT 2

Failure Reporting Analysis and Corrective Action Taken

19 Jul 2019 Guidance

MIL-STD-2073-1E DoD Standard Practice for Military Packaging, Change 4

22 Apr 2019 Requirement

MIL-STD-129R Military Marking for Shipment and Storage, Change 2

27 Sep 2019 Requirement

2.2 DEPARTMENT OF DEFENSE REGULATIONS, DIRECTIVES AND INSTRUCTIONS

Document Title Date Guidance/Requirem ent

32 CFR 117 National Industrial Security Program Operating Manual

24 FEB 2021 Requirement

DoDI 5200.48 Controlled Unclassified Information

6 Mar 2020 Requirement

Security Classification Guide

Security Classification Guide for the DoD Military Ground Based Counter Radio Controlled Improvised Explosive Device Electronic Warfare

(CREW)

Systems

31 May 2021 Requirement

Security Classification Guide

Counter- Unmanned Systems Air Domain Security Classification Guide

20 Jun 2019 Requirement

DODI 5200.39 Critical Program Information

(CPI)

Identification and Protection Within Research, Development, Test and Evaluation

(RDT&E)

28 May 2015, inc.

Chg. 3, 1 Oct 2020

Requirement

DFARS 252.211-7003 Item Unique Identificatio n and Valuation

Mar 2016 Requirement

SECNAV INST 5000.2 Defense Acquisition System and Joint Capabilities Integration and Development System Implementati on

26 Mar 2019 Requirement

2.3 OTHER REFERENCES

Title Date Guidance/Requirement Manufacturing Readiness Level (MRL) Deskbook 2020 version Guidance DOD Corrosion Prevention and Control Planning Guidebook, Spiral 4 4 Feb 2014 Guidance

2.4 INDUSTRY STANDARDS

Document Title Date Guidance/Requirement

SAE/EIA-649-C Configuration Management Standard 7 Feb 2019 Requirement

SAE/EIA-649-

1A

Configuration Management Requirements for Defense Contracts

10 Aug 2020 Requirement

ASTM-D3951-

Standard Practice for Commercial Packaging 1 May 2018 Requirement

ASQ/ANSI/ISO

9001:2015

Quality Management Systems – Requirements 21 Oct 2015 Requirement

GEIA-STD-

0009A

Reliability Program Standard for Systems Design, Development, and Manufacturing

27 May 2020 Guidance

3.0 REQUIREMENTS

3.1 FIRST ARTICLE QUALIFICATION TEST (CLIN 2000)

The Contractor shall update, as necessary, the First Article Qualification Test (FAQT) Plan provided as GFI. The Contractor shall conduct FAQT on the first unit of each variant identified in CLINs 0001-0004 in accordance with the FAQT Plan. The Contractor shall own, or have access to, equipment and facilities capable of performing FAQT.

The Contractor shall furnish all labor and materials to procure piece parts, fabricate, assemble, test, repair failed items found during FAQT, re-test, clean, package, and ship completed systems to the destination(s) identified in the Contract. The Contractor shall submit an FAQT Report subsequent to successful completion of the FAQT testing.

The Government will take acceptance of completed JCREW I1B1 and DRAKE systems when the following criteria has been completed and accepted:

1. Government approved FAQT Report.

2. All first article testing and clauses satisfied (passed).

CDRL

A003 First Article Qualification Test Plan and Procedures, FAQT Plan A004 Test/Inspection Report (FAQT)

3.2 MANUFACTURE, ASSEMBLY, AND TEST (CLINS 0001-0009, 0101-0109, 0201-0209, 0301-0309, 0401-0409).

The Contractor shall build the JCREW I1B1 and DRAKE systems in accordance with the TDPs provided as GFI that meets the Performance Specifications provided as GFI.

The Contractor shall procure, manufacture, and assemble materials required to produce JCREW I1B1 and DRAKE systems, including any special test equipment, and conduct component and manufactured item testing necessary to assure the quality of all units.

3.2.1 PRODUCTION READINESS REVIEW (PRR) (CLIN 2000)

The Contractor shall complete a successful PRR in accordance with the JCREW I1B1 Systems Engineering Plan (SEP), provided as GFI. The Contractor shall not proceed to production without successful completion of the PRR.

Successful completion of the PRR will be predicated on the JCREW I1B1 SEP PRR Entrance/Exit Criteria to be completed as confirmed by the COR, as well as demonstration of MRL 9, as defined in the MRL Deskbook. The Government will indicate successful completion of the PRR via the PRR Memorandum, generated by the Technical Review Board (TRB) and signed by the TRB Chair. A Government-led Manufacturing Readiness Assessment (MRA) will be held on-site no later than 30 days after contract award and will assess the Contractor’s MRL. It will be the Government’s option to include major subcontractors in the assessment. The MRA shall address the following criteria, at a minimum:

Industrial Resources o Plant Facilities, Production Equipment, Test Equipment, and Tooling

Plant capacity to meet production rate Available Surge Capacity Government Furnished Equipment (GFE), special tooling, production equipment has been identified Needed Plant modernization, productivity enhancements has been accomplished o Personnel

Available skilled production manpower available Personnel training and certification available and completed

Production Engineering and Planning o Production Plan developed and in place o Production schedule developed and meets delivery requirements o Manufacturing methods and processes in place o Alternative production approaches available to contingency needs o Drawings and work instructions are in place and available o Configuration Management is defined, implemented, and maintained for production o Provisions have been made for determining producibility and cost impacts of engineering changes o Production Manager in place with authority and responsibility for manufacture and delivery o Management information system in place to provide production status

Materials and Purchased Parts o Complete an accurate Bill of Material in-place o Make or Buy decisions have been made o Long lead items identified o Sole source items identified o GFI/GFE / Government Furnished Material (GFM) identified o Material control/inventory system is adequate o Material procurement plan provides

Effective procedures to determine material needs, lead times, & delivery schedule Criteria for selection of subcontractors and suppliers in place Multi-sourcing of critical items Economic lot size orders Visibility and control of vendors and subcontractors

Quality Assurance Plans and Procedures o A Quality Assurance function in place o Quality Program in accordance with contract o Necessary quality control procedures and quality acceptance criteria established o Quality Assurance Organization is a participant in product planning

Logistics o Capacity exists to manufacture initial and replenishment spares

The Contractor shall develop a Manufacturing Plan that shall identify existing and projected manufacturing issues, address areas of risk, and assess the progress in the Contractor's planning to achieve the production rates required under the delivery schedule.

Additionally, the Contractor shall use the TDP for execution of the tasking required by this contract. Specifically, the Contractor shall demonstrate the use of the TDP in enterprise software suites to import/export drawings & data necessary to execute the tasking on this contract.

CDRL

A001 Manufacturing Plan A030 Assessment of Manufacturing Risk and Readiness, Manufacturing Readiness Assessment (MRA)

3.2.1.1 CORROSION PREVENTION AND CONTROL (CPC)

The Contractor shall implement an effective CPC program in accordance with MIL-STD-1568D which establishes the requirements for materials, processes and techniques, and identifies the tasks required to implement an effective corrosion prevention and control program. DOD Corrosion Prevention and Control Planning Guidebook, Spiral 4 may be utilized for guidance. The Contractor shall submit a Finish Specification Report which identifies the specific organic and inorganic surface pretreatments and coatings used for corrosion protection in the design and manufacture of JCREW I1B1 and DRAKE systems.

CDRL

A012 Finish Specification A013 Corrosion Prevention and Control Plan

3.2.2 PHYSICAL CONFIGURATION AUDIT (PCA) (CLIN 2000)

The Contractor shall support and participate in a Government-led PCA conducted on the first production units. The Contractor shall provide the Government with two (2) units of each system variant (Dismounted, Mounted/Fixed Site, and DRAKE) for PCA. The PCA shall be held after the first production unit has successfully completed First Article Qualification Testing.

A014 Configuration Audit Plan, Physical Configuration Audit (PCA) Plan

3.2.2.1 PCA PREPARATION

The Contractor shall participate in a 3-day, Government-led Technical Interchange Meeting (TIM), to be held not later than 30 days prior to execution of PCA. The Contractor shall develop a PCA Plan, and participate and assist the Government in the development and execution of the PCA using the guidelines contained in MIL-HDBK-61A.

The Contractor shall propose a PCA date at least 60 days in advance of meeting PCA Entrance Criteria, as derived from the JCREW I1B1 SEP. PCA Entrance Criteria shall include, at a minimum, availability of: Production schedules, Production test plans, Production test specifications/requirements, Production test procedures, Production acceptance plans, Configuration Management plans and documentation, quality control documentation and reports, ECP/Request For Variance (RFV) that may affect system baseline, production hardware (to include any fabricated or manufactured testing fixtures and testing equipment), and production software (to include any calibration software with source code and component selection automation software with source code).

3.2.2.2 PCA EXECUTION

The Government will verify the as-built configuration of all components, assemblies, and end items contained as defined in the TDP. The Government will verify the use of any test equipment, test fixtures, special test equipment and fixtures, test software (to include any automated test processes, procedures, and results), production fixtures, production tooling, and any production software applications and software code utilized in the fabrication, assembly, testing, and production of any CI contained in the TDP. The Contractor shall support execution of the Government’s PCA Technical Review Action Plan (TRAP), provided as GFI, on the first unit produced of each system variant. The Contractor shall provide representatives to witness the PCA and participate in the review and classification of findings. The Contractor shall support the PCA by providing technical documentation, equipment, facilities and services, including disassembly, reassembly, and subsequent retesting of Production components, assemblies, subsystems, and systems.

3.2.2.3 PCA CLOSURE

The Contractor shall respond to audit findings, recommend corrective actions or mitigations, and resolve all findings and deficiencies identified. The Contractor shall support a delta PCA if required by the Government to address all audit findings, corrective actions, and resolved deficiencies. The PCA shall cover all products to include any manufacturing, production, and assembly documentation and hardware, as well as all mission enabling products. A Government TRB will be convened to adjudicate all PCA Execution findings, corrective actions, and resolved deficiencies and proposed mitigations. The Contractor will participate as a non-voting member of the TRB, and will adjudicate all findings as may be required by the TRB. The PCA TRB Chair will indicate successful resolution of all findings via the PCA Memorandum, generated after the Government has accepted all findings resolutions and/or mitigations provided by the Contractor.

3.2.3 CONTRACTOR PRODUCTION QUALIFICATION

Contractor qualification, as well as all subcontractors and all facilities, for this BTP procurement shall be established upon successful completion of PRR and the Government PCA. Successful qualification is predicated on the Government’s determination that the systems meet final production configuration, and that production capability and capacity demonstrates a satisfactory basis for proceeding into Full Rate Production as described above.

3.2.4 CONFIGURATION STATUS ACCOUNTING (CSA)

The Contractor shall establish, implement, and maintain a Configuration Status Accounting (CSA) database to record and track status of JCREW I1B1 and DRAKE hardware and software. This database shall be established and functional prior to PRR. The Contractor shall provide the Government electronic access to this database throughout the term of the contract. The Contractor shall record the CSA data for each JCREW I1B1/DRAKE system in this database when each system is delivered. The CSA data shall be identified to the Lowest Repairable Unit (LRU) level as defined in the TDP. The TDP baseline revisions include ECPs provided as GFI.

The Contractor shall include a report of CSA database activities in the Contractor’s Progress, Status, and Management Report (CPSMR).

A015 Configuration Status Accounting Information A016 Contractor’s Progress, Status and Management Report

3.2.5 TESTING

3.2.5.1 ACCEPTANCE TESTING

In accordance with the Contractor’s Quality Management System (QMS) – documented in the Contractor’s Quality Assurance Program Plan (QAPP) - and in accordance with this SOW, the Contractor shall perform all necessary incoming inspections and acceptance tests of material received from subcontractors, suppliers, and vendors to assure that items meet the requirements of the specification control drawings or source control documentation. All nonconforming material shall be segregated from material acceptable for production line use and disposition of nonconforming material shall be accomplished in accordance with the Contractors Quality Assurance (QA) Procedures as outlined in the Contractor’s QMS.

The Government will take acceptance of completed JCREW I1B1 and DRAKE systems when the following criteria has been completed and accepted:

1. As-Built Configuration List – Common (ABCL-C) for each individual system being sold off.

2. Functional Evaluation/Acceptance Test (FE/AT) System Test Report for each individual system being sold off.

3. Production Reliability Acceptance Test (PRAT) System Test Report for any system that was run through

PRAT being sold off.

CDRL

A003 First Article Qualification Test Plan and Procedures, FAQT Plan A004 Test/Inspection Report (FAQT)

3.2.6 AS-BUILT CONFIGURATION

The Contractor shall develop and deliver an As-Built Configuration List - Common (ABCL-C): Indentured Bill of Materials for each delivered item, including serialized systems and spares. The ABCL-C shall extend down to the LRU level and be recorded in a CSA database. The list of LRUs is provided as GFI.

A002 As-Built Configuration List - Common (ABCL-C)

3.2.7 PRODUCTION ASSURANCE TEST SUPPORT

The Production Program Manager shall ensure the associated Test Personnel, Equipment, and Facilities are used for all the required Production Tests.

3.2.7.1 ENVIRONMENTAL STRESS SCREENING

All systems shall be subjected to environmental stress screening. All spares and repaired hardware shall be subjected to environmental stress screening. Testing shall be conducted as defined in the Environmental Stress Screening (ESS) Test Procedures and Implementation Plan, provided as GFI. During thermal testing of environment stress screening, the item shall be cycled through operational modes while being subjected to the specified environmental thermal stresses. Thermal and electrical stresses shall be IAW the ESS Plan, provided as GFI. Thermal stress screening shall be conducted to include, at a minimum, six (6) cycles with the last three (3) failure free. A minimum of 8OC/minute rate of change is required to expose thermally sensitive manufacturing defects. The ambient operating temperatures are specified in the Performance Specification, provided as GFI. Vibrational stresses shall be conducted IAW the ESS Plan, provided as GFI. The random stress shall be applied along each axis perpendicular to the plane of printed circuit boards (PCBs) and shall be applied for at least five (5) minutes along each orthogonal axis. Tolerance for the random vibration spectrum shall be +3 decibels (dB). Notching at resonant frequencies is permitted. The Contractor shall provide updates to the Government provided ESS Plan and provide ESS Test Reports. At the completion of environmental stress screening, FE/AT shall be completed and delivered to the Government as required by the SOW.

A017 Environmental Stress Screening (ESS) Procedures and Implementation Plan A018 ESS Report

3.2.7.2 PRODUCTION RELIABILITY ACCEPTANCE TEST (PRAT)

Each system produced shall be subject to a Production Reliability Acceptance Test (PRAT), provided as GFI. PRAT shall be conducted after each produced system has successfully completed Environmental Stress Screening. The purpose of PRAT is to identify deficiencies in design, components, materials & workmanship introduced over the course of the production program. PRAT shall allow verification of key operational performance characteristics of each system under environmental stresses. Thermal and electrical stresses shall be IAW the PRAT Plan, provided as GFI. The Contractor shall test each system in accordance with paragraph 5.11, MIL HDBK-781A, Test Plan XVIII- D, and Figure 35. Test duration shall be the completion of two (2) test profiles of 16 hours. Cumulative equipment operating time and equipment failures shall be recorded and plotted on the chart of the approved test plan. The Contractor shall provide updates to the Government provided PRAT Plan and provide PRAT Test Reports. PRAT closeout for each system under test shall be the completion of FE/AT in accordance with the SOW. Conversion to a sampling plan shall be IAW PRAT Plan, provided as GFI. Sample sizes for mounted, fixed site, dismounted and DRAKE shall be in accordance with MIL-HDBK-781A, Paragraph 5.4.2.2(b).

CDRL

A007 Acceptance Test Plan (PRAT) A008 Acceptance Test Report (PRAT)

3.2.7.2.1 PRAT REJECT CRITERIA

All failures shall be subjected to the Failure Reporting, Analysis and Corrective Action System (FRACAS), requirements defined in SOW. All failures shall be analyzed to determine root cause(s). Occurrence of a pattern failure (defined as two (2) or more occurrences of failures having the same assignable root cause) or when the plot of equipment operating time versus failures crosses the reject line of the approved test plan shall be cause for "Reject" in PRAT. Any time a reject situation is reached, the Contractor shall notify the COR within three (3) days with written notification via e-mail. A Reject decision in PRAT shall require development and implementation of a corrective action plan. Continued acceptance of systems shall be based on the Government approval of the corrective action plan. The Government reserves the right to stop acceptance of systems until implementation and verification of appropriate corrective action occurs in accordance with an approved corrective action plan. Repairs shall require a complete repetition of PRAT. The Contractor shall provide the Government with PRAT Test Plan updates and PRAT Test Reports with functional results. PRAT requirements shall be executed in accordance with MIL-HDBK-781A, Figure 35.

CDRL

A007 Acceptance Test Plan (PRAT) A008 Acceptance Test Report (PRAT)

3.2.7.3 FUNCTIONAL EVALUATION/ACCEPTANCE TEST (FE/AT) REQUIREMENTS

All systems shall be subjected to a Functional Evaluation/Acceptance Test (FE/AT), provided as GFI. FE/AT shall be conducted after each produced system has successfully completed the required testing. The purpose of functional evaluation is to verify that key performance attributes are met. Functional evaluation will include tests to verify:

a. System Timing

b. System Zeroization

c. Power output (test frequencies across full spectrum)

d. Received sensitivity (test frequencies across full spectrum)

e. Functionality of Control and display Unit (CDU) controls

f. CDU display is fully functional

g. Voltage Standing Wave Ratio (VSWR)

h. Global Positioning System (GPS) operational

i. Loading of loadset

j. Operation of all Built In Test (BIT) modes (e.g. P-BIT and S-BIT)

k. Acceptable audible noise levels

The Contractor shall provide the Government with a FE/AT Test Report with functional results.

A005 Acceptance Test Plan (FE/AT) A006 Acceptance Test Report (FE/AT)

3.2.8 RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM

The Contractor shall develop and maintain a Reliability and Maintainability (R&M) Program using guidance from GEIA-STD-0009, to ensure the JCREW I1B1 and DRAKE system designs continue to comply with R&M requirements defined in the Performance Specification provided as GFI. The Contractor shall plan, implement, and manage the R&M engineering effort that assures the satisfaction of system requirements. The Contractor shall track actual LRU/LRM failure rates using information obtained from production testing. Any approved design changes shall require updates to the following R&M tasking:

a) Updates to GFI items:

1. Reliability Stress Prediction

2. Reliability Block Diagram

3. Reliability Critical Items List

4. Failure Modes, Effects and Criticality Analysis (FMECA)

b) Track Testing results for:

1. Environmental Stress Screening

2. Production Reliability Acceptance Test (PRAT)

3. Functional Evaluation/Acceptance Test (FE/AT)

4. Failure Reporting, Analysis and Corrective Action System (FRACAS)

A019 Reliability and Maintainability (R&M) Program Plan

3.2.8.1 FAILURE MODES, EFFECTS, AND CRITICALITY ANALYSES (FMECA)

The Contractor shall maintain the existing Failure Modes, Effects, and Criticality Analyses (FMECA), provided as GFI, to address any approved design changes introduced during manufacture and sustainment of the I1B1 and DRAKE systems.

A011 Failure Modes, Effect, and Criticality Analysis (FMECA) Report

3.2.8.2 FAILURE REPORTING, ANALYSIS AND CORRECTIVE ACTION SYSTEM (FRACAS)

The Contractor shall continue to develop the Failure Reporting, Analysis and Corrective Action System (FRACAS) and adhere to this Closed Loop Failure Reporting System, as provided as GFI for the duration of the contract. MIL- HDBK-2155 may be used as a guide in development of the FRACAS Plan. If the Contractor has an existing FRACAS Process/Plan then development of a new plan is not required and the Contractor shall deliver the existing FRACAS Plan in contractor format. If the Contractor does not have an existing FRACAS Plan then a new plan shall be developed and delivered. The Contractor shall employ procedures for analysis of failures to determine root cause, and documentation for recording corrective actions taken. FRACAS shall include uniform failure reporting, root cause failure analysis reports and corrective actions. All hardware/software/firmware failures from system level down to the component level shall be subject to these requirements throughout the life of the contract. The Contractor shall provide for visibility and traceability of all reported failures and BIT anomalies from discovery to close-out. All failure and BIT anomaly analysis reports shall be closed out within ninety (90) days of occurrence, or rationale provided for any extensions. The Contractor shall notify the Government, in writing, within twenty-four

(24) hours of any critical failure which impacts cost, schedule, producibility, interface, performance, or safety. The Contractor shall report the FRACAS failures that are not defined as critical to the Government, in writing, within ten

(10) working days from occurrence. All failures will be reported in the monthly Failure Review Board (FRB) meetings and in the Contractor Progress Status and Management Report (CPSMR).

The Contractor shall record FRACAS failures, Analysis, and Corrective Actions Failures, BIT anomalies (e.g., BIT failure to detect, BIT failure to isolate properly, and BIT false alarms), or non-conformances experienced from the end item level (LRU/LRM or lower) through the system level during manufacture and test through completion of the Contract. The Contractor shall perform failure analyses on all reported failures and BIT anomalies to the level required to determine the cause of failure, define the failure mechanism, and develop corrective actions to eliminate or limit their recurrence. In general, these analyses shall include a physical and failure analysis on electrical and electronic parts.

CDRL

A016 Contractor’s Progress, Status and Management Report (CPSMR) A009 Failure Reporting, Analysis and Corrective Action System (FRACAS) Plan A010 Failure Analysis and Corrective Action Report (FACAR)

3.2.8.2.1 FAILURE REVIEW BOARD (FRB)

The Contractor shall establish and conduct a FRB in accordance with the Contractor’s approved Failure Reporting, Analysis, and Corrective Action System (FRACAS) Plan and Procedures. The Government shall be an active member of the FRB and shall have the final authority for classification and disposition of all failures that occur during the contract period. All failures shall be presented to the FRB for disposition. The Government shall be notified of the FRB meeting dates at least ten (10) working days in advance. The FRB shall meet as often as necessary. However, the FRB shall not meet less frequently than monthly during any period when open failure reports exist.

A009 FRACAS Plan

3.2.8.2.2 FAILURE REPORTING

The Contractor shall record failures, BIT anomalies (i.e. BIT failure to detect, BIT failure to isolate properly and BIT false alarms) or non-conformance experienced from the end item level (LRU or lower when spares are procured) through the system level during manufacture.

3.2.8.2.3 FAILURE CLASSIFICATION

All failures shall be classified as relevant or non-relevant. Relevant failures shall be further classified as chargeable or non-chargeable. Classification of failures shall be proposed by the Contractor and forwarded to the procuring agency for approval.

3.2.8.2.3.1 CHARGEABLE

A relevant, independent failure of contractor furnished equipment (CFE) under test, plus any dependent failures caused thereby, classified as one failure and used to determine contractual compliance with accept/reject criteria.

3.2.8.2.3.2 NON-CHARGEABLE

A relevant failure of CFE, caused by and dependent upon an independent failure of GFE or CFE of another contractor, and therefore not used to determine contractual compliance with accept/reject criterial.

3.2.8.2.4 FAILURE ANALYSIS

The Contractor shall perform root cause failure analyses on all reported failures and BIT anomalies to the level required to determine the cause of failure, define the failure mechanism and develop corrective actions to eliminate or limit their recurrence. In general, these analyses shall include a physical failure analysis on electrical and electronic parts. The analyses of parts shall as necessary include electrical failure verification, dissection, microphotography, and adequate chemical and metallurgical analysis to define the failure mechanism (e.g. most fundamental cause). Records of failure analyses, including causes and effects, shall be maintained by the Contractor within the FRACAS process and provide failure analysis results and data to the R&M and BIT-related design analysis functions. Failures that are determined to be production/process related shall be the responsibility of the Contractor to identify and correct in accordance with all the other terms of this contract.

3.2.8.2.5 CORRECTIVE ACTIONS

The Contractor shall develop and implement effective corrective actions to eliminate or minimize recurrence of all failures, faults and BIT anomalies. Corrective actions shall meet the following criteria:

a. Be established (analytically or by test) as an effective corrective action to the satisfaction of the Government

b. Be scheduled for incorporation into all subsequent production equipment via official change controls (i.e., ECPs) as approved by the Government

c. Must adequately address performance, cost, and schedule impacts for new equipment deliveries and to implement corrective action in previously delivered equipment.

A009 FRACAS Plan

3.2.9 QUALITY MANAGEMENT PLANNING

The Contractor’s quality management program shall be in compliance with applicable ANSI/ISO/ASQ 9001:2015 standards or higher.. All manufacturing processes and quality systems procedures shall also be in accordance with applicable ANSI/ISO Standards. The Contractor shall flow all quality system requirements down to sub-tier suppliers.

3.2.10 LOGISTICS SUPPORT

The Contractor shall provide logistics support as specified below.

3.2.10.1 ITEM UNIQUE IDENTIFICATION (IUID)

The Contractor shall include Item Unique Identification (IUID) markings on JCREW I1B1 and DRAKE Systems and LRUs via Wide Area Work Flow (WAWF) in accordance with DFARS 252.211-7003 and the TDP. The TDP baseline revision includes ECPs. The Contractor shall maintain marking and verification records for all IUID qualifying items manufactured on this contract. These records shall be available for inspection by the Government at all times.

A020 Item Unique Identification (IUID) Marking Activity and Verification Report

3.2.10.2 PACKAGING, HANDLING, STORAGE, AND TRANSPORTATION (PHS&T)

The Contractor shall establish and maintain a Packaging, Handling, Storage, and Transportation (PHS&T) program in accordance with MIL-STD-2073-1E and ASTM D 3951-15. The Contractor shall implement radio-frequency identification (RFID) on all shipments in accordance with DFARS Clause 252.211-7006 and MIL-STD-129R.

3.2.11 CONFIGURATION MANAGEMENT

The Contractor shall develop and implement a Configuration Management (CM) Program, in accordance with EIA- 649-C and EAI-649-1A, which adheres to the processes defined in the JCREW I1B1 CM Plan, provided as GFI. The Contractor’s change management process shall be capable of processing required configuration changes in a time frame that enables identification, evaluation, and implementation of proposed changes without impact to production schedules.

A021 Configuration Management Plan

3.2.11.1 CHANGE MANAGEMENT PROCESS FOR DESIGN CHANGES

In the event that the design of the system has to be permanently changed, a Preliminary Engineering Change Proposal (PECP) must be submitted and approved prior to submission of an Engineering Change Proposal (ECP) for Class I/II ECPs. All PECPs and ECPs shall be submitted in accordance with the approved JCREW I1B1 CM Plan.

Contractor shall provide updated drawings with final ECP and identify required redline changes to GFI, including technical manuals, training materials, depot maintenance work requirements, Level of Repair Analysis (LORA), Logistics Product Data (LPD) data provided as GFI.

A022 Engineering Change Proposal (ECP)

3.2.11.2 REQUEST FOR VARIANCE (RFV)

When, in the opinion of the Contractor, a deviation from standards or requirements of this SOW is in order, the Contractor shall make a Request for Variance (RFV) in writing to the Procuring Contracting Officer (PCO) with an informational copy to the designated technical representative. The Government will notify the Contractor in writing of approval or disapproval of the deviation, within forty-five (45) days after receipt by the PCO.

The Contractor shall submit a RFV only as required. These requests are called non-permanent design changes because they are only approved for a specific set of serial numbered Configuration Items and Systems. RFVs are used to document specific Configuration Items and Systems that do not meet the documented drawing or specification requirements. RFVs require approval by the Contracting Officer and will require contract consideration from the Contractor. The Contractor shall submit proposed consideration with each RFV.

A023 Request for Variance (RFV)

3.2.11.3 OBSOLESCENCE MANAGEMENT

The contractor shall submit an Engineering Change Proposal (ECP) to request any changes resulting from obsolescence, Diminishing Manufacturing Sources and Material Shortages (DMSMS), or end-of-service-life issues.

The Contractor shall identify obsolete components during procurement of material and document the results in Source Data for Forecasting DMSMS. The Contractor shall install nomenclature and identification markings IAW the TDP. The TDP baseline revision includes ECPs.

CDRL

A024 Bill of Materials (BOM) for Logistics and Supply Chain Risk Management, DMSMS Health Assessment Report

3.3 ENGINEERING SUPPORT SERVICES (CLINS 0010-0015, 0110-0115, 0210-0215, 0310-0315, 0410-0415)

The Contractor shall provide technical and engineering support services as directed by Government issued Technical Instructions (TI) IAW C-242-H003 TECHNICAL INSTRUCTIONS (NAVSEA) (OCT 2018) via Contracting Officer authorization. In accordance with TIs, the contractor may be required to provide the necessary personnel, equipment and facilities to execute: evaluation of potential technologies; insertion of new technologies (TIE);

refurbishment of hardware; procurement of materials; generation of test, status, financial and logistics documentation; or other engineering and sustainment efforts as needed. Any travel and incidental material requirements shall be billed as cost only under CLINS 0012, 0015, 0112, 0115, 0212, 0215, 0312, 0315, 0412, 0415.

The contractor shall provide a status of the following Engineering Support Services in the Contractor’s Progress, Status and Management Report:

Total cost expended by authorized TI Total hours expended by authorized TI Summary of any TI issues encountered

Estimate of percent complete by authorized TI Summary of work accomplished by authorized TI

Engineering support services tasking may include a requirement for a technical report at the conclusion of the effort.

Reporting shall be provided in the Contractor’s Progress, Status and Management Report.

A016 Contractor’s Progress, Status and Management Report (CPSMR)

3.4 MANAGEMENT (ALL CLINS WITH THE EXCEPTION OF 0010-0015, 0110-0115, 0210-0215,

0310-0315, 0410-0415)

The Contractor shall assign a qualified 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 subcontractors’ efforts. The PM shall ensure all requirements are applicable to the components/parts as specified herein for all items procured. The PM shall ensure that subcontractors’, suppliers’, and vendors’ procedures are compliant with all contract requirements.

The Contractor shall develop an IMS IAW the 3-level WBS provided as GFI and maintain the Integrated Master Schedule (IMS) as a management document from each CLIN award/exercise through its period of performance. The Contractor shall provide status updates to the IMS that describes the status of the planned IMS events and milestones, accomplishments, activities, and current and potential issues, if any. The IMS shall provide most likely start dates and durations for each IMS activity and event, but shall also identify significant risk factors and their potential schedule impacts, when applicable.

A025 Integrated Program Management Data Analysis Report (IPMDAR)

3.4.1 GOVERNMENT FURNISHED INFORMATION (GFI) / GOVERNMENT FURNISHED

PROPERTY (GFP)

The Contractor will be provided with the GFI and GFP as identified in Section J. Deficiencies with GFP will be reported to the Government in accordance with 52.245-1 Contractor compliance with GFP requirements (see FAR 52.245-1) shall be reviewed periodically by Defense Contract Management Agency (DCMA), which is the designated Government Property Administration Office. The Contractor shall inspect GFP within seven (7) days of receipt and report to the Government any GFP found damaged, malfunctioning, or otherwise unsuitable for use.

CDRL

A026 Government Furnished Information Deficiency Report A031 Government Property Inventory Report

3.4.2 INTEGRATED DATA ENVIRONMENT (IDE)

The Contractor shall use the Government furnished Integrated Data (Digital) Environment (IDE) (to include Non-classified Internet Protocol Router (NIPR), Secret Internet Protocol Router (SIPR), or both) to document all aspects of the program, including the production drawings, integration and test engineering efforts, the Contractor's Systems Engineering (SE) efforts, integrated logistics support efforts, and the Contractor's PM effort. Information concerning IDE use, file structure, and access will be provided as GFI. Access to the IDE will require the issuance of DoD approved Public Key Infrastructure (PKI) certificates. A maximum of three PKI certificates will be allowed for each Contractor. The Government reserves the right to review all data associated with the JCREW I1B1 and DRAKE Systems.

3.4.3 MEETINGS

3.4.3.1 POST AWARD CONFERENCE

The Contractor shall conduct a Post Award Kickoff Meeting within thirty (30) calendar days after contract award.

During the Post Award Kickoff Meeting, the Contractor shall provide a detailed briefing on its management and contract execution strategy. The contract briefing shall include: any updates following the proposal; an organizational overview; key personnel; schedules, specific material purchasing schedules; a description of the

Contractor’s quality process, including the quality manager; and, a discussion of risk and risk mitigation strategies.

The Contractor shall plan for a two (2) day Post Award Kickoff Meeting and provide the Government with meeting minutes within 7 days of completion.

A027 Presentation Material

3.4.3.2 MONTHLY PROGRAM REVIEW

This meeting shall be held to update the Government on production progress and discuss any issues. This meeting shall be conducted via a phone conference call or in person, as requested by the Government, at the Contractor’s facility. The Contractor is responsible for setting up the phone conference facilities. If the discussion is classified, an on-site conference at the Contractor’s facilities is acceptable.