Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “ICD”

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.

141 records · Page 8

Modeling Complex Cross-Systems Software Interfaces Using SysML

The complex flight and ground systems for NASA human space exploration are designed, built, operated and managed as separate programs and projects. However, each system relies on one or more of the other systems in order to accomplish specific mission objectives, creating a complex, tightly coupled architecture. Thus, there is a fundamental need to understand how each system interacts with the other. To determine if a model-based system engineering approach could be utilized to assist with understanding the complex system interactions, the NASA Engineering and Safety Center (NESC) sponsored a task to develop an approach for performing cross-system behavior modeling. This paper presents the results of applying Model Based Systems Engineering (MBSE) principles using the System Modeling Language (SysML) to define cross-system behaviors and how they map to crosssystem software interfaces documented in system-level Interface Control Documents (ICDs).

Earth orbit↗

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

Getting to the Heart of Cardiovascular Risk Assessment in Astronauts for Exploration Class Missions

Since the beginning of manned spaceflight, NASA has recognized the potential risk of cardiovascular decrements due to stressors in the space environment. Of particular concern is the effect of space radiation on cardiovascular disease since astronauts will be exposed to higher levels of galactic cosmic rays outside the Earth's protective magnetosphere. To date, only a few studies have examined the effects of heavy ion radiation on cardiovascular disease, and at lower, space-relevant doses, the association between radiation exposure and cardiovascular pathology is more varied and unclear. Furthermore, other spaceflight conditions such as microgravity, circadian shifts, and confinement stress pose unique challenges in estimating the health risks that can be attributed to exposure to ionizing radiations. In this work, we review age, cause of mortality, and radiation exposure amongst early NASA astronauts in selection groups and discuss the limitations of assessing such a cohort when attempting to characterize the risk of space flight, including stressors such as space radiation and microgravity exposure, on cardiovascular health. METHODS: NASA astronauts in selection groups 1-7 were chosen and the comparison population was white men of the same birth cohort as drawn from data from the CDC Wonder Database and CDC National Center for Health Statistics Life Tables. Cause of death information was obtained from the Lifetime Surveillance of Astronaut Health program and deceased astronauts were classified based on ICD-10 codes: ischemic heart disease (IHD), stroke, cancer, acute occupational events, non-NASA accidents, and other/unknown. Expected years of life left and expected age at death were calculated for the cohort. RESULTS AND CONCLUSIONS: There were 32 deaths in this early astronaut population, 12 of which were due to accidents or acute occupational events that impacted lifespan considerably. The average age at death from these causes is 30 years lower than the average expected ~70 years of age in the general population. Remarkably, all 41 living early astronauts outlived our calculated expected age at death for members of their birth cohort; furthermore, 13 of the 20 deceased astronauts who did not die in NASA/non-NASA accidents exceeded this age. There was no difference in IHD between the astronaut cohort and the comparison population; therefore, it is not possible to associate IHD mortality with radiation in that astronaut cohort. As NASA looks toward future exploration-class missions, early astronaut cohorts provide a convenient option for assessing these risks and for developing mitigation strategies. However, many challenges still exist when assessing such limited evidence, including small cohort size, health and lifestyle confounders (such as smoking and drinking), the high accident mortality rate, and the fact that many of these astronauts are still alive, outliving many of their birth-cohort peers. Future analysis should include a longitudinal study, monitoring cases as they occur in the cohort. As this cohort is currently followed-up over time, and as more IHD cases are anticipated in a population of this age, this type of study is not as resource-intensive as would normally be the case.

Elgart, S. R.↗

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗

Cardiovascular Disease Outcomes Among the NASA Astronaut Corps

BACKGROUND: Acute effects of spaceflight on the cardiovascular system have been studied extensively, but the combined chronic effects of spaceflight and aging are not well understood. Preparation for and participation in spaceflight activities are associated with changes in the cardiovascular system such as decreased carotid artery distensibility and decreased ventricular mass which may lead to an increased risk of cardiovascular disease. Additionally, astronauts who travel into space multiple times or for longer durations may be at an increased risk across their lifespan. To that end, the purpose of this study was to determine the incidence of common cardiovascular disease (CVD) outcomes among the NASA astronaut corps during their active career and through retirement. METHODS: Cardiovascular disease outcomes were defined as reports of any of the following: myocardial infarction (MI), revascularization procedures (coronary artery bypass graft surgery [CABG] or percutaneous coronary intervention [PCI]), hypertension, stroke or transient ischemic attack [TIA], heart failure, or total CVD (as defined by the AHA - combined outcome of MI, Angina Pectoris, heart failure, stroke, and hypertension). Each outcome was identified individually from review of NASA's Electronic Medical Record (EMR), EKG reports, and death certificates using ICD-9 codes as well as string searches of physician notes of astronaut exams that occurred between 1959 and 2016. RESULTS: Of 338 NASA astronauts selected as of 2016, 9 reported an MI, 12 reported a revascularization procedure, (7 PCI and 5 CABG), 4 reported Angina (without MI), 5 reported heart failure, 9 reported stroke/TIA, and 96 reported hypertension. Total CVD was reported in 105 astronauts. No astronaut who had an MI or revascularization procedure flew a spaceflight mission following the event. All MI, revascularization, and stroke events occurred in male astronauts. When reviewing astronaut ECG reports, abnormal ECG reports were found in only 8% of records (n=430) and mainly among retired astronauts (82%), with marked sinus bradycardia being the reason for the abnormal classification.

Charvat, Jacqueline M.↗

Validation & Verification of Electrical Components B2 Test Facility

The research focus of this project is to assist in the closure of Measurement, Monitoring and Control System (MMCS) and other electrical requirements in support of the B2 Space Launch System (SLS) Core Stage Green Run Test Project. Alongside this goal I am to understand project management tools to analyze and control activities/tasks associated with those items. The project I am working on will assist electrical engineers in developing and or identifying closure rationale for the MMCS and electrical requirements. Also as serving the role of a training project manager, I am to develop and maintain a method for tracking progress with estimate completion dates specifically identifying those items during this performance window. The methods I used in order to perform the research consisted of worddocuments, excel sheets, and pdf documents needed for review. For example, documents consisted of: a SLS Core Stage Green Run Facility Requirement Document (FRD) identifying the SSC MMCS and electrical requirements, a Stage Controller to SSC Interface Control Document (ICD) identifying the SSC requirements, and the B2 SLS Core Stage Green Run Test project System Requirements Document (SRD) which identifies the MMCS and electrical requirements. The files were sent to me by both mentors, Mr. Barry Robinson and Ms. Dawn Davis. Overall, the review process for the word documents and excel spreadsheets proved to be successful. The data for the electrical components were accurate and were consistent with the original recorded data. However, the consistency with the pdf documents did not follow up all the way. Attention to this mistake was made and further revisions were done in order for the data to agree with each other. Furthermore, an itinerary was designed using Microsoft Outlook in order to track progress with estimated completion dates. This project contributes to NASA/Center Missions and Goals through the Waterfall Model. The Waterfall Model is a linear system used for engineering design. In the Waterfall Model, the fourth step is Verification and Validation. This involves installation, testing, and debugging of the B2 SLS Core Stage electrical components. For the SLS Core Stage Green Run Test Project, each requirement contained in this approved requirements set will have at least one Verification Item (VI) assigned to it. During the design phase, VIs will mostly consist of Analysis or Inspection types. Design phase VIs and closure information will be documented in Dynamics Data Management System (DDMS) in the form of analysis reports and design documentation.

Bastian, Tyler↗

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Autonomous Systems↗

Enabling International Data Relay at Mars

The most commonly used mode of communications be-tween Earth and a Mars surface mission is ultra-high fre-quency (UHF) radio relay via a Mars orbiter. There are four orbiters and two surface rovers operating at Mars and by October there should be five orbiters and three landers or rovers. There has been some collaboration between ESA’s Mars Express orbiter and NASA’s rovers, but 2016 is when Mars relay becomes fully international. In October, ESA will deliver the ExoMars Trace Gas Orbiter (TGO) and En-try, Descent, and Landing (EDL) Demonstrator Module (EDM) lander to Mars. The ExoMars program includes both ESA and ROSCOSMOS, with NASA participation (the Electra UHF transceiver on TGO). NASA orbiters will pro-vide relay for EDM and future ESA Mars landers and rov-ers. TGO will provide relay for NASA's current and future surface assets (as Mars Express will continue to do). Inter-national collaboration is enabled in several steps. At the in-struction of the space agencies, the Mars mission projects negotiate and write a “Service Agreement.” This describes at a high level how a new Mars orbiter would operate with its corresponding surface missions or how a new surface mis-sion would operate with its corresponding orbiters. It in-cludes the roles of the different projects, how the new mis-sion would communicate with existing or planned missions, the general flow of data and commands, and the capabilities or requirements of the new mission. After completing the Service Agreement, the projects write Interface Control Doc-uments (ICDs), each of which describes data and command flow in greater detail and quantitative aspects of the relay link and operations timeline between an orbiter and a cor-responding lander/rover. Interfaces and operations are test-ed before a new mission arrives at Mars. Once at Mars, a new orbiter performs some “practice” relay contacts with its partners. For a new lander (e.g. EDM), relay operations gen-erally begin before atmospheric entry at Mars, with record-ing of the UHF relay signal from the lander (including open-loop wide-bandwidth recording) as it enters and traverses Mars’s atmosphere and lands on its surface. After Mars EDL or orbit injection, each relay contact is negotiat-ed and scheduled using the Mars Relay Operations Service (MaROS). This paper describes the international approach to develop inter-agency agreements, inter-project interfaces, and specifics of how MaROS is used in actual relay opera-tions between international partners.

Winton, Alistair J.↗

Simulation of Fluid Flow and Collection Efficiency for a SEA Inc. Multi-Element Probe and Ice Crystal Detector Using GlennICE

Numerical simulation results of fluid flow and collection efficiency of the Science Engineering Associates Inc. Multi-Element Probe (Multiwire) and Ice Crystal Detector (ICD) are presented. Fluid flow simulations were conducted using NASA's FUN3D while collection efficiency simulations were conducted using NASA's LEWICE3D software and GlennICE software. For both probes, 3D unsteady flow results were time-averaged. Simulations were computed for free steam velocities ranging from 85 to 185 m/s and freestream total pressures of 44.8 and 93.1 kPa. Collection efficiency results were computed for four spherical particle diameter sizes of 5, 20, 50, and 100 µm. GlennICE collection efficiency results for the multiwire were compared with previously published collection efficiency values calculated using LEWICE3D. Numerical collection efficiency results for the Ice Crystal Detector are presented for the first time.

aircraft, icing, Computational Fluid Dynamics↗

Simulation of Fluid Flow and Collection Efficiency for a SEA Inc. Multi-Element Probe and Ice Crystal Detector Using GlennICE

Numerical simulation results of fluid flow and collection efficiency of the Science Engineering Associates Inc. Multi-Element Probe (Multiwire) and Ice Crystal Detector (ICD) are presented. Fluid flow simulations were conducted using NASA's FUN3D while collection efficiency simulations were conducted using NASA's LEWICE3D software and GlennICE software. For both probes, 3D unsteady flow results were time averaged. Simulations were computed for freestream velocities ranging from 85 to 185 m/s and freestream total pressures of 44.8 and 93.1 kPa. Collection efficiency results were computed for four spherical particle diameter sizes of 5, 20, 50, and 100 µm. GlennICE collection efficiency results for the multiwire were compared with previously published collection efficiency values calculated using LEWICE3D. Numerical collection efficiency results for the Ice Crystal Detector are presented for the first time.

aircraft, icing, Computational Fluid Dynamics↗

System Performance Testing of the Pulse-Echo Ultrasonic Instrument for Critical Velocity Determination during Hanford Tank Waste Transfer Operations - 13584

The delivery of Hanford double-shell tank waste to the Hanford Tank Waste Treatment and Immobilization Plant (WTP) is governed by specific Waste Acceptance Criteria that are identified in ICD 19 - Interface Control Document for Waste Feed. Waste must be certified as acceptable before it can be delivered to the WTP. The fluid transfer velocity at which solid particulate deposition occurs in waste slurry transport piping (critical velocity) is a key waste acceptance parameter that must be accurately characterized to determine if the waste is acceptable for transfer to the WTP. Washington River Protection Solutions and the Pacific Northwest National Laboratory have been evaluating the ultrasonic PulseEcho instrument since 2010 for its ability to detect particle settling and determine critical velocity in a horizontal slurry transport pipeline for slurries containing particles with a mean particle diameter of =14 micrometers (μm). In 2012 the PulseEcho instrument was further evaluated under WRPS' System Performance test campaign to identify critical velocities for slurries that are expected to be encountered during Hanford tank waste retrieval operations or bounding for tank waste feed. This three-year evaluation has demonstrated the ability of the ultrasonic PulseEcho instrument to detect the onset of critical velocity for a broad range of physical and rheological slurry properties that are likely encountered during the waste feed transfer operations between the Hanford tank farms and the WTP. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

One System Overview - 16579

The U.S. Department of Energy (DOE), Office of River Protection (ORP) is responsible for managing and completing the River Protection Project mission, which is to 'safeguard the nuclear waste stored in Hanford's 177 underground tanks, and to manage the waste safely and responsibly until it can be treated in the Waste Treatment and Immobilization Plant for final disposition'. The Office of River Protection's work scope is currently performed through two primary contracts: - The Tank Operations Contract, held by Washington River Protection Solutions LLC, (WRPS) includes the construction, operation, and maintenance activities necessary to safely store, retrieve, and transfer tank wastes; provide supplemental tank waste treatment; provide storage and/or disposal of primary and secondary waste streams; design, construction and commissioning of the Low-Activity Waste Pretreatment System; and support ORP to integrate Hanford Tank Waste Treatment and Immobilization Plant (WTP) completion and startup with Tank Farms operations. - The WTP Contract, held by Bechtel National, Inc. (BNI), includes the design, construction, and commissioning of a Pretreatment Facility, two vitrification facilities (one for high-level waste and one for low-activity waste), a dedicated analytical laboratory, and supporting facilities to treat radioactive tank wastes by immobilizing them into a stable glass waste form. One System was established as a means to improve the integration between the tank farms and the WTP project to support its safe and successful startup. One System's scope and purpose focus on mission integration consistent with DOE's plans to treat tank waste in phases, starting with direct feed of the low-activity waste stream to the WTP's Low-Activity Waste (LAW) Vitrification Facility (referred to as DFLAW). The One System organization now has four major focus areas: - Flowsheet Integration? Integrated River Protection Project (RPP) flowsheet development and management; developing a gaps, risks, and opportunities management plan and technical roadmap; and waste feed qualification. - Mission Analysis and Planning? Strategic planning, system planning, and modeling integration. - WTP Startup, Commissioning, and Operations Integration? Interface Control Document (ICD) management, coordinating facilities startup-to-commissioning-to-operations, contract directives and standards identification, and DFLAW program integration. - Project Integration and Controls? Integrated schedule, metrics/dashboards monitoring, and One System risk register. ORP established the DFLAW Program Office in February 2015 as one of its key performance goals. ORP staff, along with contractor managers, have identified roles and responsibilities for the each of the four major focus areas. One System has established an Executive Council and Governance Board to drive program progress and make decisions on DFLAW. This approach allows appropriate government and contractor senior management involvement in the DFLAW Program. Monthly critical path analysis on the integrated DFLAW schedule is being performed. Interface control documents specific to DFLAW have been developed, and system planning and modeling tools are being used to help define the DFLAW flowsheet. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Remote Sampler Demonstration Isolok Configuration Test

The accuracy and precision of a new Isolok sampler configuration was evaluated using a recirculation flow loop. The evaluation was performed using two slurry simulants of Hanford high-level tank waste. Through testing, the capability of the Isolok sampler was evaluated. Sample concentrations were compared to reference samples that were simultaneously collected by a two-stage Vezin sampler. The capability of the Isolok sampler to collect samples that accurately reflect the contents in the test loop improved – biases between the Isolok and Vezin samples were greatly reduce for fast settling particles.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA Simulation Capabilities

This presentation provides a high-level overview of NASA's Future ATM Concepts Evaluation Tool (FACET) with a high-level description of the system's inputs and outputs. This presentation is designed to support the joint simulations that NASA and the Chinese Aeronautical Establishment (CAE) will conduct under an existing Memorandum of Understanding.

ICD↗

Interconnection and Interoperability Requirements of Hydrogen Assets to Enable Grid Integration

Traditionally, the inverters used for distributed energy resources (DERs) including solar, energy storage and hydrogen fuel cells are grid following assets. Grid following assets track real power and reactive power setpoints decided by either a local autonomous controller or a remote controller like a microgrid controller. In the past five years, multiple challenges have increased the need for grid forming inverters that can interface to a wide variety of energy resources. These grid forming inverters are becoming critical assets for power systems to enable the replacement of existing rotational machines and provide grid services such as grid resiliency services and black-start. Hydrogen assets (fuel cells) have the potential to successfully replace rotating machines and act as voltage and frequency master by leveraging the long-duration and seasonal energy storage capabilities of hydrogen technologies. This poster presents the progress made in budget period 1 of the proposed work. We will leverage an existing ARIES platform experimental setup to run power-hardware-in-the-loop and controller-hardware-in-the-loop experiments with grid forming fuel cell inverters to develop and document the standardization requirements.

electrolyzer↗