Service scope and implementation plan
direction numberD06
Demand scenario8 items
main inputLWIR L2/L3; high speed LWIR/MWIR
Typical routeT03、T04、T05、T08、T19、T10、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
IR041Single cell temperature unevenness and hot spot detection
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Cell Temperature, ΔT, Hotspots and Trends
- Implementation
- Partially reusable
- critical acceptance
- Compared with thermocouple/BMS, monomer correlation rate, temperature P95
IR042Module connectors, busbars and terminals are overheated
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Connection point temperature rise and load normalization abnormality
- Implementation
- Partially reusable
- critical acceptance
- Current working condition stratification, hot spots Recall
IR043Charge-discharge thermal response curves and consistency grouping
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Unit/module response curves, clustering and outliers
- Implementation
- Reusable timing module
- critical acceptance
- Cycle repeatability, within/between group separability
IR044Thermal spread test fire point and propagation path analysis
- Minimum input and technical route
- High speed LWIR/MWIR L2/L3;T08+T19
- target output
- Starting point, travel time, speed and hot zone
- Implementation
- Requires dedicated high-speed link
- critical acceptance
- Aligned to synchronized temperature/voltage records, time offset
IR045Energy storage cabinet refrigeration airflow and heat accumulation assessment
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Hot zone in the cabinet, temperature difference between layers and fan status
- Implementation
- Partially reusable
- critical acceptance
- Air volume/environment/load stratification, hot zone stability
IR046Battery pack thermal management cold plate flow path abnormality
- Minimum input and technical route
- LWIR L2/L5;T03+T10
- target output
- Flow path temperature difference, clogging/bubble candidates
- Implementation
- Required working conditions and structural truth values
- critical acceptance
- Compare with flow/pressure differential/CT or disassembly inspection
IR047Thermal anomaly screening during the formation stage of battery manufacturing
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Channel level temperature profiles and abnormal batches
- Implementation
- Need production data
- critical acceptance
- Missing negatives/10,000 pieces, false positive rate, tempo and traceability
IR048Thermal runaway early warning multi-signal fusion
- Minimum input and technical route
- Temperature + gas + voltage L4;T05+T20
- target output
- Risk scores, evidence and escalation events
- Implementation
- Safety systems engineering required
- critical acceptance
- Independent abuse testing, lead time, and false negatives; no closed-loop shutdown based on vision alone
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.