Prior Work ยท Sanitized Case Study

Turning specialist-only factory support into a usable operational system.

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

Support outcome

~75% shifted from Tier 3 to Tier 2

Linux footprint

15 production servers

Equipment scale

300+ tools monitored

Core stack

C#, WPF, SQL, Linux

The problem

Routine diagnosis depended on specialists and terminal access.

Equipment-integration support required specialist knowledge, SSH access, and manual correlation across services, equipment state, automation logs, maintenance context, and routing status. That concentrated common troubleshooting in Tier 3 and made it difficult for Tier 2 to diagnose failures safely.

The system

One operational interface across equipment, services, data, and maintenance context.

  • Unified monitoring across 15 Red Hat Linux production servers.
  • Aggregated results from three factory-automation databases.
  • Monitored services and equipment health across 300+ tools.
  • Parsed raw SECS Message Language logs by timestamp, session, link, and status.
  • Connected factory-automation state with CMMS maintenance context.
  • Added routing visibility, failover support, a TCL viewer, and bulk configuration rollout tooling.

Why it mattered

By removing much of the terminal and SSH dependency from routine support, the application shifted approximately 75% of support calls from Tier 3 to Tier 2.

Publication boundary

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