Section 1Files to load
09_export_powerbi.py reads data/processed/rfi.duckdb and does not change it. It writes data/processed/powerbi/rfi_star_schema.xlsx, with one sheet per table, and one CSV beside that workbook. A later run replaces those files.
Every chart is a count, a filter, or a text lookup of these 107 RFIs. fact_rfi is one row per RFI, RFI-001 through RFI-107. No fact key is missing from a dimension, and every dimension row is used at least once.
| Table | Rows | What a visual shows |
|---|---|---|
| dim_date | 9 | Received date |
| dim_party | 16 | Submitter or tasked party |
| dim_discipline | 10 | Derived discipline |
| dim_issue_type | 10 | Derived issue type |
| fact_rfi | 107 | The RFI itself |
dim_party is one list. from_party_key and tasked_party_key are two relationships to that list. In this extract the roles do not share a name.
Discipline, issue type, status, and the document flags come from 06_build_rfi_features.py. They are the labels to draw. The workbook Status column is blank on every source row.
Section 2Dates
All nine received dates fall in September 2026. calendar_year is 2026 on every row and calendar_month is 9 on every row, so a month chart is one bar. A day chart is the date visual. date_received is a real date. date_key is the integer form, such as 20260901.
| Date | RFIs |
|---|---|
| 2026-09-01 | 1 |
| 2026-09-02 | 6 |
| 2026-09-04 | 67 |
| 2026-09-10 | 11 |
| 2026-09-14 | 2 |
| 2026-09-15 | 1 |
| 2026-09-16 | 8 |
| 2026-09-17 | 3 |
| 2026-09-21 | 8 |
Section 3Parties
Six contractors submit the RFIs. Ten government or design parties are tasked to answer. A submitter chart and a tasked-party chart need both relationships to dim_party.
| Submitter | RFIs |
|---|---|
| DAVID BOLAND, INC | 71 |
| Carbon Recall Chattanooga | 11 |
| Willdan | 8 |
| Dobco, Inc. | 8 |
| Richard Group LCC | 8 |
| Schweitzer Engineering Laboratories, Inc. | 1 |
| Tasked party | RFIs |
|---|---|
| AE | 66 |
| CT | 15 |
| PM | 9 |
| JBMDL | 8 |
| AE/JBMDL | 4 |
| CT/PM | 1 |
| USACE DB | 1 |
| AE/PM | 1 |
| AE/JBMDL/PM | 1 |
| JBMDL/AE | 1 |
Section 4Discipline and issue type
Electrical is 40 of 107 RFIs, so a discipline bar chart will be led by that one category. Other and General are labels from the feature rules.
| Discipline | RFIs |
|---|---|
| Electrical | 40 |
| Other | 24 |
| General | 15 |
| Civil | 9 |
| Structural | 5 |
| Mechanical | 4 |
| Architectural | 3 |
| Quality / Inspection | 3 |
| Controls / SCADA | 2 |
| Cybersecurity | 2 |
Specification Clarification is 62 of 107. Constructability is RFI-023. Scope Gap is RFI-096.
| Issue type | RFIs |
|---|---|
| Specification Clarification | 62 |
| Compliance Requirement | 11 |
| Missing Information | 11 |
| Design Clarification | 6 |
| Inspection / Quality | 6 |
| Material Requirement | 4 |
| Interface Coordination | 3 |
| Drawing Conflict | 2 |
| Constructability | 1 |
| Scope Gap | 1 |
Section 5Status, length, and documents
Status is Answered when the response has text, and Open when it is blank. response_available repeats that split as the text values true and false. The eight open IDs are RFI-086, RFI-092, RFI-093, RFI-095, RFI-096, RFI-100, RFI-106, and RFI-107.
| Status | RFIs | response_available | Response text |
|---|---|---|---|
| Answered | 99 | true | Present |
| Open | 8 | false | Blank, word count 0 |
Every question has text. Question length runs from 9 to 335 words, with a median of 69. Response length runs from 0 to 109 words, with a median of 16. The eight zeros are the open RFIs. Use the word-count columns for a length visual. Question and response text belong in a table or a tooltip.
The document flags are Yes, No, or Unknown, read from notes. Unknown means the note is blank or only says an attachment was sent. Document update is Yes when either drawing or spec is Yes. Those 19 Yes rows are 16 that update both, 2 that update a drawing only, and 1 that updates a specification only. The 51 No rows say no specification or drawing update is required.
| Flag | Yes | No | Unknown |
|---|---|---|---|
| Drawing update required | 18 | 51 | 38 |
| Spec update required | 17 | 51 | 39 |
| Document update required | 19 | 51 | 37 |
notes has seven distinct phrases, so it is a label for a chart, not a long narrative. Fifty-one notes say no update is required, 35 are blank, and 15 say an updated specification or drawing was included. The other four notes record an attachment, a drawing update tied to RFI-47, a redundant update with RFI-08, or a specification-only update.
Section 6Fields for each visual
| Visual | Fields |
|---|---|
| RFI count | Count of fact_rfi.rfi_id |
| Received by day | dim_date.date_received |
| Submitter | dim_party.party_name through from_party_key |
| Tasked party | dim_party.party_name through tasked_party_key |
| Discipline mix | dim_discipline.discipline_name |
| Issue-type mix | dim_issue_type.issue_type_name |
| Open against answered | fact_rfi.status |
| Document impact | document_update_required, with Unknown kept as its own category |
| Question and response length | question_word_count, response_word_count |
| RFI detail | rfi_id, question, response, notes |