N0002422R5206 Amendment 0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

See continuation page.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 59

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

16C. DATE SIGNED

BY 15-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 N0002422R5206

X 9B. DATED (SEE ITEM 11)

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

15-Apr-2022

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:

N0002422R5206

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

The following have been modified:

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

Labor CLIN Labor Hours Cost Per Hour*

Fee Rate Per Hour*

Loaded Hourly Rate*

0002 12,247

0008 22,371

1002 12,247

1008 2,036 1,000

2002 12,252

2008 1,000 2,036

3002 12,252

3008 1,000

4002 12,236

4008 1,000

*The offeror shall divide the proposed cost and proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

(End of text)

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

STATEMENT OF WORK

1.0 SCOPE (ALL CLINs)

The Program Executive Office for Integrated Warfare Systems, Undersea Systems Program Office (PEO IWS5) executes the acquisition and total life cycle system support responsibility for the Navy’s Surface Ship Undersea Warfare (USW) programs, including the Light Airborne Multipurpose System. The program consists of the AN/SRQ-4 radio terminal set (RTS) fitted on Cruisers (CGs) and Arleigh Burke Destroyers (DDG-51s), as well as potential USW efforts in support of FMS customers.

This Statement of Work (SOW) defines the effort required to manufacture, test, deliver, manage, and support AN/SRQ-4 RTSs, for ship small surface combatants. The phrase “CDL Hawklink” is used throughout this document to refer to the AN/SRQ-4 RTS. The phrase Common Data Link Software refers to Computer Software Configuration Items. The term Shop Replaceable Assembly (SRA) means any assembly that could be replaced at the organizational level regardless of whether the SRA is defined as an organizational level (O-level) replaceable item.

The AN/SRQ-4 RTS nomenclature used throughout this SOW is for reference and is not intended to imply that the AN/SRQ-4 RTS system provided under this contract must be identical to AN/SRQ-4 RTS systems developed and procured under previous contracts. As part of fleet modernization, the AN/SRQ-4 RTS shall support Band Efficient – Common Data Link (BE-CDL) Revision C (or later) waveform and Crypto Core Modernization (CCM) technologies, and to eliminate the legacy NTDS interface to the SQQ-89.

For new AEGIS baselines, the AN/SRQ-4 RTS will connect to the AEGIS LAN Interconnected System (ALIS), therefore the AN/SRQ-4 RTS shall meet Risk Management Framework (RMF) implementation requirements in accordance with DODI 8500.01 Cybersecurity and DODI 8510.01 Risk Management Framework for DOD Information Technology (IT).

The Contractor shall ensure that all deliverable equipment under this effort is manufactured and verified as specified herein in accordance with the requirements identified in the Prime Item Development Specification for the AN/SRQ-4 Radio Terminal Set. The requirements Prime Item Development Specification for the AN/SRQ-4 Radio Terminal Set Paragraph 4.1.1.14 Highly Accelerated Life Test (HALT) (requirement numbers SRQ-1896, -1897, - 1898, and -1899) (Section J Attachment 5 – AN/SRQ-4 Specification) are not within the scope of this contract.

Systems Engineering and Program Management (SEPM) is used to cover all systems engineering and program management efforts on this contract. This shall also cover any administrative activity and undertaken by the Contractor as part of this contract.

2.0 APPLICABLE DOCUMENTS (ALL CLINs)

The following documents are applicable to the tasks described herein and are for use by the Contractor as general guidance in the fulfillment of those tasks.

2.1 GOVERNMENT DOCUMENTS

The following documents define the technical requirements for hardware and software as well as the testing requirements for the effort defined in this SOW. In the event that this SOW and any documents in Sections 2.1 and

2.2 contradict each other, the SOW shall take precedence.

2.1.1 DEPARTMENT OF DEFENSE (DOD) DOCUMENTS

The Contractor shall comply with the latest version of the documents cited below.

DoDM 5000.04 Cost and Software Data Reporting (CSDR) Manual 07 May 2021 DoDM 5220.32 (Vol. 1)

National Industrial Security Program: Industrial Security Procedures for Government Activities

10 Dec 2021

DoDI 8500 Federal Information Progressing Standards Publication (FIPS Publication 140-3) 22 Mar 2019 DoDI 8500.01 Change 1

Cybersecurity 07 Oct 2019

DoDI 8510.01 Change 3

Risk Management Framework for DoD Information Technology 29 Dec 2020

DoDI 5230.24 Change 3

Distribution Statements on Technical Documents 15 Oct 2018

DoDI 5200.48 Controlled Unclassified Information (CUI) 06 Mar 2020 DoDM 5200.01 (Vol. 1) Change 2

DoD Information Security Program: Overview, Classification, and Declassification 28 July 2020

DoDM 5200.01 (Vol. 1, Ch-2)

DoD Information Security Program: Overview, Classification, and Declassification 28 July 2020

DoDM 5200.01 (Vo1. 2, Ch-4)

DoD Information Security Program: Marking of Classified Information 28 July 2020

DoDM 5200.01 (Vo1. 3, Ch-3)

DoD Information Security Program: Protection of Classified Information 28 July 2020

ECAC-CR-

90-079

DD Form 1494 Preparation Guide for Army Frequency Allocations Aug 1996

7681990 Rev F Waveform Specification for the Common Data Link (CDL) Nov 2002 60038368 Rev C Bandwidth Efficient Common Data Link (BE-CDL) Waveform Sep 2017

SECNAVINST

5230.15

Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software

10 Apr 2009

DoDD 5230.25 Change 2

Withholding of Unclassified Technical Data From Public Disclosure 15 Oct 2018

DoDI 5220.22 Change 3

National Industrial Security Program 10 Dec 2021

DoDM 5220.22-M Change 1

National Industrial Security Program Operating Manual 28 Mar 2013

2.1.2 MILITARY STANDARDS AND HANDBOOKS

MIL-DTL-18307H Nomenclature and Identification for Aeronautical Systems – Including Joining Electronics Type Designated Systems and Associated Support Systems

28 Apr 2006

MIL-HDBK-61B Configuration Management Guidance (Guidance Only) 07 April 2020

MIL-HDBK-217F

(Ch-2)

Reliability Prediction of Electronic Equipment 28 Feb 1995

MIL-HDBK-470A

Notice 2

Designing and Maintaining Maintainable Products and Systems 31 May 2012

MIL-HDBK-472

Notice 2

Maintainability Prediction 26 May 2020

MIL-HDBK-781A Reliability Test Methods, Plans and Environments for Engineering Development, Qualification and Production

1 Apr 1996

MIL-HDBK-502A Product Support Analysis 8 Mar 2013

MIL-HDBK-1785

Notice 1

DOD System Security Engineering Program Management Requirements 22 Apr 2014

MIL-HDBK-2165

Notice 1

Testability Program for Systems and Equipment 22 Apr 2014

MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystem and Equipment

11 Dec 2015

MIL-STD-2073-

1E Change 4

Standard Practice for Military Packaging 22 Apr 2019

MIL-STD-882E System Safety 11 May 2012

MIL-STD-785B

Notice 3

Reliability Program for Systems and Equipment Development and Production 30 Jul 1998

MIL-STD-1629A

Notice 3

Procedures for Performing a Failure Mode, Effects, and Criticality Analysis 4 Aug 1998

2.2 NON-GOVERNMENT SPECIFICATIONS

2.2.1 OTHER DOCUMENTS

ANSI/EIA-649C Configuration Management Standard 07 Feb 2019 ANSI/EIA-649-1 Configuration Management Requirements for Defense Contract 20 Nov 2014

ANSI/ISO/ASQ Q-

9001-2015

Quality Management Systems - Requirements Oct 2015

GEIA-STD-0007B Logistics Product Data 01 May 2013 GEIA-HB-0007 Logistics Product Data Handbook 10 Feb 2014 IEEE 1220 Standard for Application and Management of the Systems Engineering Process 2005

ISO/IEC/IEE

12207:2017

Systems and Software Engineering – Software Life Cycle Processes Nov 2017

IEEE/ISO/IEC

15289-2019

Systems and Software Engineering – Content of Life-Cycle Information Items (Documentation)

July 2019

IEEE/ISO/IEC

24748-4-2016

International Standard for Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Planning

3 Mar 2016

NIST 800-171

Rev 2

Protecting Control Unclassified Information in Nonfederal Systems and Organizations

28 Jan 2021

NIST 800-12

Rev 1

An Introduction to Information Security 06 Jun 2017

RTCA/DO-160G Radio Technical Commission for Aeronautics 08 Dec 2010

2.3 GOVERNMENT-FURNISHED INFORMATION (All CLINs)

The Contractor shall retain all GFI for the duration of the contract. This information, with any associated software, reports or manuals shall be returned to the Government at the completion of the contract. In accordance with CDRL A001, the Contractor shall complete a GFI Deficiency Report to report deficiencies with GFI.

3.0 REQUIREMENTS

This section defines the requirements to manufacture, test, deliver, manage, and support the AN/SRQ-4 RTS. With written Government approval, previous test results, inspection, demonstration, or analysis results used to show requirements compliance shall be used for system components that have already completed proofs of compliance including tests, inspections, demonstrations, and analyses.

3.1 SYSTEM ENGINEERING AND PROGRAM MANAGEMENT (X002)

3.1.1 GENERAL

The Contractor shall organize, coordinate, control and report the status of all program activities, including subcontractors, to ensure the correct and timely delivery of all supplies and services specified. The Contractor shall ensure Common Data Link (CDL) Hawklink efforts meet contract cost, schedule and performance objectives. The Contractor shall designate a Program Manager with complete responsibility and authority for all aspects of the program. The Contractor shall prepare an Integrated Master Schedule (IMS) in accordance with CDRL A002 – Integrated Program Management Data and Analysis Report (IPMDAR)

3.1.2 REPORTS

The Contractor shall prepare and deliver a monthly Program Progress Report in accordance with CDRL A003 – Contractor’s Progress and Status Report.

3.1.3 RISK MANAGEMENT

The Contractor shall actively identify risks that could impact the Contractor’s ability to meet its technical, cost or schedule objectives. The Contractor shall identify risk candidates and propose mitigation steps to the Government.

The Contractor shall also support quarterly PEO IWS5 risk review teleconferences.

3.1.4 PROGRAM REVIEW

The Contractor shall attend quarterly Program Management Reviews (PMRs) at locations to be agreed upon by the Contractor and Government. The Contractor shall submit proposed agendas in accordance with CDRL A004 – Conference Agenda for PMRs.

Each of these items shall be addressed for all Contractor and Subcontractor efforts. The Contractor’s Program Manager, functional representatives, and as required, subject matter experts capable of addressing specific issues or problem areas shall attend the quarterly PMR. Additionally, Subcontractor personnel with the relevant expertise for specific issues or problem areas shall attend these meetings.

The Contractor shall prepare and deliver minutes of the program management review meetings in accordance with CDRL A005 – Report, Record of Meeting/Minutes.

3.1.5 INTEGRATED PROGRAM MANAGEMENT REPORT

The Contractor shall develop, maintain, and manage an Integrated Program Management Report (IPMR) for this effort by logically networking all discrete Contractor, Subcontractor, and Government activities required for the effort in this SOW in sufficient detail to enable effective management of the program. All major program milestones shall be incorporated into the scheduling system at the appropriate level with predecessors and successors assigned. Only one (1) IPMR shall be maintained, which shall be modified to include all new information required when each option is exercised. The IPMR shall be maintained, updated, and delivered in accordance with CDRL A002 – Integrated Program Management Data and Analysis Report (IPMDAR).

3.1.6 CONTRACT WORK BREAKDOWN STRUCTURE

The Contractor shall provide the Contract Work Breakdown Structure (CWBS) and dictionary in accordance with CDRL A006 – Contract Work Breakdown Structure. The Contractor shall maintain and update the CWBS and dictionary during contract execution.

3.1.7 GOVERNMENT FURNISHED PROPERTY

The Contractor shall manage Government Furnished Property (GFP) identified in Attachment J-2, GFP List. The Contractor shall notify the Contracting Officer Representative (COR) of receipt of all GFP via e-mail. The Contractor shall report GFP that is damaged, malfunctioning, or otherwise unsuitable for use in accordance with CDRL A007 – Government Property Inventory Report. The Contractor shall deliver a copy of the Contractor’s procedures relating to GFP/Government Furnished Equipment (GFE)/Government Furnished Material (GFM) and present at the first scheduled Program Review. The Contractor's procedures shall address the following:

• Examination upon receipt, consistent with practicality, to detect damage in transit

• Inspection for completeness, proper type and quantity

• Methods for assurance of adequate storage conditions, proper handling, and protection from deterioration during storage

• Testing, as required, to determine satisfactory operation

• Identification and protection from improper use or disposition

The Contractor shall establish procedures for the storage and maintenance of Government property. Records of all inspections and maintenance performed shall be maintained. These procedures and records shall be delivered to the Government and shall be subject to review by the Government in accordance with CDRL A007 - Government Property Inventory Report.

In order to modify GFP identified in Attachment J-2, the Contractor shall submit written requests to the COR with a copy to the Contracting Officer. The Contractor shall not modify GFP without written approval by the Contracting Officer.

3.1.8 COMPUTER SOFTWARE PRODUCT

The Contractor shall establish an IDE environment of their choice for development. The Contractor shall provide all non-proprietary licenses, source code, drawings, repair, and engineering documentation to the Government and third-party Contractors at specified key events or at defined intervals in accordance with CDRL A008 – Computer Software Product.

3.1.9 CONFIGURATION MANAGEMENT (CM) (X008)

The Contractor shall implement a Configuration Management program to control products, processes, and related documentation to ensure the integrity of design and supportability for both hardware and software Configuration Items (CIs) in accordance with the ANSI/EIA-649C Configuration Management Standard, ANSI/EIA-649-1 Configuration Management Requirements for Defense Contracts, MIL-HDBK-61B Configuration Management Guidance (Guidance Only), the Contractor's Government-approved CMP, and the PEO IWS5 CMP provided as GFI, Attachment J-3. The CM effort shall include identification and control of all system functional, allocated, and product baselines, and in addition, control of the AN/SRQ-4 RTS CIs, processes, and documentation. The Contractor's CM program shall identify and implement baselines; provide an audit trail of configuration changes; as well as identify, document, and provide the status of the functional and physical characteristics of each CI. The Contractor shall support PEO IWS5 configuration control policies as per the PEO IWS5 CMP provided as GFI, Attachment J-3, to ensure designated baselines are properly communicated and coordinated through stakeholders at both the Government and Contractor level. The following apply to this SOW and are provided for clarity:

• Functional Baseline: The approved configuration documentation describing a system’s top level CI’s performance (functional, inter-operability, and interface characteristics) and the verification required to demonstrate the achievement of those specified characteristics, i.e., Prime Item Development Specification for the AN/SRQ-4 (Ku).

• Allocated Baseline: The approved performance oriented documentation for a CI, which describes the functional and interface characteristics that are allocated from those of the higher level CI, and the verification required to demonstrate achievement of those specified characteristics, i.e. Weapon Replaceable Assemblies (WRA) and SRA specifications, and Interface Control Documents (ICDs) and Acceptance Test Procedures (ATPs).

• Approved Configuration: The specific revision number of the documents in the Functional and Allocated Baselines cited above to which a CI is built plus Government-approved variances from that baseline.

• Product Baseline: The approved technical documentation that describes the configuration of a CI during the production, fielding/deployment and operational support phases of its life cycle.

Once hardware and/or software begin any validation or verification testing, any change to the hardware or software shall be approved by the Government. The Government may require regression testing or retest for each change that is approved. Any and all changes to the baseline shall be done via Government-approved ECP and shall be reported in accordance with CDRL A009 - Engineering Change Proposal (ECP).

3.1.10 CONFIGURATION MANAGEMENT PLAN (CMP) (X008)

The Contractor shall develop and deliver a CMP in accordance with CDRL A010 – Supplier’s Configuration Management Plan. All Circuit Card Assemblies (CCAs) and SRAs shall be Configuration Control Items regardless of who performs Intermediate (I)-Level, Organizational (O)-level or Depot (D)-level repair and maintenance. The CMP shall cover all production efforts by the Contractor in support of the existing primary equipment production and production of current support equipment. The need for any additional trainer/training devices, support/peculiar equipment, software, etc., shall be addressed by the Contractor.

3.1.11 CONFIGURATION STATUS ACCOUNTING DATA

The Contractor shall establish a Configuration Status Accounting (CSA) system to collect and record data of the current and approved baseline configuration throughout the CI(s) lifecycle in order to support and enable an efficient configuration management process. These practices shall be in accordance with the Contractor’s Government-approved CMP.

The Contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs in accordance with CDRL A011 – Cost Data Summary Report (DD Form 1921), CDRL A012 – Functional Cost-Hour Report (DD Form 1921-1), CDRL A013 - Progress Curve Report (DD Form 1921-2), and CDRL A014 - Contractor Business Data Report (CBDR). The Contractor shall:

a. Use the most current approved DoD 5000.04-M-1 Production Contract CSDR Plan, DD Form 2794 as the baseline for reporting.

b. Provide relevant DD Form 1921, 1921-1, and 1921-2 for every indicated element identified within the Production Contract CSDR Plan.

c. Provide updates to the Contract CSDR Plan and Resource Distribution Table (RDT) for Government approval via the Cost Working Group Integrated Product Team (CWGIPT). Updates include, but are not limited to: aligning reporting Subcontractor effort to a single WBS element and updating the RDT as new Subcontracts are awarded.

d. Flow-down Contractor Cost Data Reporting requirements to any Subcontracts valued at over $50 million or any Subcontracts valued between $20 million and $50 million that are designated by the program as high risk, high value, or high technical interest. Reporting thresholds are inclusive of all anticipated contract options and modifications and are given in then-year dollars.

e. Participate in a post award conference after contract award to include a discussion of the contactor’s CSDR process that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR plan for the contract, DD Form 2794, and related Resource Distribution Table.

3.1.12 PROPOSED SPECIFICATION CHANGE NOTICE (PSCN) (X008)

The Contractor shall request changes to the Functional and Allocated Baselines via PSCNs. The Contractor shall submit PSCNs in accordance with CDRL A015 – Specification Change Notice (SCN), for any proposed changes or revisions. Multiple PSCNs may be submitted under a single ECP.

3.1.13 WAIVERS (X008)

The Contractor shall submit all requests for major deviations, using MIL-HDBK-61B as guidance. Disposition of minor deviations shall be in accordance with ANSI/EIA-649C, ANSI/EIA-649-1, the Contractor's Government-approved CMP, and the PEO IWS5 CMP.

3.1.14 ENGINEERING CHANGE PROPOSAL (ECPs) (X008)

The Contractor shall request Government approval to modify the Product Baseline via ECPs. The Contractor shall classify ECPs as Class I or Class II in accordance with ANSI/EIA-649C, ANSI/EIA-649-1, the Contractor’s Government-approved CMP, and the PEO IWS5 CMP. The Contractor shall submit proposed Class I ECPs to the Government for disposition in accordance with CDRL A009– Engineering Change Proposal (ECP). The Contractor shall submit proposed Class II ECPs to the Government Technical Point of Contact (TPOC) as well as the on-site Defense Contracting Management Agency (DCMA) representative for concurrence in classification as directed by

TPOC.

3.1.15 INCREMENTAL FUNCTIONAL/PHYSICAL CONFIGURATION AUDITS (FCA/PCA) (X008)

After Government confirmation the AN/SRQ-4 (Ku) RTS system has successfully demonstrated that it meets all performance requirements, the Contractor shall support a Functional Configuration Audit (FCA), and a Physical Configuration Audit (PCA) conducted by the Government at the Contractor's facilities in accordance with the Contractor's Government-approved CMP and FCA/PCA Plan. The Government will control the Product Baseline following a successful PCA. The Contractor shall produce and deliver Functional and Physical Configuration Audit plans in accordance with CDRL A016 – Configuration Audit Plan.

3.1.16 CONTRACT DATA REQUIREMENTS LISTS (CDRLs) (0004)

The data to be furnished under this contract shall be prepared in accordance with C-245-H005 and DFARS PGI 211.201.

3.2 PRODUCTION SUPPORT SERVICES (PSS) INTEGRATED LOGISTICS SUPPORT (ILS) (X008)

3.2.1 ILS MANAGEMENT (X002)

The Contractor shall manage the ILS efforts for the CDL Hawklink and shall provide a single ILS point of contact to function as the ILS Lead, who will be responsible for all Logistics Elements and participate in Program and ILS meetings. As a part of this function, the Contractor’s ILS Lead shall:

a. Provide timely and appropriate/useful responses that completely address communications provided by the Government related to ILS specific issues and completely address communications provided by the Government which are addressed to logistics functional departments;

b. Ensure logistics engineers review drawings;

c. Ensure supportability and maintainability concepts are taken into consideration;

d. Maintain communications with other qualified contractors, subcontractors, and vendors to ensure effective

Logistics management of the program;

e. Ensure all Logistics Elements are current and that the Logistics Management Information (LMI)

Database is updated in accordance with paragraph 3.2.4.

The Contractor’s ILS lead and components engineer shall attend Diminishing Manufacturing Sources and Material Shortages/ DMSMS Management Team (DMSMS/DMT) Reviews, ILS working group meetings, and ILS Telecoms.

3.2.2 AN/SRQ-4 RTS IETM

The Contractor shall deliver and update the AN/SRQ-4 RTS Interactive Electronic Technical Manuals (IETMs) source data to include diagnostics source data, test and troubleshooting, remove and replace procedures for all affected systems, and illustrated parts breakdowns in accordance with CDRL A017 – Manuals, Technical: Aircraft Maintenance Instructions, Technical Content Requirements. IETM source data shall include the following:

a. Functional description,

b. Functional block diagrams,

c. Theory of operation,

d. Operating procedures,

e. Component locations,

f. Removal and replacement procedures,

g. Leading particulars,

h. Fault detection/fault isolation,

i. Built in Test (BIT) information,

j. Operational checkout procedures,

k. Adjustment procedures,

l. Support equipment requirements and usage,

m. Schematics,

n. Power distribution information,

o. Safety information,

p. Illustrated Parts Breakdown (O-level maintenance),

q. Preventative Maintenance Requirements, and;

r. All procedures necessary to load software on delivered equipment.

3.2.3 IETM VALIDATION AND VERIFICATIONS

The Contractor shall demonstrate the technical accuracy and adequacy of all AN/SRQ-4 (Ku) RTS source data content through validation. The Government reserves the right to witness the validation and shall be notified 30 days prior to the validation. Government observation of the validation will not constitute a verification of the source data. The Contractor shall deliver a final validation report in accordance with CDRL A018 -Validation Report. The Contractor shall deliver updates to source data resulting from the Government’s IETMs verification in accordance with CDRL A017 – Manuals, Technical: Aircraft Maintenance Instructions, Technical Content Requirements. The Contractor shall review all AN/SRQ-4 (Ku) RTS TMERs and Technical Publications Deficiency Reports (TPDRs) provided by the Government. The Contractor shall incorporate all Government-approved TMERs and TPDRs into source data.

3.2.4 LOGISTICS MANAGEMENT INFORMATION (LMI)

The Contractor shall deliver and maintain the LMI database by submitting original and revisions to the AN/SRQ-4 RTS LMI database for the organizational level activity, in accordance with CDRL A019 – Logistics Management Information (LMI). The Government will supply this database to the Contractor. The Contractor shall perform and document analyses to support maintenance planning/design interface, supply support, support equipment, technical data, facilities, packaging/ handling storage and transportation, manpower and personnel, computer resources support and training. MIL-HDBK-502, MIL-HDBK-502A Product Support Analysis, SAE GEIA-STD-0007B Logistics Product Data, and SAE GEIA-HB-0007B Logistics Product Data Handbook should be referred to as guidance. The LMI database file shall provide the Government the ability to print organizational level maintenance plans for review and approval. The maintenance plan shall consist of three (3) parts. Part I is a summary of the system and shall include the items that make up the system in a top down indenture; Part II shall include nomenclature, maintenance significant consumables, critical safety items, removal replacement factor, SM&R codes, Work unit codes (WUCs), part numbers, and stock numbers if available; and Part III shall include fault isolation task with the appropriate support equipment to perform the task at each maintenance level. All LMI database file deliveries shall identify all corrections and updates from previous delivery. For configuration purposes, each LMI database delivery shall be identifiable by month and year of delivery. For the AN/SRQ-4 (Ku) RTS, organizational level maintenance activities shall include all WRAs, SRAs, and Line Replaceable Units (LRU).

The LMI database shall be populated with the data and analysis used to generate the Level of Repair Analysis (LORA) reports.

3.2.4.1 LEVEL OF REPAIR ANALYSIS (LORA) (X008)

The Contractor shall deliver a LORA report in accordance with CDRL A020 - Level of Repair Analysis (LORA) Report that recommends repair or discard decision alternatives for maintenance of the AN/SRQ-4 (Ku) RTS at the Organizational, Intermediate and Depot levels. The LORA shall address both economic and non-economic factors.

3.3 OTHER DIRECT COSTS (ODC) (X003)

ODC includes travel, incidental material and other miscellaneous costs in support of LOE CLINs X002 and X008 are to be included on a cost-only basis (non-fee-bearing). The Contractor will be reimbursed for allowable travel costs incurred during the entire period of performance of this contract in accordance with FAR 31.205-46.

4.0 PROVISIONING DATA (X008)

4.1.1 PROVISIONING PARTS LISTS

The Contractor shall deliver the AN/SRQ-4 RTS Provisioning Parts Lists (PPLs) containing the end item or assembly and all support items which can be disassembled, reassembled, or replaced, and which when combined, constitute the end item, component or assembly in accordance with CDRL A021 – Provisioning Parts List. The PPLs shall be traceable to the LMI database and support provisioning for maintenance to the CCA and SRA level.

The summaries shall include:

• Part Number

• Commercial and Government Entity Code (CAGE) Code

• Item Name

• SM&R Code

• Full Reference Designator (each occurrence)

• Shelf Life (if applicable)

• Production Lead Time

• Quantity

• Unit of Issue

• Unit of Issue Price

4.1.2 ENGINEERING DATA FOR PROVISIONING (EDFP)

The Contractor shall deliver the AN/SRQ-4 RTS EDFP in digital form compatible with Joint Engineering Data Management Information Control Systems (JEDMICS) in Compact Disk Data Exchange (CDEX) format in accordance with CDRL A022 – Engineering Data for Provisioning (EDFP).

4.1.3 INTERIM SUPPORT ITEMS LIST (ISIL)

The Contractor shall deliver and update recommended spares and quantities in support of AN/SRQ-4 (Ku) RTS production and deployment. The items included in the ISIL shall be based on the AN/SRQ-4 (Ku) RTSs maintenance concept. The ISIL shall include part number, nomenclature, SM&R Codes, Cage, Mean Time Between Failure (MTBF), quantity per end item, until price, production lead time, shelf life, quantity per system, next higher assembly, and recommended quantities in accordance with CDRL A021 – Provisioning Parts List.

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

The Contractor shall deliver and update the AN/SRQ-4 RTS PHS&T summaries to identify packaging, handling, storage and transportation requirements in accordance with CDRL A023 – Logistics Product Data Summaries. The PHS&T summaries shall be traceable to the LMI database.

4.1.5 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

The Contractor shall develop, deliver, and implement an AN/SRQ-4 RTS DMSMS Parts Management Plan in accordance with CDRL A024 - Parts Management Plan.

The Contractor shall be responsible for all solutions and corrective actions that would affect system production, production schedule, repairs, defective part fall-out for the production of AN/SRQ-4 RTS systems that are delivered under the Period of Performance (PoP) of this contract. The Contractor shall provide a Master Obsolete Provisioning Parts List (MOPPL) in accordance with CDRL A023 – Logistics Product Data Summaries.

4.1.6 BILL OF MATERIAL (BOM)

The Contractor shall develop and deliver a BOM in accordance with CDRL A025 – Bill of Materials (BOM) for Logistics and Supply Chain Risk Management for all WRAs, SRAs, assemblies, components, and Commercial-Off-the-Shelf (COTS). The Contractor shall enter the BOM information and data in a commercial DMSMS tracking service of their choice which is described and outlined in their DMSMS Management Plan. The Contractor shall also deliver and support the entry of the delivered BOM data into the Government Obsolescence Management Information System (OMIS) as a Government Repository and assist the OMIS Data Base Manager in the alignment of obsolete part cases and adjudication of discrepancies affecting the Contractor’s and Government monitoring process. The OMIS database is managed by the Government at Naval Undersea Warfare Center Keyport.

As part of this contract, the Contractor shall flow-down all BOM development and monitoring responsibilities to all parts suppliers, subcontractors, vendors and COTS manufacturers and suppliers.

The Contractor shall deliver all BOM data covering the entire AN/SRQ-4 RTS system configuration to the piece-part level, including manufacturer and vendor part numbers.

4.1.7 DMSMS/OBSOLESCENCE STATUS REPORTS AND OBSOLETE PART END-OF-LIFE NOTES

(X002)

The Contractor shall provide DMSMS obsolescence status in accordance with CDRL A025 –Bill of Materials (BOM) for Logistics and Supply Chain Risk Management which address the results of on-going monitoring and/or tracking of BOM components and other methods of identifying DMSMS/Obsolescence. The Contractor shall identify and describe new, on-going, potential, and closed DMSMS/Obsolescence issues in accordance with CDRL A024 - Parts Management Plan. The Contractor shall also make recommendations for cost effective sustainability through Life-of-Type Buys (LTBs), alternate/substitute parts, and other mitigation methods for obsolete parts in the delivered MOPL for five (5) year forecast of post-production repairs. If applicable, these reports shall address the current and any planned future LTBs of the obsolete piece-parts and components including recommendations for the future procurements, LTBs, Foreign Military Sales (if applicable) and second source part/vendors. These reports shall include tentative completion schedules for DMSMS actions required for mitigation and closure of obsolete part case, Rough Order of Magnitude (ROM) and recurring costs by year for the reported obsolete component issue(s) shall also be included. Additionally, these reports shall include parts monitoring and tracking to identify DMSMS and obsolete parts for implementation of solutions. The Contractor shall monitor all active electrical/electronic and any other high risk parts outlined in their Management Plan (e.g., relays, switches, data transfer assemblies/switches, ferrite, filters, insulators, special parts resistant to vibration/heat/humidity, etc.).

4.1.8 DMSMS ANALYSIS OF ALTERNATIVES (AOA) CASE SHEET

The Contractor shall develop the AoA Case Sheets. The Contractor shall provide AoA Case Sheets in accordance with CDRL A026 – Technical Report-Study/Services: AoA Case Sheets. All identified DMSMS and/or obsolete parts identified shall be documented with an individual AoA Case Sheet. Based on the identified DMSMS issue the Contractor shall establish and include a mitigation and/or solution strategy and provide the Program Office with the options that were considered and the rationale for the recommendations. These options shall be listed based on their cost/benefit and possible complication of implementation. Based on the demand model provided by the Contractor shall determine the demand quantities for production, spares, repair, fallout, and Foreign Military Sales (if applicable). The recommended demand quantities shall also include information related to new technology roadmap upgrades, ECPs, etc. For proposed DMSMS mitigation approaches, the Contractor shall perform and use a Total Life Cycle Systems Management (TLCSM) approach to determine the best value in accordance with CDRL A027 – Technical Report-Study/Services: Total Life Cycle Systems Management Approach.

4.1.9 SUPPORT EQUIPMENT RECOMMENDATIONS DATA (SERD)

The Contractor shall identify all equipment required to support the AN/SRQ-4 RTS equipment and shall deliver SERD in accordance with CDRL A019 – Logistics Management Information (LMI).

4.1.10 PRODUCTION ENGINEERING

The Contractor shall implement an IEEE 1220, or equivalent, systems engineering management program in support of production efforts. The Contractor shall maintain and deliver a Systems Engineering Management Plan (SEMP) consistent with their configuration management program and shall be available for review by the Government in accordance with CDRL A028 – Systems Engineering Management Plan. The Contractor shall assign a Lead Engineer to coordinate production efforts.

4.1.11 ENGINEERING MEETINGS (X002)

The Contractor shall support bi-weekly status meetings. The Contractor shall status the next two (2) weeks of activity at each weekly engineering meeting and at each weekly test working group meeting and provide Contractor test start date to the Government TPOC prior to start of testing.

4.1.12 REQUIREMENTS MANAGEMENT

The Contractor shall deliver and update requirements traceability in a Dynamic Object-Oriented Requirements System (DOORS) TM Database. At a minimum, the database shall provide a record of performance requirement allocation, performance requirements traceability and performance verification. Traceability shall be established and updated in a single database from the Functional Baseline Documents (Items 1-3, 5, 5A and 16 in Table I) to all contractor-generated lower tier documents including specifications, ICDs, and test procedures; and including requirements allocated to subcontractors and subcontractor lower tier documents. The Contractor shall ensure each of the lower level requirements is verifiable and unambiguous. The Contractor shall deliver the complete DOORS TM Database in accordance with CDRL A029 – Dynamic Object-Oriented Requirements System (DOORS) Package.

The Contractor shall deliver a baseline drawing and drawing list package in accordance with CDRL A026 – Technical Data Package. The Contractor shall keep the drawings and associated list current and shall submit updates throughout the contract period of performance. The update shall be a complete set of drawings and list, not just changes. All drawings and drawing revisions necessary to produce the AN/SRQ-4 RTS shall be delivered regardless of the maintenance concept. As part of the initial baseline engineering drawing and list package, and also in subsequent submissions, the Contractor shall include the latest version of the drawing tree containing all the engineering drawings and lists, including software, related to the AN/SRQ-4 RTS system. Additionally, a statement of changes shall be submitted with each submittal of CDRL A030 – Technical Data Package that tracks the revision history of each item. All drawings shall be delivered as a separate file and appropriately marked. All software and firmware documentation shall be included as part of CDRL A030 – Technical Data Package.

4.1.13 SPECIFICATIONS AND ICDS

The Contractor shall deliver, update, and maintain the following specifications and ICDs:

a. AN/SRQ-4 RTS WRA Specifications (CDRL A031 – System/Subsystem Specification)

b. AN/SRQ-4 RTS WRA ICDs (CDRL A032 – System/Segment Interface Control Specification)

c. AN/SRQ-4 RTS SRA and CCA Specifications (CDRL A031 – System/Subsystem Specification)

d. AN/SRQ-4 RTS SRA and CCA ICDs (CDRL A032 – System/Segment Interface Control Specification)

These specifications and ICDs shall address software as well as hardware. All specifications and ICDs, including GFI items shall be maintained in the Contractor’s DOORS™ database.

4.1.14 QUALITY ASSURANCE

The Contractor shall implement Quality Assurance System (QAS) to ensure conformance to FAR 52.246-11.

4.1.15 RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM

The Contractor shall implement an R&M and BIT program using MIL-STD-785B “Reliability Program for Systems and Equipment Development and Production” as a guide to ensure achievement of the performance requirements and performance specification(s). The R&M program plan shall be delivered in accordance with CDRL A033 – Reliability and Maintainability (R&M) Program Plan. The program plan shall also include a schedule with estimated start and completion points for each R&M and BIT analysis and test task.

4.1.16 FAILURE MODE, EFFECTS AND CRITICALITY ANALYSIS (FMECA)

The Contractor shall perform a FMECA on the system employing the elements covered by tasks 101, 102 and 103 of MIL-STD-1629A Procedures for Performing a Failure Mode, Effects and Criticality Analysis and deliver in accordance with CDRL A034 - Failure Modes, Effects, and Criticality Analysis. To support the FMECA, existing FMECAs may be used providing that all assumptions presumed are consistent with this program and approved by the Government. The analysis shall be performed for all mission scenarios under worst case conditions. It shall address failure modes to all assemblies (CCA and SRA) and their associated WRAs. All single point failure modes having the most serious effect, particularly single point failures which directly result in mission failure or create unsafe conditions shall be identified, evaluated, and minimized via the design process. The FMECA shall clearly identify those failures which are detectable by BIT. The status and results of these analyses shall be detailed at all PMRs.

4.1.17 AN/SRQ-4 (Ku) RTS RELIABILITY PREDICTIONS

The Contractor shall deliver reliability predictions using the Operating High Temperature listed in Radio Technical Commission for Aeronautics (RTCA)/DO-160G, Section 4.0, Category B1in accordance with CDRL A035 – Reliability and Maintainability Predictions Report. The Contractor shall develop a math model, allocation, and design reliability prediction for the system. To support the prediction process, existing predictions for existing equipment may be used provided that all assumptions employed are consistent with this program. The predictions shall be performed using stress analysis. Part failure rates shall be consistent with the individual piece part procurement specification requirements. The prediction shall be done for continuous operation under the appropriate environment for steady state worst case conditions (for all missions). To evaluate the prediction against the individual equipment specification reliability, the specified steady state continuous operating worst case temperature shall be used. Pertinent information from other analyses shall be used as applicable (i.e., thermal analyses, worst case analysis). The Contractor shall redesign, as necessary, to meet the reliability, parts de-rating and junction temperature requirements specified in the equipment specifications. The Contractor shall combine assessments using actual data on Contractor Furnished Equipment (CFE) and GFP with predictions from newly designed or modified CFE and GFE to develop an overall system reliability prediction.

4.1.18 RELIABILITY CRITICAL ITEMS

The Contractor shall implement a program for identification, control, monitoring, and assessment of critical parts, components, subsystems, or other items, using MIL-STD-785B, Task 208. Items (1) through (12) of MIL-STD- 785B paragraph 208.3.1(a) shall be used in determining criteria to identify reliability critical items. A complete list of reliability critical items and control activities shall be delivered in accordance with CDRL A036 – Reliability Critical Items List.

4.1.19 LIFE LIMITED ITEMS

The Contractor shall maintain the list of items that change significantly with age (i.e. have a life limit that would cause failure within 10,000 operating hours and/or a 10 year period) and whose change would degrade the reliability of the equipment in accordance CDRL A037 – Failure Analysis and Corrective Action Report.

4.1.20 MAINTAINABILITY PREDICTIONS

The Contractor shall conduct maintainability and BIT allocation, predictions and analyses of the system in accordance with MIL-HDBK-472(1) Maintainability Prediction as a guide. Maintainability design and analysis shall be performed using Tasks 201 through 207 of MIL-HDBK-470A “Designing and Maintaining Maintainable Products and Systems.” To support the prediction process, existing predictions on existing equipment may be used if the assumptions employed are consistent with this program. The Contractor shall combine assessments using actual data on CFE and GFE with predictions from newly designed or modified CFE and GFE to develop an overall system maintainability prediction. Hardware, software/firmware, as well as all design changes shall be reviewed and assessed for impact to maintainability. Design changes shall comply with the Contractor's engineering where maintainability performance does not meet specified requirements. Existing, new and modified design shall incorporate the following aids to maintenance:

a. Status/monitor capability while equipment is performing mission, and

b. Organizational level Fault Detection and Fault Isolation (FD/FI) by BIT to the SRA level for the AN/SRQ-

4 (Ku) RTS.

Maintainability design, assessment, analyses, and repair time predictions shall be submitted as part of the Maintainability Predictions in accordance with CDRL A035 – Reliability and Maintainability Predictions Report.

4.1.21 FAILURE REPORTING, ANALYSIS AND CORRECTIVE ACTION SYSTEM

The Contractor shall implement a closed-loop Failure Reporting Analysis and Corrective Action System (FRACAS) using MIL-STD-785B as a guide. FRACAS reporting shall commence upon contract award and shall include historical failures from previously delivered part numbers. The entire raw FRACAS failure database as well as a FRACAS status summary report shall be delivered to the Government monthly in accordance with CDRL A037– Failure Analysis and Corrective Action Report. Additionally, the Contractor shall incorporate failure data provided by the Government into the FRACAS database.

FRACAS reporting shall include all chargeable hardware and software failures at all equipment levels (WRA and SRA) on every AN/SRQ-4 (Ku) RTS. Any operating discrepancy that requires an equipment repair or an unscheduled maintenance procedure shall be treated as an equipment failure for reporting purposes. The FRACAS data shall be traceable to equipment serial number. The FRACAS data shall include failure cause data down to the piece part level and include the part’s reference designator (REF DES). The recording and analysis data of a failure shall differentiate between, but not be restricted to, those due to equipment failure, and those due to human error in handling, transporting, storing, maintaining, and operating the equipment. A software-based record of operating elapsed time shall be provided in each AN/SRQ-4 RTS delivered to report accumulated operating time or cycles.

For failures of GFE, the failure cause shall include identification of the failed subassembly and its REF DES. The reporting level shall be down to the piece part level and include the part’s REF DES.

4.1.22 FAILURE REPORTING (X002)

Failures, BIT anomalies and non-conformances experienced on all components, SRAs, modules and end item articles during laboratory, qualification, R&M, and BIT tests/demonstrations, incoming inspection, manufacturing acceptance tests, flight tests and field returns shall be recorded by the Contractor. All failure occurrences shall be recorded, and recording shall be completed with failure and BIT anomalies and corrective actions. The Contractor’s reliability program plan shall establish the formal failure analysis and corrective action system to be used. The Contractor's failure report and failure analysis forms shall be addressed as part of the reliability program plan. The Contractor shall provide a reliability program plan in accordance with CDRL A033 – Reliability and Maintainability (R&M) Program Plan.

4.1.23 FAILURE ANALYSIS (X002)

The Contractor shall perform failure analyses on all failures and BIT anomalies recorded, to the level required to determine the root cause of failure, define the failure mechanism and to develop corrective actions to eliminate or limit their recurrence.