Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “PROCUREMENT”

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 721 records · Page 40

Low-Energy Microfocus X-Ray Source for Enhanced Testing Capability in the Stray Light Facility

Research toward high-resolution, soft x-ray optics (mirrors and gratings) necessary for the next generation large x-ray observatories requires x-ray testing using a low-energy x-ray source with fine angular size (<1 arcsecond). To accommodate this somewhat demanding requirement, NASA Marshall Space Flight Center (MSFC) has procured a custom, windowless low-energy microfocus (approximately 0.1 mm spot) x-ray source from TruFocus Corporation that mates directly to the Stray Light Facility (SLF). MSFC X-ray Astronomy team members are internationally recognized for their expertise in the development, fabrication, and testing of grazing-incidence optics for x-ray telescopes. One of the key MSFC facilities for testing novel x-ray instrumentation is the SLF. This facility is an approximately 100-m-long beam line equipped with multiple x-ray sources and detectors. This new source adds to the already robust compliment of instrumentation, allowing MSFC to support additional internal and community x-ray testing needs.

Gaskin, Jessica↗

A Framework for Assessing the Reusability of Hardware (Reusable Rocket Engines)

Within the space flight community, reusability has taken center stage as the new buzzword. In order for reusable hardware to be competitive with its expendable counterpart, two major elements must be closely scrutinized. First, recovery and refurbishment costs must be lower than the development and acquisition costs. Additionally, the reliability for reused hardware must remain the same (or nearly the same) as "first use" hardware. Therefore, it is imperative that a systematic approach be established to enhance the development of reusable systems. However, before the decision can be made on whether it is more beneficial to reuse hardware or to replace it, the parameters that are needed to deem hardware worthy of reuse must be identified. For reusable hardware to be successful, the factors that must be considered are reliability (integrity, life, number of uses), operability (maintenance, accessibility), and cost (procurement, retrieval, refurbishment). These three factors are essential to the successful implementation of reusability while enabling the ability to meet performance goals. Past and present strategies and attempts at reuse within the space industry will be examined to identify important attributes of reusability that can be used to evaluate hardware when contemplating reusable versus expendable options. This paper will examine why reuse must be stated as an initial requirement rather than included as an afterthought in the final design. Late in the process, changes in the overall objective/purpose of components typically have adverse effects that potentially negate the benefits. A methodology for assessing the viability of reusing hardware will be presented by using the Space Shuttle Main Engine (SSME) to validate the approach. Because reliability, operability, and costs are key drivers in making this critical decision, they will be used to assess requirements for reuse as applied to components of the SSME.

Childress-Thompson, Rhonda↗

A Framework for Assessing the Reusability of Hardware (Reusable Rocket Engines)

Within the space flight community, reusability has taken center stage as the new buzzword. In order for reusable hardware to be competitive with its expendable counterpart, two major elements must be closely scrutinized. First, recovery and refurbishment costs must be lower than the development and acquisition costs. Additionally, the reliability for reused hardware must remain the same (or nearly the same) as "first use" hardware. Therefore, it is imperative that a systematic approach be established to enhance the development of reusable systems. However, before the decision can be made on whether it is more beneficial to reuse hardware or to replace it, the parameters that are needed to deem hardware worthy of reuse must be identified. For reusable hardware to be successful, the factors that must be considered are reliability (integrity, life, number of uses), operability (maintenance, accessibility), and cost (procurement, retrieval, refurbishment). These three factors are essential to the successful implementation of reusability while enabling the ability to meet performance goals. Past and present strategies and attempts at reuse within the space industry will be examined to identify important attributes of reusability that can be used to evaluate hardware when contemplating reusable versus expendable options. This paper will examine why reuse must be stated as an initial requirement rather than included as an afterthought in the final design. Late in the process, changes in the overall objective/purpose of components typically have adverse effects that potentially negate the benefits. A methodology for assessing the viability of reusing hardware will be presented by using the Space Shuttle Main Engine (SSME) to validate the approach. Because reliability, operability, and costs are key drivers in making this critical decision, they will be used to assess requirements for reuse as applied to components of the SSME.

Childress-Thompson, Rhonda↗

LAVA Pressure Transducer Trade Study

The Regolith and Environment Science and Oxygen and Lunar Volatile Extraction (RESOLVE) payload will transport the (LAVA) subsystem to hydrogen-rich locations on the moon supporting NASA's in-situ resource utilization (ISRU) programs. There, the LAVA subsystem will analyze volatiles that evolve from heated regolith samples in order to quantify how much water is present. To do this, the system needs resilient pressure transducers (PTs) to calculate the moles in the gas samples. The PT trade study includes a comparison of newly-procured models to a baseline unit with prior flight history in order to determine the PT model with the best survivability in flight-forward conditions.

Trade Study↗

Development of Reliable Life Support Systems

The life support systems on the International Space Station (ISS) are the culmination of an extensive effort encompassing development, design, and test to provide the highest possible confidence in their operation on ISS. Many years of development testing are initially performed to identify the optimum technology and the optimum operational approach. The success of this development program depends on the accuracy of the system interfaces. The critical interfaces include the specific operational environment, the composition of the waste stream to be processed and the quality of the product. Once the development program is complete, a detailed system schematic is built based on the specific design requirements, followed by component procurement, assembly, and acceptance testing. A successful acceptance test again depends on accurately simulating the anticipated environment on ISS. The ISS Water Recovery System (WRS) provides an excellent example of where this process worked, as well as lessons learned that can be applied to the success of future missions. More importantly, ISS has provided a test bed to identify these design issues. Mechanical design issues have included an unreliable harmonic drive train in the Urine Processor's fluids pump, and seals in the Water Processor's Catalytic Reactor with insufficient life at the operational temperature. Systems issues have included elevated calcium in crew urine (due to microgravity effect) that resulted in precipitation at the desired water recovery rate, and the presence of an organosilicon compound (dimethylsilanediol) in the condensate that is not well removed by the water treatment process. Modifications to the WRS to address these issues are either complete (and now being evaluated on ISS) or are currently in work to insure the WRS has the required reliability before embarking on a mission to Mars.

Carter, Layne↗

Strategies for SEE Hardness Assurance - From Buy-It-And-Fly-It to Bullet Proof

This part of the course first outlines the conventional Single Event Effect (SEE), radiation hardness assurance (RHA) approach, which emphasizes mission success. Next, Dr. Ladbury will discuss the challenges posed by new satellite platforms (e.g., cubesats, nanosats, etc.), where cost and schedule receive emphasis equal to if not greater than mission success. These additional pressures, along with growing demands to reduce size, weight and power, coupled with increased performance, drive many projects toward expanding their use of commercial-off-the-shelf (COTS) technologies. While this may reduce direct parts cost and procurement lead times, it undermines many cost-reduction strategies used for conventional SEE RHA and can make radiation testing and analysis one of the most significant risks or worse, a risk neglected altogether. That section will end with some approaches for restoring balance in the troika of mission success, cost, and schedule. This is captured in SEE RHA as risk management: identify the threat, evaluate the threat, and mitigate the threat.

commercial-off-the-shelf (COTS)↗

Strategies for SEE Hardness Assurance From Buy-It-And-Fly-It to Bullet Proof

This part of the course first outlines the conventional Single Event Effect (SEE), radiation hardness assurance (RHA) approach, which emphasizes mission success. Next, Dr. Ladbury will discuss the challenges posed by new satellite platforms (e.g., cubesats, nanosats, etc.), where cost and schedule receive emphasis equal to if not greater than mission success. These additional pressures, along with growing demands to reduce size, weight and power, coupled with increased performance, drive many projects toward expanding their use of commercial-off-the-shelf (COTS) technologies. While this may reduce direct parts cost and procurement lead times, it undermines many cost-reduction strategies used for conventional SEE RHA and can make radiation testing and analysis one of the most significant risksor worse, a risk neglected altogether. That section will end with some approaches for restoring balance in the troika of mission success, cost, and schedule. This is captured in SEE RHA as risk management: identify the threat, evaluate the threat, and mitigate the threat.

commercial-off-the-shelf (COTS)↗

Expanded Guidance for NASA Systems Engineering. Volume 2: Crosscutting Topics, Special Topics, and Appendices

Historically, most successful NASA projects have depended on effectively blending project management, systems engineering, and technical expertise among NASA, contractors, and third parties. Underlying these successes are a variety of agreements (e.g., contract, memorandum of understanding, grant, cooperative agreement) between NASA organizations or between NASA and other Government agencies, Government organizations, companies, universities, research laboratories, and so on. To simplify the discussions, the term "contract" is used to encompass these agreements. This section focuses on the NASA systems engineering activities pertinent to awarding a contract, managing contract performance, and completing a contract. In particular, NASA systems engineering interfaces to the procurement process are covered, since the NASA engineering technical team plays a key role in the development and evaluation of contract documentation. Contractors and third parties perform activities that supplement (or substitute for) the NASA project technical team accomplishment of the NASA common systems engineering technical process activities and requirements outlined in this guide. Since contractors might be involved in any part of the systems engineering life cycle, the NASA project technical team needs to know how to prepare for, allocate or perform, and implement surveillance of technical activities that are allocated to contractors.

Steven R Hirshorn↗

Development of Reliable Life Support Systems

The life support systems on the International Space Station (ISS) are the culmination of an extensive effort encompassing development, design, and test to provide the highest possible confidence in their operation on ISS. Many years of development testing are initially performed to identify the optimum technology and the optimum operational approach. The success of this development program depends on the accuracy of the system interfaces. The critical interfaces include the specific operational environment, the composition of the waste stream to be processed and the quality of the product. Once the development program is complete, a detailed system schematic is built based on the specific design requirements, followed by component procurement, assembly, and acceptance testing. A successful acceptance test again depends on accurately simulating the anticipated environment on ISS. The ISS Water Recovery System (WRS) provides an excellent example of where this process worked, as well as lessons learned that can be applied to the success of future missions. More importantly, ISS has provided a test bed to identify these design issues. Mechanical design issues have included an unreliable harmonic drive train in the Urine Processor's fluids pump, and seals in the Water Processor's Catalytic Reactor with insufficient life at the operational temperature. Systems issues have included elevated calcium in crew urine (due to microgravity effect) that resulted in precipitation at the desired water recovery rate, and the presence of an organosilicon compound (dimethylsilanediol) in the condensate that is not well removed by the water treatment process. Modifications to the WRS to address these issues are either complete (and now being evaluated on ISS) or are currently in work to insure the WRS has the required reliability before embarking on a mission to Mars.

Carter, Layne↗

NASA Operational Simulator for Small Satellites: Tools for Software Based Validation and Verification of Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of tools to aid in areas such as software development, integration test (IT), mission operations training, verification and validation (VV), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, an operator interface-ground station, dynamics and environment simulations, and software-based hardware models. NOS3 enables the development of flight software (FSW) early in the project life cycle, when access to hardware is typically not available. For small satellites there are extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETU). Considering the difficulty of providing a hardware test-bed to each developer tester, hardware models are modeled based upon characteristic data or manufacturers data sheets for each individual component. The fidelity of each hardware models is such that FSW executes unaware that physical hardware is not present. This allows binaries to be compiled for both the simulation environment, and the flight computer, without changing the FSW source code. For hardware models that provide data dependent on the environment, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulation) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for VV of larger missions such as James Webb Space Telescope (JWST). As hardware is procured, drivers can be added to the environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. The open-source operator interface used in NOS3 is COSMOS from Ball Aerospace. For testing, plug-ins are implemented in COSMOS to control the NOS3 simulations, while the command and telemetry tools available in COSMOS are used to communicate with FSW. NOS3 is actively being used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat. As NOS3 matures, hardware models have been added for common CubeSat components such as Novatel GPS receivers, ClydeSpace electrical power systems and batteries, ISISpace antenna systems, etc. In the future, NASA IVV plans to distribute NOS3 to other CubeSat developers and release the suite to the open-source community.

Verification↗

Creating Innovative Frameworks to Spur Cultural Change at NASA Armstrong Flight Research Center

Changing the culture of an organization is a monumental task that often takes years and has no set formula. Steps can be taken, however, to spur cultural change by creating spaces and infrastructure to serve as the initial driving force. An innovation space and a bicycle sharing (bike share) program were implemented at the National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC) (Edwards, California) with a vision toward connecting Center personnel, fostering collaboration and innovation, retaining newer employees, promoting flexibility, and improving the culture and workplace atmosphere. This paper discusses the steps taken, challenges faced, novel culture-change-focused design elements, lessons learned, acquired metrics, and how these initiated cultural change at AFRC. For both the innovation space and the bike share program, funding was negotiated and provided through the NASA Convergent Aeronautics Solutions (CAS) project, which was seeking to improve the innovation and collaboration capabilities at each of the four NASA aeronautics Centers. Key stakeholders across AFRC from upper management, facilities, safety, engineering, and procurement were identified early in the process and were consulted and included throughout execution to ensure that any encountered roadblocks could be easily navigated. Research was then conducted by attending conferences and visiting culture-changing organizations both inside and outside United States Government agencies. Distilling the research, identifying available space, and deciding on specific design elements for the space was conducted by a subset of individuals of diverse backgrounds to enable quick, effective decision-making. Decisions were made with the intent to increase usage and diversity of users of the space; care was taken to ensure a well-crafted atmosphere that would foster the desired culture change. The allocated physical space required major structural modifications, new furniture, and new capabilities that would bring people in. Decisions and desires underwent a rapid reiterative process in order to stay within budget and short deadlines, while holding firm to what was seen as fundamental elements of an innovation space. The framework for cultural change being established, the more difficult task began: incubating the desired culture. Intentional workday use of the innovation space was encouraged, and organized events coordinated in order to truly foster culture change. Such incubation supports the organic spread of culture change to all areas of AFRC. This framework was complemented and expanded by the implementation of the bike share program. Steps for implementation included bike selection based on lessons learned, creating bike stations and signage, implementing bike share rules, and building a volunteer maintenance infrastructure. A novel user-reporting feedback system at each bike station is a low-impact method of capturing usage metrics. Due to the nature of the work conducted at AFRC, the bike share program and feedback system were negotiated and vetted through various organizations including legal, safety, and operations. The innovation space and the bike share program together are an effective initial framework for innovation and collaboration. Culture change takes time, but the innovation space and the bike share program are already showing signs of making a positive impact on the AFRC workforce.

rooms↗

A Flexible Control Center Architecture for Support of Diverse Spaceflight Missions

The Ames Multi-Mission Operations Center (MMOC) enables and supports flight and science operations for Ames' spaceflight missions. The MMOC is composed of the facilities, networks, information technology equipment, software, and system administration services needed by flight projects to effectively and efficiently perform all mission functions, including planning, scheduling, command, telemetry processing, and science analysis. The MMOC's ready-to-use services reduce start-up time, shorten procurement and provisioning and allow mission planning efforts to focus more on science and less on infrastructure. The architecture of the MMOC was designed from the start for flexibility, so that it can readily support multiple missions of greatly varying size and complexity while simultaneously keeping costs low.

Differding, Joan C.↗

NASA Mars 2020 Landed Mission Development

In January of 2014, NASA received fifty-eight proposals from U.S. and international teams for science and exploration technology investigations, for consideration for inclusion as part of NASA's next mobile landed mission to Mars. The results of the competitive procurement were released in late July of 2014: Seven payloads were selected for the investigations that would contribute to meeting the overall objectives of the mission. The extraordinary scientific and technology development interest in the Mars 2020 mission is a direct result of NASA's sustained and coordinated plan for the exploration of Mars, and ultimately, its search for life elsewhere in the universe. The Mars 2020 Mission will preserve the heritage and directly build upon NASA's Mars Science Laboratory Mission and Curiosity Rover to implement its mission. In this paper, early development history leading to its development announcement, as well as key development status and design features for its implementation, is summarized.

MSR↗

The Second European Service Module (ESM-2) Evolutions, Production and Challenges

This paper presents an overview of the Second European Service Module (ESM-2), the second in a series of European Service Modules produced as part of the Barter agreement between NASA and ESA for the Orion Program. The European Industrial consortium is led by the ESA prime contractor Airbus Defence and Space in Bremen. ESA and Airbus signed the ESM-2 contract on 16 February 2017, for this key element of the Orion Exploration Mission 2 (EM-2). EM-2 is the first crewed mission for Orion and will take astronauts farther into the solar system than humanity has ever travelled. EM-2 will also be a historic mission for Europe, as the ESM-2 will be the first European spacecraft to be part of a human transportation system carrying humans beyond low Earth orbit. ESM-2 is mainly a recurring production following ESM-1. Nevertheless, there are a number of important changes being implemented, for example, to incorporate upgrades to further enhance safety and reliability. The challenging delivery schedule for ESM-2 has driven the need to commence manufacturing prior to completion of the qualification on ESM-1. In addition, some requirement deviations and non-compliances approved for ESM-1 have resulted in modifications for ESM-2. In order to manage the competing constraints effectively, the ESM-2 Team has put in place a number of novel approaches to manage schedule, risk, and technical changes. Airbus has set up multi-functional teams according to an approach known as "Major Spacecraft Deliveries" consisting of quality assurance, engineering and procurement. The risk of starting manufacturing prior to qualification is managed through a special risk share agreement. This agreement necessitates rigorous risk reviews across the board for all manufacturing, assembly, integration and test milestones. The ESM-2 changes are managed by Configuration Management, but Airbus has also introduced the Technical Baseline Matrix to provide a transparent top-level overview of the changes from ESM-1 to ESM-2. The tool provides the basis for ESM-2 design and development needs, decisions, as well as the input for the Orion EM-2 Critical Design Review (CDR). The main technical evolutions, status of the production and the novel management approaches for ESM-2 are presented and discussed in the paper.

Orion European Service Module Programme↗

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a streamlined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to pro-ceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule, development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor downselection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measurements for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jacob↗

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a stream-lined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to proceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule. Development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor down-selection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measure-ments for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jake↗

Qualification of a Hybrid Propulsion System for the Mars Ascent Vehicle

Technology for a hybrid based propulsion system is being developed to support a potential Mars Sample Return campaign. A Mars Ascent Vehicle (MAV) concept for launching samples off of Mars, and delivering them to orbit for further transport to Earth may utilize hybrid propulsion due to the predicted favorable low temperature characteristics and high performance of this option. However, the hybrid option is still undergoing technology development to demonstrate these capabilities. Once development of a capable hybrid propulsion system is proven, further work will be required. This will include environmental testing relative to the mission, and integration with the vehicle reaction control systems and payload. Qualification of such a system will be a significant effort. It will require specialized procurements for the propellants and environments involved, and further testing of the more specialized designs. This paper details an estimate of the tasks required to complete development efforts from Technical Readiness Level 5 (TRL5) through qualification. A success based program was formulated to reach the required performance metrics sufficient for a standard Preliminary Design Review (PDR). Using task level inputs from team members cost and schedule were conceived for continued progress to Critical Design Review (CDR), then through Qualification.

Prince, Andrew↗