Provisioner Workspace is the OsprioView workspace for commissioning OSDP devices in the field. Set the PD address, switch baud rates, and — when the PD is in install mode — push the SCBK directly, so secure-channel keying is no longer the painful step of a deployment.
Before Provisioner Workspace, getting a Secure Channel Base Key onto a freshly installed PD meant choosing between two bad options. Both have shipped real deployments — neither is how a secure protocol should be commissioned.
Unmount the PD, take it back to the control panel or a benched-out rig, key it there, then reinstall it on the wall. Every extra handling step is wasted technician time and another chance to damage hardware or wiring.
Leave the PD in install mode on a live bus and set the SCBK there. Install mode accepts unauthenticated key writes, so anything else listening on RS-485 during that window can capture or spoof the exchange.
Talk to one PD over a controlled session, push address, baud, and SCBK while it's in install mode, then move on. No unmount, no live-bus key leak, no separate vendor tooling.
Provision one PD at a time from a quick-step queue, or stage a slot-backed batch plan of up to 126 devices. On capable hardware the device works through a batch autonomously while disconnected and backfills progress when you reconnect.
Set each PD's bus address with a sequential, random, or manual strategy. Give every device a deterministic address and skip the DIP-switch shuffle.
Move a PD to the baud rate the deployment actually runs at without juggling separate tools or vendor utilities.
When the PD is in install mode, push the Secure Channel Base Key over a controlled point-to-point session — the key never crosses a live, populated bus.
After keyset, the new key is verified by completing a fresh secure-channel handshake with it, and the PD leaves install mode — so it stops accepting unauthenticated key writes and is handed to the production bus in secure operation.
Track every PD's state and attempt count with precise failure outcomes — no response, wrong address, SCBK rejected, baud mismatch, and more. Try, retry, skip, or reset any step, and let auto-verify re-read each target after programming.
Save site profiles once and import them as JSON across many devices on the same job. No re-typing addresses, baud settings, or capability checks per PD.
Export the provisioned SCBKs as CSV or JSON for your key-management tooling. Per-PD keys are derived locally from a device-held seed that never touches disk — only the completed devices' keys leave the app, and the seed never does.
Most OSDP deployments are only as secure as the moment their SCBK gets installed. Provisioner Workspace moves that moment into a controlled session against a single device, verifies the new key by re-handshaking the secure channel with it, and leaves the PD with install mode disabled — so the device joins the production bus already locked into secure operation and the rest of the protocol's guarantees actually hold in the field.
Carry the workspace to the device on battery-backed field hardware. Provision multiple PDs in a single trip without tethering to a laptop.
Use a compact USB-attached unit when the install scenario is benched or staged, with the same provisioning behavior as the larger platform.
Drive everything from the universal software surface across Linux, macOS, Windows, Android, and iOS.