Service scope and implementation plan
direction numberD36
Demand scenario8 items
main inputLWIR/RGB-LWIR L4;LWIR L3;LWIR L2/L3;L2/L5
Typical routeT07、T19、T03、T10、T16、T06、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
IR281Personnel approach monitoring in safe areas of high-temperature equipment
- Minimum input and technical route
- LWIR/RGB-LWIR L4;T07+T19
- target output
- People, heat sources, distances and risk events
- Implementation
- Requires spatial calibration
- critical acceptance
- Distance Error, Risk Recall, Delay
IR282Personnel presence and fall detection in dark factories
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- People, postures, falls and stays
- Implementation
- Scenario data required
- critical acceptance
- Fall Recall, false alarm/hour
IR283Monitoring of detention and departure of cold storage personnel
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Personnel trajectory, detention and door status
- Implementation
- Business system required
- critical acceptance
- Event F1, occlusion recovery rate
IR284Recording of heat exposure in furnace front, foundry and fire protection operations
- Minimum input and technical route
- LWIR L2/L3;T03+T07
- target output
- Personnel/equipment surface temperature and exposure time
- Implementation
- Security/privacy design required
- critical acceptance
- Comparison with wearable sensors; not equal to human body core temperature
IR285Protective clothing insulation anomalies and heat penetration test
- Minimum input and technical route
- L2/L5;T10+T16
- target output
- Surface hot zones, temperature rise curves and anomalies
- Implementation
- Standard test required
- critical acceptance
- Comparison with standard thermal protection test
IR286Thermal imaging aids for wearing gloves, masks and thermal insulation gear
- Minimum input and technical route
- NIR/LWIR L3/L4;T06+T07
- target output
- Equipment area and wearing candidates
- Implementation
- Dual optical data required
- critical acceptance
- Human-level Recall, long-range/occlusion layering
IR287Joint tracking of personnel and high-temperature workpieces in the human-machine collaboration area
- Minimum input and technical route
- RGB-LWIR L4;T06+T19
- target output
- People, artifacts, trajectories, and conflict events
- Implementation
- Need system integration
- critical acceptance
- IDF1, distance error, event Recall
IR288Thermal safety alarm evidence, manual review and linked gate control
- Minimum input and technical route
- L3/L4;T20
- target output
- Alarm, evidence fragment, review and linkage status
- Implementation
- Safety engineering required
- critical acceptance
- Missing negatives, false triggers, end-to-end delays; linkage requires independent security verification
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.