Abu-Hijleh, S F (1991) A model for variance-based exception reporting with user-defined criteria. PhD thesis, University of California, Berkeley, USA.
Abstract
Project control efforts are increasingly underbudgeted and understaffed. At the same time, there has been little innovation or improvement in project control reporting and analysis. Exception reporting, hardly a new concept, is too often still largely that: a concept. Most project control systems still generate lengthy and cumbersome reports that have little support for management by exception. In an age of increasing automation, construction management and control work processes have changed little. As a result, many of the benefits of automation are still to be realized. Project planning and control work processes consist of islands of information, knowledge and expertise. Communication and sharing of data between these islands of information are rarely automated. This limits the ability of project control systems to access various project data and generate intelligent reports for management use. Although functional groups (e.g. procurement, cost control, scheduling) may be chartered to perform the specific tasks under their purview, project management must attend to the project as a whole. Integrated project information enable management to assess how the different project functions are coming together to deliver the desired product. In the fragmented project information world of today, management has to relate the various data with little help from the different information systems. This study devised an exception reporting approach that can improve management's productivity. An enhanced and systematic exception reporting capability enables management to identify critical control points in most need of attention at a given point in time. This helps insure that management's limited time is prioritized so as to achieve the most cost-effective control. This research focused on construction labor cost exception reporting with user-defined criteria. Flexibility and versatility in ways of viewing labor performance data was a guiding theme. Multiplicity of reporting perspective was emphasized. The user must not be a slave to rigid query and reporting structures. Quite the opposite, the user must be able to frame the information in the manner which is most meaningful from where he/she sits. This research also emphasized the importance of looking beyond the immediate and the obvious. Insightful information may be available in seemingly unrelated sets of data.
| Item Type: | Thesis (Doctoral) |
|---|---|
| Thesis advisor: | Ibbs, C W |
| Uncontrolled Keywords: | flexibility; construction labor; automation; communication; cost control; innovation; project control; project planning; scheduling; productivity; control system; information system |
| Index terms: | productivity, variance, project control, project management, automation, construction labour, project data, scheduling, project planning, information system, control system, cost control |
| Subjects: | measurement and scaling, information systems, management, project management theory and practice, automation and robotics, monitoring and control, operations research, financial and cost management, data collection methods, control systems |
| Topics: | Cost Management, Business Strategy, Project Management, Research Practice, Digital Applications, Site Management, Time Control |
| Descriptive scope: | 4 PCEA |
N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here