Service scope and implementation plan
direction numberD04
Demand scenario8 items
main inputLWIR L2/L4；RGB-LWIR L4；LWIR L2；NIR/SWIR L1/L5
Typical routeT03、T04、T05、T06、T14、T02、T18、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
IR025Photovoltaic module hot spot and hot spot detection
- Minimum input and technical route
- LWIR L2/L4；T03+T04
- target output
- Module/cell hot spots, ΔT and coordinates
- Implementation
- Partially reusable
- critical acceptance
- Record irradiance, wind and viewing angle as per IEC TS 62446-3 conditions; hot spots Recall
IR026Bypass diode, sub-string and string anomaly classification
- Minimum input and technical route
- LWIR L2/L4；T04+T05
- target output
- Component mode, substring/string fault candidates
- Implementation
- Need product true value
- critical acceptance
- Comparison with IV Curve/Electrical Test, Classification Macro-F1
IR027Automatic splicing and component positioning of drone photovoltaic arrays
- Minimum input and technical route
- RGB-LWIR L4；T06+T14
- target output
- Array ortho, component ID, and thermal anomaly layers
- Implementation
- Need system integration
- critical acceptance
- Registration P95, component positioning rate, duplicate/missing components
IR028Inspection of inverters, combiner boxes and joint hot spots
- Minimum input and technical route
- LWIR L2/L4；T03+T04
- target output
- Device temperature, component hotspots and alarms
- Implementation
- Partially reusable
- critical acceptance
- Versus load/contact temperature, component level Recall
IR029Component occlusion, pollution and hotspot correlation analysis
- Minimum input and technical route
- RGB-LWIR L4；T06+T04
- target output
- Contaminated/occluded areas, thermal response and correlation
- Implementation
- Dual optical data required
- critical acceptance
- Area IoU, correlation accuracy, different irradiation stratification
IR030Component thermal gradient and package anomaly screening
- Minimum input and technical route
- LWIR L2；T03+T02
- target output
- Edge/local temperature differences and abnormal patterns
- Implementation
- Required reference components
- critical acceptance
- Versus EL/Lab Inspection, Defect Recall
IR031Photovoltaic cell EL crack and failure area identification
- Minimum input and technical route
- NIR/SWIR L1/L5；T18
- target output
- Dark areas, cracks, breaks and areas
- Implementation
- Need special implementation
- critical acceptance
- Reference standard sample, smallest crack, pixel level IoU
IR032Joint diagnosis of IR, EL, IV and O&M records
- Minimum input and technical route
- Multi-source L4/L5;T18+T20
- target output
- Fault candidates, evidence chain and repair sequencing
- Implementation
- Multimodal model required
- critical acceptance
- Independent electrical truth value, calibration confidence, repair hit 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.