Service scope and implementation plan
direction numberD42
Demand scenario8 items
main inputNIR/LWIR images/videos; NIR/LWIR L3;
Typical routeT07、T19、T14、T02、T16、T20
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
IR329Infrared camera trap null trigger filtering
- Minimum input and technical route
- NIR/LWIR images/videos;T07
- target output
- Animal/null frames and trigger quality
- Implementation
- Species data required
- critical acceptance
- Null trigger filtering rate, animal missing deletion rate
IR330Species identification, abundance and activity rhythm statistics
- Minimum input and technical route
- NIR/LWIR L3；T07+T19
- target output
- Species, abundance, timing and trajectory
- Implementation
- Requires expert annotation
- critical acceptance
- Recall for each type, Rejection of unknown species
IR331Long-distance thermal imaging survey of nocturnal animals
- Minimum input and technical route
- LWIR L3/L4；T07+T14
- target output
- Animal candidates, coordinates and observation records
- Implementation
- Need field data
- critical acceptance
- Distance/vegetation layering, detection rate
IR332Study on bird/bat flight trajectories and wind turbine collision risk
- Minimum input and technical route
- MWIR/LWIR L3；T07+T19
- target output
- Trajectories, speeds and risk zones
- Implementation
- Need high-speed long-distance system
- critical acceptance
- Trajectory integrity rate, distance error
IR333Observation of thermal anomalies in nests, caves and breeding grounds
- Minimum input and technical route
- LWIR L2/L3；T02+T07
- target output
- Hot targets, active times and areas
- Implementation
- Need ecological explanation
- critical acceptance
- Compare with on-site observation; species can be determined directly without hot spots
IR334Thermography research on animal surface injuries and rehabilitation
- Minimum input and technical route
- LWIR L2/L3；T16
- target output
- Symmetry, local temperature differences and recovery curves
- Implementation
- Veterinary Ethics and Truth Values Needed
- critical acceptance
- Reproducibility, diagnostic control; ancillary research only
IR335Survey of sea turtles, seals and other coastal individuals at night
- Minimum input and technical route
- LWIR L3/L4；T07+T14
- target output
- Individuals, quantities, trajectories and coordinates
- Implementation
- Species data required
- critical acceptance
- Counting Error, Target Recall
IR336Data quality and drift management for long-term ecological infrared monitoring
- Minimum input and technical route
- L3；T20
- target output
- Camera health, seasonal drift and comparable data
- Implementation
- Requires engineering implementation
- critical acceptance
- Online rate, drift detection time, cross-season consistency
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.