Service scope and implementation plan
direction numberD31
Demand scenario8 items
main inputLine array/area array LWIR L2/L3; LWIR L2/L4;
Typical routeT03、T07、T04、T14、T05、T06、T19、T02、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
IR241Axle box, wheel hub and brake disc temperature monitoring
- Minimum input and technical route
- Line array/area array LWIR L2/L3;T03+T07
- target output
- Vehicle number/axle location, temperature and hot axis alarm candidates
- Implementation
- Requires high-speed synchronization
- critical acceptance
- Speed/distance stratification, axis correlation rate, temperature error
IR242Pantographs, catenaries and electrical connection hotspots
- Minimum input and technical route
- LWIR L2/L4；T04+T14
- target output
- Hot spots, component locations and route coordinates
- Implementation
- Requires vehicle/drone integration
- critical acceptance
- Component Recall, mileage positioning error
IR243Inspection of trackside electrical cabinets, signaling equipment and transformers
- Minimum input and technical route
- LWIR L2/L3；T04+T05
- target output
- Equipment temperatures, anomalies and trends
- Implementation
- Partially reusable
- critical acceptance
- Asset binding rate, hot spots Recall
IR244Double-light inspection of running parts under the vehicle
- Minimum input and technical route
- RGB-LWIR L4；T06+T07
- target output
- Parts, foreign objects, temperature and missing status
- Implementation
- Product data required
- critical acceptance
- Part-level Recall, registration error, takt
IR245Detection of people, animals and foreign objects in tunnels at night
- Minimum input and technical route
- LWIR L3；T07+T19
- target output
- Targets, trajectories and limit violation events
- Implementation
- Scenario data required
- critical acceptance
- Long distance recall, false alarm/hour
IR246Candidates for leakage thermal anomalies in tracks, trackbeds and tunnels
- Minimum input and technical route
- LWIR L2/L4；T02+T14
- target output
- Exception areas, mileage and review points
- Implementation
- Required environment model
- critical acceptance
- Compared with manual/water content inspection, positioning error
IR247Train air conditioning, door and cabin thermal status inspection
- Minimum input and technical route
- LWIR L2/L3；T03+T04
- target output
- Air vent/door seal/cabin temperature and abnormalities
- Implementation
- Partially reusable
- critical acceptance
- Compare with temperature sensor/door status
IR248Track inspection infrared video and mileage synchronized archiving
- Minimum input and technical route
- L3/L4；T20
- target output
- Frame-mileage-asset association and auditable records
- Implementation
- Need system integration
- critical acceptance
- Synchronization error, missed frame rate, data integrity 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.