SEARCH · Engineering Papers

Results for “Stakeholders Meeting”

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 19 records

All sources NASA NTRS DOE OSTI

NASA NTRS1994

Certify for success: A methodology for human-centered certification of advanced aviation systems

This position paper uses the methodology in Design for Success as a basis for a human factors certification program. The Design for Success (DFS) methodology espouses a multi-step process to designing and developing systems in a human-centered fashion. These steps are as follows: (1) naturalizing - understand stakeholders and their concerns; (2) marketing - understand market-oriented alternatives to meeting stakeholder concerns; (3) engineering - detailed design and development of the system considering tradeoffs between technology, cost, schedule, certification requirements, etc.; (4) system evaluation - determining if the system meets its goal(s); and (5) sales and service - delivering and maintaining the system. Because the main topic of this paper is certification, we will focus our attention on step 4, System Evaluation, since it is the natural precursor to certification. Evaluation involves testing the system and its parts for their correct behaviors. Certification focuses not only on ensuring that the system exhibits the correct behaviors, but ONLY the correct behaviors.

Small, Ronald L.↗

NASA NTRS2010

Reducing Tick-Borne Disease in Alabama: Linking Health Risk Perception with Spatial Analysis Using the NASA Earth Observing System

Lyme disease (LD) accounts for most vector-borne disease reports in the U.S., and although its existence in Alabama remains controversial, other tick-borne illnesses (TBI) such as Southern Tick-Associated Rash Illness (STARI) pose a health concern in the state. Phase One of the Marshall Space Flight Center-UAB DEVELOP study of TBI identified the presence of the chain of infection for LD (Ixodes scapularis ticks carrying Borrelia burgdorferi bacteria) and STARI (Amblyomma americanum ticks and an as-yet-unconfirmed agent) in Alabama. Both LD and STARI are associated with the development of erythema migrans rashes around an infected tick bite, and while treatable with oral antibiotics, a review of educational resources available to state residents revealed low levels of prevention information. To improve prevention, recognition, and treatment of TBI in Alabama, Phase Two builds a health communication campaign based on vector habitat mapping and risk perception assessment. NASA Advanced Spaceborne Thermal Emission and Reflection Radiometer (ASTER) satellite imagery identified likely tick habitats using remotely sensed measurements of vegetation vigor (Normalized Difference Vegetation Index) and soil moisture. Likely tick habitats, identified as those containing both high vegetation density and soil moisture, included Oak Mountain State Park, Bankhead National Forest, and Talladega National Forest. To target a high-risk group -- outdoor recreation program participants at Alabama universities -- the study developed a behavior survey instrument based on existing studies of LD risk factors and theoretical constructs from the Social Ecological Model and Health Belief Model. The survey instrument was amended to include geographic variables in the assessment of TBI knowledge, attitudes, and prevention behaviors, and the vector habitat model will be expanded to incorporate additional environmental variables and in situ data. Remotely sensed environmental data combined with risk perception assessments inform an ongoing outreach campaign consisting of stakeholder meetings and educational seminars.

Hemmings, S.↗

NASA NTRS2012

The Role of Cis-Lunar Space in Future Global Space Exploration

Cis-lunar space offers affordable near-term opportunities to help pave the way for future global human exploration of deep space, acting as a bridge between present missions and future deep space missions. While missions in cis-lunar space have value unto themselves, they can also play an important role in enabling and reducing risk for future human missions to the Moon, Near-Earth Asteroids (NEAs), Mars, and other deep space destinations. The Cis-Lunar Destination Team of NASA's Human Spaceflight Architecture Team (HAT) has been analyzing cis-lunar destination activities and developing notional missions (or "destination Design Reference Missions" [DRMs]) for cis-lunar locations to inform roadmap and architecture development, transportation and destination elements definition, operations, and strategic knowledge gaps. The cis-lunar domain is defined as that area of deep space under the gravitational influence of the earth-moon system. This includes a set of earth-centered orbital locations in low earth orbit (LEO), geosynchronous earth orbit (GEO), highly elliptical and high earth orbits (HEO), earth-moon libration or "Lagrange" points (E-ML1 through E-ML5, and in particular, E-ML1 and E-ML2), and low lunar orbit (LLO). To help explore this large possibility space, we developed a set of high level cis-lunar mission concepts in the form of a large mission tree, defined primarily by mission duration, pre-deployment, type of mission, and location. The mission tree has provided an overall analytical context and has helped in developing more detailed design reference missions that are then intended to inform capabilities, operations, and architectures. With the mission tree as context, we will describe two destination DRMs to LEO and GEO, based on present human space exploration architectural considerations, as well as our recent work on defining mission activities that could be conducted with an EML1 or EML2 facility, the latter of which will be an emphasis of this paper, motivated in part by recent interest expressed at the Global Exploration Roadmap Stakeholder meeting. This paper will also explore the links between this HAT Cis-Lunar Destination Team analysis and the recently released ISECG Global Exploration Roadmap and other potential international considerations, such as preventing harmful interference to radio astronomy observations in the shielded zone of the moon.

Bobskill, Marianne R.↗

NASA NTRS2016

International Space Station Configuration Analysis and Integration

Ambitious engineering projects, such as NASA's International Space Station (ISS), require dependable modeling, analysis, visualization, and robotics to ensure that complex mission strategies are carried out cost effectively, sustainably, and safely. Learn how Booz Allen Hamilton's Modeling, Analysis, Visualization, and Robotics Integration Center (MAVRIC) team performs engineering analysis of the ISS Configuration based primarily on the use of 3D CAD models. To support mission planning and execution, the team tracks the configuration of ISS and maintains configuration requirements to ensure operational goals are met. The MAVRIC team performs multi-disciplinary integration and trade studies to ensure future configurations meet stakeholder needs.

Anchondo, Rebekah↗

NASA NTRS2016

Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)

The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.

Vipavetz, Kevin↗

NASA NTRS2016

An Integrated Gate Turnaround Management Concept Leveraging Big Data/Analytics for NAS Performance Improvements

The Integrated Gate Turnaround Management (IGTM) concept was developed to improve the gate turnaround performance at the airport by leveraging relevant historical data to support optimization of airport gate operations, which include: taxi to the gate, gate services, push back, taxi to the runway, and takeoff, based on available resources, constraints, and uncertainties. By analyzing events of gate operations, primary performance dependent attributes of these events were identified for the historical data analysis such that performance models can be developed based on uncertainties to support descriptive, predictive, and prescriptive functions. A system architecture was developed to examine system requirements in support of such a concept. An IGTM prototype was developed to demonstrate the concept using a distributed network and collaborative decision tools for stakeholders to meet on time pushback performance under uncertainties.

Big Data and Net-enabled ATM↗

NASA NTRS2017

GC13I-0857: Designing a Frost Forecasting Service for Small Scale Tea Farmers in East Africa

Kenya is the third largest tea exporter in the world, producing 10% of the world's black tea. Sixty percent of this production occurs largely by small scale tea holders, with an average farm size of 1.04 acres, and an annual net income of $1,075. According to a recent evaluation, a typical frost event in the tea growing region causes about $200 dollars in losses which can be catastrophic for a small holder farm. A 72-hour frost forecast would provide these small-scale tea farmers with enough notice to reduce losses by approximately 80 USD annually. With this knowledge, SERVIR, a joint NASA-USAID initiative that brings Earth observations for improved decision making in developing countries, sought to design a frost monitoring and forecasting service that would provide farmers with enough lead time to react to and protect against a forecasted frost occurrence on their farm. SERVIR Eastern and Southern Africa, through its implementing partner, the Regional Centre for Mapping of Resources for Development (RCMRD), designed a service that included multiple stakeholder engagement events whereby stakeholders from the tea industry value chain were invited to share their experiences so that the exact needs and flow of information could be identified. This unique event allowed enabled the design of a service that fit the specifications of the stakeholders. The monitoring service component uses the MODIS Land Surface Temperature product to identify frost occurrences in near-real time. The prediction component, currently under testing, uses the 2-m air temperature, relative humidity, and 10-m wind speed from a series of high-resolution Weather Research and Forecasting (WRF) numerical weather prediction model runs over eastern Kenya as inputs into a frost prediction algorithm. Accuracy and sensitivity of the algorithm is being assessed with observations collected from the farmers using a smart phone app developed specifically to report frost occurrences, and from data shared through our partner network developed at the stakeholder engagement meeting. This presentation will illustrate the efficacy of our frost forecasting algorithm, and a way forward for incorporating these forecasts in a meaningful way to the key decision makers - the small-scale farmers of East Africa.

frost↗

NASA NTRS2019

Space Technology Mission Directorate Game Changing Development Program Astrobee

The HET2/Astrobee project is developing a new free-flying robot to succeed the existing SPHERES facility as a guest science research platform and to perform IVA work on the ISS. Relevance: The project will increase the capabilities of robots to perform IVA/EVA work in space and will increase the efficiency of human explorers by allowing routine, repetitive work to be off-loaded to robots. Approach: The project conducted incremental design and development of a robotic free flyer that meets project, stakeholder, and ISS interface and safety requirements. Results: 3 free flyers are on-orbit. The first robot has been unpacked and has begun flying autonomously within the ISS under crew supervision. Commissioning activities to validate the system continue.

Astrobee↗

NASA NTRS2019

The Value of Being a Trustworthy Repository

Today, NASA's Earth Observing System Data and Information System (EOSDIS), a system ofactive archives is attaching the CoreTrustSeal to its websites signifying that it merits theconfidence of its user community. But what value does being a trustworthy repository impart to auser? What does it mean to the owners and operators of repositories? What will it mean in thefuture? EOSDIS was started in the 1990s based on a framework of discipline-oriented, geographicallydistributed centers of expertise, named Distributed Active Archive Centers (DAACs). The functionof EOSDIS is to collect Earth Science data sensor measurements (principally those created andneeded by NASA) and manage the data and many derived digital products. EOSDIS providesmany services, including processing, curating, documenting, disseminating, and enabling datadiscovery as well as efficient use of the data. The EOSDIS has been operational over 25 years andmany lessons have been learned relative to the TRUST principles. During the tenure of EOSDIS,many changes have occurred as we have increased the size of the collection from gigabytes totens of petabytes and the distribution of the data to millions of users. We have had severalstages of system evolution that have improved EOSDIS in order to meet both stakeholder andcustomer expectations. This type of evolution is an on-going process to ensure that ourrepositories remain trustworthy. It is also important that our own community of data managersand system engineers add value in being trustworthy. This paper will discuss approaches to change within a large system of Earth Science data and services, while remaining a trustworthyrepository.

Behnke, Jeanne↗

NASA NTRSDate not supplied

Activities of the NASA Urban Air Mobility Noise Working Group (UNWG)

The NASA-led Urban Air Mobility Noise Working Group was established in 2018 following an exploratory meeting of stakeholders from traditional and emerging aviation sectors across industry, government agencies, academia, and community groups. Its mission is to create and support a diverse community of acoustics experts to identify, discuss, and address noise issues associated with UAM vehicles and their operations. The UNWG is comprised of four subgroups including Tools and Technologies, Ground and Flight Testing, Human Response and Metrics, and Regulation and Policy. In 2020, NASA published the white paper entitled “Urban Air Mobility Noise: Current Practice, Gaps, and Recommendations,” that presents a set of high-level goals and makes recommendations to address gaps in the current practice. This presentation is about recent activities of each of the subgroups to address those recommendations, including work towards establishment of an aeroacoustic test database for model validation, development of a set of measurement guidelines to quantify vehicle acoustic emission, a remotely administered human response study for quantifying annoyance to UAM operations, and status on noise standard, regulation, policy, and community engagement developments.

Urban air mobility↗

NASA NTRS2023

Information and Best Practices Related to NASA Nuclear Flight Safety for Space Flights Involving Space Nuclear Systems

The purpose of this handbook is to facilitate a repeatable and robust process that promotes clear and effective interfaces between activities and stakeholders focused on meeting nuclear flight safety requirements for missions utilizing space nuclear systems (SNS), within the context of NASA’s broader nuclear-related activities and interfaces. NPR 8715.26, Nuclear Flight Safety, requires that the NASA project manager “incorporate nuclear flight safety considerations starting with program or project formulation through the point at which the SNS or other radioactive material no longer has the potential to affect Earth’s biosphere.” NASA’s use of SNS inherently involves partnering with other stakeholders to conduct a range of related activities that interface with nuclear flight safety. From a categorical perspective these include: (i) meeting the authorities and licensing requirements for possession and use of nuclear material, as governed by other Federal authorities; (ii) conducting National Environmental Policy Act (NEPA) activities for nuclear-enabled missions; (iii) meeting Federal nuclear launch authorization requirements; (iv) conducting radiological contingency planning activities, including those associated with international commitments; (v) performing risk communication and public outreach activities; and (vi) ensuring decommissioning and disposal strategies reflect National policies and interests. It is the intent of this handbook to promote an effective interface between nuclear flight safety and these interrelated categorical activities. In addition to activities undertaken with partnering agencies, there are individual nuclear-related activities and programs that have a nexus to nuclear flight safety, and these include: (i) applicable NASA Standing Review Boards; (ii) the US Department of Energy nuclear safety activities conducted in partnership with NASA under Memoranda of Understanding; (iii) the Department of Defense’s Range Safety activities; (iv) NASA’s general involvement in interagency and international dialogues regarding nuclear safety; (v) the NASA-administered Interagency Nuclear Safety Review Board; (vi) NASA’s program and project governance activities and nuclear-specific Technical Discipline Team activities under the Office of the Chief Engineer; and others. It is the intent of this handbook to promote effective leveraging of these additional interrelated organizational activities, as appropriate.

Donald Helton↗

NASA NTRS2006

NASA Exploration Launch Projects Overview: The Crew Launch Vehicle and the Cargo Launch Vehicle Systems

The U.S. Vision for Space Exploration (January 2004) serves as the foundation for the National Aeronautics and Space Administration's (NASA) strategic goals and objectives. As the NASA Administrator outlined during his confirmation hearing in April 2005, these include: 1) Flying the Space Shuttle as safely as possible until its retirement, not later than 2010. 2) Bringing a new Crew Exploration Vehicle (CEV) into service as soon as possible after Shuttle retirement. 3) Developing a balanced overall program of science, exploration, and aeronautics at NASA, consistent with the redirection of the human space flight program to focus on exploration. 4) Completing the International Space Station (ISS) in a manner consistent with international partner commitments and the needs of human exploration. 5) Encouraging the pursuit of appropriate partnerships with the emerging commercial space sector. 6) Establishing a lunar return program having the maximum possible utility for later missions to Mars and other destinations. In spring 2005, the Agency commissioned a team of aerospace subject matter experts to perform the Exploration Systems Architecture Study (ESAS). The ESAS team performed in-depth evaluations of a number of space transportation architectures and provided recommendations based on their findings? The ESAS analysis focused on a human-rated Crew Launch Vehicle (CLV) for astronaut transport and a heavy lift Cargo Launch Vehicle (CaLV) to carry equipment, materials, and supplies for lunar missions and, later, the first human journeys to Mars. After several months of intense study utilizing safety and reliability, technical performance, budget, and schedule figures of merit in relation to design reference missions, the ESAS design options were unveiled in summer 2005. As part of NASA's systems engineering approach, these point of departure architectures have been refined through trade studies during the ongoing design phase leading to the development phase that begins in 2008. Comprehensive reviews of engineering data and business assessments by both internal and independent reviewers serve as decision gates to ensure that systems can fully meet customer and stakeholder requirements. This paper provides the current CLV and CaLV configuration designs and gives examples of the progress being made during the first year of this significant effort. Safe, reliable, cost-effective space transportation systems are a foundational piece of America s future in space and the next step in realizing the plan for revitalizing lunar capabilities on the passageway to the human exploration of Mars. While building on legacy knowledge and heritage hardware for risk reduction, NASA will apply lessons learned from developing these new launch vehicles to the growth path for future missions. The elements for mission success and continued U.S. leadership in space have been assembled over the past year. As NASA designs and develops these two new systems over the next dozen years, visible progress, such as that reported in this paper, may sustain the national will to stay the course across political administrations and weather the inevitable trials that will be experienced during this challenging endeavor.

Snoddy, Jimmy R.↗

NASA NTRS2007

From ESAS to Ares: A Chronology

Throughout my career, I have observed many launch vehicle efforts come and go. Although it may appear on the surface that those were dead-end streets, the knowledge we gained through them actually informs the work in progress. Following the tragic loss of the Space Shuttle Columbia's crew, the administration took the Columbia Accident Investigation Board's findings to heart and united the Agency behind the Vision for Space Exploration, with clear goals and objectives, including fielding a new generation of safe, reliable, and affordable space transportation. The genesis of the Ares I Crew Launch Vehicle and Ares V Cargo Launch Vehicle activities now under way by a nationwide Government and industry team was the confirmation of the current NASA Administrator in April 2005. Shortly thereafter, he commissioned a team of aerospace experts to conduct the Exploration Systems Architecture Study (ESAS), which gave shape to launch vehicles that will empower America's resurgence in scientific discovery through human and robotic space exploration. In October 2005, I was asked to lead this effort, building the team and forming the partnerships that will, in turn, build America's next human-rated space transportation system. In November 2006, the Ares I team began conducting the System Requirements Review milestone, just 1 year after its formation. We are gaining momentum toward the first test flight of the integrated vehicle system in 2009, just a few short years away. The Agency is now poised to deliver on the commitment this nation has made to advance our interests in space. In its inaugural year, the Ares team has conducted the first human-rated launch vehicle major milestone in over 30 years. Using the Exploration Systems Architecture Study recommendations as a starting point, the vehicle designs have been evolved to best meet customer and stakeholder requirements to fulfill the strategic goals outlined in the Vision for Space Exploration.

Cook, Stephen A.↗

NASA NTRS2005

Communicating Risk to Program Managers

Program Managers (PM) can protect program resources and improve chances of success by anticipating, understanding and managing risks. Understanding the range of potential risks helps one to avoid or manage the risks. A PM must choose which risks to accept to reduce fire fighting, must meet the expectations of stakeholders consistently, and avoid falling into costly "black holes" that may open. A good risk management process provides the PM more confidence to seize opportunities save money, meet schedule, even improve relationships with people important to the program. Evidence of managing risk and sound internal controls can mean better support from superiors for the program by building a trust and reputation from being on top of issues. Risk managers have an obligation to provide the PM with the best information possible to allow the benefits to be realized (Small Business Consortium, 2004). The Institute for Chartered Accountants in England and Wales sees very important benefits for companies in providing better information about what they do to assess and manage key business risks. Such information will: a) provide practical forward-looking information; b) reduce the cost of capital; c) encourage better risk management; and d) improve accountability for stewardship, investor protection and the usefulness of financial reporting. We are particularly convinced that enhanced risk reporting will help listed companies obtain capital at the lowest possible cost (The Institute of Chartered Accountants in England &Wales, June 2002). Risk managers can take a significant role in quantifying the success of their department and communicating those figures to executive (program) management levels while pushing for a broader risk management role. Overall, risk managers must show that risk management work matters in the most crucial place-the bottom line- as they prove risk management can be a profit center (Sullivan, 2004).

Shivers, C. Herbert↗

NASA NTRS2009

Review of the Constellation Level II Safety, Reliability, and Quality Assurance (SR&QA) Requirements Documents during Participation in the Constellation Level II SR&QA Forum

At the request of the Exploration Systems Mission Directorate (ESMD) and the Constellation Program (CxP) Safety, Reliability; and Quality Assurance (SR&QA) Requirements Director, the NASA Engineering and Safety Center (NESC) participated in the Cx SR&QA Requirements forum. The Requirements Forum was held June 24-26; 2008, at GRC's Plum Brook Facility. The forums purpose was to gather all stakeholders into a focused meeting to help complete the process of refining the CxP to refine its Level II SR&QA requirements or defining project-specific requirements tailoring. Element prime contractors had raised specific questions about the wording and intent of many requirements in areas they felt were driving costs without adding commensurate value. NESC was asked to provide an independent and thorough review of requirements that contractors believed were driving Program costs, by active participation in the forum. This document contains information from the forum.

Cameron, Kenneth D.↗

NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Lessons Learned↗

NASA NTRS2013

Human-in-the-Loop Operations over Time Delay: NASA Analog Missions Lessons Learned

Teams at NASA have conducted studies of time-delayed communications as it effects human exploration. In October 2012, the Advanced Exploration Systems (AES) Analog Missions project conducted a Technical Interchange Meeting (TIM) with the primary stakeholders to share information and experiences of studying time delay, to build a coherent picture of how studies are covering the problem domain, and to determine possible forward plans (including how to best communicate study results and lessons learned, how to inform future studies and mission plans, and how to drive potential development efforts). This initial meeting s participants included personnel from multiple NASA centers (HQ, JSC, KSC, ARC, and JPL), academia, and ESA. It included all of the known studies, analog missions, and tests of time delayed communications dating back to the Apollo missions including NASA Extreme Environment Mission Operations (NEEMO), Desert Research and Technology Studies (DRATS/RATS), International Space Station Test-bed for Analog Research (ISTAR), Pavilion Lake Research Project (PLRP), Mars 520, JPL Mars Orbiters/Rovers, Advanced Mission Operations (AMO), Devon Island analog missions, and Apollo experiences. Additionally, the meeting attempted to capture all of the various functional perspectives via presentations by disciplines including mission operations (flight director and mission planning), communications, crew, Capcom, Extra-Vehicular Activity (EVA), Behavioral Health and Performance (BHP), Medical/Surgeon, Science, Education and Public Outreach (EPO), and data management. The paper summarizes the descriptions and results from each of the activities discussed at the TIM and includes several recommendations captured in the meeting for dealing with time delay in human exploration along with recommendations for future development and studies to address this issue.

Rader, Steven N.↗