Service scope and implementation plan
direction numberD39
Demand scenario8 items
main inputTIR L2/L3;
Typical routeT05、T14、T03、T02、T12、T13、T07、T19
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
IR305Online monitoring of greenhouse canopy temperature and water stress
- Minimum input and technical route
- TIR L2/L3；T05+T14
- target output
- Plant temperature, stress zones and trends
- Implementation
- Requires meteorological/irrigation true values
- critical acceptance
- Compare with leaf water potential/irrigation records
IR306Greenhouse heating pipes, ventilation and uneven heating and cooling
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Facility temperature field and abnormal equipment
- Implementation
- Partially reusable
- critical acceptance
- Check with environmental sensor/device status
IR307Risks of night-time freezing damage to flower buds, fruits and leaves of fruit trees
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Target temperature, hypothermia duration and risk proxy
- Implementation
- Required varieties/weather models
- critical acceptance
- Comparison with tissue damage/meteorological truth
IR308Abnormal heat traces on orchard irrigation lines and emitters
- Minimum input and technical route
- TIR L2/L4；T02+T14
- target output
- Exception row/drip tip and coordinates
- Implementation
- Required environment model
- critical acceptance
- Versus flow/soil moisture
IR309Fruit ripeness, sugar content and moisture content SWIR Return
- Minimum input and technical route
- SWIR/Hyperspectral L5;T12+T13
- target output
- Maturity/Composition Regression and Intervals
- Implementation
- Requires laboratory truth value
- critical acceptance
- External validation by variety/season RMSE
IR310Bruising, spoilage and internal moisture abnormalities in fruits and vegetables
- Minimum input and technical route
- SWIR/thermal image L5;T12+T13
- target output
- Defect areas and categories
- Implementation
- Need to slice/physical and chemical truth value
- critical acceptance
- Defect Recall, minimum defect, batch migration
IR311Postharvest pre-cooling and cooling uniformity
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Surface temperature profile and uneven cooling
- Implementation
- Partially reusable
- critical acceptance
- Compared with core temperature/mass, curve error
IR312Greenhouse nighttime personnel, equipment and animal safety monitoring
- Minimum input and technical route
- LWIR L3；T07+T19
- target output
- Targets, trajectories and area events
- Implementation
- Scenario data required
- critical acceptance
- Event Recall, False Alarm/Night
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.