MLGW transforms utilities operations with Samsara AI Dash Cams and GPS, reducing preventable vehicle collisions by 20%
MLGW experienced a dramatic surge in storm-induced outages and lacked real-time visibility into crew locations to restore service quickly. They also needed a proactive way to coach drivers and exonerate employees from false claims in order to minimize safety-related costs and keep utility rates low.
source quote
source quote
source quote
source quote
source quote
source quote
source quote
Samsara reduced preventable vehicle collisions by 20%, achieved a 100% reduction in safety events using In-Cab Nudges, accelerated service restoration by deconflicting crew resources, and recovered thousands of dollars in missing assets—enabling MLGW to keep utility rates low.
Compare to your context
Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.
Frequently asked questions
What did this team achieve with this AI workflow?
Samsara reduced preventable vehicle collisions by 20%, achieved a 100% reduction in safety events using In-Cab Nudges, accelerated service restoration by deconflicting crew resources, and recovered thousands of dollar…
What tools did this team use?
Samsara Connected Operations Cloud, AI Dash Cams, Proactive Coaching, In-Cab Nudges, Samsara Safety Scores, ArcGIS.
What results were reported?
Preventable vehicle collisions: 20%; safety events using In-Cab Nudges: 100%; Recovered asset value: thousands of dollars in lost assets; Service restoration speed: get power back on more quickly (source-reported, not independently verified).
How is this field service AI workflow structured?
AI Dash Cams detect risky events → In-Cab Nudges coach drivers → Video retrieval for exoneration → ArcGIS integration for crew visibility → GPS-based crew dispatch → Safety Scores drive engagement → GPS asset recovery.
Related field service cases
Now compare it to your context
This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.