IBM Sustainability Software - Ideas Portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.
Can we add functionality where the labor rate holds the previous rate/craft/skill level allowed on the contract. to allow for current rates to be used until the labor rate contract changes become effective ? This would also allow reporting actuals for prior periods when a discrepancy/ late submission etc...
Right now we have to use a bad workaround of creating additional labor records and swap them out when there is a contract renewal/revision that change the available types of labor (labor/Craft/Skill/ rates) availability as well as needing to coordinate the cutover date and ensure all actuals are reported before we can update the contract.
There is an existing work-around for this issue:
When revising a contract and changing the status of the new revision to APPR, the LABORVIEWCHGSTAT.STATDATE can be set in the future (e.g. the first day of next month at midnight), this will provide the functionality described in this idea. But it's a quite hidden feature, so it might be a better idea to make this more intuitive, as an action under more actions instead.