2023.10.11_GTP_GOPAX_RFI.docx
DOCX document 38 KB Posted
- Solicitation number
- TRANSCOM23D017
About this file
This document is a Request for Information (RFI) issued by the United States Transportation Command (USTRANSCOM) to solicit market research for the Global Transportation Planning (GTP) and Groups Operational Passenger (GOPAX) Systems Operations and Sustainment requirement. USTRANSCOM seeks to understand industry capabilities to support the sustainment, design, development, maintenance and administration of complex web applications in a cloud environment using agile scrum methods and DevSecOps practices. Responses are due by November 8th, 2023 and one-on-one virtual technical meetings will be held the week of November 13th, 2023. The anticipated NAICS code is 541511 with small business size standard of $30 million. The incumbent contract is held by General Dynamics with a period of performance from October 2019 to September 2024.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 2023.10.11_PWS_GTP-GOPAX_RFI.docx | DOCX document |
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
RFI # TRANSCOM23D017
REQUEST FOR INFORMATION (RFI)
FOR UNITED STATES TRANSPORTATION COMMAND (USTRANSCOM)
Global Transportation Planning (GTP) And Groups Operational Passenger (GOPAX) Systems
TRANSCOM23D017
1. Purpose . This RFI is being issued for informational and planning purposes. THIS IS NOT A REQUEST FOR PROPOSAL/QUOTE nor is it to be construed as a commitment by the Government. The information requested will be used within USTRANSCOM as market research to facilitate decision making (i.e., determining acquisition strategy, small business concerns, etc.) and will not be disclosed outside the Government. Proprietary information submitted shall be appropriately marked. Please note that USTRANSCOM will NOT be responsible for any costs incurred by interested parties in responding to this RFI or Virtual Meetings.
2. Description The purpose of GTP is to provide improved time-definite delivery and best-value transportation solutions to fully support combatant commanders’ movement requirements. GTP is an umbrella program composed of various applications accessed through a portal called Distribute.Mil. GTP integrates and governs enterprise-to-enterprise (E2E) distribution process optimization initiatives including continuous business process improvement, process visualization and dynamic transportation decision making. Using enabling technology, these initiatives provide operators with new insights to solve distribution pipeline challenges quickly and collaboratively yielding enhanced E2E delivery of forces and sustainment to the warfighter. GTP supports continuous and distributed joint force operations, demanding unprecedented logistics agility and precision through process improvement, organization, and information technology (IT). GTP must support global maneuvers across inter-theater distances and operational maneuver throughout the geographic (Combatant Command’s (CCMDs) Areas of Responsibility (AORs) and must be able to manage and sustain distribution and deployment support to widely dispersed joint forces over a large area of operations. The Maritime Sustainment Command (MSC) Voyage Calculator (VC) provides courses of actions (COAs) to senior leadership based on rough order of magnitude (ROM) estimates of the numerous costs associated with operating ships throughout the various stages of the voyage, such as determining fuel usage while underway and costs associated with port and canals. It is currently a new application running as part of the GTP program.
The GOPAX system fulfills the operational requirement of moving groups of passengers throughout the Continental United States (CONUS) for USTRANSCOM. GOPAX continues to provide the Command’s operational capability for securing cost-effective lift for domestic group passenger movements. The processes identified in the PWS apply to both programs, except where identified.
A draft Performance Work Statement (PWS) has been attached for your reference and includes additional details. The Government seeks comments from industry, via virtual meetings, regarding the draft PWS to clarify any ambiguities. These comments will be addressed when the final PWS and RFQ are issued. Individual responses will not be provided to comments submitted outside of the virtual meetings.
The work associated with this PWS is at the UNCLASSIFIED level.
Place of Performance: Tasks shall be performed at the Contractor’s facility and at Scott Air Force Base, IL.
Anticipated Period of Performance:
| Transition Period: | 1 September 2024 – 30 September 2024 | ||
| Base Period: | 1 October 2024 – 30 September 2025 | ||
| Option Period 1: | 1 October 2025 – 30 September 2026 | ||
| Option Period 2: | 1 October 2026 – 30 September 2027 | ||
| Option Period 3: | 1 October 2027 – 30 September 2028 | ||
| Option Period 4: | 1 October 2028 – 30 September 2029 |
3. Background Incumbent Contract Number: HTC71119FD055 Incumbent Contractor: General Dynamics Incumbent Contract Type: Firm Fixed Price & Cost Reimbursement (Travel/ODC) Incumbent Contract Acquisition Strategy: Full and Open; VA T4NG Incumbent Contract Period of Performance: 01 Oct 2019 – 30 Sep 2024
4. Information Requested Parties interested in assisting USTRANSCOM with this market research are requested to submit the following information in the format of a White Paper as outlined below. The response should be detailed (but no more than five (5) pages for Section 4 (III) Capabilities), 12 pt. Times New Roman font, and address the information requested below (title page, cover letter, table of contents, additional information, suggestions, or recommendations will not count against the page limit of 5 pages). Include designated point of contact’s (POC) name, phone number, and email address. Again, this information will support market research activities within USTRANSCOM. USTRANSCOM is seeking tailored responses.
I. Company Information:
| A. | Company Name |
| B. | Unique Entity Identification Number |
| C. | Commercial and Government Entity (CAGE) code |
| D. | POC name, phone number, and e-mail address |
| E. | Company website |
| F. | Facility clearance |
| G. | All contract vehicles under which you hold contracts and under which this requirement could be awarded (e.g., OASIS, MAS, etc.) |
II. Business size: USTRANSCOM highly encourages RFI Responses from capable businesses of all sizes; large and small business concerns, to include all the socioeconomic categories. Small Business set-aside opportunities are being considered.
A. The anticipated North American Industry Classification System (NAICS) for this effort is 541511, Custom Computer Programming Services. The Small Business Administration small business size standard for this NAICS code is $30.0 Million.
B. Based on NAICS code 541511, please indicate your business size (check one):
Small ☐ Large ☐
C. If a small business, please check all that apply to your company:
| HUBZ HUBZone Small Business |
| ☐ |
| Se Service-Disabled Veteran-Owned Small Business |
| ☐ |
| VeVeteran-Owned Small Business |
| ☐ |
| SS Small Disadvantaged Business |
| ☐ |
| W Woman-Owned Small Business |
| ☐ |
| E Economically Disadvantaged Woman-Owned Small Business |
| ☐ |
III. Capabilities: Describe your company’s abilities and interest in fulfilling USTRANSCOM’s GTP/GOPAX requirement. Include supporting information which demonstrates your company’s knowledge to meet the requirements of the PWS tasks. If no direct performance or experience with the above, please explain how you will perform tasks utilizing experienced subcontractors, through a proposed teaming arrangement or hiring qualified personnel. USTRANSCOM is not asking for disclosure of specific or detailed innovative solutions; however, specific examples would assist the Government with this RFI. Specifically address the information in the following subparagraphs:
A. Experience using agile scrum methods and tools including requirements definition (e.g., use cases), scrum, backlog reviews, feedback loop, retrospectives, team velocity, and a defined release cadence in sustaining, designing, developing, maintaining, and administering complex web applications (e.g., Java, Go, Spring) in a cloud environment B. Experience using cloud tools to stand up and configure virtual instances (e.g., VMs, load balancers, security groups) in a cloud environment including the use of Infrastructure as Code (IaC) tools (e.g., CFT, Terraform) C. Experience in administration of Red Hat Enterprise Linux (RHEL) operating system, MySQL Database, SQL Server Database, MariaDB database, Java Runtime Environment, and Apache Tomcat application/web servers D. Experience in refactoring applications to make use of stateless application, serverless computing, containerization, automated application and infrastructure deployment, automated scaling, high availability, microservices, and cost optimization E. Experience using Micro Focus Fortify Static Code Analyzer (SCA) in both traditional and cloud environments F. Experience with Kubernetes G. Experience with Amazon/AWS services including but not limited to: Elastic Compute Cloud (EC2), Elastic Kubernetes Service (EKS), Elastic Container Registry (ECR), Elastic Load Balancer (ELB), Relational Database Service (RDS) MariaDB/PostGRES/SQL Server, Elasticache, Simple Storage Service (S3), CloudWatch, CloudTrail H. Experience with implementation of DevSecOps practices such as Continuous Integration/Continuous Delivery (CI/CD) pipelines including, but not limited to: Trufflehog, SD Elements, Linter, Sonarqube, Cypress (automated testing), Docker, Gitlab, Jenkins, Grafana, ArgoCD, Confluence, JIRA I. Experience developing and maintaining data interfaces between multiple systems using Web Services, Web Services Definition Language (WSDL), Simple Object Access Protocol (SOAP), eXtensible Markup Language (XML), XML Schema Definition (XSD), Hyper Text Transfer, Protocol Secure (HTTPS), and Secure File Transfer Protocol (SFTP) J. Experience in preparing and maintaining Risk Management Framework (RMF) accreditation documentation (artifacts & evidence), Information Assurance (IA) Control implementation and Validation, Information Systems Security Engineering, and Security Technical Implementation Guides (STIGs)/Security Requirements Guides (SRGs) K. Experience or familiarity with USAF Cloud One (C1), Platform One (P1), Iron Bank, Big Bang, and Global Content Delivery Service (GCDS), Cloud Native Access Point (CNAP), SDDC Transportation Enhanced Access Management Service (TEAMS) and other Identification and Access Management (IdAM) solutions L. Provide the following project or contract information for requirements deemed similar to this effort:
· A brief description of the project
· Contract number
· Period of performance
· Was your company a prime or subcontractor?
· Dollar value of the project
· Scope of the portion of the effort your company supported
5. Virtual Technical Capability Meetings (one-on-one meetings) The Government intends to conduct virtual, one-on-one technical capability meetings to facilitate conversations between the Government and interested parties demonstrating technical capability in providing support services which closely align to the information requested above. These engagements will include contractor representatives, the contracting officer/specialist, and Government technical/ functional representatives. In order to participate in a one-on-one meeting, interested parties shall submit a white paper response outlining their specific capability pertaining to the scope and magnitude of the GTP/GOPAX requirements identified herein and include a meeting request in their white paper submission.
Upon review of all RFI responses, a Microsoft TEAMS meeting invitation will be provided via email to all interested parties the Government determines to have capability relevant to the scope and magnitude of the GTP/GOPAX requirement. Due to scheduling constraints, allocated meeting times are firm. Requests for alternate meeting dates/times cannot be guaranteed. Time slots will be for 20 minutes (5 minutes to resolve any potential connectivity issues and no more than 15 minutes for discussion). Discussions will end promptly after 15 minutes.
NOTE: Generic capability statements received in response to this RFI will not be reviewed and will not be considered for a one-on-one meeting.
Tentative dates for meetings will be the week of 13 November 2023.
6. Submission Information RFI Responses and Requests for a Virtual Technical Capability Meeting (one-on-one meeting):
I. POC
A. Contract Specialists:
Emily J. Vosse Emily.j.vosse.civ@mail.mil
B. Contracting Officer:
Amy M. Miller amy.m.miller50.civ@mail.mil
II. Submission Deadlines:
A. White Paper: Responses to this RFI must be received by the POCs identified in Section 6. no later than 10:00 AM CT on Wednesday, November 8, 2023.
i. Oral submissions of information are not acceptable and will not be accepted in response to this notice.
B. Request for one-on-one meeting: Meeting requests in response to this RFI must be included in the vendor’s white paper response and received by the POCs identified in Section 6. no later than 10:00 AM CT on Wednesday, November 8, 2023.
Attachment:
1. Draft Performance Work Statement (PWS)
File details come from the government source that posted it. Updated .