2024.02.22 SAM.gov Update.docx

SUBJECT: Acquisition Strategy, Milestone Updates, and Evaluation Factors for HTC711-24-Q-D014 Global Freight Management (GFM)

This is not an official solicitation and the Government is not requesting nor accepting proposals at this time.

1. Acquisition Strategy and Evaluation Approach:

This requirement will be solicited as an SDVOSB set-aside under North American Industry Classification System (NAICS) code 541512, Computer Systems Design Services. It is the Government’s intent to award a firm-fixed price (FFP) task order with Labor Hourr CLINs against GSA MAS 54151S to one contractor who demonstrates the ability to successfully provide support for the GFM requirement for SDDC at Scott AFB, IL.

This will be a competitive best value tradeoff source selection and evaluations will be conducted in accordance with FAR part 8 and FAR part 12. When combined, non-price factors are more important than price. Past performance will only be evaluated on the apparent awardee on a capable/not capable basis. Within technical capability, subfactors 1, 2, 3, and 4 are of equal importance. Subfactor 5 is pass/fail.

2. Projected Key Milestone Dates:

Issue Solicitation: 03/08/2024 Proposals Due: 04/09/2024 Proposed Award Date: 07/30/2024

3. DRAFT Evaluation Factors and Submission Requirements:

(A) Price. This volume shall contain the offeror’s Price Quote, in the form of an Excel spreadsheet and all backup documentation used to support the prices.

(1) Offerors shall submit a price breakout in a MS Excel spreadsheet identifying the labor category, labor rate, and labor hours by PWS Task and Subtask Area.

(B) Technical Capability. This volume shall contain the offeror’s Technical Approach/Capability using Adobe or Microsoft Word.

(1) Subfactor 1 – GFM System Sustainment

Offeror shall provide their plan for continuous Functional and Technical support of the GFM applications and components in accordance with PWS Task Area 2. The plan shall include a detailed approach for using an Agile development methodology for managing design, development, enhancement, testing, deployment, and sustainment to ensure the GFM tools, configuration management, applications, databases, and interfaces are operational and continue to support SDDC operations, while ensuring compliance with cybersecurity directives. Offeror shall also provide their approach for maintaining UDF/EDI Sustainment of Electronic Data Interchanges (EDI), User Defined Format (UDF) and eXtensible Markup Language (XML) files for ASCII X12 to include creating and maintaining Web Service data exchanges. The approach shall include a detailed plan for updating, creating, mitigating, and/or generating the required documentation to maintain schema, Web Services Description Language (WSDL) WSDL and XML.

(2) Subfactor 2 – Enhancements and Cloud Native Refactoring or Redevelopment

Offeror shall provide their plan for enhancement projects to include the additional refactorization of all GFM applications in order become cloud native in a DoD approved Cloud Environment in accordance with PWS Task Area 3. Offeror shall provide their agile development methodology, team composition, and approach for projects from start to finish to include sprint schedules. The plan shall include a detailed approach to optimize the application(s) to perform in a ‘zero-trust’ environment, ensuring the implemented Development, Security, and Operations (DevSecOps) and Continuous Integration and Continuous Deployment (CI/CD) DevSecOps CI/CD pipeline, Resiliency, Web Services, Containerization, and Testing Automation tools/processes/components are operational and in compliance with governmental and cybersecurity directives. The plan shall demonstrate the offeror’s ability to meet changing requirements (i.e., refining existing cloud native efficiencies) to meet government capability objectives.

(3) Subfactor 3 – Risk Management Framework (RMF) Accreditation

Offeror shall provide their approach for maintaining an approved cybersecurity posture in all GFM environments in accordance with the National Institute of Standards and Technology (NIST) RMF and Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) guidelines in accordance with PWS Task Area 7, Subtask 2. The approach shall include a detailed plan for continuously monitoring, scanning, remediating, and generating required documentation to maintain accreditation compliance and support of a full RMF Authority to Operate (ATO) within designated timeframes.

(4) Subfactor 4 – Staffing Approach:

Offeror shall propose a sound Staffing Approach which identifies the necessary personnel resources given the offeror’s unique technical approach. Offeror shall submit the Staffing Matrix and identify the labor category and hours by task area and any qualifications beyond the offeror’s GSA MAS 54151S contract. The staffing approach shall also include the offeror’s plan to ensure all residential and foundational qualifications identified in PWS Appendix I, IAW DOD 8140.03M are met throughout the performance period.

(5) Subfactor 5 – Transition Plan

Offeror shall submit a transition plan to ensure personnel are available to accomplish all PWS tasks at the start of Fully Operational Capability (FOC) on 1 October 2024 as described in PWS 2.8.1 Task 8

(C) Past Performance

(1) Offeror shall submit no more than three (3) past performance references of Government (DoD, federal, state & local) or commercial contracts/work efforts which they consider relevant (has logical connection to the work described in PWS), which are currently being performed or were performed within the last three (3) years (of the quote due date), and which demonstrates their ability to perform the work identified in the past performance areas as listed in subparagraph two (2) below. A past performance reference shall be a single Government or commercial contract/work effort. The reference should correspond to the level the CPARS references (if the CPARS is done at an IDIQ level, the IDIQ should be referenced). Each reference associated with a single CPARS will be considered one reference. If CPARS reports are only reported at the IDIQ level, this should be noted. Offeror should provide a clear explanation of the relevancy of each reference submitted; however, the Government will not be bound by those statements in making its own relevancy.

(2) Note that each individual reference does not need to reflect performance in all identified performance areas. Offeror is to provide past performance information in the following performance areas as it relates to DoD, federal, state and local Government, and/or commercial experience:

(a) Performance Area 1: Experience applying agile development methodologies to develop software and experience in maintaining applications, to include fixing defects and maintaining application software, user stories, capabilities, servers, interfaces, and databases. Experience creating new capabilities, new user stories, decomposing requirements, new servers, interfaces, databases, and related functionality in support of application user communities.

(b) Performance Area 2: Experience with migrating from cloud-to-cloud environments. This includes experience working with DevSecOps CI/CD pipeline, Resiliency, Containerization, Web Services, Application Refactorization and Automation Testing. Experience with zero-trust IL-5 environment and compliance with government and cybersecurity directives. Knowledge and experience with EDI X12, UDF, and XML syntax and file formats. Experience with mapping, extracting, and ingesting UDF and XML datasets in support of EDI and Web Service data exchanges. This also includes having expertise in analyzing EDI transactions to improve the quality of these submissions and troubleshooting production issues.

(c) Performance Area 3: Experience with performing tasks in direct support of full RMF Accreditations, Vulnerability Management with Plan of Action and Milestones (POA&M), and STIG compliance. Experience with submission of full RMF packages, remediations of POA&Ms, and STIGs in continuous monitoring.