Service scope and implementation plan
direction numberD19
Demand scenario8 items
main inputMWIR/SWIR L2/L3；MWIR/LWIR L2/L3；L5；LWIR L2/L3
Typical routeT17、T03、T05、T10、T19
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
IR145Glass annealing temperature field and edge-to-edge difference
- Minimum input and technical route
- MWIR/SWIR L2/L3；T17
- target output
- Temperature fields, uniformity and cooling curves
- Implementation
- Band/transmission verification required
- critical acceptance
- Compared with contact/two-color temperature measurement, temperature P95
IR146Glass bottles and glass plates thermal cracking risk areas
- Minimum input and technical route
- MWIR/LWIR L2/L3；T03+T05
- target output
- Thermal gradients, edge anomalies and risk candidates
- Implementation
- Defect truth value required
- critical acceptance
- Comparison with failure/polarizing stress results
IR147Ceramic sintering and cooling uniformity
- Minimum input and technical route
- MWIR/LWIR L2/L3；T05+T17
- target output
- Temperature profiles, cold spots and batch differences
- Implementation
- Need craft true value
- critical acceptance
- Linked to Density/Warp/Crack results
IR148Active thermal screening of internal defects in ceramic bodies
- Minimum input and technical route
- L5；T10
- target output
- Pore/crack candidates and depth proxies
- Implementation
- Need test block
- critical acceptance
- Versus X-ray/CT, POD
IR149Abnormal refractory lining of cement kiln shell
- Minimum input and technical route
- LWIR L2/L3；T03+T17
- target output
- Housing Hotspots, Growth Trends and Locations
- Implementation
- Requires rotation synchronization
- critical acceptance
- Temperature error, angle positioning, advance amount
IR150Cement clinker cooling and conveying temperature monitoring
- Minimum input and technical route
- MWIR/LWIR L2/L3；T17+T19
- target output
- Stream temperature, cooling status and events
- Implementation
- High temperature material model required
- critical acceptance
- Compared with process temperature measurement, event accuracy rate
IR151Active/passive thermal detection of concrete voids and delaminations
- Minimum input and technical route
- L3/L5；T10
- target output
- Abnormal areas, contrast and depth candidates
- Implementation
- Requires environment/test block design
- critical acceptance
- Versus radar/tapping/coring, POD
IR152Evaluation of thermal conductivity uniformity of refractory bricks and insulation materials
- Minimum input and technical route
- L5；T10
- target output
- Thermal response, thermal conductivity proxies and abnormal areas
- Implementation
- Physical property calibration required
- critical acceptance
- Compared with standard thermal conductivity test, RMSE
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.