On this page
- Quick Answer: What Should Buyers Check First?
- What a Test Report Proves (and What It Doesn't)
- Split Ratio and Why It Changes What You Need to Check
- How to Read PLC Splitter Insertion Loss
- PLC Splitter Loss Chart: Reference Range, Not an Acceptance Standard
- PLC Splitter Loss Calculation: Checking Each Port
- Uniformity: The Number Many Buyers Skip
- Connector and Package Configuration: What the Report Must Name
- Sample PLC Splitter Test Report Breakdown
- Red Flags Before Approving a Bulk PLC Splitter Order
- Buyer Checklist Before Shipment
- Example: Reviewing a 1×32 PLC Splitter Test Report
- FAQ
Quick Answer: What Should Buyers Check First?
Before anything else, confirm the report actually corresponds to your order. Check the product model, split ratio, connector type, test wavelengths, per-port insertion loss, serial number, batch number and test date. These eight fields tell you whether the document is traceable to a specific shipment - or recycled from another job.
The most common buyer mistake is reading only the average insertion loss. A clean average can mask one or two weak ports. Always look at the worst output port value, because in the field that port defines the most marginal signal path your network will carry. A PLC splitter loss summary that shows only an average - with no per-port data - is not sufficient to approve a bulk order.
What a Test Report Proves (and What It Doesn't)
A factory test report demonstrates that the measured units were within specification before leaving the production line. For a fiber optic PLC splitter, that means real insertion loss values at relevant wavelengths, ideally with uniformity, return loss and PDL, all tied to a traceable batch reference.
Every supplier datasheet looks similar; measured batch data does not. A report lets you compare vendors on how tight their port-to-port spread actually is, whether they test at both wavelength windows, and whether their pass/fail limits are consistent with what they quoted. Two PLC optical splitter suppliers can offer the same typical loss on paper yet deliver very different batch-level consistency.
What a test report does not do: it does not certify the finished cable plant. It proves pre-shipment condition only. After deployment you still verify links with an OTDR and optical power meter, and you still inspect connector end-faces on arrival. The report reduces incoming risk; it does not replace field verification.
Test report, datasheet and Telcordia qualification are three different things. The datasheet is the supplier's declared specification - no measured data for your specific units. The factory test report is the measured evidence for that shipment. Reliability standards such as Telcordia GR-1209 and GR-1221 for passive optical components cover product-family qualification and environmental aging tests - not per-shipment batch data. A vendor can hold valid qualification records and still send a marginal batch. Ask for both; treat them as serving different purposes. For parameter definitions, ITU-T G.671 on optical component transmission characteristics is a useful neutral baseline.
Split Ratio and Why It Changes What You Need to Check
The higher the split count, the higher the insertion loss and the wider the potential port-to-port variation. A 1×32 PLC splitter divides input power across 32 outputs, so a report listing only an average hides exactly the information you need most. For most FTTH bulk orders at this split ratio, per-port data is the baseline expected in shipment documentation - a summary average on its own is not sufficient for strict incoming acceptance.
Lower ratios are easier, not exempt. A 1×8 PLC splitter or 1×16 PLC splitter can still deliver a bad port, a mismatched connector or a missing wavelength - the same fields apply, with less effort per port. Buyers planning mixed ODN architectures can cross-check split ratio requirements against an FTTH network design and ODN architecture guide to confirm which ratios belong where in the network.
How to Read PLC Splitter Insertion Loss
PLC splitter insertion loss is the optical power lost between the input and a given output port. In a test report it should appear as a measured value for every output port, not a single device-level summary:
The average tells you how the batch looks on paper. The worst-port insertion loss tells you the real risk, because the network's most marginal subscriber drop sits behind the weakest output. A report with an attractive average but two high-loss ports can still cause field problems on those specific paths. The FOA guidance on splitter and coupler testing supports the need to measure every splitter output and understand port-to-port variation, rather than relying only on a summary figure.
Watch for per-port data that looks too uniform: values that all read identical to two decimal places, loss numbers with no stated wavelength, or a worst port sitting suspiciously close to the pass/fail threshold with no margin. Any of these warrants follow-up before releasing the batch.
PLC Splitter Loss Chart: Reference Range, Not an Acceptance Standard
Use a loss chart as a sanity check - to confirm reported numbers are physically reasonable for the split ratio, not as a substitute for agreed project acceptance criteria.
These values are common reference ranges seen in supplier datasheets. Actual measured values may vary depending on split ratio, connector type, package type, test wavelength, pigtail length and individual supplier specification. Final acceptance must follow the quoted datasheet and agreed project specification - not this chart alone. Use it only as a sanity check before comparing the actual report against those agreed criteria.
The pass/fail limit on the report should also match the maximum stated in the datasheet you were quoted. If the report's threshold is looser, the document is quietly redefining acceptance in the supplier's favor. That discrepancy alone is grounds to pause shipment.
PLC Splitter Loss Calculation: Checking Each Port
PLC splitter loss calculation is straightforward. If the input power is 0 dBm and one output port reads −16.8 dBm, that port's insertion loss is 16.8 dB. The report should let you reproduce this for any port in the table. Reports that sample "a few representative ports" on a high-count device leave the rest unverified - not sufficient for strict shipment approval of high-count devices.
Per-port loss is also the direct input to your link budget. Knowing the worst-port value lets you confirm the splitter fits the planned ODN power budget before installation. Buyers managing a project FTTH loss budget can use the worst-port figure directly in the calculation, rather than the optimistic average.
Uniformity: The Number Many Buyers Skip
Uniformity describes how evenly power is shared across all output ports:
A batch with an acceptable average but poor uniformity can still create uneven subscriber power levels - some drops near the top of the budget, others close to the margin. It is a maintenance problem that typically surfaces only after deployment. If the report contains no per-port data, you cannot calculate uniformity - which is itself a sign the document is incomplete for bulk acceptance.
Connector and Package Configuration: What the Report Must Name
Connector type, return loss and end-face inspection
A PLC splitter with connector ships terminated - typically as an SC/APC PLC splitter or SC/UPC version. A PLC splitter without connector is supplied as bare fiber for field splicing. The report's stated connector type must correspond to your order exactly, including the polishing angle (APC vs UPC) and pigtail length. If the configuration listed contradicts the purchase order, reconcile it before shipment - and verify that any associated fiber optic pigtails or patch cords ordered alongside the splitters are consistent with the same configuration.
Connector polish drives reflection. APC end-faces deliver higher return loss than UPC, so return loss figures only make sense when read alongside the correct connector type. IEC 61300-3-35 defines the method for connector end-face visual inspection, covering contamination, scratches and defects. A factory test report does not replace end-face inspection after arrival; that is a separate step in incoming QC.
Return loss belongs on the report for any connectorized fiber optic PLC splitter. An APC part with weak return loss figures signals a polishing or assembly issue worth flagging before the batch leaves the supplier. PDL (polarization dependent loss) is rarely the first priority for standard FTTH procurement, but a thorough report should include it. If a supplier's document has no return loss, no PDL and no uniformity data at all, treat it as low-completeness rather than simply "passing."
Package type: bare fiber, blockless, ABS, cassette and LGX
Whether the unit is a bare fiber PLC splitter, blockless PLC splitter, ABS PLC splitter, cassette PLC splitter or LGX PLC splitter module, the package type and model code should be named explicitly on the report. A cassette or LGX module is a packaged assembly with defined connector ports; its report should reference the module model and port configuration. A bare fiber product's report covers the raw splitter and pigtails only. Confusing the two creates wrong expectations on connector loss, return loss, dimensions and handling.
For a bulk order, the model, package type, pigtail length and connector configuration on the report should align with the purchase order line by line. A generic "PLC splitter, 1×32" with no package or model code is not traceable enough for incoming acceptance.
Sample PLC Splitter Test Report Breakdown
Use the table below to evaluate each section of a supplier test report systematically.
| Report Section | What Buyers Should Check | Red Flag |
|---|---|---|
| Header information | Product model, split ratio, SN, batch number, test date | Missing batch/SN; generic description with no model code |
| Optical data - insertion loss | Per-port IL at 1310 nm and 1550 nm; 1490 nm where specified for GPON-specific acceptance | Average only; wavelength not stated; fewer ports listed than the split ratio |
| Uniformity | Highest IL minus lowest IL across all output ports | Not stated; cannot be calculated because per-port data is absent |
| Return loss | Required for connectorized products; wavelength-specific | Absent on APC parts; value lower than datasheet minimum |
| PDL | Quality indicator; request for stricter procurement | Completely absent on higher-grade OEM orders |
| Connector configuration | SC/APC, SC/UPC, LC/APC or bare fiber - stated explicitly | Blank field; configuration contradicts the PO |
| Package type | Bare fiber, blockless, ABS box, cassette, LGX module | Generic description not linked to a model number |
| QC approval | Operator name, signature or stamp, pass/fail threshold | No signature; acceptance limit differs from the quoted datasheet |
| Equipment / calibration | Meter model and calibration date | Absent on strict-quality orders - request separately if required |
Red Flags Before Approving a Bulk PLC Splitter Order
No serial number or batch reference. A report without a batch or unit reference cannot be tied to the units in the carton. For bulk shipment approval, that gap in accountability is a serious problem - not a formality.
Average loss only, no per-port values. If the document shows one number and no port-level table, you cannot identify the worst port or calculate uniformity. Request complete per-port data before releasing the order.
Identical values across many ports. Real measurements vary slightly due to measurement noise and genuine port variation. The same insertion loss value repeated across many ports to the same decimal place may indicate copied or placeholder data rather than genuine testing. Hold the batch until the supplier can provide raw measurement data.
Missing or unspecified wavelength. Loss without a stated wavelength is meaningless. Most standard reports cover 1310 nm and 1550 nm. For GPON-specific acceptance, 1490 nm may be requested separately - the required test wavelengths should be agreed with the supplier before shipment.
Report pass/fail limit looser than the datasheet. If the acceptance threshold on the report is higher than the maximum stated on the datasheet you were quoted, the document is approving units the datasheet would reject. Ask for a written explanation before the shipment moves.
QC mini-scenarios
These situations come up regularly in pre-shipment document review and incoming inspection for FTTH components.
Scenario 1 - Missing configuration detail. The PO specifies 1×32 SC/APC cassette PLC splitter. The test report says only "1×32 PLC splitter" with no connector type, no polish angle, no package type. Action: request a corrected report that names the full configuration. Do not release the shipment until the report is reconciled with the PO line.
Scenario 2 - Incomplete port data. A 1×32 PLC splitter test report lists insertion loss for 8 ports only, with a note that they are "representative samples." Action: request complete per-port data for all 32 outputs. A partial sample is not sufficient for bulk acceptance of a high-count device.
Scenario 3 - Mismatched pass/fail threshold. The supplier datasheet you were quoted states a maximum insertion loss of 17.0 dB. The test report's stated pass limit shows 17.5 dB. Action: verify the threshold against the quoted datasheet. If the limits do not match, the report is approving units the datasheet would reject. Hold shipment and request written clarification.
Buyer Checklist Before Shipment
Use this as a pre-shipment acceptance gate. A missing field is a reason to request a corrected document, not to approve and proceed.
| Item | Why It Matters | Buyer Action |
|---|---|---|
| Product model | Ties report to the ordered part | Match to PO line item |
| Split ratio | Confirms correct device | Verify against order |
| Connector type | Drives IL and return loss | Confirm APC / UPC / bare fiber |
| Package type | Affects data and handling | Align with ordered package |
| Fiber type | Confirms G.657 / G.652 grade | Check against project spec |
| Test wavelengths | Loss is wavelength-dependent | Expect 1310/1550 nm as standard; 1490 nm may be requested where GPON-specific acceptance is required |
| Per-port insertion loss | Reveals the worst port | Read every port, not the average |
| Uniformity | Shows port consistency | Calculate highest − lowest |
| Return loss | Indicates connector polish condition | Expected for connectorized products |
| PDL | Higher-grade quality indicator | Request if absent on OEM or strict orders |
| Serial number | Unit-level accountability | Confirm present |
| Batch number | Links report to shipment carton | Confirm present |
| Test date | Shows report is current, not reused | Verify recent |
| QC signature / stamp | Operator accountability | Confirm signed or stamped |
| Pass/fail limit | Defines acceptance threshold | Verify against quoted datasheet |
For a 1×32 PLC splitter order, request all 32 per-port values, confirm the uniformity result is within the agreed limit, and evaluate the worst-port figure individually against the acceptance threshold. Archive the signed report together with batch and serial references as part of your fiber distribution box and NAP box deployment records.
In supplier document reviews and pre-shipment QC communication for FTTH components, the most useful test reports are rarely the ones that show only the lowest average insertion loss. They are the ones that correlate per-port values, wavelength-specific readings, serial number, batch reference, connector configuration and package type with a clearly stated pass/fail threshold - and link all of that to a specific shipment. For OEM order review and incoming inspection, a slightly higher average with full, traceable data is far easier to approve than a flawless-looking average that cites no configuration, no batch reference and no acceptance limit. The document's value lies in the linkage, not the headline number.
Example: Reviewing a 1×32 PLC Splitter Test Report
The following is a simplified, illustrative review - not real customer data.
Step 1 - Match the model to the purchase order. Confirm the model code, package type and connector configuration on the report correspond to the PO exactly. A mismatch here stops the review before it starts.
Step 2 - Verify all 32 output ports are listed. Read each per-port insertion loss value, not the summary line. A 1×32 report that lists only a subset of ports is incomplete for bulk acceptance.
Step 3 - Identify the worst-port value and compare against the agreed maximum. If port values run from 16.45 dB to 16.95 dB, the figure to check is 16.95 dB - not the average. Also confirm the report's stated pass/fail limit corresponds to the datasheet maximum. If the report approves at 17.5 dB but the quoted datasheet states 17.2 dB, resolve the discrepancy before the shipment moves.
Step 4 - Calculate uniformity. 16.95 dB − 16.45 dB = 0.50 dB. Compare against the agreed uniformity specification.
Step 5 - Confirm connector and package consistency. Verify connector polish, pigtail length and package type appear on the report and correspond to the purchase order. Archive the signed document with batch and serial references as part of the project shipment record.
| Check | What You Verify | Illustrative Result | Decision |
|---|---|---|---|
| Model match | Report vs PO | Matches - SC/APC cassette | Proceed |
| Per-port data | 32 values present | All 32 listed | Proceed |
| Worst-port vs agreed limit | Highest IL vs acceptance threshold | 16.95 dB vs 17.2 dB limit | Within limit |
| Report limit vs datasheet | Pass/fail threshold consistency | Both state 17.2 dB max | Consistent |
| Uniformity | Highest − lowest | 0.50 dB - within spec | Proceed |
| Connector / package | Configuration alignment | SC/APC cassette as ordered | Consistent |
| Final call | All checks clear | - | Approve |
If the worst port exceeded the agreed limit, the connector configuration did not align with the PO, per-port data was missing, or the report threshold contradicted the quoted datasheet, the correct call is hold (request a corrected document and written clarification) or reject (return for re-test), not approve.
FAQ
-
Q: Can I approve a batch with only average insertion loss?
A: Not for strict incoming inspection. An average hides the worst port, makes uniformity calculation impossible, and provides no shipment-level traceability. For FTTH bulk orders, complete per-port data should be requested before the order is released.
Q: Should a 1×32 PLC splitter report show all 32 output ports?
A: Yes. A 1×32 report should list insertion loss for all 32 output ports. "Representative samples" from a subset are not sufficient for bulk acceptance of a high-count device - the unmeasured ports remain unverified.
Q: What should I do if the report connector type does not match the PO?
A: Hold the shipment and request a corrected report in writing. A bare fiber PLC splitter report should not be used to approve a connectorized product - connector loss and return loss are absent from the data, making the document unsuitable for that configuration.
Q: Is a batch report sufficient for bulk ordering?
A: A batch-level report can be acceptable for standard catalog products if it includes per-port data, test wavelengths, pass/fail limits and traceable batch references. For high-count or critical orders - 1×32, 1×64 - per-unit reports are a stronger position.
Q: Should every PLC splitter shipment include a test report?
A: For bulk procurement, yes. A supplier test report should accompany each shipment so that optical performance, configuration and traceability can be verified during incoming inspection - not assumed.
Q: What is acceptable insertion loss for a 1×32 PLC splitter?
A: A common reference range is around 16.5–17.2 dB, but actual acceptance should follow your supplier datasheet and agreed project specification. Connector type, package type and pigtail length all affect the final measured value - a generic chart is a starting point, not an acceptance standard.
Q: Why do reports show 1310 nm, 1550 nm and sometimes 1490 nm?
A: Insertion loss varies with wavelength, so reports test at the relevant operating windows. Most standard supplier reports cover 1310 nm and 1550 nm. For GPON-specific acceptance, buyers may request 1490 nm because it is the downstream operating wavelength in GPON systems. The required test wavelengths should be agreed before shipment.
Q: Is a factory test report the same as Telcordia certification?
A: No. A factory test report is measured data for a specific shipment batch. Telcordia GR-1209/GR-1221 qualification covers reliability and environmental testing of a product design family - not per-shipment measured data. Both have value; neither replaces the other.
Q: Should a bare fiber PLC splitter and a connectorized PLC splitter use the same report?
A: No. The two configurations differ in connector loss, return loss and end-face data. Each requires a report reflecting its actual tested configuration. Reusing one for the other is not appropriate for incoming inspection.
Q: Why might factory test data differ from field power meter readings?
A: Several factors contribute: factory and field measurements use different reference conditions; connector mating at installation adds loss; cable bends, splices and distribution hardware introduce further attenuation. The factory test report covers the splitter under controlled conditions - field readings reflect the complete installed link.
