RFI #
Identifier assigned to each Request for Information.
Report · Chapter 1
How a public U.S. Army Corps of Engineers RFI register becomes the foundation of a Digital Engineering analytics and AI platform.
This project develops a Digital Engineering RFI Analytics & AI Platform using a real procurement-stage Request for Information (RFI) / bidder-clarification dataset from a U.S. Army Corps of Engineers infrastructure procurement.
The goal is to show how project information stored in spreadsheets and other semi-structured sources can become a structured digital workflow for project reporting, engineering coordination, document control, automation, and AI-assisted analysis.
Scope and provenance. The actual dataset is a procurement-stage RFI / bidder-clarification register released publicly by the U.S. Army Corps of Engineers (USACE) with solicitation W912DS26BA032. The original internal system used to collect, review, and compile the questions is not verified. Autodesk Forma is presented below solely as an illustrative CDE / project-systems architecture, not as the proven origin of the Excel workbook.
For the illustrative upstream process, a project team could configure Forma Data Management as its common data environment (CDE), define information requirements, and support drawings, specifications, and models created by engineers using tools such as Revit, Civil 3D, or AutoCAD. Document-control or EDMS capabilities operate throughout information development, review, authorisation, issue, and archival, rather than appearing as one step after publication.
ISO 19650 commonly describes four CDE information states, not necessarily four physical folders:
After procurement drawings and specifications are released, prospective bidders can raise technical clarification questions. The contracting and engineering teams register, allocate, investigate, and respond to them. In a hypothetical implementation those questions might be tracked in a digital workflow system, but the source does not establish that USACE used Forma Build. Nor does it establish that every RFI was closed before the register was published.
How to read the workflow: Steps −7 to −1 describe an illustrative upstream information-management and procurement sequence. Step 0 identifies the verified public Excel source. From Step 01 onward, this portfolio project ingests and analyses that workbook. Steps 05–07 describe planned advanced analytics and AI capabilities, not established features of the original source system.
The work is designed to demonstrate capability across:
A major strength of the project is that it begins with a real publicly released procurement RFI register, rather than a synthetic portfolio dataset.
Infrastructure projects generate clarification requests during procurement and RFIs during design and construction delivery. This source specifically documents procurement-stage bidder questions and official responses.
RFIs are used when project participants need clarification on issues such as:
Because much of this information is stored as free text, it can be difficult to identify recurring engineering issues, document impacts, technical themes, or common clarification categories.
This project turns the RFI register into a structured analytical and AI-enabled platform.
The dataset comes from the U.S. Army Corps of Engineers solicitation Power Generation with Microgrid at Joint Base McGuire-Dix-Lakehurst (JBMDL), New Jersey.
Solicitation referenceW912DS26BA032
The project involves power-generation and microgrid infrastructure at Joint Base McGuire-Dix-Lakehurst in New Jersey. The wider technical context includes:
The verified source used in this project is the Excel workbook published with the federal procurement opportunity. Its internal authoring, document-management, and export software are not identified; Autodesk Forma is not established as its source.
WorkbookRFI log for posting 9.23.26.xlsx
The workbook contains approximately 111 RFI records. The original workbook will be preserved unchanged as the raw project source.
The official federal procurement opportunity is published on SAM.gov. In the Attachments section, look for RFI log for posting 9.23.26.xlsx.
A public indexed copy of the RFI workbook can also be explored on GovTribe.
The source workbook contains these main fields:
Identifier assigned to each Request for Information.
Identifies the organisation or party that submitted the RFI. This field supports counts by submitting organisation, topics by organisation, and the most active submitting parties.
Identifies the party or engineering function responsible for reviewing or responding to the RFI.
The date on which the RFI was received. This supports RFI volume over time, weekly trends, and peak clarification periods.
The original engineering or technical question. This is one of the most valuable fields because it contains unstructured engineering text. Potential derived attributes include discipline, issue type, technical topic, drawing reference, specification reference, equipment reference, and a question summary.
The official answer or clarification associated with the RFI. This supports question-response analysis, technical resolution analysis, summarisation, and semantic search.
Supplementary information that can help identify whether an RFI caused a drawing update, a specification update, an attachment issue, a document revision, or no document change.
The source status where it is populated. The original source status will be preserved. If required, a separate derived status may be created, such as Answered, Open, or Unknown.
The dataset is suitable because it combines a real construction context, structured project fields, unstructured engineering text, genuine RFI questions and responses, and relevant Digital Engineering and document-control use cases.
The technical content supports classification across:
The project will maintain clear lineage between original source data and derived fields.
The raw layer keeps the ingested record close to the source:
The clean layer standardises RFI identifiers, party names, dates, whitespace, null values, text encoding, status, and duplicates.
The enriched layer adds derived analytical and AI attributes:
The source contains approximately 111 RFI records, which is relatively small for supervised machine learning.
It also does not directly contain all fields expected in a mature RFI system, such as due date, response date, closed date, formal priority, cost impact, schedule impact, discipline, issue category, workflow history, and revision history.
Any additional fields derived using rules, manual labelling, or AI will be clearly marked as derived attributes. The project will not present inferred values as if they were present in the original source.
The final system demonstrates how a traditional RFI register can be converted into a modern Digital Engineering information platform.
A real USACE RFI workbook is ingested and cleaned using Python, modelled in SQL, visualised through Power BI, and extended in Databricks with NLP classification, document-impact prediction, semantic search, and an AI Copilot for engineering information retrieval.