Back to work projects

Work project at Collins Aerospace. In progress.

Quality dashboards on Snowflake

Quality reporting at Mission Systems grew up site by site, with every report pulling its own data its own way. I built one shared Snowflake backend in Power BI dataflows and put the quality dashboards on it: two global dashboards, one per SAP system, plus Defects in FIT and corrective actions from EtQ.

6
dashboards moving to the shared pipeline, and counting
30+
plants on two SAP systems, read through one model
14
separate queries retired
My role
Project lead; designed and built it myself
Timeline
2026 – Present
Tools
Snowflake, Power BI dataflows (Power Query M and SQL), DAX, scikit-learn, EtQ Reliance

The old setup

Each site's dashboard ran its own queries against SAP, with typed-in plant lists and its own definitions. Defects in FIT covered one site and depended on a scheduled Python export of an SAP report that often failed. Another site kept a separate copy of the quality dashboard and patched it by hand whenever the main one changed. Defect categories, customers and production areas lived in hand-kept classification files, and the two SAP systems store the same things in different fields.

How it's built

1. SAP tables
  • QNs, tasks and defect items (QMEL and the QM views)
  • Causes (QMUR) and inspection lots (QALS)
  • Orders, WBS, stock, users, catalog texts
2. Staging dataflows
  • One query per table, per SAP system
  • Merged into one table
3. Shared tables
  • QNs, tasks, defect items, causes
  • Inspection lots and quality stock
  • Plants, user names, material prices
4. Dashboards
  • Quality dashboard per SAP system
  • Defects in FIT
  • EtQ corrective actions

Each raw SAP table gets one staging query per SAP system, and the two merge into one table. Joins and lookups run once, in Snowflake SQL inside the dataflows, so every dashboard reads finished, named tables. Plants come from one global plant table, so a new site appears without editing a report. The second dashboard is rebuilt from a copy of the first, so every page, measure and field name matches.

I don't have direct Snowflake access, so every query and every check runs through dataflows under a data steward's credentials. Each change ships with a check query and the numbers it should return.

Fixes along the way

Sample views

Four views from the dashboards, rebuilt with made-up data. Each one shows how it's built.

What it answers: how long do QNs take to close, and is the average telling the whole story? Switch what the rows are, then sort.

QN TAT by
Sort
MedianAverageBusiness days from created to completed
Plant Emedian 19, average 27
Plant Bmedian 15, average 34
Plant Dmedian 14, average 18
Plant Amedian 12, average 21
Plant Cmedian 11, average 48
Plant Fmedian 10, average 15

Plant C: the average is 48 business days but the median is 11. Most QNs close quickly and a handful stay open for months. The median says how long a typical QN takes; the gap says where the stragglers are.

How it's built

A field parameter swaps the rows between plant, QN type, WBS and project, so one visual answers several questions. Both measures count only completed QNs, and a few long-open notifications pull the average far above the median, which is why the page shows both.

-- DAX: completed QNs only, in business days
QN TAT Median =
MEDIANX (
    FILTER ( QM11, NOT ISBLANK ( QM11[Date QN Completed] ) ),
    QM11[QN TAT (BD)]
)

QN TAT Average =
AVERAGEX (
    FILTER ( QM11, NOT ISBLANK ( QM11[Date QN Completed] ) ),
    QM11[QN TAT (BD)]
)

Made-up sample data. Plant, category and defect names are generic. The real numbers belong to Collins Aerospace.