Features

Everything Canopy Commander does on a wire job.

Built around one question your crew asks on every storm callout: which tree is loading this line the hardest, and what comes off first?

Sector 14B · Primary line

Removal priority

Loaded
  • T-04Red oak, split leader
    3,410 lbf
    Priority 1
  • T-07Silver maple, uprooted
    2,640 lbf
    Priority 2
  • T-02White pine, leaning
    1,630 lbf
    Standby
  • T-11Ash, limb contact
    670 lbf
    Hold
Estimated from field inputs · verify before cutting

Ranking engine

Force on the wire, tree by tree

Canopy Commander estimates the load each contacting stem transfers to the conductor from lean, contact height, stem size, and failure type. Instead of a single abstract number, you get a ranked list you can act on: which tree is doing the damage, and by how much compared to the next one down.

  • Per-tree estimated force with a relative load bar
  • Highest-priority removal flagged in high-vis orange
  • Sequence warns when releasing one stem reloads another

Field input

Measurements you can actually take at 2 a.m.

Every input is something a climber or ground worker can estimate from the truck in under a minute. No survey gear, no engineering tables, no typing paragraphs into a phone in the rain.

  • Preset failure types: uprooted, split leader, limb contact, full lean
  • Slider and stepper inputs sized for gloves
  • Duplicate a tree entry when a span has similar failures

Reliability

Works where the signal doesn't

Storm work happens on back roads with no bars. Entries are captured on device and sync when service returns, so a dead zone never costs you a job record.

  • Local capture with background sync
  • High-contrast display for headlamp and daylight use
  • Nothing to load before you can start entering trees

Crew

One plan, everyone on it

The ranked cut order goes to the ground crew and the foreman as a plain, readable summary, so the plan in the bucket is the same plan on the ground.

  • Shareable span summary with ranking and notes
  • Notes attach to the tree, not a separate log
  • Foreman view of open spans across a callout

Records

Job history the utility will accept

Every span keeps its inputs, ranking, and time stamps, so post-storm reporting is a lookup instead of a reconstruction.

  • Span, circuit, and pole reference on each record
  • Timestamped entries for restoration reporting
  • Export a callout's spans as a single summary

Want to see it on your span?

Request a demo