Prior Work ยท Sanitized Case Study

One troubleshooting surface across eight production data sources.

Frank designed and built this production application suite while serving as a manufacturing equipment engineer. It is prior employment work, not a Mozingo Systems client engagement.

Data footprint

8 production sources

Application scale

Roughly 23 screens

Core stack

C#, WPF, SQL Server, Dapper

The problem

A single investigation meant searching across separate systems.

Process engineers, equipment engineers, and engineering management had to assemble context from factory automation, MES, maintenance, parts, inventory, work-order, and incident systems. Many engineers did not know SQL or the SQL Server structure well enough to locate the correct data directly. The fragmentation slowed troubleshooting and made cross-system relationships difficult to see.

The system

A production application built around the engineers' actual troubleshooting workflow.

  • Unified eight production data sources in one interface.
  • Combined equipment state, alarms, commands, events, run logs, maintenance, work orders, inventory, parts, and incident information.
  • Provided roughly 23 screens for equipment selection, drill-downs, scheduled maintenance, and work-order search.
  • Correlated wafer-lot scrap and incident records with equipment and process context.
  • Used Dapper-based data-access layers across the multi-source application.
  • Shipped to factory engineering through ClickOnce deployment.

The repeatable pattern

Three of the same factory-automation data sources later became part of the Equipment Integration Dashboard: find where operational context is scattered, normalize access to it, and put it in the workflow where decisions are made.

Publication boundary

This case study deliberately omits the former employer's internal hostnames, database names, account details, credentials, source code, repository metrics, and private repository links.