Architecting a portfolio of systems

Maier, Mark W.

doi:10.1002/sys.21486

Cited by 6 publications

(5 citation statements)

References 42 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[Noguchi et al 2020] It should be noted that the portfolio considered here is broader than the notion of "portfolio of systems" considered by others where it is defined as a "collection of systems related by common management and budgets, and at least some relationship to mission or missions." [Maier 2019] Considering other things in the portfolio such as technologies, processes, people, facilities and services makes for a much more complex and challenging portfolio management task.…”

Section: Figure 1 Using Enterprise Portfolio Management To Help Trans...mentioning

confidence: 99%

Extending UAF for Model‐Based Capability Planning and Enterprise Portfolio Management

Martin

2022

INCOSE International Symp

View full text Add to dashboard Cite

Capabilities, the lifeblood of an enterprise, can be managed effectively using portfolio management techniques. Capability roadmaps are commonly used to manage the deployment of new and improved capabilities to address key drivers and challenges that the enterprise faces. This paper shows how MBSE can enhance an organization's ability to plan for capability deployments, as well as the ability to more effectively manage its portfolios of systems, services, people, technologies, processes, facilities, and other key enablers for the fielded capabilities. Specific enterprise modeling elements that can facilitate capability planning and portfolio management are presented. These new modeling elements are being incorporated into an update of the Unified Architecture Framework, an OMG standard for modeling an enterprise.

show abstract

Section: Figure 1 Using Enterprise Portfolio Management To Help Trans...mentioning

confidence: 99%

Extending UAF for Model‐Based Capability Planning and Enterprise Portfolio Management

Martin

2022

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…31 Maier defines architecture as a set of decisions about the system, making systems architecting a decision-making process. 4 Simmons states that the systems architecting decisions typically are non-programmed decisions characterized as non-routine and illstructured and are generally solved by creativity, judgment, rules of thumb, and general problem-solving methods. 32 Moullec et al state that systems architecture decisions are difficult because of fuzziness and lack of information combined with often conflicting objectives.…”

Section: Systems Architecting and System-level Decision-makingmentioning

confidence: 99%

“…Madni describes systems architecting as an integrative, decision‐rich activity that requires continuous generation and evaluation of options 31 . Maier defines architecture as a set of decisions about the system, making systems architecting a decision‐making process 4 . Simmons states that the systems architecting decisions typically are non‐programmed decisions characterized as non‐routine and ill‐structured and are generally solved by creativity, judgment, rules of thumb, and general problem‐solving methods 32 .…”

Section: Literature Reviewmentioning

confidence: 99%

“…The concept selection requires the engineers to make system-level decisions about the architecture. The decisions made in the early phase are taken under high uncertainty and significantly impact the system design, deciding most of the systems' value, cost, and risk [4][5][6][7] As the cost of change becomes increasingly expensive as the system design matures, making the correct decisions in the early phase is key to viable system development. 8 System-level decisions are difficult due to fuzziness and lack of information combined with conflicting objective.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Conceptual modeling to support system‐level decision‐making: An industrial case study from the Norwegian energy domain

Engen

Müller

Falk

2022

Systems Engineering

View full text Add to dashboard Cite

This article explores conceptual modeling to support system‐level decision‐making during concept evaluation. The system‐level decisions made in the concept phases decide most of the systems' value and cost. The context for our research is the Norwegian energy domain. Through an industrial case study in a global subsea system supplier company, we have explored conceptual modeling to support system‐level decision‐making in the conceptual phase. From the insights and learnings gained in the industry case, the article proposes an approach for using conceptual modeling to support System‐Level Decision‐Making. Further, the article presents three examples of applications to demonstrate the use of the approach. To evaluate the approach's usefulness in the industrial setting, we conducted a survey of 37 engineers in the company of research. The engineers perceive that using the approach would improve awareness of the system context and support a holistic mindset. Furthermore, the engineers perceive the conceptual models as efficient for knowledge sharing and communication, especially in meetings between technical and non‐technical personnel. The engineers identify simplicity as a top benefit of the approach but also as a concern. Balancing the need for abstracting with the need for being specific is a crucial challenge in modeling. The survey also shows concerns about the implementation of the approach and the effort required to use the approach in daily work. The primary outcome of the research is insights into how conceptual modeling can support system‐level decision‐making in the industrial context.

show abstract

“…The importance of systems architecture is to enable a way to understand complex systems, to design and manage them, and to provide long-term rationality of decisions made early in the project [4]. In our paper, we follow Maier's definition [5], considering architecture as a set of decisions about the system, making architecting a decision-making process. The decisions made in the early phase of system development are what decide most of the system's value, cost, and risk.…”

Section: Introductionmentioning

confidence: 99%

The Need for Systems Awareness to Support Early-Phase Decision-Making—A Study from the Norwegian Energy Industry

Engen

Falk

Müller

2021

Systems

View full text Add to dashboard Cite

In this paper, we explore the need to improve systems awareness to support early-phase decision-making. This research uses the Norwegian energy industry as context. This industry deals with highly complex engineering systems that shall operate remotely for 25+ years. Through an in-depth study in a systems supplier company, we find that engineers are not sufficiently aware of the systems operational context and do not focus on the context in the early phase. We identified the lack of a holistic mindset and the challenge of balancing internal strategy and customers’ needs as the prevalent barriers. To support the concept evaluation, the subsea system suppliers need to raise systems awareness in the early phase. The study identifies four aspects that are important to consider when developing and implementing approaches to improve systems awareness in the early phase.

show abstract

Architecting a portfolio of systems

Cited by 6 publications

References 42 publications

Extending UAF for Model‐Based Capability Planning and Enterprise Portfolio Management

Extending UAF for Model‐Based Capability Planning and Enterprise Portfolio Management

Conceptual modeling to support system‐level decision‐making: An industrial case study from the Norwegian energy domain

The Need for Systems Awareness to Support Early-Phase Decision-Making—A Study from the Norwegian Energy Industry

Contact Info

Product

Resources

About