Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Deliverables during planning & schedule development

6 replies [Last post]
Miguel Rios
User offline. Last seen 10 years 18 weeks ago. Offline
Joined: 10 Oct 2009
Posts: 18
Groups: None
What deliverables (documents) should a good planning and scheduling DEVELOPMENT phase have? (those that are under the responsibility of the Planeer & Scheduler)

Maybe?

- Schedule Baseline (Bar Chart)
- Critical Path Report (Bar Chart)
- Network Logic Diagram
- S-Curve (man-hours & cost)
- Manpower Report (Histogram)

What else? Or maybe my deliverables are not correct. Please provide your opinions. Thank you.

Replies

Rafael Davila
User offline. Last seen 11 hours 22 min ago. Offline
Joined: 1 Mar 2004
Posts: 5229
Shahul

For Miguel these reports might be deliverables with a contractual implication. He might contract his scheduler based on deliverables and not on an hourly basis. These reports upon delivery will be payable upon an agreed fee.

In the engineering and design world documents are the deliverables.

Best regards,
Rafael
It depends on the definition.
You can call any report as deliverable.

If the project model was properly developed then it can provide a lot of reports. When we plan our own work, we plan the time when the project model will be ready. We do not plan when and what report will be published. The set of project reports is usually predefined.

Best Regards,
Vladimir
Shah. HB
User offline. Last seen 15 weeks 23 hours ago. Offline
Joined: 25 Nov 2008
Posts: 773
Proper documentation of above said reports and monitoring the planned network and forecasting wont be the deliverable?
Rafael Davila
User offline. Last seen 11 hours 22 min ago. Offline
Joined: 1 Mar 2004
Posts: 5229
Miguel Rios,

Among all reports at this stage one of the most important report will be the report that provides you with the network logic.

For a job in the hundreds of activities and above the Network Logic Diagram might be too big to be of any practical use. For schedules with hundreds of activities the main use of the network logic diagrams is to trace logic.

You will need a report on predecessors/successors, type of links and lag and whether if driving or not.

You should also look for resource critical path if your schedule is or might be driven by availability of resources at any time during the execution of the job.

You should also ask for resurce usage histograms, this will simplify the verification on resource leveling and usage.

Finally ask for a copy of the computer files.

Best regards,
Rafael
Project Planner shall create project computer model that calculates all necessary data and produces all necessary reports.

These reports may include:
Activity Bar Chart,
Resource Bar Chart,
S-curves for costs and materials,
Work plans for the future day (week, month - depends on the project), etc.

These are not deliverables but reports from the created Project model. And these reports shall cover everything that is necessary for project management.

Best Regards,
Vladimir
Anoon Iimos
User offline. Last seen 2 years 11 weeks ago. Offline
Joined: 22 Sep 2006
Posts: 1422
For me, the planner has no deliverable, the prime duty is to organize and define (in terms of time) the deliverables of others (i.e. for engineering).