Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “CONTRACTORS”

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

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

At least 1,693 records · Page 94
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Shuttle Case Study Collection Website Development

As a continuation from summer 2012, the Shuttle Case Study Collection has been developed using lessons learned documented by NASA engineers, analysts, and contractors. Decades of information related to processing and launching the Space Shuttle is gathered into a single database to provide educators with an alternative means to teach real-world engineering processes. The goal is to provide additional engineering materials that enhance critical thinking, decision making, and problem solving skills. During this second phase of the project, the Shuttle Case Study Collection website was developed. Extensive HTML coding to link downloadable documents, videos, and images was required, as was training to learn NASA's Content Management System (CMS) for website design. As the final stage of the collection development, the website is designed to allow for distribution of information to the public as well as for case study report submissions from other educators online.

Ransom, Khadijah S.↗
NASA NTRS2013

Tuning and Robustness Analysis for the Orion Absolute Navigation System

The Orion Multi-Purpose Crew Vehicle (MPCV) is currently under development as NASA's next-generation spacecraft for exploration missions beyond Low Earth Orbit. The MPCV is set to perform an orbital test flight, termed Exploration Flight Test 1 (EFT-1), some time in late 2014. The navigation system for the Orion spacecraft is being designed in a Multi-Organizational Design Environment (MODE) team including contractor and NASA personnel. The system uses an Extended Kalman Filter to process measurements and determine the state. The design of the navigation system has undergone several iterations and modifications since its inception, and continues as a work-in-progress. This paper seeks to show the efforts made to-date in tuning the filter for the EFT-1 mission and instilling appropriate robustness into the system to meet the requirements of manned space ight. Filter performance is affected by many factors: data rates, sensor measurement errors, tuning, and others. This paper focuses mainly on the error characterization and tuning portion. Traditional efforts at tuning a navigation filter have centered around the observation/measurement noise and Gaussian process noise of the Extended Kalman Filter. While the Orion MODE team must certainly address those factors, the team is also looking at residual edit thresholds and measurement underweighting as tuning tools. Tuning analysis is presented with open loop Monte-Carlo simulation results showing statistical errors bounded by the 3-sigma filter uncertainty covariance. The Orion filter design uses 24 Exponentially Correlated Random Variable (ECRV) parameters to estimate the accel/gyro misalignment and nonorthogonality. By design, the time constant and noise terms of these ECRV parameters were set to manufacturer specifications and not used as tuning parameters. They are included in the filter as a more analytically correct method of modeling uncertainties than ad-hoc tuning of the process noise. Tuning is explored for the powered-flight ascent phase, where measurements are scarce and unmodelled vehicle accelerations dominate. On orbit, there are important trade-off cases between process and measurement noise. On entry, there are considerations about trading performance accuracy for robustness. Process Noise is divided into powered flight and coasting ight and can be adjusted for each phase and mode of the Orion EFT-1 mission. Measurement noise is used for the integrated velocity measurements during pad alignment. It is also used for Global Positioning System (GPS) pseudorange and delta- range measurements during the rest of the flight. The robustness effort has been focused on maintaining filter convergence and performance in the presence of unmodeled error sources. These include unmodeled forces on the vehicle and uncorrected errors on the sensor measurements. Orion uses a single-frequency, non-keyed GPS receiver, so the effects due to signal distortion in Earth's ionosphere and troposphere are present in the raw measurements. Results are presented showing the efforts to compensate for these errors as well as characterize the residual effect for measurement noise tuning. Another robustness tool in use is tuning the residual edit thresholds. The trade-off between noise tuning and edit thresholds is explored in the context of robustness to errors in dynamics models and sensor measurements. Measurement underweighting is also presented as a method of additional robustness when processing highly accurate measurements in the presence of large filter uncertainties.

Holt, Greg N.↗
NASA NTRS2013

Shuttle Repair Tools Automate Vehicle Maintenance

Successfully building, flying, and maintaining the space shuttles was an immensely complex job that required a high level of detailed, precise engineering. After each shuttle landed, it entered a maintenance, repair, and overhaul (MRO) phase. Each system was thoroughly checked and tested, and worn or damaged parts replaced, before the shuttle was rolled out for its next mission. During the MRO period, workers needed to record exactly what needed replacing and why, as well as follow precise guidelines and procedures in making their repairs. That meant traceability, and with it lots of paperwork. In 2007, the number of reports generated during electrical system repairs was getting out of hand-placing among the top three systems in terms of paperwork volume. Repair specialists at Kennedy Space Center were unhappy spending so much time at a desk and so little time actually working on the shuttle. "Engineers weren't spending their time doing technical work," says Joseph Schuh, an electrical engineer at Kennedy. "Instead, they were busy with repetitive, time-consuming processes that, while important in their own right, provided a low return on time invested." The strain of such inefficiency was bad enough that slow electrical repairs jeopardized rollout on several occasions. Knowing there had to be a way to streamline operations, Kennedy asked Martin Belson, a project manager with 30 years experience as an aerospace contractor, to co-lead a team in developing software that would reduce the effort required to document shuttle repairs. The result was System Maintenance Automated Repair Tasks (SMART) software. SMART is a tool for aggregating and applying information on every aspect of repairs, from procedures and instructions to a vehicle s troubleshooting history. Drawing on that data, SMART largely automates the processes of generating repair instructions and post-repair paperwork. In the case of the space shuttle, this meant that SMART had 30 years worth of operations that it could apply to ongoing maintenance work. According to Schuh, "SMART standardized and streamlined many shuttle repair processes, saving time and money while increasing safety and the quality of repairs." Maintenance technicians and engineers now had a tool that kept them in the field, and because SMART is capable of continually evolving, each time an engineer put it to use, it would enrich the Agency-wide knowledge base. "If an engineer sees something in the work environment that they could improve, a repair process or a procedure, SMART can incorporate that data for use in future operations," says Belson.

Source record↗
NASA NTRS2013

Global Response of the Space Shuttle External Tank with the Presence of Intertank Stringer Cracks and Radius Blocks

After propellant was loaded into the external tank (ET), the November 5, 2010 launch of Space Shuttle mission STS-133 was scrubbed due to a gaseous hydrogen leak located in a vent line near the ground umbilical and ET connection. Subsequent visual inspections identified cracks in the sprayed-on foam insulation in the forward end of the ET intertank segment, adjacent to the liquid oxygen (LOX) tank, as shown in Figure 1. These cracks necessitated repair of the foam due to debris concerns that violated launch constraints. As part of the repair process, the affected foam was removed to reveal cracks in the underlying external hat stiffeners on the intertank, as shown in Figure 2. Ultimately, five stiffeners were discovered to be cracked adjacent to the LOX tank. As the managing center for the ET Project, NASA Marshall Space Flight Center (MSFC) coordinated failure investigation and repair activities among multiple organizations, which included the ET prime contractor (Lockheed Martin Space Systems Michoud Operations), the Space Shuttle Program Office at the NASA Johnson Space Center (JSC), the NASA Kennedy Space Center (KSC), and the NASA Engineering and Safety Center (NESC). STS-133 utilized the external tank designated as ET-137. Many aspects of the investigation have been reported previously in Refs. 1-7, which focus on the root cause of the failures, the flight readiness rationale and the local analyses of the stringer failures and repair. This paper summarizes the global analyses that were conducted on ET-137 as part of the NESC effort during the investigation, which was conducted primarily to determine if the repairs that were introduced to the stringers would alter the global response of the ET. In the process of the investigation, a new STAGS tabular input capability was developed to more easily introduce the aerodynamic pressure loads using a method that could easily be extended to incorporate finite element property data such as skin and stiffener thicknesses and beam cross-sectional properties.

Lovejoy, Andrew E.↗
NASA NTRS2008

Chronology of KSC and KSC Related Events for 2007

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

Liston, Elaine E.↗
NASA NTRS2008

Tech Transfer Magazine - KSC News Volume I, Number 2, Fall/Winter 2008

Kennedy Tech Transfer News is the semiannual magazine of the Innovative Partnerships Program Office at NASA Kennedy Space Center in Cape Canaveral, Florida. This magazine seeks to inform and educate cMI servant and Contractor personnel at Kennedy about actively participating in achieving NASA's technology transfer goals:

Dunn, Carol↗
NASA NTRS2004

Space-Based Telemetry And Range Safety Flight Demonstration #1

The basic ability of STARS to maintain a satellite communications link with TDRSS satellites during dynamic aircraft flights was successfully demonstrated during FD 1. The Range Safety and Range User systems' link margins were measured. The ability to acquire/reacquire and maintain lock between a high-dynamic vehicle and a satellite-based system was demonstrated. The Range Safety system simultaneously received and processed command links from space and ground transmitters and provided near real-time Range Safety telemetry to DFRC, which then sent it in near real time to KSC, GSFC, and WFF for monitoring. The GPS receiver maintained track except during extremely dynamic maneuvers. The Range User system sent data at three different data rates. There were excellent cooperation and support from the different Centers, contractors, and Ranges. A large amount of data was recorded and extensive post-flight analysis was performed. The Range User TDRSS link margin met or exceeded the predicted performance at three different data rates. The Range Safety launch-head link margins generally agreed with the predicted performance. The UPS positions and velocities agreed with those from tracking radar to within about 20 m and a few rn/s. The link margins for the Range Safety TDRSS telemetry link were less than expected. The link margin for one TDRSS command link LPT channel was occasionally much less than the other. Additional post-flight testing has yet to identify the root causes of these results. There were many lessons learned from this first set of test flights. The most important one is that more time and testing are needed for each step to deal with the inevitable problems. It is vital that these lessons be among the primary areas of study that will carry over from FD#1 to FD#2, which is currently scheduled for early FY05 at DFRC and will use a specially designed Ku-band phased array antenna for the Range User system. The next series of flight demonstrations scheduled for late 2004 at DFRC will incorporate many lessons learned from FD#1. A specially designed Ku-band phased array antenna will be used with the Range User system. A test flight on a hypersonic vehicle is planned by the end of 2006.

Demspm. Erol↗
NASA NTRS2013

Commissioning of the Liquid Nitrogen Thermo-Siphon System for NASA-JSC Chamber-A

NASA's Space Environment Simulation Laboratory's (SESL) Chamber A, located at the Johnson Space Center in Houston Texas has recently implemented major enhancements of its cryogenic and vacuum systems. The new liquid nitrogen (LN2) thermo-siphon system was successfully commissioned in August of 2012. Chamber A, which has 20 K helium cryo-panels (or shrouds ) which are shielded by 80 K nitrogen shrouds, is capable of simulating a deep space environment necessary to perform ground testing of NASA s James Webb Space Telescope (JWST). Chamber A s previous system used forced flow LN2 cooling with centrifugal pumps, requiring 200,000 liters of LN2 to cool-down and consuming 180,000 liters per day of LN2 in steady operation. The LN2 system did not have the reliability required to meet the long duration test of the JWST, and the cost estimate provided in the initial approach to NASA-JSC by the sub-contractor for refurbishment of the system to meet the reliability goals was prohibitive. At NASA-JSC's request, the JLab Cryogenics Group provided alternative options in 2007, including a thermo-siphon, or natural flow system. This system, eliminated the need for pumps and used one tenth of the original control valves, relief valves, and burst disks. After the thermo-siphon approach was selected, JLab provided technical assistance in the process design, mechanical design, component specification development and commissioning oversight, while the installation and commissioning operations of the system was overseen by the Jacobs Technology/ESC group at JSC. The preliminary commissioning data indicate lower shroud temperatures, 70,000 liters to cool-down and less than 90,000 liters per day consumed in steady operation. All of the performance capabilities have exceeded the design goals. This paper will outline the comparison between the original system and the predicted results of the selected design option, and the commissioning results of thermo-siphon system.

Homan, J.↗
NASA NTRS2008

Intelligent Devices - Sensors and Actuators - A KSC Perspective

The primary objective of this workshop is to identify areas of advancement in sensor measurements and technologies that will help to define standard practices and procedures that will better enable the infusion into flight programs of sensors with improved capabilities but limited or no flight heritage. These standards would be crucial to demonstrating a methodology for validating current models while also creating the possibility of being able to have sufficient data to either update these models (e. g., spatial or temporal resolution, etc.) or develop new models based on the ability to simulate the new measured physical parameters. The workshop is also intended to narrow the gap between sensor measurements (and techniques), data processing techniques and the ability to make use of that data by gathering together experts in the field for a short workshop. This collaboration will unite NASA and other government agencies with contractor capabilities industry-wide to prevent duplication, spawn synergistic growth in sensor technology, help analysts make good engineering decisions and help focus new sensor maturation efforts to better meet future flight program customers' needs. This is the first such workshop designed to specifically address establishing a standardized protocol/methodology for demonstrating the technology readiness of non-flight heritage sensor systems. While other similar workshops are held covering many areas of interest to the sensor development community, no other meeting is specific enough to address this vital but often overlooked topic. By encouraging cross-fertilization of ideas from instrument experts from many different backgrounds, it is hoped that this workshop will initiate innovative new ideas and concepts in sensor development, calibration and validation. It is anticipated this workshop will repeat periodically as needed.

Mata, Carlos T.↗
NASA NTRS2010

Control of Risks Through the Use of Procedures: A Method for Evaluating the Change in Risk

This paper considers how procedures can be used to control risks faced by an organization and proposes a means of recognizing if a particular procedure reduces risk or contributes to the organization's exposure. The proposed method was developed out of the review of work documents and the governing procedures performed in the wake of the Columbia accident by NASA and the Space Shuttle prime contractor, United Space Alliance, LLC. A technique was needed to understand the rules, or procedural controls, in place at the time in the context of how important the role of each rule was. The proposed method assesses procedural risks, the residual risk associated with a hazard after a procedure's influence is accounted for, by considering each clause of a procedure as a unique procedural control that may be beneficial or harmful. For procedural risks with consequences severe enough to threaten the survival of the organization, the method measures the characteristics of each risk on a scale that is an alternative to the traditional consequence/likelihood couple. The dual benefits of the substitute scales are that they eliminate both the need to quantify a relationship between different consequence types and the need for the extensive history a probabilistic risk assessment would require. Control Value is used as an analog for the consequence, where the value of a rule is based on how well the control reduces the severity of the consequence when operating successfully. This value is composed of two parts: the inevitability of the consequence in the absence of the control, and the opportunity to intervene before the consequence is realized. High value controls will be ones where there is minimal need for intervention but maximum opportunity to actively prevent the outcome. Failure Likelihood is used as the substitute for the conventional likelihood of the outcome. For procedural controls, a failure is considered to be any non-malicious violation of the rule, whether intended or not. The model used for describing the Failure Likelihood considers how well a task was established by evaluating that task on five components. The components selected to define a well established task are: that it be defined, assigned to someone capable, that they be trained appropriately, that the actions be organized to enable proper completion and that some form of independent monitoring be performed. Validation of the method was based on the information provided by a group of experts in Space Shuttle ground processing when they were presented with 5 scenarios that identified a clause from a procedure. For each scenario, they recorded their perception of how important the associated rule was and how likely it was to fail. They then rated the components of Control Value and Failure Likelihood for all the scenarios. The order in which each reviewer ranked the scenarios Control Value and Failure Likelihood was compared to the order in which they ranked the scenarios for each of the associated components; inevitability and opportunity for Control Value and definition, assignment, training, organization and monitoring for Failure Likelihood. This order comparison showed how the components contributed to a relative relationship to the substitute risk element. With the relationship established for Space Shuttle ground processing, this method can be used to gauge if the introduction or removal of a particular rule will increase or decrease the .risk associated with the hazard it is intended to control.

Praino, Gregory T.↗
NASA NTRS2008

Space Transportation Systems Life Cycle Cost Assessment and Control

Civil and military applications of space transportation have been pursued for just over 50 years and there has been, and still is, a need for safe, dependable, affordable, and sustainable space transportation systems. Fully expendable and partially reusable space transportation systems have been developed and put in operation that have not adequately achieved this need. Access to space is technically achievable, but presently very expensive and will remain so until there is a breakthrough in the way we do business. Since 1991 the national Space Propulsion Synergy Team (SPST) has reviewed and assessed the lessons learned from the major U.S. space programs of the past decades focusing on what has been learned from the assessment and control of Life Cycle Cost (LCC) from these systems. This paper presents the results of a selected number of studies and analyses that have been conducted by the SPST addressing the need, as well as the solutions, for improvement in LCC. The major emphasis of the SPST processes is on developing the space transportation system requirements first (up front). These requirements must include both the usual system flight performance requirements and also the system functional requirements, including the infrastructure on Earth's surface, in-space and on the Moon and Mars surfaces to determine LCC. This paper describes the development of specific innovative engineering and management approaches and processes. This includes a focus on flight hardware maturity for reliability, ground operations approaches, and business processes between contractor and government organizations. A major change in program/project cost control is being proposed by the SPST to achieve a sustainable space transportation system LCC - controlling cost as a program metric in addition to the existing practice of controlling performance and weight. Without a firm requirement and methodically structured cost control, it is unlikely that an affordable and sustainable space transportation system LCC will ever be achieved. '

Robinson, John W.↗
NASA NTRS2009

NASA TEERM Project: Corn Based Blast Media

Coatings removal is a necessary part of the maintenance, repair, and overhaul activities at many NASA centers and contractor support sites. Sensitive substrates, such as composites and thin aluminum alloys require special handling such as the use of chemical stripping, pneumatic hand sanding, or softer blast media. Type V, acrylic based PMB is commonly used to de-coat, strip, or de-paint the delicate substrates of the Solid Rocket Boosters (SRBs) currently used in support of the Shuttle and slated to be used in support of CxP.

Griffin, Chuck↗
NASA NTRS2009

Recent Weather Technologies Delivered to America's Space Program by the Applied Meteorology Unit

The Applied Meteorology Unit (AMU) is a unique joint venture of NASA, the Air Force and the National Weather Service (NWS) and has been supporting the Space Program for nearly two decades. The AMU acts as a bridge between the meteorological research community and operational forecasters by developing, evaluating and transitioning new technology and techniques to improve weather support to spaceport operations at the Eastern Range (ER) and Kennedy Space Center. Its primary customers are the 45th Weather Squadron at Cape Canaveral Air Force Station (CCAFS), the Spaceflight Meteorology Group at Johnson Space Center and the National Weather Service Office in Melbourne, FL. Its products are used to support NASA's Shuttle and ELV programs as well as Department of Defense and commercial launches from the ER. Shuttle support includes landing sites beyond the ER. The AMU is co-located with the Air Force operational forecasters at CCAFS to facilitate continuous two-way interaction between the AMU and its operational customers. It is operated under a NASA, Air Force, and NWS Memorandum of Understanding (MOU) by a competitively-selected contractor. The contract, which is funded and managed by NASA, provides five full time professionals with degrees in meteorology or related fields, some of whom also have operational experience. NASA provides a Ph.D.- level NASA civil service scientist as Chief of the AMU. The AMU is tasked by its customers through a unique, nationally recognized process. The tasks are limited to development, evaluation and operational transition of technology to improve weather support to spaceport operations and providing expert advice to the customers. The MOU expressly forbids using the AMU resources to conduct operations or do basic research. The presentation will provide a brief overview of the AMU and how it is tasked by its customers to provide high priority products and services. The balance of the presentation will cover a sampling of products delivered over the last 18 years that are currently in operational use. Each example will describe the problem to be solved, the solution provided, and the operational benefits of implementing that solution.

Bauman, WIlliam, H., III↗
NASA NTRS2013

Internal Social Media at Marshall Space Flight Center - An Engineer's Snapshot

In the brief span of about six years (2004-2010), social media radically enhanced people's ways of maintaining recreational friendships. Social media's impact on public affairs (PAO) and community engagement is equally striking: NASA has involved millions of non-NASA viewers in its activities via outward-facing social media, often in a very two-way street fashion. Use of social media as an internal working tool by NASA's tens of thousands of civil servants, onsite contractor employees, and external stakeholders is evolving more slowly. This paper examines, from an engineer's perspective, Marshall Space Flight Center s (MSFC) efforts to bring the power of social media to the daily working environment. Primary emphasis is on an internal Social Networking Service called Explornet that could be scaled Agency-wide. Other topics include MSFC use of other social media day-to-day for non-PAO purposes, some specialized uses of social techniques in space flight control operations, and how to help a community open up so it can discover and adopt what works well.

Scott, David W.↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRS2013

STS Case Study Development Support

The Shuttle Case Study Collection (SCSC) has been developed using lessons learned documented by NASA engineers, analysts, and contractors. The SCSC provides educators with a new tool to teach real-world engineering processes with the goal of providing unique educational materials that enhance critical thinking, decision-making and problem-solving skills. During this third phase of the project, responsibilities included: the revision of the Hyper Text Markup Language (HTML) source code to ensure all pages follow World Wide Web Consortium (W3C) standards, and the addition and edition of website content, including text, documents, and images. Basic HTML knowledge was required, as was basic knowledge of photo editing software, and training to learn how to use NASA's Content Management System for website design. The outcome of this project was its release to the public.

Rosa de Jesus, Dan A.↗
NASA NTRS2013

Commercial Parts Technology Qualification Processes

Many high-reliability systems, including space systems, use selected commercial parts (including Plastic Encapsulated Microelectronics or PEMs) for unique functionality, small size, low weight, high mechanical shock resistance, and other factors. Predominantly this usage is subjected to certain 100% tests (typically called screens) and certain destructive tests usually (but not always) performed on the flight lot (typically called qualification tests). Frequently used approaches include those documented in EEE-INST-002 and JPL DocID62212 (which are sometimes modified by the particular aerospace space systems manufacturer). In this study, approaches from these documents and several space systems manufacturers are compared to approaches from a launch systems manufacturer (SpaceX), an implantable medical electronics manufacturer (Medtronics), and a high-reliability transport system process (automotive systems). In the conclusions section, these processes are outlined for all of these cases and presented in tabular form. Then some simple comparisons are made. In this introduction section, the PEM technology qualification process is described, as documented in EEE-INST-002 (written by the Goddard Space Flight Center, GSFC), as well as the somewhat modified approach employed at the Jet Propulsion Laboratory (JPL). Approaches used at several major NASA contractors are also described

Cooper, Mark S.↗
NASA NTRS2013

Mass Properties for Space Systems Standards Development

Current Verbiage in S-120 Applies to Dry Mass. Mass Margin is difference between Required Mass and Predicted Mass. Performance Margin is difference between Predicted Performance and Required Performance. Performance estimates and corresponding margin should be based on Predicted Mass (and other inputs). Contractor Mass Margin reserved from Performance Margin. Remaining performance margin allocated according to mass partials. Compliance can be evaluated effectively by comparison of three areas (preferably on a single sheet). Basic and Predicted Mass (including historical trend). Aggregate potential changes (threats and opportunities) which gives Mass Forecast. Mass Maturity by category (Estimated/Calculated/Actual).

Beech, Geoffrey↗