Search NASA⌕ Search

SEARCH · Search NASA

Results for “spreadsheet”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

NASA Tech Briefs, March 2009

Topics covered include: Improved Instrument for Detecting Water and Ice in Soil; Real-Time Detection of Dust Devils from Pressure Readings; Determining Surface Roughness in Urban Areas Using Lidar Data; DSN Data Visualization Suite; Hamming and Accumulator Codes Concatenated with MPSK or QAM; Wide-Angle-Scanning Reflectarray Antennas Actuated by MEMS; Biasable Subharmonic Membrane Mixer for 520 to 600 GHz; Hardware Implementation of Serially Concatenated PPM Decoder; Symbolic Processing Combined with Model-Based Reasoning; Presentation Extensions of the SOAP; Spreadsheets for Analyzing and Optimizing Space Missions; Processing Ocean Images to Detect Large Drift Nets; Alternative Packaging for Back-Illuminated Imagers; Diamond Machining of an Off-Axis Biconic Aspherical Mirror; Laser Ablation Increases PEM/Catalyst Interfacial Area; Damage Detection and Self-Repair in Inflatable/Deployable Structures; Polyimide/Glass Composite High-Temperature Insulation; Nanocomposite Strain Gauges Having Small TCRs; Quick-Connect Windowed Non-Stick Penetrator Tips for Rapid Sampling; Modeling Unsteady Cavitation and Dynamic Loads in Turbopumps; Continuous-Flow System Produces Medical-Grade Water; Discrimination of Spore-Forming Bacilli Using spoIVA; nBn Infrared Detector Containing Graded Absorption Layer; Atomic References for Measuring Small Accelerations; Ultra-Broad-Band Optical Parametric Amplifier or Oscillator; Particle-Image Velocimeter Having Large Depth of Field; Enhancing SERS by Means of Supramolecular Charge Transfer; Improving 3D Wavelet-Based Compression of Hyperspectral Images; Improved Signal Chains for Readout of CMOS Imagers; SOI CMOS Imager with Suppression of Cross-Talk; Error-Rate Bounds for Coded PPM on a Poisson Channel; Biomorphic Multi-Agent Architecture for Persistent Computing; and Using Covariance Analysis to Assess Pointing Performance.

Source record↗
NASA NTRS2009

Group Capability Model

The Group Capability Model (GCM) is a software tool that allows an organization, from first line management to senior executive, to monitor and track the health (capability) of various groups in performing their contractual obligations. GCM calculates a Group Capability Index (GCI) by comparing actual head counts, certifications, and/or skills within a group. The model can also be used to simulate the effects of employee usage, training, and attrition on the GCI. A universal tool and common method was required due to the high risk of losing skills necessary to complete the Space Shuttle Program and meet the needs of the Constellation Program. During this transition from one space vehicle to another, the uncertainty among the critical skilled workforce is high and attrition has the potential to be unmanageable. GCM allows managers to establish requirements for their group in the form of head counts, certification requirements, or skills requirements. GCM then calculates a Group Capability Index (GCI), where a score of 1 indicates that the group is at the appropriate level; anything less than 1 indicates a potential for improvement. This shows the health of a group, both currently and over time. GCM accepts as input head count, certification needs, critical needs, competency needs, and competency critical needs. In addition, team members are categorized by years of experience, percentage of contribution, ex-members and their skills, availability, function, and in-work requirements. Outputs are several reports, including actual vs. required head count, actual vs. required certificates, CGI change over time (by month), and more. The program stores historical data for summary and historical reporting, which is done via an Excel spreadsheet that is color-coded to show health statistics at a glance. GCM has provided the Shuttle Ground Processing team with a quantifiable, repeatable approach to assessing and managing the skills in their organization. They now have a common frame of reference across NASA/contractor lines to communicate and mitigate any critical skills concerns.

Olejarski, Michael↗
NASA NTRS2007

Automated Design of Restraint Layer of an Inflatable Vessel

A Mathcad computer program largely automates the design and analysis of the restraint layer (the primary load-bearing layer) of an inflatable vessel that consists of one or more sections having cylindrical, toroidal, and/or spherical shape(s). A restraint layer typically comprises webbing in the form of multiple straps. The design task includes choosing indexing locations along the straps, computing the load at every location in each strap, computing the resulting stretch at each location, and computing the amount of undersizing required of each strap so that, once the vessel is inflated and the straps thus stretched, the vessel can be expected to assume the desired shape. Prior to the development of this program, the design task was performed by use of a difficult-to-use spreadsheet program that required manual addition of rows and columns depending on the numbers of strap rows and columns of a given design. In contrast, this program is completely parametric and includes logic that automatically adds or deletes rows and columns as needed. With minimal input from the user, this program automatically computes indexing locations, strap lengths, undersizing requirements, and all design data required to produce detailed drawings and assembly procedures. It also generates textual comments that help the user understand the calculations.

Spexarth, Gary↗
NASA NTRS2009

TASS Model Application for Testing the TDWAP Model

One of the operational modes of the Terminal Area Simulation System (TASS) model simulates the three-dimensional interaction of wake vortices within turbulent domains in the presence of thermal stratification. The model allows the investigation of turbulence and stratification on vortex transport and decay. The model simulations for this work all assumed fully-periodic boundary conditions to remove the effects from any surface interaction. During the Base Period of this contract, NWRA completed generation of these datasets but only presented analysis for the neutral stratification runs of that set (Task 3.4.1). Phase 1 work began with the analysis of the remaining stratification datasets, and in the analysis we discovered discrepancies with the vortex time to link predictions. This finding necessitated investigating the source of the anomaly, and we found a problem with the background turbulence. Using the most up to date version TASS with some important defect fixes, we regenerated a larger turbulence domain, and verified the vortex time to link with a few cases before proceeding to regenerate the entire 25 case set (Task 3.4.2). The effort of Phase 2 (Task 3.4.3) concentrated on analysis of several scenarios investigating the effects of closely spaced aircraft. The objective was to quantify the minimum aircraft separations necessary to avoid vortex interactions between neighboring aircraft. The results consist of spreadsheets of wake data and presentation figures prepared for NASA technical exchanges. For these formation cases, NASA carried out the actual TASS simulations and NWRA performed the analysis of the results by making animations, line plots, and other presentation figures. This report contains the description of the work performed during this final phase of the contract, the analysis procedures adopted, and sample plots of the results from the analysis performed.

Switzer, George F.↗
NASA NTRS2007

ISPATOM: A Generic Real-Time Data Processing Tool Without Programming

Information Sharing Protocol Advanced Tool of Math (ISPATOM) is an application program allowing for the streamlined generation of comps, which subscribe to streams of incoming telemetry data, perform any necessary computations on the data, then send the data to other programs for display and/or further processing in NASA mission control centers. Heretofore, the development of comps was difficult, expensive, and time-consuming: Each comp was custom written manually, in a low-level computing language, by a programmer attempting to follow requirements of flight controllers. ISPATOM enables a flight controller who is not a programmer to write a comp by simply typing in one or more equation( s) at a command line or retrieving the equation(s) from a text file. ISPATOM then subscribes to the necessary input data, performs all of necessary computations, and sends out the results. It sends out new results whenever the input data change. The use of equations in ISPATOM is no more difficult than is entering equations in a spreadsheet. The time involved in developing a comp is thus limited to the time taken to decide on the necessary equations. Thus, ISPATOM is a real-time dynamic calculator.

Dershowitz, Adam↗
NASA NTRS2010

Trajectory Optimization: OTIS 4

The latest release of the Optimal Trajectories by Implicit Simulation (OTIS4) allows users to simulate and optimize aerospace vehicle trajectories. With OTIS4, one can seamlessly generate optimal trajectories and parametric vehicle designs simultaneously. New features also allow OTIS4 to solve non-aerospace continuous time optimal control problems. The inputs and outputs of OTIS4 have been updated extensively from previous versions. Inputs now make use of objectoriented constructs, including one called a metastring. Metastrings use a greatly improved calculator and common nomenclature to reduce the user s workload. They allow for more flexibility in specifying vehicle physical models, boundary conditions, and path constraints. The OTIS4 calculator supports common mathematical functions, Boolean operations, and conditional statements. This allows users to define their own variables for use as outputs, constraints, or objective functions. The user-defined outputs can directly interface with other programs, such as spreadsheets, plotting packages, and visualization programs. Internally, OTIS4 has more explicit and implicit integration procedures, including high-order collocation methods, the pseudo-spectral method, and several variations of multiple shooting. Users may switch easily between the various methods. Several unique numerical techniques such as automated variable scaling and implicit integration grid refinement, support the integration methods. OTIS4 is also significantly more user friendly than previous versions. The installation process is nearly identical on various platforms, including Microsoft Windows, Apple OS X, and Linux operating systems. Cross-platform scripts also help make the execution of OTIS and post-processing of data easier. OTIS4 is supplied free by NASA and is subject to ITAR (International Traffic in Arms Regulations) restrictions. Users must have a Fortran compiler, and a Python interpreter is highly recommended.

Riehl, John P.↗
NASA NTRS2010

Developing a Logistics Data Process for Support Equipment for NASA Ground Operations

The United States NASA Space Shuttle has long been considered an extremely capable yet relatively expensive rocket. A great part of the roughly US $500 million per launch expense was the support footprint: refurbishment and maintenance of the space shuttle system, together with the long list of resources required to support it, including personnel, tools, facilities, transport and support equipment. NASA determined to make its next rocket system with a smaller logistics footprint, and thereby more cost-effective and quicker turnaround. The logical solution was to adopt a standard Logistics Support Analysis (LSA) process based on GEIA-STD-0007 http://www.logisticsengineers.org/may09pres/GEIASTD0007DEXShortIntro.pdf which is the successor of MIL-STD-1388-2B widely used by U.S., NATO, and other world military services and industries. This approach is unprecedented at NASA: it is the first time a major program of programs, Project Constellation, is factoring logistics and supportability into design at many levels. This paper will focus on one of those levels NASA ground support equipment for the next generation of NASA rockets and on building a Logistics Support Analysis Record (LSAR) for developing and documenting a support solution and inventory of resources for. This LSAR is actually a standards-based database, containing analyses of the time and tools, personnel, facilities and support equipment required to assemble and integrate the stages and umbilicals of a rocket. This paper will cover building this database from scratch: including creating and importing a hierarchical bill of materials (BOM) from legacy data; identifying line-replaceable units (LRUs) of a given piece of equipment; analyzing reliability and maintainability of said LRUs; and therefore making an assessment back to design whether the support solution for a piece of equipment is too much work, i.e., too resource-intensive. If one must replace or inspect an LRU too much, perhaps a modification of the design of the equipment can make such operational effort unnecessary. Finally, this paper addresses processes of tying resources to a timeline of tasks performed in ground operations: this enables various overarching analyses, e.g., a summarization of all resources used for a given piece of equipment. Quality Control of data will also be discussed: importing and exporting data from product teams, including spreadsheets-todatabase or data exchange between databases.

Chakrabarti, Suman↗
NASA NTRS2010

Toward Right-Fidelity Rotorcraft Conceptual Design

The aviation Advanced Design Office (ADO) of the US Army Aeroflightdynamics Directorate (AMRDEC) performs conceptual design of advanced Vertical Takeoff and Landing (VTOL) concepts in support of the Army's development and acquisition of new aviation systems. In particular, ADO engages in system synthesis to assess the impact of new technologies and their application to satisfy emerging warfighter needs and requirements. Fundamental to ADO being successful in accomplishing its role; is the ability to evaluate a wide array of proposed air vehicle concepts, and independently synthesize new concepts to inform Army and DoD decision makers about the tradespace in which decisions will be made (Figure 1). ADO utilizes a conceptual design (CD) process in the execution of its role. Benefiting from colocation with NASA rotorcraft researchers at the Ames Research Center, ADO and NASA have engaged in a survey of the current rotorcraft PD practices and begun the process of improving those capabilities to enable effective design and development of the next generation of VTOL systems. A unique aspect of CD in ADO is the fact that actual designs developed in-house are not intended to move forward in the development process. Rather, they are used as reference points in discussions about requirements development and technology impact. The ultimate products of ADO CD efforts are technology impact assessments and specifications which guide industry design activity. The fact that both the requirement and design are variables in the tradespace adds to the complexity of the CD process. A frequent need is ability to assess the relative "cost" of variations in requirement for a diverse set of VTOL configurations. Each of these configurations may have fundamentally different response characteristics to this requirement variation, and such insight into how different requirements drive different designs is a critical insight ADO attempts to provide decision makers. The processes and tools utilized are driven by the timeline in which questions must be answered. This can range from quick "back-of-the-envelope" assessments of a configuration made in an afternoon, to more detailed tradespace explorations that can take upwards of a year to complete. A variety of spreadsheet based tools and conceptual design codes are currently in use. The in-house developed conceptual sizing code RC (Rotorcraft) has been the preferred tool of choice for CD activity for a number of years. Figure 2 illustrates the long standing coupling between RC and solid modeling tools for layout, as well as a number of ad-hoc interfaces with external analyses. RC contains a sizing routine that is built around the use of momentum theory for rotors, classic finite wing theory, a referred parameter engine model, and semi-emperical weight estimation techniques. These methods lend themselves to rapid solutions, measured in seconds and minutes. The successful use of RC, however requires careful consideration of model input parameters and judicious comparison with existing aircraft to avoid unjustified extrapolation of results. RC is in fact a legacy of a series of codes whose development started in the early 1970s, and is best suited to the study of conventional helicopters and XV-15 style tiltrotors. Other concepts have been analyzed with RC, but typically it became necessary to modify the source code and methods for each unique configuration. Recent activity has lead to the development of a new code, NASA Design and Analysis of Rotorcraft (NDARC). NDARC uses a similar level of analytical fidelity as RC, but is built on a new framework intended to improve modularity and ability to rapidly model a wider array of concepts. Critical to achieving this capability is the decomposition of the aircraft system into a series of fundamental components which can then be assembled to form a wide-array of configurations. The paper will provide an overview of NDARC and its capabilities.

Sinsay, Jeffrey D.↗
NASA NTRS2010

Risk Presentation Using the Three Dimensions of Likelihood, Severity, and Level of Control

Traditional hazard analysis techniques utilize a two-dimensional representation of the results determined by relative likelihood and severity of the residual risk. These matrices present a quick-look at the Likelihood (Y-axis) and Severity (X-axis) of the probable outcome of a hazardous event. A three-dimensional method, described herein, utilizes the traditional X and Y axes, while adding a new, third dimension, shown as the Z-axis, and referred to as the Level of Control. The elements of the Z-axis are modifications of the Hazard Elimination and Control steps (also known as the Hazard Reduction Precedence Sequence). These steps are: 1. Eliminate risk through design. 2. Substitute less risky materials for more hazardous materials. 3. Install safety devices. 4. Install caution and warning devices. 5. Develop administrative controls (to include special procedures and training.) 6. Provide protective clothing and equipment. When added to the two-dimensional models, the level of control adds a visual representation of the risk associated with the hazardous condition, creating a tall-pole for the leastwell-controlled failure while establishing the relative likelihood and severity of all causes and effects for an identified hazard. Computer modeling of the analytical results, using spreadsheets and three-dimensional charting gives a visual confirmation of the relationship between causes and their controls.

Watson, Clifford↗
NASA NTRS2010

Converting a C-130 Hercules into a Compound Helicopter: A Conceptual Design Study

This study presents the performance and weight changes for a Compound C-130 as compared to the Baseline C-130H Hercules, using NDARC as the primary analysis tool. First, the C-130H was modeled within NDARC, from which performance at various conditions and a parametric weight statement were generated. Then, the C-130H NDARC file was modified to represent the Compound C-130, which was then put through the same performance analysis as the C-130H. A parametric weight statement was also calculated for the Compound C-130, which allowed for comparison to the C-130H. As part of the modeling of the Compound C-130, a Rotor Design Spreadsheet was created that would allow the direct calculation of the weight of the main rotors being added. Using composite materials led to considerable weight savings for both the rotor system and the hub weights. These weight savings are reflected in the NDARC Technology Factors which were determined to be 0.71 and 0.5 for the rotor blades and the hub/hinge system, respectively. Such Technology Factors suggest that using composites for other components could drastically lighten the Operating Empty Weight of the aircraft. The weight statements show the weights for each of the components on each aircraft. It is quite evident that the Compound C-130 has a higher Operating Empty Weight due to the addition of the two main rotors and a drive system to connect each engine group on the wing tips. Upon further analysis, the main weight driver is the drive system. While the main rotor/hub/hinge weight increase is to be expected, the weight increase due to the transmission drive and gear boxes are cause for concern. Unless a method can be found of reducing the weight of the drive system, the weight penalty makes the Compound a C-130 an inefficient aircraft in terms of payload/fuel capacity. Possible solutions are either off-loading some of the power requirements through the drive system or using composite materials in the construction of the drive system. The performance of the Compound C-130 versus the C-130H shows a clear need for more powerful engines than are currently present on the C-130H. This would also adversely affect the Operating Empty Weight since a larger power plant requires more weight. However, one advantage that the Compound C-130 presents is the ability to hover and operate at low speeds in Helicopter Mode. While the C-130H is unable to travel at speeds lower than its stall speed, the Compound C-130 is able to hover using the main rotors. Thus, the Compound C-130 is able to operate independent of runways, let alone the condition of the nearest runway. Ultimately, the Compound C-130 is an effective aircraft in theaters requiring VTOL aircraft due to geographical considerations in terms or performance. Unfortunately, the weight penalty associated with converting the C-130H to a Compound C-130 suggests that further work in the area of the drive systems is required.

Kottapalli, Anjaney P.↗
NASA NTRS2010

Risk Assessment Using the Three Dimensions of Probability (Likelihood), Severity, and Level of Control

Traditional hazard analysis techniques utilize a two-dimensional representation of the results determined by relative likelihood and severity of the residual risk. These matrices present a quick-look at the Likelihood (Y-axis) and Severity (X-axis) of the probable outcome of a hazardous event. A three-dimensional method, described herein, utilizes the traditional X and Y axes, while adding a new, third dimension, shown as the Z-axis, and referred to as the Level of Control. The elements of the Z-axis are modifications of the Hazard Elimination and Control steps (also known as the Hazard Reduction Precedence Sequence). These steps are: 1. Eliminate risk through design. 2. Substitute less risky materials for more hazardous materials. 3. Install safety devices. 4. Install caution and warning devices. 5. Develop administrative controls (to include special procedures and training.) 6. Provide protective clothing and equipment. When added to the twodimensional models, the level of control adds a visual representation of the risk associated with the hazardous condition, creating a tall-pole for the least-well-controlled failure while establishing the relative likelihood and severity of all causes and effects for an identified hazard. Computer modeling of the analytical results, using spreadsheets and threedimensional charting gives a visual confirmation of the relationship between causes and their controls

Watson, Clifford↗
NASA NTRS2010

Analysis of Ancient Fluvial Patterns on the Surface of Mars

This project involves the study of ancient fluvial patterns on the surface of Mars, including raised curvilinear features (RCFs) and negative relief channels. It requires the use of geological images provided by the Mars Reconnaissance Orbiter to determine how water shaped the surface of Mars in the form of rivers, lakes and/or oceans approximately 3.5 billion years ago, during the Noachian period. The role of the intern is to examine the images and record the corresponding measurements of ancient river systems in an Excel spreadsheet to assist in determining the Noachian water cycle on Mars. Resources used to make these measurements include the Arena software, hand-drawn sketch maps, Microsoft Word, Microsoft Excel and the images provided by the Mars Reconnaissance Orbiter. The Context Imager (CTX) returns black and white images at a resolution of six meters per pixel. The camera can take images with a width of 30 km and a length of 160 km. Seventeen images were observed in total. Images are analyzed and notes are taken concerning their terminal deposits, stream ordering and drainage pattern. The Arena software is utilized to make the images more visible by allowing control of contrast and magnification. Once the image is adjusted, measurements: length, average width, drainage basin area, sinuous ridge area are recorded, at a magnification of one, through using the line segment and polygon tools. After an image has been analyzed and measured, a sketch map is drawn in order to clearly identify the various segments, basins and terminal deposits the intern observed. Observations are used to further classify the fluvial patterns; their drainage pattern is defined as dendritic, parallel, trellis, rectangular, radial, centripetal, deranged or discordant. Once observational notes are completed, mathematical relations are used to determine drainage density, stream frequency, theoretic basin area and sinuosity index. These data will be added to a larger data set that will yield a comprehensive view of early Mars drainage systems. The data obtained from the work conducted will be used to characterize the nature and behavior of water on the surface of Mars. Thorough understanding of the Martian water cycle will serve as biologically significant information. Through working on this project, I acquired insight into the study of planet Mars, and skills in the Arena software as well as the organization of a vast amount of data.

Jethani, Henna↗
NASA NTRS2010

The Significant Incidents and Close Calls in Human Space Flight Chart: Lessons Learned Gone Viral

This presentation will explore the surprising history and events that transformed a mundane spreadsheet of historical spaceflight incidents into a popular and widely distributed visual compendium of lessons learned. The Significant Incidents and Close Calls in Human Space Flight Chart (a.k.a. The Significant Incidents Chart) is a popular and visually captivating reference product that has arisen from the work of the Johnson Space Center (JSC) Safety and Mission Assurance (S&MA) Flight Safety Office (FSO). It began as an internal tool intended to increase our team s awareness of historical and modern space flight incidents. Today, the chart is widely recognized across the agency as a reference tool. It appears in several training and education programs. It is used in familiarization training in the JSC Building 9 Mockup Facility and is seen by hundreds of center visitors each week. The chart visually summarizes injuries, fatalities, and close calls sustained during the continuing development of human space flight. The poster-sized chart displays over 100 total events that have direct connections to human space flight endeavors. The chart is updated periodically. The update process itself has become a collaborative effort. Many people, spanning multiple NASA organizations, have provided suggestions for additional entries. The FSO maintains a growing list of subscribers who have requested to receive updates. The presenters will discuss the origins and motivations behind the significant incidents chart. A review of the inclusion criteria used to select events will be offered. We will address how the chart is used today by S&MA and offer a vision of how it might be used by other organizations now and in the future. Particular emphasis will be placed on features of the chart that have met with broad acceptance and have helped spread awareness of the most important lessons in human spaceflight.

Wood, Bill↗
NASA NTRS2010

Random Vibrations

Ares I Zonal Random vibration environments due to acoustic impingement and combustion processes are develop for liftoff, ascent and reentry. Random Vibration test criteria for Ares I Upper Stage pyrotechnic components are developed by enveloping the applicable zonal environments where each component is located. Random vibration tests will be conducted to assure that these components will survive and function appropriately after exposure to the expected vibration environments. Methodology: Random Vibration test criteria for Ares I Upper Stage pyrotechnic components were desired that would envelope all the applicable environments where each component was located. Applicable Ares I Vehicle drawings and design information needed to be assessed to determine the location(s) for each component on the Ares I Upper Stage. Design and test criteria needed to be developed by plotting and enveloping the applicable environments using Microsoft Excel Spreadsheet Software and documenting them in a report Using Microsoft Word Processing Software. Conclusion: Random vibration liftoff, ascent, and green run design & test criteria for the Upper Stage Pyrotechnic Components were developed by using Microsoft Excel to envelope zonal environments applicable to each component. Results were transferred from Excel into a report using Microsoft Word. After the report is reviewed and edited by my mentor it will be submitted for publication as an attachment to a memorandum. Pyrotechnic component designers will extract criteria from my report for incorporation into the design and test specifications for components. Eventually the hardware will be tested to the environments I developed to assure that the components will survive and function appropriately after exposure to the expected vibration environments.

Messaro. Semma↗
NASA NTRS2010

Integrating Variances into an Analytical Database

For this project, I enrolled in numerous SATERN courses that taught the basics of database programming. These include: Basic Access 2007 Forms, Introduction to Database Systems, Overview of Database Design, and others. My main job was to create an analytical database that can handle many stored forms and make it easy to interpret and organize. Additionally, I helped improve an existing database and populate it with information. These databases were designed to be used with data from Safety Variances and DCR forms. The research consisted of analyzing the database and comparing the data to find out which entries were repeated the most. If an entry happened to be repeated several times in the database, that would mean that the rule or requirement targeted by that variance has been bypassed many times already and so the requirement may not really be needed, but rather should be changed to allow the variance's conditions permanently. This project did not only restrict itself to the design and development of the database system, but also worked on exporting the data from the database to a different format (e.g. Excel or Word) so it could be analyzed in a simpler fashion. Thanks to the change in format, the data was organized in a spreadsheet that made it possible to sort the data by categories or types and helped speed up searches. Once my work with the database was done, the records of variances could be arranged so that they were displayed in numerical order, or one could search for a specific document targeted by the variances and restrict the search to only include variances that modified a specific requirement. A great part that contributed to my learning was SATERN, NASA's resource for education. Thanks to the SATERN online courses I took over the summer, I was able to learn many new things about computers and databases and also go more in depth into topics I already knew about.

Sanchez, Carlos↗
NASA NTRS2010

Project M: Scale Model of Lunar Landing Site of Apollo 17

The basis of the project was creating a scale model representation of the Apollo 17 lunar landing site. Vital components included surface slope characteristics, crater sizes and locations, prominent rocks, and lighting conditions. The model was made for Project M support when evaluating approach and terminal descent as well as when planning surface operations with respect to the terrain. The project had five main mi lestones during the length of the project. The first was examining the best method to use to re-create the Apollo 17 landing site and then reviewing research fmdings with Dr. Tim Crain and EO staff which occurred on June 25, 2010 at a meeting. The second step was formulating a construction plan, budget, and schedule and then presenting the plan for authority to proceed which occurred on July 6,2010. The third part was building a prototype to test materials and building processes which were completed by July 13, 2010. Next was assembling the landing site model and presenting a mid-term construction status report on July 29, 2010. The fifth and final milestone was demonstrating the model and presenting an exit pitch which happened on August 4, 2010. The project was very technical: it needed a lot of research about moon topography, lighting conditions and angles of the sun on the moon, Apollo 17, and Autonomous Landing and Hazard Avoidance Technology (ALHAT), before starting the actual building process. This required using Spreadsheets, searching internet sources and conducting personal meetings with project representatives. This information assisted the interns in deciding the scale of the model with respect to cracks, craters and rocks and their relative sizes as the objects mentioned could interfere with any of the Lunar Landers: Apollo, Project M and future Landers. The project concluded with the completion of a three dimensional scale model of the Apollo 17 Lunar landing site. This model assists Project M members because they can now visualize approach phase, terminal descent phase, and surface phase operations on the physical model. The project had an additional requirement that was also satisfied: the granite table the model was placed on must be returnable to its original condition if needed in the future.

O'Brien, Hollie↗
NASA NTRS2009

Proof of Concept Study of Trade Space Configuration Tool for Spacecraft Design

Spacecraft design is a very difficult and time consuming process because requirements and criteria are often changed or modified as the design is refined. Accounting for these adjustments in the design constraints plays a significant role in furthering the overall progress. There are numerous aspects and variables that hold significant influence on various characteristics of the design. This can be especially frustrating when attempting to conduct rapid trade space analysis on system configurations. Currently, the data and designs considered for trade space evaluations can only be displayed by using the traditional interfaces of Excel spreadsheets or CAD (Computer Aided Design) models. While helpful, these methods of analyzing the data from a systems engineering approach can be rather complicated and overwhelming. As a result, a proof of concept was conducted on a dynamic data visualization software called Thinkmap SDK (Software Developer Kit) to allow for better organization and understanding of the relationships between the various aspects that make up an entire design. The Orion Crew Module Aft Bay Subsystem was used as the test case for this study because the design and layout of many of the subsystem components will be significant in ensuring the overall center of gravity of the capsule is correct. A simplified model of this subsystem was created and programmed using Thinkmap SDK to create a preliminary prototype application of a Trade Space Configuration Tool. The completed application ensures that the core requirements for the Tool can be met. Further development is strongly suggested to produce a full prototype application to allow final evaluations and recommendations of the software capabilities.

Glidden, Geoffrey L.↗
NASA NTRS2009

Using the Saturn V and Titan III Vibroacoustic Databanks for Random Vibration Criteria Development

This is an update to TN D-7159, "Development and Application of Vibroacoustic Structural Data Banks in Predicting Vibration Design and Test Criteria for Rocket Vehicle Structures", which was originally published in 1973. Errors in the original document have been corrected and additional data from the Titan III program have been included. Methods for using the vibroacoustic databanks for vibration test criteria development are shown, as well as all of the data with drawings and pictures of the measurement locations. An Excel spreadsheet with the data included is available from the author.

Ferbee, R C.↗