Fiber Network Engineering & Design

Route selection is the design

Every fiber design starts with a line on a map, and many schedule problems begin with a route that was drawn optimistically before constructability was fully understood. The shortest route is frequently the most expensive one: it crosses a railroad, it needs three poles replaced, it runs down a street where the municipality has a moratorium, or it uses a conduit that turns out to be full.

BOGO engineers the route with those constraints in view from the start. Aerial versus underground is decided against what the poles will actually carry and what the make-ready is likely to cost, not against a preference. Where the route crosses shared infrastructure, the attachment and clearance implications are identified during design rather than discovered during permitting.

That is a different exercise from producing a drawing that satisfies an optical budget. Both matter — but a route that is optically clean and physically unbuildable has not solved anything.

Fiber counts, splice planning, and building for the next program

Fiber count is one of the few design decisions that is genuinely difficult to revisit. Placing more fiber than today's program needs costs incremental material. Placing too little costs an entire second construction cycle, with a second round of make-ready and permitting attached to it.

The counts BOGO designs to reflect the operator's stated growth horizon, architecture, resiliency requirements, and future expansion strategy — not just the immediate project scope. If a market is being segmented now and there is an intent to segment again later, the route is engineered so the second pass is a splice job rather than a rebuild. If a business services strategy will want dedicated strands out of the same route, that is accounted for while the route is still on paper.

Splice planning follows from the counts. Where splice points fall determines where enclosures and slack go, how the route is tested at turn-up, and how maintainable it is afterwards. A splice plan that minimizes splice count on paper but puts an enclosure somewhere a technician cannot safely reach has moved the cost rather than removed it. That plan feeds directly into splicing coordination and turn-up.

Where fiber design meets the coax plant

Most of BOGO's fiber work is not greenfield FTTH. It is fiber placed to serve, extend or replace part of an existing hybrid fiber-coax network — new fiber to support node segmentation, fiber deep into a market to shorten cascades, or fiber built ahead of a DOCSIS modernization program.

That makes the coupling between the two designs tight. The fiber route has to reach the node locations the RF design has chosen, with the counts that design requires, on a schedule that lets the coax work proceed. When those two designs are produced by different firms, the interface between them becomes a negotiation — and every revision on one side triggers a request on the other.

BOGO produces both, which removes that interface entirely. The same team that decides where a node boundary lands decides what fiber has to reach it. Our HFC design page covers the RF side of the same package.

GIS, records, and the design that stays true

A fiber design is also a data deliverable. The route, the structures, the splice points and the counts all have to land in the operator's system of record in a form that survives the build — otherwise the next project starts by re-discovering this one.

BOGO delivers GIS-ready data alongside the drawing set and reconciles it at closeout against what was actually placed. The reconciliation step is what separates a record that is worth something from one that is merely present. Our GIS mapping explainer covers what to model and why as-built reconciliation is the part that matters.

• Route and structure data delivered in the operator's schema
• Splice point and enclosure locations tied to the physical record
• Fiber counts and assignments traceable end to end
• As-built reconciliation at closeout, not a redline pile handed over at the end

The external constraints that shape every fiber route

Fiber design is bounded by rules BOGO does not write and cannot waive, and being honest about that is part of the job.

Pole attachment rules. Access to poles, ducts and conduits owned by utilities is governed federally under 47 CFR Part 1, Subpart J, with defined application and response timelines in § 1.1411. Those timelines shape the schedule whether or not the design accounts for them.

Safety and clearance. Aerial placement is bound by the National Electrical Safety Code and by each pole owner's construction standards, which are frequently stricter.

Local permitting. Municipal requirements, moratoria, traffic control conditions and restoration standards vary street by street and are discovered rather than assumed. BOGO identifies them during design and carries them into the permitting workflow. Approval itself remains with the pole owners and permitting authorities — BOGO keeps the workflow accurate and moving, and does not claim otherwise.

How a fiber design engagement runs

Scope is defined by route mileage, market, or a node list depending on how the program is structured. Field verification runs against the proposed corridors so that pole and conduit conditions are known before the route is committed. High level routing is agreed, then detailed design, splice planning and drafting follow.

From there the package moves into make-ready and permitting, then into construction coordination. Because BOGO carries it the whole way, a pole that comes back from make-ready as unusable is a re-route by the original designer rather than a change request across a vendor boundary.

If you have route mileage to engineer, or a fiber design that keeps colliding with make-ready, that is the conversation to have.