Results for “specifications standards” — Page 6

NASA NTRS2017

Commercial Off-The-Shelf (COTS) Parts Risk and Reliability User and Application Guide

All COTS parts are not created equal. Because they are not created equal, the notion that one can force the commercial industry to follow a set of military specifications and standards, along with the certifications, audits and qualification commitments that go with them, is unrealistic for the sale of a few parts. The part technologies that are Defense Logistics Agency (DLA) certified or Military Specification (MS) qualified, are several generations behind the state-of-the-art high-performance parts that are required for the compact, higher performing systems for the next generation of spacecraft and instruments. The majority of the part suppliers are focused on the portion of the market that is producing high-tech commercial products and systems. To that end, in order to compete in the high performance and leading edge advanced technological systems, an alternative approach to risk assessment and reliability prediction must be considered.

White, Mark↗

NASA NTRS1993

The systems engineering overview and process (from the Systems Engineering Management Guide, 1990)

The past several decades have seen the rise of large, highly interactive systems that are on the forward edge of technology. As a result of this growth and the increased usage of digital systems (computers and software), the concept of systems engineering has gained increasing attention. Some of this attention is no doubt due to large program failures which possibly could have been avoided, or at least mitigated, through the use of systems engineering principles. The complexity of modern day weapon systems requires conscious application of systems engineering concepts to ensure producible, operable and supportable systems that satisfy mission requirements. Although many authors have traced the roots of systems engineering to earlier dates, the initial formalization of the systems engineering process for military development began to surface in the mid-1950s on the ballistic missile programs. These early ballistic missile development programs marked the emergence of engineering discipline 'specialists' which has since continued to grow. Each of these specialties not only has a need to take data from the overall development process, but also to supply data, in the form of requirements and analysis results, to the process. A number of technical instructions, military standards and specifications, and manuals were developed as a result of these development programs. In particular, MILSTD-499 was issued in 1969 to assist both government and contractor personnel in defining the systems engineering effort in support of defense acquisition programs. This standard was updated to MIL-STD499A in 1974, and formed the foundation for current application of systems engineering principles to military development programs.

Source record↗

NASA NTRS2001

Lessons Learned and Technical Standards: A Logical Marriage

A comprehensive database of lessons learned that corresponds with relevant technical standards would be a boon to technical personnel and standards developers. The authors discuss the emergence of one such database within NASA, and show how and why the incorporation of lessons learned into technical standards databases can be an indispensable tool for government and industry. Passed down from parent to child, teacher to pupil, and from senior to junior employees, lessons learned have been the basis for our accomplishments throughout the ages. Government and industry, too, have long recognized the need to systematically document And utilize the knowledge gained from past experiences in order to avoid the repetition of failures and mishaps. The use of lessons learned is a principle component of any organizational culture committed to continuous improvement. They have formed the foundation for discoveries, inventions, improvements, textbooks, and technical standards. Technical standards are a very logical way to communicate these lessons. Using the time-honored tradition of passing on lessons learned while utilizing the newest in information technology, the National Aeronautics and Space Administration (NASA) has launched an intensive effort to link lessons learned with specific technical standards through various Internet databases. This article will discuss the importance of lessons learned to engineers, the difficulty in finding relevant lessons learned while engaged in an engineering project, and the new NASA project that can help alleviate this difficulty. The article will conclude with recommendations for more expanded cross-sectoral uses of lessons learned with reference to technical standards.

Gill, Paul↗

NASA NTRS2013

Science Data Preservation: Implementation and Why It Is Important

Remote Sensing data generation by NASA to study Earth s geophysical processes was initiated in 1960 with the launch of the first Television Infrared Observation Satellite Program (TIROS), to develop a meteorological satellite information system. What would be deemed as a primitive data set by today s standards, early Earth science missions were the foundation upon which today s remote sensing instruments have built their scientific success, and tomorrow s instruments will yield science not yet imagined. NASA Scientific Data Stewardship requirements have been documented to ensure the long term preservation and usability of remote sensing science data. In recent years, the Federation of Earth Science Information Partners and NASA s Earth Science Data System Working Groups have organized committees that specifically examine standards, processes, and ontologies that can best be employed for the preservation of remote sensing data, supporting documentation, and data provenance information. This presentation describes the activities, issues, and implementations, guided by the NASA Earth Science Data Preservation Content Specification (423-SPEC-001), for preserving instrument characteristics, and data processing and science information generated for 20 Earth science instruments, spanning 40 years of geophysical measurements, at the NASA s Goddard Earth Sciences Data and Information Services Center (GES DISC). In addition, unanticipated preservation/implementation questions and issues in the implementation process are presented.

Kempler, Steven J.↗

NASA NTRS1991

Lightning testing at the subsystem level

Testing at the subsystem or black box level for lightning hardness is required if system hardness is to be assured at the system level. The often applied philosophy of lighting testing only at the system level leads to extensive end of the line design changes which result in excessive costs and time delays. In order to perform testing at the subsystem level two important factors must be defined to make the testing simulation meaningful. The first factor is the definition of the test stimulus appropriate to the subsystem level. Application of system level stimulations to the subsystem level usually leads to significant overdesign of the subsystem which is not necessary and may impair normal subsystem performance. The second factor is the availability of test equipment needed to provide the subsystem level lightning stimulation. Equipment for testing at this level should be portable or at least movable to enable efficient testing in a design laboratory environment. Large fixed test installations for system level tests are not readily available for use by the design engineers at the subsystem level and usually require special operating skills. The two factors, stimulation level and test equipment availability, must be evaluated together in order to produce a practical, workable test standard. The neglect or subordination of either factor will guarantee failure in generating the standard. It is not unusual to hear that test standards or specifications are waived because a specified stimulation level cannot be accomplished by in-house or independent test facilities. Determination of subsystem lightning simulation level requires a knowledge and evaluation of field coupling modes, peak and median levels of voltages and currents, bandwidths, and repetition rates. Practical limitations on test systems may require tradeoffs in lightning stimulation parameters in order to build practical test equipment. Peak power levels that can be generated at specified bandwidths with standard electrical components must be considered in the design and costing of the test system. Stimulation tests equipment and test methods are closely related and must be considered a test system for lightning simulation. A non-perfect specification that can be reliably and repeatedly applied at the subsystem test level is more desirable than a perfect specification that cannot be applied at all.

Luteran, Frank↗

NASA NTRS2018

Trajectory Specification Language for Air Traffic Control

Trajectory Specification is a method of specifying aircraft trajectories with tolerances such that the position at any instant in time is constrained to a precisely defined bounding space. The bounding space at any instant in time is defined by tolerances relative to a reference trajectory that specifies position as a function of time. The tolerances are dynamic and are based on the aircraft navigation capabilities and the traffic situation. This paper proposes a standard Trajectory Specification Language (TSL) based on the Extensible Markup Language (XML) to represent these specifications and to communicate them by datalink. The language can be used to downlink trajectory requests from air to ground and to uplink trajectory assignments from ground to air. The XML format can be converted to binary for operational use, if necessary, using Efficient XML Interchange (EXI) or Abstract Syntax Notation (ASN.1).

XM↗

NASA NTRS2016

Providing Comprehensive and Consistent Access to Astronomical Observatory Archive Data: The NASA Archive Model

Since the turn of the millennium a constant concern of astronomical archives have begun providing data to the public through standardized protocols unifying data from disparate physical sources and wavebands across the electromagnetic spectrum into an astronomical virtual observatory (VO). In October 2014, NASA began support for the NASA Astronomical Virtual Observatories (NAVO) program to coordinate the efforts of NASA astronomy archives in providing data to users through implementation of protocols agreed within the International Virtual Observatory Alliance (IVOA). A major goal of the NAVO collaboration has been to step back from a piecemeal implementation of IVOA standards and define what the appropriate presence for the US and NASA astronomy archives in the VO should be. This includes evaluating what optional capabilities in the standards need to be supported, the specific versions of standards that should be used, and returning feedback to the IVOA, to support modifications as needed. We discuss a standard archive model developed by the NAVO for data archive presence in the virtual observatory built upon a consistent framework of standards defined by the IVOA. Our standard model provides for discovery of resources through the VO registries, access to observation and object data, downloads of image and spectral data and general access to archival datasets. It defines specific protocol versions, minimum capabilities, and all dependencies. The model will evolve as the capabilities of the virtual observatory and needs of the community change.

Virtual observatory; data archives; standards; IVO↗

NASA NTRS2011

Development of the International Space Station (ISS) Fine Water Mist (FWM) Portable Fire Extinguisher ICES Abstract

NASA is developing a Fine Water Mist (FWM) Portable Fire Extinguisher (PFE) for use on the International Space Station. The International Space Station presently uses two different types of fire extinguishers: a water foam extinguisher in the Russian Segment, and a carbon dioxide extinguisher in the US Segment and Columbus and Kibo pressurized elements. Changes in emergency breathing equipment make Fine Water Mist operationally preferable. Supplied oxygen breathing systems allow for safe discharge of a carbon dioxide fire extinguisher, without concerns of the crew inhaling unsafe levels of carbon dioxide. But the Portable Breathing Apparatus (PBA) offers no more than 15 minutes of capability, and continued use of hose based supplied oxygen system increases the oxygen content in a fire situation. NASA has developed a filtering respirator cartridge for use in a fire environment. It is qualified to provide up to 90 minutes of capability, and because it is a filtering respirator it does not add oxygen to the environment. The fire response respirator cartridge does not filter carbon dioxide (CO2), so a crew member discharging a CO2 fire extinguisher while wearing this filtering respirator would be at risk of inhaling unsafe levels of CO2. FWM extinguishes a fire without creating a large volume of air with reduced oxygen and elevated CO2. The following paper will discuss the unique functional and performance requirements that have been levied on the FWM PFE. In addition, the NASA ISS specific fire standards will be described which were developed to establish acceptable extinguisher performance. The paper will also discuss the flight hardware design. The fin e water mist fire extinguisher has two major elements: (1) the nozzle and crew interface, and (2) the tank. The nozzle and crew interface have been under development for several years. They have gone through several design iterations, and have been part of more than 400 fire challenge and spray characterizations. The crew and vehicle interface aspects of the design will use the heritage of the CO2 based Portable Fire Extinguisher, to minimize the disruption to the crew and integration impacts to the ISS. The microgravity use environment of the system poses a set of unique design requirements specifically for the tank. The nozzle requirements drive a tank pressure that is 2-5 times higher than any commercially available water mist systems. Microgravity requires deliberate separation of gas and water, facilitated by a bladder, a diaphragm, a piston, or separate tanks. This paper will describe status of the project to date, the design details of the tank and the nozzle, and discuss the trade studies that informed the decisions to select the tank and nozzle configuration.

Clements, Anna L.↗

NASA NTRSDate not supplied

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

NASA NTRS2024

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

NASA NTRS1972

Flat conductor cable for electrical packaging

Flat conductor cable (FCC) is relatively new, highly promising means for electrical packaging and system integration. FCC offers numerous desirable traits (weight, volume and cost savings, flexibility, high reliability, predictable and repeatable electrical characteristics) which make it extremely attractive as a packaging medium. FCC, today, finds wide application in everything from integration of lunar equipment to the packaging of electronics in nuclear submarines. Described are cable construction and means of termination, applicable specifications and standards, and total FCC systems. A list of additional sources of data is also included for more intensive study.

Angele, W.↗

NASA NTRS1972

A NASA family of minicomputer systems, Appendix A

This investigation was undertaken to establish sufficient specifications, or standards, for minicomputer hardware and software to provide NASA with realizable economics in quantity purchases, interchangeability of minicomputers, software, storage and peripherals, and a uniformly high quality. The standards will define minicomputer system component types, each specialized to its intended NASA application, in as many levels of capacity as required.

Deregt, M. P.↗

NASA NTRS1973

Engineering report. Part 2: NASA wheel and brake material tradeoff study for space shuttle type environmental requirements

The study included material selection and trade-off for the structural components of the wheel and brake optimizing weight vs cost and feasibility for the space shuttle type application. Analytical methods were used to determine section thickness for various materials, and a table was constructed showing weight vs. cost trade-off. The wheel and brake were further optimized by considering design philosophies that deviate from standard aircraft specifications, and designs that best utilize the materials being considered.

Bok, L. D.↗

NASA NTRS1974

Optimizing subsystem test programs

The goal of reduction of space system costs is pursued in the areas of standardization of subsystem test requirements as well as overall subsystem test program resource requirements. A number of standard components are being developed by NASA. The rationale for the various environmental tests applicable to future missions and launch vehicles is discussed. The need for and approach to developing standard component specifications is presented. In addition, a method for reduction of test expenditures utilizing indexes of mission effect and hardware history as indicators of test requirements is proposed.

Meyer, W. H.↗

NASA NTRS1976

High voltage design guide for airborne equipment

The report supplies the theoretical background and design techniques needed by an engineer who is designing electrical insulation for high-voltage high-power components, equipment, and systems on aircraft. A literature survey and abundant bibliography identify references that provide further data on the subjects of partial discharges, corona, field theory and plotting, voids and processes for applying insulation. Both gaseous and solid insulations are treated. Cryogenic and liquid design notes are included. Tests and test equipment for high voltage insulation and equipment are defined. Requirements of test plans and procedures for high-voltage high-power equipment are identified and illustrated by examples. Suggestions for high-voltage specifications are provided. Very few of the Military and Government specifications deal with system voltages above 10kv, thus most aircraft high-voltage specifications will have to be derived from the power industry specifications and standards produced by ASTM, IEEE, and NEMA.

W G Dunbar↗

NASA NTRS1977

Handbook of estimating data, factors, and procedures

Elements to be considered in estimating production costs are discussed in this manual. Guidelines, objectives, and methods for analyzing requirements and work structure are given. Time standards for specific specfic operations are listed for machining, sheet metal working, electroplating and metal treating; painting; silk screening, etching and encapsulating; coil winding; wire preparation and wiring; soldering; and the fabrication of etched circuits and terminal boards. The relation of the various elements of cost to the total cost as proposed for various programs by various contractors is compared with government estimates.

Freeman, L. M.↗

NASA NTRS1979

Feasibility study for a numerical aerodynamic simulation facility. Volume 2: Hardware specifications/descriptions

An FMP (Flow Model Processor) was designed for use in the Numerical Aerodynamic Simulation Facility (NASF). The NASF was developed to simulate fluid flow over three-dimensional bodies in wind tunnel environments and in free space. The facility is applicable to studying aerodynamic and aircraft body designs. The following general topics are discussed in this volume: (1) FMP functional computer specifications; (2) FMP instruction specification; (3) standard product system components; (4) loosely coupled network (LCN) specifications/description; and (5) three appendices: performance of trunk allocation contention elimination (trace) method, LCN channel protocol and proposed LCN unified second level protocol.

Green, F. M.↗

NASA NTRS1979

Technical assistance for law-enforcement communications: Case study report two

Two case histories are presented. In one study the feasibility of consolidating dispatch center operations for small agencies is considered. System load measurements were taken and queueing analysis applied to determine numbers of personnel required for each separate agency and for a consolidated dispatch center. Functional requirements were developed and a cost model was designed to compare relative costs of various alternatives including continuation of the present system, consolidation of a manual system, and consolidated computer-aided dispatching. The second case history deals with the consideration of a multi-regional, intrastate radio frequency for improved interregional communications. Sample standards and specifications for radio equipment are provided.

Reilly, N. B.↗