Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
From a holistic view of the system, our organization publishes Forecast data to the development environment every night. That process causes frequent changes to Bill of IT & Cost Source Master data. Other daily data activities—such as importing and exporting TCO, consumption, and budgeting data are also performed in development because these inputs change within the month. The production environment contains a locked, month-end view that reflects the completed book-close activities. We only push to production after month-end book-close is finished, and we do not edit month data once it has been published.
Because of how we manage data, many nightly processes depend on each other. We use datalinks within the same project/branch to move data (for example, from the current month to the prior month, or from reports to table unpivots). These dependent builds require precise timing: jobs must run in a specific order and must not overlap. Scheduling therefore consumes most of our evening and overnight window. If a calculation overlaps with a subsequent datalink job, it can create data-integrity issues that require re-running the jobs, costing significant labor and delaying delivery to users.
When we migrated from classic Datalink to the newer datalink platform, we appreciated the Schedule Run by Event feature because it addresses many scheduling problems. However, during testing we found event-based triggers only worked with staging calculations, not development. Because our data flows from Development to Staging and our staging calculations require much longer processing time, the current behavior is insufficient. For our organization to expand data usage in Apptio, the Schedule Run by Event capability must support triggering on Development calculations as well.