Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “timeline”

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 1,027 records · Page 57
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

International Space Station Mechanisms and Maintenance Flight Control Documentation and Training Development

International Space Station (ISS) crew and flight controller training documentation is used to aid in training operations. The Generic Simulations References SharePoint (Gen Sim) site is a database used as an aid during flight simulations. The Gen Sim site is used to make individual mission segment timelines, data, and flight information easily accessible to instructors. The Waste and Hygiene Compartment (WHC) training schematic includes simple and complex fluid schematics, as well as overall hardware locations. It is used as a teaching aid during WHC lessons for both ISS crew and flight controllers. ISS flight control documentation is used to support all aspects of ISS mission operations. The Quick Look Database and Consolidated Tool Page are imagery-based references used in real-time to help the Operations Support Officer (OSO) find data faster and improve discussions with the Flight Director and Capsule Communicator (CAPCOM). A Quick Look page was created for the Permanent Multipurpose Module (PMM) by locating photos of the module interior, labeling specific hardware, and organizing them in schematic form to match the layout of the PMM interior. A Tool Page was created for the Maintenance Work Area (MWA) by gathering images, detailed drawings, safety information, procedures, certifications, demonstration videos, and general facts of each MWA component and displaying them in an easily accessible and consistent format. Participation in ISS mechanisms and maintenance lessons, mission simulation On-the-Job Training (OJT), and real-time flight OJT was used as an opportunity to train for day-to-day operations as an OSO, as well as learn how to effectively respond to failures and emergencies during mission simulations and real-time flight operations.

Daugherty, Colin C.↗
NASA NTRS2010

The Reconstruction and Failure Analysis of The Space Shuttle Columbia

This viewgraph presentation describes a very detailed reconstruction plan and failure analysis of The Space Shuttle Columbia accident. The contents include: 1) STS-107 Timeline; 2) Foam Impact; 3) Recovery; 4) Reconstruction; 5) Reconstruction Plan; 6) Reconstruction Hanger; 7) Pathfinders; 8) Aluminum Pathfinder; 9) Early Analysis - Left MLG Door Area; 10) Emphasis Switched to Left Hand Wing Leading Edge; 11) Wing Leading Edge Subsystem (LESS); 12) 3D Reconstruction of Left WLE; 13) Left Wing Tile Table; 14) LESS Observations; 15) Left Hand Wing Debris Points to RCC 8/9 - Slumped Tile; 16) Reconstructed View of LC/P 9 tile with I/B Tile; 17) Reconstructed View of Lower C/P 9 Tile; 18) Carrier Panel 8 - Upper; 19) Left Hand Wing Debris Points to RCC 8/9 - Erosion and RCC with attach hole intact; 20) Erosion on Panel 8 Upper Outboard Rib; 21) RCC Panels 8 & 9 Erosion Features; 22) Slumping Source for Carrier Panel 9 Tile was Revealed; 23) Debris Indicated Highest Probability Initiation Site; 24) Left Hand Wing Debris Points to RCC 8/9- Metallic Deposits; 25) Relative Metallic Deposition on L/H Wing Materials; 26) Metallic Deposit Example, LH RCC 8; 27) High Level Questions; 28) Analysis Plan Challenges; 29) Analysis Techniques; 30) Analysis Approach; 31) RCC Panel 8 Erosion Features; 32) Radiographic Features; 33) Radiography WLE LH Panel 8; 34) LH RCC 8 Upper Apex; 35) LH RCC 8 - Deposit Feature: Thick Tear Shaped; 36) LH RCC 8 - Deposit Feature: Thick Globules; 37) LH RCC 8 - Deposit Feature: Spheroids; 38) LH RCC 8 - Deposit Feature: Uniform Deposit; 39) Significant Findings - Sampling All Other panels; 40) Proposed Breach Location and Plasma Flow; 41) Corroborating Information - RCC Panel Debris Locations; 42) Corroborating Information - LH OMS Pod Analysis; 43) Corroborating Information - Impact Testing; and 44) Overall Forensic Conclusions.

Russell, Richard W.↗
NASA NTRS2004

EVA Performance Prediction

Astronaut physical performance capabilities in micro gravity EV A or on planetary surfaces when encumbered by a life support suit and debilitated by a long exposure to micro gravity will be less than unencumbered pre flight capabilities. The big question addressed by human factors engineers is: what can the astronaut be expected to do on EVA or when we arrive at a planetary surface? A second question is: what aids to performance will be needed to enhance the human physical capability? These questions are important for a number of reasons. First it is necessary to carry out accurate planning of human physical demands to ensure that time and energy critical tasks can be carried out with confidence. Second it is important that the crew members (and their ground or planetary base monitors) have a realistic picture of their own capabilities, as excessive fatigue can lead to catastrophic failure. Third it is important to design appropriate equipment to enhance human sensory capabilities, locomotion, materials handling and manipulation. The evidence from physiological research points to musculoskeletal, cardiovascular and neurovestibular degradation during long duration exposure to micro gravity . The evidence from the biomechanics laboratory (and the Neutral Buoyancy Laboratory) points to a reduction in range of motion, strength and stamina when encumbered by a pressurized suit. The evidence from a long history of EVAs is that crewmembers are indeed restricted in their physical capabilities. There is a wealth of evidence in the literature on the causes and effects of degraded human performance in the laboratory, in sports and athletics, in industry and in other physically demanding jobs. One approach to this challenge is through biomechanical and performance modeling. Such models must be based on thorough task analysis, reliable human performance data from controlled studies, and functional extrapolations validated in analog contexts. The task analyses currently carried out for EVA activities are based more on extensive domain experience than any formal analytic structure. Conversely, physical task analysis for industrial and structured evidence from training and EV A contexts. Again on earth there is considerable evidence of human performance degradation due to encumbrance and fatigue. These industrial models generally take the form of a discounting equation. The development of performance estimates for space operations, such as timeline predictions for EVA is generally based on specific input from training activity, for example in the NBL or KC135. uniformed services tasks on earth are much more formalized. Human performance data in the space context has two sources: first there is the micro analysis of performance in structured tasks by the space physiology community and second there is the less structured evidence from training and EV A contexts.

Peacock, Brian↗
NASA NTRS2011

NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better understanding of the mission assurance that MOD brings to commercial ventures to the ISS

Shull, Sarah A.↗
NASA NTRS2011

Operational Philosophy Concerning Manned Spacecraft Cabin Leaks

The last thirty years have seen the Space Shuttle as the prime United States spacecraft for manned spaceflight missions. Many lessons have been learned about spacecraft design and operation throughout these years. Over the next few decades, a large increase of manned spaceflight in the commercial sector is expected. This will result in the exposure of commercial crews and passengers to many of the same risks crews of the Space Shuttle have encountered. One of the more dire situations that can be encountered is the loss of pressure in the habitable volume of the spacecraft during on orbit operations. This is referred to as a cabin leak. This paper seeks to establish a general cabin leak response philosophy with the intent of educating future spacecraft designers and operators. After establishing a relative definition for a cabin leak, the paper covers general descriptions of detection equipment, detection methods, and general operational methods for management of a cabin leak. Subsequently, all these items are addressed from the perspective of the Space Shuttle Program, as this will be of the most value to future spacecraft due to similar operating profiles. Emphasis here is placed upon why and how these methods and philosophies have evolved to meet the Space Shuttle s needs. This includes the core ideas of: considerations of maintaining higher cabin pressures vs. lower cabin pressures, the pros and cons of a system designed to feed the leak with gas from pressurized tanks vs. using pressure suits to protect against lower cabin pressures, timeline and consumables constraints, re-entry considerations with leaks of unknown origin, and the impact the International Space Station (ISS) has had to the standard Space Shuttle cabin leak response philosophy. This last item in itself includes: procedural management differences, hardware considerations, additional capabilities due to the presence of the ISS and its resource, and ISS docking/undocking considerations with a cabin leak occurring. The paper also offers a look at how different equipment configurations on future spacecraft impact the previously defined cabin leak operational philosophy and includes additional operational methods and considerations that result due to various configurations. The intent is to showcase these various considerations and highlight the variability they allow. The paper concludes with a selection of the author s personal observations from a spacecraft operator's point of view and recommendations with the goal of improving the design and operations of future spacecraft.

DeSimpelaere, Edward↗
NASA NTRS2011

Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

Price, Jennifer B.↗
NASA NTRS2011

Reverse Launch Abort System Parachute Architecture Trade Study

This study investigated a potential Launch Abort System (LAS) Concept of Operations and abort parachute architecture. The purpose of the study was to look at the concept of jettisoning the LAS tower forward (Reverse LAS or RLAS) into the free-stream flow rather than after reorienting to a heatshield forward orientation. A hypothesized benefit was that due to the compressed timeline the dynamic pressure at main line stretch would be substantially less. This would enable the entry parachutes to be designed and sized based on entry loading conditions rather than the current stressing case of a Pad Abort. Ultimately, concerns about the highly dynamic reorientation of the CM via parachutes, and the additional requirement of a triple bridle attachment for the RLAS parachute system, overshadowed the potential benefits and ended this effort.

Litton, Daniel K.↗
NASA NTRS2011

Flight Dynamics Operations: Methods and Lessons Learned from Space Shuttle Orbit Operations

The Flight Dynamics Officer is responsible for trajectory maintenance of the Space Shuttle. This paper will cover high level operational considerations, methodology, procedures, and lessons learned involved in performing the functions of orbit and rendezvous Flight Dynamics Officer and leading the team of flight dynamics specialists during different phases of flight. The primary functions that will be address are: onboard state vector maintenance, ground ephemeris maintenance, calculation of ground and spacecraft acquisitions, collision avoidance, burn targeting for the primary mission, rendezvous, deorbit and contingencies, separation sequences, emergency deorbit preparation, mass properties coordination, payload deployment planning, coordination with the International Space Station, and coordination with worldwide trajectory customers. Each of these tasks require the Flight Dynamics Officer to have cognizance of the current trajectory state as well as the impact of future events on the trajectory plan in order to properly analyze and react to real-time changes. Additionally, considerations are made to prepare flexible alternative trajectory plans in the case timeline changes or a systems failure impact the primary plan. The evolution of the methodology, procedures, and techniques used by the Flight Dynamics Officer to perform these tasks will be discussed. Particular attention will be given to how specific Space Shuttle mission and training simulation experiences, particularly off-nominal or unexpected events such as shortened mission durations, tank failures, contingency deorbit, navigation errors, conjunctions, and unexpected payload deployments, have influenced the operational procedures and training for performing Space Shuttle flight dynamics operations over the history of the program. These lessons learned can then be extended to future vehicle trajectory operations.

Cutri-Kohart, Rebecca M.↗
NASA NTRS2010

ISS/STS Ground Status at KSC

This slide presentation reviews the status of several shuttle missions. It includes a timeline for three STS missions (i.e., OV-103, OV-104, and OV-105), and specific information about each mission, and the status of the shuttle that is to be used

Kirkpatrick, Paul↗
NASA NTRS2011

Spacecraft Conceptual Design Compared to the Apollo Lunar Lander

Future human exploration of the Moon will require an optimized spacecraft design with each sub-system achieving the required minimum capability and maintaining high reliability. The objective of this study was to trade capability with reliability and minimize mass for the lunar lander spacecraft. The NASA parametric concept for a 3-person vehicle to the lunar surface with a 30% mass margin totaled was considerably heavier than the Apollo 15 Lunar Module "as flown" mass of 16.4 metric tons. The additional mass was attributed to mission requirements and system design choices that were made to meet the realities of modern spaceflight. The parametric tool used to size the current concept, Envision, accounts for primary and secondary mass requirements. For example, adding an astronaut increases the mass requirements for suits, water, food, oxygen, as well as, the increase in volume. The environmental control sub-systems becomes heavier with the increased requirements and more structure was needed to support the additional mass. There was also an increase in propellant usage. For comparison, an "Apollo-like" vehicle was created by removing these additional requirements. Utilizing the Envision parametric mass calculation tool and a quantitative reliability estimation tool designed by Valador Inc., it was determined that with today?s current technology a Lunar Module (LM) with Apollo capability could be built with less mass and similar reliability. The reliability of this new lander was compared to Apollo Lunar Module utilizing the same methodology, adjusting for mission timeline changes as well as component differences. Interestingly, the parametric concept's overall estimated risk for loss of mission (LOM) and loss of crew (LOC) did not significantly improve when compared to Apollo.

Young, C.↗
NASA NTRS2008

Ares I Integration Approach

This slide presentation reviews the planned Integration approach for the Ares I Launch vehicle. It includes organization charts, and diagrams showing responsibilities for the various activities of the launch. Included is also a timeline with milestones for the project.

Reuter, Jim↗
NASA NTRS2010

Design and Implementation of the Boundary Layer Transition Flight Experiment on Space Shuttle Discovery

In an effort to better the understanding of high speed aerodynamics, a series of flight experiments were installed on Space Shuttle Discovery during the STS-119 and STS-128 missions. This experiment, known as the Boundary Layer Transition Flight Experiment (BLTFE), provided the technical community with actual entry flight data from a known height protuberance at Mach numbers at and above Mach 15. Any such data above Mach 15 is irreproducible in a laboratory setting. Years of effort have been invested in obtaining this valuable data, and many obstacles had to be overcome in order to ensure the success of implementing an Orbiter modification. Many Space Shuttle systems were involved in the installation of appropriate components that revealed 'concurrent engineering' was a key integration tool. This allowed the coordination of all various parts and pieces which had to be sequenced appropriately and installed at the right time. Several issues encountered include Orbiter configuration and access, design requirements versus current layout, implementing the modification versus typical processing timelines, and optimizing the engineering design cycles and changes. Open lines of communication within the entire modification team were essential to project success as the team was spread out across the United States, from NASA Kennedy Space Center in Florida, to NASA Johnson Space Center in Texas, to Boeing Huntington Beach, California among others. The forum permits the discussion of processing concerns from the design phase to the implementation phase, which eventually saw the successful flights and data acquisition on STS-119 in March 2009 and on STS-128 in September 2009.

Spanos, Theodoros A.↗
NASA NTRS2011

Modeling Constellation Virtual Missions Using the Vdot(Trademark) Process Management Tool

The authors have identified a software tool suite that will support NASA's Virtual Mission (VM) effort. This is accomplished by transforming a spreadsheet database of mission events, task inputs and outputs, timelines, and organizations into process visualization tools and a Vdot process management model that includes embedded analysis software as well as requirements and information related to data manipulation and transfer. This paper describes the progress to date, and the application of the Virtual Mission to not only Constellation but to other architectures, and the pertinence to other aerospace applications. Vdot s intuitive visual interface brings VMs to life by turning static, paper-based processes into active, electronic processes that can be deployed, executed, managed, verified, and continuously improved. A VM can be executed using a computer-based, human-in-the-loop, real-time format, under the direction and control of the NASA VM Manager. Engineers in the various disciplines will not have to be Vdot-proficient but rather can fill out on-line, Excel-type databases with the mission information discussed above. The author s tool suite converts this database into several process visualization tools for review and into Microsoft Project, which can be imported directly into Vdot. Many tools can be embedded directly into Vdot, and when the necessary data/information is received from a preceding task, the analysis can be initiated automatically. Other NASA analysis tools are too complex for this process but Vdot automatically notifies the tool user that the data has been received and analysis can begin. The VM can be simulated from end-to-end using the author s tool suite. The planned approach for the Vdot-based process simulation is to generate the process model from a database; other advantages of this semi-automated approach are the participants can be geographically remote and after refining the process models via the human-in-the-loop simulation, the system can evolve into a process management server for the actual process.

Hardy, Roger↗
NASA NTRS2010

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.

Trimble, Jay Phillip↗
NASA NTRS2010

Kepler Science Operations Center Architecture

We give an overview of the operational concepts and architecture of the Kepler Science Data Pipeline. Designed, developed, operated, and maintained by the Science Operations Center (SOC) at NASA Ames Research Center, the Kepler Science Data Pipeline is central element of the Kepler Ground Data System. The SOC charter is to analyze stellar photometric data from the Kepler spacecraft and report results to the Kepler Science Office for further analysis. We describe how this is accomplished via the Kepler Science Data Pipeline, including the hardware infrastructure, scientific algorithms, and operational procedures. The SOC consists of an office at Ames Research Center, software development and operations departments, and a data center that hosts the computers required to perform data analysis. We discuss the high-performance, parallel computing software modules of the Kepler Science Data Pipeline that perform transit photometry, pixel-level calibration, systematic error-correction, attitude determination, stellar target management, and instrument characterization. We explain how data processing environments are divided to support operational processing and test needs. We explain the operational timelines for data processing and the data constructs that flow into the Kepler Science Data Pipeline.

Middour, Christopher↗
NASA NTRS2011

A Hybrid Parachute Simulation Environment for the Orion Parachute Development Project

A parachute simulation environment (PSE) has been developed that aims to take advantage of legacy parachute simulation codes and modern object-oriented programming techniques. This hybrid simulation environment provides the parachute analyst with a natural and intuitive way to construct simulation tasks while preserving the pedigree and authority of established parachute simulations. NASA currently employs four simulation tools for developing and analyzing air-drop tests performed by the CEV Parachute Assembly System (CPAS) Project. These tools were developed at different times, in different languages, and with different capabilities in mind. As a result, each tool has a distinct interface and set of inputs and outputs. However, regardless of the simulation code that is most appropriate for the type of test, engineers typically perform similar tasks for each drop test such as prediction of loads, assessment of altitude, and sequencing of disreefs or cut-aways. An object-oriented approach to simulation configuration allows the analyst to choose models of real physical test articles (parachutes, vehicles, etc.) and sequence them to achieve the desired test conditions. Once configured, these objects are translated into traditional input lists and processed by the legacy simulation codes. This approach minimizes the number of sim inputs that the engineer must track while configuring an input file. An object oriented approach to simulation output allows a common set of post-processing functions to perform routine tasks such as plotting and timeline generation with minimal sensitivity to the simulation that generated the data. Flight test data may also be translated into the common output class to simplify test reconstruction and analysis.

Moore, James W.↗
NASA NTRS2004

Creating a Scenario Suitable for Multiple Caregivers

The HPS can be utilized for the training of a wide variety of caregivers, ranging from physicians to laypeople. Methods: A single scenario was developed and adapted for a number of clinical scenarios and operational environments, ranging from in-flight to the immediate postflight timeline. In this way, different caregivers, from astronauts to search and rescue forces to specialty-boarded physicians, could make use of a single clinical situation. Five crew medical officer analogs and sixty anesthesia residents, serving as flight surgeon analogs, and, were briefed on space medicine and physiology, then were exposed to the scenario and asked to manage the patient as if they were part of the in-flight or recovery team. Results: Basic themes, such as crisis resource management, were standard across the student audiences. Discussion: A single clinical script can easily be adapted for multiple uses.

Doerr, Harold↗
NASA NTRS2003

The NEEMO Project: A Report on how NASA Utilizes the "Aquarius" Undersea Habitat as an Analog for Long-Duration Space Flight

NEEMO is the NASA Extreme Environment Mission Operations, a cooperative project between NASA and the National Oceanic and Atmospheric Administration (NOAA). NEEMO was created and is managed by the Mission Operations Directorate at the Johnson Space Center in Houston, Texas. On the NOAA side, the National Undersea Research Center (NURC) in Key Largo, FL, with the help of the University of North Carolina at Wilmington, manages and operates the Aquarius Program. NEEMO was developed by astronaut training specialists to utilize an undersea research habitat as a multi-objective mission analog for long-duration space flight. Each mission was designed to expose astronauts to extreme environments for training purposes and to research crew behavior, habitability, and space analog life sciences. All of this was done much in the model of a space mission utilizing specific crew procedures, mission rules and timelines. Objectives of the missions were very diverse and contained many of the typical space mission type activities such as EV As (also known as extra vehicular activities), in-habitat science and research, and educational, public outreach, and media events. Five missions, dubbed NEEMO 1-5, were conducted between October 2001 and July 2003, the longest of which (NEEMO 5) lasted 14 days.

Reagan, Marc↗