IBM Data Platform Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
Request
Verizon needs the ability to rename watsonx Orchestrate instances deployed in an on-prem environment.
Business Justification
Enterprise customers often need instance names to align with environment, business unit, application, support, security, audit, or governance naming standards. Over time, instance names may become outdated due to organizational changes, environment changes, project ownership changes, or evolving deployment standards.
For a large enterprise like Verizon, instance names are not cosmetic. They are often referenced in operational runbooks, monitoring tools, internal documentation, support processes, audit artifacts, and cross-team communications.
Impact if Not Delivered
If Verizon cannot rename wxO instances after deployment, they may be forced to keep inaccurate or misleading instance names, rebuild or redeploy instances, or maintain manual mappings outside the platform.
This creates unnecessary operational friction, increases the risk of support confusion, and may make long-term environment management harder as adoption scales.
Business Value if Delivered
Providing the ability to rename wxO instances would improve lifecycle management, reduce administrative overhead, support cleaner governance, and make the platform easier to operate in a large enterprise environment.
This would also reduce the need for disruptive redeployments or manual tracking processes when naming standards change.
Client is using watsonx Orchestrate on-prem deployment.
Thank you for your feedback, can you clarify what you refer to as "assistant instances"?
Agents and assistants can be renamed from within their respective builders, are you referring to the wxO SaaS tenants you see at https://dl.watson-orchestrate.ibm.com/landing/accounts (that is for AWS)?