Service scope and implementation plan
direction numberD23
Demand scenario8 items
main inputLWIR L2/L3；LWIR L2/L4；L4
Typical routeT02、T04、T05、T03、T15、T19、T14、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
IR177Tank Level and Floating Pan Status Thermal Boundaries
- Minimum input and technical route
- LWIR L2/L3；T02+T04
- target output
- Candidates for liquid level line and floating plate anomalies
- Implementation
- Requires working condition verification
- critical acceptance
- Compare with liquid level gauge/can opening record, position error
IR178Candidates for insulation under tank wall insulation defects, deposits and corrosion
- Minimum input and technical route
- LWIR L2/L3；T02+T05
- target output
- Thermal anomaly areas and review sequencing
- Implementation
- Multi-means truth value required
- critical acceptance
- Versus UT/CUI check, POD
IR179Damaged heat pipe insulation and thermal bridging of brackets
- Minimum input and technical route
- LWIR L2/L4；T03+T15
- target output
- Defect area, area and spatial coordinates
- Implementation
- Partially reusable
- critical acceptance
- Area IoU, positioning error, environment stratification
IR180Valve internal leakage and abnormal valve position thermal mode
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Pre- and post-valve thermal patterns and status candidates
- Implementation
- Required working condition true value
- critical acceptance
- Compare with flow/pressure difference/maintenance results
IR181Flange and mechanical seal liquid leakage heat traces
- Minimum input and technical route
- LWIR L2/L3；T02+T19
- target output
- Wet Zone/Leak Candidates, Spreads and Events
- Implementation
- Scenario data required
- critical acceptance
- Minimum leakage, false alarms/day, discovery latency
IR182Pipe blockage, wax build-up and material accumulation thermal modes
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Temperature zone and blockage location candidates
- Implementation
- Heat transfer/working condition model required
- critical acceptance
- Compare with pigging/pressure difference/pipe opening results
IR183Buried thermal pipe network leakage drone/vehicle screening
- Minimum input and technical route
- LWIR L2/L4；T14
- target output
- Surface thermal anomalies, GIS coordinates and review points
- Implementation
- Seasonal model required
- critical acceptance
- Excavation true value, positioning P95, false alarm/km
IR184Pipe network anomaly heat map associated with maintenance work orders
- Minimum input and technical route
- L4；T05+T20
- target output
- Assets, Exceptions, History and Priorities
- Implementation
- Requires business integration
- critical acceptance
- Asset matching rate, work order hit rate, audit completeness
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.