Service scope and implementation plan
direction numberD13
Demand scenario8 items
main inputMWIR/SWIR high speed L3; MWIR/LWIR L2/L3; MWIR/LWIR L1/L3; MWIR/SWIR L3
Typical routeT17、T05、T02、T19、T03、T10
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
IR097Laser powder bed melting pool monitoring
- Minimum input and technical route
- MWIR/SWIR high speed L3;T17
- target output
- Melt pool size, brightness/temperature proxies and anomalies
- Implementation
- Requires high-speed dedicated link
- critical acceptance
- Comparison with CT/metallographic defects, event Recall
IR098Heat accumulation and thermal field uniformity between additive layers
- Minimum input and technical route
- MWIR/LWIR L2/L3；T05+T17
- target output
- Stage temperature, heat accumulation and cooling constants
- Implementation
- Requires layer number synchronization
- critical acceptance
- Alignment with build logs, level errors
IR099Thermal response-assisted detection of powder coating defects
- Minimum input and technical route
- MWIR/LWIR L1/L3；T02+T19
- target output
- Candidates for powder shortage, powder accumulation and foreign matter
- Implementation
- Product data required
- critical acceptance
- Compare with powder laying diagram/CT after forming
IR100Directional energy deposition molten pool and powder feeding status
- Minimum input and technical route
- MWIR/SWIR L3；T17
- target output
- Melt pool, powder flow hot zone and trajectory stability
- Implementation
- Need high speed model
- critical acceptance
- Comparison with section/geometric truth
IR101Laser cutting punctures, undercuts and slag incidents
- Minimum input and technical route
- MWIR/SWIR L3；T17+T19
- target output
- Puncture time, heat traces and failure events
- Implementation
- Process data required
- critical acceptance
- Versus incision test, event F1
IR102Closed-loop observation of laser quenching and surface heat treatment temperatures
- Minimum input and technical route
- MWIR L2/L3；T03+T17
- target output
- Temperature field and scanning trajectory errors
- Implementation
- High temperature calibration required
- critical acceptance
- Compare with hardness/tissue and temperature measurement true values; perform additional safety verification in closed loop
IR103Active thermal NDT for additively formed parts
- Minimum input and technical route
- L5；T10
- target output
- Porosity/Unfused Candidates and Depth Proxies
- Implementation
- Reference test block required
- critical acceptance
- Compared with CT, POD, positioning error
IR104High energy beam equipment optical path and protective window thermal status
- Minimum input and technical route
- LWIR/MWIR L2/L3；T03+T05
- target output
- Protective window/mirror holder temperature rise and contamination candidates
- Implementation
- Required structural visibility conditions
- critical acceptance
- Trend advance compared to power/cleaning records
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.