Start with the route, not the cable code
Backhaul projects often request “outdoor armored fiber” before the survey is complete. That shortcut can lead to unnecessary metal, difficult pulling, grounding questions or insufficient protection. The better sequence is to define installation environment, duct condition, pulling length, water exposure, crush and rodent risk, shared utilities, repair access and required fiber count.
Duct cable
Duct cable relies on the conduit system for much of its external protection. It can use metallic or all-dielectric construction depending on the route. Advantages can include lower diameter and weight, easier pulling and better duct utilization. The RFQ should still define tensile strength, crush resistance, water blocking, sheath material, cable diameter, drum length and pulling method.
Direct-buried cable
Direct burial exposes the cable to soil pressure, stones, moisture, excavation and rodents. The construction may therefore require additional armor or layered sheath protection. The buyer should specify trench conditions, burial depth, warning and protection methods, joint chamber design and route marking. “Direct buried” should never be treated as an installation instruction by itself.
Armored cable
Armor is a response to a defined mechanical risk. Corrugated steel tape, steel wire or non-metallic reinforcement serve different purposes and affect diameter, flexibility, weight, grounding and installation. For shared power corridors or environments where metal is undesirable, an all-dielectric design can be more appropriate. For flooded or high-crush ducts, another construction may be justified.
Transition sections
One route may contain all three environments. The design should define where cable types change, where closures are placed, whether mid-span access is required, and how optical and mechanical continuity is maintained. Building-entry fire requirements should be treated separately from outside-plant armor.
Distributor selection matrix
Distributors should stock a narrow set of common duct and armored designs, while keeping configurable project options for fiber count, armor, sheath, drum length and printing. A route questionnaire attached to every quotation is more useful than an oversized product list.
Project Checklist for Buyers and Distributors
Use the following points as a practical pre-RFQ review. The exact cable construction, accessories, counts, labels and test limits should remain project-specific.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Confirm the applicable project condition, owner responsibility, and documentation record before ordering materials.
Frequently Asked Questions
What should be confirmed before planning duct vs direct-buried vs armored fiber cable for iberian terrestrial backhaul?
Confirm duct condition and fill, pulling distance and tension, fiber count, passive connectivity, labeling, and acceptance records. These items should be tied to the actual route and installation environment.
Can one standard fiber cable specification cover every Iberian route?
No. Duct condition, buried sections, shared corridors, data center entrance rules, fire-performance requirements, bend radius, pulling load and documentation expectations can all change the specification.
What information helps ZION support a project quotation?
Share the route segment, installation method, fiber type and count, cable construction, drum length, closure or ODF needs, connector format, testing requirements and required handover documents.
Does this article imply ZION supplied a named Nuvem or Google project?
No. The guidance is written for terrestrial fiber planning around similar infrastructure scenarios. Any named project reference is contextual and should not be read as a supply claim.
