Direct answer
PDF supports reading and sign-off; native OTDR trace files preserve data for compatible review software. Specify SOR or the instrument's supported native format and link fiber IDs, direction, wavelength, acquisition settings and report revisions. Complete files alone do not establish valid testing or acceptance.
Separate readable reports from reviewable traces
The VIAVI SmartOTDR getting-started manual distinguishes traces from PDF and other outputs and records job, cable, fiber and direction information. This is a manufacturer workflow, not a guarantee of identical files across all instruments.
Use this guide for preterminated trunks, installed-fiber acceptance and outsourced testing. Specify insertion loss, return loss and other required tests separately; an OTDR package does not replace their methods or data.
| Deliverable | Purpose | Suggested review |
|---|---|---|
| Reading and sign-off | Identity, direction, wavelength, criteria | |
| Native trace | Review in compatible software | Format, opening and completeness |
| File index | Map data to physical channels | Endpoints, fiber, wavelength, direction |
| Configuration record | Explain acquisition | Instrument, acquisition and analysis conditions |
| Revision record | Preserve review history | Originals, change reasons and approval |
Do not infer trace contents from file count
The VIAVI OTDR application manual distinguishes single-trace .sor and combined .msor settings. Before delivery, open representative files in the agreed software and confirm the included wavelengths, directions and traces.
One physical file may contain multiple traces; a PDF may contain multiple pages. Audit completeness against the contracted test combinations rather than file count alone.
For an original planning example, an order specifying 12 fibers, two wavelengths and two directions creates 48 combinations to account for. This arithmetic does not require every project to use bidirectional, dual-wavelength testing.
Name records so they remain traceable
An index can hold job ID, cable ID, endpoint names, fiber, direction, wavelength, native filename and PDF filename. Agree a readable convention without forcing every field into an unwieldy filename. Keep folder structure and index consistent.
Store first-acquisition records, processed files and approved reports separately. Document revised event markers, corrected identification and changed analysis conditions. Generating another PDF is not a new acquisition, and post-processing must not be presented as an original field reading.
Delivery checklist for a test provider
| Check | Suggested method | Unsupported inference |
|---|---|---|
| Files open | Trial with agreed software/version | Universal cross-vendor compatibility |
| Combinations complete | Compare with fiber/direction/wavelength index | More files means no missing tests |
| Parameters traceable | Review acquisition and analysis records | A pass icon validates the method |
| Reports consistent | Match PDF to native traces | Conversion cannot change content |
| Integrity retained | Optional hashes and handover list | A hash proves measurement accuracy |
Indexes, hashes and revision controls are editorial delivery recommendations, not universal contractual provisions from the cited manuals. Acceptance still requires review of reference methods, launch/receive fibers, settings and criteria.
Procurement FAQ
- Is PDF-only delivery automatically nonconforming? It depends on the contract. Specify native records before testing when later trace review is required.
- Does SOR guarantee cross-brand readability? Validate actual software and versions; the extension alone cannot guarantee it.
- Can screenshots replace native records? Screenshots support communication but do not provide equivalent trace-review capability.
- Can relabeling create a reverse-direction test? No. Direction must describe the actual acquisition; renaming cannot fill missing tests.
- Does a complete package establish fiber acceptance? Review method, settings, boundaries and criteria as well. File completeness is only one check.
Related products and reading
- OTDR launch-cable configurations
- OLTS versus OTDR acceptance
- OTDR pulse width and event resolution
- OTDR length and IOR
Product links support configuration review. Suitability and parameters depend on the agreed actual specification, without implying new certification or availability.
Contact an engineer with configuration drawings or test requirements
Sources and review date
Reviewed on 2026-10-16. Source publication dates remain separate from this review date. Procurement checklists are editorial recommendations; numerical examples illustrate assumptions, not actual specimen results.
Sources checked: 2026-10-16