Service scope and implementation plan
direction numberD57
Demand scenario8 items
main inputNIR/SWIR L1/L5；LWIR L2/L3；L5；NIR L1
Typical routeT12、T02、T10、T05、T08、T13、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
IR449Paint base sketch, overlay and repair area NIR/SWIR Observation
- Minimum input and technical route
- NIR/SWIR L1/L5；T12
- target output
- Hide textures, material differences and regions
- Implementation
- Requires professional interpretation of cultural relics
- critical acceptance
- Compare to multispectral/material analysis; non-destructive priority
IR450Murals, wood vessels and stone cultural relics are abnormally affected by the heat
- Minimum input and technical route
- LWIR L2/L3；T02
- target output
- Temperature difference zone and review position
- Implementation
- Requires environment/water content true value
- critical acceptance
- Compare with moisture meter/professional inspection
IR451Active thermal detection of hollowing and delamination in architectural heritage
- Minimum input and technical route
- L5；T10
- target output
- Abnormal area, area and depth candidates
- Implementation
- Need low-risk incentive plan
- critical acceptance
- Compared with percussion/ultrasound, cultural relics safety review
IR452Antique books, faded ink, and charcoal ink NIR Enhanced
- Minimum input and technical route
- NIR L1
- target output
- Text/handwriting enhanced image and original image coordinates
- Implementation
- Partially reusable enhancement/OCR
- critical acceptance
- Expert readability, enhancement artifacts, and review
IR453Study of residual heat traces and traces of recent contact at the site
- Minimum input and technical route
- LWIR L2/L3；T05
- target output
- Short-term thermal changes and candidate regions
- Implementation
- Controlled forensic testing required
- critical acceptance
- Time window/material/environment layering; not used as evidence of identity or time alone
IR454Review of residual heat and electrical hot spots at fire scene
- Minimum input and technical route
- LWIR L2/L4；T08
- target output
- Hotspots and spatial locations
- Implementation
- Partially reusable
- critical acceptance
- Compare with on-site inspection/evidence collection process
IR455Multispectral differences in counterfeit materials, inks and repair areas
- Minimum input and technical route
- NIR/SWIR L5；T13
- target output
- Material classes and abnormal areas
- Implementation
- Spectrum/laboratory true value required
- critical acceptance
- Each type of Recall, unknown material rejection
IR456Cultural museum/forensic infrared raw data, parameters and evidence chain archiving
- Minimum input and technical route
- arbitrary;T20
- target output
- Raw frames, metadata, processing records and hashes
- Implementation
- Evidence collection process required
- critical acceptance
- Integrity, repeatability, permissions and timestamps
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.