when the new Project starts Planner starts making new schedule for the project before it will start. as the schedule finish it will be set as Baseline, and during the project, you will make updates against this baseline, it will allow you to see the diffenrences between the planned and actual works(start, finish, duration times).
Milestone is essetially is the borders between phases and/or time to be highlighted, or decision making stage(go/no go), comissioning start and etc. its essential to have no less no more milestones, they should be reasonable identified. for instance: start date for mobilisation, finish date for structural works, finishing procurement of materials, start date for facade works, comissiong start, and etc. Milestone have no duration.
The advantages of mile stone a lot but some are given as per my experience.
1- It give just in one sentence the current progress of project/phase / unit / discipline etc. Such as Mechanical completion Mile stone
2- Higher management don’t want to be involved in figures and they don’t have enough time always. Then only the intermediate mile stone represent the true picture of project at a glance.
3- In some contracts specially Lump sum the invoice link with the mile stones not actual running progress. For example at one EPC project the procurement payment will be release on the following milestone achieving such as Issue RFQ , Issue P.O, Delivery at site etc, rather then your running progress issue RFQ 50%, issue PO 25%.
4- Also for delay analysis midterm mile stones play vital roles. Easy to understand at different stages project has how much ahead / behind the schedule.
this is to show emphasis or importance on this dates.........this is sometimes where you measure you performance.....lets face it the clients doesnt know primavera...... and sometimes they would just ask for the variance of milestone dates...... and thats it they would have the big picture.......
BASELINE is where you measure your work......baseline is also like a milestone in which you could compare your present performace can be conotated also as target......
We also have specific milestones for agreeded dates between high directory from client and contractor. This milestones has constraints because this important dates can not be change.
In the specific case fo the project im actualy working, i have many milestones becouse client wants to see all mainly deliverables as milestones and we send reports showing only this milestones.
What are the advantages adn dis advantages of using many milestones in the programme and what are the differences between a milesone with constraint anda milesone without constraint.
Imagine in you project important actions you need from your client - these actions have to be ready/started/complete in a certain date but is not up to you to plan what
/how your client does his own work.
Site take over by contractor.
Water supply available from client,
Power supply available,
Plant construction licenced
Enviromente licence issued.
supply XXXX
Contract and supply fuel gas.
Grid available to export power.
Et, etc.
These are some typical examples of milestones that normaly are in the scope of Project owner/Client.
Of course they are also normaly linked with actions from you (predecessors) - Eng. submittal, effluent data, Consummer lists for power, etc.
As successors to the milestones you have to add your next activities.
By doing this you show clearly to yourclient exactly what are the impacts if his milestones are not complished in time - avoiding a lot of discussions in the future.
But its up to your client to plan his actions, mobilize his ressources, forward his part of documents, etc,
We show to the client where we need his actions started/finished but we do not plan his own work/actions.
Milestones - as the name sais are important phases of your project where a certain event needs to be complete, started, etc.
Baselines - We must not forget that the plan of a certain project is a contractual document (normaly approved by client). Once client approves it then it should be frozen (no changes allowed) and copy into a diferrent name. This contractual baseline normaly can only change with the approval of the client.
Number of baselines - depends on your strategie to control the project: U might want to use previous months status as baseline to compair with achievments (earned value, etc) by the end of next months.
In general a big change in the project causing the previous baseline not anymore executable normaly requires a revision of strategie/ project execution plan/ etc and therefore a new baseline should be created.
I Hope to have contributed for your clarification.
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 Peter,
when the new Project starts Planner starts making new schedule for the project before it will start. as the schedule finish it will be set as Baseline, and during the project, you will make updates against this baseline, it will allow you to see the diffenrences between the planned and actual works(start, finish, duration times).
Milestone is essetially is the borders between phases and/or time to be highlighted, or decision making stage(go/no go), comissioning start and etc. its essential to have no less no more milestones, they should be reasonable identified. for instance: start date for mobilisation, finish date for structural works, finishing procurement of materials, start date for facade works, comissiong start, and etc. Milestone have no duration.
Regards,
Ismayil
Hi Yannick
Welcome to Planning Planet
You have just replied to a thread that is 5 years old.
It is not good practice to liven up long dead topics.
Best regards
Mike Testro
To ashraf alawady:
If you put constraint on a milestone, you may loose your critical path. It is the same effect when you impose start or end date to an activity.
Regards,
Dear Ashraf
The advantages of mile stone a lot but some are given as per my experience.
1- It give just in one sentence the current progress of project/phase / unit / discipline etc. Such as Mechanical completion Mile stone
2- Higher management don’t want to be involved in figures and they don’t have enough time always. Then only the intermediate mile stone represent the true picture of project at a glance.
3- In some contracts specially Lump sum the invoice link with the mile stones not actual running progress. For example at one EPC project the procurement payment will be release on the following milestone achieving such as Issue RFQ , Issue P.O, Delivery at site etc, rather then your running progress issue RFQ 50%, issue PO 25%.
4- Also for delay analysis midterm mile stones play vital roles. Easy to understand at different stages project has how much ahead / behind the schedule.
Regards
Tahir
hi guys!
for me .....
MILESTONE dates are usually contract dates....
this is to show emphasis or importance on this dates.........this is sometimes where you measure you performance.....lets face it the clients doesnt know primavera...... and sometimes they would just ask for the variance of milestone dates...... and thats it they would have the big picture.......
BASELINE is where you measure your work......baseline is also like a milestone in which you could compare your present performace can be conotated also as target......
c",)
We also have specific milestones for agreeded dates between high directory from client and contractor. This milestones has constraints because this important dates can not be change.
Regards.
In the specific case fo the project im actualy working, i have many milestones becouse client wants to see all mainly deliverables as milestones and we send reports showing only this milestones.
Regards.
Hi,
What are the advantages adn dis advantages of using many milestones in the programme and what are the differences between a milesone with constraint anda milesone without constraint.
Thanks all!
U can also have many milestones in a contract - all mainly deliverables.
Regards.
Hi Ashraf,
Ilustrating my explanation of milestones:
Imagine in you project important actions you need from your client - these actions have to be ready/started/complete in a certain date but is not up to you to plan what
/how your client does his own work.
Site take over by contractor.
Water supply available from client,
Power supply available,
Plant construction licenced
Enviromente licence issued.
supply XXXX
Contract and supply fuel gas.
Grid available to export power.
Et, etc.
These are some typical examples of milestones that normaly are in the scope of Project owner/Client.
Of course they are also normaly linked with actions from you (predecessors) - Eng. submittal, effluent data, Consummer lists for power, etc.
As successors to the milestones you have to add your next activities.
By doing this you show clearly to yourclient exactly what are the impacts if his milestones are not complished in time - avoiding a lot of discussions in the future.
But its up to your client to plan his actions, mobilize his ressources, forward his part of documents, etc,
We show to the client where we need his actions started/finished but we do not plan his own work/actions.
Hope to have contributed to clarify/help.
BR
JMFrade
hI
ahraf
your contractor is very nice to you that he is giving you
the intermediate milestones.
Intermediate milestone are helpfull in controlling the different phase of the project
but all of you milstone must be in consistance with your contract
Hi,Jose
Normally in any contract we have two contractual milestone
staring date milestone for project starting date and finishing date milestone for project completion date .
If the contractor show in the baseline programme many other
milestones which created by the contractor him self .
Can i reject the contractor proposal to use more milestones
,what are the reasons and what is the effect on the programme if we used more milestones.
Thanks Jose! Good points and very clear.
Hello Peter,
Milestones - as the name sais are important phases of your project where a certain event needs to be complete, started, etc.
Baselines - We must not forget that the plan of a certain project is a contractual document (normaly approved by client). Once client approves it then it should be frozen (no changes allowed) and copy into a diferrent name. This contractual baseline normaly can only change with the approval of the client.
Number of baselines - depends on your strategie to control the project: U might want to use previous months status as baseline to compair with achievments (earned value, etc) by the end of next months.
In general a big change in the project causing the previous baseline not anymore executable normaly requires a revision of strategie/ project execution plan/ etc and therefore a new baseline should be created.
I Hope to have contributed for your clarification.
BR
JMFrade