All workIndustrial operations software · 2026
PipeTrace
PipeTrace organizes work orders, repair activity, counts, movement, and supervisor controls around the way a working shop actually operates.
A station-first queue designed for a shared shop-floor tablet.Local PipeTrace browser verification artifact with demonstration data.- My role
- Product engineering
- Status
- Private pilot system
- Contribution
- Workflow model, resilient tablet UX, offline behavior, and role-aware operational controls.
- Next.js
- PWA
- Supabase
- Postgres
- Offline sync
01Here’s the problem
The work has to make sense before the interface can.
The data has to remain useful while the work moves between operators, stations, racks, and occasionally unreliable connections.
02What made this difficult
The environment is part of the product.
- Station workflows must remain useful when connectivity drops.
- Shared tablets still need clear operator attribution.
- Counts, corrections, and movement require an auditable history.
03Decisions that shaped it
I made the hard boundaries visible.
Start at the station
The primary path is organized around the job an operator can work next, not an office-style dashboard.
Treat sync as interface
Pending, synced, failed, and retrying events are product states instead of hidden infrastructure.
Separate fast work from control
Operators get a short station path while supervisors retain reconciliation and configuration tools.
Supervisors configure machines and allowed work away from the operator path.Local PipeTrace browser verification artifact with demonstration data.04What I built
Enough of the system to test the real seam.
- Installable Next.js PWA with local offline-first storage.
- Role-aware station, supervisor, and administrator experiences.
- Supabase and Postgres synchronization with controlled count corrections.
What is true now
A private pilot foundation for turning fragmented floor activity into traceable operational events without pretending the shop is an office.
Limits I’m keeping honest
- Customer-specific operational data is excluded from this portfolio.
- A configured pilot is not represented as company-wide production acceptance.
Next
Validate the core station and supervisor flows in the approved pilot scope before expanding the system.