Search NASA⌕ Search

SEARCH · Search NASA

Results for “Architecture Development”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Lunar Node – 1: Initial Flight Results and the Role of Surface Psuedolites in Lunar Navigation

On February 22, 2024, Intuitive Machines NOVA-C lander, nick-named Odysseus, landed on the lunar surface, carrying with it a cadre of NASA scientific and technology demonstration payloads. These payloads and missions marked the first delivery of NASA instruments to operate from the lunar surface since the Apollo landings. One of these payloads is Lunar Node -1 (LN-1), a navigation beacon demonstration mission. The payload was designed and built by NASA’s Marshall Space Flight Center. The payload’s main goal was to demonstrate and provide insight into the use of lunar surface-based radio navigation aids. As part of the mission, LN-1 successfully conducted multiple one-way transmissions from the NOVA-C vehicle to Deep Space Network ground receivers using its onboard S-band transmitter, while being disciplined by an onboard Space Chip Scale Atomic Clock. LN-1 transmitted to DSN on an almost daily basis during transit to the moon, including two surface passes. The payload was originally plan to conduct 7-10 days of surface operation as an always-on beacon. These passes focused on evaluating two main navigation approaches: performance and stability of ranging using time-based transfer techniques on a cubesat size and grade platform, as well as one-way psuedonoise ranging approaches. To assess performance, the measurements were compared to independent navigation solutions using multiple approaches including: one-way Doppler tracking, two-way Doppler Tracking, and visual verification of the landing location provided by visual observations from orbital platforms. While the mission only conducted limited surface operations, the data provides some initial insight to performance form the lunar surface. These results are compared with initial ground-based testing as well as continued evaluation of the flight-space platform using multiple grades of oscillators for maintaining clock and frequency stability. These focus on the timing stability of platform in a deep-space environment as well variations in state determination. Given these insights, this paper provides additional description and evaluation of how this approach can be utilized as part of a broader lunar navigation architecture, such as being developed and deployed across multiple international space agencies. Analysis is provided to develop overall timing requirements and assessment of operational scenarios, such as orbit and surface location determination. In addition, the results support discussion as to how surface pseudolites could best be used within existing standard signal definitions, such as defined in the LunaNet Interoperability Specifications. This will consider concerns such as the near-/far- problem as well as operational considerations, including whether a beacon is better suited as two- or one-way ranging platform. The use cases are focused on how these psuedolites can provide additional coverage to augment and support planned operational coverage. For example, this analysis provides analysis of mid-latitude surface missions, where there may be limited geometry and availability of orbital relays. The results will show how these navigation psuedolites can fit within the developing architecture to provide additional robustness, capability, and support multiple use cases. Lastly, the paper will discuss challenges and next steps to be addressed in the implementation and testing of a follow-on payload and a continued path towards demonstration and integration of this capability into Lunar PNT architectures.

Evan J Anzalone↗
NASA NTRS1997

ASAC Executive Assistant Architecture Description Summary

In this technical document, we describe the system architecture developed for the Aviation System Analysis Capability (ASAC) Executive Assistant (EA). We describe the genesis and role of the ASAC system, discuss the objectives of the ASAC system and provide an overview of components and models within the ASAC system, discuss our choice for an architecture methodology, the Domain Specific Software Architecture (DSSA), and the DSSA approach to developing a system architecture, and describe the development process and the results of the ASAC EA system architecture. The document has six appendices.

Roberts, Eileen↗
NASA NTRS2015

A New Architecture for Extending the Capabilities of the Copernicus Trajectory Optimization Program

This paper describes a new plugin architecture developed for the Copernicus spacecraft trajectory optimization program. Details of the software architecture design and development are described, as well as examples of how the capability can be used to extend the tool in order to expand the type of trajectory optimization problems that can be solved. The inclusion of plugins is a significant update to Copernicus, allowing user-created algorithms to be incorporated into the tool for the first time. The initial version of the new capability was released to the Copernicus user community with version 4.1 in March 2015, and additional refinements and improvements were included in the recent 4.2 release. It is proving quite useful, enabling Copernicus to solve problems that it was not able to solve before.

Williams, Jacob↗
NASA NTRS1987

Fluid dynamics parallel computer development at NASA Langley Research Center

To accomplish more detailed simulations of highly complex flows, such as the transition to turbulence, fluid dynamics research requires computers much more powerful than any available today. Only parallel processing on multiple-processor computers offers hope for achieving the required effective speeds. Looking ahead to the use of these machines, the fluid dynamicist faces three issues: algorithm development for near-term parallel computers, architecture development for future computer power increases, and assessment of possible advantages of special purpose designs. Two projects at NASA Langley address these issues. Software development and algorithm exploration is being done on the FLEX/32 Parallel Processing Research Computer. New architecture features are being explored in the special purpose hardware design of the Navier-Stokes Computer. These projects are complementary and are producing promising results.

Townsend, James C.↗
NASA NTRS1993

Appendix C: Rapid development approaches for system engineering and design

Conventional system architectures, development processes, and tool environments often produce systems which exceed cost expectations and are obsolete before they are fielded. This paper explores some of the reasons for this and provides recommendations for how we can do better. These recommendations are based on DoD and NASA system developments and on our exploration and development of system/software engineering tools.

Source record↗
NASA NTRS2008

Intelligent Elements for ISHM

There are a number of architecture models for implementing Integrated Systems Health Management (ISHM) capabilities. For example, approaches based on the OSA-CBM and OSA-EAI models, or specific architectures developed in response to local needs. NASA s John C. Stennis Space Center (SSC) has developed one such version of an extensible architecture in support of rocket engine testing that integrates a palette of functions in order to achieve an ISHM capability. Among the functional capabilities that are supported by the framework are: prognostic models, anomaly detection, a data base of supporting health information, root cause analysis, intelligent elements, and integrated awareness. This paper focuses on the role that intelligent elements can play in ISHM architectures. We define an intelligent element as a smart element with sufficient computing capacity to support anomaly detection or other algorithms in support of ISHM functions. A smart element has the capabilities of supporting networked implementations of IEEE 1451.x smart sensor and actuator protocols. The ISHM group at SSC has been actively developing intelligent elements in conjunction with several partners at other Centers, universities, and companies as part of our ISHM approach for better supporting rocket engine testing. We have developed several implementations. Among the key features for these intelligent sensors is support for IEEE 1451.1 and incorporation of a suite of algorithms for determination of sensor health. Regardless of the potential advantages that can be achieved using intelligent sensors, existing large-scale systems are still based on conventional sensors and data acquisition systems. In order to bring the benefits of intelligent sensors to these environments, we have also developed virtual implementations of intelligent sensors.

Schmalzel, John L.↗
NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗
NASA NTRS1999

Thermal and Mechanical Microspacecraft Technologies for X-2000 Future Deliveries

Thermal and mechanical technologies are an important part of the X-2000 Future Delivery (X-2000 FD) microspacecraft. A wide range of future space missions are expected to utilize the technologies and the architecture developed by the X-2000 FD. These technologies, besides being small in physical size, make the tiny spacecraft robust and flexible. The X2000 FD architecture is designed to be highly reliable and suitable for a wide range of missions such as planetary landers/orbiters/flybys, earth orbiters, cometary flybys/landers/sample returns, etc. One of the key ideas used in the development of these technologies and architecture is that several functions be in included in each of the thermal and mechanical elements. One of the thermal architecture being explored for the X-2000 FD microspacecraft is integrated thermal energy management of the complete spacecraft using a fluid loop. The robustness and the simplicity of the loop and the flexibility with which it can be integrated in the spacecraft have made it attractive for applications to X-2000 FD. Some of the thermal technologies to be developed as a part of this architecture are passive and active cooling loops, electrically variable emittance surfaces, miniature thermal switches, and specific high density electronic cooling technologies. In the mechanical area, multifunction architecture for the structural elements will be developed. The multifunction aspect is expected to substantially reduce the mass and volume of the spacecraft. Some of the technologies that will be developed are composite material panels incorporating electronics, cabling, and thermal elements in them. The paper to be presented at the 1999 conference, will describe the progress made so far in the microspacecraft thermal and mechanical technologies and approaches for the X2000 Future Deliveries microspacecraft.

Birur, Gaj↗
NASA NTRS2003

Shuttle Payload Ground Command and Control: An Experiment Implementation Combustion Module-2 Software Development, STS-107

This presentation covers the design of a command and control architecture developed by the author for the Combustion Module-2 microgravity experiment, which flew aboard the STS-107 Shuttle mission, The design was implemented to satisfy a hybrid network that utilized TCP/IP for both the onboard segment and ground segment, with an intermediary unreliable transport for the space to ground segment. With the infusion of Internet networking technologies into Space Shuttle, Space Station, and spacecraft avionics systems, comes the need for robust methodologies for ground command and control. Considerations of high bit error links, and unreliable transport over intermittent links must be considered in such systems. Internet protocols applied to these systems, coupled with the appropriate application layer protections, can provide adequate communication architectures for command and control. However, there are inherent limitations and additional complexities added by the use of Internet protocols that must be considered during the design. This presentation will discuss the rationale for the: framework and protocol algorithms developed by the author. A summary of design considerations, implantation issues, and learned lessons will be will be presented. A summary of mission results using this communications architecture will be presented. Additionally, areas of further needed investigation will be identified.

Carek, David Andrew↗
NASA NTRS1999

Thermal and Mechanical Microspacecraft Technologies for Deep Space Systems Program X2000 Future Deliveries

Thermal and mechanical technologies are an important part of the Deep Space Systems Technology (DSST) Program X2000 Future Deliveries (FD) microspacecraft. A wide range of future space missions are expected to utilize the technologies and the architecture developed by DSST FD. These technologies, besides being small in physical size, make the tiny spacecraft robust and flexible. The DSST FD architecture is designed to be highly reliable and suitable for a wide range of missions such as planetary landers/orbiters/flybys, earth orbiters, cometary flybys/landers/sample returns, etc. Two of the key ideas used in the development of thermal and mechanical technologies and architectures are: 1) to include several of the thermal and mechanical functions in any given single spacecraft element and 2) the architecture be modular so that it can easily be adapted to any of the future missions. One of the thermal architectures being explored for the DSST FD microspacecraft is the integrated thermal energy management of the complete spacecraft using a fluid loop. The robustness and the simplicity of the loop and the flexibility with which it can be integrated in the spacecraft have made it attractive for applications to DSST FD. Some of the thermal technologies to be developed as a part of this architecture are passive and active cooling loops, electrically variable emittance surfaces, miniature thermal switches, and specific high density electronic cooling technologies. In the mechanical area, multifunction architecture for the structural elements will be developed. The multifunction aspect is expected to substantially reduce the mass and volume of the spacecraft. Some of the technologies that will be developed are composite material panels incorporating electronics, cabling, and thermal elements in them. The paper describes the current state of the technologies and progress to be made in the thermal and mechanical technologies and approaches for the DSST Future Deliveries microspacecraft.

Birur, Gajanana C.↗
NASA NTRS2012

NASA Human Spaceflight Architecture Team Cis-Lunar Analysis

The Cis-Lunar Destination Team of NASA's Human Spaceflight Architecture Teait1 (HAT) has been perfom1ing analyses of a number of cis-lunar locations to infom1 architecture development, transportation and destination elements definition, and operations. The cis-lunar domain is defined as that area of deep space under the gravitation influence of the earth-moon system, including a set of orbital locations (low earth orbit (LEO]. geosynchronous earth orbit [GEO]. highly elliptical orbits [HEO]); earth-moon libration or "Lagrange·· points (EMLl through EMLS, and in particular, EMLI and EML2), and low lunar orbit (LLO). We developed a set of cis-lunar mission concepts defined by mission duration, pre-deployment, type of mission, and location, to develop mission concepts and the associated activities, capabilities, and architecture implications. To date, we have produced two destination operations J concepts based on present human space exploration architectural considerations. We have recently begun defining mission activities that could be conducted within an EM LI or EM L2 facility.

Lupisella, M.↗
NASA NTRS1988

A visual programming environment for the Navier-Stokes computer

The Navier-Stokes computer is a high-performance, reconfigurable, pipelined machine designed to solve large computational fluid dynamics problems. Due to the complexity of the architecture, development of effective, high-level language compilers for the system appears to be a very difficult task. Consequently, a visual programming methodology has been developed which allows users to program the system at an architectural level by constructing diagrams of the pipeline configuration. These schematic program representations can then be checked for validity and automatically translated into machine code. The visual environment is illustrated by using a prototype graphical editor to program an example problem.

Tomboulian, Sherryl↗
NASA NTRS2010

A Dual Launch Robotic and Human Lunar Mission Architecture

This paper describes a comprehensive lunar exploration architecture developed by Marshall Space Flight Center's Advanced Concepts Office that features a science-based surface exploration strategy and a transportation architecture that uses two launches of a heavy lift launch vehicle to deliver human and robotic mission systems to the moon. The principal advantage of the dual launch lunar mission strategy is the reduced cost and risk resulting from the development of just one launch vehicle system. The dual launch lunar mission architecture may also enhance opportunities for commercial and international partnerships by using expendable launch vehicle services for robotic missions or development of surface exploration elements. Furthermore, this architecture is particularly suited to the integration of robotic and human exploration to maximize science return. For surface operations, an innovative dual-mode rover is presented that is capable of performing robotic science exploration as well as transporting human crew conducting surface exploration. The dual-mode rover can be deployed to the lunar surface to perform precursor science activities, collect samples, scout potential crew landing sites, and meet the crew at a designated landing site. With this approach, the crew is able to evaluate the robotically collected samples to select the best samples for return to Earth to maximize the scientific value. The rovers can continue robotic exploration after the crew leaves the lunar surface. The transportation system for the dual launch mission architecture uses a lunar-orbit-rendezvous strategy. Two heavy lift launch vehicles depart from Earth within a six hour period to transport the lunar lander and crew elements separately to lunar orbit. In lunar orbit, the crew transfer vehicle docks with the lander and the crew boards the lander for descent to the surface. After the surface mission, the crew returns to the orbiting transfer vehicle for the return to the Earth. This paper describes a complete transportation architecture including the analysis of transportation element options and sensitivities including: transportation element mass to surface landed mass; lander propellant options; and mission crew size. Based on this analysis, initial design concepts for the launch vehicle, crew module and lunar lander are presented. The paper also describes how the dual launch lunar mission architecture would fit into a more general overarching human space exploration philosophy that would allow expanded application of mission transportation elements for missions beyond the Earth-moon realm.

Jones, David L.↗
NASA NTRS2017

Model-Driven Development of Safety Architectures

We describe the use of model-driven development for safety assurance of a pioneering NASA flight operation involving a fleet of small unmanned aircraft systems (sUAS) flying beyond visual line of sight. The central idea is to develop a safety architecture that provides the basis for risk assessment and visualization within a safety case, the formal justification of acceptable safety required by the aviation regulatory authority. A safety architecture is composed from a collection of bow tie diagrams (BTDs), a practical approach to manage safety risk by linking the identified hazards to the appropriate mitigation measures. The safety justification for a given unmanned aircraft system (UAS) operation can have many related BTDs. In practice, however, each BTD is independently developed, which poses challenges with respect to incremental development, maintaining consistency across different safety artifacts when changes occur, and in extracting and presenting stakeholder specific information relevant for decision making. We show how a safety architecture reconciles the various BTDs of a system, and, collectively, provide an overarching picture of system safety, by considering them as views of a unified model. We also show how it enables model-driven development of BTDs, replete with validations, transformations, and a range of views. Our approach, which we have implemented in our toolset, AdvoCATE, is illustrated with a running example drawn from a real UAS safety case. The models and some of the innovations described here were instrumental in successfully obtaining regulatory flight approval.

Safety case↗
NASA NTRS2007

Enterprise Information Architecture for Mission Development

This slide presentation reviews the concept of an information architecture to assist in mission development. The integrate information architecture will create a unified view of the information using metadata and the values (i.e., taxonomy).

enterprise information architecture↗
NASA NTRS2008

Control Architecture for Robotic Agent Command and Sensing

Control Architecture for Robotic Agent Command and Sensing (CARACaS) is a recent product of a continuing effort to develop architectures for controlling either a single autonomous robotic vehicle or multiple cooperating but otherwise autonomous robotic vehicles. CARACaS is potentially applicable to diverse robotic systems that could include aircraft, spacecraft, ground vehicles, surface water vessels, and/or underwater vessels. CARACaS incudes an integral combination of three coupled agents: a dynamic planning engine, a behavior engine, and a perception engine. The perception and dynamic planning en - gines are also coupled with a memory in the form of a world model. CARACaS is intended to satisfy the need for two major capabilities essential for proper functioning of an autonomous robotic system: a capability for deterministic reaction to unanticipated occurrences and a capability for re-planning in the face of changing goals, conditions, or resources. The behavior engine incorporates the multi-agent control architecture, called CAMPOUT, described in An Architecture for Controlling Multiple Robots (NPO-30345), NASA Tech Briefs, Vol. 28, No. 11 (November 2004), page 65. CAMPOUT is used to develop behavior-composition and -coordination mechanisms. Real-time process algebra operators are used to compose a behavior network for any given mission scenario. These operators afford a capability for producing a formally correct kernel of behaviors that guarantee predictable performance. By use of a method based on multi-objective decision theory (MODT), recommendations from multiple behaviors are combined to form a set of control actions that represents their consensus. In this approach, all behaviors contribute simultaneously to the control of the robotic system in a cooperative rather than a competitive manner. This approach guarantees a solution that is good enough with respect to resolution of complex, possibly conflicting goals within the constraints of the mission to be accomplished by the vehicle(s).

Huntsberger, Terrance↗
NASA NTRS1994

Standardizing the information architecture for spacecraft operations

This paper presents an information architecture developed for the Space Station Freedom as a model from which to derive an information architecture standard for advanced spacecraft. The information architecture provides a way of making information available across a program, and among programs, assuming that the information will be in a variety of local formats, structures and representations. It provides a format that can be expanded to define all of the physical and logical elements that make up a program, add definitions as required, and import definitions from prior programs to a new program. It allows a spacecraft and its control center to work in different representations and formats, with the potential for supporting existing spacecraft from new control centers. It supports a common view of data and control of all spacecraft, regardless of their own internal view of their data and control characteristics, and of their communications standards, protocols and formats. This information architecture is central to standardizing spacecraft operations, in that it provides a basis for information transfer and translation, such that diverse spacecraft can be monitored and controlled in a common way.

Easton, C. R.↗