Service scope and implementation plan
direction numberD22
Demand scenario8 items
main inputSpecial MWIR L3; Special LWIR L3; Corresponding special spectrum band L3;
Typical routeT09、T19、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
IR169Methane and hydrocarbon leak plume candidate detection
- Minimum input and technical route
- Special MWIR L3;T09
- target output
- Plume masking, duration and equipment association
- Implementation
- Requires dedicated camera/model
- critical acceptance
- Controlled release test, detection rate, false alarm rate
IR170SF₆ Leak Optical Imaging
- Minimum input and technical route
- Special LWIR L3;T09
- target output
- Air plumes, leak point candidates and fragments
- Implementation
- Narrowband equipment required
- critical acceptance
- Controlled release, distance/wind speed/background layering
IR171Refrigerant leak imaging
- Minimum input and technical route
- Special LWIR L3;T09
- target output
- Air plume candidates and equipment locations
- Implementation
- Need to match gas filter
- critical acceptance
- Compared with the leak detector, the minimum detectable conditions
IR172Imaging of specific gases such as CO/CO₂/NH₃
- Minimum input and technical route
- Corresponding to the special spectrum band L3;T09
- target output
- Air Feather Candidates and Category Configurations
- Implementation
- One gas and one verification required
- critical acceptance
- Spectral response, cross gas and environmental background testing
IR173Air plume movement, direction and origin point retrieval
- Minimum input and technical route
- OGI video L3;T09+T19
- target output
- Air plume optical flow, propagation direction and source point candidates
- Implementation
- Partially reusable optical flow
- critical acceptance
- Compared with known source/wind field, source point error
IR174Fixed OGI continuous monitoring and alarm deduplication
- Minimum input and technical route
- OGI L3；T09+T20
- target output
- Event, duration, device ID, and evidence
- Implementation
- Requires system implementation
- critical acceptance
- False positives/day, online rate, discovery and recovery time
IR175Quantitative OGI leak rate estimate
- Minimum input and technical route
- Radiation OGI+special calibration L5;T09
- target output
- Mass/Volume Leak Rate and Range
- Implementation
- Requires dedicated quantitative core
- critical acceptance
- Controlled flow, gas response factors, wind/ΔT/distance stratification
IR176OGI Joint positioning with point gas sensor
- Minimum input and technical route
- OGI+sensor L4;T09+T20
- target output
- Plumes, concentration points and combined risks
- Implementation
- Requires multi-source integration
- critical acceptance
- Space-time synchronization, source positioning error, event recall
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.