Service scope and implementation plan
direction numberD21
Demand scenario8 items
main inputLWIR L2/L3; MWIR/LWIR L2/L3; LWIR/MWIR L2/L3; LWIR L2/L3+ process data
Typical routeT03、T04、T05、T17、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
IR161Abnormal insulation of reactor, tower and reboiler
- Minimum input and technical route
- LWIR L2/L3;T03+T04
- target output
- Shell Hot Zones, Insulation Defects and Trends
- Implementation
- Partially reusable
- critical acceptance
- Environment/Condition Record, Area IoU, Repeatability
IR162Fouling of the heat exchange network and reduced heat exchange efficiency Thermal mode
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Inlet and outlet heat distribution and fouling candidates
- Implementation
- Need process model
- critical acceptance
- Compare with heat transfer coefficient/cleaning results
IR163Distillation column flood, dry plate and abnormal temperature zone candidates
- Minimum input and technical route
- LWIR L2/L3;T05
- target output
- Axial Tropics, State Classification and Trends
- Implementation
- Structural/working condition data required
- critical acceptance
- Compare with differential pressure/sampling/operation records
IR164Reactor heating/cooling jacket uniformity
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Temperature field, hot and cold zones and response time
- Implementation
- Partially reusable
- critical acceptance
- Compare with the temperature point in the kettle/jacket
IR165Abnormal catalyst bed surface/shell temperature
- Minimum input and technical route
- MWIR/LWIR L2/L3;T05+T17
- target output
- Hot spots, temperature fronts and trends
- Implementation
- Heat transfer model required
- critical acceptance
- Compare with bed temperature measurement/process records
IR166Conveyor belt hot material, agglomeration and blockage detection
- Minimum input and technical route
- LWIR/MWIR L2/L3;T04+T19
- target output
- Material flow temperature, blockage and foreign matter events
- Implementation
- Requires motion model
- critical acceptance
- Event Recall, False Alarm/Hour, Beat
IR167Thermal inspection of chemical pumps, valves and flanges
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Part-level temperature and exception list
- Implementation
- Partially reusable
- critical acceptance
- Asset correlation rate, temperature error, missed detection
IR168Identification of thermal processes and abnormal stages during device start-up and shutdown
- Minimum input and technical route
- LWIR L2/L3+ process data;T05+T20
- target output
- Stages, deviation curves and review events
- Implementation
- Process data required
- critical acceptance
- Stage accuracy, change point latency, interpretability
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.