Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “system architectures”

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 37 records · Page 2

Model-Based Systems Engineering for Capturing Mission Architecture System Processes with an Application Case Study - Orion Flight Test 1

Model-based Systems Engineering (MBSE) is an emerging methodology that can be leveraged to enhance many system development processes. MBSE allows for the centralization of an architecture description that would otherwise be stored in various locations and formats, thus simplifying communication among the project stakeholders, inducing commonality in representation, and expediting report generation. This paper outlines the MBSE approach taken to capture the processes of two different, but related, architectures by employing the Systems Modeling Language (SysML) as a standard for architecture description and the modeling tool MagicDraw. The overarching goal of this study was to demonstrate the effectiveness of MBSE as a means of capturing and designing a mission systems architecture. The first portion of the project focused on capturing the necessary system engineering activities that occur when designing, developing, and deploying a mission systems architecture for a space mission. The second part applies activities from the first to an application problem - the system engineering of the Orion Flight Test 1 (OFT-1) End-to-End Information System (EEIS). By modeling the activities required to create a space mission architecture and then implementing those activities in an application problem, the utility of MBSE as an approach to systems engineering can be demonstrated.

Orion Flight Test 1 (OFT-1)↗

Development of life prediction capabilities for liquid propellant rocket engines. Post-fire diagnostic system for the SSME system architecture study

This system architecture task (1) analyzed the current process used to make an assessment of engine and component health after each test or flight firing of an SSME, (2) developed an approach and a specific set of objectives and requirements for automated diagnostics during post fire health assessment, and (3) listed and described the software applications required to implement this system. The diagnostic system described is a distributed system with a database management system to store diagnostic information and test data, a CAE package for visual data analysis and preparation of plots of hot-fire data, a set of procedural applications for routine anomaly detection, and an expert system for the advanced anomaly detection and evaluation.

Gage, Mark↗

Precision Segmented Reflector figure control system architecture

A control system architecture for an actively controlled segmented reflector is described along with a design realization for achieving precision alignment of reflector panels. Performance requirements are derived in part from the Large Deployable Reflector, which is a representative mission, and error allocations are made which consider mirror panel surface errors, position measurement and figure estimation, and position control of both quasi-static and dynamic disturbances. The design uses multiple wavelength interferometric edge sensors and voice coil actuators in conjunction with a hybrid control strategy to correct panel position errors. A unit cell shown to be central to the concept is analyzed. The cell integrates the sensing, actuation, and mechanical functions of a control module together with a reflector panel to form a unitized assembly.

Mettler, E.↗

Space System Architecture Code

Space System Architecture Code (SSAC) program performs sensitivity studies on operating parameters of space missions. SSAC examines effects of variations in sizes of crews of piloted missions, chemical vs. nuclear electric propulsion, and specific impulse. Written in FORTRAN 77.

Jan, Darrell L.↗

System architecture and method of processing data therein

A system architecture encoded on a non-transitory computer readable medium, the system architecture includes a first protocol. The first protocol is configured to receive a plurality of outputs from an ICS used in controlling an industrial system. The first protocol is configured to receive a plurality of inputs from a physical module. The physical module includes at least one of a component, a sensor, or the ICS. Additionally, the system architecture includes a second protocol, wherein the second protocol is configured to validate the plurality of inputs from the first protocol. Moreover, the system architectures includes a third protocol, wherein the third protocol is configured to validate the plurality of outputs from the first protocol. Further, the system architecture includes a fourth protocol, wherein the fourth protocol is configured to manage the ICS based on the second protocol and the third protocol.

Abdel-Khalik, Hany S.↗

System architecture and method of processing data therein

A system architecture encoded on a non-transitory computer readable medium, the system architecture includes a first protocol. The first protocol is configured to receive a plurality of outputs from an ICS used in controlling an industrial system. The first protocol is configured to receive a plurality of inputs from a physical module. The physical module includes at least one of a component, a sensor, or the ICS. Additionally, the system architecture includes a second protocol, wherein the second protocol is configured to validate the plurality of inputs from the first protocol. Moreover, the system architectures includes a third protocol, wherein the third protocol is configured to validate the plurality of outputs from the first protocol. Further, the system architecture includes a fourth protocol, wherein the fourth protocol is configured to manage the ICS based on the second protocol and the third protocol.

Abdel-Khalik, Hany S.↗

Component-Level Electronic-Assembly Repair (CLEAR) System Architecture

This document captures the system architecture for a Component-Level Electronic-Assembly Repair (CLEAR) capability needed for electronics maintenance and repair of the Constellation Program (CxP). CLEAR is intended to improve flight system supportability and reduce the mass of spares required to maintain the electronics of human rated spacecraft on long duration missions. By necessity it allows the crew to make repairs that would otherwise be performed by Earth based repair depots. Because of practical knowledge and skill limitations of small spaceflight crews they must be augmented by Earth based support crews and automated repair equipment. This system architecture covers the complete system from ground-user to flight hardware and flight crew and defines an Earth segment and a Space segment. The Earth Segment involves database management, operational planning, and remote equipment programming and validation processes. The Space Segment involves the automated diagnostic, test and repair equipment required for a complete repair process. This document defines three major subsystems including, tele-operations that links the flight hardware to ground support, highly reconfigurable diagnostics and test instruments, and a CLEAR Repair Apparatus that automates the physical repair process.

Oeftering, Richard C.↗

A Data System Architecture for Measurement Based Systems: Precipitation Processing System

NASA s Earth Science Enterprise (ESE) is changing focus from single satellite missions to measurement oriented programs. An example of this paradigm shift is the Global Precipitation Measurement (GPM) project. GPM is conceptualized as a rolling-wave of measurement possibilities all focused on the key precipitation parameter. In response to this shift to measurement programs and also integral to the ESE s new strategy for processing and management its data, a measurement based approach is also critical for data processing system that support measurement programs like GPM. This paper provides an overview of the paradigm shift from mission to measurement. It also presents a summary of the ESE s new strategy for its data systems. Building on this background the paper details the architectural, design and implementation aspects of the Precipitation Processing System (PPS). The PPS is an evolution of a single point system developed for the Tropical Rainfall Measurement Mission to a generic precipitation data system. The paper provides the context within which PPS will support the GPM program.

Stocker, Erich Franz↗

Battery-ultracapacitor hybrid energy storage system architecture for mild-hybrid power systems

A mild-hybrid energy storage system architecture is provided, comprising: a battery; an ultracapacitor connected in parallel with the battery; a passive battery pre-charge circuit connected between a terminal of the battery and a DC bus; a battery main contactor connected in parallel with the battery pre-charge circuit between the terminal of the battery and the DC bus; a passive ultracapacitor pre-charge circuit connected between a terminal of the ultracapacitor and the DC bus; an ultracapacitor main contactor connected in parallel with the ultracapacitor pre-charge circuit between the terminal of the ultracapacitor and the DC bus; and a control module configured to independently control operation of the battery pre-charge circuit, the battery main contactor, the ultracapacitor pre-charge circuit and the ultracapacitor main contactor.

Varigonda, Subbarao↗

An advanced mixed user domestic satellite system architecture

A domestic satellite system architecture that can efficiently and economically accommodate a wide variety of disparate user classes is described and a baseline system configuration identified. With such a technique, both the efficiency of TDMA operation and the operational terminal flexibility of FDMA can be simultaneously achieved.

Raymond, H. G.↗

System architecture for the Canadian interim mobile satellite system

The system architecture for the Canadian Interim Mobile Satellite Service (IMSS) which is planned for commencement of commercial service in late 1989 is reviewed. The results of an associated field trial program which was carried out to determine the limits of coverage and the preliminary performance characteristics of the system are discussed.

Shariatmadar, M.↗

A system architecture for an advanced Canadian wideband mobile satellite system

In this paper, the system architecture for an advanced Canadian ka-band geostationary mobile satellite system is described, utilizing hopping spot beams to support a 256 kbps wideband service for both N-ISDN and packet-switched interconnectivity to small briefcase-size portable and mobile terminals. An assessment is given of the technical feasibility of the satellite payload and terminal design in the post year 2000 timeframe. The satellite payload includes regeneration and on-board switching to permit single hop interconnectivity between mobile terminals. The mobile terminal requires antenna tracking and platform stabilization to ensure acquisition of the satellite signal. The potential user applications targeted for this wideband service includes: home-office, multimedia, desk-top (PC) videoconferencing, digital audio broadcasting, single and multi-user personal communications.

Takats, P.↗

A Ground Systems Architecture Transition for A Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the ISS payloads program, and the resulting functional breakdown of the products that support that architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

A Ground Systems Architecture Transition for a Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the International Space Station (ISS) payloads program, and the resulting functional breakdown of the products that support this architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

A Generic Expert Scheduling System Architecture and Toolkit: GUESS (Generically Used Expert Scheduling System)

Scheduling has become an increasingly important element in today's society and workplace. Within the NASA environment, scheduling is one of the most frequently performed and challenging functions. Towards meeting NASA's scheduling needs, a research version of a generic expert scheduling system architecture and toolkit has been developed. This final report describes the development and testing of GUESS (Generically Used Expert Scheduling System).

Liebowitz, Jay↗

Designing a Distributed Systems Architecture Testbed for Real-Time Power Grid Systems

Power engineers who are striving to improve real-time attribute of power grid applications are ill equipped with software engineering methods and tools that allow them to rigorously evaluate their designs, taken into account data communication, geographic locations, and high performance computing capacity. This paper presents a technical approach to designing a testbed for embedding real-time monitoring and computation functionalities into the power grid system. The approach focuses on integrating the parallel computational models with the data management infrastructure for near-real time power grid state estimation. We study and summarize various forces and requirements that drive the design decisions in the distributed systems architecture. Given the continental scale of the power grid, it is important for the testbed to be extensible and scalable within a complex topology of physical entities, controlled by an overlaid network of power utilities and regulatory balancing authorities. This paper outlines the technical steps, and software toolkits to develop this testbed.

99 GENERAL AND MISCELLANEOUS↗

System Architecture Directions for Post-SoC/32-bit Networked Sensors

The emergence of low-power 32-bit Systems-on-Chip (SoCs), which integrate a 32-bit MCU, radio, and flash, presents an opportunity to re-examine design points and trade-offs at all levels of the system architecture of networked sensors. To this end, we develop a post-SoC/32-bit design point called Hamilton, showing that using integrated components enables a ~$7 core and shifts hardware modularity to design time. We study the interaction between hardware and embedded operating systems, identifying that (1) post-SoC motes provide lower idle current (5.9 μA) than traditional 16-bit motes, (2) 32-bit MCUs are a major energy consumer (e.g., tick increases idle current >50 times), comparable to radios, and (3) thread-based concurrency is viable, requiring only 8.3 μs of context switch time. We design a system architecture, based on a tickless multithreading operating system, with cooperative/adaptive clocking, advanced sensor abstraction, and preemptive packet processing. Its efficient MCU control improves concurrency with ~30% less energy consumption. Together, these developments set the system architecture for networked sensors in a new direction.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

ECLSS Does Not Exist in a Vacuum: Integrated Analysis is Necessary to Inform System Architecture Decisions

Environmental Control and Life Support System (ECLSS) architecture selection has profound implications for mission cost and mass extending far beyond the ECLSS itself. Similarly, other mission architecture decisions – particularly involving transportation systems – can influence optimal ECLSS architectures. Loop closure influences requirements for water, oxygen, and other consumables. System maintainability and reliability influences spares mass and risk. System, consumables, and spares mass interact with transportation system architectures and propellant demands and propulsion element sizing. All these interactions with other systems must be considered when evaluating ECLSS options. Analyses that focus only on maximizing ECLSS loop closure – or minimizing ECLSS mass, or minimizing ECLSS life cycle cost – may lead to sub-optimal or even counterproductive system architecture and investment decisions at the mission level. For example, an ECLSS architecture that minimizes ECLSS lifecycle cost but results in excessively high logistics mass could lead to significantly increased transportation system costs or make interplanetary transportation infeasible. Increased loop closure could result in higher development costs and higher mass if system/spares mass increases outweigh consumables reduction. In addition, systems mass and consumables mass are not directly comparable and have different impacts on propellant requirements, as consumables mass changes over the course of the mission. This paper presents an integrated analysis examining the overall impact of different ECLSS and transportation architectures on mass for a crewed Mars mission, including the habitat and transportation systems as well as consumables, spares, and propellant. Key observations are discussed, along with opportunities for further sensitivity analysis and model development. Overall, ECLSS development activities must consider their impacts at the mission level, as part of an integrated system, rather than in isolation.

Systems Analysis↗