Application guide

Candidate use cases

19 candidate event families, plus operating uses and important blind spots. This is an application map, not a list of validated automatic cause-detection capabilities.

Start with measurable motion

Start with measurable motion. SmartPole measures tilt, sway and shock. A movement alert can direct attention to a pole; an image or inspection helps establish why it moved.

Every event family below is a candidate application. Detection, nuisance response and cause identification are validated for each site, structure and mounting before anyone relies on them. Hypothetical use cases are listed separately.

Core value · events 01 to 12

Core use cases: when a pole moves

Events that move the monitored pole: what SmartPole indicates, and what still needs review. Sensitivity, mounting and cause identification are validated for each site.

  1. 01

    Vehicle hits pole

    Car, truck or other vehicle impact: shock followed by sway or a lasting tilt change. Confirm the cause with an image or inspection.

  2. 02

    Vehicle catches a line

    A raised truck body, crane or tall load pulls a span: monitor movement transmitted to its supporting poles. Does not confirm electrical contact.

  3. 03

    Equipment impact

    Construction or agricultural equipment contacts the pole or its support: shock or tilt can prompt review. Not an automatic equipment classifier.

  4. 04

    Tree falls on pole

    Direct tree or large-limb impact can produce shock and lean. A camera view may show the cause if the incident is visible.

  5. 05

    Tree falls on line

    A tree or limb loads a span: look for transmitted pole movement. Contact without sufficient pole motion may not trigger a sensor.

  6. 06

    Wind / storm movement

    Monitor unusually large sway, a tilt change or a lean remaining after a storm. Site limits must account for normal wind movement.

  7. 07

    Foundation / soil movement

    Settlement, loose backfill, erosion or washout may change pole orientation. Movement does not identify the underlying soil condition.

  8. 08

    Landslide / seismic effects

    Track tilt or shock experienced by the monitored pole. A landslide indicator or earthquake-response aid, not a hazard prediction system.

  9. 09

    Pole leaning / fracture

    Track progressive lean or abrupt rotation associated with structural damage. A destroyed node or radio link may prevent a live alert.

  10. 10

    Conductor galloping

    Large line oscillations may reach a support. Pole sensing is indirect; compare with a conductor sensor or video before making a claim.

  11. 11

    Line slapping / clashing

    A possible repeated-shock or sway indicator, only if enough motion reaches the pole. It does not establish conductor contact, arcing or an electrical fault.

  12. 12

    Construction / traffic vibration

    Nearby work, heavy traffic or maintenance can be useful context and nuisance-test cases. Motion is not automatically damage or an emergency.

Best initial demonstrations: controlled impacts, imposed tilt changes, support-tension changes and storm-like sway on a safe, de-energized test structure. Each event still needs detection and nuisance-response testing.

Events 13 to 19

Hypothetical use cases

Engineering hypotheses that may produce a useful signal but still need first evidence. Sensitivity, mounting, mechanical coupling and cause identification require separate validation before anyone relies on them.

  1. 13

    Guy-wire / anchor failure

    A snapped, loosened or damaged guy wire, or a moving anchor, may change pole lean or sway. This is not a direct tension measurement.

  2. 14

    Broken / dropped conductor

    A sudden tension change may move the pole. A downed line can also occur with little sensor motion; a quiet sensor cannot prove safety.

  3. 15

    Ice / snow loading

    Loading, shedding or breakage may change lean or motion. Does not directly measure ice thickness, line sag or conductor load.

  4. 16

    Loose crossarm / hardware

    Changed vibration may justify checking crossarms, insulators, clamps or fasteners. Cannot identify the faulty part from pole motion alone.

  5. 17

    Tampering / climbing

    Cutting, climbing, striking or moving a sensor may create motion. Cannot distinguish malicious acts from authorized work without context.

  6. 18

    Decay / termites / corrosion

    A changed mechanical response could flag a structure for inspection. It is not a direct decay, corrosion, remaining-strength or lifespan measurement.

  7. 19

    Fire-related structural movement

    Movement after thermal damage is a possible use case, not fire detection by the motion node. Camera fire and smoke functions are separate.

Conductor-motion caution: small or fast vibration may not be adequately captured at the pole-mounted sensor. Test the actual mounting and acquisition chain before relying on detection or classification.

Operating uses and customers

Where SmartPole fits

The customer outcome is better-informed review and response, not automatic electrical protection or a declaration that a structure is safe.

Operating uses

  • Remote monitoring without LTE (SmartPole Mesh, coming soon)
  • Direct-LTE sites (LTE)
  • Mixed networks with optional alert backup
  • Post-storm inspection triage
  • Review after a reported vehicle or tree strike
  • Post-repair movement history
  • Prioritizing inspection of recurring-motion poles
  • Shared Sentinel hub area imagery

The last five are proposed workflows built on SmartPole's sensing, history and visual capabilities.

Potential customers and assets

  • Electric utilities and cooperatives
  • Telecom pole owners
  • Municipal light standards and suitable masts
  • Private industrial or campus pole networks

These are candidate applications; installation and suitability are checked for each asset.

Demonstration limits

  • The event-to-alert animation is illustrative, not measured latency or field evidence.
  • Waveform upload requires cellular service at the recording sensor.
  • Shared LTE backup in a mesh carries alerts only.
  • Images depend on camera placement and visibility.

Validation before a customer claim

  • Compare known events with ground truth.
  • Vary sensor height and pole type.
  • Include normal wind, traffic and maintenance.
  • Test outages and restored links.
  • Measure missed detections, nuisance alerts and delivery time.

Physical tests run only in a suitably controlled, de-energized setting.

Have an application in mind?

We will help you scope a validation plan for your structures and sites.