Product Update Webinar

We take stock of what has shipped and how it affects your business and the customers running your machines. This session covers three areas: how maintenance planning has been rebuilt, how you can now access your machine data through your own AI platform, and how firmware updates reach the machine controller across an entire fleet.

Maintenance planning no longer stops at operating hours. Trigger service by calendar interval, or by what the machine itself reports: battery health, filter saturation, or any signal that matters to your service model.

The technician workflow now carries the instructions. Torque specs, part numbers, and task documentation sit where the work happens, not in a separate manual. The machine owner signs off on the technician's device, and the signature and timestamp stay with the record.

For mixed fleets, AEMP data brings multi-OEM planning into one place. And a REST API pushes maintenance events into the ticketing system you already run, with status syncing back automatically.

The result is a service organization that plans instead of reacts, and an after-sales business that scales with the fleet rather than with headcount.

Dashboards answer the questions you built them for. Everything else means an export, a spreadsheet, and an afternoon.

Connect your own AI platform, Claude, ChatGPT, or Microsoft Copilot, to the Proemion DataPlatform and ask instead. Which machines are idle. What the telemetry and fault codes looked like around a failure event. Create a maintenance ticket that already includes the machine context. Generate a fleet summary and send it out on a schedule.

The same connection opens your machine data to the systems around it. Route insights to your task- and ticket management tool, ERP, or CRM to trigger an alert, escalation, or service assignment without building a custom integration for each.

Your data stays yours throughout. The same permission model as DataPortal, no broader access, and a consent flow you control at every step: your machine data reaches an AI only when you send it there.

Firmware over the air (FOTA) is not new. Reaching past the telematics box and into the machine controller across an entire fleet is.

Controller updates run over UDS (ISO 14229), the same protocol your engineers use with a cable, without the cable and without the site visit. They stay vendor-agnostic across many controller manufacturers, so a mixed fleet does not force you into a single ecosystem.

The safeguards are built into the process: two-person approval before any campaign runs, safe-state verification before flashing against conditions you define, and a bootloader that is never touched, so a failed update leaves the controller recoverable for a remote retry. Every update carries a full audit trail with user identity and timestamp.