SEARCH · Engineering Papers

Results for “CONTRACTORS”

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

SourceResearch connectionFrom yearThrough year

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

At least 1,351 records · Page 75

All sources NASA NTRS DOE OSTI

NASA NTRS2011

Orion Absolute Navigation System Progress and Challenges

The Orion spacecraft is being designed as NASA's next-generation exploration vehicle for crewed missions beyond Low-Earth Orbit. The navigation system for the Orion spacecraft is being designed in a Multi-Organizational Design Environment (MODE) team including contractor and NASA personnel. The system uses an Extended Kalman Filter to process measurements and determine the state. The design of the navigation system has undergone several iterations and modifications since its inception, and continues as a work-in-progress. This paper seeks to benchmark the current state of the design and some of the rationale and analysis behind it. There are specific challenges to address when preparing a timely and effective design for the Exploration Flight Test (EFT-1), while still looking ahead and providing software extensibility for future exploration missions. The primary measurements in a Near-Earth or Mid-Earth environment consist of GPS pseudorange and deltarange, but for future explorations missions the use of star-tracker and optical navigation sources need to be considered. Discussions are presented for state size and composition, processing techniques, and consider states. A presentation is given for the processing technique using the computationally stable and robust UDU formulation with an Agee-Turner Rank-One update. This allows for computational savings when dealing with many parameters which are modeled as slowly varying Gauss-Markov processes. Preliminary analysis shows up to a 50% reduction in computation versus a more traditional formulation. Several state elements are discussed and evaluated, including position, velocity, attitude, clock bias/drift, and GPS measurement biases in addition to bias, scale factor, misalignment, and non-orthogonalities of the accelerometers and gyroscopes. Another consideration is the initialization of the EKF in various scenarios. Scenarios such as single-event upset, ground command, pad alignment, cold start are discussed as are strategies for whole and partial state updates as well as covariance considerations. Strategies are given for dealing with latent measurements and high-rate propagation using multi-rate architecture. The details of the rate groups and the data ow between the elements is discussed and evaluated.

Holt, Greg N.↗

NASA NTRS2005

Software Architecture of the NASA Shuttle Ground Operations Simulator - SGOS

The SGOS executive and its subsystems have been an integral component of the Shuttle Launch Safety Program for almost thirty years. It is usable (via the LAN) by over 2000 NASA employees at the Kennedy Space Center and 11,000 contractors. SGOS supports over 800 models comprised of several hundred thousand lines of code and over 1,000 MCP procedures. Yet neither language has a for loop!! The simulation software described in this paper is used to train ground controllers and to certify launch countdown readiness.

Cook, Robert P.↗

NASA NTRS2005

Materials Science Laboratory

The NASA Materials Science Laboratory (MSL) provides science and engineering services to NASA and Contractor customers at KSC, including those working for the Space Shuttle. International Space Station. and Launch Services Programs. These services include: (1) Independent/unbiased failure analysis (2) Support to Accident/Mishap Investigation Boards (3) Materials testing and evaluation (4) Materials and Processes (M&P) engineering consultation (5) Metrology (6) Chemical analysis (including ID of unknown materials) (7) Mechanical design and fabrication We provide unique solutions to unusual and urgent problems associated with aerospace flight hardware, ground support equipment and related facilities.

Jackson, Dionne↗

NASA NTRS2011

NASA Planning for Orion Multi-Purpose Crew Vehicle Ground Operations

The NASA Orion Ground Processing Team was originally formed by the Kennedy Space Center (KSC) Constellation (Cx) Project Office's Orion Division to define, refine and mature pre-launch and post-landing ground operations for the Orion human spacecraft. The multidisciplined KSC Orion team consisted of KSC civil servant, SAIC, Productivity Apex, Inc. and Boeing-CAPPS engineers, project managers and safety engineers, as well as engineers from Constellation's Orion Project and Lockheed Martin Orion Prime contractor. The team evaluated the Orion design configurations as the spacecraft concept matured between Systems Design Review (SDR), Systems Requirement Review (SRR) and Preliminary Design Review (PDR). The team functionally decomposed prelaunch and post-landing steps at three levels' of detail, or tiers, beginning with functional flow block diagrams (FFBDs). The third tier FFBDs were used to build logic networks and nominal timelines. Orion ground support equipment (GSE) was identified and mapped to each step. This information was subsequently used in developing lower level operations steps in a Ground Operations Planning Document PDR product. Subject matter experts for each spacecraft and GSE subsystem were used to define 5th - 95th percentile processing times for each FFBD step, using the Delphi Method. Discrete event simulations used this information and the logic network to provide processing timeline confidence intervals for launch rate assessments. The team also used the capabilities of the KSC Visualization Lab, the FFBDs and knowledge of the spacecraft, GSE and facilities to build visualizations of Orion pre-launch and postlanding processing at KSC. Visualizations were a powerful tool for communicating planned operations within the KSC community (i.e., Ground Systems design team), and externally to the Orion Project, Lockheed Martin spacecraft designers and other Constellation Program stakeholders during the SRR to PDR timeframe. Other operations planning tools included Kaizen/Lean events, mockups and human factors analysis. The majority of products developed by this team are applicable as KSC prepares 21st Century Ground Systems for the Orion Multi-Purpose Crew Vehicle and Space Launch System.

Letchworth, Gary↗

NASA NTRS2005

Launch Commit Criteria Monitoring Agent

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed a software agent to monitor the Space Shuttle's ground processing telemetry stream. The application, the Launch Commit Criteria Monitoring Agent, increases situational awareness for system and hardware engineers during Shuttle launch countdown. The agent provides autonomous monitoring of the telemetry stream, automatically alerts system engineers when predefined criteria have been met, identifies limit warnings and violations of launch commit criteria, aids Shuttle engineers through troubleshooting procedures, and provides additional insight to verify appropriate troubleshooting of problems by contractors. The agent has successfully detected launch commit criteria warnings and violations on a simulated playback data stream. Efficiency and safety are improved through increased automation.

Semmel, Glenn S.↗

NASA NTRS2012

Recent Improvements to the Copernicus Trajectory Design and Optimization System

Copernicus is a software tool for spacecraft trajectory design and optimization. The latest version (v3.0.1) was released in October 2011. It is available at no cost to NASA centers, government contractors, and organizations with a contractual affiliation with NASA. This paper is a brief overview of the recent development history of Copernicus. An overview of the evolution of the software and a discussion of significant new features and improvements is given, and how the tool is used to design spacecraft missions

Williams, Jacob↗

NASA NTRS2012

Common Data Acquisition Systems (DAS) Software Development for Rocket Propulsion Test (RPT) Test Facilities

The advent of the commercial space launch industry and NASA's more recent resumption of operation of Stennis Space Center's large test facilities after thirty years of contractor control resulted in a need for a non-proprietary data acquisition systems (DAS) software to support government and commercial testing. The software is designed for modularity and adaptability to minimize the software development effort for current and future data systems. An additional benefit of the software's architecture is its ability to easily migrate to other testing facilities thus providing future commonality across Stennis. Adapting the software to other Rocket Propulsion Test (RPT) Centers such as MSFC, White Sands, and Plumbrook Station would provide additional commonality and help reduce testing costs for NASA. Ultimately, the software provides the government with unlimited rights and guarantees privacy of data to commercial entities. The project engaged all RPT Centers and NASA's Independent Verification & Validation facility to enhance product quality. The design consists of a translation layer which provides the transparency of the software application layers to underlying hardware regardless of test facility location and a flexible and easily accessible database. This presentation addresses system technical design, issues encountered, and the status of Stennis development and deployment.

Hebert, Phillip W., Sr.↗

NASA NTRS2012

Ventilator Technologies Sustain Critically Injured Patients

Consider this scenario: A soldier has been critically wounded in a sudden firefight in a remote region of Afghanistan. The soldier s comrades attend to him and radio for help, but the soldier needs immediate medical expertise and treatment that is currently miles away. The connection between medical support for soldiers on the battlefield and astronauts in space may not be immediately obvious. But when it comes to providing adequate critical care, NASA and the military have very similar operational challenges, says Shannon Melton of NASA contractor Wyle Integrated Science and Engineering. Melton works within Johnson Space Center s Space Medicine Division, which supports astronaut crew health before, during, and after flight. In space, we have a limited number of care providers, and those providers are not always clinicians with extensive medical training. We have limited room to provide care, limited consumables, and our environment is not like that of a hospital, she says. The Space Medicine Division s Advanced Projects Group works on combining the expertise of both clinicians and engineers to develop new capabilities that address the challenges of medical support in space, including providing care to distant patients. This field, called telemedicine, blends advanced communications practices and technologies with innovative medical devices and techniques to allow caregivers with limited or no medical experience to support a patient s needs. NASA, just by its nature, has been doing remote medicine since the beginning of the Space Program, says Melton, an engineer in the Advanced Projects Group. Since part of NASA s mandate is to transfer the results of its technological innovation for the benefit of the public, the Agency has worked with doctors and private industry to find ways to apply the benefits of space medicine on Earth. In one such case, a NASA partnership has resulted in new technologies that may improve the quality of emergency medicine for wounded soldiers on the battlefield and regular civilians.

Source record↗

NASA NTRS2012

Bioreactors Drive Advances in Tissue Engineering

It was an unlikely moment for inspiration. Engineers David Wolf and Ray Schwarz stopped by their lab around midday. Wolf, of Johnson Space Center, and Schwarz, with NASA contractor Krug Life Sciences (now Wyle Laboratories Inc.), were part of a team tasked with developing a unique technology with the potential to enhance medical research. But that wasn t the focus at the moment: The pair was rounding up colleagues interested in grabbing some lunch. One of the lab s other Krug engineers, Tinh Trinh, was doing something that made Wolf forget about food. Trinh was toying with an electric drill. He had stuck the barrel of a syringe on the bit; it spun with a high-pitched whirr when he squeezed the drill s trigger. At the time, a multidisciplinary team of engineers and biologists including Wolf, Schwarz, Trinh, and project manager Charles D. Anderson, who formerly led the recovery of the Apollo capsules after splashdown and now worked for Krug was pursuing the development of a technology called a bioreactor, a cylindrical device used to culture human cells. The team s immediate goal was to grow human kidney cells to produce erythropoietin, a hormone that regulates red blood cell production and can be used to treat anemia. But there was a major barrier to the technology s success: Moving the liquid growth media to keep it from stagnating resulted in turbulent conditions that damaged the delicate cells, causing them to quickly die. The team was looking forward to testing the bioreactor in space, hoping the device would perform more effectively in microgravity. But on January 28, 1986, the Space Shuttle Challenger broke apart shortly after launch, killing its seven crewmembers. The subsequent grounding of the shuttle fleet had left researchers with no access to space, and thus no way to study the effects of microgravity on human cells. As Wolf looked from Trinh s syringe-capped drill to where the bioreactor sat on a workbench, he suddenly saw a possible solution to both problems. It dawned on me that rotating the wall of the reactor would solve one of our fundamental fluid mechanical problems, specifically by removing the velocity gradient of the tissue culture fluid media near the reactor s walls, says Wolf. It looked as though it would allow us to suspend the growing cells within the reactor without introducing turbulent fluid mechanical conditions.

Source record↗

NASA NTRS2012

Simulation Tools Model Icing for Aircraft Design

Here s a simple science experiment to try: Place an unopened bottle of distilled water in your freezer. After 2-3 hours, if the water is pure enough, you will notice that it has not frozen. Carefully pour the water into a bowl with a piece of ice in it. When it strikes the ice, the water will instantly freeze. One of the most basic and commonly known scientific facts is that water freezes at around 32 F. But this is not always the case. Water lacking any impurities for ice crystals to form around can be supercooled to even lower temperatures without freezing. High in the atmosphere, water droplets can achieve this delicate, supercooled state. When a plane flies through clouds containing these droplets, the water can strike the airframe and, like the supercooled water hitting the ice in the experiment above, freeze instantly. The ice buildup alters the aerodynamics of the plane - reducing lift and increasing drag - affecting its performance and presenting a safety issue if the plane can no longer fly effectively. In certain circumstances, ice can form inside aircraft engines, another potential hazard. NASA has long studied ways of detecting and countering atmospheric icing conditions as part of the Agency s efforts to enhance aviation safety. To do this, the Icing Branch at Glenn Research Center utilizes a number of world-class tools, including the Center s Icing Research Tunnel and the NASA 607 icing research aircraft, a "flying laboratory" for studying icing conditions. The branch has also developed a suite of software programs to help aircraft and icing protection system designers understand the behavior of ice accumulation on various surfaces and in various conditions. One of these innovations is the LEWICE ice accretion simulation software. Initially developed in the 1980s (when Glenn was known as Lewis Research Center), LEWICE has become one of the most widely used tools in icing research and aircraft design and certification. LEWICE has been transformed over the years from strictly a research tool to one used routinely by industry and other government agencies. Glenn contractor William Wright has been the architect of this development, supported by a team of researchers investigating icing physics, creating validation data, and ensuring development according to standard software engineering practices. The program provides a virtual simulation environment for determining where water droplets strike an airfoil in flight, what kind of ice would result, and what shape that ice would take. Users can enter geometries for specific, two-dimensional cross sections of an airfoil or other airframe surface and then apply a range of inputs - different droplet sizes, temperatures, airspeeds, and more - to model how ice would build up on the surface in various conditions. The program s versatility, ease of use, and speed - LEWICE can run through complex icing simulations in only a few minutes - have contributed to it becoming a popular resource in the aviation industry.

Source record↗

NASA NTRS2011

NASA Air Force Cost Model (NAFCOM): Capabilities and Results

NAFCOM is a parametric estimating tool for space hardware. Uses cost estimating relationships (CERs) which correlate historical costs to mission characteristics to predict new project costs. It is based on historical NASA and Air Force space projects. It is intended to be used in the very early phases of a development project. NAFCOM can be used at the subsystem or component levels and estimates development and production costs. NAFCOM is applicable to various types of missions (crewed spacecraft, uncrewed spacecraft, and launch vehicles). There are two versions of the model: a government version that is restricted and a contractor releasable version.

McAfee, Julie↗

NASA NTRS2011

Shuttle Propulsion System Major Events and the Final 22 Flights

Numerous lessons have been documented from the Space Shuttle Propulsion elements. Major events include loss of the Solid Rocket Boosters (SRB's) on STS-4 and shutdown of a Space Shuttle Main Engine (SSME) during ascent on STS-51F. On STS-112 only half the pyrotechnics fired during release of the vehicle from the launch pad, a testament for redundancy. STS-91 exhibited freezing of a main combustion chamber pressure measurement and on STS-93 nozzle tube ruptures necessitated a low liquid level oxygen cut off of the main engines. A number of on pad aborts were experienced during the early program resulting in delays. And the two accidents, STS-51L and STS-107, had unique heritage in history from early program decisions and vehicle configuration. Following STS-51L significant resources were invested in developing fundamental physical understanding of solid rocket motor environments and material system behavior. And following STS-107, the risk of ascent debris was better characterized and controlled. Situational awareness during all mission phases improved, and the management team instituted effective risk assessment practices. The last 22 flights of the Space Shuttle, following the Columbia accident, were characterized by remarkable improvement in safety and reliability. Numerous problems were solved in addition to reduction of the ascent debris hazard. The Shuttle system, though not as operable as envisioned in the 1970's, successfully assembled the International Space Station (ISS). By the end of the program, the remarkable Space Shuttle Propulsion system achieved very high performance, was largely reusable, exhibited high reliability, and was a heavy lift earth to orbit propulsion system. During the program a number of project management and engineering processes were implemented and improved. Technical performance, schedule accountability, cost control, and risk management were effectively managed and implemented. Award fee contracting was implemented to provide performance incentives. The Certification of Flight Readiness and Mission Management processes became very effective. A key to the success of the propulsion element projects was related to relationships between the MSFC project office and support organizations with their counterpart contractor organizations. The teams worked diligently to understand and satisfy requirements and achieve mission success.

Owen, James W.↗

NASA NTRS2004

Environmental Remediation Technologies Derived from Space Industry Research

Beginning in the 1950s and 1960s, an abundance of effort and initiative was focused on propelling the space industry outward for planetary exploration and habitation. During these early years, the push to take space science to new levels indirectly contributed to the evolution of another science field that would not fully surface until the early 1980s, environmental remediation. This field is associated with the remediation or cleanup of environmental resources such as groundwater, soil, and sediment. Because the space-exploration initiative began prior to the establishment of the U.S. Environmental Protection Agency (EPA) in December of 1970, many NASA Centers as well as space-related support contractors allowed for the release of spent chemicals into the environment. Subsequently, these land owners have been directed by the EPA to responsibly initiate cleanup of their impacted sites. This paper will focus on the processes and lessons learned with the development, testing, and commercialization initiatives associated with four remediation technologies. The technologies include installation techniques for permeable reactive barriers (PRBs), the use of ultrasound to improve long-term performance of PRBs, emulsified zero-valent iron for product-level solvent degradation, and emulsion technologies for application to metal and polychlorinated biphenyl contaminated media. Details of the paper cover technology research, evaluation, and testing; contracts and grants; and technology transfer strategies including patenting, marketing, and licensing.

Quinn, Jacqueline↗

NASA NTRS2005

Software Architecture of the NASA Shuttle Ground Operations Simulator--SGOS

The SGOS executive and its subsystems have been an integral component of the Shuttle Launch Safety Program for almost thirty years. it is usable (via the LAN) by over 2000 NASA employees at the Kennedy Space Center and 11,000 contractors. SGOS supports over 800 models comprised of several hundred thousand lines of code and over 1,00 MCP procedures. Yet neither language has a for loop!! The simulation software described in this paper is used to train ground controllers and to certify launch countdown readiness.

Cook Robert P.↗

NASA NTRS2006

Requirements and Waivers

Good requirements are the first step for good communications, and good communications are central to insure an understanding between the customer and contractor. Failure to generate good requirements is unfortunately commonplace and repeated. Waivers to requirements are discussed from a risk based point of view. The assumption that every requirement will eventually be waived is used to establish a critical review of a draft safety requirement. Validation methods of requirements are addressed. Value added that safety requirements contribute to the Project is estimated to further our critical review of draft requirements.

Goodin, James Ronald↗

NASA NTRS2012

Chronology of KSC and KSC Related Events for 2011

This document is intended to serve as a record of KSC events and is a reference source for historian and other researchers. Arrangement is by day and month and individual articles are attributed to published sources. Materials were researched and compiled by the KSC Library Archivist for KSC Library Services Contractor, Abacus Technology Corporation.

Liston, Elaine E.↗

NASA NTRS2012

NASA Software Engineering Benchmarking Effort

Benchmarking was very interesting and provided a wealth of information (1) We did see potential solutions to some of our "top 10" issues (2) We have an assessment of where NASA stands with relation to other aerospace/defense groups We formed new contacts and potential collaborations (1) Several organizations sent us examples of their templates, processes (2) Many of the organizations were interested in future collaboration: sharing of training, metrics, Capability Maturity Model Integration (CMMI) appraisers, instructors, etc. We received feedback from some of our contractors/ partners (1) Desires to participate in our training; provide feedback on procedures (2) Welcomed opportunity to provide feedback on working with NASA

Godfrey, Sally↗

NASA NTRS2011

Overview of the James Webb Space Telescope Observatory

The James Webb Space Telescope (JWST) is a large aperture, space telescope designed to provide imaging and spectroscopy from 1.0 micron to 28 microns. JWST will be launched to an orbit at L2 aboard an Ariane 5 launcher in 2013. The Goddard Space Flight Center (GSFC) is the lead center for the JWST program and manages the project for NASA. The prime contractor for JWST is Northrop Grumman Aerospace Systems (NGST). JWST is an international partnership with the European Space Agency (ESA), and the Canadian Space Agency (CSA). ESA will contribute the Ariane 5 launch, and a multi-object infrared spectrograph. CSA will contribute the Fine Guidance Sensor (FGS), which includes the Tunable Filter Imager (TFI). The European consortium, in collaboration with the Jet Propulsion Laboratory (JPL), builds the mid-infrared imager (MIRI). In this paper we present an overview of the JWST science program, and discuss recent progress in the development of the observatory.

Clampin, Mark↗