Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Making project complexity understandable: the elegance of notations
KTH, Superseded Departments, Electrical Systems.
KTH, Superseded Departments, Electrical Systems.
2003 (English)In: Proceedings of the 12th International Conference on Management of Technology (IA-MOT), Nancy, France, 2003.: From Information to Knowledge to Competencies: Key Success Factors for Innovation and Sustainable Development. / [ed] Hosni, Y.A., Khalil, T.M., Morel-Guimaraes L., 2003Conference paper, Published paper (Other academic)
Place, publisher, year, edition, pages
2003.
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:kth:diva-5353ISBN: 0-9712964-5-6 (print)OAI: oai:DiVA.org:kth-5353DiVA: diva2:9426
Note
QC 20100519Available from: 2004-10-28 Created: 2004-10-28 Last updated: 2010-05-19Bibliographically approved
In thesis
1. Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
Open this publication in new window or tab >>Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
2004 (English)Doctoral thesis, comprehensive summary (Other scientific)
Abstract [en]

Within the electric power industry, the average company's enterprise system - i.e. the overall system of IT related entities - is today highly complex. Technically, large organizations posses hundreds or thousands of extensively interconnected and heterogeneous single IT systems performing tasks that varies from enterprise resource planning to real-time control and monitoring of industrial processes. Moreover are these systems storing a wide variety of sometimes redundant data, and typically they are deployed on several different platforms. IT does, however, not execute in splendid isolation. Organizationally, the enterprise system embraces business processes and business units using as well as maintaining and acquiring the IT systems. The interplay between the organization and the IT systems are further determined by for instance business goals, ownership and governance structures, strategies, individual system users, documentation, and cost.

Lately, Enterprise Architecture (EA) has evolved with the mission to take a holistic approach to managing the above depicted enterprise system. The discipline's presumption is that architectural models are the key to succeed in understanding and administrating enterprise systems. Compared to many other engineering disciplines, EA is quite immature in many respects. This thesis identifies and elaborates on some important aspects that to date have been overlooked to a large extent. Firstly, the lack of explicit purpose for architectural models is identified. The thesis argues that the concerns of a company's Chief Information Officer (CIO) should guide the rationale behind the development of EA models. In particular, distribution of IT related information and knowledge throughout the organization is emphasized as an important concern uncared for. Secondly, the lack of architectural theory is recognized. The thesis provides examples of how theory, or analysis procedures, could be incorporated into the Enterprise Architecture approach and hereby concretely drive the development of the architectural models. Due to the nature of enterprise systems, EA theories inevitable will be of an indicative character. Finally, in relation to the models as such, three aspects are highlighted. Firstly, the cost of collecting information from the organization to populate models is routinely neglected by the EA community. This expense should be evaluated in relation to the utility of analyses that the information can provide in terms of better informed decision making by the CIO. Secondly, models (and meta-models) must be kept consistent. And thirdly, the design of models is restricted by the limited mental capabilities of the minds of the model users. CIO concerns must consequently be easy to extract from the Enterprise Architecture models.

Key words: Enterprise Architecture, Enterprise System, Chief Information Officer (CIO), Information Technology (IT) Management, Architectural Theory, Electric Power Industry

Place, publisher, year, edition, pages
Stockholm: Elektrotekniska system, 2004
Series
TRITA-ICS, ISSN 1104-3504 ; 0402
Keyword
Electronics, Enterprise architecture, Enterprise system, Chief information officer, Information technology management, Architectural theory, Electric power industry, Elektronik
National Category
Other Electrical Engineering, Electronic Engineering, Information Engineering
Identifiers
urn:nbn:se:kth:diva-36 (URN)
Public defence
2004-10-28, Kollegiesalen, KTH, Valhallvägen 79, Stockholm, 10:00
Opponent
Supervisors
Available from: 2004-10-28 Created: 2004-10-28 Last updated: 2014-07-17Bibliographically approved
2. Managing Complex Industrial Projects: A comparison between holistic models
Open this publication in new window or tab >>Managing Complex Industrial Projects: A comparison between holistic models
2005 (English)Doctoral thesis, comprehensive summary (Other scientific)
Abstract [en]

Even though the management of large projects has been studied for many years, the track record is still poor, especially for those projects developing complex systems. This thesis studies projects such as these and attempts to find clues as to why some succeed while others do not. Among the challenges, is the specific yet basic need to create a shared understanding in a group of hundreds engineering specialists with their own ideas (biases) of how things actually work. Further, complex development projects are likely to change, especially those projects involved with new technologies that should be state of the art when they hit the market after several years of development time. Thus, there is a need for a tool that can be used to adapt to changes.

An important part of this thesis is the evaluation of different diagram systems that have been used in different development projects. These diagrams function as a device to create a shared understanding of the project and enable those involved to maneuver the project through changes. The evaluation focuses on what the diagrams can express and how easy it is to understand their content. In terms of expressiveness, one of the three evaluated models: the Anatomy Model, answers the largest number of questions relevant to the total project manager. In terms of ease of use, the evaluation shows that the Anatomy did not only answer more questions relevant to the total project manager, but was also easier to maneuver through compared to the alternative models. The thesis concludes that when working with complex development projects, a model like the anatomy provides the project manager with a simple tool that can be used to maneuver through changes and create a communal understanding. Such a simplified model addresses more questions that are relevant to the project manager and is easier to update than the traditional tools that are suggested in most literature.

Place, publisher, year, edition, pages
Stockholm: KTH, 2005. 29 p.
Series
Trita-ICS, ISSN 1104-3504 ; 0602
Keyword
Project Management, Complex Project, Anatomy, Dependency Diagrams
National Category
Other Mechanical Engineering
Identifiers
urn:nbn:se:kth:diva-3860 (URN)
Public defence
2006-03-07, F3, F, Lindstedtsvägen 26, Stockholm, 10:00 (English)
Opponent
Supervisors
Note
QC 20100519Available from: 2006-02-24 Created: 2006-02-24 Last updated: 2010-05-19Bibliographically approved

Open Access in DiVA

No full text

Search in DiVA

By author/editor
Lilliesköld, JoakimJonsson, Narcisa
By organisation
Electrical Systems
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

isbn
urn-nbn

Altmetric score

isbn
urn-nbn
Total: 135 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf