Search NASA⌕ Search

SEARCH · Search NASA

Results for “assurance case”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.↗

Conformance Testing: Measurement Decision Rules

The goal of a Quality Management System (QMS) as specified in ISO 9001 and AS9100 is to provide assurance to the customer that end products meet specifications. Measuring devices, often called measuring and test equipment (MTE), are used to provide the evidence of product conformity to specified requirements. Unfortunately, processes that employ MTE can become a weak link to the overall QMS if proper attention is not given to the measurement process design, capability, and implementation. Documented "decision rules" establish the requirements to ensure measurement processes provide the measurement data that supports the needs of the QMS. Measurement data are used to make the decisions that impact all areas of technology. Whether measurements support research, design, production, or maintenance, ensuring the data supports the decision is crucial. Measurement data quality can be critical to the resulting consequences of measurement-based decisions. Historically, most industries required simplistic, one-size-fits-all decision rules for measurements. One-size-fits-all rules in some cases are not rigorous enough to provide adequate measurement results, while in other cases are overly conservative and too costly to implement. Ideally, decision rules should be rigorous enough to match the criticality of the parameter being measured, while being flexible enough to be cost effective. The goal of a decision rule is to ensure that measurement processes provide data with a sufficient level of quality to support the decisions being made - no more, no less. This paper discusses the basic concepts of providing measurement-based evidence that end products meet specifications. Although relevant to all measurement-based conformance tests, the target audience is the MTE end-user, which is anyone using MTE other than calibration service providers. Topics include measurement fundamentals, the associated decision risks, verifying conformance to specifications, and basic measurement decisions rules.

Mimbs, Scott M.↗

Recommendations on the Use of Commercial-Off-The-Shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) Parts for NASA Missions - Phase II

This assessment had two Phases. Phase I captured NASA Centers’ current practices for commercial-off-the-shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) parts 1 used in spaceflight systems and ground support equipment (available at https://ntrs.nasa.gov/citations/20205011579) [ref. 1]. The Phase II report provides guidance for selecting and using COTS parts in NASA missions. The approaches proposed in this report differ from current agency practices. This top-level executive summary touches on these new approaches for using COTS parts but does not provide the detailed information that is critical in understanding the rationale behind these new approaches. Readers will need to read the entire report to gain full understanding and effectively use the recommendations herein. NASA’s historical approach to selecting and applying parts has been to define certain parts, primarily specific classes of military specification (MIL-SPEC) parts, as “standard”, leaving all others, including COTS parts, as nonstandard. Standard parts typically are used without further testing (“use-as-is”). Nonstandard parts are subjected to initial screening and subsequent lot acceptance testing of representative samples from each procured lot per MIL-SPEC or similar requirements. Decades later, top-tier commercial part manufacturers have evolved significant manufacturing, statistical control, and technological improvements that can now provide parts as reliable or more reliable than MIL-SPEC parts, when used within their datasheet limits. Concurrently, the space science and exploration community’s needs demand technological advances unavailable with MIL-SPEC parts. This ongoing change necessitates using COTS parts for space missions. Properly selected COTS parts in appropriate applications can offer performance and supply availability advantages compared to MIL-SPEC parts. Their utility and demonstrated reliability result from large volumes and automated production and testing processes. However, careful review and a thorough understanding of their specifications (i.e., datasheet limitations) is needed, and verifying that manufacturer specifications and reliability meet space hardware application needs are necessary. This report recommends MIL-SPEC screening and non-radiation-related lot acceptance testing be reduced or eliminated in cases where evidence of sufficient quality and reliability exists for COTS parts. The extent of NASA's insight into COTS manufacturers and the amount and nature of the needed evidence will differ by mission and will likely be driven by a mission's resources and associated risk posture. To facilitate this goal, two new terminologies have been defined and described: “Industry Leading Parts Manufacturer (ILPM)” and “Established COTS parts.” An ILPM is a COTS manufacturer that produces high quality and reliable parts. Some parts produced by ILPMs, defined as Established COTS parts, do not need any additional MIL-SPEC or NASA screening and lot acceptance testing to be used in space applications. This report provides guidance for selecting, procuring, and applying COTS parts and for performing part-, board-, and system-level COTS parts verification. The recommendation to select Established COTS parts from ILPMs will assure those COTS parts will have comparable quality to corresponding MIL-SPEC parts. Selecting, applying, and verifying Established COTS parts from ILPMs requires a holistic team approach, engaging parts engineers, circuit designers, quality, reliability, and systems engineers, procurement specialists, radiation specialists, avionics leads, and program/project managers. A mission-specific approach tailored to a project’s Mission, Environment, Applications and Lifetime (MEAL) [ref. 2] requirements should be developed and approved by program/project managers. Any associated risks should be clearly identified, quantified, mitigated, and/or accepted. Different approaches are recommended according to program/project Risk Classes A, B, C, and D [ref. 3] and human-rated missions [ref. 4]: 1. Recommend Classes A and B and human-rated missions consider a “MIL-SPEC parts- based design” approach. ”MIL-SPEC parts-based design” approach is one in which most parts are MIL-SPEC parts and Established COTS parts from ILPMs are used only when an equivalent MIL-SPEC part does not meet functional or size, weight, and power (SWaP) or performance requirements, or is not available. 2. Recommend Classes D and Sub-D missions consider a “System of COTS” approach. “System of COTS” approach is one which most parts are Established COTS parts from ILPMs. 3. Recommend Class C missions determine which approach is the best for their projects; that is, use either a “MIL-SPEC parts-based design” approach, “System of COTS” approach, or a combined approach utilizing elements of both. This report intends to provide guidance in using COTS parts for NASA missions with risk classifications of A through D and human-rated missions; but it does not address the costs of using COTS parts. Costs of using COTS parts in different NASA mission classes can vary significantly even if the same parts are used in different risk postures, due to differing verification levels needed. The guidance does not distinguish between critical or non-critical systems, and a given project will need to apply the appropriate guidance based on their risk posture. The intended audience of this report are NASA personnel and commercial practitioners who support NASA’s spaceflight missions, including spaceflight program or project managers, parts engineers, parts manufacturers, radiation engineers, avionics engineers, system engineers, circuit design engineers, reliability engineers, safety and mission assurance (SMA) personnel, and parts procurement specialists. The NEPP Program will perform a pathfinder study to explore implementing the guidance in this NESC report. An ILPM verification process is not the same as conventional vendor qualification processes performed according to military standards and specifications. This NESC report intends to provide guidance in utilizing available parts data from ILPM manufacturers for parts assurance assessments needed for NASA missions. The report also captured the current practices from DoD and Federal Aviation Administration (FAA) in Section 10. Note each DoD and FAA report was provided by the corresponding agencies regarding their practices, which are independent from the NESC recommendations in the report.

Commercial-Off-The-Shelf↗

Satellite Remote-Sensing Capability to Assess Tropospheric-Column Ratios of Formaldehyde and Nitrogen Dioxide: Case Study During the Long Island Sound Tropospheric Ozone Study 2018 (LISTOS 2018) Field Campaign

Satellite retrievals of tropospheric-column formaldehyde (HCHO) and nitrogen dioxide (NO 2 ) are frequently used to investigate the sensitivity of ozone (O 3 ) production to emissions of nitrogen oxides and volatile organic carbon compounds. This study inter-compared the systematic biases and uncertainties in retrievals of NO 2 and HCHO, as well as resulting HCHO–NO 2 ratios (FNRs), from two commonly applied satellite sensors to investigate O 3 production sensitivities (Ozone Monitoring Instrument, OMI, and TROPOspheric Monitoring Instrument, TROPOMI) using airborne remote-sensing data taken during the Long Island Sound Tropospheric Ozone Study 2018 between 25 June and 6 September 2018. Compared to aircraft-based HCHO and NO 2 observations, the accuracy of OMI and TROPOMI were magnitude-dependent with high biases in clean environments and a tendency towards more accurate comparisons to even low biases in moderately polluted to polluted regions. OMI and TROPOMI NO 2 systematic biases were similar in magnitude (normalized median bias, NMB = 5 %–6 %; linear regression slope ≈ 0.5–0.6), with OMI having a high median bias and TROPOMI resulting in small low biases. Campaign-averaged uncertainties in the three satellite retrievals (NASA OMI; Quality Assurance for Essential Climate Variables, QA4ECV OMI; and TROPOMI) of NO 2 were generally similar, with TROPOMI retrievals having slightly less spread in the data compared to OMI. The three satellite products differed more when evaluating HCHO retrievals. Campaign-averaged tropospheric HCHO retrievals all had linear regression slopes ∼0.5 and NMBs of 39 %, 17 %, 13 %, and 23 % for NASA OMI, QA4ECV OMI, and TROPOMI at finer (0.05° x 0.05°) and coarser (0.15° x 0.15°) spatial resolution, respectively. Campaign-averaged uncertainty values (root mean square error, RMSE) in NASA and QA4ECV OMI HCHO retrievals were ~9.0 x 10 15 molecules cm –2 (∼ 50 %–55 % of mean column abundance), and the higher-spatial-resolution retrievals from TROPOMI resulted in RMSE values ∼30 % lower. Spatially averaging TROPOMI tropospheric-column HCHO, along with NO 2 and FNRs, to resolutions similar to the OMI reduced the uncertainty in these retrievals. Systematic biases in OMI and TROPOMI NO 2 and HCHO retrievals tended to cancel out, resulting in all three satellite products comparing well to observed FNRs. However, while satellite-derived FNRs had minimal campaign-averaged median biases, unresolved errors in the indicator species did not cancel out in FNR calculations, resulting in large RMSE values compared to observations. Uncertainties in HCHO retrievals were determined to drive the unresolved biases in FNR retrievals.

Matthew S. Johnson↗

System-Theoretic Analysis of Unsafe Collaborative Control in Teaming Systems

The interactions that occur in human-teaming are inspiring novel aerospace designs aimed at improving how humans and machines, or multiple machines, work together. Unfortunately, current Systems Engineering processes are ill-equipped to handle these complex relationships and are unable to design and assure the safety for these systems. To close part of this gap, this paper introduces a novel system-theoretic analytical process to identify unsafe collaborative control actions. It is part of a broader set of techniques that extend the state-of-the-art in hazard analysis, System Theoretic Process Analysis (STPA), to systematically address collaboration. The method rigorously expresses the different ways multiple commands may be unsafe together. Using Systems Theory, it employs abstraction to manage the combinatorial complexity in enumerating control contributions from multiple collaborating components. An algorithm integrates these concepts into an end-to-end process and is supported by automation to enumerate, refine, prune, and prioritize unsafe combinations of control actions. The output of the method feeds the specification of system requirements to implement safety-guided design starting early in concept development. The process is demonstrated on a manned-unmanned aircraft teaming case study and finds new causal factors that were not previously found in a past hazard analysis of the same system.

System Safety↗

Proceedings of the Sixth NASA Langley Formal Methods (LFM) Workshop

Today's verification techniques are hard-pressed to scale with the ever-increasing complexity of safety critical systems. Within the field of aeronautics alone, we find the need for verification of algorithms for separation assurance, air traffic control, auto-pilot, Unmanned Aerial Vehicles (UAVs), adaptive avionics, automated decision authority, and much more. Recent advances in formal methods have made verifying more of these problems realistic. Thus we need to continually re-assess what we can solve now and identify the next barriers to overcome. Only through an exchange of ideas between theoreticians and practitioners from academia to industry can we extend formal methods for the verification of ever more challenging problem domains. This volume contains the extended abstracts of the talks presented at LFM 2008: The Sixth NASA Langley Formal Methods Workshop held on April 30 - May 2, 2008 in Newport News, Virginia, USA. The topics of interest that were listed in the call for abstracts were: advances in formal verification techniques; formal models of distributed computing; planning and scheduling; automated air traffic management; fault tolerance; hybrid systems/hybrid automata; embedded systems; safety critical applications; safety cases; accident/safety analysis.

Rozier, Kristin Yvonne↗

Effect of Preconditioning on Post-Soldering Failures in Tantalum Capacitors

Soldering have a strong effect on performance and reliability of most surface mount technology components, including tantalum capacitors. High quality tantalum capacitors are likely the only type of components where soldering simulation is the first step during screening. Nevertheless, post-soldering failures of tantalum capacitors do happen and require additional analysis. Popcorning is a well-known effect in plastic encapsulated microcircuits (PEM) and it occurs also in chip tantalum capacitors. The sensitivity of parts to the presence of moisture during soldering is characterized by the moisture sensitivity level (MSL); however, contrary to PEMs, there is no standard procedure for establishing MSL for tantalum capacitors, and standard J-STD-020 is applicable partially only. In this work, the effect of absorbed moisture on soldering related degradation and failures in tantalum capacitors have been studied using 22 types of polymer and 11 types of MnO2 cathodes tantalum capacitors including single and multianode parts. The amount of moisture released during soldering has been estimated by measurements of mass and capacitance variations. Results show that moisture uptake in similar parts is approximately two times greater in polymer than in MnO2 capacitors. Cracking of the case and degradation of parameters can occur in both types of parts, but MnO2 capacitors are much more susceptible to catastrophic short circuit failures and their ignition is possible during the first power-on cycle. This type of failure in MnO2 capacitors is lot-related, can occur even at derated voltages and relatively low levels of moisture sorption corresponding to room conditions. Baking before soldering is an effective measure to prevent failures even in lots susceptible to popcorning damage. Recommendations for testing to establish MSL and for baking to reduce the probability of failures are suggested.

tantalum polymer capacitors↗

Effects of the 8 psia / 32% O2 Atmosphere on the Human in the Spaceflight Environment

Extravehicular activity (EVA) is at the core of a manned space exploration program. There are elements of exploration that may be safely and effectively performed by robots, but there are critical elements of exploration that will require the trained, assertive, and reasoning mind of a human crewmember. To effectively use these skills, NASA needs a safe, effective, and efficient EVA component integrated into the human exploration program. The EVA preparation time should be minimized and the suit pressure should be low to accommodate EVA tasks without undue fatigue, physical discomfort, or suit-related trauma. Commissioned in 2005, the Exploration Atmospheres Working Group (EAWG) had the primary goal of recommending to NASA an internal environment that allowed efficient and repetitive EVAs for missions that were to be enabled by the former Constellation Program. At the conclusion of the EAWG meeting, the 8.0 psia and 32% oxygen (O2) environment were recommended for EVA intensive phases of missions. As a result of selecting this internal environment, NASA gains the capability for efficient EVA with low risk of decompression sickness (DCS), but not without incurring additional negative stimulus of hypobaric hypoxia to the already physiologically challenging spaceflight environment. This paper provides a literature review of the human health and performance risks associated with the 8 psia/32% O2 environment. Of most concern are the potential effects on the central nervous system including increased intracranial pressure, visual impairment, sensorimotor dysfunction, and oxidative damage. Other areas of focus include validation of the DCS mitigation strategy, incidence and treatment of acute mountain sickness (AMS), development of new exercise countermeasures protocols, effective food preparation at 8 psia, assurance of quality sleep, and prevention of suit-induced injury. As a first effort, the trade space originally considered in the EAWG was re-evaluated looking for ways to decrease the hypoxic dose by further enriching the O2% or increasing the pressure. After discussion with the NASA engineering and materials community, it was determined that the O2 could be enriched from 32% to 34% and the pressure increased from 8.0 to 8.2 psia without significant penalty. These two small changes increase alveolar O2 pressure by 11 mmHg, which is expected to significantly benefit crewmembers. The 8.2/34 environment (inspired O2 pressure = 128 mmHg) is also physiologically equivalent to the staged decompression atmosphere of 10.2 psia / 26.5% O2 (inspired O2 pressure = 127 mmHg) used on 34 different shuttle missions for approximately a week each flight. Once decided, the proposed internal environment, if different than current experience, should be evaluated through appropriately simulated research studies. In many cases, the human physiologic concerns can be investigated effectively through integrated multi-discipline ground-based studies. Although missions proposing to use an 8.2/34 environment are still years away, it is recommended that these studies begin early enough to ensure that the correct decisions pertaining to vehicle design, mission operational concepts, and human health countermeasures are appropriately informed.

Environmental control↗

Architectural Analysis of Complex Evolving Systems of Systems

The goal of this collaborative project between FC-MD, APL, and GSFC and supported by NASA IV&V Software Assurance Research Program (SARP), was to develop a tool, Dynamic SAVE, or Dyn-SAVE for short, for analyzing architectures of systems of systems. The project team was comprised of the principal investigator (PI) from FC-MD and four other FC-MD scientists (part time) and several FC-MD students (full time), as well as, two APL software architects (part time), and one NASA POC (part time). The PI and FC-MD scientists together with APL architects were responsible for requirements analysis, and for applying and evaluating the Dyn-SAVE tool and method. The PI and a group of FC-MD scientists were responsible for improving the method and conducting outreach activities, while another group of FC-MD scientists were responsible for development and improvement of the tool. Oversight and reporting was conducted by the PI and NASA POC. The project team produced many results including several prototypes of the Dyn-SAVE tool and method, several case studies documenting how the tool and method was applied to APL s software systems, and several published papers in highly respected conferences and journals. Dyn-SAVE as developed and enhanced throughout this research period, is a software tool intended for software developers and architects, software integration testers, and persons who need to analyze software systems from the point of view of how it communicates with other systems. Using the tool, the user specifies the planned communication behavior of the system modeled as a sequence diagram. The user then captures and imports the actual communication behavior of the system, which is then converted and visualized as a sequence diagram by Dyn-SAVE. After mapping the planned to the actual and specifying parameter and timing constraints, Dyn-SAVE detects and highlights deviations between the planned and the actual behavior. Requirements based on the need to analyze two inter-system communication protocols that are representative of protocols used in the Aerospace industry have been specified. The protocols are related: APL s Common Ground System (CGS) as used in the MErcury Surface, Space ENvironment, GEochemistry, and Ranging (MESSENGER) and the Radiation Belt Space Probes (RBSP) missions. The analyzed communications were implementations of the Telemetry protocol and the CCSDS File Delivery Protocol (CFDP) protocol. Based on these requirements, three prototypes of Dyn-SAVE were developed and applied to these protocols. The application of Dyn-SAVE to these protocols resulted in the detection of several issues. Dyn-SAVE was also applied to several Testbeds that have previously been used for experimentation earlier on this project, as well as, to other protocols and logs for testing its broader applicability. For example, Dyn-SAVE was used to analyze 1) the communication pattern between a web browser and a web server, 2) the system log of a computer in order to detect offnominal computer shut-down behavior, and 3) the actual test cases of NASA Goddard s Core Flight System (CFS) and automatically generated test cases in order to determine the overlap between the two sets of test cases. In all cases, Dyn-SAVE assisted in providing insightful conclusions about each of the cases identified above.

Lindvall, Mikael↗

Integration of Weather Avoidance and Traffic Separation

This paper describes a dynamic convective weather avoidance concept that compensates for weather motion uncertainties; the integration of this weather avoidance concept into a prototype 4-D trajectory-based Airborne Separation Assurance System (ASAS) application; and test results from a batch (non-piloted) simulation of the integrated application with high traffic densities and a dynamic convective weather model. The weather model can simulate a number of pseudo-random hazardous weather patterns, such as slow- or fast-moving cells and opening or closing weather gaps, and also allows for modeling of onboard weather radar limitations in range and azimuth. The weather avoidance concept employs nested "core" and "avoid" polygons around convective weather cells, and the simulations assess the effectiveness of various avoid polygon sizes in the presence of different weather patterns, using traffic scenarios representing approximately two times the current traffic density in en-route airspace. Results from the simulation experiment show that the weather avoidance concept is effective over a wide range of weather patterns and cell speeds. Avoid polygons that are only 2-3 miles larger than their core polygons are sufficient to account for weather uncertainties in almost all cases, and traffic separation performance does not appear to degrade with the addition of weather polygon avoidance. Additional "lessons learned" from the batch simulation study are discussed in the paper, along with insights for improving the weather avoidance concept. Introduction

Consiglio, Maria C.↗

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision D

This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.

Roberts, Barry C.↗

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision E

The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems.

Roberts, Barry C.↗

Cracking Problems in Low-Voltage Chip Ceramic Capacitors

Cracking remains the major reason of failures in multilayer ceramic capacitors (MLCCs) used in in space electronics. Due to a tight quality control of space-grade components, the probability that as manufactured capacitors have cracks is relatively low, and cracking is often occurs during assembly, handling and the following testing of the systems. Majority of capacitors with cracks are revealed during the integration and testing period, but although extremely rarely, defective parts remain undetected and result in failures during the mission. This situation is aggravated by manual soldering and rework that are often used during low volume production of circuit boards for space. Although failures of MLCCs are often attributed to the post-manufacturing stresses, in many cases they are due to a combination of certain deviations in the manufacturing processes that result in hidden defects in the parts and excessive stresses during assembly and use. This report gives an overview of design, manufacturing and testing processes of MLCCs focusing on elements related to cracking problems. The existing and new screening and qualification procedures and techniques are briefly described and assessed by their effectiveness in revealing cracks. The capability of different test methods to simulate stresses resulting in cracking, mechanisms of failures in capacitors with cracks, and possible methods of selecting the most robust to manual soldering stresses capacitors are discussed.

testing↗

Definition of International GPM GV Research Program

The Global Precipitation Measurement (GPM) Mission will consist of a constellation of rain-measuring satellites, the main member of which (the core satellite) will serve as the measurement reference to the other members of the constellation. The core satellite is being developed jointly by the National Aeronautics and Space Administration (NASA) and the newly-named Japan Aerospace Exploration Agency (JAXA -- previously NASDA) along with its government partner, the Communications Research Laboratory (CRL). The GPM mission was proposed as a follow-up mission to the Tropical Rainfall Measuring Mission (TRMM) by both NASA and NASDA based on the unparalleled scientific success of TRMM, and has recently been joined by the European Space Agency (ESA) via its formulation of the European GPM mission (i.e., EGPM). GPM is an ambitious mission designed to produce accurate and frequent global observations of precipitation (both rain and snow) made possible by replacing the TRMM satellite with the new core satellite carrying an advanced radar-radiometer system, and serving as the centerpiece for the constellation of some eight (8) additional satellites being provided through international cooperation. The core satellite is to be flown up to high latitudes (inclined some 65-70 degrees), and will carry a Ku/Ka-band, nadir-scanning, dual-frequency precipitation radar (DPR) that is being developed by JAXA and CRL, along with a large aperture, extended frequency-range, conically-scanning passive microwave radiometer being developed by NASA and its industrial partners. Each constellation satellite will also carry some type of multi-channel passive microwave radiometer (as well as a multi-beam Ka-band radar in the case of EGPM) whose rain estimates will be calibrated and referenced to those made by the core satellite, producing for the first time fully-global, continuous, and bias-free precipitation datasets. GPM data will be delivered in near-realtime, taking a major step toward the operational use of precipitation information for model initialization and data assimilation in a number of application areas such as hazardous weather forecasting, flood warning, fresh water resource assessment, and crop growth prediction. In addition, GPM data will complement the now-existing global temperature record, allowing for improved assessments of climate change, particularly those processes in which the global water cycle both forces and responds to climatic drifts in global temperature conditions. A foremost element of this international constellation mission is a parallel international ground validation (GV) network. This GV network is needed to determine uncertainties in the rain retrievals, critical for application of the retrieval information in weather and hydrometeorological modeling and climate diagnostics, as well as assurances that the satellite retrievals of surface rainfall are consistent with those actually measured at the surface. The key aspects of this network is that it must be worldwide and created through the GPM partnership process. Therefore the network will consist of a confederation of government agencies, academic organizations, private institutions, and individual scientists from a collection of nations who have initiated the process by gathering in Abingdon to develop the fundamentals of the international GPM GV research programme. Therefore in keeping with our responsibilities as the front-runners of the programme, the main objectives of this workshop are: (1) to present and share opinions on interests, perspectives, and concerns about GPM GV research; (2) to examine the conceptual and/or planned GPM GV site templates from NASA, NASDA, ESA, and other partners; (3) to define the main scientific objectives of the international GPM GV research programme; (4) to formulate a preliminary set of international GPM GV science and measurement requirements; and (5) to convene a Steering Committee to aid the organization of the GPM GV program, to document its science implementation plans, and to aid planning for follow-up GPM GV meetings.

Smith, Eric A.↗

Characterization of frequency standard instability by estimation of their covariance matrix

The popular 3-cornered hat method used for evaluating the noise contributions of individual frequency standards is revisited. This method is used in several cases, but sometimes the results are not consistent because one or more estimated clock variances turn out to be negative. Different causes of this unacceptable result have been conjectured: among them one regards the hypothesis of uncorrelated clocks, essential in this method. Since recently realistic cases of correlation between clocks, mainly due to the environmental conditions, have been observed, this paper proposes an entirely revisited version of the 3-cornered hat method which permits to evaluate the individual variances and also the possible covariances between clocks, by relaxing the hypothesis of uncorrelation. The uncertainty and the lack of contemporaneity of the measurement series are assumed to be negligible. The lack of the uncorrelation hypothesis calls for a more general mathematical model leading to an underdetermined linear system. The estimates of the (co)variances of the measurement series us well us those of the individual clocks are introduced by means of the scalar product of the related time series and arranged in the respective covariance matrices S and R. Since covariance matrix is positive definite by definition, the problem consists in estimating the unknown R, subject to the constraint of positive definiteness, from the known S. Unfortunately, this constraint is not sufficient to estimate R. Therefore a suitable optimization criterion is proposed, which assures the positive definiteness of R and, at the same time, minimizes the global correlation among clocks. Examples of frequency instability measurements processed by the "classical" 3-cornered hat method and the here-revisited method are presented showing that the solutions are identical only when the uncorrelation hypothesis doesn't violate the positive definiteness of R.

PatriziaTravella↗