Engineering Lessons Learned and Systems Engineering Applications
NASA Technical Reports Server (NTRS)
Gill, Paul S.; Garcia, Danny; Vaughan, William W.
2005-01-01
Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.
Engineering Lessons Learned and Systems Engineering Applications
NASA Technical Reports Server (NTRS)
Gill, Paul S.; Garcia, Danny; Vaughan, William W.
2005-01-01
Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned and technical standards. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. Systems Engineering has been defined (EINIS-632) as "an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system people, product, and process solutions that satisfy customer needs". Designing reliable space-based systems has always been a goal for NASA, and many painful lessons have been learned along the way. One of the continuing functions of a system engineer is to compile development and operations "lessons learned" documents and ensure their integration into future systems development activities. They can produce insights and information for risk identification identification and characterization. on a new project. Lessons learned files from previous projects are especially valuable in risk
Safety and Mission Assurance for In-House Design Lessons Learned from Ares I Upper Stage
NASA Technical Reports Server (NTRS)
Anderson, Joel M.
2011-01-01
This viewgraph presentation identifies lessons learned in the course of the Ares I Upper Stage design and in-house development effort. The contents include: 1) Constellation Organization; 2) Upper Stage Organization; 3) Presentation Structure; 4) Lesson-Importance of Systems Engineering/Integration; 5) Lesson-Importance of Early S&MA Involvement; 6) Lesson-Importance of Appropriate Staffing Levels; 7) Lesson-Importance S&MA Team Deployment; 8) Lesson-Understanding of S&MA In-Line Engineering versus Assurance; 9) Lesson-Importance of Close Coordination between Supportability and Reliability/Maintainability; 10) Lesson-Importance of Engineering Data Systems; 11) Lesson-Importance of Early Development of Supporting Databases; 12) Lesson-Importance of Coordination with Safety Assessment/Review Panels; 13) Lesson-Implementation of Software Reliability; 14) Lesson-Implementation of S&MA Technical Authority/Chief S&MA Officer; 15) Lesson-Importance of S&MA Evaluation of Project Risks; 16) Lesson-Implementation of Critical Items List and Government Mandatory Inspections; 17) Lesson-Implementation of Critical Items List Mandatory Inspections; 18) Lesson-Implementation of Test Article Safety Analysis; and 19) Lesson-Importance of Procurement Quality.
Development of concept-based physiology lessons for biomedical engineering undergraduate students.
Nelson, Regina K; Chesler, Naomi C; Strang, Kevin T
2013-06-01
Physiology is a core requirement in the undergraduate biomedical engineering curriculum. In one or two introductory physiology courses, engineering students must learn physiology sufficiently to support learning in their subsequent engineering courses and careers. As preparation for future learning, physiology instruction centered on concepts may help engineering students to further develop their physiology and biomedical engineering knowledge. Following the Backward Design instructional model, a series of seven concept-based lessons was developed for undergraduate engineering students. These online lessons were created as prerequisite physiology training to prepare students to engage in a collaborative engineering challenge activity. This work is presented as an example of how to convert standard, organ system-based physiology content into concept-based content lessons.
Stationary Engineering. Science Manual--2.
ERIC Educational Resources Information Center
Frost, Harold J.; Steingress, Frederick M.
This second-year student manual contains 140 brief related science lessons applying science and math to trade activities in the field of stationary engineering. The lessons are organized into 16 units: (1) Introduction to Stationary Engineering, (2) Engineering Fundamentals, (3) Steam Boilers, (4) Boiler Fittings, (5) Boilerroom System, (6)…
Lessons Learned from Ares I Upper Stage Structures and Thermal Design
NASA Technical Reports Server (NTRS)
Ahmed, Rafiq
2012-01-01
The Ares 1 Upper Stage was part of the vehicle intended to succeed the Space Shuttle as the United States manned spaceflight vehicle. Although the Upper Stage project was cancelled, there were many lessons learned that are applicable to future vehicle design. Lessons learned that are briefly detailed in this Technical Memorandum are for specific technical areas such as tank design, common bulkhead design, thrust oscillation, control of flight and slosh loads, purge and hazardous gas system. In addition, lessons learned from a systems engineering and vehicle integration perspective are also included, such as computer aided design and engineering, scheduling, and data management. The need for detailed systems engineering in the early stages of a project is emphasized throughout this report. The intent is that future projects will be able to apply these lessons learned to keep costs down, schedules brief, and deliver products that perform to the expectations of their customers.
Test Planning Approach and Lessons
NASA Technical Reports Server (NTRS)
Parkinson, Douglas A.; Brown, Kendall K.
2004-01-01
As NASA began technology risk reduction activities and planning for the next generation launch vehicle under the Space Launch Initiative (SLI), now the Next Generation Launch Technology (NGLT) Program, a review of past large liquid rocket engine development programs was performed. The intent of the review was to identify any significant lessons from the development testing programs that could be applied to current and future engine development programs. Because the primary prototype engine in design at the time of this study was the Boeing-Rocketdyne RS-84, the study was slightly biased towards LOX/RP-1 liquid propellant engines. However, the significant lessons identified are universal. It is anticipated that these lessons will serve as a reference for test planning in the Engine Systems Group at Marshall Space Flight Center (MSFC). Towards the end of F-1 and J-2 engine development testing, NASA/MSFC asked Rocketdyne to review those test programs. The result was a document titled, Study to Accelerate Development by Test of a Rocket Engine (R-8099). The "intent (of this study) is to apply this thinking and learning to more efficiently develop rocket engines to high reliability with improved cost effectivenes" Additionally, several other engine programs were reviewed - such as SSME, NSTS, STME, MC-1, and RS-83- to support or refute the R-8099. R-8099 revealed two primary lessons for test planning, which were supported by the other engine development programs. First, engine development programs can benefit from arranging the test program for engine system testing as early as feasible. The best test for determining environments is at the system level, the closest to the operational flight environment. Secondly, the component testing, which tends to be elaborate, should instead be geared towards reducing risk to enable system test. Technical risk can be reduced at the component level, but the design can only be truly verified and validated after engine system testing.
Lessons Learned in Engineering
NASA Technical Reports Server (NTRS)
Blair, J. C.; Ryan, R. S.; Schutzenhofer, L. A.
2011-01-01
This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations.
Lessons learned from the Space Flyer Unit (SFU) mission.
Kuriki, Kyoichi; Ninomiya, Keiken; Takei, Mitsuru; Matsuoka, Shinobu
2002-11-01
The Space Flyer Unit (SFU) system and mission chronology are briefly introduced. Lessons learned from the SFU mission are categorized as programmatic and engineering lessons. In the programmatic category are dealt with both international and domestic collaborations. As for the engineering lessons safety design, orbital operation, in-flight anomaly, and post flight analyses are the major topics reviewed. c2002 Elsevier Science Ltd. All rights reserved.
From Bridges and Rockets, Lessons for Software Systems
NASA Technical Reports Server (NTRS)
Holloway, C. Michael
2004-01-01
Although differences exist between building software systems and building physical structures such as bridges and rockets, enough similarities exist that software engineers can learn lessons from failures in traditional engineering disciplines. This paper draws lessons from two well-known failures the collapse of the Tacoma Narrows Bridge in 1940 and the destruction of the space shuttle Challenger in 1986 and applies these lessons to software system development. The following specific applications are made: (1) the verification and validation of a software system should not be based on a single method, or a single style of methods; (2) the tendency to embrace the latest fad should be overcome; and (3) the introduction of software control into safety-critical systems should be done cautiously.
Lessons Learned in Engineering. Supplement
NASA Technical Reports Server (NTRS)
Blair, James C.; Ryan, Robert S.; Schultzenhofer, Luke A.
2011-01-01
This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations. The supplemental CD contains accompanying PowerPoint presentations.
Gemini Observatory base facility operations: systems engineering process and lessons learned
NASA Astrophysics Data System (ADS)
Serio, Andrew; Cordova, Martin; Arriagada, Gustavo; Adamson, Andy; Close, Madeline; Coulson, Dolores; Nitta, Atsuko; Nunez, Arturo
2016-08-01
Gemini North Observatory successfully began nighttime remote operations from the Hilo Base Facility control room in November 2015. The implementation of the Gemini North Base Facility Operations (BFO) products was a great learning experience for many of our employees, including the author of this paper, the BFO Systems Engineer. In this paper we focus on the tailored Systems Engineering processes used for the project, the various software tools used in project support, and finally discuss the lessons learned from the Gemini North implementation. This experience and the lessons learned will be used both to aid our implementation of the Gemini South BFO in 2016, and in future technical projects at Gemini Observatory.
ERIC Educational Resources Information Center
Texas A and M Univ., College Station. Vocational Instructional Services.
This course outline, the first volume of a two-volume set, consists of lesson plans for pre-employment laboratory training in general agricultural mechanics. Covered in the 12 lessons included in this volume are selecting tractors and engines, diagnosing engine conditions, servicing electrical systems, servicing cooling systems, servicing fuel and…
NASA Technical Reports Server (NTRS)
Oberhettinger, David
2011-01-01
A lessons learned system is a hallmark of a mature engineering organization A formal lessons learned process can help assure that valuable lessons get written and published, that they are well-written, and that the essential information is "infused" into institutional practice. Requires high-level institutional commitment, and everyone's participation in gathering, disseminating, and using the lessons
International Space Station Passive Thermal Control System Analysis, Top Ten Lessons-Learned
NASA Technical Reports Server (NTRS)
Iovine, John
2011-01-01
The International Space Station (ISS) has been on-orbit for over 10 years, and there have been numerous technical challenges along the way from design to assembly to on-orbit anomalies and repairs. The Passive Thermal Control System (PTCS) management team has been a key player in successfully dealing with these challenges. The PTCS team performs thermal analysis in support of design and verification, launch and assembly constraints, integration, sustaining engineering, failure response, and model validation. This analysis is a significant body of work and provides a unique opportunity to compile a wealth of real world engineering and analysis knowledge and the corresponding lessons-learned. The analysis lessons encompass the full life cycle of flight hardware from design to on-orbit performance and sustaining engineering. These lessons can provide significant insight for new projects and programs. Key areas to be presented include thermal model fidelity, verification methods, analysis uncertainty, and operations support.
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.
Cleared for Launch - Lessons Learned from the OSIRIS-REx System Requirements Verification Program
NASA Technical Reports Server (NTRS)
Stevens, Craig; Adams, Angela; Williams, Bradley; Goodloe, Colby
2017-01-01
Requirements verification of a large flight system is a challenge. It is especially challenging for engineers taking on their first role in space systems engineering. This paper describes our approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from developing systems engineers embroiled in this process. We begin with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including our implementation for managing the thousands of program and element level requirements and associated verification data. We discuss both successes and methods to improve the managing of this data across multiple organizational interfaces. Our approach to verifying system requirements at multiple levels of assembly is presented using examples from our work at instrument, spacecraft, and ground segment levels. We include a discussion of system end-to-end testing limitations and their impacts to the verification program. Finally, we describe lessons learned that are applicable to all emerging space systems engineers using our unique perspectives across multiple organizations of a large NASA program.
NASA Technical Reports Server (NTRS)
Dennehy, Cornelius J.; Labbe, Steve; Lebsock, Kenneth L.
2010-01-01
Within the broad aerospace community the importance of identifying, documenting and widely sharing lessons learned during system development, flight test, operational or research programs/projects is broadly acknowledged. Documenting and sharing lessons learned helps managers and engineers to minimize project risk and improve performance of their systems. Often significant lessons learned on a project fail to get captured even though they are well known 'tribal knowledge' amongst the project team members. The physical act of actually writing down and documenting these lessons learned for the next generation of NASA GN&C engineers fails to happen on some projects for various reasons. In this paper we will first review the importance of capturing lessons learned and then will discuss reasons why some lessons are not documented. A simple proven approach called 'Pause and Learn' will be highlighted as a proven low-impact method of organizational learning that could foster the timely capture of critical lessons learned. Lastly some examples of 'lost' GN&C lessons learned from the aeronautics, spacecraft and launch vehicle domains are briefly highlighted. In the context of this paper 'lost' refers to lessons that have not achieved broad visibility within the NASA-wide GN&C CoP because they are either undocumented, masked or poorly documented in the NASA Lessons Learned Information System (LLIS).
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.
NASA Technical Reports Server (NTRS)
Studor, George
2007-01-01
A viewgraph presentation on lessons learned from NASA Johnson Space Center's micro-wireless instrumentation is shown. The topics include: 1) Background, Rationale and Vision; 2) NASA JSC/Structural Engineering Approach & History; 3) Orbiter Wing Leading Edge Impact Detection System; 4) WLEIDS Confidence and Micro-WIS Lessons Learned; and 5) Current Projects and Recommendations.
Crafting usable knowledge for sustainable development.
Clark, William C; van Kerkhoff, Lorrae; Lebel, Louis; Gallopin, Gilberto C
2016-04-26
This paper distills core lessons about how researchers (scientists, engineers, planners, etc.) interested in promoting sustainable development can increase the likelihood of producing usable knowledge. We draw the lessons from both practical experience in diverse contexts around the world and from scholarly advances in understanding the relationships between science and society. Many of these lessons will be familiar to those with experience in crafting knowledge to support action for sustainable development. However, few are included in the formal training of researchers. As a result, when scientists and engineers first venture out of the laboratory or library with the goal of linking their knowledge with action, the outcome has often been ineffectiveness and disillusionment. We therefore articulate here a core set of lessons that we believe should become part of the basic training for researchers interested in crafting usable knowledge for sustainable development. These lessons entail at least four things researchers should know, and four things they should do. The knowing lessons involve understanding the coproduction relationships through which knowledge making and decision making shape one another in social-environmental systems. We highlight the lessons that emerge from examining those coproduction relationships through the ICAP lens, viewing them from the perspectives of Innovation systems, Complex systems, Adaptive systems, and Political systems. The doing lessons involve improving the capacity of the research community to put its understanding of coproduction into practice. We highlight steps through which researchers can help build capacities for stakeholder collaboration, social learning, knowledge governance, and researcher training.
Crafting usable knowledge for sustainable development
2016-01-01
This paper distills core lessons about how researchers (scientists, engineers, planners, etc.) interested in promoting sustainable development can increase the likelihood of producing usable knowledge. We draw the lessons from both practical experience in diverse contexts around the world and from scholarly advances in understanding the relationships between science and society. Many of these lessons will be familiar to those with experience in crafting knowledge to support action for sustainable development. However, few are included in the formal training of researchers. As a result, when scientists and engineers first venture out of the laboratory or library with the goal of linking their knowledge with action, the outcome has often been ineffectiveness and disillusionment. We therefore articulate here a core set of lessons that we believe should become part of the basic training for researchers interested in crafting usable knowledge for sustainable development. These lessons entail at least four things researchers should know, and four things they should do. The knowing lessons involve understanding the coproduction relationships through which knowledge making and decision making shape one another in social–environmental systems. We highlight the lessons that emerge from examining those coproduction relationships through the ICAP lens, viewing them from the perspectives of Innovation systems, Complex systems, Adaptive systems, and Political systems. The doing lessons involve improving the capacity of the research community to put its understanding of coproduction into practice. We highlight steps through which researchers can help build capacities for stakeholder collaboration, social learning, knowledge governance, and researcher training. PMID:27091979
Lessons Learned for Improving Spacecraft Ground Operations
NASA Technical Reports Server (NTRS)
Bell, Michael; Henderson, Gena; Stambolian, Damon
2013-01-01
NASA policy requires each Program or Project to develop a plan for how they will address Lessons Learned. Projects have the flexibility to determine how best to promote and implement lessons learned. A large project might budget for a lessons learned position to coordinate elicitation, documentation and archival of the project lessons. The lessons learned process crosses all NASA Centers and includes the contactor community. o The Office of The Chief Engineer at NASA Headquarters in Washington D.C., is the overall process owner, and field locations manage the local implementation. One tool used to transfer knowledge between program and projects is the Lessons Learned Information System (LLIS). Most lessons come from NASA in partnership with support contractors. A search for lessons that might impact a new design is often performed by a contractor team member. Knowledge is not found with only one person, one project team, or one organization. Sometimes, another project team, or person, knows something that can help your project or your task. Knowledge sharing is an everyday activity at the Kennedy Space Center through storytelling, Kennedy Engineering Academy presentations and through searching the Lessons Learned Information system. o Project teams search the lessons repository to ensure the best possible results are delivered. o The ideas from the past are not always directly applicable but usually spark new ideas and innovations. Teams have a great responsibility to collect and disseminate these lessons so that they are shared with future generations of space systems designers. o Leaders should set a goal for themselves to host a set numbers of lesson learned events each year and do more to promote multiple methods of lessons learned activities. o High performing employees are expected to share their lessons, however formal knowledge sharing presentation are not the norm for many employees.
ERIC Educational Resources Information Center
Peterman, Karen; Daugherty, Jenny L.; Custer, Rodney L.; Ross, Julia M.
2017-01-01
Science teachers are being called on to incorporate engineering practices into their classrooms. This study explores whether the Engineering-Infused Lesson Rubric, a new rubric designed to target best practices in engineering education, could be used to evaluate the extent to which engineering is infused into online science lessons. Eighty lessons…
2017-01-27
Mike Ciannilli, the Apollo, Challenger, Columbia Lessons Learned Program manager, welcomes participants to the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA’s Kennedy Space Center in Florida. The program's theme was "To There and Back Again." Guest panelists included Charlie Duke, former Apollo 16 astronaut and member of the Apollo 1 Emergency Egress Investigation Team; Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
System Re-engineering Project Executive Summary
1991-11-01
Management Information System (STAMIS) application. This project involved reverse engineering, evaluation of structured design and object-oriented design, and re- implementation of the system in Ada. This executive summary presents the approach to re-engineering the system, the lessons learned while going through the process, and issues to be considered in future tasks of this nature.... Computer-Aided Software Engineering (CASE), Distributed Software, Ada, COBOL, Systems Analysis, Systems Design, Life Cycle Development, Functional Decomposition, Object-Oriented
Flexible manufacturing of aircraft engine parts
NASA Astrophysics Data System (ADS)
Hassan, Ossama M.; Jenkins, Douglas M.
1992-06-01
GE Aircraft Engines, a major supplier of jet engines for commercial and military aircraft, has developed a fully integrated manufacturing facility to produce aircraft engine components in flexible manufacturing cells. This paper discusses many aspects of the implementation including process technologies, material handling, software control system architecture, socio-technical systems and lessons learned. Emphasis is placed on the appropriate use of automation in a flexible manufacturing system.
NASA Astrophysics Data System (ADS)
Peterman, Karen; Daugherty, Jenny L.; Custer, Rodney L.; Ross, Julia M.
2017-09-01
Science teachers are being called on to incorporate engineering practices into their classrooms. This study explores whether the Engineering-Infused Lesson Rubric, a new rubric designed to target best practices in engineering education, could be used to evaluate the extent to which engineering is infused into online science lessons. Eighty lessons were selected at random from three online repositories, and coded with the rubric. Overall results documented the strengths of existing lessons, as well as many components that teachers might strengthen. In addition, a subset of characteristics was found to distinguish lessons with the highest level of engineering infusion. Findings are discussed in relation to the potential of the rubric to help teachers use research evidence-informed practice generally, and in relation to the new content demands of the U.S. Next Generation Science Standards, in particular.
Defense Acquisitions: Addressing Incentives is Key to Further Reform Efforts
2014-04-30
championed sound management practices, such as realistic cost estimating, prototyping, and systems engineering . While some progress has been made...other reforms have championed sound management practices, such as realistic cost estimating, prototyping, and systems engineering . DOD’s declining...principles from disciplines such as systems engineering , as well as lessons learned and past reforms. The body of work we have done on benchmarking
Design for Safety - The Ares Launch Vehicles Paradigm Change
NASA Technical Reports Server (NTRS)
Safie, Fayssal M.; Maggio, Gaspare
2010-01-01
The lessons learned from the S&MA early involvement in the Ares I launch vehicle design phases proved that performing an in-line function jointly with engineering is critical for S&MA to have an effective role in supporting the system, element, and component design. These lessons learned were used to effectively support the Ares V conceptual design phase and planning for post conceptual design phases. The Top level Conceptual LOM assessment for Ares V performed by the S&MA community jointly with the engineering Advanced Concept Office (ACO) was influential in the final selection of the Ares V system configuration. Post conceptual phase, extensive reliability effort should be planned to support future Heavy Lift Launch Vehicles (HLLV) design. In-depth reliability analysis involving the design, manufacturing, and system engineering communities is critical to understand design and process uncertainties and system integrated failures.
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.
Lessons Learned from the Space Shuttle Engine Cutoff System (ECO) Anomalies
NASA Technical Reports Server (NTRS)
Martinez, Hugo E.; Welzyn, Ken
2011-01-01
The Space Shuttle Orbiter's main engine cutoff (ECO) system first failed ground checkout in April, 2005 during a first tanking test prior to Return-to-Flight. Despite significant troubleshooting and investigative efforts that followed, the root cause could not be found and intermittent anomalies continued to plague the Program. By implementing hardware upgrades, enhancing monitoring capability, and relaxing the launch rules, the Shuttle fleet was allowed to continue flying in spite of these unexplained failures. Root cause was finally determined following the launch attempts of STS-122 in December, 2007 when the anomalies repeated, which allowed drag-on instrumentation to pinpoint the fault (the ET feedthrough connector). The suspect hardware was removed and provided additional evidence towards root cause determination. Corrective action was implemented and the system has performed successfully since then. This white paper presents the lessons learned from the entire experience, beginning with the anomalies since Return-to-Flight through discovery and correction of the problem. To put these lessons in better perspective for the reader, an overview of the ECO system is presented first. Next, a chronological account of the failures and associated investigation activities is discussed. Root cause and corrective action are summarized, followed by the lessons learned.
Designing to Sample the Unknown: Lessons from OSIRIS-REx Project Systems Engineering
NASA Technical Reports Server (NTRS)
Everett, David; Mink, Ronald; Linn, Timothy; Wood, Joshua
2017-01-01
On September 8, 2016, the third NASA New Frontiers mission launched on an Atlas V 411. The Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) will rendezvous with asteroid Bennu in 2018, collect a sample in 2020, and return that sample to Earth in September 2023. The development team has overcome a number of challenges in order to design and build a system that will make contact with an unexplored, airless, low-gravity body. This paper will provide an overview of the mission, then focus in on the system-level challenges and some of the key system-level processes. Some of the lessons here are unique to the type of mission, like discussion of operating at a largely-unknown, low-gravity object. Other lessons, particularly from the build phase, have broad implications. The OSIRIS-REx risk management process was particularly effective in achieving an on-time and under-budget development effort. The systematic requirements management and verification and the system validation also helped identify numerous potential problems. The final assessment of the OSIRIS-REx performance will need to wait until the sample is returned in 2023, but this post-launch assessment will capture some of the key systems-engineering lessons from the development team.
Private Pilot Ground School Course. Instructor's Guide.
ERIC Educational Resources Information Center
Schlenker, Richard M.
This manual consists of 10 lesson plans for use by instructors teaching a private pilot ground school course. Addressed in the individual lesson plans are the following topics: aerodynamics and principles of flight, flight instruments and systems, operational publications, regulations, airplane operations, engine operations, radio communications,…
2017-01-27
Charlie Duke, former Apollo 16 astronaut and member of the Apollo 1 Emergency Egress Investigation Team, speaks to participants during the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA's Kennedy Space Center in Florida. The program's theme was "To There and Back Again." Other guest panelists included Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
2017-01-27
NASA Kennedy Space Center Director Bob Cabana, at left, moderates a panel discussion during the Apollo 1 Lessons Learned event in the Training Auditorium at NASA’s Kennedy Space Center in Florida. The theme of the presentation was "To There and Back Again." Answering questions are Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
System 80+{trademark} standard design incorporates radiation protection lessons learned
DOE Office of Scientific and Technical Information (OSTI.GOV)
Crom, T.D.; Naugle, C.L.; Turk, R.S.
1995-03-01
Many lessons have been learned from the current generation of nuclear plants in the area of radiation protection. The following paper will outline how the lessons learned have been incorporated into the design and operational philosophy of the System 80+{trademark} Standard Design currently under development by ABB Combustion Engineering (ABB-CE) with support from Duke Engineering and Services, Inc. and Stone and Webster Engineering Corporation in the Balance-of-Plant design. The System 80+{trademark} Standard Design is a complete nuclear power plant for national and international markets, designed in direct response to utility needs for the 1990`s, and scheduled for Nuclear Regulatory Commissionmore » (NRC) Design Certification under the new standardization rule (10 CFR Part 52). System 80+{trademark} is a natural extension of System 80{sup R} technology, an evolutionary change based on proven Nuclear Steam Supply System (NSSS) in operation at Palo Verde in Arizona and under construction at Yonggwang in the Republic of Korea. The System 80+{trademark} Containment and much of the Balance of Plant design is based upon Duke Power Company`s Cherokee Plant, which was partially constructed in the late 1970`s, but, was later canceled (due to rapid declined in electrical load growth). The System 80+{trademark} Standard Design meets the requirements given in the Electric Power Research Institute (EPRI) Advanced Light Water Reactor (ALWR) Requirements Document. One of these requirements is to limit the occupational exposure to 100 person-rem/yr. This paper illustrates how this goal can be achieved through the incorporation of lessons learned, innovative design, and the implementation of a common sense approach to operation and maintenances practices.« less
2017-01-27
Mike Ciannilli, at left, the Apollo, Challenger, Columbia Lessons Learned Program manager, presents a certificate to John Tribe, retired, Apollo 1 Reaction and Control System lead engineer, during the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA's Kennedy Space Center in Florida. The theme of the program was "To there and Back Again." The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
Human Systems Integration in Practice: Constellation Lessons Learned
NASA Technical Reports Server (NTRS)
Zumbado, Jennifer Rochlis
2012-01-01
NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.
Satellite-instrument system engineering best practices and lessons
NASA Astrophysics Data System (ADS)
Schueler, Carl F.
2009-08-01
This paper focuses on system engineering development issues driving satellite remote sensing instrumentation cost and schedule. A key best practice is early assessment of mission and instrumentation requirements priorities driving performance trades among major instrumentation measurements: Radiometry, spatial field of view and image quality, and spectral performance. Key lessons include attention to technology availability and applicability to prioritized requirements, care in applying heritage, approaching fixed-price and cost-plus contracts with appropriate attention to risk, and assessing design options with attention to customer preference as well as design performance, and development cost and schedule. A key element of success either in contract competition or execution is team experience. Perhaps the most crucial aspect of success, however, is thorough requirements analysis and flowdown to specifications driving design performance with sufficient parameter margin to allow for mistakes or oversights - the province of system engineering from design inception to development, test and delivery.
Breathing Life into Engineering: A Lesson Study Life Science Lesson
ERIC Educational Resources Information Center
Lawrence, Maria; Yang, Li-Ling; Briggs, May; Hession, Alicia; Koussa, Anita; Wagoner, Lisa
2016-01-01
A fifth grade life science lesson was implemented through a lesson study approach in two fifth grade classrooms. The research lesson was designed by a team of four elementary school teachers with the goal of emphasizing engineering practices consistent with the "Next Generation Science Standards" (NGSS) (Achieve Inc. 2013). The fifth…
Lessons learned for improving spacecraft ground operations
NASA Astrophysics Data System (ADS)
Bell, Michael; Stambolian, Damon; Henderson, Gena
NASA has a unique history in processing the Space Shuttle fleet for launches. Some of this experience has been captured in the NASA Lessons Learned Information System (LLIS). This tool provides a convenient way for design engineers to review lessons from the past to prevent problems from reoccurring and incorporate positive lessons in new designs. At the Kennedy Space Center, the LLIS is being used to design ground support equipment for the next generation of launch and crewed vehicles. This paper describes the LLIS process and offers some examples.
Lessons Learned for Improving Spacecraft Ground Operations
NASA Technical Reports Server (NTRS)
Bell, Michael A.; Stambolian, Damon B.; Henderson, Gena M.
2012-01-01
NASA has a unique history in processing the Space Shuttle fleet for launches. Some of this experience has been captured in the NASA Lessons Learned Information System (LLIS). This tool provides a convenient way for design engineers to review lessons from the past to prevent problems from reoccurring and incorporate positive lessons in new designs. At the Kennedy Space Center, the LLIS is being used to design ground support equipment for the next generation of launch and crewed vehicles. This paper describes the LLIS process and offers some examples.
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)
Safie, Fayssal M.; Messer, Bradley P.
2006-01-01
This paper presents lessons learned from the Space Shuttle return to flight experience and the importance of these lessons learned in the development of new the NASA Crew Launch Vehicle (CLV). Specifically, the paper discusses the relationship between process control and system risk, and the importance of process control in improving space vehicle flight safety. It uses the External Tank (ET) Thermal Protection System (TPS) experience and lessons learned from the redesign and process enhancement activities performed in preparation for Return to Flight after the Columbia accident. The paper also, discusses in some details, the Probabilistic engineering physics based risk assessment performed by the Shuttle program to evaluate the impact of TPS failure on system risk and the application of the methodology to the CLV.
ERIC Educational Resources Information Center
Montanes, Maria T.; Palomares, Antonio E.
2008-01-01
In this work we show how specific challenges related to sustainable development can be integrated into chemical engineering education by introducing an environmental management system in the laboratory where the students perform their experimental lessons. It is shown how the system has been developed and implemented in the laboratory, what role…
2017-01-27
Kennedy Space Center Director Bob Cabana welcomes participants to the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA’s Kennedy Space Center in Florida. The program's theme was "To There and Back Again." Guest panelists included Charlie Duke, former Apollo 16 astronaut and member of the Apollo 1 Emergency Egress Investigation Team; Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
Advances in CRISPR-Cas9 genome engineering: lessons learned from RNA interference
Barrangou, Rodolphe; Birmingham, Amanda; Wiemann, Stefan; Beijersbergen, Roderick L.; Hornung, Veit; Smith, Anja van Brabant
2015-01-01
The discovery that the machinery of the Clustered Regularly Interspaced Short Palindromic Repeats (CRISPR)-Cas9 bacterial immune system can be re-purposed to easily create deletions, insertions and replacements in the mammalian genome has revolutionized the field of genome engineering and re-invigorated the field of gene therapy. Many parallels have been drawn between the newly discovered CRISPR-Cas9 system and the RNA interference (RNAi) pathway in terms of their utility for understanding and interrogating gene function in mammalian cells. Given this similarity, the CRISPR-Cas9 field stands to benefit immensely from lessons learned during the development of RNAi technology. We examine how the history of RNAi can inform today's challenges in CRISPR-Cas9 genome engineering such as efficiency, specificity, high-throughput screening and delivery for in vivo and therapeutic applications. PMID:25800748
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.
ERIC Educational Resources Information Center
Manpower Administration (DOL), Washington, DC. Job Corps.
This self-study program for high-school level contains lessons on: Speed, Acceleration, and Velocity; Force, Mass, and Distance; Types of Motion and Rest; Electricity and Magnetism; Electrical, Magnetic, and Gravitational Fields; The Conservation and Conversion of Matter and Energy; Simple Machines and Work; Gas Laws; Principles of Heat Engines;…
Stationary Engineering. Science 2. Teachers Guide.
ERIC Educational Resources Information Center
Frost, Harold J.; Steingress, Frederick M.
This teachers guide to be used with the second-year student manual, "Stationary Engineering Science Manual--2," contains 140 lesson plans, corresponding to the lessons in the student manual. The lessons are brief and each involves concrete trade experiences where science is applied with 26 lessons also involving mathematical problems…
Orion Flight Test 1 Architecture: Observed Benefits of a Model Based Engineering Approach
NASA Technical Reports Server (NTRS)
Simpson, Kimberly A.; Sindiy, Oleg V.; McVittie, Thomas I.
2012-01-01
This paper details how a NASA-led team is using a model-based systems engineering approach to capture, analyze and communicate the end-to-end information system architecture supporting the first unmanned orbital flight of the Orion Multi-Purpose Crew Exploration Vehicle. Along with a brief overview of the approach and its products, the paper focuses on the observed program-level benefits, challenges, and lessons learned; all of which may be applied to improve system engineering tasks for characteristically similarly challenges
Introducing new technologies into Space Station subsystems
NASA Technical Reports Server (NTRS)
Wiskerchen, Michael J.; Mollakarimi, Cindy L.
1989-01-01
A new systems engineering technology has been developed and applied to Shuttle processing. The new engineering approach emphasizes the identification, quantitative assessment, and management of system performance and risk related to the dynamic nature of requirements, technology, and operational concepts. The Space Shuttle Tile Automation System is described as an example of the first application of the new engineering technology. Lessons learned from the Shuttle processing experience are examined, and concepts are presented which are applicable to the design and development of the Space Station Freedom.
Tailoring Systems Engineering for Rapid Acquisition
2014-03-27
center’s focus would be the collection of lessons learned and the dissemination of the basic knowledge to the members who are conducting rapid acquisition...dictates that they rarely do lessons learned . Adding in the turnover of personnel and they reported that they make the same mistakes over and over...weapon system program of record designated by the CSAF. This is where the interviewee heard the phrase “when skating on thin ice your best asset is
2017-01-27
John Tribe, retired, Apollo 1 Reaction and Control System lead engineer, answers questions during the Apollo 1 Lessons Learned event in the Training Auditorium at NASA’s Kennedy Space Center in Florida. The theme of the presentation was "To There and Back Again." The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
2017-01-27
Mike Ciannilli, the Apollo, Challenger, Columbia Lessons Learned Program manager, far right, is pictured with panelists from the Apollo 1 Lessons Learned event in the Training Auditorium at NASA's Kennedy Space Center in Florida. In the center, are Ernie Reyes, retired, former Apollo 1 senior operations manager; and John Tribe, retired, former Apollo 1 Reaction and Control System lead engineer. At far left is Zulie Cipo, the Apollo, Challenger, Columbia Lessons Learned Program event support team lead. The theme of the program was "To there and Back Again." The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
The Curiosity Mars Rover's Fault Protection Engine
NASA Technical Reports Server (NTRS)
Benowitz, Ed
2014-01-01
The Curiosity Rover, currently operating on Mars, contains flight software onboard to autonomously handle aspects of system fault protection. Over 1000 monitors and 39 responses are present in the flight software. Orchestrating these behaviors is the flight software's fault protection engine. In this paper, we discuss the engine's design, responsibilities, and present some lessons learned for future missions.
Optical Design and Engineering: Lessons Learned
NASA Technical Reports Server (NTRS)
Mouroulis, Pantazis
2005-01-01
This paper contains some recommendations for the optics curricula that seek to serve students intent on a career in optical engineering, as well as suggestions for the young professional embarking on such a career. It also illustrates the suggestions with some examples of actual optical systems.
The Value of Successful MBSE Adoption
NASA Technical Reports Server (NTRS)
Parrott, Edith
2016-01-01
The value of successful adoption of Model Based System Engineering (MBSE) practices is hard to quantify. Most engineers and project managers look at the success in terms of cost. But there are other ways to quantify the value of MBSE and the steps necessary to achieve adoption. The Glenn Research Center (GRC) has been doing Model-Based Engineering (design, structural, etc.) for years, but the system engineering side has not. Since 2010, GRC has been moving from documents centric to MBSE/SysML. Project adoption of MBSE has been slow, but is steadily increasing in both MBSE usage and complexity of generated products. Sharing of knowledge of lessons learned in the implementation of MBSE/SysML is key for others who want to be successful. Along with GRC's implementation, NASA is working hard to increase the successful implementation of MBSE across all the other centers by developing guidelines, templates and libraries for projects to utilize. This presentation will provide insight into recent GRC and NASA adoption efforts, lessons learned and best practices.
Cryptography and the Internet: lessons and challenges
DOE Office of Scientific and Technical Information (OSTI.GOV)
McCurley, K.S.
1996-12-31
The popularization of the Internet has brought fundamental changes to the world, because it allows a universal method of communication between computers. This carries enormous benefits with it, but also raises many security considerations. Cryptography is a fundamental technology used to provide security of computer networks, and there is currently a widespread engineering effort to incorporate cryptography into various aspects of the Internet. The system-level engineering required to provide security services for the Internet carries some important lessons for researchers whose study is focused on narrowly defined problems. It also offers challenges to the cryptographic research community by raising newmore » questions not adequately addressed by the existing body of knowledge. This paper attempts to summarize some of these lessons and challenges for the cryptographic research community.« less
NASA Workshop on Hybrid (Mixed-Actuator) Spacecraft Attitude Control
NASA Technical Reports Server (NTRS)
Dennehy, Cornelius J.; Kunz, Nans
2014-01-01
At the request of the Science Mission Directorate Chief Engineer, the NASA Technical Fellow for Guidance, Navigation & Control assembled and facilitated a workshop on Spacecraft Hybrid Attitude Control. This multi-Center, academic, and industry workshop, sponsored by the NASA Engineering and Safety Center (NESC), was held in April 2013 to unite nationwide experts to present and discuss the various innovative solutions, techniques, and lessons learned regarding the development and implementation of the various hybrid attitude control system solutions investigated or implemented. This report attempts to document these key lessons learned with the 16 findings and 9 NESC recommendations.
2017-01-27
Suzy Cunningham, with the Communication and Public Engagement Directorate, sings the National Anthem before the start of the Apollo 1 Lessons Learned presentation in the Training Auditorium at NASA’s Kennedy Space Center in Florida. The program's theme was "To There and Back Again." Guest panelists included Charlie Duke, former Apollo 16 astronaut and member of the Apollo 1 Emergency Egress Investigation Team; Ernie Reyes, retired, Apollo 1 senior operations engineer; and John Tribe, retired, Apollo 1 Reaction and Control System lead engineer. The event helped pay tribute to the Apollo 1 crew, Gus Grissom, Ed White II, and Roger Chaffee.
Overview of the Main Propulsion System for the NASA Ares I Upper Stage
NASA Technical Reports Server (NTRS)
Quinn, Jason E.; Swanson, Luke A.
2009-01-01
A functional overview of the Main Propulsion System (MPS) of the NASA Ares I Upper Stage is provided. In addition to a simple overview of the key MPS functions and design philosophies, major lessons learned are discussed. The intent is to provide a technical overview with enough detail to allow engineers outside of the MPS Integrated Product Team (IPT) to develop a rough understanding of MPS operations, components, design philosophy, and lessons learned.
Bringing Engineering Research Coupled With Art Into The K-12 Classroom
NASA Astrophysics Data System (ADS)
Cola, J.
2016-12-01
The Partnerships for Research, Innovation and Multi-Scale Engineering Program, a Research Experiences for K-12 Teachers at Georgia Institute of Technology demonstrates a successful program that blends the fine arts with engineering research. Teachers selected for the program improve their science and engineering content knowledge, as well as their understanding of how to use STEAM to increase student comprehension and engagement. Participants in the program designed Science, Technology, Engineering, Art, and Mathematics (STEAM)- based lessons based on faculty engineering research. Examples of some STEAM lessons created will be discussed along with lessons learned.
Additive Manufacturing Design Considerations for Liquid Engine Components
NASA Technical Reports Server (NTRS)
Whitten, Dave; Hissam, Andy; Baker, Kevin; Rice, Darron
2014-01-01
The Marshall Space Flight Center's Propulsion Systems Department has gained significant experience in the last year designing, building, and testing liquid engine components using additive manufacturing. The department has developed valve, duct, turbo-machinery, and combustion device components using this technology. Many valuable lessons were learned during this process. These lessons will be the focus of this presentation. We will present criteria for selecting part candidates for additive manufacturing. Some part characteristics are 'tailor made' for this process. Selecting the right parts for the process is the first step to maximizing productivity gains. We will also present specific lessons we learned about feature geometry that can and cannot be produced using additive manufacturing machines. Most liquid engine components were made using a two-step process. The base part was made using additive manufacturing and then traditional machining processes were used to produce the final part. The presentation will describe design accommodations needed to make the base part and lessons we learned about which features could be built directly and which require the final machine process. Tolerance capabilities, surface finish, and material thickness allowances will also be covered. Additive Manufacturing can produce internal passages that cannot be made using traditional approaches. It can also eliminate a significant amount of manpower by reducing part count and leveraging model-based design and analysis techniques. Information will be shared about performance enhancements and design efficiencies we experienced for certain categories of engine parts.
The role of failure/problems in engineering: A commentary of failures experienced - lessons learned
NASA Technical Reports Server (NTRS)
Ryan, R. S.
1992-01-01
The written version of a series of seminars given to several aerospace companies and three NASA centers are presented. The results are lessons learned through a study of the problems experienced in 35 years of engineering. The basic conclusion is that the primary cause of problems has not been mission technologies, as important as technology is, but the neglect of basic principles. Undergirding this is the lack of a systems focus from determining requirements through design, verification, and operations phases. Many of the concepts discussed are fundamental to total quality management (TQM) and can be used to augment this product enhanced philosophy. Fourteen principles are addressed with problems experienced and are used as examples. Included is a discussion of the implication of constraints, poorly defined requirements, and schedules. Design guidelines, lessons learned, and future tasks are listed. Two additional sections are included that deal with personal lessons learned and thoughts on future thrusts (TQM).
Systems Engineering Education Development(SEED)Case Study
NASA Technical Reports Server (NTRS)
Bagg, Thomas C., III; Brumfield, Mark D.; Jamison, Donald E.; Granata, Raymond L.; Casey, Carolyn A.
2003-01-01
The Systems Engineering Development Program (SEED) was initiated to help Goddard resolve a Systems Engineering skill shortage. The chronology of events and the experiences of the pilot program are outlined to describe the development of the present program. The program goals are included in order to give a focus on what the developers saw as the program drivers. Lessons learned from a pilot program were incorporated into the present program. This program is constantly learning from its past efforts and looks for continuous improvement. We list several future ideas for improvement and change.
Early Formulation Model-centric Engineering on Nasa's Europa Mission Concept Study
NASA Technical Reports Server (NTRS)
Bayer, Todd; Chung, Seung; Cole, Bjorn; Cooke, Brian; Dekens, Frank; Delp, Chris; Gontijo, I.; Lewis, Kari; Moshir, Mehrdad; Rasmussen, Robert;
2012-01-01
By leveraging the existing Model-Based Systems Engineering (MBSE) infrastructure at JPL and adding a modest investment, the Europa Mission Concept Study made striking advances in mission concept capture and analysis. This effort has reaffirmed the importance of architecting and successfully harnessed the synergistic relationship of system modeling to mission architecting. It clearly demonstrated that MBSE can provide greater agility than traditional systems engineering methods. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.
Lessons learned from the NEPTUNE power system, and other deep-sea adventures
NASA Astrophysics Data System (ADS)
Kirkham, Harold
2006-11-01
The development of underwater science systems presents some challenging technical issues. It seems that the best efforts of the engineers and scientists involved are sometimes inadequate, and projects that once seemed straightforward end up being late or over-budget, or cancelled. This paper will review some of the lessons that may be learned from the examples of three science projects in the deep ocean: the Deep Underwater Muon and Neutrino Detector neutrino detector, the H2O observatory, and the power system part of the NEPTUNE regional cabled observatory.
Review of Aircraft Engine Fan Noise Reduction
NASA Technical Reports Server (NTRS)
VanZante, Dale
2008-01-01
Aircraft turbofan engines incorporate multiple technologies to enhance performance and durability while reducing noise emissions. Both careful aerodynamic design of the fan and proper installation of the fan into the system are requirements for achieving the performance and acoustic objectives. The design and installation characteristics of high performance aircraft engine fans will be discussed along with some lessons learned that may be applicable to spaceflight fan applications.
Lessons learned in the development of the STOL intelligent tutoring system
NASA Technical Reports Server (NTRS)
Seamster, Thomas; Baker, Clifford; Ames, Troy
1991-01-01
Lessons learned during the development of the NASA Systems Test and Operations Language (STOL) Intelligent Tutoring System (ITS), being developed at NASA Goddard Space Flight Center are presented. The purpose of the intelligent tutor is to train STOL users by adapting tutoring based on inferred student strengths and weaknesses. This system has been under development for over one year and numerous lessons learned have emerged. These observations are presented in three sections, as follows. The first section addresses the methodology employed in the development of the STOL ITS and briefly presents the ITS architecture. The second presents lessons learned, in the areas of: intelligent tutor development; documentation and reporting; cost and schedule control; and tools and shells effectiveness. The third section presents recommendations which may be considered by other ITS developers, addressing: access, use and selection of subject matter experts; steps involved in ITS development; use of ITS interface design prototypes as part of knowledge engineering; and tools and shells effectiveness.
ERIC Educational Resources Information Center
Freifeld, Lorri
2010-01-01
With technology changing every second of every day, it is no surprise a learning management system (LMS) quickly can become outdated. But it is no easy task to re-engineer a current LMS or find exactly the right new one to purchase. In this article, three 2010 Top Young Trainers share their experiences with implementing or re-engineering an…
NASA Technical Reports Server (NTRS)
Martinez, Hugo E.; Albright, John D.; D'Amico, Stephen J.; Brewer, John M.; Melcher, John C., IV
2011-01-01
The Space Shuttle Integrated Main Propulsion System (IMPS) consists of the External Tank (ET), Orbiter Main Propulsion System (MPS), and Space Shuttle Main Engines (SSMEs). The IMPS is tasked with the storage, conditioning, distribution, and combustion of cryogenic liquid hydrogen (LH2) and liquid oxygen (LO2) propellants to provide first and second stage thrust for achieving orbital velocity. The design, certification, and operation of the associated IMPS hardware have produced many lessons learned over the course of the Space Shuttle Program (SSP). A subset of these items will be discussed in this paper for consideration when designing, building, and operating future spacecraft propulsion systems. This paper will focus on lessons learned related to Orbiter MPS and is the first of a planned series to address the subject matter.
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.
Re-engineering the Multimission Command System at the Jet Propulsion Laboratory
NASA Technical Reports Server (NTRS)
Alexander, Scott; Biesiadecki, Jeff; Cox, Nagin; Murphy, Susan C.; Reeve, Tim
1994-01-01
The Operations Engineering Lab (OEL) at JPL has developed the multimission command system as part of JPL's Advanced Multimission Operations System. The command system provides an advanced multimission environment for secure, concurrent commanding of multiple spacecraft. The command functions include real-time command generation, command translation and radiation, status reporting, some remote control of Deep Space Network antenna functions, and command file management. The mission-independent architecture has allowed easy adaptation to new flight projects and the system currently supports all JPL planetary missions (Voyager, Galileo, Magellan, Ulysses, Mars Pathfinder, and CASSINI). This paper will discuss the design and implementation of the command software, especially trade-offs and lessons learned from practical operational use. The lessons learned have resulted in a re-engineering of the command system, especially in its user interface and new automation capabilities. The redesign has allowed streamlining of command operations with significant improvements in productivity and ease of use. In addition, the new system has provided a command capability that works equally well for real-time operations and within a spacecraft testbed. This paper will also discuss new development work including a multimission command database toolkit, a universal command translator for sequencing and real-time commands, and incorporation of telecommand capabilities for new missions.
Lessons Learned and Technical Standards: A Logical Marriage for Future Space Systems Design
NASA Technical Reports Server (NTRS)
Gill, Paul S.; Garcia, Danny; Vaughan, William W.; Parker, Nelson C. (Technical Monitor)
2002-01-01
A comprehensive database of engineering lessons learned that corresponds with relevant technical standards will be a valuable asset to those engaged in studies on future space vehicle developments, especially for structures, materials, propulsion, control, operations and associated elements. In addition, this will enable the capturing of technology developments applicable to the design, development, and operation of future space vehicles as planned in the Space Launch Initiative. Using the time-honored tradition of passing on lessons learned while utilizing the newest information technology, NASA has launched an intensive effort to link lessons learned acquired through various Internet databases with applicable technical standards. This paper will discuss the importance of lessons learned, the difficulty in finding relevant lessons learned while engaged in a space vehicle development, and the new NASA effort to relate them to technical standards that can help alleviate this difficulty.
ERIC Educational Resources Information Center
Maciejewski, Anthony A.; Leung, Nelson K.
1992-01-01
The Nihongo Tutorial System is designed to assist English-speaking scientists and engineers in acquiring reading proficiency in Japanese technical literature. It provides individualized lessons that match interest area/language ability with available materials that are encoded with syntactic, phonetic, and morphological information. (14…
Development and Implementation of a Design Metric for Systems Containing Long-Term Fluid Loops
NASA Technical Reports Server (NTRS)
Steele, John W.
2016-01-01
John Steele, a chemist and technical fellow from United Technologies Corporation, provided a water quality module to assist engineers and scientists with a metric tool to evaluate risks associated with the design of space systems with fluid loops. This design metric is a methodical, quantitative, lessons-learned based means to evaluate the robustness of a long-term fluid loop system design. The tool was developed by a cross-section of engineering disciplines who had decades of experience and problem resolution.
NASA Technical Reports Server (NTRS)
Shepard, Kyle; Sager, Paul; Kusunoki, Sid; Porter, John; Campion, AL; Mouritzan, Gunnar; Glunt, George; Vegter, George; Koontz, Rob
1993-01-01
Several topics are presented in viewgraph form which together encompass the preliminary assessment of nuclear thermal rocket engine clustering. The study objectives, schedule, flow, and groundrules are covered. This is followed by the NASA groundrules mission and our interpretation of the associated operational scenario. The NASA reference vehicle is illustrated, then the four propulsion system options are examined. Each propulsion system's preliminary design, fluid systems, operating characteristics, thrust structure, dimensions, and mass properties are detailed as well as the associated key propulsion system/vehicle interfaces. A brief series of systems analysis is also covered including: thrust vector control requirements, engine out possibilities, propulsion system failure modes, surviving system requirements, and technology requirements. An assessment of vehicle/propulsion system impacts due to the lessons learned are presented.
Academic Instruction with the Visible V-8 Engine. The Coordinated Correlated Instructional Program.
ERIC Educational Resources Information Center
Davis, W. J.
The book presents three 93-day lesson plans to motivate and teach handicapped secondary students basic academic skills in reading and language arts, English, and mathematics in conjunction with learning about automobile engines from Revell's Visible V8 Engine Kit. Each lesson plan is correlated with the Visible V8 Engine Kit and includes daily…
Sustainable, Reliable Mission-Systems Architecture
NASA Technical Reports Server (NTRS)
O'Neil, Graham; Orr, James K.; Watson, Steve
2005-01-01
A mission-systems architecture, based on a highly modular infrastructure utilizing open-standards hardware and software interfaces as the enabling technology is essential for affordable md sustainable space exploration programs. This mission-systems architecture requires (8) robust communication between heterogeneous systems, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, end verification of systems, and (e) minimal sustaining engineering. This paper proposes such an architecture. Lessons learned from the Space Shuttle program and Earthbound complex engineered systems are applied to define the model. Technology projections reaching out 5 years are made to refine model details.
Sustainable, Reliable Mission-Systems Architecture
NASA Technical Reports Server (NTRS)
O'Neil, Graham; Orr, James K.; Watson, Steve
2007-01-01
A mission-systems architecture, based on a highly modular infrastructure utilizing: open-standards hardware and software interfaces as the enabling technology is essential for affordable and sustainable space exploration programs. This mission-systems architecture requires (a) robust communication between heterogeneous system, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, and verification of systems, and (e) minimal sustaining engineering. This paper proposes such an architecture. Lessons learned from the Space Shuttle program and Earthbound complex engineered system are applied to define the model. Technology projections reaching out 5 years are mde to refine model details.
Lessons learned applying CASE methods/tools to Ada software development projects
NASA Technical Reports Server (NTRS)
Blumberg, Maurice H.; Randall, Richard L.
1993-01-01
This paper describes the lessons learned from introducing CASE methods/tools into organizations and applying them to actual Ada software development projects. This paper will be useful to any organization planning to introduce a software engineering environment (SEE) or evolving an existing one. It contains management level lessons learned, as well as lessons learned in using specific SEE tools/methods. The experiences presented are from Alpha Test projects established under the STARS (Software Technology for Adaptable and Reliable Systems) project. They reflect the front end efforts by those projects to understand the tools/methods, initial experiences in their introduction and use, and later experiences in the use of specific tools/methods and the introduction of new ones.
NASA Astrophysics Data System (ADS)
Yamada, Hirofumi; Ten-Nichi, Michio; Mathui, Hirosi; Nakamura, Akizi
This paper introduces a method of the engineering design education for college of technology mechanical engineering students. In order to teach the practical engineering design, the MIL-STD-499A process is adapted and improved upon for a Mechatronics hands-on lesson used as the MOT method. The educational results in five years indicate that knowledge of the engineering management is useful for college students in learning engineering design. Portfolio for lessons and the hypothesis method also have better effects on the understanding of the engineering specialty.
ERIC Educational Resources Information Center
Hamlin, Larry
This document contains a curriculum guide and lesson plans for a general mechanical repair course with three sections: minor automotive maintenance, small engine repair, and welding. The curriculum guide begins with a matrix that relates the lesson plans to essential elements of math, science, language arts, and social studies and to Texas…
Designing an Earthquake-Proof Art Museum: An Arts- and Engineering-Integrated Science Lesson
ERIC Educational Resources Information Center
Carignan, Anastasia; Hussain, Mahjabeen
2016-01-01
In this practical arts-integrated science and engineering lesson, an inquiry-based approach was adopted to teach a class of fourth graders in a Midwest elementary school about the scientific concepts of plate tectonics and earthquakes. Lessons were prepared following the 5 E instructional model. Next Generation Science Standards (4-ESS3-2) and the…
NASA Technical Reports Server (NTRS)
Topousis, Daria E.; Lebsock, Kenneth L.; Dennehy, Cornelius J.
2010-01-01
In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited engineers from sharing their experiences, expertise, ideas, and lessons learned. The necessity to collaborate on complex development projects and the reality of constrained project resources together drove the need for ensuring that personnel at all NASA centers had comparable skill sets and that engineers could find resources in a timely fashion. Mission failures and new directions for the Agency also demanded better collaborative tools for NASA's engineering workforce. In response to these needs, the online NASA Engineering Network (NEN) was formed by the NASA Office of the Chief Engineer to provide a multi-faceted system for overcoming geographic and cultural barriers. NEN integrates communities of practice with a cross-repository search and the Lessons Learned Information System. This paper describes the features of the GN&C engineering discipline CoP site which went live on NEN in May of 2008 as an online means of gathering input and guidance from practitioners. It allows GN&C discipline expertise captured at one field center to be shared in a collaborative way with the larger discipline CoP spread across the entire Agency. The site enables GN&C engineers to find the information they need quickly, to find solutions to questions from experienced engineers, and to connect with other practitioners regardless of geographic location, thus increasing the probability of project success.
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
Space Shuttle Propulsion System Reliability
NASA Technical Reports Server (NTRS)
Welzyn, Ken; VanHooser, Katherine; Moore, Dennis; Wood, David
2011-01-01
This session includes the following sessions: (1) External Tank (ET) System Reliability and Lessons, (2) Space Shuttle Main Engine (SSME), Reliability Validated by a Million Seconds of Testing, (3) Reusable Solid Rocket Motor (RSRM) Reliability via Process Control, and (4) Solid Rocket Booster (SRB) Reliability via Acceptance and Testing.
13th Annual Systems Engineering Conference: Tues- Wed
2010-10-28
greater understanding/documentation of lessons learned – Promotes SE within the organization • Justification for continued funding of SE Infrastructure...educational process – Addresses the development of innovative learning tools, strategies, and teacher training • Research and Development – Promotes ...technology, and mathematics • More commitment to engaging young students in science, engineering, technology and mathematics • More rigor in defining
Engineer: The Professional Bulletin of Army Engineers. Volume 38, PB 5-08-3/4, July-December 2008
2008-12-01
50 The Battle of Shiloh By Captain John T. Shelton 54 Pioneering Nondoctrinal Bridging Operations: The “Roller Skate ” Repair By First...for Army Lessons Learned (CALL) to conduct an Engineer and Base Camp Collection and Analysis Team (CAAT). As a result of this trip, we collected a...provided an outbrief at the 20th Engineer Brigade Lessons Learned Conference in December. Many thanks to the 20th Engineer Brigade, 926th Engineer
Lessons from the Army’s Future Combat Systems Program
2012-01-01
FCS, from the Aviation Center at Fort Rucker, Alabama, to the Chemical and Engineer Schools at Fort Leonard Wood , Mis- souri.75 The objective was to...Engineer) and Robert Woods (MGV LSI Chief Engineer), “MGV Platform Review,” circa February 2009. Not available to the general public. 22 Daniel Wasserbly...Acquisition Decision Memo- randum,” memorandum for Secretary of the Army, June 23, 2009. 59 Matt Donohue, Kris Gardner, and Major Scot Greig, “Future Combat
Alvin (Al) Sieff: Thoughts About and Lessons from a Great Engineer
NASA Technical Reports Server (NTRS)
Tauber, Michael
2010-01-01
Alvin (Al) Seiff was known as a world-class atmospheric scientist during the last three decades of his life. Equally deserving, however, were his prior achievements as an innovative engineer, an exceptional technical manager, and a mentor of young engineers at NASA Ames Research Center. This paper outlines Al's role in developing Ames ballistic range facilities, probably the most advanced in the world at that time, and his seminal 1963 report that contained the concepts used to reconstruct the atmospheres of Mars, Venus, Jupiter and Titan. Also discussed is my affiliation with Al after he hired me in 1962, including our joint work on Mars missions and investigating the feasibility that a Jupiter probe could survive entry, work that eventually led to the development of the Galileo probe. Finally, suggestions are offered for speeding the analysis and design of thermal protection systems based on lessons learned from successful probes and landers.
NASA Technical Reports Server (NTRS)
Homola, Jeffrey; Owens, Brandon
2017-01-01
This is a presentation for a Cisco Internet of Things (IoT) Systems Engineering Virtual Training (SEVT) event. The presentation provides an overview of the UTM concept, architecture, flight test events, and lessons learned. Networking hardware used in support of flight tests is also described.
NASA Technical Reports Server (NTRS)
Orr, James K.
2010-01-01
This presentation has shown the accomplishments of the PASS project over three decades and highlighted the lessons learned. Over the entire time, our goal has been to continuously improve our process, implement automation for both quality and increased productivity, and identify and remove all defects due to prior execution of a flawed process in addition to improving our processes following identification of significant process escapes. Morale and workforce instability have been issues, most significantly during 1993 to 1998 (period of consolidation in aerospace industry). The PASS project has also consulted with others, including the Software Engineering Institute, so as to be an early evaluator, adopter, and adapter of state-of-the-art software engineering innovations.
Flight software issues in onboard automated planning: lessons learned on EO-1
NASA Technical Reports Server (NTRS)
Tran, Daniel; Chien, Steve; Rabideau, Gregg; Cichy, Benjamin
2004-01-01
This paper focuses on the onboard planner and scheduler CASPER, whose core planning engine is based on the ground system ASPEN. Given the challenges of developing flight software, we discuss several of the issues encountered in preparing the planner for flight, including reducing the code image size, determining what data to place within the engineering telemetry packet, and performing long term planning.
Development Status of the NASA MC-1 (Fastrac) Engine
NASA Technical Reports Server (NTRS)
Ballard, Richard O.; Olive, Tim; Turner, James E. (Technical Monitor)
2000-01-01
The MC-1 (formerly known as the Fastrac 60K) Engine is being developed for the X-34 technology demonstrator vehicle. It is a pump-fed liquid rocket engine with fixed thrust operating at one rated power level of 60,000 lbf vacuum thrust using a 15:1 area ratio nozzle (slightly higher for the 30:1 flight nozzle). Engine system development testing of the MC-1 has been ongoing since 24 Oct 1998. To date, 48 tests have been conducted on three engines using three separate test stands. This paper will provide some details of the engine, the tests conducted, and the lessons learned to date.
A study on an information security system of a regional collaborative medical platform.
Zhao, Junping; Peng, Kun; Leng, Jinchang; Sun, Xiaowei; Zhang, Zhenjiang; Xue, Wanguo; Ren, Lianzhong
2010-01-01
The objective of this study was to share the experience of building an information security system for a regional collaborative medical platform (RCMP) and discuss the lessons learned from practical projects. Safety measures are analyzed from the perspective of system engineering. We present the essential requirements, critical architectures, and policies for system security of regional collaborative medical platforms.
NASA Astrophysics Data System (ADS)
Gold, A. U.; Sullivan, S. M.; Manning, C. L. B.; Ledley, T. S.; Youngman, E.; Taylor, J.; Niepold, F., III; Kirk, K.; Lockwood, J.; Bruckner, M. Z.; Fox, S.
2017-12-01
The impacts of climate change are a critical societal challenge of the 21st century. Educating students about the globally connected climate system is key in supporting the development of mitigation and adaptation strategies. Systems thinking is required for students to understand the complex, dynamic climate systems and the role that humans play within them. The interdisciplinary nature of climate science challenges educators, who often don't have formal training in climate science, to identify resources that are scientifically accurate before weaving them together into units that teach about the climate system. The Climate Literacy and Energy Awareness Network (CLEAN) supports this work by providing over 700 peer-reviewed, classroom-ready resources on climate and energy topics. The resource collection itself provide only limited instructional guidance, so educators need to weave the resources together to build multi-dimensional lessons that develop systems thinking skills. The Next Generation Science Standards (NGSS) science standards encourage educators to teach science in a 3-dimensional approach that trains students in systems thinking. The CLEAN project strives to help educators design NGSS-style, three-dimensional lessons about the climate system. Two approaches are currently being modeled on the CLEAN web portal. The first is described in the CLEAN NGSS "Get Started Guide" which follows a step-by-step process starting with the Disciplinary Core Idea and then interweaves the Cross-Cutting Concepts (CCC) and the Science and Engineering Practices (SEP) based on the teaching strategy chosen for the lesson or unit topic. The second model uses a climate topic as a starting place and the SEP as the guide through a four-step lesson sequence called "Earth Systems Investigations". Both models use CLEAN reviewed lessons as the core activity but provide the necessary framework for classroom implementation. Sample lessons that were developed following these two approaches are provided on the CLEAN web portal (cleanet.org).
ERIC Educational Resources Information Center
Heck, Daniel J.; Weiss, Iris R.
2005-01-01
In 1990, the National Science Foundation (NSF) created the Statewide Systemic Initiative Program. The solicitation issued by the Directorate for Science and Engineering Education sought proposals "for projects intended to broaden the impact, accelerate the pace, and increase the effectiveness of improvements in science, mathematics, and…
Historical problem areas lessons learned
NASA Technical Reports Server (NTRS)
Sackheim, Bob; Fester, Dale A.
1991-01-01
Historical problem areas in space transportation propulsion technology are identified in viewgraph form. Problem areas discussed include materials compatibility, contamination, pneumatic/feed system flow instabilities, instabilities in rocket engine combustion and fuel sloshing, exhaust plume interference, composite rocket nozzle failure, and freeze/thaw damage.
NASA Astrophysics Data System (ADS)
Hogue, T. S.; Moldwin, M.; Nonacs, P.; Daniel, J.; Shope, R.
2009-12-01
A National Science Foundation Graduate Teaching Fellows in K- 12 Education program at UCLA (SEE-LA; http://measure.igpp.ucla.edu/GK12-SEE-LA) has just completed its first year (of a five-year program) and has greatly expanded UCLA’s science and engineering partnerships with LA Unified and Culver City Unified School Districts. The SEE-LA program partners UCLA faculty, graduate students (fellows), middle and high school science teachers and their students into a program of science and engineering exploration that brings the environment of Los Angeles into the classroom. UCLA graduate fellows serve as scientists-in-residence at the four partner schools to integrate inquiry-based science and engineering lessons, facilitate advancements in science content teaching, and ultimately, to improve their own science communication skills. As part of their fellowship, graduate students are required to develop three inquiry-based lessons in their partner classroom, including a lesson focused on their dissertation research, a lesson focused on the environmental/watershed theme of the project, and a lesson that involves longer-term data collection and synthesis with the grade 6-12 teachers and students. The developed long-term projects ideally involve continued observations and analysis through the five-year project and beyond. During the first year of the project, the ten SEE-LA fellows developed a range of long-term research projects, from seasonal invertebrate observations in an urban stream system, to home energy consumption surveys, to a school bioblitz (quantification of campus animals and insects). Examples of lesson development and integration in the classroom setting will be highlighted as well as tools required for sustainability of the projects. University and local pre-college school partnerships provide an excellent opportunity to support the development of graduate student communication skills while also contributing significantly to the integration of sustainable research projects into K-12 curriculum.
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.
Stationary Engineering, Environmental Control, Refrigeration. Science Manual I.
ERIC Educational Resources Information Center
Steingress, Frederick M.; And Others
The student materials present lessons about occupations related to environmental control, stationary engineering, and refrigeration. Included are 18 units organized by objective, information, reference, procedure, and assignment. Each lesson involves concrete trade experience where science is applied. Unit titles are: safety and housekeeping,…
NASA Technical Reports Server (NTRS)
Vaughan, William W.; Anderson, B. Jeffrey
2005-01-01
In modern government and aerospace industry institutions the necessity of controlling current year costs often leads to high mobility in the technical workforce, "one-deep" technical capabilities, and minimal mentoring for young engineers. Thus, formal recording, use, and teaching of lessons learned are especially important in the maintenance and improvement of current knowledge and development of new technologies, regardless of the discipline area. Within the NASA Technical Standards Program Website http://standards.nasa.gov there is a menu item entitled "Lessons Learned/Best Practices". It contains links to a large number of engineering and technical disciplines related data sets that contain a wealth of lessons learned information based on past experiences. This paper has provided a small sample of lessons learned relative to the atmospheric and space environment. There are many more whose subsequent applications have improved our knowledge of the atmosphere and space environment, and the application of this knowledge to the engineering and operations for a variety of aerospace programs.
NASA Astrophysics Data System (ADS)
Claver, C. F.; Selvy, Brian M.; Angeli, George; Delgado, Francisco; Dubois-Felsmann, Gregory; Hascall, Patrick; Lotz, Paul; Marshall, Stuart; Schumacher, German; Sebag, Jacques
2014-08-01
The Large Synoptic Survey Telescope project was an early adopter of SysML and Model Based Systems Engineering practices. The LSST project began using MBSE for requirements engineering beginning in 2006 shortly after the initial release of the first SysML standard. Out of this early work the LSST's MBSE effort has grown to include system requirements, operational use cases, physical system definition, interfaces, and system states along with behavior sequences and activities. In this paper we describe our approach and methodology for cross-linking these system elements over the three classical systems engineering domains - requirement, functional and physical - into the LSST System Architecture model. We also show how this model is used as the central element to the overall project systems engineering effort. More recently we have begun to use the cross-linked modeled system architecture to develop and plan the system verification and test process. In presenting this work we also describe "lessons learned" from several missteps the project has had with MBSE. Lastly, we conclude by summarizing the overall status of the LSST's System Architecture model and our plans for the future as the LSST heads toward construction.
TRENDS: The aeronautical post-test database management system
NASA Technical Reports Server (NTRS)
Bjorkman, W. S.; Bondi, M. J.
1990-01-01
TRENDS, an engineering-test database operating system developed by NASA to support rotorcraft flight tests, is described. Capabilities and characteristics of the system are presented, with examples of its use in recalling and analyzing rotorcraft flight-test data from a TRENDS database. The importance of system user-friendliness in gaining users' acceptance is stressed, as is the importance of integrating supporting narrative data with numerical data in engineering-test databases. Considerations relevant to the creation and maintenance of flight-test database are discussed and TRENDS' solutions to database management problems are described. Requirements, constraints, and other considerations which led to the system's configuration are discussed and some of the lessons learned during TRENDS' development are presented. Potential applications of TRENDS to a wide range of aeronautical and other engineering tests are identified.
STGT program: Ada coding and architecture lessons learned
NASA Technical Reports Server (NTRS)
Usavage, Paul; Nagurney, Don
1992-01-01
STGT (Second TDRSS Ground Terminal) is currently halfway through the System Integration Test phase (Level 4 Testing). To date, many software architecture and Ada language issues have been encountered and solved. This paper, which is the transcript of a presentation at the 3 Dec. meeting, attempts to define these lessons plus others learned regarding software project management and risk management issues, training, performance, reuse, and reliability. Observations are included regarding the use of particular Ada coding constructs, software architecture trade-offs during the prototyping, development and testing stages of the project, and dangers inherent in parallel or concurrent systems, software, hardware, and operations engineering.
Developing the Systems Engineering Experience Accelerator (SEEA) Prototype and Roadmap
2012-10-24
system attributes. These metrics track non-requirements performance, typically relate to production cost per unit, maintenance costs, training costs...immediately implement lessons learned from the training experience to the job, assuming the culture allows this. 1.3 MANAGEMENT PLAN/TECHNICAL OVERVIEW...resolving potential conflicts as they arise. Incrementally implement and continuously integrate capability in priority order, to ensure that final system
Jupiter Europa Orbiter Architecture Definition Process
NASA Technical Reports Server (NTRS)
Rasmussen, Robert; Shishko, Robert
2011-01-01
The proposed Jupiter Europa Orbiter mission, planned for launch in 2020, is using a new architectural process and framework tool to drive its model-based systems engineering effort. The process focuses on getting the architecture right before writing requirements and developing a point design. A new architecture framework tool provides for the structured entry and retrieval of architecture artifacts based on an emerging architecture meta-model. This paper describes the relationships among these artifacts and how they are used in the systems engineering effort. Some early lessons learned are discussed.
Fiber optic (flight quality) sensors for advanced aircraft propulsion
NASA Technical Reports Server (NTRS)
Poppel, Gary L.
1994-01-01
Development of flight prototype, fiber-optic sensing system components for measuring nine sensed parameters (three temperatures, two speeds, three positions, and one flame) on an F404-400 aircraft engine is described. Details of each sensor's design, functionality, and environmental testing, and the electro-optics architecture for sensor signal conditioning are presented. Eight different optical sensing techniques were utilized. Design, assembly, and environmental testing of an engine-mounted, electro-optics chassis unit (EOU), providing MIL-C-1553 data output, are related. Interconnection cables and connectors between the EOU and the sensors are identified. Results of sensor/cable/circuitry integrated testing, and installation and ground testing of the sensor system on an engine in October 1993 and April 1994 are given, including comparisons with the engine control system's electrical sensors. Lessons learned about the design, fabrication, testing, and integration of the sensor system components are included.
Business process re-engineering--saviour or just another fad? One UK health care perspective.
Patwardhan, Anjali; Patwardhan, Dhruv
2008-01-01
Pressure to change is politically driven owing to escalating healthcare costs and an emphasis on efficiency gains, value for money and improved performance proof in terms of productivity and recently to some extent by demands from less satisfied patients and stakeholders. In a background of newly immerging expensive techniques and drugs, there is an increasing consumer expectation, i.e. quality services. At the same time, health system managers and practitioners are finding it difficult to cope with demand and quality expectations. Clinicians are frustrated because they are not recognised for their contribution. Managers are frustrated because meaningful dialogue with clinicians is lacking, which has intensified the need for change to a more efficient system that satisfies all arguments about cost effectiveness and sustainable quality services. Various strategies, originally developed by management quality "gurus" for engineering industries, have been applied to health industries with variable success, which largely depends on the type of health care system to which they are applied. Business process re-engineering is examined as a quality management tool using past and recent publications. The paper finds that applying business process re-engineering in the right circumstances and selected settings for quality improvement is critical for its success. It is certainly "not for everybody". The paper provides a critical appraisal of business process re-engineering experiences in UK healthcare. Lessons learned regarding selecting organisations and agreeing realistic expectations are addressed. Business process re-engineering has been evaluated and reviewed since 1987 in US managed health care, with no clear lessons learned possibly because unit selection and simultaneous comparison between two units virtually performing at opposite ends has never been done before. Two UK pilot studies, however, add useful insights.
NASA Technical Reports Server (NTRS)
1991-01-01
Recommendations are made after 32 interviews, lesson identification, lesson analysis, and mission characteristics identification. The major recommendations are as follows: (1) to develop end-to-end planning and scheduling operations concepts by mission class and to ensure their consideration in system life cycle documentation; (2) to create an organizational infrastructure at the Code 500 level, supported by a Directorate level steering committee with project representation, responsible for systems engineering of end-to-end planning and scheduling systems; (3) to develop and refine mission capabilities to assess impacts of early mission design decisions on planning and scheduling; and (4) to emphasize operational flexibility in the development of the Advanced Space Network, other institutional resources, external (e.g., project) capabilities and resources, operational software and support tools.
User observations on information sharing (corporate knowledge and lessons learned)
NASA Technical Reports Server (NTRS)
Montague, Ronald A.; Gregg, Lawrence A.; Martin, Shirley A.; Underwood, Leroy H.; Mcgee, John M.
1993-01-01
The sharing of 'corporate knowledge' and lessons learned in the NASA aerospace community has been identified by Johnson Space Center survey participants as a desirable tool. The concept of the program is based on creating a user friendly information system that will allow engineers, scientists, and managers at all working levels to share their information and experiences with other users irrespective of location or organization. The survey addresses potential end uses for such a system and offers some guidance on the development of subsequent processes to ensure the integrity of the information shared. This system concept will promote sharing of information between NASA centers, between NASA and its contractors, between NASA and other government agencies, and perhaps between NASA and institutions of higher learning.
LESSONS LEARNED IN OPERATING THE HOSE-IN-HOSE SYSTEM FOR TRANSFSERRING SLUDGE AT HANFORDS K-BASINS
DOE Office of Scientific and Technical Information (OSTI.GOV)
PERES MW
In May 2007, the Department of Energy and the Fluor Hanford K Basin Closure Project completed transferring sludge from the K East Basin to new containers in the K West Basin using a Hose-in-Hose system. This project presented a number of complex and unique technical, operational, and management challenges that had to be resolved to complete the required transfers and satisfy project milestones. The project team (including DOE; regulators; and Fluor management, operations, maintenance, engineering and all other support organizations) found innovative solutions to each challenge. This paper records lessons learned during the operational phase of the sludge transfer viamore » the Hose-In-Hose system. The subject is limited to the operational phase and does not cover design, development, testing or turnover. A discussion of the situation or problem encountered is provided, along with the lesson learned as applicable to a future program or project.« less
Lessons Learned from Engineering a Multi-Mission Satellite Operations Center
NASA Technical Reports Server (NTRS)
Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David
2006-01-01
NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.
Lessons Learned from the Puerto Rico Battery Energy Storage System
DOE Office of Scientific and Technical Information (OSTI.GOV)
BOYES, JOHN D.; DE ANA, MINDI FARBER; TORRES, WENCESLANO
1999-09-01
The Puerto Rico Electric Power Authority (PREPA) installed a distributed battery energy storage system in 1994 at a substation near San Juan, Puerto Rico. It was patterned after two other large energy storage systems operated by electric utilities in California and Germany. The U.S. Department of Energy (DOE) Energy Storage Systems Program at Sandia National Laboratories has followed the progress of all stages of the project since its inception. It directly supported the critical battery room cooling system design by conducting laboratory thermal testing of a scale model of the battery under simulated operating conditions. The Puerto Rico facility ismore » at present the largest operating battery storage system in the world and is successfully providing frequency control, voltage regulation, and spinning reserve to the Caribbean island. The system further proved its usefulness to the PREPA network in the fall of 1998 in the aftermath of Hurricane Georges. The owner-operator, PREPA, and the architect/engineer, vendors, and contractors learned many valuable lessons during all phases of project development and operation. In documenting these lessons, this report will help PREPA and other utilities in planning to build large energy storage systems.« less
Settling into the midstream? Lessons for governance from the decade of nanotechnology
NASA Astrophysics Data System (ADS)
Bosso, Christopher
2016-06-01
This paper analyzes scholarly papers published from 2003 through 2013 on the general theme of nanotechnology and governance. It considers three general points: (1) the "problem" of nanotechnology; (2) general lessons for governance obtained; and (3) prospects for aligning the US regulatory system to the next generation of complex engineered nano-materials. It argues that engineered nano-materials and products are coming to market within an already mature regulatory framework of decade-old statutes, long-standing bureaucratic rules and routines, narrowly directive judicial decisions, and embedded institutional norms. That extant regulatory regime shapes how policymakers perceive, define, and address the relative benefits and risks of both proximate and yet-to-be idealized nano-materials and applications. The paper concludes that fundamental reforms in the extant regime are unlikely short of a perceived crisis.
NASA Technical Reports Server (NTRS)
Bazley, Jesse
2015-01-01
The International Space Station's (ISS) Regenerative Environmental Control and Life Support System (ECLSS) was launched in 2008 to continuously recycle urine and crew sweat into drinking water and oxygen using brand new technologies. This functionality was highly important to the ability of the ISS to transition to the long-term goal of 6-crew operations as well as being critical tests for long-term space habitability. Through the initial activation and long-term operations of these systems, important lessons were learned about the importance of system redundancy and operational workarounds that allow Systems Engineers to maintain functionality with limited on-orbit spares. This presentation will share some of these lessons learned including how to balance water through the different systems, store and use water for use in system failures and creating procedures to operate the systems in ways that they were not initially designed to do.
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge
NASA Technical Reports Server (NTRS)
Dubon, Lydia P.
2006-01-01
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Lessons learned in transitioning to an open systems environment
NASA Technical Reports Server (NTRS)
Boland, Dillard E.; Green, David S.; Steger, Warren L.
1994-01-01
Software development organizations, both commercial and governmental, are undergoing rapid change spurred by developments in the computing industry. To stay competitive, these organizations must adopt new technologies, skills, and practices quickly. Yet even for an organization with a well-developed set of software engineering models and processes, transitioning to a new technology can be expensive and risky. Current industry trends are leading away from traditional mainframe environments and toward the workstation-based, open systems world. This paper presents the experiences of software engineers on three recent projects that pioneered open systems development for NASA's Flight Dynamics Division of the Goddard Space Flight Center (GSFC).
NASA Technical Reports Server (NTRS)
Escher, William J. D.; Roddy, Jordan E.; Hyde, Eric H.
2000-01-01
The Supercharged Ejector Ramjet (SERJ) engine developments of the 1960s, as pursued by The Marquardt Corporation and its associated industry team members, are described. In just three years, engineering work on this combined-cycle powerplant type evolved, from its initial NASA-sponsored reusable space transportation system study status, into a U.S. Air Force/Navy-supported exploratory development program as a candidate 4.5 high-performance military aircraft engine. Bridging a productive transition from the spaceflight to the aviation arena, this case history supports the expectation that fully-integrated airbreathing/rocket propulsion systems hold high promise toward meeting the demanding propulsion requirements of tomorrow's aircraft-like Spaceliner class transportation systems. Lessons to be learned from this "SERJ Story" are offered for consideration by today's advanced space transportation and combined-cycle propulsion researchers and forward-planning communities.
Lessons Learned from a Collaborative Sensor Web Prototype
NASA Technical Reports Server (NTRS)
Ames, Troy; Case, Lynne; Krahe, Chris; Hess, Melissa; Hennessy, Joseph F. (Technical Monitor)
2002-01-01
This paper describes the Sensor Web Application Prototype (SWAP) system that was developed for the Earth Science Technology Office (ESTO). The SWAP is aimed at providing an initial engineering proof-of-concept prototype highlighting sensor collaboration, dynamic cause-effect relationship between sensors, dynamic reconfiguration, and remote monitoring of sensor webs.
Model-Based Systems Engineering Pilot Program at NASA Langley
NASA Technical Reports Server (NTRS)
Vipavetz, Kevin G.; Murphy, Douglas G.; Infeld, Samatha I.
2012-01-01
NASA Langley Research Center conducted a pilot program to evaluate the benefits of using a Model-Based Systems Engineering (MBSE) approach during the early phase of the Materials International Space Station Experiment-X (MISSE-X) project. The goal of the pilot was to leverage MBSE tools and methods, including the Systems Modeling Language (SysML), to understand the net gain of utilizing this approach on a moderate size flight project. The System Requirements Review (SRR) success criteria were used to guide the work products desired from the pilot. This paper discusses the pilot project implementation, provides SysML model examples, identifies lessons learned, and describes plans for further use on MBSE on MISSE-X.
NASA's J-2X Engine Builds on the Apollo Program for Lunar Return Missions
NASA Technical Reports Server (NTRS)
Snoddy, Jimmy R.
2006-01-01
In January 2006, NASA streamlined its U.S. Vision for Space Exploration hardware development approach for replacing the Space Shuttle after it is retired in 2010. The revised CLV upper stage will use the J-2X engine, a derivative of NASA s Apollo Program Saturn V s S-II and S-IVB main propulsion, which will also serve as the Earth Departure Stage (EDS) engine. This paper gives details of how the J- 2X engine effort mitigates risk by building on the Apollo Program and other lessons learned to deliver a human-rated engine that is on an aggressive development schedule, with first demonstration flight in 2010 and human test flights in 2012. It is well documented that propulsion is historically a high-risk area. NASA s risk reduction strategy for the J-2X engine design, development, test, and evaluation is to build upon heritage hardware and apply valuable experience gained from past development efforts. In addition, NASA and its industry partner, Rocketdyne, which originally built the J-2, have tapped into their extensive databases and are applying lessons conveyed firsthand by Apollo-era veterans of America s first round of Moon missions in the 1960s and 1970s. NASA s development approach for the J-2X engine includes early requirements definition and management; designing-in lessons learned from the 5-2 heritage programs; initiating long-lead procurement items before Preliminary Desi& Review; incorporating design features for anticipated EDS requirements; identifying facilities for sea-level and altitude testing; and starting ground support equipment and logistics planning at an early stage. Other risk reduction strategies include utilizing a proven gas generator cycle with recent development experience; utilizing existing turbomachinery ; applying current and recent main combustion chamber (Integrated Powerhead Demonstrator) and channel wall nozzle (COBRA) advances; and performing rigorous development, qualification, and certification testing of the engine system, with a philosophy of "test what you fly, and fly what you test". These and other active risk management strategies are in place to deliver the J-2X engine for LEO and lunar return missions as outlined in the U.S. Vision for Space Exploration.
Engineer: The Professional Bulletin of Army Engineers. Volume 41, September-December 2011
2011-12-01
and its sup- port to the joint and coalition forces that will remain in contact as far into the future as we can see, executing a unique blend of war...U.S. Army Engineer School As the regiment makes adjustments based on lessons learned during .the last 10 years, the backbone of our Army is rapidly...adjusting to support these improvements. This requires engaged NCOs at all levels. Junior NCOs should continue to provide the lessons learned to
White Cliffs: Operating Experience
NASA Technical Reports Server (NTRS)
Kaneff, S.
1984-01-01
The fourteen dish white cliffs solar power station area is remote and subject to extreme environmental conditions, solution of the associated problems required careful and thoughtful attention and the application of resources. Notwithstanding the wide range and harshness of conditions, the difficulties caused by remoteness and the lack of a technological base and the need for relatively rapid demonstration of success, the project has had a very positive outcome. Qualitative and quantitative information and lessons are now available to enable considerable simplifications to be made for a new system, reducing both hardware and operation and maintenance costs. Experience and lessons are presented, particularly in relation to: system performance in various environmental conditions; design philosophies for collectors, the array, control systems, engine and plant; operation and maintenance strategies and cost reducing possibilities. Experience so far gives encouragement for the future of such paraboloidal dish systems in appropriate areas.
Object-oriented approach for gas turbine engine simulation
NASA Technical Reports Server (NTRS)
Curlett, Brian P.; Felder, James L.
1995-01-01
An object-oriented gas turbine engine simulation program was developed. This program is a prototype for a more complete, commercial grade engine performance program now being proposed as part of the Numerical Propulsion System Simulator (NPSS). This report discusses architectural issues of this complex software system and the lessons learned from developing the prototype code. The prototype code is a fully functional, general purpose engine simulation program, however, only the component models necessary to model a transient compressor test rig have been written. The production system will be capable of steady state and transient modeling of almost any turbine engine configuration. Chief among the architectural considerations for this code was the framework in which the various software modules will interact. These modules include the equation solver, simulation code, data model, event handler, and user interface. Also documented in this report is the component based design of the simulation module and the inter-component communication paradigm. Object class hierarchies for some of the code modules are given.
Exciting middle and high school students about immunology: an easy, inquiry-based lesson.
Lukin, Kara
2013-03-01
High school students in the United States are apathetic about science, technology, engineering and mathematics (STEM), and the workforce pipeline in these areas is collapsing. The lack of understanding of basic principles of biology means that students are unable to make educated decisions concerning their personal health. To address these issues, we have developed a simple, inquiry-based outreach lesson centered on a mouse dissection. Students learn key concepts in immunology and enhance their understanding of human organ systems. The experiment highlights aspects of the scientific method and authentic data collection and analysis. This hands-on activity stimulates interest in biology, personal health and careers in STEM fields. Here, we present all the information necessary to execute the lesson effectively with middle and high school students.
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.
Constellation Program Design Challenges as Opportunities for Educational Outreach- Lessons Learned
NASA Technical Reports Server (NTRS)
Trevino, Robert C.
2010-01-01
The Texas Space Grant Consortium (TSGC) and the NASA Exploration Systems Mission Directorate (ESMD) Education Office both have programs that present design challenges for university senior design classes that offer great opportunities for educational outreach and workforce development. These design challenges have been identified by NASA engineers and scientists as actual design problems faced by the Constellation Program in its exploration missions and architecture. Student teams formed in their senior design class select and then work on a design challenge for one or two semesters. The senior design class follows the requirements set by their university, but it must also comply with the Accreditation Board for Engineering and Technology (ABET) in order to meet the class academic requirements. Based on a one year fellowship at a TSGC university under the NASA Administrator's Fellowship Program (NAFP) and several years of experience, lessons learned are presented on the NASA Design Challenge Program.
Acting on Lessons Learned: A NASA Glenn Acoustics Branch Perspective
NASA Technical Reports Server (NTRS)
Koch, L. Danielle
2008-01-01
Lessons learned from the International Space Station have indicated that early attention to acoustics will be key to achieving safer, more productive environments for new long duration missions. Fans are known to be dominant noise sources, and reducing fan noise poses challenges for fan manufacturers and systems engineers. The NASA Glenn Acoustics Branch has considered ways in which expertise and capabilities traditionally used to understand and mitigate aircraft engine noise can be used to address small fan noise issues in Exploration and Information Technology applications. Many could benefit if NASA can capture what is known about small fan aero and acoustic performance in a "Guide for the Design, Selection, and Installation of Fans for Spaceflight Applications." A draft outline for this document will be offered as a useful starting point for brainstorming ideas for the various smaller, near-term research projects that would need to be addressed first.
What went right: lessons for the intensivist from the crew of US Airways Flight 1549.
Eisen, Lewis A; Savel, Richard H
2009-09-01
On January 15, 2009, US Airways Flight 1549 hit geese shortly after takeoff from LaGuardia Airport in New York City. Both engines lost power, and the crew quickly decided that the best action was an emergency landing in the Hudson River. Due to the crew's excellent performance, all 155 people aboard the flight survived. Intensivists can learn valuable lessons from the processes and outcome of this incident, including the importance of simulation training and checklists. By learning from the aviation industry, the intensivist can apply principles of crew resource management to reduce errors and improve patient safety. Additionally, by studying the impact of the mandated process-engineering applications within commercial aviation, intensivists and health-care systems can learn certain principles that, if adequately and thoughtfully applied, may seriously improve the art and science of health-care delivery at the bedside.
SSME Electrical Harness and Cable Development and Evolution
NASA Technical Reports Server (NTRS)
Abrams, Russ; Heflin, Johnny; Burns, Bob; Camper, Scott J.; Hill, Arthur J.
2010-01-01
The Space Shuttle Main Engine (SSME) electrical harness and cable system consists of the various interconnecting devices necessary for operation of complex rocket engine functions. Thirty seven harnesses incorporate unique connectors, backshell adapters, conductors, insulation, shielding, and physical barriers for a long maintenance-free life while providing the means to satisfy performance requirements and to mitigate adverse environmental influences. The objective of this paper is to provide a description of the SSME electrical harness and cable designs as well as the development history and lessons learned.
Business Re-Engineering: Lessons Learned From the U.S. Army Corps of Engineers Modernization Program
1992-10-01
34Boeing Knocks Down the Wall Between the Dreamers and the Doers", Business , 28 Oct 1991, p. 120. "The Cost Based Activity Modeling Project...Whatever shortcomings this study may have - for which we take full responsibility, of course - the results have been immeasurably improved by their help...This was done with little or no high-level support or direction. The resulting "stovepipe" systems may have met the needs of individual functional groups
The Use of Prototypes in Weapon System Development
1981-03-01
engine to minimize flameouts; experience showed that some uses of composite mate- rials were unwarranted, and other uses were proved valid; and a special... composite structure materials. The YF-16 used a single F100, an engine already developed for the F-15 program. By the time of the YF-16 first flight...lessons learned during the prototype tests led to a reduction in the use of composite materials ir the full scale F-16A program. UTTAS. Because of the
The Tailoring of Traditional Systems Engineering for the Morpheus Project
NASA Technical Reports Server (NTRS)
Devolites, Jennifer L.; Hart, Jeremy J.
2013-01-01
NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. From the beginning, one of goals for the Morpheus Project was to streamline agency processes and practices. The Morpheus project accepted a challenge to tailor the traditional NASA systems engineering approach in a way that would be appropriate for a lower cost, rapid prototype engineering effort, but retain the essence of the guiding principles. The team has produced innovative ways to create an infrastructure and approach that would challenge existing systems engineering processes while still enabling successful implementation of the current Morpheus Project. This paper describes the tailored systems engineering approach for the Morpheus project, including the processes, tools, and amount of rigor employed over the project's multiple lifecycles since the project began in FY11. Lessons learned from these trials have the potential to be scaled up and improve efficiency on a larger projects or programs.
Surviving the Lead Reliability Engineer Role in High Unit Value Projects
NASA Technical Reports Server (NTRS)
Perez, Reinaldo J.
2011-01-01
A project with a very high unit value within a company is defined as a project where a) the project constitutes one of a kind (or two-of-a-kind) national asset type of project, b) very large cost, and c) a mission failure would be a very public event that will hurt the company's image. The Lead Reliability engineer in a high visibility project is by default involved in all phases of the project, from conceptual design to manufacture and testing. This paper explores a series of lessons learned, over a period of ten years of practical industrial experience by a Lead Reliability Engineer. We expand on the concepts outlined by these lessons learned via examples. The lessons learned are applicable to all industries.
Patterns of Change: Forces and Motion
ERIC Educational Resources Information Center
Phillips, Marianne; Jeffery, Tonya D.
2016-01-01
Patterns of Change: Forces and Motion is an integrated science lesson that uses the 5E lesson cycle to tie together science with language arts, mathematics, literature, technology, engineering and social studies in an engaging format applicable for young learners. This lesson has been uniquely designed for the purpose of providing elementary…
New Orleans and Hurricane Katrina. IV: Orleans East Bank (Metro) protected basin
Seed, R.B.; Bea, R.G.; Athanasopoulos-Zekkos, A.; Boutwell, G.P.; Bray, J.D.; Cheung, C.; Cobos-Roa, D.; Cohen-Waeber, J.; Collins, B.D.; Harder, L.F.; Kayen, R.E.; Pestana, J.M.; Riemer, M.F.; Rogers, J.D.; Storesund, R.; Vera-Grunauer, X.; Wartman, Joseph
2008-01-01
This paper addresses damage caused by Hurricane Katrina to the main Orleans East Bank protected basin. This basin represented the heart of New Orleans, and contained the main downtown area, the historic French Quarter, the Garden District, and the sprawling Lakefront and Canal Districts. Nearly half of the loss of life during this hurricane, and a similar fraction of the overall damages, occurred in this heavily populated basin. There are a number of important geotechnical lessons, as well as geo-forensic lessons, associated with the flooding of this basin. These include the difficulties associated with the creation and operation of regional-scale flood protection systems requiring federal and local cooperation and funding over prolonged periods of time. There are also a number of engineering and policy lessons regarding (1) the accuracy and reliability of current analytical methods; (2) the shortcomings and potential dangers involved in decisions that reduced short-term capital outlays in exchange for increased risk of potential system failures; (3) the difficulties associated with integrating local issues with a flood risk reduction project; and (4) the need to design and maintain levees as systems; with each of the many individual project elements being required to mesh seamlessly. These lessons are of interest and importance for similar flood protection systems throughout numerous other regions of the United States and the world. ?? 2008 ACSE.
From Evidence to Impact: Recommendations for a Dissemination Support System
ERIC Educational Resources Information Center
Kreuter, Matthew W.; Wang, Monica L.
2015-01-01
While finding effective solutions to child and adolescent health problems is very much a scientific endeavor, getting those solutions into widespread practice largely is not. This paper applies lessons from business and engineering to highlight the shortcomings of current approaches to science translation. In challenging the status quo, the paper…
Flight testing the Digital Electronic Engine Control (DEEC) A unique management experience
NASA Technical Reports Server (NTRS)
Putnam, T. W.; Burcham, F. W., Jr.; Kock, B. M.
1983-01-01
The concept for the DEEC had its origin in the early 1970s. At that time it was recognized that the F100 engine performance, operability, reliability, and cost could be substantially improved by replacing the original mechanical/supervisory electronic control system with a full-authority digital control system. By 1978, the engine manufacturer had designed and initiated the procurement of flight-qualified control system hardware. As a precursor to an integrated controls program, a flight evaluation of the DEEC system on the F-15 aircraft was proposed. Questions regarding the management of the DEEC flight evaluation program are discussed along with the program elements, the technical results of the F-15 evaluation, and the impact of the flight evaluation on after-burning turbofan controls technology and its use in and application to military aircraft. The lessons learned through the conduct of the program are discussed.
Lessons Learned and Technical Standards: A Logical Marriage
NASA Technical Reports Server (NTRS)
Gill, Paul; Vaughan, William W.; Garcia, Danny; Gill, Maninderpal S. (Technical Monitor)
2001-01-01
A comprehensive database of lessons learned that corresponds with relevant technical standards would be a boon to technical personnel and standards developers. The authors discuss the emergence of one such database within NASA, and show how and why the incorporation of lessons learned into technical standards databases can be an indispensable tool for government and industry. Passed down from parent to child, teacher to pupil, and from senior to junior employees, lessons learned have been the basis for our accomplishments throughout the ages. Government and industry, too, have long recognized the need to systematically document And utilize the knowledge gained from past experiences in order to avoid the repetition of failures and mishaps. The use of lessons learned is a principle component of any organizational culture committed to continuous improvement. They have formed the foundation for discoveries, inventions, improvements, textbooks, and technical standards. Technical standards are a very logical way to communicate these lessons. Using the time-honored tradition of passing on lessons learned while utilizing the newest in information technology, the National Aeronautics and Space Administration (NASA) has launched an intensive effort to link lessons learned with specific technical standards through various Internet databases. This article will discuss the importance of lessons learned to engineers, the difficulty in finding relevant lessons learned while engaged in an engineering project, and the new NASA project that can help alleviate this difficulty. The article will conclude with recommendations for more expanded cross-sectoral uses of lessons learned with reference to technical standards.
ERIC Educational Resources Information Center
Weaver, Kim M.
2005-01-01
In this unit, elementary students design and build a lunar plant growth chamber using the Engineering Design Process. The purpose of the unit is to help students understand and apply the design process as it relates to plant growth on the moon. This guide includes six lessons, which meet a number of national standards and benchmarks in…
Practical Applications of Cables and Ropes in the ISS Countermeasures System
NASA Technical Reports Server (NTRS)
Moore, Cherice; Svetlik, Randall; Williams, Antony
2017-01-01
As spaceflight durations have increased over the last four decades, the effects of weightlessness on the human body are far better understood, as are the countermeasures. A combination of aerobic and resistive exercise devices contribute to countering the losses in muscle strength, aerobic fitness, and bone strength of today's astronauts and cosmonauts that occur during their missions on the International Space Station. Creation of these systems has been a dynamically educational experience for designers and engineers. The ropes and cables in particular have experienced a wide range of challenges, providing a full set of lessons learned that have already enabled improvements in on-orbit reliability by initiating system design improvements. This paper examines the on-orbit experience of ropes and cables in several exercise devices and discusses the lessons learned from these hardware items, with the goal of informing future system design.
Bringing life to space exploration.
Noor, A K; Doyle, R J; Venneri, S L
1999-11-01
Characteristics of 21st century space exploration are examined. Characteristics discussed include autonomy, evolvability, robotic outposts, and an overview of future missions. Sidebar articles examine the application of lessons from biological systems to engineered systems and mission concepts taking shape at NASA. Those mission concepts include plans for Mars missions, sample return missions for Venus and a comet nucleus, Europa orbiter and lander missions, a Titan organics explorer, and a terrestrial planet finder.
Experiencing Friction in First Grade
ERIC Educational Resources Information Center
Burton, Bill
2012-01-01
With the new focus on Science, Technology, Engineering, and Math (STEM) education, it's important to keep an open mind about incorporating technology into science lessons. In many cases, lessons that incorporate technology are not about the technology itself. Rather, the technology serves as a tool to enhance the lesson or add a new dimension to…
ERIC Educational Resources Information Center
Childs, Barbara; And Others
This instructional unit for grades 8-9 combines science and social studies in a look at the broad social and economic upheavals that took place during the industrial revolution, giving special emphasis to the role of energy. The invention and development of the steam engine is highlighted in one lesson. Other lessons show how the industrial…
The final days of Solar Max - Lessons learned from engineering evaluation tests
NASA Technical Reports Server (NTRS)
Donnelly, Michael L.; Croft, John W.; Ward, David K.; Thames, Michael A.
1990-01-01
End-of-life engineering evaluation tests were performed on Solar Max between October and November 1989. The tests included four-wheel control law operation; reaction wheel rundowns; modular power subsystem standard power regulator unit voltage-temperature level tests; battery rundown/2nd plateau determination; high gain antenna retraction and jettison; and solar array jettison. This paper presents these tests, their results, and the lessons learned from them.
Development of Concept-Based Physiology Lessons for Biomedical Engineering Undergraduate Students
ERIC Educational Resources Information Center
Nelson, Regina K.; Chesler, Naomi C.; Strang, Kevin T.
2013-01-01
engineering curriculum. In one or two introductory physiology courses, engineering students must learn physiology sufficiently to support learning in their subsequent engineering courses and careers. As preparation for future learning, physiology instruction centered on concepts may…
NASA Technical Reports Server (NTRS)
Johnson, Teresa A.
2006-01-01
Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.
ERIC Educational Resources Information Center
Herder, P. M.; Subrahmanian, E.; Talukdar, S.; Turk, A. L.; Westerberg, A. W.
2002-01-01
Explains distance education approach applied to the 'Engineering Design Problem Formulation' course simultaneously at the Delft University of Technology (the Netherlands) and at Carnegie Mellon University (CMU, Pittsburgh, USA). Uses video taped lessons, video conferencing, electronic mails and web-accessible document management system LIRE in the…
A Discussion of the Software Quality Assurance Role
NASA Technical Reports Server (NTRS)
Kandt, Ronald Kirk
2010-01-01
The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).
The MSFC Systems Engineering Guide: An Overview and Plan
NASA Technical Reports Server (NTRS)
Shelby, Jerry A.; Thomas, L. Dale
2007-01-01
As systems and subsystems requirements become more complex in the pursuit of the exploration of space, advanced technology will demand and require an integrated approach to the design and development of safe and successful space vehicles and there products. System engineers play a vital and key role in transforming mission needs into vehicle requirements that can be verified and validated. This will result in a safe and cost effective design that will satisfy the mission schedule. A key to successful vehicle design within systems engineering is communication. Communication, through a systems engineering infrastructure, will not only ensure that customers and stakeholders are satisfied but will also assist in identifying vehicle requirements; i.e. identification, integration and management. This vehicle design will produce a system that is verifiable, traceable, and effectively satisfies cost, schedule, performance, and risk throughout the life-cycle of the product. A communication infrastructure will bring about the integration of different engineering disciplines within vehicle design. A system utilizing these aspects will enhance system engineering performance and improve upon required activities such as Development of Requirements, Requirements Management, Functional Analysis, Test, Synthesis, Trade Studies, Documentation, and Lessons Learned to produce a successful final product. This paper will describe the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that will describe the system engineering processes that are used by MSFC in the development of complex systems such as the Ares launch vehicle. It is the intent of this website to be a "One Stop Shop" for our systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.
Gas Station Pricing Game: A Lesson in Engineering Economics and Business Strategies.
ERIC Educational Resources Information Center
Sin, Aaron; Center, Alfred M.
2002-01-01
Describes an educational game designed for engineering majors that demonstrates engineering economics and business strategies, specifically the concepts of customer perception of product value, convenience, and price differentiation. (YDS)
The CGE-PLATO Electronic Laboratory Instructional Programs. (August 1, 1972 Through June 30, 1975).
ERIC Educational Resources Information Center
Neal, J. P.
Twelve PLATO lessons are reproduced in this document to show the status of computer guided experimentation (CGE) instructional programs. The lesson topics include a description of the CGE-PLATO instructional laboratory, an introduction to CGE-PLATO tests and special software routines, router lesson for two electrical engineering courses, and an…
Kuzma, Jennifer; Najmaie, Pouya; Larson, Joel
2009-01-01
The U.S. oversight system for genetically engineered organisms (GEOs) was evaluated to develop hypotheses and derive lessons for oversight of other emerging technologies, such as nanotechnology. Evaluation was based upon quantitative expert elicitation, semi-standardized interviews, and historical literature analysis. Through an interdisciplinary policy analysis approach, blending legal, ethical, risk analysis, and policy sciences viewpoints, criteria were used to identify strengths and weaknesses of GEOs oversight and explore correlations among its attributes and outcomes. From the three sources of data, hypotheses and broader conclusions for oversight were developed. Our analysis suggests several lessons for oversight of emerging technologies: the importance of reducing complexity and uncertainty in oversight for minimizing financial burdens on small product developers; consolidating multi-agency jurisdictions to avoid gaps and redundancies in safety reviews; consumer benefits for advancing acceptance of GEO products; rigorous and independent pre- and post-market assessment for environmental safety; early public input and transparency for ensuring public confidence; and the positive role of public input in system development, informed consent, capacity, compliance, incentives, and data requirements and stringency in promoting health and environmental safety outcomes, as well as the equitable distribution of health impacts. Our integrated approach is instructive for more comprehensive analyses of oversight systems, developing hypotheses for how features of oversight systems affect outcomes, and formulating policy options for oversight of future technological products, especially nanotechnology products.
Nationwide telecare for diabetics: a pilot implementation of the HOLON architecture.
Jones, P. C.; Silverman, B. G.; Athanasoulis, M.; Drucker, D.; Goldberg, H.; Marsh, J.; Nguyen, C.; Ravichandar, D.; Reis, L.; Rind, D.; Safran, C.
1998-01-01
This paper presents results from a demonstration project of nationwide exchange of health data for the home care of diabetic patients. A consortium of industry, academic, and health care partners has developed reusable middleware components integrated using the HOLON architecture. Engineering approaches for multi-organization systems development, lessons learned in developing layered object-oriented systems, security and confidentiality considerations, and functionality for nationwide telemedicine applications are discussed. PMID:9929239
Towards a Framework for Modeling Space Systems Architectures
NASA Technical Reports Server (NTRS)
Shames, Peter; Skipper, Joseph
2006-01-01
Topics covered include: 1) Statement of the problem: a) Space system architecture is complex; b) Existing terrestrial approaches must be adapted for space; c) Need a common architecture methodology and information model; d) Need appropriate set of viewpoints. 2) Requirements on a space systems model. 3) Model Based Engineering and Design (MBED) project: a) Evaluated different methods; b) Adapted and utilized RASDS & RM-ODP; c) Identified useful set of viewpoints; d) Did actual model exchanges among selected subset of tools. 4) Lessons learned & future vision.
The Role of Formal Experiment Design in Hypersonic Flight System Technology Development
NASA Technical Reports Server (NTRS)
McClinton, Charles R.; Ferlemann, Shelly M.; Rock, Ken E.; Ferlemann, Paul G.
2002-01-01
Hypersonic airbreathing engine (scramjet) powered vehicles are being considered to replace conventional rocket-powered launch systems. Effective utilization of scramjet engines requires careful integration with the air vehicle. This integration synergistically combines aerodynamic forces with propulsive cycle functions of the engine. Due to the highly integrated nature of the hypersonic vehicle design problem, the large flight envelope, and the large number of design variables, the use of a statistical design approach in design is effective. Modern Design-of-Experiments (MDOE) has been used throughout the Hyper-X program, for both systems analysis and experimental testing. Application of MDOE fall into four categories: (1) experimental testing; (2) studies of unit phenomena; (3) refining engine design; and (4) full vehicle system optimization. The MDOE process also provides analytical models, which are also used to document lessons learned, supplement low-level design tools, and accelerate future studies. This paper will discuss the design considerations for scramjet-powered vehicles, specifics of MDOE utilized for Hyper-X, and present highlights from the use of these MDOE methods within the Hyper-X Program.
Shuttle Transportation System Case-Study Development
NASA Technical Reports Server (NTRS)
Ransom, Khadijah
2012-01-01
A case-study collection was developed for NASA's Space Shuttle Program. Using lessons learned and documented by NASA KSC engineers, analysts, and contractors, decades of information related to processing and launching the Space Shuttle was gathered into a single database. The goal was to provide educators with an alternative means to teach real-world engineering processes and to enhance critical thinking, decision making, and problem solving skills. Suggested formats were created to assist both external educators and internal NASA employees to develop and contribute their own case-study reports to share with other educators and students. Via group project, class discussion, or open-ended research format, students will be introduced to the unique decision making process related to Shuttle missions and development. Teaching notes, images, and related documents will be made accessible to the public for presentation of Space Shuttle reports. Lessons investigated included the engine cutoff (ECO) sensor anomaly which occurred during mission STS-114. Students will be presented with general mission infom1ation as well as an explanation of ECO sensors. The project will conclude with the design of a website that allows for distribution of information to the public as well as case-study report submissions from other educators online.
Project Interface Requirements Process Including Shuttle Lessons Learned
NASA Technical Reports Server (NTRS)
Bauch, Garland T.
2010-01-01
Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings
NASA Technical Reports Server (NTRS)
Watson, Steve; Orr, Jim; O'Neil, Graham
2004-01-01
A mission-systems architecture based on a highly modular "systems of systems" infrastructure utilizing open-standards hardware and software interfaces as the enabling technology is absolutely essential for an affordable and sustainable space exploration program. This architecture requires (a) robust communication between heterogeneous systems, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, and verification of systems, and (e) minimum sustaining engineering. This paper proposes such an architecture. Lessons learned from the space shuttle program are applied to help define and refine the model.
Developing a Virtual Engineering Management Community
ERIC Educational Resources Information Center
Hewitt, Bill; Kidd, Moray; Smith, Robin; Wearne, Stephen
2016-01-01
The paper reviews the lessons of planning and running an "Engineering Management" practitioner development programme in a partnership between BP and the University of Manchester. This distance-learning programme is for professional engineers in mid-career experienced in the engineering and support activities for delivering safe,…
Tissue Engineering of Blood Vessels: Functional Requirements, Progress, and Future Challenges.
Kumar, Vivek A; Brewster, Luke P; Caves, Jeffrey M; Chaikof, Elliot L
2011-09-01
Vascular disease results in the decreased utility and decreased availability of autologus vascular tissue for small diameter (< 6 mm) vessel replacements. While synthetic polymer alternatives to date have failed to meet the performance of autogenous conduits, tissue-engineered replacement vessels represent an ideal solution to this clinical problem. Ongoing progress requires combined approaches from biomaterials science, cell biology, and translational medicine to develop feasible solutions with the requisite mechanical support, a non-fouling surface for blood flow, and tissue regeneration. Over the past two decades interest in blood vessel tissue engineering has soared on a global scale, resulting in the first clinical implants of multiple technologies, steady progress with several other systems, and critical lessons-learned. This review will highlight the current inadequacies of autologus and synthetic grafts, the engineering requirements for implantation of tissue-engineered grafts, and the current status of tissue-engineered blood vessel research.
Preparing synthetic biology for the world
Moe-Behrens, Gerd H. G.; Davis, Rene; Haynes, Karmella A.
2013-01-01
Synthetic Biology promises low-cost, exponentially scalable products and global health solutions in the form of self-replicating organisms, or “living devices.” As these promises are realized, proof-of-concept systems will gradually migrate from tightly regulated laboratory or industrial environments into private spaces as, for instance, probiotic health products, food, and even do-it-yourself bioengineered systems. What additional steps, if any, should be taken before releasing engineered self-replicating organisms into a broader user space? In this review, we explain how studies of genetically modified organisms lay groundwork for the future landscape of biosafety. Early in the design process, biological engineers are anticipating potential hazards and developing innovative tools to mitigate risk. Here, we survey lessons learned, ongoing efforts to engineer intrinsic biocontainment, and how different stakeholders in synthetic biology can act to accomplish best practices for biosafety. PMID:23355834
NASA Technical Reports Server (NTRS)
Podboy, Gary G.; Bridges, James E.; Henderson, Brenda S.
2010-01-01
A 48-microphone planar phased array system was used to acquire jet noise source localization data on both a full-scale F404-GE-F400 engine and on a 1/4th scale model of a F400 series nozzle. The full-scale engine test data show the location of the dominant noise sources in the jet plume as a function of frequency for the engine in both baseline (no chevron) and chevron configurations. Data are presented for the engine operating both with and without afterburners. Based on lessons learned during this test, a set of recommendations are provided regarding how the phased array measurement system could be modified in order to obtain more useful acoustic source localization data on high-performance military engines in the future. The data obtained on the 1/4th scale F400 series nozzle provide useful insights regarding the full-scale engine jet noise source mechanisms, and document some of the differences associated with testing at model-scale versus fullscale.
Bridging the Engineering and Medicine Gap
NASA Technical Reports Server (NTRS)
Walton, M.; Antonsen, E.
2018-01-01
A primary challenge NASA faces is communication between the disparate entities of engineers and human system experts in life sciences. Clear communication is critical for exploration mission success from the perspective of both risk analysis and data handling. The engineering community uses probabilistic risk assessment (PRA) models to inform their own risk analysis and has extensive experience managing mission data, but does not always fully consider human systems integration (HSI). The medical community, as a part of HSI, has been working 1) to develop a suite of tools to express medical risk in quantitative terms that are relatable to the engineering approaches commonly in use, and 2) to manage and integrate HSI data with engineering data. This talk will review the development of the Integrated Medical Model as an early attempt to bridge the communication gap between the medical and engineering communities in the language of PRA. This will also address data communication between the two entities in the context of data management considerations of the Medical Data Architecture. Lessons learned from these processes will help identify important elements to consider in future communication and integration of these two groups.
The military operator's experience of reliability and maintainability characteristics
NASA Astrophysics Data System (ADS)
Jones, R. Mcc.
An account is given of the British Army's approach to the achievement of high reliability and maintainability in rotorcraft during the procurement process. Attention is given to experience accumulated to date with the Gazelle, Scout, Agusta A109A, and Lynx helicopters; these offer lessons with respect to the Gem engine, fuel filtering, vibration, and an aircraft flight control system.
Proceedings of the 2nd NASA Ada User's Symposium
NASA Technical Reports Server (NTRS)
1989-01-01
Several presentations, mostly in viewgraph form, on various topics relating to Ada applications are given. Topics covered include the use of Ada in NASA, Ada and the Space Station, the software support environment, Ada in the Software Engineering Laboratory, Ada at the Jet Propulsion Laboratory, the Flight Telerobotic Servicer, and lessons learned in prototyping the Space Station Remote Manipulator System control.
Systems engineering and integration and management for manned space flight programs
NASA Technical Reports Server (NTRS)
Morris, Owen
1993-01-01
This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.
Systems engineering and integration and management for manned space flight programs
NASA Astrophysics Data System (ADS)
Morris, Owen
This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.
2011-05-01
not integrated Lack of emphasis on implementing ESOH mitigations Failure to address USD (AT&L) hexavalent chrome policy 12 ODUSD(I&E) / CMRM Value of...4.1, Design Considerations Factor 4.1.4, ESOH Factor 4.1.7, Corrosion ( Hexavalent Chromium) 6 ODUSD(I&E) / CMRM 1. Mission Capabilities – Clarity and
Impact of a process improvement program in a production software environment: Are we any better?
NASA Technical Reports Server (NTRS)
Heller, Gerard H.; Page, Gerald T.
1990-01-01
For the past 15 years, Computer Sciences Corporation (CSC) has participated in a process improvement program as a member of the Software Engineering Laboratory (SEL), which is sponsored by GSFC. The benefits CSC has derived from involvement in this program are analyzed. In the environment studied, it shows that improvements were indeed achieved, as evidenced by a decrease in error rates and costs over a period in which both the size and the complexity of the developed systems increased substantially. The principles and mechanics of the process improvement program, the lessons CSC has learned, and how CSC has capitalized on these lessons are also discussed.
Engineering Encounters: Minding Design Missteps
ERIC Educational Resources Information Center
Crismond, David; Gellert, Laura; Cain, Ryan; Wright, Shequana
2013-01-01
The "Next Generation Science Standards" (NGSS) (Achieve Inc. 2013) asks teachers to give engineering design equal standing with scientific inquiry in their science lessons. This article asks the following questions: What do engineering design practices look like, and how do you assess them? How similar and different is engineering design…
Engineered containment and control systems: nurturing nature.
Clarke, James H; MacDonell, Margaret M; Smith, Ellen D; Dunn, R Jeffrey; Waugh, W Jody
2004-06-01
The development of engineered containment and control systems for contaminated sites must consider the environmental setting of each site. The behaviors of both contaminated materials and engineered systems are affected by environmental conditions that will continue to evolve over time as a result of such natural processes as climate change, ecological succession, pedogenesis, and landform changes. Understanding these processes is crucial to designing, implementing, and maintaining effective systems for sustained health and environmental protection. Traditional engineered systems such as landfill liners and caps are designed to resist natural processes rather than working with them. These systems cannot be expected to provide long-term isolation without continued maintenance. In some cases, full-scale replacement and remediation may be required within 50 years, at an effort and cost much higher than for the original cleanup. Approaches are being developed to define smarter containment and control systems for stewardship sites, considering lessons learned from implementing prescriptive waste disposal regulations enacted since the 1970s. These approaches more effectively involve integrating natural and engineered systems; enhancing sensors and predictive tools for evaluating performance; and incorporating information on failure events, including precursors and consequences, into system design and maintenance. An important feature is using natural analogs to predict environmental conditions and system responses over the long term, to accommodate environmental change in the design process, and, as possible, to engineer containment systems that mimic favorable natural systems. The key emphasis is harmony with the environment, so systems will work with and rely on natural processes rather than resisting them. Implementing these new integrated systems will reduce current requirements for active management, which are resource-intensive and expensive.
LEGO robot vehicle lesson plans for secondary education : a recruitment tool.
DOT National Transportation Integrated Search
2012-08-01
Robotics is a great way to get kids excited about science, technology, engineering, and math (STEM) topics. It is also highly effective in stimulation development of teamwork and self-confidence. This project provides transportation-related lesson pl...
A Historical and Engineering View of Power Transmission Systems in Kansai Electric Power Co., Inc.
NASA Astrophysics Data System (ADS)
Ito, Shunichi; Akiyama, Tetsuo
During our work in operations related to power transmission technology, we have encountered various natural calamities and man-made disasters. Over the years, we learned many valuable lessons from these bitter experiences, and we now have more reliable, cost-effective and flexible electric power systems. This paper describes the new technologies we have introduced in the facilities making up the power systems and how we operate these systems and facilities. It also takes up the Southern Hyogo Earthquake and loss of Ohi nuclear power generation due to galloping phenomena as typical examples showing how a set of measures as mentioned above substantially improved the reliability of the electric power systems to such an extent that the Japanese electric power systems have attained the world's highest level of reliability. These facts prove that steady and continuous efforts are a prerequisite to success for all power engineers.
ERIC Educational Resources Information Center
Gero, Aharon
2017-01-01
A course entitled "Science and Engineering Education: Interdisciplinary Aspects" was designed to expose undergraduate students of science and engineering education to the attributes of interdisciplinary education which integrates science and engineering. The core of the course is an interdisciplinary lesson, which each student is…
A Contemporary Preservice Technology Education Program
ERIC Educational Resources Information Center
Flanigan, Rod; Becker, Kurt; Stewardson, Gary
2012-01-01
In order to teach engineering education, today's engineering and technology education teachers must be equipped with lesson plans to teach engineering design, among other principles, to the 6th-12th grade levels. At Utah State University (USU), curriculum has been developed for preservice engineering and technology education teachers that…
How Engineers Engineer: Lessons from My First Big Engineering Project
ERIC Educational Resources Information Center
Roman, Harry T.
2008-01-01
Little did the author realize how much his first engineering project would change his career path, but when it came, he was hooked forever on doing R&D-type engineering. In this article, the author takes the reader back to his first really important electrical engineering project. While the technology he worked on back then is antiquated by…
Advancing the practice of systems engineering at JPL
NASA Technical Reports Server (NTRS)
Jansma, Patti A.; Jones, Ross M.
2006-01-01
In FY 2004, JPL launched an initiative to improve the way it practices systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to "significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks." The scope of the SEA Project includes the systems engineering work performed in all three dimensions of a program, project, or task: 1. the full life-cycle, i.e., concept through end of operations 2. the full depth, i.e., Program, Project, System, Subsystem, Element (SE Levels 1 to 5) 3. the full technical scope, e.g., the flight, ground and launch systems, avionics, power, propulsion, telecommunications, thermal, etc. The initial focus of their efforts defined the following basic systems engineering functions at JPL: systems architecture, requirements management, interface definition, technical resource management, system design and analysis, system verification and validation, risk management, technical peer reviews, design process management and systems engineering task management, They also developed a list of highly valued personal behaviors of systems engineers, and are working to inculcate those behaviors into members of their systems engineering community. The SEA Project is developing products, services, and training to support managers and practitioners throughout the entire system lifecycle. As these are developed, each one needs to be systematically deployed. Hence, the SEA Project developed a deployment process that includes four aspects: infrastructure and operations, communication and outreach, education and training, and consulting support. In addition, the SEA Project has taken a proactive approach to organizational change management and customer relationship management - both concepts and approaches not usually invoked in an engineering environment. This paper'3 describes JPL's approach to advancing the practice of systems engineering at the Lab. It describes the general approach used and how they addressed the three key aspects of change: people, process and technology. It highlights a list of highly valued personal behaviors of systems engineers, discusses the various products, services and training that were developed, describes the deployment approach used, and concludes with several lessons learned.
Driving the bumpy road to commercialization.
Parenteau, Nancy L
2014-06-01
Tissue engineering has always had an applied focus and there is hardly an academic publication that does not mention the applicability of its findings to the future development of a medical product. I have been involved in the industry side of tissue engineering from the start, pursuing a variety of applications, some making it to the marketplace. There have been many lessons that I have learned from direct experience (mistakes and successes), observation, through advising others, and now, in developing innovative ways to identify and eliminate the regenerative cell populations within a tumor. This brief overview of some of these lessons is written with the next generation of pioneering product developers in mind: the biologists, biochemists, and engineers who will dedicate their careers to driving medical and commercial progress in tissue engineering.
2011-09-01
unknown • Assumed to be bigger than Legitimate Market • Security firms pay for security flaws • Example: Netragard (a cybersecurity firm) pays between... RESEARCE Does this research involve Human Subject Research? Y fl N X If yes, list protocol number(s) here and in blook l1 of Form 298, in thesis If yes, have
On the leading edge; Combining maturity and advanced technology on the F404 turbofan engine
DOE Office of Scientific and Technical Information (OSTI.GOV)
Powel, S.F. IV
1991-01-01
In this paper the overall design concept of the F404 afterburning turbofan engine is reviewed together with some of the lessons learned from over 2 million flight hours in service. GE Aircraft Engines' derivative and growth plans for the F404 family are then reviewed including the Building Block component development approach. Examples of advanced technologies under development for introduction into new F404 derivative engine models are presented in the areas of materials, digital and fiber optic controls systems, and vectoring exhaust nozzles. The design concept and details of the F404-GE-402, F412-GE-400, and other derivative engines under full-scale development are described.more » Studies for future growth variants and the benefits of the F404 derivative approach to development of afterburning engines in the 18,000-24,000 lb (80--107 kN) thrust class and non- afterburning engines in the 12,000--19,000 lb (53--85 kN) class are discussed.« less
Biomimicry as a route to new materials: what kinds of lessons are useful?
Reed, Emily J; Klumb, Lisa; Koobatian, Maxwell; Viney, Christopher
2009-04-28
We consider the attributes of a successful engineered material, acknowledging the contributions of composition and processing to properties and performance. We recognize the potential for relevant lessons to be learned from nature, at the same time conceding both the limitations of such lessons and our need to be selective. We then give some detailed attention to the molecular biomimicry of filamentous phage, the process biomimicry of silk and the structure biomimicry of hippopotamus 'sweat', in each case noting that the type of lesson now being learned is not the same as the potential lesson that originally motivated the study.
Knowledge-based assistance in costing the space station DMS
NASA Technical Reports Server (NTRS)
Henson, Troy; Rone, Kyle
1988-01-01
The Software Cost Engineering (SCE) methodology developed over the last two decades at IBM Systems Integration Division (SID) in Houston is utilized to cost the NASA Space Station Data Management System (DMS). An ongoing project to capture this methodology, which is built on a foundation of experiences and lessons learned, has resulted in the development of an internal-use-only, PC-based prototype that integrates algorithmic tools with knowledge-based decision support assistants. This prototype Software Cost Engineering Automation Tool (SCEAT) is being employed to assist in the DMS costing exercises. At the same time, DMS costing serves as a forcing function and provides a platform for the continuing, iterative development, calibration, and validation and verification of SCEAT. The data that forms the cost engineering database is derived from more than 15 years of development of NASA Space Shuttle software, ranging from low criticality, low complexity support tools to highly complex and highly critical onboard software.
A study of the portability of an Ada system in the software engineering laboratory (SEL)
NASA Technical Reports Server (NTRS)
Jun, Linda O.; Valett, Susan Ray
1990-01-01
A particular porting effort is discussed, and various statistics on analyzing the portability of Ada and the total staff months (overall and by phase) required to accomplish the rehost, are given. This effort is compared to past experiments on the rehosting of FORTRAN systems. The discussion includes an analysis of the types of errors encountered during the rehosting, the changes required to rehost the system, experiences with the Alsys IBM Ada compiler, the impediments encountered, and the lessons learned during this study.
The Habitat Demonstration Unit Project: A Modular Instrumentation System for a Deep Space Habitat
NASA Technical Reports Server (NTRS)
Rojdev, Kristina; Kennedy, Kriss J.; Yim, Hester; Williamsn, Robert M.; Hafermalz, Scott; Wagner, Raymond S.
2011-01-01
NASA is focused on developing human exploration capabilities in low Earth orbit (LEO), expanding to near Earth asteroids (NEA), and finally to Mars. Habitation is a crucial aspect of human exploration, and a current focus of NASA activities. The Habitation Demonstration Unit (HDU) is a project focused on developing an autonomous habitation system that enables human exploration of space by providing engineers and scientists with a test bed to develop, integrate, test, and evaluate habitation systems. A critical feature of the HDU is the instrumentation system, which monitors key subsystems within the habitat. The following paper will discuss the HDU instrumentation system performance and lessons learned during the 2010 Desert Research and Technology Studies (D-RaTS). In addition, this paper will discuss the evolution of the instrumentation system to support the 2011 Deep Space Habitat configuration, the challenges, and the lessons learned of implementing this configuration. In 2010, the HDU was implemented as a pressurized excursion module (PEM) and was tested at NASA s D-RaTS in Arizona [1]. For this initial configuration, the instrumentation system design used features that were successful in previous habitat instrumentation projects, while also considering challenges, and implementing lessons learned [2]. The main feature of the PEM instrumentation system was the use of a standards-based wireless sensor node (WSN), implementing an IEEE 802.15.4 protocol. Many of the instruments were connected to several WSNs, which wirelessly transmitted data to the command and data handling system via a mesh network. The PEM instrumentation system monitored the HDU during field tests at D-RaTS, and the WSN data was later analyzed to understand the performance of this system. In addition, several lessons learned were gained from the field test experience, which fed into the instrumentation design of the next generation of the HDU.
Management and systems engineering of the Kepler mission
NASA Astrophysics Data System (ADS)
Fanson, James; Livesay, Leslie; Frerking, Margaret; Cooke, Brian
2010-07-01
Kepler is the National Aeronautics and Space Administration's (NASA's) first mission capable of detecting Earth-size planets orbiting in the habitable zones around stars other than the sun. Selected for implementation in 2001 and launched in 2009, Kepler seeks to determine whether Earth-like planets are common or rare in the galaxy. The investigation requires a large, space-based photometer capable of simultaneously measuring the brightnesses of 100,000 stars at partper- million level of precision. This paper traces the development of the mission from the perspective of project management and systems engineering and describes various methodologies and tools that were found to be effective. The experience of the Kepler development is used to illuminate lessons that can be applied to future missions.
Management and Systems Engineering of the Kepler Mission
NASA Technical Reports Server (NTRS)
Fanson, James; Livesay, Leslie; Frerking, Margaret; Cooke, Brian
2010-01-01
Kepler is the National Aeronautics and Space Administration's (NASA's) first mission capable of detecting Earth-size planets orbiting in the habitable zones around stars other than the sun. Selected for implementation in 2001 and launched in 2009, Kepler seeks to determine whether Earth-like planets are common or rare in the galaxy. The investigation requires a large, space-based photometer capable of simultaneously measuring the brightnesses of 100,000 stars at part-per-million level of precision. This paper traces the development of the mission from the perspective of project management and systems engineering and describes various methodologies and tools that were found to be effective. The experience of the Kepler development is used to illuminate lessons that can be applied to future missions.
Development and qualification of the US Cruise Missile Propulsion System
NASA Astrophysics Data System (ADS)
Reardon, William H.; Cifone, Anthony J.
1992-09-01
This paper provides a description of the very successful Cruise Missile gas turbine propulsion program managed by the United States Department of Defense. The paper contains a summary of the procurement process, the technical and programmatic milestones, issues and challenges, and lessons learned. In the past fifteen years, testing at the Naval Air Propulsion Center has included over 800 cruise engine development and component substantiation efforts spanning the engine specification qualification requirements. This paper provides a detailed account of environmental test techniques used to qualify the F107 family of gas turbine engines which propel the U.S. Cruise Missile. In addition, a missile freestream flight test simulation for the TOMAHAWK Cruise Missile is discussed along with current and future program efforts.
Unleashing Lessons: Sharing Stories About the Fine Art of Systems Engineering
NASA Technical Reports Server (NTRS)
Singer, Christopher E.
2010-01-01
NASA leaders have a responsibility to share their unique oral histories with junior-level employees on whom NASA's future depends. This presentation will give a few examples of how the imaginative, flexible art of systems engineering is as necessary to mission success as is the rigorous, disciplined side of engineering. Engineering space systems involves many disciplines propulsion, loads, dynamics, and so forth that are based on the foundations of scientific principles and methodology and the application of the laws of physics. The term rocket scientist is an apt term, considering that the underlying chemical properties of propellants and the subatomic properties of materials must be understood to harness the powerful energy necessary to escape Earth's gravity in machines that can withstand the stresses and forces to which they are subjected, not to mention the harsh space environments in which they must work. This is a simplistic, yet illustrative, explanation of the scientific side of the engineer s challenge. Bringing together these individual parts into a solid system goes beyond the science of engineering to employ the art of systems engineering. Systems engineers are known for their ability to integrate various solutions to meet or exceed challenging requirements. As the old adage goes, measure twice and cut once. The act of measuring is balancing rigid, inflexible requirements with creative compromises to attain the optimum solution to the challenge of space flight. Then, we cut out those answers that are too risky, expensive, dangerous, and so forth. The process of sharing stories about the little-discussed art of engineering, also known as the art of compromise, will equip the workforce to subjectively judge the best right answer from among the many presented, while objectively integrating the various piece parts into a unified whole.
Licurse, Mindy Y; Lalevic, Darco; Zafar, Hanna M; Schnall, Mitchell D; Cook, Tessa S
2017-04-01
An automated radiology recommendation-tracking engine for incidental focal masses in the liver, pancreas, kidneys, and adrenal glands was launched within our institution in July 2013. For 2 years, the majority of CT, MR, and US examination reports generated within our health system were mined by the engine. However, the need to expand the system beyond the initial four organs was soon identified. In July 2015, the second phase of the system was implemented and expanded to include additional anatomic structures in the abdomen and pelvis, as well as to provide non-radiology and non-imaging options for follow-up. The most frequent organs with incidental findings, outside of the original four, included the ovaries and the endometrium, which also correlated to the most frequently ordered imaging follow-up study of pelvic ultrasound and non-imaging follow-up study of endometrial biopsies, respectively. The second phase expansion has demonstrated new venues for augmenting and improving radiologist roles in optimal communication and management of incidental findings.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Lackey, Michael B.; Waisley, Sandra L.; Dusek, Lansing G.
2007-07-01
Approximately $153.2 billion of work currently remains in the United States Department of Energy's (DOE's) Office of Environmental Management (EM) life cycle budget for United States projects. Contractors who manage facilities for the DOE have been challenged to identify transformational changes to reduce the life cycle costs and develop a knowledge management system that identifies, disseminates, and tracks the implementation of lessons learned and best practices. At the request of the DOE's EM Office of Engineering and Technology, the Energy Facility Contractors Group (EFCOG) responded to the challenge with formation of the Deactivation and Decommissioning (D and D) and Facilitymore » Engineering (DD/FE) Working Group. Since October 2006, members have already made significant progress in realizing their goals: adding new D and D best practices to the existing EFCOG Best Practices database; participating in lessons learned forums; and contributing to a DOE initiative on identifying technology needs. The group is also participating in a DOE project management initiative to develop implementation guidelines, as well as a DOE radiation protection initiative to institute a more predictable and standardized approach to approving authorized limits and independently verifying cleanup completion at EM sites. Finally, a D and D hotline to provide real-time solutions to D and D challenges is also being launched. (authors)« less
Reliability and Maintainability Engineering - A Major Driver for Safety and Affordability
NASA Technical Reports Server (NTRS)
Safie, Fayssal M.
2011-01-01
The United States National Aeronautics and Space Administration (NASA) is in the midst of an effort to design and build a safe and affordable heavy lift vehicle to go to the moon and beyond. To achieve that, NASA is seeking more innovative and efficient approaches to reduce cost while maintaining an acceptable level of safety and mission success. One area that has the potential to contribute significantly to achieving NASA safety and affordability goals is Reliability and Maintainability (R&M) engineering. Inadequate reliability or failure of critical safety items may directly jeopardize the safety of the user(s) and result in a loss of life. Inadequate reliability of equipment may directly jeopardize mission success. Systems designed to be more reliable (fewer failures) and maintainable (fewer resources needed) can lower the total life cycle cost. The Department of Defense (DOD) and industry experience has shown that optimized and adequate levels of R&M are critical for achieving a high level of safety and mission success, and low sustainment cost. Also, lessons learned from the Space Shuttle program clearly demonstrated the importance of R&M engineering in designing and operating safe and affordable launch systems. The Challenger and Columbia accidents are examples of the severe impact of design unreliability and process induced failures on system safety and mission success. These accidents demonstrated the criticality of reliability engineering in understanding component failure mechanisms and integrated system failures across the system elements interfaces. Experience from the shuttle program also shows that insufficient Reliability, Maintainability, and Supportability (RMS) engineering analyses upfront in the design phase can significantly increase the sustainment cost and, thereby, the total life cycle cost. Emphasis on RMS during the design phase is critical for identifying the design features and characteristics needed for time efficient processing, improved operational availability, and optimized maintenance and logistic support infrastructure. This paper discusses the role of R&M in a program acquisition phase and the potential impact of R&M on safety, mission success, operational availability, and affordability. This includes discussion of the R&M elements that need to be addressed and the R&M analyses that need to be performed in order to support a safe and affordable system design. The paper also provides some lessons learned from the Space Shuttle program on the impact of R&M on safety and affordability.
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.
Seal Technology for Hypersonic Vehicle and Propulsion: An Overview
NASA Technical Reports Server (NTRS)
Steinetz, Bruce M.
2008-01-01
Hypersonic vehicles and propulsion systems pose an extraordinary challenge for structures and materials. Airframes and engines require lightweight, high-temperature materials and structural configurations that can withstand the extreme environment of hypersonic flight. Some of the challenges posed include very high temperatures, heating of the whole vehicle, steady-state and transient localized heating from shock waves, high aerodynamic loads, high fluctuating pressure loads, potential for severe flutter, vibration, and acoustic loads and erosion. Correspondingly high temperature seals are required to meet these aggressive requirements. This presentation reviews relevant seal technology for both heritage (e.g. Space Shuttle, X-15, and X-38) vehicles and presents several seal case studies aimed at providing lessons learned for future hypersonic vehicle seal development. This presentation also reviews seal technology developed for the National Aerospace Plane propulsion systems and presents several seal case studies aimed at providing lessons learned for future hypersonic propulsion seal development.
Developing a virtual engineering management community
NASA Astrophysics Data System (ADS)
Hewitt, Bill; Kidd, Moray; Smith, Robin; Wearne, Stephen
2016-03-01
The paper reviews the lessons of planning and running an Engineering Management practitioner development programme in a partnership between BP and the University of Manchester. This distance-learning programme is for professional engineers in mid-career experienced in the engineering and support activities for delivering safe, compliant and reliable projects and operations worldwide. The programme concentrates on the why and how of leadership and judgement in managing the engineering of large and small projects and operational support. Two intensive residential weeks are combined with a virtual learning environment over one year. Assessed assignments between and after the residential weeks provide opportunities for individual reflective learning for each delegate through applying concepts and the lessons of case studies to their experience, current challenges and expected responsibilities. This successful partnership between a major global company and a university rich in research and teaching required a significant dedication of intellectual and leadership effort by all concerned. The rewards for both parties and most importantly for the engineers themselves are extensive.
Achieving Operability via the Mission System Paradigm
NASA Technical Reports Server (NTRS)
Hammer, Fred J.; Kahr, Joseph R.
2006-01-01
In the past, flight and ground systems have been developed largely-independently, with the flight system taking the lead, and dominating the development process. Operability issues have been addressed poorly in planning, requirements, design, I&T, and system-contracting activities. In many cases, as documented in lessons-learned, this has resulted in significant avoidable increases in cost and risk. With complex missions and systems, operability is being recognized as an important end-to-end design issue. Never-the-less, lessons-learned and operability concepts remain, in many cases, poorly understood and sporadically applied. A key to effective application of operability concepts is adopting a 'mission system' paradigm. In this paradigm, flight and ground systems are treated, from an engineering and management perspective, as inter-related elements of a larger mission system. The mission system consists of flight hardware, flight software, telecom services, ground data system, testbeds, flight teams, science teams, flight operations processes, procedures, and facilities. The system is designed in functional layers, which span flight and ground. It is designed in response to project-level requirements, mission design and an operations concept, and is developed incrementally, with early and frequent integration of flight and ground components.
Proceedings of the Seventeenth Annual Software Engineering Workshop
NASA Technical Reports Server (NTRS)
1992-01-01
Proceedings of the Seventeenth Annual Software Engineering Workshop are presented. The software Engineering Laboratory (SEL) is an organization sponsored by NASA/Goddard Space Flight Center and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. Topics covered include: the Software Engineering Laboratory; process measurement; software reuse; software quality; lessons learned; and is Ada dying.
ERIC Educational Resources Information Center
Donaldson, Krista M.; Chen, Helen L.; Toye, George; Sheppard, Sheri D.
2007-01-01
The Academic Pathways of People Learning Engineering Survey (APPLES or APPLE survey) is a component of the Academic Pathways Study (APS) of the Center for the Advancement of Engineering Education (CAEE). The APS aims to provide a comprehensive account of how people become engineers by exploring key questions around the engineering learning…
NASA Astrophysics Data System (ADS)
Hogue, T. S.; Burke, M. P.; Thulsirag, V.; Daniel, J.; Moldwin, M.; Nonacs, P.
2010-12-01
A National Science Foundation Graduate Teaching Fellows in K- 12 Education program at UCLA (SEE-LA; http://measure.igpp.ucla.edu/GK12-SEE-LA/ ) partners UCLA faculty and graduate students (fellows) with urban middle and high school science teachers and their students to foster programs of science and engineering exploration that bring the environment of Los Angeles into the classroom. UCLA graduate fellows serve as scientists-in-residence at four partner schools to integrate inquiry-based science lessons, facilitate advancements in science content teaching, and ultimately, to improve their own science communication skills. As part of their fellowship, graduate students are required to develop inquiry-based lessons in their partner classroom. During the first two years of the project, the SEE-LA fellows have developed a range of inquiry-based activities, from invertebrate observations in an urban stream system, to water and home energy consumption surveys, to a school biodiversity investigation, to a school-wide alternative energy fair, to engineering the cleanup of environmental disasters, such as the recent oil spill in the Gulf of Mexico. Several of the current fellows have dissertation research in water resource related fields and are specifically integrating lessons specific to their research into their partner classrooms, including urban stream water quality, post-fire watershed behavior, beach water quality assessment and E. coli source tracking. This presentation will provide an overview of goals of the SEE-LA GK-12 program, development of inquiry-based water resource lessons and resulting engagement in the partner classrooms. University and local pre-college school partnerships provide an excellent opportunity to support the development of graduate student communication and teaching skills while also contributing significantly to the integration of science education into K-12 curriculum.
ERIC Educational Resources Information Center
Eisenkraft, Arthur
2011-01-01
Current instructional and learning models insist that when teachers prepare lessons for their technology and engineering classes, they must begin with a sense of what students already know. In preparing lessons, many teachers use their years of classroom experience as data to inform them about students' prior knowledge and about student…
Standards Advisor-Advanced Information Technology for Advanced Information Delivery
NASA Technical Reports Server (NTRS)
Hawker, J. Scott
2003-01-01
Developers of space systems must deal with an increasing amount of information in responding to extensive requirements and standards from numerous sources. Accessing these requirements and standards, understanding them, comparing them, negotiating them and responding to them is often an overwhelming task. There are resources to aid the space systems developer, such as lessons learned and best practices. Again, though, accessing, understanding, and using this information is often more difficult than helpful. This results in space systems that: 1. Do not meet all their requirements. 2. Do not incorporate prior engineering experience. 3. Cost more to develop. 4. Take longer to develop. The NASA Technical Standards Program (NTSP) web site at http://standards.nasa.gov has made significant improvements in making standards, lessons learned, and related material available to space systems developers agency-wide. The Standards Advisor was conceived to take the next steps beyond the current product, continuing to apply evolving information technology that continues to improve information delivery to space systems developers. This report describes the features of the Standards Advisor and suggests a technical approach to its development.
2009-04-16
Aeronautics Technical Seminar: Dr. Elisabeth Pate-Cornell, Burt and Deedee McMurtry professor and chair of the Department of Management Science and Engineering at Stanford University presents 'Lessons Learned in Applying Engineering Risk Analysis'.
2009-04-16
Aeronautics Technical Seminar: Dr. Elisabeth Pate-Cornell, Burt and Deedee McMurtry professor and chair of the Department of Management Science and Engineering at Stanford University presents 'Lessons Learned in Applying Engineering Risk Analysis'.
2009-04-16
Aeronautics Technical Seminar: Dr. Elisabeth Pate-Cornell, Burt and Deedee McMurtry professor and chair of the Department of Management Science and Engineering at Stanford University presents 'Lessons Learned in Applying Engineering Risk Analysis'.
2009-04-16
Aeronautics Technical Seminar: Dr. Elisabeth Pate-Cornell, Burt and Deedee McMurtry professor and chair of the Department of Management Science and Engineering at Stanford University presents 'Lessons Learned in Applying Engineering Risk Analysis'.
2009-04-16
Aeronautics Technical Seminar: Dr. Elisabeth Pate-Cornell, Burt and Deedee McMurtry professor and chair of the Department of Management Science and Engineering at Stanford University presents 'Lessons Learned in Applying Engineering Risk Analysis'.
ERIC Educational Resources Information Center
Manpower Administration (DOL), Washington, DC. Job Corps.
This self-study program for the high-school level contains lessons in the following subjects: Plants and Photosynthesis; The Human Digestive System; Functions of the Blood; Human Circulation and Respiration; Reproduction of a Single Cell; Reproduction by Male and Female Cells; The Human Reproductive System; Genetics and Heredity; The Nervous…
Orion Flight Performance Design Trades
NASA Technical Reports Server (NTRS)
Jackson, Mark C.; Straube, Timothy
2010-01-01
A significant portion of the Orion pre-PDR design effort has focused on balancing mass with performance. High level performance metrics include abort success rates, lunar surface coverage, landing accuracy and touchdown loads. These metrics may be converted to parameters that affect mass, such as ballast for stabilizing the abort vehicle, propellant to achieve increased lunar coverage or extended missions, or ballast to increase the lift-to-drag ratio to improve entry and landing performance. The Orion Flight Dynamics team was tasked to perform analyses to evaluate many of these trades. These analyses not only provide insight into the physics of each particular trade but, in aggregate, they illustrate the processes used by Orion to balance performance and mass margins, and thereby make design decisions. Lessons learned can be gleaned from a review of these studies which will be useful to other spacecraft system designers. These lessons fall into several categories, including: appropriate application of Monte Carlo analysis in design trades, managing margin in a highly mass-constrained environment, and the use of requirements to balance margin between subsystems and components. This paper provides a review of some of the trades and analyses conducted by the Flight Dynamics team, as well as systems engineering lessons learned.
The Network Operations Control Center upgrade task: Lessons learned
NASA Technical Reports Server (NTRS)
Sherif, J. S.; Tran, T.-L.; Lee, S.
1994-01-01
This article synthesizes and describes the lessons learned from the Network Operations Control Center (NOCC) upgrade project, from the requirements phase through development and test and transfer. At the outset, the NOCC upgrade was being performed simultaneously with two other interfacing and dependent upgrades at the Signal Processing Center (SPC) and Ground Communications Facility (GCF), thereby adding a significant measure of complexity to the management and overall coordination of the development and transfer-to-operations (DTO) effort. Like other success stories, this project carried with it the traditional elements of top management support and exceptional dedication of cognizant personnel. Additionally, there were several NOCC-specific reasons for success, such as end-to-end system engineering, adoption of open-system architecture, thorough requirements management, and use of appropriate off-the-shelf technologies. On the other hand, there were several difficulties, such as ill-defined external interfaces, transition issues caused by new communications protocols, ambivalent use of two sets of policies and standards, and mistailoring of the new JPL management standard (due to the lack of practical guidelines). This article highlights the key lessons learned, as a means of constructive suggestions for the benefit of future projects.
Two Approaches to Engineering Design:Observations in sTEm Education
ERIC Educational Resources Information Center
Kelley, Todd R.; Brenner, Daniel C.; Pieper, Jon T.
2010-01-01
A comparative study was conducted to compare two approaches to engineering design curriculum across different schools (inter-school) and across two curricula "Project Lead the Way and Engineering Projects in Community Service" (inter-curricula). The researchers collected curricula material including handouts, lesson plans, guides,…
NASA Astrophysics Data System (ADS)
Ott, Melanie N.; Switzer, Robert; Chuska, Richard; LaRocca, Frank; Thomes, William J.; Day, Lance W.; MacMurphy, Shawn
2017-11-01
The United States, National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC), 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 assemblies for the Lunar Reconnaissance Orbiter (LRO). The two new assemblies that were designed and manufacturing at NASA GSFC for the LRO exist in configurations that are unique in the world for the application of ranging and lidar. These assemblies were developed in coordination with Diamond Switzerland, and the NASA GSFC Mechanical Systems Division. The assemblies represent a strategic enhancement for NASA's Laser Ranging and Laser Radar (LIDAR) instrument hardware by allowing light to be moved to alternative locations that were not feasible in past space flight implementations. An account will be described 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. The LRO is scheduled to launch end of 2008.
Naval Postgraduate School Research. Volume 14, Number 1, February 2004
2004-02-01
PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER 5e . TASK NUMBER 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES...this review were to ensure officers continue to receive high quality, relevant, and responsive graduate education aligned to defense needs...Initiative (COSSI), Earned Value Management System (EVMS), Activity-Based Costing (ABC), Value Engineering, and lessons from R-TOC Pilots. Sponsored
2011-05-01
fuel oxygenate MBTE Adapted from Davis, 2007 4 ( 1 ) A multimedia environmental perspective built on a product life cycle framework is essential. (2...Picatinney Arsenal Nanotechnology Research Center: Radiofrequency (RF) Induction Plasma reactor (Tekna Plasma Systems) pilot plant Synthesis Challenges: ( 1 ...Genotoxicity in vivo and in vitro, secondary to ROS (?)23 BUILDING STRONG® CEA: Lessons Learned with fuel oxygenate MBTE Adapted from Davis, 2007 24 ( 1
NASA Ares I Launch Vehicle Roll and Reaction Control Systems Lessons Learned
NASA Technical Reports Server (NTRS)
Butt, Adam; Popp, Chris G.; Jernigan, Frankie R.; Paseur, Lila F.; Pitts, Hank M.
2011-01-01
On April 15, 2010 President Barak Obama made the official announcement that the Constellation Program, which included the Ares I launch vehicle, would be canceled. NASA s Ares I launch vehicle was being designed to launch the Orion Crew Exploration Vehicle, returning humans to the moon, Mars, and beyond. It consisted of a First Stage (FS) five segment solid rocket booster and a liquid J-2X Upper Stage (US) engine. Roll control for the FS was planned to be handled by a dedicated Roll Control System (RoCS), located on the connecting interstage. Induced yaw or pitch moments experienced during FS ascent would have been handled by vectoring of the booster nozzle. After FS booster separation, the US Reaction Control System (ReCS) would have provided the US Element with three degrees of freedom control as needed. The lessons learned documented in this paper will be focused on the technical designs and producibility of both systems along with the partnership between NASA and Boeing, who was on contract to build the Ares I US Element, which included the FS RoCS and US ReCS. In regards to partnership, focus will be placed on integration along with technical work accomplished by Boeing with special emphasis on each task order. In summary, this paper attempts to capture key lessons learned that should be helpful in the development of future launch vehicle RCS designs.
NASA Astrophysics Data System (ADS)
Mignone, B. K.
2008-12-01
Effective solutions to the climate change problem will require unprecedented cooperation across space, continuity across time and coordination between disciplines. One well-known methodology for synthesizing the lessons of physical science, energy engineering and economics is integrated assessment. Typically, integrated assessment models use scientific and technological relationships as physical constraints in a larger macroeconomic optimization that is designed to either balance the costs and benefits of climate change mitigation or find the least-cost path to an exogenously prescribed endpoint (e.g. atmospheric CO2 stabilization). The usefulness of these models depends to a large extent on the quality of the assumptions and the relevance of the outcome metrics chosen by the user. In this study, I show how a scientifically-based emissions reduction scenario can be combined with engineering-based assumptions about the energy system (e.g. estimates of the marginal cost premium of carbon-free technology) to yield insights about the price path of CO2 under a future regulatory regime. I then show how this outcome metric (carbon price) relates to key decisions about the design of a future cap-and-trade system and the way in which future carbon markets may be regulated.
Gabbard, Joseph L.; Shukla, Maulik; Sobral, Bruno
2010-01-01
Systems biology and infectious disease (host-pathogen-environment) research and development is becoming increasingly dependent on integrating data from diverse and dynamic sources. Maintaining integrated resources over long periods of time presents distinct challenges. This paper describes experiences and lessons learned from integrating data in two five-year projects focused on pathosystems biology: the Pathosystems Resource Integration Center (PATRIC, http://patric.vbi.vt.edu/), with a goal of developing bioinformatics resources for the research and countermeasures development communities based on genomics data, and the Resource Center for Biodefense Proteomics Research (RCBPR, http://www.proteomicsresource.org/), with a goal of developing resources based on the experiment data such as microarray and proteomics data from diverse sources and technologies. Some challenges include integrating genomic sequence and experiment data, data synchronization, data quality control, and usability engineering. We present examples of a variety of data integration problems drawn from our experiences with PATRIC and RBPRC, as well as open research questions related to long term sustainability, and describe the next steps to meeting these challenges. Novel contributions of this work include (1) an approach for addressing discrepancies between experiment results and interpreted results and (2) expanding the range of data integration techniques to include usability engineering at the presentation level. PMID:20491070
Engineering Design for Engineering Design: Benefits, Models, and Examples from Practice
ERIC Educational Resources Information Center
Turner, Ken L., Jr.; Kirby, Melissa; Bober, Sue
2016-01-01
Engineering design, a framework for studying and solving societal problems, is a key component of STEM education. It is also the area of greatest challenge within the Next Generation Science Standards, NGSS. Many teachers feel underprepared to teach or create activities that feature engineering design, and integrating a lesson plan of core content…
Capturing flight system test engineering expertise: Lessons learned
NASA Technical Reports Server (NTRS)
Woerner, Irene Wong
1991-01-01
Within a few years, JPL will be challenged by the most active mission set in history. Concurrently, flight systems are increasingly more complex. Presently, the knowledge to conduct integration and test of spacecraft and large instruments is held by a few key people, each with many years of experience. JPL is in danger of losing a significant amount of this critical expertise, through retirement, during a period when demand for this expertise is rapidly increasing. The most critical issue at hand is to collect and retain this expertise and develop tools that would ensure the ability to successfully perform the integration and test of future spacecraft and large instruments. The proposed solution was to capture and codity a subset of existing knowledge, and to utilize this captured expertise in knowledge-based systems. First year results and activities planned for the second year of this on-going effort are described. Topics discussed include lessons learned in knowledge acquisition and elicitation techniques, life-cycle paradigms, and rapid prototyping of a knowledge-based advisor (Spacecraft Test Assistant) and a hypermedia browser (Test Engineering Browser). The prototype Spacecraft Test Assistant supports a subset of integration and test activities for flight systems. Browser is a hypermedia tool that allows users easy perusal of spacecraft test topics. A knowledge acquisition tool called ConceptFinder which was developed to search through large volumes of data for related concepts is also described and is modified to semi-automate the process of creating hypertext links.
ERIC Educational Resources Information Center
DeFina, Anthony V.
2017-01-01
To promote teaching science through inquiry, the author wanted to use his experience in the Galápagos to design a lesson that allows students to immerse themselves in the essential science and engineering practices identified in the "Next Generation Science Standards," as they ask questions; analyze and interpret data; engage in argument…
STEM Integration through Design and Inquiry
ERIC Educational Resources Information Center
Johns, Gary; Mentzer, Nathan
2016-01-01
Teachers can find opportunities to incorporate design thinking and scientific inquiry within any lesson where a constraint of the design can be connected to a scientific experiment. Within a lesson, this connection establishes context between engineering and science and can positively impact students' learning and interest in these subjects. The…
Alcohol Fuel By-Product Utilization and Production.
ERIC Educational Resources Information Center
Boerboom, Jim
Ten lessons comprise this curriculum intended to assist vocational teachers in establishing and conducting an alcohol fuels workshop on engine modification and plant design. A glossary is provided first. The 10 lessons cover these topics: the alcohol fuel plant, feedstock preparation lab, distillation lab, fuel plant processes, plant design lab,…
Adoptive immunotherapy for cancer.
Ruella, Marco; Kalos, Michael
2014-01-01
Recent clinical success has underscored the potential for immunotherapy based on the adoptive cell transfer (ACT) of engineered T lymphocytes to mediate dramatic, potent, and durable clinical responses. This success has led to the broader evaluation of engineered T-lymphocyte-based adoptive cell therapy to treat a broad range of malignancies. In this review, we summarize concepts, successes, and challenges for the broader development of this promising field, focusing principally on lessons gleaned from immunological principles and clinical thought. We present ACT in the context of integrating T-cell and tumor biology and the broader systemic immune response. © 2013 John Wiley & Sons A/S. Published by John Wiley & Sons Ltd.
Stationary Engineering Laboratory Manual--2.
ERIC Educational Resources Information Center
Steingress, Frederick M.; Frost, Harold J.
The Stationary Engineering Laboratory Manual 2 was designed for vocational/technical high school students who have received instruction in the basics of stationary engineering. It was developed for students who will be operating a live plant and who will be responsible for supplying steam for heating, cooking, and baking. Each lesson in the manual…
How Engineering Standards Are Interpreted and Translated for Middle School
ERIC Educational Resources Information Center
Judson, Eugene; Ernzen, John; Krause, Stephen; Middleton, James A.; Culbertson, Robert J.
2016-01-01
In this exploratory study we examined the alignment of Next Generation Science Standards (NGSS) middle school engineering design standards with lesson ideas from middle school teachers, science education faculty, and engineering faculty (4-6 members per group). Respondents were prompted to provide plain language interpretations of two middle…
Facilitating an Elementary Engineering Design Process Module
ERIC Educational Resources Information Center
Hill-Cunningham, P. Renee; Mott, Michael S.; Hunt, Anna-Blair
2018-01-01
STEM education in elementary school is guided by the understanding that engineering represents the application of science and math concepts to make life better for people. The Engineering Design Process (EDP) guides the application of creative solutions to problems. Helping teachers understand how to apply the EDP to create lessons develops a…
System engineering and science projects: lessons from MeerKAT
NASA Astrophysics Data System (ADS)
Kapp, Francois
2016-08-01
The Square Kilometre Array (SKA) is a large science project planning to commence construction of the world's largest Radio Telescope after 2018. MeerKAT is one of the precursor projects to the SKA, based on the same site that will host the SKA Mid array in the central Karoo area of South Africa. From the perspective of signal processing hardware development, we analyse the challenges that MeerKAT encountered and extrapolate them to SKA in order to prepare the System Engineering and Project Management methods that could contribute to a successful completion of SKA. Using the MeerKAT Digitiser, Correlator/Beamformer and Time and Frequency Reference Systems as an example, we will trace the risk profile and subtle differences in engineering approaches of these systems over time and show the effects of varying levels of System Engineering rigour on the evolution of their risk profiles. It will be shown that the most rigorous application of System Engineering discipline resulted in the most substantial reduction in risk over time. Since the challenges faced by SKA are not limited to that of MeerKAT, we also look into how that translates to a system development where there is substantial complexity in both the created system as well as the creating system. Since the SKA will be designed and constructed by consortia made up from the ten member countries, there are many additional complexities to the organisation creating the system - a challenge the MeerKAT project did not encounter. Factors outside of engineering, for instance procurement models and political interests, also play a more significant role, and add to the project risks of SKA when compared to MeerKAT.
The Nutating Engine-Prototype Engine Progress Report and Test Results
NASA Technical Reports Server (NTRS)
Meitner, Peter L.; Boruta, Mike
2006-01-01
A prototype of a new, internal combustion (IC) engine concept has been completed. The Nutating Engine features an internal disk nutating (wobbling) on a Z-shaped power shaft. The engine is exceedingly compact, and several times more power dense than any conventional (reciprocating or rotary) IC engine. This paper discusses lessons learned during the prototype engine's development and provides details of its construction. In addition, results of the initial performance tests of the various components, as well as the complete engine, are summarized.
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.
NASA Astrophysics Data System (ADS)
Wargo, Brian M.
The New Standards Framework (NRC, 2012) explicitly calls for teachers to engage students in science and engineering practices (SEPs) as they develop knowledge of scientific phenomena and canonical disciplinary ideas. This study analyzed six pre-service secondary science teachers' (PSSSTs') incorporation of SEPs into their planning practices before, during, and after an instructional intervention. The intervention, which was nested into an instructional methods course, supported the PSSSTs by representing the practices they were to engage their own students with. The PSSSTs were then able to decompose and approximate those scientific practices in their lesson planning, thereby developing pedagogical design capacity (PDC). The PSSSTs were interviewed to determine what affordances and constraints they felt when planning for incorporating SEPs into their lesson planning. Analysis of the lesson plans showed that 50% of the PSSSTs incorporated SEPs into their lesson plans when only provided a written description of the SEPs and prompted to do so. During the instructional intervention, 83% of the PSSSTs incorporated SEPs into their lesson plans. After the instructional intervention, the PSSSTs were no longer required to incorporate SEPs into their lesson planning nor were they required to hand in lesson plans for a grade. Instead, they wrote lesson plans for their cooperating teachers and for their own use. Surprisingly, the PSSSTs not only continued to incorporate SEPs into their lessons, but did so more completely by incorporating a diversity of sub-SEPs and more of them in their lessons. This is significant because this may indicate that the instructional intervention has longevity. Interview data suggests that PSSSTs experience both internal and external affordances and constrains when attempting to incorporate SEPs into their lesson planning. Three categories of issues (epistemic, logistical, and curricular) emerged in the results and influence how teachers interact with the SEPs as they plan lessons. This study reiterates the need for teacher educators to engage in instruction that represents aspects of scientific practice, allows for its decomposition, and engages pre-service teachers in approximating those practices.
NASA Astrophysics Data System (ADS)
Wray, Richard B.
1991-12-01
A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.
NASA Technical Reports Server (NTRS)
Wray, Richard B.
1991-01-01
A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.
NASA Technical Reports Server (NTRS)
Gradl, Paul
2016-01-01
NASA Marshall Space Flight Center (MSFC) has been advancing dynamic optical measurement systems, primarily Digital Image Correlation, for extreme environment rocket engine test applications. The Digital Image Correlation (DIC) technology is used to track local and full field deformations, displacement vectors and local and global strain measurements. This technology has been evaluated at MSFC through lab testing to full scale hotfire engine testing of the J-2X Upper Stage engine at Stennis Space Center. It has been shown to provide reliable measurement data and has replaced many traditional measurement techniques for NASA applications. NASA and AMRDEC have recently signed agreements for NASA to train and transition the technology to applications for missile and helicopter testing. This presentation will provide an overview and progression of the technology, various testing applications at NASA MSFC, overview of Army-NASA test collaborations and application lessons learned about Digital Image Correlation.
The Integration of COTS/GOTS within NASA's HST Command and Control System
NASA Technical Reports Server (NTRS)
Pfarr, Thomas; Reis, James E.
2001-01-01
NASA's mission critical Hubble Space Telescope (HST) command and control system has been re-engineered with commercial-off-the-shelf (COTS/GOTS) and minimal custom code. This paper focuses on the design of this new HST Control Center System (CCS) and the lessons learned throughout its development. CCS currently utilizes more than 30 COTS/GOTS products with an additional 1/2 million lines of custom glueware code; the new CCS exceeds the capabilities of the original system while significantly reducing the lines of custom code by more than 50%. The lifecycle of COTS/GOTS products will be examined including the package selection process, evaluation process, and integration process. The advantages, disadvantages, issues, concerns, and lessons learned for integrating COTS/GOTS into the NASA's mission critical HST CCS will be examined in detail. This paper will reveal the many hidden costs of COTS/GOTS solutions when compared to traditional custom code development efforts; this paper will show the high cost of COTS/GOTS solutions including training expenses, consulting fees, and long-term maintenance expenses.
Future engineers: the intrinsic technology motivation of secondary school pupils
NASA Astrophysics Data System (ADS)
Jones, Lewis C. R.; McDermott, Hilary J.; Tyrer, John R.; Zanker, Nigel P.
2018-07-01
The supply of students motivated to study engineering in higher education is critical to the sector. Results are presented from the 'Mindsets STEM Enhancement Project'. Fifty-seven new resources packs, designed to improve STEM education in Design and Technology, were given to schools across London. A modified Intrinsic Motivation Inventory questionnaire measured pupils' (n = 458) motivation towards technology. The results show that although pupils have positive reactions to the technology content within Design and Technology lessons, the type of STEM resources and lessons created through the project had made no significant difference on pupils' interest/enjoyment towards technology. This suggests stand-alone resources do not improve pupil motivation. The impact of this work to engineering higher education is that the existing levels and the inability to improve pupil motivation in technology at school could be a factor affecting the pursuit of a technology or engineering related education or career.
Advanced helmet vision system (AHVS) integrated night vision helmet mounted display (HMD)
NASA Astrophysics Data System (ADS)
Ashcraft, Todd W.; Atac, Robert
2012-06-01
Gentex Corporation, under contract to Naval Air Systems Command (AIR 4.0T), designed the Advanced Helmet Vision System to provide aircrew with 24-hour, visor-projected binocular night vision and HMD capability. AHVS integrates numerous key technologies, including high brightness Light Emitting Diode (LED)-based digital light engines, advanced lightweight optical materials and manufacturing processes, and innovations in graphics processing software. This paper reviews the current status of miniaturization and integration with the latest two-part Gentex modular helmet, highlights the lessons learned from previous AHVS phases, and discusses plans for qualification and flight testing.
Systems engineering in a joint program environment: the joint helmet-mounted cueing system
NASA Astrophysics Data System (ADS)
Wilkins, Donald F.
1999-07-01
The Joint Helmet Mounted Cueing System (JHMCS) is a design program involving two airframe companies (Boeing and Lockheed Martin), two services (USAF and USN) and four aircraft platforms: the F-22, the F-16, the F/A-18 and the F-15. Developing equipment requirements for the combined operational and environmental needs of these diverse communities is a significant challenge. In addition, the team is geographically dispersed which presented challenges in communication and coordination. This paper details the lessons learned in producing a cost-effective design within a short development schedule and makes recommendations for future development programs.
Advances in tissue engineering through stem cell-based co-culture.
Paschos, Nikolaos K; Brown, Wendy E; Eswaramoorthy, Rajalakshmanan; Hu, Jerry C; Athanasiou, Kyriacos A
2015-05-01
Stem cells are the future in tissue engineering and regeneration. In a co-culture, stem cells not only provide a target cell source with multipotent differentiation capacity, but can also act as assisting cells that promote tissue homeostasis, metabolism, growth and repair. Their incorporation into co-culture systems seems to be important in the creation of complex tissues or organs. In this review, critical aspects of stem cell use in co-culture systems are discussed. Direct and indirect co-culture methodologies used in tissue engineering are described, along with various characteristics of cellular interactions in these systems. Direct cell-cell contact, cell-extracellular matrix interaction and signalling via soluble factors are presented. The advantages of stem cell co-culture strategies and their applications in tissue engineering and regenerative medicine are portrayed through specific examples for several tissues, including orthopaedic soft tissues, bone, heart, vasculature, lung, kidney, liver and nerve. A concise review of the progress and the lessons learned are provided, with a focus on recent developments and their implications. It is hoped that knowledge developed from one tissue can be translated to other tissues. Finally, we address challenges in tissue engineering and regenerative medicine that can potentially be overcome via employing strategies for stem cell co-culture use. Copyright © 2014 John Wiley & Sons, Ltd.
Controlling changes - lessons learned from waste management facilities
DOE Office of Scientific and Technical Information (OSTI.GOV)
Johnson, B.M.; Koplow, A.S.; Stoll, F.E.
This paper discusses lessons learned about change control at the Waste Reduction Operations Complex (WROC) and Waste Experimental Reduction Facility (WERF) of the Idaho National Engineering Laboratory (INEL). WROC and WERF have developed and implemented change control and an as-built drawing process and have identified structures, systems, and components (SSCS) for configuration management. The operations have also formed an Independent Review Committee to minimize costs and resources associated with changing documents. WROC and WERF perform waste management activities at the INEL. WROC activities include storage, treatment, and disposal of hazardous and mixed waste. WERF provides volume reduction of solid low-levelmore » waste through compaction, incineration, and sizing operations. WROC and WERF`s efforts aim to improve change control processes that have worked inefficiently in the past.« less
Integrated Risk and Knowledge Management Program -- IRKM-P
NASA Technical Reports Server (NTRS)
Lengyel, David M.
2009-01-01
The NASA Exploration Systems Mission Directorate (ESMD) IRKM-P tightly couples risk management and knowledge management processes and tools to produce an effective "modern" work environment. IRKM-P objectives include: (1) to learn lessons from past and current programs (Apollo, Space Shuttle, and the International Space Station); (2) to generate and share new engineering design, operations, and management best practices through preexisting Continuous Risk Management (CRM) procedures and knowledge-management practices; and (3) to infuse those lessons and best practices into current activities. The conceptual framework of the IRKM-P is based on the assumption that risks highlight potential knowledge gaps that might be mitigated through one or more knowledge management practices or artifacts. These same risks also serve as cues for collection of knowledge particularly, knowledge of technical or programmatic challenges that might recur.
NASA Technical Reports Server (NTRS)
Price, Richard N.
2007-01-01
This paper intends to describe the lessons learned while specifying validating and installing a bit sync to replace the 30 year old Aydin Model 335a PCM bit sync used in the Space Shuttle Launch Control Center. The engineer had to analyze the original requirements and specifications and then create new requirements documentation that more correctly described our needs. One issue to consider was the removal of unnecessary requirements such as various data formats when only one format is used. The conversion to a system that no longer has an assortment of analog rotary switches required retraining of the operators. Finally, post-procurement corrections for undisclosed user requirements and missed design requirements required close contact with a manufacturer who was willing to accommodate the changes.
2007-11-15
Intelligence and Information Systems (IIS) Enterprise CMMI® ML3 SCAMPI(SM) SE/SW/IPPD/SS #5382 Raymond L. Kile , SEI Authorized Lead Appraiser Kathryn...Kirby, Raytheon IIS Process Assessments IPT Lead Picking a Representative Sample For CMMI® Enterprise Appraisals Page 2 Introductions Ray Kile has thirty...University of Missouri. Raymond L. Kile Chief Engineer Center for Systems Management 1951 Kidwell Drive, Suite 750 Vienna, VA 22182 303-601-8978 rkile@csm.com
ERIC Educational Resources Information Center
Song, Youngjin; Higgins, Teresa; Harding-DeKam, Jenni
2014-01-01
This article describes a series of inquiry-based lessons that provide English language learners (ELLs) with opportunities to experience science and engineering practices with conceptual understanding as well as to develop their language proficiency in elementary classrooms. The four-lesson sequence models how various types of instructional…
An Absorbing Look at Terry-Cloth Towels
ERIC Educational Resources Information Center
Moyer, Richard; Everett, Susan
2010-01-01
This article describes a lesson where students explore the absorbency of several towels with different weaves and weights. The lesson follows the 5E learning-cycle model and incorporates engineering in the sense of product testing with a focus on the relationship between the weave of a towel and its absorbency. The National Science Education…
Repairing Femoral Fractures: A Model Lesson in Biomaterial Science
ERIC Educational Resources Information Center
Sakakeeny, Jarred
2006-01-01
Biomaterial science is a rapidly growing field that has scientists and doctors searching for new ways to repair the body. A merger between medicine and engineering, biomaterials can be complex subject matter, and it can certainly capture the minds of middle school students. In the lesson described in this article, seventh graders generally learn…
Propulsion Ground Testing with High Test Peroxide: Lessons Learned
NASA Technical Reports Server (NTRS)
Bruce, Robert; Taylor, Gary; Taliancich, Paula
2002-01-01
Propulsion Ground Testing with High Test Peroxide (85 to 98% concentration) began at the NASA John C. Stennis Space Center in calendar year 1998, when the E3 Test Facility was modified to accomodate hydrogen peroxide (H2O2) in order to suport the research and development testing of the USAF Upper Stage Flight Experiment rocket engine. Since that time, efforts have continued to provide actual and planned test services to various customers, both U.S. Government and Commercial, in the ground test of many test articles, ranging from gas generators, to catalyst beds, to turbomachinery, to main injectors, to combustion chambers, to integrated rocket engines, to integrated stages. Along this path, and over the past 4 years, there has been both the rediscovery of previously learned lessons, through literature search, archive review, and personal interviews, as well as the learning of many new lessons as new areas are explored and new endeavors are tried. This paper will summarize those lessons learned in an effort to broaden the knowledge base as High Test Peroxide is considered more widely for use in rocket propulsion applications.
JPRS Report, Science & Technology USSR: Science & Technology Policy.
1988-04-06
YESTESTVOZNANIYA I TEKHNIKI, No 3, Mar 87] 15 Work of Nadezhnost mashin Interbranch Complex [K. Frolov et al; NTR: PROBLEMYIRESHEN1YA, No 21, 3-16 Nov 86...Equipment By Rotor Complex [L. Koshkin; PLANOVOYE KHOZYAYSTVO, No 3, Mar 87] 29 Training, Use of Engineers Severely Criticized [V.G. Aynshteyn; ZNANIYE... complex systems, were painful lessons. In other words, the social role and, let us stress, the social responsibility of science today have increased
Human Factors Engineering. A Self-Paced Text, Lessons 36-40,
1981-08-01
proposed contract does not involve ’significant human interface for operation/ maintenance /control,’ the selection guide should not be used. Turn to Page 98... work space configuration, packaging, and labeling. These are all aspects of maintenance which need to be incorporated into the original design plans... work done. An ROC is a ’Required Operational Capability’ statement that is required by the Army during the system acquisition process . Return to Page
Engineering Encounters: From STEM to STEAM
ERIC Educational Resources Information Center
Cook, Kristin; Bush, Sarah; Cox, Richard
2017-01-01
Teaching STEAM (science, technology, engineering, art, and math) in elementary school could be even more promising than teaching STEM. This is due to its ability to cross multiple subject areas and its appeal to multiple types of learners. Intentional integration of the arts in science and engineering lessons has the potential to more deeply…
An Assessment Methodology to Evaluate In-Flight Engine Health Management Effectiveness
NASA Astrophysics Data System (ADS)
Maggio, Gaspare; Belyeu, Rebecca; Pelaccio, Dennis G.
2002-01-01
flight effectiveness of candidate engine health management system concepts. A next generation engine health management system will be required to be both reliable and robust in terms of anomaly detection capability. The system must be able to operate successfully in the hostile, high-stress engine system environment. This implies that its system components, such as the instrumentation, process and control, and vehicle interface and support subsystems, must be highly reliable. Additionally, the system must be able to address a vast range of possible engine operation anomalies through a host of different types of measurements supported by a fast algorithm/architecture processing capability that can identify "true" (real) engine operation anomalies. False anomaly condition reports for such a system must be essentially eliminated. The accuracy of identifying only real anomaly conditions has been an issue with the Space Shuttle Main Engine (SSME) in the past. Much improvement in many of the technologies to address these areas is required. The objectives of this study were to identify and demonstrate a consistent assessment methodology that can evaluate the capability of next generation engine health management system concepts to respond in a correct, timely manner to alleviate an operational engine anomaly condition during flight. Science Applications International Corporation (SAIC), with support from NASA Marshall Space Flight Center, identified a probabilistic modeling approach to assess engine health management system concept effectiveness using a deterministic anomaly-time event assessment modeling approach that can be applied in the engine preliminary design stage of development to assess engine health management system concept effectiveness. Much discussion in this paper focuses on the formulation and application approach in performing this assessment. This includes detailed discussion of key modeling assumptions, the overall assessment methodology approach identified, and the identification of key supporting engine health management system concept design/operation and fault mode information required to utilize this methodology. At the paper's conclusion, discussion focuses on a demonstration benchmark study that applied this methodology to the current SSME health management system. A summary of study results and lessons learned are provided. Recommendations for future work in this area are also identified at the conclusion of the paper. * Please direct all correspondence/communication pertaining to this paper to Dennis G. Pelaccio, Science
Space Telecommunications Radio System (STRS) Application Repository Design and Analysis
NASA Technical Reports Server (NTRS)
Handler, Louis M.
2013-01-01
The Space Telecommunications Radio System (STRS) Application Repository Design and Analysis document describes the STRS application repository for software-defined radio (SDR) applications intended to be compliant to the STRS Architecture Standard. The document provides information about the submission of artifacts to the STRS application repository, to provide information to the potential users of that information, and for the systems engineer to understand the requirements, concepts, and approach to the STRS application repository. The STRS application repository is intended to capture knowledge, documents, and other artifacts for each waveform application or other application outside of its project so that when the project ends, the knowledge is retained. The document describes the transmission of technology from mission to mission capturing lessons learned that are used for continuous improvement across projects and supporting NASA Procedural Requirements (NPRs) for performing software engineering projects and NASAs release process.
Next Generation Launch Technology Program Lessons Learned
NASA Technical Reports Server (NTRS)
Cook, Stephen; Tyson, Richard
2005-01-01
In November 2002, NASA revised its Integrated Space Transportation Plan (ISTP) to evolve the Space Launch Initiative (SLI) to serve as a theme for two emerging programs. The first of these, the Orbital Space Plane (OSP), was intended to provide crew-escape and crew-transfer functions for the ISS. The second, the NGLT Program, developed technologies needed for safe, routine space access for scientific exploration, commerce, and national defense. The NGLT Program was comprised of 12 projects, ranging from fundamental high-temperature materials research to full-scale engine system developments (turbine and rocket) to scramjet flight test. The Program included technology advancement activities with a broad range of objectives, ultimate applications/timeframes, and technology maturity levels. An over-arching Systems Engineering and Analysis (SE&A) approach was employed to focus technology advancements according to a common set of requirements. Investments were categorized into three segments of technology maturation: propulsion technologies, launch systems technologies, and SE&A.
The Integration of COTS/GOTS within NASA's HST Command and Control System
NASA Technical Reports Server (NTRS)
Pfarr, Thomas; Reis, James E.; Obenschain, Arthur F. (Technical Monitor)
2001-01-01
NASA's mission critical Hubble Space Telescope (HST) command and control system has been re-engineered with COTS/GOTS and minimal custom code. This paper focuses on the design of this new HST Control Center System (CCS) and the lessons learned throughout its development. CCS currently utilizes 31 COTS/GOTS products with an additional 12 million lines of custom glueware code; the new CCS exceeds the capabilities of the original system while significantly reducing the lines of custom code by more than 50%. The lifecycle of COTS/GOTS products will be examined including the pack-age selection process, evaluation process, and integration process. The advantages, disadvantages, issues, concerns, and lessons teamed for integrating COTS/GOTS into the NASA's mission critical HST CCS will be examined in detail. Command and control systems designed with traditional custom code development efforts will be compared with command and control systems designed with new development techniques relying heavily on COTS/COTS integration. This paper will reveal the many hidden costs of COTS/GOTS solutions when compared to traditional custom code development efforts; this paper will show the high cost of COTS/GOTS solutions including training expenses, consulting fees, and long-term maintenance expenses.
Space flight requirements for fiber optic components: qualification testing and lessons learned
NASA Astrophysics Data System (ADS)
Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam
2006-04-01
"Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.
Space Flight Requirements for Fiber Optic Components; Qualification Testing and Lessons Learned
NASA Technical Reports Server (NTRS)
Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam
2007-01-01
"Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.
An overview of NASA ISS human engineering and habitability: past, present, and future.
Fitts, D; Architecture, B
2000-09-01
The International Space Station (ISS) is the first major NASA project to provide human engineering an equal system engineering an equal system engineering status to other disciplines. The incorporation and verification of hundreds of human engineering requirements applied across-the-board to the ISS has provided for a notably more habitable environment to support long duration spaceflight missions than might otherwise have been the case. As the ISS begins to be inhabited and become operational, much work remains in monitoring the effectiveness of the Station's built environment in supporting the range of activities required of a long-duration vehicle. With international partner participation, NASA's ISS Operational Habitability Assessment intends to carry human engineering and habitability considerations into the next phase of the ISS Program with constant attention to opportunities for cost-effective improvements that need to be and can be made to the on-orbit facility. Too, during its operations the ISS must be effectively used as an on-orbit laboratory to promote and expand human engineering/habitability awareness and knowledge to support the international space faring community with the data needed to develop future space vehicles for long-duration missions. As future space mission duration increases, the rise in importance of habitation issues make it imperative that lessons are captured from the experience of human engineering's incorporation into the ISS Program and applied to future NASA programmatic processes.
Multi-unit Operations in Non-Nuclear Systems: Lessons Learned for Small Modular Reactors
DOE Office of Scientific and Technical Information (OSTI.GOV)
OHara J. M.; Higgins, J.; DAgostino, A.
2012-01-17
The nuclear-power community has reached the stage of proposing advanced reactor designs to support power generation for decades to come. Small modular reactors (SMRs) are one approach to meet these energy needs. While the power output of individual reactor modules is relatively small, they can be grouped to produce reactor sites with different outputs. Also, they can be designed to generate hydrogen, or to process heat. Many characteristics of SMRs are quite different from those of current plants and may be operated quite differently. One difference is that multiple units may be operated by a single crew (or a singlemore » operator) from one control room. The U.S. Nuclear Regulatory Commission (NRC) is examining the human factors engineering (HFE) aspects of SMRs to support licensing reviews. While we reviewed information on SMR designs to obtain information, the designs are not completed and all of the design and operational information is not yet available. Nor is there information on multi-unit operations as envisioned for SMRs available in operating experience. Thus, to gain a better understanding of multi-unit operations we sought the lesson learned from non-nuclear systems that have experience in multi-unit operations, specifically refineries, unmanned aerial vehicles and tele-intensive care units. In this paper we report the lessons learned from these systems and the implications for SMRs.« less
NASA Astrophysics Data System (ADS)
Tremoulet, P. C.
The author describes a number of maintenance improvements in the Fiber Optic Cable System (FOCS). They were achieved during a production phase pilot concurrent engineering program. Listed in order of importance (saved maintenance time and material) by maintenance level, they are: (1) organizational level: improved fiber optic converter (FOC) BITE; (2) Intermediate level: reduced FOC adjustments from 20 to 2; partitioned FOC into electrical and optical parts; developed cost-effective fault isolation test points and test using standard test equipment; improved FOC chassis to have lower mean time to repair; and (3) depot level: revised test requirements documents (TRDs) for common automatic test equipment and incorporated ATE testability into circuit and assemblies and application-specific integrated circuits. These improvements met this contract's tailored logistics MIL-STD 1388-1A requirements of monitoring the design for supportability and determining the most effective support equipment. Important logistics lessons learned while accomplishing these maintainability and supportability improvements on the pilot concurrent engineering program are also discussed.
Chiang, Michael F; Starren, Justin B
2002-01-01
The successful implementation of clinical information systems is difficult. In examining the reasons and potential solutions for this problem, the medical informatics community may benefit from the lessons of a rich body of software engineering and management literature about the failure of software projects. Based on previous studies, we present a conceptual framework for understanding the risk factors associated with large-scale projects. However, the vast majority of existing literature is based on large, enterprise-wide systems, and it unclear whether those results may be scaled down and applied to smaller projects such as departmental medical information systems. To examine this issue, we discuss the case study of a delayed electronic medical record implementation project in a small specialty practice at Columbia-Presbyterian Medical Center. While the factors contributing to the delay of this small project share some attributes with those found in larger organizations, there are important differences. The significance of these differences for groups implementing small medical information systems is discussed.
FD-CHIRP: hosted payload system engineering lessons
NASA Astrophysics Data System (ADS)
Schueler, Carl F.
2012-10-01
The Commercially Hosted Infrared Payload (CHIRP) Flight Demonstration (FD-CHIRP) launched 21 Sept 2011 was designated a "resounding success" as the first Wide Field-of-View (WFOV) staring infrared (IR) sensor flown in geostationary earth orbit (GEO) with a primary mission of Missile Warning (MW). FD-CHIRP was an Air Force research and development project initiated in July 2008 via an unsolicited industry proposal aimed to mature and reduce the risk of WFOV sensors and ground processing technologies. Unlike the Defense Support Program (DSP) and the Space Based Infrared System (SBIRS) which were acquired via traditional integrated sensor and satellite design, FDCHIRP was developed using the "commercially hosted" approach. The FD-CHIRP host spacecraft and sensor were independently designed, creating significant development risk to the industry proposer, especially under a Firm Fixed Price contract. Yet, within 39 months of contract initiation, FD-CHIRP was launched and successfully operated in GEO to 30 June 2012 at a total cost of 111M including the 82.9M CHIRP commercial-hosting contract and a $28M sensor upgrade. The commercial-hosting contract included sensor and spacecraft modifications, integration and test, design and development of secure Mission Operations and Analysis Centers, launch, and nearly a year of GEO operations with 70 Mbps secure data acquisition. The Air Force extended the contract for six months to continue operations through the end of calendar 2012. This paper outlines system engineering challenges FD-CHIRP overcame and key lessons to smooth development of future commercially hosted missions.
Bioelectricity-AQA, one of the first MOOC courses in engineering.
Barr, Roger C
2014-01-01
Bioelectricity-AQA was one of the first massively open online courses in engineering, having been given the first time via Coursera starting in September, 2012. This report provides some detail on its background, presentation, enrollment, and lessons learned.
ERIC Educational Resources Information Center
Maggi, Gayle J. B.
Thirty-six lessons for introducing the metric system are outlined. Appropriate grade level is not specified. The metric lessons suggested include 13 lessons on length, 7 lessons on mass, 11 lessons on capacity, and 5 lessons on temperature. Each lesson includes a list of needed materials, a statement of the lesson purpose, and suggested…
Space Vehicle Terrestrial Environment Design Requirements Guidelines
NASA Technical Reports Server (NTRS)
Johnson, Dale L.; Keller, Vernon W.; Vaughan, William W.
2006-01-01
The terrestrial environment is an important driver of space vehicle structural, control, and thermal system design. NASA is currently in the process of producing an update to an earlier Terrestrial Environment Guidelines for Aerospace Vehicle Design and Development Handbook. This paper addresses the contents of this updated handbook, with special emphasis on new material being included in the areas of atmospheric thermodynamic models, wind dynamics, atmospheric composition, atmospheric electricity, cloud phenomena, atmospheric extremes, and sea state. In addition, the respective engineering design elements are discussed relative to terrestrial environment inputs that require consideration. Specific lessons learned that have contributed to the advancements made in the application and awareness of terrestrial environment inputs for aerospace engineering applications are presented.
Best Practices for Quality Improvement--Lessons from Top Ranked Engineering Institutions
ERIC Educational Resources Information Center
Rao, Potti Srinivasa; Viswanadhan, K. G.; Raghunandana, K.
2015-01-01
Maximum number of privately funded engineering institutions have been established in India in the last two decades to meet the growing needs of technical manpower required by the Engineering and IT companies as well as aspiring students after completion of the Pre-University Program. However, a large number of institutions have not been able to…
ERIC Educational Resources Information Center
Mississippi Research and Curriculum Unit for Vocational and Technical Education, State College.
This document, which reflects Mississippi's statutory requirement that instructional programs be based on core curricula and performance-based assessment, contains outlines of the instructional units required in local instructional management plans and daily lesson plans for small engine repair I and II. Presented first are a program description…
Taking It to the Top: A Lesson in Search Engine Optimization
ERIC Educational Resources Information Center
Frydenberg, Mark; Miko, John S.
2011-01-01
Search engine optimization (SEO), the promoting of a Web site so it achieves optimal position with a search engine's rankings, is an important strategy for organizations and individuals in order to promote their brands online. Techniques for achieving SEO are relevant to students of marketing, computing, media arts, and other disciplines, and many…
Teachers' Thoughts on Student Decision Making during Engineering Design Lessons
ERIC Educational Resources Information Center
Meyer, Helen
2018-01-01
In this paper, I share the results of a study of teachers' ideas about student decision-making at entry into a professional development program to integrate engineering into their instruction. The framework for the Engineering Design Process (EDP) was based on a Challenge-Based Learning (CBL) model. The EDP embedded within the CBL model suggests…
Crystalline-silicon reliability lessons for thin-film modules
NASA Technical Reports Server (NTRS)
Ross, Ronald G., Jr.
1985-01-01
Key reliability and engineering lessons learned from the 10-year history of the Jet Propulsion Laboratory's Flat-Plate Solar Array Project are presented and analyzed. Particular emphasis is placed on lessons applicable to the evolving new thin-film cell and module technologies and the organizations involved with these technologies. The user-specific demand for reliability is a strong function of the application, its location, and its expected duration. Lessons relative to effective means of specifying reliability are described, and commonly used test requirements are assessed from the standpoint of which are the most troublesome to pass, and which correlate best with field experience. Module design lessons are also summarized, including the significance of the most frequently encountered failure mechanisms and the role of encapsulant and cell reliability in determining module reliability. Lessons pertaining to research, design, and test approaches include the historical role and usefulness of qualification tests and field tests.
PV Reliability Development Lessons from JPL's Flat Plate Solar Array Project
NASA Technical Reports Server (NTRS)
Ross, Ronald G., Jr.
2013-01-01
Key reliability and engineering lessons learned from the 20-year history of the Jet Propulsion Laboratory's Flat-Plate Solar Array Project and thin film module reliability research activities are presented and analyzed. Particular emphasis is placed on lessons applicable to evolving new module technologies and the organizations involved with these technologies. The user-specific demand for reliability is a strong function of the application, its location, and its expected duration. Lessons relative to effective means of specifying reliability are described, and commonly used test requirements are assessed from the standpoint of which are the most troublesome to pass, and which correlate best with field experience. Module design lessons are also summarized, including the significance of the most frequently encountered failure mechanisms and the role of encapsulate and cell reliability in determining module reliability. Lessons pertaining to research, design, and test approaches include the historical role and usefulness of qualification tests and field tests.
Integrating Engineering Data Systems for NASA Spaceflight Projects
NASA Technical Reports Server (NTRS)
Carvalho, Robert E.; Tollinger, Irene; Bell, David G.; Berrios, Daniel C.
2012-01-01
NASA has a large range of custom-built and commercial data systems to support spaceflight programs. Some of the systems are re-used by many programs and projects over time. Management and systems engineering processes require integration of data across many of these systems, a difficult problem given the widely diverse nature of system interfaces and data models. This paper describes an ongoing project to use a central data model with a web services architecture to support the integration and access of linked data across engineering functions for multiple NASA programs. The work involves the implementation of a web service-based middleware system called Data Aggregator to bring together data from a variety of systems to support space exploration. Data Aggregator includes a central data model registry for storing and managing links between the data in disparate systems. Initially developed for NASA's Constellation Program needs, Data Aggregator is currently being repurposed to support the International Space Station Program and new NASA projects with processes that involve significant aggregating and linking of data. This change in user needs led to development of a more streamlined data model registry for Data Aggregator in order to simplify adding new project application data as well as standardization of the Data Aggregator query syntax to facilitate cross-application querying by client applications. This paper documents the approach from a set of stand-alone engineering systems from which data are manually retrieved and integrated, to a web of engineering data systems from which the latest data are automatically retrieved and more quickly and accurately integrated. This paper includes the lessons learned through these efforts, including the design and development of a service-oriented architecture and the evolution of the data model registry approaches as the effort continues to evolve and adapt to support multiple NASA programs and priorities.
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.
A Survey of Current Rotorcraft Propulsion Health Monitoring Technologies
NASA Technical Reports Server (NTRS)
Delgado, Irebert R.; Dempsey, Paula J.; Simon, Donald L.
2012-01-01
A brief review is presented on the state-of-the-art in rotorcraft engine health monitoring technologies including summaries on current practices in the area of sensors, data acquisition, monitoring and analysis. Also, presented are guidelines for verification and validation of Health Usage Monitoring System (HUMS) and specifically for maintenance credits to extend part life. Finally, a number of new efforts in HUMS are summarized as well as lessons learned and future challenges. In particular, gaps are identified to supporting maintenance credits to extend rotorcraft engine part life. A number of data sources were consulted and include results from a survey from the HUMS community, Society of Automotive Engineers (SAE) documents, American Helicopter Society (AHS) papers, as well as references from Defence Science & Technology Organization (DSTO), Civil Aviation Authority (CAA), and Federal Aviation Administration (FAA).
Shuttle Case Study Collection Website Development
NASA Technical Reports Server (NTRS)
Ransom, Khadijah S.; Johnson, Grace K.
2012-01-01
As a continuation from summer 2012, the Shuttle Case Study Collection has been developed using lessons learned documented by NASA engineers, analysts, and contractors. Decades of information related to processing and launching the Space Shuttle is gathered into a single database to provide educators with an alternative means to teach real-world engineering processes. The goal is to provide additional engineering materials that enhance critical thinking, decision making, and problem solving skills. During this second phase of the project, the Shuttle Case Study Collection website was developed. Extensive HTML coding to link downloadable documents, videos, and images was required, as was training to learn NASA's Content Management System (CMS) for website design. As the final stage of the collection development, the website is designed to allow for distribution of information to the public as well as for case study report submissions from other educators online.
The challenge of logistics facilities development
NASA Technical Reports Server (NTRS)
Davis, James R.
1987-01-01
The paper discusses the experiences of a group of engineers and logisticians at John F. Kennedy Space center in the design, construction and activation of a consolidated logistics facility for support of Space Transportation System ground operations and maintenance. The planning, methodology and processes are covered, with emphasis placed on unique aspects and lessons learned. The project utilized a progressive design, baseline and build concept for each phase of construction, with the Government exercising funding and configuration oversight.
Requirements management for Gemini Observatory: a small organization with big development projects
NASA Astrophysics Data System (ADS)
Close, Madeline; Serio, Andrew; Cordova, Martin; Hardie, Kayla
2016-08-01
Gemini Observatory is an astronomical observatory operating two premier 8m-class telescopes, one in each hemisphere. As an operational facility, a majority of Gemini's resources are spent on operations however the observatory undertakes major development projects as well. Current projects include new facility science instruments, an operational paradigm shift to full remote operations, and new operations tools for planning, configuration and change control. Three years ago, Gemini determined that a specialized requirements management tool was needed. Over the next year, the Gemini Systems Engineering Group investigated several tools, selected one for a trial period and configured it for use. Configuration activities including definition of systems engineering processes, development of a requirements framework, and assignment of project roles to tool roles. Test projects were implemented in the tool. At the conclusion of the trial, the group determined that the Gemini could meet its requirements management needs without use of a specialized requirements management tool, and the group identified a number of lessons learned which are described in the last major section of this paper. These lessons learned include how to conduct an organizational needs analysis prior to pursuing a tool; caveats concerning tool criteria and the selection process; the prerequisites and sequence of activities necessary to achieve an optimum configuration of the tool; the need for adequate staff resources and staff training; and a special note regarding organizations in transition and archiving of requirements.
Simulation Data Management - Requirements and Design Specification
DOE Office of Scientific and Technical Information (OSTI.GOV)
Clay, Robert L.; Friedman-Hill, Ernest J.; Gibson, Marcus J.
Simulation Data Management (SDM), the ability to securely organize, archive, and share analysis models and the artifacts used to create them, is a fundamental requirement for modern engineering analysis based on computational simulation. We have worked separately to provide secure, network SDM services to engineers and scientists at our respective laboratories for over a decade. We propose to leverage our experience and lessons learned to help develop and deploy a next-generation SDM service as part of a multi-laboratory team. This service will be portable across multiple sites and platforms, and will be accessible via a range of command-line tools andmore » well-documented APIs. In this document, we’ll review our high-level and low-level requirements for such a system, review one existing system, and briefly discuss our proposed implementation.« less
NASA Ames Sustainability Initiatives: Aeronautics, Space Exploration, and Sustainable Futures
NASA Technical Reports Server (NTRS)
Grymes, Rosalind A.
2015-01-01
In support of the mission-specific challenges of aeronautics and space exploration, NASA Ames produces a wealth of research and technology advancements with significant relevance to larger issues of planetary sustainability. NASA research on NexGen airspace solutions and its development of autonomous and intelligent technologies will revolutionize both the nation's air transporation systems and have applicability to the low altitude flight economy and to both air and ground transporation, more generally. NASA's understanding of the Earth as a complex of integrated systems contributes to humanity's perception of the sustainability of our home planet. Research at NASA Ames on closed environment life support systems produces directly applicable lessons on energy, water, and resource management in ground-based infrastructure. Moreover, every NASA campus is a 'city'; including an urbanscape and a workplace including scientists, human relations specialists, plumbers, engineers, facility managers, construction trades, transportation managers, software developers, leaders, financial planners, technologists, electricians, students, accountants, and even lawyers. NASA is applying the lessons of our mission-related activities to our urbanscapes and infrastructure, and also anticipates a leadership role in developing future environments for living and working in space.
Advanced engineering environment collaboration project.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Lamph, Jane Ann; Pomplun, Alan R.; Kiba, Grant W.
2008-12-01
The Advanced Engineering Environment (AEE) is a model for an engineering design and communications system that will enhance project collaboration throughout the nuclear weapons complex (NWC). Sandia National Laboratories and Parametric Technology Corporation (PTC) worked together on a prototype project to evaluate the suitability of a portion of PTC's Windchill 9.0 suite of data management, design and collaboration tools as the basis for an AEE. The AEE project team implemented Windchill 9.0 development servers in both classified and unclassified domains and used them to test and evaluate the Windchill tool suite relative to the needs of the NWC using weaponsmore » project use cases. A primary deliverable was the development of a new real time collaborative desktop design and engineering process using PDMLink (data management tool), Pro/Engineer (mechanical computer aided design tool) and ProductView Lite (visualization tool). Additional project activities included evaluations of PTC's electrical computer aided design, visualization, and engineering calculations applications. This report documents the AEE project work to share information and lessons learned with other NWC sites. It also provides PTC with recommendations for improving their products for NWC applications.« less
Bioelectricity-AQA, one of the first MOOC courses in Engineering
Barr, Roger C.
2014-01-01
Bioelectricity-AQA was one of the first massively open online courses in engineering, having been given the first time via Coursera starting in September, 2012. This report provides some detail on its background, presentation, enrollment, and lessons learned. PMID:25570327
NASA Astrophysics Data System (ADS)
Braaten, D. A.; Holvoet, J. F.; Gogineni, S.
2003-12-01
The Radar Systems and Remote Sensing Laboratory at the University of Kansas (KU) has implemented extensive outreach activities focusing on Polar Regions as part of the Polar Radar for Ice Sheet Measurements (PRISM) project. The PRISM project is developing advanced intelligent remote sensing technology that involves radar systems, an autonomous rover, and communications systems to measure detailed ice sheet characteristics, and to determine bed conditions (frozen or wet) below active ice sheets in both Greenland and Antarctica. These measurements will provide a better understanding of the response of polar ice sheets to global climate change and the resulting impact the ice sheets will have on sea level rise. Many of the research and technological development aspects of the PRISM project, such as robotics, radar systems, climate change and exploration of harsh environments, can kindle an excitement and interest in students about science and technology. These topics form the core of our K-12 education and training outreach initiatives, which are designed to capture the imagination of young students, and prompt them to consider an educational path that will lead them to scientific or engineering careers. The K-12 PRISM outreach initiatives are being developed and implemented in a collaboration with the Advanced Learning Technology Program (ALTec) of the High Plains Regional Technology in Education Consortium (HPR*TEC). ALTec is associated with the KU School of Education, and is a well-established educational research center that develops and hosts web tools to enable teachers nationwide to network, collaborate, and share resources with other teachers. An example of an innovative and successful web interface developed by ALTec is called TrackStar. Teachers can use TrackStar over the Web to develop interactive, resource-based lessons (called tracks) on-line for their students. Once developed, tracks are added to the TrackStar database and can be accessed and modified (if necessary) by teachers everywhere. The PRISM project has added a search engine for polar related tracks, and has developed numerous new tracks on robotics, polar exploration, and climate change under the guidance of a K-12 teacher advisory group. The PRISM project is also developing and hosting several other web-based lesson design tools and resources for K-12 educators and students on the PRISM project web page (http://www.ku-prism.org). These tools and resources include: i) "Polar Scientists and Explorers, Past and Present" covering the travels and/or unknown fate of polar explorers and scientists; ii) "Polar News" providing links to current news articles related to polar regions; iii) "Letter of Global Concern", which is a tool to help students draft a letter to a politician, government official, or business leader; iv) "Graphic Sleuth", which is an online utility that allows teachers to make lessons for student use; v) "Bears on Ice" for students in grades K - 6 that can follow the adventures of two stuffed bears that travel with scientists into polar regions; and vi) "K-12 Polar Resources," which provides teachers with images, information, TrackStar lessons, and a search engine designed to identify polar related lessons. In our presentation, we will describe and show examples of these tools and resources, and provide an assessment of their popularity with teachers nationwide.
NASA Technical Reports Server (NTRS)
Davis, Randal; Thalman, Nancy
1993-01-01
The University of Colorado's Laboratory for Atmospheric and Space Physics (CU/LASP) along with the Goddard Space Flight Center (GSFC) and the Jet Propulsion Laboratory (JPL) designed, implemented, tested, and demonstrated a prototype of the distributed, hierarchical planning and scheduling system comtemplated for the Earth Observing System (EOS) project. The planning and scheduling prototype made use of existing systems: CU/LASP's Operations and Science Instrument Support Planning and Scheduling (OASIS-PS) software package; GSFC's Request Oriented Scheduling Engine (ROSE); and JPL's Plan Integrated Timeliner 2 (Plan-It-2). Using these tools, four scheduling nodes were implemented and tied together using a new communications protocol for scheduling applications called the Scheduling Applications Interface Language (SAIL). An extensive and realistic scenario of EOS satellite operations was then developed and the prototype scheduling system was tested and demonstrated using the scenario. Two demonstrations of the system were given to NASA personnel and EOS core system (ECS) contractor personnel. A comprehensive volume of lessons learned was generated and a meeting was held with NASA and ECS representatives to review these lessons learned. A paper and presentation on the project's final results was given at the American Institute of Aeronautics and Astronautics Computing in Aerospace 9 conference.
Lessons learned for composite structures
NASA Technical Reports Server (NTRS)
Whitehead, R. S.
1991-01-01
Lessons learned for composite structures are presented in three technology areas: materials, manufacturing, and design. In addition, future challenges for composite structures are presented. Composite materials have long gestation periods from the developmental stage to fully matured production status. Many examples exist of unsuccessful attempts to accelerate this gestation period. Experience has shown that technology transition of a new material system to fully matured production status is time consuming, involves risk, is expensive and should not be undertaken lightly. The future challenges for composite materials require an intensification of the science based approach to material development, extension of the vendor/customer interaction process to include all engineering disciplines of the end user, reduced material costs because they are a significant factor in overall part cost, and improved batch-to-batch pre-preg physical property control. Historical manufacturing lessons learned are presented using current in-service production structure as examples. Most producibility problems for these structures can be traced to their sequential engineering design. This caused an excessive emphasis on design-to-weight and schedule at the expense of design-to-cost. This resulted in expensive performance originated designs, which required costly tooling and led to non-producible parts. Historically these problems have been allowed to persist throughout the production run. The current/future approach for the production of affordable composite structures mandates concurrent engineering design where equal emphasis is placed on product and process design. Design for simplified assembly is also emphasized, since assembly costs account for a major portion of total airframe costs. The future challenge for composite manufacturing is, therefore, to utilize concurrent engineering in conjunction with automated manufacturing techniques to build affordable composite structures. Composite design experience has shown that significant weight savings have been achieved, outstanding fatigue and corrosion resistance have been demonstrated, and in-service performance has been very successful. Currently no structural design show stoppers exist for composite structures. A major lesson learned is that the full scale static test is the key test for composites, since it is the primary structural 'hot spot' indicator. The major durability issue is supportability of thin skinned structure. Impact damage has been identified as the most significant issue for the damage tolerance control of composite structures. However, delaminations induced during assembly operations have demonstrated a significant nuisance value. The future challenges for composite structures are threefold. Firstly, composite airframe weight fraction should increase to 60 percent. At the same time, the cost of composite structures must be reduced by 50 percent to attain the goal of affordability. To support these challenges it is essential to develop lower cost materials and processes.
Understanding Student Experiences: A Case Study in Scientific Visualization and Civics and Economics
ERIC Educational Resources Information Center
Jessee, Emily George
2012-01-01
This research study provides the finding of a qualitative case study in Technology, Engineering, and Design Education as well as Social Studies Education. The purpose of this study was to describe the role of graphics within a social studies lesson by examining a student's experience when a new lesson is implemented in class. The participants were…
Replacing The Engine In Your Car While You Are Still Driving It [PowerPoint
DOE Office of Scientific and Technical Information (OSTI.GOV)
Bjorklund, Eric A.
The scope of the project included the following: install new network backbone, replace 201 MHz rf tubes, replace low-level rf system, replace timing system, replace industrial I/O system, replace beam synchronous data acquisition system, replace fast protect reporting system, new wire scanner hardware, and new beam position/phase monitor hardware--all of this to be done while continuing to deliver beam to users. Lessons learned, for anyone contemplating a similarly ambitious upgrade: You can’t replace the whole system at once. Some compatibility must be maintained between the old and new systems. Always have a way to fall back. Have sympathy for themore » operations staff. You will be surprised.« less
NASA Astrophysics Data System (ADS)
Talbot, C. A.; Ralph, M.; Jasperse, J.; Forbis, J.
2017-12-01
Lessons learned from the multi-agency Forecast-Informed Reservoir Operations (FIRO) effort demonstrate how research and observations can inform operations and policy decisions at Federal, State and Local water management agencies with the collaborative engagement and support of researchers, engineers, operators and stakeholders. The FIRO steering committee consists of scientists, engineers and operators from research and operational elements of the National Oceanographic and Atmospheric Administration and the US Army Corps of Engineers, researchers from the US Geological Survey and the US Bureau of Reclamation, the state climatologist from the California Department of Water Resources, the chief engineer from the Sonoma County Water Agency, and the director of the Scripps Institution of Oceanography's Center for Western Weather and Water Extremes at the University of California-San Diego. The FIRO framework also provides a means of testing and demonstrating the benefits of next-generation water cycle observations, understanding and models in water resources operations.
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
Lessons Learned from the Space Shuttle Engine Hydrogen Flow Control Valve Poppet Breakage
NASA Technical Reports Server (NTRS)
Martinez, Hugo E.; Damico, Stephen; Brewer, John
2011-01-01
The Main Propulsion System (MPS) uses three Flow Control Valves (FCV) to modulate the flow of pressurant hydrogen gas from the Space Shuttle Main Engines (SSME) to the hydrogen External Tank (ET). This maintains pressure in the ullage volume as the liquid level drops, preserving ET structural integrity and assuring the engines receive a sufficient amount of head pressure. On Space Transportation System (STS)-126 (2009), with only a handful of International Space Station (ISS) assembly flights from the end of the Shuttle program, a portion of a single FCV?s poppet head broke off at about a minute and a half after liftoff. The risk of the poppet head failure is that the increased flow area through the FCV could result in excessive gaseous hydrogen flow back to the external tank, which could result in overboard venting of hydrogen ullage pressure. If the hydrogen venting were to occur in first stage (i.e., lower atmosphere), a flammability hazard exists that could lead to catastrophic loss of crew and vehicle. Other failure risks included particle impact damage to MPS downstream hardware. Although the FCV design had been plagued by contamination-related sluggish valve response problems prior to a redesign at STS-80 (1996), contamination was ruled out as the cause of the STS-126 failure. Employing a combination of enhanced hardware inspection and a better understanding of the consequences of a poppet failure, safe flight rationale for subsequent flights (STS-119 and later) was achieved. This paper deals with the technical lessons learned during the investigation and mitigation of this problem at a time when assembly flights were each in the critical path to Space Station success.
Case Study of a Discontinued Start-Up Engineering Program: Critical Challenges and Lessons Learned
ERIC Educational Resources Information Center
Friess, Wilhelm A.
2017-01-01
The explanatory case study presented here analyzes the factors that have contributed to the failure of a start-up engineering program launched at an off-campus site, and aimed at imparting the first two years of the BSc Mechanical, Electrical, Computer and Civil Engineering utilizing an integrated curriculum. Findings indicate the root cause for…
Historical problem areas: Lessons learned for expendable and reusable vehicle propulsion systems
NASA Technical Reports Server (NTRS)
Fester, Dale A.
1991-01-01
The following subject areas are covered: expendable launch vehicle lessons learned, upper stage/transfer vehicle lessons learned, shuttle systems - reuse, and reusable system issues and lessons learned.
Lift-fan aircraft: Lessons learned-the pilot's perspective
NASA Technical Reports Server (NTRS)
Gerdes, Ronald M.
1993-01-01
This paper is written from an engineering test pilot's point of view. Its purpose is to present lift-fan 'lessons learned' from the perspective of first-hand experience accumulated during the period 1962 through 1988 while flight testing vertical/short take-off and landing (V/STOL) experimental aircraft and evaluating piloted engineering simulations of promising V/STOL concepts. Specifically, the scope of the discussions to follow is primarily based upon a critical review of the writer's personal accounts of 30 hours of XV-5A/B and 2 hours of X-14A flight testing as well as a limited simulator evaluation of the Grumman Design 755 lift-fan aircraft. Opinions of other test pilots who flew these aircraft and the aircraft simulator are also included and supplement the writer's comments. Furthermore, the lessons learned are presented from the perspective of the writer's flying experience: 10,000 hours in 100 fixed- and rotary-wing aircraft including 330 hours in 5 experimental V/STOL research aircraft. The paper is organized to present to the reader a clear picture of lift-fan lessons learned from three distinct points of view in order to facilitate application of the lesson principles to future designs. Lessons learned are first discussed with respect to case histories of specific flight and simulator investigations. These principles are then organized and restated with respect to four selected design criteria categories in Appendix I. Lastly, Appendix Il is a discussion of the design of a hypothetical supersonic short take-off vertical landing (STOVL) fighter/attack aircraft.
Shah, Hemant; Allard, Raymond D; Enberg, Robert; Krishnan, Ganesh; Williams, Patricia; Nadkarni, Prakash M
2012-03-09
A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.
2012-01-01
Background A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. Methods In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). Results The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. Conclusions When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies. PMID:22405400
1991-02-01
significant amount of lead mobilization. Studies by Lyson and Lenihan,ŝ Wong and Berrang,2 ° and Ierrra, t al.2’ describe this action and document the...Karaleka,. Jr. 1m I) V. Dc err , c a). T. Lyson and J. Lcnihan. ’Corrosion in Solder Jointed Copper tbes Resulting in Lead Contamination of Drinking...Boston Area," Journal of the New England Water Works Association, Vol 90 (1976). Lyson , T., and J. Lenihan, "Corrosion in Solder Jointed Copper Tubes
CrossTalk, The Journal of Defense Software Engineering. Volume 26, Number 2. March/April 2013
2013-04-01
standards and best practices. “Software and hardware are at risk of being tam - pered with even before they are linked together in an operational system...because of their role in national and global security and the variety of valuable lessons learned and best practices they can provide because they are...Management. GAO said DoD’s efforts to implement SCRM can be a learning tool for others in the Federal government. DoD is currently imple- CrossTalk
Towards a Unified Theory of Engineering Education
ERIC Educational Resources Information Center
Salcedo Orozco, Oscar H.
2017-01-01
STEM education is an interdisciplinary approach to learning where rigorous academic concepts are coupled with real-world lessons and activities as students apply science, technology, engineering, and mathematics in contexts that make connections between school, community, work, and the global enterprise enabling STEM literacy (Tsupros, Kohler and…
ERIC Educational Resources Information Center
Hagerott, Steven G.
1997-01-01
A Lockheed flight controls engineer describes how, as an undergraduate, he taught first graders basic lessons in physics and engineering by using slides, monkey bars, and other playground equipment to demonstrate principles like gravity, friction, force, and inertia. The children learned more about lift and gravity by constructing and flying paper…
The potential ecological consequences of the commercialization of genetically engineered (GD) crops have been the subject of intense debate, particularly when the GE crops are perennial and capable of outcrossing to wild relatives. The essential ecological impact issues for engi...
1999 NASA Seal/Secondary Air System Workshop
NASA Technical Reports Server (NTRS)
Steinetz, Bruce M.; Hendricks, Robert C.
2000-01-01
NASA Glenn hosted the Seals/Secondary Air System Workshop on October 2829, 1999. Each year NASA and our industry and university partners share their respective seal technology development. We use these workshops as a technical forum to exchange recent advancements and "lessons-learned" in advancing seal technology and solving problems of common interest. As in the past we are publishing two volumes. Volume 1 will be publicly available and will be made available on-line through the web page address listed at the end of this chapter. Volume 2 will be restricted under International Traffic and Arms Regulations (I.T.A.R.) In this conference participants gained an appreciation of NASA's new Ultra Efficient Engine Technology (UEET) program and how this program will be partnering with ongoing DOE -industrial power production and DOD- military aircraft engine programs. In addition to gaining a deeper understanding into sealing advancements and challenges that lie ahead, participants gained new working and personal relationships with the attendees. When the seals and secondary fluid management program was initiated, the emphasis was on rocket engines with spinoffs to gas turbines. Today, the opposite is true and we are, again building our involvement in the rocket engine and space vehicle demonstration programs.
NASA Technical Reports Server (NTRS)
Pryor, D.; Hyde, E. H.; Escher, W. J. D.
1999-01-01
Airbreathing/Rocket combined-cycle, and specifically rocket-based combined- cycle (RBCC), propulsion systems, typically employ an internal engine flow-path installed primary rocket subsystem. To achieve acceptably short mixing lengths in effecting the "air augmentation" process, a large rocket-exhaust/air interfacial mixing surface is needed. This leads, in some engine design concepts, to a "cluster" of small rocket units, suitably arrayed in the flowpath. To support an early (1964) subscale ground-test of a specific RBCC concept, such a 12-rocket cluster was developed by NASA's Marshall Space Flight Center (MSFC). The small primary rockets used in the cluster assembly were modified versions of an existing small kerosene/oxygen water-cooled rocket engine unit routinely tested at MSFC. Following individual thrust-chamber tests and overall subsystem qualification testing, the cluster assembly was installed at the U. S. Air Force's Arnold Engineering Development Center (AEDC) for RBCC systems testing. (The results of the special air-augmented rocket testing are not covered here.) While this project was eventually successfully completed, a number of hardware integration problems were met, leading to catastrophic thrust chamber failures. The principal "lessons learned" in conducting this early primary rocket subsystem experimental effort are documented here as a basic knowledge-base contribution for the benefit of today's RBCC research and development community.
NASA Astrophysics Data System (ADS)
van der Lee, S.; Tekverk, K.; Rooney, K.; Boxerman, J.
2013-12-01
We designed and will present a lesson plan to teach students STEM concepts through seismology. The plan addresses new generation science standards in the Framework for K-12 Science Education as well AAAS Benchmarks for Science Literacy. The plan can be executed at a facility with a seismometer in a research facility or university, on a field trip, but it can also be used in a school setting with a school seismometer. Within the lesson plan, the students first use technology to obtain earthquake location data and map them. Next, the students learn about the science of earthquakes, which is followed by an engineering activity in which the students design a hypothetical seismometer and interact with the actual seismometer and live data display. Lastly the students use mathematics to locate an earthquake through trilateration. The lesson plan has been fine-tuned through implementation with over 150 students from grades 3-12 from the Chicago area.
ERIC Educational Resources Information Center
Squires, Frances H.
This science curriculum was written for teachers of children in the elementary grades. It contains science activities for the following lessons: (1) Whirly Birds and the Concept of Lift; (2) Parachutes; (3) Weather Vanes; (4) Paper Airplanes; (5) Flying an Airplane; (6) Jet Engine; (7) Identifying Flying Objects; (8) It's a Bird! It's a Plane; (9)…
ERIC Educational Resources Information Center
Zervas, Panagiotis; Tsourlidaki, Eleftheria; Cao, Yiwei; Sotiriou, Sofoklis; Sampson, Demetrios G.; Faltin, Nils
2016-01-01
Online labs (OLs) constitute digital educational tools which can have a significant role in supporting science, technology, engineering and mathematics (STEM) teachers in their daily teaching practice. Designing STEM lessons supported by specific OLs is a challenging task and thus, it is useful for STEM teachers to be able to share their lesson…
2011-10-01
Effective planning early in and throughout program develop - ment is critical to enabling manufacturing affordability. There is no silver bullet and no...unexpected lessons. “Gee, this stove is hot” may be an unexpected lesson for the toddler but should not be so for the adult. All production programs...in program design efforts from day 1 of Engineer- ing and Manufacturing Development , you should be seriously worried. A program that includes the
ERIC Educational Resources Information Center
Ward, Nicholas D.; Finley, Rachel J.; Keil, Richard G.; Clay, Tansy G.
2013-01-01
This study explores the utility of a set of tablet-based personal computers in the K-12 science, technology, engineering, and mathematics classroom. Specifically, a lesson on food-chain dynamics and predator-prey population controls was designed on the Apple® iPad platform and delivered to three sophomore-level ecology classes (roughly 30 students…
Measuring the software process and product: Lessons learned in the SEL
NASA Technical Reports Server (NTRS)
Basili, V. R.
1985-01-01
The software development process and product can and should be measured. The software measurement process at the Software Engineering Laboratory (SEL) has taught a major lesson: develop a goal-driven paradigm (also characterized as a goal/question/metric paradigm) for data collection. Project analysis under this paradigm leads to a design for evaluating and improving the methodology of software development and maintenance.
NASA Astrophysics Data System (ADS)
Rolland, Colette; Yu, Eric; Salinesi, Camille; Castro, Jaelson
The use of intentional concepts, the notion of "goal" in particular, has been prominent in recent approaches to requirement engineering (RE). Goal-oriented frameworks and methods for requirements engineering (GORE) have been keynote topics in requirements engineering, conceptual modelling, and more generally in software engineering. What are the conceptual modelling foundations in these approaches? RIGiM (Requirements Intentions and Goals in Conceptual Modelling) aims to provide a forum for discussing the interplay between requirements engineering and conceptual modelling, and in particular, to investigate how goal- and intention-driven approaches help in conceptualising purposeful systems. What are the fundamental objectives and premises of requirements engineering and conceptual modelling respectively, and how can they complement each other? What are the demands on conceptual modelling from the standpoint of requirements engineering? What conceptual modelling techniques can be further taken advantage of in requirements engineering? What are the upcoming modelling challenges and issues in GORE? What are the unresolved open questions? What lessons are there to be learnt from industrial experiences? What empirical data are there to support the cost-benefit analysis when adopting GORE methods? Are there application domains or types of project settings for which goals and intentional approaches are particularly suitable or not suitable? What degree of formalization and automation, or interactivity is feasible and appropriate for what types of participants during requirements engineering?
NASA Technical Reports Server (NTRS)
Dumbacher, Daniel L.
2006-01-01
The United States (US) Vision for Space Exploration, announced in January 2004, outlines the National Aeronautics and Space Administration's (NASA) strategic goals and objectives, including retiring the Space Shuttle and replacing it with new space transportation systems for missions to the Moon, Mars, and beyond. The Crew Exploration Vehicle (CEV) that the new human-rated Crew Launch Vehicle (CLV) lofts into space early next decade will initially ferry astronauts to the International Space Station (ISS) Toward the end of the next decade, a heavy-lift Cargo Launch Vehicle (CaLV) will deliver the Earth Departure Stage (EDS) carrying the Lunar Surface Access Module (LSAM) to low-Earth orbit (LEO), where it will rendezvous with the CEV launched on the CLV and return astronauts to the Moon for the first time in over 30 years. This paper outlines how NASA is building these new space transportation systems on a foundation of legacy technical and management knowledge, using extensive experience gained from past and ongoing launch vehicle programs to maximize its design and development approach, with the objective of reducing total life cycle costs through operational efficiencies such as hardware commonality. For example, the CLV in-line configuration is composed of a 5-segment Reusable Solid Rocket Booster (RSRB), which is an upgrade of the current Space Shuttle 4- segment RSRB, and a new upper stage powered by the liquid oxygen/liquid hydrogen (LOX/LH2) J-2X engine, which is an evolution of the J-2 engine that powered the Apollo Program s Saturn V second and third stages in the 1960s and 1970s. The CaLV configuration consists of a propulsion system composed of two 5-segment RSRBs and a 33- foot core stage that will provide the LOX/LED needed for five commercially available RS-68 main engines. The J-2X also will power the EDS. The Exploration Launch Projects, managed by the Exploration Launch Office located at NASA's Marshall Space Flight Center, is leading the design, development, testing, and operations planning for these new space transportation systems. Utilizing a foundation of heritage hardware and management lessons learned mitigates both technical and programmatic risk. Project engineers and managers work closely with the Space Shuttle Program to transition hardware, infrastructure, and workforce assets to the new launch systems, leveraging a wealth of knowledge from Shuffle operations. In addition, NASA and its industry partners have tapped into valuable Apollo databases and are applying corporate wisdom conveyed firsthand by Apollo-era veterans of America s original Moon missions. Learning from its successes and failures, NASA employs rigorous systems engineering and systems management processes and principles in a disciplined, integrated fashion to further improve the probability of mission success.
Two-panel LCOS-based projection system: a potentially compact high-resolution avionics display
NASA Astrophysics Data System (ADS)
Sharp, Gary D.; Chen, Jianmin; Robinson, Michael B.; Korah, John K.
2003-09-01
Military displays have been limited first by the availability of CRT and then AMLCD for color multifunctional displays. Projection display technology has been offered as an alternative. With the growth of the LCOS based consumer projection display industry, commercially off the shelf (COTS) components and technology are becoming readily available. A projection display system addresses the lessons learned from the CRT or AMLCD based attempts. This approach presents multiple vendors and user defined aspect ratio, resolution, brightness and color. This paper will present the latest work at ColorLink, Inc. on a two-panel LCOS based projection light engine developed for the consumer industry driven Rear Projection Television (RPTV) market. This engine demonstrates throughput, contrast and color performance that exceeds military requirements using COTS technology and components. We will introduce the core technology and philosophy followed by this industry in defining such a product.
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.
Boehm, K. -J.; Hash, N.; Barker, D.; ...
2016-06-24
Reconciling the experimental and system requirements during the development of a new target system is one of the most challenging tasks in the design and engineering of targets used in the National Ignition Facility. Targets for the GigaBar 3 campaign were meant to allow the detection of extremely weak Thomson scattering from matter at extreme densities in the face of very bright backlighter and laser entry hole plasma emissions. The problem was to shield the detector sufficiently while maintaining beamline and view clearances, and observing target mass restrictions. A new construction process, based on a rapid prototype frame structure, wasmore » used to develop this target. As a result, details of the design process for these targets are described, and lessons from this development for production and target assembly teams are discussed.« less
Adaptive design lessons from professional architects
NASA Astrophysics Data System (ADS)
Geiger, Ray W.; Snell, J. T.
1993-09-01
Psychocybernetic systems engineering design conceptualization is mimicking the evolutionary path of habitable environmental design and the professional practice of building architecture, construction, and facilities management. In pursuing better ways to design cellular automata and qualification classifiers in a design process, we have found surprising success in exploring certain more esoteric approaches, e.g., the vision of interdisciplinary artistic discovery in and around creative problem solving. Our evaluation in research into vision and hybrid sensory systems associated with environmental design and human factors has led us to discover very specific connections between the human spirit and quality design. We would like to share those very qualitative and quantitative parameters of engineering design, particularly as it relates to multi-faceted and future oriented design practice. Discussion covers areas of case- based techniques of cognitive ergonomics, natural modeling sources, and an open architectural process of means/goal satisfaction, qualified by natural repetition, gradation, rhythm, contrast, balance, and integrity of process.
Lessons Learned with Metallized Gelled Propellants
NASA Technical Reports Server (NTRS)
1996-01-01
During testing of metallized gelled propellants in a rocket engine, many changes had to be made to the normal test program for traditional liquid propellants. The lessons learned during the testing and the solutions for many of the new operational conditions posed with gelled fuels will help future programs run more smoothly. The major factors that influenced the success of the testing were propellant settling, piston-cylinder tank operation, control of self pressurization, capture of metal oxide particles, and a gelled-fuel protective layer. In these ongoing rocket combustion experiments at the NASA Lewis Research Center, metallized, gelled liquid propellants are used in a small modular engine that produces 30 to 40 lb of thrust. Traditional liquid RP-1 and gelled RP-1 with 0-, 5-, and 55-wt% loadings of aluminum are used with gaseous oxygen as the oxidizer. The figure compares the thrust chamber efficiencies of different engines.
AFRL Solid Propellant Laboratory Explosive Siting and Renovation Lessons Learned
2010-07-01
Area 1-30A explosive facility and provide consultation/support during the review process for each of the site plans. • Applied Engineering Services...provided consultation/support during the siting review process. • Applied Engineering Services (AES) Inc. performed a detailed structural, blast, thermal... Applied Engineering Services (AES) Inc. structural, blast, thermal and fragment hazard analysis to determine the appropriate siting values based on
Software Engineering Principles for Courseware Development.
ERIC Educational Resources Information Center
Magel, Kenneth
1980-01-01
Courseware (computer based curriculum materials) development should follow the lessons learned by software engineers. The most important of 28 principles of software development presented here include a stress on human readability, the importance of early planning and analysis, the need for independent evaluation, and the need to be flexible.…
Genetic Engineering--A Lesson on Bioethics for the Classroom.
ERIC Educational Resources Information Center
Armstrong, Kerri; Weber, Kurt
1991-01-01
A unit designed to cover the topic of genetic engineering and its ethical considerations is presented. Students are expected to learn the material while using a debate format. A list of objectives for the unit, the debate format, and the results from an opinion questionnaire are described. (KR)
Optimizing Your K-5 Engineering Design Challenge
ERIC Educational Resources Information Center
Coppola, Matthew Perkins; Merz, Alice H.
2017-01-01
Today, elementary school teachers continue to revisit old lessons and seek out new ones, especially in engineering. Optimization is the process by which an existing product or procedure is revised and refined. Drawn from the authors' experiences working directly with students in grades K-5 and their teachers and preservice teachers, the…
Engine Fundamentals: Automotive Mechanics Instructional Program. Block 2.
ERIC Educational Resources Information Center
O'Brien, Ralph D.
The second of six instructional blocks in automotive mechanics, the lessons and supportive information in the document provide a guide for teachers in planning an instructional program in engine fundamentals at the secondary and postsecondary level. The material, as organized, is a suggested sequence of instruction within each block. Each lesson…
Space Shuttle Main Engine Liquid Air Insulation Redesign Lessons Learned
NASA Technical Reports Server (NTRS)
Gaddy, Darrell; Carroll, Paul; Head, Kenneth; Fasheh, John; Stuart, Jessica
2010-01-01
The Space Shuttle Main Engine Liquid Air Insulation redesign was required to prevent the reoccurance of the STS-111 High Pressure Speed Sensor In-Flight Anomaly. The STS-111 In-Flight Anomaly Failure Investigation Team's initial redesign of the High Pressure Fuel Turbopump Pump End Ball Bearing Liquid Air Insulation failed the certification test by producing Liquid Air. The certification test failure indicated not only the High Pressure Fuel Turbopump Liquid Air Insulation, but all other Space Shuttle Main Engine Liquid Air Insulation. This paper will document the original Space Shuttle Main Engine Liquid Air STS-111 In-Flight Anomaly investigation, the heritage Space Shuttle Main Engine Insulation certification testing faults, the techniques and instrumentation used to accurately test the Liquid Air Insulation systems on the Stennis Space Center SSME test stand, the analysis techniques used to identify the Liquid Air Insulation problem areas and the analytical verification of the redesign before entering certification testing, Trade study down selected to three potential design solutions, the results of the development testing which down selected the final Liquid Air Redesign are also documented within this paper.
Documenting Lessons Learned in Afghanistan Concerning Design and Construction Challenges
2011-01-01
Engineer Research and Development Center 72 Lyme Road Hanover, IL 61822 Michael Deegan Institute of Water Resources U.S. Army Corps of Engineers...Deegan, U.S. Army Corps of Engineers, Institute Water Re- sources; Dr. Reed Freeman, U.S. Army Engineer District, Afghanistan; and Dr. Shad Sargand...and gravel as well as cobbles. Higher elevations have sandy soil and rock outcrops. The water table is commonly encountered 30−70 ft (10-20 m
Intelligent systems engineering methodology
NASA Technical Reports Server (NTRS)
Fouse, Scott
1990-01-01
An added challenge for the designers of large scale systems such as Space Station Freedom is the appropriate incorporation of intelligent system technology (artificial intelligence, expert systems, knowledge-based systems, etc.) into their requirements and design. This presentation will describe a view of systems engineering which successfully addresses several aspects of this complex problem: design of large scale systems, design with requirements that are so complex they only completely unfold during the development of a baseline system and even then continue to evolve throughout the system's life cycle, design that involves the incorporation of new technologies, and design and development that takes place with many players in a distributed manner yet can be easily integrated to meet a single view of the requirements. The first generation of this methodology was developed and evolved jointly by ISX and the Lockheed Aeronautical Systems Company over the past five years on the Defense Advanced Research Projects Agency/Air Force Pilot's Associate Program, one of the largest, most complex, and most successful intelligent systems constructed to date. As the methodology has evolved it has also been applied successfully to a number of other projects. Some of the lessons learned from this experience may be applicable to Freedom.
Signal Systems of Lesson Settings and the Task-Related Behavior of Preschool Children
ERIC Educational Resources Information Center
Kounin, Jacob S.; Gump, Paul V.
1974-01-01
Teachers were videotaped teaching lessons. Lessons were seen as signal systems to participants. These signal systems were characterized along dimensions of continuity, insulation, and intrusiveness. Task involvement was used as the criterion. Results indicate most successful to least successful lessons, based on signal systems. (Author/SE)
System Issues Related to Implementing on the Internet
NASA Technical Reports Server (NTRS)
Mackey, William; Bagg, Thomas C., III
1999-01-01
Implementing capabilities on the World Wide Web should never be taken lightly. A good systems engineer is able to examine such implementations from all points of view, including political, legal, security, access, technical deployment, and quality. The evacuation discussed in this paper was conducted to ensure that the National Aeronautics and Space Administration (NASA) was proceeding in a correct direction by implementing RECALL a Lessons Learned System on the Web and, subsequently, did so successfully. The systems approach extended well beyond technical implementation to several issue that are not often addressed by an implementation team. The resulting evaluation increased the team's sensitivity to such issues and, in fact, the authors believe that the evaluation provided as much benefit as the system itself.
NASA Astrophysics Data System (ADS)
Morrow, C. A.; Throop, H. B.
1998-09-01
NASA's Cassini Mission to Saturn is the most ambitious deep space mission ever. Its 4-year scientific tour of Saturn, its majestic rings, and its 18 presently known moons will reveal new beauty, richness and insights on behalf of all humankind. This presentation introduces the inquiry-based lessons from the innovative Saturn Educator Guide, appropriate for grades 5-8. The Guide is the product of a collaborative venture among teachers, scientists, engineers, and education researchers. The Guide offers opportunities to explore Saturn as a system, and the Cassini robotic spacecraft as an extension of human senses. There are also unique lessons on the history of science, science as a human endeavor, and science in social and personal perspectives. The Guide highlights the interconnections between Saturn and other areas of human endeavor (art, language, history and mythology). This distinctive blend will enable a grander diversity of learners to share and benefit from the excitement of Cassini mission discoveries.
FINAL DESIGN REVIEW REPORT Subcritical Experiments Gen 2, 3-ft Confinement Vessel Weldment
DOE Office of Scientific and Technical Information (OSTI.GOV)
Romero, Christopher
A Final Design Review (FDR) of the Subcritical Experiments (SCE) Gen 2, 3-ft. Confinement Vessel Weldment was held at Los Alamos National Laboratory (LANL) on September 14, 2017. The review was a focused review on changes only to the confinement vessel weldment (versus a system design review). The changes resulted from lessons-learned in fabricating and inspecting the current set of confinement vessels used for the SCE Program. The baseline 3-ft. confinement vessel weldment design has successfully been used (to date) for three (3) high explosive (HE) over-tests, two (2) fragment tests, and five (5) integral HE experiments. The design teammore » applied lessons learned from fabrication and inspection of these vessel weldments to enhance fit-up, weldability, inspection, and fitness for service evaluations. The review team consisted of five (5) independent subject matter experts with engineering design, analysis, testing, fabrication, and inspection experience. The« less
NASA Astrophysics Data System (ADS)
Maeng, Jennifer L.; Whitworth, Brooke A.; Gonczi, Amanda L.; Navy, Shannon L.; Wheeler, Lindsay B.
2017-07-01
This randomised controlled trial used a mixed-methods approach to investigate the frequency and how elementary teachers integrated engineering design (ED) principles into their science instruction following professional development (PD). The ED components of the PD were aligned with Cunningham and Carlsen's [(2014). Teaching engineering practices. Journal of Science Teacher Education, 25, 197-210] guidelines for ED PD and promoted inclusion of ED within science teaching. The treatment group included 219 teachers from 83 schools. Participants in the control group included 145 teachers from 60 schools in a mid-Atlantic state. Data sources, including lesson overviews and videotaped classroom observations, were analysed quantitatively to determine the frequency of ED integration and qualitatively to describe how teachers incorporated ED into instruction after attending the PD. Results indicated more participants who attended the PD (55%) incorporated ED into instruction compared with the control participants (24%), χ2(1, n = 401) = 33.225, p < .001, ? = 0.308. Treatment and control teachers taught similar science content (p's > .05) through ED lessons. In ED lessons, students typically conducted research and created and tested initial designs. The results suggest the PD supported teachers in implementing ED into their science instruction and support the efficacy of using Cunningham and Carlsen's (2014) guidelines to inform ED PD design.
NASA Astrophysics Data System (ADS)
Birkholzer, J. T.
2017-12-01
This presentation provides an overview of an international research and model comparison collaboration (DECOVALEX) for advancing the understanding and modeling of coupled thermo-hydro-mechanical-chemical (THMC) processes in geological systems. Prediction of these coupled effects is an essential part of the performance and safety assessment of geologic disposal systems for radioactive waste and spent nuclear fuel, and is also relevant for a range of other sub-surface engineering activities. DECOVALEX research activities have been supported by a large number of radioactive-waste-management organizations and regulatory authorities. Research teams from more than a dozen international partner organizations have participated in the comparative modeling evaluation of complex field and laboratory experiments in the UK, Switzerland, Japan, France and Sweden. Together, these tasks (1) have addressed a wide range of relevant issues related to engineered and natural system behavior in argillaceous, crystalline and other host rocks, (2) have yielded in-depth knowledge of coupled THM and THMC processes associated with nuclear waste repositories and wider geo-engineering applications, and (3) have advanced the capability, as well as demonstrated the suitability, of numerical simulation models for quantitative analysis.
Mission EarthFusing GLOBE with NASA Assets to Build SystemicInnovation in STEM Education
NASA Astrophysics Data System (ADS)
Czajkowski, K. P.; Garik, P.; Padgett, D.; Darche, S.; Struble, J.; Adaktilou, N.
2016-12-01
Mission Earth is a project funded through the NASA CAN that is developing a systematic embedding of NASA assets that is being implemented by a partnership of organizations across the US. Mission Earth brings together scientists and science educators to develop a K-12 "Earth as a system" curriculum progression following research-based best practices. GLOBE and NASA assets will be infused into the curricula of schools along the K-12 continuum, leveraging existing partnerships and networks and supported through state departments of education and targeting underrepresented groups, as a systemic, effective, and sustainable approach to meeting NASA's science education objectives. This presentation will discuss plans for the Mission Earth project and successes and lessons learned in the first year. Mission Earth is developing curricular materials to support vertically integrated learning progressions. It develops models of professional development utilizing sustainable infrastructures. It will support STEM careers focusing on career technical education (CTE). And, it will engage undergraduate education majors through pre-service courses and engineering students through engineering challenges.
NASA Astrophysics Data System (ADS)
Minamino, Yoritoshi
Department of Adaptive Machine Systems, Department of Materials and Manufucturing Science and Department of Business engineering have constructed the educational programs of consecutive system from master to doctor courses in graduate school of engineering, “Pioneering Integrated Education and Research Program (PP) ”, to produce volitional and original mind researchers with high abilities of research, internationality, leader, practice, management and economics by cooperation between them for reinforcement of their ordinary curriculums. This program consists of the basic PP for master course students and the international exchange PP, leadership pp and tie-up PP of company and University for Doctor course students. In 2005th the basic PP was given to the master course students and then their effectiveness of the PP was investigated by questionnaire. The results of questionnaire proved that the graduate school students improved their various abilities by the practical lesson in cooperation between companies and our Departments in the basic PP, and that the old boys after basic PP working in companies appreciated the advantages to business planning, original conception, finding solution, patents, discussion, report skills required in companies.
NASA Technical Reports Server (NTRS)
Jellicorse, John J.; Rahman, Shamin A.
2016-01-01
NASA is currently developing the next generation crewed spacecraft and launch vehicle for exploration beyond earth orbit including returning to the Moon and making the transit to Mars. Managing the design integration of major hardware elements of a space transportation system is critical for overcoming both the technical and programmatic challenges in taking a complex system from concept to space operations. An established method of accomplishing this is formal interface management. In this paper we set forth an argument that the interface management process implemented by NASA between the Orion Multi-Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) achieves the Level 3 tier of the EIA 731.1 System Engineering Capability Model (SECM) for Generic Practices. We describe the relevant NASA systems and associated organizations, and define the EIA SECM Level 3 Generic Practices. We then provide evidence for our compliance with those practices. This evidence includes discussions of: NASA Systems Engineering Interface (SE) Management standard process and best practices; the tailoring of that process for implementation on the Orion to SLS interface; changes made over time to improve the tailored process, and; the opportunities to take the resulting lessons learned and propose improvements to our institutional processes and best practices. We compare this evidence against the practices to form the rationale for the declared SECM maturity level.
ERIC Educational Resources Information Center
Manpower Administration (DOL), Washington, DC. Job Corps.
This self-study program for high-school level contains lessons on: Life Functions and Cells; Cell Structure; Tissues, Organs, Systems; Growth and Nutrition; and Metabolism. Each of the lessons concludes with a Mastery Test to be completed by the student. (DB)
A Survey of Health Management User Objectives Related to Diagnostic and Prognostic Metrics
NASA Technical Reports Server (NTRS)
Wheeler, Kevin R.; Kurtoglu, Tolga; Poll, Scott D.
2010-01-01
One of the most prominent technical challenges to effective deployment of health management systems is the vast difference in user objectives with respect to engineering development. In this paper, a detailed survey on the objectives of different users of health management systems is presented. These user objectives are then mapped to the metrics typically encountered in the development and testing of two main systems health management functions: diagnosis and prognosis. Using this mapping, the gaps between user goals and the metrics associated with diagnostics and prognostics are identified and presented with a collection of lessons learned from previous studies that include both industrial and military aerospace applications.
NASA Applications and Lessons Learned in Reliability Engineering
NASA Technical Reports Server (NTRS)
Safie, Fayssal M.; Fuller, Raymond P.
2011-01-01
Since the Shuttle Challenger accident in 1986, communities across NASA have been developing and extensively using quantitative reliability and risk assessment methods in their decision making process. This paper discusses several reliability engineering applications that NASA has used over the year to support the design, development, and operation of critical space flight hardware. Specifically, the paper discusses several reliability engineering applications used by NASA in areas such as risk management, inspection policies, components upgrades, reliability growth, integrated failure analysis, and physics based probabilistic engineering analysis. In each of these areas, the paper provides a brief discussion of a case study to demonstrate the value added and the criticality of reliability engineering in supporting NASA project and program decisions to fly safely. Examples of these case studies discussed are reliability based life limit extension of Shuttle Space Main Engine (SSME) hardware, Reliability based inspection policies for Auxiliary Power Unit (APU) turbine disc, probabilistic structural engineering analysis for reliability prediction of the SSME alternate turbo-pump development, impact of ET foam reliability on the Space Shuttle System risk, and reliability based Space Shuttle upgrade for safety. Special attention is given in this paper to the physics based probabilistic engineering analysis applications and their critical role in evaluating the reliability of NASA development hardware including their potential use in a research and technology development environment.
Lessons Learned from Recent Failure and Incident Investigations of Composite Structures
NASA Technical Reports Server (NTRS)
Ransom, J. B.; Glaessgen, E. H.; Raju, L. S.; Knight, N. F., Jr.; Reeder, J. R.
2008-01-01
During the past few decades, NASA Langley Research Center (LaRC) has supported several large-scale failure and incident investigations and numerous requests for engineering consultations. Although various extenuating circumstances contributed to each of these incidents, in all cases, the failure resulted from accumulation and/or propagation of damage that reduced the load carrying capability of the structure to a level below that which was needed to sustain structural loads. A brief overview of various failure and incident investigations supported by LaRC, including some of the computational and experimental methodologies that have been applied, is presented. An important outcome of many of these failure and incident investigations is the development of an improved understanding of not only the state-of-the-art in experimental and analytical methods but also the state-of-the-art in the design and manufacturing processes that may contribute to such failures. In order to provide insight into such large-scale investigations, a series of lessons learned were captured. Awareness of these lessons learned is highly beneficial to engineers involved in similar investigations. Therefore, it is prudent that the lessons learned are disseminated such that they can be built upon in other investigations and in ensuing research and development activities.
NASA Astrophysics Data System (ADS)
Sánchez-Martín, Jesús; Álvarez-Gragera, García J.; Dávila-Acedo, M. Antonia; Mellado, Vicente
2017-11-01
The interest on engineering and scientific studies can be raised up even from the early years of academic instructional process. This vocation may be linked to emotions and aptitudes towards technological education. Particularly, students get in touch with these technological issues (namely STEM) during the Compulsory Secondary Education in Spain (12-16 years old).This work presents a preliminary evaluation of how relevant is Gardner's multiple intelligence theory (MIT) in the teaching-learning process within the Technology Lessons. In this sense, MIT was considered as an explanation variable of the emotional response within the different educational parts (so-called syllabus units, SU) in the Technology spanish curriculum. Different intelligence style (IS) will orient the student to a vision of the engineering and technology. This work tries to identify which relationships can be established between IS and specific technology and engineering learning. This research involved up to 135 students were subsequently tested about their predominant (IS) and on the emotions that arouse in them when working with each SU. The results were statistically significant and only those with a Logic-arithmetic or Environmental IS were not affected by the SU.Best teaching and learning practicesare required for encouraging further engineering studies.
Chemical Engineering and Instructional Computing: Are They in Step? (Part 2).
ERIC Educational Resources Information Center
Seider, Warren D.
1988-01-01
Describes the use of "CACHE IBM PC Lessons for Courses Other than Design and Control" as open-ended design oriented problems. Presents graphics from some of the software and discusses high-resolution graphics workstations. Concludes that computing tools are in line with design and control practice in chemical engineering. (MVL)
The Benefits of Using Engineering as a Context for Science Lessons
ERIC Educational Resources Information Center
Taylor, Gemma
2014-01-01
"Real life" learning has often been suggested as a good method for engaging students in the science curriculum. In this article, an evidence-based rationale for the use of engineering as a context for "real life" science study is explained. This has been achieved through development work undertaken by the National Science…
A Case Study of Coaching in Science, Technology, Engineering, and Math Professional Development
ERIC Educational Resources Information Center
DeChenne, Sue Ellen; Nugent, Gwen; Kunz, Gina; Luo, Linlin; Berry, Brandi; Craven, Katherine; Riggs, April
2012-01-01
A professional development experience for science and mathematics teachers that included coaches was provided for ten science and math teachers. This professional development experience had the teachers develop a lesson that utilized the engineering context to teach a science or mathematics concept through guided inquiry as an instructional…
Stationary Engineering, Environmental Control, Refrigeration. Science I--Teachers Guide.
ERIC Educational Resources Information Center
Steingress, Frederick M.; And Others
The document presents lessons for teaching about occupations related to environmental control, stationary engineering, and refrigeration. Intended for use with the assignments in the related science manual for students, each unit provides the teacher with objectives, a list of aids needed, procedures, a summary, and testing questions. There are 18…
Teaching Technical Writing in a Lab Course in Chemical Engineering
ERIC Educational Resources Information Center
Lombardo, Stephen J.
2010-01-01
Techniques are presented for improving the technical writing of chemical engineering students enrolled in an undergraduate laboratory course. The principles of writing covered are adopted from the book, Style: Lessons in Clarity and Grace, by Joseph M. Williams: General examples of writing are taken from this book and then are recast into examples…
Information Technologies in Higher Education: Lessons Learned in Industrial Engineering
ERIC Educational Resources Information Center
Delgado-Almonte, Milagros; Andreu, Hernando Bustos; Pedraja-Rejas, Liliana
2010-01-01
This article describes a teaching experience in which information and communication technologies were applied in five industrial engineering courses at the Universidad de Tarapaca in Chile. The paper compares the performance and course pass rates of the e-learning platform and portable pocket PC platform with those of the same courses teaching in…
Making Space for the Act of Making: Creativity in the Engineering Design Classroom
ERIC Educational Resources Information Center
Lasky, Dorothea; Yoon, Susan A.
2011-01-01
Creativity continues to be an important goal for 21st century learning. However, teachers often have difficulties fostering creativity in their classrooms. Current creativity research suggests that the act of making can enhance the teaching of creativity. Hands-on engineering design lessons are ideal contexts for studying this effect. Through…
ERIC Educational Resources Information Center
Tank, Kristina; Moore, Tamara; Strnat, Meg
2015-01-01
This article describes the final lesson within a seven-day STEM and literacy unit that is part of the Picture STEM curriculum (pictureSTEM. org) and uses engineering to integrate science and mathematics learning in a meaningful way (Tank and Moore 2013). For this engineering challenge, students used nature as a source of inspiration for designs to…
Stationary Engineers Apprenticeship. Related Training Modules. 4.1-4.5 Tools.
ERIC Educational Resources Information Center
Lane Community Coll., Eugene, OR.
This packet of five learning modules on tools is one of 20 such packets developed for apprenticeship training for stationary engineers. Introductory materials are a complete listing of all available modules and a supplementary reference list. Each module contains some or all of these components: a lesson goal, performance indicators, study guide…
Development of a Work Control System for Propulsion Testing at NASA Stennis
NASA Technical Reports Server (NTRS)
Messer, Elizabeth A.
2005-01-01
In 1996 Stennis Space Center was given management authority for all Propulsion Testing for NASA. Over the next few years several research and development (R&D) test facilities were completed and brought up to full operation in what is known as the E-Complex Test Facility at Stennis Space Center. To construct, activate and operate these test facilities, a manual paper-based work control system was created. After utilizing this paper-based work control system for approximately three years, it became apparent that the research and development test area needed a better method to execute, monitor, and report on tasks required to further propulsion testing. The paper based system did not provide the engineers adequate visibility into work tasks or the tracking of testing or hardware discrepancies. This system also restricted the engineer s ability to utilize and access past knowledge and experiences given the severe schedule limitations for most R&D propulsion testing projects. Therefore a system was developed to meet the growing need of Test Operations called the Propulsion Test Directorate (PTD) Work Control System. This system is used to plan, perform, and track tasks that support testing and also to capture lessons learned while doing so.
EDSN Development Lessons Learned
NASA Technical Reports Server (NTRS)
Chartres, James; Sanchez, Hugo S.; Hanson, John
2014-01-01
The Edison Demonstration of Smallsat Networks (EDSN) is a technology demonstration mission that provides a proof of concept for a constellation or swarm of satellites performing coordinated activities. Networked swarms of small spacecraft will open new horizons in astronomy, Earth observations and solar physics. Their range of applications include the formation of synthetic aperture radars for Earth sensing systems, large aperture observatories for next generation telescopes and the collection of spatially distributed measurements of time varying systems, probing the Earths magnetosphere, Earth-Sun interactions and the Earths geopotential. EDSN is a swarm of eight 1.5U Cubesats with crosslink, downlink and science collection capabilities developed by the NASA Ames Research Center under the Small Spacecraft Technology Program (SSTP) within the NASA Space Technology Mission Directorate (STMD). This paper describes the concept of operations of the mission and planned scientific measurements. The development of the 8 satellites for EDSN necessitated the fabrication of prototypes, Flatsats and a total of 16 satellites to support the concurrent engineering and rapid development. This paper has a specific focus on the development, integration and testing of a large number of units including the lessons learned throughout the project development.
Quantifying Cyber-Resilience Against Resource-Exhaustion Attacks
DOE Office of Scientific and Technical Information (OSTI.GOV)
Fink, Glenn A.; Griswold, Richard L.; Beech, Zachary W.
2014-07-11
Resilience in the information sciences is notoriously difficult to define much less to measure. But in mechanical engi- neering, the resilience of a substance is mathematically defined as the area under the stress vs. strain curve. We took inspiration from mechanics in an attempt to define resilience precisely for information systems. We first examine the meaning of resilience in language and engineering terms and then translate these definitions to information sciences. Then we tested our definitions of resilience for a very simple problem in networked queuing systems. We discuss lessons learned and make recommendations for using this approach in futuremore » work.« less
Tissue engineering on the nanoscale: lessons from the heart.
Fleischer, Sharon; Dvir, Tal
2013-08-01
Recognizing the limitations of biomaterials for engineering complex tissues and the desire for closer recapitulation of the natural matrix have led tissue engineers to seek new technologies for fabricating 3-dimensional (3D) cellular microenvironments. In this review, through examples from cardiac tissue engineering, we describe the nanoscale hallmarks of the extracellular matrix that tissue engineers strive to mimic. Furthermore, we discuss the use of inorganic nanoparticles and nanodevices for improving and monitoring the performance of engineered tissues. Finally, we offer our opinion on the main challenges and prospects of applying nanotechnology in tissue engineering. Copyright © 2012 Elsevier Ltd. All rights reserved.
Compton Gamma Ray Observatory: Lessons Learned in Propulsion
NASA Technical Reports Server (NTRS)
Dressler, G. A.; Joseph, G. W.; Behrens, H. W.; Asato, D. I.; Carlson, R. A.; Bauer, Frank H. (Technical Monitor)
2001-01-01
The Compton Gamma Ray Observatory was the second of NASA's Great Observatories. At 17 1/2 tons. it was the heaviest astrophysical payload ever flown at the time of its launch on April 5, 1991 aboard the Space Shuttle. During initial, on-orbit priming of the spacecraft's monopropellant hydrazine propulsion system, a severe waterhammer transient was experienced. At that time, anomalous telemetry readings were received from on-board propulsion system instrumentation. This led to ground analyses and laboratory investigations as to the root cause of the waterhammer, potential damage to system integrity and functionality, and risks for switching from the primary (A-side) propulsion system to the redundant (B-side) system. The switchover to B-side was ultimately performed successfully and the spacecraft completed its basic and extended missions in this configuration. Nine years later, following a critical control gyroscope failure, Compton was safely deorbited and re-entered the Earth's atmosphere on June 4, 2000. Additional risk assessments concerning viability of A- and B-sides were necessary to provide confidence in attitude and delta-V authority and reliability to manage the precisely controlled reentry. This paper summarizes the design and operation of the propulsion system used on the spacecraft and provides "lessons learned" from the system engineering investigations into the propellant loading procedures, the initial priming anomaly, mission operations, and the commanded re-entry following the gyro failure.
NASA Astrophysics Data System (ADS)
Garzoglio, Gabriele; Levshina, Tanya; Rynge, Mats; Sehgal, Chander; Slyz, Marko
2012-12-01
The Open Science Grid (OSG) supports a diverse community of new and existing users in adopting and making effective use of the Distributed High Throughput Computing (DHTC) model. The LHC user community has deep local support within the experiments. For other smaller communities and individual users the OSG provides consulting and technical services through the User Support area. We describe these sometimes successful and sometimes not so successful experiences and analyze lessons learned that are helping us improve our services. The services offered include forums to enable shared learning and mutual support, tutorials and documentation for new technology, and troubleshooting of problematic or systemic failure modes. For new communities and users, we bootstrap their use of the distributed high throughput computing technologies and resources available on the OSG by following a phased approach. We first adapt the application and run a small production campaign on a subset of “friendly” sites. Only then do we move the user to run full production campaigns across the many remote sites on the OSG, adding to the community resources up to hundreds of thousands of CPU hours per day. This scaling up generates new challenges - like no determinism in the time to job completion, and diverse errors due to the heterogeneity of the configurations and environments - so some attention is needed to get good results. We cover recent experiences with image simulation for the Large Synoptic Survey Telescope (LSST), small-file large volume data movement for the Dark Energy Survey (DES), civil engineering simulation with the Network for Earthquake Engineering Simulation (NEES), and accelerator modeling with the Electron Ion Collider group at BNL. We will categorize and analyze the use cases and describe how our processes are evolving based on lessons learned.
NASA Technical Reports Server (NTRS)
Fisher, Mark F.; King, Richard F.; Chenevert, Donald J.
1998-01-01
The need for low cost access to space has initiated the development of low cost liquid rocket engine and propulsion system hardware at the Marshall Space Flight Center. This hardware will be tested at the Stennis Space Center's B-2 test stand. This stand has been reactivated for the testing of the Marshall designed Fastrac engine and the Propulsion Test Article. The RP-1 and LOX engine is a turbopump fed gas generator rocket with an ablative nozzle which has a thrust of 60,000 lbf. The Propulsion Test Article (PTA) is a test bed for low cost propulsion system hardware including a composite RP-I tank, flight feedlines and pressurization system, stacked in a booster configuration. The PTA is located near the center line of the B-2 test stand, firing vertically into the water cooled flame deflector. A new second position on the B-2 test stand has been designed and built for the horizontal testing of the Fastrac engine in direct support of the X-34 launch vehicle. The design and integration of these test facilities as well as the coordination which was required between the two Centers is described and lessons learned are provided. The construction of the horizontal test position is discussed in detail. The activation of these facilities is examined and the major test milestones are described.
Certification Testing Approach for Propulsion System Design
NASA Technical Reports Server (NTRS)
Rodriguez, Henry; Popp, Chris
2005-01-01
The Certification of Propulsion Systems is costly and complex which involves development and qualification testing. The desire of the certification process is to assure all requirements can be demonstrated to be compliant. The purpose of this paper is to address the technical design concerns of certifying a system for flight. The authors of this paper have experience the lessons learned from supporting the Shuttle Program for Main Propulsion and On Orbit Propulsions Systems. They have collaborated design concerns for certifying propulsion systems. Presented are Pressurization, Tankage, Feed System and Combustion Instability concerns. Propulsion System Engineers are challenged with the dilemma for testing new systems to specific levels to reduce risk yet maintain budgetary targets. A methodical approach is presented to define the types of test suitable to address the technical issues for qualifying systems for retiring the risk levels.
Effectiveness of a Case-Based System in Lesson Planning
ERIC Educational Resources Information Center
Saad, A.; Chung, P. W. H.; Dawson, C. W.
2014-01-01
Lesson planning imposes a significant burden on teachers as they need to prepare different lesson plans for different classes according to various constraints. SmartLP, a case-based lesson planning system, has been implemented as a means of assisting teachers in constructing quality lesson plans more quickly. SmartLP enables teachers to retrieve…
Lesson 6: Using the Checklist to Work through System Requirements
Lesson 6 describes how these same requirements are presented in the CROMERR System Checklist (which was introduced in Lesson 4). You may want to refer to the checklist as you step through this lesson.
1999 NASA Seal/secondary Air System Workshop. Volume 1
NASA Technical Reports Server (NTRS)
Steinetz, Bruce M. (Editor); Hendricks, Robert C. (Editor)
2000-01-01
NASA Glenn hosted the Seals/Secondary Air System Workshop on October 28-29, 1999. Each year NASA and our industry and university partners share their respective seal technology development. We use these workshops as a technical forum to exchange recent advancements and "lessons-leamed" in advancing seal technology and solving problems of common interest. As in the past we are publishing two volumes. Volume 1 will be publicly available and volume 2 will be restricted under International Traffic and Arms Regulations (I.T.A.R.). The 1999 NASA Seal/Secondary Air System Workshop was divided into four areas; (i) overviews of the government-sponsored gas turbine programs (NASA Ultra Efficient Engine Technology program and DOE Advanced Turbine System program) and the general aviation program (GAP) with emphasis on program goals and seal needs; (ii) turbine engine seal issues from the perspective of an airline customer (i.e., United Airlines), (iii) sealing concepts, methods and results including experimental facilities and numerical predictions; and (iv) reviews of seal requirements for next generation aerospace vehicles (Trailblazer, Bantam and X-38).
Near Earth Asteroid Solar Sail Engineering Development Unit Test Program
NASA Technical Reports Server (NTRS)
Lockett, Tiffany Russell; Few, Alexander; Wilson, Richard
2017-01-01
The Near Earth Asteroid (NEA) Scout project is a 30x20x10cm (6U) cubesat reconnaissance mission to investigate a near Earth asteroid utilizing an 86m2 solar sail as the primary propulsion system. This will be the largest solar sail NASA will launch to date. NEA Scout is a secondary payload 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 furthered understanding of thermal, stress, and dynamics of the stowed system and matured an integrated sail membrane model for deployed flight dynamics. This paper will address design, fabrication, and lessons learned from the NEA Scout solar sail subsystem engineering development unit. From optical properties of the sail material to folding and spooling the single 86m2 sail, the team has developed a robust deployment system for the solar sail. This paper will also address expected and received test results from ascent vent, random vibration, and deployment tests.
NASA Technical Reports Server (NTRS)
Rowe, Sidney E.
2010-01-01
In September 2007, the Engineering Directorate at the Marshall Space Flight Center (MSFC) created the Design System Focus Team (DSFT). MSFC was responsible for the in-house design and development of the Ares 1 Upper Stage and the Engineering Directorate was preparing to deploy a new electronic Configuration Management and Data Management System with the Design Data Management System (DDMS) based upon a Commercial Off The Shelf (COTS) Product Data Management (PDM) System. The DSFT was to establish standardized CAD practices and a new data life cycle for design data. Of special interest here, the design teams were to implement Model Based Definition (MBD) in support of the Upper Stage manufacturing contract. It is noted that this MBD does use partially dimensioned drawings for auxiliary information to the model. The design data lifecycle implemented several new release states to be used prior to formal release that allowed the models to move through a flow of progressive maturity. The DSFT identified some 17 Lessons Learned as outcomes of the standards development, pathfinder deployments and initial application to the Upper Stage design completion. Some of the high value examples are reviewed.
STS Case Study Development Support
NASA Technical Reports Server (NTRS)
Rosa de Jesus, Dan A.; Johnson, Grace K.
2013-01-01
The Shuttle Case Study Collection (SCSC) has been developed using lessons learned documented by NASA engineers, analysts, and contractors. The SCSC provides educators with a new tool to teach real-world engineering processes with the goal of providing unique educational materials that enhance critical thinking, decision-making and problem-solving skills. During this third phase of the project, responsibilities included: the revision of the Hyper Text Markup Language (HTML) source code to ensure all pages follow World Wide Web Consortium (W3C) standards, and the addition and edition of website content, including text, documents, and images. Basic HTML knowledge was required, as was basic knowledge of photo editing software, and training to learn how to use NASA's Content Management System for website design. The outcome of this project was its release to the public.
REIMR: A Process for Utilizing Propulsion-Oriented 'Lessons-Learned' to Mitigate Development Risk
NASA Technical Reports Server (NTRS)
Ballard, Richard O.; Brown, Kendall K.
2005-01-01
This paper is a summary overview of a study conducted a t the NASA Marshall Space Flight Center (MSFC) during the initial phases of the Space Launch Initiative (SLI) program to evaluate a large number of technical problems associated with the design, development, test, evaluation and operation of several major liquid propellant rocket engine systems (i.e., SSME, Fastrac, J-2, F-1). The results of this study was the identification of the "Fundamental Root Causes" that enabled the technical problems to manifest, and practices that can be implemented to prevent them from recurring in future engine development efforts. This paper will discus the Fundamental Root Causes, cite some examples of how the technical problems arose from them, and provide a discussion of how they can be mitigated or avoided.
The J-2X Fuel Turbopump - Design, Development, and Test
NASA Technical Reports Server (NTRS)
Tellier, James G.; Hawkins, Lakiesha V.; Shinguchi, Brian H.; Marsh, Matthew W.
2011-01-01
Pratt and Whitney Rocketdyne (PWR), a NASA subcontractor, is executing the design, development, test, and evaluation (DDT&E) of a liquid oxygen, liquid hydrogen two hundred ninety four thousand pound thrust rocket engine initially intended for the Upper Stage (US) and Earth Departure Stage (EDS) of the Constellation Program Ares-I Crew Launch Vehicle (CLV). A key element of the design approach was to base the new J-2X engine on the heritage J-2S engine with the intent of uprating the engine and incorporating SSME and RS-68 lessons learned. The J-2S engine was a design upgrade of the flight proven J-2 configuration used to put American astronauts on the moon. The J-2S Fuel Turbopump (FTP) was the first Rocketdyne-designed liquid hydrogen centrifugal pump and provided many of the early lessons learned for the Space Shuttle Main Engine High Pressure Fuel Turbopumps. This paper will discuss the design trades and analyses performed for the current J-2X FTP to increase turbine life; increase structural margins, facilitate component fabrication; expedite turbopump assembly; and increase rotordynamic stability margins. Risk mitigation tests including inducer water tests, whirligig turbine blade tests, turbine air rig tests, and workhorse gas generator tests characterized operating environments, drove design modifications, or identified performance impact. Engineering design, fabrication, analysis, and assembly activities support FTP readiness for the first J-2X engine test scheduled for July 2011.
ERIC Educational Resources Information Center
Sánchez-Martín, Jesús; Álvarez-Gragera, García J.; Dávila-Acedo, M. Antonia; Mellado, Vicente
2017-01-01
The interest on engineering and scientific studies can be raised up even from the early years of academic instructional process. This vocation may be linked to emotions and aptitudes towards technological education. Particularly, students get in touch with these technological issues (namely STEM) during the Compulsory Secondary Education in Spain…
Managing External Relations: The Lifeblood of Mission Success
NASA Technical Reports Server (NTRS)
Dumbacher, Daniel L.
2007-01-01
The slide presentation examines the role of customer and stakeholder relations in the success of space missions. Topics include agency transformation; an overview of project and program experience with a discussion of positions, technical accomplishments, and management lessons learned; and approaches to project success with emphasis on communication. Projects and programs discussed include the Space Shuttle Main Engine System, DC-XA Flight Demonstrator, X-33 Flight Demonstrator, Space Launch Initiative/2nd Generation Reusable Launch Vehicle, X-37 Flight Demonstrator, Constellation (pre Dr. Griffin), Safety and Mission Assurance, and Exploration Launch Projects.
Basic Wind Tech Course - Lesson Plans and Activities
DOE Office of Scientific and Technical Information (OSTI.GOV)
Swapp, Andy
2011-07-01
The funds from this project were used to purchase tools and instrumentation to help replicate actual on-the-job wind energy scenarios which provided the students with the practical or applied components of wind energy jobs. This project enhanced the educational experiences provided for the students in terms of engineering and science components of wind energy by using electronics, control systems, and electro-mechanical instrumentation to help students learn standardized wind-specific craftsman skills. In addition the tools and instrumentation helped the students learn the safety necessary to work in the wind industry.
1993-04-15
Czyryca from the Naval Surface Warfare Center gave a Plenary Aodress on Lessons Learned in Metallurgical Failure Analyses of Naval Machinery. The...processing methods take many years to implement, because of the large capital investments and the learning process involved, we feel confident that they will...signals experienced by the self. Filters are an indistinguishable part of the self. As we learn about the causes of our failures, and see that we can
Re-Engineering the Mission Operations System (MOS) for the Prime and Extended Mission
NASA Technical Reports Server (NTRS)
Hunt, Joseph C., Jr.; Cheng, Leo Y.
2012-01-01
One of the most challenging tasks in a space science mission is designing the Mission Operations System (MOS). Whereas the focus of the project is getting the spacecraft built and tested for launch, the mission operations engineers must build a system to carry out the science objectives. The completed MOS design is then formally assessed in the many reviews. Once a mission has completed the reviews, the Mission Operation System (MOS) design has been validated to the Functional Requirements and is ready for operations. The design was built based on heritage processes, new technology, and lessons learned from past experience. Furthermore, our operational concepts must be properly mapped to the mission design and science objectives. However, during the course of implementing the science objective in the operations phase after launch, the MOS experiences an evolutional change to adapt for actual performance characteristics. This drives the re-engineering of the MOS, because the MOS includes the flight and ground segments. Using the Spitzer mission as an example we demonstrate how the MOS design evolved for both the prime and extended mission to enhance the overall efficiency for science return. In our re-engineering process, we ensured that no requirements were violated or mission objectives compromised. In most cases, optimized performance across the MOS, including gains in science return as well as savings in the budget profile was achieved. Finally, we suggest a need to better categorize the Operations Phase (Phase E) in the NASA Life-Cycle Phases of Formulation and Implementation
Current understanding of interactions between nanoparticles and the immune system
DOE Office of Scientific and Technical Information (OSTI.GOV)
Dobrovolskaia, Marina A., E-mail: marina@mail.nih.
2016-05-15
The delivery of drugs, antigens, and imaging agents benefits from using nanotechnology-based carriers. The successful translation of nanoformulations to the clinic involves thorough assessment of their safety profiles, which, among other end-points, includes evaluation of immunotoxicity. The past decade of research focusing on nanoparticle interaction with the immune system has been fruitful in terms of understanding the basics of nanoparticle immunocompatibility, developing a bioanalytical infrastructure to screen for nanoparticle-mediated immune reactions, beginning to uncover the mechanisms of nanoparticle immunotoxicity, and utilizing current knowledge about the structure–activity relationship between nanoparticles' physicochemical properties and their effects on the immune system to guidemore » safe drug delivery. In the present review, we focus on the most prominent pieces of the nanoparticle–immune system puzzle and discuss the achievements, disappointments, and lessons learned over the past 15 years of research on the immunotoxicity of engineered nanomaterials. - Graphical abstract: API — active pharmaceutical ingredient; NP — nanoparticles; PCP — physicochemical properties, CARPA — complement activation-related pseudoallergy, ICH — International Conference on Harmonization. Display Omitted - Highlights: • Achievements, disappointments and lessons learned over past decade are reviewed. • Areas in focus include characterization, immunotoxicity and utility in drug delivery. • Future direction focusing on mechanistic immunotoxicity studies is proposed.« less
NASA Space Mechanisms Handbook and Reference Guide Expanded Into CD-ROM Set
NASA Technical Reports Server (NTRS)
Fusaro, Robert L.
2002-01-01
Several NASA missions suffered failures and anomalies due to problems in applying space mechanisms technology to specific projects. Research shows that engineers often lack either adequate knowledge of mechanism design or sufficient understanding of how mechanisms affect sensitive systems. The Space Mechanisms Project conducted a Lessons Learned study and published a Space Mechanisms Handbook to help space industry engineers avoid recurring design, qualification, and application problems. The Space Mechanisms Handbook written at the NASA Glenn Research Center details the state-of-the-art in space mechanisms design as of 1998. NASA's objective in developing this Space Mechanisms Handbook was to provide readily accessible information on such areas as space mechanisms design, mechanical component availability and use, testing and qualification of mechanical systems, and a listing of worldwide space mechanisms experts and testing facilities in the United States. This handbook has been expanded into a two-volume CD-ROM set in an Adobe Acrobat format. In addition to the handbook, the CD's include (1) the two volume Space Mechanisms Lessons Learned Study, (2) proceedings from all the NASA hosted Aerospace Mechanisms Symposia held through the year 2000, (3) the Space Materials Handbook, (4) the Lubrication Handbook for the Space Industry, (5) the Structural & Mechanical Systems Long-Life Assurance Design Guidelines, (6) the Space Environments and Effects Source-Book, (7) the Spacecraft Deployable Appendages manual, (8) the Fastener Design Manual, (9) A Manual for Pyrotechnic Design, Development and Qualification, (10) the Report on Alternative Devices to Pyrotechnics on Spacecraft, and (11) Gearing (a manual). In addition, numerous other papers on tribology and lubrication are included.This technical summary of the project provides information on how to obtain the handbook and related information.
ERIC Educational Resources Information Center
Powell, Abigail; Dainty, Andrew; Bagilhole, Barbara
2012-01-01
In the UK, women remain under-represented in engineering and technology (E&T). Research has, therefore, investigated barriers and solutions to women's recruitment, retention and progression. Recruitment into the sector may be supported by exploring the career decisions of women and men who have chosen to study E&T. Triangulating…
Development and Experimental Validation of a Thermoelectric Test Bench for Laboratory Lessons
ERIC Educational Resources Information Center
Rodríguez García, Antonio; Astrain Ulibarrena, David; Martínez Echeverri, Álvaro; Aranguren Garacochea, Patricia; Pérez Artieda, Gurutze
2013-01-01
The refrigeration process reduces the temperature of a space or a given volume while the power generation process employs a source of thermal energy to generate electrical power. Because of the importance of these two processes, training of engineers in this area is of great interest. In engineering courses it is normally studied the vapor…
ERIC Educational Resources Information Center
Mississippi Research and Curriculum Unit for Vocational and Technical Education, State College.
This document, which reflects Mississippi's statutory requirement that instructional programs be based on core curricula and performance-based assessment, contains outlines of the instructional units required in local instructional management plans and daily lesson plans for diesel engine mechanics I and II. Presented first are a program…
Applying Peer Reviews in Software Engineering Education: An Experiment and Lessons Learned
ERIC Educational Resources Information Center
Garousi, V.
2010-01-01
Based on the demonstrated value of peer reviews in the engineering industry, numerous industry experts have listed it at the top of the list of desirable development practices. Experience has shown that problems (defects) are eliminated earlier if a development process incorporates peer reviews and that these reviews are as effective as or even…
Building Models to Better Understand the Importance of Cost versus Safety in Engineering
ERIC Educational Resources Information Center
Sumrall, William; Mott, Michael
2010-01-01
While some disasters involving engineered structures are due to events in nature (e.g., tornadoes, hurricanes, earthquakes), others may be caused by inadequate materials, design flaws, and poor maintenance. These catastrophes result in the loss of human lives and cost billions of dollars. In the set of lessons described here, students design a…
Teaching English for Science and Technology: An Approach for Reading with Engineering English
ERIC Educational Resources Information Center
Porcaro, James W.
2013-01-01
Recognizing the relevance of English for Specific Purposes, this article outlines an approach for using authentic readings in a course in Engineering English. The article describes the importance of needs analysis, rhetorical focus, and reading for content; it suggests content for 15 lessons and provides a sample worksheet and other suggestions…
Project Morpheus: Lessons Learned in Lander Technology Development
NASA Technical Reports Server (NTRS)
Olansen, Jon B.; Munday, Stephen R.; Mitchell, Jennifer D.
2013-01-01
NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing, that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. Designed, developed, manufactured and operated in-house by engineers at Johnson Space Center, the initial flight test campaign began on-site at JSC less than one year after project start. After two years of testing, including two major upgrade periods, and recovery from a test crash that caused the loss of a vehicle, flight testing will evolve to executing autonomous flights simulating a 500m lunar approach trajectory, hazard avoidance maneuvers, and precision landing, incorporating the Autonomous Landing and Hazard Avoidance (ALHAT) sensor suite. These free-flights are conducted at a simulated planetary landscape built at Kennedy Space Center's Shuttle Landing Facility. The Morpheus Project represents a departure from recent NASA programs and projects that traditionally require longer development lifecycles and testing at remote, dedicated testing facilities. This paper expands on the project perspective that technologies offer promise, but capabilities offer solutions. It documents the integrated testing campaign, the infrastructure and testing facilities, and the technologies being evaluated in this testbed. The paper also describes the fast pace of the project, rapid prototyping, frequent testing, and lessons learned during this departure from the traditional engineering development process at NASA's Johnson Space Center.
Using the Science Process Skills to Investigate Animals and Animal Habitats
NASA Astrophysics Data System (ADS)
Braithwaite, Saisha
This study explored how a STEM (science, technology, engineering, and math) engineer design challenge allowed students to analyze the characteristics of animals and animal habitats. This study was conducted in a kindergarten class within an urban school district. The class has 25 students while the study focuses on six students. The group consists of three boys and three girls. In this study, the students used the science process skills to observe, classify, infer, and make predictions about animals and habitats. In the engineer design, students created an established habitat and built their own animal that can survive in that habitat. The study analyzed how students used process skills to engage with the habitats and animals. The students successfully used the science process skills in this study. The results showed that students gained more content knowledge when they used multiple process skills within a lesson. The study shows that developing lessons using the science process skills improves students' ability to demonstrate their knowledge of animals and their habitats.
TARDEC's Intelligent Ground Systems overview
NASA Astrophysics Data System (ADS)
Jaster, Jeffrey F.
2009-05-01
The mission of the Intelligent Ground Systems (IGS) Area at the Tank Automotive Research, Development and Engineering Center (TARDEC) is to conduct technology maturation and integration to increase Soldier robot control/interface intuitiveness and robotic ground system robustness, functionality and overall system effectiveness for the Future Combat System Brigade Combat Team, Robotics Systems Joint Project Office and game changing capabilities to be fielded beyond the current force. This is accomplished through technology component development focused on increasing unmanned ground vehicle autonomy, optimizing crew interfaces and mission planners that capture commanders' intent, integrating payloads that provide 360 degree local situational awareness and expanding current UGV tactical behavior, learning and adaptation capabilities. The integration of these technology components into ground vehicle demonstrators permits engineering evaluation, User assessment and performance characterization in increasingly complex, dynamic and relevant environments to include high speed on road or cross country operations, all weather/visibility conditions and military operations in urban terrain (MOUT). Focused testing and experimentation is directed at reducing PM risk areas (safe operations, autonomous maneuver, manned-unmanned collaboration) and transitioning technology in the form of hardware, software algorithms, test and performance data, as well as User feedback and lessons learned.
NASA Technical Reports Server (NTRS)
Tavenner, Leslie A. (Editor)
1991-01-01
These proceedings overview major space information system projects and lessons learned from current missions. Other topics include the science information system requirements for the 1990s, an information systems design approach for major programs, the technology needs and projections, the standards for space data information systems, the artificial intelligence technology and applications, international interoperability, and spacecraft data systems and architectures advanced communications. Other topics include the software engineering technology and applications, the multimission multidiscipline information system architectures, the distributed planning and scheduling systems and operations, and the computer and information systems architectures. Paper presented include prospects for scientific data analysis systems for solar-terrestrial physics in the 1990s, the Columbus data management system, data storage technologies for the future, the German aerospace research establishment, and launching artificial intelligence in NASA ground systems.
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.
NASA Technical Reports Server (NTRS)
Giuliano, Victor J.; Leonard, Timothy G.; Lyda, Randy T.; Kim, Tony S.
2010-01-01
As one of the first technology development programs awarded by NASA under the Vision for Space Exploration, the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic engine supporting ongoing trade studies for NASA s Lunar Lander descent stage. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the PWR RL10, to develop technology and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in a high-energy cryogenic engine. The testbed selected for the deep throttling demonstration phases of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. Three series of demonstrator engine tests, the first in April-May 2006, the second in March-April 2007 and the third in November-December 2008, have demonstrated up to 13:1 throttling (104% to 8% thrust range) of the hydrogen/oxygen expander cycle engine. The first two test series explored a propellant feed system instability ("chug") environment at low throttled power levels. Lessons learned from these two tests were successfully applied to the third test series, resulting in stable operation throughout the 13:1 throttling range. The first three tests have provided an early demonstration of an enabling cryogenic propulsion concept, accumulating over 5,000 seconds of hot fire time over 27 hot fire tests, and have provided invaluable system-level technology data toward design and development risk mitigation for the NASA Altair and future lander propulsion system applications. This paper describes the results obtained from the highly successful third test series as well as the test objectives and early results obtained from a fourth test series conducted over March-May 2010
NASA Astrophysics Data System (ADS)
Mejías Borrero, A.; Andújar Márquez, J. M.
2012-10-01
Lab practices are an essential part of teaching in Engineering. However, traditional laboratory lessons developed in classroom labs (CL) must be adapted to teaching and learning strategies that go far beyond the common concept of e-learning, in the sense that completely virtualized distance education disconnects teachers and students from the real world, which can generate specific problems in laboratory classes. Current proposals of virtual labs (VL) and remote labs (RL) do not either cover new needs properly or contribute remarkable improvement to traditional labs—except that they favor distance training. Therefore, online teaching and learning in lab practices demand a further step beyond current VL and RL. This paper poses a new reality and new teaching/learning concepts in the field of lab practices in engineering. The developed augmented reality-based lab system (augmented remote lab, ARL) enables teachers and students to work remotely (Internet/intranet) in current CL, including virtual elements which interact with real ones. An educational experience was conducted to assess the developed ARL with the participation of a group of 10 teachers and another group of 20 students. Both groups have completed lab practices of the contents in the subjects Digital Systems and Robotics and Industrial Automation, which belong to the second year of the new degree in Electronic Engineering (adapted to the European Space for Higher Education). The labs were carried out by means of three different possibilities: CL, VL and ARL. After completion, both groups were asked to fill in some questionnaires aimed at measuring the improvement contributed by ARL relative to CL and VL. Except in some specific questions, the opinion of teachers and students was rather similar and positive regarding the use and possibilities of ARL. Although the results are still preliminary and need further study, seems to conclude that ARL remarkably improves the possibilities of current VL and RL. Furthermore, ARL can be concluded to allow further possibilities when used online than traditional laboratory lessons completed in CL.
Interactive Educational Tool for Turbofan and Afterburning Turbojet Engines
NASA Technical Reports Server (NTRS)
Benson, Thomas J.
1997-01-01
A workstation-based, interactive educational computer program has been developed at the NASA Lewis Research Center to aid in the teaching and understanding of turbine engine design and analysis. This tool has recently been extended to model the performance of two-spool turbofans and afterburning turbojets. The program solves for the flow conditions through the engine by using classical one-dimensional thermodynamic analysis found in various propulsion textbooks. Either an approximately thermally perfect or calorically perfect gas can be used in the thermodynamic analysis. Students can vary the design conditions through a graphical user interface; engine performance is calculated immediately. A variety of graphical formats are used to present results, including numerical results, moving bar charts, and student-generated temperature versus entropy (Ts), pressure versus specific volume (pv), and engine performance plots. The package includes user-controlled printed output, restart capability, online help screens, and a browser that displays teacher-prepared lessons in turbomachinery. The program runs on a variety of workstations or a personal computer using the UNIX operating system and X-based graphics. It is being tested at several universities in the midwestern United States; the source and executables are available free from the author.
HPC in a HEP lab: lessons learned from setting up cost-effective HPC clusters
NASA Astrophysics Data System (ADS)
Husejko, Michal; Agtzidis, Ioannis; Baehler, Pierre; Dul, Tadeusz; Evans, John; Himyr, Nils; Meinhard, Helge
2015-12-01
In this paper we present our findings gathered during the evaluation and testing of Windows Server High-Performance Computing (Windows HPC) in view of potentially using it as a production HPC system for engineering applications. The Windows HPC package, an extension of Microsofts Windows Server product, provides all essential interfaces, utilities and management functionality for creating, operating and monitoring a Windows-based HPC cluster infrastructure. The evaluation and test phase was focused on verifying the functionalities of Windows HPC, its performance, support of commercial tools and the integration with the users work environment. We describe constraints imposed by the way the CERN Data Centre is operated, licensing for engineering tools and scalability and behaviour of the HPC engineering applications used at CERN. We will present an initial set of requirements, which were created based on the above constraints and requests from the CERN engineering user community. We will explain how we have configured Windows HPC clusters to provide job scheduling functionalities required to support the CERN engineering user community, quality of service, user- and project-based priorities, and fair access to limited resources. Finally, we will present several performance tests we carried out to verify Windows HPC performance and scalability.
Ares Knowledge Capture: Summary and Key Themes Presentation
NASA Technical Reports Server (NTRS)
Coates, Ralph H.
2011-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 MSFC Chief Engineers Office. 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.
Infusing Software Engineering Technology into Practice at NASA
NASA Technical Reports Server (NTRS)
Pressburger, Thomas; Feather, Martin S.; Hinchey, Michael; Markosia, Lawrence
2006-01-01
We present an ongoing effort of the NASA Software Engineering Initiative to encourage the use of advanced software engineering technology on NASA projects. Technology infusion is in general a difficult process yet this effort seems to have found a modest approach that is successful for some types of technologies. We outline the process and describe the experience of the technology infusions that occurred over a two year period. We also present some lessons from the experiences.
An SSME high pressure oxidizer turbopump diagnostic system using G2(TM) real-time expert system
NASA Technical Reports Server (NTRS)
Guo, Ten-Huei
1991-01-01
An expert system which diagnoses various seal leakage faults in the High Pressure Oxidizer Turbopump of the SSME was developed using G2(TM) real-time expert system. Three major functions of the software were implemented: model-based data generation, real-time expert system reasoning, and real-time input/output communication. This system is proposed as one module of a complete diagnostic system for Space Shuttle Main Engine. Diagnosis of a fault is defined as the determination of its type, severity, and likelihood. Since fault diagnosis is often accomplished through the use of heuristic human knowledge, an expert system based approach was adopted as a paradigm to develop this diagnostic system. To implement this approach, a software shell which can be easily programmed to emulate the human decision process, the G2 Real-Time Expert System, was selected. Lessons learned from this implementation are discussed.
Teaching Engineering Practices
NASA Astrophysics Data System (ADS)
Cunningham, Christine M.; Carlsen, William S.
2014-03-01
Engineering is featured prominently in the Next Generation Science Standards (NGSS) and related reform documents, but how its nature and methods are described is problematic. This paper is a systematic review and critique of that representation, and proposes that the disciplinary core ideas of engineering (as described in the NGSS) can be disregarded safely if the practices of engineering are better articulated and modeled through student engagement in engineering projects. A clearer distinction between science and engineering practices is outlined, and prior research is described that suggests that precollege engineering design can strengthen children's understandings about scientific concepts. However, a piecemeal approach to teaching engineering practices is unlikely to result in students understanding engineering as a discipline. The implications for science teacher education are supplemented with lessons learned from a number of engineering education professional development projects.
NASA Technical Reports Server (NTRS)
Mandl, Dan; Howard, Joseph
2000-01-01
The New Millennium Program's first Earth-observing mission (EO-1) is a technology validation mission. It is managed by the NASA Goddard Space Flight Center in Greenbelt, Maryland and is scheduled for launch in the summer of 2000. The purpose of this mission is to flight-validate revolutionary technologies that will contribute to the reduction of cost and increase of capabilities for future land imaging missions. In the EO-1 mission, there are five instrument, five spacecraft, and three supporting technologies to flight-validate during a year of operations. EO-1 operations and the accompanying ground system were intended to be simple in order to maintain low operational costs. For purposes of formulating operations, it was initially modeled as a small science mission. However, it quickly evolved into a more complex mission due to the difficulties in effectively integrating all of the validation plans of the individual technologies. As a consequence, more operational support was required to confidently complete the on-orbit validation of the new technologies. This paper will outline the issues and lessons learned applicable to future technology validation missions. Examples of some of these include the following: (1) operational complexity encountered in integrating all of the validation plans into a coherent operational plan, (2) initial desire to run single shift operations subsequently growing to 6 "around-the-clock" operations, (3) managing changes in the technologies that ultimately affected operations, (4) necessity for better team communications within the project to offset the effects of change on the Ground System Developers, Operations Engineers, Integration and Test Engineers, S/C Subsystem Engineers, and Scientists, and (5) the need for a more experienced Flight Operations Team to achieve the necessary operational flexibility. The discussion will conclude by providing several cost comparisons for developing operations from previous missions to EO-1 and discuss some details that might be done differently for future technology validation missions.
Improved CPAS Photogrammetric Capabilities for Engineering Development Unit (EDU) Testing
NASA Technical Reports Server (NTRS)
Ray, Eric S.; Bretz, David R.
2013-01-01
This paper focuses on two key improvements to the photogrammetric analysis capabilities of the Capsule Parachute Assembly System (CPAS) for the Orion vehicle. The Engineering Development Unit (EDU) system deploys Drogue and Pilot parachutes via mortar, where an important metric is the muzzle velocity. This can be estimated using a high speed camera pointed along the mortar trajectory. The distance to the camera is computed from the apparent size of features of known dimension. This method was validated with a ground test and compares favorably with simulations. The second major photogrammetric product is measuring the geometry of the Main parachute cluster during steady-state descent using onboard cameras. This is challenging as the current test vehicles are suspended by a single-point attachment unlike earlier stable platforms suspended under a confluence fitting. The mathematical modeling of fly-out angles and projected areas has undergone significant revision. As the test program continues, several lessons were learned about optimizing the camera usage, installation, and settings to obtain the highest quality imagery possible.
Designing Innovative Lessons Plans to Support the Next Generation Science Standards (NGSS)
NASA Astrophysics Data System (ADS)
Passow, M. J.
2013-12-01
The Next Generation Science Standards (NGSS) issued earlier in 2013 provide the opportunity to enhance pre-college curricula through a new focus on the ';Big Ideas' in Science, more attention to reading and writing skills needed for college and career readiness, and incorporation of engineering and technology. We introduce a set of lesson plans about scientific ocean drilling which can serve as a exemplars for developing curricula to meet NGSS approaches. Designed for middle and high school students, these can also be utilized in undergraduate courses. Development of these lessons was supported through a grant from the Deep Earth Academy of the Consortium for Ocean Leadership. They will be disseminated through websites of the Deep Earth Academy (http://www.oceanleadership.org/education/deep-earth-academy/) and Earth2Class Workshops for Teachers (http://www.earth2class.org), as well as through workshops at science education conferences sponsored by the National Earth Science Teachers Association (www.nestanet.org) and other organizations. Topics include 'Downhole Logging,' 'Age of the Ocean Floors,' 'Tales of the Resolution,' and 'Continental Shelf Sediments and Climate Change Patterns.' 'Downhole Logging' focuses on the engineering and technology utilized to obtain more information about sediments and rocks cored by the JOIDES Resolution scientific drilling vessel. 'Age of the Ocean Floor' incorporates the GeoMap App visualization tools (http://www.geomapapp.org/) to compare sea bottom materials in various parts of the world. 'Tales of the Resolution' is a series of ';graphic novels' created to describe the scientific discoveries, refitting of the JOIDES Resolution, and variety of careers available in the marine sciences (http://www.ldeo.columbia.edu/BRG/outreach/media/tales/). The fourth lesson focuses on discoveries made during Integrated Ocean Drilling Program Expedition 313, which investigated patterns in the sediments beneath the continental shelf off New Jersey with respect to climate changes. The lesson plans include examples of addressing new demands to incorporate more English Language Arts and Math Common Core Standards, engineering design, and cutting-edge scientific investigations.
ERIC Educational Resources Information Center
Bianco, Andrew S.
2014-01-01
All technology educators have favorite lessons and projects that they most desire to teach. Many teachers might ask why teach robotics when there are many other concepts to cover with the students? The answer to this question is to engage students in science, technology, engineering, and math (commonly referred to as STEM) concepts. In order for…
ERIC Educational Resources Information Center
Jones, Enid B., Ed.
Background papers and recommendations from the American Association of Community Colleges' (AACC's) 1992 roundtable on issues facing minority students in mathematics, science, and engineering (MSE) education are presented. The first paper, "Community College Networks," by Wm. Carroll Marsalis and Glenna A. Mosby, describes the Tennessee Valley…
DOE Office of Scientific and Technical Information (OSTI.GOV)
Ma, S.; Yin, H.; Kline, D. M.
2006-08-01
This paper describes a joint effort of the Institute for Electrical Engineering of the Chinese Academy of Sciences (IEE), and the U.S. National Renewable Energy Laboratory (NREL) to support China's rural electrification program. This project developed a design tool that provides guidelines both for off-grid renewable energy system designs and for cost-based tariff and finance schemes to support them. This tool was developed to capitalize on lessons learned from the Township Electrification Program that preceded the Village Electrification Program. We describe the methods used to develop the analysis, some indicative results, and the planned use of the tool in themore » Village Electrification Program.« less
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
LDRD Final Report: Global Optimization for Engineering Science Problems
DOE Office of Scientific and Technical Information (OSTI.GOV)
HART,WILLIAM E.
1999-12-01
For a wide variety of scientific and engineering problems the desired solution corresponds to an optimal set of objective function parameters, where the objective function measures a solution's quality. The main goal of the LDRD ''Global Optimization for Engineering Science Problems'' was the development of new robust and efficient optimization algorithms that can be used to find globally optimal solutions to complex optimization problems. This SAND report summarizes the technical accomplishments of this LDRD, discusses lessons learned and describes open research issues.
Writing a success story: lessons learned from the Spitzer Space Telescope
NASA Astrophysics Data System (ADS)
Gehrz, R. D.; Roellig, T. L.; Werner, M. W.
2010-08-01
A key to the success of the Spitzer Space Telescope (formerly SIRTF) Mission was a unique management structure that promoted open communication and collaboration among scientific, engineering, and contractor personnel at all levels of the project. This helped us to recruit and maintain the very best people to work on Spitzer. We describe the management concept that led to the success of the mission. Specific examples of how the project benefited from the communication and reporting structure, and lessons learned about technology are described.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Borland, M.; Hettel, R.; Leemann, S. C.
With the recent success in commissioning of MAX IV, the multi-bend achromat (MBA) lattice has begun to deliver on its promise to usher in a new generation of higher-brightness synchrotron light sources. In this paper, we begin by reviewing the challenges, recent success, and lessons learned of the MAX-IV project. Drawing on these lessons, we then describe the physics challenges in even more ambitious rings and how these can be met. In addition, we touch on engineering issues and choices that are tightly linked with the physics design.
Space Shuttle GN and C Development History and Evolution
NASA Technical Reports Server (NTRS)
Zimpfer, Douglas; Hattis, Phil; Ruppert, John; Gavert, Don
2011-01-01
Completion of the final Space Shuttle flight marks the end of a significant era in Human Spaceflight. Developed in the 1970 s, first launched in 1981, the Space Shuttle embodies many significant engineering achievements. One of these is the development and operation of the first extensive fly-by-wire human space transportation Guidance, Navigation and Control (GN&C) System. Development of the Space Shuttle GN&C represented first time inclusions of modern techniques for electronics, software, algorithms, systems and management in a complex system. Numerous technical design trades and lessons learned continue to drive current vehicle development. For example, the Space Shuttle GN&C system incorporated redundant systems, complex algorithms and flight software rigorously verified through integrated vehicle simulations and avionics integration testing techniques. Over the past thirty years, the Shuttle GN&C continued to go through a series of upgrades to improve safety, performance and to enable the complex flight operations required for assembly of the international space station. Upgrades to the GN&C ranged from the addition of nose wheel steering to modifications that extend capabilities to control of the large flexible configurations while being docked to the Space Station. This paper provides a history of the development and evolution of the Space Shuttle GN&C system. Emphasis is placed on key architecture decisions, design trades and the lessons learned for future complex space transportation system developments. Finally, some of the interesting flight operations experience is provided to inform future developers of flight experiences.
Best Practices for Reliable and Robust Spacecraft Structures
NASA Technical Reports Server (NTRS)
Raju, Ivatury S.; Murthy, P. L. N.; Patel, Naresh R.; Bonacuse, Peter J.; Elliott, Kenny B.; Gordon, S. A.; Gyekenyesi, J. P.; Daso, E. O.; Aggarwal, P.; Tillman, R. F.
2007-01-01
A study was undertaken to capture the best practices for the development of reliable and robust spacecraft structures for NASA s next generation cargo and crewed launch vehicles. In this study, the NASA heritage programs such as Mercury, Gemini, Apollo, and the Space Shuttle program were examined. A series of lessons learned during the NASA and DoD heritage programs are captured. The processes that "make the right structural system" are examined along with the processes to "make the structural system right". The impact of technology advancements in materials and analysis and testing methods on reliability and robustness of spacecraft structures is studied. The best practices and lessons learned are extracted from these studies. Since the first human space flight, the best practices for reliable and robust spacecraft structures appear to be well established, understood, and articulated by each generation of designers and engineers. However, these best practices apparently have not always been followed. When the best practices are ignored or short cuts are taken, risks accumulate, and reliability suffers. Thus program managers need to be vigilant of circumstances and situations that tend to violate best practices. Adherence to the best practices may help develop spacecraft systems with high reliability and robustness against certain anomalies and unforeseen events.
Potential Nano-Enabled Environmental Applications for Radionuclides
This document provides information about nanotechnology materials and processes that may be applicable when cleaning up radioactively contaminated sites or materials, and presents a snapshot of lessons learned in nano-science and engineering.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Nai-Yang, S.
The Chinese National Standard for Emission from Vehicles was published in 1983. The most important one is Emission Standards for Pollutants at Idle Speed from Road Vehicles with Petrol Engines. This paper discusses experiences gained and lessons learned since publication.
Creating a Bio-Inspired Solution to Prevent Erosion
NASA Astrophysics Data System (ADS)
Reher, R.; Martinez, A.; Cola, J.; Frost, D.
2016-12-01
Through the study of geophysical sciences, lessons can be developed which allow for the introduction of bio-inspired design and art concepts to K-5 elementary students. Students are placed into an engineering mindset in which they must apply the concepts of bio-geotechnics to observe how we can use nature to prevent and abate erosion. Problems are staged for students using realistic engineering scenarios such as erosion prevention through biomimicry and the study of anchorage characteristics of root structures in regard to stability of soil. Specifically, a lesson is introduced where students research, learn, and present information about bio-inspired designs to understand these concepts. They lean how plant roots differ in size and shape to stabilize soil. In addition, students perform a series of hands-on experiments which demonstrate how bio-cements and roots can slow erosion.
Lessons Learned about Liquid Metal Reactors from FFTF Experience
DOE Office of Scientific and Technical Information (OSTI.GOV)
Wootan, David W.; Casella, Andrew M.; Omberg, Ronald P.
2016-09-20
The Fast Flux Test Facility (FFTF) is the most recent liquid-metal reactor (LMR) to operate in the United States, from 1982 to 1992. FFTF is located on the DOE Hanford Site near Richland, Washington. The 400-MWt sodium-cooled, low-pressure, high-temperature, fast-neutron flux, nuclear fission test reactor was designed specifically to irradiate Liquid Metal Fast Breeder Reactor (LMFBR) fuel and components in prototypical temperature and flux conditions. FFTF played a key role in LMFBR development and testing activities. The reactor provided extensive capability for in-core irradiation testing, including eight core positions that could be used with independent instrumentation for the test specimens.more » In addition to irradiation testing capabilities, FFTF provided long-term testing and evaluation of plant components and systems for LMFBRs. The FFTF was highly successful and demonstrated outstanding performance during its nearly 10 years of operation. The technology employed in designing and constructing this reactor, as well as information obtained from tests conducted during its operation, can significantly influence the development of new advanced reactor designs in the areas of plant system and component design, component fabrication, fuel design and performance, prototype testing, site construction, and reactor operations. The FFTF complex included the reactor, as well as equipment and structures for heat removal, containment, core component handling and examination, instrumentation and control, and for supplying utilities and other essential services. The FFTF Plant was designed using a “system” concept. All drawings, specifications and other engineering documentation were organized by these systems. Efforts have been made to preserve important lessons learned during the nearly 10 years of reactor operation. A brief summary of Lessons Learned in the following areas will be discussed: Acceptance and Startup Testing of FFTF FFTF Cycle Reports« less
Importance of Engineering History Education
NASA Astrophysics Data System (ADS)
Arakawa, Fumio
It is needless to cite the importance of education for succeed of engineering. IEEJ called for the establishment of ICEE in 1994, where the education is thought highly of, though its discussion has not been well working. Generally speaking, education has been one of the most important national strategies particularly at a time of its political and economical development. The science and technology education is, of course, not the exemption. But in these days around 2000 it seems that the public pays little attention on the science and technology, as they are quite day to day matters. As the results, for instance, such engineering as power systems and electric heavy machines are referred to as “endangered”. So fur, many engineers have tried not to be involved in social issues. But currently they can not help facing with risks of social issues like patent rights, troubles and accidents due to application of high technology, information security in the use of computers and engineering ethics. One of the most appropriate ways for the risk management is to learn lessons in the past, that is, history, so that the idea suggested in it could be made full use for the risk management. The author cited the global importance of education, particularly of engineering history education for engineering ethics, in the ICEE 2010 held in Bussan, Korea, as the 16th anniversary.
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
Implementation of a production Ada project: The GRODY study
NASA Technical Reports Server (NTRS)
Godfrey, Sara; Brophy, Carolyn Elizabeth
1989-01-01
The use of the Ada language and design methodologies that encourage full use of its capabilities have a strong impact on all phases of the software development project life cycle. At the National Aeronautics and Space Administration/Goddard Space Flight Center (NASA/GSFC), the Software Engineering Laboratory (SEL) conducted an experiment in parallel development of two flight dynamics systems in FORTRAN and Ada. The differences observed during the implementation, unit testing, and integration phases of the two projects are described and the lessons learned during the implementation phase of the Ada development are outlined. Included are recommendations for future Ada development projects.
Putting the “Spark” into Physical Science and Algebra
NASA Astrophysics Data System (ADS)
Dagenais, Andre; Pill, B.
2006-12-01
The presenters will describe a number of laboratory activities developed in collaboration with the Department of Electrical Engineering at the University of Delaware as part of their outreach program to help make math and science more authentic on the pre-college level. Lessons relating to electrical topics are often abstract and appropriate only for advanced students in math and science. We have devised lessons that rely on simple equipment. They promote skills that are included in National and State Standards. They emphasize the connections between math and science; they are appropriate for an algebra course, a physical science course, a PhysicsFirst course or a traditional physics course. Students benefit from seeing that what they learn in math and science courses can lead to cutting-edge work in areas such as passive wave imaging, photonics, wireless communication and high performance computing. The collaboration has been meaningful because it has motivated us to tailor our lessons to reflect what is happening in the research lab of our local university. Written materials for use in teacher training workshops will also be available. Funded by NSF Research Experience for Teachers(RET #0322633) program under the direction of Dr. Dennis Prather, University of Delaware Electrical Engineering
X-34 Main Propulsion System Design and Operation
NASA Technical Reports Server (NTRS)
Champion, R. J., Jr.; Darrow, R. J., Jr.
1998-01-01
The X-34 program is a joint industry/government program to develop, test, and operate a small, fully-reusable hypersonic flight vehicle, utilizing technologies and operating concepts applicable to future Reusable Launch Vehicle (RLV) systems. The vehicle will be capable of Mach 8 flight to 250,000 feet altitude and will demonstrate an all composite structure, composite RP-1 tank, the Marshall Space Flight Center (MSFC) developed Fastrac engine, and the operability of an advanced thermal protection systems. The vehicle will also be capable of carrying flight experiments. MSFC is supporting the X-34 program in three ways: Program Management, the Fastrac engine as Government Furnished Equipment (GFE), and the design of the Main Propulsion System (MPS). The MPS Product Development Team (PDT) at MSFC is responsible for supplying the MPS design, analysis, and drawings to Orbital. The MPS consists of the LOX and RP-1 Fill, Drain, Feed, Vent, & Dump systems and the Helium & Nitrogen Purge, Pressurization, and Pneumatics systems. The Reaction Control System (RCS) design was done by Orbital. Orbital is the prime contractor and has responsibility for integration, procurement, and construction of all subsystems. The paper also discusses the design, operation, management, requirements, trades studies, schedule, and lessons learning with the MPS and RCS designs.
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.
ERIC Educational Resources Information Center
Borrero, A. Mejias; Marquez, J. M. Andujar
2012-01-01
Lab practices are an essential part of teaching in Engineering. However, traditional laboratory lessons developed in classroom labs (CL) must be adapted to teaching and learning strategies that go far beyond the common concept of e-learning, in the sense that completely virtualized distance education disconnects teachers and students from the real…
ERIC Educational Resources Information Center
Rothberg, S. J.; Lamb, F. M.; Willis, L.
2006-01-01
This paper gives a synopsis of an extensive programme of case studies on real uses of computer-assisted learning (CAL) materials within UK engineering degree programmes. The programme was conducted between 2000 and 2003 and followed a questionnaire-based survey looking at CAL use in the UK and in Australia. The synopsis reveals a number of key…
Milestones in Software Engineering and Knowledge Engineering History: A Comparative Review
del Águila, Isabel M.; Palma, José; Túnez, Samuel
2014-01-01
We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because “those who cannot remember the past are condemned to repeat it.” This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one. PMID:24624046
Milestones in software engineering and knowledge engineering history: a comparative review.
del Águila, Isabel M; Palma, José; Túnez, Samuel
2014-01-01
We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because "those who cannot remember the past are condemned to repeat it." This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one.
NASA Astrophysics Data System (ADS)
Daniel, J. C.; Hogue, T. S.; Moldwin, M. B.; Nonacs, P.
2012-12-01
A National Science Foundation Graduate Teaching Fellows in K- 12 Education program at UCLA (SEE-LA; http://measure.igpp.ucla.edu/GK12-SEE-LA/ ) partners UCLA faculty and graduate students (fellows) with urban middle and high school science teachers and their students to foster programs of science and engineering exploration that bring the environment of Los Angeles into the classroom. UCLA science and engineering graduate fellows serve as scientists-in-residence at four partner schools to integrate inquiry-based science lessons, facilitate advancements in science content teaching, and ultimately, to improve their own science communication skills. As part of their fellowship, graduate students are required to develop three "major" lessons, including one based on their PhD research at UCLA. During the first four years of the project, the SEE-LA fellows have developed a range of research-based activities, including lessons on sustainable fisheries, ecosystems and remote sensing, earthquakes, urban water quality including invertebrate observations, and post-fire soil chemistry, among others. This presentation will provide an overview of the SEE-LA GK-12 program and development of research lessons that also address California State Science Standards. We also discuss potential sustainability of GK-12 type outreach and education programs. The SEE-LA program has provided development of graduate student communication and teaching skills while also contributing significantly to the integration of science education into K-12 curriculum in Los Angeles schools.
Lessons Learned from Engineering a Multi-Mission Satellite Operations Center
NASA Technical Reports Server (NTRS)
Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David
2006-01-01
NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.
Evolution of the IBDM Structural Latch Development into a Generic Simplified Design
NASA Technical Reports Server (NTRS)
DeVriendt, K.; Dittmer, H.; Vrancken, D.; Urmston, P.; Gracia, O.
2010-01-01
This paper presents the evolution in the development of the structural latch for the International Berthing Docking Mechanism (IBDM, see Figure 1). It reports on the lessons learned since completion of the test program on the engineering development unit of the first generation latching system in 2007. The initial latch design has been through a second generation concept in 2008, and now evolved into a third generation of this mechanism. Functional and structural testing on the latest latch hardware has recently been completed with good results. The IBDM latching system will provide the structural connection between two mated space vehicles after berthing or docking. The mechanism guarantees that the interface seals become compressed to form a leak-tight pressure system that creates a passageway for the astronauts.
NASA Astrophysics Data System (ADS)
Butcher, G. J.; Roberts-Harris, D.
2013-12-01
A set of innovative classroom lessons were developed based on informal learning activities in the 'Sensors, Circuits, and Satellites' kit manufactured by littleBits™ Electronics that are designed to lead students through a logical science content storyline about energy using sound and light and fully implements an integrated approach to the three dimensions of the Next Generation of Science Standards (NGSS). This session will illustrate the integration of NGSS into curriculum by deconstructing lesson design to parse out the unique elements of the 3 dimensions of NGSS. We will demonstrate ways in which we have incorporated the NGSS as we believe they were intended. According to the NGSS, 'The real innovation in the NGSS is the requirement that students are required to operate at the intersection of practice, content, and connection. Performance expectations are the right way to integrate the three dimensions. It provides specificity for educators, but it also sets the tone for how science instruction should look in classrooms. (p. 3). The 'Sensors, Circuits, and Satellites' series of lessons accomplishes this by going beyond just focusing on the conceptual knowledge (the disciplinary core ideas) - traditionally approached by mapping lessons to standards. These lessons incorporate the other 2 dimensions -cross-cutting concepts and the 8-practices of Sciences and Engineering-via an authentic and exciting connection to NASA science, thus implementing the NGSS in the way they were designed to be used: practices and content with the crosscutting concepts. When the NGSS are properly integrated, students are engaged in science and engineering content through the coupling of practice, content and connection. In the past, these two dimensions have been separated as distinct entities. We know now that coupling content and practices better demonstrates what goes on in real world science and engineering. We set out to accomplish what is called for in NGSS by integrating these three dimensions to 'provide students with a context for the content of science, how science knowledge is acquired and understood, and how the sciences are connected through concepts that have universal meaning across the disciplines,' which include connections to authentic NASA science (NGSS, pg.2). The NASA context is embedded in the lessons and designed to interest students in Earth and space science. Research suggests that personal interest, experience, and enthusiasm--critical to children's learning of science at school or in other settings-- may also be linked to later educational and career choices. (Framework for K-12 Science Education: Practices, Cross-cutting concepts, Core ideas, p. 28) Students are encouraged to follow their interests, through additional online resources, real world NASA applications, and career connections offering insight to course offerings and possible majors. Combined with the innovative electronic component kit manufactured by littleBits™ Electronics, students are excited and engaged in authentic science and engineering. Sample circuit used in the Sensors, Circuits, and Satellites kit.
ERIC Educational Resources Information Center
Brock, Phyllis; And Others
This interdisciplinary instructional unit contains eleven lessons for grades 10-12 which focus on the energy component of food production. There are lessons which contrast food production systems in various cultures and also lessons which look at different systems and techniques in use in this country. There are lessons dealing with organic…
Professional Learning through the Collaborative Design of Problem-Solving Lessons
ERIC Educational Resources Information Center
Wake, Geoff; Swan, Malcolm; Foster, Colin
2016-01-01
This article analyses lesson study as a mode of professional learning, focused on the development of mathematical problem solving processes, using the lens of cultural-historical activity theory. In particular, we draw attention to two activity systems, the classroom system and the lesson-study system, and the importance of making artefacts…
A Study of Technical Engineering Peer Reviews at NASA
NASA Technical Reports Server (NTRS)
Chao, Lawrence P.; Tumer, Irem Y.; Bell, David G.
2003-01-01
This report describes the state of practices of design reviews at NASA and research into what can be done to improve peer review practices. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review and Critical Design Review are a required part of every project and mission development. However, the technical, engineering peer reviews that support teams' work on such projects are informal, some times ad hoc, and inconsistent across the organization. The goal of this work is to identify best practices and lessons learned from NASA's experience, supported by academic research and methodologies to ultimately improve the process. This research has determined that the organization, composition, scope, and approach of the reviews impact their success. Failure Modes and Effects Analysis (FMEA) can identify key areas of concern before or in the reviews. Product definition tools like the Project Priority Matrix, engineering-focused Customer Value Chain Analysis (CVCA), and project or system-based Quality Function Deployment (QFD) help prioritize resources in reviews. The use of information technology and structured design methodologies can strengthen the engineering peer review process to help NASA work towards error-proofing the design process.
CRISPR Genome Engineering for Human Pluripotent Stem Cell Research
Chaterji, Somali; Ahn, Eun Hyun; Kim, Deok-Ho
2017-01-01
The emergence of targeted and efficient genome editing technologies, such as repurposed bacterial programmable nucleases (e.g., CRISPR-Cas systems), has abetted the development of cell engineering approaches. Lessons learned from the development of RNA-interference (RNA-i) therapies can spur the translation of genome editing, such as those enabling the translation of human pluripotent stem cell engineering. In this review, we discuss the opportunities and the challenges of repurposing bacterial nucleases for genome editing, while appreciating their roles, primarily at the epigenomic granularity. First, we discuss the evolution of high-precision, genome editing technologies, highlighting CRISPR-Cas9. They exist in the form of programmable nucleases, engineered with sequence-specific localizing domains, and with the ability to revolutionize human stem cell technologies through precision targeting with greater on-target activities. Next, we highlight the major challenges that need to be met prior to bench-to-bedside translation, often learning from the path-to-clinic of complementary technologies, such as RNA-i. Finally, we suggest potential bioinformatics developments and CRISPR delivery vehicles that can be deployed to circumvent some of the challenges confronting genome editing technologies en route to the clinic. PMID:29158838
NASA Technical Reports Server (NTRS)
Liebowitz, Jay
1986-01-01
At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.
RAID-2: Design and implementation of a large scale disk array controller
NASA Technical Reports Server (NTRS)
Katz, R. H.; Chen, P. M.; Drapeau, A. L.; Lee, E. K.; Lutz, K.; Miller, E. L.; Seshan, S.; Patterson, D. A.
1992-01-01
We describe the implementation of a large scale disk array controller and subsystem incorporating over 100 high performance 3.5 inch disk drives. It is designed to provide 40 MB/s sustained performance and 40 GB capacity in three 19 inch racks. The array controller forms an integral part of a file server that attaches to a Gb/s local area network. The controller implements a high bandwidth interconnect between an interleaved memory, an XOR calculation engine, the network interface (HIPPI), and the disk interfaces (SCSI). The system is now functionally operational, and we are tuning its performance. We review the design decisions, history, and lessons learned from this three year university implementation effort to construct a truly large scale system assembly.
Achievements and challenges of Space Station Freedom's safety review process
NASA Technical Reports Server (NTRS)
Robinson, David W.
1993-01-01
The most complex space vehicle in history, Space Station Freedom, is well underway to completion, and System Safety is a vital part of the program. The purpose is to summarize and illustrate the progress that over one-hundred System Safety engineers have made in identifying, documenting, and controlling the hazards inherent in the space station. To date, Space Station Freedom has been reviewed by NASA's safety panels through the first six assembly flights, when Freedom achieves a configuration known as Man Tended Capability. During the eight weeks of safety reviews spread out over a year and a half, over 200 preliminary hazard reports were presented. Along the way NASA and its contractors faced many challenges, made much progress, and even learned a few lessons.
Active cooling from the sixties to NASP
NASA Technical Reports Server (NTRS)
Kelly, H. Neale; Blosser, Max L.
1992-01-01
Vehicles, such as the X-15 or National Aero-Space Plane, traveling at hypersonic speeds through the earth's atmosphere experience aerodynamic heating. The heating can be severe enough that a thermal protection system is required to limit the temperature of the vehicle structure. Although several categories of thermal protection systems are mentioned briefly, the majority of this paper describes convectively cooled structures for large areas. Convective cooling is a method of limiting structural temperatures by circulating a coolant through the vehicle structure. Efforts to develop convectively cooled structures during the past 30 years--from early engine structures, which were intended to be tested on the X-15, to structural--are described. Many of the lessons learned from these research efforts are presented.
Achievements and challenges of Space Station Freedom's safety review process
NASA Astrophysics Data System (ADS)
Robinson, David W.
1993-07-01
The most complex space vehicle in history, Space Station Freedom, is well underway to completion, and System Safety is a vital part of the program. The purpose is to summarize and illustrate the progress that over one-hundred System Safety engineers have made in identifying, documenting, and controlling the hazards inherent in the space station. To date, Space Station Freedom has been reviewed by NASA's safety panels through the first six assembly flights, when Freedom achieves a configuration known as Man Tended Capability. During the eight weeks of safety reviews spread out over a year and a half, over 200 preliminary hazard reports were presented. Along the way NASA and its contractors faced many challenges, made much progress, and even learned a few lessons.
An application of computer aided requirements analysis to a real time deep space system
NASA Technical Reports Server (NTRS)
Farny, A. M.; Morris, R. V.; Hartsough, C.; Callender, E. D.; Teichroew, D.; Chikofsky, E.
1981-01-01
The entire procedure of incorporating the requirements and goals of a space flight project into integrated, time ordered sequences of spacecraft commands, is called the uplink process. The Uplink Process Control Task (UPCT) was created to examine the uplink process and determine ways to improve it. The Problem Statement Language/Problem Statement Analyzer (PSL/PSA) designed to assist the designer/analyst/engineer in the preparation of specifications of an information system is used as a supporting tool to aid in the analysis. Attention is given to a definition of the uplink process, the definition of PSL/PSA, the construction of a PSA database, the value of analysis to the study of the uplink process, and the PSL/PSA lessons learned.
Lessons Learned During Implementation and Early Operations of the DS1 Beacon Monitor Experiment
NASA Technical Reports Server (NTRS)
Sherwood, Rob; Wyatt, Jay; Hotz, Henry; Schlutsmeyer, Alan; Sue, Miles
1998-01-01
A new approach to mission operations will be flight validated on NASA's New Millennium Program Deep Space One (DS1) mission which launched in October 1998. The Beacon Monitor Operations Technology is aimed at decreasing the total volume of downlinked engineering telemetry by reducing the frequency of downlink and the volume of data received per pass. Cost savings are achieved by reducing the amount of routine telemetry processing and analysis performed by ground staff. The technology is required for upcoming NASA missions to Pluto, Europa, and possibly some other missions. With beacon monitoring, the spacecraft will assess its own health and will transmit one of four beacon messages each representing a unique frequency tone to inform the ground how urgent it is to track the spacecraft for telemetry. If all conditions are nominal, the tone provides periodic assurance to ground personnel that the mission is proceeding as planned without having to receive and analyze downlinked telemetry. If there is a problem, the tone will indicate that tracking is required and the resulting telemetry will contain a concise summary of what has occurred since the last telemetry pass. The primary components of the technology are a tone monitoring technology, AI-based software for onboard engineering data summarization, and a ground response system. In addition, there is a ground visualization system for telemetry summaries. This paper includes a description of the Beacon monitor concept, the trade-offs with adapting that concept as a technology experiment, the current state of the resulting implementation on DS1, and our lessons learned during the initial checkout phase of the mission. Applicability to future missions is also included.
Communications Middleware for Tactical Environments: Observations, Experiences, and Lessons Learned
2009-12-12
posi- tion at the Engineering Department of the University of Ferrara , Italy . His research interests include distributed and mobile computing, QoS...science engineering from the Uni- versity of Padova, Italy , in 2005. She continued her studies at the University of Ferrara , where she gained a Master’s...Stefanelli, University of Ferrara Jesse Kovach, U.S. Army Research Laboratory James Hanna, U.S. Air Force Research Laboratory Communications Middleware
Implementing CDIO project-based learning in training of Heat and Power engineers
NASA Astrophysics Data System (ADS)
Boiko, E. A.; Shishmarev, P. V.; Karabarin, D. I.; Yanov, S. R.; Pikalova, A. A.
2017-11-01
This paper presents the experience and current results of CDIO standards implementation in training of bachelors in Heat and Power Engineering at Thermal Power Stations academic department in Siberian Federal University. It provides information on methodology of modernization of educational programs, curricula and programs of disciplines in transition to CDIO project-based learning technology. Preliminary assessment and analysis of lessons learned and scaling perspectives are given.
Operational Problems Associated with Head-Up Displays during Instrument Flight.
1980-10-01
Force project engineers were Major Michael F. Rundle and Mr. William L. Welde . 41 4 TABLE OF CONTENTS Page ABBREVIATIONS...of Automotive Engineers SETP Society of Experimental Test Pilots SI Solid Instruments SNPL Syndicat National des Pilotes des Lignes (French ALPA) TACAN...Factors Relevent to Jet Upsets ," Lessons with Emphasis on Flight Mechanics from Operating Experience, Incidents, and Accidents, AGARD CP-76, 1971 153 J
ERIC Educational Resources Information Center
O'Connell, Daniel W.
This lesson describes the current government of Hungary and its underlying political and electoral systems. The lesson is structured with: (1) background on the parliamentary model of government, political parties, and Hungary's unique electoral system; (2) a summary of the six major political parties in Hungary and voter information for the 1990…
Yoo, Terry S; Ackerman, Michael J; Lorensen, William E; Schroeder, Will; Chalana, Vikram; Aylward, Stephen; Metaxas, Dimitris; Whitaker, Ross
2002-01-01
We present the detailed planning and execution of the Insight Toolkit (ITK), an application programmers interface (API) for the segmentation and registration of medical image data. This public resource has been developed through the NLM Visible Human Project, and is in beta test as an open-source software offering under cost-free licensing. The toolkit concentrates on 3D medical data segmentation and registration algorithms, multimodal and multiresolution capabilities, and portable platform independent support for Windows, Linux/Unix systems. This toolkit was built using current practices in software engineering. Specifically, we embraced the concept of generic programming during the development of these tools, working extensively with C++ templates and the freedom and flexibility they allow. Software development tools for distributed consortium-based code development have been created and are also publicly available. We discuss our assumptions, design decisions, and some lessons learned.
NASA Technical Reports Server (NTRS)
Johnson, Dale L.; Keller, Vernon W.; Vaughan, William W.
2005-01-01
The description and interpretation of the terrestrial environment (0-90 km altitude) is an important driver of aerospace vehicle structural, control, and thermal system design. NASA is currently in the process of reviewing the meteorological information acquired over the past decade and producing an update to the 1993 Terrestrial Environment Guidelines for Aerospace Vehicle Design and Development handbook. This paper addresses the contents of this updated handbook, with special emphasis on new material being included in the areas of atmospheric thermodynamic models, wind dynamics, atmospheric composition, atmospheric electricity, cloud phenomena, atmospheric extremes, sea state, etc. In addition, the respective engineering design elements will be discussed relative to the importance and influence of terrestrial environment inputs that require consideration and interpretation for design applications. Specific lessons learned that have contributed to the advancements made in the acquisition, interpretation, application and awareness of terrestrial environment inputs for aerospace engineering applications are discussed.
Assess/Mitigate Risk through the Use of Computer-Aided Software Engineering (CASE) Tools
NASA Technical Reports Server (NTRS)
Aguilar, Michael L.
2013-01-01
The NASA Engineering and Safety Center (NESC) was requested to perform an independent assessment of the mitigation of the Constellation Program (CxP) Risk 4421 through the use of computer-aided software engineering (CASE) tools. With the cancellation of the CxP, the assessment goals were modified to capture lessons learned and best practices in the use of CASE tools. The assessment goal was to prepare the next program for the use of these CASE tools. The outcome of the assessment is contained in this document.
The History of Orbiter Corrosion Control (1981 - 2011)
NASA Technical Reports Server (NTRS)
Russell, Richard W.
2014-01-01
After 135 missions and 30 years the Orbiter fleet was retired in 2011. Working with Orbiter project management and a world class engineering team the CCRB was successful in providing successful sustaining engineering support for approximately 20 years. Lessons learned from the Orbiter program have aided NASA and contractor engineers in the design and manufacture of new spacecraft so that exploration of space can continue. The Orbiters are proudly being displayed for all the public to see in New York City, Washington D.C., Los Angeles, and at the Kennedy Space Center in Florida.
Tissue Engineering in Orthopaedics
Tatara, Alexander M.; Mikos, Antonios G.
2016-01-01
➤ It is important to carefully select the most appropriate combination of scaffold, signals, and cell types when designing tissue engineering approaches for an orthopaedic pathology. ➤ Although clinical studies in which the tissue engineering paradigm has been applied in the treatment of orthopaedic diseases are limited in number, examining them can yield important lessons. ➤ While there is a rapid rate of new discoveries in the basic sciences, substantial regulatory, economic, and clinical issues must be overcome with more consistency to translate a greater number of technologies from the laboratory to the operating room. PMID:27385687
MARGINS mini-lessons: A tour of the Mariana Subduction System (Invited)
NASA Astrophysics Data System (ADS)
Goodliffe, A. M.; Oakley, A.
2009-12-01
MARGINS mini-lessons provide an efficient way to quickly move cutting edge MARGINS research into the university classroom. Instructors who are not necessarily familiar with the MARGINS program can easily use mini-lessons in a variety of educational settings. The mini-lesson described herein is centered on bathymetric and multi-channel seismic data collected during a 2003 NSF-MARGINS funded marine geophysical survey in the Mariana Basin. Designed as an approximately sixty minute lecture segment, the lesson covers both the techniques used to collect marine geophysical data and a description of the geology of the system. All geological provinces are included, from the subducting Pacific Plate in the east to the remnant arc in the west. Representative seismic lines and bathymetric images are presented for each province, along with a description of key processes including deformation of the subducting plate, serpentinite mud volcanism, forearc faulting, potentially tsunamigenic landslides, arc volcanism, and backarc spreading. The Mariana subduction system mini-lesson requires a computer with an internet connection, powerpoint, Google Earth, and a web-browser. Questions are embedded in the powerpoint presentation that can be adapted to a specific interactive response system as needed. Optimally the lesson should be used in parallel with a GeoWall. A 3-dimensional ArcScene visualization of the Mariana system is available for download through the MARGINS mini-lessons web site. Such visualizations are particularly effective in helping students understand complex three-dimensional systems. If presented in a computer lab students will benefit from being able to explore the Mariana system using tools such as GeoMapApp.
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.
NASA Technical Reports Server (NTRS)
Carr, Daniel; Ellenberger, Rich
2008-01-01
The Human Factors Implementation Team (HFIT) process has been used to verify human factors requirements for NASA International Space Station (ISS) payloads since 2003, resulting in $2.4 million in avoided costs. This cost benefit has been realized by greatly reducing the need to process time-consuming formal waivers (exceptions) for individual requirements violations. The HFIT team, which includes astronauts and their technical staff, acts as the single source for human factors requirements integration of payloads. HFIT has the authority to provide inputs during early design phases, thus eliminating many potential requirements violations in a cost-effective manner. In those instances where it is not economically or technically feasible to meet the precise metric of a given requirement, HFIT can work with the payload engineers to develop common sense solutions and formally document that the resulting payload design does not materially affect the astronaut s ability to operate and interact with the payload. The HFIT process is fully ISO 9000 compliant and works concurrently with NASA s formal systems engineering work flow. Due to its success with payloads, the HFIT process is being adapted and extended to ISS systems hardware. Key aspects of this process are also being considered for NASA's Space Shuttle replacement, the Crew Exploration Vehicle.
Magellan attitude control mission operations
NASA Technical Reports Server (NTRS)
Dukes, Eileen M.
1993-01-01
From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.
NASA Astrophysics Data System (ADS)
Nawroth, Janna; Lee, Hyungsuk; Feinberg, Adam; Ripplinger, Crystal; McCain, Megan; Grosberg, Anna; Dabiri, John; Parker, Kit
2012-11-01
Tissue-engineered devices promise to advance medical implants, aquatic robots and experimental platforms for tissue-fluid interactions. The design, fabrication and systematic improvement of tissue constructs, however, is challenging because of the complex interactions of living cell, synthetic materials and their fluid environments. In a proof of concept study we have tissue-engineered a construct that mimics the swimming of a juvenile jellyfish, a simple model system for muscle-powered pumps at intermediate Reynolds numbers with quantifiable fluid dynamics and morphological properties. Optimally designed constructs achieved jellyfish-like swimming and generated biomimetic propulsion and feeding currents. Focusing on the fluid interactions, we discuss failed and successful designs and the lessons learned in the process. The main challenges were (1) to derive a body shape and deformation suitable for effective fluid transport under physiological fluid conditions, (2) to understand the mechanical properties of muscle and bell matrix and device a design capable of the desired deformation, (3) to establish adequate 3D kinematics of power and recovery stroke, and (4) to evaluate the performance of the design.
Magellan attitude control mission operations
NASA Astrophysics Data System (ADS)
Dukes, Eileen M.
From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.
NASA Technical Reports Server (NTRS)
Fayssal, Safie; Weldon, Danny
2008-01-01
The United States National Aeronautics and Space Administration (NASA) is in the midst of a space exploration program called Constellation to send crew and cargo to the international Space Station, to the moon, and beyond. As part of the Constellation program, a new launch vehicle, Ares I, is being developed by NASA Marshall Space Flight Center. Designing a launch vehicle with high reliability and increased safety requires a significant effort in understanding design variability and design uncertainty at the various levels of the design (system, element, subsystem, component, etc.) and throughout the various design phases (conceptual, preliminary design, etc.). In a previous paper [1] we discussed a probabilistic functional failure analysis approach intended mainly to support system requirements definition, system design, and element design during the early design phases. This paper provides an overview of the application of probabilistic engineering methods to support the detailed subsystem/component design and development as part of the "Design for Reliability and Safety" approach for the new Ares I Launch Vehicle. Specifically, the paper discusses probabilistic engineering design analysis cases that had major impact on the design and manufacturing of the Space Shuttle hardware. The cases represent important lessons learned from the Space Shuttle Program and clearly demonstrate the significance of probabilistic engineering analysis in better understanding design deficiencies and identifying potential design improvement for Ares I. The paper also discusses the probabilistic functional failure analysis approach applied during the early design phases of Ares I and the forward plans for probabilistic design analysis in the detailed design and development phases.
Photovoltaic balance-of-system designs and costs at PVUSA
NASA Astrophysics Data System (ADS)
Reyes, A. B.; Jennings, C.
1995-05-01
This report is one in a series of 1994-1995 PVUSA reports that document PVUSA lessons learned at demonstration sites in California and Texas. During the last 7 years (1988 to 1994), 16 PV systems ranging from 20 kW to 500 kW have been installed. Six 20-kW emerging module technology (EMT) arrays and three turnkey (i.e., vendor designed and integrated) utility-scale systems were procured and installed at PVUSA's main test site in Davis, California. PVUSA host utilities have installed a total of seven EMT arrays and utility-scale systems in their service areas. Additional systems at Davis and host utility sites are planned. One of PVUSA's key objectives is to evaluate the performance, reliability, and cost of PV balance-of-system (BOS). In the procurement stage PVUSA encouraged innovative design to improve upon present practice by reducing maintenance, improving reliability, or lowering manufacturing or construction costs. The project team worked closely with suppliers during the design stage not only to ensure designs met functional and safety specifications, but to provide suggestions for improvement. This report, intended for the photovoltaic (PV) industry and for utility project managers and engineers considering PV plant construction and ownership, documents PVUSA utility-scale system design and cost lessons learned. Complementary PVUSA topical reports document: construction and safety experience; five-year assessment of EMTs; validation of the Kerman 500-kW grid-support PV plant benefits; PVUSA instrumentation and data analysis techniques; procurement, acceptance, and rating practices for PV power plants; experience with power conditioning units and power quality.
A Model-Based Expert System for Space Power Distribution Diagnostics
NASA Technical Reports Server (NTRS)
Quinn, Todd M.; Schlegelmilch, Richard F.
1994-01-01
When engineers diagnose system failures, they often use models to confirm system operation. This concept has produced a class of advanced expert systems that perform model-based diagnosis. A model-based diagnostic expert system for the Space Station Freedom electrical power distribution test bed is currently being developed at the NASA Lewis Research Center. The objective of this expert system is to autonomously detect and isolate electrical fault conditions. Marple, a software package developed at TRW, provides a model-based environment utilizing constraint suspension. Originally, constraint suspension techniques were developed for digital systems. However, Marple provides the mechanisms for applying this approach to analog systems such as the test bed, as well. The expert system was developed using Marple and Lucid Common Lisp running on a Sun Sparc-2 workstation. The Marple modeling environment has proved to be a useful tool for investigating the various aspects of model-based diagnostics. This report describes work completed to date and lessons learned while employing model-based diagnostics using constraint suspension within an analog system.
Lessons Learned Study Final Report for the Exploration Systems Mission Directorate
NASA Technical Reports Server (NTRS)
Van Laak, Jim; Brumfield, M. Larry; Moore, Arlene A.; Anderson, Brooke; Dempsey, Jim; Gifford, Bob; Holloway, Chip; Johnson, Keith
2004-01-01
This report is the final product of a 90-day study performed for the Exploration Systems Mission Directorate. The study was to assemble lessons NASA has learned from previous programs that could help the Exploration Systems Mission Directorate pursue the Exploration vision. It focuses on those lessons that should have the greatest significance to the Directorate during the formulation of program and mission plans. The study team reviewed a large number of lessons learned reports and data bases, including the Columbia Accident Investigation Board and Rogers Commission reports on the Shuttle accidents, accident reports from robotic space flight systems, and a number of management reviews by the Defense Sciences Board, Government Accountability Office, and others. The consistency of the lessons, findings, and recommendations validate the adequacy of the data set. In addition to reviewing existing databases, a series of workshops was held at each of the NASA centers and headquarters that included senior managers from the current workforce as well as retirees. The full text of the workshop reports is included in Appendix A. A lessons learned website was opened up to permit current and retired NASA personnel and on-site contractors to input additional lessons as they arise. These new lessons, when of appropriate quality and relevance, will be brought to the attention of managers. The report consists of four parts: Part 1 provides a small set of lessons, called the Executive Lessons Learned, that represent critical lessons that the Exploration Systems Mission Directorate should act on immediately. This set of Executive Lessons and their supporting rationale have been reviewed at length and fully endorsed by a team of distinguished NASA alumni; Part 2 contains a larger set of lessons, called the Selected Lessons Learned, which have been chosen from the lessons database and center workshop reports on the basis of their specific significance and relevance to the near-term work of the Exploration Directorate. These lessons frequently support the Executive lessons but are more general in nature; Part 3 consists of the reports of the center workshops that were conducted as part of this activity. These reports are included in their entirety (approximately 200 pages) in Appendix G and have significance for specific managers; Part 4 consists of the remainder of the lessons that have been selected by this effort and assembled into a database for the use of the Explorations Directorate. The database is archived and hosted in the Lessons Learned Knowledge Network, which provides a flexible search capability using a wide variety of search terms. Finally, a spreadsheet lists databases searched and a bibliography identifies reports that have been reviewed as sources of lessons for this task. NASA has been presented with many learning opportunities. We have conducted numerous programs, some extremely successful and others total failures. Most have been documented with a formal lessons learned activity, but we have not always incorporated these learning opportunities into our normal modes of business. For example, the Robbins Report of 2001 clearly indicates that many project failures of the past two decades were the result of violating well documented best practices, often in direct violation of management instructions and directives. An overarching lesson emerges: that disciplined execution in accordance with proven best practices is the greatest single contributor to a successful program. The Lessons Learned task team offers a sincere hope that the lessons presented herein will be helpful to the Exploration Systems Directorate in charting and executing their course. The success of the Directorate and of NASA in general depends on our collective ability to move forward without having to relearn the lessons of those who have gone before.
Federal Register 2010, 2011, 2012, 2013, 2014
2013-11-04
... photographs for (Science, Technology, Engineering, and Mathematics) STEM educational purposes. The gathered materials would be used to create lesson plans about Antarctic Exploration that focus on science, technology...
Optical development system lab alignment solutions for the ICESat-2 ATLAS instrument
NASA Astrophysics Data System (ADS)
Evans, T.
The ATLAS Instrument for the ICESat-2 mission at NASA's Goddard Space Flight Center requires an alignment test-bed to prove out new concepts. The Optical Development System (ODS) lab was created to test prototype models of individual instrument components to simulate how they will act as a system. The main ICESat-2 instrument is the Advanced Topographic Laser Altimeter System (ATLAS). It measures ice elevation by transmitting laser pulses, and collecting the reflection in a telescope. Because the round trip time is used to calculate distance, alignment between the outgoing transmitter beam and the incoming receiver beams are critical. An automated closed loop monitoring control system is currently being tested at the prototype level to prove out implementation for the final spacecraft. To achieve an error of less than 2 micro-radians, an active deformable mirror was used to correct the lab wave front from the collimated “ ground reflection” beam. The lab includes a focal plane assembly set up, a one meter diameter collimator optic, and a 0.8 meter flight spare telescope for alignment. ATLAS prototypes and engineering models of transmitter and receiver optics and sub-systems are brought in to develop and integrate systems as well as write procedures to be used in integration and testing. By having a fully integrated system with prototypes and engineering units, lessons can be learned before flight designs are finalized.
Design Process of Flight Vehicle Structures for a Common Bulkhead and an MPCV Spacecraft Adapter
NASA Technical Reports Server (NTRS)
Aggarwal, Pravin; Hull, Patrick V.
2015-01-01
Design and manufacturing space flight vehicle structures is a skillset that has grown considerably at NASA during that last several years. Beginning with the Ares program and followed by the Space Launch System (SLS); in-house designs were produced for both the Upper Stage and the SLS Multipurpose crew vehicle (MPCV) spacecraft adapter. Specifically, critical design review (CDR) level analysis and flight production drawing were produced for the above mentioned hardware. In particular, the experience of this in-house design work led to increased manufacturing infrastructure for both Marshal Space Flight Center (MSFC) and Michoud Assembly Facility (MAF), improved skillsets in both analysis and design, and hands on experience in building and testing (MSA) full scale hardware. The hardware design and development processes from initiation to CDR and finally flight; resulted in many challenges and experiences that produced valuable lessons. This paper builds on these experiences of NASA in recent years on designing and fabricating flight hardware and examines the design/development processes used, as well as the challenges and lessons learned, i.e. from the initial design, loads estimation and mass constraints to structural optimization/affordability to release of production drawing to hardware manufacturing. While there are many documented design processes which a design engineer can follow, these unique experiences can offer insight into designing hardware in current program environments and present solutions to many of the challenges experienced by the engineering team.
Human Factors in the Design of the Crew Exploration Vehicle (CEV)
NASA Technical Reports Server (NTRS)
Whitmore, Mihriban; Byrne, Vicky; Holden, Kritina
2007-01-01
NASA s Space Exploration vision for humans to venture to the moon and beyond provides interesting human factors opportunities and challenges. The Human Engineering group at NASA has been involved in the initial phases of development of the Crew Exploration Vehicle (CEV), Orion. Getting involved at the ground level, Human Factors engineers are beginning to influence design; this involvement is expected to continue throughout the development lifecycle. The information presented here describes what has been done to date, what is currently going on, and what is expected in the future. During Phase 1, prior to the contract award to Lockheed Martin, the Human Engineering group was involved in generating requirements, conducting preliminary task analyses based on interviews with subject matter experts in all vehicle systems areas, and developing preliminary concepts of operations based on the task analysis results. In addition, some early evaluations to look at CEV net habitable volume were also conducted. The program is currently in Phase 2, which is broken down into design cycles, including System Readiness Review, Preliminary Design Review, and Critical Design Review. Currently, there are ongoing Human Engineering Technical Interchange Meetings being held with both NASA and Lockheed Martin in order to establish processes, desired products, and schedules. Multiple design trades and quick-look evaluations (e.g. display device layout and external window size) are also in progress. Future Human Engineering activities include requirement verification assessments and crew/stakeholder evaluations of increasing fidelity. During actual flights of the CEV, the Human Engineering group is expected to be involved in in-situ testing and lessons learned reporting, in order to benefit human space flight beyond the initial CEV program.
Principles to Products: Toward Realizing MOS 2.0
NASA Technical Reports Server (NTRS)
Bindschadler, Duane L.; Delp, Christopher L.
2012-01-01
This is a report on the Operations Revitalization Initiative, part of the ongoing NASA-funded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element...) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.
Selected Lessons Learned in Space Shuttle Orbiter Propulsion and Power Subsystems
NASA Technical Reports Server (NTRS)
Hernandez, Francisco J.; Martinez, Hugo; Ryan, Abigail; Westover, Shayne; Davies, Frank
2011-01-01
Over its 30 years of space flight history, plus the nearly 10 years of design, development test and evaluation, the Space Shuttle Orbiter is full of lessons learned in all of its numerous and complex subsystems. In the current paper, only selected lessons learned in the areas of the Orbiter propulsion and power subsystems will be described. The particular Orbiter subsystems include: Auxiliary Power Unit (APU), Hydraulics and Water Spray Boiler (WSB), Mechanical Flight Controls, Main Propulsion System (MPS), Fuel Cells and Power Reactant and Storage Devices (PRSD), Orbital Maneuvering System (OMS), Reaction Control System (RCS), Electrical Power Distribution (EPDC), electrical wiring and pyrotechnics. Given the complexity and extensive history of each of these subsystems, and the limited scope of this paper, it is impossible to include most of the lessons learned; instead the attempt will be to present a selected few or key lessons, in the judgment of the authors. Each subsystem is presented separate, beginning with an overview of the hardware and their function, a short description of a few historical problems and their lessons, followed by a more comprehensive table listing of the major subsystem problems and lessons. These tables serve as a quick reference for lessons learned in each subsystem. In addition, this paper will establish common lessons across subsystems as well as concentrate on those lessons which are deemed to have the highest applicability to future space flight programs.
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.
Ares I Crew Launch Vehicle Upper Stage/Upper Stage Engine Element Overview
NASA Technical Reports Server (NTRS)
McArthur, J. Craig
2008-01-01
The Ares I upper stage is an integral part of the Constellation Program transportation system. The upper stage provides guidance, navigation and control (GN and C) for the second stage of ascent flight for the Ares I vehicle. The Saturn-derived J-2X upper stage engine will provide thrust and propulsive impulse for the second stage of ascent flight for the Ares I launch vehicle. Additionally, the upper stage is responsible for the avionics system of the the entire Ares I. This brief presentation highlights the requirements, design, progress and production of the upper stage. Additionally, test facilities to support J-2X development are discussed and an overview of the operational and manufacturing flows are provided. Building on the heritage of the Apollo and Space Shuttle Programs, the Ares I Us and USE teams are utilizing extensive lessons learned to place NASA and the US into another era of space exploration. The NASA, Boeing and PWR teams are integrated and working together to make progress designing and building the Ares I upper stage to minimize cost, technical and schedule risks.
ERIC Educational Resources Information Center
Edwards, Susan
2011-01-01
This paper examines Vygotsky's conception of play as a leading activity in the contexts of children's contemporary play worlds. Commencing with an examination of the relationship between leading activities and the development of psychological functions, the paper moves into a consideration of the relationship between imagination and reality as a…
Process Tailoring and the Software Capability Maturity Model(sm).
1995-11-01
A Discipline For Software Engineering, Addison-Wesley, 1995; Humphrey . This book summarizes the costs and benefits of a Personal Software Process ( PSP ...1994. [Humphrey95] Humphrey , Watts S . A Discipline For Software Engineering. Reading, MA: Addison-Wesley Publishing Company, 1995. CMUISEI-94-TR-24 43...practiced and institutionalized. 8 CMU/SEI-94-TR-24 . Leveraging mo n o s I cDocument" IRevise & Analyze Organizational LessonsApproach ’"- Define Processes
Mentoring Undergraduate Students through the Space Shuttle Hitchhiker GoldHELOX Project
NASA Astrophysics Data System (ADS)
Moody, J. Ward; Barnes, Jonathan; Roming, Peter; Durfee, Dallin; Campbell, Branton; Turley, Steve; Eastman, Paul
2015-01-01
In the late 1980s a team of four BYU undergraduate students designed a space-based telescope to image the sun in soft x-rays from 171-181 Angstroms to gain information on microflares and their relation to the corona-chromosphere transition region. The telescope used a near-normal incidence multi-layered mirror imaging onto film through a micro-channel plate. The system was capable of 1.0 sec time resolution and 2.5 arcsec spatial resolution. Aided by a NASA grant in 1991, a system was built and successfully tested in 1998 at Marshall Space Flight Center. Originally designed to be deployed from a Get-Away-Special (GAS) canister in the bay of a space shuttle, the good results of this test elevated GoldHelox to greater-priority Hitchhiker status. Even so technical and procedural difficulties delayed a launch until after 2003. Unfortunately after the Columbia re-entry break-up in February 2003, the Hitchhiker program was cancelled and the GoldHelox project ended.Well over 200 undergraduate students worked on GoldHelox. Many of these have since earned advanced degrees in a variety of technical fields. Several have gone on to work in the space industry, becoming NASA scientists and engineers with one becoming a PI on the Swift satellite. The broad range of talent on the team has included students majoring in physics, astronomy, mechanical engineering, electrical engineering, manufacturing engineering, design engineering, business and even English majors who have written technical and public relations documents. We report on lessons learned and the pitfalls and successes of this unique mentoring experience.
Developing Distributed Collaboration Systems at NASA: A Report from the Field
NASA Technical Reports Server (NTRS)
Becerra-Fernandez, Irma; Stewart, Helen; Knight, Chris; Norvig, Peter (Technical Monitor)
2001-01-01
Web-based collaborative systems have assumed a pivotal role in the information systems development arena. While business to customers (B-to-C) and business to business (B-to-B) electronic commerce systems, search engines, and chat sites are the focus of attention, web-based systems span the gamut of information systems that were traditionally confined to internal organizational client server networks. For example, the Domino Application Server allows Lotus Notes (trademarked) uses to build collaborative intranet applications and mySAP.com (trademarked) enables web portals and e-commerce applications for SAP users. This paper presents the experiences in the development of one such system: Postdoc, a government off-the-shelf web-based collaborative environment. Issues related to the design of web-based collaborative information systems, including lessons learned from the development and deployment of the system as well as measured performance, are presented in this paper. Finally, the limitations of the implementation approach as well as future plans are presented as well.
Computer-Based Instruction Authoring Tools System (CATS): Lesson Maintenance
1990-07-01
Tols-System ( CATS ): Lesson Maintenance Vol N. Hutton Michael R. Flaningam Barbara Tarker Ann Rybowlak Susan Sulzbach Mark Lyon Brian Thomason DTC"",~1...Authoring Tools &ystem ( CATS ): Lesson Maintenance Vel N. Hulton Michael R. Flaningam Barbara Tarker Ann Rybowiak Navy Personnel Research and...lools •ystem ( CATS ): Program Element 0604722A Lesson Maintenance 6. AUTHOR(S) V. N. Huhoa, N. R. Fl1ingam. B. Tarktr, A. Rybowiak. S. Sulzbach. M
Lander, Eric S
2016-01-14
Three years ago, scientists reported that CRISPR technology can enable precise and efficient genome editing in living eukaryotic cells. Since then, the method has taken the scientific community by storm, with thousands of labs using it for applications from biomedicine to agriculture. Yet, the preceding 20-year journey--the discovery of a strange microbial repeat sequence; its recognition as an adaptive immune system; its biological characterization; and its repurposing for genome engineering--remains little known. This Perspective aims to fill in this backstory--the history of ideas and the stories of pioneers--and draw lessons about the remarkable ecosystem underlying scientific discovery. Copyright © 2016 Elsevier Inc. All rights reserved.
Carotenoid Biosynthesis in Arabidopsis: A Colorful Pathway
Ruiz-Sola, M. Águila; Rodríguez-Concepción, Manuel
2012-01-01
Plant carotenoids are a family of pigments that participate in light harvesting and are essential for photoprotection against excess light. Furthermore, they act as precursors for the production of apocarotenoid hormones such as abscisic acid and strigolactones. In this review, we summarize the current knowledge on the genes and enzymes of the carotenoid biosynthetic pathway (which is now almost completely elucidated) and on the regulation of carotenoid biosynthesis at both transcriptional and post-transcriptional levels. We also discuss the relevance of Arabidopsis as a model system for the study of carotenogenesis and how metabolic engineering approaches in this plant have taught important lessons for carotenoid biotechnology. PMID:22582030
Rocketdyne - Lunar Ascent Engine. Chapter 7, Appendix I
NASA Technical Reports Server (NTRS)
Harmon, Tim
2009-01-01
The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).
Summary of Planned Implementation for the HTGR Lessons Learned Applicable to the NGNP
DOE Office of Scientific and Technical Information (OSTI.GOV)
Ian Mckirdy
2011-09-01
This document presents a reconciliation of the lessons learned during a 2010 comprehensive evaluation of pertinent lessons learned from past and present high temperature gas-cooled reactors that apply to the Next Generation Nuclear Plant Project along with current and planned activities. The data used are from the latest Idaho National Laboratory research and development plans, the conceptual design report from General Atomics, and the pebble bed reactor technology readiness study from AREVA. Only those lessons related to the structures, systems, and components of the Next Generation Nuclear Plant (NGNP), as documented in the recently updated lessons learned report are addressed.more » These reconciliations are ordered according to plant area, followed by the affected system, subsystem, or component; lesson learned; and finally an NGNP implementation statement. This report (1) provides cross references to the original lessons learned document, (2) describes the lesson learned, (3) provides the current NGNP implementation status with design data needs associated with the lesson learned, (4) identifies the research and development being performed related to the lesson learned, and (5) summarizes with a status of how the lesson learned has been addressed by the NGNP Project.« less
The Apollo Expericence Lessons Learned for Constellation Lunar Dust Management
NASA Astrophysics Data System (ADS)
Wagner, Sandra
2006-09-01
Lunar dust will present significant challenges to NASA's Lunar Exploration Missions. The challenges can be overcome by using best practices in system engineering design. For successful lunar surface missions, all systems that come into contact with lunar dust must consider the effects throughout the entire design process. Interfaces between all these systems with other systems also must be considered. Incorporating dust management into Concept of Operations and Requirements development are the best place to begin to mitigate the risks presented by lunar dust. However, that is only the beginning. To be successful, every person who works on NASA's Constellation lunar missions must be mindful of this problem. Success will also require fiscal responsibility. NASA must learn from Apollo the root cause of problems caused by dust, and then find the most cost-effective solutions to address each challenge. This will require a combination of common sense existing technologies and promising, innovative technical solutions
The Apollo Experience Lessons Learned for Constellation Lunar Dust Management
NASA Technical Reports Server (NTRS)
Wagner, Sandra
2006-01-01
Lunar dust will present significant challenges to NASA's Lunar Exploration Missions. The challenges can be overcome by using best practices in system engineering design. For successful lunar surface missions, all systems that come into contact with lunar dust must consider the effects throughout the entire design process. Interfaces between all these systems with other systems also must be considered. Incorporating dust management into Concept of Operations and Requirements development are the best place to begin to mitigate the risks presented by lunar dust. However, that is only the beginning. To be successful, every person who works on NASA's Constellation lunar missions must be mindful of this problem. Success will also require fiscal responsibility. NASA must learn from Apollo the root cause of problems caused by dust, and then find the most cost-effective solutions to address each challenge. This will require a combination of common sense existing technologies and promising, innovative technical solutions
NASA Technical Reports Server (NTRS)
Stambaugh, Imelda; Baccus, Shelley; Buffington, Jessie; Hood, Andrew; Naids, Adam; Borrego, Melissa; Hanford, Anthony J.; Eckhardt, Brad; Allada, Rama Kumar; Yagoda, Evan
2013-01-01
Engineers at Johnson Space Center (JSC) are developing an Environmental Control and Life Support System (ECLSS) design for the Multi-Mission Space Exploration Vehicle (MMSEV). The purpose of the MMSEV is to extend the human exploration envelope for Lunar, Near Earth Object (NEO), or Deep Space missions by using pressurized exploration vehicles. The MMSEV, formerly known as the Space Exploration Vehicle (SEV), employs ground prototype hardware for various systems and tests it in manned and unmanned configurations. Eventually, the system hardware will evolve and become part of a flight vehicle capable of supporting different design reference missions. This paper will discuss the latest MMSEV ECLSS architectures developed for a variety of design reference missions, any work contributed toward the development of the ECLSS design, lessons learned from testing prototype hardware, and the plan to advance the ECLSS toward a flight design.
Konstantinidis, Georgios; Anastassopoulos, George C; Karakos, Alexandros S; Anagnostou, Emmanouil; Danielides, Vasileios
2012-04-01
The aim of this study is to present our perspectives on healthcare analysis and design and the lessons learned from our experience with the development of a distributed, object-oriented Clinical Information System (CIS). In order to overcome known issues regarding development, implementation and finally acceptance of a CIS by the physicians we decided to develop a novel object-oriented methodology by integrating usability principles and techniques in a simplified version of a well established software engineering process (SEP), the Unified Process (UP). A multilayer architecture has been defined and implemented with the use of a vendor application framework. Our first experiences from a pilot implementation of our CIS are positive. This approach allowed us to gain a socio-technical understanding of the domain and enabled us to identify all the important factors that define both the structure and the behavior of a Health Information System.
A first step toward understanding patient safety
2016-01-01
Patient safety has become an important policy agenda in healthcare systems since publication of the 1999 report entitled "To Err Is Human." The paradigm has changed from blaming the individual for the error to identifying the weakness in the system that led to the adverse events. Anesthesia is one of the first healthcare specialties to adopt techniques and lessons from the aviation industry. The widespread use of simulation programs and the application of human factors engineering to clinical practice are the influences of the aviation industry. Despite holding relatively advanced medical technology and comparable safety records, the Korean health industry has little understanding of the systems approach to patient safety. Because implementation of the existing system and program requires time, dedication, and financial support, the Korean healthcare industry is in urgent need of developing patient safety policies and putting them into practice to improve patient safety before it is too late. PMID:27703622
NASA Technical Reports Server (NTRS)
Stambaugh, Imelda; Baccus, Shelley; Naids, Adam; Hanford, Anthony
2012-01-01
Engineers at Johnson Space Center (JSC) are developing an Environmental Control and Life Support System (ECLSS) design for the Multi-Mission Space Exploration Vehicle (MMSEV). The purpose of the MMSEV is to extend the human exploration envelope for Lunar, Near Earth Object (NEO), or Deep Space missions by using pressurized exploration vehicles. The MMSEV, formerly known as the Space Exploration Vehicle (SEV), employs ground prototype hardware for various systems and tests it in manned and unmanned configurations. Eventually, the system hardware will evolve and become part of a flight vehicle capable of supporting different design reference missions. This paper will discuss the latest MMSEV ECLSS architectures developed for a variety of design reference missions, any work contributed toward the development of the ECLSS design, lessons learned from testing prototype hardware, and the plan to advance the ECLSS toward a flight design.
NASA Astrophysics Data System (ADS)
Gero, Aharon
2017-05-01
A course entitled 'Science and Engineering Education: Interdisciplinary Aspects' was designed to expose undergraduate students of science and engineering education to the attributes of interdisciplinary education which integrates science and engineering. The core of the course is an interdisciplinary lesson, which each student is supposed to teach his/her peers. Sixteen students at advanced stages of their studies attended the course. The research presented here used qualitative instruments to characterise students' attitudes towards interdisciplinary learning and teaching of science and engineering. According to the findings, despite the significant challenge which characterises interdisciplinary teaching, a notable improvement was evident throughout the course in the percentage of students who expressed willingness to teach interdisciplinary classes in future.
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.
Nakamura, Brad J; Mueller, Charles W; Higa-McMillan, Charmaine; Okamura, Kelsie H; Chang, Jaime P; Slavin, Lesley; Shimabukuro, Scott
2014-01-01
Hawaii's Child and Adolescent Mental Health Division provides a unique illustration of a youth public mental health system with a long and successful history of large-scale quality improvement initiatives. Many advances are linked to flexibly organizing and applying knowledge gained from the scientific literature and move beyond installing a limited number of brand-named treatment approaches that might be directly relevant only to a small handful of system youth. This article takes a knowledge-to-action perspective and outlines five knowledge management strategies currently under way in Hawaii. Each strategy represents one component of a larger coordinated effort at engineering a service system focused on delivering both brand-named treatment approaches and complimentary strategies informed by the evidence base. The five knowledge management examples are (a) a set of modular-based professional training activities for currently practicing therapists, (b) an outreach initiative for supporting youth evidence-based practices training at Hawaii's mental health-related professional programs, (c) an effort to increase consumer knowledge of and demand for youth evidence-based practices, (d) a practice and progress agency performance feedback system, and (e) a sampling of system-level research studies focused on understanding treatment as usual. We end by outlining a small set of lessons learned and a longer term vision for embedding these efforts into the system's infrastructure.
NASA Astrophysics Data System (ADS)
Keller, John; Rebar, Bryan
2012-11-01
The STEM Teacher and Researcher (STAR) Program provides 9-week paid summer research experiences at national research laboratories for future science and math teachers. The program, run by the Cal Poly Center for Excellence in Science and Mathematics Education (CESaME) on behalf of the entire California State University (CSU) System, has arranged 290 research internships for 230 STEM undergraduates and credential candidates from 43 campuses over the past 6 years. The program has partnered with seven Department of Energy labs, four NASA centers, three NOAA facilities, and the National Optical Astronomy Observatory (NOAO). Primary components of the summer experience include a) conducting research with a mentor or mentor team, b) participating in weekly 2-3 hour workshops focused on translating lessons learned from summer research into classroom practice, and c) presenting a research poster or oral presentation and providing a lesson plan linked to the summer research experience. The central premise behind the STAR Program is that future science and math teachers can more effectively prepare the next generation of science, math, and engineering students if they themselves have authentic experiences as researchers.
System Design and Implementation of the Detector Assembly of the Astro-H Soft X-Ray Spectrometer
NASA Technical Reports Server (NTRS)
Chiao, M. P.; Adams, J.; Goodwin, P.; Hobson, C.W.; Kelley, R. L.; Kilbourne, C. A.; McCammom, D.; McGuinness, D. S.; Moseley, S. J.; Porter, F. S.;
2016-01-01
The soft x-ray spectrometer (SXS) onboard Astro-H presents to the science community unprecedented capability (less than 7 eV at 6 keV) for high-resolution spectral measurements in the range of 0.5-12 keV to study extended celestial sources. At the heart of this SXS is the x-ray calorimeter spectrometer (XCS) where detectors (calorimeter array and anticoincidence detector) operate at 50 mK, the bias circuit operates at nominal 1.3 K, and the first stage amplifiers operateat 130 K, all within a nominal 20 cm envelope. The design of the detector assembly in this XCS originates from the Astro-E x-ray spectrometer (XRS) and lessons learned from Astro-E and Suzaku. After the production of our engineering model, additional changes were made in order to improve our flight assembly process for better reliability and overall performance. In this poster, we present the final design and implementation of the flight detector assembly, show comparison of parameters and performance to Suzakus XRS, and list susceptibilities to other subsystems as well as our lessons learned.
Lessons from X-Ray Astronomy Applied to HST
NASA Astrophysics Data System (ADS)
Schreier, Ethan J.; Doxsey, Rodger
2000-09-01
Riccardo Giacconi, probably more than any other single individual, established x-ray astronomy as an essential sub-discipline of astronomy. Its incorporation into the mainstream of astronomy was substantially completed with the Einstein Observatory which, with its imaging capabilities and its Guest Observer program, invited non-x-ray astronomers to use the facility. It was therefore perhaps fitting that when optical astronomy moved into space, with the Hubble Space Telescope, it called on Riccardo to oversee the transition. He brought with him lessons about building and operating space observatories, experience working with NASA on large science projects, a business-like approach to attacking tasks, and his unique vision and abilities. Among the guiding principles he brought to HST were: involvement of a strong scientific research staff in all aspects of the program; establishment of a vital, active research environment; attention to "science system engineering" and applying a rational scientific approach to problems; creation of an atmosphere of "ruthless intellectual honesty" and maintenance of the highest regard for process. These formed the basis both for attacking the problems of HST, and for building an Institute to do so.
Review of NASA's Hypersonic Research Engine Project
NASA Technical Reports Server (NTRS)
Andrews, Earl H.; Mackley, Ernest A.
1993-01-01
The goals of the NASA Hypersonic Research Engine (HRE) Project, which began in 1964, were to design, develop, and construct a hypersonic research ramjet/scramjet engine for high performance and to flight-test the developed concept over the speed range from Mach 3 to 8. The project was planned to be accomplished in three phases: project definition, research engine development, and flight test using the X-15A-2 research aircraft, which was modified to carry hydrogen fuel for the research engine. The project goal of an engine flight test was eliminated when the X-15 program was canceled in 1968. Ground tests of engine models then became the focus of the project. Two axisymmetric full-scale engine models having 18-inch-diameter cowls were fabricated and tested: a structural model and a combustion/propulsion model. A brief historical review of the project with salient features, typical data results, and lessons learned is presented.
Habitability and Human Factors: Lessons Learned in Long Duration Space Flight
NASA Technical Reports Server (NTRS)
Baggerman, Susan D.; Rando, Cynthia M.; Duvall, Laura E.
2006-01-01
This study documents the investigation of qualitative habitability and human factors feedback provided by scientists, engineers, and crewmembers on lessons learned from the ISS Program. A thorough review and understanding of this data is critical in charting NASA's future path in space exploration. NASA has been involved in ensuring that the needs of crewmembers to live and work safely and effectively in space have been met throughout the ISS Program. Human factors and habitability data has been collected from every U.S. crewmember that has resided on the ISS. The knowledge gained from both the developers and inhabitants of the ISS have provided a significant resource of information for NASA and will be used in future space exploration. The recurring issues have been tracked and documented; the top 5 most critical issues have been identified from this data. The top 5 identified problems were: excessive onsrbit stowage; environment; communication; procedures; and inadequate design of systems and equipment. Lessons learned from these issues will be used to aid in future improvements and developments to the space program. Full analysis of the habitability and human factors data has led to the following recommendations. It is critical for human factors to be involved early in the design of space vehicles and hardware. Human factors requirements need to be readdressed and redefined given the knowledge gained during previous ISS and long-duration space flight programs. These requirements must be integrated into vehicle and hardware technical documentation and consistently enforced. Lastly, space vehicles and hardware must be designed with primary focus on the user/operator to successfully complete missions and maintain a safe working environment. Implementation of these lessons learned will significantly improve NASA's likelihood of success in future space endeavors.
NASA Astrophysics Data System (ADS)
Manha, William D.
2010-09-01
One to the expressions for the most demanding quality was made by a well-known rocket scientist, for which this center was named, Dr. Wernher Von Braun in the Foreword of a book about the design of rocket engines that was first published by NASA in 1967: “Success in space demands perfection. Many of the brilliant achievements made in this vast, austere environment seem almost miraculous. Behind each apparent miracle, however, stands the flawless performance of numerous highly complex systems. All are important. The failure of only one portion of a launch vehicle or spacecraft may cause failure of an entire mission. But the first to feel this awesome imperative for perfection are the propulsion systems, especially the engines. Unless they operate flawlessly first, none of the other systems will get a chance to perform in space. Perfection begins in the design of space hardware. This book emphasizes quality and reliability in the design of propulsion and engine systems. It draws deeply from the vast know-how and experience which have been the essence of several well-designed, reliable systems of the past and present. And, with a thoroughness and completeness not previously available, it tells how the present high state of reliability, gained through years of research and testing, can be maintained, and perhaps improved, in engines of the future. As man ventures deeper into space to explore the planets, the search for perfection in the design of propulsion systems will continue.” Some catastrophes with losses of life will be compared to show lapses in quality and safety and contrasted with a catastrophe without loss of life because of compliance with safety requirements. 1. October 24, 1960,(USSR) Nedelin Catastrophe, Death on the Steppes, 124 deaths 2. October 25, 1966,(USA) North American Rockwell, Apollo Block I Service Module Service(SM) Propulsion System fuel tank explosion/fire and destruction of SM and test cell, test engineer/conductor/author, Bill Manha,(the presenter) 0 injuries, 0 deaths 3. March 18, 1980,(USSR) Vostok 8A92M booster pad explosion, 48 deaths. 4. August 22, 2003,(Brazil) -Alcantara VLS -1, V03. Solid rocket ignited on pad, 21 deaths 5. Summer of 2006(USA) a payload organization inquired about requirements to fly a satellite with a new “safe” SpaceDev hybrid propulsion system using a solid polymer as the fuel and nitrous oxide as the oxidizer. The extensive titanium/nitrous oxide materials compatibility testing that was required discouraged the payload organization from further exploration of using the Shuttle as the launch vehicle. 6. July 26, 2007(USA) SpaceShipTwo nitrous oxide explosion, 3 seriously injured, 3 deaths The above listed catastrophic failures resulted in 210 deaths, but there were none on the Apollo SM explosion because of compliance with CalOSHA. This is an applied lesson learned of the Shuttle. Safety was not jeopardized without extensive materials compatibility testing. On the other hand, the nitrous oxide was erroneously identified as safe for launch from Shuttle or ISS which resulted in a catastrophic explosion and resulted in 3 major injuries, and 3 deaths. This is a testimony of a survivor of a catastrophic failure where safety rules were followed and the application of the lesson learned which confirmed safety and quality, as expressed by Von Braun, PERFECTION and SAFETY do MATTER!
NASA Astrophysics Data System (ADS)
Nicholas-Figueroa, Linda
Upon regaining the right to direct education at the local level, the North Slope Borough (NSB) of Alaska incorporated Inupiat educational philosophies into the educational system. The NSB in partnership with the University of Alaska Fairbanks established Ilisagvik College, the only tribal college in Alaska. Ilisagvik College seeks to broaden science, technology, engineering, and mathematical education on the North Slope. Incorporation of place-based and informal lessons with traditional ecological knowledge engages students in education. Ilisagvik hosted a 2-week climate change program from 2012 - 2015 for high school and middle school students that examined climate science and the effects of a warming climate on the local environment from a multitude of perspectives from scientists, Inupiat Elders, and instructor-led field trips. Pre-assessments and post-assessments using the Student Assessment of Learning Gains tool measured students' interests and conceptual understanding. Students developed and enhanced their understanding of science concepts and, at the end of the program, could articulate the impact of climatic changes on their local environment. Similarly, methods to incorporate Indigenous knowledge into research practices have been achieved, such as incorporating field trips and discussion with Elders on the importance of animal migration, whale feeding patterns, and the significance of sea-ice conditions, which are important community concerns.
GSFC Technical Outreach: The Capitol College Model
NASA Technical Reports Server (NTRS)
Marius, Julio L.; Wagner, David
2008-01-01
In February 2005, as part of the National Aeronautic and Space Administration (NASA) Technical Outreach Program, Goddard Space Flight Center (GSFC) awarded Capitol College of Laurel, Maryland an Educational Grant to establish a Space Operation academic curriculum to meet the future needs of mission operations engineers. This was in part due to the aerospace industry and GSFC concerns that a large number of professional engineers are projected to retire in the near term with evidence showing that current enrollment in engineering schools will not produce sufficient number of space operation trained engineers that will meet industry and government demands. Capitol College, under the agreement of the Educational Grant, established the Space Operations Institute (SOI) with a new curriculum in Space Operations that was approved and certified by the State of Maryland. The SO1 programs focuses on attracting, recruiting, and training a pipeline of highly qualified engineers with experience in mission operations, system engineering and development. The selected students are integrated as members of the engineering support team in any of the missions supported by the institute. The students are mentored by professional engineers from several aerospace companies that support GSFC. Initially, the institute was involved in providing console engineers and mission planning trainees for the Upper Atmosphere Research Satellite (UARS), the Earth Radiation Budget Satellite (ERBS) and the Total Ozone Mapping Spectrometer mission (TOMS). Subsequently, the students were also involved in the technology refresh of the TOMS ground system and other mission operations development. Further mission assignment by GSFC management included participation in the Tropical Rainfall Measuring Mission (TRMM) mission operations and ground system technology refresh. The SOI program has been very successful. Since October 2005, sixty-four students have been enrolled in the SOI program and twenty-five have already graduated from the program, nineteen of whom are employed by company's supporting GSFC. Due to the success of the program, the initial grant period was extended for another period of two years. This paper presents the process that established the SOI as a viable pipeline of mission operations engineers, the lessons learned in the process of dealing with grants, and experience gained in mentoring engineering students that are responsible for particular areas of expertise and functionality. This paper can also be considered a case study and model for integrating a student team with government and industry professionals in the real world of mission operations.
Lessons Learned from the Advanced Topographic Laser Altimeter System
NASA Technical Reports Server (NTRS)
Garrison, Matt; Patel, Deepak; Bradshaw, Heather; Robinson, Frank; Neuberger, Dave
2016-01-01
The ICESat-2 Advanced Topographic Laser Altimeter System (ATLAS) instrument is an upcoming Earth Science mission focusing on the effects of climate change. The flight instrument passed all environmental testing at GSFC (Goddard Space Flight Center) and is now ready to be shipped to the spacecraft vendor for integration and testing. This presentation walks through the lessons learned from design, hardware, analysis and testing perspective. ATLAS lessons learned include general thermal design, analysis, hardware, and testing issues as well as lessons specific to laser systems, two-phase thermal control, and optical assemblies with precision alignment requirements.
Enrichment Zoning Options for the Small Nuclear Rocket Engine (SNRE)
DOE Office of Scientific and Technical Information (OSTI.GOV)
Bruce G. Schnitzler; Stanley K. Borowski
2010-07-01
Advancement of U.S. scientific, security, and economic interests through a robust space exploration program requires high performance propulsion systems to support a variety of robotic and crewed missions beyond low Earth orbit. In NASA’s recent Mars Design Reference Architecture (DRA) 5.0 study (NASA-SP-2009-566, July 2009), nuclear thermal propulsion (NTP) was again selected over chemical propulsion as the preferred in-space transportation system option because of its high thrust and high specific impulse (-900 s) capability, increased tolerance to payload mass growth and architecture changes, and lower total initial mass in low Earth orbit. An extensive nuclear thermal rocket technology development effortmore » was conducted from 1955-1973 under the Rover/NERVA Program. The Small Nuclear Rocket Engine (SNRE) was the last engine design studied by the Los Alamos National Laboratory during the program. At the time, this engine was a state-of-the-art design incorporating lessons learned from the very successful technology development program. Past activities at the NASA Glenn Research Center have included development of highly detailed MCNP Monte Carlo transport models of the SNRE and other small engine designs. Preliminary core configurations typically employ fuel elements with fixed fuel composition and fissile material enrichment. Uniform fuel loadings result in undesirable radial power and temperature profiles in the engines. Engine performance can be improved by some combination of propellant flow control at the fuel element level and by varying the fuel composition. Enrichment zoning at the fuel element level with lower enrichments in the higher power elements at the core center and on the core periphery is particularly effective. Power flattening by enrichment zoning typically results in more uniform propellant exit temperatures and improved engine performance. For the SNRE, element enrichment zoning provided very flat radial power profiles with 551 of the 564 fuel elements within 1% of the average element power. Results for this and alternate enrichment zoning options for the SNRE are compared.« less
Introduction to computers: Reference guide
DOE Office of Scientific and Technical Information (OSTI.GOV)
Ligon, F.V.
1995-04-01
The ``Introduction to Computers`` program establishes formal partnerships with local school districts and community-based organizations, introduces computer literacy to precollege students and their parents, and encourages students to pursue Scientific, Mathematical, Engineering, and Technical careers (SET). Hands-on assignments are given in each class, reinforcing the lesson taught. In addition, the program is designed to broaden the knowledge base of teachers in scientific/technical concepts, and Brookhaven National Laboratory continues to act as a liaison, offering educational outreach to diverse community organizations and groups. This manual contains the teacher`s lesson plans and the student documentation to this introduction to computer course.
Lessons learned from selecting and testing spaceflight potentiometers
NASA Technical Reports Server (NTRS)
Iskenderian, T.
1994-01-01
A solar array drive (SAD) was designed for operation on the TOPEX/POSEIDON spacecraft that was launched in August, 1992. The experience gained in selecting, specifying, testing to failure, and redesigning its position sensor produced valuable lessons for future component selection and qualification. Issues of spaceflight heritage, cost/benefit/risk assessment, and component specification are addressed. It was found that costly schedule and budget overruns may have been avoided if the capability of the candidate sensors to meet requirements had been more critically examined prior to freezing the design. The use of engineering models and early qualification tests is also recommended.
Towards a Rigorous Assessment of Systems Biology Models: The DREAM3 Challenges
Prill, Robert J.; Marbach, Daniel; Saez-Rodriguez, Julio; Sorger, Peter K.; Alexopoulos, Leonidas G.; Xue, Xiaowei; Clarke, Neil D.; Altan-Bonnet, Gregoire; Stolovitzky, Gustavo
2010-01-01
Background Systems biology has embraced computational modeling in response to the quantitative nature and increasing scale of contemporary data sets. The onslaught of data is accelerating as molecular profiling technology evolves. The Dialogue for Reverse Engineering Assessments and Methods (DREAM) is a community effort to catalyze discussion about the design, application, and assessment of systems biology models through annual reverse-engineering challenges. Methodology and Principal Findings We describe our assessments of the four challenges associated with the third DREAM conference which came to be known as the DREAM3 challenges: signaling cascade identification, signaling response prediction, gene expression prediction, and the DREAM3 in silico network challenge. The challenges, based on anonymized data sets, tested participants in network inference and prediction of measurements. Forty teams submitted 413 predicted networks and measurement test sets. Overall, a handful of best-performer teams were identified, while a majority of teams made predictions that were equivalent to random. Counterintuitively, combining the predictions of multiple teams (including the weaker teams) can in some cases improve predictive power beyond that of any single method. Conclusions DREAM provides valuable feedback to practitioners of systems biology modeling. Lessons learned from the predictions of the community provide much-needed context for interpreting claims of efficacy of algorithms described in the scientific literature. PMID:20186320
Ares I-X Ground Diagnostic Prototype
NASA Technical Reports Server (NTRS)
Schwabacher, Mark A.; Martin, Rodney Alexander; Waterman, Robert D.; Oostdyk, Rebecca Lynn; Ossenfort, John P.; Matthews, Bryan
2010-01-01
The automation of pre-launch diagnostics for launch vehicles offers three potential benefits: improving safety, reducing cost, and reducing launch delays. The Ares I-X Ground Diagnostic Prototype demonstrated anomaly detection, fault detection, fault isolation, and diagnostics for the Ares I-X first-stage Thrust Vector Control and for the associated ground hydraulics while the vehicle was in the Vehicle Assembly Building at Kennedy Space Center (KSC) and while it was on the launch pad. The prototype combines three existing tools. The first tool, TEAMS (Testability Engineering and Maintenance System), is a model-based tool from Qualtech Systems Inc. for fault isolation and diagnostics. The second tool, SHINE (Spacecraft Health Inference Engine), is a rule-based expert system that was developed at the NASA Jet Propulsion Laboratory. We developed SHINE rules for fault detection and mode identification, and used the outputs of SHINE as inputs to TEAMS. The third tool, IMS (Inductive Monitoring System), is an anomaly detection tool that was developed at NASA Ames Research Center. The three tools were integrated and deployed to KSC, where they were interfaced with live data. This paper describes how the prototype performed during the period of time before the launch, including accuracy and computer resource usage. The paper concludes with some of the lessons that we learned from the experience of developing and deploying the prototype.
Evaluation of Strain Measurement Devices for Inflatable Structures
NASA Technical Reports Server (NTRS)
Litteken, Douglas A.
2017-01-01
Inflatable structures provide a significant volume savings for future NASA deep space missions. The complexity of these structures, however, provides difficulty for engineers in designing, analyzing, and testing. Common strain measurement systems for metallic parts cannot be used directly on fabrics. New technologies must be developed and tested to accuractly measure the strain of inflatable structures. This paper documents the testing of six candidate strain measurement devices for use on fabrics. The resistance devices tested showed significant hysteresis during creep and cyclic testing. The capacitive device, however, showed excellent results and little-to-no hysteresis. Because of this issue, only two out of the six proposed devices will continue in development. The resulting data and lessons learned from this effort provides direction for continued work to produce a structural health monitoring system for inflatable habitats.
Evaluation of Strain Measurement Devices for Inflatable Structures
NASA Technical Reports Server (NTRS)
Litteken, Doug
2017-01-01
Inflatable structures provide a significant volume savings for future NASA deep space missions. The complexity of these structures, however, provides difficulty for engineers in designing, analyzing, and testing. Common strain measurement systems for metallic parts cannot be used directly on fabrics. New technologies must be developed and tested to accurately measure the strain of inflatable structures. This paper documents the testing of six candidate strain measurement devices for use on fabrics. The resistance devices tested showed significant hysteresis during creep and cyclic testing. The capacitive device, however, showed excellent results and little-to-no hysteresis. Because of this issue, only two out of the six proposed devices will continue in development. The resulting data and lessons learned from this effort provides direction for continued work to produce a structural health monitoring system for inflatable habitats.
Active cooling from the sixties to NASP
NASA Technical Reports Server (NTRS)
Kelly, H. Neale; Blosser, Max L.
1994-01-01
Vehicles, such as the X-15 or the National Aerospace Plane (NASP), traveling at hypersonic speeds through the earth's atmosphere experience aerodynamic heating. The heating can be severe enough that a thermal protection system is required to limit the temperature of the vehicle structure. Although several categories of thermal protection systems are mentioned briefly, the majority of the present paper describes convectively cooled structures for large areas. Convective cooling is a method of limiting structural temperatures by circulating a coolant through the vehicle structure. Efforts to develop convectively cooled structures during the past 30 years, from early engine structures which were intended to be tested on the X-15 to structural panels fabricated and tested under the NASP program, are described. Many of the lessons learned from these research efforts are presented.
Lessons Learned from using a Livingstone Model to Diagnose a Main Propulsion System
NASA Technical Reports Server (NTRS)
Sweet, Adam; Bajwa, Anupa
2003-01-01
NASA researchers have demonstrated that qualitative, model-based reasoning can be used for fault detection in a Main Propulsion System (MPS), a complex, continuous system. At the heart of this diagnostic system is Livingstone, a discrete, propositional logic-based inference engine. Livingstone comprises a language for specifying a discrete model of the system and a set of algorithms that use the model to track the system's state. Livingstone uses the model to test assumptions about the state of a component - observations from the system are compared with values predicted by the model. The intent of this paper is to summarize some advantages of Livingstone seen through our modeling experience: for instance, flexibility in modeling, speed and maturity. We also describe some shortcomings we perceived in the implementation of Livingstone, such as modeling continuous dynamics and handling of transients. We list some upcoming enhancements to the next version of Livingstone that may resolve some of the current limitations.
Lessons from Jurassic Park: patients as complex adaptive systems.
Katerndahl, David A
2009-08-01
With realization that non-linearity is generally the rule rather than the exception in nature, viewing patients and families as complex adaptive systems may lead to a better understanding of health and illness. Doctors who successfully practise the 'art' of medicine may recognize non-linear principles at work without having the jargon needed to label them. Complex adaptive systems are systems composed of multiple components that display complexity and adaptation to input. These systems consist of self-organized components, which display complex dynamics, ranging from simple periodicity to chaotic and random patterns showing trends over time. Understanding the non-linear dynamics of phenomena both internal and external to our patients can (1) improve our definition of 'health'; (2) improve our understanding of patients, disease and the systems in which they converge; (3) be applied to future monitoring systems; and (4) be used to possibly engineer change. Such a non-linear view of the world is quite congruent with the generalist perspective.
Naval Health Research Center Command Annual Report Calendar Year 1987 and FY-88
1988-01-01
1044-1055). Conference Proceedings Space , 29-31 Aug 88, Albuquerque, New Mexico . 1988, New York: American Society of Civil Engineers. (Center...Proceedings Space , 29-31 Aug 88, Albuquerque, New Mexico . 1988, New York: American Society of Civil Engineers. Work Unit: Army 3MI62770.A87@.AR...New Mexico , 29-31 Aug 88 Dr. Palinkas - "The Human Experience in Space: Lessons from Antarctica" Association of Professional Sleep Societies Meetings
2006-09-01
Monday through Friday in a single week. This daily schedule was chosen so that engineers could still access their office during part of the normal...aluminum, austenitic SS) structures do not cleave! "* Physical Manifestation - Bright, shiny appearance - " Crystallized " fracture surface - Chevrons...region with the "striations" Fracture mode was actually by SOC *Lesson? Don’t base conclusions on a single observation Higher mag macroscopic image
Protecting Secure Facilities From Underground Intrusion Using Seismic/Acoustic Sensor Arrays
2009-08-01
the upper 6 meters of sediments were deposited as part of a delta during a time of higher sea level, when low-gradient rivers carried fine-grained...geological site characterization and stratigraphy and sedimentation processes. Dr. Jason R. McKenna is a geophysicist at the United States Army Engineer...doctrine is being revised to address the engineer force structure at all levels to ensure that emerging lessons learned from Iraq and Afghanistan are
Antidote: Civic Responsibility. Drug Avoidance Lessons for Middle & High School Students.
ERIC Educational Resources Information Center
Hanna, Jack C.; Maddalena, Gracemarie
This book contains nine lessons focusing on legal issues raised by the illegal use and abuse of alcohol and other drugs and efforts by the criminal justice system to curb that use and abuse. The lessons are interactive and sequential, although individual lessons can stand alone. The lessons are designed to be presented to middle and high school…
Ares I-X: First Step in a New Era of Exploration
NASA Technical Reports Server (NTRS)
Davis, Stephan R.
2010-01-01
Since 2005, NASA's Constellation Program has been designing, building, and testing the next generation of launch and space vehicles to carry humans beyond low-Earth orbit (LEO). On October 28, 2009, the Ares Projects successfully launched the first suborbital development flight test of the Ares I crew launch vehicle, Ares I-X, from Kennedy Space Center (KSC). Although the final Constellation Program architecture is under review, data and lessons obtained from Ares I-X can be applied to any launch vehicle. This presentation will discuss the mission background and future impacts of the flight. Ares I is designed to carry up to four astronauts to the International Space Station (ISS). It also can be used with the Ares V cargo launch vehicle for a variety of missions beyond LEO. The Ares I-X development flight test was conceived in 2006 to acquire early engineering, operations, and environment data during liftoff, ascent, and first stage recovery. Engineers are using the test flight data to improve the Ares I design before its critical design review the final review before manufacturing of the flight vehicle begins. The Ares I-X flight test vehicle incorporated a mix of flight and mockup hardware, reflecting a similar length and mass to the operational vehicle. It was powered by a four-segment SRB from the Space Shuttle inventory, and was modified to include a fifth, spacer segment that made the booster approximately the same size as the five-segment SRB. The Ares I-X flight closely approximated flight conditions the Ares I will experience through Mach 4.5, performing a first stage separation at an altitude of 125,000 feet and reaching a maximum dynamic pressure ("Max Q") of approximately 850 pounds per square foot. The Ares I-X Mission Management Office (MMO) was organized functionally to address all the major test elements, including: first stage, avionics, and roll control (Marshall Space Flight Center); upper stage simulator (Glenn Research Center); crew module/launch abort system simulator (Langley Research Center); and ground systems and operations (KSC). Interfaces between vehicle elements and vehicle-ground elements, as well as environment analyses were performed by a systems engineering and integration team at Langley. Experience and lessons learned from these integrated product teams area are already being integrated into the Ares Projects to support the next generation of exploration launch vehicles.
Eelgrass response to Changing Environmental Drivers: Lessons from PNW Mesocosm Studies
Seagrass communities are ecosystem engineers that provide important services in a dynamic estuarine environment. Seagrass is often seen as a sentinel species or indicator of estuarine health. Estuaries are increasingly impacted by natural and anthropogenic stressors, and loss o...
NASA Technical Reports Server (NTRS)
Peeris, Kumar; Izygon, Michel
1993-01-01
This report explains some of the concepts of the ESL prototype and summarizes some of the lessons learned in using the prototype for implementing the Flight Mechanics Tool Kit (FMToolKit) series of Ada programs.