SEARCH · Engineering Papers

Results for “system planning”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS2002

Methods and apparatus for graphical display and editing of flight plans

Systems and methods are provided for an integrated graphical user interface which facilitates the display and editing of aircraft flight-plan data. A user (e.g., a pilot) located within the aircraft provides input to a processor through a cursor control device and receives visual feedback via a display produced by a monitor. The display includes various graphical elements associated with the lateral position, vertical position, flight-plan and/or other indicia of the aircraft's operational state as determined from avionics data and/or various data sources. Through use of the cursor control device, the user may modify the flight-plan and/or other such indicia graphically in accordance with feedback provided by the display. In one embodiment, the display includes a lateral view, a vertical profile view, and a hot-map view configured to simplify the display and editing of the aircraft's flight-plan data.

Gibbs, Michael J.↗

NASA NTRS1993

Test, Control and Monitor System maintenance plan

The maintenance requirements for Test, Control, and Monitor System (TCMS) and the method for satisfying these requirements prior to First Need Date (FND) of the last TCMS set are described. The method for satisfying maintenance requirements following FND of the last TCMS set will be addressed by a revision to this plan. This maintenance plan serves as the basic planning document for maintenance of this equipment by the NASA Payloads Directorate (CM) and the Payload Ground Operations Contractor (PGOC) at KSC. The terms TCMS Operations and Maintenance (O&M), Payloads Logistics, TCMS Sustaining Engineering, Payload Communications, and Integrated Network Services refer to the appropriate NASA and PGOC organization. For the duration of their contract, the Core Electronic Contractor (CEC) will provide a Set Support Team (SST). One of the primary purposes of this team is to help NASA and PGOC operate and maintain TCMS. It is assumed that SST is an integral part of TCMS O&M. The purpose of this plan is to describe the maintenance concept for TCMS hardware and system software in order to facilitate activation, transition planning, and continuing operation. When software maintenance is mentioned in this plan, it refers to maintenance of TCMS system software.

Buehler, David P.↗

NASA NTRS1972

Guidance system operations plan for manned CM earth orbital missions using program SKYLARK 1. Section 4: Operational modes

The operational modes for the guidance system operations plan for Program SKYLARK 1 are presented. The procedures control the guidance and navigation system interfaces with the flight crew and the mission control center. The guidance operational concept is designed to comprise a set of manually initiated programs and functions which may be arranged by the flight crew to implement a large class of flight plans. This concept will permit both a late flight plan definition and a capability for real time flight plan changes.

Dunbar, J. C.↗

NASA NTRS1982

Speckle spectroscopy; an application for the multi-anode microchannel array detector system

Plans to combine the High Angular Resolution Imager/Spectrometer on the 4-meter Mayall telescope at the Kitt Peak National Observatory and the (256 x 1024)-pixel Multi-Anode Microchannel Array detector system to produce a unique instrument for speckle spectroscopy are described. The pulse-counting detector system will provide distortion-free imaging and will time tag each spatially-resolved photon event with an accuracy of 100 ns. The Imager/Spectrometer will provide a spatial resolution of 0.07 arcsec orthogonal to the plane of dispersion and 0.18 arcsec in the plane of dispersion.

Butcher, H. R.↗

NASA NTRS2021

Future SAR Imaging Systems: Goals, Plans, Challenges and Opportunities

Synthetic Aperture Radar (SAR) Earth observation data are becoming increasingly ubiquitous as new spaceborne systems become operational and their data are made available to scientists and applications users. The characteristic of active sensors like SAR to be able to observe Earth independent of weather or solar illumination, coupled with regular data acquisition, fosters reliability and encourages the investment in algorithm and product development toward a beneficial result. As SAR systems typically contain proprietary or nationally important technologies, civilian SAR systems are typically developed with a national focus, or in the case of the European Union, with the Union’s focus. As a result, when viewed from a global perspective, SAR programs can be generally viewed as independent developments, each with their own requirements, schedules, development approaches, and data policies. At the same time, these systems can be expensive, and particularly in an era of increasingly open data policies, coordination of programs could reduce redundancy in observations, increase sampling density and measurement diversity, and improve dependability of data streams in the long term. Since 2018, agency representatives from NASA, ESA, DLR, JAXA, ISRO, ASI, and CONAE have been evaluating the possibilities for programmatic and technical coordination of future SAR systems, data sharing, and scientific exploitation. In this paper, we describe the work in discovering trends and possibilities associated with flight systems, by evaluating current and future plans for SAR systems around the world, and identifying opportunities for coordination.

Zink, Manfred↗

NASA NTRS1968

LH 2 Tank Insulation Outgassing System Test Plan

Test plan for LH2 insulation outgassing system

Mc Farlane, J. R.↗

NASA NTRS1984

IBM PC/IX operating system evaluation plan

An evaluation plan for the IBM PC/IX Operating System designed for IBM PC/XT computers is discussed. The evaluation plan covers the areas of performance measurement and evaluation, software facilities available, man-machine interface considerations, networking, and the suitability of PC/IX as a development environment within the University of Southwestern Louisiana NASA PC Research and Development project. In order to compare and evaluate the PC/IX system, comparisons with other available UNIX-based systems are also included.

Dominick, Wayne D.↗

NASA NTRS2006

Advances in Distributed Operations and Mission Activity Planning for Mars Surface Exploration

A centralized mission activity planning system for any long-term mission, such as the Mars Exploration Rover Mission (MER), is completely infeasible due to budget and geographic constraints. A distributed operations system is key to addressing these constraints; therefore, future system and software engineers must focus on the problem of how to provide a secure, reliable, and distributed mission activity planning system. We will explain how Maestro, the next generation mission activity planning system, with its heavy emphasis on portability and distributed operations has been able to meet these design challenges. MER has been an excellent proving ground for Maestro's new approach to distributed operations. The backend that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

Mars Exploration Rover (MER)↗

NASA NTRS1999

Planning for New Primary Airports in the United States: A Survey of Metropolitan Planning Organizations

Airport congestion at primary airports in major metropolitan areas was analyzed in a report prepared by the Transportation Research Board (TRB) in 1990. Taking the top twenty-three most congested airports from this study, a questionnaire was prepared and sent to the metropolitan planning organizations (MPOS) for twenty of the twenty-three metropolitan areas represented in the TRB study. The questionnaire focused on the role of the MPOs in planning for new primary airports in the United States, including questions about the status of the most recent MPO airport system plan, whether or not the latest plan recommends a new primary airport, and whether or not any other entities in the MPO areas are recommending new primary airports. The results indicated that 44.4 percent of the eighteen respondent MPOs have airport system plans that are five years old or older. Also, only two of the respondent MPOs have recommended a new primary airport in their latest regional airport system plan and only one of these two is a common recommendation in the Federal Aviation Administration's National Plan of Integrated Airport System.

NewMeyer, David A.↗

NASA NTRS1999

Planning for New Primary Airports in the United States: A Survey of Metropolitan Planning Organizations

Airport congestion at primary airports in major metropolitan areas was analyzed in a report prepared by the Transportation Research Board (TRB) in 1990. Taking the top twenty-three most congested airports from this study, a questionnaire was prepared and sent to the metropolitan planning organizations (MPOs) for twenty of the twenty-three metropolitan areas represented in the TRB study, The questionnaire focused on the role of the MPOs in planning for new primary airports in the United States, including questions about the status of the most recent MPO airport system plan, whether or not the latest plan recommends a new primary airport, and whether or not any other entities in the MPO areas are recommending new primary airports. The results indicated that 44.4 percent of the eighteen respondent MPOs have airport system plans that are five years old or older. Also, only two of the respondent MPOs have recommended a new primary airport in their latest regional airport system plan and only one of these two is a common recommendation in the Federal Aviation Administration's National Plan of Integrated Airport System.

NewMyer, David A.↗

NASA NTRS2006

Advances in distributed operations and mission activity planning for Mars surface exploration

Shams, Khawaja↗

NASA NTRS1971

Guidance system operations plan for manned cm earth orbital and lunar missions using program Colossus 3. Section 2: Data links

The data links for use with the guidance system operations plan for manned command module earth orbital and lunar missions using program Colossus 3 are presented. The subjects discussed are: (1) digital uplink to CMC, (2) command module contiguous block update, (3) CMC retrofire external data update, (4) CMC digital downlink, and (5) CMC entry update.

Hamilton, M. H.↗

NASA NTRS1996

Re-Engineering JPL's Mission Planning Ground System Architecture for Cost Efficient Operations in the 21st Century

Work carried out to re-engineer the mission analysis segment of JPL's mission planning ground system architecture is reported on. The aim is to transform the existing software tools, originally developed for specific missions on different support environments, into an integrated, general purpose, multi-mission tool set. The issues considered are: the development of a partnership between software developers and users; the definition of key mission analysis functions; the development of a consensus based architecture; the move towards evolutionary change instead of revolutionary replacement; software reusability, and the minimization of future maintenance costs. The current status and aims of new developments are discussed and specific examples of cost savings and improved productivity are presented.

Fordyce, Jess↗

NASA NTRS2012

A Comparison of Declarative and Hybrid Declarative-Procedural Models for Rover Operations

The MAPGEN [2] (Mixed-initiative Activity Plan GENerator) planning system is a great example of a hybrid procedural/declarative system where the advantages of each are leveraged to produce an effective planner/scheduler for Mars Exploration Rover tactical planning. We explore the adaptation of the same domain to an entirely declarative planning system (ASPEN [4] Activity Scheduling and Planning ENvironment), and demonstrate that, with some translation, much of the procedural knowledge encoding is amenable to a declarative knowledge encoding.

declarative domain representations↗

NASA NTRS1984

Guidance and navigation programs and plans

System technology concepts for all weather helicopter operations in both remote and high density areas were examined. The SH-36 was used to support the remote area investigations. The primary emphasis was on the development of advanced navigation concepts to allow rotorcraft to land in remote areas where there may not be a ground based navigational aid. The focus was on the used airborne weather radar, the use of high resolution radar and satellite based navigation concepts. The high density work was conducted using the UH-1H system that allows alternate guidance and navigation algorithms to be tested in flight.

Denery, D. G.↗

NASA NTRS2013

Translating MAPGEN to ASPEN for MER

This software translates MAPGEN (Europa and APGEN) domains to ASPEN, and the resulting domain can be used to perform planning for the Mars Exploration Rover (MER). In other words, this is a conversion of two distinct planning languages (both declarative and procedural) to a third (declarative) planning language in order to solve the problem of faithful translation from mixed-domain representations into the ASPEN Modeling Language. The MAPGEN planning system is an example of a hybrid procedural/declarative system where the advantages of each are leveraged to produce an effective planner/scheduler for MER tactical planning. The adaptation of the planning system (ASPEN) was investigated, and, with some translation, much of the procedural knowledge encoding is amenable to declarative knowledge encoding. The approach was to compose translators from the core languages used for adapting MAGPEN, which consists of Europa and APGEN. Europa is a constraint- based planner/scheduler where domains are encoded using a declarative model. APGEN is also constraint-based, in that it tracks constraints on resources and states and other variables. Domains are encoded in both constraints and code snippets that execute according to a forward sweep through the plan. Europa and APGEN communicate to each other using proxy activities in APGEN that represent constraints and/or tokens in Europa. The composition of a translator from Europa to ASPEN was fairly straightforward, as ASPEN is also a declarative planning system, and the specific uses of Europa for the MER domain matched ASPEN s native encoding fairly closely. On the other hand, translating from APGEN to ASPEN was considerably more involved. On the surface, the types of activities and resources one encodes in APGEN appear to match oneto- one to the activities, state variables, and resources in ASPEN. But, when looking into the definitions of how resources are profiled and activities are expanded, one sees code snippets that access various information available during planning for the moment in time being planned to decide at the time what the appropriate profile or expansion is. APGEN is actually a forward (in time) sweeping discrete event simulator, where the model is composed of code snippets that are artfully interleaved by the engine to produce a plan/schedule. To solve this problem, representative code is simulated as a declarative series of task expansions. Predominantly, three types of procedural models were translated: loops, if statements, and code blocks. Loops and if statements were handled using controlled task expansion, and code blocks were handled using constraint networks that maintained the generation of results based on what the order of execution would be for a procedural representation. One advantage with respect to performance for MAPGEN is the use of APGEN s GUI. This GUI is written in C++ and Motif, and performs very well for large plans.

Rabideau, Gregg R.↗

NASA NTRS1989

Strategies for automatic planning: A collection of ideas

The main goal of the Jet Propulsion Laboratory (JPL) is to obtain science return from interplanetary probes. The uplink process is concerned with communicating commands to a spacecraft in order to achieve science objectives. There are two main parts to the development of the command file which is sent to a spacecraft. First, the activity planning process integrates the science requests for utilization of spacecraft time into a feasible sequence. Then the command generation process converts the sequence into a set of commands. The development of a feasible sequence plan is an expensive and labor intensive process requiring many months of effort. In order to save time and manpower in the uplink process, automation of parts of this process is desired. There is an ongoing effort to develop automatic planning systems. This has met with some success, but has also been informative about the nature of this effort. It is now clear that innovative techniques and state-of-the-art technology will be required in order to produce a system which can provide automatic sequence planning. As part of this effort to develop automatic planning systems, a survey of the literature, looking for known techniques which may be applicable to our work was conducted. Descriptions of and references for these methods are given, together with ideas for applying the techniques to automatic planning.

Collins, Carol↗

NASA NTRS1981

The 30/20 GHz flight experiment system, phase 2. Volume 4: Experiment system development plan

The development plan for the 30/20 GHz flight experiment system is presented. A master program schedule with detailed development plans for each subsystem is planned with careful attention given to how technology items to ensure a minimal risk. The work breakdown structure shows the organization of the program management with detailed task definitions. The ROM costs based on the development plan are also given.

Bronstein, L.↗