Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Standards Development”

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 91 records · Page 5

Development of Standardized Lunar Regolith Simulant Materials

Lunar exploration requires studies using standardized testing procedures. Previous lunar simulants focused on physical aspects of the lunar regolith. Renewed lunar exploration requires standardized lunar regolith simulant (SLRS) materials that simulate the physical, chemical, and mineralogical properties of the regolith [l]. A root simulant models an end-member, and a derivative is formed by addition of material [2]. The 2005 Workshop recommended a low-Ti mare basalt and a high-Ca highland anorthosite set of roots. Derivatives involve addition of ilmenite and glassy agglutinates [3]. An ideal SLRS material is homogeneous. Geochemical standards are finely-ground to reduce chemical variability, but lunar simulants have a grain size variation and mineralogy that must match the lunar regolith. The simulant homogeneity is monitored using major, minor, and trace element data of progressively smaller samples compared to bulk material. Both chemical and geotechnical properties depend on the contrast from grain to grain. The variability of simulant material is an inherent property that must be taken into account. Simulant production requires monitoring of adherence to simulant requirements and homogeneity during production. Quality control establishes a traceability to a master set of reference standards.

Carpenter, P.↗

Developing a Standard Method for Link-Layer Security of CCSDS Space Communications

Communications security for space systems has been a specialized field generally far removed from considerations of mission interoperability and cross-support in fact, these considerations often have been viewed as intrinsically opposed to security objectives. The space communications protocols defined by the Consultative Committee for Space Data Systems (CCSDS) have a twenty-five year history of successful use in over 400 missions. While the CCSDS Telemetry, Telecommand, and Advancing Orbiting Systems protocols for use at OSI Layer 2 are operationally mature, there has been no direct support within these protocols for communications security techniques. Link-layer communications security has been successfully implemented in the past using mission-unique methods, but never before with an objective of facilitating cross-support and interoperability. This paper discusses the design of a standard method for cryptographic authentication, encryption, and replay protection at the data link layer that can be integrated into existing CCSDS protocols without disruption to legacy communications services. Integrating cryptographic operations into existing data structures and processing sequences requires a careful assessment of the potential impediments within spacecraft, ground stations, and operations centers. The objective of this work is to provide a sound method for cryptographic encapsulation of frame data that also facilitates Layer 2 virtual channel switching, such that a mission may procure data transport services as needed without involving third parties in the cryptographic processing, or split independent data streams for separate cryptographic processing.

Biggerstaff, Craig↗

Orion GN and C Model Based Development: Experience and Lessons Learned

The Orion Guidance Navigation and Control (GN&C) team is charged with developing GN&C algorithms for the Exploration Flight Test One (EFT-1) vehicle. The GN&C team is a joint team consisting primarily of Prime Contractor (Lockheed Martin) and NASA personnel and contractors. Early in the GN&C development cycle the team selected MATLAB/Simulink as the tool for developing GN&C algorithms and Mathworks autocode tools as the means for converting GN&C algorithms to flight software (FSW). This paper provides an assessment of the successes and problems encountered by the GN&C team from the perspective of Orion GN&C developers, integrators, FSW engineers and management. The Orion GN&C approach to graphical development, including simulation tools, standards development and autocode approaches are scored for the main activities that the team has completed through the development phases of the program.

Jackson, Mark C.↗

Development of Standards for Nondestructive Evaluation of COPVs Used in Aerospace Applications

Composite OverWrapped Pressure Vessels (COPVs) are currently accepted by NASA based on design and qualification requirements and generally not verified by NDE for the following reasons: (1) Manufactures and end users generally do not have experience and validated quantitative methods of detecting flaws and defects of concern (1-a) If detected, the flaws are not adequately quantified and it is unclear how they may contribute to degradation in mechanical response (1-b) Carbon-epoxy COPVs also extremely sensitive to impact damage and impacts may be below the visible detection threshold (2) If damage is detected, this generally results in rejection since the effect on mechanical response is generally not known (3) NDE response has not generally been fully characterized, probability of detection (POD) established, and processes validated for evaluation of vessel condition as manufactured and delivered.

Waller, Jess M.↗

National Unmanned Aerial System Standardized Performance Testing and Rating (NUSTAR)

The overall objective of the NUSTAR Capability is to offer standardized tests and scenario conditions to assess performance of the UAS. The following are goals of the NU-STAR: 1. Create a prototype standardized tests and scenarios that vehicles can be tested against. 2. Identify key performance parameters of all UAS and their standardized measurement strategy. 3. Develop standardized performance reporting method (e.g., consumer report style) to assist prospective buyers. 4. Identify key performance metrics that could be used by judged towards overall safety of the UAS and operations. 5. If vehicle certification standard is made by a regulatory agency, the performance of individual UAS could be compared against the minimum requirement (e.g., sense and avoid detection time, stopping distance, kinetic energy, etc.).

Testing↗

Holistic and Pragmatic Standards Processes Enable Interdisciplinary Science

Open, interdisciplinary science inevitably relies heavily on standards. Standards are those often unseen agreements that we take for granted when systems and processes are working fine. Yet standards work is perpetual, laborious, and sometimes contentious, especially for standards to work across diverse disciplines. Standards development, maintenance, and implementation is a complex, ongoing socio-technical process. NASA has developed a progressively open science policy and strategy that calls for the establishment of a data standards process reaching across the five diverse divisions of the Science Mission Directorate. This is a delicate exercise. We, therefore, seek to apply a holistic yet pragmatic approach to developing and maintaining a standards process. We adopt an ecological philosophy that focuses on the interactions within the data ecosystem and how standards facilitate those interactions. We couple high-level analysis with on the ground experimentation. We began by 1) mapping information ecosystem components (e.g. data centers, missions, services, protocols, users), 2)establishing how the components interact (e.g. sharing (meta)data, funding, personnel exchange), and 3) modelling system dynamics (e.g. creation of products from multiple data centers, redundant processes, shared services). The goal is to apply understanding of the ecosystem to real world applications (e.g. planning a new mission, implementing new policy requirements, improving process efficiency, etc.). We have also conducted studies of historical standardization efforts, documenting lessons learned and cautionary tales. We then contrast this more abstract work with real examples. We reviewed and assessed multiple existing standards development processes both within and external to NASA. We now work to implement an initial test process which can be further optimized. We seek to define a consistent approach for assigning persistent identifiers for research objects, especially for the purposes of citation. The experience from this relatively ‘simple’ test case adds a pragmatic perspective on how researchers and engineers actually work. This presentation will review the details of this methodology, our initial findings, and how they might apply to other interdisciplinary standardization efforts.

Mark A Parsons↗

NASA Standards Inform Comfortable Car Seats

NASA developed standards, which included the neutral body posture (NBP), to specify ways to design flight systems that support human health and safety. Nissan Motor Company, with US offices in Franklin, Tennessee, turned to NASA's NBP research for the development of a new driver's seat. The 2013 Altima now features the new seat, and the company plans to incorporate the seats in upcoming vehicles.

Source record↗

NASA GeneLab RNASeq Consensus Pipeline: A Nextflow Implementation

The NASA GeneLab project (genelab.nasa.gov) seeks to accelerate space biology research through cataloging and democratizing omics data. Since raw omics data is largely inaccessible to non-bioinformaticians, GeneLab works with the scientific community to develop standard processing pipelines to generate and publish processed data. Unlike raw data, processed data has greater immediate value to a wide range of users with varying technical backgrounds and computational capabilities. Standardizing processing workflows is essential to match the pace of raw data generation, ensure reproducibility, and enable standardized processed data for comparison across datasets. Previously, GeneLab developed a standardized pipeline for processing RNAseq data, referred to as the ‘GeneLab RNAseq Consensus Pipeline (RCP)’, in collaboration with GeneLab’s Analysis Working Groups. The work presented here is a Nextflow implementation of GeneLab’s RCP that automates and accelerates data processing of RNASeq datasets hosted on GeneLab. In addition to the core data processing, the workflow also includes staging of GeneLab raw data and a robust verification and validation (V&V) program that runs after each processing step to identify errors in real-time, stop additional downstream computation, and preserve computational resources. The workflow, including the staging and V&V functionality, is open source for others to reuse and modify at https://github.com/nasa/GeneLab_Data_Processing/tree/master/RNAseq.

Jonathan Dejesus Oribello↗

NASA GeneLab RNASeq Consensus Pipeline: A Nextflow Implementation

The NASA GeneLab project (genelab.nasa.gov) seeks to accelerate space biology research through cataloging and democratizing omics data. Since raw omics data is largely inaccessible to non-bioinformaticians, GeneLab works with the scientific community to develop standard processing pipelines to generate and publish processed data. Unlike raw data, processed data has greater immediate value to a wide range of users with varying technical backgrounds and computational capabilities. Standardizing processing workflows is essential to match the pace of raw data generation, ensure reproducibility, and enable standardized processed data for comparison across datasets. Previously, GeneLab developed a standardized pipeline for processing RNAseq data, referred to as the ‘GeneLab RNAseq Consensus Pipeline (RCP)’, in collaboration with GeneLab’s Analysis Working Groups. The work presented here is a Nextflow implementation of GeneLab’s RCP that automates and accelerates data processing of RNASeq datasets hosted on GeneLab. In addition to the core data processing, the workflow also includes staging of GeneLab raw data and a robust verification and validation (V&V) program that runs after each processing step to identify errors in real-time, stop additional downstream computation, and preserve computational resources. The workflow, including the staging and V&V functionality, is open source for others to reuse and modify at https://github.com/nasa/GeneLab_Data_Processing/tree/master/RNAseq.

Jonathan D Oribello↗

NASA-STD 3001 and the Human Integration Design Handbook (HIDH): Evolution of NASA-STD-3000

The Habitability & Environmental Factors and Space Medicine Divisions have developed the Space Flight Human System Standard (SFHSS) (NASA-STD-3001) to replace NASA-STD-3000 as a new NASA standard for all human spaceflight programs. The SFHSS is composed of 2 volumes. Volume 1, Crew Health, contains medical levels of care, permissible exposure limits, and fitness for duty criteria, and permissible outcome limits as a means of defining successful operating criteria for the human system. Volume 2, Habitability and Environmental Health, contains environmental, habitability and human factors standards. Development of the Human Integration Design Handbook (HIDH), a companion to the standard, is currently under construction and entails the update and revision of NASA-STD-3000 data. This new handbook will, in the fashion of NASA STD-3000, assist engineers and designers in appropriately applying habitability, environmental and human factors principles to spacecraft design. Organized in a chapter-module-element structure, the HIDH will provide the guidance for the development of requirements, design considerations, lessons learned, example solutions, background research, and assist in the identification of gaps and research needs in the disciplines. Subject matter experts have been and continue to be solicited to participate in the update of the chapters. The purpose is to build the HIDH with the best and latest data, and provide a broad representation from experts in industry, academia, the military and the space program. The handbook and the two standards volumes work together in a unique way to achieve the required level of human-system interface. All new NASA programs will be required to meet Volumes 1 and 2. Volume 2 presents human interface goals in broad, non-verifiable standards. Volume 2 also requires that each new development program prepare a set of program-specific human factors requirements. These program-specific human and environmental factors requirements must be verifiable and tailored to assure the new system meets the Volume 2 standards. Programs will use the HIDH to write their verifiable program-specific requirements.

Pickett, Lynn↗

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 Technical Standards Program

The NASA Technical Standards Program was officially established in 1997 as result of a directive issued by the Administrator. It is responsible for Agency wide technical standards development, adoption (endorsement), and conversion of Center-unique standards for Agency wide use. One major element of the Program is the review of NSA technical standards products and replacement with non-Government Voluntary Consensus Standards in accordance with directions issued by the Office of Management and Budget. As part of the Program's function, it developed a NASA Integrated Technical Standards Initiative that consists of and Agency wide full-text system, standards update notification system, and lessons learned-standards integration system. The Program maintains a 'one stop-shop' Website for technical standards ad related information on aerospace materials, etc. This paper provides information on the development, current status, and plans for the NAS Technical Standards Program along with metrics on the utility of the products provided to both users within the nasa.gov Domain and the Public Domain.

Gill, Paul S.↗

NASA Technical Standards Program

The NASA Technical Standards Program was officially established in 1997 as result of a directive issued by the Administrator. It is responsible for Agency wide technical standards development, adoption (endorsement), and conversion of Center-unique standards for Agency wide use. One major element of the Program is the review of NSA technical standards products and replacement with non-Government Voluntary Consensus Standards in accordance with directions issued by the Office of Management and Budget. As part of the Program s function, it developed a NASA Integrated Technical Standards Initiative that consists of and Agency wide full-text system, standards update notification system, and lessons learned - standards integration system. The Program maintains a "one stop-shop" Website for technical standards ad related information on aerospace materials, etc. This paper provides information on the development, current status, and plans for the NAS Technical Standards Program along with metrics on the utility of the products provided to both users within the nasa.gov Domain and the Public Domain.

Gill, Paul S.↗

Standards for AI/ML and Emerging Technologies

Standards development activities require a keen and deep understanding of the problem being solved by the standard as well as the technologies being deployed in any reference implementation of the solution. It is important to understand the mechanisms and limits of the fundamental, underlying science of implementation and verification technologies used to realize and assure systems. We need to understand the limits of what current process and metrics can provide with respect to new technologies. US leadership is important in this endeavor, and it is vital that we have a measured approach that yields sound results. We wish to start with simple, well-defined, non-safety critical applications and then progress to functions which have (1) clearly defined requirements, (2) means of checking the answer/output, and (3) means of intervention and mitigation of incorrect answers/outputs.

Standards Development↗

Synergistic control center development utilizing commercial technology and industry standards

The development of the Control Center Complex (CCC), a synergistic control center supporting both the Space Station Freedom and the Space Shuttle Program, is described. To provide maximum growth and flexibility, the CCC uses commercial off-the-shelf technology and industry standards. The discussion covers the development philosophy, CCC architecture, data distribution, the software platform concept, workstation platform, commercial tools for the CCC, and benefits of synergy.

Anderson, Brian L.↗

Introduction to the National Information Display Laboratory

The goals of the National Information Display Laboratory (NIDL) are described in viewgraph form. The NIDL is a Center of Excellence in softcopy technology with the overall goal to develop new ways to satisfy government information needs through aggressive user support and the development of advanced technology. Government/industry/academia participation, standards development, and various display technologies are addressed.

Carlson, Curtis R.↗