ONVIF Profile S Deprecation: A 2027 Purchasing Checklist

ONVIF identifies March 31, 2027 as the last date for Profile S product conformance submissions. Its deprecation Q&A includes older products submitted with new firmware or software. That administrative milestone is different from an instruction to switch off an installed camera system.

For a buyer, the useful first question is which decision is being made: retain a working installation, change its software or order equipment. Record that decision before asking for a replacement list. A deadline-only purchasing instruction can otherwise combine separate questions about support, operating risk and required interoperability.

ONVIF conformance records apply to a specific product and firmware or software version. Verify the camera and the receiving client separately in the official database. A manufacturer name, family brochure or membership claim is not the same evidence as a matching product/version record.

Create a list of the equipment that must remain and the equipment being proposed. Include the client role, such as a recorder or video-management application, beside its version. Mark unknown entries as To be confirmed. This prevents a quotation from quietly substituting a different client or firmware baseline while retaining the same camera quantity.

ONVIF states that deployed Profile S systems can continue to operate; deprecation does not itself remove their implementations. Later vendor firmware decisions can still change an authentication dependency. Obtain the relevant vendor information before treating a software change as equivalent to retaining the current installation.

The table is a proposed purchasing sequence. It does not authorize an update, determine security suitability or establish a universal replacement date. The site owner and responsible technical parties decide what changes are permitted and what evidence they require.

ONVIF names Profile T as the replacement for Profile S. The Profile T description distinguishes required capabilities from functions that depend on native support. Do not read a profile label as confirmation that every audio, event, control or transport function is available in the proposed combination.

Write the required tasks in ordinary project language: receive the intended stream, record it, retrieve it and perform any separately required event or control action. Then request the matching device/client feature evidence. Network hardening and authentication choices belong with the responsible IT and security parties; a purchasing table does not replace that assessment.

A transition register is useful when its entries can be carried from the initial request into the offered configuration. Keep an evidence reference beside each unresolved question, and record who can resolve it. Avoid a single compatible checkbox that cannot identify which version or function was considered.

The following fields are an original buyer worksheet, not an ONVIF form or certification service. Keep supplier-provided model information distinct from decisions made by the buyer, system designer or site team. Revise the record when the proposed device, client or firmware changes.

Illustrative purchasing scenario: a buyer retains a recorder and requests a replacement camera. One offer describes a camera with a Profile T record; another proposes a different camera and a client change. The profile label and camera price do not make the offers equivalent. The second option also changes the receiving equipment, configuration work and acceptance scope.

Ask each supplier to identify the exact offered configuration and the functions included in its proposal. Keep the retained recorder visible on the comparison. If evidence for that combination is unavailable, leave the item unresolved instead of converting a general profile statement into a compatibility promise. This is an illustrative decision method, not a customer case or a result of equipment testing.

Ask the responsible project team to define a permitted test arrangement and the operating tasks it must demonstrate. Record the proposed versions and test conditions before making a change. Include only the functions the project actually requires; an optional feature should not become a hidden purchasing condition after the order is placed.

Use separate outcomes for viewing, recording, retrieval and any required event or control task. A successful live picture does not describe every other operation. Keep unresolved behavior and the party responsible for the next action in the record. Do not update a live system merely to complete this worksheet, share credentials in a quotation request or infer security suitability from a successful connection.

Send a brief that lets the supplier respond to the proposed equipment rather than guess the installed system. Keep secrets and account credentials out of it. Where the buyer cannot obtain a version or feature record, identify the missing evidence explicitly and ask what model information is available.

Separate the equipment request from site configuration, engineering review and installation work. A request for a camera or recorder quotation does not automatically include permission to change firmware, network policy or operating responsibilities.

Must every installed camera be replaced by the deadline? The ONVIF submission milestone does not by itself determine the replacement scope. Review the actual equipment, vendor information and operating requirements.

Does buying a Profile T camera settle the recorder choice? Check the receiving client and required functions as well as the camera. A camera-only description does not establish the complete proposed combination.

Can a supplier confirm an unknown firmware combination from a brand name? Ask for model-and-version evidence and keep unsupported items open. Do not turn an absence of evidence into an affirmative conformance or compatibility statement.

Use the existing ONVIF compatibility guide for general profile and integration background, then bring this dated transition record to the equipment discussion. The CCTV catalogue and contact route can help identify which model information is available for a proposed purchase.

NexPro-Link quotations remain limited to agreed equipment and available model information. This article offers no blanket product conformance, manufacturer certification, cybersecurity approval or government/public-tender support. Any unknown combination needs its own evidence and a decision from the responsible project parties.