Built from scratch · Field service
The report that remembers the last one.
Inspectors used to photograph a machine, drive back, and write the whole thing up in a word processor. We removed the writing.
The situation
A FUCHS report writer's day started with a drive out to site and a climb onto the machine. Then component by component across it, recording the condition of each and photographing what they saw. Then the second half of the job: back at a PC, import the images, open a word processor, and write the report.
The expensive part happens after the inspection is already over. The observation was complete on the machine. The hours went into restating it. And because the output was a document, everything the reports knew collectively stayed out of reach. Fifty inspections of the same component are fifty files, and files do not add up.
This one is not a takeover. It is the breadth proof: no inherited code, no departed vendor, a blank page.
What we did
We built a field reporting service on Azure with .NET Core and Angular. One developer, five months. Two decisions carry the whole system.
Every component keeps its own history. When an inspector reports on a component, the previous report's status is there beside the new one. Condition stops being a snapshot and becomes a trend: this part is worse than it was last time, this one is holding. That comparison is the judgement the whole inspection exists to produce, and it used to depend on whoever happened to remember the last visit.
There is no writing. A report loads carrying the memory of the last one. The inspector changes what changed, leaves the rest, and selects lookup values instead of composing sentences. Most of any report is identical to the previous one, so most of a report should never have to be typed twice. This is where the speed came from.
Where it landed
Report writers spend far less time capturing report data, and that shows up directly as reduced billable hours for the client. The second effect is slower and worth more: because every component now has a history held in fields rather than prose, the records accumulate into a data acquisition and early warning database. What is trending toward failure is a question the system can now answer. No quantity of well-written documents could ever answer it. The service runs as a Partner plan at $5,000 a month.
Your system could be the next one.
FUCHS started from a blank page rather than somebody else's code. It still started with reading the work before writing the software.
Book the audit