Service scope and implementation plan
direction numberD34
Demand scenario8 items
main inputRGB-LWIR+pose L4; RGB-IR L4;
Typical routeT04、T15、T14、T20、T07、T08
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
IR265Hotspot identification and positioning of inspection robot equipment
- Minimum input and technical route
- RGB-LWIR+pose L4;T04+T15
- target output
- Device ID, thermal anomaly, and 3D coordinates
- Implementation
- Need system integration
- critical acceptance
- Positioning error, device association rate, hot spot recall
IR266UAV infrared aerial survey and automatic abnormal go-around
- Minimum input and technical route
- RGB-IR L4;T14+T20
- target output
- Tracks, outliers, missed approach missions and coverage
- Implementation
- Required task system
- critical acceptance
- Coverage rate, repetition rate, abnormal return visit success rate
IR267Pedestrian/obstacle detection by mobile robot in dark environment
- Minimum input and technical route
- LWIR+depth L4;T07+T15
- target output
- Obstacles, People, Distances and Feasible Zones
- Implementation
- Multi-sensor model required
- critical acceptance
- Obstacle Recall, distance error, frame rate
IR268Fire extinguishing robot fire source and high temperature area navigation
- Minimum input and technical route
- LWIR/MWIR+depth L4;T08+T15
- target output
- Fire source, temperature zone, passable zone
- Implementation
- Security system required
- critical acceptance
- Thermal saturation/smoke stratification, navigation success rate
IR269Robotic arm grabs high-temperature/low-temperature workpiece identification
- Minimum input and technical route
- LWIR+RGB-D L4;T04+T15
- target output
- Workpiece, temperature, grasping posture and prohibited grasping status
- Implementation
- Calibration required for integration
- critical acceptance
- Position error, temperature gating missed decision rate
IR270Agricultural robot crop/animal sensing at night
- Minimum input and technical route
- NIR/LWIR L3/L4;T07
- target output
- Crop rows, animals, obstacles and tracks
- Implementation
- Scenario model required
- critical acceptance
- Night/Dust/Occlusion Layering
IR271Heat source following, charging stand or device mark positioning
- Minimum input and technical route
- NIR/LWIR L3;T07+T15
- target output
- Target orientation, distance and docking status
- Implementation
- Geometric calibration required
- critical acceptance
- Angle/distance error, docking success rate
IR272Multi-robot thermal anomaly map fusion
- Minimum input and technical route
- Multi-machine L4;T15+T20
- target output
- Merge maps, anomaly deduplication and provenance
- Implementation
- Requires multi-machine system
- critical acceptance
- Map alignment error, repetition rate, synchronization delay
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.