Service scope and implementation plan
direction numberD01
Demand scenario8 items
main inputLWIR L2/L3；LWIR L2
Typical routeT03、T04、T05、T19、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
IR001Screening of switchgear joints and busbars for overheating
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Component level maximum temperature, ΔT and hot spot alarms
- Implementation
- Partially reusable
- critical acceptance
- Compare to contact temperature and load records, temperature P95, hot spot Recall
IR002Abnormal temperature rise of circuit breaker and isolation switch contacts
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Contact thermal patterns, heating rates and trends
- Implementation
- Partially reusable
- critical acceptance
- Comparison of the same load and the same model, false alarms/cabinet and discovery time
IR003Hot spots on fuses, terminal strips and cable glands
- Minimum input and technical route
- LWIR L2；T03+T04
- target output
- Part location, temperature and anomaly level candidates
- Implementation
- Partially reusable
- critical acceptance
- Effective pixels of widgets, object correlation rate, temperature difference error
IR004Three-phase circuit temperature imbalance
- Minimum input and technical route
- LWIR L2；T03+T05
- target output
- Three-phase temperature differences, deviations from baseline and trends
- Implementation
- Reusable general statistics
- critical acceptance
- Load matching criteria, repeatability and threshold false negative rate
IR005Abnormal heating of contactor and relay coils
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Coil temperature rise curve and steady state after action
- Implementation
- Partially reusable
- critical acceptance
- Action cycle synchronization, temperature rise curve error, fault sample Recall
IR006Sockets, plug strips and charging interfaces are overheated
- Minimum input and technical route
- LWIR L2/L3；T03+T19
- target output
- Interface temperature, continuous exceedance and alarm fragments
- Implementation
- Partially reusable
- critical acceptance
- Different plug material/angle layering, alarm delay
IR007Baseline modeling of heat distribution inside electrical cabinets
- Minimum input and technical route
- LWIR L2/L3；T04+T05+T20
- target output
- Cabinet-Level Thermal Baseline, Part Deviation and Revision
- Implementation
- Partially reusable
- critical acceptance
- Cross-load/environment baseline stability, unknown state rejection
IR008Cabinet door infrared window inspection quality inspection
- Minimum input and technical route
- LWIR L2；T03+T20
- target output
- Window transmission compensation, field of view coverage and invalid measurements
- Implementation
- Need to add a new radiation model
- critical acceptance
- Blackbody contrast, transmittance and temperature error with/without window
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.