Search NASA⌕ Search

SEARCH · Search NASA

Results for “reusable resources”

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 127 records · Page 7

Filling in Subsurface Storage Open Data Gaps - Updates to CCS Data Availability on EDX and EDX Spatial (FWP-1022465)

There is a need to preserve and efficiently access data resources to drive the next generation of research and development while ensuring compliance with DOE regulations. Over the last 10+ years, there has been ongoing efforts by the DOE Carbon Storage Program to ensure that there is effective data curation and preservation of DOE funded research leveraging the NETL-FECM data repository, the Energy Data eXchange (EDX). This talk presents updates about ongoing efforts to continue to support the mission of ensuring that carbon storage data is findable, accessible, interoperable, and reusable to the carbon storage stakeholder community through EDX and EDX Spatial. Presented at the NETL Carbon Management Review Meeting, Pittsburgh, 2024.

Morkner, Paige↗

Accelerating the Design of Space Vehicles

One of NASA's key goals is to increase the safety and reduce the cost of space transportation. Thus, a key element of NASA's new Integrated Space Transportation Plan is to develop new propulsion, structures, and operations for future generations of reusable launch vehicles (RLVs). As part of this effort to develop the next RLV, the ClCT Program's Computing, Networking, and Information Systems (CNIS) Project is developing and demonstrating collaborative software technologies that use the collective power of the NASA Grid to accelerate spacecraft design. One of these technologies, called AeroDB, automates the execution and monitoring of computational fluid dynamics (CFD) parameter studies on the NASA Grid. About the NASA Grid The NASA Grid, or Information Power Grid,. is being developed to leverage the distributed resources of NASA's many computers. instruments, simulators, and data storage systems. The goal is to use these combined resources to sdve difficult NASA challenges, such as iimulating the entire flight of a space vehicle from ascent to descent.To realize the vision of the NASA Grid, the CNIS Project is developing the software framework and protocols for building domain-specific environments and interfaces, new Grid services based on emerging industry standards, and advanced networking and computing testbeds to support new Grid-based applications such as AeroDB.

Laufenberg, Larry↗

Trans-Global Mission Architectures

Mission operations include the utilization of both space and ground resources to achieve mission objectives. Future architectures will make the spacecraft a node on a distributed system, thus expanding the scope of missions beyond the global scale. The history and evolution of planetary mission operations are outlined, together with the current global involvement in planetary missions. The modular nature and reuse of the supporting ground data systems, and the inclusion of automation and dedicated software in space missions, are discussed. A trans-global mission architecture is presented, and consists of an extension of a layered reusable mission operations architecture to create an open ground/space operations system. Concurrent mission engineering with such trans-global structures is discussed.

Anderson, Barbara V.↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.

Turner, Susan↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.

Turner, Susan↗

Informing Wildfire Needs: The Expanded User Interface of NASA's Fire Information for Resource Management System (Firms)

As the global community continues to experience, and respond to, living in a changing environment, access to tools, technologies, and timely data utilized by an increasingly diverse set of stakeholders is increasing. This year, 2023, has thus far seen an unprecedented number of extreme events, increasingly driven by changes in the climate and a strong 2023 ENSO pattern. In Canada, a record number of wildfires, and associated weather events, evacuations, and infrastructure and habitat destruction has taken place, and is ongoing. Large swaths of Greece have experienced similar wildfire destruction. Most recently, Maui has experienced destructive wildfires, and early 2023 saw massive wildfires in Chile. NASA's Fire Information for Resource Management System, or FIRMS, has a fifteen-year history of providing timely and comprehensive data and information on wildfires to stakeholders. FIRMS was initially developed in 2007 by the University of Maryland, with funds from NASA's Applied Sciences Program and the United Nations Food and Agriculture Organization (UN FAO), to provide near real-time active fire Locations to natural resource managers that faced challenges obtaining timely satellite-derived fire information. FIRMS has consistently evolved to address the needs of stakeholders Living in a changing environment; in 2012 it transitioned to NASA LANCE and in 2021 through a partnership between NASA and the US Forest Service, an updated version of FIRMS was released for the US and Canada. As NASA and other federal agencies continue to accelerate Open Science through integrated efforts such as the Year of Open Science, the provision of readily discoverable, findable, accessible, interoperable, reusable data represents a major focus to facilitate equitable outcomes. FIRMS supports this acceleration in Open Science by continuing to provision data and information for its traditional user base, while addressing the novel user needs of an increasingly diverse set of stakeholders seeking robust, reliable, transparently generated data and information. Increasingly, FIRMS is utilized by citizen scientists and individuals directly affected by wildfires - through evacuations, risks to structures/homes, poor air quality. etc. FIRMS has also been Leveraged to detect and assess the impacts resulting from ongoing conflicts. This further highlights the multi-faceted impacts of wildfires and other events. In the Fall of 2023, FIRMS will release an expanded User Interface (UI). This interface captures and reflects the needs of, and input from, a multitude of users. These users range from federal agency representatives to non-government organizations to the private sector to citizen science entities. To respond to this expansive and diverse user need base, the updated FIRMS UI will capture a range of features to support those beginning to explore the range of data and tools available to inform wildfire awareness and knowledge. These users are supported through a Basic Mode interface, furnishing access to a light set of functionalities that provision straight-forward, readily usable information and data, and ingestible knowledge. The Advanced Mode interface supports those stakeholder groups already proficient in navigating FIRMS. These stakeholders, representing fire managers and others, perform active fire management and tactical wildfire response activities. For these stakeholders, additional datasets have been included which require in-depth knowledge of both the utility as well as the caveats of such datasets. Additional functionalities have also been embedded to aid specific user queries. The expanded UI will introduce a new Experimental Mode. The focus of this UI will be to support the provision of emerging and innovative datasets that are in development for review and comment by the user community Examples include post-fire products generated by NASA's Earth Information System (EIS) Fire. This presentation will provide an overview of the expanded FIRMS UI. We will discuss how this UI is designed to be scalable and support the unique needs of an expanding and diverse user base. We will highlight key features, elements, and datasets, and describe how user needs have informed and guided the design of the UI. We will also share recent use cases to convey, and increase awareness, among conference participants. As the global community faces more extreme wildfires, due to climate variability and change, there is an increased need for reliable data to inform, manage, and mitigate the impacts of these events. Through this work, NASA FIRMS is striving to level the playing field, by making information accessible to all; from policy makers to the private sector to historically marginalized communities. In doing so, NASA is promoting the all-hands-on-deck response needed to minimize the impacts of wildfires and harness the strengths of open science to address the greatest environmental challenge faced.

Jenny Hewson↗

Space Shuttle Corrosion Protection Performance

The reusable Manned Space Shuttle has been flying into Space and returning to earth for more than 25 years. The launch pad environment can be corrosive to metallic substrates and the Space Shuttles are exposed to this environment when preparing for launch. The Orbiter has been in service well past its design life of 10 years or 100 missions. As part of the aging vehicle assessment one question under evaluation is how the thermal protection system and aging protective coatings are performing to insure structural integrity. The assessment of this cost resources and time. The information is invaluable when minimizing risk to the safety of Astronauts and Vehicle. This paper will outline a strategic sampling plan and some operational improvements made by the Orbiter Structures team and Corrosion Control Review Board.

Curtis, Cris E.↗

STS-80 Mission Highlights Resource Tape

The flight crew of STS-80, Cmdr. Kenneth D. Cockrell, Pilot Kent V. Rominger, Mission Specialists, Tamara E. Jernigan, Thomas D. Jones, and F. Story Musgrave are seen performing pre-launch activities such as eating the traditional breakfast, being suited-up, and riding out to the launch pad. Also, included are various panoramic views of the shuttle on the pad. The crew is readied in the 'white room' for their mission. After the closing of the hatch and arm retraction, launch activities are shown including the countdown, engine ignition, launch, and the separation of the Solid Rocket Boosters (SRB) from the shuttle. The crew completes the first major objective of the mission with the deployment of the Orbiting Retrievable Far and Extreme Ultraviolet Spectrometer (ORFEUS) on the reusable Shuttle Pallet Satellite. The crew than begins final preparations for the release of Wake Shield. Jones powers up the shuttle's Canadian-built robot arm and grapples the satellite, while Jernigan powers up the Orbiter Space Vision System, which will be used to track precisely the Wake Shield's location. Cockrell places Columbia in a gravity gradient attitude to minimize disturbances during the release. Jones uses the robot arm to hold Wake Shield in position for a two-and-a-half hour cleansing by atomic oxygen molecules before moving the arm to the deploy position. The failure of the hatch to properly open causes the cancellation of all EVA's planned for this mission by Jernigan and Jones. The mission ends with the shuttle landing at the Kennedy Space Center.

Source record↗

Aligning NASA Earth Science Data Stewardship with FAIR Principles: Outcomes, Recommendations, and Future Directions

The FAIR Principles—Findable, Accessible, Interoperable, and Reusable—offer a widely accepted framework for improving the sharing and reuse of digital scientific data by both human and machine users. Following these principles is critical for effective scientific data stewardship, broader scientific collaboration, and compliance with federal and agency data policies. This paper, based on the work of NASA’s Open, Free, and FAIR Working Group (O’FAIR WG) under the Earth Science Data Systems Program, presents an overview of how FAIR is being applied within NASA’s Earth science data landscape. It highlights ongoing progress and challenges, identifies FAIR-enabling resources, and offers recommendations and strategic actions to enhance the FAIRness of NASA-funded open and free Earth science data products. The FAIR-enabling resources identified underscore the vital role of NASA's existing enterprise processes, standards, tools, and infrastructures in supporting FAIR implementation. Our findings show strong performance in making NASA Earth science data more findable and accessible. However, further work is needed—especially in enhancing interoperability, so that different systems and tools can better understand and exchange data. This is especially important for enabling machine-driven discovery and analysis. We emphasize the importance of a balanced strategy that combines a centralized, top-down approach—focused on building enterprise-level capabilities and processes—with a decentralized, bottom-up approach driven by discipline-specific needs and community practices. We advocate for coordinated efforts to enhance (meta)data interoperability to facilitate seamless data and information sharing and exchange of Earth science data both within NASA and across other agencies managing Earth science data.

Data Product↗

AdaNET research plan

The mission of the AdaNET research effort is to determine how to increase the availability of reusable Ada components and associated software engineering technology to both private and Federal sectors. The effort is structured to define the requirements for transfer of Federally developed software technology, study feasible approaches to meeting the requirements, and to gain experience in applying various technologies and practices. The overall approach to the development of the AdaNET System Specification is presented. A work breakdown structure is presented with each research activity described in detail. The deliverables for each work area are summarized. The overall organization and responsibilities for each research area are described. The schedule and necessary resources are presented for each research activity. The estimated cost is summarized for each activity. The project plan is fully described in the Super Project Expert data file contained on the floppy disk attached to the back cover of this plan.

Mcbride, John G.↗

Uncrewed Lunar Surface Operations and Support Activities

Sustained human presence on the surface of the Moon and future missions to Mars require increased independence from surface crews and Earth-based mission control to operate efficiently, safely, and reliably. The time for surface crews to perform tasks will be limited. Extravehicular activities by surface personnel are burdensome and time-consuming, even when a continuous human presence on the surface occurs. Identifying and balancing human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle will be essential to achieve mission objectives. Among these objectives are attaining a sustained human presence, improving performance and mission effectiveness, reducing operations and maintenance (O&M) costs, and ensuring operations that are robust to communication delays. To achieve these objectives, an operational shift toward increased automation and autonomy with less reliance on humans is needed. Uncrewed lunar surface operations and support activities occur when surface crews are not present or are independent of surface crew timeline activities requiring no surface crew oversight or intervention. These uncrewed surface opportunities can also be planned to minimize crew workload that avoids routine maintenance and support tasks, thus maximizing crew exploration time. Uncrewed preparations such as staging and prepositioning equipment and materials before the crew arrives could improve crew task efficiency. Additional opportunities exist to conduct uncrewed science, exploration, and utilization. Uncrewed surface architecture functions can include science and exploration; habitation; launch and landing support; surface communication and navigation; surface power generation and distribution; human surface mobility; lifting, handling, manipulating; excavation, construction, and site preparation; logistics management; maintenance and repair; surface resource utilization; integrated site operations and shared support services (e.g., site scheduling/prioritization, dust mitigation/contamination control, and surface safety). Early robotic lunar surface campaigns will provide information on the availability of resources, such as oxygen and water, and demonstrate surface-based technologies. After the Artemis III human lunar return mission, a series of landers will deliver surface systems, cargo, supplies, science packages, spare parts, and commodities. A balance of crewed and uncrewed surface operations will enable a sustained lunar surface presence at the South Pole of the Moon at a site that will be known as the Artemis Base Camp (ABC). It is envisioned that base camp operations on and around the Moon will then help prepare for the mission durations and activities needed to support the first human mission to Mars. Before long-duration crew missions to the base camp can occur, the necessary surface infrastructure will be pre-deployed and verified operational. Surface assets will be teleoperated and remotely managed from Earth. Additionally, robotic and short-duration crewed missions to the ABC will ensure the site’s merit to achieve long-term science objectives, availability of usable resources, and that terrain, seasonal variations, and illumination conditions are acceptable. ABC will consist of different areas where specific functions and services are rendered, including: • Launch and Landing Area • Habitation Area • Power Production Area • Resource Areas Launch and Landing Area—The launch and landing area will support associated functions for the arrival and departure of vehicles, such as crewed landing and ascent and uncrewed cargo deliveries and offloading. It will evolve from an unimproved site at the beginning of the exploration campaign to a more sustainable landing and launch area that can support repeated arrivals and departures. Initial uncrewed Lunar Terrain Vehicle (LTV) surface operations may include emplacement of navigation beacons and communication equipment, real-time video and photography of landing/liftoff events, and element repositioning, such as portable utility power (PUP) (applicable for other landed assets at other areas). Site preparations, such as surface leveling, soil compaction, and berm/path construction, may be needed for a more sustainable launch and landing area capable of accommodating vehicles that are increasingly more reusable and reduce the effects of plume surface interactions and ejecta impacts on nearby surface assets. During the ABC missions, cargo and logistics will be delivered to the lunar surface via robotic cargo landers before the crew arrives. These shipments, which can arrive in pressurized logistics carriers, will deliver the logistics necessary to support a crewed mission and include items such as food, water, equipment spares, etc. Providing the capability to retrieve, offload, and transport the logistics closer to the ABC site before the arrival of the crew will increase the overall efficiency of crew operations once they arrive. In the sustained phase of exploration, other supporting services may be needed, such as lander propellant servicing, surface power services, commodity refreshes, and additional inspection, maintenance, and repair capabilities, to sustain a cadence of extended personnel stays and cargo arrivals and departures. Habitation Area—Uncrewed support to surface habitation could involve supporting activation and pre-entry operations of the habitat while the crew is in orbit at the Gateway outpost preparing for a surface landing. Surface Habitat (SH) uncrewed operations may include bringing the cabin environment to a habitable temperature and air mix and activating other critical crew support systems. Potential crop production uncrewed tasks in the SH could also include autonomous watering and tending. Additionally, when the crew departs, the SH enters dormancy for the long period of uncrewed operation. A logistical staging area could also be collocated near the SH. If so, staging operations for crew supplies, waste re-location, and recycling operations may be opportunities for uncrewed operations. Power Production Area—The Fission Surface Power (FSP) element and its supporting distribution equipment provide power to surface elements as needed across the ABC to supplement day-to-day operations and survive lunar nights. Uncrewed support of this power system includes any initial LTV-assisted deployments of cables and other distributed equipment, associated electrical connections, and system testing and activation operations. Robotically performing some inspections, maintenance, or repair tasks on the power distribution equipment could reduce the surface crew workload. Resource Area— Uncrewed resource prospecting, mapping, and characterizing possible resource sites is likely to be time-consuming and represents an opportunity for uncrewed operations between crewed missions. Uncrewed mobile equipment operations will be needed in the extreme environments of permanently shadowed locations where resource extractions occur. As In-Situ Resource Utilization (ISRU) pilot plant operations begin, uncrewed surface support activities with available mobile and portable assets (LTV, PUP, etc.) will better support these operations. Any produced commodities can be stored at a centralized storage location for future use. Also associated with these operations is the use of mobile robotic excavators for resource acquisition and robotic/autonomous regolith processing. The waste tailings generated during excavation and regolith processing would also need to be transported and deposited at a dedicated location. Surface assets will continue operating between crew visits to maintain surface capabilities, conduct lunar surface science, technology demonstrations, and public outreach opportunities. Additionally, certain sustaining tasks that would consume valuable crew time could be performed before crew arrival, or after their departure. This capability may offer more affordable options to construct, activate, test, and maintain a broad set of surface assets. Telerobotically operated human surface mobility systems, such as the LTV and Pressurized Rover (PR), can be utilized for various tasks. Surface environmental conditions pose a distinct challenge for all these activities. Surface illumination and localized shadows are one such factor. Night-survival operations could consist of thermal management, battery pre-charging, and load shedding. Some surface systems may hibernate through the night and then awake and continue nominal operations. Uncrewed mobile assets may use a more adaptive approach to optimize their power and operations; one method is to follow the sunlight. Night-survival operations may be initiated remotely by teleoperation, automated, or accomplished by supervised autonomous operation. The ability to pre-deploy and control remote assets in orbit or on Mars before the arrival of the mission crew is a key capability that can be simulated on the moon. The base camp provides a venue where these advanced operational concepts, technologies, and autonomous methods and techniques, including the incorporation of time delays to simulate Earth-Mars latency can be replicated to help buy down future Mars mission risks. This paper will examine the evolution of uncrewed lunar surface operations and support activities. It will also discuss the lunar surface environmental conditions (thermal, lighting, terrain, topography, communications) along with the challenges they pose on uncrewed surface operations, and the performance of these activities with limited to minimal human interaction and/or teleoperation. Since lunar missions include Mars mission analogs, such investigation provides the framework for future uncrewed Mars mission support.

Mark E Lewis↗

Using C to build a satellite scheduling expert system: Examples from the Explorer Platform planning system

A C-based artificial intelligence (AI) development effort which is based on a software tools approach is discussed with emphasis on reusability and maintainability of code. The discussion starts with simple examples of how list processing can easily be implemented in C and then proceeds to the implementations of frames and objects which use dynamic memory allocation. The implementation of procedures which use depth first search, constraint propagation, context switching, and blackboard-like simulation environment are described. Techniques for managing the complexity of C-based AI software are noted, especially the object-oriented techniques of data encapsulation and incremental development. Finally, all these concepts are put together by describing the components of planning software called the Planning And Resource Reasoning (PARR) Shell. This shell was successfully utilized for scheduling services of the Tracking and Data Relay Satellite System for the Earth Radiation Budget Satellite since May of 1987 and will be used for operations scheduling of the Explorer Platform in Nov. of 1991.

Mclean, David R.↗

Using C to build a satellite scheduling expert system: Examples from the Explorer platform planning system

Recently, many expert systems were developed in a LISP environment and then ported to the real world C environment before the final system is delivered. This situation may require that the entire system be completely rewritten in C and may actually result in a system which is put together as quickly as possible with little regard for maintainability and further evolution. With the introduction of high performance UNIX and X-windows based workstations, a great deal of the advantages of developing a first system in the LISP environment have become questionable. A C-based AI development effort is described which is based on a software tools approach with emphasis on reusability and maintainability of code. The discussion starts with simple examples of how list processing can easily be implemented in C and then proceeds to the implementations of frames and objects which use dynamic memory allocation. The implementation of procedures which use depth first search, constraint propagation, context switching and a blackboard-like simulation environment are described. Techniques for managing the complexity of C-based AI software are noted, especially the object-oriented techniques of data encapsulation and incremental development. Finally, all these concepts are put together by describing the components of planning software called the Planning And Resource Reasoning (PARR) shell. This shell was successfully utilized for scheduling services of the Tracking and Data Relay Satellite System for the Earth Radiation Budget Satellite since May 1987 and will be used for operations scheduling of the Explorer Platform in November 1991.

Mclean, David R.↗

CFD applications in hypersonic flight

Design studies are underway for a variety of hypersonic flight vehicles. The National Aero-Space Plane will provide a reusable, single-stage-to-orbit capability for routine access to low earth orbit. Flight-capable satellites will dip into the atmosphere to maneuver to new orbits, while planetary probes will decelerate at their destination by atmospheric aerobraking. To supplement limited experimental capabilities in the hypersonic regime, CFD is being used to analyze the flow about these configurations. The governing equations include fluid dynamic as well as chemical species equations, which are solved with robust upwind differencing schemes. Examples of CFD applications to hypersonic vehicles suggest an important role this technology will play in the development of future aerospace systems. The computational resources needed to obtain solutions are large, but various strategies are being exploited to reduce the time required for complete vehicle simulations.

Edwards, T. A.↗

International Space Station as a Platform for Exploration Beyond Low Earth Orbit

The International Space Station (ISS) has established a new model for the achievement of the most difficult engineering goals in space: international collaboration at the program level with competition at the level of technology. This strategic shift in management approach provides long term program stability while still allowing for the flexible evolution of technology needs and capabilities. Both commercial and government sponsored technology developments are well supported in this management model. ISS also provides a physical platform for development and demonstration of the systems needed for missions beyond low earth orbit. These new systems at the leading edge of technology require operational exercise in the unforgiving environment of space before they can be trusted for long duration missions. Systems and resources needed for expeditions can be aggregated and thoroughly tested at ISS before departure thus providing wide operational flexibility and the best assurance of mission success. We will describe representative mission profiles showing how ISS can support exploration missions to the Moon, Mars, asteroids and other potential destinations. Example missions would include humans to lunar surface and return, and humans to Mars orbit as well as Mars surface and return. ISS benefits include: international access from all major launch sites; an assembly location with crew and tools that could help prepare departing expeditions that involve more than one launch; a parking place for reusable vehicles; and the potential to add a propellant depot.

Raftery, Michael↗

Some design constraints required for the assembly of software components: The incorporation of atomic abstract types into generically structured abstract types

It is nearly axiomatic, that to take the greatest advantage of the useful features available in a development system, and to avoid the negative interactions of those features, requires the exercise of a design methodology which constrains their use. A major design support feature of the Ada language is abstraction: for data, functions processes, resources, and system elements in general. Atomic abstract types can be created in packages defining those private types and all of the overloaded operators, functions, and hidden data required for their use in an application. Generically structured abstract types can be created in generic packages defining those structured private types, as buildups from the user-defined data types which are input as parameters. A study is made of the design constraints required for software incorporating either atomic or generically structured abstract types, if the integration of software components based on them is to be subsequently performed. The impact of these techniques on the reusability of software and the creation of project-specific software support environments is also discussed.

Johnson, Charles S.↗

Governing Data Findability, Accessibility, Interoperability and Reusability (FAIR) Compliance

The most recent data strategy documents at both the federal and NASA levels stipulate that systems should strive for the data they manage to be Findable, Accessible, Interoperable, and Reusable (FAIR). The NASA Life Sciences Portal (NLSP) has already begun leading efforts in this area for HRP, initiating efforts to comply with the FAIR principles. The broad interpretation of the FAIR principles has led to a plethora of tools that use a splay of metrics specifically but variably developed to judge how compliant data and systems are with the principles. A recent review [3] identified and studied 1,180 metrics across 20 publicly available tools for checking FAIR compliance of data and systems. Because of their very recent development, many organizations and data systems managers and developers have not yet had adequate time or resources to understand these FAIR compliance tools and metrics, their variations in design, accuracy or ease of application to their specific data sets and systems. Thus, it would be best for larger organizations like NASA to approach formulating a strategy for governance of FAIR compliance that can be flexibly applied and is adaptable to an evolving awareness knowledge of FAIR compliance methods and tools. In September 2024, the NASA Science Mission Directorate(SMD) organized a workshop on NASA science data repositories, including the topics of implementing FAIR and governing FAIR compliance across SMD. The initial part of these FAIR discussions focused on developing consensus around required science metadata fields. This is challenging given the diverse nature of NASA’s scientific data portfolio, the variety of metadata models and vocabularies used, and variable level of resources available to curate these data. Later discussion focused on three possible approaches to governing FAIR compliance: distributed, in which various programs, projects or systems define their own methods for assessing FAIR compliance, reporting results up appropriate management lines; centralized, in which higher-level organization(s) specify compliance tools or methods for the various data systems; and multi-level, in which a group comprised of individuals with expertise from multiple levels with organizations is formed to provide guidance and/or specifications for governing FAIR compliance. We report on the recommendations this session yielded, and how these might be shaped specifically to help implement and govern the compliance with FAIR of Human Research Program data and systems.

governance↗

Expert systems built by the Expert: An evaluation of OPS5

Two expert systems were written in OPS5 by the expert, a Ph.D. astronomer with no prior experience in artificial intelligence or expert systems, without the use of a knowledge engineer. The first system was built from scratch and uses 146 rules to check for duplication of scientific information within a pool of prospective observations. The second system was grafted onto another expert system and uses 149 additional rules to estimate the spacecraft and ground resources consumed by a set of prospective observations. The small vocabulary, the IF this occurs THEN do that logical structure of OPS5, and the ability to follow program execution allowed the expert to design and implement these systems with only the data structures and rules of another OPS5 system as an example. The modularity of the rules in OPS5 allowed the second system to modify the rulebase of the system onto which it was grafted without changing the code or the operation of that system. These experiences show that experts are able to develop their own expert systems due to the ease of programming and code reusability in OPS5.

Jackson, Robert↗