Search NASASearch

SEARCH · Search NASA

Results for “Timeline”

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 73 records · Page 4

Global Precipitation Measurement (GPM) Safety Inhibit Timeline Tool

The Global Precipitation Measurement (GPM) Observatory is a joint mission under the partnership by National Aeronautics and Space Administration (NASA) and the Japan Aerospace Exploration Agency (JAXA), Japan. The NASA Goddard Space Flight Center (GSFC) has the lead management responsibility for NASA on GPM. The GPM program will measure precipitation on a global basis with sufficient quality, Earth coverage, and sampling to improve prediction of the Earth's climate, weather, and specific components of the global water cycle. As part of the development process, NASA built the spacecraft (built in-house at GSFC) and provided one instrument (GPM Microwave Imager (GMI) developed by Ball Aerospace) JAXA provided the launch vehicle (H2-A by MHI) and provided one instrument (Dual-Frequency Precipitation Radar (DPR) developed by NTSpace). Each instrument developer provided a safety assessment which was incorporated into the NASA GPM Safety Hazard Assessment. Inhibit design was reviewed for hazardous subsystems which included the High Gain Antenna System (HGAS) deployment, solar array deployment, transmitter turn on, propulsion system release, GMI deployment, and DPR radar turn on. The safety inhibits for these listed hazards are controlled by software. GPM developed a "pathfinder" approach for reviewing software that controls the electrical inhibits. This is one of the first GSFC in-house programs that extensively used software controls. The GPM safety team developed a methodology to document software safety as part of the standard hazard report. As part of this process a new tool "safety inhibit time line" was created for management of inhibits and their controls during spacecraft buildup and testing during 1& Tat GSFC and at the Range in Japan. In addition to understanding inhibits and controls during 1& T the tool allows the safety analyst to better communicate with others the changes in inhibit states with each phase of hardware and software testing. The tool was very useful for communicating compliance with safety requirements especially when working with a foreign partner.

Dion, Shirley

The Ice, Cloud, and land Elevation Satellite (ICESat) Summary Mission Timeline and Performance Relative to Pre-Launch Mission Success Criteria

The Ice, Cloud and land Elevation Satellite (ICESat) mission was conceived, primarily, to quantify the spatial and temporal variations in the topography of the Greenland and Antarctic ice sheets. It carried on board the Geoscience Laser Altimeter System (GLAS), which measured the round-trip travel time of a laser pulse emitted from the satellite to the surface of the Earth and back. Each range derived from these measurements was combined with precise, concurrent orbit and pointing information to determine the location of the laser spot centroid on the Earth. By developing a time series of precise topographic maps for each ice sheet, changes in their surface elevations can be used to infer their mass balances.

Webb, Charles E.

Supporting Real-Time Operations and Execution through Timeline and Scheduling Aids

Since 2003, the NASA Ames Research Center has been actively involved in researching and advancing the state-of-the-art of planning and scheduling tools for NASA mission operations. Our planning toolkit SPIFe (Scheduling and Planning Interface for Exploration) has supported a variety of missions and field tests, scheduling activities for Mars rovers as well as crew on-board International Space Station and NASA earth analogs. The scheduled plan is the integration of all the activities for the day/s. In turn, the agents (rovers, landers, spaceships, crew) execute from this schedule while the mission support team members (e.g., flight controllers) follow the schedule during execution. Over the last couple of years, our team has begun to research and validate methods that will better support users during realtime operations and execution of scheduled activities. Our team utilizes human-computer interaction principles to research user needs, identify workflow processes, prototype software aids, and user test these. This paper discusses three specific prototypes developed and user tested to support real-time operations: Score Mobile, Playbook, and Mobile Assistant for Task Execution (MATE).

scheduling

Radar Surveillance Volume for Phase 1 UAS's Alerting Timeline

This presentation briefs simulation results for the Phase 1 UAS encounters. Results are broken into four UAS speed ranges and metrics computed include the cumulative distribution curves for range, bearing, and elevation at the first corrective alerts.

unmanned

Adventures in Lunar Core Processing: Timeline of and Preparation for Opening of Core Sample 73002 for the ANGSA Program

The Apollo mission returned 382 kg of rocks, soil and core samples, which have helped to advance our knowledge of lunar science. Studies of these lunar samples are crucial for our understanding of the Moon’s geological evolution. Here, we present the meticulous process that involves preparing for, and ultimately opening, the unopened Apollo 17 drive tube: 73002,0, so that the next generation of lunar scientists can further our insight into the Moon’s history.

Krysher, C. H.

Human Mars Surface Mission Surface Power Impacts on Timeline and Traverse Capabilities

The National Aeronautics and Aerospace Administration’s (NASA) Mars Architecture Team (MAT) developed a concept for power management operations to support a thirty-day, minimal infrastructure Mars surface mission. The surface elements in this minimal surface mission concept include three landers as platforms for surface operations, a crewed Mars ascent vehicle (MAV), an unpressurized rover, and a pressurized rover where the crew will live for the duration of the thirty-day mission. In this analysis the power system is a ten kilowatt fission power system, which has been selected for its resiliency to dust storms, and will provide power for all aspects of the surface mission including thermal management of propellant and electronic systems, communications, and battery recharge of mobile surface assets. Developing a power management plan with the consideration of the various elements and mission phases helps define the traverse and exploration capabilities for the crew in the pressurized rover. Also, considerations need to be made for the different power requirements for each phase of the surface mission including arrival, offload, surface exploration, launch preparation, and departure. The described analysis aims to achieve a balance of maintaining power to critical systems while enabling desired traverse and exploration range in the pressurized rover. Additionally, a few enhancing technologies were explored that could expand the power capability if the additional capacity is necessary in the future. This study is used as a baseline to understand the constraints on all aspects of the surface mission for a minimal surface infrastructure human Mars campaign if a ten-kilowatt fission surface power system is available on the surface.

Michael B. Chappell

Human Mars Mission Surface Power Impacts on Timeline and Traverse Capabilities

The National Aeronautics and Aerospace Administration’s (NASA) Mars Architecture Team (MAT) developed a concept for power management operations to support a thirty-day, minimal infrastructure Mars surface mission. The surface elements in this minimal surface mission concept include three landers as platforms for surface operations, a crewed Mars ascent vehicle (MAV), an unpressurized rover, and a pressurized rover where the crew will live for the duration of the thirty-day mission. In this analysis the power system is a ten kilowatt fission power system, which has been selected for its resiliency to dust storms, and will provide power for all aspects of the surface mission including thermal management of propellant and electronic systems, communications, and battery recharge of mobile surface assets. Developing a power management plan with the consideration of the various elements and mission phases helps define the traverse and exploration capabilities for the crew in the pressurized rover. Also, considerations need to be made for the different power requirements for each phase of the surface mission including arrival, offload, surface exploration, launch preparation, and departure. The described analysis aims to achieve a balance of maintaining power to critical systems while enabling desired traverse and exploration range in the pressurized rover. Additionally, a few enhancing technologies were explored that could expand the power capability if the additional capacity is necessary in the future. This study is used as a baseline to understand the constraints on all aspects of the surface mission for a minimal surface infrastructure human Mars campaign if a ten-kilowatt fission surface power system is available on the surface.

Michael B Chappell

In-Space Crew-Collaborative Task Scheduling

For all past and current human space missions, the final scheduling of tasks to be done in space has been devoid of crew control, flexibility, and insight. Ground controllers, with minimal input from the crew, schedule the tasks and uplink the timeline to the crew or uplink the command sequences to the hardware. Prior to the International Space Station (ISS), the crew could make requests about tomorrow s timeline, they could omit a task, or they could request that something in the timeline be delayed. This lack of control over one's own schedule has had negative consequences. There is anecdotal consensus among astronauts that control over their own schedules will mitigate the stresses of long duration missions. On ISS, a modicum of crew control is provided by the job jar. Ground controllers prepare a task list (a.k.a. "job jar") of non-conflicting tasks from which jobs can be chosen by the in space crew. Because there is little free time and few interesting non-conflicting activities, the task-list approach provides little relief from the tedium of being micro-managed by the timeline. Scheduling for space missions is a complex and laborious undertaking which usually requires a large cadre of trained specialists and suites of complex software tools. It is a giant leap from today s ground prepared timeline (with a job jar) to full crew control of the timeline. However, technological advances, currently in-work or proposed, make it reasonable to consider scheduling a collaborative effort by the ground-based teams and the in-space crew. Collaboration would allow the crew to make minor adjustments, add tasks according to their preferences, understand the reasons for the placement of tasks on the timeline, and provide them a sense of control. In foreseeable but extraordinary situations, such as a quick response to anomalies and extended or unexpected loss of signal, the crew should have the autonomous ability to make appropriate modifications to the timeline, extend the timeline, or even start over with a new timeline. The Vision for Space Exploration (VSE), currently being pursued by the National Aeronautics and Space Administration (NASA), will send humans to Mars in a few decades. Stresses on the human mind will be exacerbated by the longer durations and greater distances, and it will be imperative to implement stress-reducing innovations such as giving the crew control of their daily activities.

Jaap, John

International Space Station (ISS) Payload Autonomous Operations Past, Present and Future

Draper Laboratorys Timeliner is a scripting and automation system that runs onboard computers in the International Space Station (ISS). Timeliner is fully integrated with ISS and can be used to automate ISS operations tasks. Some of the most challenging aspects of operating a payload in low earth orbit are communication delays, ground equipment failures, and human errors. How does a Payload Developer (PD) know their equipment is operating nominally and collecting science in the most efficient way possible or even powered at any given time? During a ground Loss of Signal (LOS) data outage, PDs have no insight into their experiments state, and benefit greatly from Timeliner scripts executing on ISS to perform telemetry monitoring and commanding operations. This paper will discuss current software designs, and new operational uses for Timeliner. Existing Timeliner capabilities discussed will include: autonomous EXPRESS Rack activation and deactivation; autonomous science data downlinks; Minus Eighty Degree Freezer (MELFI) Dewar autonomous safing; JAXA and ESA module autonomous payload facility safing; as well as many others. New operational concepts discussed will include allowing Timeliner on the payload computer to issue core commands (Thermal, Power, Fire Detection), creation of new ground tools that will monitor the current status of Payload Racks as well as all the messaging from autonomous scripts executing, decreasing approval time for Timeliner bundles, and opening up the Payload MDM Enhanced Processor Integrated Communications Card (EPIC) interface. The EPIC interface could provide a new crew interface for PL Timeliner execution. The new interface could operate on either a Payload Computer System (PCS) or a Station Support Computer (SSC) that is plugged into either the Payload LAN or the Operations LAN which will make communicating to the PL MDM more flexible and greatly increase band width for communication.

Space Mission Automation

Onboard Short Term Plan Viewer

Onboard Short Term Plan Viewer (OSTPV) is a computer program for electronic display of mission plans and timelines, both aboard the International Space Station (ISS) and in ISS ground control stations located in several countries. OSTPV was specifically designed both (1) for use within the limited ISS computing environment and (2) to be compatible with computers used in ground control stations. OSTPV supplants a prior system in which, aboard the ISS, timelines were printed on paper and incorporated into files that also contained other paper documents. Hence, the introduction of OSTPV has both reduced the consumption of resources and saved time in updating plans and timelines. OSTPV accepts, as input, the mission timeline output of a legacy, print-oriented, UNIX-based program called "Consolidated Planning System" and converts the timeline information for display in an interactive, dynamic, Windows Web-based graphical user interface that is used by both the ISS crew and ground control teams in real time. OSTPV enables the ISS crew to electronically indicate execution of timeline steps, launch electronic procedures, and efficiently report to ground control teams on the statuses of ISS activities, all by use of laptop computers aboard the ISS.

Hall, Tim

Irreducible Tests for Space Mission Sequencing Software

As missions extend further into space, the modeling and simulation of their every action and instruction becomes critical. The greater the distance between Earth and the spacecraft, the smaller the window for communication becomes. Therefore, through modeling and simulating the planned operations, the most efficient sequence of commands can be sent to the spacecraft. The Space Mission Sequencing Software is being developed as the next generation of sequencing software to ensure the most efficient communication to interplanetary and deep space mission spacecraft. Aside from efficiency, the software also checks to make sure that communication during a specified time is even possible, meaning that there is not a planet or moon preventing reception of a signal from Earth or that two opposing commands are being given simultaneously. In this way, the software not only models the proposed instructions to the spacecraft, but also validates the commands as well.To ensure that all spacecraft communications are sequenced properly, a timeline is used to structure the data. The created timelines are immutable and once data is as-signed to a timeline, it shall never be deleted nor renamed. This is to prevent the need for storing and filing the timelines for use by other programs. Several types of timelines can be created to accommodate different types of communications (activities, measurements, commands, states, events). Each of these timeline types requires specific parameters and all have options for additional parameters if needed. With so many combinations of parameters available, the robustness and stability of the software is a necessity. Therefore a baseline must be established to ensure the full functionality of the software and it is here where the irreducible tests come into use.

sequencing test