SEARCH · Search NASA

Results for “Technical Integration Office”

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.

167 records · Page 10

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Ares I and Ares V First Stage - Powering Exploration

The National Aeronautics and Space Administration (NASA) Ares Projects Office (APO) is continuing to make progress toward the final design of the first stage propulsion system for the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Ares I and Ares V will provide the space launch capabilities needed to fulfill NASA' s exploration strategy of sending human beings to the Moon, Mars, and beyond. As primary propulsion for the Ares launch vehicles, the Space Shuttle-derived Reusable Solid Rocket Motor (RSRM) is one of the first and most important components to be tested. The first flight of Ares I, called Ares I-X, will occur in April 2009, with booster integration to begin at Kennedy Space Center (KSC) by autumn 2008. The Ares I-X flight will use a combination of flight and simulation hardware to obtain data on controlling the long and narrow crew launch vehicle configuration. The test will use a four-segment RSRM from the Shuttle inventory and a fifth spacer segment to simulate the size and weight of the operational five-segment motor to be used on later flights. The upper stage, Orion crew exploration vehicle, and launch abort system will all be replaced with simulator hardware. Manufacturing work has begun on the spacer segment, as well as the new forward hardware for the booster. Atlas V avionics will be adapted to control Ares I-X' s first stage. That hardware is undergoing hardware-in-the-loop testing in a contractor-provided systems integration laboratory (SIL); a critical design review (CDR) was completed in December 2007. Drogue and main parachute drop tests have also been conducted successfully at Yuma Proving Grounds, allowing the First Stage team to begin fabricating parachutes for Ares I-X. The Ares I-X flight test will be the first flight test for the parachutes. A series of preliminary design technical interchange meetings is being conducted prior to the Ares I-X CDR in January 2007 to ensure readiness for the flight. Much of the First Stage activity in 2007 has focused on a series of preliminary design (PDR) activities associated with each booster subsystem. These events will culminate in a formal preliminary design review in 2008, where subsystems and component specifications will be developed and associated analyses and drawings will be evaluated for technical adequacy. The first stage also has been undergoing a series of trade studies to determine means for upgrading booster performance and reducing operational costs. Performance improvement studies have included changing from polybutadiene acrylonitrile (PBAN) propellant to hydroxyl-terminated polybutadiene (HTPB); replacing aluminum with composite motor casings; and optimizing or upgrading the propellant grain and nozzle structures. Some or all of these changes could result in a block upgrade to the Ares I first stage, after becoming the standard configuration for the Ares V. The cost reduction studies included a change from reusable or recoverable boosters to completely expendable boosters; changing from hydrazine-powered to more environmentally friendly electrohydrostatic actuators (EHAs) on the thrust vector control (TVC) system; and changing the location of the separation plane to reduce the likelihood of recontact upon booster separation. The expendability trade study resulted in a decision to keep the recoverable boosters, as the new hardware costs significantly outweighed the potential operational cost savings due to reduced ground operations. Likewise, due to cost considerations, the team continued using existing hydrazine-powered actuators for the TVC system. The separation plane location for Ares I is still being studied, with results to be announced in 2008. In short, the Ares launch vehicles' first stage is building upon NASA's close familiarity with this Shuttle-derived system, while continuing to seek out improvements for long-term exploration.

Priskos, Alex S.↗

NASA NTRS2007

Science and the Constellation Systems Program Office

An underlying tension has existed throughout the history of NASA between the human spaceflight programs and the external scientific constituencies of the robotic exploration programs. The large human space projects have been perceived as squandering resources that might otherwise be utilized for scientific discoveries. In particular, the history of the relationship of science to the International Space Station Program has not been a happy one. The leadership of the Constellation Program Office, created in NASA in October, 2005, asked me to serve on the Program Manager s staff as a liaison to the science community. Through the creation of my position, the Program Manager wanted to communicate and elucidate decisions inside the program to the scientific community and, conversely, ensure that the community had a voice at the highest levels within the program. Almost all of my technical contributions at NASA, dating back to the Apollo Program, has been within the auspices of what is now known as the Science Mission Directorate. However, working at the Johnson Space Center, where human spaceflight is the principal activity, has given me a good deal of incidental contact and some more direct exposure through management positions to the structures and culture of human spaceflight programs. I entered the Constellation family somewhat naive but not uninformed. In addition to my background in NASA science, I have also written extensively over the past 25 years on the topic of human exploration of the Moon and Mars. (See, for example, Mendell, 1985). I have found that my scientific colleagues generally have little understanding of the structure and processes of a NASA program office; and many of them do not recognize the name, Constellation. In many respects, the international ILEWG community is better informed. Nevertheless, some NASA decision processes on the role of science, particularly with respect to the formulation of a lunar surface architecture, are not well known, even in ILEWG. At the recent annual Lunar and Planetary Science Conference, I reviewed the evolution of the program as a function of Agency leadership and the constraints put on NASA by the President in his 2004 announcement. I plan to continue my long-time ILEWG tradition of reporting a personal view of the state of development of human exploration of the solar system, this time coming from within the program office tasked to implement the vision for the United States. The current NASA implementation of the Vision for Space Exploration is consistent with certain classical scenarios that have been discussed extensively in the literature. I will discuss the role of science within the Vision, both from official policy and from a de facto interaction. While science goals are not officially driving the implementation of the Vision, the tools of scientific exploration are integral to defining the extraterrestrial design environments. In this respect the sharing of results from international missions to the Moon can make significant contributions to the success of the future human activities.

Mendell, Wendell↗

NASA NTRS2009

Connecting Research and Practice: An Experience Report on Research Infusion with SAVE

NASA systems need to be highly dependable to avoid catastrophic mission failures. This calls for rigorous engineering processes including meticulous validation and verification. However, NASA systems are often highly distributed and overwhelmingly complex, making the software portion of these systems challenging to understand, maintain, change, reuse, and test. NASA's systems are long-lived and the software maintenance process typically constitutes 60-80% of the total cost of the entire lifecycle. Thus, in addition to the technical challenges of ensuring high life-time quality of NASA's systems, the post-development phase also presents a significant financial burden. Some of NASA's software-related challenges could potentially be addressed by some of the many powerful technologies that are being developed in software research laboratories. Many of these research technologies seek to facilitate maintenance and evolution by for example architecting, designing and modeling for quality, flexibility, and reuse. Other technologies attempt to detect and remove defects and other quality issues by various forms of automated defect detection, architecture analysis, and various forms of sophisticated simulation and testing. However promising, most such research technologies nevertheless do not make the transition from the research lab to the software lab. One reason the transition from research to practice seldom occurs is that research infusion and technology transfer is difficult. For example, factors related to the technology are sometimes overshadowed by other types of factors such as reluctance to change and therefore prohibits the technology from sticking. Successful infusion might also take very long time. One famous study showed that the discrepancy between the conception of the idea and its practical use was 18 years plus or minus three. Nevertheless, infusing new technology is possible. We have found that it takes special circumstances for such research infusion to succeed: 1) there must be evidence that the technology works in the practitioner's particular domain, 2) there must be a potential for great improvements and enhanced competitive edge for the practitioner, 3) the practitioner has to have strong individual curiosity and continuous interest in trying out new technologies, 4) the practitioner has to have support on multiple levels (i.e. from the researchers, from management, from sponsors etc), and 5) to remain infused, the new technology has to be integrated into the practitioner's processes so that it becomes a natural part of the daily work. NASA IV&V's Research Infusion initiative sponsored by NASA's Office of Safety & Mission Assurance (OSMA) through the Software Assurance Research Program (SARP), strives to overcome some of the problems related to research infusion.

Lindvall, Mikael↗

DOE OSTI2025

2020 Budget Request for the DOE Computational Science Graduate Fellowship (CSGF) Grant

The Department of Energy Computational Science Graduate Fellowship (DOE CSGF) is essential for addressing the increasingly complex national workforce demands stemming from the growth of computational science and engineering challenges. Computational science and engineering (CSE) takes a multidisciplinary approach that utilizes scientific computing to tackle practical problems and provide technical tools across the spectrum of scientific discovery. The DOE CSGF specifically highlights high-performance computing (HPC) as a critical enabling technology in CSE, driving advancements in science and engineering that are vital to both the DOE and the broader economy. Over the past half-century, HPC has been an essential tool for DOE’s success. During this period, important missions, such as nuclear stockpile stewardship, have turned to HPC as an essential technology. Entire science disciplines have been transformed through the augmentation of scientific observation via HPC. At government laboratories, academic institutions, and in industry, DOE CSGF alumni are helping push traditional HPC boundaries while contributing to discoveries in high-energy physics, quantum information systems, fusion-reactor design, machine learning, additive manufacturing, nano materials for next-generation batteries and transistors, and advanced nuclear reactor modeling. In addition, HPC is used to address national health needs that will eventually point to cures both by helping cancer researchers manage and analyze huge troves of data, by simulating biological mechanisms, and by accelerating drug development. A 2023 report from the ASCAC Subcommittee on American Competitiveness and Innovation to the ASCR office, “Can the United States Maintain Its Leadership in High-Performance Computing?” says of the Program, “The CSGF program provides a barometer for disciplines that will be of interest to future DOE computing. Computational biology, machine learning, and quantum computing are among the subjects that began to swell in the ranks of CSGF applicants before the labs were hiring as high a percentage of employees in these categories.” The explosion of scientific and technological data has heightened the demand for advanced high-performance computing (HPC) to transform these data into meaningful scientific insights. As access to vast amounts of data increases, the fields of Machine Learning and Artificial Intelligence are experiencing a resurgence, enhancing the established practices of computational modeling and simulation. In its September 2020 subcommittee report on "AI/ML, Data Intensive Science, and High-Performance Computing," the DOE Advanced Scientific Computing Advisory Committee (ASCAC) specifically called for a fellowship program to train computational and data scientists to address exascale and data-intensive computing challenges. This integration of empirical and theoretical modeling will increasingly guide federal policymakers in making decisions that impact American society and future generations. It demands a workforce of highly skilled and intellectually agile computational scientists capable of navigating the rapid advancements in scientific computing within the DOE National Laboratory research environment. The DOE CSGF program has consistently addressed this critical need.

97 MATHEMATICS AND COMPUTING↗

NASA NTRS2012

The Namibia Early Flood Warning System, A CEOS Pilot Project

Over the past year few years, an international collaboration has developed a pilot project under the auspices of Committee on Earth Observation Satellite (CEOS) Disasters team. The overall team consists of civilian satellite agencies. For this pilot effort, the development team consists of NASA, Canadian Space Agency, Univ. of Maryland, Univ. of Colorado, Univ. of Oklahoma, Ukraine Space Research Institute and Joint Research Center(JRC) for European Commission. This development team collaborates with regional , national and international agencies to deliver end-to-end disaster coverage. In particular, the team in collaborating on this effort with the Namibia Department of Hydrology to begin in Namibia . However, the ultimate goal is to expand the functionality to provide early warning over the South Africa region. The initial collaboration was initiated by United Nations Office of Outer Space Affairs and CEOS Working Group for Information Systems and Services (WGISS). The initial driver was to demonstrate international interoperability using various space agency sensors and models along with regional in-situ ground sensors. In 2010, the team created a preliminary semi-manual system to demonstrate moving and combining key data streams and delivering the data to the Namibia Department of Hydrology during their flood season which typically is January through April. In this pilot, a variety of moderate resolution and high resolution satellite flood imagery was rapidly delivered and used in conjunction with flood predictive models in Namibia. This was collected in conjunction with ground measurements and was used to examine how to create a customized flood early warning system. During the first year, the team made use of SensorWeb technology to gather various sensor data which was used to monitor flood waves traveling down basins originating in Angola, but eventually flooding villages in Namibia. The team made use of standardized interfaces such as those articulated under the Open Cloud Consortium (OGC) Sensor Web Enablement (SWE) set of web services was good [1][2]. However, it was discovered that in order to make a system like this functional, there were many performance issues. Data sets were large and located in a variety of location behind firewalls and had to be accessed across open networks, so security was an issue. Furthermore, the network access acted as bottleneck to transfer map products to where they are needed. Finally, during disasters, many users and computer processes act in parallel and thus it was very easy to overload the single string of computers stitched together in a virtual system that was initially developed. To address some of these performance issues, the team partnered with the Open Cloud Consortium (OCC) who supplied a Computation Cloud located at the University of Illinois at Chicago and some manpower to administer this Cloud. The Flood SensorWeb [3] system was interfaced to the Cloud to provide a high performance user interface and product development engine. Figure 1 shows the functional diagram of the Flood SensorWeb. Figure 2 shows some of the functionality of the Computation Cloud that was integrated. A significant portion of the original system was ported to the Cloud and during the past year, technical issues were resolved which included web access to the Cloud, security over the open Internet, beginning experiments on how to handle surge capacity by using the virtual machines in the cloud in parallel, using tiling techniques to render large data sets as layers on map, interfaces to allow user to customize the data processing/product chain and other performance enhancing techniques. The conclusion reached from the effort and this presentation is that defining the interoperability standards in a small fraction of the work. For example, once open web service standards were defined, many users could not make use of the standards due to security restrictions. Furthermore, once an interoperable sysm is functional, then a surge of users can render a system unusable, especially in the disaster domain.

Mandl, Daniel↗