SEARCH · Engineering Papers
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.
A program plan is presented for a space communications application utilizing the 30/20 GHz frequency bands (30 GHz uplink and 20 GHz downlink). Results of market demand studies and spacecraft systems studies which significantly affect the supporting research and technology program are also presented, along with the scheduled activities of the program plan.
The Autonomous Power System (APS) project at NASA LeRC is designed to demonstrate the applications of integrated intelligent diagnosis, control, and scheduling techniques to space power distribution systems. The project consists of three elements: the Autonomous Power Expert System (APEX) for Fault Diagnosis, Isolation, and Recovery (FDIR); the Autonomous Intelligent Power Scheduler (AIPS) to efficiently assign activities start times and resources; and power hardware (Brassboard) to emulate a space-based power system. The AIPS scheduler was tested within the APS system. This scheduler is able to efficiently assign available power to the requesting activities and share this information with other software agents within the APS system in order to implement the generated schedule. The AIPS scheduler is also able to cooperatively recover from fault situations by rescheduling the affected loads on the Brassboard in conjunction with the APEX FDIR system. AIPS served as a learning tool and an initial scheduling testbed for the integration of FDIR and automated scheduling systems. Many lessons were learned from the AIPS scheduler and are now being integrated into a new scheduler called SCRAP (Scheduler for Continuous Resource Allocation and Planning). This paper will service three purposes: an overview of the AIPS implementation, lessons learned from the AIPS scheduler, and a brief section on how these lessons are being applied to the new SCRAP scheduler.
The document of ASTER Calibration Requirement specifies the following items related to spectral and radiometric characteristics of the ASTER instrument: (1) characteristics whose knowledge is specified, (2) requirement for knowledge of the characteristics, (3) methodology for characteristics evaluation, and (4) supplementary information and data related with characteristics evaluation. This document is applicable to the document of the ASTER Instrument Specification on Observational Performances, and will be a part of the ASTER Calibration Plan. ASTER Calibration Requirement is scheduled to establish the concept and framework by March 1992 when the 5th Calibration and Data Validation Panel Meeting is held, and to determine details including requirement values and evaluation methodologies by October 1992 around which the Calibration Peer Review may be held. The ASTER Calibration Plan is planned to finish by the same time.
Construction of the Synroc Waste Treatment Facility is well underway at ANSTO. This plant has been designed to treat intermediate level liquid waste arising from the production of Mo-99 within the newly constructed ANSTO Nuclear Medicine (ANM) precinct [1]. The facility utilises ANSTO Synroc technology that has been tailored to the chemical, physical, and radiological properties of the waste. The result is a highly durable wasteform with a significant reduction in the final volume of the treated waste. This paper presents the construction status of the Synroc Waste Treatment Facility and the status of the associated technology maturation plan. Construction of the building is scheduled for completion in late 2020 followed by process installation and commissioning. A key component of the technology maturation plan has been the construction of an Inactive Engineering Demonstrator [2]. This has aided in the mitigation of risks with respect to technology selection, process integration, and process nuclearisation. Furthermore, the demonstration facility has provided an environment for the design and development of the instrumentation and control philosophy resulting in a seamlessly integrated plant control system. Successful demonstration of the technology by the inactive engineering demonstrator has significantly reduced the associated risks. Details of the Synroc Waste Treatment Facility project progress will also be presented. (authors)
The NASA Hubble Space Telescope (HST) was designed to be deployed and later serviced for maintenance and upgrades, as required, by the space shuttle fleet, with a Goodyear mission life for the batteries. HST was deployed 380 miles above the Earth, from Space Shuttle Discovery, on April 25, 1990. Four servicing missions, (SM1, SM2, SM3A, AND SM3B) have been performed. Astronauts have replaced or modified optics, solar arrays, a power control unit, and various science packages. A fifth Servicing Mission, SM4 scheduled for early 2004, is planned to replace the batteries for the first time. The HST is powered by solar array wings and nickel hydrogen (NiH2) Duracell batteries, which are grouped into two parallel battery modules of three parallel batteries each. With a design life of 7 years at launch, these batteries have surpassed 12 years in orbit, which gives HST the highest number of charge/discharge cycles of any NiH2 battery currently in low earth orbit (LEO) application. Being in a LEO orbit, HST has a 45-minute umbra period, during which spacecraft power requirements normally force the batteries into discharge, and a 60-minute sun period, which is available for battery recharge. The intent of this paper is to address the issue of NiH2 battery reliability and how battery capacity degradation can impact scheduling of a Servicing Mission to bring replacement batteries to HST, and extend mission life till deployment of Next Generation Space Telescope (NGST), planned for 2008 at the earliest.
Expected development maturity under contract (spec) should correlate with Project/Program Approved MGA Depletion Schedule in Mass Properties Control Plan. If specification NTE, MGA is inclusive of Actual MGA (A5 & A6). If specification is not an NTE Actual MGA (e.g. nominal), then MGA values are reduced by A5 values and A5 is representative of remaining uncertainty. Basic Mass = Engineering Estimate based on design and construction principles with NO embedded margin MGA Mass = Basic Mass * assessed % from approved MGA schedule. Predicted Mass = Basic + MGA. Aggregate MGA % = (Aggregate Predicted - Aggregate Basic) /Aggregate Basic.
Airports globally are shifting from ICE-powered to electric Ground Support Equipment (eGSE) to enhance efficiency, reduce operational costs, and improve operator health. Leveraging predictable routes, flat terrain, and low operational speeds, airports provide ideal conditions for electrification. This study evaluates freight GSE electrification at Dallas-Fort Worth International Airport (DFW), USA, using the Agile@ platform, which integrates three analytical methods: Freight Facility Model (FFM), Activity-Structure-Intensity-Fuel (ASIF), and Monte Carlo simulations. Results from 10,000 simulations indicate modest but critical increases in electricity demand and significant variability in GSE energy consumption. These insights emphasize the importance of data-driven scheduling, targeted maintenance, and strategic infrastructure planning. For high-uncertainty scenarios, airports are advised to deploy buffer energy storage systems (battery banks), implement demand-response charging strategies, schedule flexible workforce shifts, and prioritize proactive maintenance-particularly for equipment with higher operational uncertainty, such as tug tractors with trailers. Agile@ thus offers a robust, scalable, and data-driven framework to optimize long-term GSE planning and enhance reliability across diverse airport environments.
The general topics covered in the engineering technical planning briefing are 1) overviews of NASA, Marshall Space Flight Center (MSFC), and Engineering, 2) the NASA Systems Engineering(SE) Engine and its implementation , 3) the NASA Project Life Cycle, 4) MSFC Technical Management Branch Services in relation to the SE Engine and the Project Life Cycle , 5) Technical Reviews, 6) NASA Human Factor Design Guidance , and 7) the MSFC Human Factors Team. The engineering technical review portion of the presentation is the primary focus of the overall presentation and will address the definition of a design review, execution guidance, the essential stages of a technical review, and the overall review planning life cycle. Examples of a technical review plan content, review approaches, review schedules, and the review process will be provided and discussed. The human factors portion of the presentation will focus on the NASA guidance for human factors. Human factors definition, categories, design guidance, and human factor specialist roles will be addressed. In addition, the NASA Systems Engineering Engine description, definition, and application will be reviewed as background leading into the NASA Project Life Cycle Overview and technical review planning discussion.
A key element of the National Vision for Space Exploration is the development of a heavy-lift Cargo Launch Vehicle (CaLV). Missions to the Moon, Mars, and beyond are only possible with the logistical capacity of putting large payloads in low-earth orbit. However, beyond simple logistics, there exists the need for this capability to be as cost effective as possible to ensure mission sustainability. An element of the CaLV project is, therefore, the development of the RS-25, which represents the evolution of the proven Space Shuttle Main Engine (SSME) into a high-performance, cost-effective expendable rocket engine. The development of the RS-25 will be built upon the foundation of over one million seconds of accumulated hot-fire time on the SSME. Yet in order to transform the reusable SSME into the more cost-effective, expendable RS-25 changes will have to be made. Thus the project will inevitably strive to maintain a balance between demonstrated heritage products and processes and the utilization of newer technology developments. Towards that end, the Core Stage Engine Office has been established at the NASA Marshall Space Flight Center to initiate the design and development of the RS-25 engine. This paper is being written very early in the formulation phase of the RS-25 project. Therefore the focus of this paper will be to present the scope, challenges, and opportunities for the RS-25 project. Early schedules and development decisions and plans will be explained. For not only must the RS-25 project achieve cost effectiveness through the development of new, evolved components such as a channel-wall nozzle, a new HIP-bonded main combustion chamber, and several others, it must simultaneously develop the means whereby this engine can be manufactured on a scale never envisioned for the SSME. Thus, while the overall project will span the next eight to ten years, there is little doubt that even this schedule is aggressive with a great deal of work to accomplish.
The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include quantifying resource or capabilities to be allocated, prioritizing science observations and estimating resource needs for each, working inter-and intra-orbit trades of these resources among the Project elements, and planning real-time science activity. The first major mission planning activity, a high level, orbit-by-orbit allocation of resources among science objectives, has already been completed; and results are illustrated in the paper. To make efficient use of limited resources, Galileo mission planning will rely on automated mission planning tools capable of dealing with interactions among time-varying downlink capability, real-time science and engineering data transmission, and playback of recorded data. A new generic mission planning tool is being adapted for this purpose.
Continuing remote controlled pulsar observations are noted, along with routine observations of 22 pulsars. Preliminary installation of equipment for planned unattended operation of the Venus Station is reported, along with extensive measurements and performance evaluation of the 26-m antenna. Support of the X-band radar at the Mars Station (DSS 14), and stability and reliability testing of the DSS 13 receiving system is reported. Klystron testing and other DSN support activities of the DSN High-Power Transmitter Maintenance Facility are noted, along with energy conservation modifications to two buildings at DSS 13. Radio Science experiment support included Planetary Radio Astronomy, Pulsar Rotation Constancy, Interstellar Microwave Spectroscopy, and Very Long Baseline Interferometry observations. An increased schedule of clock synchronization transmissions, planned on five-day centers, is noted, as 39 transmissions were made to Australia, DSS 43, and Spain, DSS 63.
This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.
The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd generation system by 2 orders of magnitude - equivalent to a crew risk of 1-in-10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. To best direct technology development decisions, analytical models are employed to accurately predict the benefits of each technology toward potential space transportation architectures as well as the risks associated with each technology. Rigorous systems analysis provides the foundation for assessing progress toward safety and cost goals. The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.
The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd-generation system by 2 orders of magnitude - equivalent to a crew risk of 1-in-10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. To best direct technology development decisions, analytical models are employed to accurately predict the benefits of each technology toward potential space transportation architectures as well as the risks associated with each technology. Rigorous systems analysis provides the foundation for assessing progress toward safety and cost goals. The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.
The Voyager mission to the giant outer planets of our solar system is described. Scientific highlights include interplanetary cruise, Jupiter, Saturn, Uranus, and their vast satellite and ring systems. Detailed plans are provided for the August 1989 Neptune encounter and subsequent interstellar journey to reach the heliopause. As background, the elements of an unmanned space mission are explained, with emphasis on the capabilities of the spacecraft and the scientific sensors. Other topics include the Voyager Grand Tour trajectory design, deep-space navigation, and gravity-assist concepts. The Neptune flyby is animated through the use of computer-generated, flip-page movie frames that appear in the corners of the publication. Useful historical information is also presented, including facts associated with the Voyager mission. Finally, short summaries are provided to describe the major objectives and schedules for several space missions planned for the remainder of the 20th century.
An example system includes an aggregator configured to receive a service collaboration request and iteratively determine, based on minimum and maximum power values for DERs under its management, an optimized operation schedule. The aggregator may also be configured to iteratively determine, based on the optimized operation schedule, an estimated flexibility range for devices under its management and output an indication thereof. The system may also include a power management unit (PMU) configured to iteratively receive the indication and determine, based on a network model that includes the estimated flexibility range, a reconfiguration plan and an overall optimized operation schedule for the network. The PMU may also be configured to iteratively cause reconfiguration of the network based on the plan. The PMU and aggregator may also be configured to iteratively, at a fast timescale, cause energy resources under their management to modify operation based on the overall optimized operation schedule.
The international character of future manned space missions will compel the involvement of several international space agencies in mission planning tasks. Additionally, the community of users requires a higher degree of freedom for experiment planning. Both of these problems can be solved by a decentralized mission planning concept using the so-called 'envelope method,' by which resources are allocated to users by distributing resource profiles ('envelopes') which define resource availabilities at specified times. The users are essentially free to plan their activities independently of each other, provided that they stay within their envelopes. The new developments were aimed at refining the existing vague envelope concept into a practical method for decentralized planning. Selected critical functions were exercised by planning an example, founded on experience acquired by the MSCC during the Spacelab missions D-1 and D-2. The main activity regarding future mission planning tasks was to improve the existing MSCC mission planning system, using new techniques. An electronic interface was developed to collect all formalized user inputs more effectively, along with an 'envelope generator' for generation and manipulation of the resource envelopes. The existing scheduler and its data base were successfully replaced by an artificial intelligence scheduler. This scheduler is not only capable of handling resource envelopes, but also uses a new technology based on neuronal networks. Therefore, it is very well suited to solve the future scheduling problems more efficiently. This prototype mission planning system was used to gain new practical experience with decentralized mission planning, using the envelope method. In future steps, software tools will be optimized, and all data management planning activities will be embedded into the scheduler.
The Hubble Space Telescope (HST) team is preparing for NASA's third scheduled service call to Hubble. This mission, STS-103, will launch from Kennedy Space Center aboard the Space Shuttle Discovery. The seven flight crew members are Commander Curtis L. Brown, Pilot Scott J. Kelly, European Space Agency (ESA) astronaut Jean-Francois Clervoy who will join space walkers Steven L. Smith, C. Michael Foale, John M. Grunsfeld, and ESA astronaut Claude Nicollier. The objectives of the HST Third Servicing Mission (SM3A) are to replace the telescope's six gyroscopes, a Fine-Guidance Sensor, an S-Band Single Access Transmitter, a spare solid-state recorder and a high-voltage/temperature kit for protecting the batteries from overheating. In addition, the crew plans to install an advanced computer that is 20 times faster and has six times the memory of the current Hubble Space Telescope computer. To prepare for these extravehicular activities (EVAs), the SM3A astronauts participated in Crew Familiarization sessions with the actual SM3A flight hardware. During these sessions the crew spent long hours rehearsing their space walks in the Guidance Navigation Simulator and NBL (Neutral Buoyancy Laboratory). Using space gloves, flight Space Support Equipment (SSE), and Crew Aids and Tools (CATs), the astronauts trained with and verified flight orbital replacement unit (ORU) hardware. The crew worked with a number of trainers and simulators, such as the High Fidelity Mechanical Simulator, Guidance Navigation Simulator, System Engineering Simulator, the Aft Shroud Door Trainer, the Forward Shell/Light Shield Simulator, and the Support Systems Module Bay Doors Simulator. They also trained and verified the flight Orbital Replacement Unit Carrier (ORUC) and its ancillary hardware. Discovery's planned 10-day flight is scheduled to end with a night landing at Kennedy.