SEARCH · Engineering Papers

Results for “Secure by Design”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS2007

Flutter Analysis of the Shuttle Tile Overlay Repair Concept

The Space Shuttle tile overlay repair concept, developed at the NASA Johnson Space Center, is designed for on-orbit installation over an area of damaged tile to permit safe re-entry. The thin flexible plate is placed over the damaged area and secured to tile at discreet points around its perimeter. A series of flutter analyses were performed to determine if the onset of flutter met the required safety margins. Normal vibration modes of the panel, obtained from a simplified structural analysis of the installed concept, were combined with a series of aerodynamic analyses of increasing levels of fidelity in terms of modeling the flow physics to determine the onset of flutter. Results from these analyses indicate that it is unlikely that the overlay installed at body point 1800 will flutter during re-entry.

Bey, Kim S.↗

NASA NTRS2007

Large-Scale Cryogen Systems and Test Facilities

NASA has completed initial construction and verification testing of the Integrated Systems Test Facility (ISTF) Cryogenic Testbed. The ISTF is located at Complex 20 at Cape Canaveral Air Force Station, Florida. The remote and secure location is ideally suited for the following functions: (1) development testing of advanced cryogenic component technologies, (2) development testing of concepts and processes for entire ground support systems designed for servicing large launch vehicles, and (3) commercial sector testing of cryogenic- and energy-related products and systems. The ISTF Cryogenic Testbed consists of modular fluid distribution piping and storage tanks for liquid oxygen/nitrogen (56,000 gal) and liquid hydrogen (66,000 gal). Storage tanks for liquid methane (41,000 gal) and Rocket Propellant 1 (37,000 gal) are also specified for the facility. A state-of-the-art blast proof test command and control center provides capability for remote operation, video surveillance, and data recording for all test areas.

Johnson, R. G.↗

NASA NTRSDate not supplied

The State of Cryptolib – The Open-Source Satellite Cryptography Library

What state would the world be in if all internet traffic was unencrypted? Imagine an alternate universe where you can plug a packet sniffing device into your home internet and capture the web traffic of the entire world. It seems obvious that this scenario is less than desirable. If we would not allow this for the internet, why would we allow this in the space domain? With the advent of open-source ground stations, commercial off the shelf hardware, and ground stations as a service, the barrier to entry for space communications is rapidly lowering. New players enter the space realm everydayevery day, and the presence of tools to allow apprentice evildoers the ability to exploit satellite communications is on the horizon. Not only are legacy missions at risk, but future missions are as well - particularly lower budget science missions with more stringent sciencesize, weight, and power constraints. that may find it difficult to utilize hardware-based encryption solutions. In terms of Civilian Aerospace, NASA Standard 1006 generally directs that missions "shall protect the command stack with encryption that meets or exceeds Federal Information Processing Standards (FIPS) 140". Fortunately, the Consultative Committee for Space Data Systems (CCSDS) has published an international standard on Space Data Link Security. The combination of these two forces has resulted in CryptoLib - an open-source, C-based, encryption library that aims to be CCSDS SDLS compliant. CryptoLib is designed to support smaller missions on a tight budget that may be subject to the more stringent command link encryption requirements. Additionally, CryptoLib serves as an underpinning in JPL's Key Management & Cryptography (KMC) suite and is also designed to function as a 'drop-in' for smaller missions. CryptoLib is in active development and currently provides Telecommand (TC), Telemetry (TM), and Advanced Orbiting Systems (AOS) encryption and decryption capabilities with a variety of encryption and authentication schemes. This presentation will report the latest features, current status, and future plans for CryptoLib.

open-source encryption↗

NASA NTRSDate not supplied

The State of CryptoLib – The Open-Source Satellite Cryptography Library

open-source encryption↗

NASA NTRS2005

Documentation: No Substitute for Communication

SO WHAT IS AN RFI? IT WAS ONE OF THE FIRST THINGS I learned about back when I started my project management career with my first large construction firm. I learned how to use these forms as a convenient and effective means of documenting the many legitimate clarifications needed on a major project. However, like most other young engineers, I also learned to use the RFI as a weapon in the ongoing battle between owners. or their designer and the construction contractors. Recently, our project team has done a few simple things to greatly reduce the waste and frustration that comes from this type of battle. The RFI form can be a great tool if used properly, and I certainly don t recommend that they be eliminated entirely. The RFI form was created to document the many clarifications that are commonly required on projects. Typically, the contractor uses the top half of the form to clarify-or request permission to vary from-the contract documents. The bottom half of the form is used to record the answer. But this seemingly simple process is plagued by a number of problems. From the contractor s perspective, RFIs are needed to secure information that should have been in the contract documents in the first place. The missing information keeps their crews from working effectively, and it makes hitting already demanding cost and schedule targets even more difficult. Owners, or their design firms, often view the RFI as a means of harassment. Both sides of the issue have legitimate complaints, and both sides cause most of their own pain.

Strickland, John↗

NASA NTRS2009

Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits and difficulties that a migration to cloud-based computing philosophies has uncovered when compared to the legacy Mission Control Center architecture. The team consists of system and software engineers with extensive experience with the MCC infrastructure and software currently used to support the International Space Station (ISS) and Space Shuttle program (SSP).

Martin, Keith↗

NASA NTRS1991

National Launch System Space Transportation Main Engine

The present liquid-oxygen/liquid-hydrogen engine is described as meeting the specific requirements of the National Launch System (NLS) Program including cost-effectiveness and robustness. An overview of the NLS and its objectives is given which indicates that the program aims to develop a flexible launch system to meet security, civil, and commercial needs. The Space Transportation Main Engine (STME) provides core and boost propulsion for the 1.5-stage vehicle and core propulsion for the solid booster vehicle. The design incorporates step-throttling, order-of-magnitude reductions in welds, and configuration targets designed to optimize robustness. The STME is designed to provide adaptable and dependable propulsion while minimizing recurring costs and is designed to meet the needs of NLS and other typical space-transportation programs currently being planned.

Hoodless, Ralph M., Jr.↗

NASA NTRS1995

Reusable launch vehicle: Technology development and test program

The National Aeronautics and Space Administration (NASA) requested that the National Research Council (NRC) assess the Reusable Launch Vehicle (RLV) technology development and test programs in the most critical component technologies. At a time when discretionary government spending is under close scrutiny, the RLV program is designed to reduce the cost of access to space through a combination of robust vehicles and a streamlined infrastructure. Routine access to space has obvious benefits for space science, national security, commercial technologies, and the further exploration of space. Because of technological challenges, knowledgeable people disagree about the feasibility of a single-stage-to-orbit (SSTO) vehicle. The purpose of the RLV program proposed by NASA and industry contractors is to investigate the status of existing technology and to identify and advance key technology areas required for development and validation of an SSTO vehicle. This report does not address the feasibility of an SSTO vehicle, nor does it revisit the roles and responsibilities assigned to NASA by the National Transportation Policy. Instead, the report sets forth the NRC committee's findings and recommendations regarding the RLV technology development and test program in the critical areas of propulsion, a reusable cryogenic tank system (RCTS), primary vehicle structure, and a thermal protection system (TPS).

Source record↗

NASA NTRS2009

Developing a Standard Method for Link-Layer Security of CCSDS Space Communications

Communications security for space systems has been a specialized field generally far removed from considerations of mission interoperability and cross-support in fact, these considerations often have been viewed as intrinsically opposed to security objectives. The space communications protocols defined by the Consultative Committee for Space Data Systems (CCSDS) have a twenty-five year history of successful use in over 400 missions. While the CCSDS Telemetry, Telecommand, and Advancing Orbiting Systems protocols for use at OSI Layer 2 are operationally mature, there has been no direct support within these protocols for communications security techniques. Link-layer communications security has been successfully implemented in the past using mission-unique methods, but never before with an objective of facilitating cross-support and interoperability. This paper discusses the design of a standard method for cryptographic authentication, encryption, and replay protection at the data link layer that can be integrated into existing CCSDS protocols without disruption to legacy communications services. Integrating cryptographic operations into existing data structures and processing sequences requires a careful assessment of the potential impediments within spacecraft, ground stations, and operations centers. The objective of this work is to provide a sound method for cryptographic encapsulation of frame data that also facilitates Layer 2 virtual channel switching, such that a mission may procure data transport services as needed without involving third parties in the cryptographic processing, or split independent data streams for separate cryptographic processing.

Biggerstaff, Craig↗

NASA NTRS2011

Kennedy Space Center ITC-1 Internship Overview

As an intern for Priscilla Elfrey in the ITC-1 department, I was involved in many activities that have helped me to develop many new skills. I supported four different projects during my internship, which included the Center for Life Cycle Design (CfLCD), SISO Space Interoperability Smackdown, RTI Teacher Mentor Program, and the Discrete Event Simulation Integrated Visualization Environment Team (DIVE). I provided the CfLCD with web based research on cyber security initiatives involving simulation, education for young children, cloud computing, Otronicon, and Science, Technology, Engineering, and Mathematics (STEM) education initiatives. I also attended STEM meetings regarding simulation courses, and educational course enhancements. To further improve the SISO Simulation event, I provided observation feedback to the technical advisory board. I also helped to set up a chat federation for HLA. The third project involved the RTI Teacher Mentor program, which I helped to organize. Last, but not least, I worked with the DIVE team to develop new software to help visualize discrete event simulations. All of these projects have provided experience on an interdisciplinary level ranging from speech and communication to solving complex problems using math and science.

Ni, Marcus↗

NASA NTRS2016

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

NASA NTRSDate not supplied

Enabling Model Organism and Commercial Astronaut Data Access Through the NASA Open Science Data Repository

NASA’s Open Science Data Repository (OSDR) brings together omics data from NASA’s GeneLab project and non-omics data, including physiological, phenotypic, imaging, and behavioral data from NASA’s Ames Life Sciences Data Archive (ALSDA) collected from decades of space biology research, providing open and FAIR (findable, accessible, interoperable, and reusable) access of these precious data to scientists world-wide. This rich source of meticulously curated metadata and data from spaceflight and analog studies has been mined by the scientific community resulting in dozens of high impact scientific publications that reveals a complex network of molecular and physiological effects of spaceflight across living systems, from microbes to plants, to mammals. Understanding how these effects translate to the human condition is critical as we move deeper into the era of commercial space travel. However, the integration of data, specifically omics data, from astronauts is particularly challenging due to their sensitive nature. OSDR has risen to this challenge by developing a mechanism to control access to identifiable levels of omics data, such as raw sequence data, while enabling public access to processed, unidentifiable, data and associated metadata that will allow the scientific community to interrogate human astronaut data alongside data from model organisms to begin answering these critical questions. The 2021 SpaceX Inspiration4 (I4) mission collected a comprehensive atlas of biological measurements from four civilian astronauts, providing a wealth of data to characterize the effects of spaceflight on the human body. These data include both non-omics and omics assays such as direct RNA sequencing (RNA-seq), single nuclei ATAC-seq and RNA-seq, metagenomics, proteomics, and comprehensive metabolic and cytokine panels, all of which have been integrated into the OSDR system across no less than 9 studies. Each study has been carefully curated using community-backed OSDR standards for sample and assay level metadata ensuring these data are findable and accessible. In addition to hosting both raw and processed data from the principal investigator team for each assay type, the GeneLab team plans to re-process the I4 omics data using GeneLab’s standard processing pipelines. The GeneLab processed data outputs will allow for comparisons across studies on OSDR and enable visualization of these data through the OSDR data visualization platform thereby enabling data reusability and interoperability. Here we describe the robust privacy and security protocols implemented by OSDR to safeguard sensitive health data from astronauts while facilitating metadata and processed data sharing for research purposes. We further provide a road map for navigating the vast amount of data provided for each I4 study on the OSDR, including experimental design, associated experiments, payloads, and missions, data generation and analysis protocols, and associated scientific articles. Additionally, we illustrate how to interrogate the standardized metadata provided in the sample and assay tables as well as various means to download and access the data including programmatically through the GeneLab Open API (GLOpenAPI). The open access of datasets in NASA’s OSDR provides a unique opportunity for the scientific community, as well as citizen scientists and students, to continue using OSDR resources to further unlock profound insights into the consequences of space travel on the human body. Through implementation of security measures to protect sensitive human data, the OSDR seeks to strengthen the science exchange between the Biological and Physical Sciences Program and the Human Research Program, per recommendation 4-1 of the 2023-2032 Decadal Survey, and encourage further sharing and dissemination of astronaut data to provide the scientific community with the resources needed to lay the groundwork for developing targeted mitigation strategies to help withstand the rigors of long-duration spaceflight.

Amanda Marie Saravia-butler↗

NASA NTRS1985

ACCESS (Assembly Concept for Construction of Erectable Space Structure) - A Shuttle flight experiment

ACCESS is a planned Shuttle flight experiment to assess the potential of an on-orbit construction concept designed for efficient manual assembly of a space truss. The experiment, which is scheduled for launch November 27, 1985, on the Space Transportation System (STS) flight 61-B, uses two astronauts secured in fixed foot restraints located in the Shuttle cargo bay to assemble a 45-foot long aluminum truss beam from 93 tubular struts and 33 nodal joints. Neutral buoyancy simulations of the flight experiment indicate the truss can be assembled in less than thirty minutes. Structural assembly, structural repair, flexible cable attachment and manual manipulation of the truss is also planned for the experiment using an astronaut secured in the Manipulator Foot Restraint attached to the Remote Manipulator System arm. Flight assembly data will be generated for correlation of the neutral buoyancy ground test data. This paper describes the ACCESS flight experiment and presents results of the neutral buoyancy development and training tests.

Heard, W. L., Jr.↗

NASA NTRS2009

High-Temperature Modal Survey of a Hot-Structure Control Surface

NASA Dryden is directing a program to test a Carbon-Silicon Carbide (C/SiC) Ruddervator Subcomponent Test Article (RSTA). The RSTA is a truncated version of the full-scale X-37 hot-structure control surface incorporating all major features including the metallic spindle and five major C/SiC quasi isotropic lay-up components secured with C/SiC fasteners. As part of NASA's Aeronautics Research Mission Directorate Hypersonics program, the RSTA will undergo thermal-structural testing to develop an extensive database for future structural design and analysis methodology validation. Ground Vibration Tests (GVTs) are routinely conducted for model validation in supporting flutter analysis for subsonic and supersonic vehicles; however, for hypersonic vehicle applications, GVT techniques are not well-established. New fabrication technologies, high-temperature materials systems, and sensors offer new opportunities to develop techniques for performing GVTs at elevated temperatures. The RSTA is comprised of materials whose stiffness both increases and decreases with increasing temperature. The impact of this type of material system interaction must be understood as it will ultimately affect hypersonic flutter analysis. The test objectives are to perform room-temperature GVTs, develop the capability to conduct high-temperature GVTs and to compare and generate an understanding of the modal characteristics which capture RSTA's material interaction when subjected to temperature varying conditions.

Spivey, Natalie D.↗

NASA NTRS2011

Flying Unmanned Aircraft: A Pilot's Perspective

The National Aeronautics and Space Administration (NASA) is pioneering various Unmanned Aircraft System (UAS) technologies and procedures which may enable routine access to the National Airspace System (NAS), with an aim for Next Gen NAS. These tools will aid in the development of technologies and integrated capabilities that will enable high value missions for science, security, and defense, and open the door to low-cost, extreme-duration, stratospheric flight. A century of aviation evolution has resulted in accepted standards and best practices in the design of human-machine interfaces, the displays and controls of which serve to optimize safe and efficient flight operations and situational awareness. The current proliferation of non-standard, aircraft-specific flight crew interfaces in UAS, coupled with the inherent limitations of operating UAS without in-situ sensory input and feedback (aural, visual, and vestibular cues), has increased the risk of mishaps associated with the design of the "cockpit." The examples of current non- or sub- standard design features range from "annoying" and "inefficient", to those that are difficult to manipulate or interpret in a timely manner, as well as to those that are "burdensome" and "unsafe." A concerted effort is required to establish best practices and standards for the human-machine interfaces, for the pilot as well as the air traffic controller. In addition, roles, responsibilities, knowledge, and skill sets are subject to redefining the terms, "pilot" and "air traffic controller", with respect to operating UAS, especially in the Next-Gen NAS. The knowledge, skill sets, training, and qualification standards for UAS operations must be established, and reflect the aircraft-specific human-machine interfaces and control methods. NASA s recent experiences flying its MQ-9 Ikhana in the NAS for extended duration, has enabled both NASA and the FAA to realize the full potential for UAS, as well as understand the implications of current limitations. Ikhana is a Predator-B/Reaper UAS, built by General Atomics, Aeronautical Systems, Inc., and modified for research. Since 2007, the aircraft has been flown seasonally with a wing-mounted pod containing an infrared scanner, utilized to provide real-time wildfire geo-location data to various fire-fighting agencies in the western U.S. The multi-agency effort included an extensive process to obtain flight clearance from the FAA to operate under special provisions, given that UAS in general do not fully comply with current airspace regulations (e.g. sense-and-avoid requirements).

Pestana, Mark E.↗

NASA NTRS2011

L-Band System Engineering - Concepts of Use, Systems Performance Requirements, and Architecture

This document is being provided as part of ITT s NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract NNC05CA85C, Task 7: New ATM Requirements-Future Communications, C-band and L-band Communications Standard Development. Task 7 was motivated by the five year technology assessment performed for the Federal Aviation Administration (FAA) under the joint FAA-EUROCONTROL cooperative research Action Plan (AP-17), also known as the Future Communications Study (FCS). It was based on direction provided by the FAA project-level agreement (PLA FY09_G1M.02-02v1) for "New ATM Requirements-Future Communications." Task 7 was separated into two distinct subtasks, each aligned with specific work elements and deliverable items. Subtask 7-1 addressed C-band airport surface data communications standards development, systems engineering, test bed development, and tests/demonstrations to establish operational capability for what is now referred to as the Aeronautical Mobile Airport Communications System (AeroMACS). Subtask 7-2, which is the subject of this report, focused on preliminary systems engineering and support of joint FAA/EUROCONTROL development and evaluation of a future L-band (960 to 1164 MHz) air/ground (A/G) communication system known as the L-band digital aeronautical communications system (L-DACS), which was defined during the FCS. The proposed L-DACS will be capable of providing ATM services in continental airspace in the 2020+ timeframe. Subtask 7-2 was performed in two phases. Phase I featured development of Concepts of Use, high level functional analyses, performance of initial L-band system safety and security risk assessments, and development of high level requirements and architectures. It also included the aforementioned support of joint L-DACS development and evaluation, including inputs to L-DACS design specifications. Phase II provided a refinement of the systems engineering activities performed during Phase I, along with continued joint FAA/EUROCONTROL L-DACS development and evaluation support.

Henriksen, Stephen↗

NASA NTRS2012

RS-34 Phoenix (Peacekeeper Post Boost Propulsion System) Utilization Study

The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) in conjunction with Pratt & Whitney Rocketdyne conducted a study to evaluate potential in-space applications for the Rocketdyne produced RS-34 propulsion system. The existing RS-34 propulsion system is a remaining asset from the decommissioned United States Air Force Peacekeeper ICBM program; specifically the pressure-fed storable bipropellant Stage IV Post Boost Propulsion System, renamed Phoenix. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in October 2009. RS-34 propulsion system components were harvested from stages supplied by the USAF and used on the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC is working closely with the USAF to obtain all the remaining RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Phoenix Utilization Study sought to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions: 1) small satellite delivery (SSD), 2) orbital debris removal (ODR), 3) ISS re-supply, 4) SLS kick stage, 5) manned GEO servicing precursor mission, and an Earth-Moon L-2 Waypoint mission. The small satellite delivery and orbital debris removal missions were found to closely mimic the heritage RS-34 mission. It is believed that this technology will enable a small, low-cost multiple satellite delivery to multiple orbital locations with a single boost. For both the small satellite delivery and the orbital debris mission candidates, the RS-34 Phoenix requires the least amount of modification to the existing hardware. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed

Esther, Elizabeth A.↗

NASA NTRS2017

[Network Design of the Spaceport Command and Control System]

I helped the Launch Control System (LCS) hardware team sustain the network design of the Spaceport Command and Control System. I wrote the procedure that will be used to satisfy an official hardware test for the hardware carrying data from the Launch Vehicle. I installed hardware and updated design documents in support of the ongoing development of the Spaceport Command and Control System and applied firewall experience I gained during my spring 2017 semester to inspect and create firewall security policies as requested. Finally, I completed several online courses concerning networking fundamentals and Unix operating systems.

Teijeiro, Antonio↗