Service scope and implementation plan
direction numberD52
Demand scenario8 items
main inputL3/L5；LWIR L2/L4；TIR L2/L4；LWIR L2/L3
Typical routeT10、T02、T14、T05、T03、T17、T04、T07、T08、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
IR409Passive/active thermal detection of concrete bridge deck delamination
- Minimum input and technical route
- L3/L5；T10
- target output
- Delamination candidates, area and depth proxies
- Implementation
- Requires environment/test block design
- critical acceptance
- Versus percussion/radar/coring, POD
IR410Tunnel lining voids, leakage and shedding risks Thermal anomalies
- Minimum input and technical route
- LWIR L2/L4；T02+T14
- target output
- Exception areas, mileage and review points
- Implementation
- Multi-means truth value required
- critical acceptance
- Versus radar/drilling/manual inspection
IR411Road surface voids, repairs and water-containing thermal inertia differences
- Minimum input and technical route
- TIR L2/L4；T05+T14
- target output
- Abnormal area and road coordinates
- Implementation
- Requires sunshine/weather model
- critical acceptance
- Compared with drill core/radar, IoU
IR412Asphalt Paving Temperature Separation and Compaction Window
- Minimum input and technical route
- LWIR L2/L3；T03+T17
- target output
- Paving temperature maps, cold zones and events
- Implementation
- Vehicle/mileage synchronization required
- critical acceptance
- Versus core sample density/temperature
IR413Bridge expansion joints, bearings and drainage thermal anomaly candidates
- Minimum input and technical route
- LWIR L2/L4；T02+T04
- target output
- Component Hot Patterns and Review Checklists
- Implementation
- Need structure truth value
- critical acceptance
- Versus manual/displacement/leak inspection
IR414Hotspot inspection of tunnel electromechanical, cable and lighting equipment
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Equipment temperature and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Asset correlation rate, hot spots Recall
IR415Subway/tunnel fire and personnel perception at night
- Minimum input and technical route
- LWIR L3；T07+T08
- target output
- Personnel, fire and evacuation area incidents
- Implementation
- Security system required
- critical acceptance
- Fire/Thermal Equipment Interference Stratification, Event Recall
IR416Drone/vehicle infrastructure thermal image stitching and BIM/GIS association
- Minimum input and technical route
- RGB-IR L4；T06+T15
- target output
- Exception 3D location, assembly ID, and reporting
- Implementation
- Need system integration
- critical acceptance
- Registration P95, component correlation rate, coverage rate
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.