Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “technical support services”

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

Dip leg plug formation evaluation and abatement testing in support of the H-Canyon accelerated basin de-inventory

As requested in the Technical Task Request (TTR), the Savannah River National Laboratory (SRNL) performed testing on the current typical bubbler dip leg design used in the H-Area Canyon (HCA). The TTR has a functional classification of General Services. Testing was initiated to ascertain if the plugging described in the TTR could be reproduced and, if so, to obtain general metrics on the resulting plugging dynamics, and evaluate possible mitigating methods, including design changes and cleaning/purging protocols. The bubblers were to be suspended in a simulant typical of H-Canyon solutions containing aluminum nitrate and silica at a temperature of 25°C using a nominal bubbler air flowrate of 7.5 SCFH. Emphasis was placed on minimizing equipment changes necessary to accomplish the mitigations, as equipment changes in the existing facility would be costly. Testing evolved into four (4) phases, concluding that plugging could indeed be reproduced (believed to be attributed to localized evaporation and bridging of crystals in the dip legs). During testing, plug formation information was obtained, including time, pressure, and temperature traces leading to plugging were defined; solution compositions leading to plugging were determined, and various physical characteristics (visual and mechanical) of the crystallized plug were obtained.

42 ENGINEERING↗

Towards the formal verification of the requirements and design of a processor interface unit: HOL listings

This technical report contains the Higher-Order Logic (HOL) listings of the partial verification of the requirements and design for a commercially developed processor interface unit (PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault tolerant computer system. This system, the Fault Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU verification as it currently exists. Section two of this report contains general-purpose HOL theories and definitions that support the PIU verification. These include arithmetic theories dealing with inequalities and associativity, and a collection of tactics used in the PIU proofs. Section three contains the HOL listings for the completed PIU design verification. Section 4 contains the HOL listings for the partial requirements verification of the P-Port.

Fura, David A.↗

Towards the formal specification of the requirements and design of a processor interface unit: HOL listings

This technical report contains the HOL listings of the specification of the design and major portions of the requirements for a commercially developed processor interface unit (or PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU specification as it currently exists. Section two of this report contains general-purpose HOL theories that support the PIU specification. These theories include definitions for the hardware components used in the PIU, our implementation of bit words, and our implementation of temporal logic. Section three contains the HOL listings for the PIU design specification. Aside from the PIU internal bus (I-Bus), this specification is complete. Section four contains the HOL listings for a major portion of the PIU requirements specification. Specifically, it contains most of the definition for the PIU behavior associated with memory accesses initiated by the local processor.

Fura, David A.↗

Concepts, requirements, and design approaches for building successful planning and scheduling systems

Traditional practice of systems engineering management assumes requirements can be precisely determined and unambiguously defined prior to system design and implementation; practice further assumes requirements are held static during implementation. Human-computer decision support systems for service planning and scheduling applications do not conform well to these assumptions. Adaptation to the traditional practice of systems engineering management are required. Basic technology exists to support these adaptations. Additional innovations must be encouraged and nutured. Continued partnership between the programmatic and technical perspective assures proper balance of the impossible with the possible. Past problems have the following origins: not recognizing the unusual and perverse nature of the requirements for planning and scheduling; not recognizing the best starting point assumptions for the design; not understanding the type of system that being built; and not understanding the design consequences of the operations concept selected.

Hornstein, Rhoda Shaller↗

A systems approach to the commercialization of space communications technology - The NASA/JPL Mobile Satellite Program

This paper discusss the systems approach taken by NASA and the Jet Propulsion Laboratory in the commercialization of land-mobile satellite services (LMSS) in the United States. As the lead center for NASA's Mobile Satellite Program, JPL was involved in identifying and addressing many of the key barriers to commercialization of mobile satellite communications, including technical, economic, regulatory and institutional risks, or uncertainties. The systems engineering approach described here was used to mitigate these risks. The result was the development and implementation of the JPL Mobile Satellite Experiment Project. This Project included not only technology development, but also studies to support NASA in the definition of the regulatory, market, and investment environments within which LMSS would evolve and eventually operate, as well as initiatives to mitigate their associated commercialization risks. The end result of these government-led endeavors was the acceleration of the introduction of commercial mobile satellite services, both nationally and internationally.

Weber, William J., III↗

Space and Earth Sciences, Computer Systems, and Scientific Data Analysis Support, Volume 1

This Final Progress Report covers the specific technical activities of Hughes STX Corporation for the last contract triannual period of 1 June through 30 Sep. 1993, in support of assigned task activities at Goddard Space Flight Center (GSFC). It also provides a brief summary of work throughout the contract period of performance on each active task. Technical activity is presented in Volume 1, while financial and level-of-effort data is presented in Volume 2. Technical support was provided to all Division and Laboratories of Goddard's Space Sciences and Earth Sciences Directorates. Types of support include: scientific programming, systems programming, computer management, mission planning, scientific investigation, data analysis, data processing, data base creation and maintenance, instrumentation development, and management services. Mission and instruments supported include: ROSAT, Astro-D, BBXRT, XTE, AXAF, GRO, COBE, WIND, UIT, SMM, STIS, HEIDI, DE, URAP, CRRES, Voyagers, ISEE, San Marco, LAGEOS, TOPEX/Poseidon, Pioneer-Venus, Galileo, Cassini, Nimbus-7/TOMS, Meteor-3/TOMS, FIFE, BOREAS, TRMM, AVHRR, and Landsat. Accomplishments include: development of computing programs for mission science and data analysis, supercomputer applications support, computer network support, computational upgrades for data archival and analysis centers, end-to-end management for mission data flow, scientific modeling and results in the fields of space and Earth physics, planning and design of GSFC VO DAAC and VO IMS, fabrication, assembly, and testing of mission instrumentation, and design of mission operations center.

Estes, Ronald H.↗

Study and Sub-System Optimization of Propulsion and Drive Systems for the Large Civil TiltRotor (LCTR2) Rotorcraft

In a series of study tasks conducted as a part of NASA's Fundamental Aeronautics Program, Rotary Wing Project, Boeing and Rolls-Royce explored propulsion, drive, and rotor system options for the NASA Large Civil Tilt Rotor (LCTR2) concept vehicle. The original objective of this study was to identify engine and drive system configurations to reduce rotor tip speed during cruise conditions and quantify the associated benefits. Previous NASA studies concluded that reducing rotor speed (from 650 fps hover tip speed) during cruise would reduce vehicle gross weight and fuel burn. Initially, rotor cruise speed ratios of 54% of the hover tip speed were of most interest during operation at cruise air speed of 310 ktas. Interim results were previously reported1 for cruise tip speed ratios of 100%, 77%, and 54% of the hover tip speed using engine and/or gearbox features to achieve the reduction. Technology levels from commercial off-the-shelf (COTS), through entry-in-service (EIS) dates of 2025 and 2035 were considered to assess the benefits of advanced technology on vehicle gross weight and fuel burn. This technical paper presents the final study results in terms of vehicle sizing and fuel burn as well as Operational and Support (O&S) costs. New vehicle sizing at rotor tip speed reduced to 65% of hover is presented for engine performance with an EIS 2035 fixed geometry variable speed power turbine. LCTR2 is also evaluated for missions range cases of 400, 600, 800, 1000, and 1200 nautical miles and cruise air speeds of 310, 350 and 375 ktas.

Robuck, Mark↗

Validation of Cryogenic Propellant Tank Filling using Computational Fluid Dynamics Simulation

The Fluid Dynamics Branch at MSFC has positioned itself to support a wide range of customers in need of Cryogenic Fluid Management (CFM) analysis. A computational fluid dynamics (CFD) tool used for all manner of internal and external propulsion applications has been extended and refined to better model cryogenic propellant storage and tanking operations. Through the CFM Portfolio project, several validation activities were initiated. Validation of propellant tank self-pressurization, autogenous pressurization, slosh-induced ullage collapse, and jet-induced mixing all aid in defining model accuracy. The on-going validation effort has enabled confident application of the tool to in-line design and evaluation of CFM hardware and operations. Recent project support included defining the impact of in-space slosh dynamics on reaction control system mass for Space Launch System (SLS) upper stages. Propellant mixing strategies were defined to improve performance of a thermal vent system for a Commercial Lunar Payload Services (CLPS) partner. Design support of in-space maneuvers, tank hardware, and autogenous pressurization operations was also provided through Human Landing System (HLS) collaboration work. The branch has engaged the CFM community to share recent findings and capabilities through several forums including conferences, technical interchange meetings, and workshops. Development and demonstration of CFM modeling capabilities continues in this work on the no-vent fill of propellant tank in micro-gravity to meet the needs of NASA and its industry partners in the endeavor to sustainably reach the Moon and beyond.

CFD↗

JDD, Inc. Database

JDD Inc, is a maintenance and custodial contracting company whose mission is to provide their clients in the private and government sectors "quality construction, construction management and cleaning services in the most efficient and cost effective manners, (JDD, Inc. Mission Statement)." This company provides facilities support for Fort Riley in Fo,rt Riley, Kansas and the NASA John H. Glenn Research Center at Lewis Field here in Cleveland, Ohio. JDD, Inc. is owned and operated by James Vaughn, who started as painter at NASA Glenn and has been working here for the past seventeen years. This summer I worked under Devan Anderson, who is the safety manager for JDD Inc. in the Logistics and Technical Information Division at Glenn Research Center The LTID provides all transportation, secretarial, security needs and contract management of these various services for the center. As a safety manager, my mentor provides Occupational Health and Safety Occupation (OSHA) compliance to all JDD, Inc. employees and handles all other issues (Environmental Protection Agency issues, workers compensation, safety and health training) involving to job safety. My summer assignment was not as considered "groundbreaking research" like many other summer interns have done in the past, but it is just as important and beneficial to JDD, Inc. I initially created a database using a Microsoft Excel program to classify and categorize data pertaining to numerous safety training certification courses instructed by our safety manager during the course of the fiscal year. This early portion of the database consisted of only data (training field index, employees who were present at these training courses and who was absent) from the training certification courses. Once I completed this phase of the database, I decided to expand the database and add as many dimensions to it as possible. Throughout the last seven weeks, I have been compiling more data from day to day operations and been adding the information to the database. It now consists of seven different categories of data (carpet cleaning, forms, NASA Event Schedules, training certifications, wall and vent cleaning, work schedules, and miscellaneous) . I also did some field inspecting with the supervisors around the site and was present at all of the training certification courses that have been scheduled since June 2004. My future outlook for the JDD, Inc. database is to have all of company s information from future contract proposals, weekly inventory, to employee timesheets all in this same database.

Miller, David A., Jr.↗

SARS-CoV-2 transmission control in California correctional facilities

LBNL provided technical assistance to the CalPROTECT project, which is a collaboration between the University of California, Berkeley and the University of California, San Francisco. The CalPORTECT team provided support and guidance to the California Department of Corrections and Rehabilitation (CDCR) and the California Correctional Health Care Services (CCHCS) in their response to the COVID-19 pandemic. The CalPROTECT team provided recommendations to mitigate the risk posed to the residents and staff who live and work in CDCR prisons through considering scientific knowledge of the virus, analyzing anonymized resident and staff level data from CCHCS, evaluation of statewide and institution-level policies, and data collection during site visits to CDCR prisons during the pandemic.

59 BASIC BIOLOGICAL SCIENCES↗

Next-Generation RS-25 Engines for the NASA Space Launch System

The utilization of heritage RS-25 engines, also known as the Space Shuttle Main Engine (SSME), has enabled rapid progress in the development and certification of the NASA Space Launch System (SLS) toward operational flight status. The RS-25 brings design maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over 1 million seconds total accumulated hot-fire time. In addition, there were also 16 flight engines and 2 development engines remaining from the Space Shuttle program that could be leveraged to support the first four flights. Beyond these initial SLS flights, NASA must have a renewed supply of RS-25 engines that must reflect program affordability imperatives as well as technical requirements imposed by the SLS Block-1B vehicle (i.e., 111% RPL power level, reduced service life). Recognizing the long lead times needed for the fabrication, assembly and acceptance testing of flight engines, design activities are underway to improve system affordability and eliminate obsolescence concerns. These key objectives are enabled largely by utilizing modern materials and fabrication technologies, but also by innovations in systems engineering and integration (SE&I) practices.

Ballard, Richard O.↗

Next-Generation RS-25 Engines for the NASA Space Launch System

The utilization of heritage RS-25 engine, also known as the Space Shuttle Main Engine (SSME), has enabled rapid progress in the development and certification of the NASA Space Launch System (SLS) toward operational flight status. The RS-25 brings design maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over a million seconds total accumulated hot-fire time. In addition, there were also over a dozen functional flight assets remaining from the Space Shuttle program that could be leveraged to support the first four flights. Beyond these initial SLS flights, NASA must have a renewed supply of RS-25 engines that must reflect program affordability imperatives as well as technical requirements imposed by the SLS Block-1B vehicle (i.e., 111% RPL power level, reduced service life). Recognizing the long lead times needed for the fabrication, assembly and acceptance testing of flight engines, design activities are underway at NASA and the RS-25 engine provider, Aerojet Rocketdyne, to improve system affordability and eliminate obsolescence concerns. This paper describes how the achievement of these key objectives are enabled largely by utilizing modern materials and fabrication technologies, but also by innovations in systems engineering and integration (SE&I) practices.

Ballard, Richard O.↗

Agency Agreements Process Champion Support Intern

This document will provide information on the 2018 Spring semester NIFS Intern who represented the Office of Chief Financial Officer (OCFO) as a Reimbursable Accountant at Kennedy Space Center (KSC). This intern supported the Agency Agreements Process Champions and Team Lead, Susan Kroskey, Sandy Massey and Mecca Murphy, with major initiatives to advance the KSC OCFO's vision of creating and innovating healthy financial management practices that maximize the value of resources entrusted to NASA. These initiatives include, but are not limited to: updating the Agency Guidance and NASA Procedural Guidance 9090.1 Agreements, implementing a new budget structure to be utilized across all centers, submitting a Call Request (CRQ) to enhance non-federal customer reporting, initiating a discussion to incorporate a 3-year funding program for NASA agreements, and undertaking the Office of Inspector General (OIG) Audit. In support of these initiatives, this intern identified technical methods to enhance and reduce the workload of financial processes for reimbursable and non-reimbursable agreements, prepared reports in support of accounting functions, and performed administrative work and miscellaneous technical tasks in support of the OCFO as requested. In conclusion of the internship, the intern will become knowledgeable on reimbursable accounting, reimbursable policy, types of reimbursable agreements, the agreements process, estimated pricing reports, and the roles and responsibilities of the Financial Accounting and Financial Services offices.

Process Champion↗

NASA-ACEE/Boeing 737 graphite-epoxy horizontal stabilizer service

The 737 graphite-epoxy horizontal stabilizer was developed by Boeing as part of the NASA-ACEE (Aircraft Energy Efficiency) Advanced Composite Structures Program. NASA-ACEE programs challenged large-transport manufacturers to use graphite material in redesigning existing aircraft components. The goal of the program was to develop the necessary data and technology to achieve production commitments to advanced composites. Boeing designed, fabricated, and certified five shipsets of horizontal stabilizers for the 737-200 airframe. The program was initiated in July 1977 and certification was achieved in August 1982. Schedule highlights are shown. The work performed on this program is reported in NASA technical summaries and final reports. Boeing introduced the stabilizer into commercial operation in 1984, and has maintained surveillance for seven years of in-service evaluation. Outstanding performance was demonstrated with no service incidents attributed to the graphite-epoxy structure. Boeing will continue to monitor and support these aircraft, adding to the database of commercial composite experience.

Quinlivan, J. T.↗

Challenges of Integrating NASAs Space Communication Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Reinert, Jessica M.↗

Challenges of Integrating NASA's Space Communications Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Systems Integration↗

Base Support Building Solid Waste Management Unit (SWMU) 014 PlumeStop Injection Pilot Study Work Plan

This document is a Pilot Study Work Plan (PSWP) for a PlumeStop® permeable reactive barrier (PRB) at the Base Support Building (BSB; the Site) located at the John F. Kennedy Space Center (KSC), Florida. The Site has been designated as Solid Waste Management Unit (SWMU) 014 under KSC’s Resource Conservation and Recovery Act (RCRA) Corrective Action program. This document was prepared by AECOM Technical Services, Inc. (AECOM) for the National Aeronautics and Space Administration (NASA) under Indefinite Delivery Indefinite Quantity Contract 80KSC019D0010, Task Order 80KSC021F0096. This PSWP details the permeable reactive barrier (PRB) being installed at the BSB to decrease concentrations of per- and polyfluoroalkyl substances (PFAS) in downgradient groundwater using PlumeStop®. PlumeStop® is a colloidal activated carbon that PFAS compounds readily adsorb to. This PSWP outlines the design criteria, injection plan, and performance monitoring schedule for the proposed PlumeStop® PRB study that will guide the possible selection for use and future design of future full-scale PlumeStop® PRBs at KSC.

PFAS↗

Utility Managed Distributed Energy Resources Intelligent Community - UDERMS iCommunity (Final Technical Report)

The Utility Managed Distributed Energy Resources Intelligent Community (UDERMS iCommunity) project, led by PacifiCorp and supported by the U.S. Department of Energy’s Building Technologies Office (Award No. DEEE0009782), aimed to demonstrate an integrated, utility-managed “behind-the-meter” distributed energy resource (DER) program connecting multifamily, commercial, institutional, and industrial buildings to deliver grid services and improve energy efficiency.

14 SOLAR ENERGY↗