Service scope and implementation plan
direction numberD10
Demand scenario8 items
main inputMWIR/LWIR L2/L3；LWIR/MWIR L2；LWIR L2/L3；MWIR L1/L3
Typical routeT17、T03、T05、T04、T08、T02、T15
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
IR073Hot spots and coking candidates on the outer surface of boiler water wall
- Minimum input and technical route
- MWIR/LWIR L2/L3；T17
- target output
- Hot zones, temperature trends and locations
- Implementation
- High temperature radiation model required
- critical acceptance
- Compare with maintenance/process records, hot spot Recall
IR074Furnace lining and refractory layer thinning and shedding thermal anomalies
- Minimum input and technical route
- LWIR/MWIR L2；T03+T17
- target output
- Exterior wall hot spots, areas and risk zones
- Implementation
- Structural thermal model required
- critical acceptance
- Compared with furnace shutdown internal inspection/thickness inspection, POD
IR075Rotary kiln cylinder temperature scanning and brick lining anomalies
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Circumferential/axial temperature map, hot spot trajectory
- Implementation
- Requires rotation synchronization
- critical acceptance
- Angle positioning error, temperature error, missed detection
IR076Heat exchanger tube bundle blockage and uneven heat transfer
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Pipe zone temperature differences, blockage candidates and trends
- Implementation
- Demand condition model
- critical acceptance
- Compare with flow/cleaning results, area Recall
IR077Boiler combustion flame shape and deflection analysis
- Minimum input and technical route
- MWIR L1/L3；T08+T17
- target output
- Flame profile, center, swing and stability
- Implementation
- Requires dedicated filtering and dynamic range
- critical acceptance
- Contour repeatability compared to process parameters
IR078Furnace doors, inspection holes and sealed heat leaks
- Minimum input and technical route
- LWIR L2；T02+T03
- target output
- Heat leakage area, area and temperature difference
- Implementation
- Partially reusable
- critical acceptance
- Environmental stability conditions, area IoU, repeatability
IR079Heat treatment furnace charging uniformity and workpiece surface temperature
- Minimum input and technical route
- MWIR/LWIR L2/L3；T03+T17
- target output
- Workpiece temperature, uniformity and process curves
- Implementation
- Requires emissivity and occlusion models
- critical acceptance
- Comparison with thermocouple/furnace temperature uniformity test
IR080Heat losses from flues, chimneys and waste heat recovery surfaces
- Minimum input and technical route
- LWIR L2/L4；T03+T15
- target output
- Heat loss candidate areas and repair sequencing
- Implementation
- Thermal model required
- critical acceptance
- Wind/environmental recording, area error; energy consumption must be calculated independently
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.