Service scope and implementation plan
direction numberD28
Demand scenario8 items
main inputLWIR L3/L4；MWIR/LWIR L3/L4；LWIR L3；RGB-LWIR L4
Typical routeT07、T14、T06、T08、T09、T04、T19、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
IR217Drone search for missing persons at night
- Minimum input and technical route
- LWIR L3/L4；T07+T14
- target output
- Personnel candidates, trajectories and geographical coordinates
- Implementation
- Need unmanned aerial vehicle system
- critical acceptance
- Distance/vegetation/terrain layering, Recall, positioning error
IR218Hot target search for drowning persons in mountains, waters and seas
- Minimum input and technical route
- MWIR/LWIR L3/L4；T07+T14
- target output
- Personnel/floating target candidates and coordinates
- Implementation
- Requires special data
- critical acceptance
- Sea state/wave/distance stratification, false alarm/hour
IR219Surface heat traces and personnel candidates at earthquake/collapse sites
- Minimum input and technical route
- LWIR L3；T07
- target output
- Hot targets and review areas
- Implementation
- Need rescue data
- critical acceptance
- Occlusion conditions are layered; cannot penetrate solid ruins
IR220Flood night person, vehicle and obstacle sensing
- Minimum input and technical route
- RGB-LWIR L4；T06+T07
- target output
- Goals, trajectories and risk zones
- Implementation
- Requires dual light model
- critical acceptance
- Rain fog/water reflection layering, target Recall
IR221Volcanic lava and high temperature eruption area monitoring
- Minimum input and technical route
- MWIR/TIR L2/L4；T08+T14
- target output
- High temperature zones, heat flux proxies and changes
- Implementation
- Requires remote sensing physical model
- critical acceptance
- Saturation/atmospheric correction, ground station comparison
IR222Joint observation of leakage plumes and personnel areas in hazardous chemical accidents
- Minimum input and technical route
- OGI+LWIR/RGB L4；T09+T07
- target output
- Air plumes, personnel and quarantine candidates
- Implementation
- Multiple camera system required
- critical acceptance
- Time synchronization, event recall; category confirmed by dedicated sensing
IR223Post-disaster rapid inspection of power supply, gas and heating facilities
- Minimum input and technical route
- RGB-LWIR L4；T04+T14
- target output
- Asset thermal anomalies and review checklist
- Implementation
- Required asset map
- critical acceptance
- Coverage rate, asset correlation rate, missed detection
IR224Real-time annotation of search and rescue videos, map return and evidence archiving
- Minimum input and technical route
- L3/L4；T19+T20
- target output
- Goals, coordinates, fragments and mission logs
- Implementation
- Need system integration
- critical acceptance
- End-to-end delay, coordinate error, data integrity rate
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.