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

This makes perfectly good sense all this means is

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: ized into divisions by product and within product lines (divisions), by engineering disciplines (departments), such as electrical engineers, mechanical engineers, and software engineers. For the purpose of illustrating an alternate hierarchy in this chapter, we will assume that the company performing the work on the example project is organized primarily by craft. Furthermore, we assume that these crafts are summarized at higher levels into what we will refer to as disciplines. The OBS hierarchy we will assume is shown in Figure 6-12. Notice that the (summary-level) craft called ''Pavers" appears to be a work package since there are no lower-level packages under it in the hierarchy. But this is not the case. The reason it appears this way is that there is no paving work on this project. The "real" OBS may have summary-level control packages that are not relevant to a given project. Consequently, when we enter the OBS structure into the database, we will not include the Pavers control package. This makes perfectly good sense. All this means is that only a subhierarchy of the "real" OBS hierarchy is relevant to this project. To maintain alternate hierarchies for the example project, you will need a separate database that we will refer to as the hierarchy database for the example project. This hierarchy database will be used to contain the various hierarchies that correspond to the different views of your project. To save you the effort of building a database in which to store different hierarchies, we TE Team-Fly® AM FL Y 6.5.1— Building Alternate Hierarchies Page 155 Figure 6-12. OBS hierarchy for example project. Page 156 have included a database titled Hierarchies.mdb on the CD provided with this book. This database has two tables in it. One is named WBS, and the other is named OBS. The WBS table contains the work breakdown structure that is in the example project database, and the OBS table contains the organizational breakdown structure shown in Figure 6-12. You will probably want to copy the Hierarchies.mdb database from the CD into the directory you are using to store your example project database. Even though you do not have to build the OBS hierarchy yourself, we will go over the process of building additional hierarchy tables, since you may want to create yet another hierarchy table for some other view in the future. We will also explain the process of how to export these different tables into the example project database in order to get reports summarized by means of an alternate hierarchy. After you have produced the project reports summarized by the alternate hierarchy, you may want to again produce reports summarized by the WBS hierarchy. To do this, you just export the WBS table into the project database, and it will replace the alternate hierarchy. You will then be back where you started and can again produce project reports summarized by the WBS. If you have copied the Hierarchies.mdb table into your working directory, you can now open this database. When you do, your computer screen shoul...
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