Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “workforce data”

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 55 records · Page 3

Building a Field: The Future of Astronomy with Gravitational Waves

Harnessing the sheer discovery potential of GW Astronomy will require bold, deliberate,and sustained efforts to train and develop the requisite workforce. The next decaderequires a strategic plan to build - from the ground up - a robust, open, andwell-connected GW Astronomy community with deep participation from traditionalastronomers, physicists, data scientists, and instrumentalists. This basic infrastructure issorely needed as an enabling foundation for research. We outline a set ofrecommendations for funding agencies, universities, and professional societies to helpbuild a thriving, diverse, and inclusive new field.

Holley-Bockelman, Kelly↗

Integrated Assessments of the Impact of Climate Change on Agriculture: An Overview of AgMIP Regional Research in South Asia

South Asia encompasses a wide and highly varied geographic region, and includes climate zones ranging from the mountainous Himalayan territory to the tropical lowland and coastal zones along alluvial floodplains. The region's climate is dominated by a monsoonal circulation that heralds the arrival of seasonal rainfall, upon which much of the regional agriculture relies. The spatial and temporal distribution of this rainfall is, however, not uniform over the region. Northern South Asia, central India, and the west coast receive much of their rainfall during the southwest monsoon season, between June and September. These rains partly result from the moisture transport accompanying the monsoonal winds, which move in the southwesterly direction from the equatorial Indian Ocean. Regions further south, such as south/southeast India and Sri Lanka, may receive rains from both the southwest monsoon, and also during the northeast monsoon season between October and December (with northeasterly monsoon wind flow and moisture flux), which results in a bi- or multi-modal rainfall distribution. In addition, rainfall across South Asia displays a large amount of intraseasonal and interannual variability. Interannual variability is influenced by many drivers, both natural (e.g., El Ni-Southern Oscillation; ENSO) and man-made (e.g., rising temperatures due to increasing greenhouse gas concentrations), and it is challenging to obtaining accurate time-series of annual rainfall, even amongst various observed data products, which display inconsistencies amongst themselves. These climatic and rainfall variations can further complicate South Asia's agricultural and water management. Agriculture employs at least 65 of the workforce in most South Asian countries, and nearly 80 of South Asia's poor inhabit rural areas. Understanding the response of current agricultural production to climate variability and future climate change is of utmost importance in securing food and livelihoods for South Asia's growing population. In order to assess the future of food and livelihood security across South Asia, the Agricultural Model Intercomparison and Improvement Project (AgMIP) has undertaken integrated climate-crop-economic assessments of the impact of climate change on food security and poverty in South Asia, encompassing Bangladesh, India, Nepal, Pakistan, and Sri Lanka. AgMIP has funded, on a competitive basis, four South Asian regional research teams (RRTs) and one South Asian coordination team (CT) to undertake climate-crop-economic integrated assessments of food security for many districts in each of these countries, with the goal of characterizing the state of food security and poverty across the region, and projecting how these are subject to change under future climate change conditions.

mountains↗

Lessons Learned Study Final Report for the Exploration Systems Mission Directorate

This report is the final product of a 90-day study performed for the Exploration Systems Mission Directorate. The study was to assemble lessons NASA has learned from previous programs that could help the Exploration Systems Mission Directorate pursue the Exploration vision. It focuses on those lessons that should have the greatest significance to the Directorate during the formulation of program and mission plans. The study team reviewed a large number of lessons learned reports and data bases, including the Columbia Accident Investigation Board and Rogers Commission reports on the Shuttle accidents, accident reports from robotic space flight systems, and a number of management reviews by the Defense Sciences Board, Government Accountability Office, and others. The consistency of the lessons, findings, and recommendations validate the adequacy of the data set. In addition to reviewing existing databases, a series of workshops was held at each of the NASA centers and headquarters that included senior managers from the current workforce as well as retirees. The full text of the workshop reports is included in Appendix A. A lessons learned website was opened up to permit current and retired NASA personnel and on-site contractors to input additional lessons as they arise. These new lessons, when of appropriate quality and relevance, will be brought to the attention of managers. The report consists of four parts: Part 1 provides a small set of lessons, called the Executive Lessons Learned, that represent critical lessons that the Exploration Systems Mission Directorate should act on immediately. This set of Executive Lessons and their supporting rationale have been reviewed at length and fully endorsed by a team of distinguished NASA alumni; Part 2 contains a larger set of lessons, called the Selected Lessons Learned, which have been chosen from the lessons database and center workshop reports on the basis of their specific significance and relevance to the near-term work of the Exploration Directorate. These lessons frequently support the Executive lessons but are more general in nature; Part 3 consists of the reports of the center workshops that were conducted as part of this activity. These reports are included in their entirety (approximately 200 pages) in Appendix G and have significance for specific managers; Part 4 consists of the remainder of the lessons that have been selected by this effort and assembled into a database for the use of the Explorations Directorate. The database is archived and hosted in the Lessons Learned Knowledge Network, which provides a flexible search capability using a wide variety of search terms. Finally, a spreadsheet lists databases searched and a bibliography identifies reports that have been reviewed as sources of lessons for this task. NASA has been presented with many learning opportunities. We have conducted numerous programs, some extremely successful and others total failures. Most have been documented with a formal lessons learned activity, but we have not always incorporated these learning opportunities into our normal modes of business. For example, the Robbins Report of 2001 clearly indicates that many project failures of the past two decades were the result of violating well documented best practices, often in direct violation of management instructions and directives. An overarching lesson emerges: that disciplined execution in accordance with proven best practices is the greatest single contributor to a successful program. The Lessons Learned task team offers a sincere hope that the lessons presented herein will be helpful to the Exploration Systems Directorate in charting and executing their course. The success of the Directorate and of NASA in general depends on our collective ability to move forward without having to relearn the lessons of those who have gone before.

Van Laak, Jim↗

U.S. Aerospace and Aviation Industry: A State-By-State Analysis

President George W. Bush and the Congress created the Commission on the Future of the United States Aerospace Industry to evaluate the current and future health of the industry as well as the challenges that lie ahead for the U.S. workforce and the economy. To accomplish our mission, we commissioned a study on the economic impact of the aerospace industry nationally and on a state-by-state basis, using the best available U.S. government data. This study sought to define the core of the aerospace industry. The resulting data represents that very core those jobs specifically tied to commercial and civilian aerospace. U.S. Aerospace and Aviation: A State-by-State Analysis examines the civilian and commercial aerospace and aviation industry by employment, wages, payroll, and establishments. The report found that the U.S. civilian and commercial aerospace and aviation industry employed over 2 million workers in 2001.

STATES (UNITED STATES)↗

The Challenges of Integrating NASA's Human, Budget, and Data Capital within the Constellation Program's Exploration Launch Projects Office

The U.S. Vision for Space Exploration directs NASA to retire the Space Shuttle in 2010 and replace it with safe, reliable, and cost-effective space transportation systems for crew and cargo travel to the Moon, Mars, and beyond. Such emerging space transportation initiatives face massive organizational challenges, including building and nurturing an experienced, dedicated team with the right skills for the required tasks; allocating and tracking the fiscal capital invested in achieving technical progress against an integrated master schedule; and turning generated data into useful knowledge that equips the team to design and develop superior products for customers and stakeholders. It has been more than 30 years since the Space Shuttle was designed; therefore, the current aerospace workforce has limited experience with developing new designs for human-rated spaceflight hardware. To accomplish these activities, NASA is using a wide range of state-of-the-art information technology tools that connect its diverse, decentralized teams and provide timely, accurate information for decision makers. In addition, business professionals are assisting technical managers with planning, tracking, and forecasting resource use against an integrated master schedule that horizontally and vertically interlinks hardware elements and milestone events. Furthermore, NASA is employing a wide variety of strategies to ensure that it has the motivated and qualified staff it needs for the tasks ahead. This paper discusses how NASA's Exploration Launch Projects Office, which is responsible for delivering these new launch vehicles, integrates its resources to create an engineering business environment that promotes mission success, which is defined by replacing the Space Shuttle by 2014 and returning to the Moon by 2020.

Kidd, Luanne↗

Climate Lecture 20: The Educational Global Climate Model (EdGCM)

Climate change will profoundly impact Earth's environmental health as well as the world's economic and geopolitical landscape over the coming decades. The impacts of climate change are, in fact, already beginning to be experienced and have the potential to affect every living plant and animal on Earth within decades. Given this reality, every citizen of this planet should have the right to knowledge about the Earth's climate system and have the option to adapt to, or help mitigate the profound changes that are coming. In addition, a portion of the workforce needs to be capable of interpreting and analyzing climate information because, since the impacts of climate change will be widespread, pervasive, and continue to change over time, more professions will be interacting with climate data. We are already at, or past, the point where educators and their students require access to the scientific and technological resources - computer models, data, and visualization tools - that scientists use daily in the study of climate change. Although scientists use many methods to study Earth's climate system, global climate models (GCMs) have become the primary tools for exploring the complex interactions between components of the entire system: atmosphere, oceans, and land. GCMs are used to make projections of future climate change, to simulate climates of the past, and even to help scientists look for life on other planets. Like any model, a GCM can help people evaluate actions before they are taken. Like Business Intelligence software, they are Climate Intelligence tools. Unfortunately, GCMs are black boxes to most people. A previous chapter in this book by Gary Russell, entitled Building a Climate Model, is one example of the growing body of literature aimed at the general public describing the inner workings of global climate models. This literature goes a long way toward explaining climate model fundamentals. However, it will not be enough to alleviate their black-box nature unless people are afforded hands-on, authentic learning experiences as well.

Chandler, Mark A.↗

Building a Transdisciplinary, Exascale-Capable Workforce for Geospace Science

Key Points: ●First-principles, self-consistent geospace modeling will require at least exascale-level computing capabilities; however, the technical skills necessary to develop such simulation codes are not taught as part of Heliophysics training/PhD programs. ●Developing exascale Heliophysics codes will require transdisciplinary collaborations between physicists, computer scientists, software engineers, data scientists, and applied mathematics. Such teams must be persistent and formed around specific skills, not specific problems. ●We must have stable, positive long-term career outcomes for Heliophysics scientific developers in order to retain knowledge of and promote future innovation in scientific algorithm development and advanced computing techniques. One such way to do this is by funding long-term scientific programming groups, akin to Heliophysics DRIVE Centers. ●We must have a balance between promoting innovation via funding short-term closed-source development and allowing the open-source community to benefit from and build on the newest scientific modeling techniques.

C Bard↗

Space Station Furnace Facility Management Information System (SSFF-MIS) Development

This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.

Meade, Robert M.↗

Integrated Vehicle Ground Vibration Testing of Manned Spacecraft: Historical Precedent

For the first time in nearly 30 years, NASA is developing a new manned space flight launch system. The Ares I will carry crew and cargo to not only the International Space Station, but onward for the future exploration of the Moon and Mars. The Ares I control system and structural designs use complex computer models for their development. An Integrated Vehicle Ground Vibration Test (IVGVT) will validate the efficacy of these computer models. The IVGVT will reduce the technical risk of unexpected conditions that could place the vehicle or crew in jeopardy. The Ares Project Office's Flight and Integrated Test Office commissioned a study to determine how historical programs, such as Saturn and Space Shuttle, validated the structural dynamics of an integrated flight vehicle. The study methodology was to examine the historical record and seek out members of the engineering community who recall the development of historic manned launch vehicles. These records and interviews provided insight into the best practices and lessons learned from these historic development programs. The information that was gathered allowed the creation of timelines of the historic development programs. The timelines trace the programs from the development of test articles through test preparation, test operations, and test data reduction efforts. These timelines also demonstrate how the historical tests fit within their overall vehicle development programs. Finally, the study was able to quantify approximate staffing levels during historic development programs. Using this study, the Flight and Integrated Test Office was able to evaluate the Ares I Integrated Vehicle Ground Vibration Test schedule and workforce budgets in light of the historical precedents to determine if the test had schedule or cost risks associated with it.

Lemke, Paul R.↗

Operational Lessons Learned from the Ares I-X Flight Test

The Ares I-X flight test, launched in 2009, is the first test of the Ares I crew launch vehicle. This development flight test evaluated the flight dynamics, roll control, and separation events, but also provided early insights into logistical, stacking, launch, and recovery operations for Ares I. Operational lessons will be especially important for NASA as the agency makes the transition from the Space Shuttle to the Constellation Program, which is designed to be less labor-intensive. The mission team itself comprised only 700 individuals over the life of the project compared to the thousands involved in Shuttle and Apollo missions; while missions to and beyond low-Earth orbit obviously will require additional personnel, this lean approach will serve as a model for future Constellation missions. To prepare for Ares I-X, vehicle stacking and launch infrastructure had to be modified at Kennedy Space Center's Vehicle Assembly Building (VAB) as well as Launch Complex (LC) 39B. In the VAB, several platforms and other structures designed for the Shuttle s configuration had to be removed to accommodate the in-line, much taller Ares I-X. Vehicle preparation activities resulted in delays, but also in lessons learned for ground operations personnel, including hardware deliveries, cable routing, transferred work and custodial paperwork. Ares I-X also proved to be a resource challenge, as individuals and ground service equipment (GSE) supporting the mission also were required for Shuttle or Atlas V operations at LC 40/41 at Cape Canaveral Air Force Station. At LC 39B, several Shuttle-specific access arms were removed and others were added to accommodate the in-line Ares vehicle. Ground command, control, and communication (GC3) hardware was incorporated into the Mobile Launcher Platform (MLP). The lightning protection system at LC 39B was replaced by a trio of 600-foot-tall towers connected by a catenary wire to account for the much greater height of the vehicle. Like Shuttle, Ares I-X will be stacked on a MLP and rolled out to the pad on a Saturn-era crawler-transporter. While Ares I-X was only held in place by the four hold-down posts on its aft skirt during rollout, a new vehicle stabilization system (VSS) attached to the vertical service structure kept the vehicle from undue swaying prior to launch at the pad, LC 39B. Following the launch, the flight test vehicle first stage was recovered with the aid of new parachutes resized to accommodate the five-segment-long first stage, which had a much greater length and mass than the Shuttle s reusable solid rocket boosters. After splashdown, recovery divers exercised extra care when handling the first stage to ensure that the flight data recorders in the fifth segment simulator were not damaged by exposure to sea water. The data recovered from the Ares I-X flight test will be very valuable in verifying the predicted environments and models used to design the vehicle. Lessons learned from Ares I-X will be shared with the Ares Projects through written and verbal reports and through integration of mission team members into the Project workforce.

Davis, Stephan R.↗

Partners in Freedom: Contributions of the Langley Research Center to U.S. Military Aircraft of the 1990's

Established in 1917 as the nation#s first civil aeronautics research laboratory under the National Advisory Commit-tee for Aeronautics (NACA), Langley was a small laboratory that solved the problems of flight for military and civil aviation. Throughout history, Langley has maintained a working partnership with the Department of Defense, U.S. industry, universities, and other government agencies to support the defense of the nation with research. During World War II, Langley directed virtually all of its workforce and facilities to research for military aircraft. Following the war, a balanced program of military and civil projects was undertaken. In some instances Langley research from one aircraft program helped solve a problem in another. At the conclusion of some programs, Langley obtained the research models for additional tests to learn more about previously unknown phenomena. The data also proved useful in later developmental programs. Many of the military aircraft in the U.S. inventory as of late 1999 were over 20 years old. Langley activities that contributed to the development of some of these aircraft began over 50 years prior. This publication documents the role, from early concept stages to problem solving for fleet aircraft, that Langley played in the military aircraft fleet of the United States for the 1990's.

Chambers, Joseph R.↗

Budget estimates: Fiscal year 1994. Volume 3: Research and program management

The research and program management (R&PM) appropriation provides the salaries, other personnel and related costs, and travel support for NASA's civil service workforce. This FY 1994 budget funds costs associated with 23,623 full-time equivalent (FTE) work years. Budget estimates are provided for all NASA centers by categories such as space station and new technology investments, space flight programs, space science, life and microgravity sciences, advanced concepts and technology, center management and operations support, launch services, mission to planet earth, tracking and data programs, aeronautical research and technology, and safety, reliability, and quality assurance.

Source record↗

Creating Portfolio Management Concepts for Highly Agile and Innovative Government Research Programs Using Design Thinking and Lean Startup Methodologies

Managing a research and development (R&D) portfolio presents numerous challenges, such as prioritizing research areas, remaining agile, strategic workforce planning, and measuring return on investment, impact, and innovation. One government R&D program is charged with producing a high degree of innovative, transformational breakthroughs in aviation technology. A practical, structured methodology for strategically prioritizing emerging aviation R&D in such an environment is lacking. The existing multi-criteria decision aid tools are primarily utilized at an enterprise level, take months to set up and collect data, require large teams of experts, are used on an infrequent basis, and are not conducive to a highly innovative, high-risk portfolio. Prior to audaciously creating a new portfolio prioritization process, the exact challenges with portfolio management for R&D projects were identified using the design thinking and lean start-up methods. A key part of this discovery process was interviewing stakeholders, as well as other managers of organizations charged with producing innovative portfolios. These interviews, as well as additional techniques, were used to develop a deeper understanding of the challenges and, subsequently, lay the foundation for development of an effective portfolio prioritization process. Four potential concepts that represent key findings emerged: carefully selected criteria for portfolio assessment and selection, targeted portfolio turnover rate, dynamic portfolio prioritization framework, and streamlined transition or commercialization of R&D. Acting on any one of the resulting portfolio management concepts will increase the transparency and confidence in portfolio decisions and, ideally, result in a greater degree of transformational breakthroughs in aviation technology.

project portfolio management↗

Atmospheric/Space Environment Support Lessons Learned Regarding Aerospace Vehicle Design and Operations

In modern government and aerospace industry institutions the necessity of controlling current year costs often leads to high mobility in the technical workforce, "one-deep" technical capabilities, and minimal mentoring for young engineers. Thus, formal recording, use, and teaching of lessons learned are especially important in the maintenance and improvement of current knowledge and development of new technologies, regardless of the discipline area. Within the NASA Technical Standards Program Website http://standards.nasa.gov there is a menu item entitled "Lessons Learned/Best Practices". It contains links to a large number of engineering and technical disciplines related data sets that contain a wealth of lessons learned information based on past experiences. This paper has provided a small sample of lessons learned relative to the atmospheric and space environment. There are many more whose subsequent applications have improved our knowledge of the atmosphere and space environment, and the application of this knowledge to the engineering and operations for a variety of aerospace programs.

Vaughan, William W.↗

Ares I-X Flight Test Development Challenges and Success Factors

The NASA Constellation Program's Ares I-X rocket launched successfully on October 28, 2009 collecting valuable data and providing risk reduction for the Ares I project. The Ares I-X mission was formulated and implemented in less than four years commencing with the Exploration Systems Architecture Study in 2005. The test configuration was founded upon assets and processes from other rocket programs including Space Shuttle, Atlas, and Peacekeeper. For example, the test vehicle's propulsion element was a Shuttle Solid Rocket Motor. The Ares I-X rocket comprised a motor assembly, mass and outer mold line simulators of the Ares I Upper Stage, Orion Spacecraft and Launch Abort System, a roll control system, avionics, and other miscellaneous components. The vehicle was 327 feet tall and weighed approximately 1,800,000 pounds. During flight the rocket reached a maximum speed of Mach 4.8 and an altitude of 150,000 feet. The vehicle demonstrated staging at 130,000 feet, tested parachutes for recovery of the motor, and utilized approximately 900 sensors for data collection. Developing a new launch system and preparing for a safe flight presented many challenges. Specific challenges included designing a system to withstand the environments, manufacturing large structures, and re-qualifying heritage hardware. These and other challenges, if not mitigated, may have resulted in test cancellation. Ares I-X succeeded because the mission was founded on carefully derived objectives, led by decisive and flexible management, implemented by an exceptionally talented and dedicated workforce, and supported by a thorough independent review team. Other major success factors include the use of proven heritage hardware, a robust System Integration Laboratory, multi-NASA center and contractor team, concurrent operations, efficient vehicle assembly, effective risk management, and decentralized element development with a centralized control board. Ares I-X was a technically complex test that required creative thinking, risk taking, and a passion to succeed.

Askins, Bruce↗

NASA Capacity Building Program Intern Team Findings Final Report

NASA’s Capacity Building Program (CBP) provides individuals and institutions with workforce development, training activities, and collaborative projects to strengthen understanding of Earth observations and expand their use around the world. The team of eight interns set out this summer to work with CBP leadership to explore opportunities & innovations and identify process improvements within the program. For the 10-week summer term, the interns virtually assembled from Washington, Montana, Virginia, Maine, and Puerto Rico to collaborate on this project. The work was divided into four sub-projects: Data Analysis, Communications, Web Development and Strategy.

Grace Finstrom↗

NASA Enterprise Digital Transformation Initiative Strategic Framework & Implementation Approach

Since 1958, NASA has delivered its enduring bold purpose, characterized in the 2022 NASA Strategic Plan as a mission to discover, explore, innovate, and advance solutions to the problems of flight, within and outside the Earth’s atmosphere, for the benefit of humankind. The NASA Strategic Plan also recognizes that this mission will be delivered differently as it looks to a future marked by radical global change, which is in part being driven by digital advances. For this reason, in late 2020 NASA established an Enterprise Digital Transformation (DT) agency-level strategic initiative to accelerate and coordinate leveraging digital advances to transform the way the Agency works, the experience of its workforce and the agility of its workplace. This paper documents NASA’s DT strategic framework and associated implementation approach, with the DT strategic initiative serving to ignite, connect, integrate, and facilitate DT progress across a federated organizational operating model.

digital transformation↗

DEVELOP’s Approach to Experiential Learning

The NASA DEVELOP Program addresses environmental decision making needs and geoscience workforce development through 10-week feasibility studies that apply Earth observations to environmental issues at hand. The program builds capacity to use geospatial information in both its participants (students, recent graduates, early career professionals, and transitioning career professionals) and partner organizations (federal agencies, state & local governments, non-profits, and private industry). This is accomplished through a structured project execution model that provides opportunities for participants to have autonomy, learn “on the job,” and gain new skillsets for working with remote sensing data. A pipeline of leadership positions enhances opportunities for individuals engaged in the program to get hands-on experience conducting data analyses, communicating their work, leading technical projects, and building their knowledge bank of Earth-observing satellite capabilities. These skillsets and knowledge are then transferred to partners through the projects. This panel contribution will introduce the DEVELOP model, highlight experiences of participants, and share the program’s insights into good practices for effective experiential learning.

Capacity Building↗