Attachment 4 TO PWS - ATG GLOBAL MX - 06FEB2026.pdf

ENERGY AUTOMATION OPERATIONAL TECHNOLOGY SUSTAINMENT (EAOTS)

AUTOMATIC TANK GAUGING (ATG), INDEPENDENT ALARM SYSTEMS (IAS), AND

OVERFILL PROTECTION EQUIPMENT (OPE) GLOBAL SUPPORT

MAINTENANCE (MX) TASK ORDER (TO) PERFORMANCE WORK STATEMENT (PWS)

RFP # SP4706-26-R-0002

SECTION C-1: INTRODUCTION

1.0 Introduction

Compliant with the EATOS ATG, IAS, OPE Global Support IDIQ contract, the DLA OEA ATG/IAS/OPE program requires a Task Order (TO) for acquiring supplies and services to sustain, support, modify, and repair the various ATG, IAS, and OPE solutions deployed globally at the Defense Fuel Support Points (DFSPs). The ATG/IAS/OPE solutions are mission critical components for DLA Energy and must be maintained.

1.1 Purpose / Objectives

The purpose of this TO is to achieve the following objectives:

a. Acquire support services to successfully administer this TO and support the ATG/IAS/OPE program.

b. Acquire a combination of supplies and services to sustain, maintain, troubleshoot, and repair the ATG/IAS/OPE systems deployed globally, regardless of geographic location (i.e. within the Contiguous United States (CONUS) and Outside the Contiguous United States (OCONUS)).

SECTION C-2: SCOPE

2.0 Scope

To ensure the Government’s objectives for this TO are met, the contractor will need to provide supplies and services for administering the TO as well as centralized oversight of Complex CM and Site Support TOs assigned to the contractor. The contractor’s services under this TO will need to support, maintain, troubleshoot, and repair the ATG/IAS/OPE solutions deployed globally. The overall scope of supplies and services for this TO are defined at the IDIQ contract level, including the sites for the deployed ATG/IAS/OPE solutions. Reference Basic IDIQ PWS – Attachment # 1 - List of ATG-IAS-OPE Sites for additional details.

However, the following additional information is provided that is unique to this effort:

Successful performance of this TO will require the contractor to provide a wide variety of supplies and services. These supplies and services will be comprised of all the necessary support required to successfully execute the tasks described in this PWS including all personnel, equipment, materials, Maintenance Program Management (MPM), and activities necessary to

EAOTS ATG, IAS, & OPE GLOBAL SUPPORT MX TO PWS

sustain, maintain, troubleshoot, and repair all of the deployed ATG/IAS/OPE solutions deployed globally. Services rendered under this TO will require the contractor to possess expertise in sustaining, supporting, maintaining, troubleshooting, and repairing petroleum systems compliant with applicable codes, criteria, and federal, state, local and/or host nation regulations.

It is crucial that the contractor accounts for the large geographical disbursement (i.e. CONUS & OCONUS) of the DFSPs due to different military installations / areas of responsibility to perform the work described in this TO PWS. The contractor will also need to account for and provide any commercial / ancillary software necessary to render services (i.e. software products required to restore operability, interface, troubleshoot, configure, etc. the ATG/IAS/OPE solutions).

2.1 Work Breakdown Structure (WBS)

Execution of this TO is comprised of six (6) distinct parts as depicted in the graphic below and WBS. Detailed information on each of these parts of the ATG/IAS/OPE program are described within this TO PWS. To achieve the Government’s desired objective for the scoped work effort, the supplies and services provided by the contractor must (at a minimum) be rendered to complete the following:

Figure 1 – Work Breakdown Structure

3.

ATG/IAS/OPE Support MX

3.1 Task 1:

Transition In

3.2 Task 2: TO

Administrative Management

3.3 Task 3:

Preventative Maintenance

(PM)

3.4 Task 4:

Technical Support

3.5 Task 5:

Corrective Maintenance (CM)/Repair

3.6 Task 6:

Transistion Out

Work Breakdown Structure (WBS)

PWS # Description

3.0 ATG/IAS/OPE Global Support MX Requirements

3.1 Task 1: Transition In (IDIQ Task Area 1 – Administrative Support)

3.2 Task 2: Task Order (TO) Administrative Management (IDIQ Task Area 1 –

Administrative Support)

3.2.1 Subtask 2.1: Staffing Plan

3.2.2 Subtask 2.2: Post Award Conference

3.2.3 Subtask 2.3: Weekly Updates & Weekly Activity Report (WAR)

3.2.4 Subtask 2.4: Monthly Status Report (MSR)

3.2.5 Subtask 2.5: In Progress Review (IPR)

3.2.6 Subtask 2.6: Contractor Personnel Roster, Common Access Card (CAC), &

Alternate Token Report)

3.2.7 Subtask 2.7: Quarterly Inventory Report (QIR)

3.2.8 Subtask 2.8: Commercial Documents

3.3 Task 3: Preventive Maintenance (PM) (IDIQ Task Area 2 – Preventative

Maintenance Support)

3.3.1 Subtask 3.1: PM Planning & Coordination

3.3.2 Subtask 3.2: PM Travel

3.3.3 Subtask 3.3: PM Services

3.3.4 Subtask 3.4: PM Documentation

3.4 Task 4: Technical Support (IDIQ Task Area 3 – Technical Support)

3.4.1 Subtask 4.1: Technical Support Team Resources & Availability

3.4.2 Subtask 4.2: Technical Support Team Communications

3.4.3 Subtask 4.3: Technical Support Team Services

3.4.4 Subtask 4.4: Technical Support Team CM/Repair Service Planning and

Coordination

3.5 Task 5: Corrective Maintenance (CM)/Repair (IDIQ Task Area 4 – Corrective Maintenance (CM) / Repair Support)

3.5.1 Subtask 5.1: CM/Repair SNOW Case Prioritization

3.5.2 Subtask 5.2: CM/Repair Travel

3.5.3 Subtask 5.3: CM/Repair Services

3.5.4 Subtask 5.4: CM/Repair Documentation

3.6 Task 6: Transition Out (IDIQ Task Area 1 – Administrative Support)

Table 1 – Work Breakdown Structure

SECTION C-3: DESCRIPTION OF SUPPLIES AND SERVICES

3.0 Description of Supplies and Services - ATG/IAS/OPE Global Support MX Requirements

The contractor must provide adequate resources (i.e. competent, capable, professional, and qualified personnel with the necessary supplies) to manage, deliver, and ensure timely completion for:

3.1 Task 1: Transition In (CLIN 0001) (IDIQ Task Area 1 – Administrative Support)

If the awardee is NOT the incumbent identified in this PWS, the Government may require transition-in services for the contractor. All transition-in services rendered to complete this task will be performed on a Firm-Fixed-Price (FFP) basis. Contractor rendered services for this task will be documented within the Monthly Status Report (MSR) deliverable as described within this PWS. The Government Contracting Officer’s Representative (COR) will perform evaluation and formal inspection and acceptance of the contractor’s services in accordance with (IAW) the Quality Assurance Surveillance Plan (QASP).

To reduce the risks associated with contract performance, including decrements to productivity and/or possible negative impacts on additional services, the contractor will provide the necessary services to support a 90-calendar day transitional period. To ensure uninterrupted operations and successful TO performance, the contactor’s Key Personnel will need to be fully engaged in and ensure the successful transfer of services from third-party contractors. This transition-in period will utilize an iterative approach that will consist of:

a. Knowledge Transfer: During the transitional period the contractor will be expected to participate in knowledge (tacit and explicit) transfer activities working alongside existing third-party contractors. These knowledge transfer activities will include interactive working sessions between the existing and newly incoming contractor to ensure continuity of services and gain familiarity with tools, processes, and organizational assets.

b. Transfer Duties: During the transitional period the contractor will be required to review, understand, and accept the duties for Key Personnel, services, and all active ServiceNow (SNOW) cases for the program. The transfer of these duties will require the contractor to work alongside existing third-party contractors to fully understand these duties. As the transition-in period progresses, work will continue to be performed by current third-party contractors IAW the terms and conditions of separate Government contractual obligations until confirmation is obtained by the Government that all Key Personnel responsibilities, services, and SNOW cases have been successfully transferred. If any existing supplies (i.e. bench stock, Government Furnished Equipment (GFE), etc.) are transferred, the contactor will ensure they are accurately inventoried and accounted for. The contractor will promptly notify the COR in writing of any problems/issues preventing their ability to accept responsibilities for Key Personnel, services, and SNOW cases prior to confirmation of these activities being completed.

c. Confirmation: Once knowledge and duties transfer has been completed, the contractor will provide confirmation to the Government. The target date for the contractor’s acceptance of the responsibilities for Key Personnel, services, and SNOW cases as described in this PWS is no later than (NLT) 30 calendar days prior to the end of the transition period. This will allow the Government adequate time to address any transition problems/issues between the contractor and any third-party contractors before the end of the transition period. No later than fifteen (15) calendar days before the end of the transition period, the COR will meet with the contractor to ensure all concerns and issues have been addressed. At the contactor’s meeting with the COR, the contractor will submit a Transition-In Report to support Government oversight. The Transition-In Report will be utilized by the Government to confirm the contractor has formally accepted the responsibilities for Key Personnel, services, and SNOW cases from third party contactors. The contractor will be expected to have fully accepted responsibility for Key Personnel roles and successful performance of all work described throughout this PWS at the end of the 90-calendar day transition-out period.

3.1.1 Deliverable: Transition-In Report [CDRL A001]

a. Schedule: No later than (NLT) fifteen (15) days before the end of the transition period.

b. Content: At a minimum, the data product will include:

1. Parts Statuses for ATG/IAS/OPE program sustainment based upon region (i.e.

CONUS, Europe, Caribbean, etc.).

2. Open/Active Preventative Maintenance (PM), Corrective Maintenance (CM), and site support SNOW cases including the following information (for each case):

i. SNOW case #.

ii. Summary Description of work.

iii. SNOW case priority.

iv. Assigned technician / contractor personnel.

v. Status on work progress.

vi. Region of PM work (i.e. CONUS, OCONUS, etc.).

vii. Site/Location of work.

viii. Latest version(s) of Plan of Actions & Milestones (POAMs) for work completion.

ix. Any POAM extensions/deferments requested with basis of logic/reasoning for

Government review and approval.

3. Confirmation all existing services to perform PM, CM, and site support activities have been transitioned from the previous contractor and identification of any outstanding questions or concerns that are risks to successful performance.

c. Format: Electronic copies viewable using the latest version of Microsoft Office or

Adobe PDF

3.2 Task 2: Task Order Administrative Management (CLIN 0002) (IDIQ Task Area 1 – Administrative Support)

All TO Administrative Management services rendered to complete this task (including subtasks) will be performed on a FFP basis. Contractor services rendered for this task (including all subtasks) will be documented within the MSR deliverable as described within this PWS. The Government COR will perform evaluation and formal inspection and acceptance of the contractor’s services IAW the QASP.

To meet the Government’s objective of sustaining, maintaining, and administering the ATG/IAS/OPE systems the contractor will be required to provide a wide variety of administrative support services. These services will include centralized oversight of Complex CM or Site Support TOs assigned to the contractor. The services will also ensure all work performance on this TO is coordinated with supplies and services rendered at an acceptable level of quality and grade IAW the contractor’s Quality Control Plan (QCP). The contractor will ensure their records are well kept/maintained and be responsible for the planning, orchestrating, executing, and monitoring the movement/travel of resources (supplies and personnel) to the ATG/IAS/OPE solutions deployed globally in order to perform the services described in this PWS. The contractor’s administrative support services will ensure all general terms, conditions, and requirements described in this TO PWS are met. The contractor’s administrative support services will be expected to include all necessary activities to support Government oversight, evaluation, inspection, and acceptance of work performed on this TO.

To successfully render these services, the contractor will be required to assign a single point of contact (POC), also known as the Maintenance Program Manager (MPM), who will serve as the primary resource for coordination with the Government. The MPM will work closely with the Government Contracting Officer (KO), COR, and Technical Point of Contact (TPOC) to ensure all supplies and services are rendered at an acceptable level of quality and grade. The MPM will be Key Personnel on this TO. The contractor’s MPM will have the requisite authority for full control over company resources necessary for contract performance. As part of the contractor’s administrative support, the contractor will perform the following:

3.2.1 Subtask 2.1: Staffing Plan

The contractor must submit a Staffing Plan that describes the resources and organizational structure the contractor will use to perform the work described in this PWS. This description must provide details on the contractor’s organizational structure, methods to address staffing changes and training, and identification of labor categories and key personnel. The contractor’s Staffing Plan must be submitted as part of the Offeror's proposal and will be incorporated at time of award to serve as the initial baseline plan. A finalized version of the Staffing Plan must be delivered within ten (10) business days after completion of the post award conference described in this PWS. This version must align with the Offeror's proposed plan and incorporate any clarifications or revisions discussed with the Government prior to award. The contractor must subsequently update the Staffing Plan at least annually, or as significant changes to the contractor's management approach occur. The contractor must ensure the Staffing Plan does not contain Controlled Unclassified Information (CUI) including (but not limited to) Personally Identifiable Information (PII).

3.2.1.1 Deliverable: Staffing Plan – [CDRL A002]

a. Schedule:

1. Initial version submitted at time of contractor proposal to support evaluations for acceptability.

2. Final versions submitted to the Government within ten (10) business days after completion of the post award conference.

3. Updates made annually or as required throughout contract performance.

b. Content: The contractor’s Staffing Plan must clearly contain (at a minimum):

1. Organizational Structure: A summary description with applicable figures or charts demonstrating the proposed organizational structure to complete the tasks and requirements in this PWS. This includes identifying the logical hierarchy (including roles/responsibilities) and clear identification of the organizational placement for all Key Personnel.

2. Staff Changes and Training: The methods the Offeror will use to supplement resourcing if staff/personnel changes occur to ensure continuity of operations and successful work performance. This also will include description of how the Offeror will maintain training and applicable certifications for staff/personnel based upon the requirements described in this PWS.

3. TO Level Labor Identification: Identification of all labor categories/types (i.e. both key and non-key personnel) and subcontractors, vendors, or suppliers intended for use to perform the tasks described in this PWS. The Offeror must specify which tasks from the EAOTS ATG/IAS/OPE Global MX TO PWS will be performed by the prime contractor versus other entities.

4. TO Level Essential / Key Personnel: The resumes and applicable supporting documentation (including certifications) for all proposed Key Personnel identified in this PWS. The Offeror must ensure all resumes and applicable supporting documentation does not contain any Controlled Unclassified Information (CUI) including (but not limited to) Personally Identifiable Information (PII).

i. For each essential/key personnel labor category or position, identification of which individual(s) are anticipated to be a full-time, part-time, matrixed, or a split resource (i.e. not a full-time equivalent (FTE)/dedicated to the performance of work described in the PWS).

ii. The resumes of Key Personnel must provide a clear demonstration that the proposed resources meet or exceed the education, qualification, and experience requirements described in this PWS.

A. The Offeror must ensure that all Key Personnel possess eligibility for applicable personnel security clearance investigations and can obtain a Common Access Card (CAC).

iii. The Offeror must provide, along with resumes, Letters of Intent (LOI)/Letters of Commitment (LOC) confirming Key Personnel selection and availability immediately upon task order award.

A. The Government reserves the right to use any available information to evaluate Key Personnel, including (but not limited to) verification of proposed Key Personnel performance or availability from assignment on other Government contracts. The Government may contact references identified in Key Personnel resumes, query databases for certification validity, and inquire with end user representatives regarding the quality of Key Personnel experience and performance.

5. Additional Information: Any additional relevant information associated with the contractor’s Staffing Plan including (but not limited to) appendices, glossaries, definitions, enclosures, or attachments as applicable.

Adobe PDF.

3.2.2 Subtask 2.2: Post Award Conference

The contractor will be required to participate in a single and/or multi-day post award conference that is intended to serve as orientation for TO execution compliant with FAR 42.5. At a minimum, all Key Personnel identified in this PWS must attend the post award conference. The post award conference may be held virtually (i.e. video teleconference) or face-to-face or at a specific location designated by the Government. The post award conference will help both the Government and contractor to achieve a clear and mutual understanding of all contractual requirements as well as identify and resolve any potential problems before they arise during contract performance. The post award conference is not a substitute for the contractor’s full understanding of the work requirements at the time their proposal was submitted, nor is it to be used to alter the final agreement arrived at in any negotiations leading to contract award. As part of the contractor’s participation in the post award conference, the contractor will be expected to prepare and present an executive overview of their plan to manage the scope, schedule, and resources for the contract. An agenda for the post award conference will be provided to the contractor by the KO, COR, and/or TPOC before the conference date. The contractor will support the Government oversight of the post award conference by recording meeting minutes summarizing the events that transpired during the post award conference. All documentation generated by the contractor for the post award conference will be submitted to the COR/TPOC NLT ten (10) business days after the conclusion of the conference.

3.2.2.1 Deliverable: Post Award Conference Presentation & Meeting Minutes [CDRL A003]

a. Schedule: Within ten (10) business upon conclusion of the post award conference.

b. Content: As determined by COR/TPOC in collaboration with the contractor based upon the requirement.

3.2.3 Subtask 2.3: Weekly Updates and Weekly Activity Report (WAR)

To support Government oversight and monitoring of the contractor’s performance, the contractor will provide reoccurring weekly updates to the COR/TPOC. The purpose of the weekly update is to provide a means for an informal interchange between the Government and contractor during the execution of the contract. The weekly updates will occur on a continuous basis throughout the duration of the TO on a business day (i.e. Monday, Tuesday, Wednesday, Thursday, or Friday) that is mutually agreed upon by the contractor and the COR/TPOC. Weekly updates that are scheduled to occur on Federal Holidays as identified in this PWS will be rescheduled at the discretion of the COR/TPOC. The weekly update should be intentionally designed so that it is short in duration (no longer than one (1) hour) and will consist of the following elements:

a. Weekly Virtual Teleconference – The weekly teleconference will be scheduled by the contractor with the COR/TPOC and consist of a well-organized agenda to discuss topic(s) that will assist the Government with oversight and monitoring of the contractor’s performance. The contractor will develop the agenda for the weekly virtual teleconference in collaboration with the COR/TPOC and include all areas of Government concern as needed.

For example, the weekly virtual teleconference agenda should contain a summary review of all open/active SNOW cases within the ITSM solution assigned to the contractor. The weekly virtual teleconference should also review travel authorizations for upcoming services and SNOW cases to ensure smooth operations. During the weekly virtual teleconference, the Government will review work progress for the services rendered as described in this PWS as well as any major risks / issues identified that could be (or already is) an impediment or roadblock to successful contract performance. Additionally, during the weekly teleconference the contractor will be expected to identify SNOW cases in which services may exceed the Performance Standards identified in Section 7.2 of this PWS and request extension or deferment. Any requests for extension or deferment of SNOW cases must include justification stating the reasoning, basis, and logic for not achieving timely completion of the work. The Government will review the justification provided and decide if an extension/deferment is warranted. Extensions/deferments for the timely completion of services is NOT automatic and will be reviewed and authorized by the Government on a case-by-case basis. The contractor will take meeting minutes of the weekly virtual teleconference summarizing attendees, the discussions/conversations held, action items, assigned action officers, corrective actions, and associated due dates. The contractor’s meeting minutes from the weekly virtual teleconference will be provided to the COR/TPOC as part of the Weekly Activity Report (WAR).

b. Weekly Activity Report (WAR) – NLT two (2) business days after completion of the weekly virtual teleconference (preferably within the same Monday through Friday week of occurrence), the contractor will provide to the COR/TPOC a WAR. The WAR will be logically organized to support expeditious Government review (i.e. it should not be excessive in page count or information) and contain the contractor’s meeting minutes with any relevant data presented during the weekly virtual teleconference to support Government oversight of performance monitoring. This deliverable is expected to contain CUI data that is controlled technical information and must be marked and handled appropriately.

3.2.3.1 Deliverable: Weekly Activity Report (WAR) – CUI – [CDRL A004]

a. Schedule: NLT two (2) business days after completion of the weekly virtual teleconference.

b. Content: At a minimum, the following must be provided by the contractor in each WAR submission:

1. Executive summary of upcoming weekly activities, milestones, and achievements.

2. Meeting minutes of weekly virtual teleconference and action items, assigned action officers, and associated due dates.

3. A summary list of deliverables (i.e. tasks, subtasks, work packages, action items, etc.) that are:

i. Past due / behind schedule

ii. Recently completed (within the past week)

iii. Upcoming (planned to be completed in the next week)

4. Reports on all open/active SNOW cases assigned to the contractor:

i. The report’s data will contain (at a minimum) the following information:

A. SNOW case #

B. Summary Description of work C. Priority of SNOW case D. Region (i.e. CONUS, Caribbean, etc.)

E. Specific site/location of work F. Assigned contractor technician / personnel G. SNOW Case age (based upon Performance Standards described in Section

7.2 of this PWS) H. Brief summation of work progress status I. Projected work finish/completion date

1. At each WAR submittal, the contractor will clearly identify any changes to projected work finish/completion dates. Changes to the projected work finish/completion dates must include justification stating the reasoning, basis, and logic for the untimely rendering of services. The Government will review the contractor’s justification during the weekly teleconference and decide if an extension/deferment is warranted. Extensions/deferments for services rendered are NOT automatic and will be reviewed and authorized by the Government on a case-by-case basis.

J. For active site support SNOW cases the following additional information is required:

1. Month and year the site support TO was awarded

2. Month and year site support services started

3. Last PM date for specific site

ii. The data will be grouped by SNOW case types (i.e. PM, CM, Technical

Support, site support, etc.) and then by the following criteria:

A. All cases that are “Emergency” and “High” in Priority B. All newly assigned cases and cases aged between 0 and 29 calendar days C. All cases aged between 30 and 59 calendar days D. All cases aged between 60 and 89 calendar days E. All cases aged 90 calendar days or greater

5. Reports on all closed/completed SNOW cases since the last WAR submission:

i. The report’s data will contain (at a minimum) the following information:

A. SNOW case # B. Summary Description of work C. Priority of SNOW case D. Region (i.e. CONUS, Caribbean, etc.)

E. Specific site/location of work F. Total case age / duration (based upon assignment to contractor)

ii. The data will be grouped by SNOW case types (i.e. PM, CM, Technical

Support, site support, etc.).

6. A summary list of contractor travel organized by SNOW case types (i.e. PM, CM, site support, etc.) identifying:

i. SNOW Case #

ii. Travel location

iii. Travel dates (start and end)

iv. Name of contractor personnel assigned

7. Additional data identified in writing by the COR as necessary to support

Government oversight of contractor performance.

3.2.4 Subtask 2.4: Monthly Status Report (MSR)

To provide adequate documentation and support Government oversight, inspection, and acceptance of the supplies and services rendered, the contractor will provide reoccurring a Monthly Status Reports (MSR). The MSR will serve as formal documentation throughout the performance of the contract for Government inspection and acceptance on most supplies and services rendered by the contractor to meet the requirements identified in this PWS. The primary purpose of the MSR is to support Government surveillance, review, and evaluation of contractor work performance by providing status, update, and formal record on task, subtask, work effort, activity, and required data products/deliverables completion. The MSR intended to be a summation of the contractor’s preceding month’s supplies and services rendered and will need to contain information on contractor travel, financial expenditures, data/metrics on contract performance, action items, staff changes, and any significant risks or issues encountered during work performance.

The contractor will submit the first MSR to the Government within thirty (30) calendar days after contract award. Follow on MSRs will be provided by the contractor to the Government by no later than (NLT) the fifth (5th) business day of each month for the duration of the TO. Upon Government review of the MSR, the document will be formalized via signature of the contractor and Government to establish an auditable record of the supplies and services rendered for each month of contract performance. Finalized copies of each MSR must be distributed to the contractor and the COR/TPOC for retention.

The MSR must be submitted in the contractor’s design unless otherwise agreed upon between the contractor and the Government. The documentation must be provided in a digital format, viewable using the latest version of Microsoft Office or Adobe PDF. The contractor must ensure the MSR does not contain CUI.

3.2.4.1 Deliverable: Monthly Status Report (MSR) – [CDRL A005]

a. Schedule: Within thirty (30) calendar days after contract award and NLT the fifth (5th) business day of each month thereafter for the duration of contract performance.

b. Content: Each MSR submitted will contain the following:

1. Logical and methodical organization of all content such as a table of contents, page numbers, etc.

2. Clear and concise identification of the supplies and services rendered to the Government for the preceding calendar month including tasks, subtasks, Government reviews, milestones, action items, or required data deliverables completed compliant to this PWS.

3. Figures, graphics, and/or tables of current data/metrics from the last day of the calendar month identifying SNOW cases assigned to the contractor to perform the services described in this PWS. This data is intended to be a monthly roll up of the contractor WARs as described in this PWS to support Government oversight on the quality and timeliness of services rendered. The COR/TPOC may perform inspection (random or specific/targeted) on any SNOW case identified in the MSR to evaluate quality and timeliness of the contractor’s rendered services. SNOW cases determined by the COR/TPOC to be in non-conformance to quality and/or timeliness (for example, excessive in age and/or insufficiently supported by the contractor) may result in a performance evaluation below “Satisfactory” compliant to the Performance Standards described in this PWS. The contractor’s data/metrics is expected to include a monthly summation of all SNOW case data reported in the WARs as well as the following additional information:

i. Open Active SNOW cases:

A. Total # of new SNOW cases assigned to the contractor for the month grouped by type (i.e. PMs, CMs, Technical Support, and site support).

B. Total # of active SNOW cases assigned to the contractor at the time of

MSR submission.

C. Total # of SNOW cases for PMs currently behind schedule at the time of

MSR submission.

D. Total # of SNOW cases for CM/Repairs aged 31 calendar days or greater from approval to execute CM/Repair services.

E. Average cumulative age of SNOW cases grouped by type (i.e. rolling average age of open/active PMs, CMs, Technical Support and site support SNOW cases).

ii. Completed SNOW cases:

A. SNOW cases completed for the month by type (i.e. the total # of PMs, CMs, Technical Support and site support completed since last MSR submission).

B. Total # of SNOW cases completed during the PoP by type.

C. Total # of SNOW cases for PMs completed on time or ahead of schedule for the month.

D. Cumulative total # of SNOW cases completed during the PoP based upon region (i.e. CONUS, Europe, Caribbean, etc.).

E. Average cumulative age during the PoP of SNOW cases completed (i.e.

rolling average # of days to successfully complete PM, CM, Technical Support, and site support SNOW cases).

F. Monthly total # of SNOW cases resolved by Technical Support Team (i.e.

problem resolved remotely).

G. Cumulative % of SNOW cases resolved during the PoP by Technical Support Team (i.e. problem resolved remotely).

iii. Completed Site Support Projects SNOW cases: The contractor will provide a summary of all completed Site Support Project SNOW cases with the following information:

A. Total # of Site Support SNOW cases completed for the month/since last

MSR submission.

B. Cumulative list of Site Support SNOW cases completed during the PoP based upon region (i.e. CONUS, Europe, and Caribbean, etc.).

C. Cumulative average age of Site Support SNOW cases.

iv. Relevant contractor information justifying deferment/delay on the progress of

SNOW cases (regardless of status) to support Government analysis on the quality or timeliness of contractor performance.

v. Any additional SNOW case data identified by the COR as necessary to assist in Government oversight or contractor performance monitoring.

4. Description and supporting documentation (if necessary) of contractor travel completed in the preceding month and upcoming contractor travel.

5. Summary of all active risks or issues to contractor performance complaint with the

Government’s risk, issue, and opportunity management processes including:

i. All risks categorized by likelihood and consequence (i.e. High, Medium, Low)

ii. All issues are categorized by impact (i.e. High, Medium, Low)

iii. Mitigation / resolution strategies for each risk / issue with status of implementation.

6. Contract financial information (such as documentation identifying by funds expended and amounts remaining) for all CLINs.

i. Included in this financial information, the contractor must include summary cost expenditure data associated with CM/Repair services rendered including:

A. Monthly total labor costs incurred B. Monthly total supplies costs incurred C. Monthly total travel costs incurred D. Cumulative total labor costs E. Cumulative total supplies costs F. Cumulative total travel costs G. Funds remaining for CM/Repair services CLIN(s)

7. Any additional information or documentation necessary to support successful

Government surveillance (including identifying problem areas/issues requiring attention) and/or oversight.

8. A section reserved for the Government to provide input / feedback.

i. The COR will utilize this area/section in the MSR to provide formal comments to the contractor, document performance concerns, and identify the assigned monthly performance ratings for the contractor IAW the Performance Standards described in this PWS.

9. A signature page containing lines for:

i. Contractor Representative

A. The contractor will sign the MSR prior to its submission for Government review.

ii. Government Representative

A. The COR will review the MSR and if the deliverable is acceptable, provide input / feedback with assignment of monthly performance ratings.

The COR will sign the MSR deliverable and provide a copy of the document to the contractor. The contractor will provide a response to the Government within five (5) business days if they do not agree with the COR’s ratings as assigned. In the event of the contactor not agreeing with the COR’s ratings, the KO will review the contractor’s response and make the final rating determination

3.2.5 Subtask 2.5: In Progress Reviews (IPRs)

To meet the requirements described in this PWS, the contractor will need to participate in and provide administrative support services for IPRs on an as needed basis to assist with Government coordination, oversight, and surveillance of contractor work performance. Documentation generated for IPRs will be identified by the contractor and the Government as to its content and format at the time of IPR. All documentation generated to support IPRs will be submitted to the Government COR for inspection, acceptance, and retention on an as needed basis.

The purpose of the IPR is to provide a means for a formal exchange between the Government and contractor during the execution of the contract. IPRs will be conducted as required and during the IPR the KO and COR will appraise the contractor of how the Government views the contractor's performance. In exchange, the contractor will be expected to identify to the Government any issues, problems, roadblocks, impediments, etc. that are preventing successful performance. Topics best suited for IPRs include formal discussion on risks or issues discovered;

reoccurring updates on progress towards completing specific tasks, subtasks, work efforts, activities of Government or contractor concern; or other collaborative efforts that necessitate formal coordination. For example, if there is a specific contractor task requiring formal oversight or the Government has concerns regarding contractor performance, the IPR should be utilized to rapidly and effectively address those concerns. The Government or contractor may request to conduct an IPR at any point during contract performance but must do so in writing. IPRs should be infrequent and contain a pre-arranged, well-organized agenda to maximize their effectiveness.

IPRs may be conducted virtually or in person as appropriate. Documentation generated for IPRs will be identified by the contractor and the Government as to its content and format at the time of IPR. All documentation generated to support IPRs will be submitted to the Government COR for inspection, acceptance, and retention NLT five (5) business days after completion of each IPR.

Although IPRs will be conducted on an as-needed basis, to assist with planning the Government anticipates the total number of IPR occurrences to be approximately four (4) times in any given year of contract performance.

3.2.5.1 Deliverable: IPR Documentation [CDRL A006]

a. Schedule: NLT five (5) business days after completion of each IPR.

b. Content: As determined by COR/TPOC in collaboration with the contractor based upon the requirement.

3.2.6 Subtask 2.6: Contractor Personnel Roster, Common Access Card (CAC), & Alternate Tokens Report

To support Government monitoring of Government Property (GP), the contractor will be required to submit reoccurring reports identifying all employees working on the contract. This report will include all contractor personnel (regardless of whether Prime or Subcontractor). The report will also identify which contractor personnel have been issued CACs and/or alternate tokens for privileged access to the Government NE or CE. The contractor will provide at the time of each report submission confirmation the employees listed are still working on the contract and/or require CACs and alternate tokens. The report must note where changes have occurred (i.e. any additions or deletions) since the previous month at the time of each submission. Contract employees who already have a CAC or alternate token related to another DLA or DoD contract must be included in the monthly report. The contractor will note the issuing organization and the expiration date for all CACs and alternate tokens. The contractor will be responsible for notifying the KO and COR in writing, within 24 hours when any of their personnel are no longer working under the contract. At the time of contractor personnel departure/roll-off, the contractor will be responsible for ensuring (at no additional cost to the Government) the collection and turn-in of any CAC or alternate token issued to their personnel (regardless of whether Prime or Subcontractor). This deliverable is expected to contain CUI data that is general privacy/PII and must be marked and handled appropriately.

3.2.6.1 Deliverable: Contractor Personnel Roster, Common Access Card (CAC), & Alternate Tokens Report [CDRL A007]

a. Schedule: Submitted with MSR within thirty (30) calendar days after contract award and NLT the fifth (5th) business day of each month thereafter for the duration of contract performance.

b. Content: At a minimum the contractor Personnel Roster & CAC Report will include the following data:

1. For all contractor personnel (regardless of whether Prime or Subcontractor):

i. Full name (first, middle, and last)

ii. Roll-On Date

iii. DLAH 1728 Submission Date

iv. Roll-Off Date

2. For all contractor personnel (regardless of whether Prime or Subcontractor) who have been issued a CAC:

i. CAC/alternate token issuance date

ii. CAC/alternate token expiration date

iii. CAC/alternate token EDIPI #

iv. CAC/alternate token turn-in date

v. CAC/alternate token turn-in location

vi. Government POC for CAC/alternate token turn-in

3. An additional text field for notes/comments

3.2.7 Subtask 2.7: Quarterly Inventory Report (QIR)

The QIR is a continuously maintained list of all Government products and equipment deployed or utilized. The Government will provide an initial QIR as Government Furnished Information

(GFI) during the transition-in period as described in this PWS. After receipt of the initial QIR, the contractor will be expected to maintain the inventory, listing all deployed products and equipment throughout the duration performance. The QIR will need to be updated by the contractor as work is performed, and an updated version will be submitted to the Government on a reoccurring basis (i.e. every three (3) months/quarterly). The QIR will include information used by the Government to monitor and track deployed inventory, downtime, site/system locations, and system types. This deliverable is expected to contain CUI data that is controlled technical information and must be marked and handled appropriately.

3.2.7.1 Deliverable: Quarterly Inventory Report (QIR) – CUI – [CDRL A008]

a. Schedule: Quarterly (every three (3) months) after the start of contract performance and by NLT the last calendar day of month

b. Content: Data product will include an inventory list (separated by region such as CONUS, Europe, Caribbean, etc.) with the following information:

1. DODAAC

2. Site Name

3. Configuration Item Name

4. Configuration Item Description

5. Status

6. Part Number

7. Serial Number

8. Program

9. System

10. Manufacturer

11. Location/Floor

12. Last known PM date

13. System Type

14. Quantities

3.2.8 Subtask 2.8: Commercial Documents

The contractor will provide applicable commercial documentation for supplies rendered to support the ATG/IAS/OPE program throughout the performance of this TO. This commercial documentation is expected to include (but is not limited to) equipment manuals, publications, manufacturers' descriptive literature of cataloged products, equipment drawings, diagrams, performance and characteristic curves, catalog cuts, warranty periods, etc. to the Government for supplies rendered. All commercial documentation will be uploaded electronically into the Government NE as directed by the COR for retention and support of the ATG/IAS/OPE program. The contractor will submit all commercial documents to the Government NLT ten (10) business days after identification of each requirement.

3.2.8.1 Deliverable: Commercial Documents [CDRL A009]

a. Schedule: NLT ten (10) business days after identification of each requirement.

b. Content: Determined based upon supplies rendered such as equipment manuals, publications, manufacturers' descriptive literature of cataloged products, equipment drawings, diagrams, performance and characteristic curves, catalog cuts, warranty periods, etc.

3.3 Task 3: Preventive Maintenance (PM) (CLIN 0003) (IDIQ Task Area 2 – Preventive Maintenance Support)

All PM support supplies and services rendered to complete this task (including subtasks) will be performed on a FFP basis. Contractor services rendered for this task (including all subtasks) will be documented within the MSR deliverable as described within this PWS.

The Government COR will perform evaluation and formal inspection and acceptance of the contractor’s services IAW the QASP.

To meet the Government’s objectives identified in this PWS, the contractor will be required to provide preventative maintenance (PM) (i.e. recurring maintenance) support services for the deployed ATG/IAS/OPE equipment. PM focuses on regularly scheduled inspections, inventorying, maintenance activities, and component replacements to prevent equipment failures before they occur. This is a proactive approach that aims to keep assets in optimal condition with the goal of maximizing equipment up time, extending asset lifespan, and reducing the likelihood of unexpected breakdowns requiring CM/Repair. As a general principle, the contractor will ensure PM support services will be completed compliant with the planned maintenance cycles (see Attachment # 1 - PM Frequency Listing) to ensure the Government does not have sites with overdue PM activities. The contractor will ensure their PM services rendered support the Government’s goal to attain an uptime of greater than (>) 95% uptime for the ATG/IAS/OPE solutions deployed globally.

The contractor’s PM support services for the ATG/IAS/OPE program will follow Unified Facilities Criteria (UFC) 3-460-03, general inspection and maintenance criteria for military land-based liquid petroleum fuel facilities. The PM process will also follow guidance for the equipment manufacture recommended PM processes and any additional PM processes or guidance aligned with DLA PM guidance / SOPs. These criteria are applicable to all branches of the DoD (including DLA). The contractor PM support services require personnel experienced in repair, maintenance, and operation of federal petroleum facilities and petroleum systems to ensure compliance with codes, criteria, regulations, and laws of the United States/host nation (local and national). The contractor personnel may be required to attain Honeywell ENRAF Veeder Root certifications to perform this task. UFC 3-460-03 applies to all real property facilities used for storing, distributing, and dispensing fuels for reciprocating and jet engine aircraft, automotive fuels, lubricating oils, and diesel fuel. As part of these PM support services, the contractor will be expected to generate detailed reports documenting the on-site conditions as encountered, testing verification of functionality, and identification of any deficiencies discovered.

PM support services rendered by the contractor will be based upon the unique configuration of each ATG/IAS/OPE site and deployed equipment. The contractor’s PM support services will be expected to include activities such as inspection, testing, maintenance, verification, validation, inventory, and documentation of the ATG/IAS/OPE solution at each site listed in Attachment 1 - List of ATG-IAS-OPE Sites. The contractor’s PM support services will also include drafting or revising applicable drawings/schematics for the ATG/IAS/OPE systems at each site. The contractor’s PM support services will be conducted compliant with the Government’s SOPs outlined in Appendix A – Guidance/Reference Documents. Contractor PM support at sites with IAS will include validation of the level alarms function as intended and fully interface with the SCADA, ICS, PLCs, and any other applicable AFS components on-site.

Contractor performance of PM support services requires their personnel to possess the capability of traveling CONUS and within OCONUS to the various DFSPs (i.e. performance of the work requires physical presence and PM support services cannot be done remotely). All contractor personnel performing PM support services at the DFSPs will have at least a basic level of technical knowledge on the operations of AFS and petroleum facilities/petroleum systems, including the physical hardware / equipment, communication protocols, testing and calibration, system of systems integration, etc. All contractor services rendered at the DFSPs will strictly observe all safety/security protocols and comply with applicable codes, criteria, and federal, state, local and/or host nation regulations.

The contractor will ensure all PM support services are logged and monitored within the Government’s ITSM solution (i.e. SNOW cases). All PM support must have at least one (1) SNOW case for each instance of services rendered. Inquiries to combine any SNOW cases will be directed to the COR on a case-by-case basis. The contractor will be responsible for logging into each SNOW case within the Government’s NE to actively log, monitor, update, maintain, and record all PM support services. All contractor personnel assigned the duties for logging into the Government’s NE will be required to have a valid CAC for access. The contractor will immediately inform the COR if their personnel no longer require access to the Government NE due to termination of employment or for any reason.

All PM support services rendered by the contractor must meet the Government’s expectations for the timely completion of the work compliant with Section 7.2 – Performance Standards of this

PWS.

In the performance of PM support services, the Contactor will be required to complete:

3.3.1 Subtask 3.1: PM Planning and Coordination

Contractor services rendered for this subtask will be documented within the MSR deliverable as described within this PWS. The Government COR will perform evaluation and formal inspection and acceptance of the contractor’s services IAW the QASP.

Based upon the Government PM schedule listing described in Attachment 3, the contractor will conduct all planning and coordination for PM support services of the ATG/IAS/OPE equipment deployed globally. This includes (but is not limited to) orchestration of contractor personnel travel and delivery of supplies to the DoD fuel facility/DFSP site. Each PM support service will be tracked on an individual basis via SNOW cases in the ITSM solution. The contractor will be required to perform all advance coordination with the various DFSPs site personnel to ensure all inspections and maintenance efforts can be accomplished during a site visit for PM. The Government will not be responsible for reimbursement of travel or lost time due to a lack of advanced coordination with the DFSPs prior to site visits for PM. Confirmation of contractor coordination with the DFSPs prior to personnel travel will be documented in writing and logged by the Contactor within each SNOW case as applicable.