1. Introduction

Information systems (IS) are technical systems with social consequences[1]. They comprise people, software, hardware, procedures and the surrounding organizational system. Most importantly, information models play an important role in the analysis, design and deployment of information systems [2]. Depending on the phase or level of IS design and implementation, three different types of such information models can be distinguished[3]: (a). Conceptual models help with documenting, analysing and understanding the requirements that an IS needs to meet.

These models do not take any technical aspects into consideration and focus on the problem that needs to be solved or the processes that need to be supported; (b). Design models specify the general architecture of the information system by describing larger technical building blocks called components. Such components are not, however, analysed in detail and (c) implementation models depend on specific technologies and are closely related to software programming.

The term ‘‘reference information model” was first used by[4] when they combined their individual research activities on modelling in the architecture, engineering and construction domains. The resulting unified domain model is called IRMA (Information Reference Model for AEC)[4]. Reference models are one approach to accelerate the development of enterprise-specific models[2]. Reference models provide companies and researchers with an initial solution for the design of organisation and application systems[5]. Thus, the following sections review and compare the available project management reference models to be selected as the reference model in this research.

2. Project and Programme Management Reference Models

One of the important reference information models for project management in the architecture, engineering and construction (AEC) industry was published by[6], who called it a “standard model”. Proprietary, object-oriented, modelling techniques are used to develop a project management domain model and a corresponding application system. This is followed by Sacks[7], who developed an integrated AEC information service using object methods and a central project model. Both models were designed for a single-project management system.

The first reference information model for programme management was published by Turner and[8]. This model requires the coordination of the objectives of programme directors, project managers and resource managers. It shows how the information requirements of all three sets of managers can be met by an integrated system. The integrated system consisting of three major elements[8] is as follows: (a) A master project scheduler (MPS) (that is used by programme directors to manage the priorities between projects and to assign resources to individual projects); (b) Traditional project-management systems (that are used by project managers to deliver individual project objectives in conventional ways, using the assigned resources) and (c) People schedulers (that are used by resource managers to assign people to the multidisciplinary teams working on projects, within the constraints set by the programme directors, but meeting the objectives of the project managers).

Ahlemann[3] presented a reference information model for enterprise-wide project management that covers all project management processes that are related to planning, controlling and coordinating projects (RefMod^PM). RefMod^PM’s primary target is to provide validated process and data structure descriptions, based on the literature and empirical research, for project management[9]. The model can also be used for the design of project management software and the set-up of the surrounding organizational system, as well as for the definition of software requirements that are essential to select a commercial project management software system. RefMod^PM covers both single-project management and multi-project management. It is based on a single, uniform, information system architecture called M-Model[3] and makes use of the Unified Modelling Language (UML) Version 2. Within RefMod^PM, the M-Model is divided into ten activity diagrams that correspond to the project life-cycle phases outlined in the scope of the M-Model in[3].

3. Comparison of the Reference Models

Based on the previous and current project management information system review, Table 1 compares four project and programme management information system reference models intended for construction management. Based on the research study by[3], and for the purpose of comparison, to find the most suitable programme management information system model to be adopted in this research, the following general requirements were adopted: (a) PMIS models must clearly identify the applicability of the model to a project lifecycle phase or project status; (b) PMIS models must identify the project’s information in a hierarchical system (at project, programme or portfolio level) for the purpose of multi-project management and (c) PMIS models must be identified on the topic covered according to the ten knowledge areas of the Project Management Body of Knowledge (PMBOK) by the Project Management Institute (2013)[10].

Based on the comparison in Table 1, it is clear that the RefMod^PM model goes beyond the scope of previous reference models. However, this is not surprising, since RefMod^PM uses some ideas from previous work and extends them according to additional requirements. Table 1 also demonstrates the extent to which RefMod^PM represents significant research progress in the field of PMIS reference models. RefMod^PM was found to be the most complete reference model because: (i) It has a significantly wider scope (covering project planning, execution, initiation and benefit realisation); (ii) It has been designed to serve both single and multi-project management purposes; and (iii) It covers almost all functional areas of PMI PMBOK 5^th Edition.

4. Discussion

Although not all the PMBOK areas of knowledge are covered by RefMod^PM, it can still provide guidelines for developing a computerised system for construction project and programme management by using an activity diagram that corresponds to the project lifecycle phases outlined in the scope of the M-Model. Further research and development of a reference model that meets all the knowledge areas in the latest PMBOK 5^th edition are needed. This is due to the current needs of knowledge management and sustainability factors in system development.

The implementation of a computerised system with the right project management information system reference model can improve the quality and quantity of information flow in the current information systems for the construction industry. An important task of better information and communication flow is to provide an up-to-date organisational structure that will resolve the problems of multiple agents and hierarchies[11]. Therefore, to overcome problems caused by the complexity and fragmented nature of the construction industry, the lack of co-ordination and communication between partners and the increasing amounts of data and information[12]; necessitates the idea of using an appropriated reference models in AEC system development.

Table 1. Comparison of Project and Programme Management IS Reference Models

5. Summary

This paper has given an overview of the various reference models for construction management. Although not all the PMBOK areas of knowledge are covered by RefMod^PM, it was found that RefMod^PM is currently the most comprehensive reference model for construction management. Further research and development of a reference model that meets all the knowledge areas in the latest PMBOK 5^th edition is needed. The study presented in this paper is part of an on-going research in developing a comprehensive reference model that meets the current project management standard.

ACKNOWLEDGEMENTS

This work was financially supported by Institut Penilaian Negara (INSPEN) and Universiti Teknologi Malaysia, under research grant 4B086.