System Maintenance

# Ongoing Network Support

TLDR

Ongoing network support is contracted field capacity for the work that comes up between capital projects: adds, moves, relocations, small placements, locate support, and corrective repairs. Strilla Communications runs that work under a standing agreement with reserved crew time, defined priority classes, a named point of contact, and daily reporting on what actually moved.

## The Work That Falls Between Projects

Every network generates a steady stream of work that is too small to bid and too important to ignore. A new service drop. A relocation ahead of a road widening. A handhole that needs raising after a paving contractor finished. A pole transfer notice with a deadline. A section that needs replacing after a mower found it.

Handled one at a time, each of those becomes a procurement exercise: scope it, find a contractor, get a price, cut a purchase order, wait for availability. Handled under a standing agreement, they become work orders against a scope and rate structure that already exist, which is usually the difference between work happening this month and work happening next quarter.

The cost of treating small work as an exception is mostly invisible until somebody adds it up. Engineering time spent scoping a two hour job, purchasing time spent issuing an order, and the schedule risk of a customer waiting on a drop all belong to work that a standing agreement absorbs without ceremony.

Ongoing support covers aerial and underground together because real requests do not split cleanly. One job can involve a bore, a splice, a strand adjustment, and a records update, and dividing that across three subcontractors is exactly where schedule and accountability go missing.

## How the Agreement and Work Order Flow Works

The agreement defines covered facilities, geography, priority classes, the rate structure for routine items, and the reporting rhythm. Individual jobs then run as work orders underneath it instead of as new contracts each time.

Requests arrive through one channel and get acknowledged with a scope readback, so both sides agree on what was actually asked for before anyone mobilizes. Anything that needs a site visit before it can be scoped gets one, and you receive an estimate with its assumptions listed rather than a bare number you cannot evaluate.

Priority classes decide sequence. Service affecting work outranks scheduled work, scheduled work outranks discretionary improvement, and every open item sits on one visible list so you can move something up when your own priorities shift. That list is the same list we work from, which keeps status conversations short.

## Relocations, Conflicts, and Other People's Projects

A large share of ongoing support is work created by someone else. FDOT and county roadway projects force relocations. Developers cut driveways and utilities through your alignment. A pole owner issues transfer notices. A neighboring utility discovers a conflict during design and the resolution lands on you.

This category has its own rhythm. Notice arrives with a deadline you did not choose, the engineering has to be reconciled against plant that may be poorly documented, and permitting plus coordination sit in front of any field work. Treating it as an emergency when the deadline approaches is the expensive path.

We handle the coordination side as part of the support: reviewing plan sets against your facilities, walking the conflict in the field, proposing a route that survives the new grade or the new pavement section, pulling the permits, and scheduling alongside the other contractor rather than waiting behind them.

## Reserved Crew Capacity and Why It Matters

Crews get committed to project work well ahead of the calendar. Reserved capacity under a support agreement is what keeps your small jobs from queuing behind somebody else's large build, and it is the practical reason support agreements exist at all.

Because we own our drills, bucket trucks, and splice equipment and run our own crews, capacity is a scheduling decision rather than a search for an available subcontractor. Aerial and underground can be dispatched together when a job needs both, which removes a coordination handoff that usually costs a day or more.

Reserved capacity also means the crew already knows your plant. They know how your enclosures are built, where slack is stored, how your fibers are assigned, and how your records are organized. On a difficult ticket that familiarity is worth more than general experience.

## Reporting, Reviews, and One Point of Contact

You get one person who knows the entire list. That is deliberate. Chasing status across a dispatcher, a foreman, and an office is how small work becomes invisible and how a two day job quietly turns into a two week job.

Daily production reporting covers what crews did, what they found, what is blocked, and what is scheduled next. Blockers are named specifically: a permit in review, a locate that has not cleared, a material item, an access issue on private property. Vague status is worse than no status because it cannot be acted on.

Closeout on each work order carries the same discipline as project work: test data where testing applies, photographs, restoration confirmation, and record updates. A support job that leaves no record behind is how a well documented network turns into a poorly documented one over a few quiet years.

Periodic reviews look at the program rather than the current ticket. Repeated requests in the same area usually indicate a design condition worth correcting, and closing that permanently costs less than answering it over and over. Those recommendations come with the reasoning, not just a proposal.

## How Are Pole Transfers and Make-Ready Requests Handled?

Pole transfers are handled as tracked work orders with the pole owner's deadline attached. When a pole is replaced, every attacher has to move its facilities to the new pole. Power facilities usually move first, and the communications attachers follow in the order their positions on the pole allow.

Our role is to watch for the notice, confirm the pole and the attachment involved, and schedule the transfer once the attachers above have cleared. A transfer left undone keeps the old pole standing beside the new one, a double pole condition that pole owners track closely. We close transfers and report the closure rather than letting them sit on a list.

Make-ready on your existing routes follows the same pattern. When another attacher needs space on a pole you occupy, your cable may need to be raised, lowered, or rearranged inside the communications space to meet NESC clearances and the pole owner's standard. Support crews make those moves under your agreement and update your attachment records when the work is done.

Both kinds of work arrive on someone else's timeline. Handling them inside a standing agreement means the notice turns into a scheduled work order the week it arrives, instead of becoming a scramble when the pole owner follows up.

## Key takeaways

- Ongoing network support is reserved field capacity for adds, moves, relocations, small placements, and repairs that arrive between capital projects.
- A standing agreement turns each small job into a work order against agreed scope and rates, which removes a procurement cycle from every request.
- Relocations forced by roadway and development projects cost less when coordination starts at notice rather than at the deadline.
- Every support work order should close with test data, photographs, and record updates so documentation stays current between builds.

## Key terms

**Work order**: A single job authorized under a standing agreement. It names the location, scope, priority class, and pricing basis, and it closes with a record of what was done. Work orders let small tasks move without a new contract, purchase order, or bid each time.

**Pole transfer**: Moving an attachment from an old pole to its replacement. Power facilities typically move first, then each communications attacher in turn. Until every attacher has moved, the old pole stays beside the new one, a condition usually called a double pole.

**Make-ready**: The work needed to prepare existing poles for a new attachment, such as raising or rearranging existing cables, replacing poles, or adding hardware. It brings each pole into compliance with NESC clearances and the pole owner's standard before new cable is placed.

**Utility relocation**: Moving existing facilities out of the way of a roadway, drainage, or development project. The project owner issues notice with a deadline, and the facility owner must design, permit, and build a new route, often while the project contractor is working in the same corridor.

**Scope readback**: A written confirmation sent back to the requester that restates what a work order covers, where it is, and any assumptions behind it. It catches misunderstandings before a crew mobilizes, when correcting them costs a reply rather than a wasted trip.

*Common ongoing support requests and what each involves*

| Request type | Usual trigger | Work involved | Coordination needed |
| --- | --- | --- | --- |
| New drop or extension | Customer order | Short bore or aerial span, splice, test | Locates and property access |
| Roadway relocation | FDOT, county, or city project notice | Plan review, new route, bore or aerial, cutover splicing | Permits and the roadway contractor's schedule |
| Pole transfer | Pole owner notice | Move strand and cable to the new pole | Pole owner and other attachers |
| Make-ready on an existing route | Another attacher's application | Raise, lower, or rearrange your attachment | Pole owner and the applicant |
| Structure adjustment | Paving, grading, or damage | Raise, lower, or replace a handhole or pedestal | Road or property owner |
| Corrective repair | Inspection finding or damage | Splice, section replacement, hardware | Maintenance windows and network operations |

*Utility pole attachment zones*

## What this means for your project

For a project or operations manager, the main risk in small work is that it stalls. A drop that waits a month for a purchase order, or a relocation that starts two weeks before the roadway contractor needs the corridor, carries real cost in lost customers, penalties, or a rushed and poorly documented reroute. A standing agreement removes the procurement step and puts every request on a list someone is accountable for.

Cost becomes easier to manage because routine items are priced against agreed rates and larger items arrive with written assumptions. You can compare estimates across work orders, see where money goes by corridor, and spot recurring requests that justify a permanent fix instead of another ticket.

Documentation is the quiet benefit. Small jobs are where records usually decay, because nobody updates a drawing for a two hour task. Closing every work order with photographs, test data where it applies, and red lines keeps the record set usable for the next locate, the next relocation, and the next outage.

## Related reading

- [Make-ready supportField work that prepares poles for new attachments on your routes.](https://strillacommunications.com/services/supporting-services/make-ready-support)
- [Pole attachment supportApplications, transfers, and clearances on jointly used poles.](https://strillacommunications.com/services/aerial-cable-construction/pole-attachment-support)
- [Driveway crossing boresThe short bores behind most new service drops and extensions.](https://strillacommunications.com/services/directional-drilling/driveway-crossings)
- [Daily production reportingThe daily note format used on every open support work order.](https://strillacommunications.com/services/supporting-services/daily-production-reporting)
- [Preventive maintenance cyclesScheduled inspections that generate much of the corrective work support crews close.](https://strillacommunications.com/services/system-maintenance/preventive-maintenance)
- [Support for internet service providersHow ISPs use standing agreements for drops, moves, and relocations.](https://strillacommunications.com/industries-we-service/internet-service-providers)

## What's Included

- A standing agreement covering scope, geography, priority classes, rate structure, and reporting rhythm.
- Single intake channel with a scope readback, so requests are confirmed before crews mobilize.
- Reserved crew capacity for aerial and underground work, dispatched together where a job needs both.
- Small placement work: drops, extensions, added handholes, conduit repairs, strand adjustments, and splice changes.
- Relocation and conflict work driven by roadway, development, and pole owner projects, including permitting and coordination.
- Locate ticket support and field verification of your facilities.
- Daily production reporting with named blockers and the next scheduled activity.
- Record set updates on every work order so documentation stays current between capital projects.

## Our Process

- 01 ### Agreement Setup We define covered facilities and geography, agree on priority classes and rate structure for routine items, name the point of contact on each side, and set the reporting rhythm. That work happens once instead of repeating on every request.
- 02 ### Request Intake and Readback Requests come through one channel and get acknowledged with a scope readback. If a site visit is needed to scope the work, we make it and return an estimate with its assumptions written out so you can evaluate it.
- 03 ### Prioritization and Scheduling Work is sequenced by priority class against reserved capacity, and every open item stays on one shared list. You can move an item up when your priorities change without renegotiating anything.
- 04 ### Execution and Daily Reporting Crews execute with the same daily reporting we use on project work: what was completed, what was found, what is blocked and by whom, and what is scheduled next. Findings that affect other segments get flagged rather than filed.
- 05 ### Closeout and Program Review Each work order closes with test data, photographs, and record updates. On an agreed interval we review the whole program and recommend permanent corrections for anything that keeps generating tickets.

## Capability Overview

| Engagement model | Standing agreement with work orders, or individual task orders |
| --- | --- |
| Work types covered | Aerial, underground, splice, conduit, structures, relocations, locate support |
| Priority classes | Service affecting, scheduled, discretionary |
| Intake | Single channel, acknowledged with a scope readback |
| Reporting | Daily production notes, per work order closeout, periodic program review |
| Crews and equipment | Owned directional drills, bucket trucks, and fiber splicing and test equipment |
| Coordination handled | Permitting, pole owner notices, roadway project conflicts, third party scheduling |
| Service area | Volusia County primary, Central Florida secondary, statewide by arrangement |

## Frequently Asked Questions

**How is ongoing support different from a preventive maintenance program?**: Preventive maintenance is calendar driven inspection of plant that is still working. Ongoing support is capacity for the work that arrives without a schedule: adds, relocations, small placements, conflicts, and corrective repairs. Most owners run both under one agreement, because the inspection cycles generate corrective work and the support crews are the ones who close it out.

**Can you handle relocations required by an FDOT or county roadway project?**: Yes. Relocation work is a regular part of ongoing support. We review the plan set against your facilities, walk the conflict, propose a route that survives the new grade and pavement section, handle permitting and utility coordination, and schedule the field work alongside the roadway contractor. Starting when notice arrives rather than when the deadline approaches keeps the cost down.

**How quickly can support work get scheduled?**: That depends on the priority class written into your agreement and on whether the work needs permits, locates, or material. Service affecting work is dispatched ahead of scheduled work. The value of reserved capacity is that your request is sequenced against a plan instead of waiting for a crew to become available somewhere else in the schedule.

**Can ongoing support cover plant we own but did not build?**: Yes, and it usually should. Inherited plant tends to have the weakest records, which is where support work gets slow and expensive. We start with a survey of the covered facilities, document what is actually there, and then work orders run against a record set that reflects the field rather than the original design intent.

**What reporting do we receive that we can pass upward?**: Daily production notes covering completed work, findings, blockers by name, and the next scheduled activity, plus a closeout package on each work order with test data, photographs, and record updates. The reporting is written to be forwarded, so your project manager is not translating field notes into a status update for management.

**Do you handle pole transfer notices for our attachments?**: Yes. Transfer notices can be routed to us under the support agreement. We confirm the pole and the attachment, wait for the attachers above to clear, move your strand and cable to the new pole, and report the closure with photographs. Clearing transfers promptly keeps double pole conditions off your record with the pole owner and avoids follow-up from the road authority.

**Can small jobs be priced without a separate bid each time?**: Yes. Routine items such as drops, short bores, splice changes, and structure adjustments are priced against unit rates set in the agreement, so a work order can move as soon as the scope readback is confirmed. Larger or unusual jobs get a scoped estimate with assumptions listed. Either way, the pricing basis is agreed before any crew mobilizes, not after the work is done.

**What happens when a support job turns out larger than expected?**: The crew stops at the point where the scope changed and reports what they found, with photographs. We then send a revised scope and estimate for your approval before continuing, unless the condition is service threatening and the agreement allows us to proceed. Hidden conditions such as crushed duct, undocumented facilities, or a failed structure are common, and handling them in writing keeps the cost visible.

## Related Services

- [Preventive MaintenanceScheduled preventive maintenance for fiber plant in Florida. Aerial and underground inspection cycles, OTDR trending, defect lists, and seasonal passes.](https://strillacommunications.com/services/system-maintenance/preventive-maintenance)
- [Locate and RepairFiber locate and repair in Florida. Tracer wire testing, OTDR fault location, fusion splice repairs, structure rebuild, restoration, and damage records.](https://strillacommunications.com/services/system-maintenance/locate-and-repair)
- [Make-Ready SupportField survey, documentation and coordination support for pole make-ready, with honest reporting when make-ready is the item holding your schedule.](https://strillacommunications.com/services/supporting-services/make-ready-support)
- [Daily Production ReportingEnd of day reports covering production, next day plan, field conditions and blockers, so progress is visible without anyone having to chase it.](https://strillacommunications.com/services/supporting-services/daily-production-reporting)
- [As-Built DocumentationAccurate as-built records captured in the field during construction, not reconstructed afterward. Coordinates, depths, photos and reconciled footage.](https://strillacommunications.com/services/supporting-services/as-built-documentation)

---
Source: https://strillacommunications.com/services/system-maintenance/ongoing-network-support