About

Most factories do not lack systems — they lack systems that work as one. I have spent my career connecting them: for years the sole owner of the production test software, the firmware stations, and the data backbone across three manufacturing sites.

  • Built for floors where failure is not an option: safety-critical (SIL 3) production test and traceability
  • Data entered once, steps that cannot be skipped, reports that build themselves — the process lives in software, not in memos
  • Management gets answers in seconds; sensitive data never leaves the building
  • Everyone has AI. I make it work in production — placed where it pays back, secured, and measured before it ships
  • Two decades of SQL Server and .NET underneath — the boring, load-bearing kind of software
25+
Years in software & automation
3
Manufacturing sites supported
SIL 3
Safety-critical scope

Drive

I take over the stalled rollouts and finish them.

Integrate

I connect the systems you already run, so data is entered once and visible everywhere.

Automate + AI

I build the automation and AI that fill the gaps, on your hardware.

Approach

Scan in · track the floor · bridge the data

Scan at entry Tracked through WIP AI AI bridges the disconnects

A demo is not a system. What survives production is built in layers — the same seven, every time.

Measure first

Audit the workflows, score them, model the return. Work starts where the measured value is highest — not where the change is easiest.

Data before features

Most projects die in the data. I clean the sources and fill the gaps first, starting with what you already have.

Built like infrastructure

Production needs more than a working demo: pipelines, API layers, and the right tool for each task, reliable at scale.

AI, made to work

Everyone uses AI. Placing it right, securing it, and gating it with evals is the difference — if the score drops, it does not ship.

Built for the operator

The system has to make the operator's day shorter. Fewer steps, clearer screens, visible wins — adoption is designed, not hoped for.

Your hardware, your data

Everything can run on your own iron. Sensitive data stays inside the building, and your regulatory posture stays intact.

Written down

I write it down. The system keeps running — and improving — when I am not in the room.

Skills

Software & Architecture

System DesignData ArchitectureAPIs & Integration Internal Apps & ToolsCloud / CI-CDC# / .NET SQL ServerPython

Test & Automation

NI TestStandLabVIEWSTEM ATE / PXI / DAQHILDFT / DFM SPEATeradyne

Cyber & Safety

IEC 62443SIL 3 / IEC 61508Secure Boot PKIFirmware SigningCode Signing SDLThreat Modeling

AI Engineering

Context EngineeringMulti-model OrchestrationAI Guardrails RAG / Knowledge SystemsOn-prem LLMsAgentic Workflows Claude CodeGemini CLICodex
What's next

Let's connect your operation.

If your operation runs on disconnected systems and stalled rollouts, that is the work I take. Open to architect-level roles and embedded engagements.

Share at least one link — your profile, or the role you have in mind.