Service scope and implementation plan
direction numberD12
Demand scenario8 items
main inputMWIR/SWIR L1/L3；MWIR/LWIR L2/L3；MWIR L2/L3；L5
Typical routeT17、T19、T05、T10、T03
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
IR089Dynamic analysis of arc welding molten pool and heat affected zone
- Minimum input and technical route
- MWIR/SWIR L1/L3；T17
- target output
- Melt pool profile, temperature proxies and cooling rates
- Implementation
- Narrowband/high dynamic link required
- critical acceptance
- Contour error compared to high-speed camera/thermocouple
IR090Laser welding molten pool, keyhole and spatter thermal events
- Minimum input and technical route
- MWIR/SWIR L1/L3；T17+T19
- target output
- Melt-pool size, spatter and instability events
- Implementation
- Need high speed model
- critical acceptance
- Defect sample association, event recall, delay
IR091Resistance spot welding electrodes and solder joint thermal response
- Minimum input and technical route
- MWIR/LWIR L2/L3；T05
- target output
- Solder joint thermal profile, cooling time and anomalies
- Implementation
- Need craft true value
- critical acceptance
- Compare with pull-off/section test, classification F1
IR092Braze filler flow and joint thermal uniformity
- Minimum input and technical route
- MWIR L2/L3；T05+T17
- target output
- Flow regions, temperature windows and defect candidates
- Implementation
- Need test data
- critical acceptance
- Versus X-ray/section true value
IR093Active thermography crack and lack of fusion screening of welds
- Minimum input and technical route
- L5；T10
- target output
- Defect comparison, masking and depth candidates
- Implementation
- Need to add new core
- critical acceptance
- Artificial defect samples, POD, minimum defects
IR094Spatialization of reflow soldering heat curves for electronic packaging
- Minimum input and technical route
- LWIR/MWIR L2/L3；T03+T05
- target output
- Device Level Thermal Profiles and Temperature Zone Pass Status
- Implementation
- Requires macro radiation calibration
- critical acceptance
- Compared with the thermocouple furnace temperature plate, the curve error
IR095Ultrasonic welding, friction welding and thermocompression bonding heating modes
- Minimum input and technical route
- LWIR/MWIR L2/L3；T05
- target output
- Joint zone thermal proxy and anomaly classification
- Implementation
- Need product true value
- critical acceptance
- Comparison with strength/section tests, correlation and rejection
IR096Post-weld cooling, preheating and interpass temperature monitoring
- Minimum input and technical route
- LWIR L2/L3；T03+T19
- target output
- Workpiece temperature, waiting times and process events
- Implementation
- Partially reusable
- critical acceptance
- Compared with standard temperature measurement points, the event accuracy rate
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.