SEARCH · Search NASA
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.
The hardware development schedule for the Common Lunar Lander's (CLLs) tracking system is presented. Among the topics covered are the following: historical perspective, solution options, industry contacts, and the rationale for selection.
A set of benchmark tests were developed to analyze and measure Space Network scheduling characteristics and to assess the potential benefits of a proposed flexible scheduling concept. This paper discusses the role of the benchmark tests in evaluating alternative flexible scheduling approaches and defines a set of performance measurements. The paper describes the rationale for the benchmark tests as well as the benchmark components, which include models of the Tracking and Data Relay Satellite (TDRS), mission spacecraft, their orbital data, and flexible requests for communication services. Parameters which vary in the tests address the degree of request flexibility, the request resource load, and the number of events to schedule. Test results are evaluated based on time to process and schedule quality. Preliminary results and lessons learned are addressed.
A baseline implementation plan, including alternative implementation approaches for critical software elements and variants to the plan, was developed. The basic philosophy was aimed at: (1) a progressive release of capability for three major computing systems, (2) an end product that was a working tool, (3) giving participation to industry, government agencies, and universities, and (4) emphasizing the development of critical elements of the IPAD framework software. The results of these tasks indicate an IPAD first release capability 45 months after go-ahead, a five year total implementation schedule, and a total developmental cost of 2027 man-months and 1074 computer hours. Several areas of operational cost increases were identified mainly due to the impact of additional equipment needed and additional computer overhead. The benefits of an IPAD system were related mainly to potential savings in engineering man-hours, reduction of design-cycle calendar time, and indirect upgrading of product quality and performance.
The NASA X-57 distributed electric propulsion flight demonstrator uses a high-lift propeller system to maintain low-speed capability with a highly loaded, cruise-efficient wing. Previous research showed that the control scheme for the high-lift propellers was a crucial factor to enable an adequate balance between stabilized glideslope control and appropriate lift margin during the approach-to-landing phase of flight. This paper expands the high-lift propeller control considerations to include all phases of low-speed flight, including preflight, taxi, takeoff, initial climb, approach, and landing. Two control modes, termed airspeed and fixed mode, are developed in this paper. The airspeed mode varies propeller torque based on equivalent airspeed to account for different phases of ground and flight operations. The fixed mode operates the high-lift propeller system at a fixed rotational speed to account for failures in the air data system, preflight checkout, and high-performance takeoff operations. Modeling of the high-lift propellers within the X-57 low-speed flight envelope shows that (1) the structural rotational speed limit of the propeller blades limits their effectiveness at higher altitudes and airspeeds, (2) the speed setting of the fixed mode is set by the maximum torque of the airspeed mode, and (3) minimizing the potential for windmilling in non-standard conditions sets the torque schedule at higher speeds. Additionally, the fixed mode is shown to provide an increased climb rate during normal takeoff operations.
Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a streamlined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to pro-ceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule, development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor downselection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measurements for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.
Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a stream-lined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to proceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule. Development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor down-selection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measure-ments for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.
This presentation provides a status of the Goddard Space Flight Center (GSFC) effort to increase foundational knowledge of Product Development Leads (PDLs) in schedule and cost management including earned value management (EVM). In 2012, GSFC’s Engineering and Technology Directorate (ETD) implemented an in-house training program to prepare PDLs for managing the technical, cost, schedule, and risk aspects of spaceflight systems to meet their subsystem commitments. Developed in-house, the PDL training program provides an integrated approach to requirements development, risk, schedule and cost management, EVM, performance tracking, and other areas. The program has been held twice yearly since its inception with 531 participating and 451 completing the curriculum. In 2017, the program won the Robert H. Goddard award for Quality and Process Improvement. Program development and evolution were presented in the 2018 NASA Schedule and Cost Symposium. The presentation was so well received that this year we focus on one workshop within the program: Schedule and Cost Development, including EVM. We examine the on-going logic modeling process and how participant and stakeholder data influence workshop content and design, and how the disciplines of schedule and cost contribute to mission success. In this presentation we refresh you on how the approach integrates lecture, small group discussion, estimating, case study exercises, and problem solving. We update you on the data collected from participants and stakeholders, and we discuss how we use these data to measure training effectiveness. Specific topics include: • How the logic model is used as the backbone for continuous program improvement, • How feedback influences implementation and curriculum updates, • How data collection and analysis inform workshop content and development, including participant discoveries of EVM data, • How including the resource analyst and planner in the product development team supports project success.
Programs such as space transportation systems are developed and deployed only rarely, and they have long development schedules and large development and life cycle costs (LCC). They have not historically had their LCC predicted well and have only had an effort to control the DDT&E phase of the programs. One of the factors driving the predictability, and thus control, of the LCC of a program is the maturity of the technologies incorporated in the program. If the technologies incorporated are less mature (as measured by their Technology Readiness Level - TRL), then the LCC not only increases but the degree of increase is difficult to predict. Consequently, new programs avoid incorporating technologies unless they are quite mature, generally TRL greater than or equal to 7 (system prototype demonstrated in a space environment) to allow better predictability of the DDT&E phase costs unless there is no alternative. On the other hand, technology development programs rarely develop technologies beyond TRL 6 (system/subsystem model or prototype demonstrated in a relevant environment). Currently the lack of development funds beyond TRL 6 and the major funding required for full scale development leave little or no funding available to prototype TRL 6 concepts so that hardware would be in the ready mode for safe, reliable and cost effective incorporation. The net effect is that each new program either incorporates little new technology or has longer development schedules and costs, and higher LCC, than planned. This paper presents methods to ensure that advanced technologies are incorporated into future programs while providing a greater accuracy of predicting their LCC. One method is having a dedicated organization to develop X-series vehicles or separate prototypes carried on other vehicles. The question of whether such an organization should be independent of NASA and/or have an independent funding source is discussed. Other methods are also discussed. How to make the choice of which technologies to pursue to the prototype level is also discussed since, to achieve better LCC, first the selection of the appropriate technologies.
Nuclear Thermal Propulsion (NTP) is a concept which uses a nuclear reactor to heat a propellant to high temperatures without combustion and can achieve significantly greater specific impulse than chemical engines. NTP has been considered many times for human and cargo missions beyond low earth orbit. A lot of development and technical maturation of NTP components took place during the Rover/NERVA program of the 60's and early 70's. Other NTP programs and studies followed attempting to further mature the NTP concept and identify a champion customer willing to devote the funds and support the development schedule to a demonstration mission. Budgetary constraints require the use of an affordable development and qualification strategy that takes into account all the previous work performed on NTP to construct an existing database, and include lessons learned and past guidelines followed. Current guidelines and standards NASA uses for human rating chemical rocket engines is referenced. The long lead items for NTP development involve the fuel elements of the reactor and ground testing the engine system, subsystem, and components. Other considerations which greatly impact the development plans includes the National Space Policy, National Environmental Policy Act, Presidential Directive/National Security Council Memorandum #25 (Scientific or Technological Experiments with Possible Large-Scale Adverse Environmental Effects and Launch of Nuclear Systems into Space), and Safeguards and Security. Ground testing will utilize non-nuclear test capabilities to help down select components and subsystems before testing in a nuclear environment to save time and cost. Existing test facilities with minor modifications will be considered to the maximum extent practical. New facilities will be designed to meet minimum requirements. Engine and test facility requirements are based on the driving mission requirements with added factors of safety for better assurance and reliability. Emphasis will be placed on small engines, since the smaller the NTP engine, the easier it is to transport, assemble/disassemble, and filter the exhaust during tests. A new ground test concept using underground bore holes (modeled after the underground nuclear test program) to filter the NTP engine exhaust is being considered. The NTP engine system design, development, test, and evaluation plan includes many engine components and subsystems, which are very similar to those used in chemical engines, and can be developed in conjunction with them Other less mature NTP engine components and subsystems (e.g., reactor) will be thoroughly analyzed and tested to acceptable levels recommended by the referenced standards and guidelines. The affordable development strategy also considers a prototype flight test, as a final step in the development process. Preliminary development schedule estimates show that an aggressive development schedule (without much margin) will be required to be flight ready for a 2033 human mission to Mars.
Nuclear Thermal Propulsion (NTP) is a concept which uses a nuclear reactor to heat a propellant to high temperatures without combustion and can achieve significantly greater specific impulse than chemical engines. NTP has been considered many times for human and cargo missions beyond low earth orbit. A lot of development and technical maturation of NTP components took place during the Rover/NERVA program of the 60's and early 70's. Other NTP programs and studies followed attempting to further mature the NTP concept and identify a champion customer willing to devote the funds and support the development schedule to a demonstration mission. Budgetary constraints require the use of an affordable development and qualification strategy that takes into account all the previous work performed on NTP to construct an existing database, and include lessons learned and past guidelines followed. Current guidelines and standards NASA uses for human rating chemical rocket engines is referenced. The long lead items for NTP development involve the fuel elements of the reactor and ground testing the engine system, subsystem, and components. Other considerations which greatly impact the development plans includes the National Space Policy, National Environmental Policy Act, Presidential Directive/National Security Council Memorandum #25 (Scientific or Technological Experiments with Possible Large-Scale Adverse Environmental Effects and Launch of Nuclear Systems into Space), and Safeguards and Security. Ground testing will utilize non-nuclear test capabilities to help down select components and subsystems before testing in a nuclear environment to save time and cost. Existing test facilities with minor modifications will be considered to the maximum extent practical. New facilities will be designed to meet minimum requirements. Engine and test facility requirements are based on the driving mission requirements with added factors of safety for better assurance and reliability. Emphasis will be placed on small engines, since the smaller the NTP engine, the easier it is to transport, assemble/disassemble, and filter the exhaust during tests. A new ground test concept using underground bore holes (modeled after the underground nuclear test program) to filter the NTP engine exhaust is being considered. The NTP engine system design, development, test, and evaluation plan includes many engine components and subsystems, which are very similar to those used in chemical engines, and can be developed in conjunction with them Other less mature NTP engine components and subsystems (e.g., reactor) will be thoroughly analyzed and tested to acceptable levels recommended by the referenced standards and guidelines. The affordable development strategy also considers a prototype flight test, as a final step in the development process. Preliminary development schedule estimates show that an aggressive development schedule (without much margin) will be required to be flight ready for a 2033 human mission to Mars.
In FY11, NASA formulated a plan for Nuclear Thermal Propulsion (NTP) development that included Foundational Technology Development followed by system-level Technology Demonstrations. The ongoing NTP project, funded by NASA's Advanced Exploration Systems (AES) program, is focused on Foundational Technology Development and includes 5 key task activities: (1) Fuel element fabrication and non-nuclear validation testing of heritage fuel options; (2) Engine conceptual design; (3) Mission analysis and engine requirements definition; (4) Identification of affordable options for ground testing; and (5) Formulation of an affordable and sustainable NTP development program. Performance parameters for Point of Departure designs for a small criticality-limited and full size 25 klb (sub f) (kip, or 1000 pound-force)-class engine were developed during FYs 13-14 using heritage fuel element designs for both Rover NERVA (Nuclear Engine for Rocket Vehicle Applications) Graphite Composite (GC) and Ceramic Metal (Cermet) fuel forms. To focus the fuel development effort and maximize use of its resources, the AES program decided, in FY14, that a leader-follower down-selection between GC and cermet fuel was required. An Independent Review Panel (IRP) was convened by NASA and tasked with reviewing the available fuel data and making a recommendation to NASA. In February 2015, the IRP recommended and the AES program endorsed GC as the leader fuel In FY14, a preliminary development schedule DDTE (Design Development Test and Evaluation) plan was produced by GRC (Glenn Research Center), DOE (Department of Energy) and industry for the AES program. Assumptions, considerations and key task activities are presented here. At the direction of NASA HQ (32515), NASA and DOE are to work together to formulate a detailed development plan and schedule allowing the affordable development of a small (7.5-16.5 klbf) GC engine for possible flight technology demonstration (FTD) mission within a 10-year timeframe.
NASA has completed a preliminary mission and systems study of nuclear electric propulsion (NEP) systems for 'split-sprint' human exploration and related robotic cargo missions to Mars. This paper describes the study, the mission architecture selected, the NEP system and technology development needs, proposed development schedules, and estimated development costs. Since current administration policy makers have delayed funding for key technology development activities that could make Mars exploration missions a reality in the near future, NASA will have time to evaluate various alternate mission options, and it appears prudent to ensure that Mars mission plans focus on astronaut and mission safety, while reducing costs to acceptable levels. The split-sprint nuclear electric propulsion system offers trip times comparable to nuclear thermal propulsion (NTP) systems, while providing mission abort opportunities that are not possible with 'reference' mission architectures. Thus, NEP systems offer short transit times for the astronauts, reducing the exposure of the crew to intergalactic cosmic radiation. The high specific impulse of the NEP system, which leads to very low propellant requirements, results in significantly lower 'initial mass in low earth orbit' (IMLEO). Launch vehicle packaging studies show that the NEP system can be launched, assembled, and deployed, with about one less 240-metric-ton heavy lift launch vehicle (HLLV) per mission opportunity - a very Technology development cost of the nuclear reactor for an NEP system would be shared with the proposed nuclear surface power systems, since nuclear systems will be required to provide substantial electrical power on the surface of Mars. The NEP development project plan proposed includes evolutionary technology development for nuclear electric propulsion systems that expands upon SP-100 (Space Power - 100 kw(e)) technology that has been developed for lunar and Mars surface nuclear power, and small NEP systems for interplanetary probes. System upgrades are expected to evolve that will result in even shorter trip times, improved payload capabilities, and enhanced safety and reliability.
Bipropellant propulsion systems currently represent the largest bus subsystem for many missions. These missions range from low Earth orbit satellite to geosynchronous communications and planetary exploration. The payoff of high performance bipropellant systems is illustrated by the fact that Aerojet Redmond has qualified a commercial NTO/MMH engine based on the high Isp technology recently delivered by this program. They are now qualifying a NTO/hydrazine version of this engine. The advanced rhenium thrust chambers recently provided by this program have raised the performance of earth storable propellants from 315 sec to 328 sec of specific impulse. The recently introduced rhenium technology is the first new technology introduced to satellite propulsion in 30 years. Typically, the lead time required to develop and qualify new chemical thruster technology is not compatible with program development schedules. These technology development programs must be supported by a long term, Base R&T Program, if the technology s to be matured. This technology program then addresses the need for high performance, storable, on-board chemical propulsion for planetary rendezvous and descent/ascent. The primary NASA customer for this technology is Space Science, which identifies this need for such programs as Mars Surface Return, Titan Explorer, Neptune Orbiter, and Europa Lander. High performance (390 sec) chemical propulsion is estimated to add 105% payload to the Mars Sample Return mission or alternatively reduce the launch mass by 33%. In many cases, the use of existing (flight heritage) propellant technology is accommodated by reducing mission objectives and/or increasing enroute travel times sacrificing the science value per unit cost of the program. Therefore, a high performance storable thruster utilizing fluorinated oxidizers with hydrazine is being developed.
Earned Value Management (EVM), like project management, is as much art as it is science to develop an implementation plan for a project. This presentation will cover issues that were overcome and the implementation strategy to deploy Earned Value Management (EVM) within the Constellation Program (CxP), EVA Systems Project Office (ESPO), as well as discuss additional hurdles that currently prevent the organization from optimizing EVM. Each organization and each project within an organization needs to mold an EVM implementation plan around existing processes and tools, while at the same time revising those existing processes and tools as necessary to make them compatible with EVM. The ESPO EVM implementation covers work breakdown structure, organizational breakdown structure, control account, work/planning package development; integrated master schedule development using an integrated master plan; incorporating reporting requirements for existing funding process such as Planning, Programming, Budgeting, and Execution (PPBE) and JSC Internal Task Agreements (ITA); and interfacing with other software tools such as the Systems Applications and Products (SAP) accounting system and the CxP wInsight EVM analysis tool. However, there are always areas for improvement and EVM is no exception. As EVM continues to mature within the NASA CxP, these areas will continue to be worked to resolution to provide the Program Managers, Project Managers, and Control Account Managers the best EVM data possible to make informed decisions.
In many domains, scheduling a sequence of jobs is an important function contributing to the overall efficiency of the operation. At Boeing, we develop schedules for many different domains, including assembly of military and commercial aircraft, weapons systems, and space vehicles. Boeing is under contract to develop scheduling systems for the Space Station Payload Planning System (PPS) and Payload Operations and Integration Center (POIC). These applications require that we respect certain sequencing restrictions among the jobs to be scheduled while at the same time assigning resources to the jobs. We call this general problem scheduling and resource allocation. Genetic algorithms (GA's) offer a search method that uses a population of solutions and benefits from intrinsic parallelism to search the problem space rapidly, producing near-optimal solutions. Good intermediate solutions are probabalistically recombined to produce better offspring (based upon some application specific measure of solution fitness, e.g., minimum flowtime, or schedule completeness). Also, at any point in the search, any intermediate solution can be accepted as a final solution; allowing the search to proceed longer usually produces a better solution while terminating the search at virtually any time may yield an acceptable solution. Many processes are constrained by restrictions of sequence among the individual jobs. For a specific job, other jobs must be completed beforehand. While there are obviously many other constraints on processes, it is these on which we focussed for this research: how to allocate crews to jobs while satisfying job precedence requirements and personnel, and tooling and fixture (or, more generally, resource) requirements.
Demonstrate increased, more consistent use of Performance‐ Based Navigation (PBN). Accelerate transfer of NASA scheduling and spacing technologies for inclusion in late mid‐term NAS. During high‐fidelity human‐in‐the‐loop simulations of Terminal Sequencing and Spacing, air traffic controllers have significantly improved their use of PBN procedures during busy traffic periods without increased workload. Executed an aggressive, short timeframe development schedule. Developed TSS prototype based upon FAA operational systems. Conducted multiple joint FAA/NASA human‐in‐the‐loop simulations. Performed repeated incremental deliveries of tech transfer material to non‐traditional RTT stakeholders. Will continue to participate in later phases of FAA acquisition process. ATD‐1 transferred Terminal Sequencing and Spacing (TSS) technologies to the FAA. TSS enables routine use of underutilized advanced avionics and PBN procedures. Potential benefits to airlines operating at initial TSS sites estimated to be $300‐400M/year. FAA is planning for an initial capability in the NAS in 2018.
The Mars 2020 Rover mission is using automated scheduling in two capacities. As of March 2021 a ground-based scheduler automatically schedules rover wake/sleep and preheats to support Mars 2020 daily operations. Included in the ground system is an explainable scheduling tool that allows users in-sight into the schedule developed by the automated scheduler. An onboard scheduler that will allow the rover autonomously better account for variations in execution is in development for use later in the mission.
Both the Department of Defense and NASA have clearly defined missions for the Saturn which cannot be performed by a lesser vehicle. In addition, many missions which can be marginally performed by less capable vehicles in the early years, will benefit greatly by use of the Saturn. Lastly, there are, no doubt, missions for the Saturn which cannot be clearly foresen at this time but which will come to light in the normal course of events. Although the Saturn need Is well established, the selection of the upper stage configurations remains to be made. Among the many factors to be considered in such a selection, the mission requirements are among the most important and caution must be exercised in compromising the potential of the Saturn to meet these requirements for such expedients as somewhat faster and less expensive vehicle development schedules. It is thus the purpose of this chapter to review for the reader the many Saturn applications of foreseeable interest to the Department of Defense and NASA. Having done this, the relative priorities of the missions will be discussed and the relatively high priority missions will be incorporated into a suggested launch schedule. Other NASA projects leading into and supporting the Saturn projects will be indicated. A funding plan based on the Saturn launch schedule will then be developed for the spacecraft and payloads involved. The chapter will conclude with a discussion of the constraints placed upon the Saturn configuration by the missions and payloads.