Service scope and implementation plan
direction numberD07
Demand scenario8 items
main inputLWIR L2/L3；LWIR L2；MWIR/LWIR L2/L3
Typical routeT03、T05、T04、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
IR049Motor bearing end and frame temperature rise monitoring
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- End cap/frame temperatures, gradients and trends
- Implementation
- Partially reusable
- critical acceptance
- Compared with the embedded temperature measurement/load, the temperature is P95
IR050Unbalanced heating of motor three-phase wiring and cables
- Minimum input and technical route
- LWIR L2；T03+T04
- target output
- Three-phase temperature difference and abnormal terminals
- Implementation
- Partially reusable
- critical acceptance
- Current balance conditions, object correlation rate, false alarms
IR051Frequency converter IGBT/MOSFET and heat sink hot spots
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Device/heatsink temperature and dynamic response
- Implementation
- Partially reusable
- critical acceptance
- Transient time error vs. onboard sensor/power
IR052Motor cooling duct is blocked and fan fails
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Thermal distribution pattern and cooling status
- Implementation
- Need fault sample
- critical acceptance
- Status F1, discovery time, environment tiering
IR053Thermal imaging laboratory testing of winding ends
- Minimum input and technical route
- MWIR/LWIR L2/L3；T03+T05
- target output
- Winding thermal distribution and local temperature rise
- Implementation
- Need to test tooling
- critical acceptance
- Comparison with embedded thermocouple and explanation of field of view occlusion
IR054Analysis of thermal cycle of servo motor frequently starting and stopping
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Periodic temperature rise, cooling constant and cumulative trend
- Implementation
- Reusable timing module
- critical acceptance
- Cycle synchronization error, curve repeatability
IR055Thermal status monitoring of braking resistors and reactors
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Component Temperature, Sustained Overruns and Load Dependencies
- Implementation
- Partially reusable
- critical acceptance
- Power condition stratification, threshold false alarm rate
IR056Thermal health ranking of motor groups of the same model
- Minimum input and technical route
- LWIR L2/L3；T05+T20
- target output
- Normalized thermal features, outlier ranking
- Implementation
- Partially reusable
- critical acceptance
- Cross-environment correction, sorting stability, fault hit 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.