Service scope and implementation plan
direction numberD53
Demand scenario8 items
main inputLWIR L2/L3; Macro LWIR/MWIR L2/L3;
Typical routeT03、T04、T05、T02、T19、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
IR417Server cabinet air inlet and outlet and hot spot monitoring
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Cabinet temperatures, hot and cold zones and trends
- Implementation
- Partially reusable
- critical acceptance
- Versus cabinet sensors/loads
IR418CPU/GPU/acceleration card board-level thermal evaluation
- Minimum input and technical route
- Macro LWIR/MWIR L2/L3;T03+T05
- target output
- Device/heatsink temperature and transients
- Implementation
- Requires macro calibration
- critical acceptance
- Versus on-chip/thermocouple, temperature P95
IR419PDU, UPS, battery and busbar connection hotspots
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Device/junction temperature and anomalies
- Implementation
- Partially reusable
- critical acceptance
- Compare with load/maintenance results
IR420Cold aisle containment, air leakage and airflow organization assessment
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Hot and cold mixing zone and air outlet status
- Implementation
- Requires environmental sensing
- critical acceptance
- Compare with air volume/temperature point
IR421Thermal abnormalities of liquid cooling pipelines, cold plates and quick connectors
- Minimum input and technical route
- LWIR L2/L3;T02+T05
- target output
- Uneven Cooling, Leak Candidates and Trends
- Implementation
- Required flow/pressure true value
- critical acceptance
- Compare with cooling system instrumentation
IR422Base station RF power amplifier, power supply and feeder hotspots
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Component temperature rise and load correlation
- Implementation
- Partially reusable
- critical acceptance
- Compare with power/alarm/maintenance
IR423Outdoor communication cabinet door seal, heating and cooling status
- Minimum input and technical route
- LWIR L2/L3;T03+T19
- target output
- Thermal distribution, door status and environmental events
- Implementation
- Partially reusable
- critical acceptance
- Compare with door sensor/air conditioner status
IR424Computing equipment thermal imaging and telemetry combined capacity/fault analysis
- Minimum input and technical route
- L4;T05+T20
- target output
- Thermal status, telemetry correlation and exception sequencing
- Implementation
- Multi-source model required
- critical acceptance
- Time synchronization, correlation, 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.