Industrial video procurement should distinguish software integration, interoperability between specified products, and any external test or formal conformance evidence required by the contract. Successful registration or video communication in a development environment does not establish compatibility with other manufacturers' products or a product-certification conclusion.
Define protocols and products first
Record protocol names and editions, device or platform roles, product models, software and firmware versions, enabled functions and network conditions. For example, the official GB/T 28181-2022 information page identifies the standard. It is not evidence that a particular product conforms to that standard.
| Verification level | Main question | Evidence to retain |
|---|---|---|
| Internal integration | Can a development version complete specified flows with a controlled test counterpart? | Build version, configuration, messages and results |
| Specified-product interoperability | Can two actual product versions complete agreed tasks? | Product combination, function inventory and test records |
| Formal conformance requirements | Are the applicable scheme's declaration or testing requirements met? | Applicable rules, declaring party and checkable documents |
| On-site business acceptance | Do the actual network and business workflow meet agreed conditions? | Deployment configuration, business results and exception checks |
Establish the applicable evidence mechanism
ONVIF's conformance process describes its self-declaration scheme tied to specific product versions. This is an example of that particular mechanism. Check the rules for other protocols or procurement projects separately. Internal logs, external test reports, manufacturer declarations and official database entries are different kinds of evidence.
Retain gaps in contracts and acceptance records
For each function, agree on software delivery, test counterparts, external products, required documents, responsibilities and retest conditions. Mark untested models, versions, alarm functions and abnormal conditions as unverified. Deliver the completed integration scope under its actual description. Planned tests must not be recorded as passed, and unsupported universal-compatibility or certification claims must not be used.
Related services: Vision hardware and embedded technology, edge AI deployment, project consultation.