SEARCH · Engineering Papers

Results for “NASA Process Requirements”

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

SourceResearch connectionFrom yearThrough year

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

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS1973

Phase 111A Crew Interface Specifications Development for Inflight Maintenance and Stowage Functions

This report presents the findings and data products developed during the Phase IIIA Crew Interface Specification Study for Inflight Maintenance and Stowage Functions, performed by General Electric for the NASA, Johnson Space Center with a set of documentation that can be used as definitive guidelines to improve the present process of defining, controlling and managing flight crew interface requirements that are related to inflight maintenance (including assembly and servicing) and stowage functions. During the Phase IIIA contract period, the following data products were developed: 1) Projected NASA Crew Procedures/Flight Data File Development Process. 2) Inflight Maintenance Management Process Description. 3) Preliminary Draft, General Specification, Inflight Maintenance Management Requirements. 4) Inflight Maintenance Operational Process Description. 5) Preliminary Draft, General Specification, Inflight Maintenance Task and Support Requirements Analysis. 6) Suggested IFM Data Processing Reports for Logistics Management The above Inflight Maintenance data products have been developed during the Phase IIIA study after review of Space Shuttle Program Documentation, including the Level II Integrated Logistics Requirements and other DOD and NASA data relative to Payloads Accommodations and Satellite On-Orbit Servicing. These Inflight Maintenance data products were developed to be in consonance with Space Shuttle Program technical and management requirements.

Carl, John G.↗

NASA NTRS2010

ISS Logistics Hardware Disposition and Metrics Validation

I was assigned to the Logistics Division of the International Space Station (ISS)/Spacecraft Processing Directorate. The Division consists of eight NASA engineers and specialists that oversee the logistics portion of the Checkout, Assembly, and Payload Processing Services (CAPPS) contract. Boeing, their sub-contractors and the Boeing Prime contract out of Johnson Space Center, provide the Integrated Logistics Support for the ISS activities at Kennedy Space Center. Essentially they ensure that spares are available to support flight hardware processing and the associated ground support equipment (GSE). Boeing maintains a Depot for electrical, mechanical and structural modifications and/or repair capability as required. My assigned task was to learn project management techniques utilized by NASA and its' contractors to provide an efficient and effective logistics support infrastructure to the ISS program. Within the Space Station Processing Facility (SSPF) I was exposed to Logistics support components, such as, the NASA Spacecraft Services Depot (NSSD) capabilities, Mission Processing tools, techniques and Warehouse support issues, required for integrating Space Station elements at the Kennedy Space Center. I also supported the identification of near-term ISS Hardware and Ground Support Equipment (GSE) candidates for excessing/disposition prior to October 2010; and the validation of several Logistics Metrics used by the contractor to measure logistics support effectiveness.

Rogers, Toneka R.↗

NASA NTRS1994

Recycle Requirements for NASA's 30 cm Xenon Ion Thruster

Electrical breakdowns have been observed during ion thruster operation. These breakdowns, or arcs, can be caused by several conditions. In flight systems, the power processing unit must be designed to handle these faults autonomously. This has a strong impact on power processor requirements and must be understood fully for the power processing unit being designed for the NASA Solar Electric Propulsion Technology Application Readiness program. In this study, fault conditions were investigated using a NASA 30 cm ion thruster and a power console. Power processing unit output specifications were defined based on the breakdown phenomena identified and characterized.

Pinero, Luis R.↗

NASA NTRS2015

Modeling and Analysis of Chill and Fill Processes for the EDU Tank

NASA's future missions may require long-term storage and transfer of cryogenic propellants. The Engineering Development Unit (EDU), a NASA in-house effort supported by both Marshall Space Flight Center (MSFC) and Glenn Research Center (GRC), is a Cryogenic Fluid Management (CFM) test article that primarily serves as a manufacturing pathfinder and a risk reduction task for a future CFM payload. The EDU test article, comprises a flight like tank, internal components, insulation, and attachment struts. The EDU is designed to perform integrated passive thermal control performance testing with liquid hydrogen in a space-like vacuum environment. A series of tests, with liquid hydrogen as a testing fluid, was conducted at Test Stand 300 at MSFC during summer of 2014. The objective of this effort was to develop a thermal/fluid model for evaluating the thermodynamic behavior of the EDU tank during the chill and fill processes. Generalized Fluid System Simulation Program (GFSSP), an MSFC in-house general-purpose computer program for flow network analysis, was utilized to model and simulate the chill and fill portion of the testing. The model contained the liquid hydrogen supply source, feed system, EDU tank, and vent system. The modeling description and comparison of model predictions with the test data will be presented in the final paper.

Hedayat, A.↗

NASA NTRS2003

Orbital Space Plane Program Status

The Orbital Space Plane Program is an integral part of NASA's Integrated Space Transportation Program (ISTP). The ISTP consists of three major programs: Space Shuttle, Orbital Space Plane, and Next Generation Launch Technology. The Orbital Space Plane (OSP) Program will develop a new Crew Transfer Vehicle (CTV) with multipurpose utility for the Agency. The CTV will complement and back up the Space Shuttle by taking crews to and from the International Space Station (ISS), as well as enable a transition path to future reusable launch vehicle systems. In the CTV development cycle, around 2010 it will be used as a Crew Return Vehicle (CRV). The OSP will be launched on an Evolved Expendable Launch Vehicle (EELV). NASA is in the process of establishing Level 1 Requirements and initiating concept studies. Ongoing flight demonstrators will continue, while new flight demonstrator projects will begin. The OSP Program contains two elements: (1) Technology and Demonstrations, and (2) Design, Development, and Production. The OSP Design, Development, and Production element will enter the Formulation Phase in FY03. Per NASA Procedures and Guidelines 7120.5B, the Formulation Phase will be utilized to establish the Program schedule and budget plans. Current budget planning is based on Phase A concept studies being conducted in FY03 and FY04, preliminary design activities conducted in FY04 and FY05, and a Preliminary Design Review in FY05. An OSP full-scale development decision will be made in FY05. At that point, a conclusion to proceed will result in the OSP Program transitioning from the Formulation Phase to the Development Phase.

Dumbacher, Daniel L.↗

NASA NTRS1992

Small Business Innovation Research. Program solicitation. Closing date: July 21, 1992

The National Aeronautics and Space Administration (NASA) invites small businesses to submit Phase 1 proposals in response to its Small Business Innovation Research (SBIR) Program Solicitation 92-1. Firms with research or research and development capabilities (R/R&D) in science or engineering in any of the areas listed are encouraged to participate. This, the tenth annual SBIR solicitation by NASA, describes the program, identifies eligibility requirements, describes the proposal evaluation and award selection process, and provides other information to assist those interested in participating in NASA's SBIR program. It also identifies, in Section 8.0, the technical topics and subtopics in which SBIR Phase 1 proposals are solicited in 1992. These topics and subtopics cover a broad range of current NASA interests but do not necessarily include all areas in which NASA plans or currently conducts research. The NASA SBIR program seeks innovative approaches that respond to the needs, technical requirements, and new opportunities described in the subtopics. The focus is on innovation through the use of emerging technologies, novel applications of existing technologies, exploitation of scientific breakthroughs, or new capabilities or major improvements to existing technologies. NASA plans to select about 320 high-quality research or research and development proposals for Phase 1 contract awards on the basis of this Solicitation. Phase 1 contracts are normally six months in duration and funded up to $50,000, including profit. Selections will be based on the competitive merits of the offers and on NASA needs and priorities.

Source record↗

NASA NTRS2006

Communal Cooperation in Sensor Networks for Situation Management

Situation management is a rapidly evolving science where managed sources are processed as realtime streams of events and fused in a way that maximizes comprehension, thus enabling better decisions for action. Sensor networks provide a new technology that promises ubiquitous input and action throughout an environment, which can substantially improve information available to the process. Here we describe a NASA program that requires improvements in sensor networks and situation management. We present an approach for massively deployed sensor networks that does not rely on centralized control but is founded in lessons learned from the way biological ecosystems are organized. In this approach, fully distributed data aggregation and integration can be performed in a scalable fashion where individual motes operate based on local information, making local decisions that achieve globally-meaningful results. This exemplifies the robust, fault-tolerant infrastructure required for successful situation management systems.

Jones, Kennie H.↗

NASA NTRS2006

A Roadmap for Using Agile Development in a Traditional Environment

One of the newer classes of software engineering techniques is called 'Agile Development'. In Agile Development software engineers take small implementation steps and, in some cases, they program in pairs. In addition, they develop automatic tests prior to implementing their small functional piece. Agile Development focuses on rapid turnaround, incremental planning, customer involvement and continuous integration. Agile Development is not the traditional waterfall method or even a rapid prototyping method (although this methodology is closer to Agile Development). At the Jet Propulsion Laboratory (JPL) a few groups have begun Agile Development software implementations. The difficulty with this approach becomes apparent when Agile Development is used in an organization that has specific criteria and requirements handed down for how software development is to be performed. The work at the JPL is performed for the National Aeronautics and Space Agency (NASA). Both organizations have specific requirements, rules and processes for developing software. This paper will discuss some of the initial uses of the Agile Development methodology, the spread of this method and the current status of the successful incorporation into the current JPL development policies and processes.

software methodology↗

NASA NTRS1993

Telemetry ground system development via the component approach

NASA's deployment of major space projects such as the Earth Observing System (EOS) will demand increased functionality and ground-based telemetry processing performance well above current capabilities. At the NASA/Goddard Space Flight Center, custom hardware and software components have been developed and combined into a unique architecture to address this problem. The hardware components utilize Application Specific Integrated Circuits (ASIC's) developed specifically to support NASA's telemetry data systems needs and designed to handle data rates up to 300 Mbps. A generalized set of software components, called the Telemetry Processing Control Environment facilitate the rapid construction of control and monitoring functions for the ground-based telemetry processing systems. This combination of hardware and software elements enables rapid construction of flexible, cost-effective telemetry processing systems capable of meeting the performance requirements facing NASA in the coming decade.

Thorn, Karen E.↗

NASA NTRS2019

Numerical Model of the Mars Electrostatic Precipitator

NASA's future human exploration missions will require chemical processing plants to convert local resources into consumables to support astronaut activities. The thin and mostly carbon dioxide atmosphere of Mars is estimated to have 1 - 10 particles/cu.cm with diameters of 1 - 10 m and up to 1000 particles/cu.cm during storms. The dust in the Martian atmosphere can foul chemical reactors and pose a risk to life support systems. Electrostatic precipitation (ESP) removes dust particles from the Martian atmosphere. The Electrostatics and Surface Physics Laboratory at NASA's Kennedy Space Center has developed a COMSOL Multiphysics(Registered Trademark) model of an ESP for dust filtration on Mars. The fundamental principles of an ESP can be simulated by four physics modules: plasma, AC/DC electromagnetics, computational fluid dynamics (CFD), and particle tracing. In the ESP model presented here, the plasma module was solved to estimate particle charge. The AC/DC and CFD module were solved for the electrostatic force and fluid force. The particle-tracing module was solved for particle collection efficiency.

Wang, Jerry J.↗

NASA NTRS2011

Evaluating Cloud Computing in the Proposed NASA DESDynI Ground Data System

The proposed NASA Deformation, Ecosystem Structure and Dynamics of Ice (DESDynI) mission would be a first-of-breed endeavor that would fundamentally change the paradigm by which Earth Science data systems at NASA are built. DESDynI is evaluating a distributed architecture where expert science nodes around the country all engage in some form of mission processing and data archiving. This is compared to the traditional NASA Earth Science missions where the science processing is typically centralized. What's more, DESDynI is poised to profoundly increase the amount of data collection and processing well into the 5 terabyte/day and tens of thousands of job range, both of which comprise a tremendous challenge to DESDynI's proposed distributed data system architecture. In this paper, we report on a set of architectural trade studies and benchmarks meant to inform the DESDynI mission and the broader community of the impacts of these unprecedented requirements. In particular, we evaluate the benefits of cloud computing and its integration with our existing NASA ground data system software called Apache Object Oriented Data Technology (OODT). The preliminary conclusions of our study suggest that the use of the cloud and OODT together synergistically form an effective, efficient and extensible combination that could meet the challenges of NASA science missions requiring DESDynI-like data collection and processing volumes at reduced costs.

Benchmark↗

NASA NTRS2000

Ames Research Center FY 2000 Implementation Plan: Leading Technology into the New Millennium

This document presents the implementation plan for Ames Research Center (ARC) within the overall framework of the NASA Strategic Plan. It describes how ARC intends to implement its Center of Excellence responsibilities, Agency assigned missions, Agency and Enterprise lead programs, and other roles in support of NASA's vision and mission. All Federal agencies are required by the 1993 Government Performance and Results Act to implement a long-term strategic planning process that includes measurable outcomes and strict accountability. At NASA, this planning process is shaped by the Space Act of 1958, annual appropriations, and other external mandates, as well as by customer requirements. The resulting Strategic Plan sets the overall architecture for what we do, identifies who our customers are, and directs where we are going and why. The Strategic Plan is the basis upon which decisions regarding program implementation and resource deployment are made. Whereas the strategic planning process examines the long-term direction of the organization and identifies a specific set of goals, the implementation planning process examines the detailed performance of the organization and allocates resources toward meeting these goals. It is the purpose of this implementation document to provide the connection between the NASA Strategic Plan and the specific programs and support functions that ARC employees perform. This connection flows from the NASA Strategic Plan, through the various Strategic Enterprise plans to the ARC Center of Excellence, primary missions, Lead Center programs, program support responsibilities, and ultimately, to the role of the individual ARC employee.

Source record↗

NASA NTRS2007

Robust Low-Cost Cathode for Commercial Applications

Under funding from the NASA Commercial Technology Office, a cathode assembly was designed, developed, fabricated, and tested for use in plasma sources for ground-based materials processing applications. The cathode development activity relied on the large prior NASA investment and successful development of high-current, high-efficiency, long-life hollow cathodes for use on the International Space Station Plasma Contactor System. The hollow cathode was designed and fabricated based on known engineering criteria and manufacturing processes for compatibility with the requirements of the plasma source. The transfer of NASA GRC-developed hollow cathode technology for use as an electron emitter in the commercial plasma source is anticipated to yield a significant increase in process control, while eliminating the present issues of electron emitter lifetime and contamination.

Patterson, Michael J.↗

NASA NTRS2002

Managing Risk for Cassini During Mission Operations and Data Analysis (MOandDA)

A Risk Management Process has been tailored for Cassini that not only satisfies the requirements of NASA and JPL, but also allows the Program to proactively identify and assess risks that threaten mission objectives. Cassini Risk Management is a team effort that involves both management and engineering staff. The process is managed and facilitated by the Mission Assurance Manager (MAM), but requires regular interactions with Program Staff and team members to instill the risk management philosophy into the day to day mission operations. While Risk Management is well defined for projects in the development phase, it is a relatively new concept for Mission Operations. The Cassini team has embraced this process and has begun using it in an effective, proactive manner, to ensure mission success. It is hoped that the Cassini Risk Management Process will form the basis by which risk management is conducted during MO&DA on future projects. proactive in identifying, assessing and mitigating risks before they become problems. Cost ehtiveness is achieved by: Comprehensively identifying risks Rapidly assessing which risks require the expenditure of pruject cewums Taking early actions to mitigate these risks Iterating the process frequently, to be responsive to the dynamic internal and external environments The Cassini Program has successfully implemented a Risk Management Process for mission operations, The initial SRL has been developed and input into he online tool. The Risk Management webbased system has been rolled out for use by the flight team and risk owners we working proactive in identifying, assessing and mitigating risks before they become problems. Cost ehtiveness is achieved by: Comprehensively identifying risks Rapidly assessing which risks require the expenditure of pruject cewums Taking early actions to mitigate these risks Iterating the process frequently, to be responsive to the dynamic internal and external environments The Cassini Program has successfully implemented a Risk Management Process for mission operations, The initial SRL has been developed and input into he online tool. The Risk Management webbased system has been rolled out for use by the flight team and risk owners we working put into place will become visible and will be illusmted in future papers.

risk management↗

NASA NTRS1989

Integrating NASA's Land Analysis System (LAS) image processing software with an appropriate Geographic Information System (GIS): A review of candidates in the public domain

A user requirements analysis (URA) was undertaken to determine and appropriate public domain Geographic Information System (GIS) software package for potential integration with NASA's LAS (Land Analysis System) 5.0 image processing system. The necessity for a public domain system was underscored due to the perceived need for source code access and flexibility in tailoring the GIS system to the needs of a heterogenous group of end-users, and to specific constraints imposed by LAS and its user interface, Transportable Applications Executive (TAE). Subsequently, a review was conducted of a variety of public domain GIS candidates, including GRASS 3.0, MOSS, IEMIS, and two university-based packages, IDRISI and KBGIS. The review method was a modified version of the GIS evaluation process, development by the Federal Interagency Coordinating Committee on Digital Cartography. One IEMIS-derivative product, the ALBE (AirLand Battlefield Environment) GIS, emerged as the most promising candidate for integration with LAS. IEMIS (Integrated Emergency Management Information System) was developed by the Federal Emergency Management Agency (FEMA). ALBE GIS is currently under development at the Pacific Northwest Laboratory under contract with the U.S. Army Corps of Engineers' Engineering Topographic Laboratory (ETL). Accordingly, recommendations are offered with respect to a potential LAS/ALBE GIS linkage and with respect to further system enhancements, including coordination with the development of the Spatial Analysis and Modeling System (SAMS) GIS in Goddard's IDM (Intelligent Data Management) developments in Goddard's National Space Science Data Center.

Rochon, Gilbert L.↗

NASA NTRS1991

Computational needs survey of NASA automation and robotics missions. Volume 2: Appendixes

NASA's operational use of advanced processor technology in space systems lags behind its commercial development by more than eight years. One of the factors contributing to this is the fact that mission computing requirements are frequency unknown, unstated, misrepresented, or simply not available in a timely manner. NASA must provide clear common requirements to make better use of available technology, to cut development lead time on deployable architectures, and to increase the utilization of new technology. Here, NASA, industry and academic communities are provided with a preliminary set of advanced mission computational processing requirements of automation and robotics (A and R) systems. The results were obtained in an assessment of the computational needs of current projects throughout NASA. The high percent of responses indicated a general need for enhanced computational capabilities beyond the currently available 80386 and 68020 processor technology. Because of the need for faster processors and more memory, 90 percent of the polled automation projects have reduced or will reduce the scope of their implemented capabilities. The requirements are presented with respect to their targeted environment, identifying the applications required, system performance levels necessary to support them, and the degree to which they are met with typical programmatic constraints. Here, appendixes are provided.

Davis, Gloria J.↗

NASA NTRS1998

The Impact of NPG 7120.5A Upon Training and Development

NASA Procedures and Guidance 7120.5A for Program and Project Management Processes and Requirements should have minimal effect upon current Agency training and development programs - mainly because the new directive simply formalizes what we have been teaching and learning in the NASA Program/Project Management Initiative all along. A frequent complaint we get from the 8,000 or so graduates of our PPMI courses over the years, however, deals with resistance to what they may have learned in the classroom or training site. Brimming with new ideas, these young men and women often run up against an entrenched program or project manager who insists that things be done "the old way," too often perceived as "the NASA way" or even "the Goddard way." Management was all too often in the eyes of the manager; now we're all reading from the same book, 7120.5A, Still, there is no single method or "one size fits all" approach to project management in NASA. While each Center is responsible for developing policies, processes and procedures to comply with the new NPG, individual program and project managers will still need to tailor their requirements to the specific needs of the project, consistent with the size, complexity, risk and criticality of the project. Under NPG 7120.5A, the results of such tailoring are to be documented in agreements among managers, directors, Enterprise Associate Administrators and the Administrator.

Hoffman, Edward J.↗

NASA NTRS2000

Goals Analysis Procedure Guidelines for Applying the Goals Analysis Process

One of the key elements to successful project management is the establishment of the "right set of requirements", requirements that reflect the true customer needs and are consistent with the strategic goals and objectives of the participating organizations. A viable set of requirements implies that each individual requirement is a necessary element in satisfying the stated goals and that the entire set of requirements, taken as a whole, is sufficient to satisfy the stated goals. Unfortunately, it is the author's experience that during project formulation phases' many of the Systems Engineering customers do not conduct a rigorous analysis of the goals and objectives that drive the system requirements. As a result, the Systems Engineer is often provided with requirements that are vague, incomplete, and internally inconsistent. To complicate matters, most systems development methodologies assume that the customer provides unambiguous, comprehensive and concise requirements. This paper describes the specific steps of a Goals Analysis process applied by Systems Engineers at the NASA Langley Research Center during the formulation of requirements for research projects. The objective of Goals Analysis is to identify and explore all of the influencing factors that ultimately drive the system's requirements.

Motley, Albert E., III↗