Amend 00007.pdf
PDF 121 KB Posted
- Solicitation number
- 693JK426R600002
About this file
This is Amendment 00007 to RFP 693JK426R600002 for an Airline Analysis and Scheduling Solution Application issued by the Department of Transportation (DOT). The amendment, dated March 10, 2026, extends the proposal due date from March 27, 2026, to Monday, March 30, 2026, at 10:00 AM EST, and increases the page requirement for Volume I (Technical Capacity/Approach/Frequency of Data Updates/Comprehensiveness of Historical Data) from 60 pages to 75 pages, excluding resumes and table of contents.
The amendment incorporates a modular procurement framework for AI and data integration with three primary modifications to the solicitation. First, the pricing structure is revised to require offerors to provide standalone pricing for raw data provision decoupled from software or AI applications, enabling DOT to evaluate options where data providers and AI providers function as separate entities. Second, technical approach requirements are expanded to include comprehensive explanations of data sources and methodologies for acquiring global origin-destination data, fare data, schedule data, fleet information, and advanced booking data dating back to at least 2005; detailed AI integration plans delineating AI roles in back-end infrastructure and front-end UI/UX; guardrails and models to prevent hallucinated or compromised analysis including content filters, anti-prompt injection defense, bias mitigation, grounding and fact-checking, and operational constraints; AI testing methodologies prior to and during deployment; and accuracy assurance mechanisms for data and AI-generated outputs. Third, user interface requirements are expanded to require comprehensive descriptions of functionality supporting DOT analysts in executing custom reports, advanced booking evaluations, and market queries, including details on UI customization processes and enhancement scope determination if applicable.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Additional questions. docx.pdf | ||
| Amend 00006.pdf | ||
| FINAL DOT RFQ Questions_Answers Read Only.xlsx | XLSX spreadsheet | |
| Amend 00005.pdf | ||
| Amend 00004.pdf | ||
| Amend 00003.pdf.pdf | ||
| Amend 00002.pdf.pdf | ||
| RFP Airline Analysis and Scheduling.pdf | ||
| Amend 00001.pdf | ||
| RFP Airline Analysis and Scheduling.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
RFP 693JK426R600002
Amend 00007 - Airline Analysis and Scheduling Solution Application
Date of modification:
03/10/2026
Description:
The purpose of this amendment is as follows:
1. In addition, the proposal due date is hereby changed from March 27, 2026, to Monday, March 30, 2026, at 10am EST.
2. In addition, the page requirement in section Volume I - Technical
Capacity/Approach/Frequency of Data Updates/Comprehensiveness of Historical Data is increased from 60 pages to a total of 75 pages (Excluding Resumes and Table of Content and Descriptions).
3. Incorporate a Modular Procurement Framework for AI and Data Integration into the solicitation. The following sections of the Statement of Work (SOW) and Instructions to Offerors are hereby amended to address these new requirements. See Below:
1. MODIFICATION TO SECTION 1: CONTRACT PRICING & VOLUME II (PRICE) To allow the DOT to evaluate modular procurement options where the data provider and AI provider function as separate entities, the Pricing Schedule is amended.
• Modular Pricing Requirement: Offerors should provide a standalone "Price and product subscription of just providing the data," decoupled from the overarching software or AI applications. Offerors should structure their Volume II: Cost/Price proposal to clearly separate the costs of the raw data provision from the interface and AI tools when applicable.
2. MODIFICATION TO SECTION "DESCRIPTION/TECHNICAL APPROACH" &
PART I (TECHNICAL CAPACITY) The Technical Approach requirements are expanded to include specific responses regarding data provenance, methodology, Artificial Intelligence (AI) integration, and data accuracy. Offerors must provide detailed responses to the following:
• Data Sources and Methodology: Offerors must provide a comprehensive explanation of the specific sources used to acquire all required data elements, including global origination and destination (OD) data, fare data, global schedule data, fleet information, and advanced booking data. Furthermore, offerors must detail the exact methodologies employed to collect, process, aggregate, and validate this data from these sources to ensure it meets the Department's requirements for comprehensiveness and historical availability dating back to at least 2005.
• AI Integration Plans: Offerors must provide a detailed clarification of their plans to incorporate Artificial Intelligence (AI) into the proposed applications, specifically defining the precise role AI will play within the system. This explanation must delineate how AI technologies will be integrated into both the back-end infrastructure and the front-end User Interface/User Experience (UI/UX). Furthermore, offerors must describe the mechanisms in place for system transparency, detailing how end-users will be able to verify that the AI has accurately interpreted their requests and correctly processed the underlying data.
• Guardrails and Models: For AI included offers, offerors must describe in detail how they will ensure appropriate guardrails (content filters, anti-prompt injection defense, bias mitigation, grounding and fact-checking, and operational/action constraints) and manage the AI models utilized within their solution to prevent hallucinated or compromised analysis.
• AI Testing: Offerors must specifically describe the methodology for how testing of an AI tool will be done prior to and during deployment.
• Accuracy Assurance: Offerors must detail the exact mechanisms and protocols used to ensure the overall accuracy of the data and any AI-generated outputs or business intelligence reports.
3. MODIFICATION TO "USER REQUIREMENTS" & PART III (WEB-BASED
APPLICATION) The requirements surrounding the user interface (UI) are expanded to ensure clarity on technical capabilities.
Interface Functionality: Offerors must comprehensively describe the functionality and capability of the interface, specifically demonstrating how the proposed UI will support DOT analysts in executing custom reports, advanced booking evaluations, and market queries. Where an offeror proposes to provide a UI customized to DOT needs involving an initial startup round of requirements gathering with DOT staff and/or ongoing contract lifecycle enhancements, please provide details on how the process would work and how enhancement scope will be determined.
File details come from the government source that posted it. Updated .