2022.01.09 BSCM SAM.gov Update.pdf

PDF 104 KB Posted

Attached to
BUSINESS SUPPORT & CONTAINER MANAGEMENT (BSCM)
Solicitation number
USTRANSCOM23D004
Issued by

View the file

Other files

File Type Posted
2022.11.01 BSCM RFI Q&A.pdf PDF
2022.10.31 BSCM RFI.pdf PDF
2022.11.01 BSCM PWS.pdf PDF
2022.10.31 BSCM PWS.pdf PDF
Questions and Answers - Posted.docx DOCX document
Appendix C - Posted.docx DOCX document
Questions and Answers - Posted.docx DOCX document
RFI BSCM.pdf PDF
BSCM PWS FY24.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SUBJECT: Acquisition Strategy, Milestone Updates, and Evaluation Factors for HTC711-23-Q- D013 Business Support & Container Management.

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 Unrestricted under North American Industry Classification System (NAICS) code 541519, Other Computer Related Services. It is the Government’s intent to award a firm-fixed price (FFP) and labor hour (LH) task order against the GSA MAS 54151S Contract to one contractor who demonstrates the ability to successfully provide support for the BSCM 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.4. When combined, non-price factors are more important than price. Technical capability is of equal importance to past performance. Within technical capability, subfactors 1, 2 and 3 are of equal importance and considered more important than subfactor 4. Subfactor 5 is pass/fail.

2. Projected Key Milestone Dates:

Issue Solicitation: 01/26/2023

Proposals Due: 02/27/2023

Proposed Award Date: 07/07/2023

3. DRAFT Evaluation Factors and Submission Requirements:

(A) Price. This volume shall contain the offerors’ 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 – PAT/JCM System Sustainment and Enhancement

Offeror shall provide their approach for continuous Functional and Technical support of the BSCM applications and components in accordance with PWS Task 3 and Task 4. The detailed approach shall include a plan for using an Agile development methodology for managing design, software development, enhancement, testing, deployment, and sustainment to ensure the BSCM tools, applications, databases, and interfaces are operational and continue to support SDDC operations, while ensuring compliance with cybersecurity directives.

(2) Subfactor 2 – Cloud One Migration

Offeror shall provide their approach for migrating BSCM to the Cloud One Environment in accordance with PWS Task 5, Subtasks 1 and 2. The detailed approach shall include a plan for ensuring the implemented DevSecOps CI/CD pipeline, Resiliency, Web Services, 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 – Accreditation Sustainment

Offeror shall provide their approach for maintaining an approved cybersecurity posture in all BSCM environments in accordance with PWS Task 11, Subtask 1 and the National Institute of Standards and Technology (NIST) Risk Management Framework (RMF) and Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) guidelines. The detailed approach shall include a plan for continuously monitoring, scanning, mitigating, and/or generating the required documentation to maintain cybersecurity/STIG compliance and achievement/sustainment of a full Risk Management Framework (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 to performing the requirements.

The Staffing Matrix shall identify the GSA MAS 54151S labor category and hours by task and subtask area; and any additional qualifications beyond the offeror’s GSA MAS 54151S contract. Only GSA MAS 54151S labor categories will be allowed. The Staffing Approach shall provide stable staffing, with types and numbers of positions proposed, that are sufficient to ensure successful performance of the requirements based on the offeror’s unique technical approach. In the event of a discrepancy in the comparison of the Staffing Matrix to the Price Quote, the Price Quote shall be considered to represent the offeror’s intent.

(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 2023 as described in PWS Task 2.

(C) Past Performance

(1) Offeror shall submit no more than four (4) 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. Since an umbrella contract or agreement (e.g. IDIQ or BPA) does not result in actual performance, it will not be considered as a valid reference; only the work performed on the resulting delivery/task order or call will be accepted. Individual deliveries/task orders awarded against a basic contract will be considered a single past performance example. 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; however, the Government will give greater consideration to references that reflect past performance in multiple 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, tools, capabilities, servers, interfaces, databases, and related functionality in support of application user communities.

(b) Performance Area 2: Experience with the Universal Services Contract (USC) or comparable commercial contract. This includes experience working with shipper and carrier data, data quality, surface cargo visibility, invoicing, import and export customs documentation, detention tracking, facilitating ocean cargo transportation. This also includes having expertise in viewing and analyzing Electronic Data Interchange (EDI) transactions, to improve the quality of these submissions.

(c) Performance Area 3: Experience with infrastructure sustainment, cloud migration, or cloud native development (i.e., CI/CD pipelines using Cloud tools, COTS resiliency processes, web services) in a restricted (i.e., IL4 and above) Cloud Service Provider Environment

(d) Performance Area 4: Experience with performing tasks in direct support of Risk Management Framework (RMF) Accreditations, Vulnerability management, STIG compliance.

File details come from the government source that posted it. Updated .