OTDR testing sends light pulses into a fibre and measures the reflections to map loss, joints, connectors and faults along its length. It is paired with a light source and power meter test that measures total link loss. Shruti IT Service tests, certifies and audits fiber links, and issues reports suitable for handover and client sign-off.
At a glance
- Typical timeline
- A 24-fibre route is usually tested in a day or two, depending on access and length.
- Key standards
- ITU-T G.652.D attenuation, TIA-568 and ISO/IEC 11801 channel testing practice.
- What you receive
- OTDR traces in native and PDF form, power meter results, loss budget comparison and a summary.
- Best suited for
- Project handover, acceptance tests, troubleshooting and audits of existing networks.
- Our scope
- OTDR traces, power meter testing, certification reports, fault location and third-party audit.
- Site survey
- Access points, connector types and fibre counts are confirmed before testing is scheduled.
OTDR Testing & Certification Overview
OTDR testing is how you find out what your fibre actually does. An optical time-domain reflectometer sends short light pulses down the fibre and records the light that returns. From that return, it draws a trace showing the length of the link, the loss of each splice and connector, the attenuation of the cable and the position of any break or sharp bend. A trace is a picture of the link, and a skilled technician can read it like a map.
We pair the OTDR with a light source and power meter test. The OTDR shows events along the route. The power meter measures the total loss end to end, which is what the optics in your switches will actually experience. For acceptance, many specifications require both, because each catches things the other misses. The OTDR can miss loss at the first or last connector, where its dead zone hides detail, and the power meter cannot say where a loss sits.
Certification means comparing results with a stated limit. We build a loss budget in the design: fibre attenuation times length, plus splices and connectors, plus margin. Test results are then reported against that budget. A link that passes is documented, and a link that fails is investigated, with the trace pointing to the joint or bend responsible. The report is signed off by your representative or consultant.
The same service is used on existing networks. If you inherited a fibre network with no records, or you suspect degradation after road works or monsoon, a third-party style audit tests every link, builds a baseline and flags the weak points. That baseline is the starting point for any future AMC, and comparing it with later traces shows slow changes that would otherwise go unnoticed.
Ideal for: Project handovers, acceptance tests and troubleshooting.
What Our OTDR Testing & Certification Includes
Our OTDR testing and certification scope covers measurement, fault location, reporting and audit. All results are delivered in readable and native formats.
OTDR trace testing and fault location
We take traces in both directions with launch and receive leads, set the correct index and pulse width, and mark events. On a failing link we locate the fault distance and match it to the route map. Tip: ask for native trace files as well as PDFs, since only native files can be re-analysed later.
Power-meter and light-source loss testing
We measure end-to-end loss at the working wavelengths, commonly 1310 nm and 1550 nm for single-mode, after referencing the leads. Results are recorded per fibre. Tip: insist on reference method statements, because a poorly referenced test can be off by several tenths of a decibel.
Link certification reports for client sign-off
Each fibre is reported against the design loss budget with a pass or fail, trace attached. The report identifies the link, date, equipment, settings and technician. Tip: agree acceptance limits in writing before testing starts, so that nobody argues about them at handover.
Third-party audit of existing fiber networks
We test every accessible link, rebuild missing records where possible, and issue a findings list with suggested fixes. We do not touch live links without agreement. Tip: schedule audits before road works or expansion starts, so you have a baseline to compare against.
What happens when fiber is accepted without proper testing
A link that carries a signal is not necessarily a good link. Optics have a loss budget, and a link running close to it may work today and fail in summer, after a repair joint or when a faster transceiver is fitted. Without a trace and a power reading, nobody knows how much margin remains. Owners find out when a link flaps and nobody can say whether it always did.
Testing done badly is as unhelpful as no testing. One-direction traces, short launch leads, wrong index settings or dirty connectors give misleading numbers. A short fibre tested without a launch lead hides the first connector entirely. A trace taken with the wrong refractive index gives wrong distances, and a repair crew will dig in the wrong place.
Missing baselines make every later fault harder. When a break occurs, the OTDR reading of the fault distance is only useful if you can match it to the route map and compare it with the original trace. Without both, the crew works from a rough guess, and each restoration costs longer than it should.
What You Gain
A clear pass or fail on every link
Results are compared with the loss budget and a stated limit, so acceptance is a measured decision rather than an opinion.
Faults located within metres
Traces convert a fault into a distance. With a route map and index settings that match the cable, crews can open the right chamber instead of digging trial pits.
A baseline for the future
Traces stored at handover let you compare later readings and see slow degradation, such as a loosening joint or a growing bend loss.
Evidence for contract and warranty
A signed test report supports completion certificates, payment milestones and any claim against the cable or installer if a defect appears.
Independent view of an existing network
A third-party audit tests links built by others, builds a baseline and lists defects, which helps owners decide between repair, upgrade and replacement.
Confidence before higher speed optics
Before upgrading a link to higher-speed optics, a test confirms the existing fibre has enough margin, avoiding failed upgrades and wasted purchases.
How the Work Is Delivered
Testing follows a fixed method so that results are repeatable and comparable between visits.
- 1
Test plan and acceptance limits
We agree the links to be tested, the wavelengths, the method and the acceptance limits derived from the loss budget. This avoids disputes later and fixes the report format in advance.
- 2
Equipment and lead preparation
OTDR, light source and power meter are checked and calibrated. Launch and receive leads of suitable length are prepared, and connector end faces are inspected and cleaned before every connection.
- 3
OTDR tracing in both directions
Each fibre is traced from both ends with correct index and pulse settings. Splices, connectors and events are marked, and bidirectional averaging is used to give true splice loss.
- 4
Power meter loss testing
Leads are referenced and each fibre's end-to-end loss is measured at the working wavelengths. Results are compared with the design budget and with the OTDR total.
- 5
Analysis and fault investigation
Failed or marginal links are analysed. We identify the event responsible, such as a high-loss splice, a tight bend or a damaged connector, and recommend repair or re-termination.
- 6
Re-test after repair
Once a defect is fixed, the link is tested again and the new results replace the old in the final report. Both versions can be kept in the file if you want an audit trail.
- 7
Report and handover
You receive trace files, power meter results, a pass or fail summary and a signed certification report. Results are stored as the baseline for any AMC that follows.
How an OTDR reads a fiber, and where it misleads
An OTDR works on backscatter. The pulse travels down the fibre, and a tiny fraction of the light scatters back continuously. The instrument measures that returning light against time and converts time to distance using the fibre's group index. A straight slope on the trace shows fibre attenuation, with single-mode G.652.D typically near 0.35 dB/km at 1310 nm and about 0.22 dB/km at 1550 nm. A step down shows a splice, a spike shows a connector, and a large drop or the end of the trace shows a break. Pulse width trades resolution against distance: a short pulse sees close events clearly, a long pulse reaches further but blurs neighbours.
OTDRs have limits that a skilled tester knows. They have a dead zone after strong reflections, so launch leads are needed to see the first connector. They can show an apparent gain at a splice between fibres of different backscatter, so true splice loss comes from averaging both directions. And they measure at test wavelengths, so 1550 nm testing is also useful for finding macrobends, which cost more at the longer wavelength. The light source and power meter test remains the reference for total link loss, which is why we report both.
ITU-T G.652.D attenuation values
Published attenuation at 1310 nm and 1550 nm gives the baseline for the loss budget. Test results are compared with it, with allowance for cable, splices and connectors.
TIA-568 and ISO/IEC 11801 channel testing practice
These describe how cabling channels are tested and reported inside buildings. We use them as reference for Tier 1 loss testing and Tier 2 OTDR testing in premises cabling.
Loss budget as acceptance limit
Limits are calculated from the design: fibre loss, splices near 0.1 dB, connectors near 0.3 dB, plus margin. We write the numbers in the test plan.
Launch and receive leads
A rule of practice: use leads long enough to move the first and last connector out of the dead zone, so both are measured and reported.
Bidirectional measurement
Splice loss is reported as the average of two directions, which removes the apparent gain or loss effect caused by differing fibres.
Equipment calibration
Test instruments are kept within their calibration period, and the calibration date is shown on the report so that results can be trusted.
Worked example: acceptance testing of a 4 km, 24-fibre route
Consider a new 4 km route with 24 fibres, one intermediate joint at a chamber and LIU terminations at each end. The design loss budget for the longest fibre is: fibre loss 4 km at 0.35 dB/km, which is 1.4 dB, plus three splices at 0.1 dB, 0.3 dB, plus two connector pairs at 0.3 dB, 0.6 dB, giving 2.3 dB. A margin of 1 dB sets the acceptance limit near 3.3 dB.
The team connects launch and receive leads, takes OTDR traces at 1310 nm and 1550 nm from both ends, and records the results. The power meter test then measures total loss on each fibre at both wavelengths. Twenty-two fibres read between 1.9 and 2.6 dB. Two fibres read near 3.8 dB at 1550 nm, and the traces show a bend loss at one chamber where the slack coil was too tight.
The coil is re-formed at the correct radius, the two fibres are re-tested and now read about 2.4 dB. The report shows all 24 fibres passing, with the earlier results kept as an appendix. The client receives native trace files, the signed certification and a baseline for future comparison.
- Every fibre has a bidirectional trace and a power reading against the budget.
- A marginal bend was found and fixed before handover.
- The client holds native trace files for later comparison.
- Acceptance rests on measured values and agreed limits.
This is an illustrative scenario built from typical site conditions. Actual quantities, timelines and results depend on your site survey.
OTDR Testing & Certification Across Four States
We are based in Nashik and deliver across Maharashtra, Gujarat, Madhya Pradesh and Rajasthan. Each state has its own utilities, approvals and site conditions, and these are the points that matter most for this service.
Maharashtra
Acceptance tests often follow monsoon-season construction, so we check for water in chambers and for bend loss at 1550 nm after settling. Highway and MIDC projects usually need the report in a format a consultant or authority can verify, with native trace files attached to each fibre record.
Gujarat
Long expressway and port-linked routes are tested in sections, with both-direction traces on each. In coastal areas, corrosion at closures and connectors can raise loss over time, so we recommend repeat tests after the first year and compare them with the handover baseline.
Madhya Pradesh
Routes through industrial areas and highway sections are often tested in high summer, when cable temperature changes loss slightly. We note ambient conditions on the report so later tests are compared fairly. Black cotton soil movement can stress buried cable, which a repeat trace after the monsoon can reveal.
Rajasthan
Very long unmanned routes make fault location by trace essential, since a wrong distance means a long drive and a wrong dig. We check index settings carefully and record cable length per drum. Heat and wide day-night swings make a second test at a different time of day useful on aerial spans.
Where This Work Is Most Often Needed
Why Teams Work With Us on This
Testing by the people who understand the build
Our crews lay, splice and test fibre, so they know where losses usually hide and read traces with that experience, not just by software prompts.
Reports that stand up to scrutiny
Reports state equipment, settings, wavelengths, limits and dates, and include native trace files. Consultants and auditors can verify them independently.
Baselines that feed our AMC
Traces taken at handover become the reference for periodic health checks under our AMC, so changes are detected by comparison, not by memory.
Test teams mobilised from Nashik
Technicians travel from our Nashik base to sites in Maharashtra, Gujarat, Madhya Pradesh and Rajasthan. Test dates are fixed against your acceptance milestone, and long routes are tested in sections so results arrive while the contractor is still on site.
Need AMC for an existing system?
We maintain installations done by other vendors too, after a short audit of what is already on site.
Guides and Projects Related to This Service
Frequently Asked Questions
01What is OTDR testing?
OTDR testing sends light pulses down a fibre and measures the reflected light to draw a trace of the link. The trace shows length, attenuation, splices, connectors and breaks. It is the standard method for locating faults and verifying joint quality. It is normally combined with a power meter test for total loss.
02What is the difference between an OTDR and a power meter test?
An OTDR shows events along the fibre and where loss occurs, while a power meter and light source measure total end-to-end loss. The power meter reflects what your equipment will see. The OTDR explains where the loss is. Acceptance testing often requires both, since each covers weaknesses of the other.
03How much does OTDR testing and certification cost?
Pricing usually depends on the number of fibres and links, wavelengths tested, site access and whether bidirectional traces and certification reports are required. Fault finding on a live network is priced differently from acceptance testing. A short scope review gives a firm figure, and we state what is included in the report.
04How long does fiber testing take?
A typical 24-fibre route can be tested in a day or two, once both ends are accessible and connectors are clean and labelled. Large networks take longer, and fault finding can vary, because the cause may take time to isolate. We estimate after reviewing the link list and access arrangements.
05What should an OTDR certification report include?
It should include link identification, date, equipment and calibration, wavelengths, settings, bidirectional traces, power meter results, the acceptance limit and a pass or fail result for each fibre. Native trace files should be supplied with it. A report without these items cannot be verified or compared later.
06Can you test fiber that someone else installed?
Yes, as a third-party audit, with your permission and with live links handled by agreement. We test accessible links, build a baseline, and list defects with suggested fixes. If route records are missing, we reconstruct what we can from the traces, and tell you what could not be verified.

