Search NASA⌕ Search

SEARCH · Search NASA

Results for “Payload developer”

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.

At least 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

Semi-automatic development of Payload Operations Control Center software

This report summarizes the current status of CTA's investigation of methods and tools for automating the software development process in NASA Goddard Space Flight Center, Code 500. The emphasis in this effort has been on methods and tools in support of software reuse. The most recent phase of the effort has been a domain analysis of Payload Operations Control Center (POCC) software. This report summarizes the results of the domain analysis, and proposes an approach to semi-automatic development of POCC Application Processor (AP) software based on these results. The domain analysis enabled us to abstract, from specific systems, the typical components of a POCC AP. We were also able to identify patterns in the way one AP might be different from another. These two perspectives--aspects that tend to change from AP to AP, and aspects that tend to remain the same--suggest an overall approach to the reuse of POCC AP software. We found that different parts of an AP require different development technologies. We propose a hybrid approach that combines constructive and generative technologies. Constructive methods emphasize the assembly of pre-defined reusable components. Generative methods provide for automated generation of software from specifications in a very-high-level language (VHLL).

Ballin, Sidney↗
NASA NTRSDate not supplied

Advanced Manufacturing of the SLS Block 1B Payload Adapter: Engineering Development Unit

The Payload Adapter (PLA) for the Space Launch System Block 1B configuration (SLS B1B) is a structural frustum that interfaces with the Exploration Upper Stage (EUS) and the Universal Stage Adapter (USA) or the cargo fairing at the aft end and interfaces with the primary or co-manifested payload at the forward end. The primary structure is composed of a single piece aluminum forward ring, a segmented aluminum aft ring, eight carbon composite sandwich panels, and composite bonded longitudinal joints. The PLA is designed and fabricated in-house at MSFC. Development and flight article builds are joint efforts between the Materials & Processes Laboratory (EM), the Spacecraft & Vehicle Systems Department (EV), the Space Systems Department (ES), and the Test Laboratory (ET). The large-scale manufacturing efforts associated with this task include the fabrication of pathfinder panels; the fabrication and assembly of a full-scale Manufacturing Demonstration Article (MDA); the fabrication, assembly, and test of an Engineering Demonstration Unit (EDU); the fabrication, assembly, and test of a qualification Article; and the fabrication, assembly, and proof test of subsequent flight articles. The PLA team recently completed assembly of the EDU. The final assembly included the instillation of the co-manifested secondary payload, NEST, and the instillation and tensioning of the Payload Separation System (PSS). This poster will detail the assembly process which includes: (1) composite panel to ring assembly, (2) adhesive bonding for the longitudinal joints, and (3) instillation of the NEST and PSS. The PLA EDU is prepared to undergo modal and static load testing.

Monique Wallace↗
NASA NTRS2018

Advanced Utilization of the Payload Executive Processor (PEP) Ethernet Port to Support JSL Based Payloads

Increased interest by Payload Developers in utilization of the Joint Station LAN (Local Area Network) (JSL) for command and data transactions has driven the investigation of providing bi-directional Ethernet communication with PEP (Payload Executive Processor). Ethernet-only payload developers are interested in taking advantage of the services provided by PEP. Enabling Ethernet communications within PEP requires more than just turning on the hardware. PEP contains no Operating System (OS) or Ethernet stack so it does not inherit any built in functionality for Ethernet support. Both hardware drivers and application software must be developed from scratch. In the absence of an OS (Operating System) the design must address security issues in terms of access and data transferred, i.e. blocking unauthorized users and preventing denial of service. Developing a design to process Ethernet data within the existing real-time constraints of PEP requires a few compromises: data rates, supported protocols, custom packet format and limited client connections to name a few. Integration of the light weight internet protocol (LwIP). Ethernet stack provides a customizable solution for the embedded real-time environment. As utilization of the JSL increases, the successful implementation of an Ethernet interface enhances the utilization of PEP, and provides a new path for future Ethernet-only payloads to gain access to around the clock command and data services.

Guyette, Greg↗
NASA NTRS2018

Overview of the Life Sciences Glovebox (LSG) Facility

The Life Sciences Glovebox (LSG) is a rack-level payload facility designed to house biological investigations in a "workbench" type environment aboard the International Space Station (ISS). The facility is scheduled to be launched in September 2018 and will be installed in the Japanese Experiment Module (JEM) of the ISS. LSG is comprised of an extendable work volume, an airlock, an avionics package, a laptop, and supporting structure. The 450L work volume provides two levels of containment for investigations via the physical barrier of its structure and an internal, filtered airflow that results in a negative pressure relative to ISS cabin pressure. The facility provides many other resources for investigation use including 28 VDC power, 120 VAC power, heat rejection, data connections, and video. Portions of the interior surfaces of the work volume are ferrous, allowing investigations and supporting hardware to be magnetically affixed to these surfaces. A UV decontamination system and a variety of ancillary hardware are available for investigations to use while occupying LSG. An engineering unit on the ground is used for payload development and integrated verification testing. Once the facility is installed and commissioned, it will be managed by the same team that manages the Microgravity Science Glovebox (MSG), another rack-level payload facility that has been operating aboard the ISS since 2002. Experienced Investigation Payload Integration Managers (IPIMs), who also support MSG payloads, will be available to assist payload developers through the integration process. This presentation will provide an overview of the LSG facility and the planned investigation flow for the near future.

Jordan, Lee↗
NASA NTRS2001

A Stream lined Approach for the Payload Customer in Identifying Payload Design Requirements

NASA payload developers from across various disciplines were asked to identify areas where process changes would simplify their task of developing and flying flight hardware. Responses to this query included a central location for consistent hardware design requirements for middeck payloads. The multidisciplinary team assigned to review the numerous payload interface design documents is assessing the Space Shuttle middeck, the SPACEHAB Inc. locker, as well as the MultiPurpose Logistics Module (MPLM) and EXpedite the PRocessing of Experiments to Space Station (EXPRESS) rack design requirements for the payloads. They are comparing the multiple carriers and platform requirements and developing a matrix which illustrates the individual requirements, and where possible, the envelope that encompasses all of the possibilities. The matrix will be expanded to form an overall envelope that the payload developers will have the option to utilize when designing their payload's hardware. This will optimize the flexibility for payload hardware and ancillary items to be manifested on multiple carriers and platforms with minimal impact to the payload developer.

Miller, Ladonna J.↗
NASA NTRS2019

NASA's Space Launch System: Deep Space Access for CubeSats

NASA is embarking on a new generation of missions to the Moon, known as the Artemis program. The Agency’s new super heavy-lift launch vehicle, the Space Launch System (SLS), is a critical enabling capability for these efforts, which will serve as a proving ground for future crewed expeditions to Mars. SLS is designed to return astronauts to the Moon in the Orion spacecraft and to launch more mass and provide more volume for critical payloads than commercially available vehicles, giving NASA a unique asset for deep space exploration. When performance margin and volume is available, as it is on the first flight, Artemis I (previously Exploration Mission-1), SLS can offer CubeSats access to deep space, beyond Earth’s orbit. The Artemis I flight has 13 6U (14 kg) CubeSats manifested, and the Program is currently accepting proposals for 6U and 12U payloads for the Artemis II flight through the agency’s CubeSat Launch Initiative (CSLI) program. Proposals from U.S.-based payload developers to fly on Artemis II will be accepted through CSLI until November 4, 2019. When ridesharing on SLS deep space missions, CubeSats must demonstrate they will not interfere with primary mission objectives. The 13 Artemis I CubeSats that hail from industry, academia, NASA and its international partners represent an array of exciting deep space science investigations and technology demonstrations that may help inform future Artemis missions. The initial SLS Block 1 vehicle for the Artemis I flight is fully manufactured; several elements are complete and have been delivered to the Exploration Ground Systems (EGS) Program at Kennedy Space Center (KSC), which has responsibility for integrating and launching the SLS and Orion stack. Completed elements of the Artemis I vehicle include the Orion Stage Adapter (OSA), which houses the 13 Artemis I CubeSats. With the Artemis I flight hardware and software nearing completion, work is in progress for the second Block 1 launcher, designated for the crewed Artemis II flight. Hardware is being manufactured for every element of the Artemis II vehicle. In this paper, the author will review the status of the Artemis I vehicle and the payloads manifested for the initial flight. Information on the Secondary Payload Deployment System (SPDS) that the SLS Program provides to payload developers will also be included.

Creech, Stephen D.↗
NASA NTRS1971

Development of payload subsystem-primate mission-Biosatellite program

Design and operation of the primate life support subsystem for the Biosatellite Program as used during the flight of Biosatellite 3 are discussed. Included are preflight changes necessitated by the primate's (a Macaca nemistrina monkey) influence on the initial equipment design.

Hall, J. F., Jr.↗
NASA NTRS2000

Computer accelerated conceptual design and development of spacecraft

The Next Generation Payload Development Team (NPDT), also called Team I, at the Jet Propulsion Laboratory provides a customer with a state-of-the-art Concurrent Design and Analysis environment for the early Design stages and emphasizes a total Systems approach, and features Multi-Disciplinary design teams, and interconnected high-end Analysis and Design tools.

NPDT design payload spacecraft↗
NASA NTRSDate not supplied

Space Shuttle Cargo Integration Coupled Loads Analysis Lessons Learned

When a system experiences a loading environment characterized by rapidly varying forces, such as a rocket launch, a transient analysis is used to analyze the response of the system. The most common transient analysis methodology is the Coupled Loads Analysis (CLA). CLAs are used by the automotive and aerospace industry to analyze cars, trucks, planes, helicopters, spacecraft, etc. The Space Shuttle program used the CLA methodology to assess the compatibility of the payload with the Orbiter and the flight environment. The Space Shuttle Verification Loads Analysis (VLA) was a standardized CLA process that started between ten and thirteen months prior to launch, and included several meetings as well as analysis by both the Space Shuttle Program and the payload developers to verify that the payloads were compatible with the flight loads environment and would not interact negatively with the vehicle. Over the course of the Space Shuttle Program, many improvements were made to the process, which reduced cycle time and improved manifest flexibility. There were several issues which were never fully addressed, but workarounds were developed to keep the process flowing. The lessons learned included automation of some processes and standardization of others, early assessments, improved documentation and better coordination with all stakeholders in the process. Lessons learned also included the limitations in the current process, and what to do to avoid the same issues in the future.

Erica E. Bruno↗
NASA NTRSDate not supplied

Space Shuttle Cargo Integration Coupled Loads Analysis Lessons Learned

When a system experiences a loading environment characterized by rapidly varying forces, such as a rocket launch, a transient analysis is used to analyze the response of the system. The most common transient analysis methodology is the Coupled Loads Analysis(CLA). CLAs are used by the automotive and aerospace industry to analyze cars, trucks,planes, helicopters, spacecraft, etc. The Space Shuttle program used the CLA methodology to assess the compatibility of the payload with the Orbiter and the flight environment. The Space Shuttle Verification Loads Analysis (VLA) was a standardized CLA process that started between ten and thirteen months prior to launch, and included several meetings as well as analysis by both the Space Shuttle Program and the payload developers to verify that the payloads were compatible with the flight loads environment and would not interact negatively with the vehicle. Over the course of the Space Shuttle Program, many improvements were made to the process, which reduced cycle time and improved manifest flexibility. There were several issues which were never fully addressed, but work-arounds were developed to keep the process flowing. The lessons learned included automation of some processes and standardization of others, early assessments, improved documentation and better coordination with all stakeholders in the process. Lessons learned also included the limitations in the current process, and what to do to avoid the same issues.

ERICA E. BRUNO↗
NASA NTRS1978

Payload planning information development study

The results of the Payload Planning Information Sheets Development Study were summarized. The two payload planning questionnaires that were developed in this study are included.

Source record↗
NASA NTRS2017

Case Studies in Crewed Spacecraft Environmental Control and Life Support System Process Compatibility and Cabin Environmental Impact

Contamination of a crewed spacecraft's cabin environment leading to environmental control and life support system (ECLSS) functional capability and operational margin degradation or loss can have an adverse effect on NASA's space exploration mission figures of merit-safety, mission success, effectiveness, and affordability. The role of evaluating the ECLSS's compatibility and cabin environmental impact as a key component of pass trace contaminant control is presented and the technical approach is described in the context of implementing NASA's safety and mission success objectives. Assessment examples are presented for a variety of chemicals used in vehicle systems and experiment hardware for the International Space Station program. The ECLSS compatibility and cabin environmental impact assessment approach, which can be applied to any crewed spacecraft development and operational effort, can provide guidance to crewed spacecraft system and payload developers relative to design criteria assigned ECLSS compatibility and cabin environmental impact ratings can be used by payload and system developers as criteria for ensuring adequate physical and operational containment. In additional to serving as an aid for guiding containment design, the assessments can guide flight rule and procedure development toward protecting the ECLSS as well as approaches for contamination event remediation.

Perry, J. L.↗
NASA NTRS2020

Introduction to ISS Crew Displays

The International Space Station (ISS) began payload operations in earnest in 2000 with the arrival of the Expedition 1. To date, ISS has offered Principal Investigators (PIs) a reliable platform for microgravity research, having hosted thousands of onboard science experiments. Most of this research is supported by experiment hardware and software and many include a crew‐operated Graphical User Interface (GUI). The purpose of this article is to share information with PIs and Payload Developer (PD) teams about the processes, standards, and guidelines applicable to crew GUI design that must be complied with when planning payload software. The goal is not to enumerate all of the ISS display standards, but rather to highlight design guidelines and the ISS Program milestones for verification and approval of onboard crew displays.

Graphical User Interface↗
NASA NTRS2018

Innovative Development of a Cross-Center Timeline Planning Tool

The Payload Operations Integration Center (POIC) at Marshall Space Flight Center (MSFC) supports planning, coordination and scheduling of science activities for the International Space Station (ISS) in coordination with other NASA centers, international partners, and payload developers. The ability to efficiently plan and re-plan in response to change is critical to the flight planning teams. With the achievement of supporting a fourth crew member aboard the ISS and an increasing amount of payload science activities, came the need for a dynamic, more efficient way of building timeline planning reports that could be readily updated as fast as payload science plans could change. This paper addresses software architecture considerations in the successful cross-center development of an automated planning tool with multiple data sources. It also discusses the practical implementation of a time-boxed, hybrid Agile Software Development (ASD) approach to deliver customer-driven value despite changing requirements with respect to low-Earth orbit operational planning activities. The goal of this paper is to open discussion with members of the international community and trade effective strategies for cross-center architectural and customer-developer driven collaborations, to support increasing utilization of planning and conducting science activities in space.

Pedoto, Ramon W.↗
NASA NTRS2001

International Space Station Payload Training Overview

This paper describes payload crew training-related activities performed by NASA and the U.S. Payload Developer (PD) community for the International Space Station (ISS) Program. It describes how payloads will be trained and the overall training planning and integration process. The overall concept, definition, and template for payload training are described. The roles and responsibilities of individuals, organizations, and groups involved are discussed. The facilities utilized during payload training and the primary processes and activities performed to plan, develop, implement, and administer payload training for ISS crews are briefly described. Areas of improvement to crew training processes that have been achieved or are currently being worked are identified.

Underwood, Deborah B.↗
NASA NTRS2012

External Contamination Control of Attached Payloads on the International Space Station

The International Space Station (ISS) is an on-orbit platform for science utilization in low Earth orbit with multiple sites for external payloads with exposure to the natural and induced environments. Contamination is one of the induced environments that can impact performance, mission success and science utilization on the vehicle. This paper describes the external contamination control requirements and integration process for externally mounted payloads on the ISS. The external contamination control requirements are summarized and a description of the integration and verification process is detailed to guide payload developers in the certification process of attached payloads on the vehicle. A description of the required data certification deliverables covers the characterization of contamination sources. Such characterization includes identification, usage and operational data for each class of contamination source. Classes of external contamination sources covered are vacuum exposed materials, sources of leakage, vacuum venting and thrusters. ISS system level analyses are conducted by the ISS Space Environments Team to certify compliance with external contamination control requirements. This paper also addresses the ISS induced contamination environment at attached payload sites, both at the requirements level as well as measurements made on ISS.

Soares, Carlos E.↗
NASA NTRSDate not supplied

AstroDOME: Standardized, Mass-Produceable, Small NASA Astrophysics Observatories for Big Missions

NASA’s Goddard Space Flight Center is investigating the use of small, commercial off the shelf (COTS) spacecraft to enable breakthrough astrophysics research at radically reduced cost over previous generations of missions. This paper will focus on the Mission Systems perspective of this investigation. It will cover the spacecraft to instrument interface, and lessons learned in early concept payload development. Low-cost COTS spacecraft have proliferated in the last ~5 years. They represent an order of magnitude reduction in the cost of spacecraft bus development and acquisition. They are enabled by the advent of low-cost smallsat launch options in the immediately preceding years, and are seeded by recent distributed and disaggregated missions in other sectors such as telecommunications megaconstellations (e.g. Starlink, OneWeb, Project Kuiper) and ongoing Space Development Agency (SDA) developments. Our study was tasked with developing a standardized, mass-produceable, astrophysics payload which is reconfigurable to different wavelength bands while maintaining a single optics bench design, and a standardized mechanical, electrical, data, and thermal interface to the spacecraft bus, and which may be reconfigured to multiple COTS spacecraft offerings. In this paper we will discuss lessons learned from our case study. We will also present identified keys to mission success for performing cutting edge astrophysics observations while taking advantage of economies of scale with a disaggregated, standardized architecture.

Matthew Marcus↗