- Reference
- Original file ID
- Purpose
- Access and geometry context
Illustrative report structure
Internal Blade Inspection Report
This page demonstrates an illustrative information structure without publishing field or customer imagery. It is not a customer report, a field-case record, an independent validation or a diagnosis of any asset.
WindInspectTech
Illustrative report structure- Reference
- WIT-SAMPLE-001
- System
- HZBR-60Pro
- Status
- Illustrative only
01 · Scope
Asset and inspection context
02 · Capture
Make source-file requirements explicit.
These code-native placeholders show where original files and their references belong in a controlled report. They do not depict a blade, product, defect or inspection result.
- Reference
- Capture + annotation IDs
- Purpose
- Human review trail
03 · Observation record
Separate capture from judgement.
| Field | Illustrative content | Review state |
|---|---|---|
| Position | Blade / cavity / distance from root / image reference | Captured |
| Observation | Visible surface feature and measurable dimensions | Human verification |
| Classification | Project defect taxonomy and applicable acceptance criteria | Engineering review |
| Next action | Monitor, re-inspect, evaluate or plan repair | Asset-owner decision |
- Field
- Position
- Illustrative content
- Blade / cavity / distance from root / image reference
- Review state
- Captured
- Field
- Observation
- Illustrative content
- Visible surface feature and measurable dimensions
- Review state
- Human verification
- Field
- Classification
- Illustrative content
- Project defect taxonomy and applicable acceptance criteria
- Review state
- Engineering review
- Field
- Next action
- Illustrative content
- Monitor, re-inspect, evaluate or plan repair
- Review state
- Asset-owner decision
Illustrative-content limitation
The reference, asset fields, observation fields, source-file slots and review states are constructed examples and do not come from a customer case. No product, field, customer or defect imagery is presented on this page. Actual report content depends on the approved inspection procedure, asset information, capture quality, project taxonomy and human engineering review.
Build the right record
Define the required review record.
We’ll map capture views, location fields, review states and export requirements to the documented configuration.