Clarifications and working definitions

Before a scenario moves into field work, we fix a few terms so that councils, cooperatives, and operators read the same document the same way. These notes are not legal advice; they exist to remove ambiguity from the technical record.

Scenario versus commitment

A use case on this page describes a typical situation and the technical questions we help answer. It is not a scope of work, a schedule, or an approval. Any engagement starts from a signed preliminary evaluation with its own assumptions.

Node and edge node

We use "node" for any aggregation point with active equipment, and "edge node" for a small facility placed close to end demand. Cabinet-only installations, huts, and containerized rooms are treated as separate categories in the capacity model.

Phased deployment

A phase is a segment of the ring that can be built, tested, and put into service on its own. Phases are ordered by demand and by permit readiness, not by distance on the map. A later phase may be reordered if a servitude or a substation connection is delayed.

Technical dossier

The dossier is the document set submitted to a council or committee: demand context, network design, civil works permits, and a phased schedule. It states what has been verified in the field and what remains an assumption to be confirmed.

Land access and servitudes

Access to private land, municipal right-of-way, or cooperative easements is handled by the client's legal team. We document the tenure status of each site and flag where a route depends on an agreement that is not yet in place.

Capacity figures

Capacity numbers in our models are projections built from current subscribers, five-year growth, and peak traffic per segment. They are planning inputs, not performance guarantees. Actual throughput depends on equipment configuration and operating conditions.

If a term in your project documents carries a different meaning, tell us at the start of the evaluation and we will align the glossary before any field survey is scheduled.

Bring us the scenario you are actually stuck on

Whether it is a municipal council asking where the first node should sit, a cooperative weighing which fiber segments to build now, or an operator comparing two edge sites, the useful starting point is the same: a short written evaluation. We review your constraints, flag what is still unconfirmed, and outline the next practical step.

Send the site location, current network reach, and the approval body you answer to. That is enough for a first pass.

Request a preliminary evaluation

Prefer to read how we work first? Start with our approach, or see the full overview of the firm.

What we actually do when a municipality or cooperative calls

Most projects stall in the same place: nobody has translated a coverage gap into a site list, a node count, and a permit sequence. That translation is the work. Below are the tasks that come up again and again across municipal extensions, cooperative upgrades, and operator edge plans.

Each one produces a document a council, a board, or a technical committee can read and question. Nothing here is a sales deck.

If your situation is closer to a phased rollout than a single build, the phased approach explains how we sequence the work.

Field survey and site screening

Coordinates, land tenure, power availability, and vehicle access for every candidate plot. We flag the ones that will fail at the substation before anyone pays for topographic work.

Capacity modeling and node sizing

Current subscribers, five-year projection, peak traffic per segment. That gives you active fiber counts, where to leave empty ducts, and which spans can wait for a later phase.

Civil works permits and easements

Trenching, poles, and rights of way are where schedules slip. We map the permit sequence against the construction calendar so approvals do not arrive after crews are already mobilized.

Technical dossiers for committees

Four blocks: demand context, network design, permits and servitudes, and a phased schedule. Each block carries verifiable annexes and a note on what still needs confirmation.

Equipment specifications

Rack layouts, power draw, cooling assumptions, and interface standards written so procurement can issue a tender without guessing what the design intended.

Commissioning the first service ring

Acceptance tests, splice records, and handover documentation. The ring goes live with a baseline the operations team can actually maintain.

Not sure which of these applies to your project yet? Start with a preliminary evaluation request and we will tell you what is missing.

Cookie settingsWe use cookies to keep the site reliable, remember basic choices, and understand which pages are useful. You can accept, reject, or review the settings before continuing.