Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “#engineering”

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 721 records · Page 40

Preliminary Altitude Operational Characteristics of a J57-P1 Turbojet Engine

The operational characteristics of a J57-P1 turbojet engine have been investigated at altitudes between 15,000 and 66,000 feet in the Lewis altitude wind tunnel. Included in this study is a discussion of fuel nozzle coking, the altitude operating limits with and without the standard engine control, the compressor surge characteristics, and the engine starting and windmilling characteristics. Severe circumferential turbine outlet temperature gradients which occurred at high altitude as a result of fuel nozzle coking were alleviated by the manufacturer's change in the fuel flow divider schedule and in a nozzle gasket material. Compressor air bleed is required to prevent surge of the outboard compressor in the low engine speed region. The maximum altitude at which the engine was operated without the control was about 66,000 feet at 0.8 flight Mach number and at a reduced engine speed to avoid compressor surge; with the engine control in operation, the altitude operating limit is reduced to approximately 59,000 feet. The maximum altitude at which the engine was started was about 40,000 feet.

Wallner, Lewis E.↗

Preliminary Results of Altitude-Wind-Tunnel Investigation of X24C-4B Turbojet Engine. I - Pressure and Temperature Distributions

Pressures and temperatures throughout the X24C-4B turbojet engine are presented in both tabular and graphical forms to show the effect of altitude, flight Mach number, and engine speed on the internal operation of the engine. These data were obtained in the NACA Cleveland altitude wind tunnel at simulated altitudes from 5000 to 45,000 feet, simulated flight Mach numbers from 0.25 to 1.08, and engine speeds from 4000 to 12,500 rpm. Location and detail drawings of the instrumentation installed at seven survey stations in the engine are shown. Application of generalization factors to pressures and temperatures at each measuring station for the range of altitudes investigated showed that the data did not generalize above an altitude of 25,000 feet. Total-pressure distribution at the compressor outlet varied only with change in engine speed. At altitudes above 35,000 feet and engine speeds above 11,000 rpm, the peak temperature at the turbine-outlet annulus moved inward toward the root of the blade, which is undesirable from blade-stress considerations. The temperature levels at the turbine outlet and the exhaust-nozzle outlet were lowered as the Mach number was increased. The static-pressure measurements obtained at each stator stage of the compressor showed a pressure drop through the inlet guide vanes and the first-stage rotor at high engine speeds. The average values measured by the manufacturer's instrumentation werein close agreement with the average values obtained with NACA instrumentation.

Prince, William R.↗

CECE: A Deep Throttling Demonstrator Cryogenic Engine for NASA's Lunar Lander

As one of the first technology development programs awarded under NASA's Vision for Space Exploration, the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic Lunar Lander engine for use across multiple human and robotic lunar exploration mission segments with extensibility to Mars. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the RL10, to develop and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in a high-energy, cryogenic engine. NASA Marshall Space Flight Center and NASA Glenn Research Center personnel were integral design and analysis team members throughout the requirements assessment, propellant studies and the deep throttling demonstrator elements of the program. The testbed selected for the initial deep throttling demonstration phase of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. In just nine months from technical program start, CECE Demonstrator No. 1 engine testing in April/May 2006 at PWR's E06 test stand successfully demonstrated in excess of 10:1 throttling of the hydrogen/oxygen expander cycle engine. This test provided an early demonstration of a viable, enabling cryogenic propulsion concept with invaluable system-level technology data acquisition toward design and development risk mitigation for both the subsequent CECE Demonstrator No. 2 program and to the future Lunar Lander Design, Development, Test and Evaluation effort.

Giuliano, Victor J.↗

Efficient Model-Based Diagnosis Engine

An efficient diagnosis engine - a combination of mathematical models and algorithms - has been developed for identifying faulty components in a possibly complex engineering system. This model-based diagnosis engine embodies a twofold approach to reducing, relative to prior model-based diagnosis engines, the amount of computation needed to perform a thorough, accurate diagnosis. The first part of the approach involves a reconstruction of the general diagnostic engine to reduce the complexity of the mathematical-model calculations and of the software needed to perform them. The second part of the approach involves algorithms for computing a minimal diagnosis (the term "minimal diagnosis" is defined below). A somewhat lengthy background discussion is prerequisite to a meaningful summary of the innovative aspects of the present efficient model-based diagnosis engine. In model-based diagnosis, the function of each component and the relationships among all the components of the engineering system to be diagnosed are represented as a logical system denoted the system description (SD). Hence, the expected normal behavior of the engineering system is the set of logical consequences of the SD. Faulty components lead to inconsistencies between the observed behaviors of the system and the SD (see figure). Diagnosis - the task of finding faulty components - is reduced to finding those components, the abnormalities of which could explain all the inconsistencies. The solution of the diagnosis problem should be a minimal diagnosis, which is a minimal set of faulty components. A minimal diagnosis stands in contradistinction to the trivial solution, in which all components are deemed to be faulty, and which, therefore, always explains all inconsistencies.

Fijany, Amir↗

An Object-Oriented Computer Code for Aircraft Engine Weight Estimation

Reliable engine-weight estimation at the conceptual design stage is critical to the development of new aircraft engines. It helps to identify the best engine concept amongst several candidates. At NASA Glenn Research Center (GRC), the Weight Analysis of Turbine Engines (WATE) computer code, originally developed by Boeing Aircraft, has been used to estimate the engine weight of various conceptual engine designs. The code, written in FORTRAN, was originally developed for NASA in 1979. Since then, substantial improvements have been made to the code to improve the weight calculations for most of the engine components. Most recently, to improve the maintainability and extensibility of WATE, the FORTRAN code has been converted into an object-oriented version. The conversion was done within the NASA's NPSS (Numerical Propulsion System Simulation) framework. This enables WATE to interact seamlessly with the thermodynamic cycle model which provides component flow data such as airflows, temperatures, and pressures, etc., that are required for sizing the components and weight calculations. The tighter integration between the NPSS and WATE would greatly enhance system-level analysis and optimization capabilities. It also would facilitate the enhancement of the WATE code for next-generation aircraft and space propulsion systems. In this paper, the architecture of the object-oriented WATE code (or WATE++) is described. Both the FORTRAN and object-oriented versions of the code are employed to compute the dimensions and weight of a 300-passenger aircraft engine (GE90 class). Both versions of the code produce essentially identical results as should be the case.

Tong, Michael T.↗

Nitrous Oxide/Paraffin Hybrid Rocket Engines

Nitrous oxide/paraffin (N2OP) hybrid rocket engines have been invented as alternatives to other rocket engines especially those that burn granular, rubbery solid fuels consisting largely of hydroxyl- terminated polybutadiene (HTPB). Originally intended for use in launching spacecraft, these engines would also be suitable for terrestrial use in rocket-assisted takeoff of small airplanes. The main novel features of these engines are (1) the use of reinforced paraffin as the fuel and (2) the use of nitrous oxide as the oxidizer. Hybrid (solid-fuel/fluid-oxidizer) rocket engines offer advantages of safety and simplicity over fluid-bipropellant (fluid-fuel/fluid-oxidizer) rocket en - gines, but the thrusts of HTPB-based hybrid rocket engines are limited by the low regression rates of the fuel grains. Paraffin used as a solid fuel has a regression rate about 4 times that of HTPB, but pure paraffin fuel grains soften when heated; hence, paraffin fuel grains can, potentially, slump during firing. In a hybrid engine of the present type, the paraffin is molded into a 3-volume-percent graphite sponge or similar carbon matrix, which supports the paraffin against slumping during firing. In addition, because the carbon matrix material burns along with the paraffin, engine performance is not appreciably degraded by use of the matrix.

Zubrin, Robert↗

Unleashing Lessons: Sharing Stories About the Fine Art of Systems Engineering

NASA leaders have a responsibility to share their unique oral histories with junior-level employees on whom NASA's future depends. This presentation will give a few examples of how the imaginative, flexible art of systems engineering is as necessary to mission success as is the rigorous, disciplined side of engineering. Engineering space systems involves many disciplines propulsion, loads, dynamics, and so forth that are based on the foundations of scientific principles and methodology and the application of the laws of physics. The term rocket scientist is an apt term, considering that the underlying chemical properties of propellants and the subatomic properties of materials must be understood to harness the powerful energy necessary to escape Earth's gravity in machines that can withstand the stresses and forces to which they are subjected, not to mention the harsh space environments in which they must work. This is a simplistic, yet illustrative, explanation of the scientific side of the engineer s challenge. Bringing together these individual parts into a solid system goes beyond the science of engineering to employ the art of systems engineering. Systems engineers are known for their ability to integrate various solutions to meet or exceed challenging requirements. As the old adage goes, measure twice and cut once. The act of measuring is balancing rigid, inflexible requirements with creative compromises to attain the optimum solution to the challenge of space flight. Then, we cut out those answers that are too risky, expensive, dangerous, and so forth. The process of sharing stories about the little-discussed art of engineering, also known as the art of compromise, will equip the workforce to subjectively judge the best right answer from among the many presented, while objectively integrating the various piece parts into a unified whole.

Singer, Christopher E.↗

System Would Detect Foreign-Object Damage in Turbofan Engine

A proposed data-fusion system, to be implemented mostly in software, would further process the digitized and preprocessed outputs of sensors in a turbofan engine to detect foreign-object damage (FOD) [more precisely, damage caused by impingement of such foreign objects as birds, pieces of ice, and runway debris]. The proposed system could help a flight crew to decide what, if any, response is necessary to complete a flight safely, and could aid mechanics in deciding what post-flight maintenance action might be needed. The sensory information to be utilized by the proposed system would consist of (1) the output of an accelerometer in an engine-vibration-monitoring subsystem and (2) features extracted from a gas path analysis. ["Gas path analysis" (GPA) is a term of art that denotes comprehensive analysis of engine performance derived from readings of fuel-flow meters, shaft-speed sensors, temperature sensors, and the like.] The acceleration signal would first be processed by a wavelet-transform-based algorithm, using a wavelet created for the specific purpose of finding abrupt FOD-induced changes in noisy accelerometer signals. Two additional features extracted would be the amplitude of vibration (determined via a single- frequency Fourier transform calculated at the rotational speed of the engine), and the rate of change in amplitude due to an FOD-induced rotor imbalance. This system would utilize two GPA features: the fan efficiency and the rate of change of fan efficiency with time. The selected GPA and vibrational features would be assessed by two fuzzy-logic inference engines, denoted the "Gas Path Expert" and the "Vibration Expert," respectively (see Figure 1). Each of these inference engines would generate a "possibility" distribution for occurrence of an FOD event: Each inference engine would assign, to its input information, degrees of membership, which would subsequently be transformed into basic probability assignments for the gas path and vibration components. The outputs of the inference engines would be fused by use of Dempster s combination algorithm (more precisely, an algorithm, based on the Dempster-Shafer-Yager theory of evidence, for fusing uncertain or imprecise information) to provide a reduced body of information to a human or computer decision maker. Figure 2 depicts some outputs generated in response to simulated accelerometer and GPA signals

Torso, James A.↗

Rocketdyne - J-2 Saturn V 2nd and 3rd Stage Engine

The J-2 engine was unique in many respects. Technology was not nearly as well-developed in oxygen/hydrogen engines at the start of the J-2 project. As a result, it experienced a number of "teething" problems. It was used in two stages on the Saturn V vehicle in the Apollo Program, as well as on the later Skylab and Apollo/Soyuz programs. In the Apollo Program, it was used on the S-II stage, which was the second stage of the Saturn V vehicle. There were five J-2 engines at the back end of the S-II Stage. In the S-IV-B stage, it was a single engine, but that single engine had to restart. The Apollo mission called for the entire vehicle to reach orbital velocity in low Earth orbit after the first firing of the Saturn-IV-B stage and, subsequently, to fire a second time to go on to the moon. The engine had to be man-rated (worthy of transporting humans). It had to have a high thrust rate and performance associated with oxygen/hydrogen engines, although there were some compromises there. It had to gimbal for thrust vector control. It was an open-cycle gas generator engine delivering up to 230,000 pounds of thrust.

Coffman, Paul↗

CECE: Expanding the Envelope of Deep Throttling in Liquid Oxygen/Liquid Hydrogen Rocket Engines For NASA Exploration Missions

As one of the first technology development programs awarded by NASA under the Vision for Space Exploration, the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic engine supporting ongoing trade studies for NASA s Lunar Lander descent stage. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the PWR RL10, to develop technology and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in a high-energy cryogenic engine. The testbed selected for the deep throttling demonstration phases of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. Three series of demonstrator engine tests, the first in April-May 2006, the second in March-April 2007 and the third in November-December 2008, have demonstrated up to 13:1 throttling (104% to 8% thrust range) of the hydrogen/oxygen expander cycle engine. The first two test series explored a propellant feed system instability ("chug") environment at low throttled power levels. Lessons learned from these two tests were successfully applied to the third test series, resulting in stable operation throughout the 13:1 throttling range. The first three tests have provided an early demonstration of an enabling cryogenic propulsion concept, accumulating over 5,000 seconds of hot fire time over 27 hot fire tests, and have provided invaluable system-level technology data toward design and development risk mitigation for the NASA Altair and future lander propulsion system applications. This paper describes the results obtained from the highly successful third test series as well as the test objectives and early results obtained from a fourth test series conducted over March-May 2010

Giuliano, Victor J.↗

A High-Fidelity Simulation of a Generic Commercial Aircraft Engine and Controller

A new high-fidelity simulation of a generic 40,000 lb thrust class commercial turbofan engine with a representative controller, known as CMAPSS40k, has been developed. Based on dynamic flight test data of a highly instrumented engine and previous engine simulations developed at NASA Glenn Research Center, this non-proprietary simulation was created especially for use in the development of new engine control strategies. C-MAPSS40k is a highly detailed, component-level engine model written in MATLAB/Simulink (The MathWorks, Inc.). Because the model is built in Simulink, users have the ability to use any of the MATLAB tools for analysis and control system design. The engine components are modeled in C-code, which is then compiled to allow faster-than-real-time execution. The engine controller is based on common industry architecture and techniques to produce realistic closed-loop transient responses while ensuring that no safety or operability limits are violated. A significant feature not found in other non-proprietary models is the inclusion of transient stall margin debits. These debits provide an accurate accounting of the compressor surge margin, which is critical in the design of an engine controller. This paper discusses the development, characteristics, and capabilities of the C-MAPSS40k simulation

May, Ryan D.↗

Influence of Alternative Engine Concepts on LCTR2 Sizing and Mission Profile

The Large Civil Tiltrotor (LCTR) was developed as part of the NASA Heavy Lift Rotorcraft Systems Investigation in order to establish a consistent basis for evaluating the benefits of advanced technology for large tiltrotors. The concept has since evolved into the second-generation LCTR2, designed to carry 90 passengers for 1,000 nm at 300 knots, with vertical takeoff and landing. This paper examines the impact of advanced propulsion system concepts on LCTR2 sizing. Two concepts were studied: an advanced, single-speed engine with a conventional power turbine layout (Advanced Conventional Engine, or ACE), and a variable-speed power turbine engine (VSPT). The ACE is the lighter engine, but requires a multi-speed (shifting) gearbox, whereas the VSPT uses a lighter, fixed-ratio gearbox. The NASA Design and Analysis of Rotorcraft (NDARC) design code was used to study the trades between rotor and engine efficiency and weight. Rotor performance was determined by Comprehensive Analytical Model of Rotorcraft Aerodynamics and Dynamics (CAMRAD II), and engine performance was estimated with the Numerical Propulsion System Simulation (NPSS). Design trades for the ACE vs. VSPT are presented in terms of vehicle weight empty for variations in mission altitude and range; the effect of different One Engine Inoperative (OEI) criteria are also examined. Because of its strong effect on gearbox weight and on both rotor and engine efficiency, rotor speed was chosen as the reference design variable for comparing design trades. The two propulsion concepts had nearly identical vehicle weights and mission fuel consumption, and their relative advantages varied little with cruise altitude, mission range, or OEI criteria; high cruise altitude and low cruise tip speed were beneficial for both concepts.

Acree, C. W., Jr.↗

Engineering Technical Review Planning Briefing

The general topics covered in the engineering technical planning briefing are 1) overviews of NASA, Marshall Space Flight Center (MSFC), and Engineering, 2) the NASA Systems Engineering(SE) Engine and its implementation , 3) the NASA Project Life Cycle, 4) MSFC Technical Management Branch Services in relation to the SE Engine and the Project Life Cycle , 5) Technical Reviews, 6) NASA Human Factor Design Guidance , and 7) the MSFC Human Factors Team. The engineering technical review portion of the presentation is the primary focus of the overall presentation and will address the definition of a design review, execution guidance, the essential stages of a technical review, and the overall review planning life cycle. Examples of a technical review plan content, review approaches, review schedules, and the review process will be provided and discussed. The human factors portion of the presentation will focus on the NASA guidance for human factors. Human factors definition, categories, design guidance, and human factor specialist roles will be addressed. In addition, the NASA Systems Engineering Engine description, definition, and application will be reviewed as background leading into the NASA Project Life Cycle Overview and technical review planning discussion.

Gardner, Terrie↗

Combustion Stability of the Gas Generator Assembly from J-2X Engine E10001 and Powerpack Tests

Testing of a powerpack configuration (turbomachinery and gas generator assembly) and the first complete engine system of the liquid oxygen/liquid hydrogen propellant J-2X rocket engine have been completed at the NASA Stennis Space Center. The combustion stability characteristics of the gas generator assemblies on these two systems are of interest for reporting since considerable effort was expended to eliminate combustion instability during early development of the gas generator assembly with workhorse hardware. Comparing the final workhorse gas generator assembly development test data to the powerpack and engine system test data provides an opportunity to investigate how the nearly identical configurations of gas generator assemblies operate with two very different propellant supply systems one the autonomous pressure-fed test configuration on the workhorse development test stand, the other the pump-fed configurations on the powerpack and engine systems. The development of the gas generator assembly and the elimination of the combustion instability on the pressure-fed workhorse test stand have been reported extensively in the two previous Liquid Propulsion Subcommittee meetings 1-7. The powerpack and engine system testing have been conducted from mid-2011 through 2012. All tests of the powerpack and engine system gas generator systems to date have been stable. However, measureable dynamic behavior, similar to that observed on the pressure-fed test stand and reported in Ref. [6] and attributed to an injection-coupled response, has appeared in both powerpack and engine system tests. As discussed in Ref. [6], these injection-coupled responses are influenced by the interaction of the combustion chamber with a branch pipe in the hot gas duct that supplies gaseous helium to pre-spin the turbine during the start transient. This paper presents the powerpack and engine system gas generator test data, compares these data to the development test data, and provides additional combustion stability analyses of the configurations.

Hulka, J. R.↗

Engine Power Turbine and Propulsion Pod Arrangement Study

A study has been conducted for NASA Glenn Research Center under contract NNC10BA05B, Task NNC11TA80T to identify beneficial arrangements of the turboshaft engine, transmissions and related systems within the propulsion pod nacelle of NASA's Large Civil Tilt-Rotor 2nd iteration (LCTR2) vehicle. Propulsion pod layouts were used to investigate potential advantages, disadvantages, as well as constraints of various arrangements assuming front or aft shafted engines. Results from previous NASA LCTR2 propulsion system studies and tasks performed by Boeing under NASA contracts are used as the basis for this study. This configuration consists of two Fixed Geometry Variable Speed Power Turbine Engines and related drive and rotor systems (per nacelle) arranged in tilting nacelles near the wing tip. Entry-into-service (EIS) 2035 technology is assumed for both the engine and drive systems. The variable speed rotor system changes from 100 percent speed for hover to 54 percent speed for cruise by the means of a two speed gearbox concept developed under previous NASA contracts. Propulsion and drive system configurations that resulted in minimum vehicle gross weight were identified in previous work and used here. Results reported in this study illustrate that a forward shafted engine has a slight weight benefit over an aft shafted engine for the LCTR2 vehicle. Although the aft shafted engines provide a more controlled and centered CG (between hover and cruise), the length of the long rotor shaft and complicated engine exhaust arrangement outweighed the potential benefits. A Multi-Disciplinary Analysis and Optimization (MDAO) approach for transmission sizing was also explored for this study. This tool offers quick analysis of gear loads, bearing lives, efficiencies, etc., through use of commercially available RomaxDESIGNER software. The goal was to create quick methods to explore various concept models. The output results from RomaxDESIGNER have been successfully linked to Boeing spreadsheets that generate gear tooth geometry in Catia 3D environment. Another initial goal was to link information from RomaxDESIGNER (such as hp, rpm, gear ratio) to populate Boeing's parametric weight spreadsheet and create an automated method to estimate drive system weight. This was only partially achieved due to the variety of weight models, number of manual inputs, and qualitative assessments required. A simplified weight spreadsheet was used with data inputs from RomaxDESIGNER along with manual inputs to perform rough weight calculations.

Robuck, Mark↗

A Fully Non-metallic Gas Turbine Engine Enabled by Additive Manufacturing

The Non-Metallic Gas Turbine Engine project, funded by NASA Aeronautics Research Institute (NARI), represents the first comprehensive evaluation of emerging materials and manufacturing technologies that will enable fully nonmetallic gas turbine engines. This will be achieved by assessing the feasibility of using additive manufacturing technologies for fabricating polymer matrix composite (PMC) and ceramic matrix composite (CMC) gas turbine engine components. The benefits of the proposed effort include: 50 weight reduction compared to metallic parts, reduced manufacturing costs due to less machining and no tooling requirements, reduced part count due to net shape single component fabrication, and rapid design change and production iterations. Two high payoff metallic components have been identified for replacement with PMCs and will be fabricated using fused deposition modeling (FDM) with high temperature capable polymer filaments. The first component is an acoustic panel treatment with a honeycomb structure with an integrated back sheet and perforated front sheet. The second component is a compressor inlet guide vane. The CMC effort, which is starting at a lower technology readiness level, will use a binder jet process to fabricate silicon carbide test coupons and demonstration articles. The polymer and ceramic additive manufacturing efforts will advance from monolithic materials toward silicon carbide and carbon fiber reinforced composites for improved properties. Microstructural analysis and mechanical testing will be conducted on the PMC and CMC materials. System studies will assess the benefits of fully nonmetallic gas turbine engine in terms of fuel burn, emissions, reduction of part count, and cost. The proposed effort will be focused on a small 7000 lbf gas turbine engine. However, the concepts are equally applicable to large gas turbine engines. The proposed effort includes a multidisciplinary, multiorganization NASA - industry team that includes experts in ceramic materials and CMCs, polymers and PMCs, structural engineering, additive manufacturing, engine design and analysis, and system analysis.

manufacturing↗

Model-Based Control of an Aircraft Engine using an Optimal Tuner Approach

This paper covers the development of a model-based engine control (MBEC) method- ology applied to an aircraft turbofan engine. Here, a linear model extracted from the Commercial Modular Aero-Propulsion System Simulation 40,000 (CMAPSS40k) at a cruise operating point serves as the engine and the on-board model. The on-board model is up- dated using an optimal tuner Kalman Filter (OTKF) estimation routine, which enables the on-board model to self-tune to account for engine performance variations. The focus here is on developing a methodology for MBEC with direct control of estimated parameters of interest such as thrust and stall margins. MBEC provides the ability for a tighter control bound of thrust over the entire life cycle of the engine that is not achievable using traditional control feedback, which uses engine pressure ratio or fan speed. CMAPSS40k is capable of modeling realistic engine performance, allowing for a verification of the MBEC tighter thrust control. In addition, investigations of using the MBEC to provide a surge limit for the controller limit logic are presented that could provide benefits over a simple acceleration schedule that is currently used in engine control architectures.

Connolly, Joseph W.↗

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗