Conformance Workspace is the planned OsprioView workspace for semi-automated OSDP PD conformance validation. Drive a structured test plan against a PD at your desk and take away a detailed report of exactly how it behaved — command by command, down to the physical layer. This page previews where the workspace is headed; it is not yet available in OsprioView.
"Vendor says it's compliant" is not a test result. Conformance Workspace turns that claim into something you can reproduce, measure, and disagree with — early, on your own bench and in CI — so issues surface while they're still cheap to fix. Here's what it does.
Step through the plan with the workspace as your guide — it tells you exactly what to do at the PD and what to expect at each step, prompting for the physical actions a scenario needs (present a card, trip a tamper, check an LED) and recording how the device responded.
For unattended use, the suite skips any scenario that needs a person at the PD and runs everything it can drive over the bus on its own — so the same plan fits cleanly into CI and fast re-checks.
Exercise the OSDP command surface — polls, output control, LED, buzzer, secure channel handshakes, and the rest — and record exactly how the PD under test responded to each one.
Validate baud-rate behavior, inter-byte timing, reply turnaround, and framing — the layer-1 details that decide whether a "compliant" device actually plays well on a real bus.
Run the same plan on every firmware build and compare reports automatically. Catch conformance regressions the moment they appear and confirm a fix actually held.
Bench-attach the PD, point the workspace at it, and go. No lab-time, no portable instrumentation, no waiting for a compliance window with shared hardware.
Two OsprioMini devices run conformance — one drives the PD under test, the other monitors the bus independently for trustworthy timing.
Download any run as a self-contained, timestamped PDF — a fixed snapshot you can archive and pull up later for audit, retention, or traceability long after the bench is packed up.
Each run will produce a detailed conformance report that records how the PD behaved against the OSDP command set and the physical-layer expectations — to gauge a device's readiness, compare candidates side by side, or attach to an internal interop deliverable.
Pass, fail, or partial — with the actual reply bytes captured against the expectation. The report tells you not just that something failed, but in what way.
Turnaround and timing metrics rolled up alongside the command-level checks, so the report covers both protocol behavior and bus behavior.
Beyond pass or fail, the report keeps an ordered record of every scenario the plan ran and how the PD responded to it — so you can go back and check exactly how a device behaved in a given situation, not just whether it passed overall.
Export the report and pass it to a customer, integrator, or auditor. It's structured the same way every time, so the recipient can compare devices without re-reading the format each run.
The conformance rig is a pair of OsprioMini working together — one drives the PD under test while the other watches the bus, the compact hardware that does the whole job.
No new hardware to buy: if you already run OsprioMini, a quick app switch turns the same two units into a conformance setup — no lab gear required.
Drive the whole run from the universal software surface across Linux, macOS, Windows, Android, and iOS.
Conformance Workspace is an independent pre-certification and CI regression-testing tool. Osprio is not affiliated with, endorsed by, or sponsored by the Security Industry Association (SIA). "OSDP" and "OSDP Verified" are programs and marks of SIA; SIA's OSDP Verified certification is a separate process carried out by SIA and runs orthogonally to this product.
The reports this workspace produces reflect your own testing and do not constitute, grant, or replace OSDP Verified certification. Its purpose is to help you validate a PD on your own bench and in CI — easing your way into the verification process and reducing the time-to-market delays that verification surprises can cause.