The term "Fixed Duration" should be more accurately interpreted as "elapsed duration" - as it spans the entire length of the activity, from start to finish - regardless of any idle-time or task splits. In general, however, he task-types are important when you are applying resources to the activities. A so-called fixed duration task will retain its end-date, even if you work fewer or more hours than planned. It will adjust the remaining hours to spread equally across the remaining duration. In essence, you are correct in that a fixed-duration task assumes no idle time unless you specifically input a split. Once you input a split, you might as well allocate it a fixed-work or fixed- unit attribute.
The fixed-unit and fixed-work task types have different behavioural characteristics when applying resources and re-scheduling uncompleted work - and knowledge is best gained by doing a few experiments. SO Ill let you get on with it, as it is virtually impossible to explain it in words.
Your presumption about task set at "fixed duration" was correct.
But what does this behaviour implies , does it mean if i have task whose duration is fixed , i cannot have idle time for that task . Since splitting will negate the definition of task " Duration " ?
Your task-type is probably set at "Fixed Duration". Double-click on the task, click "Advanced" tab, change the task-type to either "Fixed Work" or "Fixed Units". This will then display the duration in accordance with how many "activity days". Note, however, that all summary-task durations are set at Fixed Duration, so you cannot change those.
When I try what you are doing, my original duration is preserved, regardless of how many times I split the Task, down to 5 x 1 day splits with one day spaces.
Your definition, using "active" days is pretty close.
Splits are pretty much the only exception to the definition of duration as:
the number of working days, according to the calendar for that task, from the start of the task to the finish of the task.
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.
Hi Vinod,
Glad you "fixed" the problem he he he.
The term "Fixed Duration" should be more accurately interpreted as "elapsed duration" - as it spans the entire length of the activity, from start to finish - regardless of any idle-time or task splits. In general, however, he task-types are important when you are applying resources to the activities. A so-called fixed duration task will retain its end-date, even if you work fewer or more hours than planned. It will adjust the remaining hours to spread equally across the remaining duration. In essence, you are correct in that a fixed-duration task assumes no idle time unless you specifically input a split. Once you input a split, you might as well allocate it a fixed-work or fixed- unit attribute.
The fixed-unit and fixed-work task types have different behavioural characteristics when applying resources and re-scheduling uncompleted work - and knowledge is best gained by doing a few experiments. SO Ill let you get on with it, as it is virtually impossible to explain it in words.
Cheers.
James.
Hi James ,
Your presumption about task set at "fixed duration" was correct.
But what does this behaviour implies , does it mean if i have task whose duration is fixed , i cannot have idle time for that task . Since splitting will negate the definition of task " Duration " ?
Or is there some other angle to it ?
thanks,
regards,
vinod
Hi Vinod,
Your task-type is probably set at "Fixed Duration". Double-click on the task, click "Advanced" tab, change the task-type to either "Fixed Work" or "Fixed Units". This will then display the duration in accordance with how many "activity days". Note, however, that all summary-task durations are set at Fixed Duration, so you cannot change those.
HTH
James.
When I try what you are doing, my original duration is preserved, regardless of how many times I split the Task, down to 5 x 1 day splits with one day spaces.
Your definition, using "active" days is pretty close.
Splits are pretty much the only exception to the definition of duration as:
the number of working days, according to the calendar for that task, from the start of the task to the finish of the task.
Check your calendar for the task.