Construction & Program Coordination

The coordination problem

Construction on a broadband program is not one activity. It is aerial crews, underground crews, splice crews, and equipment installs, drawing on a finite pool of contractor capacity, gated by permits that arrive in an order nobody chose, across markets that each have their own constraints.

The engineering for any single node is usually straightforward. The difficulty is that a crew mobilized to a market where the permits have not landed is an expensive idle day, and a permit that lands in a market with no crew available is an expiring approval. Neither problem is visible from inside a single discipline.

Construction coordination is the work of keeping those three variables — design released, permits approved, crews available — aligned closely enough that the program keeps moving. It is a scheduling and communication discipline more than an engineering one, which is precisely why it gets under-resourced.

Construction planning

Planning turns an issued design package into an executable work plan. That means deciding how the work is broken into units a crew can be dispatched against, what sequence those units run in, what each one depends on, and what it needs on site.

• Work breakdown — the unit of dispatch, chosen so progress is measurable and blockers are visible early
• Dependency mapping — what has to be approved, placed or spliced before each unit can start
• Material and equipment readiness — lead times on optics, node hardware and actives are frequently the constraint nobody planned for
• Access and permissions — private property, MDU access, traffic control, and railroad or state crossings
• Method and standard — how the work is to be performed, to whose specification, with what documentation returned

Where the plan touches shared infrastructure it depends directly on the outcome of make-ready and permitting, and aerial work has to satisfy the National Electrical Safety Code and the pole owner's standards as built, not just as designed.

Contractor coordination

BOGO does not perform the physical construction. Contractors place the strand, pull the fiber, set the equipment and do the splicing. BOGO's role is to coordinate them against the design and the schedule — which is a distinct job from either engineering or building.

In practice that means being the single point through which questions, conflicts and field conditions flow. A crew that finds the plant does not match the drawing needs an answer the same day, not a change request that enters a queue. Because BOGO also holds the design and the OSP engineering, that answer comes from the people who drew it.

It also means holding the work to the design rather than to convenience. Field crews solve problems, which is valuable — but an undocumented field solution becomes a record discrepancy at closeout and a mystery for the next project. The coordination role is where that gets caught while it is still cheap to fix.

Fiber construction coordination

Fiber construction carries its own sequence: placement, then splicing, then testing, with each step dependent on the last and on conditions that are only discovered when crews are on site.

The coordination points that matter most are the ones between organizations — the placement crew and the splice crew, the splice plan and what was actually placed, and the test results and the operator's acceptance criteria. BOGO coordinates across those boundaries so that a splice crew arrives to find the fiber where the plan says it is, with the slack the enclosure needs.

Placement follows the route and counts set out in fiber network design, and hands off into splicing and turn-up at activation and closeout.

Program scheduling across markets

At program scale the schedule is the deliverable. Managing one market's build is tractable; managing several simultaneously, each at a different stage, with a shared contractor pool and independent permitting queues, is where programs need real scheduling.

BOGO manages that as a continuous release rather than a set of phases. Design is released to feed permitting; permitting output is released to feed construction; construction feeds activation. The aim is that no stage is ever waiting on a batch that has not been started, which is the condition that produces both idle crews and expiring approvals.

For coordination at that scale, BOGO uses Bogoflow, our own software product built for broadband program workflows. It is our product, not a third-party tool we are recommending — more about Bogoflow.

Field execution coordination and what gets returned

Coordination continues through execution. Daily and weekly progress against the plan, blockers identified early enough to re-sequence rather than absorb, and documentation captured while crews are still on site rather than reconstructed afterwards.

That last part is the bridge into closeout. Every deviation from the design, every field solution, and every as-placed condition has to be captured at the time. A program that defers documentation until the end produces a redline pile that nobody can reconcile — which is how operators end up with plant records that are wrong from the day the project completed.

What flows out of construction into activation and closeout is a documented build: what was placed, where, and where it differs from what was drawn.