Service scope and implementation plan
direction numberD09
Demand scenario8 items
main inputLWIR L2/L3;LWIR L2
Typical routeT03、T05、T20、T04、T02、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
IR065Pump bearing and mechanical seal temperature rise
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Part temperatures, trends and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compared to process/contact temperature, temperature P95
IR066Pump drying, cavitation, and underflow heat mode candidates
- Minimum input and technical route
- LWIR L2/L3;T05+T20
- target output
- Thermal patterns, status classification and confidence
- Implementation
- Requires multiple sources of truth values
- critical acceptance
- Versus pressure/flow/acoustics, status F1
IR067Compressor cylinder, interstage and exhaust temperature distribution
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Regional temperatures, stage differences and trends
- Implementation
- Partially reusable
- critical acceptance
- Versus instrument temperature/load, area error
IR068Joint thermal inspection of fan bearings, belts and motors
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Multi-part thermal status and exception list
- Implementation
- Partially reusable
- critical acceptance
- Component location rate, fault recall
IR069In-tube flow state and liquid level thermal boundary candidates
- Minimum input and technical route
- LWIR L2;T02+T04
- target output
- Thermal Boundary, Level/Flow Candidates
- Implementation
- Media and wall thickness verification required
- critical acceptance
- Compared with level meter/flow meter, position error
IR070Steam/Hot Water Pump Insulation and Leak Heat Traces
- Minimum input and technical route
- LWIR L2/L3;T02+T19
- target output
- Leak candidates, diffusion zones and duration
- Implementation
- Scenario data required
- critical acceptance
- Minimum leakage, false alarms/day, time to discovery
IR071Analysis of thermal plumes in air ducts, nozzles and heat dissipation flow fields
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Plume area, direction and velocity proxies
- Implementation
- Partially reusable optical flow
- critical acceptance
- Compare with wind speed/smoke visualization
IR072Optimization of thermal status rotation of multiple pumps in the same unit
- Minimum input and technical route
- LWIR L2/L3;T05+T20
- target output
- Health ranking and review recommendations
- Implementation
- Need normalization of operating conditions
- critical acceptance
- Sorting stability, fault hit rate; no direct closed-loop control
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.