Service scope and implementation plan
direction numberD32
Demand scenario8 items
main inputL5；MWIR L2/L3；LWIR L2/L3；LWIR/RGB-LWIR L4
Typical routeT10、T17、T03、T04、T06、T07、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
IR249Aerospace composite skin delamination thermal NDT
- Minimum input and technical route
- L5；T10
- target output
- Delamination/Debonding Masks and Depth Candidates
- Implementation
- Standard test block required
- critical acceptance
- Perform POD, minimum defects and repeatability according to applicable procedures
IR250Water accumulation in honeycomb structures and thermal inspection of repair areas
- Minimum input and technical route
- L5；T10
- target output
- Water accumulation/repair abnormal areas
- Implementation
- Reference parts required
- critical acceptance
- Compare with ultrasound/X-ray/disassembly inspection
IR251Engine ground test hot field and jet flow observation
- Minimum input and technical route
- MWIR L2/L3；T17
- target output
- Hot zones, jet boundaries and transients
- Implementation
- Highly dynamic dedicated system required
- critical acceptance
- Synchronization with instrumentation/commissioning parameters, saturation and time delays
IR252Wheels, brakes and landing gear overheating checks
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Wheel position temperature, left-right difference and cooling trend
- Implementation
- Partially reusable
- critical acceptance
- Compare with standard temperature measurement/maintenance limit process
IR253Airport runway night vision for people, animals and foreign objects
- Minimum input and technical route
- LWIR/RGB-LWIR L4；T06+T07
- target output
- Target, trajectory and runway incursions
- Implementation
- Requires airport scene data
- critical acceptance
- Long range Recall, false alarm/hour, delay
IR254Inspection of ground thermal anomalies in aviation electrical/hydraulic systems
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Part temperature and leak/overheat candidates
- Implementation
- Need to maintain true value
- critical acceptance
- Versus maintenance inspection, component level Recall
IR255Thermal image recording of spacecraft thermal vacuum test
- Minimum input and technical route
- MWIR/LWIR L2/L3；T03+T20
- target output
- Surface temperature fields, phases and anomalies
- Implementation
- Vacuum window calibration required
- critical acceptance
- Compared with thermocouple/test timing, temperature error
IR256Thermal cycle and thermal balance analysis of satellite components
- Minimum input and technical route
- L2/L3+telemetry;T05+T20
- target output
- Thermal Gradient, Steady State and Model Differences
- Implementation
- demand heat model
- critical acceptance
- Versus thermal math model/telemetry, residuals and reproducibility
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.