Service scope and implementation plan
direction numberD59
Demand scenario8 items
main inputTIR multi-band L5; TIR+visible+meteorological L4; specific IR band L5;
Typical routeT14、T08、T13、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
IR465Satellite cloud top temperature and cloud classification
- Minimum input and technical route
- TIR multi-band L5;T14
- target output
- Cloud top temperature, cloud type and mass layer
- Implementation
- Atmospheric model required
- critical acceptance
- Compare with authoritative meteorological products/soundings
IR466Fog, low cloud and road visibility infrared assist
- Minimum input and technical route
- TIR+visible+meteorological L4;T14
- target output
- Fog areas, visibility proxies and road risks
- Implementation
- Multi-source model required
- critical acceptance
- Compare with visibility meter/site
IR467Remote sensing of water vapor channels and atmospheric humidity structure
- Minimum input and technical route
- Specific IR band L5;T14
- target output
- Water vapor distribution and mass layers
- Implementation
- Radiative transfer inversion required
- critical acceptance
- Comparison with sounding/operational products
IR468High temperature monitoring of craters, lava flows and eruptions
- Minimum input and technical route
- MWIR/TIR L4/L5；T08+T14
- target output
- Thermal anomalies, lava extent and changes
- Implementation
- Requires saturation/atmospheric correction
- critical acceptance
- Comparison with ground/aerial observations
IR469Multispectral identification of dust, smoke plumes and volcanic ash
- Minimum input and technical route
- IR multi-band L5;T13+T14
- target output
- Plume category, extent and confidence
- Implementation
- Requires authoritative label
- critical acceptance
- Each type of Recall, cross-region performance
IR470Surface frost and nighttime low temperature area monitoring
- Minimum input and technical route
- TIR L2/L4；T14
- target output
- Cold zones, duration and risk proxies
- Implementation
- Ground station required
- critical acceptance
- Versus site/crop damage
IR471Infrared time series analysis of thunderstorm clouds and convection development
- Minimum input and technical route
- Satellite TIR L3/L5;T05+T14
- target output
- Genting cooling, growth rates and events
- Implementation
- Need meteorological truth value
- critical acceptance
- Compare with radar/lightning/business records
IR472Aurora, atmospheric glow and infrared scientific observations
- Minimum input and technical route
- NIR/MWIR L3/L5；T13
- target output
- Luminescence structure, intensity and time changes
- Implementation
- Need scientific research equipment
- critical acceptance
- Wavelength/radiation calibration, time synchronization
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.