Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “small projects”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Spherical Coordinate Systems for Streamlining Suited Mobility Analysis

Introduction: When describing human motion, biomechanists generally report joint angles in terms of Euler angle rotation sequences. However, there are known limitations in using this method to describe complex motions such as the shoulder joint during a baseball pitch. Euler angle notation uses a series of three rotations about an axis where each rotation is dependent upon the preceding rotation. As such, the Euler angles need to be regarded as a set to get accurate angle information. Unfortunately, it is often difficult to visualize and understand these complex motion representations. It has been shown that using a spherical coordinate system allows Anthropometry and Biomechanics Facility (ABF) personnel to increase their ability to transmit important human mobility data to engineers, in a format that is readily understandable and directly translatable to their design efforts. Objectives: The goal of this project was to use innovative analysis and visualization techniques to aid in the examination and comprehension of complex motions. Methods: This project consisted of a series of small sub‐projects, meant to validate and verify a new method before it was implemented in the ABF's data analysis practices. A mechanical test rig was built and tracked in 3D using an optical motion capture system. Its position and orientation were reported in both Euler and spherical reference systems. In the second phase of the project, the ABF estimated the error inherent in a spherical coordinate system, and evaluated how this error would vary within the reference frame. This stage also involved expanding a kinematic model of the shoulder to include the rest of the joints of the body. The third stage of the project involved creating visualization methods to assist in interpreting motion in a spherical frame. These visualization methods will be incorporated in a tool to evaluate a database of suited mobility data, which is currently in development. Results: Initial results demonstrated that a spherical coordinate system is helpful in describing and visualizing the motion of a space suit. The system is particularly useful in describing the motion of the shoulder, where multiple degrees of freedom can lead to very complex motion paths.

Benson, Elizabeth↗
NASA NTRS1981

Half-projected Hartree-Fock calculations on several small molecules

The half-projected Hartree-Fock (HPHF) method is examined with respect to its ability to obtain molecular correlation, describe molecular potential energy surfaces, and provide a one-particle basis for more elaborate treatments. The equivalence, aside from questions of efficiency, of two different HPHF algorithms is demonstrated. The results of calculations on H2O, C2, N2, and CH2 indicate that the performance of the HPHF method, with spin projection in appropriate cases, is roughly equivalent to limited MCSCF treatments. In particular, a small but important fraction of the correlation energy, qualitatively correct potential energy surfaces, and good one-particle orbital bases are obtained.

Lengsfield, B. H., III↗
NASA NTRS2005

A NASA Strategy for Leveraging Emerging Launch Vehicles for Routine, Small Payload Missions

Orbital flight opportunities for small payloads have always been few and far between, and then on February 1, 2002, the situation got worse. In the wake of the loss of the Columbia during STS- 107, changing NASA missions and priorities led to the termination of the Shuttle Small Payloads Projects, including Get-Away Special, Hitcbker, and Space Experiment Module. In spite of the limited opportunities, long queue, and restrictions associated with flying experiments on a man-rated transportation system; the carriers provided a sustained, high quality experiment services for education, science, and technology payloads, and was one of the few games in town. Attempts to establish routine opportunities aboard existing ELVs have been unsuccessful, as the cost-per-pound on small ELVs and conflicts with primary spacecraft on larger vehicles have proven prohibitive. Ths has led to a backlog of existing NASA-sponsored payloads and no prospects or plans for fbture opportunities within the NASA community. The prospects for breaking out of this paradigm appear promising as a result of NASA s partnership with DARPA in pursuit of low-cost, responsive small ELVs under the Falcon Program. Through this partnership several new small ELVs, providing 1000 lbs. to LEO will be demonstrated in less than two years that promise costs that are reasonable enough that NASA, DoD, and other sponsors can once again invest in small payload opportunities. Within NASA, planning has already begun. NASA will be populating one or more of the Falcon demonstration flights with small payloads that are already under development. To accommodate these experiments, Goddard s Wallops Flight Facility has been tasked to develop a multi-payload ejector (MPE) to accommodate the needs of these payloads. The MPE capabilities and design is described in detail in a separately submitted abstract. Beyond use of the demonstration flights however, Goddard has already begun developing strategies to leverage these new ELVs as elements of a larger system designed to provide routine, low-cost end-to-end services for small science, Exploration, and education payloads. The plan leverages the management approaches of the successful Sounding Rocket Program and Shuttle Small Payloads Projects. The strategy consists of using a systems implementation approach of elements, including 1) Falcon ELVs, 2) advanced launch site technologies and processes, 3) suite of experiment carriers accommodating different mission requirements, 4) streamlined integration and test operations, 5 ) experiment brokering and management, and 6) standardized, distributed payload operations. The envisioned suite of carriers includes the MPE, a standard interface experiment carrier, and potentially a reentry fieeflyer experiment carrier. Key to the success of this strategy is standard experiment interfaces within the carriers to limit mission- unique tasks, establishmg and managing a program of scheduled reoccurring flights rather than discrete missions, and streamlined, centralized implementation of the elements. These individual elements are each under development and Goddard will demonstrate the overall system strategy low-cost small payload missions on the initial Falcon demonstration launches from Wallops. goal is to show that this model should be converted to a sustained NASA program supporting science, technology, and education, with annual flight opportunities. The paper will define in detail the various elements of the overall program, as well as provide status, philosophy, and strategy for the program that will hopefully once-and-for-all provide low-cost, routine access to space for the small payloads community.

Underwood, Bruce E.↗
NASA NTRS2003

Integration and Test of Shuttle Small Payloads

Recommended approaches for space shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of shuttle small payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration and interface testing; (7) Postflight operations. This paper is of special interest to those payload projects that have small budgets and few resources: that is, the truly faster, cheaper, better projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.

Wright, Michael R.↗
NASA NTRS2017

Funding and Strategic Alignment Guidance for Infusing Small Business Innovation Research Technology into Aeronautics Research Mission Directorate Projects for 2016

This report is intended to help NASA program and project managers incorporate Small Business Innovation Research (SBIR) technologies into NASA Aeronautics Research Mission Directorate (ARMD) projects. Other Government and commercial project managers interested in ARMD funding opportunities through NASA's SBIR program will find this report useful as well.

Structural Efficiency; Aeroelasticity; Low Emissio↗
NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗
NASA NTRS2001

Integration and Test for Small Shuttle Payloads

Recommended approaches for shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of small shuttle payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of the NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration, and interface testing; and (7) Postflight operations. This paper is of special interest to those payload projects which have small budgets and few resources: That is, the truly 'faster, cheaper, better' projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.

Wright, Michael R.↗
NASA NTRS2002

Fast Reaction Experiments Enabling Science, Technology, Applications and Research (FREESTAR)

Goddard Space Flight Center (GSFC) Wallops Flight Facility (WFF) manages NASA's Shuttle Small Payloads Project (SSPP). The SSPP designs, develops, tests, integrates and flies a group of small payload carrier systems for the space shuttle. These carriers - the Hitchhiker, Getaway Specials (GAS), and Space Experiment Module (SEM) - support payloads supplied by NASA, other U.S. government agencies, universities, high schools, domestic commercial customers, and foreign nationals and governments. These carriers can support payloads that range in size between 50 lbs. (23 kg) and 4,000 lbs. (2,270 kg).

Source record↗
NASA NTRS2010

Developing Collective Training for Small Unmanned Aerial Systems Employment

The projected use of small unmanned aerial systems (SUAS) in military operations will produce training requirements which go beyond current capabilities. The paper describes the development of prototype training procedures and accompanying research simulations to address this need. We initially constructed a testbed to develop simulation-based training for an SUAS operator equipped with a simulated vertical-lift and land SUAS. However, the required training will go beyond merely training an operator how to pilot an SUAS. In addition to tactics, techniques, and procedures for employment of SUASs, collective training methods must be trained. Moreover, the leader of a unit equipped with SUAS will need to learn how to plan missions which incorporate the SUAS, and take into account air space and frequency management considerations. The demands of the task require the leader to allocate personnel to the SUAS mission, communicate and coordinate with those personnel during the mission, and make use of the information provided. To help address these training issues, we expanded our research testbed to include a command and control node (C2 node), to enable communications between a leader and the SUAS operator. In addition, we added a virtual environment in which dismounted infantry missions can be conducted. This virtual environment provides the opportunity for interactions among human-controlled avatars and non-player characters (NPCs), plus authoring tools to construct scenarios. Using these NPCs, a collective exercise involving friendly, enemy, and civilian personnel can be conducted without the need for a human role-player for every entity. We will describe the results of our first experiment, which examined the ability of players to negotiate use of the C2 node and the virtual environment at the same time, in order to see if this is a feasible combination of tools for training development.

Durlach, Paula J.↗
NASA NTRS1995

Space Experiment Module: A new low-cost capability for education payloads

The Space Experiment Module (SEM) concept is one of a number of education initiatives being pursued by the NASA Shuttle Small Payloads Project (SSPP) in an effort to increase educational access to space by means of Space Shuttle Small Payloads and associated activities. In the SEM concept, NASA will provide small containers ('modules') which can accommodate small zero-gravity experiments designed and constructed by students. A number, (nominally ten), of the modules will then be flown in an existing Get Away Special (GAS) carrier on the Shuttle for a flight of 5 to 10 days. In addition to the module container, the NASA carrier system will provide small amounts of electrical power and a computer system for controlling the operation of the experiments and recording experiment data. This paper describes the proposed SEM carrier system and program approach.

Goldsmith, Theodore C.↗
NASA NTRS1999

The Hitchhiker's Guide to I&T

With over two dozen missions since the first in 1986, the Hitchhiker project has a reputation for providing quick-reaction, low-cost flight services for Shuttle Small Payloads Project (SSPP) customers. Despite the successes, several potential improvements in customer payload integration and test (I&T) deserve consideration. This paper presents suggestions to Hitchhiker customers on how to help make the I&T process run smoother. Included are: customer requirements and interface definition, pre-integration test and evaluation, configuration management, I&T overview and planning, problem mitigation, and organizational communication. In this era of limited flight opportunities and new ISO-based requirements, issues such as these have become more important than ever.

Wright, Michael R.↗
NASA NTRS2017

Funding and Strategic Alignment Guidance for Infusing Small Business Innovation Research Technology Into Human Exploration and Operations Mission Directorate Projects for 2016

This report is intended to help NASA program and project managers incorporate Small Business Innovation Research Small Business Technology Transfer (SBIR/STTR) technologies into NASA Human Exploration and Operations Mission Directorate (HEOMD) projects. Other Government and commercial projects managers can also find this useful. Space Transportation; Life Support and Habitation Systems; Extra-Vehicular Activity; High EfficiencySpace Power; Human Exploration and Operations Mission,

Space Transportation; Life Support and Habitation ↗
NASA NTRS2016

Funding and Strategic Alignment Guidance for Infusing Small Business Innovation Research Technology Into Aeronautics Research Mission Directorate Programs and Projects for 2015

This report is intended to help NASA program and project managers incorporate Small Business Innovation Research/Small Business Technology Transfer (SBIR)/(STTR) technologies into NASA Aeronautics Research Mission Directorate (ARMD) projects. Other Government and commercial projects managers can also find this useful.

aeronautics↗
NASA NTRS2014

Designing an Alternate Mission Operations Control Room

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a serviceoriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building. This paper presents the HPOC architecture and lessons learned during testing and the planned maiden operational commissioning. Additionally, this paper documents the necessity of an HPOC capability given the unplanned HOSC Facility power outage on April 27th, 2011, as a result of the tornado outbreak that damaged the electrical grid to such a degree that significantly inhibited the Tennessee Valley Authority's ability to transmit electricity throughout the North Alabama region.

Montgomery, Patty↗
NASA NTRS2014

Designing an Alternate Mission Operations Control Room

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a service-oriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building.

Montgomery, Patty↗
NASA NTRS2010

We're Here to Help You

Air Force lore tells us that the two biggest lies you will ever hear on the tarmac are when the Inspector General steps off the plane and says to the Wing Commander, "We're here to help you," and the Wing Commander replies, "We're glad to see you." Not too surprisingly, a similar relationship is often perceived between a project manager and the mission assurance representative (especially for operations). This perception intensifies as budgets shrink and missions shorten, after all, where is the value added? That is the question we will examine for three small, short projects: Phoenix, WISE, and Grail (which is yet to launch). All have limited resources to devote to "niceties" and a very short mission to reap the benefits for their operations. We will examine how mission operations assurance evolved for each project, what worked well, what could have been improved, and how these lessons can be applied to ensure mission operations assurance is a value added function for Grail and future small missions.

Topex↗
NASA NTRSDate not supplied

Localizing Earth Science: The NASA DEVELOP Model of Community Science & Engagement

NASA’s DEVELOP Program conducts rapid feasibility studies that apply Earth observations to address community priorities and needs and enable informed decision making. Part of NASA’s Applied Sciences’ Capacity Building Program, DEVELOP builds skills in both participants (students, recent graduates, and early/transitioning career professionals) who conduct projects on small teams, and partner organizations (state and local governments, federal agencies, non-profit and for-profit organizations, and international organizations) that work closely with DEVELOP to design the project. While only a subset of DEVELOP partner organizations are local municipalities or community-led non-profits, the DEVELOP model is an effective engagement tool and often used by NASA as an introduction for communities to engage in Earth science research and familiarization with satellite remote sensing. This presentation will highlight the DEVELOP model of co-production and community collaboration, lessons learned in partnering with local communities, and evaluation activities that look at the program’s reach and efforts.

Robert Cecil Byles↗
NASA NTRS1999

Space Experiment Module (SEM)

The Space Experiment Module (SEM) Program is an education initiative sponsored by the National Aeronautics and Space Administration (NASA) Shuttle Small Payloads Project. The program provides nationwide educational access to space for Kindergarten through University level students. The SEM program focuses on the science of zero-gravity and microgravity. Within the program, NASA provides small containers or "modules" for students to fly experiments on the Space Shuttle. The experiments are created, designed, built, and implemented by students with teacher and/or mentor guidance. Student experiment modules are flown in a "carrier" which resides in the cargo bay of the Space Shuttle. The carrier supplies power to, and the means to control and collect data from each experiment.

Brodell, Charles L.↗