Handbook › Chapter 15 of 16

🛣️Roadmap

This chapter is a single source of truth for features that are planned but not yet shipped in the version of Myncel you are reading this handbook from. Anything mentioned in earlier chapters as "on the roadmap" is listed here, grouped by area, so you know exactly what is real today versus what is coming. We update this list as features ship — when an item ships it gets removed from here and the relevant chapter is updated to describe how it actually works.

How to read this chapter

Everywhere else in this handbook we describe Myncel as it works today. If a feature is not mentioned in another chapter, it is not in the product yet. This Roadmap chapter is the only place where forward-looking items are documented, and we deliberately keep them short and unambiguous so there is no confusion between "shipped" and "planned".

If you need a planned feature urgently for a deployment, talk to us — most of these items have rough timelines and a few have customer-funded fast-tracks available.

ℹ️
Info

No promises on dates. Items here are committed in scope but not in calendar — priorities shift based on customer demand and reviewer feedback.

Equipment & onboarding

Today you add machines one at a time from the Equipment page using the "+ Add Machine" button, or in bulk via the public REST API (POST /api/machines, see chapter "Equipment & Onboarding"). The roadmap below extends that with import wizards and richer location structures.

  • CSV / Excel bulk importer in the UI — drag-drop a spreadsheet, map columns to fields, preview, import. Today only the API does bulk.
  • Named importers for common CMMS migrations — SAP PM, IBM Maximo, Limble, UpKeep, eMaint, Fiix, MaintainX, Hippo. Today: do the export from the source system to CSV, then call the public REST API.
  • OEM-specific fleet telematics importers — Toyota I_Site (forklifts), Crown InfoLink, John Deere Operations Center, Caterpillar VisionLink. Native importers for Geotab, Samsara, Verizon Connect, Motive (KeepTruckin), and Fleetio are now shipped — see /docs/telematics. The OEM-specific list above is what is still on the roadmap.
  • Equipment groups / parent-child relationships (e.g. a "Compressor pack" parent containing 4 individual compressors). Today: model each compressor as its own machine and put the pack name in the Notes or Location field.

Equipment record

The full tabbed equipment page is live today (Overview, Documents, Parts, Schedules, Timeline, Telemetry — see the Equipment chapter). The roadmap items below add deeper drill-downs on top of that foundation.

  • Embedded interactive DWG / DXF viewer with pan, zoom, layer toggling, and measurement tools (today: PDF and image preview render inline; native CAD files offer a download with a friendly "open in your CAD tool" message).
  • Document version history — keep every revision of a manual or drawing, with a side-by-side diff and rollback (today: each upload is a new row).
  • Per-machine bill-of-materials linking installed parts to the inventory catalog with low-stock alerts wired to the asset (today: the Parts tab aggregates parts ever consumed on the machine from completed work orders).

Work orders

Work orders today support assignment, priority, status, checklists, photo attachments, comments, schedules (with all 9 frequency types including BY_HOURS), labor / cost capture, and multi-step approval workflows (see the Work Orders chapter for the full approvals walk-through). The roadmap adds reusable templates and richer parts-reservation logic.

  • Reusable Work Order templates — define a "30-day Haas VF-2 PM" once, spawn it from any machine.
  • Parts reservation and auto-deduction from inventory when a WO is completed.
  • Labor timer that runs in the mobile app (today labor is entered as a number when completing the WO).

Reports & analytics

Today Myncel ships Saved & Scheduled Reports — six datasets (Work Orders, Alerts, Machines, Parts, Downtime, PM Compliance) with filterable CSV export and daily/weekly/monthly email scheduling. The roadmap layers richer analytics on top of that engine.

  • Custom field-by-field report builder with drag-and-drop columns, group-by, and pivot tables across any Myncel data model.
  • Pre-built MTBF / MTTR / OEE roll-up reports (today: derive from Work Orders + Downtime CSV exports in your BI tool of choice).
  • XLSX export with formula-friendly numeric typing and PDF export with the org logo (today: CSV only).
  • Charts inside the report — bar, line, area, pie, gauges — and an option to pin any saved report to the dashboard as a widget.
  • Role-based sharing rules (today: any org member can see any saved report; we plan to add owner-only / role-only / public visibility).
  • Conditional-formatting alert thresholds inside reports (highlight rows where a column crosses a threshold; emails the report only when at least one row qualifies).
  • Quarterly schedule cadence and arbitrary cron-string schedules (today: daily / weekly Mon / monthly 1st).

Predictive & connectivity

Today Myncel ships with 8 production-ready Edge Gateway connectors: Modbus TCP/RTU, OPC-UA, MQTT, MTConnect, BACnet/IP, Siemens S7, Rockwell EtherNet/IP, and Beckhoff ADS — each documented at /docs/edge-gateway/<protocol> with copy-pasteable YAML. The roadmap adds more protocols and richer ML.

  • SNMP connector for network and IT-OT bridge devices (printers, UPS, switches, environmental sensors).
  • Native cloud connectors for AWS IoT Core, Azure IoT Hub, and GCP IoT (today: bridge them via MQTT).
  • On-device anomaly detection (run the model inside the Edge Gateway, not just in the cloud) for low-bandwidth sites — today, the AI engine runs cloud-side. The full per-org / per-machine AI Settings panel with statistical, hybrid, and LLM-assisted models is now shipped (see the AI & Predictive Maintenance chapter).

Integrations

Today the native integrations are: Slack (channels and DMs), Microsoft Teams (adaptive-card alerts to any channel via Incoming Webhook), PagerDuty (Events API v2 with severity-aware paging), QuickBooks Online (parts purchases → bills), Google Sheets (export schedules and WOs), and Twilio (SMS alerts). Anything else can be wired through Webhooks (Settings → Webhooks). The roadmap turns the remaining most-requested webhook recipes into native one-click integrations.

  • Opsgenie native integration. Today: Webhook → Opsgenie REST API.
  • SAP S/4HANA, NetSuite, Microsoft Dynamics 365, Oracle Fusion, Sage Intacct, Xero — native ERP/accounting integrations. Today: QuickBooks Online is native; everything else via Webhooks or the public REST API.

Multi-domain expansion (vehicles, vessels, drones)

The first wave of multi-domain support is shipped — see the new "Vehicles, Vessels & UAVs" chapter for the full step-by-step. OBD-II, SAE J1939, NMEA 2000, and MAVLink connectors run on the Edge Gateway today; native importers for Geotab, Samsara, Verizon Connect, Motive (KeepTruckin), and Fleetio accept telematics directly via /api/telematics/import; and DVIR pre-trip / post-trip, USCG-style vessel pre-departure / return, and FAA Part 107-aligned UAV pre-flight / post-flight checklists are published at /docs/vehicle-templates. What is left on the roadmap below is the longer tail of EV-specific manufacturer APIs and a few additional convenience features.

  • EV-specific manufacturer APIs — Tesla Fleet API, Ford Pro, GM OnStar Business, Rivian Fleet — for fleets that have already gone electric and need OEM-grade telemetry that OBD-II cannot provide (state of charge, battery thermal, regen energy, charging-session events).
  • Native distance-frequency PM schedules (BY_DISTANCE) — today, distance-based PMs are modeled by combining the imported odometer reading with a tiny scheduled job that pivots distance into BY_HOURS triggers. A native BY_DISTANCE frequency removes that workaround.
  • Additional telematics importers — Lytx, Azuga, GPS Insight, Teletrac Navman, Wialon, on top of the five already shipped (Geotab, Samsara, Verizon Connect, Motive, Fleetio).
  • GPS-based geofence trigger — native rule type that opens a WO when a Machine's gps_lat/gps_lon enters or exits a polygon (rather than requiring a customer-side scheduled job today).
ℹ️
Info

If you are running a car dealership, trucking company, marine charter operator, drone-services company, or any vehicle-heavy fleet and you would like to be a design partner for the remaining items, contact sales — early customers in this category get accelerated implementation and influence over the priority of the EV-OEM API list.

Mobile

The mobile app covers the full technician floor workflow today — view assigned WOs, complete checklists, attach photos, scan QR codes, read the handbook offline, and (now shipped) work offline with an automatic sync queue for work-order status changes and alert resolutions (see the Mobile App chapter, "Working offline" section). The roadmap below extends the offline coverage to richer mutations and adds a few power-user touches.

  • Extend the offline queue to cover photo uploads (delayed-upload pipeline), part stock adjustments, and free-form work-order edits (today: status changes and alert resolutions only).
  • Extended offline cache with size selector up to 4 GB (for remote installers covering large sites).
  • iPadOS split-screen multitasking and external-keyboard shortcuts (cmd-N for new WO, cmd-K for global search).
  • Rich-content push notifications with embedded chart thumbnails for critical alerts.

Other

Smaller items that do not fit the categories above but are tracked.

  • Multi-language UI (today: English only; the handbook is English only).
← Previous
🛠 Troubleshooting & FAQ
Next →
📚 Glossary
Still have questions about this chapter? The AI chat at the bottom-right of every page is grounded in this handbook and answers in seconds. Or contact support.