The landing is a transition, not a destination
A subsea cable landing creates a new international route, but the capacity becomes usable only after the landing infrastructure connects to terrestrial transmission, metro networks, carrier facilities and data centers. The subsea system and the field-deployable terrestrial network therefore form one service path while retaining different cable constructions, installation methods and operational responsibilities.
Planning should begin with the complete chain rather than a single cable segment. Identify each physical transition, confirm who owns and maintains it, then align fiber count, splice strategy, patching, route diversity, testing and records across those boundaries.
Beach manhole and shore-end transition
Near the coastline, the protected shore end reaches a beach manhole or equivalent transition structure. A project-specific joint connects the submarine segment to terrestrial infrastructure while preserving mechanical protection, water blocking, bend control and access for future maintenance.
Nuvem installation documentation for Portugal identifies the existing EllaLink beach manhole at Praia do Areão in Sines and a direct connection to the terrestrial section. It illustrates one real landing arrangement; the applicable manhole, joint design, route boundary and access method still need to be confirmed from the drawings and responsibilities of each project.
Cable landing station functions
The cable landing station houses or interfaces with transmission, power-feed, monitoring and network equipment. For passive infrastructure, the design must define terrestrial cable entry, fiber allocation, ODF layout, patching policy, secure access, restoration paths and the demarcation between the system owner and terrestrial carrier.
The handoff schedule should identify every fiber pair and port, connector type, splice tray, label convention and approved test reference. This prevents the physical build from reaching the station before the ownership and acceptance rules are ready.
Terrestrial backhaul and metro distribution
The route from the landing environment may pass through duct, buried, road-crossing or shared utility sections before reaching a metro ring or long-haul node. Each section can justify a different construction. A compact all-dielectric duct cable may suit one segment, while another needs steel-tape armor or greater water and crush resistance.
Use the route survey to turn these conditions into a segment schedule. Record pathway type, chamber spacing, available duct, pulling direction, bend constraints, water exposure, shared-corridor risks and access limitations. Drum length and joint planning can then follow the surveyed route and safe installation limits.
Interconnection and data center handoff
At the data center, the design normally transitions from outside plant into an entrance room, ODF or splice enclosure. The link then continues to a meet-me room, carrier rack or cross-connect environment. The specification must coordinate OS2 fiber, pigtails, adapters, LC or MPO/MTP assemblies, polarity, labeling and loss budget.
Confirm the facility entrance rules before selecting the indoor segment. Fire-performance requirements, pathway availability, permitted enclosure types and the location of the carrier demarcation can all affect the final cable and connectivity BOM. The acceptance pack should connect outside-plant test results to the exact fibers and ports presented inside the facility.
The distributor's role
Regional distributors can support both deployment and restoration by holding compatible closures, splice trays, pigtails, adapters and patch cords; arranging local cut lengths or project staging; and maintaining consistent labeling and document packs. The stocking plan should follow the installed cable and connector families so that emergency materials remain mechanically and optically compatible.
For multi-stage routes, distributors can also group materials by work package: shore transition, landing station, terrestrial route, metro handoff and data-center entrance. This makes quantities, labels and delivery windows easier to reconcile with the route schedule.
Project Checklist for Buyers and Distributors
Use this pre-RFQ checklist to turn the route concept into a coordinated passive-infrastructure package. Cable construction, accessory counts, labels and test limits should follow the approved route and handoff documents.
| Stage | Confirm before RFQ | Passive items and records |
|---|---|---|
| Beach manhole and shore end | Structure, joint location, segment boundary, access and environmental protection | Joint closure, splice system, cable entry hardware, route and responsibility drawing |
| Landing station | Cable entry, fiber allocation, ODF layout, demarcation and restoration path | ODF, pigtails, adapters, patch cords, labels, port and fiber schedule |
| Terrestrial backhaul | Duct or buried sections, chamber spacing, pulling limits, water and crush exposure | Segment-specific cable, drums, closures, route survey and joint plan |
| Metro or long-haul handoff | Fiber count, route diversity, node interface, loss budget and ownership boundary | Splice or patch assemblies, labels, link schedule and acceptance limits |
| Data-center entrance | Entrance-room rules, fire performance, enclosure location, connector format and polarity | Indoor cable, ODF or enclosure, LC or MPO/MTP assemblies, port map and test pack |
| Restoration stock | Installed cable families, compatible accessories, storage location and release process | Closures, trays, pigtails, adapters, patch cords and controlled inventory list |
Frequently Asked Questions
What should be confirmed before planning what happens after a subsea cable lands?
Confirm beach manhole and shore-end joint, landing-station demarcation, 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.
