Backend
Operator-in-the-Loop Rolling Dispatch for Damage-Assessment Crews Under Partial Storm Information
arXiv cs.SY0 views
arXiv:2512.20719v2 Announce Type: replace Abstract: Natural disasters often inflict severe damage on distribution grids. Rapid, reliable damage assessment (DA) is essential for storm restoration, yet most optimization work targets repair dispatch after faults are identified. This paper presents a production, rolling horizon DA crew allocation system deployed across multiple U.S. states in Eversource Energy's service territory and used during live storms. The method implements a sequential k-job assignment policy per available crew, executed on a fixed cadence and on operators' control. The objective jointly prioritizes critical facilities and customer impact while controlling travel time on the actual road network via the Google Maps API. A key constraint is the absence of live crew GPS; we infer crew locations from the last confirmed DA site and robustify travel estimates for staleness, yielding stable recommendations without continuous tracking. The operator remains in the loop with controls to limit churn and to publish a feasible plan. Using data from the March 7 New Hampshire storm with 90 moderate outages and seven DA crews, we observe shorter time to first assessment, fewer revisits with reduced distance traveled. To our knowledge, this is among the first multi-state enterprise integrated deployments to treat DA crews as a first-class optimized resource in storm restoration.
Source:https://arxiv.org/abs/2512.20719PreviousPrivacy-Preserving Fully Distributed Gaussian Process RegressionNextThe BAR-SOT Method: Long-term Average Cost Control as Stochastic Optimal Self-Transport
Related posts
I Had a Perfect Sprint Board. 18 AI Subagents Still Wrecked the Repo.
0dev.to GitHub
What Is Attribution? AI Music Needs a Trail Back to the People Who Made the Work
0dev.to News
A Free Google Alerts Alternative: Monitoring Global News With the GDELT DOC API
0dev.to News
Butter Scraped Over Too Much Bread
0dev.to Discuss
From Six Seven to Six Zeros to What Next?
0dev.to Discuss
When a document assistant refuses: quota, context, and the missing model call
0dev.to C#