A Model-Based Systems Engineering Methodology to Support Early Phase Australian Off-the-Shelf Naval Ship Acquisitions

A significant capability modernisation program and a wide-ranging review of Defence has meant that Australian naval ship acquisitions are now being undertaken with both increasing pace and increasing oversight. This comes at a time when naval ship acquisition has also swung away from the top-down approach of designing a ship to meet unique Australian requirements, to the strong preference to use off-the-shelf (OTS) ship designs from overseas. This situation creates a need for new approaches to support stakeholders with naval ship concept definition and acquisition methodologies (which include methods, tools, techniques, and processes) that can develop robust, defensible business cases for milestone decisions by government. This thesis addresses this important need through the construction of a structured Model-Based Systems Engineering (MBSE) methodology that combines ship design aspects with technical and trade-off analyses to enable evidence-based decision making by Defence and government on the preferred technical solution to a capability need. The research utilised the Constructive Research Approach to produce an artefact, the Middle-out Early-phase Above-the-line Naval Ship (MEANS) MBSE methodology. The methodology is focused on the Risk Mitigation and Requirements Setting Phase (early conceptual design) in the Australian Defence capability lifecycle as this is the key stage in determining the outcome of an acquisition project. Specifically, the MEANS MBSE methodology supports requirements definition through a concept and requirements exploration approach. This approach facilitates the definition of traceable, defensible requirements based on top-down requirements analysis and design space exploration, combined with a bottom-up market survey of the existing naval ship design space. Furthermore, the MEANS MBSE methodology uses multi-criteria decision making to provide robust evaluation of candidate OTS naval ship design options to select the preferred solution and identify design weaknesses, or relative deficiencies in each design. The MEANS MBSE methodology encourages design to take place in the modelling environment (as opposed to simply recording the design) and supports iterative “what-if” solution option analysis to evaluate proposed design changes. The research produced a validated, exemplar MBSE methodology, and a body of work on early-stage ship design approaches that together have much to offer Australian Defence for future ship acquisitions. Specifically, it extended the use of MBSE to establish, manage and guide early stage design and analysis activities, whilst simultaneously maintaining traceability to Defence strategic guidance and capability needs. This extension allows capability development stakeholders to demonstrate the links between strategy, design activities, and requirements definition, thereby making ‘contestability’ and Systems Engineering rigour inherent in the specification of the required naval ship. The novelty of the research arises from the novel synthesis of several proven system design and analysis methods into a bespoke MBSE methodology that provides unique functionality and assistance to ship acquisition stakeholders. The thesis is presented in a combined conventional narrative and publications format, with the publications upon which the body of the thesis is based included in the appendices.Thesis (Ph.D.) -- University of Adelaide, Entrepreneurship, Commercialisation and Innovation Centre, 201

MBSE METHODOLOGY AND ANALYSIS TOOL TO IMPLEMENT MBSE POST MILESTONE C

This thesis proposes a model-based systems engineering (MBSE) methodology to be implemented post Milestone C, develops a Microsoft Excel MBSE analysis tool which provides a recommendation to implement MBSE, and provides a case study for implementing MBSE post Milestone C on a Department of Defense (DoD) acquisition program. The purpose of the MBSE methodology is to identify how MBSE should be implemented post Milestone C to address the systemic challenges which are faced by DoD acquisition programs post Milestone C. The Excel MBSE analysis tool provides a set of questions which provide metrics to the program office to determine the benefit of implementing MBSE post Milestone C into their program. The thesis then details, through a case study, how the Excel MBSE analysis tool can be used to decide whether to implement MBSE. Prior research on the systemic challenges within DoD acquisition programs as well as the use of MBSE during post Milestone C activities were leveraged in developing the proposed MBSE methodology and Excel MBSE analysis tool. The thesis makes a recommendation to implement MBSE post Milestone C to mitigate schedule, cost, and risk uncertainties. This is done through digitally linking various models, such as a manufacturing model and a logistics model to an integrated master schedule (IMS). Based on the metrics and cost, the Excel MBSE analysis tool provides a recommendation on which models should be implemented.http://archive.org/details/mbsemethodologya1094560439Civilian, Department of the NavyApproved for public release; distribution is unlimited

Technical Data Interoperability (TDI) Pathfinder Via Emerging Standards

The TDI project (TDI) investigates trending technical data standards for applicability to NASA vehicles, space stations, payloads, facilities, and equipment. TDI tested COTS software compatible with a certain suite of related industry standards for capabilities of individual benefits and interoperability. These standards not only esnable Information Technology (IT) efficiencies, but also address efficient structures and standard content for business processes. We used source data from generic industry samples as well as NASA and European Space Agency (ESA) data from space systems

Tradespace and Affordability – Phase 1

One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering – “SE Transformation.” The Grand Challenge goal for SE Transformation is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, outside-in, document-driven, point-solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, balanced outside-in and inside-out, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

System Development and Risk Propagation in Systems-of-Systems

Proceedings Paper (for Acquisition Research Program)The emphasis of the Department of Defense on capability-based acquisition has led to the simultaneous development of systems that must eventually interact within a system-of-systems. Thus, system development and acquisition processes encounter interdependencies that generate complexity and risk. The authors'' prior work has developed a Computational Exploratory Model to simulate the development processes of these complex networks of systems intended for a system-of-systems capability. The model''s goal is to understand the impact of system-specific risk and system interdependencies on development time. The progress documented in this paper focuses on the quantification of risk propagation and the impact of network topologies on the propagation of disruptions. The improved model enables trade studies that differentiate the effectiveness of alternate configurations of constituent systems and that quantify the impact of varying levels of interdependencies on the timely completion of a project that aims to achieve a desired capability level.Naval Postgraduate School Acquisition Research ProgramApproved for public release; distribution is unlimited

Tradespace and Affordability – Phase 2

MOTIVATION AND CONTEXT: One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering – “SE Transformation.” The Grand Challenge goal for SE Transformation is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, outside-in, document-driven, point-solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, balanced outside-in and inside-out, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

System engineering for radio frequency communication consolidation with parabolic antenna stacking

2020 Fall.Includes bibliographical references.This dissertation implements System Engineering (SE) practices while utilizing Model Based System Engineering (MBSE) methods through software applications for the design and development of a parabolic stacked antenna. Parabolic antenna stacking provides communication system consolidation by having multiple antennas on a single pedestal which reduces the number of U.S. Navy shipboard topside antennas. The dissertation begins with defining early phase system lifecycle processes and the correlation of these early processes to activities performed when the system is being developed. Performing SE practices with the assistance of MBSE, Agile, Lean methodologies and SE / engineering software applications reduces the likelihood of system failure, rework, schedule delays, and cost overruns. Using this approach, antenna system consolidation via parabolic antenna stacking is investigated while applying SE principles and utilizing SE software applications. SE / engineering software such as IBM Rational Software, Innoslate, Antenna Magus, ExtendSim, and CST Microwave Studio were used to perform SE activities denoted in ISO, IEC, and IEEE standards. A method to achieve multi-band capabilities on a single antenna pedestal in order to reduce the amount of U.S. Navy topside antennas is researched. An innovative approach of parabolic antenna stacking is presented to reduce the amount of antennas that take up physical space on shipboard platforms. Process simulation is presented to provide an approach to improve predicting delay times for operational availability measures and to identify process improvements through lean methodologies. Finally, this work concludes with a summary and suggestions for future work

System Qualities Ontology, Tradespace and Affordability (SQOTA) Project – Phase 4

This task was proposed and established as a result of a pair of 2012 workshops sponsored by the DoD Engineered Resilient Systems technology priority area and by the SERC. The workshops focused on how best to strengthen DoD’s capabilities in dealing with its systems’ non-functional requirements, often also called system qualities, properties, levels of service, and –ilities. The term –ilities was often used during the workshops, and became the title of the resulting SERC research task: “ilities Tradespace and Affordability Project (iTAP).” As the project progressed, the term “ilities” often became a source of confusion, as in “Do your results include considerations of safety, security, resilience, etc., which don’t have “ility” in their names?” Also, as our ontology, methods, processes, and tools became of interest across the DoD and across international and standards communities, we found that the term “System Qualities” was most often used. As a result, we are changing the name of the project to “System Qualities Ontology, Tradespace, and Affordability (SQOTA).” Some of this year’s university reports still refer to the project as “iTAP.”This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant of Defense for Research and Engineering (ASD(R&E)) under Contract HQ0034-13-D-0004.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant of Defense for Research and Engineering (ASD(R&E)) under Contract HQ0034-13-D-0004

MH-60 Seahawk / MQ-8 Fire Scout interoperability

Approved for public release; distribution is unlimitedAs part of a Naval Postgraduate School's capstone project in Systems Engineering, a project team from Cohort 311-0911 performed a Systems Engineering analysis. This Project focused on defining alternatives for enhanced Anti-Surface Warfare (ASUW) mission effectiveness through increased interoperability and integration for the Fire Scout Unmanned Air Vehicle and Seahawk helicopter. Specifically, the Project explored the available trade space for enhancing communications back to the ship for analysis and decision-making. Modeling and Simulation (MandS) was used to assess the impact of enhanced communication on specific Key performance Parameters (KPPs) and Measures of Effectiveness (MOEs) associated with the ASUW mission. Once the trade space was defined, alternatives were analyzed and a recommendation provided that supports near-, mid-, and long-term mission enhancement

Expanded Guidance for NASA Systems Engineering. Volume 2: Crosscutting Topics, Special Topics, and Appendices

Historically, most successful NASA projects have depended on effectively blending project management, systems engineering, and technical expertise among NASA, contractors, and third parties. Underlying these successes are a variety of agreements (e.g., contract, memorandum of understanding, grant, cooperative agreement) between NASA organizations or between NASA and other Government agencies, Government organizations, companies, universities, research laboratories, and so on. To simplify the discussions, the term "contract" is used to encompass these agreements. This section focuses on the NASA systems engineering activities pertinent to awarding a contract, managing contract performance, and completing a contract. In particular, NASA systems engineering interfaces to the procurement process are covered, since the NASA engineering technical team plays a key role in the development and evaluation of contract documentation. Contractors and third parties perform activities that supplement (or substitute for) the NASA project technical team accomplishment of the NASA common systems engineering technical process activities and requirements outlined in this guide. Since contractors might be involved in any part of the systems engineering life cycle, the NASA project technical team needs to know how to prepare for, allocate or perform, and implement surveillance of technical activities that are allocated to contractors