Fibre rollout in a complex site: field notes

A complex fiber deployment in PACA — FTTO, a listed building, an occupied hotel, a campsite in season, a technical room that is too small — is not an operator quote sent by email. It is works coordination, permissions, and an integrator who talks to every party. Host Technology, based in Tourrettes-sur-Loup, runs the technical package on the Côte d'Azur and in Monaco: from the cable route through to the firewall, including voice QoS and 4G backup.

FTTH, FTTO: what the site changes

Shared FTTH is often installed faster and more cheaply; dedicated FTTO brings guaranteed throughput and a short GTR. On a critical site (clinic, hotel, multi-site headquarters), dedicated fiber becomes the foundation. Host helps decide according to real use: IP telephony, VPN, cloud backup, seasonal peaks — not according to the marketing sheet.

The FTTO/FTTH choice also affects IP telephony and backups: a weak or variable uplink degrades the SIP trunk and lengthens backup windows. Host always crosses voice and data use before recommending an offer.

The parties to synchronize

Operator, building manager or owner, electrician, possibly an Architecte des Bâtiments de France, then Host for the LAN. One shared calendar. Connection lead times are counted in weeks, sometimes more. Without a conductor, everyone waits for someone else and the go-live date slips.

A kickoff meeting report with target dates and responsibilities avoids three weeks of “we’re waiting for the operator’s email.” Host Technology keeps that dashboard until go-live.

A technical visit before any throughput promise

Cable route, a saturated duct, no technical room, fiber already full in the street cabinet, ONT-to-rack distance, constraints of an open hotel: the site is visited before anything is promised. In Monaco and in Nice’s older fabric, route surprises are frequent. Host Technology documents blocking points from the first visit.

Photograph the route and the room: that evidence speeds exchanges with the operator and the building manager. It also serves managed IT for future interventions.

Works on an occupied site

Hotel, clinic, offices in operation: work windows, client areas to protect, noise, access to roof spaces. A fiber deployment cannot ignore operations. Work is planned outside peaks, passages are secured, and the technical room is validated (air conditioning, UPS, rack space).

Include client reception, emergency exits, and noise-sensitive areas (rooms, treatment rooms) in the schedule. A local integrator knows these constraints better than a generic national quote.

After the fiber: the real business network

Firewall, VLAN, voice QoS, Wi-Fi, 4G/5G backup, monitoring. Fiber alone is not a network. Many projects fail because the operator delivers the link and nobody takes over the LAN. Host follows connection with integration: telephony, data, remote backup on the new throughput.

Voice QoS and the VLAN are ideally configured the day the fiber is delivered, not “later.” Host sequences the work so the business moves onto the new link quickly.

Fiber deployment checklist (complex site)

1. Field visit: cable route, technical room, building constraints.
2. FTTH vs FTTO choice according to criticality, GTR, and budget.
3. Shared calendar: operator / building manager / electrician / integrator.
4. Rack preparation: switch, firewall, UPS, patching.
5. 4G/5G backup plan during and after the works.
6. Throughput, latency, and voice QoS tests before the business cutover.
7. IP telephony / VPN / backup go-live on the new link.
8. Documentation and incident contacts for the operator and Host.

Each checklist item has a named owner (operator, building manager, Host, client). Without an owner, tasks slip. It is site discipline applied to IT.

GTR, SLA, and the responsibility boundary

A 4-hour GTR covers the operator link, not your failed switch or a bad firewall config. Host clarifies the boundary, centralizes tickets, and avoids the “not my side” ping-pong. For a PACA SME, a single point of contact is often worth more than theoretical throughput.

Require incident numbers and business hotline hours, not only the consumer customer portal. Host records them in monitoring so a ticket can be opened faster.

Multi-site and growth

Two branches, a warehouse, a headquarters: each site can have its own operator. The integrator unifies the layer above (VPN, SD-WAN, consistent voice QoS). Host Technology sets the Côte d'Azur / Monaco multi-site design so the fiber at each address serves the same network policy.

A clear multi-site design avoids cascaded NAT and overlapping IP addressing between branches. Host Technology standardizes the PACA addressing plan from the first site.

Managed IT after delivery

Link monitoring, alerts, follow-up of operator tickets, QoS changes as IP telephony expands. The fiber deployment is finished only when day-to-day operations are stable and documented.

The 30-day service review (real throughput, tickets, QoS) closes the deployment. If gaps appear, they are handled before the works warranty period ends.

• Regular measurement of availability, latency, packet loss, and utilization on the primary link and the backup.
• Retention of circuit references, operator contacts, service commitments, and incident-opening procedures.
• Backup of firewall and network-equipment configurations after go-live.
• Review of real usage so QoS, VPN capacity, and remote-backup windows can be adapted.

In practical terms, every PACA site has its own constraints (building, seasonality, multi-site setups across Monaco and Nice): Host Technology adapts the action plan rather than copying a fixed national template, with a single point of contact for the network, telephony, backup, and managed IT.

The end-of-works file brings together route photographs, the patching plan, acceptance results, responsibilities, and warranty dates. It stops a future intervention from starting with a new investigation. For an SME that rents its premises, it also makes exchanges with the owner or the building manager easier. Host Technology hands over usable documentation and updates the items that change during settling-in.

• Check that physical labeling matches the ports on the diagram and the equipment actually connected.
• Keep a throughput and quality test taken before and after security rules are activated.
• Sign off acceptance while clearly stating reservations, their owner, and the target date to clear them.
• Test opening an operator incident and the 4G or 5G failover before declaring the project finished.

This discipline is particularly useful in complex buildings in Nice, Cannes, and Monaco, where access to ducts or shared rooms requires authorizations. It is also useful in Tourrettes-sur-Loup and the hinterland, where distances and operator options can require a hybrid scenario. The integrator connects site constraints to IT objectives, rather than treating fiber as a simple box delivery.

FAQ

What is the difference between FTTH and FTTO for an SME?

FTTH uses shared infrastructure and generally offers a lower cost, with variable guarantees. FTTO is dedicated to the business and can bring guaranteed throughput, better monitoring, and a contractual restoration time. The right choice depends on the cost of an outage, telephony, the number of users, and the backup available. Host Technology compares the real commitments, not only the speeds shown in commercial offers.

Why can a fiber connection take several months?

Delays often come from route studies, authorizations, civil engineering, a blocked duct, or coordination with the building manager. An operator order does not automatically authorize every passage in a building. The technical visit identifies these dependencies and lets requests start early. A shared calendar, photographs, and a named owner reduce the periods when each party is waiting for someone else to act.

Should a second connection be kept after go-live?

Yes when the Internet, telephony, or cloud applications are critical. Backup should ideally use a different technology or path so the same incident does not cut both links. A 4G or 5G link can suit some uses, but its coverage and capacity must be tested. Host Technology configures the failover, limits non-priority flows in degraded mode, and checks regularly that it works.

Who is responsible if the fiber works but the internal network does not?

The operator generally stops at its termination equipment. The firewall, switches, Wi-Fi, VLANs, and applications belong to the client or its integrator. This boundary must be documented before cutover. Host Technology runs an end-to-end diagnosis and opens the ticket with the right party. The company thus avoids unproductive exchanges between the operator, the network maintainer, and the telephony provider.

How do you confirm that a new fiber link is ready for production?

Acceptance checks throughput in both directions, latency, packet loss, addresses, the firewall, VPNs, voice, and critical applications. It also includes a backup test and a check at representative hours. A simple download test is not enough. The integrator records the measurements and reservations, then supports a progressive cutover so it is possible to return temporarily to the old link if something is wrong.

A complex fiber project (FTTO, occupied site, multiple addresses) on the Côte d'Azur or in Monaco? Contact Host Technology for field coordination — visit, operator calendar, LAN, and backup included.