Service scope and implementation plan
direction numberD24
Demand scenario8 items
main inputLWIR L2/L4；LWIR L2/L3；LWIR L2；L3/L5
Typical routeT02、T06、T05、T04、T10、T15、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
IR185Missing exterior wall insulation and thermal bridge detection
- Minimum input and technical route
- LWIR L2/L4；T02+T06
- target output
- Thermal bridge/insulation abnormal area and facade location
- Implementation
- Partially reusable
- critical acceptance
- Indoor and outdoor temperature difference/wind/sunlight records, area IoU
IR186Candidates for door and window airtightness and frame heat leakage
- Minimum input and technical route
- LWIR L2/L3；T02
- target output
- Border thermal anomalies and review points
- Implementation
- Partially reusable
- critical acceptance
- Blower door/smoke comparison; thermal imaging cannot alone provide air leakage volume
IR187Candidates for roof insulation due to moisture and water accumulation
- Minimum input and technical route
- LWIR L2/L3；T02+T05
- target output
- Thermal inertia abnormal area and maintenance diagram
- Implementation
- Requires day/night/environment model
- critical acceptance
- Versus water/excavation true value, POD
IR188Candidate paths for building water leakage and dampness
- Minimum input and technical route
- LWIR L2/L3；T02
- target output
- Cold/hot anomalies and diffusion zones
- Implementation
- Requires multi-phase verification
- critical acceptance
- Compare with the results of moisture meter/wall opening; do not write the temperature difference directly as water
IR189Assisted locating of floor heating pipes, blockages and leaks
- Minimum input and technical route
- LWIR L2；T02+T04
- target output
- Pipeline heat traces, abnormal sections and coordinates
- Implementation
- Partially reusable
- critical acceptance
- Compare with piping diagram/pressure test, positioning error
IR190Curtain wall hollowing and debonding active/passive thermal detection
- Minimum input and technical route
- L3/L5；T10
- target output
- Abnormal area, area and depth candidates
- Implementation
- Required test block/environment design
- critical acceptance
- Contrast with knocking/pulling/opening, POD
IR191Drone thermal inspection and three-dimensional mapping of building facades
- Minimum input and technical route
- RGB-LWIR L4；T06+T15
- target output
- Facade thermal texture, defect location and area
- Implementation
- Need system integration
- critical acceptance
- Registration error, coverage, area error
IR192Joint verification of building thermal imaging and energy consumption model
- Minimum input and technical route
- L4+building parameters;T03+T20
- target output
- Abnormal components and simulated calibration data
- Implementation
- Requires building thermal model
- critical acceptance
- Compare with measured energy consumption/heat transfer test; do not calculate R value from thermal image alone
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.