Fiber Analysisbeta

Drop a job's test files (OTDR traces, OLTS tables, fiber inspection and report files, from any manufacturer) and get one repair verdict per fiber, and a table of all fibers.

Checking access…

Frequently asked questions

How the whole-job analysis works, which files it reads, and where your data goes. New here? Start with the Fiber Analysis walkthrough.

What files can I drop in?

A whole job at once, from any manufacturer, mixed together: OTDR traces (.sor, Viavi multi-wavelength .msor, EXFO .trc / .trcx), OLTS light-source/power-meter results (EXFO .jolts), iOLM results (EXFO .bdr.json), and Viavi report JSON (.fcpro.json). Drop the files, and the tool sorts them into fibers on its own.

Does this upload my files anywhere?

Your test files are parsed entirely in your browser and never leave your machine. The only thing sent to the server is the short written review at the end, and only when you ask for it by pressing Run Analysis. Nothing is shared with anyone else.

Why did I need to give my email address?

Building and running the analysis summaries takes real work and real money, so access is gated to keep the tool from being abused. You sign in with your email (one tap on a link, no password), which ties usage to a real person and keeps the free version going.

Your address is only used to send that sign-in link. It isn't sold or shared, and we only email you about new tools or launches if you tick the optional opt-in box when you sign in.

How does it decide which files belong to the same fiber?

It reads the identifiers stored inside each file and the file names, then groups everything for one fiber together: both directions of an OTDR trace, the OLTS reading, and the iOLM result all land on one row. It handles reversed site order (A→B vs B→A), span and direction tags, and files that come from different instruments. If a file lands in the wrong group, you can fix its identifiers from the results without leaving the page.

What is bidirectional analysis?

When both directions of a span are present (A→B and B→A), the tool averages the two to report the true bidirectional loss, and it keeps the reflectance from each end (A and Z) so a bad connector isn't hidden by the averaging. Direction is read from the file's own AB / BA / OE / EO tag first, then the leading site name.

Can I change the pass/fail thresholds?

Yes. The Thresholds control above the results sets the mid-span loss, span attenuation, maximum link loss, and minimum ORL used to judge each fiber. Change them and the verdicts recompute immediately, no re-drop needed. If a file carries its own pass/fail limits, those win for that file.

How is this different from the Trace Analyzer?

The Trace Analyzer is for one file at a time: drop a single trace to see its waveform, event table, and numbers in detail. Fiber Analysis is for the whole job: drop everything, and get one plain-language repair verdict per fiber plus a table across all of them. Click any fiber in the table to open the underlying trace in the analyzer view.

What does the repair verdict tell me?

For each fiber you get a pass/fail call and a short read on what to do next: whether the span is clean, which event or connector is the likely culprit, and roughly where along the fiber to look. The table alongside it shows span length, total loss, worst reflectance, and how many events crossed your thresholds, so you can scan the whole job and jump straight to the fibers that need a truck roll.