Verify Synergis IX OSDP reader state beyond the online indicator

Bottom line: Use independent reader evidence when accepting the documented Synergis IX OSDP integration; keep the online icon out of the role of sole acceptance criterion.

Source fact: documented behavior

The About OSDP reader support with Synergis IX topic is the primary reference for this Synergis Softwire 12.2 integration guide discussion.

The Synergis Softwire 12.2 integration topic says OSDP readers connected through Synergis IX are displayed online in Security Center even when they are not online. The same known-issues list says offline operations and tamper state are not supported for these OSDP readers. The topic supplies specific hybrid-controller, reader-expander, firmware and reader requirements.

What the source does not establish

These statements are scoped to the documented Synergis IX integration. They are not limitations of every OSDP product or proof of behavior in a later configuration. A successful credential read also does not resolve a documented reporting or offline capability gap. Confirm current manufacturer guidance for the actual components.

Applicability questions

• Do the controller, expander, readers and firmware match the documented scope?
• Which required functions depend on offline operation, tamper state or communication supervision?
• What independent evidence can the integrator obtain for actual reader communication?
• How will operators respond when a required condition is not represented by the online display?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends a capability-gap record for each affected integration before commissioning acceptance. Separate required functions, documented support and observed test evidence in that record.

1. Have the authorized integrator compare the installed component inventory with the guide’s exact requirements. Resolve unmet functional requirements with the manufacturer and system owner before treating the integration as accepted.
2. Use an approved test rig to exercise normal credential presentation and a manufacturer-supported reader communication fault. Agree the expected evidence and operational response in advance. Record the reader behavior and the Security Center display separately.
3. Review the result with the monitoring team. Document the evidence they can rely on, the conditions the interface cannot establish and the procedure for investigating an apparently online but non-responsive reader. Keep any compensating procedure owned and subject to review.

Verification and evidence

Retain the exact models and firmware, guide version, required-capability matrix, test method, timestamps, reader observations, interface captures and operator response. Redact credential and key material from the review package.

Record failures and unresolved requirements without recasting a successful test as support for an unavailable function. Reassess after controller, reader, firmware or platform changes. These are proposed DSE commissioning checks, not a claim that a live opening has been interrupted or a customer deployment has passed testing.

Official references

• About OSDP reader support with Synergis IX — Genetec; Synergis Softwire 12.2 integration guide.

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.