I agree to what John wrote for the different levels: Use common sense and dont think too complicate. Often it is part of the contract, what should be delievered in the different levels. Basis must be a common plan from which you create the different views using filters and/or collapse data.
In any case it should be agreed during the start-up - e.g. the kick-off meeting - between all parties/stakeholders.
Just apply a bit of common sense, rembering a level II is only a summation of the detail in your level III plan, with level I being a summation of the level II.
When setting up a plan I try to think what does the person reading the plan will want to know and be be able to understand and follow. Bearing in mind I will have to be easily and quickly acuratly progress the plans etc.
I normally break the work down into whatever is sensible to the project. This could be a breakdown by Work Location, Work Phase, Work Stage, Disciplnes, Systems, Sub System, Contractors. etc etc.
For the number of activites for the plans will depend on the size of the projects. Using a rule of thumb I try to keep level I & II plans onto single sheets of paper. This always looks better in the weekly/monthly progress reports!
I always discuss with the Manger/Director what their ideas are on the subject of levels of planning, at the same time showing them what I have produced.
A final point is to check the contract requirements, they may have specifiled what is required for levels of planning.
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.
Thank you every much for your help/links/advice. I have been informed it does state in the contract what is expected in the level 2 plan etc.
it is always good to know good advice is at hand
Hi Karim
Thank you for the excellent link!
Hi Dave
I agree to what John wrote for the different levels: Use common sense and dont think too complicate. Often it is part of the contract, what should be delievered in the different levels. Basis must be a common plan from which you create the different views using filters and/or collapse data.
In any case it should be agreed during the start-up - e.g. the kick-off meeting - between all parties/stakeholders.
Regards
Dieter
Hi Dave,
Just apply a bit of common sense, rembering a level II is only a summation of the detail in your level III plan, with level I being a summation of the level II.
When setting up a plan I try to think what does the person reading the plan will want to know and be be able to understand and follow. Bearing in mind I will have to be easily and quickly acuratly progress the plans etc.
I normally break the work down into whatever is sensible to the project. This could be a breakdown by Work Location, Work Phase, Work Stage, Disciplnes, Systems, Sub System, Contractors. etc etc.
For the number of activites for the plans will depend on the size of the projects. Using a rule of thumb I try to keep level I & II plans onto single sheets of paper. This always looks better in the weekly/monthly progress reports!
I always discuss with the Manger/Director what their ideas are on the subject of levels of planning, at the same time showing them what I have produced.
A final point is to check the contract requirements, they may have specifiled what is required for levels of planning.
Above seems to have worked over the years!!
Regards
John L.
Hi Dave,
Download this file:
http://www.planningengineers.org/publications/papers_download.aspx?id=21
Karim