SEARCH · Engineering Papers
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.
The following subject areas are covered: a DOD development system - the Army Secure Operating System; non-development commercial computer systems; security, integrity, and assurance of service (SI and A); post delivery SI and A and malicious software; computer system unique attributes; positive feedback to commercial computer systems vendors; and NDI (Non-Development Item) computers and software safety.
The Sampler sequence was introduced into the SCALE nuclear modeling and simulation suite in SCALE 6.2 to perform uncertainty quantification via random sampling of nuclear data, material number densities, and dimensions. Sampler was expanded with the introduction of a parametric capability in SCALE 6.2.2. This paper discusses input for the Sampler parametric sequence and presents two case studies of analyses performed using the sequence. These case studies include preconceptual design of a package for transporting high assay low-enriched uranium (HALEU) oxide and scoping calculations to support subcritical limit development for a future update of the ANSI/ANS-8.1 (ANS-8.1) standard. The parametric capability within Sampler provides many benefits to analysts. For instance, parametric sweeps are frequently used to identify optimum parameter values as part of safety analysis or system design, but such sweeps can require substantial engineering time or may rely on custom-written scripts or scripts such as Write One, Run Many (or WORM) developed outside of any software quality assurance program. With the parametric capabilities in Sampler, however, a large number of inputs can be generated automatically without recourse to scripting by individual analysts. The parametric capability can also be used in lieu of the CSAS5S search sequence to identify optimum parameters more simply with straightforward inputs and outputs. Sampler can also be used to calculate input parameters from engineering specifications. For example, diameters can be converted to radii, or masses can be used to calculate number densities. Overall, the Sampler parametric capability provides a robust feature within SCALE, eliminating the need for user-developed scripting.
Human-rated missions like Orion are becoming exceedingly complex in terms of software contribution to achieving mission objectives, and this creates a resource challenge for everyone whose job is to add assurance that the mission is going to fly safely. Orion IV&V has addressed this challenge by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V was evaluating areas of risk in much broader, and more static, terms. Due to the Agile software development cycle that Orion follows, IV&V findings were often reported months out of phase with the developer. As a result of evolving the approach to providing assurance on Orion, IV&V is able to incrementally deliver high-priority assurance data and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This presentation will discuss the principles which drive the design of our approach, results to date, and aspirations for long-term performance.
As demands increase to use unmanned aircraft systems (UAS) for a broad spectrum of commercial applications, regulatory authorities are examining how to safely integrate them without loss of safety or major disruption to existing airspace operations. This work addresses the development of the Safeguard system as an assured safety net technology for UAS. The Safeguard system monitors and enforces conformance to a set of rules defined prior to flight (e.g., geospatial stay-out or stay-in regions, speed limits, altitude limits). Safeguard operates independently of the UAS autopilot and is strategically designed in a way that can be realized by a small set of verifiable functions to simplify compliance with regulatory standards for commercial aircraft. A framework is described that decouples the system from any other devices on the UAS as well as introduces complementary positioning source(s) for applications that require integrity and availability beyond what the Global Positioning System (GPS) can provide. Additionally, the high level logic embedded within the software is presented, as well as the steps being taken toward verification and validation (V&V) of proper functionality. Next, an initial prototype implementation of the described system is disclosed. Lastly, future work including development, testing, and system V&V is summarized.
NASA’s System-Wide Safety project is developing the concept and requirements for an assured In-Time Aviation Safety Management System (IASMS) that will: Improve the efficiency of flight, the access to airspace, and the expansion of services provided by air vehicles; Explore, discover, and understand the impact on safety from growing complexity introduced by industry modernization; Develop and demonstrate innovative solutions that enable the aviation transformation envisioned for global airspace system; Identify and proactively mitigate risks in accordance with target levels of safety; Assure safe, rapid, and repeatable access to a transformed National Airspace System (NAS)
There is a trend in the aviation industry to go from federated to integrated computing systems. Combining a number of traditional stand-alone federated systems into an integrated common platform (called Integrated Modular Avionics, IMA) has the benefit of increased power efficiency, reduced support hardware, and reduced cabling. However, changing from federated to integrated has a significant impact on the system architecture and hence the process of how avionic systems are to be analyzed. Traditional approaches to safety analysis become inefficient when functional boundaries can no longer be assumed for failure independence and fault isolation. In this report, we describe a tool that we developed to accelerate the safety engineer's ability to perform safety analysis of IMA systems through modeling, as well as optimize the system engineer's ability to develop a system through architecture synthesis. This work was the result of a three-year research effort called SOTERIA (Safe and Optimal Techniques Enabling Recovery, Integrity, and Assurance). We developed a compositional modeling language that supports rapid development, modification, and evaluation of architectures. The modeling language is structured such that the end-user defines a library of components with information on component reliability, connectivity, and fault propagation logic. The system model is built by instantiating the components from the library, connecting the components, and identifying the top-level faults of interest. Our tool is compositional in that the end-user only needs to define safety aspects at the component level. The tool takes the model and automatically synthesizes both the qualitative and quantitative safety analyses. We go further by allowing users to describe system information such as components to use in an architecture and their connection compatibility and automatically synthesize an architecture that meets the top-level probability target adhering to end-user specified constraints. This capability allows users to rapidly explore a design space..
Developing a long-range manifest begins with the assessment of flight rate capability for the next 6 years. Payloads priorities, launch readiness, and service needs are reviewed and compatible mixed cargo flights are determined and integrated with the dedicated missions to become the manifest. Manifest development must also address Orbiter upgrades to assure that payload-related enhancements meet need dates and that new hardware integration does not adversely affect flight rate capability. A series of Space Shuttle upgrades and new capabilities are in development driven by a continuing effort to improve safety margins, support recognized payload needs, and unique SSF requirements. These enhancements include extended mission duration capability, ASRM development, extended middeck payload support capability, and improved attitude control systems.
The Airspace Systems Program is committed to supporting the Next Generation Air Transportation System through research and development in select areas. One such area, referred to as Super Density Operations, is conducting research to develop technologies that will safely increase the throughput in busy terminal area environments. The purpose of this document is to develop a Concept of Operations for the Tactical Separation Assurance function, one of the functions included in Super Density Operations. A functional description of the technologies required for Super Density Operations is presented followed by a more detail description of the Tactical Separation Assurance function. Two story boards are presented to illustrate the operational use of the Tactical Separation Assurance function under different situations. The last section proposes a pathway to implementing the Tactical Separation Assurance function.
The spacecraft was nearly integrated and had passed some of its early mechanical and electrical testing. One of its instruments, the Proportional Counter Array (PCA), had a gas leak in one of the five proportional counter modules that made up the array. The science division where the instrument was being developed wanted a gas replenishment system added to assure the PCA would last for the entire mission. Adding a gas replenishment system would mean interrupting spacecraft integration and testing; developing a new subsystem and integrating it onto the spacecraft; modifying all the PCA modules; including a complex integration of the instrument onto the spacecraft; and implementing a more complex performance and environmental test process. It was the wrong answer because it made a simple design more complex and added little value to the mission at a major cost in time and dollars. Our mission couldn't afford the additional budget and schedule risks. XTE was the latest of a long line of projects being managed by my Explorer Program Office, but it was unique in being the first project we had agreed to do for a fixed price. NASA HQ agreed, in return, to provide us with the funding profile we needed to make it happen. We were both trying to break the unhealthy spiral in the Explorer program that saw current missions overrunning and pushing subsequent missions downstream to the point where their science was becoming marginal. The science community was upset and wanted better performance from NASA. I summarized my arguments to the director. The Engineering Directorate had taken responsibility for the spacecraft development when we established XTE as an in-house project at Goddard Space Flight Center, and also was supporting the PCA development. "It adds complexity," I reiterated. "It's a significant cost impact for only a marginal reliability increase". His response was music to my ears, "Jim, I won't stand in your way, but you'll have to convince the scientists and engineers."
Quality assurance R and D for product design and operational integrity in manned space flight, noting space developments application to aircraft safety
The development of a culture of safety and NASA since the Challenger accident is reviewed. The technical elements of the strengthened NASA safety program are described, including problem reporting, risk/assessment/risk management, operational safety, and safety assurance are addressed. Future directions in the development of safety are considered.
A preliminary survey of existing separation assurance and collision avoidance advancements, technologies, and efforts has been conducted in order to develop a concept of operations for flight testing autonomous separation assurance at Dryden Flight Research Center. This effort was part of the Unmanned Aerial Systems in the National Airspace System project. The survey focused primarily on separation assurance projects validated through flight testing (including lessons learned), however current forays into the field were also examined. Comparisons between current Dryden flight and range assets were conducted using House of Quality matrices in order to allow project management to make determinations regarding asset utilization for future flight tests. This was conducted in order to establish a body of knowledge of the current collision avoidance landscape, and thus focus Dryden s efforts more effectively towards the providing of assets and test ranges for future flight testing within this research field.
The National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) is investigating current and anticipated wireless communications concepts and technologies that the National Airspace System (NAS) may need in the next 50 years. NASA has awarded three NASA Research Announcements (NAR) studies with the objective to determine the most promising candidate technologies for air-to-air and air-to-ground data exchange and analyze their suitability in a post-NextGen NAS environment. This paper will present progress made in the studies and describe the communications challenges and opportunities that have been identified as part of the study. NASA's NextGen Concepts and Technology Development (CTD) Project integrates solutions for a safe, efficient and high-capacity airspace system through joint research efforts and partnerships with other government agencies. The CTD Project is one of two within NASA's Airspace Systems Program and is managed by the NASA Ames Research Center. Research within the CTD Project is in support the 2011 NASA Strategic Plan Sub-Goal 4.1: Develop innovative solutions and advanced technologies, through a balanced research portfolio, to improve current and future air transportation. The focus of CTD is on developing capabilities in traffic flow management, dynamic airspace configuration, separation assurance, super density operations and airport surface operations. Important to its research is the development of human/automation information requirements and decisionmaking guidelines for human-human and human-machine airportal decision-making. Airborne separation, oceanic intrail climb/descent and interval management applications depend on location and intent information of surrounding aircraft. ADS-B has been proposed to provide the information exchange, but other candidates such as satellite-based receivers, broadband or airborne internet, and cellular communications are possible candidate's.
This paper will present data related to software development processes and personnel involvement from the perspective of software quality assurance. We examine eight years of data collected from six projects. Data collected varied by project but usually included defect and fault density with limited use of code metrics, schedule adherence, and budget growth information. The data are a blend of AFSCP 800-14 and suggested productivity measures in Software Metrics: A Practioner's Guide to Improved Product Development. A software quality assurance database tool, SQUID, was used to store and tabulate the data.
New processes, methods and tools are constantly appearing in the field of software engineering. Many of these augur great potential in improving software development processes, resulting in higher quality software with greater levels of assurance. However, there are a number of obstacles that impede their infusion into software development practices. These are the recurring obstacles common to many forms of research. Practitioners cannot readily identify the emerging techniques that may most benefit them, and cannot afford to risk time and effort in evaluating and experimenting with them while there is still uncertainty about whether they will have payoff in this particular context. Similarly, researchers cannot readily identify those practitioners whose problems would be amenable to their techniques and lack the feedback from practical applications necessary to help them to evolve their techniques to make them more likely to be successful. This paper describes an ongoing effort conducted by a software engineering research infusion team, and the NASA Research Infusion Initiative, established by NASA s Software Engineering Initiative, to overcome these obstacles.
The research performed under this contract involved definition of the natural environmental parameters affecting the design, development, and operation of space and launch vehicles. The Universities Space Research Association (USRA) provided the manpower and resources to accomplish the following tasks: defining environmental parameters critical for design, development, and operation of launch vehicles; defining environmental forecasts required to assure optimal utilization of launch vehicles; and defining orbital environments of operation and developing models on environmental parameters affecting launch vehicle operations.
The NASA Chief Health and Medical Officer (CHMO) recently directed that the agency establish crew health standards to aid in the development of requirements for future vehicles and habitats. Response to this direction includes development of a new NASA habitability and human factors standard and an accompanying design handbook. The new standard contains high-level, over-arching principles to assure its applicability and usability across all NASA development programs. The handbook will provide detailed design requirements and suggestions that will meet the standards. The information contained in NASA-STD-3000 will be updated and included in the new design handbook. In this approach, each new program will derive detailed program-specific requirements from the new standard using the handbook as a design guide and resource. With the completion of the standard, the focus of this year s effort is the development of the new handbook: Human Integration Design Handbook (HIDH). This is an opportunity for the space flight human factors and habitability community to consolidate up-to-date data for use by NASA programs and designers as well as outside researchers and policy makers looking for the next research focus. The goal of the handbook is to help NASA design and build human space flight systems which accommodate the capabilities and limitations of the crew so as to provide an environment where the crew can live and work effectively, safely, and comfortably. Handbook contents will address that primary goal, addressing unique aspects of space flight and habitation, including reduced gravity conditions, time lags, EVA systems and day/night cycles, not addressed in other standards or handbooks. The handbook will be divided into topics similar to NASA-STD-3000 (anthropometrics, architecture, workstations, etc.) and each topic area will contain elements for designers, human factors practitioners, program managers, operators, and researchers. The handbook will include the following elements: (1) Design considerations include a clear and concise summary of what is important to designers in space vehicle / habitat design, design information to translate Earth-base knowledge to the space environment, space issues and the data necessary to address those issues, and a consistent set of terminology. (2) Updates to Lessons Learned and example solutions from Shuttle and Station program experience will provide historical examples to help prevent repeating mistakes or reinvention of the wheel. (3) Requirements will aid in the translation of standards into program specific requirements. The scope of included requirements will define the pool that each program needs to consider and tailor for their specific program. (4) Requirements rationale will help understanding of the importance of these considerations. The HIDH development team at JSC is finalizing the format of the new handbook, prioritizing topic areas for expansion and update, and contacting subject matter experts within the scientific community to assist with this effort. Plans are also being made to continue handbook expansion and maintenance to assure it remains a valuable resource for human factors and human space flight programs.
The reliability and quality assurance system and procedures used in developing test equipment for the Lunar Experiment projects are described. The subjects discussed include the following: (1) documentation control, (2) design review, (3) parts and materials selection, (4) material procurement, (5) inspection procedures, (6) qualification and special testing, and failure modes and effects analysis.