Service scope and implementation plan
direction numberD29
Demand scenario8 items
main inputMWIR/LWIR L2/L3;LWIR L2/L3;L5;LWIR/MWIR L2/L3
Typical routeT03、T17、T07、T04、T05、T10、T02
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
IR225Engine, exhaust and turbine thermal distribution testing
- Minimum input and technical route
- MWIR/LWIR L2/L3;T03+T17
- target output
- Component Temperature, Hotspots and Transients
- Implementation
- High temperature calibration required
- critical acceptance
- Compared with thermocouple/ECU, temperature P95
IR226Brake disc, wheel hub and tire temperature rise uniformity
- Minimum input and technical route
- LWIR L2/L3;T03+T07
- target output
- Wheel position temperature, left and right difference and cooling curve
- Implementation
- Partially reusable
- critical acceptance
- Comparison with contact temperature/braking conditions
IR227Vehicle wiring harnesses, fuse boxes and high voltage connection hotspots
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Connection point temperature rise and abnormality list
- Implementation
- Partially reusable
- critical acceptance
- Current working condition stratification, hot spots Recall
IR228New energy vehicle battery pack and thermal management testing
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Temperature field of inclusion body, uneven cooling and transient state
- Implementation
- Need structure truth value
- critical acceptance
- Compare to internal sensor/cooling parameters
IR229Cabin HVAC, seat heating and defrost effects
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Surface temperature, coverage and response time
- Implementation
- Partially reusable
- critical acceptance
- Compare with temperature point/defrost area standard
IR230Active thermal NDT for body bonding, composites and solder joints
- Minimum input and technical route
- L5;T10
- target output
- Bonding/welding anomalies and areas
- Implementation
- Need reference sample
- critical acceptance
- Comparison with ultrasound/X-ray/destructive testing
IR231Spray drying and coating curing thermal processes
- Minimum input and technical route
- LWIR/MWIR L2/L3;T05
- target output
- Body temperature, uniformity and cure window
- Implementation
- Need craft true value
- critical acceptance
- Comparison with furnace temperature/coating performance
IR232Post-repair thermal imaging review of air conditioning, cooling and exhaust leaks
- Minimum input and technical route
- LWIR L2/L3;T02+T05
- target output
- Abnormal heat traces and comparison before and after repair
- Implementation
- Repair process required
- critical acceptance
- Compare with pressure/leak detection/road test results
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.