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

A USB workflow for air-gapped machine handover

A practical commissioning stack keeps PLC exports, closeout evidence and verification on the plant laptop, with USB media used only to move controlled files.

By Zelda Fontenot·November 2, 2026·4 min read
What matters here
  1. A USB stick moves files; it does not by itself make a commissioning process air-gapped.
  2. Keep the native PLC project, readable evidence and revision record together for each release.
  3. Viggen is in development; its planned offline release workflow should be tested before adoption.

Air-gapped commissioning is not just a matter of unplugging the network cable. Controls engineers still need a reliable way to export PLC and HMI files, gather drawings and signoffs, record revisions, and give a customer evidence they can check later. A small toolchain can do that without relying on cloud storage: an approved plant laptop, the offline engineering software already used on the machine, controlled USB media and a local release process.

Membran Digital is developing Viggen for industrial automation handover. It is designed to assemble release evidence locally, with no account, cloud connection or telemetry. Viggen is listed as coming soon, so this is a workflow to evaluate against the product when available, not a claim that it can be installed and used today. Its stated Windows 10/11 support fits many plant laptops; macOS is on the roadmap.

1. Set the boundary before export

Choose the approved laptop and the USB media permitted by the plant’s security procedure. Treat the drive as a transfer path, not as proof of isolation. Confirm which machine, controller revision and handover milestone the work covers. If the plant requires scanned or registered media, follow that process. Keep unrelated files off the handover drive.

On the laptop, use the controls engineer’s existing offline PLC or HMI IDE. Export the native project or backup using the established project procedure. Include readable outputs where the engineering workflow provides them, such as a PDF representation of logic or a drawing. Do not assume an export is complete just because the IDE produced a file: check it against the machine and revision being handed over.

2. Assemble evidence as a release, not a folder dump

Gather the artifacts needed to explain the machine’s state: native backups, drawings, readable documents, test records and required signoffs. Make the relationship between a native file and its readable counterpart clear. Record the revision or handover stage in the release process, rather than relying on filenames alone.

That is the part Viggen is intended to handle. Membran says it supports content-addressed artifacts, native-to-readable PDF pairing, a revision guard, a closeout readiness score and a SHA-256 integrity ledger. It also describes a PDF dossier and ZIP export that a customer can verify without installing Viggen. Those details make it a potential local-first handover layer over the PLC IDE, not a replacement for the engineering software or for the engineer’s validation.

For background on the evidence side of the process, a disciplined FAT package structure and offline checksum check are useful starting points. The important practice is to make the release understandable to someone who did not assemble it.

3. Move the package with a deliberate USB routine

Use a controlled sequence: export to a staging location on the laptop, assemble and inspect the release, then copy the approved output to the designated USB drive. If plant procedure calls for a second person to check the package, make that review a required step before transfer. On the receiving side, copy the release into the customer’s approved location and retain the original media according to site policy.

Keep the handover package and the working project distinct. A later correction should create a new revision, not silently replace the files already issued. Viggen’s stated revision guard and release chain are meant to support that distinction, including superseding rather than editing a prior release. Engineers should still agree on revision naming and approval rules; software cannot decide whether a technical change is acceptable.

4. Verify independently, then close out

Before delivery, inspect the release contents and resolve any missing evidence or revision conflicts. Viggen describes a preflight gate, a closeout readiness score and SHA-256 checks. It also says the exported package can be verified offline with a plain shasum command. That independent check matters: a customer should not need a cloud service, an account or the release tool itself just to confirm that files match the manifest.

Test this handover path on a non-critical package before relying on it for a machine closeout. Confirm that the receiving team can open the documents, identify the intended revision and verify the checksums on its own offline laptop. A manifest can show that files match recorded hashes; it cannot prove the files are correct, complete or approved. Those remain engineering and quality checks.

Where the trade-offs sit

A USB-based, air-gapped commissioning stack limits dependence on network access, but it adds handling steps and makes version discipline more important. USB media can be lost, misidentified or used to move the wrong revision. A local release tool can make evidence and integrity checks more structured, but it does not remove the need for site security rules or technical review.

That is the practical case for a local-first handover layer: keep the PLC IDE’s native exports, readable evidence and verification data together, and make the package inspectable without connectivity. For teams evaluating Viggen, the next question is whether its offline workflow fits the plant’s approval process and the customer’s verification habits. The broader shift toward offline evidence in closeout work is covered in this industrial handover digest.

More from Membran Digital News