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,405 records · Page 78

Achieving Maximum Integration Utilizing Requirements Flow Down

A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.

Archiable, Wes↗

System Engineering Paper

The Iowa State University team, Team LunaCY, is composed of the following sub-teams: the main student organization, the Lunabotics Club; a senior mechanical engineering design course, ME 415; a senior multidisciplinary design course, ENGR 466; and a senior design course from Wartburg College in Waverly, Iowa. Team LunaCY designed and fabricated ART-E III, Astra Robotic Tractor- Excavator the Third, for the team's third appearance in the NASA Lunabotic Mining competition. While designing ART-E III, the team had four main goals for this year's competition:to reduce the total weight of the robot, to increase the amount of regolith simulant mined, to reduce dust, and to make ART-E III autonomous. After many designs and research, a final robot design was chosen that obtained all four goals of Team LunaCY. A few changes Team LunaCY made this year was to go to the electrical, computer, and software engineering club fest at Iowa State University to recruit engineering students to accomplish the task of making ART-E III autonomous. Team LunaCY chose to use LabView to program the robot and various sensors were installed to measure the distance between the robot and the surroundings to allow ART-E III to maneuver autonomously. Team LunaCY also built a testing arena to test prototypes and ART-E III in. To best replicate the competition arena at the Kennedy Space Center, a regolith simulant was made from sand, QuickCrete, and fly ash to cover the floor of the arena. Team LunaCY also installed fans to allow ventilation in the arena and used proper safety attire when working in the arena . With the additional practice in the testing arena and innovative robot design, Team LunaCY expects to make a strong appearance at the 2012 NASA Lunabotic Mining Competition. .

Heise, James↗

JPL's Foundry Furnace: Web-Based Concurrent Engineering for Formulation

The Jet Propulsion Laboratory’s Innovation Foundry is an enterprise tasked with shepherding space mission concepts through the formulation lifecycle. It oversees a number of “virtual teams” for the various stages of formulation. Among these is Team X, which has had considerable success over its more than 20-year history. In a Team X study, domain experts (including engineers devoted to the various spacecraft subsystems) work concurrently and collaboratively over several days to arrive at a feasible point design with a reasonable cost estimate. They use a set of linked Excel workbooks, each developed and approved by a responsible “line organization” within JPL. This toolset has served Team X well over the years, and has evolved since its inception. At the same time, the Innovation Foundry’s portfolio of formulation teams has expanded, and so has the scope of the design challenges they face. The A-Team runs workshop-like architecture studies to focus science investigations, generate mission concepts, assess feasibility, and explore trade spaces. Team Xc performs rapid point design in the style of Team X, but for CubeSats and small spacecraft, using a different toolset. Proposal teams further mature concepts to the point where they can be proposed. Recognizing the importance of trade space modeling combined with new IT services for providing and integrating data, JPL is developing the Foundry Furnace web-based software infrastructure. It will support A-Team, Team Xc, and Team X, providing study management, a catalog of hardware components, a library of re-usable analyses, and a design environment. It is a modernization of JPL’s concurrent engineering infrastructure, embracing the core concepts of Model-Based Systems Engineering, and built with modern software design philosophies.

Murphy, Jonathan↗

Lunar Wormbot: Design and Development of a Ground Base Robotic Tunneling Worm for Operation in Harsh Environments

From 1969 to 1972, the National Aeronautics and Space Administration (NASA) sent Apollo missions to the moon to conduct various exploration experiment. A few of the missions were directed to the study and sampling of moon soil, otherwise known as lunar regolith. The extent of the sample acquisition was limited due to the astronauts' limited ability to penetrate the moon's surface to a depth greater than three meters. However. the samples obtained were sufficient enough to provide key information pertaining to lunar regolith material properties that would further assist in future exploration endeavors. Analysis of the collected samples showed that the properties of lunar regolith may lead to knowledge of processed materials that will be beneficial for future human exploration or colonization. However, almost 40 years after the last Apollo mission, limited infonnation is known about regions underneath the moon's surface. Future lunar missions will require hardware that possesses the ability to burrow to greater depths in order to collect samples for subsequent analysis. During the summer of 2010, a team (Dr. Jessica Gaskin, Michael Kuhlman. Blaze Sanders, and Lafe Zabowski) from the NASA Robotics Academy at Marshall Space Flight Center (MSFC) was given the task of designing a robot to function as a soil collection and analysis device. Working with the National Space Science and Technology Center (NSSTC), the team was able to propose an initial design, build a prototype, and test the various subsystems of the prototype to be known as the "Lunar Wormbot" (LW). The NASA/NSSTC team then transferred the project to a University of Alabama in Huntsville (UAH) Mechanical and Aerospace Engineering (MAE) senior design class for further development. The UAH team was to utilize the NASA Systems Engineering Engine Design Process in the continuance of the Lunar Wormbot project. This process was implemented in order to coordinate the efforts of the team and guide the design of the project to ensure a high quality product that met requirements within the academic year timeframe. When the transition from the NASA NSSTC team to the UAH team occurred in August 2010, the scope and requirements were provided to the UAH team. The main objective for the UAH team was to design and fabricate a robotic burrowing prototype using peristaltic or earthworm-like motion with the purpose of collecting soil samples. The team was tasked with the design of a sub-system of the LW called the locomotive, or active, segment. Through the design process, the team extensively reviewed the requirements and functions to be performed of the LW, which led to the proposal of a final design. The present paper provides the details of the development of the design up to and including the Critical Design Review (CDR) of the Lunar Wormbot. This document briefly describes thc overall system and its function but primarily focuses on the design and implementation of the locomotive segment. Content presented includes: general design and system functionality, technical drawings, system analysis, manufacturing methods, and general project costs.

Boyles, Charles↗

Examining Circadian Disadvantages in the National Basketball Association's (NBA) Playoffs

Introduction: Prior research on travel in the National Basketball Association’s (NBA) regular season has shown that teams journeying west relative to their home base face circadian disadvantages for evening games, while those traveling east have advantages. The current study extends previous research by examining these effects within the NBA playoffs. We hypothesized that teams would have a greater circadian advantage during eastward compared to westward travel. Methods: In 2013, the NBA implemented a 7-game series playoff structure, in which teams play an alternating home/away 2-2-1-1-1 format for the Finals. Data for all 499 postseason games played during the 2013-14 to 2018-2019 seasons were collected from Basketball-Reference and FiveThirtyEight. We investigated the impact of direction of travel based on home base city (same time zone, westward, eastward) and time zones traveled on actual game outcomes, Elo rating differences (i.e., a team quality metric based on wins and losses), Elo predicted win probability, and team scoring for visiting teams. Results: Teams had lower Elo predicted win probabilities following 3-hour westward than same time zone and all eastward travel, while 3-hour eastward travel related to higher probabilities of winning compared to same time zone and all westward travel (p < .02, d > .95). Teams travelling westward with 2-hour time changes lost significantly more games than those experiencing 1-hour westward (p = .04, OR = 2.45), 1-hour eastward (p = .05, OR = 2.34), and 3-hour eastward changes (p = .02, OR = 4.68). Scoring was significantly higher following eastward travel compared to both westward (p = .001, d = 0.60) and same time zone travel (p = .003, d = 0.44). There were no statistically clear differences in team quality based on overall direction of travel or number of time zones traveled, and game outcomes based on direction of travel (p > .05). Conclusion: Overall direction of travel was related to team scoring, while number of time zones traveled was associated with Elo predicted win probability and game outcomes. Generally, teams travelling eastward and within the same time zone gained an advantage over those travelling westward. Adjustment to travel and time zone changes appear to influence certain aspects of in-game performances and outcomes in the NBA playoffs.

circadian misalignment↗

NASA GPU Hackathon Yields Significant Code Improvements

The NASA GPU Hackathon 2020 brought together application developers and computer experts to help get important NASA applications running effectively on graphics processing unit (GPU) nodes. Nine teams of application developers participated in this virtual event, a major impetus for teams to modernize codes of interest for NASA missions to CPU nodes containing GPU accelerators, with a focus on hands-on problem solving. The photo in Figure1 shows 30 of the more than50 participants. The HECC project and NVIDIA jointly organized the event, and HECC provided five Pleiades nodes each with 4 V100 GPUs for teams to use. The virtual event, which took place over four days from September 28–October 7, 2020, used Microsoft Teams and Slack as collaboration tools. Each team consisted of three to six members from NASA Centers and supporting organizations. The teams were paired with one to two mentors from industry, government, and academia. The experience levels of the teams ranged from being GPU novices to advanced CUDA programming experts. OpenACC and the emerging Kokkos API were used in addition to CUDA for GPU programming. During the event, which focused on accelerating AeroSciences and CFD applications, most teams achieved considerable performance improvements on both GPUs and CPUs. For example, a team with no GPU experience completed a first port of a time-critical loop to a GPU. Another team of expert CUDA programmers were able to restructure their algorithm, yielding a factor of five speed-up. And another team sped up some of their CUDA kernels by a factor of 20, which directly translated into their production code. This article highlights some of the many successes resulting from the event.

HECC↗

Packages of Distributed Energy Technologies Demonstrating Demand Flexibility at Community Scale

The combination of increased electric load growth across all sectors, deferred electrical infrastructure investment, and other factors resulting in variable electric power supply, has created technical challenges to maintaining a resilient and reliable grid. Many federal, regional, and local efforts are in play to modernize the electric grid, including advancing building technologies and distributed energy resources (DERs) that are utilizing smarter controls to become responsive to both occupant and grid needs. This report reviews ten pilot projects demonstrating how groups of buildings combined with behind-the-meter (BTM) DERs such as electric vehicle (EV) charging, battery storage, flexible HVAC and domestic hot water systems, and photovoltaic systems can reliably and cost effectively provide grid services. Each of the ten pilot projects aim to deliver both energy efficiency and demand flexibility (DF) while supporting load growth. The ten demonstration teams are piloting flexible DER packages across diverse communities of residential and commercial buildings to address a variety of regional grid needs. The outcomes of these pilot projects will be used to inform future scaling through utility program development. This paper characterizes the ten teams, showcasing the decision-making process used by each group to develop their packages (Section 2), the grid services they plan to deliver (Section 3), the types of DER packages selected for deployment within building sectors (Section 4) and trends between building sector, DER types, and grid services In order to achieve community scale benefits, the pilot projects must utilize aggregated control mechanisms for coordinating buildings and DERs together. Several types of coordinated control architectures have evolved amongst the teams, influenced by use type, existing market conditions, and integration type. Three coordinated controls architectures have been characterized, highlighting their use cases, benefits, challenges, and tradeoffs in their design. These insights can aid utilities, control vendors, and developers in scaling community-level energy systems (Paul, 2024). Ultimately, the technology packages selected by the ten teams will be coordinated to provide power system services, also known as grid services. Insights from these demonstrations will be useful for grid operators, regulators, aggregators and other stakeholders as they look to deploy demand flexible resources as grid services in the future. The grid services that each team is targeting for demonstration are described in Section 3 and Section 4. Methods for evaluating the grid services have been described in the paper Metrics for Evaluating Grid Service Provision from Communities of Grid-interactive and Efficient Buildings and other DER (MacDonald, 2023). To identify technology packages for demonstration, Section 2 shows that project teams used a range of analysis approaches, including building energy modeling, AMI data analysis, cost-benefit frameworks, and utility pilot data. Some teams emphasized technical modeling to quantify grid impacts and demand reduction potential, while others prioritized economic evaluations, stakeholder input, or exploratory pilots to inform deployment decisions. This diversity reflects the need to tailor selection methods to project goals, available data, and organizational context. Section 5 discusses trends between the DER technologies deployed and the grid service provisions from each team. Residential buildings (multifamily and single family) lean towards technologies that enhance energy efficiency (e.g. weatherization upgrades, smart thermostats) and onsite power generation integration (e.g. solar PV). Commercial building demonstrations prioritize technologies that ensure operational reliability (e.g. battery storage) and centralized energy management systems and optimization solutions. Teams that are deploying controllable storage-based technologies are more likely to provide grid services that require a near real-time response. Teams incorporating load shifting technologies like smart thermostats with HEMs are likely to include energy markets participation and customer bill management offerings. Campus demonstrations are adopting diverse sets of DERs to emphasize renewable generation, paired with centralized control. This section also describes technologies that were considered during project planning but ultimately excluded from final deployment. These demonstrations reveal that effective DER package design should be tailored to building type, customer segment, and construction vintage. Multifamily buildings benefit from centralized HVAC upgrades and supervisory controls, while single-family homes are well-suited for individualized technologies like solar, storage, and smart home energy monitors. Commercial and campus settings prioritize EMIS integration and load optimization. New construction enables cost-effective integration of DER-ready infrastructure, whereas retrofits require deployments aligned with owner and tenant value streams. For utility program planners, early coordination with developers and building owners, paired with segmented and modular program offerings, can improve adoption, scalability, and grid impact.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Lead Research and Development Activity for DOE's High Temperature, Low Relative Humidity Membrane Program (Topic 2)

The Department of Energy’s High Temperature, Low Relative Humidity Membrane Program was begun in 2006 with the Florida Solar Energy Center (FSEC) as the lead organization. During the first three years of the program, FSEC was tasked with developing non-Nafion® proton exchange membranes with improved conductivity for fuel cells. Additionally, FSEC was responsible for developing protocols for the measurement of in-plane conductivity, providing conductivity measurements for the other funded teams, developing a method for through-plane conductivity and organizing and holding semiannual meetings of the High Temperature Membrane Working Group (HTMWG). The FSEC membrane research focused on the development of supported poly[perfluorosulfonic acid] (PFSA) – Teflon membranes and a hydrocarbon membrane, sulfonated poly(ether ether ketone). The fourth generation of the PFSA membrane (designated FSEC-4) came close to, but did not meet, the Go/No-Go milestone of 0.1 S/cm at 50% relative humidity at 120 °C. In-plane conductivity of membranes provided by the funded teams was measured and reported to the teams and DOE. Late in the third year of the program, DOE used this data and other factors to decide upon the teams to continue in the program. The teams that continued provided promising membranes to FSEC for development of membrane electrode assemblies (MEAs) that could be tested in an operating fuel cell. FSEC worked closely with each team to provide customized support. A logic flow chart was developed and discussed before MEA fabrication or any testing began. Of the five teams supported, by the end of the project, membranes from two of the teams were easily manufactured into MEAs and successfully characterized for performance. One of these teams exceeded performance targets, while the other requires further optimization. An additional team developed a membrane that shows great promise for significantly reducing membrane costs and increasing membrane lifetime.

08 HYDROGEN↗

Evaluation of American Indian Science and Engineering Society Intertribal Middle School Science and Math Bowl Project

The American Indian Science and Engineering Society (AISES) has been funded under a U.S. Department of Energy (DOE) grant (Grant Award No. DE-SC0004058) to host an Intertribal Middle-School Science and Math Bowl (IMSSMB) comprised of teams made up of a majority of American Indian students from Bureau of Indian Education-funded schools and public schools. The intent of the AISES middle school science and math bowl is to increase participation of American Indian students at the DOE-sponsored National Science Bowl. Although national in its recruitment scope, the AISES Intertribal Science and Math Bowl is considered a “regional” science bowl, equivalent to the other 50 regional science bowls which are geographically limited to states. Most regional bowls do not have American Indian student teams competing, hence the AISES bowl is meant to encourage American Indian student teams to increase their science knowledge in order to participate at the national level. The AISES competition brings together teams from various American Indian communities across the nation. Each team is provided with funds for travel to and from the event, as well as for lodging and meals. In 2011 and 2012, there were 10 teams participating; in 2013, the number of teams participating doubled to 20. Each Science and Math Bowl team is comprised of four middle school — grades 6 through 8 — students, one alternate, and a teacher who serves as advisor and coach — although in at least two cases, the coach was not a teacher, but was the Indian Education Coordinator. Each team member must have at least a 3.0 GPA. Furthermore, the majority of students in each team must be comprised of American Indian, Alaska Native or Native Hawaiian students. Under the current DOE grant, AISES sponsored three annual middle school science bowl competitions over the years 2011, 2012 and 2013. The science and math bowls have been held in late March concurrently with the National American Indian Science and Engineering Fair (NAISEF) and EXPO at the Albuquerque, NM Convention Center. Albuquerque is also the home of the AISES national office. The AISES staff also recruits volunteers to assist with implementation of the science and math bowl event. In 2011, there were 7 volunteers; in 2012, 15 volunteers, and in 2013, 19 volunteers. Volunteers are recruited from a variety of local sources, including Sandia Laboratories, Southwest Indian Polytechnic Institute students, Department of Defense, as well as family members of AISES staff. For AISES, the goals of the Intertribal Middle School Science and Math Bowl project are to have more Native students learn science, for them to gain confidence in competing, and to reward their effort in order to motivate them to pursue studies in the sciences and engineering. For DOE, the goals of the project are to get more Native students to compete at the National Science Bowl, held in Washington, DC.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Multimodal Nondestructive Dry Cask Basket Structure and Spent Fuel Evaluation

This NEUP-IRP assembled a team from diverse institutions and a diverse set of expertise to examine the problem of assessing the structural health of dry nuclear fuel storage casks, specifically the TN-32 design. With no physical access designed into these storage casks and the high cost and risk associated with opening casks for direct inspection, the technical difficulty of structural assessment of the basket structure and fuel assemblies is high. In response to this challenge, this IRP brought together experts in both traditional and novel NDE methodologies: active acoustics (University of Mississippi), emissions tomography (University of Florida), muon tomography (Oregon State University), and passive-active ultrasonics (University of South Carolina). Further, our industry partners in the Electric Power Research Institute (EPRI) and AREVA provided invaluable insight into technical design details for the cask, practical knowledge of operating parameters at a storage facility, and key relationships that enabled activities unforeseen at the time of the proposed work but were critical in guiding the path of the research. The team decided early in the project that we had a collective goal of laying the technical ground work for practical solutions that could be implemented in the field with reasonable cost, time, and reliability. A fortunate opportunity arose early in this IRP project to obtain access to a new TN-32 cask at Columbiana High Tech. Both acoustics teams were given access for testing concepts in the first year of the project. This ended up providing critical guidance in the design of subsequent laboratory experiments. Specifically, it became clear that the only reliable acoustic pathways to the interior were through the trunnions, base plate, and top ring of the cask. Based on these field tests and discussions about what would be of practical interest, the team as a whole decided a realistic goal was to detect catastrophic failure of a single fuel assembly, or one that was missing. It is clear from this work that the active acoustics / resonance and muon tomography methodologies would be capable of detecting interior structural integrity problems at this level. The other two areas of investigation (emissions tomography and passive/active ultrasonics) would need more testing to determine a successful implementation, but each may also have other applications such as long term monitoring and monitoring during transportation. This IRP project resulted in technical advances with applications that extend beyond the problem at hand, supported the training of 10 graduate students + 1 post doc, 21 publications, and 13 conference presentations. The remainder of this summary highlights significant activities and achievements in each of the methodologies and a brief discussion on how they can be combined to leverage strengths. Active Acoustics The active acoustics team at UM used both linear and non-linear structural resonance methods to infer information about the internal structure of a cask. Significant activities were a set of four field test measurements on a full scale TN-32 cask at the Columbiana Hi Tech facility in Greensboro, NC and the design and fabrication of a 1/6th scale model TN-32 cask for laboratory measurements. A significant set of acoustic data has been acquired on both the full scale and laboratory scale casks. It was determined early in the project that mechanical resonance techniques were not going to be sensitive to small scale (centimeter) cracks and structural defects in the basket structure or fuel assemblies. We were able to ascertain that both the energy and complexity of the resonance spectra were sensitive to “bulk state” of the fuel assemblies – an intact assembly versus a severely degraded assembly. By developing a novel combination of metrics, we are able to measure a statistically significant shift due to one out of the 32 fuel assemblies being either missing or degraded to a point of complete loss of structural coherence (i.e. “rubble”). We believe this combination of resonance metrics is new to the field and will have applications beyond the fuel storage problem. Emissions Tomography The Emissions Tomography team at the University of Florida explored the concept of using scattering of radiation emissions from the stored fuel as method of evaluating the internal structural health of the cask. Due to the need for emissive fuel assemblies and the difficulties of gaining access to storage facilities, this team primarily relied on simulations to inform feasibility. A key question was the flux estimates of neutrons with a small enough number of scattering events to retain spatial information. Some key conclusions from the transmission component of this work are that the number of scattering events falls rapidly with energy – setting a 11MeV threshold, the average number of scattering events is 8∓4. Rough estimates of scanning times using an ideal detector array would be 1 week. The team also explored the case of significant structural failure resulting in a shift of the source material (fuel). The result is that a +/- 2% mass shift results in a detectable (5.13%) shift in the correlated 2 neutron emission counts and thus may be a candidate as an initial survey. Finally, simulations for predicting the azimuthal dependence of the flux based on specific loading patterns were conducted. Due to self-shielding effects of the assemblies, a periodic pattern results and could potentially be used to identify missing or severely degraded assemblies. This work forms a basis for proper detector placement with the goal of optimizing sensitivity. Muon Tomography Muon tomography (MT) is a relatively novel method of interrogating interior structure on a large scale. One of the advantages of this technique is that the exciting energy source (cosmic muons) is ubiquitous and relatively stable in time. Challenging aspects are relatively low flux rates and appropriate detector technologies. The efforts of the muon group at Oregon State University focused on two areas: (1) simulation of various combinations of muon scattering events and detection schemes to assess sensitivities and time scales for image construction and (2) building a prototype muon detection system applicable to the dry storage cask problem as well as many other similar systems. Significant accomplishments in this area are: (1) demonstration that MT is a viable method for detecting missing or severely degraded rod assemblies, (2) a scintillation based detector with 4 panels and 32 channels of position data each were constructed, tested, and calibrated. Testing of the panels using natural muon background and no scattering objects yielded largely expected results – a straight line path for the muon through the four panels. However some anomalies (paths deviating from a line) were also detected. A redesign of the board improved the signal which greatly improved the muon tracking through the panels. Testing with lead bricks as scattering bodies showed a reduction in the coincidence rate with increasing bricks indicating increased scattering events. A refinement of the scintillator detector design resulted in a spatial image resolution of around 2 cm based on lead brick spacing tests lasting 24 hours. Passive/Active Ultrasonics This team at the University of South Carolina investigated the feasibility of combining passive ultrasonics, in which an elastic pulse is generated by a degradation process (such as a crack extending), and active ultrasonics, in which a known excitation is introduced into the structure and detected by an array of transducers. Significant accomplishments in this area include the development of elastic wave propagation simulation in relevant materials, development of diagnostic algorithms, and laboratory testing and validation using laser doppler vibrometry. This group demonstrated the applicability of various non-contact vibration detection methodologies such as air-coupled ultrasonic transducers and scanning laser doppler vibrometry. While passive acoustic emissions monitoring will likely have a role during the transportation of a fuel storage cask, the level of detailed information about the defect generating the event which can be ascertained from the detections in a complex structure remains for future work. Thermography The EPRI team contributed early in the project a series of thermography measurements in which various levels of water pooled in a mock-up canister were analyzed using commercially available infrared imaging technologies. While large levels of water (100 L, ~10 cm deep) were observable in the thermograms, more realistic levels of pooled water (1 L) were not detectable whether localized or distributed.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Integrated Solutions for Optimized Performance (ISOP) Final Technical Report

The goal of this project was to demonstrate technical feasibility of an integrated approach for deep energy retrofits by packaging innovative technologies with smart communicating controls that represent the next generation of energy efficiency. The integrated solutions for optimized performance (ISOP) package integrates (i) advanced lighting and plug load controls; (ii) intelligent daylight harvesting through automated self-powered shades and window films; (iii) advanced HVAC controls sequences (ASHRAE Guideline (GDL) 36); and (iv) fault detection and diagnosis (FDD) and continuous commissioning (CCx) using advanced analytics. These technologies address energy use across multiple building end uses that represent more than 60% of the energy consumption in all commercial buildings. The project was structured to be implemented over three budget periods: Budget Period 1 scope included site selection, project design, site-specific customization of technology packages, procurement of technologies, initiation of installation of technologies, the development of a measurement and verification plan and collection of pre-retrofit data collection. The first year go/no-go decision was based on securing host sites representing 250,000 sq. ft. of occupied operational spaces, savings analysis, technology procurement and initiation of installation. Budget Period 2 planned to complete technology installations and initiate data collection of post-retrofit performance data. The second year go/no-go was to be the completion of technology installations and commissioning, metering and data collecting to support the requirements laid out in site specific M&V plans. Budget Period 3 planned to collect and analyze post-retrofit performance data and provide data and reporting to support energy efficiency rebate programs. After the team completed activities planned for Budget Period 1, the team reached a Go/No-Go Decision Point. At that point, TRC recommended that DOE discontinue the project without prejudice due to challenges with securing demonstration sites to meet the full 250,000 sf of occupied operational spaces and DOE concurred. In Budget Period 1, the TRC team developed criteria to recruit and evaluate potential demonstration host sites. TRC worked with Princeton University, the project demonstration partner, to identify buildings on their campus as potential candidates for the demonstration. Following the selection of demonstration sites, the TRC team customized energy technology packages according to the needs and characteristics of each site. TRC defined technology specifications, identified vendors, and conducted analysis to estimate energy and cost savings potential. The project team then developed schedules for technology procurement processes and scheduled for installation at all selected demonstration sites. The project team worked with Princeton University and DOE to develop an approach to verify energy savings achieved through measurement and verification (M&V) 2.0 methods. Princeton University initiated open bids to procure the necessary materials and installation contractors. Bid results came back higher than estimates due to a couple of factors – lack of familiarity of the bidders with the proposed technologies and lack of local trained installers to execute the installation of these new measures. Due to the higher bids, projects no longer met the internal cost-effectiveness criteria used by Princeton to proceed with procurement of the full suite of technologies as proposed in ISOP. Princeton had already procured parts of the ISOP package as part of a campus-wide initiative for FDD and lighting retrofits, but with the higher costs for other ISOP components, Princeton could no longer commit to the full ISOP package on the selected sites. Based on this, the team reached the Go/No-Go decision point, where they decided not to proceed with the project. Princeton is separately installing portions of the ISOP package where they individually meet Princeton’s payback criteria but on a different schedule than would have been needed for the DOE ISOP project. The team has learned several lessons from project progress in the first budget period. The team will utilize these lessons in future projects, as should any team which proceeds with a project around the ISOP technology. The first lesson is that more information about the proposed sites is required earlier in the process (perhaps even at the proposal stage) in order to have a successful demonstration. Technical details not evident earlier in the process (such as the TLED limitations for ALCS) can derail project execution. The second lesson is that pricing of emerging technologies is highly variable due to lack of familiarity of local installers and distributor with the proposed technologies as well as alternate bids using products they were more familiar with, but that cost more than the ones proposed by TRC. Finally, the last major lesson is that the host site’s internal project criteria is of critical importance. Based on these higher installed costs and lack of an informed installer base for the products proposed for this project, the project does not meet Princeton’s simple payback goals of five years.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Office of Nuclear Verification FY 2023 Quarterly Report TSVT Q1

This project encompasses the continued development and training of a U.S. operational team, the Test Site Verification Team (TSVT), supporting verification of nuclear testing activities. TSVT builds on decades of U.S. nuclear testing history and nuclear explosion monitoring experience. The Team maintains readiness to deploy internationally on short notice to provide field-based support of verification of declared or undeclared nuclear testing and associated activities, as well as follow-on activities including monitoring and capability disablement and dismantlement, as established by negotiated agreement or treaty. The roles and structure of the TSVT are integrated with other NA-243 deployable verification teams and the interagency. FY23 TSVT activities focus on continued capability buildup within the team, including Team trainings and exercises with a focus on missions in confined spaces (e.g., tunnels, mines, other underground facilities), increased familiarity with foreign nuclear weapons testing programs, demonstration of Team capacity to deploy, train, and practice sustained OPSEC in non-western locations, establishment of sustainable storage and maintenance of equipment, specification and procurement of additional equipment to support field observations, further evolution of concepts of operation documents (CONOPs), and mission coordination with Headquarters and associated Stakeholders. Activities will culminate with a full-scale domestic team exercise at the end of FY23 focusing on underground activities signatures/observations and safety including advanced outdoor safety and familiarity in working around explosive test environments. In addition, we will be further articulating approaches and capacity relevant to the identification of nuclear tests, as well as monitoring of nuclear testing activities and/or dismantlement of nuclear test sites and anticipate developing additional equipment requests in support of this evolution. The TSVT Team Leads will also coordinate with its Senior Advisor, the TSVT Logistics and Readiness (L&R) Training Lead, and NNSA Headquarters to draft a five-year TSVT training and exercise plan, that strategically and incrementally builds capacity and expertise in key areas of significance for the continuum of nuclear and nuclear-related testing activities that fall within the team’s mission space.

42 ENGINEERING↗

Novel Analysis and Visualization of Chemical Events for Public Health Surveillance

Pacific Northwest National Laboratory hosted an intern-based web application development contest in the summer of 2016 centered around developing novel chemical surveillance applications to aid in health situational awareness. Making up the three teams were three graduate students (n=9) from various US schools majoring in non-public health domains, such as computer science and user design. The interns successfully developed three applications that demonstrated a value-add to chemical surveillance—ChemAnalyzer (text analytics), RetroSpect (retrospective analysis of chemical events),and ToxicBusters (geo-based trend analytics). These applications will be the basis for the first chemical surveillance application to be incorporated into the DTRA Biosurveillance Ecosystem (BSVE).Pacific Northwest National Laboratory (PNNL), on behalf the Defense Threat Reduction Agency (DTRA; project number CB10190), hosts an annual intern- based web app development contest. Previous competitions have focused on mobile biosurveillance. The 2016 competition pivoted away from biosurveillance to focus on addressing challenges within the field of chemical surveillance and increasing public health chemical situational awareness. The result of the app will be integrated within the DTRA BSVE. PNNL hosted nine graduate interns for a 10-week period in the summer of 2016 as participants in a summer web application development contest. Students were drawn from such fields as software engineering and user experience and design and placed into three teams of three students. The challenge presented to the interns was to design and develop a fully-functional web application that would address a critical need within the chemical surveillance community. The interns developed their own ideas (vetted by PNNL and DTRA), discovered and integrated their own data sources, and produced their own visualizations and analytics, independent of any assistance outside of that provided in an advisory capacity. The competition end with a judging event with a panel of subject matter experts and cash awards were distributed to the teams. Each team produced a unique application. Although there was mild overlap between some of the ideas, the applications were developed independently and each reflected the unique contributions of the teams. ChemAnalyzer is a text-analytics platform designed to facilitate more data-driven decision, given a corpus of text data about a chemical event. Their platform provided the ability to automatically identify and highlight key words in documents related to chemical events. The keywords are drawn from an ontology installed with the system, as well as any user-identified keywords. The ChemAnalyzer team finished in third place. The RetroSpect team developed a visual analytic tool for performing retrospective analysis and monitoring of chemical events. Their app provided the ability to search and analyze past events, as well as visualization of state and county information for the recorded chemical events. The RetroSpect team finished in second place. The Toxic busters team - the winners of the competition - created a geo-based situational awareness tool for tracking chemical events. Their app featured an updateable map overlay, search functionality for finding specific or related events, incident and city/state/national-level statistics and trends, as well as news and social media integration based on keywords related to chemical surveillance. Each of the apps developed by the teams provides value to an analyst tasked with monitoring chemical events. The apps integrated unique data sources to provides a full picture of a chemical event, and its effects upon the surrounding population. This integrated analytics provides a valuable benefit over existing workflows, where analysts must monitor news, social, and other information sources manually for real-time information. The apps developed by these interns are designed to enable identification and analysis of the incident as quickly as possible, allowing for more timely assessments of the incident and its impacts. The web app development contest provided a unique opportunity for students to learn about the emerging needs in chemical surveillance as it relates to health situational awareness. Students were drawn from a variety of fields and were tasked with developing novel web apps addressing some of the most pressing challenges in the field of chemical surveillance. The ideas generated by the students will help form the basis for future chemical surveillance application development to be integrated with the DTRABSVE.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Re-engineering NASA's space communications to remain viable in a constrained fiscal environment

Along with the Red and Blue Teams commissioned by the NASA Administrator in 1992, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo, including current work processes, functional distinctions, interfaces, and information flow, as well as traditional management and system development practices. The Blue Team's unconstrained, non-parochial, and imaginative look at NASA's space communications program produced a simplified representation of the space communications infrastructure that transcends organizational and functional boundaries, in addition to existing systems and facilities. Further, the Blue Team adapted the 'faster, better, cheaper' charter to be relevant to the multi-mission, continuous nature of the space communications program and to serve as a gauge for improving customer services concurrent with achieving more efficient operations and infrastructure life cycle economies. This simplified representation, together with the adapted metrics, offers a future view and process model for reengineering NASA's space communications to remain viable in a constrained fiscal environment. Code O remains firm in its commitment to improve productivity, effectiveness, and efficiency. In October 1992, the Associate Administrator reconstituted the Blue Team as the Code O Success Team (COST) to serve as a catalyst for change. In this paper, the COST presents the chronicle and significance of the simplified representation and adapted metrics, and their application during the FY 1993-1994 activities.

Hornstein, Rhoda Shaller↗

An approach to verification and validation of a reliable multicasting protocol: Extended Abstract

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. This initial version did not handle off-nominal cases such as network partitions or site failures. Meanwhile, the V&V team concurrently developed a formal model of the requirements using a variant of SCR-based state tables. Based on these requirements tables, the V&V team developed test cases to exercise the implementation. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or off-nominal behaviors predicted by the current model. If the execution of a test in the model and implementation agreed, then the test either found a potential problem or verified a required behavior. However, if the execution of a test was different in the model and implementation, then the differences helped identify inconsistencies between the model and implementation. In either case, the dialogue between both teams drove the co-evolution of the model and implementation. We have found that this interactive, iterative approach to development allows software designers to focus on delivery of nominal functionality while the V&V team can focus on analysis of off nominal cases. Testing serves as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP. Although RMP has provided our research effort with a rich set of test cases, it also has practical applications within NASA. For example, RMP is being considered for use in the NASA EOSDIS project due to its significant performance benefits in applications that need to replicate large amounts of data to many network sites.

Callahan, John R.↗

Implementing Distributed Operations: A Comparison of Two Deep Space Missions

Two very different deep space exploration missions--Mars Exploration Rover and Cassini--have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a mission of more than ten years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process. Additionally, MER has benefited from the initial co-location of its entire operations team, and from having a single Principal Investigator, while Cassini operations have had to reconcile multiple science teams distributed from before launch. Cassini has faced greater challenges in implementing effective distributed operations. Because extensive early planning is required to capture science opportunities on its tour and because sequence development takes significantly longer than sequence execution, multiple teams are contributing to multiple sequences concurrently. The complexity of integrating inputs from multiple teams is exacerbated by spacecraft operability issues and resource contention among the teams, each of which has their own Principal Investigator. Finally, much of the technology that MER has exploited to facilitate distributed operations was not available when the Cassini ground system was designed, although later adoption of web-based and telecommunication tools has been critical to the success of Cassini operations.

Cassini Mission↗

Lessons Learned from Applying Design Thinking in a NASA Rapid Design Study in Aeronautics

In late 2015, NASA's Aeronautics Research Mission Directorate (ARMD) funded an experiment in rapid design and rapid teaming to explore new approaches to solving challenging design problems in aeronautics in an effort to cultivate and foster innovation. This report summarizes several lessons learned from the rapid design portion of the study. This effort entailed learning and applying design thinking, a human-centered design approach, to complete the conceptual design for an open-ended design challenge within six months. The design challenge focused on creating a capability to advance experimental testing of autonomous aeronautics systems, an area of great interest to NASA, the US government as a whole, and an entire ecosystem of users and developers around the globe. A team of nine civil servant researchers from three of NASA's aeronautics field centers with backgrounds in several disciplines was assembled and rapidly trained in design thinking under the guidance of the innovation and design firm IDEO. The design thinking process, while used extensively outside the aerospace industry, is less common and even counter to many practices within the aerospace industry. In this report, several contrasts between common aerospace research and development practices and design thinking are discussed, drawing upon the lessons learned from the NASA rapid design study. The lessons discussed included working towards a design solution without a set of detailed design requirements, which may not be practical or even feasible for management to ascertain for complex, challenging problems. This approach allowed for the possibility of redesigning the original problem statement to better meet the needs of the users. Another lesson learned was to approach problems holistically from the perspective of the needs of individuals that may be affected by advances in topic area instead of purely from a technological feasibility viewpoint. The interdisciplinary nature of the design team also provided valuable experience by allowing team members from different technological backgrounds to work side-by-side instead of dividing into smaller teams, as is frequently done in traditional multidisciplinary design. The team also learned how to work with qualitative data obtained primarily through the 70-plus interviews that were conducted over the course of this project, which was a sharp contrast to using quantitative data with regards to identifying, capturing, analyzing, storing, and recalling the data. When identifying potential interviewees who may have useful contributions to the design subject area, the team found great value in talking to non-traditional users and potential beneficiaries of autonomous aeronautics systems whose impact on the aeronautics autonomy ecosystem is growing swiftly. Finally, the team benefitted from using "sacrificial prototyping," which is a method of rapidly prototyping draft concepts and ideas with the intent of enabling potential users to provide significant feedback early in the design process. This contrasts the more common approach of using expensive prototypes that focus on demonstrating technical feasibility. The unique design approach and lessons learned by the team throughout this process culminated in a final design concept that was quite different than what the team originally assumed would be the design concept initially. A summary of the more usercentered final design concept is also provided.

McGowan, Anna-Maria↗

Modeling to Mars: a NASA Model Based Systems Engineering Pathfinder Effort

The NASA Engineering Safety Center (NESC) Systems Engineering (SE) Technical Discipline Team (TDT) initiated the Model Based Systems Engineering (MBSE) Pathfinder effort in FY16. The goals and objectives of the MBSE Pathfinder include developing and advancing MBSE capability across NASA, applying MBSE to real NASA issues, and capturing issues and opportunities surrounding MBSE. The Pathfinder effort consisted of four teams, with each team addressing a particular focus area. This paper focuses on Pathfinder team 1 with the focus area of architectures and mission campaigns. These efforts covered the timeframe of February 2016 through September 2016. The team was comprised of eight team members from seven NASA Centers (Glenn Research Center, Langley Research Center, Ames Research Center, Goddard Space Flight Center IV&V Facility, Johnson Space Center, Marshall Space Flight Center, and Stennis Space Center). Collectively, the team had varying levels of knowledge, skills and expertise in systems engineering and MBSE. The team applied their existing and newly acquired system modeling knowledge and expertise to develop modeling products for a campaign (Program) of crew and cargo missions (Projects) to establish a human presence on Mars utilizing In-Situ Resource Utilization (ISRU). Pathfinder team 1 developed a subset of modeling products that are required for a Program System Requirement Review (SRR)/System Design Review (SDR) and Project Mission Concept Review (MCR)/SRR as defined in NASA Procedural Requirements. Additionally, Team 1 was able to perform and demonstrate some trades and constraint analyses. At the end of these efforts, over twenty lessons learned and recommended next steps have been identified.

Phojanamongkolkij, Nipa↗