Separating local and central tasks
One possible architecture processes camera images on-site and sends only count or defect events centrally. Training, reporting and device management may run elsewhere. Define what imagery is retained and what information is transmitted from the outset. Local processing does not remove responsibilities for personal data.
Practical device-selection criteria
Assess camera count, resolution, memory, power and ambient temperature alongside model size. A headline compute figure alone does not explain application latency. Evaluate the selected device through extended operation with the actual image pipeline. Cooling, reliable power and service access also belong in the installation scope.
Connection loss and updates
Decide whether connection loss allows local decisions, queues events or pauses the process. Bound queue and disk usage. Version model updates, try them on a limited device first and preserve a rollback route. Remote access needs explicit permissions, an audit trail and a secure connection.