Genset Digest / Maintenance & Operation Guides / Image files in the service record
Image files in the service record: formats, loops and what a technician needs
The photographs and diagrams in a service file are evidence, and evidence wants boring formats: files that open on any machine, degrade gracefully, and survive being copied for twenty years. The exotic part of the record, the animated sequence that shows a sequence of positions or states, is the part that needs the most care.
A service record accumulates images the way it accumulates readings: rating plates, damage photographs, screen captures, diagrams, and occasionally a sequence, a leak that drips, a damper that travels, a gauge needle that swings. Most of it belongs in the plainest formats available. The animated sequence is the exception, and the engineering behind a format that looks trivial is genuinely instructive: animated GIFs in Java is a technical guide to building and processing GIF sequences, covering timing, loops, colour tables, disposal methods and the handling of malformed input, and it reads like a checklist for anyone who has to produce or repair such files.
What an image in a record has to survive
Decades, copies and bad viewers. The file that opens today on the latest phone must also open on whatever is reading the record in fifteen years, which argues for formats with published, stable specifications and multiple independent implementations. It must also survive being copied, renamed, attached to reports and embedded in other documents, so the meaningful information belongs in the file itself, not in a filename or a folder position that the next migration will lose.
When is an animated sequence worth keeping?
When motion is the evidence. A sticking damper, a hunting governor, a weeping seal: some findings are genuinely clearer as a short loop than as ten stills. The trade-off is durability and control. A useful sequence fixes its timing so states can be read, loops deliberately rather than accidentally, and stays small enough to live inside a report. The details that separate a readable loop from a broken one, frame delays, disposal between frames, colour limits, are exactly what the format's documentation treats as engineering rather than as decoration.
Prefer formats a stranger's machine can open without the internet. A record image that needs a specific app or an online viewer is already half lost.
Filing so the image can be found
An image joins the record the same way a reading does: dated, attributed, and tied to the entry it evidences. The naming convention matters less than the index that links file to event, which is the same index discipline behind the digital file behind the set and the paper trail in the printed record guide. Where the image is part of a test report, it belongs inside that report, as the test sheets described in the standards and documents page assume.
The quiet audit
Once a year, open the file and open the images. The exercise finds the corrupted attachment, the photograph that exists only inside an old email, the sequence that no current viewer plays correctly. It is the visual counterpart of the tested restore: the record is real only when someone has checked that it still reads. The audit is also where formats are re-argued: anything that needed special software to open is a candidate for conversion to something duller, because dull formats are the ones that outlive their applications.
Capturing images worth keeping
The service photograph is taken for a reader who was not there, so it is composed like evidence: the fault in frame with enough context to locate it, a scale or a familiar part for size, light that shows the subject rather than the photographer's skill. The pair of photographs that record a finding, wide for location and close for detail, answers most of the questions the next engineer will ask.
What is left out matters as much. Screenshots cropped to the error number lose the timestamps that make them evidence; photographs taken only of the defect cannot later prove where it was. The habit is to shoot one frame wider than instinct suggests and to let the file keep its original name and date until it is filed, because the metadata is part of the chain of custody.
Migration is the quiet threat nobody schedules. Every office move, computer replacement and software upgrade is an opportunity to lose the images silently, not by deletion but by orphaning, the files survive but the link from record to image does not. The migration checklist is therefore part of the image discipline: before the move, a count; after it, the same count, and a spot check that the links still resolve.
It is also worth deciding what not to keep. A folder of five hundred undifferentiated photographs is harder to use than a hundred captioned ones, so the filing rule includes a culling rule: keep the frame that shows the finding and the frame that shows the place, and let the rest go. The record that is pruned is the record that gets read.
The formats' own documentation is part of the toolkit too. Knowing that a GIF holds a colour table, a delay per frame and a disposal method is what lets a corrupted sequence be diagnosed rather than re-taken, and a record that can diagnose its own files outlives the software that made them.
It is a modest discipline, like everything else in the record. Choose durable formats, capture with the stranger in mind, file against the event, audit once a year, and let the exotic formats be earned rather than accumulated. The record that follows those rules is the record that still opens in twenty years.
Sources
Read next
When the record has to speak for money, the paperwork behind a paid invoice follows the same evidence logic into a dispute.
For the file structure these images live in, see the digital record guide and the documentation resources.