Search NASA⌕ Search

SEARCH · Search NASA

Results for “Planning software”

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 37 records · Page 2

Space Station Mission Planning Study (MPS) development study. Volume 3: Software development plan

A software development plan is presented for the definition, design, and implementation of the Space Station (SS) Payload Mission Planning System (MPS). This plan is an evolving document and must be updated periodically as the SS design and operations concepts as well as the SS MPS concept evolve. The major segments of this plan are as follows: an overview of the SS MPS and a description of its required capabilities including the computer programs identified as configurable items with an explanation of the place and function of each within the system; an overview of the project plan and a detailed description of each development project activity breaking each into lower level tasks where applicable; identification of the resources required and recommendations for the manner in which they should be utilized including recommended schedules and estimated manpower requirements; and a description of the practices, standards, and techniques recommended for the SS MPS Software (SW) development.

Klus, W. L.↗

Lightweight Software Process Improvement Using Productivity and Sustainability Improvement Planning (PSIP)

Productivity and Sustainability Improvement Planning (PSIP) is a lightweight, iterative workflow that allows software development teams to identify development bottlenecks and track progress to overcome them. In this paper, we present an overview of PSIP and how it compares to other software process improvement (SPI) methodologies, and provide two case studies that describe how the use of PSIP led to successful improvements in team effectiveness and efficiency.

Heroux, Michael A.↗

Development and use of the computer software package for planning the 12 GHz broadcasting-satellite service at RARC '83

The 1983 Regional Administrative Radio Conference (RARC '83) had mainly the objective to draw up a plan of detailed frequency assignments and orbital positions for the 12 GHz broadcasting-satellite service (BSS) in ITU Region 2 (the Western Hemisphere) and associated feeder links (earth-to-space) in the 17 GHz band. It was found that for RARC '83 new planning methods and procedures would be needed. The new requirements made it necessary to develop a new generation of planning software. Attention is given to the development of the computer programs to be used at the conference, the package of computer programs, and the use of the computer programs.

Bowen, R. R.↗

An allotment planning concept and related computer software for planning the fixed satellite service at the 1988 space WARC

The authors describe a two-phase approach to allotment planning suitable for use in planning the fixed satellite service at the 1988 Space World Administrative radio Conference (ORB-88). The two phases are (1) the identification of predetermined geostationary arc segments common to groups of administrations and (2) the use of a synthesis program to identify example scenarios of space station placements. The planning approach is described in detail and is related to the objectives of the conference. Computer software has been developed to implement the concepts, and the logic and rationale for identifying predetermined arc segments is discussed. Example scenarios are evaluated to give guidance in the selection of the technical characteristics of space communications systems to be planned. The allotment planning concept described guarantees equitable access to the geostationary orbit, provides flexibility in implementation, and reduces the need for coordination among administrations.

Miller, Edward F.↗

An allotment planning concept and related computer software for planning the fixed satellite service at the 1988 space WARC

Described is a two-phase approach to allotment planning suitable for use in establishing the fixed satellite service at the 1988 Space World Administrative Radio Conference (ORB-88). The two phases are (1) the identification of predetermined geostationary arc segments common togroups of administrations, and (2) the use of a synthesis program to identify example scenarios of space station placements. The planning approach is described in detail and is related to the objectives of the confernece. Computer software has been developed to implement the concepts, and a complete discussion on the logic and rationale for identifying predetermined arc segments is given. Example scenarios are evaluated to give guidance in the selection of the technical characteristics of space communications systems to be planned. The allotment planning concept described guarantees in practice equitable access to the geostationary orbit, provides flexibility in implementation, and reduces the need for coordination among administrations.

Miller, Edward F.↗

Integrated System Planning: Emerging Software Requirements in the Power Industry

Power system planning software remains fragmented across organizational boundaries, with specialized tools for capacity expansion, production cost modeling, power flow, and dynamic analysis operating on incompatible data models and assumptions. This article argues that the fragmentation is not merely a technical problem but a predictable consequence of Conway's law: software architectures mirror the departmental structures within which they are developed. Regulatory milestones like Federal Energy Regulatory Commission (FERC) Order 888 formalized these divisions, but the roots trace back to the distinct engineering disciplines-mechanical, chemical, and electrical-that staffed generation and transmission planning departments in vertically integrated utilities. As the industry moves toward integrated system planning (ISP) that coordinates generation, transmission, and distribution investment decisions, the software ecosystem must evolve accordingly. We identify five categories of software requirements to enable this transition: coherent data inputs decoupled from individual applications, unified and extensible data schemas, modular component representations that support multiple abstraction levels, lifecycle management of planning datasets, and well-defined application programming interface (API) contracts that separate data exchange from algorithmic control. We examine how these requirements interact with three common workflow patterns-serial gate clearing, sequential multiapplication, and convergence oriented-and discuss the interface design principles each demands. We then outline a vision for platform-based planning architectures where specialized analytical services compose through standardized interfaces and where artificial intelligence (AI)/machine learning (ML) tools augment decision support within a disciplined software infrastructure. The practices proposed here offer a path from today's siloed tool collections toward collaborative planning ecosystems capable of handling the complexity of modern power system transformation.

24 POWER TRANSMISSION AND DISTRIBUTION↗

ICESat (GLAS) Science Processing Software Document Series: Science Software Management Plan - Volume 1

This document provides the Software Management Plan for the GLAS Standard Data Software (SDS) supporting the GLAS instrument of the EOS ICESat Spacecraft. The SDS encompasses the ICESat Science Investigator-led Processing System (I-SIPS) Software and the Instrument Support Terminal (IST) Software. For the I-SIPS Software, the SDS will produce Level 0, Level 1, and Level 2 data products as well as the associated product quality assessments and descriptive information. For the IST Software, the SDS will accommodate the GLAS instrument support areas of engineering status, command, performance assessment, and instrument health status.

Hancock, David W., III↗

MPACT Software Test Plan, Requirements, and Test Report (V.4.3)

This document presents the software test plan for MPACT. The software requirements and software test report are provided in the appendices. The test platform hardware and software are described herein. Appendix A provides a list of the tests that were run and their acceptability as a test report. Appendix B provides the list of low-level software requirements as a requirements traceability matrix.

97 MATHEMATICS AND COMPUTING↗

Software for Optimizing Plans Involving Interdependent Goals

A computer program enables construction and optimization of plans for activities that are directed toward achievement of goals that are interdependent. Goal interdependence is defined as the achievement of one or more goals affecting the desirability or priority of achieving one or more other goals. This program is overlaid on the Automated Scheduling and Planning Environment (ASPEN) software system, aspects of which have been described in a number of prior NASA Tech Briefs articles. Unlike other known or related planning programs, this program considers interdependences among goals that can change between problems and provides a language for easily specifying such dependences. Specifications of the interdependences can be formulated dynamically and provided to the associated planning software as part of the goal input. Then an optimization algorithm provided by this program enables the planning software to reason about the interdependences and incorporate them into an overall objective function that it uses to rate the quality of a plan under construction and to direct its optimization search. In tests on a series of problems of planning geological experiments by a team of instrumented robotic vehicles (rovers) on new terrain, this program was found to enhance plan quality.

Estlin, Tara↗

Software verification plan for GCS

This verification plan is written as part of an experiment designed to study the fundamental characteristics of the software failure process. The experiment will be conducted using several implementations of software that were produced according to industry-standard guidelines, namely the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, Software Consideration in Airborne Systems and Equipment Certification, for the development of flight software. This plan fulfills the DO-178A requirements for providing instructions on the testing of each implementation of software. The plan details the verification activities to be performed at each phase in the development process, contains a step by step description of the testing procedures, and discusses all of the tools used throughout the verification process.

Dent, Leslie A.↗

JPL software training plan

The purpose of this document is to define the software training approach and plans for the Jet Propulsion Laboratory.

software training plan↗

Flashline Mars Arctic Research Station (FMARS) 2009 Expedition Crew Perspectives

The Flashline Mars Arctic Research Station (FMARS), located on the rim of the Haughton Crater on Devon Island in the Canadian Arctic, is a simulated Mars habitat that provides operational constraints similar to those which will be faced by future human explorers on Mars. In July 2009, a six-member crew inhabited the isolated habitation module and conducted the twelfth FMARS mission. The crew members conducted frequent EVA operations wearing mock space suits to conduct field experiments under realistic Mars-like conditions. Their scientific campaign spanned a wide range of disciplines and included many firsts for Mars analog research. Among these are the first use of a Class IV medical laser during a Mars simulation, helping to relieve crew stress injuries during the mission. Also employed for the first time in a Mars simulation at FMARS, a UAV (Unmanned Aerial Vehicle) was used by the space-suited explorers, aiding them in their search for mineral resources. Sites identified by the UAV were then visited by geologists who conducted physical geologic sampling. For the first time, explorers in spacesuits deployed passive seismic equipment to monitor earthquake activity and characterize the planet's interior. They also conducted the first geophysical electromagnetic survey as analog Mars pioneers to search for water and characterize geological features under the surface. The crew collected hydrated minerals and attempted to produce drinkable water from the rocks. A variety of equipment was field tested as well, including new cameras that automatically geotag photos, data-recording GPS units, a tele-presence rover (operated from Florida), as well as MIT-developed mission planning software. As plans develop to return to the Moon and go on to Mars, analog facilities like FMARS can provide significant benefit to NASA and other organizations as they prepare for robust human space exploration. The authors will present preliminary results from these studies as well as their perspectives on topics including human factors, logistics, EVA operations, and the use of social media throughout the mission.

Cusack, Stacy↗

Advanced communications technology satellite high burst rate link evaluation terminal power control and rain fade software test plan, version 1.0

The Power Control and Rain Fade Software was developed at the NASA Lewis Research Center to support the Advanced Communications Technology Satellite High Burst Rate Link Evaluation Terminal (ACTS HBR-LET). The HBR-LET is an experimenters terminal to communicate with the ACTS for various experiments by government, university, and industry agencies. The Power Control and Rain Fade Software is one segment of the Control and Performance Monitor (C&PM) Software system of the HBR-LET. The Power Control and Rain Fade Software automatically controls the LET uplink power to compensate for signal fades. Besides power augmentation, the C&PM Software system is also responsible for instrument control during HBR-LET experiments, control of the Intermediate Frequency Switch Matrix on board the ACTS to yield a desired path through the spacecraft payload, and data display. The Power Control and Rain Fade Software User's Guide, Version 1.0 outlines the commands and procedures to install and operate the Power Control and Rain Fade Software. The Power Control and Rain Fade Software Maintenance Manual, Version 1.0 is a programmer's guide to the Power Control and Rain Fade Software. This manual details the current implementation of the software from a technical perspective. Included is an overview of the Power Control and Rain Fade Software, computer algorithms, format representations, and computer hardware configuration. The Power Control and Rain Fade Test Plan provides a step-by-step procedure to verify the operation of the software using a predetermined signal fade event. The Test Plan also provides a means to demonstrate the capability of the software.

Reinhart, Richard C.↗

VERAIO Software Management Plan

VERAIO is a set of utility codes used to provide a common set of input and outputs to the Virtual Environment for Reactor Applications (VERA). VERA is a collection of several different computer codes that all have a common input and output. This prevents the need to manage input and output from each individual code, allowing for ease of use and reducing errors associated with code operability. The VERAIO utilities include VERAIn, VERAView, and VERARun. Each of these utilities is described below. VERAIn is an input processor that reads an ASCII input file generated by users, parses the file, performs some error checking, and writes an XML file to be read by other VERA codes. The main purpose of VERAIn is to provide a common input to all of the VERA codes so users only need to learn one input. VERAIn is written in Perl and uses YAML configuration files to provide flexibility. VERAView is a graphical user interface (GUI) that reads a VERA HDF output file and allows users to visualize results. VERAView is written in Python. VERARun is a script that drives the VERA execution in a high performance computing (HPC) environment. Work performed at the code level supports the Quality Assurance Program Plan (QAPP) (VERA-QA-001), and VERA Software Quality Assurance Plan (VERA-QA-002).

97 MATHEMATICS AND COMPUTING↗

MPACT Software Management Plan (V.4.3)

The MPACT code solves a discretized form of the Boltzmann transport equation on a wide variety of geometries and is distributed with a multigroup neutron cross section library. MPACT provides an advanced geometrically resolved neutral-particle transport capability to solve the flux distribution throughout the entire problem geometry, and it can model the isotopic depletion, decay, and activation of materials. The flux solution in MPACT is provided using a 2D/1D synthesis method within the framework of the 3D coarse mesh finite difference (CMFD) method for which axial and radial correction factors are obtained from 2D method of characteristics (MOC) and 1D nodal expansion method (NEM), PN, or SN. Other key characteristics of the MPACT code include the subgroup method and the embedded self-shielding method (ESSM) for resonance treatment, depletion capability based on the ORIGEN exponential matrix method, and a simplified thermal-hydraulics method for temperature/fluid feedback. The sole purpose of the simplified feedback model is to provide a mechanism for testing during code development and to provide a limited capability for educational applications. Work performed at the code level supports the VERA-QA-001, quality assurance program plan (QAPP) and VERA-QA-002, VERA Software Quality Assurance Plan.

97 MATHEMATICS AND COMPUTING↗

Software Quality Assurance Plan: Argonne Reactor Code Software

The Argonne Reactor Code (ARC) software package consists of 13 primary and many secondary pieces of software that are connected through interface files. The ARC software suite supports users in their fast reactor design goals by providing neutronic, thermal-hydraulic, and structural analysis capabilities.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗