ATTACH08_PWS_PocketJ_Rev01.pdf

PERFORMANCE WORK STATEMENT

For

Pocket J Contractor Logistics Support (CLS)

AN/FSC-134 INTEGRATED SYSTEM CONTROL (POCKET J FIXED ELEMENT (FE))

AN/FSC-135 COMMUNICATIONS DATA LINK SYSTEM (POCKET J REMOTE ELEMENT (RE))

Purchase Request: FD2060-22-30573

November 03, 2022

DISTRIBUTION STATEMENT D: - Distribution authorized to the Department of Defense and DoD Contractors only: Administrative or Operational Use, 15 October 2018. Other requests shall be referred to AFLCMC/WNY, 235 Byron Street, Suite 19A, Robins Air Force Base, GA 31098-1813.

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

PR: FD2060-22-30573 PWS Revision 1: Final 2 Distribution Statement: D

PR: FD2060-22-30573 PWS REVISION 1: Final Distribution Statement D: ………..

HANDLING AND DESTRUCTION NOTICE - …………

Revision History

Revision # Date Updates

1 28 Oct 2022 • Updated date on page 1 to November 03, 2022.

• Updated paragraph 4.2 - Contract Data Requirements List(s) (CDRL)

• Updated paragraph 4.5.1 – Help Desk to remove the word “business hour” and replace with “one hour”.

• Updated paragraph 4.7.1 – General Inspections

• Updated paragraph 5.2.2 – Operations Security (OPSEC)

• Updated paragraph 6.2 – Cybersecurity Vulnerability Management

• Updated paragraph 6.3 - Information Assurance Products final sentence to read, “The Government will provide the ITAC information to the contractor.”

• Removed original paragraphs 6.13.1, 6.13.2, & 6.13.3.

• Updated (new renumbered) paragraph 6.13.1 - Remote Software and Configuration Updates in regards to how often the patches will be applied (quarterly).

• Updated table of contents to remove the 3 above paragraphs and renumbered the rest of the section of 6.13. Updated table of contents with newly added paragraph #’s of 6.14, 6.14.1, 6.14.2, 6.14.3, 6.15, 6.15.1, and 6.15.2.

• Added paragraphs 6.14 - Program Protection,

6.14.1 - Cybersecurity and Trusted Systems and Networks, and 6.15 - Supply Chain Risk Management (SCRM)

PR: FD2060-22-30573 PWS Revision 1: Final 3

• Updated paragraph 7.1.2 – Engineering Change Proposal (ECP) to remove the following words, “24 hours during the work week and 72 hours during the weekend.” And replaced with the following timeline, “two weeks (14 calendar days) from the point of discovery.”

• Updated 8.1.1 - Required Block Cycle Change

• Updated paragraph 9.0 – User Familiarization

Training to remove the following sentence, “The CO will exercise the option for the training CLIN IAW the contract terms based on the requested training.”

• Updated paragraph 10.1 - Documentation of Pocket J Implementation of MIL-STD-6106.

PR: FD2060-22-30573 PWS Revision 1: Final 4

TABLE of CONTENTS

Para Name

1.0 Description of Services

1.1 Objective(s)

1.2 Background

1.3 Benefit to United States Air Force (USAF)

2.0 Services Summary

3.0 Government Property

3.1 Contractor Responsibility

3.2 Government Property-Provided

3.2.1 Specialized Tools/Test Equipment to be provided

3.3 Reporting of Government Property

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

3.4.2 Reporting Loss of Government Property

3.5 Return of Government Property

3.6 Government System(s)

4.0 Technical Requirements

4.1 Ordering Period and Place of Performance

4.1.1 Contract/Ordering Period

4.1.2 Place of Performance

4.2 Contract Data Requirements List(s) (CDRL)

4.2.1 Quality of CDRL Deliverable

4.2.2 Submission of CDRL Deliverable

4.2.3 Receipt of CDRL Deliverable

4.2.4 ---

4.3 Program Management

4.3.1 Subcontract Management and Associate Contractor Agreements (ACAs)

4.3.1.1 ---

4.3.1.1.2 ---

PR: FD2060-22-30573 PWS Revision 1: Final 5

4.3.1.1.3 ---

4.3.1.1.4 ---

4.3.1.1.5 ---

4.3.1.1.6 ---

4.3.1.1.7 ---

4.3.1.1.8 ---

4.3.1.1.9 ---

4.3.1.1.10 ---

4.3.1.1.11 ---

4.3.2 Meeting Support

4.3.3 Diminishing Manufacturing Sources and Material Shortages

(DMSMS)

4.3.4 Quality

4.3.5 Configuration Management (CM)

4.3.6 Transition Plan, Phase in

4.3.7 Transition Plan, Phase Out

4.4 Government Furnished Equipment (GFE) Management

4.4.1 Contractor Furnished Material

4.5 Maintenance Support

4.5.1 Help Desk

4.5.2 Scheduled Maintenance

4.5.3 Unscheduled Maintenance

4.6 Engineering Services

4.6.1 KG-250X Integration

4.7 Hardware, Inspections, Repair

4.7.1 General Inspections

4.7.2 Repair

4.7.2.1 Beyond Economical Repair (BER)

4.7.2.2 MILSTRIP Repair

4.7.2.3 Counterfeit Electronic Parts

PR: FD2060-22-30573 PWS Revision 1: Final 6

4.7.2.4 Parts Approval Request

4.7.2.5 Final Inspection

4.7.2.6 Final Acceptance Testing

4.8 Over and Above

4.8.1 Over and Above Maintenance

4.8.2 Over and Above Repair

4.9 Travel

4.10 Technical Data

4.11 Provisioning

4.12 Deficiency Reports

4.12.1 Deficiency Reporting, Investigation, and Resolution (DRI&R)

4.13 Demilitarization

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.2 Security Requirements

5.2.1 Security Regulations

5.2.2 Operations Security (OPSEC)

5.2.3 Communications Security (COMSEC)

5.2.4 Security Clearance

5.2.5 Security Incident or Violation

5.2.6 Access to Government System(s)

5.2.7 Access to Government Facility or Military Installation

5.2.8 Identification (ID) Card/Badge

5.2.8.1 - -

5.2.8.2 - -

5.3 Environmental Management System (EMS)

5.4 Agency Affirmative Procurement Programs

5.5 Safety Requirements

5.5.1 Contractor Compliance

5.5.2 Mishap Notification / Investigation

PR: FD2060-22-30573 PWS Revision 1: Final 7

5.5.3 Voluntary Protection Program (VPP)

5.6 Inspection of Services

5.7 Service Contract Reporting

5.8 Invoicing / Payment and Receipt / Acceptance

5.8.1 ---

5.8.2 ---

5.9 Trafficking in Persons

5.10 Packaging

5.11 Item Unique Identification (IUID)

5.11.1 Marking Requirement

5.12 Government-Industry Data Exchange Program (GIDEP)

5.12.1 - -

5.12.2 Government Industry Data Exchange Program (GIDEP)

Alert/Safe-Alert Report

6.0 Cybersecurity

6.1 Documentation Support

6.2 Cybersecurity Vulnerability Management

6.3 Information Assurance Products

6.4 Cybersecurity Testing

6.5 Cybersecurity Laboratory

6.6 Baselining Vulnerability Management Plan (VMP) Compliance

6.6.1 ---

6.7 Out-of-Cycle Security Patching / Mitigation

6.8 Corrective Action

6.9 NSI & CUI Protection

6.10 Cybersecurity & Systems Security Engineering

6.11 Software Assurance

6.11.1 ---

6.12 Cybersecurity Change Management

6.13 Continuous Monitoring

PR: FD2060-22-30573 PWS Revision 1: Final 8

6.13.1 Remote Software and Configuration Management

6.13.2 Vulnerability and Compliance Scanning

6.14 Program Protection

6.14.1 Cybersecurity and Trusted Systems and Networks

6.14.2 Critical Program Information (CPI) / Anti-Tamper (AT)

6.14.3 Supply Chain Risk Management (SCRM)

6.15 Systems Security

6.15.1 Security Management / Information Protection

6.15.2 Incident Reporting

7.0 Data

7.1 Control Data Requirement and Mandatory Regulations

7.1.1 Status Report

7.1.2 Engineering Change Proposal (ECP)

8.0 Block Cycle Upgrade / Tech Refresh Work Requirements

8.1 Block Cycle Upgrade / Tech Refresh Requirements

8.1.1 Required Block Cycle Change

8.1.2 Change Requests

8.1.3 Acceptance Criteria

8.1.4 Technical Support

8.1.5 Problem Report / Change Request Investigation

8.1.6 Test Environment Support

8.1.7 Independent Validation and Verification (IV&V) Support

8.1.8 Software Maintenance and Updates

8.1.8.1 Computer Software Configuration Items (CSCIs)

8.1.8.2 Testing

8.1.9 Documentation / Trouble Report Fixes

8.1.10 Technical Data

8.1.10.1 Engineering Data

8.1.10.2 In-Process Review (IPR) of the Technical Data Package (TDP)

8.1.10.3 Relationship of Contractor with Subcontractors / Vendors

8.1.10.4 Engineering Data Updates and Revisions

PR: FD2060-22-30573 PWS Revision 1: Final 9

8.1.11 Test

8.1.12 Test Working Group (TWG) Meetings

8.1.13 Test Readiness Reviews (TRR)

8.1.14 Retest & Regression Testing

8.1.15 Development Test and Evaluation (DT&E)

8.1.16 Air Force System Interoperability Test (AFSIT)

8.1.17 Operational Testing

9.0 User Familiarization Training

10.0 Interoperability Systems Management and Requirements

10.1 Documentation of Pocket-J Implementation of MIL-STD-6106 in i- SMART / e-SMART

10.2 Documentation of Pocket-J Implementation of MIL-STD-3011 in i-

10.3 Documentation of Pocket-J Implementation of MIL-STD-6020 in i-

10.4 Government Responsibility Regarding i-SMART / e-SMART

Appx. A References

Appx. B Site Locations

Appx. C Supporting Documents

Appx. D Hardware Line Replaceable Units

Appx. E Systems & Software Applications

Appx. F Acronym List

1.0 DESCRIPTION OF SERVICES

1.1 Objective(s):

This Performance-based Work Statement (PWS) describes the services required to support the Pocket J system. These services include Program Management, management of Government Furnished Equipment (GFE) , Maintenance Support (Help Desk, Scheduled and Unscheduled Maintenance), Line Replaceable Unit (LRU) repair, Travel, Data, Cybersecurity, completion of Block Cycle and Software Upgrades, and Training. The Contractor shall return systems to serviceable condition to the latest hardware configuration approved IAW Appendix C. The Contractor shall determine the most cost effective means of repair for the system consistent with meeting required system performance and Cybersecurity criteria. The goal is to maximize the operational availability and reliability of Pocket J

PR: FD2060-22-30573 PWS Revision 1: Final 10 systems and hardware while minimizing Government logistics support investments required to achieve desired Operational Availability with predictable and affordable sustainment costs.

1.2 Background:

The Pocket J system is the primary ground-based Tactical Data Link (TDL) Gateway supporting Headquarters Air Combat Command and the North American Aerospace Defense Command (NORAD) air sovereignty missions for Home Land Defense (HLD). The Continental United States (CONUS) NORAD Region (CONR) Concept of Operations states: “The Air Defense Sector (ADS) has an immediate requirement for select pockets of radio frequency (RF), Link 16 Tactical Data Link (TDL), and Situational Awareness Data Link (SADL) coverage to adequately execute the NORAD and HLD missions. These pockets will enable the ADS to provide areas of RF multi-TDL coverage for protection of designated high threat metropolitan areas and national security strategic assets. ADS operations are severely limited without Link 16 and SADL capability. Only Link 16 and SADL can fully support the two-way Information Exchange Requirements between ADS sensors, airborne early warning assets, ground-based C2 units, and the fighter aircraft that are routinely required to support

HLD.”

Pocket J enables airborne platforms equipped with SADL and Link-16 to exchange tactical data, thus merging dissimilar systems into a single tactical picture. Pocket J provides Beyond Line Of Sight (BLOS) forwarding of the air picture between the ADS and HLD assets, increasing situational awareness and decreasing tactical reaction time.

Pocket J is comprised of three (3) ground-based elements connected by multiple communications paths, which ensures continuity of operations. The Fixed Elements (FEs) are installed at the ADS and control, monitor, and exchange BLOS information with the Pocket J Remote Elements (REs) installed throughout the CONUS. Three (3) FEs communicate with 36 REs for 39 Pocket J systems in total.

1.3 Benefit to United States Air Force (USAF):

This acquisition will benefit the USAF by providing needed maintenance and Cybersecurity for a system supporting NORAD for HLD missions.

2.0 SERVICES SUMMARY

Performance

Objective

PWS

Reference Performance Threshold

PR: FD2060-22-30573 PWS Revision 1: Final 11

Quality of CDRL Deliverable

4.2.1 There shall be no more than one (1) rejection of any

deliverable. There shall be no more than a total of one (1) rejection(s) of deliverables per month. The Government will reject a deliverable if any technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL, or the content not being accurate and complete in accordance with the CDRL, PWS, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

Submission of CDRL Deliverable

4.2.2 The Contractor shall provide data deliverables via

Multi-user ECP Automated Review System

(MEARS).

http://mears1.redstone.army.mil/mears/Default.aspx

Separately priced data must be accepted in WAWF in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order for the contract line item to be closed out.

Receipt of CDRL Deliverable

4.2.3, 7.1.1 There shall be no more than one (1) late receipt of deliverables per quarter, i.e., no more than a total of four (4) late receipt(s) per contract year. However, there shall be no more than one (1) late receipt of Status Report(s) per contract year. (Ref: para 7.1.1.)

All data/document(s) shall be delivered to the Government by the date(s) indicated on the respective CDRL(s). The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Status Report(s) shall be delivered by the tenth calendar day of the following month in accordance with CDRL A005, Status Report, DI-MGMT80368A (Ref: para 7.1.1.)

PR: FD2060-22-30573 PWS Revision 1: Final 12

GFE Management

4.4

The Contractor shall maintain an updated GFE listing and document as part of the monthly status report. There shall be no more than three errors per listing.

Help Desk

4.5.1

The Contractor shall provide toll free on call technical assistance for operational questions, system troubleshooting & system problem diagnosis. The Contractor shall respond to 95% of all calls (initial response) within one (1) business hour. This metric will be calculated per quarter.

Requests for assistance and actions taken shall be logged into a maintenance database & provided to Program Office in the monthly status reports.

Scheduled Maintenance

4.5.2

The Contractor shall conduct Preventive Maintenance Inspections (PMI) on equipment per agreed schedule. The Contractor shall not miss more than one scheduled site visit per contract year.

Unscheduled Maintenance

4.5.3

The Contractor shall perform unscheduled maintenance as needed. The Contractor shall determine cause of fault/problem within 16 business hours after arrival at the site and restore system to operational capability within 16 business hours after the determination of cause of the fault/problem for Priority 1 sites (100% of the time); Priority 2 sites (95% of the time) and for Priority 3 sites (90% of the time). See appx B for prioritization. This metric will be calculated per contract year.

PR: FD2060-22-30573 PWS Revision 1: Final 13

Service Contract Reporting

5.7 Within 30 calendar days of contract/order award, the

Contractor shall establish a record for the contract/order in the System for Award Management

(SAM).

The Contractor shall report all SCR data for each fiscal year including a count of contractor/subcontractor personnel performing services; all contractor labor hours, including subcontractor labor hours; the total amount invoiced;

and any required Tier 1 subcontractor information in SAM by 31 October of the following fiscal year.

Cybersecurity 6.0 The Contractor shall provide solutions for continuous monitoring, software assurance, configuration management and control, vulnerability management, and Security Information and Event Monitoring

(SIEM).

Status Report 7.1.1 The content & format of the report shall be in accordance with the CDRL. The report shall be delivered by the tenth calendar day of the following month. No more than one late receipt per contract year.

3.0 GOVERNMENT PROPERTY

3.1 Contractor Responsibility

The Contractor shall be responsible for Government property in its possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property; and all other applicable Government regulations. The FAR and applicable supplements can be accessed at the site below.

https://www.acquisition.gov/

3.2 Government Property to be provided

Government property includes GFP, GFM, GFE, special tooling, special test equipment, etc. GFP does include asssets furnished for repair, maintenance, overhaul or modification. The current list of GFP will be housed in the GFP Module of the Procurement Integrated Enterprise Environment (PIEE) system.

3.2.1 Specialized Tools/Test Equipment to be provided

Specialized Tools/Test Equipment (STE) may be made available as GFE, but is currently stored at other vendor locations. In the event GFE is available through this means, it will be the Contractor's

PR: FD2060-22-30573 PWS Revision 1: Final 14 responsibility to coordinate teardown and pickup of available material in coordination with those identified vendors. Arrangements must be made for movement of this GFE no later than 60 days post award.

3.3 Reporting of Government Property

The Contractor shall create and maintain records of all Government property accountable to the contract/order. In accordance with OUSD(A&S)/DPC Memo, 24 Mar 21, Implementation of the Government Furnished Property Module, the Contractor shall record receipt and shipment of Government Furnished Property (GFP) in the GFP Module of the Procurement Integrated Enterprise Environment (PIEE).

In addition, the Contractor shall submit a quarterly physical inventory report for all GFP supplied under the contract via the Chief Financial Officer (CFO) Report template provided by the Program Office. Quarterly submissions are required until such time the Contractor implements electronic transaction reporting or direct input to the Defense Property Accountability System (DPAS).

CDRL A00S, Physical Inventories Report, DI-MGMT-80259/T

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

In accordance with DFARS 252.245-7002, Reporting Loss of Government Property, “loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, theft, loss due to lack of security, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property

Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in the Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil/piee-landing/. Training on how to utilize the GFP module can be found at https://dodprocurementtoolbox.com

3.5 Return or Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed by the Procuring Contracting Officer (PCO), but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than upon completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract. All

PR: FD2060-22-30573 PWS Revision 1: Final 15

Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL) deliverables become the property of the Government upon receipt and shall be delivered to the Government as indicated by CDRL instructions.

3.6 Government System(s)

The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed.

4.0 TECHNICAL REQUIREMENTS

4.1 Ordering Period and Place of Performance

4.1.1 Contract/Ordering Period

The Ordering Period for the ID/IQ contract will be 5-years (one year basic and four 12-monthordering periods) from contract award.

4.1.2 Place of Performance

These services shall be performed at 39, Government, sites geographically dispersed around the continental United States (U.S.) Reference PWS Appendix B, Pocket J Site Locations. Services will also be provided at contractor’s facility capable of hosting a mock-up fixed and remote element (lab) that will be provided as GFE. Contract Ordering Period: June 2023 – June 2028.

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier

DID Title PWS Reference(s)

A001, B001, C001, D001, E001

DI-ADMN-81373 Presentation Material 4.3.2

A002, B002, DI-ADMN-81249, -

81250B

Meeting Agenda 4.3.2; 8.1;

8.1.10.2

C002, D002, E002

A003, B003, C003, D003, E003

DI-MGMT-81948 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

4.3.3

PR: FD2060-22-30573 PWS Revision 1: Final 16

A004, B004, C004, D004, E004

DI-SESS-81875 Configuration Management Plan (MIL-

STD3046)

4.2.2, 4.3.5

A005, B005, C005, D005, E005

DI-MGMT-80368A Status Report 4.4; 4.5; 4.5.1;

4.7.2; 4.8.1;

7.1.1

A006, B006, C006, D006, E006

DI-ADMN-81250C Meeting Minutes 4.3.2; 8.1;

8.1.10.2

A007, B007, C007, D007, E007

DI-QCIC-80553A Acceptance Test Plan 4.7.2.6

A008, B008, C008, D008, E008

TM-86-01R Technical Manual Contract Requirements

(TMCR)

4.10; 8.1

A009, B009, C009, D009, E009

DI-SESS-81000F/T Product Engineering Design Data and Associated Lists

4.6; 4.10; 8.1;

8.1.10.1

A00A, B00A, C00A, D00A, E00A

DI-SESS-81758A Provisioning - Logistics Product Data 4.11; 8.1

A00B, B00B, C00B, D00B, E00B

DI-SAFT-81563 Accident/Incident Report 5.5.2

PR: FD2060-22-30573 PWS Revision 1: Final 17

A00C, B00C, C00C, D00C, E00C

DI-QCIC-80126B Government Industry Data Exchange Program (GIDEP) Alert Response, 5.12.1

A00D, B00D, C00D, D00D, E00D

DI-QCIC-80125B Government Industry Data Exchange Program (GIDEP) Alert/Safe-Alert Report

5.12.2

A00E, B00E, C00E, D00E, E00E

DI-SESS-80639E Engineering Change Proposal (ECP) 7.1.2

A00F, B00F, C00F, D00F, E00F

DI-IPSC-81427B Software Development Plan (SDP) 8.1

A00G, B00G, C00G, D00G, E00G

DI-IPSC-81442A Software Version Description (SVD) 8.1

A00H, B00H, C00H, D00H, E00H

DI-IPSC-81435B Software Design Description (SDD) 8.1

A00J, B00J, C00J, D00J, E00J

DI-SESS-81248B Interface Control Document (ICD) 8.1

A00K, B00K, C00K, D00K, E00K

DI-IPSC-81433A Software Requirements Specification (SRS) 8.1

PR: FD2060-22-30573 PWS Revision 1: Final 18

A00L, B00L, C00L, D00L, E00L

DI-IPSC-81434A Interface Requirements Specification (IRS) 8.1

A00M, B00M, C00M, D00M, E00M

DI-SESS-80643E Specification Change Notice (SCN) 8.1

A00N, B00N, C00N, D00N, E00N

DI-IPSC-81432A System/Subsystem Design Description

(SSDD)

8.1

A00P, B00P, C00P, D00P, E00P

DI-IPSC-81436A Interface Design Descriptions (IDD) 8.1

A00Q, B00Q, C00Q, D00Q, E00Q

DI-MGMT-81803A Item Unique Identification

(IUID)

Marking Plan

8.1

A00R, B00R, C00R, D00R, E00R

DI-MGMT-81945 Phase-Out Transition Plan 4.3.7

A00S, B00S, C00S, D00S, E00S

DI-MGMT-80259/T Physical Inventories Report 3.3

A00T, B00T, C00T, D00T, E00T

DI-MGMT-

81453B/T

Data Accession List (DAL) 4.2.4

PR: FD2060-22-30573 PWS Revision 1: Final 19

A00U, B00U, C00U, D00U, E00U

DI-MGMT-80004A Management Plan 4.3.1

A00V, B00V, C00V, D00V, E00V

DI-MGMT- 82001A DOD Risk Management Framework (RMF) Package Deliverables

6.1, 6.2

A00W, B00W, C00W, D00W, E00W

DI-SESS-81704 Test Plans/Test Procedures 6.4

A00X, B00X, C00X, D00X, E00X

DI-MISC-80508B Technical Report-Study/Services 6.12

A00Y, B00Y, C00Y, D00Y, E00Y

DI-MGMT-82142 Naval Aviation Cybersecurity Test Report 6.12

A00Z, B00Z, C00Z, D00Z, E00Z

DI-SESS-81874 Provisioning - Engineering Data for Provisioning (EDFP)

4.11; 8.1

A0AA,

B0AA,

C0AA,

D0AA,

E0AA

DI-ADMN-81306 Program Protection Implementation Plan

(PPIP)

6.14.2

PR: FD2060-22-30573 PWS Revision 1: Final 20

4.2.1 Quality of CDRL Deliverable

There shall be no more than one (1) rejection of any deliverable. There shall be no more than a total of one (1) rejection(s) of deliverables per month. The Government will reject a deliverable if any technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL, or the content not being accurate and complete in accordance with the CDRL, PWS, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

4.2.2 Submission of CDRL Deliverable

The Contractor shall implement existing data management procedures for the preparation, quality control, administration and delivery of data required by the CDRL, in accordance with the Contractor’s Configuration Management Plan (MIL-STD-3046). The Contractor shall maintain data status and delivery schedules for all CDRL items. The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user ECP Automated Review System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx, The Contractor shall work with the government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system. The Contractor shall prepare, maintain, and track the contract data status, schedule and ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DOD SAFE, https://safe.apps.mil/. It will be available to all DOD Common Access Card (CAC) holders or Contractor personnel who possess Public Key Infrastructure (PKI) certification from an accepted Government source. Separately priced data must be accepted in WAWF in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order for the contract line item to be closed out.

CDRL A004, Configuration Management Plan (MIL-STD-3046), DI-SESS-81875

4.2.3 Receipt of CDRL Deliverable

There shall be no more than one (1) late receipt(s) of deliverables per quarter. All data/document(s) shall be delivered to the Government by the date(s) indicated on the respective CDRL(s). The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.2.4 The Contractor shall maintain a current listing of all non-CDRL data generated in performance of the contract in a Data Accession List (DAL) electronic information system accessible by the Government.

All technical documentation and other data generated in performance of this program shall be made available to the Government via the DAL. The Contractor shall provide a central point of contact for Data Management who shall ensure contract data compliance with the contract.

CDRL A00T, Data Accession List (DAL), DI-MGMT-81453B/T

4.3 Program Management

The Contractor shall assign a PM to plan and execute the tasks required in this PWS. The PM shall be the single Point of Contact for the Government. The Contractor shall support and document monthly management reviews. The Contractor shall identify, assess, and manage risks. Particular https://mears1.redstone.army.mil/mears/Default.aspx https://mears1.redstone.army.mil/mears/Default.aspx

PR: FD2060-22-30573 PWS Revision 1: Final 21 attention shall be paid to risks associated with the Contractor not meeting the requirements of the contract. Risk management shall be fully integrated with all elements of the program.

4.3.1 Subcontract Management and Associate Contractor Agreements (ACAs) The Contractor shall integrate and manage subcontract efforts, if any, required to support Pocket-J deployment and sustainment. If subcontract(s) efforts are required, the Contractor shall generate, maintain and implement a Subcontract Management Plan. The plan shall include, at a minimum, the process and procedures the Contractor shall follow to manage all aspects of the subcontract(s). The Contractor shall monitor the activities of all subcontractors to ensure compliance with all terms and conditions, policies and procedures contained in the subcontract. The contractor, if required, shall identify, include, describe, specify and execute Associate Contractor Agreements (ACAs) for any effort requiring joint contractor participation to accomplish Government Pocket-J program requirements. The Contractor shall enter into ACA for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the success of this contract, which shall ensure the greatest degree of cooperation to meet the terms of the contract.

CDRL A00U, Management Plan, DI-MGMT-800004A

4.3.1.1 ACAs shall include the following general information:

4.3.1.1.2 Identify the associate contractor(s) and their relationships.

4.3.1.1.3 Identify the system(s) involved and the relevant Government contracts of the associate contractors.

4.3.1.1.4 Describe the associate contractor interfaces by general subject matter.

4.3.1.1.5 Specify the categories of information to be exchanged or support to be provided. The Contractors shall share information and data to achieve the requirements as documented in this PWS.

4.3.1.1.6 Include the expiration date (or event) of the ACA.

4.3.1.1.7 Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

4.3.1.1.8 A copy of such agreement shall be provided to the PCO for review before execution of the document by the cooperating contractors.

PR: FD2060-22-30573 PWS Revision 1: Final 22

4.3.1.1.9 The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

4.3.1.1.10 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

4.3.1.1.11 All costs associated with the agreements are included in the awarded cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

4.3.2 Meeting Support

The Contractor shall conduct, attend, support, and participate in a kick-off (within 30 calendar days of contract award), Initial Program Management Reviews (PMR) (Within 90 calendar days of kick-off meeting) and scheduled meetings which are mutually agreed with the Government as necessary to facilitate continued performance improvement and risk. The planned meetings shall include semiannual PMRs at the Government’s choosing. The Contractor’s semi-annual PMRs shall address risk management, program management, cybersecurity, contracting, finance, and logistics status, data, and issues. The frequency of the PMRs may be decreased at Government direction depending upon the program stability. The Contractor shall submit Conference Minutes for each meeting. The Contractor shall submit Presentation Material for meetings. The contractor shall participate in weekly maintenance status telecommunications.

CDRL A001, Presentation Material, DI-ADMN-81373 CDRL A002, Meeting Agenda, DI-ADMN-81249C CDRL A006, Meeting Minutes, DI-ADMN-81250C

4.3.3 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The Contractor shall have a proactive DMSMS program. The loss of sources of items or material, surfaces when a source announces the actual or impending discontinuation of a product, or when procurements fail because of product unavailability. DMSMS may endanger the life-cycle support and viability of the weapon system or equipment. The Contractor shall develop an Obsolescence and DMSMS Management Plan for managing the loss, or impending loss, of manufacturers' or suppliers' parts and/or material required for performance of this contract. The plan shall address the following:

means and approach for providing the Government with information regarding obsolescence and DMSMS issues, planned resolution of current obsolescence and DMSMS issues, parts list screening, parts list monitoring, processing Government Industry Data Exchange Program (GIDEP) (www.gidep.org) DMSMS Alerts, processing DLA DMSMS Alerts, communication with and availability of information to the Government, means and approach for establishing obsolescence and DMSMS solutions, and plan for conducting DMSMS predictions. The "Implementing Parts Obsolescence Management Contractual Requirements", published by the Defense Microelectronics Agency (available at https://apps.dtic.mil/dtic/tr/fulltext/u2/a518172.pdf ) may be used as a guide in developing the Obsolescence Management and DMSMS Plan.

CDRL A003, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan, DI-MGMT-81948 https://apps.dtic.mil/dtic/tr/fulltext/u2/a518172.pdf%20) https://apps.dtic.mil/dtic/tr/fulltext/u2/a518172.pdf%20)

PR: FD2060-22-30573 PWS Revision 1: Final 23

4.3.4 Quality

ISO 9001 or equivalent certification is required to meet Government Standards. The contractor shall maintain hardware and software engineering process standards applicable to military products, military qualification test requirements, verification/validation processes.

4.3.5 Configuration Management (CM)

The Contractor shall provide CM in support of hardware, software, lab, and documentation. The configuration management support for these areas shall provide consistent baseline configurations in the field and in the lab.

The Contractor will maintain a formal CM system for the Pocket J program that includes, at a minimum, the following processes: Configuration Identification, Configuration Control, and Engineering Data Management.

The Contractor shall implement CM, develop, and document the CM Plan (maintained at Contractor facility). Support preparation of required documents to support Configuration Review Board, Technical Review Board and Configuration Control Board may include travel as required.

CDRL A004, Configuration Management Plan (MIL-STD-3046), DI-SESS-81875

4.3.6 Transition Plan, Phase in

To ensure a smooth transition in the change of work effort from the current contract/order, the contractor shall begin the transition period upon contract/order award. The Contractor shall provide a comprehensive transition plan to the PMO with-in 15 calendar days of contract award using best commercial practice such as Microsoft Project or equivalent which includes but not be limited to:

• Prepare facility for GFE storage and lab setup

• Complete employee training requirement specific to Pocket J

• Complete development of necessary work plans/procedures.

• Obtain CAC cards for base facility access

• Obtain security clearances, if required

• Complete the development of quality control plans/procedures

• Complete personnel requirements (workforce) including the hiring of personnel to assure satisfactory performance beginning on the order start date. Soliciting Government or incumbent contractor personnel for employment during their duty hours is prohibited, unless arrangements are made through the contracting and personnel offices at this installation.

• Become thoroughly familiar with work requirements and work procedures

4.3.7 Transition Plan, Phase out

The Contractor shall provide a Phase Out transition Plan 90 calendar days prior to contract expiration. The Contractor shall provide a written comprehensive plan explaining actions required to complete the total transition effort using a 60 calendar day transition period utilizing best commercial practice which includes but not limited to:

• Details for the removal of all contractor owned items

• Turn in of Government provided Common Access Cards (CACs)

• Provide current inventory and packaging plan for shipment

• Critical path schedule for risk mitigation of the transition period

PR: FD2060-22-30573 PWS Revision 1: Final 24

• Provide system admin passwords to PMO through secure channels CDRL A00R, Phase-Out Transition Plan, DI-MGMT-81945

4.4 Government Furnished Equipment (GFE) Management

The Contractor shall provide management of and secure storage space for GFE that will be provided under this contract. GFE items will fall into one of three categories, Consumables (Expendables), Contractor Repair (Non Expendable), and MILSTRIP Repair. The Contractor shall provide the necessary labor, materials, facilities and equipment required to analyze, assess Cybersecurity vulnerabilities, troubleshoot, repair, overhaul, integrate and test Pocket J assemblies, parts and the Pocket J Software that is maintained or repaired under this contract. These services also include alignment, adjustment, calibration, testing, movement (shipping), storage and reporting status related services to the repair and return of parts to the user. The Contractor shall maintain an updated GFE listing as part of the monthly status report. There shall be no more than three errors per listing.

Reparable items shall be returned in “A” (serviceable) condition prior to the end of contract. CDRL A005, Status Report, DI-MGMT-80368A

4.4.1 Contractor Furnished Material

The Contractor will procure Consumable/Expendable supplies to support the Pocket J system. These supplies will be stored at Contractor facility and used at Contractor’s facility or shipped to a Pocket J site to replace failed Consumable/Expendable GFE items. Consumable items will be disposed of at the field level in accordance with demilitarization or consistent with accepted commercial practice.

4.5 Maintenance Support

The Pocket J maintenance concept consists of a help desk combined with scheduled and unscheduled maintenance (at FE/RE site) and hardware repair (off-site). SMEs under this contract will be thoroughly trained and certified by the contractor on RE, FE, various Data Link and network operations. Scheduled and unscheduled maintenance support shall be performed by the Contractor and provided on-site by technicians/maintenance personnel. It shall consist of system restoration by fault verification/isolation, removal/replacement of faulty LRU, and functional checkout of all installed REs and FEs using technical manuals and other technical data. The Contractor shall travel to all 39 sites as required to perform duties necessary to restore system. The Contractor shall maintain adequate stock levels of parts required to ensure full and consistent support at required operational levels. The Contractor shall also assist the Government with troubleshooting problems with the TDL Wide Area Network (WAN). Contractor shall provide weekly spreadsheet documenting maintenance actions and planned actions to support weekly teleconference.

CDRL A005, Status Report, DI-MGMT-80368A

4.5.1 Help Desk

The Contractor shall provide toll free on call technical assistance for operational questions, system troubleshooting and system problem diagnosis. The Contractor shall respond to 95% of calls (initial response) within one hour. This metric will be calculated per quarter. Requests for assistance and actions taken shall be logged into a maintenance database and provided to the Program Office in the monthly status report. The status report shall provide monthly and annual maintenance totals to include number of help desk calls, trouble tickets, repair action, LRUs, location, and response/repair time.

PR: FD2060-22-30573 PWS Revision 1: Final 25

4.5.2 Scheduled Maintenance

The Contractor shall provide on-site scheduled maintenance support at least once every 6-months at each of the 39 Pocket J sites. Support shall include, but is not limited to, Preventive Maintenance Inspections (PMI) on the electronic equipment, Configuration Verification/Audits, software and Cybersecurity updates, repair of cables/connectors, replacement of LRUs/Circuit Cards, etc. The Contractor shall conduct PMI on equipment per agreed schedule. The Contractor shall not miss more than one scheduled site visit per contract year. If a fault/problem is detected during visit, Contractor must diagnose fault/problem within 16 business hours and restore system to operational capability within 16 business hours after the determination of cause of the fault/problem.

4.5.3 Unscheduled Maintenance

Unscheduled maintenance is defined as trouble shooting and repairing the Pocket J system as needed to restore it to fully operational condition. Unscheduled maintenance shall be required anytime a Pocket J site is deemed Non Mission Capable (NMC), as defined in the prioritization table (see Appx B). The Contractor shall provide unscheduled maintenance support for all 39 Pocket J sites. The Contractor shall determine cause of fault/problem within 16 business hours after arrival at the site.

Within an additional 16 business hours, the Contractor shall restore system to full operational capability. The Contractor shall comply with the requirements of this section as follows: Priority 1 sites (100% of time), Priority 2 sites (95% of the time), and Priority 3 sites (90% of the time). This metric will be calculated per contract year. It is anticipated that there will be 72 unscheduled maintenance visits annually. If unscheduled maintenance exceeds 72 visits, it will be considered over and above and will be negotiated before issuance of an order.

4.6 Engineering Services:

It is recognized by the parties hereto that during the performance of this contract, engineering services and other system support not forecasted may be required hereunder, and shall be independently estimated and priced on a case by case basis. These activities may include, but are not limited to:

Engineering Services in support of:

System Analysis Failure Analysis Diminishing Source Problems Improved Item Replacement Program (IIRP) R & M Improvements Data Evaluation Analysis Software Updates/Corrective Maintenance (ECPs) Hardware ECPs Deficiency Reports Technical Data Package The Contractor shall produce and deliver a Technical Data Package (TDP) that accurately depicts the final products. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, A. Operation Handbook (OPH) - (At the 35% and 70% completion point ) B. Mx TO—minimal change (At the 35% and 70% completion point ) C. Sys Admin—Configuration Item changes (At the 35% and 70% completion point ) D. Drawings E. Capture all new COTS manuals as applicable

PR: FD2060-22-30573 PWS Revision 1: Final 26

The TDP shall provide the necessary design, engineering, manufacturing, testing, and quality assurance requirements information necessary to include all associated drawings/Mil Standards for items identified on assembly parts lists to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data developed under this contract shall be considered a part of the TDP and shall be delivered to the Government in accordance with clauses in basic contract. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752); reference attached DD Form 1423 Block 16.

MIL-STD-3018

4.6.1 KG-250X Integration

The Contractor shall perform development, integration, testing, deployment and installation activities required such that the KG-250X can be used in place of the KG-250 on all fielded and development Pocket-J systems in order to meet cryptologic modernization mandates. The Contractor shall insure that the KG-250X is compatible with Pocket-J software and hardware baselines. KG-250X deployment is expected to occur within six months after contract award. If this is not feasible, the Contractor shall deploy the KG-250X upgrade in conjunction with the next appropriate Pocket-J Quarterly Update. The Contractor shall provide the Government an entire inventory list of all KG-250s and the model variants (e.g. KG-250X) with a recommendation to retain or dispose for each item within 30 calendar days after the last KG-250X deployment is accomplished.

4.7 Hardware, Inspections, Repair

4.7.1 General Inspections

In the course of repair, overhaul, and restoration, inspections shall be performed in order to ascertain the condition of the incoming equipment. After identification of a needed repair by the Contractor, customer, or AFLCMC/WNY, a separate task order will be issued via the Firm Fixed Price Teardown, Test and Evaluation (TT&E) CLIN. Under the TT&E CLIN, the Contractor will be required to accomplish a TT&E of the equipment before starting repairs and provide a findings report to the PMO (AFLCMC/WNY). The Government will take the provided information and the repair of the asset will be written as a separate task order by the contracting officer and processed under the Repair CLIN.

4.7.2 Repair

The Contractor shall furnish, repair, replace, or provide new components, equipment, and materials that shall conform to Government-approved baseline specifications. The Contractor shall maintain serviceable inventory levels of sufficient quantities to sustain Pocket J system. The new components and material shall be of the same manufacturer, class, grade, type, and function as those being replaced unless otherwise approved by Pocket J PMO. The Contractor may recommend substitutions. However, the Contractor must obtain approval from the Procuring Contracting Officer (PCO) prior to purchasing or installing any substituted component or material. The Contractor shall provide all written specifications and details of the proposed material, component or equipment to the contracting officer or authorized approval authority as designated by the PCO.

The Contractor shall ship parts to and from the site using best commercial practice when replacing failed LRUs at Pocket J locations. Failed LRUs will be processed in accordance with the appropriate

PR: FD2060-22-30573 PWS Revision 1: Final 27 repair CLIN for that item (major/minor). The Contractor shall provide repair services for hardware to provide the LRU-level repair services defined within this PWS. Contractor shall provide status of repairable items in repair cycle. See Appx D for repairable LRU list.

These services also include bench checking LRUs prior to shipping for repair, alignment, adjustment, calibration, testing, shipping, storage, and reporting status related services to the repair and return of equipment to serviceable condition. Contractor furnished material or parts used for replacement shall equal or exceed the quality of the original material or parts. The material or parts shall be entirely suitable for restoration of the end item for its intended purposes. All LRUs (see Appx D of the contract) will be inspected and analyzed for the repair function that will comply with the specifications and requirements as listed in the appropriate TO or data. The Contractor shall repair items to serviceable condition to the latest hardware/software configuration approved by the Government for that item to ensure interoperability between SADL and Link 16 terminal platform variants. The LRU shall be handled, tracked, repaired, stored, and shipped IAW the specifications. A record shall be kept indicating components utilized/repair completed to return each LRU to Class “A” serviceable condition.

4.7.2.1 Beyond Economical Repair (BER)

Beyond Economical Repair is defined as a failure of LRUs where required repairs are beyond 75% of the total value of the LRU. The damage can be confirmed in the course of Inspection, Repair, Overhaul, Restoration, or where the root cause of the failure would indicate the potential of excessive stress on multiple sub-assemblies within the unit. This may include but is not limited to: high voltage, physical, water, or chemical i.e. fire suppression damage. Contractor shall identify BER items to the PCO/PMO for condemnation approval and disposition instructions.

4.7.2.2 MILSTRIP Repair

The Contractor will use the DoD supply system known as Military Standard Requisitioning and Issue Procedures (MILSTRIP) to order and replace failed stock listed Line Replaceable Units (LRUs) identified in Appendix D. Failed items will be shipped back to the supply system. Access to MILSTRIP will be provided by Pocket J PMO.

4.7.2.3 Counterfeit Electronic Parts

The Contractor shall establish policy and procedures to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory in accordance with Aerospace Standard (AS) 5553A, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and…