Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Requirement and 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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

The CEOS/GEO Constellation Concept

The Constellation concept was first proposed during a discussion at the 19th CEOS Plenary, in London, in November 2005. The first Paper of the Constellation Concept was presented at the CEOS Strategic Implementation Team meeting (SIT-18), in Frascati, in March 2006, and strongly endorsed by the CEOS Principals. The concept attempts to provide agencies with tools for implementation of the elements that have been previously discussed in international forums (GEO Work Plan, GCOS Implementation Plan). This provides a solid foundation from the community providing requirements. Though agency spending is governed by national requirements, CEOS seeks synergies among member agency programs to fulfil GEOSS requirements, defining guidelines and standards to help agencies to determine from the outset what can be achieved. The constellations concept will allow the development of a commonalties approach among different agencies. At the heart of the application of the Constellations concept is the definition of a series of standards (specific to each Constellation) - required to be satisfied for any mission to be included in the constellation - and a process of recognition/acceptance, whereby an agency applies to SIT to have one or more of its missions (ideally from the outset of planning) recognised as meeting the constellation standards and thereby satisfying the relevant user community needs.

Cramer, Bryant↗
NASA NTRSDate not supplied

Long Duration Medical System Foundation for Lunar Orbital and Lunar Surface Exploration Missions

For long-duration lunar orbital and lunar surface (LDLOS) exploration missions, the NASA Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a medical system foundation through which clinical considerations may be represented via a systems engineering-based model. Components of the Long Duration Medical System Foundation model include a concept of operations (ConOps), functional decomposition, medical conditions to be addressed, clinical capabilities and resources, technical requirements, and traces of requirements to NASA standards documents and parent-level (Program- and Vehicle habitat system-level) requirements. The Foundation model offers the means to present information in a readily accessible format that is understandable across all clinical, engineering, scientific, and managerial disciplines. Collectively, these components constitute a foundation that serves future programs with similar long duration mission profiles as a starting point for medical system design. The Foundation was developed by a multidisciplinary team of systems engineers, scientists, and clinicians across NASA. The process started with ConOps development, subsequently decomposed into the functionalities needed to diagnose, treat, and prevent medical conditions. The clinical team identified medical conditions most likely needed to be diagnosed and treated during a long-duration lunar exploration mission. Through these approaches, requirements were codified for the LDLOS medical system. These requirements were then traced to NASA standards, medical conditions, medical capabilities, and medical resources, facilitating stakeholders’ use of the Foundation model to analyze traces and to identify medical system interfaces with other vehicle systems or subsystems. In addition, the Foundation may be used as a basis for performing risk trades on medical system mass and volume allocation. This discussion will focus on the processes through which the LDLOS Medical System Foundation was developed, how the Foundation builds a bridge between the medical and engineering domains, and how these processes may be applied more broadly to a crew health and performance system and other system domains.

Jay Lemery↗
DOE OSTI2024

Cybersecurity Certification Requirements for Distributed Energy Resources: A Survey of SunSpec Alliance Standards

This survey paper explores the cybersecurity certification requirements defined by the SunSpec Alliance for Distributed Energy Resource (DER) devices, focusing on aspects such as software updates, device communications, authentication mechanisms, device security, logging, and test procedures. The SunSpec cybersecurity standards mandate support for remote and automated software updates, secure communication protocols, stringent authentication practices, and robust logging mechanisms to ensure operational integrity. Furthermore, the paper discusses the implementation of the SAE J3072 standard using the IEEE 2030.5 protocol, emphasizing the secure interactions between electric vehicle supply equipment (EVSE) and plug-in electric vehicles (PEVs) for functionalities like vehicle-to-grid (V2G) capabilities. This research also examines the SunSpec Modbus standard, which enhances the interoperability among DER system components, facilitating compliance with grid interconnection standards. This paper also analyzes the existing SunSpec Device Information Models, which standardize data exchange formats for DER systems across communication interfaces. Finally, this paper concludes with a detailed discussion of the energy storage cybersecurity specification and the blockchain cybersecurity requirements as proposed by SunSpec Alliance.

Tsikteris, Sean (ORCID:0009000524202250)↗
NASA NTRS2009

NASA Standard for Models and Simulations: Philosophy and Requirements Overview

Following the Columbia Accident Investigation Board report, the NASA Administrator chartered an executive team (known as the Diaz Team) to identify those CAIB report elements with NASA-wide applicability and to develop corrective measures to address each element. One such measure was the development of a standard for the development, documentation, and operation of models and simulations. This report describes the philosophy and requirements overview of the resulting NASA Standard for Models and Simulations.

Blattnig, St3eve R.↗
NASA NTRS2013

NASA Standard for Models and Simulations: Philosophy and Requirements Overview

Following the Columbia Accident Investigation Board report, the NASA Administrator chartered an executive team (known as the Diaz Team) to identify those CAIB report elements with NASA-wide applicability and to develop corrective measures to address each element. One such measure was the development of a standard for the development, documentation, and operation of models and simulations. This report describes the philosophy and requirements overview of the resulting NASA Standard for Models and Simulations.

Blattnig, Steve R.↗
DOE OSTI2022

Requirements for Soldering Fluxes Research using the B-53 Test Board

IPC J-STD-004B standard prescribes general requirements for the classification and testing of soldering flux for high qualify interconnections. This standard defines the classification of soldering materials through specifications of test methods and inspection criteria. The materials include liquid flux, paste flux, solderpaste flux, solder preform flux, and flux-cored solder. This research will use the proposed IPC-53 Surface Insulation Resistance (SIR) test patterns by means of an open comb (2D) and closed comb (3D to simulate a component over the comb pattern). The 2D open comb has uniformity of conductor spacing, sheet resistance, and flux outgassing. The 3D-closed comb simulates the effect of leadless or bottom-terminated components, which have non-uniform sheet resistance and flux outgassing. The response variables will include SIR testing and visual imaging. The objective is to investigate IPC test method improvements for characterizing soldering fluxes when using leadless components with narrow pad-to-pad spacing.

Diamond, Louis↗
DOE OSTI2024

Federal Facility Agreement and Consent Order: Nevada National Security Site Use Restriction Management Plan with ROTC 1

This Use Restriction Management Plan (URMP) provides the information needed to create, modify, and manage use restrictions (URs) for sites on the Nevada National Security Site (NNSS), and sites accessed through the NNSS main gate, that were closed using the corrective action alternative (CAA) of closure in place under the Federal Facility Agreement and Consent Order (FFACO) (1996, as amended). (Note: This pertains to those FFACO sites not managed by the U.S. Department of Energy [DOE], Legacy Management.) The closure in place alternative is used for sites closed with residual contamination at levels requiring corrective action as determined using the FFACO process. The URs contain and control all requirements for long-term monitoring. This URMP also serves as the single repository of the URs implemented under the FFACO that identify use restricted areas and contain the current requirements for inspections, maintenance, and monitoring of the UR. The requirements in these URs replace all requirements listed in previous documentation. This consolidates post-closure monitoring requirements into a single source that ensures completeness and consistency of UR requirements and information. Standardized UR forms were developed to clearly document post-closure requirements that are consistent with current protocols and to ensure consistent information is contained in the URs. Standard notification, summary, and site controls statements were developed for all URs with provisions to insert site-specific options in the text. Current protocols for Industrial Sites and Soils URs are defined in this document and in the Soils Risk-Based Corrective Action (RBCA) Evaluation Process (DOE/EMNV, 2018). The standardized UR forms that have been approved to date are listed in Appendix A. Additional UR forms will be added once the review and approval process has been completed.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1975

Standardized equipment for Space Shuttle experiment payloads

NIM and CAMAC standards were evaluated for use in Space Shuttle experiment payloads. Six payloads were studied, and it was found that 30 to 90% of the electronic functions could be performed with standard, commercially available modules. Only minor modifications are required to adapt the standards to the Shuttle requirements.

More, K. A.↗
NASA NTRS2009

Spaceflight Human System Standards

NASA created a new approach for human system integration and human performance standards. NASA created two documents a standard and a reference handbook. The standard is titled NASA Space Flight Human-System Standard (SFHSS) and consists of two-volumes: Volume 1- Crew Health This volume covers standards needed to support astronaut health (medical care, nutrition, sleep, exercise, etc.) Volume 2 Human Factors, Habitability and Environmental Health This volume covers the standards for system design that will maintain astronaut performance (ie., environmental factors, design of facilities, layout of workstations, and lighting requirements). It includes classic human factors requirements. The new standards document is written in terms so that it is applicable to a broad range of present and future NASA systems. The document states that all new programs prepare system-specific requirements that will meet the general standards. For example, the new standard does not specify a design should accommodate specific percentiles of a defined population. Rather, NASA-STD-3001, Volume 2 states that all programs shall prepare program-specific requirements that define the user population and their size ranges. The design shall then accommodate the full size range of those users. The companion reference handbook, Human Integration Design Handbook (HIDH), was developed to capture the design consideration information from NASA-STD-3000, and adds spaceflight lessons learned, gaps in knowledge, example solutions, and suggests research to further mature specific disciplines. The HIDH serves two major purposes: HIDH is the reference document for writing human factors requirements for specific systems. HIDH contains design guidance information that helps insure that designers create systems which safely and effectively accommodate the capabilities and limitations of space flight crews.

Holubec, Keith↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources

This study addresses the compliance of Inverter-based Resources (IBRs) with IEEE Standard 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a controller development framework for abnormal grid conditions. This framework caters to maintaining ride-through operation in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller framework is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

grid↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗
NASA NTRS2019

NASA CA Operations Devolution: Status Update

What is Devolution? Devolution is a spreading of CA (Conjunction Assessment) operations responsibilities to mission FOTs (Flight Operations Teams): Permits efficiencies in handling the increased workload caused by Space Fence and large constellations; Missions given more flexibility in choosing specific approach to CA requirements that resonates best with their particular needs; CARA (Conjunction Assessment Risk Analysis) retains Agency oversight through an established NASA Standard - will establish requirements for devolved CA preparations, processing, and operations conduct. Devolution is a PROPOSED paradigm under consideration by SMD (Space Missions Directorate): Number of activities required before Agency-level decision can be rendered; Agency requirements established via approved CA Standard; Operational experience testimony from two separate pilot programs; After these activities complete, decision will be made whether devolution is a feasible option for missions; CARA is recommending devolution to exist as an option for missions.

conjunction↗
NASA NTRS2010

Workmanship Standards Personnel Training and Certification Explained

This slide presentation reviews the standards that NASA requires for workmanship and discusses the rationale and the NASA-STD-8739.x standard series. The training and certification of inspectors and operators is to guarantee that workmanship is qualified for NASA applications. The NASA workmanship standard documents review the standards for: Polymeric Applications, Surface Mount Technology, Soldered Electrical Connections, Crimp, Cable and Harnesses, Fiber Optic Terminations, including ANSI and IPC standards for Electrostatic Discharge Safety, Space Applications Electronic Hardware and Requirements for Soldered Electrical and Electronic Assemblies. It also reviews the certification requirements for appropriate personnel. It also reviews the various levels of trainers for the various requirements. There is also a review of calibration requirements for training equipment. Some variations on the curriculum are allowed. NASA requires operators and inspectors to be certified by their employer to ensure that oversight is being performed.

Plante, Jeannette F.↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources: Preprint

This study addresses the compliance of Inverter-based Resources (IBRs) with the IEEE Std 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a comprehensive controller development framework. This framework caters to maintaining ride-trhough operation or implementing strategic disconnections in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller framework is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

IEEE Std 2800↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources

This study addresses the compliance of Inverter-based Resources (IBRs) with IEEE Standard 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a controller development framework for abnormal grid conditions. This framework caters to maintaining ride-through operation in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller frame-work is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

IEEE Std 2800↗
NASA NTRS2024

NASA Spaceflight Medical Selection, Recertification and Mission Evaluation Standards

This NASA Technical Standard provides medical requirements and clinical procedures designed to ensure crew health and safety and occupational longevity of NASA career astronauts. This NASA Technical Standard used for selection and annual recertification of astronauts reflects the medical requirements to successfully complete specific mission tasks and the multifaceted training and performance required of a NASA astronaut. These include, but are not limited to, flying in high performance aircraft, exposure to hypobaric and hyperbaric conditions, exposure to unique environments (e.g., microgravity), and conducting specialized operations (e.g., extra-vehicular activities, robotic arm operations). NASA policy for establishing standards to protect the health and safety of crew and for providing health and medical programs for astronauts during all phases of space flight is authorized by NPD 1000.3 - The NASA Organization, and by NPD 8900.5B - NASA Health and Medical Policy for Human Space Exploration. This document includes medical evaluations for private astronauts and NASA Suborbital Research Specialist (NSRS). Private astronauts are defined as a crew member who is not a NASA career (U.S. government) astronaut or international partner astronaut. NASA Suborbital Research Specialist is an individual who is employed by NASA or funded by NASA to conduct research, technology testing, training, or other activities onboard a sub-orbital vehicle. This excludes those individuals who are the commercially employed crew of the suborbital vehicle. This NASA Technical Standard also provides mission specific medical evaluations which include both clinical and occupational requirements that may be tailored for future missions.

Standards↗