Skip to Main Content
Update: This Suggestion Box has been migrated to The Network, Trimble's online user community and is now read-only. Please click the link to add a new idea, vote, or comment.
Created by Guest
Created on May 19, 2021

Budget Allocation for Covering Negative Over/Under Needs UX Improvement

Issue: Currently in ProjectSight budget, when there is line showing a loss, in the Projected Over/Under column, you have to review the transactions to determine if the loss is from overusing Uncommitted Cost (by contract or by Use Uncommitted Cost (pending)) or if it's due to a Pending Commitment allocation. To cover the loss from a different line item, overuse from Uncommitted Cost requires a different cost allocation (Uncommitted Cost) than a pending allocation (No Allocation).

Enhancement: Have a way for users to instantly see where the loss is coming from and what Cost Allocation is needed in this situation. Ideally, all Budget Transaction columns should have a way to see the full calculation leading to its current value, either via tooltip or informational screen. This also should be easily viewable from the PCO screen so users do not have to browse back and forth between pages or browser tabs to confirm what is needed.

  • Attach files