The drawing revision everyone assumes they have isn't the one running in the control cabinet. Field wire adjustments during FAT vanish into unredlined local PDF copies.
Date-stamped ZIP archives, an unverified Excel checklist, and optimism. Filesystem timestamps get modified on every network copy. Nothing is cryptographically sealed.
The customer's critical variable frequency drive parameter set was never dropped into the release bundle. Plant engineering discovers this eight months later during an unscheduled midnight changeover.
"Has this ladder logic file changed since FAT signoff?" Without deterministic SHA-256 digests, no engineer on site can answer with mathematical certainty.
Viggen Release Tool— Cartoner Line 04 (Customer Handover v1.2)Export Handover Package• In ReviewCartoner Line 04 — Target Release: v1.2-handover-2025.03
Drag in artifacts by machine subsystem. PLC native backup pairs automatically with searchable schematic PDF. Viggen organizes ten industrial subsystems cleanly into local workspace nodes.
Local SHA-256 integrity, revision guard, and live closeout readiness score. Two unarchived VFD nodes or missing safety signoffs? You know before the plant manager ever runs FAT.
One master PDF dossier, one locked ZIP archive, one cryptographic checksum manifest. Fully verifiable thirty years from now with native command-line shasum. Absolute zero tool lock-in.
Early testers running real machine handovers on the Viggen alpha — quoted with permission, first names only.
“I'd been doing the native-plus-PDF pairing by hand in a spreadsheet for years. Watching Viggen flag a drawing revision clash on its own during my first real handover in it — that's the moment I stopped keeping my own spreadsheet.”
“I was skeptical because I told him I want free and local, no accounts. It actually is. Readiness dashboard at 62% told me exactly what was missing before the customer asked — normally I'd find out at the worst possible moment.”
“First tool I've used that understands a PLC backup and its PDF aren't the same thing. Export took four minutes, and the checksum manifest meant the customer's engineer could verify it without installing anything.”