Service scope and implementation plan
direction numberD27
Demand scenario8 items
main inputLWIR/MWIR L2/L3; LWIR L3; UAV/Fixed MWIR/LWIR L3/L4; LWIR L2/L3
Typical routeT08、T19、T07、T14、T05、T03、T15
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
IR209Early hot spot and open flame detection outdoors/indoors
- Minimum input and technical route
- LWIR/MWIR L2/L3;T08+T19
- target output
- Fire point, flame, persistence and alarm
- Implementation
- Fire scene data required
- critical acceptance
- Different fire source/reflection/thermal equipment layering, event Recall
IR210Searching for people and heat sources under smoke cover
- Minimum input and technical route
- LWIR L3;T07+T08
- target output
- Person/heat source boxes, trajectories and confidence
- Implementation
- Fire scene data required
- critical acceptance
- Visibility/smoke density/distance stratification, missed detection rate
IR211Fire spread front and burned area tracking
- Minimum input and technical route
- UAV/Fixed MWIR/LWIR L3/L4;T08+T14
- target output
- Line of fire, speed, direction, and geography layers
- Implementation
- Requires geographical integration
- critical acceptance
- Fire line position error, update delay
IR212Troubleshooting of residual fire, smoldering and re-ignition points
- Minimum input and technical route
- LWIR L2/L3;T08
- target output
- Hot spots, cooling trends and review checklists
- Implementation
- Partially reusable
- critical acceptance
- Comparison with manual peeling/contact temperature measurement
IR213Thermal runaway fire warning for batteries, stockpiles and warehouses
- Minimum input and technical route
- LWIR L2/L3;T05+T08
- target output
- Rising trends, risk stratification and events
- Implementation
- Need accident sample
- critical acceptance
- Early detection and omissions are discovered; not solely responsible for firefighting linkage
IR214Firefighter Thermal Exposure and Equipment Surface Temperature Recording
- Minimum input and technical route
- LWIR L2/L3;T03+T07
- target output
- Personnel/equipment surface temperature and exposure time
- Implementation
- Need for ethical and safe design
- critical acceptance
- Compare to wearable sensors; not equivalent to core body temperature
IR215Observation of sprinkler, fire hose and cooling coverage effects
- Minimum input and technical route
- LWIR L2/L3;T03+T05
- target output
- Cooling zones, cooling rates and coverage gaps
- Implementation
- Requires controlled testing
- critical acceptance
- Area coverage compared to flow/temperature points
IR216Review of building hot spots after fire disposal
- Minimum input and technical route
- LWIR L2/L4;T08+T15
- target output
- Structural surface hot spots and spatial locations
- Implementation
- Requires structural professional review
- critical acceptance
- Positioning error, review consistency; does not replace structural safety appraisal
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.