The value for Duration is a derived number (it’s the difference between Start and Finish) so you can’t set up a formula to force it to something else.
As a workaround, you could do this: Let’s assume that the duration is the product of two factors: Coats of paint (1, 2, or 3); and Number of Widgets. And let’s assume that these are *big* widgets and it takes a day to apply a coat of paint (which can dry overnight).
So the duration for 10 widgets would be 10 days (if they get just 1 coat of paint), 20 days (if they get 2 coats) and 30 days (if they get three coats).
Display the task columns Number1 and Number2. In column 1 put the number of coats of paint; in column 2 put the number of widgets.
Display the column Duration1. Give it the formula:
[Number1]*[Number2]*[Minutes Per Day]
You need [Minutes Per Day] because project stores durations in minutes.
Finally, you need to move "Duration1" into "Duration" and for that you’ll need a little VBA:
sub DurationOverride()
dim tsk as Task
for each tsk in activeproject.tasks
If not tsk is nothing then ’ignore blank lines
if not tsk.summary then ’ignore summary tasks
if tsk.duration1 > 0 then ’update tasks that have a calculated value
tsk.duration = tsk.duration1
end if
end if
end if
next
Note that if you have tasks with a FNLT, FNET, MFO Constraint type then the Start Date will move to an earlier date (the Finish date is locked and won’t move).
Note that if you have predecessors/successors on the task where you have calculated the Duration then Project will impose those constraints on the task Start/Finish as well.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
The value for Duration is a derived number (it’s the difference between Start and Finish) so you can’t set up a formula to force it to something else.
As a workaround, you could do this: Let’s assume that the duration is the product of two factors: Coats of paint (1, 2, or 3); and Number of Widgets. And let’s assume that these are *big* widgets and it takes a day to apply a coat of paint (which can dry overnight).
So the duration for 10 widgets would be 10 days (if they get just 1 coat of paint), 20 days (if they get 2 coats) and 30 days (if they get three coats).
Display the task columns Number1 and Number2. In column 1 put the number of coats of paint; in column 2 put the number of widgets.
Display the column Duration1. Give it the formula:
[Number1]*[Number2]*[Minutes Per Day]
You need [Minutes Per Day] because project stores durations in minutes.
Finally, you need to move "Duration1" into "Duration" and for that you’ll need a little VBA:
sub DurationOverride()
dim tsk as Task
for each tsk in activeproject.tasks
If not tsk is nothing then ’ignore blank lines
if not tsk.summary then ’ignore summary tasks
if tsk.duration1 > 0 then ’update tasks that have a calculated value
tsk.duration = tsk.duration1
end if
end if
end if
next
Note that if you have tasks with a FNLT, FNET, MFO Constraint type then the Start Date will move to an earlier date (the Finish date is locked and won’t move).
Note that if you have predecessors/successors on the task where you have calculated the Duration then Project will impose those constraints on the task Start/Finish as well.