We have recently started using the planned cost function in Workfront. Previously we managed our costs by managing labor hours (planned hours) but with the increase in leveraging software or off/nearshoring we had to get more mature in using planned cost.
We set some tasks at a 0-day duration with an "ASAP" constraint to make sure they are done on the same day as their predecessor but are also connected and moving with the predecessor during project adjustments, but that 0day duration zeroes out planned costs.
I GET that a task cannot actually have a 0-day duration, but is there an alternate solution to have a task after a predecessor due on the same day AND will move out if you move the preceding task? My best idea so far is to use a duration in the increment of hours so that I can keep "ASAP as the task constraint and have it trigger immediately.
Views
Replies
Total Likes
The duration of the task shouldn't impact your planned labor cost. Do you have hours in the task for the assignments?
The Task Planned Labor Cost is calculated based on the following:
Planned Labor Cost of a project:
Project Planned Labor Cost= SUM(Tasks Planned Labor Cost)
Planned Labor Cost of a task:
Task Planned Cost = Planned Hours x User or Job Role Cost Per Hour
Views
Replies
Total Likes
Do I have to change a setting?
Here is the exact same task when I switch to a 0 day duration, planned cost updates to $0.
this all rolls up to the project cost, creating incorrect projected costs for any task set to 0 day duration
Views
Replies
Total Likes
Just thinking out loud here. Would it work to change that predecessor to "task number minus 1" -- so if you are looking at tasks 6 and 7, make task 7's predecessor "6-1". This way you can leave your duration on task 7 as 1. But then it should finish the same time as task 6.
I don't know what it does for notifications though.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies