Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “integrated planning 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

Integration of safety engineering into a cost optimized development program.

A six-segment management model is presented, each segment of which represents a major area in a new product development program. The first segment of the model covers integration of specialist engineers into 'systems requirement definition' or the system engineering documentation process. The second covers preparation of five basic types of 'development program plans.' The third segment covers integration of system requirements, scheduling, and funding of specialist engineering activities into 'work breakdown structures,' 'cost accounts,' and 'work packages.' The fourth covers 'requirement communication' by line organizations. The fifth covers 'performance measurement' based on work package data. The sixth covers 'baseline requirements achievement tracking.'

Ball, L. W.↗

Earned Value Management (EVM): Reference Guide for Project-Control Account Managers

The purpose of this guide is intended to be a quick reference for a Project-Control Account Manager (P CAM) or technical manager empowered with a project’s cost, schedule, and technical responsibilities of a control account(s) when Earned Value Management (EVM) is required. The overall objective is to support the P CAM in performing their responsibilities as they relate to EVM. In addition, the reference guide describes at a summary level how the scope, schedule, and budget of a project integrate for optimal planning and control of prime contracts and in-house projects.

Control Account Manager↗

Automating Mid- and Long-Range Scheduling for NASA's Deep Space Network

NASA has recently deployed a new mid-range scheduling system for the antennas of the Deep Space Network (DSN), called Service Scheduling Software, or S(sup 3). This system is architected as a modern web application containing a central scheduling database integrated with a collaborative environment, exploiting the same technologies as social web applications but applied to a space operations context. This is highly relevant to the DSN domain since the network schedule of operations is developed in a peer-to-peer negotiation process among all users who utilize the DSN (representing 37 projects including international partners and ground-based science and calibration users). The initial implementation of S(sup 3) is complete and the system has been operational since July 2011. S(sup 3) has been used for negotiating schedules since April 2011, including the baseline schedules for three launching missions in late 2011. S(sup 3) supports a distributed scheduling model, in which changes can potentially be made by multiple users based on multiple schedule "workspaces" or versions of the schedule. This has led to several challenges in the design of the scheduling database, and of a change proposal workflow that allows users to concur with or to reject proposed schedule changes, and then counter-propose with alternative or additional suggested changes. This paper describes some key aspects of the S(sup 3) system and lessons learned from its operational deployment to date, focusing on the challenges of multi-user collaborative scheduling in a practical and mission-critical setting. We will also describe the ongoing project to extend S(sup 3) to encompass long-range planning, downtime analysis, and forecasting, as the next step in developing a single integrated DSN scheduling tool suite to cover all time ranges.

scheduling↗

Using Flexible Execution, Replanning, and Model Parameter Updates to Address Environmental Uncertainty for a Planetary Lander

Planning in an unknown environment presents a number of challenges: incorrect world models, unpredictable variation in execution, and fixed depletable resources. Productivity in the face of these challenges requires an integrated approach to planning and execution that is capable of accomplishing goals, reacting to variation, and maximizing overall utility. We examine this problem in the context of a Europa Lander concept mission. We model the problem as a hierarchical task network, framing it as a utility maximization problem with a depletable energy resource. Then, we propose a planning and execution framework that responds to feedback using three techniques: flexible execution, periodic replanning, and online parameter estimation and re-goaling. We demonstrate the efficacy of each of these techniques through simulation of a Europa Lander mission, showing higher utility achievement compared to simpler approaches, when presented with variation in energy consumption. We demonstrate that an approach to scheduling and execution that is grounded in decision theory and integrated planning and execution will be an enabling technology for future tightly-constrained planetary surface missions.

Chien, Steve↗

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗

Scheduling with genetic algorithms

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.

Fennel, Theron R.↗

Shuttle free-flying teleoperator system experiment definition. Volume 3: program development requirements

The planning data are presented for subsequent phases of free-flying teleoperator program (FFTO) and includes costs, schedules and supporting research and technology activities required to implement the free-flying teleoperator system and associated flight equipment. The purpose of the data presented is to provide NASA with the information needed to continue development of the FFTO and integrate it into the space shuttle program. The planning data describes three major program phases consisting of activities and events scheduled to effect integrated design, development, fabrication and operation of an FFTO system. Phase A, Concept Generation, represents a study effort directed toward generating and evaluating a number of feasible FFTO experiment system concepts. Phase B, Definition, will include preliminary design and supporting analysis of the FFTO, the shuttle based equipment and ground support equipment. Phase C/D, Design, Development and Operations will include detail design of the operational FFTO, its integration into the space shuttle, hardware fabrication and testing, delivery of flight hardware and support of flight operations. Emphasis is placed on the planning for Phases A and B since these studies will be implemented early in the development cycle. Phase C/D planning is more general and subject to refinement during the definition phase.

Source record↗

Automating Mid- and Long-Range Scheduling for the NASA Deep Space Network

NASA has recently deployed a new mid-range scheduling system for the antennas of the Deep Space Network (DSN), called Service Scheduling Software, or S(sup 3). This system was designed and deployed as a modern web application containing a central scheduling database integrated with a collaborative environment, exploiting the same technologies as social web applications but applied to a space operations context. This is highly relevant to the DSN domain since the network schedule of operations is developed in a peer-to-peer negotiation process among all users of the DSN. These users represent not only NASA's deep space missions, but also international partners and ground-based science and calibration users. The initial implementation of S(sup 3) is complete and the system has been operational since July 2011. This paper describes some key aspects of the S(sup 3) system and on the challenges of modeling complex scheduling requirements and the ongoing extension of S(sup 3) to encompass long-range planning, downtime analysis, and forecasting, as the next step in developing a single integrated DSN scheduling tool suite to cover all time ranges.

Deep Space Network↗

The Ares I-1 Flight Test--Paving the Road for the Ares I Crew Launch Vehicle

In accordance with the U.S. Vision for Space Exploration and the nation's desire to again send humans to explore beyond Earth orbit, NASA has been tasked to send human beings to the moon, Mars, and beyond. It has been 30 years since the United States last designed and built a human-rated launch vehicle. NASA is now building the Ares I crew launch vehicle, which will loft the Orion crew exploration vehicle into orbit, and the Ares V cargo launch vehicle, which will launch the Lunar Surface Access Module and Earth departure stage to rendezvous Orion for missions to the moon. NASA has marshaled unique resources from the government and private sectors to perform the technically and programmatically complex work of delivering astronauts to orbit early next decade, followed by heavy cargo late next decade. Our experiences with Saturn and the Shuttle have taught us the value of adhering to sound systems engineering, such as the "test as you fly" principle, while applying aerospace best practices and lessons learned. If we are to fly humans safely aboard a launch vehicle, we must employ a variety of methodologies to reduce the technical, schedule, and cost risks inherent in the complex business of space transportation. During the Saturn development effort, NASA conducted multiple demonstration and verification flight tests to prove technology in its operating environment before relying upon it for human spaceflight. Less testing on the integrated Shuttle system did not reduce cost or schedule. NASA plans a progressive series of demonstration (ascent), verification (orbital), and mission flight tests to supplement ground research and high-altitude subsystem testing with real-world data, factoring the results of each test into the next one. In this way, sophisticated analytical models and tools, many of which were not available during Saturn and Shuttle, will be calibrated and we will gain confidence in their predictions, as we gain hands-on experience in operating the first of two new launch vehicle systems. The Ares I-1 flight test vehicle (FTV) will incorporate a mix of flight and mockup hardware, reflecting a configuration similar in mass, weight, and shape (outer mold line or OML) to the operational vehicle. It will be powered by a four-segment reusable solid rocket booster (RSRB), which is currently in Shuttle inventory, and will be modified to include a fifth, inert segment that makes it approximately the same size and weight as the five segment RSRB, which will be available for the second flight test in 2012. The Ares I-1 vehicle configuration is shown. Each test flight has specific objectives appropriate to the design analysis cycle in progress. The Ares I-1 demonstration test, slated for April 2009, gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack, understand how to control its roll during flight, and other characterize the severe stage separation environment that the upper stage will experience during future operational flights. NASA also will begin the process of modifying the launch infrastructure and fine-tuning ground and mission operational scenarios, as NASA transitions from the Shuttle to the Ares/Orion system.

Davis, Stephan R.↗

The SAX Italian scientific satellite. The on-board implemented automation as a support to the ground control capability

This paper presents the capabilities implemented in the SAX system for an efficient operations management during its in-flight mission. SAX is an Italian scientific satellite for x-ray astronomy whose major mission objectives impose quite tight constraints on the implementation of both the space and ground segment. The most relevant mission characteristics require an operative lifetime of two years, performing scientific observations both in contact and in noncontact periods, with a low equatorial orbit supported by one ground station, so that only a few minutes of communications are available each orbit. This operational scenario determines the need to have a satellite capable of performing the scheduled mission automatically and reacting autonomously to contingency situations. The implementation approach of the on-board operations management, through which the necessary automation and autonomy are achieved, follows a hierarchical structure. This has been achieved adopting a distributed avionic architecture. Nine different on-board computers, in fact, constitute the on-board data management system. Each of them performs the local control and monitors its own functions while the system level control is performed at a higher level by the data handling applications software. The SAX on-board architecture provides the ground operators with different options of intervention by three classes of telecommands. The management of the scientific operations will be scheduled by the operation control center via dedicated operating plans. The SAX satellite flight mode is presently being integrated at Alenia Spazio premises in Turin for a launch scheduled for the end of 1995. Once in orbit, the SAX satellite will be subject to intensive check-out activities in order to verify the required mission performances. An overview of the envisaged procedure and of the necessary on-ground activities is therefore depicted as well.

Martelli, Andrea↗

PLAN-IT - Scheduling assistant for solar system exploration

A frame-based expert scheduling system shell, PLAN-IT, is developed for spacecraft scheduling in the Request Integration Phase, using the Comet Rendezvous Asteroid Flyby (CRAF) mission as a development base. Basic, structured, and expert scheduling techniques are reviewed. Data elements such as activity representation and resource conflict representation are discussed. Resource constraints include minimum and maximum separation times between activities, percentage of time pointed at specific targets, and separation time between targeted intervals of a given activity. The different scheduling technique categories and the rationale for their selection are also considered.

Dias, William C.↗

PLAN-IT: Scheduling assistant for solar system exploration

A frame-based expert scheduling system shell, PLAN-IT, is developed for spacecraft scheduling in the Request Integration Phase, using the Comet Rendezvous Asteroid Flyby (CRAF) mission as a development base. Basic, structured, and expert scheduling techniques are reviewed. Data elements such as activity representation and resource conflict representation are discussed. Resource constraints include minimum and maximum separation times between activities, percentage of time pointed at specific targets, and separation time between targeted intervals of a given activity. The different scheduling technique categories and the rationale for their selection are also considered.

Dias, William C.↗

Development of a preprototype Advanced Extravehicular Mobility Unit (AEMU) regenerable life support subsystem - A progress report

Regenerable life support (RLS) technologies are being developed for use in the Advanced Extravehicle Mobility Unit (AEMU) aboard Space Station Freedom. This report describes the requirements that these RLS technologies must satisfy in the Space Station application and the significant features of the technologies now being evaluated. Who is developing the equipment and how the subsystems will be integrated are addressed. An overview of the planned test program schedule is given.

Allen, Norman C.↗

Onboard planning for geological investigations using a rover team

This paper describes an integrated system for coordinating multiple rover behavior with the overall goal of collecting planetary surface data. The Multi-Rover Integrated Science Understanding System (MISUS) combines techniques from planning and scheduling with machine learning to perform autonomous scientific exploration with cooperating rovers.

scheduling↗

Lost in Translation: the Case for Integrated Testing

The building of a spacecraft is complex and often involves multiple suppliers and companies that have their own designs and processes. Standards have been developed across the industries to reduce the chances for critical flight errors at the system level, but the spacecraft is still vulnerable to the introduction of critical errors during integration of these systems. Critical errors can occur at any time during the process and in many cases, human reliability analysis (HRA) identifies human error as a risk driver. Most programs have a test plan in place that is intended to catch these errors, but it is not uncommon for schedule and cost stress to result in less testing than initially planned. Therefore, integrated testing, or "testing as you fly," is essential as a final check on the design and assembly to catch any errors prior to the mission. This presentation will outline the unique benefits of integrated testing by catching critical flight errors that can otherwise go undetected, discuss HRA methods that are used to identify opportunities for human error, lessons learned and challenges over ownership of testing will be discussed.

Young, Aaron↗

Integration and Testing Challenges of Small, Multiple Satellite Missions: Experiences from the Space Technology 5 Project

The ST5 technology demonstration mission led by GSFC of NASA's New Millennium Program managed by JPL consisted of three micro satellites (approximately 30 kg each) deployed into orbit from the Pegasus XL launch vehicle. In order to meet the launch date schedule of ST5, a different approach was required rather than the standard I&T approach used for single, room-sized satellites. The three spacecraft were designed, integrated, and tested at NASA Goddard Space Flight Center. It was determined that there was insufficient time in the schedule to perform three spacecraft I&T activities in series using standard approaches. The solution was for spacecraft #1 to undergo integration and test first, followed by spacecraft #2 and #3 simultaneously. This simultaneous integration was successful for several reasons. Each spacecraft had a Lead Test Conductor who planned and coordinated their spacecraft through its integration and test activities. One team of engineers and technicians executed the integration of all three spacecraft, learning and gaining knowledge and efficiency as spacecraft #1 integration and testing progressed. They became acutely familiar with the hardware, operation and processes for I&T, thus had the experience and knowledge to safely execute I&T for spacecraft #2 and #3. The integration team was extremely versatile; each member could perform many different activities or work any spacecraft, when needed. ST5 was successfully integrated, tested and shipped to the launch site per the I&T schedule that was planned three years previously. The I&T campaign was completed with ST5's successful launch on March 22, 2006.

Sauerwein, Timothy A.↗

Methods to Reduce Communication Workload for UAM Operations

Implementation of Urban Air Mobility (UAM) operations, or air passenger transportation systems within densely populated metropolitan areas, seeks to mitigate increasing traffic congestion. However, the development and integration of UAM operations into the national airspace system comes with its own unique challenges, such as vehicle requirements, flight planning and scheduling, and coordination between UAM flights and air traffic controllers. In particular, verbal coordination will play an integral part in the determined success of UAM operations and its ability to meet projected high consumer demands. In order to meet demands and higher traffic volumes on UAM routes, verbal communication between the UAM pilot and controller must be streamlined to reduce the controller's workload while helping to maintain safety within a given airspace. One method of reducing verbal workload are Letters Of Agreement (LOAs) that outline responsibilities and procedures for operations in an airspace. These LOAs will specify the operations, procedures, and routes for UAM flights. The proposed study will examine the usability of two route formatting styles for LOAs; (i) Verbal route descriptions and (ii) Tower En Route Control (TECs) routes. Verbal route descriptions will include the route name and associated visual cues on the route. The TEC route versions will include relevant waypoints and charts outlining the route with waypoints marked. The study will be part of a UAM X1 human in the loop (HITL) simulation. Controller participants will handle traditional air traffic including moderate levels of UAM traffic on current and modified helicopter routes within the Dallas Fort-Worth area. Scenarios will be counterbalanced and repeated to test both route formatting versions. After each trial, participants will rate the usability of the LOA used in the previous trial via a subjective questionnaire. We expect that controllers will prefer the LOA with TEC routes due to simplicity and visual elements available.

aerospace human factors↗

Integrated resource scheduling in a distributed scheduling environment

The Space Station era presents a highly-complex multi-mission planning and scheduling environment exercised over a highly distributed system. In order to automate the scheduling process, customers require a mechanism for communicating their scheduling requirements to NASA. A request language that a remotely-located customer can use to specify his scheduling requirements to a NASA scheduler, thus automating the customer-scheduler interface, is described. This notation, Flexible Envelope-Request Notation (FERN), allows the user to completely specify his scheduling requirements such as resource usage, temporal constraints, and scheduling preferences and options. The FERN also contains mechanisms for representing schedule and resource availability information, which are used in the inter-scheduler inconsistency resolution process. Additionally, a scheduler is described that can accept these requests, process them, generate schedules, and return schedule and resource availability information to the requester. The Request-Oriented Scheduling Engine (ROSE) was designed to function either as an independent scheduler or as a scheduling element in a network of schedulers. When used in a network of schedulers, each ROSE communicates schedule and resource usage information to other schedulers via the FERN notation, enabling inconsistencies to be resolved between schedulers. Individual ROSE schedules are created by viewing the problem as a constraint satisfaction problem with a heuristically guided search strategy.

Zoch, David↗