Search NASA⌕ Search

SEARCH · Search NASA

Results for “developments”

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 451 records · Page 25

Propulsion Technology Development for Sample Return Missions Under NASA's ISPT Program

The In-Space Propulsion Technology (ISPT) Program was tasked in 2009 to start development of propulsion technologies that would enable future sample return missions. Sample return missions could be quite varied, from collecting and bringing back samples of comets or asteroids, to soil, rocks, or atmosphere from planets or moons. The paper will describe the ISPT Program s propulsion technology development activities relevant to future sample return missions. The sample return propulsion technology development areas for ISPT are: 1) Sample Return Propulsion (SRP), 2) Planetary Ascent Vehicles (PAV), 3) Entry Vehicle Technologies (EVT), and 4) Systems/mission analysis and tools that focuses on sample return propulsion. The Sample Return Propulsion area is subdivided into: a) Electric propulsion for sample return and low cost Discovery-class missions, b) Propulsion systems for Earth Return Vehicles (ERV) including transfer stages to the destination, and c) Low TRL advanced propulsion technologies. The SRP effort will continue work on HIVHAC thruster development in FY2011 and then transitions into developing a HIVHAC system under future Electric Propulsion for sample return (ERV and transfer stages) and low-cost missions. Previous work on the lightweight propellant-tanks will continue under advanced propulsion technologies for sample return with direct applicability to a Mars Sample Return (MSR) mission and with general applicability to all future planetary spacecraft. A major effort under the EVT area is multi-mission technologies for Earth Entry Vehicles (MMEEV), which will leverage and build upon previous work related to Earth Entry Vehicles (EEV). The major effort under the PAV area is the Mars Ascent Vehicle (MAV). The MAV is a new development area to ISPT, and builds upon and leverages the past MAV analysis and technology developments from the Mars Technology Program (MTP) and previous MSR studies.

Anderson, David J.↗

Collaborative Software Development Approach Used to Deliver the New Shuttle Telemetry Ground Station

United Space Alliance (USA) developed and used a new software development method to meet technical, schedule, and budget challenges faced during the development and delivery of the new Shuttle Telemetry Ground Station at Kennedy Space Center. This method, called Collaborative Software Development, enabled KSC to effectively leverage industrial software and build additional capabilities to meet shuttle system and operational requirements. Application of this method resulted in reduced time to market, reduced development cost, improved product quality, and improved programmer competence while developing technologies of benefit to a small company in California (AP Labs Inc.). Many modifications were made to the baseline software product (VMEwindow), which improved its quality and functionality. In addition, six new software capabilities were developed, which are the subject of this article and add useful functionality to the VMEwindow environment. These new software programs are written in C or VXWorks and are used in conjunction with other ground station software packages, such as VMEwindow, Matlab, Dataviews, and PVWave. The Space Shuttle Telemetry Ground Station receives frequency-modulation (FM) and pulse-code-modulated (PCM) signals from the shuttle and support equipment. The hardware architecture (see figure) includes Sun workstations connected to multiple PCM- and FM-processing VersaModule Eurocard (VME) chassis. A reflective memory network transports raw data from PCM Processors (PCMPs) to the programmable digital-to-analog (D/A) converters, strip chart recorders, and analysis and controller workstations.

Kirby, Randy L.↗

An MBSE Approach to Space Suit Development

The EVA/Space Suit Development Office (ESSD) Systems Engineering and Integration (SE&I) team has utilized MBSE in multiple programs. After developing operational and architectural models, the MBSE framework was expanded to link the requirements space to the system models through functional analysis and interfaces definitions. By documenting all the connections within the technical baseline, ESSD experienced significant efficiency improvements in analysis and identification of change impacts. One of the biggest challenges presented to the MBSE structure was a program transition and restructuring effort, which was completed successfully in 4 months culminating in the approval of a new EVA Technical Baseline. During this time three requirements sets spanning multiple DRMs were streamlined into one NASA-owned Systems Requirement Document (SRD) that successfully identified requirements relevant to the current hardware development effort while remaining extensible to support future hardware developments. A capability-based hierarchy was established to provide a more flexible framework for future space suit development that can support multiple programs with minimal rework of basic EVA/Space Suit requirements. This MBSE approach was most recently applied for generation of an EMU Demonstrator technical baseline being developed for an ISS DTO. The relatively quick turnaround of operational concepts, architecture definition, and requirements for this new suit development has allowed us to test and evolve the MBSE process and framework in an extremely different setting while still offering extensibility and traceability throughout ESSD projects. The ESSD MBSE framework continues to be evolved in order to support integration of all products associated with the SE&I engine.

Cordova, Lauren↗

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.↗

Five-Segment Solid Rocket Motor Development Status

In support of the National Aeronautics and Space Administration (NASA), Marshall Space Flight Center (MSFC) is developing a new, more powerful solid rocket motor for space launch applications. To minimize technical risks and development costs, NASA chose to use the Space Shuttle s solid rocket boosters as a starting point in the design and development. The new, five segment motor provides a greater total impulse with improved, more environmentally friendly materials. To meet the mass and trajectory requirements, the motor incorporates substantial design and system upgrades, including new propellant grain geometry with an additional segment, new internal insulation system, and a state-of-the art avionics system. Significant progress has been made in the design, development and testing of the propulsion, and avionics systems. To date, three development motors (one each in 2009, 2010, and 2011) have been successfully static tested by NASA and ATK s Launch Systems Group in Promontory, UT. These development motor tests have validated much of the engineering with substantial data collected, analyzed, and utilized to improve the design. This paper provides an overview of the development progress on the first stage propulsion system.

Priskos, Alex S.↗

National Aeronautics and Space Administration (NASA) Environmental Control and Life Support (ECLS) Capability Roadmap Development for Exploration

NASA is considering a number of future human space exploration mission concepts. Although detailed requirements and vehicle architectures remain mostly undefined, near-term technology investment decisions need to be guided by the anticipated capabilities needed to enable or enhance the mission concepts. This paper describes a roadmap that NASA has formulated to guide the development of Environmental Control and Life Support Systems (ECLSS) capabilities required to enhance the long-term operation of the International Space Station (ISS) and enable beyond-Low Earth Orbit (LEO) human exploration missions. Three generic mission types were defined to serve as a basis for developing a prioritized list of needed capabilities and technologies. Those are 1) a short duration micro gravity mission; 2) a long duration transit microgravity mission; and 3) a long duration surface exploration mission. To organize the effort, ECLSS was categorized into three major functional groups (atmosphere, water, and solid waste management) with each broken down into sub-functions. The ability of existing, flight-proven state-of-the-art (SOA) technologies to meet the functional needs of each of the three mission types was then assessed. When SOA capabilities fell short of meeting the needs, those "gaps" were prioritized in terms of whether or not the corresponding capabilities enable or enhance each of the mission types. The resulting list of enabling and enhancing capability gaps can be used to guide future ECLSS development. A strategy to fulfill those needs over time was then developed in the form of a roadmap. Through execution of this roadmap, the hardware and technologies needed to enable and enhance exploration may be developed in a manner that synergistically benefits the ISS operational capability, supports Multi-Purpose Crew Vehicle (MPCV) development, and sustains long-term technology investments for longer duration missions. This paper summarizes NASA s ECLSS capability roadmap development process, findings, and recommendation

Bagdigian, Robert M.↗

Development of Human System Integration at NASA

Human Systems Integration seeks to design systems around the capabilities and limitations of the humans which use and interact with the system, ensuring greater efficiency of use, reduced error rates, and less rework in the design, manufacturing and operational deployment of hardware and software. One of the primary goals of HSI is to get the human factors practitioner involved early in the design process. In doing so, the aim is to reduce future budget costs and resources in redesign and training. By the preliminary design phase of a project nearly 80% of the total cost of the project is locked in. Potential design changes recommended by evaluations past this point will have little effect due to lack of funding or a huge cost in terms of resources to make changes. Three key concepts define an effective HSI program. First, systems are comprised of hardware, software, and the human, all of which operate within an environment. Too often, engineers and developers fail to consider the human capacity or requirements as part of the system. This leads to poor task allocation within the system. To promote ideal task allocation, it is critical that the human element be considered early in system development. Poor design, or designs that do not adequately consider the human component, could negatively affect physical or mental performance, as well as, social behavior. Second, successful HSI depends upon integration and collaboration of all the domains that represent acquisition efforts. Too often, these domains exist as independent disciplines due to the location of expertise within the service structure. Proper implementation of HSI through participation would help to integrate these domains and disciplines to leverage and apply their interdependencies to attain an optimal design. Via this process domain interests can be integrated to perform effective HSI through trade-offs and collaboration. This provides a common basis upon which to make knowledgeable decisions. Finally, HSI must be considered early in the requirements development phase of system design and acquisition. This will provide the best opportunity to maximize return on investment (ROI) and system performance. HSI requirements must be developed in conjunction with capability ]based requirements generation through functional. HSI requirements will drive HSI metrics and embed HSI issues within the system design. After a system is designed, implementation of HSI oversights can be very expensive. An HSI program should be included as an integral part of a total system approach to vehicle and habitat development. This would include, but not limited to, workstation design, D&C development, volumetric analysis, training, operations, and human -robotic interaction. HSI is a necessary process for Human Space Flight programs to meet the Agency Human ]System standards and thus mitigate human risks to acceptable levels. NASA has been involved in HSI planning, procedures development, process, and implementation for many years, and has been building several internal and publicly accessible products to facilitate HSI fs inclusion in the NASA Systems Engineering Lifecycle. Some of these products include: NASA STD 3001 Volumes 1 and 2, Human Integration Design Handbook, NASA HSI Implementation Plan, NASA HSI Implementation Plan Templates, NASA HSI Implementation Handbook, and a 2 ]hour short course on HSI delivered as part of the NASA Space and Life Sciences Directorate Academy. These products have been created leveraging industry best practices and lessons learned from other Federal Government agencies.

Whitmore, Mihriban↗

Development of Waypoint Planning Tool in Response to NASA Field Campaign Challenges

Airborne real time observations are a major component of NASA's Earth Science research and satellite ground validation studies. For mission scientists, planning a research aircraft mission within the context of meeting the science objectives is a complex task because it requires real time situational awareness of the weather conditions that affect the aircraft track. Multiple aircrafts are often involved in NASA field campaigns. The coordination of the aircrafts with satellite overpasses, other airplanes and the constantly evolving, dynamic weather conditions often determines the success of the campaign. A flight planning tool is needed to provide situational awareness information to the mission scientists, and help them plan and modify the flight tracks. Scientists at the University of Alabama-Huntsville and the NASA Marshall Space Flight Center developed the Waypoint Planning Tool, an interactive software tool that enables scientists to develop their own flight plans (also known as waypoints) with point -and-click mouse capabilities on a digital map filled with real time raster and vector data. The development of this Waypoint Planning Tool demonstrates the significance of mission support in responding to the challenges presented during NASA field campaigns. Analysis during and after each campaign helped identify both issues and new requirements, and initiated the next wave of development. Currently the Waypoint Planning Tool has gone through three rounds of development and analysis processes. The development of this waypoint tool is directly affected by the technology advances on GIS/Mapping technologies. From the standalone Google Earth application and simple KML functionalities, to Google Earth Plugin and Java Web Start/Applet on web platform, and to the rising open source GIS tools with new JavaScript frameworks, the Waypoint Planning Tool has entered its third phase of technology advancement. The newly innovated, cross ]platform, modular designed JavaScript ]controlled Way Point Tool is planned to be integrated with NASA Airborne Science Mission Tool Suite. Adapting new technologies for the Waypoint Planning Tool ensures its success in helping scientists reach their mission objectives. This presentation will discuss the development processes of the Waypoint Planning Tool in responding to field campaign challenges, identify new information technologies, and describe the capabilities and features of the Waypoint Planning Tool with the real time aspect, interactive nature, and the resultant benefits to the airborne science community.

He, Matt↗

The Status of Spacecraft Bus and Platform Technology Development under the NASA ISPT Program

The In-Space Propulsion Technology (ISPT) program is developing spacecraft bus and platform technologies that will enable or enhance NASA robotic science missions. The ISPT program is currently developing technology in four areas that include Propulsion System Technologies (electric and chemical), Entry Vehicle Technologies (aerocapture and Earth entry vehicles), Spacecraft Bus and Sample Return Propulsion Technologies (components and ascent vehicles), and Systems/Mission Analysis. Three technologies are ready for near-term flight infusion: 1) the high-temperature Advanced Material Bipropellant Rocket (AMBR) engine providing higher performance; 2) NASA s Evolutionary Xenon Thruster (NEXT) ion propulsion system, a 0.6-7 kW throttle-able gridded ion system; and 3) Aerocapture technology development with investments in a family of thermal protection system (TPS) materials and structures; guidance, navigation, and control (GN&C) models of blunt-body rigid aeroshells; and aerothermal effect models. Two component technologies being developed with flight infusion in mind are the Advanced Xenon Flow Control System and ultralightweight propellant tank technologies. Future directions for ISPT are technologies that relate to sample return missions and other spacecraft bus technology needs like: 1) Mars Ascent Vehicles (MAV); 2) multi-mission technologies for Earth Entry Vehicles (MMEEV); and 3) electric propulsion. These technologies are more vehicles and mission-focused, and present a different set of technology development and infusion steps beyond those previously implemented. The Systems/Mission Analysis area is focused on developing tools and assessing the application of propulsion and spacecraft bus technologies to a wide variety of mission concepts. These inspace propulsion technologies are applicable, and potentially enabling for future NASA Discovery, New Frontiers, and sample return missions currently under consideration, as well as having broad applicability to potential Flagship missions. This paper provides a brief overview of the ISPT program, describing the development status and technology infusion readiness of in-space propulsion technologies in the areas of electric propulsion, Aerocapture, Earth entry vehicles, propulsion components, Mars ascent vehicle, and mission/systems analysis.

Anderson, David J.↗

The Status of Spacecraft Bus and Platform Technology Development Under the NASA ISPT Program

The In-Space Propulsion Technology (ISPT) program is developing spacecraft bus and platform technologies that will enable or enhance NASA robotic science missions. The ISPT program is currently developing technology in four areas that include Propulsion System Technologies (electric and chemical), Entry Vehicle Technologies (aerocapture and Earth entry vehicles), Spacecraft Bus and Sample Return Propulsion Technologies (components and ascent vehicles), and Systems/Mission Analysis. Three technologies are ready for near-term flight infusion: 1) the high-temperature Advanced Material Bipropellant Rocket (AMBR) engine providing higher performance 2) NASAs Evolutionary Xenon Thruster (NEXT) ion propulsion system, a 0.6-7 kW throttle-able gridded ion system and 3) Aerocapture technology development with investments in a family of thermal protection system (TPS) materials and structures guidance, navigation, and control (GN&C) models of blunt-body rigid aeroshells and aerothermal effect models. Two component technologies being developed with flight infusion in mind are the Advanced Xenon Flow Control System, and ultra-lightweight propellant tank technologies. Future direction for ISPT are technologies that relate to sample return missions and other spacecraft bus technology needs like: 1) Mars Ascent Vehicles (MAV) 2) multi-mission technologies for Earth Entry Vehicles (MMEEV) and 3) electric propulsion. These technologies are more vehicle and mission-focused, and present a different set of technology development and infusion steps beyond those previously implemented. The Systems/Mission Analysis area is focused on developing tools and assessing the application of propulsion and spacecraft bus technologies to a wide variety of mission concepts. These in-space propulsion technologies are applicable, and potentially enabling for future NASA Discovery, New Frontiers, and sample return missions currently under consideration, as well as having broad applicability to potential Flagship missions. This paper provides a brief overview of the ISPT program, describing the development status and technology infusion readiness of in-space propulsion technologies in the areas of electric propulsion, Aerocapture, Earth entry vehicles, propulsion components, Mars ascent vehicle, and mission/systems analysis.

Anderson, David J.↗

Spacecraft Bus and Platform Technology Development under the NASA ISPT Program

The In-Space Propulsion Technology (ISPT) program is developing spacecraft bus and platform technologies that will enable or enhance NASA robotic science missions. The ISPT program is currently developing technology in four areas that include Propulsion System Technologies (electric and chemical), Entry Vehicle Technologies (aerocapture and Earth entry vehicles), Spacecraft Bus and Sample Return Propulsion Technologies (components and ascent vehicles), and Systems/Mission Analysis. Three technologies are ready for near-term flight infusion: 1) the high-temperature Advanced Material Bipropellant Rocket (AMBR) engine providing higher performance; 2) NASA s Evolutionary Xenon Thruster (NEXT) ion propulsion system, a 0.6-7 kW throttle-able gridded ion system; and 3) Aerocapture technology development with investments in a family of thermal protection system (TPS) materials and structures; guidance, navigation, and control (GN&C) models of blunt-body rigid aeroshells; and aerothermal effect models. Two component technologies being developed with flight infusion in mind are the Advanced Xenon Flow Control System, and ultra-lightweight propellant tank technologies. Future direction for ISPT are technologies that relate to sample return missions and other spacecraft bus technology needs like: 1) Mars Ascent Vehicles (MAV); 2) multi-mission technologies for Earth Entry Vehicles (MMEEV) for sample return missions; and 3) electric propulsion for sample return and low cost missions. These technologies are more vehicle and mission-focused, and present a different set of technology development and infusion steps beyond those previously implemented. The Systems/Mission Analysis area is focused on developing tools and assessing the application of propulsion and spacecraft bus technologies to a wide variety of mission concepts. These in-space propulsion technologies are applicable, and potentially enabling for future NASA Discovery, New Frontiers, and sample return missions currently under consideration, as well as having broad applicability to potential Flagship missions. This paper provides a brief overview of the ISPT program, describing the development status and technology infusion readiness of in-space propulsion technologies in the areas of electric propulsion, Aerocapture, Earth entry vehicles, propulsion components, Mars ascent vehicle, and mission/systems analysis.

Anderson, David J.↗

Spacecraft Bus and Platform Technology Development under the NASA ISPT Program

The In-Space Propulsion Technology (ISPT) program is developing spacecraft bus and platform technologies that will enable or enhance NASA robotic science missions. The ISPT program is currently developing technology in four areas that include Propulsion System Technologies (electric and chemical), Entry Vehicle Technologies (aerocapture and Earth entry vehicles), Spacecraft Bus and Sample Return Propulsion Technologies (components and ascent vehicles), and Systems/Mission Analysis. Three technologies are ready for near-term flight infusion: 1) the high-temperature Advanced Material Bipropellant Rocket (AMBR) engine providing higher performance 2) NASAs Evolutionary Xenon Thruster (NEXT) ion propulsion system, a 0.6-7 kW throttle-able gridded ion system and 3) Aerocapture technology development with investments in a family of thermal protection system (TPS) materials and structures guidance, navigation, and control (GN&C) models of blunt-body rigid aeroshells and aerothermal effect models. Two component technologies being developed with flight infusion in mind are the Advanced Xenon Flow Control System, and ultra-lightweight propellant tank technologies. Future direction for ISPT are technologies that relate to sample return missions and other spacecraft bus technology needs like: 1) Mars Ascent Vehicles (MAV) 2) multi-mission technologies for Earth Entry Vehicles (MMEEV) for sample return missions and 3) electric propulsion for sample return and low cost missions. These technologies are more vehicle and mission-focused, and present a different set of technology development and infusion steps beyond those previously implemented. The Systems/Mission Analysis area is focused on developing tools and assessing the application of propulsion and spacecraft bus technologies to a wide variety of mission concepts. These in-space propulsion technologies are applicable, and potentially enabling for future NASA Discovery, New Frontiers, and sample return missions currently under consideration, as well as having broad applicability to potential Flagship missions. This paper provides a brief overview of the ISPT program, describing the development status and technology infusion readiness of in-space propulsion technologies in the areas of electric propulsion, Aerocapture, Earth entry vehicles, propulsion components, Mars ascent vehicle, and mission/systems analysis.

Anderson, David J.↗

Development of FIAT-Based Parametric Thermal Protection System Mass Estimating Relationships for NASA's Multi-Mission Earth Entry Concept

Part of NASAs In-Space Propulsion Technology (ISPT) program is the development of the tradespace to support the design of a family of multi-mission Earth Entry Vehicles (MMEEV) to meet a wide range of mission requirements. An integrated tool called the Multi Mission System Analysis for Planetary Entry Descent and Landing or M-SAPE tool is being developed as part of Entry Vehicle Technology project under In-Space Technology program. The analysis and design of an Earth Entry Vehicle (EEV) is multidisciplinary in nature, requiring the application many disciplines. Part of M-SAPE's application required the development of parametric mass estimating relationships (MERs) to determine the vehicle's required Thermal Protection System (TPS) for safe Earth entry. For this analysis, the heat shield was assumed to be made of a constant thickness TPS. This resulting MERs will then e used to determine the pre-flight mass of the TPS. Two Mers have been developed for the vehicle forebaody. One MER was developed for PICA and the other consisting of Carbon Phenolic atop an Advanced Carbon-Carbon composition. For the the backshell, MERs have been developed for SIRCA, Acusil II, and LI-900. How these MERs were developed, the resulting equations, model limitations, and model accuracy are discussed in this poster.

Sepka, Steven A.↗

Develop a Model Component

During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.

Ensey, Tyler S.↗

AWIPS II Application Development, a SPoRT Perspective

The National Weather Service (NWS) is deploying its next‐generation decision support system, called AWIPS II (Advanced Weather Interactive Processing System II). NASA's Short‐term Prediction Research and Transition (SPoRT) Center has developed several software 'plug‐ins' to extend the capabilities of AWIPS II. SPoRT aims to continue its mission of improving short‐term forecasts by providing NASA and NOAA products on the decision support system used at NWS weather forecast offices (WFOs). These products are not included in the standard Satellite Broadcast Network feed provided to WFOs. SPoRT has had success in providing support to WFOs as they have transitioned to AWIPS II. Specific examples of transitioning SPoRT plug‐ins to WFOs with newly deployed AWIPS II systems will be presented. Proving Ground activities (GOES‐R and JPSS) will dominate SPoRT's future AWIPS II activities, including tool development as well as enhancements to existing products. In early 2012 SPoRT initiated the Experimental Product Development Team, a group of AWIPS II developers from several institutions supporting NWS forecasters with innovative products. The results of the team's spring and fall 2013 meeting will be presented. Since AWIPS II developers now include employees at WFOs, as well as many other institutions related to weather forecasting, the NWS has dealt with a multitude of software governance issues related to the difficulties of multiple remotely collaborating software developers. This presentation will provide additional examples of Research‐to‐Operations plugins, as well as an update on how governance issues are being handled in the AWIPS II developer community.

Burks, Jason E.↗

The Use of the STAGS Finite Element Code in Stitched Structures Development

In the last 30 years NASA has worked in collaboration with industry to develop enabling technologies needed to make aircraft more fuel-efficient and more affordable. The focus on the airframe has been to reduce weight, improve damage tolerance and better understand structural behavior under realistic flight and ground loading conditions. Stitched structure is a technology that can address the weight savings, cost reduction, and damage tolerance goals, but only if it is supported by accurate analytical techniques. Development of stitched technology began in the 1990's as a partnership between NASA and Boeing (McDonnell Douglas at the time) under the Advanced Composites Technology Program and has continued under various titles and programs and into the Environmentally Responsible Aviation Project today. These programs contained development efforts involving manufacturing development, design, detailed analysis, and testing. Each phase of development, from coupons to large aircraft components was supported by detailed analysis to prove that the behavior of these structures was well-understood and predictable. The Structural Analysis of General Shells (STAGS) computer code was a critical tool used in the development of many stitched structures. As a key developer of STAGS, Charles Rankin's contribution to the programs was quite significant. Key features of STAGS used in these analyses and discussed in this paper include its accurate nonlinear and post-buckling capabilities, its ability to predict damage growth, and the use of Lagrange constraints and follower forces.

Jegley, Dawn C.↗

Nuclear Cryogenic Propulsion Stage Affordable Development Strategy

The development of nuclear power for space use in nuclear thermal propulsion (NTP) systems will involve significant expenditures of funds and require major technology development efforts. The development effort must be economically viable yet sufficient to validate the systems designed. Efforts are underway within the National Aeronautics and Space Administration's (NASA) Nuclear Cryogenic Propulsion Stage Project (NCPS) to study what a viable program would entail. The study will produce an integrated schedule, cost estimate and technology development plan. This will include the evaluation of various options for test facilities, types of testing and use of the engine, components, and technology developed. A "Human Rating" approach will also be developed and factored into the schedule, budget and technology development approach.

Doughty, Glen E.↗

SCaN Testbed Software Development and Lessons Learned

National Aeronautics and Space Administration (NASA) has developed an on-orbit, adaptable, Software Defined Radio (SDR)Space Telecommunications Radio System (STRS)-based testbed facility to conduct a suite of experiments to advance technologies, reduce risk, and enable future mission capabilities on the International Space Station (ISS). The SCAN Testbed Project will provide NASA, industry, other Government agencies, and academic partners the opportunity to develop and field communications, navigation, and networking technologies in the laboratory and space environment based on reconfigurable, SDR platforms and the STRS Architecture.The SDRs are a new technology for NASA, and the support infrastructure they require is different from legacy, fixed function radios. SDRs offer the ability to reconfigure on-orbit communications by changing software for new waveforms and operating systems to enable new capabilities or fix any anomalies, which was not a previous option. They are not stand alone devices, but required a new approach to effectively control them and flow data. This requires extensive software to be developed to utilize the full potential of these reconfigurable platforms. The paper focuses on development, integration and testing as related to the avionics processor system, and the software required to command, control, monitor, and interact with the SDRs, as well as the other communication payload elements. An extensive effort was required to develop the flight software and meet the NASA requirements for software quality and safety. The flight avionics must be radiation tolerant, and these processors have limited capability in comparison to terrestrial counterparts. A big challenge was that there are three SDRs onboard, and interfacing with multiple SDRs simultaneously complicatesd the effort. The effort also includes ground software, which is a key element for both the command of the payload, and displaying data created by the payload. The verification of the software was an extensive effort. The challenges of specifying a suitable test matrix with reconfigurable systems that offer numerous configurations is highlighted. Since the flight system testing requires methodical, controlled testing that limits risk, a nearly identical ground system to the on-orbit flight system was required to develop the software and write verification procedures before it was installed and tested on the flight system. The development of the SCAN testbed was an accelerated effort to meet launch constraints, and this paper discusses tradeoffs made to balance needed software functionality and still maintain the schedule. Future upgrades are discussed that optimize the avionics and allow experimenters to utilize the SCAN testbed potential.

radio communication↗