Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Nov 2, 2026

STORM-SHIFT — Storm restoration orchestration agent

STORM-SHIFT — Storm restoration orchestration agent

Problem: Storm-related outages cost the U.S. billions annually. Legacy SCADA and outage-management systems remain siloed, crews get dispatched on stale damage pictures, mutual-aid coordination is manual (risking roster overlaps), and customer communication is batch SMS blasts sent hours late — while regulatory penalties for poor reliability keep rising. Restoration speed is decided in the first hours, when situational awareness is worst.

Idea: Add a watsonx Orchestrate agent that fuses pre-storm asset baselines (vehicle-mounted inspection data such as Noteworthy AI's grid-intelligence program), real-time storm reports, and outage telemetry into a living damage map; builds restoration queues prioritized by customer criticality; verifies crew certifications on the fly and assembles mutual-aid rosters without overlaps; and produces timestamped, FEMA-ready documentation so eligible disaster-assistance costs do not go unreimbursed. Human dispatchers approve every crew assignment — the agent proposes the plan, people send the trucks.

Value: Restoration moves at the speed of the damage map instead of the rumor mill (the EY–Eversource pattern avoided roughly 40,000 customer outages in two months; KYRO AI users report SAIDI down 20% and SAIFI down 15%), mutual-aid chaos becomes a coordinated roster, and timestamped evidence protects the utility's disaster-assistance claims.

Idea priority Low