May be this problem is similar to a problem that I have met in Primavera project Planner.
the problem was: the Late Finish date is changed,
from my Experience the Late finish date should not change because this is your limit.
I discover after a while that this problem they have named it in primavera "Out of sequence problem".
Out of sequence can be happen if you update the progress not according to the relation you give(linking the activities).
How?
If an activity A is a predessor of B and linked by a Finish-Start relation(F.S).
And you update the Activity B(give actual date),before the Activity A Finish , you will find after sheduling that the Late finish has been changed ,inspite that it should be fixed.
To solve this problem , you should update according to the relations given, other wise change the link to reflict the actual situation of the Project.
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,
May be this problem is similar to a problem that I have met in Primavera project Planner.
the problem was: the Late Finish date is changed,
from my Experience the Late finish date should not change because this is your limit.
I discover after a while that this problem they have named it in primavera "Out of sequence problem".
Out of sequence can be happen if you update the progress not according to the relation you give(linking the activities).
How?
If an activity A is a predessor of B and linked by a Finish-Start relation(F.S).
And you update the Activity B(give actual date),before the Activity A Finish , you will find after sheduling that the Late finish has been changed ,inspite that it should be fixed.
To solve this problem , you should update according to the relations given, other wise change the link to reflict the actual situation of the Project.
Best Luck
Ali
-------------------------------
Additional investigation has led to the following observations:
1. Late dates and Total Slack (Total Float) calculate properly for activities that are "to-go".
2. Late Finish dates and TS calculate properly for in-progress tasks that are not "critical".
3. The "bad" dates and "bad" TS only show-up when the path hits a critical condition.