Service scope and implementation plan
direction numberD03
Demand scenario8 items
main inputLWIR L2/L3；LWIR L2/L4；LWIR L2
Typical routeT03、T05、T04、T15、T02、T08
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
IR017Turbine casing and shaft seal temperature field monitoring
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Temperature fields, axial gradients and trends
- Implementation
- Partially reusable
- critical acceptance
- Comparison with temperature measurement points, load stratification, trend advance amount
IR018Abnormalities in generator stator housing and cooling path
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Uneven cooling, local temperature rise and trends
- Implementation
- Partially reusable
- critical acceptance
- Contrast with current/cooling status, area Recall
IR019Steam pipe insulation damage and heat loss candidates
- Minimum input and technical route
- LWIR L2/L4；T03+T15
- target output
- Abnormal surface, area and heat loss estimation
- Implementation
- Thermal model required
- critical acceptance
- Environmental/wind speed records, area errors; heat loss must be compared with thermal calculations
IR020Thermal pattern recognition of steam trap working status
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Patency, blockage, leak candidates and cycles
- Implementation
- Need product true value
- critical acceptance
- Compare with ultrasonic/process records, status F1
IR021Candidates for valve internal leakage and bypass thermal anomalies
- Minimum input and technical route
- LWIR L2/L3；T02+T05
- target output
- Temperature distribution before and after the valve and leakage candidates
- Implementation
- Demand condition model
- critical acceptance
- Pressure difference/medium/insulation layering, false alarm rate
IR022Uneven heat transfer on condenser and heat exchanger surfaces
- Minimum input and technical route
- LWIR L2；T03+T04
- target output
- Tube bundle/plate temperature difference and clogging candidates
- Implementation
- Required object model
- critical acceptance
- Comparison with flow/cleaning before and after, area IoU
IR023Self-heating monitoring for coal and biomass stockpiles
- Minimum input and technical route
- LWIR L2/L3；T03+T05+T08
- target output
- Hot zones, warming rates and risk stratification
- Implementation
- Partially reusable
- critical acceptance
- Deep temperature cannot be directly replaced by the surface; verify the discovery advance amount
IR024Thermal mode of clogging of slag discharge, ash hopper and ash conveying system
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Flow/blockage status, location and events
- Implementation
- Process data required
- critical acceptance
- Compare with material level/maintenance record, status F1, delay
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.