Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “team”

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 1,495 records · Page 83

Integration and Testing Challenges of Small Satellite Missions: Experiences from the Space Technology 5 Project

The Space Technology 5(ST5) payload was successfully carried into orbit on an OSC Pegasus XL launch vehicle, which was carried aloft and dropped from the OSC Lockheed L-1011 from Vandenberg Air Force Base March 22,2006, at 9:03 am Eastern time, 6:03 am Pacific time. In order to reach the completion of the development and successful launch of ST 5, the systems integration and test(I&T) team determined that a different approach was required to meet the project requirements rather than the standard I&T approach used for single, room-sized satellites. The ST5 payload, part of NASA's New Millennium Program headquartered at JPL, consisted of three micro satellites (approximately 30 kg each) and the Pegasus Support Structure (PSS), the system that connected the spacecrafts to the launch vehicle and deployed the spacecrafts into orbit from the Pegasus XL launch vehicle. ST5 was a technology demonstration payload, intended to test six (6) new technologies for potential use for future space flights along with demonstrating the ability of small satellites to perform quality science. The main technology was a science grade magnetometer designed to take measurements of the earth's magnetic field. The three spacecraft were designed, integrated, and tested at NASA Goddard Space Flight Center with integration and environmental testing occurring in the Bldg. 7-1 0-15-29. The three spacecraft were integrated and tested by the same I&T team. The I&T Manager determined that there was insufficient time in the schedule to perform the three I&T spacecraft activities in series used standard approaches. The solution was for spacecraft #1 to undergo integration and test first, followed by spacecraft #2 and #3 simultaneously. This simultaneous integration was successful for several reasons. Each spacecraft had a Lead Test Conductor who planned and coordinated their spacecraft through its integration and test activities. One team of engineers and technicians executed the integration of all three spacecraft, learning and gaining knowledge and efficiency as spacecraft #1 integration and testing progressed. They became acutely familiar with the hardware, operation and processes for I&T, thus each team member had the experience and knowledge to safely execute I&T for spacecraft #2 and #3 together. The integration team was very versatile and each member could perform many different activities or work any spacecraft, when needed. Daily meetings between the three Lead TCs and technician team allowed the team to plan and implement activities efficiently. The three (3) spacecraft and PSS were successfully integrated and tested, shipped to the launch site, and ready for launch per the I&T schedule that was planned three years previously.

Sauerwein, Timothy A.↗

Production and Distribution of NASA MODIS Remote Sensing Products

The two Moderate Resolution Imaging Spectroradiometer (MODIS) instruments on-board NASA's Earth Observing System (EOS) Terra and Aqua satellites make key measurements for understanding the Earth's terrestrial ecosystems. Global time-series of terrestrial geophysical parameters have been produced from MODIS/Terra for over 7 years and for MODIS/Aqua for more than 4 1/2 years. These well calibrated instruments, a team of scientists and a large data production, archive and distribution systems have allowed for the development of a new suite of high quality product variables at spatial resolutions as fine as 250m in support of global change research and natural resource applications. This talk describes the MODIS Science team's products, with a focus on the terrestrial (land) products, the data processing approach and the process for monitoring and improving the product quality. The original MODIS science team was formed in 1989. The team's primary role is the development and implementation of the geophysical algorithms. In addition, the team provided feedback on the design and pre-launch testing of the instrument and helped guide the development of the data processing system. The key challenges the science team dealt with before launch were the development of algorithms for a new instrument and provide guidance of the large and complex multi-discipline processing system. Land, Ocean and Atmosphere discipline teams drove the processing system requirements, particularly in the area of the processing loads and volumes needed to daily produce geophysical maps of the Earth at resolutions as fine as 250 m. The processing system had to handle a large number of data products, large data volumes and processing loads, and complex processing requirements. Prior to MODIS, daily global maps from heritage instruments, such as Advanced Very High Resolution Radiometer (AVHRR), were not produced at resolutions finer than 5 km. The processing solution evolved into a combination of processing the lower level (Level 1) products and the higher level discipline specific Land and Atmosphere products in the MODIS Science Investigator Lead Processing System (SIPS), the MODIS Adaptive Processing System (MODAPS), and archive and distribution of the Land products to the user community by two of NASA s EOS Distributed Active Archive Centers (DAACs). Recently, a part of MODAPS, the Level 1 and Atmosphere Archive and Distribution System (LAADS), took over the role of archiving and distributing the Level 1 and Atmosphere products to the user community.

Wolfe, Robert↗

Extreme Programming: Maestro Style

"Extreme Programming: Maestro Style" is the name of a computer programming methodology that has evolved as a custom version of a methodology, called extreme programming that has been practiced in the software industry since the late 1990s. The name of this version reflects its origin in the work of the Maestro team at NASA's Jet Propulsion Laboratory that develops software for Mars exploration missions. Extreme programming is oriented toward agile development of software resting on values of simplicity, communication, testing, and aggressiveness. Extreme programming involves use of methods of rapidly building and disseminating institutional knowledge among members of a computer-programming team to give all the members a shared view that matches the view of the customers for whom the software system is to be developed. Extreme programming includes frequent planning by programmers in collaboration with customers, continually examining and rewriting code in striving for the simplest workable software designs, a system metaphor (basically, an abstraction of the system that provides easy-to-remember software-naming conventions and insight into the architecture of the system), programmers working in pairs, adherence to a set of coding standards, collaboration of customers and programmers, frequent verbal communication, frequent releases of software in small increments of development, repeated testing of the developmental software by both programmers and customers, and continuous interaction between the team and the customers. The environment in which the Maestro team works requires the team to quickly adapt to changing needs of its customers. In addition, the team cannot afford to accept unnecessary development risk. Extreme programming enables the Maestro team to remain agile and provide high-quality software and service to its customers. However, several factors in the Maestro environment have made it necessary to modify some of the conventional extreme-programming practices. The single most influential of these factors is that continuous interaction between customers and programmers is not feasible.

Norris, Jeffrey↗

Human Factors in Training - Space Flight Resource Management Training

Accidents and incidents show that high workload-induced stress and poor teamwork skills lead to performance decrements and errors. Research on teamwork shows that effective teams are able to adapt to stressful situations, and to reduce workload by using successful strategies for communication and decision making, and through dynamic redistribution of tasks among team members. Furthermore, superior teams are able to recognize signs and symptoms of workload-induced stress early, and to adapt their coordination and communication strategies to the high workload, or stress conditions. Mission Control Center (MCC) teams often face demanding situations in which they must operate as an effective team to solve problems with crew and vehicle during onorbit operations. To be successful as a team, flight controllers (FCers) must learn effective teamwork strategies. Such strategies are the focus of Space Flight Resource Management (SFRM) training. SFRM training in MOD has been structured to include some classroom presentations of basic concepts and case studies, with the assumption that skill development happens in mission simulation. Integrated mission simulations do provide excellent opportunities for FCers to practice teamwork, but also require extensive technical knowledge of vehicle systems, mission operations, and crew actions. Such technical knowledge requires lengthy training. When SFRM training is relegated to integrated simulations, FCers can only practice SFRM after they have already mastered the technical knowledge necessary for these simulations. Given the centrality of teamwork to the success of MCC, holding SFRM training till late in the flow is inefficient. But to be able to train SFRM earlier in the flow, the training cannot rely on extensive mission-specific technical knowledge. Hence, the need for a generic SFRM training framework that would allow FCers to develop basic teamwork skills which are mission relevant, but without the required mission knowledge. Work on SFRM training has been conducted in collaboration with the Expedition Vehicle Division at the Mission Operations Directorate (MOD) and with United Space Alliance (USA) which provides training to Flight Controllers. The space flight resource management training work is part of the Human Factors in Training Directed Research Project (DRP) of the Space Human Factors Engineering (SHFE) Project under the Space Human Factors and Habitability (SHFH) Element of the Human Research Program (HRP). Human factors researchers at the Ames Research Center have been investigating team work and distributed decision making processes to develop a generic SFRM training framework for flight controllers. The work proposed for FY10 continues to build on this strong collaboration with MOD and the USA Training Group as well as previous research in relevant domains such as aviation. In FY10, the work focuses on documenting and analyzing problem solving strategies and decision making processes used in MCC by experienced FCers.

Bryne, Vicky↗

Toolsets Maintain Health of Complex Systems

First featured in Spinoff 2001, Qualtech Systems Inc. (QSI), of Wethersfield, Connecticut, adapted its Testability, Engineering, and Maintenance System (TEAMS) toolset under Small Business Innovation Research (SBIR) contracts from Ames Research Center to strengthen NASA's systems health management approach for its large, complex, and interconnected systems. Today, six NASA field centers utilize the TEAMS toolset, including TEAMS-Designer, TEAMS-RT, TEAMATE, and TEAMS-RDS. TEAMS is also being used on industrial systems that generate power, carry data, refine chemicals, perform medical functions, and produce semiconductor wafers. QSI finds TEAMS can lower costs by decreasing problems requiring service by 30 to 50 percent.

Source record↗

Habitat Demonstration Unit Project: Leadership and Management Strategies for a Rapid Prototyping Project

This paper gives an overview of the National Aeronautics and Space Administration (NASA) led multi-center Habitat Demonstration Unit (HDU) project leadership and management strategies being used by the NASA HDU team for a rapid prototyping project. The HDU project team constructed and tested an analog prototype lunar surface habitat/laboratory called the Pressurized Excursion Module (PEM) during 2010. The prototype unit subsystems were integrated in a short amount of time, utilizing a tiger team rapid prototyping approach that brought together over 20 habitation-related technologies and innovations from a variety of NASA centers. This paper describes the leadership and management strategies as well as lessons learned pertaining to leading and managing a multi-center diverse team in a rapid prototype environment. The PEM configuration went from a paper design to an operational surface habitat demonstration unit in less than 12 months. The HDU project is part of the strategic plan from the Exploration Systems Mission Directorate (ESMD) Directorate Integration Office (DIO) and the Exploration Mission Systems Office (EMSO) to test destination elements in analog environments. The 2011 HDU-Deep Space Habitat (DSH) configuration will build upon the PEM work, and emphasize validity of crew operations (remote working and living), EVA operations, mission operations, logistics operations, and science operations that might be required in a deep space context for Near Earth Object (NEO) exploration mission architectures. The 2011 HDU-DSH will be field-tested during the 2011 Desert Research and Technologies Studies (DRaTS) field tests. The HDU project is a "technology-pull" project that integrates technologies and innovations from multiple NASA centers. This project will repurpose the HDU 2010 demo unit that was field tested in the 2010 DRaTS, adding habitation functionality to the prototype unit. This paper will describe the strategy of establishing a multi-center project management team that put in place the key multi-center leadership skills and disciplines to enable a successful tiger team approach. Advocacy was established with key stakeholders and NASA Headquarters (HQ) by defining a strategic vision, mission, goals and objectives for the project and team. As a technology-pull testbed capability the HDU project was able to collaborate and leverage the Exploration Technology Development Program (ETDP) and individual NASA center investments which capitalized on their respective center core competencies and skills. This approach enable the leveraging of over $7.5m of value to create an operational habitat demonstration unit 2010 PEM configuration.

Kennedy, Kriss J.↗

The Reconstruction and Failure Analysis of the Space Shuttle Columbia

Several days following the Columbia accident a team formed and began planning for the reconstruction of Columbia. A hangar at the Kennedy Space Center was selected for this effort due to it's size, available technical workforce and materials science laboratories and access to the vehicle ground processing infrastructure. The Reconstruction team established processes for receiving, handling, decontamination, tracking, identifying, cleaning and assessment of the debris. Initially, a 2-dimensional reconstruction of the Orbiter outer mold line was developed. As the investigation progressed fixtures which allowed a 3-dimensional reconstruction of the forward portions of the left wing's leading edge was developed. To support the reconstructions and forensic analyses a Materials and Processes (M&P) 'team was formed. This M&P team established processes for recording factual observations, debris cleaning, and engineering analysis. Fracture surfaces and thermal effects of selected airframe debris were assessed, and process flows for both nondestructive and destructive sampling and evaluation of debris were developed. The Team also assessed left hand airframe components that were believed to be associated with a structural breach of Columbia. A major portion of this analysis was evaluation of metallic deposits were prevalent on left wing leading edge components. Extensive evaluation of the visual, metallurgical and chemical nature of the deposits provided conclusions that were consistent with the visual assessments and interpretations of the NASA lead teams and the findings of the Columbia Accident Investigation Board. Analytical data collected by the M&P Team showed that a significant thermal event occurred at the left wing leading edge in the proximity of LH RCC Panels 8-9, and a correlation was formed between the deposits and overheating in these areas to the wing leading edge components. The analysis of deposits also showed exposure to temperatures in excess of 1649 C (3200 F), which would severely degrade support structure, tiles, and RCC panel materials. The integrated failure analysis of wing leading edge debris and deposits strongly supported the hypothesis that a breach occurred at LH RCC Panel 8.

Russell, Richard↗

Kalman Filter for Calibrating a Telescope Focal Plane

The instrument-pointing frame (IPF) Kalman filter, and an algorithm that implements this filter, have been devised for calibrating the focal plane of a telescope. As used here, calibration signifies, more specifically, a combination of measurements and calculations directed toward ensuring accuracy in aiming the telescope and determining the locations of objects imaged in various arrays of photodetectors in instruments located on the focal plane. The IPF Kalman filter was originally intended for application to a spaceborne infrared astronomical telescope, but can also be applied to other spaceborne and ground-based telescopes. In the traditional approach to calibration of a telescope, (1) one team of experts concentrates on estimating parameters (e.g., pointing alignments and gyroscope drifts) that are classified as being of primarily an engineering nature, (2) another team of experts concentrates on estimating calibration parameters (e.g., plate scales and optical distortions) that are classified as being primarily of a scientific nature, and (3) the two teams repeatedly exchange data in an iterative process in which each team refines its estimates with the help of the data provided by the other team. This iterative process is inefficient and uneconomical because it is time-consuming and entails the maintenance of two survey teams and the development of computer programs specific to the requirements of each team. Moreover, theoretical analysis reveals that the engineering/ science iterative approach is not optimal in that it does not yield the best estimates of focal-plane parameters and, depending on the application, may not even enable convergence toward a set of estimates.

Kang, Bryan↗

NASA Planning for Orion Multi-Purpose Crew Vehicle Ground Operations

The NASA Orion Ground Processing Team was originally formed by the Kennedy Space Center (KSC) Constellation (Cx) Project Office's Orion Division to define, refine and mature pre-launch and post-landing ground operations for the Orion human spacecraft. The multidisciplined KSC Orion team consisted of KSC civil servant, SAIC, Productivity Apex, Inc. and Boeing-CAPPS engineers, project managers and safety engineers, as well as engineers from Constellation's Orion Project and Lockheed Martin Orion Prime contractor. The team evaluated the Orion design configurations as the spacecraft concept matured between Systems Design Review (SDR), Systems Requirement Review (SRR) and Preliminary Design Review (PDR). The team functionally decomposed prelaunch and post-landing steps at three levels' of detail, or tiers, beginning with functional flow block diagrams (FFBDs). The third tier FFBDs were used to build logic networks and nominal timelines. Orion ground support equipment (GSE) was identified and mapped to each step. This information was subsequently used in developing lower level operations steps in a Ground Operations Planning Document PDR product. Subject matter experts for each spacecraft and GSE subsystem were used to define 5th - 95th percentile processing times for each FFBD step, using the Delphi Method. Discrete event simulations used this information and the logic network to provide processing timeline confidence intervals for launch rate assessments. The team also used the capabilities of the KSC Visualization Lab, the FFBDs and knowledge of the spacecraft, GSE and facilities to build visualizations of Orion pre-launch and postlanding processing at KSC. Visualizations were a powerful tool for communicating planned operations within the KSC community (i.e., Ground Systems design team), and externally to the Orion Project, Lockheed Martin spacecraft designers and other Constellation Program stakeholders during the SRR to PDR timeframe. Other operations planning tools included Kaizen/Lean events, mockups and human factors analysis. The majority of products developed by this team are applicable as KSC prepares 21st Century Ground Systems for the Orion Multi-Purpose Crew Vehicle and Space Launch System.

Letchworth, Gary↗

Use of VIIRS DNB Data to Monitor Power Outages and Restoration for Significant Weather Events

NASA fs Short-term Prediction Research and Transition (SPoRT) project operates from NASA's Marshall Space Flight Center in Huntsville, Alabama. The team provides unique satellite data to the National Weather Service (NWS) and other agencies and organizations for weather analysis. While much of its work is focused on improving short-term weather forecasting, the SPoRT team supported damage assessment and response to Hurricane Superstorm Sandy by providing imagery that highlighted regions without power. The team used data from the Visible Infrared Imaging Radiometer Suite (VIIRS) on the Suomi National Polar-orbiting Partnership (Suomi NPP) satellite. The VIIRS low-light sensor, known as the day-night-band (DNB), can detect nighttime light from wildfires, urban and rural communities, and other human activity which emits light. It can also detect moonlight reflected from clouds and surface features. Using real time VIIRS data collected by our collaborative partner at the Space Science and Engineering Center of the University of Wisconsin, the SPoRT team created composite imagery to help detect power outages and restoration. This blackout imagery allowed emergency response teams from a variety of agencies to better plan and marshal resources for recovery efforts. The blackout product identified large-scale outages, offering a comprehensive perspective beyond a patchwork GIS mapping of outages that utility companies provide based on customer complaints. To support the relief efforts, the team provided its imagery to the USGS data portal, which the Federal Emergency Management Agency (FEMA) and other agencies used in their relief efforts. The team fs product helped FEMA, the U.S. Army Corps of Engineers, and U.S. Army monitor regions without power as part of their disaster response activities. Disaster responders used the images to identify possible outages and effectively distribute relief resources. An enhanced product is being developed and integrated into a web mapping service (WMS) for dissemination and use by a broader end user community.

Jedlovec, Gary↗

NASA's Solar System Exploration Research Virtual Institute: Merging Science and Exploration

NASA's Solar System Exploration Research Virtual Institute (SSERVI) represents a close collaboration between science, technology and exploration, and was created to enable a deeper understanding of the Moon and other airless bodies. SSERVI is supported jointly by NASA's Science Mission Directorate and Human Exploration and Operations Mission Directorate. The institute currently focuses on the scientific aspects of exploration as they pertain to the Moon, Near Earth Asteroids (NEAs) and the moons of Mars, but the institute goals may expand, depending on NASA's needs, in the future. The 9 initial teams, selected in late 2013 and funded from 2014-2019, have expertise across the broad spectrum of lunar, NEA, and Martian moon sciences. Their research includes various aspects of the surface, interior, exosphere, near-space environments, and dynamics of these bodies. NASA anticipates a small number of additional teams to be selected within the next two years, with a Cooperative Agreement Notice (CAN) likely to be released in 2016. Calls for proposals are issued every 2-3 years to allow overlap between generations of institute teams, but the intent for each team is to provide a stable base of funding for a five year period. SSERVI's mission includes acting as a bridge between several groups, joining together researchers from: 1) scientific and exploration communities, 2) multiple disciplines across a wide range of planetary sciences, and 3) domestic and international communities and partnerships. The SSERVI central office is located at NASA Ames Research Center in Mountain View, CA. The administrative staff at the central office forms the organizational hub for the domestic and international teams and enables the virtual collaborative environment. Interactions with geographically dispersed teams across the U.S., and global partners, occur easily and frequently in a collaborative virtual environment. This poster will provide an overview of the 9 current US teams and international partners, as well as information about outreach efforts and future opportunities to participate in SSERVI.

technology↗

CisLunar Habitat Internal Architecture Design Criteria

BACKGROUND: In preparation for human exploration to Mars, there is a need to define the development and test program that will validate deep space operations and systems. In that context, a Proving Grounds CisLunar habitat spacecraft is being defined as the next step towards this goal. This spacecraft will operate differently from the ISS or other spacecraft in human history. The performance envelope of this spacecraft (mass, volume, power, specifications, etc.) is being defined by the Future Capabilities Study Team. This team has recognized the need for a human-centered approach for the internal architecture of this spacecraft and has commissioned a CisLunar Phase-1 Habitat Internal Architecture Study Team to develop a NASA reference configuration, providing the Agency with a "smart buyer" approach for future acquisition. THE CISLUNAR HABITAT INTERNAL ARCHITECTURE STUDY: Overall, the CisLunar Habitat Internal Architecture study will address the most significant questions and risks in the current CisLunar architecture, habitation, and operations concept development. This effort is achieved through definition of design criteria, evaluation criteria and process, design of the CisLunar Habitat Phase-1 internal architecture, and the development and fabrication of internal architecture concepts combined with rigorous and methodical Human-in-the-Loop (HITL) evaluations and testing of the conceptual innovations in a controlled test environment. The vision of the CisLunar Habitat Internal Architecture Study is to design, build, and test a CisLunar Phase-1 Habitat Internal Architecture that will be used for habitation (e.g. habitability and human factors) evaluations. The evaluations will mature CisLunar habitat evaluation tools, guidelines, and standards, and will interface with other projects such as the Advanced Exploration Systems (AES) Program integrated Power, Avionics, Software (iPAS), and Logistics for integrated human-in-the-loop testing. The mission of the CisLunar Habitat Internal Architecture Study is to become a forcing function to establish a common understanding of CisLunar Phase-1 Habitation Internal Architecture design criteria, processes, and tools. The scope of the CisLunar Habitat Internal Architecture study is to design, develop, demonstrate, and evaluate a Phase-1 CisLunar Habitat common module internal architecture based on design criteria agreed to by NASA, the International Partners, and Commercial Exploration teams. This task is to define the CisLunar Phase-1 Internal Architecture Government Reference Design, assist NASA in becoming a "smart buyer" for Phase-1 Habitat Concepts, and ultimately to derive standards and requirements from the Internal Architecture Design Process. The first step was to define a Habitat Internal Architecture Design Criteria and create a structured philosophy to be used by design teams as a filter by which critical aspects of consideration would be identified for the purpose of organizing and utilizing interior spaces. With design criteria in place, the team will develop a series of iterative internal architecture concept designs which will be assessed by means of an evaluation criteria and process. These assessments will successively drive and refine the design, leading to the combination and down-selection of design concepts. A single refined reference design configuration will be developed into in a medium-to-high fidelity mockup. A multi-day human-in-the-loop mission test will fully evaluate the reference design and validate its configuration. Lessons learned from the design and evaluation will enable the team to identify appropriate standards for Phase-1 CisLunar Habitat Internal Architecture and will enable NASA to develop derived requirements in support of maturing CisLunar Habitation capabilities. This paper will describe the criteria definition process, workshop event, and resulting CisLunar Phase-1 Habitat Internal Architecture Design Criteria.

Jones, R.↗

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Bolton, Albanie T.↗

X-HAB 2020: AR Field Treks Summary and Conclusions

As part of the FY20 X-Hab Challenge, BLiSS sought to create an Augmented Reality (AR) toolkit to help with analog field trek operations under the supervision of the Solar System Exploration Research Virtual Institute (SSERVI). These treks are operational and technical demonstrations at space-like destinations on Earth to test current extra-vehicular activity (EVA) techniques. While BLiSS as an organization has experience studying operational tasks such as this, it has never developed AR software at this scale. For that reason, another team at the University was brought on to work in parallel. The Collaborative Lab for Advancing Work in Space (CLAWS) is a veteran group of the NASA Spacesuit User Interface Technologies for Students (SUITS) challenge in which Hololens displays for astronauts are created within a year. The operational and technological pairing was ideally suited for tackling this problem. The team divided its responsibilities so that BLiSS would handle the research required to shape the project. As this deliverable had an end user, it was decided that interviewing these field geologists and operations specialists would provide the best insight. These interviews paired with literature review would reveal niche applications for AR that remained within feasible bounds. These science-driven EVAs in unknown terrain require more flexible tools than the current generation of EVA assistants. Rather than focus on sequential instructions, there instead needs to be a broad toolkit that's only called upon in specific instances. This AR Toolkit for Lunar Astronauts and Scientists (ATLAS) became the development goal of the project: create a non-intrusive assembly of tools that could be accessed in AR on the field. The current ATLAS design makes use of a geospatially and temporally annotated eld note system called GeoNotes. This allows for data to be collected and coordinated in a way that's synchronized across time, space, and different users. A Mission Control Center (MCC) and Mobile Support Equipment (MSE) were all needed to transport the AR headset into the field with the user. A network infrastructure was designed and set up within the University to enable this functionality. The software is based on a Protocol-Module structure that allows for modular development of each capability. A Protocol Manager coordinates different protocols that make use of modules. Each module tackles a different individual task while the protocol puts each one to use. The protocol manager coordinates when these are called to be used. This software is hosted on a head-mounted display (HMD) with the MCC acting as support from afar. While the software would be unit-tested at each level and each hardware component verified, a final demonstration would serve to prove the system's capabilities: an analog field trek. The team would prepare to support a user in a remote location from the MCC back at the University. A local area near campus would be tested before going out to do sample field geology further away. This unfortunately became impossible with the arrival of COVID-19. Access to all of the facilities to complete the project as planned were shut down. Our team was scattered across the globe and forced to complete the rest virtually. Adjustments were made to produce a small virtual concept in Adobe XD in the meantime. Even digital surveys were created based on the NASA task-load index (TLX) originally intended for testing actual users. The goal shifted towards completing software and getting feedback on the user interfaces (UI) and user experiences (UX). This team has reformed in response to COVID and its focus has shifted to what can be done remotely. There is still an intention to finish the original deliverable described in this report. The work has been expanded beyond the original X-Hab challenge and has instead become its own research e ort to be continued afterwards. This report collects the processes and knowledge gained from a year of studying and working at this problem with two teams. It should preserve it for the time until the world returns to normal and work can resume. CLAWS will be taking over full responsibility from that point forward, eventually surpassing the original needs of the project. While this document captures the work done towards an eventual end, the CLAWS team has written their own proposal alongside it. It outlines a new future for ATLAS beyond X-Hab, BLiSS, and hopefully beyond COVID-19. This project began as a vague goal hoping to place a new technology into the unique setting of exploration science. The project has since comfortably taken root and will hopefully bloom over the next year.

Alex Sena↗

Building Capacity for Policy-makers in a Virtual Setting: Providing Tools to Analyze Wildfire Smoke Plumes and Their Impacts

The NASA DEVELOP Program conducted 10-week long feasibility projects in a remote work setting, including partnering with The Nature Conservancy’s Washington Chapter and the Puget Sound Clean Air Agency to investigate wildfire smoke from 2000 - 2020 in the Pacific Northwest using satellite-derived data. The team engaged with platforms for collaboration both internally with NASA affiliates and externally with community organizations. Working from multiple states, the team members used a variety of software including Google Meet, Microsoft Teams, and Google Earth Engine to foster communication and work with data in a shared virtual environment. Throughout the project, the team learned that executing the project in a distanced work setting made it easier to reach out to scientists across the country for expertise and guidance. To study changes in air quality resulting from wildfire smoke, the team utilized data from NASA’s Fire Information from Resource Management System (FIRMS) and the ESA’s Sentinel-5 TROPOspheric Monitoring Instrument (TROPOMI). The team created a Google Earth Engine web-based tool, “Plume Hazards and Observations of Emissions by Navigating an Interactive eXplorer” (PHOENIX), to visualize changes in pollutants and aerosol optical depth after fire events. The potential relationship between plume height and fire radiative power was evaluated by using NASA’s Moderate Resolution Imaging Spectroradiometer (MODIS) aboard Aqua and Terra satellites and NASA’s Multi-angle Imaging SpectroRadiometer (MISR) aboard Terra with the MISR INteractive eXplorer (MINX). The PHOENIX smoke assessment tool and science communication infographics will be shared electronically with the partner organizations. Furthermore, the team introduced the partners to MINX and will provide a tailored tutorial that included a recorded video and a written component with a live virtual workshop. These resources build capacity for further research and education on wildfire smoke and air quality within communities.

NASA DEVELOP↗

The “Gearamid” Model: Transforming NASA Langley’s Role in the Aerospace Technology Ecosystem

NASA’s operating environment is evolving: numerous new emerging technologies are converging to create breakthrough solutions, many nontraditional players are partnering to create those solutions, and a diverse array of new public-private funding models are being employed. A team at NASA’s Langley Research Center (LaRC) developed a model to describe the challenges that must be addressed for an emerging breakthrough technology to penetrate the appropriate market sector, and how all the players in the relevant ecosystem can collaborate to accelerate the market infusion process. This model, which the team dubbed the “Gearamid,” originated from a narrower study to determine what LaRC should do to capitalize on and advance autonomous technology as a “game changer” in the civil aerospace domain. The elements in the original version of the Gearamid depict the various challenges that need to be addressed as an autonomous technology proceeds from initial development to market infusion. In addition, the Gearamid indicates the “actors” best suited to address each challenge element. The study team noted that all challenge elements in the Gearamid must be worked concurrently to assure successful infusion of autonomous solutions. The team also found that NASA expertise naturally positions Agency organizations—including LaRC—to lead contributions that address certain challenge elements and to play a supplemental role in other areas where entities external to NASA are actively working and investing to solve challenges. Furthermore, the team concluded that NASA can play a leadership role in coordinating efforts of the diverse entities across the civil aerospace community. After determining the center’s optimal role in the autonomous technology development ecosystem, the study team then extrapolated the Gearamid model for autonomous technologies into a broader, more general model depicting the challenge elements that must be overcome to develop and infuse any emerging technology. LaRC has embraced the Gearamid model and is using it to drive changes that will transform the center and allow it to function optimally in the evolving landscape. Given LaRC’s successes, the study team suggests that other organizations may also be able to use the Gearamid model to inform future planning/strategy efforts.

Jill M Marlowe↗

An Exploration of Mission Concepts That Could Utilize Small RPS

The NASA Radioisotope Power Systems (RPS) Program Mission Analysis Team at the Jet Propulsion Laboratory (JPL) requested a JPL Innovation Foundry Architecture Team (A-Team) study to assess mission pull for small RPS (1 mWe - 40 We) in order to inform the RPS Program Office on what future power system developments should be focused on. The A-Team is JPL’s concurrent engineering design team for science definition and early mission concept development, targeting concept maturation levels of 1 through 3. The requested small RPS study was tasked to identify the architecture space of potential small RPS missions, and suggest power levels that could enable or enhance potential future small spacecraft missions. This paper describes the collaborative engineering processes that the A-Team and Mission Analysis Team used to reach results quickly and the findings to inform the RPS Program about mission concept power requirements on RPS for small missions.

Bairstow, Brian K.↗

Forging the Forge

As part of the NASA Johnson Space Center’s (JSC) effort to revitalize and recommit to our “Dare Unite Explore” vision for the future, the Center is exploring a new strategy to spread the innovation mindset and increase collaboration across the workforce. In order to maintain JSC’s leadership in human spaceflight, there is a need for working at the speed of commercial industry, breaking down silos between organizations, improving innovation and increasing workforce flexibility. Through brainstorming concepts and benchmarking other facilities, the leadership team evaluated several ideas, assessed constraints and derived that an “Innovation Team” was relatively easy to adopt. Modeled after productive teams like the Jet Propulsion Laboratory’s Innovation Foundry and Glenn Research Center's Compass team, JSC is laying the foundation of a new innovation team called the Forge. This team is as much about getting employees tempered in the ways of innovative thinking as it is about refining design studies and hammering out proposals. By the dictionary definition of the verb, forge can mean either to move ahead slowly and steadily or to move with a sudden increase of speed and power. Driving cultural change in a large government organization like NASA often involves slow perseverance with small injections of momentum to forge ahead. Leveraging lessons learned from the Innovation Foundry and Compass, this paper describes how the collaborative, concurrent engineering framework was tailored to JSC’s needs, as well as the aspects that were considered given JSC’s operation-focused, Program-driven landscape. Our process to drive cultural change, the steps taken, and challenges encountered are discussed. The first two pilots of the teaming framework are described with initial results presented in terms of employee engagement and fostering innovation. We also describe the planned future work and next steps to continue to push the initiative forward. Long has the Center been resting on its operations heritage, now we are forging a new path to Dare to expand frontiers, Unite with our partners and Explore space to benefit humanity.

Culture Change↗