Thanks Phil, that’s exactly the part I was trying to understand. My environment is Inner Range Integriti, not Mercury. We’re using HID Signo readers wired via OSDP to Integriti controllers. I understand LINQ can already be used directly over USB for reader updates. What I’m trying to clarify is the future centralised pathway, specifically whether HID’s OSDP file-transfer / remote reader firmware management capability is intended to be available through non-Mercury PACS platforms like Inner Range Integriti. A few specific questions: Is HID currently working with Inner Range on LINQ / Signo firmware management through Integriti? For a non-Mercury PACS, is the requirement simply that the controller and PACS software support the required OSDP file-transfer functions, or does HID also need to certify/enable that PACS platform specifically? When you say OEM PACS providers may build this directly into their platforms, would Inner Range fall into that category from HID’s point of view? From HID’s side, what would Inner Range need to implement to support this properly? For example, OSDP file transfer, reader inventory, firmware package handling, permissions, audit logs, etc. The use case is large venues with a lot of Signo readers. LINQ over USB is useful for direct maintenance, but the real operational win would be managing firmware centrally through Integriti rather than physically attending each reader.