Search NASA⌕ Search

SEARCH · Search NASA

Results for “scheduler development”

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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS1986

Time-based air traffic management using expert systems

A prototype expert system has been developed for the time scheduling of aircraft into the terminal area. The three functions of the air-traffic-control schedule advisor are as follows: (1) for each new arrival, it develops an admisible flight plan for that aircraft; (2) as the aircraft progresses through the terminal area, it monitors deviations from the aircraft's flight plan and provides advisories to return the aircraft to its assigned schedule; and (3) if major disruptions such as missed approaches occur, it develops a revised plan. The advisor is operational on a Symbolics 3600, and is programmed in MRS (a logic programming language), Lisp, and Fortran.

Tobias, L.↗
NASA NTRS1992

Integration and use of Microgravity Research Facility: Lessons learned by the crystals by vapor transport experiment and Space Experiments Facility programs

The Crystals by Vapor Transport Experiment (CVTE) and Space Experiments Facility (SEF) are materials processing facilities designed and built for use on the Space Shuttle mid deck. The CVTE was built as a commercial facility owned by the Boeing Company. The SEF was built under contract to the UAH Center for Commercial Development of Space (CCDS). Both facilities include up to three furnaces capable of reaching 850 C minimum, stand-alone electronics and software, and independent cooling control. In addition, the CVTE includes a dedicated stowage locker for cameras, a laptop computer, and other ancillary equipment. Both systems are designed to fly in a Middeck Accommodations Rack (MAR), though the SEF is currently being integrated into a Spacehab rack. The CVTE hardware includes two transparent furnaces capable of achieving temperatures in the 850 to 870 C range. The transparent feature allows scientists/astronauts to directly observe and affect crystal growth both on the ground and in space. Cameras mounted to the rack provide photodocumentation of the crystal growth. The basic design of the furnace allows for modification to accommodate techniques other than vapor crystal growth. Early in the CVTE program, the decision was made to assign a principal scientist to develop the experiment plan, affect the hardware/software design, run the ground and flight research effort, and interface with the scientific community. The principal scientist is responsible to the program manager and is a critical member of the engineering development team. As a result of this decision, the hardware/experiment requirements were established in such a way as to balance the engineering and science demands on the equipment. Program schedules for hardware development, experiment definition and material selection, flight operations development and crew training, both ground support and astronauts, were all planned and carried out with the understanding that the success of the program science was as important as the hardware functionality. How the CVTE payload was designed and what it is capable of, the philosophy of including the scientists in design and operations decisions, and the lessons learned during the integration process are descussed.

Heizer, Barbara L.↗
NASA NTRS1994

Renaissance architecture for Ground Data Systems

The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.

Perkins, Dorothy C.↗
NASA NTRS2023

Adaptive Mission Assurance (AMA) – A Conceptual Guide for NASA Missions

NASA is well acquainted with and skilled in conducting Risk Class A Safety and Mission Assurance (SMA). Class A missions are characterized as having highly specific performance with an ultra-low risk tolerance for risk and mission failure. But space is rapidly changing, and the space enterprise is challenged to pursue faster more agile mission developments with fewer resources and directed schedules. To meet this demand mission development teams face accepting more risk and trading performance within strict cost and schedule constraints. In responding to this challenge, The Aerospace Corporation has evolved the Adaptive Mission Assurance (AMA) approach. The benefit of an “adaptive” approach is most realized for smaller Research and Development (R&D), or Science and Technology (S&T) demonstration missions constrained by significantly smaller budgets and directed schedules. The challenge for these “risk tolerant, constraints-driven” missions is how to identify the most valuable mission assurance tasks that will fit within strict budgetary and schedule constraints for “gracefully” accepting risk that still achieves an agreeable expectation of mission success. AMA can respond to this challenge with little to no impact to team staffing or existing workload. This conceptual guide introduces AMA as a potential implementation for NASA Risk Class D and Sub-Class D missions.

Douglas A. Harris↗
NASA NTRS1979

Information adaptive system of NEEDS

The NASA End-to-End Data System (NEEDS) program was initiated by NASA to improve significantly the state of the art in acquisition, processing, and distribution of space-acquired data for the mid-1980s and beyond. The information adaptive system (IAS) is a program element under NEEDS Phase II which addresses sensor specific processing on board the spacecraft. The IAS program is a logical first step toward smart sensors, and IAS developments - particularly the system components and key technology improvements - are applicable to future smart efforts. The paper describes the design goals and functional elements of the IAS. In addition, the schedule for IAS development and demonstration is discussed.

Howle, W. M., Jr.↗
NASA NTRS1984

Progress in developing ultrathin solar cell blanket technology

A program was conducted to develop technologies for welding interconnects to three types of 50-micron-thick, 2 by 2-cm solar cells. Parallel-gap resistance welding was used for interconnect attachment. Weld schedules were independently developed for each of the three cell types and were coincidentally identical. Six 48-cell modules were assembled with 50-micron (nominal) thick cells, frosted fused-silica covers, silver-plated Invar interconnectors, and four different substrate designs. Three modules (one for each cell type) have single-layer Kapton (50-micron-thick) substrates. The other three modules each have a different substrate (Kapton-Kevlar-Kapton, Kapton-graphite-Kapton, and Kapton-graphite-aluminum honeycomb-graphite). All six modules were subjected to 4112 thermal cycles from -175 to 65 C (corresponding to over 40 years of simulated geosynchronous orbit thermal cycling) and experienced only negligible electrical degradation (1.1 percent average of six 48-cell modules).

Patterson, R. E.↗
NASA NTRS1991

Long range science scheduling for the Hubble Space Telescope

Observations with NASA's Hubble Space Telescope (HST) are scheduled with the assistance of a long-range scheduling system (SPIKE) that was developed using artificial intelligence techniques. In earlier papers, the system architecture and the constraint representation and propagation mechanisms were described. The development of high-level automated scheduling tools, including tools based on constraint satisfaction techniques and neural networks is described. The performance of these tools in scheduling HST observations is discussed.

Miller, Glenn↗
NASA NTRS1995

Panoramic, large-screen, 3-D flight display system design

The report documents and summarizes the results of the required evaluations specified in the SOW and the design specifications for the selected display system hardware. Also included are the proposed development plan and schedule as well as the estimated rough order of magnitude (ROM) cost to design, fabricate, and demonstrate a flyable prototype research flight display system. The thrust of the effort was development of a complete understanding of the user/system requirements for a panoramic, collimated, 3-D flyable avionic display system and the translation of the requirements into an acceptable system design for fabrication and demonstration of a prototype display in the early 1997 time frame. Eleven display system design concepts were presented to NASA LaRC during the program, one of which was down-selected to a preferred display system concept. A set of preliminary display requirements was formulated. The state of the art in image source technology, 3-D methods, collimation methods, and interaction methods for a panoramic, 3-D flight display system were reviewed in depth and evaluated. Display technology improvements and risk reductions associated with maturity of the technologies for the preferred display system design concept were identified.

Franklin, Henry↗
NASA NTRS2015

Big Software for SmallSats: Adapting CFS to CubeSat Missions

Expanding capabilities and mission objectives for SmallSats and CubeSats is driving the need for reliable, reusable, and robust flight software. While missions are becoming more complicated and the scientific goals more ambitious, the level of acceptable risk has decreased. Design challenges are further compounded by budget and schedule constraints that have not kept pace. NASA's Core Flight Software System (cFS) is an open source solution which enables teams to build flagship satellite level flight software within a CubeSat schedule and budget. NASA originally developed cFS to reduce mission and schedule risk for flagship satellite missions by increasing code reuse and reliability. The Lunar Reconnaissance Orbiter, which launched in 2009, was the first of a growing list of Class B rated missions to use cFS. Large parts of cFS are now open source, which has spurred adoption outside of NASA. This paper reports on the experiences of two teams using cFS for current CubeSat missions. The performance overheads of cFS are quantified, and the reusability of code between missions is discussed. The analysis shows that cFS is well suited to use on CubeSats and demonstrates the portability and modularity of cFS code.

Open Source↗
NASA NTRS2015

Big Software for SmallSats: Adapting cFS to CubeSat Missions

Expanding capabilities and mission objectives for SmallSats and CubeSats is driving the need for reliable, reusable, and robust flight software. While missions are becoming more complicated and the scientific goals more ambitious, the level of acceptable risk has decreased. Design challenges are further compounded by budget and schedule constraints that have not kept pace. NASA's Core Flight Software System (cFS) is an open source solution which enables teams to build flagship satellite level flight software within a CubeSat schedule and budget. NASA originally developed cFS to reduce mission and schedule risk for flagship satellite missions by increasing code reuse and reliability. The Lunar Reconnaissance Orbiter, which launched in 2009, was the first of a growing list of Class B rated missions to use cFS.

Flight Software↗
NASA NTRS1987

Space station: A program overview

An overview is presented of the NASA program for the development of the Space Station. A general representation of the initial Space Station complex is shown. The Space Station goals and program objectives are briefly reviewed, as well as the program schedule. An advanced development program and program management approach are also presented.

Ambrus, Judith H.↗
NASA NTRS2018

Development of the ITACA Network Loading Analysis Tool's Scheduling Techniques

NASA's SCENIC project aims to simplify and reduce the cost of space mission planning by creating analysis capabilities which are integrated with relevant analysis parameters specific to SCaN assets and SCaN supported user missions. The Integrated Tradespace Analysis of Communications Architectures (ITACA) will provide an all-in-one package for various analysis capabilities that normally require add-ons or multiple tools to complete. The ITACA tool will be responsible for assessing the given network architecture and generating a schedule for the missions as well as the assets. ITACA will allow users to evaluate the quality of service of a given network and determine whether or not the network will satisfy the mission's requirements. ITACA is currently under development, and during the spring of 2018 major development in the tools scheduling techniques were completed. A total of seven different techniques were completed.

space communications↗
NASA NTRS1996

Scheduled civil aircraft emission inventories for 1992: Database development and analysis

This report describes the development of a three-dimensional database of aircraft fuel burn and emissions (fuel burned, NOx, CO, and hydrocarbons) from scheduled commercial aircraft for each month of 1992. The seasonal variation in aircraft emissions was calculated for selected regions (global, North America, Europe, North Atlantic, and North Pacific). A series of parametric calculations were done to quantify the possible errors introduced from making approximations necessary to calculate the global emission inventory. The effects of wind, temperature, load factor, payload, and fuel tankering on fuel burn were evaluated to identify how they might affect the accuracy of aircraft emission inventories. These emissions inventories are available for use by atmospheric scientists conducting the Atmospheric Effects of Aviation Project (AEAP) modeling studies. Fuel burned and emissions of nitrogen oxides (NOx as N02), carbon monoxide, and hydrocarbons have been calculated on a 1 degree latitude x 1 degree longitude x 1 kilometer altitude grid and delivered to NASA as electronic files.

Baughcum, Steven L.↗
NASA NTRS2001

Scheduled Civil Aircraft Emission Inventories for 1999: Database Development and Analysis

This report describes the development of a three-dimensional database of aircraft fuel burn and emissions (NO(x), CO, and hydrocarbons) for the scheduled commercial aircraft fleet for each month of 1999. Global totals of emissions and fuel burn for 1999 are compared to global totals from 1992 and 2015 databases. 1999 fuel burn, departure and distance totals for selected airlines are compared to data reported on DOT Form 41 to evaluate the accuracy of the calculations. DOT Form T-100 data were used to determine typical payloads for freighter aircraft and this information was used to model freighter aircraft more accurately by using more realistic payloads. Differences in the calculation methodology used to create the 1999 fuel burn and emissions database from the methodology used in previous work are described and evaluated.

Sutkus, Donald J., Jr.↗
NASA NTRS1982

Development of technologies for welding interconnects to fifty-micron thick silicon solar cells

A program was conducted to develop technologies for welding interconnects to 50 microns thick, 2 by 2 cm solar cells. The cells were characterized with respect to electrical performance, cell thickness, silver contact thickness, contact waviness, bowing, and fracture strength. Weld schedules were independently developed for each of the three cell types and were coincidentally identical. Thermal shock tests (100 cycles from 100 C to -180 C) were performed on 16 cell coupons for each cell type without any weld joint failures or electrical degradation. Three 48 cell modules (one for each cell type) were assembled with 50 microns thick cells, frosted fused silica covers, silver clad Invar interconnectors, and Kapton substrates.

Patterson, R. E.↗
NASA NTRS1996

Explicit and Implicit Resources: A Simplified Approach to User Requirements Modeling

The International Space Station (ISS) program is dependent on the concept of distributed planning, which places a large responsibility in the hands of the science users. The users assume the responsibility in submitting the operations scheduling requirements in the format required by the scheduling software. The concept of explicit and implicit resources, developed to facilitate the operations scheduling of ISS by non-scheduling experts, is presented. The proposed concepts are defined and examples of scheduling requirements, implemented using explicit and implicit resources, are described together with the requirements modeling and scheduler formatting functions. The software developed to support the implicit and explicit resources concept is discussed.

Hagopian, Jeff↗
NASA NTRS2006

Temporal Investment Strategy to Enable JPL Future Space Missions

The Jet Propulsion Laboratory (JPL) formulates and conducts deep space missions for NASA (the National Aeronautics and Space Administration). The Chief Technologist of JPL has the responsibility for strategic planning of the laboratory's advanced technology program to assure that the required technological capabilities to enable future JPL deep space missions are ready as needed; as such he is responsible for the development of a Strategic Plan. As part of the planning effort, he has supported the development of a structured approach to technology prioritization based upon the work of the START (Strategic Assessment of Risk and Technology) team. A major innovation reported here is the addition of a temporal model that supports scheduling of technology development as a function of time. The JPL Strategic Technology Plan divides the required capabilities into 13 strategic themes. The results reported here represent the analysis of an initial seven.

investment strategy↗