Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Standards”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗
NASA NTRS1993

Definition of spacecraft standard interfaces by the NASA Space Assembly and Servicing Working Group (SASWG)

The purpose of the NASA Space Assembly and Servicing Working Group (SASWG) is to study enabling technologies for on-orbit spacecraft maintenance and servicing. One key technology required for effective space logistics activity is the development of standard spacecraft interfaces, including the 'Basic Set' defined by NASA, the U.S. Space Command, and industry panelists to be the following: (1) navigation aids; (2) grasping, berthing, and docking; and (3) utility connections for power, data, and fluids. Draft standards have been prepared and referred to professional standards organizations, including the AIAA, EIA, and SAE space standards committee. The objective of the SASWG is to support these committees with the technical expertise required to prepare standards, guidelines, and recommended practices which will be accepted by the ANSI and international standards organizations, including the ISO, IEC, and PASC.

Radtke, Robert↗
NASA NTRS1994

National Center for Standards and Certification Information: Service and programs

The National Center for Standards and Certification Information (NCSCI) provides information on U.S., foreign and international voluntary standards, government regulations, and conformity assessment procedures for non-agricultural products. The Center serves as a referral service and focal point in the United States for information on standards and standards-related information. NCSCI staff respond to inquiries, maintain a reference collection of standards and standards-related documents, and serve as the U.S. inquiry point for information to and from foreign countries.

Overman, Joanne↗
NASA NTRS1994

The ESA standard for telemetry and telecommand packet utilisation: PUS

ESA has developed standards for packet telemetry and telecommand, which are derived from the recommendations of the Inter-Agency Consultative Committee for Space Data Systems (CCSDS). These standards are now mandatory for future ESA programs as well as for many programs currently under development. However, while these packet standards address the end-to-end transfer of telemetry and telecommand data between applications on the ground and Application Processes on-board, they leave open the internal structure or content of the packets. This paper presents the ESA Packet Utilization Standard (PUS) which addresses this very subject and, as such, serves to extend and complement the ESA packet standards. The goal of the PUS is to be applicable to future ESA missions in all application areas (Telecommunications, Science, Earth Resources, microgravity, etc.). The production of the PUS falls under the responsibility of the ESA Committee for Operations and EGSE Standards (COES).

Kaufeler, Jean-Francois↗
NASA NTRS2003

Standards-and Component-Based Mission Operations Architecture at NASA's Goddard Space Flight Center

NASA Goddard Space Flight Center (GSFC) manages many of NASA s earth and space science satellite missions. A wide variety of commercial products and GSFC-developed software components are typically integrated into a unique system configuration for each mission. Independent development of the many mission operations center systems has led to systems that are expensive to integrate, difficult to infuse with new capabilities developed for other programs, and cumbersome to maintain. This traditional approach becomes even more problematic as NASA moves towards satellite constellations, new operations concepts, and even further budgets reductions. The GSFC Mission Services Evolution Center (GMSEC) is creating a new architecture for future missions at GSFC. Instead of selecting the best-in-class components and creating a standard control center system, GMSEC is developing component interface standards so that multiple products can plug-and-play into the configuration. Missions can then select the best components based on the merits of the product and not simply based on recent integration history at NASA. The GMSEC system utilizes a publish/subscribe information bus and standard XML-based key message interfaces. Functional components can either match directly to the interface standard, or adapters can be developed to match the product's interface to the GMSEC standard with out impacting the source product. Applications Program Interfaces (API's) are being developed to isolate the underlying middleware from the applications software and to allow the middleware product to be switched if necessary. Interface Control Documents (ICDs) between each pair of communicating components is replaced by a single message/API specification document. New applications must simply match to the information bus standards and need not worry about all of the other applications in the system. For legacy software, adapters can be developed to facilitate communications between the application and the information bus. As the approach has matured, it has become apparent that it can provide innovative solutions to some of the multi-satellite challenges facing GSFC.

Smith, Danford↗
NASA NTRS2003

Standards Advisor-Advanced Information Technology for Advanced Information Delivery

Developers of space systems must deal with an increasing amount of information in responding to extensive requirements and standards from numerous sources. Accessing these requirements and standards, understanding them, comparing them, negotiating them and responding to them is often an overwhelming task. There are resources to aid the space systems developer, such as lessons learned and best practices. Again, though, accessing, understanding, and using this information is often more difficult than helpful. This results in space systems that: 1. Do not meet all their requirements. 2. Do not incorporate prior engineering experience. 3. Cost more to develop. 4. Take longer to develop. The NASA Technical Standards Program (NTSP) web site at http://standards.nasa.gov has made significant improvements in making standards, lessons learned, and related material available to space systems developers agency-wide. The Standards Advisor was conceived to take the next steps beyond the current product, continuing to apply evolving information technology that continues to improve information delivery to space systems developers. This report describes the features of the Standards Advisor and suggests a technical approach to its development.

Hawker, J. Scott↗
NASA NTRS2007

NASA's Software Safety Standard

NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.

Ramsay, Christopher M.↗
NASA NTRS2007

Standardization of XML Database Exchanges and the James Webb Space Telescope Experience

Personnel from the National Aeronautics and Space Administration (NASA) James Webb Space Telescope (JWST) Project have been working with various standard communities such the Object Management Group (OMG) and the Consultative Committee for Space Data Systems (CCSDS) to assist in the definition of a common extensible Markup Language (XML) for database exchange format. The CCSDS and OMG standards are intended for the exchange of core command and telemetry information, not for all database information needed to exercise a NASA space mission. The mission-specific database, containing all the information needed for a space mission, is translated from/to the standard using a translator. The standard is meant to provide a system that encompasses 90% of the information needed for command and telemetry processing. This paper will discuss standardization of the XML database exchange format, tools used, and the JWST experience, as well as future work with XML standard groups both commercial and government.

Gal-Edd, Jonathan↗
NASA NTRS2007

Defining the Core Archive Data Standards of the International Planetary Data Alliance (IPDA)

A goal of the International Planetary Data Alliance (lPDA) is to develop a set of archive data standards that enable the sharing of scientific data across international agencies and missions. To help achieve this goal, the IPDA steering committee initiated a six month proj ect to write requirements for and draft an information model based on the Planetary Data System (PDS) archive data standards. The project had a special emphasis on data formats. A set of use case scenarios were first developed from which a set of requirements were derived for the IPDA archive data standards. The special emphasis on data formats was addressed by identifying data formats that have been used by PDS nodes and other agencies in the creation of successful data sets for the Planetary Data System (PDS). The dependency of the IPDA information model on the PDS archive standards required the compilation of a formal specification of the archive standards currently in use by the PDS. An ontology modelling tool was chosen to capture the information model from various sources including the Planetary Science Data Dictionary [I] and the PDS Standards Reference [2]. Exports of the modelling information from the tool database were used to produce the information model document using an object-oriented notation for presenting the model. The tool exports can also be used for software development and are directly accessible by semantic web applications.

ontology↗
NASA NTRS2010

Dichotomy of Solar Coronal Jets: Standard Jets and Blowout Jets

By examining many X-ray jets in Hinode/XRT coronal X-ray movies of the polar coronal holes, we found that there is a dichotomy of polar X-ray jets. About two thirds fit the standard reconnection picture for coronal jets, and about one third are another type. We present observations indicating that the non-standard jets are counterparts of erupting-loop H alpha macrospicules, jets in which the jet-base magnetic arch undergoes a miniature version of the blowout eruptions that produce major CMEs. From the coronal X-ray movies we present in detail two typical standard X-ray jets and two typical blowout X-ray jets that were also caught in He II 304 Angstrom snapshots from STEREO/EUVI. The distinguishing features of blowout X-ray jets are (1) X-ray brightening inside the base arch in addition to the outside bright point that standard jets have, (2) blowout eruption of the base arch's core field, often carrying a filament of cool (T ~10(exp 4) - 10(exp 5) K) plasma, and (3) an extra jet-spire strand rooted close to the bright point. We present cartoons showing how reconnection during blowout eruption of the base arch could produce the observed features of blowout X-ray jets. We infer that (1) the standard-jet/blowout-jet dichotomy of coronal jets results from the dichotomy of base arches that do not have and base arches that do have enough shear and twist to erupt open, and (2) there is a large class of spicules that are standard jets and a comparably large class of spicules that are blowout jets.

Moore, R. L.↗
NASA NTRS2011

JSC Design and Procedural Standards, JSC-STD-8080

This document provides design and procedural requirements appropriate for inclusion in specifications for any human spaceflight program, project, spacecraft, system, or end item. The term "spacecraft" as used in the standards includes launch vehicles, orbital vehicles, non-terrestrial surface vehicles, and modules. The standards are developed and maintained as directed by Johnson Space Center (JSC) Policy Directive JPD 8080.2, JSC Design and Procedural Standards for Human Space Flight Equipment. The Design and Procedural Standards contained in this manual represent human spacecraft design and operational knowledge applicable to a wide range of spaceflight activities. These standards are imposed on JSC human spaceflight equipment through JPD 8080.2. Designers shall comply with all design standards applicable to their design effort.

Punch, Danny T.↗
NASA NTRS2012

NASA-STD-3001, Space Flight Human-System Standard and the Human Integration Design Handbook

NASA-STD-3001 Space Flight Human-System Standard Volume 1, Crew Health, Volume 2, Human Factors, Habitability and Environmental Health, and the Human Integration Design Handbook (HIDH) have replaced the Man-Systems Integration Standards (MSIS), NASA-STD-3000. For decades, NASA-STD-3000 was a significant contribution to human spaceflight programs and to human-systems integration. However, with research program and project results being realized, advances in technology, and the availability of new information in a variety of topic areas, the time had arrived to update this extensive suite of standards and design information. NASA-STD-3001, Volume 2 contains the Agency level standards from the human and environmental factors disciplines that ensure human spaceflight operations are performed safely, efficiently, and effectively. The HIDH is organized in the same sequence and serves as the companion document to NASA-STD-3001, Volume 2, providing a compendium of human spaceflight history and knowledge. The HIDH is intended to aid interpretation of NASA-STD-3001, Volume 2 standards and to provide guidance for requirement writers and vehicle and habitat designers. Keywords Human Factors, Standards, Environmental Factors, NASA

Whitmore, Mihriban↗
NASA NTRS2015

Planning the Unplanned Experiment: Assessing the Efficacy of Standards for Safety Critical Software

We need well-founded means of determining whether software is t for use in safety-critical applications. While software in industries such as aviation has an excellent safety record, the fact that software aws have contributed to deaths illustrates the need for justi ably high con dence in software. It is often argued that software is t for safety-critical use because it conforms to a standard for software in safety-critical systems. But little is known about whether such standards `work.' Reliance upon a standard without knowing whether it works is an experiment; without collecting data to assess the standard, this experiment is unplanned. This paper reports on a workshop intended to explore how standards could practicably be assessed. Planning the Unplanned Experiment: Assessing the Ecacy of Standards for Safety Critical Software (AESSCS) was held on 13 May 2014 in conjunction with the European Dependable Computing Conference (EDCC). We summarize and elaborate on the workshop's discussion of the topic, including both the presented positions and the dialogue that ensued.

Graydon, Patrick J.↗
NASA NTRS2015

Planning the Unplanned Experiment: Towards Assessing the Efficacy of Standards for Safety-Critical Software

Safe use of software in safety-critical applications requires well-founded means of determining whether software is fit for such use. While software in industries such as aviation has a good safety record, little is known about whether standards for software in safety-critical applications 'work' (or even what that means). It is often (implicitly) argued that software is fit for safety-critical use because it conforms to an appropriate standard. Without knowing whether a standard works, such reliance is an experiment; without carefully collecting assessment data, that experiment is unplanned. To help plan the experiment, we organized a workshop to develop practical ideas for assessing software safety standards. In this paper, we relate and elaborate on the workshop discussion, which revealed subtle but important study design considerations and practical barriers to collecting appropriate historical data and recruiting appropriate experimental subjects. We discuss assessing standards as written and as applied, several candidate definitions for what it means for a standard to 'work,' and key assessment strategies and study techniques and the pros and cons of each. Finally, we conclude with thoughts about the kinds of research that will be required and how academia, industry, and regulators might collaborate to overcome the noted barriers.

Graydon, Patrick J.↗
NASA NTRSDate not supplied

Results of the Field Test and Defining Sensormotor Fitness for Duty Standards

The primary goals of the Field Test were (1) to determine functional abilities associated with long-duration space flight crews beginning as soon after landing as possible (< 2 hours), and (2) to characterize the time course of recovery with additional follow-up measurement sessions within 24 hours after landing. The NASA and Russian teams have collected data on a total of 39 different United States Orbital Segment (USOS) and Russian crewmembers, with 9 Russian crewmembers being tested twice (total of 48 tests). Eighteen subjects (7 Russian, 11 USOS) completed a reduced Field Test (pilot) protocol and 30 subjects (19 Russian and 11 USOS) participated in the full Field Test. This presentation will focus on a subset of the measures that will be used in the upcoming ground study to determine sensorimotor fitness for duty standards, namely: tandem walk, obstacle walk, eye-hand coordination task, finger-to-nose task, and Computerized Dynamic Posturography (CDP). Exploration-class missions including Artemis, Gateway, and beyond will require a new level of autonomy around periods of gravitational transition, where sensorimotor disturbances increase. The operational support that is available upon return to Earth including rescue teams, medical interventions, and the ability to rest as needed will not be available after landing on the lunar or Martian surface. Because of this, there is a need to define fitness for duty standards that will help inform crew capabilities during and soon after gravitational transitions. Due to the new requirements of the exploration environment, we must utilize a set of exploration field measures, for which no previous spaceflight data exists to define fitness for duty standards. A Sensorimotor Adaptation Analog (SAA) that can provide different levels of acute disorientation through combined vestibular, visual, and proprioceptive disruptions will be used to increase the range of performance in exploration field measures, simulating the moderate-to-severe performance decrements observed in spaceflight. The levels of SAA will be titrated and validated by comparison to gold standard measures that have a wealth of spaceflight data at different time points during recovery. These data will be pulled directly from the results of Field Test and help ensure the range of performance while being exposed to SAA mimics the range of performance from pre-flight to immediately postflight in Field Test subjects. Specifically, we will be using the tandem walk, obstacle walk, eye-hand coordination task, finger-to-nose task, and CDP as the gold standard measures. Referencing this Field Test data in the form of gold standard measures will also help us characterize and contextualize how each magnitude of SAA disorientation compares to recovery from long-term microgravity exposure.

M J F Rosenberg↗
NASA NTRSDate not supplied

Assessing the Needs for Space Reactor Standards

A U.S. governmental interagency space reactor standards working group (SWG) was convened to address the limited availability of voluntary consensus standards currently in place specifically for space nuclear reactor design and safety. The SWG focused on reviewing existing standards, assessing agency needs, specifying gaps that could be addressed by new standards, and prioritizing those gaps through consensus group deliberations. The SWG identified a series of findings and recommendations relative to the development of space reactor standards, including moving three specific high-priority gap items to be pursued through a consensus standards development process: Safety and Risk Analysis Methods for Space Reactors, Testing Requirements for Space Reactors, including Facility Requirements, and Safe Operating Practices for Space Reactors.

Andrew Klein↗
NASA NTRSDate not supplied

Research Needs for Developing Qualification Standards for Flight Simulation Training Devices with Head Mounted Displays

This presentation discusses research needs to support evidence-based qualification standards for Flight Simulation Training Devices (FSTDs) with head mounted displays (HMDs). Currently, the FAA and EASA have no qualification standards specifically for FSTDs using HMDs and extended reality (XR) visuals, and existing qualification standards may not be sufficient. Special Conditions can be prescribed for the evaluation and qualification of individual devices, but these Special Conditions need to be assessed and adjusted on a case-by-case basis resulting in an elaborate process. Furthermore, test tolerances used in Special Conditions are often based on conventional visual systems and may not be adequate. This presentation first identifies gaps in the current knowledge of using HMDs in pilot training, and, more specifically, using HMDs in the training of manual aircraft control with motion cues. Next, research is proposed to help close these gaps, inform the development of qualification criteria and tolerances, and guide efforts to update regulations. The Vertical Motion Simulator (VMS) at NASA Ames Research Center, with its large motion capability, is currently undergoing significant upgrades including a state-of-the-art out-the-window visual system. In addition, an HMD capability will be introduced to use in conjunction with the conventional visual system. With its long history of setting standards in the simulation industry, the VMS is the ultimate tool to conduct research that could help accelerate the development of standards for the use of HMDs in FSTDs. The goal of the talk is ultimately to spark a discussion about the research needs and priorities to best serve the development of new qualification standards.

XR↗
NASA NTRS2022

Report of the Interagency Space Reactor Standards Working Group

A U.S. governmental interagency space reactor standards working group (SWG) was convened in April 2021 with a memo from the NASA Chief Engineer to address the limited standards and regulations in place specifically for space reactor design and safety. The convening memo requested support from the Standards Executives of six other federal agencies. The Standards Executives agreed to support a 6-month study to assess the need for consensus standards and identified SWG representatives from each agency. This report summarizes the SWG’s study, their findings, and their recommendations.

Space Reactor Standards Working Group↗