Services

# System Maintenance

Contract maintenance for aerial and underground plant: scheduled inspection cycles, optical testing, locating, and permanent repairs under one agreement.

TLDR

System maintenance is the ongoing care of fiber and coaxial plant already in service: scheduled inspections, optical testing against a baseline, locating, and permanent repair. Strilla Communications works under recurring maintenance agreements across Volusia County and Central Florida, using owned crews and equipment so the same people who know your network are the ones who come back to it.

## What a Maintenance Program Covers After Construction Ends

A maintenance program covers everything that keeps existing plant working: the poles, strand, and lashed cable overhead, the conduit, handholes, and vaults below grade, the splice enclosures at both, and the records that describe all of it. Construction ends at acceptance. Maintenance is the part that runs for the rest of the plant's service life.

Most networks are maintained by accident. Something fails, someone finds a contractor with a truck available, the fault gets patched, and the as-built never gets updated. Two years of that produces a network nobody can describe accurately, which is exactly the network that takes longest to restore when a real outage arrives.

A maintenance agreement replaces that pattern with a schedule and an owner. Inspection cycles run on the calendar whether or not anything is broken. Defects found during a cycle become work orders with priorities. Every touch updates the record set, so the drawing you hand a crew at two in the morning matches what is actually in the ground.

We maintain plant we built and plant we did not. Taking over another contractor's network starts with a baseline survey, because we will not commit to a response standard on facilities nobody on our side has seen. Coverage typically includes:

- Aerial plant: poles, strand, lashed and self supporting cable, guys, anchors, bonding, and stored slack.
- Underground plant: conduit, innerduct, handholes, vaults, tracer wire, markers, and pedestals.
- Splice points: enclosure integrity, sealing, trays, buffer tube routing, and grounding.
- Optical performance: bidirectional OTDR traces, end to end loss, and connector inspection where accessible.
- Records: as-built corrections, fiber assignment updates, splice matrix changes, and a photo log tied to location.
- Field response: locating, damage repair, relocations, and support while third party contractors work near your alignment.

## Why an Agreement Beats Calling Around After a Failure

The difference between an agreement and a callout is who is already prepared. Under an agreement, the crew has your route maps, your splice matrix, your enclosure types, and your fiber counts before the phone rings. A callout crew spends its first hours learning your network at the worst possible time.

Availability is the second difference. Crews get committed to project work weeks ahead of the calendar. A maintenance agreement reserves capacity, and reserved capacity is what turns a response commitment into something you can put in front of your own management without hedging it.

Materials are the third. Repairs stall when the cable on the reel does not match the cable in the ground, or when the enclosure on the truck will not accept the tray family already spliced into your plant. Under an agreement we identify your cable types, fiber counts, hardware, and enclosure families up front, so the fix is a proper repair rather than a hybrid nobody wants to own later.

Knowledge is the fourth difference. Every network has quirks: a segment where the fiber assignments never matched the design, a handhole that floods every summer, a span that was always tight on clearance. Crews that return to the same plant carry that knowledge forward instead of rediscovering it, and none of it has to be explained again by your project manager at the start of each visit.

Last, an agreement gives the work a single point of contact. One person knows what is open, what is scheduled, and what changed yesterday, and you receive that in a daily note instead of assembling it by calling a crew leader from a job site.

## How We Structure a Maintenance Agreement

We build agreements around four things: scope, cadence, response classes, and reporting. Scope names which facilities are covered and where coverage stops, usually at a demarcation, a hut wall, or a defined boundary on the route. Anything outside that line gets handled as separate work rather than argued about during an outage.

Cadence sets how often each class of plant gets inspected. Aerial cable in a wind exposed, tree lined corridor needs a shorter interval than conduit running under a divided highway. We propose cadence from what the baseline survey actually finds, and it can differ segment by segment inside the same agreement instead of applying one interval to everything.

Response classes separate the urgent from the merely open. A service affecting fault, a damaged but still working facility, and a cosmetic defect should not compete for the same crew on the same morning. We define those categories with you and write the target response for each into the agreement, so priority does not depend on who escalates loudest.

Reporting keeps the program honest. Every cycle produces a report, every corrective action produces a record, and periodic reviews look at what keeps failing rather than only at what failed last week. Recurring defects usually point at a design or construction condition worth correcting once instead of repairing forever. A workable agreement names:

- Covered facilities, geography, and demarcation boundaries, listed explicitly.
- Inspection cadence set per segment rather than a single interval network wide.
- Response classes with defined priorities and a target response for each.
- Unit priced task work for routine items, with scoped estimates for larger corrections.
- A named point of contact and an agreed reporting rhythm.
- An escalation path and an after hours contact procedure that both sides have read.

## Inspection Cycles for Aerial and Underground Plant

Aerial and underground plant fail differently, so they get inspected differently. Aerial problems are usually visible: a sagging span, tree contact, loose lashing, corroded hardware, a leaning pole, an enclosure swinging on its mount. Underground problems hide until something digs them up, so underground inspection focuses on access points, structures, and evidence rather than on the cable itself.

Aerial cycles therefore work by sight and measurement: the pole line is walked or driven, suspect spans get a closer look from the bucket, and clearance at road and driveway crossings is measured rather than judged by eye.

An underground cycle opens handholes and vaults. Standing water, silt, and root intrusion get noted. Slack coils are checked for support and for the bend radius they were left at. Enclosures are inspected for seal integrity, corrosion at the ports, and moisture indication where the design uses it. Racking gets corrected on the visit so the next crew is not working out of a mud pit.

Above grade, we check markers, pedestals, riser guards, and tracer wire access points. A missing marker and a dead tracer wire are the two conditions most likely to turn a routine locate ticket into a dig-in, and both are inexpensive to fix on a scheduled visit and expensive to fix after an excavator has already been through.

## Optical Testing and the Value of a Baseline

A trace only means something compared to another trace. The first cycle establishes a baseline: bidirectional OTDR at the wavelengths your plant uses, end to end loss, and connector inspection at the patch points we can reach. Everything measured after that is a comparison rather than an isolated number.

Comparison is what turns testing into warning. A splice that has crept upward in loss, an event that appeared where the trace used to be clean, a connector that degrades a little each time it is handled: all of those show up in a trend and hide inside a single test. Rising loss almost always has a physical cause, and finding that cause during a scheduled window costs a fraction of finding it during an outage.

Live fibers are tested inside agreed maintenance windows and coordinated with your network operations group, because nothing about a maintenance program should surprise the people watching alarms. Dark and spare strands in the same cable can be tested without that constraint, and they frequently show the same environmental problem first, since they share the route, the slack, and the water.

Testing scope is a decision rather than a default. Some owners want every fiber traced every cycle. Others want a sample per cable, with full testing reserved for segments that showed movement or that carry the most critical traffic. Both are defensible. What is not defensible is testing without recording the conditions, because a trace taken at a different wavelength or from the opposite direction is not comparable to the one before it.

Results go into your record set with the fiber identifier, the direction, the wavelength, the date, and the technician. A trace file with no context is nearly useless a year later, so we deliver test data as organized records rather than as attachments buried in an email thread.

## Keeping Records Accurate as the Network Changes

Documentation starts decaying the day construction ends. Fibers get reassigned, a section gets rerouted around a road widening, a splice moves into a new enclosure, and each of those changes is correct in somebody's head and wrong in the drawing.

Maintenance is the only routine that touches the whole network on a schedule, which makes it the right place to catch that drift. Each inspection compares field condition against the record, and differences come back as red lines instead of surprises. Over a few cycles the record set converges on reality rather than drifting further from it.

We return the same document family every cycle: marked up route drawings, splice matrix corrections wherever we changed something, photographs tied to a location, GPS points for facilities we opened, added, or relocated, and the test data. If your network lives in a GIS or an OSP records system, we deliver in a format your team can import instead of a PDF somebody has to retype.

This pays off hardest during emergencies. The value of accurate records is measured in the hours you do not spend guessing which handhole holds the splice, and it compounds every year the discipline holds.

## Florida Conditions That Set the Maintenance Calendar

Florida's maintenance year is built around one obvious season and several less obvious ones. Storm season drives a pre-season hardening pass and a post-season verification pass. The rest of the calendar is scheduled around heat, water, and growth.

Water is the constant. A high water table means handholes flood and stay flooded, so hardware selection, sealing, slack support, and racking get inspected more aggressively here than in drier regions. Sandy soil moves: conduit settles, markers migrate, and anchor rods work in ground that does not hold the way clay does. Those are ordinary conditions rather than failures, but they have to be watched.

Vegetation grows year round. A span with comfortable clearance in January can be resting in a palm frond by August. Lightning activity is heavy, so bonding and grounding get real verification rather than a checkbox, and surge damaged hardware near the power space gets replaced instead of reused.

Heat matters more than most schedules assume. Aerial cable sags further in August than a sag chart used during a January installation suggests, so clearance measured in cool weather can read better than the plant actually performs. Where a crossing is close to the limit, we measure it at the worst time of day in the warm months rather than at the most convenient time to send a crew.

Roadwork and development are the other driver. Corridors get widened, driveways get cut, and somebody else's excavator eventually arrives near your alignment. Scheduled inspection cycles combined with the locate tickets we handle for you catch third party construction near your plant while it is still a phone call instead of a repair.

## Who Sets Inspection Intervals, Response Targets, and Loss Limits?

The network owner sets them, and the maintenance agreement writes them down. Inspection intervals, the response target for each class of trouble, and the optical loss a span or splice may show before it is flagged all come from the owner's engineering standard, the specification the plant was accepted under, and any service commitments the owner has made to its own customers. A maintenance contractor should not invent those numbers.

Our part is to make the numbers workable. After the baseline survey we can show where a proposed interval looks long for the exposure we found, where a response target depends on access that does not exist at night, or where an acceptance figure was written for a design the field no longer matches. The owner decides, and the agreement records the decision.

Loss limits deserve particular care. A splice or a span is usually judged two ways: against the absolute figure in the owner's standard, and against its own baseline. A reading can pass the standard and still show a change worth investigating, so the agreement should say which comparison opens a work order and which only puts the item on a watch list.

Writing these terms down before the first cycle prevents the most common maintenance dispute, which is a disagreement during an outage about what was promised. When both sides can point to the same page, the conversation moves straight to the repair.

## How Does a Handover From Another Maintenance Contractor Work?

A handover works best as a short, deliberate project with its own checklist. The outgoing records, the open work list, the material on hand, and the access arrangements move to the new contractor before the first scheduled cycle, and the baseline survey then confirms what the paperwork says.

Records come first. We ask for route drawings, splice matrices, fiber assignment sheets, test data from acceptance and any later cycles, cable and enclosure specifications, and the list of open defects. Gaps are normal on inherited plant. What matters is knowing where the gaps are before a crew is sent to a fault.

Access comes next. Locked cabinets, gated easements, hut entry procedures, and pole owner contacts each have a key, a phone number, or a permit behind them. A crew that cannot get through a gate at night cannot meet any response target, so we test access during the handover instead of discovering the problem during an outage.

Temporary repairs need their own attention. Inherited networks often carry restoration splices, cable lying on the ground, and enclosures that were never remounted. Each one goes on the open list with a location and a recommended permanent fix, because those points are the most likely to fail first. A complete handover package includes:

- Route drawings, splice matrices, and fiber assignment records in their current form.
- Acceptance test data and any trace files from later maintenance cycles.
- Cable, enclosure, and hardware specifications, plus any spare material on hand.
- The open defect list, including every temporary repair still in place.
- Access details for cabinets, huts, gated easements, and private property.
- Contacts for pole owners, road authorities, and the owner's network operations group.

## Key takeaways

- A fiber maintenance program is scheduled inspection, testing, locating, and repair of plant that is already in service, run on a calendar rather than after a failure.
- Inspection intervals, response targets, and optical loss limits belong in the maintenance agreement and come from the network owner's standard, not from the contractor.
- An OTDR trace is most useful when it is compared with a baseline taken from the same direction at the same wavelength.
- Every maintenance visit should update the record set, because accurate as-builts are what shorten the next outage.
- In Florida, storm season, a high water table, and year round vegetation growth shape the maintenance calendar.

## Key terms

**Maintenance agreement**: A standing contract between a network owner and a contractor that defines covered facilities, inspection cadence, response classes, pricing structure, and reporting. It turns maintenance from a series of one-off callouts into planned work, and it is where the owner's intervals and response targets are written down for both sides.

**Baseline survey**: The first full inspection of covered plant, done before a maintenance program starts. It records routes, structures, enclosure types, cable and fiber counts, hardware condition, tracer wire continuity, and optical performance, so every later inspection has a known starting condition to compare against.

**OTDR (optical time domain reflectometer)**: A test instrument that sends light pulses into a fiber and measures the light reflected and scattered back. The resulting trace shows splices, connectors, bends, and breaks as events at a distance along the fiber, along with the loss at each event.

**Response class**: A category of trouble defined in a maintenance agreement, such as service affecting, damaged but working, or cosmetic. Each class carries its own priority and a target response set by the network owner, so crews are dispatched by agreed rules rather than by whoever escalates first.

**Tracer wire**: A copper conductor buried alongside nonmetallic conduit or fiber so locators can find the route with an electronic signal. Tracer wire that is broken or corroded leaves a segment unlocatable, which makes it far more likely that another excavator will damage the cable.

*System maintenance services compared by trigger, scope, and output*

| Service | What triggers the work | Typical scope | What you receive |
| --- | --- | --- | --- |
| Preventive maintenance | The inspection calendar in the agreement | Aerial and underground passes, OTDR trending, tracer wire checks | Defect list, photos, trace files, red lines |
| Ongoing network support | A work order for adds, moves, relocations, or small placements | Bore, strand, splice, and structure work between capital projects | Daily notes and a closeout per work order |
| Locate and repair | A locate ticket, a fault, or third party damage | Locating, fault location, excavation, splicing, restoration | Test data, damage record, repair record |
| Seasonal passes | The approach and end of storm season | Tension, anchors, slack, enclosure mounts, vegetation | Prioritized hardening and damage lists |
| Program review | The review interval named in the agreement | Repeat defects, chronic segments, record gaps | Recommendations for one-time corrections |

*Preventive maintenance cycle*

## What this means for your project

For an owner or operations manager, a maintenance agreement converts unknown risk into scheduled work. Many outages on mature plant trace back to conditions an inspection could have seen: a dead tracer wire, a flooded handhole with unsupported slack, a span that sagged into a tree line, a splice whose loss kept climbing. Finding those on a planned visit costs a crew day. Finding them during an outage costs restoration time, customer credits, and overtime.

Budget becomes predictable when the agreement separates recurring inspection cost from unit priced corrective work and scoped estimates for larger fixes. You can forecast a normal year, and an abnormal one arrives with its pricing structure already agreed. Reserved crew capacity protects your schedule as well, because maintenance and small jobs no longer wait behind someone else's construction project.

The longest lasting benefit is the record set. Each cycle corrects drawings, splice matrices, and GPS positions, so the information your engineers, locators, and restoration crews rely on gets more accurate over time instead of less. When a storm or a dig-in does take plant down, accurate records shorten the hours between the first call and restored service.

## Related reading

- [Emergency service restorationUnscheduled response when plant is already down, made faster by maintained records.](https://strillacommunications.com/services/emergency-service-restoration)
- [Fusion splicing for repairs and changesSplice work and acceptance testing used in permanent repairs and fiber reassignments.](https://strillacommunications.com/services/fiber-splicing-installation/fusion-splicing)
- [Tracer wire installation and repairRestoring locatability on underground segments that fail a locate.](https://strillacommunications.com/services/conduit-installation/tracer-wire-installation)
- [As-built documentationHow field changes get captured in drawings, splice matrices, and GPS data.](https://strillacommunications.com/services/supporting-services/as-built-documentation)
- [Maintenance project typesThe kinds of maintenance engagements we take on and what each covers.](https://strillacommunications.com/projects/maintenance-projects)
- [Guidance for maintenance and operations managersWhat operations teams usually need from a maintenance contractor.](https://strillacommunications.com/industries-we-service/maintenance-and-operations-managers)
- [Closeout and documentation standardsThe record package every job should leave behind.](https://strillacommunications.com/resources/closeout-and-documentation-standards)

## What's Included

- Scheduled inspection cycles for aerial and underground plant, with the interval set per segment rather than one interval network wide.
- Bidirectional OTDR testing and end to end loss measurement, compared against a baseline established on the first cycle.
- Handhole and vault entry including pumping, cleaning, slack re-racking, and enclosure seal inspection.
- Aerial hardware inspection covering lashing, dead ends, guys, anchors, bonding, and midspan clearance at road and driveway crossings.
- Cable locating and tracer wire continuity verification, including support for locate tickets on facilities you own.
- Permanent repair of damaged fiber, conduit, and structures, with splice work tested and documented before the crew demobilizes.
- Corrective work orders with defined priority classes and a named point of contact for status.
- Record set updates: red-lined as-builts, splice matrix corrections, GPS points, and a photo log tied to location.
- Pre-storm hardening passes and post-storm verification sweeps scheduled around the season.
- Program reviews that identify repeat failures and recommend a one time correction instead of a recurring repair.

## Our System Maintenance Process

- 01 ### Baseline Survey Before any commitment, we walk the covered plant and record what is actually there: route, structures, enclosure types, cable and fiber counts, hardware condition, tracer wire continuity, and the gap between the field and your drawings. The survey sets the starting condition so later cycles have something to measure against.
- 02 ### Maintenance Plan We write the plan from what the survey found. Segments get an inspection cadence based on exposure, response classes get defined with you, boundaries and demarcations get named, and the reporting rhythm gets agreed. The plan is specific to your network rather than a standard interval applied to everything.
- 03 ### Scheduled Cycles Crews run the cycle on the calendar whether or not anything is broken. Aerial passes, underground access point entries, optical testing, and tracer wire checks happen in the planned sequence, and minor corrections get made during the visit wherever scope and safety allow.
- 04 ### Corrective Work Orders Defects that cannot be fixed inside the cycle become work orders carrying a severity, a location, a photograph, and a recommended correction. You approve the ones that need approval, and everything open stays visible on one list rather than living in separate email threads.
- 05 ### Record Update Every cycle and every corrective action updates the record set. Red lines go against the as-builts, splice matrix entries get corrected, GPS points get captured for anything opened or added, and test data gets filed with the fiber identifier, direction, wavelength, and date attached.
- 06 ### Program Review On an agreed interval we review the program rather than the last ticket. Repeat failures, chronic segments, damage clusters, and record gaps get pulled out, and we recommend the permanent corrections that would remove recurring work from the schedule.

## Capability Overview

| Engagement model | Recurring maintenance agreement, task order, or time and materials |
| --- | --- |
| Plant covered | Aerial and underground, backbone and distribution, fiber and coaxial |
| Inspection cadence | Set per segment in the maintenance agreement, to the network owner's standard |
| Optical testing | Bidirectional OTDR, end to end loss, connector inspection where accessible |
| Locating methods | Tracer wire toning, conductive and inductive locating, metallic cable tracing |
| Repair classes | Temporary restoration splice, permanent replacement section, structure rebuild |
| Documentation returned | Defect lists, geotagged photos, trace files, red-lined as-builts, work order history |
| Crews and equipment | Owned directional drills, bucket trucks, and fiber splicing and test equipment |
| Service area | Volusia County primary, Central Florida secondary, statewide Florida by arrangement |

## System Maintenance 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)
- [Ongoing Network SupportOngoing network support for Florida fiber owners. Reserved crew capacity for adds, moves, relocations, small placements, and daily reporting on open work.](https://strillacommunications.com/services/system-maintenance/ongoing-network-support)
- [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)

## Frequently Asked Questions

**Do you maintain networks your company did not build?**: Yes, and it starts with a baseline survey. We walk the covered plant, record structures, enclosure types, cable and fiber counts, hardware condition, and tracer wire continuity, then compare that against your drawings. The survey sets a defensible starting condition and lets us commit to a cadence and a response standard on facilities we have actually seen rather than facilities we have only read about.

**What is the difference between maintenance and emergency restoration?**: Maintenance is scheduled work on plant that is still functioning, run on a calendar to find defects before they cause outages. Emergency restoration is unscheduled response after service is already down. They support each other: a maintained network restores faster because the records are accurate, the slack locations are known, and the responding crew has already worked on that plant.

**How often should fiber plant be inspected?**: It depends on exposure, not on a single rule. Aerial cable in a tree lined, wind exposed corridor justifies a shorter interval than conduit under a divided highway. Most programs use a mix of frequent passes on exposed segments, longer intervals on protected ones, and seasonal passes around storm season. We recommend cadence per segment after the baseline survey, and the owner's standard and the agreement set the final intervals.

**Can you test fiber that is carrying live traffic?**: Live fibers are tested inside maintenance windows you agree to and coordinated with your network operations group, so nothing surprises the people watching alarms. Dark and spare strands in the same cable can be tested outside those windows, and because they share the route, the slack, and the water, they often reveal an environmental problem before the lit fibers do.

**What happens when an inspection finds a defect?**: Each finding gets a severity, a location, and a photograph. Minor items get corrected during the visit where scope and safety allow. Anything larger becomes a work order with a recommended correction, and it stays on one open list with a priority until it is closed. You approve what needs approval, and nothing sits in an inspector's notebook.

**Do you handle locate tickets for facilities we own?**: Yes. Locate support can be written into the agreement, covering ticket response, field marking, tracer wire continuity testing, and repair of tracer wire that has failed. It also feeds the maintenance program: repeated tickets in one corridor usually signal upcoming construction near your plant, which is useful warning rather than routine paperwork.

**How is maintenance work priced?**: Agreements typically combine a recurring component for scheduled inspection cycles with unit rates for routine corrective items and scoped estimates for larger corrections. The structure matters more than any single line: you should be able to predict the cost of a normal year, and you should never be negotiating scope during an outage. We put the pricing structure in writing before the first cycle runs.

**What should a maintenance agreement say about response times?**: It should list each response class and the target the network owner sets for it, in writing, before the first cycle. A service affecting fault, a damaged but working facility, and a cosmetic defect each need a different target. We do not quote one number for every network, because a realistic target depends on geography, access, and after hours arrangements, which the baseline survey and the agreement work out together.

**Can the contractor that built our network also maintain it?**: Yes, and there are practical advantages. The builder already holds the as-builts, the splice records, and the acceptance test data, so the baseline is largely in hand. The main caution is independence: inspection findings on plant a contractor built should be reported with photographs and test data the owner can verify, so construction defects get recorded honestly rather than quietly fixed and left out of the record.

## Related Services

- [Directional DrillingTrenchless directional drilling for fiber and utility conduit across Volusia County and Central Florida, planned against verified locates and closed out with documented bore logs.](https://strillacommunications.com/services/directional-drilling)
- [Aerial Cable ConstructionPole line construction, strand placement, lashing, and aerial fiber installation with make-ready coordination and NESC clearance verification.](https://strillacommunications.com/services/aerial-cable-construction)
- [Fiber Splicing & InstallationFusion splicing, fiber placement, termination, and enclosure installation with bidirectional OTDR support and a recorded loss value for every fiber.](https://strillacommunications.com/services/fiber-splicing-installation)
- [Conduit InstallationHDPE duct, innerduct, and microduct placed by bore, trench, or plow, proofed with a mandrel, and made locatable with tracer wire and marker tape.](https://strillacommunications.com/services/conduit-installation)
- [Emergency Service RestorationUnplanned repair work that puts a damaged fiber or conduit network back in service after a cut, a storm, or a failure, followed by permanent repair and a documented closeout.](https://strillacommunications.com/services/emergency-service-restoration)
- [Outside Plant ConstructionTurnkey OSP construction that carries a fiber build from permitting and boring through aerial, splicing, restoration, and a documented closeout.](https://strillacommunications.com/services/outside-plant-construction)

---
Source: https://strillacommunications.com/services/system-maintenance