Service scope and implementation plan
direction numberD37
Demand scenario8 items
main inputLWIR L2/L3；RGB-LWIR L4
Typical routeT04、T19、T05、T08、T03、T07、T02、T06、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
IR289Separation of hot materials, cold materials and abnormal packages on the conveyor line
- Minimum input and technical route
- LWIR L2/L3；T04+T19
- target output
- Package temperature, trajectory and shunt events
- Implementation
- Requires tracking/PLC integration
- critical acceptance
- Temperature error, routing accuracy, delay
IR290Early monitoring of hot spots in lithium batteries and chemical warehouses
- Minimum input and technical route
- LWIR L2/L3；T05+T08
- target output
- Cargo hot spots, rising trends and events
- Implementation
- Partially reusable
- critical acceptance
- Discover the lead time, false alarm/day, and cargo location correlation rate
IR291Cold chain pallet and box surface temperature screening
- Minimum input and technical route
- LWIR L2/L3；T03+T07
- target output
- Pallet/Case Temperature and Overrun Candidates
- Implementation
- Required object model
- critical acceptance
- Compare with recorder/core temperature sampling
IR292Warehouse doors, loading and unloading openings and thermal insulation curtains are leaking cold
- Minimum input and technical route
- LWIR L2/L3；T02+T19
- target output
- Cold leakage zone, door status and duration
- Implementation
- Partially reusable
- critical acceptance
- Door status comparison, area IoU
IR293Forklift brake, battery and motor overheating inspection
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Vehicle/component temperatures and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compare with vehicle telemetry/maintenance records
IR294Monitoring of self-heating surfaces in silos, silos and stacks
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Hot zones, heating rates and review locations
- Implementation
- Need internal temperature control
- critical acceptance
- Surface thermal imaging cannot replace deep probes; verification lead time
IR295Online inspection of packaging heat sealing and heat shrink integrity
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Sealing heat marks, chips and OK/NG
- Implementation
- Production line data required
- critical acceptance
- Compared with leakage/peel test, missed detection/10,000 pieces
IR296Drone warehouse/yard thermal inspection and asset binding
- Minimum input and technical route
- RGB-LWIR L4；T06+T15
- target output
- Assets, thermal anomalies and spatial locations
- Implementation
- Need system integration
- critical acceptance
- Coverage rate, asset correlation rate, positioning error
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.