Customer-Ready Equipment Servicing Report
A Bibra Lake based commercial kitchen supplier and maintenance company uses a third party system to record their equipment maintenance runs. The system holds all the data. What it couldn't do was produce a report they were happy to hand to a customer.
They'd been through multiple vendors trying to get one.
Complications
When technicians serviced equipment, they were presented with a series of questions about each machine, which they answered in their own words.
Even though everyone was trained on how to answer, each person answered the questions slightly differently - enough that the original reports looked for specific keywords to categorise the data. A typo or slightly different wording caused the keyword matcher to fail, requiring a human to go over everything, line by line, and correct it.
What I did
I stepped in and wrote a new report generator for them, to their exact requirements. The data comes out of the system they already use, and the report comes out the other side, ready for the customer.
A sprinkling of AI in the middle interpreted the answers each technician gave, correctly understanding their actual intent and mapping that into the final report.
No new system to learn. No changing how the technicians record their work. Just the report they'd been asking for all along.
The numbers
- Before: about 3 hours of manual work per report.
- After: about 60 seconds.
- 50 reports per month x 3 hours saved = 150 hours saved per month.
Enough said.
Why this is a good example
This is exactly the kind of work I like doing. It's small. It didn't need a big project or a new platform. The business already had the data and already had the system - it just needed someone to sit down, understand precisely what the customer-facing report had to look like, and build it.
If you've got a system that holds your data but won't give it back to you in the shape you need, let's chat.