Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Requirements”

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,117 records · Page 62

Mars Sample Return Using Commercial Capabilities: ERV Trajectory and Capture Requirements

Mars Sample Return was presented as the highest priority planetary science mission of the next decade [1]. Lemke et al. [2] present a Mars Sample Return mission concept in which the sample is returned directly from the surface of Mars to an Earth orbit. The sample is recovered in Earth Orbit instead of being transferred between spacecraft in Mars Orbit. This paper provides the details of this sample recovery in Earth orbit and presents as such a sub-element of the overall Mars sample return concept given in [2]. We start from the assumption that a Mars Ascent Vehicle (MAV), initially landed on Mars using a modified SpaceX Dragon capsule, has successfully delivered the sample, already contained within an Earth Return Vehicle (ERV), to a parking orbit around Mars. From the parking orbit, the ERV imparts sufficient Delta-V to inject itself into an earthbound trajectory and to be captured into an Earth orbit eventually. We take into account launch window and Delta-V considerations as well as the additional constraint of increased safety margins imposed by planetary protection regulations. We focus on how to overcome two distinct challenges of the sample return that are driven by the issues of planetary protection: (1) the design of an ERV trajectory meeting all the requirements including the need to avoid contamination of Earth's atmosphere; (2) the concept of operations for retrieving the Martian samples in Earth orbit in a safe way. We present an approach to retrieve the samples through a rendezvous between the ERV and a second SpaceX Dragon capsule. The ERV executes a trajectory that brings it from low Mars orbit (LMO) to a Moon-trailing Earth orbit at high inclination with respect to the Earth-Moon plane. After a first burn at Trans-Earth Injection (TEI), the trajectory uses a second burn at perigee during an Earth flyby maneuver to capture the ERV in Earth orbit. The ERV then uses a non-propulsive Moon flyby to come to a near-circular Moon-trailing orbit. To perform the Earth Orbit Rendezvous (EOR), a second Dragon capsule is then launched from Earth and a similar lunar flyby is performed to rendezvous with the ERV. The requirements for rendezvous, close proximity operations and capture of the sample canister are described. A concept of operations for sample retrieval is presented along with design specifications of the ERV, the required modifications to the Dragon capsule, as well as the hardware, software, sensors, actuators, and capture mechanisms used. In our concept, a container is mounted to the front hatch of Dragon, capable of accommodating the sample canister and sealing it from the rest of the capsule. The sample canister is captured using a robotic arm with a magnetic grappling mechanism. Dragon then performs a propulsive maneuver to return to Earth for a controlled re-entry while the ERV (sans sample container) is left in the Moon trailing orbit. Contingency cases and related mitigation strategies are also discussed, including the advantages and disadvantages of performing the ERV rendezvous with a crew.

Faber, Nicolas F.↗

Postures and Motions Library Development for Verification of Ground Crew Human Factors Requirements

Spacecraft and launch vehicle ground processing activities require a variety of unique human activities. These activities are being documented in a primitive motion capture library. The library will be used by human factors engineering analysts to infuse real to life human activities into the CAD models to verify ground systems human factors requirements. As the primitive models are being developed for the library, the project has selected several current human factors issues to be addressed for the Space Launch System (SLS) and Orion launch systems. This paper explains how the motion capture of unique ground systems activities is being used to verify the human factors engineering requirements for ground systems used to process the SLS and Orion vehicles, and how the primitive models will be applied to future spacecraft and launch vehicle processing.

Stambolian, Damon↗

Improved Traceability of Mission Concept to Requirements Using Model Based Systems Engineering

Model Based Systems Engineering (MBSE) has recently been gaining significant support as a means to improve the traditional document-based systems engineering (DBSE) approach to engineering complex systems. In the spacecraft design domain, there are many perceived and propose benefits of an MBSE approach, but little analysis has been presented to determine the tangible benefits of such an approach (e.g. time and cost saved, increased product quality). This thesis presents direct examples of how developing a small satellite system model can improve traceability of the mission concept to its requirements. A comparison of the processes and approaches for MBSE and DBSE is made using the NASA Ames Research Center SporeSat CubeSat mission as a case study. A model of the SporeSat mission is built using the Systems Modeling Language standard and No Magics MagicDraw modeling tool. The model incorporates mission concept and requirement information from the missions original DBSE design efforts. Active dependency relationships are modeled to analyze the completeness and consistency of the requirements to the mission concept. Overall experience and methodology are presented for both the MBSE and original DBSE design efforts of SporeSat.

Systems Engineering↗

Assessment of Soil Moisture Data Requirements by the Potential SMAP Data User Community: Review of SMAP Mission User Community

NASA's Soil Moisture Active and Passive (SMAP) mission is planned for launch in October 2014 and will provide global measurements of soil moisture and freeze thaw state. The project is driven by both basic research and applied science goals. Understanding how application driven end-users will apply SMAP data, prior to the satellite's launch, is an important goal of NASA's applied science program and SMAP mission success. Because SMAP data are unique, there are no direct proxy data sets that can be used in research and operational studies to determine how the data will interact with existing processes. The objective of this study is to solicit data requirements, accuracy needs, and current understanding of the SMAP mission from the potential user community. This study showed that the data to be provided by the SMAP mission did substantially meet the user community needs. Although there was a broad distribution of requirements stated, the SMAP mission fit within these requirements.

applications↗

Improved Traceability of a Small Satellite Mission Concept to Requirements Using Model Based System Engineering

Model Based Systems Engineering (MBSE) has recently been gaining significant support as a means to improve the "traditional" document-based systems engineering (DBSE) approach to engineering complex systems. In the spacecraft design domain, there are many perceived and propose benefits of an MBSE approach, but little analysis has been presented to determine the tangible benefits of such an approach (e.g. time and cost saved, increased product quality). This paper presents direct examples of how developing a small satellite system model can improve traceability of the mission concept to its requirements. A comparison of the processes and approaches for MBSE and DBSE is made using the NASA Ames Research Center SporeSat CubeSat mission as a case study. A model of the SporeSat mission is built using the Systems Modeling Language standard and No Magic's MagicDraw modeling tool. The model incorporates mission concept and requirement information from the mission's original DBSE design efforts. Active dependency relationships are modeled to demonstrate the completeness and consistency of the requirements to the mission concept. Anecdotal information and process-duration metrics are presented for both the MBSE and original DBSE design efforts of SporeSat.

Model Based Systems Engineering↗

AMTD: Update of Engineering Specifications Derived from Science Requirements for Future UVOIR Space Telescopes

The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope

Stahl, H. Philip↗

Evolution of MPCV Service Module Propulsion and GNC Interface Requirements

The Orion Multi-Purpose Crew Vehicle Service Module Propulsion Subsystem provides propulsion for the integrated Crew and Service Module. Updates in the exploration architecture between Constellation and MPCV as well as NASA's partnership with the European Space Agency have resulted in design changes to the SM Propulsion Subsystem and updates to the Propulsion interface requirements with Guidance Navigation and Control. This paper focuses on the Propulsion and GNC interface requirement updates between the Constellation Service Module and the European Service Module and how the requirement updates were driven or supported by architecture updates and the desired use of hardware with heritage to United States and European spacecraft for the Exploration Missions, EM-1 and EM-2.

spacecraft propulsion↗

Functional Foods Baseline and Requirements Analysis

Current spaceflight foods were evaluated to determine if their nutrient profile supports positioning as a functional food and if the stability of the bioactive compound within the food matrix over an extended shelf-life correlated with the expected storage duration during the mission. Specifically, the research aims were: Aim A. To determine the amount of each nutrient in representative spaceflight foods immediately after processing and at predetermined storage time to establish the current nutritional state. Aim B. To identify the requirements to develop foods that stabilize these nutrients such that required concentrations are maintained in the space food system throughout long duration missions (up to five years). Aim C. To coordinate collaborations with health and performance groups that may require functional foods as a countermeasure.

Cooper, M. R.↗

Developing the Cleanliness Requirements for an Organic-detection Instrument MOMA-MS

The cleanliness requirements for an organic-detection instrument, like the Mars Organic Molecule Analyzer Mass Spectrometer (MOMA-MS), on a Planetary Protection Class IVb mission can be extremely stringent. These include surface molecular and particulate, outgassing, and bioburden. The prime contractor for the European Space Agencys ExoMars 2018 project, Thales Alenia Space Italy, provided requirements based on a standard, conservative approach of defining limits which yielded levels that are unverifiable by standard cleanliness verification methods. Additionally, the conservative method for determining contamination surface area uses underestimation while conservative bioburden surface area relies on overestimation, which results in inconsistencies for the normalized reporting. This presentation will provide a survey of the challenge to define requirements that can be reasonably verified and still remain appropriate to the core science of the ExoMars mission.

Planetary Protection↗

Deriving Earth Science Data Analytics Requirements

Data Analytics applications have made successful strides in the business world where co-analyzing extremely large sets of independent variables have proven profitable. Today, most data analytics tools and techniques, sometimes applicable to Earth science, have targeted the business industry. In fact, the literature is nearly absent of discussion about Earth science data analytics. Earth science data analytics (ESDA) is the process of examining large amounts of data from a variety of sources to uncover hidden patterns, unknown correlations, and other useful information. ESDA is most often applied to data preparation, data reduction, and data analysis. Co-analysis of increasing number and volume of Earth science data has become more prevalent ushered by the plethora of Earth science data sources generated by US programs, international programs, field experiments, ground stations, and citizen scientists.Through work associated with the Earth Science Information Partners (ESIP) Federation, ESDA types have been defined in terms of data analytics end goals. Goals of which are very different than those in business, requiring different tools and techniques. A sampling of use cases have been collected and analyzed in terms of data analytics end goal types, volume, specialized processing, and other attributes. The goal of collecting these use cases is to be able to better understand and specify requirements for data analytics tools and techniques yet to be implemented. This presentation will describe the attributes and preliminary findings of ESDA use cases, as well as provide early analysis of data analytics toolstechniques requirements that would support specific ESDA type goals. Representative existing data analytics toolstechniques relevant to ESDA will also be addressed.

data analytics↗

Mesh Convergence Requirements for Composite Damage Models

The ability of the finite element method to accurately represent the response of objects with intricate geometry and loading renders the finite element method as an extremely versatile analysis technique for structural analysis. Finite element analysis is routinely used in industry to calculate deflections, stress concentrations, natural frequencies, buckling loads, and much more. The method works by discretizing complex problems into smaller, simpler approximations that are valid over small uniform domains. For common analyses, the maximum size of the elements that can be used is often be determined by experience. However, to verify the quality of a solution, analyses with several levels of mesh refinement should be performed to ensure that the solution has converged. In recent years, the finite element method has been used to calculate the resistance of structures, and in particular that of composite structures. A number of techniques such as cohesive zone modeling, the virtual crack closure technique, and continuum damage modeling have emerged that can be used to predict cracking, delaminations, fiber failure, and other composite damage modes that lead to structural collapse. However, damage models present mesh refinement requirements that are not well understood. In this presentation, we examine different mesh refinement issues related to the representation of damage in composite materials. Damage process zone sizes and their corresponding mesh requirements will be discussed. The difficulties of modeling discontinuities and the associated need for regularization techniques will be illustrated, and some unexpected element size constraints will be presented. Finally, some of the difficulties in constructing models of composite structures capable of predicting transverse matrix cracking will be discussed. It will be shown that to predict the initiation and propagation of transverse matrix cracks, their density, and their saturation may require models that are significantly more refined than those that have been contemplated in the past.

Davila, Carlos G.↗

Mobile/Modular BSL-4 Facilities for Meeting Restricted Earth Return Containment Requirements

NASA robotic sample return missions designated Category V Restricted Earth Return by the NASA Planetary Protection Office require sample containment and biohazard testing in a receiving laboratory as directed by NASA Procedural Requirement (NPR) 8020.12D - ensuring the preservation and protection of Earth and the sample. Currently, NPR 8020.12D classifies Restricted Earth Return for robotic sample return missions from Mars, Europa, and Enceladus with the caveat that future proposed mission locations could be added or restrictions lifted on a case by case basis as scientific knowledge and understanding of biohazards progresses. Since the 1960s, sample containment from an unknown extraterrestrial biohazard have been related to the highest containment standards and protocols known to modern science. Today, Biosafety Level (BSL) 4 standards and protocols are used to study the most dangerous high-risk diseases and unknown biological agents on Earth. Over 30 BSL-4 facilities have been constructed worldwide with 12 residing in the United States; of theses, 8 are operational. In the last two decades, these brick and mortar facilities have cost in the hundreds of millions of dollars dependent on the facility requirements and size. Previous mission concept studies for constructing a NASA sample receiving facility with an integrated BSL-4 quarantine and biohazard testing facility have also been estimated in the hundreds of millions of dollars. As an alternative option, we have recently conducted an initial trade study for constructing a mobile and/or modular sample containment laboratory that would meet all BSL-4 and planetary protection standards and protocols at a faction of the cost. Mobile and modular BSL-2 and 3 facilities have been successfully constructed and deployed world-wide for government testing of pathogens and pharmaceutical production. Our study showed that a modular BSL-4 construction could result in approximately 90% cost reduction when compared to traditional construction methods without compromising the preservation of the sample or Earth.

Calaway, M. J.↗

Managing Requirements-Documents to Data

Managing Requirements on long term projects like International Space Station (ISS) can go thru many phases, from initial product development to almost over 20 years of operations and sustainment. Over that time many authorized changes have been made to the requirement set, that apply to any new systems that would visit the ISS today, like commercial cargo/crew vehicles or payloads. Explore the benefits of managing requirements in a database while satisfying traditional documents needs for contracts and stakeholder/user consumption that are not tied into the database.

Orr, Kevin↗

UTM TCL2 Software Requirements

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level (TCL) 2 software implements the UTM TCL 2 software requirements described herein. These software requirements are linked to the higher level UTM TCL 2 System Requirements. Each successive TCL implements additional UTM functionality, enabling additional use cases. TCL 2 demonstrated how to enable expanded multiple operations by implementing automation for beyond visual line-of-sight, tracking operations, and operations flying over sparsely populated areas.

Smith, Irene S.↗

Design and Requirements Creep In A Build-To-Print Mission

Build-to-Print designs, or rebuilds of flight proven designs, are attractive to mission stakeholders, as they give the appearance of minimal engineering development cost, risk, and schedule. The reality is that seldom is a project an exact duplicate of a predecessor. Mission reclassification, improvements in hardware, and science objective changes can all serve as a source of requirements and design creep and have ramifications often not fully anticipated during initial proposals. The Thermal Infrared Sensor Instrument (TIRS) was a late addition to the LandSat-8 program to provide infrared imaging to measure evapotranspiration for water cycle management. To meet the launch requirements for LandSat-8, instrument design life requirements were relaxed, the sensor development expedited, and technology development was minimized. Consequently, TIRS was designed as a higher risk instrument, with less redundancy than an instrument critical to mission success. After the successful LandSat-8 launch in 2013 and instrument performance, a rebuild of the instrument for the next LandSat spacecraft was included in the baseline mission success criteria. This paper discusses the technical challenges encountered during the rebuild of the TIRS-2 (Thermal Infrared Sensor 2) instrument and the resultant impacts on the thermal system design.

TIRS-2 Thermal Design↗

Requirements and Design Reference Mission for the WFIRST-AFTA Coronagraph Instrument

The WFIRST-AFTA coronagraph instrument take s advantage of AFTA s 2.4 -meter aperture to provide novel exoplanet imaging science at approximately the same instrument cost as an Explorer mission. The AFTA coronagraph also matures direct imaging technologies to high TRL for an Exo-Earth Imager in the next decade. The coronagraph Design Reference Mission (DRM) optical design is based on the highly successful High Contrast Imaging Testbed (HCIT), with modifications to accommodate the AFTA telescope design, service-ability, volume constraints, and the addition of an Integral Field Spectrograph (IFS). In order to optimally satisfy the three science objectives of planet imaging, planet spectral characterization and dust debris imaging, the coronagraph is designed to operate in two different modes : Hybrid Lyot Coronagraph or Shaped Pupil Coronagraph. Active mechanisms change pupil masks, focal plane masks, yot masks, and bandpass filters to shift between modes. A single optical beam train can thus operate alternatively as two different coronagraph architecture s. Structural Thermal Optical Performance (STOP) analysis predict s the instrument contrast with the Low Order Wave Front Control loop closed. The STOP analysis was also used to verify that the optical/structural/thermal design provides the extreme stability required for planet characterization in the presence of thermal disturbances expected in a typical observing scenario. This paper describes the instrument design and the flow down from science requirements to high level engineering requirements.

contrast↗

NASA Requirements for Ground-Based Pressure Vessels and Pressurized Systems (PVS)

The purpose of this document is to ensure the structural integrity of PVS through implementation of a minimum set of requirements for ground-based PVS in accordance with this document, NASA Policy Directive (NPD) 8710.5, NASA Safety Policy for Pressure Vessels and Pressurized Systems, NASA Procedural Requirements (NPR) 8715.3, NASA General Safety Program Requirements, applicable Federal Regulations, and national consensus codes and standards (NCS).

Greulich, Owen Rudolf↗

Crewed Space Vehicle Battery Safety Requirements Revision D

The Crewed Space Vehicle Battery Safety Requirements document has been prepared for use by designers of battery-powered vehicles, portable equipment, and experiments intended for crewed spaceflight. The purpose of the requirements document is to provide battery designers with information on design provisions to be incorporated in and around the battery and on the verification to be undertaken to demonstrate a safe battery is provided. The term "safe battery" means that the battery is safe for ground personnel and crew members to handle and use; safe to be used in the enclosed environment of a crewed space vehicle; and safe to be mounted or used in unpressurized spaces adjacent to habitable areas. Battery design review, approval, and certification is required before the batteries can be used for ground operations and be certified for flight.

Russell, Samuel↗