Attachment_3_-_Performance_Work_Statement_(PWS).pdf

PR: FD2060-18-34116

Distribution Statement: D

Performance Work Statement for

LINK-16 ALASKA (LAK) AN/FSQ-228

Communications Control Set

Purchase Request: FD2060-18-34116

06 March 2019

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD

Contractors only. Other requests shall be referred to AFLCMC/WNY.

Table of Contents

1.0 Decription of Services……

1.1 Objectives……

1.2 Benefit to United States Air Force (USAF)

1.3 Background………

2.0 Services Summary……

3.0 Government Property……

3.1 Contractor Responsibility

3.1.1 Government Property Storage Requirements

3.2 Government Property to be Provided

3.2.1 Base Support

3.2.2 Reporting of Government Property

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 Place of Performance

4.1.1 Contract/Order Period of Performance

4.2 Maintenance Support Concept

4.2.1 SME Help Desk Support

4.2.2 Unscheduled Maintenance

4.3 Contract Data Requirements List(s) (CDRL)

4.3.1 Quality of CDRL Deliverable

4.3.2 Reciept of CDRL Deliverable

4.4 Engineering Services

4.4.1 Software Analysis

4.4.1.1 Software Changes and Corrective Patches

4.4.2 Item Unique Identifications

4.4.2.1 Marking Requirement

4.4.2.2 Reporting in IUID Registry

4.4.3 Packaging

4.5 Holidays and Facility Closings

4.6 Travel

4.7 Hardware, Inspections and Repair

4.7.1 General Inspections

4.7.2 Hardware Repair and Cleaning

4.7.3 Turn Around Time (TAT)

4.7.4 Tasks

4.7.5 Acceptance Test

4.7.6 Level of Repair

4.8 Program Management

4.8.1 Diminishing Manufacturing Sources and Material Shortages……………...16

4.8.2 Configuration Management

4.8.3 Deficiency Reports

4.8.3.1 Deficiency Reporting, Investigation, and Resolution………………...17

4.8.4 Transition Plan, Phase In

4.8.4.1 Transition Plan, Phase Out

4.9 Cybersecurity

4.9.1 LAK ATO, ATO w/ Conditions, ATC

4.9.2 Cybersecurity Scans

4.9.3 Urgently Required (Out of Cycle) Cybersecurity Fixes…………………….20

4.10 Block Cycle Upgrade Work Requirements………………………………………….20

4.10.1 Block Upgrade Requirements………………………………………………...20

4.10.1.1 Change Requests………………………………………………21

4.10.1.2 Acceptance Criteria…………………………………………...21

4.10.1.3 Problem Report/Change Request Investigation…………….22

4.10.1.4 Test Environment Support…………………………………...22

4.10.1.5 Independent Validation and Verifications Support………...22

4.10.1.6 Software Maintenance and Update…………………………..22

4.10.1.7 Testing, Approval and Deficiency Report…………………...22

4.10.1.8 Software Release……………………...……

4.10.1.9 Testing and Approval

4.10.1.10 Documentation/TR Fixes

4.10.1.11 Technical Data

4.10.1.11.1 Library

4.10.1.11.2 Engineering Data

4.10.1.11.3 In-Process Review (IPR) of the TDP

4.10.1.11.4 Engineering Data Updates and Revisions………………24

4.10.1.12 Test

4.10.1.13 Support Test Working Group (TWG) Meetings……………25

4.10.1.14 Support Test Readiness Reviews (TRR)………

4.10.1.15 Retest & Regression Testing………

4.10.1.16 Developmental Test (DT)………

4.10.1.17 Air Force System Interoperability Test (AFSIT)…………...25

4.10.1.18 Operational Testing………

4.10.1.19 Technical Support………

4.11 User Familiarization Training System Administration Training…………………26

5.0 General Information……

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Designation of Services as Mission-Essential

5.2 Security Requirements

5.2.1 Security Regulations

5.2.2 Operations Security (OPSEC)

5.2.3 Communications Security (COMSEC)

5.2.4 Security Clearance

5.2.5 Security Incident or Violation

5.2.6 Security of Contractor System(s)

5.2.7 Access to Government System(s)

5.2.8 Access to Government Facility or Military Installation

5.2.9 Identification (ID) Card/Badge

5.2.10 Common Access Card (CAC)

5.3 Environmental Management System (EMS)

5.4 Agency Affirmative Procurement Programs

5.5 Safety Requirements

5.5.1 Contractor Compliance

5.5.2 Mishap Notification/Investigation

5.5.3 Safety and Health Plan/Program

5.5.4 Voluntary Protection Program (VPP)

5.6 Inspection of Services

5.7 Contractor Manpower Reporting

5.8 Invoicing/Payment and Receipt/Acceptance

5.9 Trafficking in Persons

6.0 Documentation……

6.1 Control Data Requirement And Mandatory Regulations

6.1.1 Status Reports

6.1.2 Parts Approval Request

6.1.3 Engineering Change Proposal (ECP)

6.1.4 GIDEP Alert/Safe-Alert Reports

7.0 Production of Future LAK Sites……

8.0 Appendices……

8.1 Appendix A, References

8.2 Appendix B, LAK Systems and Software Applications

8.3 Appendix C, Supporting Documents

8.4 Appendix D, LAK Hardware Line Replaceable Units (LRUs)

8.5 Appendix E, Acronym List

9.0 Attachment……

1.0 Description of Services

This Performance-based Work Statement (PWS) defines the services required to support Link-

16 Alaska (LAK) which contributes to the security of the United States through the use of the secure, digital, jam-resistant Link-16 network that takes the radar air picture and promulgates it to fighter aircraft allowing them to see the full scope of enemy and friendly aircraft in its vicinity over the austere Alaskan air space. This infrastructure is hosted by the 611th AF Joint Interface Control Cell

(JICC) and supports Alaskan North American Aerospace Defense Command (NORAD) Region

(ANR), Alaskan Command (ALCOM), and Joint Task Force (JTF)-AK command and control (C2) of air sovereignty, air defense, and homeland defense missions. LAK uses sixteen Line of Sight (LOS)

Multifunctional Information Distribution System Low Volume Terminals (MIDS LVT)-1/4, using ultra high frequency (UHF) radio frequency (RF) waveform, to provide the coverage necessary for the

Area of Responsibility (AOR). LAK is unique in its ability to remotely key the crypto for the MIDS

(Link-16) radio terminals to ensure message security. Work performed under this PWS includes actions necessary to repair components to fully operational status and to maintain the system to ensure interoperability with all internal components and external agencies that comply with MIL-STD 6016F.

The Contractor shall provide program management, engineering services, hardware repair, software repair, software upgrades (patches), Cybersecurity support, Technical Orders and technical documents support, systems and software engineering, Help Desk support, scheduled and unscheduled maintenance, installation of future LAK sites, training, technical assistance, test and development as part of tech refresh/Block Upgrade, and documentation to support LAK and the Cybersecurity certification and accreditation (C&A) of LAK which includes the AN/FSQ-228, Communications

Control Set. 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. Functional capabilities shall not be changed, modified, or altered except when an Engineering Change Proposal (ECP) has been submitted by the Contractor and approved by the Government. The Contractor shall repair items to serviceable condition t o t h e l a t e s t h a r d w a r e /software c o n f i g u r a t i o n approved and funded by the government for that item to ensure compliance with 6016F, as applicable. Appendix D lists authorized repairable hardware under this PWS.

1.1 Objective(s):

This Performance Work Statement (PWS) describes the services required for successful system maintenance for these sixteen (16) sites (Communications Control Set at Joint Base Elmendorf-

Richardson (JBER), AK and 15 remote sites in Alaska (Murphy Dome, Sparrevohn, Middleton Island, Point Barrow, Cape Romanzof, Cold Bay, Cape Lisburne, Barter Island, Tin City, Indian Mountain, Cape Newenham, Oliktok, Tatalina, Kotzebue, and Valdez). This PWS will also cover any future LAK

GEP sites added to the current baseline. These services include Government required LAK system maintenance.

1.2 Benefit to United States Air Force (USAF):

This acquisition will benefit the United States Air Force (USAF) by implementing future version and system upgrades in LAK to support Cybersecurity Requirements.

1.3 Background:

Alaskan North American Aerospace Defense Command (NORAD) Region (ANR) and Alaskan

Command (ALCOM) require Link-16 capabilities to comply with Joint and Service directives, and to effectively command and control assigned forces during Joint and Combined operations. The LAK program was initiated out of the necessity to modernize the communications and Command and Control

(C2) system for operational and tactical level C2 agencies in Alaska. One Air Force program, LAK, implemented a multi-phase process to integrate Link-16 capabilities and equipment into the Alaskan

Joint Operations Area.

2.0 Services Summary

PERFORMANCE

OBJECTIVE

PWS

REFERENCE

PERFORMANCE THRESHOLD

Help Desk 4.2.1 The prime Contractor shall provide Subject Matter Expert (SME) support for all Help Desk calls. The prime Contractor shall respond to 99% of calls (initial response) within 24 hours.

The contactor shall provide a resolution within 2 calendar days. 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 tickets, repair actions, LRUs, location, and response/repair time.

Unscheduled Maintenance

4.2.2 The prime Contractor shall provide unscheduled

maintenance support for all LAK sites. The prime Contractor shall arrive to LAK site(s) within 48 hours.

Within an additional 48 hours, the Contractor shall determine cause of fault/problem and restore that site to full operational capability. It is anticipated that there will be 4 unscheduled maintenance visits annually. If unscheduled maintenance exceeds 4 visits, it will be considered over and above and will be negotiated before issuance of an order.

Hardware Repair and Cleaning

4.7.2

Contractor will e-mail a listing of all items receipt-in for repair to the Program Management Office (PMO) (AFLCMC/WNY) and the Procurement Contracting Officer (PCO) (AFLCMC/WNKE), no later than 2 business days upon arrival of property at Contractor facility.

Maintenance and repair of items

4.7.3 The Contractor will perform final

Acceptance testing of each LAK LRU process under CLS prior to returning it to the Government. The required

Turn Around Time (TAT) is no more than 60 calendar days after determination that item is not over 75% of acquisition Cost making it uneconomical to repair.

Expedited repair and shipment of

Critical items

4.7.3 The Contractor shall respond to the PMO

(AFLCMC/WNY) and the PCO (AFLCMC/WNKE) within one (1) business day upon receipt of critical items or Mission Impaired Capability Awaiting Parts (MICAP) and coordinate the time required to repair the item and/or support sustainment surge or MICAP requirements.

Configuration control of design and Functional capabilities

4.8.2 The Contractor shall maintain updated

Configuration Management (CM) in support of hardware, software, lab, and documentation. A list of all

Configuration changes made to the system both hardware and software shall be submitted to the government within

60 days action notifying the government of same changes to the system.

Cybersecurity 4 . 9 . 3 The Contractor shall notify the Government PMO/Information Systems Security Manager (ISSM) within 24 hours of the vulnerability and a recommended course of action. The Contractor along with the Government shall work together to determine a solution.

The Contractor shall implement the solution within 30 calendar days.

Submission of Engineering Change Proposal

(ECP)

6.1.3 The Contractor shall submit an ECP for

All Class 1 changes to the baseline configurations

(Appendix B). The ECP submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes. The

Contractor shall notify the Government of all proposed

Class 2 changes (including items not in Appendix B), including all substitute parts changes, through Document

Change Notices (DCN) within 15 calendar days of identified need for changes. Government shall concur/non-concur and will provide expected ECP format upon need/request.

3.0 Government Property

3.1 Contractor Responsibility:

The Contractor shall be responsible for Government property in their 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.1.1 Government Property Storage Requirements

Based on similar efforts, the Government recommended storage requirement for all GFE is approximately 400 square feet, and it must meet DoD requirements based on classification of the equipment.

3.2 Government Property to be Provided:

Government property is authorized in accordance to GFE listing attached to the contract and in

Procurement Integrated Enterprise Environment (PIEE).

3.2.1 Base Support:

The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment, and office supplies.

3.2.2 Reporting of Government Property:

The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government-Furnished Property (GFP) in the Item Unique Identification (IUID) Registry. Government property shall be listed as a GFP attachment and is created as a fillable document at http://dodprocurementtoolbox.com/.

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 notify the PMO (AFLCMC/WNY) within 48 hours of identification of missing

GFE/GFP. The Contractor shall also use the Defense Contract Management Agency (DCMA) eTools software application within 48 hours 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/

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 Procuring Contracting

Officer (PCO) (AFLCMC/WNKE). All material generated under the contract/order becomes the http://farsite.hill.af.mil/ http://dodprocurementtoolbox.com/ http://www.dcma.mil/aboutetools/ property of the Government and shall be returned to the Government upon completion of the contract/order. All Departments of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), and 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.

4.0 Technical Requirements

4.1 Place of Performance:

These services shall be performed at the Contractor’s facility and military installations, if necessary.

4.1.1 Contract/Order Period of Performance:

The period of performance for the contract/order will extend 13 Mar 2020 – 13 Sep 2025.

IDIQ Contract: Basic one year plus four one year options, with a -8 option to extend services up to six months.

4.2 Maintenance Support Concept:

The LAK maintenance concept consists of Equipment Maintenance Contractor (ARCTEC) to provide scheduled (conduct preventive maintenance inspections and apply cybersecurity patches every 6 months) and unscheduled maintenance (troubleshooting, removal & replacement of hardware).

The Contractor Logistics Support (CLS) Contractor is required to perform maintenance support tasks;

unscheduled maintenance and Help Desk support.

4.2.1 SME Help Desk Support:

The CLS Contractor shall provide toll free on call Subject Matter Expert (SME) support and technical assistance for operational questions, system troubleshooting, and system problem diagnosis. The CLS

Contractor shall respond to 99% of calls (initial response) within 24 hours. The contactor shall provide a resolution within 2 calendar days. 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 the number of help desk calls, trouble tickets, repair actions, LRUs, location, and response/repair time. (DI-MGMT-80368A, Status Reports, CDRL A019)

4.2.2 Unscheduled Maintenance:

Unscheduled maintenance is defined as troubleshooting and repairing the LAK system as needed to restore it to a fully operational condition by the CLS Contractor that is considered out of scope of the

ARCTEC contract. The CLS Contractor shall provide unscheduled maintenance support for all LAK sites. The CLS Contractor shall arrive to LAK site(s) within 48 hours. Within an additional 48 hours, the Contractor shall determine cause of fault/problem and restore that site to full operational capability.

It is anticipated that there will be 4 unscheduled maintenance visits annually. If unscheduled maintenance exceeds 4 visits, it will be considered over and above, and it will be negotiated before the issuance of an order. (DI-MGMT-80368A, Status Reports, CDRL A019)

4.3 Contract Data Requirements List(s) (CDRL):

Document

Identifier

DID Title PWS Reference(s)

A001 DI-MGMT-81804 IUID Marking Activity and Verification Report 4.3.1.2.2

A002 DI-ENVR-81375 Environmental Health and Safety Plan (HSP) 5.5.3

A003 DI-SAFT-81563/T Accident/Incident Report 5.5.2

A004 DI-OCIC-80736 Quality Deficiency Report 4.10.1.7

A005 DI-CMAN-80639C Engineering Change Proposal (ECP) 6.1.3

A006 DI-IPSC-81442 Software Version Description 4.10.1

A007 DI-IPSC-81431A System Requirements Document 4.10.1

A008 DI-CMAN-81248A Interface Control Document (ICD) 4.1.9.7, 4.10.1

A009 DI-MISC-80071E Parts Approval Request 6.1.2

A00A DI-OCIC-80125B

& 80126B

Gov’t Industry Data Exchange Program (GIDEP) 6.1.4, 6.1.4.2

A00B DI-ALSS-81529/T

& 81530

Information (LMI) Data Product(s) 4.10.1

A00C DI-NDTI-80566A Test Plans 4.10.1

A00D DI-NDTI-80603A Test Procedures 4.10.1

A00E DI-NDTI-80809A Test/Inspection Report 4.10.1

A00F DI-ADMN-81805 Report, Record of Meeting Minutes 4.10.1

A00G DI-SESS-81000E/T Product Drawings/Models And Associated Lists 4.4, 4.10.1, 4.10.1.11.2

A00H DI-IPSC-81427A Software Development Plan (SDP) 4.10.1

A00J DI-ADMN-81249A

& 81250A

Conference Agenda and Minutes 4.10.1.11.3

A00K DI-MGMT-80368A Status Reports 4.2.1, 4.2.2, 6.1.1

A00L DI-IPSC-81435A Software Design Description 4.10.1

A00M DI-IPSC-81436A Interface Design Description (IDD) 4.10.1

A00N DI-ALSS-81557 Supplemental Data for Provisioning (SDFP) 4.10.1

A023 DI-MGMT-

80004A

Management Plan 4.8

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

A00Q DI-IPSC-81434A Interface Requirements Specification (IRS) 4.10.1

A00R DI-IPSC-81440A Software Test Report 4.10.1

A00S DI-IPSC-81439A Software Test Description 4.10.1

A00T DI-CMAN-80643C Specification Change Notice 4.10.1

A00U DI-IPSC-81432A System Subsystem Design Description (SSDD) 4.10.1

A00V DI-SESS-81656 Data Item Description, Source Data for Forecasting

Diminishing Manufacturing Sources and Material

Shortages

4.8.1

A00W

A00X

A00Y

TM-86-01N

DI-MGMT-81945

DI-SESS-81875

Technical Manual Contract Requirement (TMCR)

Phase-Out Transition Plan

Configuration Management Plan (CMP)

4.10.1

4.8.4.1

4.8.2.3

4.3.1 Quality of CDRL Deliverable:

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

4.3.2 Receipt of CDRL Deliverable:

CDRL deliverables must be submitted via Procurement Integrated Enterprise Environment (PIEE) e-

Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT). 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.

4.4 Engineering Services:

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

Engineering Services in support of:

System Analysis

Failure Analysis

Diminishing Source Problems

Improved Item Replacement Program (IIRP)

R & M Improvements

Data Evaluation Analysis

Software Updates/Corrective Maintenance (ECPs) Hardware ECPs

Deficiency Reports

Technical Data Package

The Contractor shall produce and deliver a Technical Data Package (TDP) that accurately depicts the final products. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s).

TDP data includes, but is not limited to, A. Operation Handbook (OPH) - (At the 35% and 70% completion point )

B. Mx TO—minimal change (At the 35% and 70% completion point )

C. Sys Admin—Configuration Item changes (At the 35% and 70% completion point )

D. Drawings

E. Capture all new COTS manuals as applicable

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

SESS-81000E/T, Product Drawings/Models And Associated Lists, CDRL A00G)

4.4.1 Software Analysis

The Contractor shall provide software analysis and support. This support includes, but is not limited to performing all the necessary actions to analyze deficiency reports (DRs) assigned in order to determine their validity. This support further includes the analysis required to determine the updates necessary to the Requirements Documentation. Analysis will include recreating the problem to include laboratory analysis and code inspection. This analysis will focus on problem correction as well as resources necessary to correct the DR, once the DR has been validated as an actual problem. For each DR, the

Contractor shall provide a Change Request Report (CRR) that includes: a detailed description of the problem, the software change classification (corrective, adaptive, perfective), the estimated effort required for implementation, the risks associated with implementation, and the cost to implement. The

Contractor shall make changes as required to maintain and/or be corrective in nature to ensure full operational capability of the system software on a block cycle basis as directed by the Government in order to: Correct identified defects and deficiencies, or adapt the software to a modified environment, incorporate new technologies, functionalities, and security changes per Engineering Change Proposals.

4.4.1.1 Software Changes And Corrective Patches:

The Contractor shall be responsible for the development and delivery of software changes generated by hardware/software configuration changes of the items in Appendix B and other components interfacing with the LAK system to ensure interoperability in a “plug and play” type format using CD with auto Play/run/install features, when feasible or applicable. Also applicable for software changes required to correct deficiencies.

4.4.2 Item Unique Identification

4.4.2.1 .Marking Requirement:

In accordance with DFARS 252-211.7003(a), Item Identification and Valuation / Definitions, “DoD unique item identification” means “a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items.” Unique item identification is required for all items that meet the criteria established by DFARS

211.274-2, Policy for unique item identification.

The Contractor shall mark items in accordance with DFARS 211.274-2, DFARS 252-211.7003, and

Military Standard (MIL-STD)-130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property.

4.4.2.2 Reporting in IUID Registry:

4.4.2.2.1 Transmission of Government property must be recorded in the IUID Registry. The

Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.4.2.2.2 The Government 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 – non-Government, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry. (DI-MGMT-81804, IUID Marking Activity and Verification Report, CDRL

A001)

4.4.3 Packaging:

The Contractor shall package and mark end items and components in accordance with the contract

(basic or order, as applicable) Air Force Materiel Command (AFMC) Form 158, Packaging

Requirements; MIL-STD-129R, Department of Defense Standard Practice / Military Marking for

Shipment and Storage; MIL-STD-130N; and MIL-STD-2073-1D, Standard Practice for Military

Packaging. The Contractor shall ensure that classified material is packaged, marked and shipped in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

The Contractor shall package and mark material for movement, shipment, receipt, and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination.

4.5 Holidays and Facility Closings:

Contractor/subContractor personnel shall observe holidays and facility closings as authorized for

Government personnel. Contractor/subContractor personnel shall only be permitted access to

Government facilities when Government personnel are present.

4.6 Travel

CONUS and OCONUS travel requests for Contractor/subContractor personnel shall be submitted for approval to the PCO (AFLCMC/WNKE) prior to costs being incurred and a minimum of 10 business days in advance of departure. The Contractor shall also submit a 30 day schedule of required travel in advance. Receipts for travel must be presented with the invoice for reimbursement of actual travel costs.

Contractor 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 personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs. All travel payments must be submitted through Procurement

Integrated Enterprise Environment (PIEE) for reimbursement of travel costs. Travel will be reimbursed in accordance with the current Joint Travel Regulation (JTR) rates in effect at the time of travel.

Submissions received with less than 10 business days’ notice may not be approved by the Government and must include a requirement for why the 10 business day requirement could not be met.

4.7 Hardware, Inspections and Repair

4.7.1 General Inspections:

In the course of repair, overhaul, and restoration, inspections shall be performed in order to ascertain the condition of the incoming equipment. After identification of a needed repair by the Contractor, customer, or AFLCMC/WNY, a separate task order will be issued via the Firm Fixed Price Teardown, Test and Evaluation (TT&E) CLIN. Under this CLIN, the Contractor will be required to accomplish a

TT&E of the equipment before starting repairs and provide a findings report to the PMO

(AFLCMC/WNY). The Government will take the provided information and request a proposal be submitted for the repairable asset. The repair of the asset will be negotiated as a separate action by the contracting officer. Additionally, an Examination and Inventory (E&I) shall be accomplished for compliance with any applicable TCTO’s. All TCTO’s that have been accomplished will be recorded on the historical data record. A copy of the historical data record will be maintained by the Contractor, a copy placed in the system at final shipmen t, and a copy sent to the PMO (AFLCMC/WNY).

Accomplishment of the AFTO 470 series Inventory Checklists will be completed upon induction of the unit. Any shortages should be promptly reported to initiate proper actions. If the repair of any item is found to be beyond 75% of replacement cost, contact the PMO (AFLCMC/WNY) for disposal action.

4.7.2 Hardware Repair and Cleaning

The Contractor shall furnish, repair, replace, or provide new components, equipment, and materials that conform to Government approved baseline specifications. The Contractor shall maintain serviceable inventory levels of sufficient quantities to sustain the LAK system. The Contractor shall ensure all Line

Replaceable Units (LRU) (in Appendix D of the PWS) items are returned to serviceable condition to the latest hardware/software configuration approved and funded by the Government for that item to ensure compliance with 6016F, as applicable. The LRUs shall be handled, tracked, repaired, stored, and shipped IAW the specifications. Return Merchandise Authorization (RMA) will be provided to the unit.

A record shall be kept indicating components utilized/repaired/completed to return each LRU to a serviceable condition. Contractor will e-mail a list of all items receipt-in for repair to the PMO

(AFLCMC/WNY), no later than 2 calendar days upon arrival of property at Contractor facility.

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. 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)5553B, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition.

4.7.3 Turn Around Time (TAT):

The required Turn Around Time (TAT) is no more than 60 calendar days after determination that the item is not over 75% of acquisition cost making it uneconomical to repair in order to maintain inventory levels of spares at 25% of fielded quantity for long lead time items and inventory levels of spares at 15% for items which are readily available. The Contractor shall respond to the PMO (AFLCMC/WNY) within one (1) business day upon receipt of critical items or Mission Impaired Capability Awaiting Parts

(MICAP) and coordinate the time required to repair the item and/or support sustainment surge or

MICAP requirements. TAT is measured from Contractor’s receipt of the repairable item to date of shipment. Surge backorders and MICAPs will take precedence over the routine schedule. Contractor shall ship MICAP and Surge items via 2nd day air or sooner. Contractor will notify PMO

(AFLCMC/WNY) at receipt of an item in for repair.

4.7.4 Tasks:

The Contractor shall provide the necessary labor, materials, facilities, and equipment required to analyze, troubleshoot, repair, overhaul, and test LAK assemblies, parts, and LAK 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.

4.7.5 Acceptance Test

Both Line Replaceable Unit (LRU) and Shop Replaceable Unit (SRU) test equipment will be available to perform testing during in-plant depot repairs. If necessary, manufacturing test equipment will be used to perform Acceptance Test Procedures (ATP) or troubleshooting of identified LAK repair items. The depot repair processes and organizations that fulfill the supportability requirements will maintain ISO

9001-2000 certification or equivalent.

4.7.6 Level of Repair:

The Contractor shall provide repair services to establish LAK support capability (other than repair/replace provided by the 611th Support Contractor) for non-warranty hardware to provide the

Organizational (LRU-level) and Depot (SRU-level) repair services defined within this PWS. The long-term goals are to maximize the operational availability and reliability of LAK systems and hardware while minimizing Government logistics support investments required to achieve desired system life cycle with predictable and affordable sustainment costs.

4.8 Program Management:

The Contractor shall plan and execute the tasks required in this PWS and shall identify, assess, and manage associated risks. The program manager or equivalent shall be the single POC for the

Government. Questions concerning the restoration or repair of the equipment, procedures, substitutions, or funds shall be directed to the Warner Robins, GA Air Force Life Cycle Management Center

(AFLCMC/WNY). This PWS provides detailed information for CLS of the LAK system and LAK software. The information contained in this section is not intended to be all inclusive or to detract from procedures outlined in specifications and other directives listed in Appendix C of this PWS.

Workmanship shall be in accordance with Contractor’s standard repair procedures and acceptance criteria in accordance with best industry practice. (DI-MGMT-80004A, Management Plan,CDRL A023)

4.8.1 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 and submit an Obsolescence and DMSMS Management Plan for managing the loss, or impending loss, of manufacturers or suppliers of parts and/or material required for performance of this contract. At a minimum, 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 Manager's Handbook -

Common Practices to Mitigate the Risk of Obsolescence", published by the Defense Microelectronics

Agency (available at https://www.dmea.osd.mil/docs/pmhandbook_rev_d.pdf ) may be used as a guide in developing the Obsolescence Management and DMSMS Plan. In lieu of preparing and submitting an

Obsolescence and DMSMS Plan, the Contractor may provide an existing plan or existing written processes and procedures for review. (DI-SESS-81656, Data Item Description, Source Data for

Forecasting Diminishing Manufacturing Sources and Material Shortages, CDRL A00V)

4.8.2 Configuration Management

4.8.2.1 The Contractor shall provide and maintain updated Configuration Management (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. A list of all Configuration https://www.dmea.osd.mil/docs/pmhandbook_rev_d.pdf changes made to the system both hardware and software shall be submitted to the government within 60 days action notifying the government of same changes to the system.

4.8.2.2 The Contractor will maintain a formal CM system for the LAK program that includes, at a minimum, the following processes: Configuration Identification, Configuration Status Accounting, Configuration Control, Configuration Verification/Audits, Contract Data Management, Deficiency

Reporting and Investigating, and Engineering Data Management.

4.8.2.3 The Contractor shall implement CM, develop and document the Configuration Management

Plan (CMP) (maintained at Contractor facility), and support the preparation of required documents to support Configuration Review Board (CRB), Technical Review Board (TRB), and Configuration

Control Board (CCB) may include travel as required. (DI-SESS-81875, Configuration Management

Plan, CDRL A00Y)

4.8.3 Deficiency Reports

The Contractor shall provide and maintain a quality assurance program. Materiel and software deficiencies and quality deficiency reports shall be handled IAW technical data provided.

4.8.3.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 weapons 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 system to augment JDRS capability, but not replace JDRS as the official USAF deficiency repository.

The Contractor shall provide initial responses within 5 calendar days. The Contractor will adhere to directives outlined in TO 00-35D-54 for proper management of the DRI&R for the LAK system.

4.8.4 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 LAK

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 http://www.jdrs.mil/

4.8.4.1 Transition Plan, Phase out

The Contractor shall provide a Phase Out transition Plan 60 days prior to contract expiration. The

Contractor shall provide a written comprehensive plan explaining actions required to complete the total transition effort using a 30 calendar day transition period utilizing best commercial practice which includes but not limited to:

Details for the removal of all Contractor owned items

Turn in of Government provided Common Access Cards (CACs)

Provide current inventory and packaging plan for shipment

Critical path schedule for risk mitigation of the transition period

Provide system admin passwords to PMO (AFLCMC/WNY) through secure channels

(DI-MGMT-81945, Phase-Out Transition Plan, CDRL A00X)

4.9 Cybersecurity

4.9.1 LAK ATO, ATO w/ Conditions, ATC:

The Contractor will support the LAK Information Systems Security Manager (ISSM) in completion of the Risk Management Framework (RMF) process for LAK in preparation for obtaining an Authority to

Operate (ATO) and Authority to Connect (ATC) from the Command and Control (C2) Authorizing

Official (AO) according to DODI 8510.01 RMF for DOD IT, AFI 17-101 RMF for AF IT, and the DOD

RMF Knowledge Service. In the event the AO grants an ATO with Conditions the Contractor shall support the Government ISSM on Cybersecurity actions until the ATO/ATC is granted. This involves providing system documentation and artifacts for input into the Risk Management process. In support of the RMF process, the Contractor shall provide input and updates to The System Security Plan (SSP) which includes at a minimum the following documents:

1) Security Concept of Operations (SECONOPS)

2) LAK unique Continuity of Operations Plan (COOP), including the Disaster Recovery Plan (DRP), and Contingency Plan. These will be used as input to the 611 Air Communication Squadron

(ACOMS) COOP, Contingency Plan, and DRP

3) LAK unique incident response requirements to supplement the 611ACOMS Incident Response

Plan (IRP)

4) Hardware listing (baseline)

5) Software listing (baseline)

6) Topology with logical and data flow diagrams

7) Ports and Protocol Services Matrix (PPSM)

8) Physical Security Plan

9) Audit and Accountability Policy

10) Configuration Management Policy

11) Cybersecurity Training Plan

12) Vulnerability Management Plan (VMP) and Patch Management Plan to be updated periodically as required by the latest Cybersecurity guidance

13) Plan of Action and Milestones (POA&M)

14) Contractor In-Plant Cybersecurity Test Report from Contractor Cybersecurity self-assessments

15) The Contractor shall implement Cybersecurity controls as defined by DoDI 8510.01, Risk

Management Framework (RMF) for DoD Information Technology (IT) (change 1 May 24 2016) and

NIST 800.53 and the RMF Knowledge Service. The Air Force has moved to the Risk Management

Framework (RMF)

4.9.1.1: The Risk Management Framework (RMF) process is not defined by system versions. In the event that a version change does occur, the Contractor shall still be responsible for supporting the items and tasks listed in paragraph 4.9.1 at no additional cost to the Government.

4.9.1.1.1: The Contractor shall implement Cybersecurity controls as defined by DoD (8500.01, Cybersecurity and NIST 800.53) and the RMF Knowledge Service, as well as specific controls required by the FIPS 199, Standards for Security Categorization of Federal Information and Information

Systems.

4.9.1.2: The Contractor shall provide the Government with all test results via secure means via

Department of Defense (DoD) 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM) as these test results may be classified.

4.9.1.3: The Contractor shall analyze all latent defects and attribute vulnerability severity values according to the National Institute of Standards and Technology Special Publication 800-30, Guide for

Conducting Risk Assessments. (e.g. High, Medium, Low)

4.9.1.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 biannually and current DOD requirements.

4.9.1.5: The Contractor shall analyze the findings to identify any latent defects and attribute vulnerability categorization codes and review the test results and analysis report with the

Government. The Contractor shall deliver results of the source code analysis via secure channels if required.

4.9.1.6: With the Government’s approval, Contractor shall fix findings in accordance with Government priorities and schedule. The Contractor must provide software free from all High risks, and must satisfactorily mitigate all Medium findings to achieve and maintain the ATO. (Ref. DoDI 8510.01, Risk

Management Framework (RMF) for DoD Information Technology (IT)).

4.9.1.7: 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 LAK prior to its use or integration, and the Contractor must meet the requirements defined in the current DISA

Application Security and Development Security STIG (Technical Implementation Guide). Approval is accomplished by either selecting a product already approved for use on Air Force networks from an appropriate list or by following the Air Force Network Integration Center (AFNIC)/External Volume

Serial Number (EVSN) instructions for obtaining an approval for use of such software. The Contractor shall document the evaluation/approval status for each third party software item in a Software

Evaluation Summary Form (DI-NDTI-80566A, Test Plans, CDRL A00C; DI-NDTI-80603A, Test

Procedures, CDRL A00D; DI-NDTI-80809B, Test/Inspection Report, CDRL A00E; DI-CMAN-

81248A, Interface Control Document, CDRL A008).

4.9.1.8: The Contractor shall “lock down” and test the different variants of LAK system with 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. Any deviation to settings that become findings shall be documented on a Plan of Action & Milestones (POA&M) and submitted to the Government via secure means.

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

4.9.2 Cybersecurity Scans:

The Contractor shall assist the ISSM with ACAS scans against the baseline LAK configurations and develop patches/updates as required and approved by the Government. The images created from these scans will be used on all new systems and all systems returned to the Contractor for repair.

4.9.2.1: The Contractor shall evaluate all IAVAs for applicability to LAK. The Contractor shall conduct vulnerability scans against the current system baseline configuration, utilizing current DOD approved software. The Contractor will be required to create IAVA patch disk of all applicable patches quarterly, to include third party software. Once created, the disks will be provided to the Government to test and approve for fielding. The images created from these scans will be used on all new systems and all systems returned to the Contractor for repair. If the Contractor is unable to patch a vulnerability due to system requirements, operational issues, costs, resources, or any other issue these items will be annotated on a Plan of Action and Milestones (POA&M) and shipped to the Government overnight, as this is a classified document.

4.9.2.2: Any time a High or Medium vulnerability is identified or discovered, the Contractor shall notify the Government PMO (AFLCMC/WNY) within 24 hours.

4.9.3 Urgently Required (Out of Cycle) Cybersecurity Fixes:

The Contractor shall evaluate all IAVAs for applicability to LAK. The Contractor shall recommend to the Government Program Office a course of action and cost estimate based on urgency (High, Medium, or Low) 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 ISSM. The Contractor shall notify the Government PMO

(AFLCMC/WNY) and ISSM within 24 hours of discovering vulnerability and necessary out of cycle cybersecurity fixes with information pertaining to the findings of the problem, urgency of the problem, availability of a fix, corrective action, and projected timetable to complete the cybersecurity fix.