Service scope and implementation plan
direction numberD26
Demand scenario8 items
main inputLWIR L2/L3；LWIR L2
Typical routeT02、T19、T04、T05、T03、T07、T15
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
IR201The cold storage door is not closed, the door seal is leaking, and the door is opened frequently
- Minimum input and technical route
- LWIR L2/L3；T02+T19
- target output
- Door status, cold leakage area and duration
- Implementation
- Partially reusable
- critical acceptance
- Door sensor/operation record comparison, event F1
IR202Cold storage enclosure insulation defects and thermal bridges
- Minimum input and technical route
- LWIR L2；T02
- target output
- Abnormal areas, areas and repair points
- Implementation
- Partially reusable
- critical acceptance
- Indoor and outdoor temperature difference/frost stratification, area IoU
IR203Evaporator frosting and defrost stage identification
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Frost zones, stages and abnormal defrost
- Implementation
- Need working condition data
- critical acceptance
- Compare with pressure/defrost control record
IR204Refrigeration compressor, condenser and pipeline thermal status
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Component Temperature and Abnormal Trends
- Implementation
- Partially reusable
- critical acceptance
- Compare with pressure/temperature instrument
IR205Screening for abnormal surface temperature of cold chain packages
- Minimum input and technical route
- LWIR L2/L3；T03+T07
- target output
- Package temperature, trajectory and out-of-limit events
- Implementation
- Requires object tracking
- critical acceptance
- Compare with data logger/core temperature sampling; surface temperature is not equal to core temperature
IR206Refrigerated compartment doors, air ducts and cargo heat distribution
- Minimum input and technical route
- LWIR L2/L3；T03+T15
- target output
- Car heat maps, local anomalies and events
- Implementation
- Requires spatial mapping
- critical acceptance
- Compare with multi-point temperature records to achieve complete coverage rate
IR207Frozen food warming and melting boundary candidates
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Surface temperature curve and temperature return anomaly
- Implementation
- Product thermal model required
- critical acceptance
- Compare with core temperature/quality test
IR208Exposure time and heat accumulation during cold chain loading and unloading
- Minimum input and technical route
- LWIR L2/L3；T07+T19
- target output
- Cargo trajectories, exposure duration and thermal risk proxies
- Implementation
- Business data required
- critical acceptance
- ID correlation rate, time error; risk threshold verified by product
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.