EdgeVISS Cloud Manager
AI Commissioning
Describe a device instead of hand-filling a form. A draft configuration comes back with its sources shown, compiles against the real gateway before anything is written, and waits for a human to approve it — commissioning in minutes, not a support call.
Five stages, one checkpoint no draft skips. Nothing left of it touches a gateway; nothing right of it happened without a human saying yes.
1
Describe
Upload a datasheet or just describe the device in plain language — protocol, address, what each point measures.
2
Draft
A draft configuration comes back with every field marked confirmed, inferred, ambiguous, or missing — nothing is guessed silently.
3
Compile
The draft round-trips to the real gateway and compiles against its actual protocol driver, before anything is written — a config that looks right on paper still has to prove it translates.
4
Review
A human reviews and approves the exact plan that was compiled — the same one, not a re-generated one — before it ever reaches a device.
5
Verify
Once applied, pull live values and re-run verification checks on demand — proof the device is really reporting, not just that a record was created.
A draft, not an assumption
Every field, sourced
The gateway service, the MQTT connection, the device profile — all fetched live from the gateway itself. Never free-typed, never guessed.
Nothing applied unreviewed
A draft is just a draft until someone approves it. What gets approved is exactly what was compiled — there is no gap for it to drift in between.
Compiled before written
The same protocol compiler the manual commissioning workflow uses validates the draft against the real device driver first — a config that fails to compile never reaches a device.
One channel, no open port
The gateway pulls its own work over the same outbound connection it already uses for health and updates — nothing new is exposed at the site for this to work.
Still one commissioning path underneath
AI Commissioning is a second front door onto the exact same commissioning engine the guided manual workflow already uses — the same protocol compiler, the same device write, the same verification checks. Nothing about how a device actually gets commissioned changes; only how much of the form you had to fill in yourself does.
See the manual commissioning workflow →