How Do I Combine Photos, Sensor Readings and Technician Notes Into One Record?

The photos are on somebody's phone. The thermal images are on the camera, or in a folder on a laptop that one person knows the path to. The readings are in a spreadsheet, if they got typed up, which depends on whether the shift ran long. The notes are handwritten on a form, scanned if you're lucky, in a filing cabinet if you're not.

Four systems. None of them talk to each other. And when an auditor asks what happened in the mechanical room in March, somebody spends a day reassembling it.

That's not a filing problem. It's a capture problem, and it starts at the moment the information is created.

The obvious fix is to build a process. Everyone uploads their photos to a shared drive, everyone types their readings into the same sheet, everyone scans their forms.

It fails for a reason that has nothing to do with discipline. The pieces don't have anything in common to join them on.

A photo has a timestamp from whatever phone took it. A thermal image has a timestamp from the camera, which is probably set wrong. The spreadsheet row has the date someone typed it, not the date they took the reading. The handwritten note says "Tuesday."

You can put all four in one folder. You still can't prove they describe the same moment at the same piece of equipment, and that's the only thing that makes a record worth anything.

The fix is to have one thing do all four at once.

When our robot stops at a checkpoint, it takes the thermal image, the visible photo, and the environmental readings in the same few seconds, from the same position, and attaches all of them to the same checkpoint identifier and the same run.

They're not joined afterwards. They were never separate.

The observations attach the same way. If a technician adds a note about that checkpoint, it lands on the same record rather than in a different system with a different date format.

• One place to look. You ask what happened at rack C12 in March and you get the thermal image, the photo, the temperature, the humidity, the time, and anything anyone wrote about it, together.
• Comparison that means something. Because the robot captures from the same position every pass, March and September can sit side by side and actually tell you whether something is changing.
• A record that survives being questioned. Every piece traces to a checkpoint and a run. Nobody has to remember which folder, which phone, which spreadsheet.
• No reassembly. The audit-ready version is the same version that was created on the day. Nothing is compiled later, which means nothing can be compiled wrong.

Once everything is in one record, the obvious worry is whether the record is honest.

So we made it checkable. Change a value and the record stops matching itself, and it names the field that changed. Swap one of the images and the checkpoint flags the mismatch. Delete something to make a bad month look better and the chain breaks across the gap.

The tool that runs the check works on your laptop, offline. You can take it away and verify six months of records without asking us anything.

That's the difference between a folder of files and a record. A folder is a place where you put different things. A record is something you can verifiably stand behind.