Service scope and implementation plan
direction numberD33
Demand scenario8 items
main inputLWIR L2/L3;MWIR/LWIR L2/L3;LWIR L2;MWIR/LWIR L3
Typical routeT04、T05、T03、T02、T07、T14、T08、T09、T06、T19
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
IR257Thermal inspection of electrical and rotating equipment in ship engine room
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Device temperatures, hotspots and trends
- Implementation
- Partially reusable
- critical acceptance
- Load/chamber temperature stratification, hot spots Recall
IR258Analysis of temperature difference between main engine exhaust, cylinder liner and shafting
- Minimum input and technical route
- MWIR/LWIR L2/L3;T03+T05
- target output
- Cylinder/component temperature differences and abnormal trends
- Implementation
- Demand condition model
- critical acceptance
- Compare with ship engine instrument/maintenance records
IR259Heat leakage from hull insulation, bulkheads and cold storage
- Minimum input and technical route
- LWIR L2;T02
- target output
- Abnormal areas and maintenance points
- Implementation
- Partially reusable
- critical acceptance
- Indoor and outdoor temperature difference/sea breeze stratification, area IoU
IR260Detection of boats, buoys and people on the sea surface at night
- Minimum input and technical route
- MWIR/LWIR L3;T07
- target output
- Goals, trajectories and confidence
- Implementation
- Need sea surface data
- critical acceptance
- Sea state/wave/distance stratification, false alarm/hour
IR261Search and geolocation of drowning persons
- Minimum input and technical route
- LWIR L3/L4;T07+T14
- target output
- Personnel candidates, trajectories and coordinates
- Implementation
- Search and rescue system required
- critical acceptance
- Detection distance, positioning error, time delay
IR262Monitoring of hot cargo, coal piles and dangerous goods in port yards
- Minimum input and technical route
- LWIR L2/L3;T05+T08
- target output
- Hot spots, growth trends and asset locations
- Implementation
- Partially reusable
- critical acceptance
- Discovery lead time, false positives/day
IR263Dual-light inspection of pipelines, flares and gas leaks on offshore platforms
- Minimum input and technical route
- OGI+LWIR/RGB L4;T09+T06
- target output
- Air plumes, hotspots, devices and events
- Implementation
- Requires dedicated system
- critical acceptance
- Controlled release/asset association/environment layering
IR264Ship-to-shore berthing night vision and personnel safety zone awareness
- Minimum input and technical route
- RGB-LWIR L4;T06+T07+T19
- target output
- Personnel, cable/equipment thermal targets and risk events
- Implementation
- Scenario data required
- critical acceptance
- Wind/Occlusion Layering, 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.