Tires Module
Tires are one of the most expensive line items in any fleet maintenance budget, yet that work has historically been managed through generic forms, inspection checklists, and standalone work orders never built with tires specifically in mind. This release introduces a dedicated Tires module designed around the full lifecycle of a tyre, from installation through retirement. Fleets can log inspections and tread depth readings per tyre and per position, capture photos to document condition and wear patterns over time, and build a complete service history for every tyre in the fleet. Because it lives inside the same iMarq workflow used for other maintenance tasks, technicians don’t need a separate tool or process, work orders, inspections, and tyre records all stay connected. The result is better visibility into one of the highest-cost components in the maintenance cycle, and an easier way to catch wear issues, rotation schedules, and replacement needs before they become bigger problems.
Isaac Integration
iMarq now connects directly to Isaac Instruments telematics, closing the loop between what Isaac detects on the road and what happens in the shop. Today, that gap is often bridged manually: a phone call, a paper form, a work order created after the fact, with no reliable way to track resolution or confirm that a repair actually happened. This integration removes that gap entirely.
When a driver logs a DVIR defect during a pre- or post-trip inspection, when a fault code fires, or when an odometer or hours-of-service threshold is reached in Isaac, iMarq automatically generates a work order, complete with the vehicle’s exact location at the time of the event. That work order lands directly on a technician’s mobile device, ready to action, no dispatcher relay required. The technician completes the repair in iMarq, capturing labor, parts used, photos, and sign-offs along the way. Once the job is closed, the status syncs back to Isaac to close out the DVIR, and the full maintenance record posts to your backend CMMS or EAM, so every system of record reflects the same information at the same time.
The practical result: no defect falls through the cracks, drivers get confirmation that what they flagged was actually resolved, and a complete, timestamped audit trail is ready whenever a DOT inspection or internal audit comes around.
Pinpoint: AI-Powered Document Lookup in iBot
iBot, the AI assistant built into iMarq, now includes Pinpoint, a new way to get answers straight from your equipment documentation. Instead of digging through binders or scrolling PDFs on a phone screen, a technician can simply ask iBot a question about a piece of equipment, a trailer, or a truck. Pinpoint searches across manufacturer manuals and your organization’s own maintenance documentation to find the answer, and grounds its response directly in that material rather than generating a generic or best-guess reply.
Pinpoint returns not just the answer, but exactly where it came from, down to the page number and paragraph, so technicians can verify the source in seconds and trust what they’re looking at. By combining AI-driven search with a direct link back to the source documentation, Pinpoint gives field crews faster, more reliable answers without ever losing the connection to the official record.
Also in This Release
A number of bug fixes and smaller enhancements across the platform.
