Service scope and implementation plan
direction numberD35
Demand scenario8 items
main inputLWIR L3;
Typical routeT07、T19、T20、T06
The project scope is determined based on samples, equipment, working conditions and written indicators; general modules, special models and multi-sensor integration are configured according to the evaluation results.
Application scenarios and development content
IR273Perimeter person and vehicle intrusion detection at night
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Goals, trajectories, transgressions and events
- Implementation
- Scenario model required
- critical acceptance
- Distance/weather stratification, false alarm/night, recall
IR274Animal invasion in forests, farms and photovoltaic fields
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Animal categories, tracks and regional events
- Implementation
- Animal data required
- critical acceptance
- Each type of Recall, null trigger rate
IR275Low-light channel entry and exit count and direction statistics
- Minimum input and technical route
- NIR/LWIR L3;T07+T19
- target output
- Number of entries and exits, trajectories and occupancy
- Implementation
- Product data required
- critical acceptance
- Counting error, occlusion layering
IR276Dwell, loiter and cluster thermal imaging analysis
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Dwell length, density and events
- Implementation
- Business rules required
- critical acceptance
- Event F1, false alarm/hour
IR277Boundary crossing by people at waterside, docks and dangerous areas
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Personnel trajectories, boundary crossing and overboard candidates
- Implementation
- Scenario model required
- critical acceptance
- Event Recall, alarm delay
IR278Nighttime search of people on rooftops, tunnels and underground spaces
- Minimum input and technical route
- LWIR L3;T07
- target output
- Candidates, trajectories and review clips
- Implementation
- Scenario data required
- critical acceptance
- Occlusion/thermal background layering, Recall
IR279Anonymous traffic statistics without saving visible faces
- Minimum input and technical route
- Low resolution LWIR L3;T07+T20
- target output
- Anonymous trajectories, counts and regional heatmaps
- Implementation
- Privacy design required
- critical acceptance
- Counting error, re-identification risk assessment, retention strategy
IR280Dual-light security camera health, registration and modal degradation monitoring
- Minimum input and technical route
- RGB-LWIR L4;T06+T20
- target output
- Online, occlusion, offset and degraded status
- Implementation
- Requires engineering implementation
- critical acceptance
- Fault injection Recall, discovery/recovery time
Implementation and delivery methods
- Project input confirmationCheck camera, spectral band, bit depth, SDK, environmental conditions, sample and acceptance true value.
- Sample verificationVerify key processing links, applicable conditions and abnormal working conditions, and determine the development scope and acceptance methods.
- Algorithm development and integrationImplement data parsing, algorithms, quality gating, interfaces and target platform deployment.
- Test acceptance and handoverRetest according to the agreed test set and target platform, and hand over the deliverables, test results and applicable conditions.
- Requirements and technical solutions, input and output and interface field definitions
- Algorithm library, model or SDK/API; delivery form is confirmed in the project plan
- Sample program, parameter configuration, error status and calling instructions
- Test set version, indicator definition, stratification results and failed sample records
- Target platform adaptation, resource usage and running delay records
- Version, dependencies, license, reproduction steps and applicable conditions description
Acceptance design
Each scenario establishes independent test cases according to "key acceptance". When sharing models across scenarios, results are reported separately for each scenario, distance, load, environment, and target size, supplemented by overall statistics.
When high-risk alarms or controls are involved, the algorithm output is used for review or linkage judgment; safety functions, regulatory responsibilities, and automatic disposal require separate design and acceptance.
Frequently Asked Questions for Enterprise Customers
Can I purchase directly based on one of the scenes?
Can be evaluated first as a separate work package. The formal scope should describe the device, data, target objects, environment, interfaces, delivery form, and acceptance thresholds.
Can it be started when there are no abnormal samples?
The data interface, normal baseline, acquisition plan and simulation/controlled test design can be completed first; the abnormal detection rate and fault classification effect can be evaluated after obtaining sufficient abnormal true values.
Can the algorithm directly trigger alarms or equipment actions?
Duration, deduplication, quality gating, manual review, communication failure and safety interlocking need to be designed based on business risks. High-risk actions should be activated after completion of independent safety mechanisms and on-site acceptance.