Service scope and implementation plan
direction numberD25
Demand scenario8 items
main inputLWIR L2/L3; LWIR L2/L4;
Typical routeT03、T05、T02、T04、T15、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
IR193Return air inlet temperature distribution and short-circuit return air candidates
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Outlet temperatures, thermal plumes and anomaly patterns
- Implementation
- Partially reusable
- critical acceptance
- Compare with air volume/temperature sensor
IR194Air duct insulation defects and air leakage heat traces
- Minimum input and technical route
- LWIR L2/L3;T02
- target output
- Exception areas and review points
- Implementation
- Partially reusable
- critical acceptance
- Compare with pressure/smoke/air volume
IR195Frosting, clogging and uneven heat transfer of air conditioning coils
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Coil temperature, frost zone and status
- Implementation
- Need working condition data
- critical acceptance
- Versus pressure/refrigerant/labor inspection
IR196Radiators, radiators and hydraulic imbalances
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Surface temperature distribution and imbalance candidates
- Implementation
- Partially reusable
- critical acceptance
- Versus flow/valve position, zone repeatability
IR197Cooling tower water distribution and heat exchange abnormalities
- Minimum input and technical route
- LWIR L2/L4;T03+T04
- target output
- Hot areas, uneven water distribution and fan status
- Implementation
- Required environment model
- critical acceptance
- Compare with temperature difference/flow rate/maintenance
IR198Indoor uneven heating and cooling and thermal comfort space diagram
- Minimum input and technical route
- LWIR L2/L4+ environment sensing;T15
- target output
- Surface temperature, personnel area thermal environment and changes
- Implementation
- Architectural model required
- critical acceptance
- Compare with air/radiant temperature measurements; do not judge comfort by thermal imaging alone
IR199Fresh air, exhaust air and heat recovery performance screening
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Inlet and outlet temperature fields and efficiency candidates
- Implementation
- Flow/temperature and humidity data required
- critical acceptance
- Comparison with standard efficiency calculations
IR200HVAC equipment group abnormal thermal status ranking
- Minimum input and technical route
- L2/L3;T05+T20
- target output
- Equipment baselines, outliers, and maintenance checklists
- Implementation
- Partially reusable
- critical acceptance
- Working condition normalization and sorting stability
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.