Service scope and implementation plan
direction numberD05
Demand scenario8 items
main inputLWIR L2/L3；L5；LWIR L2/L5；LWIR L2/L4
Typical routeT04、T05、T03、T10、T15、T02、T06、T14、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
IR033Thermal abnormalities of main bearings, gearboxes and couplings
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Component temperature rise, left-right difference and trend
- Implementation
- Partially reusable
- critical acceptance
- Compared with SCADA/vibration, abnormal recall, advance amount
IR034Generator and converter power module hotspots
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Module temperature, hotspot and load normalized trends
- Implementation
- Partially reusable
- critical acceptance
- Compared to built-in sensor/load, temperature P95
IR035Active thermal detection of blade surface debonding
- Minimum input and technical route
- L5；T10
- target output
- Debonding candidates, area and depth proxies
- Implementation
- Need to add new core
- critical acceptance
- Artificial defect test block, POD, minimum defect
IR036Blade lightning protection system connection thermal abnormality
- Minimum input and technical route
- LWIR L2/L5；T03+T10
- target output
- Connection area thermal response and anomalies
- Implementation
- Need to test tooling
- critical acceptance
- Comparison with resistance/continuity test, defective Recall
IR037Cabin cooling and ventilation path assessment
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Heat accumulation areas, ventilation status and trends
- Implementation
- Partially reusable
- critical acceptance
- Fan status, ambient temperature stratification, regional stability
IR038Hot spot inspection of tower flanges and cable connection points
- Minimum input and technical route
- LWIR L2/L4；T04+T15
- target output
- Junction point temperature, spatial location and inventory
- Implementation
- Need system integration
- critical acceptance
- Positioning error, visible coverage, temperature error
IR039Thermal imaging assists in judging blade icing and melting conditions
- Minimum input and technical route
- LWIR L2/L4；T02+T06
- target output
- Ice candidate areas, melting progress and uncertainty
- Implementation
- Required environment model
- critical acceptance
- Compare with physical objects/weather conditions, area IoU; does not replace safety criteria
IR040Wind farm UAV thermal inspection mission planning and review
- Minimum input and technical route
- RGB-LWIR L4；T14+T20
- target output
- Routes, asset binding, exception review and reporting
- Implementation
- Need system integration
- critical acceptance
- Coverage completeness rate, duplication rate, asset correlation rate
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.