Science.gov

Sample records for lesson learned case

  1. [Lessons learned from tuberculosis outbreak cases].

    PubMed

    Kato, Seiya; Kuwabara, Katsuhiro

    2014-02-01

    Most TB outbreaks were caused by exposure of many people to tuberculosis bacilli due to delayed detection of initial cases who had long-lasting severe coughs and excretion of massive tuberculosis bacilli. They were also affected by several other factors, such as socio-environmental factors of the initial case; time and place of infection; and host factors of the infected persons such as immune status, infectivity, and/or pathogenicity of the bacilli. In this symposium, we learned the seriousness of infection and disease among immune-suppressed groups, special environmental factors with regard to the spread of infection, disease after treatment of latent tuberculosis infection, diagnostic specification of IGRA, and bacteriological features including genotyping of the bacilli. We reaffirmed that countermeasures for the case are important, but outbreaks can provide excellent opportunities to learn important information about infection, disease progression, etc. 1. Tuberculosis outbreak in a cancer ward: Katsuhiro KUWABARA (Division of Respiratory Diseases, National Hospital Organization Nishi-Niigata Chuo National Hospital) There was an outbreak of tuberculosis in a cancer ward of a highly specialized medical center. Outbreak cases included eight hospitalized patients and two medical staff members over a 1.5-year observation period after initial contact. Three immune-compromised patients including the index patent died of cancer and tuberculosis. Community hospitals and highly specialized medical centers, such as cancer centers, should carefully prepare a proper system to prevent nosocomial transmission of tuberculosis. 2. Sixty-one cases of TB exposures in hospital settings and contact investigations of the hospital staff, with special reference to the application of QFT: Hiroko Yoshikawa NIGORIKAWA (The Division of Infectious Diseases, Tokyo Metropolitan Health and Medical Treatment Corporation, Toshima Hospital; present: Division of Infectious Diseases, Tokyo

  2. Environmental effects consideration: A case study - Lessons learned

    NASA Technical Reports Server (NTRS)

    Vaughan, William W.; Anderson, B. J.

    1992-01-01

    This paper discusses the importance for serious consideration of environmental effects and associated risks by management early in the development cycle of a facility. A case study on the Space Shuttle provides information with regard to some of the environmental effects issues encountered and the lesson learned. The importance of early management action to enable the acceptance of known environmental risks, or to make program adjustments to avoid their potential consequences, is emphasized.

  3. Two gimbal bearing case studies: Some lessons learned

    NASA Technical Reports Server (NTRS)

    Loewenthal, Stuart H.

    1988-01-01

    Two troublesome, torque related problems associated with gimbal actuators are discussed. Large, thin section angular contact bearings can have a surprisingly high torque sensitivity to radial thermal gradients. A predictive thermal-mechanical bearing analysis, as described, was helpful in establishing a safe temperature operating envelope. In the second example, end-of-travel torque limits of an oscillatory gimbal bearing appoached motor stall during limit cycling life tests. Bearing modifications required to restore acceptable torque performance are described. The lessons learned from these case studies should benefit designers of precision gimbals where singular bearing torque related problems are not uncommon.

  4. Lessons Learned

    PubMed Central

    Davis, Michaela

    2015-01-01

    The public health nurses’ scope of practice explicitly includes child protection within their role, which places them in a prime position to identify child protection concerns. This role compliments that of other professions and voluntary agenices who work with children. Public health nurses are in a privileged position as they form a relationship with the child’s parent(s)/guardian(s) and are able to see the child in its own environment, which many professionals cannot. Child protection in Ireland, while influenced by other countries, has progressed through a distinct pathway that streamlined protocols and procedures. However, despite the above serious failures have occurred in the Irish system, and inquiries over the past 20 years persistently present similar contributing factors, namely, the lack of standardized and comprehensive service responses. Moreover, poor practice is compounded by the lack of recognition of the various interactional processes taking place within and between the different agencies of child protection, leading to psychological barriers in communication. This article will explore the lessons learned for public health nurses practice in safeguarding children in the Republic of Ireland. PMID:27335944

  5. Lesson Learning at JPL

    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

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

  7. Making Interdisciplinary Collaboration Work: Key Ideas, a Case Study and Lessons Learned

    ERIC Educational Resources Information Center

    McMurtry, Angus; Clarkin, Chantalle; Bangou, Francis; Duplaa, Emmanuel; MacDonald, Colla; Ng-A-Fook, Nicholas; Trumpower, David

    2012-01-01

    This article discusses the "lessons learned" from an attempt to establish an interdisciplinary education research group. The growth, development and dissolution of the group are treated as an instrumental case study. Current literature on interdisciplinary collaboration is synthesized in order to provide a frame for analysis. Data was collected…

  8. Learning with and about Advertising in Chemistry Education with a Lesson Plan on Natural Cosmetics--A Case Study

    ERIC Educational Resources Information Center

    Belova, Nadja; Eilks, Ingo

    2015-01-01

    This paper describes a case study on the chemistry behind natural cosmetics in five chemistry learning groups (grades 7-11, age range 13-17) in a German comprehensive school. The lesson plan intends to promote critical media literacy in the chemistry classroom and specifically emphasizes learning with and about advertising. The lessons of four…

  9. Ecological risk assessments for watersheds: Lessons learned from case studies

    SciTech Connect

    Marcy, S.K.M.

    1994-12-31

    The USEPA Office of Water and Risk Assessment Forum are co-sponsoring the development of watershed level ecological risk assessments in Big Darby Creek, OH, Clinch River, VA, Middle Platte River Wetlands, NE, Snake River, ID, and Waquoit Bay Estuary, MA. The case studies are testing the Agency`s Framework for Ecological Risk Assessment at a watershed scale for multiple stressors. During case study development much has been learned about how to apply and modify the principles in the Framework to landscape scale risk assessments. Insights include how to select appropriate assessment endpoints to drive the risk assessment, how to effectively increase involvement by risk management teams, and provide decision opportunities for managers throughout development. The case studies demonstrate diverse ways to conduct watershed risk assessments, and illustrate the importance of multiple risk hypotheses in conceptual models addressing the combined and relative risk of chemical, physical and biological stressors. Issues the case studies highlight include the need for a process to determine when watershed risk assessments are appropriate and at what level of complexity they should be performed, how to increase the use of the ecological risk assessments in management decision-making and how to determine the best risk reduction strategy. An update on the watershed case studies will be provided and the insights and issues stated above, discussed.

  10. Lessons Learned... and Not Learned: A Case Study in Regulatory Evolution

    SciTech Connect

    Conant, J. F.; Woodard, R. C.

    2006-07-01

    'Are you better off than you were four years ago?' 'You've come a long way, baby.' Eschewing politics and advertising, these idioms are applied to the evolution of regulatory processes for Decontamination and Decommissioning (D and D) of nuclear facilities. We use a case study of a (nearly) completed D and D project at a large nuclear fuel manufacturing facility, to chronicle one licensee's experience with US Nuclear Regulatory Commission (NRC) D and D regulations from the 1990's to the present. Historical milestones include the birth of a D and D project, a false start and resultant consequences, a D and D 'moratorium' with subsequent planning and stakeholder integration, a second start which included the challenge of parallel path D and D physical work and regulatory processes, and the 'lessons learned' contributions to timely project progress. Further discussion includes a look at the 'declaration of victory' and examines what it really means to be finished. The rich contextual experience from the case study and the observations of other industry members provides the basis for answers to several key questions: How far has the regulatory process for D and D really evolved, and in what direction? Are licensees generally satisfied or dissatisfied with the methods? What has not improved? Which improvements looked promising, but languished in recent years? How far have we really come and are we better off? What are the opportunities for further improvement? The summary answer to each question, using compendious engineering terms is... 'it depends'. (authors)

  11. Apollo Lesson Sampler: Apollo 13 Lessons Learned

    NASA Technical Reports Server (NTRS)

    Interbartolo, Michael A.

    2008-01-01

    This CD-ROM contains a two-part case study of the Apollo 13 accident. The first lesson contains an overview of the electrical system hardware on the Apollo spacecraft, providing a context for the details of the oxygen tank explosion, and the failure chain reconstruction that led to the conditions present at the time of the accident. Given this background, the lesson then covers the tank explosion and immediate damage to the spacecraft, and the immediate response of Mission Control to what they saw. Part 2 of the lesson picks up shortly after the explosion of the oxygen tank on Apollo 13, and discusses how Mission Control gained insight to and understanding of the damage in the aftermath. Impacts to various spacecraft systems are presented, along with Mission Control's reactions and plans for in-flight recovery leading to a successful entry. Finally, post-flight vehicle changes are presented along with the lessons learned.

  12. Lessons learned from case studies of inhalation exposures of workers to radioactive aerosols

    SciTech Connect

    Hoover, M.D.; Fencl, A.F.; Newton, G.J.

    1995-12-01

    Various Department of Energy requirements, rules, and orders mandate that lessons learned be identified, evaluated, shared, and incorporated into current practices. The recently issued, nonmandatory DOE standard for Development of DOE Lessons Learned Program states that a DOE-wide lessons learned program will {open_quotes}help to prevent recurrences of negative experiences, highlight best practices, and spotlight innovative ways to solve problems or perform work more safely, efficiently, and cost effectively.{close_quotes} Additional information about the lessons learned program is contained in the recently issued DOE handbook on Implementing U.S. Department of Energy Lessons Learned Programs and in October 1995 DOE SAfety Notice on Lessons Learned Programs. This report summarizes work in progress at ITRI to identify lessons learned for worker exposures to radioactive aerosols, and describes how this work will be incorporated into the DOE lessons learned program, including a new technical guide for measuring, modeling, and mitigating airborne radioactive particles. Follow-on work is focusing on preparation of {open_quotes}lessons learned{close_quotes} training materials for facility designers, managers, health protection professionals, line supervisors, and workers.

  13. Lessons Learned about Effective Professional Development: Two Contrasting Case Studies

    ERIC Educational Resources Information Center

    Holm, Jennifer; Kajander, Ann

    2015-01-01

    Professional learning groups are becoming a popular form of teacher development in mathematics. Due to the personal nature of the groups, as well as differences in initial beliefs and capacity, teachers may respond differently to such opportunities. A total of 14 teachers were observed over a three-year period, and two contrasting participants,…

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

  15. How to learn and develop from both good and bad lessons- the 2011Tohoku tsunami case -

    NASA Astrophysics Data System (ADS)

    Sugimoto, Megumi; Okazumi, Toshio

    2013-04-01

    The 2011 Tohoku tsunami revealed Japan has repeated same mistakes in a long tsunami disaster history. After the disaster Japanese remember many old lessons and materials: an oral traditional evacuation method 'Tsunami TENDENKO' which is individual independent quick evacuation, a tsunami historical memorial stone "Don't construct houses below this stone to seaside" in Aneyoshi town Iwate prefecture, Namiwake-shrine naming from the story of protect people from tsunami in Sendai city, and so on. Tohoku area has created various tsunami historical cultures to descendent. Tohoku area had not had a tsunami disaster for 50 years after the 1960 Chilean tsunami. The 2010 Chilean tsunami damaged little fish industry. People gradually lost tsunami disaster awareness. At just the bad time the magnitude (M) 9 scale earthquake attacked Tohoku. It was for our generations an inexperienced scale disaster. People did not make use of the ancestor's lessons to survive. The 2004 Sumatra tsunami attacked just before 7 years ago. The magnitude scale is almost same as M 9 scale. Why didn't Tohoku people and Japanese tsunami experts make use of the lessons? Japanese has a character outside Japan. This lesson shows it is difficult for human being to learn from other countries. As for Three mile island accident case in US, it was same for Japan. To addition to this, there are similar types of living lessons among different hazards. For examples, nuclear power plantations problem occurred both the 2012 Hurricane Sandy in US and the 2011 Tohoku tsunami. Both local people were not informed about the troubles though Oyster creek nuclear power station case in US did not proceed seriously all. Tsunami and Hurricane are different hazard. Each exparts stick to their last. 1. It is difficult for human being to transfer living lessons through next generation over decades. 2. It is difficult for human being to forecast inexperienced events. 3. It is usually underestimated the danger because human being

  16. Lessons Learned

    SciTech Connect

    Dougan, A D; Blair, S

    2006-11-14

    LLNL turned in 5 Declaration Line Items (DLI's) in 2006. Of these, one was declared completed. We made some changes to streamline our process from 2005, used less money, time and fewer team members. This report is a description of what changes we made in 2006 and what we learned. Many of our core review team had changed from last year, including our Laboratory Director, the Facility safety and security representatives, our Division Leader, and the OPSEC Committee Chair. We were able to hand out an AP Manual to some of them, and briefed all newcomers to the AP process. We first went to the OPSEC Committee and explained what the Additional Protocol process would be for 2006 and solicited their help in locating declarable projects. We utilized the 'three questions' from the AP meeting last year. LLNL has no single place to locate all projects at the laboratory. We talked to Resource Managers and key Managers in the Energy and Environment Directorate and in the Nonproliferation Homeland and International Security Directorate to find applicable projects. We also talked to the Principal Investigators who had projects last year. We reviewed a list of CRADA's and LDRD projects given to us by the Laboratory Site Office. Talking to the PI's proved difficult because of vacation or travel schedules. We were never able to locate one PI in town. Fortunately, collateral information allowed us to screen out his project. We had no problems in downloading new versions of the DWA and DDA. It was helpful for both Steve Blair and Arden Dougan to have write privileges. During the time we were working on the project, we had to tag-team the work to allow for travel and vacation schedules. We had some difficulty locating an 'activities block' in the software. This was mentioned as something we needed to fix from our 2005 declaration. Evidently the Activities Block has been removed from the current version of the software. We also had trouble finding the DLI Detail Report, which we included

  17. Cumulative risk assessment lessons learned: a review of case studies and issue papers.

    PubMed

    Gallagher, Sarah S; Rice, Glenn E; Scarano, Louis J; Teuschler, Linda K; Bollweg, George; Martin, Lawrence

    2015-02-01

    Cumulative risk assessments (CRAs) examine potential risks posed by exposure to multiple and sometimes disparate environmental stressors. CRAs are more resource intensive than single chemical assessments, and pose additional challenges and sources of uncertainty. CRAs may examine the impact of several factors on risk, including exposure magnitude and timing, chemical mixture composition, as well as physical, biological, or psychosocial stressors. CRAs are meant to increase the relevance of risk assessments, providing decision makers with information based on real world exposure scenarios that improve the characterization of actual risks and hazards. The U.S. Environmental Protection Agency has evaluated a number of CRAs, performed by or commissioned for the Agency, to seek insight into CRA concepts, methods, and lessons learned. In this article, ten case studies and five issue papers on key CRA topics are examined and a set of lessons learned are identified for CRA implementation. The lessons address the iterative nature of CRAs, importance of considering vulnerability, need for stakeholder engagement, value of a tiered approach, new methods to assess multiroute exposures to chemical mixtures, and the impact of geographical scale on approach and purpose. PMID:25462315

  18. Assessing Stewardship Maturity: Use Case Results and Lessons Learned

    NASA Astrophysics Data System (ADS)

    Ritchey, N. A.; Peng, G.

    2015-12-01

    Assessing the current stewardship maturity state of datasets is an important part of ensuring and improving the way datasets are documented, preserved, stewarded, and disseminated to users. It is a critical step towards meeting U.S. federal regulations, organizational requirements, and user needs, especially in the area of data quality. Stewardship maturity assessment models provide a uniform framework for a consistent assessment within the context of data management in organizations and portfolios, and stewardship of individual datasets, respectively. A key component of dataset and stewardship models maturity is data quality and documentation of the quality. The Data Stewardship Maturity Matrix(DSMM) developed in partnership with NOAA's National Centers of Environmental Information (NCEI) and the Cooperative Institute for Climate and Satellites-North Carolina (CICS-NC) has been used to assess stewardship maturity of highly-utilized datasets within NCEI. Consistent application of the model across heterogenous data types (satellite, in situ, regional, global, etc.) and across multiple levels of stewardship support has proven beneficial but challenging.This presentation will demonstrate the utility of the DSMM through results from use case studies and its application for documenting data quality, indicate the challenges of consistent implementation and provide recommendations on improved application.

  19. A case study of delayed serotonin syndrome: lessons learned.

    PubMed

    Pearce, Shannon; Ahned, Nasiva; Varas, Grace M

    2009-01-01

    Serotonin syndrome is a potentially life-threatening condition that results from excessive serotonin agonism of the central and peripheral nervous system. Though serotonin syndrome is most often associated with ingestion of more than one serotonergic drug, many other mechanisms have been associated with serotonergic excess. This case study presents a 79-year-old African-American female, an assisted living resident, who presented to the emergency department with altered mental status, acute onset of "chills," reduced appetite, urinary incontinence, and an elevated temperature of 103 degrees F (39.4 degrees C). Extensive initial diagnostic findings were negative for urinary tract infection, systemic infection, pneumonia, myocardial infarction, and stroke. Despite aggressive medical management, including intravenous hydration and broad-spectrum antibiotics, the patient continued to become more confused, agitated, and despondent over the subsequent 24 hours. The initial working diagnosis did not include serotonin syndrome, but once other studies did not reveal an etiology of the symptoms and the patient continued to be delirious, paroxetine was discontinued and all symptoms resolved within 48 hours of last dose. Voluntary reporting, postmarketing surveillance, and implementation of well-designed randomized clinical trials are all mechanisms to gather data on serotonin syndrome. These practices will provide future researchers with needed information to solidify diagnostic criteria, educate health care professionals, and safeguard the public against this preventable and potentially lethal drug-drug interaction. PMID:19275460

  20. Project-Based Learning Communities in Developmental Education: A Case Study of Lessons Learned

    ERIC Educational Resources Information Center

    Butler, Alison; Christofili, Monica

    2014-01-01

    This case study tracks the application of project-based learning (PBL) during four separate college terms at Portland Community College in Portland, Oregon. Each term follows a different learning community of first-term college students enrolled in a program of developmental education (DE), reading, writing, math, and college survival and success…

  1. Lessons Learned from Laparoscopic Gastric Banding.

    PubMed

    Broadbent

    1993-11-01

    The author reviews 27 laparoscopic gastric banding operations, of which 19 cases were completed. Of the 27 operations, eight were revisions of earlier laparoscopic banding. The lessons learned from these cases are highlighted. PMID:10757955

  2. Handling of the bariatric patient in critical care: a case study of lessons learned.

    PubMed

    Muir, Marylou; Heese, Gail Archer; McLean, Daria; Bodnar, Sheila; Rock, Betty Lou

    2007-06-01

    Bariatric admissions across the United States (US) are increasing at an alarming rate. The obesity epidemic costs the US health care system $70 billion per year. Many bariatric surgical and medical patients are admitted to critical care units. The mortality risks for these patients compared with non-bariatric patients is up to 2:1. Managing these patients is a challenge to health care nursing personnel. Patient size, care required, equipment technology, availability, and environmental space can increase risk for injury for nursing personnel and patients. The Health Sciences Center in Winnipeg shares a case study of an admission of a 697-lb patient, reviewing lessons learned, techniques, equipment, and difficulties. PMID:17512478

  3. Constellation Program Lessons Learned. Volume 2; Detailed Lessons Learned

    NASA Technical Reports Server (NTRS)

    Rhatigan, Jennifer; Neubek, Deborah J.; Thomas, L. Dale

    2011-01-01

    These lessons learned are part of a suite of hardware, software, test results, designs, knowledge base, and documentation that comprises the legacy of the Constellation Program. The context, summary information, and lessons learned are presented in a factual format, as known and described at the time. While our opinions might be discernable in the context, we have avoided all but factually sustainable statements. Statements should not be viewed as being either positive or negative; their value lies in what we did and what we learned that is worthy of passing on. The lessons include both "dos" and "don ts." In many cases, one person s "do" can be viewed as another person s "don t"; therefore, we have attempted to capture both perspectives when applicable and useful. While Volume I summarizes the views of those who managed the program, this Volume II encompasses the views at the working level, describing how the program challenges manifested in day-to-day activities. Here we see themes that were perhaps hinted at, but not completely addressed, in Volume I: unintended consequences of policies that worked well at higher levels but lacked proper implementation at the working level; long-term effects of the "generation gap" in human space flight development, the need to demonstrate early successes at the expense of thorough planning, and the consequences of problems and challenges not yet addressed because other problems and challenges were more immediate or manifest. Not all lessons learned have the benefit of being operationally vetted, since the program was cancelled shortly after Preliminary Design Review. We avoid making statements about operational consequences (with the exception of testing and test flights that did occur), but we do attempt to provide insight into how operational thinking influenced design and testing. The lessons have been formatted with a description, along with supporting information, a succinct statement of the lesson learned, and

  4. Responding To Infectious Disease: Multiple Cases of Staph Infections in a Rural School District. Lessons Learned From School Crises and Emergencies, Volume 3, Issue 3, 2008

    ERIC Educational Resources Information Center

    US Department of Education, 2008

    2008-01-01

    "Lessons Learned" is a series of publications that are a brief recounting of actual school emergencies and crises. This "Lessons Learned" issue focuses on an incident involving several cases of Methicillin-resistant Staphylococcus aureus (MRSA) at a rural high school. MRSA is a specific strain of Staphylococcus aureus bacteria (often called staph)…

  5. Research Administration: Lessons Learned.

    ERIC Educational Resources Information Center

    Dummer, George H.

    1995-01-01

    The ways in which accountability issues have affected federal-university relationships, particularly in the area of academic research, are examined. Lessons university administrators have learned since issuance of Office of Management and Budget Circular A-21 in 1958, Congressional hearings on the operations of the National Institutes of Health…

  6. DSCOVR Contamination Lessons Learned

    NASA Technical Reports Server (NTRS)

    Graziani, Larissa

    2015-01-01

    The Triana observatory was built at NASA GSFC in the late 1990's, then placed into storage. After approximately ten years it was removed from storage and repurposed as the Deep Space Climate Observatory (DSCOVR). This presentation outlines the contamination control program lessons learned during the integration, test and launch of DSCOVR.

  7. Lessons Learned from Planck

    NASA Astrophysics Data System (ADS)

    Lawrence, Charles; Planck Collaboration Collaboration

    2016-03-01

    Planck's measurements of the microwave sky at seven frequencies spanning 30 to 353 GHz represent an important advance in our understanding of both the cosmic microwave background (CMB) radiation and the properties of astrophysical foregrounds. I will discuss the lessons learned from Planck for future experiments, particularly in the areas of foreground confusion and systematic errors that will set the ultimate limits to what can learned from CMB polarization.

  8. Lessons learned bulletin. Number 2

    SciTech Connect

    Not Available

    1994-05-01

    During the past four years, the Department of Energy -- Savannah River Operations Office and the Westinghouse Savannah River Company (WSRC) Environmental Restoration (ER) Program completed various activities ranging from waste site investigations to closure and post closure projects. Critiques for lessons learned regarding project activities are performed at the completion of each project milestone, and this critique interval allows for frequent recognition of lessons learned. In addition to project related lessons learned, ER also performs lessons learned critiques. T`he Savannah River Site (SRS) also obtains lessons learned information from general industry, commercial nuclear industry, naval nuclear programs, and other DOE sites within the complex. Procedures are approved to administer the lessons learned program, and a database is available to catalog applicable lessons learned regarding environmental remediation, restoration, and administrative activities. ER will continue to use this database as a source of information available to SRS personnel.

  9. Lessons Learned From a Case of Gastric Cancer After Liver Transplantation for Hepatocellular Carcinoma

    PubMed Central

    Yang, Kun; Zhu, Hong; Chen, Chong-Cheng; Wen, Tian-Fu; Zhang, Wei-Han; Liu, Kai; Chen, Xin-Zu; Guo, Dong-Jiao; Zhou, Zong-Guang; Hu, Jian-Kun

    2016-01-01

    Abstract Nowadays, de novo malignancies have become an important cause of death after transplantation. According to the accumulation of cases with liver transplantation, the incidence of de novo gastric cancer is anticipated to increase among liver transplant recipients in the near future, especially in some East Asian countries where both liver diseases requiring liver transplantation and gastric cancer are major burdens. Unfortunately, there is limited information regarding the relationship between de novo gastric cancer and liver transplantation. Herein, we report a case of stage IIIc gastric cancer after liver transplantation for hepatocellular carcinoma, who was successfully treated by radical distal gastrectomy with D2 lymphadenectomy but died 15 months later due to tumor progression. Furthermore, we extract some lessons to learn from the case and review the literatures. The incidence of de novo gastric cancer following liver transplantations is increasing and higher than the general population. Doctors should be vigilant in early detection and control the risk factors causing de novo gastric cancer after liver transplantation. Curative gastrectomy with D2 lymphadenectomy is still the mainstay of treatment for such patients. Preoperative assessments, strict postoperative monitoring, and managements are mandatory. Limited chemotherapy could be given to the patients with high risk of recurrence. Close surveillance, early detection, and treatment of posttransplant cancers are extremely important and essential to improve the survival. PMID:26886605

  10. Pragmatic Meta-Analytic Studies: Learning the Lessons from Naturalistic Evaluations of Multiple Cases

    ERIC Educational Resources Information Center

    Lam, Paul; McNaught, Carmel; Cheng, Kin-Fai

    2008-01-01

    This paper explores the concept of pragmatic meta-analytic studies in eLearning. Much educational technology literature focuses on developers and teachers describing and reflecting on their experiences. Few connections are made between these experiential "stories". The data set is fragmented and offers few generalisable lessons. The field needs…

  11. MSFC Skylab lessons learned

    NASA Technical Reports Server (NTRS)

    1974-01-01

    Key lessons learned during the Skylab Program that could have impact on on-going and future programs are presented. They present early and sometimes subjective opinions; however, they give insights into key areas of concern. These experiences from a complex space program management and space flight serve as an early assessment to provide the most advantage to programs underway. References to other more detailed reports are provided.

  12. Health Information Exchange Implementation: Lessons Learned and Critical Success Factors From a Case Study

    PubMed Central

    2014-01-01

    implementation of a health system to the statewide HIE were found. The most significant perceived success was accomplishing the implementation, although many interviewees also underscored the value of a project champion with decision-making power. In terms of lessons learned, social reasons were found to be very significant motivators for early implementation, frequently outweighing economic motivations. It was clear that understanding the guides early in the project would have mitigated some of the challenges that emerged, and early communication with the electronic health record vendor so that they have a solid understanding of the undertaking was critical. An HIE implementations evaluation framework was found to be useful for assessing challenges, motivations, value propositions for participating, and success factors to consider for future implementations. Conclusions This case study illuminates five critical success factors for implementation of a health system onto a statewide HIE. This study also reveals that organizations have varied motivations and value proposition perceptions for engaging in the exchange of health information, few of which, at the early stages, are economically driven. PMID:25599991

  13. Developing scientific confidence in HTS-derived prediction models: lessons learned from an endocrine case study.

    PubMed

    Cox, Louis Anthony; Popken, Douglas; Marty, M Sue; Rowlands, J Craig; Patlewicz, Grace; Goyak, Katy O; Becker, Richard A

    2014-08-01

    High throughput (HTS) and high content (HCS) screening methods show great promise in changing how hazard and risk assessments are undertaken, but scientific confidence in such methods and associated prediction models needs to be established prior to regulatory use. Using a case study of HTS-derived models for predicting in vivo androgen (A), estrogen (E), thyroid (T) and steroidogenesis (S) endpoints in endocrine screening assays, we compare classification (fitting) models to cross validation (prediction) models. The more robust cross validation models (based on a set of endocrine ToxCast™ assays and guideline in vivo endocrine screening studies) have balanced accuracies from 79% to 85% for A and E, but only 23% to 50% for T and S. Thus, for E and A, HTS results appear promising for initial use in setting priorities for endocrine screening. However, continued research is needed to expand the domain of applicability and to develop more robust HTS/HCS-based prediction models prior to their use in other regulatory applications. Based on the lessons learned, we propose a framework for documenting scientific confidence in HTS assays and the prediction models derived therefrom. The documentation, transparency and the scientific rigor involved in addressing the elements in the proposed Scientific Confidence Framework could aid in discussions and decisions about the prediction accuracy needed for different applications. PMID:24845243

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

  15. GPS lessons learned

    NASA Technical Reports Server (NTRS)

    Heflin, Michael B.

    2003-01-01

    Global geodesy has improved dramatically over the past decade starting with the GPS for IERS and Geodynamics demonstration campaign in 1991 (GIG 91). At the time it took over a week of CPU time to process a network solution based on 21 global receivers and orbit overlaps were in the 40 cm range. Today it is possible to process a network solution based on 80 global receivers in less then one day of CPU time and orbit overlaps are in the 4 cm range. Special methods are under development for efficient processing of increasingly large regional networks which may contain hundreds or thousands of GPS receivers. Along the way there have been many lessons learned about GPS satellites, receivers, monuments, antennas, radomes, analysis, reference frames, error sources, and interpretation. A wide range of scientific disciplines have been impacted including studies of plate motion, post-glacial rebound, seasonal loading, deformation in plate boundary zones, coseismic displacements due to major earthquakes, postseiemic relaxation, and interseismic strain accumulation related to assessment of seismic hazards. Lessons learned will be presented in the context of new dense networks such as the Plate Boundary Observation (PBO).

  16. St. Louis FUSRAP Lessons Learned

    SciTech Connect

    Eberlin, J.; Williams, D.; Mueller, D.

    2003-02-26

    The purpose of this paper is to present lessons learned from fours years' experience conducting Remedial Investigation and Remedial Action activities at the St. Louis Downtown Site (SLDS) under the Formerly Utilized Sites Remedial Action Program (FUSRAP). Many FUSRAP sites are experiencing challenges conducting Remedial Actions within forecasted volume and budget estimates. The St. Louis FUSRAP lessons learned provide insight to options for cost effective remediation at FUSRAP sites. The lessons learned are focused on project planning (budget and schedule), investigation, design, and construction.

  17. What Lessons Can We Learn?

    ERIC Educational Resources Information Center

    Hart, W. A.

    2012-01-01

    It has become commonplace to ask, whenever anything has gone wrong, what lessons can be learned from the experience. But the appearance of open-endedness in that question is misleading: not every answer that we could give to it is acceptable. There are, in the context of such a question, tacit constraints in what counts as a valid lesson to be…

  18. Higher Education ERP: Lessons Learned.

    ERIC Educational Resources Information Center

    Swartz, Dave; Orgill, Ken

    2001-01-01

    Shares experiences and lessons learned by chief information officers of large universities about enterprise resource planning (ERP). Specifically, provides a framework for approaching an ERP that could save universities millions of dollars. (EV)

  19. “Can LUSI be stopped? - A case study and lessons learned from the relief wells”

    NASA Astrophysics Data System (ADS)

    Sutrisna, E.

    2009-12-01

    Since May 2006, in East Java, Indonesia, the LUSI mud volcano has been erupting huge volumes of mixture of predominately mud and water, with little sign of slowing down. It has disrupted social and economic life in this highly populated region. Most geologists believe LUSI is a naturally-occurring mud volcano (MV), like other MV in the Java island of particular interest are the MV along the Watukosek fault, such as, Kalang Anyar, Pulungan, Gunung Anyar, and Socah MV. All of these MV lie in the vicinity of the SSW/NNE trending Watukosek fault that passes through LUSI. The Porong collapse structure is an ancient MV closest to LUSI approx. 7 km away, which on seismic sections demonstrate its complex multi-branching plumbing system. Assuming that the mudflow passed through the wellbore due to an underground blowout, relief wells (RW) were planned to kill the mudflow and carried out in 3 stages, these were: 1. Re-entering the original Banjarpanji-1 (BJP-1) well to obtain accurate survey data so the relief wells could be steered into intersect this original well. 2. Drilling a monitoring well (M-1) to ascertain whether the soil had sufficient strength to support relief wells. 3. Drilling RW-1 and RW-2. Both RW-1 and RW-2 suffered of surface and subsurface problems never achieved their objectives and had to be aborted. Numbers of good lessons were learned from the relief well initiative, such as: 1. No gas or liquid flowed from the wellhead area when it was excavated one month after the eruption started. The wellhead remained intact and totally dead suggesting that the mud flowed to surface through a fault zone or a fracture network instead of up the wellbore. 2. The ‘fish’ in BJP-1 wellbore was found at its original location and not eroded away. This suggests that the mud flow did not pass through the wellbore. 3. The Temperature log showed lower temp. than surface mud temp. The Sonan log response was quiet. These results suggest that there was no near casing mudflow

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

  1. What Is Inside A Lesson Learned?

    NASA Astrophysics Data System (ADS)

    Scheer, S.

    2009-04-01

    The learning of lessons is something that is inherent to normal human behavior. All kind of human interaction experiences critical inspection after a severe or even disastrous event has occurred. Particular inspections have been undertaken in the field of natural disasters. Hence human risk management can continuously be improved according to lessons learned from previous disasters or with the outcome of experience shared with other stakeholders in that field. This paper shows the results of a lessons learned project over the past years: the NEDIES (Natural and Environmental Information Exchange System) deals with lessons learned during the classical risk management phases of prevention, preparedness and response At first glance a lesson is just pure text. Basically it mirrors what has been experienced within a certain context. Having a closer look at a lesson one finds out that a lesson refers to a specific emergency-triggering situation. A situation is more than a simple reference to a hazard: a "rapidly rising lake level" could have more meaning than "a flood". In order to take out positive information it is advisable not only to list up all potential benefits that could be drawn from a lesson; the explicit mentioning of benefits could be helpful in order to prepare further actions beforehand. Moreover one should also consider possible actions to take if that particular situation of the lesson exhibits again or elsewhere. In the case of rapidly rising lake level an a-priori prioritization of response actions could be done. The description of the situation is linked with other characteristics of the lesson; local issues as well as historical considerations can play a role. A flood in a densely populated town can produce different implications than a flood in the countryside. The benefits of the lesson and actions proposed could be linked with experiences made in the past. Other issues concern people involved: the addressees. Typical addressees are local decision

  2. Environmental Restoration Disposal Facility Lessons Learned

    SciTech Connect

    Caulfield, R.

    2012-07-12

    The purpose of lessons learned is to identify insight gained during a project – successes or failures – that can be applied on future projects. Lessons learned can contribute to the overall success of a project by building on approaches that have worked well and avoiding previous mistakes. Below are examples of lessons learned during ERDF’s ARRA-funded expansion project.

  3. Investigating How and What Prospective Teachers Learn through Microteaching Lesson Study

    ERIC Educational Resources Information Center

    Fernandez, Maria Lorelei

    2010-01-01

    Microteaching Lesson Study [MLS] combines elements of Japanese lesson study and microteaching. A case study of MLS was conducted with 18 prospective teachers in an initial course on learning to teach. Various data sources (i.e., pre- and post-lesson plans, MLS lesson plans, videotaped lessons, transcripts of group discussions, observation field…

  4. Lessons learned related to packaging and transportation

    SciTech Connect

    Wallen, C.

    1995-12-31

    The use of lessons learned as a tool for learning from past experiences is well established, especially by many organizations within the nuclear industry. Every person has, at some time, used the principles of lessons learned to adopt good work practices based on their own experiences or the experiences of others. Lessons learned can also help to avoid the recurrence of adverse practices, which is often an area that most lessons-learned programs tend to focus on. This paper will discuss how lessons learned relate to packaging and transportation issues and events experienced at Department of Energy (DOE) facilities. It will also discuss the role performed by the Office of Nuclear and Facility Safety`s Office of Operating Experience Analysis and Feedback in disseminating lessons learned and operating experience feedback to the DOE complex. The central concept of lessons learned is that any organization should be able to learn from its own experiences and events. In addition, organizations should implement methodologies to scan external environments for lessons learned, to analyze and determine the relevance of lessons learned, and to bring about the necessary changes learned from these experiences. With increased concerns toward facility safety, the importance of utilizing the lessons-learned principles and the establishment of lessons-learned programs can not be overstated.

  5. Lessons learned from RTG programs

    NASA Astrophysics Data System (ADS)

    Reinstrom, Robert M.; Cockfield, Robert D.

    1998-01-01

    During the Cassini Radioisotope Thermoelectric Generator (RTG) program, the heritage RTG design was reviewed and modified to incorporate lessons learned. Design changes were made both to resolve problems as they occurred and to correct difficulties noted in earlier missions. Topics addressed in this paper included problems experienced previously at the launch facility in attaching the pressure relief device to the generators, and the open circuit conditions that occurred at times in the resistance temperature device wiring harness. Also discussed is a problem caused by mistakes in software configuration management. How lessons learned refined the RTG design and integration with the spacecraft are discussed and the adopted solutions are described.

  6. Lessons Learned from Safety Events

    SciTech Connect

    Weiner, Steven C.; Fassbender, Linda L.

    2012-11-01

    The Hydrogen Incident Reporting and Lessons Learned website (www.h2incidents.org) was launched in 2006 as a database-driven resource for sharing lessons learned from hydrogen-related safety events to raise safety awareness and encourage knowledge-sharing. The development of this database, its first uses and subsequent enhancements have been described at the Second and Third International Conferences on Hydrogen Safety. [1,2] Since 2009, continuing work has not only highlighted the value of safety lessons learned, but enhanced how the database provides access to another safety knowledge tool, Hydrogen Safety Best Practices (http://h2bestpractices.org). Collaborations with the International Energy Agency (IEA) Hydrogen Implementing Agreement (HIA) Task 19 – Hydrogen Safety and others have enabled the database to capture safety event learnings from around the world. This paper updates recent progress, highlights the new “Lessons Learned Corner” as one means for knowledge-sharing and examines the broader potential for collecting, analyzing and using safety event information.

  7. EMU Lessons Learned Database

    NASA Technical Reports Server (NTRS)

    Matthews, Kevin M., Jr.; Crocker, Lori; Cupples, J. Scott

    2011-01-01

    As manned space exploration takes on the task of traveling beyond low Earth orbit, many problems arise that must be solved in order to make the journey possible. One major task is protecting humans from the harsh space environment. The current method of protecting astronauts during Extravehicular Activity (EVA) is through use of the specially designed Extravehicular Mobility Unit (EMU). As more rigorous EVA conditions need to be endured at new destinations, the suit will need to be tailored and improved in order to accommodate the astronaut. The Objective behind the EMU Lessons Learned Database(LLD) is to be able to create a tool which will assist in the development of next-generation EMUs, along with maintenance and improvement of the current EMU, by compiling data from Failure Investigation and Analysis Reports (FIARs) which have information on past suit failures. FIARs use a system of codes that give more information on the aspects of the failure, but if one is unfamiliar with the EMU they will be unable to decipher the information. A goal of the EMU LLD is to not only compile the information, but to present it in a user-friendly, organized, searchable database accessible to all familiarity levels with the EMU; both newcomers and veterans alike. The EMU LLD originally started as an Excel database, which allowed easy navigation and analysis of the data through pivot charts. Creating an entry requires access to the Problem Reporting And Corrective Action database (PRACA), which contains the original FIAR data for all hardware. FIAR data are then transferred to, defined, and formatted in the LLD. Work is being done to create a web-based version of the LLD in order to increase accessibility to all of Johnson Space Center (JSC), which includes converting entries from Excel to the HTML format. FIARs related to the EMU have been completed in the Excel version, and now focus has shifted to expanding FIAR data in the LLD to include EVA tools and support hardware such as

  8. Ecological risk assessment: Lessons learned

    SciTech Connect

    DeShields, B.R.; Stelljes, M.E.; Hawkins, E.T.; Alsop, W.R.

    1995-12-31

    On the basis of experience with ecological risk assessments and regulatory involvement in the process, a number of lessons can be learned relating to design, implementation, and reporting of ecological risk assessments. A number of case studies will be presented in order to evaluate the advantages and disadvantages of different approaches. Issues surrounding the selection of assessment and measurement endpoints, receptors, accuracy of models when compared with field data, bioavailability of chemicals, selection of appropriate reference sites, availability of relevant toxicological data, utility of bioassays, and accounting for temporal and seasonal variability, species adaptation, and ecological relevance will be examined. In addition, effective ways of dealing with limitations such as duration and cost of the assessments will be evaluated. Case studies ranging from large, complex Superfund sites to small, relatively simplistic sites will be included. By scrutinizing the approaches used and the outcomes of these case studies, insight can be gained that will allow risk assessors to deal with limitations and to focus future efforts to provide useful and relevant information and sound scientifically-based results.

  9. Constellation Lessons Learned Executive Summary

    NASA Technical Reports Server (NTRS)

    Thomas, L. Dale; Neubek, Deb

    2011-01-01

    This slide presentation reviews the lessons learned from the Constellation Program (CxP) and identified several factors that contributed to the inability of the CxP to meet the cost and schedule commitments. The review includes a significant section on the context in which the CxP operated since new programs are likely to experience the same constraints.

  10. NASA Materials Related Lessons Learned

    NASA Technical Reports Server (NTRS)

    Garcia, Danny; Gill, Paul S.; Vaughan, William W.

    2003-01-01

    Lessons Learned have been the basis for our accomplishments throughout the ages. They have been passed down from father to son, mother to daughter, teacher to pupil, and older to younger worker. Lessons Learned have also been the basis for the nation s accomplishments for more than 200 years. Both government and industry 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. Through the knowledge captured and recorded in Lessons Learned from more than 80 years of flight in the Earth s atmosphere, NASA s materials researchers are constantly working to develop stronger, lighter, and more durable materials that can withstand the challenges of space. The Agency s talented materials engineers and scientists continue to build on that rich tradition by using the knowledge and wisdom gained from past experiences to create futuristic materials and technologies that will be used in the next generation of advanced spacecraft and satellites that may one day enable mankind to land men on another planet or explore our nearest star. These same materials may also have application here on Earth to make commercial aircraft more economical to build and fly. With the explosion in technical accomplishments over the last decade, the ability to capture knowledge and have the capability to rapidly communicate this knowledge at lightning speed throughout an organization like NASA has become critical. Use of Lessons Learned is a principal component of an organizational culture committed to continuous improvement.

  11. NASA Materials Related Lessons Learned

    NASA Technical Reports Server (NTRS)

    Garcia, Danny; Gill, Paul S.; Vaughan, William W.; Parker, Nelson C. (Technical Monitor)

    2002-01-01

    Lessons Learned have been the basis for our accomplishments throughout the ages. They have been passed down from father to son, mother to daughter, teacher to pupil, and older to younger worker. Lessons Learned have also been the basis for the nation's accomplishments for more than 200 years. Both government and industry 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. Through the knowledge captured and recorded in Lessons Learned from more than 80 years of flight in the Earth's atmosphere, NASA's materials researchers are constantly working to develop stronger, lighter, and more durable materials that can withstand the challenges of space. The Agency's talented materials engineers and scientists continue to build on that rich tradition by using the knowledge and wisdom gained from past experiences to create futurist materials and technologies that will be used in the next generation of advanced spacecraft and satellites that may one day enable mankind to land men on another planet or explore our nearest star. These same materials may also have application here on Earth to make commercial aircraft more economical to build and fly. With the explosion in technical accomplishments over the last decade, the ability to capture knowledge and have the capability to rapidly communicate this knowledge at lightning speed throughout an organization like NASA has become critical. Use of Lessons Learned is a principal component of an organizational culture committed to continuous improvement.

  12. A Lesson Learned through Gaming

    ERIC Educational Resources Information Center

    Kovalik, Ludovic M.; Kovalik, Doina L.

    2008-01-01

    This article describes an educational card game the objective of which is to raise students' awareness of the need for clarity, structure, and organization in all everyday activities of humans. Although the game as such was played in freshman composition, therefore addressing the immediate needs of that particular class, the lesson learned through…

  13. Lessons learned in crisis management.

    PubMed

    Olson, Chris

    2014-01-01

    This paper will explore lessons learned following a series of natural and man-made disasters affecting the Massachusetts Mutual Life Insurance Company and/or its subsidiaries. The company employs a team of certified continuity professionals who are charged with overseeing resilience on behalf of the enterprise and leading recovery activities wherever and whenever necessary. PMID:24578026

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

  15. Development of a State Machine Sequencer for the Keck Interferometer: Evolution, Development and Lessons Learned using a CASE Tool Approach

    NASA Technical Reports Server (NTRS)

    Rede, Leonard J.; Booth, Andrew; Hsieh, Jonathon; Summer, Kellee

    2004-01-01

    This paper presents a discussion of the evolution of a sequencer from a simple EPICS (Experimental Physics and Industrial Control System) based sequencer into a complex implementation designed utilizing UML (Unified Modeling Language) methodologies and a CASE (Computer Aided Software Engineering) tool approach. The main purpose of the sequencer (called the IF Sequencer) is to provide overall control of the Keck Interferometer to enable science operations be carried out by a single operator (and/or observer). The interferometer links the two 10m telescopes of the W. M. Keck Observatory at Mauna Kea, Hawaii. The IF Sequencer is a high-level, multi-threaded, Hare1 finite state machine, software program designed to orchestrate several lower-level hardware and software hard real time subsystems that must perform their work in a specific and sequential order. The sequencing need not be done in hard real-time. Each state machine thread commands either a high-speed real-time multiple mode embedded controller via CORB A, or slower controllers via EPICS Channel Access interfaces. The overall operation of the system is simplified by the automation. The UML is discussed and our use of it to implement the sequencer is presented. The decision to use the Rhapsody product as our CASE tool is explained and reflected upon. Most importantly, a section on lessons learned is presented and the difficulty of integrating CASE tool automatically generated C++ code into a large control system consisting of multiple infrastructures is presented.

  16. Case study: the Argentina Road Safety Project: lessons learned for the decade of action for road safety, 2011-2020.

    PubMed

    Raffo, Veronica; Bliss, Tony; Shotten, Marc; Sleet, David; Blanchard, Claire

    2013-12-01

    This case study of the Argentina Road Safety Project demonstrates how the application of World Bank road safety project guidelines focused on institution building can accelerate knowledge transfer, scale up investment and improve the focus on results. The case study highlights road safety as a development priority and outlines World Bank initiatives addressing the implementation of the World Report on Road Traffic Injury's recommendations and the subsequent launch of the Decade of Action for Road Safety, from 2011-2020. The case study emphasizes the vital role played by the lead agency in ensuring sustainable road safety improvements and promoting the shift to a 'Safe System' approach, which necessitated the strengthening of all elements of the road safety management system. It summarizes road safety performance and institutional initiatives in Argentina leading up to the preparation and implementation of the project. We describe the project's development objectives, financing arrangements, specific components and investment staging. Finally, we discuss its innovative features and lessons learned, and present a set of supplementary guidelines, both to assist multilateral development banks and their clients with future road safety initiatives, and to encourage better linkages between the health and transportation sectors supporting them. PMID:24722740

  17. Lessons Learned on Communication and Engagement for Educator Evaluation: Colorado Case Study. Policy-to-Practice Brief

    ERIC Educational Resources Information Center

    Behrstock-Sherratt, Ellen; Biggers, Kietha; Fetters, Jenni

    2012-01-01

    With many efforts underway across the United States, state education agency (SEA) leaders have the opportunity to utilize the expertise of their contacts in other SEAs and regional comprehensive centers (RCCs) in their region and throughout the country to exchange ideas and share the lessons they have learned about involving stakeholders in…

  18. A Case for Culturally Relevant Teaching in Science Education and Lessons Learned for Teacher Education

    ERIC Educational Resources Information Center

    Mensah, Felicia Moore

    2011-01-01

    In this article, the researcher discusses three elementary pre-service teachers' experiences in co-planning and co-teaching a Pollution Unit in a 4th-5th grade science classroom in New York City. The study makes use of microteaching papers, lesson plans, researcher classroom observations, interviews, and informal conversations to elicit lessons…

  19. Shuttle Lesson Learned - Toxicology

    NASA Technical Reports Server (NTRS)

    James, John T.

    2010-01-01

    This is a script for a video about toxicology and the space shuttle. The first segment is deals with dust in the space vehicle. The next segment will be about archival samples. Then we'll look at real time on-board analyzers that give us a lot of capability in terms of monitoring for combustion products and the ability to monitor volatile organics on the station. Finally we will look at other issues that are about setting limits and dealing with ground based lessons that pertain to toxicology.

  20. Safeguards Culture: Lessons Learned

    SciTech Connect

    Mladineo, Stephen V.

    2009-05-27

    Abstract: At the 2005 INMM/ESARDA Workshop in Santa Fe, New Mexico, I presented a paper entitled “Changing the Safeguards Culture: Broader Perspectives and Challenges.” That paper described a set of theoretical models that can be used as a basis for evaluating changes to safeguards culture. This paper builds on that theoretical discussion to address practical methods for influencing culture. It takes lessons from methods used to influence change in safety culture and security culture, and examines the applicability of these lessons to changing safeguards culture. Paper: At the 2005 INMM/ESARDA Workshop on “Changing the Safeguards Culture: Broader Perspectives and Challenges,” in Santa Fe, New Mexico, I presented a paper entitled “Changing the Safeguards Culture: Broader Perspectives and Challenges.” That paper, coauthored by Karyn R. Durbin and Andrew Van Duzer, described a set of theoretical models that can be used as a basis for evaluating changes to safeguards culture. This paper updates that theoretical discussion, and seeks to address practical methods for influencing culture. It takes lessons from methods used to influence change in safety culture and security culture, and examines the applicability of these lessons to changing safeguards culture. Implicit in this discussion is an understanding that improving a culture is not an end in itself, but is one method of improving the underlying discipline, that is safety, security, or safeguards. Culture can be defined as a way of life, or general customs and beliefs of a particular group of people at a particular time. There are internationally accepted definitions of safety culture and nuclear security culture. As yet, there is no official agreed upon definition of safeguards culture. At the end of the paper I will propose my definition. At the Santa Fe Workshop the summary by the Co-Chairs of Working Group 1, “The Further Evolution of Safeguards,” noted: “It is clear that ‘safeguards culture

  1. Assessing Learning Communities: Lessons Learned.

    ERIC Educational Resources Information Center

    Mullen, Debra

    2001-01-01

    Discusses how to develop an effective assessment process for learning communities, including initial considerations, the value of student involvement, questions guiding the study, data management, and considerations for future studies. (EV)

  2. System safety management lessons learned

    SciTech Connect

    Piatt, J.A.

    1989-05-01

    The Assistant Secretary of the Army for Research, Development and Acquisition directed the Army Safety Center to provide an audit of the causes of accidents and safety of use restrictions on recently fielded systems by tracking residual hazards back through the acquisition process. The objective was to develop ''lessons learned'' that could be applied to the acquisition process to minimize mishaps in fielded systems. System safety management lessons learned are defined as Army practices or policies, derived from past successes and failures, that are expected to be effective in eliminating or reducing specific systemic causes of residual hazards. They are broadly applicable and supportive of the Army structure and acquisition objectives. 29 refs., 7 figs.

  3. Lessons learned from RTG programs

    SciTech Connect

    Reinstrom, R.M.; Cockfield, R.D.

    1998-01-01

    During the Cassini Radioisotope Thermoelectric Generator (RTG) program, the heritage RTG design was reviewed and modified to incorporate lessons learned. Design changes were made both to resolve problems as they occurred and to correct difficulties noted in earlier missions. Topics addressed in this paper included problems experienced previously at the launch facility in attaching the pressure relief device to the generators, and the open circuit conditions that occurred at times in the resistance temperature device wiring harness. Also discussed is a problem caused by mistakes in software configuration management. How lessons learned refined the RTG design and integration with the spacecraft are discussed and the adopted solutions are described. {copyright} {ital 1998 Lockheed Martin Missles and Space, reproduced with permission.}

  4. Special lessons learned from Iraq.

    PubMed

    Sebesta, James

    2006-06-01

    Operation Iraqi Freedom is the largest casualty-producing conflict this nation's military has faced since Vietnam. Medical departments from the three services have done an extraordinary job reacting to the ever-changing landscape of modern warfare and the devastating injuries produced. From the revamping of prehospital care to new applications of damage-control surgery, challenges have erupted, lessons have been learned, and lives are being saved. PMID:16781278

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

  6. Software Carpentry: lessons learned

    PubMed Central

    Wilson, Greg

    2016-01-01

    Since its start in 1998, Software Carpentry has evolved from a week-long training course at the US national laboratories into a worldwide volunteer effort to improve researchers' computing skills. This paper explains what we have learned along the way, the challenges we now face, and our plans for the future. PMID:24715981

  7. Translating evidence into policy: lessons learned from the case of lowering the legal blood alcohol limit for drivers.

    PubMed

    Mercer, Shawna L; Sleet, David A; Elder, Randy W; Cole, Krista Hopkins; Shults, Ruth A; Nichols, James L

    2010-06-01

    This case study examines the translation of evidence on the effectiveness of laws to reduce the blood alcohol concentration (BAC) of drivers into policy. It was reconstructed through discussions among individuals involved in the processes as well as a review of documentation and feedback on oral presentations. The Centers for Disease Control and Prevention collaborated extensively with federal and non-federal partners and stakeholders in conducting a rigorous systematic review, using the processes of the Guide to Community Preventive Services to evaluate the body of empirical evidence on 0.08% BAC laws. The timely dissemination of the findings and related policy recommendations-made by the independent Task Force on Community Preventive Services-to Congress very likely contributed to the inclusion of strong incentives to States to adopt 0.08 BAC laws by October 2003. Subsequent dissemination to partners and stakeholders informed decision-making about support for state legislative and policy action. This case study suggests the value of: clearly outlining the relationships between health problems, interventions and outcomes; systematically assessing and synthesizing the evidence; using a credible group and rigorous process to assess the evidence; having an impartial body make specific policy recommendations on the basis of the evidence; being ready to capitalize in briefly opening policy windows; engaging key partners and stakeholders throughout the production and dissemination of the evidence and recommendations; undertaking personalized, targeted and compelling dissemination of the evidence and recommendations; involving multiple stakeholders in encouraging uptake and adherence of policy recommendations; and addressing sustainability. These lessons learned may help others working to translate evidence into policy. PMID:20470967

  8. Lessons from an Experiential Learning Process: The Case of Cowpea Farmer Field Schools in Ghana

    ERIC Educational Resources Information Center

    Nederlof, E. Suzanne; Odonkor, Ezekiehl N.

    2006-01-01

    The Farmer Field School (FFS) is a form of adult education using experiential learning methods, aimed at building farmers' decision-making capacity and expertise. The National Research Institute in West Africa conducted FFS in cowpea cultivation and we use this experience to analyse the implementation of the FFS approach. How does it work in…

  9. THE INTEGRATION OF ENGINEERED AND INSTITUTIONAL CONTROLS: A CASE STUDY APPROACH WITH LESSONS LEARNED FROM PREVIOUSLY CLOSED SITES

    SciTech Connect

    Kevin M. Kostelnik; James H. Clarke; Jerry L. Harbour

    2005-02-01

    Environmental remediation efforts that are underway at hundreds of contaminated sites in the United States will not be able to remediate large portions of those sites to conditions that would permit unrestricted access. Rather, large volumes of waste materials, contaminated soils and cleanup residuals will have to be isolated either in place or in new, often on-site, disposal cells with long term monitoring, maintenance and institutional control needs. The challenge continues to be to provide engineering systems and controls that can ensure the protection of public health and the environment over very long time horizons (hundreds to perhaps thousands of years) with minimal intervention. Effective long term management of legacy hazardous and nuclear waste requires an integrated approach that addresses both the engineered containment and control system itself and the institutional controls and other responsibilities that are needed. Decisions concerning system design, monitoring and maintenance, and the institutional controls that will be employed are best done through a "risk-nformed, performance-based" approach. Such an approach should incorporate an analysis of potential "failure" modes and consequences for all important system features, together with lessons learned from experience with systems already in place. The authors will present the preliminary results of a case study approach that included several sites where contamination isolation systems including institutional controls have been implemented. The results are being used together with failure trees and logic diagrams that have been developed for both the engineered barriers and the institutional controls. The use of these analytical tools to evaluate the potential for different levels of failure and associated consequences will be discussed. Of special interest is the robustness of different approaches to providing long-term protection through redundancy and defense in depth.

  10. Lessons Learned from the Parents Matter! Program

    ERIC Educational Resources Information Center

    Long, Nicholas; Miller, Kim S.; Jackson, Leslie C.; Lindner, Gretchen K.; Hunt, Regina G.; Robinson, A. Doris; Goldsby, W. Dean; Armistead, Lisa P.

    2004-01-01

    We present a discussion of some of the lessons the investigators learned during the development and implementation phases of the Parents Matter! Program (PMP). Lessons were learned that are relevant to various groups involved in large scale, multi-site, community-based intervention studies: investigators, community leaders, community members,…

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

  12. A Singapore Case of Lesson Study

    ERIC Educational Resources Information Center

    Cheng, Lu Pien; Yee, Lee Peng

    2012-01-01

    In this article, we present a case study of six Singaporean elementary school teachers working in a Lesson Study team that prepared them for problem solving instruction. The Lesson Study process included preparing, observing, and critiquing mathematics lessons in the context of solving fractions tasks. By conducting Lesson Study, we anticipated…

  13. Review of 500 single incision laparoscopic colorectal surgery cases - Lessons learned

    PubMed Central

    Keller, Deborah S; Flores-Gonzalez, Juan R; Ibarra, Sergio; Haas, Eric M

    2016-01-01

    Single incision laparoscopic surgery (SILS) is a minimally invasive platform with specific benefits over traditional multiport laparoscopic surgery. The safety and feasibility of SILS has been proven, and the applications continue to grow with experience. After 500 cases at a high-volume, single-institution, we were able to standardize instrumentation and operative steps, as well as develop adaptations in technique to help overcome technical and ergonomic challenges. These technical adaptations have allowed the successful application of SILS to technically difficult patient populations, such as pelvic cases, inflammatory bowel disease cases, and high body mass index patients. This review is a frame of reference for the application and wider integration of the single incision laparoscopic platform in colorectal surgery. PMID:26811615

  14. Case study: a midclerkship crisis-lessons learned from advising a medical student with career indecision.

    PubMed

    Levine, Rachel B; Cayea, Danelle; Shochet, Robert B; Wright, Scott M

    2010-04-01

    Advising medical students is a challenging task. Faculty who serve as advisors for students require specific skills and knowledge to do their jobs effectively. Career choice is one of the many complex issues about which medical students often seek assistance from a faculty advisor. The authors present a case of a third-year medical student with career indecision, with a focus on the various factors that may be influencing her thinking about career choice. Key advising principles are provided as a framework for the discussion of the case and include reflection, self-disclosure, active listening, support and advocacy, confidentiality, and problem solving. These principles were developed as part of the Advising Case Conference series of the Johns Hopkins University School of Medicine Colleges Advisory Program. Emergent themes from the case included a student's evolving professional identity, a student's distress and burnout, lifestyle considerations, and advisor bias and self-awareness. The authors propose reflective questions to enhance meaningful discussions between the advisor and student and assist in problem solving. Many of these questions, together with the key advising principles, are generalizable to a variety of advising scenarios between advisors and learners at all levels of training. PMID:20354382

  15. Lessons Learned from a Four Year Case Study of Preparing Teachers for Inner-City Schools.

    ERIC Educational Resources Information Center

    Stallings, Jane

    A 4-year case study was done of a partnership program between the Houston (Texas) Independent School District and Texas A&M University's College of Education (College Station) designed to prepare student teachers for work in inner-city public schools. The two institutions worked together through four collaborative decision-making councils to form…

  16. Statistical Downscaling: Lessons Learned

    NASA Astrophysics Data System (ADS)

    Walton, D.; Hall, A. D.; Sun, F.

    2013-12-01

    In this study, we examine ways to improve statistical downscaling of general circulation model (GCM) output. Why do we downscale GCM output? GCMs have low resolution, so they cannot represent local dynamics and topographic effects that cause spatial heterogeneity in the regional climate change signal. Statistical downscaling recovers fine-scale information by utilizing relationships between the large-scale and fine-scale signals to bridge this gap. In theory, the downscaled climate change signal is more credible and accurate than its GCM counterpart, but in practice, there may be little improvement. Here, we tackle the practical problems that arise in statistical downscaling, using temperature change over the Los Angeles region as a test case. This region is an ideal place to apply downscaling since its complex topography and shoreline are poorly simulated by GCMs. By comparing two popular statistical downscaling methods and one dynamical downscaling method, we identify issues with statistically downscaled climate change signals and develop ways to fix them. We focus on scale mismatch, domain of influence, and other problems - many of which users may be unaware of - and discuss practical solutions.

  17. Special Session: Lessons Learned From the L'Aquila Earthquake Case

    NASA Astrophysics Data System (ADS)

    Ambrogio, Olivia

    2013-01-01

    The verdict and prison sentences, delivered on 22 October 2012, that found six Italian scientists and one government official guilty of manslaughter in connection with the 2009 L'Aquila earthquake shocked the scientific community worldwide. A late-breaking special session co-convened by John Bates, at the National Climatic Data Center of the National Oceanic and Atmospheric Administration, and Stephen Sparks, University of Bristol, was added to the Fall Meeting schedule to address this case and to discuss the complex process of assessing and communicating the risks associated with natural hazards.

  18. Interpreting risk as evidence of causality: lessons learned from a legal case to determine medical malpractice.

    PubMed

    Mercuri, Mathew; Baigrie, Brian S

    2016-08-01

    Translating risk estimates derived from epidemiologic study into evidence of causality for a particular patient is problematic. The difficulty of this process is not unique to the medical context; rather, courts are also challenged with the task of using risk estimates to infer evidence of cause in particular cases. Thus, an examination of how this is done in a legal context might provide insight into when and how it is appropriate to use risk information as evidence of cause in a medical context. A careful study of the case of Goodman v. Viljoen, a medical malpractice suit litigated in the Ontario Superior Court of Justice in 2011, reveals different approaches to how risk information is used as or might be considered a substitute for evidence of causation, and the pitfalls associated with these approaches. Achieving statistical thresholds, specifically minimizing the probability of falsely rejecting the null hypothesis, and exceeding a relative risk of 2, plays a significant role in establishing causality of the particular in the legal setting. However, providing a reasonable explanation or establishing "biological plausibility" of the causal association also seems important, and (to some) may even take precedent over statistical thresholds for a given context. PMID:27305892

  19. A typical case of myoclonic epilepsy with ragged red fibers (MERRF) and the lessons learned

    PubMed Central

    Chandra, SR; Issac, TG; Gayathri, N; Gupta, N; Abbas, MM

    2015-01-01

    Mitochondrial diseases have a special predilection to involve the brain in view of its high metabolic demand and the tendency for the formation of excitatory neurotransmitters when there is deficiency of intracellular ATP. These diseases have a great phenotypic variation and need a high degree of suspicion. However, some specific syndromes are well defined, both genotypically and phenotypically. Some of the drugs are potentially fatal mitochondrial poisons and an insight into that may be lifesaving as well as prevent serious morbidities. We report a typical case of myoclonic epilepsy with ragged red fibers (MERRF) with classical phenotype and genotype. There was rapid multiaxial deterioration with the introduction of sodium valproate which partly reversed on introducing mitochondrial cocktail and withdrawal of the offending drug. Sodium valproate, phenobarbitone, chloramphenicol and many anti-viral agents are mitochondrial poisons that increase the morbidity and mortality in patients with mitochondrial disease. More harm to the patient can be avoided with insight into this information. PMID:26119441

  20. Lessons Learned and Questions Raised by an Atypical Case of Clozapine-Induced Myocarditis.

    PubMed

    Earnshaw, Charles H; Powell, Lucy; Haeney, Owen

    2016-01-01

    A Caucasian male in his early twenties suffering from treatment resistant schizophrenia was started on clozapine. After three days he developed tachycardia, a common side effect of clozapine induction. He had one temperature spike (38.9°C) on day ten after induction but remained clinically well. An ECG and blood tests were normal. Due to persistent tachycardia and an episode of collapse whilst seated on day 12, he was admitted to hospital for further investigation. A diagnosis of myocarditis was confirmed as a result of elevated cardiac enzyme levels and an echocardiogram. Following withdrawal of clozapine, supportive management, and initiation of cardiac medication, the patient made a successful recovery. He will be followed up with the cardiology team to ensure that his heart function returns to normal. Given the incidence of clozapine-induced myocarditis, the associated mortality risk, and diagnostic difficulties, this case raises questions about whether a formal system for identifying myocarditis should be adopted. PMID:27478671

  1. Lessons to be learned: a case study approach--acute appendicitis masquerading as macroamylasaemia.

    PubMed

    Ganesh, Muniappan; Salam, Imroz

    2008-05-01

    Macroamylasaemia is a condition in which serum amylase is elevated in the presence of a low to normal urinary amylase and normal renal function. It is rare but can masquerade as other clinical disorders. Discussed here is a case report of a patient who presented initially with abdominal pain (later recognized as being due to gangrenous appendicitis) and in whom there was a very high serum amylase level, leading to an erroneous initial diagnosis and management as acute pancreatitis. The CT scan of the abdomen was normal without any evidence of pancreatitis. Subsequently, the renal amylase:creatinine clearance ratio (C(am)/C(cr)) was found to be low, being characteristic and diagnostic of macroamylasaemia; the latter was, in turn, the cause for the elevated serum amylase level. The underlying macroamylasaemia had thus masqueraded as pancreatitis. The patient underwent appendicectomy and hence made an excellent recovery. It is vitally important to recognize this condition in order to avoid both an incorrect diagnosis and inappropriate treatment/management. PMID:18595630

  2. A typical case of myoclonic epilepsy with ragged red fibers (MERRF) and the lessons learned.

    PubMed

    Chandra, S R; Issac, T G; Gayathri, N; Gupta, N; Abbas, M M

    2015-01-01

    Mitochondrial diseases have a special predilection to involve the brain in view of its high metabolic demand and the tendency for the formation of excitatory neurotransmitters when there is deficiency of intracellular ATP. These diseases have a great phenotypic variation and need a high degree of suspicion. However, some specific syndromes are well defined, both genotypically and phenotypically. Some of the drugs are potentially fatal mitochondrial poisons and an insight into that may be lifesaving as well as prevent serious morbidities.We report a typical case of myoclonic epilepsy with ragged red fibers (MERRF) with classical phenotype and genotype. There was rapid multiaxial deterioration with the introduction of sodium valproate which partly reversed on introducing mitochondrial cocktail and withdrawal of the offending drug.Sodium valproate, phenobarbitone, chloramphenicol and many anti-viral agents are mitochondrial poisons that increase the morbidity and mortality in patients with mitochondrial disease. More harm to the patient can be avoided with insight into this information. PMID:26119441

  3. Implementing US Department of Energy lessons learned programs. Volume 2

    SciTech Connect

    1995-08-01

    The DOE Lessons Learned Handbook is a two-volume publication developed to supplement the DOE Lessons Learned Standard (DOE-STD-7501-95) with information that will organizations in developing or improving their lessons learned programs. Volume 1 includes greater detail than the Standard in areas such as identification and documentation of lessons learned; it also contains sections on specific processes such as training and performance measurement. Volume 2 (this document) contains examples of program documents developed by existing lessons learned programs as well as communications material, functional categories, transmittal documents, sources of professional and industry lessons learned, and frequently asked questions about the Lessons Learned List Service.

  4. Team Collaboration: Lessons Learned Report

    NASA Technical Reports Server (NTRS)

    Arterberrie, Rhonda Y.; Eubanks, Steven W.; Kay, Dennis R.; Prahst, Stephen E.; Wenner, David P.

    2005-01-01

    An Agency team collaboration pilot was conducted from July 2002 until June 2003 and then extended for an additional year. The objective of the pilot was to assess the value of collaboration tools and adoption processes as applied to NASA teams. In an effort to share knowledge and experiences, the lessons that have been learned thus far are documented in this report. Overall, the pilot has been successful. An entire system has been piloted - tools, adoption, and support. The pilot consisted of two collaboration tools, a team space and a virtual team meeting capability. Of the two tools that were evaluated, the team meeting tool has been more widely accepted. Though the team space tool has been met with a lesser degree of acceptance, the need for such a tool in the NASA environment has been evidenced. Both adoption techniques and support were carefully developed and implemented in a way that has been well received by the pilot participant community.

  5. Psychiatric lessons learned in Kandahar.

    PubMed

    Jetly, Rakesh

    2011-12-01

    Not since the Korean War have the Canadian Forces engaged in combat missions like those in Afghanistan. Combat, asymmetric warfare, violent insurgency and the constant threat of improvised explosive devices all contribute to the psychological stressors experienced by Canadian soldiers. Mental health teams deployed with the soldiers and provided assessment, treatment and education. Lessons learned included refuting the myth that all psychological disorders would be related to trauma; confirming that most patients do well after exposure to trauma; confirming that treating disorders in a war zone requires flexible and creative adaptation of civilian treatment guidelines; and confirming that in a combat mission mental health practice is not limited to the clinical setting. PMID:22099328

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

  7. Lessons learned in organizing for performance

    SciTech Connect

    Long, R.L.

    1993-12-31

    Lessons learned from the Three Mile Island accident are described. The effectiveness of the General Public Utilities Corporation in the decontamination/support issues and restart of the three mile unit-1 reactor, is discussed.

  8. Science and Sandy: Lessons Learned

    NASA Astrophysics Data System (ADS)

    Werner, K.

    2013-12-01

    Following Hurricane Sandy's impact on the mid-Atlantic region, President Obama established a Task Force to '...ensure that the Federal Government continues to provide appropriate resources to support affected State, local, and tribal communities to improve the region's resilience, health, and prosperity by building for the future.' The author was detailed from NOAA to the Task Force between January and June 2013. As the Task Force and others began to take stock of the region's needs and develop plans to address them, many diverse approaches emerged from different areas of expertise including: infrastructure, management and construction, housing, public health, and others. Decision making in this environment was complex with many interests and variables to consider and balance. Although often relevant, science and technical expertise was not always at the forefront of this process. This talk describes the author's experience with the Sandy Task Force focusing on organizing scientific expertise to support the work of the Task Force. This includes a description of federal activity supporting Sandy recovery efforts, the role of the Task Force, and lessons learned from developing a science support function within the Task Force.

  9. FRMAC-93 lessons learned report

    SciTech Connect

    Kerns, K.C.

    1994-03-01

    FRMAC-93 simulated a radiological accident at the Fort Calhoun nuclear power plant, 25 miles north of Omaha, Nebraska. The exercise involved the state Iowa and Nebraska, NRC as the lead Federal agency, FRMAC (Federal Radiological Monitoring and Assessment Center), and several federal agencies with statutory emergency responsibility. FRMAC-93 was a major 2-day field exercise designed to determine the effectiveness, coordination, and operations of a DOE-managed FRMAC. Other objectives were to ensure that appropriate priorities were established and assistance was provided to the states and the lead Federal agency by FRMAC. Day 1 involved the Fort Calhoun evaluated plume phase exercise. On Day 2, the flow of data, which was slow initially, improved so that confidence of states and other federal responders in FRMAC support capabilities was high. The impact and lessons learned from FRMAC-93 provided the necessary impetus to make organizational and operational changes to the FRMAC program, which were put into effect in the DOE exercise FREMONT at Hanford 3 months later.

  10. Huygens Highlights and lessons learned

    NASA Astrophysics Data System (ADS)

    Lebreton*, Jean-Pierre

    2015-04-01

    Ten years ago, on 14 January 2005, the Huygens Probe parachuted down to the surface of Titan, Saturn's largest moon. Huygens is part of the international Cassini/Huygens mission, a joint endeavor of NASA, the European Space Agency, and Agenzia Spaziale Italiana. Cassini/Huygens, comprising the NASA-provided Saturn Orbiter and the ESA-provided Huygens probe, was launched in October 1997. It arrived at Saturn in early July 2004. Huygens was released on the 3rd orbit around Saturn. It made measurements during the hypersonic entry, the descent, and for more than one hour on the surface. Unique in situ characterization of the atmosphere along the entry and descent trajectory and of the surface at the landing site was provided, revealing that many Earth-like processes were at work on Titan, a very fascinating methane world. Huygens observations also allowed inferring the ice crust thickness, hence an estimation of the depth of the icy crust/liquid water ocean interface. Huygens measurements are also used as ground-truth of the measurements made by the orbiter during Titan flybys. In this presentation, after a brief review of the major mission milestones, Huygens achievements are discussed in the context of the progress made in our understanding of Titan during the Cassini/Huygens mission. Lessons learned for the future in situ exploration of Titan are addressed. * Most of this work was performed while at ESA/ESTEC, Noordwijk, The Netherlands

  11. Extension Learning Exchange: Lessons from Nicaragua

    ERIC Educational Resources Information Center

    Treadwell, Paul; Lachapelle, Paul; Howe, Rod

    2013-01-01

    There is a clear need to support global professional development, international education, and collaborative learning opportunities in Extension. The program described here established an international learning exchange in Nicaragua to lead to global professional development and future international collaboration. The primary lessons and outcomes…

  12. Logistics Lessons Learned in NASA Space Flight

    NASA Technical Reports Server (NTRS)

    Evans, William A.; DeWeck, Olivier; Laufer, Deanna; Shull, Sarah

    2006-01-01

    The Vision for Space Exploration sets out a number of goals, involving both strategic and tactical objectives. These include returning the Space Shuttle to flight, completing the International Space Station, and conducting human expeditions to the Moon by 2020. Each of these goals has profound logistics implications. In the consideration of these objectives,a need for a study on NASA logistics lessons learned was recognized. The study endeavors to identify both needs for space exploration and challenges in the development of past logistics architectures, as well as in the design of space systems. This study may also be appropriately applied as guidance in the development of an integrated logistics architecture for future human missions to the Moon and Mars. This report first summarizes current logistics practices for the Space Shuttle Program (SSP) and the International Space Station (ISS) and examines the practices of manifesting, stowage, inventory tracking, waste disposal, and return logistics. The key findings of this examination are that while the current practices do have many positive aspects, there are also several shortcomings. These shortcomings include a high-level of excess complexity, redundancy of information/lack of a common database, and a large human-in-the-loop component. Later sections of this report describe the methodology and results of our work to systematically gather logistics lessons learned from past and current human spaceflight programs as well as validating these lessons through a survey of the opinions of current space logisticians. To consider the perspectives on logistics lessons, we searched several sources within NASA, including organizations with direct and indirect connections with the system flow in mission planning. We utilized crew debriefs, the John Commonsense lessons repository for the JSC Mission Operations Directorate, and the Skylab Lessons Learned. Additionally, we searched the public version of the Lessons Learned

  13. Natural Disasters: What Is Inside A Lesson Learned?

    NASA Astrophysics Data System (ADS)

    Scheer, S.

    2009-04-01

    The learning of lessons is something that is inherent to normal human behavior. All kind of human interaction experiences critical inspection after a severe or even disastrous event has occurred. Particular inspections have been undertaken in the field of natural disasters. Hence human risk management can continuously be improved according to lessons learned from previous disasters or with the outcome of experience shared with other stakeholders in that field. This paper shows the results of a lessons learned project over the past years: the NEDIES (Natural and Environmental Information Exchange System) deals with lessons learned during the classical risk management phases of prevention, preparedness and response At first glance a lesson is just pure text. Basically it mirrors what has been experienced within a certain context. Having a closer look at a lesson one finds out that a lesson refers to a specific emergency-triggering situation. A situation is more than a simple reference to a hazard: a "rapidly rising lake level" could have more meaning than "a flood". In order to take out positive information it is advisable not only to list up all potential benefits that could be drawn from a lesson; the explicit mentioning of benefits could be helpful in order to prepare further actions beforehand. Moreover one should also consider possible actions to take if that particular situation of the lesson exhibits again or elsewhere. In the case of rapidly rising lake level an a-priori prioritization of response actions could be done. The description of the situation is linked with other characteristics of the lesson; local issues as well as historical considerations can play a role. A flood in a densely populated town can produce different implications than a flood in the countryside. The benefits of the lesson and actions proposed could be linked with experiences made in the past. Other issues concern people involved: the addressees. Typical addressees are local decision

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

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

  16. Applying pharmaceutical lessons: learning lessons from the past.

    PubMed

    Spilker, B

    1998-06-01

    Systematic evaluation of a project, product or other successes, and failures, is an important method for improving the performance of a company, as well as that of an individual. One should evaluate and determine if lessons learned can be applied to the systems and procedures being used in the company. Even if the company does not have to adjust its strategies, procedures, portfolio or systems as a result of lessons it has learned, there may be pointers to communicate to staff. It is easy for many aspects of a system to become outdated, particularly in an organization that is growing or changing rapidly. It is therefore generally appropriate to evaluate the company's regulatory compliance, toxicology compliance, clinical auditing practices and other appropriate systems on an annual or biannual basis. Most lessons of success or failure are specific to a single situation because of the combination of people, drug, competition, priorities and many other factors involved, and cannot be extrapolated to other situations. Some general lessons and principles are presented that will facilitate drug discovery, development and marketing. PMID:15616644

  17. From Experience to Expertise: The Development of Teachers' Learning in Lesson Study

    ERIC Educational Resources Information Center

    Bocala, Candice

    2015-01-01

    This article presents a case study of how educators in one northeastern school district participated in school-based learning through lesson study (LS). Using a sociocultural perspective on teachers' learning, I compared the participation of educators who were new to lesson study ("LS novices") with those who had more experience with the…

  18. Assuring that Lessons Learned Critical to Mission Success Get Used

    NASA Technical Reports Server (NTRS)

    Oberhettinger, David

    2012-01-01

    NASA has an established process for documenting and disseminating lessons learned from spaceflight missions and related activities. However, independent assessments of the NASA lessons learned process conducted in 2002, 2003, and 2011 have concluded that NASA programs and projects are failing to heed and apply these lessons learned. JPL recently completed implementation of a three-pronged approach to assure that NASA lessons learned get used by JPL spaceflight projects.

  19. Lessons Learned from JTA Tester Safety Studies

    SciTech Connect

    R. L. Bierbaum

    2001-05-01

    EP401575, Issue C, calls out a requirement to perform safety studies for testers that are used to accept Joint Test Assembly (JTA) product at Pantex (Reference 1). The underlying motivation is to ensure that personnel hazards due to inadvertent initiation of electro-explosive devices (EEDs) during JTA testing are understood and minimized. Studies have been performed on the B61-7/11 JTA, B61-3/4/10 JTA, B83 JTA, and W76 Type 2F testers at Pantex (References 2-5). Each of these studies includes an examination of the relevant Pantex tester as well as the instrumentation and War Reserve (WR) hardware. In performing these analyses, several themes have emerged that could be useful for the Phase 6.3 design efforts for the weapons, the associated instrumentation, and the JTA testers. This report summarizes the lessons learned from these studies. Note that in some cases, the recommendations provided below to enhance safety during JTA testing operations (e.g., adding isolation resistors in the monitoring lines) may result in a reliability degradation or other surety impact. Thus it is important to consider these lessons learned in the context of the overall design and to make tradeoffs in light of the integrated surety objectives. The lessons learned are listed in five different categories, summarized as: (1) Instrumentation considerations; (2) WR design considerations; (3) Tester considerations; (4) Administrative procedures during JTA assembly; and (5) Administrative procedures prior to and during JTA testing. The first three focus on minimizing the probability of inadvertent application of power to EED initiation lines due to component, connector, and assembly failures. The last two describe procedural steps that can be taken at Pantex to either minimize the risk (e.g., by ensuring that tester power supplies cannot supply excessive power to the unit under test) or to mitigate the consequences of unexpected EED initiation (e.g., by instructing test operators to avoid

  20. X-31 Mishap: Lessons Learned

    NASA Technical Reports Server (NTRS)

    Larson, Richard R.

    2007-01-01

    , and the program was successfully completed without incident. This presentation also shows a video of the mishap including lessons learned, and the changes that were made to resume the flight-test program are presented.

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

  2. Lessons learned from early criticality accidents

    SciTech Connect

    Malenfant, R.E.

    1996-06-01

    Four accidents involving the approach to criticality occurred during the period July, 1945, through May, 1996. These have been described in the format of the OPERATING EXPERIENCE WEEKLY SUMMARY which is distributed by the Office of Nuclear and Facility Safety. Although the lessons learned have been incorporated in standards, codes, and formal procedures during the last fifty years, this is their first presentation in this format. It is particularly appropriate that they be presented in the forum of the Nuclear Criticality Technology Safety Project Workshop closest to the fiftieth anniversary of the last of the four accidents, and that which was most instrumental in demonstrating the need to incorporate lessons learned.

  3. The lift-fan aircraft: Lessons learned

    NASA Technical Reports Server (NTRS)

    Deckert, Wallace H.

    1995-01-01

    This report summarizes the highlights and results of a workshop held at NASA Ames Research Center in October 1992. The objective of the workshop was a thorough review of the lessons learned from past research on lift fans, and lift-fan aircraft, models, designs, and components. The scope included conceptual design studies, wind tunnel investigations, propulsion systems components, piloted simulation, flight of aircraft such as the SV-5A and SV-5B and a recent lift-fan aircraft development project. The report includes a brief summary of five technical presentations that addressed the subject The Lift-Fan Aircraft: Lessons Learned.

  4. Lessons Learned In Developing The VACIS™ Products

    NASA Astrophysics Data System (ADS)

    Orphan, Victor J.

    2011-06-01

    SAIC's development of VACIS™ provides useful "lessons learned" in bridging the gap from an idea to a security or contraband detection product. From a gamma densitometer idea for solving a specific Customs Service (CS) requirement (detection of drugs in near-empty tanker trucks) in mid-1990's, SAIC developed a broad line of vehicle and cargo inspections systems (over 500 systems deployed to date) based on a gamma-ray radiographic imaging technique. This paper analyzes the reasons for the successful development of VACIS and attempts to identify "lessons learned" useful for future security and contraband detection product developments.

  5. Lessons Learned In Developing The VACIS Products

    SciTech Connect

    Orphan, Victor J.

    2011-06-01

    SAIC's development of VACIS provides useful 'lessons learned' in bridging the gap from an idea to a security or contraband detection product. From a gamma densitometer idea for solving a specific Customs Service (CS) requirement (detection of drugs in near-empty tanker trucks) in mid-1990's, SAIC developed a broad line of vehicle and cargo inspections systems (over 500 systems deployed to date) based on a gamma-ray radiographic imaging technique. This paper analyzes the reasons for the successful development of VACIS and attempts to identify ''lessons learned'' useful for future security and contraband detection product developments.

  6. Very Large System Dynamics Models - Lessons Learned

    SciTech Connect

    Jacob J. Jacobson; Leonard Malczynski

    2008-10-01

    This paper provides lessons learned from developing several large system dynamics (SD) models. System dynamics modeling practice emphasize the need to keep models small so that they are manageable and understandable. This practice is generally reasonable and prudent; however, there are times that large SD models are necessary. This paper outlines two large SD projects that were done at two Department of Energy National Laboratories, the Idaho National Laboratory and Sandia National Laboratories. This paper summarizes the models and then discusses some of the valuable lessons learned during these two modeling efforts.

  7. From Lessons Learned to Emerging Practices

    ERIC Educational Resources Information Center

    Baizerman, Michael; Roholt, Ross VeLure; Korum, Kathy; Rana, Sheetal

    2013-01-01

    Organizational development is based in part on knowledge development, both formal, scientifically proven and also nonscientific practice wisdom. This article brings together all of the lessons learned over our six years of work with Saint Paul Parks and Recreation, and suggests the practice utility of these.

  8. Lessons Learned on "Scaling Up" of Projects

    ERIC Educational Resources Information Center

    Viadero, Debra

    2007-01-01

    Having developed a technology-based teaching unit on weather that appeared to work well for middle school students, Nancy Butler Songer and her colleagues at the University of Michigan decided in the late 1990s to take the next logical step in their research program: They scaled up. This article discusses lessons learned by several faculty…

  9. Lessons learned from existing biomass power plants

    SciTech Connect

    Wiltsee, G.

    2000-02-24

    This report includes summary information on 20 biomass power plants, which represent some of the leaders in the industry. In each category an effort is made to identify plants that illustrate particular points. The project experiences described capture some important lessons learned that lead in the direction of an improved biomass power industry.

  10. Columbines 10th Anniversary Finds Lessons Learned

    ERIC Educational Resources Information Center

    Trump, Kenneth S.

    2009-01-01

    When school administrators hear that the 10th anniversary of the Columbine High School attack is approaching, most shake their heads in disbelief. They are amazed that 10 years have passed since this watershed event, which changed the landscape of K-12 school safety. In this article, the author reflects on the lessons learned from the Columbine…

  11. Developing a Workplace Skills Course: Lessons Learned.

    ERIC Educational Resources Information Center

    Holter, Norma C.; Kopka, Donald J.

    2001-01-01

    Describes the development of a multidisciplinary cornerstone business course focused on communication, teamwork, problem solving, professional demeanor, research, ethics, and diversity. Discusses lessons learned: change itself raises obstacles, appropriate faculty are crucial, and time frame and course content should not be overly ambitious. (SK)

  12. Teaching Community: Lessons Learned in Wartime

    ERIC Educational Resources Information Center

    Hoffman, Darlene Haffner; Spencer, Ray C.

    2003-01-01

    In this article, the authors present the lessons learned by the teaching community from the September 11 attack and the ongoing war on terror. The ongoing war against terrorism presents some unique challenges to the nation's educators. Classroom teachers must cope with explaining to their students the daily war news and acts of violence. Decisions…

  13. Developing and Sustaining Partnerships: Lessons Learned.

    ERIC Educational Resources Information Center

    Wills, Joan L.; Kaufmann, Barbara A.

    This paper reports on a study that examined skill standards pilot programs to identify lessons learned in the selection and involvement of representatives from the various stakeholder communities and the potential for sustaining the efforts of the pilot programs. Data were gathered through structured conversations with staff and committee members…

  14. Lessons Learned: Reflections of a University President

    ERIC Educational Resources Information Center

    Bowen, William G.

    2010-01-01

    "Lessons Learned" gives unprecedented access to the university president's office, providing a unique set of reflections on the challenges involved in leading both research universities and liberal arts colleges. In this landmark book, William Bowen, former president of Princeton University and of the Andrew W. Mellon Foundation, and coauthor of…

  15. LESSONS LEARNED AND BEST PRACTICES PROGRAM MANUAL

    SciTech Connect

    Gravois, Melanie C.

    2007-05-24

    This document provides requirements and guidelines for conducting a Lessons Learned and Best Practices Program within Lawrence Berkeley National Laboratory (LBNL) to ensure ongoing improvement of safety and reliability, prevent the recurrence of significant adverse events/trends, and determine implementation strategies that will help LBNL successfully meet the missions and goals set forth by the Department of Energy (DOE).

  16. Commissioning MMS: Challenges and Lessons Learned

    NASA Technical Reports Server (NTRS)

    Wood, Paul; Gramling, Cheryl; Reiter, Jennifer; Smith, Patrick; Stone, John

    2016-01-01

    This paper discusses commissioning of NASA's Magnetospheric MultiScale (MMS) Mission. The mission includes four identical spacecraft with a large, complex set of instrumentation. The planning for and execution of commissioning for this mission is described. The paper concludes by discussing lessons learned.

  17. Library 101: Why, How, and Lessons Learned

    ERIC Educational Resources Information Center

    Porter, Michael; King, David Lee

    2010-01-01

    This article describes how and why the Library 101 Project was created and the lessons that the developers learned out of this project. The Library 101 is a project that challenges librarians to revise the paradigm of "basic" library services in order to remain relevant in this technology-driven world. It was developed by Michael Porter,…

  18. Lessons learned on the Skylab program

    NASA Technical Reports Server (NTRS)

    1974-01-01

    Lessons learned in the Skylab program and their application and adaptation to other space programs are summarized. Recommendations and action taken on particular problems are described. The use of Skylab recommendations to identify potential problems of future space programs is discussed.

  19. Lessons Learned from the NASA Plum Brook Reactor Facility Decommissioning

    NASA Technical Reports Server (NTRS)

    2010-01-01

    NASA has been conducting decommissioning activities at its PBRF for the last decade. As a result of all this work there have been several lessons learned both good and bad. This paper presents some of the more exportable lessons.

  20. Lessons learned from modal testing of aerospace structures

    NASA Astrophysics Data System (ADS)

    Hunt, David L.; Brillhart, Ralph D.

    1993-02-01

    The primary factors affecting the accuracy and the time required to perform modal tests on aerospace structures are discussed, and the lessons learned from modal tests performed over the past 15 yrs are examined. Case histories of modal testing on aerospace structures are reviewed, including the Galileo satellite and the Space Shuttle solid rocket motor and test stand. Currently recommended approaches to the modal testing are addressed.

  1. From Lessons Learned Towards Disaster Reduction Measures

    NASA Astrophysics Data System (ADS)

    Scheer, S.

    2009-04-01

    Efforts have been undertaken over the past years in eliciting and collecting lessons as they could be derived from the outcome of natural disasters management. Lessons are viewed from various perspectives according to • the situation or triggering event which led to the disaster • the local or time-dependent characteristics of this situation and further analysed according to • their benefits • necessary actions to do in order to better implement a lesson. The explicit elicitation of all that information fosters the generation of good practices and the identification of bad practices. Hence the creation of appropriate measures concerning disaster reduction issues could be positively influenced. On the other hand, continuous efforts are undertaken in the field of establishing lists of disaster reduction measures for all major hazards. Those measures comprise both concrete techniques (e.g. a tool or a structure) and advisory techniques (teaching practices or procedural instructions). This paper gives an overview of ways to "produce" disaster reduction measures from lessons learned; moreover it will explain how context-dependent analysis of lessons can potentially lead to alterations of existing disaster reduction measures.

  2. Lessons learned in command environment development

    NASA Astrophysics Data System (ADS)

    Wallace, Daniel F.; Collie, Brad E.

    2000-11-01

    As we consider the issues associated with the development of an Integrated Command Environment (ICE), we must obviously consider the rich history in the development of control rooms, operations centers, information centers, dispatch offices, and other command and control environments. This paper considers the historical perspective of control environments from the industrial revolution through the information revolution, and examines the historical influences and the implications that that has for us today. Environments to be considered are military command and control spaces, emergency response centers, medical response centers, nuclear reactor control rooms, and operations centers. Historical 'lessons learned' from the development and evolution of these environments will be examined to determine valuable models to use, and those to be avoided. What are the pitfalls? What are the assumptions that drive the environment design? Three case histories will be presented, examining (1) the control room of the Three Mile Island power plant, (2) the redesign of the US Naval Space Command operations center, and (3) a testbed for an ICE aboard a naval surface combatant.

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

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

  5. WHC significant lessons learned 1993--1995

    SciTech Connect

    Bickford, J.C.

    1997-12-12

    A lesson learned as defined in DOE-STD-7501-95, Development of DOE Lessons Learned Programs, is: A ``good work practice`` or innovative approach that is captured and shared to promote repeat applications or an adverse work practice or experience that is captured and shared to avoid a recurrence. The key word in both parts of this definition is ``shared``. This document was published to share a wide variety of recent Hanford experiences with other DOE sites. It also provides a valuable tool to be used in new employee and continuing training programs at Hanford facilities and at other DOE locations. This manual is divided into sections to facilitate extracting appropriate subject material when developing training modules. Many of the bulletins could be categorized into more than one section, however, so examination of other related sections is encouraged.

  6. LDCM Ground System. Network Lesson Learned

    NASA Technical Reports Server (NTRS)

    Gal-Edd, Jonathan

    2010-01-01

    This slide presentation reviews the Landsat Data Continuity Mission (LDCM) and the lessons learned in implementing the network that was assembled to allow for the acquisition, archiving and distribution of the data from the Landsat mission. The objective of the LDCM is to continue the acquisition, archiving, and distribution of moderate-resolution multispectral imagery affording global, synoptic, and repetitive coverage of the earth's land surface at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time. It includes a review of the ground network, including a block diagram of the ground network elements (GNE) and a review of the RF design and testing. Also included is a listing of the lessons learned.

  7. Turning Operational Lessons Learned into Design Reality

    NASA Technical Reports Server (NTRS)

    Brady, David A.

    2009-01-01

    The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.

  8. NASA Lessons Learned from Space Lubricated Mechanisms

    NASA Technical Reports Server (NTRS)

    Predmore, Roamer E.

    2000-01-01

    This document reviews the lessons learned from short-life and long life lubricated space mechanisms. A short-life lubricated mechanisms complete their life test qualification requirements after a few cycles. The mechanisms include the hinges, motors and bearings for deployment, release mechanisms, latches, release springs and support shops. Performance testing can be difficult and expensive but must be accomplished. A long-life lubricated mechanisms requires up to 5 years of life testing, or 10 to 100 years of successful flight. The long-life mechanisms include reaction wheels, momentum wheels, antenna gimbals, solar array drives, gyros and despin mechanisms. Several instances of how a mechanisms failed either in test, or in space use, and the lessons learned from these failures are reviewed. The effect of the movement away from CFC-113 cleaning solvent to ODC (Ozone-Depleting Chemical) -free is reviewed, and some of the alternatives are discussed.

  9. MSL Lessons Learned and Knowledge Capture

    NASA Technical Reports Server (NTRS)

    Buxbaum, Karen L.

    2012-01-01

    The Mars Program has recently been informed of the Planetary Protection Subcommittee (PPS) recommendation, which was endorsed by the NAC, concerning Mars Science Lab (MSL) lessons learned and knowledge capture. The Mars Program has not had an opportunity to consider any decisions specific to the PPS recommendation. Some of the activities recommended by the PPS would involve members of the MSL flight team who are focused on cruise, entry descent & landing, and early surface operations; those activities would have to wait. Members of the MSL planetary protection team at JPL are still available to support MSL lessons learned and knowledge capture; some of the specifically recommended activities have already begun. The Mars Program shares the PPS/NAC concerns about loss of potential information & expertise in planetary protection practice.

  10. Implementation of a Multimodal Mobile System for Point-of-Sale Surveillance: Lessons Learned From Case Studies in Washington, DC, and New York City

    PubMed Central

    Ganz, Ollie; Ilakkuvan, Vinu; Tacelosky, Michael; Kreslake, Jennifer; Moon-Howard, Joyce; Aidala, Angela; Vallone, Donna; Anesetti-Rothermel, Andrew; Kirchner, Thomas R

    2015-01-01

    logistical challenges; (2) developing a streamlined workflow and user-friendly interfaces for data collection; (3) allowing for ongoing communication, feedback, and technology-related skill-building among all staff; and (4) supporting infrastructure for back-end data systems. Although mobile technologies are evolving rapidly, lessons learned from these case studies are essential for ensuring that the many benefits of new mobile systems for rapid point-of-sale surveillance are fully realized. PMID:27227138

  11. Dietary Approaches to Stop Hypertension: Lessons Learned From a Case Study on the Development of an mHealth Behavior Change System

    PubMed Central

    2014-01-01

    Background Evidence-based solutions for changing health behaviors exist but problems with feasibility, sustainability, and dissemination limit their impact on population-based behavior change and maintenance. Objective Our goal was to overcome the limitations of an established behavior change program by using the inherent capabilities of smartphones and wireless sensors to develop a next generation mobile health (mHealth) intervention that has the potential to be more feasible. Methods In response to the clinical need and the growing capabilities of smartphones, our study team decided to develop a behavioral hypertension reduction mHealth system inspired by Dietary Approaches to Stop Hypertension (DASH), a lifestyle modification program. We outline the key design and development decisions that molded the project including decisions about behavior change best practices, coaching features, platform, multimedia content, wireless devices, data security, integration of systems, rapid prototyping, usability, funding mechanisms, and how all of these issues intersect with clinical research and behavioral trials. Results Over the 12 months, our study team faced many challenges to developing our prototype intervention. We describe 10 lessons learned that will ultimately stimulate more effective and sustainable approaches. Conclusions The experiences presented in this case study can be used as a reference for others developing mHealth behavioral intervention development projects by highlighting the benefits and challenges facing mHealth research. PMID:25340979

  12. The X-15 airplane - Lessons learned

    NASA Technical Reports Server (NTRS)

    Dana, William H.

    1993-01-01

    The X-15 rocket research airplane flew to an altitude of 354,000 ft and reached Mach 6.70. In almost 200 flights, this airplane was used to gather aerodynamic-heating, structural loads, stability and control, and atmospheric-reentry data. This paper describes the origins, design, and operation of the X-15 airplane. In addition, lessons learned from the X-15 airplane that are applicable to designing and testing the National Aero-Space Plane are discussed.

  13. Lessons learned in recent beryllium mirror fabrication

    NASA Astrophysics Data System (ADS)

    Wells, J. A.; Lombard, C. M.; Sloan, G. B.; Moore, W. W.; Martin, C. E.

    1991-09-01

    The lessons learned in recent fabrication of beryllium mirrors could have a significant impact on how beryllium optics of the future are produced. This paper provides an overview of the latest techniques for beryllium optics fabrication and a comparison of the results achieved. Specific technical ureas discussed include: new beryllium powders, results of consolidation, beryllium material property improvements, modified machining procedures, thermal stabilization, single point turning, burnishing techniques, replica faceplates, support structure bonding, mirror superpolishing, and new optical testing techniques.

  14. Lessons Learned for Collaborative Clinical Content Development

    PubMed Central

    Collins, S.A.; Bavuso, K.; Zuccotti, G.; Rocha, R.A.

    2013-01-01

    Background Site-specific content configuration of vendor-based Electronic Health Records (EHRs) is a vital step in the development of standardized and interoperable content that can be used for clinical decision-support, reporting, care coordination, and information exchange. The multi-site, multi-stakeholder Acute Care Documentation (ACD) project at Partners Healthcare Systems (PHS) aimed to develop highly structured clinical content with adequate breadth and depth to meet the needs of all types of acute care clinicians at two academic medical centers. The Knowledge Management (KM) team at PHS led the informatics and knowledge management effort for the project. Objectives We aimed to evaluate the role, governance, and project management processes and resources for the KM team’s effort as part of the standardized clinical content creation. Methods We employed the Center for Disease Control’s six step Program Evaluation Framework to guide our evaluation steps. We administered a forty-four question, open-ended, semi-structured voluntary survey to gather focused, credible evidence from members of the KM team. Qualitative open-coding was performed to identify themes for lessons learned and concluding recommendations. Results Six surveys were completed. Qualitative data analysis informed five lessons learned and thirty specific recommendations associated with the lessons learned. The five lessons learned are: 1) Assess and meet knowledge needs and set expectations at the start of the project; 2) Define an accountable decision-making process; 3) Increase team meeting moderation skills; 4) Ensure adequate resources and competency training with online asynchronous collaboration tools; 5) Develop focused, goal-oriented teams and supportive, consultative service based teams. Conclusions Knowledge management requirements for the development of standardized clinical content within a vendor-based EHR among multi-stakeholder teams and sites include: 1) assessing and meeting

  15. VTEC: lessons learned from British outbreaks.

    PubMed

    Pennington, T H

    2000-01-01

    Important Escherichia coli O157 outbreaks in England and Scotland since 1982-83 are reviewed. The scientific lessons learned from them are described and their legal consequences outlined. The light shed by them on relationships between law and science is discussed, and questions of blame are analysed in the context of Reason's 'resident pathogen' metaphor and Vaughan's study of the 1986 Challenger Space Shuttle disaster. PMID:10880183

  16. Lessons learned from experiments conducted on radar data management systems

    NASA Astrophysics Data System (ADS)

    Pierce, Mark W.

    1994-06-01

    The thesis provides lessons learned from experiments conducted by the 11th Air Force to verify the capabilities of two vendor-produced Radar Data Management Systems (RDMS). The first part of the thesis provides background information explaining the impetus for such experiments and why a lessons learned approach was taken. The experimental plan and the final report from the PACAF experiments are analyzed using evaluation tools taught in the C3 curriculum at the Naval Postgraduate School. The lessons learned from the mistakes made during these experiments are applied to produce a revised experimental plan. A lessons learned section follows the analysis. This section discusses specific lessons learned from the 11th Air Force experiments as well as more general lessons learned by the author. The thesis concludes with two chapters that provide overall conclusions and a summary, and recommendations for future work that can be accomplished in the area of radar data management.

  17. Army Medical Department Lessons Learned Program marks 25th anniversary.

    PubMed

    Cannon, David W; McCollum, Jeffery

    2011-11-01

    The year 2010 marked the 25th anniversary of the Center for Army Lessons Learned (CALL) as well as the Army Medical Department (AMEDD) Center and School's Lessons Learned Division. In the aftermath of Operation Urgent Fury in 1983, the Army recognized the need to create an organization whose sole purpose was to collect, review, and analyze lessons learned and created the CALL in 1985 at Fort Leavenworth, Kansas. The AMEDD followed suit and established the Medical Information System/AMEDD Lessons Learned office under the Directorate of Evaluation and Standardization to research and compile lessons learned as the AMEDD's point of contact for the CALL program. Over these past 25 years the AMEDD Center and School Lessons Learned program evolved and underwent organizational realignments, but the overall mission continues to promote changes either directly or indirectly in the AMEDD's Doctrine, Organizations, Training, Leader Development, Materiel, Personnel and Facilities domains and capabilities to provide combat health service support on the battlefield. PMID:22165647

  18. Organizational safety factors research lessons learned

    SciTech Connect

    Ryan, T.G.

    1995-10-01

    This Paper reports lessons learned and state of knowledge gained from an organizational factors research activity involving commercial nuclear power plants in the United States, through the end of 1991, as seen by the scientists immediately involved in the research. Lessons learned information was gathered from the research teams and individuals using a question and answer format. The following five questions were submitted to each team and individual: (1) What organizational factors appear to influence safety performance in some systematic way, (2) Should organizational factors research focus at the plant level, or should it extend beyond the plant level to the parent company, rate setting commissions, regulatory agencies, (3) How important is having direct access to plants for doing organizational factors research, (4) What lessons have been learned to date as the result of doing organizational factors research in a nuclear regulatory setting, and (5) What organizational research topics and issues should be pursued in the future? Conclusions based on the responses provided for this report are that organizational factors research can be conducted in a regulatory setting and produce useful results. Technologies pioneered in other academic, commercial, and military settings can be adopted for use in a nuclear regulatory setting. The future success of such research depends upon the cooperation of regulators, contractors, and the nuclear industry.

  19. Lessons learned or lessons noted: A retrospective case study of the stored organizational memory of the causes of mishaps in NASA

    NASA Astrophysics Data System (ADS)

    Miller, Susan Burgess

    This study of the National Aeronautics and Space Administration's (NASA) organizational memory explores how the root causes of NASA mishaps have changed from the creation of NASA in 1958 through 2002. Official Mishap Board Reports document in stored organizational memory the organization's analyses of the causes of the mishaps. Using Parsons' Social Action Theory for its theoretical frame, and the Schwandt Organizational Learning Systems Model as the theoretical lens, this study provides a meta-analysis of 112 Type A mishap reports to discern what patterns in this stored organizational memory have emerged over time. Results indicate marked stability in the causes of mishaps until the latter portion of the study period. The theory of revolutionary change is considered to explain this apparent shift. Discussion includes the roles organizational culture, sensemaking and identity played in data collection and knowledge management challenges as well as in the lack of change in mishap causes.

  20. Preparing a Qualitative Research-Based Dissertation: Lessons Learned

    ERIC Educational Resources Information Center

    Bowen, Glenn A.

    2005-01-01

    In this article, a newly minted Ph.D. shares seven lessons learned during the process of preparing a dissertation based on qualitative research methods. While most of the lessons may be applicable to any kind of research, the writer focuses on the special challenges of employing a qualitative methodology. The lessons are: (1) Read, read, read; (2)…

  1. Lessons learned from the Space Flyer Unit (SFU) mission.

    PubMed

    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. PMID:12369586

  2. The Lessons of Learning Expeditions.

    ERIC Educational Resources Information Center

    Rugen, Leah; Hartl, Scott

    1994-01-01

    Students in expeditionary learning schools spend most of their time engaged in sustained, in-depth studies of a single theme or topic. The experiences, lasting four to nine weeks, include strong intellectual, service, and physical dimensions. Intellectually rigorous projects and purposeful fieldwork provide a vision and an assessment strategy that…

  3. Movie Lessons for New Learning

    ERIC Educational Resources Information Center

    Saltmarsh, David

    2009-01-01

    In 2004 the Australia Council of Deans of Education (ACDE) released a report entitled "New teaching, new learning: A vision for Australian education". This report was prepared on behalf of the ACDE by Mary Kalantzis and Andrew Harvey, respectively the President and Executive Officer of the ACDE. The argument put forward in the report is that…

  4. Lessons in Developing Distance Learning.

    ERIC Educational Resources Information Center

    Gant, Lenora Peters

    1996-01-01

    Describes the use of video teletraining (VTT) for distance learning in the Department of Defense. Topics include planning and organizing the VTT facility, staff development, site facilitators, the necessity of protocol, instructional design and development strategies, student involvement and interactivity, and evaluation and assessment. (LRW)

  5. Space Shuttle Reusable Solid Rocket Motor Program Overview and Lessons Learned

    NASA Technical Reports Server (NTRS)

    Graves, Stan R.; McCool, Alex (Technical Monitor)

    2001-01-01

    An overview of the Space Shuttle Reusable Solid Rocket Motor (RSRM) program is provided with a summary of lessons learned since the first test firing in 1977. Fifteen different lessons learned are discussed that fundamentally changed the motor's design, processing, and RSRM program risk management systems. The evolution of the rocket motor design is presented including the baseline or High Performance Solid Rocket Motor (HPM), the Filament Wound Case (FWC), the RSRM, and the proposed Five-Segment Booster (FSB).

  6. Understanding the Severity of Wrongdoing in Health Care Delivery and Research: Lessons Learned From a Historiometric Study of 100 Cases

    PubMed Central

    Anderson, Emily E.; Chibnall, John T.

    2015-01-01

    Background Wrongdoing among physicians and researchers causes myriad problems for patients and research participants. While many articles have been published on professional wrongdoing, our literature review found no studies that examined the rich contextual details of large sets of historical cases of wrongdoing. Methods We examined 100 cases of wrongdoing in healthcare delivery and research using historiometric methods, which involve the statistical description and analysis of coded historical narratives. We used maximum variation, criterion-based sampling to identify cases involving 29 kinds of wrongdoing contained in a taxonomy of wrongdoing developed for the project. We coded the presence of a variety of environmental and wrongdoer variables and rated the severity of wrongdoing found in each case. This approach enabled us to (a) produce rich descriptions of variables characterizing cases; (b) identify factors influencing the severity of wrongdoing; and (c) test the hypothesis that professional wrongdoing is a unified, relatively homogenous phenomenon such as “organizational deviance.” Results Some variables were consistently found across cases (e.g., wrongdoers were male and cases lasted more than 2 years), and some variables were consistently absent across cases (e.g., cases did not involve wrongdoers who were mistreated by institutions or penalized for doing what is right). However, we also found that some variables associated with wrongdoing in research (such as ambiguous legal and ethical norms) differ from those associated with wrongdoing in healthcare delivery (such as wrongdoers with a significant history of professional misbehavior). Conclusions Earlier intervention from colleagues might help prevent the pattern we observed of repeated wrongdoing across multiple years. While some variables characterize the vast majority of highly publicized cases of wrongdoing in healthcare delivery and research—regardless of the kind of wrongdoing—it is

  7. Best Practices for Researching and Documenting Lessons Learned

    NASA Technical Reports Server (NTRS)

    Goodman, John L.

    2007-01-01

    Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/JSC Flight Design and Dynamics Division. Each project published a report, titled as follows: GPS Lessons Learned From the ISS, Space Shuttle and X-38; Lessons Learned From Seven Space Shuttle Missions; Space Shuttle Rendezvous and Proximity Operations Experience Report; and Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: Defining Report Requirements, Project Organization, and Schedule, Collection and Analysis of Source Material, Writing and Integrating the Report, and Review and Revision of the Report.

  8. 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…

  9. Six lessons learned for greater success.

    PubMed

    Leander, W J

    1993-01-01

    These six lessons learned for greater success with your Patient Focused communications can help keep your cultural change process in sync with your operational change process. Of course, there are other key elements of the former, including: formal Patient Focused educational programs; restructured Human Resources "systems" (e.g., job descriptions and compensation programs); and migration toward greater organizational empowerment and more self-directed work teams. Still, your Patient Focused communications campaign will spearhead the cultural change process. As such, it will have the opportunity to make the very first impact. Basically, your communications can make or break your Patient Focused Care program from Day One. It's up to you--learn the lessons learned by others and your organization may follow the words of Marx rather than those of Brand: "Workers of the world, unite (on behalf of your Patient Focused Care program)!" Karl Marx.p6 "Workers of the world, fan out (in formation against your Patient Focused Care program)!" Stewart Brand. PMID:10133393

  10. ICT & Learning in Chilean Schools: Lessons Learned

    ERIC Educational Resources Information Center

    Sanchez, Jaime; Salinas, Alvaro

    2008-01-01

    By the early nineties a Chilean network on computers and education for public schools had emerged. There were both high expectancies that technology could revolutionize education as well as divergent voices that doubted the real impact of technology on learning. This paper presents an evaluation of the Enlaces network, a national Information and…

  11. Lessons Learned in Computer-Based Learning.

    ERIC Educational Resources Information Center

    Modesitt, Kenneth L.

    This personal account of the development of computer-based learning from the 1960s to the present argues that the 1960s were a period of gestation. Instructional applications of computers at that time included efforts to simulate physics experiments and the debut of the PLATO system, which already had the ability to deliver interactive instruction…

  12. Team Learning in SMES: Learning the Lessons

    ERIC Educational Resources Information Center

    McKeown, Ian

    2012-01-01

    This research identifies and explores the factors that influence team learning in the context of an SME management team. It examines the difficulties the team members face in attempting to share and combine their experiences to co-construct knowledge and understanding of their environment and future opportunities. The paper reveals a connection…

  13. LESSONS LEARNED FROM A RECENT LASER ACCIDENT

    SciTech Connect

    Woods, Michael; /SLAC

    2011-01-26

    A graduate student received a laser eye injury from a femtosecond Ti:sapphire laser beam while adjusting a polarizing beam splitter optic. The direct causes for the accident included failure to follow safe alignment practices and failure to wear the required laser eyewear protection. Underlying root causes included inadequate on-the-job training and supervision, inadequate adherence to requirements, and inadequate appreciation for dimly visible beams outside the range of 400-700nm. This paper describes how the accident occurred, discusses causes and lessons learned, and describes corrective actions being taken.

  14. Lessons Learned from Autonomous Sciencecraft Experiment

    NASA Technical Reports Server (NTRS)

    Chien, Steve A.; Sherwood, Rob; Tran, Daniel; Cichy, Benjamin; Rabideau, Gregg; Castano, Rebecca; Davies, Ashley; Mandl, Dan; Frye, Stuart; Trout, Bruce; D'Agostino, Jeff; Shulman, Seth; Boyer, Darrell; Hayden, Sandra; Sweet, Adam; Christa, Scott

    2005-01-01

    An Autonomous Science Agent has been flying onboard the Earth Observing One Spacecraft since 2003. This software enables the spacecraft to autonomously detect and responds to science events occurring on the Earth such as volcanoes, flooding, and snow melt. The package includes AI-based software systems that perform science data analysis, deliberative planning, and run-time robust execution. This software is in routine use to fly the EO-l mission. In this paper we briefly review the agent architecture and discuss lessons learned from this multi-year flight effort pertinent to deployment of software agents to critical applications.

  15. Operations to Research: Communication of Lessons Learned

    NASA Technical Reports Server (NTRS)

    Fogarty, Jennifer

    2009-01-01

    This presentation explores ways to build upon previous spaceflight experience and communicate this knowledge to prepare for future exploration. An operational approach is highlighted, focusing on selection and retention standards (disease screening and obtaining medical histories); pre-, in-, and post-flight monitoring (establishing degrees of bone loss, skeletal muscle loss, cardiovascular deconditioning, medical conditions, etc.); prevention, mitigation, or treatment (in-flight countermeasures); and, reconditioning, recovery, and reassignment (post-flight training regimen, return to pre-flight baseline and flight assignment). Experiences and lessons learned from the Apollo, Skylab, Shuttle, Shuttle-Mir, International Space Station, and Orion missions are outlined.

  16. Lessons learned from commercial reactor safety analysis

    NASA Astrophysics Data System (ADS)

    Fragola, J. R.

    1992-07-01

    As design concepts involving nuclear power are developed for space missions, prudence requires a consideration of the historical perspective provided by the commerical nuclear power generating station industry. This would allow the aerospace industry to take advantage of relevant historical experience, drawing from the best features and avoiding the pitfalls which appear to have stifled the growth of the commercial nuclear industry as a whole despite its comparatively admirable safety performance record. This paper provides some history of the development of commercial nuclear plant designs, and discusses the lessons which have been learned and how they apply to the space nuclear propulsion situation.

  17. Lessons Learned from Designing Visualization Dashboards.

    PubMed

    Froese, Maria-Elena; Tory, Melanie

    2016-01-01

    A variety of visualization guidelines, principles, and techniques are available to help create a visualization-based dashboard, but few publications discuss the experience of designing dashboards in the real world. This article discuss the lessons learned from designing applications for small start-up companies and institutions. From their experience as visualization practitioners, the authors confirm the need for tailored and customizable approaches, emphasize the need for a quicker way to create functional prototypes, point out frequent misconceptions on the scope of a functional prototype, discuss how performance can affect prototyping, and discuss the resistance of industrial partners to involve their customers in requirements gathering. PMID:26960030

  18. Lessons learned in the IBL project

    NASA Astrophysics Data System (ADS)

    Miucci, A.

    2016-07-01

    The ATLAS experiment is ready for Run II of the LHC with improved tracking performance thanks to the installation of a new Pixel Detector layer, called the Insertable B-Layer (IBL). The IBL was installed in May 2014 located at only 3.3 cm radius from the beam axis and has been successfully taking data since the beginning of Run II in June 2015. An overview of the lessons learned during the IBL construction will be presented, focusing on the challenges and highlighting the issues met during the production, integration, installation and commissioning phases of the detector.

  19. First Spacelab mission status and lessons learned

    NASA Technical Reports Server (NTRS)

    Craft, H. G., Jr.; Smith, M. J.; Mullinger, D.

    1982-01-01

    There are 38 experiments and/or facilities currently under development, or undergoing testing, which will be incorporated into Spacelab for its first mission. These experiments cover a range of scientific disciplines which includes atmospheric research, life sciences, space plasma research, materials science, and space industrialization technology. In addition to the full development of individual experiments, the final design of the integrated payload and the development of all requisite integration hardware have been accomplished. Attention is given to the project management lessons learned during payload integration development.

  20. International Space Station Materials: Selected Lessons Learned

    NASA Technical Reports Server (NTRS)

    Golden, Johnny L.

    2007-01-01

    The International Space Station (ISS) program is of such complexity and scale that there have been numerous issues addressed regarding safety of materials: from design to manufacturing, test, launch, assembly on-orbit, and operations. A selection of lessons learned from the ISS materials perspective will be provided. Topics of discussion are: flammability evaluation of materials with connection to on-orbit operations; toxicity findings for foams; compatibility testing for materials in fluid systems; and contamination control in precision clean systems and critical space vehicle surfaces.

  1. Some lessons learned with wind tunnels

    NASA Technical Reports Server (NTRS)

    Spearman, M. L.

    1986-01-01

    A review is presented of some of the lessons learned from wind tunnel tests since World War II. Wind tunnels achieved a very high productivity rate during the war due in part to development testing of numerous military aircraft concepts. Following the war, in addition to development testing, a rapid increase in basic research testing occurred in order to explore areas of interest revealed by the conduct of war and to expand on advanced technology that became available from Germany and Italy. The research test areas discussed are those primarily related to the transition from subsonic flight to supersonic flight.

  2. Lessons learned: DC-X

    NASA Technical Reports Server (NTRS)

    Steinmeyer, D. A.

    1996-01-01

    The DC-X was conceived and developed specifically to lay the ground work for significantly lowering the cost of space operations. The system design was based on an initial set of program goals and a finite, limited set of resources. The goal in its simplest terms was to demonstrate vertical landing after rotation of the vehicle from a nose-first to an engines-first altitude. Finite resources actually drove the selection of a robust design to reduce fabrication and preflight testing costs. The result was a system with a large amount of flexibility which allowed expansion of the test goals as the system, and test program, evolved. The use of the vehicle flight computer interfacing with the ground control system for flight crew training was also not an initial concept. However, by defining an architecture for the system control modes which allowed additions and modifications as learning progressed, the 6 DOF codes used for flight controls software development were transported to the operating system to be used in a simulated flight mode. Flight data reduction was also greatly improved as the program progressed, and the data needs and presentation were refined. The software, avionics hardware, and the FOCC system development proceeded ahead of the vehicle, primarily because most of the hardware elements were existing at the outset of the program. The Built-in-Test (BIT) for avionics and propulsion systems were adequate. Particularly the flight readiness system which verified the vehicle health after engine start and before throttle-up for flight.

  3. Launch Vehicle Propulsion Life Cycle Cost Lessons Learned

    NASA Technical Reports Server (NTRS)

    Zapata, Edgar; Rhodes, Russell E.; Robinson, John W.

    2010-01-01

    This paper will review lessons learned for space transportation systems from the viewpoint of the NASA, Industry and academia Space Propulsion Synergy Team (SPST). The paper provides the basic idea and history of "lessons learned". Recommendations that are extremely relevant to NASA's future investments in research, program development and operations are"'provided. Lastly, a novel and useful approach to documenting lessons learned is recommended, so as to most effectively guide future NASA investments. Applying lessons learned can significantly improve access to space for cargo or people by focusing limited funds on the right areas and needs for improvement. Many NASA human space flight initiatives have faltered, been re-directed or been outright canceled since the birth of the Space Shuttle program. The reasons given at the time have been seemingly unique. It will be shown that there are common threads as lessons learned in many a past initiative.

  4. A Treatment-Refractory Case of Social Anxiety Disorder: Lessons Learned from a Failed Course of Cognitive-Behavioral Therapy

    ERIC Educational Resources Information Center

    Brozovich, Faith A.; Heimberg, Richard G.

    2011-01-01

    Over the past 25 years researchers have made enormous strides in the implementation of cognitive-behavioral therapy (CBT) for social anxiety disorder (SAD), although considerable work remains to be done. The present paper discusses a treatment refractory case seen in our clinic. The young man presented numerous interrelated obstacles, such as low…

  5. Flight Planning Branch Space Shuttle Lessons Learned

    NASA Technical Reports Server (NTRS)

    Price, Jennifer B.; Scott, Tracy A.; Hyde, Crystal M.

    2011-01-01

    Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

  6. Lessons learned from a case of multivessel median arcuate ligament syndrome in the setting of an Arc of Buhler.

    PubMed

    O'Brien, Kevin; Ferral, Hector

    2016-09-01

    The median arcuate ligament (MAL) can rarely compress both the celiac axis and superior mesenteric artery. We present a case of a 70-year male who presented with isolated episodes of upper abdominal pain and diarrhea associated with sweats and nausea. Angiography images demonstrated complete occlusion of the celiac axis and compression of the superior mesenteric artery during the expiration phases. The celiac axis was reconstituted distal to its origin by a patent Arc of Buhler. Other reported cases of multivessel MALs have produced severe symptoms in young adults requiring surgical and/or endovascular intervention. In this case, our patient's Arc of Buhler was protective against more severe chronic mesenteric ischemia. We suggest that a patent Arc of Buhler is protective against symptoms in a single vessel MALs patient. A significant percentage of patients receiving surgical intervention for MALs do not have relief of symptoms. There should be a search for an Arc of Buhler before surgical management of patients suspected to have single vessel MALs. PMID:27594946

  7. Lessons learned from starting Rochester Precision Optics

    NASA Astrophysics Data System (ADS)

    Hurley, William P.

    2014-12-01

    Thank you very much for coming to attend this talk. I see a few familiar faces in the crowd that have had their own journeys, and if you're thinking of starting your own optics business, this is not the authoritative talk on how to do. It's just a talk on what I've learned from my journey and some of my own stories on Lessons Learned. It does tie into some of the previous talks, and I do give credit to some mentors. The developments I've been involved with do make use of the ability to adapt and change, and there have been Bumps in the Road here and there, and I'll tell you a little bit more about that during this Talk.

  8. Microplastics: addressing ecological risk through lessons learned.

    PubMed

    Syberg, Kristian; Khan, Farhan R; Selck, Henriette; Palmqvist, Annemette; Banta, Gary T; Daley, Jennifer; Sano, Larissa; Duhaime, Melissa B

    2015-05-01

    Plastic litter is an environmental problem of great concern. Despite the magnitude of the plastic pollution in our water bodies, only limited scientific understanding is available about the risk to the environment, particularly for microplastics. The apparent magnitude of the problem calls for quickly developing sound scientific guidance on the ecological risks of microplastics. The authors suggest that future research into microplastics risks should be guided by lessons learned from the more advanced and better understood areas of (eco) toxicology of engineered nanoparticles and mixture toxicity. Relevant examples of advances in these two fields are provided to help accelerate the scientific learning curve within the relatively unexplored area of microplastics risk assessment. Finally, the authors advocate an expansion of the "vector effect" hypothesis with regard to microplastics risk to help focus research of microplastics environmental risk at different levels of biological and environmental organization. PMID:25655822

  9. NASA Access Mechanism: Lessons learned document

    NASA Technical Reports Server (NTRS)

    Burdick, Lisa; Dunbar, Rick; Duncan, Denise; Generous, Curtis; Hunter, Judy; Lycas, John; Taber-Dudas, Ardeth

    1994-01-01

    The six-month beta test of the NASA Access Mechanism (NAM) prototype was completed on June 30, 1993. This report documents the lessons learned from the use of this Graphical User Interface to NASA databases such as the NASA STI Database, outside databases, Internet resources, and peers in the NASA R&D community. Design decisions, such as the use of XWindows software, a client-server distributed architecture, and use of the NASA Science Internet, are explained. Users' reactions to the interface and suggestions for design changes are reported, as are the changes made by the software developers based on new technology for information discovery and retrieval. The lessons learned section also reports reactions from the public, both at demonstrations and in response to articles in the trade press and journals. Recommendations are included for future versions, such as a World Wide Web (WWW) and Mosaic based interface to heterogeneous databases, and NAM-Lite, a version which allows customization to include utilities provided locally at NASA Centers.

  10. Lessons Learned in Building the Ares Projects

    NASA Technical Reports Server (NTRS)

    Sumrall, John Phil

    2010-01-01

    Since being established in 2005, the Ares Projects at Marshall Space Flight Center have been making steady progress designing, building, testing, and flying the next generation of exploration launch vehicles. Ares is committed to rebuilding crucial capabilities from the Apollo era that made the first human flights to the Moon possible, as well as incorporating the latest in computer technology and changes in management philosophy. One example of an Apollo-era practice has been giving NASA overall authority over vehicle integration activities, giving civil service engineers hands-on experience in developing rocket hardware. This knowledge and experience help make the agency a "smart buyer" of products and services. More modern practices have been added to the management tool belt to improve efficiency, cost effectiveness, and institutional knowledge, including knowledge management/capture to gain better insight into design and decision making; earned value management, where Ares won a NASA award for its practice and implementation; designing for operability; and Lean Six Sigma applications to identify and eliminate wasted time and effort. While it is important to learn technical lessons like how to fly and control unique rockets like the Ares I-X flight test vehicle, the Ares management team also has been learning important lessons about how to manage large, long-term projects.

  11. Neutron Radiography Reactor Reactivity -- Focused Lessons Learned

    SciTech Connect

    Eric Woolstenhulme; Randal Damiana; Kenneth Schreck; Ann Marie Phillips; Dana Hewit

    2010-11-01

    As part of the Global Threat Reduction Initiative, the Neutron Radiography Reactor (NRAD) at the Idaho National Laboratory (INL) was converted from using highly enriched uranium (HEU) to low enriched uranium (LEU) fuel. After the conversion, NRAD resumed operations and is meeting operational requirements. Radiography image quality and the number of images that can be produced in a given time frame match pre-conversion capabilities. However, following the conversion, NRAD’s excess reactivity with the LEU fuel was less than it had been with the HEU fuel. Although some differences between model predictions and actual performance are to be expected, the lack of flexibility in NRAD’s safety documentation prevented adjusting the reactivity by adding more fuel, until the safety documentation could be modified. To aid future reactor conversions, a reactivity-focused Lessons Learned meeting was held. This report summarizes the findings of the lessons learned meeting and addresses specific questions posed by DOE regarding NRAD’s conversion and reactivity.

  12. Receiver System: Lessons Learned From Solar Two

    SciTech Connect

    LITWIN, ROBERT Z.; PACHECO, JAMES E.

    2002-03-01

    The Boeing Company fabricated the Solar Two receiver as a subcontractor for the Solar Two project. The receiver absorbed sunlight reflected from the heliostat field. A molten-nitrate-salt heat transfer fluid was pumped from a storage tank at grade level, heated from 290 to 565 C by the receiver mounted on top of a tower, then flowed back down into another storage tank. To make electricity, the hot salt was pumped through a steam generator to produce steam that powered a conventional Rankine steam turbine/generator. This evaluation identifies the most significant Solar Two receiver system lessons learned from the Mechanical Design, Instrumentation and Control, Panel Fabrication, Site Construction, Receiver System Operation, and Management from the perspective of the receiver designer/manufacturer. The lessons learned on the receiver system described here consist of two parts: the Problem and one or more identified Solutions. The appendix summarizes an inspection of the advanced receiver panel developed by Boeing that was installed and operated in the Solar Two receiver.

  13. Space Station Control Moment Gyroscope Lessons Learned

    NASA Technical Reports Server (NTRS)

    Gurrisi, Charles; Seidel, Raymond; Dickerson, Scott; Didziulis, Stephen; Frantz, Peter; Ferguson, Kevin

    2010-01-01

    Four 4760 Nms (3510 ft-lbf-s) Double Gimbal Control Moment Gyroscopes (DGCMG) with unlimited gimbal freedom about each axis were adopted by the International Space Station (ISS) Program as the non-propulsive solution for continuous attitude control. These CMGs with a life expectancy of approximately 10 years contain a flywheel spinning at 691 rad/s (6600 rpm) and can produce an output torque of 258 Nm (190 ft-lbf)1. One CMG unexpectedly failed after approximately 1.3 years and one developed anomalous behavior after approximately six years. Both units were returned to earth for failure investigation. This paper describes the Space Station Double Gimbal Control Moment Gyroscope design, on-orbit telemetry signatures and a summary of the results of both failure investigations. The lessons learned from these combined sources have lead to improvements in the design that will provide CMGs with greater reliability to assure the success of the Space Station. These lessons learned and design improvements are not only applicable to CMGs but can be applied to spacecraft mechanisms in general.

  14. 2010 CEOS Field Reflectance Intercomparisons Lessons Learned

    NASA Technical Reports Server (NTRS)

    Thome, Kurtis; Fox, Nigel

    2011-01-01

    This paper summarizes lessons learned from the 2009 and 2010 joint field campaigns to Tuz Golu, Turkey. Emphasis is placed on the 2010 campaign related to understanding the equipment and measurement protocols, processing schemes, and traceability to SI quantities. Participants in both 2009 and 2010 used an array of measurement approaches to determine surface reflectance. One lesson learned is that even with all of the differences in collection between groups, the differences in reflectance are currently dominated by instrumental artifacts including knowledge of the white reference. Processing methodology plays a limited role once the bi-directional reflectance of the white reference is used rather than a hemispheric-directional value. The lack of a basic set of measurement protocols, or best practices, limits a group s ability to ensure SI traceability and the development of proper error budgets. Finally, rigorous attention to sampling methodology and its impact on instrument behavior is needed. The results of the 2009 and 2010 joint campaigns clearly demonstrate both the need and utility of such campaigns and such comparisons must continue in the future to ensure a coherent set of data that can span multiple sensor types and multiple decades.

  15. Lunar Prospector: First Results and Lessons Learned

    NASA Astrophysics Data System (ADS)

    Scott Hubbard, G.; Feldman, William; Cox, Sylvia A.; Smith, Marcie A.; Chu-Thielbar, Lisa

    2002-01-01

    Lunar Prospector, the first competitively selected mission in NASA's Discovery Program, is conducting a one-year orbital survey of the Moon's composition and structure. Launched on January 6 1998, the suite of five instruments is measuring water/ice to a sensitivity of 50 ppm (hydrogen), detecting key elemental constituents, gas release events and mapping the Moon's gravitational and magnetic fields. The mission is described with emphasis on the first scientific results and lessons learned from managing a very low cost project. A mission overview and systems description is given along with final mission trajectories. Lessons learned from government-industry teaming, new modes of project management, and novel contractual arrangements are discussed. The suite of five instruments (neutron spectrometer, alpha particle spectrometer, gamma-ray spectrometer, electron reflectometer and magnetometer) is outlined with attention to final technical performance as well as development on a constrained budget and schedule. A review of our novel approaches to education and public outreach is discussed and a summary with suggestions and implications for future missions is provided.

  16. Using the EC decision on case definitions for communicable diseases as a terminology source--lessons learned.

    PubMed

    Balkanyi, Laszlo; Heja, Gergely; Nagy, Attlia

    2014-01-01

    Extracting scientifically accurate terminology from an EU public health regulation is part of the knowledge engineering work at the European Centre for Disease Prevention and Control (ECDC). ECDC operates information systems at the crossroads of many areas - posing a challenge for transparency and consistency. Semantic interoperability is based on the Terminology Server (TS). TS value sets (structured vocabularies) describe shared domains as "diseases", "organisms", "public health terms", "geo-entities" "organizations" and "administrative terms" and others. We extracted information from the relevant EC Implementing Decision on case definitions for reporting communicable diseases, listing 53 notifiable infectious diseases, containing clinical, diagnostic, laboratory and epidemiological criteria. We performed a consistency check; a simplification - abstraction; we represented lab criteria in triplets: as 'y' procedural result /of 'x' organism-substance/on 'z' specimen and identified negations. The resulting new case definition value set represents the various formalized criteria, meanwhile the existing disease value set has been extended, new signs and symptoms were added. New organisms enriched the organism value set. Other new categories have been added to the public health value set, as transmission modes; substances; specimens and procedures. We identified problem areas, as (a) some classification error(s); (b) inconsistent granularity of conditions; (c) seemingly nonsense criteria, medical trivialities; (d) possible logical errors, (e) seemingly factual errors that might be phrasing errors. We think our hypothesis regarding room for possible improvements is valid: there are some open issues and a further improved legal text might lead to more precise epidemiologic data collection. It has to be noted that formal representation for automatic classification of cases was out of scope, such a task would require other formalism, as e.g. those used by rule

  17. Radiological risk from thoron, a case study: The particularly radon-prone area of Bolsena, and the lesson learned

    NASA Astrophysics Data System (ADS)

    Cinelli, G.; Capaccioni, B.; Hernández-Ceballos, M. A.; Mostacci, D.; Perghem, A.; Tositti, L.

    2015-11-01

    The contribution of 220Rn is usually negligible compared to that of 222Rn: its very short half-life makes escape from its source site within the rock very unlikely and it never has time enough to filtrate through the ground and through cracks in the floors or cellar walls to reach living quarters. This however becomes untrue if walls built with 232Th-rich materials are present: then sizeable amounts of thoron may be detected in the closed areas bounded by those walls. This is the case for many dwellings in central Italy, and the town of Bolsena (northern Latium) is presented as a case study. A typical building of the area, entirely constructed with tuff blocks, is investigated and the annual dose rates calculated for varying distances from the wall. Thoron concentration was found to decrease with a relaxation length of 13 cm. Thoron was found to pose a significant risk. The rate of air exchange was found to produce little effect. Wall plastering acts as a filter: thoron diffuses through it but a HVL of less than 1 cm was found to prevail.

  18. E-Learning and Development: Lessons from Multi-Disciplinary Capacity Strengthening

    ERIC Educational Resources Information Center

    Babu, Suresh Chandra

    2014-01-01

    This paper documents the experience and lessons from implementing an e-learning program aimed at creating multidisciplinary research capacity. It presents a case study of bringing together a multidisciplinary group of professionals on-line to learn the skills needed to be a successful researcher in the context of HIV/AIDS and food security…

  19. Mobile Learning vs. Traditional Classroom Lessons: A Comparative Study

    ERIC Educational Resources Information Center

    Furió, D.; Juan, M.-C.; Seguí, I.; Vivó, R.

    2015-01-01

    Different methods can be used for learning, and they can be compared in several aspects, especially those related to learning outcomes. In this paper, we present a study in order to compare the learning effectiveness and satisfaction of children using an iPhone game for learning the water cycle vs. the traditional classroom lesson. The iPhone game…

  20. Seizing the Moment: State Lessons for Transforming Professional Learning

    ERIC Educational Resources Information Center

    Learning Forward, 2013

    2013-01-01

    Explore this first look at lessons learned through Learning Forward's ongoing initiative to develop a comprehensive system of professional learning that spans the distance from the statehouse to the classroom. This policy brief underscores the importance of a coordinated state professional learning strategy, the adoption of professional learning…

  1. Learning to Lead, Leading to Learn: How Facilitators Learn to Lead Lesson Study

    ERIC Educational Resources Information Center

    Lewis, Jennifer M.

    2016-01-01

    This article presents research on how teacher developers in the United States learn to conduct lesson study. Although the practice of lesson study is expanding rapidly in the US, high-quality implementation requires skilled facilitation. In contexts such as the United States where this form of professional development is relatively novel, few…

  2. School Teachers' Continuous Professional Development in an Online Learning Community: Lessons from a Case Study of an eTwinning Learning Event

    ERIC Educational Resources Information Center

    Holmes, Brian

    2013-01-01

    A social revolution is occurring in the way information is shared, knowledge is generated and innovation takes place over the Internet and there is renewed interest in the social concept of "community" to support online learning. This article describes action research conducted in the context of an eTwinning Learning Event (LE) that provides…

  3. Social support and child protection: Lessons learned and learning.

    PubMed

    Thompson, Ross A

    2015-03-01

    Social support has been a topic of research for nearly 50 years, and its applications to prevention and intervention have grown significantly, including programs advancing child protection. This article summarizes the central conclusions of the 1994 review of research on social support and the prevention of child maltreatment prepared for the U.S. Advisory Board on Child Abuse and Neglect, and surveys advances in the field since its publication. Among the lessons learned twenty years ago are (a) the diversity of the social support needs of at-risk families and their association with child endangerment, (b) the need to supplement the emotionally affirmative aspects of social support with efforts to socialize parenting practices and monitor child well-being, (c) the desirability of integrating formal and informal sources of social support for recipients, and (d) the importance of considering the complex recipient reactions to receiving support from others. The lessons we are now learning derive from research exploring the potential of online communication to enhance social support, the neurobiology of stress and its buffering through social support, and the lessons of evaluation research that are identifying the effective ingredients of social support interventions. PMID:25043921

  4. The computerization of programming: Ada (R) lessons learned

    NASA Technical Reports Server (NTRS)

    Struble, Dennis D.

    1986-01-01

    One of the largest systems yet written in Ada has been constructed. This system is the Intermetrics Ada compiler. Many lessons have been learned during the implementation of this Ada compiler. Some of these lessons, concentrating on those lessons relevant to large system implementations are described. The characteristics of the Ada compiler implementation project at Intermetrics are also described. Some specific experiences during the implementation are pointed out.

  5. NASA's Lessons Learned and Technical Standards: A Logical Marriage

    NASA Technical Reports Server (NTRS)

    Gill, Paul; Vaughan, William W.; Garcia, Danny; Weinstein, Richard

    2001-01-01

    Lessons Learned have been the basis for our accomplishments throughout the ages. They have been passed down from father to son, mother to daughter, teacher to pupil, and older to younger worker. Lessons Learned have also been the basis for NASA's accomplishments for more than forty years. Both government and industry 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. Lessons Learned have formed the foundation for discoveries, inventions, improvements, textbooks, and Technical Standards.

  6. Considerations for implementing an organizational lessons learned process.

    SciTech Connect

    Fosshage, Erik

    2013-05-01

    This report examines the lessons learned process by a review of the literature in a variety of disciplines, and is intended as a guidepost for organizations that are considering the implementation of their own closed-loop learning process. Lessons learned definitions are provided within the broader context of knowledge management and the framework of a learning organization. Shortcomings of existing practices are summarized in an attempt to identify common pitfalls that can be avoided by organizations with fledgling experiences of their own. Lessons learned are then examined through a dual construct of both process and mechanism, with emphasis on integrating into organizational processes and promoting lesson reuse through data attributes that contribute toward changed behaviors. The report concludes with recommended steps for follow-on efforts.

  7. Teaching science to science teachers: Lessons taught and lessons learned

    NASA Astrophysics Data System (ADS)

    Douglas, E. M.; Hashimoto-Martell, E. A.; Balicki, S.; Oglavie, D. R.

    2009-12-01

    our diverse participants was a constant challenge for us as instructors. In summer 2008, the course was organized so that fundamentals (chemistry, heat transfer, convection, physics) were taught in the first week and then applied in broader topics (water cycle, carbon cycle, weather and precipitation) in the second week. Learning these fundamentals was challenging for many teachers. Furthermore, the organization of topics caused frustration because there was not enough connection to the broader concepts of the course. In summer 2009, we rearranged the topics and interwove fundamentals with contextual topics within each week. We found this approach to be more successful in engaging and educating the teachers. The most successful activities were often the simplest to organize. Valuable instructional strategies included daily assessments in the form of morning quizzes, keeping a class website with all course materials, and centering the major project of the course around a lesson that teachers would design for their particular context. We saw a dramatic improvement in pre- and post-assessment test scores, with the class average increasing from 58% (pre-test) to 95% (post-test).

  8. ATLAS Beam Steering Mechanism Lessons Learned

    NASA Technical Reports Server (NTRS)

    Blumenstock, Kenneth A.; Cramer, Alexander K.; Gostin, Alan B.; Hakun, Claef F.; Haney, Paul G.; Hinkle, Matthew R.; Lee, Kenneth Y.; Lugo, Carlos F.; Matuszeski, Adam J.; Morrell, Armando; Armani, Nerses V.; Bonafede, Joseph; Jackson, Molly I.; Steigner, Peter J.; Stromsdorfer, Juan J.

    2016-01-01

    This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. The high resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of the methodology to verify performance required significant effort. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite II Mission (ICESat II), which is scheduled to be launched in 2017. The ICESat II primary mission is to map the earth's surface topography for the determination of seasonal changes of ice sheet thickness and vegetation canopy thickness to establish long-term trends.

  9. Sellafield Decommissioning Programme - Update and Lessons Learned

    SciTech Connect

    Lutwyche, P. R.; Challinor, S. F.

    2003-02-24

    The Sellafield site in North West England has over 240 active facilities covering the full nuclear cycle from fuel manufacture through generation, reprocessing and waste treatment. The Sellafield decommissioning programme was formally initiated in the mid 1980s though several plants had been decommissioned prior to this primarily to create space for other plants. Since the initiation of the programme 7 plants have been completely decommissioned, significant progress has been made in a further 16 and a total of 56 major project phases have been completed. This programme update will explain the decommissioning arrangements and strategies and illustrate the progress made on a number of the plants including the Windscale Pile Chimneys, the first reprocessing plan and plutonium plants. These present a range of different challenges and requiring approaches from fully hands on to fully remote. Some of the key lessons learned will be highlighted.

  10. ATLAS Beam Steering Mechanism (BSM) Lessons Learned

    NASA Technical Reports Server (NTRS)

    Blumenstock, Kenneth A.; Cramer, Alexander K.; Gosten, Alan B.; Hakun, Claef F.; Haney, Paul G.; Hinkle, Matthew R.; Lee, Kenneth Y.; Lugo, Carlos F.; Matuszeski, Adam J.; Morell, Armando; Armani, Nerses V.; Bonafede, Joseph; Jackson, Molly I.; Steigner, Peter J.; Stromsdorfer, Juan J.

    2016-01-01

    This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. The high resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of the methodology to verify performance required significant effort. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite II Mission (ICESat II), which is scheduled to be launched in 2017. The ICESat II primary mission is to map the Earth's surface topography for the determination of seasonal changes of ice sheet thickness and vegetation canopy thickness to establish long-term trends.

  11. Beam Steering Mechanism (BSM) Lessons Learned

    NASA Technical Reports Server (NTRS)

    Blumenstock, Kenneth A.; Cramer, Alexander K.; Gostin, Alan B.; Hakun, Claef F.; Haney, Paul G.; Hinkle, Matthew R.; Lee, Kenneth Y.; Lugo, Carlos F.; Matuszeski, Adam J.; Morell, Armando; Armani, Nerses V.; Bonafede, Joseph; Jackson, Molly I.; Steigner, Peter J.; Stromsdorfer, Juan J.

    2016-01-01

    This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. High resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of methodology to verify performance was a significant effortadvancement. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite 2 Mission (ICESat 2), which is scheduled to be launched in 2017. The ICESat 2 primary mission is to map the earths surface topography for the determination of seasonal changes of ice sheet thickness as well as vegetation canopy thickness.

  12. Lessons learned in simulating a command center

    NASA Astrophysics Data System (ADS)

    Mack, Gregory A.; Cantor, Robert M.; Wenzel, Gregory

    1995-06-01

    This paper presents some lessons learned from simulating the operation of a command center in distributed interactive simulations (DIS). We present the design of the Booz Allen Command Center Systems Interface (C2SI) in terms of its functional architecture as well as the technologies used in its implementation. We discuss the design of the distributed component interfaces based on cooperating software agent pairs. We discuss aspects of several issues in simulating command and control systems in the ADS/DIS environment, namely, interoperation of constructive and virtual simulation, situation awareness, communication with adjacent C2 entities, control of subordinate entities and external sensors, terrain/environmental data management, and data collection for after-action reporting.

  13. Lessons learned during Type A Packaging testing

    SciTech Connect

    O`Brien, J.H.; Kelly, D.L.

    1995-11-01

    For the past 6 years, the US Department of Energy (DOE) Office of Facility Safety Analysis (EH-32) has contracted Westinghouse Hanford Company (WHC) to conduct compliance testing on DOE Type A packagings. The packagings are tested for compliance with the U.S. Department of Transportation (DOT) Specification 7A, general packaging, Type A requirements. The DOE has shared the Type A packaging information throughout the nuclear materials transportation community. During testing, there have been recurring areas of packaging design that resulted in testing delays and/or initial failure. The lessons learned during the testing are considered a valuable resource. DOE requested that WHC share this resource. By sharing what is and can be encountered during packaging testing, individuals will hopefully avoid past mistakes.

  14. Lessons learned from the 1994 Northridge Earthquake

    SciTech Connect

    Eli, M.W.; Sommer, S.C.

    1995-04-01

    Southern California has a history of major earthquakes and also has one of the largest metropolitan areas in the United States. The 1994 Northridge Earthquake challenged the industrial facilities and lifetime infrastructure in the northern Los Angeles (LA) area. Lawrence Livermore National Laboratory (LLNL) sent a team of engineers to conduct an earthquake damage investigation in the Northridge area, on a project funded jointly by the United States Nuclear Regulatory Commission (USNRC) and the United States Department of Energy (USDOE). Many of the structures, systems, and components (SSCs) and lifelines that suffered damage are similar to those found in nuclear power plants and in USDOE facilities. Lessons learned from these experiences can have some applicability at commercial nuclear power plants.

  15. LESSONS LEARNED IN TESTING OF SAFEGUARDS EQUIPMENT.

    SciTech Connect

    PEPPER,S.; FARNITANO,M.; CARELLI,J.; HAZELTINE,J.; BAILEY,D.

    2001-10-29

    The International Atomic Energy Agency's (IAEA) Department of Safeguards uses complex instrumentation for the application of safeguards at nuclear facilities around the world. Often, this equipment is developed through cooperation with member state support programs because the Agency's requirements are unique and are not met by commercially available equipment. Before approving an instrument or system for routine inspection use, the IAEA subjects it to a series of tests designed to evaluate its reliability. In 2000, the IAEA began to observe operational failures in digital surveillance systems. In response to the observed failures, the IAEA worked with the equipment designer and manufacturer to determine the cause of failure. An action plan was developed to correct the performance issues and further test the systems to make sure that additional operational issues would not surface later. This paper addresses the steps taken to address operation issues related to digital image surveillance systems and the lessons learned during this process.

  16. UAVs for Glacier Mapping: Lessons Learned

    NASA Astrophysics Data System (ADS)

    McKinnon, T.; McKinnon, K. A.; Anderson, B.

    2014-12-01

    Using two different unmanned aerial vehicles (UAVs) mounted with cameras, we created a digital elevation model (DEM) of the lower 12 km^2 of Tasman Glacier, South Island, New Zealand in March 2014. The project served primarily as a proof-of-concept, and here we discuss the lessons learned, emphasizing the practical, logistical, and flight issues. We tested two different fixed-wing airframes -- a twin-boom tradition and flying wing; two different camera types, both consumer-grade RGB; and various combinations of RC and telemetry radios. We used both commercial and open-source photogrammetry software to create the mosaic and DEM imagery. Some of the most critical UAV-specific issues are: access to a launch/landing site, adequate landing zones, range, airspace contention with manned aircraft, and hardware reliability. While UAVs provide a lower-cost method for photogrammetry access, it also comes with a unique set of challenges.

  17. Social support in cyberspace: lessons learned.

    PubMed

    Cudney, Shirley; Winters, Charlene; Weinert, Clarann; Anderson, Kerri

    2005-01-01

    The lessons learned from the implementation of phase one of Women to Women (WTW1), a research-based computer outreach program for rural women with chronic illness, and their influence on the development of phase two of Women to Women (WTW2) are discussed in this article. The changes implemented in WTW2 included moving from the FirstClass delivery platform to WebCT; increasing the intra- and interdisciplinary nature of the team by adding nurse experts in Web skills and women's health and non-nurse colleagues in family finance and nutrition; expanding the geographical area to be served from Montana to adjoining states; developing health teaching units that harness the internet as the major source of ever-current health information; including a control group in the study design; and selecting more pertinent, repeated measurement instruments to assess psychosocial variables. PMID:15736616

  18. Rapid Spacecraft Development: Results and Lessons Learned

    NASA Technical Reports Server (NTRS)

    Watson, William A.

    2002-01-01

    The Rapid Spacecraft Development Office (RSDO) at NASA's Goddard Space Flight Center is responsible for the management and direction of a dynamic and versatile program for the definition, competition, and acquisition of multiple indefinite delivery and indefinite quantity contracts - resulting in a catalog of spacecraft buses. Five spacecraft delivery orders have been placed by the RSDO and one spacecraft has been launched. Numerous concept and design studies have been performed, most with the intent of leading to a future spacecraft acquisition. A collection of results and lessons learned is recorded to highlight management techniques, methods and processes employed in the conduct of spacecraft acquisition. Topics include working relationships under fixed price delivery orders, price and value, risk management, contingency reserves, and information restrictions.

  19. Evolutionary fire ecology: lessons learned from pines.

    PubMed

    Pausas, Juli G

    2015-05-01

    Macroevolutionary studies of the genus Pinus provide the oldest current evidence of fire as an evolutionary pressure on plants and date back to ca. 125 million years ago (Ma). Microevolutionary studies show that fire traits are variable within and among populations, especially among those subject to different fire regimes. In addition, there is increasing evidence of an inherited genetic basis to variability in fire traits. Added together, pines provide compelling evidence that fire can exert an evolutionary pressure on plants and, thus, shape biodiversity. In addition, evolutionary fire ecology is providing insights to improve the management of pine forests under changing conditions. The lessons learned from pines may guide research on the evolutionary ecology of other taxa. PMID:25814325

  20. Pediatric Cardiovascular Drug Trials, Lessons Learned

    PubMed Central

    Li, Jennifer S.; Cohen-Wolkowiez, Michael; Pasquali, Sara K.

    2011-01-01

    Few drugs have been labeled for pediatric cardiovascular indications and many children with cardiac disease are prescribed drugs off-label. Recent initiatives have narrowed this gap and as a result there are an increasing number of cardiology trials in the pediatric population. Many studies, however, have either failed to show a dose response in children or have not shown efficacy in children when they have established efficacy in adults. Clinical trials are challenging in children; many factors such as lack of development of a liquid formulation, failure to fully incorporate pharmacokinetic information into trial design, poor dose selection, the lack of clinical equipoise, and the use of difficult surrogate and composite primary endpoints have led to the difficulties and failures observed in several pediatric cardiovascular trials. These lessons learned may help to inform future pediatric clinical trial development. PMID:21242809

  1. XML technology planning database : lessons learned

    NASA Technical Reports Server (NTRS)

    Some, Raphael R.; Neff, Jon M.

    2005-01-01

    A hierarchical Extensible Markup Language(XML) database called XCALIBR (XML Analysis LIBRary) has been developed by Millennium Program to assist in technology investment (ROI) analysis and technology Language Capability the New return on portfolio optimization. The database contains mission requirements and technology capabilities, which are related by use of an XML dictionary. The XML dictionary codifies a standardized taxonomy for space missions, systems, subsystems and technologies. In addition to being used for ROI analysis, the database is being examined for use in project planning, tracking and documentation. During the past year, the database has moved from development into alpha testing. This paper describes the lessons learned during construction and testing of the prototype database and the motivation for moving from an XML taxonomy to a standard XML-based ontology.

  2. Lessons Learned from Mir - A Payload Perspective

    NASA Technical Reports Server (NTRS)

    Uri, John J.; Nygren, Richard W.; Cardenas, Jeffrey A.

    2003-01-01

    Among the principal objectives of the Phase 1 NASA/Mir program were for the United States to gain experience working with an international partner, to gain working experience in long-duration space flight, and to gain working experience in planning for and executing research on a long-duration space platform. The Phase 1 program was to provide to the US early experience prior to the construction and operation of the International Space Station (Phase 2 and 3). While it can be argued that Mir and ISS are different platforms and that programmatically Phase 1 and ISS are organized differently, it is also clear that many aspects of operating a long-duration research program are platform independent. This can be demonstrated by a review of lessons learned from Skylab, a US space station program of the mid-1970's, many of which were again "learned" on Mir and are being "learned" on ISS. Among these are optimum crew training strategies, on-orbit crew operations, ground support, medical operations and crew psychological support, and safety certification processes

  3. Lessons learned from the Shoreham fuel shipping experience

    SciTech Connect

    Jones, R H

    1995-01-01

    The shipment of slightly exposed nuclear fuel from the Shoreham Nuclear Power Station to the Limerick Generating Station serves as a model for future shipments of spent nuclear fuel (SNF). Many lessons were learned from this experience both general and specific. This paper presents a sampling of these lessons and suggests that future SNF campaigns can benefit from studying this and other relevant projects.

  4. Lessons Learned from the Uniontown Community Health Project.

    ERIC Educational Resources Information Center

    Littleton, Mary Ann; Cornell, Carol E.; Dignan, Mark; Brownstein, J. Nell; Raczynski, James M.; Stalker, Varena G.; McDuffie, Kathleen Y.; Greene, Paul G.; Sanderson, Bonnie; Struempler, Barbara Jo.

    2002-01-01

    Examines lessons learned from a 5-year project designed to develop, implement, and evaluate a multifaceted community health advisor-based intervention to reduce the risk of cardiovascular disease among older, rural, African American women. Data from observations surveys, and discussion groups highlight six lessons (e.g., establish personal working…

  5. New Horizons Risk Communication Strategy, Planning, Implementation, and Lessons Learned

    NASA Technical Reports Server (NTRS)

    Dawson, Sandra A.

    2006-01-01

    This paper discusses the risk communication goals, strategy, planning process and product development for the New Horizons mission, including lessons from the Cassini mission that were applied in that effort, and presents lessons learned from the New Horizons effort that could be applicable to future missions.

  6. Japanese Lesson Study Sustaining Teacher Learning in the Classroom Context

    ERIC Educational Resources Information Center

    Loose, Crystal Corle

    2014-01-01

    The purposes of this action research study were first to explore teacher perceptions of Japanese lesson study as a method of professional development, and second to take teachers through an action research process as they observed the implementation of a literacy lesson in the classroom. Situated Learning Theory, particularly related to teacher…

  7. Improved Lesson Planning with Universal Design for Learning (UDL)

    ERIC Educational Resources Information Center

    Courey, Susan Joan; Tappe, Phyllis; Siker, Jody; LePage, Pam

    2013-01-01

    Efficient lesson planning with universal design for learning (UDL) enables teachers to more effectively meet students' individual needs. In this study, a comparison of lesson plans by teacher candidates in a teacher preparation program before and after UDL training is presented. After training, teachers (n = 45) incorporated more differentiated…

  8. Lessons Learned from the Kepler Mission and Space Telescope Management

    NASA Technical Reports Server (NTRS)

    Fanson, James

    2010-01-01

    This paper presents lessons learned over the course of several space telescope mission and instrument developments spanning two decades. These projects involved astronomical telescopes developed by the National Aeronautics and Space Administration (NASA) and were designed to further our understanding of the Universe. It is hoped that the lessons drawn from these experiences may be of use to future mission developers.

  9. Unpressurized Logistics Carriers for the International Space Station: Lessons Learned

    NASA Technical Reports Server (NTRS)

    Robbins, William W., Jr.

    1999-01-01

    The International Space Station has been in development since 1984, and has recently begun on orbit assembly. Most of the hardware for the Space Station has been manufactured and the rest is well along in design. The major sets of hardware that are still to be developed for Space Station are the pallets and interfacing hardware for resupply of unpressurized spares and scientific payloads. Over the last ten years, there have been numerous starts, stops, difficulties and challenges encountered in this effort. The Space Station program is now entering the beginning of orbital operations. The Program is only now addressing plans to design and build the carriers that will be needed to carry the unpressurized cargo for the Space Station lifetime. Unpressurized carrier development has been stalled due to a broad range of problems that occurred over the years. These problems were not in any single area, but encompassed budgetary, programmatic, and technical difficulties. Some lessons of hindsight can be applied to developing carriers for the Space Station. Space Station teams are now attempting to incorporate the knowledge gained into the current development efforts for external carriers. In some cases, the impacts of these lessons are unrecoverable for Space Station, but can and should be applied to future programs. This paper examines the progress and problems to date with unpressurized carrier development identifies the lessons to be learned, and charts the course for finally accomplishing the delivery of these critical hardware sets.

  10. Lessons learned in detailed clinical modeling at Intermountain Healthcare

    PubMed Central

    Oniki, Thomas A; Coyle, Joseph F; Parker, Craig G; Huff, Stanley M

    2014-01-01

    Background and objective Intermountain Healthcare has a long history of using coded terminology and detailed clinical models (DCMs) to govern storage of clinical data to facilitate decision support and semantic interoperability. The latest iteration of DCMs at Intermountain is called the clinical element model (CEM). We describe the lessons learned from our CEM efforts with regard to subjective decisions a modeler frequently needs to make in creating a CEM. We present insights and guidelines, but also describe situations in which use cases conflict with the guidelines. We propose strategies that can help reconcile the conflicts. The hope is that these lessons will be helpful to others who are developing and maintaining DCMs in order to promote sharing and interoperability. Methods We have used the Clinical Element Modeling Language (CEML) to author approximately 5000 CEMs. Results Based on our experience, we have formulated guidelines to lead our modelers through the subjective decisions they need to make when authoring models. Reported here are guidelines regarding precoordination/postcoordination, dividing content between the model and the terminology, modeling logical attributes, and creating iso-semantic models. We place our lessons in context, exploring the potential benefits of an implementation layer, an iso-semantic modeling framework, and ontologic technologies. Conclusions We assert that detailed clinical models can advance interoperability and sharing, and that our guidelines, an implementation layer, and an iso-semantic framework will support our progress toward that goal. PMID:24993546

  11. Lessons learned from a regional strategy for resource allocation.

    PubMed

    Edwards, Janine C; Stapley, Jonathan; Akins, Ralitsa; Silenas, Rasa; Williams, Josie R

    2005-01-01

    Two qualitative case studies focus on the allocation of CDC funds distributed during 2002 for bioterrorism preparedness in two Texas public health regions (each as populous and complex as many states). Lessons learned are presented for public health officials and others who work to build essential public health services and security for our nation. The first lesson is that personal relationships are the cornerstone of preparedness. A major lesson is that a regional strategy to manage funds may be more effective than allocating funds on a per capita basis. One regional director required every local department to complete a strategic plan as a basis for proportional allocation of the funds. Control of communicable diseases was a central component of the planning. Some funds were kept at the regional level to provide epidemiology services, computer software, equipment, and training for the entire region. Confirmation of the value of this regional strategy was expressed by local public health and emergency management officials in a focus group 1 year after the strategy had been implemented. The group members also pointed out the need to streamline the planning process, provide up-to-date computer networks, and receive more than minimal communication. This regional strategy can be viewed from the perspective of adaptive leadership, defined as activities to bring about constructive change, which also can be used to analyze other difficult areas of preparedness. PMID:16000042

  12. Lessons Learned from the Clementine Mission

    NASA Technical Reports Server (NTRS)

    1997-01-01

    According to BMDO, the Clementine mission achieved many of its technology objectives during its flight to the Moon in early 1994 but, because of a software error, was unable to test the autonomous tracking of a cold target. The preliminary analyses of the returned lunar data suggest that valuable scientific measurements were made on several important topics but that COMPLEX's highest-priority objectives for lunar science were not achieved. This is not surprising given that the rationale for Clementine was technological rather than scientific. COMPLEX lists below a few of the lessons that may be learned from Clementine. Although the Clementine mission was not conceived as a NASA science mission exactly like those planned for the Discovery program, many operational aspects of the two are similar. It is therefore worthwhile to understand the strengths and faults of the Clementine approach. Some elements of the Clementine operation that led to the mission's success include the following: (1) The mission's achievements were the responsibility of a single organization and its manager, which made that organization and that individual accountable for the final outcome; (2) The sponsor adopted a hands-off approach and set a minimum number of reviews (three); (3) The sponsor accepted a reasonable amount of risk and allowed the project team to make the trade-offs necessary to minimize the mission's risks while still accomplishing all its primary objectives; and (4) The development schedule was brief and the agreed-on funding (and funding profile) was adhered to. Among the operational shortcomings of Clementine were the following: (1) An overly ambitious schedule and a slightly lean budget (meaning insufficient time for software development and testing, and leading ultimately to human exhaustion); and (2) No support for data calibration, reduction, and analysis. The principal lesson to be learned in this category is that any benefits from the constructive application of higher

  13. M-learning in a geography lesson

    NASA Astrophysics Data System (ADS)

    Mirski, Katri

    2014-05-01

    their work in Google Earth where they did a tour of their journey. In the feedback students said that it was a very interesting and an educational practical task. A new opportunity in M-learning is to use QR codes. This means that you don't have to print out worksheets with questions. You can hide question in the code and students can read them with their own devices on site. From the Master's thesis I also developed a tutorial material named "M-learning in a geography lesson" (in Estonian: M-õpe geograafiatunnis), you can see it in the webpage katrimope@wordpress.com. The tutorial received a second place on the Estonian study material contest in 2013. This is only one example on how to use M-learning. In Gustav Adolf Grammar School we use M-learning in lots of different subjects because it's really important in modern school to link new technologies, surrounding environment and learning for the purpose of better obtainment of knowledge.

  14. Web Cast on Arsenic Demonstration Program: Lessons Learned

    EPA Science Inventory

    Web cast presentation covered 10 Lessons Learned items selected from the Arsenic Demonstration Program with supporting information. The major items discussed include system design and performance items and the cost of the technologies.

  15. Heritage Adoption Lessons Learned: Cover Deployment and Latch Mechanism

    NASA Technical Reports Server (NTRS)

    Wincentsen, James

    2006-01-01

    This viewgraph presentation reviews the lessons learned from heritage adoption designs. A general overview of cover deployment hardware that includes the three mechanisms of latch, hinge, and energy absorbers are also discussed.

  16. Retrieval Lesson Learned from NAST-I Hyperspectral Data

    NASA Technical Reports Server (NTRS)

    Zhou, Daniel K.; Smith, William L.; Liu, Xu; Larar, Allen M.; Mango, Stephen A.

    2007-01-01

    The retrieval lesson learned is important to many current and future hyperspectral remote sensors. Validated retrieval algorithms demonstrate the advancement of hyperspectral remote sensing capabilities to be achieved with current and future satellite instruments.

  17. CYGNSS: Lessons We are Learning from a Class D Mission

    NASA Technical Reports Server (NTRS)

    Tumlinson, Jessica

    2015-01-01

    CYGNSS: Lessons Learned from NASA Class D Mission and how they selected their parts for the program to include balance between cost, risk, schedule and technology available as well as balancing cost restraints with mission risk profile.

  18. Implementing a lessons learned process at Sandia National Laboratories

    SciTech Connect

    Fosshage, Erik D.; Drewien, Celeste A.; Eras, Kenneth; Hartwig, Ronald Craig; Post, Debra S.; Stoecker, Nora Kathleen

    2016-01-01

    The Lessons Learned Process Improvement Team was tasked to gain an understanding of the existing lessons learned environment within the major programs at Sandia National Laboratories, identify opportunities for improvement in that environment as compared to desired attributes, propose alternative implementations to address existing inefficiencies, perform qualitative evaluations of alternative implementations, and recommend one or more near-term activities for prototyping and/or implementation. This report documents the work and findings of the team.

  19. Heritage Adoption Lessons Learned: Cover Deployment and Latch Mechanism

    NASA Technical Reports Server (NTRS)

    Wincentsen, James

    2006-01-01

    Within JPL, there is a technology thrust need to develop a larger Cover Deployment and Latch Mechanism (CDLM) for future missions. The approach taken was to adopt and scale the CDLM design as used on the Galaxy Evolution Explorer (GALEX) project. The three separate mechanisms that comprise the CDLM will be discussed in this paper in addition to a focus on heritage adoption lessons learned and specific examples. These lessons learned will be valuable to any project considering the use of heritage designs.

  20. Commercial Orbital Transportation Services (COTS) Program Lessons Learned

    NASA Technical Reports Server (NTRS)

    Lindenmoyer, Alan; Horkachuck, Mike; Shotwell, Gwynne; Manners, Bruce; Culbertson, Frank

    2015-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 COTS Program. 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.

  1. Lessons learned from radiation oncology clinical trials.

    PubMed

    Liu, Fei-Fei; Okunieff, Paul; Bernhard, Eric J; Stone, Helen B; Yoo, Stephen; Coleman, C Norman; Vikram, Bhadrasain; Brown, Martin; Buatti, John; Guha, Chandan

    2013-11-15

    A workshop entitled "Lessons Learned from Radiation Oncology Trials" was held on December 7-8, 2011, in Bethesda, MD, to present and discuss some of the recently conducted radiation oncology clinical trials with a focus on those that failed to refute the null hypothesis. The objectives of this workshop were to summarize and examine the questions that these trials provoked, to assess the quality and limitations of the preclinical data that supported the hypotheses underlying these trials, and to consider possible solutions to these challenges for the design of future clinical trials. Several themes emerged from the discussions: (i) opportunities to learn from null-hypothesis trials through tissue and imaging studies; (ii) value of preclinical data supporting the design of combinatorial therapies; (iii) significance of validated biomarkers; (iv) necessity of quality assurance in radiotherapy delivery; (v) conduct of sufficiently powered studies to address the central hypotheses; and (vi) importance of publishing results of the trials regardless of the outcome. The fact that well-designed hypothesis-driven clinical trials produce null or negative results is expected given the limitations of trial design and complexities of cancer biology. It is important to understand the reasons underlying such null results, however, to effectively merge the technologic innovations with the rapidly evolving biology for maximal patient benefit through the design of future clinical trials. PMID:24043463

  2. University Reactor Conversion Lessons Learned Workshop for Purdue University Reactor

    SciTech Connect

    Eric C. Woolstenhulme; Dana M. Hewit

    2008-09-01

    The Department of Energy’s Idaho National Laboratory, under its programmatic responsibility for managing the University Research Reactor Conversions, has completed the conversion of the reactor at Purdue University Reactor. With this work completed and in anticipation of other impending conversion projects, the INL convened and engaged the project participants in a structured discussion to capture the lessons learned. The lessons learned process has allowed us to capture gaps, opportunities, and good practices, drawing from the project team’s experiences. These lessons will be used to raise the standard of excellence, effectiveness, and efficiency in all future conversion projects.

  3. Planning and scheduling lessons learned study, executive summary

    NASA Technical Reports Server (NTRS)

    Robinson, Toni

    1990-01-01

    The study was performed to document the lessons on planning and scheduling activities for a number of missions and institutional facilities in such a way that they can be applied to future missions; to provide recommendations to both projects and Code 500 that will improve the end-to-end planning and scheduling process; and to identify what, if any, mission characteristics might be related to certain lessons learned. The results are a series of recommendations of both a managerial and technical nature related to the underlying lessons learned.

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

  5. Providing community education: lessons learned from Native Patient Navigators.

    PubMed

    Burhansstipanov, Linda; Krebs, Linda U; Harjo, Lisa; Watanabe-Galloway, Shinobu; Pingatore, Noel; Isham, Debra; Duran, Florence Tinka; Denny, Loretta; Lindstrom, Denise; Crawford, Kim

    2014-09-01

    Native Navigators and the Cancer Continuum (NNACC) was a community-based participatory research study among five American Indian organizations. The intervention required lay Native Patient Navigators (NPNs) to implement and evaluate community education workshops in their local settings. Community education was a new role for the NPNs and resulted in many lessons learned. NPNs met quarterly from 2008 through 2013 and shared lessons learned with one another and with the administrative team. In July 2012, the NPNs prioritized lessons learned throughout the study that were specific to implementing the education intervention. These were shared to help other navigators who may be including community education within their scope of work. The NPNs identified eight lessons learned that can be divided into three categories: NPN education and training, workshop content and presentation, and workshop logistics and problem-solving. A ninth overarching lesson for the entire NNACC study identified meeting community needs as an avenue for success. This project was successful due to the diligence of the NPNs in understanding their communities' needs and striving to meet them through education workshops. Nine lessons were identified by the NPNs who provided community education through the NNACC project. Most are relevant to all patient navigators, regardless of patient population, who are incorporating public education into navigation services. Due to their intervention and budget implications, many of these lessons also are relevant to those who are developing navigation research. PMID:25087698

  6. Providing Community Education: Lessons Learned from Native Patient Navigators

    PubMed Central

    Burhansstipanov, Linda; Krebs, Linda U.; Harjo, Lisa; Watanabe-Galloway, Shinobu; Pingatore, Noel; Isham, Debra; Duran, Florence Tinka; Denny, Loretta; Lindstrom, Denise; Crawford, Kim

    2014-01-01

    Native Navigators and the Cancer Continuum (NNACC) was a community-based participatory research study among five American Indian organizations. The intervention required lay Native Patient Navigators (NPNs) to implement and evaluate community education workshops in their local settings. Community education was a new role for the NPNs and resulted in many lessons learned. NPNs met quarterly from 2008 through 2013 and shared lessons learned with one another and with the administrative team. In July 2012, the NPNs prioritized lessons learned throughout the study that were specific to implementing the education intervention. These were shared to help other navigators who may be including community education within their scope of work. The NPNs identified eight lessons learned that can be divided into three categories: NPN education and training, workshop content and presentation, and workshop logistics and problem-solving. A ninth overarching lesson for the entire NNACC study identified meeting community needs as an avenue for success. This project was successful due to the diligence of the NPNs in understanding their communities’ needs and striving to meet them through education workshops. Nine lessons were identified by the NPNs who provided community education through the NNACC project. Most are relevant to all patient navigators, regardless of patient population, who are incorporating public education into navigation services. Due to their intervention and budget implications, many of these lessons also are relevant to those who are developing navigation research. PMID:25087698

  7. Calibration Lessons Learned from Hyperion Experience

    NASA Astrophysics Data System (ADS)

    Casement, S.; Ho, K.; Sandor-Leahy, S.; Biggar, S.; Czapla-Myers, J.; McCorkel, J.; Thome, K.

    2009-12-01

    The use of hyperspectral imagers to provide climate-quality data sets, such as those expected from the solar reflective sensor on the Climate Absolute Radiance and Refractivity Observatory (CLARREO), requires stringent radiometric calibration requirements. These stringent requirements have been nearly met with broadband radiometers such as CERES, but high resolution spectrometers pose additional challenges. A review of the calibration processes for past space-based HSIs provide guidance on the calibration processes that will be needed for future sensors. In November 2000, the Earth Observer-1 (EO-1) platform was launched onboard a Boeing Delta II launch vehicle. The primary purpose of the EO-1 mission was to provide a technological testbed for spaceborne components. The platform has three sensors onboard, of which, the hyperspectral imager (HSI) Hyperion, is discussed here. The Hyperion sensor at the time had no comparable sensor in earth orbit, being the first grating-based, hyperspectral, civilian sensor in earth orbit. Ground and on-orbit calibration procedures including all cross-calibration activities have achieved an estimated instrument absolute radiometric error of 2.9% in the Visible channel (0.4 - 1.0 microns) and 3.4% in the shortwave infrared (SWIR, 0.9 - 2.5 microns) channel (EO-1/Hyperion Early Orbit Checkout Report Part II On-Orbit Performance Verification and Calibration). This paper describes the key components of the Hyperion calibration process that are applicable to future HSI missions. The pre-launch methods relied on then newly-developed, detector-based methods. Subsequent vicarious methods including cross-calibration with other sensors and the reflectance-based method showed significant differences from the prelaunch calibration. Such a difference demonstrated the importance of the vicarious methods as well as pointing to areas for improvement in the prelaunch methods. We also identify areas where lessons learned from Hyperion regarding

  8. Lessons Learned from Radioactive Waste Storage and Disposal Facilities

    SciTech Connect

    Esh, David W.; Bradford, Anna H.

    2008-01-15

    The safety of radioactive waste disposal facilities and the decommissioning of complex sites may be predicated on the performance of engineered and natural barriers. For assessing the safety of a waste disposal facility or a decommissioned site, a performance assessment or similar analysis is often completed. The analysis is typically based on a site conceptual model that is developed from site characterization information, observations, and, in many cases, expert judgment. Because waste disposal facilities are sited, constructed, monitored, and maintained, a fair amount of data has been generated at a variety of sites in a variety of natural systems. This paper provides select examples of lessons learned from the observations developed from the monitoring of various radioactive waste facilities (storage and disposal), and discusses the implications for modeling of future waste disposal facilities that are yet to be constructed or for the development of dose assessments for the release of decommissioning sites. Monitoring has been and continues to be performed at a variety of different facilities for the disposal of radioactive waste. These include facilities for the disposal of commercial low-level waste (LLW), reprocessing wastes, and uranium mill tailings. Many of the lessons learned and problems encountered provide a unique opportunity to improve future designs of waste disposal facilities, to improve dose modeling for decommissioning sites, and to be proactive in identifying future problems. Typically, an initial conceptual model was developed and the siting and design of the disposal facility was based on the conceptual model. After facility construction and operation, monitoring data was collected and evaluated. In many cases the monitoring data did not comport with the original site conceptual model, leading to additional investigation and changes to the site conceptual model and modifications to the design of the facility. The following cases are discussed

  9. Lessons learned -- NREL Village Power Program

    SciTech Connect

    Flowers, L.

    1998-07-01

    In 1993, a workshop was convened at the National Renewable Energy Laboratory (NREL) to discuss the issues of applying renewable energy in a sustainable manner to international rural development. One of the summary recommendations was that NREL could assist in the renewable energy for rural electrification effort by developing and supplying six related activities: resource assessment, comparative analysis and modeling, performance monitoring and analysis, pilot project development, internet-based project data, communications, and training. In response to this recommendation, NREL launched its Village Power Program consisting of these activities that cut across NREL technologies and disciplines. Currently NREL is active in 20 countries, with pilot projects in 12 of those countries. At this time the technologies include photovoltaics, wind, biomass, and hybrids. The rural applications include home lighting and communications, water pumping, schools and health posts, battery charging stations, ecotourism, and village systems. These pilot projects are central to the renewable energy village power development through the demonstration of three aspects critical to replication and implementation of the projects on a significant scale. The three aspects are technical functionality, economic competitiveness, and institutional sustainability. It is important to note that the pilot projects from which NREL's experience has been gained were funded and, in many cases, developed by other organizations and agencies. NREL's role has been one of technical assistance or project management or both. The purpose of this paper is to describe the lessons NREL staff has gleaned from their participation in the various pilot projects. The author hopes that these lessons will help the Renewable Energy-Based Rural Electrification (RERE) community in implementing sustainable projects that lead to replication.

  10. Teaching with Internet Telescopes: Some Lessons Learned

    NASA Astrophysics Data System (ADS)

    Stencel, Robert

    Observational astronomy is often difficult for pre-college students and teachers because: (1) school occurs in daytime and visual observing at night; (2) light pollution hides the stars from students living in cities; (3) few schools have teachers trained to use and maintain astronomy equipment; (4) there is lack of access to expertise when needed; (5) physically disabled students cannot easily access a telescope eypiece. Internet access to computer controlled telescopes with digital cameras can solve many of these difficulties. The Web enables students and teachers to access well-maintained internet-controllable telescopes at dark-site locations and to consult more readily with experts. This paper reports on a three-month pilot project exploring this situation conducted Feb-May 2002 which allowed high school students to access a CCD-equipped accurately-pointing and tracking telescope located in New Mexico controllable over the Web with a user-friendly skymap browser tool. User interest proved phenomenal and user statistics proved diverse. There were distinct lessons learned about how to enhance student participation in the research process. Details available at website www.du.edu/~rstencel/stn.htm. We thank the ICSRC for a grant to Denver University and acknowledge in-kind support from the estate of William Herschel Womble.

  11. Contamination and UV lasers: lessons learned

    NASA Astrophysics Data System (ADS)

    Daly, John G.

    2015-09-01

    Laser induced damage to optical elements has been a subject of significant research, development, and improvement, since the first lasers were built over the last 50 years. Better materials, with less absorption, impurities, and defects are available, as well as surface coatings with higher laser damage resistance. However, the presence of contamination (particles, surface deposition films, or airborne) can reduce the threshold for damage by several orders of magnitude. A brief review of the anticipated laser energy levels for damage free operation is presented as a lead into the problems associated with contamination for ultraviolet (UV) laser systems. As UV lasers become more common in applications especially in areas such as lithography, these problems have limited reliability and added to costs. This has been characterized as Airborne Molecular Contamination (AMC) in many published reports. Normal engineering guidelines such as screening materials within the optical compartment for low outgassing levels is the first step. The use of the NASA outgassing database (or similar test methods) with low Total Mass Loss (TML) and Condensed Collected Volatiles Collected Mass (CVCM) is a good baseline. Energetic UV photons are capable of chemical bond scission and interaction with surface contaminant or airborne materials results in deposition of obscuring film laser footprints that continue to degrade laser system performance. Laser systems with average powers less than 5 mW have been shown to exhibit aggressive degradation. Lessons learned over the past 15 years with UV laser contamination and steps to reduce risk will be presented.

  12. CEBAF Upgrade: Cryomodule Performance And Lessons Learned

    SciTech Connect

    Drury, Michael A.; Davis, G. Kirk; Hogan, John P.; Hovater, J. Curt; King, Lawrence; Marhauser, Frank; Park, HyeKyoung; Preble, Joe; Reece, Charles E.; Rimmer, Robert A.; Wang, Haipeng; Wiseman, Mark A.

    2014-02-01

    The Thomas Jefferson National Accelerator Facility is currently engaged in the 12 GeV Upgrade Project. The goal of the 12 GeV Upgrade is a doubling of the available beam energy of the Continuous Electron Beam Accelerator Facility (CEBAF) from 6 GeV to 12 GeV. This increase in beam energy will be due in large part to the addition of ten C100 cryomodules plus associated new RF in the CEBAF linacs. The C100 cryomodules are designed to deliver 100 MeV per installed cryomodule. Each C100 cryomodule is built around a string of eight seven-cell, electro-polished, superconducting RF cavities. While an average performance of 100MV per cryomodule is needed to achieve the overall 12 GeV beam energy goal, the actual performance goal for the cryomodules is an average energy gain of 108 MV to provide operational headroom. Cryomodule production started in December 2010. All ten of the C100 cryomodules are installed in the linac tunnels and are on schedule to complete commissioning by September 2013. Performance during Commissioning has ranged from 104 MV to 118 MV. In May, 2012 a test of an early C100 achieved 108 MV with full beam loading. This paper will discuss the performance of the C100 cryomodules along with operational challenges and lessons learned for future designs.

  13. Resource Allocation Planning Helper (RALPH): Lessons learned

    NASA Technical Reports Server (NTRS)

    Durham, Ralph; Reilly, Norman B.; Springer, Joe B.

    1990-01-01

    The current task of Resource Allocation Process includes the planning and apportionment of JPL's Ground Data System composed of the Deep Space Network and Mission Control and Computing Center facilities. The addition of the data driven, rule based planning system, RALPH, has expanded the planning horizon from 8 weeks to 10 years and has resulted in large labor savings. Use of the system has also resulted in important improvements in science return through enhanced resource utilization. In addition, RALPH has been instrumental in supporting rapid turn around for an increased volume of special what if studies. The status of RALPH is briefly reviewed and important lessons learned from the creation of an highly functional design team are focused on through an evolutionary design and implementation period in which an AI shell was selected, prototyped, and ultimately abandoned, and through the fundamental changes to the very process that spawned the tool kit. Principal topics include proper integration of software tools within the planning environment, transition from prototype to delivered to delivered software, changes in the planning methodology as a result of evolving software capabilities and creation of the ability to develop and process generic requirements to allow planning flexibility.

  14. Lessons Learned in Risk Management on NCSX

    SciTech Connect

    G.H. Neilson, C.O. Gruber, J.H. Harris, D.J. Rej, R.T. Simmons, and R.L. Strykowsky

    2009-02-11

    The National Compact Stellarator Experiment (NCSX) was designed to test physics principles of an innovative stellarator design developed by the Princeton Plasma Physics Laboratory and Oak Ridge National Laboratory. Construction of some of the major components and sub-assemblies was completed, but the estimated cost and schedule for completing the project grew as the technical requirements and risks became better understood, leading to its cancellation in 2008. The project's risks stemmed from its technical challenges, primarily the complex component geometries and tight tolerances that were required. The initial baseline, established in 2004, was supported by a risk management plan and risk-based contingencies, both of which proved to be inadequate. Technical successes were achieved in the construction of challenging components and subassemblies, but cost and schedule growth was experienced. As part of an effort to improve project performance, a new risk management program was devised and implemented in 2007-08. It led to a better understanding of project risks, a sounder basis for contingency estimates, and improved management tools. Although the risks ultimately were unacceptable to the sponsor, valuable lessons in risk management were learned through the experiences with the NCSX project.

  15. Lessons Learned in Risk Management on NCSX

    SciTech Connect

    G.H. Neilson, C.O. Gruber, J.H. Harris, D.J. Rej, R.T. Simmons, and R.L. Strykowsky

    2009-07-21

    The National Compact Stellarator Experiment (NCSX) was designed to test physics principles of an innovative stellarator design developed by the Princeton Plasma Physics Laboratory and Oak Ridge National Laboratory. Construction of some of the major components and sub-assemblies was completed, but the estimated cost and schedule for completing the project grew as the technical requirements and risks became better understood, leading to its cancellation in 2008. The project's risks stemmed from its technical challenges, primarily the complex component geometries and tight tolerances that were required. The initial baseline, established in 2004, was supported by a risk management plan and risk-based contingencies, both of which proved to be inadequate. Technical successes were achieved in the construction of challenging components and subassemblies, but cost and schedule growth was experienced. As part of an effort to improve project performance, a new risk management program was devised and implemented in 2007-08. It led to a better understanding of project risks, a sounder basis for contingency estimates, and improved management tools. Although the risks ultimately were unacceptable to the sponsor, valuable lessons in risk management were learned through the experiences with the NCSX project.

  16. Lessons learned and unlearned in periodontal microbiology

    PubMed Central

    Teles, Ricardo; Teles, Flavia; Frias-Lopez, Jorge; Paster, Bruce; Haffajee, Anne

    2013-01-01

    Periodontal diseases are initiated by bacterial species living in polymicrobial biofilms at or below the gingival margin and progress largely as a result of the inflammation initiated by specific subgingival species. In the past few decades, efforts to understand the microbiota of periodontal diseases have led to an exponential increase in information about biofilms associated with periodontal health and disease. In fact, the oral microbiota is one of the best characterized microbiomes that colonize the human body. Despite this increased knowledge, one has to ask if our fundamental concepts of the etiology and pathogenesis of periodontal diseases have really changed. In this chapter we will review how our comprehension of the structure and function of the subgingival microbiota evolved over the years in search of lessons learned and unlearned in periodontal microbiology. More specifically, this review focuses on: 1) how the data obtained through molecular techniques has impacted our knowledge of the etiology of periodontal infections; 2) the potential role of viruses in the etiopathogenesis of periodontal diseases; 3) how concepts of microbial ecology have expanded our understanding of host microbial interactions that might lead to periodontal diseases; 4) the role of inflammation in the pathogenesis of periodontal diseases; and 5) the impact of these evolving concepts on treatment and preventive approaches to periodontal infections. We will conclude by reviewing how novel systems biology approaches promise to unravel new details of the pathogenesis of periodontal diseases and, hopefully, lead to a better understanding of periodontal disease mechanisms. PMID:23574465

  17. FUSE: lessons learned for future FUV missions

    NASA Astrophysics Data System (ADS)

    Moos, H. W.; McCandliss, Stephan R.; Kruk, Jeffrey W.

    2004-10-01

    The far ultraviolet spectral region (roughly 900 - 1200 Å) is densely packed with strong atomic, ionic and molecular transitions of astrophysical importance. Many of these transitions provide unique access to the associated species. This spectral region is also technically challenging: optical reflectivities are limited, contamination control requirements are severe and detectors must be windowless. The Far Ultraviolet Spectroscopic Explorer (FUSE) covers the spectral region 905 -1187 Å with a resolution ~ 15 km s-1. The mission, launched in June 1999 and now in its fifth year of science operations, has reaped a rich scientific harvest from this spectral region. This paper will examine the lessons learned from the FUSE mission with the perspective of looking ahead to possible future missions. In order to build on the scientific advances of the FUSE mission, such a mission would require both increased sensitivity and higher spectral resolution. We conclude that achieving these requirements will necessitate, among other advances, new approaches to far ultraviolet mirror coating technology. We also examine the possibility of accessing the far ultraviolet using an ultraviolet observatory designed for longer wavelength ultraviolet radiation.

  18. Workshop on Discovery Lessons-Learned

    NASA Technical Reports Server (NTRS)

    Saunders, M. (Editor)

    1995-01-01

    As part of the Discovery Program's continuous improvement effort, a Discovery Program Lessons-Learned workshop was designed to review how well the Discovery Program is moving toward its goal of providing low-cost research opportunities to the planetary science community while ensuring continued U.S. leadership in solar system exploration. The principal focus of the workshop was on the recently completed Announcement of Opportunity (AO) cycle, but the program direction and program management were also open to comment. The objective of the workshop was to identify both the strengths and weaknesses of the process up to this point, with the goal of improving the process for the next AO cycle. The process for initializing the workshop was to solicit comments from the communities involved in the program and to use the feedback as the basis for establishing the workshop agenda. The following four sessions were developed after reviewing and synthesizing both the formal feedback received and informal feedback obtained during discussions with various participants: (1) Science and Return on Investment; (2) Technology vs. Risk; Mission Success and Other Factors; (3) Cost; and (4) AO.AO Process Changes and Program Management.

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

  20. Protein Name Tagging Guidelines: Lessons Learned

    PubMed Central

    Hu, Zhangzhi; Jang, Seok Bae; Samuel, Ken; Krause, Matthew; Phillips, Jon; Wu, Cathy H.

    2005-01-01

    Interest in information extraction from the biomedical literature is motivated by the need to speed up the creation of structured databases representing the latest scientific knowledge about specific objects, such as proteins and genes. This paper addresses the issue of a lack of standard definition of the problem of protein name tagging. We describe the lessons learned in developing a set of guidelines and present the first set of inter-coder results, viewed as an upper bound on system performance. Problems coders face include: (a) the ambiguity of names that can refer to either genes or proteins; (b) the difficulty of getting the exact extents of long protein names; and (c) the complexity of the guidelines. These problems have been addressed in two ways: (a) defining the tagging targets as protein named entities used in the literature to describe proteins or protein-associated or -related objects, such as domains, pathways, expression or genes, and (b) using two types of tags, protein tags and long-form tags, with the latter being used to optionally extend the boundaries of the protein tag when the name boundary is difficult to determine. Inter-coder consistency across three annotators on protein tags on 300 MEDLINE abstracts is 0.868 F-measure. The guidelines and annotated datasets, along with automatic tools, are available for research use. PMID:18629297

  1. Constellation Program: Lessons Learned. Volume 1; Executive Summary

    NASA Technical Reports Server (NTRS)

    Rhatigan, Jennifer L. (Editor)

    2011-01-01

    This document (Volume I) provides an executive summary of the lessons learned from the Constellation Program. A companion Volume II provides more detailed analyses for those seeking further insight and information. In this volume, Section 1.0 introduces the approach in preparing and organizing the content to enable rapid assimilation of the lessons. Section 2.0 describes the contextual framework in which the Constellation Program was formulated and functioned that is necessary to understand most of the lessons. Context of a former program may seem irrelevant in the heady days of new program formulation. However, readers should take some time to understand the context. Many of the lessons would be different in a different context, so the reader should reflect on the similarities and differences in his or her current circumstances. Section 3.0 summarizes key findings developed from the significant lessons learned at the program level that appear in Section 4.0. Readers can use the key findings in Section 3.0 to peruse for particular topics, and will find more supporting detail and analyses in Section 4.0 in a topical format. Appendix A contains a white paper describing the Constellation Program formulation that may be of use to readers wanting more context or background information. The reader will no doubt recognize some very similar themes from previous lessons learned, blue-ribbon committee reviews, National Academy reviews, and advisory panel reviews for this and other large-scale human spaceflight programs; including Apollo, Space Shuttle, Shuttle/Mir, and the ISS. This could represent an inability to learn lessons from previous generations; however, it is more likely that similar challenges persist in the Agency structure and approach to program formulation, budget advocacy, and management. Perhaps the greatest value of these Constellation lessons learned can be found in viewing them in context with these previous efforts to guide and advise the Agency and its

  2. Academies: It's Time to Learn the Lessons. NFER Thinks: What the Evidence Tells Us

    ERIC Educational Resources Information Center

    Worth, Jack

    2015-01-01

    Academies are now a part of the English school landscape. Future policy should focus on learning the lessons from the growth of academy schools. In this "NFER Thinks," the author presents the case that any future expansion in the number of academies should be motivated by a clear vision of the long-term outcomes for learners that…

  3. Positive Examples and Lessons Learned from Rural Small Business Adoption of E-Commerce Strategies

    ERIC Educational Resources Information Center

    Lamie, R. David; Barkley, David L.; Markley, Deborah M.

    2011-01-01

    Rural small businesses struggling against the current of competition from "big box" retailers, weak consumer demand, and on-line shopping options must find strategies that work. Many are finding that adoption of e-commerce strategies is a key to survival, even prosperity. This article highlights the lessons learned from a recent case study…

  4. Microbiological Lessons Learned from the Space Shuttle

    NASA Technical Reports Server (NTRS)

    Pierson, Duane L.; Ott, C. Mark; Bruce, Rebekah; Castro, Victoria A.; Mehta, Satish K.

    2011-01-01

    functions were found to be altered. Selected microorganisms were found to become more virulent during spaceflight. The increased knowledge gained on the Space Shuttle resulted in further studies of the host-microbe interactions on the ISS to determine if countermeasures were necessary. Lessons learned from the Space Shuttle Program were integrated into the ISS resulting in the safest space habitat to date.

  5. Applying Universal Design for Learning to Instructional Lesson Planning

    ERIC Educational Resources Information Center

    McGhie-Richmond, Donna; Sung, Andrew N.

    2013-01-01

    Universal Design for Learning is a framework for developing inclusive instructional lesson plans. The effects of introducing Universal Design for Learning Principles and Guidelines in a university teacher education program with pre-service and practicing teachers were explored in a mixed methods approach. The results indicate that the study…

  6. School Planning: Lessons Learned at the Celebration School.

    ERIC Educational Resources Information Center

    Cohen, Sarah

    1998-01-01

    Discusses the lessons learned from Disney's K-12 Celebration School when trying to apply the latest research on teaching and learning to the school's design. Explores the future of business/school partnering in school planning, and offers expert advice on the school-planning process. (GR)

  7. Building a Better Lessons Learned Program - White Paper

    SciTech Connect

    Miller, Charles Frederick

    2002-04-01

    Lessons learned are more in vogue today than at any time in our history. You can’t tune into a news broadcast without hearing a reference to the concept – and for good reason. People are finally accepting the idea that they may be able to benefit from the experiences of others. Corporations, government departments, and even the military are actively using lessons learned information to help them to achieve their varied goals. The Department of Energy is one of the government departments that has a Lessons Learned Program and requires its contractors to develop a program of their own. Unfortunately, adequate guidance is not available to enable contractors to design a fully mature program (i.e., a program that will immediately meet their every need) and to ensure that it is implemented such that it will be deemed acceptable during subsequent assessments. The purpose of this paper is to present the reader with information that might help him or her better plan and develop a new or upgraded Lessons Learned Program. The information is based on the actual development and implementation of a “second generation” lessons learned program and is presented as a chronicle of the steps taken to build the rudimentary system and the subsequent events and problems that led to the programs present-day configuration.

  8. Lessons Learned Designing and Building the Chandra Telescope

    NASA Astrophysics Data System (ADS)

    Arenberg, Jonathan

    2016-04-01

    This poster offers some of the major lessons learned by key members of the Chandra Telescope team. These lessons are gleaned from our experiences developing, designing, building and testing the telescope and its subsystems, with 15 years of hindsight. Among the topics to be discussed are the early developmental tests, known as VETA-I and VETA-II, requirements derivation, the impact of late requirements and reflection on the conservatism in the design process. This poster offers some opinions on how these lessons can affect future missions.

  9. Learning from extraordinary lovers: lessons from the edge.

    PubMed

    Kleinplatz, Peggy J

    2006-01-01

    This paper discusses lessons about sexuality and eroticism gleaned from those who engage in extraordinary sex, even though such relationships have typically been classified as pathological. What can clinicians learn from those who seek and attain uncommon sexual relations? Such individuals' sexual epistemology, goals, understanding of the nature and spectrum of sexual and erotic relations, communication strategies and "outcome" criteria can provide valuable lessons for those who treat sexual problems or aim to overcome sexual mediocrity. For example, while traditional sex therapy often focuses on what is on the surface, some SM participants are interested in the meanings that lie at a deeper level. Whereas conventional clinicians may focus on enabling particular sexual acts (especially heterosexual intercourse), SM participants are more apt to be concerned with the varied spectrum of underlying purposes motivating these acts. Whereas many couples are willing to settle for merely functional sex, SM practitioners may be more interested in contact that necessitates intense, erotic connection; sophisticated communication of subtle differences in intent; and eventuates in profound self-knowledge and transcendent levels of intimacy. Illustrative case examples are provided. PMID:16803770

  10. Why Has Computer Assisted Learning Made So Little Impact in Secondary Education? Lessons from an Economics and Business Subject Case-Study

    ERIC Educational Resources Information Center

    Hurd, Steve

    2009-01-01

    This article reports the findings and draws lessons from a major twenty-year longitudinal study of computer use in economics and business studies teaching in UK secondary schools. Over the period, the level and pattern of computer use within subject lessons has changed substantially. In particular, there has been a progressive shift away from…