Search NASA⌕ Search

SEARCH · Search NASA

Results for “Greybeard”

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.

So Easy a Greybeard Can Do It: Mobile Paperless Engineering

Picture a NASA Engineer out at the launch pad - some new construction has been completed, and he has been tasked to inspect the job. While working, he repeatedly travels between the site and his desk, spending time seeking out information, printing out drawings for reference, and attempting to align schedules to meet with the team. This type of scenario is not just specific to Kennedy Space Center though, many industries partake in similar circumstances most realizing that there is always a need for more information, and often at a moments notice. While this approach will eventually get the job done, NASA KSC-ESC has questioned how to use readily available resources to streamline work processes, become more efficient, and produce less waste.

Greybeard↗

COMSAC: Computational Methods for Stability and Control

Work on stability and control included the following reports:Introductory Remarks; Introduction to Computational Methods for Stability and Control (COMSAC); Stability & Control Challenges for COMSAC: a NASA Langley Perspective; Emerging CFD Capabilities and Outlook A NASA Langley Perspective; The Role for Computational Fluid Dynamics for Stability and Control:Is it Time?; Northrop Grumman Perspective on COMSAC; Boeing Integrated Defense Systems Perspective on COMSAC; Computational Methods in Stability and Control:WPAFB Perspective; Perspective: Raytheon Aircraft Company; A Greybeard's View of the State of Aerodynamic Prediction; Computational Methods for Stability and Control: A Perspective; Boeing TacAir Stability and Control Issues for Computational Fluid Dynamics; NAVAIR S&C Issues for CFD; An S&C Perspective on CFD; Issues, Challenges & Payoffs: A Boeing User s Perspective on CFD for S&C; and Stability and Control in Computational Simulations for Conceptual and Preliminary Design: the Past, Today, and Future?

Fremaux, C. Michael↗

Exploring the Science Trade Space with the JPL Innovation Foundry A-Team

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts with a group called the Architecture Team (A-Team). The A-Team combines innovative collaborative methods and facilitated sessions with subject matter experts and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an ATeam study. In these studies, Concept Maturity Levels (CML) are used to group methods. These levels include idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for exploring the science objectives, feasibility, and scope will be described including use of a new technique for understanding the most compelling science, called a Science Return Diagram (SRD). In the process of developing the SRD, gradients in the science trade space are uncovered along with their implications for implementation and mission architecture. Special attention is paid towards developing complete investigations, establishing a series of logical claims that lead to the natural selection of a measurement approach. Over 20 science-focused A-Team studies have used these techniques to help science teams refine their mission objectives, make implementation decisions and reveal the mission concept’s most compelling science. This paper will describe the A-Team process for exploring the mission concept's science trade space and the Science Return Diagram technique.In June of 2011 a new collaborative engineering approach forearly concept formulation began in the JPL InnovationFoundry [1], six months later becoming the “A-Team” [2].Responding to a need for exploring mission architecturelevel trades [3], the A-Team precedes Team X [4,5] in asequence of concurrent engineering teams at JPL that can beused to mature a concept from a “cocktail napkin” level ideato a complete mission point design. The A-Team efficientlyexplores the science, implementation, and programmatictrade space in early concept formulation. Small, facilitatedgroups of experts generate innovative ideas, quantitativelyassess feasibility, and discover key sensitivities in the tradespace through collaborative analysis and use of advancedmethods and tools. The A-Team process builds off theexperience within JPL and other recent approaches to earlyconcept formulation [6] including best practices of the JPLInnovation Foundry, Project Systems Engineering &Formulation Section, Team Eureka and the Rapid MissionArchitecture Team[7].The A-Team is a focal point for innovative formulationapproaches and people within JPL. It relies on a largebackground of study resources, creative thinkers and “greybeard” scrutinizers, advanced tools, and subject matterexperts with both breadth and depth in experience andexpertise that are all available at JPL. The A-Team isdesigned to be a rapid and efficient process takingapproximately 6 weeks (the entire process can be as short asjust a few days or as long as up to three months) and costingthe equivalent of a work-month of a full-time employee orless. Studies begin with detailed planning and client reviewfollowed by study sessions, analysis work, and reporting.The staffing on each study is customized to the study goalsand objectives, and it is addressed early in the A-Teamprocess. Sessions are generally half-day or whole-day eventsand conducted over a series of days with focused agendas thatare moderated by a trained facilitator. Preliminary results andknowledge capture are available within hours of each session,and a final report is generally available two weeks later.One of the biggest challenges facing early conceptdevelopment is understanding the gradient in science returnversus various available mission scenarios and payload options. Often times, major areas of scientific inquiry havealready been prioritized by science groups, including throughthe National Research Council’s Decadal Studies inAstronomy, Planetary, and Earth Science. Yet science teamscontinue to struggle, especially in competitive missionsolicitations, to capture the right amount of scope that’sachievable within the cost constraints of the opportunity.Often the desire to completely and comprehensively study ascience area in just one mission (after all, true missionopportunities are rare) drives teams to take on too much,providing requirements that are unachievable within theresources of the opportunity without inducing unacceptableimplementation risk. Alternatively, science teams can seekto reduce risk by using an established instrument, but havenot thought through the traceability and key aspects of thescience question to justify its use. Both scenarios lead to badassumptions at the beginning of the concept development thatcan then ripple through implementation option choices,potentially preventing what would have been a good scienceinvestigation from being selected.The purpose of this paper is first to provide some additionalbackground and summary of the A-Team process, tools,people, and facilities. We then focus on the A-Teammethodology for overcoming the barriers of defining thescience scope well at the early concept development stage.This includes understanding the science story andtraceability, and then examining the gradient in science returnversus key characteristics of observables, developing theright payload and mission requirement specification throughexamining the science and implementation trade space.

Ziemer, John K.↗