Identifying Knowledge, Skill, and Ability Requirements for 33Sx Officers in Deployed Environments

Military operations in the past, present, and future are highly dependent on the timely distribution of accurate information; the only thing really changing is the speed and means of which it is dispersed. As we proceed forward in the information age, technology and the men and women responsible for it will play an ever increasing role in getting the right information in the right place at the right time. As the United States Air Force continues to transform into an ever increasing expeditionary service the knowledge, skills, and abilities of Air Force officers must transform as well to meet the evolving needs of combatant commanders. 33S officers perform garrison duties in many different capacities; current duty position or past experience thus does not guarantee we have acquired the knowledge, skills and abilities necessary to succeed when and where it matters most. Hence, the purpose of this research is to identify core skill sets in the form of knowledge, skills, and abilities, which are most important to Communication and Information (AFSC 33S) Officers to successfully carry out assigned duties in forward operating locations

A Conceptual Framework for Analysis of System Safety Interoperability of United States Navy\u27s Combat Systems

Today\u27s political and military reality requires the optimal use of our legacy systems. The objective is to maximize the effectiveness of our operations by efficient allocation, placement and the use of our forces and war-fighting systems. The synergism drawn from the capabilities of the legacy complex systems enables today\u27s war-fighting needs to be met without substantial increase in cost or resources. This synergism can be realized by the effective integration and interoperation of legacy systems into a larger, more complex system of systems. However, the independently developed legacy systems in this new tactical environment often have different data types, languages, data modeling, operating systems, etc. These differences are impediments to the requirement for interoperability, and can create an environment of confusion, misinformation and certainly un-interoperability, hence hinder the safe interoperation of the metasystem and potentially increase the risk for mishaps. Safe interoperability capability assures that the mission objectives are achieved not only effectively but also safely. The System Safety Interoperability Framework (SSIF) introduced in this dissertation provides the framework for the engineering community to evaluate, from system safety perspective, the interoperability issues between multiple complex systems in the U.S. Navy\u27s system of systems context. SSIF characterization attributes are System of Systems (SoS) tactical environment, SoS Engineering, SoS Safety Engineering, and Safety Critical Data. SSIF is applied to AEGIS Ballistic Missile Defense 3.0 Program to explore and analyze the safety interoperability issues in the overall system, by which the SSIF is further validated as an effective approach in analyzing the safe interoperability capability in Navy\u27s combat systems

Using operational risk to increase systems engineering effectiveness

Includes bibliographical references.2016 Summer.A key activity in the systems engineering process is managing risk. Systems engineers transform end-user needs into requirements that then drive design, development, and deployment activities. Experienced systems engineers are aware of both programmatic risk and technical risk and how these risks impact program outcomes. A programmatic change to cost, schedule, process, team structure, or a wide variety of other elements may impact the engineering effort and increase the risk of failing to deliver a product or capability when needed, with all required functionality, at the promised cost. Technical challenges may introduce risk as well. If a subcomponent or element of the design is immature or doesn’t perform as expected, additional effort may be required to redesign the element or may even necessitate a change in requirements or a complete system re-design. Anticipating programmatic and technical risks and implementing plans to mitigate these risks is part of the systems engineering process. Even with a potent risk management process in place, end-users reject new capabilities when the iii delivered capabilities fail to perform to their expectations or fail to address the end-user’s operational need. The time between the identification of an operational need and the delivery of the resulting capability may be months or even years. When delivered, the new capability either does not fulfil the original need or the need has evolved over time. This disconnect increases operational risk to the end-user’s mission or business objectives. When systems engineers explicitly identify and mitigate operational risk, in addition to programmatic and technical risk, program outcomes are more likely to meet the end-user’s real operational need. The purpose of this research is first to define the activities that could be used by systems engineers to ensure that engineering activities are influenced by operational risk considerations. Secondly, to determine if a focus on operational risk during the systems engineering lifecycle has a positive impact on program outcomes. A structured approach to addressing operational risk during the systems engineering process, Operational Risk-Driven Engineering Requirements/Engineering Development (ORDERED), is introduced. ORDERED includes an exhaustive operational risk taxonomy designed to assist systems engineers with incorporating the end-user’s evolving operational risk considerations into systems engineering activities. iv To examine the relationship between operational risk considerations during the systems engineering process and program outcomes, a survey instrument was developed and administered. In addition, a system dynamics model was developed to examine the relationship between operational risk and technical debt. Finally, case studies of successful and challenged programs were evaluated against characteristics of successfully addressing operational risk during the program lifecycle. These activities lead to the conclusion that a focus on operational risk during the systems engineering lifecycle has a positive impact on program outcomes

NASA Risk Management Handbook

The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced

Space shuttle avionics system

The Space Shuttle avionics system, which was conceived in the early 1970's and became operational in the 1980's represents a significant advancement of avionics system technology in the areas of systems and redundacy management, digital data base technology, flight software, flight control integration, digital fly-by-wire technology, crew display interface, and operational concepts. The origins and the evolution of the system are traced; the requirements, the constraints, and other factors which led to the final configuration are outlined; and the functional operation of the system is described. An overall system block diagram is included

Department of Defense Dictionary of Military and Associated Terms

The Joint Publication 1-02, Department of Defense Dictionary of Military and Associated Terms sets forth standard US military and associated terminology to encompass the joint activity of the Armed Forces of the United States. These military and associated terms, together with their definitions, constitute approved Department of Defense (DOD) terminology for general use by all DOD components

CONDITION-BASED UNMANNED UNDERSEA VEHICLE MAINTENANCE MONITORING AND PREDICTION SYSTEM (C-BUMMPS)

As the Navy introduces its large displacement and extra-large class Unmanned Undersea Vehicles (UUVs), the need and desire grows for increased endurance on the order of weeks to months. Extended endurance is a necessary capability to enable UUVs to take on some of the mission areas of nuclear submarines. Energy efficiency and storage capacity are some of the first factors to be considered for extending the endurance of unmanned vehicles. However, a secondary and more challenging factor is UUV system reliability, and the ability to tolerate or avoid system failures. The intent of this project is to capture the stakeholder needs for improving UUV reliability, maintainability, and availability, then transform those needs into system requirements for a Condition-Based UUV Maintenance Monitoring and Prediction System (C-BUMMPS). Specifically, this project will develop and identify stakeholder, system functional, and system non-functional requirements. A C-BUMMPS architecture is developed to address the stakeholders’ needs. The developed architecture will consist of on-board sensing, monitoring, and processing elements on the UUV, in addition to ashore testing, data analytics, and maintenance activities needed to support the maturation of the C-BUMMPS. This project will utilize a model based systems engineering (MBSE) approach, and Innoslate was chosen as the desired MBSE tool. As such, certain views will be developed to depict the C-BUMMPS architecture from various perspectives.Civilian, Department of the NavyCivilian, Department of the NavyCivilian, Department of the NavyCivilian, Department of the NavyApproved for public release. Distribution is unlimited

A system engineering study and concept development for a Humanitarian Aid and Disaster Relief Operations Management Platform

This thesis develops a concept and initial system definition of a Humanitarian Aid and Disaster Relief (HADR) Operations Management Platform (OMP) that supports various stakeholders involved in time critical humanitarian response efforts. The concept for the OMP explores the various functions necessary to manage HADR operations to include facilitation of information exchange, collaboration among disaster responders, and a common operating picture (COP) that informs decision makers of the operational environment. The development of the OMP uses system engineering methodologies and a tailored development process to identify the requirements, functions, and architecture necessary to support the platform. The OMP concept also includes multiple data sources for near real-time information and support tools for assessments, planning, implementation, execution, and evaluation. This thesis also assesses advances in technology and applications to more effectively support and manage HADR efforts. As such, the OMP takes into consideration how current HADR operations are conducted today, and the role of virtual volunteers in supporting the platform. These virtual volunteers support the HADR effort by conducting tasks virtually via their computers and an internet connection anywhere in the world.http://archive.org/details/asystemengineeri1094550472Captain, United States Air ForceApproved for public release; distribution is unlimited

Assessment of avionics technology in European aerospace organizations

This report provides a summary of the observations and recommendations made by a technical panel formed by the National Aeronautics and Space Administration (NASA). The panel, comprising prominent experts in the avionics field, was tasked to visit various organizations in Europe to assess the level of technology planned for use in manufactured civil avionics in the future. The primary purpose of the study was to assess avionics systems planned for implementation or already employed on civil aircraft and to evaluate future research, development, and engineering (RD&E) programs, address avionic systems and aircraft programs. The ultimate goal is to ensure that the technology addressed by NASa programs is commensurate with the needs of the aerospace industry at an international level. The panel focused on specific technologies, including guidance and control systems, advanced cockpit displays, sensors and data networks, and fly-by-wire/fly-by-light systems. However, discussions the panel had with the European organizations were not limited to these topics