Samkit ParakProject index / 2026
← Project index

Project 03Industrial AI · Production Systems · Full-stack Engineering

HIVE OS — Industrial Operations Intelligence

A manufacturing operations system I built for HAEEV, a custom woodworking factory in India—connecting machine evidence, production flow and governed decision support in one deployable platform.

Explore HIVE OS on GitHub
HIVE OS production dashboard showing factory telemetry confidence, loss accounting, flow, autonomy and value assurance
The HIVE OS operations dashboard during factory commissioning, with evidence readiness visible alongside production decisions.View source on GitHub

StatusBuilt · Factory commissioning

My partSystem architect & developer

AreaIndustrial AI · Production Systems · Full-stack Engineering

Core toolsPython 3.12 · FastAPI · React · MQTT

01

Context

HAEEV needed a trustworthy operational picture across 15 machines and seven production areas without replacing existing equipment or giving experimental software control of machine motion. The core problem was turning uneven factory evidence—machine logs, telemetry, cut lists, scans and operator input—into decisions that people could understand, verify and safely act on.

02

My work

  • Architected and built the Python, FastAPI, SQLite and React system, including the live dashboard, REST/SSE interfaces and the factory data model.
  • Created an observation-first integration layer for Cabinet Vision exports, Maestro machine logs and commissioned MQTT, Modbus TCP and OPC-UA telemetry.
  • Implemented evidence-gated OEE, production-loss accounting, WIP and flow intelligence, predictive control, maintenance, warehouse and production-planning workflows.
  • Designed a governed autonomy layer that can shadow, recommend or approve reversible order-release decisions while remaining technically separated from PLCs, CNC controls and machine safety functions.
  • Built an offline Windows deployment and recovery path for the factory central PC and machine agents, including mutual-TLS device identities, diagnostics, backups and rollback.
03

Notes / next

What I learned

  • Industrial intelligence depends on evidence quality and operational definitions before it depends on sophisticated models.
  • A useful factory system must explain why a metric or recommendation is ready—and why it is still pending when evidence is weak.
  • Safety boundaries, conservative defaults and operator authority are architectural requirements, not final-stage compliance work.
  • Deployment, recovery and commissioning are part of the product when software has to survive on a real factory floor.

Next

  • Commission each machine passport, route, cycle model and telemetry contract against physical factory evidence.
  • Run the release controller in shadow mode and compare its decisions with named supervisors before enabling supervised authority.
  • Calibrate production forecasts and improvement experiments with completed-shift data from the live factory.

Next project / 04

Experimental Model Rocketry