As Dieter said, you can easily filter on activities with EF in the past (I use : "EF is less than Data Date").
When you use EF, be careful not using FF relationships. In that case, it doesnt work very well (if you are not logical and you have conflictual dates). In some cases, EF is then ignored.
Expected finish is a constraint as it was in P3. In my opinion its independent from retained logic or progress override if EF is taken into account. It just depends on the parameter "Use...".
If youll update with expected finish, another item might be dangereous if you use activities longer than two periods. You might forget it, but P6 doesnt. Just display it in a column and check or by filter (exp f not equal to "").
For many people its easier to say Ill finish the... than Ill need this many days - for my experience.
Having time to search what has been written regarding “Expected finish”, I realized about two different things;
Expected finish as part of constraints: In P6.2 we have Finish On (3 types) or mandatory finish
Expected finis as part of Status.
For the latter, the schedule option needs to be modified to the following: Use expected finish and progress override.
I would recommend expected finish as part of status ONLY for procurement activities such as “ fab/delibery”. This activity normally has a duration of more than one reported period.
By doing this, I need to change the schedule option.
It seems that I will have a schedule with two schedules options. One portion with RDU and only the procurement activities with expected finish.
Conclusion: Better to update with actual dates and remaining durations.
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.
Hello Dieter and Carmen,
I am using Expected Finish dates.
As Dieter said, you can easily filter on activities with EF in the past (I use : "EF is less than Data Date").
When you use EF, be careful not using FF relationships. In that case, it doesnt work very well (if you are not logical and you have conflictual dates). In some cases, EF is then ignored.
Kindest regards.
Patricia
Carmen
Expected finish is a constraint as it was in P3. In my opinion its independent from retained logic or progress override if EF is taken into account. It just depends on the parameter "Use...".
If youll update with expected finish, another item might be dangereous if you use activities longer than two periods. You might forget it, but P6 doesnt. Just display it in a column and check or by filter (exp f not equal to "").
For many people its easier to say Ill finish the... than Ill need this many days - for my experience.
Regards
Dieter
Dieter,
Having time to search what has been written regarding “Expected finish”, I realized about two different things;
Expected finish as part of constraints: In P6.2 we have Finish On (3 types) or mandatory finish
Expected finis as part of Status.
For the latter, the schedule option needs to be modified to the following: Use expected finish and progress override.
I would recommend expected finish as part of status ONLY for procurement activities such as “ fab/delibery”. This activity normally has a duration of more than one reported period.
By doing this, I need to change the schedule option.
It seems that I will have a schedule with two schedules options. One portion with RDU and only the procurement activities with expected finish.
Conclusion: Better to update with actual dates and remaining durations.
Cheers,
Dear Dieter,
Thanks for your quick answer. It came just on time.
Regarding Schedule options, I have set up them as follow:
1)Tab GENERAL : ON: Use expected finish
2)When scheduling progressed activities use : Progress override
3)Start to start lag from : early START
Apparently is doing OK.
Let me finish with my update and issue today and I would like to share with you, when to use expected finish as part of updating method.
Have a nice day,
Ciao, Carmen
Dear Carmen
I didnt realize those surprises up to now.
In using "Expected Finish" those items I found to be regarded:
1. Scheduling options: Must be switched on
2. If EF hits a date which is "nonwork" in your calendar, it will be transferred to the next working day.
3. Early or Actual Start > Expected Finish: EF will be ignored.
Maybe youll explain more in detail those inconsistencies.
Regards from Germany
Dieter