Service scope and implementation plan
direction numberD20
Demand scenario8 items
main inputLWIR L2/L3;
Typical routeT03、T04、T17、T02、T19、T14、T08、T06、T05、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
IR153Thermal anomalies in wellhead, Christmas tree valves and flanges
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Component temperature, abnormality and inspection records
- Implementation
- Partially reusable
- critical acceptance
- Comparison with process parameters/contact temperature
IR154Heating furnace tubes and refractory hot spots
- Minimum input and technical route
- MWIR/LWIR L2/L3;T17
- target output
- Furnace tube/wall temperatures, hot spots and trends
- Implementation
- High temperature model required
- critical acceptance
- Compare with temperature measurement/furnace shutdown inspection
IR155Crude oil/natural gas pipeline insulation damage and leakage heat traces
- Minimum input and technical route
- LWIR L2/L3;T02+T19
- target output
- Anomalous areas, spreads and events
- Implementation
- On-site data required
- critical acceptance
- Minimum visible anomaly, false alarm/km
IR156Underground pipeline paths and leaky surface thermal anomaly candidates
- Minimum input and technical route
- UAV/Ground LWIR L2/L4;T14
- target output
- Thermal anomaly layer and review coordinates
- Implementation
- Required environment model
- critical acceptance
- Compare with excavation/pressure true value, positioning error
IR157Tank level, sedimentation and insulation abnormal thermal boundaries
- Minimum input and technical route
- LWIR L2;T02+T04
- target output
- Level/Deposition Candidates and Shell Hot Zones
- Implementation
- Requires working condition verification
- critical acceptance
- Compare with level gauge/tank clearing record
IR158Correlation between wellsite torch flame existence, stability and black smoke emission
- Minimum input and technical route
- MWIR/RGB L3/L4;T08+T06
- target output
- Flame states, swings and events
- Implementation
- Dual optical data required
- critical acceptance
- Compare to process/emission records, event F1
IR159UAV dual-light inspection of oil and gas facilities
- Minimum input and technical route
- RGB-LWIR/MWIR L4;T06+T14
- target output
- Assets, Thermal Anomalies, Visible Defects and GIS
- Implementation
- Need system integration
- critical acceptance
- Asset correlation rate, coverage rate, positioning error
IR160Thermal status baseline of similar equipment in pipeline stations
- Minimum input and technical route
- LWIR L2/L3;T05+T20
- target output
- Device fleet baselines, outliers, and review 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.