Service scope and implementation plan
direction numberD54
Demand scenario8 items
main inputLWIR L2/L3;
Typical routeT02、T05、T03、T08、T07、T19、T16
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
IR425Refrigerator door seal, evaporator and box cold leakage test
- Minimum input and technical route
- LWIR L2/L3;T02+T05
- target output
- Cold leakage areas, frost and thermal cycles
- Implementation
- Partially reusable
- critical acceptance
- Compare with power consumption/temperature point/door status
IR426Air conditioner air outlet, heat exchanger and defrost heat status
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Temperature fields, phases and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compare with cooling parameters/sensors
IR427Heating uniformity of induction cooktops, ovens and electric heaters
- Minimum input and technical route
- MWIR/LWIR L2/L3;T03+T05
- target output
- Heating zones, uniformity and response time
- Implementation
- Requires surface emissivity treatment
- critical acceptance
- Versus standard load/thermocouple
IR428Thermal design of mobile phones, notebooks and chargers
- Minimum input and technical route
- Macro LWIR L2/L3;T03+T05
- target output
- Case/Device Temperature and Hot Spots
- Implementation
- Partially reusable
- critical acceptance
- Versus internal sensors/power consumption
IR429Power bank and home energy storage are abnormally hot
- Minimum input and technical route
- LWIR L2/L3;T05+T08
- target output
- Hot spots, warming trends and alarm candidates
- Implementation
- Partially reusable
- critical acceptance
- Fault injection, advance amount; not solely responsible for fire protection
IR430Smart home low resolution thermal array people presence
- Minimum input and technical route
- Thermal array L3;T07+T19
- target output
- Occupancy, orientation and area activity
- Implementation
- Need low resolution model
- critical acceptance
- Occupancy F1, multi-person occlusion and privacy assessment
IR431Sleep bed occupancy, bed alighting, and respiratory proxy studies
- Minimum input and technical route
- thermal array/LWIR L3;T07+T16
- target output
- Position, Away from Bed, and Waveforms
- Implementation
- Controlled/medical boundaries required
- critical acceptance
- Versus pressure pad/breathing belt
IR432Kitchen stove fire, pot dry burning and high temperature risk detection
- Minimum input and technical route
- LWIR/MWIR L2/L3;T08+T19
- target output
- Heat sources, temperatures and persistent events
- Implementation
- Appliance safety verification required
- critical acceptance
- Fault injection, false alarm/day; linkage must be independently certified
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.