Brian Sauser
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Brian Sauser has a total of 16 co-authors. Here are the top co-authors by number of shared publications:
- Art Pyster
Stevens Institute of Technology
2 shared publications - David Olwell
Naval Postgraduate School
2 shared publications - Don Gelosh
Department of Defense Crystal Mall 3, Suite 102 1851, S. Bell Street Arlington VA 22202
2 shared publications - Jim Anthony
DoD Contractor Support 1550 Crystal Drive, Suite 1004 Arlington VA 22202
2 shared publications A. Concho
Stevens Institute of Technology
1 shared publication- Alice Squires
Stevens Institute of Technology, Hoboken, NJ 07030
1 shared publication
Latest Publications
- 21 April 2011
- Published by Taylor & Francis in Technology Analysis & Strategic Management
- Vol. 23 (5) , 509-526
Optimal component substitution within system evolution planning considering multiple-vendor, functionally equivalent commercial products
The use of commercial-off-the-shelf components (COTS) in systems with long-term life cycles eventually affects system functionality. Such systems must undergo component substitutions to avoid component obsolescence and maintain the system operationally effective. While performing such substitutions, sustainment costs must be kept within projected budgets, and system and component evolution must seamlessly provide continued availability. However, planning system evolution while minimising costs becomes a competing resource allocation problem (even more so when multiple manufacturers offer functionally equivalent COTS that can satisfy the system requirements). This research presents a mathematical model for calculating system life cycle costs while considering different substitution alternatives, and proposes an optimisation approach and a network model to obtain an optimal substitution sequence based on a minimisation criteria of life cycle costs. It was observed that upgrading the system with available technologies often results in better affordability than keeping the same technologies for the entire system life cycle.
- 21 April 2011
- Published by Taylor & Francis in Technology Analysis & Strategic Management
- Vol. 23 (5) , 509-526
Optimal component substitution within system evolution planning considering multiple-vendor, functionally equivalent commercial products
The use of commercial-off-the-shelf components (COTS) in systems with long-term life cycles eventually affects system functionality. Such systems must undergo component substitutions to avoid component obsolescence and maintain the system operationally effective. While performing such substitutions, sustainment costs must be kept within projected budgets, and system and component evolution must seamlessly provide continued availability. However, planning system evolution while minimising costs becomes a competing resource allocation problem (even more so when multiple manufacturers offer functionally equivalent COTS that can satisfy the system requirements). This research presents a mathematical model for calculating system life cycle costs while considering different substitution alternatives, and proposes an optimisation approach and a network model to obtain an optimal substitution sequence based on a minimisation criteria of life cycle costs. It was observed that upgrading the system with available technologies often results in better affordability than keeping the same technologies for the entire system life cycle.
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 739-753
6.1.1 Applying Systems Thinking via Systemigrams™ for Defining the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) Project
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 739-753
6.1.1 Applying Systems Thinking via Systemigrams™ for Defining the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) Project
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 302-322
3.1.2 Exploring Resilience Measurement Methodologies
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 302-322
3.1.2 Exploring Resilience Measurement Methodologies
- Open Access
- 1 January 2010
- Published by Defense Technical Information Center (DTIC)
Applying Systems Thinking via Systemigrams(TM) for Defining the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) Project
Systems thinking is commonly accepted as the backbone of a successful systems engineering approach. As such, the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) team chose to leverage a systems thinking based tool called Systemitool, to describe our project to the vast audience that would potentially become involved directly or indirectly in the success of the project. This paper describes the process and steps used by the authors and the BKCASE team to develop the project's systemic diagram, or Systemigram, and the story behind the project, the products, and the vision of the BKCASE project. The goal of the paper is to provide guidance so that readers can leverage the lessons learned from this effort to successfully develop their own project definitions and stories.
- 1 January 2010
- Published by Defense Technical Information Center (DTIC)
Open AccessApplying Systems Thinking via Systemigrams(TM) for Defining the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) Project
Systems thinking is commonly accepted as the backbone of a successful systems engineering approach. As such, the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) team chose to leverage a systems thinking based tool called Systemitool, to describe our project to the vast audience that would potentially become involved directly or indirectly in the success of the project. This paper describes the process and steps used by the authors and the BKCASE team to develop the project's systemic diagram, or Systemigram, and the story behind the project, the products, and the vision of the BKCASE project. The goal of the paper is to provide guidance so that readers can leverage the lessons learned from this effort to successfully develop their own project definitions and stories.
- 1 July 2009
- Published by Wiley in INCOSE International Symposium
- Vol. 19 (1) , 1154-1166
7.3.2 Monte‐Carlo Simulation Approach for System Readiness Level Estimation
- 1 July 2009
- Published by Wiley in INCOSE International Symposium
- Vol. 19 (1) , 1154-1166
7.3.2 Monte‐Carlo Simulation Approach for System Readiness Level Estimation
- 1 December 2008
- Published by Taylor & Francis in Engineering Management Journal
- Vol. 20 (4) , 3-8
Taking Hold of System of Systems Management
Knowledge for managing projects, for the development of systems, has not kept pace with the increasing complexity and integration of the projects themselves. This increased complexity has permitted some to reason distinctions between systems projects and propose a form of system called a “system of system” (SoS). Faced with this situation, we argue that a single point solution cannot be the answer to how to manage these systems. We suggest the remedy is a form of project management predicated on four principles that underline SoS thinking: problem demystification, legacy assessment, state-space solutioning, and integration framework. Using these principles as a foundation, we provide a set of characteristics (i.e. autonomy, belonging, connectivity, diversity, and emergence) that can be applied as fundamental building blocks to actualize the management of an SoS, or any system. More importantly, we present an architecture predicated on the paradoxes that exist in realizing and formalizing these characteristics.
- 1 December 2008
- Published by Taylor & Francis in Engineering Management Journal
- Vol. 20 (4) , 3-8
Taking Hold of System of Systems Management
Knowledge for managing projects, for the development of systems, has not kept pace with the increasing complexity and integration of the projects themselves. This increased complexity has permitted some to reason distinctions between systems projects and propose a form of system called a “system of system” (SoS). Faced with this situation, we argue that a single point solution cannot be the answer to how to manage these systems. We suggest the remedy is a form of project management predicated on four principles that underline SoS thinking: problem demystification, legacy assessment, state-space solutioning, and integration framework. Using these principles as a foundation, we provide a set of characteristics (i.e. autonomy, belonging, connectivity, diversity, and emergence) that can be applied as fundamental building blocks to actualize the management of an SoS, or any system. More importantly, we present an architecture predicated on the paradoxes that exist in realizing and formalizing these characteristics.