Service scope and implementation plan
direction numberD51
Demand scenario8 items
main inputLWIR/TIR L2/L4; MWIR/LWIR L2/L3;
Typical routeT05、T08、T17、T13、T12、T14、T09、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
IR401Landfill self-heating, underground fires and gas hot spots
- Minimum input and technical route
- LWIR/TIR L2/L4;T05+T08
- target output
- Hot spots, trends and review coordinates
- Implementation
- Partially reusable
- critical acceptance
- Compare with borehole temperature/gas detection
IR402Waste incinerator and flue thermal status monitoring
- Minimum input and technical route
- MWIR/LWIR L2/L3;T17
- target output
- Furnace body/flue temperature and abnormalities
- Implementation
- High temperature model required
- critical acceptance
- Compare with process temperature measurement/emission records
IR403Recycling plastics, paper and fabrics SWIR Material sorting
- Minimum input and technical route
- SWIR/Hyperspectral L5;T13
- target output
- Material class, contamination and sorting signals
- Implementation
- Need sample library
- critical acceptance
- Recall, mixture/stain layering per category
IR404Black plastic NIR/SWIR classification feasibility screening
- Minimum input and technical route
- SWIR L5;T12+T13
- target output
- Separable/non-separable materials and candidate categories
- Implementation
- Band test required
- critical acceptance
- Spectral separability, batch external validation
IR405Remote sensing of sewage outfalls and thermal pollution plumes
- Minimum input and technical route
- TIR L2/L4;T14
- target output
- Exhaust heat trace, range and coordinates
- Implementation
- Required water temperature/flow true value
- critical acceptance
- Temperature RMSE, plume IoU
IR406Compost fermentation and organic windrow temperature uniformity
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Candidates for surface hot zone and turning pile requirements
- Implementation
- Need deep probe
- critical acceptance
- Versus internal temperature/oxygen content
IR407VOC/methane/SF₆ and other emissions OGI monitoring
- Minimum input and technical route
- Special OGI L3;T09
- target output
- Air plume incidents, equipment and evidence
- Implementation
- One gas and one configuration are required
- critical acceptance
- Controlled release, environmental stratification, false positives
IR408Environmental inspection multi-source evidence and GIS archiving
- Minimum input and technical route
- IR+Visible+Sensor L4;T14+T20
- target output
- Exception, coordinates, time and review records
- Implementation
- Need system integration
- critical acceptance
- Data integrity, coordinate error, auditability
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.