Skip to content
Current State: ALPHA - Use at your own risk / Work in Progress

Roadmap

Features we’re considering — nothing planned, promised, or guaranteed.

We’re considering moving this to GitHub for better community interaction.


  • Items listed are considerations only — not commitments
  • Features may be built, modified, or dropped
  • To influence direction: GitHub Issues

Show parts completed (aantal gereed) in operator work queue per operation.

Why: Operators want to see done vs. remaining at a glance for batch production.

Current: Data exists in operation_quantities but isn’t prominently displayed.


Calculate cycle time per piece from multiple samples, not just total time / quantity.

Why: Simple averages are skewed by setup time. Shops want accurate per-piece times for quoting.

Current: Basic calculation exists (actualTime / totalGood). No multi-sample averaging.


Dedicated remarks field for operators to leave notes for shift handoff.

Why: Quick notes that don’t fit formal issue reporting.

Current: Notes exist on various entities. No dedicated “werkbon” remarks field.


Record scrap quantity with reason codes during production, not just good parts.

Why: Capture rejects with reasons in the same workflow as production reporting.

Current: Scrap reasons configured. Database fields exist. Operator modal focuses on good parts only.


Transfer NC files directly from Eryxon to CNC machines.

Why: Eliminate manual file transfers (USB, network shares).

Current: Not implemented. Requires protocol support and significant effort.


Real-time dashboard showing job progress, completion percentages, bottlenecks.

Why: Managers want to monitor production without walking the floor.

Current: Activity Monitor shows events. No aggregated job progress view.


Display PMI (dimensions, tolerances, GD&T) from STEP files in the 3D viewer.

Why: Operators need dimensions without opening separate drawings.

Current: 3D viewer is usable for geometry. PMI would require a backend CAD service — browser-based approach has limitations.


Pre-built connectors for common manufacturing ERP systems.

Why: Lower barrier for shops without development resources.

Current: API supports sync with external_id. No out-of-the-box connectors.


Make MQTT, webhooks, and MCP connectors production-ready. Then expand features.

Why: Industrial environments expect reliable real-time data flow.

Current: Code exists but is untested and experimental — not production-ready.


See Introduction for what Eryxon explicitly does not do:

  • Financial tracking
  • Purchasing/PO management
  • Multi-level BOM management
  • Scheduling optimization
  • Built-in historical reports