SEARCH · Search NASA
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.
Computerized interactive harness engineering program inexpensive, interactive system for learning and using engineering approach to interconnection systems. Basically data-base system that stores information as files of individual connectors and handles wiring information in circuit groups stored as records.
This charter establishes the International Space Station Program (ISSP) Mobile Servicing System (MSS) Systems Engineering Working Group (SEWG). The MSS SEWG is established to provide a mechanism for Systems Engineering for the end-to-end MSS function. The MSS end-to-end function includes the Space Station Remote Manipulator System (SSRMS), the Mobile Remote Servicer (MRS) Base System (MBS), Robotic Work Station (RWS), Special Purpose Dexterous Manipulator (SPDM), Video Signal Converters (VSC), and Operations Control Software (OCS), the Mobile Transporter (MT), and by interfaces between and among these elements, and United States On-Orbit Segment (USOS) distributed systems, and other International Space Station Elements and Payloads, (including the Power Data Grapple Fixtures (PDGFs), MSS Capture Attach System (MCAS) and the Mobile Transporter Capture Latch (MTCL)). This end-to-end function will be supported by the ISS and MSS ground segment facilities. This charter defines the scope and limits of the program authority and document control that is delegated to the SEWG and it also identifies the panel core membership and specific operating policies.
Increasing complexity in modern systems as well as cost and schedule constraints require a new paradigm of system engineering to fulfill stakeholder needs. Challenges facing efficient trade studies include poor tool interoperability, lack of simulation coordination (design parameters) and requirements flowdown. A recent trend toward Model Based System Engineering (MBSE) includes flexible architecture definition, program documentation, requirements traceability and system engineering reuse. As a new domain MBSE still lacks governing standards and commonly accepted frameworks. This paper proposes a framework for efficient architecture definition using MBSE in conjunction with Domain Specific simulation to evaluate trade studies. A general framework is provided followed with a specific example including a method for designing a trade study, defining candidate architectures, planning simulations to fulfill requirements and finally a weighted decision analysis to optimize system objectives.
Seminar on systems engineering in space exploration - systems design, systems analysis, space flight operations, and program engineering and project problems
During the Formulation phases of the NASA Project Life Cycle, communication systems engineers are responsible for designing space communication links and analyzing their performance to ensure that the proposed communication architecture is capable of satisfying high-level mission requirements. Senior engineers with extensive experience in communications systems perform these activities. However, the increasing complexity of space systems coupled with the current shortage of communications systems engineers has led to an urgent need for expedited training of new systems engineers. A pilot program, in which college-bound high school and undergraduate students studying various engineering disciplines are immersed in NASA s systems engineering practices, was conceived out of this need. This rapid summerlong training approach is feasible because of the availability of advanced software and technology tools and the students inherent ability to operate such tools. During this pilot internship program, a team of college-level and recently-hired engineers configured and utilized various software applications in the design and analysis of communication links for a plausible lunar sortie mission. The approach taken was to first design the direct-to-Earth communication links for the lunar mission elements, then to design the links between lunar surface and lunar orbital elements. Based on the data obtained from these software applications, an integrated communication system design was realized and the students gained valuable systems engineering knowledge. This paper describes this approach to rapidly training college-bound high school and undergraduate engineering students from various disciplines in NASA s systems engineering practices and tools. A summary of the potential use of NASA s emerging systems engineering internship program in broader applications is also described.
Program plans, schedules, and costs are determined for a synchronous orbit-based power generation and relay system. Requirements for the satellite solar power station (SSPS) and the power relay satellite (PRS) are explored. Engineering analysis of large solar arrays, flight mechanics and control, transportation, assembly and maintenance, and microwave transmission are included.
A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.
The DYLOFLEX computer program system expands the aeroelastic cycle from that in the FLEXSTAB computer program system to include dynamic loads analyses involving active controls. Two aerodynamic options exist within DYLOFLEX. The analyst can formulate the problem with unsteady aerodynamics calculated using the doublet lattice method or with quasi-steady aerodynamics formulated from either FLEXSTAB or doublet lattice steady state aerodynamics with unsteady effects approximated by indicial lift growth functions. The equations of motion are formulated assuming straight and level flight and small motions. Loads are calculated using the force summation technique. DYLOFLEX consists of nine standalone programs which can be linked with each other by magnetic files used to transmit the required data between programs.
This paper examines the question of cost, from the birth of a program to its conclusion, particularly from the point of view of large multi-center programs, and suggests how to avoid some of the traps and pitfalls. Emphasis is given to cost in the systems engineering process, but there is an inevitable overlap with program management. (The terms systems engineering and program management have never been clearly defined.) In these days of vast Federal budget deficits and increasing overseas competition, it is imperative that we get more for each research and development dollar. This is the only way we will retain our leadership in high technology and, in the long run, our way of life.
Systems engineering could also be called the art of compromise. At its heart, systems engineering seeks to find that solution which maximizes the utility of the system, usually compromising the performance of each individual subsystem. While seemingly straightforward, systems engineering methodology is complicated when the utility to be maximized is unclear and the costs to each individual subsystem are not - or not easily - quantifiable. In this paper, we explore one such systems engineering problem within the Constellation Program as a case study in applied systems engineering. During suited operations, astronauts within Orion will be connected to an umbilical to receive and return breathing gas. The pressure drop associated with this umbilical must be overcome by the Orion vehicle. A smaller umbilical, which is desirable for crew operations, means a higher pressure drop, resulting in additional mass and power for the vehicle. We outline the technical considerations in the development of this integrated system and discuss the method by which we reached the ultimate solution. This paper, while just one example of the kind of problem solving that happens every day, offers insight into what happens when the theories of systems engineering are put into practice.
The updated study plan for the Space Transportation System orbit transfer vehicle (OTV) engine study is presented. The study program consists of engine system, programmatic, cost, and risk analyses of OTV engine concepts. Detailed task descriptions for the advanced expander cycle engine optimization, alternate low thrust capability, and safety, reliability, and cost comparisons are given.
The space station data management system involves networks of computing resources that must work cooperatively and reliably over an indefinite life span. This program requires a long schedule of modular growth and an even longer period of maintenance and operation. The development and operation of space station computing resources will involve a spectrum of systems and software life cycle activities distributed across a variety of hosts, an integration, verification, and validation host with test bed, and distributed targets. The requirement for the early establishment and use of an apporopriate Computer Systems and Software Engineering Support Environment is identified. This environment will support the Research and Development Productivity challenges presented by the space station computing system.
The digital control systems for the Under-the-Wing (UTW) and Over-the-Wing (OTW) engines developed on the NASA/General Electric Quiet Clean Shorthaul Experimental Engine (QCSEE) program are described. The system to control engine variables includes three major functional parts: system sensors, digital control and system actuators. One of the primary control system functions is to prevent the engine from exceeding speed or temperature limits. The UTW control system also provides fault detection and condition monitoring. The control system requirements for the OTW engine are essentially the same as the UTW engine, however the inlet Mach number control requirement is eliminated, and failure indication and corrective action and full authority digital control are added. The digital controls scheduled the engine variables and maintained engine operation within all physical limits throughout the test program of approximately 200 hours of operation and provided stable and accurate control of both engines.
This paper examines the question of cost, from the birth of a program to its conclusion, particularly from the point of view of large multi-center programs, and suggests how to avoid some of the traps and pitfalls. Emphasis is given to cost in the systems engineering process, but there is an inevitable overlap with program management. (These terms, systems engineering and program management, have never been clearly defined.) In these days of vast Federal budget deficits and increasing overseas competition, it is imperative that we get more for each research and development dollar. This is the only way we will retain our leadership in high technology and, in the long run, our way of life.
This report details the use of infrared imaging for temperature measurement and thermal pattern determination during simulated altitude engine testing in the NASA Lewis Propulsion Systems Laboratory. Three identical argon-cooled imaging systems were installed in the facility exhaust collector behind sapphire windows to look at engine internal surfaces. The report describes the components of each system, presents the specifics of the complicated installation, and explains the operation of the systems during engine testing. During the program, several problems emerged, such as argon contamination system, component overheating, cracked sapphire windows, and other unexplained effects. This report includes a summary of the difficulties as well as the solutions developed. The systems performed well, considering they were in an unusually harsh exhaust environment. Both video and digital data were recorded, and the information provided valuable material for the engineers and designers to quickly make any necessary design changes to the engine hardware cooling system. The knowledge and experience gained during this program greatly simplified the installation and use of the systems during later test programs in the facility. The infrared imaging systems have significantly enhanced the measurement capabilities of the facility, and have become an outstanding and versatile testing resource in the Propulsion Systems Laboratory.
The LAWS phase 1 and phase 2 studies have been completed on schedule and have led to significant advances in CO2 laser development. The Phase 2 Design Definition Study has shown that a large scanning mirror/high pulse energy laser LAWS Instrument is feasible and within the existing technology. The capability to monitor wind velocities with backscatter ratios of 10(exp 11) m(exp -1) SR(exp -1) is feasible. The weight budget allocated for the baseline LAWS is adequate, and sufficient reserves exist with the potential downsized configuration. With the possible decrease in available power from the baseline of 2.2 kW guideline, power and shot management is critical for the baseline configuration (15 to 20 J). This is particularly true during the 100 day occultation period each year. With the downsized configurations (5 to 7 J), power management is still necessary during the occultation but is primarily limited to shot management over the polar regions. The breadboard effort has produced significant laser advances for a tight 18 month schedule and the minimum budgets available from NASA, Lockheed, and TDS. Using the NASA funds and Lockheed and TDS fixed assets budgets, the breadboard was designed, fabricated, and brought on-line with first laser light within 16 months after ATP. First laser beam was obtained on 21 April 1992 at a 5 J power level. Tests since then have been conducted at sustained, repetitive pulse levels of over 7 J and 20 Hz. This is an increase of over two or three times greater than any system previously developed from this type laser. Increased power levels and additional life tests will be accomplished in the next LAWS phase. The Lockheed LAWS design will operate in the gravity gradient mode on-orbit, and all possible instrument vibration and jitter modes have been considered. Adequate pointing stability and control is state-of-the-art technology for the critical time periods, frequency rates, and control responses required by LAWS. Lockheed recommends a 6-1/2 year phase C/D program for LAWS to provide adequate feedback from the engineering unit and the qualification unit to the final flight unit. Assuming a one year period for LAWS integration to the spacecraft, followed by a six-month period for launch vehicle integration, LAWS could be successfully developed and launched in eight years. Our baseline design or downsized design can be accommodated by either the Atlas 2AS or the Delta launch vehicles. Lockheed's recommendation is that, based on the successful phase 2 design study and breadboard program, a follow-on 18 month extended breadboard testing program and additional system engineering studies, primarily in interfacing with a to be defined platform, be initiated. This should be immediately followed by the phase C/D program, leading to a LAWS launch in late 2001 or early 2002.
Artificial intelligence aids engineers and technicians in controlling and monitoring complicated systems. Operations Analyst for Distributed Systems (OPERA) software is developmental suite of expert-system computer programs helping engineers and technicians operating from number of computer workstations to control and monitor spacecraft during prelaunch and launch phases of operation. OPERA designed to serve as consultant to operating engineers and technicians. It preprocesses incoming data, using expertise collected from conglomerate of specialists in design and operation of various parts of system. Driven by menus and mouse-activated commands. Modified versions of OPERA used in chemical-processing plants, factories, banks, and other enterprises in which there are distributed-computer systems including computers that monitor or control other computers.
NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.