Search NASA⌕ Search

SEARCH · Search NASA

Results for “GSDO”

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.

45 records · Page 3

Configuration and Evaluation of a Dual-Doppler 3-D Wind Field System

Current LSP, GSDO, and SLS space vehicle operations are halted when wind speeds from specific directions exceed defined thresholds and when lightning is a threat. Strong winds and lightning are difficult parameters for the 45th Weather Squadron (45 WS) to forecast, yet are important in the protection of customer vehicle operations and the personnel that conduct them. A display of the low-level horizontal wind field to reveal areas of high winds or convergence would be a valuable tool for forecasters in assessing the timing of high winds, or convection initiation and subsequent lightning occurrence. This is especially important for areas where no weather observation platforms exist. Developing a dual-Doppler radar capability would provide such a display to assist forecasters in predicting high winds and convection initiation. The wind fields can also be used to initialize a local mesoscale numerical weather prediction model to help improve the model forecast winds, convection initiation, and other phenomena. The 45 WS and NWS MLB tasked the Applied Meteorology Unit (AMU) to develop a dual- Doppler wind field display using data from the 45th Space Wing radar, known as the Weather Surveillance Radar (WSR), NWS MLB Weather Surveillance Radar 1988 Doppler (KMLB), and the Orlando International Airport Terminal Doppler Weather Radar (KMCO). They also stipulated that the software used should be freely available. The AMU evaluated two software packages and, with concurrence from NWS MLB and the 45 WS, chose the Warning Decision Support System-Integrated Information (WDSS-II). The AMU collected data from two significant weather cases: a tornadic event on 14 April 2013 and a severe wind and hail event on 12 February 2014. For the 14 April case, the data were from WSR and KMLB. For the 12 February case, the data were from KMCO and KMLB. The AMU installed WDSS-II on a Linux PC, then processed and quality controlled the radar data for display and analysis using WDSS-II tools. Because of issues with de-aliasing the WSR velocity field, the AMU did not use data from this radar in this study and only analyzed the 12 February case. Merging the data to create the dual-Doppler analysis involved several steps. The AMU used instructions from the WDSS-II website and discussion forum to determine the correct tools to use for the analysis, and was successful in creating a merged reflectivity field, which was critical to the success of creating a merged velocity field. However, the AMU was unable to create a merged velocity field. The AMU researched the WDSS-II forum for discussions on similar issues, asked questions on the forum, and tested different options and values in the merger tool with no success. Developing a dual-Doppler wind field was the main goal of this task, but that was not accomplished. It could be an issue of not using the correct options or the correct value for the options used, or there could be issues with the radar data. There is a follow-on AMU task to install the operational version of WDSS-II in the NWS MLB office. This will provide more opportunities to try different options and input values in order to create a merged wind field from KMCO and KMLB.

Doppler radar↗

Safety Characteristics in System Application of Software for Human Rated Exploration Missions for the 8th IAASS Conference

NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development. The GFAS system integrates the flight software packages of the Orion and SLS with the ground systems and launch countdown sequencers through the 'agile' software development process. A unique approach is needed to develop the GFAS project capabilities within this agile process. NASA has defined the software development process through a set of standards. The standards were written during the infancy of the so-called industry 'agile development' movement and must be tailored to adapt to the highly integrated environment of human exploration systems. Safety of the space systems and the eventual crew on board is paramount during the preparation of the exploration flight systems. A series of software safety characteristics have been incorporated into the development and certification efforts to ensure readiness for use and compatibility with the space systems. Three underlining factors in the exploration architecture require the GFAS system to be unique in its approach to ensure safety for the space systems, both the flight as well as the ground systems. The first are the missions themselves, which are exploration in nature, and go far beyond the comfort of low Earth orbit operations. The second is the current exploration system will launch only one mission per year even less during its developmental phases. Finally, the third is the partnered approach through the use of many different prime contractors, including commercial and international partners, to design and build the exploration systems. These three factors make the challenges to meet the mission preparations and the safety expectations extremely difficult to implement. As NASA leads a team of partners in the exploration beyond earth's influence, it is a safety imperative that the application software used to test, checkout, prepare and launch the exploration systems put safety of the hardware and mission first. Software safety characteristics are built into the design and development process to enable the human rated systems to begin their missions safely and successfully. Exploration missions beyond Earth are inherently risky, however, with solid safety approaches in both hardware and software, the boldness of these missions can be realized for all on the home planet.

capability↗

Safety Characteristics in System Application Software for Human Rated Exploration

NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development.

exploration↗

Space Launch System Spacecraft and Payload Elements: Making Progress Toward First Launch

Significant and substantial progress continues to be accomplished in the design, development, and testing of the Space Launch System (SLS), the most powerful human-rated launch vehicle the United States has ever undertaken. Designed to support human missions into deep space, SLS is one of three programs being managed by the National Aeronautics and Space Administration's (NASA's) Exploration Systems Development directorate. The Orion spacecraft program is developing a new crew vehicle that will support human missions beyond low Earth orbit, and the Ground Systems Development and Operations (GSDO) program is transforming Kennedy Space Center (KSC) into next-generation spaceport capable of supporting not only SLS but also multiple commercial users. Together, these systems will support human exploration missions into the proving ground of cislunar space and ultimately to Mars. SLS will deliver a near-term heavy-lift capability for the nation with its 70 metric ton Block 1 configuration, and will then evolve to an ultimate capability of 130 metric tons. The SLS program marked a major milestone with the successful completion of the Critical Design Review in which detailed designs were reviewed and subsequently approved for proceeding with full-scale production. This marks the first time an exploration class vehicle has passed that major milestone since the Saturn V vehicle launched astronauts in the 1960s during the Apollo program. Each element of the vehicle now has flight hardware in production in support of the initial flight of the SLS - Exploration Mission-1 (EM-1), an uncrewed mission to orbit the moon and return, and progress in on track to meet the initial targeted launch date in 2018. In Utah and Mississippi, booster and engine testing are verifying upgrades made to proven shuttle hardware. At Michoud Assembly Facility (MAF) in Louisiana, the world's largest spacecraft welding tool is producing tanks for the SLS core stage. This paper will particularly focus on work taking place at Marshall Space Flight Center (MSFC) and United Launch Alliance (ULA) in Alabama, where upper stage and adapter elements of the vehicle are being constructed and tested. Providing the Orion crew capsule/launch vehicle interface and in-space propulsion via a cryogenic upper stage, the Spacecraft/Payload Integration and Evolution (SPIE) Element serves a key role in achieving SLS goals and objectives. The SPIE element marked a major milestone in 2014 with the first flight of original SLS hardware, the Orion Stage Adapter (OSA) which was used on Exploration Flight Test-1 with a design that will be used again on EM-1. Construction is already underway on the EM-1 Interim Cryogenic Propulsion Stage (ICPS), an in-space stage derived from the Delta Cryogenic Second Stage. Manufacture of the Orion Stage Adapter and the Launch Vehicle Stage Adapter is set to begin at the Friction Stir Facility located at MSFC while structural test articles are either completed (OSA) or nearing completion (Launch Vehicle Stage Adapter). An overview is provided of the launch vehicle capabilities, with a specific focus on SPIE Element qualification/testing progress, as well as efforts to provide access to deep space regions currently not available to the science community through a secondary payload capability utilizing CubeSat-class satellites.

Schorr, Andrew A.↗

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗

Final Test Report: Hexavalent Chrome Free Coatings for Electronics Electromagnetic Interference (EMI) Shielding Effectiveness (SE)

The test results for Salt Spray Resistance, Static Heat and Humidity and Marine Environment can be found in Sections 3.1.3.3, 3.1.4.3 and 3.1.5.3 respectively. In summary, both the Metalast TCP and SurTec 650 Type 2 conversion coatings perform very similar to the incumbent Type 1 conversion coating against both 6061 and 5052 aluminum under all three test conditions. Significant prior work was performed to select the aluminum and conversion coating included within this test cycle; Reference - NASA GSDO Program Hexavalent Chrome Alternatives Final Pretreatments Test Report Task Order: NNH12AA45D September 01, 2013. As illustrated in the data, the 6061 aluminum panels SLIGHTLY out-performed the 5052 aluminum panels. Individual shielding effectiveness graphs for each panel are included within Appendix C and D. One other notable effect found during review of the data is that the Test Panels exposed to B117 Salt Fog reduced in shielding effectiveness significantly more than the Marine Environment Test Panels. The shielding effectiveness of the Marine Test Panels was approximately 20dB higher than the Test Panels that underwent B117 Salt Fog Exposure. The intent of this evaluation was not to maximize shielding effectiveness values. The same Parker Chomerics Cho-Seal 6503 gasket material was used for all panels with aluminum and conversion coating variants. A typical EMI gasket design for corrosive environments would be done quite differently. The intent was to execute a test that would provide the best possible evaluation of different aluminum materials and conversion coatings in corrosive environments. The test program achieved this intent. The fact that the two aluminums and two Type II conversion coatings performed similar to the incumbent Type 1 conversion coating is a positive outcome. It was desired to have an outcome that further differentiation the performance of two aluminum types and two conversion coating types but this could not be extracted by the test results. Further analysis of the test plates may be done by X-Ray Photoelectron Spectroscopy (XPS) or Electrochemical Impedance Spectroscopy (EIS). Feasibility of this is under review.

Kessel, Kurt R.↗

Space Launch System Spacecraft and Payload Elements: Progress Toward Crewed Launch and Beyond

While significant and substantial progress continues to be accomplished toward readying the Space Launch System (SLS) rocket for its first test flight, work is already underway on preparations for the second flight - using an upgraded version of the vehicle - and beyond. Designed to support human missions into deep space, SLS is the most powerful human-rated launch vehicle the United States has ever undertaken, and is one of three programs being managed by the National Aeronautics and Space Administration's (NASA's) Exploration Systems Development division. The Orion spacecraft program is developing a new crew vehicle that will support human missions beyond low Earth orbit (LEO), and the Ground Systems Development and Operations (GSDO) program is transforming Kennedy Space Center (KSC) into a next-generation spaceport capable of supporting not only SLS but also multiple commercial users. Together, these systems will support human exploration missions into the proving ground of cislunar space and ultimately to Mars. For its first flight, SLS will deliver a near-term heavy-lift capability for the nation with its 70-metric-ton (t) Block 1 configuration. Each element of the vehicle now has flight hardware in production in support of the initial flight of the SLS, which will propel Orion around the moon and back. Encompassing hardware qualification, structural testing to validate hardware compliance and analytical modeling, progress is on track to meet the initial targeted launch date. In Utah and Mississippi, booster and engine testing are verifying upgrades made to proven shuttle hardware. At Michoud Assembly Facility (MAF) in Louisiana, the world's largest spacecraft welding tool is producing tanks for the SLS core stage. Providing the Orion crew capsule/launch vehicle interface and in-space propulsion via a cryogenic upper stage, the Spacecraft/Payload Integration and Evolution (SPIE) element serves a key role in achieving SLS goals and objectives. The SPIE element marked a major milestone in 2014 with the first flight of original SLS hardware, the Orion Stage Adapter (OSA) which was used on Exploration Flight Test-1 with a design that will be used again on the first flight of SLS. The element has overseen production of the Interim Cryogenic Propulsion Stage (ICPS), an in-space stage derived from the Delta Cryogenic Second Stage, which was manufactured at United Launch Alliance (ULA) in Decatur, Alabama, prior to being shipped to Florida for flight preparations. Manufacture of the OSA and the Launch Vehicle Stage Adapter (LVSA) took place at the Friction Stir Facility located at Marshall Space Flight Center (MSFC) in Huntsville, Alabama. Marshall is also home to the Integrated Structural Test of the ICPS, LVSA, and OSA, subjecting the stacked components to simulated stresses of launch. The SPIE Element is also overseeing integration of 13 "CubeSat" secondary payloads that will fly on the first flight of SLS, providing access to deep space regions in a way currently not available to the science community. At the same time as this preparation work is taking place toward the first launch of SLS, however, the Space Launch System Program is actively working toward its second launch. For its second flight, SLS will be upgraded to the more-capable Block 1B configuration. While the Block 1 configuration is capable of delivering more than 70 t to LEO, the Block 1B vehicle will increase that capability to 105 t. For that flight, the new configuration introduces two major new elements to the vehicle - an Exploration Upper Stage (EUS) that will be used for both ascent and in-space propulsion, and a Universal Stage Adapter (USA) that serves as a "payload bay" for the rocket, allowing the launch of large exploration systems along with the Orion spacecraft. Already, flight hardware is being prepared for the Block 1B vehicle. Welding is taking place on the second rocket's core stage. Flight hardware production has begun on booster components. An RS-25 engine slated for that flight has been tested. Development work is taking place on the EUS, with contracts in place for both the stage and the RL10 engines which will power it. (The EUS will use four RL10 engines, an increase from one on the ICPS.) For the crew configuration of the Block 1B vehicle, the SLS SPIE element is managing the USA and accompanying Payload Adapter, which will accommodate both large payloads co-manifested with Orion and small-satellite secondary payloads. This co-manifested payload capacity will be instrumental for missions into the proving ground around the moon, where NASA will test new systems and demonstrate new capabilities needed for human exploration farther into deep space.

Schorr, Andrew A.↗

Kennedy Space Center: Apollo to Multi-User Spaceport

NASA Kennedy Space Center (KSC) was established as the gateway to exploring beyond earth. Since the establishment of KSC in December 1963, the Center has been critical in the execution of the United States of Americas bold mission to send astronauts beyond the grasp of the terra firma. On May 25, 1961, a few weeks after a Soviet cosmonaut became the first person to fly in space, President John F. Kennedy laid out the ambitious goal of landing a man on the moon and returning him safely to the Earth by the end of the decade. The resultant Apollo program was massive endeavor, driven by the Cold War Space Race, and supported with a robust budget. The Apollo program consisted of 18 launches from newly developed infrastructure, including 12 manned missions and six lunar landings, ending with Apollo 17 that launched on December 7, 1972. Continuing to use this infrastructure, the Skylab program launched four missions. During the Skylab program, KSC infrastructure was redesigned to meet the needs of the Space Shuttle program, which launched its first vehicle (STS-1) on April 12, 1981. The Space Shuttle required significant modifications to the Apollo launch pads and assembly facilities, as well as new infrastructure, such as Orbiter and Payload Processing Facilities, as well as the Shuttle Landing Facility. The Space Shuttle was a workhorse that supported many satellite deployments, but was key for the construction and maintenance of the International Space Station, which required additional facilities at KSC to support processing of the flight hardware. After reaching the new Millennium, United States policymakers searched for new ways to reduce the cost of space exploration. The Constellation Program was initiated in 2005 with a goal of providing a crewed lunar landing with a much smaller budget. The very successful Space Shuttle made its last launch on July 8, 2011, after 135 missions. In the subsequent years, KSC continues to evolve, and this paper will address past and future efforts of the transformation of the KSC Apollo and Space Shuttle heritage infrastructure into a more versatile, multi-user spaceport. The paper will also discuss the US Congressional and NASA initiatives for developing and supporting multiple commercial partners, while simultaneously supporting NASAs human exploration initiative, consisting of Space Launch System (SLS), Orion spacecraft and associated ground launch systems. In addition, the paper explains the approach with examples for NASA KSC to leverage new technologies and innovative capabilities developed to reduce the cost to individual users.

launchpad↗

Materials Science Corrosion Internship Overview

The overarching purpose of this semester-long internship at the National Aeronautics and Space Administration's (NASA) John F. Kennedy Space Center (KSC) was to study the impacts of corrosion regarding the development of ground support equipment (GSE), launch support structures, and flight hardware in aid of the Space Launch System (SLS) and Orion program. Environmental corrosion is known as one of the largest material degradation issues for any structure comprised of metal on the Space Coast and requires the initiation of special protective measures for proper corrosion mitigation. The four (4) projects to be described were conducted with NASA Civil Servants and NASA Contractors who provided necessary resources to ensure the highest quality of data acquisition and knowledge transfer. The main objective shared between all four (4) of the following projects was to assess the modes by which corrosion takes place in multiple environments as well as the methods by which these modes of corrosion can be reduced for the enhancement of the mechanical, structural, and chemical compatibility of those respective environments with different candidate metals. A multitude of test methods were performed over the duration of this internship to assess the corrosive properties of these different candidate metals.

Ground Systems Development and Operations↗