Search NASA⌕ Search

SEARCH · Search NASA

Results for “System Engineering Processes”

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 1,423 records · Page 79

Three Dimensional Rover/Lander/Orbiter Mission-Planning (3D-ROMPS) System: A Modern Approach to Mission Planning

NASA's current mission planning system is based on point design, two-dimensional display, spread sheets, and report technology. This technology does not enable engineers to analyze the results of parametric studies of missions plans. This technology will not support the increased observational complexity and data volume of missions like Cassini, Mars Reconnaissance Orbiter (MRO), Mars Science Laboratory (MSL), and Mars Sample Return (MSR). The goal of the 3D-ROMPS task has been to establish a set of operational mission planning and analysis tools in the Image Processing Laboratory (IPL) Mission Support Area (MSA) that will respond to engineering requirements for planning future Solar System Exploration (SSE) missions using a three-dimensional display.

Scharfe, Nathan D.↗

Shape Memory Alloy Actuator Design: CASMART Collaborative Best Practices

Upon examination of shape memory alloy (SMA) actuation designs, there are many considerations and methodologies that are common to them all. A goal of CASMART's design working group is to compile the collective experiences of CASMART's member organizations into a single medium that engineers can then use to make the best decisions regarding SMA system design. In this paper, a review of recent work toward this goal is presented, spanning a wide range of design aspects including evaluation, properties, testing, modeling, alloy selection, fabrication, actuator processing, design optimization, controls, and system integration. We have documented each aspect, based on our collective experiences, so that the design engineer may access the tools and information needed to successfully design and develop SMA systems. Through comparison of several case studies, it is shown that there is not an obvious single, linear route a designer can adopt to navigate the path of concept to product. SMA engineering aspects will have different priorities and emphasis for different applications.

Benafan, Othmane↗

A parallel strategy for implementing real-time expert systems using CLIPS

As evidenced by current literature, there appears to be a continued interest in the study of real-time expert systems. It is generally recognized that speed of execution is only one consideration when designing an effective real-time expert system. Some other features one must consider are the expert system's ability to perform temporal reasoning, handle interrupts, prioritize data, contend with data uncertainty, and perform context focusing as dictated by the incoming data to the expert system. This paper presents a strategy for implementing a real time expert system on the iPSC/860 hypercube parallel computer using CLIPS. The strategy takes into consideration not only the execution time of the software, but also those features which define a true real-time expert system. The methodology is then demonstrated using a practical implementation of an expert system which performs diagnostics on the Space Shuttle Main Engine (SSME). This particular implementation uses an eight node hypercube to process ten sensor measurements in order to simultaneously diagnose five different failure modes within the SSME. The main program is written in ANSI C and embeds CLIPS to better facilitate and debug the rule based expert system.

Ilyes, Laszlo A.↗

Method of depositing a coating on Si-based ceramic composites

A process of depositing a coating system suitable for use as an environmental barrier coating on various substrate materials, particularly those containing silicon and intended for high temperature applications such as the hostile thermal environment of a gas turbine engine. The process comprises depositing a first coating layer containing mullite, and preferably a second coating layer of an alkaline earth aluminosilicate, such as barium-strontium-aluminosilicate (BSAS), by thermal spraying while maintaining the substrate at a temperature of 800.degree. C. or less, preferably 500.degree. C. or less, by which a substantially crack-free coating system is produced with desirable mechanical integrity.

Wang, Hongyu↗

Knowledge-based requirements analysis for automating software development

We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.

Markosian, Lawrence Z.↗

Propellant Delivery via VDC Driven Pump

The SMART (Scalable Mobile Autonomous Rocket engine Test) testbed system initiative at SSC was conceived to attempt to address many of the principal cost drivers in developing and maintaining a rocket engine test facility. The system (optimized to test engines and components generating up to 10K lbf nominal thrust) is serving as a testbed for innovative technologies and processes to provide lower cost test services with a rapid test cadence and expedient turnaround times. The system can also potentially be used as a testbed to test other related technologies relevant to surface situations (e.g., moon, Mars associated with crogenic fluid management, engine/component testing, autonomous operations, etc.). This FY20 CIF project, being conducted as part of the SMART testbed system, is developing and testing a propellant delivery system via electrically driven centrifugal pumps (obviating dependence upon Multi-Layer Pressure Vessels) with configuration and operation by a minimal number of personnel. During FY20 the team identified the requirements and worked with P3 and Masten Space Systems to develop the long lead (9 months after receipt of order) items, the 400 VDC pumps, for delivery in mid FY21. Since control of the 400 VDC pump motor is not well developed the team has established heuristics to control flows in LN2 at off nominal shaft speeds to allow deep throttling of the pump in flow test scenarios. Various test scenarios including nominal i.e. high flow high pressure, high flow low pressure, low flow high pressure, low flow low pressure, minimum throttle step change, and low inlet pressure cavitation testing were developed ahead of the anticipated hardware delivery and test. FY20 COVID Stage 3 conditions restricted access to the center and hindered lab work, so efforts focused on the system design and testing plans along with the project procurement paperwork for the hardware... now with its anticipated delivery in spring FY21. Some limited access to the center is expected by spring/summer FY21 for the continuing second year (FY21) CIF project effort meant to be focused upon system integration and initial testing.

Aaron Head↗

A Framework for Performing Verification and Validation in Reuse Based Software Engineering

Verification and Validation (V&V) is currently performed during application development for many systems, especially safety-critical and mission- critical systems. The V&V process is intended to discover errors, especially errors related to critical processing, as early as possible during the development process. The system application provides the context under which the software artifacts are validated. This paper describes a framework that extends V&V from an individual application system to a product line of systems that are developed within an architecture-based software engineering environment. This framework includes the activities of traditional application-level V&V, and extends these activities into domain engineering and into the transition between domain engineering and application engineering. The framework includes descriptions of the types of activities to be performed during each of the life-cycle phases, and provides motivation for the activities.

Addy, Edward A.↗

SpaceCube Mini

This version of the SpaceCube will be a full-fledged, onboard space processing system capable of 2500+ MIPS, and featuring a number of plug-andplay gigabit and standard interfaces, all in a condensed 3x3x3 form factor [less than 10 watts and less than 3 lb (approximately equal to 1.4 kg)]. The main processing engine is the Xilinx SIRF radiation- hardened-by-design Virtex-5 FX-130T field-programmable gate array (FPGA). Even as the SpaceCube 2.0 version (currently under test) is being targeted as the platform of choice for a number of the upcoming Earth Science Decadal Survey missions, GSFC has been contacted by customers who wish to see a system that incorporates key features of the version 2.0 architecture in an even smaller form factor. In order to fulfill that need, the SpaceCube Mini is being designed, and will be a very compact and low-power system. A similar flight system with this combination of small size, low power, low cost, adaptability, and extremely high processing power does not otherwise exist, and the SpaceCube Mini will be of tremendous benefit to GSFC and its partners. The SpaceCube Mini will utilize space-grade components. The primary processing engine of the Mini is the Xilinx Virtex-5 SIRF FX-130T radiation-hardened-by-design FPGA for critical flight applications in high-radiation environments. The Mini can also be equipped with a commercial Xilinx Virtex-5 FPGA with integrated PowerPCs for a low-cost, high-power computing platform for use in the relatively radiation- benign LEOs (low-Earth orbits). In either case, this version of the Space-Cube will weigh less than 3 pounds (.1.4 kg), conform to the CubeSat form-factor (10x10x10 cm), and will be low power (less than 10 watts for typical applications). The SpaceCube Mini will have a radiation-hardened Aeroflex FPGA for configuring and scrubbing the Xilinx FPGA by utilizing the onboard FLASH memory to store the configuration files. The FLASH memory will also be used for storing algorithm and application code for the PowerPCs and the Xilinx FPGA. In addition, it will feature highspeed DDR SDRAM (double data rate synchronous dynamic random-access memory) to store the instructions and data of active applications. This version will also feature SATA-II and Gigabit Ethernet interfaces. Furthermore, there will also be general-purpose, multi-gigabit interfaces. In addition, the system will have dozens of transceivers that can support LVDS (low-voltage differential signaling), RS-422, or SpaceWire. The SpaceCube Mini includes an I/O card that can be customized to meet the needs of each mission. This version of the SpaceCube will be designed so that multiple Minis can be networked together using SpaceWire, Ethernet, or even a custom protocol. Scalability can be provided by networking multiple SpaceCube Minis together. Rigid-Flex technology is being targeted for the construction of the SpaceCube Mini, which will make the extremely compact and low-weight design feasible. The SpaceCube Mini is designed to fit in the compact CubeSat form factor, thus allowing deployment in a new class of missions that the previous SpaceCube versions were not suited for. At the time of this reporting, engineering units should be available in the summer 2012.

Michael Lin↗

Propulsion Design With Freeform Fabrication (PDFF)

The nation is challenged to decrease the cost and schedule to develop new space transportation propulsion systems for commercial, scientific, and military purposes. Better design criteria and manufacturing techniques for small thrusters are needed to meet current applications in missile defense, space, and satellite propulsion. The requirements of these systems present size, performance, and environmental demands on these thrusters that have posed significant challenges to the current designers and manufacturers. Designers are limited by manufacturing processes, which are complex, costly, and time consuming, and ultimately limited in their capabilities. The PDFF innovation vastly extends the design opportunities of rocket engine components and systems by making use of the unique manufacturing freedom of solid freeform rapid prototype manufacturing technology combined with the benefits of ceramic materials. The unique features of PDFF are developing and implementing a design methodology that uses solid freeform fabrication (SFF) techniques to make propulsion components with significantly improved performance, thermal management, power density, and stability, while reducing development and production costs. PDFF extends the design process envelope beyond conventional constraints by leveraging the key feature of the SFF technique with the capability to form objects with nearly any geometric complexity without the need for elaborate machine setup. The marriage of SFF technology to propulsion components allows an evolution of design practice to harmonize material properties with functional design efficiency. Reduced density of materials when coupled with the capability to honeycomb structure used in the injector will have significant impact on overall mass reduction. Typical thrusters in use for attitude control have 60 90 percent of its mass in the valve and injector, which is typically made from titanium. The combination of material and structure envisioned for use in an SFF thruster design could reduce thruster weight by a factor of two or more. The thrust-to-weight ratios for such designs can achieve 1,000:1 or more, depending on chamber pressure. The potential exists for continued development in materials, size, speed, accuracy of SFF techniques, which can lead to speculative developments of PDFF processes such as fabrication of custom human interface devices like masks, chairs, and clothing, and advanced biomedical application to human organ reconstruction. Other potential applications are: higher fidelity lower cost test fixtures for probes and inspection, disposable thrusters, and ISRU (in situ resource utilization) for component production in space or on Lunar and Martian missions, and application for embedding MEMS (microelectromechanical systems) during construction process of form changing aerostructure/dynamic structures.

Barnes, Daudi↗

PVEX: An expert system for producibility/value engineering

PVEX is described as an expert system that solves the problem of selection of the material and process in missile manufacturing. The producibility and the value problem has been deeply studied in the past years, and was written in dBase III and PROLOG before. A new approach is presented in that the solution is achieved by introducing hypothetical reasoning, heuristic criteria integrated with a simple hypertext system and shell programming. PVEX combines KMS with Unix scripts which graphically depicts decision trees. The decision trees convey high level qualitative problem solving knowledge to users, and a stand-alone help facility and technical documentation is available through KMS. The system developed is considerably less development costly than any other comparable expert system.

Lam, Chun S.↗

Investigation of low cost material processes for liquid rocket engines

The development of low cost material processes is essential to the achievement of economical liquid rocket propulsion systems in the next century. This paper will present the results of the evaluation of some promising material processes including powder metallurgy, vacuum plasma spray, metal spray forming, and bulge forming. The physical and mechanical test results from the samples and subscale hardware fabricated from high strength copper alloys and superalloys will be discussed.

Nguyentat, Thinh↗

Salient Characteristics for Terrestrial Analog Engineering Test Sites

The use of terrestrial analog sites is an essential component of the development process for systems that are planned for lunar and planetary surfaces. These sites can also be valuable for training personnel who are expected to operate those systems. The fact that the site is an integral element, capable of influencing data and impacting test results, must not be overlooked. For tests performed in analog environments to be truly valid it is essential that the relevant characteristics of the employed sites be thoroughly understood. It is also critical that a comparative evaluation be made to assess the similarity of the analog sites to target planetary sites. Examples of relevant characteristics include terrain, soil properties, meteorology, geologic features, biological history, and remoteness. The importance of each of the characteristics varies with the type of extraterrestrial activity to be conducted. As a result, a site that is ideal for one purpose may be totally inadequate for another. It may also be appropriate to utilize multiple sites of increasing fidelity as the development process evolves. For example, early in the development process, the use of lower-fidelity sites may be elected - especially if they are available for a lower cost. Later, it may be necessary to employ higher-fidelity sites to capture greater realism, even if there is an associated increased cost. Finally, when interpreting the results of field tests, it is necessary to understand the sensitivity of the results to the relevant conditions. Knowledge of characteristics and sensitivity of results is particularly important when using field test results to validate analytical model predictions. This is especially true for activities that involve physical interaction with the site. Examples would include tests of rovers or other vehicles and associated trafficability modeling, spacesuit mobility tests, and tests associated with system deployment operations.

Watson, J.K.↗

Attacking the IEC-61131 Logic Engine in Programmable Logic Controllers in Industrial Control Systems

In industrial control systems (ICS), programmable logic controllers (PLCs) directly monitor and control a physical process such as nuclear power plants, gas pipelines, and water treatment. They are equipped with a control logic written in IEC-61131 languages (e.g., ladder logic and structured text) that defines how a PLC should control a physical process. A PLC's control logic is a usual target of a cyberattack to sabotage a physical process. For instance, Stuxnet targets a control logic of a Siemens S7-300 PLC to damage a nuclear facility's centrifuges. The existing attacks in the literature generally focus only on injecting malicious control logic into a PLC. This paper presents a new dimension of control logic attacks that target the control logic engine (responsible for running a control logic) of a PLC. It demonstrates that a cyberattack can disable the control logic engine successfully by exploiting inherent PLC features such as program mode and starting/stopping engine. We develop two novel case studies on control logic engine attacks by employing the MITRE ATT\&CK knowledge base on the real-world PLCs used in industry settings, i.e., 1) Schweitzer Engineering Laboratory (SEL)'s Real-Time Automation Controller (SEL-3505 RTAC) equipped with security features such as encrypted traffic and device-level access control, and 2) traditional PLCs, i.e., Schneider Electric's Modicon M221, Allen-Bradley's MicroLogix 1400 and 1100 that do not have security features. The case studies present the internals of the logic engine attacks and facilitate the ICS research community and industry to understand the attack vectors on the control logic engine. We evaluate the effectiveness of the control engine attacks on a power substation, a 4-floor elevator, and a conveyor belt to demonstrate their real-world impact of halting a physical process.

Ali qasim, Syed↗

Vexcel Spells Excellence for Earth and Space

With assistance from Stennis Space Center, Vexcel was able to strengthen the properties of its Apex Ground Station(TM), an affordable, end-to-end system that comes complete with a tracking antenna that permits coverage within an approximate 2,000-kilometer radius of its location, a high speed direct-to-disk data acquisition system that can download information from virtually any satellite, and data processing software for virtually all synthetic aperture radar and optical satellite sensors. Vexcel is using an Apex system linked to the Terra satellite to help scientists and NASA personnel measure land and ocean surface temperatures, detect fires, monitor ocean color and currents, produce global vegetation maps and data, and assess cloud characteristics and aerosol concentrations. In addition, Vexcel is providing NASA with close-range photogrammetry software for the International Space Station. The technology, commercially available as FotoG(TM), was developed with SBIR funding and support from NASA's Jet Propulsion Laboratory. Commercially, FotoG is used for demanding projects taken on by engineering firms, nuclear power plants, oil refineries, and process facilities. A version of Vexcel's close-range photo measurement system was also used to create virtual 3-D backdrops for a high-tech science fiction film.

Source record↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

Modeling the effects of river flow on population dynamics of piping plovers (Charadrius melodus) and least terns (Sternula antillarum) nesting on the Missouri River

Humans make extensive use of rivers and floodplains for economic benefits including agriculture, hydropower, commerce and recreation. Economic development of floodplains subsequently requires control of river levels to avoid flood damage. This process began in the Missouri River basin in the 1890s with the construction of a series of hydropower dams in Montana and escalated to new levels with the approval of the Pick-Sloan plan in the 1944 Flood Control Act. Maximizing these human uses of the river led to changes in and losses of hydrological and ecological processes, ultimately resulting in the federal listing of three fish and wildlife species under the Endangered Species Act: the pallid sturgeon (Scaphirhyncus albus; 1983), the piping plover (Charadrius melodus; 1984), and the interior population of least tern (Sternula antillarum; 1985). The listing of terns and plovers did not affect river management until the United States Army Corps of Engineers (USACE) proposed to modify the governing document of the Missouri River Mainstem System, the Master Manual, a process which was completed in 2003. Although there was little disagreement over the habitat conditions that terns and plovers used for nesting, there was substantial disagreement over the amount of habitat necessary for terns and plovers to meet population recovery goals. Answering this question requires forecasting species-specific population responses to dynamic habitat affected by both human actions (reservoir management and habitat restoration) and natural variability in precipitation. Piping plovers and least terns nest along the Missouri River from Fort Peck, Montana to just north of Sioux City, Iowa (Figure 1). Both species prefer to nest on sand and fine gravel substrates with no or sparse vegetation cover (Prindiville Gaines and Ryan, 1988; Sherfy et al., 2012), such as riverine sandbars (emergent sandbar habitat; ESH). Piping plovers also nest on reservoir shorelines that lack vegetation cover (Anteau et al., 2012). The amount of ESH available for nesting in a given year is strongly affected by the amount of water entering the Missouri River system through precipitation and the management of water flow from six reservoirs operated by the USACE on the mainstem Missouri River. Prior to the construction of dams, the Missouri River experienced bimodal peak flows in spring and early summer in concordance with the melting of plains and mountain snowpack (Galat and Lipkin, 2000). Flows decreased during summer months, with river stage then dependent upon rainfall. The combination of consistent high flows and occasional extreme high flows, together with the meandering characteristic of the river, regularly reshaped and scoured vegetation from ESH.

adaptive management↗