| contributor author | John C. Bishop | |
| contributor author | E. Casey Madden | |
| date accessioned | 2017-05-08T22:18:14Z | |
| date available | 2017-05-08T22:18:14Z | |
| date copyright | July 1994 | |
| date issued | 1994 | |
| identifier other | 40162121.pdf | |
| identifier uri | http://yetl.yabesh.ir/yetl/handle/yetl/76882 | |
| description abstract | There are complex and unforeseen difficulties with owner and architect/engineer relationships over long distances. Where the technical support to the owner is not readily available, both owner and consultant need to be more sensitive to each other's needs. A lack of communication skills and experience by both parties, budgetary constraints, and unforeseen conditions can result in failure, unless the project managers understand the need for special consideration of these problems. The key is communication—not only receiving directions but also recognizing the professional experiences of both parties and developing a trust and understanding of each other's position. The triangular relationship of cost, efficiency, and accuracy must be understood and negotiated before the project starts so that both owner and consultant understand the scope of work and the cost of the project. For the inexperienced engineering manager or consultant unfamiliar with remote sites, this relationship can strain the professionalism of both parties. This paper describes the engineer‐consultant management pitfalls inherent in long‐distance project management and any added costs, and provides “dos and don'ts” to manage a technical consultant or project by long‐distance. Understanding the project triangle is the key. | |
| publisher | American Society of Civil Engineers | |
| title | Engineering Management and Project Triangle | |
| type | Journal Paper | |
| journal volume | 10 | |
| journal issue | 4 | |
| journal title | Journal of Management in Engineering | |
| identifier doi | 10.1061/(ASCE)9742-597X(1994)10:4(24) | |
| tree | Journal of Management in Engineering:;1994:;Volume ( 010 ):;issue: 004 | |
| contenttype | Fulltext | |