Service scope and implementation plan
direction numberD17
Demand scenario8 items
main inputL5;L4/L5
Typical routeT10、T15、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
IR129CFRP/GFRP layered flash thermography
- Minimum input and technical route
- L5;T10
- target output
- Layered masks, contrast and depth candidates
- Implementation
- Need to add new core
- critical acceptance
- Artificial defect test block, POD, depth delamination
IR130Honeycomb interlayer water accumulation, debonding and core damage
- Minimum input and technical route
- L5;T10
- target output
- Water ponding/debonding candidates, area and location
- Implementation
- Need reference sample
- critical acceptance
- Compare with ultrasound/X-ray/disassembly inspection
IR131Screening for lack of glue, weak adhesion and debonding of adhesive joints
- Minimum input and technical route
- L5;T10
- target output
- Abnormal bonding area and confidence level
- Implementation
- Experimental design required
- critical acceptance
- Compared with mechanical damage/ultrasonic true value, POD
IR132Coating thickness and thermal response to delamination
- Minimum input and technical route
- L5;T10
- target output
- Coating anomalies and thickness regression candidates
- Implementation
- Requires physical calibration
- critical acceptance
- Compared with section/eddy current thickness measurement, RMSE
IR133Composite thermal NDT after impact damage
- Minimum input and technical route
- L5;T10
- target output
- Impact Damage Range and Depth Proxy
- Implementation
- Need impact sample
- critical acceptance
- Compared with ultrasound C-scan/CT, IoU
IR134Vibration thermography fatigue crack detection
- Minimum input and technical route
- L5;T10
- target output
- Crack heat source and location
- Implementation
- Requires vibration tooling
- critical acceptance
- Compared with penetration/micro/ultrasound, minimal cracks
IR135Automatic scanning of large-area composite materials for wind power/aviation
- Minimum input and technical route
- L4/L5;T10+T15
- target output
- Stitching defect maps, 3D locations and coverage
- Implementation
- Requires robot integration
- critical acceptance
- Coverage completeness, registration error, POD
IR136HOT NDT DATA DICONDE ARCHIVE
- Minimum input and technical route
- L5;T20
- target output
- Raw sequences, parameters, results and portable archives
- Implementation
- Requires standard implementation
- critical acceptance
- Field completeness, cross-software readability and auditing
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.