{"id":79215,"date":"2026-09-15T09:34:47","date_gmt":"2026-09-15T12:34:47","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=79215"},"modified":"2026-09-15T16:16:02","modified_gmt":"2026-09-15T19:16:02","slug":"onvif-access-control-profiles-a-c-d-interoperability","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/onvif-access-control-profiles-a-c-d-interoperability\/","title":{"rendered":"ONVIF in Access Control: Profiles A, C and D, Interoperability and Design Criteria"},"content":{"rendered":"\n

ONVIF in access control<\/strong> is the use of ONVIF standardized interfaces to enable interoperability between devices and clients in IP-based electronic access control systems. In this domain, the core profiles are ONVIF Profile A<\/strong>, focused on configuring credentials, schedules and access rules; ONVIF Profile C<\/strong>, focused on door control and event management; and ONVIF Profile D<\/strong>, focused on peripherals such as readers, locks, sensors, keypads and biometric devices.<\/p>\n\n\n\n

This scope differs from the better-known use of ONVIF in video surveillance. The term ONVIF is widely associated with cameras and VMS platforms, but Profiles A, C and D specifically address the physical access ecosystem. In design, the ONVIF logo or a generic statement that a product \u201csupports ONVIF\u201d is not enough: it is necessary to verify which profile<\/strong>, the product’s role as device or client<\/strong>, which functions are mandatory or conditional<\/strong>, which firmware\/software version appears in the official conformance database<\/strong>, and whether the set of functions required by the design is actually covered.<\/p>\n\n\n\n

ONVIF is not a single protocol or a generic guarantee of compatibility<\/h2>\n\n\n\n

ONVIF is a standardization initiative for interfaces used by IP-based physical security products. Functionalities are organized into specifications and profiles<\/strong>. Each profile brings together a fixed set of capabilities that conformant devices and clients must implement at the levels defined by ONVIF.<\/p>\n\n\n\n

This means that the question \u201cdoes the equipment have ONVIF?\u201d is incomplete. Two products may be ONVIF conformant and still support different profiles intended for different functions. A Profile D reader and Profile A software, for example, are not automatically equivalent and do not perform the same role in the system.<\/p>\n\n\n\n

The general article What is ONVIF?<\/strong> should remain the reference for the broader concept. Here, the focus is the specific application to physical access control and the functional differences among Profiles A, C and D.<\/p>\n\n\n\n

Profiles A, C and D cover different layers of access control<\/h2>\n\n\n\n
\n

ONVIF must be specified by function: profile, device\/client role, features and conformant version. \u201cONVIF compatible\u201d alone does not define interoperability.<\/p>\n\n\n\n

Learn about Access Control System Design<\/a><\/p>\n<\/div>\n\n\n\n

ONVIF describes the three profiles as complementary:<\/p>\n\n\n\n

Profile<\/td>Main focus<\/td>Examples of functions<\/td><\/tr>
Profile A<\/td>access control configuration<\/td>credentials, schedules, rules and privileges<\/td><\/tr>
Profile C<\/td>door control and events<\/td>site, doors, access points, events and alarms<\/td><\/tr>
Profile D<\/td>access control peripherals<\/td>readers, biometrics, keypads, sensors, locks and displays<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This separation matters because interoperability must be specified by function. A design that requires only \u201cONVIF\u201d without stating the profile and expected function leaves room for products that are formally ONVIF compatible in another area but unsuitable for the contracted access integration.<\/p>\n\n\n\n

Functional relationship among ONVIF Profiles A, C and D in an access control system<\/title>