|
|
|
|
|
|
|
without abnormal resource constraints and unexpected problems. When available, benchmarking data from high performing competitors should be used to set the standard durations. |
|
|
|
|
|
|
|
|
Network plans and standard plans are not very suitable for representing repetitive tasks, such as production and release of drug substance or formulation supply in numerous consecutive batches. These important activities should be tracked separately in suitable task lists or action plans. A similar situation applies to certain actions required mostly in preparing and optimizing the plan, such as collecting information and opinions. |
|
|
|
|
|
|
|
|
1.
Requirements for Single Project Planning |
|
|
|
|
|
|
|
|
When starting on a new project plan, the team lists tasks, defines work packages, determines predecessor/successor sequences and asks for time duration estimates. The clearest way to present and discuss this information is the classical bar or Gantt chart. Initially, this is probably drawn on a flip chart but, as soon as the information starts consolidating, it is useful to document and organize it by using one of the many available project management softwares. This allows quick and easy changes, presentations in various levels of detail or in various time-frames, what-if tests of alternative ways to proceed, and, generally, a very nice and clear presentation of the data. |
|
|
|
|
|
|
|
|
However, the benefit of using network software for project optimization seems limited. The critical path of a project, typically, is evident without computer help, and the effect of possible measures for time reduction may be evaluated easily on paper. However, it is useful to see the early and late start dates of noncritical activities and to use this information for resource scheduling. Many software packages allow entering original and revised plan dates for convenient tracking and preparation of progress reports. |
|
|
|
|
|
|
|
|
For these reasons, the author recommends the use of networking software for pharmaceutical development projects. The systems may be PC-based or mainframe. Usually, PC-based software can also be run on client/server networks using a variety of operating systems. Many of them can also exchange their data with common data banks, e.g., ORACLE. Some of the more frequently used systems are listed in Table 7. Detailed information on the functionality and system requirements of the different products can easily be obtained from vendors, e.g., through their Internet presentations. Reviews and comparisons can also be found in a variety of computer publications, e.g., in [3]. The choice of a system also depends on the ap- |
|
|
|
|
|