But I am sorry to tell you that I had already checked that predecessors were finished (Actual Finish Date).
This is a mystery.
I met the pb also today afternoon on one task that was started (without any link, I mean no predecessor and no successor). When we did the progress last month it was OK ; today, I had a similar pb with the Remaining Early Start that had been postponed till Aug 2nd instead of May 1st after scheduling (F9). I noticed this pb as the ETC was wrong.
Primavera schedules activities based on logic. It will not schedule an activity to have an early start until all of the predecessor activities have had time to complete.
When a successor activity is started (with an Actual Start Date) before all of the predecessor activities have completed, then we say that it has started out-of-sequence.
If the out-of-sequence activity has started but not finished as of the data date, P5 (using the Retained Logic CPM setting) will delay the scheduling of the remaining early start until such time as all of the preceding activities have had time to complete. The activity may have been able to start earlier that logic would have allowed but it cannot continue to be progressed until all predecessor work is first complete.
This is correct and normal behavior and that is why you observed the delayed remaining early start dates. I hope that this helps. Good luck!
We have some LOE Activities with Predecessors (Relationships SS for one, and FF for the other one).
All the activities are in Fixed Duration & Units per Time.
On some LOE activities that are already started, in many cases, we have the Remaining Early Start Date of the Resource that is loaded on this activity which is wrong ; as the activity is started, we should have the Remaining Early Start Date of the resource equal to Data Date (or very close to it, depending on Calendar). But in some cases, this Remaining Early Start Date of the resource is starting a few months later.
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 Ronald,
Thanks for your advises.
But I am sorry to tell you that I had already checked that predecessors were finished (Actual Finish Date).
This is a mystery.
I met the pb also today afternoon on one task that was started (without any link, I mean no predecessor and no successor). When we did the progress last month it was OK ; today, I had a similar pb with the Remaining Early Start that had been postponed till Aug 2nd instead of May 1st after scheduling (F9). I noticed this pb as the ETC was wrong.
Hello Fadhel,
Resources Calendar as well as Activity calendar are btoh OK !
I have to find the pb somewhere else.
But thanks for your help.
Primavera schedules activities based on logic. It will not schedule an activity to have an early start until all of the predecessor activities have had time to complete.
When a successor activity is started (with an Actual Start Date) before all of the predecessor activities have completed, then we say that it has started out-of-sequence.
If the out-of-sequence activity has started but not finished as of the data date, P5 (using the Retained Logic CPM setting) will delay the scheduling of the remaining early start until such time as all of the preceding activities have had time to complete. The activity may have been able to start earlier that logic would have allowed but it cannot continue to be progressed until all predecessor work is first complete.
This is correct and normal behavior and that is why you observed the delayed remaining early start dates. I hope that this helps. Good luck!
check the followings:
*Check the resource calendar:Make sure of working day of the resource assigned.
Ronald,
Could you please explain what you mean by "out-of-sequence progress using the Retained Logic CPM setting".
Sorry, I have still a lot to learn...
Do you mean it could be a pb with non-logical link (predecessor dates ?) ; if it is what you think about, I checked this point.
Fadhel,
In response to your question : I am using P3e V5.2, but we do have this problem since P3e V4 at least.
Have you considered out-of-sequence progress using the Retained Logic CPM setting being the cause of the apparent delayed dates?
which version of Primavera EC are you using and SP..??!!
We have some LOE Activities with Predecessors (Relationships SS for one, and FF for the other one).
All the activities are in Fixed Duration & Units per Time.
On some LOE activities that are already started, in many cases, we have the Remaining Early Start Date of the Resource that is loaded on this activity which is wrong ; as the activity is started, we should have the Remaining Early Start Date of the resource equal to Data Date (or very close to it, depending on Calendar). But in some cases, this Remaining Early Start Date of the resource is starting a few months later.
That means that the Workload profile is wrong.
Patricia,
Can you explain a little bit more your question?
Regards,
Ashraf