Skip to content
Samar Siddiqui
All projects

2026SMS InfoComm

Fusion Report

Live production-floor shift dashboard

  • PowerShell
  • WPF / XAML
  • REST
  • Microsoft Teams

At a glance

  • A live desktop dashboard for a server test/production floor that pulls from the internal test-tracking system and shows real-time shift KPIs: units testing, passed, failed, and idle bays.
  • Deeper analytics tabs: per-configuration and per-work-order breakdowns, top failures and a failure Pareto, a stalled-unit wall, operator performance, throughput, cycle time, and retest rates.
  • Composes a shift snapshot and pushes it to Microsoft Teams on a configurable interval, with a preview-before-send dialog and per-pane CSV export.
  • Built as a WPF app in PowerShell + XAML, organized as an API layer → report/aggregation layer → UI, with a login overlay, auto-refresh timer, and a drill-down side panel.
  • Operator- and bay-level opt-out lists (persisted to disk) keep excluded stations and people out of the tiles and rankings without code changes.

A single pane of glass for a server test floor: a live desktop dashboard that turns the shift's raw test-tracking data into the numbers a lead actually watches (how many units are testing, passing, failing, stalled, and who's producing) and pushes a clean shift snapshot straight to Teams.

Purpose

Running a server validation floor through a shift means constantly answering the same questions: how many units are under test right now, how many passed and failed, which bays are idle, which configurations and work orders are moving, where failures cluster, and how each operator is doing. That information lived in an internal test-tracking system that wasn't built to answer them at a glance. I built Fusion Report as a live dashboard over that system so a shift lead can see the state of the floor in one window, and so the recurring shift snapshot shared with the team is generated automatically instead of assembled by hand.

Development process

  • Layered PowerShell app. Even though it ships as a script, I structured it like an application: a thin HTTP client, an API layer that talks to the test-tracking backend, a reporting layer that filters to the shift window and aggregates the metrics, and a UI layer of XAML views with per-surface event handlers wired after the controls are bound.
  • WPF / XAML front end. The UI is a real windowed dashboard (KPI tiles, multiple data grids, a performance tab with charts, a drill-down side panel, and a login overlay) laid out in XAML and driven by an auto-refresh timer.
  • Shift-aware aggregation. The reporting layer computes metrics against a configurable shift window and surfaces them as deltas, breakdowns by configuration and work order, a top-failure Pareto, a stalled-unit wall, throughput, cycle time, retest rate, and per-operator ledgers.
  • Teams integration with a safety net. A snapshot builder composes the shift summary as text and posts it to a Teams webhook on a chosen interval, but always through a preview-before-send dialog, so nothing reaches the channel unseen.
  • Operational niceties. Per-pane CSV export for anything on screen, persisted opt-out lists so specific bays or operators can be excluded from tiles and rankings, and a keep-awake helper so the dashboard keeps refreshing through a shift.