Service scope and implementation plan
direction numberD40
Demand scenario8 items
main inputMWIR/TIR L3/L4; LWIR/TIR L2/L4; NIR+SWIR multi-phase; NIR/SWIR/TIR L4/L5
Typical routeT08、T14、T13、T07、T19、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
IR313Monitoring of early fire spots and heat sources under smoke in forest areas
- Minimum input and technical route
- MWIR/TIR L3/L4；T08+T14
- target output
- Fire points, confidence levels and geographic coordinates
- Implementation
- Fire scene data required
- critical acceptance
- Small fire source detection, false alarm/square kilometer, delay
IR314Wildfire lines, spread direction, and intensity proxies
- Minimum input and technical route
- MWIR/TIR L3/L4；T08+T14
- target output
- FireWire, Velocity, Thermal Radiation Proxy and GIS
- Implementation
- Requires radiometric/geographic correction
- critical acceptance
- Compare with ground/aeronautical records, position error
IR315Investigation of residual fire and underground smoldering surface thermal anomalies
- Minimum input and technical route
- LWIR/TIR L2/L4；T08+T14
- target output
- Hot spots, cooling trends and review points
- Implementation
- Partially reusable
- critical acceptance
- Compare with ground/temperature probe
IR316Analysis of NBR/dNBR changes in burned areas
- Minimum input and technical route
- NIR+SWIR multi-phase;T14
- target output
- Burn area and level agents
- Implementation
- Atmospheric/time phase correction required
- critical acceptance
- Comparison with ground plot/authoritative fire boundary
IR317Forest water stress and disease spectrum anomalies
- Minimum input and technical route
- NIR/SWIR/TIR L4/L5；T13+T14
- target output
- Stress zones, canopy temperatures and changes
- Implementation
- Need forestry truth value
- critical acceptance
- Compare with tree sample/moisture content
IR318Nighttime illegal logging, vehicle and personnel thermal target monitoring
- Minimum input and technical route
- LWIR L3；T07+T19
- target output
- Human and vehicle targets, trajectories and events
- Implementation
- Scenario data required
- critical acceptance
- False alarm/night, distance stratification
IR319Thermal imaging survey of understory wildlife
- Minimum input and technical route
- LWIR L3/L4；T07
- target output
- Animal categories, quantity, activity time and trajectory
- Implementation
- Species data required
- critical acceptance
- Each type of Recall, repeat count rate
IR320Review of forest drone infrared routes, splicing and changes
- Minimum input and technical route
- RGB-IR L4；T06+T14
- target output
- Heat map stitching, change points and go-around plans
- Implementation
- Need system integration
- critical acceptance
- Coverage, registration P95, geographical 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.