Attachment 0002 - Performance Work Statement PWS.v3.pdf

Performance Work Statement (PWS) - Robot Logistic Support Center

Contents

PART 1 INTRODUCTION

1.1 4

1.2 Program Office Background

PART 2 GENERAL INFORMATION

2.1 5

2.2 6

2.3 6

2.4 6

2.4.1 Permanent Locations to be included in Task Order award

2.4.2 Temporary Duty (TDY) and Potential Locations

2.4.3 7

2.4.4 7

2.5 8

2.6 9

2.7 Travel

2.7.1 Travel Notification

2.7.2 10

2.8 11

2.8.1 11

2.9 Deployment Processing

2.9.1 Processing Requirements

2.10 14

2.10.1 CONUS

2.10.2 OCONUS

2.10.3 Overtime

2.10.4 16

2.11 16

2.12 16

2.13 16

2.13.1 Phase-in

2.13.2 Phase-out

2.14 18

2.15 19

2.16 19

2.16.1 CUI

2.16.2 Operations Security (OPSEC)

2.16.3 Security Classification Guide (SCG)

2.16.4 Common Access Card (CAC)/Key Control

2.16.5 Limitations on Use or Disclosure

2.17 Telework

2.17.1 Procedures and Authorization

2.17.2 Situational Telework

2.18 22

2.18.1 General CDRL Delivery Requirements

2.18.2 Classified Deliverables

2.18.3 Coversheet and Administrative Instructions

2.19 Government Property Incidental to Place of Performance

2.19.1 Provision and Definition

2.19.2 Contractor Responsibility & Liability

2.19.3 Acceptable Use

PART 3 REQUIREMENTS / SPECIFIC TASKS

3.0 GSA OASIS+

3.1 25

3.1.1 26

3.2 Task Area 1: Program Management Support

3.3 Task Area 2: Technical Support

3.3.1 System Engineering Support

3.3.2 Software Engineering Support

3.3.3 Radio Frequency (RF) Engineering Support

3.3.4 Technical and Risk Management Support

3.4 Task Area 3: Logistic Management

3.4.1 Program Logistic Support

3.4.2 Warehouse and General Supply activities

3.4.3 Web Based Supply Chain Management System Analysis

3.5 Task Area 4: Maintenance and Sustainment Support

3.6 Task Area 5: Material Fielding and Training

3.6.1 Fielding and training development

3.6.2 Fielding and Training Execution

3.6.3 New Equipment Training (NET)

3.6.4 Training Administration

PART 4 ADDITIONAL REQUIREMENTS

4.1 Task Order Management

4.1.1 44

4.1.2 44

4.1.3 44

4.1.4 45

4.2 Task Order Administration

4.2.1 45

4.2.2 45

4.2.3 45

4.2.4 46

4.2.5 46

4.2.6 46

4.2.7 Accident Reporting and Responsibilities

4.2.8 Mission Partner Identity, Credential And Access Management (MP-ICAM)

4.2.9 Access And General Protection/Security Policy And Procedures

4.2.10 Anti-Terrorism (AT) Awareness Training Requirement For Contractor Personnel Traveling Overseas

4.2.11 iWATCH Training

4.2.12 OPSEC Training Requirement

4.2.13 Information Assurance (IA)/Information Technology (IT) Training

4.2.14 Contractor Employees Who Require Access To Government Information Systems

4.2.15 Threat Awareness Reporting Program (TARP)

4.2.16 Army Information System (IS) Security Requirement

4.2.17 Cybersecurity Maturity Model Certification (CMMC)

4.2.18 Cyber Incident Monitoring

4.2.19 Cyber Incident Response

PART 1 INTRODUCTION

1.1 Executive Overview & Objectives: This non-personal services Performance Work Statement (PWS) establishes the requirements for Contractor provided services to the Robot Logistics Support Center (RLSC). The scope of this PWS consists of the necessary mechanical repair and operations support services for robots which involves maintenance, logistics, Systems Engineering and Technical Assistance (SETA), and program management support services required to accomplish the RLSC’s mission, equipping the Joint Warfighter with robotic warfighting capability. This mission includes deployment, systems engineering, integration, testing, fielding, sustainment, and improvement of unmanned systems, which forms the backbone of the future force. As a Multiple-Award (MA) Indefinite Delivery Indefinite Quantity (IDIQ) Task Order, this effort is subject to the General Services Administration (GSA) One Acquisition Solution for Integrated Services Plus (OASIS+) contract requirements. Performance under this Task Order will require the Contractor to provide qualified personnel, and may require supplies, transportation, tools, materials, supervision, and other items, and non-personal services, necessary to perform the services as defined in this PWS, except for those items incidental to the place of performance. Part 3 defines the specific tasks of this PWS.

1.2 Program Office Background:

The RLSC was established in 2014 to provide depot level maintenance repairs, sustainment, and training for all Army units and customers outside the Army on all robot models identified in section 3.1.1 below.

The RLSC is the Department of War's (DoW) sole provider of government repair and maintenance for its robotic fleet across all service branches. To successfully provide these services, the RLSC must maintain a fully staffed Technical, Management, and Logistics organization capable of responding to the current and future robotic systems needs of the Joint Warfighter, including program management, maintenance, repair, training, warehousing, logistics, and engineering support services to troops both within the Continental United States (CONUS) and Outside the Continental United States (OCONUS).

The RLSC is the only Program Management Office (PMO) that supports, sustains, recaps, and resets standard and non-standard robotic systems for all DoW services, and other customers such as National Guard, Coast Guard, and Rapid Equipment Force (REF). The RLSC mission has undergone sustained growth over the last decade in response to the continuous emergence of new customer support requirements.

PART 2 GENERAL INFORMATION

2.1 Base IDIQ Terms & Conditions: The Contractor shall adhere to all the terms and conditions set forth in the GSA OASIS+ base MA IDIQ contract. The terms and conditions in the GSA OASIS+ base MA IDIQ are in full force and effect for this effort, in addition to those included in this Task Order. The Contractor shall review sections C and H of the MA IDIQ, for potential updates to topics that may be unique to this PWS, such as Organizational Conflicts of Interest (OCI); Inherently Government Functions; non-personal services; Contractor Manpower Reporting (CMR); and Quality Assurance Surveillance.

2.2 Commerciality: The contracting officer has determined the services under this Task Order are non-commercial. As such, the Non-Commercial clauses in the Base OASIS+ IDIQ are applicable to this task order.

2.3 Period of Performance and Estimated Labor per Location: The Period of Performance for this Task Order shall be for a 30 day phase-in, one (1) base period of 11 months, and two (2) 12-month Option Periods, which may, in the Government’s sole discretion, be exercised separately, in whole or in part, by the Contracting Officer in one

(1) month or more increments Revolutionary (Federal Acquisition Regulation (FAR) Overhaul (RFO) FAR 52.217-9, Option to Extend the Term of the Contract).

2.4 Place of Performance: The work to be performed under this task order will be performed at locations, which are indicated below:

2.4.1 Permanent Locations to be included in Task Order award:

a. Bluegrass Station, KY

b. Ft. Belvoir, VA

c. Ft. Bragg, NC

d. Ft. Carson, CO

e. Ft. Hood, TX

f. Ft. Irwin, CA

g. Ft. Leonard Wood, MO (FLW)

h. Ft. Polk, LA

i. Joint Base Lewis-McChord (JBLM), WA

j. Kuwait

k. Selfridge Air National Guard Base, MI

l. Tyndall Airforce Base, FL

2.4.2 Temporary Duty (TDY) and Potential Locations

a. Ft. Bliss, TX

b. Ft. Benning, GA

c. Ft. Eustis, VA

d. Ft. Campbell, KY

e. Ft. Drum, NY

g. Central Command (CENTCOM) Area of Responsibility (AOR) (as defined at

URL: http://www.centcom.mil/AREA-OF-RESPONSIBILITY/)

h. United States Indo-Pacific Command (USINDOPACOM) AoR (as defined at

URL: https://www.pacom.mil/About-USINDOPACOM/Area-of-Responsibility-map/)

i. Warren, MI

j. Schofield Barracks, HI

k. Vilseck, Germany

l. Navy Explosive Ordnance Disposal (EOD) Group One, San Diego, CA

m. Navy EOD Group Two, Virginia Beach, VA

There could be additional CONUS and OCONUS TDY locations as identified to support mission requirements.

2.4.3 Site Requirements: Most of the work to be performed must occur on-site in the offices of the RLSC listed in section 2.4. If computer resources other than those provided by the Government are necessary to complete the requirements of the contract, the Contractor shall provide its personnel with these items. The Government will provide office space, office supplies, computer equipment, internet and web access, tools, telephone and reproductions facilities, as required. In assigning office space, special attention will be given to recognizing the nature of services performed by the Contractor. The Contractor has the responsibility to ensure safekeeping of Government equipment while in its employees’ possession. Any Government issued Property, Material or Equipment that is lost or damaged while in the Contractor’s possession, to include handling on a Government installation, will be reimbursed, at replacement value, by the Contractor within 30-days of receipt of a reimbursement request from the Contracting Officers Representative (COR) or Procurement Contracting Officer (PCO). If any Government issued Property, Material or Equipment is lost or damaged while in possession of or while being handled by a Contractor employee, the Contractor will be presumed responsible. The Contractor may submit rationale to the COR if the Contractor believes it was not responsible for the loss or damage. Unless the Government explicitly advises the Contractor, it was not at fault, the Contractor shall be liable for the loss. Section 2.4.3 shall be considered as otherwise provided in the contract as referenced in RFO FAR 52.245-1(h)(1).

2.4.4 Staffing: The Contractor shall, throughout the entire period of performance, provide a sufficient number of qualified employees to perform all tasks identified in this http://www.centcom.mil/AREA-OF-RESPONSIBILITY/) https://www.pacom.mil/About-USINDOPACOM/Area-of-Responsibility-map/) https://www.pacom.mil/About-USINDOPACOM/Area-of-Responsibility-map/) https://www.pacom.mil/About-USINDOPACOM/Area-of-Responsibility-map/)

PWS. All employees assigned to this effort shall meet the minimum labor-category qualifications established in the Attachment 0001 – Government Format Pricing Model (GFPM), Minimum Qualifications tab.

The Government estimates an annual requirement of 45 to 65 full-time-equivalent (FTE) positions. This estimate is provided for planning purposes only and does not constitute a minimum or maximum staffing commitment. Actual staffing requirements may increase or decrease at any time based on Government needs.

As RLSC customer requirements change, the Government may direct increases or decreases in staffing levels. Upon issuance of the Task Order award or a modification that changes staffing requirements, the Contractor shall adjust its staffing and fully implement the required changes within 30 calendar days.

The Contractor shall notify the COR and the PCO, in writing, of any technical, financial, personnel, or managerial issues that may affect performance. Such notification does not relieve the Contractor of any performance obligations under this Task Order.

Any deviation from, or relief of, the requirements of this PWS must be authorized in writing by the PCO. Any such relief shall apply only for the duration and to the extent expressly stated in the PCO’s written authorization.

2.5 Vehicles and Insurance: Usage of Interagency Fleet Management System Vehicles, Government Leased Vehicles, Government Vehicles, or Government transportation equipment may be required under this Task Order. The Contractor shall obtain insurance, in the minimum amounts specified below, and shall maintain the insurance for the duration of performance under this Task Order, in accordance with (IAW) RFO FAR 52.228-5, Insurance Work on a Government Installation and RFO FAR 52.228-8, Liability and Insurance Leased Motor Vehicles. This shall be charged as an allowable expense under Other Direct Costs (ODCs).

a. Workers’ compensation and employers’ liability. The Contractor shall provide employers with liability insurance of at least $200,000, except in States with exclusive or monopolistic funds that do not permit workers’ compensation to be written by private carries per RFO FAR 28.307-2.

b. General Liability. The Contractor shall provide bodily injury liability insurance, written on the comprehensive form of the policy, of at least $500,000 per occurrence.

c. Automobile Liability. The Contractor shall provide automobile liability insurance, written on the comprehensive form of the policy. The policy shall provide and maintain insurance covering the Contractor’s liabilities as stated in RFO FAR 52.228-8.

2.6 Driver Certification and Insurance. The provisions of Army Regulation (AR) 600-55, Chapters 2-1thorugh 2-7, apply to this Task Order. Contract employees shall be certified at the Contractor’s expense, as being fully qualified to operate the vehicles/equipment to which they are assigned. The Contractor shall provide written certification to the COR for all qualified and certified individuals performing work under this Task Order to operate Interagency Fleet Management System Vehicles, Government Leased Vehicles, Government Vehicles, or Government transportation equipment by location. Certification requirements may vary based on the location of performance. The Contractor shall comply with the certification requirements for each location of performance listed in Section 2.4. The Contractor shall verify local certification requirements with the transportation office at each place of performance. The Contractor shall ensure required insurance is obtained IAW RFO FAR 52.228-5. The Contractor shall make these certifications available to the COR(s) or PCO upon request, within one (1) business day of the Government's request.

2.7 Travel

The Contractor personnel may be required to travel during performance of this Task Order and perform services, for example, but not limited to, meetings and conferences, at a TDY location which may be at CONUS or OCONUS. The Contractor is responsible for arranging all CONUS and OCONUS transportation. All travel performed under this contract shall be IAW the Joint Travel Regulation (JTR) and RFO FAR 31.205-46. The Contractor shall obtain written authorization from the COR prior to any travel. The services performed while at the TDY location shall be billed at the established rates for the principal duty location. Travel shall not be authorized for the Contractor personnel to participate in non-billable services nor commute to their place of performance.

2.7.1 Travel Notification.

The Government Office will request for the Contractor’s employees to travel. The Contractor shall initiate a request for Travel Authorization utilizing a Government approved

Travel Authorization Form. The travel authorization requires notification by the Contractor to the COR, at least 21 calendar days prior to the start date of the CONUS travel and 45 calendar days prior to the start date of the OCONUS travel. The Contractor’s notification shall, at a minimum, include the following: justification on why the travel is needed, supporting documentation showing the detailed calculation of each travel cost element, and assurance that there are sufficient funds on the respective Contract Line-Item Number (CLIN) for each travel request. The COR’s written approval/authorization to the Contractor is required prior to making arrangements for the actual travel. After receiving the COR’s approval/authorization, if any travel cost element has increased; the Contractor shall immediately notify the COR of the increase, verify there are sufficient funds on the respective CLIN, and obtain the COR’s written approval/authorization for the increased cost prior to making final travel arrangements. Any allowable and reasonable increase in estimated costs that occur during the travel shall be communicated to the COR within 5 calendar days of knowing of the price increase, but approval is not required prior to incurring those costs.

2.7.1.1 For allowable reimbursable expenses, the Contractor shall submit, as a minimum, receipts, Privately Owned Vehicle (POV) mileage log, etc. These documents shall be submitted with the travel invoice with email notification to the COR.

2.7.2 Travel Arrangements and Joint Travel Regulations. Travel arrangements, including, but not limited to, lodging, transportation, and car rental accommodations, shall be the responsibility of the Contractor or its travel office. The Contractor will be authorized travel expenses in compliance with the provisions of the JTR with no profit or fee and subject to the limitation of funds specified in this contract and IAW RFO FAR 31.205-46, Travel Costs. Request for approval of costs in excess of maximum per diem rates, IAW the procedures contained in RFO FAR 31.205-46(a)(3), must be submitted to the COR for final approval prior to commencement of travel arrangements. The JTR is available at https://www.defensetravel.dod.mil/site/travelreg.cfm .

2.7.3 Trip/Travel Report. A Trip/Travel Report for each trip is required and must be submitted by the traveling employee IAW Contract Data Requirements List (CDRL) A006 – Trip/Travel Report. In addition to the requirements stated in CDRL A006, the Travel Report shall include the traveler’s Labor Category and CLIN/Title, Travel CLIN, travel destinations.

The Contractor shall submit travel cost vouchers to the COR for approval prior to submitting for payment.

https://www.defensetravel.dod.mil/site/travelreg.cfm

2.7.4 Travel Requirements for OCONUS. A valid U.S. passport is required for all personnel;

a visa may be required for personnel traveling to OCONUS locations. Any Contractor personnel traveling OCONUS shall be required to take appropriate Government provided OCONUS security / anti-terrorism training. In addition, the Contractor personnel shall enroll and complete all requirements as directed by the Project Manager (PM), Autonomous Robotic Capabilities (ARC) Security Manager.

2.7.5 Local Travel. For all Contractor employees, there shall be no reimbursement for local travel in and around the Contractor employees’ place of performance within a 50-mile radius.

2.8 Personnel Support/Letter of Authorization (LOA)

Every deploying Contractor employee must obtain a Common Access Card (CAC) and a letter of authorization (LOA) from the Synchronized Pre-deployment Operational Tracker (SPOT) system, prior to deploying to OCONUS locations. The Contractor shall input information to enable the Government to develop an LOA containing all the information needed to request a Call Forward, Individual Replacement Deployment Operation (IRDO) request, and data to input information into Special Projects Office (SPO) Tracker for Assistant Secretary of the Army for Acquisition, Logistics, and Technology (ASA (ALT)). The Contractor shall provide transportation for its personnel from point of origin to the IRDO site and return. The Contractor may only submit one (1) round trip (from employee's home residence to IRDO and return) per deployment to the COR for approval.

The COR will validate each Contractor request for an LOA. The PCO will, if appropriate, approve the LOA for each deploying Contractor employee in the SPOT system authorizing the following Government furnished Contractor support privileges, on an as available basis: meals, billeting, Resuscitative Care (emergency medical care, emergency dental care), use of Army Post Office/Fleet Post Office (APO/FPO), and access to base exchange, commissary, on-post bank, morale and welfare activities, and available chaplains. The Contractor shall use the SPOT database before traveling to IRDO for processing.

2.8.1 Documentation: Contractor personnel must possess appropriate documentation (i.e. passports, orders, and visa) prior to deployment to enter the task areas and perform this mission.

2.8.1.1 Contractor employees are not authorized to carry or possess a Government Furnished or personally owned weapon for self-defense purposes in the AOR.

2.8.1.2 When and if entrance into a war zone area is required, the Government will immediately notify the Contractor.

2.8.1.3 The Contractor, at its own expense, may rotate or replace personnel in OCONUS locations provided the rotating employees go through the CONUS Replacement Center (CRC) at Ft. Bliss, TX and complete all CRC required Theater Specific Individual Readiness Training (TSIRT), medical training, obtain a CAC through the Contractor Verification System (CVS), and have a valid LOA in the SPOT system. If the Contractor rotates or replaces personnel, there shall be no break in support to the mission under the PWS.

2.8.1.4 Personnel deployed to OCONUS locations shall be entitled to one (1) rest and relaxation (R&R) period after having worked for a period of ninety (90) consecutive calendar days within 12-months of continuous service. This R&R period shall not exceed twenty-one

(21) consecutive calendar days. The time for R&R begins when the employee leaves or is considered in a non-working status and ends when they return to base or a working status.

The Government will only reimburse for airfare not to exceed (NTE) $4,000.00 (USD)/trip.

Hourly wages or per diem are not allowable costs for R&R. (JTR:

http://www.defensetravel.dod.mil/site/travelreg.cfm). The Contractor shall ensure there is no break in support while the employee is within their R&R period.

2.9 Deployment Processing

Contractor personnel deploying in support of a Combatant Commander or a declared War Zone must attend CRC at Ft. Bliss, TX for deployment processing prior to deployment.

2.9.1 Processing Requirements

2.9.1.1 CRC is a six (6) day process, starting on Sunday and ending the following Friday. The Contractor shall be responsible for arriving on Saturday, the day before CRC starts, to be present at the beginning of training Sunday morning. The Contractor shall be responsible to stay on Ft. Bliss at the CRC provided billeting.

2.9.1.2 The Contractor shall coordinate all CRC enrollments with the COR. The COR will be responsible for staffing a Tank-automotive and Armaments Command (TACOM) G3 http://www.defensetravel.dod.mil/site/travelreg.cfm

Deployment Call Forward Request with the RLSC’s chain of command, to include a CRC reservation request.

2.9.1.3 Contractor personnel attending CRC must bring a copy of their valid medical and dental records for the deployment period (Note: Physicals are valid for 1 year; Medical Validations are valid for 30-days).

2.9.1.4 The Contractor shall pay for shots, physicals, and any other needed medical evaluations required for its designated employees to be medically cleared for deployment.

The Contractor shall be prepared to complete any additional medical requirements identified during the CRC medical clearance process at a non-military facility if needed. All medical requirements can be found on the CRC website.

2.9.1.5 If the Contractor is deploying personnel hereunder who have deployed through CRC before, such personnel shall bring all previously issued equipment (examples:

Kevlar vest, Kevlar helmets, and sleeping bags) with them when they report to CRC. If the Contractor personnel do not have the equipment issued by CRC from prior deployments under this Task Order, the Contractor shall be held responsible for any previously issued equipment before new equipment is issued.

2.9.1.6 The CRC website (https://home.army.mil/bliss/units-tenants/crc) provides the most up to date policies and requirements. The Fort Bliss Central Issued Facilities (CIF) will not reissue Personal Protection Equipment (PPE). If the Contractor employee was issued equipment/gear from a previous deployment, they are required to bring it with them, no matter what base/installation issued or what company the employee was with at the time; a Contract employee cannot deploy without it. Contract Employees are required to out-process through the CRC and turn-in equipment IAW Department of Defense Instruction (DODI) 3020.41, pg. 26. Contract companies must enforce this requirement and refrain from allowing their employees to bypass the CRC out-processing requirements.

At the conclusion of the contract, if there are any missing issued equipment/gear from a deployment, the Contractor is responsible for paying for the Government for the missing equipment/gear. The Contractor shall bring up any outstanding questions or issues due to this policy at the Start of Work Meeting or prior to deployment of personnel. At any point during the performance of work on this Task Order, the Contractor shall notify the COR in writing if there are any issues or violations of DODI 3020.41 requirements.

2.9.1.7 The Government will provide roundtrip transportation to and from AOR as necessary to get the Contractor employee into the AOR for contract performance and https://home.army.mil/bliss/units-tenants/crc) return the Contractor employee to CONUS at the conclusion of the Contractor employee(s) deployment period, at the conclusion of out-processing at the CRC. The Government will not provide transportation for R&R or any other purpose. If for any reason an employee must be removed from the AOR prior to the end of the deployment period, the employee will be responsible for all expenses incurred during return trip to home station. The Contractor shall maintain staffing levels and replace Contractor employees at the AOR, as required to ensure no break in service, at no additional cost to the Government. Excess baggage is only authorized consistent with military travel policies in effect. If subsistence changes during deployment (e.g. the Combatant Commander or subordinate Commander changes the authorizations), the Contractor shall notify the PCO, who will evaluate the notice and determine if any contractual action is required. Reimbursable emergency medical services are billable to the DBA Insurance carrier. Therefore, each LOA shall include the policy number, address, and point of contact (POC) information for the DBA insurance carrier.

2.9.1.8 Contractors who deploy to and mainly work out of Kuwait and Germany are not permitted to be housed on Government facilities. Contractor employees shall be responsible for providing their own housing expenses and are not allowed to invoice for additional costs. If the Contractor is traveling through Kuwait to another final deployment location, Government housing will be provided. If a Contractor is traveling to Kuwait or Germany for TDY, Government housing will not be provided; therefore, the Contractor shall provide housing at their own expense.

2.9.1.9 Contractors traveling to a declared War Zone are required to be housed in Government facilities. Therefore, Contractors shall not be allowed to invoice for additional housing expenses.

2.10 Hours of Operations:

For Contractors in CONUS or OCONUS, only actual hours worked (productive hours) shall be billed to the Task Order; those hours not worked (non-productive hours) shall not be billed to the Task Order.

2.10.1 CONUS: Unless additional hours during the workday are coordinated in advance and approved in writing by the COR, the Contractor is responsible for conducting business, no more than 10 work hours per day, 40 hours per work week, between the core hours of 06:00 AM (0600) to 06:00 PM (1800), Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Lunch and union time are not considered productive times, which are not billable. If the hours required in a billing period cannot be fulfilled because of a Government created circumstance, the Contractor, COR, and PCO will discuss an alternate billing arrangement on a case-by-case basis. The Contractor must always maintain an adequate workforce for the performance of all tasks defined within this PWS when the Government facility is not closed. Upon mutual agreement of the COR and the Contractor, Contractor personnel may shift work hours from the Monday to Friday schedule to weekends to support Reserve Units who are drilling or for other units that may conduct training in such periods. Any such shift will be hour-for-hour, meaning any hour worked on the weekend would be offset by a corresponding reduction during the Monday through Friday period. There is no change to the labor rates for work performed during weekend periods, unless such work is covered by Section 2.10.3 of the

PWS.

2.10.2 OCONUS: For Contractors serving OCONUS in the CENTCOM AOR (e.g. Kuwait) a standard workday is 8 hours with a standard work week consisting of six (6) days, Saturday

- Thursday. Unless agreed upon in advance in writing, between the Contractor and the PCO, Contractors serving OCONUS in other AORs (e.g. European Command (EUCOM), USINDOPACOM), a standard workweek will consist of 40 hours, 8 hours per day, 5 days per week (except as provided by section 2.8.1.4, above), 52 weeks per year, with the possibility of overtime for personnel for a maximum work schedule of 12 hours per day, 7 days per week, 52 weeks per year to include holidays and weekends, based on mission requirements. Lunch breaks shall be unpaid and shall not be part of the 8-hour workday; the Contractor shall not bill the Government for any lunch periods. Contractor employees working OCONUS (excluding Alaska and Hawaii), must report to their place of performance on Federal Holidays, unless otherwise notified or agreed upon between the Contractor and COR.

2.10.3 Overtime: The Contractor shall request overtime in writing, in advance, to the COR for routing to the PCO. If approved, PCO will provide written approval IAW RFO FAR 22.104-2. Overtime requests shall include the following information: place(s) where overtime will be performed, date(s) when overtime will be performed, number of employees that require overtime, overtime breakdown by employee, total number of overtime hours requested, and justification for the overtime. The Contractor shall verify sufficient funds are available on the applicable Task Order CLIN to cover the overtime hours/cost prior to submission of the overtime request. The overtime rate shall be 1.5 times the hourly rate listed in Attachment 0001 – GFPM. In accordance with CDRL A001 (Monthly

Status Reports), the Contractor shall deliver the actual overtime hours worked to the COR for verification upon completion of the overtime work.

2.10.4 OCONUS Uplifts: All OCONUS uplifts, including hazard pay, danger pay, hardship pay, and Defense Base Act (DBA) insurance, will be invoiced as an ODC. Uplifts will be reimbursed on a cost no fee basis.

2.11 Contracting Officer Representative:

The COR will monitor all technical aspects of the Task Order and assist in contract administration. The COR is authorized to perform IAW with the COR appointment letter.

The COR is not authorized to direct any changes to the contract. If the Contractor believes an out-of-scope change has been directed, they shall notify the PCO in writing immediately and not proceed with this work until written authorization is received from the PCO.

2.12 Start of Work Meeting (SOWM):

The Contractor shall host a SOWM at the RLSC Facility, Selfridge Air National Guard Base (SANGB) with its leadership, RLSC Leadership, the COR and the PCO, no later than 15 calendar days after Task Order award. The purpose of the SOWM is to discuss and clarify the Government’s expectations for performance during the effort covered by this PWS, meet with the Contractor's program team, and align the contractor and Government teams. The Contractor shall present key program objectives and risks, provide an overview of its approach, and present key elements of the contract. The Contractor shall outline how all tasks will be accomplished at each location, discuss any issues regarding completing all assigned tasks, and provide mitigation steps to reduce risk. The Contractor shall be prepared to review the status of the Phase-In Plan at the SOWM. A meeting agenda, briefing material, and meeting minutes shall be delivered, IAW CDRL A002 – Meeting Agenda, CDRL A003 - Briefing Material, and CDRL A004 – Meeting Minutes.

2.13 Phase-in/Phase-out:

To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall provide a phase-in and phase-out period as follows:

2.13.1 Phase-in:

The duration of the Phase-In period shall last no more than 30 calendar days.

2.13.1.1 The Phase-In Plan shall be delivered IAW CDRL A008 – (Phased Support Plan) Phase-In Transition Plan. The plan shall describe the steps the Contractor will take and the processes it will use to be prepared to assume complete responsibility for performance of the services cited in the PWS at the end of the Phase-In period. These procedures shall include a detailed milestone chart and narrative describing the chronological sequence of events that will be accomplished during phase-in. The Contractor shall not bill for labor hours or ODCs during the Phase-In period as it is Firm-Fixed-Price. The Contractor may obtain Seniority data of the incumbent during this time, if requested and if made available, through the COR.

2.13.1.2 Right of First Refusal (ROFR).

To ensure a smooth transition during the Phase-In period, the Contractor shall provide ROFR of employment to the current workforce to remain after the transition.

2.13.1.3 At time of award, the PCO will provide the Contractor with a list of all personnel who perform(ed) services on the predecessor contract, and who may be adversely affected or separated because of the issuance of this Task Order. The Contractor, and its subcontractors, shall give such personnel the ROFR for employment openings under this Task Order for positions in which they are qualified.

2.13.1.4 Automatic Waiver of Education/Certification and/or Experience.

If contract personnel performing services in an equivalent labor category on a predecessor contract would otherwise be displaced under this Task Order because they do not meet the Minimum Qualifications as identified in the Attachment 0001, GFPM, Minimum Qualifications tab, the Government waives the minimum qualifications for the personnel as long as they continue to occupy the same labor category.

2.13.1.5 The Contractor shall give predecessor contract personnel a minimum of five

(5) business days to respond to the ROFR.

2.13.1.6 The Contractor shall update and deliver the Government’s list of predecessor employees provided, IAW CDRL A007 – Personnel Report (Staffing Plan). The updated list shall include:

• Employee name

• Service Contract Act (SCA) or Standard Occupational Classification (SOC) labor category

• Prime or subcontractor under predecessor

• Current CAC expiration date

• Primary work site

• Job title

• Incumbent status (Retained/Declined)

• Type of security investigation on file

• Security Officer POC under the new Task Order

If an incumbent declines the job offer, the submission shall also identify the Contractor’s plan to fill the vacancy. The Contractor shall provide weekly updates to CDRL A007 - Staffing Plan until all positions are successfully filled.

2.13.1.7 The Contractor shall review CDRL A008 - Phase-in Transition Plan and Government list of predecessor contract employees at the SOWM.

2.13.2 Phase-out: Prior to the completion of this Task Order (to include option periods), an observation period shall occur to permit management personnel of an incoming workforce to observe operations and performance methods of the incumbent Contractor.

This allows for orderly turnover of facilities, equipment, and records and ensures continuity of service. The Contractor shall not defer any requirements for the purpose of avoiding responsibility or of transferring such responsibility to the succeeding Contractor. The Contractor shall fully cooperate with the succeeding Contractor and the Government.

2.13.2.1 Phase-Out Plan: The Contractor shall establish and implement plans for an orderly phase-out of the contracted operations nearing the expiration of this Task Order, delivered IAW CDRL A009 – Phase-Out Transition Plan.

2.13.2.2 IAW CDRL A009 – Phase-Out Transition Plan, the Contractor shall provide the PCO with a certified list of all service employees who worked during the final six months of contract performance. This list must be submitted at least 60 business days before expiration of this Task Order and must include each employee's name and original anniversary date of employment. Should any workforce changes occur after this submission, the Contractor must provide an updated list—including any employee separation dates—no later than 10 days before the Task Order has concluded. The PCO will provide the final list to the successor Contractor upon award of the follow-on contract, in accordance with the Privacy Act 5 U.S.C. 552a.

2.14 Other Direct Costs (ODCs): To the maximum extent possible, all anticipated ODCs associated with performance shall have an established Task Order price. ODCs must not be the primary purpose of the Task Order. All ODCs above $2,000.00 shall be approved and communicated in writing by the COR prior to expenditure.

As part of each ODC request above $2,000.00, the Contractor shall summarize the steps it has taken to solicit, evaluate, and price the proposed purchase; summary shall be sufficient for the COR to verify the fairness and reasonableness of the proposed price via email.

2.15 Quality Control Plan (QCP):

The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS.

2.15.1 The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor shall provide description of the plan outlining the method of inspection at the SOWM. A formal QCP shall be delivered IAW CDRL A005 - Scientific and Technical Reports (Quality Control Plan), that includes methods for identifying and preventing defects in the quality of services performed.

2.15.2 The Contractor’s QCP shall explain the manner in which the Contractor will ensure all Task Order requirements are being accomplished IAW the terms of this Task Order. A sustaining focus throughout the QCP shall be the attainment of continuous quality improvement. The Contractor’s QCP shall emphasize deficiency prevention over deficiency detection.

2.15.3 The QCP shall address, at a minimum the following: inspection program, deficiency identification (verbal corrective action log, written corrective action log), deficiency correction, surveillance methods, and a customer complaint program.

2.16 Security Requirements: All Contractor personnel must possess a SECRET clearance. Any delays in obtaining a SECRET clearance shall not be an excused delay in contract performance. The Contractor shall be responsible for considering SECRET clearance processing times when staffing this contract for performance. Contractor personnel possessing an Interim-SECRET security clearance may perform tasks under this Task Order only after receiving prior written authorization from the PCO. Such authorizations may only be issued by the PCO on a case-by-case basis. Each Contractor employee assigned to perform tasks under this Task Order must maintain the required SECRET clearance during the period of performance to access Government databases and Local Area Network IAW AR 25-2 and AR 380-67. The Contractor shall be responsible for handling and safeguarding both classified and Controlled Unclassified Information (CUI) in support of this contract. The types of information considered CUI for the program are technical data and information marked CUI by the Government. When handling classified and CUI information, the Contractor shall adhere to the guidelines below, Attachment 0004

- Department of Defense (DD) Form 254, DoDM 5200.01- V4, AR 25-55, AR 25-2, AR 25-1, DoDI 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems, and AR 380-5 Army Information Security Program.

2.16.1 CUI: Contract employees will be required to maintain CUI at their Contractor location IAW AR 380-5.

2.16.2 Operations Security (OPSEC). The Contractor shall adhere to OPSEC guidelines and DoW and Army Regulations further identified in the DD 254 and its respective continuation sheets.

2.16.3 Security Classification Guide (SCG). Collateral classified information and CUI generated in support of this contract shall be classified and marked IAW the source material used or the governing SCG. The Program of Records’s applicable SCG is the governing SCG. In addition to the SCG, classified information shall also be protected IAW DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and the associated DD 254. CUI will be protected IAW the Government’s SCG, the OPSEC Plan, and additional guidance located in DD 254.

2.16.4 Common Access Card (CAC)/Key Control. The Contractor shall implement procedures to track and account for all keys/CACs issued to the Contractor by the Government. The Contractor shall immediately report the loss or misplacement of keys/CACs and shall also report any unauthorized use of Government-issued keys/CACs to the PCO. NOTE: All references for keys include CAC and key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control IAW AR 190-13. Such procedures shall include the return of Government issued keys/CACs by Contractor personnel no longer requiring access to secured areas.

2.16.4.1 The Contractor shall prohibit the use of Government issued keys by any persons other than the Contractor's authorized employees. The Contractor shall prohibit Contractor employees from permitting unauthorized personnel to enter designated work areas.

2.16.4.2 The Contractor is responsible for obtaining required identification cards, tags, and badges IAW AR 600-8-14.

2.16.4.3 The Contractor and subcontractor(s), if any, shall successfully complete a background security check of all personnel (SF-85P) requiring a CAC. Execution of SF-85P is a requirement for Contractor personnel to receive a CAC. This must be completed before a Contractor employee may perform tasks under this Task Order or have access to the Task Order performance location(s).

2.16.5 Limitations on Use or Disclosure: All information or data developed or received under this Task Order shall be protected IAW RFO DFARS 252.227-7994, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends. The Contractor shall not release any information or data to third parties without the express written approval of the PCO.

2.16.5.1 Contract documents shall be properly marked (classification markings and distribution statements) as applicable IAW AR 380-5.

2.16.5.2 Public Release Request: The Contractor shall screen all information submitted for determination of public release to ensure it is both unclassified and technically accurate. The Contractor shall provide a letter of transmittal certifying a screening was conducted and that the Contractor attests that the information is unclassified and technically accurate, to the best of the Contractor's knowledge. The Contractor shall not release program information outside of program channels until the Government review process is complete. The Contractor shall submit all requests for public release approval to the Government for review. The Government will, after appropriate review, either authorize or reject the request to disseminate Government information publicly. Note that authorization may be given contingent on specified changes being made to the material for which public release has been requested. The program requires 45 calendar days to process the request and render a decision. Requests for public release shall be sent electronically via encrypted email using cryptographic products that are National Institute for Standards and Technology/National Information Assurance Partnership (NIST/NIAP) approved or mail a Compact Disc (CD) or Digital Video Disc (DVD) using U.S. Postal First-Class mail.

2.17 Telework

2.17.1 Procedures and Authorization: Teleworking may be required when it is in the Government's best interest to accomplish the mission or may be permitted upon request with approval from the COR and Government site (office) lead. The Contractor's teleworking procedures must comply with the local site's teleworking procedures for regular telework or situational telework. Prior to authorizing telework for any employee(s), the Contractor shall ensure it has a signed certification from the requesting employee, which acknowledges that the employee 1) shall comply with the requiring Government Office’s Telework procedures and 2) shall have the required equipment and resources necessary to telework. The Contractor shall make these certifications available to the COR(s) or PCO upon request, within one (1) business day of the Government’s request. The Government will not assume operating costs associated with the teleworker using their personal residence as the alternate worksite, including home maintenance, insurance, utilities, phone lines, or internet.

2.17.2 Situational Telework. Situational telework is approved on a case-by-case basis where the hours worked are not part of a previously approved telework schedule.

Situational telework may occur continuously for a temporary specific period of time. All Contractor employees shall be capable of being ready (prepared) to situational telework at any time. Situational telework may be required by the Government or requested by the Contractor employee. The Government may initiate situational telework for, as an example but not limited to, a Government facility closure due to inclement weather. A Contractor employee who initiates situational telework must request COR approval and receive COR approval prior to situational telework.

2.18 Contract Data Requirements List (CDRL) Delivery

2.18.1 General CDRL Delivery Requirements

The Contractor shall deliver all data deliverables as specified in the CDRL, DD Form 1423, and IAW the specific requirements of the applicable Data Item Description (DID). Delivery shall be made to the COR and any additional distribution recipients denoted in Block 14 of the respective CDRL. Unless otherwise specified, electronic submission is preferred.

2.18.1.1 File Format: Unless otherwise explicitly directed in Block 16 (Remarks) of the respective CDRL or mandated by the applicable DID, all deliverables shall be submitted in a compatible Microsoft Office Suite format (e.g., Microsoft Word, Excel, or PowerPoint).

2.18.1.2 Transmission: Unclassified deliverables, to include those containing CUI, shall be transmitted electronically via secure, approved methods. Authorized methods include encrypted email (if within attachment size limits), DoD SAFE, or a designated Government-approved Impact Level 5 (IL5) collaborative portal.

2.18.1.3 Marking Requirements:

All CUI must be explicitly marked IAW DoDI 5200.48, "Controlled Unclassified Information (CUI)." The Contractor shall ensure appropriate Distribution Statements (e.g., Distribution Statement B, C, D, E, or F) are applied to the cover and title pages of all technical documents IAW DoDI 5230.24, "Distribution Statements on Technical Documents."

2.18.2 Classified Deliverables

2.18.2.1 DD Form 254 Compliance: The Contractor shall generate, handle, mark, and transmit all classified deliverables in strict adherence to the NISPOM and the Contract Security Classification Specification (DD Form 254) associated with this contract.

2.18.2.1 Transmission: Under no circumstances shall classified CDRL items be transmitted over unclassified networks or systems. Electronic delivery of classified material shall be executed exclusively via approved classified networks (e.g., SIPRNet or JWICS) as coordinated with the COR. Physical delivery must utilize approved courier methods IAW DoD Manual 5200.01, Volume 3 and Attachment 0004 – DD Form 254.

2.18.2.3 Classified Marking: Classified deliverables shall bear overall classification markings at the top and bottom of the outside of the front cover, the title page, the first page, and the outside of the back cover. All internal pages and individual paragraphs must be portion-marked IAW DoW classification standards.

2.18.3 Coversheet and Administrative Instructions

All CDRL submissions, regardless of their classification level, shall include a standardized administrative coversheet.

2.18.3.1 Coversheet Elements: The coversheet must prominently display the following data elements:

Contract Number and Task/Delivery Order Number (if applicable) CDRL Data Item Number (e.g., A001) Data Item Description (DID) Number CDRL Title / Report Title Date of Submission Reporting Period (e.g., 01 Jan 2026 - 31 Jan 2026) Contractor Name, Address, and CAGE Code Name and contact information of the document preparer Placement of Markings on Coversheet:

Any required security classification banner (e.g., SECRET), CUI designation banner, or Distribution Statement must be prominently displayed at the top and bottom of the coversheet.

For classified documents, the coversheet must also include the full classification authority block (Derived From, Declassify On).

2.19 Government Property Incidental to Place of Performance

2.19.1 Provision and Definition

The Government will provide workspace, facilities, and equipment incidental to the place of performance for Contractor personnel operating on a Government installation.

Incidental property includes, but is not limited to, office space, desks, chairs, telephones, standard desktop/laptop computers, warehouse equipment, and tools for use by the Contractor as part of contract performance at Government facilities. IAW RFO FAR 45.000(b)(5), these items are classified as property incidental to the place of performance and are not considered Government Furnished Property (GFP) subject to RFO FAR 52.245-

1. Government property is subject to policies and procedures IAW AR 710-4, Inventory Management – Property Accountability.

2.19.2 Contractor Responsibility & Liability

The Contractor shall ensure that its employees exercise reasonable care and proper use of all incidental…