Service scope and implementation plan
direction numberD50
Demand scenario8 items
main inputHyperspectral L5; VNIR/SWIR L5; SWIR/Hyperspectral L5;
Typical routeT13、T14、T05、T08、T02、T07、T19、T04
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
IR393SWIR Spectral Classification of Minerals and Alteration Types
- Minimum input and technical route
- Hyperspectral L5;T13+T14
- target output
- Mineral class, abundance and confidence
- Implementation
- Requires spectral library/sample true value
- critical acceptance
- Spectral angle, Recall per class, instrument migration
IR394Automatic cataloging of rock core hyperspectral
- Minimum input and technical route
- VNIR/SWIR L5;T13
- target output
- Lithology/Mineral Distribution and Depth Index
- Implementation
- Need core true value
- critical acceptance
- Compare with geological catalog/XRD
IR395Ore grade and gangue SWIR sorting
- Minimum input and technical route
- SWIR/Hyperspectral L5;T13
- target output
- Grade/category and sorting signals
- Implementation
- Need to test the true value
- critical acceptance
- Blind test RMSE, sorting purity/recovery rate
IR396Self-heating and fire point monitoring of mine piles and coal piles
- Minimum input and technical route
- LWIR/TIR L2/L3;T05+T08
- target output
- Hot spots, growth trends and review coordinates
- Implementation
- Partially reusable
- critical acceptance
- Compared with internal probe/site control, lead time
IR397Candidates for water seepage and thermal inertia anomalies in open-pit mine slopes
- Minimum input and technical route
- TIR L2/L4;T02+T14
- target output
- Anomalies, change and GIS
- Implementation
- Requires geological/hydrological truth values
- critical acceptance
- Compare with monitoring holes/inspection; do not judge stability separately
IR398Remote sensing of geothermal anomalies, hot springs and volcanic hot areas
- Minimum input and technical route
- TIR L4/L5;T14
- target output
- Thermal anomalies, changes, and geographic layers
- Implementation
- Requires atmospheric/terrain correction
- critical acceptance
- Compare with ground temperature/geological survey
IR399Night vision of personnel, vehicles and heat sources in underground mines
- Minimum input and technical route
- LWIR L3;T07+T19
- target output
- Goals, trajectories and risk events
- Implementation
- Need underground data
- critical acceptance
- Dust/Humidity/Occlusion Layering
IR400Thermal inspection of mine conveying, crushing and electrical equipment
- Minimum input and technical route
- LWIR L2/L3;T04+T05
- target output
- Equipment temperature, blockage and abnormalities
- Implementation
- Partially reusable
- critical acceptance
- Compare with load/maintenance records
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.