Search NASA⌕ Search

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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Task network models in the prediction of workload imposed by extravehicular activities during the Hubble Space Telescope servicing mission

In a joint effort with Brooks AFB, Texas, the Flight Crew Support Division at JSC has begun a computer simulation and performance modeling program directed at establishing the predictive validity of software tools for modeling human performance during spaceflight. This paper addresses the utility of task network modeling for predicting the workload that astronauts are likely to encounter in extravehicular activities (EVA) during the Hubble Space Telescope (HST) repair mission. The intent of the study was to determine whether two EVA crewmembers and one intravehicular activity (IVA) crewmember could reasonably be expected to complete HST Wide Field/Planetary Camera (WFPC) replacement in the allotted time. Ultimately, examination of the points during HST servicing that may result in excessive workload will lead to recommendations to the HST Flight Systems and Servicing Project concerning (1) expectation of degraded performance, (2) the need to change task allocation across crewmembers, (3) the need to expand the timeline, and (4) the need to increase the number of EVA's.

Diaz, Manuel F.↗
NASA NTRS1994

Reuseable Objects Software Environment (ROSE): Introduction to Air Force Software Reuse Workshop

The Reusable Objects Software Environment (ROSE) is a common, consistent, consolidated implementation of software functionality using modern object oriented software engineering including designed-in reuse and adaptable requirements. ROSE is designed to minimize abstraction and reduce complexity. A planning model for the reverse engineering of selected objects through object oriented analysis is depicted. Dynamic and functional modeling are used to develop a system design, the object design, the language, and a database management system. The return on investment for a ROSE pilot program and timelines are charted.

Cottrell, William L.↗
NASA NTRS1994

Demand access communications for TDRSS users

The Tracking and Data Relay Satellite System (TDRSS) has long been used to provide reliable low and high-data rate relay services between user spacecraft in Earth orbit and the ground. To date, these TDRSS services have been implemented via prior scheduling based upon estimates of user needs and mission event timelines. While this approach may be necessary for large users that require greater amounts of TDRSS resources, TDRSS can potentially offer the planned community of smaller science missions (e.g., the small explorer missions), and other emerging users, the unique opportunity for services on demand. In particular, innovative application of the existing TDRSS Multiple Access (MA) subsystem, with its phased array antenna, could be used to implement true demand access services without modification to either the TDRSS satellites or the user transponder, thereby introducing operational and performance benefits to both the user community and the Space Network. In this paper, candidate implementations of demand access service via the TDRSS MA subsystem are examined in detail. Both forward and return link services are addressed and a combination of qualitative and quantitative assessments are provided. The paper also identifies further areas for investigation in this ongoing activity that is being conducted by GSFC/Code 531 under the NASA Code O Advanced Systems Program.

Zillig, David↗
NASA NTRS1994

Joint operations planning for space surveillance missions on the MSX satellite

The Midcourse Space Experiment (MSX) satellite, sponsored by BMDO, is intended to gather broad-band phenomenology data on missiles, plumes, naturally occurring earthlimb backgrounds and deep space backgrounds. In addition the MSX will be used to conduct functional demonstrations of space-based space surveillance. The JHU/Applied Physics Laboratory (APL), located in Laurel, MD, is the integrator and operator of the MSX satellite. APL will conduct all operations related to the MSX and is charged with the detailed operations planning required to implement all of the experiments run on the MSX except the space surveillance experiments. The non-surveillance operations are generally amenable to being defined months ahead of time and being scheduled on a monthly basis. Lincoln Laboratory, Massachusetts Institute of Technology (LL), located in Lexington, MA, is the provider of one of the principle MSX instruments, the Space-Based Visible (SBV) sensor, and the agency charged with implementing the space surveillance demonstrations on the MSX. The planning timelines for the space surveillance demonstrations are fundamentally different from those for the other experiments. They are generally amenable to being scheduled on a monthly basis, but the specific experiment sequence and pointing must be refined shortly before execution. This allocation of responsibilities to different organizations implies the need for a joint mission planning system for conducting space surveillance demonstrations. This paper details the iterative, joint planning system, based on passing responsibility for generating MSX commands for surveillance operations from APL to LL for specific scheduled operations. The joint planning system, including the generation of a budget for spacecraft resources to be used for surveillance events, has been successfully demonstrated during ground testing of the MSX and is being validated for MSX launch within the year. The planning system developed for the MSX forms a model possibly applicable to developing distributed mission planning systems for other multi-use satellites.

Stokes, Grant↗
NASA NTRS1994

A software architecture for automating operations processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Miller, Kevin J.↗
NASA NTRS1994

SEQ-GEN: A comprehensive multimission sequencing system

SEQ-GEN is a user-interactive computer program used to plan and generate a sequence of commands for spacecraft. Desired activities are specified by the user of SEQ-GEN; SEQ-GEN in turn expands these activities, deriving the spacecraft commands necessary to accomplish the desired activities. SEQ-GEN models the effects on the spacecraft of the commands, predicting the state as a function of time, flagging any conflicts and rule violations. These states, conflicts, and violations are viewable both graphically and textually at the user's request. SEQ-GEN also displays the entire sequence graphically, showing each requested activity as a bar on its graphical timeline. SEQ-GEN immediately revalidates the sequence, updating its models and calculations along with its displays based on these changes. Because it has the ability to recalculate spacecraft states immediately, the user is able to perform 'what-if' sessions easily. SEQ-GEN, a multimission tool, is adaptable to any flight project. A flight project writes its adaptation files containing project unique information including in its simplest form, only spacecraft commands. For more involved projects the adaptation files may also contain flight and mission rules, description of the spacecraft and ground models, and the definition of activities. SEQ-GEN operates at whatever level of detail the adaptation files imply. Simple adaptations are straight forward to do. There is, however, no limit to the complexity of activity definitions or of spacecraft models: both may involve unlimited logical decision points. Commands and activities may involve any number of parameters of a wide variety of data types, including integer, float, time, boolean, and character strings. SEQ-GEN will be used by the Mars Pathfinder, Cassini, and VIM (Voyager Interstellar Mission) project in an effort to speed up adaptation time and to keep sequence generation costs down. SEQ-GEN is hosted on UNIX workstations. It uses MOTIF and X for windowing, and was designed and coded in an object-oriented style in the language C++.

Salcedo, Jose↗
NASA NTRS1995

Quick Look Report of Acceleration Measurements on Mir Space Station During Mir-16

The NASA Microgravity Science and Applications Division (MSAD) sponsors the Space Acceleration Measurement System (SAMS) to support microgravity science experiments with microgravity acceleration measurements. In the past, SAMS was flown exclusively on the NASA Orbiters. MSAD is currently sponsoring science experiments participating in the Shuttle-Mir Science Program in cooperation with the Russians on the Mir space station. Included in the complement of MSAD experiments and equipment is a SAMS unit installed on the Mir space station. On 25 August 1994, the SAMS unit was launched on a Russia Progress vehicle to the Mir space station. The SAMS unit will support science experiments from the U.S. and Russia in a manner similar to the Orbiter missions by measuring the microgravity environments during the experiment operations. In October 1994, the SAMS unit recorded data on Mir for over fifty-three hours in seven different time periods to survey possible locations for future experiments. This report presents a quick look at the data and the microgravity environment during the time periods in which SAMS data were acquired. The Mir acceleration data were examined to ascertain gross attributes of the data. This report does not present an exhaustive examination of all possible activities due to the short time available to prepare this quick look report and due to the absence of complete timeline information during the SAMS recording time periods. Appendices A, B and C provide plots of the SAMS data for an overview of the microgravity environment at the times that data were recorded. Appendix D describes the procedures to access SAMS data by file transfer protocol (ftp) utilizing the internet. Appendix E contains a user comment sheet.

Delombard, Richard↗
NASA NTRS1994

Interactive autonomy and robotic skills

Current concepts of robot-supported operations for space laboratories (payload servicing, inspection, repair, and ORU exchange) are mainly based on the concept of 'interactive autonomy' which implies autonomous behavior of the robot according to predefined timelines, predefined sequences of elementary robot operations and within predefined world models supplying geometrical and other information for parameter instantiation on the one hand, and the ability to override and change the predefined course of activities by human intervention on the other hand. Although in principle a very powerful and useful concept, in practice the confinement of the robot to the abstract world models and predefined activities appears to reduce the robot's stability within real world uncertainties and its applicability to non-predefined parts of the world, calling for frequent corrective interaction by the operator, which in itself may be tedious and time-consuming. Methods are presented to improve this situation by incorporating 'robotic skills' into the concept of interactive autonomy.

Kellner, A.↗
NASA NTRS1995

Space Shuttle mission: STS-67

The Space Shuttle Endeavor, scheduled to launch March 2, 1995 from NASA's Kennedy Space Center, will conduct NASA's longest Shuttle flight prior to date. The mission, designated STS-67, has a number of experiments and payloads, which the crew, commanded by Stephen S. Oswald, will have to oversee. This NASA press kit for the mission contains a general background (general press release, media services information, quick-look facts page, shuttle abort modes, summary timeline, payload and vehicle weights, orbital summary, and crew responsibilities); cargo bay payloads and activities (Astro 2, Get Away Special Experiments); in-cabin payloads (Commercial Minimum Descent Altitude Instrumentation Technology Associates Experiments, protein crystal growth experiments, Middeck Active Control Experiment, and Shuttle Amateur Radio Experiment); and the STS-67 crew biographies. The payloads and experiments are described and summarized to give an overview of the goals, objectives, apparatuses, procedures, sponsoring parties, and the assigned crew members to carry out the tasks.

Source record↗
NASA NTRS1995

The transition of GTDS to the Unix workstation environment

Future Flight Dynamics systems should take advantage of the possibilities provided by current and future generations of low-cost, high performance workstation computing environments with Graphical User Interface. The port of the existing mainframe Flight Dynamics systems to the workstation environment offers an economic approach for combining the tremendous engineering heritage that has been encapsulated in these systems with the advantages of the new computing environments. This paper will describe the successful transition of the Draper Laboratory R&D version of GTDS (Goddard Trajectory Determination System) from the IBM Mainframe to the Unix workstation environment. The approach will be a mix of historical timeline notes, descriptions of the technical problems overcome, and descriptions of associated SQA (software quality assurance) issues.

Carter, D.↗
NASA NTRS1993

Shuttle flight data and in-flight anomaly list. STS-1 through STS-50, and STS-52 through STS-56. Revision T

This report contains mission data for space shuttle flights and consists of three sections. The first section is a listing of shuttle flight data for flights STS-1 through STS-55 gathered during the mission evaluation process. The second section is a listing of all orbiter in-flight anomalies arranged in order by affected Work Unit Codes of the failed items from shuttle flights STS-1 through STS-50 and STS-52 through STS-56. The third section consists of data derived from the as-flown orbiter attitude timelines and crew activity plans for each mission. The data are presented in chart form and show the progression of the mission from launch to entry interface with the varying orbiter attitudes (roll, pitch, and yaw) and the time duration in each attitude. The chart also shows the orbiter's velocity vector, i.e., which of the orbiter's body axes is pointing forward along the orbital path. The Beta angle, the angle between the sun vector and the orbital plane, is also shown for each 12-hour period of the mission.

Source record↗
NASA NTRS1995

Flight demonstration of laser diode initiated ordnance

A program has been initiated by NASA Headquarters to validate laser initiated ordnance in flight applications. The primary program goal is to bring together a team of government and industry members to develop a laser initiated ordnance system having the test and analysis pedigree to be flown on launch vehicles. The culmination of this effort was a flight of the Pegasus launch vehicle which had two fin rockets initiated by this laser system. In addition, a laser initiated ordnance squib was fired into a pressure bomb during thrusting flight. The complete ordnance system comprising a laser diode firing unit, fiber optic cable assembly, laser initiated detonator, and laser initiated squib was designed and built by The Ensign Bickford Company. The hardware was tested to the requirements of the Pegasus launch vehicle and integrated into the vehicle by The Ensign Bickford Company and the Orbital Sciences Corporation. Discussions include initial program concept, contract implementation, team member responsibilities, analysis results, vehicle integration, safing architecture, ordnance interfaces, mission timeline and telemetry data. A complete system description, summary of the analyses, the qualification test results, and the results of flight are included.

Boucher, Craig J.↗
NASA NTRS1993

Study and Demonstration of Planning and Scheduling Concepts for the Earth Observing System Data and Information System

The University of Colorado's Laboratory for Atmospheric and Space Physics (CU/LASP) along with the Goddard Space Flight Center (GSFC) and the Jet Propulsion Laboratory (JPL) designed, implemented, tested, and demonstrated a prototype of the distributed, hierarchical planning and scheduling system comtemplated for the Earth Observing System (EOS) project. The planning and scheduling prototype made use of existing systems: CU/LASP's Operations and Science Instrument Support Planning and Scheduling (OASIS-PS) software package; GSFC's Request Oriented Scheduling Engine (ROSE); and JPL's Plan Integrated Timeliner 2 (Plan-It-2). Using these tools, four scheduling nodes were implemented and tied together using a new communications protocol for scheduling applications called the Scheduling Applications Interface Language (SAIL). An extensive and realistic scenario of EOS satellite operations was then developed and the prototype scheduling system was tested and demonstrated using the scenario. Two demonstrations of the system were given to NASA personnel and EOS core system (ECS) contractor personnel. A comprehensive volume of lessons learned was generated and a meeting was held with NASA and ECS representatives to review these lessons learned. A paper and presentation on the project's final results was given at the American Institute of Aeronautics and Astronautics Computing in Aerospace 9 conference.

Davis, Randal↗
NASA NTRS1996

Preparation of Flight Operations and IWS Integration of the CELIAS Experiment on the SOHO Spacecraft

During this annual progress report time period, the following activities took place: (1) Generation of several versions of the CELIAS (STOF/SEM/CTOF/MTOF/DPU) commissioning timeline for the first 180 days after launch. These were written and submitted by A. Galvin after consultation (phone, fax, e-mail, meetings) with the CELIAS Instrument Manager and Lead-Co-I's. (2) Identification of several problems with the CELIAS portion of the Project Data Base (PDB). (3) Meetings with the Flight Operations Team regarding PDB, critical commands, etc. (4) Attend Science Operations Working Group (SOWG) Meetings (November 1994, February 1995, May 1995) and Flight Operations Review Meeting (July 1995). (5) Participate in Flight Operation Simulations SIM 1 (November 14-18, 1994), SIM 2 (May 1-4, 1995) and SIM3 (August 7-11, 1995). (6) Participate in the Ground System Compatibility Test Rehearsal (April 24- 28, 1995), GSCT #2 (May 30-June 14, 1995), GSCT #3 (September 12-22, 1995), and GSCT #4b (October 30-November 5, 1995). A small portion of the documentation for the above cited activities is appended.

Ipavich, Fred↗
NASA NTRS1996

Preparation of Flight Operations and IWS Integration of the CELIAS Experiment on the SOHO Spacecraft

During this reporting time period, the following activities took place: (1) generation of several versions of the CELIAS (STOF/SEM/CTOF/MTOF/DPU) commissioning timeline for the first 180 days after launch; (2) identification of several problems with the CELIAS portion of the Project Data Base (PDB); (3) attendance of the Science Operations Working Group (SOWG) Meetings (November 1994, February 1995, May 1995) and Flight Operations Review Meeting (July 1995); (4) participation in Flight Operation Simulations SIM 1 (November 14-18, 1994), SIM 2 (May 1-4, 1995) and SIM3 (August 7-11, 1995); and (5) participation in the Ground System Compatibility Test Rehearsal (April 24-28) 1995), GSCT #2 (May 30-June 14, 1995), GSCT #3 (September 12-22 1995), and GSCT #4b (October 30-November 5, 1995).

Ipavich, Fred↗
NASA NTRS1996

Technology Directions for the 21st Century

The Office of Space Communications (OSC) is tasked by NASA to conduct a planning process to meet NASA's science mission and other communications and data processing requirements. A set of technology trend studies was undertaken by Science Applications International Corporation (SAIC) for OSC to identify quantitative data that can be used to predict performance of electronic equipment in the future to assist in the planning process. Only commercially available, off-the-shelf technology was included. For each technology area considered, the current state of the technology is discussed, future applications that could benefit from use of the technology are identified, and likely future developments of the technology are described. The impact of each technology area on NASA operations is presented together with a discussion of the feasibility and risk associated with its development. An approximate timeline is given for the next 15 to 25 years to indicate the anticipated evolution of capabilities within each of the technology areas considered. This volume contains four chapters: one each on technology trends for database systems, computer software, neural and fuzzy systems, and artificial intelligence. The principal study results are summarized at the beginning of each chapter.

Crimi, Giles F.↗
NASA NTRS1996

Balancing Science Objectives and Operational Constraints: A Mission Planner's Challenge

The Air Force minute sensor technology integration (MSTI-3) satellite's primary mission is to characterize Earth's atmospheric background clutter. MSTI-3 will use three cameras for data collection, a mid-wave infrared imager, a short wave infrared imager, and a visible imaging spectrometer. Mission science objectives call for the collection of over 2 million images within the one year mission life. In addition, operational constraints limit camera usage to four operations of twenty minutes per day, with no more than 10,000 data and calibrating images collected per day. To balance the operational constraints and science objectives, the mission planning team has designed a planning process to e event schedules and sensor operation timelines. Each set of constraints, including spacecraft performance capabilities, the camera filters, the geographical regions, and the spacecraft-Sun-Earth geometries of interest, and remote tracking station deconflictions has been accounted for in this methodology. To aid in this process, the mission planning team is building a series of tools from commercial off-the-shelf software. These include the mission manifest which builds a daily schedule of events, and the MSTI Scene Simulator which helps build geometrically correct scans. These tools provide an efficient, responsive, and highly flexible architecture that maximizes data collection while minimizing mission planning time.

Weldy, Michelle↗
NASA NTRS1996

Design and implementation of a Windows NT network to support CNC activities

The Manufacturing, Materials, & Processes Technology Division is undergoing dramatic changes to bring it's manufacturing practices current with today's technological revolution. The Division is developing Computer Automated Design and Computer Automated Manufacturing (CAD/CAM) abilities. The development of resource tracking is underway in the form of an accounting software package called Infisy. These two efforts will bring the division into the 1980's in relationship to manufacturing processes. Computer Integrated Manufacturing (CIM) is the final phase of change to be implemented. This document is a qualitative study and application of a CIM application capable of finishing the changes necessary to bring the manufacturing practices into the 1990's. The documentation provided in this qualitative research effort includes discovery of the current status of manufacturing in the Manufacturing, Materials, & Processes Technology Division including the software, hardware, network and mode of operation. The proposed direction of research included a network design, computers to be used, software to be used, machine to computer connections, estimate a timeline for implementation, and a cost estimate. Recommendation for the division's improvement include action to be taken, software to utilize, and computer configurations.

Shearrow, C. A.↗