1×4 Singlemode FBT Splitter Module with SC/APC Interfaces

FBT-1×4-SM-2.0-SCAPC

Model reference: FBT-1×4-SM-2.0-SCAPC — model cross-reference requires product-owner confirmation.

Product summary

This proposed model is a connectorized 1-input/4-output FBT splitter assembly in a black rectangular module. The supplied product photos show yellow pigtails and green SC/APC-form connectors. Before quotation or purchase approval, confirm the output ratio, wavelength window, fiber grade, pigtail construction and length, module dimensions, optical limits and test-record scope against the approved model documents.

Buyer summary

Use this page to validate one exact FBT module configuration—not to select between every splitter technology or ratio. Submit the model reference, required power distribution, wavelength plan, host-enclosure space, connector schedule and acceptance limits. BWNFiber should return a model-matched datasheet, drawing and document list for approval before the item is released to a quotation or purchase order.

Confirmed visual configuration

• One visible input pigtail and four visible output pigtails.
• Black rectangular protected module.
• Yellow pigtails, consistent with a singlemode-coded assembly but not proof of the fiber grade.
• Five green SC/APC-form connectors are visible; the final input/output connector schedule must match the approved drawing.
• Four supplied 800×800 WebP views show the same photographed configuration.

Technical specification and approval status

Interface and connector checks

Do not approve the module from the connector color alone. The order record should identify the connector family and APC polish for the input and every output, pigtail length, label convention, adapter compatibility, end-face inspection requirement and optical reference plane. Do not mate APC directly to UPC; use the approved interface plan.

Fiber and configuration checks

The model name proposes a singlemode, 2.0 mm build. Confirm the exact fiber grade and cable/pigtail construction instead of inferring them from the yellow jacket or filename. Also confirm whether the four outputs are equal or assigned different ratios. A 1×4 designation specifies port count, not the power delivered to each output.

Application and compatibility conditions

This module can be shortlisted only where the approved design calls for an FBT 1×4 device and its wavelength, per-path loss, reflection, temperature and mechanical limits fit the system. Compatibility is conditional on:

1. the required input-to-output ratio and port assignment;
2. the system wavelengths and any coexistence plan;
3. the maximum and minimum optical power at every receiver;
4. connector/polish, adapter and cleaning/inspection method;
5. host-enclosure dimensions, cable exits, bend management and strain relief;
6. the project acceptance method and required records.

Do not describe this model as universally GPON-, XGS-PON-, CATV- or equipment-compatible without the approved network and model evidence.

How to select and approve this model

1. Confirm the network designer has specified FBT rather than PLC.
2. Record the required 1×4 output ratio and identify every output port.
3. State the operating wavelength(s) and the maximum allowed loss by path.
4. Confirm fiber grade, pigtail diameter/length, SC/APC interfaces and labels.
5. Check the module drawing against the tray, cabinet or enclosure.
6. Approve the model datasheet, drawing and test-record format.
7. Validate a sample when the project or substitution-control plan requires it.
8. Release the quotation/PO only when the configuration and evidence revisions match.

Difference from related options

Related decision paths: browse the FBT splitter family, review the fiber optic splitter catalog, use the 1×4 splitter configuration guide, follow the splitter selection and RFQ guide, or compare technologies in the PLC vs FBT splitter guide.

Suitable and non-fit conditions

Potential fit: a controlled BOM already calls for a connectorized 1×4 FBT module and engineering can approve its exact ratio, wavelength, path limits and enclosure fit.

Do not release this item when the design only says “1×4 splitter,” when PLC/FBT has not been decided, when the ratio or port map is absent, when the required wavelength is outside the approved model window, when the enclosure fit is unknown, or when model-level acceptance data is required but unavailable.

Testing and quality-control record

The published page should describe only the test scope that BWNFiber can document for this exact model. At minimum, the approval pack should define the test wavelengths, input/output reference planes, per-port insertion-loss limits, uniformity calculation, return-loss/directivity/PDL requirements where applicable, connector end-face inspection, report sampling rate, serial/lot traceability and failed-unit disposition. Current status: TBC — QA source required.

Packaging and procurement information

Packaging method, quantity per pack/carton, labels, MOQ, sample terms, price, stock, lead time, warranty, Incoterm and destination-specific documents are TBC — commercial confirmation required. Keep them out of Product/Offer schema until visible, current and approved.

Required information for an RFQ

Send:

• model/reference and approved equivalent policy;
• system/application and operating wavelength(s);
• 1×4 ratio and output-port map;
• maximum insertion loss per path and other optical acceptance limits;
• fiber grade, pigtail construction, input/output lengths and tolerances;
• SC/APC input/output schedule, adapter interface and label convention;
• available host-enclosure space and routing constraints;
• quantity, sample requirement, destination and requested date;
• required datasheet, drawing, test report, compliance, packing and traceability documents;
• permitted substitutions and approval authority.

Datasheet, drawing and test-document area

• Model datasheet: TBC — approved file required
• Dimensioned drawing: TBC — approved file required
• Test-record sample: TBC — QA-approved file required
• Compliance documentation: TBC — model/revision scope required

Do not display empty or generic download buttons.