Service scope and implementation plan
direction numberD02
Demand scenario8 items
main inputLWIR L2/L3; LWIR L2;
Typical routeT03、T04、T08、T14、T02、T06、T15、T05、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
IR009Thermal abnormalities of transformer bushings and terminal blocks
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Bushing/terminal temperature, phase difference and alarm
- Implementation
- Partially reusable
- critical acceptance
- Distance and load stratification, component recall, temperature P95
IR010Transformer radiator clogged and uneven cooling
- Minimum input and technical route
- LWIR L2；T03+T04
- target output
- Heat sink temperature field, cold/hot areas and uniformity
- Implementation
- Partially reusable
- critical acceptance
- Versus flow/fan status, area IoU and uniformity error
IR011Lightning Arrester Thermal Defect Screening
- Minimum input and technical route
- LWIR L2；T03+T04
- target output
- Examples of lightning arresters, phase-to-phase temperature differences and abnormal levels
- Implementation
- Partially reusable
- critical acceptance
- Same group comparison, reflection elimination, defect recall
IR012Candidates for abnormal heating of insulator strings and dirty discharges
- Minimum input and technical route
- LWIR/MWIR L2/L3；T04+T08
- target output
- Hotspot location, persistence and string numbering
- Implementation
- Special data required
- critical acceptance
- Distance to target pixels, discharge condition stratification, false alarm/km
IR013Overhead conductor tension clamps and deflector hot spots
- Minimum input and technical route
- Drone LWIR L2/L4;T04+T14
- target output
- Clamp positioning, temperature difference and geographical coordinates
- Implementation
- Requires multi-sensor integration
- critical acceptance
- Geolocation error, hotspot recall, wind/distance stratification
IR014Thermal anomalies in cable trenches and underground cable paths
- Minimum input and technical route
- LWIR L2/L4；T02+T14
- target output
- Anomaly tropics, paths and review points
- Implementation
- Scenario model required
- critical acceptance
- Covering soil/surface condition stratification, false alarm area, positioning error
IR015Drone/robot infrared inspection of station equipment
- Minimum input and technical route
- RGB-LWIR L4；T04+T06+T15
- target output
- Device ID, temperature, posture and inspection records
- Implementation
- Need system integration
- critical acceptance
- Point arrival rate, device correlation rate, temperature error, missed detection
IR016Sorting of thermal status of similar equipment in substations
- Minimum input and technical route
- LWIR L2/L3；T05+T20
- target output
- Same type equipment baseline, deviation ranking and review list
- Implementation
- Partially reusable
- critical acceptance
- Working condition normalization, ranking stability, abnormal recall
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.