SystemAsset Management & Maintenance

Vegetation Management Planning

Risk-based vegetation management planning: see when each span will lose its clearance, and trim it before fire season

Every span forecast to lose its clearance is trimmed before fire season.

See one case, screen by screen ↓
target37of 37spans forecast inside the 4 ft minimum trimmed before fire season, on the sample line
estimated$1.88Mof the cycle budget moved from 152 miles with nothing to cut to the spans that turn red — 152 mi × $12,400 a cycle mile
target25%fewer tree-caused outage minutes on lines planned by the forecast
demo6 → 37spansinside 4 ft on line L-204 — today, and by 1 June 2027, when fire season starts; the calendar trims it in October 2027
The problem

Why a fixed trim cycle reaches the line after the trees do

Vegetation Management Planning is software for a utility's vegetation programme: it measures how close the trees are to the wire on every span of every overhead line, forecasts when each span will lose its clearance, and builds the trim plan from the spans at risk instead of from the calendar. Many programmes still trim each line on a fixed cycle of a few years. The calendar reaches a line when its turn comes, not when its trees reach the wire. Cottonwood, willow and alder on wet creek bottoms are hazardous a year before the crew arrives, while oak and pine ridges are trimmed with nothing to cut.

The evidence that would change the plan sits in pieces. LiDAR is accurate but too expensive to fly every year. Foresters' patrol notes and customer reports of branches on the line end up in spreadsheets nobody opens. Outage cause codes are not tied to spans. And contractor invoices are paid on the spans claimed, with a manual sample checked afterwards. Vegetation is the most common cause of US power outages, and in a high fire-threat area a span inside the minimum clearance is a fire risk.

typical20%+of US power outages are caused by vegetation (US DOE, 2024)
typical$1.21per $1of cost for every $1 of vegetation work deferred one year, as cited in testimony in Kentucky PSC case 2025-00114
Where a line's planning days go, from patrol to paid invoiceestimated
By hand19 days
With the solution3.3 days
  • Patrolling and measuring the line to find what needs cutting6 → 1 d
  • Reading patrol notes and customer reports into findings2 → 0.3 d
  • Tying past outages to spans1 → 0.2 d
  • Grouping, prescribing and pricing the work units3 → 0.5 d
  • Writing the bid package for the contractor panel2 → 0.3 d
  • Checking the contractor's work against the invoice5 → 1 d

Estimated split for one distribution line of about 400 spans, in working days, by hand and with the solution.

How it works

How imagery becomes a trim plan

Six specialist agents measure, forecast and plan every span; the vegetation programme manager signs the plan.

What comes in
Evidence in5 sources · satellite, LiDAR, patrols, outages, trim records
Agents at work
Clearance measurerevery span, every pass
Then
Growth forecaster
Patrol note reader
Outage cause matcher
Then
Trim plan builderred by fire season
Then
Work verifierbefore payment
A person decides
Vegetation programme managersigns the plan and deferrals
What comes out
Risk-ranked trim plan
Bid package
Verified work
One case, step by step

One line, from a satellite pass to a signed trim plan

Lumina Utilities trims its 2,380 overhead miles on a four-year calendar. Line L-204, Harlow – Pine Hollow, is 21.4 miles and 412 spans of 12.47 kV, serving 2,914 customers; spans 181–412 lie in the high fire-risk area. It was last trimmed in October 2023, so the calendar trims it next in October 2027 — four months into fire season. Here is 13 October 2026, screen by screen, in the working solution.

  1. 0106:10

    The line opens as one strip of spans

    Nadia Kerr · Vegetation programme manager

    Nadia owns the FY2027 vegetation budget and the 595-mile cycle plan. Her home screen draws L-204 as a straight strip from Harlow substation to Pine Hollow, the canopy rising toward the wire, dashed lines at the 6 ft trim trigger and the 4 ft minimum, and a colour band span by span. Today 6 spans are inside 4 ft — 5 of them in the fire-risk area — and 30 are amber, at 4–6 ft. The agents ran at 06:10 on the 9 Oct satellite pass.

    Run log: “Clearance measurer · measured 350 spans with trees from the 9 Oct pass · 3 used the 14 Sep pass (cloud, shadow)”

  2. 02Slide to June

    Move the forecast to fire season: 37 spans turn red

    Growth forecaster

    Under the title runs a forecast slider from today to September 2027, with fire season from 1 June marked. Nadia moves it to 1 June 2027 and the strip redraws: 37 spans inside 4 ft, 31 more than today, 29 of them in the fire-risk area. The forecast is learned from three years of satellite canopy change, the species and the season. The rail on the right lists the red spans in the order they cross 4 ft.

    “25 of 37 cross 4 ft between March and June — the spring growth a fixed cycle cannot see coming.”

  3. 03Span 287

    6.4 ft clear today — a patrol would pass it

    Clearance measurer and Growth forecaster

    Span 287, P-287 to P-288, is a black cottonwood on the Hollis Creek bottom, with 589 customers beyond it. It is 6.4 ft from the wire on the 9 Oct pass, calibrated to the 18 June 2025 LiDAR flight. It grows toward the wire at 6.4 ft a year, crosses 4 ft on 12 May 2027 and reaches 3.2 ft ± 0.6 ft on 1 June. The side view shows today's crown and the forecast crown as a ghost, and each number cites its source.

    The growth forecaster never forecasts past 12 months, and sends a low-confidence span to patrol instead of hiding it.

  4. 04The patrol note

    A note written at the pole reaches the plan

    Ellen Marsh · Utility forester

    On 22 Sep Ellen walked the Hollis Creek bottom and wrote: “Big cottonwood on the creek side of P-287/P-288, dead top, leaning maybe 8 degrees toward the wire, about 26 in DBH, 70 ft.” The patrol note reader matched it to span 287 and read it into tree, condition, access and urgency, highlighting the words each came from. Its finding: hazard tree — remove. Access: locked gate, call the landowner first. Urgency: remove on the first visit.

    The patrol note reader never closes a hazard tree; a forester confirms every one.

  5. 05Every line

    All 70 lines, ranked by what will be red in June

    Nadia Kerr · Vegetation programme manager

    The same slider drives the Lines screen. On 1 June 2027 the network has 1,126 spans inside 4 ft, against 214 today. L-204 leads with 37, then L-152 Alder Flats with 29 and L-226 Stonebridge with 24 — both on the calendar for 2028. L-163 Copper Gulch is due in May 2027 and should come forward to March. L-117 Marrow Creek, due in March, can defer its cycle to FY2029 and spot-trim 3 spans.

    Each line beside its calendar date and a recommendation: before June, bring forward, spot trim, on the calendar or defer.

  6. 06One click

    The plan is built from the red spans, step by step

    Trim plan builder

    Nadia builds the plan. The trim plan builder collects the 37 spans red by 1 June, adds the 4 hazard trees from patrol notes — spans 287, 302, 334 and 371, each confirmed by Ellen Marsh — groups them into 9 work units with one access point each, writes prescriptions and prices them on the contract unit rates, and sequences them before fire season.

    “Nothing goes to a contractor until you approve.”

  7. 07The plan

    9 work units, 14 crew-days, $86,400 — done by 24 February

    Trim plan builder

    Visit 1, by 12 Nov 2026, takes the 6 spans already inside 4 ft, 1 red by January and the 4 hazard trees. Visit 2, from 11 Jan to 24 Feb 2027, takes 30 spans in the dormant season, before spring growth — well inside the 15 May deadline. Post-trim clearance is 15 ft for cottonwood and willow and 12 ft for the rest. The calendar would trim all 412 spans in October 2027 for $265,400.

    Calendar: “All 412 spans in October 2027 — four months after 37 spans turn red.”

  8. 08Signed

    Nadia approves and signs the plan

    Nadia Kerr · Vegetation programme manager

    The sign-off states what she approves: 9 work units, 37 spans and 4 hazard trees for $86,400; the L-204 calendar cycle of $265,400 moves to FY2029; bid package BP-2027-014 is released to the contracts manager. Version 3 of the FY2027 plan re-sequences 152 cycle miles with nothing to cut and moves $1,884,800 to spans that turn red. The signature goes on the audit trail.

    Deferrals only where no span is forecast inside 6 ft for 12 months; a line in the fire-risk area needs the director.

  9. 09Out to bid

    A bid package with spans, prescriptions and access notes

    Owen Pratt · Contracts manager

    BP-2027-014 lists 37 side-trim spans to ANSI A300 natural-target pruning, 4 hazard tree removals, 3 days of traffic control and 2 visits, with access notes down to the locked gate at the Hollis barn. It goes to the three panel contractors, bids due Fri 6 Nov 2026 at 17:00. On L-152, three bids are compared by unit price: Cascade Edge Arborists is the lowest compliant bid at $64,650, inside the $68,900 estimate.

    Northfork Vegetation Co. is marked not compliant: “No ISA-certified utility specialist named as crew lead.”

  10. 10Before payment

    Pay for the spans that were cut to spec

    Work verifier · Ellen Marsh signs

    Last season, on L-311 Fernbank, Cascade Edge claimed 52 spans and 2 hazard trees on invoice CE-26-1187 for $64,880. The work verifier matched 54 completion records to their spans, compared them with Ellen's audit of 18 spans and the 9 Oct satellite pass: 49 verified to spec, spans 118 and 141 short of the post-trim clearance, span 203 billed but not worked. $61,140 goes for payment and $3,740 is held.

    The work verifier never approves a payment; the forester signs the verification and the contracts manager pays.

Who it’s for

Built for everyone who keeps trees off the wire.

The same line, seen by the five people who plan, cut, check and pay for the work — what their season looked like, and what it looks like now.

NK
Nadia KerrVegetation programme manager · owns the $11.6M FY2027 budget and the 595-mile cycle plan
Vegetation programme manager
Before
Answers to the director for tree outages and fire-season readiness, with a plan set by the calendar. “The calendar sent crews to Marrow Creek, where there was nothing to cut, while Pine Hollow was growing into the wire.”
Now
Slides the forecast to fire season, builds the plan from the spans that will be red, and signs every plan and deferral.
EM
Ellen MarshUtility forester · pre-inspection and audit · confirms hazard trees and signs verification
Utility forester
Before
Patrols lines, writes hazard-tree notes and audits contractor work. “I write it down at the pole. Then it sits in a spreadsheet nobody opens.”
Now
Her notes are read into span, tree, condition and urgency, and she confirms each hazard tree before it goes on the first visit.
TR
Tomás ReyesReliability engineer · reviews every tree-caused outage and owns the reliability report
Reliability engineer
Before
Knows where trees caused outages, not where they will. “I can tell you which spans tripped last year. I can't tell you which ones will next June.”
Now
Sees tree-caused outages tied to spans, confirms each cause, and compares forecast-planned lines with calendar-planned ones.
OP
Owen PrattContracts manager · sends bid packages, awards work, approves contractor invoices
Contracts manager
Before
Pays on the spans claimed and checks a sample afterwards. “I pay for what was verified, not for what was claimed.”
Now
Compares bids by unit price with a compliance check, and pays only the spans verified to the post-trim spec.
WB
Wes BrandtGeneral foreman, Ridgeline Tree Services · prices and schedules crews
Contractor
Before
Prices from a line name and a cycle date. “Give me spans, prescriptions and access notes, and I'll give you a real price.”
Now
Gets a bid package with every span, prescription, quantity, visit window and access note.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents measure, forecast and plan every span; the vegetation programme manager signs the plan.

Clearance measurer

Measures radial and overhang clearance on every span from the latest LiDAR and each satellite pass, and calibrates the satellite canopy height to the last LiDAR flight.

  • Never measures through cloud — uses the last clear pass and marks the span low confidence
  • Never changes a minimum clearance or a clearance rule
Growth forecaster

Learns growth toward the wire from three years of passes on spans of the same species and soil, adjusts for this season's rainfall, and forecasts monthly when each span crosses the 6 ft trigger and the 4 ft minimum, with a confidence band.

  • Never forecasts past 12 months
  • Low-confidence spans go to patrol, not hidden
Patrol note reader

Reads foresters' notes, storm patrols, contractor notes, photos and customer reports into line, span, species, condition, access and urgency, matching pole numbers, addresses or GPS and quoting the sentence.

  • Never closes a hazard tree — a forester confirms every one
Outage cause matcher

Ties outage records and cause codes to spans, and adds the customers downstream and the fire-risk area to each span's risk.

  • Never re-codes an outage cause — it proposes, reliability confirms
Trim plan builder

Groups red spans and confirmed hazard trees into work units by access, writes prescriptions, prices them on the contract unit rates, sequences them before fire season within budget and drafts the bid package.

  • Never drops a span forecast inside 4 ft before fire season
  • Proposes deferrals only where no span is forecast inside 6 ft for 12 months
  • Never awards work — the programme manager approves the plan
Work verifier

Compares contractor completion — GPS photos, crew notes and unit counts — with the forester's audit and post-work satellite imagery, and reconciles the invoice span by span.

  • Never approves a payment — the contracts manager does
Vegetation programme manager

Signs; forester confirms hazards; contracts manager pays. The agents propose; a named person decides.

Ask in plain words

Ask about any line, span or plan, in plain words

Ask about any line, span or plan — or say what to trim first. Every answer points to its source.

Which spans on L-204 go red before June?

37 spans are forecast inside 4 ft by 1 June 2027. Six already are today; the other 31 cross between January and June, most of them in April and May, when cottonwood, willow and alder put on half a year's growth. 29 are in the high fire-risk area. The worst stretch is the Hollis Creek bottom, spans 284–291: seven red spans and a dead-top cottonwood at 287. The calendar does not reach this line until October 2027.

Why will span 287 lose its clearance by May?

Span 287 is a black cottonwood on wet creek-bottom soil. It is 6.4 ft from the wire today — above the 6 ft trigger, so a patrol would pass it. It grows toward the wire at 6.4 ft a year, and nearly a fifth of that arrives in May: it crosses 4 ft around 12 May and reaches 3.2 ft on 1 June. Ellen Marsh also found a dead top leaning about 8° toward the line, so it is a hazard-tree removal on the first visit.

What can wait on Marrow Creek?

Almost all of it. L-117 Marrow Creek is on the calendar for March 2027, a full cycle of 18.2 miles at $225,680. No span is forecast inside 6 ft before September 2027 except blackberry on the guy wires at spans 212–214, which Ellen Marsh confirmed on 2 Oct. Spot-trim those three for about $4,100 and defer the cycle to FY2029. Across the network, 11 lines and 152 miles look like this. Deferring needs your approval in the plan.

Build the trim plan from the June red spans

Building it now from the 06:10 forecast: the 37 spans red by 1 June and the 4 hazard trees from patrol notes, grouped by access, priced on the contract rates and sequenced so the six spans already inside 4 ft are cut by 12 November. You approve it before anything goes to a contractor.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The clearance stripLine L-204 as one strip of 412 spans: the canopy under the wire, the 6 ft and 4 ft lines, the fire-risk area, the magnifier, today's red spans and the agents' run log.
The forecast at fire seasonThe slider moved to 1 June 2027: 37 spans inside 4 ft, 29 in the fire-risk area, listed in the order they cross.
One span, today and forecastSpan 287 in side view with today's crown and the June forecast, the clearance and growth figures, why it ranks where it does and the evidence behind each number.
Patrol notes, readForesters' notes and customer reports, each read into line, span, tree, condition, access and urgency, with the words it came from highlighted.
Every line, rankedAll 70 lines ranked by spans inside 4 ft on the forecast date, each with its mini-strip, calendar date and recommendation.
Building the planThe trim plan builder collecting red spans and hazard trees, grouping, pricing and sequencing them before fire season.
The trim planNine work units with span ranges, prescriptions, crew-days, estimates and visit dates, beside the plan totals and the calendar compared with the forecast.
Approve and signThe programme manager signs the plan, with what it approves, what moves to FY2029 and the bid package it releases.
The programme, re-sequencedThe signed plan and the FY2027 programme: off-cycle work on spans that turn red, and cycles deferred where there is nothing to cut.
Bid packagesScope, quantities, specs and access notes for the contractor panel, and three bids compared by unit price with a compliance check.
Verify before paymentEvery claimed span checked against its completion photo, the forester's audit and the next satellite pass, with the invoice reconciled.
ReliabilityTree-caused outages by month, tied to spans, and forecast-planned lines compared with calendar-planned lines per 100 miles.
Your rulesClearances, the forecast, the calendar and deferral rules, and who approves what.
Governance

Signed, cited and on the record — before any crew is sent or any invoice paid.

Every clearance cites its sourceEach clearance, forecast and finding points to where it came from — the LiDAR flight, the satellite pass and its date, the sentence in the patrol note, the outage record.
Named people signThe programme manager approves the trim plan and every deferral before any package goes out. A utility forester confirms each hazard tree and signs the verification. The contracts manager awards and pays.
No span at risk is droppedThe trim plan builder cannot drop a span forecast inside 4 ft before fire season, and deferral is allowed only where no span is forecast inside 6 ft for 12 months.
A second signature for fire-risk linesDeferring a line in the high fire-risk area needs a second signature from the director of wildfire safety and vegetation.
Agents cannot change the rulesNo agent may lower a clearance, award work, approve a payment, close a hazard tree or re-code an outage cause. They measure, forecast, read, match and propose.
Every change on the audit trailRule changes are versioned, and every plan change, signature and contractor upload is recorded with who made it and when.
Configuration

Your vegetation standard, not ours

The clearances, the forecast, the calendar it is compared with and who signs are settings, chosen by the utility. Changes are versioned and on the audit trail.

SettingDefaultChoose from
Minimum clearance4.0 ftSet in feet — inside it a span is red; the state's minimum in fire-risk areas, applied on every line
Trim trigger6 ft6 ft · 5 ft · 8 ft — inside it a span is amber and goes on the next plan
Post-trim clearance12 ft · 15 ft for cottonwood and willow12 ft, 15 ft for cottonwood and willow · 10 ft, 12 ft for fast growers · 15 ft on every species
Fire season starts1 June · work done by 15 May1 June, work done by 15 May · 15 May, work done by 1 May · 1 July, work done by 15 June
Forecast horizon12 months12 months · 6 months · 9 months
Cloud or shadow over a spanOnOn · Off — use the last clear pass and mark the span low confidence; a separate switch sends low-confidence spans to patrol
LiDAR flightsEvery 3 years · next June 2028Every 3 years (next June 2028) · Every 2 years (next June 2027) · Every year — calibrates the satellite canopy height
Cycle the forecast is compared with4 years4 years · 3 years · 5 years
Allow deferralOnOn · Off — only when no span is forecast inside 6 ft for 12 months; a fire-risk line needs the director's signature
Connections

Works with the imagery and records a vegetation programme already has

Satellite imageryevery pass, about weekly — canopy height and change along each line
LiDAR flightsconductor and canopy point clouds that calibrate the satellite heights
Patrol notes and customer reportsforesters' notes, storm patrols, contractor notes, photos and web-form reports
Outage recordssustained outages and cause codes, tied to the span and the fuse
Trim cycle recordsthe span register, last trim dates, the cycle plan and the budget
Contractor completions and invoicesGPS completion photos, unit counts and invoices, checked before payment
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
37 of 37
spans forecast inside 4 ft trimmed before fire season, on the hero line
37 of 37 red spans
done by 24 Feb, deadline 15 May
estimated
$1.88M
of the cycle budget moved from 152 miles with nothing to cut to the spans that turn red
152 of 595 cycle miles
deferred: no span below 6 ft
target
25%
fewer tree-caused outage minutes on lines planned by the forecast
Calendar431,000 min / 100 mi
Forecasttarget −25%

“demo” = seen in the working solution, on its sample utility data · “target” = the design goal, measured in the live solution · “estimated” = our arithmetic, inputs shown ($1.88M = 152 cycle miles × $12,400 a cycle mile, the demo utility's contract rate) · “typical” = published figures (US DOE, Vegetation Management, 2024 — vegetation causes over 20% of US outages; rebuttal testimony in Kentucky PSC case 2025-00114 — $1.21 of cost for every $1 deferred one year). Rules named as context: NERC FAC-003; CPUC GO 95 Rule 35 and D.17-12-024 (at least 4 ft in high fire-threat areas); ANSI A300 Part 7. Lumina Utilities and the people, lines, contractors and records named on this page are fictional — characters and sample data in the working solution.

Questions

What vegetation managers ask us.

What is vegetation management planning software?

Software that decides which spans of an overhead line to trim, when and at what cost. Vegetation Management Planning measures the clearance between trees and the wire on every span, forecasts when each span will lose its clearance, and builds a priced trim plan and bid package from the spans at risk — the vegetation programme manager approves and signs it.

How does risk-based vegetation management work?

Instead of trimming each line when its cycle comes round, the plan starts from the spans forecast inside the 4 ft minimum before fire season and the hazard trees confirmed by a forester. Spans are ranked with the fire-risk area, the customers beyond them and their outage history. Lines with nothing to cut can be deferred, and that budget moves to the spans that turn red.

How does it forecast when trees will reach the power line?

The growth forecaster learns growth toward the wire from three years of satellite passes on spans of the same species and soil, adjusted for the season's rainfall, and calibrated to the last LiDAR flight. It forecasts month by month for up to 12 months, with a confidence band, and sends spans hidden by cloud or shadow to patrol.

Does it replace LiDAR flights and patrols?

No. LiDAR still calibrates the satellite canopy height — every three years in the sample utility — and each satellite pass keeps the measurement current in between. Patrols go where they matter: to low-confidence spans and suspected hazard trees, and foresters confirm every hazard tree.

How does it decide which trim cycles can be deferred?

A cycle can be deferred only where no span is forecast inside 6 ft for 12 months, and only with the programme manager's approval; a line in the fire-risk area needs the director's second signature too. In the sample programme, 152 cycle miles qualified and an estimated $1.88M moved to spans that turn red.

How does it verify contractor tree trimming before payment?

The work verifier matches every completion record to its span and compares it with the forester's audit and the next satellite pass, then reconciles the invoice. Spans short of the post-trim clearance or billed but not worked are held, and a rework order can be sent. The forester signs the verification; the contracts manager pays.

Do people stay in control of the trim plan?

Yes. The agents measure, forecast, read notes, match outages and propose; they cannot lower a clearance, award work, approve a payment, close a hazard tree or re-code an outage cause. Nothing goes to a contractor until the programme manager approves and signs the plan.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your vegetation standard, contract unit rates, span register, imagery and a sample of patrol notes and outage records — and it goes live once every quality gate has passed. We will walk you through it on your own lines first.

See it on
your lines.

We'll run Vegetation Management Planning on a sample of your own lines, imagery and patrol notes.