Search NASA⌕ Search

SEARCH · Search NASA

Results for “COTS actives”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

A Space Based Internet Protocol System for Sub-Orbital Tracking and Control

Personnel from the Goddard Space Flight Center Wallops Flight Facility (GSFC/WFF) in Virginia are responsible for the overall management of the NASA Sounding Rocket Program. Payloads are generally in support of NASA's Space Science Enterprise's missions and return a variety of scientific data as well as providing a reasonably economical means of conducting engineering tests for instruments and devices used on satellites and other spacecraft. The fifteen types of sounding rockets used by NASA can carry payloads of various weights to altitudes from 50 km to more than 1,300 km. Launch activities are conducted not only from established missile ranges, but also from remote locations worldwide requiring mobile tracking and command equipment to be transported and set up at considerable expense. The advent of low earth orbit (LEO) commercial communications satellites provides an opportunity to dramatically reduce tracking and control costs of launch vehicles and Unpiloted Aerial Vehicles (UAVs) by reducing or eliminating this ground infrastructure. Additionally, since data transmission is by packetized Internet Protocol (IP), data can be received and commands initiated from practically any location. A low cost Commercial Off The Shelf (COTS) system is currently under development for sounding rockets which also has application to UAVs and scientific balloons. Due to relatively low data rate (9600 baud) currently available, the system will first be used to provide GPS data for tracking and vehicle recovery. Range safety requirements for launch vehicles usually stipulate at least two independent tracking sources. Most sounding rockets flown by NASA now carry GPS receivers that output position data via the payload telemetry system to the ground station. The Flight Modem can be configured as a completely separate link thereby eliminating requirement for tracking radar. The system architecture which integrates antennas, GPS receiver, commercial satellite packet data modem, and a single board computer with custom software is described along with the technical challenges and the plan for their resolution. These include antenna development, high Doppler rates, reliability, environmental ruggedness, hand over between satellites and data security. An aggressive test plan is included which in addition to environmental testing measures bit error rate, latency and antenna patterns. Actual flight tests are planned for the near future on aircraft, long duration balloons and sounding rockets and these results as well as the current status of the project are reported.

Bull, Barton↗
NASA NTRS2014

Flight Avionics Hardware Roadmap

The Avionics Technology Roadmap takes an 80% approach to technology investment in spacecraft avionics. It delineates a suite of technologies covering foundational, component, and subsystem-levels, which directly support 80% of future NASA space mission needs. The roadmap eschews high cost, limited utility technologies in favor of lower cost, and broadly applicable technologies with high return on investment. The roadmap is also phased to support future NASA mission needs and desires, with a view towards creating an optimized investment portfolio that matures specific, high impact technologies on a schedule that matches optimum insertion points of these technologies into NASA missions. The roadmap looks out over 15+ years and covers some 114 technologies, 58 of which are targeted for TRL6 within 5 years, with 23 additional technologies to be at TRL6 by 2020. Of that number, only a few are recommended for near term investment: 1. Rad Hard High Performance Computing 2. Extreme temperature capable electronics and packaging 3. RFID/SAW-based spacecraft sensors and instruments 4. Lightweight, low power 2D displays suitable for crewed missions 5. Radiation tolerant Graphics Processing Unit to drive crew displays 6. Distributed/reconfigurable, extreme temperature and radiation tolerant, spacecraft sensor controller and sensor modules 7. Spacecraft to spacecraft, long link data communication protocols 8. High performance and extreme temperature capable C&DH subsystem In addition, the roadmap team recommends several other activities that it believes are necessary to advance avionics technology across NASA: center dot Engage the OCT roadmap teams to coordinate avionics technology advances and infusion into these roadmaps and their mission set center dot Charter a team to develop a set of use cases for future avionics capabilities in order to decouple this roadmap from specific missions center dot Partner with the Software Steering Committee to coordinate computing hardware and software technology roadmaps and investment recommendations center dot Continue monitoring foundational technologies upon which future avionics technologies will be dependent, e.g., RHBD and COTS semiconductor technologies

Some, Raphael↗
NASA NTRS2001

A Space Based Internet Protocol System for Launch Vehicle Tracking and Control

Personnel from the Goddard Space Flight Center Wallops Flight Facility (GSFC/WFF) in Virginia are responsible for the overall management of the NASA Sounding Rocket and Scientific Balloon Programs. Payloads are generally in support of NASA's Space Science Enterprise's missions and return a variety of scientific data as well as providing a reasonably economical means of conducting engineering tests for instruments and devices used on satellites and other spacecraft. Sounding rockets used by NASA can carry payloads of various weights to altitudes from 50 km to more than 1,300 km. Scientific balloons can carry a payload weighing as much as 3,630 Kg to an altitude of 42 km. Launch activities for both are conducted not only from established ranges, but also from remote locations worldwide requiring mobile tracking and command equipment to be transported and set up at considerable expense. The advent of low earth orbit (LEO) commercial communications satellites provides an opportunity to dramatically reduce tracking and control costs of these launch vehicles and Unpiloted Aerial Vehicles (UAVs) by reducing or eliminating this ground infrastructure. Additionally, since data transmission is by packetized Internet Protocol (IP), data can be received and commands initiated from practically any location. A low cost Commercial Off The Shelf (COTS) system is currently under development for sounding rockets that also has application to UAVs and scientific balloons. Due to relatively low data rate (9600 baud) currently available, the system will first be used to provide GPS data for tracking and vehicle recovery. Range safety requirements for launch vehicles usually stipulate at least two independent tracking sources. Most sounding rockets flown by NASA now carry GP~ receivers that output position data via the payload telemetry system to the ground station. The Flight Modem can be configured as a completely separate link thereby eliminating the requirement for tracking radar. The system architecture that integrates antennas, GPS receiver, commercial satellite packet data modem, and a single board computer with custom software is described along with the technical challenges and the plan for their resolution. These include antenna development, high Doppler rates, reliability, environmental ruggedness, hand over between satellites, and data security. An aggressive test plan is included which, in addition to environmental testing, measures bit error rate, latency and antenna patterns. Actual launches on a sounding rocket and various aircraft flights have taken place. Flight tests are planned for the near future on aircraft, long duration balloons and sounding rockets. These results, as well as the current status of the project, are reported.

Bull, Barton↗
NASA NTRS2010

Launch Pad Coatings for Smart Corrosion Control

Corrosion is the degradation of a material as a result of its interaction with the environment. The environment at the KSC launch pads has been documented by ASM International (formerly American Society for Metals) as the most corrosive in the US. The 70 tons of highly corrosive hydrochloric acid that are generated by the solid rocket boosters during a launch exacerbate the corrosiveness of the environment at the pads. Numerous failures at the pads are caused by the pitting of stainless steels, rebar corrosion, and the degradation of concrete. Corrosion control of launch pad structures relies on the use of coatings selected from the qualified products list (QPL) of the NASA Standard 5008A for Protective Coating of Carbon Steel, Stainless Steel, and Aluminum on Launch Structures, Facilities, and Ground Support Equipment. This standard was developed to establish uniform engineering practices and methods and to ensure the inclusion of essential criteria in the coating of ground support equipment (GSE) and facilities used by or for NASA. This standard is applicable to GSE and facilities that support space vehicle or payload programs or projects and to critical facilities at all NASA locations worldwide. Environmental regulation changes have dramatically reduced the production, handling, use, and availability of conventional protective coatings for application to KSC launch structures and ground support equipment. Current attrition rate of qualified KSC coatings will drastically limit the number of commercial off the shelf (COTS) products available for the Constellation Program (CxP) ground operations (GO). CxP GO identified corrosion detection and control technologies as a critical, initial capability technology need for ground processing of Ares I and Ares V to meet Constellation Architecture Requirements Document (CARD) CxP 70000 operability requirements for reduced ground processing complexity, streamlined integrated testing, and operations phase affordability. Researchers at NASA's Corrosion Technology Laboratory at KSC are developing a smart, environmentally friendly coating system for early corrosion detection, inhibition, and self healing of mechanical damage without external intervention. This smart coating will detect and respond actively to corrosion and mechanical damage such as abrasion and scratches, in a functional and predictable manner, and will be capable of adapting its properties dynamically. This coating is being developed using corrosion sensitive microcapsules that deliver the contents of their core (corrosion inhibiting compounds, corrosion indicators, and self healing agents) on demand when corrosion or mechanical damage to the coating occurs.

Calle, Luz M.↗
NASA NTRS2001

A Simplified Model of ARIS for Optimal Controller Design

Many space-science experiments require active vibration isolation. Boeing's Active Rack Isolation System (ARIS) isolates experiments at the rack (vs. experiment or sub-experiment) level, with multi e experiments per rack. An ARIS-isolated rack typically employs eight actuators and thirteen umbilicals; the umbilicals provide services such as power, data transmission, and cooling. Hampton, et al., used "Kane's method" to develop an analytical, nonlinear, rigid-body model of ARIS that includes full actuator dynamics (inertias). This model, less the umbilicals, was first implemented for simulation by Beech and Hampton; they developed and tested their model using two commercial-off-the-shelf (COTS) software packages. Rupert, et al., added umbilical-transmitted disturbances to this nonlinear model. Because the nonlinear model, even for the untethered system, is both exceedingly complex and "encapsulated" inside these COTS tools, it is largely inaccessible to ARIS controller designers. This paper shows that ISPR rattle-space constraints and small ARIS actuator masses permit considerable model simplification, without significant loss of fidelity. First, for various loading conditions, comparisons are made between the dynamic responses of the nonlinear model (untethered) and a truth model. Then comparisons are made among nonlinear, linearized, and linearized reduced-mass models. It is concluded that these three models all capture the significant system rigid-body dynamics, with the third being preferred due to its relative simplicity.

Beech, Geoffrey S.↗
NASA NTRS2004

An Introduction to Flight Software Development: FSW Today, FSW 2010

Experience and knowledge gained from ongoing maintenance of Space Shuttle Flight Software and new development projects including Cockpit Avionics Upgrade are applied to projected needs of the National Space Exploration Vision through Spiral 2. Lessons learned from these current activities are applied to create a sustainable, reliable model for development of critical software to support Project Constellation. This presentation introduces the technologies, methodologies, and infrastructure needed to produce and sustain high quality software. It will propose what is needed to support a Vision for Space Exploration that places demands on the innovation and productivity needed to support future space exploration. The technologies in use today within FSW development include tools that provide requirements tracking, integrated change management, modeling and simulation software. Specific challenges that have been met include the introduction and integration of Commercial Off the Shelf (COTS) Real Time Operating System for critical functions. Though technology prediction has proved to be imprecise, Project Constellation requirements will need continued integration of new technology with evolving methodologies and changing project infrastructure. Targets for continued technology investment are integrated health monitoring and management, self healing software, standard payload interfaces, autonomous operation, and improvements in training. Emulation of the target hardware will also allow significant streamlining of development and testing. The methodologies in use today for FSW development are object oriented UML design, iterative development using independent components, as well as rapid prototyping . In addition, Lean Six Sigma and CMMI play a critical role in the quality and efficiency of the workforce processes. Over the next six years, we expect these methodologies to merge with other improvements into a consolidated office culture with all processes being guided by automated office assistants. The infrastructure in use today includes strict software development and configuration management procedures, including strong control of resource management and critical skills coverage. This will evolve to a fully integrated staff organization with efficient and effective communication throughout all levels guided by a Mission-Systems Architecture framework with focus on risk management and attention toward inevitable product obsolescence. This infrastructure of computing equipment, software and processes will itself be subject to technological change and need for management of change and improvement,

Gouvela, John↗
NASA NTRS2019

Seeker Free-Flying Inspector GNC System Overview

Seeker is an ultra-low cost approach to highly automated extravehicular inspection of crewed or uncrewed spacecraft that has been designed and built in-house at the NASA Johnson Space Center (JSC). The first version of Seeker is intended to be an incremental development towards an advanced inspection capability. This effort builds on past free-flying inspector development efforts such as the Autonomous Extravehicular Activity Robotic Camera Sprint (AERCam Sprint) and Mini AERCam. Seeker was funded as an International Space Station (ISS) "X-by" Project, which required delivery of the vehicle approximately one year after authority to proceed and within the budget of $1.8 million. Seeker will fly onboard the NG-11 Cygnus mission in 2019 and will deploy after Cygnus' primary mission is completed. Seeker will perform inspection-like maneuvers within 50 meters of the target vehicle (Cygnus) and then dispose itself. The Seeker Guidance, Navigation, and Control (GNC) system is composed entirely of commercial off-the-shelf (COTS) and space-rated COTS items, an inertial-relative Multiplicative Extended Kalman Filter (MEKF), point-to-point guidance (with various additional modes such as stationkeeping), proportional-integral translational control, phase plane rotational control, and a state machine for automated mission moding with minimal ground input.

Navigation↗
NASA NTRS2012

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

Mangieri, Mark L.↗
NASA NTRS2022

Electrical Ground Support Equipment for the Sampling Caching System of the Mars 2020 Rover

In this work we describe in detail the architecture, design, testing and operation of the Electrical Ground Support Equipment (EGSE) “Blue Box” used to test and validate the Sampling Caching System (SCS) of the Mars 2020 Perseverance rover. The Blue Box architecture is centered around COTS motor controllers and COTS input-output modules communicating over an EtherCAT bus. A custom, low-level safety subsystem ensures no harm can be done to the flight articles. The modular architecture of the EGSE reduces cost and complexity while expediting assembly time. The Blue Box drives the 19 actuators of the SCS which span the main robotic arm, the corer system, the internal sample handling arm, the sample tube sealing system and the gas dust removal tool; mimicking the Rover Motor Control Assembly (RMCA). Due to the limited availability of RMCA’s, the EGSE enabled and performed the bulk of testing activities for SCS. The majority of the SCS actuators are composed of a 3-phase DC brushless motors, hall sensors for commutation, dual resolvers for output angular measurement, brakes, heaters and platinum thermistors. Additionally, the EGSE read 12 strain gauges forming part of a force torque sensor, and switches used for external positioning references. Over the 3-year span of the V&V campaign for the SCS, over 32 EGSE systems were built, tested and deployed to test venues at JPL and externally. The EGSE tested several families of the SCS subsystem, ranging from engineering units, life test units and two flight units. Test venues that this EGSE supported included lab benches, ultra-clean cleanrooms, ATLO facilities, and thermal vacuum chambers. Together with the test software systems, SSDEV and SSDEV-ECAT, the Blue Box EGSE enabled the team to efficiently test flight hardware and flight software together. We go over the safety features and fault management techniques employed to protect flight hardware. The effects of the long, 50-feet, EGSE harnesses on motor performance, EMI, electrical noise, and motor control performance are explained. Mitigations to these unwanted effects, including shielding strategy and inductance compensation, are summarized. We go over an excerpt of notable anomalies that this EGSE suffered through its operation, along with investigations and resolutions. Lessons learned, areas of improvement as part of future work, and recommendations for future implementations for similar EGSE’s, are shared.

Levine, Dan↗
NASA NTRS1997

Case Study of an Object-Oriented System: EOSDIS

Mission to Planet Earth (MTPE) is a long-term NASA research mission to study the processes leading to global climate change. The Earth Observing System (EOS) is a NASA campaign of satellite observatories that are a major component of MTPE. The EOS Data and Information System (EOSDIS) is another component of MTPE that will provide the Earth science community with easy, affordable, and reliable access to Earth science data. EOSDIS is a distributed system, with major facilities at six Distributed Active Archive Centers (DAACS) located throughout the United States. The EOSDIS software architecture is being designed to receive, process, and archive several terabytes of science data on a daily basis. Thousands of science users and perhaps several hundred thousands of non-science users are expected to access the system. While there are many segments in EOSDIS (e.g., flight operations, network) this case study discusses the development of the science data processing segment (SDPS). We briefly review the architecture of the system, the goals of the SDPS, and the development progress to date. This study highlights key software development challenges, experiences integrating COTS, and the difficulties of managing a complex system development effort.

Behnke, Jeanne↗
NASA NTRS2000

Hardware Development Process for Human Research Facility Applications

The simple goal of the Human Research Facility (HRF) is to conduct human research experiments on the International Space Station (ISS) astronauts during long-duration missions. This is accomplished by providing integration and operation of the necessary hardware and software capabilities. A typical hardware development flow consists of five stages: functional inputs and requirements definition, market research, design life cycle through hardware delivery, crew training, and mission support. The purpose of this presentation is to guide the audience through the early hardware development process: requirement definition through selecting a development path. Specific HRF equipment is used to illustrate the hardware development paths. The source of hardware requirements is the science community and HRF program. The HRF Science Working Group, consisting of SCientists from various medical disciplines, defined a basic set of equipment with functional requirements. This established the performance requirements of the hardware. HRF program requirements focus on making the hardware safe and operational in a space environment. This includes structural, thermal, human factors, and material requirements. Science and HRF program requirements are defined in a hardware requirements document which includes verification methods. Once the hardware is fabricated, requirements are verified by inspection, test, analysis, or demonstration. All data is compiled and reviewed to certify the hardware for flight. Obviously, the basis for all hardware development activities is requirement definition. Full and complete requirement definition is ideal prior to initiating the hardware development. However, this is generally not the case, but the hardware team typically has functional inputs as a guide. The first step is for engineers to conduct market research based on the functional inputs provided by scientists. CommerCially available products are evaluated against the science requirements as well as modifications needed to meet program requirements. Options are consolidated and the hardware development team reaches a hardware development decision point. Within budget and schedule constraints, the team must decide whether or not to complete the hardware as an in-house, subcontract with vendor, or commercial-off-the-shelf (COTS) development. An in-house development indicates NASA personnel or a contractor builds the hardware at a NASA site. A subcontract development is completed off-site by a commercial company. A COTS item is a vendor product available by ordering a specific part number. The team evaluates the pros and cons of each development path. For example, in-bouse developments utilize existing corporate knowledge regarding bow to build equipment for use in space. However, technical expertise would be required to fully understand the medical equipment capabilities, such as for an ultrasound system. It may require additional time and funding to gain the expertise that commercially exists. The major benefit of subcontracting a hardware development is the product is delivered as an end-item and commercial expertise is utilized. On the other hand, NASA has limited control over schedule delays. The final option of COTS or modified COTS equipment is a compromise between in-house and subcontracts. A vendor product may exist that meets all functional requirements but req uires in-house modifications for successful operation in a space environment. The HRF utilizes equipment developed using all of the paths described: inhouse, subcontract, and modified COTS.

Bauer, Liz↗
NASA NTRS1994

Spacecraft maximum allowable concentrations for selected airborne contaminants, volume 1

As part of its efforts to promote safe conditions aboard spacecraft, NASA requested the National Research Council (NRC) to develop guidelines for establishing spacecraft maximum allowable concentrations (SMAC's) for contaminants, and to review SMAC's for various spacecraft contaminants to determine whether NASA's recommended exposure limits are consistent with the guidelines recommended by the subcommittee. In response to NASA's request, the NRC organized the Subcommittee on Guidelines for Developing Spacecraft Maximum Allowable Concentrations for Space Station Contaminants within the Committee on Toxicology (COT). In the first phase of its work, the subcommittee developed the criteria and methods for preparing SMAC's for spacecraft contaminants. The subcommittee's report, entitled Guidelines for Developing Spacecraft Maximum Allowable Concentrations for Space Station Contaminants, was published in 1992. The executive summary of that report is reprinted as Appendix A of this volume. In the second phase of the study, the Subcommittee on Spacecraft Maximum Allowable Concentrations reviewed reports prepared by NASA scientists and contractors recommending SMAC's for 35 spacecraft contaminants. The subcommittee sought to determine whether the SMAC reports were consistent with the 1992 guidelines. Appendix B of this volume contains the first 11 SMAC reports that have been reviewed for their application of the guidelines developed in the first phase of this activity and approved by the subcommittee.

National Research Council↗
NASA NTRS1996

Spacecraft Maximum Allowable Concentrations for Selected Airborne Contaminants

As part of its efforts to promote safe conditions aboard spacecraft, NASA requested the National Research Council (NRC) to develop guidelines for establishing spacecraft maximum allowable concentrations (SMACs) for contaminants, and to review SMACs for various spacecraft contaminants to determine whether NASA's recommended exposure limits are consistent with the guidelines recommended by the subcommittee. In response to NASA's request, the NRC organized the Subcommittee on Guidelines for Developing Spacecraft Maximum Allowable Concentrations for Space Station Contaminants within the Committee on Toxicology (COT). In the first phase of its work, the subcommittee developed the criteria and methods for preparing SMACs for spacecraft contaminants. The subcommittee's report, entitled Guidelines for Developing Spacecraft Maximum Allowable Concentrations for Space Station Contaminants , was published in 1992. The executive summary of that report is reprinted as Appendix A of this volume. In the second phase of the study, the Subcommittee on Spacecraft Maximum Allowable Concentrations reviewed reports prepared by NASA scientists and contractors recommending SMACs for approximately 35 spacecraft contaminants. The subcommittee sought to determine whether the SMAC reports were consistent with the 1992 guidelines. Appendix B of this volume contains the SMAC reports for 12 chemical contaminants that have been reviewed for their application of the guidelines developed in the first phase of this activity and approved by the subcommittee. This report is the second volume in the series Spacecraft McLrimum Allowable Concentrations for Space Station Contaminants . The first volume was published in 1994.

National Research Council↗
NASA NTRS2010

Preliminary Evaluation of Commercial Off the Shelf (COTS) Packing Materials for Flight Medication Dispenser (FMD) Technology Development

With the advent of longer duration space missions, pharmaceutical use in space has increased. During the first 33 space shuttle missions, crew members took more than 500 individual doses of 31 different medications . Anecdotal reports from crew members described medications as generally "well tolerated" and "effective". However, reported use of increased medication doses and discrepancies in ground vs. flight efficacy may result from reduced potency or altered bioavailability due to changes in chemical and/or physical parameters of pharmaceutical stability. Based on preliminary results from a ground-based irradiation and an inflight study on pharmaceutical stability, three susceptible medications, Amoxicillin/Clavulanate and Sulfamethoxazole/trimethoprim antibiotics tablets and promethazine (PMZ), an antihistamine were selected for testing using two types of Oliver-Tolas bags, TPC-1475(Clear) and TPF-0599B (Foil) for radiation Shielding effectiveness. The material composition of the bags included aluminum coated Mylar sheathing coated with multifunctional nanocomposities based on polyethylene with dispersed boron-rich nanophases. Two bags of each medication were irradiated for different time intervals with 14.6 rad/min to achieve 0.1 Gy, 1 Gy and 10 Gy of cumulative radiation dose. Active pharmaceutical content (API) in each medication was determined and results analyzed. No significant difference in API content was observed between control and irradiated samples for both antibiotic tablets suggesting both types of bags may offer protection against gamma radiation; results with PMZ were inconclusive. These preliminary results suggest that Oliver-Tolas TPL-1475 and TPF-0599B materials may possess characteristics suitable for protection against ionizing radiation and can be considered for designing and further testing of FMD technology.

Du, Brian↗
NASA NTRS2010

COTS/CRS: KSC Evolving Host Initiatives with Commercial Space Partners

NASA's Commercial Crew and Cargo Program Office (C3PO) leads the agency's commercial efforts to stimulate United States private companies as the shuttle program comes to a close. Through the Commercial Orbital Transportation Services (COTS) program, two companies, SpaceX and Orbital, were selected to demonstrate their ability to perform flights to the International Space Station. The Commercial Resupply Services (CRS) Project leverages off the COTS experience, and awarded these two private companies contracts to resupply the International Space Station after shuttle fly out. As a 2010 summer intern, I supported the COTS/CRS team in their team meetings, attended and contributed to project discussions and planning, and assisted in developing visual representations for the variety of processes and organizational endeavors required for the program to run smoothly. One aspect of the COTS/CRS program gives the involved private companies the opportunity to request available services from Kennedy Space Center (KSC); one of my projects included assisting in the development of a related Task Order Request (TOR) process. In addition, an integral part of the project was to maintain and enhance the team database for processing the variety of TORS. My experience in the project gave me great insight into the growing field of commercial space activities. The development of the TOR process involved coordinating representatives from a variety of backgrounds at KSC. A clear and concise visual representation of the TOR process in the form of a flow chart was necessary to successfully implement a task order request from one of NASA's commercial partners. The goals of the process charts were to communicate the team's ideas and foster a common thought process while at the same time allow the process to grow and evolve. It was critical that the requests from the private companies were addressed quickly and thoroughly as the process developed this summer is expected to have extensive future use.

Yohpe, Megan↗
NASA NTRS2022

Recommendations for Developing Space Suit Integrated Food Systems and Delivering Nutrition Before, During, and After Lunar EVA

The concept of providing hydration and nutrition during extravehicular activity (EVA) is nearly as old as the space program itself. Astronauts currently have access to 32 ounces of water through a disposable in-suit drink bag (DIDB) while they are confined to their space suit. During the Apollo program, methods for providing food/nutrition to crewmembers in space suits were included as contingency solutions (1) but were eventually abandoned. The main reasons that provision of in-suit nutrition beyond water was discontinued after Apollo were the complicated engineering requirements, the additional mass and volume that was required for the applicable food formulations, hardware needed for a suit-specialized food system, and because the perceived need for in-suit nutrition during EVAs was not sufficient during the Space Shuttle and the International Space Station (ISS) eras. A custom-made 165-kcal fruit bar was fitted into the EVA suit during the Space Shuttle program, but crewmembers rarely consumed it during the EVA and rather chose to consume it before or after suited activities (2). Since 2011, between 4 and 13 EVAs have been conducted from the ISS each year, with durations ranging from 1:32 to 8:17 hours (https://www.nasa.gov/mission_pages/station/spacewalks ). It has been acceptable for the crewmembers to schedule food intake around these relatively infrequent suited activities. Because upcoming Artemis missions will include nominal 8-hour lunar exploration EVAs that are expected to increase in frequency to several (4 to 5) sorties per week (3), the desire for an in-suit nutrition system has increased. In preparation for these missions, requirements to provide in-suit nutrition has been outlined in the most recent NASA Human Spaceflight Standards documents (4). Establishing general recommendations for in-suit nutrition systems precedes the selection of a lunar EVA pressure suit system. The current document is intended to define the rationale for nutrition to support EVA (whether in-suit or from the pantry in the habitat), document the requirements, constraints, and crewmember preferences, and recommend necessary next steps for developing an in-suit EVA nutrition system. Assessments presented in this report include a review of commercial off-the-shelf (COTS) food products as potential in-suit formulations, a comparison of conceptual designs for delivering nutrition to a crewmember while confined to a space suit, an evaluation of space suit volume constraints for the placement of in-suit nutrition systems, and feedback from astronauts regarding preferences for nutrition support during EVA. Based on these assessments, recommendations were formulated that can be used to help develop a method to deliver nutrition safely and acceptably to a crewmember while they are confined to a space suit for an EVA duration of up to 8 hours, and a total time in the suit of up to 12 hours.

space suit↗
NASA NTRS1996

Development of Secondary Archive System at Goddard Space Flight Center Version 0 Distributed Active Archive Center

The Goddard Space Flight Center (GSFC) version 0 Distributed Active Archive Center (DAAC) has been developed to support existing and pre Earth Observing System (EOS) Earth science datasets, facilitate the scientific research, and test EOS data and information system (EOSDIS) concepts. To ensure that no data is ever lost, each product received at GSFC DAAC is archived on two different media, VHS and digital linear tape (DLT). The first copy is made on VHS tape and is under the control of UniTree. The second and third copies are made to DLT and VHS media under a custom built software package named 'Archer'. While Archer provides only a subset of the functions available with commercial software like UniTree, it supports migration between near-line and off-line media and offers much greater performance and flexibility to satisfy the specific needs of a data center. Archer is specifically designed to maximize total system throughput, rather than focusing on the turn-around time for individual files. The commercial off the shelf software (COTS) hierarchical storage management (HSM) products evaluated were mainly concerned with transparent, interactive, file access to the end-user, rather than a batch-orientated, optimizable (based on known data file characteristics) data archive and retrieval system. This is critical to the distribution requirements of the GSFC DAAC where orders for 5000 or more files at a time are received. Archer has the ability to queue many thousands of file requests and to sort these requests into internal processing schedules that optimize overall throughput. Specifically, mount and dismount, tape load and unload cycles, and tape motion are minimized. This feature did not seem to be available in many COTS pacages. Archer also uses a generic tar tape format that allows tapes to be read by many different systems rather than the proprietary format found in most COTS packages. This paper discusses some of the specific requirements at GSFC DAAC, the motivations for implementing the Archer system, and presents a discussion of the Archer design that resulted.

Sherman, Mark↗
NASA NTRS2009

Assessment of SOI AND Gate, Type CHT-7408, for Operation in Extreme Temperature Environments

Electronic parts based on silicon-on-insulator (SOI) technology are finding widespread applications due to their ability to operate in harsh environments and the benefits they offer as compared to their silicon counterparts. Due to their construction, they are tailored for high temperature operation and show good tolerance to radiation events. In addition, their inherent design lessens the formation of parasitic junctions, thereby reducing leakage currents, decreasing power consumption, and enhancing speed. These devices are typically rated in temperature capability from -55 C to about +225 C, and their characteristics over this temperature range are documented in data sheets. Since electronics in some of NASA space exploration missions are required to operate under extreme temperature conditions, both cold and hot, their characteristic behavior within the full temperature spectrum must be determined to establish suitability for use in space applications. The effects of extreme temperature exposure on the performance of a new commercial-off-the-shelf (COTS) SOI AND gate device were evaluated in this work. The high temperature, quad 2-inputs AND gate device, which was recently introduced by CISSOID, is fabricated using a CMOS SOI process. Some of the specifications of the CHT-7408 chip are listed in a table. By supplying a constant DC voltage to one gate input and a 10 kHz square wave into the other associated gate input, the chip was evaluated in terms of output response, output rise (t(sub r)) and fall times (tf), and propagation delays (using a 50% level between input and output during low to high (tPLH) and high to low (tPHL) transitions). The supply current of the gate circuit was also obtained. These parameters were recorded at various test temperatures between -195 C and +250 C using a Sun Systems environmental chamber programmed at a temperature rate of change of 10 C/min. In addition, the effects of thermal cycling on this chip were determined by exposing it to a total of 12 cycles between -195 C and +250 C. Following the cycling activity, measurements were performed again at the test temperatures of -195 C, +21 C, and +250 C.

Patterson, Richard↗