Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016)

A Pilot Study to Determine MBSE Utility for Process Modeling of Complex Interfaces

Modeling a full system or a complete interface between systems in a MBSE environment is a very large task and not all organizations will benefit enough from using MBSE to offset the effort that is required to do this. Completely modeling a system or interface is not necessary to evaluate the utility of MBSE for a specific application or organization. A small pilot can be executed over a short period of time that only models small portions of a system or interface and, if structured properly, this pilot can successfully demonstrate the utility of MBSE for an organization before having to invest a larger amount of resources to fully implement and deploy MBSE. This paper documents one such pilot that was conducted for NASAs Launch Services Program

A Pilot Study to Determine MBSE Utility for Process Modeling of Complex Interfaces

Modeling a full system or a complete interface between systems in a MBSE environment is a very large task and not all organizations will benefit enough from using MBSE to offset the effort that is required to do this. Completely modeling a system or interface is not necessary to evaluate the utility of MBSE for a specific application or organization. A small pilot can be executed over a short period of time that only models small portions of a system or interface and, if structured properly, this pilot can successfully demonstrate the utility of MBSE for an organization before having to invest a larger amount of resources to fully implement and deploy MBSE. This paper documents one such pilot that was conducted for NASA's Launch Services Program