Amacom - Modern Project Management (Ocr) - 2001 ! - (By Laxxuss)

The discussion of task sequencing and resource

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: eduling system can be manually interfaced to Modern Project, it is possible to use the Modern Project toolset with any scheduling system. Moreover, it is probably not a great deal more difficult to interface scheduling systems other than Microsoft Project with Modern Project. The fact that the only automated interface supplied on the CD that is distributed with this book is to Microsoft Project should not be viewed as an endorsement of that product. Rather, the automated interface is supplied to indicate how such an interface can be implemented simply. 7.1— Task Sequencing with Microsoft Project In Chapter 2, not a lot of detail was given about resource scheduling. The difference between work sequencing and resource Page 168 scheduling was discussed, but the details of resource scheduling were deferred to this chapter. It is now time to cover this topic in more detail. Since we entered additional tasks into the example project database in Chapter 6, we now have quite a few more tasks to schedule. We begin the discussion of resource scheduling by sequencing all the tasks we now have in the example project database. The discussion of task sequencing and resource scheduling that follows uses Microsoft Project. Since some readers may have access to Microsoft Project but may not have actually used it before, we explain how to use this scheduling tool to both sequence and schedule the tasks in the example project. For readers who are utilizing another scheduling tool, this should not present a problem, since the same process can be followed using other scheduling tools. 7.1.1— Task-Naming Convention To use Microsoft Project to sequence the tasks in the example project, we must first enter the tasks into this scheduling tool. In order to help you do this, we now explain a certain convention in task naming. This convention serves two purposes. The first is to overcome a limitation in the Microsoft Project task-naming convention. The second is to make the automated interface between Microsoft Project and Modern Project as simple as possible. Microsoft Project does not allow multiple tasks to have the same name. You may be wondering why you would want to give two different tasks the same name. But having many tasks with the same name is common on many projects, and for good reason. Most project management systems are package oriented , but scheduling systems are often task oriented. In the User's Guide for Microsoft Project, the explanation of how to enter a task begins by explaining to the reader to ''use a verb and a noun to name a task (for example, Pour concrete)." On many construction projects there may be many tasks named "Pour concrete." For instance, there may be several work packages Page 169 (e.g., "Footings," "Columns," "Culverts," ''Retaining Walls," and "Spans") that contain a task named "Pour concrete." These are all different tasks, and the project management system can distinguish them as being different because it knows the relationship between each task and the work package in which it is contained. In th...
View Full Document

This note was uploaded on 01/11/2011 for the course ACC 9 taught by Professor Yeetan during the Spring '10 term at Sunway University College.

Ask a homework question - tutors are online