DRAFT ARCTICS II PWS_10-08-2024.docx

PERFORMANCE WORK STATEMENT

FOR

Alaska Range Combat Training Integrated Communications and Support (ARCTICS) Date: 08 October 2024

SOLICITATION NUMBER:

TBD

PREPARED BY:

766 Enterprise Sourcing Squadron (ESS), Joint Base Pearl Harbor-Hickam, Hawaii

ARCTICS Performance Work Statement Table of Contents

ARCTICS Performance Work Statement ARCTICS Performance Work Statement

1 SECTION 1 – DESCRIPTION OF SERVICES

1.1 Overview

The 354th Range Squadron (RANS) has a requirement for integrated range operations and maintenance in support of joint air and ground combat training and testing for the United States Air Force’s (USAF) Headquarters (HQ) Pacific Air Forces (PACAF) at the Joint Pacific-Alaska Range Complex (JPARC). The JPARC consists of all air, land, and sea training capacity and assets in Alaska. JPARC is composed of military land ranges, maritime training areas, and airspace that provide critical training and testing environment to the Department of Defense (DoD) Service units based in Alaska. PACAF's primary mission is to provide ready air and space power to promote U.S. interests in the Asia-Pacific region during peacetime, through crisis, and in war. The JPARC is the predominant PACAF Area of Responsibility (AOR) training venue supporting mission requirements. It can provide highly realistic training for service, joint, and coalition combat aircrews, aviation ground crews, surface maneuver units, and command staff. RED FLAG-Alaska (RF-A) is a primary USAF combat training exercise and a Joint National Training Capability (JNTC) accredited and certified event that is executed within the JPARC. The JPARC consists of Military Operations Areas (MOAs), Military Training Routes (MTRs), Restricted Airspaces, combat training ranges with both live and inert weapons impact areas, electronic warfare (EW) sites, and all facilities, structures, shelters, systems, and equipment necessary to support live combat training operations. “JPARC South” refers to facilities at Joint Base Elmendorf- Richardson (JBER) and Special Use Airspace (SUA), in accordance with (IAW) 14 CFR Part 73, used/controlled primarily by the 3rd Wing (WG). “JPARC North” refers to all facilities, ranges, and SUA at Eielson Air Force Base (AFB), as well as other facilities, ranges, and SUA not included in JPARC South. Capabilities include providing realistic adversary Electronic Orders of Battle (EOB), Electronic Attack (EA) training, integrated Live, Virtual, and Constructive (LVC) operations, and real-time air-to-air, air-to-ground, ground-to-air monitoring and playback for user feedback and performance self-evaluation.

1.2 Purpose

This Performance Work Statement (PWS) establishes the requirements and responsibilities of the Contractor to provide PACAF specified Operations and Maintenance (O&M) support of Government Furnished Property/Equipment (GFP/GFE), materials, facilities, structures, shelters, and infrastructures. Contractor support requirements are defined throughout the entirety of this PWS.

1.3 Background

The Contractor shall provide specified O&M support to provide realistic combat training capabilities in support of daily operations, Large Force Employment (LFE) events, and Major Force Exercise (MFE) activities in the JPARC and at deployed locations.

The Contractor shall be responsible for all management and labor, equipment, tools, and supplies not otherwise specified as GFE, in support of specified JPARC activities. The Contractor shall comply with all applicable laws, regulations, technical data, and standards while providing O&M support.

The Contractor shall provide a workforce that is trained and fully qualified/certified for the tasks assigned.

The Contractor shall schedule, coordinate, and cooperate with government agencies, other contractors, and/or external agencies that are simultaneously supporting JPARC missions with the purpose of all entities working toward the same goal of providing world-class combat training.

Upon commencement of performing contracted tasks, the Contractor shall possess a Facility Security Clearance (FCL) adjudicated to the TOP SECRET (TS) level. Contractor personnel shall possess a minimum Personnel Clearance (PCL) adjudicated to the SECRET level. Contractor personnel required to perform work in facilities accredited to a TS, SENSITIVE COMPARTMENTED INFORMATION (SCI), and/or SPECIAL ACCESS PROGRAM (SAP) shall have the requisite security clearances. A detailed listing of functions requiring TS/SCI and/or SAP clearances is found in PWS 3.2.8.2.

The Contractor will be given access to adequate space at the requisite security level for refurbishment of large, motorized vehicles and radar systems. When required, O&M support shall be conducted in secure Government facilities with requisite security accreditation or within the systems themselves.

The Contractor shall provide and maintain a signed copy of Standard Form 1408 [Pre-Award Survey of Prospective Contractor (Accounting System)]. IAW Block 1 of Standard Form 1408 (Accounting System Review Be Performed After Contract Award), the Contractor shall conduct a review of their Accounting System.

2 SECTION 2 – APPLICABLE DOCUMENTS

In the event of a conflict between documents referenced herein and the contents of this PWS, the contents of the PWS shall be the governing requirement.

2.1 Department of Defense Specifications

2.1.1 Availability of Department of Defense Specifications

Copies are available on the WWW at URL: https://www.dsp.dla.mil/Specs-Standards/

2.2 Department of Defense Standards

· MIL-STD-130: Identification Marking of U.S. Military Property

· Property MIL-STD-31000: Technical Data Packages

· MIL-STD-40051-2A: Page-Based Technical Manuals

· GEIA-STD-0007-A: Logistics Product Data

2.2.1 Availability of Department of Defense Standards

Copies are available on the WWW at URL: https://www.dsp.dla.mil/Specs-Standards/

2.3 Department of Defense Directives

· DOD 8140: Information Assurance (IA) Training, Certification, and Workforce Management

2.3.1 Availability of Department of Defense Directives

Copies are available on the WWW at URL: https://www.esd.whs.mil/DD/DoD-Issuances/

2.4 Department of Defense Instructions

Required DOD Instructions (DODI) may include the below, but also may other publications.

· DODI 5000.2: Operation of the Adaptive Acquisition Framework

· DODI 5000.90: Cybersecurity or Acquisition Decision Authorities and Program Managers

· DODI 8500.01: Cybersecurity

· DODI 8510.01: Risk Management Framework (RMF) for DOD Information Technology (IT)

2.4.1 Availability of Department of Instructions

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.5 Other Government Documents, Drawings, and Publications

· Department of Defense Intelligence Information System (DODIIS): Joint Security Implementation Guide (DJSIG)

· DAG: Defense Acquisition Guidebook

· https://dag.dau.mil/Pages/Default.aspx

· DISR: Department of Defense Information Technology Standards Registry

· http://jtaonline.disa.mil/VJTA/index.jsp

· AFMAN 23-110 U.S. Air Force Supply Manual

· http://static.e-publishing.af.mil/afman/23-110/VOLTOC.pdf

· See Appendix 3 for Department of Air Force Instructions (DAFIs), Directives, Technical Orders, Standards, and Commercial Materials

2.6 Required Publications

Required publications consist of: DAFIs, Directives, Technical Orders, Standards, Army Regulations, and Commercial Manuals. It is the Contractor’s responsibility to ensure they are familiar with the most up-to-date versions of the Required Publications and to notify the Government if they are unable to access those documents or require further guidance. The Contractor shall reference and comply with stipulations as defined in this PWS and Appendix 3.

3 SECTION 3 – REQUIREMENTS

The Contractor shall provide the technical services and support pursuant to the requirements specified within this PWS.

3.1 Administration

3.1.1 Work Locations

3.1.1.1 Permanent Sites

Special Use Airspace (SUA) of the JPARC:

· Restricted Airspace: R-2201, R-2202, R-2205, R-2211, R-2203

· Warning Areas: W-612

· Military Operations Areas (MOA): Birch/Buffalo/Delta/Eielson/Fox/Galena/Naknek, Paxon/Stony/Susitna/Viper/Yukon

· Air Traffic Control Assigned Airspace (ATCAA): Blair/Colorado/Delta/Eielson/Fox/Galena/Hayes/Kantishna/Naknek/Paxon/Sand Point/Sparrevohn/Stony/Susitna/Tok/Utopia/Viper/Yukon Training Ranges of the JPARC:

· Yukon Training Area (TA) (YTA)

· Donnelly Training Area (DTA)

· Blair Lakes Training Range Complex Training Areas of the JPARC:

· TA-600 (Gerstle River) A detailed listing of sites/locations is contained in Appendix 6. When additional SUA, Training Ranges, and/or Training Areas are added to the JPARC, the Contractor will be required to perform work to support training operations in the additional locations. The Government will initiate a modification by releasing a Request for Proposal (RFP) and modify Appendix 6 as applicable. Infrastructure and equipment are listed in Attachment 3, GFE/GFP Listing, and Appendices 6, 7, and 8.

3.1.1.2 Deployed Sites

As required and coordinated with the Contracting Officer (CO), based on USAF training support requirements and flying exercise commitments such as, but not limited to: JBER, Road accessible sites within Alaska not identified in Appendix 6, Sites and Locations; Middleton Island/Gulf of Alaska (GOA); sites of the Long-Range Radar System (LRRS) operated by the 611 AOC to include but not limited to Ft. Yukon, Barter Island, etc., the High-frequency Active Auroral Research Program (HAARP) site near Gakona, AK., U.S. Coast Guard Station, Kodiak, training areas/ranges within the contiguous 48 United States and Canada; and throughout the PACAF AOR, to include the Republic of Korea, Thailand, Singapore, Malaysia, Australia, Japan, Indonesia, India, the U.S. Territory of Guam, and the state of Hawaii.

3.1.2 Work Hours

3.1.2.1 Employee Work Hours

The Contractor's employee schedule shall accommodate schedules of the Government (e.g., 353 CTS, 354 RANS, 354 OG, 354 OG Det 1, 354 FW, 3 WG, aircraft units, wing safety, etc.). Contractor’s attention is directed to paragraphs 3.8, 3.10. 2.11, 3.12 and sub-paragraphs for work schedule requirements in support of flying training operations.

3.1.2.2 Maintenance Work Schedule

The Contractor shall establish work hours for maintenance. All maintenance shall be performed on a non-interference basis with scheduled operations. No systems will be exempt from operational availability except for the purpose of maintenance to bring the system back on-line. Routine maintenance will be scheduled during non-operation hours.

3.1.2.3 Work Commute

IAW A.S. 785.33 and 785.35, Portal-to-Portal travel prior to, and post work hours are not compensable time. Portal-to-portal is defined as normal travel to/from home to work site, even if work sites vary. The Contractor shall not bill the government for personnel travel to/from work sites.

3.1.2.4 Worktime during Travel

IAW A.S. 785.39, travel away from home community shall be considered work time during normal work hours. Time spent in travel away from home outside of regular working hours as a passenger on an airplane, train, boat, bus, or automobile is not considered work time. Contractor shall not bill the government for personnel time spent in travel outside of defined work time.

3.1.2.5 Overtime Pay

The Government will compensate the Contractor for approved overtime hours expended for performance of task during training support deployments and requested expansion of operation hours. The Contractor shall provide a cost estimate, to include the anticipated overtime required, for each deployment and expansion of operation hours. The Contractor shall make every effort to shift employee work schedules to accommodate expanded flying hour requests to avoid overtime. The Contractor shall not bill more than 40 hours per week per employee unless the additional hours were pre-approved by the CO through the Contracting Officer Representative (COR). Additionally, COR approval is required prior to commencement of overtime workhours. Temporary duty (TDY) travel during non-duty hours, weekends, and holidays shall not be considered compensable overtime; however, transportation and per diem expenses for travel performed during these periods shall be reimbursable.

3.1.2.6 Federal Holidays, Down/Goal Days, and PACAF Family Day Work Schedules The Contractor shall not be excused from work performance on any days except as defined as legal federal holidays, stipulated in 5 U.S. Code 6103 – Holidays. Down/Goal Day, and/or PACAF Family days shall be workdays unless an alternate work schedule is approved by the CO and COR.

3.1.2.7 Legal Federal Holidays

New Year’s Day; Birthday of Martin Luther King, Jr.; Washington’s Birthday; Memorial Day; Juneteenth National Independence Day; Independence Day; Labor Day; Columbus Day; Veterans Day; Thanksgiving Day; and Christmas Day.

3.1.2.8 Contingency Situations

During a Crisis Declared by the National Command Authority or Overseas Combatant Commander, the services performed under this contract are not applicable to the requirements as described in DoDI 1100.22 Policy and Procedure for Determining Workforce Mix.

3.1.2.9 Disaster Response

At the direction of the Government and negotiated with the Contractor, the Contractor shall provide, within areas of its expertise, for disaster response work and emergency service for disaster damage repair to JPARC systems and infrastructures.

3.1.3 Contractor Performance Requirements

3.1.3.1 Contractor Responsibilities

The Contractor shall deploy, operate, repair, maintain, fuel, and re-deploy systems as directed by the elements of this PWS. Upon return from mission execution events, the Contractor shall inventory, repair, replenish, and prepare systems and equipment for redeployment for other test events. The Contractor shall assume total performance responsibility for work performed and deliveries under this contract. The Contractor shall ensure proper management of ARCTICS subcontractors through analysis, critique, and assessment of the adequacy, timeliness, and cost effectiveness of work performed. The Contractor shall coordinate management efforts with Government personnel. To aid Government oversight, the Contractor shall submit reports as described in the sections and paragraphs in this contract. When issues are identified, the Contractor shall formulate and provide alternatives for issue resolution.

3.1.3.2 Contractor Manpower Reporting

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services under this contract to the 766 ESS via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: https://www.sam.gov. Reporting inputs will be for labor executed during the period of performance during each Government Fiscal Year (FY) which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than (NLT) October 31 of each calendar year. Contractors can find User Guides, Frequently Asked Questions and may direct questions to the help desk https://www.sam.gov.

3.1.3.3 Operational Security Plan

The Contractor shall develop and implement an Operational Security (OPSEC) Plan for control of critical program information and sensitive data. The Contractor shall provide an electronic copy to the 354 RANS as well as the 766 ESS after award, and updated copies shall be provided after any change is made. The plan, as updated, shall continue to conform to the requirements of this contract and further instructions contained in AFI 10-701 (Operations Security). The Contractor shall deliver the plan NLT 10 duty days after contract award to the CO and COR as part of the Management Plan. Reference Appendix 5 for more information.

3.1.3.4 Property Management Plan

The Contractor shall develop their Property Management Plan (PMP) (IAW requirements in Section H) for any GFP or Contractor Acquired Property (CAP). This plan shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of GFP. The Contractor shall provide an electronic copy of the PMP to the CO and COR NLT 10 days after contract award as part of the Management Plan. Reference Appendix 5 for more information.

3.1.4 Work Control

All program requirements, contract actions, and data interchange shall be conducted in a digital environment using electronic and web-based applications that are accessible on a standard Non-Secure Internet Protocol Router (NIPR) computer. When applicable, such data shall be compatible with the latest version of Microsoft Office family of products. Contractor developed or procured software packages to meet this requirement, if any, that are to reside on computers connected to NIPR, must be on the approved software listing for NIPR and be approved by 354th Communications Squadron.

3.1.5 Meetings and Reviews

3.1.5.1 Range Meetings

The Contractor shall conduct, attend, and participate in range meetings related to events in the JPARC. The meetings are to be scheduled upon request of the responsible CO or COR to discuss and to informally evaluate the Contractor’s efforts and accomplishments. During these meetings, the Contractor shall present necessary data to enable a joint review of its various assigned efforts, attendant schedules, and resource expenditures. The Contractor shall present and participate in technical discussions and shall inform, in a timely fashion, the COR of any problems with contract execution and any proposed solutions. The Contractor shall provide meeting minutes and all necessary presentation material. Reference Appendix 5 for more information.

3.1.5.2 Annual Contract Performance Review

The Contractor shall meet with the CO and COR at the end of each 12-month period following contract award for a Contract Performance Review. During this review, the Contractor and CO/COR will review the Contractor’s plans and reports for any updates. Reference Appendix 5 for more information.

3.1.5.3 Kickoff Meeting

The Contractor shall meet with the CO, COR, Requirement Owner, and users NLT 10 days after the start of performance to kick off performance of the contract.

3.1.6 Routine Reports

3.1.6.1 Monthly Progress, Status, and Management Report

The Contractor shall submit a monthly Contractor’s Monthly Progress, Status, and Management Report (MPSMR). This report and the financial reports shall convey the status of all base Contract Line Items (CLINs) as well as cumulative contract performance. The Contractor shall notify the Government when 75% of the Cost and CLINs have been expended. This report shall include cost data identifying Labor Category, Material, and Travel on a monthly basis and on a cumulative basis for each month. In addition, all travel and material costs shall be documented on a monthly basis and cumulative monthly. CLINS that have been completed shall be listed as such. Reference Appendix 5 for more information.

3.1.6.2 Material Status Report

The Contractor shall provide a weekly Material Status Report (MSR) listing the equipment that is not mission capable, the reasons for that status, and the action(s) being taken to repair the equipment. The Contractor shall identify any special needs or concerns requiring Government assistance.

The Contractor shall provide an Annual MSR in which the Contractor shall report maintenance, logistics, and operations trends that the government can use to make strategic management corrections to systemic problems made visible during the year. The Contractor shall provide an Annual Maintenance Service and Repair Cost Report that provides the government with data that shows the cost of service and repair parts, hours worked, shipping and postage, Petroleum, Oil, Lubricants (POL), and Other Consumables expended to provide preventive maintenance and repair maintenance to GFE. Demand history shall be used as the basis of future-year expense planning through the Program Objective Memorandum (POM) years. Reference Appendix 5 for more information.

3.1.7 Import/Export, End-User Certificate and ITAR Compliance The Contractor must be familiar with unique circumstances that require Import/Export, End-User Certificate and International Traffic in Arms Regulations (ITAR) compliance. The Contractor shall comply with all import/export regulation requirements. The Contractor shall comply with all End-user Certificate regulation requirements referencing Defense Federal Acquisition Supplement (DFARS) Clause 225.802-71 to execute the proper signing of these documents. The Contractor shall execute a comprehensive ITAR compliance program that includes information, policy, and procedures on: Organization Structure, Corporate Commitment and Policy, Identification, Receipt and Tracking of ITAR Controlled Items/Technical Data, Re-Exports/Retransfers, Restricted/Prohibited Exports and Transfers, Recordkeeping, Internal Monitoring, Training, and Violations and Penalties.

3.2 General Requirements

3.2.1 Contract Transition

The transition period is that period during which the incumbent Contractor and the successor Contractor jointly accomplish a transfer of property and responsibility for contract performance. The transition period will be the final 90 days of the incumbent’s contract.

3.2.1.1 Incumbent Contractor responsibilities

When the contract reaches 90 days before completion, the Contractor shall continue to provide supervision, control, and work task responsibility for all functions described in their applicable PWS(s) during the transition period. The incumbent Contractor shall support the Government and the successor Contractor to ensure an orderly transition. As a minimum, the incumbent Contractor shall provide the successor access to facilities, structures, shelters, equipment, technical documentation, property accountability, publications, spares etc. on a non-interference, no-cost basis during the transition period.

3.2.1.2 GFP/GFE Audit

The Government, incumbent Contractor, and successor shall perform an audit to include a joint inventory and inspection, and all GFP will be transferred no later than the end of the transition period. The successor Contractor shall inform the CO and COR of any GFP/GFE that is unable to be transferred/audited during the transition period no later than 15 working days prior to the end of the transition period. At the start of the audit, incumbent Contractor shall provide a 100% complete and accurate GFP listing. The incumbent shall be solely responsible for replacement of missing or damaged-beyond-repair GFP/GFE.

3.2.1.3 GFP/GFE Repair

The Contractor is liable for the repair or replacement of all items (e.g., facilities, structures, shelters, major systems, all other GFP/GFE) in the same or better condition than received, discounted for normal wear and tear. During contract transition, the successor Contractor shall accept items “as is” that have open work orders for maintenance or repairs that are reasonable and expected during the lifecycle of the items.

3.2.1.4 GFP Documentation

The incumbent Contractor shall replace any missing, unusable, or outdated documentation NO LATER THAN 30 days before the end of the contract performance period.

3.2.1.5 Data and Documentation Transfer

The incumbent Contractor shall transfer all data, information, reports, records, schedules, software products, point of contacts, information on requisitioned items, etc. that pertain to the equipment, systems or services defined by this contract to the successor Contractor.

3.2.1.6 Successor Contractor Responsibilities – Phase-in Plan The successor Contractor shall develop and submit a Phase-in Plan to the CO and COR. The Phase-in Plan shall be sent to the CO and COR NLT 5 duty days following contract award. The plan shall contain a listing of phase-in team members and their contact information, projected timelines, and critical phase-in activities/action items. In addition, the plan shall specify when each employee/position transitions on-site and include their duties and responsibilities. During phase-in, the Contractor shall provide daily reports on transition. The successor Contractor shall execute the phase-in plan on the first day of the transition period. Reference Appendix 5 for more information.

3.2.1.7 Phase-Out Plan

The Contractor shall develop and submit to the CO and COR a Phase-out plan within the first 180 days from contract start date. The plan shall be updated annually to ensure accuracy and effectiveness. The plan shall be specific on how the Contractor will smoothly turn over responsibilities assuring full operational capability for the successor on the first day the successor’s contract becomes effective (e.g., transition of property accountability, orientation, training). The Contractor shall implement the Phase-out Plan 90 days prior to the last day of the contract. Reference Appendix 5 for more information.

3.2.2 Program Management

The Contractor shall manage all aspects of contract performance and provide stewardship of Government resources. The Contractor shall provide a responsive and proactive organization whose personnel perform at a proficient skill level and at a minimum meet the performance thresholds identified in Table 5-1.

3.2.2.1 Management Plan

(a) The Contractor shall submit a Management Plan to the CO and COR NLT 10 duty days after contract award. The plan shall be in Contractor format and conform to the following:

(b) The plan shall be identified with the preparing office or Contractor’s title, the identifying numbers or designators of the contract, the identity of the program, the security classification, and the Government activity issuing the controlling contract.

(c) The plan may include descriptive material such as graphs, worksheets, tables, etc. as required to clarify or illustrate matters within the text.

(d) The plan shall be in a current digital format per Appendix 5, A5.1.1.

(e) The plan shall consist of as a minimum:

1) Contractor’s organizational structure and assignment of functions, duties, and responsibilities

2) Contractor’s procedures, policies, and the reporting requirements that are established for the initiation, monitoring, control, completion, and reporting of contractual tasks, projects, and programs.

3) Contractor’s maintenance plans

4) Contractor’s security program and procedures

5) Contractor’s Operational Security Plan

6) Contractor’s Property Management Plan

7) Contractor’s Quality Control Plan

8) Contractor’s Environmental Management Plan

9) Contractor’s Occupational Safety Plan

10) Contractor’s Command Supported Equipment Management Plan

11) Contractor’s Configuration Management Plan

12) Contractor’s Key, Lock, and Lock Combinations Procedures

13) Contractor’s Integrated Master Plan

3.2.2.2 Program Manager

The Contractor shall provide a Program Manager, located at Eielson AFB, responsible for the overall supervision and control of all JPARC O&M services required by this PWS. Contractor shall provide a point of contact (POC) at JBER to facilitate and coordinate operations.

3.2.2.2.1 Appointment Letters

The name of the Program Manager, JBER POC, and alternates shall be designated in writing to the CO, and COR no later than the transition start date. Updated letters for new/additional personnel shall be provided within 2 business days of appointment. Reference Appendix 5 for more information.

3.2.2.3 Meetings with Government

The Program Manager is required to meet with the CO, contract administrator, COR, Quality Assurance Evaluators (QAE), and other Government personnel when requested. The Contractor may request a meeting with the CO.

3.2.2.4 Program Manager Availability

During operation hours, the Program Manager or alternate shall be available either telephonically or in-person within 30 minutes to discuss contract matters with Government personnel. Outside of operation hours, the Program Manager or designated alternate shall be available within 2 hours.

3.2.2.5 Meeting Minutes

The Contractor shall record the minutes for meetings with the Government relating to this contract. The Contractor shall coordinate the minutes with the COR prior to finalizing, publishing, and distributing meeting minutes to all attendees within 5 business days. The Contractor shall reference Appendix 5 for specific requirements regarding drafting of meeting minutes.

3.2.3 Financial Management

The Contractor shall include in the MPSMR its financial status, budget, schedule, and control of the resources allocated to meet the requirements of the contract. The Contractor shall be responsible for cost containment and shall assess potential impact of future cost increases (if any) and provide the Government options to offset increases to stay within original contract costs.

3.2.3.1 Unfunded Requirements List

The Contractor shall identify any supplies, equipment, or line-item requirements that cannot be supported within approved funding on a prioritized Unfunded Requirements List (URL). The number one priority shall be the requirement that is the most mission essential. The Contractor shall coordinate with the Government as to the priority of items on the URL. The URL shall be saved to an electronic file system managed by the 354 RANS on NIPR/SIPR to which the Contractor will be given access. The URL shall be included in the referenced in paragraph 3.2.2.6 and its sub-paragraphs.

3.2.3.2 Document Financial Information

The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations, and invoices against each contract line item and sub-line item. The Contractor shall develop the Contractor’s Work Breakdown Structure (CWBS) and extend the CWBS to define the lower-level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the Contractor and the Contractor’s responsibility. The extended CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the extended CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall document financial information in its MPSMR to the CO and COR. The MPSMR shall reflect current and previous fiscal year contract cost data, projected funding requirements, and expenditures. Additional financial information shall include (as applicable):

(a) A summary listing of all cost reimbursable expenditures by CLIN indicating funding authorized to date.

(b) Cumulative billings.

(c) Actual cumulative costs to date.

(d) Actual costs incurred since last reporting period.

(e) Projected costs through end of fiscal year.

(f) Cost variances comparing the estimated cost of completion to amount of funds authorized.

(g) Percentage of funding obligated and spent.

(h) Notice to the Government of any potential inability to fulfill financial obligations a minimum of 30 days prior to delinquency, to include proposed solutions URL reviewed for accuracy and completeness.

3.2.4 Information Assurance Contractor Training and Certification The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD Directive 8140.01: Cyberspace Workforce Management, and DoD Manual 8140.03: Cyberspace Workforce Qualification and Management Program. This includes an approved DD Form 2875. The Contractor shall meet the applicable information assurance certification requirements, including:

(a) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD Manual 8140.03, and AFI 17-1303.

(b) Appropriate Computing Environment certification for information assurance technical positions as required by DoD Manual 8140.03.

(c) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(d) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

(e) Contractor personnel with administrator privileges must meet additional requirements, including but not limited to CE certifications.

3.2.5 Contractor Quality Control

Contractor shall develop and maintain a quality program to ensure support services are performed in accordance with commonly accepted commercial practices, manufacturers’ recommendations, this contract, and all federal, state, and local laws and regulations. As a minimum, the Contractor shall develop quality control procedures addressing all major requirements as outlined in this PWS, including the areas identified in the Service Summary. The Contractor shall develop and implement proactive procedures to identify, prevent, correct, and ensure non-recurrence of defective services. Records of all inspections conducted by the Contractor and corrective action taken shall be made available to the Government within one business day upon request.

3.2.5.1 Quality Control Plan

The Contractor shall submit its Quality Control (QC) Plan as part of its Management Plan to the CO and COR. As a minimum, the QC Plan shall provide a detailed approach and information on how services will be evaluated and shall identify the frequency, scheduling, and degree of QC inspections that are sufficient to identify deficiencies before they become larger problems and minimizes Government inspection. The QC Plan shall:

(a) Detail controls that will be utilized to substantiate those personnel are able to meet PWS requirements.

(b) Detail analysis processes to be used to identify trends with equipment reliability, Product Quality Deficiency Reports (PQDRs), and repeated deficiencies found during inspections.

(c) Detail how the Contractor’s quality program will ensure accuracy, thoroughness, and timeliness of all reports submitted to the Government.

3.2.5.1.1 Contractor shall reference Appendix 5, paragraph A5.2.6 for QC Plan requirements.

3.2.5.2 Monthly Report of Inspections

The Contractor shall include summaries of inspections accomplished, results thereof, and projected remedies (if applicable), and next month’s inspection schedule in its MPSMR sent NLT 5 duty days at the end of the previous month.

3.2.6 Contract Administrative Management

3.2.6.1 Records – General.

The Contractor shall keep records current and organized. The CO and COR may require copies of documentation or electronic data. The Contractor shall provide requested information within 2 hours for urgent requirements or within 1 working day for routine requirements. Unless otherwise specified in Appendix 5 or by the CO/COR, the Contractor may provide reports and requested information electronically, such as on CD/DVD, or via e-mail. All documentation referred to in this PWS, including all automated electronic data is the property of the Government and shall remain so upon termination of this contract.

3.2.6.2 Contract Data Management

The Contractor is responsible for all aspects associated with contract Data Management for the JPARC. The Contractor shall develop and maintain all contract-required data.

3.2.6.3 Single Focal Point for Data Management

The Contractor shall:

(a) Designate a single focal point for management of all contract data requirements.

(b) Integrate and manage data from all functional areas of the contract.

(c) Include all records, instructions, plans, permits, and all other documentation created by the Contractor or collected as a result of a PWS requirement in the management of data.

3.2.6.4 Maintaining Master Copies

The Contractor shall:

(a) Maintain and control master copies of all contract data, including reports, plans, meeting minutes.

(b) Ensure data created meets all contract and Government requirements.

(c) Ensure that any data being delivered has incorporated the latest revisions.

(d) Ensure subcontractors and vendors provide data required by this contract.

3.2.6.4.1 Single Software-Based Data Program

The Contractor shall provide and utilize a single software-based data program that is accessible at NIPR government workstations designated by the COR. This program shall:

(a) Have a simple, easy-to-use interface.

(b) Include a file plan, directory, and complete user instructions, and where the user can select and open for display, copy, or print any record, instruction, plan, permit, or any other documentation created by the Contractor during the life of this contract (data not computer generated shall be referenced by the program).

3.2.6.4.2 Retain Master and Working Copies

The Contractor shall retain a master copy and working copy of all data submitted under this contract or transferred from previous contracts, unless stipulated otherwise elsewhere in this PWS. All data forwarded to the data repository shall be retainable, reproducible copies. Any loss of stored data due to a single IT systems failure shall not be excused.

3.2.7 Synchronized Pre-Deployment & Operational Tracker

Synchronized Pre-Deployment Operational Tracker (SPOT) is the central authoritative repository for applicable DoD contracts, Contractor personnel, and contract equipment as defined by the Congressional Acts and DoD regulations listed in the Compliance section below. SPOT delivers a standard, collaborative method for the management, tracking and visibility of Contractor personnel and contracts in support of contingencies, humanitarian assistance, disaster recovery operations, and other military operations or military exercises, when designated by the Combatant Commander. It provides a centralized means to identify the Department’s reliance and dependence on contracted capabilities. Additionally, SPOT offers fidelity and visibility of existing and previously contracted support, so that planners and others may consider current and historical data when developing future total force structure requirements as well as logistics and operational plans across all phases of operations.

3.2.7.1 Regulatory

DoD Instruction 3020.41, dated 20 Dec 11, incorporating change 1 April 11, 2017, Operational Contract Support (OCS): Requires that in applicable contingency operations, Contractor visibility and accountability shall be maintained through a common joint database, i.e., the SPOT or its successor. Additionally, it requires that all mandatory data must be entered into SPOT or its successor before a Contractor employee is permitted to deploy to or enter a military theater of operations. Contracting officers, through the terms of the contracts, shall require Contractors to enter by-name data before an employee’s deployment and to maintain and update the information in SPOT or its successor. Additionally, DFARS Clause 252.225-7040. Contractor Personnel Supporting U.S. Armed Forces Deployed outside the United States: Requires Contractor companies to use SPOT to enter all applicable data on contracted personnel before deployment and maintain data for all Contractor personnel that are authorized to accompany U.S. Armed Forces deployed outside the United States. It further requires Contractor personnel to have a SPOT-generated Letter of Authorization (LOA) signed by the Contracting Officer to process through a deployment center or to travel to, from, or within the designated operational area. The LOA identifies authorizations, privileges, or Government support that Contractor personnel are entitled to under the specific contract for which they are deployed.

3.2.7.2 Contractor Requirements

The Contractor shall appoint a Contractor Administrator (CA), that shall interact with the CO and COR and SPOT Government Agent to meet requirements as stipulated in regulatory documents.

3.2.8 Contractor Personnel Management

The Contractor shall establish and maintain all the management entities necessary to fulfill all requirements specified in this PWS. The Contractor shall provide the manpower to perform all operations and maintenance to the performance levels defined within this PWS at no additional cost to the Government.

3.2.8.1 Personnel Training

The Contractor shall be responsible for all training of its personnel at no additional cost to the Government.

3.2.8.1.1 Laws and Regulations

The Contractor shall train its personnel in applicable Federal, State, local, and DAF laws and regulations and requirements.

3.2.8.1.2 Certifications

The Contractor shall ensure personnel performing tasks requiring unique certifications and/or training (e.g. CSL, CST, Cyber Defense Infrastructure Support Specialist (CDISS)/ Information Systems Security Officer (ISSO) qualifications, Communications Security (COMSEC) Responsible Officer, HAZMAT certifications, flight line driver’s licenses, commercial driver’s licenses, Load Planners and Certifiers, Helicopter Load Riggers and Certifiers, tower climbing, etc.) are fully qualified and current.

3.2.8.1.3 New Equipment

Contractor will be afforded access to new equipment during installation/integration to facilitate familiarization and hands-on experience.

3.2.8.1.4 Opportune Training

The Contractor may take advantage of non-obligatory government provided training courses (e.g. Network Administrator, airlift load Rigger/Certifier, HAZMAT Training, etc.) in lieu of civilian courses, where allowed. The Government may assist in scheduling if reasonable to do so. The Contractor shall bear all costs for said training, if fees apply. However, the Government shall not waive the requirement for the Contractor to provide a properly trained workforce, 100% of the time. Awaiting a non-obligatory government provided course shall not be an excuse toward a lack of proper training/certifications.

3.2.8.2 Security Clearances

The Contractor shall hire and maintain a sufficient number of qualified personnel (including possession of security clearances, ranging from SECRET to TOP SECRET, with SCI and SAP access as required), to meet all the requirements of this contract. Task areas requiring personnel with TS, SCI, and/or SAP clearances include:

(a) Threat system operations of IADS components in SCI and/or SAP accredited facilities.

(b) Threat system operations performed with advanced IADS components, including other systems that will be procured as a part of the JPARC 2025 modernization program.

(c) Aircraft merge and debrief processes.

(d) CDS Systems.

(e) Program or Operations Managers.

(f) Computer system or network administrators that manage equipment inside SCI and/or SAP accredited facilities.

(g) Persons with TS or SAP cleared computer network accounts such as JWICS or CV2.

3.2.8.3 Employee Base Access

The Contractor site manager shall provide the host base Security Force’s Pass and ID division, through the CO, a list of personnel who require access to the host base for official business. The Contractor site manager will also identify personnel required to perform work in restricted areas, and ensure they receive and wear Restricted Area Badges (RAB) with the required credentials. All employees must meet all USAF, 354 FW, 3 WG, and deployed or TDY location base access requirements. Employment on this contract, or a subcontractor thereto will not be sufficient in and of itself to grant access to any Government facility. Having an employee(s) lose their base access privileges is not an acceptable reason for lack of performance of the contract. Reference Appendix 5 for more information.

3.2.8.4 Identification and Appearance

Contractor personnel shall present a clean and neat appearance. T-shirts, cut-off shorts, greasy and/or heavily stained outerwear will not be allowed. Contractor personnel shall wear nametags or security badges identifying them as Contractor employees while on duty. Security badges will be provided as GFE.

3.2.8.5 Personal Equipment

The Government will not provide any personal or safety gear for Contractor personnel.

3.2.8.6 Flight line Personnel

Contractor personnel operating on flight lines shall comply with local operating instructions for appropriate clothing attire (e.g., no hats; secured line badges; reflective vests/belts; etc.).

3.2.8.7 Lost, Stolen, or Mutilated Badges

Contractor shall report lost, and/or stolen badges to the RF-A and 354 RANS Security Manager(s) immediately if during the duty day, or if after hours, no later than the next duty day.

3.2.8.8 Scheduled and/or Short Notice Terminated Employees

Contractor shall secure badges from employees at the end of their last duty day if on a scheduled termination (e.g., layoff, retirement, etc.). If employees are terminated on short notice (i.e., fired), Contractor shall secure the employee’s badge prior to the end of the termination notice and immediate notify applicable Security Manager(s). Badges will be returned to the Security Manager(s) at the earliest convenience.

3.2.9 Vehicle Requirements in Performance of Contract

The Contractor shall provide all vehicles necessary in the performance of this PWS. See paragraph 3.23.1 and its subsequent paragraphs for amplifying statements of responsibility.

3.2.10 Radio Usage

The Contractor shall comply with all radio procedures as stipulated by the Government while accessing on-base restricted areas and JPARC range lands. Radios will be provided as GFE.

3.2.11 Gate, Key, and Lock Control

The Contractor shall establish and implement procedures that ensure keys, locks, and/or lock combinations issued to the Contractor by the…