Testing proceeds using a settings file found on a laptop, received by email, renamed by a user, or already loaded into the relay. The report identifies the device and measured results but not a controlled filename, revision, export time, or unique digital fingerprint. Files called FINAL, FINAL-2, or Latest can contain different values while appearing to describe the same test basis.
A successful injection proves how the relay responded to one configuration at one moment. Without unique identification, nobody can later reproduce the test, compare two exports reliably, establish whether the installed file changed, or demonstrate which result belongs to which configuration. A filename alone is weak evidence because it can be renamed without changing the file-and changed without changing the name.
Record the relay and asset identity, model, serial number, firmware, settings filename, controlled revision, active group, and export timestamp. Generate a SHA-256 checksum or capture the manufacturer configuration CRC for the exact file tested. Attach the pre-test export and final installed readback, then record their fingerprints in the report. Matching fingerprints demonstrate an unchanged configuration; a mismatch triggers a documented comparison and targeted retest.
Add a mandatory Configuration Identity block to every relay test sheet: document number, revision, export timestamp, active group, file checksum or relay CRC, and final readback reference. Store the tested file with the report rather than relying on a shared-folder path. If the configuration cannot be uniquely identified, classify the result as preliminary and do not use it as final evidence.
05 · FIELD TAKEAWAYA PASS result is reproducible only when the tested configuration has a unique identity.
This note describes a recurring industry pattern using combined and simplified examples. It does not represent a particular client or project.