I think the proposal schedule is as important as detailed project schedule is. During the tender period you should have a good understanding of the project and define the method statement and choose proper technology to do the job. Without having a good schedule showing the real critical path, how you can define the minimum time requirement? How you can analyze the project cost which is the most important issue in your proposal documents. You can show just Bar chart in proposal schedule without using CPM tools but at least your team should have a very depth thinking of the duration and dependencies of each task before start to draw a Bar Chart.
Actually, what we are doing for our proposal schedule are as follows:
1-Define the project scope in detail as much as RFP documents allow.
2-Prepare the Base Schedule using CPM tools (P3, MS-Project, ….) with enough detail to define the critical path (Max. level-3).
3-Check the contract Milestones and adjust the logic of the schedule accordingly to meet all Contract Target Dates issued in RFP.
4-Estimate require resources including Man-Power, Equipment and Material based on the time frame defined in the schedule
5-For proposal document the Base Schedule will be summarized to show just level 1 or 2 of the project and not all detailed activities.
6-The logistic drawings (and Project Snapshots for huge project) will be prepared to support the method statement and schedule.
7-After award contract, the proposal schedule will be developed in more detail by keeping the time frames of proposal schedule.
I think the proposal schedule is as important as detailed project schedule is. During the tender period you should have a good understanding of the project and define the method statement and choose proper technology to do the job. Without having a good schedule showing the real critical path, how you can define the minimum time requirement? How you can analyze the project cost which is the most important issue in your proposal documents. You can show just Bar chart in proposal schedule without using CPM tools but at least your team should have a very depth thinking of the duration and dependencies of each task before start to draw a Bar Chart.
Actually, what we are doing for our proposal schedule are as follows:
1-Define the project scope in detail as much as RFP documents allow.
2-Prepare the Base Schedule using CPM tools (P3, MS-Project, ….) with enough detail to define the critical path (Max. level-3).
3-Check the contract Milestones and adjust the logic of the schedule accordingly to meet all Contract Target Dates issued in RFP.
4-Estimate require resources including Man-Power, Equipment and Material based on the time frame defined in the schedule
5-For proposal document the Base Schedule will be summarized to show just level 1 or 2 of the project and not all detailed activities.
6-The logistic drawings (and Project Snapshots for huge project) will be prepared to support the method statement and schedule.
7-After award contract, the proposal schedule will be developed in more detail by keeping the time frames of proposal schedule.
One, you do not want to put too much effort since it is a tender proposal. You just want to show the general intention of your company.
On the other hand it might be advantageous to show a good planning capability by doing a well devised schedule, although brief.
Third, you are talking about doing a gantt chart, seems to me you are not using the critical path method. You need to evaluate this and make a desicion if have not done it yet.
Fourth, you can do a much as time allows.
Fifth, if you do not review your project in depth, the more detailed your schedule the greater risk you are taking about showing activities that might be scheduled in an incorrect place in time, or incorrectly coordinated with other activities.
Having said the above, I would expect between 30 and 50 activities if using the gantt chart method. You can go up to 250 activities if using the critical path method. The latter if you analize your project in greater depth.
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.
Stevan;
I think the proposal schedule is as important as detailed project schedule is. During the tender period you should have a good understanding of the project and define the method statement and choose proper technology to do the job. Without having a good schedule showing the real critical path, how you can define the minimum time requirement? How you can analyze the project cost which is the most important issue in your proposal documents. You can show just Bar chart in proposal schedule without using CPM tools but at least your team should have a very depth thinking of the duration and dependencies of each task before start to draw a Bar Chart.
Actually, what we are doing for our proposal schedule are as follows:
1-Define the project scope in detail as much as RFP documents allow.
2-Prepare the Base Schedule using CPM tools (P3, MS-Project, ….) with enough detail to define the critical path (Max. level-3).
3-Check the contract Milestones and adjust the logic of the schedule accordingly to meet all Contract Target Dates issued in RFP.
4-Estimate require resources including Man-Power, Equipment and Material based on the time frame defined in the schedule
5-For proposal document the Base Schedule will be summarized to show just level 1 or 2 of the project and not all detailed activities.
6-The logistic drawings (and Project Snapshots for huge project) will be prepared to support the method statement and schedule.
7-After award contract, the proposal schedule will be developed in more detail by keeping the time frames of proposal schedule.
Hope it helps.
Regards,
Ali
Stevan;
I think the proposal schedule is as important as detailed project schedule is. During the tender period you should have a good understanding of the project and define the method statement and choose proper technology to do the job. Without having a good schedule showing the real critical path, how you can define the minimum time requirement? How you can analyze the project cost which is the most important issue in your proposal documents. You can show just Bar chart in proposal schedule without using CPM tools but at least your team should have a very depth thinking of the duration and dependencies of each task before start to draw a Bar Chart.
Actually, what we are doing for our proposal schedule are as follows:
1-Define the project scope in detail as much as RFP documents allow.
2-Prepare the Base Schedule using CPM tools (P3, MS-Project, ….) with enough detail to define the critical path (Max. level-3).
3-Check the contract Milestones and adjust the logic of the schedule accordingly to meet all Contract Target Dates issued in RFP.
4-Estimate require resources including Man-Power, Equipment and Material based on the time frame defined in the schedule
5-For proposal document the Base Schedule will be summarized to show just level 1 or 2 of the project and not all detailed activities.
6-The logistic drawings (and Project Snapshots for huge project) will be prepared to support the method statement and schedule.
7-After award contract, the proposal schedule will be developed in more detail by keeping the time frames of proposal schedule.
Hope it helps.
Regards,
Ali
Stevan:
There are several factors to consider:
One, you do not want to put too much effort since it is a tender proposal. You just want to show the general intention of your company.
On the other hand it might be advantageous to show a good planning capability by doing a well devised schedule, although brief.
Third, you are talking about doing a gantt chart, seems to me you are not using the critical path method. You need to evaluate this and make a desicion if have not done it yet.
Fourth, you can do a much as time allows.
Fifth, if you do not review your project in depth, the more detailed your schedule the greater risk you are taking about showing activities that might be scheduled in an incorrect place in time, or incorrectly coordinated with other activities.
Having said the above, I would expect between 30 and 50 activities if using the gantt chart method. You can go up to 250 activities if using the critical path method. The latter if you analize your project in greater depth.
I hope this helps
Tomas Rivera