SharPcam analytics: build a function acceptance sheet
Turn a feature request into a model-specific test, without assuming capabilities from a code.
Updated
Principle and limits
Start with the required observation: crossing a boundary, remaining in a zone or counting a passage. Then identify where the function executes: camera, recorder or software. A supported video connection does not prove that analytics metadata reaches the receiving application. Separate device capability, event transport and the receiving application’s interpretation.
Worked example
For a line-crossing requirement, record a camera model and firmware, rule direction, target classes, schedule and intended receiver. Stage ten crossings in each direction plus ten movements parallel to the line. These small counts check configuration; they do not establish a statistically reliable detection rate. Verify timestamps and matching video at the receiver.
Installation and acceptance
The acceptance sheet should contain the source document, license, simultaneous-rule limits, stream settings and pass/fail evidence. Use the current product page and request the applicable function package before specifying a tender. The ONVIF register verifies listed conformance, not every vendor analytic.