Search NASA⌕ Search

SEARCH · Search NASA

Results for “process and scheduling”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Use of Dynamic Models and Operational Architecture to Solve Complex Navy Challenges

The United States Navy established 8 Maritime Operations Centers (MOC) to enhance the command and control of forces at the operational level of warfare. Each MOC is a headquarters manned by qualified joint operational-level staffs, and enabled by globally interoperable C41 systems. To assess and refine MOC staffing, equipment, and schedules, a dynamic software model was developed. The model leverages pre-existing operational process architecture, joint military task lists that define activities and their precedence relations, as well as Navy documents that specify manning and roles per activity. The software model serves as a "computational wind-tunnel" in which to test a MOC on a mission, and to refine its structure, staffing, processes, and schedules. More generally, the model supports resource allocation decisions concerning Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) at MOCs around the world. A rapid prototype effort efficiently produced this software in less than five months, using an integrated process team consisting of MOC military and civilian staff, modeling experts, and software developers. The work reported here was conducted for Commander, United States Fleet Forces Command in Norfolk, Virginia, code N5-0LW (Operational Level of War) that facilitates the identification, consolidation, and prioritization of MOC capabilities requirements, and implementation and delivery of MOC solutions.

Grande, Darby↗
NASA NTRS2014

The Cassini Solstice Mission: Streamlining Operations by Sequencing with PIEs

The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks, with 6 overlapping processes.

Vandermey, Nancy↗
NASA NTRS2000

Putting ROSE to Work: A Proposed Application of a Request-Oriented Scheduling Engine for Space Station Operations

Scheduling engines are found at the core of software systems that plan and schedule activities and resources. A Request-Oriented Scheduling Engine (ROSE) is one that processes a single request (adding a task to a timeline) and then waits for another request. For the International Space Station, a robust ROSE-based system would support multiple, simultaneous users, each formulating requests (defining scheduling requirements), submitting these requests via the internet to a single scheduling engine operating on a single timeline, and immediately viewing the resulting timeline. ROSE is significantly different from the engine currently used to schedule Space Station operations. The current engine supports essentially one person at a time, with a pre-defined set of requirements from many payloads, working in either a "batch" scheduling mode or an interactive/manual scheduling mode. A planning and scheduling process that takes advantage of the features of ROSE could produce greater customer satisfaction at reduced cost and reduced flow time. This paper describes a possible ROSE-based scheduling process and identifies the additional software component required to support it. Resulting changes to the management and control of the process are also discussed.

Jaap, John↗
NASA NTRSDate not supplied

Enterprise Mission Integration for Artemis Lunar Missions

Mission integration is an iterative process by which a specific mission is formulated, refined, planned, and executed within the established vehicle(s), architecture, and ground systems design. Mission integration includes the people, vehicle(s) and ground hardware/software, products, processes, analyses, schedules, facilities, Certification of Flight Readiness, etc. The Artemis Mission Integration Task Team (MITT) developed a series of products and processes to support the complex mission integration across various Programs within the Artemis Mission Campaign (Orion, Space Launch Systems, Exploration Ground Systems, Gateway, Human Landing System, and Extravehicular Activity and Human Surface Mobility). The Moon to Mars (M2M) Program is referred to as ‘the enterprise’ as it includes both the M2M organization and the Programs supporting the Artemis Mission Campaign. Artemis Mission Integration has five phases: mission capability, mission definition, mission preparation, mission execution, and post-mission assessment. This paper focuses on one of the enterprise-level mission checkpoints as a kick-off to the Mission Preparation phase, the Mission Integration Review (MIR), which occurs 18-24 months prior to launch. The MIR helps to confirm the defined mission technical baseline is within the existing analyzed design envelope. Details are provided on the identification of dependencies, issues, or gaps for mission-specific objectives and requirements, as well as the definition of the analysis, training, mission execution products, facilities, and detailed supporting operations requirements. The MIR was held for both Artemis I and II and this paper aims to share with the aerospace community its value as we prepare for upcoming Artemis Missions.

Mary Anne Plaza↗
NASA NTRSDate not supplied

Exploring Self-Scheduling Strategies and Heuristics in Novice Schedulers

Missions beyond low Earth orbit will require crews to act with greater autonomy. Increasing communication delays will require crews to take on tasks currently supported by Mission Control, including the involved process of scheduling and rescheduling their own complex spaceflight timelines to fit a variety of restrictions and constraints. Astronauts, unlike Mission Control, are not expert planners, however, and determining simple strategies and heuristics that enable them to schedule successfully can increase the range of problems they can solve successfully. In two human-in-the-loop scheduling experiments, we analyzed 1) common strategies among novice schedules, and 2) the development of self-scheduling heuristics. We find that, even when participants are instructed to follow a given strategy, they rapidly develop their own self-scheduling heuristics as they learn to successfully complete the scheduling task. Participants conducting naturally learn to schedule activities with the most constraints first, while participants vary in heuristics in the rescheduling task.

self-scheduling↗
NASA NTRSDate not supplied

Exploring Self-Scheduling Strategies and Heuristics in Novice Schedulers

Missions beyond low Earth orbit will require crews to act with greater autonomy. Increasing communication delays will require crews to take on tasks currently supported by Mission Control, including the involved process of scheduling and rescheduling their own complex spaceflight timelines to fit a variety of restrictions and constraints. Unlike Mission Control, astronauts are not expert planners, and determining strategies and heuristics that enable crews to schedule successfully may increase the range of problems they can solve. In two human-in-the-loop scheduling experiments, we analyzed 1) common strategies among novice schedulers and 2) the development of self-scheduling heuristics. We find that, even when participants are instructed to follow a given strategy, they rapidly develop their own self-scheduling heuristics as they learn to successfully complete the scheduling task. While scheduling, participants naturally learn to arrange activities with the most constraints first, whereas while rescheduling, they display greater variability in their heuristics.

self-scheduling↗
NASA NTRS1989

A heuristic approach to incremental and reactive scheduling

An heuristic approach to incremental and reactive scheduling is described. Incremental scheduling is the process of modifying an existing schedule if the initial schedule does not meet its stated initial goals. Reactive scheduling occurs in near real-time in response to changes in available resources or the occurrence of targets of opportunity. Only minor changes are made during both incremental and reactive scheduling because a goal of re-scheduling procedures is to minimally impact the schedule. The described heuristic search techniques, which are employed by the Request Oriented Scheduling Engine (ROSE), a prototype generic scheduler, efficiently approximate the cost of reaching a goal from a given state and effective mechanisms for controlling search.

Odubiyi, Jide B.↗
NASA NTRS2009

Multi-Mission Automated Task Invocation Subsystem

Multi-Mission Automated Task Invocation Subsystem (MATIS) is software that establishes a distributed data-processing framework for automated generation of instrument data products from a spacecraft mission. Each mission may set up a set of MATIS servers for processing its data products. MATIS embodies lessons learned in experience with prior instrument- data-product-generation software. MATIS is an event-driven workflow manager that interprets project-specific, user-defined rules for managing processes. It executes programs in response to specific events under specific conditions according to the rules. Because requirements of different missions are too diverse to be satisfied by one program, MATIS accommodates plug-in programs. MATIS is flexible in that users can control such processing parameters as how many pipelines to run and on which computing machines to run them. MATIS has a fail-safe capability. At each step, MATIS captures and retains pertinent information needed to complete the step and start the next step. In the event of a restart, this information is retrieved so that processing can be resumed appropriately. At this writing, it is planned to develop a graphical user interface (GUI) for monitoring and controlling a product generation engine in MATIS. The GUI would enable users to schedule multiple processes and manage the data products produced in the processes. Although MATIS was initially designed for instrument data product generation,

Cheng, Cecilia S.↗
NASA NTRS2014

Technology Estimating 2: A Process to Determine the Cost and Schedule of Space Technology Research and Development

As a leader in space technology research and development, NASA is continuing in the development of the Technology Estimating process, initiated in 2012, for estimating the cost and schedule of low maturity technology research and development, where the Technology Readiness Level is less than TRL 6. NASA' s Technology Roadmap areas consist of 14 technology areas. The focus of this continuing Technology Estimating effort included four Technology Areas (TA): TA3 Space Power and Energy Storage, TA4 Robotics, TA8 Instruments, and TA12 Materials, to confine the research to the most abundant data pool. This research report continues the development of technology estimating efforts completed during 2013-2014, and addresses the refinement of parameters selected and recommended for use in the estimating process, where the parameters developed are applicable to Cost Estimating Relationships (CERs) used in the parametric cost estimating analysis. This research addresses the architecture for administration of the Technology Cost and Scheduling Estimating tool, the parameters suggested for computer software adjunct to any technology area, and the identification of gaps in the Technology Estimating process.

Cole, Stuart K.↗
NASA NTRS1983

Launch processing for Spacelab 1

The final integration of Spacelab payloads with the Shuttle is described. Attention is given to launch processing planning, schedules, quality control, and problem reports and configuration maintenance. Also covered are the integration and checkout of individual and combined experiments, mounting the end cones, attachment of the transfer tunnel, and inclusion of an extra experiments pallet. The entire Spacelab module was subjected to a full systems simulation before deliverance to the Orbiter bay. Modular parts that were transferred from building-to-building were placed in sealed containers filled with a purged atmosphere during transport.

Mcbrayer, R. O.↗
NASA NTRS1988

The influence of grain size and composition on 1000 to 1400 K slow plastic flow properties of NiAl

The compressive slow plastic flow behavior of several B2 crystal structure NiAl intermetallics has been studied in air between 1000 and 1400 K. Small grain-sized Ni-48.25 at. pct Al (of about 10 microns) was found to be stronger than the previously studied 17 microns diameter material. While grain refinement improved the strength at all test temperatures, the exact mechanism is not clear. Experiments at lower temperature revealed that composition as well as grain size can be an important factor, since Ni-49.2Al was weaker than Ni-48.25Al. Pronounced yield points were found during slow strain-rate testing at 1000 K; however, continued deformation appears to take place by the same mechanism(s) as found at high temperatures. Small changes in thermomechanical processing (TMP) schedules to fabricate Ni-49.2Al indicated that basic deformation characteristics (stress exponent and activation energy) are not affected; however, the preexponential term could be modified if TMP alters the grain structure.

Whittenberger, J. Daniel↗
NASA NTRS1989

CHIMERA II - A real-time multiprocessing environment for sensor-based robot control

A multiprocessing environment for a wide variety of sensor-based robot system, providing the flexibility, performance, and UNIX-compatible interface needed for fast development of real-time code is addressed. The requirements imposed on the design of a programming environment for sensor-based robotic control is outlined. The details of the current hardware configuration are presented, along with the details of the CHIMERA II software. Emphasis is placed on the kernel, low-level interboard communication, user interface, extended file system, user-definable and dynamically selectable real-time schedulers, remote process synchronization, and generalized interprocess communication. A possible implementation of a hierarchical control model, the NASA/NBS standard reference model for telerobot control system is demonstrated.

Stewart, David B.↗
NASA NTRS1997

Insoluble Coatings for Stirling Engine Heat Pipe Condenser Surfaces

The principal objective of this Phase 2 SBIR program was to develop and demonstrate a practically insoluble coating for nickel-based superalloys for Stirling engine heat pipe applications. Specific technical objectives of the program were: (1) Determine the solubility corrosion rates for Nickel 200, Inconel 718, and Udimet 72OLI in a simulated Stirling engine heat pipe environment, (2) Develop coating processes and techniques for capillary groove and screen wick structures, (3) Evaluate the durability and solubility corrosion rates for capillary groove and screen wick structures coated with an insoluble coating in cylindrical heat pipes operating under Stirling engine conditions, and (4) Design and fabricate a coated full-scale, partial segment of the current Stirling engine heat pipe for the Stirling Space Power Convertor program. The work effort successfully demonstrated a two-step nickel aluminide coating process for groove wick structures and interior wall surfaces in contact with liquid metals; demonstrated a one-step nickel aluminide coating process for nickel screen wick structures; and developed and demonstrated a two-step aluminum-to-nickel aluminide coating process for nickel screen wick structures. In addition, the full-scale, partial segment was fabricated and the interior surfaces and wick structures were coated. The heat pipe was charged with sodium, processed, and scheduled to be life tested for up to ten years as a Phase 3 effort.

Dussinger, Peter M.↗
NASA NTRS1998

Data Understanding Applied to Optimization

The goal of this research is to explore and develop software for supporting visualization and data analysis of search and optimization. Optimization is an ever-present problem in science. The theory of NP-completeness implies that the problems can only be resolved by increasingly smarter problem specific knowledge, possibly for use in some general purpose algorithms. Visualization and data analysis offers an opportunity to accelerate our understanding of key computational bottlenecks in optimization and to automatically tune aspects of the computation for specific problems. We will prototype systems to demonstrate how data understanding can be successfully applied to problems characteristic of NASA's key science optimization tasks, such as central tasks for parallel processing, spacecraft scheduling, and data transmission from a remote satellite.

Buntine, Wray↗
NASA NTRS2006

Three Years of Global Positioning System Experience on International Space Station

The International Space Station global positioning system (GPS) receiver was activated in April 2002. Since that time, numerous software anomalies surfaced that had to be worked around. Some of the software problems required waivers, such as the time function, while others required extensive operator intervention, such as numerous power cycles. Eventually enough anomalies surfaced that the three pieces of code included in the GPS unit have been re-written and the GPS units upgraded. The technical aspects of the problems are discussed, as well as the underlying causes that led to the delivery of a product that has had so many problems. The technical aspects of the problems included physical phenomena that were not well understood, such as the affect that the ionosphere would have on the GPS measurements. The underlying causes were traced to inappropriate use of legacy software, changing requirements, inadequate software processes, unrealistic schedules, incorrect contract type, and unclear ownership responsibilities..

Gomez, Susan↗
NASA NTRS2005

Three Years of Global Positioning System Experience on International Space Station

The International Space Station global positioning systems (GPS) receiver was activated in April 2002. Since that time, numerous software anomalies surfaced that had to be worked around. Some of the software problems required waivers, such as the time function, while others required extensive operator intervention, such as numerous power cycles. Eventually, enough anomalies surfaced that the three pieces of code included in the GPS unit have been re-written and the GPS units were upgraded. The technical aspects of the problems are discussed, as well as the underlying causes that led to the delivery of a product that has had numerous problems. The technical aspects of the problems included physical phenomena that were not well understood, such as the affect that the ionosphere would have on the GPS measurements. The underlying causes were traced to inappropriate use of legacy software, changing requirements, inadequate software processes, unrealistic schedules, incorrect contract type, and unclear ownership responsibilities.

Gomez, Susan↗