Different hardware, one deployment
Sites may use CPUs, GPUs, FPGAs, or system-on-chip devices from different vendors. Analytics should be deployable across suitable hardware without rebuilding the entire solution for each location.
Turn live video and sensor streams into timely, useful information—while choosing where processing runs and how the solution evolves.
Cameras and sensors produce continuous streams, but sending every frame or reading to a central service can add latency, consume network capacity, and complicate privacy or connectivity requirements. Edge analytics processes relevant data near the source and can forward events or metadata for broader review and management.
Sites may use CPUs, GPUs, FPGAs, or system-on-chip devices from different vendors. Analytics should be deployable across suitable hardware without rebuilding the entire solution for each location.
Edge systems and cloud services have different constraints. A consistent, modular deployment model helps teams operate and update analytics across both.
Lighting, camera angles, site layouts, and activity patterns shift over time. Models need a path for review and refinement so they remain useful in their actual deployment environment.
A streaming workflow can ingest video, audio, sensor, or network data; normalize it; apply machine-learning models; derive events; and present results for review. Teams can configure processing and the rules that turn model output into operational alerts.
Connect supported streams and normalize data for downstream processing.
Apply models to identify events, objects, and patterns relevant to the site.
Combine events from multiple streams with operational rules for more informed alerts.
Present events through dashboards, queries, reports, and notifications.
Real-world deployments benefit from the ability to tailor analytics, select appropriate infrastructure, and connect results to existing workflows.
Configure the processing pipeline, select models for the task, and tune rules to the needs of a stream or site.
Choose suitable compute—including CPUs, GPUs, FPGAs, or system-on-chip hardware—and deployment locations, from on-site systems to private, public, or hybrid cloud environments.
Connect analytics with cameras, sensors, business systems, dashboards, and applications through integration interfaces and development tools.
A representative solution combines edge analytics with site-management tools. The exact components and placement depend on camera compatibility, connectivity, operational requirements, and the agreed deployment.
Stage 1
Compatible IP cameras and sensors provide the input data.
Stage 2
A configurable pipeline processes streams and derives events at a suitable edge or cloud location.
Stage 3
Selected metadata and events can be presented for site monitoring, notifications, queries, and reports.
Stage 4
Development tools can support site-specific pipeline and visualization requirements.
A practical model-improvement process uses examples from deployment to identify gaps, evaluate changes, and update models deliberately. The process should include validation and monitoring rather than automatically changing production behavior without review.
Step 1
Review events and examples from real operating conditions, including cases where model confidence is low.
Step 2
Use reviewed examples to refine an existing model or develop a model for a new requirement.
Step 3
Test the candidate model against representative data and compare it with the current deployment.
Step 4
Promote a validated model through a controlled update and continue monitoring its performance.
Analytics can run on a camera-side device, an on-site gateway, an edge server, or cloud infrastructure. Distributed deployments can keep time-sensitive processing close to the camera while sending selected metadata to centralized services for management, reporting, and cross-site context.
Process streams locally for responsive analytics and site-specific requirements.
Connect multiple sites to shared tools for configuration and operations.
Use cloud or private infrastructure for centralized services where appropriate.
Hardware, camera compatibility, integrations, and feature availability should be confirmed for each proposed deployment. This guide intentionally omits hardware specifications and performance figures from older materials.
See how Echelon Platform use cases can be tailored to buildings, cities, factories, retail, and warehouses.