Experimental Evaluation of the New Automated Team Composition System (ATCS) by Formation of Optimal Teams for an Engineering Research Task

DTIC Science & Technology

2010-12-24

Los Angeles Police Department ) 3. LACSD ( Los Angeles County Sheriff’ Department ) 4. USDHS (US Department of Homeland Security) Candidate Roster... The present study used archival data from a UCLA (University of California Los Angeles ) engineering course in which nominally student teams prepare...psychological literature. The present study used archival data from a UCLA (University of California Los Angeles ) engineering course

Applying Model Based Systems Engineering to NASA's Space Communications Networks

NASA Technical Reports Server (NTRS)

Bhasin, Kul; Barnes, Patrick; Reinert, Jessica; Golden, Bert

2013-01-01

System engineering practices for complex systems and networks now require that requirement, architecture, and concept of operations product development teams, simultaneously harmonize their activities to provide timely, useful and cost-effective products. When dealing with complex systems of systems, traditional systems engineering methodology quickly falls short of achieving project objectives. This approach is encumbered by the use of a number of disparate hardware and software tools, spreadsheets and documents to grasp the concept of the network design and operation. In case of NASA's space communication networks, since the networks are geographically distributed, and so are its subject matter experts, the team is challenged to create a common language and tools to produce its products. Using Model Based Systems Engineering methods and tools allows for a unified representation of the system in a model that enables a highly related level of detail. To date, Program System Engineering (PSE) team has been able to model each network from their top-level operational activities and system functions down to the atomic level through relational modeling decomposition. These models allow for a better understanding of the relationships between NASA's stakeholders, internal organizations, and impacts to all related entities due to integration and sustainment of existing systems. Understanding the existing systems is essential to accurate and detailed study of integration options being considered. In this paper, we identify the challenges the PSE team faced in its quest to unify complex legacy space communications networks and their operational processes. We describe the initial approaches undertaken and the evolution toward model based system engineering applied to produce Space Communication and Navigation (SCaN) PSE products. We will demonstrate the practice of Model Based System Engineering applied to integrating space communication networks and the summary of its results and impact. We will highlight the insights gained by applying the Model Based System Engineering and provide recommendations for its applications and improvements.

Toolsets Maintain Health of Complex Systems

NASA Technical Reports Server (NTRS)

2010-01-01

First featured in Spinoff 2001, Qualtech Systems Inc. (QSI), of Wethersfield, Connecticut, adapted its Testability, Engineering, and Maintenance System (TEAMS) toolset under Small Business Innovation Research (SBIR) contracts from Ames Research Center to strengthen NASA's systems health management approach for its large, complex, and interconnected systems. Today, six NASA field centers utilize the TEAMS toolset, including TEAMS-Designer, TEAMS-RT, TEAMATE, and TEAMS-RDS. TEAMS is also being used on industrial systems that generate power, carry data, refine chemicals, perform medical functions, and produce semiconductor wafers. QSI finds TEAMS can lower costs by decreasing problems requiring service by 30 to 50 percent.

Towards a Methodology for Managing Competencies in Virtual Teams - A Systemic Approach

NASA Astrophysics Data System (ADS)

Schumacher, Marinita; Stal-Le Cardinal, Julie; Bocquet, Jean-Claude

Virtual instruments and tools are future trends in Engineering which are a response to the growing complexity of engineering tasks, the facility of communication and strong collaborations on the international market. Outsourcing, off-shoring, and the globalization of organisations’ activities have resulted in the formation of virtual product development teams. Individuals who are working in virtual teams must be equipped with diversified competencies that provide a basis for virtual team building. Thanks to the systemic approach of the functional analysis our paper responds to the need of a methodology of competence management to build virtual teams that are active in virtual design projects in the area of New Product Development (NPD).

Team Expo: A State-of-the-Art JSC Advanced Design Team

NASA Technical Reports Server (NTRS)

Tripathi, Abhishek

2001-01-01

In concert with the NASA-wide Intelligent Synthesis Environment Program, the Exploration Office at the Johnson Space Center has assembled an Advanced Design Team. The purpose of this team is two-fold. The first is to identify, use, and develop software applications, tools, and design processes that streamline and enhance a collaborative engineering environment. The second is to use this collaborative engineering environment to produce conceptual, system-level-of-detail designs in a relatively short turnaround time, using a standing team of systems and integration experts. This includes running rapid trade studies on varying mission architectures, as well as producing vehicle and/or subsystem designs. The standing core team is made up of experts from all of the relevant engineering divisions (e.g. Power, Thermal, Structures, etc.) as well as representatives from Risk and Safety, Mission Operations, and Crew Life Sciences among others. The Team works together during 2- hour sessions in the same specially enhanced room to ensure real-time integration/identification of cross-disciplinary issues and solutions. All subsystem designs are collectively reviewed and approved during these same sessions. In addition there is an Information sub-team that captures and formats all data and makes it accessible for use by the following day. The result is Team Expo: an Advanced Design Team that is leading the change from a philosophy of "over the fence" design to one of collaborative engineering that pushes the envelope to achieve the next-generation analysis and design environment.

KSC-2011-7245

NASA Image and Video Library

2011-10-04

CAPE CANAVERAL, Fla. -- NASA managers at NASA's Kennedy Space Center in Florida show off the Florida Project of the Year trophies that the crawlerway system evaluation team received from the American Society of Civil Engineers (ASCE). From left are Michael Benik, director of Center Operations; Pepper Phillips, manager of the 21st Century Ground Systems Program Office; and Russell Romanella, associate director for Engineering and Technical Operations. The Cape Canaveral branch of the ASCE nominated the team for its project, the Crawlerway Evaluation to Support a Heavy-Lift Program. The crawlerway is a 130-foot-wide, specialty-built roadway between Kennedy's Vehicle Assembly Building (VAB), where rockets and spacecraft are prepared for flight, and Launch Pad 39A and 39B. The team's more than two-year evaluation confirmed the crawlerway system would be able to support the weight of moving the agency's future heavy-lift rockets and potential commercial vehicles from the VAB to the launch pads. The award honors the team's outstanding engineering efforts in research, design, construction and management, recognizing the complexity of multi-agency coordination and cost-effective engineering advances. For more information on the American Society of Civil Engineers, visit: http://www.asce.org. Photo credit: NASA/Kim Shiflett

KSC-2011-7246

NASA Image and Video Library

2011-10-04

CAPE CANAVERAL, Fla. -- Members of the crawlerway system evaluation team pose for a group portrait in front of the Headquarters Building at NASA's Kennedy Space Center in Florida. The team received the Florida Project of the Year award from the American Society of Civil Engineers (ASCE). The Cape Canaveral branch of the ASCE nominated the team for its project, the Crawlerway Evaluation to Support a Heavy-Lift Program. The crawlerway is a 130-foot-wide, specialty-built roadway between Kennedy's Vehicle Assembly Building (VAB), where rockets and spacecraft are prepared for flight, and Launch Pad 39A and 39B. The team's more than two-year evaluation confirmed the crawlerway system would be able to support the weight of moving the agency's future heavy-lift rockets and potential commercial vehicles from the VAB to the launch pads. The award honors the team's outstanding engineering efforts in research, design, construction and management, recognizing the complexity of multi-agency coordination and cost-effective engineering advances. For more information on the American Society of Civil Engineers, visit: http://www.asce.org. Photo credit: NASA/Kim Shiflett

Exploring Mission Concepts with the JPL Innovation Foundry A-Team

NASA Technical Reports Server (NTRS)

Ziemer, John K.; Ervin, Joan; Lang, Jared

2013-01-01

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts called the A-Team. The A-Team combines innovative collaborative methods with subject matter expertise and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an A-Team study. Methods are grouped by Concept Maturity Level (CML), from 1 through 3, including idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for each CML are presented, and the key team roles are described from two points of view: innovative methods and technical expertise. A-Team roles for providing innovative methods include the facilitator, study lead, and assistant study lead. A-Team roles for providing technical expertise include the architect, lead systems engineer, and integration engineer. In addition to these key roles, each A-Team study is uniquely staffed to match the study topic and scope including subject matter experts, scientists, technologists, flight and instrument systems engineers, and program managers as needed. Advanced analysis and collaborative engineering tools (e.g. cost, science traceability, mission design, knowledge capture, study and analysis support infrastructure) are also under development for use in A-Team studies and will be discussed briefly. The A-Team facilities provide a constructive environment for innovative ideas from all aspects of mission formulation to eliminate isolated studies and come together early in the development cycle when they can provide the biggest impact. This paper provides an overview of the A-Team, its study processes, roles, methods, tools and facilities.

Aerospace Systems Design in NASA's Collaborative Engineering Environment

NASA Technical Reports Server (NTRS)

Monell, Donald W.; Piland, William M.

2000-01-01

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g., manufacturing and systems operation). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost, risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographical distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across Agency.

A Systematic Review of Developing Team Competencies in Information Systems Education

ERIC Educational Resources Information Center

Figl, Kathrin

2010-01-01

The ability to work effectively in teams has been a key competence for information systems engineers for a long time. Gradually, more attention is being paid to developing this generic competence as part of academic curricula, resulting in two questions: how to best promote team competencies and how to implement team projects successfully. These…

Human Systems Integration Competency Development for Navy Systems Commands

DTIC Science & Technology

2012-09-01

cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences. KSA...cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences...requirements (as required). Fundamental cognizance of Applied Engineering / Psychology relative to knowledge engineering, training, team work, user

KSC-2013-3538

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers from NASA's Kennedy Space Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3544

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers from NASA's Marshall Space Flight Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3539

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers from NASA's Kennedy Space Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3545

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – An engineer from NASA's Marshall Space Flight Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3547

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – An engineer from NASA's Marshall Space Flight Center watches the landing of remote-controlled aircraft. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined a Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

White House Science Fair

NASA Image and Video Library

2014-05-27

Bobak Ferdowsi, a system's engineer at NASA's Jet Propulsion Laboratory, speaks with a member of "invenTeam" at the White House Science Fair. Olivia Van Amsterdam, 16, Katelyn Sweeney, 17, and their team of student engineers from Natick, MA, invented a 120 lb remotely operated vehicle (ROV) that can help search-and-rescue dive teams search for bodies in dangerous, icy waters. The fourth White House Science Fair was held at the White House and included 100 students from more than 30 different states who competed in science, technology, engineering, and math (STEM) competitions. (Photo Credit: NASA/Aubrey Gemignani)

Aerospace Systems Design in NASA's Collaborative Engineering Environment

NASA Technical Reports Server (NTRS)

Monell, Donald W.; Piland, William M.

1999-01-01

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g. manufacturing and systems operations). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographically distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across the Agency.

Aerospace Systems Design in NASA's Collaborative Engineering Environment

NASA Astrophysics Data System (ADS)

Monell, Donald W.; Piland, William M.

2000-07-01

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g., manufacturing and systems operations). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often led to the inability of assessing critical programmatic and technical issues (e.g., cost, risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographically distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across the Agency.

Space Transportation System Liftoff Debris Mitigation Process Overview

NASA Technical Reports Server (NTRS)

Mitchell, Michael; Riley, Christopher

2011-01-01

Liftoff debris is a top risk to the Space Shuttle Vehicle. To manage the Liftoff debris risk, the Space Shuttle Program created a team with in the Propulsion Systems Engineering & Integration Office. The Shutt le Liftoff Debris Team harnesses the Systems Engineering process to i dentify, assess, mitigate, and communicate the Liftoff debris risk. T he Liftoff Debris Team leverages off the technical knowledge and expe rtise of engineering groups across multiple NASA centers to integrate total system solutions. These solutions connect the hardware and ana lyses to identify and characterize debris sources and zones contribut ing to the Liftoff debris risk. The solutions incorporate analyses sp anning: the definition and modeling of natural and induced environmen ts; material characterizations; statistical trending analyses, imager y based trajectory analyses; debris transport analyses, and risk asse ssments. The verification and validation of these analyses are bound by conservative assumptions and anchored by testing and flight data. The Liftoff debris risk mitigation is managed through vigilant collab orative work between the Liftoff Debris Team and Launch Pad Operation s personnel and through the management of requirements, interfaces, r isk documentation, configurations, and technical data. Furthermore, o n day of launch, decision analysis is used to apply the wealth of ana lyses to case specific identified risks. This presentation describes how the Liftoff Debris Team applies Systems Engineering in their proce sses to mitigate risk and improve the safety of the Space Shuttle Veh icle.

Domain-specific languages and diagram customization for a concurrent engineering environment

NASA Astrophysics Data System (ADS)

Cole, B.; Dubos, G.; Banazadeh, P.; Reh, J.; Case, K.; Wang, Y.; Jones, S.; Picha, F.

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 severa- 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.

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

NASA Technical Reports Server (NTRS)

Cole, Bjorn; Dubos, Greg; Banazadeh, Payam; Reh, Jonathan; Case, Kelley; Wang, Yeou-Fang; Jones, Susan; Picha, Frank

2013-01-01

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.

Hydrogen Vent Ground Umbilical Quick Disconnect - Flight Seal Advanced Development

NASA Technical Reports Server (NTRS)

Girard, Doug; Jankowski, Fred; Minich, Mark C.; Yu, Weiping

2012-01-01

This project is a team effort between NASA Engineering (NE) and Team QNA Engineering personnel to provide support for the Umbilical Systems Development project which is funded by Advanced Exploration Systems (AES) and 21st Century Launch Complex. Specifically, this project seeks to develop a new interface between the PPBE baselined Legacy SSP LH2 Vent Arm QD probe and SLS vent seal.

Collaborative engineering and design management for the Hobby-Eberly Telescope tracker upgrade

NASA Astrophysics Data System (ADS)

Mollison, Nicholas T.; Hayes, Richard J.; Good, John M.; Booth, John A.; Savage, Richard D.; Jackson, John R.; Rafal, Marc D.; Beno, Joseph H.

2010-07-01

The engineering and design of systems as complex as the Hobby-Eberly Telescope's* new tracker require that multiple tasks be executed in parallel and overlapping efforts. When the design of individual subsystems is distributed among multiple organizations, teams, and individuals, challenges can arise with respect to managing design productivity and coordinating successful collaborative exchanges. This paper focuses on design management issues and current practices for the tracker design portion of the Hobby-Eberly Telescope Wide Field Upgrade project. The scope of the tracker upgrade requires engineering contributions and input from numerous fields including optics, instrumentation, electromechanics, software controls engineering, and site-operations. Successful system-level integration of tracker subsystems and interfaces is critical to the telescope's ultimate performance in astronomical observation. Software and process controls for design information and workflow management have been implemented to assist the collaborative transfer of tracker design data. The tracker system architecture and selection of subsystem interfaces has also proven to be a determining factor in design task formulation and team communication needs. Interface controls and requirements change controls will be discussed, and critical team interactions are recounted (a group-participation Failure Modes and Effects Analysis [FMEA] is one of special interest). This paper will be of interest to engineers, designers, and managers engaging in multi-disciplinary and parallel engineering projects that require coordination among multiple individuals, teams, and organizations.

Teaching the Next Generation of Scientists and Engineers the NASA Design Process

NASA Technical Reports Server (NTRS)

Caruso, Pamela W.; Benfield, Michael P. J.; Justice, Stefanie H.

2011-01-01

The Integrated Product Team (IPT) program, led by The University of Alabama in Huntsville (UAH), is a multidisciplinary, multi-university, multi-level program whose goal is to provide opportunities for high school and undergraduate scientists and engineers to translate stakeholder needs and requirements into viable engineering design solutions via a distributed multidisciplinary team environment. The current program supports three projects. The core of the program is the two-semester senior design experience where science, engineering, and liberal arts undergraduate students from UAH, the College of Charleston, Southern University at Baton Rouge, and Ecole Suprieure des Techniques Aronautiques et de Construction Automobile (ESTACA) in Paris, France form multidisciplinary competitive teams to develop system concepts of interest to the local aerospace community. External review boards form to provide guidance and feedback throughout the semester and to ultimately choose a winner from the competing teams. The other two projects, the Innovative Student Project for the Increased Recruitment of Engineering and Science Students (InSPIRESS) Level I and Level II focus exclusively on high school students. InSPIRESS Level I allows high schools to develop a payload to be accommodated on the system being developed by senior design experience teams. InSPIRESS Level II provides local high school students first-hand experience in the senior design experience by allowing them to develop a subsystem or component of the UAH-led system over the two semesters. This program provides a model for NASA centers to engage the local community to become more involved in design projects.

ESMD Risk Management Workshop: Systems Engineering and Integration Risks

NASA Technical Reports Server (NTRS)

Thomas, L. Dale

2005-01-01

This report has been developed by the National Aeronautics and Space Administration (NASA) Exploration Systems Mission Directorate (ESMD) Risk Management team in close coordination with the Systems Engineering Team. This document provides a point-in-time, cumulative, summary of key lessons learned derived from the SE RFP Development process. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

NCC: A Multidisciplinary Design/Analysis Tool for Combustion Systems

NASA Technical Reports Server (NTRS)

Liu, Nan-Suey; Quealy, Angela

1999-01-01

A multi-disciplinary design/analysis tool for combustion systems is critical for optimizing the low-emission, high-performance combustor design process. Based on discussions between NASA Lewis Research Center and the jet engine companies, an industry-government team was formed in early 1995 to develop the National Combustion Code (NCC), which is an integrated system of computer codes for the design and analysis of combustion systems. NCC has advanced features that address the need to meet designer's requirements such as "assured accuracy", "fast turnaround", and "acceptable cost". The NCC development team is comprised of Allison Engine Company (Allison), CFD Research Corporation (CFDRC), GE Aircraft Engines (GEAE), NASA Lewis Research Center (LeRC), and Pratt & Whitney (P&W). This development team operates under the guidance of the NCC steering committee. The "unstructured mesh" capability and "parallel computing" are fundamental features of NCC from its inception. The NCC system is composed of a set of "elements" which includes grid generator, main flow solver, turbulence module, turbulence and chemistry interaction module, chemistry module, spray module, radiation heat transfer module, data visualization module, and a post-processor for evaluating engine performance parameters. Each element may have contributions from several team members. Such a multi-source multi-element system needs to be integrated in a way that facilitates inter-module data communication, flexibility in module selection, and ease of integration.

Modular projects and 'mean questions': best practices for advising an International Genetically Engineered Machines team.

PubMed

Tsui, Jennifer; Meyer, Anne S

2016-07-01

In the yearly Internationally Genetically Engineered Machines (iGEM) competition, teams of Bachelor's and Master's students design and build an engineered biological system using DNA technologies. Advising an iGEM team poses unique challenges due to the inherent difficulties of mounting and completing a new biological project from scratch over the course of a single academic year; the challenges in obtaining financial and structural resources for a project that will likely not be fully realized; and conflicts between educational and competition-based goals. This article shares tips and best practices for iGEM team advisors, from two team advisors with very different experiences with the iGEM competition. © FEMS 2016. All rights reserved. For permissions, please e-mail: journals.permissions@oup.com.

Model-Based Systems Engineering in Concurrent Engineering Centers

NASA Technical Reports Server (NTRS)

Iwata, Curtis; Infeld, Samantha; Bracken, Jennifer Medlin; McGuire; McQuirk, Christina; Kisdi, Aron; Murphy, Jonathan; Cole, Bjorn; Zarifian, Pezhman

2015-01-01

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a focused design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

Model-Based Systems Engineering in Concurrent Engineering Centers

NASA Technical Reports Server (NTRS)

Iwata, Curtis; Infeld, Samatha; Bracken, Jennifer Medlin; McGuire, Melissa; McQuirk, Christina; Kisdi, Aron; Murphy, Jonathan; Cole, Bjorn; Zarifian, Pezhman

2015-01-01

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

STS-114 Engine Cut-off Sensor Anomaly Technical Consultation Report

NASA Technical Reports Server (NTRS)

Wilson, Timmy R.; Kichak, Robert A.; Ungar, Eugene K.; Cherney, Robert; Rickman, Steve L.

2009-01-01

The NESC consultation team participated in real-time troubleshooting of the Main Propulsion System (MPS) Engine Cutoff (ECO) sensor system failures during STS-114 launch countdown. The team assisted with External Tank (ET) thermal and ECO Point Sensor Box (PSB) circuit analyses, and made real-time inputs to the Space Shuttle Program (SSP) problem resolution teams. Several long-term recommendations resulted. One recommendation was to conduct cryogenic tests of the ECO sensors to validate, or disprove, the theory that variations in circuit impedance due to cryogenic effects on swaged connections within the sensor were the root cause of STS-114 failures.

IDC Integrated Master Plan.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Clifford, David J.; Harris, James M.

2014-12-01

This is the IDC Re-Engineering Phase 2 project Integrated Master Plan (IMP). The IMP presents the major accomplishments planned over time to re-engineer the IDC system. The IMP and the associate Integrated Master Schedule (IMS) are used for planning, scheduling, executing, and tracking the project technical work efforts. REVISIONS Version Date Author/Team Revision Description Authorized by V1.0 12/2014 IDC Re- engineering Project Team Initial delivery M. Harris

Digital Model-Based Engineering: Expectations, Prerequisites, and Challenges of Infusion

NASA Technical Reports Server (NTRS)

Hale, J. P.; Zimmerman, P.; Kukkala, G.; Guerrero, J.; Kobryn, P.; Puchek, B.; Bisconti, M.; Baldwin, C.; Mulpuri, M.

2017-01-01

Digital model-based engineering (DMbE) is the use of digital artifacts, digital environments, and digital tools in the performance of engineering functions. DMbE is intended to allow an organization to progress from documentation-based engineering methods to digital methods that may provide greater flexibility, agility, and efficiency. The term 'DMbE' was developed as part of an effort by the Model-Based Systems Engineering (MBSE) Infusion Task team to identify what government organizations might expect in the course of moving to or infusing MBSE into their organizations. The Task team was established by the Interagency Working Group on Engineering Complex Systems, an informal collaboration among government systems engineering organizations. This Technical Memorandum (TM) discusses the work of the MBSE Infusion Task team to date. The Task team identified prerequisites, expectations, initial challenges, and recommendations for areas of study to pursue, as well as examples of efforts already in progress. The team identified the following five expectations associated with DMbE infusion, discussed further in this TM: (1) Informed decision making through increased transparency, and greater insight. (2) Enhanced communication. (3) Increased understanding for greater flexibility/adaptability in design. (4) Increased confidence that the capability will perform as expected. (5) Increased efficiency. The team identified the following seven challenges an organization might encounter when looking to infuse DMbE: (1) Assessing value added to the organization. Not all DMbE practices will be applicable to every situation in every organization, and not all implementations will have positive results. (2) Overcoming organizational and cultural hurdles. (3) Adopting contractual practices and technical data management. (4) Redefining configuration management. The DMbE environment changes the range of configuration information to be managed to include performance and design models, database objects, as well as more traditional book-form objects and formats. (5) Developing information technology (IT) infrastructure. Approaches to implementing critical, enabling IT infrastructure capabilities must be flexible, reconfigurable, and updatable. (6) Ensuring security of the single source of truth (7) Potential overreliance on quantitative data over qualitative data. Executable/ computational models and simulations generally incorporate and generate quantitative vice qualitative data. The Task team also developed several recommendations for government, academia, and industry, as discussed in this TM. The Task team recommends continuing beyond this initial work to further develop the means of implementing DMbE and to look for opportunities to collaborate and share best practices.

ADVANCED MANUFACTURING TEAM

NASA Image and Video Library

2016-03-17

KEN COOPER, TEAM LEAD OF MSFC’S ADVANCED MANUFACTURING TEAM, WITH NICKEL ALLOY 718 PARTS FABRICATED USING THE M1 SELECTIVE LASER MELTING SYSTEM. THE M1 MACHINE IS DEDICATED TO BUILDING QUALIFICATION SAMPLES AND HARDWARE DEMONSTRATORS FOR THE RS25 ENGINE PROJECT.

A Genuine TEAM Player

NASA Technical Reports Server (NTRS)

2001-01-01

Qualtech Systems, Inc. developed a complete software system with capabilities of multisignal modeling, diagnostic analysis, run-time diagnostic operations, and intelligent interactive reasoners. Commercially available as the TEAMS (Testability Engineering and Maintenance System) tool set, the software can be used to reveal unanticipated system failures. The TEAMS software package is broken down into four companion tools: TEAMS-RT, TEAMATE, TEAMS-KB, and TEAMS-RDS. TEAMS-RT identifies good, bad, and suspect components in the system in real-time. It reports system health results from onboard tests, and detects and isolates failures within the system, allowing for rapid fault isolation. TEAMATE takes over from where TEAMS-RT left off by intelligently guiding the maintenance technician through the troubleshooting procedure, repair actions, and operational checkout. TEAMS-KB serves as a model management and collection tool. TEAMS-RDS (TEAMS-Remote Diagnostic Server) has the ability to continuously assess a system and isolate any failure in that system or its components, in real time. RDS incorporates TEAMS-RT, TEAMATE, and TEAMS-KB in a large-scale server architecture capable of providing advanced diagnostic and maintenance functions over a network, such as the Internet, with a web browser user interface.

Propulsion Technology Lifecycle Operational Analysis

NASA Technical Reports Server (NTRS)

Robinson, John W.; Rhodes, Russell E.

2010-01-01

The paper presents the results of a focused effort performed by the members of the Space Propulsion Synergy Team (SPST) Functional Requirements Sub-team to develop propulsion data to support Advanced Technology Lifecycle Analysis System (ATLAS). This is a spreadsheet application to analyze the impact of technology decisions at a system-of-systems level. Results are summarized in an Excel workbook we call the Technology Tool Box (TTB). The TTB provides data for technology performance, operations, and programmatic parameters in the form of a library of technical information to support analysis tools and/or models. The lifecycle of technologies can be analyzed from this data and particularly useful for system operations involving long running missions. The propulsion technologies in this paper are listed against Chemical Rocket Engines in a Work Breakdown Structure (WBS) format. The overall effort involved establishing four elements: (1) A general purpose Functional System Breakdown Structure (FSBS). (2) Operational Requirements for Rocket Engines. (3) Technology Metric Values associated with Operating Systems (4) Work Breakdown Structure (WBS) of Chemical Rocket Engines The list of Chemical Rocket Engines identified in the WBS is by no means complete. It is planned to update the TTB with a more complete list of available Chemical Rocket Engines for United States (US) engines and add the Foreign rocket engines to the WBS which are available to NASA and the Aerospace Industry. The Operational Technology Metric Values were derived by the SPST Sub-team in the form of the TTB and establishes a database for users to help evaluate and establish the technology level of each Chemical Rocket Engine in the database. The Technology Metric Values will serve as a guide to help determine which rocket engine to invest technology money in for future development.

The KSC Simulation Team practices for contingencies in Firing Room 1

NASA Technical Reports Server (NTRS)

1998-01-01

In Firing Room 1 at KSC, Shuttle launch team members put the Shuttle system through an integrated simulation. The control room is set up with software used to simulate flight and ground systems in the launch configuration. A Simulation Team, comprised of KSC engineers, introduce 12 or more major problems to prepare the launch team for worst-case scenarios. Such tests and simulations keep the Shuttle launch team sharp and ready for liftoff. The next liftoff is targeted for Oct. 29.

Mars Reconnaissance Orbiter Mission: Systems Engineering Challenges on the Mars Reconnaissance Orbiter Mission

NASA Technical Reports Server (NTRS)

Havens, Glen G.

2007-01-01

MRO project is a system of systems requiring system engineering team to architect, design, integrate, test, and operate these systems at each level of the project. The challenge of system engineering mission objectives into a single mission architecture that can be integrated tested, launched, and operated. Systems engineering must translate high-level requirements into integrated mission design. Systems engineering challenges were overcome utilizing a combination by creative designs built into MRO's flight and ground systems: a) Design of sophisticated spacecraft targeting and data management capabilities b) Establishment of a strong operations team organization; c) Implementation of robust operational processes; and d) Development of strategic ground tools. The MRO system has met the challenge of its driving requirements: a) MRO began its two-year primary science phase on November 7, 2006, and by July 2007, met it minimum requirement to collect 15 Tbits of data after only eight months of operations. Currently we have collected 22 Tbits. b) Based on current performance, mission data return could return 70 Tbits of data by the end of the primary science phase in 2008.

A Simplified Model of Human Alcohol Metabolism That Integrates Biotechnology and Human Health into a Mass Balance Team Project

ERIC Educational Resources Information Center

Yang, Allen H. J.; Dimiduk, Kathryn; Daniel, Susan

2011-01-01

We present a simplified human alcohol metabolism model for a mass balance team project. Students explore aspects of engineering in biotechnology: designing/modeling biological systems, testing the design/model, evaluating new conditions, and exploring cutting-edge "lab-on-a-chip" research. This project highlights chemical engineering's impact on…

Interdisciplinary Team-Teaching Experience for a Computer and Nuclear Energy Course for Electrical and Computer Engineering Students

ERIC Educational Resources Information Center

Kim, Charles; Jackson, Deborah; Keiller, Peter

2016-01-01

A new, interdisciplinary, team-taught course has been designed to educate students in Electrical and Computer Engineering (ECE) so that they can respond to global and urgent issues concerning computer control systems in nuclear power plants. This paper discusses our experience and assessment of the interdisciplinary computer and nuclear energy…

Systems Engineering and Integration for Technology Programs

NASA Technical Reports Server (NTRS)

Kennedy, Kruss J.

2006-01-01

The Architecture, Habitability & Integration group (AH&I) is a system engineering and integration test team within the NASA Crew and Thermal Systems Division (CTSD) at Johnson Space Center. AH&I identifies and resolves system-level integration issues within the research and technology development community. The timely resolution of these integration issues is fundamental to the development of human system requirements and exploration capability. The integration of the many individual components necessary to construct an artificial environment is difficult. The necessary interactions between individual components and systems must be approached in a piece-wise fashion to achieve repeatable results. A formal systems engineering (SE) approach to define, develop, and integrate quality systems within the life support community has been developed. This approach will allow a Research & Technology Program to systematically approach the development, management, and quality of technology deliverables to the various exploration missions. A tiered system engineering structure has been proposed to implement best systems engineering practices across all development levels from basic research to working assemblies. These practices will be implemented through a management plan across all applicable programs, projects, elements and teams. While many of the engineering practices are common to other industries, the implementation is specific to technology development. An accounting of the systems engineering management philosophy will be discussed and the associated programmatic processes will be presented.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

The U.S. Army Corps of Engineers (USACE) in Stability Operations

DTIC Science & Technology

2008-12-12

advance (FEST-A) or forward engineer support team-main (FEST- M ) is another vital asset that USACE can provide in stability operations. The FEST- M ...engineer units and if deployed with a FEST- M will fall under that element. FEST are small teams with specialized expertise based on where they are...in Afghanistan and set the conditions for the creation of an Afghan political system ( Donini et al., 46). Major reconstruction projects were not

Perceptions of Engineers Regarding Successful Engineering Team Design

NASA Technical Reports Server (NTRS)

Nowaczyk, Ronald H.

1998-01-01

The perceptions of engineers and scientists at NASA Langley Research Center toward engineering design teams were evaluated. A sample of 49 engineers and scientists rated 60 team behaviors in terms of their relative importance for team success. They also completed a profile of their own perceptions of their strengths and weaknesses as team members. Behaviors related to team success are discussed in terms of those involving the organizational culture and commitment to the team and those dealing with internal team dynamics. The latter behaviors focused on team issues occurring during the early stages of a team's existence. They included the level and extent of debate and discussion regarding methods for completing the team task and the efficient use of team time to explore and discuss methodologies critical to the problem. The discussion includes a comparison of engineering teams with the prototypical business team portrayed in the literature.

KSC-98pc970

NASA Image and Video Library

1998-08-20

In Firing Room 1 at KSC, Shuttle launch team members put the Shuttle system through an integrated simulation. The control room is set up with software used to simulate flight and ground systems in the launch configuration. A Simulation Team, comprised of KSC engineers, introduce 12 or more major problems to prepare the launch team for worst-case scenarios. Such tests and simulations keep the Shuttle launch team sharp and ready for liftoff. The next liftoff is targeted for Oct. 29

Model collaboration: university library system and rehabilitation research team to advance telepractice knowledge.

PubMed

Deliyannides, Timothy S; Gabler, Vanessa

2012-01-01

This Publisher's Report describes the collaboration between a university library system's scholarly communication and publishing office and a federally funded research team, the Rehabilitation Engineering Research Center (RERC) on Telerehabilitation. This novel interdisciplinary collaboration engages librarians, information technologists, publishing professionals, clinicians, policy experts, and engineers and has produced a new Open Access journal, International Journal of Telerehabilitation, and a developing, interactive web-based product dedicated to disseminating information about telerehabilitation. Readership statistics are presented for March 1, 2011 - February 29, 2012.

7 CFR Appendix C to Subpart B of... - Technical Report for Hydropower Projects

Code of Federal Regulations, 2013 CFR

2013-01-01

...,000 require the services of a licensed professional engineer (PE) or team of PEs. Depending on the... services of a licensed PE or a team of licensed PEs may be required for smaller projects. (a) Qualifications of project team. The hydropower project team should consist of a system designer, a project...

7 CFR Appendix C to Subpart B of... - Technical Report for Hydropower Projects

Code of Federal Regulations, 2014 CFR

2014-01-01

...,000 require the services of a licensed professional engineer (PE) or team of PEs. Depending on the... services of a licensed PE or a team of licensed PEs may be required for smaller projects. (a) Qualifications of project team. The hydropower project team should consist of a system designer, a project...

7 CFR Appendix C to Subpart B of... - Technical Report for Hydropower Projects

Code of Federal Regulations, 2012 CFR

2012-01-01

...,000 require the services of a licensed professional engineer (PE) or team of PEs. Depending on the... services of a licensed PE or a team of licensed PEs may be required for smaller projects. (a) Qualifications of project team. The hydropower project team should consist of a system designer, a project...

A Status Report on the Parachute Development for NASA's Next Manned Spacecraft

NASA Technical Reports Server (NTRS)

Sinclair, Robert

2008-01-01

NASA has determined that the parachute portion of the Landing System for the Crew Exploration Vehicle (CEV) will be Government Furnished Equipment (GFE). The Earth Landing System has been designated CEV Parachute Assembly System (CPAS). Thus a program team was developed consisting of NASA Johnson Space Center (JSC) and Jacobs Engineering through their Engineering and Science Contract Group (ESCG). Following a rigorous competitive phase, Airborne Systems North America was selected to provide the parachute design, testing and manufacturing role to support this team. The development program has begun with some early flight testing of a Generation 1 parachute system. Future testing will continue to refine the design and complete a qualification phase prior to manned flight of the spacecraft. The program team will also support early spacecraft system testing, including a Pad Abort Flight Test in the Fall of 2008

KSC-2013-3534

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers fine-tune a remote-controlled helicopter before it takes off. The helicopter is equipped with a unique set of sensors and software and was assembled by a team of engineers from NASA's Johnson Space Center for a competition at the agency's Kennedy Space Center. Teams from Johnson, Kennedy and Marshall Space Flight Center competed in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

NASA systems engineering handbook

NASA Astrophysics Data System (ADS)

Shishko, Robert; Aster, Robert; Chamberlain, Robert G.; McDuffee, Patrick; Pieniazek, Les; Rowell, Tom; Bain, Beth; Cox, Renee I.; Mooz, Harold; Polaski, Lou

1995-06-01

This handbook brings the fundamental concepts and techniques of systems engineering to NASA personnel in a way that recognizes the nature of NASA systems and environment. It is intended to accompany formal NASA training courses on systems engineering and project management when appropriate, and is designed to be a top-level overview. The concepts were drawn from NASA field center handbooks, NMI's/NHB's, the work of the NASA-wide Systems Engineering Working Group and the Systems Engineering Process Improvement Task team, several non-NASA textbooks and guides, and material from independent systems engineering courses taught to NASA personnel. Five core chapters cover systems engineering fundamentals, the NASA Project Cycle, management issues in systems engineering, systems analysis and modeling, and specialty engineering integration. It is not intended as a directive.

Modular Simulator System (MSS). System/Segment Specification for the Generic MSS - System Integration. Volume 1

DTIC Science & Technology

1993-08-20

UNLIMITED. SYSTEMS ENGINEERING DIVISION AERONAUTICAL SYSTEMS CENTER AIR FORCE MATERIEL COMMAND WRIGHT PATTERSON AFB OH 45433-7126 YOITCE When Government...BASINGER Progatl anager Team Leader Special Programs Divsion Special Programs Division JAMES J. O’CONNELL Chief, Systems Engineering Division Training...ADDRESS(ES) 10. SPONSORING/ MONITORING AGENCY REPORT NUMBER Aeronautical Systems Center Systems Engineering Division ASC-TR-94-50 10 Bldg 11 2240 B St

Extraterrestrial surface propulsion systems

NASA Astrophysics Data System (ADS)

Ash, Robert L.; Blackstock, Dexter L.; Barnhouse, K.; Charalambous, Z.; Coats, J.; Danagan, J.; Davis, T.; Dickens, J.; Harris, P.; Horner, G.

Lunar traction systems, Mars oxygen production, and Mars methane engine operation were the three topics studied during 1992. An elastic loop track system for lunar construction operations was redesigned and is being tested. A great deal of work on simulating the lunar environment to facilitate traction testing has been reported. Operation of an oxygen processor under vacuum conditions has been the focus of another design team. They have redesigned the processor facility. This included improved seals and heat shields. Assuming methane and oxygen can be produced from surface resources on Mars, a third design team has addressed the problem of using Mars atmospheric carbon dioxide to control combustion temperatures in an internal combustion engine. That team has identified appropriate tests and instrumentation. They have reported on the test rig that they designed and the computer-based system for acquiring data.

Extraterrestrial surface propulsion systems

NASA Technical Reports Server (NTRS)

Ash, Robert L.; Blackstock, Dexter L.; Barnhouse, K.; Charalambous, Z.; Coats, J.; Danagan, J.; Davis, T.; Dickens, J.; Harris, P.; Horner, G.

1992-01-01

Lunar traction systems, Mars oxygen production, and Mars methane engine operation were the three topics studied during 1992. An elastic loop track system for lunar construction operations was redesigned and is being tested. A great deal of work on simulating the lunar environment to facilitate traction testing has been reported. Operation of an oxygen processor under vacuum conditions has been the focus of another design team. They have redesigned the processor facility. This included improved seals and heat shields. Assuming methane and oxygen can be produced from surface resources on Mars, a third design team has addressed the problem of using Mars atmospheric carbon dioxide to control combustion temperatures in an internal combustion engine. That team has identified appropriate tests and instrumentation. They have reported on the test rig that they designed and the computer-based system for acquiring data.

KSC-98pc969

NASA Image and Video Library

1998-08-19

KENNEDY SPACE CENTER, FLA. -- In Firing Room 1 at KSC, Shuttle launch team members put the Shuttle system through an integrated simulation. The control room is set up with software used to simulate flight and ground systems in the launch configuration. A Simulation Team, comprisING KSC engineers, introduce 12 or more major problems to prepare the launch team for worst-case scenarios. Such tests and simulations keep the Shuttle launch team sharp and ready for liftoff. The next liftoff is targeted for Oct. 29.

KSC-98pc971

NASA Image and Video Library

1998-08-20

KENNEDY SPACE CENTER, FLA. -- In Firing Room 1 at KSC, Shuttle launch team members put the Shuttle system through an integrated simulation. The control room is set up with software used to simulate flight and ground systems in the launch configuration. A Simulation Team, comprising KSC engineers, introduce 12 or more major problems to prepare the launch team for worst-case scenarios. Such tests and simulations keep the Shuttle launch team sharp and ready for liftoff. The next liftoff is targeted for Oct. 29

Systems Engineering Models and Tools | Wind | NREL

Science.gov Websites

(tm)) that provides wind turbine and plant engineering and cost models for holistic system analysis turbine/component models and wind plant analysis models that the systems engineering team produces. If you integrated modeling of wind turbines and plants. It provides guidance for overall wind turbine and plant

76 FR 10403 - Hewlett Packard (HP), Global Product Development, Engineering Workstation Refresh Team, Working...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-02-24

...), Global Product Development, Engineering Workstation Refresh Team, Working On-Site at General Motors... groups: The Non-Information Technology Business Development Team, the Engineering Application Support Team, and the Engineering Workstation Refresh Team. On February 2, 2011, the Department issued an...

System Engineering Paper

NASA Technical Reports Server (NTRS)

Heise, James; Hull, Bethanne J.; Bauer, Jonathan; Beougher, Nathan G.; Boe, Caleb; Canahui, Ricardo; Charles, John P.; Cooper, Zachary Davis Job; DeShaw, Mark A.; Fontanella, Luan Gasparetto;

Testing for the J-2X Upper Stage Engine

NASA Technical Reports Server (NTRS)

Buzzell, James C.

2010-01-01

NASA selected the J-2X Upper Stage Engine in 2006 to power the upper stages of the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Based on the proven Saturn J-2 engine, this new engine will provide 294,000 pounds of thrust and a specific impulse of 448 seconds, making it the most efficient gas generator cycle engine in history. The engine's guiding philosophy emerged from the Exploration Systems Architecture Study (ESAS) in 2005. Goals established then called for vehicles and components based, where feasible, on proven hardware from the Space Shuttle, commercial, and other programs, to perform the mission and provide an order of magnitude greater safety. Since that time, the team has made unprecedented progress. Ahead of the other elements of the Constellation Program architecture, the team has progressed through System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of February 2010, more than 100,000 development engine parts have been ordered and more than 18,000 delivered. Approximately 1,300 of more than 1,600 engine drawings were released for manufacturing. A major factor in the J-2X development approach to this point is testing operations of heritage J-2 engine hardware and new J-2X components to understand heritage performance, validate computer modeling of development components, mitigate risk early in development, and inform design trades. This testing has been performed both by NASA and its J-2X prime contractor, Pratt & Whitney Rocketdyne (PWR). This body of work increases the likelihood of success as the team prepares for testing the J-2X powerpack and first development engine in calendar 2011. This paper will provide highlights of J-2X testing operations, engine test facilities, development hardware, and plans.

System engineering of the Atacama Large Millimeter/submillimeter Array

NASA Astrophysics Data System (ADS)

Bhatia, Ravinder; Marti, Javier; Sugimoto, Masahiro; Sramek, Richard; Miccolis, Maurizio; Morita, Koh-Ichiro; Arancibia, Demián.; Araya, Andrea; Asayama, Shin'ichiro; Barkats, Denis; Brito, Rodrigo; Brundage, William; Grammer, Wes; Haupt, Christoph; Kurlandczyk, Herve; Mizuno, Norikazu; Napier, Peter; Pizarro, Eduardo; Saini, Kamaljeet; Stahlman, Gretchen; Verzichelli, Gianluca; Whyborn, Nick; Yagoubov, Pavel

2012-09-01

The Atacama Large Millimeter/submillimeter Array (ALMA) will be composed of 66 high precision antennae located at 5000 meters altitude in northern Chile. This paper will present the methodology, tools and processes adopted to system engineer a project of high technical complexity, by system engineering teams that are remotely located and from different cultures, and in accordance with a demanding schedule and within tight financial constraints. The technical and organizational complexity of ALMA requires a disciplined approach to the definition, implementation and verification of the ALMA requirements. During the development phase, System Engineering chairs all technical reviews and facilitates the resolution of technical conflicts. We have developed analysis tools to analyze the system performance, incorporating key parameters that contribute to the ultimate performance, and are modeled using best estimates and/or measured values obtained during test campaigns. Strict tracking and control of the technical budgets ensures that the different parts of the system can operate together as a whole within ALMA boundary conditions. System Engineering is responsible for acceptances of the thousands of hardware items delivered to Chile, and also supports the software acceptance process. In addition, System Engineering leads the troubleshooting efforts during testing phases of the construction project. Finally, the team is conducting System level verification and diagnostics activities to assess the overall performance of the observatory. This paper will also share lessons learned from these system engineering and verification approaches.

NASA Systems Engineering Handbook

NASA Technical Reports Server (NTRS)

Shishko, Robert; Aster, Robert; Chamberlain, Robert G.; Mcduffee, Patrick; Pieniazek, Les; Rowell, Tom; Bain, Beth; Cox, Renee I.; Mooz, Harold; Polaski, Lou

1995-01-01

This handbook brings the fundamental concepts and techniques of systems engineering to NASA personnel in a way that recognizes the nature of NASA systems and environment. It is intended to accompany formal NASA training courses on systems engineering and project management when appropriate, and is designed to be a top-level overview. The concepts were drawn from NASA field center handbooks, NMI's/NHB's, the work of the NASA-wide Systems Engineering Working Group and the Systems Engineering Process Improvement Task team, several non-NASA textbooks and guides, and material from independent systems engineering courses taught to NASA personnel. Five core chapters cover systems engineering fundamentals, the NASA Project Cycle, management issues in systems engineering, systems analysis and modeling, and specialty engineering integration. It is not intended as a directive. Superseded by: NASA/SP-2007-6105 Rev 1 (20080008301).

Concurrent Mission and Systems Design at NASA Glenn Research Center: The Origins of the COMPASS Team

NASA Technical Reports Server (NTRS)

McGuire, Melissa L.; Oleson, Steven R.; Sarver-Verhey, Timothy R.

2012-01-01

Established at the NASA Glenn Research Center (GRC) in 2006 to meet the need for rapid mission analysis and multi-disciplinary systems design for in-space and human missions, the Collaborative Modeling for Parametric Assessment of Space Systems (COMPASS) team is a multidisciplinary, concurrent engineering group whose primary purpose is to perform integrated systems analysis, but it is also capable of designing any system that involves one or more of the disciplines present in the team. The authors were involved in the development of the COMPASS team and its design process, and are continuously making refinements and enhancements. The team was unofficially started in the early 2000s as part of the distributed team known as Team JIMO (Jupiter Icy Moons Orbiter) in support of the multi-center collaborative JIMO spacecraft design during Project Prometheus. This paper documents the origins of a concurrent mission and systems design team at GRC and how it evolved into the COMPASS team, including defining the process, gathering the team and tools, building the facility, and performing studies.

Principles of Rapid Acquisition and Systems Engineering

DTIC Science & Technology

2012-06-14

Systems Engineering Research Council ( SERC ) research team interviewed over 30 organizations from across the DoD which focus on less traditional...enthusiasm • Lt Col John Elshaw, for his guidance on our statistical analysis • Our sponsors, the SERC , SAF/AQR, and the AF Center for Systems...experienced staff of 20 – 50 people” (Defense Science Board, 2011) Research Focus The Systems Engineering Research Center ( SERC ) has been charged with

Designing, Implementing and Maintaining a First Year Project Course in Electrical Engineering

ERIC Educational Resources Information Center

Lillieskold, J.; Ostlund, S.

2008-01-01

Being a modern electrical engineer does not only require state of the art skills in areas such as transfer and processing of information, electronics, systems engineering, and biomedical electrical engineering; it also requires generic engineering skills such as oral and written communication, team building, interpersonal skills, and the ability…

Software Users Manual (SUM): Extended Testability Analysis (ETA) Tool

NASA Technical Reports Server (NTRS)

Maul, William A.; Fulton, Christopher E.

2011-01-01

This software user manual describes the implementation and use the Extended Testability Analysis (ETA) Tool. The ETA Tool is a software program that augments the analysis and reporting capabilities of a commercial-off-the-shelf (COTS) testability analysis software package called the Testability Engineering And Maintenance System (TEAMS) Designer. An initial diagnostic assessment is performed by the TEAMS Designer software using a qualitative, directed-graph model of the system being analyzed. The ETA Tool utilizes system design information captured within the diagnostic model and testability analysis output from the TEAMS Designer software to create a series of six reports for various system engineering needs. The ETA Tool allows the user to perform additional studies on the testability analysis results by determining the detection sensitivity to the loss of certain sensors or tests. The ETA Tool was developed to support design and development of the NASA Ares I Crew Launch Vehicle. The diagnostic analysis provided by the ETA Tool was proven to be valuable system engineering output that provided consistency in the verification of system engineering requirements. This software user manual provides a description of each output report generated by the ETA Tool. The manual also describes the example diagnostic model and supporting documentation - also provided with the ETA Tool software release package - that were used to generate the reports presented in the manual

Recipe for Success: Digital Viewables

NASA Technical Reports Server (NTRS)

LaPha, Steven; Gaydos, Frank

2014-01-01

The Engineering Services Contract (ESC) and Information Management Communication Support contract (IMCS) at Kennedy Space Center (KSC) provide services to NASA in respect to flight and ground systems design and development. These groups provides the necessary tools, aid, and best practice methodologies required for efficient, optimized design and process development. The team is responsible for configuring and implementing systems, software, along with training, documentation, and administering standards. The team supports over 200 engineers and design specialists with the use of Windchill, Creo Parametric, NX, AutoCAD, and a variety of other design and analysis tools.

NASA Planning for Orion Multi-Purpose Crew Vehicle Ground Operations

NASA Technical Reports Server (NTRS)

Letchworth, Gary; Schlierf, Roland

2011-01-01

The NASA Orion Ground Processing Team was originally formed by the Kennedy Space Center (KSC) Constellation (Cx) Project Office's Orion Division to define, refine and mature pre-launch and post-landing ground operations for the Orion human spacecraft. The multidisciplined KSC Orion team consisted of KSC civil servant, SAIC, Productivity Apex, Inc. and Boeing-CAPPS engineers, project managers and safety engineers, as well as engineers from Constellation's Orion Project and Lockheed Martin Orion Prime contractor. The team evaluated the Orion design configurations as the spacecraft concept matured between Systems Design Review (SDR), Systems Requirement Review (SRR) and Preliminary Design Review (PDR). The team functionally decomposed prelaunch and post-landing steps at three levels' of detail, or tiers, beginning with functional flow block diagrams (FFBDs). The third tier FFBDs were used to build logic networks and nominal timelines. Orion ground support equipment (GSE) was identified and mapped to each step. This information was subsequently used in developing lower level operations steps in a Ground Operations Planning Document PDR product. Subject matter experts for each spacecraft and GSE subsystem were used to define 5th - 95th percentile processing times for each FFBD step, using the Delphi Method. Discrete event simulations used this information and the logic network to provide processing timeline confidence intervals for launch rate assessments. The team also used the capabilities of the KSC Visualization Lab, the FFBDs and knowledge of the spacecraft, GSE and facilities to build visualizations of Orion pre-launch and postlanding processing at KSC. Visualizations were a powerful tool for communicating planned operations within the KSC community (i.e., Ground Systems design team), and externally to the Orion Project, Lockheed Martin spacecraft designers and other Constellation Program stakeholders during the SRR to PDR timeframe. Other operations planning tools included Kaizen/Lean events, mockups and human factors analysis. The majority of products developed by this team are applicable as KSC prepares 21st Century Ground Systems for the Orion Multi-Purpose Crew Vehicle and Space Launch System.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Factors Related to Successful Engineering Team Design

NASA Technical Reports Server (NTRS)

Nowaczyk, Ronald H.; Zang, Thomas A.

1998-01-01

The perceptions of a sample of 49 engineers and scientists from NASA Langley Research Center toward engineering design teams were evaluated. The respondents rated 60 team behaviors in terms of their relative importance for team success. They also completed a profile of their own perceptions of their strengths and weaknesses as team members. Behaviors related to team success are discussed in terms of those involving the organizational culture and commitment to the team and those dealing with internal team dynamics. The latter behaviors included the level and extent of debate and discussion regarding methods for completing the team task and the efficient use of team time to explore and discuss methodologies critical to the problem. Successful engineering teams may find their greatest challenges occurring during the early stages of their existence. In contrast to the prototypical business team, members on an engineering design share expertise and knowledge which allows them to deal with task issues sooner. However, discipline differences among team members can lead to conflicts regarding the best method or approach to solving the engineering problem.

Consequences of Team Charter Quality: Teamwork Mental Model Similarity and Team Viability in Engineering Design Student Teams

ERIC Educational Resources Information Center

Conway Hughston, Veronica

2014-01-01

Since 1996 ABET has mandated that undergraduate engineering degree granting institutions focus on learning outcomes such as professional skills (i.e. solving unstructured problems and working in teams). As a result, engineering curricula were restructured to include team based learning--including team charters. Team charters were diffused into…

CASIS Fact Sheet: Hardware and Facilities

NASA Technical Reports Server (NTRS)

Solomon, Michael R.; Romero, Vergel

2016-01-01

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS

KSC-2013-4342

NASA Image and Video Library

2013-12-11

CAPE CANAVERAL, Fla. -- At NASA's Kennedy Space Center in Florida, from the left, Leandro James, rocket avionics lead, Gary Dahlke, high powered rocket subject matter expert, and Julio Najarro of Mechanical Systems make final adjustments to a small rocket prior to launch as part of Rocket University. The launch will test systems designed by the student engineers. As part of Rocket University, the engineers are given an opportunity to work a fast-track project to develop skills in developing spacecraft systems of the future. As NASA plans for future spaceflight programs to low-Earth orbit and beyond, teams of engineers at Kennedy are gaining experience in designing and flying launch vehicle systems on a small scale. Four teams of five to eight members from Kennedy are designing rockets complete with avionics and recovery systems. Launch operations require coordination with federal agencies, just as they would with rockets launched in support of a NASA mission. Photo credit: NASA/Jim Grossmann

KSC-2013-4343

NASA Image and Video Library

2013-12-11

CAPE CANAVERAL, Fla. -- At NASA's Kennedy Space Center in Florida, from the left, Leandro James, rocket avionics lead, and Julio Najarro of Mechanical Systems make final adjustments to a small rocket prior to launch as part of Rocket University. The launch will test systems designed by the student engineers. As part of Rocket University, the engineers are given an opportunity to work a fast-track project to develop skills in developing spacecraft systems of the future. As NASA plans for future spaceflight programs to low-Earth orbit and beyond, teams of engineers at Kennedy are gaining experience in designing and flying launch vehicle systems on a small scale. Four teams of five to eight members from Kennedy are designing rockets complete with avionics and recovery systems. Launch operations require coordination with federal agencies, just as they would with rockets launched in support of a NASA mission. Photo credit: NASA/Jim Grossmann

Using SFOC to fly the Magellan Venus mapping mission

NASA Technical Reports Server (NTRS)

Bucher, Allen W.; Leonard, Robert E., Jr.; Short, Owen G.

1993-01-01

Traditionally, spacecraft flight operations at the Jet Propulsion Laboratory (JPL) have been performed by teams of spacecraft experts utilizing ground software designed specifically for the current mission. The Jet Propulsion Laboratory set out to reduce the cost of spacecraft mission operations by designing ground data processing software that could be used by multiple spacecraft missions, either sequentially or concurrently. The Space Flight Operations Center (SFOC) System was developed to provide the ground data system capabilities needed to monitor several spacecraft simultaneously and provide enough flexibility to meet the specific needs of individual projects. The Magellan Spacecraft Team utilizes the SFOC hardware and software designed for engineering telemetry analysis, both real-time and non-real-time. The flexibility of the SFOC System has allowed the spacecraft team to integrate their own tools with SFOC tools to perform the tasks required to operate a spacecraft mission. This paper describes how the Magellan Spacecraft Team is utilizing the SFOC System in conjunction with their own software tools to perform the required tasks of spacecraft event monitoring as well as engineering data analysis and trending.

Customizing the JPL Multimission Ground Data System: Lessons learned

NASA Technical Reports Server (NTRS)

Murphy, Susan C.; Louie, John J.; Guerrero, Ana Maria; Hurley, Daniel; Flora-Adams, Dana

1994-01-01

The Multimission Ground Data System (MGDS) at NASA's Jet Propulsion Laboratory has brought improvements and new technologies to mission operations. It was designed as a generic data system to meet the needs of multiple missions and avoid re-inventing capabilities for each new mission and thus reduce costs. It is based on adaptable tools that can be customized to support different missions and operations scenarios. The MGDS is based on a distributed client/server architecture, with powerful Unix workstations, incorporating standards and open system architectures. The distributed architecture allows remote operations and user science data exchange, while also providing capabilities for centralized ground system monitor and control. The MGDS has proved its capabilities in supporting multiple large-class missions simultaneously, including the Voyager, Galileo, Magellan, Ulysses, and Mars Observer missions. The Operations Engineering Lab (OEL) at JPL has been leading Customer Adaptation Training (CAT) teams for adapting and customizing MGDS for the various operations and engineering teams. These CAT teams have typically consisted of only a few engineers who are familiar with operations and with the MGDS software and architecture. Our experience has provided a unique opportunity to work directly with the spacecraft and instrument operations teams and understand their requirements and how the MGDS can be adapted and customized to minimize their operations costs. As part of this work, we have developed workstation configurations, automation tools, and integrated user interfaces at minimal cost that have significantly improved productivity. We have also proved that these customized data systems are most successful if they are focused on the people and the tasks they perform and if they are based upon user confidence in the development team resulting from daily interactions. This paper will describe lessons learned in adapting JPL's MGDS to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team of a handful of engineers flying the Galileo Spacecraft flight system model.

Teaching Engineering Students Team Work

NASA Technical Reports Server (NTRS)

Levi, Daniel

1998-01-01

The purpose of this manual is to provide professor's in engineering classes which the background necessary to use student team projects effectively. This manual describes some of the characteristics of student teams and how to use them in class. It provides a set of class activities and films which can be used to introduce and support student teams. Finally, a set of teaching modules used in freshmen, sophomore, and senior aeronautical engineering classes are presented. This manual was developed as part of a NASA sponsored project to improve the undergraduate education of aeronautical engineers. The project has helped to purchase a set of team work films which can be checked out from Cal Poly's Learning Resources Center in the Kennedy Library. Research for this project has included literature reviews on team work and cooperative learning; interviews, observations, and surveys of Cal Poly students from Industrial and Manufacturing Engineering, Aeronautical Engineering and Psychology; participation in the Aeronautical Engineering senior design lab; and interviews with engineering faculty. In addition to this faculty manual, there is a student team work manual which has been designed to help engineering students work better in teams.

KSC-2013-3537

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled helicopter with a unique set of sensors and software assembled by a team of engineers from NASA's Johnson Space Center flies in a competition at the agency's Kennedy Space Center. Teams from Johnson, Kennedy and Marshall Space Flight Center competed in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3536

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled helicopter with a unique set of sensors and software assembled by a team of engineers from NASA's Johnson Space Center flies in a competition at the agency's Kennedy Space Center. Teams from Johnson, Kennedy and Marshall Space Flight Center competed in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

The Systems and Global Engineering Project

ERIC Educational Resources Information Center

Harms, Henry; Janosz, David A., Jr.; Maietta, Steve

2010-01-01

This article describes the Systems and Global Engineering (SAGE) Project in which students collaborate with others from around the world to model solutions to some of today's most significant global problems. Stevens Institute of Technology and the New Jersey Technology Education Association (NJTEA) have teamed up to develop innovative…

Hubble Space Telescope on-line telemetry archive for monitoring scientific instruments

NASA Astrophysics Data System (ADS)

Miebach, Manfred P.

2002-12-01

A major milestone in an effort to update the aging Hubble Space Telescope (HST) ground system was completed when HST operations were switched to a new ground system, a project called "Vision 2000 Control Center System CCS)", at the time of the third Servicing Mission in December 1999. A major CCS subsystem is the Space Telescope Engineering Data Store, the design of which is based on modern Data Warehousing technology. In fact, the Data Warehouse (DW) as implemented in the CCS Ground System that operates and monitors the Hubble Space Telescope represents, the first use of a commercial Data Warehouse to manage engineering data. By the end of February 2002, the process of populating the Data Warehouse with HST historical telemetry data had been completed, providing access to HST engineering data for a period of over 12 years with a current data volume of 2.8 Terabytes. This paper describes hands-on experience from an end user perspective, using the CCS system capabilities, including the Data Warehouse as an HST engineering telemetry archive. The Engineering Team at the Space Telescope Science Institute is using HST telemetry extensively for monitoring the Scientific Instruments, in particular for · Spacecraft anomaly resolutions · Scientific Instrument trending · Improvements of Instrument operational efficiency The overall idea is to maximize science output of the space observatory. Furthermore, the CCS provides a powerful feature to build, save, and recall real-time display pages customized to specific subsystems and operational scenarios. Engineering teams are using the real-time monitoring capabilities intensively during Servicing Missions and real time commanding to handle anomaly situations, while the Flight Operations Team (FOT) monitors the spacecraft around the clock.

Multi-Organization Multi-Discipline Effort Developing a Mitigation Concept for Planetary Defense

NASA Technical Reports Server (NTRS)

Leung, Ronald Y.; Barbee, Brent W.; Seery, Bernard D.; Bambacus, Myra; Finewood, Lee; Greenaugh, Kevin C.; Lewis, Anthony; Dearborn, David; Miller, Paul L.; Weaver, Robert P.;

Medical Engineering and Microneurosurgery: Application and Future.

PubMed

Morita, Akio; Sora, Shigeo; Nakatomi, Hirofumi; Harada, Kanako; Sugita, Naohiko; Saito, Nobuhito; Mitsuishi, Mamoru

2016-10-15

Robotics and medical engineering can convert traditional surgery into digital and scientific procedures. Here, we describe our work to develop microsurgical robotic systems and apply engineering technology to assess microsurgical skills. With the collaboration of neurosurgeons and an engineering team, we have developed two types of microsurgical robotic systems. The first, the deep surgical systems, enable delicate surgical procedures such as vessel suturing in a deep and narrow space. The second type allows for super-fine surgical procedures such as anastomosing artificial vessels of 0.3 mm in diameter. Both systems are constructed with master and slave manipulator robots connected to local area networks. Robotic systems allowed for secure and accurate procedures in a deep surgical field. In cadaveric models, these systems showed a good potential of being useful in actual human surgeries, but mechanical refinements in thickness and durability are necessary for them to be established as clinical systems. The super-fine robotic system made the very intricate surgery possible and will be applied in clinical trials. Another trial included the digitization of surgical technique and scientific analysis of surgical skills. Robotic and human hand motions were analyzed in numerical fashion as we tried to define surgical skillfulness in a digital format. Engineered skill assessment is also feasible and should be useful for microsurgical training. Robotics and medical engineering should bring science into the surgical field and training of surgeons. Active collaboration between medical and engineering teams and academic and industry groups is mandatory to establish such medical systems to improve patient care.

Medical Engineering and Microneurosurgery: Application and Future

PubMed Central

MORITA, Akio; SORA, Shigeo; NAKATOMI, Hirofumi; HARADA, Kanako; SUGITA, Naohiko; SAITO, Nobuhito; MITSUISHI, Mamoru

2016-01-01

Robotics and medical engineering can convert traditional surgery into digital and scientific procedures. Here, we describe our work to develop microsurgical robotic systems and apply engineering technology to assess microsurgical skills. With the collaboration of neurosurgeons and an engineering team, we have developed two types of microsurgical robotic systems. The first, the deep surgical systems, enable delicate surgical procedures such as vessel suturing in a deep and narrow space. The second type allows for super-fine surgical procedures such as anastomosing artificial vessels of 0.3 mm in diameter. Both systems are constructed with master and slave manipulator robots connected to local area networks. Robotic systems allowed for secure and accurate procedures in a deep surgical field. In cadaveric models, these systems showed a good potential of being useful in actual human surgeries, but mechanical refinements in thickness and durability are necessary for them to be established as clinical systems. The super-fine robotic system made the very intricate surgery possible and will be applied in clinical trials. Another trial included the digitization of surgical technique and scientific analysis of surgical skills. Robotic and human hand motions were analyzed in numerical fashion as we tried to define surgical skillfulness in a digital format. Engineered skill assessment is also feasible and should be useful for microsurgical training. Robotics and medical engineering should bring science into the surgical field and training of surgeons. Active collaboration between medical and engineering teams and academic and industry groups is mandatory to establish such medical systems to improve patient care. PMID:27464471

Energy Conservation Projects to Benefit the Railroad Industry

DOE Office of Scientific and Technical Information (OSTI.GOV)

Clifford Mirman; Promod Vohra

The Energy Conservation Projects to benefit the railroad industry using the Norfolk Southern Company as a model for the railroad industry has five unique tasks which are in areas of importance within the rail industry, and specifically in the area of energy conservation. The NIU Engineering and Technology research team looked at five significant areas in which research and development work can provide unique solutions to the railroad industry in energy the conservation. (1) Alternate Fuels - An examination of various blends of bio-based diesel fuels for the railroad industry, using Norfolk Southern as a model for the industry. Themore » team determined that bio-diesel fuel is a suitable alternative to using straight diesel fuel, however, the cost and availability across the country varies to a great extent. (2) Utilization of fuel cells for locomotive power systems - While the application of the fuel cell has been successfully demonstrated in the passenger car, this is a very advanced topic for the railroad industry. There are many safety and power issues that the research team examined. (3) Thermal and emission reduction for current large scale diesel engines - The current locomotive system generates large amount of heat through engine cooling and heat dissipation when the traction motors are used to decelerate the train. The research team evaluated thermal management systems to efficiently deal with large thermal loads developed by the operating engines. (4) Use of Composite and Exotic Replacement Materials - Research team redesigned various components using new materials, coatings, and processes to provide the needed protection. Through design, analysis, and testing, new parts that can withstand the hostile environments were developed. (5) Tribology Applications - Identification of tribology issues in the Railroad industry which play a significant role in the improvement of energy usage. Research team analyzed and developed solutions which resulted in friction modification to improve energy efficiency.« less

Skills Conversion Project: Chapter 9, Security Systems and Criminal Justice. Final Report.

ERIC Educational Resources Information Center

National Society of Professional Engineers, Washington, DC.

This report provides the findings of two skills conversion research teams on the placement of displaced aerospace and defense engineers, scientists, and technicians in the fields of security systems and criminal justice. The teams, located in Philadelphia and San Jose, concluded independently that a minimum of 2,000 positions could be created in…

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

NASA Technical Reports Server (NTRS)

Catena, John J.; Saylor, Rick; Casasanta, Ralph; Weikel, Craig; Powers, Edward I. (Technical Monitor)

2000-01-01

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

Towards a Rigorous Assessment of Systems Biology Models: The DREAM3 Challenges

PubMed Central

Prill, Robert J.; Marbach, Daniel; Saez-Rodriguez, Julio; Sorger, Peter K.; Alexopoulos, Leonidas G.; Xue, Xiaowei; Clarke, Neil D.; Altan-Bonnet, Gregoire; Stolovitzky, Gustavo

2010-01-01

Background Systems biology has embraced computational modeling in response to the quantitative nature and increasing scale of contemporary data sets. The onslaught of data is accelerating as molecular profiling technology evolves. The Dialogue for Reverse Engineering Assessments and Methods (DREAM) is a community effort to catalyze discussion about the design, application, and assessment of systems biology models through annual reverse-engineering challenges. Methodology and Principal Findings We describe our assessments of the four challenges associated with the third DREAM conference which came to be known as the DREAM3 challenges: signaling cascade identification, signaling response prediction, gene expression prediction, and the DREAM3 in silico network challenge. The challenges, based on anonymized data sets, tested participants in network inference and prediction of measurements. Forty teams submitted 413 predicted networks and measurement test sets. Overall, a handful of best-performer teams were identified, while a majority of teams made predictions that were equivalent to random. Counterintuitively, combining the predictions of multiple teams (including the weaker teams) can in some cases improve predictive power beyond that of any single method. Conclusions DREAM provides valuable feedback to practitioners of systems biology modeling. Lessons learned from the predictions of the community provide much-needed context for interpreting claims of efficacy of algorithms described in the scientific literature. PMID:20186320

Decisionmaking in Military Command Teams: An Experimental Study

DTIC Science & Technology

1992-03-01

of the problems that remain to be solved by systems designers . The Fogarty report concluded that "The AEGIS combat system’s performance was excellent...1989). He maintains that the designers of the AEGIS system failed to incorporate enough human engineering in their design . Without addressing the fault...Naval Command Teams (RAINCOAT), Composite Warfare Commander - Destributed Dynamc Decisionmaking ICWC-[I)), resource coordination, resource effectiveness

Nuclear Engine System Simulation (NESS) version 2.0

NASA Technical Reports Server (NTRS)

Pelaccio, Dennis G.; Scheil, Christine M.; Petrosky, Lyman J.

1993-01-01

The topics are presented in viewgraph form and include the following; nuclear thermal propulsion (NTP) engine system analysis program development; nuclear thermal propulsion engine analysis capability requirements; team resources used to support NESS development; expanded liquid engine simulations (ELES) computer model; ELES verification examples; NESS program development evolution; past NTP ELES analysis code modifications and verifications; general NTP engine system features modeled by NESS; representative NTP expander, gas generator, and bleed engine system cycles modeled by NESS; NESS program overview; NESS program flow logic; enabler (NERVA type) nuclear thermal rocket engine; prismatic fuel elements and supports; reactor fuel and support element parameters; reactor parameters as a function of thrust level; internal shield sizing; and reactor thermal model.

KSC-2013-3533

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled helicopter with a unique set of sensors and software assembled by a team of engineers from NASA's Johnson Space Center prepares to fly in a competition at the agency's Kennedy Space Center. Teams from Johnson, Kennedy and Marshall Space Flight Center competed in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

Linking engineering and medicine: fostering collaboration skills in interdisciplinary teams.

PubMed

Khoo, Michael C K

2012-07-01

Biomedical engineering embodies the spirit of combining disciplines. The engineer's pragmatic approach to--and appetite for--solving problems is matched by a bounty of technical challenges generated in medical domains. From nanoscale diagnostics to the redesign of systems of health-care delivery, engineers have been connecting advances in basic and applied science with applications that have helped to improve medical care and outcomes. Increasingly, however, integrating these areas of knowledge and application is less individualistic and more of a team sport. Success increasingly relies on a direct focus on practicing and developing collaboration skills in interdisciplinary teams. Such an approach does not fit easily into individual-focused, discipline-based programs. Biomedical engineering has done its fair share of silo busting, but new approaches are needed to inspire interdisciplinary teams to form around challenges in particular areas. Health care offers a wide variety of complex challenges across an array of delivery settings that can call for new interdisciplinary approaches. This was recognized by the deans of the University of Southern California's (USC's) Medical and Engineering Schools when they began the planning process, leading to the creation of the Health, Technology, and Engineering (HTE@USC or HTE for short) program. “Health care and technology are changing rapidly, and future physicians and engineers need intellectual tools to stay ahead of this change,” says Carmen A. Puliafito, dean of the Keck School of Medicine. His goal is to train national leaders in the quest for devices and processes to improve health care.

STS-114 Mission Management Team Meeting

NASA Image and Video Library

2005-08-04

JSC2005-E-32012 (4 August 2005) --- John Muratore, Manager of Space Shuttle Systems Engineering & Integration Office, discusses a key STS-114 issue during the Mission Management Team (MMT) session of the afternoon of August 4. The MMT meets daily in Houston's Mission Control Center.

Pediatric medical device development by surgeons via capstone engineering design programs.

PubMed

Sack, Bryan S; Elizondo, Rodolfo A; Huang, Gene O; Janzen, Nicolette; Espinoza, Jimmy; Sanz-Cortes, Magdalena; Dietrich, Jennifer E; Hakim, Julie; Richardson, Eric S; Oden, Maria; Hanks, John; Haridas, Balakrishna; Hury, James F; Koh, Chester J

2018-03-01

There is a need for pediatric medical devices that accommodate the unique physiology and anatomy of pediatric patients that is increasingly receiving more attention. However, there is limited literature on the programs within children's hospitals and academia that can support pediatric device development. We describe our experience with pediatric device design utilizing collaborations between a children's hospital and two engineering schools. Utilizing the academic year as a timeline, unmet pediatric device needs were identified by surgical faculty and matched with an engineering mentor and a team of students within the Capstone Engineering Design programs at two universities. The final prototypes were showcased at the end of the academic year and if appropriate, provisional patent applications were filed. All twelve teams successfully developed device prototypes, and five teams obtained provisional patents. The prototypes that obtained provisional patents included a non-operative ureteral stent removal system, an evacuation device for small kidney stone fragments, a mechanical leech, an anchoring system of the chorio-amniotic membranes during fetal surgery, and a fetal oxygenation monitor during fetoscopic procedures. Capstone Engineering Design programs in partnership with surgical faculty at children's hospitals can play an effective role in the prototype development of novel pediatric medical devices. N/A - No clinical subjects or human testing was performed. Copyright © 2017 Elsevier Inc. All rights reserved.

Engineering Design and Automation in the Applied Engineering Technologies (AET) Group at Los Alamos National Laboratory.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Wantuck, P. J.; Hollen, R. M.

2002-01-01

This paper provides an overview of some design and automation-related projects ongoing within the Applied Engineering Technologies (AET) Group at Los Alamos National Laboratory. AET uses a diverse set of technical capabilities to develop and apply processes and technologies to applications for a variety of customers both internal and external to the Laboratory. The Advanced Recovery and Integrated Extraction System (ARIES) represents a new paradigm for the processing of nuclear material from retired weapon systems in an environment that seeks to minimize the radiation dose to workers. To achieve this goal, ARIES relies upon automation-based features to handle and processmore » the nuclear material. Our Chemical Process Development Team specializes in fuzzy logic and intelligent control systems. Neural network technology has been utilized in some advanced control systems developed by team members. Genetic algorithms and neural networks have often been applied for data analysis. Enterprise modeling, or discrete event simulation, as well as chemical process simulation has been employed for chemical process plant design. Fuel cell research and development has historically been an active effort within the AET organization. Under the principal sponsorship of the Department of Energy, the Fuel Cell Team is now focusing on technologies required to produce fuel cell compatible feed gas from reformation of a variety of conventional fuels (e.g., gasoline, natural gas), principally for automotive applications. This effort involves chemical reactor design and analysis, process modeling, catalyst analysis, as well as full scale system characterization and testing. The group's Automation and Robotics team has at its foundation many years of experience delivering automated and robotic systems for nuclear, analytical chemistry, and bioengineering applications. As an integrator of commercial systems and a developer of unique custom-made systems, the team currently supports the automation needs of many Laboratory programs.« less

From Paper to Production: An Update on NASA's Upper Stage Engine for Exploration

NASA Technical Reports Server (NTRS)

Kynard, Mike

2010-01-01

In 2006, NASA selected an evolved variant of the proven Saturn/Apollo J-2 upper stage engine to power the Ares I crew launch vehicle upper stage and the Ares V cargo launch vehicle Earth departure stage (EDS) for the Constellation Program. Any design changes needed by the new engine would be based where possible on proven hardware from the Space Shuttle, commercial launchers, and other programs. In addition to the thrust and efficiency requirements needed for the Constellation reference missions, it would be an order of magnitude safer than past engines. It required the J-2X government/industry team to develop the highest performance engine of its type in history and develop it for use in two vehicles for two different missions. In the attempt to achieve these goals in the past five years, the Upper Stage Engine team has made significant progress, successfully passing System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of spring 2010, more than 100,000 experimental and development engine parts have been completed or are in various stages of manufacture. Approximately 1,300 of more than 1,600 engine drawings have been released for manufacturing. This progress has been due to a combination of factors: the heritage hardware starting point, advanced computer analysis, and early heritage and development component testing to understand performance, validate computer modeling, and inform design trades. This work will increase the odds of success as engine team prepares for powerpack and development engine hot fire testing in calendar 2011. This paper will provide an overview of the engine development program and progress to date.

Including natural systems into the system engineering process: benefits to spaceflight and beyond

NASA Astrophysics Data System (ADS)

Studor, George

2014-03-01

How did we get to the point where we don't have time to be inspired by the wonders of Nature? Our office walls, homes and city streets are so plain that even when we do escape to a retreat with nature all around us, we may be blind to its magnificence. Yet there are many who have applied what can be known of natural systems (NS) to create practical solutions, but often definite applications for them are lacking. Mimicry of natural systems is not only more possible than ever before, but the education and research programs in many major universities are churning out graduates with a real appreciation for Nature's complex integrated systems. What if these skills and perspectives were employed in the teams of systems engineers and the technology developers that support them to help the teams think "outside-the-box" of manmade inventions? If systems engineers (SE) and technology developers regularly asked the question, "what can we learn from Nature that will help us?" as a part of their processes, they would discover another set of potential solutions. Biomimicry and knowledge of natural systems is exploding. What does this mean for systems engineering and technology? Some disciplines such as robotics and medical devices must consider nature constantly. Perhaps it's time for all technology developers and systems engineers to perceive natural systems experts as potential providers of the technologies they need.

Integrated System-Level Optimization for Concurrent Engineering With Parametric Subsystem Modeling

NASA Technical Reports Server (NTRS)

Schuman, Todd; DeWeck, Oliver L.; Sobieski, Jaroslaw

2005-01-01

The introduction of concurrent design practices to the aerospace industry has greatly increased the productivity of engineers and teams during design sessions as demonstrated by JPL's Team X. Simultaneously, advances in computing power have given rise to a host of potent numerical optimization methods capable of solving complex multidisciplinary optimization problems containing hundreds of variables, constraints, and governing equations. Unfortunately, such methods are tedious to set up and require significant amounts of time and processor power to execute, thus making them unsuitable for rapid concurrent engineering use. This paper proposes a framework for Integration of System-Level Optimization with Concurrent Engineering (ISLOCE). It uses parametric neural-network approximations of the subsystem models. These approximations are then linked to a system-level optimizer that is capable of reaching a solution quickly due to the reduced complexity of the approximations. The integration structure is described in detail and applied to the multiobjective design of a simplified Space Shuttle external fuel tank model. Further, a comparison is made between the new framework and traditional concurrent engineering (without system optimization) through an experimental trial with two groups of engineers. Each method is evaluated in terms of optimizer accuracy, time to solution, and ease of use. The results suggest that system-level optimization, running as a background process during integrated concurrent engineering sessions, is potentially advantageous as long as it is judiciously implemented.

Biomedical engineering education through global engineering teams.

PubMed

Scheffer, C; Blanckenberg, M; Garth-Davis, B; Eisenberg, M

2012-01-01

Most industrial projects require a team of engineers from a variety of disciplines. The team members are often culturally diverse and geographically dispersed. Many students do not acquire sufficient skills from typical university courses to function efficiently in such an environment. The Global Engineering Teams (GET) programme was designed to prepare students such a scenario in industry. This paper discusses five biomedical engineering themed projects completed by GET students. The benefits and success of the programme in educating students in the field of biomedical engineering are discussed.

SOFIA Program SE and I Lessons Learned

NASA Technical Reports Server (NTRS)

Ray, Ronald J.; Fobel, Laura J.; Brignola, Michael P.

2011-01-01

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Consequences of team charter quality: Teamwork mental model similarity and team viability in engineering design student teams

NASA Astrophysics Data System (ADS)

Conway Hughston, Veronica

Since 1996 ABET has mandated that undergraduate engineering degree granting institutions focus on learning outcomes such as professional skills (i.e. solving unstructured problems and working in teams). As a result, engineering curricula were restructured to include team based learning---including team charters. Team charters were diffused into engineering education as one of many instructional activities to meet the ABET accreditation mandates. However, the implementation and execution of team charters into engineering team based classes has been inconsistent and accepted without empirical evidence of the consequences. The purpose of the current study was to investigate team effectiveness, operationalized as team viability, as an outcome of team charter implementation in an undergraduate engineering team based design course. Two research questions were the focus of the study: a) What is the relationship between team charter quality and viability in engineering student teams, and b) What is the relationship among team charter quality, teamwork mental model similarity, and viability in engineering student teams? Thirty-eight intact teams, 23 treatment and 15 comparison, participated in the investigation. Treatment teams attended a team charter lecture, and completed a team charter homework assignment. Each team charter was assessed and assigned a quality score. Comparison teams did not join the lecture, and were not asked to create a team charter. All teams completed each data collection phase: a) similarity rating pretest; b) similarity posttest; and c) team viability survey. Findings indicate that team viability was higher in teams that attended the lecture and completed the charter assignment. Teams with higher quality team charter scores reported higher levels of team viability than teams with lower quality charter scores. Lastly, no evidence was found to support teamwork mental model similarity as a partial mediator of the team charter quality on team viability relationship. Foci for future research opportunities include using: a) online data collection methods to improve participant adherence to similarity rating instructions; b) story or narratives during pre- and posttest similarity rating data collection to create common levels of contextual perception; and c) support to ensure charters are integrated into the full project life cycle, not just a pre-project one time isolated activity. Twenty five sections, on average, of EDSGN 100 are taught each spring and fall semester. Consistent instructor expectations are set for the technical aspects of the course. However, ideas to foster team effectiveness are often left to the discretion of the individual instructor. Implementing empirically tested team effectiveness instructional activities would bring consistency to EDGSN 100 curriculum. Other instructional activities that would be of benefit to engineering educators include qualitative inquiry---asking intrateam process questions (at the mid-point of the project) and in-class reflection---dedicated time, post project, to discuss what went well/not well within the team.

The 2015-2016 SEPMAP Program at NASA JSC: Science, Engineering, and Program Management Training

NASA Technical Reports Server (NTRS)

Graham, L.; Archer, D.; Bakalyar, J.; Berger, E.; Blome, E.; Brown, R.; Cox, S.; Curiel, P.; Eid, R.; Eppler, D.;

The Value of SysML Modeling During System Operations: A Case Study

NASA Technical Reports Server (NTRS)

Dutenhoffer, Chelsea; Tirona, Joseph

2013-01-01

System models are often touted as engineering tools that promote better understanding of systems, but these models are typically created during system design. The Ground Data System (GDS) team for the Dawn spacecraft took on a case study to see if benefits could be achieved by starting a model of a system already in operations. This paper focuses on the four steps the team undertook in modeling the Dawn GDS: defining a model structure, populating model elements, verifying that the model represented reality, and using the model to answer system-level questions and simplify day-to-day tasks. Throughout this paper the team outlines our thought processes and the system insights the model provided.

The value of SysML modeling during system operations: A case study

NASA Astrophysics Data System (ADS)

Dutenhoffer, C.; Tirona, J.

System models are often touted as engineering tools that promote better understanding of systems, but these models are typically created during system design. The Ground Data System (GDS) team for the Dawn spacecraft took on a case study to see if benefits could be achieved by starting a model of a system already in operations. This paper focuses on the four steps the team undertook in modeling the Dawn GDS: defining a model structure, populating model elements, verifying that the model represented reality, and using the model to answer system-level questions and simplify day-to-day tasks. Throughout this paper the team outlines our thought processes and the system insights the model provided.

Introduction to the Navigation Team: Johnson Space Center EG6 Internship

NASA Technical Reports Server (NTRS)

Gualdoni, Matthew

2017-01-01

The EG6 navigation team at NASA Johnson Space Center, like any team of engineers, interacts with the engineering process from beginning to end; from exploring solutions to a problem, to prototyping and studying the implementations, all the way to polishing and verifying a final flight-ready design. This summer, I was privileged enough to gain exposure to each of these processes, while also getting to truly experience working within a team of engineers. My summer can be broken up into three projects: i) Initial study and prototyping: investigating a manual navigation method that can be utilized onboard Orion in the event of catastrophic failure of navigation systems; ii) Finalizing and verifying code: altering a software routine to improve its robustness and reliability, as well as designing unit tests to verify its performance; and iii) Development of testing equipment: assisting in developing and integrating of a high-fidelity testbed to verify the performance of software and hardware.

SE Capstone Project: Building Systems Engineering Education and Workforce Capacity

DTIC Science & Technology

2012-04-01

This project developed a system to improve fuel efficiency by means of regenerative braking . The team designed a simple system that allows "bolt-on...air traffic control, social networking, credit/debit cards, and anti-lock brakes are only a few functions enabled by complex systems of systems . We...Building Systems Engineering Education and Workforce Capacity SE Capstone Project APRIL 2012 Report Documentation Page Form ApprovedOMB No. 0704

The twelfth annual Intelligent Ground Vehicle Competition: team approaches to intelligent vehicles

NASA Astrophysics Data System (ADS)

Theisen, Bernard L.; Maslach, Daniel

2004-10-01

The Intelligent Ground Vehicle Competition (IGVC) is one of three, unmanned systems, student competitions that were founded by the Association for Unmanned Vehicle Systems International (AUVSI) in the 1990s. The IGVC is a multidisciplinary exercise in product realization that challenges college engineering student teams to integrate advanced control theory, machine vision, vehicular electronics, and mobile platform fundamentals to design and build an unmanned system. Both U.S. and international teams focus on developing a suite of dual-use technologies to equip ground vehicles of the future with intelligent driving capabilities. Over the past 12 years, the competition has challenged undergraduate, graduate and Ph.D. students with real world applications in intelligent transportation systems, the military and manufacturing automation. To date, teams from over 43 universities and colleges have participated. This paper describes some of the applications of the technologies required by this competition and discusses the educational benefits. The primary goal of the IGVC is to advance engineering education in intelligent vehicles and related technologies. The employment and professional networking opportunities created for students and industrial sponsors through a series of technical events over the three-day competition are highlighted. Finally, an assessment of the competition based on participant feedback is presented.

Working Smarter Not Harder - Developing a Virtual Subsurface Data Framework for U.S. Energy R&D

NASA Astrophysics Data System (ADS)

Rose, K.; Baker, D.; Bauer, J.; Dehlin, M.; Jones, T. J.; Rowan, C.

2017-12-01

The data revolution has resulted in a proliferation of resources that span beyond commercial and social networking domains. Research, scientific, and engineering data resources, including subsurface characterization, modeling, and analytical datasets, are increasingly available through online portals, warehouses, and systems. Data for subsurface systems is still challenging to access, discontinuous, and varies in resolution. However, with the proliferation of online data there are significant opportunities to advance access and knowledge of subsurface systems. The Energy Data eXchange (EDX) is an online platform designed to address research data needs by improving access to energy R&D products through advanced search capabilities. In addition, EDX hosts private, virtualized computational workspaces in support of multi-organizational R&D. These collaborative workspaces allow teams to share working data resources and connect to a growing number of analytical tools to support research efforts. One recent application, a team digital data notebook tool, called DataBook, was introduced within EDX workspaces to allow teams to capture contextual and structured data resources. Starting with DOE's subsurface R&D community, the EDX team has been developing DataBook to support scientists and engineers working on subsurface energy research, allowing them to contribute and curate both structured and unstructured data and knowledge about subsurface systems. These resources span petrophysical, geologic, engineering, geophysical, interpretations, models, and analyses associated with carbon storage, water, oil, gas, geothermal, induced seismicity and other subsurface systems to support the development of a virtual subsurface data framework. The integration of EDX and DataBook allows for these systems to leverage each other's best features, such as the ability to interact with other systems (Earthcube, OpenEI.net, NGDS, etc.) and leverage custom machine learning algorithms and capabilities to enhance user experience, make access and connection to relevant subsurface data resources more efficient for research teams to use, analyze and draw insights. Ultimately, the public and private resources in EDX seek to make subsurface energy research more efficient, reduce redundancy, and drive innovation.

KSC-2013-3542

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled aircraft flies during a competition with a unique set of sensors and software to conduct a mock search-and-rescue operation. The aircraft was assembled by a team of engineers from NASA's Kennedy Space Center. Teams from Johnson Space Center, Kennedy and Marshall Space Flight Center competed in the unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3543

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled aircraft flies during a competition with a unique set of sensors and software to conduct a mock search-and-rescue operation. The aircraft was assembled by a team of engineers from NASA's Kennedy Space Center. Teams from Johnson Space Center, Kennedy and Marshall Space Flight Center competed in the unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3546

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled aircraft flies during a competition with a unique set of sensors and software to conduct a mock search-and-rescue operation. The aircraft was assembled by a team of engineers from NASA's Marshall Space Flight Center. Teams from Johnson Space Center, Kennedy Space Center and Marshall competed in the unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3540

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled aircraft takes off during a competition with a unique set of sensors and software to conduct a mock search-and-rescue operation. The aircraft was assembled by a team of engineers from NASA's Kennedy Space Center. Teams from Johnson Space Center, Kennedy and Marshall Space Flight Center competed in the unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3541

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – A remote-controlled aircraft flies during a competition with a unique set of sensors and software to conduct a mock search-and-rescue operation. The aircraft was assembled by a team of engineers from NASA's Kennedy Space Center. Teams from Johnson Space Center, Kennedy and Marshall Space Flight Center competed in the unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

Dr. von Braun With Management Team

NASA Technical Reports Server (NTRS)

1961-01-01

Dr. von Braun is shown in this photograph, which was probably taken in the early 1960s, with members of his management team. Pictured from left to right are, Werner Kuers, Director of the Manufacturing Engineering Division; Dr. Walter Haeussermarn, Director of the Astrionics Division; Dr. William Mrazek, Propulsion and Vehicle Engineering Division; Dr. von Braun; Dieter Grau, Director of the Quality Assurance Division; Dr. Oswald Lange, Director of the Saturn Systems Office; and Erich Neubert , Associate Deputy Director for Research and Development.

Vulcain engine tests prove reliability

NASA Astrophysics Data System (ADS)

Covault, Craig

1994-04-01

The development of the oxygen/hydrogen Vulcain first-stage engine for the Ariane 5 involves more than 30 European companies and $1.19-billion. These companies are using existing technology to produce a low-cost system with high thrust and reliability. This article describes ground test of this engine, and provides a comparison of the Vulcain's capabilities with the capabilities of other systems. A list of key Vulcain team members is also given.

Training System Device Certification and Qualification Process

DTIC Science & Technology

2013-09-01

Engineering IPT Integrated Product Team ISD Instructional Systems Development ISEO In-Service Engineering Office KSAs Knowledge, Skills, and Attributes...Plan TES Tactical Engagement Simulation TPM Training Pipeline Managers T&R Training and Readiness TRR Test Readiness Review TS Training System...NAWCTSD) is the Navy’s source for a full range of innovative products and services that provide complete training solutions. This includes

System Qualities Ontology, Tradespace and Affordability (SQOTA) Project: Phase 5

DTIC Science & Technology

2017-04-30

Principal Investigator: Dr. Barry Boehm, University of Southern California Research Team: Organizations 1: Air force Institute of Technology...Date April 30, 2017 Copyright © 2017 Stevens Institute of Technology, Systems Engineering Research Center The Systems Engineering Research ...Center (SERC) is a federally funded University Affiliated Research Center managed by Stevens Institute of Technology. This material is based upon

Space Station Food System

NASA Technical Reports Server (NTRS)

Thurmond, Beverly A.; Gillan, Douglas J.; Perchonok, Michele G.; Marcus, Beth A.; Bourland, Charles T.

1986-01-01

A team of engineers and food scientists from NASA, the aerospace industry, food companies, and academia are defining the Space Station Food System. The team identified the system requirements based on an analysis of past and current space food systems, food systems from isolated environment communities that resemble Space Station, and the projected Space Station parameters. The team is resolving conflicts among requirements through the use of trade-off analyses. The requirements will give rise to a set of specifications which, in turn, will be used to produce concepts. Concept verification will include testing of prototypes, both in 1-g and microgravity. The end-item specification provides an overall guide for assembling a functional food system for Space Station.

Pneumatic injection system using a hot exhaust gases, developed in Institute of Automobiles and Internal Combustion Engines of Cracow University of Technology

NASA Astrophysics Data System (ADS)

Marek, W.; Śliwiński, K.

2016-09-01

The article concerns research carried out by the Krakow University of Technology on the concept of a pneumatic fuel injection spark ignition engines. In this artkule an example of an application of this type of power to the Wankel's engine, together with a description of its design and operating principles and the benefits of its use. The work was carried out over many years by Prof. Stanislaw Jarnuszkiewicz despite the development of many patents but not widely used in engines. Authors who were involved in the team-work of the team of Prof. Jarnuszkiewicz, after conducting exploratory studies, believed that this solution has development potential and this will be presented in future articles.

Orion Flight Test 1 Architecture: Observed Benefits of a Model Based Engineering Approach

NASA Technical Reports Server (NTRS)

Simpson, Kimberly A.; Sindiy, Oleg V.; McVittie, Thomas I.

2012-01-01

This paper details how a NASA-led team is using a model-based systems engineering approach to capture, analyze and communicate the end-to-end information system architecture supporting the first unmanned orbital flight of the Orion Multi-Purpose Crew Exploration Vehicle. Along with a brief overview of the approach and its products, the paper focuses on the observed program-level benefits, challenges, and lessons learned; all of which may be applied to improve system engineering tasks for characteristically similarly challenges

Characterizing Distributed Concurrent Engineering Teams: A Descriptive Framework for Aerospace Concurrent Engineering Design Teams

NASA Technical Reports Server (NTRS)

Chattopadhyay, Debarati; Hihn, Jairus; Warfield, Keith

2011-01-01

As aerospace missions grow larger and more technically complex in the face of ever tighter budgets, it will become increasingly important to use concurrent engineering methods in the development of early conceptual designs because of their ability to facilitate rapid assessments and trades in a cost-efficient manner. To successfully accomplish these complex missions with limited funding, it is also essential to effectively leverage the strengths of individuals and teams across government, industry, academia, and international agencies by increased cooperation between organizations. As a result, the existing concurrent engineering teams will need to increasingly engage in distributed collaborative concurrent design. This paper is an extension of a recent white paper written by the Concurrent Engineering Working Group, which details the unique challenges of distributed collaborative concurrent engineering. This paper includes a short history of aerospace concurrent engineering, and defines the terms 'concurrent', 'collaborative' and 'distributed' in the context of aerospace concurrent engineering. In addition, a model for the levels of complexity of concurrent engineering teams is presented to provide a way to conceptualize information and data flow within these types of teams.

2014-2685

NASA Image and Video Library

2014-05-23

CAPE CANAVERAL, Fla. -- Kennedy Space Center engineer Marc Seibert presents the Communication Award to the University of New Hampshire team members during NASA's 2014 Robotic Mining Competition award ceremony inside the Space Shuttle Atlantis attraction at the Kennedy Space Center Visitor Complex in Florida. The team moved 10 kilograms of simulated Martian soil with its robot while using the least amount of communication power. More than 35 teams from colleges and universities around the U.S. designed and built remote-controlled robots for the mining competition. The competition is a NASA Human Exploration and Operations Mission Directorate project designed to engage and retain students in science, technology, engineering and mathematics, or STEM, fields by expanding opportunities for student research and design. Teams use their remote-controlled robotics to maneuver and dig in a supersized sandbox filled with a crushed material that has characteristics similar to Martian soil. The objective of the challenge is to see which team’s robot can collect and move the most regolith within a specified amount of time. The competition includes on-site mining, writing a systems engineering paper, performing outreach projects for K-12 students, slide presentation and demonstrations, and team spirit. For more information, visit www.nasa.gov/nasarmc. Photo credit: NASA/Kim Shiflett

Design Development Test and Evaluation (DDT and E) Considerations for Safe and Reliable Human Rated Spacecraft Systems

NASA Technical Reports Server (NTRS)

Miller, James; Leggett, Jay; Kramer-White, Julie

2008-01-01

A team directed by the NASA Engineering and Safety Center (NESC) collected methodologies for how best to develop safe and reliable human rated systems and how to identify the drivers that provide the basis for assessing safety and reliability. The team also identified techniques, methodologies, and best practices to assure that NASA can develop safe and reliable human rated systems. The results are drawn from a wide variety of resources, from experts involved with the space program since its inception to the best-practices espoused in contemporary engineering doctrine. This report focuses on safety and reliability considerations and does not duplicate or update any existing references. Neither does it intend to replace existing standards and policy.

Defining Medical Capabilities for Exploration Missions

NASA Technical Reports Server (NTRS)

Hailey, M.; Antonsen, E.; Blue, R.; Reyes, D.; Mulcahy, R.; Kerstman, E.; Bayuse, T.

2018-01-01

Exploration-class missions to the moon, Mars and beyond will require a significant change in medical capability from today's low earth orbit centric paradigm. Significant increases in autonomy will be required due to differences in duration, distance and orbital mechanics. Aerospace medicine and systems engineering teams are working together within ExMC to meet these challenges. Identifying exploration medical system needs requires accounting for planned and unplanned medical care as defined in the concept of operations. In 2017, the ExMC Clinicians group identified medical capabilities to feed into the Systems Engineering process, including: determining what and how to address planned and preventive medical care; defining an Accepted Medical Condition List (AMCL) of conditions that may occur and a subset of those that can be treated effectively within the exploration environment; and listing the medical capabilities needed to treat those conditions in the AMCL. This presentation will discuss the team's approach to addressing these issues, as well as how the outputs of the clinical process impact the systems engineering effort.

Virtual Collaborative Environments for System of Systems Engineering and Applications for ISAT

NASA Technical Reports Server (NTRS)

Dryer, David A.

2002-01-01

This paper describes an system of systems or metasystems approach and models developed to help prepare engineering organizations for distributed engineering environments. These changes in engineering enterprises include competition in increasingly global environments; new partnering opportunities caused by advances in information and communication technologies, and virtual collaboration issues associated with dispersed teams. To help address challenges and needs in this environment, a framework is proposed that can be customized and adapted for NASA to assist in improved engineering activities conducted in distributed, enhanced engineering environments. The approach is designed to prepare engineers for such distributed collaborative environments by learning and applying e-engineering methods and tools to a real-world engineering development scenario. The approach consists of two phases: an e-engineering basics phase and e-engineering application phase. The e-engineering basics phase addresses skills required for e-engineering. The e-engineering application phase applies these skills in a distributed collaborative environment to system development projects.

An engineering database management system for spacecraft operations

NASA Technical Reports Server (NTRS)

Cipollone, Gregorio; Mckay, Michael H.; Paris, Joseph

1993-01-01

Studies at ESOC have demonstrated the feasibility of a flexible and powerful Engineering Database Management System in support for spacecraft operations documentation. The objectives set out were three-fold: first an analysis of the problems encountered by the Operations team in obtaining and managing operations documents; secondly, the definition of a concept for operations documentation and the implementation of prototype to prove the feasibility of the concept; and thirdly, definition of standards and protocols required for the exchange of data between the top-level partners in a satellite project. The EDMS prototype was populated with ERS-l satellite design data and has been used by the operations team at ESOC to gather operational experience. An operational EDMS would be implemented at the satellite prime contractor's site as a common database for all technical information surrounding a project and would be accessible by the cocontractor's and ESA teams.

Educating Tomorrow's Aerrospace Engineers by Developing and Launching Liquid-Propelled Rockets

NASA Astrophysics Data System (ADS)

Besnard, Eric; Garvey, John; Holleman, Tom; Mueller, Tom

2002-01-01

conducted at California State University, Long Beach (CSULB), in which engineering students develop and launch liquid propelled rockets. The program is articulated around two main activities, each with specific objectives. The first component of CALVEIN is a systems integration laboratory where students develop/improve vehicle subsystems and integrate them into a vehicle (Prospector-2 - P-2 - for the 2001-02 academic year - AY). This component has three main objectives: (1) Develop hands- on skills for incoming students and expose them to aerospace hardware; (2) allow for upper division students who have been involved in the program to mentor incoming students and manage small teams; and (3) provide students from various disciplines within the College of Engineering - and other universities - with the chance to develop/improve subsystems on the vehicle. Among recent student projects conducted as part of this component are: a new 1000 lbf thrust engine using pintle injector technology, which was successfully tested on Dec. 1, 2001 and flown on Prospector-2 in Feb. 2002 (developed by CSULB Mechanical and Aerospace Engineering students); a digital flight telemetry package (developed by CSULB Electrical Engineering students); a new recovery system where a mechanical system replaces pyrotechnics for parachute release (developed by CSULB Mechanical and Aerospace Engineering students); and a 1-ft payload bay to accommodate experimental payloads (e.g. "CANSATS" developed by Stanford University students). The second component of CALVEIN is a formal Aerospace System Design curriculum. In the first-semester, from top-level system requirements, the students perform functional analysis, define the various subsystems and derive their requirements. These are presented at the Systems Functional and Requirement Reviews (SFR &SRR). The methods used for validation and verification are determined. Specifications and Interface Control Documents (ICD) are generated by the student team(s). Trade studies are identified and conducted, leading to a Preliminary Design Review (PDR) at the end of the first semester. A detailed design follows, culminating in a Critical Design Review (CDR), etc. A general process suitable for a two-semester course sequence will be outlined. The project is conducted in an Integrated Product Team (IPT) environment, which includes a project manager, a systems engineer, and the various disciplines needed for the project (propulsion, aerodynamics, structures and materials, mass, CAD, thermal, fluids, etc.). Each student works with a Faculty member or industry advisor who is a specialist in his/her area. This design curriculum enhances the education of the graduates and provides future employers with engineers cognizant of and experienced in the application of Systems Engineering to a full-scale project over the entire product development cycle. For the AY01-02, the curriculum is being applied to the development of a gimbaled aerospike engine and its integration into P-3, scheduled to fly in May 2002. The paper ends with a summary of "lessons learned" from this experience. Budget issues are also addressed to demonstrate the ability to replicate such projects at other institutions with minimal costs, provided that it can be taken advantages of possible synergies between existing programs, in-house resources, and cooperation with other institutions or organizations.

Improving engineering effectiveness

NASA Technical Reports Server (NTRS)

Fiero, J. D.

1985-01-01

Methodologies to improve engineering productivity were investigated. The rocky road to improving engineering effectiveness is reviewed utilizing a specific semiconductor engineering organization as a case study. The organization had a performance problem regarding new product introductions. With the help of this consultant as a change agent the engineering team used a systems approach to through variables that were effecting their output significantly. Critical factors for improving this engineering organization's effectiveness and the roles/responsibilities of management, the individual engineers and the internal consultant are discussed.

Detecting the Norovirus Season in Sweden Using Search Engine Data – Meeting the Needs of Hospital Infection Control Teams

PubMed Central

Edelstein, Michael; Wallensten, Anders; Zetterqvist, Inga; Hulth, Anette

2014-01-01

Norovirus outbreaks severely disrupt healthcare systems. We evaluated whether Websök, an internet-based surveillance system using search engine data, improved norovirus surveillance and response in Sweden. We compared Websök users' characteristics with the general population, cross-correlated weekly Websök searches with laboratory notifications between 2006 and 2013, compared the time Websök and laboratory data crossed the epidemic threshold and surveyed infection control teams about their perception and use of Websök. Users of Websök were not representative of the general population. Websök correlated with laboratory data (b = 0.88-0.89) and gave an earlier signal to the onset of the norovirus season compared with laboratory-based surveillance. 17/21 (81%) infection control teams answered the survey, of which 11 (65%) believed Websök could help with infection control plans. Websök is a low-resource, easily replicable system that detects the norovirus season as reliably as laboratory data, but earlier. Using Websök in routine surveillance can help infection control teams prepare for the yearly norovirus season. PMID:24955857

Detecting the norovirus season in Sweden using search engine data--meeting the needs of hospital infection control teams.

PubMed

Edelstein, Michael; Wallensten, Anders; Zetterqvist, Inga; Hulth, Anette

2014-01-01

Norovirus outbreaks severely disrupt healthcare systems. We evaluated whether Websök, an internet-based surveillance system using search engine data, improved norovirus surveillance and response in Sweden. We compared Websök users' characteristics with the general population, cross-correlated weekly Websök searches with laboratory notifications between 2006 and 2013, compared the time Websök and laboratory data crossed the epidemic threshold and surveyed infection control teams about their perception and use of Websök. Users of Websök were not representative of the general population. Websök correlated with laboratory data (b = 0.88-0.89) and gave an earlier signal to the onset of the norovirus season compared with laboratory-based surveillance. 17/21 (81%) infection control teams answered the survey, of which 11 (65%) believed Websök could help with infection control plans. Websök is a low-resource, easily replicable system that detects the norovirus season as reliably as laboratory data, but earlier. Using Websök in routine surveillance can help infection control teams prepare for the yearly norovirus season.

Global Engineering Teams--A Programme Promoting Teamwork in Engineering Design and Manufacturing

ERIC Educational Resources Information Center

Oladiran, M. T.; Uziak, J.; Eisenberg, M.; Scheffer, C.

2011-01-01

Engineering graduates are expected to possess various competencies categorised into hard and soft skills. The hard skills are acquired through specific coursework, but the soft skills are often treated perfunctorily. Global Engineering Teams (GET) is a programme that promotes project-oriented tasks in virtual student teams working in collaboration…

Update on Risk Reduction Activities for a Liquid Advanced Booster for NASA's Space Launch System

NASA Technical Reports Server (NTRS)

Crocker, Andrew M.; Greene, William D.

2017-01-01

The stated goals of NASA's Research Announcement for the Space Launch System (SLS) Advanced Booster Engineering Demonstration and/or Risk Reduction (ABEDRR) are to reduce risks leading to an affordable Advanced Booster that meets the evolved capabilities of SLS and enable competition by mitigating targeted Advanced Booster risks to enhance SLS affordability. Dynetics, Inc. and Aerojet Rocketdyne (AR) formed a team to offer a wide-ranging set of risk reduction activities and full-scale, system-level demonstrations that support NASA's ABEDRR goals. During the ABEDRR effort, the Dynetics Team has modified flight-proven Apollo-Saturn F-1 engine components and subsystems to improve affordability and reliability (e.g., reduce parts counts, touch labor, or use lower cost manufacturing processes and materials). The team has built hardware to validate production costs and completed tests to demonstrate it can meet performance requirements. State-of-the-art manufacturing and processing techniques have been applied to the heritage F-1, resulting in a low recurring cost engine while retaining the benefits of Apollo-era experience. NASA test facilities have been used to perform low-cost risk-reduction engine testing. In early 2014, NASA and the Dynetics Team agreed to move additional large liquid oxygen/kerosene engine work under Dynetics' ABEDRR contract. Also led by AR, the objectives of this work are to demonstrate combustion stability and measure performance of a 500,000 lbf class Oxidizer-Rich Staged Combustion (ORSC) cycle main injector. A trade study was completed to investigate the feasibility, cost effectiveness, and technical maturity of a domestically-produced engine that could potentially both replace the RD-180 on Atlas V and satisfy NASA SLS payload-to-orbit requirements via an advanced booster application. Engine physical dimensions and performance parameters resulting from this study provide the system level requirements for the ORSC risk reduction test article. The test article is scheduled to complete fabrication and assembly soon and continue testing through late 2019. Dynetics has also designed, developed, and built innovative tank and structure assemblies using friction stir welding to leverage recent NASA investments in manufacturing tools, facilities, and processes, significantly reducing development and recurring costs. The full-scale cryotank assembly was used to verify the structural design and prove affordable processes. Dynetics performed hydrostatic and cryothermal proof tests on the assembly to verify the assembly meets performance requirements..

Technology as Teammate: Examining the Role of External Cognition in Support of Team Cognitive Processes

PubMed Central

Fiore, Stephen M.; Wiltshire, Travis J.

2016-01-01

In this paper we advance team theory by describing how cognition occurs across the distribution of members and the artifacts and technology that support their efforts. We draw from complementary theorizing coming out of cognitive engineering and cognitive science that views forms of cognition as external and extended and integrate this with theorizing on macrocognition in teams. Two frameworks are described that provide the groundwork for advancing theory and aid in the development of more precise measures for understanding team cognition via focus on artifacts and the technologies supporting their development and use. This includes distinctions between teamwork and taskwork and the notion of general and specific competencies from the organizational sciences along with the concepts of offloading and scaffolding from the cognitive sciences. This paper contributes to the team cognition literature along multiple lines. First, it aids theory development by synthesizing a broad set of perspectives on the varied forms of cognition emerging in complex collaborative contexts. Second, it supports research by providing diagnostic guidelines to study how artifacts are related to team cognition. Finally, it supports information systems designers by more precisely describing how to conceptualize team-supporting technology and artifacts. As such, it provides a means to more richly understand process and performance as it occurs within sociotechnical systems. Our overarching objective is to show how team cognition can both be more clearly conceptualized and more precisely measured by integrating theory from cognitive engineering and the cognitive and organizational sciences. PMID:27774074

Technology as Teammate: Examining the Role of External Cognition in Support of Team Cognitive Processes.

PubMed

Fiore, Stephen M; Wiltshire, Travis J

2016-01-01

In this paper we advance team theory by describing how cognition occurs across the distribution of members and the artifacts and technology that support their efforts. We draw from complementary theorizing coming out of cognitive engineering and cognitive science that views forms of cognition as external and extended and integrate this with theorizing on macrocognition in teams. Two frameworks are described that provide the groundwork for advancing theory and aid in the development of more precise measures for understanding team cognition via focus on artifacts and the technologies supporting their development and use. This includes distinctions between teamwork and taskwork and the notion of general and specific competencies from the organizational sciences along with the concepts of offloading and scaffolding from the cognitive sciences. This paper contributes to the team cognition literature along multiple lines. First, it aids theory development by synthesizing a broad set of perspectives on the varied forms of cognition emerging in complex collaborative contexts. Second, it supports research by providing diagnostic guidelines to study how artifacts are related to team cognition. Finally, it supports information systems designers by more precisely describing how to conceptualize team-supporting technology and artifacts. As such, it provides a means to more richly understand process and performance as it occurs within sociotechnical systems. Our overarching objective is to show how team cognition can both be more clearly conceptualized and more precisely measured by integrating theory from cognitive engineering and the cognitive and organizational sciences.

Touchdown: The Development of Propulsion Controlled Aircraft at NASA Dryden

NASA Technical Reports Server (NTRS)

Tucker, Tom

1999-01-01

This monograph relates the important history of the Propulsion Controlled Aircraft project at NASA's Dryden Flight Research Center. Spurred by a number of airplane crashes caused by the loss of hydraulic flight controls, a NASA-industry team lead by Frank W. Burcham and C. Gordon Fullerton developed a way to land an aircraft safely using only engine thrust to control the airplane. In spite of initial skepticism, the team discovered that, by manually manipulating an airplane's thrust, there was adequate control for extended up-and-away flight. However, there was not adequate control precision for safe runway landings because of the small control forces, slow response, and difficulty in damping the airplane phugoid and Dutch roll oscillations. The team therefore conceived, developed, and tested the first computerized Propulsion Controlled Aircraft (PCA) system. The PCA system takes pilot commands, uses feedback from airplane measurements, and computes commands for the thrust of each engine, yielding much more precise control. Pitch rate and velocity feedback damp the phugoid oscillation, while yaw rate feedback damps the Dutch roll motion. The team tested the PCA system in simulators and conducted flight research in F-15 and MD-11 airplanes. Later, they developed less sophisticated variants of PCA called PCA Lite and PCA Ultralite to make the system cheaper and therefore more attractive to industry. This monograph tells the PCA story in a non- technical way with emphasis on the human aspects of the engineering and flic,ht-research effort. It thereby supplements the extensive technical literature on PCA and makes the development of this technology accessible to a wide audience.

Building a computer-aided design capability using a standard time share operating system

NASA Technical Reports Server (NTRS)

Sobieszczanski, J.

1975-01-01

The paper describes how an integrated system of engineering computer programs can be built using a standard commercially available operating system. The discussion opens with an outline of the auxiliary functions that an operating system can perform for a team of engineers involved in a large and complex task. An example of a specific integrated system is provided to explain how the standard operating system features can be used to organize the programs into a simple and inexpensive but effective system. Applications to an aircraft structural design study are discussed to illustrate the use of an integrated system as a flexible and efficient engineering tool. The discussion concludes with an engineer's assessment of an operating system's capabilities and desirable improvements.

DRACO Flowpath Performance and Environments

NASA Technical Reports Server (NTRS)

Komar, D. R.; McDonald, Jon

1999-01-01

The Advanced Space Transportation (AST) project office has challenged NASA to design, manufacture, ground-test and flight-test an axisymmetric, hydrocarbon-fueled, flight-weight, ejector-ramjet engine system testbed no later than 2005. To accomplish this, a multi-center NASA team has been assembled. The goal of this team, led by NASA-Marshall Space Flight Center (MSFC), is to develop propulsion technologies that demonstrate rocket and airbreathing combined-cycle operation (DRACO). Current technical activities include flowpath conceptual design, engine systems conceptual design, and feasibility studies investigating the integration and operation of the DRACO engine with a Lockheed D-21B drone. This paper focuses on the activities of the Flowpath Systems Product Development Team (PDT), led by NASA-Glenn Research Center (GRC) and supported by NASA-MSFC and TechLand Research, Inc. The objective of the Flowpath PDT at the start of the DRACO program was to establish a conceptual design of the flowpath aerodynamic lines, determine the preliminary performance, define the internal environments, and support the DRACO testbed concept feasibility studies. To accomplish these tasks, the PDT convened to establish a baseline flowpath concept. With the conceptual lines defined, cycle analysis tasks were planned and the flowpath performance and internal environments were defined. Additionally, sensitivity studies investigating the effects of inlet reference area, combustion performance, and combustor/nozzle materials selection were performed to support the Flowpath PDT design process. Results of these tasks are the emphasis of this paper and are intended to verify the feasibility of the DRACO flowpath and engine system as well as identify the primary technical challenges inherent in the flight-weight design of an advanced propulsion technology demonstration engine. Preliminary cycle performance decks were developed to support the testbed concept feasibility studies but are not discussed further in this paper.

What is the Final Verification of Engineering Requirements?

NASA Technical Reports Server (NTRS)

Poole, Eric

2010-01-01

This slide presentation reviews the process of development through the final verification of engineering requirements. The definition of the requirements is driven by basic needs, and should be reviewed by both the supplier and the customer. All involved need to agree upon a formal requirements including changes to the original requirements document. After the requirements have ben developed, the engineering team begins to design the system. The final design is reviewed by other organizations. The final operational system must satisfy the original requirements, though many verifications should be performed during the process. The verification methods that are used are test, inspection, analysis and demonstration. The plan for verification should be created once the system requirements are documented. The plan should include assurances that every requirement is formally verified, that the methods and the responsible organizations are specified, and that the plan is reviewed by all parties. The options of having the engineering team involved in all phases of the development as opposed to having some other organization continue the process once the design has been complete is discussed.

78 FR 7464 - Large Scale Networking (LSN) ; Joint Engineering Team (JET)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-02-01

... NATIONAL SCIENCE FOUNDATION Large Scale Networking (LSN) ; Joint Engineering Team (JET) AGENCY: The Networking and Information Technology Research and Development (NITRD) National Coordination...://www.nitrd.gov/nitrdgroups/index.php?title=Joint_Engineering_Team_ (JET)#title. SUMMARY: The JET...

The 13 th Annual Intelligent Ground Vehicle Competition: intelligent ground vehicles created by intelligent teams

NASA Astrophysics Data System (ADS)

Theisen, Bernard L.

2005-10-01

The Intelligent Ground Vehicle Competition (IGVC) is one of three, unmanned systems, student competitions that were founded by the Association for Unmanned Vehicle Systems International (AUVSI) in the 1990s. The IGVC is a multidisciplinary exercise in product realization that challenges college engineering student teams to integrate advanced control theory, machine vision, vehicular electronics, and mobile platform fundamentals to design and build an unmanned system. Teams from around the world focus on developing a suite of dual-use technologies to equip ground vehicles of the future with intelligent driving capabilities. Over the past 13 years, the competition has challenged undergraduate, graduate and Ph.D. students with real world applications in intelligent transportation systems, the military and manufacturing automation. To date, teams from over 50 universities and colleges have participated. This paper describes some of the applications of the technologies required by this competition and discusses the educational benefits. The primary goal of the IGVC is to advance engineering education in intelligent vehicles and related technologies. The employment and professional networking opportunities created for students and industrial sponsors through a series of technical events over the three-day competition are highlighted. Finally, an assessment of the competition based on participant feedback is presented.

11th Annual Intelligent Ground Vehicle Competition: team approaches to intelligent driving and machine vision

NASA Astrophysics Data System (ADS)

Theisen, Bernard L.; Lane, Gerald R.

2003-10-01

The Intelligent Ground Vehicle Competition (IGVC) is one of three, unmanned systems, student competitions that were founded by the Association for Unmanned Vehicle Systems International (AUVSI) in the 1990's. The IGVC is a multidisciplinary exercise in product realization that challenges college engineering student teams to integrate advanced control theory, machine vision, vehicular electronics, and mobile platform fundamentals to design and build an unmanned system. Both the U.S. and international teams focus on developing a suite of dual-use technologies to equip ground vehicles of the future with intelligtent driving capabilities. Over the past 11 years, the competition has challenged both undergraduates and graduates, including Ph.D. students with real world applications in intelligent transportation systems, the military, and manufacturing automation. To date, teams from over 40 universities and colleges have participated. In this paper, we describe some of the applications of the technologies required by this competition, and discuss the educational benefits. The primary goal of the IGVC is to advance engineering education in intelligent vehicles and related technologies. The employment and professional networking opportunities created for students and industrial sponsors through a series of technical events over the three-day competition are highlighted. Finally, an assessment of the competition based on participant feedback is presented.

Systems integrated human engineering on the Navy's rapid acquisition of manufactured parts/test and integration facility

NASA Technical Reports Server (NTRS)

Gallaway, Glen R.

1987-01-01

Human Engineering in many projects is at best a limited support function. In this Navy project the Human Engineering function is an integral component of the systems design and development process. Human Engineering is a member of the systems design organization. This ensures that people considerations are: (1) identified early in the project; (2) accounted for in the specifications; (3) incorporated into the design; and (4) the tested product meets the needs and expectations of the people while meeting the overall systems requirements. The project exemplifies achievements that can be made by the symbiosis between systems designers, engineers and Human Engineering. This approach increases Human Engineering's effectiveness and value to a project because it becomes an accepted, contributing team member. It is an approach to doing Human Engineering that should be considered for most projects. The functional and organizational issues giving this approach strength are described.

Cultivation of students' engineering designing ability based on optoelectronic system course project

NASA Astrophysics Data System (ADS)

Cao, Danhua; Wu, Yubin; Li, Jingping

2017-08-01

We carry out teaching based on optoelectronic related course group, aiming at junior students majored in Optoelectronic Information Science and Engineering. " Optoelectronic System Course Project " is product-designing-oriented and lasts for a whole semester. It provides a chance for students to experience the whole process of product designing, and improve their abilities to search literature, proof schemes, design and implement their schemes. In teaching process, each project topic is carefully selected and repeatedly refined to guarantee the projects with the knowledge integrity, engineering meanings and enjoyment. Moreover, we set up a top team with professional and experienced teachers, and build up learning community. Meanwhile, the communication between students and teachers as well as the interaction among students are taken seriously in order to improve their team-work ability and communicational skills. Therefore, students are not only able to have a chance to review the knowledge hierarchy of optics, electronics, and computer sciences, but also are able to improve their engineering mindset and innovation consciousness.

Crusader solid propellant best technical approach

DOE Office of Scientific and Technical Information (OSTI.GOV)

Graves, V.; Bader, G.; Dolecki, M.

1995-12-01

The goal of the Solid Propellant Resupply Team is to develop Crusader system concepts capable of automatically handling 155mm projectiles and Modular Artillery Charges (MACs) based on system requirements. The system encompasses all aspects of handling from initial input into a resupply vehicle (RSV) to the final loading into the breech of the self-propelled howitzer (SPH). The team, comprised of persons from military and other government organizations, developed concepts for the overall vehicles as well as their interior handling components. An intermediate review was conducted on those components, and revised concepts were completed in May 1995. A concept evaluation wasmore » conducted on the finalized concepts, from both a systems level and a component level. The team`s Best Technical Approach (BTA) concept was selected from that evaluation. Both vehicles in the BTA have a front-engine configuration with the crew situated behind the engine-low in the vehicles. The SPH concept utilizes an automated reload port at the rear of the vehicle, centered high. The RSV transfer boom will dock with this port to allow automated ammunition transfer. The SPH rearm system utilizes fully redundant dual loaders. Active magazines are used for both projectiles and MACs. The SPH also uses a nonconventional tilted ring turret configuration to maximize the available interior volume in the vehicle. This configuration can be rearmed at any elevation angle but only at 0{degree} azimuth. The RSV configuration is similar to that of the SPH. The RSV utilizes passive storage racks with a pick-and-place manipulator for handling the projectiles and active magazines for the MACs. A telescoping transfer boom extends out the front of the vehicle over the crew and engine.« less

B-2 Systems Engineering Case Study

DTIC Science & Technology

2007-01-01

formal configuration freeze , an immediate refocus of the Task Teams was required. Within several days, the air vehicle task teams were conducting...39 3.3.3 Configuration Freeze ...1983 PDR 1 Oct 1982 Reconfiguration Feb 1983-Aug 1983 (LP3, LP4) Configuration Freeze July 1983 PDR 2 Mar-April 1984 CDR Dec 1986

Systematic Approach to the Development, Evolution, and Effectiveness of Integrated Product Development Teams (IPDTs)

DOE Office of Scientific and Technical Information (OSTI.GOV)

Margie Jeffs; R. Douglas Hamelin

Integrated Product Development Teams (IPDT) are a key component of any systems engineering (SE) application, but since they are formed primarily from technical considerations, many IPDTs are far less productive than they otherwise could be. By recognizing specific personality types and skill sets, a random group of 'technical' individuals can be structured to become a highly effective team capable of delivering much more than the sum of its members.

Case study: Comparison of motivation for achieving higher performance between self-directed and manager-directed aerospace engineering teams

NASA Astrophysics Data System (ADS)

Erlick, Katherine

"The stereotype of engineers is that they are not people oriented; the stereotype implies that engineers would not work well in teams---that their task emphasis is a solo venture and does not encourage social aspects of collaboration" (Miner & Beyerlein, 1999, p. 16). The problem is determining the best method of providing a motivating environment where design engineers may contribute within a team in order to achieve higher performance in the organization. Theoretically, self-directed work teams perform at higher levels. But, allowing a design engineer to contribute to the team while still maintaining his or her anonymity is the key to success. Therefore, a motivating environment must be established to encourage greater self-actualization in design engineers. The purpose of this study is to determine the favorable motivational environment for design engineers and describe the comparison between two aerospace design-engineering teams: one self-directed and the other manager directed. Following the comparison, this study identified whether self-direction or manager-direction provides the favorable motivational environment for operating as a team in pursuit of achieving higher performance. The methodology used in this research was the case study focusing on the team's levels of job satisfaction and potential for higher performance. The collection of data came from three sources, (a) surveys, (b) researcher observer journal and (c) collection of artifacts. The surveys provided information regarding personal behavior characteristics, potentiality for higher performance and motivational attributes. The researcher journal provided information regarding team dynamics, individual interaction, conflict and conflict resolution. The milestone for performance was based on the collection of artifacts from the two teams. The findings from this study illustrated that whether the team was manager-directed or self-directed does not appear to influence the needs and wants of the team members. The self-directed team was more motivated to learn their topic than was the manager-directed team, but they struggled with their path in following their vision whereas the manager-directed team kept their focus under the guidance of their manager. Finally, both teams are in fact effective; however specific circumstances may be an important objective when deciding to utilize either a self-directed or manager-directed team.

77 FR 58415 - Large Scale Networking (LSN); Joint Engineering Team (JET)

Federal Register 2010, 2011, 2012, 2013, 2014

2012-09-20

... NATIONAL SCIENCE FOUNDATION Large Scale Networking (LSN); Joint Engineering Team (JET) AGENCY: The Networking and Information Technology Research and Development (NITRD) National Coordination Office (NCO..._Engineering_Team_ (JET). SUMMARY: The JET, established in 1997, provides for information sharing among Federal...

78 FR 70076 - Large Scale Networking (LSN)-Joint Engineering Team (JET)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-22

... NATIONAL SCIENCE FOUNDATION Large Scale Networking (LSN)--Joint Engineering Team (JET) AGENCY: The Networking and Information Technology Research and Development (NITRD) National Coordination Office (NCO..._Engineering_Team_ (JET)#title. SUMMARY: The JET, established in 1997, provides for information sharing among...

Update on Risk Reduction Activities for a Liquid Advanced Booster for NASA's Space Launch System

NASA Technical Reports Server (NTRS)

Crocker, Andrew M.; Doering, Kimberly B; Meadows, Robert G.; Lariviere, Brian W.; Graham, Jerry B.

2015-01-01

The stated goals of NASA's Research Announcement for the Space Launch System (SLS) Advanced Booster Engineering Demonstration and/or Risk Reduction (ABEDRR) are to reduce risks leading to an affordable Advanced Booster that meets the evolved capabilities of SLS; and enable competition by mitigating targeted Advanced Booster risks to enhance SLS affordability. Dynetics, Inc. and Aerojet Rocketdyne (AR) formed a team to offer a wide-ranging set of risk reduction activities and full-scale, system-level demonstrations that support NASA's ABEDRR goals. For NASA's SLS ABEDRR procurement, Dynetics and AR formed a team to offer a series of full-scale risk mitigation hardware demonstrations for an affordable booster approach that meets the evolved capabilities of the SLS. To establish a basis for the risk reduction activities, the Dynetics Team developed a booster design that takes advantage of the flight-proven Apollo-Saturn F-1. Using NASA's vehicle assumptions for the SLS Block 2, a two-engine, F-1-based booster design delivers 150 mT (331 klbm) payload to LEO, 20 mT (44 klbm) above NASA's requirements. This enables a low-cost, robust approach to structural design. During the ABEDRR effort, the Dynetics Team has modified proven Apollo-Saturn components and subsystems to improve affordability and reliability (e.g., reduce parts counts, touch labor, or use lower cost manufacturing processes and materials). The team has built hardware to validate production costs and completed tests to demonstrate it can meet performance requirements. State-of-the-art manufacturing and processing techniques have been applied to the heritage F-1, resulting in a low recurring cost engine while retaining the benefits of Apollo-era experience. NASA test facilities have been used to perform low-cost risk-reduction engine testing. In early 2014, NASA and the Dynetics Team agreed to move additional large liquid oxygen/kerosene engine work under Dynetics' ABEDRR contract. Also led by AR, the objectives of this work are to demonstrate combustion stability and measure performance of a 500,000 lbf class Oxidizer-Rich Staged Combustion (ORSC) cycle main injector. A trade study was completed to investigate the feasibility, cost effectiveness, and technical maturity of a domestically produced Atlas V engine that could also potentially satisfy NASA SLS payload-to-orbit requirements via an advanced booster application. Engine physical dimensions and performance parameters resulting from this study provide the system level requirements for the ORSC risk reduction test article. The test article is scheduled to complete critical design review this fall and begin testing in 2017. Dynetics has also designed, developed, and built innovative tank and structure assemblies using friction stir welding to leverage recent NASA investments in manufacturing tools, facilities, and processes, significantly reducing development and recurring costs. The full-scale cryotank assembly was used to verify the structural design and prove affordable processes. Dynetics performed hydrostatic and cryothermal proof tests on the assembly to verify the assembly meets performance requirements. This paper will discuss the ABEDRR engine task and structures task achievements to date and the remaining effort through the end of the contract.

RT 164: Design and Development Tools for the Systems Engineering Experience Accelerator - Part 3

DTIC Science & Technology

2017-04-29

Investigator: Dr. Jon Wade, Stevens Institute of Technology Co-Principal Investigator: Dr. Doug Bodner, Georgia Institute of Technology Research Team...Defense Acquisition University: Yvette Rodriguez Georgia Institute of Technology : Jing Liu Stevens Institute of Technology : Dr. Richard Turner...Stevens Institute of Technology : Peizhu Zhang Sponsor: Office of the DASD (Systems Engineering) Report No. SERC-2017-TR-107

Sharing Planetary Exploration: The Education and Public Outreach Program for the NASA MESSENGER Mission to Orbit Mercury

NASA Astrophysics Data System (ADS)

Solomon, S. C.; Stockman, S.; Chapman, C. R.; Leary, J. C.; McNutt, R. L.

2003-12-01

The Education and Public Outreach (EPO) Program of the MESSENGER mission to the planet Mercury, supported by the NASA Discovery Program, is a full partnership between the project's science and engineering teams and a team of professionals from the EPO community. The Challenger Center for Space Science Education (CCSSE) and the Carnegie Academy for Science Education (CASE) are developing sets of MESSENGER Education Modules targeting grade-specific education levels across K-12. These modules are being disseminated through a MESSENGER EPO Website developed at Montana State University, an Educator Fellowship Program managed by CCSSE to train Fellows to conduct educator workshops, additional workshops planned for NASA educators and members of the Minority University - SPace Interdisciplinary Network (MU-SPIN), and existing inner-city science education programs (e.g., the CASE Summer Science Institute in Washington, D.C.). All lessons are mapped to national standards and benchmarks by MESSENGER EPO team members trained by the American Association for the Advancement of Science (AAAS) Project 2061, all involve user input and feedback and quality control by the EPO team, and all are thoroughly screened by members of the project science and engineering teams. At the college level, internships in science and engineering are provided to students at minority institutions through a program managed by MU-SPIN, and additional opportunities for student participation across the country are planned as the mission proceeds. Outreach efforts include radio spots (AAAS), museum displays (National Air and Space Museum), posters and traveling exhibits (CASE), general language books (AAAS), programs targeting underserved communities (AAAS, CCSSE, and MU-SPIN), and a documentary highlighting the scientific and technical challenges involved in exploring Mercury and how the MESSENGER team has been meeting these challenges. As with the educational elements, science and engineering team members are active partners in each of the public outreach efforts. MESSENGER fully leverages other NASA EPO programs, including the Solar System Exploration EPO Forum and the Solar System Ambassadors. The overarching goal of the MESSENGER EPO program is to convey the excitement of planetary exploration to students and the lay public throughout the nation.

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA Technical Reports Server (NTRS)

Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David

2006-01-01

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

First-Year Engineering Students' Portrayal of Engineering in a Proposed Museum Exhibit for Middle School Students

NASA Astrophysics Data System (ADS)

Mena, Irene B.; Diefes-Dux, Heidi A.

2012-04-01

Students' perceptions of engineering have been documented through studies involving interviews, surveys, and word associations that take a direct approach to asking students about various aspects of their understanding of engineering. Research on perceptions of engineering rarely focuses on how students would portray engineering to others. First-year engineering student teams proposed a museum exhibit, targeted to middle school students, to explore the question "What is engineering?" The proposals took the form of a poster. The overarching research question focuses on how these students would portray engineering to middle school students as seen through their museum exhibit proposals. A preliminary analysis was done on 357 posters to determine the overall engineering themes for the proposed museum exhibits. Forty of these posters were selected and, using open coding, more thoroughly analyzed to learn what artifacts/objects, concepts, and skills student teams associate with engineering. These posters were also analyzed to determine if there were any differences by gender composition of the student teams. Building, designing, and teamwork are skills the first-year engineering students link to engineering. Regarding artifacts, students mentioned those related to transportation and structures most often. All-male teams were more likely to focus on the idea of space and to mention teamwork and designing as engineering skills; equal-gender teams were more likely to focus on the multidisciplinary aspect of engineering. This analysis of student teams' proposals provides baseline data, positioning instructors to develop and assess instructional interventions that stretch students' self-exploration of engineering.

Liquid Hydrogen Fill

NASA Image and Video Library

2016-08-03

Inside a control building at NASA's Kennedy Space Center in Florida, Adam Swinger, cryogenic research engineer in the Exploration Research and Technology Directorate, communicates with team members during a test of the Ground Operations Demo Unit for liquid hydrogen. The system includes a 33,000 gallon liquid hydrogen storage tank with an internal cold heat exchanger supplied from a cryogenic refrigerator. The primary goal of the testing is to achieve a liquid hydrogen zero boil-off capability. The system was designed, installed and tested by a team of civil servants and contractors from the center's Cryogenic Test Laboratory, with support from engineers at NASA's Glenn Research Center in Cleveland and Stennis Space Center in Mississippi. It may be applicable for use by the Ground Systems Development and Operations Program at Launch Pad 39B.

78 FR 31592 - T-Mobile Usa, Inc., Core Fault Isolation Team, Engineering Division, Bethlehem, Pennsylvania...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-24

... DEPARTMENT OF LABOR Employment and Training Administration [TA-W-82,371] T-Mobile Usa, Inc., Core Fault Isolation Team, Engineering Division, Bethlehem, Pennsylvania; Notice of Affirmative Determination...., Core Fault Isolation Team, Engineering Division, Bethlehem, Pennsylvania (subject firm). The...

Developing the Next Generation of Science Data System Engineers

NASA Technical Reports Server (NTRS)

Moses, John F.; Behnke, Jeanne; Durachka, Christopher D.

2016-01-01

At Goddard, engineers and scientists with a range of experience in science data systems are needed to employ new technologies and develop advances in capabilities for supporting new Earth and Space science research. Engineers with extensive experience in science data, software engineering and computer-information architectures are needed to lead and perform these activities. The increasing types and complexity of instrument data and emerging computer technologies coupled with the current shortage of computer engineers with backgrounds in science has led the need to develop a career path for science data systems engineers and architects.The current career path, in which undergraduate students studying various disciplines such as Computer Engineering or Physical Scientist, generally begins with serving on a development team in any of the disciplines where they can work in depth on existing Goddard data systems or serve with a specific NASA science team. There they begin to understand the data, infuse technologies, and begin to know the architectures of science data systems. From here the typical career involves peermentoring, on-the-job training or graduate level studies in analytics, computational science and applied science and mathematics. At the most senior level, engineers become subject matter experts and system architect experts, leading discipline-specific data centers and large software development projects. They are recognized as a subject matter expert in a science domain, they have project management expertise, lead standards efforts and lead international projects. A long career development remains necessary not only because of the breadth of knowledge required across physical sciences and engineering disciplines, but also because of the diversity of instrument data being developed today both by NASA and international partner agencies and because multidiscipline science and practitioner communities expect to have access to all types of observational data.This paper describes an approach to defining career-path guidance for college-bound high school and undergraduate engineering students, junior and senior engineers from various disciplines.

Developing the Next Generation of Science Data System Engineers

NASA Astrophysics Data System (ADS)

Moses, J. F.; Durachka, C. D.; Behnke, J.

2015-12-01

At Goddard, engineers and scientists with a range of experience in science data systems are needed to employ new technologies and develop advances in capabilities for supporting new Earth and Space science research. Engineers with extensive experience in science data, software engineering and computer-information architectures are needed to lead and perform these activities. The increasing types and complexity of instrument data and emerging computer technologies coupled with the current shortage of computer engineers with backgrounds in science has led the need to develop a career path for science data systems engineers and architects. The current career path, in which undergraduate students studying various disciplines such as Computer Engineering or Physical Scientist, generally begins with serving on a development team in any of the disciplines where they can work in depth on existing Goddard data systems or serve with a specific NASA science team. There they begin to understand the data, infuse technologies, and begin to know the architectures of science data systems. From here the typical career involves peer mentoring, on-the-job training or graduate level studies in analytics, computational science and applied science and mathematics. At the most senior level, engineers become subject matter experts and system architect experts, leading discipline-specific data centers and large software development projects. They are recognized as a subject matter expert in a science domain, they have project management expertise, lead standards efforts and lead international projects. A long career development remains necessary not only because of the breath of knowledge required across physical sciences and engineering disciplines, but also because of the diversity of instrument data being developed today both by NASA and international partner agencies and because multi-discipline science and practitioner communities expect to have access to all types of observational data. This paper describes an approach to defining career-path guidance for college-bound high school and undergraduate engineering students, junior and senior engineers from various disciplines.

Photonics engineering: snapshot applications in healthcare, homeland security, agriculture, and industry

NASA Astrophysics Data System (ADS)

Sumriddetchkajorn, Sarun

2015-01-01

Throughout my experience in photonics engineering, this article shows that photonics is indeed a key technology enabler for enhancing our competitiveness. In particular, I snapshot the achievements of NECTEC research teams in implementing devices and systems suitable for healthcare, homeland security, agriculture, and industry.

Requirements Engineering in Building Climate Science Software

ERIC Educational Resources Information Center

Batcheller, Archer L.

2011-01-01

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling…

International Space Station Passive Thermal Control System Analysis, Top Ten Lessons-Learned

NASA Technical Reports Server (NTRS)

Iovine, John

2011-01-01

The International Space Station (ISS) has been on-orbit for over 10 years, and there have been numerous technical challenges along the way from design to assembly to on-orbit anomalies and repairs. The Passive Thermal Control System (PTCS) management team has been a key player in successfully dealing with these challenges. The PTCS team performs thermal analysis in support of design and verification, launch and assembly constraints, integration, sustaining engineering, failure response, and model validation. This analysis is a significant body of work and provides a unique opportunity to compile a wealth of real world engineering and analysis knowledge and the corresponding lessons-learned. The analysis lessons encompass the full life cycle of flight hardware from design to on-orbit performance and sustaining engineering. These lessons can provide significant insight for new projects and programs. Key areas to be presented include thermal model fidelity, verification methods, analysis uncertainty, and operations support.

Robotic Mining Competition - Awards Ceremony

NASA Image and Video Library

2018-05-18

NASA's 9th Annual Robotic Mining Competition concludes with an awards ceremony May 18, 2018, at the Apollo/Saturn V Center at the Kennedy Space Center Visitor Complex in Florida. The University of Alabama Team Astrobotics received first place for their Systems Engineering Paper. At left is retired NASA astronaut Jerry Ross. At right is Jonette Stecklein, lead systems engineering paper judge. More than 40 student teams from colleges and universities around the U.S. participated in the competition, May 14-18, by using their mining robots to dig in a supersized sandbox filled with BP-1, or simulated lunar soil, gravel and rocks, and participate in other competition requirements. The Robotic Mining Competition is a NASA Human Exploration and Operations Mission Directorate project designed to encourage students in science, technology, engineering and math, or STEM fields. The project provides a competitive environment to foster innovative ideas and solutions that could be used on NASA's deep space missions.

Robotic Mining Competition - Awards Ceremony

NASA Image and Video Library

2018-05-18

NASA's 9th Annual Robotic Mining Competition concludes with an awards ceremony May 18, 2018, at the Apollo/Saturn V Center at the Kennedy Space Center Visitor Complex in Florida. The team from The University of Akron received third place for their Systems Engineering Paper. At left is retired NASA astronaut Jerry Ross. At right is Jonette Stecklein, lead systems engineering paper judge. More than 40 student teams from colleges and universities around the U.S. participated in the competition, May 14-18, by using their mining robots to dig in a supersized sandbox filled with BP-1, or simulated lunar soil, gravel and rocks, and participate in other competition requirements. The Robotic Mining Competition is a NASA Human Exploration and Operations Mission Directorate project designed to encourage students in science, technology, engineering and math, or STEM fields. The project provides a competitive environment to foster innovative ideas and solutions that could be used on NASA's deep space missions.

How to renovate a 50-year-old wastewater treating plant: Part 1

DOE Office of Scientific and Technical Information (OSTI.GOV)

Hunter, M.L.

1996-01-01

How does an existing refinery cost-effectively renovate wastewater/stormwater treating systems to meet today`s environmental regulations and standards? Faced with solving this problem, Amoco`s Whiting Refinery developed a project team consisting of plant and operations engineers, corporate project and design engineers, contractors and vendors to map out a strategy to re-engineer the existing wastewater treating plant (WWTP) and auxiliary functions. This case history shows how an old refinery limited by existing equipment, building space, operation`s availability requirements and costs divided the project into several design phases. The design team used a proactive approach with empowerment responsibilities to solve construction, equipment usagemore » and regulatory problems throughout the project`s lifetime. Focusing on front-end planning and customer service (the refinery), team members applied value-based engineering designs to keep costs down, implemented safe work practices during construction, used HAZOP reviews to scrutinize proposed designs for operating and maintenance procedures, etc. The result has been the renovation of a 50-year-old WWTP completed under budget, ontime and in compliance with federal mandates.« less

NASA's Solar Dynamics Observatory (SDO): A Systems Approach to a Complex Mission

NASA Technical Reports Server (NTRS)

Ruffa, John A.; Ward, David K.; Bartusek, LIsa M.; Bay, Michael; Gonzales, Peter J.; Pesnell, William D.

2012-01-01

The Solar Dynamics Observatory (SDO) includes three advanced instruments, massive science data volume, stringent science data completeness requirements, and a custom ground station to meet mission demands. The strict instrument science requirements imposed a number of challenging drivers on the overall mission system design, leading the SDO team to adopt an integrated systems engineering presence across all aspects of the mission to ensure that mission science requirements would be met. Key strategies were devised to address these system level drivers and mitigate identified threats to mission success. The global systems engineering team approach ensured that key drivers and risk areas were rigorously addressed through all phases of the mission, leading to the successful SDO launch and on-orbit operation. Since launch, SDO's on-orbit performance has met all mission science requirements and enabled groundbreaking science observations, expanding our understanding of the Sun and its dynamic processes.

NASA's Solar Dynamics Observatory (SDO): A Systems Approach to a Complex Mission

NASA Technical Reports Server (NTRS)

Ruffa, John A.; Ward, David K.; Bartusek, Lisa M.; Bay, Michael; Gonzales, Peter J.; Pesnell, William D.

2012-01-01

The Solar Dynamics Observatory (SDO) includes three advanced instruments, massive science data volume, stringent science data completeness requirements, and a custom ground station to meet mission demands. The strict instrument science requirements imposed a number of challenging drivers on the overall mission system design, leading the SDO team to adopt an integrated systems engineering presence across all aspects of the mission to ensure that mission science requirements would be met. Key strategies were devised to address these system level drivers and mitigate identified threats to mission success. The global systems engineering team approach ensured that key drivers and risk areas were rigorously addressed through all phases of the mission, leading to the successful SDO launch and on-orbit operation. Since launch, SDO s on-orbit performance has met all mission science requirements and enabled groundbreaking science observations, expanding our understanding of the Sun and its dynamic processes.

PRACA Enhancement Pilot Study Report: Engineering for Complex Systems Program (formerly Design for Safety), DFS-IC-0006

NASA Technical Reports Server (NTRS)

Korsmeyer, David; Schreiner, John

2002-01-01

This technology evaluation report documents the findings and recommendations of the Engineering for Complex Systems Program (formerly Design for Safety) PRACA Enhancement Pilot Study of the Space Shuttle Program's (SSP's) Problem Reporting and Corrective Action (PRACA) System. A team at NASA Ames Research Center (ARC) performed this Study. This Study was initiated as a follow-on to the NASA chartered Shuttle Independent Assessment Team (SIAT) review (performed in the Fall of 1999) which identified deficiencies in the current PRACA implementation. The Pilot Study was launched with an initial qualitative assessment and technical review performed during January 2000 with the quantitative formal Study (the subject of this report) started in March 2000. The goal of the PRACA Enhancement Pilot Study is to evaluate and quantify the technical aspects of the SSP PRACA systems and recommend enhancements to address deficiencies and in preparation for future system upgrades.

A Framework of Working Across Disciplines in Early Design and R&D of Large Complex Engineered Systems

NASA Technical Reports Server (NTRS)

McGowan, Anna-Maria Rivas; Papalambros, Panos Y.; Baker, Wayne E.

2015-01-01

This paper examines four primary methods of working across disciplines during R&D and early design of large-scale complex engineered systems such as aerospace systems. A conceptualized framework, called the Combining System Elements framework, is presented to delineate several aspects of cross-discipline and system integration practice. The framework is derived from a theoretical and empirical analysis of current work practices in actual operational settings and is informed by theories from organization science and engineering. The explanatory framework may be used by teams to clarify assumptions and associated work practices, which may reduce ambiguity in understanding diverse approaches to early systems research, development and design. The framework also highlights that very different engineering results may be obtained depending on work practices, even when the goals for the engineered system are the same.

Industrial Adoption of Model-Based Systems Engineering: Challenges and Strategies

NASA Astrophysics Data System (ADS)

Maheshwari, Apoorv

As design teams are becoming more globally integrated, one of the biggest challenges is to efficiently communicate across the team. The increasing complexity and multi-disciplinary nature of the products are also making it difficult to keep track of all the information generated during the design process by these global team members. System engineers have identified Model-based Systems Engineering (MBSE) as a possible solution where the emphasis is placed on the application of visual modeling methods and best practices to systems engineering (SE) activities right from the beginning of the conceptual design phases through to the end of the product lifecycle. Despite several advantages, there are multiple challenges restricting the adoption of MBSE by industry. We mainly consider the following two challenges: a) Industry perceives MBSE just as a diagramming tool and does not see too much value in MBSE; b) Industrial adopters are skeptical if the products developed using MBSE approach will be accepted by the regulatory bodies. To provide counter evidence to the former challenge, we developed a generic framework for translation from an MBSE tool (Systems Modeling Language, SysML) to an analysis tool (Agent-Based Modeling, ABM). The translation is demonstrated using a simplified air traffic management problem and provides an example of a potential quite significant value: the ability to use MBSE representations directly in an analysis setting. For the latter challenge, we are developing a reference model that uses SysML to represent a generic infusion pump and SE process for planning, developing, and obtaining regulatory approval of a medical device. This reference model demonstrates how regulatory requirements can be captured effectively through model-based representations. We will present another case study at the end where we will apply the knowledge gained from both case studies to a UAV design problem.

MD-11 PCA - Research flight team photo

NASA Technical Reports Server (NTRS)

1995-01-01

On Aug. 30, 1995, a the McDonnell Douglas MD-11 transport aircraft landed equipped with a computer-assisted engine control system that has the potential to increase flight safety. In landings at NASA Dryden Flight Research Center, Edwards, California, on August 29 and 30, the aircraft demonstrated software used in the aircraft's flight control computer that essentially landed the MD-11 without a need for the pilot to manipulate the flight controls significantly. In partnership with McDonnell Douglas Aerospace (MDA), with Pratt & Whitney and Honeywell helping to design the software, NASA developed this propulsion-controlled aircraft (PCA) system following a series of incidents in which hydraulic failures resulted in the loss of flight controls. This new system enables a pilot to operate and land the aircraft safely when its normal, hydraulically-activated control surfaces are disabled. This August 29, 1995, photo shows the MD-11 team. Back row, left to right: Tim Dingen, MDA pilot; John Miller, MD-11 Chief pilot (MDA); Wayne Anselmo, MD-11 Flight Test Engineer (MDA); Gordon Fullerton, PCA Project pilot; Bill Burcham, PCA Chief Engineer; Rudey Duran, PCA Controls Engineer (MDA); John Feather, PCA Controls Engineer (MDA); Daryl Townsend, Crew Chief; Henry Hernandez, aircraft mechanic; Bob Baron, PCA Project Manager; Don Hermann, aircraft mechanic; Jerry Cousins, aircraft mechanic; Eric Petersen, PCA Manager (Honeywell); Trindel Maine, PCA Data Engineer; Jeff Kahler, PCA Software Engineer (Honeywell); Steve Goldthorpe, PCA Controls Engineer (MDA). Front row, left to right: Teresa Hass, Senior Project Management Analyst; Hollie Allingham (Aguilera), Senior Project Management Analyst; Taher Zeglum, PCA Data Engineer (MDA); Drew Pappas, PCA Project Manager (MDA); John Burken, PCA Control Engineer.

Model-Based Testability Assessment and Directed Troubleshooting of Shuttle Wiring Systems

NASA Technical Reports Server (NTRS)

Deb, Somnath; Domagala, Chuck; Shrestha, Roshan; Malepati, Venkatesh; Cavanaugh, Kevin; Patterson-Hine, Ann; Sanderfer, Dwight; Cockrell, Jim; Norvig, Peter (Technical Monitor)

2000-01-01

We have recently completed a pilot study on the Space shuttle wiring system commissioned by the Wiring Integrity Research (WIRe) team at NASA Ames Research Center, As the space shuttle ages, it is experiencing wiring degradation problems including arcing, chaffing insulation breakdown and broken conductors. A systematic and comprehensive test process is required to thoroughly test and quality assure (QA) the wiring systems. The NASA WIRe team recognized the value of a formal model based analysis for risk-assessment and fault coverage analysis. However. wiring systems are complex and involve over 50,000 wire segments. Therefore, NASA commissioned this pilot study with Qualtech Systems. Inc. (QSI) to explore means of automatically extracting high fidelity multi-signal models from wiring information database for use with QSI's Testability Engineering and Maintenance System (TEAMS) tool.

ADVANCED MANUFACTURING TEAM

NASA Image and Video Library

2016-03-17

JOHNNIE CLARK, BRIAN WEST, AND ZACK JONES OF MSFC’S ADVANCED MANUFACTURING TEAM, WITH MSFC’S XLINE SELECTIVE LASER MELTING SYSTEM. CURRENTLY ONE OF THE LARGEST METAL 3D PRINTERS, THE XLINE AT MARSHALL IS BEING USED TO DEVELOP AND CERTIFY NICKEL ALLOY 718 MATERIAL PROPERTIES AND LARGE MANUFACTURING TECH DEMOS FOR THE RS25 ENGINE AND THE COMMERCIAL CREWED VEHICLE PROJECTS.

[Hospital clinical engineer orientation and function in the maintenance system of hospital medical equipment].

PubMed

Li, Bin; Zheng, Yunxin; He, Dehua; Jiang, Ruiyao; Chen, Ying; Jing, Wei

2012-03-01

The quantity of medical equipment in hospital rise quickly recent year. It provides the comprehensive support to the clinical service. The maintenance of medical equipment becomes more important than before. It is necessary to study on the orientation and function of clinical engineer in medical equipment maintenance system. Refer to three grade health care system, the community doctors which is called General practitioner, play an important role as the gatekeeper of health care system to triage and cost control. The paper suggests that hospital clinical engineer should play similar role as the gatekeeper of medical equipment maintenance system which composed by hospital clinical engineer, manufacture engineer and third party engineer. The hospital clinical engineer should be responsible of guard a pass of medical equipment maintenance quality and cost control. As the gatekeeper, hospital clinical engineer should take the responsibility of "General engineer" and pay more attention to safety and health of medical equipment. The responsibility description and future transition? development of clinical engineer as "General Engineer" is discussed. More attention should be recommended to the team building of hospital clinical engineer as "General Engineer".

Europa Explorer Operational Scenarios Development

NASA Technical Reports Server (NTRS)

Lock, Robert E.; Pappalardo, Robert T.; Clark, Karla B.

2008-01-01

In 2007, NASA conducted four advanced mission concept studies for outer planets targets: Europa, Ganymede, Titan and Enceladus. The studies were conducted in close cooperation with the planetary science community. Of the four, the Europa Explorer Concept Study focused on refining mission options, science trades and implementation details for a potential flagship mission to Europa in the 2015 timeframe. A science definition team (SDT) was appointed by NASA to guide the study. A JPL-led engineering team worked closely with the science team to address 3 major focus areas: 1) credible cost estimates, 2) rationale and logical discussion of radiation risk and mitigation approaches, and 3) better definition and exploration of science operational scenario trade space. This paper will address the methods and results of the collaborative process used to develop Europa Explorer operations scenarios. Working in concert with the SDT, and in parallel with the SDT's development of a science value matrix, key mission capabilities and constraints were challenged by the science and engineering members of the team. Science goals were advanced and options were considered for observation scenarios. Data collection and return strategies were tested via simulation, and mission performance was estimated and balanced with flight and ground system resources and science priorities. The key to this successful collaboration was a concurrent development environment in which all stakeholders could rapidly assess the feasibility of strategies for their success in the full system context. Issues of science and instrument compatibility, system constraints, and mission opportunities were treated analytically and objectively leading to complementary strategies for observation and data return. Current plans are that this approach, as part of the system engineering process, will continue as the Europa Explorer Concept Study moves toward becoming a development project.

A systematic approach for introducing innovative product design in courses with engineering and nonengineering students.

PubMed

Patterson, P E

2007-01-01

In our new global economy, biomedical product development teams need to be even more innovative in an environment constrained by fewer resources with less time from concept to market. Teams are often comprised of individuals spread around the world. To simulate this setting, we revised an existing course to incorporate teams of on-campus and distance students, with each team including both engineers and other specialties. Through interactive lectures and projects, we presented a systematic approach to innovation that should be useful to engineers and non-engineers alike. Students found the course challenging and exciting, displaying an improved ability to work in distributed teams and in developing innovative design solutions.

NASA Planetary Science Summer School: Preparing the Next Generation of Planetary Mission Leaders

NASA Astrophysics Data System (ADS)

Budney, C. J.; Lowes, L. L.; Sohus, A.; Wheeler, T.; Wessen, A.; Scalice, D.

2010-12-01

Sponsored by NASA’s Planetary Science Division, and managed by the Jet Propulsion Laboratory, the Planetary Science Summer School prepares the next generation of engineers and scientists to participate in future solar system exploration missions. Participants learn the mission life cycle, roles of scientists and engineers in a mission environment, mission design interconnectedness and trade-offs, and the importance of teamwork. For this professional development opportunity, applicants are sought who have a strong interest and experience in careers in planetary exploration, and who are science and engineering post-docs, recent PhDs, and doctoral students, and faculty teaching such students. Disciplines include planetary science, geoscience, geophysics, environmental science, aerospace engineering, mechanical engineering, and materials science. Participants are selected through a competitive review process, with selections based on the strength of the application and advisor’s recommendation letter. Under the mentorship of a lead engineer (Dr. Charles Budney), students select, design, and develop a mission concept in response to the NASA New Frontiers Announcement of Opportunity. They develop their mission in the JPL Advanced Projects Design Team (Team X) environment, which is a cross-functional multidisciplinary team of professional engineers that utilizes concurrent engineering methodologies to complete rapid design, analysis and evaluation of mission concept designs. About 36 students participate each year, divided into two summer sessions. In advance of an intensive week-long session in the Project Design Center at JPL, students select the mission and science goals during a series of six weekly WebEx/telecons, and develop a preliminary suite of instrumentation and a science traceability matrix. Students assume both a science team and a mission development role with JPL Team X mentors. Once at JPL, students participate in a series of Team X project design sessions, during which their mentors aid them in finalizing their mission design and instrument suite, and in making the necessary trade-offs to stay within the cost cap. Tours of JPL facilities highlight the end-to-end life cycle of a mission. At week’s end, students present their Concept Study to a “proposal review board” of JPL scientists and engineers and NASA Headquarters executives, who feed back the strengths and weaknesses of their proposal and mission design. The majority of students come from top US universities with planetary science or engineering programs, such as Brown University, MIT, Georgia Tech, University of Colorado, Caltech, Stanford, University of Arizona, UCLA, and University of Michigan. Almost a third of Planetary Science Summer School alumni from the last 10 years of the program are currently employed by NASA or JPL. The Planetary Science Summer School is implemented by the JPL Education Office in partnership with JPL’s Team X Project Design Center.

Mercury Orbiter: Report of the Science Working Team

NASA Technical Reports Server (NTRS)

Belcher, John W.; Slavin, James A.; Armstrong, Thomas P.; Farquhar, Robert W.; Akasofu, Syun I.; Baker, Daniel N.; Cattell, Cynthia A.; Cheng, Andrew F.; Chupp, Edward L.; Clark, Pamela E.

1991-01-01

The results are presented of the Mercury Orbiter Science Working Team which held three workshops in 1988 to 1989 under the auspices of the Space Physics and Planetary Exploration Divisions of NASA Headquarters. Spacecraft engineering and mission design studies at the Jet Propulsion Lab were conducted in parallel with this effort and are detailed elsewhere. The findings of the engineering study, summarized herein, indicate that spin stabilized spacecraft carrying comprehensive particles and fields experiments and key planetology instruments in high elliptical orbits can survive and function in Mercury orbit without costly sun shields and active cooling systems.

A human factors systems approach to understanding team-based primary care: a qualitative analysis

PubMed Central

Mundt, Marlon P.; Swedlund, Matthew P.

2016-01-01

Background. Research shows that high-functioning teams improve patient outcomes in primary care. However, there is no consensus on a conceptual model of team-based primary care that can be used to guide measurement and performance evaluation of teams. Objective. To qualitatively understand whether the Systems Engineering Initiative for Patient Safety (SEIPS) model could serve as a framework for creating and evaluating team-based primary care. Methods. We evaluated qualitative interview data from 19 clinicians and staff members from 6 primary care clinics associated with a large Midwestern university. All health care clinicians and staff in the study clinics completed a survey of their communication connections to team members. Social network analysis identified key informants for interviews by selecting the respondents with the highest frequency of communication ties as reported by their teammates. Semi-structured interviews focused on communication patterns, team climate and teamwork. Results. Themes derived from the interviews lent support to the SEIPS model components, such as the work system (Team, Tools and Technology, Physical Environment, Tasks and Organization), team processes and team outcomes. Conclusions. Our qualitative data support the SEIPS model as a promising conceptual framework for creating and evaluating primary care teams. Future studies of team-based care may benefit from using the SEIPS model to shift clinical practice to high functioning team-based primary care. PMID:27578837

Using CASE tools to write engineering specifications

NASA Astrophysics Data System (ADS)

Henry, James E.; Howard, Robert W.; Iveland, Scott T.

1993-08-01

There are always a wide variety of obstacles to writing and maintaining engineering documentation. To combat these problems, documentation generation can be linked to the process of engineering development. The same graphics and communication tools used for structured system analysis and design (SSA/SSD) also form the basis for the documentation. The goal is to build a living document, such that as an engineering design changes, the documentation will `automatically' revise. `Automatic' is qualified by the need to maintain textual descriptions associated with the SSA/SSD graphics, and the need to generate new documents. This paper describes a methodology and a computer aided system engineering toolset that enables a relatively seamless transition into document generation for the development engineering team.

Systems Engineering Model for ART Energy Conversion

DOE Office of Scientific and Technical Information (OSTI.GOV)

Mendez Cruz, Carmen Margarita; Rochau, Gary E.; Wilson, Mollye C.

The near-term objective of the EC team is to establish an operating, commercially scalable Recompression Closed Brayton Cycle (RCBC) to be constructed for the NE - STEP demonstration system (demo) with the lowest risk possible. A systems engineering approach is recommended to ensure adequate requirements gathering, documentation, and mode ling that supports technology development relevant to advanced reactors while supporting crosscut interests in potential applications. A holistic systems engineering model was designed for the ART Energy Conversion program by leveraging Concurrent Engineering, Balance Model, Simplified V Model, and Project Management principles. The resulting model supports the identification and validation ofmore » lifecycle Brayton systems requirements, and allows designers to detail system-specific components relevant to the current stage in the lifecycle, while maintaining a holistic view of all system elements.« less

Low Cost Rapid Response Spacecraft, (LCRRS): A Research Project in Low Cost Spacecraft Design and Fabrication in a Rapid Prototyping Environment

NASA Technical Reports Server (NTRS)

Spremo, Stevan; Bregman, Jesse; Dallara, Christopher D.; Ghassemieh, Shakib M.; Hanratty, James; Jackson, Evan; Kitts, Christopher; Klupar, Pete; Lindsay, Michael; Ignacio, Mas;

Exploration Design Challenge 2014

NASA Image and Video Library

2014-04-25

Team Titan Shielding Systems poses with NASA Administrator Charles Bolden and Lockheed Martin CEO, Marillyn Hewson. Team Titan Shielding Systems was one of the semi-finalists in the Exploration Design Challenge. The goal of the Exploration Design Challenge is for students to research and design ways to protect astronauts from space radiation. The winner of the challenge was announced on April 25, 2014 at the USA Science and Engineering Festival at the Washington Convention Center in Washington, DC. Photo Credit: (NASA/Aubrey Gemignani)

Toward a Model-Based Approach for Flight System Fault Protection

NASA Technical Reports Server (NTRS)

Day, John; Meakin, Peter; Murray, Alex

2012-01-01

Use SysML/UML to describe the physical structure of the system This part of the model would be shared with other teams - FS Systems Engineering, Planning & Execution, V&V, Operations, etc., in an integrated model-based engineering environment Use the UML Profile mechanism, defining Stereotypes to precisely express the concepts of the FP domain This extends the UML/SysML languages to contain our FP concepts Use UML/SysML, along with our profile, to capture FP concepts and relationships in the model Generate typical FP engineering products (the FMECA, Fault Tree, MRD, V&V Matrices)

The 21st annual intelligent ground vehicle competition: robotists for the future

NASA Astrophysics Data System (ADS)

Theisen, Bernard L.

2013-12-01

The Intelligent Ground Vehicle Competition (IGVC) is one of four, unmanned systems, student competitions that were founded by the Association for Unmanned Vehicle Systems International (AUVSI). The IGVC is a multidisciplinary exercise in product realization that challenges college engineering student teams to integrate advanced control theory, machine vision, vehicular electronics and mobile platform fundamentals to design and build an unmanned system. Teams from around the world focus on developing a suite of dual-use technologies to equip ground vehicles of the future with intelligent driving capabilities. Over the past 21 years, the competition has challenged undergraduate, graduate and Ph.D. students with real world applications in intelligent transportation systems, the military and manufacturing automation. To date, teams from over 80 universities and colleges have participated. This paper describes some of the applications of the technologies required by this competition and discusses the educational benefits. The primary goal of the IGVC is to advance engineering education in intelligent vehicles and related technologies. The employment and professional networking opportunities created for students and industrial sponsors through a series of technical events over the fourday competition are highlighted. Finally, an assessment of the competition based on participation is presented.

The 20th annual intelligent ground vehicle competition: building a generation of robotists

NASA Astrophysics Data System (ADS)

Theisen, Bernard L.; Kosinski, Andrew

2013-01-01

The Intelligent Ground Vehicle Competition (IGVC) is one of four, unmanned systems, student competitions that were founded by the Association for Unmanned Vehicle Systems International (AUVSI). The IGVC is a multidisciplinary exercise in product realization that challenges college engineering student teams to integrate advanced control theory, machine vision, vehicular electronics and mobile platform fundamentals to design and build an unmanned system. Teams from around the world focus on developing a suite of dual-use technologies to equip ground vehicles of the future with intelligent driving capabilities. Over the past 20 years, the competition has challenged undergraduate, graduate and Ph.D. students with real world applications in intelligent transportation systems, the military and manufacturing automation. To date, teams from over 80 universities and colleges have participated. This paper describes some of the applications of the technologies required by this competition and discusses the educational benefits. The primary goal of the IGVC is to advance engineering education in intelligent vehicles and related technologies. The employment and professional networking opportunities created for students and industrial sponsors through a series of technical events over the four-day competition are highlighted. Finally, an assessment of the competition based on participation is presented.

A Team Building Model for Software Engineering Courses Term Projects

ERIC Educational Resources Information Center

Sahin, Yasar Guneri

2011-01-01

This paper proposes a new model for team building, which enables teachers to build coherent teams rapidly and fairly for the term projects of software engineering courses. Moreover, the model can also be used to build teams for any type of project, if the team member candidates are students, or if they are inexperienced on a certain subject. The…

Evaluating Machine Learning Classifiers for Hybrid Network Intrusion Detection Systems

DTIC Science & Technology

2015-03-26

7 VRT Vulnerability Research Team...and the Talos (formerly the Vulnerability Research Team ( VRT )) [7] 7 ruleset libraries are the two leading rulesets in use. Both libraries offer paid...rule sets to load for the signature-based IDS. Snort is selected as the IDS engine using the “ VRT and ET No/GPL” rule set. The total rule count in the

Research on Building Education and Workforce Capacity in Systems Engineering

DTIC Science & Technology

2012-01-31

Professional Ethics Since one goal of RT-19A is to understand how best to increase the number of schools offering systems engineering capstone courses...project evaluation plan  Developed and issued the request for proposals and selection process (an independent review team and rubric) for...faculty members from both institutions talk frequently to share ideas, compare progress and clarify any issues . Auburn recruited faculty only, so

Requirements, Verification, and Compliance (RVC) Database Tool

NASA Technical Reports Server (NTRS)

Rainwater, Neil E., II; McDuffee, Patrick B.; Thomas, L. Dale

2001-01-01

This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

Implementing large projects in software engineering courses

NASA Astrophysics Data System (ADS)

Coppit, David

2006-03-01

In software engineering education, large projects are widely recognized as a useful way of exposing students to the real-world difficulties of team software development. But large projects are difficult to put into practice. First, educators rarely have additional time to manage software projects. Second, classrooms have inherent limitations that threaten the realism of large projects. Third, quantitative evaluation of individuals who work in groups is notoriously difficult. As a result, many software engineering courses compromise the project experience by reducing the team sizes, project scope, and risk. In this paper, we present an approach to teaching a one-semester software engineering course in which 20 to 30 students work together to construct a moderately sized (15KLOC) software system. The approach combines carefully coordinated lectures and homeworks, a hierarchical project management structure, modern communication technologies, and a web-based project tracking and individual assessment system. Our approach provides a more realistic project experience for the students, without incurring significant additional overhead for the instructor. We present our experiences using the approach the last 2 years for the software engineering course at The College of William and Mary. Although the approach has some weaknesses, we believe that they are strongly outweighed by the pedagogical benefits.

Combustion devices technology team - An overview and status of STME-related activities

NASA Technical Reports Server (NTRS)

Tucker, P. K.; Croteau-Gillespie, Margie

1992-01-01

The Consortium for CFD applications in propulsion technology has been formed at NASA/Marshall Space Flight Center. The combustion devices technology team is one of the three teams that constitute the Consortium. While generally aiming to advance combustion devices technology for rocket propulsion, the team's efforts for the last 1 and 1/2 years have been focused on issues relating to the Space Transportation Main Engine (STME) nozzle. The nozzle design uses hydrogen-rich turbine exhaust to cool the wall in a film/dump scheme. This method of cooling presents challenges and associated risks for the nozzle designers and the engine/vehicle integrators. Within the nozzle itself, a key concern is the ability to effectively and efficiently film cool the wall. From the National Launch System vehicle base standpoint, there are concerns with dumping combustible gases at the nozzle exit and their potential adverse effects on the base thermal environment. The Combustion Team has developed and is implementing plans to use validated CFD tools to aid in risk mitigation for both areas.

Overview of the NCC

NASA Technical Reports Server (NTRS)

Liu, Nan-Suey

2001-01-01

A multi-disciplinary design/analysis tool for combustion systems is critical for optimizing the low-emission, high-performance combustor design process. Based on discussions between then NASA Lewis Research Center and the jet engine companies, an industry-government team was formed in early 1995 to develop the National Combustion Code (NCC), which is an integrated system of computer codes for the design and analysis of combustion systems. NCC has advanced features that address the need to meet designer's requirements such as "assured accuracy", "fast turnaround", and "acceptable cost". The NCC development team is comprised of Allison Engine Company (Allison), CFD Research Corporation (CFDRC), GE Aircraft Engines (GEAE), NASA Glenn Research Center (LeRC), and Pratt & Whitney (P&W). The "unstructured mesh" capability and "parallel computing" are fundamental features of NCC from its inception. The NCC system is composed of a set of "elements" which includes grid generator, main flow solver, turbulence module, turbulence and chemistry interaction module, chemistry module, spray module, radiation heat transfer module, data visualization module, and a post-processor for evaluating engine performance parameters. Each element may have contributions from several team members. Such a multi-source multi-element system needs to be integrated in a way that facilitates inter-module data communication, flexibility in module selection, and ease of integration. The development of the NCC beta version was essentially completed in June 1998. Technical details of the NCC elements are given in the Reference List. Elements such as the baseline flow solver, turbulence module, and the chemistry module, have been extensively validated; and their parallel performance on large-scale parallel systems has been evaluated and optimized. However the scalar PDF module and the Spray module, as well as their coupling with the baseline flow solver, were developed in a small-scale distributed computing environment. As a result, the validation of the NCC beta version as a whole was quite limited. Current effort has been focused on the validation of the integrated code and the evaluation/optimization of its overall performance on large-scale parallel systems.

NASA Planetary Science Summer School: Preparing the Next Generation of Planetary Mission Leaders

NASA Astrophysics Data System (ADS)

Lowes, L. L.; Budney, C. J.; Sohus, A.; Wheeler, T.; Urban, A.; NASA Planetary Science Summer School Team

2011-12-01

Sponsored by NASA's Planetary Science Division, and managed by the Jet Propulsion Laboratory, the Planetary Science Summer School prepares the next generation of engineers and scientists to participate in future solar system exploration missions. Participants learn the mission life cycle, roles of scientists and engineers in a mission environment, mission design interconnectedness and trade-offs, and the importance of teamwork. For this professional development opportunity, applicants are sought who have a strong interest and experience in careers in planetary exploration, and who are science and engineering post-docs, recent PhDs, and doctoral students, and faculty teaching such students. Disciplines include planetary science, geoscience, geophysics, environmental science, aerospace engineering, mechanical engineering, and materials science. Participants are selected through a competitive review process, with selections based on the strength of the application and advisor's recommendation letter. Under the mentorship of a lead engineer (Dr. Charles Budney), students select, design, and develop a mission concept in response to the NASA New Frontiers Announcement of Opportunity. They develop their mission in the JPL Advanced Projects Design Team (Team X) environment, which is a cross-functional multidisciplinary team of professional engineers that utilizes concurrent engineering methodologies to complete rapid design, analysis and evaluation of mission concept designs. About 36 students participate each year, divided into two summer sessions. In advance of an intensive week-long session in the Project Design Center at JPL, students select the mission and science goals during a series of six weekly WebEx/telecons, and develop a preliminary suite of instrumentation and a science traceability matrix. Students assume both a science team and a mission development role with JPL Team X mentors. Once at JPL, students participate in a series of Team X project design sessions, during which their mentors aid them in finalizing their mission design and instrument suite, and in making the necessary trade-offs to stay within the cost cap. Tours of JPL facilities highlight the end-to-end life cycle of a mission. At week's end, students present their Concept Study to a "proposal review board" of JPL scientists and engineers and NASA Headquarters executives, who feed back the strengths and weaknesses of their proposal and mission design. A survey of Planetary Science Summer School alumni administered in summer of 2011 provides information on the program's impact on students' career choices and leadership roles as they pursue their employment in planetary science and related fields. Preliminary results will be discussed during the session. Almost a third of the approximately 450 Planetary Science Summer School alumni from the last 10 years of the program are currently employed by NASA or JPL. The Planetary Science Summer School is implemented by the JPL Education Office in partnership with JPL's Team X Project Design Center.

Global engineering teams - a programme promoting teamwork in engineering design and manufacturing

NASA Astrophysics Data System (ADS)

Oladiran, M. T.; Uziak, J.; Eisenberg, M.; Scheffer, C.

2011-05-01

Engineering graduates are expected to possess various competencies categorised into hard and soft skills. The hard skills are acquired through specific coursework, but the soft skills are often treated perfunctorily. Global Engineering Teams (GET) is a programme that promotes project-oriented tasks in virtual student teams working in collaboration with industry partners. Teamwork is a major success factor for GET as students always work in groups of varying sizes. A questionnaire-based survey of the 2008 cohort of GET students was conducted to assess teamwork, communication and conflict resolution among group members. The results confirmed that deliverables are readily achieved in teams and communication was open. A challenge of using virtual teams is the availability of high-speed Internet access. The GET programme shows that it is possible to deliver engineering design and manufacturing via industry/university collaboration. The programme also facilitates multidisciplinary teamwork at an international level.

Aerospace Concurrent Engineering Design Teams: Current State, Next Steps and a Vision for the Future

NASA Technical Reports Server (NTRS)

Hihn, Jairus; Chattopadhyay, Debarati; Karpati, Gabriel; McGuire, Melissa; Borden, Chester; Panek, John; Warfield, Keith

2011-01-01

Over the past sixteen years, government aerospace agencies and aerospace industry have developed and evolved operational concurrent design teams to create novel spaceflight mission concepts and designs. These capabilities and teams, however, have evolved largely independently. In today's environment of increasingly complex missions with limited budgets it is becoming readily apparent that both implementing organizations and today's concurrent engineering teams will need to interact more often than they have in the past. This will require significant changes in the current state of practice. This paper documents the findings from a concurrent engineering workshop held in August 2010 to identify the key near term improvement areas for concurrent engineering capabilities and challenges to the long-term advancement of concurrent engineering practice. The paper concludes with a discussion of a proposed vision for the evolution of these teams over the next decade.

One more thing: Faculty response to increased emphasis on project teams in undergraduate engineering education

NASA Astrophysics Data System (ADS)

Hunter, Jane

Tenured and tenure-track faculty members at institutions of higher education, especially those at Research I institutions, are being asked to do more than ever before. With rapidly changing technology, significant decreases in public funding, the shift toward privately funded research, and the ever increasing expectations of students for an education that adequately prepares them for professional careers, engineering faculty are particularly challenged by the escalating demands on their time. In 1996, the primary accreditation organization for engineering programs (ABET) adopted new criteria that required, among other things, engineering programs to teach students to function on multidisciplinary teams and to communicate effectively. In response, most engineering programs utilize project teams as a strategy for teaching these skills. The purpose of this qualitative study of tenured and tenure track engineering faculty at a Research I institution in the southwestern United States was to explore the variety of ways in which the engineering faculty responded to the demands placed upon them as a result of the increased emphasis on project teams in undergraduate engineering education. Social role theory and organizational climate theory guided the study. Some faculty viewed project teams as an opportunity for students to learn important professional skills and to benefit from collaborative learning but many questioned the importance and feasibility of teaching teamwork skills and had concerns about taking time away from other essential fundamental material such as mathematics, basic sciences and engineering sciences. Although the administration of the College of Engineering articulated strong support for the use of project teams in undergraduate education, the prevailing climate did little to promote significant efforts related to effective utilization of project teams. Too often, faculty were unwilling to commit sufficient time or effort to make project teamwork a truly valuable learning opportunity because those efforts were not perceived to be valuable and were rarely rewarded. Few formal professional development opportunities were available and few incentives were in place to encourage other informal efforts to develop the necessary skills. Those who committed significant effort to project teams were challenged by concerns about team composition, student accountability and assigning individual grades for group teamwork.

Concurrent engineering: Spacecraft and mission operations system design

NASA Technical Reports Server (NTRS)

Landshof, J. A.; Harvey, R. J.; Marshall, M. H.

1994-01-01

Despite our awareness of the mission design process, spacecraft historically have been designed and developed by one team and then turned over as a system to the Mission Operations organization to operate on-orbit. By applying concurrent engineering techniques and envisioning operability as an essential characteristic of spacecraft design, tradeoffs can be made in the overall mission design to minimize mission lifetime cost. Lessons learned from previous spacecraft missions will be described, as well as the implementation of concurrent mission operations and spacecraft engineering for the Near Earth Asteroid Rendezvous (NEAR) program.

The Tools That Help Systems Engineering

NASA Technical Reports Server (NTRS)

Gamertsfelder, Jacob O.

2017-01-01

There are many tools that systems engineers use in today's space programs. In my time in the Commercial Crew Program I sought to improve one of the vital tools for the verification and validation team. This was my main project but only a small part of what I have done in the department. I have also had the chance to learn from the best and see actual hardware, this real world experience will help me be a better aerospace engineer when I enter the workforce. I look forward to seeing the Commercial Crew Program progress to launch.

A Matrix Approach to Software Process Definition

NASA Technical Reports Server (NTRS)

Schultz, David; Bachman, Judith; Landis, Linda; Stark, Mike; Godfrey, Sally; Morisio, Maurizio; Powers, Edward I. (Technical Monitor)

2000-01-01

The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

Team-Based Development of Medical Devices: An Engineering-Business Collaborative.

PubMed

Eberhardt, Alan W; Johnson, Ophelia L; Kirkland, William B; Dobbs, Joel H; Moradi, Lee G

2016-07-01

There is a global shift in the teaching methodology of science and engineering toward multidisciplinary, team-based processes. To meet the demands of an evolving technical industry and lead the way in engineering education, innovative curricula are essential. This paper describes the development of multidisciplinary, team-based learning environments in undergraduate and graduate engineering curricula focused on medical device design. In these programs, students actively collaborate with clinicians, professional engineers, business professionals, and their peers to develop innovative solutions to real-world problems. In the undergraduate senior capstone courses, teams of biomedical engineering (BME) and business students have produced and delivered numerous functional prototypes to satisfied clients. Pursuit of commercialization of devices has led to intellectual property (IP) disclosures and patents. Assessments have indicated high levels of success in attainment of student learning outcomes and student satisfaction with their undergraduate design experience. To advance these projects toward commercialization and further promote innovative team-based learning, a Master of Engineering (MEng) in Design and Commercialization was recently launched. The MEng facilitates teams of graduate students in engineering, life sciences, and business who engage in innovation-commercialization (IC) projects and coursework that take innovative ideas through research and development (R&D) to create marketable devices. The activities are structured with students working together as a "virtual company," with targeted outcomes of commercialization (license agreements and new start-ups), competitive job placement, and/or career advancement.

33 CFR 385.17 - Project Delivery Team.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 33 Navigation and Navigable Waters 3 2011-07-01 2011-07-01 false Project Delivery Team. 385.17... Processes § 385.17 Project Delivery Team. (a) In accordance with the procedures of the Corps of Engineers...,” the Corps of Engineers and the non-Federal sponsor shall form a Project Delivery Team to develop the...

33 CFR 385.17 - Project Delivery Team.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 33 Navigation and Navigable Waters 3 2013-07-01 2013-07-01 false Project Delivery Team. 385.17... Processes § 385.17 Project Delivery Team. (a) In accordance with the procedures of the Corps of Engineers...,” the Corps of Engineers and the non-Federal sponsor shall form a Project Delivery Team to develop the...

33 CFR 385.17 - Project Delivery Team.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 33 Navigation and Navigable Waters 3 2014-07-01 2014-07-01 false Project Delivery Team. 385.17... Processes § 385.17 Project Delivery Team. (a) In accordance with the procedures of the Corps of Engineers...,” the Corps of Engineers and the non-Federal sponsor shall form a Project Delivery Team to develop the...

33 CFR 385.17 - Project Delivery Team.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 33 Navigation and Navigable Waters 3 2010-07-01 2010-07-01 false Project Delivery Team. 385.17... Processes § 385.17 Project Delivery Team. (a) In accordance with the procedures of the Corps of Engineers...,” the Corps of Engineers and the non-Federal sponsor shall form a Project Delivery Team to develop the...

33 CFR 385.17 - Project Delivery Team.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 33 Navigation and Navigable Waters 3 2012-07-01 2012-07-01 false Project Delivery Team. 385.17... Processes § 385.17 Project Delivery Team. (a) In accordance with the procedures of the Corps of Engineers...,” the Corps of Engineers and the non-Federal sponsor shall form a Project Delivery Team to develop the...

Field-Reversed Configuration Power Plant Critical-Issue Scoping Study

DOE Office of Scientific and Technical Information (OSTI.GOV)

Santarius, J. F.; Mogahed, E. A.; Emmert, G. A.

A team from the Universities of Wisconsin, Washington, and Illinois performed an engineering scoping study of critical issues for field-reversed configuration (FRC) power plants. The key tasks for this research were (1) systems analysis for deuterium-tritium (D-T) FRC fusion power plants, and (2) conceptual design of the blanket and shield module for an FRC fusion core. For the engineering conceptual design of the fusion core, the project team focused on intermediate-term technology. For example, one decision was to use steele structure. The FRC systems analysis led to a fusion power plant with attractive features including modest size, cylindrical symmetry, goodmore » thermal efficiency (52%), relatively easy maintenance, and a high ratio of electric power to fusion core mass, indicating that it would have favorable economics.« less

Team Problem Solving Strategies with a Survey of These Methods Used by Faculty Members in Engineering Technology

ERIC Educational Resources Information Center

Marcus, Michael L.; Winters, Dixie L.

2004-01-01

Students from science, engineering, and technology programs should be able to work together as members of project teams to find solutions to technical problems. The exercise in this paper describes the methods actually used by a project team from a Biomedical Instrumentation Corporation in which scientists, technicians, and engineers from various…

Mission operations and command assurance: Flight operations quality improvements

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Potts, Sherrill S.; Witkowski, Mona M.

1994-01-01

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous solving among flight teams and provides continuous process improvement to reduce risk in mission operations by addressing human factors. The MO&CA task has evolved from participating as a member of the spacecraft team, to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

Effective Team Support: From Modeling to Software Agents

NASA Technical Reports Server (NTRS)

Remington, Roger W. (Technical Monitor); John, Bonnie; Sycara, Katia

2003-01-01

The purpose of this research contract was to perform multidisciplinary research between CMU psychologists, computer scientists and engineers and NASA researchers to design a next generation collaborative system to support a team of human experts and intelligent agents. To achieve robust performance enhancement of such a system, we had proposed to perform task and cognitive modeling to thoroughly understand the impact technology makes on the organization and on key individual personnel. Guided by cognitively-inspired requirements, we would then develop software agents that support the human team in decision making, information filtering, information distribution and integration to enhance team situational awareness. During the period covered by this final report, we made substantial progress in modeling infrastructure and task infrastructure. Work is continuing under a different contract to complete empirical data collection, cognitive modeling, and the building of software agents to support the teams task.

Integrating computer programs for engineering analysis and design

NASA Technical Reports Server (NTRS)

Wilhite, A. W.; Crisp, V. K.; Johnson, S. C.

1983-01-01

The design of a third-generation system for integrating computer programs for engineering and design has been developed for the Aerospace Vehicle Interactive Design (AVID) system. This system consists of an engineering data management system, program interface software, a user interface, and a geometry system. A relational information system (ARIS) was developed specifically for the computer-aided engineering system. It is used for a repository of design data that are communicated between analysis programs, for a dictionary that describes these design data, for a directory that describes the analysis programs, and for other system functions. A method is described for interfacing independent analysis programs into a loosely-coupled design system. This method emphasizes an interactive extension of analysis techniques and manipulation of design data. Also, integrity mechanisms exist to maintain database correctness for multidisciplinary design tasks by an individual or a team of specialists. Finally, a prototype user interface program has been developed to aid in system utilization.

A human factors systems approach to understanding team-based primary care: a qualitative analysis.

PubMed

Mundt, Marlon P; Swedlund, Matthew P

2016-12-01

Research shows that high-functioning teams improve patient outcomes in primary care. However, there is no consensus on a conceptual model of team-based primary care that can be used to guide measurement and performance evaluation of teams. To qualitatively understand whether the Systems Engineering Initiative for Patient Safety (SEIPS) model could serve as a framework for creating and evaluating team-based primary care. We evaluated qualitative interview data from 19 clinicians and staff members from 6 primary care clinics associated with a large Midwestern university. All health care clinicians and staff in the study clinics completed a survey of their communication connections to team members. Social network analysis identified key informants for interviews by selecting the respondents with the highest frequency of communication ties as reported by their teammates. Semi-structured interviews focused on communication patterns, team climate and teamwork. Themes derived from the interviews lent support to the SEIPS model components, such as the work system (Team, Tools and Technology, Physical Environment, Tasks and Organization), team processes and team outcomes. Our qualitative data support the SEIPS model as a promising conceptual framework for creating and evaluating primary care teams. Future studies of team-based care may benefit from using the SEIPS model to shift clinical practice to high functioning team-based primary care. © The Author 2016. Published by Oxford University Press. All rights reserved. For permissions, please e-mail: journals.permissions@oup.com.

An Exposure Prevention Plan for an Anhydrous Ammonia Handling System

NASA Technical Reports Server (NTRS)

Padolewski, Cathy L.; Bower, Amy; Ponikvar, Gary; Mellott, Ken

1997-01-01

In July of 1996, the Industrial Hygiene Team of the Environmental Management Office at NASA Lewis Research Center was contacted by the Space Station Program Office to conduct ammonia awareness training for a team of engineers and technicians. The team was tasked with assembling and operating an ammonia handling system for testing of a photovoltaic radiator at the NASA Plum Brook Station Space Power Facility. The ammonia handling system supports a radiator designed to radiate excess heat from a photovoltaic array module used to provide power to the International Space Station. The system would consist of a hazardous materials trailer equipped with an anhydrous ammonia tank, heater, accumulator, chiller, and flow bench. Meetings were held with representatives from the Space Station Program Office, the engineers and Plum Brook safety personnel. Guidance was also provided by representatives from Kennedy Space Center. Determinations were made concerning the locations and types of potential exposures and a plan was developed which included training, personal protective equipment, engineering controls and emergency response. Various organizations including the Plum Brook Safety Committee, the Lewis Environmental Management Office, the Test Readiness Review Board and the Program Office all had requirements that had to be met in order to satisfy themselves that all personnel involved in the operation of the system would be safe. What resulted was a comprehensive plan that provided more than adequate safety measures and succeeded in protecting all personnel from the hazards of the ammonia system. Testing of the photovoltaic radiator was successful and although ammonia leaks were detected and maintenance of the system was ongoing, no one was injured. It was felt that the training and controls in place allowed for a comfort level that did not interfere with the operations.

Design study to simulate the development of a commercial transportation system

NASA Technical Reports Server (NTRS)

1991-01-01

Seven teams of senior-level Aerospace Engineering undergraduates were given a Request for Proposals (RFP) for a design concept of a remotely piloted vehicle (RPV). The RPV designs were intended to simulate commercial transport aircraft within the model of 'Aeroworld.' The Aeroworld model was developed so that the RPV designs would be subject to many of the engineering problems and tradeoffs that dominate real-world commercial air transport designs, such as profitability, fuel efficiency, range vs. payload capabilities, and ease of production and maintenance. As part of the proposal, each team was required to construct a prototype and validate its design with a flight demonstration.

NASA's Information Power Grid: Large Scale Distributed Computing and Data Management

NASA Technical Reports Server (NTRS)

Johnston, William E.; Vaziri, Arsi; Hinke, Tom; Tanner, Leigh Ann; Feiereisen, William J.; Thigpen, William; Tang, Harry (Technical Monitor)

2001-01-01

Large-scale science and engineering are done through the interaction of people, heterogeneous computing resources, information systems, and instruments, all of which are geographically and organizationally dispersed. The overall motivation for Grids is to facilitate the routine interactions of these resources in order to support large-scale science and engineering. Multi-disciplinary simulations provide a good example of a class of applications that are very likely to require aggregation of widely distributed computing, data, and intellectual resources. Such simulations - e.g. whole system aircraft simulation and whole system living cell simulation - require integrating applications and data that are developed by different teams of researchers frequently in different locations. The research team's are the only ones that have the expertise to maintain and improve the simulation code and/or the body of experimental data that drives the simulations. This results in an inherently distributed computing and data management environment.

Teamed for Success: The Imperative for Aligning Systems Engineering and Life Cycle Logistics

DTIC Science & Technology

2013-02-01

January-February 2013 Kobren is director of the DAU Logistics & Sustainment Center, and the DoD Product Support Assessment Human Capital IPT lead...engineering colleagues, here are 10 key life-cycle logistics, product support, and system sustainment tenets to be cognizant of: Decisions You Make Will...and updates to the Life Cycle Sustainment Plan (LCSP). A vast majority of a weapon systems’ total ownership costs are determined by decisions made

Space systems engineering and risk management - joined at the hip

NASA Technical Reports Server (NTRS)

Rose, James R.

2004-01-01

This paper explores the separate skills and capabilities practiced until now, and the powerful coupling to be achieved, practically and effectively, in implementing a space mission, from inception (pre-phase A) to the end of Operations (phase E). The use of risk assessment techniques in balancing cost risk against performance risk, and the application of the systems engineering team in these trades, is the key to achieving this new implementation paradigm.

Technology Readiness Level Assessment Process as Applied to NASA Earth Science Missions

NASA Technical Reports Server (NTRS)

Leete, Stephen J.; Romero, Raul A.; Dempsey, James A.; Carey, John P.; Cline, Helmut P.; Lively, Carey F.

2015-01-01

Technology assessments of fourteen science instruments were conducted within NASA using the NASA Technology Readiness Level (TRL) Metric. The instruments were part of three NASA Earth Science Decadal Survey missions in pre-formulation. The Earth Systematic Missions Program (ESMP) Systems Engineering Working Group (SEWG), composed of members of three NASA Centers, provided a newly modified electronic workbook to be completed, with instructions. Each instrument development team performed an internal assessment of its technology status, prepared an overview of its instrument, and completed the workbook with the results of its assessment. A team from the ESMP SEWG met with each instrument team and provided feedback. The instrument teams then reported through the Program Scientist for their respective missions to NASA's Earth Science Division (ESD) on technology readiness, taking the SEWG input into account. The instruments were found to have a range of TRL from 4 to 7. Lessons Learned are presented; however, due to the competition-sensitive nature of the assessments, the results for specific missions are not presented. The assessments were generally successful, and produced useful results for the agency. The SEWG team identified a number of potential improvements to the process. Particular focus was on ensuring traceability to guiding NASA documents, including the NASA Systems Engineering Handbook. The TRL Workbook has been substantially modified, and the revised workbook is described.

The Social Construction of a Teacher Support Team: An Experience of University Lecturers' Professional Development in STEM

ERIC Educational Resources Information Center

Castro-Félix, Elvia; Daniels, Harry

2018-01-01

This paper focuses on understanding and exploring how a group of university engineering and science tutor educators learn and assimilate new conceptions about their role in the face of the forces of globalisation that are transforming the system of higher education. This research paper adopts the notion of the Teacher Support Team (TST) as…

Understanding the Effects of Team Cognition Associated with Complex Engineering Tasks: Dynamics of Shared Mental Models, Task-SMM, and Team-SMM

ERIC Educational Resources Information Center

Lee, Miyoung; Johnson, Tristan E.

2008-01-01

This study investigates how shared mental models (SMMs) change over time in teams of students in a manufacturing engineering course. A complex ill-structured project was given to each team. The objective of the team project was to analyze, test, and propose ways to improve their given manufactured product. Shared mental models were measured in…

Lunar Wormbot: Design and Development of a Ground Base Robotic Tunneling Worm for Operation in Harsh Environments

NASA Technical Reports Server (NTRS)

Boyles, Charles; Eledui, Emory; Gasser, Ben; Johnson, Josh; Long, Jay " Ben" ; Toy, Nathan; Murphy, Gloria

2011-01-01

From 1969 to 1972, the National Aeronautics and Space Administration (NASA) sent Apollo missions to the moon to conduct various exploration experiment. A few of the missions were directed to the study and sampling of moon soil, otherwise known as lunar regolith. The extent of the sample acquisition was limited due to the astronauts' limited ability to penetrate the moon's surface to a depth greater than three meters. However. the samples obtained were sufficient enough to provide key information pertaining to lunar regolith material properties that would further assist in future exploration endeavors. Analysis of the collected samples showed that the properties of lunar regolith may lead to knowledge of processed materials that will be beneficial for future human exploration or colonization. However, almost 40 years after the last Apollo mission, limited infonnation is known about regions underneath the moon's surface. Future lunar missions will require hardware that possesses the ability to burrow to greater depths in order to collect samples for subsequent analysis. During the summer of 2010, a team (Dr. Jessica Gaskin, Michael Kuhlman. Blaze Sanders, and Lafe Zabowski) from the NASA Robotics Academy at Marshall Space Flight Center (MSFC) was given the task of designing a robot to function as a soil collection and analysis device. Working with the National Space Science and Technology Center (NSSTC), the team was able to propose an initial design, build a prototype, and test the various subsystems of the prototype to be known as the "Lunar Wormbot" (LW). The NASA/NSSTC team then transferred the project to a University of Alabama in Huntsville (UAH) Mechanical and Aerospace Engineering (MAE) senior design class for further development. The UAH team was to utilize the NASA Systems Engineering Engine Design Process in the continuance of the Lunar Wormbot project. This process was implemented in order to coordinate the efforts of the team and guide the design of the project to ensure a high quality product that met requirements within the academic year timeframe. When the transition from the NASA NSSTC team to the UAH team occurred in August 2010, the scope and requirements were provided to the UAH team. The main objective for the UAH team was to design and fabricate a robotic burrowing prototype using peristaltic or earthworm-like motion with the purpose of collecting soil samples. The team was tasked with the design of a sub-system of the LW called the locomotive, or active, segment. Through the design process, the team extensively reviewed the requirements and functions to be performed of the LW, which led to the proposal of a final design. The present paper provides the details of the development of the design up to and including the Critical Design Review (CDR) of the Lunar Wormbot. This document briefly describes thc overall system and its function but primarily focuses on the design and implementation of the locomotive segment. Content presented includes: general design and system functionality, technical drawings, system analysis, manufacturing methods, and general project costs.

Essential elements in teaming: Creation of a team rubric

DOT National Transportation Integrated Search

2002-12-01

To further meet the needs of faculty and students at the University of Idaho in the College of Engineering, the Learning Environment Developers (a group of seven undergraduate mechanical engineering students known as Team LED) proposed to develop a r...

Developing Design and Management Skills for Senior Industrial Engineering Students

ERIC Educational Resources Information Center

Urbanic, R. J.

2011-01-01

In Canadian engineering institutions, a significant design experience must occur in the final year of study. In the Department of Industrial and Manufacturing Systems at the University of Windsor, unsolved, open ended projects sponsored by industrial partners from a variety of sectors are provided to the student teams in order for them to apply…

Exploring the Relationships among Creativity, Engineering Knowledge, and Design Team Interaction on Senior Engineering Design Projects

ERIC Educational Resources Information Center

Ibrahim, Badaruddin

2012-01-01

In the 21st century, engineers are expected to be creative and work collaboratively in teams to solve or design new products. Research in the past has shown how creativity and good team communication, together with knowledge, can impact the outcomes in the organization. The purpose of this study was to explore the relationships among creativity,…

Lockheed Martin Skunk Works Single Stage to Orbit/Reusable Launch Vehicle

NASA Technical Reports Server (NTRS)

1999-01-01

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Lockheed Martin's contribution to the program. The following is a summary of the Lockheed Martin Centers involved and work reviewed under their portion of the agreement: (1) Lockheed Martin Skunk Works - Vehicle Development, Operations Development, X-33 and RLV Systems Engineering, Manufacturing, Ground Operations, Reliability, Maintainability/Testability, Supportability, & Special Analysis Team, and X-33 Flight Assurance; (2) Lockheed Martin Technical Operations - Launch Support Systems, Ground Support Equipment, Flight Test Operations, and RLV Operations Development Support; (3) Lockheed Martin Space Operations - TAEM and A/L Guidance and Flight Control Design, Evaluation of Vehicle Configuration, TAEM and A/L Dispersion Analysis, Modeling and Simulations, Frequency Domain Analysis, Verification and Validation Activities, and Ancillary Support; (4) Lockheed Martin Astronautics-Denver - Systems Engineering, X-33 Development; (5) Sanders - A Lockheed Martin Company - Vehicle Health Management Subsystem Progress, GSS Progress; and (6) Lockheed Martin Michoud Space Systems - X-33 Liquid Oxygen (LOX) Tank, Key Challenges, Lessons Learned, X-33/RLV Composite Technology, Reusable Cyrogenic Insulation (RCI) and Vehicle Health Monitoring, Main Propulsion Systems (MPS), Structural Testing, X-33 System Integration and Analysis, and Cyrogenic Systems Operations.

The development of a tool to predict team performance.

PubMed

Sinclair, M A; Siemieniuch, C E; Haslam, R A; Henshaw, M J D C; Evans, L

2012-01-01

The paper describes the development of a tool to predict quantitatively the success of a team when executing a process. The tool was developed for the UK defence industry, though it may be useful in other domains. It is expected to be used by systems engineers in initial stages of systems design, when concepts are still fluid, including the structure of the team(s) which are expected to be operators within the system. It enables answers to be calculated for questions such as "What happens if I reduce team size?" and "Can I reduce the qualifications necessary to execute this process and still achieve the required level of success?". The tool has undergone verification and validation; it predicts fairly well and shows promise. An unexpected finding is that the tool creates a good a priori argument for significant attention to Human Factors Integration in systems projects. The simulations show that if a systems project takes full account of human factors integration (selection, training, process design, interaction design, culture, etc.) then the likelihood of team success will be in excess of 0.95. As the project derogates from this state, the likelihood of team success will drop as low as 0.05. If the team has good internal communications and good individuals in key roles, the likelihood of success rises towards 0.25. Even with a team comprising the best individuals, p(success) will not be greater than 0.35. It is hoped that these results will be useful for human factors professionals involved in systems design. Copyright © 2011 Elsevier Ltd and The Ergonomics Society. All rights reserved.

CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 4

DTIC Science & Technology

2007-04-01

and test markets . The decision fails the review, gets marked for adjustment, or passes. • The decision gets pushed out into the world. At this point...STD- 1521, Institute for Electrical and Electronics Engineers [IEEE]-15288). Myopically focused on early correctness, systems engineering can seem to...based on Mishkin Berteig’s experiences as an agile coach, consultant or trainer to teams and management in organizations across North America. From

Roster of NSAP (Navy Science Assistance Program) Field Team Members, Fiscal Years 1971-1986

DTIC Science & Technology

1985-08-05

CAPTOR Evaluation Program, NSWC. Current Job/Position: Operational Requirements Analyst for a new generation of mines. Current Address: Officer in...to NSAP Field Assignment: General Engineer; combat systems engineering on new ship design concepts, NSWC. Current Job/Position: Electronic Engineer...ADDRESS 12. REPORT DATE Naval Surface Weapons Center (Code D23) 5 August 1985 10901 New Hampshire Avenue 13. NUMBER OF PAGES Silver Spring, MD 20910

Advanced Methods for Aircraft Engine Thrust and Noise Benefits: Nozzle-Inlet Flow Analysis

NASA Technical Reports Server (NTRS)

Morgan, Morris H., III; Gilinsky, Mikhail M.

2004-01-01

In this project on the first stage (2000-Ol), we continued to develop the previous joint research between the Fluid Mechanics and Acoustics Laboratory (FM&AL) at Hampton University (HU) and the Jet Noise Team (JNT) at the NASA Langley Research Center (NASA LaRC). At the second stage (2001-03), FM&AL team concentrated its efforts on solving of problems of interest to Glenn Research Center (NASA GRC), especially in the field of propulsion system enhancement. The NASA GRC R&D Directorate and LaRC Hyper-X Program specialists in a hypersonic technology jointly with the FM&AL staff conducted research on a wide region of problems in the propulsion field as well as in experimental testing and theoretical and numerical simulation analyses for advanced aircraft and rocket engines. The last year the Hampton University School of Engineering & Technology was awarded the NASA grant, for creation of the Aeropropulsion Center, and the FM&AL is a key team of the project fulfillment responsible for research in Aeropropulsion and Acoustics (Pillar I). This work is supported by joint research between the NASA GRC/ FM&AL and the Institute of Mechanics at Moscow State University (IMMSU) in Russia under a CRDF grant. The main areas of current scientific interest of the FM&AL include an investigation of the proposed and patented advanced methods for aircraft engine thrust and noise benefits. This is the main subject of our other projects, of which one is presented. The last year we concentrated our efforts to analyze three main problems: (a) new effective methods fuel injection into the flow stream in air-breathing engines; (b) new re-circulation method for mixing, heat transfer and combustion enhancement in propulsion systems and domestic industry application; (c) covexity flow The research is focused on a wide regime of problems in the propulsion field as well as in experimental testing and theoretical and numerical simulation analyses for advanced aircraft and rocket engines (see, for example, Figures 4). The FM&AL Team uses analytical methods, numerical simulations and experimental tests at the Hampton University campus, NASA and IM/MSU.

A status of the Turbine Technology Team activities

NASA Technical Reports Server (NTRS)

Griffin, Lisa W.

1992-01-01

The recent activities of the Turbine Technology Team of the Consortium for Computational Fluid Dynamics (CFD) Application in Propulsion Technology is presented. The team consists of members from the government, industry, and universities. The goal of this team is to demonstrate the benefits to the turbine design process attainable through the application of CFD. This goal is to be achieved by enhancing and validating turbine design tools for improved loading and flowfield definition and loss prediction, and transferring the advanced technology to the turbine design process. In order to demonstrate the advantages of using CFD early in the design phase, the Space Transportation Main Engine (STME) turbines for the National Launch System (NLS) were chosen on which to focus the team's efforts. The Turbine Team activities run parallel to the STME design work.

40 CFR 1042.620 - Engines used solely for competition.

Code of Federal Regulations, 2013 CFR

2013-07-01

... section apply for new Category 1 engines and vessels built on or after January 1, 2009. (a) We may grant... limited to professional racing teams, professional racers, or other qualified racers. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers...

40 CFR 1042.620 - Engines used solely for competition.

Code of Federal Regulations, 2011 CFR

2011-07-01

... section apply for new Category 1 engines and vessels built on or after January 1, 2009. (a) We may grant... limited to professional racing teams, professional racers, or other qualified racers. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers...

40 CFR 1042.620 - Engines used solely for competition.

Code of Federal Regulations, 2012 CFR

2012-07-01

... section apply for new Category 1 engines and vessels built on or after January 1, 2009. (a) We may grant... limited to professional racing teams, professional racers, or other qualified racers. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers...

40 CFR 1042.620 - Engines used solely for competition.

Code of Federal Regulations, 2010 CFR

2010-07-01

... section apply for new Category 1 engines and vessels built on or after January 1, 2009. (a) We may grant... limited to professional racing teams, professional racers, or other qualified racers. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers...

40 CFR 1042.620 - Engines used solely for competition.

Code of Federal Regulations, 2014 CFR

2014-07-01

... section apply for new Category 1 engines and vessels built on or after January 1, 2009. (a) We may grant... limited to professional racing teams, professional racers, or other qualified racers. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers...

Risk Identification and Visualization in a Concurrent Engineering Team Environment

NASA Technical Reports Server (NTRS)

Hihn, Jairus; Chattopadhyay, Debarati; Shishko, Robert

2010-01-01

Incorporating risk assessment into the dynamic environment of a concurrent engineering team requires rapid response and adaptation. Generating consistent risk lists with inputs from all the relevant subsystems and presenting the results clearly to the stakeholders in a concurrent engineering environment is difficult because of the speed with which decisions are made. In this paper we describe the various approaches and techniques that have been explored for the point designs of JPL's Team X and the Trade Space Studies of the Rapid Mission Architecture Team. The paper will also focus on the issues of the misuse of categorical and ordinal data that keep arising within current engineering risk approaches and also in the applied risk literature.

The Vehicle Integrated Performance Analysis Experience: Reconnecting With Technical Integration

NASA Technical Reports Server (NTRS)

McGhee, D. S.

2006-01-01

Very early in the Space Launch Initiative program, a small team of engineers at MSFC proposed a process for performing system-level assessments of a launch vehicle. Aimed primarily at providing insight and making NASA a smart buyer, the Vehicle Integrated Performance Analysis (VIPA) team was created. The difference between the VIPA effort and previous integration attempts is that VIPA a process using experienced people from various disciplines, which focuses them on a technically integrated assessment. The foundations of VIPA s process are described. The VIPA team also recognized the need to target early detailed analysis toward identifying significant systems issues. This process is driven by the T-model for technical integration. VIPA s approach to performing system-level technical integration is discussed in detail. The VIPA process significantly enhances the development and monitoring of realizable project requirements. VIPA s assessment validates the concept s stated performance, identifies significant issues either with the concept or the requirements, and then reintegrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program s insight and review process. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful

Systems engineering implementation in the preliminary design phase of the Giant Magellan Telescope

NASA Astrophysics Data System (ADS)

Maiten, J.; Johns, M.; Trancho, G.; Sawyer, D.; Mady, P.

2012-09-01

Like many telescope projects today, the 24.5-meter Giant Magellan Telescope (GMT) is truly a complex system. The primary and secondary mirrors of the GMT are segmented and actuated to support two operating modes: natural seeing and adaptive optics. GMT is a general-purpose telescope supporting multiple science instruments operated in those modes. GMT is a large, diverse collaboration and development includes geographically distributed teams. The need to implement good systems engineering processes for managing the development of systems like GMT becomes imperative. The management of the requirements flow down from the science requirements to the component level requirements is an inherently difficult task in itself. The interfaces must also be negotiated so that the interactions between subsystems and assemblies are well defined and controlled. This paper will provide an overview of the systems engineering processes and tools implemented for the GMT project during the preliminary design phase. This will include requirements management, documentation and configuration control, interface development and technical risk management. Because of the complexity of the GMT system and the distributed team, using web-accessible tools for collaboration is vital. To accomplish this GMTO has selected three tools: Cognition Cockpit, Xerox Docushare, and Solidworks Enterprise Product Data Management (EPDM). Key to this is the use of Cockpit for managing and documenting the product tree, architecture, error budget, requirements, interfaces, and risks. Additionally, drawing management is accomplished using an EPDM vault. Docushare, a documentation and configuration management tool is used to manage workflow of documents and drawings for the GMT project. These tools electronically facilitate collaboration in real time, enabling the GMT team to track, trace and report on key project metrics and design parameters.

Team-Based Development of Medical Devices: An Engineering–Business Collaborative

PubMed Central

Eberhardt, Alan W.; Johnson, Ophelia L.; Kirkland, William B.; Dobbs, Joel H.; Moradi, Lee G.

2016-01-01

There is a global shift in the teaching methodology of science and engineering toward multidisciplinary, team-based processes. To meet the demands of an evolving technical industry and lead the way in engineering education, innovative curricula are essential. This paper describes the development of multidisciplinary, team-based learning environments in undergraduate and graduate engineering curricula focused on medical device design. In these programs, students actively collaborate with clinicians, professional engineers, business professionals, and their peers to develop innovative solutions to real-world problems. In the undergraduate senior capstone courses, teams of biomedical engineering (BME) and business students have produced and delivered numerous functional prototypes to satisfied clients. Pursuit of commercialization of devices has led to intellectual property (IP) disclosures and patents. Assessments have indicated high levels of success in attainment of student learning outcomes and student satisfaction with their undergraduate design experience. To advance these projects toward commercialization and further promote innovative team-based learning, a Master of Engineering (MEng) in Design and Commercialization was recently launched. The MEng facilitates teams of graduate students in engineering, life sciences, and business who engage in innovation-commercialization (IC) projects and coursework that take innovative ideas through research and development (R&D) to create marketable devices. The activities are structured with students working together as a “virtual company,” with targeted outcomes of commercialization (license agreements and new start-ups), competitive job placement, and/or career advancement. PMID:26902869

Improving Engineering Student Team Collaborative Discussions by Moving Them Online: An Investigation of Synchronous Chat and Face-to-Face Team Conversations

ERIC Educational Resources Information Center

Fowler, Robin Revette

2014-01-01

Collaborative learning, particularly in the context of team-based, project-based learning, is common in undergraduate engineering education and is associated with deeper learning and enhanced student motivation and retention. However, grouping students in teams for project-based learning sometimes has negative outcomes, which can include lowered…

Are your engineers talking to one another when they should?

PubMed

Sosa, Manuel E; Eppinger, Steven D; Rowles, Craig M

2007-11-01

Communication may not be on managers' minds at companies that design complex, highly engineered products, but it should be. When mistakes take place, it's often because product-component teams fail to talk. The consequences can be huge: Ford and Bridgestone Firestone lost billions by not coordinating the design of the Explorer with the design of its tires. The major delays and cost overruns involved in the development of Airbus's A380 "superjumbo"--which most likely led to the CEO's exit--were a result of unforeseen design incompatibilities. To help managers mitigate such problems, the authors present a new application of the design structure matrix, a project management tool that maps the flow of information and its impact on product development. Drawing on research into how Pratt & Whitney handled the development of the PW4098 jet engine, they have developed an approach that uncovers (a) areas where communication should be occurring but is not (unattended interfaces, usually bad) and (b) areas where communication is occurring but has not been planned for (unidentified interfaces, usually good). After finding the unattended and unidentified interfaces, the next step is to figure out the causes of the critical ones. If a significant number of unattended interfaces cross organizational boundaries, executives may need to redraw organizational lines. Executives can then manage the remaining critical interfaces by extending the responsibilities of existing integration teams (those responsible for cross-system aspects, such as a jet engine's fuel economy) to include supervising the interaction, by dedicating teams to specific interfaces, or by formally charging teams already involved with the interfaces to oversee them. Finally, it's important to ensure that the teams are working with compatible design equipment; inconsistencies between CAD tools have cost Airbus dearly.

The Tsunami Project: Integrating engineering, natural and social sciences into post-tsunami surveys

NASA Astrophysics Data System (ADS)

McAdoo, B. G.; Goff, J. R.; Fritz, H. M.; Cochard, R.; Kong, L. S.

2009-12-01

Complexities resulting from recent tsunamis in the Solomon Islands (2007), Java (2006) and Sumatra (2004, 2005) have demonstrated the need for an integrated, interdisciplinary team of engineers, natural and social scientists to better understand the nature of the disaster. Documenting the complex interactions in the coupled human-environment system necessitate a coordinated, interdisciplinary approach that combines the strengths of engineering, geoscience, ecology and social science. Engineers, modelers and geoscientists untangle the forces required to leave an imprint of a tsunami in the geologic record. These same forces affect ecosystems that provide services from buffers to food security; therefore coastal ecologists play a vital role. It is also crucial to understand the social structures that contribute to disasters, so local or regional policy experts, planners, economists, etc. should be included. When these experts arrive in a disaster area as part of an Interdisciplinary Tsunami Survey Team, the interactions between the systems can be discussed in the field, and site-specific data can be collected. A diverse team in the field following a tsunami shares critical resources and discoveries in real-time, making the survey more efficient. Following the 2006 Central Java earthquake and tsunami, civil engineers covered broad areas quickly, collecting ephemeral water level data and communicating areas of interest to the geologists, who would follow to do the slower sediment data collection. The 2007 Solomon Islands earthquake and tsunami caused extensive damage to the coral reef, which highlighting the need to have an ecologist on the team who was able to identify species and their energy tolerance. Rather than diluting the quality of post-tsunami data collection, this approach in fact strengthens it- engineers and geoscientists no longer have to indentify coral or mangrove species, nor do ecologists evaluate the velocity of a wave as it impacted a forested coastline. Interviews, a core element of post-tsunami surveys and which most US academic institutions require human-subject training to complete, can be undertaken by social scientists trained to ask pertinent questions to both the natural scientists and engineers, and those that will illuminate the underlying weaknesses of the social institutions that contributed to the magnitude of the disaster. Data collected by interdisciplinary teams provides baseline data that can set the redevelopment process off on the right track. Geoscientists constrain the location, frequency and magnitude of hazards, and how they affect the landscape. Ecologists document the interaction of hazards with ecosystems and evaluate their risk reduction role. Engineers and modelers constrain the effects of a hazard on the built environment. A coupled human-environment approach at the intersection of the physical, ecological and the built environments provides the right kind of data decision makers need to build back better in the most ecologically and economically sustainable manner.

Exploration Medical System Technical Development

NASA Technical Reports Server (NTRS)

McGuire, K.; Middour, C.; Cerro, J.; Burba, T.; Hanson, A.; Reilly, J.; Mindock, J.

2017-01-01

The Exploration Medical Capability (ExMC) Element systems engineering goals include defining the technical system needed to implement exploration medical capabilities for Mars. This past year, scenarios captured in the medical system concept of operations laid the foundation for systems engineering technical development work. The systems engineering team analyzed scenario content to identify interactions between the medical system, crewmembers, the exploration vehicle, and the ground system. This enabled the definition of functions the medical system must provide and interfaces to crewmembers and other systems. These analyses additionally lead to the development of a conceptual medical system architecture. The work supports the ExMC community-wide understanding of the functional exploration needs to be met by the medical system, the subsequent development of medical system requirements, and the system verification and validation approach utilizing terrestrial analogs and precursor exploration missions.

Design of a vibration isolation system for a cycle ergometer to be used onboard the Space Shuttle

NASA Technical Reports Server (NTRS)

Pearson, Lillian; Tait, Steven; Trevino, Maurice

1991-01-01

Low frequency vibrations generated during exercise using the cycle ergometer onboard the Space Shuttle are disrupting sensitive microgravity experiments. The design team is asked by NASA/USRA to generate alternatives for the design of a vibration isolation system for the cycle ergometer. It is the design team's objective to present alternative designs and a problem solution for a vibration isolation system for an exercise cycle ergometer to be used onboard the Space Shuttle. In the development of alternative designs, the design team emphasizes passive systems as opposed to active control systems. This decision is made because the team feels that passive systems are less complex than active control systems, external energy sources are not required, and mass is reduced due to the lack of machinery such as servomotors or compressors typical of active control systems. Eleven alternative designs are developed by the design team. From these alternatives, three active control systems are included to compare the benefits of active and passive systems. Also included in the alternatives is an isolation system designed by an independent engineer that was acquired late in the project. The eight alternatives using passive isolation systems are narrowed down by selection criteria to four considered to be the most promising by the design team. A feasibility analysis is performed on these four passive isolation systems. Based on the feasibility analysis, a final design solution is chosen and further developed. From the development of the design, the design team has concluded that passive systems are not effective at isolating vibrations for the low frequencies considered for this project. Recommendations are made for guidelines of passive isolation design and application of such systems.

Piloting Telepresence-Enabled Education and Outreach Programs from a UNOLS Ship - Live Interactive Broadcasts from the R/V Endeavor

NASA Astrophysics Data System (ADS)

Pereira, M.; Coleman, D.; Donovan, S.; Sanders, R.; Gingras, A.; DeCiccio, A.; Bilbo, E.

2016-02-01

The University of Rhode Island's R/V Endeavor was recently equipped with a new satellite telecommunication system and a telepresence system to enable live ship-to-shore broadcasts and remote user participation through the Inner Space Center. The Rhode Island Endeavor Program, which provides state-funded ship time to support local oceanographic research and education, funded a 5-day cruise off the Rhode Island coast that involved a multidisciplinary team of scientists, engineers, students, educators and video producers. Using two remotely operated vehicle (ROV) systems, several dives were conducted to explore various shipwrecks including the German WWII submarine U-853. During the cruise, a team of URI ocean engineers supported ROV operations and performed engineering tests of a new manipulator. Colleagues from the United States Coast Guard Academy operated a small ROV to collect imagery and environmental data around the wreck sites. Additionally, a team of engineers and oceanographers from URI tested a new acoustic sound source and small acoustic receivers developed for a fish tracking experiment. The video producers worked closely with the participating scientists, students and two high school science teachers to communicate the oceanographic research during live educational broadcasts streamed into Rhode Island classrooms, to the public Internet, and directly to Rhode Island Public Television. This work contributed to increasing awareness of possible career pathways for the Rhode Island K-12 population, taught about active oceanographic research projects, and engaged the public in scientific adventures at sea. The interactive nature of the broadcasts included live responses to questions submitted online and live updates and feedback using social media tools. This project characterizes the power of telepresence and video broadcasting to engage diverse learners and exemplifies innovative ways to utilize social media and the Internet to draw a varied audience.

Linking First-Year and Senior Engineering Design Teams: Engaging Early Academic Career Students in Engineering Design

ERIC Educational Resources Information Center

Fox, Garey A.; Weckler, Paul; Thomas, Dan

2015-01-01

In Biosystems Engineering at Oklahoma State University, senior design is a two semester course in which students work on real-world projects provided by clients. First-year (freshmen and trans­fer) students enroll in an introductory engineering course. Historically, these students worked on a team-based analysis project, and the engineering design…

Atmospheric Risk Assessment for the Mars Science Laboratory Entry, Descent, and Landing System

NASA Technical Reports Server (NTRS)

Chen, Allen; Vasavada, Ashwin; Cianciolo, Alicia; Barnes, Jeff; Tyler, Dan; Hinson, David; Lewis, Stephen

2010-01-01

In 2012, the Mars Science Laboratory (MSL) mission will pioneer the next generation of robotic Entry, Descent, and Landing (EDL) systems, by delivering the largest and most capable rover to date to the surface of Mars. As with previous Mars landers, atmospheric conditions during entry, descent, and landing directly impact the performance of MSL's EDL system. While the vehicle's novel guided entry system allows it to "fly out" a range of atmospheric uncertainties, its trajectory through the atmosphere creates a variety of atmospheric sensitivities not present on previous Mars entry systems and landers. Given the mission's stringent landing capability requirements, understanding the atmosphere state and spacecraft sensitivities takes on heightened importance. MSL's guided entry trajectory differs significantly from recent Mars landers and includes events that generate different atmospheric sensitivities than past missions. The existence of these sensitivities and general advancement in the state of Mars atmospheric knowledge has led the MSL team to employ new atmosphere modeling techniques in addition to past practices. A joint EDL engineering and Mars atmosphere science and modeling team has been created to identify the key system sensitivities, gather available atmospheric data sets, develop relevant atmosphere models, and formulate methods to integrate atmosphere information into EDL performance assessments. The team consists of EDL engineers, project science staff, and Mars atmospheric scientists from a variety of institutions. This paper provides an overview of the system performance sensitivities that have driven the atmosphere modeling approach, discusses the atmosphere data sets and models employed by the team as a result of the identified sensitivities, and introduces the tools used to translate atmospheric knowledge into quantitative EDL performance assessments.

The P-38 Lightning Aircraft: Lessons Learned for Future Weapon Systems Development

DTIC Science & Technology

2010-04-01

PMBOK TEL \\ u.s. WER List of ~cronyms iv Brake Horse Power Design-Build Team District of Columbia Department of Defense Department of...record. Despite unresolved issues like the flap and brake system problems and limited test hours, on 11 February 1939, Lieutenant Kelsey flew the XP-38...engine, giving the P-3 8 engines a 1425 brake horse power (BHP)22 rating. However, limitations of the integral wing leading edge intercoolers23 could

Issues in NASA Program and Project Management: Focus on Project Planning and Scheduling

NASA Technical Reports Server (NTRS)

Hoffman, Edward J. (Editor); Lawbaugh, William M. (Editor)

1997-01-01

Topics addressed include: Planning and scheduling training for working project teams at NASA, overview of project planning and scheduling workshops, project planning at NASA, new approaches to systems engineering, software reliability assessment, and software reuse in wind tunnel control systems.

A Software Tool for Integrated Optical Design Analysis

NASA Technical Reports Server (NTRS)

Moore, Jim; Troy, Ed; DePlachett, Charles; Montgomery, Edward (Technical Monitor)

2001-01-01

Design of large precision optical systems requires multi-disciplinary analysis, modeling, and design. Thermal, structural and optical characteristics of the hardware must be accurately understood in order to design a system capable of accomplishing the performance requirements. The interactions between each of the disciplines become stronger as systems are designed lighter weight for space applications. This coupling dictates a concurrent engineering design approach. In the past, integrated modeling tools have been developed that attempt to integrate all of the complex analysis within the framework of a single model. This often results in modeling simplifications and it requires engineering specialist to learn new applications. The software described in this presentation addresses the concurrent engineering task using a different approach. The software tool, Integrated Optical Design Analysis (IODA), uses data fusion technology to enable a cross discipline team of engineering experts to concurrently design an optical system using their standard validated engineering design tools.

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world-class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in-house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software-related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.

Agile Software Teams: How They Engage with Systems Engineering on DoD Acquisition Programs

DTIC Science & Technology

2014-07-01

under Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineer- ing Institute, a federally funded...issues that would preclude or limit the use of Agile methods within the DoD” [Broadus 2013]. As operational tempos increase and programs fight to...environment in which it operates . This makes software different from other disciplines that have toleranc- es, generally resulting in software engineering

Acoustics and Thrust of Separate Flow Exhaust Nozzles With Mixing Devices Investigated for High Bypass Ratio Engines

NASA Technical Reports Server (NTRS)

Saiyed, Naseem H.

2000-01-01

Typical installed separate-flow exhaust nozzle system. The jet noise from modern turbofan engines is a major contributor to the overall noise from commercial aircraft. Many of these engines use separate nozzles for exhausting core and fan streams. As a part of NASA s Advanced Subsonic Technology (AST) program, the NASA Glenn Research Center at Lewis Field led an experimental investigation using model-scale nozzles in Glenn s Aero-Acoustic Propulsion Laboratory. The goal of the investigation was to develop technology for reducing the jet noise by 3 EPNdB. Teams of engineers from Glenn, the NASA Langley Research Center, Pratt & Whitney, United Technologies Research Corporation, the Boeing Company, GE Aircraft Engines, Allison Engine Company, and Aero Systems Engineering contributed to the planning and implementation of the test.

Developing teamwork skills in capstone design courses.

PubMed

Goldberg, Jay

2010-01-01

The majority of our biomedical engineering graduates will eventually work in an industry where they will be part of multidisciplinary teams that use the collective skills, expertise, experience, and training of each team member. Diversity within these teams provides different perspectives, opinions, and ways of viewing problems, leading to a larger set of potential solutions. Successful careers require engineers to be able to function on multidisciplinary teams.

Hurricane Hugo briefing

NASA Astrophysics Data System (ADS)

Bush, Susan M.

The effects of Hurricane Hugo could have been much worse, in terms of lives lost and structural damage, according to postdisaster study teams. As part of the National Research Council's Committee on Natural Disasters, teams were sent to the disaster sites almost immediately after Hugo struck on September 18.Meteorologists, wind engineers, coastal geologists, civil engineers, structural engineers, and other members of the study teams presented their findings at a briefing held November 28 in Washington, D.C.

Implementation of activity-based costing (ABC) to drive cost reduction efforts in a semiconductor manufacturing operation

NASA Astrophysics Data System (ADS)

Naguib, Hussein; Bol, Igor I.; Lora, J.; Chowdhry, R.

1994-09-01

This paper presents a case study on the implementation of ABC to calculate the cost per wafer and to drive cost reduction efforts for a new IC product line. The cost reduction activities were conducted through the efforts of 11 cross-functional teams which included members of the finance, purchasing, technology development, process engineering, equipment engineering, production control, and facility groups. The activities of these cross functional teams were coordinated by a cost council. It will be shown that these activities have resulted in a 57% reduction in the wafer manufacturing cost of the new product line. Factors contributed to successful implementation of an ABC management system are discussed.

Team science of nursing, engineering, statistics, and practitioner in the development of a robotic reflexology device.

PubMed

Wyatt, Gwen; Sikorskii, Alla; Bush, Tamara Reid; Mukherjee, Ranjan

2010-01-01

The purpose of this article is to share the lessons learned in forming an interdisciplinary team that implements a team science approach to integrative medicine (IM) research. The disciplines of nursing, statistics, and engineering, along with consultants and a reflexology practitioner, formed this university-based team to conceptualize and develop a prototype robotic device for reflexology for breast cancer patients. The nurse investigator contributed the intervention background and access to the population; the statistician guided the team thinking on factors that needed to be controlled for; the engineers provided the expertise in device design and development; consultants facilitated the team's thinking in new directions; and the reflexology practitioner prescribed the protocol. We discuss the contributions and achievements of each discipline, as well as the challenges, and share the team experiences with the intent to help guide the formation of new IM teams that promote a conducive atmosphere for carrying out cutting-edge IM research and advancing the science.

Brian Bush | NREL

Science.gov Websites

W Bush Photo of Brian Bush Brian Bush Researcher VI-Systems Engineering Brian.Bush@nrel.gov | 303 -384-7472 Orcid ID http://orcid.org/0000-0003-2864-7028 Brian W Bush is a member of the Systems Modeling team within the Systems Modeling & Geospatial Data Science Group in the Strategic Energy

Using an Undergraduate Materials Research Project to Foster Multidisciplinary Teaming Skills

ERIC Educational Resources Information Center

Newell, James A.; Cleary, Doug D.

2004-01-01

This paper describes the use of undergraduate materials multidisciplinary research projects as a means of addressing the growing industrial demand for graduates experienced in working in multidisciplinary teams. It includes a detailed description of a project in which a multidisciplinary team of chemical engineering and civil engineering students…

Investigating Team Cohesion in COCOMO II.2000

ERIC Educational Resources Information Center

Snowdeal-Carden, Betty A.

2013-01-01

Software engineering is team oriented and intensely complex, relying on human collaboration and creativity more than any other engineering discipline. Poor software estimation is a problem that within the United States costs over a billion dollars per year. Effective measurement of team cohesion is foundationally important to gain accurate…

A Brief Survey of the Team Software ProcessSM (TSPSM)

DTIC Science & Technology

2011-10-24

spent more than 20 years in industry as a software engineer, system designer, project leader, and development manager working on control systems...InnerWorkings, Inc. Instituto Tecnologico y de Estudios Superiores de Monterrey Siemens AG SILAC Ingenieria de Software S.A. de C.V

Solar Stirling system development

NASA Technical Reports Server (NTRS)

Stearns, J. W., Jr.; Won, Y. S.; Poon, P. T.; Das, R.; Chow, E. Y.

1979-01-01

A low-cost, high-efficiency dish-Stirling solar thermal-electric power system is being developed for test in 1981. System components are the solar concentrator, receiver, fossil fuel combustor, thermal energy storage (TES), engine-generator, and power processing. System conceptualization is completed and design is in progress. Two receiver alternatives are being evaluated, a direct-coupled receiver-engine configuration with no TES and a heat pipe receiver with TES. System cost projections are being made. Goals for the system development task are (1) to develop an advanced dish-Stirling technology, utilizing a team of industrial contractors, (2) to demonstrate that technology at the system level, and (3) to determine how to achieve low production cost.

The Impact of Structured Writing and Developing Awareness of Learning Preferences on the Performance and Attitudes of Engineering Teams

ERIC Educational Resources Information Center

Dahm, Kevin; Newell, James; Newell, Heidi; Harvey, Roberta

2009-01-01

This paper discusses efforts to develop metacognition in teams of engineering students by: first, exploring personal learning patterns, and second, ongoing biweekly journaling exercises. Thirty-three junior and senior engineering students (30 chemical engineer, one each from mechanical, civil and electrical) working on semester-long projects in…

Technology evaluation, assessment, modeling, and simulation: the TEAMS capability

NASA Astrophysics Data System (ADS)

Holland, Orgal T.; Stiegler, Robert L.

1998-08-01

The United States Marine Corps' Technology Evaluation, Assessment, Modeling and Simulation (TEAMS) capability, located at the Naval Surface Warfare Center in Dahlgren Virginia, provides an environment for detailed test, evaluation, and assessment of live and simulated sensor and sensor-to-shooter systems for the joint warfare community. Frequent use of modeling and simulation allows for cost effective testing, bench-marking, and evaluation of various levels of sensors and sensor-to-shooter engagements. Interconnectivity to live, instrumented equipment operating in real battle space environments and to remote modeling and simulation facilities participating in advanced distributed simulations (ADS) exercises is available to support a wide- range of situational assessment requirements. TEAMS provides a valuable resource for a variety of users. Engineers, analysts, and other technology developers can use TEAMS to evaluate, assess and analyze tactical relevant phenomenological data on tactical situations. Expeditionary warfare and USMC concept developers can use the facility to support and execute advanced warfighting experiments (AWE) to better assess operational maneuver from the sea (OMFTS) concepts, doctrines, and technology developments. Developers can use the facility to support sensor system hardware, software and algorithm development as well as combat development, acquisition, and engineering processes. Test and evaluation specialists can use the facility to plan, assess, and augment their processes. This paper presents an overview of the TEAMS capability and focuses specifically on the technical challenges associated with the integration of live sensor hardware into a synthetic environment and how those challenges are being met. Existing sensors, recent experiments and facility specifications are featured.

The Advanced Modeling, Simulation and Analysis Capability Roadmap Vision for Engineering

NASA Technical Reports Server (NTRS)

Zang, Thomas; Lieber, Mike; Norton, Charles; Fucik, Karen

2006-01-01

This paper summarizes a subset of the Advanced Modeling Simulation and Analysis (AMSA) Capability Roadmap that was developed for NASA in 2005. The AMSA Capability Roadmap Team was chartered to "To identify what is needed to enhance NASA's capabilities to produce leading-edge exploration and science missions by improving engineering system development, operations, and science understanding through broad application of advanced modeling, simulation and analysis techniques." The AMSA roadmap stressed the need for integration, not just within the science, engineering and operations domains themselves, but also across these domains. Here we discuss the roadmap element pertaining to integration within the engineering domain, with a particular focus on implications for future observatory missions. The AMSA products supporting the system engineering function are mission information, bounds on information quality, and system validation guidance. The Engineering roadmap element contains 5 sub-elements: (1) Large-Scale Systems Models, (2) Anomalous Behavior Models, (3) advanced Uncertainty Models, (4) Virtual Testing Models, and (5) space-based Robotics Manufacture and Servicing Models.

2014-2688

NASA Image and Video Library

2014-05-23

CAPE CANAVERAL, Fla. -- Team members from the University of Alaska-Fairbanks received the Judges' Innovation Award during NASA's 2014 Robotic Mining Competition awards ceremony inside the Space Shuttle Atlantis attraction at the Kennedy Space Center Visitor Complex in Florida. More than 35 teams from colleges and universities around the U.S. designed and built remote-controlled robots for the mining competition. The competition is a NASA Human Exploration and Operations Mission Directorate project designed to engage and retain students in science, technology, engineering and mathematics, or STEM, fields by expanding opportunities for student research and design. Teams use their remote-controlled robotics to maneuver and dig in a supersized sandbox filled with a crushed material that has characteristics similar to Martian soil. The objective of the challenge is to see which team’s robot can collect and move the most regolith within a specified amount of time. The competition includes on-site mining, writing a systems engineering paper, performing outreach projects for K-12 students, slide presentation and demonstrations, and team spirit. For more information, visit www.nasa.gov/nasarmc. Photo credit: NASA/Kim Shiflett

2014-2690

NASA Image and Video Library

2014-05-23

CAPE CANAVERAL, Fla. -- The University of Alabama team Astrobotics in collaboration with Shelton State Community College received the highest award, the Joe Kosmo Award for Excellence, during NASA's 2014 Robotic Mining Competition awards ceremony inside the Space Shuttle Atlantis attraction at the Kennedy Space Center Visitor Complex in Florida. More than 35 teams from colleges and universities around the U.S. designed and built remote-controlled robots for the mining competition. The competition is a NASA Human Exploration and Operations Mission Directorate project designed to engage and retain students in science, technology, engineering and mathematics, or STEM, fields by expanding opportunities for student research and design. Teams use their remote-controlled robotics to maneuver and dig in a supersized sandbox filled with a crushed material that has characteristics similar to Martian soil. The objective of the challenge is to see which team’s robot can collect and move the most regolith within a specified amount of time. The competition includes on-site mining, writing a systems engineering paper, performing outreach projects for K-12 students, slide presentation and demonstrations, and team spirit. For more information, visit www.nasa.gov/nasarmc. Photo credit: NASA/Kim Shiflett

Mission operations and command assurance: Instilling quality into flight operations

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Witkowski, Mona M.; Bruno, Kristin J.; Potts, Sherrill S.

1993-01-01

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous process improvement to reduce the probability of radiating incorrect commands to a spacecraft. The MO&CA task has evolved from participating as a member of the spacecraft team to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

Tools for Tomorrow's Science and Technology Workforce: MATE's 2006 ROV Competition Sets Students' Sights on Ocean Observing Systems

NASA Technical Reports Server (NTRS)

Zande, Jill; Meeson, Blanche; Cook, Susan; Matsumoto, George

2006-01-01

Teams participating in the 2006 ROV competition organized by the Marine Advanced Technology Education (MATE) Center and the Marine Technology Society's (MTS) ROV Committee experienced first-hand the scientific and technical challenges that many ocean scientists, technicians, and engineers face every day. The competition tasked more than 1,000 middle and high school, college, and university students from Newfoundland to Hong Kong with designing and building ROVs to support the next generation of ocean observing systems. Teaming up with the National Office for Integrated and Sustained Ocean Observations, Ocean. US, and the Ocean Research Interactive Observatory Networks (ORION) Program, the competition highlighted ocean observing systems and the careers, organizations, and technologies associated with ocean observatories. The student teams were challenged to develop vehicles that can deploy, install, and maintain networks of instruments as well as to explore the practical applications and the research questions made possible by observing systems.

An Interdisciplinary Field Robotics Program for Undergraduate Computer Science and Engineering Education

ERIC Educational Resources Information Center

Kitts, Christopher; Quinn, Neil

2004-01-01

Santa Clara University's Robotic Systems Laboratory conducts an aggressive robotic development and operations program in which interdisciplinary teams of undergraduate students build and deploy a wide range of robotic systems, ranging from underwater vehicles to spacecraft. These year-long projects expose students to the breadth of and…

Incorporating Solid Modeling and Team-Based Design into Freshman Engineering Graphics.

ERIC Educational Resources Information Center

Buchal, Ralph O.

2001-01-01

Describes the integration of these topics through a major team-based design and computer aided design (CAD) modeling project in freshman engineering graphics at the University of Western Ontario. Involves n=250 students working in teams of four to design and document an original Lego toy. Includes 12 references. (Author/YDS)

Photo-realistic Terrain Modeling and Visualization for Mars Exploration Rover Science Operations

NASA Technical Reports Server (NTRS)

Edwards, Laurence; Sims, Michael; Kunz, Clayton; Lees, David; Bowman, Judd

2005-01-01

Modern NASA planetary exploration missions employ complex systems of hardware and software managed by large teams of. engineers and scientists in order to study remote environments. The most complex and successful of these recent projects is the Mars Exploration Rover mission. The Computational Sciences Division at NASA Ames Research Center delivered a 30 visualization program, Viz, to the MER mission that provides an immersive, interactive environment for science analysis of the remote planetary surface. In addition, Ames provided the Athena Science Team with high-quality terrain reconstructions generated with the Ames Stereo-pipeline. The on-site support team for these software systems responded to unanticipated opportunities to generate 30 terrain models during the primary MER mission. This paper describes Viz, the Stereo-pipeline, and the experiences of the on-site team supporting the scientists at JPL during the primary MER mission.

Spring 2013 Graduate Engineering Internship Summary

NASA Technical Reports Server (NTRS)

Ehrlich, Joshua

2013-01-01

In the spring of 2013, I participated in the National Aeronautics and Space Administration (NASA) Pathways Intern Employment Program at the Kennedy Space Center (KSC) in Florida. This was my final internship opportunity with NASA, a third consecutive extension from a summer 2012 internship. Since the start of my tenure here at KSC, I have gained an invaluable depth of engineering knowledge and extensive hands-on experience. These opportunities have granted me the ability to enhance my systems engineering approach in the field of payload design and testing as well as develop a strong foundation in the area of composite fabrication and testing for repair design on space vehicle structures. As a systems engineer, I supported the systems engineering and integration team with final acceptance testing of the Vegetable Production System, commonly referred to as Veggie. Verification and validation (V and V) of Veggie was carried out prior to qualification testing of the payload, which incorporated the process of confirming the system's design requirements dependent on one or more validation methods: inspection, analysis, demonstration, and testing.

Navigation Ground Data System Engineering for the Cassini/Huygens Mission

NASA Technical Reports Server (NTRS)

Beswick, R. M.; Antreasian, P. G.; Gillam, S. D.; Hahn, Y.; Roth, D. C.; Jones, J. B.

2008-01-01

The launch of the Cassini/Huygens mission on October 15, 1997, began a seven year journey across the solar system that culminated in the entry of the spacecraft into Saturnian orbit on June 30, 2004. Cassini/Huygens Spacecraft Navigation is the result of a complex interplay between several teams within the Cassini Project, performed on the Ground Data System. The work of Spacecraft Navigation involves rigorous requirements for accuracy and completeness carried out often under uncompromising critical time pressures. To support the Navigation function, a fault-tolerant, high-reliability/high-availability computational environment was necessary to support data processing. Configuration Management (CM) was integrated with fault tolerant design and security engineering, according to the cornerstone principles of Confidentiality, Integrity, and Availability. Integrated with this approach are security benchmarks and validation to meet strict confidence levels. In addition, similar approaches to CM were applied in consideration of the staffing and training of the system administration team supporting this effort. As a result, the current configuration of this computational environment incorporates a secure, modular system, that provides for almost no downtime during tour operations.

Superconducting gravity gradiometer mission. Volume 1: Study team executive summary

NASA Technical Reports Server (NTRS)

Morgan, Samuel H. (Editor); Paik, Ho Jung (Editor)

1989-01-01

An executive summary is presented based upon the scientific and engineering studies and developments performed or directed by a Study Team composed of various Federal and University activities involved with the development of a three-axis Superconducting Gravity Gradiometer integrated with a six-axis superconducting accelerometer. This instrument is being developed for a future orbital mission to make precise global gravity measurements. The scientific justification and requirements for such a mission are discussed. This includes geophysics, the primary mission objective, as well as secondary objectives, such as navigation and tests of fundamental laws of physics, i.e., a null test of the inverse square law of gravitation and tests of general relativity. The instrument design and status along with mission analysis, engineering assessments, and preliminary spacecraft concepts are discussed. In addition, critical spacecraft systems and required technology advancements are examined. The mission requirements and an engineering assessment of a precursor flight test of the instrument are discussed.

Superconducting gravity gradiometer mission. Volume 2: Study team technical report

NASA Technical Reports Server (NTRS)

Morgan, Samuel H. (Editor); Paik, Ho Jung (Editor)

1988-01-01

Scientific and engineering studies and developments performed or directed by a Study Team composed of various Federal and University activities involved with the development of a three-axis superconducting gravity gradiometer integrated with a six-axis superconducting accelerometer are examined. This instrument is being developed for a future orbital mission to make precise global gravity measurements. The scientific justification and requirements for such a mission are discussed. This includes geophysics, the primary mission objective, as well as secondary objective, such as navigation and feats of fundamental laws of physics, i.e., a null test of the inverse square law of gravitation and tests of general relativity. The instrument design and status along with mission analysis, engineering assessments, and preliminary spacecraft concepts are discussed. In addition, critical spacecraft systems and required technology advancements are examined. The mission requirements and an engineering assessment of a precursor flight test of the instrument are discussed.

Renovation of a Mechanical Engineering Senior Design Class to an Industry-Tied and Team-Oriented Course

ERIC Educational Resources Information Center

Liu, Yucheng

2017-01-01

In this work, an industry-based and team-oriented education model was established based on a traditional mechanical engineering (ME) senior design class in order to better prepare future engineers and leaders so as to meet the increasing demand for high-quality engineering graduates. In the renovated curriculum, industry-sponsored projects became…

Development of Automated Testing Tools for Traffic Control Signals and Devices

DOT National Transportation Integrated Search

2012-01-30

Through a coordinated effort among the electrical engineering research team of the Florida State University (FSU) and key Florida Department of Transportation (FDOT) personnel, an automated testing system for National Electrical Manufacturers Associa...

Engineering a Successful Mission: Lessons from the Lunar Reconnaissance Orbiter

NASA Technical Reports Server (NTRS)

Everett, David F.

2011-01-01

Schedule pressure is common in the commercial world, where late delivery of a product means delayed income and loss of profit. 12 Research spacecraft developed by NASA, on the other hand, tend to be driven by the high cost of launch vehicles and the public scrutiny of failure-- the primary driver is ensuring proper operation in space for a system that cannot be retrieved for repair. The Lunar Reconnaissance Orbiter (LRO) development faced both schedule pressure and high visibility. The team had to balance the strong push to meet a launch date against the need to ensure that this first mission for Exploration succeeded. This paper will provide an overview of the mission from concept through its first year of operation and explore some of the challenges the systems engineering team faced taking a mission from preliminary design review to pre-ship review in 3 years.

Near Earth Asteroid Scout Solar Sail Engineering Development Unit Test Suite

NASA Technical Reports Server (NTRS)

Lockett, Tiffany Russell; Few, Alexander; Wilson, Richard

2017-01-01

The Near Earth Asteroid (NEA) Scout project is a 6U reconnaissance mission to investigate a near Earth asteroid utilizing an 86m(sub 2) solar sail as the primary propulsion system. This will be the largest solar sail NASA has launched to date. NEA Scout is currently manifested on the maiden voyage of the Space Launch System in 2018. In development of the solar sail subsystem, design challenges were identified and investigated for packaging within a 6U form factor and deployment in cis-lunar space. Analysis was able to capture understanding of thermal, stress, and dynamics of the stowed system as well as mature an integrated sail membrane model for deployed flight dynamics. Full scale system testing on the ground is the optimal way to demonstrate system robustness, repeatability, and overall performance on a compressed flight schedule. To physically test the system, the team developed a flight sized engineering development unit with design features as close to flight as possible. The test suite included ascent vent, random vibration, functional deployments, thermal vacuum, and full sail deployments. All of these tests contributed towards development of the final flight unit. This paper will address several of the design challenges and lessons learned from the NEA Scout solar sail subsystem engineering development unit. Testing on the component level all the way to the integrated subsystem level. From optical properties of the sail material to fold and spooling the single sail, the team has developed a robust deployment system for the solar sail. The team completed several deployments of the sail system in preparation for flight at half scale (4m) and full scale (6.8m): boom only, half scale sail deployment, and full scale sail deployment. This paper will also address expected and received test results from ascent vent, random vibration, and deployment tests.

Securely Partitioning Spacecraft Computing Resources: Validation of a Separation Kernel

NASA Astrophysics Data System (ADS)

Bremer, Leon; Schreutelkamp, Erwin

2011-08-01

The F-35 Lightning II, also known as the Joint Strike Fighter, will be the first operational fighter aircraft equipped with an operational MultiShip Embedded Training capability. This onboard training system allows teams of fighter pilots to jointly operate their F-35 in flight against virtual threats, avoiding the need for real adversary air threats and surface threat systems in their training. The European Real-time Operations Simulator (EuroSim) framework is well known in the space domain, particularly in support of engineering and test phases of space system development. In the MultiShip Embedded Training project, EuroSim is not only the essential tool for development and verification throughout the project but is also the engine of the final embedded simulator on board of the F-35 aircraft. The novel ways in which EuroSim is applied in the project in relation to distributed simulation problems, team collaboration, tool chains and embedded systems can benefit many projects and applications. The paper describes the application of EuroSim as the simulation engine of the F-35 Embedded Training solution, the extensions to the EuroSim product that enable this application, and its usage in development and verification of the whole project as carried out at the sites of Dutch Space and the National Aerospace Laboratory (NLR).

Lessons Learned for Improving Spacecraft Ground Operations

NASA Technical Reports Server (NTRS)

Bell, Michael; Henderson, Gena; Stambolian, Damon

2013-01-01

NASA policy requires each Program or Project to develop a plan for how they will address Lessons Learned. Projects have the flexibility to determine how best to promote and implement lessons learned. A large project might budget for a lessons learned position to coordinate elicitation, documentation and archival of the project lessons. The lessons learned process crosses all NASA Centers and includes the contactor community. o The Office of The Chief Engineer at NASA Headquarters in Washington D.C., is the overall process owner, and field locations manage the local implementation. One tool used to transfer knowledge between program and projects is the Lessons Learned Information System (LLIS). Most lessons come from NASA in partnership with support contractors. A search for lessons that might impact a new design is often performed by a contractor team member. Knowledge is not found with only one person, one project team, or one organization. Sometimes, another project team, or person, knows something that can help your project or your task. Knowledge sharing is an everyday activity at the Kennedy Space Center through storytelling, Kennedy Engineering Academy presentations and through searching the Lessons Learned Information system. o Project teams search the lessons repository to ensure the best possible results are delivered. o The ideas from the past are not always directly applicable but usually spark new ideas and innovations. Teams have a great responsibility to collect and disseminate these lessons so that they are shared with future generations of space systems designers. o Leaders should set a goal for themselves to host a set numbers of lesson learned events each year and do more to promote multiple methods of lessons learned activities. o High performing employees are expected to share their lessons, however formal knowledge sharing presentation are not the norm for many employees.

Hierarchy curriculum for practical skills training in optics and photonics

NASA Astrophysics Data System (ADS)

Zheng, XiaoDong; Wang, XiaoPing; Liu, Xu; Liu, XiangDong; Lin, YuanFang

2017-08-01

The employers in optical engineering fields hope to recruit students who are capable of applying optical principles to solve engineering problems and have strong laboratory skills. In Zhejiang University, a hierarchy curriculum for practical skill training has been constructed to satisfy this demand. This curriculum includes "Introductive practicum" for freshmen, "Opto-mechanical systems design", "Engineering training", "Electronic system design", "Student research training program (SRTP)", "National University Students' Optical-Science-Technology Competition game", and "Offcampus externship". Without cutting optical theory credit hours, this hierarchy curriculum provides a step-by-step solution to enhance students' practical skills. By following such a hierarchy curriculum, students can smoothly advance from a novice to a qualified professional expert in optics. They will be able to utilize optical engineering tools to design, build, analyze, improve, and test systems, and will be able to work effectively in teams to solve problems in engineering and design.

The Strength of the Strongest Ties in Collaborative Problem Solving

NASA Astrophysics Data System (ADS)

de Montjoye, Yves-Alexandre; Stopczynski, Arkadiusz; Shmueli, Erez; Pentland, Alex; Lehmann, Sune

2014-06-01

Complex problem solving in science, engineering, and business has become a highly collaborative endeavor. Teams of scientists or engineers collaborate on projects using their social networks to gather new ideas and feedback. Here we bridge the literature on team performance and information networks by studying teams' problem solving abilities as a function of both their within-team networks and their members' extended networks. We show that, while an assigned team's performance is strongly correlated with its networks of expressive and instrumental ties, only the strongest ties in both networks have an effect on performance. Both networks of strong ties explain more of the variance than other factors, such as measured or self-evaluated technical competencies, or the personalities of the team members. In fact, the inclusion of the network of strong ties renders these factors non-significant in the statistical analysis. Our results have consequences for the organization of teams of scientists, engineers, and other knowledge workers tackling today's most complex problems.

The strength of the strongest ties in collaborative problem solving.

PubMed

de Montjoye, Yves-Alexandre; Stopczynski, Arkadiusz; Shmueli, Erez; Pentland, Alex; Lehmann, Sune

2014-06-20

Complex problem solving in science, engineering, and business has become a highly collaborative endeavor. Teams of scientists or engineers collaborate on projects using their social networks to gather new ideas and feedback. Here we bridge the literature on team performance and information networks by studying teams' problem solving abilities as a function of both their within-team networks and their members' extended networks. We show that, while an assigned team's performance is strongly correlated with its networks of expressive and instrumental ties, only the strongest ties in both networks have an effect on performance. Both networks of strong ties explain more of the variance than other factors, such as measured or self-evaluated technical competencies, or the personalities of the team members. In fact, the inclusion of the network of strong ties renders these factors non-significant in the statistical analysis. Our results have consequences for the organization of teams of scientists, engineers, and other knowledge workers tackling today's most complex problems.

Constructing engineers through practice: Gendered features of learning and identity development

NASA Astrophysics Data System (ADS)

Tonso, Karen L.

How do women and men student engineers develop an engineering identity (a sense of belonging, or not), while practicing "actual" engineering? What are the influences of gender, learning and knowledge, relations of power, and conceptions of equality on cultural identity development? I studied these issues in reform-minded engineering design classes, courses organized around teaching students communications, teamwork, and practical engineering. Engineering-student cultural identity categories revealed a status hierarchy, predicated on meeting "academic" criteria for excellence, and the almost total exclusion of women. While working as an engineering colleague on five student teams (three first-year and two senior) and attending their design classes, I documented how cultural identities were made evident and constructed in students' practical engineering. Design projects promoted linking academic knowledge with real-world situations, sharing responsibilities and trusting colleagues, communicating engineering knowledge to technical and non-technical members of business communities, and addressing gaps in students' knowledge. With a curriculum analysis and survey of students' perceptions of the differences between design and conventional courses, I embedded the design classes in the wider campus and found that: (1) Engineering education conferred prestige, power, and well-paying jobs on students who performed "academic" engineering, while failing to adequately encourage "actual" engineering practices. High-status student engineers were the least likely to perform "actual" engineering in design teams. (2) Engineering education advanced an ideology that encouraged its practitioners to consider men's privilege and women's invisibility normal. By making "acting like men act" the standards to which engineering students must conform, women learned to put up with oppressive treatment. Women's accepting their own mistreatment and hiding their womanhood became a condition of women's belonging. (3) Despite all of the pressures to do otherwise, (some) teams of students (at all levels) carved out small oases where "actual" engineering prevailed and women's participation was robust. Students--not faculty, not progressive pedagogy, not "reformed" courses--disrupted prevailing norms. However, two women engineering students, one on each senior team, performed fabulous "actual" engineering, yet neither of them had a job when they graduated--the only two senior students on my teams without jobs.

Engineering within the assembly, verification, and integration (AIV) process in ALMA

NASA Astrophysics Data System (ADS)

Lopez, Bernhard; McMullin, Joseph P.; Whyborn, Nicholas D.; Duvall, Eugene

2010-07-01

The Atacama Large Millimeter/submillimeter Array (ALMA) is a joint project between astronomical organizations in Europe, North America, and East Asia, in collaboration with the Republic of Chile. ALMA will consist of at least 54 twelve-meter antennas and 12 seven-meter antennas operating as an interferometer in the millimeter and sub-millimeter wavelength range. It will be located at an altitude above 5000m in the Chilean Atacama desert. As part of the ALMA construction phase the Assembly, Verification and Integration (AIV) team receives antennas and instrumentation from Integrated Product Teams (IPTs), verifies that the sub-systems perform as expected, performs the assembly and integration of the scientific instrumentation and verifies that functional and performance requirements are met. This paper aims to describe those aspects related to the AIV Engineering team, its role within the 4-station AIV process, the different phases the group underwent, lessons learned and potential space for improvement. AIV Engineering initially focused on the preparation of the necessary site infrastructure for AIV activities, on the purchase of tools and equipment and on the first ALMA system installations. With the first antennas arriving on site the team started to gather experience with AIV Station 1 beacon holography measurements for the assessment of the overall antenna surface quality, and with optical pointing to confirm the antenna pointing and tracking capabilities. With the arrival of the first receiver AIV Station 2 was developed which focuses on the installation of electrical and cryogenic systems and incrementally establishes the full connectivity of the antenna as an observing platform. Further antenna deliveries then allowed to refine the related procedures, develop staff expertise and to transition towards a more routine production process. Stations 3 and 4 deal with verification of the antenna with integrated electronics by the AIV Science Team and is not covered directly in this paper. It is believed that both continuous improvement and the clear definition of the AIV 4-station model were key factors in achieving the goal of bringing the antennas into a state that is well enough characterized in order to smoothly start commissioning activities.

Recent Experiences of the NASA Engineering and Safety Center (NESC) GN and C Technical Discipline Team (TDT)

NASA Technical Reports Server (NTRS)

Dennehy, Cornelius J.

2010-01-01

The NASA Engineering and Safety Center (NESC), initially formed in 2003, is an independently funded NASA Program whose dedicated team of technical experts provides objective engineering and safety assessments of critical, high risk projects. The GN&C Technical Discipline Team (TDT) is one of fifteen such discipline-focused teams within the NESC organization. The TDT membership is composed of GN&C specialists from across NASA and its partner organizations in other government agencies, industry, national laboratories, and universities. This paper will briefly define the vision, mission, and purpose of the NESC organization. The role of the GN&C TDT will then be described in detail along with an overview of how this team operates and engages in its objective engineering and safety assessments of critical NASA projects. This paper will then describe selected recent experiences, over the period 2007 to present, of the GN&C TDT in which they directly performed or supported a wide variety of NESC assessments and consultations.

Identification and Classification of Common Risks in Space Science Missions

NASA Technical Reports Server (NTRS)

Hihn, Jairus M.; Chattopadhyay, Debarati; Hanna, Robert A.; Port, Daniel; Eggleston, Sabrina

2010-01-01

Due to the highly constrained schedules and budgets that NASA missions must contend with, the identification and management of cost, schedule and risks in the earliest stages of the lifecycle is critical. At the Jet Propulsion Laboratory (JPL) it is the concurrent engineering teams that first address these items in a systematic manner. Foremost of these concurrent engineering teams is Team X. Started in 1995, Team X has carried out over 1000 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. The ability to do integrated risk identification and assessment was first introduced into Team X in 2001. Since that time the mission risks identified in each study have been kept in a database. In this paper we will describe how the Team X risk process is evolving highlighting the strengths and weaknesses of the different approaches. The paper will especially focus on the identification and classification of common risks that have arisen during Team X studies of space based science missions.

Relating MBSE to Spacecraft Development: A NASA Pathfinder

NASA Technical Reports Server (NTRS)

Othon, Bill

2016-01-01

The NASA Engineering and Safety Center (NESC) has sponsored a Pathfinder Study to investigate how Model Based Systems Engineering (MBSE) and Model Based Engineering (MBE) techniques can be applied by NASA spacecraft development projects. The objectives of this Pathfinder Study included analyzing both the products of the modeling activity, as well as the process and tool chain through which the spacecraft design activities are executed. Several aspects of MBSE methodology and process were explored. Adoption and consistent use of the MBSE methodology within an existing development environment can be difficult. The Pathfinder Team evaluated the possibility that an "MBSE Template" could be developed as both a teaching tool as well as a baseline from which future NASA projects could leverage. Elements of this template include spacecraft system component libraries, data dictionaries and ontology specifications, as well as software services that do work on the models themselves. The Pathfinder Study also evaluated the tool chain aspects of development. Two chains were considered: 1. The Development tool chain, through which SysML model development was performed and controlled, and 2. The Analysis tool chain, through which both static and dynamic system analysis is performed. Of particular interest was the ability to exchange data between SysML and other engineering tools such as CAD and Dynamic Simulation tools. For this study, the team selected a Mars Lander vehicle as the element to be designed. The paper will discuss what system models were developed, how data was captured and exchanged, and what analyses were conducted.

A Decision Support System for Evaluating Systems of Undersea Sensors and Weapons

DTIC Science & Technology

2015-12-01

distribution is unlimited A DECISION SUPPORT SYSTEM FOR EVALUATING SYSTEMS OF UNDERSEA SENSORS AND WEAPONS by Team Mental Focus Cohort 142O...A DECISION SUPPORT SYSTEM FOR EVALUATING SYSTEMS OF UNDERSEA SENSORS AND WEAPONS 5. FUNDING NUMBERS 6. AUTHOR(S) Systems Engineering Cohort...undersea weapons, it requires the supporting tools to evaluate and predict the effectiveness of these system concepts. While current naval minefield

Space Launch System Base Heating Test: Sub-Scale Rocket Engine/Motor Design, Development & Performance Analysis

NASA Technical Reports Server (NTRS)

Mehta, Manish; Seaford, Mark; Kovarik, Brian; Dufrene, Aaron; Solly, Nathan

2014-01-01

ATA-002 Technical Team has successfully designed, developed, tested and assessed the SLS Pathfinder propulsion systems for the Main Base Heating Test Program. Major Outcomes of the Pathfinder Test Program: Reach 90% of full-scale chamber pressure Achieved all engine/motor design parameter requirements Reach steady plume flow behavior in less than 35 msec Steady chamber pressure for 60 to 100 msec during engine/motor operation Similar model engine/motor performance to full-scale SLS system Mitigated nozzle throat and combustor thermal erosion Test data shows good agreement with numerical prediction codes Next phase of the ATA-002 Test Program Design & development of the SLS OML for the Main Base Heating Test Tweak BSRM design to optimize performance Tweak CS-REM design to increase robustness MSFC Aerosciences and CUBRC have the capability to develop sub-scale propulsion systems to meet desired performance requirements for short-duration testing.

WATER TREATMENT AND EDUCATION IN VILLAHERMOSA, MEXICO

EPA Science Inventory

The interdisciplinary P3 team included mechanical, civil and environmental, and electrical engineers. This was critical to overcome the technical challenges presented by this project. A successful full-scale system was developed that greatly reduces the probability of contract...

Developing Systems Engineering Skills Through NASA Summer Intern Project

NASA Technical Reports Server (NTRS)

Bhasin, Kul; Barritt, Brian; Golden, Bert; Knoblock, Eric; Matthews, Seth; Warner, Joe

2010-01-01

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.

40 CFR 1054.620 - What are the provisions for exempting engines used solely for competition?

Code of Federal Regulations, 2014 CFR

2014-07-01

... equipment built on or after January 1, 2010. (a) We may grant you an exemption from the standards and... competition teams, professional competitors, or other qualified competitors. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers, other...

40 CFR 1054.620 - What are the provisions for exempting engines used solely for competition?

Code of Federal Regulations, 2013 CFR

2013-07-01

... equipment built on or after January 1, 2010. (a) We may grant you an exemption from the standards and... competition teams, professional competitors, or other qualified competitors. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers, other...

40 CFR 1054.620 - What are the provisions for exempting engines used solely for competition?

Code of Federal Regulations, 2012 CFR

2012-07-01

... equipment built on or after January 1, 2010. (a) We may grant you an exemption from the standards and... competition teams, professional competitors, or other qualified competitors. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers, other...

40 CFR 1054.620 - What are the provisions for exempting engines used solely for competition?

Code of Federal Regulations, 2011 CFR

2011-07-01

... equipment built on or after January 1, 2010. (a) We may grant you an exemption from the standards and... competition teams, professional competitors, or other qualified competitors. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers, other...

40 CFR 1054.620 - What are the provisions for exempting engines used solely for competition?

Code of Federal Regulations, 2010 CFR

2010-07-01

... equipment built on or after January 1, 2010. (a) We may grant you an exemption from the standards and... competition teams, professional competitors, or other qualified competitors. For replacement engines, the sale of the engine itself must be limited to professional racing teams, professional racers, other...

System Issues Related to Implementing on the Internet

NASA Technical Reports Server (NTRS)

Mackey, William; Bagg, Thomas C., III

1999-01-01

Implementing capabilities on the World Wide Web should never be taken lightly. A good systems engineer is able to examine such implementations from all points of view, including political, legal, security, access, technical deployment, and quality. The evacuation discussed in this paper was conducted to ensure that the National Aeronautics and Space Administration (NASA) was proceeding in a correct direction by implementing RECALL a Lessons Learned System on the Web and, subsequently, did so successfully. The systems approach extended well beyond technical implementation to several issue that are not often addressed by an implementation team. The resulting evaluation increased the team's sensitivity to such issues and, in fact, the authors believe that the evaluation provided as much benefit as the system itself.

Twelve Scientific Specialists of the Peenemuende Team

NASA Technical Reports Server (NTRS)

2004-01-01

Twelve scientific specialists of the Peenemuende team at the front of Building 4488, Redstone Arsenal, Huntsville, Alabama. They led the Army's space efforts at ABMA before transfer of the team to National Aeronautic and Space Administration (NASA), George C. Marshall Space Flight Center (MSFC). (Left to right) Dr. Ernst Stuhlinger, Director, Research Projects Office; Dr. Helmut Hoelzer, Director, Computation Laboratory: Karl L. Heimburg, Director, Test Laboratory; Dr. Ernst Geissler, Director, Aeroballistics Laboratory; Erich W. Neubert, Director, Systems Analysis Reliability Laboratory; Dr. Walter Haeussermarn, Director, Guidance and Control Laboratory; Dr. Wernher von Braun, Director Development Operations Division; William A. Mrazek, Director, Structures and Mechanics Laboratory; Hans Hueter, Director, System Support Equipment Laboratory;Eberhard Rees, Deputy Director, Development Operations Division; Dr. Kurt Debus, Director Missile Firing Laboratory; Hans H. Maus, Director, Fabrication and Assembly Engineering Laboratory

Advanced Information Technology in Simulation Based Life Cycle Design

NASA Technical Reports Server (NTRS)

Renaud, John E.

2003-01-01

In this research a Collaborative Optimization (CO) approach for multidisciplinary systems design is used to develop a decision based design framework for non-deterministic optimization. To date CO strategies have been developed for use in application to deterministic systems design problems. In this research the decision based design (DBD) framework proposed by Hazelrigg is modified for use in a collaborative optimization framework. The Hazelrigg framework as originally proposed provides a single level optimization strategy that combines engineering decisions with business decisions in a single level optimization. By transforming this framework for use in collaborative optimization one can decompose the business and engineering decision making processes. In the new multilevel framework of Decision Based Collaborative Optimization (DBCO) the business decisions are made at the system level. These business decisions result in a set of engineering performance targets that disciplinary engineering design teams seek to satisfy as part of subspace optimizations. The Decision Based Collaborative Optimization framework more accurately models the existing relationship between business and engineering in multidisciplinary systems design.

Coal gasification systems engineering and analysis. Appendix G: Commercial design and technology evaluation

NASA Technical Reports Server (NTRS)

1980-01-01

A technology evaluation of five coal gasifier systems (Koppers-Totzek, Texaco, Babcock and Wilcox, Lurgi and BGC/Lurgi) and procedures and criteria for evaluating competitive commercial coal gasification designs is presented. The technology evaluation is based upon the plant designs and cost estimates developed by the BDM-Mittelhauser team.

Fault Management Technology Maturation for NASA's Constellation Program

NASA Technical Reports Server (NTRS)

Waterman, Robert D.

2010-01-01

This slide presentation reviews the maturation of fault management technology in preparation for the Constellation Program. There is a review of the Space Shuttle Main Engine (SSME) and a discussion of a couple of incidents with the shuttle main engine and tanking that indicated the necessity for predictive maintenance. Included is a review of the planned Ares I-X Ground Diagnostic Prototype (GDP) and further information about detection and isolation of faults using Testability Engineering and Maintenance System (TEAMS). Another system that being readied for use that detects anomalies, the Inductive Monitoring System (IMS). The IMS automatically learns how the system behaves and alerts operations it the current behavior is anomalous. The comparison of STS-83 and STS-107 (i.e., the Columbia accident) is shown as an example of the anomaly detection capabilities.

Automation of Shuttle Tile Inspection - Engineering methodology for Space Station

NASA Technical Reports Server (NTRS)

Wiskerchen, M. J.; Mollakarimi, C.

1987-01-01

The Space Systems Integration and Operations Research Applications (SIORA) Program was initiated in late 1986 as a cooperative applications research effort between Stanford University, NASA Kennedy Space Center, and Lockheed Space Operations Company. One of the major initial SIORA tasks was the application of automation and robotics technology to all aspects of the Shuttle tile processing and inspection system. This effort has adopted a systems engineering approach consisting of an integrated set of rapid prototyping testbeds in which a government/university/industry team of users, technologists, and engineers test and evaluate new concepts and technologies within the operational world of Shuttle. These integrated testbeds include speech recognition and synthesis, laser imaging inspection systems, distributed Ada programming environments, distributed relational database architectures, distributed computer network architectures, multimedia workbenches, and human factors considerations.

KSC-2013-3535

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers from NASA's Johnson Space Center fly a remote-controlled helicopter equipped with a unique set of sensors and software during a competition at the agency's Kennedy Space Center. Teams from Johnson, Kennedy and Marshall Space Flight Center competed in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

1300906

NASA Image and Video Library

2013-08-05

MORE THAN 250 PEOPLE FROM ACROSS NASA'S MARSHALL SPACE FLIGHT CENTER PARTICIPATED IN THE SPACE LAUNCH SYSTEM (SLS) POST-PRELIMINARY DESIGN REVIEW REPORT, HELD AUG. 5 IN ACTIVITIES BUILDING 4316. DISCUSSING THE REVIEW AND THANKING THE MARSHALL TEAM FOR A JOB WELL DONE, ARE FROM LEFT, GARRY LYLES, SLS CHIEF ENGINEER; TODD MAY, MANAGER OF THE SLS PROGRAM; STEVE CASH, DIRECTOR OF MARSHALL’S SAFETY & MISSION ASSURANCE DIRECTORATE; AND CHRIS SINGER, MANAGER OF MARSHALL’S ENGINEERING DIRECTORATE

Standard CMMI Appraisal Method for Process Improvement (SCAMPI) A, Version 1.3: Method Definition Document

DTIC Science & Technology

2011-03-01

performance of Federal Government Contract Number FA8721-05- C -0003 with Carnegie Mellon University for the operation of the Software Engineering... C Roles and Responsibilities 195 Appendix D Reporting Requirements and Options 201 Appendix E Managed Discovery 203 Appendix F Scoping and...Upgrade Team (SUT) • Mary Busby , Lockheed Martin • Palma Buttles-Valdez, Software Engineering Institute • Paul Byrnes, Integrated System Diagnostics

Developing a Sand Management Plan for Galveston Island

DTIC Science & Technology

2015-10-16

Engineer Coastal & Hydraulics Laboratory Engineer Research & Development Center On behalf of the Project Team: Andrew Morang, David King, and Robert...Budget Objectives • Identify sources and sinks of sediment in coastal system  Beach fills  Littoral and offshore sources  Dredge data...more than 100 ft of erosion After 10 years After 50 years Innovative solutions for a safer, better world BUILDING STRONG® Beach Fills (West End

Performance of student software development teams: the influence of personality and identifying as team members

NASA Astrophysics Data System (ADS)

Monaghan, Conal; Bizumic, Boris; Reynolds, Katherine; Smithson, Michael; Johns-Boast, Lynette; van Rooy, Dirk

2015-01-01

One prominent approach in the exploration of the variations in project team performance has been to study two components of the aggregate personalities of the team members: conscientiousness and agreeableness. A second line of research, known as self-categorisation theory, argues that identifying as team members and the team's performance norms should substantially influence the team's performance. This paper explores the influence of both these perspectives in university software engineering project teams. Eighty students worked to complete a piece of software in small project teams during 2007 or 2008. To reduce limitations in statistical analysis, Monte Carlo simulation techniques were employed to extrapolate from the results of the original sample to a larger simulated sample (2043 cases, within 319 teams). The results emphasise the importance of taking into account personality (particularly conscientiousness), and both team identification and the team's norm of performance, in order to cultivate higher levels of performance in student software engineering project teams.

Communication skills to develop trusting relationships on global virtual engineering capstone teams

NASA Astrophysics Data System (ADS)

Zaugg, Holt; Davies, Randall S.

2013-05-01

As universities seek to provide cost-effective, cross-cultural experiences using global virtual (GV) teams, the 'soft' communication skills typical of all teams, increases in importance for GV teams. Students need to be taught how to navigate through cultural issues and virtual tool issues to build strong trusting relationships with distant team members. Weekly team meetings provide an excellent opportunity to observe key team interactions that facilitate relationship and trust-building among team members. This study observed the weekly team meetings of engineering students attending two US universities and one Asian university as they collaborated as a single GV capstone GV team. In addition local team members were interviewed individually and collectively throughout the project to determine strategies that facilitated team relations and trust. Findings indicate the importance of student choice of virtual communication tools, the refining of communication practices, and specific actions to build trusting relationships. As student developed these attributes, collaboration and success was experienced on this GV team.

Model Based Definition

NASA Technical Reports Server (NTRS)

Rowe, Sidney E.

2010-01-01

In September 2007, the Engineering Directorate at the Marshall Space Flight Center (MSFC) created the Design System Focus Team (DSFT). MSFC was responsible for the in-house design and development of the Ares 1 Upper Stage and the Engineering Directorate was preparing to deploy a new electronic Configuration Management and Data Management System with the Design Data Management System (DDMS) based upon a Commercial Off The Shelf (COTS) Product Data Management (PDM) System. The DSFT was to establish standardized CAD practices and a new data life cycle for design data. Of special interest here, the design teams were to implement Model Based Definition (MBD) in support of the Upper Stage manufacturing contract. It is noted that this MBD does use partially dimensioned drawings for auxiliary information to the model. The design data lifecycle implemented several new release states to be used prior to formal release that allowed the models to move through a flow of progressive maturity. The DSFT identified some 17 Lessons Learned as outcomes of the standards development, pathfinder deployments and initial application to the Upper Stage design completion. Some of the high value examples are reviewed.

Propulsion System Advances that Enable a Reusable Liquid Fly Back Booster (LFBB)

NASA Technical Reports Server (NTRS)

Keith, Edward L.; Rothschild, William J.

1998-01-01

This paper provides an overview of the booster propulsion system for the Liquid Fly Back Booster (LFBB). This includes, system requirements, design approach, concept of operations, reliability, safety and cost assumptions. The paper summarizes the findings of the Boeing propulsion team that has been studying the LFBB feasibility as a booster replacement for the Space Shuttle. This paper will discuss recent advances including a new generation of kerosene and oxygen rich pre-burner staged combustion cycle main rocket engines. The engine reliability and safety is expected to be much higher than current standards by adding extra operating margins into the design and normally operating the engines at 75% of engine rated power. This allows for engine out capability. The new generation of main engines operates at significantly higher chamber pressure than the prior generation of gas generator cycle engines. The oxygen rich pre-burner engine cycle, unlike the fuel rich gas generator cycle, results in internally self-cleaning firings which facilitates reusability. Maintenance is further enhanced with integrated health monitoring to improve safety and turn-around efficiency. The maintainability of the LFBB LOX / kerosene engines is being improved by designing the vehicle/engine interfaces for easy access to key engine components.

Propulsion system advances that enable a reusable Liquid Fly Back Booster (LFBB)

NASA Technical Reports Server (NTRS)

Keith, E. L.; Rothschild, W. J.

1998-01-01

This paper provides an overview of the booster propulsion system for the Liquid Fly Back Booster (LFBB). This includes, system requirements, design approach, concept of operations, reliability, safety and cost assumptions. The paper summarizes the findings of the Boeing propulsion team that has been studying the LFBB feasibility as a booster replacement for the Space Shuttle. This paper will discuss recent advances including a new generation of kerosene and oxygen rich pre-burner staged combustion cycle main rocket engines. The engine reliability and safety is expected to be much higher than current standards by adding extra operating margins into the design and normally operating the engines at 75% of engine rated power. This allows for engine out capability. The new generation of main engines operates at significantly higher chamber pressure than the prior generation of gas generator cycle engines. The oxygen rich pre-burner engine cycle, unlike the fuel rich gas generator cycle, results in internally self-cleaning firings which facilitates reusability. Maintenance is further enhanced with integrated health monitoring to improve safety and turn-around efficiency. The maintainability of the LFBB LOX/kerosene engines is being improved by designing the vehicle/engine interfaces for easy access to key engine components.

A methodology for system-of-systems design in support of the engineering team

NASA Astrophysics Data System (ADS)

Ridolfi, G.; Mooij, E.; Cardile, D.; Corpino, S.; Ferrari, G.

2012-04-01

Space missions have experienced a trend of increasing complexity in the last decades, resulting in the design of very complex systems formed by many elements and sub-elements working together to meet the requirements. In a classical approach, especially in a company environment, the two steps of design-space exploration and optimization are usually performed by experts inferring on major phenomena, making assumptions and doing some trial-and-error runs on the available mathematical models. This is done especially in the very early design phases where most of the costs are locked-in. With the objective of supporting the engineering team and the decision-makers during the design of complex systems, the authors developed a modelling framework for a particular category of complex, coupled space systems called System-of-Systems. Once modelled, the System-of-Systems is solved using a computationally cheap parametric methodology, named the mixed-hypercube approach, based on the utilization of a particular type of fractional factorial design-of-experiments, and analysis of the results via global sensitivity analysis and response surfaces. As an applicative example, a system-of-systems of a hypothetical human space exploration scenario for the support of a manned lunar base is presented. The results demonstrate that using the mixed-hypercube to sample the design space, an optimal solution is reached with a limited computational effort, providing support to the engineering team and decision makers thanks to sensitivity and robustness information. The analysis of the system-of-systems model that was implemented shows that the logistic support of a human outpost on the Moon for 15 years is still feasible with currently available launcher classes. The results presented in this paper have been obtained in cooperation with Thales Alenia Space—Italy, in the framework of a regional programme called STEPS. STEPS—Sistemi e Tecnologie per l'EsPlorazione Spaziale is a research project co-financed by Piedmont Region and firms and universities of the Piedmont Aerospace District in the ambit of the P.O.R-F.E.S.R. 2007-2013 program.

Reaching Out: Team AETHER

NASA Technical Reports Server (NTRS)

Murphy, Gloria A.

2010-01-01

Embry Riddle Aeronautical University's Daytona Beach Campus Lunabotics Team took the opportunity to share the love of space, engineering and technology through the educational outreach portion of the competition. Through visits to elementary schools and high schools, and through support of science fairs and robotics competitions, younger generations were introduced to space, engineering and robotics. This report documents the outreach activities of team Aether.

Inspection of the Math Model Tools for On-Orbit Assessment of Impact Damage Report

NASA Technical Reports Server (NTRS)

Harris, Charles E.; Raju, Ivatury S.; Piascik, Robert S> ; KramerWhite, Julie A.; KramerWhite, Julie A.; Labbe, Steve G.; Rotter, Hank A.

2007-01-01

In Spring of 2005, the NASA Engineering Safety Center (NESC) was engaged by the Space Shuttle Program (SSP) to peer review the suite of analytical tools being developed to support the determination of impact and damage tolerance of the Orbiter Thermal Protection Systems (TPS). The NESC formed an independent review team with the core disciplines of materials, flight sciences, structures, mechanical analysis and thermal analysis. The Math Model Tools reviewed included damage prediction and stress analysis, aeroheating analysis, and thermal analysis tools. Some tools are physics-based and other tools are empirically-derived. Each tool was created for a specific use and timeframe, including certification, real-time pre-launch assessments. In addition, the tools are used together in an integrated strategy for assessing the ramifications of impact damage to tile and RCC. The NESC teams conducted a peer review of the engineering data package for each Math Model Tool. This report contains the summary of the team observations and recommendations from these reviews.

Spacelab Operations Support Room Space Engineering Support Team in the SL POCC During the IML-1

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Featured is the Spacelab Operations Support Room Space Engineering Support team in the SL POCC during STS-42, IML-1 mission.

2014-2689

NASA Image and Video Library

2014-05-23

CAPE CANAVERAL, Fla. -- NASA's 2014 Robotic Mining Competition award ceremony was held inside the Space Shuttle Atlantis attraction at the Kennedy Space Center Visitor Complex in Florida. More than 35 teams from colleges and universities around the U.S. designed and built remote-controlled robots for the mining competition, held May 19-23 at the visitor complex. The competition is a NASA Human Exploration and Operations Mission Directorate project designed to engage and retain students in science, technology, engineering and mathematics, or STEM, fields by expanding opportunities for student research and design. Teams use their remote-controlled robotics to maneuver and dig in a supersized sandbox filled with a crushed material that has characteristics similar to Martian soil. The objective of the challenge is to see which team’s robot can collect and move the most regolith within a specified amount of time. The competition includes on-site mining, writing a systems engineering paper, performing outreach projects for K-12 students, slide presentation and demonstrations, and team spirit. For more information, visit www.nasa.gov/nasarmc. Photo credit: NASA/Kim Shiflett

Final Report of the NASA Office of Safety and Mission Assurance Agile Benchmarking Team

NASA Technical Reports Server (NTRS)

Wetherholt, Martha

2016-01-01

To ensure that the NASA Safety and Mission Assurance (SMA) community remains in a position to perform reliable Software Assurance (SA) on NASAs critical software (SW) systems with the software industry rapidly transitioning from waterfall to Agile processes, Terry Wilcutt, Chief, Safety and Mission Assurance, Office of Safety and Mission Assurance (OSMA) established the Agile Benchmarking Team (ABT). The Team's tasks were: 1. Research background literature on current Agile processes, 2. Perform benchmark activities with other organizations that are involved in software Agile processes to determine best practices, 3. Collect information on Agile-developed systems to enable improvements to the current NASA standards and processes to enhance their ability to perform reliable software assurance on NASA Agile-developed systems, 4. Suggest additional guidance and recommendations for updates to those standards and processes, as needed. The ABT's findings and recommendations for software management, engineering and software assurance are addressed herein.

System verification and validation: a fundamental systems engineering task

NASA Astrophysics Data System (ADS)

Ansorge, Wolfgang R.

2004-09-01

Systems Engineering (SE) is the discipline in a project management team, which transfers the user's operational needs and justifications for an Extremely Large Telescope (ELT) -or any other telescope-- into a set of validated required system performance characteristics. Subsequently transferring these validated required system performance characteris-tics into a validated system configuration, and eventually into the assembled, integrated telescope system with verified performance characteristics and provided it with "objective evidence that the particular requirements for the specified intended use are fulfilled". The latter is the ISO Standard 8402 definition for "Validation". This presentation describes the verification and validation processes of an ELT Project and outlines the key role System Engineering plays in these processes throughout all project phases. If these processes are implemented correctly into the project execution and are started at the proper time, namely at the very beginning of the project, and if all capabilities of experienced system engineers are used, the project costs and the life-cycle costs of the telescope system can be reduced between 25 and 50 %. The intention of this article is, to motivate and encourage project managers of astronomical telescopes and scientific instruments to involve the entire spectrum of Systems Engineering capabilities performed by trained and experienced SYSTEM engineers for the benefit of the project by explaining them the importance of Systems Engineering in the AIV and validation processes.

Conversion from Tree to Graph Representation of Requirements

NASA Technical Reports Server (NTRS)

Mayank, Vimal; Everett, David Frank; Shmunis, Natalya; Austin, Mark

2009-01-01

A procedure and software to implement the procedure have been devised to enable conversion from a tree representation to a graph representation of the requirements governing the development and design of an engineering system. The need for this procedure and software and for other requirements-management tools arises as follows: In systems-engineering circles, it is well known that requirements- management capability improves the likelihood of success in the team-based development of complex systems involving multiple technological disciplines. It is especially desirable to be able to visualize (in order to identify and manage) requirements early in the system- design process, when errors can be corrected most easily and inexpensively.

Arizona Geology Trip - February 25-28, 2008

NASA Technical Reports Server (NTRS)

Thomas, Gretchen A.; Ross, Amy J.

2008-01-01

A variety of hardware developers, crew, mission planners, and headquarters personnel traveled to Gila Bend, Arizona, in February 2008 for a CxP Lunar Surface Systems Team geology experience. Participating in this field trip were the CxP Space Suit System (EC5) leads: Thomas (PLSS) and Ross (PGS), who presented the activities and findings learned from being in the field during this KC. As for the design of a new spacesuit system, this allowed the engineers to understand the demands this type of activity will have on NASA's hardware, systems, and planning efforts. The engineers also experienced the methods and tools required for lunar surface activity.

Teams begin their preparations for the FIRST competition

NASA Technical Reports Server (NTRS)

2000-01-01

Team 393 from Morristown, Ind., sets up its robot on a table to prepare it for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 at the KSC Visitor Complex. KSC is co-sponsoring the team, The Bee Bots, from Morristown Junior and Senior High Schools. On the floor at right is team 386, known as Voltage: The South Brevard First Team. This team is made up of students from Eau Gallie, Satellite, Palm Bay, Melbourne, Bayside and Melbourne Central Catholic High Schools. They are sponsored by KSC as well as Harris Corp., Intersil Corp., Interface & Control Systems. Inc. and Rockwell Collins. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing at KSC, 16 are Florida teams co-sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusville.

Bagging system, soil stabilization mat, and tent frame for a lunar base

NASA Technical Reports Server (NTRS)

1990-01-01

Georgia Tech's School of Textile and Fiber Engineering and School of Mechanical Engineering participated in four cooperative design efforts this year. Each of two interdisciplinary teams designed a system consisting of a lunar regolith bag and an apparatus for filling this bag. The third group designed a mat for stabilization of lunar soil during takeoff and landing, and a method for packaging and deploying this mat. Finally, the fourth group designed a sunlight diffusing tent to be used as a lunar worksite. Summaries of these projects are given.

Bagging system, soil stabilization mat, and tent frame for a lunar base

NASA Astrophysics Data System (ADS)

1990-11-01

Georgia Tech's School of Textile and Fiber Engineering and School of Mechanical Engineering participated in four cooperative design efforts this year. Each of two interdisciplinary teams designed a system consisting of a lunar regolith bag and an apparatus for filling this bag. The third group designed a mat for stabilization of lunar soil during takeoff and landing, and a method for packaging and deploying this mat. Finally, the fourth group designed a sunlight diffusing tent to be used as a lunar worksite. Summaries of these projects are given.

Ship to Shore Data Communication and Prioritization

DTIC Science & Technology

2011-12-01

First Out FTP File Transfer Protocol GCCS-M Global Command and Control System Maritime HAIPE High Assurance Internet Protocol Encryptor HTTP Hypertext...Transfer Protocol (world wide web protocol ) IBS Integrated Bar Code System IDEF0 Integration Definition IER Information Exchange Requirements...INTEL Intelligence IP Internet Protocol IPT Integrated Product Team ISEA In-Service Engineering Agent ISNS Integrated Shipboard Network System IT

A Virtual Mission Operations Center: Collaborative Environment

NASA Technical Reports Server (NTRS)

Medina, Barbara; Bussman, Marie; Obenschain, Arthur F. (Technical Monitor)

2002-01-01

The Virtual Mission Operations Center - Collaborative Environment (VMOC-CE) intent is to have a central access point for all the resources used in a collaborative mission operations environment to assist mission operators in communicating on-site and off-site in the investigation and resolution of anomalies. It is a framework that as a minimum incorporates online chat, realtime file sharing and remote application sharing components in one central location. The use of a collaborative environment in mission operations opens up the possibilities for a central framework for other project members to access and interact with mission operations staff remotely. The goal of the Virtual Mission Operations Center (VMOC) Project is to identify, develop, and infuse technology to enable mission control by on-call personnel in geographically dispersed locations. In order to achieve this goal, the following capabilities are needed: Autonomous mission control systems Automated systems to contact on-call personnel Synthesis and presentation of mission control status and history information Desktop tools for data and situation analysis Secure mechanism for remote collaboration commanding Collaborative environment for remote cooperative work The VMOC-CE is a collaborative environment that facilitates remote cooperative work. It is an application instance of the Virtual System Design Environment (VSDE), developed by NASA Goddard Space Flight Center's (GSFC) Systems Engineering Services & Advanced Concepts (SESAC) Branch. The VSDE is a web-based portal that includes a knowledge repository and collaborative environment to serve science and engineering teams in product development. It is a "one stop shop" for product design, providing users real-time access to product development data, engineering and management tools, and relevant design specifications and resources through the Internet. The initial focus of the VSDE has been to serve teams working in the early portion of the system/product lifecycle - concept development, proposal preparation, and formulation. The VMOC-CE expands the application of the VSDE into the operations portion of the system lifecycle. It will enable meaningful and real-time collaboration regardless of the geographical distribution of project team members. Team members will be able to interact in satellite operations, specifically for resolving anomalies, through access to a desktop computer and the Internet. Mission Operations Management will be able to participate and monitor up to the minute status of anomalies or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities, and technologies.

Missouri S&T formula electric racing.

DOT National Transportation Integrated Search

2014-05-01

The Formula Electric racing team will promote Missouri S&Ts engineering excellence by successfully competing against other top : engineering universities in the US and around the world. Students on the team will have the opportunity to reinforce t...

DART system analysis.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Boggs, Paul T.; Althsuler, Alan; Larzelere, Alex R.

2005-08-01

The Design-through-Analysis Realization Team (DART) is chartered with reducing the time Sandia analysts require to complete the engineering analysis process. The DART system analysis team studied the engineering analysis processes employed by analysts in Centers 9100 and 8700 at Sandia to identify opportunities for reducing overall design-through-analysis process time. The team created and implemented a rigorous analysis methodology based on a generic process flow model parameterized by information obtained from analysts. They also collected data from analysis department managers to quantify the problem type and complexity distribution throughout Sandia's analyst community. They then used this information to develop a communitymore » model, which enables a simple characterization of processes that span the analyst community. The results indicate that equal opportunity for reducing analysis process time is available both by reducing the ''once-through'' time required to complete a process step and by reducing the probability of backward iteration. In addition, reducing the rework fraction (i.e., improving the engineering efficiency of subsequent iterations) offers approximately 40% to 80% of the benefit of reducing the ''once-through'' time or iteration probability, depending upon the process step being considered. Further, the results indicate that geometry manipulation and meshing is the largest portion of an analyst's effort, especially for structural problems, and offers significant opportunity for overall time reduction. Iteration loops initiated late in the process are more costly than others because they increase ''inner loop'' iterations. Identifying and correcting problems as early as possible in the process offers significant opportunity for time savings.« less

Clinical Immersion: An Approach for Fostering Cross-disciplinary Communication and Innovation in Nursing and Engineering Students.

PubMed

Geist, Melissa J; Sanders, Robby; Harris, Kevin; Arce-Trigatti, Andrea; Hitchcock-Cass, Cary

2018-05-24

A faculty team from nursing and chemical engineering developed a course that brought together students from each discipline for cross-disciplinary, team-based clinical immersion and collaboration. Health care processes and devices are rapidly changing, and nurses are uniquely positioned to be bedside innovators to improve patient care delivery. During each clinical immersion, the student teams rotated through various hospital units where they identified problems and worked together in the university's makerspace (iMaker Space) to design and build prototypes to improve health outcomes. Data from the Critical thinking Assessment Test provided evidence of gains in critical-thinking and problem-solving skills, while the problems identified in the clinical setting and prototypes developed demonstrated the impact of bringing nursing and engineering students together to design innovations. When challenged to identify authentic problems during their clinical immersion, the teams of nursing and engineering students proposed creative solutions and developed commercially viable prototypes.

A Curriculum to Enhance Decision-Making Skills of Technical Personnel Working in Teams

ERIC Educational Resources Information Center

Raju, P. K.; Sankar, Chetan S.; Xue, Yajiong

2004-01-01

Rapidly changing engineering designs and business scenarios make it essential for engineers and technical personnel to be trained to be effective team players and project managers. This paper reports the experiences gained in developing and implementing a workshop to train engineers at a steel manufacturing plant. The objective of the workshop was…

Peer-Led Team Learning in Mathematics Courses for Freshmen Engineering and Computer Science Students

ERIC Educational Resources Information Center

Reisel, John R.; Jablonski, Marissa R.; Munson, Ethan; Hosseini, Hossein

2014-01-01

Peer-led Team Learning (PLTL) is an instructional method reported to increase student learning in STEM courses. As mathematics is a significant hurdle for many freshmen engineering students, a PLTL program was implemented for students to attempt to improve their course performance. Here, an analysis of PLTL for freshmen engineering students in…

Promoting Collaborative Problem-Solving Skills in a Course on Engineering Grand Challenges

ERIC Educational Resources Information Center

Zou, Tracy X. P.; Mickleborough, Neil C.

2015-01-01

The ability to solve problems with people of diverse backgrounds is essential for engineering graduates. A course on engineering grand challenges was designed to promote collaborative problem-solving (CPS) skills. One unique component is that students need to work both within their own team and collaborate with the other team to tackle engineering…

Research on Intelligent Synthesis Environment

NASA Technical Reports Server (NTRS)

Loftin, R. Bowen; Dryer, David; Major, Debra; Fletcher, Tom

2002-01-01

The ultimate goal of this research project is to develop a methodology for the assessment and continuous improvement of engineering team effectiveness in distributed collaborative environments. This review provides the theoretical foundation upon which subsequent empirical work will be based. Our review of the team performance literature has identified the following 12 conceptually distinct team interaction processes as characteristic of effective teams. 1) Mission Analysis; 2) Resource Distribution; 3) Leadership; 4) Timing; 5) Intra-team Feedback; 6) Motivational Functions; 7) Team Orientation; 8) Communication; 9) Coordination; 10) Mutual Performance Monitoring; 11) Back-up Behaviors; and 12) Cooperation. In addition, this review summarizes how team task characteristics (i.e., task type, task complexity, motivation, and temporal changes), team characteristics (i.e., team structure and team knowledge), and individual team member characteristics (i.e., dispositions and teamwork knowledge, skills, and abilities) affect team interaction processes, determine the relevance of these processes, and influence team performance. The costs and benefits of distributed team collaboration are also considered. The review concludes with a brief discussion of the nature of collaborative team engineering tasks.

Research on Intelligent Synthesis Environment

NASA Astrophysics Data System (ADS)

Loftin, R. Bowen; Dryer, David; Major, Debra; Fletcher, Tom

2002-10-01

The ultimate goal of this research project is to develop a methodology for the assessment and continuous improvement of engineering team effectiveness in distributed collaborative environments. This review provides the theoretical foundation upon which subsequent empirical work will be based. Our review of the team performance literature has identified the following 12 conceptually distinct team interaction processes as characteristic of effective teams. 1) Mission Analysis; 2) Resource Distribution; 3) Leadership; 4) Timing; 5) Intra-team Feedback; 6) Motivational Functions; 7) Team Orientation; 8) Communication; 9) Coordination; 10) Mutual Performance Monitoring; 11) Back-up Behaviors; and 12) Cooperation. In addition, this review summarizes how team task characteristics (i.e., task type, task complexity, motivation, and temporal changes), team characteristics (i.e., team structure and team knowledge), and individual team member characteristics (i.e., dispositions and teamwork knowledge, skills, and abilities) affect team interaction processes, determine the relevance of these processes, and influence team performance. The costs and benefits of distributed team collaboration are also considered. The review concludes with a brief discussion of the nature of collaborative team engineering tasks.

Conducting Closed Habitation Experiments: Experience from the Lunar Mars Life Support Test Project

NASA Technical Reports Server (NTRS)

Barta, Daniel J.; Edeen, Marybeth A.; Henninger, Donald L.

2004-01-01

The Lunar-Mars Life Support Test Project (LMLSTP) was conducted from 1995 through 1997 at the National Aeronautics and Space Administration s (NASA) Johnson Space Center (JSC) to demonstrate increasingly longer duration operation of integrated, closed-loop life support systems that employed biological and physicochemical techniques for water recycling, waste processing, air revitalization, thermal control, and food production. An analog environment for long-duration human space travel, the conditions of isolation and confinement also enabled studies of human factors, medical sciences (both physiology and psychology) and crew training. Four tests were conducted, Phases I, II, IIa and III, with durations of 15, 30,60 and 91 days, respectively. The first phase focused on biological air regeneration, using wheat to generate enough oxygen for one experimental subject. The systems demonstrated in the later phases were increasingly complex and interdependent, and provided life support for four crew members. The tests were conducted using two human-rated, atmospherically-closed test chambers, the Variable Pressure Growth Chamber (VPGC) and the Integrated Life Support Systems Test Facility (ILSSTF). Systems included test articles (the life support hardware under evaluation), human accommodations (living quarters, kitchen, exercise equipment, etc.) and facility systems (emergency matrix system, power, cooling, etc.). The test team was managed by a lead engineer and a test director, and included test article engineers responsible for specific systems, subsystems or test articles, test conductors, facility engineers, chamber operators and engineering technicians, medical and safety officers, and science experimenters. A crew selection committee, comprised of psychologists, engineers and managers involved in the test, evaluated male and female volunteers who applied to be test subjects. Selection was based on the skills mix anticipated for each particular test, and utilized information from psychological and medical testing, data on the knowledge, experience and skills of the applicants, and team building exercises. The design, development, buildup and operation of test hardware and documentation followed the established NASA processes and requirements for test buildup and operation.

Conducting Closed Habitation Experiments: Experience from the Lunar Mars Life Support Test Project

NASA Technical Reports Server (NTRS)

Barta, Daniel J.; Edeen, Marybeth A.; Henninger, Donald L.

2006-01-01

The Lunar-Mars Life Support Test Project (LMLSTP) was conducted from 1995 through 1997 at the National Aeronautics and Space Administration s (NASA) Johnson Space Center (JSC) to demonstrate increasingly longer duration operation of integrated, closed-loop life support systems that employed biological and physicochemical techniques for water recycling, waste processing, air revitalization, thermal control, and food production. An analog environment for long-duration human space travel, the conditions of isolation and confinement also enabled studies of human factors, medical sciences (both physiology and psychology) and crew training. Four tests were conducted, Phases I, II, IIa and III, with durations of 15, 30, 60 and 91 days, respectively. The first phase focused on biological air regeneration, using wheat to generate enough oxygen for one experimental subject. The systems demonstrated in the later phases were increasingly complex and interdependent, and provided life support for four crew members. The tests were conducted using two human-rated, atmospherically-closed test chambers, the Variable Pressure Growth Chamber (VPGC) and the Integrated Life Support Systems Test Facility (ILSSTF). Systems included test articles (the life support hardware under evaluation), human accommodations (living quarters, kitchen, exercise equipment, etc.) and facility systems (emergency matrix system, power, cooling, etc.). The test team was managed by a lead engineer and a test director, and included test article engineers responsible for specific systems, subsystems or test articles, test conductors, facility engineers, chamber operators and engineering technicians, medical and safety officers, and science experimenters. A crew selection committee, comprised of psychologists, engineers and managers involved in the test, evaluated male and female volunteers who applied to be test subjects. Selection was based on the skills mix anticipated for each particular test, and utilized information from psychological and medical testing, data on the knowledge, experience and skills of the applicants, and team building exercises. The design, development, buildup and operation of test hardware and documentation followed the established NASA processes and requirements for test buildup and operation.

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA Technical Reports Server (NTRS)

Bolton, Albanie T.

2016-01-01

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Effectiveness of Systems Engineering (SE) Tailored for the Science & Technology (S&T) Environment: Improvement of USAF Airdrop Accuracy

DTIC Science & Technology

2011-10-27

public release; distribution is unlimited  Dr. Keith Bowman, AFRL, Precision Airdrop ( PAD ) Program Manager  Ms. Carol Ventresca, SynGenics Corporation...Presentation Outline  Entrance Criteria for PAD  Integrated Product Team (IPT)  S&T SE Process Steps  Initial Project S&T Development Strategy...Entrance Criteria for PAD  Integrated Product Team (IPT)  S&T SE Process Steps  Initial Project S&T Development Strategy  User Understanding of

Use of activity theory-based need finding for biomedical device development.

PubMed

Rismani, Shalaleh; Ratto, Matt; Machiel Van der Loos, H F

2016-08-01

Identifying the appropriate needs for biomedical device design is challenging, especially for less structured environments. The paper proposes an alternate need-finding method based on Cultural Historical Activity Theory and expanded to explicitly examine the role of devices within a socioeconomic system. This is compared to a conventional need-finding technique in a preliminary study with engineering student teams. The initial results show that the Activity Theory-based technique allows teams to gain deeper insights into their needs space.

Improving collaborative learning in online software engineering education

NASA Astrophysics Data System (ADS)

Neill, Colin J.; DeFranco, Joanna F.; Sangwan, Raghvinder S.

2017-11-01

Team projects are commonplace in software engineering education. They address a key educational objective, provide students critical experience relevant to their future careers, allow instructors to set problems of greater scale and complexity than could be tackled individually, and are a vehicle for socially constructed learning. While all student teams experience challenges, those in fully online programmes must also deal with remote working, asynchronous coordination, and computer-mediated communications all of which contribute to greater social distance between team members. We have developed a facilitation framework to aid team collaboration and have demonstrated its efficacy, in prior research, with respect to team performance and outcomes. Those studies indicated, however, that despite experiencing improved project outcomes, students working in effective software engineering teams did not experience significantly improved individual achievement. To address this deficiency we implemented theoretically grounded refinements to the collaboration model based upon peer-tutoring research. Our results indicate a modest, but statistically significant (p = .08), improvement in individual achievement using this refined model.

Team 282 prepares for the FIRST competition

NASA Technical Reports Server (NTRS)

2000-01-01

The Orange Crusher team (282) works on their robot, which is named Rust Bot, during the FIRST competition. The team of students from Lake Howell, Winter Springs and Orange Christian Private high schools was co-sponsored by NASA Kennedy Space Center, Matern Professional Engineering The Foundation, Control Technologies, Lucent Technologies and Sandy Engineering. Students from all over the country are at the KSC Visitor Complex for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 in the Rocket Garden. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing, 16 are Florida teams co- sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusville.

Keeping Cool With Solar-Powered Refrigeration

NASA Technical Reports Server (NTRS)

2003-01-01

In the midst of developing battery-free, solar-powered refrigeration and air conditioning systems for habitats in space, David Bergeron, the team leader for NASA's Advanced Refrigerator Technology Team at Johnson Space Center, acknowledged the need for a comparable solar refrigerator that could operate in conjunction with the simple lighting systems already in place on Earth. Bergeron, a 20-year veteran in the aerospace industry, founded the company Solus Refrigeration, Inc., in 1999 to take the patented advanced refrigeration technology he co-developed with his teammate, Johnson engineer Michael Ewert, to commercial markets. Now known as SunDanzer Refrigeration, Inc., Bergeron's company is producing battery-free, photovoltaic (PV) refrigeration systems under license to NASA, and selling them globally.

Teaching medical management and operations engineering for systems-based practice to radiology residents.

PubMed

Brandon, Catherine J; Mullan, Patricia B

2013-03-01

To better prepare radiology residents for providing care within the context of the larger health care system, this study evaluated the feasibility and impact of a curriculum to enhance radiology residents' understanding and ability to apply concepts from medical management and industrial and operational engineering to systems-based practice problems in radiology practice. A multiprofessional team including radiology, medical education, and industrial and operational engineering professionals collaborated in developing a seven-module curriculum, including didactic lectures, interactive large-group analysis, and small-group discussions with case-based radiology examples, which illustrated real-life management issues and the roles physicians held. Residents and faculty participated in topic selection. Pre- and post-instruction formative assessments were administered, and results were shared with residents during teaching sessions. Attendance and participation in case-based scenario resolutions indicate the feasibility and impact of the interactive curriculum on residents' interest and ability to apply curricular concepts to systems-based practice in radiology. Paired t test analyses (P < .05) and effect sizes showed residents significantly increased their knowledge and ability to apply concepts to systems-based practice issues in radiology. Our iterative curriculum development and implementation process demonstrated need and support for a multiprofessional team approach to teach management and operational engineering concepts. Curriculum topics are congruent with Accreditation Council for Graduate Medical Education requirements for systems-based practice. The case-based curriculum using a mixed educational format of didactic lectures and small-group discussion and problem analysis could be adopted for other radiology programs, for both residents and continuing medical education applications. Copyright © 2013 AUR. Published by Elsevier Inc. All rights reserved.

Tinkering self-efficacy and team interaction on freshman engineering design teams

NASA Astrophysics Data System (ADS)

Richardson, Arlisa Labrie

This study utilizes Bandura's theory of self-efficacy as a framework to examine the development of tinkering skills white working on a freshman engineering design team. The four sources of self-efficacy were analyzed in the context of tinkering within the design team. The research question, 'Does tinkering self-efficacy change for female students during the Freshman Engineering Design class while working on mixed sex teams?', was addressed using quantitative data collection and field observations. Approximately 41 students enrolled in a freshman engineering design class at a public university in the southwest participated by providing self-reports about their tinkering involvement during each design project. In addition, three mixed-sex student teams were observed while working to complete the course design projects. An observation protocol based on Bandura's sources of self efficacy, was used to document tinkering interactions within the three observed teams. The results revealed that Bandura's sources of self-efficacy influenced tinkering involvement. The self-efficacy source, performance accomplishment measured through prior tinkering experience, was the most influential on tinkering involvement. Unlike Bandura's ranking of influence, verbal persuasion was shown to correlate with more tinkering behaviors than the observation of others. The number of females on a team had no impact on tinkering involvement. Tinkering involvement did not change as students progressed from one project to another. However, the competitive nature of the design project appeared to have a negative impact on tinkering involvement and the division of tasks within the team. In addition, a difference was found in the female students' perception of their tinkering involvement and observation of their tinkering involvement. The findings suggest that effective implementation of teamwork including teamwork preparation, more emphasis on the design process and the elimination of competition between teams are necessary to create a more equitable learning environment.

Gender and Modes of Collaboration in an Engineering Classroom: A Profile of Two Women on Student Teams.

ERIC Educational Resources Information Center

Ingram, Sandra; Parker, Anne

2002-01-01

Profiles two women from student engineering teams who participated in a study on collaboration and the role of gender. Shows that men and women alike displayed both gender-linked and non-gender-linked behavior, and that successful collaboration was influenced less by gender and more by such factors as a strong work ethic, team commitment, and…

Recent Experiences of the NASA Engineering and Safety Center (NESC) Guidance Navigation and Control (GN and C) Technical Discipline Team (TDT)

NASA Technical Reports Server (NTRS)

Dennehy, Cornelius J.

2011-01-01

The NASA Engineering and Safety Center (NESC) is an independently funded NASA Program whose dedicated team of technical experts provides objective engineering and safety assessments of critical, high risk projects. NESC's strength is rooted in the diverse perspectives and broad knowledge base that add value to its products, affording customers a responsive, alternate path for assessing and preventing technical problems while protecting vital human and national resources. The Guidance Navigation and Control (GN&C) Technical Discipline Team (TDT) is one of fifteen such discipline-focused teams within the NESC organization. The TDT membership is composed of GN&C specialists from across NASA and its partner organizations in other government agencies, industry, national laboratories, and universities. This paper will briefly define the vision, mission, and purpose of the NESC organization. The role of the GN&C TDT will then be described in detail along with an overview of how this team operates and engages in its objective engineering and safety assessments of critical NASA.

KSC-99pp0289

NASA Image and Video Library

1999-03-06

At the award ceremony for the 1999 FIRST Southeastern Regional robotic competition held at KSC, the Space Coast FIRST Team walks past the greeting line. In the middle, shaking hands with the team, are KSC's Director of Engineering Development Sterling Walker (left) and Center Director Roy Bridges (right). The Space Coast Team included Rockledge, Cocoa Beach and Merritt Island High Schools. FIRST is a nonprofit organization, For Inspiration and Recognition of Science and Technology, that sponsors the event pitting gladiator robots against each other in an athletic-style competition. The FIRST robotics competition is designed to provide students with a hands-on, inside look at engineering and other professional careers, pairing high school students with engineer mentors and corporations. The regional event comprised 27 teams. Along with the championship award, which went to high school teams from Miami and San German, Puerto Rico, 15 other awards were presented

KSC00pp0325

NASA Image and Video Library

2000-03-10

The Orange Crusher team (282) works on their robot, which is named Rust Bot, during the FIRST competition. The team of students from Lake Howell, Winter Springs and Orange Christian Private high schools was co-sponsored by NASA Kennedy Space Center, Matern Professional Engineering The Foundation, Control Technologies, Lucent Technologies and Sandy Engineering. Students from all over the country are at the KSC Visitor Complex for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 in the Rocket Garden. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing, 16 are Florida teams co-sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusvill

KSC-00pp0325

NASA Image and Video Library

2000-03-10

The Orange Crusher team (282) works on their robot, which is named Rust Bot, during the FIRST competition. The team of students from Lake Howell, Winter Springs and Orange Christian Private high schools was co-sponsored by NASA Kennedy Space Center, Matern Professional Engineering The Foundation, Control Technologies, Lucent Technologies and Sandy Engineering. Students from all over the country are at the KSC Visitor Complex for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 in the Rocket Garden. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing, 16 are Florida teams co-sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusvill

SHARP's systems engineering challenge: rectifying integrated product team requirements with performance issues in an evolutionary spiral development acquisition

NASA Astrophysics Data System (ADS)

Kuehl, C. Stephen

2003-08-01

Completing its final development and early deployment on the Navy's multi-role aircraft, the F/A-18 E/F Super Hornet, the SHAred Reconnaissance Pod (SHARP) provides the war fighter with the latest digital tactical reconnaissance (TAC Recce) Electro-Optical/Infrared (EO/IR) sensor system. The SHARP program is an evolutionary acquisition that used a spiral development process across a prototype development phase tightly coupled into overlapping Engineering and Manufacturing Development (EMD) and Low Rate Initial Production (LRIP) phases. Under a tight budget environment with a highly compressed schedule, SHARP challenged traditional acquisition strategies and systems engineering (SE) processes. Adopting tailored state-of-the-art systems engineering process models allowd the SHARP program to overcome the technical knowledge transition challenges imposed by a compressed program schedule. The program's original goal was the deployment of digital TAC Recce mission capabilities to the fleet customer by summer of 2003. Hardware and software integration technical challenges resulted from requirements definition and analysis activities performed across a government-industry led Integrated Product Team (IPT) involving Navy engineering and test sites, Boeing, and RTSC-EPS (with its subcontracted hardware and government furnished equipment vendors). Requirements development from a bottoms-up approach was adopted using an electronic requirements capture environment to clarify and establish the SHARP EMD product baseline specifications as relevant technical data became available. Applying Earned-Value Management (EVM) against an Integrated Master Schedule (IMS) resulted in efficiently managing SE task assignments and product deliveries in a dynamically evolving customer requirements environment. Application of Six Sigma improvement methodologies resulted in the uncovering of root causes of errors in wiring interconnectivity drawings, pod manufacturing processes, and avionics requirements specifications. Utilizing the draft NAVAIR SE guideline handbook and the ANSI/EIA-632 standard: Processes for Engineering a System, a systems engineering tailored process approach was adopted for the accelerated SHARP EMD prgram. Tailoring SE processes in this accelerated product delivery environment provided unique opportunities to be technically creative in the establishment of a product performance baseline. This paper provides an historical overview of the systems engineering activities spanning the prototype phase through the EMD SHARP program phase, the performance requirement capture activities and refinement process challenges, and what SE process improvements can be applied to future SHARP-like programs adopting a compressed, evolutionary spiral development acquisition paradigm.

NASA advanced design program. Design and analysis of a radio-controlled flying wing aircraft

NASA Technical Reports Server (NTRS)

1993-01-01

The main challenge of this project was to design an aircraft that will achieve stability while flying without a horizontal tail. The project focused on both the design, analysis and construction of a remotely piloted, elliptical shaped flying wing. The design team was composed of four sub-groups each of which dealt with the different aspects of the design, namely aerodynamics, stability and control, propulsion, and structures. Each member of the team initially researched the background information pertaining to specific facets of the project. Since previous work on this topic was limited, most of the focus of the project was directed towards developing an understanding of the natural instability of the aircraft. Once the design team entered the conceptual stage of the project, a series of compromises had to be made to satisfy the unique requirements of each sub-group. As a result of the numerous calculations and iterations necessary, computers were utilized extensively. In order to visualize the design and layout of the wing, engines and control surfaces, a solid modeling package was used to evaluate optimum design placements. When the design was finalized, construction began with the help of all the members of the project team. The nature of the carbon composite construction process demanded long hours of manual labor. The assembly of the engine systems also required precision hand work. The final product of this project is the Elang, a one-of-a-kind remotely piloted aircraft of composite construction powered by two ducted fan engines.

A Technical Report To The Secretary Of Transportation On A National Approach To Augmented Gps Services

DOT National Transportation Integrated Search

1994-12-01

THIS REPORT DOCUMENTS THE DEVELOPMENT OF RECOMMENDATIONS FOR A NATIONAL APPROACH TO AUGMENTED GLOBAL POSITIONING SYSTEM (GPS) SERVICES. THE INSTITUTE FOR TELECOMMUNICATION SCIENCES LED A STUDY TEAM THAT INCLUDED THE U.S. ARMY TOPOGRAPHIC ENGINEERING ...

User engineering: A new look at system engineering

NASA Technical Reports Server (NTRS)

Mclaughlin, Larry L.

1987-01-01

User Engineering is a new System Engineering perspective responsible for defining and maintaining the user view of the system. Its elements are a process to guide the project and customer, a multidisciplinary team including hard and soft sciences, rapid prototyping tools to build user interfaces quickly and modify them frequently at low cost, and a prototyping center for involving users and designers in an iterative way. The main consideration is reducing the risk that the end user will not or cannot effectively use the system. The process begins with user analysis to produce cognitive and work style models, and task analysis to produce user work functions and scenarios. These become major drivers of the human computer interface design which is presented and reviewed as an interactive prototype by users. Feedback is rapid and productive, and user effectiveness can be measured and observed before the system is built and fielded. Requirements are derived via the prototype and baselined early to serve as an input to the architecture and software design.

Standard CMMI (Registered Trademark) Appraisal Method for Process Improvement (SCAMPI (Service Mark)) A, Version 1.3: Method Definition Document

DTIC Science & Technology

2011-03-01

performance of Federal Government Contract Number FA8721-05- C -0003 with Carnegie Mellon University for the operation of the Software Engineering... C Roles and Responsibilities 195 Appendix D Reporting Requirements and Options 201 Appendix E Managed Discovery 203 Appendix F Scoping and...Upgrade Team (SUT) • Mary Busby , Lockheed Martin • Palma Buttles-Valdez, Software Engineering Institute • Paul Byrnes, Integrated System Diagnostics

1400879

NASA Image and Video Library

2014-08-13

AIDING IN THE OFFICIAL BUILDING 4220 RIBBON-CUTTING ARE, FROM LEFT, JOHN HONEYCUTT, DEPUTY MANAGER OF THE SPACE LAUNCH SYSTEM PROGRAM OFFICE; LT. COL. TOM NELSON, DEPUTY COMMANDER OF THE U.S. ARMY CORPS OF ENGINEERS-MOBILE DISTRICT; U.S. SEN. JEFF SESSIONS OF ALABAMA; MARSHALL CENTER DIRECTOR PATRICK SCHEUERMANN; U.S. REP. MO BROOKS OF ALABAMA'S 5TH DISTRICT; MARSHALL DEPUTY DIRECTOR TERESA VANHOOSER; AND MARSHALL ENGINEER DAVID SKRIDULIS, TEAM LEAD FOR THE FACILITIES MANAGEMENT OFFICE'S CIVIL STRUCTURAL GROUP.

A-1 Test Stand modifications

NASA Image and Video Library

2011-09-14

Team members check the progress of a liquid nitrogen cold shock test on the A-1 Test Stand at Stennis Space Center on Sept. 15. The cold shock test is used to confirm the test stand's support system can withstand test conditions, when super-cold rocket engine propellant is piped. The A-1 Test Stand is preparing to conduct tests on the powerpack component of the J-2X rocket engine, beginning in early 2012.

Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report

DTIC Science & Technology

2010-03-01

instrumental in formulating the concepts and approaches presented in this report: Dan Burton, Anita Carleton, Timothy Chick, Mike Fehring, Watts Humphrey ...Senate,” GAO-04-393, Defense Acquisitions, 2004. http://www.gao.gov/new.items/d04393.pdf [ Humphrey 06] W. S . Humphrey , TSP: Leading a Development... Humphrey 08] W. S . Humphrey , “The Process Revolution,” CrossTalk The Journal of Defense Software Engineering, August 2008, Volume 28 Number 8

An Artificial Neural Network-Based Decision-Support System for Integrated Network Security

DTIC Science & Technology

2014-09-01

group that they need to know in order to make team-based decisions in real-time environments, (c) Employ secure cloud computing services to host mobile...THESIS Presented to the Faculty Department of Electrical and Computer Engineering Graduate School of Engineering and Management Air Force...out-of-the-loop syndrome and create complexity creep. As a result, full automation efforts can lead to inappropriate decision-making despite a

Booster Main Engine Selection Criteria for the Liquid Fly-Back Booster

NASA Technical Reports Server (NTRS)

Ryan, Richard M.; Rothschild, William J.; Christensen, David L.

1998-01-01

The Liquid Fly-Back Booster (LFBB) Program seeks to enhance the Space Shuttle system safety performance and economy of operations through the use of an advanced, liquid propellant Booster Main Engine (BME). There are several viable BME candidates that could be suitable for this application. The objective of this study was to identify the key criteria to be applied in selecting among these BME candidates. This study involved an assessment of influences on the overall LFBB utility due to variations in the candidate rocket engines' characteristics. This includes BME impacts on vehicle system weight, perfortnance,design approaches, abort modes, margins of safety, engine-out operations, and maintenance and support concepts. Systems engineering analyses and trade studies were performed to identify the LFBB system level sensitivities to a wide variety of BME related parameters. This presentation summarizes these trade studies and the resulting findings of the LFBB design teams regarding the BME characteristics that most significantly affect the LFBB system. The resulting BME choice should offer the best combination of reliability, performance, reusability, robustness, cost, and risk for the LFBB program.

Booster Main Engine Selection Criteria for the Liquid Fly-Back Booster

NASA Technical Reports Server (NTRS)

Ryan, Richard M.; Rothschild, William J.; Christensen, David L.

1998-01-01

The Liquid Fly-Back Booster (LFBB) Program seeks to enhance the Space Shuttle system safety, performance and economy of operations through the use of an advanced, liquid propellant Booster Main Engine (BME). There are several viable BME candidates that could be suitable for this application. The objective of this study was to identify the key Criteria to be applied in selecting among these BME candidates. This study involved an assessment of influences on the overall LFBB utility due to variations in the candidate rocket-engines characteristics. This includes BME impacts on vehicle system weight, performance, design approaches, abort modes, margins of safety, engine-out operations, and maintenance and support concepts. Systems engineering analyses and trade studies were performed to identify the LFBB system level sensitivities to a wide variety of BME related parameters. This presentation summarizes these trade studies and the resulting findings of the LFBB design teams regarding the BME characteristics that most significantly affect the LFBB system. The resulting BME choice should offer the best combination of reliability, performance, reusability, robustness, cost, and risk for the LFBB program.

Marquardt's Mach 4.5 Supercharged Ejector Ramjet (SERJ) High-Performance Aircraft Engine Project: Unfulfilled Aspirations Ca.1970

NASA Technical Reports Server (NTRS)

Escher, William J. D.; Roddy, Jordan E.; Hyde, Eric H.

2000-01-01

The Supercharged Ejector Ramjet (SERJ) engine developments of the 1960s, as pursued by The Marquardt Corporation and its associated industry team members, are described. In just three years, engineering work on this combined-cycle powerplant type evolved, from its initial NASA-sponsored reusable space transportation system study status, into a U.S. Air Force/Navy-supported exploratory development program as a candidate 4.5 high-performance military aircraft engine. Bridging a productive transition from the spaceflight to the aviation arena, this case history supports the expectation that fully-integrated airbreathing/rocket propulsion systems hold high promise toward meeting the demanding propulsion requirements of tomorrow's aircraft-like Spaceliner class transportation systems. Lessons to be learned from this "SERJ Story" are offered for consideration by today's advanced space transportation and combined-cycle propulsion researchers and forward-planning communities.

PNNL Development and Analysis of Material-Based Hydrogen Storage Systems for the Hydrogen Storage Engineering Center of Excellence

DOE Office of Scientific and Technical Information (OSTI.GOV)

Brooks, Kriston P.; Alvine, Kyle J.; Johnson, Kenneth I.

The Hydrogen Storage Engineering Center of Excellence is a team of universities, industrial corporations, and federal laboratories with the mandate to develop lower-pressure, materials-based, hydrogen storage systems for hydrogen fuel cell light-duty vehicles. Although not engaged in the development of new hydrogen storage materials themselves, it is an engineering center that addresses engineering challenges associated with the currently available hydrogen storage materials. Three material-based approaches to hydrogen storage are being researched: 1) chemical hydrogen storage materials 2) cryo-adsorbents, and 3) metal hydrides. As a member of this Center, Pacific Northwest National Laboratory (PNNL) has been involved in the design andmore » evaluation of systems developed with each of these three hydrogen storage materials. This report is a compilation of the work performed by PNNL for this Center.« less

Excite Kids about Engineering: Design Squad[TM] and Engineer Your Life[TM] Resources Make It Easy

ERIC Educational Resources Information Center

Cheng, Jack

2008-01-01

The author discusses "Design Squad", a television program designed to introduce students to the engineering process. Each episode tells the story of how two teams tackled a particular challenge. A graphic announces each stage (e.g., brainstorm, design, build, test, and redesign) as the teams construct their solutions. These graphics make visual…

New Tool Released for Engine-Airframe Blade-Out Structural Simulations

NASA Technical Reports Server (NTRS)

Lawrence, Charles

2004-01-01

Researchers at the NASA Glenn Research Center have enhanced a general-purpose finite element code, NASTRAN, for engine-airframe structural simulations during steady-state and transient operating conditions. For steady-state simulations, the code can predict critical operating speeds, natural modes of vibration, and forced response (e.g., cabin noise and component fatigue). The code can be used to perform static analysis to predict engine-airframe response and component stresses due to maneuver loads. For transient response, the simulation code can be used to predict response due to bladeoff events and subsequent engine shutdown and windmilling conditions. In addition, the code can be used as a pretest analysis tool to predict the results of the bladeout test required for FAA certification of new and derivative aircraft engines. Before the present analysis code was developed, all the major aircraft engine and airframe manufacturers in the United States and overseas were performing similar types of analyses to ensure the structural integrity of engine-airframe systems. Although there were many similarities among the analysis procedures, each manufacturer was developing and maintaining its own structural analysis capabilities independently. This situation led to high software development and maintenance costs, complications with manufacturers exchanging models and results, and limitations in predicting the structural response to the desired degree of accuracy. An industry-NASA team was formed to overcome these problems by developing a common analysis tool that would satisfy all the structural analysis needs of the industry and that would be available and supported by a commercial software vendor so that the team members would be relieved of maintenance and development responsibilities. Input from all the team members was used to ensure that everyone's requirements were satisfied and that the best technology was incorporated into the code. Furthermore, because the code would be distributed by a commercial software vendor, it would be more readily available to engine and airframe manufacturers, as well as to nonaircraft companies that did not previously have access to this capability.

Ambient Pressure Test Rig Developed for Testing Oil-Free Bearings in Alternate Gases and Variable Pressures

NASA Technical Reports Server (NTRS)

Bauman, Steven W.

1990-01-01

The Oil-Free Turbomachinery research team at the NASA Glenn Research Center is conducting research to develop turbomachinery systems that utilize high-speed, high temperature foil (air) bearings that do not require an oil lubrication system. Such systems combine the most advanced foil bearings from industry with NASA-developed hightemperature solid-lubricant technology. New applications are being pursued, such as Oil- Free turbochargers, auxiliary power units, and turbine propulsion systems for aircraft. An Oil-Free business jet engine, for example, would be simpler, lighter, more reliable, and less costly to purchase and maintain than current engines. Another application is NASA's Prometheus mission, where gas bearings will be required for the closed-cycle turbine based power-conversion system of a nuclear power generator for deep space. To support these applications, Glenn's Oil-Free Turbomachinery research team developed the Ambient Pressure Test Rig. Using this facility, researchers can load and heat a bearing and evaluate its performance with reduced air pressure to simulate high altitude conditions. For the nuclear application, the test chamber can be purged with gases such as helium to study foil gas bearing operation in working fluids other than air.

KSC-00pp0315

NASA Image and Video Library

2000-03-09

Team 393 from Morristown, Ind., sets up its robot on a table to prepare it for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 at the KSC Visitor Complex. KSC is co-sponsoring the team, The Bee Bots, from Morristown Junior and Senior High Schools. On the floor at right is team 386, known as Voltage: The South Brevard First Team. This team is made up of students from Eau Gallie, Satellite, Palm Bay, Melbourne, Bayside and Melbourne Central Catholic High Schools. They are sponsored by KSC as well as Harris Corp., Intersil Corp., Interface & Control Systems. Inc. and Rockwell Collins. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing at KSC, 16 are Florida teams co-sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusville

KSC00pp0315

NASA Image and Video Library

2000-03-09

Team 393 from Morristown, Ind., sets up its robot on a table to prepare it for the FIRST (For Inspiration and Recognition of Science and Technology) Southeast Regional competition March 9-11 at the KSC Visitor Complex. KSC is co-sponsoring the team, The Bee Bots, from Morristown Junior and Senior High Schools. On the floor at right is team 386, known as Voltage: The South Brevard First Team. This team is made up of students from Eau Gallie, Satellite, Palm Bay, Melbourne, Bayside and Melbourne Central Catholic High Schools. They are sponsored by KSC as well as Harris Corp., Intersil Corp., Interface & Control Systems. Inc. and Rockwell Collins. Teams of high school students are testing the limits of their imagination using robots they have designed, with the support of business and engineering professionals and corporate sponsors, to compete in a technological battle against other schools' robots. Of the 30 high school teams competing at KSC, 16 are Florida teams co-sponsored by NASA and KSC contractors. Local high schools participating are Astronaut, Bayside, Cocoa Beach, Eau Gallie, Melbourne, Melbourne Central Catholic, Palm Bay, Rockledge, Satellite, and Titusville

Red gaming in support of the war on terrorism : Sandia Red Game report.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Moore, Judy Hennessey; Whitley, John B.; Craft, Richard Layne, II

2004-02-01

The Advanced Concepts Group (ACG) at Sandia National Laboratories is exploring the use of Red Teaming to help intelligence analysts with two key processes: determining what a piece or pieces of information might imply and deciding what other pieces of information need to be found to support or refute hypotheses about what actions a suspected terrorist organization might be pursuing. In support of this effort, the ACG hosted a terrorism red gaming event in Albuquerque on July 22-24, 2003. The game involved two 'red teams' playing the roles of two terrorist cells - one focused on implementing an RDD attackmore » on the DC subway system and one focused on a bio attack against the same target - and two 'black teams' playing the role of the intelligence collection system and of intelligence analysts trying to decide what plans the red teams might be pursuing. This exercise successfully engaged human experts to seed a proposed compute engine with detailed operational plans for hypothetical terrorist scenarios.« less

How Systems Engineering and Risk Management Defend Against Murphy's Law and Human Error

NASA Technical Reports Server (NTRS)

Bay, Michael; Connley, Warren

2004-01-01

Systems Engineering and Risk Management processes can work synergistically to defend against the causes of many mission ending failures. Defending against mission ending failures is facilitated by fostering a team that has a healthy respect for Murphy's Law and a team with a of curiosity for how things work, how they can fail, and what they need to know. This curiosity is channeled into making the unknowns known or what is uncertain more certain. Efforts to assure mission success require the expenditure of energy in the following areas: 1. Understanding what defines Mission Success as guided by the customer's needs, objectives and constraints. 2. Understanding how the system is supposed to work and how the system is to be produced, fueled by the curiosity of how the system should work and how it should be produced. 3. Understanding how the system can fail and how the system might not be produced on time and within cost, fueled by the curiosity of how the system might fail and how production might be difficult. 4. Understanding what we need to know and what we need learn for proper completion of the above three items, fueled by the curiosity of what we might not know in order to make the best decisions.

From Science To Design: Systems Engineering For The Lsst

NASA Astrophysics Data System (ADS)

Claver, Chuck F.; Axelrod, T.; Fouts, K.; Kantor, J.; Nordby, M.; Sebag, J.; LSST Collaboration

2009-01-01

The LSST is a universal-purpose survey telescope that will address scores of scientific missions. To assist the technical teams to convergence to a specific engineering design, the LSST Science Requirements Document (SRD) selects four stressing principle scientific missions: 1) Constraining Dark Matter and Dark Energy; 2) taking an Inventory of the Solar System; 3) Exploring the Transient Optical Sky; and 4) mapping the Milky Way. From these 4 missions the SRD specifies the needed requirements for single images and the full 10 year survey that enables a wide range of science beyond the 4 principle missions. Through optical design and analysis, operations simulation, and throughput modeling the systems engineering effort in the LSST has largely focused on taking the SRD specifications and deriving system functional requirements that define the system design. A Model Based Systems Engineering approach with SysML is used to manage the flow down of requirements from science to system function to sub-system. The rigor of requirements flow and management assists the LSST in keeping the overall scope, hence budget and schedule, under control.

Sharing best practices in teaching biomedical engineering design.

PubMed

Allen, R H; Acharya, S; Jancuk, C; Shoukas, A A

2013-09-01

In an effort to share best practices in undergraduate engineering design education, we describe the origin, evolution and the current status of the undergraduate biomedical engineering design team program at Johns Hopkins University. Specifically, we describe the program and judge the quality of the pedagogy by relating it to sponsor feedback, project outcomes, external recognition and student satisfaction. The general pedagogic practices, some of which are unique to Hopkins, that have worked best include: (1) having a hierarchical team structure, selecting team leaders the Spring semester prior to the academic year, and empowering them to develop and manage their teams, (2) incorporating a longitudinal component that incudes freshmen as part of the team, (3) having each team choose from among pre-screened clinical problems, (4) developing relationships and fostering medical faculty, industry and government to allow students access to engineers, clinicians and clinical environments as needed, (5) providing didactic sessions on topics related to requirements for the next presentation, (6) employing judges from engineering, medicine, industry and government to evaluate designs and provide constructive criticisms approximately once every 3-4 weeks and (7) requiring students to test the efficacy of their designs. Institutional support and resources are crucial for the design program to flourish. Most importantly, our willingness and flexibility to change the program each year based on feedback from students, sponsors, outcomes and judges provides a mechanism for us to test new approaches and continue or modify those that work well, and eliminate those that did not.

Improving motivation and engagement in core engineering courses with student teams

NASA Astrophysics Data System (ADS)

Trenshaw, Kathryn Faye

Team-based projects are common in capstone engineering design courses and increasingly common in first-year engineering programs. Despite high enrollments and budget cutbacks affecting many programs, second- and third-year students can also benefit from team-based project experiences, which motivate them to succeed in engineering and prepare them for a globally competitive workforce. My dissertation research demonstrates that team design projects can be incorporated into the curricula of engineering departments, and these projects result in positive affective outcomes for students. Using ABET outcomes and Self Determination Theory (SDT) as the background for my studies, I investigated students' confidence, motivation, and sense of community after experiencing team design projects in two different engineering departments at a large public institution. In the first study, I used a sequential mixed methods approach with a primary quantitative phase followed by an explanatory qualitative phase to evaluate a chemical engineering program that integrated team design projects throughout the curriculum. The evaluation methods included a survey based on desired ABET outcomes for students and focus groups to expand on the quantitative results. Students reported increased confidence in their design, teamwork, and communication skills after completing the projects. In my second and third studies, I used qualitative interviews based on SDT to explore student motivation in an electrical and computer engineering course redesigned to support students' intrinsic motivation to learn. SDT states that intrinsic motivation to learn is supported by increasing students' sense of autonomy, competence, and relatedness in regard to their learning. Using both narrative inquiry and phenomenological methodologies, I analyzed data from interviews of students for mentions of autonomy, competence, and relatedness as well as course events that were critical in changing students' motivation. Analysis revealed that individual choice, constructive failures, and a strong sense of community in the classroom were critical to moving students toward intrinsic motivation. Further, community building through team experiences characterized the essence of the student experience in the course. My research highlights a need for better quantitative measures of students' affective outcomes, specifically motivation, in the context of a single course. Based on the results of my studies, SDT should be reevaluated in terms of possible interdependencies between autonomy, competence, and relatedness, and how the social context of large engineering courses may create a deeper need for supporting relatedness.

Marine Fouling and Thermal Dissipation of Undersea Wireless Power Transfer

DTIC Science & Technology

2014-09-01

Warfare Systems Center Pacific (SSC Pacific), San Diego, CA. The Naval Innovative Science and Engineering (NISE) Program at SSC Pacific funded this team...FLIR Systems , Inc. MG Chemicals® is registered trademarks of MG Chemicals Ltd. Released by J. Spenser, Head Radiation Technologies Branch...Under authority of M. H. Berry. Head Maritime Systems Division iii EXECUTIVE SUMMARY This report describes the thermal effects and marine

The Tailoring of Traditional Systems Engineering for the Morpheus Project

NASA Technical Reports Server (NTRS)

Devolites, Jennifer L.; Hart, Jeremy J.

2013-01-01

NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. From the beginning, one of goals for the Morpheus Project was to streamline agency processes and practices. The Morpheus project accepted a challenge to tailor the traditional NASA systems engineering approach in a way that would be appropriate for a lower cost, rapid prototype engineering effort, but retain the essence of the guiding principles. The team has produced innovative ways to create an infrastructure and approach that would challenge existing systems engineering processes while still enabling successful implementation of the current Morpheus Project. This paper describes the tailored systems engineering approach for the Morpheus project, including the processes, tools, and amount of rigor employed over the project's multiple lifecycles since the project began in FY11. Lessons learned from these trials have the potential to be scaled up and improve efficiency on a larger projects or programs.

Evaluation of an Ejector Ramjet Based Propulsion System for Air-Breathing Hypersonic Flight

NASA Technical Reports Server (NTRS)

Thomas, Scott R.; Perkins, H. Douglas; Trefny, Charles J.

1997-01-01

A Rocket Based Combined Cycle (RBCC) engine system is designed to combine the high thrust to weight ratio of a rocket along with the high specific impulse of a ramjet in a single, integrated propulsion system. This integrated, combined cycle propulsion system is designed to provide higher vehicle performance than that achievable with a separate rocket and ramjet. The RBCC engine system studied in the current program is the Aerojet strutjet engine concept, which is being developed jointly by a government-industry team as part of the Air Force HyTech program pre-PRDA activity. The strutjet is an ejector-ramjet engine in which small rocket chambers are embedded into the trailing edges of the inlet compression struts. The engine operates as an ejector-ramjet from takeoff to slightly above Mach 3. Above Mach 3 the engine operates as a ramjet and transitions to a scramjet at high Mach numbers. For space launch applications the rockets would be re-ignited at a Mach number or altitude beyond which air-breathing propulsion alone becomes impractical. The focus of the present study is to develop and demonstrate a strutjet flowpath using hydrocarbon fuel at up to Mach 7 conditions.

Liquid Hydrogen Fill

NASA Image and Video Library

2016-08-03

Engineers complete a test of the Ground Operations Demo Unit for liquid hydrogen at NASA's Kennedy Space Center in Florida. The system includes a 33,000 gallon liquid hydrogen storage tank with an internal cold heat exchanger supplied from a cryogenic refrigerator. The primary goal of the testing is to achieve a liquid hydrogen zero boil-off capability. The system was designed, installed and tested by a team of civil servants and contractors from the center's Cryogenic Test Laboratory, with support from engineers at NASA's Glenn Research Center in Cleveland and Stennis Space Center in Mississippi. It may be applicable for use by the Ground Systems Development and Operations Program at Launch Pad 39B.

SLS Model Based Design: A Navigation Perspective

NASA Technical Reports Server (NTRS)

Oliver, T. Emerson; Anzalone, Evan; Park, Thomas; Geohagan, Kevin

2018-01-01

The SLS Program has implemented a Model-based Design (MBD) and Model-based Requirements approach for managing component design information and system requirements. This approach differs from previous large-scale design efforts at Marshall Space Flight Center where design documentation alone conveyed information required for vehicle design and analysis and where extensive requirements sets were used to scope and constrain the design. The SLS Navigation Team is responsible for the Program-controlled Design Math Models (DMMs) which describe and represent the performance of the Inertial Navigation System (INS) and the Rate Gyro Assemblies (RGAs) used by Guidance, Navigation, and Controls (GN&C). The SLS Navigation Team is also responsible for navigation algorithms. The navigation algorithms are delivered for implementation on the flight hardware as a DMM. For the SLS Block 1B design, the additional GPS Receiver hardware model is managed as a DMM at the vehicle design level. This paper describes the models, and discusses the processes and methods used to engineer, design, and coordinate engineering trades and performance assessments using SLS practices as applied to the GN&C system, with a particular focus on the navigation components.

Development of automated testing tools for traffic control signals and devices (NTCIP and Security) phase 2.

DOT National Transportation Integrated Search

2015-02-01

Through a coordinated effort among the electrical engineering research team of the Florida State : University (FSU) and key Florida Department of Transportation (FDOT) personnel, an NTCIP-based : automated testing system for NTCIP-compliant ASC has b...

Embedded systems engineering for products and services design.

PubMed

Ahram, Tareq Z; Karwowski, Waldemar; Soares, Marcelo M

2012-01-01

Systems engineering (SE) professionals strive to develop new techniques to enhance the value of contributions to multidisciplinary smart product design teams. Products and services designers challenge themselves to search beyond the traditional design concept of addressing the physical, social, and cognitive factors. This paper covers the application of embedded user-centered systems engineering design practices into work processes based on the ISO 13407 framework [20] to support smart systems and services design and development. As practitioners collaborate to investigate alternative smart product designs, they concentrate on creating valuable products which will enhance positive interaction. This paper capitalizes on the need to follow a user-centered SE approach to smart products design [4, 22]. Products and systems intelligence should embrace a positive approach to user-centered design while improving our understanding of usable value-adding, experience and extending our knowledge of what inspires others to design enjoyable services and products.

The Electronic Encyclopedia of Earthquakes

NASA Astrophysics Data System (ADS)

Benthien, M.; Marquis, J.; Jordan, T.

2003-12-01

The Electronic Encyclopedia of Earthquakes is a collaborative project of the Southern California Earthquake Center (SCEC), the Consortia of Universities for Research in Earthquake Engineering (CUREE) and the Incorporated Research Institutions for Seismology (IRIS). This digital library organizes earthquake information online as a partner with the NSF-funded National Science, Technology, Engineering and Mathematics (STEM) Digital Library (NSDL) and the Digital Library for Earth System Education (DLESE). When complete, information and resources for over 500 Earth science and engineering topics will be included, with connections to curricular materials useful for teaching Earth Science, engineering, physics and mathematics. Although conceived primarily as an educational resource, the Encyclopedia is also a valuable portal to anyone seeking up-to-date earthquake information and authoritative technical sources. "E3" is a unique collaboration among earthquake scientists and engineers to articulate and document a common knowledge base with a shared terminology and conceptual framework. It is a platform for cross-training scientists and engineers in these complementary fields and will provide a basis for sustained communication and resource-building between major education and outreach activities. For example, the E3 collaborating organizations have leadership roles in the two largest earthquake engineering and earth science projects ever sponsored by NSF: the George E. Brown Network for Earthquake Engineering Simulation (CUREE) and the EarthScope Project (IRIS and SCEC). The E3 vocabulary and definitions are also being connected to a formal ontology under development by the SCEC/ITR project for knowledge management within the SCEC Collaboratory. The E3 development system is now fully operational, 165 entries are in the pipeline, and the development teams are capable of producing 20 new, fully reviewed encyclopedia entries each month. Over the next two years teams will complete 450 entries, which will populate the E3 collection to a level that fully spans earthquake science and engineering. Scientists, engineers, and educators who have suggestions for content to be included in the Encyclopedia can visit www.earthquake.info now to complete the "Suggest a Web Page" form.

Turbine Technology Team - An overview of current and planned activities relevant to the National Launch System (NLS)

NASA Technical Reports Server (NTRS)

Griffin, Lisa W.; Huber, Frank W.

1992-01-01

The current status of the activities and future plans of the Turbine Technology Team of the Consortium for Computational Fluid Dynamics is reviewed. The activities of the Turbine Team focus on developing and enhancing codes and models, obtaining data for code validation and general understanding of flows through turbines, and developing and analyzing the aerodynamic designs of turbines suitable for use in the Space Transportation Main Engine fuel and oxidizer turbopumps. Future work will include the experimental evaluation of the oxidizer turbine configuration, the development, analysis, and experimental verification of concepts to control secondary and tip losses, and the aerodynamic design, analysis, and experimental evaluation of turbine volutes.

Multidisciplinary propulsion simulation using the numerical propulsion system simulator (NPSS)

NASA Technical Reports Server (NTRS)

Claus, Russel W.

1994-01-01

Implementing new technology in aerospace propulsion systems is becoming prohibitively expensive. One of the major contributions to the high cost is the need to perform many large scale system tests. The traditional design analysis procedure decomposes the engine into isolated components and focuses attention on each single physical discipline (e.g., fluid for structural dynamics). Consequently, the interactions that naturally occur between components and disciplines can be masked by the limited interactions that occur between individuals or teams doing the design and must be uncovered during expensive engine testing. This overview will discuss a cooperative effort of NASA, industry, and universities to integrate disciplines, components, and high performance computing into a Numerical propulsion System Simulator (NPSS).

Engineering Technical Review Planning Briefing

NASA Technical Reports Server (NTRS)

Gardner, Terrie

2012-01-01

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.

NASA's Space Launch System: Progress Report

NASA Technical Reports Server (NTRS)

Cook, Jerry; Lyles, Garry

2017-01-01

NASA and its commercial industry team achieved significant progress in 2016 in manufacturing and testing of the Block 1 vehicle for the first launch of the Space Launch System (SLS). Test and flight article hardware for the liquid hydrogen fuel tank as well as the engine section for the core stage were completed at Michoud Assembly Facility (MAF) in New Orleans. Test stands neared completion at Marshall Space Flight Center for the propellant tanks, engine section, intertank and payload section. Stennis Space Center completed major structural renovations on the B2 test stand, where the core stage "green run" test program will be conducted. The SLS team completed a hotfire test series at Stennis to successfully demonstrate the ability of the RS-25 engine to operate under SLS environments and performance conditions. The team also test fired the second qualification five-segment solid rocket motor and cast the first six motor segments for the first SLS mission. The Interim Cryogenic Propulsion Stage (ICPS) test article was delivered to Marshall for structural tests, and work is nearly finished on the flight stage. Flight software testing completed at Marshall included power quality and command and data handling. In 2017, that work continues. SLS completed Preliminary Design Review (PDR) on the Exploration Upper Stage (EUS), a powerful, human-rated spacecraft that will propel explorers to cis-lunar space. In 2017, hardware will continue to be integrated at MAF for core stage structural test articles and the first two operational flights. RS-25 hotfire testing will continue to explore engine performance, as well as test flight-like software and four new Engine Controller Units (ECUs) for the first mission. Production of development components for a more affordable RS-25 design is underway. Core stage structural test articles have begun arriving at Marshall. While engineering challenges typical of a new development are possible, SLS is working toward launch readiness in late 2018. This paper will discuss these and other technical and programmatic successes and challenges over the past year and provide a preview of work ahead before first flight

Reaction Control System Thruster Cracking Consultation: NASA Engineering and Safety Center (NESC) Materials Super Problem Resolution Team (SPRT) Findings

NASA Technical Reports Server (NTRS)

MacKay, Rebecca A.; Smith, Stephen W.; Shah, Sandeep R.; Piascik, Robert S.

2005-01-01

The shuttle orbiter s reaction control system (RCS) primary thruster serial number 120 was found to contain cracks in the counter bores and relief radius after a chamber repair and rejuvenation was performed in April 2004. Relief radius cracking had been observed in the 1970s and 1980s in seven thrusters prior to flight; however, counter bore cracking had never been seen previously in RCS thrusters. Members of the Materials Super Problem Resolution Team (SPRT) of the NASA Engineering and Safety Center (NESC) conducted a detailed review of the relevant literature and of the documentation from the previous RCS thruster failure analyses. It was concluded that the previous failure analyses lacked sufficient documentation to support the conclusions that stress corrosion cracking or hot-salt cracking was the root cause of the thruster cracking and lacked reliable inspection controls to prevent cracked thrusters from entering the fleet. The NESC team identified and performed new materials characterization and mechanical tests. It was determined that the thruster intergranular cracking was due to hydrogen embrittlement and that the cracking was produced during manufacturing as a result of processing the thrusters with fluoride-containing acids. Testing and characterization demonstrated that appreciable environmental crack propagation does not occur after manufacturing.

Special Gender Studies for Engineering?

ERIC Educational Resources Information Center

Ihsen, Susanne

2005-01-01

Today we are confronted with a new challenge in product development: "Diversity" needs to be implemented in the engineering design and development teams. Such diversity means to "mirror" within the teams the characteristics of different customer groups: the two genders, the different age groups, and the different cultural…

Installation Restoration Program. Phase I. Records Search, Plattsburgh AFB, New York

DTIC Science & Technology

1985-04-01

Storage Area (WSA) drainage to the Salmon River, the POL and housing area drainage to Lake Champlaln, and the golf course streams and ponds drain...Sanitary Engineering; 2. Michael A. Zapkln, Project Director, M. Eng. Environmental Engineering and M.S. Biology - Team Chief and Ecologlst; 3. Andrew...college courses were offered to World War II veterans. This center became part of the State University system in 1950 and was known as Champlain College

The design of two-stage-to-orbit vehicles

NASA Technical Reports Server (NTRS)

1991-01-01

Two separate student design groups developed conceptual designs for a two-stage-to-orbit vehicle, with each design group consisting of a carrier team and an orbiter team. A two-stage-to-orbit system is considered in the event that single-stage-to-orbit is deemed not feasible in the foreseeable future; the two-stage system would also be used as a complement to an already existing heavy lift vehicle. The design specifications given are to lift a 10,000-lb payload 27 ft long by 10 ft diameter, to low Earth orbit (300 n.m.) using an air breathing carrier configuration that will take off horizontally within 15,000 ft. The staging Mach number and altitude were to be determined by the design groups. One group designed a delta wing/body carrier with the orbiter nested within the fuselage of the carrier, and the other group produced a blended cranked-delta wing/body carrier with the orbiter in the more conventional piggyback configuration. Each carrier used liquid hydrogen-fueled turbofanramjet engines, with data provided by General Electric Aircraft Engine Group. While one orbiter used a full-scale Space Shuttle Main Engine (SSME), the other orbiter employed a half-scale SSME coupled with scramjet engines, with data again provided by General Electric. The two groups conceptual designs, along with the technical trade-offs, difficulties, and details that surfaced during the design process are presented.

Optical and system engineering in the development of a high-quality student telescope kit

NASA Astrophysics Data System (ADS)

Pompea, Stephen M.; Pfisterer, Richard N.; Ellis, Scott; Arion, Douglas N.; Fienberg, Richard Tresch; Smith, Thomas C.

2010-07-01

The Galileoscope student telescope kit was developed by a volunteer team of astronomers, science education experts, and optical engineers in conjunction with the International Year of Astronomy 2009. This refracting telescope is in production with over 180,000 units produced and distributed with 25,000 units in production. The telescope was designed to be able to resolve the rings of Saturn and to be used in urban areas. The telescope system requirements, performance metrics, and architecture were established after an analysis of current inexpensive telescopes and student telescope kits. The optical design approaches used in the various prototypes and the optical system engineering tradeoffs will be described. Risk analysis, risk management, and change management were critical as was cost management since the final product was to cost around 15 (but had to perform as well as 100 telescopes). In the system engineering of the Galileoscope a variety of analysis and testing approaches were used, including stray light design and analysis using the powerful optical analysis program FRED.

Organizational Influences on Interdisciplinary Interactions during Research and Design of Large-Scale Complex Engineered Systems

NASA Technical Reports Server (NTRS)

McGowan, Anna-Maria R.; Seifert, Colleen M.; Papalambros, Panos Y.

2012-01-01

The design of large-scale complex engineered systems (LaCES) such as an aircraft is inherently interdisciplinary. Multiple engineering disciplines, drawing from a team of hundreds to thousands of engineers and scientists, are woven together throughout the research, development, and systems engineering processes to realize one system. Though research and development (R&D) is typically focused in single disciplines, the interdependencies involved in LaCES require interdisciplinary R&D efforts. This study investigates the interdisciplinary interactions that take place during the R&D and early conceptual design phases in the design of LaCES. Our theoretical framework is informed by both engineering practices and social science research on complex organizations. This paper provides preliminary perspective on some of the organizational influences on interdisciplinary interactions based on organization theory (specifically sensemaking), data from a survey of LaCES experts, and the authors experience in the research and design. The analysis reveals couplings between the engineered system and the organization that creates it. Survey respondents noted the importance of interdisciplinary interactions and their significant benefit to the engineered system, such as innovation and problem mitigation. Substantial obstacles to interdisciplinarity are uncovered beyond engineering that include communication and organizational challenges. Addressing these challenges may ultimately foster greater efficiencies in the design and development of LaCES and improved system performance by assisting with the collective integration of interdependent knowledge bases early in the R&D effort. This research suggests that organizational and human dynamics heavily influence and even constrain the engineering effort for large-scale complex systems.

Materials, Processes, and Environmental Engineering Network

NASA Technical Reports Server (NTRS)

White, Margo M.

1993-01-01

Attention is given to the Materials, Processes, and Environmental Engineering Network (MPEEN), which was developed as a central holding facility for materials testing information generated by the Materials and Processes Laboratory of NASA-Marshall. It contains information from other NASA centers and outside agencies, and also includes the NASA Environmental Information System (NEIS) and Failure Analysis Information System (FAIS) data. The data base is NEIS, which is accessible through MPEEN. Environmental concerns are addressed regarding materials identified by the NASA Operational Environment Team (NOET) to be hazardous to the environment. The data base also contains the usage and performance characteristics of these materials.

Ethical considerations for a better collaboration between architects and structural engineers: design of buildings with reinforced concrete frame systems in earthquake zones.

PubMed

Hurol, Yonca

2014-06-01

Architects design building structures, although structural design is the profession of structural engineers. Thus, it is better for architects and structural engineers to collaborate starting from the initial phases of the architectural design. However, this is not very common because of the contradictory design processes and value systems held within the two professions. This article provides a platform upon which architects and structural engineers can resolve the value conflicts between them by analysing phases of the structural design of reinforced concrete frame systems in architecture, the criteria of the structural design for each phase and determining the conflicting values for each criterion. The results shown in the article demonstrate that the architectural design of structures is a complex process, which is based on contradictory values and value systems. Finally, the article suggests to architects and structural engineers to use Value Sensitive Design and to choose an appropriate team leader in order to resolve the unethical conflict between them and to avoid any unreasonable decision making.

Oil-Free Turbomachinery Team Passed Milestone on Path to the First Oil-Free Turbine Aircraft Engine

NASA Technical Reports Server (NTRS)

Bream, Bruce L.

2002-01-01

The Oil-Free Turbine Engine Technology Project team successfully demonstrated a foil-air bearing designed for the core rotor shaft of a turbine engine. The bearings were subjected to test conditions representative of the engine core environment through a combination of high speeds, sustained loads, and elevated temperatures. The operational test envelope was defined during conceptual design studies completed earlier this year by bearing manufacturer Mohawk Innovative Technologies and the turbine engine company Williams International. The prototype journal foil-air bearings were tested at the NASA Glenn Research Center. Glenn is working with Williams and Mohawk to create a revolution in turbomachinery by developing the world's first Oil-Free turbine aircraft engine. NASA's General Aviation Propulsion project and Williams International recently developed the FJX-2 turbofan engine that is being commercialized as the EJ-22. This core bearing milestone is a first step toward a future version of the EJ-22 that will take advantage of recent advances in foil-air bearings by eliminating the need for oil lubrication systems and rolling element bearings. Oil-Free technology can reduce engine weight by 15 percent and let engines operate at very high speeds, yielding power density improvements of 20 percent, and reducing engine maintenance costs. In addition, with NASA coating technology, engines can operate at temperatures up to 1200 F. Although the project is still a couple of years from a full engine test of the bearings, this milestone shows that the bearing design exceeds the expected environment, thus providing confidence that an Oil-Free turbine aircraft engine will be attained. The Oil-Free Turbomachinery Project is supported through the Aeropropulsion Base Research Program.

Group Development and Integration in a Cross-Disciplinary and Intercultural Research Team.

PubMed

Kirk-Lawlor, Naomi; Allred, Shorna

2017-04-01

Cross-disciplinary research is necessary to solve many complex problems that affect society today, including problems involving linked social and environmental systems. Examples include natural resource management or scarcity problems, problematic effects of climate change, and environmental pollution issues. Intercultural research teams are needed to address many complex environmental matters as they often cross geographic and political boundaries, and involve people of different countries and cultures. It follows that disciplinarily and culturally diverse research teams have been organized to investigate and address environmental issues. This case study investigates a team composed of both monolingual and bilingual Chilean and US university researchers who are geoscientists, engineers and economists. The objective of this research team was to study both the natural and human parts of a hydrologic system in a hyper-arid region in northern Chile. Interviews (n = 8) addressed research questions focusing on the interaction of cross-disciplinary diversity and cultural diversity during group integration and development within the team. The case study revealed that the group struggled more with cross-disciplinary challenges than with intercultural ones. Particularly challenging ones were instances the of disciplinary crosstalk, or hidden misunderstandings, where team members thought they understood their cross-disciplinary colleagues, when in reality they did not. Results showed that translation served as a facilitator to cross-disciplinary integration of the research team. The use of translation in group meetings as a strategy for effective cross-disciplinary integration can be extended to monolingual cross-disciplinary teams as well.

Group Development and Integration in a Cross-Disciplinary and Intercultural Research Team

NASA Astrophysics Data System (ADS)

Kirk-Lawlor, Naomi; Allred, Shorna

2017-04-01

Cross-disciplinary research is necessary to solve many complex problems that affect society today, including problems involving linked social and environmental systems. Examples include natural resource management or scarcity problems, problematic effects of climate change, and environmental pollution issues. Intercultural research teams are needed to address many complex environmental matters as they often cross geographic and political boundaries, and involve people of different countries and cultures. It follows that disciplinarily and culturally diverse research teams have been organized to investigate and address environmental issues. This case study investigates a team composed of both monolingual and bilingual Chilean and US university researchers who are geoscientists, engineers and economists. The objective of this research team was to study both the natural and human parts of a hydrologic system in a hyper-arid region in northern Chile. Interviews ( n = 8) addressed research questions focusing on the interaction of cross-disciplinary diversity and cultural diversity during group integration and development within the team. The case study revealed that the group struggled more with cross-disciplinary challenges than with intercultural ones. Particularly challenging ones were instances the of disciplinary crosstalk, or hidden misunderstandings, where team members thought they understood their cross-disciplinary colleagues, when in reality they did not. Results showed that translation served as a facilitator to cross-disciplinary integration of the research team. The use of translation in group meetings as a strategy for effective cross-disciplinary integration can be extended to monolingual cross-disciplinary teams as well.

High-Penetration PV Integration Handbook for Distribution Engineers

DOE Office of Scientific and Technical Information (OSTI.GOV)

Seguin, Rich; Woyak, Jeremy; Costyk, David

2016-01-01

This handbook has been developed as part of a five-year research project which began in 2010. The National Renewable Energy Laboratory (NREL), Southern California Edison (SCE), Quanta Technology, Satcon Technology Corporation, Electrical Distribution Design (EDD), and Clean Power Research (CPR) teamed together to analyze the impacts of high-penetration levels of photovoltaic (PV) systems interconnected onto the SCE distribution system. This project was designed specifically to leverage the experience that SCE and the project team would gain during the significant installation of 500 MW of commercial scale PV systems (1-5 MW typically) starting in 2010 and completing in 2015 within SCE’smore » service territory through a program approved by the California Public Utility Commission (CPUC).« less

Teaching engineering ethics using BLOCKS game.

PubMed

Lau, Shiew Wei; Tan, Terence Peng Lian; Goh, Suk Meng

2013-09-01

The aim of this study was to investigate the use of a newly developed design game called BLOCKS to stimulate awareness of ethical responsibilities amongst engineering students. The design game was played by seventeen teams of chemical engineering students, with each team having to arrange pieces of colored paper to produce two letters each. Before the end of the game, additional constraints were introduced to the teams such that they faced similar ambiguity in the technical facts that the engineers involved in the Challenger disaster had faced prior to the space shuttle launch. At this stage, the teams had to decide whether to continue with their original design or to develop alternative solutions. After the teams had made their decisions, a video of the Challenger explosion was shown followed by a post-game discussion. The students' opinion on five Statements on ethics was tracked via a Five-Item Likert survey which was administered three times, before and after the ethical scenario was introduced, and after the video and post-game discussion. The results from this study indicated that the combination of the game and the real-life incident from the video had generally strengthened the students' opinions of the Statements.

Aerocapture Technologies

NASA Technical Reports Server (NTRS)

Keys, Andrew S.

2006-01-01

Aeroassist technology development is a vital part of the NASA In-Space Propulsion Technology (ISPT) Program. One of the main focus areas of ISPT is aeroassist technologies through the Aerocapture Technology (AT) Activity. Within the ISPT, the current aeroassist technology development focus is aerocapture. Aerocapture relies on the exchange of momentum with an atmosphere to achieve thrust, in this case a decelerating thrust leading to orbit capture. Without aerocapture, a substantial propulsion system would be needed on the spacecraft to perform the same reduction of velocity. This could cause reductions in the science payload delivered to the destination, increases in the size of the launch vehicle (to carry the additional fuel required for planetary capture) or could simply make the mission impossible due to additional propulsion requirements. The AT is advancing each technology needed for the successful implementation of aerocapture in future missions. The technology development focuses on both rigid aeroshell systems as well as the development of inflatable aerocapture systems, advanced aeroshell performance sensors, lightweight structure and higher temperature adhesives. Inflatable systems such as tethered trailing ballutes ('balloon parachutes'), clamped ballutes, and inflatable aeroshells are also under development. Aerocapture-specific computational tools required to support future aerocapture missions are also an integral part of the ATP. Tools include: engineering reference atmosphere models, guidance and navigation, aerothermodynamic modeling, radiation modeling and flight simulation. Systems analysis plays a key role in the AT development process. The NASA in-house aerocapture systems analysis team has been taken with multiple systems definition and concept studies to complement the technology development tasks. The team derives science requirements, develops guidance and navigation algorithms, as well as engineering reference atmosphere models and aeroheating specifications. The study team also creates designs for the overall mission spacecraft. Presentation slides are provided to further describe the aerocapture project.

The Cooperate Assistive Teamwork Environment for Software Description Languages.

PubMed

Groenda, Henning; Seifermann, Stephan; Müller, Karin; Jaworek, Gerhard

2015-01-01

Versatile description languages such as the Unified Modeling Language (UML) are commonly used in software engineering across different application domains in theory and practice. They often use graphical notations and leverage visual memory for expressing complex relations. Those notations are hard to access for people with visual impairment and impede their smooth inclusion in an engineering team. Existing approaches provide textual notations but require manual synchronization between the notations. This paper presents requirements for an accessible and language-aware team work environment as well as our plan for the assistive implementation of Cooperate. An industrial software engineering team consisting of people with and without visual impairment will evaluate the implementation.

Pipe Flow Simulation Software: A Team Approach to Solve an Engineering Education Problem.

ERIC Educational Resources Information Center

Engel, Renata S.; And Others

1996-01-01

A computer simulation program for use in the study of fluid mechanics is described. The package is an interactive tool to explore the fluid flow characteristics of a pipe system by manipulating the physical construction of the system. The motivation, software design requirements, and specific details on how its objectives were met are presented.…

Naturalistic Decision Making: Implications for Design

DTIC Science & Technology

1993-04-01

Cognitive Task Analysis Decision Making Design Engineer Design System Human-Computer Interface System Development 15. NUMBER OF PAGES 182 16...people use to select a course of action. The SOAR explains how stress affects the decision making of both individuals and teams. COGNITIVE TASK ANALYSIS : This...procedures for Cognitive Task Analysis , contrasting the strengths and weaknesses of each, and showing how a Cognitive Task Analysis

75 FR 60495 - Eighteenth Plenary Meeting: RTCA Special Committee 203: Unmanned Aircraft Systems

Federal Register 2010, 2011, 2012, 2013, 2014

2010-09-30

..., 20036; telephone (202) 833-9339; fax (202) 833-9434; Web site http://www.rtca.org . SUPPLEMENTARY... Product Team Breakout Session. RTCA Workspace Web Tool. Closing Plenary Session. Plenary Adjourns until... Engineering Workgroup. Control and Communications Workgroup. Sense and Avoid Workgroup. Wednesday, October...

Interactive Model-Centric Systems Engineering (IMCSE) Phase 5

DTIC Science & Technology

2018-02-28

Conducting Program Team Launches ................................................................................................. 12 Informing Policy...research advances knowledge relevant to human interaction with models and model-generated information . Figure 1 highlights several questions the...stakeholders interact using models and model generated information ; facets of human interaction with visualizations and large data sets; and underlying

Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering - Phase 2

DTIC Science & Technology

2010-05-31

Westerman, Crawshaw , Hockey, and Sauer, 1998) for practitioners. Thus, CTA extends research by providing a toolbox of methods for understanding teams...drive process and performance. Washington, DC: American Psychological Association. pp. 3-8. Shrayne, N. M., Westerman, S. J., Crawshaw , C. M

Overview and Recent Accomplishments of Advanced Mirror Technology Development Phase 2 (AMTD-2)

NASA Technical Reports Server (NTRS)

Stahl, H. Philip

2015-01-01

AMTD uses a science-driven systems engineering approach to define & execute a long-term strategy to mature technologies necessary to enable future large aperture space telescopes. Because we cannot predict the future, we are pursuing multiple technology paths including monolithic & segmented mirrors. Assembled outstanding team from academia, industry & government; experts in science & space telescope engineering. Derived engineering specifications from science measurement needs & implementation constraints. Maturing 6 critical technologies required to enable 4 to 8 meter UVOIR space telescope mirror assemblies for both general astrophysics & ultra-high contrast exoplanet imaging. AMTD achieving all its goals & accomplishing all its milestones.

Human factors engineering approaches to patient identification armband design.

PubMed

Probst, C Adam; Wolf, Laurie; Bollini, Mara; Xiao, Yan

2016-01-01

The task of patient identification is performed many times each day by nurses and other members of the care team. Armbands are used for both direct verification and barcode scanning during patient identification. Armbands and information layout are critical to reducing patient identification errors and dangerous workarounds. We report the effort at two large, integrated healthcare systems that employed human factors engineering approaches to the information layout design of new patient identification armbands. The different methods used illustrate potential pathways to obtain standardized armbands across healthcare systems that incorporate human factors principles. By extension, how the designs have been adopted provides examples of how to incorporate human factors engineering into key clinical processes. Copyright © 2015 Elsevier Ltd and The Ergonomics Society. All rights reserved.

Medical evaluations on the KC-135 1990 flight report summary

NASA Technical Reports Server (NTRS)

Lloyd, Charles W.; Guess, Terrell M.; Whiting, Charles W.; Doarn, Charles R.

1991-01-01

The medical investigations completed on the KC-135 during FY 1990 in support of the development of the Health Maintenance Facility and Medical Operations are discussed. The experiments are comprised of engineering evaluations of medical hardware and medical procedures. The investigating teams are made up of both medical and engineering personnel responsible for the development of medical hardware and medical operations. The hardware evaluated includes dental equipment, a coagulation analyzer, selected pharmaceutical aerosol devices, a prototype air/fluid separator, a prototype packaging and stowage system for medical supplies, a microliter metering system, and a workstation for minor surgical procedures. The results of these engineering evaluations will be used in the design of fleet hardware as well as to identify hardware specific training requirements.

TEAMS Model Analyzer

NASA Technical Reports Server (NTRS)

Tijidjian, Raffi P.

2010-01-01

The TEAMS model analyzer is a supporting tool developed to work with models created with TEAMS (Testability, Engineering, and Maintenance System), which was developed by QSI. In an effort to reduce the time spent in the manual process that each TEAMS modeler must perform in the preparation of reporting for model reviews, a new tool has been developed as an aid to models developed in TEAMS. The software allows for the viewing, reporting, and checking of TEAMS models that are checked into the TEAMS model database. The software allows the user to selectively model in a hierarchical tree outline view that displays the components, failure modes, and ports. The reporting features allow the user to quickly gather statistics about the model, and generate an input/output report pertaining to all of the components. Rules can be automatically validated against the model, with a report generated containing resulting inconsistencies. In addition to reducing manual effort, this software also provides an automated process framework for the Verification and Validation (V&V) effort that will follow development of these models. The aid of such an automated tool would have a significant impact on the V&V process.

Ocean Drilling Program: Drilling Services

Science.gov Websites

Drilling operations team Material services team Development engineering team ODP/TAMU Science Operator Home Services department consists of three team-oriented project groups, which also work to improve the existing team. A member of this team sails with each cruise to provide expertise for the shipboard scientific

A NOVEL PROCESS FOR BIOLOGICAL NITROGEN REMOVAL FROM DAIRY WASTEWATER IN CONSTRUCTED WETLANDS

EPA Science Inventory

SUNY-ESF has a multidisciplinary P3 Team, although it is mainly composed of undergraduate students in forest engineering and graduate students in environmental and resources engineering. The Team has successfully enriched anammox bacteria in two vertical flow baffled biofilter...

Low Emissions Alternative Power (LEAP) Project Office Business Team of the Aeropropulsion Research Program Office (ARPO) Org. 0140

NASA Technical Reports Server (NTRS)

Buttler, Jennifer A.

2004-01-01

The program for which I am working at this summer is Propulsion and Power/Low Emissions Alternative Power (P&P/LEAP). It invests in a fundamental TRL 1-6 research and technology portfolio that will enable the future of: Alternative fuels and/or alternative propulsion systems, non-combustion (electric) propulsion systems. P&P/LEAP will identify and capitalize on the highest potential concepts generated both internal and external to the Agency. During my 2004 summer at NASA Glenn Research Center, I worked with my mentor Barbara Mader, in the Project Office with the Business Team completing various tasks for the project and personnel. The LEAP project is a highly matrixed organization. The Project Office is responsible for the goals advocacy and dollar (budget) of the LEAP project. The objectives of the LEAP Project are to discover new energy sources and develop unconventional engines and power systems directed towards greatly reduced emissions, enable new vehicle concepts for public mobility, new science missions and national security. The Propulsion and PowerLow Emissions Alternative Power directly supports the environmental, mobility, national security objectives of the Vehicle Systems Program and the Aeronautics Technology Theme. Technology deliverables include the demonstration through integrated ground tests, a constant volume combustor in an engine system, and UAV/small transport aircraft all electric power system. My mentor serves as a key member of the management team for the Aeropropulsion Research Program Office (ARPO). She has represented the office on numerous occasions, and is a member of a number of center-wide panels/teams, such as the Space management Committee and is chair to the Business Process Consolidation Team. She is responsible for the overall coordination of resources for the Propulsion and Power Project - from advocacy to implementation. The goal for my summer at NASA was to document processes and archive program documents from the past years. I used the computer and office machines, and also worked with personnel in setting up a Cost Estimation Plan. I gained office experience in Word, Excel, and Power Point, with the completion of a variety of tasks. I made spreadsheets that pertained to the budget plan for Journey to Tomorrow, to name a few I have supported the office by tracking resource information: including programmatic travel, project budget at the center level to budgets for individual research sub-projects and grants. I also assisted the Program Support Office in their duties including, representing the office on numerous occasions on center-wide team/panels, such as the Space management committee, IFMP Budget Formulation, Journey to Tomorrow Committee, and the Vehicle Systems Program Business Process Team.

Designing to Sample the Unknown: Lessons from OSIRIS-REx Project Systems Engineering

NASA Technical Reports Server (NTRS)

Everett, David; Mink, Ronald; Linn, Timothy; Wood, Joshua

2017-01-01

On September 8, 2016, the third NASA New Frontiers mission launched on an Atlas V 411. The Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) will rendezvous with asteroid Bennu in 2018, collect a sample in 2020, and return that sample to Earth in September 2023. The development team has overcome a number of challenges in order to design and build a system that will make contact with an unexplored, airless, low-gravity body. This paper will provide an overview of the mission, then focus in on the system-level challenges and some of the key system-level processes. Some of the lessons here are unique to the type of mission, like discussion of operating at a largely-unknown, low-gravity object. Other lessons, particularly from the build phase, have broad implications. The OSIRIS-REx risk management process was particularly effective in achieving an on-time and under-budget development effort. The systematic requirements management and verification and the system validation also helped identify numerous potential problems. The final assessment of the OSIRIS-REx performance will need to wait until the sample is returned in 2023, but this post-launch assessment will capture some of the key systems-engineering lessons from the development team.

Inspection of the Math Model Tools for On-Orbit Assessment of Impact Damage Report. Version 1.0

NASA Technical Reports Server (NTRS)

Harris, Charles E.; Raju, Ivatury S.; Piascik, Robert S.; Kramer White, Julie; Labbe, Steve G.; Rotter, Hank A.

2005-01-01

In Spring of 2005, the NASA Engineering Safety Center (NESC) was engaged by the Space Shuttle Program (SSP) to peer review the suite of analytical tools being developed to support the determination of impact and damage tolerance of the Orbiter Thermal Protection Systems (TPS). The NESC formed an independent review team with the core disciplines of materials, flight sciences, structures, mechanical analysis and thermal analysis. The Math Model Tools reviewed included damage prediction and stress analysis, aeroheating analysis, and thermal analysis tools. Some tools are physics-based and other tools are empirically-derived. Each tool was created for a specific use and timeframe, including certification, real-time pre-launch assessments, and real-time on-orbit assessments. The tools are used together in an integrated strategy for assessing the ramifications of impact damage to tile and RCC. The NESC teams conducted a peer review of the engineering data package for each Math Model Tool. This report contains the summary of the team observations and recommendations from these reviews.

2014-2687

NASA Image and Video Library

2014-05-23

CAPE CANAVERAL, Fla. -- Rob Mueller announces the winner of the Judges' Innovation Award during NASA's 2014 Robotic Mining Competition awards ceremony inside the Space Shuttle Atlantis attraction at the Kennedy Space Center Visitor Complex in Florida. More than 35 teams from colleges and universities around the U.S. designed and built remote-controlled robots for the mining competition. The competition is a NASA Human Exploration and Operations Mission Directorate project designed to engage and retain students in science, technology, engineering and mathematics, or STEM, fields by expanding opportunities for student research and design. Teams use their remote-controlled robotics to maneuver and dig in a supersized sandbox filled with a crushed material that has characteristics similar to Martian soil. The objective of the challenge is to see which team’s robot can collect and move the most regolith within a specified amount of time. The competition includes on-site mining, writing a systems engineering paper, performing outreach projects for K-12 students, slide presentation and demonstrations, and team spirit. For more information, visit www.nasa.gov/nasarmc. Photo credit: NASA/Kim Shiflett

Human-factors engineering control-room design review/audit: Waterford 3 SES Generating Station, Louisiana Power and Light Company

DOE Office of Scientific and Technical Information (OSTI.GOV)

Savage, J.W.

1983-03-10

A human factors engineering design review/audit of the Waterford-3 control room was performed at the site on May 10 through May 13, 1982. The report was prepared on the basis of the HFEB's review of the applicant's Preliminary Human Engineering Discrepancy (PHED) report and the human factors engineering design review performed at the site. This design review was carried out by a team from the Human Factors Engineering Branch, Division of Human Factors Safety. The review team was assisted by consultants from Lawrence Livermore National Laboratory (University of California), Livermore, California.

Next Generation Heavy-Lift Launch Vehicle: Large Diameter, Hydrocarbon-Fueled Concepts

NASA Technical Reports Server (NTRS)

Holliday, Jon; Monk, Timothy; Adams, Charles; Campbell, Ricky

2012-01-01

With the passage of the 2010 NASA Authorization Act, NASA was directed to begin the development of the Space Launch System (SLS) as a follow-on to the Space Shuttle Program. The SLS is envisioned as a heavy lift launch vehicle that will provide the foundation for future large-scale, beyond low Earth orbit (LEO) missions. Supporting the Mission Concept Review (MCR) milestone, several teams were formed to conduct an initial Requirements Analysis Cycle (RAC). These teams identified several vehicle concept candidates capable of meeting the preliminary system requirements. One such team, dubbed RAC Team 2, was tasked with identifying launch vehicles that are based on large stage diameters (up to the Saturn V S-IC and S-II stage diameters of 33 ft) and utilize high-thrust liquid oxygen (LOX)/RP engines as a First Stage propulsion system. While the trade space for this class of LOX/RP vehicles is relatively large, recent NASA activities (namely the Heavy Lift Launch Vehicle Study in late 2009 and the Heavy Lift Propulsion Technology Study of 2010) examined specific families within this trade space. Although the findings from these studies were incorporated in the Team 2 activity, additional branches of the trade space were examined and alternative approaches to vehicle development were considered. Furthermore, Team 2 set out to define a highly functional, flexible, and cost-effective launch vehicle concept. Utilizing this approach, a versatile two-stage launch vehicle concept was chosen as a preferred option. The preferred vehicle option has the capability to fly in several different configurations (e.g. engine arrangements) that gives this concept an inherent operational flexibility which allows the vehicle to meet a wide range of performance requirements without the need for costly block upgrades. Even still, this concept preserves the option for evolvability should the need arise in future mission scenarios. The foundation of this conceptual design is a focus on low cost and effectiveness rather than efficiency or cutting-edge technology. This paper details the approach and process, as well as the trade space analysis, leading to the preferred vehicle concept.

KSC-07pd3598

NASA Image and Video Library

2007-12-09

KENNEDY SPACE CENTER, FLA. -- LeRoy Cain, the Mission Management Team chairman, participates in a news briefing following the conclusion of a team meeting. The meeting followed the morning's launch scrub caused by problems experienced with the space shuttle Atlantis STS-122 external tank's engine cutoff sensor system during tanking for the second launch attempt. An announcement was made during the briefing that the STS-122 launch is postponed to no earlier than Jan. 2, 2008, to give the team time to resolve the system's problems. Atlantis will carry the Columbus Laboratory, the European Space Agency's largest contribution to the construction of the International Space Station. It will support scientific and technological research in a microgravity environment. Permanently attached to the Harmony node of the space station, the laboratory will carry out experiments in materials science, fluid physics and biosciences, as well as perform a number of technological applications. Photo credit: NASA/Kim Shiflett

CPAS Preflight Drop Test Analysis Process

NASA Technical Reports Server (NTRS)

Englert, Megan E.; Bledsoe, Kristin J.; Romero, Leah M.

2015-01-01

Throughout the Capsule Parachute Assembly System (CPAS) drop test program, the CPAS Analysis Team has developed a simulation and analysis process to support drop test planning and execution. This process includes multiple phases focused on developing test simulations and communicating results to all groups involved in the drop test. CPAS Engineering Development Unit (EDU) series drop test planning begins with the development of a basic operational concept for each test. Trajectory simulation tools include the Flight Analysis and Simulation Tool (FAST) for single bodies, and the Automatic Dynamic Analysis of Mechanical Systems (ADAMS) simulation for the mated vehicle. Results are communicated to the team at the Test Configuration Review (TCR) and Test Readiness Review (TRR), as well as at Analysis Integrated Product Team (IPT) meetings in earlier and intermediate phases of the pre-test planning. The ability to plan and communicate efficiently with rapidly changing objectives and tight schedule constraints is a necessity for safe and successful drop tests.

SemanticOrganizer: A Customizable Semantic Repository for Distributed NASA Project Teams

NASA Technical Reports Server (NTRS)

Keller, Richard M.; Berrios, Daniel C.; Carvalho, Robert E.; Hall, David R.; Rich, Stephen J.; Sturken, Ian B.; Swanson, Keith J.; Wolfe, Shawn R.

2004-01-01

SemanticOrganizer is a collaborative knowledge management system designed to support distributed NASA projects, including diverse teams of scientists, engineers, and accident investigators. The system provides a customizable, semantically structured information repository that stores work products relevant to multiple projects of differing types. SemanticOrganizer is one of the earliest and largest semantic web applications deployed at NASA to date, and has been used in diverse contexts ranging from the investigation of Space Shuttle Columbia's accident to the search for life on other planets. Although the underlying repository employs a single unified ontology, access control and ontology customization mechanisms make the repository contents appear different for each project team. This paper describes SemanticOrganizer, its customization facilities, and a sampling of its applications. The paper also summarizes some key lessons learned from building and fielding a successful semantic web application across a wide-ranging set of domains with diverse users.

Automation and Process Improvement Enables a Small Team to Operate a Low Thrust Mission in Orbit Around the Asteroid Vesta

NASA Technical Reports Server (NTRS)

Weise, Timothy M

2012-01-01

NASA's Dawn mission to the asteroid Vesta and dwarf planet Ceres launched September 27, 2007 and arrived at Vesta in July of 2011. This mission uses ion propulsion to achieve the necessary delta-V to reach and maneuver at Vesta and Ceres. This paper will show how the evolution of ground system automation and process improvement allowed a relatively small engineering team to transition from cruise operations to asteroid operations while maintaining robust processes. The cruise to Vesta phase lasted almost 4 years and consisted of activities that were built with software tools, but each tool was open loop and required engineers to review the output to ensure consistency. Additionally, this same time period was characterized by the evolution from manually retrieved and reviewed data products to automatically generated data products and data value checking. Furthermore, the team originally took about three to four weeks to design and build about four weeks of spacecraft activities, with spacecraft contacts only once a week. Operations around the asteroid Vesta increased the tempo dramatically by transitioning from one contact a week to three or four contacts a week, to fourteen contacts a week (every 12 hours). This was accompanied by a similar increase in activity complexity as well as very fast turn around activity design and build cycles. The design process became more automated and the tools became closed loop, allowing the team to build more activities without sacrificing rigor. Additionally, these activities were dependent on the results of flight system performance, so more automation was added to analyze the flight data and provide results in a timely fashion to feed the design cycle. All of this automation and process improvement enabled up the engineers to focus on other aspects of spacecraft operations, including spacecraft health monitoring and anomaly resolution.

Next-generation concurrent engineering: developing models to complement point designs

NASA Technical Reports Server (NTRS)

Morse, Elizabeth; Leavens, Tracy; Cohanim, Barbak; Harmon, Corey; Mahr, Eric; Lewis, Brian

2006-01-01

Concurrent Engineering Design teams have made routine the rapid development of point designs for space missions. The Jet Propulsion Laboratory's Team X is now evolving into a next generation CED; nin addition to a point design, the team develops a model of the local trade space. The process is a balance between the power of model-developing tools and the creativity of human experts, enabling the development of a variety of trade models for any space mission.

The Roles of Implicit Understanding of Engineering Ethics in Student Teams' Discussion.

PubMed

Lee, Eun Ah; Grohman, Magdalena; Gans, Nicholas R; Tacca, Marco; Brown, Matthew J

2017-12-01

Following previous work that shows engineering students possess different levels of understanding of ethics-implicit and explicit-this study focuses on how students' implicit understanding of engineering ethics influences their team discussion process, in cases where there is significant divergence between their explicit and implicit understanding. We observed student teams during group discussions of the ethical issues involved in their engineering design projects. Through the micro-scale discourse analysis based on cognitive ethnography, we found two possible ways in which implicit understanding influenced the discussion. In one case, implicit understanding played the role of intuitive ethics-an intuitive judgment followed by reasoning. In the other case, implicit understanding played the role of ethical insight, emotionally guiding the direction of the discussion. In either case, however, implicit understanding did not have a strong influence, and the conclusion of the discussion reflected students' explicit understanding. Because students' implicit understanding represented broader social implication of engineering design in both cases, we suggest to take account of students' relevant implicit understanding in engineering education, to help students become more socially responsible engineers.

Methodology to Support Dynamic Function Allocation Policies Between Humans and Flight Deck Automation

NASA Technical Reports Server (NTRS)

Johnson, Eric N.

2012-01-01

Function allocation assigns work functions to all agents in a team, both human and automation. Efforts to guide function allocation systematically have been studied in many fields such as engineering, human factors, team and organization design, management science, cognitive systems engineering. Each field focuses on certain aspects of function allocation, but not all; thus, an independent discussion of each does not address all necessary aspects of function allocation. Four distinctive perspectives have emerged from this comprehensive review of literature on those fields: the technology-centered, human-centered, team-oriented, and work-oriented perspectives. Each perspective focuses on different aspects of function allocation: capabilities and characteristics of agents (automation or human), structure and strategy of a team, and work structure and environment. This report offers eight issues with function allocation that can be used to assess the extent to which each of issues exist on a given function allocation. A modeling framework using formal models and simulation was developed to model work as described by the environment, agents, their inherent dynamics, and relationships among them. Finally, to validate the framework and metrics, a case study modeled four different function allocations between a pilot and flight deck automation during the arrival and approach phases of flight.

NASA's Gravitational - Wave Mission Concept Study

NASA Technical Reports Server (NTRS)

Stebbins, Robin; Jennrich, Oliver; McNamara, Paul

2012-01-01

With the conclusion of the NASA/ESA partnership on the Laser Interferometer Space Antenna (LISA) Project, NASA initiated a study to explore mission concepts that will accomplish some or all of the LISA science objectives at lower cost. The Gravitational-Wave Mission Concept Study consisted of a public Request for Information (RFI), a Core Team of NASA engineers and scientists, a Community Science Team, a Science Task Force, and an open workshop. The RFI yielded were 12 mission concepts, 3 instrument concepts and 2 technologies. The responses ranged from concepts that eliminated the drag-free test mass of LISA to concepts that replace the test mass with an atom interferometer. The Core Team reviewed the noise budgets and sensitivity curves, the payload and spacecraft designs and requirements, orbits and trajectories and technical readiness and risk. The Science Task Force assessed the science performance by calculating the horizons. the detection rates and the accuracy of astrophysical parameter estimation for massive black hole mergers, stellar-mass compact objects inspiraling into central engines. and close compact binary systems. Three mission concepts have been studied by Team-X, JPL's concurrent design facility. to define a conceptual design evaluate kt,y performance parameters. assess risk and estimate cost and schedule. The Study results are summarized.

Discourse in freshman engineering teams: The relationship between verbal persuasions, self-efficacy, and achievement

NASA Astrophysics Data System (ADS)

Yasar, Senay

Collaborative teamwork is a common practice in both science and engineering schools and workplaces. This study, using a mixed-methods approach, was designed to identify which team discourse characteristics are correlated with changes in student self-efficacy and achievement. Bandura's self-efficacy theory constitutes the theoretical framework. Seven teams, consisting of first-year engineering students, took the pre- and post-surveys and were video- and audio-recorded during a semester-long Introduction to Engineering Design course. Three instruments were developed: a self-efficacy survey, a team interaction observation protocol, and a team interaction self-report survey. The reliability and validity of these instruments were established. An iterative process of code development and refinement led to the development of thirty-five discourse types, which were grouped under six discourse categories: task-oriented, response-oriented, learning-oriented, support-oriented, challenge-oriented, and disruptive. The results of the quantitative data analysis showed that achievement and gain in self-efficacy were significantly correlated ( r=.55, p<.01). There was also a positive correlation between support-orientated discourse and post self-efficacy scores ( r=.43, p<.05). Negative correlations were observed between disruptive discourse behaviors and post self-efficacy (r=-.48, p<.05). Neither being challenged by peers nor receiving negative feedback revealed significant correlations with student self-efficacy. In addition, no direct correlations between the team discourse characteristics and achievement were found. These findings suggest that collaborative teamwork can lead to achievement to the extent that it supports self-efficacy. They also suggest that interactions such as receiving positive or negative feedback have less impact on self-efficacy than does the overall constructive behavior of the group. The qualitative component of the study, which focused on three case studies, presents how supportive and disruptive interactions occurred during team discourse. Discussion includes recommendations for educators on how to help teams build supportive environments as well as what to look for when forming teams and evaluating student team interactions.

Noyce SWARMS Scholars and Two Professional Development Models (LASSI and RAMPED): Summer 2015, 2016, and 2017

NASA Astrophysics Data System (ADS)

Burrows, Andrea C.; Myers, Adam D.; Borowczak, Mike

2018-06-01

This poster showcases an astronomy professional development (PD) for 41 K-12 teachers. The project was entitled Launching Astronomy Standards and STEM Integration (LASSI). A project description (activities in the 18 months - Summer 2015 and 2016) for the astronomy, authentic science, and pre-service teacher opportunities is included. The PD team utilized real-world problems, participant-generated questions, science instruments, technology, evidence, communication, dissemination, and collaboration in the LASSI PD model. Computer science was a feature of the PD and the K-12 teacher participants showcased various methods of its use. Embracing an engineering process with an authentic astronomy PD allowed participants to make connections to current topics and create shareable projects. The PD team highlights teacher work from LASSI entitled - A Model for Determining Size of Objects in an Artificial Solar System. The Sustaining Wyoming's Advancing Reach in Mathematics and Science (SWARMS) Scholars (NSF Noyce funded) interacted with and used the materials from the LASSI PD. The poster highlights PD use from the LASSI participants and SWARMS Scholars as well as explains lessons learned to date as a follow-up PD Robotics, Applied Mathematics, Physics, and Engineering Design (RAMPED) was implemented in Summer 2017 and carried methods from LASSI. The LASSI and RAMPED PD teams included faculty from the College of Education, College of Engineering and Applied Science, College of Arts and Sciences, graduate students, and the teachers themselves. The PD teams created a website with these and other PD materials - UWpd.org - for others to view and change to meet their needs.

Re-engineering NASA's space communications to remain viable in a constrained fiscal environment

NASA Astrophysics Data System (ADS)

Hornstein, Rhoda Shaller; Hei, Donald J., Jr.; Kelly, Angelita C.; Lightfoot, Patricia C.; Bell, Holland T.; Cureton-Snead, Izeller E.; Hurd, William J.; Scales, Charles H.

1994-11-01

Along with the Red and Blue Teams commissioned by the NASA Administrator in 1992, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo, including current work processes, functional distinctions, interfaces, and information flow, as well as traditional management and system development practices. The Blue Team's unconstrained, non-parochial, and imaginative look at NASA's space communications program produced a simplified representation of the space communications infrastructure that transcends organizational and functional boundaries, in addition to existing systems and facilities. Further, the Blue Team adapted the 'faster, better, cheaper' charter to be relevant to the multi-mission, continuous nature of the space communications program and to serve as a gauge for improving customer services concurrent with achieving more efficient operations and infrastructure life cycle economies. This simplified representation, together with the adapted metrics, offers a future view and process model for reengineering NASA's space communications to remain viable in a constrained fiscal environment. Code O remains firm in its commitment to improve productivity, effectiveness, and efficiency. In October 1992, the Associate Administrator reconstituted the Blue Team as the Code O Success Team (COST) to serve as a catalyst for change. In this paper, the COST presents the chronicle and significance of the simplified representation and adapted metrics, and their application during the FY 1993-1994 activities.

Re-engineering NASA's space communications to remain viable in a constrained fiscal environment

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller; Hei, Donald J., Jr.; Kelly, Angelita C.; Lightfoot, Patricia C.; Bell, Holland T.; Cureton-Snead, Izeller E.; Hurd, William J.; Scales, Charles H.

1994-01-01

Along with the Red and Blue Teams commissioned by the NASA Administrator in 1992, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo, including current work processes, functional distinctions, interfaces, and information flow, as well as traditional management and system development practices. The Blue Team's unconstrained, non-parochial, and imaginative look at NASA's space communications program produced a simplified representation of the space communications infrastructure that transcends organizational and functional boundaries, in addition to existing systems and facilities. Further, the Blue Team adapted the 'faster, better, cheaper' charter to be relevant to the multi-mission, continuous nature of the space communications program and to serve as a gauge for improving customer services concurrent with achieving more efficient operations and infrastructure life cycle economies. This simplified representation, together with the adapted metrics, offers a future view and process model for reengineering NASA's space communications to remain viable in a constrained fiscal environment. Code O remains firm in its commitment to improve productivity, effectiveness, and efficiency. In October 1992, the Associate Administrator reconstituted the Blue Team as the Code O Success Team (COST) to serve as a catalyst for change. In this paper, the COST presents the chronicle and significance of the simplified representation and adapted metrics, and their application during the FY 1993-1994 activities.

KSC-98pc786

NASA Image and Video Library

1998-07-06

James W. Tibble (pointing at engine), an Engine Systems/Ground Support Equipment team manager for Rocketdyne, discusses the operation of a Space Shuttle Main Engine with Robert B. Sieck, director of Shuttle Processing; U.S. Congressman Dave Weldon; and KSC Center Director Roy D. Bridges Jr. Following the ribbon cutting ceremony for KSC's new 34,600-square-foot Space Shuttle Main Engine Processing Facility (SSMEPF), KSC employees and media explored the facility. A major addition to the existing Orbiter Processing Facility Bay 3, the SSMEPF replaces the Shuttle Main Engine Shop located in the Vehicle Assembly Building (VAB). The decision to move the shop out of the VAB was prompted by safety considerations and recent engine processing improvements. The first three main engines to be processed in the new facility will fly on Shuttle Endeavour's STS-88 mission in December 1998

The SSMEPF opens with a ribbon-cutting ceremony

NASA Technical Reports Server (NTRS)

1998-01-01

James W. Tibble (pointing at engine), an Engine Systems/Ground Support Equipment team manager for Rocketdyne, discusses the operation of a Space Shuttle Main Engine with Robert B. Sieck, director of Shuttle Processing; U.S. Congressman Dave Weldon; and KSC Center Director Roy D. Bridges Jr. Following the ribbon cutting ceremony for KSC's new 34,600-square-foot Space Shuttle Main Engine Processing Facility (SSMEPF), KSC employees and media explored the facility. A major addition to the existing Orbiter Processing Facility Bay 3, the SSMEPF replaces the Shuttle Main Engine Shop located in the Vehicle Assembly Building (VAB). The decision to move the shop out of the VAB was prompted by safety considerations and recent engine processing improvements. The first three main engines to be processed in the new facility will fly on Shuttle Endeavour's STS-88 mission in December 1998.

Oil-Free Turbomachinery Research Enhanced by Thrust Bearing Test Capability

NASA Technical Reports Server (NTRS)

Bauman, Steven W.

2003-01-01

NASA Glenn Research Center s Oil-Free Turbomachinery research team is developing aircraft turbine engines that will not require an oil lubrication system. Oil systems are required today to lubricate rolling-element bearings used by the turbine and fan shafts. For the Oil-Free Turbomachinery concept, researchers combined the most advanced foil (air) bearings from industry with NASA-developed high-temperature solid lubricant technology. In 1999, the world s first Oil-Free turbocharger was demonstrated using these technologies. Now we are working with industry to demonstrate Oil-Free turbomachinery technology in a small business jet engine, the EJ-22 produced by Williams International and developed during Glenn s recently concluded General Aviation Propulsion (GAP) program. Eliminating the oil system in this engine will make it simpler, lighter (approximately 15 percent), more reliable, and less costly to purchase and maintain. Propulsion gas turbines will place high demands on foil air bearings, especially the thrust bearings. Up until now, the Oil-Free Turbomachinery research team only had the capability to test radial, journal bearings. This research has resulted in major improvements in the bearings performance, but journal bearings are cylindrical, and can only support radial shaft loads. To counteract axial thrust loads, thrust foil bearings, which are disk shaped, are required. Since relatively little research has been conducted on thrust foil air bearings, their performance lags behind that of journal bearings.

Turkey BILSAT-1: a Case Study for the Surrey Know-How Transfer and Training Program

NASA Astrophysics Data System (ADS)

Ghafoor, Nadeem; Murat Leloglu, Ugur; Sweeting, Martin, , Sir

2002-01-01

Surrey has established itself over the past 18 years as a world leader in providing hands-on spacecraft engineering training through its Small Satellite Engineering Know-How Transfer and Training (`KHTT') programme. This 18- month course runs alongside the construction of a microsatellite executed through SSTL, and strikes a balance between classroom-based teaching and total immersion within professional engineering teams. Hands-on training is provided covering the entire satellite engineering process, from mission and subsystem design, through module manufacture, assembly and integration, to qualification and flight model environmental tests, launch and commissioning. SSTL's experience in providing the KHTT programme has resulted in a well-defined course structure that yet retains the ability to accommodate individual customer requirements. The programme also takes full advantage of SSTL's intrinsic link with the Surrey Space Centre (`SSC') at the University of Surrey, offering a range of MSc and PhD research programmes pursuing common research interests of both SSTL and the customer, and in many cases complementing the development of either the customer's satellite or their future plans for an evolved space capability. Throughout 2002, three KHTT programmes have run in parallel at SSTL. A team of 11 engineers from the Centre Nationale des Techniques Spatiales in Algeria have now reached completion of their programme with Alsat-1, the first enhanced microsatellite of the Disaster Monitoring Constellation (`DMC'). In December 2001, 15 engineers from the Federal Ministry of Science and Technology in Nigeria arrived at SSTL and are now midway through their programme with Nigeriasat-1, the second enhanced microsatellite of the DMC. Thirdly, arriving slightly earlier in August 2001, a team from Tubitak-Bilten in Turkey commenced their KHTT programme with BILSAT-1, a high-capability enhanced microsatellite also contributing to the DMC, and are due to continue through February 2003. This paper explores the case of BILSAT-1 as a particular example of the SSTL KHTT approach. The BILSAT-1 KHTT team comprises a core group of 8 young engineers with strong backgrounds in mechanical, electrical and electronic engineering. Complementing the activities of this SSTL-based team are 4 MSc students conducting research at the Surrey Space Centre and a number of academic staff and technicians at Tubitak-Bilten in Ankara. The core team engineers, upon completing their academic lecture programme, immediately became involved in the development work on BILSAT-1. Hardware experience has been gained through the building, integrating and testing of an engineering model, before the team proceeds with testing of the assembled BILSAT-1 flight model. The team has also worked with their colleagues at Tubitak-Bilten in proposing and designing two of the BILSAT-1 payloads, the multispectral imager and the high-performance DSP card, both being manufactured in Turkey. In support of the new facility being built at Tubitak-Bilten several future cleanroom and ECAD staff visited SSTL earlier this year to attend soldering and PCB manufacturing courses. With training in project management forming the final component of the KHTT team's training a firm basis is established from which Tubitak-Bilten hopes to further develop its own satellite production capabilities.

Assisting Instructional Assessment of Undergraduate Collaborative Wiki and SVN Activities

ERIC Educational Resources Information Center

Kim, Jihie; Shaw, Erin; Xu, Hao; Adarsh, G. V.

2012-01-01

In this paper we examine the collaborative performance of undergraduate engineering students who used shared project documents (Wikis, Google documents) and a software version control system (SVN) to support project collaboration. We present an initial implementation of TeamAnalytics, an instructional tool that facilitates the analyses of the…

The Five-Factor Model Personality Assessment for Improved Student Design Team Performance

ERIC Educational Resources Information Center

Ogot, Madara; Okudan, Gul E.

2006-01-01

Researchers have long noted the correlation of various personality traits and team performance. Studies relating aggregate team personality traits to team performance are scattered in the literature and may not always be relevant to engineering design teams. This paper synthesizes the results from applicable Five-Factor Model (FFM)-based…

Measuring Learners' Attitudes toward Team Projects: Scale Development Through Exploratory And Confirmatory Factor Analyses

ERIC Educational Resources Information Center

Chyung, Seung Youn; Winiecki, Donald J.; Hunt, Gary; Sevier, Carol M.

2017-01-01

Team projects are increasingly used in engineering courses. Students may develop attitudes toward team projects from prior experience, and their attitudinal responses could influence their performance during team project-based learning in the future. Thus, instructors need to measure students' attitudes toward team projects during their learner…

Conceptual Design of In-Space Vehicles for Human Exploration of the Outer Planets

NASA Technical Reports Server (NTRS)

Adams, R. B.; Alexander, R. A.; Chapman, J. M.; Fincher, S. S.; Hopkins, R. C.; Philips, A. D.; Polsgrove, T. T.; Litchford, R. J.; Patton, B. W.; Statham, G.

2003-01-01

During FY-2002, a team of engineers from TD30/Advanced Concepts and TD40/Propulsion Research Center embarked on a study of potential crewed missions to the outer solar system. The study was conducted under the auspices of the Revolutionary Aerospace Systems Concepts activity administered by Langley Research Center (LaRC). The Marshall Space Flight Center (MSFC) team interacted heavily with teams from other Centers including Glenn Research Center, LaRC, Jet Propulsion Laboratory, and Johnson Space Center. The MSFC team generated five concept missions for this project. The concept missions use a variety of technologies, including magnetized target fusion (MTF), magnetoplasmadynamic thrusters, solid core reactors, and molten salt reactors in various combinations. The Technical Publication (TP) reviews these five concepts and the methods used to generate them. The analytical methods used are described for all significant disciplines and subsystems. The propulsion and power technologies selected for each vehicle are reviewed in detail. The MSFC team also expended considerable effort refining the MTF concept for use with this mission. The results from this effort are also contained within this TP. Finally, the lessons learned from this activity are summarized in the conclusions section.

Readiness for First Crewed Flight

NASA Technical Reports Server (NTRS)

Schaible, Dawn M.

2011-01-01

The NASA Engineering and Safety Center (NESC) was requested to develop a generic framework for evaluating whether any given program has sufficiently complete and balanced plans in place to allow crewmembers to fly safely on a human spaceflight system for the first time (i.e., first crewed flight). The NESC assembled a small team which included experts with experience developing robotic and human spaceflight and aviation systems through first crewed test flight and into operational capability. The NESC team conducted a historical review of the steps leading up to the first crewed flights of Mercury through the Space Shuttle. Benchmarking was also conducted with the United States (U.S.) Air Force and U.S. Navy. This report contains documentation of that review.

GFAST Software Demonstration

NASA Image and Video Library

2017-03-17

NASA engineers and test directors gather in Firing Room 3 in the Launch Control Center at NASA's Kennedy Space Center in Florida, to watch a demonstration of the automated command and control software for the agency's Space Launch System (SLS) and Orion spacecraft. The software is called the Ground Launch Sequencer. It will be responsible for nearly all of the launch commit criteria during the final phases of launch countdowns. The Ground and Flight Application Software Team (GFAST) demonstrated the software. It was developed by the Command, Control and Communications team in the Ground Systems Development and Operations (GSDO) Program. GSDO is helping to prepare the center for the first test flight of Orion atop the SLS on Exploration Mission 1.

Stennis group receives NESC award

NASA Image and Video Library

2009-04-14

The NASA Engineering & Safety Center recently presented its Group Achievement Award to a Stennis team in recognition of technical excellence in evaluating the operational anomalies and reliability improvements associated with the space shuttle engine cut-off system. Stennis employees receiving the award were: (standing, l to r) Freddie Douglas (NASA), George Drouant (Jacobs Technology Inc.), Fred Abell (Jacobs), Robert Drackett (Jacobs) and Mike Smiles (NASA); (seated, l to r): Binh Nguyen (Jacobs), Stennis Director Gene Goldman and Joseph Lacker (NASA). Phillip Hebert of NASA is not pictured.

Systems Engineering Lessons Learned from Solar Array Structures and Mechanisms Deployment

NASA Technical Reports Server (NTRS)

Vipavetz, Kevin; Kraft, Thomas

2013-01-01

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the Engineering Directorate at LaRC. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

Apollo 1 Lessons Learned Show

NASA Image and Video Library

2017-01-27

Charlie Duke, former Apollo 16 astronaut and member of the Apollo 1 Emergency Egress Investigation Team, speaks to participants during the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA's Kennedy Space Center in Florida. The program's theme was "To There and Back Again." Other guest panelists included Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.

Stennis group receives NESC award

NASA Technical Reports Server (NTRS)

2009-01-01

The NASA Engineering & Safety Center recently presented its Group Achievement Award to a Stennis team in recognition of technical excellence in evaluating the operational anomalies and reliability improvements associated with the space shuttle engine cut-off system. Stennis employees receiving the award were: (standing, l to r) Freddie Douglas (NASA), George Drouant (Jacobs Technology Inc.), Fred Abell (Jacobs), Robert Drackett (Jacobs) and Mike Smiles (NASA); (seated, l to r): Binh Nguyen (Jacobs), Stennis Director Gene Goldman and Joseph Lacker (NASA). Phillip Hebert of NASA is not pictured.

Proposing an Evidence-Based Strategy for Software Requirements Engineering.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2016-01-01

This paper discusses an evidence-based approach to software requirements engineering. The approach is called evidence-based, since it uses publications on the specific problem as a surrogate for stakeholder interests, to formulate risks and testing experiences. This complements the idea that agile software development models are more relevant, in which requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The strategy is exemplified and applied to the development of a Software Requirements list used to develop software systems for patient registries.

Component Cost Reduction by Value Engineering: A Case Study

NASA Astrophysics Data System (ADS)

Kalluri, Vinayak; Kodali, Rambabu

2017-04-01

The concept value engineering (VE) acts to increase the value of a product through the improvement in existent functions without increasing their costs. In other words, VE is a function oriented, systematic team approach study to provide value in a product, system or service. The authors systematically explore VE through the six step framework proposed by SAVE and a case study is presented to address the concern of reduction in cost without compromising the function of a hydraulic steering cylinder through the aforementioned VE framework.

Leader evaluation and team cohesiveness in the process of team development: A matter of gender?

PubMed Central

Sczesny, Sabine; Gumí, Tània; Guimerà, Roger; Sales-Pardo, Marta

2017-01-01

Leadership positions are still stereotyped as masculine, especially in male-dominated fields (e.g., engineering). So how do gender stereotypes affect the evaluation of leaders and team cohesiveness in the process of team development? In our study participants worked in 45 small teams (4–5 members). Each team was headed by either a female or male leader, so that 45 leaders (33% women) supervised 258 team members (39% women). Over a period of nine months, the teams developed specific engineering projects as part of their professional undergraduate training. We examined leaders’ self-evaluation, their evaluation by team members, and team cohesiveness at two points of time (month three and month nine, the final month of the collaboration). While we did not find any gender differences in leaders’ self-evaluation at the beginning, female leaders evaluated themselves more favorably than men at the end of the projects. Moreover, female leaders were evaluated more favorably than male leaders at the beginning of the project, but the evaluation by team members did not differ at the end of the projects. Finally, we found a tendency for female leaders to build more cohesive teams than male leaders. PMID:29059231

Human Planetary Landing System (HPLS) Capability Roadmap NRC Progress Review

NASA Technical Reports Server (NTRS)

Manning, Rob; Schmitt, Harrison H.; Graves, Claude

2005-01-01

Capability Roadmap Team. Capability Description, Scope and Capability Breakdown Structure. Benefits of the HPLS. Roadmap Process and Approach. Current State-of-the-Art, Assumptions and Key Requirements. Top Level HPLS Roadmap. Capability Presentations by Leads. Mission Drivers Requirements. "AEDL" System Engineering. Communication & Navigation Systems. Hypersonic Systems. Super to Subsonic Decelerator Systems. Terminal Descent and Landing Systems. A Priori In-Situ Mars Observations. AEDL Analysis, Test and Validation Infrastructure. Capability Technical Challenges. Capability Connection Points to other Roadmaps/Crosswalks. Summary of Top Level Capability. Forward Work.

Systems engineering in practice: can rigour and creativity co-exist?

NASA Astrophysics Data System (ADS)

Schnetler, Hermine; Rees, Philip; Egan, Ian

2006-06-01

Systems engineering as a discipline has been established for many years, being utilised to good effect most notably, in the defence industry. Its introduction in a formalised way to the UK ATC is relatively recent. Although a good start has been made in embedding the process within the lifecycle model, much work is still required to refine the systems engineering elements to cope with the complex (internationally collaborative) business model, the need to nurture creativity in the design process and the translation into a highly challenging cost-driven technology domain. This paper explores the current status of systems engineering at the UK ATC, shows where further work is needed, and how improvements can be made to meet the challenges of next generation telescopes and instrumentation. It is shown why the discipline is necessary, especially given that projects often comprise diverse global teams (both small and large), and it indicates the pitfalls of a tendency in the early stages of a project to focus on solutions rather than robust requirements capture. Finally, despite the obvious value and yet often ill-understood rigours of system engineering, it is shown how innovation and creativity can be promoted rather than stifled.

Case Studies in Application of System Engineering Practices to Capstone Projects

NASA Technical Reports Server (NTRS)

Murphy, Gloria; vanSusante, Paul; Carmen, Christina; Morris, Tommy; Schmidt, Peter; Zalewski, Janusz

2011-01-01

The Exploration Systems Mission Directorate (ESMD) of the National Aeronautics and Space Administration (NASA) sponsors a faculty fellowship program that engages researchers with interests aligned with current ESMD development programs. The faculty-members are committed to run a capstone senior design project based- on the materials and experience gained during the fellowship. For the 2010 - 2011 academic year, 5 projects were approved. These projects are in the areas of mechanical and electrical hardware design and optimization, fault prediction and extra planetary civil site preparation. This work summarizes the projects, describes the student teams performing the work, and comments on the integration of Systems Engineering principles into the projects, as well as the affected course curriculums.

M.U.S.T. 2007 Summer Research Project at NASA's KSC MILA Facility

NASA Technical Reports Server (NTRS)

PintoRey, Christian R.

2007-01-01

The summer research activity at Kennedy Space Center (KSC) aims to introduce the student to the basic principles in their field of study. While at KSC, a specific research project awaits the student to complete. As an Aeronautical Engineering student, my assigned project is to assist the cognizant engineer, Mr. Troy Hamilton, in the six engineering phases for replacing the Ponce De Leon (PDL)4.3M Antenna Control Unit (ACU). Although the project mainly requires the attention of two engineers and two students, it also involves the participation of many colleagues at various points during the course of the engineering change (EC). Since the PDL 4.3M ACU engineering change makes both hardware and software changes, it calls upon the expertise of a Hardware Engineer as well as a Software Engineer. As students, Mr. Jeremy Bresette and I have worked side by side with the engineers, gaining invaluable experience. We work in two teams, the hardware team and the software team, On certain tasks, we assist the engineers, while on others we assume their roles. By diligently working in this fashion, we are learning how to communicate effectively as professionals, despite the fact that we are studying different engineering fields. This project has been a great fit for my field of study, as it has highly improved my awareness of the many critical tasks involved in carrying out an engineering project.

KSC-03pd0272

NASA Image and Video Library

2003-02-05

KENNEDY SPACE CENTER, FLA. - Don Maxwell, Safety, United Space Alliance, checks a map of Texas during a meeting of the Recovery Management Team at KSC. The team is part of the investigation into the accident that claimed orbiter Columbia and her crew of seven on Feb. 1, 2003, over East Texas as they returned to Earth after a 16-day research mission. Other team members are Russ DeLoach, chief, Shuttle Mission Assurance Branch, NASA; George Jacobs, Shuttle Engineering; Jeff Campbell, Shuttle Engineering; Dave Rainer, Launch and Landing Operations; the two co-chairs of the Response Management Team, Denny Gagen, Landing Recovery Manager, Chris Hasselbring, Landing Operations, USA; and Larry Ulmer, Safety, NASA. The team is coordinating KSC technical support and assets to the Mishap Investigation Team in Barksdale, La., and providing support for the Recovery teams in Los Angeles, Texas, New Mexico, Arizona and California. In addition, the team is following up on local leads pertaining to potential debris in the KSC area. .

Team LunaCY Outreach Paper

NASA Technical Reports Server (NTRS)

Heise, James; Hull, Bethanne J.

2012-01-01

Iowa State University's Lunabotics Club, Team LunaCY, has worked hard to generate enthusiasm for robotics, engineering, and lunar activities. Team LunaCY participated in a variety of different outreach events making a strong impression on Iowa youth. These events led the chair of the mechanical engineering department, Dr. Ted Heindel, to refer to the club's outreach program as "the model that all other engineering clubs should follow." Team LunaCY's outreach activities totaled over 200 hours and captivated over 3000 students and adults throughout the course of this acaden1ic year, reaching out to people all over Iowa and to several special guests. These guests included Vice-President Joe Biden, during a visit to Iowa State University in March 2012, and astronaut Clayton Anderson, during a visit to Iowa State's campus in the fall 2011. Team LunaCY's outreach events created hands on learning opportunities for local youth ranging in age from elementary school children to high school students. The team strove to make a positive impression on Iowa youth and to encourage interest and involvement in scientific fields. The full list of events is shown in Table 1. Three of the major outreach events the team participated in were the FIRST LEGO League, Science Bound, and iExplore STEM Festival.

Computational studies of an intake manifold for restricted engine application

NASA Astrophysics Data System (ADS)

Prasetyo, Bagus Dwi; Ubaidillah, Maharani, Elliza Tri; Setyohandoko, Gabriel; Idris, Muhammad Idzdihar

2018-02-01

The Formula Society of Automotive Engineer (FSAE) student competition is an international contest for a vehicle that entirely designed and built by students from various universities. The engine design in the Formula SAE competition has to comply a tight regulation. Concerning the engine intake line, an air restrictor of circular cross-section less than 20 mm must be fitted between the throttle valve and the engine inlet. The throat is aimed to limit the engine air flow rate as it strongly influences the volumetric efficiency and then the maximum power. This article focuses on the design of the engine intake system of the Bengawan FSAE team vehicle to optimize the engine power output and its stability. The performance of engine intake system is studied through computational fluid dynamics (CFD). The objective of CFD is to know the pressure, velocity, and airflow of the air intake manifold for the best performance of the engine. The three-dimensional drawing of the intake manifold was made, and CFD simulation was conducted using ANSYS FLUENT. Two models were studied. The result shows that the different design produces a different value of the velocity of airflow and the kind of flow type.

Industry Partners at CBE

Science.gov Websites

* Charles M. Salter Associates DIALOG HGA Architects and Engineers HOK Integral Group Interface Engineering + Will SERA Architects Taylor Engineering Team: Atelier Ten Taylor Engineering TRC Energy Services

Requirements Engineering in Building Climate Science Software

NASA Astrophysics Data System (ADS)

Batcheller, Archer L.

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling Framework assists modeling applications, the Earth System Grid distributes data via a web portal, and the NCAR (National Center for Atmospheric Research) Command Language is used to convert, analyze and visualize data. Document analysis, observation, and interviews were used to investigate the requirements-related work. The first research question is about how and why stakeholders engage in a project, and what they do for the project. Two key findings arise. First, user counts are a vital measure of project success, which makes adoption important and makes counting tricky and political. Second, despite the importance of quantities of users, a few particular "power users" develop a relationship with the software developers and play a special role in providing feedback to the software team and integrating the system into user practice. The second research question focuses on how project objectives are articulated and how they are put into practice. The team seeks to both build a software system according to product requirements but also to conduct their work according to process requirements such as user support. Support provides essential communication between users and developers that assists with refining and identifying requirements for the software. It also helps users to learn and apply the software to their real needs. User support is a vital activity for scientific software teams aspiring to create infrastructure. The third research question is about how change in scientific practice and knowledge leads to changes in the software, and vice versa. The "thickness" of a layer of software infrastructure impacts whether the software team or users have control and responsibility for making changes in response to new scientific ideas. Thick infrastructure provides more functionality for users, but gives them less control of it. The stability of infrastructure trades off against the responsiveness that the infrastructure can have to user needs.

Air Force Civil Engineer, Volume 16, Number 2, 2008

DTIC Science & Technology

2008-01-01

HORSE and Prime BEEF work together to put up a legal complex for JTF Guantanamo 11 Building Information Modeling in the Air Force Going beyond CADD 14...construction team. Engineers from the 823rd RED HORSE Squadron, Hurlburt Field, Fla., were responsible for most of the design work. The 474th...BEEF construction team and a RED HORSE design team, we quickly became known as the “Red Bulls.” The advance party — consisting of the first sergeant

Mentoring Undergraduate Students through the Space Shuttle Hitchhiker GoldHELOX Project

NASA Astrophysics Data System (ADS)

Moody, J. Ward; Barnes, Jonathan; Roming, Peter; Durfee, Dallin; Campbell, Branton; Turley, Steve; Eastman, Paul

2015-01-01

In the late 1980s a team of four BYU undergraduate students designed a space-based telescope to image the sun in soft x-rays from 171-181 Angstroms to gain information on microflares and their relation to the corona-chromosphere transition region. The telescope used a near-normal incidence multi-layered mirror imaging onto film through a micro-channel plate. The system was capable of 1.0 sec time resolution and 2.5 arcsec spatial resolution. Aided by a NASA grant in 1991, a system was built and successfully tested in 1998 at Marshall Space Flight Center. Originally designed to be deployed from a Get-Away-Special (GAS) canister in the bay of a space shuttle, the good results of this test elevated GoldHelox to greater-priority Hitchhiker status. Even so technical and procedural difficulties delayed a launch until after 2003. Unfortunately after the Columbia re-entry break-up in February 2003, the Hitchhiker program was cancelled and the GoldHelox project ended.Well over 200 undergraduate students worked on GoldHelox. Many of these have since earned advanced degrees in a variety of technical fields. Several have gone on to work in the space industry, becoming NASA scientists and engineers with one becoming a PI on the Swift satellite. The broad range of talent on the team has included students majoring in physics, astronomy, mechanical engineering, electrical engineering, manufacturing engineering, design engineering, business and even English majors who have written technical and public relations documents. We report on lessons learned and the pitfalls and successes of this unique mentoring experience.

Accident analysis and control options in support of the sludge water system safety analysis

DOE Office of Scientific and Technical Information (OSTI.GOV)

HEY, B.E.

A hazards analysis was initiated for the SWS in July 2001 (SNF-8626, K Basin Sludge and Water System Preliminary Hazard Analysis) and updated in December 2001 (SNF-10020 Rev. 0, Hazard Evaluation for KE Sludge and Water System - Project A16) based on conceptual design information for the Sludge Retrieval System (SRS) and 60% design information for the cask and container. SNF-10020 was again revised in September 2002 to incorporate new hazards identified from final design information and from a What-if/Checklist evaluation of operational steps. The process hazards, controls, and qualitative consequence and frequency estimates taken from these efforts have beenmore » incorporated into Revision 5 of HNF-3960, K Basins Hazards Analysis. The hazards identification process documented in the above referenced reports utilized standard industrial safety techniques (AIChE 1992, Guidelines for Hazard Evaluation Procedures) to systematically guide several interdisciplinary teams through the system using a pre-established set of process parameters (e.g., flow, temperature, pressure) and guide words (e.g., high, low, more, less). The teams generally included representation from the U.S. Department of Energy (DOE), K Basins Nuclear Safety, T Plant Nuclear Safety, K Basin Industrial Safety, fire protection, project engineering, operations, and facility engineering.« less

GSFC Technical Outreach: The Capitol College Model

NASA Technical Reports Server (NTRS)

Marius, Julio L.; Wagner, David

2008-01-01

In February 2005, as part of the National Aeronautic and Space Administration (NASA) Technical Outreach Program, Goddard Space Flight Center (GSFC) awarded Capitol College of Laurel, Maryland an Educational Grant to establish a Space Operation academic curriculum to meet the future needs of mission operations engineers. This was in part due to the aerospace industry and GSFC concerns that a large number of professional engineers are projected to retire in the near term with evidence showing that current enrollment in engineering schools will not produce sufficient number of space operation trained engineers that will meet industry and government demands. Capitol College, under the agreement of the Educational Grant, established the Space Operations Institute (SOI) with a new curriculum in Space Operations that was approved and certified by the State of Maryland. The SO1 programs focuses on attracting, recruiting, and training a pipeline of highly qualified engineers with experience in mission operations, system engineering and development. The selected students are integrated as members of the engineering support team in any of the missions supported by the institute. The students are mentored by professional engineers from several aerospace companies that support GSFC. Initially, the institute was involved in providing console engineers and mission planning trainees for the Upper Atmosphere Research Satellite (UARS), the Earth Radiation Budget Satellite (ERBS) and the Total Ozone Mapping Spectrometer mission (TOMS). Subsequently, the students were also involved in the technology refresh of the TOMS ground system and other mission operations development. Further mission assignment by GSFC management included participation in the Tropical Rainfall Measuring Mission (TRMM) mission operations and ground system technology refresh. The SOI program has been very successful. Since October 2005, sixty-four students have been enrolled in the SOI program and twenty-five have already graduated from the program, nineteen of whom are employed by company's supporting GSFC. Due to the success of the program, the initial grant period was extended for another period of two years. This paper presents the process that established the SOI as a viable pipeline of mission operations engineers, the lessons learned in the process of dealing with grants, and experience gained in mentoring engineering students that are responsible for particular areas of expertise and functionality. This paper can also be considered a case study and model for integrating a student team with government and industry professionals in the real world of mission operations.

Engineers Without Borders Australia--lessons learned from an innovative approach to the upgrade of water supply infrastructure in Tenganan, Indonesia.

PubMed

Third, K; Fun, O M; Bowen, J; Micenko, A; Grey, V; Prohasky, T

2009-01-01

The community of Tenganan in eastern Bali, Indonesia, has requested technical assistance from Engineers Without Borders Australia (EWB) to improve the quantity and quality of water delivered through their water supply system. This is a unique development project in which the Tenganan people have identified their own needs and developed their own conceptual solution to the problem. For the first time, EWB is undertaking the design phase for the water system by an off-shore design team and project assistance team (PAT) based in Australia. This allows EWB to draw on resources and experience of EWB members and their employing companies in Australia. It also enables young engineers to develop skills and experience in development work without having to leave the country. However, the innovative approach also presented significant challenges to the project members, particularly in establishing appropriate design criteria and the co-ordination of simultaneous activities across Australia. This paper describes the approach taken by EWB and makes a preliminary assessment of the benefits and limitations inherent in this approach. The overall aim of the project is to produce a successful "bottom-up" development action that will deliver a sustainable solution to the Tenganan community.

Using Life-Cycle Human Factors Engineering to Avoid $2.4 Million in Costs: Lessons Learned from NASA's Requirements Verification Process for Space Payloads

NASA Technical Reports Server (NTRS)

Carr, Daniel; Ellenberger, Rich

2008-01-01

The Human Factors Implementation Team (HFIT) process has been used to verify human factors requirements for NASA International Space Station (ISS) payloads since 2003, resulting in $2.4 million in avoided costs. This cost benefit has been realized by greatly reducing the need to process time-consuming formal waivers (exceptions) for individual requirements violations. The HFIT team, which includes astronauts and their technical staff, acts as the single source for human factors requirements integration of payloads. HFIT has the authority to provide inputs during early design phases, thus eliminating many potential requirements violations in a cost-effective manner. In those instances where it is not economically or technically feasible to meet the precise metric of a given requirement, HFIT can work with the payload engineers to develop common sense solutions and formally document that the resulting payload design does not materially affect the astronaut s ability to operate and interact with the payload. The HFIT process is fully ISO 9000 compliant and works concurrently with NASA s formal systems engineering work flow. Due to its success with payloads, the HFIT process is being adapted and extended to ISS systems hardware. Key aspects of this process are also being considered for NASA's Space Shuttle replacement, the Crew Exploration Vehicle.

The Human Powered Submarine Team of Virginia Tech Propulsion System Design Final Report

NASA Technical Reports Server (NTRS)

An, Eric; Bennett, Matt; Callis, Ron; Chen, Chester; Lee, John; Milan-Williams, Kristy

1999-01-01

The Human Powered Submarine Team has been in existence at Virginia Tech since its conception in 1993. Since then, it has served as a way for engineering students from many different disciplines to implement design conception and realization. The first submarine built was Phantom 1, a two-man submarine made of fiberglass. After construction was complete, Phantom 1 was ready for racing, but, unfortunately, suffered fatal problems come race time. The submarine team slowed down a bit after experiencing racing problems, but was revived in 1995 when design efforts for a new two-man submarine, the Phantom 2 commence. The propulsion system consisted of a chain and gear drive system using an ultra-light helicopter tail rotor for a propeller. Although the team learned valuable lessons as a result of Phantom 1's problems, Phantom 2 still experiences problems at races. After various parts of Phantom 2 are redesigned, it is once again ready for racing and proves that the redesign was well worth the time and effort. In 1997, Phantom 2 not only finishes its first race, held in San Diego, California, but comes in third. This success sparks yet another revival of the submarine team and design for the team's current project, the Phantom 3, a one-man submarine, is started. In 1998, the plug for Phantom 3 is built and the hull is constructed. With so many past problems from which to learn, Phantom 3 promises to be the fastest and best-designed submarine the team has developed thus far. The current speed world-record is 7 knots.

Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering

DTIC Science & Technology

2009-10-30

their first session, the team, using ACS, identifies potential stakeholders within the DHS, the CDC, state emergency response agencies, city governments ...variety of government and private sector institutions for new systems, modifications to existing systems and for mapping out operational strategies...irspace syst em," in 11th Confer ence on Aviation, Range, and Ae rospace, 2004, The Boeing Company and Lockheed Martin Corporation , " CONOPS for the syst

Annual report to the NASA Administrator by the Aerospace Safety Advisory Panel on the space shuttle program. Part 2: Summary of information developed in the panel's fact-finding activities

NASA Technical Reports Server (NTRS)

1976-01-01

Safety management areas of concern include the space shuttle main engine, shuttle avionics, orbiter thermal protection system, the external tank program, and the solid rocket booster program. The ground test program and ground support equipment system were reviewed. Systems integration and technical 'conscience' were of major priorities for the investigating teams.

NASA Planetary Science Summer School: Longitudinal Study

NASA Astrophysics Data System (ADS)

Giron, Jennie M.; Sohus, A.

2006-12-01

NASA’s Planetary Science Summer School is a program designed to prepare the next generation of scientists and engineers to participate in future missions of solar system exploration. The opportunity is advertised to science and engineering post-doctoral and graduate students with a strong interest in careers in planetary exploration. Preference is given to U.S. citizens. The “school” consists of a one-week intensive team exercise learning the process of developing a robotic mission concept into reality through concurrent engineering, working with JPL’s Advanced Project Design Team (Team X). This program benefits the students by providing them with skills, knowledge and the experience of collaborating with a concept mission design. A longitudinal study was conducted to assess the impact of the program on the past participants of the program. Data collected included their current contact information, if they are currently part of the planetary exploration community, if participation in the program contributed to any career choices, if the program benefited their career paths, etc. Approximately 37% of 250 past participants responded to the online survey. Of these, 83% indicated that they are actively involved in planetary exploration or aerospace in general; 78% said they had been able to apply what they learned in the program to their current job or professional career; 100% said they would recommend this program to a colleague.

Using Wikis to Investigate Communication, Collaboration and Engagement in Capstone Engineering Design Projects

ERIC Educational Resources Information Center

Berthoud, L.; Gliddon, J.

2018-01-01

In today's global Aerospace industry, virtual workspaces are commonly used for collaboration between geographically distributed multidisciplinary teams. This study investigated the use of wikis to look at communication, collaboration and engagement in 'Capstone' team design projects at the end of an engineering degree. Wikis were set up for teams…

Implementation of Process Oriented Guided Inquiry Learning (POGIL) in Engineering

ERIC Educational Resources Information Center

Douglas, Elliot P.; Chiu, Chu-Chuan

2013-01-01

This paper describes implementation and testing of an active learning, team-based pedagogical approach to instruction in engineering. This pedagogy has been termed Process Oriented Guided Inquiry Learning (POGIL), and is based upon the learning cycle model. Rather than sitting in traditional lectures, students work in teams to complete worksheets…

Effective Engineering Presentations through Teaching Visual Literacy Skills.

ERIC Educational Resources Information Center

Kerns, H. Dan; And Others

This paper describes a faculty resource team in the Bradley University (Illinois) Department of Industrial Engineering that works with student project teams in an effort to improve their visualization and oral presentation skills. Students use state of the art technology to develop and display their visuals. In addition to technology, students are…

The MUSES Satellite Team and Multidisciplinary System Engineering

NASA Technical Reports Server (NTRS)

Chen, John C.; Paiz, Alfred R.; Young, Donald L.

1997-01-01

In a unique partnership between three minority-serving institutions and NASA's Jet Propulsion Laboratory, a new course sequence, including a multidisciplinary capstone design experience, is to be developed and implemented at each of the schools with the ambitious goal of designing, constructing and launching a low-orbit Earth-resources satellite. The three universities involved are North Carolina A&T State University (NCA&T), University of Texas, El Paso (UTEP), and California State University, Los Angeles (CSULA). The schools form a consortium collectively known as MUSES - Minority Universities System Engineering and Satellite. Four aspects of this project make it unique: (1) Including all engineering disciplines in the capstone design course, (2) designing, building and launching an Earth-resources satellite, (3) sustaining the partnership between the three schools to achieve this goal, and (4) implementing systems engineering pedagogy at each of the three schools. This paper will describe the partnership and its goals, the first design of the satellite, the courses developed at NCA&T, and the implementation plan for the course sequence.

JSC Astronaut corps, STS-3 vehicle integration test team and others

NASA Technical Reports Server (NTRS)

1982-01-01

Members of the JSC astronaut corps, STS-3 vehicle integration test (VIT) team and other personnel pose for photograph at the completion of a countdown demonstration test (CDDT) and safety briefings at Launch Pad 39A, Kennedy Space Center. Participants are, from the left, Wilbur J. Etbauer, engineer with the VIT team; George W.S. Abbey, Director of Flight Operations at JSC; Astronaut John H. Young, Chief of the Astronaut Office at JSC; Jack Fleming of Rockwell International; Mission Specialist-Astronaut John M. Lounge; Astronaut Daniel C. Brandenstein; Mission Specialist-Astronaut James D. Van Hoften; Astronauts C. Gordon Fullerton and Jack Lousma, prime crew for STS-3; Olan J. Bertrand, VIT team member; Mission Specialist-Astronaut Kathryn D. Sullivan; Richard W. Nygren, head of the VIT team; and Astronaut Donald E. Williams. The Columbia is obscured by its service structure on Launch Pad 39A in the background. Part of slide-wire emergency escape system is visible in the picture.

Scheduling System Assessment, and Development and Enhancement of Re-engineered Version of GPSS

NASA Technical Reports Server (NTRS)

Loganantharaj, Rasiah; Thomas, Bushrod; Passonno, Nicole

1996-01-01

The objective of this project is two-fold. First to provide an evaluation of a commercially developed version of the ground processing scheduling system (GPSS) for its applicability to the Kennedy Space Center (KSC) ground processing problem. Second, to work with the KSC GPSS development team and provide enhancement to the existing software. Systems reengineering is required to provide a sustainable system for the users and the software maintenance group. Using the LISP profile prototype code developed by the GPSS reverse reengineering groups as a building block, we have implemented the resource deconfliction portion of GPSS in common LISP using its object oriented features. The prototype corrects and extends some of the deficiencies of the current production version, plus it uses and builds on the classes from the development team's profile prototype.

Operation of a Thin-Film Inflatable Concentrator System Demonstrated in a Solar Thermal Vacuum Environment

NASA Technical Reports Server (NTRS)

Wong, Wayne A.

2002-01-01

Thin-film inflatable solar concentrators offer significant advantages in comparison to stateof- the-art rigid panel concentrators, including low weight, low stowage volume, and simple gas deployment. From June 10 to 22, 2001, the ElectroMagnetic Radiation Control Experiment (EMRCE) Team used simulated solar energy to demonstrate the operation of an inflatable concentrator system at NASA Glenn Research Center's Tank 6 thermal vacuum facility. The joint Government/industry test team was composed of engineers and technicians from Glenn, the Air Force Research Laboratory, SRS Technologies, and ATK Thiokol Propulsion. The research hardware consisted of the following: 1) A thin-film inflatable concentrator; 2) The hexapod pointing and focus control system; 3) Two rigidized support struts using two candidate technologies - ultraviolet-rigidized glass and radiation-cured isographite.

Health Management Applications for International Space Station

NASA Technical Reports Server (NTRS)

Alena, Richard; Duncavage, Dan

2005-01-01

Traditional mission and vehicle management involves teams of highly trained specialists monitoring vehicle status and crew activities, responding rapidly to any anomalies encountered during operations. These teams work from the Mission Control Center and have access to engineering support teams with specialized expertise in International Space Station (ISS) subsystems. Integrated System Health Management (ISHM) applications can significantly augment these capabilities by providing enhanced monitoring, prognostic and diagnostic tools for critical decision support and mission management. The Intelligent Systems Division of NASA Ames Research Center is developing many prototype applications using model-based reasoning, data mining and simulation, working with Mission Control through the ISHM Testbed and Prototypes Project. This paper will briefly describe information technology that supports current mission management practice, and will extend this to a vision for future mission control workflow incorporating new ISHM applications. It will describe ISHM applications currently under development at NASA and will define technical approaches for implementing our vision of future human exploration mission management incorporating artificial intelligence and distributed web service architectures using specific examples. Several prototypes are under development, each highlighting a different computational approach. The ISStrider application allows in-depth analysis of Caution and Warning (C&W) events by correlating real-time telemetry with the logical fault trees used to define off-nominal events. The application uses live telemetry data and the Livingstone diagnostic inference engine to display the specific parameters and fault trees that generated the C&W event, allowing a flight controller to identify the root cause of the event from thousands of possibilities by simply navigating animated fault tree models on their workstation. SimStation models the functional power flow for the ISS Electrical Power System and can predict power balance for nominal and off-nominal conditions. SimStation uses realtime telemetry data to keep detailed computational physics models synchronized with actual ISS power system state. In the event of failure, the application can then rapidly diagnose root cause, predict future resource levels and even correlate technical documents relevant to the specific failure. These advanced computational models will allow better insight and more precise control of ISS subsystems, increasing safety margins by speeding up anomaly resolution and reducing,engineering team effort and cost. This technology will make operating ISS more efficient and is directly applicable to next-generation exploration missions and Crew Exploration Vehicles.

Software Assists in Responding to Anomalous Conditions

NASA Technical Reports Server (NTRS)

James, Mark; Kronbert, F.; Weiner, A.; Morgan, T.; Stroozas, B.; Girouard, F.; Hopkins, A.; Wong, L.; Kneubuhl, J.; Malina, R.

2004-01-01

Fault Induced Document Retrieval Officer (FIDO) is a computer program that reduces the need for a large and costly team of engineers and/or technicians to monitor the state of a spacecraft and associated ground systems and respond to anomalies. FIDO includes artificial-intelligence components that imitate the reasoning of human experts with reference to a knowledge base of rules that represent failure modes and to a database of engineering documentation. These components act together to give an unskilled operator instantaneous expert assistance and access to information that can enable resolution of most anomalies, without the need for highly paid experts. FIDO provides a system state summary (a configurable engineering summary) and documentation for diagnosis of a potentially failing component that might have caused a given error message or anomaly. FIDO also enables high-level browsing of documentation by use of an interface indexed to the particular error message. The collection of available documents includes information on operations and associated procedures, engineering problem reports, documentation of components, and engineering drawings. FIDO also affords a capability for combining information on the state of ground systems with detailed, hierarchically-organized, hypertext- enabled documentation.

The MSFC Collaborative Engineering Process for Preliminary Design and Concept Definition Studies

NASA Technical Reports Server (NTRS)

Mulqueen, Jack; Jones, David; Hopkins, Randy

2011-01-01

This paper describes a collaborative engineering process developed by the Marshall Space Flight Center's Advanced Concepts Office for performing rapid preliminary design and mission concept definition studies for potential future NASA missions. The process has been developed and demonstrated for a broad range of mission studies including human space exploration missions, space transportation system studies and in-space science missions. The paper will describe the design team structure and specialized analytical tools that have been developed to enable a unique rapid design process. The collaborative engineering process consists of integrated analysis approach for mission definition, vehicle definition and system engineering. The relevance of the collaborative process elements to the standard NASA NPR 7120.1 system engineering process will be demonstrated. The study definition process flow for each study discipline will be will be outlined beginning with the study planning process, followed by definition of ground rules and assumptions, definition of study trades, mission analysis and subsystem analyses leading to a standardized set of mission concept study products. The flexibility of the collaborative engineering design process to accommodate a wide range of study objectives from technology definition and requirements definition to preliminary design studies will be addressed. The paper will also describe the applicability of the collaborative engineering process to include an integrated systems analysis approach for evaluating the functional requirements of evolving system technologies and capabilities needed to meet the needs of future NASA programs.

Introductory Education for Mechanical Engineering by Exercise in Mechanical Disassembly

NASA Astrophysics Data System (ADS)

Matsui, Yoshio; Asakawa, Naoki; Iwamori, Satoru

An introductory program “Exercise for engineers in mechanical disassembly” is an exercise that ten students of every team disassemble a motor scooter to the components and then assemble again to the initial form in 15 weeks. The purpose of this program is to introduce mechanical engineering by touching the real machine and learning how it is composed from various mechanical parts to the students at the early period after the entrance into the university. Additional short lectures by young teachers and a special lecture by a top engineer in the industry encourage the students to combine the actual machine and the mechanical engineering subjects. Furthermore, various educations such as group leader system, hazard prediction training, parts filing are included in this program. As a result, students recognize the importance of the mechanical engineering study and the way of group working.

Managing Complexity in the MSL/Curiosity Entry, Descent, and Landing Flight Software and Avionics Verification and Validation Campaign

NASA Technical Reports Server (NTRS)

Stehura, Aaron; Rozek, Matthew

2013-01-01

The complexity of the Mars Science Laboratory (MSL) mission presented the Entry, Descent, and Landing systems engineering team with many challenges in its Verification and Validation (V&V) campaign. This paper describes some of the logistical hurdles related to managing a complex set of requirements, test venues, test objectives, and analysis products in the implementation of a specific portion of the overall V&V program to test the interaction of flight software with the MSL avionics suite. Application-specific solutions to these problems are presented herein, which can be generalized to other space missions and to similar formidable systems engineering problems.

KSC-2013-2699

NASA Image and Video Library

2013-06-13

TITUSVILLE, Fla. - NASA Kennedy Space Center Lead Engineer David Bush, center, demos a small liquid-air filled backpack called CryoBA, short for Cryogenic Breathing Apparatus, at BCS Life Support in Titusville, Fla. The CryoBA and a larger Cryogenic Refuge Alternative Supply System, or CryoRASS, are being developed by a Kennedy engineering team in collaboration with The National Institute for Occupational Safety and Health to provide miners with twice the amount of breathable and cooler air than traditional compressed systems. The technology also could be used for commercial applications, such as fire and military rescue operations, as well as NASA's future human spaceflight missions. Photo credit: NASA/Daniel Casper

KSC-2013-2822

NASA Image and Video Library

2013-06-19

CAPE CANAVERAL, Fla. - NASA Kennedy Space Center Lead Engineer David Bush works on a prototype of a Cryogenic Refuge Alternative Supply System, or CryoRASS, in the Operations and Checkout Building. CryoRASS and a small liquid-air filled backpack called CryoBA, short for Cryogenic Breathing Apparatus, are being developed by a NASA Kennedy Space Center engineering team in collaboration with The National Institute for Occupational Safety and Health to provide miners with twice the amount of breathable and cooler air than traditional compressed systems. The technology also could be used for commercial applications, such as fire and military rescue operations, as well as NASA's future human spaceflight missions. Photo credit: NASA/Jim Gossmann