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...
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...
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...
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.
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...
Team-Based Development of Medical Devices: An Engineering-Business Collaborative.
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.
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.
Team-Based Development of Medical Devices: An Engineering–Business Collaborative
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
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…
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.
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.
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...
Modeling to Mars: a NASA Model Based Systems Engineering Pathfinder Effort
NASA Technical Reports Server (NTRS)
Phojanamongkolkij, Nipa; Lee, Kristopher A.; Miller, Scott T.; Vorndran, Kenneth A.; Vaden, Karl R.; Ross, Eric P.; Powell, Bobby C.; Moses, Robert W.
2017-01-01
The NASA Engineering Safety Center (NESC) Systems Engineering (SE) Technical Discipline Team (TDT) initiated the Model Based Systems Engineering (MBSE) Pathfinder effort in FY16. The goals and objectives of the MBSE Pathfinder include developing and advancing MBSE capability across NASA, applying MBSE to real NASA issues, and capturing issues and opportunities surrounding MBSE. The Pathfinder effort consisted of four teams, with each team addressing a particular focus area. This paper focuses on Pathfinder team 1 with the focus area of architectures and mission campaigns. These efforts covered the timeframe of February 2016 through September 2016. The team was comprised of eight team members from seven NASA Centers (Glenn Research Center, Langley Research Center, Ames Research Center, Goddard Space Flight Center IV&V Facility, Johnson Space Center, Marshall Space Flight Center, and Stennis Space Center). Collectively, the team had varying levels of knowledge, skills and expertise in systems engineering and MBSE. The team applied their existing and newly acquired system modeling knowledge and expertise to develop modeling products for a campaign (Program) of crew and cargo missions (Projects) to establish a human presence on Mars utilizing In-Situ Resource Utilization (ISRU). Pathfinder team 1 developed a subset of modeling products that are required for a Program System Requirement Review (SRR)/System Design Review (SDR) and Project Mission Concept Review (MCR)/SRR as defined in NASA Procedural Requirements. Additionally, Team 1 was able to perform and demonstrate some trades and constraint analyses. At the end of these efforts, over twenty lessons learned and recommended next steps have been identified.
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.
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.
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…
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.
An overview of SAE ARP 1587: Aircraft gas turbine engine monitoring system guide
NASA Technical Reports Server (NTRS)
Murphy, J. A.
1981-01-01
A systematic approach to developing an engine monitoring system (EMS) is outlined. An extensive shopping list of EMS capabilities and benefits are included. A team approach to developing an EMS is emphasized with a description of the responsibilities of each team member.
Developing teamwork skills in capstone design courses.
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.
Engineering performance metrics
NASA Astrophysics Data System (ADS)
Delozier, R.; Snyder, N.
1993-03-01
Implementation of a Total Quality Management (TQM) approach to engineering work required the development of a system of metrics which would serve as a meaningful management tool for evaluating effectiveness in accomplishing project objectives and in achieving improved customer satisfaction. A team effort was chartered with the goal of developing a system of engineering performance metrics which would measure customer satisfaction, quality, cost effectiveness, and timeliness. The approach to developing this system involved normal systems design phases including, conceptual design, detailed design, implementation, and integration. The lessons teamed from this effort will be explored in this paper. These lessons learned may provide a starting point for other large engineering organizations seeking to institute a performance measurement system accomplishing project objectives and in achieving improved customer satisfaction. To facilitate this effort, a team was chartered to assist in the development of the metrics system. This team, consisting of customers and Engineering staff members, was utilized to ensure that the needs and views of the customers were considered in the development of performance measurements. The development of a system of metrics is no different than the development of any type of system. It includes the steps of defining performance measurement requirements, measurement process conceptual design, performance measurement and reporting system detailed design, and system implementation and integration.
NASA Technical Reports Server (NTRS)
2004-01-01
In early 1995, NASA s Glenn Research Center (then Lewis Research Center) formed an industry-government team with several jet engine companies to develop the National Combustion Code (NCC), which would help aerospace engineers solve complex aerodynamics and combustion problems in gas turbine, rocket, and hypersonic engines. The original development team consisted of Allison Engine Company (now Rolls-Royce Allison), CFD Research Corporation, GE Aircraft Engines, Pratt and Whitney, and NASA. After the baseline beta version was established in July 1998, the team focused its efforts on consolidation, streamlining, and integration, as well as enhancement, evaluation, validation, and application. These activities, mainly conducted at NASA Glenn, led to the completion of NCC version 1.0 in October 2000. NCC version 1.0 features high-fidelity representation of complex geometry, advanced models for two-phase turbulent combustion, and massively parallel computing. Researchers and engineers at Glenn have been using NCC to provide analysis and design support for various aerospace propulsion technology development projects. NASA transfers NCC technology to external customers using non- exclusive Space Act Agreements. Glenn researchers also communicate research and development results derived from NCC's further development through publications and special sessions at technical conferences.
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…
Achieving Maximum Integration Utilizing Requirements Flow Down
NASA Technical Reports Server (NTRS)
Archiable, Wes; Askins, Bruce
2011-01-01
A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.
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.
Next-generation concurrent engineering: developing models to complement point designs
NASA Technical Reports Server (NTRS)
Morse, Elizabeth; Leavens, Tracy; Cohanim, Babak; Harmon, Corey; Mahr, Eric; Lewis, Brian
2006-01-01
Concurrent Engineering Design (CED) 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; in addition to a point design, the Team develops a model of the local trade space. The process is a balance between the power of a model developing tools and the creativity of humal experts, enabling the development of a variety of trade models for any space mission. This paper reviews the modeling method and its practical implementation in the ED environment. Example results illustrate the benefit of this approach.
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.
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.
An Example of Concurrent Engineering
NASA Technical Reports Server (NTRS)
Rowe, Sidney; Whitten, David; Cloyd, Richard; Coppens, Chris; Rodriguez, Pedro
1998-01-01
The Collaborative Engineering Design and Analysis Room (CEDAR) facility allows on-the- spot design review capability for any project during all phases of development. The required disciplines assemble in this facility to work on any problems (analysis, manufacturing, inspection, etc.) associated with a particular design. A small highly focused team of specialists can meet in this room to better expedite the process of developing a solution to an engineering task within the framework of the constraints that are unique to each discipline. This facility provides the engineering tools and translators to develop a concept within the confines of the room or with remote team members that could access the team's data from other locations. The CEDAR area is envisioned as excellent for failure investigation meetings to be conducted where the computer capabilities can be utilized in conjunction with the Smart Board display to develop failure trees, brainstorm failure modes, and evaluate possible solutions.
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.
Damage-Tolerant, Affordable Composite Engine Cases Designed and Fabricated
NASA Technical Reports Server (NTRS)
Hopkins, Dale A.; Roberts, Gary D.; Pereira, J. Michael; Bowman, Cheryl L.
2005-01-01
An integrated team of NASA personnel, Government contractors, industry partners, and university staff have developed an innovative new technology for commercial fan cases that will substantially influence the safety and efficiency of future turbine engines. This effective team, under the direction of the NASA Glenn Research Center and with the support of the Federal Aviation Administration, has matured a new class of carbon/polymer composites and demonstrated a 30- to 50-percent improvement in specific containment capacity (blade fragment kinetic energy/containment system weight). As the heaviest engine component, the engine case/containment system greatly affects both the safety and efficiency of aircraft engines. The ballistic impact research team has developed unique test facilities and methods for screening numerous candidate material systems to replace the traditional heavy, metallic engine cases. This research has culminated in the selection of a polymer matrix composite reinforced with triaxially braided carbon fibers and technology demonstration through the fabrication of prototype engine cases for three major commercial engine manufacturing companies.
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.
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).
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.
ERIC Educational Resources Information Center
Kearney, Kerri S.; Damron, Rebecca; Sohoni, Sohum
2015-01-01
This paper investigates group/team development in computer engineering courses at a University in the Central USA from the perspective of organization behavior theory, specifically Tuckman's model of the stages of group development. The investigation, conducted through linguistic analysis of student reflection essays, and through focus group…
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…
Leader evaluation and team cohesiveness in the process of team development: A matter of gender?
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
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.
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.
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…
Using A Model-Based Systems Engineering Approach For Exploration Medical System Development
NASA Technical Reports Server (NTRS)
Hanson, A.; Mindock, J.; McGuire, K.; Reilly, J.; Cerro, J.; Othon, W.; Rubin, D.; Urbina, M.; Canga, M.
2017-01-01
NASA's Human Research Program's Exploration Medical Capabilities (ExMC) element is defining the medical system needs for exploration class missions. ExMC's Systems Engineering (SE) team will play a critical role in successful design and implementation of the medical system into exploration vehicles. The team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." Development of the medical system is being conducted in parallel with exploration mission architecture and vehicle design development. Successful implementation of the medical system in this environment will require a robust systems engineering approach to enable technical communication across communities to create a common mental model of the emergent engineering and medical systems. Model-Based Systems Engineering (MBSE) improves shared understanding of system needs and constraints between stakeholders and offers a common language for analysis. The ExMC SE team is using MBSE techniques to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. Systems Modeling Language (SysML) is the specific language the SE team is utilizing, within an MBSE approach, to model the medical system functional needs, requirements, and architecture. Modeling methods are being developed through the practice of MBSE within the team, and tools are being selected to support meta-data exchange as integration points to other system models are identified. Use of MBSE is supporting the development of relationships across disciplines and NASA Centers to build trust and enable teamwork, enhance visibility of team goals, foster a culture of unbiased learning and serving, and be responsive to customer needs. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. Here, we describe the methods and approach to building this integrated model.
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.
Center for Advanced Bioengineering for Soldier Survivability
2013-06-01
useful products have been limited. This is in part because the technology development teams have failed to include clinicians and engineers...to useful products have been limited. This is in part because the technology development teams have failed to include clinicians and engineers...7, 14, 21, and 28 days. After 28 days the samples were explanted, fixed, and scanned for mineralized matrix using Micro -CT imaging. Some samples
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
Ocean Drilling Program: Drilling Services
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
Teaching engineering ethics using BLOCKS game.
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.
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.
Sharing best practices in teaching biomedical engineering design.
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.
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.
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.
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.
A self-referential HOWTO on release engineering
DOE Office of Scientific and Technical Information (OSTI.GOV)
Galassi, Mark C.
Release engineering is a fundamental part of the software development cycle: it is the point at which quality control is exercised and bug fixes are integrated. The way in which software is released also gives the end user her first experience of a software package, while in scientific computing release engineering can guarantee reproducibility. For these reasons and others, the release process is a good indicator of the maturity and organization of a development team. Software teams often do not put in place a release process at the beginning. This is unfortunate because the team does not have early andmore » continuous execution of test suites, and it does not exercise the software in the same conditions as the end users. I describe an approach to release engineering based on the software tools developed and used by the GNU project, together with several specific proposals related to packaging and distribution. I do this in a step-by-step manner, demonstrating how this very paper is written and built using proper release engineering methods. Because many aspects of release engineering are not exercised in the building of the paper, the accompanying software repository also contains examples of software libraries.« less
The structural approach to shared knowledge: an application to engineering design teams.
Avnet, Mark S; Weigel, Annalisa L
2013-06-01
We propose a methodology for analyzing shared knowledge in engineering design teams. Whereas prior work has focused on shared knowledge in small teams at a specific point in time, the model presented here is both scalable and dynamic. By quantifying team members' common views of design drivers, we build a network of shared mental models to reveal the structure of shared knowledge at a snapshot in time. Based on a structural comparison of networks at different points in time, a metric of change in shared knowledge is computed. Analysis of survey data from 12 conceptual space mission design sessions reveals a correlation between change in shared knowledge and each of several system attributes, including system development time, system mass, and technological maturity. From these results, we conclude that an early period of learning and consensus building could be beneficial to the design of engineered systems. Although we do not examine team performance directly, we demonstrate that shared knowledge is related to the technical design and thus provide a foundation for improving design products by incorporating the knowledge and thoughts of the engineering design team into the process.
An Open Source Tool to Test Interoperability
NASA Astrophysics Data System (ADS)
Bermudez, L. E.
2012-12-01
Scientists interact with information at various levels from gathering of the raw observed data to accessing portrayed processed quality control data. Geoinformatics tools help scientist on the acquisition, storage, processing, dissemination and presentation of geospatial information. Most of the interactions occur in a distributed environment between software components that take the role of either client or server. The communication between components includes protocols, encodings of messages and managing of errors. Testing of these communication components is important to guarantee proper implementation of standards. The communication between clients and servers can be adhoc or follow standards. By following standards interoperability between components increase while reducing the time of developing new software. The Open Geospatial Consortium (OGC), not only coordinates the development of standards but also, within the Compliance Testing Program (CITE), provides a testing infrastructure to test clients and servers. The OGC Web-based Test Engine Facility, based on TEAM Engine, allows developers to test Web services and clients for correct implementation of OGC standards. TEAM Engine is a JAVA open source facility, available at Sourceforge that can be run via command line, deployed in a web servlet container or integrated in developer's environment via MAVEN. The TEAM Engine uses the Compliance Test Language (CTL) and TestNG to test HTTP requests, SOAP services and XML instances against Schemas and Schematron based assertions of any type of web service, not only OGC services. For example, the OGC Web Feature Service (WFS) 1.0.0 test has more than 400 test assertions. Some of these assertions includes conformance of HTTP responses, conformance of GML-encoded data; proper values for elements and attributes in the XML; and, correct error responses. This presentation will provide an overview of TEAM Engine, introduction of how to test via the OGC Testing web site and description of performing local tests. It will also provide information about how to participate in the open source code development of TEAM Engine.
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…
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.
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.
Managing MDO Software Development Projects
NASA Technical Reports Server (NTRS)
Townsend, J. C.; Salas, A. O.
2002-01-01
Over the past decade, the NASA Langley Research Center developed a series of 'grand challenge' applications demonstrating the use of parallel and distributed computation and multidisciplinary design optimization. All but the last of these applications were focused on the high-speed civil transport vehicle; the final application focused on reusable launch vehicles. Teams of discipline experts developed these multidisciplinary applications by integrating legacy engineering analysis codes. As teams became larger and the application development became more complex with increasing levels of fidelity and numbers of disciplines, the need for applying software engineering practices became evident. This paper briefly introduces the application projects and then describes the approaches taken in project management and software engineering for each project; lessons learned are highlighted.
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.
Model building techniques for analysis.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Walther, Howard P.; McDaniel, Karen Lynn; Keener, Donald
2009-09-01
The practice of mechanical engineering for product development has evolved into a complex activity that requires a team of specialists for success. Sandia National Laboratories (SNL) has product engineers, mechanical designers, design engineers, manufacturing engineers, mechanical analysts and experimentalists, qualification engineers, and others that contribute through product realization teams to develop new mechanical hardware. The goal of SNL's Design Group is to change product development by enabling design teams to collaborate within a virtual model-based environment whereby analysis is used to guide design decisions. Computer-aided design (CAD) models using PTC's Pro/ENGINEER software tools are heavily relied upon in the productmore » definition stage of parts and assemblies at SNL. The three-dimensional CAD solid model acts as the design solid model that is filled with all of the detailed design definition needed to manufacture the parts. Analysis is an important part of the product development process. The CAD design solid model (DSM) is the foundation for the creation of the analysis solid model (ASM). Creating an ASM from the DSM currently is a time-consuming effort; the turnaround time for results of a design needs to be decreased to have an impact on the overall product development. This effort can be decreased immensely through simple Pro/ENGINEER modeling techniques that summarize to the method features are created in a part model. This document contains recommended modeling techniques that increase the efficiency of the creation of the ASM from the DSM.« less
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
From 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 GDS Team met the SC Sim integration challenge in eight months. The GDS System Engineering approach in response to the SC Simintegration challenge, focused on a set of key practices: decomposition of project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; risk management thru management of expectations; and aggregation of intermediate products into a final product. By maintaining a a system-level focus, the overall systems engineering process unified team GDS Team members with a common goal: the success of the ground system as a whole and not just the success of their individual expert contributions. Incorporation of Agile-type development efforts were aligned with a risk strategy based on team-oriented principles and expectations management, thus achieving a more stable baseline solution without compromising the integrity of the GDS design.
Communication Skills to Develop Trusting Relationships on Global Virtual Engineering Capstone Teams
ERIC Educational Resources Information Center
Zaugg, Holt; Davies, Randall S.
2013-01-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…
Survey Tools for Faculty to Quickly Assess Multidisciplinary Team Dynamics in Capstone Courses
ERIC Educational Resources Information Center
Solnosky, Ryan; Fairchild, Joshua
2017-01-01
Many engineering faculty have limited skills and/or assessment tools to evaluate team dynamics in multidisciplinary team-based capstone courses. Rapidly deployable tools are needed here to provide proactive feedback to teams to facilitate deeper learning. Two surveys were developed based on industrial and organizational psychology theories around…
NASA Astrophysics Data System (ADS)
Arevalo, S.; Atwood, C.; Bell, P.; Blacker, T. D.; Dey, S.; Fisher, D.; Fisher, D. A.; Genalis, P.; Gorski, J.; Harris, A.; Hill, K.; Hurwitz, M.; Kendall, R. P.; Meakin, R. L.; Morton, S.; Moyer, E. T.; Post, D. E.; Strawn, R.; Veldhuizen, D. v.; Votta, L. G.; Wynn, S.; Zelinski, G.
2008-07-01
In FY2008, the U.S. Department of Defense (DoD) initiated the Computational Research and Engineering Acquisition Tools and Environments (CREATE) program, a 360M program with a two-year planning phase and a ten-year execution phase. CREATE will develop and deploy three computational engineering tool sets for DoD acquisition programs to use to design aircraft, ships and radio-frequency antennas. The planning and execution of CREATE are based on the 'lessons learned' from case studies of large-scale computational science and engineering projects. The case studies stress the importance of a stable, close-knit development team; a focus on customer needs and requirements; verification and validation; flexible and agile planning, management, and development processes; risk management; realistic schedules and resource levels; balanced short- and long-term goals and deliverables; and stable, long-term support by the program sponsor. Since it began in FY2008, the CREATE program has built a team and project structure, developed requirements and begun validating them, identified candidate products, established initial connections with the acquisition programs, begun detailed project planning and development, and generated the initial collaboration infrastructure necessary for success by its multi-institutional, multidisciplinary teams.
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.
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 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.
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.
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.
Pediatric medical device development by surgeons via capstone engineering design programs.
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.
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.
Developing Teaching of Mathematics to First Year Engineering Students
ERIC Educational Resources Information Center
Jaworski, Barbara; Matthews, Janette
2011-01-01
Engineering Students Understanding Mathematics (ESUM) is a developmental research project at a UK university. The motivating aim is that engineering students should develop a more conceptual understanding of mathematics through their participation in an innovation in teaching. A small research team has both studied and contributed to innovation,…
Concurrency in product realization
NASA Astrophysics Data System (ADS)
Kelly, Michael J.
1994-03-01
Technology per se does not provide a competitive advantage. Timely exploitation of technology is what gives the competitive edge, and this demands a major shift in the product development process and management of the industrial enterprise. `Teaming to win' is more than a management theme; it is the disciplined engineering practice that is essential to success in today's global marketplace. Teaming supports the concurrent engineering practices required to integrate the activities of people responsible for product realization through achievement of shorter development cycles, lower costs, and defect-free products.
The (mis)use of subjective process measures in software engineering
NASA Technical Reports Server (NTRS)
Valett, Jon D.; Condon, Steven E.
1993-01-01
A variety of measures are used in software engineering research to develop an understanding of the software process and product. These measures fall into three broad categories: quantitative, characteristics, and subjective. Quantitative measures are those to which a numerical value can be assigned, for example effort or lines of code (LOC). Characteristics describe the software process or product; they might include programming language or the type of application. While such factors do not provide a quantitative measurement of a process or product, they do help characterize them. Subjective measures (as defined in this study) are those that are based on the opinion or opinions of individuals; they are somewhat unique and difficult to quantify. Capturing of subjective measure data typically involves development of some type of scale. For example, 'team experience' is one of the subjective measures that were collected and studied by the Software Engineering Laboratory (SEL). Certainly, team experience could have an impact on the software process or product; actually measuring a team's experience, however, is not a strictly mathematical exercise. Simply adding up each team member's years of experience appears inadequate. In fact, most researchers would agree that 'years' do not directly translate into 'experience.' Team experience must be defined subjectively and then a scale must be developed e.g., high experience versus low experience; or high, medium, low experience; or a different or more granular scale. Using this type of scale, a particular team's overall experience can be compared with that of other teams in the development environment. Defining, collecting, and scaling subjective measures is difficult. First, precise definitions of the measures must be established. Next, choices must be made about whose opinions will be solicited to constitute the data. Finally, care must be given to defining the right scale and level of granularity for measurement.
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.
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.
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…
Human Systems Integration Competency Development for Navy Systems Commands
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
Forum on Workforce Development
NASA Technical Reports Server (NTRS)
Hoffman, Edward
2010-01-01
APPEL Mission: To support NASA's mission by promoting individual, team, and organizational excellence in program/project management and engineering through the application of learning strategies, methods, models, and tools. Goals: a) Provide a common frame of reference for NASA s technical workforce. b) Provide and enhance critical job skills. c) Support engineering, program and project teams. d) Promote organizational learning across the agency. e) Supplement formal educational programs.
Achieving Agility and Stability in Large-Scale Software Development
2013-01-16
temporary team is assigned to prepare layers and frameworks for future feature teams. Presentation Layer Domain Layer Data Access Layer...http://www.sei.cmu.edu/training/ elearning ~ Software Engineering Institute CarnegieMellon
Are your engineers talking to one another when they should?
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.
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.
Examining engineering costs for development of highway projects.
DOT National Transportation Integrated Search
2012-12-01
The Texas Department of Transportation (TxDOT) commissioned a research team at Texas State University-San Marcos Department of Accounting to analyze the cost of projects by determining the cost of a preliminary engineering hour necessary to develop h...
ERIC Educational Resources Information Center
Klein, Stacy S.; Sherwood, Robert D.
2005-01-01
This study reports on a multi-year effort to create and evaluate cognitive-based curricular materials for secondary school science classrooms. A team of secondary teachers, educational researchers, and academic biomedical engineers developed a series of curriculum units that are based in biomedical engineering for secondary level students in…
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.
NASA Astrophysics Data System (ADS)
Regnell, Björn; Höst, Martin; Nilsson, Fredrik; Bengtsson, Henrik
When developing software-intensive products for a market-place it is important for a development organisation to create innovative features for coming releases in order to achieve advantage over competitors. This paper focuses on assessment of innovation capability at team level in relation to the requirements engineering that is taking place before the actual product development projects are decided, when new business models, technology opportunities and intellectual property rights are created and investigated through e.g. prototyping and concept development. The result is a measurement framework focusing on four areas: innovation elicitation, selection, impact and ways-of-working. For each area, candidate measurements were derived from interviews to be used as inspiration in the development of a tailored measurement program. The framework is based on interviews with participants of a software team with specific innovation responsibilities and validated through cross-case analysis and feedback from practitioners.
NASA Astrophysics Data System (ADS)
Musil, Juergen; Schweda, Angelika; Winkler, Dietmar; Biffl, Stefan
Based on our observations of Austrian video game software development (VGSD) practices we identified a lack of systematic processes/method support and inefficient collaboration between various involved disciplines, i.e. engineers and artists. VGSD includes heterogeneous disciplines, e.g. creative arts, game/content design, and software. Nevertheless, improving team collaboration and process support is an ongoing challenge to enable a comprehensive view on game development projects. Lessons learned from software engineering practices can help game developers to increase game development processes within a heterogeneous environment. Based on a state of the practice survey in the Austrian games industry, this paper presents (a) first results with focus on process/method support and (b) suggests a candidate flexible process approach based on Scrum to improve VGSD and team collaboration. Results showed (a) a trend to highly flexible software processes involving various disciplines and (b) identified the suggested flexible process approach as feasible and useful for project application.
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
Table-Top Robotics for Engineering Design
ERIC Educational Resources Information Center
Wilczynski, Vincent; Dixon, Gregg; Ford, Eric
2005-01-01
The Mechanical Engineering Section at the U.S. Coast Guard Academy has developed a comprehensive activity based course to introduce second year students to mechanical engineering design. The culminating design activity for the course requires students to design, construct and test robotic devices that complete engineering challenges. Teams of…
Enabling performance skills: Assessment in engineering education
NASA Astrophysics Data System (ADS)
Ferrone, Jenny Kristina
Current reform in engineering education is part of a national trend emphasizing student learning as well as accountability in instruction. Assessing student performance to demonstrate accountability has become a necessity in academia. In newly adopted criterion proposed by the Accreditation Board for Engineering and Technology (ABET), undergraduates are expected to demonstrate proficiency in outcomes considered essential for graduating engineers. The case study was designed as a formative evaluation of freshman engineering students to assess the perceived effectiveness of performance skills in a design laboratory environment. The mixed methodology used both quantitative and qualitative approaches to assess students' performance skills and congruency among the respondents, based on individual, team, and faculty perceptions of team effectiveness in three ABET areas: Communications Skills. Design Skills, and Teamwork. The findings of the research were used to address future use of the assessment tool and process. The results of the study found statistically significant differences in perceptions of Teamwork Skills (p < .05). When groups composed of students and professors were compared, professors were less likely to perceive student's teaming skills as effective. The study indicated the need to: (1) improve non-technical performance skills, such as teamwork, among freshman engineering students; (2) incorporate feedback into the learning process; (3) strengthen the assessment process with a follow-up plan that specifically targets performance skill deficiencies, and (4) integrate the assessment instrument and practice with ongoing curriculum development. The findings generated by this study provides engineering departments engaged in assessment activity, opportunity to reflect, refine, and develop their programs as it continues. It also extends research on ABET competencies of engineering students in an under-investigated topic of factors correlated with team processes, behavior, and student learning.
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.
Achieving Agility and Stability in Large-Scale Software Development
2013-01-16
temporary team is assigned to prepare layers and frameworks for future feature teams. Presentation Layer Domain Layer Data Access Layer Framework...http://www.sei.cmu.edu/training/ elearning ~ Software Engineering Institute CarnegieMellon
An Engineering Research Program for High School Science Teachers: Year Two Changes and Results
ERIC Educational Resources Information Center
DeJong, Brian P.; Yelamarthi, Kumar; Kaya, Tolga
2016-01-01
The research experiences for teachers program at Central Michigan University was initiated to team in-service and pre-service teachers with undergraduate engineering students and engineering faculty, in an engineering research setting. During the six-week program, teachers learn engineering concepts and develop high-school instructional material…
Orion GN and C Model Based Development: Experience and Lessons Learned
NASA Technical Reports Server (NTRS)
Jackson, Mark C.; Henry, Joel R.
2012-01-01
The Orion Guidance Navigation and Control (GN&C) team is charged with developing GN&C algorithms for the Exploration Flight Test One (EFT-1) vehicle. The GN&C team is a joint team consisting primarily of Prime Contractor (Lockheed Martin) and NASA personnel and contractors. Early in the GN&C development cycle the team selected MATLAB/Simulink as the tool for developing GN&C algorithms and Mathworks autocode tools as the means for converting GN&C algorithms to flight software (FSW). This paper provides an assessment of the successes and problems encountered by the GN&C team from the perspective of Orion GN&C developers, integrators, FSW engineers and management. The Orion GN&C approach to graphical development, including simulation tools, standards development and autocode approaches are scored for the main activities that the team has completed through the development phases of the program.
ERIC Educational Resources Information Center
Fiore, Stephen M.; Rodriguez, Walter E.; Carstens, Deborah S.
2012-01-01
This paper presents a framework for facilitating communication among STEM project teams that are geographically dispersed in synchronous or asynchronous online courses. The framework has been developed to: (a) improve how engineering and technology students and faculty work with collocated and geographically-dispersed teams; and (b) to connect the…
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.
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.
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.
Biomedical engineering education through global engineering teams.
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.
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.
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.;
2017-01-01
There have been significant recent efforts in addressing mitigation approaches to neutralize Potentially Hazardous Asteroids (PHA). One such research effort was performed in 2015 by an integrated, inter-disciplinary team of asteroid scientists, energy deposition modeling scientists, payload engineers, orbital dynamist engineers, spacecraft discipline engineers, and systems architecture engineer from NASAs Goddard Space Flight Center (GSFC) and the Department of Energy (DoE) National Nuclear Security Administration (NNSA) laboratories (Los Alamos National Laboratory (LANL), Lawrence Livermore National Laboratories (LLNL) and Sandia National Laboratories). The study team collaborated with GSFCs Integrated Design Centers Mission Design Lab (MDL) which engaged a team of GSFC flight hardware discipline engineers to work with GSFC, LANL, and LLNL NEA-related subject matter experts during a one-week intensive concept formulation study in an integrated concurrent engineering environment. This team has analyzed the first of several distinct study cases for a multi-year NASA research grant. This Case 1 study references the Near-Earth Asteroid (NEA) named Bennu as the notional target due to the availability of a very detailed Design Reference Asteroid (DRA) model for its orbit and physical characteristics (courtesy of the Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) mission team). The research involved the formulation and optimization of spacecraft trajectories to intercept Bennu, overall mission and architecture concepts, and high-fidelity modeling of both kinetic impact (spacecraft collision to change a NEAs momentum and orbit) and nuclear detonation effects on Bennu, for purposes of deflecting Bennu.
Teaching introductory game development with unreal engine: Challenges, strategies, and experiences
NASA Astrophysics Data System (ADS)
Head, Nicholas A.
From the days of Pong to 100 million dollar projects such as the Grand Theft Auto franchise, video games have evolved significantly over the years. This evolution has also changed the way game development is viewed as a career. Today, video games are one of the most profitable forms of entertainment, and game development courses are appearing at universities around the world. Even with this growth, a degree from a university has yet to be an important factor in finding a job in game development (Owen, 2013). This thesis examines a method of creating and implementing an introductory gaming course and recommends ways to improve the curriculum. The main focus of the course was to introduce game development to the students. Each week, they were given an exercise that covered a different topic. Students also took part in a team project in which they were tasked with creating a complete game. The goal of the team projects was to expand the student's basic knowledge given to them from the exercises. Data was gathered on the students' subjective experiences with the class. This data and the class's overall performance were compared with past iterations of the course. New to the course was the Unreal Engine. Students used the latest version of the engine, Unreal Engine 4, to complete exercises. Not all students chose to use this engine for the team project. Instructor and students experiences with the engine were also recorded. While there were some problems implementing the engine within our lab environment, we were still able to execute the overall lesson plan. Even with the engine issues, the course had overall good performance. CGT 241, Introduction to 3D Animation, was shown to help the students to complete the course while CGT 215, Computer Graphics Programming I, did not provide enough information on game programming. Exercises were found to be helpful but students wanted a better understanding of how these skills can be applied to game development. Team projects also went well with most teams creating a functional project. Students wanted more time to complete projects along with a structured approach to the project. Confidence in game development and the Unreal Engine were not high but students were enthusiastic in continuing in the field of game development. Recommendations were made to the curriculum in order to fix some of the issues with the introductory course and help students find a career. In order to fix the gap between the programming course and the introductory game course, a video game programming course was recommended that focused on teaching students how code works with video game engines. An option to specialize was also recommended in order to see a higher level of understanding on game concepts and a higher level of quality of game projects. Changes to the higher courses were also made for a yearlong course where students would focus on a single project to publish. This would expand on the introductory course while also replicating the game development process.
ERIC Educational Resources Information Center
McFadden, Justin R.; Roehrig, Gillian H.
2017-01-01
Background: This study presents two teacher design teams (TDTs) during a professional development experience centered on science, technology, engineering, and mathematics (STEM)-integrated curriculum development. The main activity of the study, curriculum design, was framed as a design problem in order to better understand how teachers engaged…
Linking engineering and medicine: fostering collaboration skills in interdisciplinary teams.
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.
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
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.
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.
NASA Technical Reports Server (NTRS)
Phfarr, Barbara B.; So, Maria M.; Lamb, Caroline Twomey; Rhodes, Donna H.
2009-01-01
Experienced systems engineers are adept at more than implementing systems engineering processes: they utilize systems thinking to solve complex engineering problems. Within the space industry demographics and economic pressures are reducing the number of experienced systems engineers that will be available in the future. Collaborative systems thinking within systems engineering teams is proposed as a way to integrate systems engineers of various experience levels to handle complex systems engineering challenges. This paper uses the GOES-R Program Systems Engineering team to illustrate the enablers and barriers to team level systems thinking and to identify ways in which performance could be improved. Ways NASA could expand its engineering training to promote team-level systems thinking are proposed.
NASA Astrophysics Data System (ADS)
Mitchell, K. L.; Lowes, L. L.; Budney, C. J.; Sohus, A.
2014-12-01
NASA's Planetary Science Summer School (PSSS) is an intensive program for postdocs and advanced graduate students in science and engineering fields with a keen interest in planetary exploration. The goal is to train the next generation of planetary science mission leaders in a hands-on environment involving a wide range of engineers and scientists. It was established in 1989, and has undergone several incarnations. Initially a series of seminars, it became a more formal mission design experience in 1999. Admission is competitive, with participants given financial support. The competitively selected trainees develop an early mission concept study in teams of 15-17, responsive to a typical NASA Science Mission Directorate Announcement of Opportunity. They select the mission concept from options presented by the course sponsors, based on high-priority missions as defined by the Decadal Survey, prepare a presentation for a proposal authorization review, present it to a senior review board and receive critical feedback. Each participant assumes multiple roles, on science, instrument and project teams. They develop an understanding of top-level science requirements and instrument priorities in advance through a series of reading assignments and webinars help trainees. Then, during the five day session at Jet Propulsion Laboratory, they work closely with concurrent engineers including JPL's Advanced Projects Design Team ("Team X"), a cross-functional multidisciplinary team of engineers that utilizes concurrent engineering methodologies to complete rapid design, analysis and evaluation of mission concept designs. All are mentored and assisted directly by Team X members and course tutors in their assigned project roles. There is a strong emphasis on making difficult trades, simulating a real mission design process as accurately as possible. The process is intense and at times dramatic, with fast-paced design sessions and late evening study sessions. A survey of PSSS alumni administered in 2013 provides information on the program's impact on trainees' career choices and leadership roles as they pursue their employment in planetary science and related fields. Results will be presented during the session, along with highlights of topics and missions covered since the program's inception.
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
NASA Technical Reports Server (NTRS)
Hirshorn, Steven R.
2017-01-01
Historically, most successful NASA projects have depended on effectively blending project management, systems engineering, and technical expertise among NASA, contractors, and third parties. Underlying these successes are a variety of agreements (e.g., contract, memorandum of understanding, grant, cooperative agreement) between NASA organizations or between NASA and other Government agencies, Government organizations, companies, universities, research laboratories, and so on. To simplify the discussions, the term "contract" is used to encompass these agreements. This section focuses on the NASA systems engineering activities pertinent to awarding a contract, managing contract performance, and completing a contract. In particular, NASA systems engineering interfaces to the procurement process are covered, since the NASA engineering technical team plays a key role in the development and evaluation of contract documentation. Contractors and third parties perform activities that supplement (or substitute for) the NASA project technical team accomplishment of the NASA common systems engineering technical process activities and requirements outlined in this guide. Since contractors might be involved in any part of the systems engineering life cycle, the NASA project technical team needs to know how to prepare for, allocate or perform, and implement surveillance of technical activities that are allocated to contractors.
Designing primary health care teams for developing countries.
Reisman, A; Duran, L
1983-01-01
A time-honored industrial engineering technique, job evaluation, which was developed to set rates for manual labor, was used in the design of new teams for delivering primary health care in Latin America. The technique was used both in writing job descriptions for new allied health personnel and in designing the curriculums needed to train the personnel. PMID:6856744
ERIC Educational Resources Information Center
Lent, Robert W.; Schmidt, Janet; Schmidt, Linda
2006-01-01
A measure of collective efficacy was developed and administered to undergraduates working in project teams in engineering courses. Findings in each of two samples revealed that the measure contained a single factor and was related to ratings of team cohesion and personal efficacy. Collective efficacy was also found to relate to indicators of team…
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.
The Effects of Development Team Skill on Software Product Quality
NASA Technical Reports Server (NTRS)
Beaver, Justin M.; Schiavone, Guy A.
2006-01-01
This paper provides an analysis of the effect of the skill/experience of the software development team on the quality of the final software product. A method for the assessment of software development team skill and experience is proposed, and was derived from a workforce management tool currently in use by the National Aeronautics and Space Administration. Using data from 26 smallscale software development projects, the team skill measures are correlated to 5 software product quality metrics from the ISO/IEC 9126 Software Engineering Product Quality standard. in the analysis of the results, development team skill is found to be a significant factor in the adequacy of the design and implementation. In addition, the results imply that inexperienced software developers are tasked with responsibilities ill-suited to their skill level, and thus have a significant adverse effect on the quality of the software product. Keywords: software quality, development skill, software metrics
An automated environment for multiple spacecraft engineering subsystem mission operations
NASA Technical Reports Server (NTRS)
Bahrami, K. A.; Hioe, K.; Lai, J.; Imlay, E.; Schwuttke, U.; Hsu, E.; Mikes, S.
1990-01-01
Flight operations at the Jet Propulsion Laboratory (JPL) are now performed by teams of specialists, each team dedicated to a particular spacecraft. Certain members of each team are responsible for monitoring the performances of their respective spacecraft subsystems. Ground operations, which are very complex, are manual, labor-intensive, slow, and tedious, and therefore costly and inefficient. The challenge of the new decade is to operate a large number of spacecraft simultaneously while sharing limited human and computer resources, without compromising overall reliability. The Engineering Analysis Subsystem Environment (EASE) is an architecture that enables fewer controllers to monitor and control spacecraft engineering subsystems. A prototype of EASE has been installed in the JPL Space Flight Operations Facility for on-line testing. This article describes the underlying concept, development, testing, and benefits of the EASE prototype.
DOE Office of Scientific and Technical Information (OSTI.GOV)
McCullough, M. C.; Ebeling-Koning, D.; Evans, M. C.
2012-07-01
The lessons learned during the early phase of design engineering and construction activities for the AP1000 China Project can be applied to any project involving multiple disciplines and multiple organizations. Implementation of a first-of-a-kind design to directly support construction activities utilizing resources assigned to design development and design delivery creates challenges with prioritization of activities, successful closure of issues, and communication between site organizations and the home office. To ensure successful implementation, teams were assigned and developed to directly support construction activities including prioritization of activities, site communication and ensuring closure of site emergent issues. By developing these teams, themore » organization is better suited to meet the demands of the construction schedule while continuing with design evolution of a standard plant and engineering delivery for multiple projects. For a successful project, proper resource utilization and prioritization are key for overcoming obstacles and ensuring success of the engineering organization. (authors)« less
Vermeulen, Joan; Verwey, Renée; Hochstenbach, Laura M J; van der Weegen, Sanne; Man, Yan Ping; de Witte, Luc P
2014-05-19
User-centered design (UCD) methodologies can help take the needs and requirements of potential end-users into account during the development of innovative telecare products and services. Understanding how members of multidisciplinary development teams experience the UCD process might help to gain insight into factors that members with different backgrounds consider critical during the development of telecare products and services. The primary objective of this study was to explore how members of multidisciplinary development teams experienced the UCD process of telecare products and services. The secondary objective was to identify differences and similarities in the barriers and facilitators they experienced. Twenty-five members of multidisciplinary development teams of four Research and Development (R&D) projects participated in this study. The R&D projects aimed to develop telecare products and services that can support self-management in elderly people or patients with chronic conditions. Seven participants were representatives of end-users (elderly persons or patients with chronic conditions), three were professional end-users (geriatrician and nurses), five were engineers, four were managers (of R&D companies or engineering teams), and six were researchers. All participants were interviewed by a researcher who was not part of their own development team. The following topics were discussed during the interviews: (1) aim of the project, (2) role of the participant, (3) experiences during the development process, (4) points of improvement, and (5) what the project meant to the participant. Experiences of participants related to the following themes: (1) creating a development team, (2) expectations regarding responsibilities and roles, (3) translating user requirements into technical requirements, (4) technical challenges, (5) evaluation of developed products and services, and (6) valorization. Multidisciplinary team members from different backgrounds often reported similar experienced barriers (eg, different members of the development team speak a "different language") and facilitators (eg, team members should voice expectations at the start of the project to prevent miscommunication at a later stage). However, some experienced barriers and facilitators were reported only by certain groups of participants. For example, only managers reported the experience that having different ideas about what a good business case is within one development team was a barrier, whereas only end-users emphasized the facilitating role of project management in end-user participation and the importance of continuous feedback from researchers on input of end-users. Many similarities seem to exist between the experienced barriers and facilitators of members of multidisciplinary development teams during UCD of telecare products and services. However, differences in experiences between team members from various backgrounds exist as well. Insights into these similarities and differences can improve understanding between team members from different backgrounds, which can optimize collaboration during the development of telecare products and services.
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.
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.
ERIC Educational Resources Information Center
Shelby, Kenneth R., Jr.
2013-01-01
Systems engineering teams' value-creation for enterprises is slower than possible due to inefficiencies in communication, learning, common knowledge collaboration and leadership conduct. This dissertation outlines the surrounding people, process and technology dimensions for higher performing engineering teams. It describes a true experiment…
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…
NASA Technical Reports Server (NTRS)
Hihn, Jairus; Chattopadhyay, Debarati; Karpati, Gabriel; McGuire, Melissa; Panek, John; Warfield, Keith; Borden, Chester
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 of performance, cost and schedule. To successfully accomplish these complex missions with limited funding, it is 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. The purpose of this white paper is to identify a near-term vision for the future of distributed collaborative concurrent engineering design for aerospace missions as well as discuss the challenges to achieving that vision. The white paper also documents the advantages of creating a working group to investigate how to engage the expertise of different teams in joint design sessions while enabling organizations to maintain their organizations competitive advantage.
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.
and high school student teams on science and math topics. The National Science Bowl provides an opportunity for students to develop science, technology, engineering, and math (STEM) skills in a non tournament challenges students' knowledge of science. Student teams are questioned on life science, math
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.
Generic Skill Development and Learning/Assessment Process: Use of Rubrics and Student Validation
ERIC Educational Resources Information Center
Iborra Urios, Montserrat; Ramirez Rangel, Eliana; Bringué Tomàs, Roger; Tejero Salvador, Javier; Cunill García, Fidel; Fité Piquer, Carles
2015-01-01
To fulfill the European Higher Education context in the subject of the Chemical Engineering Undergraduate Degree of University of Barcelona named "Chemical Engineering Experimentation II" team work, written and oral communication generic skills were developed and assessed by means of rubrics. In order to appraise the methodological…
ERIC Educational Resources Information Center
Chen, Chung-Yang; Hong, Ya-Chun; Chen, Pei-Chi
2014-01-01
Software development relies heavily on teamwork; determining how to streamline this collaborative development is an essential training subject in computer and software engineering education. A team process known as the meetings-flow (MF) approach has recently been introduced in software capstone projects in engineering programs at various…
Fitting the Framework: The STEM Institute and the 4-H Essential Elements
ERIC Educational Resources Information Center
Sallee, Jeff; Peek, Gina G.
2014-01-01
Extension and 4-H youth development programs are addressing a shortage of scientists, engineers, and other related professionals by promoting science, technology, engineering, and math (STEM). This case study illustrates how the Oklahoma 4-H Youth Development program trained youth-adult teams to design and implement STEM projects. The STEM…
ERIC Educational Resources Information Center
Foster, W. Tad; Shahhosseini, A. Mehran; Maughan, George
2016-01-01
Facilitating student growth and development in diagnosing and solving technical problems remains a challenge for technology and engineering educators. With funding from the National Science Foundation, this team of researchers developed a self-guided, computer-based instructional program to experiment with conceptual mapping as a treatment to…
2011-08-01
Thomas Meitzler (Team Leader, Research Engineer), Dr. Elena Bankowski (Research Engineer) & Mr. Steven Zielinski (Engineer). •Oakland University...our experiments. •We would like to thank TARDEC Director Dr. Grace Bochenek, the Chief Scientist Dr. Dave Gorsich and GVSS Associate Director Mr. Steve
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 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.
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.
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.
A systems engineering initiative for NASA's space communications
NASA Technical Reports Server (NTRS)
Hornstein, Rhoda S.; Hei, Donald J., Jr.; Kelly, Angelita C.; Lightfoot, Patricia C.; Bell, Holland T.; Cureton-Snead, Izeller E.; Hurd, William J.; Scales, Charles H.
1993-01-01
In addition to but separate from the Red and Blue Teams commissioned by the NASA Administrator, 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, without compromising safety. 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. The Blue Team process and results are summarized. The Associate Administrator for Space Communications subsequently convened a special management session to discuss the significance and implications of the Blue Team's report and to lay the groundwork and teamwork for the next steps, including the transition from engineering systems to systems engineering. The methodology and progress toward realizing the Code O Family vision and accomplishing the systems engineering initiative for NASA's space communications are presented.
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.
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.
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...
Training to Enhance Design Team Performance: A Cure for Tunnel Vision
NASA Technical Reports Server (NTRS)
Parker, James W.; Parker, Nelson C. (Technical Monitor)
2001-01-01
Design Team performance is a function of the quality and degree of academic training and the cumulative, learned experience of the individual members of the team. Teamwork, leadership, and communications certainly are factors that affect the measure of the performance of the team, but they are not addressed here. This paper focuses on accelerating the learned experience of team members and describes an organizational approach that can significantly increase the effective experience level for any engineering design team. The performance measure of the whole team can be increased by increasing the engineering disciplines' cross awareness of each other and by familiarizing them with their affect at the system level. Discipline engineers know their own discipline well, but typically are not intimately familiar with their technical interaction with and dependencies on all the other disciplines of engineering. These dependencies are design integration functions and are worked out well by the discipline engineers as long as they are involved in the design of types of systems that they have experience with.
Climbing the Extravehicular Activity (EVA) Wall - Safely
NASA Technical Reports Server (NTRS)
Fuentes, Jose; Greene, Stacie
2010-01-01
The success of the EVA team, that includes the EVA project office, Crew Office, Mission Operations, Engineering and Safety, is assured by the full integration of all necessary disciplines. Safety participation in all activities from hardware development concepts, certification and crew training, provides for a strong partnership within the team. Early involvement of Safety on the EVA team has mitigated risk and produced a high degree of mission success.
Student Participation in Rover Field Trials
NASA Astrophysics Data System (ADS)
Bowman, C. D.; Arvidson, R. E.; Nelson, S. V.; Sherman, D. M.; Squyres, S. W.
2001-12-01
The LAPIS program was developed in 1999 as part of the Athena Science Payload education and public outreach, funded by the JPL Mars Program Office. For the past three years, the Athena Science Team has been preparing for 2003 Mars Exploration Rover Mission operations using the JPL prototype Field Integrated Design and Operations (FIDO) rover in extended rover field trials. Students and teachers participating in LAPIS work with them each year to develop a complementary mission plan and implement an actual portion of the annual tests using FIDO and its instruments. LAPIS is designed to mirror an end-to-end mission: Small, geographically distributed groups of students form an integrated mission team, working together with Athena Science Team members and FIDO engineers to plan, implement, and archive a two-day test mission, controlling FIDO remotely over the Internet using the Web Interface for Telescience (WITS) and communicating with each other by email, the web, and teleconferences. The overarching goal of LAPIS is to get students excited about science and related fields. The program provides students with the opportunity to apply knowledge learned in school, such as geometry and geology, to a "real world" situation and to explore careers in science and engineering through continuous one-on-one interactions with teachers, Athena Science Team mentors, and FIDO engineers. A secondary goal is to help students develop improved communication skills and appreciation of teamwork, enhanced problem-solving skills, and increased self-confidence. The LAPIS program will provide a model for outreach associated with future FIDO field trials and the 2003 Mars mission operations. The base of participation will be broadened beyond the original four sites by taking advantage of the wide geographic distribution of Athena team member locations. This will provide greater numbers of students with the opportunity to actively engage in rover testing and to explore the possibilities of science, engineering, and technology.
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.
How Engineers Really Think About Risk: A Study of JPL Engineers
NASA Technical Reports Server (NTRS)
Hihn, Jairus; Chattopadhyay, Deb; Valerdi, Ricardo
2011-01-01
The objectives of this work are: To improve risk assessment practices as used during the mission design process by JPL's concurrent engineering teams. (1) Developing effective ways to identify and assess mission risks (2) Providing a process for more effective dialog between stakeholders about the existence and severity of mission risks (3) Enabling the analysis of interactions of risks across concurrent engineering roles.
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.
Development of a Pedagogical Model to Help Engineering Faculty Design Interdisciplinary Curricula
ERIC Educational Resources Information Center
Navarro, Maria; Foutz, Timothy; Thompson, Sidney; Singer, Kerri Patrick
2016-01-01
The purpose of this study was to develop a model to help engineering faculty overcome the challenges they face when asked to design and implement interdisciplinary curricula. Researchers at a U.S. University worked with an Interdisciplinary Consultant Team and prepared a steering document with Guiding Principles and Essential Elements for the…
Social Work and Engineering Collaboration: Forging Innovative Global Community Development Education
ERIC Educational Resources Information Center
Gilbert, Dorie J.
2014-01-01
Interdisciplinary programs in schools of social work are growing in scope and number. This article reports on collaboration between a school of social work and a school of engineering, which is forging a new area of interdisciplinary education. The program engages social work students working alongside engineering students in a team approach to…
NASA Astrophysics Data System (ADS)
Aleksandrov, Y. B.; Mingazov, B. G.
2017-09-01
The paper shows a method of modeling and optimization of processes in combustion chambers of gas turbine engines using a computer program developed by a team at the Department of Jet Engines and Power Plants (DJEPP) of Technical University named after A N Tupolev KNRTU-KAI.
2014-01-01
Background User-centered design (UCD) methodologies can help take the needs and requirements of potential end-users into account during the development of innovative telecare products and services. Understanding how members of multidisciplinary development teams experience the UCD process might help to gain insight into factors that members with different backgrounds consider critical during the development of telecare products and services. Objective The primary objective of this study was to explore how members of multidisciplinary development teams experienced the UCD process of telecare products and services. The secondary objective was to identify differences and similarities in the barriers and facilitators they experienced. Methods Twenty-five members of multidisciplinary development teams of four Research and Development (R&D) projects participated in this study. The R&D projects aimed to develop telecare products and services that can support self-management in elderly people or patients with chronic conditions. Seven participants were representatives of end-users (elderly persons or patients with chronic conditions), three were professional end-users (geriatrician and nurses), five were engineers, four were managers (of R&D companies or engineering teams), and six were researchers. All participants were interviewed by a researcher who was not part of their own development team. The following topics were discussed during the interviews: (1) aim of the project, (2) role of the participant, (3) experiences during the development process, (4) points of improvement, and (5) what the project meant to the participant. Results Experiences of participants related to the following themes: (1) creating a development team, (2) expectations regarding responsibilities and roles, (3) translating user requirements into technical requirements, (4) technical challenges, (5) evaluation of developed products and services, and (6) valorization. Multidisciplinary team members from different backgrounds often reported similar experienced barriers (eg, different members of the development team speak a “different language”) and facilitators (eg, team members should voice expectations at the start of the project to prevent miscommunication at a later stage). However, some experienced barriers and facilitators were reported only by certain groups of participants. For example, only managers reported the experience that having different ideas about what a good business case is within one development team was a barrier, whereas only end-users emphasized the facilitating role of project management in end-user participation and the importance of continuous feedback from researchers on input of end-users. Conclusions Many similarities seem to exist between the experienced barriers and facilitators of members of multidisciplinary development teams during UCD of telecare products and services. However, differences in experiences between team members from various backgrounds exist as well. Insights into these similarities and differences can improve understanding between team members from different backgrounds, which can optimize collaboration during the development of telecare products and services. PMID:24840245
Quigley, Dianne
2015-02-01
A collaborative team of environmental sociologists, community psychologists, religious studies scholars, environmental studies/science researchers and engineers has been working together to design and implement new training in research ethics, culture and community-based approaches for place-based communities and cultural groups. The training is designed for short and semester-long graduate courses at several universities in the northeastern US. The team received a 3 year grant from the US National Science Foundation's Ethics Education in Science and Engineering in 2010. This manuscript details the curriculum topics developed that incorporate ethical principles, particularly for group protections/benefits within the field practices of environmental/engineering researchers.
NASA Astrophysics Data System (ADS)
Hodges, Jeanelle Bland
1999-11-01
The purpose of the study was to determine factors associated with staff development processes and the creation of innovative science courses by higher education faculty who have participated in a model staff development project. The staff development program was designed for college faculty interested in creating interdisciplinary, constructivist-based science, mathematics, or engineering courses designed for non-majors. The program includes workshops on incorporating constructivist pedagogy, alternative assessment, and technology into interdisciplinary courses. Staff development interventions used in the program include grant opportunities, distribution of resource materials, and peer mentoring. University teams attending the workshops are comprised of faculty from the sciences, mathematics, or engineering, as well as education, and administration. A purposeful and convenient sample of three university teams were subjects for this qualitative study. Each team had attended a NASA Opportunities for Visionary Academics (NOVA) workshop, received funding for course development, and offered innovative courses. Five questions were addressed in this study: (a) What methods were used by faculty teams in planning the courses? (b) What changes occurred in existing science courses? (c) What factors affected the team collaboration process? (d) What personal characteristics of faculty members were important in successful course development? and (e) What barriers existed for faculty in the course development process? Data was collected at each site through individual faculty interviews (N = 11), student focus group interviews (N = 15), and classroom observations. Secondary data included original funding proposals. The NOVA staff development model incorporated effective K--12 interventions with higher education interventions. Analysis of data revealed that there were four factors of staff development processes that were most beneficial. First, the team collaborative processes were crucial in successful course development. Second, the use of instructional grants to fund course development gave credibility to the faculty involved in course development. Third, the faculty members taking the lead in creating teams actively sought out faculty members in the sciences who had previous experience teaching at the K--12 level or in informal education. In addition, college environments were found to have an impact on the success of the innovative course development projects.
MC-1 Engine Valves, Lessons Learned
NASA Technical Reports Server (NTRS)
Laszar, John
2003-01-01
Many lessons were learned during the development of the valves for the MC-1 engine. The purpose of this report is to focus on a variety of issues related to the engine valves and convey the lessons learned. This paper will not delve into detailed technical analysis of the components. None of the lessons learned are new or surprising, but simply reinforce the importance of addressing the details of the design early, at the component level. The Marshall Space Flight Center (MSFC), Huntsville, Alabama developed the MC-1 engine, a LOX / FW-1, 60,000 pound thrust engine. This engine was developed under the Low Cost Boost Technology office at MSFC and proved to be a very successful project for the MSFC Propulsion team and the various subcontractors working the development of the engine and its components.
Using Collaborative Engineering to Inform Collaboration Engineering
NASA Technical Reports Server (NTRS)
Cooper, Lynne P.
2012-01-01
Collaboration is a critical competency for modern organizations as they struggle to compete in an increasingly complex, global environment. A large body of research on collaboration in the workplace focuses both on teams, investigating how groups use teamwork to perform their task work, and on the use of information systems to support team processes ("collaboration engineering"). This research essay presents collaboration from an engineering perspective ("collaborative engineering"). It uses examples from professional and student engineering teams to illustrate key differences in collaborative versus collaboration engineering and investigates how challenges in the former can inform opportunities for the latter.
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.
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.
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
Reflections on an Interdisciplinary, Community-Based, Team-Taught Adventure
ERIC Educational Resources Information Center
Fauvel, Anne Marie; Miller, Lisa K.; Lane, Paul; Farris, John
2010-01-01
A new team-taught course focused on interdisciplinary teaching and integrative learning was offered at Grand Valley State University during the Summer of 2008 at a regional campus in Holland, Michigan. Faculty from Engineering and Business developed this community-based, alternative-format course to engage students in the question: "What will…
developer. He is a member of the OpenStudio development team, where he focuses on creating new simulation expertise in fluid mechanics and numerical simulation. Education M.S. Mechanical Engineering, Missouri
DOE Office of Scientific and Technical Information (OSTI.GOV)
Adams, B.E.
1995-04-01
A cross-functional team of process, product, quality, material, and design lab engineers was assembled to develop an environmentally friendly cleaning process for leadless chip carrier assemblies (LCCAs). Using flush and filter testing, Auger surface analysis, GC-Mass spectrophotometry, production yield results, and electrical testing results over an extended testing period, the team developed an aqueous cleaning process for LCCAs. The aqueous process replaced the Freon vapor degreasing/ultrasonic rinse process.
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;
2009-01-01
The Low Cost Rapid Response Spacecraft (LCRRS) is an ongoing research development project at NASA Ames Research Center (ARC), Moffett Field, California. The prototype spacecraft, called Cost Optimized Test for Spacecraft Avionics and Technologies (COTSAT) is the first of what could potentially be a series of rapidly produced low-cost satellites. COTSAT has a target launch date of March 2009 on a SpaceX Falcon 9 launch vehicle. The LCRRS research system design incorporates use of COTS (Commercial Off The Shelf), MOTS (Modified Off The Shelf), and GOTS (Government Off The Shelf) hardware for a remote sensing satellite. The design concept was baselined to support a 0.5 meter Ritchey-Chretien telescope payload. This telescope and camera system is expected to achieve 1.5 meter/pixel resolution. The COTSAT team is investigating the possibility of building a fully functional spacecraft for $500,000 parts and $2,000,000 labor. Cost is dramatically reduced by using a sealed container, housing the bus and payload subsystems. Some electrical and RF designs were improved/upgraded from GeneSat-1 heritage systems. The project began in January 2007 and has yielded two functional test platforms. It is expected that a flight-qualified unit will be finished in December 2008. Flight quality controls are in place on the parts and materials used in this development with the aim of using them to finish a proto-flight satellite. For LEO missions the team is targeting a mission class requiring a minimum of six months lifetime or more. The system architecture incorporates several design features required by high reliability missions. This allows for a true skunk works environment to rapidly progress toward a flight design. Engineering and fabrication is primarily done in-house at NASA Ames with flight certifications on materials. The team currently employs seven Full Time Equivalent employees. The success of COTSATs small team in this effort can be attributed to highly cross trained engineering team. The engineers on the team are capable of functioning in two to three engineering disciplines which allows highly efficient interdisciplinary engineering collaboration. NASA Ames is actively proposing mission concepts to use the COTSAT platform to accomplish science. If the COTSAT team validates this approach, it will allow the possibility for remote sensing missions to produce a high science yield for minimal cost and reduced schedule. Another aim of this approach is to yield an accelerated pathway from a Phase A study to mission launch. Leaders in the aerospace industry have shown interest in this methodology. Several visits and tours have been given in the lab. Although the concept of low-cost development is initially met with skepticism from some within the prohibitive aerospace industry, the project's efforts have been highly praised for the accomplishments met within a limited time and budget. Overall the development has progressed tremendously well and the team is answering critical questions for current and future low-cost small satellite developments. COTSAT subsystems are not limited to a specific weight class and could be adapted to produce smaller platforms and to fit various launch vehicles.
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.
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
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.
NASA Astrophysics Data System (ADS)
Cutright, Teresa J.; Evans, Edward; Brantner, Justin S.
2014-06-01
A unique undergraduate team that spans five different engineering disciplines, chemistry, biology, and mathematics was formed. The team was formed to promote cross-disciplinary learning, to improve retention, and to prepare the students for the kind of problems they will face in their careers. This paper describes the variety of activities used over 2 years to tie the team together, as well as afford opportunities to develop team-building skills. The activities described highlight the critical elements of a faculty leader whose own work is interdisciplinary, correct balance of disciplines in the team, and sufficient time for team development. The use of external feedback was essential for all activities. Clearly defined goals and hard deadlines were critical for the completion of individual activities, as well as developing a healthy team environment. Although the student cohort has learned from the activities, more time is needed to assess whether the students have become a fully efficient team. Furthermore, an additional cohort would be needed to assess whether the approach was able to assist with student's interest in STEM and their desire to help other people.
Information Protection Engineering: Using Technology and Experience to Protect Assets
2001-07-01
SAIC’s highly experienced team has developed technology, techniques and expertise in protecting these information assets from electronic attack by...criminals, terrorists, hackers or nation states. INFORMATION PROTECTION ENGINEERING : Using Technology and Experience to Protect Assets William J. Marlow... Engineering : Using Technology and Experience to Protect Assets Contract or Grant Number Program Element Number Authors Marlow, William J. Project
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…
ERIC Educational Resources Information Center
Ejiwale, James A.
2014-01-01
Collaboration plays a major role in interdisciplinary activities among Science, Technology, Engineering & Mathematics (STEM) disciplines or fields. It also affects the relationships among cluster members on the management team. Although effective collaboration does not guarantee success among STEM disciplines, its absence usually assures…
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…
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
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
Walter Thiel—Short life of a rocket scientist
NASA Astrophysics Data System (ADS)
Thiel, Karen; Przybilski, Olaf
2013-10-01
In 2012 we celebrate the 70th anniversary of the first successful rocket launch that reached a height of 84.5 km and had a speed of 4.824 km/h (5x sonic speed). This rocket flew 190 km to the target location. One of the masterminds of this launch was Walter Thiel, a German chemist and rocket engineer. Thiel was highly talented, during his education from primary school until diploma exams he always received a grade of A in his exams. He was called "the student with the 7 A grades". In 1934 Thiel became Dr.-Ing. (chem.), with the highest possible honor (summa cum laude), when he was only 24 years old. He started to work for the rocket development department at Humboldt University, Berlin. Walter Dornberger asked him to leave the university research department and become head of rocket propulsion development in his team in Kummersdorf, near Berlin. Thiel's groundbreaking ideas for the rocket engine would lead to a significant reduction in material, weight and work processes, as well as a shortening in the length of the engine itself. Thiel and his team also defined the fuel itself and the best ratio of mixture between ethanol and liquid oxygen for the engine. In 1940 the propulsion team moved from Kummersdorf to Peenemünde after the launch sites were completed there. Thiel became deputy of Wernher von Braun at the R&D units. One of Thiel's team members was Konrad Dannenberg, who later became famous in the development of the Saturn program. On the night from August 17 to August 18, 1943, Thiel and his family (wife and two children) were killed during a Royal Air Force bombing raid (Operation Hydra). The Moon crater "Thiel" on the far side of the Moon is named after Walter Thiel. The research results of Walter Thiel had a strong impact on the United States' rocket program as well as the Russian rocket development program.
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.
The European Project Semester at ISEP: the challenge of educating global engineers
NASA Astrophysics Data System (ADS)
Malheiro, Benedita; Silva, Manuel; Ribeiro, Maria Cristina; Guedes, Pedro; Ferreira, Paulo
2015-05-01
Current engineering education challenges require approaches that promote scientific, technical, design and complementary skills while fostering autonomy, innovation and responsibility. The European Project Semester (EPS) at Instituto Superior de Engenharia do Porto (ISEP) (EPS@ISEP) is a one semester project-based learning programme (30 European Credit Transfer Units (ECTU)) for engineering students from diverse scientific backgrounds and nationalities that intends to address these goals. The students, organised in multidisciplinary and multicultural teams, are challenged to solve real multidisciplinary problems during one semester. The EPS package, although on project development (20 ECTU), includes a series of complementary seminars aimed at fostering soft, project-related and engineering transversal skills (10 ECTU). Hence, the students enrolled in this programme improve their transversal skills and learn, together and with the team of supervisors, subjects distinct from their core training. This paper presents the structure, implementation and results of the EPS@ISEP that was created in 2011 to apply the best engineering practices and promote internationalisation and engineering education innovation at ISEP.
Randy B. Foltz; Peter R. Robichaud; Hakjun Rhee
2008-01-01
We synthesized post-fire road treatment information to assist BAER specialists in making road rehabilitation decisions. We developed a questionnaire; conducted 30 interviews of BAER team engineers and hydrologists; acquired and analyzed gray literature and other relevant publications; and reviewed road rehabilitation procedures and analysis tools. Post-fire road...
ERIC Educational Resources Information Center
Hsiung, Chin-Min; Zheng, Xiang-Xiang
2015-01-01
The Measurements for Team Functioning (MTF) database contains a series of student academic performance measurements obtained at a national university in Taiwan. The measurements are acquired from unit tests and homework tests performed during a core mechanical engineering course, and provide an objective means of assessing the functioning of…
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.
WFF TOPEX Software Documentation Overview, May 1999. Volume 2
NASA Technical Reports Server (NTRS)
Brooks, Ronald L.; Lee, Jeffrey
2003-01-01
This document provides an overview'of software development activities and the resulting products and procedures developed by the TOPEX Software Development Team (SWDT) at Wallops Flight Facility, in support of the WFF TOPEX Engineering Assessment and Verification efforts.
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.
Rurality as an Asset for Inclusive Teaching in Chemical Engineering
ERIC Educational Resources Information Center
Gomez, Jamie; Svihla, Vanessa
2018-01-01
We developed and tested a pedagogical strategy--asset-based design challenges--to enhance diversity in early chemical engineering coursework. Using qualitative methods, we found first-year students justified high-cost solutions with ethical arguments; teams that included rural expertise argued instead for economically-viable solutions. In the…
Implementing Large Projects in Software Engineering Courses
ERIC Educational Resources Information Center
Coppit, David
2006-01-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…
Leading the Teacher Team--Balancing between Formal and Informal Power in Program Leadership
ERIC Educational Resources Information Center
Högfeldt, Anna-Karin; Malmi, Lauri; Kinnunen, Päivi; Jerbrant, Anna; Strömberg, Emma; Berglund, Anders; Villadsen, Jørgen
2018-01-01
This continuous research within Nordic engineering institutions targets the contexts and possibilities for leadership among engineering education program directors. The IFP-model, developed based on analysis of interviews with program leaders in these institutions, visualizes the program director's informal and formal power. The model is presented…
2011-08-09
Elena Bankowski (Research Engineer) & Mr. Steven Zielinski (Engineer). •Oakland University Research Team: Dr. Andrei Slavin (Chair, Physics...Dr. Grace Bochenek, the Chief Scientist Dr. Dave Gorsich and GVSS Associate Director Mr. Steve Knott for their support of this innovative research
FY-12 INL KR CAPTURE ACTIVITIES SUPPORTING THE OFF-GAS SIGMA TEAM
DOE Office of Scientific and Technical Information (OSTI.GOV)
Troy G. Garn; Mitchell R. Greenhalgh; Jack D Law
2012-08-01
Tasks performed this year by INL Kr capture off-gas team members can be segregated into three separate task sub-sections which include: 1) The development and testing of a new engineered form sorbent, 2) An initial NDA gamma scan effort performed on the drum containing the Legacy Kr-85 sample materials, and 3) Collaborative research efforts with PNNL involving the testing of the Ni-DOBDC MOF and an initial attempt to make powdered chalcogel material into an engineered form using our binding process. This document describes the routes to success for the three task sub-sections.
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…
Are the expected benefits of requirements reuse hampered by distance? An experiment.
Carrillo de Gea, Juan M; Nicolás, Joaquín; Fernández-Alemán, José L; Toval, Ambrosio; Idri, Ali
2016-01-01
Software development processes are often performed by distributed teams which may be separated by great distances. Global software development (GSD) has undergone a significant growth in recent years. The challenges concerning GSD are especially relevant to requirements engineering (RE). Stakeholders need to share a common ground, but there are many difficulties as regards the potentially variable interpretation of the requirements in different contexts. We posit that the application of requirements reuse techniques could alleviate this problem through the diminution of the number of requirements open to misinterpretation. This paper presents a reuse-based approach with which to address RE in GSD, with special emphasis on specification techniques, namely parameterised requirements and traceability relationships. An experiment was carried out with the participation of 29 university students enrolled on a Computer Science and Engineering course. Two main scenarios that represented co-localisation and distribution in software development were portrayed by participants from Spain and Morocco. The global teams achieved a slightly better performance than the co-located teams as regards effectiveness , which could be a result of the worse productivity of the global teams in comparison to the co-located teams. Subjective perceptions were generally more positive in the case of the distributed teams ( difficulty , speed and understanding ), with the exception of quality . A theoretical model has been proposed as an evaluation framework with which to analyse, from the point of view of the factor of distance, the effect of requirements specification techniques on a set of performance and perception-based variables. The experiment utilised a new internationalisation requirements catalogue. None of the differences found between co-located and distributed teams were significant according to the outcome of our statistical tests. The well-known benefits of requirements reuse in traditional co-located projects could, therefore, also be expected in GSD projects.
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".
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
Job Analysis Results for Malicious-Code Reverse Engineers: A Case Study
2014-05-01
Testing in Personnel Selection: Contemporary Issues in Cognitive Ability and Personality Testing .” Journal of Business Inquiry: Research , Edu- cation, and...federally funded research and development center. Any opinions, findings and conclusions or recommendations expressed in this material are those of...predict the develop- ment of expertise is important. Currently, job analysis research on teams of malicious-code re- verse engineers is lacking. Therefore
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.
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…
Technology transfer: Transportation
NASA Technical Reports Server (NTRS)
Anyos, T.; Lizak, R.; Merrifield, D.
1973-01-01
Standard Research Institute (SRI) has operated a NASA-sponsored team for four years. The SRI Team is concentrating on solving problems in the public transportation area and on developing methods for decreasing the time gap between the development and the marketing of new technology and for aiding the movement of knowledge across industrial, disciplinary, and regional boundaries. The SRI TAT has developed a methodology that includes adaptive engineering of the aerospace technology and commercialization when a market is indicated. The SRI Team has handled highway problems on a regional rather than a state basis, because many states in similar climatic or geologic regions have similar problems. Program exposure has been increased to encompass almost all of the fifty states.
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.
NASA Technical Reports Server (NTRS)
Lenz, Robert W.
1995-01-01
A fact-finding team of American scientists and engineers visited Japan to assess the status of research and development and applications in biodegradable polymers. The visit was sponsored by the National Science Foundation and industry. In Japan, the team met with representatives of 31 universities, government ministries and institutes, companies, and associations. Japan's national program on biodegradable polymers and plastics evaluates new technologies, testing methods, and potential markets for biodegradables. The program is coordinated by the Biodegradable Plastics Society of Japan, which seeks to achieve world leadership in biodegradable polymer technology and identify commercial opportunities for exploiting this technology. The team saw no major new technology breakthroughs. Japanese scientists and engineers are focusing on natural polymers from renewable resources, synthetic polymers, and bacterially-produced polymers such as polyhydroxyalkanoates, poly(amino acids), and polysaccharides. The major polymers receiving attention are the Zeneca PHBV copolymers, Biopol(registered trademark), poly(lactic acid) from several sources, polycaprolactone, and the new synthetic polyester, Bionolle(registered trademark), from Showa High Polymer. In their present state of development, these polymers all have major deficiencies that inhibit their acceptance for large-scale applications.
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.
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.
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,…
Software Development in the Water Sciences: a view from the divide (Invited)
NASA Astrophysics Data System (ADS)
Miles, B.; Band, L. E.
2013-12-01
While training in statistical methods is an important part of many earth scientists' training, these scientists often learn the bulk of their software development skills in an ad hoc, just-in-time manner. Yet to carry out contemporary research scientists are spending more and more time developing software. Here I present perspectives - as an earth sciences graduate student with professional software engineering experience - on the challenges scientists face adopting software engineering practices, with an emphasis on areas of the science software development lifecycle that could benefit most from improved engineering. This work builds on experience gained as part of the NSF-funded Water Science Software Institute (WSSI) conceptualization award (NSF Award # 1216817). Throughout 2013, the WSSI team held a series of software scoping and development sprints with the goals of: (1) adding features to better model green infrastructure within the Regional Hydro-Ecological Simulation System (RHESSys); and (2) infusing test-driven agile software development practices into the processes employed by the RHESSys team. The goal of efforts such as the WSSI is to ensure that investments by current and future scientists in software engineering training will enable transformative science by improving both scientific reproducibility and researcher productivity. Experience with the WSSI indicates: (1) the potential for achieving this goal; and (2) while scientists are willing to adopt some software engineering practices, transformative science will require continued collaboration between domain scientists and cyberinfrastructure experts for the foreseeable future.
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.
Structure and Management of an Engineering Senior Design Course.
Tanaka, Martin L; Fischer, Kenneth J
2016-07-01
The design of products and processes is an important area in engineering. Students in engineering schools learn fundamental principles in their courses but often lack an opportunity to apply these methods to real-world problems until their senior year. This article describes important elements that should be incorporated into a senior capstone design course. It includes a description of the general principles used in engineering design and a discussion of why students often have difficulty with application and revert to trial and error methods. The structure of a properly designed capstone course is dissected and its individual components are evaluated. Major components include assessing resources, identifying projects, establishing teams, understanding requirements, developing conceptual designs, creating detailed designs, building prototypes, testing performance, and final presentations. In addition to the course design, team management and effective mentoring are critical to success. This article includes suggested guidelines and tips for effective design team leadership, attention to detail, investment of time, and managing project scope. Furthermore, the importance of understanding business culture, displaying professionalism, and considerations of different types of senior projects is discussed. Through a well-designed course and proper mentoring, students will learn to apply their engineering skills and gain basic business knowledge that will prepare them for entry-level positions in industry.
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.
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.
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.
Teaching Note--An Exploration of Team-Based Learning and Social Work Education: A Natural Fit
ERIC Educational Resources Information Center
Robinson, Michael A.; Robinson, Michelle Bachelor; McCaskill, Gina M.
2013-01-01
The literature on team-based learning (TBL) as a pedagogical methodology in social work education is limited; however, TBL, which was developed as a model for business, has been successfully used as a teaching methodology in nursing, business, engineering, medical school, and many other disciplines in academia. This project examines the use of TBL…
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.
Integrating International Engineering Organizations For Successful ISS Operations
NASA Technical Reports Server (NTRS)
Blome, Elizabeth; Duggan, Matt; Patten, L.; Pieterek, Hhtrud
2006-01-01
The International Space Station (ISS) is a multinational orbiting space laboratory that is built in cooperation with 16 nations. The design and sustaining engineering expertise is spread worldwide. As the number of Partners with orbiting elements on the ISS grows, the challenge NASA is facing as the ISS integrator is to ensure that engineering expertise and data are accessible in a timely fashion to ensure ongoing operations and mission success. Integrating international engineering teams requires definition and agreement on common processes and responsibilities, joint training and the emergence of a unique engineering team culture. ISS engineers face daunting logistical and political challenges regarding data sharing requirements. To assure systematic information sharing and anomaly resolution of integrated anomalies, the ISS Partners are developing multi-lateral engineering interface procedures. Data sharing and individual responsibility are key aspects of this plan. This paper describes several examples of successful multilateral anomaly resolution. These successes were used to form the framework of the Partner to Partner engineering interface procedures, and this paper describes those currently documented multilateral engineering processes. Furthermore, it addresses the challenges experienced to date, and the forward work expected in establishing a successful working relationship with Partners as their hardware is launched.
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.
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.;
2017-01-01
The Systems Engineering Project Management Advancement Program (SEPMAP) at NASA Johnson Space Center (JSC) is an employee development program designed to provide graduate level training in project management and systems engineering. The program includes an applied learning project with engineering and integrated science goals requirements. The teams were presented with a task: Collect a representative sample set from a field site using a hexacopter platform, as if performing a scientific reconnaissance to assess whether the site is of sufficient scientific interest to justify exploration by astronauts. Four teams worked through the eighteen-month course to design customized sampling payloads integrated with the hexacopter, and then operate the aircraft to meet sampling requirements of number (= 5) and mass (= 5g each). The "Mars Yard" at JSC was utilized for this purpose. This project activity closely parallels NASA plans for the future exploration of Mars, where remote sites will be reconnoitered ahead of crewed exploration.
2007-10-04
The team developing NASA Mars Science Laboratory calls this test rover Scarecrow because the vehicle does not include a computer brain. Mobility engineers use this test rover to evaluate mobility and suspension performance.
Anderson, Devon E; Watts, Bradley V
2013-09-01
Despite innumerable attempts to eliminate the postoperative retention of surgical sponges, the medical error persists in operating rooms worldwide and places significant burden on patient safety, quality of care, financial resources, and hospital/physician reputation. The failure of countless solutions, from new sponge counting methods to radio labeled sponges, to truly eliminate the event in the operating room requires that the emerging field of health-care delivery science find innovative ways to approach the problem. Accordingly, the VA National Center for Patient Safety formed a unique collaboration with a team at the Thayer School of Engineering at Dartmouth College to evaluate the retention of surgical sponges after surgery and find a solution. The team used an engineering problem solving methodology to develop the best solution. To make the operating room a safe environment for patients, the team identified a need to make the sponge itself safe for use as opposed to resolving the relatively innocuous counting methods. In evaluation of this case study, the need for systematic engineering evaluation to resolve problems in health-care delivery becomes clear.
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.
ERIC Educational Resources Information Center
Haruna, Umar Ibrahim
2015-01-01
Collaboration plays a major role in interdisciplinary activities among Science, Technology, Engineering & Mathematics (STEM) disciplines or fields. It also affects the relationships among cluster members on the management team. Although effective collaboration does not guarantee success among STEM disciplines, its absence usually assures…
Investigating the Impacts of Design Heuristics on Idea Initiation and Development
ERIC Educational Resources Information Center
Kramer, Julia; Daly, Shanna R.; Yilmaz, Seda; Seifert, Colleen M.; Gonzalez, Richard
2015-01-01
This paper presents an analysis of engineering students' use of Design Heuristics as part of a team project in an undergraduate engineering design course. Design Heuristics are an empirically derived set of cognitive "rules of thumb" for use in concept generation. We investigated heuristic use in the initial concept generation phase,…
An Example-Centric Tool for Context-Driven Design of Biomedical Devices
ERIC Educational Resources Information Center
Dzombak, Rachel; Mehta, Khanjan; Butler, Peter
2015-01-01
Engineering is one of the most global professions, with design teams developing technologies for an increasingly interconnected and borderless world. In order for engineering students to be proficient in creating viable solutions to the challenges faced by diverse populations, they must receive an experiential education in rigorous engineering…
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…
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.
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.
Developing a Sand Management Plan for Galveston Island
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
2017-04-10
Natick Soldier Research , Development and Engineering Center’s Sustainability/Logistics- Basing -Science and Technology Objective – Demonstration to...CERDEC) Tank Automotive Research , Development, and Engineering Center (TARDEC) Product Director Contingency Basing Infrastructure (PdD – CBI...assessed using the QoL (O) tool, developed for the SLB-STO-D program by the Consumer Research Team (NSRDEC), based upon the assumptions documented within
The shuttle main engine: A first look
NASA Technical Reports Server (NTRS)
Schreur, Barbara
1996-01-01
Anyone entering the Space Shuttle Main Engine (SSME) team attends a two week course to become familiar with the design and workings of the engine. This course provides intensive coverage of the individual hardware items and their functions. Some individuals, particularly those involved with software maintenance and development, have felt overwhelmed by this volume of material and their lack of a logical framework in which to place it. To provide this logical framework, it was decided that a brief self-taught introduction to the overall operation of the SSME should be designed. To aid the people or new team members with an interest in the software, this new course should also explain the structure and functioning of the controller and its software. This paper presents a description of this presentation.
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 transfer) students enroll in an introductory engineering course. Historically, these students worked on a team-based analysis project, and the engineering design…
VE at Scope Time (VEST): Three construction examples
DOE Office of Scientific and Technical Information (OSTI.GOV)
Sperling, R.B.
1991-04-01
Value Engineering at Scope Time (VEST)'' was published in Value World, January-February-March 1991. That article describes VEST as a four-phase process utilizing the heart'' of VE methodology, which is designed to be used with members of construction design teams to help them focus on the scope of work by doing cost modeling, function analysis, brainstorming and evaluation of ideas. With minimal training designers, architects and engineers can become energized to find creative design solutions and learn an effective, synergistic team approach to facilities design projects using VEST. If time is available, the team can begin the development of some highermore » ranked ideas into preliminary proposals. This paper is an expansion of that article, adding a brief section on training and presenting three examples of VEST on construction projects at a federally-funded research Laboratory.« less
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
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.
Teaching Tip: Managing Software Engineering Student Teams Using Pellerin's 4-D System
ERIC Educational Resources Information Center
Doman, Marguerite; Besmer, Andrew; Olsen, Anne
2015-01-01
In this article, we discuss the use of Pellerin's Four Dimension Leadership System (4-D) as a way to manage teams in a classroom setting. Over a 5-year period, we used a modified version of the 4-D model to manage teams within a senior level Software Engineering capstone course. We found that this approach for team management in a classroom…
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.
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
The Montana ALE (Autonomous Lunar Excavator) Systems Engineering Report
NASA Technical Reports Server (NTRS)
Hull, Bethanne J.
2012-01-01
On May 2 1-26, 20 12, the third annual NASA Lunabotics Mining Competition will be held at the Kennedy Space Center in Florida. This event brings together student teams from universities around the world to compete in an engineering challenge. Each team must design, build and operate a robotic excavator that can collect artificial lunar soil and deposit it at a target location. Montana State University, Bozeman, is one of the institutions selected to field a team this year. This paper will summarize the goals of MSU's lunar excavator project, known as the Autonomous Lunar Explorer (ALE), along with the engineering process that the MSU team is using to fulfill these goals, according to NASA's systems engineering guidelines.
Students Across Borders: A Summer Earth Science Workshop for Hispanic High School Students
NASA Astrophysics Data System (ADS)
Butler, R. F.; Kresan, P.; Baez, A.; Sheppard, P.; Forger, G.; Rendon-Coke, G.; Gray, F.
2003-12-01
Southern Arizona has a high school (HS) population that is 28% Hispanic. However this fast-growing minority group represents only 14% of undergraduate students at the University of Arizona and 11% of science and engineering majors. The Students Across Borders Program was designed to assist Hispanic HS students across borders that often separate them from higher education and careers in science. In June 2003, five person student-teacher teams from Tucson, Yuma, and northern Sonora, Mexico lived in dormitories and participated in a weeklong program based on the University of Arizona campus. Activities included: field trips featuring inquiry-based investigations of geology, water quality, and tree rings; tours of engineering and science laboratories; introduction to student support organizations such as the Society of Hispanic Professional Engineers; and counseling by Career Services and Admissions personnel. Technology training included instruction in web design, digital imaging and online communication tools. Web sites developed by the student teams were presented to participants and families at the conclusion of the on-campus program. Web site development is continuing during the academic year to foster continuing communication between the student teams and presentation of results of follow-on projects assisted by graduate and undergraduate CATTS fellows and university faculty.
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.
Aerodynamic Characterization of a Modern Launch Vehicle
NASA Technical Reports Server (NTRS)
Hall, Robert M.; Holland, Scott D.; Blevins, John A.
2011-01-01
A modern launch vehicle is by necessity an extremely integrated design. The accurate characterization of its aerodynamic characteristics is essential to determine design loads, to design flight control laws, and to establish performance. The NASA Ares Aerodynamics Panel has been responsible for technical planning, execution, and vetting of the aerodynamic characterization of the Ares I vehicle. An aerodynamics team supporting the Panel consists of wind tunnel engineers, computational engineers, database engineers, and other analysts that address topics such as uncertainty quantification. The team resides at three NASA centers: Langley Research Center, Marshall Space Flight Center, and Ames Research Center. The Panel has developed strategies to synergistically combine both the wind tunnel efforts and the computational efforts with the goal of validating the computations. Selected examples highlight key flow physics and, where possible, the fidelity of the comparisons between wind tunnel results and the computations. Lessons learned summarize what has been gleaned during the project and can be useful for other vehicle development projects.
Case study: use of problem-based learning to develop students' technical and professional skills
NASA Astrophysics Data System (ADS)
Warnock, James N.; Mohammadi-Aragh, M. Jean
2016-03-01
Problem-based learning (PBL) is a pedagogy that has attracted attention for many biomedical engineering curricula. The aim of the current study was to address the research question, 'Does PBL enable students to develop desirable professional engineering skills?' The desirable skills identified were communication, teamwork, problem solving and self-directed learning. Forty-seven students enrolled in a biomedical materials course participated in the case study. Students worked in teams to complete a series of problems throughout the semester. The results showed that students made significant improvements in their problem-solving skills, written communication and self-directed learning. Students also demonstrated an ability to work in teams and communicate orally. In conclusion, this case study provides empirical evidence of the efficacy of PBL on student learning. We discuss findings from our study and provide observations of student performance and perceptions that could be useful for faculty and researchers interested in PBL for biomedical engineering education.
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…
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…
NASA Technical Reports Server (NTRS)
Stecklein, Jonette
2017-01-01
NASA has held an annual robotic mining competition for teams of university/college students since 2010. This competition is yearlong, suitable for a senior university engineering capstone project. It encompasses the full project life cycle from ideation of a robot design to actual tele-operation of the robot in simulated Mars conditions mining and collecting simulated regolith. A major required element for this competition is a Systems Engineering Paper in which each team describes the systems engineering approaches used on their project. The score for the Systems Engineering Paper contributes 25% towards the team's score for the competition's grand prize. The required use of systems engineering on the project by this competition introduces the students to an intense practical application of systems engineering throughout a full project life cycle.
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.
Progress update on a 2015 USIP interdisciplinary undergraduate student microgravity experiment
NASA Astrophysics Data System (ADS)
Dove, A.; Colwell, J. E.; Brisset, J.; Kirstein, J.; Brightwell, K.; Hayden, R.; Jorges, J.; Schwartzberg, D.; Strange, J.; Yates, A.
2016-12-01
Our team was selected by the 2016 USIP program to build, fly, and analyze the results from a granular dynamics experiment that will fly in 2017 on a suborbital flight. The experiment will be designed to test technology and enable science relevant to low-gravity planetary objects, such as asteroids, comets, and small moons. Following on the success of previous NASA Flight Opportunities Program (FOP) and Undergraduate Student Instrumentation Project (USIP) projects, however, the primary driver of the project is to enable undergraduate student participation in the entire lifetime of a science and technology development project. Our mentoring team consists of faculty, postdoctoral researchers, and graduate students, who have experience with the past USIP program and similar projects, as well as with mentoring undergraduate students. The undergraduate team includes a diversity of major disciplines, including physics, mechanical/aerospace engineering, electrical engineering, business (accounting), and marketing. Each team member has specific project tasks, as outlined in the proposal, and all members will also help develop and participate in outreach events. In additional to their project roles, students will also be responsible for presentations and milestones, such as design reviews. Through these reviews and the outreach events, all team members have the chance to develop their technical and non-technical communication skills. Previous experience with the NASA USIP program demonstrated that students achieve significant growth through these projects -gaining a better understanding of the entire lifecycle of a project, and, likely more importantly, how to work with a diverse team. In this talk, we will discuss the status of the project, and present student impressions and thoughts on the project thus far.
Joint Contracture Orthosis (JCO)
NASA Technical Reports Server (NTRS)
Lunsford, Thomas R.; Parsons, Ken; Krouskop, Thomas; McGee, Kevin
1997-01-01
The purpose of this project was to develop an advanced orthosis which is effective in reducing upper and lower limb contractures in significantly less time than currently required with conventional methods. The team that developed the JCO consisted of an engineer, orthotist, therapist, and physician.
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…
2017-04-20
In the second annual Swarmathon competition at NASA's Kennedy Space Center in Florida, students were asked to develop computer code for the small robots called "Swarmies." The students programmed the robots to look for "resources" in the form of cubes with AprilTags, similar to barcodes. A team from Southwestern Indian Polytechnic Institute (SIPI) in Albuquerque, New Mexico, captured first place and a $5,000 cash prize. SIPI team members, from the left, are: students Emery Sutherland, Ty Shurley, Christian Martinez, SIPI engineering professor Dr. Nader Vadiee who was the team's faculty advisor, and student Schulte Cooke.
Proposing an Evidence-Based Strategy for Software Requirements Engineering.
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.
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.
New Frontiers AO: Advanced Materials Bi-propellant Rocket (AMBR) Engine Information Summary
NASA Technical Reports Server (NTRS)
Liou, Larry C.
2008-01-01
The Advanced Material Bi-propellant Rocket (AMBR) engine is a high performance (I(sub sp)), higher thrust, radiation cooled, storable bi-propellant space engine of the same physical envelope as the High Performance Apogee Thruster (HiPAT(TradeMark)). To provide further information about the AMBR engine, this document provides details on performance, development, mission implementation, key spacecraft integration considerations, project participants and approach, contact information, system specifications, and a list of references. The In-Space Propulsion Technology (ISPT) project team at NASA Glenn Research Center (GRC) leads the technology development of the AMBR engine. Their NASA partners were Marshall Space Flight Center (MSFC) and Jet Propulsion Laboratory (JPL). Aerojet leads the industrial partners selected competitively for the technology development via the NASA Research Announcement (NRA) process.
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.
NASA Technical Reports Server (NTRS)
Adamovsky, Grigory; Mackey, Jeffrey R.; Kren, Lawrence A.; Floyd, Bertram M.; Elam, Kristie A.; Martinez, Martel
2014-01-01
A High Temperature Fiber Optic Sensor (HTFOS) has been developed at NASA Glenn Research Center for aircraft engine applications. After fabrication and preliminary in-house performance evaluation, the HTFOS was tested in an engine environment at NASA Armstrong Flight Research Center. The engine tests enabled the performance of the HTFOS in real engine environments to be evaluated along with the ability of the sensor to respond to changes in the engine's operating condition. Data were collected prior, during, and after each test in order to observe the change in temperature from ambient to each of the various test point levels. An adequate amount of data was collected and analyzed to satisfy the research team that HTFOS operates properly while the engine was running. Temperature measurements made by HTFOS while the engine was running agreed with those anticipated.
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)
Students Compete in NASA's Student Launch Competition
2018-03-30
NASA's Student Launch competition challenges middle school, high school and college teams to design, build, test and fly a high-powered, reusable rocket to an altitude of one mile above ground level while carrying a payload. During the eight-month process, the selected teams will go through a series of design, test and readiness reviews that resemble the real-world process of rocket development. In addition to building and preparing their rocket and payload, the teams must also create and execute an education and outreach program that will share their work with their communities and help inspire the next generation of scientists, engineers and explorers. Student Launch is hosted by NASA's Marshall Space Flight Center in Huntsville, Alabama, and is managed by Marshall's Academic Affairs Office to further NASA’s major education goal of attracting and encouraging students to pursue degrees and careers in the STEM fields of science, technology, engineering and mathematics.
Capabilities of the Materials Contamination Team at Marshall Space Flight Center
NASA Technical Reports Server (NTRS)
Burns, H. D.; Finckenor, M. M.; Boothe, R. E.; Albyn, K. C.; Finchum, C. A.
2003-01-01
The Materials Contamination Team of the Environmental Effects Group, Materials, Processes, and Manufacturing Department, has been recognized for its contribution to space flight, including space transportation, space science and flight projects, such as the reusable solid rocket motor, Chandra X-Ray Observatory, and the International Space Station. The Materials Contamination Team s realm of responsibility encompasses all phases of hardware development including design, manufacturing, assembly, test, transportation, launch-site processing, on-orbit exposure, return, and refurbishment if required. Contamination is a concern in the Space Shuttle with sensitivity bondlines and reactive fluid (liquid oxygen) compatibility as well as for sensitive optics, particularly spacecraft such as Hubble Space Telescope and Chandra X-Ray Observatory. The Materials Contamination Team has a variety of facilities and instrumentation capable of contaminant detection identification, and monitoring. The team addresses material applications dealing with environments, including production facilities, clean rooms, and on-orbit exposure. The team of engineers and technicians also develop and evaluates new surface cleanliness inspection technologies. Databases are maintained by the team for proces! materials as well as outgassing and optical compatibility test results for specific environments.
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…
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.
Frontier Observatory for Research in Geothermal Energy: Phase 1 Topical Report Fallon, NV
DOE Office of Scientific and Technical Information (OSTI.GOV)
Blankenship, Douglas A.; Akerley, John; Blake, Kelly
The Department of Energy (DOE) Frontier Observatory for Research in Geothermal Energy (FORGE) is to be a dedicated site where the subsurface scientific and engineering community can develop, test, and improve technologies and techniques for the creation of cost-effective and sustainable enhanced geothermal systems (EGS) in a controlled, ideal environment. The establishment of FORGE will facilitate development of an understanding of the key mechanisms controlling a successful EGS. Execution of FORGE is occurring in three phases with five distinct sub-phases (1, 2A, 2B, 2C, and 3). This report focuses on Phase 1 activities. During Phase 1, critical technical and logisticalmore » tasks necessary to demonstrate the viability of the Fallon FORGE Project site were completed and the commitment and capability of the Fallon FORGE team to execute FORGE was demonstrated. As part of Phase 1, the Fallon FORGE Team provided an assessment of available relevant data and integrated these geologic and geophysical data to develop a conceptual 3-D geologic model of the proposed test location. Additionally, the team prepared relevant operational plans for full FORGE implementation, provided relevant site data to the science and engineering community, engaged in outreach and communications with interested stakeholders, and performed a review of the environmental and permitting activities needed to allow FORGE to progress through Phase 3. The results of these activities are provided as Appendices to this report. The Fallon FORGE Team is diverse, with deep roots in geothermal science and engineering. The institutions and key personnel that comprise the Fallon FORGE Team provide a breadth of geoscience and geoengineering capabilities, a strong and productive history in geothermal research and applications, and the capability and experience to manage projects with the complexity anticipated for FORGE. Fallon FORGE Team members include the U.S. Navy, Ormat Nevada Inc., Sandia National Laboratories (SNL), Lawrence Berkeley National Laboratory (LBNL), the United States Geological Survey (USGS), the University of Nevada, Reno (UNR), GeothermEx/Schlumberger (GeothelinEx), and Itasca Consulting Group (Itasca). The site owners (through direct land ownership or via applicable permits)—the U.S. Navy and Ormat Nevada Inc.—are deeply committed to expanding the development of geothermal resources and are fully supportive of FORGE operations taking place on their lands.« less
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.
Research and technology 1995 annual report
NASA Technical Reports Server (NTRS)
1995-01-01
As the NASA Center responsible for assembly, checkout, servicing, launch, recovery, and operational support of Space Transportation System elements and payloads, the John F. Kennedy Space Center is placing increasing emphasis on its advanced technology development program. This program encompasses the efforts of the Engineering Development Directorate laboratories, most of the KSC operations contractors, academia, and selected commercial industries - all working in a team effort within their own areas of expertise. This edition of the Kennedy Space Center Research and Technology 1995 Annual Report covers efforts of all these contributors to the KSC advanced technology development program, as well as technology transfer activities. Major areas of research include environmental engineering, automation, robotics, advanced software, materials science, life sciences, mechanical engineering, nondestructive evaluation, and industrial engineering.
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..
DOE Office of Scientific and Technical Information (OSTI.GOV)
Alan Black; Arnis Judzis
2003-10-01
This document details the progress to date on the OPTIMIZATION OF DEEP DRILLING PERFORMANCE--DEVELOPMENT AND BENCHMARK TESTING OF ADVANCED DIAMOND PRODUCT DRILL BITS AND HP/HT FLUIDS TO SIGNIFICANTLY IMPROVE RATES OF PENETRATION contract for the year starting October 2002 through September 2002. The industry cost shared program aims to benchmark drilling rates of penetration in selected simulated deep formations and to significantly improve ROP through a team development of aggressive diamond product drill bit--fluid system technologies. Overall the objectives are as follows: Phase 1--Benchmark ''best in class'' diamond and other product drilling bits and fluids and develop concepts for amore » next level of deep drilling performance; Phase 2--Develop advanced smart bit--fluid prototypes and test at large scale; and Phase 3--Field trial smart bit--fluid concepts, modify as necessary and commercialize products. Accomplishments to date include the following: 4Q 2002--Project started; Industry Team was assembled; Kick-off meeting was held at DOE Morgantown; 1Q 2003--Engineering meeting was held at Hughes Christensen, The Woodlands Texas to prepare preliminary plans for development and testing and review equipment needs; Operators started sending information regarding their needs for deep drilling challenges and priorities for large-scale testing experimental matrix; Aramco joined the Industry Team as DEA 148 objectives paralleled the DOE project; 2Q 2003--Engineering and planning for high pressure drilling at TerraTek commenced; 3Q 2003--Continuation of engineering and design work for high pressure drilling at TerraTek; Baker Hughes INTEQ drilling Fluids and Hughes Christensen commence planning for Phase 1 testing--recommendations for bits and fluids.« less
1940-01-01
This drawing illustrates the vital dimensions of the A-4 (Aggregate-4). Later renamed the V-2 (Vengeance Weapon-2), the rocket was developed by Dr. Wernher von Braun and the German rocket team at Peenemuende, Germany on the Baltic Sea. At the end of World War II, the team of German engineers and scientists came to the United States and continued rocket research for the Army at Fort Bliss, Texas, and Redstone Arsenal in Huntsville, Alabama.
1940-01-01
The cutaway drawing of the A-4 (Aggregate-4) rocket. Later renamed the V-2 (Vengeance Weapon-2), The rocket was developed by Dr. Wernher von Braun and the German rocket team at Peenemuende, Germany on the Baltic Sea. At the end of World War II, the team of German engineers and scientists came to the United States and continued rocket research for the Army at Fort Bliss, Texas, and Redstone Arsenal in Huntsville, Alabama.
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.
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.
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;
2012-01-01
The Iowa State University team, Team LunaCY, is composed of the following sub-teams: the main student organization, the Lunabotics Club; a senior mechanical engineering design course, ME 415; a senior multidisciplinary design course, ENGR 466; and a senior design course from Wartburg College in Waverly, Iowa. Team LunaCY designed and fabricated ART-E III, Astra Robotic Tractor- Excavator the Third, for the team's third appearance in the NASA Lunabotic Mining competition. While designing ART-E III, the team had four main goals for this year's competition:to reduce the total weight of the robot, to increase the amount of regolith simulant mined, to reduce dust, and to make ART-E III autonomous. After many designs and research, a final robot design was chosen that obtained all four goals of Team LunaCY. A few changes Team LunaCY made this year was to go to the electrical, computer, and software engineering club fest at Iowa State University to recruit engineering students to accomplish the task of making ART-E III autonomous. Team LunaCY chose to use LabView to program the robot and various sensors were installed to measure the distance between the robot and the surroundings to allow ART-E III to maneuver autonomously. Team LunaCY also built a testing arena to test prototypes and ART-E III in. To best replicate the competition arena at the Kennedy Space Center, a regolith simulant was made from sand, QuickCrete, and fly ash to cover the floor of the arena. Team LunaCY also installed fans to allow ventilation in the arena and used proper safety attire when working in the arena . With the additional practice in the testing arena and innovative robot design, Team LunaCY expects to make a strong appearance at the 2012 NASA Lunabotic Mining Competition. .
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.
Highway rail crossing prioritization.
DOT National Transportation Integrated Search
2015-03-01
Research team members at the University of Kentucky in the Department of Civil Engineering and the : Kentucky Transportation Center (KTC) worked with the Kentucky Transportation Cabinet (KYTC) to develop : a high-level mechanism for ranking highway-r...
Career Profiles- Aero-Mechanical Design- Operations Engineering Branch
2015-10-26
NASA Armstrong’s Aeromechanical Design Group provides mechanical design solutions ranging from research and development to ground support equipment. With an aerospace or mechanical engineering background, team members use the latest computer-aided design software to create one-of-kind parts, assemblies, and drawings, and aid in the design’s fabrication and integration. Reverse engineering and inspection of Armstrong’s fleet of aircraft is made possible by using state-of-the-art coordinate measuring machines and laser scanning equipment.
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.
Marshall (MSFC) 3D Printing Media Resource
2018-06-12
Edited b-roll video from NASA’s Marshall Space Flight Center in Huntsville, Ala. Engineers at Marshall are pioneering and advancing new additive manufacturing techniques that can greatly reduce costs and development of rocket engines and other spacecraft components. Marshall teams also managed the development of the International Space Station’s first 3D printer. For more information and/or more detailed footage please contact the Marshall Office of Communications. PAO: Jennifer Stanfield, 256-544-0034, Jennifer.stanfield@nasa.gov
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.
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.
ERIC Educational Resources Information Center
Grande, Francisco José Suñé; Witt, Hans Jörg; Avalos, Josep Bonet
2015-01-01
The Escola Tècnica Superior d'Enginyeria Química has a long tradition in the deployment of social competencies in engineering curricula through Integrated Projects (IP) carried out in structured teams. Social competencies are taught and practiced during the development of the IPs. We conceptually introduce a methodology for a 360 degrees…
Training System Device Certification and Qualification Process
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
RT 164: Design and Development Tools for the Systems Engineering Experience Accelerator - Part 3
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
DOE Office of Scientific and Technical Information (OSTI.GOV)
Minana, Molly A.; Sturtevant, Judith E.; Heaphy, Robert
2005-01-01
The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in DOE/AL Quality Criteria (QC-1) as conformance to customer requirements and expectations. This quality plan defines the ASC program software quality practices and provides mappings of these practices to the SNL Corporate Process Requirements (CPR 1.3.2 and CPR 1.3.6) and the Department of Energy (DOE) document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines (GP&G). This quality plan identifies ASC management andmore » software project teams' responsibilities for cost-effective software engineering quality practices. The SNL ASC Software Quality Plan establishes the signatories commitment to improving software products by applying cost-effective software engineering quality practices. This document explains the project teams opportunities for tailoring and implementing the practices; enumerates the practices that compose the development of SNL ASC's software products; and includes a sample assessment checklist that was developed based upon the practices in this document.« less
1998-09-16
A team of engineers at Marshall Space Flight Center (MSFC) has designed, fabricated, and tested the first solar thermal engine, a non-chemical rocket that produces lower thrust but has better thrust efficiency than the chemical combustion engines. This segmented array of mirrors is the solar concentrator test stand at MSFC for firing the thermal propulsion engines. The 144 mirrors are combined to form an 18-foot diameter array concentrator. The mirror segments are aluminum hexagons that have the reflective surface cut into it by a diamond turning machine, which is developed by MSFC Space Optics Manufacturing Technology Center.
An Industrial Engineering Approach to Cost Containment of Pharmacy Education.
Duncan, Wendy; Bottenberg, Michelle; Chase, Marilea; Chesnut, Renae; Clarke, Cheryl; Schott, Kathryn; Torry, Ronald; Welty, Tim
2015-11-25
A 2-semester project explored employing teams of fourth-year industrial engineering students to optimize some of our academic management processes. Results included significant cost savings and increases in efficiency, effectiveness, and student and faculty satisfaction. While we did not adopt all of the students' recommendations, we did learn some important lessons. For example, an initial investment of time in developing a mutually clear understanding of the problems, constraints, and goals maximizes the value of industrial engineering analysis and recommendations. Overall, industrial engineering was a valuable tool for optimizing certain academic management processes.
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.
Exploring the Intersections of Science and History Learning
ERIC Educational Resources Information Center
Hughes, Catherine; Cosbey, Allison
2016-01-01
How can history museums incorporate Science, Technology, Engineering and Math (STEM) activities while preserving their missions and identities? How do interdisciplinary experiences lead to learning? A cross-institutional exhibit development and evaluation team wrestled with these ideas as they developed "Create.Connect," an National…
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.
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.
Korb, Werner; Geißler, Norman; Strauß, Gero
2015-03-01
Engineering a medical technology is a complex process, therefore it is important to include experts from different scientific fields. This is particularly true for the development of surgical technology, where the relevant scientific fields are surgery (medicine) and engineering (electrical engineering, mechanical engineering, computer science, etc.). Furthermore, the scientific field of human factors is important to ensure that a surgical technology is indeed functional, process-oriented, effective, efficient as well as user- and patient-oriented. Working in such trans- and inter-disciplinary teams can be challenging due to different working cultures. The intention of this paper is to propose an innovative cooperative working culture for the interdisciplinary field of computer-assisted surgery (CAS) based on more than ten years of research on the one hand and the interdisciplinary literature on working cultures and various organizational theories on the other hand. In this paper, a retrospective analysis of more than ten years of research work in inter- and trans-disciplinary teams in the field of CAS will be performed. This analysis is based on the documented observations of the authors, the study reports, protocols, lab reports and published publications. To additionally evaluate the scientific experience in an interdisciplinary research team, a literature analysis regarding scientific literature on trans- and inter-disciplinarity was performed. Own research and literature analyses were compared. Both the literature and the scientific experience in an interdisciplinary research team show that consensus finding is not always easy. It is, however, important to start trans- and interdisciplinary projects with a shared mental model and common goals, which include communication and leadership issues within the project teams, i.e. clear and unambiguous information about the individual responsibilities and objectives to attain. This is made necessary due to differing leadership cultures within the cooperating disciplines. Another research outcome is the relevance of a cooperative learning culture throughout the complete duration of the project. Based on this cooperation, new ideas and projects were developed, i.e. a training concept for surgical trainers including technological competence for surgeons. An adapted innovative paradigm for a cooperating working culture in CAS is based on a shared mental model and common goals from the very beginning of a project. All actors in trans- and inter-disciplinary teams need to be interested in cooperation. This will lead to a common view on patients and technology models. Copyright © 2015 Elsevier B.V. All rights reserved.
Medical Engineering and Microneurosurgery: Application and Future.
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
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
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...
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.
Preliminary Design Phases, Part of Indoor Air Quality Design Tools for Schools
The typical design process for schools begins with programming and selection of the architectural-engineering team. It then proceeds through schematic design, design development, contract documents, construction, commissioning and occupancy.
Pitfalls and Successes of Developing an Interdisciplinary Watershed Field Science Course
ERIC Educational Resources Information Center
Pearce, Andrea R.; Bierman, Paul R.; Druschel, Gregory K.; Massey, Christine; Rizzo, Donna M.; Watzin, Mary C.; Wemple, Beverly C.
2010-01-01
At the University of Vermont, an interdisciplinary faculty team developed an introductory watershed science field course. This course honed field skills and catalyzed communication across water-related disciplines without requiring specific prerequisites. Five faculty (geology, engineering, geography, natural resources) taught the four-credit…
SAFETY ON UNTRUSTED NETWORK DEVICES (SOUND)
2017-10-10
in the Cyber & Communication Technologies Group , but not on the SOUND project, would review the code, design and perform attacks against a live...3.5 Red Team As part of our testing , we planned to conduct Red Team assessments. In these assessments, a group of engineers from BAE who worked...developed under the DARPA CRASH program and SOUND were designed to be companion projects. SAFE focused on the processor and the host, SOUND focused on
1940-01-01
This German cutaway drawing of the Aggregate-4 (A-4) illustrates the dimensions and internal workings of the rocket. Later renamed the V-2, the rocket was developed by Dr. Wernher von Braun and the German Rocket Team at Peenemuende on the Baltic Sea. At the end of World War II, the team of German engineers and scientists came to the United States to work for the Army at Fort Bliss, Texas, and Redstone Arsenal in Huntsville, Alabama.
Synthetic Teammates as Team Players: Coordination of Human and Synthetic Teammates
2016-05-31
distribution is unlimited 13. SUPPLEMENTARY NOTES 14. ABSTRACT This project is part of a larger effort that focuses on human-automation coordination in the...context of the development, integration, and validation of a computational cognitive model that acts as a full-fledged synthetic teammate on an...integrated the synthetic teammate model into the CERTT II (Cognitive Engineering Research on Team Tasks II) testbed in order to empirically address these
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.
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
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
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
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
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
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)
Learning to Write Programs with Others: Collaborative Quadruple Programming
ERIC Educational Resources Information Center
Arora, Ritu; Goel, Sanjay
2012-01-01
Most software development is carried out by teams of software engineers working collaboratively to achieve the desired goal. Consequently software development education not only needs to develop a student's ability to write programs that can be easily comprehended by others and be able to comprehend programs written by others, but also the ability…
Creating a High Impact Learning Environment for Engineering Technology Students
ERIC Educational Resources Information Center
Zhan, Wei; Wang, Jyhwen; Vanajakumari, Manoj; Johnson, Michael D.
2018-01-01
This paper discusses an initiative called Product Innovation and Development (PID) that was launched at Texas A&M University. The goal of PID is to create a high impact learning environment that focuses on innovative product development. Undergraduate students are hired to develop innovative new products. The student teams generate ideas for…
The Outer Planetary Mission Design Project
NASA Astrophysics Data System (ADS)
Benfield, Michael; Turner, M. W.
2010-10-01
With the recent focus from the planetary science community on the outer planets of the solar system, The University of Alabama in Huntsville Integrated Product Team program is embarking on a new challenge to develop an outer planetary mission for the academic year 2010-2011. Currently four bodies are of interest for this mission: Titan, Europa, Triton, and Enceledus, with one body being chosen by the instructors by the beginning of the fall semester. This project will use the 2010 Discovery Announcement of Opportunity as its Request for Proposal (RFP). All of the teams competing in this project will use the AO to respond with a proposal to the instructors for their proposed mission and spacecraft concept. The project employs the two-semester design sequence of the IPT program to provide a framework for the development of this mission. This sequence is divided into four phases. Phase 1 - Requirements Development - focuses on the development of both the scientific and engineering requirements of the mission. During this phase the teams work very closely with the PI organization, represented by the College of Charleston. Phase 2 - Team Formation and Architecture Development - concentrates on the assessment of the overall mission architecture from the launch vehicle to the ground operations of the proposed spacecraft. Phase 3 - System Definition - provides for spacecraft subsystem trade studies and further refinement of the specific spacecraft to meet the scientific requirements and objectives developed in Phase 1. Phase 4 - Design - is the phase where the engineers provide the spacecraft design that is required for the mission of interest. At the conclusion of Phases 2 and 4, an external review board evaluates the proposed designs and chooses one winner of the competition.
Vielhauer, Jan; Böckmann, Britta
2017-01-01
Requirements engineering of software products for elderly people faces some special challenges to ensure a maximum of user acceptance. Within the scope of a research project, a web-based platform and a mobile app are approached to enable people to live in their own home as long as possible. This paper is about a developed method of interdisciplinary requirements engineering by a team of social scientists in cooperation with computer scientists.
Lessons Learned during the Development of HumaPen® Memoir™, an Insulin Pen with a Memory Feature
Breslin, Stuart D.; Ignaut, Debra A.; Boyd, Douglas E.
2010-01-01
Insulin pens are developed to address specific needs of diabetes patients for their pens, such as ease of use, portability, and discreetness. Like many consumer-based products, the development of insulin pens can pose significant challenges to the development team in that they must balance substantial accuracy requirements with aesthetic desires. The HumaPen® Memoir™ team learned valuable lessons throughout the development process that may be worth highlighting. A keen understanding of the unmet needs of the patient population and a skillfully planned product generation map are critical to successful device development. A development team must decide whether to use a Quality Functional Deployment or system engineering-based development plan and, additionally, recognize where proof of concept ends and product development begins to maintain a strict timeline for the project. A proficiency in understanding and managing technical risk is critical to ensure a timely and high-quality product launch to the marketplace. PMID:20513318
From Paper to Production to Test: An Update on NASA's J-2X Engine for Exploration
NASA Technical Reports Server (NTRS)
Kynard, Michael
2011-01-01
The NASA/industry team responsible for developing the J-2X upper stage engine for the Space Launch System (SLS) Program has made significant progress toward moving beyond the design phase and into production, assembly, and test of development hardware. The J-2X engine exemplifies the SLS Program goal of using proven technology and experience from more than 50 years of United States spaceflight experience combined with modern manufacturing processes and approaches. It will power the second stage of the fully evolved SLS Program launch vehicle that will enable a return to human exploration of space beyond low earth orbit. Pratt & Whitney Rocketdyne (PWR) is under contract to develop and produce the engine, leveraging its flight-proven LH2/LOX, gas generator cycle J-2 and RS-68 engine capabilities, recent experience with the X-33 aerospike XRS-2200 engine, and development knowledge of the J-2S tap-off cycle engine. The J- 2X employs a gas generator operating cycle designed to produce 294,000 pounds of vacuum thrust in primary operating mode with its full nozzle extension. With a truncated nozzle extension suitable to support engine clustering on the stage, the nominal vacuum thrust level in primary mode is 285,000 pounds. It also has a secondary mode, during which it operates at 80 percent thrust by altering its mixture ratio. The J-2X development philosophy is based on proven hardware, an aggressive development schedule, and early risk reduction. NASA Marshall Space Flight Center (MSFC) and PWR began development of the J-2X in June 2006. The government/industry team of more than 600 people within NASA and PWR successfully completed the Critical Design Review (CDR) in November 2008, following extensive risk mitigation testing. Assembly of the first development engine was completed in May 2011 and the first engine test was conducted at the NASA Stennis Space Center (SSC), test stand A2, on 14 July 2011. Testing of the first development engine will continue through the autumn of 2011, be paused for test stand modifications to the passive diffuser, and then restart in the spring of 2012. This testing will be followed by specialized powerpack testing intended to examine the design and operating margins of the engine turbomachinery. The development plan beyond this point leads through more system-level, engine testing of several samples, analytical model validation activities, functional and performance verification, and then ultimate certification to support human spaceflight. This paper will discuss the J-2X development background, provide top-level information on design and development planning, and will explore some of the development challenges and mitigation activities pursued to date.
Teaching practical leadership in MIT satellite development class: CASTOR and Exoplanet projects
NASA Astrophysics Data System (ADS)
Babuscia, Alessandra; Craig, Jennifer L.; Connor, Jane A.
2012-08-01
For more than a decade, the Aeronautics and Astronautics Department at MIT has offered undergraduate students the opportunity of conceiving, developing, implementing and operating new spacecraft's missions. During a three term class, junior and senior students experience all the challenges of a true engineering team project: design, analysis, testing, technical documentation development, team management, and leadership. Leadership instruction is an important part of the curricula; through the development of leadership skills, students learn to manage themselves and each other in a more effective way, increasing the overall productivity of the team. Also, a strong leadership education is a key factor in improving the abilities of future engineers to be effective team members and leaders in the companies and agencies in which they will work. However, too often leadership instruction is presented in an abstract way, which does not provide students with suggestions for immediate applicability. As a consequence, students underestimate the potential that leadership education can have on the development of their projects. To counteract that effect, a new approach for teaching "practical" leadership has been developed. This approach is composed of a set of activities developed to improve students' leadership skills in the context of a project. Specifically, this approach has been implemented in the MIT satellite development class. In that class, students experienced the challenges of building two satellites: CASTOR and Exoplanet. These two missions are real space projects which will be launched in the next two years, and which involve cooperation with different entities (MIT, NASA, and Draper). Hence, the MIT faculty was interested in developing leadership activities to improve the productivity of the teams in a short time. In fact, one of the key aspects of the approach proposed is that it can be quickly implemented in a single semester, requiring no more than 4 h of activity. Data collected show that the approach improved the ability of students to interact productively with each other. This suggests that the activity can also be used in different contexts where a rapid and effective way of improving leadership and team membership is required. The article presents an overview of MIT satellite development class and of the two missions used as test cases, a detailed description of the leadership approach implemented, and of the results obtained.
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...
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.
Large-Scale Digital Geologic Map Databases and Reports of the North Coal District in Afghanistan
Hare, Trent M.; Davis, Philip A.; Nigh, Devon; Skinner, James A.; SanFilipo, John R.; Bolm, Karen S.; Fortezzo, Corey M.; Galuszka, Donna; Stettner, William R.; Sultani, Shafiqullah; Nader, Billal
2008-01-01
This report describes the Afghanistan coal resource maps and associated databases that have been digitally captured and maps that have been thus far converted to GIS databases. Several maps by V/O Technoexport, USSR (VOTU) and Bundesanstalt fur Bodenforschung (BGR), Hannover, Germany, are captured here. Most of the historical coal exploration is concentrated in north-central Afghanistan, a region referred to as the 'North Coal District', and almost all of the coal-related maps found Afghanistan Geological Survey (AGS) archives to date cover various locations within that district as shown in the index map. Most of the maps included herein were originally scanned during U.S. Geological Survey (USGS) site visits to Kabul in November 2004 and February 2006. The scanning was performed using equipment purchased by U.S. Agency for International Development (USAID) and U.S. Trade and Development Agency (USTDA) and installed at the AGS by USGS. Many of these maps and associated reports exist as single unpublished copies in the AGS archives, so these efforts served not only to provide a basis for digital capturing, but also as a means for preserving these rare geologic maps and reports. The data included herein represent most of the coal-related reports and maps that are available in the AGS archives. This report excludes the limited cases when a significant portion of a report's text could not be located, but it does not exclude reports with missing plates. The vector files are released using the Environmental Systems Research Institute (ESRI) Personal Geodatabase, ESRI shapefile vector format, and the open Geography Markup Language (GML) format. Scanned images are available in JPEG and, when rectified, GeoTIFF format. The authors wish to acknowledge the contributions made by the staff of the AGS Records and Coal Departments whose valuable assistance made it possible to locate and catalogue the data provided herein. We especially acknowledge the efforts of particular members of the coal team: Engineer Saifuddin Aminy (Team Leader); Engineer Gul Pacha Azizi; Engineer Abdul Haq Barakati; Engineer Abdul Basir; Engineer Mohammad Daoud; Engineer Abdullah Ebadi; Engineer Abdul Ahad Omaid; Engineer Spozmy; and Engineer Shapary Tokhi. The ongoing efforts of Engineer Mir M. Atiq Kazimi (Team leader); Engineer M. Anwar Housinzada; and Engineer Shereen Agha of the AGS Records Department to organize and catalogue the AGS material were invaluable in locating and preserving these data. The efforts of the entire AGS staff to personally preserve these data during war time, in the absence of virtually any supporting infrastructure, was truly remarkable. The efforts by the British Geological Survey (BGS) to assist the AGS in archiving these data, and the personal assistance provided by BGS (notably Robert McIntosh), to the USGS teams were also appreciated. The logistical support provided by the U.S. Embassy in Kabul, particularly the Afghanistan Reconstruction Group, was critical to the success of the USGS teams while in Afghanistan. Finally, the efforts of the Minister of the Ministry of Mines and Industries (M. Ibrahim Adel) to support the USGS coal resource assessment in Afghanistan, in both his current and former role as President of the Mines Affairs Department was vital to this effort.
ERIC Educational Resources Information Center
Reid, Kenneth J.
2012-01-01
Ethics is among the professional skills embedded in the first year engineering curriculum in many institutions. The general format of the study of ethics is similar to many other institutions: student teams review case studies and develop written and oral presentations on the ethical issues encountered. This report investigates whether the use of…
How to Do Science From an Engineering Organization
NASA Technical Reports Server (NTRS)
Suggs, Robert M.
2003-01-01
MSFC's Space Environments Team performs engineering support for a number of NASA spaceflight projects by defining the space environment, developing design requirements, supporting the design process, and supporting operations. Examples of this type of support are given including meteoroid environment work for the Jovian Icy Moon Orbiter mission, ionizing radiation support for the Chandra X-Ray Observatory, and astronomicaVgeophysica1 observation planning for International Space Station.
Advanced Mirror Technology Development (AMTD) for Very Large Space Telescopes
NASA Technical Reports Server (NTRS)
Stahl, H. Philip
2013-01-01
Accomplishments include: Assembled outstanding team from academia, industry and government with expertise in science and space telescope engineering. Derived engineering specifications for monolithic primary mirror from science measurement needs & implementation constraints. Pursuing long-term strategy to mature technologies necessary to enable future large aperture space telescopes. Successfully demonstrated capability to make 0.5 m deep mirror substrate and polish it to UVOIR traceable figure specification.
Integrating CMMI and TSP/PSP: Using TSP Data to Create Process Performance Models
2009-11-01
Humphrey , Watts S . PSP : A Self-Improvement Process for Software Engineers. Addison-Wesley, 2005. http://www.sei.cmu.edu/library/abstracts/ books ...Engineering. Addison-Wesley, 2002. [ Humphrey 00] Humphrey , Watts S . The Personal Software Process ( PSP ) (CMU/SEI-2000-TR-022, ADA387268). Pittsburgh...0321305493.cfm [ Humphrey 06a] Humphrey , W. S . TSP: Leading a Development Team. Addison-Wesley, 2006.
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…
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.
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.
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.
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...
NEAR EARTH ASTERIOD SCOUT SOLAR SAIL
2015-01-08
NEAR EARTH ASTEROID (NEA) SAIL TEAM PERFORMING A DEPLOYMENT OF THE FLIGHT-LIKE ENGINEERING DEVELOPMENT UNIT SOLAR SAIL. THE SAIL WAS MANUFACTURED AT NEXOLVE (HSV, AL) AND DEPLOYED FOR THE FIRST TIME AT MSFC ON AUGUST 4TH, 2016
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.
Team 278 gets help from KSC machine shop
NASA Technical Reports Server (NTRS)
2000-01-01
The Hero Team (278) gets some help from a Kennedy Space Center research and development machine shop in repairing their robot, named Hero. The team of Edgewater High School students was co- sponsored by NASA Kennedy Space Center and Honeywell. 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.
Team 278 gets help from KSC machine shop
NASA Technical Reports Server (NTRS)
2000-01-01
The Hero Team (278) robot, named Hero, is repaired in a Kennedy Space Center research and development machine shop. The team of Edgewater High School students was co-sponsored by NASA Kennedy Space Center and Honeywell. 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.
Rosch, David M; Imoukhuede, P I
2016-12-01
The development of a leadership identity has become significant in bioengineering education as a result of an increasing emphasis on teamwork within the profession and corresponding shifts in accreditation criteria. Unsurprisingly, placing bioengineering students in teams to complete classroom-based projects has become a dominant pedagogical tool. However, recent research indicates that engineering students may not develop a leadership identity, much less increased leadership capacity, as a result of such efforts. Within this study, we assessed two similar sections of an introductory course in bioengineering; each placed students in teams, while one also included leadership training and leadership practice. Results suggest that students in the leadership intervention section developed a strong self-image of themselves as leaders compared to students in the control section. These data suggest that creating mechanisms for bioengineering students to be trained in leadership and to practice leadership behaviors within a classroom team may be keys for unlocking leadership development.
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.
Ellis, Heidi J C; Nowling, Ronald J; Vyas, Jay; Martyn, Timothy O; Gryk, Michael R
2011-04-11
The CONNecticut Joint University Research (CONNJUR) team is a group of biochemical and software engineering researchers at multiple institutions. The vision of the team is to develop a comprehensive application that integrates a variety of existing analysis tools with workflow and data management to support the process of protein structure determination using Nuclear Magnetic Resonance (NMR). The use of multiple disparate tools and lack of data management, currently the norm in NMR data processing, provides strong motivation for such an integrated environment. This manuscript briefly describes the domain of NMR as used for protein structure determination and explains the formation of the CONNJUR team and its operation in developing the CONNJUR application. The manuscript also describes the evolution of the CONNJUR application through four prototypes and describes the challenges faced while developing the CONNJUR application and how those challenges were met.
Systematic Method for Establishing Officer Grade Requirements Based Upon Job Demands.
ERIC Educational Resources Information Center
Christal, Raymond E.
This report presents interim results of a study developing a methodology for management engineering teams to determine the appropriate grade requirements for officer positions based on job content and responsibilities. The technology reported represents a modification and extension of methods developed between 1963 and 1966. Results indicated that…
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
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…
Spoelstra, Howard; Stoyanov, Slavi; Burgoyne, Louise; Bennett, Deirdre; Sweeney, Catherine; Drachsler, Hendrik; Vanderperren, Katrien; Van Huffel, Sabine; McSweeney, John; Shorten, George; O'Flynn, Siun; Cantillon-Murphy, Padraig; O'Tuathaigh, Colm
2014-01-22
Healthcare worldwide needs translation of basic ideas from engineering into the clinic. Consequently, there is increasing demand for graduates equipped with the knowledge and skills to apply interdisciplinary medicine/engineering approaches to the development of novel solutions for healthcare. The literature provides little guidance regarding barriers to, and facilitators of, effective interdisciplinary learning for engineering and medical students in a team-based project context. A quantitative survey was distributed to engineering and medical students and staff in two universities, one in Ireland and one in Belgium, to chart knowledge and practice in interdisciplinary learning and teaching, and of the teaching of innovation. We report important differences for staff and students between the disciplines regarding attitudes towards, and perceptions of, the relevance of interdisciplinary learning opportunities, and the role of creativity and innovation. There was agreement across groups concerning preferred learning, instructional styles, and module content. Medical students showed greater resistance to the use of structured creativity tools and interdisciplinary teams. The results of this international survey will help to define the optimal learning conditions under which undergraduate engineering and medicine students can learn to consider the diverse factors which determine the success or failure of a healthcare engineering solution.
2014-01-01
Background Healthcare worldwide needs translation of basic ideas from engineering into the clinic. Consequently, there is increasing demand for graduates equipped with the knowledge and skills to apply interdisciplinary medicine/engineering approaches to the development of novel solutions for healthcare. The literature provides little guidance regarding barriers to, and facilitators of, effective interdisciplinary learning for engineering and medical students in a team-based project context. Methods A quantitative survey was distributed to engineering and medical students and staff in two universities, one in Ireland and one in Belgium, to chart knowledge and practice in interdisciplinary learning and teaching, and of the teaching of innovation. Results We report important differences for staff and students between the disciplines regarding attitudes towards, and perceptions of, the relevance of interdisciplinary learning opportunities, and the role of creativity and innovation. There was agreement across groups concerning preferred learning, instructional styles, and module content. Medical students showed greater resistance to the use of structured creativity tools and interdisciplinary teams. Conclusions The results of this international survey will help to define the optimal learning conditions under which undergraduate engineering and medicine students can learn to consider the diverse factors which determine the success or failure of a healthcare engineering solution. PMID:24450310
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.
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
Growing our own: building a native research team.
Gray, Jacqueline S; Carter, Paula M
2012-01-01
In 2006, American Indian/Alaska Natives (AI/AN) made up less than 1% of the science, engineering and health doctorates in the U.S. Early introduction of AI/AN students to research and continued opportunities are necessary to develop successful AI/AN researchers who can better serve their communities. This team was developed to form a cohort of American Indian students, staff and faculty interested in research and becoming researchers. Since implementation, the program grew from one student to over 20 AI students ranging from freshmen just entering college to doctoral students working to complete their dissertations. This article highlights the team growth, increasing structure, student needs and the faculty and staff involved. It further addresses the support and educational aspects of growing an ongoing, multidisciplinary research team committed to ethical research in Native communities. The team addresses substance use prevalence, the relationship of substance abuse to other mental health diagnoses, and treatment issues. The team includes weekly team meetings, a Blackboard site on the Internet that is populated with resources and focused on sharing materials and information, a weekly journal club discussion of research articles, and collaborative discussions on each project and the barriers and challenges that need to be addressed to move forward.
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
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
Advanced Engineering Environments: Implications for Aerospace Manufacturing
NASA Technical Reports Server (NTRS)
Thomas, D.
2001-01-01
There are significant challenges facing today's aerospace industry. Global competition, more complex products, geographically-distributed design teams, demands for lower cost, higher reliability and safer vehicles, and the need to incorporate the latest technologies quicker all face the developer of aerospace systems. New information technologies offer promising opportunities to develop advanced engineering environments (AEEs) to meet these challenges. Significant advances in the state-of-the-art of aerospace engineering practice are envisioned in the areas of engineering design and analytical tools, cost and risk tools, collaborative engineering, and high-fidelity simulations early in the development cycle. These advances will enable modeling and simulation of manufacturing methods, which will in turn allow manufacturing considerations to be included much earlier in the system development cycle. Significant cost savings, increased quality, and decreased manufacturing cycle time are expected to result. This paper will give an overview of the NASA's Intelligent Synthesis Environment, the agency initiative to develop an AEE, with a focus on the anticipated benefits in aerospace manufacturing.
The design of a long range megatransport aircraft
NASA Technical Reports Server (NTRS)
Weisshaar, Terrence A.; Allen, Carl L.
1992-01-01
During the period from August 1991 - June 1992 two design classes at Purdue University participated in the design of a long range, high capacity transport aircraft, dubbed the megatransport. Thirteen Purdue design teams generated RFP's that defined passenger capability and range, based upon team perception of market needs and infrastructure constraints. Turbofan engines were designed by each group to power these aircraft. The design problem and the variety of solutions developed are described in an attached paper.
2010-12-01
PSP and TSP books by Watts Humphrey or in the TSP-MT (multi-team) process extension. A few additional items should be created, e.g., see OPD-2...Institute, Carnegie Mellon University, 2000. www.sei.cmu.edu/library/abstracts/reports/00tr023.cfm [ Humphrey 2005] Humphrey , Watts S . PSP : A Self... Humphrey 2006] Humphrey , Watts S . TSP: Coaching Development Teams. Addison Wesley, 2006 (ISBN 978- 0201731132). www.sei.cmu.edu/library/abstracts/
Problem-based learning biotechnology courses in chemical engineering.
Glatz, Charles E; Gonzalez, Ramon; Huba, Mary E; Mallapragada, Surya K; Narasimhan, Balaji; Reilly, Peter J; Saunders, Kevin P; Shanks, Jacqueline V
2006-01-01
We have developed a series of upper undergraduate/graduate lecture and laboratory courses on biotechnological topics to supplement existing biochemical engineering, bioseparations, and biomedical engineering lecture courses. The laboratory courses are based on problem-based learning techniques, featuring two- and three-person teams, journaling, and performance rubrics for guidance and assessment. Participants initially have found them to be difficult, since they had little experience with problem-based learning. To increase enrollment, we are combining the laboratory courses into 2-credit groupings and allowing students to substitute one of them for the second of our 2-credit chemical engineering unit operations laboratory courses.
An Industrial Engineering Approach to Cost Containment of Pharmacy Education
Bottenberg, Michelle; Chase, Marilea; Chesnut, Renae; Clarke, Cheryl; Schott, Kathryn; Torry, Ronald; Welty, Tim
2015-01-01
A 2-semester project explored employing teams of fourth-year industrial engineering students to optimize some of our academic management processes. Results included significant cost savings and increases in efficiency, effectiveness, and student and faculty satisfaction. While we did not adopt all of the students’ recommendations, we did learn some important lessons. For example, an initial investment of time in developing a mutually clear understanding of the problems, constraints, and goals maximizes the value of industrial engineering analysis and recommendations. Overall, industrial engineering was a valuable tool for optimizing certain academic management processes. PMID:26839421
A new model for graduate education and innovation in medical technology.
Yazdi, Youseph; Acharya, Soumyadipta
2013-09-01
We describe a new model of graduate education in bioengineering innovation and design- a year long Master's degree program that educates engineers in the process of healthcare technology innovation for both advanced and low-resource global markets. Students are trained in an iterative "Spiral Innovation" approach that ensures early, staged, and repeated examination of all key elements of a successful medical device. This includes clinical immersion based problem identification and assessment (at Johns Hopkins Medicine and abroad), team based concept and business model development, and project planning based on iterative technical and business plan de-risking. The experiential, project based learning process is closely supported by several core courses in business, design, and engineering. Students in the program work on two team based projects, one focused on addressing healthcare needs in advanced markets and a second focused on low-resource settings. The program recently completed its fourth year of existence, and has graduated 61 students, who have continued on to industry or startups (one half), additional graduate education, or medical school (one third), or our own Global Health Innovation Fellowships. Over the 4 years, the program has sponsored 10 global health teams and 14 domestic/advanced market medtech teams, and launched 5 startups, of which 4 are still active. Projects have attracted over US$2.5M in follow-on awards and grants, that are supporting the continued development of over a dozen projects.
NASA Technical Reports Server (NTRS)
Cowen, Benjamin
2011-01-01
Simulations are essential for engineering design. These virtual realities provide characteristic data to scientists and engineers in order to understand the details and complications of the desired mission. A standard development simulation package known as Trick is used in developing a source code to model a component (federate in HLA terms). The runtime executive is integrated into an HLA based distributed simulation. TrickHLA is used to extend a Trick simulation for a federation execution, develop a source code for communication between federates, as well as foster data input and output. The project incorporates international cooperation along with team collaboration. Interactions among federates occur throughout the simulation, thereby relying on simulation interoperability. Communication through the semester went on between participants to figure out how to create this data exchange. The NASA intern team is designing a Lunar Rover federate and a Lunar Shuttle federate. The Lunar Rover federate supports transportation across the lunar surface and is essential for fostering interactions with other federates on the lunar surface (Lunar Shuttle, Lunar Base Supply Depot and Mobile ISRU Plant) as well as transporting materials to the desired locations. The Lunar Shuttle federate transports materials to and from lunar orbit. Materials that it takes to the supply depot include fuel and cargo necessary to continue moon-base operations. This project analyzes modeling and simulation technologies as well as simulation interoperability. Each team from participating universities will work on and engineer their own federate(s) to participate in the SISO Spring 2011 Workshop SIW Smackdown in Boston, Massachusetts. This paper will focus on the Lunar Rover federate.
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…
2000-03-10
The Hero Team (278) robot, named Hero, is repaired in a Kennedy Space Center research and development machine shop. The team of Edgewater High School students was co-sponsored by NASA Kennedy Space Center and Honeywell. 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
2000-03-10
The Hero Team (278) robot, named Hero, is repaired in a Kennedy Space Center research and development machine shop. The team of Edgewater High School students was co-sponsored by NASA Kennedy Space Center and Honeywell. 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
2000-03-10
The Hero Team (278) robot, named Hero, is repaired in a Kennedy Space Center research and development machine shop. The team of Edgewater High School students was co-sponsored by NASA Kennedy Space Center and Honeywell. 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
WATER TREATMENT AND EDUCATION IN VILLAHERMOSA, MEXICO
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...
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>
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.
A Capstone Course on Agile Software Development Using Scrum
ERIC Educational Resources Information Center
Mahnic, V.
2012-01-01
In this paper, an undergraduate capstone course in software engineering is described that not only exposes students to agile software development, but also makes it possible to observe the behavior of developers using Scrum for the first time. The course requires students to work as Scrum Teams, responsible for the implementation of a set of user…
NASA Space Environments Technical Discipline Team Space Weather Activities
NASA Astrophysics Data System (ADS)
Minow, J. I.; Nicholas, A. C.; Parker, L. N.; Xapsos, M.; Walker, P. W.; Stauffer, C.
2017-12-01
The Space Environment Technical Discipline Team (TDT) is a technical organization led by NASA's Technical Fellow for Space Environments that supports NASA's Office of the Chief Engineer through the NASA Engineering and Safety Center. The Space Environments TDT conducts independent technical assessments related to the space environment and space weather impacts on spacecraft for NASA programs and provides technical expertise to NASA management and programs where required. This presentation will highlight the status of applied space weather activities within the Space Environment TDT that support development of operational space weather applications and a better understanding of the impacts of space weather on space systems. We will first discuss a tool that has been developed for evaluating space weather launch constraints that are used to protect launch vehicles from hazardous space weather. We then describe an effort to better characterize three-dimensional radiation transport for CubeSat spacecraft and processing of micro-dosimeter data from the International Space Station which the team plans to make available to the space science community. Finally, we will conclude with a quick description of an effort to maintain access to the real-time solar wind data provided by the Advanced Composition Explorer satellite at the Sun-Earth L1 point.
ORNL engineering design and construction reengineering report
DOE Office of Scientific and Technical Information (OSTI.GOV)
McNeese, L.E.
1998-01-01
A team composed of individuals representing research and development (R and D) divisions, infrastructure support organizations, and Department of Energy (DOE)-Oak Ridge Operations was chartered to reengineer the engineering, design, and construction (ED and C) process at Oak Ridge National Laboratory (ORNL). The team recognized that ED and C needs of both R and D customers and the ORNL infrastructure program have to be met to maintain a viable and competitive national laboratory. Their goal was to identify and recommend implementable best-in-class ED and C processes that will efficiently and cost-effectively support the ORNL R and D staff by beingmore » responsive to their programmatic and infrastructure needs. The team conducted process mapping of current and potential ED and C approaches, developed idealized versions of ED and C processes, and identified potential barriers to an efficient ED and C process. Eight subteams were assigned to gather information and to evaluate the significance of potential barriers through benchmarking, surveys, interviews, and reviews of key topical areas in order to determine whether the perceived barriers were real and important and whether they resulted from laws or regulations over which ORNL has no control.« less
Distributed Planning and Control for Teams of Cooperating Mobile Robots
DOE Office of Scientific and Technical Information (OSTI.GOV)
Parker, L.E.
2004-06-15
This CRADA project involved the cooperative research of investigators in ORNL's Center for Engineering Science Advanced Research (CESAR) with researchers at Caterpillar, Inc. The subject of the research was the development of cooperative control strategies for autonomous vehicles performing applications of interest to Caterpillar customers. The project involved three Phases of research, conducted over the time period of November 1998 through December 2001. This project led to the successful development of several technologies and demonstrations in realistic simulation that illustrated the effectiveness of the control approaches for distributed planning and cooperation in multi-robot teams.
Fabrics Protect Sensitive Skin from UV Rays
NASA Technical Reports Server (NTRS)
2009-01-01
Late Johnson Space Center engineer Dr. Robert Dotts headed a team to develop cool suits for children suffering from life-threatening sun sensitivities. Dotts hoped to develop ultraviolet-blocking technology in a fabric that -- unlike in a bulky space suit -- could remain comfortable, light, and breathable in the sun and heat. The team worked with SPF 4 US LLC (SPF) of Madison, Wisconsin to design ultraviolet-blocking cool suits, which protect sun-sensitive patients and enable them to experience life outdoors safely. Using knowledge gained during the NASA collaboration, SPF created an entire line of ultraviolet-blocking apparel.
Efficacy Evaluation of Current and Future Naval Mine Warfare Neutralization Method
2016-12-01
Distribution is unlimited. EFFICACY EVALUATION OF CURRENT AND FUTURE NAVAL MINE WARFARE NEUTRALIZATION METHOD by Team MIW Cohort SE311-152O...EFFICACY EVALUATION OF CURRENT AND FUTURE NAVAL MINE WARFARE NEUTRALIZATION METHOD 5. FUNDING NUMBERS 6. AUTHOR (S) Team MIW, Systems Engineering...NEUTRALIZATION METHOD Team MIW, Systems Engineering Cohort SE311-152O Submitted in partial fulfillment of the requirements for the degrees of
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.
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.
Research on Building Education and Workforce Capacity in Systems Engineering
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
SE Capstone Project: Building Systems Engineering Education and Workforce Capacity
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
Evaluation and Validation (E&V) Team Public Report. Volume 5
1990-10-31
aspects, software engineering practices, etc. The E&V requirements which are developed will be used to guide the E&V technical effort. The currently...interoperability of Ada software engineering environment tools and data. The scope of the CAIS-A includes the functionality affecting transportability that is...requirement that they be CAIS conforming tools or data. That is, for example numerous CIVC data exist on special purpose software currently available
CrossTalk: The Journal of Defense Software Engineering. Volume 18, Number 9
2005-09-01
2004. 12. Humphrey , Watts . Introduction to the Personal Software Process SM. Addison- Wesley 1997. 13. Humphrey , Watts . Introduction to the Team...Personal Software ProcessSM (PSPSM)is a software development process orig- inated by Watts Humphrey at the Software Engineering Institute (SEI) in the...meets its commitments and bring a sense of control and predictability into an apparently chaotic project.u References 1. Humphrey , Watts . Coaching
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.
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.
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
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.
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
NASA Technical Reports Server (NTRS)
Boyles, Charles; Eledui, Emory; Gasser, Ben; Johnson, Josh; Long, Jay " Ben"
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.
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.
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.
NASA Technical Reports Server (NTRS)
Henderson, A. J., Jr.
2001-01-01
FIRST is the acronym of For Inspiration and Recognition of Science and Technology. FIRST is a 501.C.3 non-profit organization whose mission is to generate an interest in science and engineering among today's young adults and youth. This mission is accomplished through a robot competition held annually in the spring of each year. NASAs Marshall Space Flight Center, Education Programs Department, awarded a grant to Lee High School, the sole engineering magnet school in Huntsville, Alabama. MSFC awarded the grant in hopes of fulfilling its goal of giving back invaluable resources to its community and engineers, as well as educating tomorrow's work force in the high-tech area of science and technology. Marshall engineers, Lee High School students and teachers, and a host of other volunteers and parents officially initiated this robot design process and competitive strategic game plan. The FIRST Robotics Competition is a national engineering contest, which immerses high school students in the exciting world of science and engineering. Teaming with engineers from government agencies, businesses, and universities enables the students to learn about the engineering profession. The students and engineers have six weeks to work together to brainstorm, design, procure, construct, and test their robot. The team then competes in a spirited, 'no-holds barred' tournament, complete with referees, other FIRST-designed robots, cheerleaders, and time clocks. The partnerships developed between schools, government agencies, businesses, and universities provide an exchange of resources and talent that build cooperation and expose students to new and rewarding career options. The result is a fun, exciting, and stimulating environment in which all participants discover the important connections between classroom experiences and real-world applications. This paper will highlight the story, engineering development, and evolutionary design of Xtraktor, the rookie robot, a manufacturing marvel and engineering achievement.
NASA Technical Reports Server (NTRS)
Barley, Bryan; Newhouse, Marilyn
2012-01-01
In the development of complex spacecraft missions, project management authority is usually extended hierarchically from NASA's highest agency levels down to the implementing institution's project team level, through both the center and the program. In parallel with management authority, NASA utilizes a complementary, but independent, hierarchy of technical authority (TA) that extends from the agency level to the project, again, through both the center and the program. The chief engineers (CEs) who serve in this technical authority capacity oversee and report on the technical status and ensure sound engineering practices, controls, and management of the projects and programs. At the lowest level, implementing institutions assign project CEs to technically engage projects, lead development teams, and ensure sound technical principles, processes, and issue resolution. At the middle level, programs and centers independently use CEs to ensure the technical success of their projects and programs. At the agency level, NASA's mission directorate CEs maintain technical cognizance over every program and project in their directorate and advise directorate management on the technical, cost, schedule, and programmatic health of each. As part of this vertically-extended CE team, a program level CE manages a continually varying balance between penetration depth and breadth across his or her assigned missions. Teamwork issues and information integration become critical for management at all levels to ensure value-added use of both the synergy available between CEs at the various agency levels, and the independence of the technical authority at each organization.
Teaching Scientific and Technical French at Napier College in Scotland.
ERIC Educational Resources Information Center
Mitchell, Evelyne
Scotland's vocationally-oriented Napier College was funded by the French Government to develop language courses for scientists and engineers. The courses developed have been intensive and extensive, based on work started by a team of French scientists focusing on the language, concepts, and ways of thinking common to the scientific community.…
ERIC Educational Resources Information Center
Sankar, Chetan S.; Kawulich, Barbara; Clayton, Howard; Raju, P. K.
2010-01-01
A literature review identifies a partial list of leadership skills to include developing higher-order cognitive skills, team working skills, positive attitude, and ability to transfer these skills to future environment. This paper discusses the results of research conducted on the use of multiple instructional methodologies in two different…
Code of Federal Regulations, 2010 CFR
2010-07-01
... utilize an interdisciplinary team with leadership by planning, and participation from engineering, design.... Subsequent aspects of planning, development, and management for the specific project will be directed to... management plans for each specific water resource project, including at least one public meeting. The...
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.
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.
Building inclusive engineering identities: implications for changing engineering culture
NASA Astrophysics Data System (ADS)
Atadero, Rebecca A.; Paguyo, Christina H.; Rambo-Hernandez, Karen E.; Henderson, Heather L.
2018-05-01
Ongoing efforts to broaden the participation of women and people of colour in engineering degree programmes and careers have had limited success. This paper describes a different approach to broadening participation that seeks to work with all students and develop inclusive engineering identities. Researchers worked with the instructors of two first-year engineering courses to integrate curriculum activities designed to promote the formation of engineering identities and build an appreciation for how diversity and inclusion strengthen engineering practice. Multilevel modelling results indicated positive effects of the intervention on appreciation for diversity but no effects on engineering identity, and qualitative results indicated students learned the most about diversity not through one of the intervention activities, but through team projects in the courses. We also describe lessons learned in how to teach engineering students about diversity in ways that are relevant to engineering.
Best practices for team-based assistive technology design courses.
Goldberg, Mary R; Pearlman, Jonathan L
2013-09-01
Team-based design courses focused on products for people with disabilities have become relatively common, in part because of training grants such as the NSF Research to Aid Persons with Disabilities course grants. An output from these courses is an annual description of courses and projects but has yet to be complied into a "best practices guide," though it could be helpful for instructors. To meet this need, we conducted a study to generate best practices for assistive technology product development courses and how to use these courses to teach students the fundamentals of innovation. A full list of recommendations is comprised in the manuscript and include identifying a client through a reliable clinical partner; allowing for transparency between the instructors, the client, and the team(s); establishing multi-disciplinary teams; using a process-oriented vs. solution-oriented product development model; using a project management software to facilitate and archive communication and outputs; facilitating client interaction through frequent communication; seeking to develop professional role confidence to inspire students' commitment to engineering and (where applicable) rehabilitation field; publishing student designs on repositories; incorporating both formal and informal education opportunities related to design; and encouraging students to submit their designs to local or national entrepreneurship competitions.
DOE Office of Scientific and Technical Information (OSTI.GOV)
No, author
2013-09-29
The primary goal of this project was to speed the development of one of the first commercially available, OEM-produced plug-in hybrid electric vehicles (PHEV). The performance of the PHEV was expected to double the fuel economy of the conventional hybrid version. This vehicle program incorporated a number of advanced technologies, including advanced lithium-ion battery packs and an E85-capable flex-fuel engine. The project developed, fully integrated, and validated plug-in specific systems and controls by using GM’s Global Vehicle Development Process (GVDP) for production vehicles. Engineering Development related activities included the build of mule vehicles and integration vehicles for Phases I &more » II of the project. Performance data for these vehicles was shared with the U.S. Department of Energy (DOE). The deployment of many of these vehicles was restricted to internal use at GM sites or restricted to assigned GM drivers. Phase III of the project captured the first half or Alpha phase of the Engineering tasks for the development of a new thermal management design for a second generation battery module. The project spanned five years. It included six on-site technical reviews with representatives from the DOE. One unique aspect of the GM/DOE collaborative project was the involvement of the DOE throughout the OEM vehicle development process. The DOE gained an understanding of how an OEM develops vehicle efficiency and FE performance, while balancing many other vehicle performance attributes to provide customers well balanced and fuel efficient vehicles that are exciting to drive. Many vehicle content and performance trade-offs were encountered throughout the vehicle development process to achieve product cost and performance targets for both the OEM and end customer. The project team completed two sets of PHEV development vehicles with fully integrated PHEV systems. Over 50 development vehicles were built and operated for over 180,000 development miles. The team also completed four GM engineering development Buy-Off rides/milestones. The project included numerous engineering vehicle and systems development trips including extreme hot, cold and altitude exposure. The final fuel economy performance demonstrated met the objectives of the PHEV collaborative GM/DOE project. Charge depletion fuel economy of twice that of the non-PHEV model was demonstrated. The project team also designed, developed and tested a high voltage battery module concept that appears to be feasible from a manufacturability, cost and performance standpoint. The project provided important product development and knowledge as well as technological learnings and advancements that include multiple U.S. patent applications.« less
Use of activity theory-based need finding for biomedical device development.
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.
Kalman Filter for Calibrating a Telescope Focal Plane
NASA Technical Reports Server (NTRS)
Kang, Bryan; Bayard, David
2006-01-01
The instrument-pointing frame (IPF) Kalman filter, and an algorithm that implements this filter, have been devised for calibrating the focal plane of a telescope. As used here, calibration signifies, more specifically, a combination of measurements and calculations directed toward ensuring accuracy in aiming the telescope and determining the locations of objects imaged in various arrays of photodetectors in instruments located on the focal plane. The IPF Kalman filter was originally intended for application to a spaceborne infrared astronomical telescope, but can also be applied to other spaceborne and ground-based telescopes. In the traditional approach to calibration of a telescope, (1) one team of experts concentrates on estimating parameters (e.g., pointing alignments and gyroscope drifts) that are classified as being of primarily an engineering nature, (2) another team of experts concentrates on estimating calibration parameters (e.g., plate scales and optical distortions) that are classified as being primarily of a scientific nature, and (3) the two teams repeatedly exchange data in an iterative process in which each team refines its estimates with the help of the data provided by the other team. This iterative process is inefficient and uneconomical because it is time-consuming and entails the maintenance of two survey teams and the development of computer programs specific to the requirements of each team. Moreover, theoretical analysis reveals that the engineering/ science iterative approach is not optimal in that it does not yield the best estimates of focal-plane parameters and, depending on the application, may not even enable convergence toward a set of estimates.
NASA Astrophysics Data System (ADS)
Liu, Yucheng
2017-11-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 the most important course component and critical assessment tool, from which problem-solving skills as well as employability skills of the ME students can be fully developed. Hands-on experiences in finite element analysis (FEA) modelling and simulation were also added into the renovated curriculum to promote the application of FEA on engineering design and assessment. Evaluation of the renovated course was conducted using two instruments and the results have shown that the course made the ME senior students more prepared for their future career and a win-win model was created between the industry partner and the ME programme through it. Impact of the renovated syllabus on Accreditation Board for Engineering Technology goals was discussed. Based on the current progress, a more substantial change is being planned to further improve the effectiveness and practicability of this design course. The renovated course was started to offer to the ME senior students at Mississippi State University.
Operations planning and analysis handbook for NASA/MSFC phase B development projects
NASA Technical Reports Server (NTRS)
Batson, Robert C.
1986-01-01
Current operations planning and analysis practices on NASA/MSFC Phase B projects were investigated with the objectives of (1) formalizing these practices into a handbook and (2) suggesting improvements. The study focused on how Science and Engineering (S&E) Operational Personnel support Program Development (PD) Task Teams. The intimate relationship between systems engineering and operations analysis was examined. Methods identified for use by operations analysts during Phase B include functional analysis, interface analysis methods to calculate/allocate such criteria as reliability, Maintainability, and operations and support cost.
The Cooperate Assistive Teamwork Environment for Software Description Languages.
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.
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.
NASA Astrophysics Data System (ADS)
Chou, L.; Howell, S. M.; Bhattaru, S.; Blalock, J. J.; Bouchard, M.; Brueshaber, S.; Cusson, S.; Eggl, S.; Jawin, E.; Marcus, M.; Miller, K.; Rizzo, M.; Smith, H. B.; Steakley, K.; Thomas, N. H.; Thompson, M.; Trent, K.; Ugelow, M.; Budney, C. J.; Mitchell, K. L.
2017-12-01
The NASA Planetary Science Summer Seminar (PSSS), sponsored by the Jet Propulsion Laboratory (JPL), offers advanced graduate students and recent doctoral graduates the unique opportunity to develop a robotic planetary exploration mission that answers NASA's Science Mission Directorate's Announcement of Opportunity for the New Frontiers Program. Preceded by a series of 10 weekly webinars, the seminar is an intensive one-week exercise at JPL, where students work directly with JPL's project design team "TeamX" on the process behind developing mission concepts through concurrent engineering, project design sessions, instrument selection, science traceability matrix development, and risks and cost management. The 2017 NASA PSSS team included 18 participants from various U.S. institutions with a diverse background in science and engineering. We proposed a Centaur Reconnaissance Mission, named CAMILLA, designed to investigate the geologic state, surface evolution, composition, and ring systems through a flyby and impact of Chariklo. Centaurs are defined as minor planets with semi-major axis that lies between Jupiter and Neptune's orbit. Chariklo is both the largest Centaur and the only known minor planet with rings. CAMILLA was designed to address high priority cross-cutting themes defined in National Research Council's Vision and Voyages for Planetary Science in the Decade 2013-2022. At the end of the seminar, a final presentation was given by the participants to a review board of JPL scientists and engineers as well as NASA headquarters executives. The feedback received on the strengths and weaknesses of our proposal provided a rich and valuable learning experience in how to design a successful NASA planetary exploration mission and generate a successful New Frontiers proposal. The NASA PSSS is an educational experience that trains the next generation of NASA's planetary explorers by bridging the gap between scientists and engineers, allowing for participants to learn how to design a mission and build a spacecraft in a collaborative and fast-pace environment.
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.
A NOVEL PROCESS FOR BIOLOGICAL NITROGEN REMOVAL FROM DAIRY WASTEWATER IN CONSTRUCTED WETLANDS
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...
ERIC Educational Resources Information Center
Brown-Turner, Jasmine
2017-01-01
Edutainment refers to curriculum and instruction designed with a clear educational purpose, including multi-faceted virtual learning game design. Tools such as the Jacob's Ladder pre-production design tactic have been developed to ensure that voices of both engineers and educators are heard. However, it is unclear how development team members…
X-33 Reusable Launch Vehicle Demonstrator, Spaceport and Range
NASA Technical Reports Server (NTRS)
Letchworth, Gary F.
2011-01-01
The X-33 was a suborbital reusable spaceplane demonstrator, in development from 1996 to early 2001. The intent of the demonstrator was to lower the risk of building and operating a full-scale reusable vehicle fleet. Reusable spaceplanes offered the potential to lower the cost of access to space by an order of magnitude, compared with conventional expendable launch vehicles. Although a cryogenic tank failure during testing ultimately led to the end of the effort, the X-33 team celebrated many successes during the development. This paper summarizes some of the accomplishments and milestones of this X-vehicle program, from the perspective of an engineer who was a member of the team throughout the development. X-33 Program accomplishments include rapid, flight hardware design, subsystem testing and fabrication, aerospike engine development and testing, Flight Operations Center and Operations Control Center ground systems design and construction, rapid Environmental Impact Statement NEPA process approval, Range development and flight plan approval for test flights, and full-scale system concept design and refinement. Lessons from the X-33 Program may have potential application to new RLV and other aerospace systems being developed a decade later.
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).
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
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.
2000-03-10
The Hero Team (278) gets some help from a Kennedy Space Center research and development machine shop in repairing their robot, named Hero. The team of Edgewater High School students was co-sponsored by NASA Kennedy Space Center and Honeywell. 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
Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report
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
The development of a tool to predict team performance.
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.
Spaceflight Safety on the North Coast of America
NASA Technical Reports Server (NTRS)
Ciancone, Michael L.; Havenhill, Maria T.; Terlep, Judith A.
1996-01-01
Spaceflight Safety (SFS) engineers at NASA Lewis Research Center (LeRC) are responsible for evaluating the microgravity fluids and combustion experiments, payloads and facilities developed at NASA LeRC which are manifested for spaceflight on the Space Shuttle, the Russian space station Mir, and/or the International Space Station (ISS). An ongoing activity at NASA LeRC is the comprehensive training of its SFS engineers through the creation and use of safety tools and processes. Teams of SFS engineers worked on the development of an Internet website (containing a spaceflight safety knowledge database and electronic templates of safety products) and the establishment of a technical peer review process (known as the Safety Assurance for Lewis Spaceflight Activities (SALSA) review).
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.
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 ...
An Assessment of Team Development at the Air Force Flight Dynamics Laboratory.
1979-09-01
criterion variables: employee job satisfaction; job motivation; absenteeism ; five factor dimensions of organizational climate; and for Scientists and...Engineers (S and Es), three productivity factors. All variables except absenteeism were measured with a questionnaire. Absenteeism data was obtained from
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 Roles of Implicit Understanding of Engineering Ethics in Student Teams' Discussion.
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.
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.
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.
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
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.
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.
NASA Astrophysics Data System (ADS)
Egger, A. E.; Baldassari, C.; Bruckner, M. Z.; Iverson, E. A.; Manduca, C. A.; Mcconnell, D. A.; Steer, D. N.
2013-12-01
InTeGrate is NSF's STEP Center in the geosciences. A major goal of the project is to develop curricula that will increase the geoscience literacy of all students such that they are better positioned to make sustainable decisions in their lives and as part of the broader society. This population includes the large majority of students that do not major in the geosciences, those historically under-represented in the geosciences, and future K-12 teachers. To achieve this goal, we established a model for the development of curricular materials that draws on the distributed expertise of the undergraduate teaching community. Our model seeks proposals from across the higher education community for courses and modules that meet InTeGrate's overarching goals. From these proposals, we select teams of 3-5 instructors from three or more different institutions (and institution types) and pair them with assessment and web experts. Their communication and development process is supported by a robust, web-based content management system (CMS). Over two years, this team develops materials that explicitly address a geoscience-related societal challenge, build interdisciplinary problem-solving skills, make use of real geoscience data, and incorporate geoscientific and systems thinking. Materials are reviewed with the InTeGrate design rubric and then tested by the authors in their own courses, where student learning is assessed. Results are reviewed by the authors and our assessment team to guide revisions. Several student audiences are targeted: students in general education and introductory geoscience courses, pre-service K-12 teachers, students in other science and engineering majors, as well as those in the humanities and social sciences. Curriculum development team members from beyond the geosciences are critical to producing materials that can be adopted for all of these audiences, and we have been successful in engaging faculty from biology, economics, engineering, sociology, Spanish, and other disciplines. In its first year, InTeGrate engaged 20 individuals from 17 different institutions on materials development teams. During interviews and responses to open-ended survey questions, first-year team members provided feedback about the challenges and successes of the model. Several described that the materials design rubric was a useful tool in guiding their work and pushed them in directions they may not have otherwise gone. Most responded that working as part of a team with members from different institutions created numerous challenges, but was ultimately beneficial in sharing ideas and resulted in a better product. Other key components to model success are the development of resources by the web experts to support use of the CMS and frequent feedback from the assessment team. All feedback was used to refine the model for the second year, during which 56 additional authors have begun to develop materials. By engaging this broad and diverse community in innovative curriculum development, we anticipate widespread adoption of InTeGrate materials.
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…
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.
NASA Astrophysics Data System (ADS)
Guzzomi, Andrew L.; Male, Sally A.; Miller, Karol
2017-05-01
Engineering educators should motivate and support students in developing not only technical competence but also professional competence including commitment to excellence. We developed an authentic assessment to improve students' understanding of the importance of 'perfection' in engineering - whereby 50% good enough will not be acceptable in industry. Subsequently we aimed to motivate them to practise performing at their best when they practice engineering. Students in a third-year mechanical and mechatronic engineering unit completed a team design project designed with authentic assessment features to replicate industry expectations and a novel marking scheme to encourage the pursuit of excellence. We report mixed responses from students. Students' ratings of their levels of effort on this assessment indicate that many perceived a positive influence on their effort. However, students' comments included several that were consistent with students experiencing the assessment as alienating.
NASA Technical Reports Server (NTRS)
Scarffe, V. A.
2002-01-01
NASA is focusing on small, low-cost spacecraft for both planetary and earth science missions. Deep Space 1 (DS1) was the first mission to be launched by the NMP. The New Millennium Project (NMP) is designed to develop and test new technology that can be used on future science missions with lower cost and risk. The NMP is finding ways to reduce cost not only in development, but also in operations. DS 1 was approved for an extended mission, but the budget was not large, so the project began looking into part time team members shared with other projects. DS1 launched on October 24, 1998, in it's primary mission it successfully tested twelve new technologies. The extended mission started September 18, 1999 and ran through the encounter with Comet Borrelly on September 22,2001. The Flight Control Team (FCT) was one team that needed to use part time or multi mission people. Circumstances led to a situation where for the few months before the Borrelly encounter in September of 2001 DSl had no certified full time Flight Control Engineers also known as Aces. This paper examines how DS 1 utilized cross-project support including the communication between different projects, and the how the tools used by the Flight Control Engineer fit into cross-project support.
Recent development in blast performance of fiber-reinforced concrete
NASA Astrophysics Data System (ADS)
Hajek, R.; Foglar, M.; Kohoutkova, A.
2017-09-01
The paper presents an overview of the recent development in blast performance of fiber reinforced concrete. The paper builds on more than ten years’ history of the research in this field by the team of the Department of Concrete and Masonry Structures of the Faculty of Civil Engineering of the Czech Technical University in Prague.
Civilian First Responder Decontamination Equipment Characteristics Survey Results
2010-01-01
EQUIPMENT CHARACTERISTICS SURVEY RESULTS Scott Kooistra Shawn Bowen John Walther PROGRAM INTEGRATION DIRECTORATE Michael B. DeZearn ENGINEERING...COVERED (From - To) Mar 2007-Feb 2008 4. TITLE AND SUBTITLE Civilian First Responder Decontamination Equipment Characteristics Survey Results 5a...Department of Homeland Security/National Institute of Standards and Technology (DHS/NIST) Standards Development Team to develop a survey to
STUDY AND DEVELOPMENT OF SHOP-CENTERED TEAM TEACHING FOR POTENTIAL HIGH SCHOOL DROP-OUTS.
ERIC Educational Resources Information Center
ODELL, WILLIAM R.
A RATIONALE AND PROCEDURE FOR THE EFFECTIVE VOCATIONAL EDUCATION OF LOW ACHIEVING HIGH SCHOOL STUDENTS WAS DEVELOPED FROM AN ANALYSIS OF 13 HIGH SCHOOL PROGRAMS IN 10 SAN FRANCISCO BAY AREA SCHOOL SYSTEMS WHERE THE RICHMOND PRE-ENGINEERING TECHNOLOGY PROGRAM WAS UNDER OPERATION. EXPERIMENTAL EFFORTS WERE MADE TO ESTABLISH SHOP-CENTERED TEAM…
NASA Astrophysics Data System (ADS)
Goncher, Andrea M.
thResearch on engineering design is a core area of concern within engineering education, and a fundamental understanding of how engineering students approach and undertake design is necessary in order to develop effective design models and pedagogies. This dissertation contributes to scholarship on engineering design by addressing a critical, but as yet underexplored, problem: how does the context in which students design shape their design practices? Using a qualitative study comprising of video data of design sessions, focus group interviews with students, and archives of their design work, this research explored how design decisions and actions are shaped by context, specifically the context of higher education. To develop a theoretical explanation for observed behavior, this study used the nested structuration. framework proposed by Perlow, Gittell, & Katz (2004). This framework explicated how teamwork is shaped by mutually reinforcing relationships at the individual, organizational, and institutional levels. I appropriated this framework to look specifically at how engineering students working on a course-related design project identify constraints that guide their design and how these constraints emerge as students interact while working on the project. I first identified and characterized the parameters associated with the design project from the student perspective and then, through multi-case studies of four design teams, I looked at the role these parameters play in student design practices. This qualitative investigation of first-year engineering student design teams revealed mutual and interconnected relationships between students and the organizations and institutions that they are a part of. In addition to contributing to research on engineering design, this work provides guidelines and practices to help design educators develop more effective design projects by incorporating constraints that enable effective design and learning. Moreover, I found that when appropriated in the context of higher education, multiple sublevels existed within nested structuration's organizational context and included course-level and project-level factors. The implications of this research can be used to improve the design of engineering course projects as well as the design of research efforts related to design in engineering education.
2001-04-26
The first NASA Dropping In a Microgravity Environment (DIME) student competition pilot project came to a conclusion at the Glenn Research Center in April 2001. The competition involved high-school student teams who developed the concept for a microgravity experiment and prepared an experiment proposal. The two student teams - COSI Academy, sponsored by the Columbus Center of Science and Industry, and another team from Cincinnati, Ohio's Sycamore High School, designed a microgravity experiment, fabricated the experimental apparatus, and visited NASA Glenn to operate their experiment in the 2.2 Second Drop Tower. Here, students are briefed by NASA engineer Daniel Dietrich at the top of the drop tower. This image is from a digital still camera; higher resolution is not available.
Issues in Developing a Normative Descriptive Model for Dyadic Decision Making
NASA Technical Reports Server (NTRS)
Serfaty, D.; Kleinman, D. L.
1984-01-01
Most research in modelling human information processing and decision making has been devoted to the case of the single human operator. In the present effort, concepts from the fields of organizational behavior, engineering psychology, team theory and mathematical modelling are merged in an attempt to consider first the case of two cooperating decisionmakers (the Dyad) in a multi-task environment. Rooted in the well-known Dynamic Decision Model (DDM), the normative descriptive approach brings basic cognitive and psychophysical characteristics inherent to human behavior into a team theoretic analytic framework. An experimental paradigm, involving teams in dynamic decision making tasks, is designed to produce the data with which to build the theoretical model.
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
Spaceport Command and Control System Support Software Development
NASA Technical Reports Server (NTRS)
Brunotte, Leonard
2016-01-01
The Spaceport Command and Control System (SCCS) is a project developed and used by NASA at Kennedy Space Center in order to control and monitor the Space Launch System (SLS) at the time of its launch. One integral subteam under SCCS is the one assigned to the development of a data set building application to be used both on the launch pad and in the Launch Control Center (LCC) at the time of launch. This web application was developed in Ruby on Rails, a web framework using the Ruby object-oriented programming language, by a 15 - employee team (approx.). Because this application is such a huge undertaking with many facets and iterations, there were a few areas in which work could be more easily organized and expedited. As an intern working with this team, I was charged with the task of writing web applications that fulfilled this need, creating a virtual and highly customizable whiteboard in order to allow engineers to keep track of build iterations and their status. Additionally, I developed a knowledge capture web application wherein any engineer or contractor within SCCS could ask a question, answer an existing question, or leave a comment on any question or answer, similar to Stack Overflow.
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.
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. .
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.
* 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
NASA Technical Reports Server (NTRS)
Simmons, J.; Erlich, D.; Shockey, D.
2009-01-01
A team consisting of Arizona State University, Honeywell Engines, Systems & Services, the National Aeronautics and Space Administration Glenn Research Center, and SRI International collaborated to develop computational models and verification testing for designing and evaluating turbine engine fan blade fabric containment structures. This research was conducted under the Federal Aviation Administration Airworthiness Assurance Center of Excellence and was sponsored by the Aircraft Catastrophic Failure Prevention Program. The research was directed toward improving the modeling of a turbine engine fabric containment structure for an engine blade-out containment demonstration test required for certification of aircraft engines. The research conducted in Phase II began a new level of capability to design and develop fan blade containment systems for turbine engines. Significant progress was made in three areas: (1) further development of the ballistic fabric model to increase confidence and robustness in the material models for the Kevlar(TradeName) and Zylon(TradeName) material models developed in Phase I, (2) the capability was improved for finite element modeling of multiple layers of fabric using multiple layers of shell elements, and (3) large-scale simulations were performed. This report concentrates on the material model development and simulations of the impact tests.
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...
Improving safety of aircraft engines: a consortium approach
NASA Astrophysics Data System (ADS)
Brasche, Lisa J. H.
1996-11-01
With over seven million departures per year, air transportation has become not a luxury, but a standard mode of transportation for the United States. A critical aspect of modern air transport is the jet engine, a complex engineered component that has enabled the rapid travel to which we have all become accustomed. One of the enabling technologies for safe air travel is nondestructive evaluation, or NDE, which includes various inspection techniques used to assess the health or integrity of a structure, component, or material. The Engine Titanium Consortium (ETC) was established in 1993 to respond to recommendations made by the Federal Aviation Administration (FAA) Titanium Rotating Components Review Team (TRCRT) for improvements in inspection of engine titanium. Several recent accomplishments of the ETC are detailed in this paper. The objective of the Engine Titanium Consortium is to provide the FAAand the manufacturers with reliable and costeffective new methods and/or improvements in mature methods for detecting cracks, inclusions, and imperfections in titanium. The consortium consists of a team of researchers from academia and industry-namely, Iowa State University, Allied Signal Propulsion Engines, General Electric Aircraft Engines, and Pratt & Whitney Engines-who work together to develop program priorities, organize a program plan, conduct the research, and implement the solutions. The true advantage of the consortium approach is that it brings together the research talents of academia and the engineering talents of industry to tackle a technology-base problem. In bringing industrial competitors together, the consortium ensures that the research results, which have safety implications and result from FAA funds, are shared and become part of the public domain.
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.
Air Force Civil Engineer, Volume 16, Number 2, 2008
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
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.
Athena: Providing Insight into the History of the Universe
NASA Technical Reports Server (NTRS)
Murphy, Gloria A.
2010-01-01
The American Institute for Aeronautics and Astronautics has provided a Request for Proposal which calls for a manned mission to a Near-Earth Object. It is the goal of Team COLBERT to respond to their request by providing a reusable system that can be implemented as a solid stepping stone for future manned trips to Mars and beyond. Despite Team COLBERT consisting of only students in Aerospace Engineering, in order to achieve this feat, the team must employ the use of Systems Engineering. Tools and processes from Systems Engineering will provide quantitative and semi-quantitative tools for making design decisions and evaluating items such as budgets and schedules. This paper will provide an in-depth look at some of the Systems Engineering processes employed and will step through the design process of a Human Asteroid Exploration System.
Ares V: Progress Toward Unprecedented Heavy Lift
NASA Technical Reports Server (NTRS)
Sumrall, Phil
2010-01-01
Ares V represents the vehicle that will again make possible human exploration beyond low Earth orbit. The Ares V is part of NASA s Constellation Program architecture developed to support the International Space Station (ISS), establish a permanent human presence on the Moon, and explore it to an extent far greater than was possible with the Apollo Program. Ares V will carry the lunar lander to orbit where it will join the Orion crew spacecraft, launched by the smaller Ares I launch vehicle. Then the Ares V upper stage will send the Orion and lander to the Moon. Ares V is also intended to launch automated cargo landers to the Moon. The Ares vehicles are designed to employ the proven technologies and experience from the Space Shuttle, Delta IV, and earlier U.S. programs, as well as sharing common components where feasible. The Ares V is in an early stage of concept development. However, commonality allows it to benefit from development work already under way on the Ares I, including the first stage booster, and upper stage, J-2X upper stage engine. This paper will discuss progress to date on the Ares V and its potential for freeing payload designers from current mass and volume constraints. Progress includes development progress on Ares I elements that will be shared by the two launch vehicles. The Ares I first stage recently completed a successful test firing of Development Motor 1 (DM-1). The J-2X engine is proceeding with manufacturing of components for the first development engines that will be used for testing. Several component-level tests have been completed or are under way that will help verify designs and confirm solutions to design challenges. The Ares V Earth departure stage will benefit from the Ares I upper stage development, including design, manufacturing, and materials testing. NASA is also working with government and industry to collect data on flights and testing of the operational RS-68 engine and potential upgrades. The Ares V team continues to evaluate technical options, vehicle configurations, and operations concepts for the Ares V. The team recently completed a Fall Face-to-Face meeting that served as a stepping-stone to the Systems Requirements Review (SRR). This four-day meeting served as an information exchange for the various teams at several NASA field centers and supporting contractors.
Alpbach Summer School - a unique learning experience
NASA Astrophysics Data System (ADS)
Kern, K.; Aulinas, J.; Clifford, D.; Krejci, D.; Topham, R.
2011-12-01
The Alpbach Summer School is a ten-day program that provides a unique opportunity for young european science and engineering students, both undergraduate and graduate, to learn how to approach the entire design process of a space mission. The theme of the 2010 Summer School was "New Space Missions to Understand Climate Change", a current, challenging, very broad and complex topic. The program was established more than 35 years ago and is organised in two interrelated parts: a series of lectures held by renowned experts in the field (in the case of this specific year, climate change and space engineering experts) that provides a technical and scientific background for the workshops that follow, the core of the Summer School. For the workshops the students are split into four international, interdisciplinary teams of about 15 students. In 2010 every team had to complete a number of tasks, four in total: (1) identify climate change research gaps and design a space mission that has not yet been flown or proposed, (2) define the science objectives and requirements of the mission, (3) design a spacecraft that meets the mission requirements, which includes spacecraft design and construction, payload definition, orbit calculations, but also the satellite launch, operation and mission costs and (4) write up a short mission proposal and present the results to an expert review panel. Achieving these tasks in only a few days in a multicultural, interdisciplinary team represents a major challenge for all participants and provides an excellent practical learning experience. Over the course of the program, students do not just learn facts about climate change and space engineering, but scientists also learn from engineers and engineers from scientists. The participants have to deepen their knowledge in an often unfamiliar field, develop organisational and team-work skills and work under pressure. Moreover, teams are supported by team and roving tutors and get the opportunity to meet and learn from international experts. This presentation will provide an overview of the Alpbach Summer School program from a student's perspective. The different stages of this unique and enriching experience will be covered. Special attention will be paid to the workshops, which, as mentioned above, are the core of the Alpbach Summer School. During these intense workshops, participants work towards the proposed goals resulting in the design proposal of a space mission. The Alpbach Summer School is organised by FFG and co-sponsored by ESA, ISSI and the national space authorities of ESA member and cooperating states.
Garitte, B.; Nguyen, T. S.; Barnichon, J. D.; ...
2017-05-09
Coupled thermal–hydrological–mechanical (THM) processes in the near field of deep geological repositories can influence several safety features of the engineered and geological barriers. Among those features are: the possibility of damage in the host rock, the time for re-saturation of the bentonite, and the perturbations in the hydraulic regime in both the rock and engineered seals. Within the international cooperative code-validation project DECOVALEX-2015, eight research teams developed models to simulate an in situ heater experiment, called HE-D, in Opalinus Clay at the Mont Terri Underground Research Laboratory in Switzerland. The models were developed from the theory of poroelasticity in ordermore » to simulate the coupled THM processes that prevailed during the experiment and thereby to characterize the in situ THM properties of Opalinus Clay. The modelling results for the evolution of temperature, pore water pressure, and deformation at different points are consistent among the research teams and compare favourably with the experimental data in terms of trends and absolute values. The models were able to reproduce the main physical processes of the experiment. In particular, most teams simulated temperature and thermally induced pore water pressure well, including spatial variations caused by inherent anisotropy due to bedding.« less
DOE Office of Scientific and Technical Information (OSTI.GOV)
Garitte, B.; Nguyen, T. S.; Barnichon, J. D.
Coupled thermal–hydrological–mechanical (THM) processes in the near field of deep geological repositories can influence several safety features of the engineered and geological barriers. Among those features are: the possibility of damage in the host rock, the time for re-saturation of the bentonite, and the perturbations in the hydraulic regime in both the rock and engineered seals. Within the international cooperative code-validation project DECOVALEX-2015, eight research teams developed models to simulate an in situ heater experiment, called HE-D, in Opalinus Clay at the Mont Terri Underground Research Laboratory in Switzerland. The models were developed from the theory of poroelasticity in ordermore » to simulate the coupled THM processes that prevailed during the experiment and thereby to characterize the in situ THM properties of Opalinus Clay. The modelling results for the evolution of temperature, pore water pressure, and deformation at different points are consistent among the research teams and compare favourably with the experimental data in terms of trends and absolute values. The models were able to reproduce the main physical processes of the experiment. In particular, most teams simulated temperature and thermally induced pore water pressure well, including spatial variations caused by inherent anisotropy due to bedding.« less
The P-38 Lightning Aircraft: Lessons Learned for Future Weapon Systems Development
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
2009-11-01
quality control RCRA Resource Conservation and Recovery Act SAE Society for Automotive Engineers S-N stress vs number of cycles (fatigue curve...Automotive Engineers ( SAE ) Aerospace Materials Specifications (AMS): Figure 3. Air handler and dust filter installation at FRC-E. 8 - AMS 2447 was...developed with the assistance of the HCAT team and issued by SAE in 1998. It is now a widely used standard in the aerospace industry. - AMS 2448
Energy Optimization Assessment at U.S. Army Installations: West Point Military Academy, NY
2008-09-01
Richland, WA 99352 Roland Ziegler GEF Final Report Approved for public release; distribution is unlimited. Prepared for U.S. Army Corps of Engineers ...Executive Order 13123 and Energy Policy Act (EPAct) 2005. A team of researchers from the Engineer Research and Development Cen- ter, Construction...CEP #5 Longer use of the backpressure steam turbine by increasing the low pres- sure steam demand 1,200,000 0 $150,000 0 $— $— $150,000
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.
Role of strategic planning in engineering management
NASA Technical Reports Server (NTRS)
Krishen, Kumar
1993-01-01
Today, more than ever before, engineers are faced with uncertain and sometimes chaotic environments in which to function. The traditional roles of an engineer to design, develop, and streamline a manufacturing process for a product are still valued and relevant. However, the need for an engineer to participate in the process of identifying the product to be developed, the schedule and resources required, and the goal of satisfying the customer, has become paramount to achieving the success of the enterprise. When we include these endeavors in the functions of an engineer, management of 'engineering' takes on a new dimension. In this paper, the ramifications of the changing and increased functions of an engineer and consequent impacts on engineering management are explored. The basic principles which should be invoked in order to embrace the new environment for engineering management are outlined. The ultimate finding of this study is that the enterprise strategic plan should be developed in such a way as to allow engineering management to encompass the full spectrum of the responsibilities of engineers. A consequence of this is that the fundamental elements of the strategic process can best be implemented through a project team or group approach. The paper thus concentrates on three areas: evolving environment, strategic plan, and ways to achieve enterprise success.
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…
Group Development and Integration in a Cross-Disciplinary and Intercultural Research Team.
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.
Technology Applications Team: Applications of aerospace technology
NASA Technical Reports Server (NTRS)
1993-01-01
Highlights of the Research Triangle Institute (RTI) Applications Team activities over the past quarter are presented in Section 1.0. The Team's progress in fulfilling the requirements of the contract is summarized in Section 2.0. In addition to our market-driven approach to applications project development, RTI has placed increased effort on activities to commercialize technologies developed at NASA Centers. These Technology Commercialization efforts are summarized in Section 3.0. New problem statements prepared by the Team in the reporting period are presented in Section 4.0. The Team's transfer activities for ongoing projects with the NASA Centers are presented in Section 5.0. Section 6.0 summarizes the status of four add-on tasks. Travel for the reporting period is described in Section 7.0. The RTI Team staff and consultants and their project responsibilities are listed in Appendix A. The authors gratefully acknowledge the contributions of many individuals to the RTI Technology Applications Team program. The time and effort contributed by managers, engineers, and scientists throughout NASA were essential to program success. Most important to the program has been a productive working relationship with the NASA Field Center Technology Utilization (TU) Offices. The RTI Team continues to strive for improved effectiveness as a resource to these offices. Industry managers, technical staff, medical researchers, and clinicians have been cooperative and open in their participation. The RTI Team looks forward to continuing expansion of its interaction with U.S. industry to facilitate the transfer of aerospace technology to the private sector.
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.
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.
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.
Design definition of the Laser Atmospheric Wind Sounder (LAWS), phase 2. Volume 2: Final report
NASA Technical Reports Server (NTRS)
Wilson, D. J.
1992-01-01
Lockheed personnel, along with team member subcontractors and consultants, have performed a preliminary design for the LAWS Instrument. Breadboarding and testing of a LAWS class laser have also been performed. These efforts have demonstrated that LAWS is a feasible Instrument and can be developed with existing state-of-the-art technology. Only a commitment to fund the instrument development and deployment is required to place LAWS in orbit and obtain the anticipated science and operational forecasting benefits. The LAWS Science Team was selected in 1988-89 as were the competing LAWS phase 1/2 contractor teams. The LAWS Science Team developed requirements for the LAWS Instrument, and the NASA/LAWS project office defined launch vehicle and platform design constraints. From these requirements and constraints, the lockheed team developed LAWS Instrument concepts and configurations. A system designed to meet these requirements and constraints is outlined. The LAWS primary subsystem and interfaces - laser, optical, and receiver/processor - required to assemble a lidar are identified. Also identified are the support subsystems required for the lidar to function from space: structures and mechanical, thermal, electrical, and command and data management. The Lockheed team has developed a preliminary design of a LAWS Instrument System consisting of these subsystems and interfaces which will meet the requirements and objectives of the Science Team. This final report provides a summary of the systems engineering analyses and trades of the LAWS. Summaries of the configuration, preliminary designs of the subsystems, testing recommendations, and performance analysis are presented. Environmental considerations associated with deployment of LAWS are discussed. Finally, the successful LAWS laser breadboard effort is discussed along with the requirements and test results.
The U.S. Army Corps of Engineers (USACE) in Stability Operations
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
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 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.
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.
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.
Building international experiences into an engineering curriculum - a design project-based approach
NASA Astrophysics Data System (ADS)
Maldonado, Victor; Castillo, Luciano; Carbajal, Gerardo; Hajela, Prabhat
2014-07-01
This paper is a descriptive account of how short-term international and multicultural experiences can be integrated into early design experiences in an aerospace engineering curriculum. Such approaches are considered as important not only in fostering a student's interest in the engineering curriculum, but also exposing them to a multicultural setting that they are likely to encounter in their professional careers. In the broader sense, this programme is described as a model that can be duplicated in other engineering disciplines as a first-year experience. In this study, undergraduate students from Rensselaer Polytechnic Institute (RPI) and Universidad del Turabo (UT) in Puerto Rico collaborated on a substantial design project consisting of designing, fabricating, and flight-testing radio-controlled model aircraft as a capstone experience in a semester-long course on Fundamentals of Flight. The two-week long experience in Puerto Rico was organised into academic and cultural components designed with the following objectives: (i) to integrate students in a multicultural team-based academic and social environment, (ii) to practise team-building skills and develop students' critical thinking and analytical skills, and finally (iii) to excite students about their engineering major through practical applications of aeronautics and help them decide if it is a right fit for them.
NASA Technical Reports Server (NTRS)
Ott, Melanie N.; Switzer, Robert; Chuska, Richard; LaRocca, Frank; Thomas, William Joe; Macmurphy, Shawn
2008-01-01
The NASA Goddard Fiber Optics Team in the Electrical Engineering Division of the Applied Engineering and Technology Directorate, designed, developed and integrated the space flight optical fiber array hardware for the Lunar Reconnaissance Orbiter (LRO). The two new assemblies that were designed and manufacturing at GSFC for the LRO exist in configurations that are unique in the world for the application of ranging and LIDAR. Described here is an account of the journey and the lessons learned from design to integration for the Lunar Orbiter Laser Altimeter and the Laser Ranging Application on the LRO.
Preliminary summary of the ETF conceptual studies
NASA Technical Reports Server (NTRS)
Seikel, G. R.; Bercaw, R. W.; Pearson, C. V.; Owens, W. R.
1978-01-01
Power plant studies have shown the attractiveness of MHD topped steam power plants for baseload utility applications. To realize these advantages, a three-phase development program was initiated. In the first phase, the engineering data and experience were developed for the design and construction of a pilot plant, the Engineering Test Facility (ETF). Results of the ETF studies are reviewed. These three parallel independent studies were conducted by industrial teams led by the AVCO Everett Research Laboratory, the General Electric Corporation, and the Westinghouse Corporation. A preliminary analysis and the status of the critical evaluation of these results are presented.
A Brief Survey of the Team Software ProcessSM (TSPSM)
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
Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering - Phase 2
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
Engineering and agronomy aspects of a long-term precision agriculture field experiment
USDA-ARS?s Scientific Manuscript database
Much research has been conducted on specific precision agriculture tools and implementation strategies, but little has been reported on long-term evaluation of integrated precision agriculture field experiments. In 2004 our research team developed and initiated a multi-faceted “precision agriculture...
Capabilities of the Materials Contamination Team at Marshall Space Flight Center
NASA Technical Reports Server (NTRS)
Burns, Howard; Albyn, Keith; Edwards, David; Boothe, Richard; Finchum, Charles; Finckenor, Miria
2003-01-01
The Materials Contamination Team at the Marshall Space Flight Center (MSFC) has been recognized for its contributions supporting the National Aeronautics and Space Administration (NASA) spacecraft development programs. These programs include the Reusable Solid Rocket Motor (RSRM), Chandra X-Ray Observatory, and the International Space Station (ISS). The Environmental Effects Group, with the Materials Contamination Team and the Space Environmental Effects Team has been an integral part of NASA's success by the testing, evaluation, and qualification of materials, hardware, and processes. This paper focuses on the capabilities of the Materials Contamination Team. The Materials Contamination Team's realm of responsibility includes establishing contamination control during all phases of hardware development, including design, manufacturing, assembly, test, transportation, launch site processing, on-orbit exposure, return, and refurbishment. The team continues its mission of reducing the risk of equipment failure due to molecular or particulate contamination. Contamination is a concern in the Space Shuttle with sensitive bond-lines and reactive fluid (liquid oxygen) compatibility as well as for spacecraft with sensitive optics, such as Hubble Space Telescope and Chandra X-ray Observatory. The Materials Contamination Team has a variety of facilities and instrumentation capable of contaminant detection, identification, and monitoring. The team addresses material applications dealing with environments, including production facilities, clean rooms, and on-orbit exposure. The optically stimulated electron emission (OSEE) system, the Ultraviolet (UV) fluorescence (UVF) surface contamination detection, and the Surface Optics Corporation 400 (SOC 400) portable hand-held Fourier Transform Infrared (FTIR) spectrometer are state-of-the-art tools for in-process molecular contamination detection. The team of engineers and technicians also develop contamination calibration standards and evaluate new surface cleanliness inspection technologies. The team utilizes facilities for on-orbit simulation testing of materials for outgassing and molecular film deposition characteristics in the presence of space environmental effects, such as Atomic Oxygen (AO) and UV radiation exposure. The Materials Contamination Team maintains databases for process materials as well as outgassing and optical compatibility test results for specific environments.
Team Based Engineering Design Thinking
ERIC Educational Resources Information Center
Mentzer, Nathan
2012-01-01
The objective of this research was to explore design thinking among teams of high school students. This objective is encompassed in the research question driving this inquiry: How do teams of high school students allocate time across stages of design? Design thinking on the professional level typically occurs in a team environment. Many…
33 CFR 385.21 - Quality control.
Code of Federal Regulations, 2012 CFR
2012-07-01
... will be produced by a Project Delivery Team. The quality control plan shall be included in the Project... Corps of Engineers and the non-Federal sponsor shall establish a Technical Review Team to conduct.... The members of the Technical Review Team shall be independent of the Project Delivery Team and the...
Team Based Engineering Design Thinking
ERIC Educational Resources Information Center
Mentzer, Nathan
2014-01-01
The objective of this research was to explore design thinking among teams of high school students. This objective was encompassed in the research question driving the inquiry: How do teams of high school students allocate time across stages of design? Design thinking on the professional level typically occurs in a team environment. Many…
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.
Engineering Technical Support Center Annual Report Fiscal ...
The United States Environmental Protection Agency (EPA or Agency) Office of Research and Development (ORD) created the Engineering Technical Support Center (ETSC) in 1987, one of several technical support centers created as part of the Technical Support Project (TSP). ETSC provides engineering expertise to Agency program and regional offices and remediation teams working at contaminated sites across the country. The ETSC is operated within ORD’s Land Remediation and Pollution Control Division (LRPCD) of the National Risk Management Research Laboratory (NRMRL) in Cincinnati, Ohio. The ETSC’s mission is to provide site-specific scientific and engineering technical support to Remedial Project Managers, On-Scene Coordinators, and other remediation personnel at contaminated sites. This allows local, regional, or national authorities to work more quickly, efficiently, and cost effectively, while also increasing the technical experience of the remediation team. Since its inception, the ETSC has supported countless projects across all EPA Regions in almost all states and territories. This report highlights significant projects the ETSC supported in fiscal year 2015 (FY15). These projects addressed an array of environmental scenarios, such as remote mining contamination, expansive landfill waste, cumulative impacts from multiple contamination sources, and persistent threats from abandoned industrial sites. Constructing and testing new and innovative treatment technol
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.
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.
Preparing technicians for engineering materials technology
NASA Technical Reports Server (NTRS)
Jacobs, James A.; Metzloff, Carlton H.
1990-01-01
A long held principle is that for every engineer and scientist there is a need for ten technicians to maximize the efficiency of the technology team for meeting needs of industry and government. Developing an adequate supply of technicians to meet the requirements of the materials related industry will be a challenge and difficult to accomplish. A variety of agencies feel the need and wish to support development of engineering materials technology programs. In a joint effort among Battelle Laboratories, the Department of Energy (DOE) and Northwest College and University Association for Science (NORCUS), the development of an engineering materials technology program for vocational programs and community colleges for the Pacific Northwest Region was recently completed. This effort has implications for a national model. The model Associate of Applied Science degree in Engineering Materials Technology shown provides a general structure. It purposely has course titles which need delimiting while also including a core of courses necessary to develop cognitive, affective and psychomotor skills with the underlining principles of math, science and technology so students have job entry skills, and so that students can learn about and adapt to evolving technology.
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.
ERIC Educational Resources Information Center
Pazos, Pilar; Micari, Marina; Light, Gregory
2010-01-01
Collaborative learning is being used extensively by educators at all levels. Peer-led team learning in a version of collaborative learning that has shown consistent success in science, technology, engineering and mathematics disciplines. Using a multi-phase research study we describe the development of an observation instrument that can be used to…
Design Skills and Prototyping for Defense Systems
2015-04-30
however, the utility of prototyping has had a demonstrably mixed record in defense acquisition. Some programs, such as the Manhattan Project , were...almost completely undefined. The first production reactors for the Manhattan Project suffered a near- catastrophic engineering design flaw stemming...architecture, as was seen in the F-117 and Manhattan Project development efforts. Architectural Prototyping Simply maintaining design teams or developing
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.
NASA Microgravity Science Competition for High-school-aged Student Teams
NASA Technical Reports Server (NTRS)
DeLombard, Richard; Stocker, Dennis; Hodanbosi, Carol; Baumann, Eric
2002-01-01
NASA participates in a wide variety of educational activities including competitive events. There are competitive events sponsored by NASA and student teams which are mentored by NASA centers. This participation by NASA in public forums serves to bring the excitement of aerospace science to students and educators. A new competition for highschool-aged student teams involving projects in microgravity has completed two pilot years and will have national eligibility for teams during the 2002-2003 school year. A team participating in the Dropping In a Microgravity Environment will research the field of microgravity, develop a hypothesis, and prepare a proposal for an experiment to be conducted in a microgravity drop tower facility. A team of NASA scientists and engineers will select the top proposals and those teams will then design and build their experiment apparatus. When the experiment apparatus are completed, team representatives will visit NASA Glenn in Cleveland, Ohio for operation of their facility and participate in workshops and center tours. Presented in this paper will be a description of DIME, an overview of the planning and execution of such a program, results from the first two pilot years, and a status of the first national competition.
NASA Astrophysics Data System (ADS)
Berthoud, L.; Gliddon, J.
2018-03-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 of engineering students from different disciplinary backgrounds and years. The students' perception of the usefulness of the tool were surveyed and the user contribution statistics and content categorisation were analysed for a case study wiki. Recommendations and lessons learned for the deployment of wikis are provided for interested academic staff from other institutions. Wikis were found to be of limited use to investigate levels of communication and collaboration in this study, but may be of interest in other contexts. Wikis were considered a potentially useful tool to track engagement for Capstone design projects in engineering subjects.
Empirical studies of design software: Implications for software engineering environments
NASA Technical Reports Server (NTRS)
Krasner, Herb
1988-01-01
The empirical studies team of MCC's Design Process Group conducted three studies in 1986-87 in order to gather data on professionals designing software systems in a range of situations. The first study (the Lift Experiment) used thinking aloud protocols in a controlled laboratory setting to study the cognitive processes of individual designers. The second study (the Object Server Project) involved the observation, videotaping, and data collection of a design team of a medium-sized development project over several months in order to study team dynamics. The third study (the Field Study) involved interviews with the personnel from 19 large development projects in the MCC shareholders in order to study how the process of design is affected by organizationl and project behavior. The focus of this report will be on key observations of design process (at several levels) and their implications for the design of environments.
Design study to simulate the development of a commercial freight transportation system
NASA Technical Reports Server (NTRS)
Batill, Stephen M.; Costello, Kevin; Pinkelman, Jim
1992-01-01
The Notre Dame Aerospace Engineering senior class was divided into six design teams. A request for proposals (RFP) asking for the design of a remotely piloted vehicle (RPV) was given to the class, and each design team was responsible for designing, developing, producing, and presenting an RPV concept. The RFP called for the design of commercial freight transport RPV. The RFP provided a description of a fictitious world called 'Aeroworld'. Aeroworld's characteristics were scaled to provide the same types of challenges for RPV design that the real world market provides for the design of commercial aircraft. Fuel efficiency, range and payload capabilities, production and maintenance costs, and profitability are a few of the challenges that were addressed in this course. Each design team completed their project over the course of a semester by designing and flight testing a prototype, freight-carrying remotely piloted vehicle.
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.
2003-02-05
KENNEDY SPACE CENTER, FLA. -- Members of the Recovery Management Team at KSC are at work in the Operations Support Building. They are 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. Seated around the table (clockwise from far left) are Chris Hasselbring, Landing Operations, USA (co-chair of the Response Management Team); Don Maxwell, Safety, United Space Alliance (USA); Russ DeLoach, chief, Shuttle Mission Assurance Branch, NASA; George Jacobs, Shuttle Engineering; Jeff Campbell, Shuttle Engineering; Denny Gagen, Landing Recovery Manager (second co-chair of the team); and Dave Rainer, Launch and Landing Operations. 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. .
2003-02-05
KENNEDY SPACE CENTER, FLA. - Two members of the Recovery Management Team at KSC are at work in the Operations Support Building. At left is Don Maxwell, Safety, United Space Alliance, and at right is Larry Ulmer, Safety, NASA. They are 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; and the two co-chairs of the Response Management Team, Denny Gagen, Landing Recovery Manager, and Chris Hasselbring, Landing Operations, USA. 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. .
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…
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…
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.
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.
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
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.