Service scope and implementation plan
direction numberD11
Demand scenario8 items
main inputMWIR/SWIR L2/L3；MWIR L2/L3；LWIR/MWIR L2/L3；MWIR/LWIR L2/L3
Typical routeT17、T05、T03、T19、T02
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
IR081Surface temperature uniformity of billets, ingots and slabs
- Minimum input and technical route
- MWIR/SWIR L2/L3；T17
- target output
- Surface temperature, longitudinal and transverse uniformity and cold spots
- Implementation
- High temperature calibration required
- critical acceptance
- Compared with the standard temperature measurement/process point, the temperature is P95
IR082Uneven heating mode of continuous casting billet solidification and secondary cooling
- Minimum input and technical route
- MWIR L2/L3；T05+T17
- target output
- Temperature field, secondary cooling anomalies and trends
- Implementation
- Need process model
- critical acceptance
- Compare with water volume/pulling speed/defect records
IR083Refractory lining hot spots for ladles, ladles and tundishes
- Minimum input and technical route
- LWIR/MWIR L2/L3；T03+T17
- target output
- Exterior hotspots, growth rates and risk zones
- Implementation
- True value of life required
- critical acceptance
- Comparing with the shutdown internal inspection/lining thickness, it is found that the advance amount
IR084Lateral temperature distribution of rolls, strips and plates
- Minimum input and technical route
- MWIR/SWIR L2/L3；T17
- target output
- Temperature contours, edge differences and process states
- Implementation
- Requires high-speed synchronization
- critical acceptance
- Line speed/emissivity stratification, contour error
IR085Temperature window for forgings coming out of furnace, transfer and final forging
- Minimum input and technical route
- MWIR L2/L3；T03+T19
- target output
- Workpiece temperature, window status and timeout events
- Implementation
- Requires object tracking
- critical acceptance
- Compared with contact/optical temperature measurement, event accuracy rate
IR086Observation of casting mold filling and solidification thermal processes
- Minimum input and technical route
- MWIR/LWIR L2/L3；T05+T17
- target output
- Thermal fronts, cooling curves and uneven areas
- Implementation
- Need to test tooling
- critical acceptance
- Time synchronization, curve repeatability, defect correlation
IR087Thermal mode of interface between aluminum liquid, copper liquid and slag layer
- Minimum input and technical route
- MWIR/SWIR L2/L3；T17
- target output
- Liquid level, slag zone and temperature agents
- Implementation
- Spectral band/emissivity verification required
- critical acceptance
- Compare to sampling/operational records; reflections and smoke stratification
IR088Metallurgical equipment water cooling leaks and abnormal cold spots
- Minimum input and technical route
- LWIR/MWIR L2/L3；T02+T19
- target output
- Cold Spots, Diffusion Zones and Events
- Implementation
- Partially reusable
- critical acceptance
- Compare with flow/maintenance records, false alarm/shift
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.