Service scope and implementation plan
direction numberD41
Demand scenario8 items
main inputLWIR/NIR L3；LWIR L2/L3；LWIR L3；NIR/LWIR L3
Typical routeT07、T16、T19、T03、T05
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
IR321Individual detection and night counting of cattle, pigs and sheep
- Minimum input and technical route
- LWIR/NIR L3；T07
- target output
- Animal frame, ID, quantity and trajectory
- Implementation
- Product data required
- critical acceptance
- Each type of Recall, counting error, occlusion recovery
IR322Animal surface temperature and left-right symmetry screening
- Minimum input and technical route
- LWIR L2/L3；T16
- target output
- ROI Temperature, symmetry and anomaly candidates
- Implementation
- Need veterinary medicine
- critical acceptance
- Environment/hair/distance stratification; only for auxiliary screening
IR323Candidates for Breast, Hoof, and Joint Inflammatory Thermal Abnormalities
- Minimum input and technical route
- LWIR L2/L3；T16
- target output
- Local hot spots, contralateral differences and trends
- Implementation
- Requires clinical/veterinary verification
- critical acceptance
- Compare with veterinary exam/lab results
IR324Study on thermal characteristics of estrus, prepartum and stress states
- Minimum input and technical route
- LWIR L2/L3；T16
- target output
- Temperature/behavioral characteristics and research metrics
- Implementation
- Longitudinal study is needed
- critical acceptance
- Individual baselines, confounders, and statistical power
IR325Monitoring of poultry house aggregation, thermal comfort and abnormal mortality
- Minimum input and technical route
- LWIR L3；T07+T19
- target output
- Density, clustered heatmaps, and unusual events
- Implementation
- Scenario model required
- critical acceptance
- Comparison with manual inventory/environmental sensing
IR326Breeding house ventilation, insulation and equipment thermal status
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Thermal environment zoning and equipment anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compare with temperature and humidity/wind speed
IR327Surface object detection of fish schools and breeding ponds at night
- Minimum input and technical route
- NIR/LWIR L3；T07
- target output
- Fish School/Surface Event Candidates
- Implementation
- Requires surface/underwater dedicated data
- critical acceptance
- Water surface reflection/temperature difference stratification, event F1
IR328Joint analysis of feeding troughs, drinking water and animal activity thermal images
- Minimum input and technical route
- LWIR L3；T07+T19
- target output
- Individual visits, stays and unusual behavior
- Implementation
- Requires individual tracking
- critical acceptance
- IDF1, access count error
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.