Service scope and implementation plan
direction numberD49
Demand scenario8 items
main inputTIR L2/L4; TIR+profile sensing; VIS+NIR L4;
Typical routeT14、T02、T05、T07、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
IR385River, lake and sea surface temperatures and thermal pollution emission plumes
- Minimum input and technical route
- TIR L2/L4；T14
- target output
- Water surface temperature, thermal plume and diffusion zone
- Implementation
- Requires radiation/atmospheric correction
- critical acceptance
- Compared to buoy/sampling, temperature RMSE
IR386Candidates for sewage outlets, groundwater inflows and abnormal hot and cold spots
- Minimum input and technical route
- TIR L2/L4；T02+T14
- target output
- Abnormal area and review coordinates
- Implementation
- Need hydrological truth value
- critical acceptance
- Compare with flow/water quality sampling
IR387Research on reservoir stratification, thermocline and release temperature
- Minimum input and technical route
- TIR+ profile sensing;T14
- target output
- Surface temperature, shore zone anomalies and model inputs
- Implementation
- Need underwater profile
- critical acceptance
- Thermal imaging of surface only; joint verification with profiling instrument
IR388Coastline, land and water boundary and flood extent NIR extraction
- Minimum input and technical route
- VIS+NIR L4；T14
- target output
- Water body mask and change range
- Implementation
- Partially reusable
- critical acceptance
- Compare with high-resolution image/scene boundary, IoU
IR389Irrigation canal leakage and underground pipe network surface heat traces
- Minimum input and technical route
- TIR L2/L4；T14
- target output
- Abnormal zones, locations and review points
- Implementation
- Required environment model
- critical acceptance
- Compare with excavation/flow true value
IR390Water treatment tank temperature, aeration and hybrid heat modes
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Surface heat distribution and mixing anomaly candidates
- Implementation
- Process data required
- critical acceptance
- Compare with temperature/flow/aeration records
IR391Nighttime thermal targets for ships, buoys and marine animals
- Minimum input and technical route
- MWIR/LWIR L3/L4；T07+T14
- target output
- Target, trajectory and coordinates
- Implementation
- Need sea surface data
- critical acceptance
- Sea state/distance stratification, false alarm rate
IR392Ocean infrared remote sensing cloud masking and quality control
- Minimum input and technical route
- Satellite TIR L5;T14+T20
- target output
- Cloud/Invalid Cells, Quality Tiers, and Availability Zones
- Implementation
- Remote sensing algorithm required
- critical acceptance
- Versus authoritative product/manual inspection
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.