SP470926Q0001.pdf

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NO. 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE 17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NO.

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

RFQ IFB RFP

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REF.

DATED . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 3/2005)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITON IS

UNRESTRICTED OR

NAICS:

SIZE STANDARD:

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

OFFER

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED VETERAN-

OWNED SMALL BUSINESS

EMERGING SMALL

BUSINESS

8(A)

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

541519

$34,000,000

STANDARD FORM 1449 (REV. 3/2005) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

36. PAYMENT

COMPLETE PARTIAL FINAL

37. CHECK NUMBER

PARTIAL FINAL

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 42a. RECEIVED BY (Print)

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 3/2005) BACK

SP4709-26-Q-0001

Complete the following tables to include the unit price and total of all categories.

Optional Transition-in Period: January 1, 2026, through March 31, 2026

CLIN DESCRIPTION U/I

QTY

UNIT

PRICE

TOTAL

Task 1: (Optional) Transition-in Support 3 Months

UN

Base Period: April 1, 2026, through March 31, 2027

CLIN DESCRIPTION U/I QTY UNIT

PRICE

TOTAL

Task 2: Task Order (TO) Administrative Management: 12 Months

Task 3: Technical Support (Tier II & III):

12 Months

Task 4: Cybersecurity Support:

Task 5: Application Enhancement Support:

Total $

Option Period 1: April 1, 2027, through March 31, 2028

CLIN DESCRIPTION U/I QTY UNIT

PRICE

TOTAL

Task 2: TO Administrative Management Option Period 1: 12 Months UN 1

Task 3: Technical Support (Tier II & III) Option Period 1: 12 Months UN 1

Task 4: Cybersecurity Support Option Period 1:

12 Months UN 1

Task 5: Application Enhancement Support Option Period 1: 12 Months UN 1

Option Period 2: April 1, 2028, through March 31, 2029

CLIN DESCRIPTION U/I QTY UNIT

PRICE

TOTAL

Task 2: TO Administrative Management Period 2: 12 Months UN 1

Task 3: Technical Support (Tier II & III) Option Period 2: 12 Months UN 1

Task 4: Cybersecurity Support Option Period 2:

Section 1: Schedule of Supplies

Task 5: Application Enhancement Support Option Period 2: 12 Months UN 1

Optional Transition Out Period: January 1, 2029, through March 31, 2029

2006 Task 6: (Optional) Transition-Out Support 3-Months

Total Base & All Options $

SECTION 2: PERFORMANCE WORK STATEMENT (PWS)

2.1 BACKGROUND

The Defense Logistics Agency (DLA) provides worldwide logistics support, acquisition, and technical services to the military services, other federal and civilian agencies, and partner nations. DLA Energy, as the DoD's Executive Agent for bulk energy products (CLASS III), manages fuel inventory and war reserve stock levels globally. To execute this mission, DLA Energy requires Information Technology (IT) development, maintenance, and sustainment services for its critical applications and systems, including incorporating enhancements through software requirements determination, design, development, integration, and deployment.

2.1.1 IT Systems Overview

DLA Information Operations (J62) maintains the Energy Procurement Support Tool (EPST) and the Inventory Accountability Web Tool (IAWT) to support DLA Energy's mission. These systems have achieved Full Operating Capability (FOC) and maintain an Authority / Authorization to Operate (ATO) compliant with DoD Risk Management Framework (RMF) cybersecurity requirements. These systems operate in development, test, stage, and production instances hosted in government or commercial cloud and on-premises environments.

2.1.1.1 Energy Procurement Support Tool (EPST)

EPST is designated as a DLA Energy mission critical system and is a conglomerate of commercial off-the-shelf (COTS) applications that are fully deployed (e.g. are in the operations phase of the acquisition lifecycle). These mature applications were formerly part of the Business Systems Modernization Energy (BSM-E) set of applications and were previously accredited under BSM-E. EPST supports DLA Energy in the procurement process for fuel products for DOD as well as for many Federal Civilian agencies. EPST performs a very important mission support role for DLA Energy by providing a very advanced toolset for critical procurement-based decision-making processes. As a collection of applications, EPST works to take an Enterprise Business Solution Solicitation for fuel and make it available to fuel vendors to electronically enter their offers. EPST is NOT a financial management system - that role is provided by DLA’s Enterprise Business System (EBS) which serves as the authoritative system for facilitating procurement, supply, and financial related functions for DLA-Energy.

2.1.1.1.1 EPST Key Business Functions:

At a high level, EPST provides DLA energy the following business functions:

# DLA Energy Key Business Function 1 Solicitation imports from EBS.

2 Secure bid entry by vendors.

3 Replaces paper submission.

4 Manual bid entry by DLA if necessary.

5 Receive up-to-date transportation rate information.

6 Freight Management database and applies transportation rates to fuel delivery arcs.

7 Bid evaluation.

8 Fuel coverage evaluation.

9 Fuel least cost solution.

10 Reverse Auctions.

11 Multiple spreadsheets / reports for data evaluation.

12 Awards to winning Offerors.

13 Contract creation.

14 Contract and distribution export to EBS.

15 Freedom of Information Act (FOIA) contract information as necessary for publication.

16 Real-time access to escalated prices and price history.

17 Coordination / validation of data.

18 A repository for historical contract information.

Table 1 – EPST Key Business Functions

2.1.1.1.2 EPST Key Modules:

• Offer Entry Tool (OET) - The OET web application is a public, but restricted web-based application that is used primarily by external potential fuel vendors. OET provides the automated means to conduct bid rounds and/or reverse auctions for DLA acquisition of products (e.g. ground and bulk fuels, based on requirements published in DLA solicitations). OET automates and streamlines the process of identifying product coverage gaps, as well as the time-to-award process for bid evaluation and contract award. OET replaced submission of paper bids by vendors to DLA.

• Transportation Rate Information System (TRIS) – TRIS is a Controlled Unclassified Information (CUI), Common Access Card (CAC)-authenticated application that provides DLA Energy internal only users with transportation rate information for all bulk fuel moves necessary in the bid evaluation process. TRIS provides the capability for the EPST Bid Evaluation Module (BEM) to query the Global Freight Management (GFM) database for the latest approved transportation rates for fuel commodities to perform mathematical analyses. It automates import and updates to transportation rates as specified by Military Traffic Management Command

(MTMC).

• Bid Evaluation Model (BEM) – The information generated by the BEM application is categorized as Controlled Unclassified Information (CUI). BEM supports DLA Energy’s procurement activities by automating the evaluation of bulk fuel bids received from OET using Government procurement business rules / processes and data originating from TRIS. It leverages mathematical optimization to satisfy the procurement requirements of each specific DLA Energy fuel solicitation by identifying a solution at the least / optimal cost within the strictures of Government economic programs. To perform its functions, BEM uses highly complex mathematical programming system (MPS) files that contain linear programming (LP)and mixed integer linear programing (MILP) with numerous continuous and discrete variables. Data from BEM is fed into Gurobi Optimizer, a data prescriptive analytics tool that performs solves the equations by performing the mathematic calculations and providing solutions in the form of source selection recommendations / award determinations.

• Energy Contract Information System (ECIS) - ECIS is a public facing web application that allows visitors to view contract information that has been cleared for public release and is published as required by public law under the Freedom of Information Act (FOIA). Due to its public nature, no user login is required to access ECIS. It allows government personnel, contractors, suppliers, and other interested parties to view current and historical line-item detail and information about the corresponding government contracts for DLA Energy.

ECIS receives its data via interfaces with various applications internal and external to DLA.

• Prices to Web (P2W) – P2W is also a public facing web application that allows government personnel, contractors, suppliers, and other interested parties to view current and historical energy product prices. The information contained in P2W is approved for public release and is published as required by public law under FOIA. Due to its public nature, no user login is required to access P2W.

• Provisioner - The EPST Provisioner Tool is a CUI, CAC-authenticated application that allows DLA Database Administrators (DBAs) to manage the user account and logon data for non-FOIA EPST modules/applications in a role-based fashion. The Provisioner allows Administrators to: add, edit, and archive EPST user account data including names, email addresses, and user types/access levels to the OETs, BEMs and TRIS modules; register, or link, user accounts to an EPST application user’s CAC; change/reset an EPST application user’s password for the OETs; enforce the expiration of users’ accounts due to inactivity via an automated process; create Microsoft Excel spreadsheet reports of EPST user data using filters.

2.1.1.2 Inventory Accountability Web Tool (IAWT)

IAWT is designated as a DLA Energy mission critical system primary comprised of a web application that assists DLA Energy with oversight of the Defense-Wide Working Capital Fund (DWWCF). It is DLA Energy’s inventory accountable officers’ management tool that provides headquarters and regional personnel with things such as daily inventory, reconciliation of transactions across multiple systems, determinable gain/loss investigations, etc.

2.1.1.3 FASTracker

FASTracker is a web application that DLA Energy uses as a central repository to manage and maintain critical site documentation and contains in excess of 1.4 terabytes of data including; Points of Contact (POCs), upload shared files, technical data, configurations for Defense Fuel Supply Points (DFSPs), equipment inventories, etc. The data within FASTracker does contain controlled unclassified information (CUI) and the system is not authorized to store classified information.

2.2 Objectives & Scope

This Performance Work Statement (PWS) outlines the Government’s requirements to acquire the necessary Information Technology (IT) services for EPST, IAWT, and FASTracker.

2.2.1 Objectives

The Government's objectives of this Firm-Fixed-Price (FFP) Task Order (TO) is:

a. Maintain, sustain, and provide technical support for DLA Energy critical IT systems: Ensure the continued operation, functionality, and security of EPST, IAWT, and FASTracker as well as obtain expert-level assistance to users, troubleshoot issues, and ensure their availability.

b. Ensure cybersecurity compliance: Continuously monitor and implement security controls for EPST, IAWT, and FASTracker and retain existing Authorizations to Operate (ATOs).

c. Enhance and improve EPST, IAWT, and FASTracker: Design, develop, test, and deploy new improvements and features to meet DLA Energy’s evolving business needs.

2.2.2 Scope

To meet the Government's objectives, the Contractor is required to provide IT, administrative, and program or project management services for EPST, IAWT, and FASTracker including:

• Sustaining current operations, including bug fixes and defect resolution.

• Maintaining the existing solutions and system of systems including ensuring:

o The continued functionality of mathematical optimization within EPST – BEM based upon DLA Energy’s business needs.

o The interoperability of all existing interfaces into a holistically integrated solution.

• Ensuring cybersecurity compliance and retaining existing ATOs.

• Designing, developing, testing, and deploying new enhancements to the existing solutions and system of systems using agile methods.

The Contractor will need to provide a wide variety of IT, administrative, and project management services to develop new enhancements, sustain current operations (including fixing bugs/defects), and maintain EPST, IAWT, and FASTracker. Services unrelated to meeting the requirements described in this PWS for the EPST and/or IAWT solutions are NOT included within the scope of this FFP TO.

For the purposes of defining the scope of this TO, the entirety of the EPST, IAWT, and FASTracker solutions includes the overall technology stack elements such as:

• Network / computing environments (NE / CE) (such as Development, Test, Stage, Production, Fail/Cut Over, Recovery, etc.)

• Modules

• Components

• Software

• Firmware

• Hardware

• Equipment

• Coding

• Configuration

• Batch programs

• Mathematic optimization / programming (such as Linear Programming (LP) or Mixed Integer Linear Programming (MILP))

• Scripts

• Sub/ancillary software

• Licenses

• Data

• Infrastructure

• Databases

• Servers / Machines (physical or vitual)

• Interfaces

• Reports / reporting

• Documentation

• Artifacts

• Cybersecurity controls

All of these elements are holistically intertwined and depend upon each other to provide the Government with the features, functions, and capabilities rendered by EPST, IAWT, and FASTracker regardless of geographical location.

Therefore, references to "EPST", “IAWT”, or "FASTracker" within this PWS should be understood by the Contractor as the entirety of the respective solutions unless otherwise explicitly stated.

This PWS describes the requirements for the Contractor to provide various types of IT and program support services including:

• Program / project management support

• Technical support

• Cybersecurity support

• Agile software development and enhancement support

• Configuration / change management support

• Mathematical optimization

• Web application support

• Database administration support

• Interface support

The Contractor’s support services for EPST, IAWT, and FASTracker will be provided within their development, test, stage, failover / continuity of operations (COOP), and production instances hosted in Government or commercial cloud environments. A rendering of the support services will require the Contractor to obtain “privileged” access and regularly communicate / coordinate work performance with third-party contractors and Government personnel such as J61 Cybersecurity, J64 Technology Foundation Services (TFS), etc.

2.2.2.1 Mathematical Optimization and Gurobi Optimizer:

Due to EPST – BEM’s dependency on mathematical optimization and problem solving via Gurobi Optimizer to function correctly, the Contractor will need to possess the capability of:

a. Mathematical Optimization:

i. Reviewing, analyzing, and maintaining highly complex MPS files containing LPs and MILPs that are comprised of equations, formulas, mathematical data (e.g. continuous and discrete variables).

ii. Identifying LP and MILP problems / errors and expeditiously correcting them.

iii. Enhancing EPST – BEM functionality by:

1. Receiving DLA procurement business rules / processes (e.g. decision variables, constraints, etc.)

and translating them into requirements (e.g. user stories) to design new or revise existing LPs or MILPs.

2. Building, reverse engineering, reformulating, configuring, or modifying LPs or MILPs using agile methods.

A. Changes to LPs or MILPs within MPS files will only be performed complaint to Government approved Configuration / Change Management (CM) processes.

b. Gurobi Optimizer:

i. Understanding Gurobi licensing models and managing them for the Government’s BEM environments.

ii. Conducting performance tuning by adjusting Gurobi Optimizer parameters to improve solution time and quality.

iii. Leveraging the Gurobi Application Programming Interface (API) with java programming to test, validate, and debug LPs and MILPs.

iv. Working with third-party Gurobi technical support to resolve complex issues including:

1. Reviewing, analyzing, and interpreting Gurobi Optimizer data error messages and log files.

2. Clearly and concisely documenting problem statements associated with mathematical optimizations (e.g. MPS files with LPs and MILPs)

3. Generating and submitting tickets for expert level technical support.

4. Receiving corrections from Gurobi support and implementing them compliant to Government approved CM processes.

2.2.2.2 Current EPST Infrastructure:

At a high level, the contractor’s EPST support services will include:

Component Operating System (OS) Applications Software File Transfer Services (SFTP)

Lunix 8.10

Perl 5.38.0

Application Web Servers

Oracle WebLogic 12.2.1.4

Gurobi Optimizer 11.x

Chron scheduler

Database Administration Application Server Oracle Client 21.6

Database Servers Oracle Database 19c Enterprise Edition Table 2 – EPST Current Infrastructure

2.2.2.3 Current IAWT Infrastructure:

At a high level, the contractor’s IAWT support services will include:

Application Web Servers Windows Server 2022 Datacenter IIS 6 & Visual Studio 2015

Database Servers Windows Server 2019 Microsoft SQL Server 2019

Table 3 – IAWT Current Infrastructure

2.2.2.4 Current FASTracker System Infrastructure:

At a high level, the contractor’s EPST support services will include:

Application Web Servers* Windows Server 2022 Datacenter IIS 10 & ColdFusion 2021

Database Servers* Windows Server 2016 Microsoft Structured Query Language (SQL) Server 2019

Table 4 – FASTracker Current Infrastructure

2.2.3 Work Breakdown Structure (WBS)

Within the scope of services for this FFP TO, the Contractor will be expected to align work rendered with the following WBS and successfully complete all tasks identified. Execution of the required services is comprised of six (6) distinct tasks as depicted in the below graphic and WBS, with detailed information described in this PWS.

Figure 1 – EPST, IAWT, & FASTracker Support Work Breakdown Structure (WBS)

2.3.

EPST, IAWT, & FASTracker Support

2.3.1 Task 1

Transition-In (Optional)

2.3.2 Task 2

TO Admin Management

2.3.3 Task 3

Technical Support

(Tier II & III)

2.3.4 Task 4

Cybersecurity Support

2.3.5 Task 5

Application Enhancement

Support

2.3.6 Task 6

Transition- Out

(Optional)

This Task Order falls under IDIQ RFP: SP4709-23-R-0001 Task Areas:

EPST, IAWT, & FASTracker Support Work Breakdown Structure (WBS)

PWS # This Task Order JETS 2.0 IDIQ SOW Task

2.3.1

TASK 1 – Transition-In (Optional)

• 2.3.1.1 Subtask 1 - Knowledge Transfer

• 2.3.1.2 Subtask 2 - Transfer of Duties

• 2.3.1.3 Subtask 3 - Confirmation & Reporting IUS (Internal Use Software) # 0003 – Operational Phase

Task Area 7 – Task Order Project Management Support

2.3.2

TASK 2 – Task Order (TO) Administrative Management

• 2.3.2.1 Subtask 1 - Post Award Conference

• 2.3.2.2 Subtask 2 - Weekly Updates / Weekly Activity Report (WAR)

• 2.3.2.3 Subtask 3 - Monthly Status Report (MSR)

• 2.3.2.4 Subtask 4 - In Process Reviews (IPRs)

• 2.3.2.5 Subtask 5 - Monthly DoDM 8570.01-M / DoDD 8140.01 Report - CUI

• 2.3.2.6 Subtask 6 - Meeting Agendas, Presentations, and Minutes IUS # 0004 – Program Management

Task Area 7 – Task Order Project Management Support

2.3.3

TASK 3 – Technical Support (Tier II & III)

• 2.3.3.1 Subtask 1 - DLA ServiceNow (SNOW) Tickets, Incidents, and Cases

• 2.3.3.2 Subtask 2 - User Account Management

• 2.3.3.3 Subtask 3 - Operations & Sustainment (O&S) and Incident Resolution Support

• 2.3.3.4 Subtask 4 - Web Application Support

• 2.3.3.5 Subtask 5 - Database Administration Support

• 2.3.3.6 Subtask 6 - Interface Support

• 2.3.3.7 Subtask 7 - Technical Documentation Support IUS # 0003 – Operational Phase

Task Area 2 – Technology Services

2.3.4 TASK 4 – Cybersecurity Support IUS # 0003 – Operational Phase

Task Area 6 – Cyber Security Support Services

2.3.5 TASK 5 – Application Enhancement Support IUS # 0003 – Operational Phase

Task Area 2 – Technology Services

2.3.6

Task 6 – Transition-Out (Optional)

• 2.3.6.1 Subtask 1 – Transition Plan Development

• 2.3.6.2 Subtask 2 – Execute Knowledge Transfer to Follow-on Provider IUS # 0003 – Operational Phase

Task Area 7 – Task Order Project Management Support

Table 5 – EPST, IAWT, & FASTracker Support WBS – Tasks & Subtasks

Set Aside for Small Businesses, Group A contractors

This task order will be evaluated in accordance with Tradeoff source selection procedures. Award of this task order will be made on a competitive best value basis, using “tradeoff” procedures between non-price and price. In evaluating task order proposals, the non-price factor(s) is/are considered significantly more important than price. The Government may consider award to other than the lowest priced Contractors or other than the highest technically rated Contractors.

The criteria used to select the contractor for award of this task order will be based on an evaluation of the contractor’s proposed labor mix and allocation along with its proposed price as compared to the government’s estimate of the work to be performed.

Non-Price Factor 1 – Level of Effort/Labor Mix: The contractor’s quality of proposed personnel will be evaluated based on an assessment of the level of experience and skill necessary to minimize Government risk and successfully complete the technical requirements outlined in the task order PWS. Proposed labor mix and allocation will be evaluated on experience, skills and qualifications as they relate to the requirements of the task order PWS. Contractors are required to submit copies of resumes for all key personnel (and key personnel substitutions) proposed in response to this task order PWS.

Non-Price Factor 2 – Technical Approach: Describe in detail your approach to develop the specified deliverables and perform each tasking in the PWS. The Contractor must provide evidence demonstrating a clear understanding of the scope and complexity of the requirements set forth in the PWS. The proposed approach must be well-defined and logical and include the methodologies and processes that can successfully meet DLA objectives and mitigate risk. Provide a Transition Plan strategy to execute the transition-in of all service areas; a strategy to transition-out all services to include knowledge transfer to personnel designated by the government; and details on a full performance schedule for both the transition-in and transition-out phases.

Non-Price Factor 3 – Past Performance: The Government will consider the contractor’s past performance/experience under U.S. Government contracts or other contracts/projects within 3 years of the initial closing date of this RFQ. Any contracts/projects submitted in reference to past performance that are outside of the 3-year recency period will not be considered for evaluation. Contractors will submit at least one past performance example, but not more than two examples. Contractors may submit JETS task orders as past performance examples.

Note: In the case of a contractor without a record of relevant past performance or for whom information on past performance is not available, the contractor will not be evaluated favorably or unfavorably on past performance and will receive a Neutral rating.

In evaluation of this factor, the following aspects will be considered:

Aspect One: Relevancy of Prior Contracts - The relevancy of contractor’s prior projects to the current PWS requirements will be evaluated based on the similarity to the service/support, the complexity, and dollar value. The Government will evaluate the contractor’s demonstrated evidence of experience in performing contracts with a similar size, scope, and complexity to this task order requirement.

Aspect Two: Quality of Past Performance (i.e., how well the contractor performed) - The contractor’s history of success in completion of projects, history of producing high-quality reports and deliverables, and commitment to customer satisfaction and history of staying on schedule and within budget will be evaluated via CPARS/PPIRS; information provided in the contractor’s offer; and/or with the Government’s independent contact with the contractor’s prior customers. Degree of conformance to contractual requirements, responsiveness, and effectiveness in addressing issues, quality of customer service, and/or conformance to cost/price requirements or goals, will be evaluated in the qualitative past performance ratings.

Factor 4 – Price: The proposed task order pricing will be evaluated to determine if it is in accordance with the IDIQ.

Pricing will be evaluated to ensure completeness and reasonableness.

Current Incumbent Information:

DLA is consolidating the requirements from the following current IT support contracts into this PWS:

Sustainment Incumbent Information:

• Contractor Name: Information Technologies Strategies, LLC (IT-Strat)

• CAGE: 4PRV8

• Address: 23392 Summerstown, PL Dulles, VA. 20166-2178

• Contract #: SP4709-17-D-0054

• TO #: SP4709-22-F-0085

Development Incumbent Information:

• Contractor Name: Aymx, INC

• CAGE: 1QNC9

• Address: 1768 Business Center Dr, STE 300, Reston VA, 20190-5349

• Contract #: SP4709-17-D-0015

• TO #: SP4709-24-F-0063

2.3 EPST, IAWT, and FASTracker Support Task Requirements

Unless explicitly specified otherwise, the contractor must report on all activities performed in accordance with (IAW) this PWS to the Government designated Contracting Officer’s Representative (COR) and/or Technical Point of Contact (TPOC) as assigned. Final inspection and acceptance of all supplies and services to complete the activities, Government reviews, and required data deliverables will rest with the Contracting Officer (KO) or COR. In terms of all deliverables (whether formal or informal), a “Day” means (unless otherwise specified) a business day or workday. All electronic documentation must be submitted by the contractor to the Government using the latest version of Microsoft Office or Adobe software products unless otherwise directed.

In the performance of the requirements outlined in this PWS, 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 each of the following:

2.3.1 Task 1 - Transition-In (Optional)

The Contractor's rendered services for this task will be documented within the Monthly Status Report (MSR) deliverable as described within this PWS.

If the awardee is NOT the incumbent identified in this PWS, the Government may choose to execute these OPTIONAL transition-in services. If executed, the contractor will be required to support a 90-calendar day transition-in period to ensure uninterrupted services. The purpose of these transition-in services is to prevent impact on Government operations and reduce the risks associated with contract performance including decrements to productivity or possible negative impacts on additional services. These services will ensure the successful transfer of services from third-party contractors and the contractor's key personnel must be fully engaged in the transfer activities. During the transition period, work should continue to be performed by current third-party contractors IAW the terms and conditions of separate Government contractual obligations until confirmation is obtained that all key personnel responsibilities, services, and ServiceNow (SNOW) cases have been successfully transferred to the contractor. Successful execution of these transition services necessitate the contractor to use an iterative approach and complete the following:

2.3.1.1 Subtask 1 - Knowledge Transfer:

The Contractor is expected to:

a. Coordinate, participate, and facilitate interactive working sessions with existing third-party contractors to gain familiarity with tools, processes, and organizational assets.

b. Generate new or revise existing knowledge documentation to codify tacit or explicit information gained during the transition.

i. All documentation (new or revised) from knowledge transfers must be submitted to the Government by no later than (NLT) fifteen (15) calendar days before the end of the transition period.

Deliverable: A001 – Transition-In Documentation

• Schedule: NLT fifteen (15) calendar days before the end of the transition period.

• Content: As determined by Government in collaboration with contractor based upon the transition-in working sessions and knowledge gained (tacit and explicit).

• Format: Electronic copies viewable using the latest version of Microsoft Office or Adobe PDF.

2.3.1.2 Subtask 2 - Transfer of Duties: The Contractor is expected to:

a. Review, understand, and accept the duties for key personnel, services, and all active SNOW cases.

b. Work alongside existing third-party contractors to understand and be fully capable of executing the duties assigned by the end of the transition period.

c. Accurately inventory, account for, and transfer any existing supplies (e.g., bench stock, Government

Furnished Equipment (GFE), etc.).

d. Provide prompt written notification to the COR of problems / issues associated with transition of services from third-party contractors. This includes (but is not limited to) anything preventing acceptance of responsibilities for key personnel, services, and SNOW cases before the end of the transition-in period.

2.3.1.3 Subtask 3 - Confirmation & Reporting: The Contractor is expected to:

a. Schedule, facilitate, and participate in a meeting with the COR no later than fifteen (15) calendar days before the end of the transition period to ensure all problems / issues associated with the transition of services have been identified and are addressed.

b. Provide confirmation that transfer of knowledge and duties has been completed.

i. The Government’s target date for the Contractor’s acceptance of responsibilities of key personnel roles and services is NLT 30 calendar days prior to the end of the transition-in period. However, regardless of the target date, the Contractor is expected to have fully accepted responsibility for key personnel roles and services by NLT the end of transition-in period.

c. Submit a Transition-In Report to document transition of duties and support Government oversight.

Deliverable: A002 - Transition-In Report

• Schedule: NLT fifteen (15) calendar days before the end of the transition period.

• Content:

o Confirmation that knowledge transfer from third-party contractor is complete and all knowledge documentation has been generated.

o Confirmation the contractor has formally accepted responsibilities for key personnel roles and services.

o Confirmation all SNOW cases have been reassigned from third-party contractors.

o Any additional relevant information for transition-in of duties and responsibilities.

2.3.2 Task 2 – Task Order (TO) Administrative Management

(MSR) deliverable as described within this PWS.

The Contractor will provide comprehensive TO administrative management (prime and subcontractor), including work activity planning, oversight, schedule control, risk management, communications, staff coordination, and stakeholder engagement. The Contractor must designate a TO Project Manager (PM) who will implement disciplined, flexible program management, proactively monitor performance, and manage risks and issues to ensure timely work completion. The Contractor's administrative responsibilities for performing this TO and supporting EPST, IAWT, and FASTracker are expected to include:

a. Ensuring transfer-in and transfer-out services identified in this PWS are successfully rendered.

b. Providing qualified staffing, including skill sets, on/off boarding, and reporting.

c. Meeting performance goals and promptly completing assigned action items.

d. Managing Contractor personnel compliance with 8570 requirements and tracking IT system access.

e. Ensuring timely delivery and proper upload of all deliverables, documents, and data to the Government-designated Repository.

f. Managing daily operations and coordinating Contractor resources including:

i. Ensuring the seamless integration of the Contractor’s personnel successfully complete all tasks, subtasks, and deliverables.

ii. Monitoring and verifying completion of all assignments, tasks, etc.

iii. Attending meetings, discussions, troubleshooting calls, etc.

iv. Confirming the Contractor’s technical support team maintains technical documentation, artifacts, etc.

v. Verifying CM activities adhere to Government processes via DLA's Information Technology

Service Management (ITSM) solution (i.e. ServiceNow/SNOW).

vi. Planning regularly scheduled maintenance window activities.

g. Schedule or participate in meetings, generate meeting agendas, presentations, minutes, action items, etc.

h. Reporting contractor performance and applicable data to the Government.

i. Request, monitor, confirm, and maintain Contractor access to the Government Network Environment (NE) to render services including:

i. Continuously ensuring services are logged within the ITSM solution (i.e. SNOW).

ii. Monitoring and verifying Contractor personnel complete all mandatory training to obtain or maintain access to the Government NE.

1. Contractor personnel (including subcontractors) accessing the Government NE will be required to complete safety, Information Assurance (IA), security, or other Government mandated training. The COR will notify the contractor of training requirements.

2. The contractor will ensure assigned personnel successfully participate in and complete all mandatory training prior to access being granted to the Government NE.

j. Proactively identifying, assessing, and managing Risks, Issues, and Opportunities (RIOs) compliant with Government processes.

k. Performing additional in-scope TO administrative management duties as required.

At a minimum, the Contractor’s services rendered to complete this task will include:

2.3.2.1 Subtask 1 – Post Award Conference

The Contractor is expected to participate in a single and/or multi-day post award conference that is intended to serve as orientation for contract 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 aid both 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 fully understanding 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 Government before the conference date. The Contractor will document a summary of the events that transpired and the action items assigned during the post award conference. All documentation generated by the Contractor for the post award conference is expected to be submitted to the Government NLT ten (10) business days after conclusion of the conference.

Deliverable: A003 - Post Award Conference Presentation & Action Items

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

• Content: As determined by Government in collaboration with Contractor based upon the requirement.

• Format: Electronic copies viewable using the latest version of Microsoft Office or Adobe PDF

2.3.2.2 Subtask 2 - Weekly Updates & Weekly Activity Report (WAR)

To support Government oversight and monitoring of the Contractor’s performance, the Contractor is expected to provide reoccurring weekly updates to the Government. The purpose of the weekly update and WAR is to provide a means for an informal exchange 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 contract on a business day (i.e. Monday, Tuesday, Wednesday, Thursday, or Friday) that is mutually agreed upon by the Contractor and the Government. Weekly updates that are scheduled to occur on Federal Holidays will be rescheduled at the discretion of the Government. The weekly update will be intentionally designed so that it is short in duration (no longer than one (1) hour) and is expected to consist of the following elements:

a. Weekly Virtual Teleconference – The Contractor is expected to schedule a weekly virtual teleconference with the Government. The Contractor will develop and provide an agenda that covers topics to aid Government oversight, such as a summary of open tickets within SNOW with supporting information, relevant Contractor activities / work progress, performance risks or issues, etc. The Contractor will generate a summary that records attendees, discussions, and any action items (including responsible parties and due dates). These minutes will be included in the 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 a WAR. The WAR is expected to be organized for easy review and is expected to contain the summary and relevant data presented during the teleconference (such as summary reports from SNOW).

Deliverable: A004 - Weekly Activity Report (WAR)

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

• Content: Weekly Virtual Teleconference Summary & Applicable Data.

2.3.2.3 Subtask 3 - Monthly Status Report (MSR)

To provide adequate documentation for Government oversight, inspection, and acceptance of services, the Contractor is expected to provide recurring Monthly Status Reports (MSRs). The MSR will serve as formal documentation of services rendered, supporting Government surveillance, review, and evaluation of Contractor performance. The MSR is intended to summarize the preceding month’s work and is expected to include, financial expenditures, data/metrics, action items, staff changes, and any significant risks/issues/concerns. The Contractor will ensure that no Controlled Unclassified Information (CUI) is included. The first MSR will be submitted to the Government within thirty (30) calendar days after contract award, with subsequent MSRs due no later than the fifth (5th) business day of each month. The document will be formalized via signature to establish a record of services rendered and copies will be provided to the Government for retention.

Deliverable: A005 - Monthly Status Report (MSR)

• Schedule: Within thirty (30) calendar days after contract award and NLT the fifth (5th) business day thereafter.

• Content: Each MSR submitted is expected to contain the following:

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

o The services rendered during the preceding month, including completed tasks, subtasks, Government reviews, milestones, action items, and deliverables compliant with this PWS. It is also expected to include, financial expenditures, staff changes, and any significant issues/concerns as applicable.

o Current (within two (2) business days of submission) data/metrics from the Government’s

Project Information Management System (PIMS) (i.e. JIRA / DLA SNOW) for Contractor (prime or subcontractor) assigned work described in this PWS. The Government may inspect reported the data/metrics to evaluate service quality and timeliness. For example, deficient tickets/incidents/cases from DLA SNOW may result in a Government determination of "less than Satisfactory" for the Contractor’s performance rating. The Contractor and the Government will collaborate to define the specific data/metrics from the PIMS to be included in the MSR based on Government oversight needs.

o A summary list of current Contractor staffing (prime and subcontractor) who are performing work on the contract.

o Description of any known risks or issues to Contractor performance and efforts to mitigate or remedy them.

All risks or issues must be identified and managed complaint to the Government’s risk, issue, and opportunity (RIO) management processes.

o Contract financial information (such as documentation identifying by CLIN funds expended and amounts remaining).

o Any additional information or documentation necessary to support successful Government surveillance.

o An area / section reserved for use by the Government to provide input, feedback, and performance evaluation information.

o Signature page containing lines for:

Contractor

Government

2.3.2.4 Subtask 4 - In Process 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. 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 identify any issues that are preventing successful performance. Suitable topics include active risks/issues, progress updates, tasks of Government or contractor concern, or other efforts requiring 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.

Deliverable: A006 - In Process Review (IPR) Documentation

• Schedule: Within five (5) business days after completion of each IPR.

• Content: As determined by COR in collaboration with Contractor based upon the requirement.

2.3.2.5 Subtask 5 - Monthly DoDM 8570.01-M / DoDD 8140.01 Report – CUI

The DoDM 8570.01 / DoDD 8140.01, Information Assurance Workforce Improvement Program, requires training and certification for Information Assurance (IA) duties performed. All contract employees performing IA functions (i.e. regardless of whether the personnel are prime or subcontractor and key or non-key personnel) must meet the requirements in accordance with DoD/DLA guidance. Additionally, Contractor employees performing System Administration (SYSADMIN) or other privileged access duties are expected to be certified in the specific operating systems for which these duties are performed. Proof of certification must be provided before privileged access is granted and (for key personnel) must be provided by the Contractor at time of proposal submission (i.e.

via key personnel resumes). The requirements for DoDM 8570.01 / DoDD 8140.01 include (but is not limited to) system administration access, network administration access, router/switch access, firewall access, and Intrusion Detection System (IDS) access, Programmable Logic Controller (PLC) access, and Supervisory Control and Data Acquisition (SCADA) access. All documentation required for security certification will be maintained by both the Contractor and the Government via the reporting described within this PWS. The certification requirements associated with are not based on position title; they are based on assigned duties. As such, the Contractor is expected to ensure that all personnel accessing information systems, including network or system components, either during provisioning or post award, have the proper and current information assurance certification to perform functions in accordance with the latest edition or successor publication of DoD 8570.01-M.

Contractor/subcontractor personnel identified on this contract as requiring IA certification are expected to have their required security and industry competency certifications compliant with DoDM 8570.01 / DoDD 8140.01, Information Assurance Improvement Program, prior to starting work and maintaining their certifications so long as they are performing duties requiring privileged access throughout the life of the contract. If a certification becomes obsolete during the life of the contract, the Contractor is expected to be responsible for ensuring applicable personnel obtain a replacement certification that is acceptable to the Government prior to the continuation of work on the contract. The Contractor is expected to immediately inform the Contracting Officer if a contractor personnel’s clearance is revoked or otherwise changed or called into question.

Contractor employees must have a security investigation that has been favorably adjudicated at the level appropriate for the required system access. As personnel are replaced or added during contract performance, the Contractor should provide only those employees with an active security investigation that has been favorably adjudicated at the level appropriate for the required system access.

Contractor personnel who do not have proper and current certifications will be denied access to DoD information systems for the purpose of performing information assurance functions as described in DoDM 8570.01. New hires can shadow current personnel with a valid certification, however new personnel is expected to obtain their certification within 6 months from their official start date on the contract. A monthly status on certification qualification is expected to be provided for all new hires and current employees whose certifications will expire in the next 6 months.

All Contractor personnel provided with access to Information Systems should observe local and host Automated Information Systems policies and procedures directed by the Information System Security Manager (ISSM) or Information System Security…