Service scope and implementation plan
direction numberD38
Demand scenario8 items
main inputTIR L2/L4; TIR+multispectral L4; VIS+NIR L4;
Typical routeT14、T12、T13、T07、T11
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
IR297Canopy temperature and crop water stress zoning
- Minimum input and technical route
- TIR L2/L4；T14
- target output
- Canopy temperature, CWSI/stress proxies and plot plots
- Implementation
- Meteorological/base temperature required
- critical acceptance
- Compared with leaf water potential/soil moisture, plot error
IR298Identification of uneven irrigation, blockages and water shortage areas
- Minimum input and technical route
- TIR+Multispectral L4;T14
- target output
- Abnormal rows/areas, irrigation review points
- Implementation
- Requires plot true value
- critical acceptance
- Versus flow/soil moisture, area IoU
IR299NDVI, red edge and growth zoning
- Minimum input and technical route
- VIS+NIR L4；T14
- target output
- Vegetation index, coverage and zoning
- Implementation
- Reflectivity correction required
- critical acceptance
- Comparison with ground quadrat/leaf area index
IR300Leaf water content and drought SWIR index
- Minimum input and technical route
- NIR+SWIR L4；T12+T14
- target output
- Moisture Index and Change Chart
- Implementation
- Need to correct across dates
- critical acceptance
- Compare with moisture content/leaf water potential
IR301Early thermal/spectral anomaly candidates for pests and diseases
- Minimum input and technical route
- TIR+NIR/SWIR L4/L5；T13+T14
- target output
- Abnormal strains/regions and confidence
- Implementation
- Need pathological truth value
- critical acceptance
- Recall for each disease type, Recall for unknown types
IR302Field weeds, crop rows and nighttime obstruction identification
- Minimum input and technical route
- NIR/LWIR L3/L4；T07+T11
- target output
- Crop/Weed/Barrier Mask
- Implementation
- Product model required
- critical acceptance
- IoU, row deviation, nighttime robustness
IR303Soil surface temperature, moisture proxies and bare ground zoning
- Minimum input and technical route
- TIR+SWIR L4；T14
- target output
- Surface temperature, humidity proxies and plot statistics
- Implementation
- Requires soil/meteorological truth values
- critical acceptance
- Contrast with probe/sampling; humidity is not a direct measurement
IR304UAV multi-temporal crop growth and disaster damage changes
- Minimum input and technical route
- Multispectral/TIR L4/L5;T14
- target output
- Change masks, parcel statistics and GIS
- Implementation
- Need time to match
- critical acceptance
- Registration error, change area IoU, cross-date stability
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.