Home | | Construction Planning and Scheduling | Information Transfer and Flow

Chapter: Civil - Construction Planning And Scheduling - Organization and Use of Project Information

| Study Material, Lecturing Notes, Assignment, Reference, Wiki description explanation, brief detail |

Information Transfer and Flow

In an overabundance of optimism or enthusiasm, it might be tempting to conclude that all information pertaining to a project might be stored in a single database.

Information Transfer and Flow

 

The previous sections outlined the characteristics of a computerized database. In an overabundance of optimism or enthusiasm, it might be tempting to conclude that all information pertaining to a project might be stored in a single database. This has never been achieved and is both unlikely to occur and undesirable in itself. Among the difficulties of such excessive centralization are:

 

z Existence of multiple firms or agencies involved in any project. Each organization must retain its own records of activities, whether or not other information is centralized. Geographic dispersion of work even within the same firm can also be advantageous. With design offices around the globe, fast track projects can have work underway by different offices 24 hours a day.

 

z Advantages of distributed processing. Current computer technology suggests that using a number of computers at the various points that work is performed is more cost effective than using a single, centralized mainframe computer. Personal computers not only have cost and access advantages, they also provide a degree of desired redundancy and increased reliability.

z Dynamic changes in information needs. As a project evolves, the level of detail and the types of information required will vary greatly.

 

z Database diseconomies of scale. As any database gets larger, it becomes less and less efficient to find desired information.

 

z Incompatible user perspectives. Defining a single data organization involves trade-offs between different groups of users and application systems. A good organization for one group may be poor for another.

 

In addition to these problems, there will always be a set of untidy information which cannot be easily defined or formalized to the extent necessary for storage in a database. While a single database may be undesirable, it is also apparent that it is desirable to structure independent application systems or databases so that measurement information need only be manually recorded once and communication between the database might exist. Consider the following examples illustrating the desirability of communication between independent application systems or databases. While some progress has occurred, the level of integration and existing mechanisms for information flow in project management is fairly primitive. By and large, information flow relies primarily on talking, written texts of reports and specifications and drawings.


Study Material, Lecturing Notes, Assignment, Reference, Wiki description explanation, brief detail


Copyright © 2018-2020 BrainKart.com; All Rights Reserved. Developed by Therithal info, Chennai.