OsprioView — Conformance Workspace
Available

OSDP Conformance & Verification Testing

Compliance claims become repeatable evidence

Conformance Workspace is the Osprio View tool for semi-automated OSDP conformance testing and interoperability verification. Drive a structured test plan against a peripheral (PD) or controller (ACU) at your desk and take away a detailed report of exactly how it behaved — command by command, down to the physical layer — to qualify a device in CI and ease the path to SIA OSDP Verified. Book a walkthrough and we'll show you a full run on your own hardware.

Request a demoLaunch Osprio View ↗OSDP conformance docsOsprio View brochure (PDF)
The conformance bench

One host, two roles on the wire

A conformance run is split across three responsibilities on a shared RS-485 bus. Osprio View orchestrates the whole thing from your host; a first Osprio Mini plays the opposite role to your device under test and actively exercises it; a second Osprio Mini does nothing but listen, so the evidence behind every verdict comes from an independent witness rather than the device that generated the traffic.

Host — orchestration & verdict

Osprio View owns the run end to end: it walks the plan, tells the conformer what to do at each step, and gates progress on the results. When a step completes it reads the captured bus trace, checks the exact bytes and their timing on the wire against what the spec requires, and records a pass, fail, or not-applicable — then rolls it all into the report.

Conformer — drives the DUT

One Osprio Mini stands in as the counterpart your device expects to talk to — an ACU when you are testing a PD, a PD when you are testing an ACU. The host drives it to issue commands, provoke edge cases, and inject faults, so the DUT is exercised by a controlled peer whose behaviour is known exactly.

Capture — independent evidence

A second Osprio Mini sits silently on the same bus and records every frame in both directions. Because it never transmits, the timing and byte-level evidence it collects is impartial — the unit generating the traffic is not also the sole judge of what landed on the wire, which is what makes a verdict defensible.

Why It Exists

Catch conformance issues before they delay you

"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.

01

Test a PD or an ACU

Point the workspace at either side of the bus. When your device under test is a peripheral (PD), the conformer stands in as the controlling ACU and drives it; when it is a controller (ACU), the conformer plays the PD and answers it — so the same tool qualifies readers and controllers alike.

Declare the device once — manufacturer, model, address, firmware — and the workspace tailors the plan and the setup steps to what you are actually testing, then carries that identity through to the saved report.

02

An extensive test catalogue

Runs draw on a deep catalogue of dozens of checks organised into suites — link-layer framing, command and status handling, NAK and error behaviour, reader outputs, COMSET, secure channel, file transfer, and the manufacturer and PIV extensions. It is informed by SIA's published OSDP test matrix and extended by our own engineers, so coverage is thorough for vendors targeting the OSDP Verified program.

You are never forced to run everything. Pick and choose the suites and individual tests that matter for this device or this build — a quick smoke check today, the full matrix before a release.

03

Build the two-unit bench

Prepare the test topology right in the UI. Conformance runs on two Osprio Mini units on the same RS-485 bus: one takes the conformer role and drives the exchange, while the other sits in capture mode and passively records every frame.

That independent capture unit is what makes the results trustworthy — the device generating the traffic is not also the sole judge of what happened on the wire, so the timing and framing evidence stands on its own.

04

Run the suite or a single test

Kick off the whole plan and let the executor work through it, or drill into any one test and run it on its own while you iterate on a fix. Each check lands as pass, fail, or not-applicable against the OSDP spec, with the actual reply bytes captured alongside the expectation.

Because a plan is a structured, repeatable procedure rather than a pile of ad-hoc commands, the same run you step through at the bench doubles as a regression guard — re-run it on every firmware build to catch a conformance regression the moment it appears.

05

Guided manual steps

Some checks touch the physical world — present a card, trip a tamper, confirm an LED or buzzer fired. When a test needs a person at the device, execution pauses and a prompt spells out exactly what to do, then waits for the operator before grading the result and moving on.

Human-in-the-loop checks live in the same recorded plan as the automated ones, so nothing that requires an operator quietly falls out of coverage.

06

An evidence-backed report

Every run produces a detailed, signed-off report: per-command results with the bytes that were exchanged, a physical-layer summary of turnaround and timing, and an ordered audit trail of exactly how the device behaved, step by step.

The packet capture behind each verdict travels with the report as evidence, and the whole thing is saved to your account to revisit or export — a self-contained artifact you can archive, compare across builds, or hand to a customer or auditor.

Inside the report

A document you can defend in a room

Each run produces a detailed conformance report that records how the device 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.

01

Per-command results

Each command-level check lands as 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 it diverged from what OSDP requires.

That byte-level detail is what makes a result actionable — a firmware engineer can see the exact divergence rather than re-running the test to find out what went wrong.

02

Physical-layer summary

Turnaround and timing metrics are rolled up alongside the command-level checks, so a single report covers both protocol behavior and bus behavior.

Reading them together is what distinguishes a device that answers correctly but too slowly from one that is genuinely ready for a shared, real-world bus.

03

Audit trail

Beyond pass or fail, the report keeps an ordered record of every scenario the plan ran and how the PD responded to each one. You can go back and check exactly how a device behaved in a given situation, not just whether it passed overall.

That ordered history is what lets a report stand up to scrutiny later — when someone asks why a device was or was not signed off, the evidence is right there in sequence.

04

Shareable artifact

Export the report and hand it to a customer, integrator, or auditor. It is structured the same way every time, so the recipient can compare devices without re-reading the format on each run.

A consistent, self-describing artifact is what turns one team's bench testing into something another team can actually trust and act on.

FAQ

We get these questions a lot

Can I run OSDP conformance tests automatically in CI?

Yes. The suite runs every scenario it can drive over the bus unattended, so the same plan fits into CI — re-check each firmware build and catch conformance regressions the moment they appear.

Is this the same as SIA OSDP Verified?

No. Conformance Workspace is an independent pre-certification and CI regression tool. It is not affiliated with SIA, and its reports do not grant OSDP Verified certification — they help you find issues before formal verification.

What hardware does OSDP conformance testing need?

Two Osprio Mini units: one drives the device under test — a PD or an ACU — while the other independently monitors the bus for trustworthy timing, with no lab gear to buy.

Have a question? Ask us →

Related OSDP Tools

Explore the rest of the toolkit

OSDP Protocol Analyzer

Sniff a live RS-485 bus and decode every OSDP command and reply.

OSDP Emulator

Stand in as a CP or PD and script tests against real readers and controllers.

OSDP Provisioning Tool

Set address and baud, then key the SCBK secure channel in install mode.

Hardware

Built for Osprio Mini

Osprio Mini

Conformance runs on Osprio Mini — bench-attach the compact hardware and go, with no new lab gear to buy if you already run Mini.

Notice

Not affiliated with SIA or the OSDP Verified program

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.