Pocket_J_PWS_(2_Feb_17).pdf

PERFORMANCE WORK STATEMENT

for

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

COMMUNICATIONS DATA LINK SYSTEM (POCKET J REMOTE ELEMENT (RE))

FD2060-14-30523

14 May 2015, Rev 18 Dec 2015 Rev 31 Aug 2016 Rev 2 Feb 2017

DISTRIBUTION STATEMENT D: - Distribution authorized to the Department of Defense and DoD Contractors only:

Administrative or Operational Use, 12 January 2010. Other requests shall be referred to AFLCMC/WNYEDA, 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-14-30523 PWS REVISION: 0 2

REVISION HISTORY

PCOL

Number/Date

History of Changes

Revision

Comments

Original N/A

18 Dec 2015

Mod para 4.0, 4.2.4, 4.3.1, 4.4, 4.6.1, 4.7, 4.14, 4.17.1, 4.17.3, 6.2.1, 6.2.5, 8.1.1, Appendix H Acronym List, Table of Contents

General Work Requirements language now falls under Technical Requirements; General Work Requirements section deleted/reserved; Quality section to replace Subject Matter Expert; Subject Matter Expert language added under Repair Services; Consumable/Expendable language updated; Scheduled Maintenance to occur every 6- months; Provisioning references added; General Inspections section updated;

TAT section deleted; RMF references updated; Required Block Cycle Upgrade language updated; Appendix H Acronym List and Table of Contents updated

31 Aug 2016

-Moved verbiage from para 4.6.1 to 4.4 for clarity -Reworded title 4.17.2 -Mod para 6 -Add Tech Refresh to title para 8.1

Updated language from Information Assurance to Cyber Security reflecting Risk Management Framework (RMF) requirement for ATO process

2 Feb 2017 - Added para 4.2.1, 4.3.2, 4.3.2.3, 4.3.2.4, 4.17, 12.0, 13.0

- Combined para 4.2.2 w/4.3.2.1, 4.17 w/ 4.32

- Deleted para 1.2, 4.14, 4.25, 7.13, and 4.2.3 from Description of Services, 4.9, 4.12, 4.14, 10.1, 10.2, 10.3, 10.4

- Mod para 4.0, 4.2, 4.2.4.2, 4.3, 4.3.2.1, 4.5, 4.6.1, 4.7, 4.8, 4.11, 4.14, 8.1.1, 8.1.8.1 Moved para 5 to para

3 Deleted sections from the Description of Services that were duplicates; Moved Tech Requirements to GFE; Deleted duplications in Program Management; Added Meeting Support; Moved Tasks and Level of Repair to Contractor Repair; Modified GFE;

Modified Over and Above; Moved Inspections under Program Management;

Consolidated Packaging to one section;

Modified Block Cycle Changes; Modified Software Updates; Moved Software Requirements to Software Updates; Add Lang for Comprehensive Transition Plan;

Added CDRLs

PR: FD2060-14-30523 PWS REVISION: 0 3

TABLE of CONTENTS

Para Name

1.0 Description of Services

2.0 Services Summary

3.0 Government Property and Services

3.1 Contractor Responsibility

3.2 Government Property-Provided

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

3.3.2 Reporting Loss of Government Property

3.4 Return of Government Property

3.5 Government System(s)

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

4.2.1 Meeting Support

4.2.2 Diminishing Manufacturing Sources and Material Shortages

4.2.3 Quality

4.2.4 Configuration Management

4.2.5 Transition Plan, Phase In

4.2.6 Transition Plan, Phase Out

4.3 Government Furnished Equipment Management

4.3.1 Contractor Furnished Material

4.4 Maintenance Support

4.4.1 Help Desk

4.4.2 Unscheduled Maintenance

4.4.3 Scheduled Maintenance

4.5 Repair

4.5.1 LRU Repair, Minor

4.5.2 LRU Repair, Major

4.5.3 Beyond Economical Repair

4.5.4 MILSTRIP Repair

4.5.5 Hardware Repair Services

4.5.5.1 Counterfeit Electronic Parts

4.5.5.2 Parts Approval Request

PR: FD2060-14-30523 PWS REVISION: 0 4

4.5.5.3 Provisioning

4.5.5.4 Final Acceptance Testing

4.6 Over and Above

4.6.1 Maintenance

4.6.2 Repair

4.7 Travel

4.8 Technical Data

4.9 Provisioning

4.10 Deficiency Reports

4.10.1 Deficiency Reporting, Investigation, and Resolution

4.11 Demilitarization

5.0 RESERVED

6.0 Cybersecurity

6.1 ATT/ATO/ATO w/conditions, ATC/ATC w/conditions

6.2 Contractor Responsibilities

6.3 Cybersecurity Scans

6.4 Urgently Required (Out of Cycle) Cybersecurity Fixes

7.0 Data

7.1 Control Data Requirement & Mandatory Regulations

7.1.1 Status Reports

7.1.2 Parts Approval Request

7.1.3 Engineering Change Proposal

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 Support

8.1.8 Software Maintenance and Updates

8.1.8.1 Computer Software Configuration Items

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 of the Technical Data Package

PR: FD2060-14-30523 PWS REVISION: 0 5

8.1.10.3 Relationship of Contractor with Subcontractors/Vendors

8.1.10.4 Engineering Data Updates & Revisions

8.1.11 Test

8.1.12 Test Working Group Meetings

8.1.13 Test Readiness Reviews

8.1.14 Retest and Regression Testing

8.1.15 Developmental Testing & Evaluation

8.1.16 Air Force System Interoperability Test

8.1.17 Operational Testing

9.0 User Familiarization Training

10.0 Interoperability Systems Management and Requirements Transformation (i-SMART) and Enhanced i-SMART

11.1 Continuation of Mission-Essential Services During a Crisis

11.1.1 Definition of Continuation of Mission-Essential Services

11.1.2 Designation of Services as Mission-Essential

11.2 Security Requirements

11.2.1 Clearances

11.2.2 Government Security Regulations

11.2.3 Operations Security

11.2.4 Communications Security

11.2.5 Security Clearance

11.2.6 Security Incident or Violation

11.2.7 Security of Contractor System(s)

11.2.8 Access to Government System(s)

11.2.9 Access to Government Facility

11.3 Environmental Management System

11.4 Green Procurement Program

11.5 Safety Requirements

11.5.3 Mishap Notification/Investigation

11.5.4 Safety and Health Plan

11.6 Inspection of Services

11.7 Trafficking in Persons

11.8 Contract Manpower Reporting

11.9 Invoicing/Payment and Receipt/Acceptance

11.10 Packaging

11.11 Item Unique Identification Requirements

11.12 Government Industry Data Exchange Program (GIDEP)

11.12.2 GIDEP Alert/Safe-Alert Reports

PR: FD2060-14-30523 PWS REVISION: 0 6

12.0 Appendices

Appx. A References

Appx. B Site Locations

Appx. C Supporting Documents

Appx. E Hardware Line Replaceable Units

Appx. F Systems & Software Applications

Appx. G Consumable Spares List

Appx. H Acronym List

Appx. J Proposed System Modifications

PR: FD2060-14-30523 PWS REVISION: 0 7

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, Government Furnished Equipment (GFE) management, 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 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.

PR: FD2060-14-30523 PWS REVISION: 0 8

2.0 SERVICES SUMMARY

Performance Objective

PWS

Reference

Performance Threshold

GFE Management

4.3

The Contractor shall maintain an updated GFE listing with, at minimum, 98 percent accuracy.

Help Desk

4.4.1

The Contractor shall provide toll free on call technical assistance for operational questions, system troubleshooting & system problem diagnosis. The Contractor shall respond to 99% of all calls (initial response) within one (1) hour.

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

Unscheduled Maintenance

4.4.2

The Contractor shall perform unscheduled maintenance as needed. The Contractor shall determine cause of fault/problem within 48 hours after arrival at the site and restore system to operational capability within 48 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.

Scheduled

Maintenance

4.4.3

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

Cybersecurity

6.0

When vulnerability is identified or discovered, the Contractor shall notify the Government Program Manager (PM)/Information Systems Security Manager (ISSM) within two (2) hrs. for all occurrences. The Contractor shall provide monthly updates via Monthly Status Reports (MSR).

Status Reports 7.1.1 The Contractor shall provide a data deliverable. 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 submission annually.

PR: FD2060-14-30523 PWS REVISION: 0 9

3.0 GOVERNMENT PROPERTY & SERVICES

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. The FAR and applicable supplements can be accessed at the site below.

http://farsite.hill.af.mil

3.2 Government Property (Provided)

Government property to be provided is included in Attachment 3.

3.3 Loss of Government Property

3.3.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.3.2 Reporting Loss of Government Property

The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.4 Return of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order. 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 upon completion of the contract/order. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL) deliverables become the property of the Government upon receipt.

3.5 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 system account(s) will be closed.

http://www.ecmra.mil/ http://www.acq.osd.mil/dpap/pdi

PR: FD2060-14-30523 PWS REVISION: 0 10

4.0 TECHNICAL REQUIREMENTS

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

The Period of Performance for the ID/IQ contract will be 5-years (one year basic and four 12-month options) 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.

4.2 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 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.2.1 Meeting Support

The Contractor shall conduct, attend, support, and participate in a kick-off (within 30 days of contract award), Initial Program Management Reviews (PMR) (Within 90 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.

DI-ADMN-81373, Presentation Material, CDRL A001 DI-ADMN-81249, -81250B, Conference Minutes, CDRL A002

4.2.2 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 "Program

PR: FD2060-14-30523 PWS REVISION: 0 11

Manager's Handbook - Common Practices to Mitigate the Risk of Obsolescence", published by the Defense Microelectronics Agency (available at www.dmea.osd.mil/pmhandbook_rev_d.pdf) may be used as a guide in developing the Obsolescence Management and DMSMS Plan.

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

4.2.3 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.2.4 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.

DI-MGMT-81875, Configuration Management Plan, CDRL A004

4.2.5 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 with-in 5 days of contract award using best commercial practice 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.2.6 Transition Plan, Phase out

The Contractor shall provide a Phase Out transition Plan 90 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:

http://www.acq.osd.mil/dpap/UID/atta

PR: FD2060-14-30523 PWS REVISION: 0 12

• 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

• Provide system admin passwords to PMO through secure channels

DI-MGMT-81945, Phase-Out Transition Plan, CDRL A025

4.3 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 with, at minimum, 98 percent accuracy and document as part of the monthly status report. Reparable items shall be returned in “A” (serviceable) condition prior to the end of contract.

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

4.3.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.4 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.

4.4.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 99% of calls (initial response) within one hour. Requests for assistance and actions taken shall be logged into a maintenance database and provided to the Program Office in the Monthly Status Report (MSR).

MSR shall provide monthly and annual maintenance totals to include number of help desk calls, trouble

PR: FD2060-14-30523 PWS REVISION: 0 13

tickets, repair action, LRUs, location, and response/repair time.

4.4.2 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 48 hours after arrival at the site. Within an additional 48 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). 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.4.3 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 annually. If a fault/problem is detected during visit, Contractor must diagnose fault/problem within 48 hours and restore system to operational capability within 48 hours after the determination of cause of the fault/problem.

4.5 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 will 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 repair CLIN for that item (minor/major). 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 E 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 E of the contract) will be inspected and analyzed for the repair function that will comply with the specifications

PR: FD2060-14-30523 PWS REVISION: 0 14

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.

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

4.5.1 LRU 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.5.2 LRU 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.5.3 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.5.4 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 E. Failed items will be shipped back to the supply system. Access to MILSTRIP will be provided by Pocket J PMO.

4.5.5 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 Disposition.

4.5.6 Parts Approval Request

Nonstandard parts that are used in any repair must be approved by AFLCMC/WNYBBC via submittal of DI-MISC-80071E, Parts Approval Request, CDRL A006

4.5.7 Final Inspection

The Contractor shall inspect each completed item for compliance with the work specification.

Failure of the product to meet applicable standards shall be cause for rejection and rework.

4.5.8 Final Acceptance Testing

PR: FD2060-14-30523 PWS REVISION: 0 15

Final acceptance test procedures shall demonstrate that the Pocket J LRU is in serviceable condition when returned to stock. The Contractor shall furnish all facilities, equipment and services necessary to perform the acceptance tests and inspections.

DI-QCIC-80553A, Acceptance Test Plan, CDRL A007

4.6 Over and Above

Any over and above will require written authorization from the PCO and will require issuance of a new task order.

4.6.1 Over and Above Maintenance

These services could include but are not limited to: exceeding allotment of expected unscheduled maintenance, conducting site surveys, and relocation services to conduct intrabase or interbase Pocket J system moves. Contractor will notify PCO/PMO, via MSR, of the percentage of unscheduled use.

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

4.6.2 Over and Above Repair

Written authorization for repair of recoverable items not listed in Attachment 3 must be received from AFLCMC/WNYBBC through the PCO prior to commencement of required activity.

4.7 Travel

For regular travel (i.e., scheduled maintenance), Contractor personnel shall submit monthly site maintenance requests for approval to the PCO prior to costs being incurred. Any additional travel outside approved monthly site requests must be approved by the PCO prior to costs being incurred. For emergency travel (i.e., unscheduled maintenance for Priority 1 sites per Appx B), Contractor personnel can proceed to travel to conduct maintenance, but must contact the PCO the following business day for approval. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46 and Joint Travel Regulation (JTR), Travel Costs. Unscheduled maintenance for Priority 2 & 3 sites shall be approved by PCO prior to travel. Contractor shall procure transportation to remote and fixed sites and bill travel expenses to the appropriate line item.

4.8 Technical Data

The Contractor shall develop and deliver to the Government a Maintenance Technical Manual for both Fixed and Remote sites, System Administration Manual for both Fixed and Remote sites, Work Unit Code Manual for both Fixed and Remote sites, TO changes, and TO Supplements in accordance with Technical manual Contract Requirement (TMCR); Engineering Drawings/Data in accordance with following CDRLs:

TM-86-01P, Technical Manual Contract Requirement (TMCR), CDRL A008 DI-SESS-81000E, Product Drawings/Models and Associated Lists, CDRL A009

4.9 Provisioning

Contractor shall complete provisioning of system. Documents being submitted for Provisioning must be in accordance with the D220 data system. The following Data Item Descriptions (DIDs) apply:

DI-ALSS-81529 Provisioning Technical Documentation (PTD) Specific PTD to be submitted:

- Provisioning Parts List (PPL)

- Common and Bulk Items List (CBIL)

- Short Form Provisioning Parts List (SFPPL)

- Design Change Notices (DCNs)

PR: FD2060-14-30523 PWS REVISION: 0 16

- Spares Acquisition Integrated with Production (SAIP)

- Long Lead Items List (LLIL)

- Statement of Prior Submission (SPS)

DI-ALSS-81557 Supplemental Data For Provisioning (SDFP).

DI-ALSS-81530 SE Recommendation Data (SERD) – Standard/Modified Hand Tools List Specific Summaries to be delivered:

- Support Equipment Recommendation Data (SERD)

- Standard Modified Hand Tools List

For Provisioning (SDFP), and Logistics Management Information (LMI) Summaries DI-SESS-81758A, -81874, -81759A, Provisioning, CDRL A010

4.10 Deficiency Reports

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

4.10.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 (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 shall provide initial responses within five (5) calendar days. The Contractor will adhere to directives outlined in TO 00-35D-54 for proper management of the DRI&R for the Pocket J System.

4.11 Demilitarization

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

5.0 RESERVED

6.0 CYBERSECURITY

6.1 ATT/ATO/ATO w/conditions, ATC/ATC w/conditions

The Contractor shall support the Pocket J Information Systems Security Manager (ISSM) in completion of the Risk Management Framework (RMF) process for Pocket J in preparation for obtaining an Authority to Test (ATT), Authority to Operate (ATO) and Authority to Connect (ATC) from the Authorizing Official (AO). In the event the AO grants an ATO with conditions or ATC with conditions the Contractor shall support the Government ISSM on Plan of Actions and Milestone items until the ATO/ATC is granted. This involves providing system documentation and artifacts for input into the Authorization package.

6.2 Contractor Responsibilities

The Contractor shall support the RMF process t o i nc lude providing input and updates to the System Security Plan (SSP) including;

1) Security Concept of Operations

PR: FD2060-14-30523 PWS REVISION: 0 17

2) Continuity of Operations Plan (COOP), Disaster Recovery Plan (DRP), and Contingency Plan

3) Incident Response Plan

4) Hardware listing (baseline)

5) Software listing (baseline)

6) Ports and Protocol Services Matrix

7) Cybersecurity Training Plan

8) Vulnerability Management Plan to be updated periodically as required by the latest Cybersecurity guidance

9) Contractor In-Plant Cybersecurity assessment report from Cybersecurity self-assessments.

6.2.1 The Contractor shall implement Cybersecurity controls as identified by the PMO’s initial control baseline derived from the Categorization performed in accordance with DoDI 8510.01, Risk Management Framework for DoD Information Technology and Committee for National Security Systems (CNSS) 1253 and the RMF Knowledge Service, as well as specific controls identified by Attachment 5 of Appendix F of CNSS 1253, Classified Information Overlay.

6.2.2 The Contractor shall document and provide the Government with all test, scans, and code analysis results

6.2.3 The Contractor shall analyze all latent defects and attribute vulnerability categorization codes (e.g. CAT I, CAT II, CAT III).

6.2.4 The Contractor shall analyze and test all software source code included in the system via static analysis tools that are consistent with the DISA STIGs at an interval determined by the Government.

6.2.5 With the Government’s approval, Contractor shall fix findings in accordance with Government priorities and schedule. The Contractor must provide software free from all CAT I risks and satisfactorily mitigate all CAT II findings to achieve and maintain the ATO. (Ref. DoD 8510.01, RMF)

6.2.6 The Contractor shall obtain Government approval for the inclusion of all third party software (e.g., open-source, freeware, mobile code, source code or binaries) proposed for use on Pocket J prior to its use or integration. All software must meet the requirements defined in the current DISA Application Security and Development Security STIG.

6.2.7 The Contractor will assist the IAM with Security Content Automation Protocol Compliance Checker (SCC) scans against the baseline Pocket J configurations and apply patches/updates as required and approved by the Government.

PR: FD2060-14-30523 PWS REVISION: 0 18

6.2.8 The Contractor shall “lock down” and test the different variants of Pocket J system with the Assured Compliance Assessment Solution (ACAS) and the latest applicable DISA STIGs, SRRs (to include SCC), and applicable Security Checklists on base-lined software and hardware. All deviations to settings which become findings shall be documented and submitted to the Government.

Documentation shall include rationale for the findings as well as, a mitigation plan. The mitigation plan becomes part of the plan of action and milestones.

6.2.9 The Contractor shall include Cybersecurity as a part of all PMRs.

6.2.10 The contractor shall review and analyze information system audit records during scheduled maintenance periods for indications of inappropriate or unusual activity, and report findings to the Government ISSM.

6.3 Cybersecurity Scans

The Contractor shall assist the ISSM with Security SCC scans against the baseline Pocket J configurations and apply patches/updates as required by the scan. The images created from these scans will be used on all new systems and all systems returned to the Contractor for repair.

6.3.1 At any time vulnerability is identified or discovered, the Contractor shall notify the Government PM/ISSM via email within two hours of identification for all occurrences.

6.4 Urgently Required (Out of Cycle) Cybersecurity Fixes

The Contractor shall evaluate all IAVAs for applicability to Pocket J. The Contractor shall recommend to the Government Program Office a course of action and cost estimate, based on urgency of the problem, availability of a fix, maintaining configuration control, and authorized level of corrective action. Based on the SPO’s direction, the Contractor shall implement an out- of cycle corrective action and report compliance to the IAM.

7.0 DATA

7.1 Control Data Requirement and Mandatory Regulations

Data - Reports IAW DD 1423s and mandatory regulations as cited below:

7.1.1 Status Reports

For the term(s) of the exercised basic contract and options(s), the Contractor shall maintain a history of repair data for non-warranty Pocket J hardware. The Contractor shall use the monthly status reports to propose updates and changes, document slippages to the deliverables schedule, and provide Teardown Test & Evaluation (TT&E) on LRUs (including estimates for repairs for LRUs in repair cycle and breakdown of costs associated with LRUs that have been repaired). The Contractor shall provide the number of calls for technical assistance with resolution reports, software, equipment and licensing issues, and information requests to the Government as part of the monthly status report to include annual totals. The content and 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

PR: FD2060-14-30523 PWS REVISION: 0 19

submission annually. The Government acceptance of the monthly status reports does not indicate concurrence with the content or proposed changes to schedule(s).

7.1.2 Engineering Change Proposal (ECP)

The Contractor will submit Class 1 ECP, as required, for all changes to the baseline configurations within 24 hours during the work week and 72 hours during the weekend. The ECPs submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes. The Contractor shall notify the Government of all Class 2 changes, as required, including all substitute parts changes, through Document Change Notices (DCN), within 15 calendar days.

DI-SESS-80639D, Engineering Change Proposal, CDRL A014

8.0 BLOCK CYCLE UPGRADE / TECH REFRESH WORK REQUIREMENTS

8.1 Block Cycle Upgrade / Tech Refresh Requirements

Block cycle upgrades will incorporate the most current MIL-STDs (6016 and 3011), Windows Operating System and Security Controls. As part of a Block Upgrades the Contractor shall provide technical support, software and hardware maintenance/upgrades to sustain Pocket J. If the Contractor determines there are requirements for block upgrades that are not covered in this paragraph, they will provide a list to the CO/program manager with a detail cost breakdown to be negotiated in accordance with the terms of the contract. The Contractor shall execute structured software engineering and program management processes that facilitate effective and high-quality software development. The Contractor shall ensure that all changes, upgrades, and enhancements to baseline versions of the Pocket J software are in compliance with the approved System Requirements Document (SRD) within 60 calendar days. The Contractor shall comply with the following:

DI-SESS-81758A, -81874, -81759A, Provisioning, (CDRL A010) DI-IPSC-81427A, Software Development Plan, (CDRL A015) DI-IPSC-81442A, Software Version Description, (CDRL A016) DI-IPSC-81435A, Software Design Description, (CDRL A017) DI-CMAN-81248B, Interface Control Document, (CDRL A018) TM-86-01P, Technical Manual/Technical Order Updates, (CDRL A008) DI-SESS-81000E, Product Drawings/Models and Associated Lists, (CDRL A009) DI-ADMN-81250B, Reports/Records of Meetings/Minutes, (CDRL A002) DI-IPSC-81433A, Software Requirements Specification (SRS), (CDRL A019) DI-IPSC-81434A, Interface Requirements Specification (IRS), (CDRL A020) DI-CMAN-80643D, Specification Change Notice, (CDRL A021) DI-IPSC-81432A, System/Subsystem Design Description (SSDD), (CDRL A022) DI-IPSC-81436A, Interface Design Descriptions (IDDs), (CDRL A023) DI-MGMT-80803, Item Unique Identification Marking Plan, (CDRL A024)

8.1.1 Required Block Cycle Change

Upon receipt of an approved block cycle change request from user (an approved AF Form 1067, Modification Proposal) or ECP from Contractor, the program office will submit a request for quote through Contracting Officer to Contractor through a contract modification. The Contractor shall plan, manage and direct the BCU through an Integrated Management Plan per this PWS. There shall be no deviations from the Integrated Management Plan (IMP) without prior Government concurrence.

The Contractor shall provide identification of all work to be accomplished, the Integrated Master

PR: FD2060-14-30523 PWS REVISION: 0 20

Schedule (IMS) for this work, and the functional organization charged with the responsibility for performance of the work.

8.1.2 Change Requests

Other than those listed in this para, the Contractor shall provide block cycle upgrades or changes to the Pocket J system under separate authorized modifications to the contract IAW paragraph 8.1.

The block cycle upgrade will consist of ONLY Government approved Change Requests (CRs).

During the block cycle time period, appropriate testing shall be performed.

Current proposed upgrades are:

A) Modify Pocket J FE Dashboard B) Enable Windows Remote C) Add workstation to Pocket FEs D) Remove PRC-117 from Pocket J REs E) Complete Pocket J Tactical Data Link Wide Area network (TDL WAN) communication path F) Upgrade Pocket J from Windows XP to latest AF accepted OS, integrate latest TDL s/w G) Change security banner on JRE H) Add system audit / audit reduction capability

(See Appx J for details)

8.1.3 Acceptance Criteria

The Contractor shall ensure that all Contractor-delivered products meet the following criteria for Government acceptance of software maintenance/upgrades:

A) Successful conduct of Developmental Test (DT)/ Air Force System Interoperability Test (AFSIT)/ Operational Test (OT) to include Force Development Evaluation (FDE), Operational Utility Evaluation (OUE), Joint Interoperability Test (JIT)/ Regression Test. The Contractor has no control over the Government test schedule and will not be responsible for any time delays associated with the scheduling. This test time will not be included in the Contractor’s block cycle schedule.

B) No priority 1, 2A, or 2B (as defined by IEEE/EIA 12207.2 Annex J) problem reports open as specified per delivery order.

C) Government approval of the deliverables, to include documentation required for each block cycle.

Additional specific acceptance criteria may be established on a per block cycle basis.

The Government will determine when these criteria have been met and document this determination in the Government Independent Assessment Report.

8.1.4 Technical Support

The Contractor shall provide technical support for problem report/change request investigation and change proposal development, test environment support, and Independent Validation and Verification (IV&V) support. In addition, the Contractor may be tasked to monitor technology as it progresses and make recommendations to the Government for inclusion in the current baseline version of the software application. Recommendations shall include performance, schedule, and cost components.

8.1.5 Problem Report/Change Request Investigation

The Contractor shall investigate problem reports and change requests. The Contractor shall develop subsequent recommendations for change proposals. Recommendations shall include performance, schedule, and cost components.

PR: FD2060-14-30523 PWS REVISION: 0 21

8.1.6 Test Environment Support

The Contractor shall provide and maintain a test environment capable of testing former and current software configurations. The Contractor shall document and control the configuration of each test environment the Contractor utilizes, to include but not be limited to all elements of equipment, software, and human or automated processes present in each test environment. The Contractor shall establish and maintain a factory test bed/development environment for support and developmental testing of the Pocket J systems. The test bed will be capable of supporting a wide range of efforts including Factory Acceptance Testing, factory training in Pocket J operation and maintenance, software security scans and accreditation, and formal test program support (i.e., supporting Air Force System Interoperability Testing, Joint Interoperability Testing, and Operational Testing as directed by the SPO). The Government will provide resources (appropriate GFE) to ensure that the factory test bed is fully capable of interoperating with other Government and contactor test organizations. The support equipment includes non-prime system equipment necessary to support the operation of the Gateway such as cryptographic equipment, modem, etc.

8.1.7 Independent Validation and Verification (IV&V) Support

The Contractor shall provide technical expertise on the Pocket J software for Government IV&V of the Pocket J systems.

8.1.8 Software Maintenance and Updates

The Contractor shall make corrective changes, improvements, or upgrades to the software on a block cycle basis as directed by the Government in order to:

1) Correct defects and deficiencies identified through ECP and JDRS to be verified through Contractor test bed.

2) Improve performance, combat obsolescence, or adapt the software to a modified environment.

3) Incorporate new technologies, functionalities, interoperability, and/or security upgrades.

4) Ensure interoperability with the latest hardware/software configuration of items listed in Appx F of this PWS and other communication systems interfacing with the Pocket J systems.

5) Install…