11.3.1 Transforming the Enterprise Using a Systems Approach
01 Jun 2011-Vol. 21, Iss: 1, pp 1336-1355
TL;DR: In this article, the authors describe a set of principles and concepts that enable greater benefits when using the systems approach for enterprise transformation, including technical activities, of course, but they also address the substantial leadership and managerial challenges at the enterprise level.
Abstract: Enterprise Systems Engineering (ESE) is an emerging discipline that can be used to more confidently and rapidly create the essential changes for the modern enterprise to survive in these days of enormous economic and social uncertainty. Systems Engineering (SE) could have much to offer in enabling this transformation, but significant enhancements to traditional SE tools and methods must be brought to bear. This paper describes a set of principles and concepts that enables greater benefits when using the systems approach for enterprise transformation. These enhancements include technical activities, of course, but they also address the substantial leadership and managerial challenges at the enterprise level.
Citations
More filters
01 Oct 2015
TL;DR: The reasons for this approach are provided, the new Architecture Definition process in the updated standard that was published in 2015 is described and it is expected that this process will be incorporated into the next version of INCOSE's Systems Engineering Handbook and in the Guide to the Systems Engineering Body of Knowledge.
6 citations
Cites background from "11.3.1 Transforming the Enterprise ..."
...As the field of “architecting” has matured it became clear that there was a need to separate architecture into something separate from the design (Maier and Rechtin 2009, Martin 2011)....
[...]
01 Jul 2016
TL;DR: This paper provides an overview of the key concepts in this standard and the rationale for these ideas, and can be used as a foundation for organizational training and guidebooks on architecture management and development.
Abstract: A new, emerging standard on architecture practices is under development as ISO/IEC 42020. This paper provides an overview of the key concepts in this standard and the rationale for these ideas. The standard defines six architecture-related processes: governance, management, conceptualization, evaluation, elaboration, and enablement. These are comprised of 37 activities, having five to eight tasks specified for each activity. It is expected that these processes will be incorporated into the next version of INCOSE's Systems Engineering Handbook and in the Guide to the Systems Engineering Body of Knowledge. This standard can be used as a foundation for organizational training and guidebooks on architecture management and development.
6 citations
01 Nov 2016
TL;DR: This paper presents two real-world examples that illustrate the potential value of applying ESE thinking and presents a number of lessons learnt in doing so.
Abstract: Enterprise systems engineering (ESE) is a multidisciplinary approach that combines traditional systems engineering (TSE) and strategic management to address methods and approaches for aligning system architectures, system development and system implementation with enterprise business rules, enterprise strategic objectives and enterprise capabilities within diverse complex subsystems. ESE therefore refers to TSE at the enterprise level. ESE is a complex approach by itself, but in this paper, we argue and illustrate that value from ESE thinking can be obtained without following the entire ESE set of processes. This paper presents two real-world examples that illustrate the potential value of applying ESE thinking and presents a number of lessons learnt in doing so.
1 citations
Cites background or methods from "11.3.1 Transforming the Enterprise ..."
...The first example study fits predominantly in the enterprise conception life cycle phase [19, 21] and the ESE process of strategic technical planning [10-12, 23, 25]....
[...]
...In order to close the gap between ESE and TSE, [10-12, 23] include the following process areas in the ESE approach:...
[...]
...The second example study fits into the enterprise conception and development life cycle phases [19, 21] and contains the ESE processes of strategic technical planning, enterprise architecture, capability-based planning analysis and technology planning [10-12, 23, 25]....
[...]
...business analysis and modelling), especially those related to enterprise goals and key mission needs [10, 17, 22]....
[...]
...According to [10, 22], the following typical business activities can be supported by ESE activities:...
[...]
01 Oct 2015
TL;DR: This paper describes a six‐step process for managing architectures under these conditions that has been implemented at some large government agencies and is based on best practices from government and industry.
Cites methods from "11.3.1 Transforming the Enterprise ..."
...Enterprise Planning supports the Strategic Planning process as illustrated below (Martin 2011)....
[...]
References
More filters
IBM1
TL;DR: Information systems architecture is defined by creating a descriptive framework from disciplines quite independent of information systems, then by analogy specifies information systems architecture based upon the neutral, objective framework.
Abstract: With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system. This paper defines information systems architecture by creating a descriptive framework from disciplines quite independent of information systems, then by analogy specifies information systems architecture based upon the neutral, objective framework. Also, some preliminary conclusions about the implications of the resultant descriptive framework are drawn. The discussion is limited to architecture and does not include a strategic planning methodology.
3,219 citations
"11.3.1 Transforming the Enterprise ..." refers methods in this paper
...(Zachman 1987, 276- 292; Spewak 1992; Zachman 1992, 590-616) Architecture descriptions have also been developed using a business-question based approach....
[...]
Book•
01 Jan 2007TL;DR: This book is not a textbook, but rather an essay on complex adaptive systems, and the best method to discover their properties is to dispatch many computer agents to experience the system’s possibilities.
Abstract: Theoretical physics is replete with models. When equations of motion are not available, or not amenable to perturbation theory, or just too hard from which to extract useful information, then physicists turn to models and computation. The Ising model of ferromagnetism is a classic example. A simple nearest neighbor temperature dependent interaction, in two or more dimensions, leads to long-range order and a phase transition at a finite temperature. This model has many locally interacting parts and an emergent behavior (ferromagnetism) at a critical temperature. However, the system never adapts. It does not change the phase transition to a higher temperature or avoid a phase transition altogether. Social systems are always adapting, and this interesting twist produces a vast array of possibilities and forms the basis of much of the discussion in Miller and Page’s book. This book is not a textbook, but rather an essay on complex adaptive systems. The discussions and insights will be better appreciated by readers who have already tried their hand at investigating complex adaptive systems. These systems can be so complex that the best method to discover their properties is to dispatch many computer agents to experience the system’s possibilities. The study becomes more interesting when the agents can alter their actions and the rules of the game. Miller and Page give the simple, but instructive example of forest growth and lightning induced forest fires. If trees grow too rapidly they will cover the allowable space and a fire started anywhere in the forest will spread and destroy the entire forest. A very slow growth will only produce a sparse forest. The authors find a tree growth rate to achieve an optimal stable high forest coverage. Their solution is trumped when altruistic agents are introduced, one for each tree. Some of the agents adapt by not growing a tree in their plot of land (to their personal disadvantage) but the overall global organization is one of firebreaks preventing large scale fires. Adaptation wins! Another model discussed is what physicists call the minority game, that is, making a choice that puts you in the minority. This is perhaps best known through the El Faro example of choosing whether or not to go to Santa Fe’s El Faro bar tonight based on whether it was
1,712 citations
TL;DR: The introduction of democracy in south africa brought some hope to millions who were previously marginalised and the new government transformed the public.
Abstract: (1995). Reengineering the Corporation: A Manifesto for Business Revolution. European Journal of Information Systems: Vol. 4, No. 2, pp. 116-117.
1,605 citations
TL;DR: Bertalanffy's theory of general systems theory was introduced by Dr. William Gray in 1965 at an APA panel as mentioned in this paper and has not managed to sustain much over-all enthusiasm in psychiatry except for a small group of investigators.
Abstract: It is often disconcerting to learn that a discovery that one has made has been around a long time, and thus is no discovery at all; but this should not deter one from sharing his good fortune. Ludwig von Bertalanffy has been writing about a general systems theory since at least 1945 but it did not become a component of psychiatric study until introduced by Dr. William Gray in 1965 at an APA panel. It has not, however, managed to sustain much over-all enthusiasm in psychiatry except for a small group of investigators. The present volume by Bertalanffy, as its title suggests, covers the foundations, the development, and the applications of this theory. This reviewer can only suggest and urge that every psychiatrist read it. Once that has been done, I would next urge you to read it again. The book consists of ten chapters
1,556 citations
"11.3.1 Transforming the Enterprise ..." refers background in this paper
...(von Bertalanffy 1968; Weinberg and Weinberg 1988; Miller and Page 2007; Rouse 2008, 17-25) For an approach to complex adaptive systems engineering (CASE), refer to (White 2008, 1-16) and (White and McCarter 2009, 71-105)....
[...]
Book•
01 Jan 1981
TL;DR: The design for operational feasibility and design for Usability, as well as Alternatives and Models in Decision Making, and Design for Affordability and Disposability, are reviewed.
Abstract: Preface. I. INTRODUCTION TO SYSTEMS. 1. System Definitions and Concepts. 2. Bringing Systems Into Being. II. THE SYSTEM DESIGN PROCESS. 3. Conceptual System Design. 4. Preliminary System Design. 5. Detail Design and Development. 6. System Test and Evaluation. III. SYSTEM ANALYSIS AND DESIGN EVALUATION. 7. Alternatives and Models in Decision Making. 8. Models for Economic Evaluation. 9. Optimization in Design and Operations. 10. Queuing Theory and Analysis. 11. Control Concepts and Techniques. IV. DESIGN FOR OPERATIONAL FEASIBILITY. 12. Design for Reliability. 13. Design for Maintainability. 14. Design for Usability (Human Factors). 15. Design for Supportability (Serviceability). 16. Design for Producibility and Disposability. 17. Design for Affordability (Life-Cycle Cost). V. SYSTEMS ENGINEERING MANAGEMENT. 18. Systems Engineering Planning and Organization. 19. Program Management and Control. VI. APPENDICES. A: Analysis and Checklist Methods. B: Probability Theory and Analysis. C: Probability and Statistical Tables. D: Interest Factors Tables. E: Finite Queuing Tables. F: Selected Bibliography.
1,535 citations