Search NASA⌕ Search

SEARCH · Search NASA

Results for “capability”

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 397 records · Page 22

NASA Enterprise Managed Cloud Computing (EMCC): Delivering an Initial Operating Capability (IOC) for NASA use of Commercial Infrastructure-as-a-Service (IaaS)

In 2016, Ames supported the NASA CIO in delivering an initial operating capability for Agency use of commercial cloud computing. This presentation provides an overview of the project, the services approach followed, and the major components of the capability that was delivered. The presentation is being given at the request of Amazon Web Services to a contingent representing the Brazilian Federal Government and Defense Organization that is interested in the use of Amazon Web Services (AWS). NASA is currently a customer of AWS and delivered the Initial Operating Capability using AWS as its first commercial cloud provider. The IOC, however, designed to also support other cloud providers in the future.

IT Governance for Cloud Computing↗

Medical Data Architecture Capabilities and Design

Mission constraints will challenge the delivery of medical care on a long-term, deep space explorationmission. This type of mission will be restricted in the availability of medical knowledge, skills, procedures and resourcesto prevent, diagnose, and treat in-flight medical events. Challenges to providing medical care are anticipated, includingresource and resupply constraints, delayed communications and no ability for medical evacuation. The Medical DataArchitecture (MDA) project will enable medical care capability in this constrained environment.The first version of thesystem, called Test Bed 1, includes capabilities for automated data collection, data storage and data retrieval to provideinformation to the Crew Medical Officer (CMO). Test Bed 1 seeks to establish a data architecture foundation and developa scalable data management system through modular design and standardized interfaces. In addition, it will demonstrateto stakeholders the potential for an improved, automated, flow of data to and from the medical system over the currentmethods employed on the International Space Station (ISS). It integrates a set of external devices, software andprocesses, and a Subjective, Objective, Assessment, and Plan (SOAP) note commonly used by clinicians. Medical datalike electrocardiogram plots, heart rate, skin temperature, respiration rate, medications taken, and more are collectedfrom devices and stored in the Electronic Medical Records (EMR) system, and reported to crew and clinician. Devicesintegrated include the Astroskin biosensor vest and IMED CARDIAX electrocardiogram (ECG) device with INEED MDECG Glove, and the NASA-developed Medical Dose Tracker application.The system is designed to be operated as astandalone system, and can be deployed in a variety of environments, from a laptop to a data center. The system isprimarily composed of open-source software tools, and is designed to be modular, so new capabilities can be added. Thesoftware components and integration methods will be discussed.

Exploration medical system↗

Defining Medical Capabilities for Exploration Missions

Exploration-class missions to the moon, Mars and beyond will require a significant change in medical capability from today's low earth orbit centric paradigm. Significant increases in autonomy will be required due to differences in duration, distance and orbital mechanics. Aerospace medicine and systems engineering teams are working together within ExMC to meet these challenges. Identifying exploration medical system needs requires accounting for planned and unplanned medical care as defined in the concept of operations. In 2017, the ExMC Clinicians group identified medical capabilities to feed into the Systems Engineering process, including: determining what and how to address planned and preventive medical care; defining an Accepted Medical Condition List (AMCL) of conditions that may occur and a subset of those that can be treated effectively within the exploration environment; and listing the medical capabilities needed to treat those conditions in the AMCL. This presentation will discuss the team's approach to addressing these issues, as well as how the outputs of the clinical process impact the systems engineering effort.

Hailey, M.↗

The Evolution of Payload Data Capabilities on the Commercial Visiting Vehicles that Service the International Space Station

In 2008, NASA awarded the first contracts to U.S. commercial companies to deliver cargo and supplies to the International Space Station (ISS). These contracts, called the first phase of Commercial Resupply Services (CRS1), were awarded to Space Exploration Technologies (SpaceX) and Orbital Sciences. Under the CRS1 contracts, commercial visiting vehicles not only provide a couple tons of cargo to the ISS each mission, but they also provide the ability for payloads to be transferred to the ISS in an active, powered state. Prior to the start of the CRS1 program, most vehicles that serviced the ISS transported science experiments as passive cargo. Therefore, the CRS1 program through offering frequent flight opportunities with powered payload transport capability ushered in a new era in which NASA and payload developers could reimagine operational concepts for payloads during the transit phase to and from the ISS. To take advantage of this powered payload transport capability, NASA first added requirements under the CRS1 program for the commercial vehicles to provide telemetry monitoring services for pressurized payloads to give payload developers situational awareness during the transport phase. Since then, payload developer use-cases for visiting vehicle data services during free-flight have evolved with each new commercial visiting vehicle contract to cover a variety of payload monitoring and control abilities. Additional commercial contracts include the Commercial Crew Transportation Capability (CCtCap) contracts that were awarded to SpaceX and Boeing, and the second phase of Commercial Resupply Services (CRS2) contracts that were awarded to SpaceX, Orbital ATK (formerly Orbital Sciences), and Sierra Nevada Corporation. Commercial crew flights will commence in 2018, and the first flight under the CRS2 program is currently planned for 2019.

Wiggins, Lindsay M.↗

The Evolution of Payload Data Capabilities on the Commercial Visiting Vehicles that Service the International Space Station

For over 10 years, NASA has been working with U.S.-based commercial companies to support the design, development, and operations of new commercial space vehicles. The purpose of these vehicles is to provide cargo and crew transportation services to the International Space Station (ISS) and to stimulate the commercial space transportation industry to Low-Earth Orbit (LEO). Along with the ability to provide a couple tons of cargo to the ISS each mission, the commercial visiting vehicles also provide the ability to transfer NASA payloads to and from the ISS in an active, powered state. To take advantage of this capability, NASA requirements for the data services that payloads need while they are integrated into the visiting vehicles have grown with each set of commercial contracts. Today, NASA desires for payload data services encompass a variety of capabilities including payload health and status (H&S) telemetry monitoring, visiting vehicle environment data monitoring, and payload commanding. The intent of these capabilities is to provide payload developers with situational awareness and the ability to quickly diagnose any problems with payload operations prior to vehicle docking or post-landing to support immediate troubleshooting response. As new requirements for payload data services have emerged over the years, the ISS Payload Operations Integration Center (POIC) at the NASA Marshall Space Flight Center (MSFC) has established ground segment interfaces to the visiting vehicle control centers to enable payload developers to use these services. Many technical and programmatic challenges have been faced while establishing these interfaces. The most significant challenge faced has been in finding the right balance amongst providing interfaces to payloads that are compatible with the ISS so that payload hardware or software changes are not necessary to ensure compatibility with the visiting vehicles; keeping POIC ground system development costs low by standardizing implementation approaches across commercial vehicle partners; and fostering commercialization through supporting vendor-unique implementations that are commercially economical. This paper will first detail the data services that will be available to payload users under each commercial visiting vehicle contract. Secondly, this paper will offer discussion of the most significant technical and programmatic challenges faced to-date in offering these new data services to payload developers.

Wiggins, Lindsay M.↗

Justification of Crew Function and Function Capability for Long Duration Deep Space Habitation

There are currently no established standards or guidelines that define the functions to be present in habitats for use beyond Low Earth Orbit (LEO), or for the capabilities of those functions. There is limited human experience with long duration space habitation, none of which is beyond LEO. There is significantly less experience with even short duration human habitation beyond LEO. Studies since the Apollo program that have proposed long duration habitats have applied inconsistent functionality, yet these functions have substantial implications for spacecraft mass and volume. There are also numerous aspects of human space flight beyond LEO that have implications for these functions. This paper develops a method for design teams to identify and justify the functions and capabilities to include in long duration habitats intended for use beyond LEO. Finally, human-in-the-loop testing methods are recommended for use in the early spacecraft design stages to ensure that the habitat will successfully provide the intended functions and capabilities.

Howard, Robert L.↗

New Capabilities, Products and Usage of NASA Earth Imagery for Near Real Time Applications

NASA's Worldview and Global Imagery Browse Services (GIBS) have provided near real time (NRT) imagery to the public since 2011 and continue to add new capabilities and products. As a web map app for GIBS, Worldview (https://worldview.earthdata.nasa.gov) has recently added new features to support NRT applications such as a "before" and "after" comparison capability and support for geostationary imagery. As an open set of standards-based web map services, GIBS (https://earthdata.nasa.gov/gibs) has added several new NRT imagery products and will soon add new capabilities for better integration with Geographic Information System (GIS) clients. One of NASA's original NRT imagery systems and a long-running workhorse, Rapid Response, has been retired and replaced with a modern, mobile-friendly, and low-bandwidth app dubbed Worldview Snapshots (https://wvs.earthdata.nasa.gov). Finally, this presentation will demonstrate recent usage of these tools and services by those in the NRT community.

Boller, R.↗

Technical Capability Level 2 Unmanned Aircraft System Traffic Management (UTM) Flight Demonstration: Description and Analysis

NASA's UAS Traffic Management (UTM) project concluded its second flight demonstration activity in late October 2016. This activity demonstrated the capabilities and functionality incorporated into its Technical Capability Level 2 (TCL2) concept, which envisions future operations that are low density, capable of being performed over sparsely populated areas, and allow for a concurrent mix of longer duration, beyond visual-line-of-sight flights and shorter flights within visual-line-of-sight (VLOS). To incorporate these features into a flight demonstration, a scenario-based approach was taken to address different aspects of the TCL2 environment and to meet defined objectives. This paper will describe elements of how the flight activity was conducted and present analyses regarding UTM operations, system messages, and alerting as they pertained to meeting the demonstration objectives and shedding light on research questions and lessons learned.NASA was able to successfully demonstrate complex UTMoperations in a TCL 2 environment in collaboration withindustry partners and the Reno-Stead Airport UAS test range.A scenario-based approach to the demonstration provided arelevant means through which the key elements and objectivesof the test could be captured. Although issues were identifiedthrough the testing and feedback of test participants, theoverall results were in line with the overall UTM objective ofsafely enabling large-scale UAS operations in low altitudeairspace.

Homola, Jeffrey↗

Future Planetary Instrument Capabilities Made Possible by Micro- and Nanotechnology

A number of new instrument capabilities are currently in maturation for future in situ use on planetary science missions. Moving beyond the impressive in situ instrumentation already operating in planetary environments beyond Earth will enable the next step in scientific discovery. The approach for developing beyond current instrumentation requires a careful assessment of science-driven capability advancement. To this end, two examples of instrument technology development efforts that are leading to new and important analytical capabilities for in situ planetary science will be discussed: (1) an instrument prototype enabling the interface between liquid separation techniques and laser desorption/ionization mass spectrometry and (2) an addressable excitation source enabling miniaturized electron probe microanalysis for elemental mapping of light and heavy elements.

Getty, Stephanie A.↗

Development of an Accepted Medical Condition List for Exploration Medical Capability Scoping

The Accepted Medical Conditions List (AMCL) is a product designed to provide a traceable, repeatable, evidence-based consensus process for scoping the medical capability needs for future design reference missions (DRMs) and upcoming programs. These include a Mars transit DRM and a shorter duration cis-lunar DRM. The development of a baseline AMCL by the Exploration Medical Capability (ExMC) Element will assist the effort to identify high priority medical capabilities for inclusion in mission and vehicle planning and provide traceable and documented clinical needs to the Systems Engineering teams tasked with requirements development and design work.

Medical Condition List↗

Capability Considerations for Enhancing Safety on Long Duration Crewed Missions: Insights from a Technical Interchange Meeting on Autonomous Crew Operations

As future flight crews on long duration deep space missions are expected to operate more autonomously, considerations must be given to onboard capabilities and human-computer teaming that will fortify the safety net traditionally provided by the Mission Control Center. In August 2018, the Human Factors and Behavioral Performance Element of NASA's Human Research Program convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center to address how intelligent technologies can be utilized to augment crew capabilities to support real-time anomaly response. In this paper, we highlight three topic areas discussed at the TIM that have direct implications for future crew anomaly response capabilities: smart structures, cognitive assistants, and manpower.

autonomous crew operations↗

Supporting Crew Autonomy in Deep Space Exploration: Preliminary Onboard Capability Requirements and Proposed Research Questions. Technical Report of the Autonomous Crew Operations Technical Interchange Meeting

Communication delays are a critical challenge posed by long duration deep space exploration. Space missions historically have relied on an ever-present Mission Control Center (MCC) to direct operations in near real-time. As unanticipated anomalies that defeat fault detection and resolution systems do arise, the lack of real-time communication will significantly weaken what the MCC support represents: a reliable safety net for the flight crew through its deep and diverse areas of expertise and investigative resources. As a consequence, future space vehicles and habitats need to be equipped with capabilities to support the flight crew to operate with little or no ground support. Considerations must be given to vehicle and mission designs that will fortify the traditionally ground-centered safety net and forge new support systems, when communication delays exist. In August 2018, NASA’s Human Research Program, through its Human Factors and Behavioral Performance Element, convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center. The goal of the meeting was to gather input from NASA centers, industry, academia, and branches of the Department of Defense (DoD) to address how intelligent technologies can be applied to augment onboard capabilities to support crew anomaly response. The TIM featured 24 presentations by 29 speakers and hosted a total of 59 attendees, including 43 from 5 NASA centers (Ames, Johnson, Langley, Marshall, and Jet Propulsion Lab) and 4 from the DoD (3 from Army Research Lab and 1 from Naval Postgraduate School), with remaining attendees from academia (e.g., UC Davis, CMU) and industry (e.g., IBM, Siemens). Discussions were centered around three themes: standards and guidelines, lessons learned in analog environments, and technologies. To help provide a framework for discussion, a concept matrix describing anomaly response processes was created prior to the TIM (Figure 1, page 6). The matrix captures the steps involved (monitoring and detection, diagnosis, solution development and evaluation, solution implementation and verification, resolution documentation) as well as the resources and capabilities required to support these steps (data, knowledge, analysis, synthesis, resource management). A wallpaper size printout of the matrix was utilized at the TIM to solicit attendee inputs along the three themes; the activity garnered 108 submissions of ideas. Overall, what emerged from TIM discussions was a picture of mismatch between crew anomaly response needs and support that can be provided by existing intelligent technologies. The needs are broad, spanning multiple steps and processes/resources, with many of which lacking support from existing technologies, such as knowledge management throughout the steps of problem solving (especially in resolution documentation) and manpower management. The solutions provided by existing intelligent technologies are specific to the steps/processes that they are designed to support and constrained to solving only problems similar to those that have occurred before. What is lacking from technologies is typically made up by humans, specifically their complex critical thinking, creative problem solving, and domain expertise. In the end, the TIM highlighted the pressing need to support responses to onboard anomalies during autonomous crew operations, particularly those that have eluded the system tests, inspection, and other assurance processes. Such anomalies can potentially threaten crew and vehicle safety, as well as significantly impact overall operations with additional workload. These fairly rare events are difficult to anticipate and prepare for, given the state-of-the-art in intelligent technologies. This is true even for anomalies that stem from “unknown knowns”—cases in which there is sufficient external information to characterize the problem but the overall pattern fails to be recognized by the problem solver, or in which the internal knowledge needed to solve a problem is held tacitly and potentially accessible by the problem solver but not articulated. It follows that the ability to tackle anomalies lies not only with the availability of relevant information and knowledge but also their accessibility in times of need. To that end, we propose research questions along the following three broad themes: • How intelligent technologies can help make relevant knowledge and information available? • How intelligent technologies can help make relevant knowledge and information accessible? • How intelligent technologies can help support the crew operating as a team in anomaly response processes?

autonomous crew operations↗

Distributed Spacecraft Autonomy (DSA): Development of Swarm Autonomy Capability and Scalability for Spacecraft

The Distributed Spacecraft Autonomy project is developing a suite of software tools that enable an operator to command and receive data from a swarm as a single entity, enable a swarm to autonomously coordinate its actions via distributed decision making and reactive closed-loop control, and model swarm behavior in the presence of anomalies or failures. Our use case is the mapping of the electron density of the ionosphere using radio tomography by coordinating the selection of appropriate GPS channels, and by recording Total Electron Count (TEC)measurements. DSA will be demonstrated on board the NASA Ames Starling mission a swarm of four small, LEO spacecraft, scheduled to launch in 2021. We will also perform a ground demonstration with simulated and hardware-in-the-loop elements, to validate the tools for controlling swarms of up to 100 assets.The capability to communicate autonomously between the swarm satellites is demonstrated via a sophisticated simulation architecture. Historical Plasma sphere TEC data obtained via dual-band Novatel GPS Receivers are utilized as a representative input data set for the swarm. The representative TEC data and GPS satellite observability information is fed to the autonomous software package in place of a true real-time ground data collection process. The swarm satellites actively share status updates amongst one another and utilize multi-agent decision making to optimally identify regions of interest in the TEC distribution. The software,aware of the bandwidth limitations of the swarm satellites, prioritizes explorative measurements,which define the range of observability for the satellites, as well as exploitative measurements,which focus on maximizing the observance potential of regions with prolonged, elevated TEC density. The science of this study can ultimately be used to determine the dynamics and coupling of Earth's magnetosphere, ionosphere, and atmosphere and their response to solar and terrestrial inputs. The findings can be applied to the imaging of critical, transient phenomena in the magnetosphere in later missions. Meanwhile, the swarm autonomy capabilities have far reaching potential in future satellite missions.As an experimental demonstration of the autonomous capabilities of the network, a message is first printed within a core Flight Executive (cFE) application. Two cFE applications that communicate with one another within the same core Flight System (cFS) are shown.Communication between mission applications on the internal cFE bus is extended to utilize Data Distribution Service (DDS) for vehicle-to-vehicle networking. The DDS middle ware provides reliable delivery, routing, and topic subscription features over User Data gram Protocol (UDP).Leveraging Linux containerization, a networked set of satellite instances are generated by script to simulate swarm behavior. Swarm commanding and synchronization through the network is demonstrated under various topologies and data-loss conditions. Finally, autonomous swarms calability from 2 satellites to 100 satellites is shown.

Fugate, Jason↗

Current Test Capabilities of NASA Langley’s Arc-Heated Scramjet Test Facility

The Arc-Heated Scramjet Test Facility at NASA Langley Research Center has demonstrated itself repeatedly as a key contributor to fundamental hypersonic research and scramjet engine technology development in the Mach 4.7 to 8 range. Since its inception in the 1970’s, the facility has hosted numerous scramjet engine configurations that explored the performance and operability of airframe-integrated hydrogen-fueled scramjet flow path concepts, successfully maturing both analysis tools and design technique and methodology for hypersonic propulsion. Contributions to major programs include extensive tests of the hydrogen-fueled NASP and Hyper-X scramjet engines, and the hydrocarbon-fueled HIFiRE Flight 2 scramjet flow path, in addition to fundamental in-house research. The facility capabilities have expanded to include direct-connect flow path support, gaseous hydrocarbon fuels, dynamic trajectory simulation and extension of flight simulation down to Mach 2.2. The low-Mach upgrades include increased air flow rate and controls capability and two new low-Mach nozzles (Mach 2.2 and 3.5). The facility recently completed verification of the new operational range through successful envelope expansion tests with the Mach 2.2 nozzle. With these new modifications, the operating envelope for the facility is now Mach 2.2 – 8.0(+), with a demonstrated dynamic pressure simulation of 2000 psf at the low end, and margin available for even more. Lastly, a continuous run time of over 5 minutes has been demonstrated, indicating that run time is limited only by test hardware or back-pressure requirements. This paper will provide a detailed description of these previously unreported upgrades and expanded simulation capabilities.

Hypersonic↗

Strategic Deconfliction Performance: Results and Analysis from the NASA UTM Technical Capability Level 4 Demonstration

Unmanned Aircraft System (UAS) Traffic Management (UTM) refers to the service-based, cooperative approach to the management of small UAS in the National Airspace System that is safe, scalable, and fair. UTM provides the means to manage the airspace in a complementary manner that does not burden the current air traffic control workforce or infrastructure but allows the Air Navigation Service Provider to maintain its regulatory and operational authority of the airspace. A key feature of UTM is the ability to provide operators the means to strategically deconflict operations from others in the airspace through the digital exchange of information via supporting services. Through this approach, the four-dimensional operation volumes that encompass the intent of operators in a given area are discoverable and can be used for airspace awareness as well as planning conflict free operations that account for and avoid other operations. In certain cases, it is also possible to negotiate volume intersections for shared airspace use without the need to re-plan. In the NASA UTM concept, strategic deconfliction is the first layer of three in the overall conflict management model. The three layers of the conflict management model, which follow the International Civil Aviation Organization’s scheme [ICAO 2005] are: strategic conflict management, separate provision, and collision avoidance. In UTM, the strategic layer mostly occurs prior to departure, but is applicable to en route operations with sufficient planning horizon. The initial requirements for a strategic deconfliction capability within UTM are defined in a NASA publication [Rios 2018]. Within the concept and implementation of service-provided strategic deconfliction is the notion of priority. It is understood that there are instances in which an operation requires a priority designation within the UTM system and special handling accordingly to provide situation awareness and facilitate appropriate responses from other airspace users. Examples of situations requiring priority designation include: when an operator declares an emergency due to problems with the vehicle or its immediate surroundings; operations that are in support of certain organizations (e.g., public safety and first responders); or special missions that also require priority use of airspace (e.g., emergency medical deliveries). UAS Volume Reservations (UVRs) also relate to the topic of priority in the sense that the airspace that the volume encompasses has a different status or classification in which unassociated operations must vacate if inside, or avoid if outside, through strategic deconfliction with the volume. Operations that are specially permitted to access the UVR area are typically assigned priority status given the nature of their mission and their associated credentials. The ability to perform strategic deconfliction, handle certain operations with a priority distinction, and establish UVRs that are communicated throughout the UTM system, is predicated on an architecture that has been established through an evolutionary process in response to close collaboration with stakeholders from government and industry. Another important and influential aspect of these capabilities and architecture is the live, distributed flight tests that have been conducted across the Technical Capability Levels (TCLs) that culminated with a set of complex tests performed as part of TCL4 [Rios 2020]. The TCL4 flight test involved two FAA-designated UAS test sites building teams to collaborate with NASA’s UTM Project on the execution of several detailed, small UAS scenarios in urban environments.

conflict management↗

Distributed Spacecraft Autonomy - Development of Swarm Autonomy Capability and Scalability for Spacecraft

The Distributed Spacecraft Autonomy project is developing a suite of software tools that enable an operator to command and receive data from a swarm as a single entity, enable a swarm to autonomously coordinate its actions via distributed decision making and reactive closed-loop control, and model swarm behavior in the presence of anomalies or failures. Our use case is the mapping of the electron density of the ionosphere using radio tomography by coordinating the selection of appropriate GPS channels, and by recording Total Electron Count (TEC) measurements. DSA will be demonstrated onboard the NASA Ames Starling mission – a swarm of four small, LEO spacecraft, scheduled to launch in 2021. We will also perform a ground demonstration with simulated and hardware-in-the-loop elements, to validate the tools for controlling swarms of up to 100 assets. The capability to communicate autonomously between the swarm satellites is demonstrated via a sophisticated simulation architecture. Historical Plasmasphere TEC data obtained via dual-band Novatel GPS Receivers are utilized as a representative input dataset for the swarm. The representative TEC data and GPS satellite observability information is fed to the autonomous software package in place of a true real-time ground data collection process. The swarm satellites actively share status updates amongst one another and utilize multi-agent decision making to optimally identify regions of interest in the TEC distribution. The software, aware of the bandwidth limitations of the swarm satellites, prioritizes explorative measurements, which define the range of observability for the satellites, as well as exploitative measurements, which focus on maximizing the observance potential of regions with prolonged, elevated TEC density. The science of this study can ultimately be used to determine the dynamics and coupling of Earth’s magnetosphere, ionosphere, and atmosphere and their response to solar and terrestrial inputs. The findings can be applied to the imaging of critical, transient phenomena in the magnetosphere in later missions. Meanwhile, the swarm autonomy capabilities have far reaching potential in future satellite missions. As an experimental demonstration of the autonomous capabilities of the network, a message is first printed within a core Flight Executive (cFE) application. Two cFE applications that communicate with one another within the same core Flight System (cFS) are shown. Communication between mission applications on the internal cFE bus is extended to utilize Data Distribution Service (DDS) for vehicle-to-vehicle networking. The DDS middleware provides reliable delivery, routing, and topic subscription features over User Datagram Protocol (UDP). Leveraging Linux containerization, a networked set of satellite instances are generated by script to simulate swarm behavior. Swarm commanding and synchronization through the network is demonstrated under various topologies and data-loss conditions. Finally, autonomous swarm scalability from 2 satellites to 100 satellites is shown.

Distributed Autonomy↗

Technology Capability Needs of Future Earth Science Missions

Technology capability needs for future Earth science space missions have been collected as an input to NASA's New Millenium Program. Candidate technologies to meet these capability needs have been identified and a set of candidate mission architectures developed. This paper describes the process that was used to develop the capability needs and lists the needs that resulted from that process.

New↗

Hot Structure and High-Temperature Material Capability

This presentation give an overview of NASA Langley Research Center capability in the technical area of structures and high-temperature materials. Included is an overview of the capability, test facilities, analysis capability, and recent work.

Thermal↗