OTDR Trace Reader

— Who this is for

Outside-plant techs, splicers, last-mile ISP field crews — anyone who has to interpret a trace at 2am and call back the dispatcher with a real answer.

— What you get on setup day

• A workflow that ingests SOR files (Bellcore standard) and outputs a clean event table
• Event-by-event interpretation in plain English — splice loss, connector loss, macrobend flag
• Distance + loss budget against your run spec — flags whether you're in or out of tolerance
• Fault-location callout if a reflection event is high enough to be a break
• Customer-facing summary PDF for the ticket close-out (clean, single page, signed)
• 60-min setup call to load YOUR run spec + loss budget so the tolerance flags are calibrated for your network

— How it runs after setup

1. 01Drop the SOR file (or a photo of the trace screen if that's all you have)
2. 02Tool extracts the event table — distance, loss, type, reflection
3. 03Compares against your loss budget and flags the issue
4. 04Outputs the "here's what's wrong, here's where" summary for dispatch
5. 05Customer summary PDF generates automatically when you mark the ticket closed

— Sample questions you can ask

The notebook answers things like this, with the source page cited every time:

• "What's the loss budget violation on this trace?"
• "Walk me through the events on this trace in plain English"
• "Estimate fault location based on the largest reflection"
• "Compare this trace to last month's baseline for the same run"

— Not built for this

Honest scope. If you need any of these, it's a different conversation:

• OTDR-side configuration or pulse-width tuning — that's still you and the instrument
• Permanent baseline storage at scale — pair with a network-monitoring platform if you need that
• iOLM-style multi-pulse analysis (single-trace SOR for now)

— Subscriptions you keep

You pay these vendors direct. I don't mark them up, I don't host your data behind a wall. Your account, your seat.