Service scope and implementation plan
direction numberD08
Demand scenario8 items
main inputLWIR L2/L3; multi-source L4
Typical routeT03、T05、T04、T07、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
IR057Abnormal temperature rise and left-right difference of bearing seat
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Bearing housing temperatures, differences and trends
- Implementation
- Reusable general statistics
- critical acceptance
- Compare with contact temperature/vibration, alarm advance amount
IR058Insufficient gearbox lubrication or candidate for friction heating
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Cabinet thermal patterns and anomaly scores
- Implementation
- Required working condition true value
- critical acceptance
- Oil volume/load/speed stratification, status F1
IR059Coupling misalignment thermal pattern assisted identification
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Temperature difference between two ends, periodic changes and candidate causes
- Implementation
- Requires multi-sensor true values
- critical acceptance
- Compare with vibration/laser alignment results; do not determine cause alone
IR060Belt slipping and wheel grooves are abnormally hot
- Minimum input and technical route
- LWIR L2/L3；T07+T05
- target output
- Belt/pull temperature, slip events
- Implementation
- Target tracking required
- critical acceptance
- Speed/load tiering, event recall, latency
IR061Chain drive lubrication and stuck heat abnormalities
- Minimum input and technical route
- LWIR L2/L3；T07+T05
- target output
- Segment hot spots, location and duration
- Implementation
- Requires motion compensation
- critical acceptance
- Position error, missed detection rate, speed stratification
IR062Mechanical seal friction heat abnormality
- Minimum input and technical route
- LWIR L2/L3；T03+T05
- target output
- Temperature rise and trend in the vicinity of the sealing surface
- Implementation
- Partially reusable
- critical acceptance
- Advance compared to leakage/vibration records
IR063Modeling of bearing start-stop thermal inertia and cooling constants
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Time constant, baseline and deviation
- Implementation
- Reusable A24/A77
- critical acceptance
- Repeated working condition fitting error, parameter stability
IR064Combined thermal imaging, vibration and acoustic mechanical diagnosis
- Minimum input and technical route
- Multi-source L4;T05+T20
- target output
- Fault Candidates, Evidence Weight, and Rejection
- Implementation
- Multimodal model required
- critical acceptance
- Independent failure test, Macro-F1, calibration confidence
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.