06 — VERIFICATION
Every conversion ships with proof.
A converted project is worthless if nobody can check it. Verification is the part of ScadaPort that exists so an engineer who did not run the conversion can still audit the result — and so can an auditor two years from now.
03 — LOSSLESS ROUND-TRIP
Nothing gets lost. Even what the target can't represent.
Every conversion writes a shadow file (.shadow.scdx) alongside the target project. Anything the destination platform cannot express — an animation type, a binding, a script in its original language — is preserved there, byte for byte. Convert back, and the shadow restores it. In a real round-trip test, 24 tags, 19 bindings, 2 tank animations, 7 original scripts, recipes and schedules came back intact after passing through a format that couldn't hold them.
No other SCADA converter does this. A migration with ScadaPort is reversible by design.
06 — VERIFICATION
Every conversion ships with proof.
After converting, the engine re-reads both projects and tests them against each other: every alarm threshold is swept across 7 test points and must trip identically on both sides; every tag and every screen binding is structurally matched. The result is a score, not an opinion. Then the whole output is sealed: a certificate lists the SHA-256 of the source file and of every generated file, so nobody — including us — can alter the delivery afterwards.
Certificate of Functional Equivalence
- certificate_id
- 1877c6cd2a234fb6
- engine
- scada-convert v2.2.0
- project
- Demo_Estrusore
- direction
- movicon_next → ignition
- score
- 100.0% (157 verified · 0 failed)
- alarms
- 10/10 — 7-point threshold sweep
- structure
- 147/147 tags & bindings
- source sha256
- bdb5aaa1…2da4116
- sealed
- 2026-08-05 · digitally signed
07 — THE CHECKS
What the 157 checks actually test.
| Alarm thresholds | 7-point sweep per alarm: below, at, and above every limit must trip identically on both sides |
|---|---|
| Alarm delays | activation and deactivation delays compared in milliseconds |
| Tags & UDTs | type, scaling, engineering units and default value matched per tag |
| Screen bindings | every binding resolved and matched to its source expression |
| Historian | retention window and deadband compared per logged tag |
| File integrity | SHA-256 of the source and of every generated file, recorded in the certificate |
09 — LIMITS
What the engine won't pretend to do.
No converter delivers a 100% finished project, and anyone claiming otherwise is selling you rework without a list. ScadaPort automates the mechanical 70–80% and documents the rest with surgical precision. From a real report: 2 scripts in a proprietary language were copied and flagged, not guessed; 55 graphic objects without a direct equivalent were substituted and listed one by one; device connections are documented for recreation in the target's driver layer, because writing to your live PLCs is not the converter's job. You get the exact rework list — item, screen, reason — before you pay for the conversion.