Overview
NCAM is a Manufacturing Execution System (MES) focused on OEE (Overall Equipment Effectiveness) and shop-floor visibility. It helps teams understand what’s happening on their machines in near real-time, and—more importantly—why performance changes over time (downtime, slow cycles, micro-stops, operator context).
What it does
- OEE dashboards to track availability, performance, and quality
- Downtime tracking with categorization (planned vs unplanned, root-cause tags)
- Shift / time-window analytics to compare lines, machines, or time periods
- Operational reporting for continuous improvement workflows
My contributions (high level)
- Dashboard UX: turning raw events into clear, actionable visualizations
- Data modeling: structuring machine events, states, and aggregations so analytics stay fast
- Workflow design: making it easy to go from “metric looks off” → “here’s the reason” → “here’s what we changed”
Why OEE needs a good product layer
OEE tooling often fails when it’s either:
- Too technical (engineers can’t quickly use it day-to-day), or
- Too shallow (nice charts, but no path to diagnosis).
NCAM is designed to bridge that gap by pairing metrics with context and a practical workflow for continuous improvement.
Tech stack (high level)
- Frontend: Next.js + TypeScript + Tailwind CSS
- Backend/API: Node.js (service/API layer)
- Data: MongoDB
Links
- Website:
https://ncam.io - GitHub org:
https://github.com/ncam-io