diff --git a/.gitignore b/.gitignore index 51b4cfd..5b08a30 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,4 @@ local/ +case_study.css +case_study_one_page.html +case_study_one_page.md diff --git a/case_study.css b/case_study.css deleted file mode 100644 index 882b716..0000000 --- a/case_study.css +++ /dev/null @@ -1,14 +0,0 @@ -@page { size: A4; margin: 14mm; } -body { font-family: Arial, sans-serif; color: #1f2933; font-size: 10pt; line-height: 1.25; } -h1 { color: #0b4f71; font-size: 24pt; margin: 0 0 2pt; } -h2 { color: #0b4f71; font-size: 13pt; margin: 10pt 0 4pt; border-bottom: 1px solid #b8c9d3; padding-bottom: 2pt; } -h3 { color: #0b4f71; font-size: 11pt; margin: 7pt 0 2pt; } -p { margin: 4pt 0; } -table { width: 100%; border-collapse: collapse; margin: 4pt 0 7pt; font-size: 9pt; } -th { background: #0b4f71; color: white; text-align: left; } -th, td { border: 1px solid #cbd5e1; padding: 4pt; vertical-align: top; } -code, pre { font-family: monospace; font-size: 8pt; } -pre { background: #eef4f7; padding: 6pt; border-left: 3px solid #0b4f71; } -ul { margin: 3pt 0 5pt 15pt; padding: 0; } -li { margin: 1pt 0; } -strong { color: #0b4f71; } diff --git a/case_study_one_page.html b/case_study_one_page.html deleted file mode 100644 index cfb9444..0000000 --- a/case_study_one_page.html +++ /dev/null @@ -1,49 +0,0 @@ - - - - -Talk-to-Data Case Study - - - -

Talk-to-Data

-

Governance-first semantic analytics for enterprise quotation workflows

-

The challenge

-

More than 30 salespeople could depend on internal experts to answer routine quotation questions about products, discounts, and customer agreements. Manual lookup and email or chat coordination introduced an estimated 5–30 minute delay per question.

-

The approach

-

Build a proof of concept around a curated semantic layer instead of exposing raw enterprise tables to an LLM.

-
SAP ERP
-   │ daily batch
-   ▼
-Snowflake raw → dbt staging → dbt transforms
-                                  │
-                                  ▼
-                         Semantic views
-                                  │
-                                  ▼
-                    Cortex guardrails & audit
-                         ┌────────┴────────┐
-                         ▼                 ▼
-                  Snowflake UI      Internal chatbot
-

Architecture decisions

- - - - - -
DecisionWhy
Snowflake + CortexFast POC path with data, AI, and governance in one platform.
dbt layersReproducible SQL, lineage, testing, and versioned business logic.
Semantic viewsOne business contract for dashboards and natural-language queries.
Daily refreshSufficient for quotation research; avoids premature real-time complexity.
Guardrails in data layerProtection of personal and customer information, access control, freshness checks, and exception escalation are enforceable—not only prompt instructions.
-

Estimated outcome

- - - - -
SignalEstimate
Routine answer latency5–30 min → <1 min
Sales users in scope30+
Data freshnessDaily batch
Main benefitLess coordination overhead and faster quote responses.
-

These are estimates based on the human workflow, not measured production KPIs. The next delivery step is a controlled pilot that captures actual latency, adoption, escalation rate, and answer quality.

-

Delivery lesson

-

The reusable asset was not just the chatbot. It was the delivery pattern: establish the semantic contract, encode business rules, apply governance, and then expose the smallest useful interface.

-

Stack: SAP source system · Snowflake · dbt · Snowflake semantic views · Cortex Analytics · internal chatbot workspace

-

All examples are anonymized and contain no proprietary source data.

- - diff --git a/case_study_one_page.md b/case_study_one_page.md deleted file mode 100644 index 926e6bf..0000000 --- a/case_study_one_page.md +++ /dev/null @@ -1,55 +0,0 @@ -# Talk-to-Data -## Governance-first semantic analytics for quotation workflows - -### The challenge - -More than 30 salespeople could depend on internal experts to answer routine quotation questions about products, discounts, and customer agreements. Manual lookup and email or chat coordination introduced an estimated **5–30 minute delay per question**. - -### The approach - -Build a proof of concept around a curated semantic layer instead of exposing raw enterprise tables to an LLM. - -```text -SAP ERP - │ daily batch - ▼ -Snowflake raw → dbt staging → dbt transforms - │ - ▼ - Semantic views - │ - ▼ - Cortex guardrails & audit - ┌────────┴────────┐ - ▼ ▼ - Snowflake UI Internal chatbot -``` - -### Architecture decisions - -| Decision | Why | -|---|---| -| Snowflake + Cortex | Fast POC path with data, AI, and governance in one platform | -| dbt layers | Reproducible SQL, lineage, testing, and versioned business logic | -| Semantic views | One business contract for dashboards and natural-language queries | -| Daily refresh | Sufficient for the quotation research use case; avoids premature real-time complexity | -| Guardrails in the data layer | Protection of personal and customer information, access control, freshness checks, and exception escalation are enforceable—not only prompt instructions | - -### Estimated outcome - -| Signal | Estimate | -|---|---:| -| Routine answer latency | **5–30 min → <1 min** | -| Sales users in scope | **30+** | -| Data freshness | **Daily batch** | -| Main benefit | Less coordination overhead and faster quote responses | - -These are **estimates based on the human workflow**, not measured production KPIs. The next delivery step is a controlled pilot that captures actual latency, adoption, escalation rate, and answer quality. - -### Delivery lesson - -The reusable asset was not just the chatbot. It was the delivery pattern: establish the semantic contract, encode business rules, apply governance, and then expose the smallest useful interface. - -**Stack:** SAP source system · Snowflake · dbt · Snowflake semantic views · Cortex Analytics · internal chatbot workspace - -*All examples are anonymized and contain no proprietary source data.*