ELaNa: Educational Launch of NanoSatellite, Developing the Process and Requirements to Launch on NASA ELV's
No abstract available
Skrobot, Garrett↗
SEARCH · Engineering Papers
Results for “NASA Process Requirements”
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.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
NASA-STD-6030 Qualified Material Process Requirements for Joint Non-Metallic SDO Forum
Explore the source record for details and available documents.
Sam Cordner↗
Anthropometric Accommodation in Space Suit Design
Design requirements for next generation hardware are in process at NASA. Anthropometry requirements are given in terms of minimum and maximum sizes for critical dimensions that hardware must accommodate. These dimensions drive vehicle design and suit design, and implicitly have an effect on crew selection and participation. At this stage in the process, stakeholders such as cockpit and suit designers were asked to provide lists of dimensions that will be critical for their design. In addition, they were asked to provide technically feasible minimum and maximum ranges for these dimensions. Using an adjusted 1988 Anthropometric Survey of U.S. Army (ANSUR) database to represent a future astronaut population, the accommodation ranges provided by the suit critical dimensions were calculated. This project involved participation from the Anthropometry and Biomechanics facility (ABF) as well as suit designers, with suit designers providing expertise about feasible hardware dimensions and the ABF providing accommodation analysis. The initial analysis provided the suit design team with the accommodation levels associated with the critical dimensions provided early in the study. Additional outcomes will include a comparison of principal components analysis as an alternate method for anthropometric analysis.
Rajulu, Sudhakar↗
Development of a Human Systems Integration Plan
NASA defines Human Systems Integration (HSI) as part of the overall systems engineering and acquisition strategy for space systems. The HSI Plan defines how HSI activities will be implemented across the lifecycle of the mission, as required by NPR 7123.1C, NASA Systems Engineering Processes and Requirements, and NPR 8705.2C Human-Rating Requirements for Space Systems. The goal of this presentation is to share with government and industry how an HSI Plan can be implemented. The presentation will cover HSI implementation for flight systems, vehicle processing, and interfaces. These are divided into six NASA HSI Domains: human factors engineering, operations resources, safety, training, maintainability and supportability, habitability and environment. HSI activities go across the mission’s lifecycle from pre-formulation and acquisition through design, development, operations, maintenance, and decommissioning. The HSI Plan includes a description of the HSI activities and products that are essential for human rating, operability, maintainability, supportability, and affordability of the mission systems. It also describes the role of the HSI Team required as part of the Human Rating process. The HSI Plan utilizes the operational expertise within NASA to ensure designs and testing are successful, leading to acceptable human spaceflight vehicles.
Jackelynne Silva-Martinez↗
NASA-STD-(I)-6016, Standard Materials and Processes Requirements for Spacecraft
This document is directed toward Materials and Processes (M&P) used in the design, fabrication, and testing of flight components for all NASA manned, unmanned, robotic, launch vehicle, lander, in-space and surface systems, and spacecraft program/project hardware elements. All flight hardware is covered by the M&P requirements of this document, including vendor designed, off-the-shelf, and vendor furnished items. Materials and processes used in interfacing ground support equipment (GSE); test equipment; hardware processing equipment; hardware packaging; and hardware shipment shall be controlled to prevent damage to or contamination of flight hardware.
Pedley, Michael↗
Human Integration Design Processes (HIDP)
The purpose of the Human Integration Design Processes (HIDP) document is to provide human-systems integration design processes, including methodologies and best practices that NASA has used to meet human systems and human rating requirements for developing crewed spacecraft. HIDP content is framed around human-centered design methodologies and processes in support of human-system integration requirements and human rating. NASA-STD-3001, Space Flight Human-System Standard, is a two-volume set of National Aeronautics and Space Administration (NASA) Agency-level standards established by the Office of the Chief Health and Medical Officer, directed at minimizing health and performance risks for flight crews in human space flight programs. Volume 1 of NASA-STD-3001, Crew Health, sets standards for fitness for duty, space flight permissible exposure limits, permissible outcome limits, levels of medical care, medical diagnosis, intervention, treatment and care, and countermeasures. Volume 2 of NASASTD- 3001, Human Factors, Habitability, and Environmental Health, focuses on human physical and cognitive capabilities and limitations and defines standards for spacecraft (including orbiters, habitats, and suits), internal environments, facilities, payloads, and related equipment, hardware, and software with which the crew interfaces during space operations. The NASA Procedural Requirements (NPR) 8705.2B, Human-Rating Requirements for Space Systems, specifies the Agency's human-rating processes, procedures, and requirements. The HIDP was written to share NASA's knowledge of processes directed toward achieving human certification of a spacecraft through implementation of human-systems integration requirements. Although the HIDP speaks directly to implementation of NASA-STD-3001 and NPR 8705.2B requirements, the human-centered design, evaluation, and design processes described in this document can be applied to any set of human-systems requirements and are independent of reference missions. The HIDP is a reference document that is intended to be used during the development of crewed space systems and operations to guide human-systems development process activities.
Boyer, Jennifer↗
Telemetry Systems
Goddard Space Flight Center developed satellite telemetry processing technology to meet NASA's sophisticated processing requirements. The Microelectronic Systems Branch, a 'company' within Goddard, provided NASA with the telemetry data systems from 1985 to 1994. TSI/Telsys, Inc. was then founded to commercialize the systems and began operations on October 1, 1995. The system aids the remote sensing industry by providing affordable and quick access to data collected from space.
Source record↗
Solar System Exploration Technology Requirements and Planning Process
The NASA Office of Space Science, in alliance with the Office of Advanced Concepts and Technology, has developed an Integrated Technology Strategy to guide its investment in technology for space science missions. This strategy establishes goals and strategic objectives that ensure that NASA and the nation derive the greatest possible scientific and economic benefits from investments in space science missions and technologies. Within the Office of Space Science, the Solar System Exploration Division in collaboration with the Office of Space Access and Technology, is developing a Technology Plan to implement these goals and to identify specific goals and to identify specific technology needs for solar system missions. This paper describes the philosophy, processes, and preliminary results of the systematic process being established for the identification and prioritization of solar system exploration technology needs.
space↗
Managing Programs and Projects at NASA
The presentation provides an overview of the NASA organization and several highlights of major NASA Programs and Projects. The presentation then provides additional details regarding project management processes and requirements at NASA. The briefing concludes with insights and information regarding management, communication and collaboration between NASA and international partners on joint projects. All information contained in this briefing is from the public domain.
Smith, Jeffrey D.↗
DIP for Service Providers
The second DIP workshop’s topic is DIP for Service Providers. The workshop presentation covers topics such as DIP onboarding process, service authentication, catalog service capabilities, API requirements, NASA services and their access points, and data requirements for service providers. The Onboarding Process describes the required documentation that enables to collaborate with NASA as well as other industry partners through DIP. Also, step by step approach for the partner to take to register services or consme services through the DIP platform. The Catalog Service describes the different ways for the users to search for services that are of interest as well as registering services to the platform, so other users can search and discover. The API Requirements and Service Specifications describes the benefits of DIP's API management approach via API Gateway where services are managed centrally but ownership is decentralized and partners completely own the administration of their own services. NASA Services and Data Access Points topic describes the services, both data access service and machine learning prediction service, that NASA provides via the DIP platform in near time and post operations via REST API endpoints defined on the API Gateway. Also, NASA's approach for data storage process is explained. The Data Requirements for service providers describes the requirements for storing and exposing to support the performance of services that are provided by the service providers. Lastly, NASA's technology development plan with preliminary scheduler will be presented. There will be a Q&A session at the end of each segment of the presentation to solicit feedback from the participants.
ATM-X↗
Technology utilization office data base analysis and design
NASA Headquarters is placing a high priority on the transfer of NASA and NASA contractor developed technologies and expertise to the private sector and to other federal, state and local government organizations. The ultimate objective of these efforts is positive economic impact, an improved quality of life, and a more competitive U.S. posture in international markets. The Technology Utilization Office (TUO) currently serves seven states with its technology transfer efforts. Since 1989, the TUO has handled over one-thousand formal requests for NASA related technologies assistance. The technology transfer process requires promoting public awareness of NASA related soliciting requests for assistance, matching technologies to specific needs, assuring appropriate technology transfer, and monitoring and evaluating the process. Each of these activities have one very important aspect in common: the success of each is dissemination of appropriate high quality information. The purpose of the research was to establish the requirements and develop a preliminary design for a database system to increase the effectiveness and efficiency of the TUO's technology transfer function. The research was conducted following the traditional systems development life cycle methodology and was supported through the use of modern structured analysis techniques. The next section will describe the research and findings as conducted under the life cycle approach.
Floyd, Stephen A.↗
Replacement/Refurbishment of JSC/NASA POD Specimens
The NASA Special NDE certification process requires demonstration of NDE capability by test per NASA-STD-5009. This test is performed with fatigue cracked specimens containing very small cracks. The certification test results are usually based on binomial statistics and must meet a 90/95 Probability of Detection (POD). The assumption is that fatigue cracks are tightly closed, difficult to detect, and inspectors and processes passing such a test are well qualified for inspecting NASA fracture critical hardware. The JSC NDE laboratory has what may be the largest inventory that exists of such fatigue cracked NDE demonstration specimens. These specimens were produced by the hundreds in the late 1980s and early 1990s. None have been produced since that time and the condition and usability of the specimens are questionable.
Castner, Willard L.↗
EMASS (trademark): An expandable solution for NASA space data storage needs
The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2 x 10(exp 12) Bytes). As the scientific community makes use of this data, their work will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. The expendable architecture of the E-Systems Modular Automated Storage System (EMASS(TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century is described.
Peterson, Anthony L.↗
EMASS (tm): An expandable solution for NASA space data storage needs
The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2(10)(exp 12) Bytes). As the scientific community makes use of this data their work product will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. This paper describes the expandable architecture of the E-Systems Modular Automated Storage System (EMASS (TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century.
Peterson, Anthony L.↗
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.
Dezfuli, Homayoon↗
Defining a Space Mission Architectural Framework: Guiding Robotic Space Mission Design and Development at NASA Goddard Spaceflight Center
Modern Systems Engineering activities for robotic science missions face increased complexity due to evolving measurement requirements, increased collaboration amongst stakeholders and increased collaboration between human and robotic systems. While NASA has employed standard process frameworks for project management and systems engineering for years, it has not yet established an architecture framework (AF) by which its mission systems are described. While an architecture framework is not a necessary component of an organization's operations, the value of a specified AF greatly enhances an organization's ability to define systems consistently and aid in communication across project and organizational boundaries. The current effort identifies an approach to establishing a Space Mission Architecture Framework (SMAF), an AF with roots in ISO 42010 (Systems and Software Engineering-Architecture Description), NASA Procedural Requirements (NPR) 7120.5 (NASA Space Flight Program and Project Management Requirements) and 7123.1B (NASA Systems Engineering Processes and Requirements). The heart of the AF lies in its viewpoints and work products, artifacts that represent a set of information from the viewpoint of a particular stakeholder. This effort articulates the needs, goals and objectives that the SMAF addresses, as well as the approach to creating the framework and establishing the various work products. A full set of work products, sufficient to satisfy the Mission System reporting requirements of NPR 7120/7123 at Key Decision Point (KDP) A is identified in this paper.
Architecture↗
The NASA Commercial Crew Program (CCP) Mission Assurance Process
In 2010, NASA established the Commercial Crew Program in order to provide human access to the International Space Station and low earth orbit via the commercial (non-governmental) sector. A particular challenge to NASA has been how to determine the commercial providers transportation system complies with Programmatic safety requirements. The process used in this determination is the Safety Technical Review Board which reviews and approves provider submitted Hazard Reports. One significant product of the review is a set of hazard control verifications. In past NASA programs, 100 percent of these safety critical verifications were typically confirmed by NASA. The traditional Safety and Mission Assurance (SMA) model does not support the nature of the Commercial Crew Program. To that end, NASA SMA is implementing a Risk Based Assurance (RBA) process to determine which hazard control verifications require NASA authentication. Additionally, a Shared Assurance Model is also being developed to efficiently use the available resources to execute the verifications. This paper will describe the evolution of the CCP Mission Assurance process from the beginning of the Program to its current incarnation. Topics to be covered include a short history of the CCP; the development of the Programmatic mission assurance requirements; the current safety review process; a description of the RBA process and its products and ending with a description of the Shared Assurance Model.
Commercial Crew Program↗
Implementation of Human Systems Integration Technical and Management Process for the Lunar Gateway Program
NASA recognizes Human Systems Integration (HSI) as part of the overall systems engineering and acquisition strategy for space systems. The Lunar Gateway Program is implementing HSI technical and management process across the lifecycle of the mission, as required by NPR 7123.1C NASA Systems Engineering Processes and Requirements, and led by the Gateway HSI team as required by NPR 8705.2C Human-Rating Requirements for Space Systems, now HEOMD-003 Crewed Deep Space Systems Human Rating Certification Requirements and Standards for NASA Missions. NASA has been using HSI principles for many years and has applied them to many of its previous human spaceflight Programs. As NASA returns to the Moon in a more sustainable manner, the Gateway Program is maturing the application of HSI by implementing it more visibly as part of Artemis, with guidance from the NASA/SP-20210010952 NASA HSI Handbook. This paper discusses how HSI is being implemented in the Gateway Program, challenges faced with its implementation during the development phase, and strategies/approaches used to overcome those. The paper also covers HSI implementation for flight systems, vehicle processing, and interfaces across the six identified NASA HSI Domains: human factors engineering, operations, safety, training, maintainability and supportability, habitability and environment. The goal is to provide an overview of the implementation process of HSI in the Gateway Program as an example for other Programs/Projects/Missionsthat are looking to implement HSI.
Jackelynne Silva-Martinez↗