There is a "must finish" date in the project overview, but I think you’re talking about activity level constraints, right? In which case I assume you mean Mandatory start / finish constraints
My mentor (the bloke who taught me P3) described the use of Mandatory dates as akin to swearing in church, by which I assume he meant blasphemy. They circumvent the logic in your plan. I don’t use them.
Ive just reread your post and realise that I probably misinterpreted what youre after. the above still stands but I think you mean the Early Finish and Must finish dates in the project overview?
If so, then what the 2 previous posters say is accurate. The Early Finish date is the last Early Finish date that appears on any of the activities in your project. This is calcualted by the schedule and so you cant set it. You can set a Project Must Finish by date. Setting a "Project Must Finish by" date effectively puts a "Late Finish" constraint on whatever activity has the latest Early Finish on your project. If you have an activity with an Early finish date that is later than your stated "Project Must finish by" date then a path of negative float will be generated, showing that teh analysis says you cannot finish your project on time. Personally, I have only found this useful for very simple plans. Much better is to build a high level plan, above your detailed plan, which contains your completion milestones fro each phase, work area, etc. Then you can set late finish constraints on these milestones. That way each of them will generate a negative float path if their finish dates are under threat, you will also get more detailed float information for embedded activities, where you will see teh float on that activity before it affects the relevant milestone (or the nearest one, if it attached to many of them).
The "Must finish date" can be the contract completion date when establishing a baseline, but for analysis purpose it is better to remove this constraint.
Early Finish date is generated by Time-Analysing the Schedule and signifies the earliest date you can finish a schedule. Must Finish defines Mandatory date or a constraint that the Project must end by. Must finish date can be the Contract Completion Date, if you own the Program Float.
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.
There is a "must finish" date in the project overview, but I think you’re talking about activity level constraints, right? In which case I assume you mean Mandatory start / finish constraints
My mentor (the bloke who taught me P3) described the use of Mandatory dates as akin to swearing in church, by which I assume he meant blasphemy. They circumvent the logic in your plan. I don’t use them.
Ive just reread your post and realise that I probably misinterpreted what youre after. the above still stands but I think you mean the Early Finish and Must finish dates in the project overview?
If so, then what the 2 previous posters say is accurate. The Early Finish date is the last Early Finish date that appears on any of the activities in your project. This is calcualted by the schedule and so you cant set it. You can set a Project Must Finish by date. Setting a "Project Must Finish by" date effectively puts a "Late Finish" constraint on whatever activity has the latest Early Finish on your project. If you have an activity with an Early finish date that is later than your stated "Project Must finish by" date then a path of negative float will be generated, showing that teh analysis says you cannot finish your project on time. Personally, I have only found this useful for very simple plans. Much better is to build a high level plan, above your detailed plan, which contains your completion milestones fro each phase, work area, etc. Then you can set late finish constraints on these milestones. That way each of them will generate a negative float path if their finish dates are under threat, you will also get more detailed float information for embedded activities, where you will see teh float on that activity before it affects the relevant milestone (or the nearest one, if it attached to many of them).
Kevin
The "Must finish date" can be the contract completion date when establishing a baseline, but for analysis purpose it is better to remove this constraint.
Early Finish date is generated by Time-Analysing the Schedule and signifies the earliest date you can finish a schedule. Must Finish defines Mandatory date or a constraint that the Project must end by. Must finish date can be the Contract Completion Date, if you own the Program Float.