Start With the Connection Path, Not a Generic Cable Name
“Pre-terminated drop cable” describes an assembly concept, but it does not by itself tell a supplier where the cable will run or what each end must connect to. An ISP rollout, contractor installation and distribution project can use similar-looking cable lines while requiring different endpoint references, installation routing, length schedules and packing instructions. The RFQ should preserve those distinctions.
Begin by giving each assembly line a simple reference: its route or installation point, Endpoint A and Endpoint B. Then state whether the item is needed as a connectorized assembly, a cable with a specified termination arrangement, or a line that still needs field installation. This avoids treating pre-terminated and field-installable work as the same request.
Specification Fields for Each Assembly Line
Separate Pre-Terminated, Field-Terminated and Bulk Cable Lines
Procurement comparisons become clearer when different delivery forms remain separate. A pre-terminated assembly should show both endpoints and the length schedule. A field-termination line should instead identify the required FTTH fast connector, its cable match and the installation context. Bulk drop cable should retain its own construction, drum or cut-length and quantity fields. Combining these into one “drop cable kit” line makes it difficult to see what must be quoted or checked.
The same principle applies to project accessories. A fiber optic adapter is a connection-point item, while a pigtail, splitter, ODF or terminal item has a different role in the network. They can be sent together in one project package, but each should have a separately reviewable line and quantity.
Common RFQ Errors to Catch Before Sending
- Listing only one connector family without describing what is required at the other end of the assembly.
- Giving a total cable quantity but no length schedule by route, unit or installation point.
- Combining indoor, outdoor and self-supporting applications in one unqualified item.
- Using “pre-terminated” when the project actually expects field-installed connectors or an unspecified termination arrangement.
- Combining cable, connectors and accessories into one kit line with no individual specifications or quantities.
- Leaving out the drawing, endpoint label or BOM revision when the project uses internal model references.
- Omitting packing, marking or destination details where they are part of the procurement requirement.
Build a Connected FTTH BOM Without Losing Line-Item Detail
A connected project request can place the assembly next to the passive items that support the same installation path. Depending on the design, this may include PLC splitter sourcing details, ODF or terminal hardware, pigtails, adapters, field connectors, splice sleeves and clamps. The useful approach is to group the package by project while keeping each item’s interface, role and quantity visible.
For a broader planning sequence, use the FTTH drop cable buying guide to review cable application and related installation items, then use the FTTH network product sourcing page to map the complete access-network BOM. This guide focuses on the assembly line that often gets underspecified between those two steps.
Copyable Pre-Terminated Drop Cable RFQ Checklist
- Project or route reference for every assembly line
- Indoor, outdoor, self-supporting or other installation context
- Fiber count, fiber type, cable construction and jacket requirement
- Endpoint A and Endpoint B locations, plus the required interface or termination reference for each
- Cut length or route-specific length schedule and quantity by line
- Separate fields for pre-terminated assemblies, field-installable connector work and bulk cable
- Related splitter, ODF/terminal, pigtail, adapter, fast-connector and accessory lines where required
- Packing, label, destination, drawing, BOM and revision-control details