Attachment 1 PWS 20 July 2023.pdf

PR: FD2060-23-30009 PWS REVISION: 0

DISTRIBUTION STATEMENT: D

Performance-Based Work Statement (PWS) for Contractor Logistics Support and Services of the

Joint Range Extension Gateway (JRE-GW) System, AN/TYQ-123(V)3

Fixed JRE-GW Tactical Equipment Package (JTEP), AN/FSQ-225

Transportable JRE-GW Tactical Equipment Package (JTEP), AN/TSQ-235 and the Joint Range Extension (JRE) software Purchase Request: FD2060-23-30009

Date/Revision: 20 July 2023

DISTRIBUTION STATEMENT D: - Distribution authorized to Department of Defense and U.S. DoD contractors only (Administrative or Operational Use.) (01 Dec 2016). Other request for this document shall be referred to AFLCMC/WNYBBC.

CHANGE LOG

Revision Date Reference Change Contact

Contents

1.0 Description of Services

1.1 Objective (s)

1.2 Benefit to United States Air Force (USAF)

1.3 Background

2.0 Services Summary

3.0 Government Property

3.1 Contractor Responsibilities

3.2 Government Property/Services 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/Retention of Government Property

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

4.1.2 Place of Performance

4.2 Contract Data Requirements List (CDRLS)

4.2.1 Quality of CDRL Deliverable

4.2.2 Receipt of CDRL Deliverable

4.3 Repair/Engineering Services

4.3.1 Item Unique Identification (IUID)

4.3.1.1 Marking Requirement

4.3.1.2 Reporting in IUID Registry

4.3.1.3 Life Cycle Event

4.3.2 Packaging, Handling, Storage and Transportation

4.3.3 Counterfeit Electronic Parts

4.4 Holiday and Facility Closings

4.5 Travel

4.6 System Sustainment

4.6.1 Sustainment and Maintenance

4.6.2 Configuration Management

4.6.3 JRE Softwaresustainment

4.7 Engineering Support Services

4.7.1 Urgent Operational Needs

4.7.2 Engineering Studies

4.7.3 Engineering Change Proposal (ECP)

4.8 Deficiency Reports

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

4.9 Onsite Software Sustainment-Field Support

4.9.1 Unscheduled Maintenance

4.9.2 Scheduled Maintenance

4.9.3 Field Support, Full CONUS/OCONUS SME

4.9.3.1 CONUS SME

4.9.3.2 OCONUS Deployed SME

4.10 Repair Support Services

4.10.1 SAIC 3G Server

4.10.2 Repair, Minor

4.10.3 Repair, Major

4.10.4 Standards

4.10.5 Parts/Components

4.10.6 Obsolescence

4.10.7 Condemnation

4.10.8 Bench Testing

4.11 Stock, Store, Issue Parts

4.11.1 Consumable/Expendable

4.11.2 Contractor Repairable/Non-Expendable

4.11.3 Handling

4.11.4 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

4.12 Training As Needed

4.13 Cybersecurity

4.13.1 Contractor Responsibilities in Cyber Approval

4.13.2 Assess and Authorization

4.13.3 Cybersecurity Controls

4.13.4 Risk Management

4.13.5 Test and Evaluation

4.13.6 Third-Party Software

4.13.7 Assured Compliance Assessment Solution (ACAS) and Security Content Automation Protocol Compliance Checker (SCC)

4.13.8 Audits

4.13.9 Documentation

4.13.10 Cybersecurity Scans

4.13.11 Urgently Required (Out of Cycle) Cybersecurity Fixes

4.14 Technical Support Desk

4.15 Block Cycle Upgrade

4.15.1 Software Updates

4.15.2 Documentation

4.15.3 Tech Refresh (TR) Fixes

4.15.4 Acceptance Criteria

4.15.4.1 31

4.15.4.2 31

4.15.5 Block Cycle Training

4.16 Technical Support

4.16.1 Problem Report/Change Request Investigation

4.17 Engineering Data

4.17.1 In-Process Review (IPR) of the TDP

4.17.2 Relationship of Contractor with Sub-Contractors/Vendors

4.17.3 Engineering Data Updates and Revisions

4.17.4 Provisioning

4.18 Interoperability Systems Management and Requirements Transformation (i- SMART/e-

SMART)

4.18.1 Documentation of JRE Implementation of MIL-STD 6016 in i-SMART/e- SMART

4.18.2 Documentation of JRE Implementation of MIL-STD 3011 in i-SMART/e- SMART

4.18.3 Documentation of JRE Implementation of MIL-STD 6020 in i-SMART/e- SMART

4.18.4 Government Responsibility Regarding i-SMART/e-SMART

4.19 Testing

4.20 Status, Alert and Parts Reports

4.20.1 Progress/Status Reporting

4.20.2 Risk Matrix

4.20.3 Testing status and ATO/ATC status

4.20.4 Monthly Status Reports

4.20.5 Parts Approval Request

4.20.6 GIDEP Alert/Safe-Alert Report and GIDEP Alert Response

4.21 Program Management Review

4.21.1 Teleconferences

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crises

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 Incidents and Violations

5.2.6 Access to Government Systems

5.2.7 Access to Government Facility or Military Installation

5.2.8 Common Access Card (CAC)

5.3 Environmental Management System (EMS)

5.4 Agency Affirmative Procurement Program

5.5 Safety Requirements

5.5.1 Contractor Compliance

5.5.2 Mishap Notification/Investigation

5.5.3 Safety and Health Plan/Program

5.5.4 Voluntary Protection Program (VPP)

5.6 Inspection of Services Clause

5.7 Service Contract Reporting

5.7.1 ........................................................................................................ Error! Bookmark not defined.

5.7.2 ........................................................................................................ Error! Bookmark not defined.

5.7.3 ........................................................................................................ Error! Bookmark not defined.

5.7.4 ........................................................................................................ Error! Bookmark not defined.

5.8 Invoicing/Payment and Receipt/Acceptance

5.9 Quality Management System (QMS)

5.11 Trafficking in Person

Appendices

Appendix A: Site Locations

Appendix B: References

Appendix C: Acronym List

8 PR: FD2060-23-30009 PWS REVISION: 0

1.0 Description of Services

This Performance-Based Work Statement (PWS) provides detailed information for Contractor Logistics Support (CLS) of the Science Application International Corporation (SAIC) Gateway (GW), the Fixed and Transportable JRE-GW Tactical Equipment Package (JTEP), JRE-GW System and the GW software, henceforth collectively referred to as GW systems.

1.1 Objective (s)

The Contractor shall provide gateway systems sustainment/maintenance support, engineering support services, field support, hardware repair supports services, stock, store, and issue, training, cybersecurity (CS), block cycle upgrades, testing, Technical Support Desk (TSD), travel, data, and variable engineering for the. National Stock Numbers (NSNs) and Part Numbers are subject to change as the baseline changes at the system level. Such configuration changes may drive Contract Line-Item Number (CLIN) additions and/or deletions, as mutually agreed to between the Government and Contractor. Manage configuration to meet maintain functional capabilities, modifications, or changes through Engineering Change Proposal (ECP) submitted by the contractor and approved by the Government. The contractor shall repair items to serviceable condition to the latest hardware/software configuration approved and funded by the Government for that item to ensure interoperability between Situation Awareness Data Link (SADL) and Link 16 terminal platform variants.

1.2 Benefit to United States Air Force (USAF)

This acquisition will benefit the United States Air Force (USAF) by providing near real time beyond line-of-sight (BLOS) Link 16 connectivity and routing throughout a theater of operations, between theaters, and from theaters to rear-area Command and Control (C2) centers and provides the ability to link two dissimilar data link networks (Link 16 and SADL).

1.3 Background

The GW system has been supported via Contractor Logistics Support (CLS) with the original equipment manufacturer (OEM) under contracts FA8574-18-D-0004 and FA8523-12-D-0006.

The JRE-GW is a communications router that provides the capability to pass timely secure Link- 16/Tactical Data Link (TDL) J series messages (data) via long haul means BLOS. The transportable JTEP provides AF Control and Reporting Centers (CRC) the capability to interface with SADL and Link-16 radios, thereby establishing near real time link and then transporting that data BLOS throughout a theater of operations and between theaters. The fixed JTEP provides Air National Guard Air Defense Fighter Interceptor Wings with the capability of communicating with their SADL aircraft and routing that information to the Air Defense Sectors (ADS) for Homeland Security. JRE/JTEP supports the following platforms: F-15, F-16. F/A-18, E-3, E-8, Air Operations Center (AOC), Army Missile Defense Systems, Navy & Marine systems.

2.0 Services Summary

Performance

Objective PWS Reference Performance Threshold

9 PR: FD2060-23-30009 PWS REVISION: 0

Repair Support Services 4.10

The Contractor shall repair 100% of reparable items to serviceable condition within the Government established turnaround time of 30 calendar days after receiving parts from the Original Equipment Manufacturer (OEM).

24 Hour Technical Support Desk (TSD)

4.14

The Contractor shall provide a 24 Hour Call-in TSD for users to resolve technical issues. Response time (defined as the time span from when a user calls in with an issue to when the user actually speaks with a Subject Matter Expert) for all calls shall be less than 12 hours. 75% of Resolutions shall be provided in 6 hours or less after communication with the Subject Matter Expert (SME).

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

Submission of Engineering Change

Proposal (ECP) 4.7.3

The Contractor shall submit an ECP for all Class 1 changes within 24 hours during the work week and 72 hours during the weekend. The contractor will notify the Government of all Class 2 changes through Document Change Notices (DCN) within 15 calendar days.

Completion of Block Cycle Upgrade

4.15 The Contractor shall address all approved Change Requests (CR). The contractor shall ensure all changes and upgrades are in compliance with the approved System Requirement Documents (SRD) within 60 calendar days.

Contractor Data Requirements List

(CDRL)

4.2.1

4.2.2

There shall be no more than a total of two (2) rejection(s) of final deliverables per contract year. The Government will reject a deliverable if any technical errors or five (5) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection. There shall be no more than one (1) late submission(s) of deliverables per contract year.

Tech Refresh (TR) Fixes 4.15.3

The Contractor shall resolve all CAT I and CAT II Priority contractor developed software and hardware defects. The contractor shall ensure all changes and upgrades are in compliance with the approved System Requirement Documents (SRD) within 60 calendar days of government approval.

Cybersecurity 4.13.10

The Contractor shall notify the Government Program Manager (PM)/ Information System Security Manager (ISSM) within one (1) business day for a CAT I vulnerability and within two (2) business days for a CAT II vulnerability or below.

10 PR: FD2060-23-30009 PWS REVISION: 0

Onsite Software Sustainment-Field

Support, Unscheduled maintenance

4.9.1 The Contractor shall determine cause of fault/problem within 24 hours after arrival at the site and provide resolution within 48 hours after the determination of cause of the fault/problem.

Onsite Software Sustainment-Field

Support, Scheduled maintenance

4.9.2

Appx A

The Contractor shall conduct Preventive Maintenance Inspections (PMI) on equipment at the listed locations per agreed schedule in Appendix A. The Contractor shall not miss more than one (1) scheduled site visit per contract year without Government approval.

Government Furnished Equipment (GFE)

Management

3.0

3.1

The GFE listings, provided in conjunction with the monthly status reports, shall have no more than a total of three late updates and/or omissions per contract year.

Status Reports 4.20

The Contractor shall provide a data deliverable. The content and format of the report shall be in accordance with the Contractor Data Requirements List (CDRL). The report shall be delivered by the tenth

(10) calendar day of the following month. No more than one (1) late submission per contract year.

Cybersecurity Patch Delivery

4.14 The Contractor shall ship the cybersecurity patches to TSD users except those who receive PMI visits NLT 10 business days after receiving approval from the PMO to release the quarterly update.

The Contractor shall install the latest cybersecurity patch at the sites with schedule maintenance visits within 90 days of a government approved patch update.

Technical Orders Development

4.6.2 The Contractor shall write Technical Orders with no more than 60% USG mark-up on redline review.

Service Contract Reporting

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

3.0 Government Property

The Contractor shall be authorized to requisition Government Furnished Equipment (GFE) items upon approval of AFMC Form 8s. These items shall remain at the Contractor’s facility after contract award (ACA). The Contractor shall maintain an updated GFE listing. The GFE listings, provided in conjunction with the monthly status reports, shall have no more than a total of three late updates and/or omissions per contract year.

11 PR: FD2060-23-30009 PWS REVISION: 0

3.1 Contractor Responsibilities

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;

other applicable Government regulations and as specified in the contract/order. The contractor shall provide secure (Defense Information System Agency (DISA) approved) facility/room for a secure internet connection.

3.2 Government Property/Services to be Provided

Government property will be provided in accordance with the Government Furnished Property (GFP) List. The Contractor shall store and manage GFE and Controlled Cryptographic Items

(CCI) GFE.

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 the OUSD (A&S)/DPC Memorandum, Implementation of the Government Furnished Property Module, the Contractor shall record receipt and shipment of GFP in the GFP Module of the Procurement Integrated Enterprise Environment (PIEE). The Contractor shall also record receipt and disposition of Government property, which falls under the Item Unique Identification (IUID) categories identified in the FAR, in the IUID Registry.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

“Loss of Government property” means unintended loss or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, 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

The Contractor shall report loss of Government property using the GFP Module located in the PIEE, https://piee.eb.mil/. Training on how to utilize the GFP module can be found at https://dodprocurementtoolbox.com.

[CDRL A008, Report, Record of Meeting/Minutes, DI-ADMN-81505]

3.5 Return/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, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for https://piee.eb.mil/ https://dodprocurementtoolbox.com/

12 PR: FD2060-23-30009 PWS REVISION: 0

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 completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

This contract will have a Period of Performance (PoP) of 66 months (12-month base period and four (4) 12-month opting periods) with a (6) six-month priced option to extend services.

4.1.2 Place of Performance

Services for this contract will be performed at Contractor’s facility in addition to field support for CONUS locations per Appx A and OCONUS locations.

4.2 Contract Data Requirements List (CDRLS)

Document Identifier DID Title PWS

Reference(s) A001 B001 C001 D001 E001 F001

TM-86-01R Technical Manual Contract Requirements (TCMR)

4.13 4.13.9 4.15

4.17.3

A002 B002 C002 D002 E002 F002

DI-NDTI-80566A Test Plan 4.13 4.15 4.19

A003 B003 C003 D003 E003 F003

DI-NDTI-80603A Test Procedure 4.10.8 4.13 4.19

A004 B004 C004 D004 E004

DI-NDTI-80809B Test/Inspection Report 4.13 4.15 4.19

13 PR: FD2060-23-30009 PWS REVISION: 0

F004

A005 B005 C005 D005 E005 F005

DI-SESS-81874 Engineering Data for Provisioning

(EDFP) 4.17.4

A006 B006 C006 D006 E006 F006

DI-IPSC-81439A Software Test Description (STD) 4.13 4.15

4.17.4

A007 B007 C007 D007 E007 F007

DI-SESS-81758A/T Logistics Product Data 4.17.4

A008 B008 C008 D008 E008 F008

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.4.2 4.17.1 4.21

4.21.1

A009 B009 C009 D009 E009 F009

DI-MGMT-81804A

Item Unique Identification (IUID) Marking Activity, Validation and

Verification Report

4.3.1.1 4.3.1.3

A010 B010 C010 D010 E010 F010

DI-SAFT-82313 Environmental, Safety and Occupational Health (ESOH) Plan 5.5.1

A012 B012 C012 D012 E012 F012

DI-QCIC-80736 Quality Deficiency Report 4.8.1

A013 B013 DI-IPSC-81435B Software Design Description (SDD) 4.6.3

4.13

14 PR: FD2060-23-30009 PWS REVISION: 0

C013 D013 E013 F013

4.15 4.17.4

A014 B014 C014 D014 E014 F014

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

4.6.3 4.13 4.15 4.19

A015 B015 C015 D015 E015 F015

DI-AVCS-80700A Computer Software Product End Items

4.13 4.15

A016 B016 C016 D016 E016 F016

DI-ISPC-81434A Interface Requirements Specifications (IRS)

4.13 4.15

A017 B017 C017 D017 E017 F017

DI-IPSC-81436A Interface Design Description (IDD) 4.13 4.15

A018 B018 C018 D018 E018 F018

DI-MGMT-80368A Status Report 4.6.1 4.20.4

A019 B019 C019 D019 E019 F019

DI-IPSC-81442A Software Version Description (SVD) 4.6.3 4.13 4.15

A020 B020 C020 D020 E020 F020

DI-MGMT-81948

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

ManagementPlan 4.11.4

15 PR: FD2060-23-30009 PWS REVISION: 0

A021 B021 C021 D021 E021 F021

DI-MISC-80508B Technical Reports – Study/Services

4.7.2 4.13.1 4.14

4.15.3

A022 B022 C022 D022 E022 F022

DI-QCIC-80125B GIDEP Alert/Safe-Alert Report 4.20.6

A023 B023 C023 D023 E023 F023

DI-SESS-80639E Engineering Change Proposal (ECP) 4.6.2 4.7

4.7.3

A024 B024 C024 D024 E024 F024

DI-SESS-81248B Interface Control Document (ICD) 4.13 4.15

A025 B025 C025 D025 E025 F025

DI-SAFT-80101C System Safety Hazard Analysis Report (SSHAR) 5.5.3

A026 B026 C026 D026 E026 F026

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

4.6.2 4.13 4.15 4.17

A027 B027 C027 D027 E027 F027

DI-MGMT-82199 Quality Management System (QMS) Document Library Report 5.9

A028 B028 C028 D028

DI-IPSC-81431A Systems / Subsystem Specification 4.13 4.15

4.17.4

16 PR: FD2060-23-30009 PWS REVISION: 0

E028 F028 A029 B029 C029 D029 E029 F029

DI-IPSC-81440A Software Test Report (STR)

4.6.3 4.13 4.15

4.17.4

A030 B030 C030 D030 E030 F030

DI-SESS-80643E Specification Change Notice (SCN) 4.6.3 4.13 4.15

A031 B031 C031 D031 E031 F031

DI-QCIC-80126B GIDEP Alert Response 4.20.6

4.2.1 Quality of CDRL Deliverable

There shall be no more than a total of two (2) rejection(s) of final deliverables per contract year.

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 defined as a typographical or grammatical error.

The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection in accordance with the associated DD Form 1423 instructions/requirements.

4.2.2 Receipt of CDRL Deliverable

All CDRL deliverables must be submitted via Multi-user ECP Automated Review System (MEARS) unless otherwise noted by the PMO. There shall be no more than one (1) late submission(s) of deliverables per contract year. 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. The Contractor shall electronically deliver all contractual data specified herein using the Government-controlled method of delivery, MEARS. The Contractor shall work with the government to ensure that an adequate number of contractor/subcontractor 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. It will be available to all DOD Common Access Card (CAC) holders or contractor/subcontractor personnel

17 PR: FD2060-23-30009 PWS REVISION: 0

who possess Public Key Infrastructure (PKI) certification from an accepted Government source.

When using DOD SAFE, the Contractor shall submit deliverables directly to the government (such as, current Program/Logistics Manager (PM/LM) and the Multi-Functional Team (MFT) member identified on the CDRL).

MEARS: https://mears1.redstone.army.mil/mears/Default.aspx DOD SAFE: https://safe.apps.mil/

4.3 Repair/Deliverable Management

4.3.1 Item Unique Identification (IUID)

4.3.1.1 Marking Requirement

Item Unique Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

[CDRL A009, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report, DI-MGMT-81804A]

4.3.1.2 Reporting in IUID Registry

Transmission of Government property, which falls under the IUID categories specified in the FAR, must be recorded in the IUID Registry. The Government is required to record the transfer of IUID-designated property to the Contractor. The Contractor is required to record the receipt of IUID-designated property from the Government. The Contractor is required to record the return of IUID-designated property to the Government. The Contractor shall provide an IUID Marking Activity and Verification Report.

4.3.1.3 Life Cycle Event

The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

[CDRL A009, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report, DI-MGMT-81804A]

4.3.2 Packaging, Handling, Storage and Transportation

Military Aircraft (MILAIR) is authorized for shipments if necessary.

The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Commercial Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

https://mears1.redstone.army.mil/mears/Default.aspx https://safe.apps.mil/

18 PR: FD2060-23-30009 PWS REVISION: 0

The Contractor shall package electronic parts susceptible to electrostatic discharge damage in accordance with ANSI/ESD S20.20-2021, ESD Association Standard for the Development of an Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies, and Equipment (Excluding Electrically Initiated Explosive Devices).

In accordance with MIL-STD-2073-1E, Standard Practice for Military Packaging, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.3.3 Counterfeit Electronic Parts

The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory.

4.4 Holiday and Facility Closings

Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as directed by the Government. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.5 Travel

CONUS and OCONUS travel requests for contractor/subcontractor personnel in bulk for approval to the Contracting Officer prior to costs being incurred and a minimum of 10 business days in advance of departure for travel not already identified in the PWS. Receipts must be presented with the invoice for reimbursement of actual travel costs. Contractor/subcontractor personnel may be required to travel to accomplish tasks or training as directed by the Government. The number of trips and personnel traveling shall be limited to the minimum number required to accomplish assigned tasks. Travel by contractor/subcontractor personnel shall be conducted in accordance with FAR 31.205-46, Travel costs, and Joint Travel Regulation

(JTR).

4.6 System Sustainment

4.6.1 Sustainment and Maintenance

The Contractor shall provide internal management and control on all matters related to this PWS, from conception to final completion. A Program Manager (PM) shall be designated to serve as Contractor’s focal point for the Government and will ensure successful fulfillment of all PWS requirements within the agreed upon schedule. The Contractor PM shall report program status monthly in accordance with contract requirements. The report shall include maintenance actions, TSD log, milestone/task status, future plans, contract delivery status, and report preparer as defined in DI-MGMT-80368A. The contractor will recommend the most cost-effective means of repair for each Commercial Off The Shelf (COTS) hardware item consistent with meeting required system performance criteria and availability of technical data and spares.

[CDRL A018, Status Report, DI-MGMT–80368A] shall be submitted

19 PR: FD2060-23-30009 PWS REVISION: 0

4.6.2 Configuration Management

The Contractor shall manage and apply Configuration Management (CM) to hardware, software and documentation developed and delivered under this contract. Changes to the configuration(s) shall be made only when approved by the Program Management Office (PMO). Under Configuration Management the Technical Orders will be updated. The Contractor shall write Technical Orders with no more than 60% USG mark-up on redline review. Examples of such changes are ECPs generated as the result of diminishing sources and preferred spares, and any changes to the software. Records shall be maintained which readily and systematically account for configuration changes from the baseline configuration(s).

[CDRL A023, Engineering Change Proposal (ECP), DI-SESS-80639E] [CDRL A026, Product Engineering Design Data and Associated Lists, DI-SESS-81000F]

4.6.3 JRE Software Sustainment

The Contractor shall update the JRE gateway software as required to ensure interoperability with the latest hardware/software configuration of SADL, Multifunctional Distribution Information System (MIDS), PRC-117, PSC-5, other communication systems interfaced with JRE/JRE- GW/JTEP systems, and 3rd party software developments per direction from the Government. The contractor shall correct identified defects and deficiencies, improve performance or other attributes, or adapt the software to a modified environment. Incorporate new technologies, functionalities, and security upgrades. The contractor will notify the PMO of any software changes and any testing or requirements that may be needed. The contractor will not install the software on operational systems until it has been approved by the PMO and any required tests have been completed and errors that the PMO requires fixed, are corrected.

[CDRL A013, Software Design Description (SDD), DI-IPSC-81435B] [CDRL A014, Software Requirements Specification, DI-IPSC-81433A] [CDRL A019, Software Version Description (SVD), DI-IPSC-81442A] [CDRL A029, Software Test Report (STR), DI-IPSC-81440A] [CDRL A030, Specification Change Notice (SCN), DI-SESS-80643E]

4.7 Engineering Support Services

During the performance of this contract, engineering services and other system support not forecast or specifically defined, may be required, and shall be independently estimated and priced on a case-by-case basis. These activities may include, but are not limited to: System Analysis, Failure Analysis, Diminishing Source Problems, Improved Item Replacement Program (IIRP), Reliability and Maintainability (R&M) Improvements, Data Evaluation Analysis, Software Updates/Corrective Maintenance, Cybersecurity requirements, Engineer Change Proposals (ECPs), Hardware ECPs, Deficiency Reports, and Technical Data Package (TDP).

These requirements may include development of necessary system configuration baseline changes associated with an approved Modification Proposals (AF Form 1067) or Engineer Change Proposal (ECP) from contractor.

[CDRL A023, Engineering Change Proposal (ECP), DI-SESS-80639E]

20 PR: FD2060-23-30009 PWS REVISION: 0

4.7.1 Urgent Operational Needs

Urgent Operational Needs (UON) that are outside the scope of this statement of work shall be accomplished as required. Engineering support will include out of cycle software images, hardware changes, integration, test and verification at the Contractor facility and external facilities as directed by the Government PCO. Written authorization for repair of recoverable items not listed, or engineering services not identified must be initiated by the PMO and authorized by the PCO prior to commencement of required activity.

4.7.2 Engineering Studies

Tasks shall include engineering support to conduct performance perfecting investigations. Study efforts to focus on requirements for system improvements utilizing current and or proposed future system configurations. Reports containing investigation results and performance improvement recommendations will be submitted to the Government at the conclusion of each.

[CDRL A021, Technical Report-Study/Services, DI-MISC-80508B]

4.7.3 Engineering Change Proposal (ECP)

Neither design nor functional capabilities shall be changed, modified, or altered except when an ECP is submitted and approved in accordance with EIA 649. The Contractor shall submit to the PMO any change notice, design change notice, engineering order, engineering change order, engineering change notice, or specification change notice that would affect the configuration of the item. The Contractor shall submit an ECP for all Class 1 changes within 24 hours during the work week and 72 hours during the weekend. The contractor will notify the Government of all Class 2 changes through Document Change Notices (DCN) within 15 calendar days. Any changes made without written approval from the contracting agency shall require removal at the Contractor’s expense. ECPs generated and approved under a formal retrofit program may be implemented under this contract. However, costs associated with implementation shall be funded by the retrofit program.

[CDRL A023, Engineering Change Proposal (ECP), DI-SESS-80639E]

4.8 Deficiency Reports

The Contractor shall provide and maintain a quality assurance program. Material deficiencies and Quality Deficiency Reports (QDRs) shall be handled IAW technical data provided.

4.8.1 Deficiency Reporting, Investigation and Resolution (DRI&R) The DRI&R processes applies to all USAF, Contractor members and organizations that acquire, test, operate, or sustain USAF owned or managed military or weapon systems. The Contractor shall use the Joint Deficiency Reporting System (JDRS, www.JDRS.mil) to report, investigate, and help with deficiency resolution. Additionally, the Contractor may use their own operated and maintained deficiency data systems to augment JDRS capability but may not replace JDRS as the official USAF deficiency repository. The Contractor and program office will adhere to directives outlined in TO 00-35D-54 for proper management of the DRI&R for the system.

[CDRL A012, Quality Deficiency Report, DI-QCIC-80736]

4.9 Onsite Software Sustainment-Field Support

21 PR: FD2060-23-30009 PWS REVISION: 0

CONUS: The Contractor shall provide Contiguous United States (CONUS) Field SME support.

SME support shall include but not be limited to; fielding of JTEP systems, updating of system hardware and software, on-site troubleshooting, and additional operator training. Field support will be divided into three categories; Unscheduled maintenance, Scheduled maintenance, and Full support.

4.9.1 Unscheduled Maintenance

The Contractor shall perform unscheduled maintenance to return the system to fully operational status to minimize downtime. The Contractor shall determine cause of fault/problem within 24 hours after arrival at the site and provide resolution within 48 hours after the determination of cause of the fault/problem. If the Contractor is unable to identify the cause of fault/problem within the 24hr timeline they will contact the PCO/COR/PM prior to the expiration of 24hrs to provide reasoning as to why with an anticipated timeframe to identify the fault/problem. The Contractor shall provide the necessary labor, materials, facilities, and equipment required to analyze, troubleshoot, and repair GW system, assemblies, parts and the GW system software that is maintained or repaired under this contract. These services also include alignment, adjustment, calibration, testing, movement, storage, and reporting status related services to the repair and return of GW to the user. Repair, overhaul, and replacement shall include GW system subassemblies and major assemblies up to and including the complete GW system.

4.9.2 Scheduled Maintenance

The Contractor shall perform scheduled maintenance at the listed sites per Appendix A. The Contractor shall not miss more than one (1) scheduled site visit per contract year without Government approval. Support shall include but not be limited to; installation of cybersecurity patches, preventative maintenance inspections (PMI) per Technical Order (TO) on the electronic equipment, troubleshooting, repair of cables/connectors, and replacement of LRUs/Circuit Cards, bonding straps, fans, and hard and disk drives using GFE spares in accordance with (IAW) PWS paragraph 3 (GFE). NOTE: Any lost or missing equipment identified during a site visit shall be promptly reported to the government program office. The Contractor is not responsible for lost/missing system hardware from sites.

4.9.3 Field Support, Full CONUS/OCONUS SME

The Contractor shall provide CONUS/OCONUS SME support. SME support shall include but not be limited to; installation of cybersecurity patches, fielding of GW systems, updating of system hardware and software, on-site troubleshooting, and additional operator training.

4.9.3.1 CONUS SME

The Contractor shall provide CONUS SMEs in support of operations in Shaw AFB, South Carolina. The Contractor shall provide coverage through the period of performance of this contract and will allow for a 7-day transition period to provide coordination with the incoming SME(s). Shift hours may be flexible due to mission requirements.

The SME will report to the 609 ACOMS commander and work closely with the Joint Interface Control Officer (JICO) as directed by or coordinated with the 609 ACOMS Commander. The SMEs daily duties will be to support the mission at Shaw AFB, SC.

4.9.3.2 OCONUS Deployed SME

22 PR: FD2060-23-30009 PWS REVISION: 0

The Contractor shall provide OCONUS SMEs in support of operations in Southwest Asia. If directed, temporary travel may include “Hostile Fire/Imminent Danger Zone” operations as defined by DoD 7000.14-R Financial Management Regulation Chapter 10. The Contractor shall provide coverage through the period of performance of this contract and will allow for a 7-day transition period to provide coordination with the incoming SME. Shift hours may be flexible due to mission requirements.

The SME will coordinate with the 609 ACOMS Det 1 commander and work closely with the Joint Interface Control Officer (JICO) as required. The SMEs daily duties will be to support the mission at the CAOC. The SME may be required by the 609 ACOMS Det 1 Commander or the JICO with approval of the 609 ACOMS Det 1 Commander to travel to Afghanistan, UAE, Bahrain, Kuwait or other to be determined (TBD) locations.

The Government will work with the Contractor to approve the OCONUS SME information submitted by the Contractor in the Synchronized Pre-deployment and Operational Tracker (SPOT) system 30 calendar days prior to SME deployment as well as approving the SME’s CAC request. The Contractor is responsible to obtain all required vaccines, passports, and visas. The Defense Base Act (DBA) applies.

4.9.3.2.1 Country Regulations

The Contractor shall follow all regulations pertaining to contractors while traveling to countries in support of this effort.

4.9.3.2.2 Employee Processing to Deploy to Qatar or Afghanistan All contractors going to the Central Command (CENTCOM) region (i.e., Qatar, Afghanistan, Kuwait etc.) shall obtain all necessary information pertaining to employee processing.

4.9.3.2.3 Deleted

4.9.3.2.4 Contractor/Command Requirements

The Contractor agrees to incorporate the substance of this clause, including this paragraph, in all subcontracts under this contract.

Contractor Personnel Assignment and Relocation Only Items Indicated In The Order Apply:

• Before traveling overseas, you shall comply with the Foreign Clearance Guide for passport, immunization, and clearance requirements.

• If away from home base in a TDY, PCS, or leave status during an attack, you should proceed as soon as conditions permit to the nearest Air Force Base.

• Immunizations will be accomplished at the earliest possible date before departure from

CONUS.

• Individual will be accorded the same privileges the location provides an Air Force (a) Company Grade Officer regarding bachelor officer’s quarters (BOQ) accommodations, local transportation, messing, and military logistical support. Medical facilities may be furnished as prescribed by local procedures and USAF policies.

Command Approval The Commander of the organization of assignment is responsible for issuing, Uniformed Services Identification and Privileges Card, and DD Form 489, Geneva Conventions Identify Card for civilians who accompany the Armed Forces, according to AFI 36-3026 Volume 1. After the mission has been completed, the cards must be returned to the issuing agency.

4.10 Repair Support Services

The Contractor shall provide the necessary labor, materials, facilities, and equipment required to analyze, troubleshoot, repair, overhaul and test the GW system. These services also include testing, movement, storage, and reporting status related services to the repair and return of the GW system to the users. Contractor shall provide the Government an estimated repair time within 2 business days of receiving that information from the OEM. The contractor will recommend the most cost-effective means of repair for each Commercial Off The Shelf (COTS) hardware item consistent with meeting required system performance criteria and availability of technical data and spares. Repairs should be within 15 days of receiving parts from the OEM.

The contractor will notify the Program Office of any repair taking longer than 15 calendar days.

4.10.1 SAIC 3G Server

The Contractor shall provide the necessary labor, materials, facilities, and equipment required to analyze, troubleshoot, repair, overhaul and test the GW system. These services also include testing, movement, storage, and reporting status related services to the repair and return of the GW system to the users. Turnaround time for repair is 30 calendar days.

4.10.2 Repair, Minor

Minor Component repairs are defined as failures of Line Replaceable Units (LRU) and where the failure does not exceed 25% of the total value of the LRU. May include but not limited to:

power supply, video cards, hard drive, simple circuit card, wire harness. All minor repairs will be bench tested prior to return to service.

4.10.3 Repair, Major

Major Component Repairs are defined as failures of LRUs where required repairs are between more than 25% but not to exceed 75% of the total value of the LRU. May include but not limited to: Single Board Computer, excessive physical damage (which causes internal component damage). All major repairs will complete factory acceptance test prior to return to service.

4.10.4 Standards

The Contractor’s ISO 9001:2015 or equivalent approved repair processes will ensure that all repaired hardware meets the same performance standards as the original units to ensure that form, fit, function, and interchangeability are maintained for the length of the contract.

4.10.5 Parts/Components

Parts/components of an end item determined defective shall be replaced with equivalent serviceable parts. 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 repair of the end item for its intended purposes and shall be completely interchangeable without alterations.

24 PR: FD2060-23-30009 PWS REVISION: 0

4.10.6 Obsolescence

Contractor will notify the government of evolving obsolete part conditions and make recommendations including last time buy opportunities and any redesign that may ensue.

Requests for funding and all related issues will be directed through the PCO. Replacement parts or re-design will be recommended to minimize cost and impact.

4.10.7 Condemnation

Request for condemnation shall only be submitted to the ACO for approval/disapproval if the unit falls into one of the criteria specified below:

• Major/extensive damage of the mechanical and electrical integrity of the unit.

• Overheating and subsequent destruction to a majority of the internal electrical components or electrical connections.

• Damage due to fire, explosion, flood, aircraft crash or enemy combat action.

• Uneconomical to repair. The Contractor shall not repair any items where the cost of parts and labor exceed 75% of the current government stock listed price (from FED LOG) of the item unless authorized through the PCO. When computing the repair cost of the item, any missing recoverable subassemblies shall be included. The PCO will make the final determination as to whether an item is uneconomical to repair. Any item found to be uneconomical to repair shall be reported through the PCO to the JRE/JTEP PMO for disposition instructions.

• Condemned items shall be disposed of and demilitarized in accordance with DoD Publication 4160.28-M “Defense Demilitarization”.

4.10.8 Bench Testing

The Contractor shall perform acceptance testing of each GW system item processed under CLS prior to it being returned to the Government. Acceptance test procedures shall demonstrate that the GW system item to be returned to the Government is in serviceable condition. The Contractor shall furnish all facilities, equipment, and services necessary to perform the acceptance tests and inspections. Prior to returning a serviceable GW system item back to the Government, the Contractor shall notify the government representative as to the results of the acceptance tests and inspections. Any deviations to this requirement to be approved by the PMO.

A signed DDFORM 250 by the Contractor’s quality assurance will evidence final acceptance.

[CDRL A003, Test Procedure, DI-NDTI-80603A]

4.11 Stock, Store, Issue Parts

The Contractor shall provide management of and secure storage space for Government Furnished Equipment (GFE) provided under this contract. GFE items will fall into one of three categories, Consumables (Expendables), Contractor Repair (Non-Expendable) and CCI equipment. The Contractor shall keep this GFE listing current, and a log will be kept and reported in the Monthly Status Report (MSR) for PMO review. Contractor shall ship items as required in support of the contract.

4.11.1 Consumable/Expendable

The Contractor will deliver Consumable/Expendable GFE (including shipping to the site) from the Contractor’s depot to replace failed consumable/Expendable GFE items at NORAD Fixed

25 PR: FD2060-23-30009 PWS REVISION: 0

JTEP locations for those items in support of and included as part of the Fixed NORAD JTEP.

Consumable items will not be returned to the contractor.

Incidental/Consumable material may be required in support of other Government approved systems. The PMO will approve use of and restocking of consumable materials. Vendor shall notify PMO when funds are at 75% of authorization. Use of Return Merchandise Authorization (RMA) is contingent on PMO approval.

4.11.2 Contractor Repairable/Non-Expendable

The Contractor will supply Contractor Repair GFE (including shipping to/from the site) from the Contractor’s depot to replace failed Contractor Repair GFE items at NORAD Fixed JTEP locations. Failed Contractor repair items returned to the Contractor will be processed in accordance with the appropriate repair CLIN for that item. Government will pursue MILSTRIP authority for CCI items.

4.11.3 Handling

Handling of equipment shall be in accordance with AFMC FORM 807. Reusable containers shall be retained, protected, and stored for reuse. The Contractor shall package, handle, store, and transport materials using best commercial practices to ensure effective use of space for packaging, handling, and transportation consistent with transportability on commercial and military aircraft. The Contractor shall provide packaging and preservation methods (i.e., dehumidified, etc.) to protect material against corrosion, physical and mechanical damage, and other forms of degradation.

Contractor shall annotate the applicable receiving document with National Stock Number, Part Number, and Serial Number (DD1348 and DD1149).

Contractor shall use Wide Area Workflow (WAWF) in Procurement Integrated Enterprise Environment (PIEE) to annotate serial number on each invoice, Material Inspection and Receiving Report. Training on how to utilize the GFP module can be found at https://dodprocurementtoolbox.com.

PIEE: https://piee.eb.mil/

4.11.4 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) 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 may be used as a guide in https://dodprocurementtoolbox.com/ https://piee.eb.mil/

26 PR: FD2060-23-30009 PWS REVISION: 0

developing the Obsolescence Management and DMSMS Plan.

GIDEP: www.gidep.org Defense Microelectronics Agency: https://apps.dtic.mil/dtic/tr/fulltext/u2/a518172.pdf

[CDRL A020, Diminishing Manufacturing Sources and…