Service scope and implementation plan
direction numberD55
Demand scenario8 items
main inputLow resolution LWIR L3;
Typical routeT07、T19、T06、T04、T05、T03、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
IR433Anonymous passenger flow and area occupancy in shopping malls/stations
- Minimum input and technical route
- Low resolution LWIR L3;T07+T19
- target output
- Counting, occupancy and flow
- Implementation
- Scenario data required
- critical acceptance
- Counting error, occlusion layering, privacy assessment
IR434Thermal abnormalities of people, vehicles and charging piles in parking lots at night
- Minimum input and technical route
- RGB-LWIR L4;T06+T07
- target output
- Target, trajectory, charging device hotspot
- Implementation
- Requires multi-tasking model
- critical acceptance
- Target Recall, Device Hotspot Recall
IR435Public restroom/meeting room occupancy thermal array sensing
- Minimum input and technical route
- Thermal array L3;T07
- target output
- Occupancy status and number of people range
- Implementation
- Privacy design required
- critical acceptance
- Occupancy F1, headcount error, risk of re-identification
IR436Thermal inspection of escalators, elevator machine rooms and power distribution equipment
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Component temperatures and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Check with maintenance/load records
IR437Commercial kitchen, freezer and food display thermal conditions
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Surface temperature, door status and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compare with temperature record/core temperature sampling
IR438Energy-saving control input for building air conditioning zones and uninhabited areas
- Minimum input and technical route
- Thermal array + environmental sensing L4;T07+T20
- target output
- Occupancy and thermal status
- Implementation
- Requires control system verification
- critical acceptance
- Occupancy error and energy savings need to be measured independently
IR439Public charging station connectors, gun wires and power module hotspots
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Equipment temperatures, anomalies, and work orders
- Implementation
- Partially reusable
- critical acceptance
- Compare with current/contact temperature/maintenance results
IR440Building infrared inspection work orders, assets and retest closed loop
- Minimum input and technical route
- L4;T20
- target output
- Comparison and audit of assets, anomalies, and maintenance before and after
- Implementation
- Requires business integration
- critical acceptance
- Asset correlation rate, closed-loop integrity rate, retest consistency
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.