Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “service oriented architecture”

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.

83 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Photochemical Phenomenology Model for the New Millenium

This project tackles the problem of conversion of validated a priori physics-based modeling capabilities, specifically those relevant to the analysis and interpretation of planetary atmosphere observations, to application-oriented software for use in science and science-support activities. The software package under development, named the Photochemical Phenomenology Modeling Tool (PPMT), has particular focus on the atmospheric remote sensing data to be acquired by the CIRS instrument during the CASSINI Jupiter flyby and orbital tour of the Saturnian system. Overall, the project has followed the development outline given in the original proposal, and the Year 1 design and architecture goals have been met. Specific accomplishments and the difficulties encountered are summarized in this report. Most of the effort has gone into complete definition of the PPMT interfaces within the context of today's IT arena: adoption and adherence to the CORBA Component Model (CCM) has yielded a solid architecture basis, and CORBA-related issues (services, specification options, development plans, etc.) have been largely resolved. Implementation goals have been redirected somewhat so as to be more relevant to the upcoming CASSINI flyby of Jupiter, with focus now being more on data analysis and remote sensing retrieval applications.

Bishop, James↗
NASA NTRS1996

Long-term archiving and data access: modelling and standardization

This paper reports on the multiple difficulties inherent in the long-term archiving of digital data, and in particular on the different possible causes of definitive data loss. It defines the basic principles which must be respected when creating long-term archives. Such principles concern both the archival systems and the data. The archival systems should have two primary qualities: independence of architecture with respect to technological evolution, and generic-ness, i.e., the capability of ensuring identical service for heterogeneous data. These characteristics are implicit in the Reference Model for Archival Services, currently being designed within an ISO-CCSDS framework. A system prototype has been developed at the French Space Agency (CNES) in conformance with these principles, and its main characteristics will be discussed in this paper. Moreover, the data archived should be capable of abstract representation regardless of the technology used, and should, to the extent that it is possible, be organized, structured and described with the help of existing standards. The immediate advantage of standardization is illustrated by several concrete examples. Both the positive facets and the limitations of this approach are analyzed. The advantages of developing an object-oriented data model within this contxt are then examined.

Hoc, Claude↗
NASA NTRS1991

A parallel-pipelined architecture for a multi carrier demodulator

Analog devices have been used for processing the information on board the satellites. Presently, digital devices are being used because they are economical and flexible as compared to their analog counterparts. Several schemes of digital transmission can be used depending on the data rate requirement of the user. An economical scheme of transmission for small earth stations uses single channel per carrier/frequency division multiple access (SCPC/FDMA) on the uplink and time division multiplexing (TDM) on the downlink. This is a typical communication service offered to low data rate users in commercial mass market. These channels usually pertain to either voice or data transmission. An efficient digital demodulator architecture is provided for a large number of law data rate users. A demodulator primarily consists of carrier, clock, and data recovery modules. This design uses principles of parallel processing, pipelining, and time sharing schemes to process large numbers of voice or data channels. It maintains the optimum throughput which is derived from the designed architecture and from the use of high speed components. The design is optimized for reduced power and area requirements. This is essential for satellite applications. The design is also flexible in processing a group of a varying number of channels. The algorithms that are used are verified by the use of a computer aided software engineering (CASE) tool called the Block Oriented System Simulator. The data flow, control circuitry, and interface of the hardware design is simulated in C language. Also, a multiprocessor approach is provided to map, model, and simulate the demodulation algorithms mainly from a speed view point. A hypercude based architecture implementation is provided for such a scheme of operation. The hypercube structure and the demodulation models on hypercubes are simulated in Ada.

Kwatra, S. C.↗
NASA NTRS2001

High Speed PC Based Data Acquisition and Instrumentation for Measurement of Simulated Low Earth Orbit Thermally Induced Disturbances

The Hubble Space Telescope (HST) Disturbance Verification Test (DVT) was conducted to characterize responses of the Observatory's new set of rigid solar array's (SA3) to thermally induced 'creak' or stiction releases. The data acquired in the DVT were used in verification of the HST Pointing Control System on-orbit performance, post-Servicing Mission 3B (SM3B). The test simulated the on-orbit environment on a deployed SA3 flight wing. Instrumentation for this test required pretest simulations in order to select the correct sensitivities. Vacuum compatible, highly accurate accelerometers and force gages were used for this test. The complexity of the test, as well as a short planning schedule, required a data acquisition system that was easy to configure, highly flexible, and extremely robust. A PC Windows oriented data acquisition system meets these requirements, allowing the test engineers to minimize the time required to plan and perform complex environmental test. The SA3 DVT provided a direct practical and complex demonstration of the versatility that PC based data acquisition systems provide. Two PC based data acquisition systems were assembled to acquire, process, distribute, and provide real time processing for several types of transducers used in the SA3 DVT. A high sample rate digital tape recorder was used to archive the sensor signals. The two systems provided multi-channel hardware and software architecture and were selected based on the test requirements. How these systems acquire and processes multiple data rates from different transducer types is discussed, along with the system hardware and software architecture.

Sills, Joel W., Jr.↗
NASA NTRSDate not supplied

Defining a Global Lunar Position, Navigation, and Timing System

As NASA seeks to fulfill its mission of extending humanity’s reach through exploration as delineated in the Moon to Mars Strategy and Objectives Development and the Moon to Mars Architecture Definition Document, accurate and timely position, navigation, and timing (PNT) services are critical in the architecture, identifying a need to expand a PNT capability to the full lunar proximity service volume. This is echoed in the White House Office of Science, Technology, and Policy Cislunar Science and Technology Strategy, which pinpoints the fundamental need for PNT infrastructure to enable and sustain a vibrant cislunar ecosystem. While the Human Lunar Return segment seeks commercial services to provide a PNT service over a South Pole service volume for a limited period per Earth day, meeting the Sustained Lunar Evolution segment requires a Lunar Navigation System (LNS) focused on delivery of precise and resilient PNT services across the lunar globe and near-Moon space. This presentation describes the pre-Phase A system concept for an orbital constellation, the requisite lunar surface-based in-situ monitor and control segment, and an Earth control segment to provide lunar PNT services out to 200km altitude above the surface. The LNS leverages the foundational efforts on lunar reference system components such as the Lunar Geodetic System, Lunar Time System, and lunar ephemeris and orientation critical to safe, accurate, and seamless navigation.

navigation↗
NASA NTRS1995

An object-oriented, technology-adaptive information model

The primary objective was to develop a computer information system for effectively presenting NASA's technologies to American industries, for appropriate commercialization. To this end a comprehensive information management model, applicable to a wide variety of situations, and immune to computer software/hardware technological gyrations, was developed. The model consists of four main elements: a DATA_STORE, a data PRODUCER/UPDATER_CLIENT and a data PRESENTATION_CLIENT, anchored to a central object-oriented SERVER engine. This server engine facilitates exchanges among the other model elements and safeguards the integrity of the DATA_STORE element. It is designed to support new technologies, as they become available, such as Object Linking and Embedding (OLE), on-demand audio-video data streaming with compression (such as is required for video conferencing), Worldwide Web (WWW) and other information services and browsing, fax-back data requests, presentation of information on CD-ROM, and regular in-house database management, regardless of the data model in place. The four components of this information model interact through a system of intelligent message agents which are customized to specific information exchange needs. This model is at the leading edge of modern information management models. It is independent of technological changes and can be implemented in a variety of ways to meet the specific needs of any communications situation. This summer a partial implementation of the model has been achieved. The structure of the DATA_STORE has been fully specified and successfully tested using Microsoft's FoxPro 2.6 database management system. Data PRODUCER/UPDATER and PRESENTATION architectures have been developed and also successfully implemented in FoxPro; and work has started on a full implementation of the SERVER engine. The model has also been successfully applied to a CD-ROM presentation of NASA's technologies in support of Langley Research Center's TAG efforts.

Anyiwo, Joshua C.↗
NASA NTRS1990

Spaceport aurora: An orbiting transportation node

With recent announcements of the development of permanently staffed facilities on the Moon and Mars, the national space plan is in need of an infrastructure system for transportation and maintenance. A project team at the University of Houston College of Architecture and the Sasakawa International Center for Space Architecture, recently examined components for a low Earth orbit (LEO) transportation node that supports a lunar build-up scenario. Areas of investigation included identifying transportation node functions, identifying existing space systems and subsystems, analyzing variable orbits, determining logistics strategies for maintenance, and investigating assured crew return systems. The information resulted in a requirements definition document, from which the team then addressed conceptual designs for a LEO transportation node. The primary design drivers included: orbital stability, maximizing human performance and safety, vehicle maintainability, and modularity within existing space infrastructure. For orbital stability, the power tower configuration provides a gravity gradient stabilized facility and serves as the backbone for the various facility components. To maximize human performance, human comfort is stressed through zoning of living and working activities, maintaining a consistent local vertical orientation, providing crew interaction and viewing areas and providing crew return vehicles. Vehicle maintainability is accomplished through dual hangars, dual work cupolas, work modules, telerobotics and a fuel depot. Modularity is incorporated using Space Station Freedom module diameter, Space Station Freedom standard racks, and interchangeable interior partitions. It is intended that the final design be flexible and adaptable to provide a facility prototype that can service multiple mission profiles using modular space systems.

Source record↗
NASA NTRS1994

Accommodating Heterogeneity in a Debugger for Distributed Computations

In an ongoing project at NASA Ames Research Center, we are building debugger for distributed computations running on a heterogeneous set of machines. Historically, such debuggers have been built as front-ends to existing source-level debuggers on the target platforms. In effect, these back-end debuggers are providing a collection of debugger services to a client. The major drawback is that because of inconsistencies among the back-end debuggers, the front-end must use a different protocol when talking to each back-end debugger. This can make the front-end quite complex. We have avoided this complexity problem by defining the client-server debugger protocol. While it does require vendors to adapt their existing debugger code to meet the protocol, vendors are generally interested in doing so because the approach has several advantages. In addition to solving the heterogenous platform debugging problem, it will be pos~sible to write interesting debugger user interfaces that can be easily ported across a variety of machines. This will likely encourage investment in application-domain specific debuggers. In fact, the user interface of our debugger will be geared to scientists developing computational fluid dynamics codes. This paper describes some of the problems encountered in developing a portable debugger for heterogenous, distributed computing and how the architecture of our debugger avoids them. It then provides a detailed description of the debugger client-server protocol. Some of the more interesting attributes of the protocol are: (1) It is object-oriented; (2) It uses callback functions to capture the asynchronous nature of debugging in a procedural fashion; (3) It contains abstractions, such as in-line instrumentation, for the debugging of computationally intensive programs; (4) For remote debugging, it has operations that enable the implementor to optimize message passing traffic between client and server. The soundness of the protocol is being tested through the implementation of a prototype client and server pair.

Hood, Robert↗
NASA NTRS2009

Extreme Programming: Maestro Style

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

Norris, Jeffrey↗
NASA NTRS2024

Workshop on the Role of Design Assurance in System-Wide Safety’s Safety Demonstrator Series

This report summarizes a three-hour hybrid in-person/online workshop on June 7, 2024 on the topic of design assurance and the Safety Demonstrator Series (SDS), which was held at NASA Ames Research Center. The SDS provides an operational demonstration of, and recommendations for, requirements and standards necessary to monitor, assess, and mitigate risks to assure safety in disaster-oriented operations. Over sixty NASA personnel participated in the workshop. Four main topics were discussed: (1) assurance needs for the Safety Demonstrator Series, (2) assurance and the In-Time Aviation Safety Management System (IASMS), (3) in-time assurance: existing efforts and future opportunities, and (4) demonstrating assurance tools in the Safety Demonstrators. Key takeaways are as follows: 1. Design assurance tools can be used to assure an In-Time Aviation Safety Management System, the systems that comprise it, and other systems or missions. Assurance must consider both systems and components and include the interactions between elements in both a systems/aircraft context and a systems-of-systems/airspace context. 2. Design-time assurance activities can support the identification of monitors needed for operational assurance activities (i.e., the “monitor” function in the monitor-assess-mitigate paradigm at the heart of the IASMS concept). 3. A major opportunity for design-time assurance tools to contribute to the IASMS concept is to support rapid re-validation of systems. This will be particularly important for (1) supporting novel operations in the IASMS, where operational data may disprove design-time assumptions (motivating re-analysis of system safety) and (2) adapting technologies (e.g., AI/ML for autonomous operations) to new operational domains, where there may be new or different safety considerations not included in the initial scope of operations. 4. There are several design assurance tools under development in the System-Wide Safety project that can support assurance of Services, Functions, and Capabilities (SFCs) in the Safety Demonstrators. Transitioning these tools from one-off research projects into a functioning part of IASMS assurance will require closer integration between these tools. 5. It is not clear whether the role of design assurance tools is primarily as a part of IASMS architecture or as an external check on IASMS. The workshop consisted of four discussion topics initiated via four lightning talks by System-Wide Safety researchers. Discussions utilized Mural to engage both in-person and online participants in the hybrid format. Polls and surveys were also utilized to gather participant input. The workshop closed with a reflection activity for participants, as well as new ideas for collaboration and coordination of ongoing System-Wide Safety research.

design assurance↗
NASA NTRS2016

Flat H Redundant Frangible Joint Development

Orion and Commercial Crew Program (CCP) Partners have chosen to use frangible joints for certain separation events. The joints currently available are zero failure tolerant and will be used in mission safety applications. The goal is to further develop a NASA designed redundant frangible joint that will lower flight risk and increase reliability. FY16 testing revealed a successful design in subscale straight test specimens that gained efficiency and supports Orion load requirements. Approach / Innovation A design constraint is that the redundant joint must fit within the current Orion architecture, without the need for additional vehicle modification. This limitation required a design that changed the orientation of the expanding tube assemblies (XTAs), by rotating them 90deg from the standard joint configuration. The change is not trivial and affects the fracture mechanism and structural load paths. To address these changes, the design incorporates cantilevered arms on the break plate. The shock transmission and expansion of the XTA applies force to these arms and creates a prying motion to push the plate walls outward to the point of structural failure at the notched section. The 2014 test design revealed that parts could slip during functioning wasting valuable energy needed to separate the structure with only a single XTA functioning. Dual XTA functioning fully separated the assembly showing a discrepancy can be backed up with redundancy. Work on other fully redundant systems outside NASA is limited to a few patents that have not been subjected to functionality testing Design changes to prevent unwanted slippage (with ICA funding in 2015) showed success with a single XTA. The main goal for FY 2016 was to send the new Flat H RFJ to WSTF where single XTA test failures occurred back in 2014. The plan was to gain efficiency in this design by separating the Flat H RFJ with thicker ligaments with dimensions baselined in 2014. Other modifications included geometry changes to better disperse loads paths and to minimize air gaps. The design additionally added more structural strength to enhance the structural limits in static loads testing. The design also implemented a smoother load line through the assembly. Results / Knowledge Gained The new Flat H RFJ successfully fractured at WSTF with thicker ligaments and lower cord size. Where failure to separate occurred earlier, there is now excessive energy available for structural separation. The new challenge to provide some structural support to prevent secondary fracturing of the break plate remains to be completed. This future work is being funded by the JSC Engineering Directorate in 2017 to elevate the TRL on curved Flat H RFJs that configure with the Orion Service Panel Separation. Additional funding from JSC Engineering will provide new design testing to avoid secondary fracturing.

Brown, Chris↗