May 2026 Product Updates

Until now, maintenance in DataPortal was triggered by usage – typically operating hours. This works well for machines that run consistently, but it leaves a gap for seasonal equipment, standby units, and low-utilization assets. A machine that only runs 80 hours a year still needs annual inspections. Relying on operating-hour counters alone means those services are missed.

With Maintenance 2.0, you can now schedule maintenance on a calendar basis – every 6 months, annually, or any custom interval – in addition to or in combination with usage triggers. When both are configured, the platform fires the maintenance event at the first threshold reached. This is particularly relevant for OEMs with mixed product lines, where some machines run continuously while others are used only during specific seasons or operational windows.

The result is a maintenance plan that consistently covers the entire installed base, not just the machines that happen to accumulate hours quickly. For OEMs and service organizations, this translates into more predictable planned-maintenance revenue and greater confidence that machines stay operational – including seasonal and standby units that would otherwise slip through the schedule.

Every maintenance task can now carry its own documentation – step-by-step instructions, torque specs, part numbers, or links to spare parts. Technicians see this directly in the workflow when they execute the task in the Machine Companion App.

The intent is straightforward: reduce execution errors, shorten the time it takes a less experienced technician to complete a task correctly, and eliminate the back-and-forth between the field and the workshop. For OEMs, it also standardizes service activities across a dealer network.

A persistent gap in service operations is verifying that scheduled maintenance was actually performed – not just marked complete in a system. We have addressed this by adding a task acknowledgment feature to the Machine Companion App.

After a technician completes a maintenance task, they request acknowledgment from the machine owner or operator directly on the device. The machine owner provides basic identification and signs on the technician’s screen. The signature, identification, and timestamp are stored together with the maintenance record, and the acknowledged task appears in DataPortal with a full audit trail.

For OEMs, this means a verifiable record of service delivery. For dealers, it removes a common source of disputes with customers. For machine owners, the service history reflects what actually happened on their equipment.

For OEMs that already run mature service-management systems, Maintenance 2.0 is designed to fit alongside existing tooling rather than replace it. Maintenance events generated from machine data can be pushed into external ticketing systems via REST API, and ticket status can be synchronized back – including automatic closure based on machine signals or external updates.

In environments that need only the data layer, the same APIs expose operating-hour and condition data for use in the OEM’s own maintenance workflows, without requiring adoption of the full DataPortal maintenance feature set.