A label such as "1×32 PLC LGX SC/APC" does not fully define a fiber optic splitter type. It compresses several independent choices: branching technology, port topology, power distribution, package, fiber leads and connector interface. One missing field can turn apparently similar offers into different products.
The six-layer method below translates inconsistent supplier names into one comparison format. Engineers, distributors and sourcing teams can then see which facts are stated, which still need evidence and whether two catalog entries belong in the same equivalence review. Technology selection, optical-loss calculation and model shortlisting remain separate tasks, with links provided later in the guide.
Quick answer: a splitter type has six fields
Record a splitter in this order:
Technology | Topology | Power distribution | Package | Fiber and pigtail | Connector interface
Hypothetical normalized example:
PLC | 1×32 | equal | LGX-style cassette | G.657.A1, 2.0 mm, 1.5 m | SC/APC on input and outputs
Treat this as a normalized comparison record. It is not a universal manufacturer part number. Supplier model codes may arrange the fields differently, omit fields or use different vocabulary.
What to do with the six-field record
After filling the six fields, assign one outcome:
| Outcome | What the record shows | Next action |
|---|---|---|
| Same stated fields | The catalog names appear to describe the same six-layer configuration | Continue to the mechanical, optical and order gates; matching names alone do not prove equivalence |
| Different | At least one required field has a different stated value | Record the difference and do not compare the offers as like-for-like substitutes |
| Unresolved | A required field is missing from the available model information | Ask for the exact datasheet, drawing, port map or interface schedule needed to close the field |
| Conflicting | Model-matched sources disagree | Stop the equivalence review until the supplier identifies the controlling document and revision |
In this guide, BWNFiber uses the worksheet to preserve the original model, expose missing or conflicting fields and specify the evidence needed for the next review. Buyers can use the copy-ready normalization worksheet independently before requesting a price or approving a substitute.
Why "splitter type" is ambiguous in catalogs
Catalogs use the word "type" to answer at least six different questions:
| When a catalog says "type," it may mean | Example answer | What that answer does not tell you |
|---|---|---|
| Optical technology | PLC or FBT | Port count, housing or connector |
| Port topology | 1×8 or 2×16 | Whether power is divided equally |
| Power distribution | Equal or 70:30 | Package or port assignment |
| Mechanical package | Blockless or cassette | Optical limits or connector polish |
| Fiber lead construction | 250 μm bare fiber or 2.0 mm cable | Connector family or polarity |
| Connector interface | SC/APC or LC/UPC | Housing dimensions or mounting method |
Treating one answer as the complete "type" creates false equivalence. Place every catalog term in its proper layer and mark missing fields as unresolved. Familiarity with another model is not evidence for the missing value.
The six-layer fiber optic splitter classification
| Layer | Typical catalog terms | Question it answers | Evidence to confirm it |
|---|---|---|---|
| 1. Technology | PLC, FBT | How is the optical branching function produced? | Model datasheet or manufacturer declaration |
| 2. Topology | 1×N, 2×N | How many input and output ports are identified? | Port diagram and labels |
| 3. Power distribution | Equal, symmetric, unequal, 70:30 | How is nominal power assigned among outputs? | Ratio table or port map |
| 4. Package | Bare, steel tube, blockless, ABS, cassette, LGX, rack | How is the splitter physically protected and mounted? | Dimensional drawing |
| 5. Fiber and pigtail | Fiber grade, buffer or cable diameter, lead length | What leaves the package before termination? | Construction drawing or configuration schedule |
| 6. Interface | SC, LC, APC, UPC, connectorized, unterminated | How do the input and output fibers connect? | Interface schedule, labels and end-face requirement |
Each layer describes a different property. Keep the fields separate even when a supplier combines several of them in one product title.
Before using the six layers, identify the object
The method applies directly to a passive, non-wavelength-selective branching device and its physical presentation. IEC 60875-1:2024 addresses the generic requirements for this device class. First add a scope flag so a housing or composite assembly is not confused with the splitter inside it:
| Scope flag | What the catalog item is | How to record it |
|---|---|---|
| Standalone branching device | The item performs optical power branching | Apply all six layers to the item |
| Composite assembly | The item combines a splitter with WDM, monitoring, patching or another function | Record the added function, then classify the embedded splitter separately |
| Host equipment | A panel, closure, box or frame that may contain a splitter | Create separate records for the host and the installed splitter |
For example, record a "WDM-integrated splitter" as a composite assembly with branching and wavelength-selective functions. Within this framework, WDM belongs neither to the PLC/FBT technology field nor to the package field.
Network and host labels such as PON, ODN, FTTH, ODF or data-center panel describe deployment context. They do not replace any of the six type fields.
Layer 1: technology, PLC or FBT
PLC means planar lightwave circuit. FBT means fused biconical taper. Both identify the branching technology rather than the package shape.
A technology label does not determine installation fit. The same stated technology can appear in more than one package family.
If the task is to decide which technology fits a network, use the dedicated PLC vs FBT splitter comparison. On this page, PLC and FBT are classification labels only.
Layer 2: topology, 1×N and 2×N
Topology identifies the stated input and output arrangement:
- 1×N indicates one identified input and N outputs.
- 2×N indicates two identified inputs and N outputs.
The multiplication sign describes ports. It says nothing about power percentage or package size. A 1×32 unit may use several package formats, while a 2×8 designation alone provides no automatic protection function.
For 2×N products, the second input should not be interpreted as automatic protection switching. The passive component has no active failover logic. The network design and external equipment determine how the two inputs are used.
Layer 3: power distribution, equal or unequal
An equal splitter is intended to divide nominal power uniformly among its stated outputs. An unequal splitter assigns different nominal proportions to different paths.
Unequal notation needs more than two percentages. A label such as "70:30" remains incomplete unless it also shows:
- which output receives each nominal share;
- the direction of the input-to-output path;
- the port numbering used on the drawing;
- whether the value is a nominal coupling ratio or an acceptance limit.
Do not infer the port map from the sequence of percentages in a short catalog title.
Layer 4: package, physical protection and mounting
Package terminology varies more across supplier catalogs than the other five layers. Common labels include bare fiber, steel tube, mini, blockless, micro module, ABS box, cassette, plug-in, LGX and rack-mounted. Normalize each term to a broad family while retaining the supplier's wording and drawing reference:
| Supplier term seen in catalogs | Normalized package family | What the term may indicate | What still requires a drawing |
|---|---|---|---|
| Bare fiber, bare type | Minimal-protection component | Small component intended for integration | Body construction, fiber protection, dimensions and handling limits |
| Steel tube, mini steel tube | Tubular compact package | Protected optical component in a narrow body | Tube dimensions, lead construction and cable exits |
| Blockless, micro, mini module | Compact rectangular module | Integration into a tray, closure or box | Exact body size, bend clearance and mounting method |
| ABS box, ABS module | Boxed module | More physical protection and managed pigtails | Box dimensions, cable diameter, exits and fixing method |
| Cassette, plug-in module | Removable or mounted module | Front-access or modular installation | Form factor, retention method, adapter layout and host compatibility |
| LGX, LGX-style | LGX-related cassette family | Intended use with a compatible shelf or enclosure | Vendor-specific dimensions, mounting points and port orientation |
| Rack-mounted, panel, tray | Rack or frame assembly | Interfaces presented in an installable assembly | Rack width and height, access direction, adapter map and internal routing |
These catalog terms help locate a product family; they do not prove mechanical interchangeability. Physical compatibility depends on exact dimensions, retention details, adapter layout and cable exits.
Layer 5: fiber and pigtail construction
The fiber leaving the splitter package is a separate configuration layer. Relevant terms may identify:
- fiber mode and exact grade;
- coating, buffer or cable construction;
- outside diameter;
- pigtail length;
- color identification;
- jacket or buffer material where specified;
- documented bend, tensile or crush limits when the lead is cableized and those limits are part of the offered configuration.
Record the grade only when a model-matched source states it. G.652.D and G.657.A1/A2 are single-mode fiber designations; OM3, OM4 and OM5 are multimode designations. They belong in the fiber-and-pigtail layer, not in the PLC/FBT or package layer. A connector color, an FTTH label or a data-center application tag does not by itself verify the fiber grade.
Cable vocabulary also needs a boundary. Tight-buffered construction can belong in this layer when it describes the actual pigtail. Broader labels such as loose-tube, armored, ADSS, drop cable or duct cable should not be imported into the splitter record unless the exact supplied assembly includes that construction. For a composite assembly, record the host or cable assembly separately from the embedded splitter.
"Bare splitter" and "unterminated splitter" describe different properties. Bare usually refers to the package or fiber-protection format. Unterminated means connectors are not installed. A compact module may have unterminated pigtails, while a similar package may be connectorized.
Layer 6: connector and end-face interface
The interface layer should identify both connector family and polish, such as SC/APC, SC/UPC, LC/APC or LC/UPC. It should also state whether the designation applies to the input, outputs or both.
"SC" without APC or UPC is incomplete wherever end-face polish matters. "APC" without a connector family is also incomplete. Do not infer the ordered interface from a catalog photo.
For help choosing an interface rather than merely decoding its name, use the fiber splitter selection guide.
How to decode and normalize a fiber splitter catalog name
Consider this hypothetical title:
PLC Splitter 1×32 LGX SC/APC, G.657.A1, 2.0 mm, 1.5 m
Separate it into the six layers:
| Layer | Decoded value | Status |
|---|---|---|
| Technology | PLC | Stated |
| Topology | 1×32 | Stated |
| Power distribution | Not stated | Must not be assumed from the title |
| Package | LGX | Broad family stated; dimensions and mounting still unconfirmed |
| Fiber and pigtail | G.657.A1, 2.0 mm, 1.5 m | Stated, but input/output construction should be checked |
| Interface | SC/APC | Stated, but port assignment should be checked |
The title is detailed enough to locate a product family. It is still insufficient for approval of the delivered configuration because power distribution, exact mechanical fit and port-level interface assignment remain open.
Use four evidence states instead of guessing
Every normalized field should carry one of four states:
| Evidence state | Meaning | Required action |
|---|---|---|
| Stated | The value appears in the catalog title or page | Record the source, but do not treat it as independently confirmed |
| Verified | The same value is confirmed on a model-matched datasheet, drawing or written configuration | Record the document name and revision |
| Unresolved | The supplier has not provided the value | Keep the field open and ask a specific question |
| Conflicting | Model-matched sources show different values | Stop the equivalence decision until the supplier identifies the controlling document |
"Verified" describes consistency among model-matched documents. It does not mean that BWNFiber independently tested the product. This distinction matters when a sourcing team compares third-party offers.
Four steps to normalize any splitter name
- Preserve the original identifier. Copy the supplier name, model code, source URL or document title, and revision without translation.
- Separate the terms into layers. Place each stated term under technology, topology, power distribution, package, fiber/pigtail or interface.
- Mark gaps and conflicts. Use unresolved or conflicting instead of inferring a familiar value from another model.
- Attach controlling evidence. Link each verified field to the exact drawing, datasheet or written configuration used to confirm it.
The completed worksheet preserves the original part number while adding a traceable comparison record.
Copy-ready normalization worksheet
Use one row per candidate. Preserve the supplier's original term before adding a normalized value.
| Original model and source | Technology | Topology | Power map | Package: original / normalized | Fiber and pigtail | Interface and port assignment | Evidence state | Source revision |
|---|---|---|---|---|---|---|---|---|
| [Enter exact identifier] | [Value] | [Value] | [Value or unresolved] | [Supplier term] / [broad family] | [Grade, construction, diameter, length] | [Input and output details] | [Stated / verified / unresolved / conflicting] | [Document and revision] |
The worksheet is shorter than a purchase specification because it serves an earlier decision. Use it to decide whether catalog descriptions can enter the same comparison set before engineering selection or commercial shortlisting.
For documents covering a published BWNFiber configuration, locate the exact model in the fiber optic splitter product directory. Then request its current datasheet, configuration drawing and available test-record format. A generic category sheet cannot replace a model-matched record.
Worked comparison: similar names, different evidence
The following two offers are hypothetical and do not represent BWNFiber product specifications:
- Offer A: "PLC Splitter 1×8 Mini SC/APC"
- Offer B: "1×8 PLC Steel Tube 0.9 mm SC/APC"
| Layer | Offer A | Offer B | Comparison result |
|---|---|---|---|
| Technology | PLC, stated | PLC, stated | Same stated value |
| Topology | 1×8, stated | 1×8, stated | Same stated value |
| Power distribution | Unresolved | Unresolved | Cannot compare |
| Package | "Mini," broad form unresolved | Steel tube, tubular family stated | Not proven mechanically equivalent |
| Fiber and pigtail | Unresolved | 0.9 mm stated; grade and length unresolved | Different evidence depth |
| Interface | SC/APC stated; port assignment unresolved | SC/APC stated; port assignment unresolved | Short labels match; assignment remains open |
The two names are candidates for further review, not substitutes. A buyer still needs the model-matched drawings and configuration documents before deciding whether the same host, routing plan and interface schedule can be used.
Four gates for deciding whether two offers are equivalent
Matching names answer only the first part of an equivalence decision:
| Gate | Question | Evidence needed |
|---|---|---|
| Classification equivalence | Do the six normalized fields match? | Completed worksheet with gaps and conflicts exposed |
| Mechanical equivalence | Will the body, mounting, lead exits and adapters fit the same host? | Model-matched dimensional drawings |
| Optical equivalence | Do the documented limits and acceptance conditions match the project requirement? | Model-matched datasheets and agreed test or acceptance documents |
| Order equivalence | Is the exact deliverable controlled for purchase? | Approved written specification tied to model and revision |
Passing one gate does not prove the next. A catalog label supports discovery; a normalized record supports comparison; model-matched documents support technical verification; an approved written specification controls the order.
Challenge high-risk claims before treating them as type evidence
Some catalog phrases sound complete but still collapse several classification layers or imply evidence that the phrase itself does not provide. Use the following matrix before moving a candidate from catalog discovery into technical comparison:
| Catalog or supplier claim | What the claim may be trying to say | Minimum model-matched evidence | Stop condition |
|---|---|---|---|
| "LGX-compatible" | The cassette is intended for an LGX-related host | Dimensional drawing, retention or mounting detail, adapter map, port orientation and identified host | The host is unnamed, or the drawing does not establish fit |
| "Outdoor splitter" | The offered assembly is intended for an outdoor installation | Separate records for the splitter and host, plus model-matched enclosure, cable-entry and environmental requirements | A product label is used instead of evidence for the complete installed assembly |
| "2×N redundancy" | Two inputs are available for a protection or alternate-path design | Port diagram plus the external switching, control and protection architecture | No external failover behavior is defined, but automatic redundancy is implied |
| "G.657.A2," "OM4" or another fiber grade | A stated fiber grade is used in the offered leads or assembly | Construction document tied to the exact model and input/output configuration | The grade is inferred from color, application, photograph or a different variant |
| "SC/APC" or another interface label | A connector family and polish are offered | Interface schedule showing input/output assignment, adapter or mating requirements and port labels | Connector family, polish or port assignment remains ambiguous |
| "IEC tested" or "compliant with international standards" | A test method or requirement is claimed to apply | Exact standard and edition, parameter, method, wavelength, acceptance limit, report identity, model and revision | The claim cannot be connected to the offered model and a defined acceptance requirement |
| "Equivalent replacement for model X" | The candidate is proposed as a substitute | Completed six-layer record and evidence for all four equivalence gates | Any required field is conflicting or a downstream gate is supported only by a similar name |
A claim can advance only after it is assigned to the correct layer and tied to the offered model and revision. Any unresolved conflict that affects the project requirement stops the comparison. Use this matrix only to screen catalog evidence. Supplier qualification, product selection and commercial approval follow separate controls.
If a disputed term prevents two offers from entering the same comparison set, send BWNFiber the exact model names, source URLs and documents already available. A terminology review can identify stated, unresolved and conflicting fields. It cannot certify a third-party product or approve the project design.
Testing evidence does not change the classification
Optical acceptance is a separate decision from type-name decoding. When insertion loss, attenuation or return loss is part of an equivalence review, record the parameter, test method, wavelength, port direction, acceptance limit and controlling document revision. IEC 61300-3-4:2023 describes attenuation-measurement methods for optical components, while IEC 61300-3-6:2008 describes return-loss measurement procedures. ITU-T G.671 identifies transmission characteristics used for optical branching components.
An OTDR trace can support installed-link troubleshooting, but it does not by itself establish that a splitter passed component-level attenuation or return-loss acceptance. Confirm the agreed component test method and model-matched report separately. Use the fiber splitter loss guide for link-budget work rather than adding loss assumptions to the classification record.
Resolve conflicting documents before comparing offers
If a catalog title, photo, datasheet and drawing disagree:
- Match each document to the exact manufacturer model and revision.
- Mark the disputed field as conflicting, not merely unresolved.
- Ask the supplier to identify the controlling document in writing.
- Update the worksheet only after the conflict is closed.
Do not choose the value that appears most often. Reseller pages may repeat the same upstream source error, and a catalog photo may be shared across variants.
Copy-ready supplier clarification request
Use the following request when an unresolved or conflicting field prevents a fair comparison:
Subject: Model and document clarification for [manufacturer model]
Please confirm the exact manufacturer model and revision offered. Attach the current datasheet and dimensional or configuration drawing for that model. Confirm the technology, topology, power distribution, package, fiber and pigtail construction, and input/output connector assignment. Mark any unavailable field as not stated. If the catalog page, datasheet and drawing disagree, identify the controlling document and revision in writing. Please carry the confirmed configuration into the quotation or order specification.
The request produces evidence that can be entered in the normalization worksheet. It does not ask a supplier to declare two models equivalent without mechanical, optical and order evidence.
Where splitter naming gaps surface in project handoffs
These are representative review scenarios. BWNFiber is not presenting them as customer cases. Each one shows where an incomplete type name can create a document or installation mismatch:
| Project handoff | Naming gap | Evidence to close the gap |
|---|---|---|
| FTTH closure or terminal-box design | "Mini," "bare" and "blockless" are treated as interchangeable | Host drawing, splitter dimensions, pigtail construction, bend clearance and port map |
| Rack, ODF or data-center panel integration | "LGX" is treated as a universal mechanical interface | Cassette dimensions, retention method, adapter map, port orientation and access direction |
| Outdoor cabinet or closure assembly | An "outdoor splitter" label is assumed to describe both the passive component and its enclosure protection | Separate host and splitter records; confirm the exact enclosure, cable-entry and environmental requirements on model-matched documents |
| Incoming inspection and acceptance | The carton or unit label matches the purchase text, but the drawing revision or agreed test evidence does not | Approved order specification, received model and revision, port labels, drawing and contract-required test record |
| Maintenance replacement | A legacy short name is copied without the original model, revision or as-built record | As-built BOM, approved drawing, port identification and written approval for any substitute |
Country or region names are not technical specifications. If a project has regional standards, environmental conditions, labeling language or document-format requirements, record them in the project specification rather than inventing a seventh splitter-type layer.
Five catalog-naming mistakes to avoid
| Mistake | Why it fails | Better record |
|---|---|---|
| Using "blockless" as the complete type | It leaves technology, topology, power map, pigtails and interfaces open | Record blockless only in the package field |
| Treating every "mini" product as the same size | "Mini" does not establish a universal dimensional envelope | Retain "mini," normalize the broad family and attach the drawing |
| Reading 2×N as built-in redundancy | Topology identifies ports, not active switching behavior | Record the two inputs and leave protection behavior to the network design |
| Assuming percentage order defines the port map | A ratio pair does not identify output assignment or acceptance meaning | Attach the ratio table and port diagram |
| Translating a part number without preserving it | The internal label can become detached from supplier evidence | Keep the original model, source and revision beside the normalized record |
Use the right BWNFiber page for the next task
| Your task | Page that owns that task |
|---|---|
| Decode a splitter name and normalize supplier terminology | This fiber optic splitter types guide |
| Compare PLC and FBT as technologies | PLC vs FBT Splitter |
| Choose technology, ratio, architecture, package or connector | Fiber Splitter Selection Guide |
| Calculate splitter loss or build a link budget | Fiber Optic Splitter Loss Chart |
| Browse published product families and prepare an RFQ | Fiber Optic Splitter Products and Configurations |
Frequently asked questions about splitter type names
Is an LGX splitter a different optical technology?
No. LGX is a package or form-factor label. The optical technology may be PLC or another stated technology and must be confirmed separately.
Does 1×32 identify the package?
No. It identifies one stated input and 32 outputs. A 1×32 splitter can be offered in several physical package formats.
Are steel-tube and blockless splitters always the same?
No. Suppliers may use overlapping "mini" terminology, but a tubular package and a rectangular blockless module should not be treated as identical without drawings.
Does "LGX" guarantee cross-vendor compatibility?
No. Confirm dimensions, mounting or retention features, adapter layout, cable exits and port orientation for the exact host equipment.
What should I send a supplier to confirm whether two models are equivalent?
Send both original model identifiers, source links, the completed six-layer worksheet and the documents already available. Ask the supplier to return model-matched datasheets and drawings, identify unresolved fields and state which revision controls the offered configuration.
How should an unequal splitter ratio be written?
Record the nominal ratio together with input direction, output assignment, port numbers and the source drawing. A percentage pair by itself is ambiguous.
Why can two 1×32 PLC splitters be non-equivalent?
They can differ in power distribution, package, fiber grade, pigtail construction, connector assignment, dimensions and other model-specific requirements even when the short titles look similar.
Is the six-layer format a manufacturer part number?
No. It is a neutral comparison format. Keep the original manufacturer model code and revision with every normalized record.
When should a drawing override a catalog title?
Never assume an override silently. First verify that both documents belong to the same model and revision, then obtain written clarification identifying the controlling configuration.
What should be marked when a catalog omits a field?
Use "not stated" or "unresolved." An explicit gap is safer than an inferred value and gives the supplier a precise question to answer.
Can a catalog photo verify the connector and package?
No. A photo can support visual orientation, but it may be reused across variants or omit scale and port details. Use the model-matched interface schedule and dimensional drawing for verification.
Which guide should I read after decoding the name?
Use the technology comparison for PLC versus FBT, the selection guide for design choices, the loss chart for optical-budget work, or the product directory for model shortlisting and RFQ preparation.
BWNFiber's role in turning a catalog name into a controlled requirement
BWNFiber can turn two or three catalog descriptions into one traceable six-layer record before product selection or an RFQ. The resulting comparison preserves original identifiers, exposes missing or conflicting fields and identifies the model-matched documents still needed. It does not replace engineering selection or supplier qualification.
BWNFiber follows a simple review rule: preserve the supplier name, expose missing fields and let model-matched evidence control the next decision.
What to send for a terminology review
- original manufacturer or supplier model names;
- source URLs and document titles;
- available datasheets, drawings or configuration schedules;
- the fields or claims that appear inconsistent;
- the host equipment or interface that makes the difference material.
The review can return a six-layer comparison, a list of unresolved or conflicting fields and specific clarification questions for each supplier. Independent laboratory verification, product certification, architecture approval and equivalence guarantees are outside its scope.
Request a splitter terminology review
If you are ready for selection, samples or a quotation
- For technology, topology, package or interface selection, continue to the fiber splitter selection guide.
- For a published BWNFiber configuration, request the current model datasheet, drawing and available test-record format through the splitter product directory.
- If the configuration is already approved and you need a sample, OEM identification or volume quotation, send the exact configuration, quantity, destination, target schedule and required document pack with the request.
Prepare a model review, sample or project quote
Availability, sample scope, OEM scope, optical acceptance limits, compliance evidence, price, MOQ and lead time remain model- and order-specific and require separate written confirmation.
How BWNFiber prepared this guide
BWNFiber prepared this vendor-neutral terminology guide by comparing fields used in splitter catalog names and checking the device scope and measurement vocabulary against the standards listed below. The page makes no claim of a customer deployment, site inspection, laboratory comparison, model-level performance result, splitter-specific certification or regional delivery record. Worked examples and handoff scenarios are hypothetical or representative. Confirm every product value on model-matched manufacturer documentation.
Technical scope and references
- IEC 60875-1:2024 covers generic requirements for passive, non-wavelength-selective fiber optic branching devices.
- ITU-T G.671 (05/2025) covers transmission characteristics of optical components and subsystems, including optical branching components.
- IEC 61300-3-4:2023 covers attenuation-measurement methods for optical components.
- IEC 61300-3-6:2008 covers return-loss measurement procedures for a fiber optic device under test.
- ITU-T G.652 (08/2024) describes characteristics of a single-mode optical fiber and cable.
- ITU-T G.657 (08/2024) describes characteristics of bending-loss-insensitive single-mode optical fiber and cable.
These references define device scope, fiber characteristics or measurement procedures; citing them does not prove that a particular product complies. This article is a terminology and classification guide. Manufacturer drawings, model-specific datasheets, agreed test evidence and the approved written configuration control the product supplied.
