We build small, opinionated tools that solve boring problems in exciting ways. No tracking

Pair PLC backups with readable logic for long-term handovers

A machine handover needs both the native PLC backup and a readable logic export, tied to the same revision and verifiable offline.

By Sibyl Kearsley·November 12, 2026·4 min read
What matters here
  1. Pair each PLC binary backup with a PDF logic export from the same project revision.
  2. A document register should connect each file to its machine, controller, revision and checksum.
  3. SHA-256 can show that files have not changed; it cannot prove the logic is correct or safe.

A PLC backup and a PDF logic export answer different questions. The native backup is the artifact needed to restore or continue engineering work. The PDF gives a person a readable record of the logic without requiring the original engineering environment. A handover that includes only one leaves a gap: the binary may be difficult to inspect years later, while the PDF is not a substitute for the project that can be loaded into a controller.

The practical rule is simple: pair one native backup with one readable export from the same project revision, and record that relationship in the handover register. Do not treat two files with similar names as a matched pair. Revisions can diverge, and a readable printout from an earlier build can create false confidence about what the backup contains.

Make the pair before you assemble the package

Start with the controller and the project revision being handed over. Export the native PLC backup and its readable logic representation as part of the same closeout activity. If the project includes multiple controllers or distinct programs, make a separate pair for each relevant backup rather than bundling several binaries under one generic PDF.

  1. Identify the source. Record the machine or system, controller identity, project name and revision. Use identifiers that will still make sense when the commissioning team is no longer available to explain them.
  2. Export both forms. Preserve the native backup as supplied by the engineering environment. Generate the PDF logic export from that same project state. Keep original filenames if useful, but do not rely on filenames alone to establish a match.
  3. Check the readable export. Open the PDF and confirm it is legible, complete for its intended scope, and labelled with the same machine and revision as the native file. A PDF that opens is not automatically a complete or accurate representation.
  4. Record the relationship. Put the binary and PDF in the master document register as a paired set. Give each artifact its own file name and checksum, then identify which PDF documents which native backup.
  5. Verify the package offline. Recheck the files after assembling the handover copy. Record the verification results alongside the release, rather than relying on a note that the files were checked at some earlier point.

Build a register that can outlive the project team

A useful register is more than a list of filenames. For each pair, record the machine or system, controller, project and revision; the native file and PDF names; the pair relationship; and a checksum for each file. Add the export or handover date and any scope notes needed to distinguish a complete backup from a partial or purpose-specific export. Keep the register itself in ordinary, readable formats where possible, so a future recipient does not need the original authoring software just to understand what was delivered.

Exact pairing matters for auditability. If a later reviewer sees a discrepancy between the controller state and the PDF, the register should help establish which artifacts were delivered together. If an updated backup replaces an earlier one, preserve the earlier release as a prior revision rather than silently swapping a file beneath an unchanged document entry. A revision guard is useful here: it helps surface expected-versus-actual conflicts before export. The release record should make clear what changed and which paired files belong to each handover state.

Use checksums for integrity, not as a stamp of correctness

A SHA-256 checksum gives a repeatable way to detect whether a file's bytes have changed. It does not prove that the PLC logic is correct, that the PDF matches the binary, or that the machine is safe. Those are engineering and review questions. The checksum supports the narrower claim that a file checked later is byte-for-byte the same as the file whose digest was recorded.

Keep the checksum list with the release and make verification possible without a cloud service or a vendor application. Also preserve enough context to interpret the hashes: which file each one belongs to, which pair it is part of, and which release it describes. For a long retention period, readability is as important as integrity. A checksum with no durable register or understandable file labels is difficult to use.

This is the same offline constraint behind air-gapped machine handover workflows: transfer controlled files, then verify them where the work is done. Keep the release self-contained so a future recipient can inspect the documents and run a plain checksum tool without needing an account, network connection or the original release application.

Where Viggen fits

Membran Digital is developing Viggen as a local-first release tool for industrial automation handover. Its stated design includes native-to-readable-PDF pairing, a SHA-256 integrity ledger, a master document register, and exports a customer can verify without installing Viggen. It is intended to operate air-gapped, without accounts, cloud connectivity or telemetry. Viggen is listed as coming soon, so this is a handover method, not a claim that the tool is currently available.

The standard to aim for is straightforward: a future engineer should be able to identify the controller and revision, open the readable logic, locate its exact native backup, and check that the delivered files have not changed. No package can promise that every file format or tool will remain usable for 30 years. But a carefully paired backup and PDF, a durable register, and offline integrity checks make the handover far easier to examine when the original project team and software are gone.

More from Membran Digital News