Professional Documents
Culture Documents
com
Abstract
Project management information systems have changed considerably over the last decade. They no longer focus on scheduling and
resource management alone. Instead, they have become comprehensive systems that support the entire life-cycle of projects, project programs, and project portfolios. In this context, project-oriented organizations are facing a new challenge: the design, implementation, and
operation of project management information systems have become increasingly complex. Numerous processes have to be considered,
diverse stakeholder interests taken into account, and corresponding software systems selected. The reference information model (RefModPM) presented in this article addresses this challenge and aims to accelerate the set-up of project information systems. RefModPM
was developed with the help of 13 domain experts from German and Swiss enterprises. Furthermore, it is based on an analysis of 28
commercial project management software systems. RefModPM has already been applied in several projects and is the basis of the forthcoming German DIN norm for a standardized project management data model.
2008 Elsevier Ltd and IPMA. All rights reserved.
Keywords: Information technology; Processes; Procedures; Managing information systems
1. Introduction
Project management information systems (PMIS) are
widely regarded as an important building block in todays
project management [1]. The nature of these systems has
changed considerably during the last decade; they are, in
fact, still developing from single-user/single-project management systems to complex, distributed, multi-functional
systems that no longer only cover project planning [2].
Information systems research has to date only partly
reected this PMIS evolution. Typical elds of research
are (1) algorithms in respect of operation research problems related to project management (e.g. [35]), (2) the
assessment and comparison of commercial project management solutions and corresponding assessment frameworks
(e.g. [68]), (3) the development of prototypes to test new
kinds of functionality (e.g. [911]), and (4) research into
20
Problem definition
Problem Definition
Exploration and
generation of
hypotheses
Validation
Practical Application
Refinement of
the Reference Model
Documentation
Documentation
Legend
Research Activity
Research Phase
21
Order
22
Table 1
Analyzed project management IS
Product
Company
Acos Plus.1
Alpha Project Line
AMS Realtime Projects
Artemis Portfolio, Project and
Resource Management Solution
Cat4
eRoom
fx-project
iPlan
Nucleus
OurProject
PC Projekt-Controlling-System
Planview
PPMS
PQM
Primavera P3e
Project Insight
Project Scheduler
ProjectExplorer, WebTime
Projekta
Prolog Scheduler
ProMOS
PSIPENTA PM
resSolution
SureTrak Project Manager
Teamcenter Project
untermStrich
Vertabase Pro
vProject
Table 2
Interview partner companies for the reference model validation phase
Company
Location
Wadenswil, Switzerland
Inneon Technologies AG
Multi-national nancial services company
(anonymous)
Softlab GmbH
T-Systems International GmbH
ThyssenKrupp Stahl AG
Vattenfall Europe
Ludwigshafen, Germany
Munich, Germany
Zurich, Switzerland
Ulm, Germany
Dusseldorf, Germany
Ottobrunn-Riemerling
(Munich), Germany
Munich, Germany
Zurich, Switzerland
Hamburg, Germany
Erfurt, Germany
Duisburg, Germany
Berlin, Germany
Lincoln and Guba [33, p. 234], this cyclic process was terminated when insights gained from preceding interview discussions no longer enhanced the reference model. It was
then concluded that the domain experts had reached consensus on the reference models propositions. The selection
of domain experts followed both the chain sampling and
theoretical sampling approaches [32, p. 237]. Although
they were identied by means of chain sampling, the interview topic was determined by means of the M-Model and
theoretical sampling since not all aspects of enterprise-wide
project management can be discussed in a single interview.
(3b) Practical application. The validation of the reference model was not only achieved through the interviews
with domain experts, but it was also validated in respect
of application projects (see Section 6).
(3c) Renement of the reference model. The experience
gained in the above-mentioned projects was also used to
rene the reference model.
(4) Documentation. The documentation of the reference
model contains a description of the construction process,
the reference model itself, annotations of model elements,
including theoretical and empirical evidences, and the documentation of the interview results.
4. The architecture of the reference model: the M-Model
The reference model is based on a single, uniform conceptual architecture called the M-Model (Fig. 2). The Mmodel embraces all tasks related to the initiation, planning,
execution, and termination of projects. It describes the process of enterprise-wide project management (project life-
Top Management:
Portfolios
Strategy Definition
Portfolio
Planning
Project
Office,
Committees:
Projects,
Programs
Project
Manager:
Projects
Idea
Evaluation
Idea
Generation
Portfolio
Controlling
Project
Preparation
Detailed
Planning
23
Project
Controlling
Project
Execution
External
Project
Termination
Internal
Project
Termination
Processes
Data Structures
24
Project manager: At the operational project management level, the project manager is responsible for the
planning and execution of a single project. This level is
represented by the lower third of the M-Model.
Project oce/committees: This management level comprises all permanent or temporary organizational elements that are responsible for multi-project
Table 3
Activity diagrams that are part of the RefModPM reference model
M-Model element
Contents
Number of
diagrams
Idea generation
Idea evaluation
Portfolio planning
Project Preparation
Project planning
Project execution
Project controlling
Portfolio controlling
Internal project
termination
External project
termination
The reference model consists of 10 basic activity diagrams that correspond to the project life-cycle phases outTable 4
Class diagrams in the RefModPM reference model
M-Model element
Number of
diagrams
Foundation
Financial management
Strategic planning
Idea generation
Idea evaluation
1
Portfolio planning
5
Project preparation
Project planning
Project execution
1
1
Project controlling
Portfolio controlling
Internal project
termination
External project
termination
1
1
2
1
1
1
1
25
26
OrgaPlanArchive
Orga, IT
PlanVersion
-VersionNumber
-CreationDate
-Description
-Editable
OrgaScenario
Orga
Programme
0..1
0..1
0..1
0..*
0..*
Orga
Project
-ActualPlan
0..*
-AppovedPlan
0..*
-BasePlan
Orga
SubProject
Orga, IT
Initiative
-Child
0..*
-ID
-Name
-Description
-Comment
-Objective
-Activities
-Conditions
-Dependencies
-StartDate
-EndDate
-LatestStartDate
-EarliestStartDate
-LatestEndDate
-EarliestEndDate
-Effort
-Float
-Duration
-Risk
-PostponedUntil
-Priority
-ResourcePlanningType
-Mandatory
0..1
-Parent
Orga
Phase
Orga
WorkPackage
Orga
Task
0..*
1..*
Orga, IT
InitiativeLifeCyclePhase
-Date
-Decision
-Comment
0..*
PM
Schlaghecks model is clearly more advanced than Froeses. It allows work breakdown structures with an unlimited number of levels to be set up. Consequently,
Schlagheck is at least able to meet requirement 2.
5.4. RefModPM
RefModPM tries to meet the requirements outlined
above by introducing a very fundamental data structure
called Initiative (Fig. 3). An initiative is a generalization
of any form of action that has a dened start and end date
and is undertaken to reach a goal. Therefore, an initiative
may be a program, a project, a sub-project, a project phase,
a work package, an activity or a task (indicated by the
inheritance relationship between these classes). By using a
generic data structure for these dierent types of objects,
project management methods from, for example, risk,
27
ProjectSpecificObject
-ProjectNumber
ActivityCategory
-Action
-ComponentCategories
-Method
-PartOf
-QuantityFormula
-...
Project
-Contracts
-Facility
-Location
-Particiapants
1
ConstructionPlan
-DefaultConstructionMethod
-DurationUnits
1
Activity
-Components
-EarlyFinish
-EarlyStart
-LateFinish
-LateStart
-Duration
-TotalFloat
1
*
*
-Successor
-Predecessor
-Hierarchy
0..1
Project
0..*
ProjectPlan
-Objective
-Status
-ResponsiblePerson
1
WorkBreakdownStructure
0..*
-Hierarchy
WorkBreakdownStructurePlanning
WBSElement
-Description
1
0..1
1..*
SubProject
-Hierarchy
Task
0..1
0..*
WorkPackage
Activity
28
Table 5
RefModPM compared to existing reference information models for project management
Domain Characteristics
Project lifecycle phases
Management levels
Supported industries
Coveredb
Integration management
Scope management
Time management
Cost management
Quality management
Human resource management
Communications management
Risk management
Procurement management
(Semi-)Formal models available for
Data structures
Organizational structures
Processes
Other characteristics
Number of classes/object types
Modeling language(s)
Research methodology
Model evaluation
Documentation of design and evaluation methods
Communication of research
a
b
c
Froese (1992)
Schlagheck (2000)
RefModPM
Planning
Project
Construction industry
Planning, execution
Project
Any
No
Yes
Yes
Yes
No
No
No
No
Yes
No
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Noa
Yes
No
Yes
Yes
Yes
Yes
36
SOL (Proprietary)
20
UML 1
101
UML 2
Yesc
No
Yes
No
No
Yes
Yes
Yes
Yes
Processes are only modeled implicitly, representing process steps (activities) in the data model.
According to the nine knowledge areas of the Project Management Body of Knowledge (PMBOK) [PMI04, 9].
A prototype has been developed, although it is unclear whether this prototype has been evaluated.
29
30
Konstruktion