Science.gov

Sample records for control mission operations

  1. Overall view of Mission Operations Control in Mission Control Center

    NASA Image and Video Library

    1969-05-18

    S69-34316 (18 May 1969) --- Overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, on the first day of the Apollo 10 lunar orbit mission. A color television transmission was being received from Apollo 10. This picture was made following Command and Service Module/Lunar Module/Saturn IVB (CSM/LM-S-IVB) separation and prior to LM extraction from the S-IVB. The CSM were making the docking approach to the LM/S-IVB.

  2. Mission Operations Control Room (MOCR) activities during STS-6 mission

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Vice President George Bush talks to the STS-6 astronauts from the spacecraft communicators (CAPCOM) console in the mission operations control room (MOCR) of JSC's mission control center. Astronauts Bryan D. O'Connor, second left and Roy D. Bridges, center, are the on-duty CAPCOMS. Standing near the console are (left) JSC Director Gerald D. Griffin and NASA Administrator James Beggs. Eugene F. Kranz, Director of Mission Operations, is at the back console near the glass.

  3. Mission Operations Control Room (MOCR) activities during STS-6 mission

    NASA Image and Video Library

    1983-04-05

    Astronauts Roy D. Bridges (left) and RIchard O. Covey serve as spacecraft communicators (CAPCOM) for STS-6. They are seated at the CAPCOM console in the mission operations control room (MOCR) of JSC's mission control center (30119); Flight Director Jay H. Greene communicates with a nearby flight controller in the MOCR just after launch of the Challenger (30120).

  4. Mission Operations Control Room (MOCR) activities during STS-6 mission

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Flight director Jay H. Greene (center) talks with Eugene F. Kranz, director of mission operations, in the mission operations control room (MOCR) of JSC's mission control center. Challenger was beginning to fly over Africa in Day 3 of this mission (30136); Flight director Brock R. (Randy) Stone, at the FD console in the MOCR studies the list of activities scheduled for the Challenger on that day (30137); Granvil A. (Al) Pennington waits for the launch of STS-6 as he begins his duties as ascent team integrated communication system officer (INCO) at the INCO console in the MOCR (30138).

  5. Mission Operations Control Room (MOCR) activities during STS-6 mission

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Flight director Jay H. Greene (center) talks with Eugene F. Kranz, director of mission operations, in the mission operations control room (MOCR) of JSC's mission control center. Challenger was beginning to fly over Africa in Day 3 of this mission (30136); Flight director Borck R. (Randy) Stone, at the FD console in the MOCR studies the list of activities scheduled for the Challenger on that day (30137); Granvil A. (Al) Pennington waits for the launch of STS-6 as he begins his duties as ascent team integrated communication system officer (INCO) at the INCO console in the MOCR (30138).

  6. Mission Operations Control Room (MOCR) activities during STS-6 mission

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Vice president George Bush talks to the STS-6 astronauts from the spacecraft communicators (CAPCOM) console in the mission operations control room (MOCR) of JSC's mission control center. Astronaut Roy D. Bridges, left, is one of the CAPCOM personnel on duty (30190,30192); Vice president Bush recieves instructions from Bridges at the CAPCOM console prior to talking to the STS-6 crew. The two are flanked by JSC Director Gerald D. Griffin, left, and NASA Administrator James Beggs. Mission Operations Director Eugene F. Kranz is in center background (30191); Vice President Bush, left, is briefed by JSC Director Griffin, right, during a visit to the MOCR. NASA Administrator Beggs, center, accompanied the Vice President on his visit (30193).

  7. Mission Operations Control Room Activities during STS-2 mission

    NASA Technical Reports Server (NTRS)

    1981-01-01

    Mission Operations Control Room (MOCR) activities during STS-2 mission. President Ronald Reagan is briefed by Dr. Christopher C. Kraft, Jr., JSC Director, who points toward the orbiter spotter on the projection plotter at the front of the MOCR (39499); President Reagan joking with STS-2 astronauts during space to ground conversation (39500); Mission Specialist/Astronaut Sally K. Ride communicates with the STS-2 crew from the spacecraft communicator console (39501); Charles R. Lewis, bronze team Flight Director, monitors activity from the STS-2 crew. He is seated at the flight director console in MOCR (39502); Eugene F. Kranz, Deputy Director of Flight Operations at JSC answers a question during a press conference on Nov. 13, 1981. He is flanked by Glynn S. Lunney, Manager, Space Shuttle Program Office, JSC; and Dr. Christopher C. Kraft, Jr., Director of JSC (39503).

  8. Mission Operations Control Room Activities during STS-2 mission

    NASA Technical Reports Server (NTRS)

    1981-01-01

    Mission Operations Control Room (MOCR) activities during STS-2 mission. Overall view of the MOCR in the Johnson Space Center's Mission Control Center. At far right is Eugene F. Kranz, Deputy Director of Flight Operations. At the flight director console in front of Kranz's FOD console are Flight Directors M.P. Frank, Neil B. Hutchinson and Donald R. Puddy as well as others (39506); Wide-angle view of flight controllers in the MOCR. Clifford E. Charlesworth, JSC Deputy Director, huddles with several flight directors for STS-2 at the flight director console. Kranz, is at far right of frame (39507); Dr. Christopher C. Kraft, Jr., JSC Director, center, celebrates successful flight and landing of STS-2 with a cigar in the MOCR. He is flanked by Dr. Maxime A Faget, left, Director of Engineering and Development, and Thomas L. Moser, of the Structures and Mechanics Division (39508); Flight Director Donald R. Puddy, near right, holds replica of the STS-2 insignia. Insignias on the opposite wall

  9. Designing an Alternate Mission Operations Control Room

    NASA Technical Reports Server (NTRS)

    Montgomery, Patty; Reeves, A. Scott

    2014-01-01

    The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a service-oriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building.

  10. An Open Specification for Space Project Mission Operations Control Architectures

    NASA Technical Reports Server (NTRS)

    Hooke, A.; Heuser, W. R.

    1995-01-01

    An 'open specification' for Space Project Mission Operations Control Architectures is under development in the Spacecraft Control Working Group of the American Institute for Aeronautics and Astro- nautics. This architecture identifies 5 basic elements incorporated in the design of similar operations systems: Data, System Management, Control Interface, Decision Support Engine, & Space Messaging Service.

  11. A university-based distributed satellite mission control network for operating professional space missions

    NASA Astrophysics Data System (ADS)

    Kitts, Christopher; Rasay, Mike

    2016-03-01

    For more than a decade, Santa Clara University's Robotic Systems Laboratory has operated a unique, distributed, internet-based command and control network for providing professional satellite mission control services for a variety of government and industry space missions. The system has been developed and is operated by students who become critical members of the mission teams throughout the development, test, and on-orbit phases of these missions. The mission control system also supports research in satellite control technology and hands-on student aerospace education. This system serves as a benchmark for its comprehensive nature, its student-centric nature, its ability to support NASA and industry space missions, and its longevity in providing a consistent level of professional services. This paper highlights the unique features of this program, reviews the network's design and the supported spacecraft missions, and describes the critical programmatic features of the program that support the control of professional space missions.

  12. Payload Operations Control Center During the Astro-1 Mission

    NASA Technical Reports Server (NTRS)

    1990-01-01

    This photograph was taken during the Astro-1 mission (STS-35) showing activities at NASA's new Payload Operations Control Center (POCC) at the Marshall Space Flight Center. The POCC was the air/ground communication charnel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crewmembers to resolve problems with their experiments.

  13. Dye fading test for mission control operator console displays

    NASA Technical Reports Server (NTRS)

    Lockwood, H. E.

    1975-01-01

    A dye fading test of 40 days duration was conducted to determine the effect of mission control operator console and ambient lighting effects on a series of photographic products under consideration for use in mission console operator consoles. Six different display samples, each containing 36 windows of several different colors, were prepared and placed in the mission control consoles for testing. No significant changes were recorded during the testing period. All changes were attributed to a mechanical problem with the densitometer. Detailed results are given in graphs.

  14. The NASA Mission Operations and Control Architecture Program

    NASA Technical Reports Server (NTRS)

    Ondrus, Paul J.; Carper, Richard D.; Jeffries, Alan J.

    1994-01-01

    The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

  15. (abstract) Mission Operations and Control Assurance: Flight Operations Quality Improvements

    NASA Technical Reports Server (NTRS)

    Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Witkowski, Mona M.

    1993-01-01

    Mission Operations and Command Assurance (MO&CA), a recent addition to flight operations teams at JPL. provides a system level function to instill quality in mission operations. MO&CA's primary goal at JPL is to help improve the operational reliability for projects during flight. MO&CA tasks include early detection and correction of process design and procedural deficiencies within projects. Early detection and correction are essential during development of operational procedures and training of operational teams. MO&CA's effort focuses directly on reducing the probability of radiating incorrect commands to a spacecraft. Over the last seven years at JPL, MO&CA has become a valuable asset to JPL flight projects. JPL flight projects have benefited significantly from MO&CA's efforts to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit directly from previous and ongoing experience. Since MO&CA, like Total Quality Management (TQM), focuses on continuous improvement of processes and elimination of rework, we recommend that this effort be continued on NASA flight projects.

  16. (abstract) Mission Operations and Control Assurance: Flight Operations Quality Improvements

    NASA Technical Reports Server (NTRS)

    Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Witkowski, Mona M.

    1993-01-01

    Mission Operations and Command Assurance (MO&CA), a recent addition to flight operations teams at JPL. provides a system level function to instill quality in mission operations. MO&CA's primary goal at JPL is to help improve the operational reliability for projects during flight. MO&CA tasks include early detection and correction of process design and procedural deficiencies within projects. Early detection and correction are essential during development of operational procedures and training of operational teams. MO&CA's effort focuses directly on reducing the probability of radiating incorrect commands to a spacecraft. Over the last seven years at JPL, MO&CA has become a valuable asset to JPL flight projects. JPL flight projects have benefited significantly from MO&CA's efforts to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit directly from previous and ongoing experience. Since MO&CA, like Total Quality Management (TQM), focuses on continuous improvement of processes and elimination of rework, we recommend that this effort be continued on NASA flight projects.

  17. Verification and Implementation of Operations Safety Controls for Flight Missions

    NASA Technical Reports Server (NTRS)

    Smalls, James R.; Jones, Cheryl L.; Carrier, Alicia S.

    2010-01-01

    There are several engineering disciplines, such as reliability, supportability, quality assurance, human factors, risk management, safety, etc. Safety is an extremely important engineering specialty within NASA, and the consequence involving a loss of crew is considered a catastrophic event. Safety is not difficult to achieve when properly integrated at the beginning of each space systems project/start of mission planning. The key is to ensure proper handling of safety verification throughout each flight/mission phase. Today, Safety and Mission Assurance (S&MA) operations engineers continue to conduct these flight product reviews across all open flight products. As such, these reviews help ensure that each mission is accomplished with safety requirements along with controls heavily embedded in applicable flight products. Most importantly, the S&MA operations engineers are required to look for important design and operations controls so that safety is strictly adhered to as well as reflected in the final flight product.

  18. Orbit Control Operations for the Cassini-Huygens Mission

    NASA Technical Reports Server (NTRS)

    Williams, Powtawche N.; Gist, Emily M.; Goodson, Troy D.; Hahn, Yungsun; Stumpf, Paul W.; Wagner, Sean V.

    2008-01-01

    The Cassini-Huygens spacecraft was launched in 1997 as an international and collaborative mission to study Saturn and its many moons. After a seven-year cruise, Cassini began orbiting Saturn for a four- year tour. This tour consists of 157 planned maneuvers, and their back-up locations, designed to target 52 encounters, mostly of Saturn's largest moon Titan. One of the mission's first activities was to release the Huygens probe to Titan in December 2004. Currently in its last year of the prime mission, Cassini-Huygens continues to obtain valuable data on Saturn, Titan, and Saturn's other satellites. Return of this information is in large part due to a healthy spacecraft and successful navigation. A two-year extended mission, beginning July 2008, will offer the opportunity to continue science activities. With a demanding navigation schedule that compares with the prime tour, the Cassini Navigation team relies on operations procedures developed during the prime mission to carry-out the extended mission objectives. Current processes for orbit control operations evolved from the primary navigational requirement of staying close to predetermined targeting conditions according to Cassini science sequence planning. The reference trajectory is comprised of flyby conditions to be accomplished at minimal propellant cost. Control of the planned reference trajectory orbit, and any trajectory updates, is achieved with the execution of Orbit Trim Maneuvers (OTMs). The procedures for designing, processing, and analyzing OTMs during Cassini operations is presented. First, a brief overview of the Cassini-Huygens Mission is given, followed by a general description of navigation. Orbit control and maneuver execution methods are defined, along with an outline of the orbit control staffing and operations philosophy. Finally, an example schedule of orbit control operations is shown.

  19. Orbit Control Operations for the Cassini-Huygens Mission

    NASA Technical Reports Server (NTRS)

    Williams, Powtawche N.; Gist, Emily M.; Goodson, Troy D.; Hahn, Yungsun; Stumpf, Paul W.; Wagner, Sean V.

    2008-01-01

    The Cassini-Huygens spacecraft was launched in 1997 as an international and collaborative mission to study Saturn and its many moons. After a seven-year cruise, Cassini began orbiting Saturn for a four- year tour. This tour consists of 157 planned maneuvers, and their back-up locations, designed to target 52 encounters, mostly of Saturn's largest moon Titan. One of the mission's first activities was to release the Huygens probe to Titan in December 2004. Currently in its last year of the prime mission, Cassini-Huygens continues to obtain valuable data on Saturn, Titan, and Saturn's other satellites. Return of this information is in large part due to a healthy spacecraft and successful navigation. A two-year extended mission, beginning July 2008, will offer the opportunity to continue science activities. With a demanding navigation schedule that compares with the prime tour, the Cassini Navigation team relies on operations procedures developed during the prime mission to carry-out the extended mission objectives. Current processes for orbit control operations evolved from the primary navigational requirement of staying close to predetermined targeting conditions according to Cassini science sequence planning. The reference trajectory is comprised of flyby conditions to be accomplished at minimal propellant cost. Control of the planned reference trajectory orbit, and any trajectory updates, is achieved with the execution of Orbit Trim Maneuvers (OTMs). The procedures for designing, processing, and analyzing OTMs during Cassini operations is presented. First, a brief overview of the Cassini-Huygens Mission is given, followed by a general description of navigation. Orbit control and maneuver execution methods are defined, along with an outline of the orbit control staffing and operations philosophy. Finally, an example schedule of orbit control operations is shown.

  20. INFLIGHT (MISSION OPERATIONS CONTROL ROOM [MOCR]) - STS-7 - JSC

    NASA Image and Video Library

    1983-06-18

    S83-34270 (18 June 1983) --- Astronaut C. Gordon Fullerton supplies helpful consultation for Edward I. Fendell (seated) at the Integrated Communications System (INCO) console in the Mission Operations Control Room (MOCR) of the Johnson Space Center's (JSC) Mission Control Center (MCC). Fendell had control over the TV systems during a brief television transmission that featured the opening of the payload bay doors and the revealing of the cargo in the space shuttle Challenger's 18-meter (60-feet) long payload bay. The door-opening was the first of a series of many TV sessions planned for this six-day flight. Photo credit: NASA

  1. Mission Control Center operations for the Space Transportation System

    NASA Technical Reports Server (NTRS)

    Frank, M. P.

    1982-01-01

    Orbital flight tests of the Space Shuttle Program involved three types of activities, including classic flight testing of the vehicle hardware and software, operational procedures evaluation and development, and performance of payload mission operations. This combination of activities required a capability of the Mission Control Center (MCC) to provide thorough support to the Orbiter and its crew across a broad spectrum of activities. Attention is given to MCC organization, the general functions performed by the MCC teams, a flight support description, the motivation for a change in MCC operations, support elements, orbit phase functions, and dynamic flight phase functions. It is pointed out that the MCC facilities for the operational mode of support will not be fully implemented until 1984.

  2. CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

    NASA Technical Reports Server (NTRS)

    Lucord, Steve; Martinez, Lindolfo

    2009-01-01

    We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the

  3. CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

    NASA Technical Reports Server (NTRS)

    Lucord, Steve; Martinez, Lindolfo

    2009-01-01

    We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the

  4. Verification and Implementation of Operations Safety Controls for Flight Missions

    NASA Technical Reports Server (NTRS)

    Jones, Cheryl L.; Smalls, James R.; Carrier, Alicia S.

    2010-01-01

    Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

  5. NASDA's view of ground control in mission operations

    NASA Technical Reports Server (NTRS)

    Tateno, Satoshi

    1993-01-01

    This paper presents an overview of the present status and future plans of the National Space Development Agency of Japan 's (NASDA's) ground segment and related space missions. The described ground segment consists of the tracking and data acquisition (T&DA) system and the Earth Observation Center (EOC) system. In addition to these systems, the current plan of the Engineering Support Center (ESC) for the Japanese Experiment Module (JEM) attached to Space Station Freedom is introduced. Then, NASDA's fundamental point of view on the future trend of operations and technologies in the coming new space era is discussed. Within the discussion, the increasing importance of international cooperation is also mentioned.

  6. Mission operations data analysis tools for Mars Observer guidance and control

    NASA Technical Reports Server (NTRS)

    Kan, Edwin P.

    1994-01-01

    Mission operations for the Mars Observer (MO) Project at the Jet Propulsion Laboratory were supported by a variety of ground data processing software and analysis tools. Some of these tools were generic to multimission spacecraft mission operations, some were specific to the MO spacecraft, and others were custom tailored to the operation and control of the Attitude and Articulation Control Subsystem (AACS). The focus of this paper is on the data analysis tools for the AACS. Four different categories of analysis tools are presented; with details offered for specific tools. Valuable experience was gained from the use of these tools and through their development. These tools formed the backbone and enhanced the efficiency of the AACS Unit in the Mission Operations Spacecraft Team. These same tools, and extensions thereof, have been adopted by the Galileo mission operations, and are being designed into Cassini and other future spacecraft mission operations.

  7. Spacelab Payload Operations Control Center (POCC) Control Room During STS-35 Mission

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Due to loss of data used for pointing and operating the ultraviolet telescopes, MSFC ground teams were forced to aim the telescopes with fine tuning by the flight crew. This photo is an overview of the MSFC Payload Control Room (PCR).

  8. Spacelab Payload Operations Control Center (POCC) Control Room During STS-35 Mission

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Due to loss of data used for pointing and operating the ultraviolet telescopes, MSFC ground teams were forced to aim the telescopes with fine tuning by the flight crew. This photo is an overview of the MSFC Payload Control Room (PCR).

  9. Autonomous mission operations

    NASA Astrophysics Data System (ADS)

    Frank, J.; Spirkovska, L.; McCann, R.; Wang, Lui; Pohlkamp, K.; Morin, L.

    NASA's Advanced Exploration Systems Autonomous Mission Operations (AMO) project conducted an empirical investigation of the impact of time delay on today's mission operations, and of the effect of processes and mission support tools designed to mitigate time-delay related impacts. Mission operation scenarios were designed for NASA's Deep Space Habitat (DSH), an analog spacecraft habitat, covering a range of activities including nominal objectives, DSH system failures, and crew medical emergencies. The scenarios were simulated at time delay values representative of Lunar (1.2-5 sec), Near Earth Object (NEO) (50 sec) and Mars (300 sec) missions. Each combination of operational scenario and time delay was tested in a Baseline configuration, designed to reflect present-day operations of the International Space Station, and a Mitigation configuration in which a variety of software tools, information displays, and crew-ground communications protocols were employed to assist both crews and Flight Control Team (FCT) members with the long-delay conditions. Preliminary findings indicate: 1) Workload of both crewmembers and FCT members generally increased along with increasing time delay. 2) Advanced procedure execution viewers, caution and warning tools, and communications protocols such as text messaging decreased the workload of both flight controllers and crew, and decreased the difficulty of coordinating activities. 3) Whereas crew workload ratings increased between 50 sec and 300 sec of time delay in the Baseline configuration, workload ratings decreased (or remained flat) in the Mitigation configuration.

  10. Autonomous Mission Operations Roadmap

    NASA Technical Reports Server (NTRS)

    Frank, Jeremy David

    2014-01-01

    As light time delays increase, the number of such situations in which crew autonomy is the best way to conduct the mission is expected to increase. However, there are significant open questions regarding which functions to allocate to ground and crew as the time delays increase. In situations where the ideal solution is to allocate responsibility to the crew and the vehicle, a second question arises: should the activity be the responsibility of the crew or an automated vehicle function? More specifically, we must answer the following questions: What aspects of mission operation responsibilities (Plan, Train, Fly) should be allocated to ground based or vehicle based planning, monitoring, and control in the presence of significant light-time delay between the vehicle and the Earth?How should the allocated ground based planning, monitoring, and control be distributed across the flight control team and ground system automation? How should the allocated vehicle based planning, monitoring, and control be distributed between the flight crew and onboard system automation?When during the mission should responsibility shift from flight control team to crew or from crew to vehicle, and what should the process of shifting responsibility be as the mission progresses? NASA is developing a roadmap of capabilities for Autonomous Mission Operations for human spaceflight. This presentation will describe the current state of development of this roadmap, with specific attention to in-space inspection tasks that crews might perform with minimum assistance from the ground.

  11. Developing a corss-project support system during mission operations: Deep Space 1 extended mission flight control

    NASA Technical Reports Server (NTRS)

    Scarffe, V. A.

    2002-01-01

    NASA is focusing on small, low-cost spacecraft for both planetary and earth science missions. Deep Space 1 (DS1) was the first mission to be launched by the NMP. The New Millennium Project (NMP) is designed to develop and test new technology that can be used on future science missions with lower cost and risk. The NMP is finding ways to reduce cost not only in development, but also in operations. DS 1 was approved for an extended mission, but the budget was not large, so the project began looking into part time team members shared with other projects. DS1 launched on October 24, 1998, in it's primary mission it successfully tested twelve new technologies. The extended mission started September 18, 1999 and ran through the encounter with Comet Borrelly on September 22,2001. The Flight Control Team (FCT) was one team that needed to use part time or multi mission people. Circumstances led to a situation where for the few months before the Borrelly encounter in September of 2001 DSl had no certified full time Flight Control Engineers also known as Aces. This paper examines how DS 1 utilized cross-project support including the communication between different projects, and the how the tools used by the Flight Control Engineer fit into cross-project support.

  12. Mission Manager Area of the Spacelab Payload Operations Control Center (SL POCC)

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Pictured is Jack Jones in the Mission Manager Area.

  13. Command and Control of Joint Air Operations through Mission Command

    DTIC Science & Technology

    2016-06-01

    trust.”14 Such trust is mandatory for leading and executing in today’s complex global and geographically dispersed environments. To the joint force...those tactical-level commanders in the control and reporting center (CRC), Airborne Warning and Control System (AWACS), Marine air command and control

  14. An intelligent automated command and control system for spacecraft mission operations

    NASA Technical Reports Server (NTRS)

    Stoffel, A. William

    1994-01-01

    The Intelligent Command and Control (ICC) System research project is intended to provide the technology base necessary for producing an intelligent automated command and control (C&C) system capable of performing all the ground control C&C functions currently performed by Mission Operations Center (MOC) project Flight Operations Team (FOT). The ICC research accomplishments to date, details of the ICC, and the planned outcome of the ICC research, mentioned above, are discussed in detail.

  15. Mission operations management

    NASA Technical Reports Server (NTRS)

    Rocco, David A.

    1994-01-01

    Redefining the approach and philosophy that operations management uses to define, develop, and implement space missions will be a central element in achieving high efficiency mission operations for the future. The goal of a cost effective space operations program cannot be realized if the attitudes and methodologies we currently employ to plan, develop, and manage space missions do not change. A management philosophy that is in synch with the environment in terms of budget, technology, and science objectives must be developed. Changing our basic perception of mission operations will require a shift in the way we view the mission. This requires a transition from current practices of viewing the mission as a unique end product, to a 'mission development concept' built on the visualization of the end-to-end mission. To achieve this change we must define realistic mission success criteria and develop pragmatic approaches to achieve our goals. Custom mission development for all but the largest and most unique programs is not practical in the current budget environment, and we simply do not have the resources to implement all of our planned science programs. We need to shift our management focus to allow us the opportunity make use of methodologies and approaches which are based on common building blocks that can be utilized in the space, ground, and mission unique segments of all missions.

  16. IRIS Mission Operations Director's Colloquium

    NASA Technical Reports Server (NTRS)

    Carvalho, Robert; Mazmanian, Edward A.

    2014-01-01

    Pursuing the Mysteries of the Sun: The Interface Region Imaging Spectrograph (IRIS) Mission. Flight controllers from the IRIS mission will present their individual experiences on IRIS from development through the first year of flight. This will begin with a discussion of the unique nature of IRISs mission and science, and how it fits into NASA's fleet of solar observatories. Next will be a discussion of the critical roles Ames contributed in the mission including spacecraft and flight software development, ground system development, and training for launch. This will be followed by experiences from launch, early operations, ongoing operations, and unusual operations experiences. The presentation will close with IRIS science imagery and questions.

  17. Views of the Mission Operations Control room (MOCR) during STS-5

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Hans Mark, NASA Deputy Administrator, and Daniel M. Germany, Assistant Manager, Orbiter Project Office, monitor activity from STS-5 in the mission operations control room (MOCR) of JSC's mission control center. Arnold D. Aldrich, Manager of the Orbiter Project Office, can be seen at left background (27153); Gerald D. Griffin, JSC Director, stands near the flight director console in the MOCR. Astronaut Robert L. Stewart, STS-5 spacecraft communicator, mans the CAPCOM console at left. Others in the background include M.P. Frank, Chief of the Flight Operations Integration Office (back row); Eugene F. Kranz, Deputy Director of Flight Operations; Tommy W. Holloway, flight director (right of Griffin) (27154); Flight directors during STS-5 posed at the flight directors console are from left to right: Lawrence S. Bourgeois, Brock R. Stone, Jay H. Greene, Tommy W. Holloway, John T. Cox and Gary E. Coen. Other flight controllers are pictured in the background of the MOCR (27155).

  18. Low Cost Mission Operations Workshop. [Space Missions

    NASA Technical Reports Server (NTRS)

    1994-01-01

    The presentations given at the Low Cost (Space) Mission Operations (LCMO) Workshop are outlined. The LCMO concepts are covered in four introductory sections: Definition of Mission Operations (OPS); Mission Operations (MOS) Elements; The Operations Concept; and Mission Operations for Two Classes of Missions (operationally simple and complex). Individual presentations cover the following topics: Science Data Processing and Analysis; Mis sion Design, Planning, and Sequencing; Data Transport and Delivery, and Mission Coordination and Engineering Analysis. A list of panelists who participated in the conference is included along with a listing of the contact persons for obtaining more information concerning LCMO at JPL. The presentation of this document is in outline and graphic form.

  19. NEAR Shoemaker spacecraft mission operations

    NASA Astrophysics Data System (ADS)

    Holdridge, Mark E.

    2002-01-01

    On 12 February 2001, Near Earth Asteroid Rendezvous (NEAR) Shoemaker became the first spacecraft to land on a small body, 433 Eros. Prior to that historic event, NEAR was the first-ever orbital mission about an asteroid. The mission presented general challenges associated with other planetary space missions as well as challenges unique to an inaugural mission around a small body. The NEAR team performed this operations feat with processes and tools developed during the 4-year-long cruise to Eros. Adding to the success of this historic mission was the cooperation among the NEAR science, navigation, guidance and control, mission design, and software teams. With clearly defined team roles, overlaps in responsibilities were minimized, as were the associated costs. This article discusses the processes and systems developed at APL that enabled the success of NEAR mission operations.

  20. SPOT satellite family: Past, present, and future of the operations in the mission and control center

    NASA Technical Reports Server (NTRS)

    Philippe, Pacholczyk

    1993-01-01

    SPOT sun-synchronous remote sensing satellites are operated by CNES since February 1986. Today, the SPOT mission and control center (CCM) operates SPOT1, SPOT2, and is ready to operate SPOT3. During these seven years, the way to operate changed and the CCM, initially designed for the control of one satellite, has been modified and upgraded to support these new operating modes. All these events have shown the performances and the limits of the system. A new generation of satellite (SPOT4) will continue the remote sensing mission during the second half of the 90's. Its design takes into account the experience of the first generation and supports several improvements. A new generation of control center (CMP) has been developed and improves the efficiency, quality, and reliability of the operations. The CMP is designed for operating two satellites at the same time during launching, in-orbit testing, and operating phases. It supports several automatic procedures and improves data retrieval and reporting.

  1. Leadership Challenges in ISS Operations: Lessons Learned from Junior and Senior Mission Control Personnel

    NASA Technical Reports Server (NTRS)

    Clement, James L.; Ritsher, Jennifer Boyd; Saylor, Stephanie A.; Kanas, Nick

    2006-01-01

    The International Space Station (ISS) is operated by a multi-national, multi-organizational team that is dispersed across multiple locations, time zones, and work schedules. At NASA, both junior and senior mission control personnel have had to find ways to address the leadership challenges inherent in such work, but neither have had systematic training in how to do so. The goals of this study were to examine the major leadership challenges faced by ISS mission control personnel and to highlight the approaches that they have found most effective to surmount them. We pay particular attention to the approaches successfully employed by the senior personnel and to the training needs identified by the junior personnel. We also evaluate the extent to which responses are consistent across the junior and senior samples. Further, we compare the issues identified by our interview survey to those identified by a standardized questionnaire survey of mission control personnel and a contrasting group of space station crewmembers. We studied a sample of 14 senior ISS flight controllers and a contrasting sample of 12 more junior ISS controllers. Data were collected using a semi-structured qualitative interview and content analyzed using an iterative process with multiple coders and consensus meetings to resolve discrepancies. To further explore the meaning of the interview findings, we also conducted new analyses of data from a previous questionnaire study of 13 American astronauts, 17 Russian cosmonauts, and 150 U.S. and 36 Russian mission control personnel supporting the ISS or Mir space stations. The interview data showed that the survey respondents had substantial consensus on several leadership challenges and on key strategies for dealing with them, and they offered a wide range of specific tactics for implementing these strategies. Interview data from the junior respondents will be presented for the first time at the meeting. The questionnaire data showed that the US mission

  2. Leadership Challenges in ISS Operations: Lessons Learned from Junior and Senior Mission Control Personnel

    NASA Technical Reports Server (NTRS)

    Clement, James L.; Ritsher, Jennifer Boyd; Saylor, Stephanie A.; Kanas, Nick

    2006-01-01

    The International Space Station (ISS) is operated by a multi-national, multi-organizational team that is dispersed across multiple locations, time zones, and work schedules. At NASA, both junior and senior mission control personnel have had to find ways to address the leadership challenges inherent in such work, but neither have had systematic training in how to do so. The goals of this study were to examine the major leadership challenges faced by ISS mission control personnel and to highlight the approaches that they have found most effective to surmount them. We pay particular attention to the approaches successfully employed by the senior personnel and to the training needs identified by the junior personnel. We also evaluate the extent to which responses are consistent across the junior and senior samples. Further, we compare the issues identified by our interview survey to those identified by a standardized questionnaire survey of mission control personnel and a contrasting group of space station crewmembers. We studied a sample of 14 senior ISS flight controllers and a contrasting sample of 12 more junior ISS controllers. Data were collected using a semi-structured qualitative interview and content analyzed using an iterative process with multiple coders and consensus meetings to resolve discrepancies. To further explore the meaning of the interview findings, we also conducted new analyses of data from a previous questionnaire study of 13 American astronauts, 17 Russian cosmonauts, and 150 U.S. and 36 Russian mission control personnel supporting the ISS or Mir space stations. The interview data showed that the survey respondents had substantial consensus on several leadership challenges and on key strategies for dealing with them, and they offered a wide range of specific tactics for implementing these strategies. Interview data from the junior respondents will be presented for the first time at the meeting. The questionnaire data showed that the US mission

  3. Activities in the Payload Operations Control Center at MSFC During the IML-1 Mission

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This photograph shows activities during the International Microgravity Laboratory-1 (IML-1) mission (STS-42) in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center. Members of the Fluid Experiment System (FES) group monitor the progress of their experiment through video at the POCC. The IML-1 mission was the first in a series of Shuttle flights dedicated to fundamental materials and life sciences research. The mission was to explore, in depth, the complex effects of weightlessness on living organisms and materials processing. The crew conducted experiments on the human nervous system's adaptation to low gravity and the effects on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Low gravity materials processing experiments included crystal growth from a variety of substances such as enzymes, mercury, iodine, and virus. The International space science research organizations that participated in this mission were: The U.S. National Aeronautics and Space Administion, the European Space Agency, the Canadian Space Agency, the French National Center for Space Studies, the German Space Agency, and the National Space Development Agency of Japan. The POCC was the air/ground communication charnel used between astronauts aboard the Spacelab and scientists, researchers, and ground control teams during the Spacelab missions. The facility made instantaneous video and audio communications possible for scientists on the ground to follow the progress and to send direct commands of their research almost as if they were in space with the crew.

  4. Activities in the Payload Operation Control Center at MSFC During the IML-1 Mission

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This photograph shows activities during the International Microgravity Laboratory-1 (IML-1) mission (STS-42) in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center. The IML-1 mission was the first in a series of Shuttle flights dedicated to fundamental materials and life sciences research. The mission was to explore, in depth, the complex effects of weightlessness on living organisms and materials processing. The crew conducted experiments on the human nervous system's adaptation to low gravity and the effects on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Low gravity materials processing experiments included crystal growth from a variety of substances such as enzymes, mercury, iodine, and virus. The International space science research organizations that participated in this mission were: The U.S. National Aeronautics and Space Administration, the European Space Agency, the Canadian Space Agency, the French National Center for Space Studies, the German Space Agency, and the National Space Development Agency of Japan. The POCC was the air/ground communication charnel used between the astronauts aboard the Spacelab and scientists, researchers, and ground control teams during the Spacelab missions. The facility made instantaneous video and audio communications possible for scientists on the ground to follow the progress and to send direct commands of their research almost as if they were in space with the crew.

  5. Activities in the Payload Operation Control Center at MSFC During the IML-1 Mission

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This photograph shows activities during the International Microgravity Laboratory-1 (IML-1) mission (STS-42) in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center. The IML-1 mission was the first in a series of Shuttle flights dedicated to fundamental materials and life sciences research. The mission was to explore, in depth, the complex effects of weightlessness on living organisms and materials processing. The crew conducted experiments on the human nervous system's adaptation to low gravity and the effects on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Low gravity materials processing experiments included crystal growth from a variety of substances such as enzymes, mercury, iodine, and virus. The International space science research organizations that participated in this mission were: The U.S. National Aeronautics and Space Administration, the European Space Agency, the Canadian Space Agency, the French National Center for Space Studies, the German Space Agency, and the National Space Development Agency of Japan. The POCC was the air/ground communication charnel used between the astronauts aboard the Spacelab and scientists, researchers, and ground control teams during the Spacelab missions. The facility made instantaneous video and audio communications possible for scientists on the ground to follow the progress and to send direct commands of their research almost as if they were in space with the crew.

  6. Activities in the Payload Operations Control Center at MSFC During the IML-1 Mission

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This photograph shows activities during the International Microgravity Laboratory-1 (IML-1) mission (STS-42) in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center. Members of the Fluid Experiment System (FES) group monitor the progress of their experiment through video at the POCC. The IML-1 mission was the first in a series of Shuttle flights dedicated to fundamental materials and life sciences research. The mission was to explore, in depth, the complex effects of weightlessness on living organisms and materials processing. The crew conducted experiments on the human nervous system's adaptation to low gravity and the effects on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Low gravity materials processing experiments included crystal growth from a variety of substances such as enzymes, mercury, iodine, and virus. The International space science research organizations that participated in this mission were: The U.S. National Aeronautics and Space Administion, the European Space Agency, the Canadian Space Agency, the French National Center for Space Studies, the German Space Agency, and the National Space Development Agency of Japan. The POCC was the air/ground communication charnel used between astronauts aboard the Spacelab and scientists, researchers, and ground control teams during the Spacelab missions. The facility made instantaneous video and audio communications possible for scientists on the ground to follow the progress and to send direct commands of their research almost as if they were in space with the crew.

  7. Leadership challenges in ISS operations: Lessons learned from junior and senior mission control personnel

    NASA Astrophysics Data System (ADS)

    Clement, James L.; Boyd, Jennifer E.; Kanas, Nick; Saylor, Stephanie

    2007-06-01

    The International Space Station (ISS) is operated by a multi-national, multi-organizational team that is dispersed across multiple locations, time zones, and work schedules. At NASA, mission control personnel have had to find ways to address the leadership challenges inherent in such work, but have not had systematic training on how to do so. We interviewed 12 junior controllers and 14 senior controllers to examine the major leadership challenges they face and to highlight the solutions that they have found most effective to surmount them. We compare the perspectives of the two groups. Further, we contextualize our survey results with new analyses of standardized questionnaire data from 186 mission control personnel and a contrasting group of 30 space station crewmembers. The interview data showed that respondents had substantial consensus on several leadership challenges and on key strategies for dealing with them, but junior and senior controllers' perspectives were different. The questionnaire data showed that the US mission control sample reported a level of support from their management that compared favorably to national norms. Although specific to space station personnel, our results are consistent with recent management, cultural, and aerospace research.

  8. Integrated mission management operations

    NASA Technical Reports Server (NTRS)

    1971-01-01

    Operations required to launch a modular space station and to provides sustaining ground operations for support of that orbiting station throughout its 10 year mission are studied. A baseline, incrementally manned program and attendent experiment program options are derived. In addition, features of the program that significantly effect initial development and early operating costs are identified, and their impact on the program is assessed. A preliminary design of the approved modular space station configuration is formulated.

  9. Activities During Spacelab-J Mission at Payload Operations and Control Center

    NASA Technical Reports Server (NTRS)

    1992-01-01

    The group of Japanese researchers of the Spacelab-J (SL-J) were thumbs-up in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center after the successful launch of Space Shuttle Orbiter Endeavour that carried their experiments. The SL-J was a joint mission of NASA and the National Space Development Agency of Japan (NASDA) utilizing a marned Spacelab module. The mission conducted microgravity investigations in materials and life sciences. Materials science investigations covered such fields as biotechnology, electronic materials, fluid dynamics and transport phenomena, glasses and ceramics, metals and alloys, and acceleration measurements. Life sciences included experiments on human health, cell separation and biology, developmental biology, animal and human physiology and behavior, space radiation, and biological rhythms. Test subjects included the crew, Japanese koi fish (carp), cultured animal and plant cells, chicken embryos, fruit flies, fungi and plant seeds, frogs, and frog eggs. The POCC was the air/ground communications channel between the astronauts and ground control teams during the Spacelab missions. The Spacelab science operations were a cooperative effort between the science astronaut crew in orbit and their colleagues in the POCC. Spacelab-J was launched aboard the Space Shuttle Orbiter Endeavour on September 12, 1992.

  10. Rosetta mission operations for landing

    NASA Astrophysics Data System (ADS)

    Accomazzo, Andrea; Lodiot, Sylvain; Companys, Vicente

    2016-08-01

    The International Rosetta Mission of the European Space Agency (ESA) was launched on 2nd March 2004 on its 10 year journey to comet Churyumov-Gerasimenko and has reached it early August 2014. The main mission objectives were to perform close observations of the comet nucleus throughout its orbit around the Sun and deliver the lander Philae to its surface. This paper describers the activities at mission operations level that allowed the landing of Philae. The landing preparation phase was mainly characterised by the definition of the landing selection process, to which several parties contributed, and by the definition of the strategy for comet characterisation, the orbital strategy for lander delivery, and the definition and validation of the operations timeline. The definition of the landing site selection process involved almost all components of the mission team; Rosetta has been the first, and so far only mission, that could not rely on data collected by previous missions for the landing site selection. This forced the teams to include an intensive observation campaign as a mandatory part of the process; several science teams actively contributed to this campaign thus making results from science observations part of the mandatory operational products. The time allocated to the comet characterisation phase was in the order of a few weeks and all the processes, tools, and interfaces required an extensive planning an validation. Being the descent of Philae purely ballistic, the main driver for the orbital strategy was the capability to accurately control the position and velocity of Rosetta at Philae's separation. The resulting operations timeline had to merge this need of frequent orbit determination and control with the complexity of the ground segment and the inherent risk of problems when doing critical activities in short times. This paper describes the contribution of the Mission Control Centre (MOC) at the European Space Operations Centre (ESOC) to this

  11. STS-3 FLIGHT DAY 1 ACTIVITIES - MISSION OPERATIONS CONTROL ROOM (MOCR) - JSC

    NASA Image and Video Library

    1982-03-22

    MOCR during Flight Day 1 of the STS-3 Mission. View: Thomas L. Moser, of the Structures and Mechanics Division, briefing Flight Director Eugene Kranz, Flight Operations, and Dr. Kraft, JSC Director. JSC, HOUSTON, TX

  12. The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

    NASA Technical Reports Server (NTRS)

    Dittermore, Gary; Bertels, Christie

    2011-01-01

    Operations of human spaceflight systems is extremely complex; therefore, the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center in Houston, Texas, manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. An overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified, reveals that while the training methodology for developing flight controllers has evolved significantly over the last thirty years the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. Changes in methodology and tools have been driven by many factors, including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers share their experiences in training and operating the space shuttle. The primary training method throughout the program has been mission simulations of the orbit, ascent, and entry phases, to truly train like you fly. A review of lessons learned from flight controller training suggests how they could be applied to future human spaceflight endeavors, including missions to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle.

  13. Discovery Planetary Mission Operations Concepts

    NASA Technical Reports Server (NTRS)

    Coffin, R.

    1994-01-01

    The NASA Discovery Program of small planetary missions will provide opportunities to continue scientific exploration of the solar system in today's cost-constrained environment. Using a multidisciplinary team, JPL has developed plans to provide mission operations within the financial parameters established by the Discovery Program. This paper describes experiences and methods that show promise of allowing the Discovery Missions to operate within the program cost constraints while maintaining low mission risk, high data quality, and reponsive operations.

  14. Nuclear Electric Propulsion mission operations.

    NASA Technical Reports Server (NTRS)

    Prickett, W. Z.; Spera, R. J.

    1972-01-01

    Mission operations are presented for comet rendezvous and outer planet exploration missions conducted by unmanned Nuclear Electric Propulsion (NEP) system employing in-core thermionic reactors for electric power generation. The selected reference mission are Comet Halley rendezvous and a Jupiter orbiter at 5.9 planet radii, the orbit of the moon Io. Mission operations and options are defined from spacecraft assembly through mission completion. Pre-launch operations and related GSE requirements are identified. Shuttle launch and subsequent injection to earth escape by the Centaur d-1T are discussed, as well as power plant startup and heliocentric mission phases.

  15. Mission Operations Insights

    NASA Technical Reports Server (NTRS)

    Littman, Dave; Parksinson, Lou

    2006-01-01

    The mission description Polar Operational Environmental Satellites (POES): I) Collect and disseminate worldwide meteorological and environmental data: a) Provide day and night information (AVHRR): 1) cloud cover distribution and type; 2) cloud top temperature; 3) Moisture patterns and ice/snow melt. b) Provide vertical temperature and moisture profiles of atmospheres (HIRS, AMSU, MHS. c) Measure global ozone distribution and solar UV radiation (SBUV). d) Measure proton, electro, and charged particle density to provide solar storm warnings (SEM). d) Collect environmental data (DCS): 1) Stationary platforms in remote locations; 2) Free floating platforms on buoys, balloons, migratory animals. II) Provide Search and Rescue capabilities (SARR, SARP): a) Detection and relay of distress signals. b) Has saved thousands of lives around the world.

  16. Enhancing the ACE control center for the multiple uses of spacecraft integration and test and mission and science operations

    NASA Technical Reports Server (NTRS)

    Snow, Frank; Garrard, Thomas L.; Steck, Jane A.; Maury, Jesse L.

    1996-01-01

    In relation to the mandate to reduce space mission development and operations costs, the advanced composition explorer (ACE) will use a version of the Transportable Payload Operations Control Center (TPOCC) for its mission operations. It was determined during the phase B of the ACE project that a potential existed for substantial savings if the adaptation of the TPOCC for the ACE mission operations could include its adaptation for use as the primary component in the ground support equipment for the integration and testing of the ACE spacecraft, and for use as the basic component in the ACE science center. The implementation of this approach required the enhancement of the TPOCC requirements, changes in the development schedule and changes in the allocation and activities of the personnel responsible for the development of ACE operations. It is discussed how these issues, and the problems that arose, were addressed.

  17. The Virtual Mission Operations Center

    NASA Technical Reports Server (NTRS)

    Moore, Mike; Fox, Jeffrey

    1994-01-01

    Spacecraft management is becoming more human intensive as spacecraft become more complex and as operations costs are growing accordingly. Several automation approaches have been proposed to lower these costs. However, most of these approaches are not flexible enough in the operations processes and levels of automation that they support. This paper presents a concept called the Virtual Mission Operations Center (VMOC) that provides highly flexible support for dynamic spacecraft management processes and automation. In a VMOC, operations personnel can be shared among missions, the operations team can change personnel and their locations, and automation can be added and removed as appropriate. The VMOC employs a form of on-demand supervisory control called management by exception to free operators from having to actively monitor their system. The VMOC extends management by exception, however, so that distributed, dynamic teams can work together. The VMOC uses work-group computing concepts and groupware tools to provide a team infrastructure, and it employs user agents to allow operators to define and control system automation.

  18. COMS normal operation for Earth Observation mission

    NASA Astrophysics Data System (ADS)

    Cho, Young-Min

    2012-09-01

    Communication Ocean Meteorological Satellite (COMS) for the hybrid mission of meteorological observation, ocean monitoring, and telecommunication service was launched onto Geostationary Earth Orbit on June 27, 2010 and it is currently under normal operation service since April 2011. The COMS is located on 128.2° East of the geostationary orbit. In order to perform the three missions, the COMS has 3 separate payloads, the meteorological imager (MI), the Geostationary Ocean Color Imager (GOCI), and the Ka-band antenna. Each payload is dedicated to one of the three missions, respectively. The MI and GOCI perform the Earth observation mission of meteorological observation and ocean monitoring, respectively. For this Earth observation mission the COMS requires daily mission commands from the satellite control ground station and daily mission is affected by the satellite control activities. For this reason daily mission planning is required. The Earth observation mission operation of COMS is described in aspects of mission operation characteristics and mission planning for the normal operation services of meteorological observation and ocean monitoring. And the first year normal operation results after the In-Orbit-Test (IOT) are investigated through statistical approach to provide the achieved COMS normal operation status for the Earth observation mission.

  19. The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

    NASA Technical Reports Server (NTRS)

    Dittemore, Gary D.; Bertels, Christie

    2010-01-01

    This paper will summarize the thirty-year history of Space Shuttle operations from the perspective of training in NASA Johnson Space Center's Mission Control Center. It will focus on training and development of flight controllers and instructors, and how training practices have evolved over the years as flight experience was gained, new technologies developed, and programmatic needs changed. Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The audience will learn what it is like to perform a simulation as a shuttle flight controller. Finally, we will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors.

  20. Modeling Real-Time Coordination of Distributed Expertise and Event Response in NASA Mission Control Center Operations

    NASA Astrophysics Data System (ADS)

    Onken, Jeffrey

    This dissertation introduces a multidisciplinary framework for the enabling of future research and analysis of alternatives for control centers for real-time operations of safety-critical systems. The multidisciplinary framework integrates functional and computational models that describe the dynamics in fundamental concepts of previously disparate engineering and psychology research disciplines, such as group performance and processes, supervisory control, situation awareness, events and delays, and expertise. The application in this dissertation is the real-time operations within the NASA Mission Control Center in Houston, TX. This dissertation operationalizes the framework into a model and simulation, which simulates the functional and computational models in the framework according to user-configured scenarios for a NASA human-spaceflight mission. The model and simulation generates data according to the effectiveness of the mission-control team in supporting the completion of mission objectives and detecting, isolating, and recovering from anomalies. Accompanying the multidisciplinary framework is a proof of concept, which demonstrates the feasibility of such a framework. The proof of concept demonstrates that variability occurs where expected based on the models. The proof of concept also demonstrates that the data generated from the model and simulation is useful for analyzing and comparing MCC configuration alternatives because an investigator can give a diverse set of scenarios to the simulation and the output compared in detail to inform decisions about the effect of MCC configurations on mission operations performance.

  1. Mission Control Operations: Employing a New High Performance Design for Communications Links Supporting Exploration Programs

    NASA Technical Reports Server (NTRS)

    Jackson, Dan E., Jr.

    2015-01-01

    The planetary exploration programs demand a totally new examination of data multiplexing, digital communications protocols and data transmission principles for both ground and spacecraft operations. Highly adaptive communications devices on-board and on the ground must provide the greatest possible transmitted data density between deployed crew personnel, spacecraft and ground control teams. Regarding these requirements, this proposal borrows from research into quantum mechanical computing by applying the concept of a qubit, a single bit that represents 16 states, to radio frequency (RF) communications link design for exploration programs. This concept of placing multiple character values into a single data bit can easily make the evolutionary steps needed to meet exploration mission demands. To move the qubit from the quantum mechanical research laboratory into long distance RF data transmission, this proposal utilizes polarization modulation of the RF carrier signal to represent numbers from zero to fifteen. It introduces the concept of a binary-to-hexadecimal converter that quickly chops any data stream into 16-bit words and connects variously polarized feedhorns to a single-frequency radio transmitter. Further, the concept relies on development of a receiver that uses low-noise amplifiers and an antenna array to quickly assess carrier polarity and perform hexadecimal to binary conversion. Early testbed experiments using the International Space Station (ISS) as an operations laboratory can be implemented to provide the most cost-effective return for research investment. The improvement in signal-to-noise ratio while supporting greater baseband data rates that could be achieved through this concept justifies its consideration for long-distance exploration programs.

  2. The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

    NASA Technical Reports Server (NTRS)

    Dittemore, Gary D.

    2011-01-01

    Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The reader will learn what it is like to perform a simulation as a shuttle flight controller. Finally, the paper will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors. These endeavors could range from going to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle and inspire the next generation of space explorers.

  3. Soviet Mission Control Center

    NASA Technical Reports Server (NTRS)

    2003-01-01

    This photo is an overall view of the Mission Control Center in Korolev, Russia during the Expedition Seven mission. The Expedition Seven crew launched aboard a Soyez spacecraft on April 26, 2003. Photo credit: NASA/Bill Ingalls

  4. Soviet Mission Control Center

    NASA Technical Reports Server (NTRS)

    2003-01-01

    This photo is an overall view of the Mission Control Center in Korolev, Russia during the Expedition Seven mission. The Expedition Seven crew launched aboard a Soyez spacecraft on April 26, 2003. Photo credit: NASA/Bill Ingalls

  5. MISSION CONTROL CENTER (MCC) - CELEBRATION - CONCLUSION - APOLLO 11 MISSION - MSC

    NASA Image and Video Library

    1969-07-25

    S69-40023 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), showing the flight controllers celebrating the successful conclusion of the Apollo 11 lunar landing mission.

  6. Mission management aircraft operations manual

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This manual prescribes the NASA mission management aircraft program and provides policies and criteria for the safe and economical operation, maintenance, and inspection of NASA mission management aircraft. The operation of NASA mission management aircraft is based on the concept that safety has the highest priority. Operations involving unwarranted risks will not be tolerated. NASA mission management aircraft will be designated by the Associate Administrator for Management Systems and Facilities. NASA mission management aircraft are public aircraft as defined by the Federal Aviation Act of 1958. Maintenance standards, as a minimum, will meet those required for retention of Federal Aviation Administration (FAA) airworthiness certification. Federal Aviation Regulation Part 91, Subparts A and B, will apply except when requirements of this manual are more restrictive.

  7. The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

    NASA Technical Reports Server (NTRS)

    Dittemore, Gary D.; Bertels, Christie

    2011-01-01

    Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. As the space shuttle program ends in 2011, a review of how training for STS-1 was conducted compared to STS-134 will show multiple changes in training of shuttle flight controller over a thirty year period. This paper will additionally give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams have been trained certified over the life span of the space shuttle. The training methods for developing flight controllers have evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The reader will learn what it is like to perform a simulation as a shuttle flight controller. Finally, the paper will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors.

  8. Mission Control, 1964

    NASA Image and Video Library

    2016-10-27

    This archival image was released as part of a gallery comparing JPL's past and present, commemorating the 80th anniversary of NASA's Jet Propulsion Laboratory on Oct. 31, 2016. When spacecraft in deep space "phone home," they do it through NASA's Deep Space Network. Engineers in this room at NASA's Jet Propulsion Laboratory -- known as Mission Control -- monitor the flow of data. This image was taken in May 1964, when the building this nerve center is in, the Space Flight Operations Facility (Building 230), was dedicated at JPL. http://photojournal.jpl.nasa.gov/catalog/PIA21120

  9. ISS Update: Autonomous Mission Operations

    NASA Image and Video Library

    NASA Public Affairs Officer Brandi Dean interviews Jeff Mauldin, Simulation Supervisor for Autonomous Mission Operations at Johnson Space Center in Houston, Texas. Ask us on Twitter @NASA_Johnson a...

  10. View of Mission Control during Apollo 9 earth orbital mission

    NASA Image and Video Library

    1969-03-03

    S69-26301 (March 1969) --- Overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, during the Apollo 9 Earth-orbital mission. When this photograph was taken a live television transmission was being received from Apollo 9 as it orbited Earth.

  11. Mission operations for Astronomy Spacelab Payloads

    NASA Technical Reports Server (NTRS)

    Osler, S. J.

    1975-01-01

    An overview is provided of mission operations for Astronomy Spacelab Payloads. Missions considered are related to solar physics, high energy astrophysics, and stellar ultraviolet/optical astronomy. Operational aspects are examined. Mission operations include the flight activities and associated ground support work for implementing the mission. The prelaunch activity will begin about a year before launch with the assignment of a mission operations manager.

  12. Mission operations computing systems evolution

    NASA Technical Reports Server (NTRS)

    Kurzhals, P. R.

    1981-01-01

    As part of its preparation for the operational Shuttle era, the Goddard Space Flight Center (GSFC) is currently replacing most of the mission operations computing complexes that have supported near-earth space missions since the late 1960's. Major associated systems include the Metric Data Facility (MDF) which preprocesses, stores, and forwards all near-earth satellite tracking data; the Orbit Computation System (OCS) which determines related production orbit and attitude information; the Flight Dynamics System (FDS) which formulates spacecraft attitude and orbit maneuvers; and the Command Management System (CMS) which handles mission planning, scheduling, and command generation and integration. Management issues and experiences for the resultant replacement process are driven by a wide range of possible future mission requirements, flight-critical system aspects, complex internal system interfaces, extensive existing applications software, and phasing to optimize systems evolution.

  13. Mission operations computing systems evolution

    NASA Technical Reports Server (NTRS)

    Kurzhals, P. R.

    1981-01-01

    As part of its preparation for the operational Shuttle era, the Goddard Space Flight Center (GSFC) is currently replacing most of the mission operations computing complexes that have supported near-earth space missions since the late 1960's. Major associated systems include the Metric Data Facility (MDF) which preprocesses, stores, and forwards all near-earth satellite tracking data; the Orbit Computation System (OCS) which determines related production orbit and attitude information; the Flight Dynamics System (FDS) which formulates spacecraft attitude and orbit maneuvers; and the Command Management System (CMS) which handles mission planning, scheduling, and command generation and integration. Management issues and experiences for the resultant replacement process are driven by a wide range of possible future mission requirements, flight-critical system aspects, complex internal system interfaces, extensive existing applications software, and phasing to optimize systems evolution.

  14. Advancing Autonomous Operations Technologies for NASA Missions

    NASA Technical Reports Server (NTRS)

    Cruzen, Craig; Thompson, Jerry Todd

    2013-01-01

    This paper discusses the importance of implementing advanced autonomous technologies supporting operations of future NASA missions. The ability for crewed, uncrewed and even ground support systems to be capable of mission support without external interaction or control has become essential as space exploration moves further out into the solar system. The push to develop and utilize autonomous technologies for NASA mission operations stems in part from the need to reduce operations cost while improving and increasing capability and safety. This paper will provide examples of autonomous technologies currently in use at NASA and will identify opportunities to advance existing autonomous technologies that will enhance mission success by reducing operations cost, ameliorating inefficiencies, and mitigating catastrophic anomalies.

  15. Lunar Surface Mission Operations Scenario and Considerations

    NASA Technical Reports Server (NTRS)

    Arnold, Larissa S.; Torney, Susan E.; Rask, John Doug; Bleisath, Scott A.

    2006-01-01

    Planetary surface operations have been studied since the last visit of humans to the Moon, including conducting analog missions. Mission Operations lessons from these activities are summarized. Characteristics of forecasted surface operations are compared to current human mission operations approaches. Considerations for future designs of mission operations are assessed.

  16. Mission control team structure and operational lessons learned from the 2009 and 2010 NASA desert RATS simulated lunar exploration field tests

    NASA Astrophysics Data System (ADS)

    Bell, Ernest R.; Badillo, Victor; Coan, David; Johnson, Kieth; Ney, Zane; Rosenbaum, Megan; Smart, Tifanie; Stone, Jeffry; Stueber, Ronald; Welsh, Daren; Guirgis, Peggy; Looper, Chris; McDaniel, Randall

    2013-10-01

    The NASA Desert Research and Technology Studies (Desert RATS) is an annual field test of advanced concepts, prototype hardware, and potential modes of operation to be used on human planetary surface space exploration missions. For the 2009 and 2010 NASA Desert RATS field tests, various engineering concepts and operational exercises were incorporated into mission timelines with the focus of the majority of daily operations being on simulated lunar geological field operations and executed in a manner similar to current Space Shuttle and International Space Station missions. The field test for 2009 involved a two week lunar exploration simulation utilizing a two-man rover. The 2010 Desert RATS field test took this two week simulation further by incorporating a second two-man rover working in tandem with the 2009 rover, as well as including docked operations with a Pressurized Excursion Module (PEM). Personnel for the field test included the crew, a mission management team, engineering teams, a science team, and the mission operations team. The mission operations team served as the core of the Desert RATS mission control team and included certified NASA Mission Operations Directorate (MOD) flight controllers, former flight controllers, and astronaut personnel. The backgrounds of the flight controllers were in the areas of Extravehicular Activity (EVA), onboard mechanical systems and maintenance, robotics, timeline planning (OpsPlan), and spacecraft communicator (Capcom). With the simulated EVA operations, mechanized operations (the rover), and expectations of replanning, these flight control disciplines were especially well suited for the execution of the 2009 and 2010 Desert RATS field tests. The inclusion of an operations team has provided the added benefit of giving NASA mission operations flight control personnel the opportunity to begin examining operational mission control techniques, team compositions, and mission scenarios. This also gave the mission operations

  17. Distributed science operations for JPL planetary missions

    NASA Technical Reports Server (NTRS)

    Benson, Richard D.; Kahn, Peter B.

    1993-01-01

    Advances in spacecraft, flight instruments, and ground systems provide an impetus and an opportunity for scientific investigation teams to take direct control of their instruments' operations and data collection while at the same time, providing a cost effective and flexible approach in support of increasingly complex science missions. Operations of science instruments have generally been integrated into planetary flight and ground systems at a very detailed level. That approach has been successful, but the cost of incorporating instrument expertise into the central mission operations system has been high. This paper discusses an approach to simplify planetary science operations by distributing instrument computing and data management tasks from the central mission operations system to each investigator's home center of observational expertise. Some early results of this operations concept will be presented based on the Mars Observer (MO) Project experience and Cassini Project plans.

  18. A Virtual Mission Operations Center: Collaborative Environment

    NASA Technical Reports Server (NTRS)

    Medina, Barbara; Bussman, Marie; Obenschain, Arthur F. (Technical Monitor)

    2002-01-01

    The Virtual Mission Operations Center - Collaborative Environment (VMOC-CE) intent is to have a central access point for all the resources used in a collaborative mission operations environment to assist mission operators in communicating on-site and off-site in the investigation and resolution of anomalies. It is a framework that as a minimum incorporates online chat, realtime file sharing and remote application sharing components in one central location. The use of a collaborative environment in mission operations opens up the possibilities for a central framework for other project members to access and interact with mission operations staff remotely. The goal of the Virtual Mission Operations Center (VMOC) Project is to identify, develop, and infuse technology to enable mission control by on-call personnel in geographically dispersed locations. In order to achieve this goal, the following capabilities are needed: Autonomous mission control systems Automated systems to contact on-call personnel Synthesis and presentation of mission control status and history information Desktop tools for data and situation analysis Secure mechanism for remote collaboration commanding Collaborative environment for remote cooperative work The VMOC-CE is a collaborative environment that facilitates remote cooperative work. It is an application instance of the Virtual System Design Environment (VSDE), developed by NASA Goddard Space Flight Center's (GSFC) Systems Engineering Services & Advanced Concepts (SESAC) Branch. The VSDE is a web-based portal that includes a knowledge repository and collaborative environment to serve science and engineering teams in product development. It is a "one stop shop" for product design, providing users real-time access to product development data, engineering and management tools, and relevant design specifications and resources through the Internet. The initial focus of the VSDE has been to serve teams working in the early portion of the system

  19. A Virtual Mission Operations Center: Collaborative Environment

    NASA Technical Reports Server (NTRS)

    Medina, Barbara; Bussman, Marie; Obenschain, Arthur F. (Technical Monitor)

    2002-01-01

    The Virtual Mission Operations Center - Collaborative Environment (VMOC-CE) intent is to have a central access point for all the resources used in a collaborative mission operations environment to assist mission operators in communicating on-site and off-site in the investigation and resolution of anomalies. It is a framework that as a minimum incorporates online chat, realtime file sharing and remote application sharing components in one central location. The use of a collaborative environment in mission operations opens up the possibilities for a central framework for other project members to access and interact with mission operations staff remotely. The goal of the Virtual Mission Operations Center (VMOC) Project is to identify, develop, and infuse technology to enable mission control by on-call personnel in geographically dispersed locations. In order to achieve this goal, the following capabilities are needed: Autonomous mission control systems Automated systems to contact on-call personnel Synthesis and presentation of mission control status and history information Desktop tools for data and situation analysis Secure mechanism for remote collaboration commanding Collaborative environment for remote cooperative work The VMOC-CE is a collaborative environment that facilitates remote cooperative work. It is an application instance of the Virtual System Design Environment (VSDE), developed by NASA Goddard Space Flight Center's (GSFC) Systems Engineering Services & Advanced Concepts (SESAC) Branch. The VSDE is a web-based portal that includes a knowledge repository and collaborative environment to serve science and engineering teams in product development. It is a "one stop shop" for product design, providing users real-time access to product development data, engineering and management tools, and relevant design specifications and resources through the Internet. The initial focus of the VSDE has been to serve teams working in the early portion of the system

  20. Apollo 13 - Mission Control Console

    NASA Image and Video Library

    1970-04-15

    S70-35096 (16 April 1970) --- As the problem-plagued Apollo 13 crewmen entered their final 24 hours in space, several persons important to the mission remained attentive at consoles in the Mission Operations Control Room of the Mission Control Center at Manned Spacecraft Center. Among those monitoring communications and serving in supervisory capacities were these four officials from National Aeronautics and Space Administration Headquarters, Washington, D.C.: (from left) Thomas H. McMullen, Office of Manned Space Flight, who served as Shift 1 mission director; Dale Myers, associate administrator, Manned Space Flight; Chester M. Lee of the Apollo Program Directorate, OMSF, Apollo 13 mission director; and Dr. Rocco A. Petrone, Apollo program director, OMSF.

  1. Mission Control Roses

    NASA Image and Video Library

    The 110th bouquet of roses arrived in Mission Control on Saturday, July 9, 2011. They were sent as quietly as they have been for more than 23 years by a family near Dallas, Texas. For 110 shuttle m...

  2. Flight Operations . [Zero Knowledge to Mission Complete

    NASA Technical Reports Server (NTRS)

    Forest, Greg; Apyan, Alex; Hillin, Andrew

    2016-01-01

    Outline the process that takes new hires with zero knowledge all the way to the point of completing missions in Flight Operations. Audience members should be able to outline the attributes of a flight controller and instructor, outline the training flow for flight controllers and instructors, and identify how the flight controller and instructor attributes are necessary to ensure operational excellence in mission prep and execution. Identify how the simulation environment is used to develop crisis management, communication, teamwork, and leadership skills for SGT employees beyond what can be provided by classroom training.

  3. Computer graphics aid mission operations. [NASA missions

    NASA Technical Reports Server (NTRS)

    Jeletic, James F.

    1990-01-01

    The application of computer graphics techniques in NASA space missions is reviewed. Telemetric monitoring of the Space Shuttle and its components is discussed, noting the use of computer graphics for real-time visualization problems in the retrieval and repair of the Solar Maximum Mission. The use of the world map display for determining a spacecraft's location above the earth and the problem of verifying the relative position and orientation of spacecraft to celestial bodies are examined. The Flight Dynamics/STS Three-dimensional Monitoring System and the Trajectroy Computations and Orbital Products System world map display are described, emphasizing Space Shuttle applications. Also, consideration is given to the development of monitoring systems such as the Shuttle Payloads Mission Monitoring System and the Attitude Heads-Up Display and the use of the NASA-Goddard Two-dimensional Graphics Monitoring System during Shuttle missions and to support the Hubble Space Telescope.

  4. Mission Control Center (MCC) - Celebration - Conclusion - Apollo XI Mission - MSC

    NASA Image and Video Library

    1969-07-24

    S69-40301 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), at the conclusion of the Apollo 11 lunar landing mission. The television monitor shows President Richard M. Nixon greeting the Apollo 11 astronauts aboard the USS Hornet in the Pacific recovery area. Astronauts Neil A. Armstrong, Michael Collins, and Edwin E. Aldrin Jr. are inside the Mobile Quarantine Facility (MQF).

  5. Integrated payload and mission planning, phase 3. Volume 3: Ground real-time mission operations

    NASA Technical Reports Server (NTRS)

    White, W. J.

    1977-01-01

    The payloads tentatively planned to fly on the first two Spacelab missions were analyzed to examine the cost relationships of providing mission operations support from onboard vs the ground-based Payload Operations Control Center (POCC). The quantitative results indicate that use of a POCC, with data processing capability, to support real-time mission operations is the most cost effective case.

  6. Advancing Autonomous Operations Technologies for NASA Missions

    NASA Technical Reports Server (NTRS)

    Cruzen, Craig; Thompson, Jerry T.

    2013-01-01

    This paper discusses the importance of implementing advanced autonomous technologies supporting operations of future NASA missions. The ability for crewed, uncrewed and even ground support systems to be capable of mission support without external interaction or control has become essential as space exploration moves further out into the solar system. The push to develop and utilize autonomous technologies for NASA mission operations stems in part from the need to reduce cost while improving and increasing capability and safety. This paper will provide examples of autonomous technologies currently in use at NASA and will identify opportunities to advance existing autonomous technologies that will enhance mission success by reducing cost, ameliorating inefficiencies, and mitigating catastrophic anomalies

  7. Mission Operations with an Autonomous Agent

    NASA Technical Reports Server (NTRS)

    Pell, Barney; Sawyer, Scott R.; Muscettola, Nicola; Smith, Benjamin; Bernard, Douglas E.

    1998-01-01

    The Remote Agent (RA) is an Artificial Intelligence (AI) system which automates some of the tasks normally reserved for human mission operators and performs these tasks autonomously on-board the spacecraft. These tasks include activity generation, sequencing, spacecraft analysis, and failure recovery. The RA will be demonstrated as a flight experiment on Deep Space One (DSI), the first deep space mission of the NASA's New Millennium Program (NMP). As we moved from prototyping into actual flight code development and teamed with ground operators, we made several major extensions to the RA architecture to address the broader operational context in which PA would be used. These extensions support ground operators and the RA sharing a long-range mission profile with facilities for asynchronous ground updates; support ground operators monitoring and commanding the spacecraft at multiple levels of detail simultaneously; and enable ground operators to provide additional knowledge to the RA, such as parameter updates, model updates, and diagnostic information, without interfering with the activities of the RA or leaving the system in an inconsistent state. The resulting architecture supports incremental autonomy, in which a basic agent can be delivered early and then used in an increasingly autonomous manner over the lifetime of the mission. It also supports variable autonomy, as it enables ground operators to benefit from autonomy when L'@ey want it, but does not inhibit them from obtaining a detailed understanding and exercising tighter control when necessary. These issues are critical to the successful development and operation of autonomous spacecraft.

  8. Mission Control Center (MCC) - Apollo 8

    NASA Image and Video Library

    1968-12-25

    S68-56007 (23 Dec. 1968) --- Overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, on the third day of the Apollo 8 lunar orbit mission. Seen on the television monitor is a picture of Earth which was telecast from the Apollo 8 spacecraft 176,000 miles away.

  9. Mars Pathfinder mission operations concepts

    NASA Technical Reports Server (NTRS)

    Sturms, Francis M., Jr.; Dias, William C.; Nakata, Albert Y.; Tai, Wallace S.

    1994-01-01

    The Mars Pathfinder Project plans a December 1996 launch of a single spacecraft. After jettisoning a cruise stage, an entry body containing a lander and microrover will directly enter the Mars atmosphere and parachute to a hard landing near the sub-solar latitude of 15 degrees North in July 1997. Primary surface operations last for 30 days. Cost estimates for Pathfinder ground systems development and operations are not only lower in absolute dollars, but also are a lower percentage of total project costs than in past planetary missions. Operations teams will be smaller and fewer than typical flight projects. Operations scenarios have been developed early in the project and are being used to guide operations implementation and flight system design. Recovery of key engineering data from entry, descent, and landing is a top mission priority. These data will be recorded for playback after landing. Real-time tracking of a modified carrier signal through this phase can provide important insight into the spacecraft performance during entry, descent, and landing in the event recorded data is never recovered. Surface scenarios are dominated by microrover activity and lander imaging during 7 hours of the Mars day from 0700 to 1400 local solar time. Efficient uplink and downlink processes have been designed to command the lander and microrover each Mars day.

  10. Integrating Automation into a Multi-Mission Operations Center

    NASA Technical Reports Server (NTRS)

    Surka, Derek M.; Jones, Lori; Crouse, Patrick; Cary, Everett A, Jr.; Esposito, Timothy C.

    2007-01-01

    NASA Goddard Space Flight Center's Space Science Mission Operations (SSMO) Project is currently tackling the challenge of minimizing ground operations costs for multiple satellites that have surpassed their prime mission phase and are well into extended mission. These missions are being reengineered into a multi-mission operations center built around modern information technologies and a common ground system infrastructure. The effort began with the integration of four SMEX missions into a similar architecture that provides command and control capabilities and demonstrates fleet automation and control concepts as a pathfinder for additional mission integrations. The reengineered ground system, called the Multi-Mission Operations Center (MMOC), is now undergoing a transformation to support other SSMO missions, which include SOHO, Wind, and ACE. This paper presents the automation principles and lessons learned to date for integrating automation into an existing operations environment for multiple satellites.

  11. Satellite Mission Operations Best Practices

    NASA Technical Reports Server (NTRS)

    Galal, Ken; Hogan, Roger P. (Technical Monitor)

    2001-01-01

    The effort of compiling a collection of Best Practices for use in Space Mission Operations was initiated within a subcommittee of the American Institute of Aeronautics and Astronautics (AIAA) Space Operations and Support Technical Committee (SOSTC). The idea was to eventually post a collection of Best Practices on a website so as to make them available to the general Space Operations community. The effort of searching for available Best Practices began in the fall of 1999. As the search progressed, it became apparent that there were not many Best Practices developed that were available to the general community. Therefore, the subcommittee decided to use the SOSTC Annual Workshop on Reducing Space Mission Costs as a forum for developing Best Practices for our purpose of sharing them with a larger audience. A dedicated track at the April 2000 workshop was designed to stimulate discussions on developing such Best Practices and forming working groups made up of experienced people from various organizations to perform the development. These groups were solicited to help outside the workshop to bring this effort to fruition. Since that time, biweekly teleconferences have been held to discuss the development of the Best Practices and their posting.

  12. Reconfigurable Software for Mission Operations

    NASA Technical Reports Server (NTRS)

    Trimble, Jay

    2014-01-01

    We developed software that provides flexibility to mission organizations through modularity and composability. Modularity enables removal and addition of functionality through the installation of plug-ins. Composability enables users to assemble software from pre-built reusable objects, thus reducing or eliminating the walls associated with traditional application architectures and enabling unique combinations of functionality. We have used composable objects to reduce display build time, create workflows, and build scenarios to test concepts for lunar roving operations. The software is open source, and may be downloaded from https:github.comnasamct.

  13. A Conceptual Operational Model for Command and Control of International Missions in the Canadian Forces

    DTIC Science & Technology

    2002-09-01

    Description Capture Method Larry Cochran and Kendall Wheaton 4 IDEF3 is an appropriate method for use in the COP21 operational model because it captures the...with each element (Arrow entities and Box activities) is information that describes the entity or activity. The Modeling Process The COP21 Conceptual

  14. The Mission Operations Planning Assistant

    NASA Technical Reports Server (NTRS)

    Schuetzle, James G.

    1987-01-01

    The Mission Operations Planning Assistant (MOPA) is a knowledge-based system developed to support the planning and scheduling of instrument activities on the Upper Atmospheric Research Satellite (UARS). The MOPA system represents and maintains instrument plans at two levels of abstraction in order to keep plans comprehensible to both UARS Principal Investigators and Command Management personnel. The hierarchical representation of plans also allows MOPA to automatically create detailed instrument activity plans from which spacecraft command loads may be generated. The MOPA system was developed on a Symbolics 3640 computer using the ZetaLisp and ART languages. MOPA's features include a textual and graphical interface for plan inspection and modification, recognition of instrument operational constraint violations during the planning process, and consistency maintenance between the different planning levels. This paper describes the current MOPA system.

  15. STS payloads mission control study continuation phase A-1. Volume 2-C, task 3: Identification of joint activities and estimation of resources in preparation for joint flight operations

    NASA Technical Reports Server (NTRS)

    1976-01-01

    Payload mission control concepts are developed for real time flight operations of STS. Flight planning, training, simulations, and other flight preparations are included. Payload activities for the preflight phase, activity sequences and organizational allocations, and traffic and experience factors to establish composite man-loading for joint STS payload activities are identified for flight operations from 1980 to 1985.

  16. LST data management and mission operations concept. [pointing control optimization for maximum data

    NASA Technical Reports Server (NTRS)

    Walker, R.; Hudson, F.; Murphy, L.

    1977-01-01

    A candidate design concept for an LST ground facility is described. The design objectives were to use NASA institutional hardware, software and facilities wherever practical, and to maximize efficiency of telescope use. The pointing control performance requirements of LST are summarized, and the major data interfaces of the candidate ground system are diagrammed.

  17. The IRAS project organisation and mission operations

    NASA Technical Reports Server (NTRS)

    Van Holtz, R. C.

    1983-01-01

    The project organisation of IRAS is described, showing the tasks assigned to each project group during post-launch operations. The satellite is described, emphasizing the detectors. In the task division, the role of the U.S. is to construct the telescope and survey instrument, launch the satellite, process final science data for the survey instrument, and provide certain standard satellite items. The Netherlands construct the spacecraft and three additional instruments, integrates and tests the overall satellite, and designs and participates in the development of the operational system. The U.K. provides the operational control center and primary tracking station, generates a system for preliminary science analysis of the survey data, provides housekeeping analysis software and science data distribution software, and staffs the control center operations. The teams involved in mission planning and operations, and their roles, are identified, and a block diagram of the operations organisation is presented.

  18. Mission Operations Planning and Scheduling System (MOPSS)

    NASA Technical Reports Server (NTRS)

    Wood, Terri; Hempel, Paul

    2011-01-01

    MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.

  19. Operational Lessons Learned from NASA Analog Missions

    NASA Technical Reports Server (NTRS)

    Arnold, Larissa S.

    2010-01-01

    vehicle and system capabilities are required to support the activities? How will the crew and the Earth-based mission control team interact? During the initial phases of manned planetary exploration, one challenge in particular is virtually the same as during the Apollo program: How can scientific return be maximized during a relatively short surface mission? Today, NASA is investigating solutions to these challenges by conducting analog missions. These Earth-based missions possess characteristics that are analogous to missions on the Moon or Mars. These missions are excellent for testing operational concepts, and the design, configuration, and functionality of spacesuits, robots, rovers, and habitats. Analog mission crews test specific techniques and procedures for surface field geology, biological sample collection, and planetary protection. The process of actually working an analog mission reveals a myriad of small details, which either contribute to or impede efficient operations, many of which would never have been thought about otherwise. It also helps to define the suite of tools, containers, and other small equipment that surface explorers will use. This paper focuses on how analog missions have addressed selected operational considerations for future planetary missions.

  20. Hitchhiker mission operations: Past, present, and future

    NASA Technical Reports Server (NTRS)

    Anderson, Kathryn

    1995-01-01

    What is mission operations? Mission operations is an iterative process aimed at achieving the greatest possible mission success with the resources available. The process involves understanding of the science objectives, investigation of which system capabilities can best meet these objectives, integration of the objectives and resources into a cohesive mission operations plan, evaluation of the plan through simulations, and implementation of the plan in real-time. In this paper, the authors present a comprehensive description of what the Hitchhiker mission operations approach is and why it is crucial to mission success. The authors describe the significance of operational considerations from the beginning and throughout the experiment ground and flight systems development. The authors also address the necessity of training and simulations. Finally, the authors cite several examples illustrating the benefits of understanding and utilizing the mission operations process.

  1. Earth orbital operations supporting manned interplanetary missions

    NASA Astrophysics Data System (ADS)

    Sherwood, Brent; Buddington, Patricia A.; Whittaker, William L.

    The orbital operations required to accumulate, assemble, test, verify, maintain, and launch complex manned space systems on interplanetary missions from earth orbit are as vital as the flight hardware itself. Vast numbers of orbital crew are neither necessary nor desirable for accomplishing the required tasks. A suite of robotic techniques under human supervisory control, relying on sensors, software and manipulators either currently emergent or already applied in terrestrial settings, can make the job tractable. The mission vehicle becomes largely self-assembling, using its own rigid aerobrake as a work platform. The Space Station, having been used as a laboratory testbed and to house an assembly crew of four, is not dominated by the process. A feasible development schedule, if begun soon, could emplace orbital support technologies for exploration missions in time for a 2004 first interplanetary launch.

  2. Earth orbital operations supporting manned interplanetary missions

    NASA Technical Reports Server (NTRS)

    Sherwood, Brent; Buddington, Patricia A.; Whittaker, William L.

    1989-01-01

    The orbital operations required to accumulate, assemble, test, verify, maintain, and launch complex manned space systems on interplanetary missions from earth orbit are as vital as the flight hardware itself. Vast numbers of orbital crew are neither necessary nor desirable for accomplishing the required tasks. A suite of robotic techniques under human supervisory control, relying on sensors, software and manipulators either currently emergent or already applied in terrestrial settings, can make the job tractable. The mission vehicle becomes largely self-assembling, using its own rigid aerobrake as a work platform. The Space Station, having been used as a laboratory testbed and to house an assembly crew of four, is not dominated by the process. A feasible development schedule, if begun soon, could emplace orbital support technologies for exploration missions in time for a 2004 first interplanetary launch.

  3. Russian Mission Control Center

    NASA Image and Video Library

    2004-04-20

    Helen Conijn, fiancée of European Space Agency astronaut Andre Kuipers of the Netherlands, far right, joins Renita Fincke, second from right, wife of Expedition 9 Flight Engineer and NASA International Space Station Science Officer Michael Fincke, along with family members at the Russian Mission Control Center outside Moscow, Wednesday, April 21, 2004 to view the docking of the Soyuz capsule to the International Space Station that brought Kuipers, Fincke and Expedition 9 Commander Gennady Padalka to the complex following their launch Monday from Kazakhstan. Photo Credit: (NASA/Bill Ingalls)

  4. Infusion of innovative technologies for mission operations

    NASA Astrophysics Data System (ADS)

    Donati, Alessandro

    2010-11-01

    The Advanced Mission Concepts and Technologies Office (Mission Technologies Office, MTO for short) at the European Space Operations Centre (ESOC) of ESA is entrusted with research and development of innovative mission operations concepts systems and provides operations support to special projects. Visions of future missions and requests for improvements from currently flying missions are the two major sources of inspiration to conceptualize innovative or improved mission operations processes. They include monitoring and diagnostics, planning and scheduling, resource management and optimization. The newly identified operations concepts are then proved by means of prototypes, built with embedded, enabling technology and deployed as shadow applications in mission operations for an extended validation phase. The technology so far exploited includes informatics, artificial intelligence and operational research branches. Recent outstanding results include artificial intelligence planning and scheduling applications for Mars Express, advanced integrated space weather monitoring system for the Integral space telescope and a suite of growing client applications for MUST (Mission Utilities Support Tools). The research, development and validation activities at the Mission technologies office are performed together with a network of research institutes across Europe. The objective is narrowing the gap between enabling and innovative technology and space mission operations. The paper first addresses samples of technology infusion cases with their lessons learnt. The second part is focused on the process and the methodology used at the Mission technologies office to fulfill its objectives.

  5. Architectures for mission control at the Jet Propulsion Laboratory

    NASA Technical Reports Server (NTRS)

    Davidson, Reger A.; Murphy, Susan C.

    1992-01-01

    JPL is currently converting to an innovative control center data system which is a distributed, open architecture for telemetry delivery and which is enabling advancement towards improved automation and operability, as well as new technology, in mission operations at JPL. The scope of mission control within mission operations is examined. The concepts of a mission control center and how operability can affect the design of a control center data system are discussed. Examples of JPL's mission control architecture, data system development, and prototype efforts at the JPL Operations Engineering Laboratory are provided. Strategies for the future of mission control architectures are outlined.

  6. OTF Mission Operations Prototype Status

    NASA Technical Reports Server (NTRS)

    Reynolds, Walter F.; Lucord, Steven A.; Stevens, John E.

    2009-01-01

    Reports on the progress of the JSC/OTF prototype of a CCSDS SM&C protocol based communications link between two space flight operations control centers. Varied implementations using software architectures from current web enterprise venues are presented. The AMS protocol (CCSDS Blue Book standard 735.1) was used for messaging and link communications.

  7. Low Cost Missions Operations on NASA Deep Space Missions

    NASA Astrophysics Data System (ADS)

    Barnes, R. J.; Kusnierkiewicz, D. J.; Bowman, A.; Harvey, R.; Ossing, D.; Eichstedt, J.

    2014-12-01

    The ability to lower mission operations costs on any long duration mission depends on a number of factors; the opportunities for science, the flight trajectory, and the cruise phase environment, among others. Many deep space missions employ long cruises to their final destination with minimal science activities along the way; others may perform science observations on a near-continuous basis. This paper discusses approaches employed by two NASA missions implemented by the Johns Hopkins University Applied Physics Laboratory (JHU/APL) to minimize mission operations costs without compromising mission success: the New Horizons mission to Pluto, and the Solar Terrestrial Relations Observatories (STEREO). The New Horizons spacecraft launched in January 2006 for an encounter with the Pluto system.The spacecraft trajectory required no deterministic on-board delta-V, and so the mission ops team then settled in for the rest of its 9.5-year cruise. The spacecraft has spent much of its cruise phase in a "hibernation" mode, which has enabled the spacecraft to be maintained with a small operations team, and minimized the contact time required from the NASA Deep Space Network. The STEREO mission is comprised of two three-axis stabilized sun-staring spacecraft in heliocentric orbit at a distance of 1 AU from the sun. The spacecraft were launched in October 2006. The STEREO instruments operate in a "decoupled" mode from the spacecraft, and from each other. Since STEREO operations are largely routine, unattended ground station contact operations were implemented early in the mission. Commands flow from the MOC to be uplinked, and the data recorded on-board is downlinked and relayed back to the MOC. Tools run in the MOC to assess the health and performance of ground system components. Alerts are generated and personnel are notified of any problems. Spacecraft telemetry is similarly monitored and alarmed, thus ensuring safe, reliable, low cost operations.

  8. Calculation of Operations Efficiency Factors for Mars Surface Missions

    NASA Technical Reports Server (NTRS)

    Laubach, Sharon

    2014-01-01

    The duration of a mission--and subsequently, the minimum spacecraft lifetime--is a key component in designing the capabilities of a spacecraft during mission formulation. However, determining the duration is not simply a function of how long it will take the spacecraft to execute the activities needed to achieve mission objectives. Instead, the effects of the interaction between the spacecraft and ground operators must also be taken into account. This paper describes a method, using "operations efficiency factors", to account for these effects for Mars surface missions. Typically, this level of analysis has not been performed until much later in the mission development cycle, and has not been able to influence mission or spacecraft design. Further, the notion of moving to sustainable operations during Prime Mission--and the effect that change would have on operations productivity and mission objective choices--has not been encountered until the most recent rover missions (MSL, the (now-cancelled) joint NASA-ESA 2018 Mars rover, and the proposed rover for Mars 2020). Since MSL had a single control center and sun-synchronous relay assets (like MER), estimates of productivity derived from MER prime and extended missions were used. However, Mars 2018's anticipated complexity (there would have been control centers in California and Italy, and a non-sun-synchronous relay asset) required the development of an explicit model of operations efficiency that could handle these complexities. In the case of the proposed Mars 2018 mission, the model was employed to assess the mission return of competing operations concepts, and as an input to component lifetime requirements. In this paper we provide examples of how to calculate the operations efficiency factor for a given operational configuration, and how to apply the factors to surface mission scenarios. This model can be applied to future missions to enable early effective trades between operations design, science mission

  9. Calculation of Operations Efficiency Factors for Mars Surface Missions

    NASA Technical Reports Server (NTRS)

    Laubach, Sharon

    2014-01-01

    The duration of a mission--and subsequently, the minimum spacecraft lifetime--is a key component in designing the capabilities of a spacecraft during mission formulation. However, determining the duration is not simply a function of how long it will take the spacecraft to execute the activities needed to achieve mission objectives. Instead, the effects of the interaction between the spacecraft and ground operators must also be taken into account. This paper describes a method, using "operations efficiency factors", to account for these effects for Mars surface missions. Typically, this level of analysis has not been performed until much later in the mission development cycle, and has not been able to influence mission or spacecraft design. Further, the notion of moving to sustainable operations during Prime Mission--and the effect that change would have on operations productivity and mission objective choices--has not been encountered until the most recent rover missions (MSL, the (now-cancelled) joint NASA-ESA 2018 Mars rover, and the proposed rover for Mars 2020). Since MSL had a single control center and sun-synchronous relay assets (like MER), estimates of productivity derived from MER prime and extended missions were used. However, Mars 2018's anticipated complexity (there would have been control centers in California and Italy, and a non-sun-synchronous relay asset) required the development of an explicit model of operations efficiency that could handle these complexities. In the case of the proposed Mars 2018 mission, the model was employed to assess the mission return of competing operations concepts, and as an input to component lifetime requirements. In this paper we provide examples of how to calculate the operations efficiency factor for a given operational configuration, and how to apply the factors to surface mission scenarios. This model can be applied to future missions to enable early effective trades between operations design, science mission

  10. Long duration mission support operations concepts

    NASA Technical Reports Server (NTRS)

    Eggleston, T. W.

    1990-01-01

    It is suggested that the system operations will be one of the most expensive parts of the Mars mission, and that, in order to reduce their cost, they should be considered during the conceptual phase of the Space Exploration Initiative (SEI) program. System operations of Space Station Freedom, Lunar outpost, and Mars Rover Sample Return are examined in order to develop a similar concept for the manned Mars mission. Factors that have to be taken into account include: (1) psychological stresses caused by long periods of isolation; (2) the effects of boredom; (3) the necessity of onboard training to maintain a high level of crew skills; and (4) the 40-min time delays between issuing and receiving a command, which make real-time flight control inoperative and require long-term decisions to be made by the ground support.

  11. Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

    NASA Technical Reports Server (NTRS)

    Khan, Ahmed

    2010-01-01

    The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

  12. Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

    NASA Technical Reports Server (NTRS)

    Khan, Ahmed

    2010-01-01

    The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

  13. Mission Operations and Navigation Toolkit Environment

    NASA Technical Reports Server (NTRS)

    Sunseri, Richard F.; Wu, Hsi-Cheng; Hanna, Robert A.; Mossey, Michael P.; Duncan, Courtney B.; Evans, Scott E.; Evans, James R.; Drain, Theodore R.; Guevara, Michelle M.; Martin Mur, Tomas J.; Attiyah, Ahlam A.

    2009-01-01

    MONTE (Mission Operations and Navigation Toolkit Environment) Release 7.3 is an extensible software system designed to support trajectory and navigation analysis/design for space missions. MONTE is intended to replace the current navigation and trajectory analysis software systems, which, at the time of this reporting, are used by JPL's Navigation and Mission Design section. The software provides an integrated, simplified, and flexible system that can be easily maintained to serve the needs of future missions in need of navigation services.

  14. Pointing control for the International Comet Mission

    NASA Technical Reports Server (NTRS)

    Leblanc, D. R.; Schumacher, L. L.

    1980-01-01

    The design of the pointing control system for the proposed International Comet Mission, intended to fly by Comet Halley and rendezvous with Comet Tempel-2 is presented. Following a review of mission objectives and the spacecraft configuration, design constraints on the pointing control system controlling the two-axis gimballed scan platform supporting the science instruments are discussed in relation to the scientific requirements of the mission. The primary design options considered for the pointing control system design for the baseline spacecraft are summarized, and the design selected, which employs a target-referenced, inertially stabilized control system, is described in detail. The four basic modes of operation of the pointing control subsystem (target acquisition, inertial hold, target track and slew) are discussed as they relate to operations at Halley and Tempel-2. It is pointed that the pointing control system design represents a significant advance in the state of the art of pointing controls for planetary missions.

  15. Pointing control for the International Comet Mission

    NASA Technical Reports Server (NTRS)

    Leblanc, D. R.; Schumacher, L. L.

    1980-01-01

    The design of the pointing control system for the proposed International Comet Mission, intended to fly by Comet Halley and rendezvous with Comet Tempel-2 is presented. Following a review of mission objectives and the spacecraft configuration, design constraints on the pointing control system controlling the two-axis gimballed scan platform supporting the science instruments are discussed in relation to the scientific requirements of the mission. The primary design options considered for the pointing control system design for the baseline spacecraft are summarized, and the design selected, which employs a target-referenced, inertially stabilized control system, is described in detail. The four basic modes of operation of the pointing control subsystem (target acquisition, inertial hold, target track and slew) are discussed as they relate to operations at Halley and Tempel-2. It is pointed that the pointing control system design represents a significant advance in the state of the art of pointing controls for planetary missions.

  16. Cost efficient operations for Discovery class missions

    NASA Technical Reports Server (NTRS)

    Cameron, G. E.; Landshof, J. A.; Whitworth, G. W.

    1994-01-01

    The Near Earth Asteroid Rendezvous (NEAR) program at The Johns Hopkins University Applied Physics Laboratory is scheduled to launch the first spacecraft in NASA's Discovery program. The Discovery program is to promote low cost spacecraft design, development, and mission operations for planetary space missions. The authors describe the NEAR mission and discuss the design and development of the NEAR Mission Operations System and the NEAR Ground System with an emphasis on those aspects of the design that are conducive to low-cost operations.

  17. LANDSAT-D Mission Operations Review (MOR)

    NASA Technical Reports Server (NTRS)

    1982-01-01

    The integrated LANDSAT-D systems operation plan is presented and discussed with respect to functional elements, personnel, and procedures. Specifically, a review of the LANDSAT-D program, mission requirements and management, and flight operations is given.

  18. Evolution of Training in NASA's Mission Operations Directorate

    NASA Technical Reports Server (NTRS)

    Hutt, Jason

    2012-01-01

    NASA s Mission Operations Directorate provides all the mission planning, training, and operations support for NASA's human spaceflight missions including the International Space Station (ISS) and its fleet of supporting vehicles. MOD also develops and maintains the facilities necessary to conduct training and operations for those missions including the Mission Control Center, Space Station Training Facility, Space Vehicle Mockup Facility, and Neutral Buoyancy Laboratory. MOD's overarching approach to human spaceflight training is to "train like you fly." This approach means not only trying to replicate the operational environment in training but also to approach training with the same mindset as real operations. When in training, this means using the same approach for executing operations, responding to off-nominal situations, and conducting yourself in the operations environment in the same manner as you would for the real vehicle.

  19. The space mission MIR'97: operational aspects.

    PubMed

    Ewald, R; Lohn, K; Gerzer, R

    2000-12-01

    A German astronaut visited the MIR space station between 10 February and 2 March 1997. Together with his Russian colleagues, he conducted a series of scientific investigations before, during and after his stay aboard the MIR station. Research performed during this flight was part of a global space life sciences programme and focused on metabolic homeostasis, fluid balance, calcium homeostasis and cardiovascular regulatory mechanisms. The main goal of the scientific experiments was to use this mission as a milestone to establish international networks of scientific collaboration using space research as a tool for focused research in respective fields. Thus, in most cases the results obtained from the astronaut complemented a series of results obtained on ground and from other flights. In other cases, they extended previous results and opened new fields for future research. Human space flight with astronauts serving as operators and at the same time as test subjects is very complex. Many people, including mission control, a science management team, medical operations, ethics committees and a medical board, participated to harmonize the different requirements, thus making a maximal scientific outcome possible. In summary, this space mission may be seen as a model for focused long-term multidisciplinary international research, and demonstrates that space medicine is no longer adventure but science.

  20. NASA Antarctic Mission Operation ICE Bridge 2009

    NASA Image and Video Library

    NASA's Operation ICE Bridge is the most recent success for the Airborne Science Program, NASA scientists and climate researchers. This six minute video summarizes NASA's research mission over west ...

  1. INFLIGHT (MISSION CONTROL CENTER) - STS-2 - JSC

    NASA Image and Video Library

    1981-11-12

    S81-39433 (12 Nov. 1981) --- Flight director Neil B. Hutchinson monitors data displayed on a cathode ray tube (CRT) at his console in the mission operations control room (MOCR) in the Johnson Space Center?s Mission Control Center (MCC) during the launch phase of STS-2. Launch of the Columbia occurred at 9:10 a.m. CST today with astronauts Joe H. Engle and Richard H. Truly aboard the Columbia. Photo credit: NASA

  2. View of Mission Control Center celebrating conclusion of Apollo 11 mission

    NASA Image and Video Library

    1969-07-25

    S69-40022 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), showing the flight controllers celebrating the successful conclusion of the Apollo 11 lunar landing mission.

  3. Artificial intelligence in a mission operations and satellite test environment

    NASA Technical Reports Server (NTRS)

    Busse, Carl

    1988-01-01

    A Generic Mission Operations System using Expert System technology to demonstrate the potential of Artificial Intelligence (AI) automated monitor and control functions in a Mission Operations and Satellite Test environment will be developed at the National Aeronautics and Space Administration (NASA) Jet Propulsion Laboratory (JPL). Expert system techniques in a real time operation environment are being studied and applied to science and engineering data processing. Advanced decommutation schemes and intelligent display technology will be examined to develop imaginative improvements in rapid interpretation and distribution of information. The Generic Payload Operations Control Center (GPOCC) will demonstrate improved data handling accuracy, flexibility, and responsiveness in a complex mission environment. The ultimate goal is to automate repetitious mission operations, instrument, and satellite test functions by the applications of expert system technology and artificial intelligence resources and to enhance the level of man-machine sophistication.

  4. Mission operations and command assurance - Automating an operations TQM task

    NASA Technical Reports Server (NTRS)

    Welz, Linda; Kazz, Sheri; Potts, Sherrill; Witkowski, Mona; Bruno, Kristin

    1993-01-01

    A long-term program is in progress at JPL to reduce cost and risk of mission operations through defect prevention and error management. A major element of this program, Mission Operations and Command Assurance (MO&CA), provides a system level function on flight projects to instill quality in mission operations. MO&CA embodies the total quality management TQM principle of continuous process improvement (CPI) and uses CPI in applying automation to mission operations to reduce risk and costs. MO&CA has led efforts to apply and has implemented automation in areas that impact the daily flight project work environment including Incident Surprise Anomaly tracking and reporting; command data verification, tracking and reporting; and command support data usage. MO&CA's future work in automation will take into account that future mission operations systems must be designed to avoid increasing error through the introduction of automation, while adapting to the demands of smaller flight teams.

  5. Tropical Rainfall Measurement Mission (TRMM) Operation Summary

    NASA Technical Reports Server (NTRS)

    Nio, Tomomi; Saito, Susumu; Stocker, Erich; Pawloski, James H.; Murayama, Yoshifumi; Ohata, Takeshi

    2015-01-01

    The Tropical Rainfall Measurement Mission (TRMM) is a joint U.S. and Japan mission to observe tropical rainfall, which was launched by H-II No. 6 from Tanegashima in Japan at 6:27 JST on November 28, 1997. After the two-month commissioning of TRMM satellite and instruments, the original nominal mission lifetime was three years. In fact, the operations has continued for approximately 17.5 years. This paper provides a summary of the long term operations of TRMM.

  6. Autonomous Operations Mission Development Suite

    NASA Technical Reports Server (NTRS)

    Toro Medina, Jaime A.

    2016-01-01

    This is a presentation related to the development of Autonomous Operations Systems at NASA Kennedy Space Center. It covers a high level description of the work of FY14, FY15, FY16 for the AES IGODU and APL projects.

  7. Navigation Operations for the Magnetospheric Multiscale Mission

    NASA Technical Reports Server (NTRS)

    Long, Anne; Farahmand, Mitra; Carpenter, Russell

    2015-01-01

    The Magnetospheric Multiscale (MMS) mission employs four identical spinning spacecraft flying in highly elliptical Earth orbits. These spacecraft will fly in a series of tetrahedral formations with separations of less than 10 km. MMS navigation operations use onboard navigation to satisfy the mission definitive orbit and time determination requirements and in addition to minimize operations cost and complexity. The onboard navigation subsystem consists of the Navigator GPS receiver with Goddard Enhanced Onboard Navigation System (GEONS) software, and an Ultra-Stable Oscillator. The four MMS spacecraft are operated from a single Mission Operations Center, which includes a Flight Dynamics Operations Area (FDOA) that supports MMS navigation operations, as well as maneuver planning, conjunction assessment and attitude ground operations. The System Manager component of the FDOA automates routine operations processes. The GEONS Ground Support System component of the FDOA provides the tools needed to support MMS navigation operations. This paper provides an overview of the MMS mission and associated navigation requirements and constraints and discusses MMS navigation operations and the associated MMS ground system components built to support navigation-related operations.

  8. MSFC Skylab contamination control systems mission evaluation

    NASA Technical Reports Server (NTRS)

    1974-01-01

    Cluster external contamination control evaluation was made throughout the Skylab Mission. This evaluation indicated that contamination control measures instigated during the design, development, and operational phases of this program were adequate to reduce the general contamination environment external to the Cluster below the threshold senstivity levels for experiments and affected subsystems. Launch and orbit contamination control features included eliminating certain vents, rerouting vents for minimum contamination impact, establishing filters, incorporating materials with minimum outgassing characteristics and developing operational constraints and mission rules to minimize contamination effects. Prior to the launch of Skylab, contamination control math models were developed which were used to predict Cluster surface deposition and background brightness levels throughout the mission. The report summarizes the Skylab system and experiment contamination control evaluation. The Cluster systems and experiments evaluated include Induced Atmosphere, Corollary and ATM Experiments, Thermal Control Surfaces, Solar Array Systems, Windows and Star Tracker.

  9. Autonomous Mission Operations for Sensor Webs

    NASA Astrophysics Data System (ADS)

    Underbrink, A.; Witt, K.; Stanley, J.; Mandl, D.

    2008-12-01

    We present interim results of a 2005 ROSES AIST project entitled, "Using Intelligent Agents to Form a Sensor Web for Autonomous Mission Operations", or SWAMO. The goal of the SWAMO project is to shift the control of spacecraft missions from a ground-based, centrally controlled architecture to a collaborative, distributed set of intelligent agents. The network of intelligent agents intends to reduce management requirements by utilizing model-based system prediction and autonomic model/agent collaboration. SWAMO agents are distributed throughout the Sensor Web environment, which may include multiple spacecraft, aircraft, ground systems, and ocean systems, as well as manned operations centers. The agents monitor and manage sensor platforms, Earth sensing systems, and Earth sensing models and processes. The SWAMO agents form a Sensor Web of agents via peer-to-peer coordination. Some of the intelligent agents are mobile and able to traverse between on-orbit and ground-based systems. Other agents in the network are responsible for encapsulating system models to perform prediction of future behavior of the modeled subsystems and components to which they are assigned. The software agents use semantic web technologies to enable improved information sharing among the operational entities of the Sensor Web. The semantics include ontological conceptualizations of the Sensor Web environment, plus conceptualizations of the SWAMO agents themselves. By conceptualizations of the agents, we mean knowledge of their state, operational capabilities, current operational capacities, Web Service search and discovery results, agent collaboration rules, etc. The need for ontological conceptualizations over the agents is to enable autonomous and autonomic operations of the Sensor Web. The SWAMO ontology enables automated decision making and responses to the dynamic Sensor Web environment and to end user science requests. The current ontology is compatible with Open Geospatial Consortium (OGC

  10. Achieving Operability via the Mission System Paradigm

    NASA Technical Reports Server (NTRS)

    Hammer, Fred J.; Kahr, Joseph R.

    2006-01-01

    In the past, flight and ground systems have been developed largely-independently, with the flight system taking the lead, and dominating the development process. Operability issues have been addressed poorly in planning, requirements, design, I&T, and system-contracting activities. In many cases, as documented in lessons-learned, this has resulted in significant avoidable increases in cost and risk. With complex missions and systems, operability is being recognized as an important end-to-end design issue. Never-the-less, lessons-learned and operability concepts remain, in many cases, poorly understood and sporadically applied. A key to effective application of operability concepts is adopting a 'mission system' paradigm. In this paradigm, flight and ground systems are treated, from an engineering and management perspective, as inter-related elements of a larger mission system. The mission system consists of flight hardware, flight software, telecom services, ground data system, testbeds, flight teams, science teams, flight operations processes, procedures, and facilities. The system is designed in functional layers, which span flight and ground. It is designed in response to project-level requirements, mission design and an operations concept, and is developed incrementally, with early and frequent integration of flight and ground components.

  11. Spaceport operations for deep space missions

    NASA Technical Reports Server (NTRS)

    Holt, Alan C.

    1990-01-01

    Space Station Freedom is designed with the capability to cost-effectively evolve into a transportation node which can support manned lunar and Mars missions. To extend a permanent human presence to the outer planets (moon outposts) and to nearby star systems, additional orbiting space infrastructure and great advances in propulsion system and other technologies will be required. To identify primary operations and management requirements for these deep space missions, an interstellar design concept was developed and analyzed. The assembly, test, servicing, logistics resupply, and increment management techniques anticipated for lunar and Mars missions appear to provide a pattern which can be extended in an analogous manner to deep space missions. A long range, space infrastructure development plan (encompassing deep space missions) coupled with energetic, breakthrough level propulsion research should be initiated now to assist in making the best budget and schedule decisions.

  12. Mission operations systems for planetary exploration

    NASA Technical Reports Server (NTRS)

    Mclaughlin, William I.; Wolff, Donna M.

    1988-01-01

    The purpose of the paper is twofold: (1) to present an overview of the processes comprising planetary mission operations as conducted at the Jet Propulsion Laboratory, and (2) to present a project-specific and historical context within which this evolving process functions. In order to accomplish these objectives, the generic uplink and downlink functions are described along with their specialization to current flight projects. Also, new multimission capabilities are outlined, including prototyping of advanced-capability software for subsequent incorporation into more automated future operations. Finally, a specific historical ground is provided by listing some major operations software plus a genealogy of planetary missions beginning with Mariner 2 in 1962.

  13. Mission operations systems for planetary exploration

    NASA Technical Reports Server (NTRS)

    Mclaughlin, William I.; Wolff, Donna M.

    1988-01-01

    The purpose of the paper is twofold: (1) to present an overview of the processes comprising planetary mission operations as conducted at the Jet Propulsion Laboratory, and (2) to present a project-specific and historical context within which this evolving process functions. In order to accomplish these objectives, the generic uplink and downlink functions are described along with their specialization to current flight projects. Also, new multimission capabilities are outlined, including prototyping of advanced-capability software for subsequent incorporation into more automated future operations. Finally, a specific historical ground is provided by listing some major operations software plus a genealogy of planetary missions beginning with Mariner 2 in 1962.

  14. Knowledge systems support for mission operations automation

    NASA Astrophysics Data System (ADS)

    Atkinson, David J.

    1990-10-01

    A knowledge system which utilizes artificial intelligence technology to automate a subset of real time mission operations functions is described. An overview of spacecraft telecommunications operations at the Jet Propulsion Laboratories (JPL) highlights requirements for automation. The knowledge system, called the Spacecraft Health Automated Reasoning Prototype (SHARP), developed to explore methods for automated health and status analysis is outlined. The advantages of the system were demonstrated during the spacecraft's encounter with the planet Neptune. The design of the fault detection and diagnosis portions of SHARP is discussed. The performance of SHARP during the encounter is discussed along with issues and benefits arising from application of knowledge system to mission operations automation.

  15. Preparing Cassini Uplink Operations for Extended Mission

    NASA Technical Reports Server (NTRS)

    Maxwell, Jennifer L.; McCullar, Michelle L.; Conner, Diane

    2008-01-01

    The Cassini-Huygens Mission to Saturn and Titan, a joint venture between the National Aeronautics and Space Administration, the European Space Agency, and the Italian Space Agency, is conducting a four-year, prime mission exploring the Saturnian system, including its atmosphere, rings, magnetosphere, moons and icy satellites. Launched in 1997, Cassini began its prime mission in 2004. Cassini is now preparing for a new era, a two-year extended mission to revisit many of the highlights and new discoveries made during the prime mission. Because of the light time delay from Earth to Saturn, and the time needed to coordinate the complicated science and engineering activities that take place on the spacecraft, commanding on Cassini is done in approximately 40-day intervals known as sequences. The Cassini Uplink Operations team is responsible for the final development and validation of the pointing profile and instrument and spacecraft commands that are contained in a sequence. During this final analysis prior to uplink to the spacecraft, thorough and exact evaluation is necessary to ensure there are no mistakes during commanding. In order to perform this evaluation, complete and refined processes and procedures are fundamental. The Uplink Operations team is also responsible for anomaly response during sequence execution, a process in which critical decisions often are made in real-time. Recent anomalies on other spacecraft missions have highlighted two major risks in the operations process: (1) personnel turnover and the retirement of critical knowledge and (2) aging, outdated operations procedures. If other missions are a good barometer, the Cassini extended mission will be presented with a high personnel turnover of the Cassini flight team, which could lead to a loss of expertise that has been essential to the success of the prime mission. In order to prepare the Cassini Uplink Operations Team for this possibility and to continue to develop and operate safe science and

  16. Preparing Cassini Uplink Operations for Extended Mission

    NASA Technical Reports Server (NTRS)

    Maxwell, Jennifer L.; McCullar, Michelle L.; Conner, Diane

    2008-01-01

    The Cassini-Huygens Mission to Saturn and Titan, a joint venture between the National Aeronautics and Space Administration, the European Space Agency, and the Italian Space Agency, is conducting a four-year, prime mission exploring the Saturnian system, including its atmosphere, rings, magnetosphere, moons and icy satellites. Launched in 1997, Cassini began its prime mission in 2004. Cassini is now preparing for a new era, a two-year extended mission to revisit many of the highlights and new discoveries made during the prime mission. Because of the light time delay from Earth to Saturn, and the time needed to coordinate the complicated science and engineering activities that take place on the spacecraft, commanding on Cassini is done in approximately 40-day intervals known as sequences. The Cassini Uplink Operations team is responsible for the final development and validation of the pointing profile and instrument and spacecraft commands that are contained in a sequence. During this final analysis prior to uplink to the spacecraft, thorough and exact evaluation is necessary to ensure there are no mistakes during commanding. In order to perform this evaluation, complete and refined processes and procedures are fundamental. The Uplink Operations team is also responsible for anomaly response during sequence execution, a process in which critical decisions often are made in real-time. Recent anomalies on other spacecraft missions have highlighted two major risks in the operations process: (1) personnel turnover and the retirement of critical knowledge and (2) aging, outdated operations procedures. If other missions are a good barometer, the Cassini extended mission will be presented with a high personnel turnover of the Cassini flight team, which could lead to a loss of expertise that has been essential to the success of the prime mission. In order to prepare the Cassini Uplink Operations Team for this possibility and to continue to develop and operate safe science and

  17. Operational training for the mission operations at the Brazilian National Institute for Space Research (INPE)

    NASA Technical Reports Server (NTRS)

    Rozenfeld, Pawel

    1993-01-01

    This paper describes the selection and training process of satellite controllers and data network operators performed at INPE's Satellite Tracking and Control Center in order to prepare them for the mission operations of the INPE's first (SCD1) satellite. An overview of the ground control system and SCD1 architecture and mission is given. Different training phases are described, taking into account that the applicants had no previous knowledge of space operations requiring, therefore, a training which started from the basics.

  18. Integrated Human-Robotic Missions to the Moon and Mars: Mission Operations Design Implications

    NASA Technical Reports Server (NTRS)

    Korth, David; LeBlanc, Troy; Mishkin, Andrew; Lee, Young

    2006-01-01

    For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.

  19. Integrated Human-Robotic Missions to the Moon and Mars: Mission Operations Design Implications

    NASA Technical Reports Server (NTRS)

    Mishkin, Andrew; Lee, Young; Korth, David; LeBlanc, Troy

    2007-01-01

    For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.

  20. Integrated Human-Robotic Missions to the Moon and Mars: Mission Operations Design Implications

    NASA Technical Reports Server (NTRS)

    Mishkin, Andrew; Lee, Young; Korth, David; LeBlanc, Troy

    2007-01-01

    For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.

  1. Activity in Mission Control Center during Apollo 12 lunar landing mission

    NASA Technical Reports Server (NTRS)

    1969-01-01

    Overal view of activity in the Mission Operations Control Room in the Mission Control Center, bldg 30, during the Apollo 12 lunar landing mission. When this picture was made the first Apollo 12 extravehicular activity was being televised from the surface of the Moon.

  2. Mission Control Center at conclusion of Apollo 15 lunar landing mission

    NASA Technical Reports Server (NTRS)

    1971-01-01

    An overall view of activity in the Mission Operations Control Room in the Mission Control Center at the conclusion of the Apollo 15 lunar landing mission. The television monitor in the right background shows the welcome ceremonies aboard the prime recovery ship, U.S.S. Okinawa, in the mid-Pacific Ocean.

  3. Mission Control Center at conclusion of Apollo 15 lunar landing mission

    NASA Image and Video Library

    1971-08-07

    An overall view of activity in the Mission Operations Control Room in the Mission Control Center at the conclusion of the Apollo 15 lunar landing mission. The television monitor in the right background shows the welcome ceremonies aboard the prime recovery ship, U.S.S. Okinawa, in the mid-Pacific Ocean.

  4. Design of mission operations systems for scientific remote sensing

    NASA Technical Reports Server (NTRS)

    Wall, Stephen D.; Ledbetter, Kenneth W.

    1991-01-01

    The present work describes the mission operations system (MOS) design process for remote-sensing missions. A MOS is defined as the system required to perform, monitor, and control an operation, encompassing personnel, hardware, software and/or documentation. Attention is given to telecommunications and remote-sensing instrumentation, MOS definition program phases and reviews, and MOS organization, management, and staffing. Also treated are the uplink and downlink processes, anomalies and contingency plans, the illustrative case of the MOS for the Magellan radar sensing mission, and a projection of future MOSs incorporating AI.

  5. Automation of Hubble Space Telescope Mission Operations

    NASA Technical Reports Server (NTRS)

    Burley, Richard; Goulet, Gregory; Slater, Mark; Huey, William; Bassford, Lynn; Dunham, Larry

    2012-01-01

    On June 13, 2011, after more than 21 years, 115 thousand orbits, and nearly 1 million exposures taken, the operation of the Hubble Space Telescope successfully transitioned from 24x7x365 staffing to 815 staffing. This required the automation of routine mission operations including telemetry and forward link acquisition, data dumping and solid-state recorder management, stored command loading, and health and safety monitoring of both the observatory and the HST Ground System. These changes were driven by budget reductions, and required ground system and onboard spacecraft enhancements across the entire operations spectrum, from planning and scheduling systems to payload flight software. Changes in personnel and staffing were required in order to adapt to the new roles and responsibilities required in the new automated operations era. This paper will provide a high level overview of the obstacles to automating nominal HST mission operations, both technical and cultural, and how those obstacles were overcome.

  6. Mariner Mars 1971 project. Volume 3: Mission operations system implementation and standard mission flight operations

    NASA Technical Reports Server (NTRS)

    1973-01-01

    The Mariner Mars 1971 mission which was another step in the continuing program of planetary exploration in search of evidence of exobiological activity, information on the origin and evolution of the solar system, and basic science data related to the study of planetary physics, geology, planetology, and cosmology is reported. The mission plan was designed for two spacecraft, each performing a separate but complementary mission. However, a single mission plan was actually used for Mariner 9 because of failure of the launch vehicle for the first spacecraft. The implementation is described, of the Mission Operations System, including organization, training, and data processing development and operations, and Mariner 9 spacecraft cruise and orbital operations through completion of the standard mission from launch to solar occultation in April 1972 are discussed.

  7. Advanced automation in space shuttle mission control

    NASA Technical Reports Server (NTRS)

    Heindel, Troy A.; Rasmussen, Arthur N.; Mcfarland, Robert Z.

    1991-01-01

    The Real Time Data System (RTDS) Project was undertaken in 1987 to introduce new concepts and technologies for advanced automation into the Mission Control Center environment at NASA's Johnson Space Center. The project's emphasis is on producing advanced near-operational prototype systems that are developed using a rapid, interactive method and are used by flight controllers during actual Shuttle missions. In most cases the prototype applications have been of such quality and utility that they have been converted to production status. A key ingredient has been an integrated team of software engineers and flight controllers working together to quickly evolve the demonstration systems.

  8. Cost Analysis in a Multi-Mission Operations Environment

    NASA Technical Reports Server (NTRS)

    Felton, Larry; Newhouse, Marilyn; Bornas, Nick; Botts, Dennis; Ijames, Gayleen; Montgomery, Patty; Roth, Karl

    2014-01-01

    Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and

  9. Apollo guidance, navigation and control: Guidance system operations plan for manned CM earth orbital and lunar missions using Program COLOSSUS 3. Section 3: Digital autopilots (revision 14)

    NASA Technical Reports Server (NTRS)

    1972-01-01

    Digital autopilots for the manned command module earth orbital and lunar missions using program COLOSSUS 3 are discussed. Subjects presented are: (1) reaction control system digital autopilot, (2) thrust vector control autopilot, (3) entry autopilot and mission control programs, (4) takeover of Saturn steering, and (5) coasting flight attitude maneuver routine.

  10. Medical System Concept of Operations for Mars Exploration Missions

    NASA Technical Reports Server (NTRS)

    Urbina, Michelle; Rubin, D.; Hailey, M.; Reyes, D.; Antonsen, Eric

    2017-01-01

    Future exploration missions will be the first time humanity travels beyond Low Earth Orbit (LEO) since the Apollo program, taking us to cis-lunar space, interplanetary space, and Mars. These long-duration missions will cover vast distances, severely constraining opportunities for emergency evacuation to Earth and cargo resupply opportunities. Communication delays and blackouts between the crew and Mission Control will eliminate reliable, real-time telemedicine consultations. As a result, compared to current LEO operations onboard the International Space Station, exploration mission medical care requires an integrated medical system that provides additional in-situ capabilities and a significant increase in crew autonomy. The Medical System Concept of Operations for Mars Exploration Missions illustrates how a future NASA Mars program could ensure appropriate medical care for the crew of this highly autonomous mission. This Concept of Operations document, when complete, will document all mission phases through a series of mission use case scenarios that illustrate required medical capabilities, enabling the NASA Human Research Program (HRP) Exploration Medical Capability (ExMC) Element to plan, design, and prototype an integrated medical system to support human exploration to Mars.

  11. Mission Control Center (MCC) - Apollo 15 Launch - MSC

    NASA Image and Video Library

    1971-07-26

    S71-41357 (26 July 1971) --- An overall, wide-angle lens view of activity in the Mission Operations Control Room in the Mission Control Center minutes after the launch of the Apollo 15 lunar landing mission. Ground elapsed time was 45 minutes and 42 seconds when this photograph was taken.

  12. Clifford Charlesworth seated at his console in Mission Control Room

    NASA Image and Video Library

    1968-12-21

    S68-55742 (21 Dec. 1968) --- Clifford E. Charlesworth, Apollo 8 "Green Team" flight director, is seated at his console in the Mission Operations Control Room in the Mission Control Center, Building 30, during the launch of the Apollo 8 (Spacecraft 103/Saturn 503) manned lunar orbit space mission.

  13. Solar bimodal mission and operational analysis

    SciTech Connect

    Frye, P.; Law, G.

    1996-03-01

    Recent interest by both government and industry has prompted evaluation of a solar bimodal upper stage for propulsion/power applications in Earth orbit. The solar bimodal system provides an integral propulsion and power system for the orbit transfer and on-orbit phases of a satellite mission. This paper presents an initial systems evaluation of a solar bimodal system used to place satellite payloads for Geosynchronous Earth Orbit (GEO), High Earth Orbit (HEO-Molniya class), and Mid Earth Orbit (GPS class) missions with emphasis on the GEO mission. The analysis was performed as part of the Operational Effectiveness and Cost Comparison Study (OECS) sponsored by Phillips Laboratory (PL). The solar bimodal concept was investigated on a mission operational and performance basis for on-orbit power levels ranging from less than 1 kWe to 20 kWe. Atlas IIAS, Delta 7920, and Titan IV launch vehicles were considered for injecting the solar bimodal upper stage and payload into initial orbits ranging from Low Earth Orbit (LEO) (185{times}185 km circular) to higher apogee altitudes (185{times}18,500 km elliptical). The influences of engine thrust, power level, trip time, staging altitude, and thermal storage charge-discharge characteristics on the mission payload capability were developed. {copyright} {ital 1996 American Institute of Physics.}

  14. Front view of bldg 30 which houses mission control

    NASA Image and Video Library

    1984-08-30

    41D-3072 (30 Aug 1984) --- A 41-D shift change is taking place in the Johnson Space Center's Building 30. In its twenty years of operation, the mission control center has been the scene of many such changes. The windowless wing at left houses three floors, including rooms supporting flight control rooms 1 & 2 (formerly called mission operations control rooms 1 & 2).

  15. M.P. Frank is seated at console in Mission Control during ASTP mission

    NASA Technical Reports Server (NTRS)

    1975-01-01

    M.P. Frank (foreground), the American senior ASTP flight director, is seated at his console in the Mission Operations Control Room in the Mission Control Center during the joint U.S.-USSR Apollo-Soyuz Test Project (ASTP) docking in Earth orbit mission. The other two men are Alan C. Glines (in center), operations and procedures officer; and Donald R. Puddy, flight director.

  16. Cost Analysis In A Multi-Mission Operations Environment

    NASA Technical Reports Server (NTRS)

    Newhouse, M.; Felton, L.; Bornas, N.; Botts, D.; Roth, K.; Ijames, G.; Montgomery, P.

    2014-01-01

    Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the

  17. Wind Prelaunch Mission Operations Report (MOR)

    NASA Technical Reports Server (NTRS)

    1994-01-01

    The National Aeronautics and Space Administration (NASA) Wind mission is the first mission of the Global Geospace Science (GGS) initiative. The Wind laboratory will study the properties of particles and waves in the region between the Earth and the Sun. Using the Moon s gravity to save fuel, dual lunar swing-by orbits enable the spacecraft to sample regions close to and far from the Earth. During the three year mission, Wind will pass through the bow shock of Earth's magnetosphere to begin a thorough investigation of the solar wind. Mission objectives require spacecraft measurements in two orbits: lunar swing- by ellipses out to distances of 250 Earth radii (RE) and a small orbit around the Lagrangian point L-l that remains between the Earth and the Sun. Wind will be placed into an initial orbit for approximately 2 years. It will then be maneuvered into a transition orbit and ultimately into a halo orbit at the Earth-Sun L-l point where it will operate for the remainder of its lifetime. The Wind satellite development was managed by NASA's Goddard Space Flight Center with the Martin Marietta Corporation, Astro-Space Division serving as the prime contractor. Overall programmatic direction was provided by NASA Headquarters, Office of Space Science. The spacecraft will be launched under a launch service contract with the McDonnell Douglas Corporation on a Delta II Expendable Launch Vehicle (ELV) within a November l-l4, 1994 launch window. The Wind spacecraft carries six U.S. instruments, one French instrument, and the first Russian instrument ever to fly on an American satellite. The Wind and Polar missions are the two components of the GGS Program. Wind is also the second mission of the International Solar Terrestrial Physics (ISTP) Program. The first ISTP mission, Geotail, is a joint project of the Institute of Space and Astronautical Science of Japan and NASA which launched in 1992. The Wind mission is planned to overlap Geotail by six months and Polar by one year

  18. Mission Control Center (MCC): Apollo XV - MSC

    NASA Image and Video Library

    1971-08-02

    S71-41759 (2 Aug. 1971) --- A partial view of activity in the Mission Operations Control Room in the Mission Control Center during the liftoff of the Apollo 15 Lunar Module "Falcon" ascent stage from the lunar surface. An RCA color television camera mounted on the Lunar Roving Vehicle made it possible for people on Earth to watch the LM's spectacular launch from the moon. The LM liftoff was at 171:37 ground elapsed time. The LRV was parked about 300 feet east of the LM. The TV camera was remotely controlled from a console in the MOCR. Seated in the right foreground is astronaut Edgar D. Mitchell, a spacecraft communicator. Mitchell was lunar module pilot of the Apollo 14 lunar landing mission. Note liftoff on the television monitor in the center background.

  19. Mission operations and command assurance: Flight operations quality improvements

    NASA Technical Reports Server (NTRS)

    Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Potts, Sherrill S.; Witkowski, Mona M.

    1994-01-01

    Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous solving among flight teams and provides continuous process improvement to reduce risk in mission operations by addressing human factors. The MO&CA task has evolved from participating as a member of the spacecraft team, to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

  20. Space Ops 2002: Bringing Space Operations into the 21st Century. Track 3: Operations, Mission Planning and Control. 2nd Generation Reusable Launch Vehicle-Concepts for Flight Operations

    NASA Technical Reports Server (NTRS)

    Hagopian, Jeff

    2002-01-01

    performed by crew and ground controllers. This experience has also identified the need for new approaches to staffing and training for both crew and ground controllers. This paper provides a brief overview of the mission capabilities provided by the 2nd Gen RLV, a description of NASA's approach to developing the 2nd Gen RLV, a discussion of operations concepts, and a list of challenges to implementing those concepts.

  1. Operations Concepts for Deep-Space Missions: Challenges and Opportunities

    NASA Technical Reports Server (NTRS)

    McCann, Robert S.

    2010-01-01

    Historically, manned spacecraft missions have relied heavily on real-time communication links between crewmembers and ground control for generating crew activity schedules and working time-critical off-nominal situations. On crewed missions beyond the Earth-Moon system, speed-of-light limitations will render this ground-centered concept of operations obsolete. A new, more distributed concept of operations will have to be developed in which the crew takes on more responsibility for real-time anomaly diagnosis and resolution, activity planning and replanning, and flight operations. I will discuss the innovative information technologies, human-machine interfaces, and simulation capabilities that must be developed in order to develop, test, and validate deep-space mission operations

  2. Constellation Program Mission Operations Project Office Status and Support Philosophy

    NASA Technical Reports Server (NTRS)

    Smith, Ernest; Webb, Dennis

    2007-01-01

    The Constellation Program Mission Operations Project Office (CxP MOP) at Johnson Space Center in Houston Texas is preparing to support the CxP mission operations objectives for the CEV/Orion flights, the Lunar Lander, and and Lunar surface operations. Initially the CEV will provide access to the International Space Station, then progress to the Lunar missions. Initial CEV mission operations support will be conceptually similar to the Apollo missions, and we have set a challenge to support the CEV mission with 50% of the mission operations support currently required for Shuttle missions. Therefore, we are assessing more efficient way to organize the support and new technologies which will enhance our operations support. This paper will address the status of our preparation for these CxP missions, our philosophical approach to CxP operations support, and some of the technologies we are assessing to streamline our mission operations infrastructure.

  3. Constellation Program Mission Operations Project Office Status and Support Philosophy

    NASA Technical Reports Server (NTRS)

    Smith, Ernest; Webb, Dennis

    2007-01-01

    The Constellation Program Mission Operations Project Office (CxP MOP) at Johnson Space Center in Houston Texas is preparing to support the CxP mission operations objectives for the CEV/Orion flights, the Lunar Lander, and and Lunar surface operations. Initially the CEV will provide access to the International Space Station, then progress to the Lunar missions. Initial CEV mission operations support will be conceptually similar to the Apollo missions, and we have set a challenge to support the CEV mission with 50% of the mission operations support currently required for Shuttle missions. Therefore, we are assessing more efficient way to organize the support and new technologies which will enhance our operations support. This paper will address the status of our preparation for these CxP missions, our philosophical approach to CxP operations support, and some of the technologies we are assessing to streamline our mission operations infrastructure.

  4. Remote Operations Control Center (ROCC)

    NASA Technical Reports Server (NTRS)

    1997-01-01

    Students at Rensselaer Polytechnic Institute (RPI) in Troy, NY, monitor the progress of the Isothermal Dendritic Growth Experiment (IDGE) during the U.S. Microgravity Payload-4 (USMP-4) mission (STS-87, Nov. 19 - Dec. 5, 1997). Remote Operation Control Center (ROCC) like this one will become more common during operations with International Space Station. IDGE, flown on three Space Shuttle missions, is yielding new insights into virtually all industrially relevant metal and alloy forming operations. Photo credit: Renssenlaer Polythnic Institute (RPI)

  5. A Muli-Mission Operations Strategy for Sequencing and Commanding

    NASA Technical Reports Server (NTRS)

    Brooks, R.

    2000-01-01

    The Telecommunications and Mission Operations Directorate (TMOD) of the Jet Propulsion Laboratory is responsible for development, maintenance and operation of flight operations systems for several classes of science missions planned for the next several years.

  6. NASA's Spitzer Space Telescope's Operational Mission Experience

    NASA Technical Reports Server (NTRS)

    Wilson, Robert K.; Scott, Charles P.

    2006-01-01

    New Generation of Detector Arrays(100 to 10,000 Gain in Capability over Previous Infrared Space Missions). IRAC: 256 x 256 pixel arrays operating at 3.6 microns, 4.5 microns, 5.8 microns, 8.0 microns. MIPS: Photometer with 3 sets of arrays operating at 24 microns, 70 microns and 160 microns. 128 x 128; 32 x 32 and 2 x 20 arrays. Spectrometer with 50-100 micron capabilities. IRS: 4 Array (128x128 pixel) Spectrograph, 4 -40 microns. Warm Launch Architecture: All other Infrared Missions launched with both the telescope and scientific instrument payload within the cryostat or Dewar. Passive cooling used to cool outer shell to approx.40 K. Cryogenic Boil-off then cools telescope to required 5.5K. Earth Trailing Heliocentric Orbit: Increased observing efficiency, simplification of observation planning, removes earth as heat source.

  7. Venus Express ground segment and mission operations

    NASA Astrophysics Data System (ADS)

    Warhaut, Manfred; Accomazzo, Andrea

    2005-11-01

    ESOC was responsible for developing the ground-segment facilities for both the Rosetta and Mars Express interplanetary mission. The high degree of commonality between those spacecraft and Venus Express, the twin spacecraft of Mars Express, has allowed large-scale re-use of ground-segment elements and the replication of the operations concepts for those spacecraft, resulting in significant cost and risk reductions.

  8. Magnetospheric Multiscale Science Mission Profile and Operations

    NASA Astrophysics Data System (ADS)

    Fuselier, S. A.; Lewis, W. S.; Schiff, C.; Ergun, R.; Burch, J. L.; Petrinec, S. M.; Trattner, K. J.

    2016-03-01

    The Magnetospheric Multiscale (MMS) mission and operations are designed to provide the maximum reconnection science. The mission phases are chosen to investigate reconnection at the dayside magnetopause and in the magnetotail. At the dayside, the MMS orbits are chosen to maximize encounters with the magnetopause in regions where the probability of encountering the reconnection diffusion region is high. In the magnetotail, the orbits are chosen to maximize encounters with the neutral sheet, where reconnection is known to occur episodically. Although this targeting is limited by engineering constraints such as total available fuel, high science return orbits exist for launch dates over most of the year. The tetrahedral spacecraft formation has variable spacing to determine the optimum separations for the reconnection regions at the magnetopause and in the magnetotail. In the specific science regions of interest, the spacecraft are operated in a fast survey mode with continuous acquisition of burst mode data. Later, burst mode triggers and a ground-based scientist in the loop are used to determine the highest quality data to downlink for analysis. This operations scheme maximizes the science return for the mission.

  9. 2016 Mission Operations Working Group: Earth Observing-1 (EO-1)

    NASA Technical Reports Server (NTRS)

    Frye, Stuart

    2016-01-01

    EO-1 Mission Status for the Constellation Mission Operations Working Group to discuss the EO-1 flight systems, mission enhancements, debris avoidance maneuver, orbital information, 5-year outlook, and new ground stations.

  10. Mission operations of the handicapped FORMOSAT-2

    NASA Astrophysics Data System (ADS)

    Lin, Shin-Fa; Chern, Jeng-Shing; Wu, An-Ming

    2014-10-01

    Since its launch on 20 May 2004, FORMOSAT-2 (FS2, Formosa satellite ♯2) has been operated on orbit for more than 9 years. It carries two payloads: the remote sensing instrument (RSI) for Earth observations and the imager of sprites and upper atmospheric lightning instrument (ISUAL) for the purpose of scientific observations. The RSI is operating at daytime while ISUAL is active at night-time. To meet both mission objectives simultaneously, the satellite operations planning has been more complicated. In order to maximize the usage of the on-board resources, the satellite attitude maneuver activities and power charge/discharge cycles have been scheduled cautiously in every detail. Under such fully engaged operations scenario and with a design life of 5 years, it is inevitable that the satellite encountered many anomalies, either permanent or temporary. In particular, one attitude gyro (totally four) and one reaction wheel (totally four) have been failed. This paper presents the major anomalies and resolutions in the past years. Many iterations and trade-offs have been made to minimize the effect on mission operations of the handicapped FORMOSAT-2. It still can provide about 80% of the designed functions and capabilities.

  11. Operations mission planner beyond the baseline

    NASA Technical Reports Server (NTRS)

    Biefeld, Eric; Cooper, Lynne

    1991-01-01

    The scheduling of Space Station Freedom must satisfy four major requirements. It must ensure efficient housekeeping operations, maximize the collection of science, respond to changes in tasking and available resources, and accommodate the above changes in a manner that minimizes disruption of the ongoing operations of the station. While meeting these requirements the scheduler must cope with the complexity, scope, and flexibility of SSF operations. This requires the scheduler to deal with an astronomical number of possible schedules. The Operations Mission Planner (OMP) is centered around minimally disruptive replanning and the use of heuristics limit search in scheduling. OMP has already shown several artificial intelligence based scheduling techniques such as Interleaved Iterative Refinement and Bottleneck Identification using Process Chronologies.

  12. Mission Operations of EO-1 with Onboard Autonomy

    NASA Technical Reports Server (NTRS)

    Tran, Daniel Q.

    2006-01-01

    Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the prior, labor and knowledge intensive mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the new autonomous operations as part of the Autonomous Sciencecraft Experiment.

  13. Mission Operations of EO-1 with Onboard Autonomy

    NASA Technical Reports Server (NTRS)

    Tran, Daniel Q.

    2006-01-01

    Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the prior, labor and knowledge intensive mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the new autonomous operations as part of the Autonomous Sciencecraft Experiment.

  14. Controlling UCAVs by JTACs in CAS missions

    NASA Astrophysics Data System (ADS)

    Kumaş, A. E.

    2014-06-01

    By means of evolving technology, capabilities of UAVs (Unmanned Aerial Vehicle)s are increasing rapidly. This development provides UAVs to be used in many different areas. One of these areas is CAS (Close Air Support) mission. UAVs have several advantages compared to manned aircraft, however there are also some problematic areas. The remote controlling of these vehicles from thousands of nautical miles away via satellite may lead to various problems both ethical and tactical aspects. Therefore, CAS missions require a good level of ALI (Air-Land Integration), a high SA (situational awareness) and precision engagement. In fact, there is an aware friendly element in the target area in CAS missions, unlike the other UAV operations. This element is an Airman called JTAC (Joint Terminal Attack Controller). Unlike the JTAC, UAV operators are too far away from target area and use the limited FOV (Field of View) provided by camera and some other sensor data. In this study, target area situational awareness of a UAV operator and a JTAC, in a high-risk mission for friendly ground forces and civilians such as CAS, are compared. As a result of this comparison, answer to the question who should control the UCAV (Unmanned Combat Aerial Vehicle) in which circumstances is sought. A literature review is made in UAV and CAS fields and recent air operations are examined. The control of UCAV by the JTAC is assessed by SWOT analysis and as a result it is deduced that both control methods can be used in different situations within the framework of the ROE (Rules Of Engagement) is reached.

  15. Hubble Space Telescope First Servicing Mission Prelaunch Mission Operation Report

    NASA Technical Reports Server (NTRS)

    1993-01-01

    The Hubble Space Telescope (HST) is a high-performance astronomical telescope system designed to operate in low-Earth orbit. It is approximately 43 feet long, with a diameter of 10 feet at the forward end and 14 feet at the aft end. Weight at launch was approximately 25,000 pounds. In principle, it is no different than the reflecting telescopes in ground-based astronomical observatories. Like ground-based telescopes, the HST was designed as a general-purpose instrument, capable of using a wide variety of scientific instruments at its focal plane. This multi-purpose characteristic allows the HST to be used as a national facility, capable of supporting the astronomical needs of an international user community. The telescope s planned useful operational lifetime is 15 years, during which it will make observations in the ultraviolet, visible, and infrared portions of the spectrum. The extended operational life of the HST is possible by using the capabilities of the Space Transportation System to periodically visit the HST on-orbit to replace failed or degraded components, install instruments with improved capabilities, re-boost the HST to higher altitudes compensating for gravitational effects, and to bring the HST back to Earth when the mission is terminated. The largest ground-based observatories, such as the 200-inch aperture Hale telescope at Palomar Mountain, California, can recognize detail in individual galaxies several billion light years away. However, like all earthbound devices, the Hale telescope is limited because of the blurring effect of the Earth s atmosphere. Further, the wavelength region observable from the Earth s surface is limited by the atmosphere to the visible part of the spectrum. The very important ultraviolet portion of the spectrum is lost. The HST uses a 2.4-meter reflective optics system designed to capture data over a wavelength region that reaches far into the ultraviolet and infrared portions of the spectrum.

  16. View of Mission Control during joint U.S.-USSR ASTP mission

    NASA Image and Video Library

    1975-07-17

    S75-28685 (17 July 1975) --- An overall view of activity in the Mission Operations Control Room in the Mission Control Center during joint U.S.-USSR Apollo Soyuz Test Project (ASTP) docking mission in Earth orbit. The large television monitor shows an interior view of the Soyuz Orbital Module with astronaut Thomas P. Stafford (in front) visiting with cosmonaut Aleksey A. Leonov. Neil B. Hutchinson (right hand to chin) is the flight director for this shift.

  17. Formation Control for the MAXIM Mission

    NASA Technical Reports Server (NTRS)

    Luquette, Richard J.; Leitner, Jesse; Gendreau, Keith; Sanner, Robert M.

    2004-01-01

    Over the next twenty years, a wave of change is occurring in the space-based scientific remote sensing community. While the fundamental limits in the spatial and angular resolution achievable in spacecraft have been reached, based on today s technology, an expansive new technology base has appeared over the past decade in the area of Distributed Space Systems (DSS). A key subset of the DSS technology area is that which covers precision formation flying of space vehicles. Through precision formation flying, the baselines, previously defined by the largest monolithic structure which could fit in the largest launch vehicle fairing, are now virtually unlimited. Several missions including the Micro-Arcsecond X-ray Imaging Mission (MAXIM), and the Stellar Imager will drive the formation flying challenges to achieve unprecedented baselines for high resolution, extended-scene, interferometry in the ultraviolet and X-ray regimes. This paper focuses on establishing the feasibility for the formation control of the MAXIM mission. MAXIM formation flying requirements are on the order of microns, while Stellar Imager mission requirements are on the order of nanometers. This paper specifically addresses: (1) high-level science requirements for these missions and how they evolve into engineering requirements; and (2) the development of linearized equations of relative motion for a formation operating in an n-body gravitational field. Linearized equations of motion provide the ground work for linear formation control designs.

  18. Interactive experimenters' planning procedures and mission control

    NASA Technical Reports Server (NTRS)

    Desjardins, R. L.

    1973-01-01

    The computerized mission control and planning system routinely generates a 24-hour schedule in one hour of operator time by including time dimensions into experimental planning procedures. Planning is validated interactively as it is being generated segment by segment in the frame of specific event times. The planner simply points a light pen at the time mark of interest on the time line for entering specific event times into the schedule.

  19. An agent-oriented approach to automated mission operations

    NASA Technical Reports Server (NTRS)

    Truszkowski, Walt; Odubiyi, Jide

    1994-01-01

    As we plan for the next generation of Mission Operations Control Center (MOCC) systems, there are many opportunities for the increased utilization of innovative knowledge-based technologies. The innovative technology discussed is an advanced use of agent-oriented approaches to the automation of mission operations. The paper presents an overview of this technology and discusses applied operational scenarios currently being investigated and prototyped. A major focus of the current work is the development of a simple user mechanism that would empower operations staff members to create, in real time, software agents to assist them in common, labor intensive operations tasks. These operational tasks would include: handling routine data and information management functions; amplifying the capabilities of a spacecraft analyst/operator to rapidly identify, analyze, and correct spacecraft anomalies by correlating complex data/information sets and filtering error messages; improving routine monitoring and trend analysis by detecting common failure signatures; and serving as a sentinel for spacecraft changes during critical maneuvers enhancing the system's capabilities to support nonroutine operational conditions with minimum additional staff. An agent-based testbed is under development. This testbed will allow us to: (1) more clearly understand the intricacies of applying agent-based technology in support of the advanced automation of mission operations and (2) access the full set of benefits that can be realized by the proper application of agent-oriented technology in a mission operations environment. The testbed under development addresses some of the data management and report generation functions for the Explorer Platform (EP)/Extreme UltraViolet Explorer (EUVE) Flight Operations Team (FOT). We present an overview of agent-oriented technology and a detailed report on the operation's concept for the testbed.

  20. STS Payloads Mission Control Study

    NASA Technical Reports Server (NTRS)

    1975-01-01

    Basic study tasks are described which produce documentation to meet the following objectives: (1) flight control functions, (2) NASA flight control capabilities, (3) function allocations, (4) operational communications and information processing plans, (5) alternative system concepts for STS payload flight control support, and (6) estimated additional resources for selected system concept(s).

  1. Agent-Supported Mission Operations Teamwork

    NASA Technical Reports Server (NTRS)

    Malin, Jane T.

    2003-01-01

    This slide presentation reviews the development of software agents to support of mission operations teamwork. The goals of the work was to make automation by agents easy to use, supervise and direct, manage information and communication to decrease distraction, interruptions, workload and errors, reduce mission impact of off-nominal situations and increase morale and decrease turnover. The accomplishments or the project are: 1. Collaborative agents - mixed initiative and creation of instructions for mediating agent 2. Methods for prototyping, evaluating and evolving socio-technical systems 3. Technology infusion: teamwork tools in mISSIons 4. Demonstrations in simulation testbed An example of the use of agent is given, the use of an agent to monitor a N2 tank leak. An incomplete instruction to the agent is handled with mediating assistants, or Intelligent Briefing and Response Assistant (IBRA). The IBRA Engine also watches data stream for triggers and executes Act-Whenever actions. There is also a Briefing and Response Instruction (BRI) which is easy for a discipline specialist to create through a BRI editor.

  2. Autonomous Satellite Operations Via Secure Virtual Mission Operations Center

    NASA Technical Reports Server (NTRS)

    Miller, Eric; Paulsen, Phillip E.; Pasciuto, Michael

    2011-01-01

    The science community is interested in improving their ability to respond to rapidly evolving, transient phenomena via autonomous rapid reconfiguration, which derives from the ability to assemble separate but collaborating sensors and data forecasting systems to meet a broad range of research and application needs. Current satellite systems typically require human intervention to respond to triggers from dissimilar sensor systems. Additionally, satellite ground services often need to be coordinated days or weeks in advance. Finally, the boundaries between the various sensor systems that make up such a Sensor Web are defined by such things as link delay and connectivity, data and error rate asymmetry, data reliability, quality of service provisions, and trust, complicating autonomous operations. Over the past ten years, researchers from the NASA Glenn Research Center (GRC), General Dynamics, Surrey Satellite Technology Limited (SSTL), Cisco, Universal Space Networks (USN), the U.S. Geological Survey (USGS), the Naval Research Laboratory, the DoD Operationally Responsive Space (ORS) Office, and others have worked collaboratively to develop a virtual mission operations capability. Called VMOC (Virtual Mission Operations Center), this new capability allows cross-system queuing of dissimilar mission unique systems through the use of a common security scheme and published application programming interfaces (APIs). Collaborative VMOC demonstrations over the last several years have supported the standardization of spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of new tactics, techniques and procedures that lead to responsive space employment.

  3. Concurrent engineering: Spacecraft and mission operations system design

    NASA Technical Reports Server (NTRS)

    Landshof, J. A.; Harvey, R. J.; Marshall, M. H.

    1994-01-01

    Despite our awareness of the mission design process, spacecraft historically have been designed and developed by one team and then turned over as a system to the Mission Operations organization to operate on-orbit. By applying concurrent engineering techniques and envisioning operability as an essential characteristic of spacecraft design, tradeoffs can be made in the overall mission design to minimize mission lifetime cost. Lessons learned from previous spacecraft missions will be described, as well as the implementation of concurrent mission operations and spacecraft engineering for the Near Earth Asteroid Rendezvous (NEAR) program.

  4. TAMU: A New Space Mission Operations Paradigm

    NASA Technical Reports Server (NTRS)

    Meshkat, Leila; Ruszkowski, James; Haensly, Jean; Pennington, Granvil A.; Hogle, Charles

    2011-01-01

    The Transferable, Adaptable, Modular and Upgradeable (TAMU) Flight Production Process (FPP) is a model-centric System of System (SoS) framework which cuts across multiple organizations and their associated facilities, that are, in the most general case, in geographically diverse locations, to develop the architecture and associated workflow processes for a broad range of mission operations. Further, TAMU FPP envisions the simulation, automatic execution and re-planning of orchestrated workflow processes as they become operational. This paper provides the vision for the TAMU FPP paradigm. This includes a complete, coherent technique, process and tool set that result in an infrastructure that can be used for full lifecycle design and decision making during any flight production process. A flight production process is the process of developing all products that are necessary for flight.

  5. Mission operations and command assurance: Instilling quality into flight operations

    NASA Astrophysics Data System (ADS)

    Welz, Linda L.; Witkowski, Mona M.; Bruno, Kristin J.; Potts, Sherrill S.

    1993-03-01

    Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous process improvement to reduce the probability of radiating incorrect commands to a spacecraft. The MO&CA task has evolved from participating as a member of the spacecraft team to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

  6. Mission operations and command assurance: Instilling quality into flight operations

    NASA Technical Reports Server (NTRS)

    Welz, Linda L.; Witkowski, Mona M.; Bruno, Kristin J.; Potts, Sherrill S.

    1993-01-01

    Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous process improvement to reduce the probability of radiating incorrect commands to a spacecraft. The MO&CA task has evolved from participating as a member of the spacecraft team to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

  7. Lean Mission Operations Systems Design - Using Agile and Lean Development Principles for Mission Operations Design and Development

    NASA Technical Reports Server (NTRS)

    Trimble, Jay Phillip

    2014-01-01

    The Resource Prospector Mission seeks to rove the lunar surface with an in-situ resource utilization payload in search of volatiles at a polar region. The mission operations system (MOS) will need to perform the short-duration mission while taking advantage of the near real time control that the short one-way light time to the Moon provides. To maximize our use of limited resources for the design and development of the MOS we are utilizing agile and lean methods derived from our previous experience with applying these methods to software. By using methods such as "say it then sim it" we will spend less time in meetings and more time focused on the one outcome that counts - the effective utilization of our assets on the Moon to meet mission objectives.

  8. Web Based Tool for Mission Operations Scenarios

    NASA Technical Reports Server (NTRS)

    Boyles, Carole A.; Bindschadler, Duane L.

    2008-01-01

    A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum

  9. Web Based Tool for Mission Operations Scenarios

    NASA Technical Reports Server (NTRS)

    Boyles, Carole A.; Bindschadler, Duane L.

    2008-01-01

    A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum

  10. Maintenance of Space Station Freedom - The role of mission controllers

    NASA Technical Reports Server (NTRS)

    Watson, J. K.; Davison, M. T.; Langendorf, S. E.

    1991-01-01

    The key roles played in the on-orbit maintenance of Space Station Freedom by mission controllers working in the Space Station Control Center are discussed. Responsibilities ranging from planning and procedure development to training and real-time support are addressed. The organization of the Mission Operations Directorate is described.

  11. Mission Analysis, Operations, and Navigation Toolkit Environment (Monte) Version 040

    NASA Technical Reports Server (NTRS)

    Sunseri, Richard F.; Wu, Hsi-Cheng; Evans, Scott E.; Evans, James R.; Drain, Theodore R.; Guevara, Michelle M.

    2012-01-01

    Monte is a software set designed for use in mission design and spacecraft navigation operations. The system can process measurement data, design optimal trajectories and maneuvers, and do orbit determination, all in one application. For the first time, a single software set can be used for mission design and navigation operations. This eliminates problems due to different models and fidelities used in legacy mission design and navigation software. The unique features of Monte 040 include a blowdown thruster model for GRAIL (Gravity Recovery and Interior Laboratory) with associated pressure models, as well as an updated, optimalsearch capability (COSMIC) that facilitated mission design for ARTEMIS. Existing legacy software lacked the capabilities necessary for these two missions. There is also a mean orbital element propagator and an osculating to mean element converter that allows long-term orbital stability analysis for the first time in compiled code. The optimized trajectory search tool COSMIC allows users to place constraints and controls on their searches without any restrictions. Constraints may be user-defined and depend on trajectory information either forward or backwards in time. In addition, a long-term orbit stability analysis tool (morbiter) existed previously as a set of scripts on top of Monte. Monte is becoming the primary tool for navigation operations, a core competency at JPL. The mission design capabilities in Monte are becoming mature enough for use in project proposals as well as post-phase A mission design. Monte has three distinct advantages over existing software. First, it is being developed in a modern paradigm: object- oriented C++ and Python. Second, the software has been developed as a toolkit, which allows users to customize their own applications and allows the development team to implement requirements quickly, efficiently, and with minimal bugs. Finally, the software is managed in accordance with the CMMI (Capability Maturity Model

  12. Reinventing User Applications for Mission Control

    NASA Technical Reports Server (NTRS)

    Trimble, Jay Phillip; Crocker, Alan R.

    2010-01-01

    In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous

  13. NASA Extreme Environment Mission Operations: Science Operations Development for Human Exploration

    NASA Technical Reports Server (NTRS)

    Bell, Mary S.

    2014-01-01

    The purpose of NASA Extreme Environment Mission Operations (NEEMO) mission 16 in 2012 was to evaluate and compare the performance of a defined series of representative near-Earth asteroid (NEA) extravehicular activity (EVA) tasks under different conditions and combinations of work systems, constraints, and assumptions considered for future human NEA exploration missions. NEEMO 16 followed NASA's 2011 Desert Research and Technology Studies (D-RATS), the primary focus of which was understanding the implications of communication latency, crew size, and work system combinations with respect to scientific data quality, data management, crew workload, and crew/mission control interactions. The 1-g environment precluded meaningful evaluation of NEA EVA translation, worksite stabilization, sampling, or instrument deployment techniques. Thus, NEEMO missions were designed to provide an opportunity to perform a preliminary evaluation of these important factors for each of the conditions being considered. NEEMO 15 also took place in 2011 and provided a first look at many of the factors, but the mission was cut short due to a hurricane threat before all objectives were completed. ARES Directorate (KX) personnel consulted with JSC engineers to ensure that high-fidelity planetary science protocols were incorporated into NEEMO mission architectures. ARES has been collaborating with NEEMO mission planners since NEEMO 9 in 2006, successively building upon previous developments to refine science operations concepts within engineering constraints; it is expected to continue the collaboration as NASA's human exploration mission plans evolve.

  14. Flight Controllers in Mission Control Center during splashdown of Apollo 14

    NASA Image and Video Library

    1971-02-09

    S71-18400 (9 Feb. 1971) --- Flight controllers in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) view a colorful display which signals the successful splashdown and recovery of the crew of the Apollo 14 lunar landing mission. The MOCR's large screen at right shows a television shot aboard the USS New Orleans, Apollo 14 prime recovery ship.

  15. Hypermedia and intelligent tutoring applications in a mission operations environment

    NASA Technical Reports Server (NTRS)

    Ames, Troy; Baker, Clifford

    1990-01-01

    Hypermedia, hypertext and Intelligent Tutoring System (ITS) applications to support all phases of mission operations are investigated. The application of hypermedia and ITS technology to improve system performance and safety in supervisory control is described - with an emphasis on modeling operator's intentions in the form of goals, plans, tasks, and actions. Review of hypermedia and ITS technology is presented as may be applied to the tutoring of command and control languages. Hypertext based ITS is developed to train flight operation teams and System Test and Operation Language (STOL). Specific hypermedia and ITS application areas are highlighted, including: computer aided instruction of flight operation teams (STOL ITS) and control center software development tools (CHIMES and STOL Certification Tool).

  16. View of Mission Control Center during Apollo 13 splashdown

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Overall view of Mission Operations Control Room in Mission Control Center at the Manned Spacecraft Center (MSC) during the ceremonies aboard the U.S.S. Iwo Jima, prime recovery ship for the Apollo 13 mission. The Apollo 13 spacecraft, with Astronauts James Lovell, John Swigert, and Fred Haise aboard splashed down in the South Pacific at 12:07:44 p.m., April 17, 1970.

  17. View of Mission Control Center during the Apollo 13 liftoff

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Sigurd A. Sjoberg, Director of Flight Operations at Manned Spacecraft Center (MSC), views the Apollo 13 liftoff from a console in the MSC Mission Control Center, bldg 30. Apollo 13 lifted off at 1:13 p.m., April 11, 1970 (34627); Astronaut Thomas F. Mattingly II, who was scheduled as a prime crewman for the Apollo 13 mission but was replaced in the final hours when it was discovered he had been exposed to measles, watches the liftoff phase of the mission. He is seated at a console in the Mission Control Center's Mission Operations Control Room. Scientist-Astronaut Joseph P. Kerwin, a spacecraft communicator for the mission, looks on at right (34628).

  18. Lunar Precursor Missions for Human Exploration of Mars - II. Studies of Mission Operations

    NASA Astrophysics Data System (ADS)

    Mendell, W. W.; Griffith, A. D.

    necessary precursor to human missions to Mars. He observed that mission parameters for Mars expeditions far exceed current and projected near-term space operations experience in categories such as duration, scale, logistics, required system reliability, time delay for communications, crew exposure to the space environment (particularly reduced gravity), lack of abort-to-Earth options, degree of crew isolation, and long-term political commitment. He demonstrated how a program of lunar exploration could be structured to expand the experience base, test operations approaches, and validate proposed technologies. In this paper, we plan to expand the discussion on the topic of mission operations, including flight and trajectory design, crew activity planning, procedure development and validation, and initialization load development. contemplating the nature of the challenges posed by a mission with a single crew lasting 3 years with no possibility of abort to Earth and at a distance where the light-time precludes conversation between with the astronauts. The brief durations of Apollo or Space Shuttle missions mandates strict scheduling of in-space tasks to maximize the productivity. On a mission to Mars, the opposite obtains. Transit times are long (~160 days), and crew time may be principally devoted to physical conditioning and repeated simulations of the landing sequence. While the physical exercise parallels the experience on the International Space Station (ISS), the remote refresher training is new. The extensive surface stay time (~500 days) implies that later phases of the surface missions will have to be planned in consultation with the crew to a large extent than is currently the case. resolve concerns over the form of new methodologies and philosophies needed. Recent proposed reductions in scope and crew size for ISS exacerbate this problem. One unknown aspect is whether any sociological pathologies will develop in the relationship of the crew to Mission

  19. Calculation of Operations Efficiency Factors for Mars Surface Missions

    NASA Technical Reports Server (NTRS)

    Layback, Sharon L.

    2014-01-01

    For planning of Mars surface missions, to be operated on a sol-by-sol basis by a team on Earth (where a "sol" is a Martian day), activities are described in terms of "sol types" that are strung together to build a surface mission scenario. Some sol types require ground decisions based on a previous sol's results to feed into the activity planning ("ground in the loop"), while others do not. Due to the differences in duration between Earth days and Mars sols, for a given Mars local solar time, the corresponding Earth time "walks" relative to the corresponding times on the prior sol/day. In particular, even if a communication window has a fixed Mars local solar time, the Earth time for that window will be approximately 40 minutes later each succeeding day. Further complexity is added for non-Mars synchronous communication relay assets, and when there are multiple control centers in different Earth time zones. The solution is the development of "ops efficiency factors" that reflect the efficiency of a given operations configuration (how many and location of control centers, types of communication windows, synchronous or non-synchronous nature of relay assets, sol types, more-or-less sustainable operations schedule choices) against a theoretical "optimal" operations configuration for the mission being studied. These factors are then incorporated into scenario models in order to determine the surface duration (and therefore minimum spacecraft surface lifetime) required to fulfill scenario objectives. The resulting model is used to perform "what-if" analyses for variations in scenario objectives. The ops efficiency factor is the ratio of the figure of merit for a given operations factor to the figure of merit for the theoretical optimal configuration. The current implementation is a pair of models in Excel. The first represents a ground operations schedule for 500 sols in each operations configuration for the mission being studied (500 sols was chosen as being a long

  20. New Human-Computer Interface Concepts for Mission Operations

    NASA Technical Reports Server (NTRS)

    Fox, Jeffrey A.; Hoxie, Mary Sue; Gillen, Dave; Parkinson, Christopher; Breed, Julie; Nickens, Stephanie; Baitinger, Mick

    2000-01-01

    The current climate of budget cuts has forced the space mission operations community to reconsider how it does business. Gone are the days of building one-of-kind control centers with teams of controllers working in shifts 24 hours per day, 7 days per week. Increasingly, automation is used to significantly reduce staffing needs. In some cases, missions are moving towards lights-out operations where the ground system is run semi-autonomously. On-call operators are brought in only to resolve anomalies. Some operations concepts also call for smaller operations teams to manage an entire family of spacecraft. In the not too distant future, a skeleton crew of full-time general knowledge operators will oversee the operations of large constellations of small spacecraft, while geographically distributed specialists will be assigned to emergency response teams based on their expertise. As the operations paradigms change, so too must the tools to support the mission operations team's tasks. Tools need to be built not only to automate routine tasks, but also to communicate varying types of information to the part-time, generalist, or on-call operators and specialists more effectively. Thus, the proper design of a system's user-system interface (USI) becomes even more importance than before. Also, because the users will be accessing these systems from various locations (e.g., control center, home, on the road) via different devices with varying display capabilities (e.g., workstations, home PCs, PDAS, pagers) over connections with various bandwidths (e.g., dial-up 56k, wireless 9.6k), the same software must have different USIs to support the different types of users, their equipment, and their environments. In other words, the software must now adapt to the needs of the users! This paper will focus on the needs and the challenges of designing USIs for mission operations. After providing a general discussion of these challenges, the paper will focus on the current efforts of

  1. SCOSII OL: A dedicated language for mission operations

    NASA Technical Reports Server (NTRS)

    Baldi, Andrea; Elgaard, Dennis; Lynenskjold, Steen; Pecchioli, Mauro

    1994-01-01

    The Spacecraft Control and Operations System 2 (SCOSII) is the new generation of Mission Control Systems (MCS) to be used at ESOC. The system is generic because it offers a collection of standard functions configured through a database upon which a dedicated MCS is established for a given mission. An integral component of SCOSII is the support of a dedicated Operations Language (OL). The spacecraft operation engineers edit, test, validate, and install OL scripts as part of the configuration of the system with, e.g., expressions for computing derived parameters and procedures for performing flight operations, all without involvement of software support engineers. A layered approach has been adopted for the implementation centered around the explicit representation of a data model. The data model is object-oriented defining the structure of the objects in terms of attributes (data) and services (functions) which can be accessed by the OL. SCOSII supports the creation of a mission model. System elements as, e.g., a gyro are explicit, as are the attributes which described them and the services they provide. The data model driven approach makes it possible to take immediate advantage of this higher-level of abstraction, without requiring expansion of the language. This article describes the background and context leading to the OL, concepts, language facilities, implementation, status and conclusions found so far.

  2. NASA Sample Return Missions: Recovery Operations

    NASA Technical Reports Server (NTRS)

    Pace, L. F.; Cannon, R. E.

    2017-01-01

    The Utah Test and Training Range (UTTR), southwest of Salt Lake City, Utah, is the site of all NASA unmanned sample return missions. To date these missions include the Genesis solar wind samples (2004) and Stardust cometary and interstellar dust samples (2006). NASA’s OSIRIS-REx Mission will return its first asteroid sample at UTTR in 2023.

  3. Mission Operations of Earth Observing-1 with Onboard Autonomy

    NASA Technical Reports Server (NTRS)

    Rabideau, Gregg; Tran, Daniel Q.; Chien, Steve; Cichy, Benjamin; Sherwood, Rob; Mandl, Dan; Frye, Stuart; Shulman, Seth; Szwaczkowski, Joseph; Boyer, Darrell; hide

    2006-01-01

    Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the past mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the more autonomous operations to which we transferred as part of the Autonomous Sciencecraft Experiment (ASE).

  4. Mission Operations of Earth Observing-1 with Onboard Autonomy

    NASA Technical Reports Server (NTRS)

    Rabideau, Gregg; Tran, Daniel Q.; Chien, Steve; Cichy, Benjamin; Sherwood, Rob; Mandl, Dan; Frye, Stuart; Shulman, Seth; Szwaczkowski, Joseph; Boyer, Darrell; VanGaasbeck, Jim

    2006-01-01

    Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the past mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the more autonomous operations to which we transferred as part of the Autonomous Sciencecraft Experiment (ASE).

  5. MISSION CONTROL CENTER (MCC) - GEMINI-TITAN (GT)-7 - MSC

    NASA Image and Video Library

    1965-12-07

    S65-60039 (7 Dec. 1965) --- Christopher C. Kraft Jr. (left), assistant director for Flight Operations, monitors his console in the Mission Control Center during the Gemini-7 spaceflight. Photo credit: NASA

  6. Mission Operations of the Mars Exploration Rovers

    NASA Technical Reports Server (NTRS)

    Bass, Deborah; Lauback, Sharon; Mishkin, Andrew; Limonadi, Daniel

    2007-01-01

    A document describes a system of processes involved in planning, commanding, and monitoring operations of the rovers Spirit and Opportunity of the Mars Exploration Rover mission. The system is designed to minimize command turnaround time, given that inherent uncertainties in terrain conditions and in successful completion of planned landed spacecraft motions preclude planning of some spacecraft activities until the results of prior activities are known by the ground-based operations team. The processes are partitioned into those (designated as tactical) that must be tied to the Martian clock and those (designated strategic) that can, without loss, be completed in a more leisurely fashion. The tactical processes include assessment of downlinked data, refinement and validation of activity plans, sequencing of commands, and integration and validation of sequences. Strategic processes include communications planning and generation of long-term activity plans. The primary benefit of this partition is to enable the tactical portion of the team to focus solely on tasks that contribute directly to meeting the deadlines for commanding the rover s each sol (1 sol = 1 Martian day) - achieving a turnaround time of 18 hours or less, while facilitating strategic team interactions with other organizations that do not work on a Mars time schedule.

  7. Remote Operations Control Center (ROCC)

    NASA Technical Reports Server (NTRS)

    1997-01-01

    Undergraduate students Kristina Wines and Dena Renzo at Rensselaer Poloytech Institute (RPI) in Troy, NY, monitor the progress of the Isothermal Dendritic Growth Experiment (IDGE) during the U.S. Microgravity Payload-4 (USMP-4) mission (STS-87), Nov. 19 - Dec.5, 1997). Remote Operations Control Center (ROCC) like this one will become more common during operations with the International Space Station. The Isothermal Dendritic Growth Experiment (IDGE), flown on three Space Shuttle missions, is yielding new insights into virtually all industrially relevant metal and alloy forming operations. Photo credit: Rensselaer Polytechnic Institute (RPI)

  8. Remote Operations Control Center (ROCC)

    NASA Technical Reports Server (NTRS)

    1997-01-01

    Matthew Koss (forground) and Martin Glicksman (rear), principal investigator and lead scientist (respectively), review plans for the next step in the Isothermal Dendritic Growth Experiment (IDGE) during the U.S. Microgravity Payload-4 (USMP-4) mission (STS-87, Nov. 19 - Dec. 5, 1997). Remote Operations Control Center (ROCC) like this one, at Rensselaer Polytechnic Institute (RPI) in Troy, NY, will become more common during operations with the International Space Station. IDGE, flown on three Space Shuttle missions, is yielding new insights into virtually all industrially relavent metal and alloy forming operations. Photo credit: Rensselaer Polytechnic Institute (RPI)

  9. Mission Control Center (MCC) View - Skylab (SL)-3 Recovery - JSC

    NASA Image and Video Library

    1973-09-27

    S73-34553 (25 Sept. 1973) --- Skylab flight directors (foreground) and flight controllers (background) view the large screen in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) at JSC during recovery operations of the second manned Skylab mission. From left to right in the foreground are flight directors Charles R. Lewis, Donald R. Puffy, Phillip Shaffer and Neil B. Hutchinson. The Skylab 3 crewmen were preparing to egress the spacecraft aboard the USS New Orleans. Television cameras aboard the New Orleans recorded post-recovery activity. Photo credit: NASA

  10. Views of the mission control center during STS-9

    NASA Technical Reports Server (NTRS)

    1983-01-01

    The two backup payload specialists for Drs. Byron K. Lichtenberg and Ulf Merbold huddle in the mission control center during day three activity aboard Spacelab. Seated at the Console is Dr. Michael Lampton. Leaning over Lampton's shoulder is Dutch scientist Wubbo Ockels. The two are surrounded by a few of the flight controllers in the payload operations control center (POCC) portion of JSC's mission control center.

  11. Apollo 11 Celebration at Mission Control

    NASA Technical Reports Server (NTRS)

    1969-01-01

    NASA and Manned Spacecraft Center (MSC) officials join the flight controllers in celebrating the conclusion of the Apollo 11 mission. From left foreground Dr. Maxime A. Faget, MSC Director of Engineering and Development; George S. Trimble, MSC Deputy Director; Dr. Christopher C. Kraft Jr., MSC Director fo Flight Operations; Julian Scheer (in back), Assistant Adminstrator, Office of Public Affairs, NASA HQ.; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Robert R. Gilruth, MSC Director; and Charles W. Mathews, Deputy Associate Administrator, Office of Manned Space Flight, NASA HQ.

  12. Mission Control activities during Day 1 First TV Pass of STS-11

    NASA Technical Reports Server (NTRS)

    1984-01-01

    Robert E. Castle, integrated communications officer (INCO), at a console in the JSC mission operations control room (MOCR) in the mission control center. He is responsible for ground controlled television from the orbiter on his shift for 41-B.

  13. A distributed computing approach to mission operations support. [for spacecraft

    NASA Technical Reports Server (NTRS)

    Larsen, R. L.

    1975-01-01

    Computing mission operation support includes orbit determination, attitude processing, maneuver computation, resource scheduling, etc. The large-scale third-generation distributed computer network discussed is capable of fulfilling these dynamic requirements. It is shown that distribution of resources and control leads to increased reliability, and exhibits potential for incremental growth. Through functional specialization, a distributed system may be tuned to very specific operational requirements. Fundamental to the approach is the notion of process-to-process communication, which is effected through a high-bandwidth communications network. Both resource-sharing and load-sharing may be realized in the system.

  14. Designing Mission Operations for the Gravity Recovery and Interior Laboratory Mission

    NASA Technical Reports Server (NTRS)

    Havens, Glen G.; Beerer, Joseph G.

    2012-01-01

    NASA's Gravity Recovery and Interior Laboratory (GRAIL) mission, to understand the internal structure and thermal evolution of the Moon, offered unique challenges to mission operations. From launch through end of mission, the twin GRAIL orbiters had to be operated in parallel. The journey to the Moon and into the low science orbit involved numerous maneuvers, planned on tight timelines, to ultimately place the orbiters into the required formation-flying configuration necessary. The baseline GRAIL mission is short, only 9 months in duration, but progressed quickly through seven very unique mission phases. Compressed into this short mission timeline, operations activities and maneuvers for both orbiters had to be planned and coordinated carefully. To prepare for these challenges, development of the GRAIL Mission Operations System began in 2008. Based on high heritage multi-mission operations developed by NASA's Jet Propulsion Laboratory and Lockheed Martin, the GRAIL mission operations system was adapted to meet the unique challenges posed by the GRAIL mission design. This paper describes GRAIL's system engineering development process for defining GRAIL's operations scenarios and generating requirements, tracing the evolution from operations concept through final design, implementation, and validation.

  15. Cloud Computing for Mission Design and Operations

    NASA Technical Reports Server (NTRS)

    Arrieta, Juan; Attiyah, Amy; Beswick, Robert; Gerasimantos, Dimitrios

    2012-01-01

    The space mission design and operations community already recognizes the value of cloud computing and virtualization. However, natural and valid concerns, like security, privacy, up-time, and vendor lock-in, have prevented a more widespread and expedited adoption into official workflows. In the interest of alleviating these concerns, we propose a series of guidelines for internally deploying a resource-oriented hub of data and algorithms. These guidelines provide a roadmap for implementing an architecture inspired in the cloud computing model: associative, elastic, semantical, interconnected, and adaptive. The architecture can be summarized as exposing data and algorithms as resource-oriented Web services, coordinated via messaging, and running on virtual machines; it is simple, and based on widely adopted standards, protocols, and tools. The architecture may help reduce common sources of complexity intrinsic to data-driven, collaborative interactions and, most importantly, it may provide the means for teams and agencies to evaluate the cloud computing model in their specific context, with minimal infrastructure changes, and before committing to a specific cloud services provider.

  16. Cloud Computing for Mission Design and Operations

    NASA Technical Reports Server (NTRS)

    Arrieta, Juan; Attiyah, Amy; Beswick, Robert; Gerasimantos, Dimitrios

    2012-01-01

    The space mission design and operations community already recognizes the value of cloud computing and virtualization. However, natural and valid concerns, like security, privacy, up-time, and vendor lock-in, have prevented a more widespread and expedited adoption into official workflows. In the interest of alleviating these concerns, we propose a series of guidelines for internally deploying a resource-oriented hub of data and algorithms. These guidelines provide a roadmap for implementing an architecture inspired in the cloud computing model: associative, elastic, semantical, interconnected, and adaptive. The architecture can be summarized as exposing data and algorithms as resource-oriented Web services, coordinated via messaging, and running on virtual machines; it is simple, and based on widely adopted standards, protocols, and tools. The architecture may help reduce common sources of complexity intrinsic to data-driven, collaborative interactions and, most importantly, it may provide the means for teams and agencies to evaluate the cloud computing model in their specific context, with minimal infrastructure changes, and before committing to a specific cloud services provider.

  17. An Architecture to Promote the Commercialization of Space Mission Command and Control

    NASA Technical Reports Server (NTRS)

    Jones, Michael K.

    1996-01-01

    This paper describes a command and control architecture that encompasses space mission operations centers, ground terminals, and spacecraft. This architecture is intended to promote the growth of a lucrative space mission operations command and control market through a set of open standards used by both gevernment and profit-making space mission operators.

  18. View of Mission Control Center celebrating conclusion of Apollo 11 mission

    NASA Technical Reports Server (NTRS)

    1969-01-01

    Overall view of the Mission Operations Control Room in the Mission Control Center, bldg 30, Manned Spacecraft Center (MSC), at the conclusion of the Apollo 11 lunar landing mission. The television monitor shows President Richard M. Nixon greeting the Apollo 11 astronauts aboard the U.S.S. Hornet in the Pacific recovery area (40301); NASA and MSC Officials join the flight controllers in celebrating the conclusion of the Apollo 11 mission. From left foreground Dr. Maxime A. Faget, MSC Director of Engineering and Development; George S. Trimble, MSC Deputy Director; Dr. Christopher C. Kraft Jr., MSC Director fo Flight Operations; Julian Scheer (in back), Assistant Adminstrator, Offic of Public Affairs, NASA HQ.; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Robert R. Gilruth, MSC Director; and Charles W. Mathews, Deputy Associate Administrator, Office of Manned Space Flight, NASA HQ (40302).

  19. Mars Telecom Orbiter mission operations concepts

    NASA Technical Reports Server (NTRS)

    Deutsch, Marie-Jose; Komarek, Tom; Lopez, Saturnino; Townes, Steve; Synnott, Steve; Austin, Richard; Guinn, Joe; Varghese, Phil; Edwards, Bernard; Bondurant, Roy; De Paula, Ramon

    2004-01-01

    The Mars Telecom Orbiter (MTO) relay capability enables next decadal missions at Mars, collecting gigabits of data a day to be relayed back at speeds exceeding 4 Mbps and it facilitates small missions whose limited resources do not permit them to have a direct link to Earth.

  20. Vehicle management and mission planning in support of shuttle operations.

    NASA Technical Reports Server (NTRS)

    Pruett, W. R.; Bell, J. A.

    1973-01-01

    An operational approach to shuttle mission planning during high flight frequency years (20 or more flights per year) is described wherein diverse mission planning functions interface via an interactive computer system and common data base. The Vehicle Management and Mission Planning System (VMMPS) is proposed as a means of helping to accomplish the mission planning function. The VMMPS will link together into an interactive system the major mission planning areas such as trajectory, crew, vehicle performance, and launch operations. A common data base will be an integral part of the system and the concept of standard mission types and phases will be used to minimize mission to mission uniqueness. The use of this system will eliminate much redundancy and replanning, shorten interface times between functions, and provide a means to evaluate unplanned events and modify schedules.

  1. Vehicle management and mission planning in support of shuttle operations.

    NASA Technical Reports Server (NTRS)

    Pruett, W. R.; Bell, J. A.

    1973-01-01

    An operational approach to shuttle mission planning during high flight frequency years (20 or more flights per year) is described wherein diverse mission planning functions interface via an interactive computer system and common data base. The Vehicle Management and Mission Planning System (VMMPS) is proposed as a means of helping to accomplish the mission planning function. The VMMPS will link together into an interactive system the major mission planning areas such as trajectory, crew, vehicle performance, and launch operations. A common data base will be an integral part of the system and the concept of standard mission types and phases will be used to minimize mission to mission uniqueness. The use of this system will eliminate much redundancy and replanning, shorten interface times between functions, and provide a means to evaluate unplanned events and modify schedules.

  2. Management of information for mission operations using automated keyword referencing

    NASA Technical Reports Server (NTRS)

    Davidson, Roger A.; Curran, Patrick S.

    1993-01-01

    Although millions of dollars have helped to improve the operability and technology of ground data systems for mission operations, almost all mission documentation remains bound in printed volumes. This form of documentation is difficult and timeconsuming to use, may be out-of-date, and is usually not cross-referenced with other related volumes of mission documentation. A more effective, automated method of mission information access is needed. A new method of information management for mission operations using automated keyword referencing is proposed. We expound on the justification for and the objectives of this concept. The results of a prototype tool for mission information access that uses a hypertextlike user interface and existing mission documentation are shared. Finally, the future directions and benefits of our proposed work are described.

  3. STS payloads mission control study continuation phase A-1. Volume 2-B: Task 2. Evaluation and refinement of implementation guidelines for the selected STS payload operator concept

    NASA Technical Reports Server (NTRS)

    1976-01-01

    The functions of Payload Operations Control Centers (POCC) at JSC, GSFC, JPL, and non-NASA locations are analyzed to establish guidelines for standardization, and facilitate the development of a fully integrated NASA-wide system of ground facilities for all classes of payloads. Operational interfaces between the space transportation system operator and the payload operator elements are defined. The advantages and disadvantages of standardization are discussed.

  4. Avoiding Human Error in Mission Operations: Cassini Flight Experience

    NASA Technical Reports Server (NTRS)

    Burk, Thomas A.

    2012-01-01

    Operating spacecraft is a never-ending challenge and the risk of human error is ever- present. Many missions have been significantly affected by human error on the part of ground controllers. The Cassini mission at Saturn has not been immune to human error, but Cassini operations engineers use tools and follow processes that find and correct most human errors before they reach the spacecraft. What is needed are skilled engineers with good technical knowledge, good interpersonal communications, quality ground software, regular peer reviews, up-to-date procedures, as well as careful attention to detail and the discipline to test and verify all commands that will be sent to the spacecraft. Two areas of special concern are changes to flight software and response to in-flight anomalies. The Cassini team has a lot of practical experience in all these areas and they have found that well-trained engineers with good tools who follow clear procedures can catch most errors before they get into command sequences to be sent to the spacecraft. Finally, having a robust and fault-tolerant spacecraft that allows ground controllers excellent visibility of its condition is the most important way to ensure human error does not compromise the mission.

  5. Avoiding Human Error in Mission Operations: Cassini Flight Experience

    NASA Technical Reports Server (NTRS)

    Burk, Thomas A.

    2012-01-01

    Operating spacecraft is a never-ending challenge and the risk of human error is ever- present. Many missions have been significantly affected by human error on the part of ground controllers. The Cassini mission at Saturn has not been immune to human error, but Cassini operations engineers use tools and follow processes that find and correct most human errors before they reach the spacecraft. What is needed are skilled engineers with good technical knowledge, good interpersonal communications, quality ground software, regular peer reviews, up-to-date procedures, as well as careful attention to detail and the discipline to test and verify all commands that will be sent to the spacecraft. Two areas of special concern are changes to flight software and response to in-flight anomalies. The Cassini team has a lot of practical experience in all these areas and they have found that well-trained engineers with good tools who follow clear procedures can catch most errors before they get into command sequences to be sent to the spacecraft. Finally, having a robust and fault-tolerant spacecraft that allows ground controllers excellent visibility of its condition is the most important way to ensure human error does not compromise the mission.

  6. Magellan Post Launch Mission Operation Report

    NASA Technical Reports Server (NTRS)

    1982-01-01

    Magellan was successfully launched by the Space Shuttle Atlantis from the Kennedy Space Center at 2:47 p.m. EDT on May 4, 1989. The Inertial Upper Stage (IUS) booster and attached Magellan Spacecraft were successfully deployed from Atlantis on Rev. 5 as planned, at 06:14 hrs Mission Elapsed Time (MET). The two IUS propulsion burns which began at 07:14 hrs MET and were completed at 07:22 hrs MET, placed the Magellan Spacecraft almost perfectly on its preplanned trajectory to Venus. The IUS was jettisoned at 07:40 hrs MET and Magellan telemetry was immediately acquired by the Deep Space Network (DSN). A spacecraft trajectory correction maneuver was performed on May 21 and the spacecraft is in the planned standard cruise configuration with all systems operating nominally. An initial attempt was made to launch Atlantis on April 28, 1989, but the launch was scrubbed at T-31 sec due to a failure of the liquid hydrogen recirculation pump on Space Shuttle Main Engine #1. The countdown had proceeded smoothly until T-20 min when the Magellan radio receiver "locked-on" the MIL 71 Unified S-Band (USB) transmission as the transmitter power was increased fro 2 kw to 10 kw in support of the orbiter launch. During the planned hold at T-9 min, the USB was confirmed as the source of the receiver "lock" and Magellan's launch readiness was reaffirmed. In addition a five-minute extension of the T-9 hold occurred when a range safety computer went off-line, creating a loss of redundancy in the range safety computer network. Following resumption of the countdown, both the orbiter and Magellan flows proceeded smoothly until the launch was scrubbed at T-31 sec.

  7. Timeline-Based Mission Operations Architecture: An Overview

    NASA Technical Reports Server (NTRS)

    Chung, Seung H.; Bindschadler, Duane L.

    2012-01-01

    Some of the challenges in developing a mission operations system and operating a mission can be traced back to the challenge of integrating a mission operations system from its many components and to the challenge of maintaining consistent and accountable information throughout the operations processes. An important contributing factor to both of these challenges is the file-centric nature of today's systems. In this paper, we provide an overview of these challenges and argue the need to move toward an information-centric mission operations system. We propose an information representation called Timeline as an approach to enable such a move, and we provide an overview of a Timeline-based Mission Operations System architecture.

  8. Rapid Turnaround of Costing/Designing of Space Missions Operations

    NASA Technical Reports Server (NTRS)

    Kudrle, Paul D.; Welz, Gregory A.; Basilio, Eleanor

    2008-01-01

    The Ground Segment Team (GST), at NASA's Jet Propulsion Laboratory in Pasadena, California, provides high-level mission operations concepts and cost estimates for projects that are in the formulation phase. GST has developed a tool to track costs, assumptions, and mission requirements, and to rapidly turnaround estimates for mission operations, ground data systems, and tracking for deep space and near Earth missions. Estimates that would often take several weeks to generate are now generated in minutes through the use of an integrated suite of cost models. The models were developed through interviews with domain experts in areas of Mission Operations, including but not limited to: systems engineering, payload operations, tracking resources, mission planning, navigation, telemetry and command, and ground network infrastructure. Data collected during interviews were converted into parametric cost models and integrated into one tool suite. The tool has been used on a wide range of missions from small Earth orbiters, to flagship missions like Cassini. The tool is an aid to project managers and mission planners as they consider different scenarios during the proposal and early development stages of their missions. The tool is also used for gathering cost related requirements and assumptions and for conducting integrated analysis of multiple missions.

  9. Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

    NASA Technical Reports Server (NTRS)

    Martin, Keith; Sen-Roy, Michael; Heiman, Jennifer

    2009-01-01

    Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits

  10. Re-Engineering the Mission Operations System (MOS) for the Prime and Extended Mission

    NASA Technical Reports Server (NTRS)

    Hunt, Joseph C., Jr.; Cheng, Leo Y.

    2012-01-01

    One of the most challenging tasks in a space science mission is designing the Mission Operations System (MOS). Whereas the focus of the project is getting the spacecraft built and tested for launch, the mission operations engineers must build a system to carry out the science objectives. The completed MOS design is then formally assessed in the many reviews. Once a mission has completed the reviews, the Mission Operation System (MOS) design has been validated to the Functional Requirements and is ready for operations. The design was built based on heritage processes, new technology, and lessons learned from past experience. Furthermore, our operational concepts must be properly mapped to the mission design and science objectives. However, during the course of implementing the science objective in the operations phase after launch, the MOS experiences an evolutional change to adapt for actual performance characteristics. This drives the re-engineering of the MOS, because the MOS includes the flight and ground segments. Using the Spitzer mission as an example we demonstrate how the MOS design evolved for both the prime and extended mission to enhance the overall efficiency for science return. In our re-engineering process, we ensured that no requirements were violated or mission objectives compromised. In most cases, optimized performance across the MOS, including gains in science return as well as savings in the budget profile was achieved. Finally, we suggest a need to better categorize the Operations Phase (Phase E) in the NASA Life-Cycle Phases of Formulation and Implementation

  11. Re-Engineering the Mission Operations System (MOS) for the Prime and Extended Mission

    NASA Technical Reports Server (NTRS)

    Hunt, Joseph C., Jr.; Cheng, Leo Y.

    2012-01-01

    One of the most challenging tasks in a space science mission is designing the Mission Operations System (MOS). Whereas the focus of the project is getting the spacecraft built and tested for launch, the mission operations engineers must build a system to carry out the science objectives. The completed MOS design is then formally assessed in the many reviews. Once a mission has completed the reviews, the Mission Operation System (MOS) design has been validated to the Functional Requirements and is ready for operations. The design was built based on heritage processes, new technology, and lessons learned from past experience. Furthermore, our operational concepts must be properly mapped to the mission design and science objectives. However, during the course of implementing the science objective in the operations phase after launch, the MOS experiences an evolutional change to adapt for actual performance characteristics. This drives the re-engineering of the MOS, because the MOS includes the flight and ground segments. Using the Spitzer mission as an example we demonstrate how the MOS design evolved for both the prime and extended mission to enhance the overall efficiency for science return. In our re-engineering process, we ensured that no requirements were violated or mission objectives compromised. In most cases, optimized performance across the MOS, including gains in science return as well as savings in the budget profile was achieved. Finally, we suggest a need to better categorize the Operations Phase (Phase E) in the NASA Life-Cycle Phases of Formulation and Implementation

  12. Mission control activity during STS-61 EVA

    NASA Image and Video Library

    1993-12-07

    Flight controller Susan P. Rainwater observes as two astronauts work through a lengthy period of extravehicular activity (EVA) in the cargo bay of the Earth-looking Space Shuttle Endeavour. Rainwater's EVA console was one of Mission Control's busiest during this eleven-day Hubble Space Telescope (HST) servicing mission in Earth orbit.

  13. EURECA mission control experience and messages for the future

    NASA Technical Reports Server (NTRS)

    Huebner, H.; Ferri, P.; Wimmer, W.

    1994-01-01

    EURECA is a retrievable space platform which can perform multi-disciplinary scientific and technological experiments in a Low Earth Orbit for a typical mission duration of six to twelve months. It is deployed and retrieved by the NASA Space Shuttle and is designed to support up to five flights. The first mission started at the end of July 1992 and was successfully completed with the retrieval in June 1993. The operations concept and the ground segment for the first EURECA mission are briefly introduced. The experiences in the preparation and the conduction of the mission from the flight control team point of view are described.

  14. Lessons Learned on Operating and Preparing Operations for a Technology Mission from the Perspective of the Earth Observing-1 Mission

    NASA Technical Reports Server (NTRS)

    Mandl, Dan; Howard, Joseph

    2000-01-01

    The New Millennium Program's first Earth-observing mission (EO-1) is a technology validation mission. It is managed by the NASA Goddard Space Flight Center in Greenbelt, Maryland and is scheduled for launch in the summer of 2000. The purpose of this mission is to flight-validate revolutionary technologies that will contribute to the reduction of cost and increase of capabilities for future land imaging missions. In the EO-1 mission, there are five instrument, five spacecraft, and three supporting technologies to flight-validate during a year of operations. EO-1 operations and the accompanying ground system were intended to be simple in order to maintain low operational costs. For purposes of formulating operations, it was initially modeled as a small science mission. However, it quickly evolved into a more complex mission due to the difficulties in effectively integrating all of the validation plans of the individual technologies. As a consequence, more operational support was required to confidently complete the on-orbit validation of the new technologies. This paper will outline the issues and lessons learned applicable to future technology validation missions. Examples of some of these include the following: (1) operational complexity encountered in integrating all of the validation plans into a coherent operational plan, (2) initial desire to run single shift operations subsequently growing to 6 "around-the-clock" operations, (3) managing changes in the technologies that ultimately affected operations, (4) necessity for better team communications within the project to offset the effects of change on the Ground System Developers, Operations Engineers, Integration and Test Engineers, S/C Subsystem Engineers, and Scientists, and (5) the need for a more experienced Flight Operations Team to achieve the necessary operational flexibility. The discussion will conclude by providing several cost comparisons for developing operations from previous missions to EO-1 and

  15. Modeling and Simulation for Mission Operations Work System Design

    NASA Technical Reports Server (NTRS)

    Sierhuis, Maarten; Clancey, William J.; Seah, Chin; Trimble, Jay P.; Sims, Michael H.

    2003-01-01

    Work System analysis and design is complex and non-deterministic. In this paper we describe Brahms, a multiagent modeling and simulation environment for designing complex interactions in human-machine systems. Brahms was originally conceived as a business process design tool that simulates work practices, including social systems of work. We describe our modeling and simulation method for mission operations work systems design, based on a research case study in which we used Brahms to design mission operations for a proposed discovery mission to the Moon. We then describe the results of an actual method application project-the Brahms Mars Exploration Rover. Space mission operations are similar to operations of traditional organizations; we show that the application of Brahms for space mission operations design is relevant and transferable to other types of business processes in organizations.

  16. Computer support for cooperative tasks in Mission Operations Centers

    NASA Technical Reports Server (NTRS)

    Fox, Jeffrey; Moore, Mike

    1994-01-01

    Traditionally, spacecraft management has been performed by fixed teams of operators in Mission Operations Centers. The team cooperatively: (1) ensures that payload(s) on spacecraft perform their work; and (2) maintains the health and safety of the spacecraft through commanding and monitoring the spacecraft's subsystems. In the future, the task demands will increase and overload the operators. This paper describes the traditional spacecraft management environment and describes a new concept in which groupware will be used to create a Virtual Mission Operations Center. Groupware tools will be used to better utilize available resources through increased automation and dynamic sharing of personnel among missions.

  17. Computer support for cooperative tasks in Mission Operations Centers

    SciTech Connect

    Fox, J.; Moore, M.

    1994-10-01

    Traditionally, spacecraft management has been performed by fixed teams of operators in Mission Operations Centers. The team cooperatively (1) ensures that payload(s) on spacecraft perform their work and (2) maintains the health and safety of the spacecraft through commanding and monitoring the spacecraft`s subsystems. In the future, the task demands will increase and overload the operators. This paper describes the traditional spacecraft management environment and describes a new concept in which groupware will be used to create a Virtual Mission Operations Center. Groupware tools will be used to better utilize available resources through increased automation and dynamic sharing of personnel among missions.

  18. Current Level of Mission Control Automation at NASA/Goddard Space Flight Center

    NASA Technical Reports Server (NTRS)

    Maks, Lori; Breed, Julie; Rackley, Michael; Powers, Edward I. (Technical Monitor)

    2001-01-01

    NASA is particularly concerned with reducing mission operations costs through increased automation. This paper examines the operations procedures within NASA Mission Control Centers in order to uncover the level of automation that currently exists within them. Based on an assessment of mission operations procedures within three representative control centers, this paper recommends specific areas where there is potential for mission cost reduction through increased automation.

  19. Safe Operation of HIFI Local Oscillator Subsystem on Herschel Mission

    NASA Astrophysics Data System (ADS)

    Michalska, Malgorzata; Juchnikowski, Grzegorz; Klein, Thomas; Leinz, Christian; Nowosielski, Witold; Orleanski, Piotr; Ward, John

    The HIFI Local Oscillator Subsystem is part of the Heterodyne Instrument for Far Infrared (HIFI) dedicated for astronomical observations,to be mounted on the ESA satellite HER- SCHEL. The Subsystem provides the local oscillator signal (480-1910 GHz) to each of the fourteen HIFI input mixers. Part of LO, the Local Oscillator Control Unit (LCU) provides the main interface between Local Oscillator Subsystem and HIFI/Herschel power and telemetry buses. The unit supplies Local Oscillator, decodes the HIFI macro-commands, programs and monitors the parameters of Ka-Band Synthesizer and THz multiplier chains and controls the operation of the whole Local Oscillator Subsystem. The unique microwave components used in HF multipliers are extremely sensitive to the proper biasing (polarity, voltage, current, presence of HF power).The ESA strategy of this mission requires full safe operation of the instrument. This requirements is covered by complex protection system implemented inside LCU. In this paper, we present the general overview of the protection system of microwave components. The different levels of protection (hardware realization and software procedures) are described as well as various reliability aspects. The functionality of LO subsystem controlled by LCU was tested in 2007. Now the flight model of HIFI instrument is integrated with the satellite and will be launched with Herschel mission in July 2008.

  20. Dust Storm Impacts on Human Mars Mission Equipment and Operations

    NASA Technical Reports Server (NTRS)

    Rucker, M. A.

    2017-01-01

    Although it is tempting to use dust impacts on Apollo lunar exploration mission equipment and operations as an analog for human Mars exploration, there are a number of important differences to consider. Apollo missions were about a week long; a human Mars mission will start at least two years before crew depart from Earth, when cargo is pre-deployed, and crewed mission duration may be over 800 days. Each Apollo mission landed at a different site; although no decisions have been made, NASA is investigating multiple human missions to a single Mars landing site, building up capability over time and lowering costs by re-using surface infrastructure. Apollo missions used two, single-use spacecraft; a human Mars mission may require as many as six craft for different phases of the mission, most of which would be re-used by subsequent crews. Apollo crews never ventured more than a few kilometers from their lander; Mars crews may take "camping trips" a hundred kilo-meters or more from their landing site, utilizing pressurized rovers to explore far from their base. Apollo mission designers weren't constrained by human for-ward contamination of the Moon; if we plan to search for evidence of life on Mars we'll have to be more careful. These differences all impact how we will mitigate and manage dust on our human Mars mission equipment and operations.

  1. Expert systems and advanced automation for space missions operations

    NASA Astrophysics Data System (ADS)

    Durrani, Sajjad H.; Perkins, Dorothy C.; Carlton, P. Douglas

    1990-10-01

    Increased complexity of space missions during the 1980s led to the introduction of expert systems and advanced automation techniques in mission operations. This paper describes several technologies in operational use or under development at the National Aeronautics and Space Administration's Goddard Space Flight Center. Several expert systems are described that diagnose faults, analyze spacecraft operations and onboard subsystem performance (in conjunction with neural networks), and perform data quality and data accounting functions. The design of customized user interfaces is discussed, with examples of their application to space missions. Displays, which allow mission operators to see the spacecraft position, orientation, and configuration under a variety of operating conditions, are described. Automated systems for scheduling are discussed, and a testbed that allows tests and demonstrations of the associated architectures, interface protocols, and operations concepts is described. Lessons learned are summarized.

  2. LANDSAT-D Mission Operations Review (MOR)

    NASA Technical Reports Server (NTRS)

    1982-01-01

    Portions of the LANDSAT-D systems operation plan are presented. An overview of the data processing operations, logistics and other operations support, prelaunch and post-launch activities, thematic mapper operations during the scrounge period, and LANDSAT-D performance evaluation is given.

  3. Personnel discussing Gemini 11 space flight in Mission Control

    NASA Image and Video Library

    1966-09-12

    S66-52157 (12 Sept. 1966) --- Discussing the Gemini-11 spaceflight in the Mission Control Center are: (left to right) Christopher C. Kraft Jr., (wearing glasses), Director of Flight Operations; Charles W. Mathews (holding phone), Manager, Gemini Program Office; Dr. Donald K. Slayton (center, checked coat), Director of Flight Crew Operations; astronaut William A. Anders, and astronaut John W. Young. Photo credit: NASA

  4. Beyond Mission Command: Maneuver Warfare for Cyber Command and Control

    DTIC Science & Technology

    2015-05-18

    operation in an A2AD environment. 15. SUBJECT TERMS command and control; maneuver warfare; cyberspace; cyberspace operations; cyber warfare , mission...Some Principles of Cyber Warfare (NWC 2160) (U.S. Naval War College, Joint Military Operations Department, Newport, RI: U.S. Naval War College...research/ innovationleadership.pdf. Crowell, Richard M. Some Principles of Cyber Warfare (NWC 2160). U.S. Naval War College, Joint Military Operations

  5. View of Mission Control Center during Apollo 13 splashdown

    NASA Image and Video Library

    1970-04-17

    S70-35471 (17 April 1970) --- Two flight controllers man consoles in the Missions Operations Control Room (MOCR) of the Mission Control Center (MCC) at the Manned Spacecraft Center (MSC), Houston, Texas, just before splashdown occurred in the south Pacific Ocean. Though the MOCR does not appear to be crowded in this photo, there was a very large crowd of persons on hand for the splashdown and recovery operations coverage. Most of the group crowded around in the rear of the room. Apollo 13 splashdown occurred at 12:07:44 p.m. (CST), April 17, 1970.

  6. Middleware Evaluation and Benchmarking for Use in Mission Operations Centers

    NASA Technical Reports Server (NTRS)

    Antonucci, Rob; Waktola, Waka

    2005-01-01

    Middleware technologies have been promoted as timesaving, cost-cutting alternatives to the point-to-point communication used in traditional mission operations systems. However, missions have been slow to adopt the new technology. The lack of existing middleware-based missions has given rise to uncertainty about middleware's ability to perform in an operational setting. Most mission architects are also unfamiliar with the technology and do not know the benefits and detriments to architectural choices - or even what choices are available. We will present the findings of a study that evaluated several middleware options specifically for use in a mission operations system. We will address some common misconceptions regarding the applicability of middleware-based architectures, and we will identify the design decisions and tradeoffs that must be made when choosing a middleware solution. The Middleware Comparison and Benchmark Study was conducted at NASA Goddard Space Flight Center to comprehensively evaluate candidate middleware products, compare and contrast the performance of middleware solutions with the traditional point- to-point socket approach, and assess data delivery and reliability strategies. The study focused on requirements of the Global Precipitation Measurement (GPM) mission, validating the potential use of middleware in the GPM mission ground system. The study was jointly funded by GPM and the Goddard Mission Services Evolution Center (GMSEC), a virtual organization for providing mission enabling solutions and promoting the use of appropriate new technologies for mission support. The study was broken into two phases. To perform the generic middleware benchmarking and performance analysis, a network was created with data producers and consumers passing data between themselves. The benchmark monitored the delay, throughput, and reliability of the data as the characteristics were changed. Measurements were taken under a variety of topologies, data demands

  7. Geostationary Operational Environmental Satellite (GOES)-8 mission flight experience

    NASA Technical Reports Server (NTRS)

    Noonan, C. H.; Mcintosh, R. J.; Rowe, J. N.; Defazio, R. L.; Galal, K. F.

    1995-01-01

    The Geostationary Operational Environmental Satellite (GOES)-8 spacecraft was launched on April 13, 1994, at 06:04:02 coordinated universal time (UTC), with separation from the Atlas-Centaur launch vehicle occurring at 06:33:05 UTC. The launch was followed by a series of complex, intense operations to maneuver the spacecraft into its geosynchronous mission orbit. The Flight Dynamics Facility (FDF) of the Goddard Space Flight Center (GSFC) Flight Dynamics Division (FDD) was responsible for GOES-8 attitude, orbit maneuver, orbit determination, and station acquisition support during the ascent phase. This paper summarizes the efforts of the FDF support teams and highlights some of the unique challenges the launch team faced during critical GOES-8 mission support. FDF operations experience discussed includes: (1) The abort of apogee maneuver firing-1 (AMF-1), cancellation of AMF-3, and the subsequent replans of the maneuver profile; (2) The unexpectedly large temperature dependence of the digital integrating rate assembly (DIRA) and its effect on GOES-8 attitude targeting in support of perigee raising maneuvers; (3) The significant effect of attitude control thrusting on GOES-8 orbit determination solutions; (4) Adjustment of the trim tab to minimize torque due to solar radiation pressure; and (5) Postlaunch analysis performed to estimate the GOES-8 separation attitude. The paper also discusses some key FDF GOES-8 lessons learned to be considered for the GOES-J launch which is currently scheduled for May 19, 1995.

  8. Psychological Support Operations and the ISS One-Year Mission

    NASA Technical Reports Server (NTRS)

    Beven, G.; Vander Ark, S. T.; Holland, A. W.

    2016-01-01

    Since NASA began human presence on the International Space Station (ISS) in November 1998, crews have spent two to seven months onboard. In March 2015 NASA and Russia embarked on a new era of ISS utilization, with two of their crewmembers conducting a one-year mission onboard ISS. The mission has been useful for both research and mission operations to better understand the human, technological, mission management and staffing challenges that may be faced on missions beyond Low Earth Orbit. The work completed during the first 42 ISS missions provided the basis for the pre-flight, in-flight and post-flight work completed by NASA's Space Medicine Operations Division, while our Russian colleagues provided valuable insights from their long-duration mission experiences with missions lasting 10-14 months, which predated the ISS era. Space Medicine's Behavioral Health and Performance Group (BHP) provided pre-flight training, evaluation, and preparation as well as in-flight psychological support for the NASA crewmember. While the BHP team collaboratively planned for this mission with the help of all ISS international partners within the Human Behavior and Performance Working Group to leverage their collective expertise, the US and Russian BHP personnel were responsible for their respective crewmembers. The presentation will summarize the lessons and experience gained within the areas identified by this Working Group as being of primary importance for a one-year mission.

  9. Voice loops as coordination aids in space shuttle mission control

    NASA Technical Reports Server (NTRS)

    Patterson, E. S.; Watts-Perotti, J.; Woods, D. D.

    1999-01-01

    Voice loops, an auditory groupware technology, are essential coordination support tools for experienced practitioners in domains such as air traffic management, aircraft carrier operations and space shuttle mission control. They support synchronous communication on multiple channels among groups of people who are spatially distributed. In this paper, we suggest reasons for why the voice loop system is a successful medium for supporting coordination in space shuttle mission control based on over 130 hours of direct observation. Voice loops allow practitioners to listen in on relevant communications without disrupting their own activities or the activities of others. In addition, the voice loop system is structured around the mission control organization, and therefore directly supports the demands of the domain. By understanding how voice loops meet the particular demands of the mission control environment, insight can be gained for the design of groupware tools to support cooperative activity in other event-driven domains.

  10. Voice loops as coordination aids in space shuttle mission control.

    PubMed

    Patterson, E S; Watts-Perotti, J; Woods, D D

    1999-01-01

    Voice loops, an auditory groupware technology, are essential coordination support tools for experienced practitioners in domains such as air traffic management, aircraft carrier operations and space shuttle mission control. They support synchronous communication on multiple channels among groups of people who are spatially distributed. In this paper, we suggest reasons for why the voice loop system is a successful medium for supporting coordination in space shuttle mission control based on over 130 hours of direct observation. Voice loops allow practitioners to listen in on relevant communications without disrupting their own activities or the activities of others. In addition, the voice loop system is structured around the mission control organization, and therefore directly supports the demands of the domain. By understanding how voice loops meet the particular demands of the mission control environment, insight can be gained for the design of groupware tools to support cooperative activity in other event-driven domains.

  11. Voice loops as coordination aids in space shuttle mission control

    NASA Technical Reports Server (NTRS)

    Patterson, E. S.; Watts-Perotti, J.; Woods, D. D.

    1999-01-01

    Voice loops, an auditory groupware technology, are essential coordination support tools for experienced practitioners in domains such as air traffic management, aircraft carrier operations and space shuttle mission control. They support synchronous communication on multiple channels among groups of people who are spatially distributed. In this paper, we suggest reasons for why the voice loop system is a successful medium for supporting coordination in space shuttle mission control based on over 130 hours of direct observation. Voice loops allow practitioners to listen in on relevant communications without disrupting their own activities or the activities of others. In addition, the voice loop system is structured around the mission control organization, and therefore directly supports the demands of the domain. By understanding how voice loops meet the particular demands of the mission control environment, insight can be gained for the design of groupware tools to support cooperative activity in other event-driven domains.

  12. Expanding ESOC's Science Family of Mission Control Systems

    NASA Astrophysics Data System (ADS)

    Kowalczyk, A.; Ercolani, A.; Spada, M.

    2009-05-01

    The interplanetary family of science missions at ESOC has enjoyed the benefits of having a pool of team members working across missions, sharing knowledge and experience, but most importantly it has benefited from significant Mission Control System (MCS) software re-use. This has resulted in a drastic reduction in costs, accomplished by a single software system. Today, this family of missions is growing. BepiColombo and ExoMars have their own individual characteristics and there is inevitably more complexity, but they share much with their "ancestors". Also Gaia, an astrometry mission to be launched in 2012, shares many operational principles with interplanetary missions and requires much of the added complexity inherent in control systems used by them. So, is it possible to develop a software concept that encapsulates the needs of both types of mission? This paper describes the different characteristics of the missions mentioned, and explains why a common system makes sense. It will also describe how we meet this challenge, using solid requirements consolidation and efficient reuse of existing software. The paper describes how common requirements have evolved out of the original Rosetta MCS (RMCS) requirements, and looks at the different issues involved in reaching a point where a generic ‘Science Kernel' control system can be specified and eventually developed.

  13. Mars geoscience/climatology orbiter low cost mission operations

    NASA Technical Reports Server (NTRS)

    Erickson, K. D.

    1984-01-01

    It will not be possible to support the multiple planetary missions of the magnitude and order of previous missions on the basis of foreseeable NASA funding. It is, therefore, necessary to seek innovative means for accomplishing the goals of planetary exploration with modestly allocated resources. In this connection, a Core Program set of planetary exploration missions has been recommended. Attention is given to a Mission Operations design overview which is based on the Mars Geoscience/Climatology Orbiter Phase-A study performed during spring of 1983.

  14. Lewis Wooten, manager of the Mission Operations Laboratory

    NASA Image and Video Library

    2015-07-20

    LEWIS WOOTEN MANAGES THE MISSION OPERATIONS LABORATORY. MORE THAN 1600 INVESTIGATIONS AND STUDENT EXPERIMENTS FOR OVER 80 COUNTRIES HAVE BEEN COMPLETED WITH THE HELP OF WOOTEN'S TEAM AT NASA'S MARSHALL SPACE FLIGHT CENTER IN HUNTSVILLE, ALABAMA.

  15. ISS Update: Astronaut Participates in Autonomous Mission Operations Test

    NASA Image and Video Library

    NASA Public Affairs Officer Brandi Dean talks with astronaut Alvin Drew who is participating in the Autonomous Mission Operations test, which looks at how communication delays will affect future de...

  16. View of Mission Control Center during Apollo 13 splashdown

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Dr. Thomas O. Paine (center), NASA Administrator, and other NASA Officials joined others in applauding the successful splashdown of the Apollo 13 crewmen. Others among the large crowd in the Mission Operations Control Room of the Mission Control Center, Manned Spacecraft Center (MSC) at the time of recovery were U.S. Air Force Lt. Gen. Samuel C. Phillips (extreme left), who formerly served as Apollo program Director, Office of Manned Space Flight, NASA Headquarters; Dr. Charles A. Berry (third from left), Director, Medical Research and Operations Directorate, MSC; and Dr. George M. Low, Associate NASA Administrator.

  17. View of Mission Control Center during Apollo 13 splashdown

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Dr. Thomas O. Paine (center), NASA Administrator, and other NASA Officials joined others in applauding the successful splashdown of the Apollo 13 crewmen. Others among the large crowd in the Mission Operations Control Room of the Mission Control Center, Manned Spacecraft Center (MSC) at the time of recovery were U.S. Air Force Lt. Gen. Samuel C. Phillips (extreme left), who formerly served as Apollo program Director, Office of Manned Space Flight, NASA Headquarters; Dr. Charles A. Berry (third from left), Director, Medical Research and Operations Directorate, MSC; and Dr. George M. Low, Associate NASA Administrator.

  18. Program control for mission success

    NASA Technical Reports Server (NTRS)

    Longanecker, G. W.

    1994-01-01

    This article suggests that in order to be able to exercise control over a particular program, the program itself must be controllable. A controllable program therefore, according to the author, is one that has been properly scoped technically, realistically scheduled, and adequately budgeted. The article delves indepth into each of the above aspects of a controllable program and discusses both the pros and cons of each.

  19. Terra Mission Operations: Launch to the Present (and Beyond)

    NASA Technical Reports Server (NTRS)

    Kelly, Angelita; Moyer, Eric; Mantziaras, Dimitrios; Case, Warren

    2014-01-01

    The Terra satellite, flagship of NASA's long-term Earth Observing System (EOS) Program, continues to provide useful earth science observations well past its 5-year design lifetime. This paper describes the evolution of Terra operations, including challenges and successes and the steps taken to preserve science requirements and prolong spacecraft life. Working cooperatively with the Terra science and instrument teams, including NASA's international partners, the mission operations team has successfully kept the Terra operating continuously, resolving challenges and adjusting operations as needed. Terra retains all of its observing capabilities (except Short Wave Infrared) despite its age. The paper also describes concepts for future operations. This paper will review the Terra spacecraft mission successes and unique spacecraft component designs that provided significant benefits extending mission life and science. In addition, it discusses special activities as well as anomalies and corresponding recovery efforts. Lastly, it discusses future plans for continued operations.

  20. Terra mission operations: Launch to the present (and beyond)

    NASA Astrophysics Data System (ADS)

    Kelly, Angelita; Moyer, Eric; Mantziaras, Dimitrios; Case, Warren

    2014-09-01

    The Terra satellite, flagship of NASA's long-term Earth Observing System (EOS) Program, continues to provide useful earth science observations well past its 5-year design lifetime. This paper describes the evolution of Terra operations, including challenges and successes and the steps taken to preserve science requirements and prolong spacecraft life. Working cooperatively with the Terra science and instrument teams, including NASA's international partners, the mission operations team has successfully kept the Terra operating continuously, resolving challenges and adjusting operations as needed. Terra retains all of its observing capabilities (except Short Wave Infrared) despite its age. The paper also describes concepts for future operations. This paper will review the Terra spacecraft mission successes and unique spacecraft component designs that provided significant benefits extending mission life and science. In addition, it discusses special activities as well as anomalies and corresponding recovery efforts. Lastly, it discusses future plans for continued operations.

  1. Ensemble: an Architecture for Mission-Operations Software

    NASA Technical Reports Server (NTRS)

    Norris, Jeffrey; Powell, Mark; Fox, Jason; Rabe, Kenneth; Shu, IHsiang; McCurdy, Michael; Vera, Alonso

    2008-01-01

    Ensemble is the name of an open architecture for, and a methodology for the development of, spacecraft mission operations software. Ensemble is also potentially applicable to the development of non-spacecraft mission-operations- type software. Ensemble capitalizes on the strengths of the open-source Eclipse software and its architecture to address several issues that have arisen repeatedly in the development of mission-operations software: Heretofore, mission-operations application programs have been developed in disparate programming environments and integrated during the final stages of development of missions. The programs have been poorly integrated, and it has been costly to develop, test, and deploy them. Users of each program have been forced to interact with several different graphical user interfaces (GUIs). Also, the strategy typically used in integrating the programs has yielded serial chains of operational software tools of such a nature that during use of a given tool, it has not been possible to gain access to the capabilities afforded by other tools. In contrast, the Ensemble approach offers a low-risk path towards tighter integration of mission-operations software tools.

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

    NASA Technical Reports Server (NTRS)

    Weldy, Michelle

    1996-01-01

    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.

  3. Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

    NASA Technical Reports Server (NTRS)

    Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David

    2006-01-01

    NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

  4. Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

    NASA Technical Reports Server (NTRS)

    Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David

    2006-01-01

    NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

  5. VIew of Mission Control on first day of ASTP docking in Earth orbit

    NASA Technical Reports Server (NTRS)

    1975-01-01

    An overall view of the Mission Operations Control Room in the Mission Control Center on the first day of the Apollo Soyuz Test Project (ASTP) docking in Earth orbit mission. The American ASTP flight controllers at JSC were monitoring the progress of the Soviet ASTP launch when this photograph was taken. The television monitor shows Cosmonaut Yuri V. Romanenko at his spacecraft communicator's console in the ASTP mission control center in the Soviet Union.

  6. SSS-A attitude control prelaunch analysis and operations plan

    NASA Technical Reports Server (NTRS)

    Werking, R. D.; Beck, J.; Gardner, D.; Moyer, P.; Plett, M.

    1971-01-01

    A description of the attitude control support being supplied by the Mission and Data Operations Directorate is presented. Descriptions of the computer programs being used to support the mission for attitude determination, prediction, control, and definitive attitude processing are included. In addition, descriptions of the operating procedures which will be used to accomplish mission objectives are provided.

  7. Proximity operations analysis: Retrieval of the solar maximum mission observatory

    NASA Technical Reports Server (NTRS)

    Yglesias, J. A.

    1980-01-01

    Retrieval of the solar maximum mission (SMM) observatory is feasible in terms of orbiter primary reaction control system (PRCS) plume disturbance of the SMM, orbiter propellant consumed, and flight time required. Man-in-loop simulations will be required to validate these operational techniques before the verification process is complete. Candidate approach and flyaround techniques were developed that allow the orbiter to attain the proper alinement with the SMM for clear access to the grapple fixture (GF) prior grappling. Because the SMM has very little control authority (approximately 14.8 pound-foot-seconds in two axes and rate-damped in the third) it is necessary to inhibit all +Z (upfiring) PRCS jets on the orbiter to avoid tumbling the SMM. A profile involving a V-bar approach and an out-of-plane flyaround appears to be the best choice and is recommended at this time. The flyaround technique consists of alining the +X-axes of the two vehicles parallel with each other and then flying the orbiter around the SMM until the GF is in view. The out-of-plane flyaround technique is applicable to any inertially stabilized payload, and, the entire final approach profile could be considered as standard for most retrieval missions.

  8. Mission operations system for Russian space Very-Long-Baseline Interferometry mission

    NASA Technical Reports Server (NTRS)

    Altunin, V. I.; Robinett, K. H.

    1992-01-01

    A mission operations system developed to meet the unique requirements of the prospective Russian space VLBI mission Radioastron is described. The challenges associated with the Radioastron operations are mainly due to the interrelationship between the space-based telescope and the ground observatories, and the mission's international character. The Radioastron project includes radio observatories located in 17 different countries, tracking facilities in possibly seven different countries, orbit determination centers in Russia and USA, and widely located data processing facilities. In addition, unique scheduling constraints arise from the competing demands placed on the ground observatory time by earth-based VLBI experiments, and the tracking station time by a Japanese space interferometry mission VSOP, which is expected to be in orbit concurrently with Radioastron. A diagram illustrating the organizational structure of the Radioastron project during operations is presented.

  9. Autonomous Data Transfer Operations for Missions

    NASA Technical Reports Server (NTRS)

    Repaci, Max; Baker, Paul; Brosi, Fred

    2000-01-01

    Automating the data transfer operation can significantly reduce the cost of moving data from a spacecraft to a location on Earth. Automated data transfer methods have been developed for the terrestrial Internet. However, they often do not apply to the space environment, since in general they are based on assumptions about connectivity that are true on the Internet but not on space links. Automated file transfer protocols have been developed for use over space links that transfer data via store-and-forward of files or segments of files. This paper investigates some of the operational concepts made possible by these protocols.

  10. Inflight - Apollo XI (Mission Control Center [MCC]) - MSC

    NASA Image and Video Library

    1969-07-24

    S69-40302 (24 July 1969) --- A group of NASA and Manned Spacecraft Center (MSC) officials join in with the flight controllers in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, in celebrating the successful conclusion of the Apollo 11 lunar landing mission. From left foreground are Dr. Maxime A. Faget, MSC Director of Engineering and Development; George S. Trimble, MSC Deputy Director; Dr. Christopher C. Kraft Jr., MSC Director of Flight Operations; Julian Scheer (in back), Assistant Administrator, Office of Public Affairs, NASA Headquarters; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Robert R. Gilruth, MSC Director; and Charles W. Mathews, Deputy Associate Administrator, Office of Manned Space Flight, NASA Headquarters.

  11. MISSION CONTROL CENTER (MCC) VIEW - CONCLUSION APOLLO 11 CELEBRATION - MSC

    NASA Image and Video Library

    1969-07-24

    S69-40024 (24 July 1969) --- NASA and Manned Spacecraft Center (MSC) officials join in with the flight controllers, in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), in celebrating the successful conclusion of the Apollo 11 lunar landing mission. Identifiable in the picture, starting in foreground, are Dr. Robert R. Gilruth, MSC Director; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Christopher C. Kraft Jr., MSC Director of Flight Operation; U.S. Air Force Lt. Gen. Samuel C. Phillips (with glasses, looking downward), Apollo Program Director, Office of Manned Space Flight, NASA Headquarters; and Dr. George E. Mueller (with glasses, looking toward left), Associate Administrator, Office of Manned Space Flight, NASA Headquarters. Former astronaut John H. Glenn Jr. is standing behind Mr. Low.

  12. hwhap_Ep11_Mission Control

    NASA Image and Video Library

    2017-09-22

    and fifty thousand views. Famous. >> That's a lot. I try not to think about that, really. >> [laughs] But it was so fun. It was like, I mean we title it Everything. I mean it wasn't really everything, but it was, it was like fast paced information. You got to know more about Mission Control than I guess people would normally kind of find out. And we got to be on the floor. It's kind of different though, that they didn't have the titles up there, you know. We we're mission that Flight Director, GC. Those kinds of things. >> Yeah, remind me again. We'll make improvements for next time, right. >> For the next one. Okay, so welcome to the podcast. For this one we don't have to be as wrapped in fire, so that's good. >> Okay. >> We can kind of take our time. But today we are here to talk about Mission Control, and I feel like you're the perfect person to do this, because you are a Flight Director. You're in that, you're in Mission Control making all the decisions. And I guess that's sort of what a Flight Controller does. Or, sorry. A Flight Director does, right. You're kind of the, the main person in that room. >> That's right, yes. >> Okay. >> The Flight Director is the lead of the flight control team. So, they're kind of the final decision maker and real-time spacecraft operations. >> Cool. And you do that how often, in general? >> I spend a lot of time on console. I'm one of the newer Flight Directors. >> Okay. >> So probably spend a little more time on console than some of the more experienced guys that have a lot more assignments. >> I see. >> But I would say over the past year I probably pulled about a hundred shifts. >> Whoa. >> So, one shift is about eight to nine hours long. Eight hours with a one-hour hand over period. And, we do that every few weeks. We're on console for a string of anywhere from one to seven shifts I would say. >> Okay. And there three shifts in a day, right? It's just how, because you have that hand over period so nine, nine, nine. You guys can

  13. Science operations planning expertise: A neglected component of mission design

    NASA Astrophysics Data System (ADS)

    Chaizy, P. A.; Dimbylow, T. G.; Allan, P. M.; Hapgood, M. A.

    2011-09-01

    In this paper, Science Operations Planning Expertise (SOPE) is defined as the expertise that is held by people who have the two following qualities. First they have both theoretical and practical experience in operations planning, in general, and in space science operations planning in particular. Second, they can be used, on request and at least, to provide with advice the teams that design and implement science operations systems in order to optimise the performance and productivity of the mission. However, the relevance and use of such SOPE early on during the Mission Design Phase (MDP) is not sufficiently recognised. As a result, science operations planning is often neglected or poorly assessed during the mission definition phases. This can result in mission architectures that are not optimum in terms of cost and scientific returns, particularly for missions that require a significant amount of science operations planning. Consequently, science operations planning difficulties and cost underestimations are often realised only when it is too late to design and implement the most appropriate solutions. In addition, higher costs can potentially reduce both the number of new missions and the chances of existing ones to be extended. Moreover, the quality, and subsequently efficiency, of SOPE can vary greatly. This is why we also believe that the best possible type of SOPE requires a structure similar to the ones of existing bodies of expertise dedicated to the data processing such as the International Planetary Data Alliance (IPDA), the Space Physics Archive Search and Extract (SPASE) or the Planetary Data System (PDS). Indeed, this is the only way of efficiently identifying science operations planning issues and their solutions as well as of keeping track of them in order to apply them to new missions. Therefore, this paper advocates for the need to allocate resources in order to both optimise the use of SOPE early on during the MDP and to perform, at least, a

  14. Deep Space Habitat Concept of Operations for Transit Mission Phases

    NASA Technical Reports Server (NTRS)

    Hoffman, Stephen J.

    2011-01-01

    The National Aeronautics and Space Administration (NASA) has begun evaluating various mission and system components of possible implementations of what the U.S. Human Spaceflight Plans Committee (also known as the Augustine Committee) has named the flexible path (Anon., 2009). As human spaceflight missions expand further into deep space, the duration of these missions increases to the point where a dedicated crew habitat element appears necessary. There are several destinations included in this flexible path a near Earth asteroid (NEA) mission, a Phobos/Deimos (Ph/D) mission, and a Mars surface exploration mission that all include at least a portion of the total mission in which the crew spends significant periods of time (measured in months) in the deep space environment and are thus candidates for a dedicated habitat element. As one facet of a number of studies being conducted by the Human Spaceflight Architecture Team (HAT) a workshop was conducted to consider how best to define and quantify habitable volume for these future deep space missions. One conclusion reached during this workshop was the need for a description of the scope and scale of these missions and the intended uses of a habitat element. A group was set up to prepare a concept of operations document to address this need. This document describes a concept of operations for a habitat element used for these deep space missions. Although it may eventually be determined that there is significant overlap with this concept of operations and that of a habitat destined for use on planetary surfaces, such as the Moon and Mars, no such presumption is made in this document.

  15. SKYLAB III - POSTLAUNCH (MISSION CONTROL CENTER [MCC]) - JSC

    NASA Image and Video Library

    1973-08-06

    S73-31964 (5 August 1973) --- This group of flight controllers discuss today's approaching extravehicular activity (EVA) to be performed by the Skylab 3 crewmen. They are, left to right, scientist-astronaut Story Musgrave, a Skylab 3 spacecraft communicator; Robert Kain and Scott Millican, both of the Crew Procedures Division, EVA Procedures Section; William C. Schneider, Skylab Program Director, NASA Headquarters; and Milton Windler, flight director. Windler points to the model of the Skylab space station cluster to indicate the location of the ATM's film magazines. The group stands near consoles in the Mission Operations Control Room (MOCR) of the JSC Mission Control Center (MCC). Photo credit: NASA

  16. Orbital Express mission operations planning and resource management using ASPEN

    NASA Astrophysics Data System (ADS)

    Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Daniel

    2008-04-01

    As satellite equipment and mission operations become more costly, the drive to keep working equipment running with less labor-power rises. Demonstrating the feasibility of autonomous satellite servicing was the main goal behind the Orbital Express (OE) mission. Like a tow-truck delivering gas to a car on the road, the "servicing" satellite of OE had to find the "client" from several kilometers away, connect directly to the client, and transfer fluid (or a battery) autonomously, while on earth-orbit. The mission met 100% of its success criteria, and proved that autonomous satellite servicing is now a reality for space operations. Planning the satellite mission operations for OE required the ability to create a plan which could be executed autonomously over variable conditions. As the constraints for execution could change weekly, daily, and even hourly, the tools used create the mission execution plans needed to be flexible and adaptable to many different kinds of changes. At the same time, the hard constraints of the plans needed to be maintained and satisfied. The Automated Scheduling and Planning Environment (ASPEN) tool, developed at the Jet Propulsion Laboratory, was used to create the schedule of events in each daily plan for the two satellites of the OE mission. This paper presents an introduction to the ASPEN tool, an overview of the constraints of the OE domain, the variable conditions that were presented within the mission, and the solution to operations that ASPEN provided. ASPEN has been used in several other domains, including research rovers, Deep Space Network scheduling research, and in flight operations for the NASA's Earth Observing One mission's EO1 satellite. Related work is discussed, as are the future of ASPEN and the future of autonomous satellite servicing.

  17. Spitzer Pre Launch Mission Operations System - The Road to Launch

    NASA Technical Reports Server (NTRS)

    Scott, Charles P.; Wilson, Robert K.

    2006-01-01

    Spitzer Space Telescope was launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Development of the Mission Operations System (MOS) portion prior to launch was very different from planetary missions from the stand point that the MOS teams and Ground Data System had to be ready to support all aspects of the mission at launch (i.e., no cruise period for finalizing the implementation). For Spitzer, all mission-critical events post launch happen in hours or days rather than months or years, as is traditional with deep space missions. At the end of 2000 the Project was dealt a major blow when the Mission Operations System (MOS) had an unsuccessful Critical Design Review (CDR). The project made major changes at the beginning of 2001 in an effort to get the MOS (and Project) back on track. The result for the Spitzer Space Telescope was a successful launch of the observatory followed by an extremely successful In Orbit Checkout (IOC) and operations phase. This paper describes how the project was able to recover the MOS to a successful Delta (CDR) by mid 2001, and what changes in philosophies, experiences, and lessons learned followed. It describes how projects must invest early or else invest heavily later in the development phase to achieve a successful operations phase.

  18. Spitzer Pre Launch Mission Operations System - The Road to Launch

    NASA Technical Reports Server (NTRS)

    Scott, Charles P.; Wilson, Robert K.

    2006-01-01

    Spitzer Space Telescope was launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Development of the Mission Operations System (MOS) portion prior to launch was very different from planetary missions from the stand point that the MOS teams and Ground Data System had to be ready to support all aspects of the mission at launch (i.e., no cruise period for finalizing the implementation). For Spitzer, all mission-critical events post launch happen in hours or days rather than months or years, as is traditional with deep space missions. At the end of 2000 the Project was dealt a major blow when the Mission Operations System (MOS) had an unsuccessful Critical Design Review (CDR). The project made major changes at the beginning of 2001 in an effort to get the MOS (and Project) back on track. The result for the Spitzer Space Telescope was a successful launch of the observatory followed by an extremely successful In Orbit Checkout (IOC) and operations phase. This paper describes how the project was able to recover the MOS to a successful Delta (CDR) by mid 2001, and what changes in philosophies, experiences, and lessons learned followed. It describes how projects must invest early or else invest heavily later in the development phase to achieve a successful operations phase.

  19. Solar-A Prelaunch Mission Operation Report (MOR)

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The Solar-A mission is a Japanese-led program with the participation of the United States and the United Kingdom. The Japanese Institute of Space and Astronautical Science (ISAS) is providing the Solar-A spacecraft, two of the four science instruments, the launch vehicle and launch support, and the principal ground station with Operational Control Center. NASA is providing a science instrument, the Soft X-ray Telescope (SXT)and tracking support using the Deep Space Network (DSN) ground stations. The United Kingdom s Science and Engineering Research Council (SERC) provides the Bragg Crystal Spectrometer. The Solar-A mission will study solar flares using a cluster of instruments on a satellite in a 600 km altitude, 31 degree inclination circular orbit. The emphasis of the mission is on imaging and spectroscopy of hard and soft X-rays. The principal instruments are a pair of X-ray imaging instruments, one for the hard X-ray range and one for the soft X-ray range. The Hard X-Ray Telescope (HXT), provided by ISAS, operates in the energy range of 10-100 keV and uses an array of modulation collimators to record Fourier transform images of the non-thermal and hot plasmas that are formed during the early phases of a flare. These images are thought to be intimately associated with the sites of primary energy release. The Soft X-Ray Telescope (SXT), jointly provided by NASA and ISAS, operates in the wavelength range of 3-50 Angstroms and uses a grazing incidence mirror to form direct images of the lower temperature (but still very hot) plasmas that form as the solar atmosphere responds to the injection of energy. The SXT instrument is a joint development effort between the Lockheed Palo Alto Research Laboratory and the National Astronomical Observatory of Japan. The U.S. effort also involves Stanford University, the University of California at Berkeley and the University of Hawaii, who provide support in the areas of theory, data analysis and interpretation, and ground

  20. Intelligent resources for satellite ground control operations

    NASA Technical Reports Server (NTRS)

    Jones, Patricia M.

    1994-01-01

    This paper describes a cooperative approach to the design of intelligent automation and describes the Mission Operations Cooperative Assistant for NASA Goddard flight operations. The cooperative problem solving approach is being explored currently in the context of providing support for human operator teams and also in the definition of future advanced automation in ground control systems.

  1. Mission Control Technologies: A New Way of Designing and Evolving Mission Systems

    NASA Technical Reports Server (NTRS)

    Trimble, Jay; Walton, Joan; Saddler, Harry

    2006-01-01

    Current mission operations systems are built as a collection of monolithic software applications. Each application serves the needs of a specific user base associated with a discipline or functional role. Built to accomplish specific tasks, each application embodies specialized functional knowledge and has its own data storage, data models, programmatic interfaces, user interfaces, and customized business logic. In effect, each application creates its own walled-off environment. While individual applications are sometimes reused across multiple missions, it is expensive and time consuming to maintain these systems, and both costly and risky to upgrade them in the light of new requirements or modify them for new purposes. It is even more expensive to achieve new integrated activities across a set of monolithic applications. These problems impact the lifecycle cost (especially design, development, testing, training, maintenance, and integration) of each new mission operations system. They also inhibit system innovation and evolution. This in turn hinders NASA's ability to adopt new operations paradigms, including increasingly automated space systems, such as autonomous rovers, autonomous onboard crew systems, and integrated control of human and robotic missions. Hence, in order to achieve NASA's vision affordably and reliably, we need to consider and mature new ways to build mission control systems that overcome the problems inherent in systems of monolithic applications. The keys to the solution are modularity and interoperability. Modularity will increase extensibility (evolution), reusability, and maintainability. Interoperability will enable composition of larger systems out of smaller parts, and enable the construction of new integrated activities that tie together, at a deep level, the capabilities of many of the components. Modularity and interoperability together contribute to flexibility. The Mission Control Technologies (MCT) Project, a collaboration of

  2. Management of Operational Support Requirements for Manned Flight Missions

    NASA Technical Reports Server (NTRS)

    1991-01-01

    This Instruction establishes responsibilities for managing the system whereby operational support requirements are levied for support of manned flight missions including associated payloads. This management system will ensure that support requirements are properly requested and responses are properly obtained to meet operational objectives.

  3. Astronaut Uses Manual Point Control During Astro-1 Mission

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Due to loss of data used for pointing and operating the ultraviolet telescopes, MSFC ground teams were forced to aim the telescopes with fine tuning by the flight crew. Pictured onboard the shuttle is astronaut Robert Parker using a Manual Pointing Controller (MPC) for the ASTRO-1 mission Instrument Pointing System (IPS).

  4. MISSION CONTROL CENTER (MCC) ACTIVITY - GEMINI-12 SPLASHDOWN - MSC

    NASA Image and Video Library

    1966-11-15

    S66-64884 (15 Nov. 1966) --- Watching console activity in the Mission Control Center in Houston during the Gemini-12 splashdown (left to right), are Dr. Charles A. Berry, Director of Medical Research and Operations; astronaut John H. Glenn Jr.; James C. Elms, Director, NASA Electronics Research Center; and Dr. Robert R. Gilruth, Manned Spaceflight Center (MSC) Director. Photo credit: NASA

  5. View of Medical Support Room in Mission Control Center during Apollo 16

    NASA Technical Reports Server (NTRS)

    1972-01-01

    Dr. J.F. Zieglschmid, M.D., Mission Operations Control Room (MOCR) White Team Surgeon, is seated in the Medical Support Room in the Mission Control Center as he monitors crew biomedical data being received from the Apollo 16 spacecraft on the third day of the Apollo 16 lunar landing mission.

  6. Mission Operations Directorate - Success Legacy of the Space Shuttle Program

    NASA Technical Reports Server (NTRS)

    Azbell, James A.

    2011-01-01

    In support of the Space Shuttle Program, as well as NASA s other human space flight programs, the Mission Operations Directorate (MOD) at the Johnson Space Center has become the world leader in human spaceflight operations. From the earliest programs - Mercury, Gemini, Apollo - through Skylab, Shuttle, ISS, and our Exploration initiatives, MOD and its predecessors have pioneered ops concepts and emphasized a history of mission leadership which has added value, maximized mission success, and built on continual improvement of the capabilities to become more efficient and effective. MOD s focus on building and contributing value with diverse teams has been key to their successes both with the US space industry and the broader international community. Since their beginning, MOD has consistently demonstrated their ability to evolve and respond to an ever changing environment, effectively prepare for the expected and successfully respond to the unexpected, and develop leaders, expertise, and a culture that has led to mission and Program success.

  7. Preliminary Report on Mission Design and Operations for Critical Events

    NASA Technical Reports Server (NTRS)

    Hayden, Sandra C.; Tumer, Irem

    2005-01-01

    Mission-critical events are defined in the Jet Propulsion Laboratory s Flight Project Practices as those sequences of events which must succeed in order to attain mission goals. These are dependent on the particular operational concept and design reference mission, and are especially important when committing to irreversible events. Critical events include main engine cutoff (MECO) after launch; engine cutoff or parachute deployment on entry, descent, and landing (EDL); orbital insertion; separation of payload from vehicle or separation of booster segments; maintenance of pointing accuracy for power and communication; and deployment of solar arrays and communication antennas. The purpose of this paper is to report on the current practices in handling mission-critical events in design and operations at major NASA spaceflight centers. The scope of this report includes NASA Johnson Space Center (JSC), NASA Goddard Space Flight Center (GSFC), and NASA Jet Propulsion Laboratory (JPL), with staff at each center consulted on their current practices, processes, and procedures.

  8. Mission Operations Directorate - Success Legacy of the Space Shuttle Program

    NASA Technical Reports Server (NTRS)

    Azbell, Jim

    2010-01-01

    In support of the Space Shuttle Program, as well as NASA's other human space flight programs, the Mission Operations Directorate (MOD) at the Johnson Space Center has become the world leader in human spaceflight operations. From the earliest programs - Mercury, Gemini, Apollo - through Skylab, Shuttle, ISS, and our Exploration initiatives, MOD and its predecessors have pioneered ops concepts and emphasized a history of mission leadership which has added value, maximized mission success, and built on continual improvement of the capabilities to become more efficient and effective. MOD's focus on building and contributing value with diverse teams has been key to their successes both with the US space industry and the broader international community. Since their beginning, MOD has consistently demonstrated their ability to evolve and respond to an ever changing environment, effectively prepare for the expected and successfully respond to the unexpected, and develop leaders, expertise, and a culture that has led to mission and Program success.

  9. Implementing Distributed Operations: A Comparison of Two Deep Space Missions

    NASA Technical Reports Server (NTRS)

    Mishkin, Andrew; Larsen, Barbara

    2006-01-01

    Two very different deep space exploration missions--Mars Exploration Rover and Cassini--have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a mission of more than ten years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process. Additionally, MER has benefited from the initial co-location of its entire operations team, and from having a single Principal Investigator, while Cassini operations have had to reconcile multiple science teams distributed from before launch. Cassini has faced greater challenges in implementing effective distributed operations. Because extensive early planning is required to capture science opportunities on its tour and because sequence development takes significantly longer than sequence execution, multiple teams are contributing to multiple sequences concurrently. The complexity of integrating inputs from multiple teams is exacerbated by spacecraft operability issues and resource contention among the teams, each of which has their own Principal Investigator. Finally, much of the technology that MER has exploited to facilitate distributed operations was not available when the Cassini ground system was designed, although later adoption

  10. Constraint and Flight Rule Management for Space Mission Operations

    NASA Technical Reports Server (NTRS)

    Barreiro, J.; Chachere, J.; Frank, J.; Bertels, C.; Crocker, A.

    2010-01-01

    The exploration of space is one of the most fascinating domains to study from a human factors perspective. Like other complex work domains such as aviation (Pritchett and Kim, 2008), air traffic management (Durso and Manning, 2008), health care (Morrow, North, and Wickens, 2006), homeland security (Cooke and Winner, 2008), and vehicle control (Lee, 2006), space exploration is a large-scale sociotechnical work domain characterized by complexity, dynamism, uncertainty, and risk in real-time operational contexts (Perrow, 1999; Woods et al, 1994). Nearly the entire gamut of human factors issues - for example, human-automation interaction (Sheridan and Parasuraman, 2006), telerobotics, display and control design (Smith, Bennett, and Stone, 2006), usability, anthropometry (Chaffin, 2008), biomechanics (Marras and Radwin, 2006), safety engineering, emergency operations, maintenance human factors, situation awareness (Tenney and Pew, 2006), crew resource management (Salas et al., 2006), methods for cognitive work analysis (Bisantz and Roth, 2008) and the like -- are applicable to astronauts, mission control, operational medicine, Space Shuttle manufacturing and assembly operations, and space suit designers as they are in other work domains (e.g., Bloomberg, 2003; Bos et al, 2006; Brooks and Ince, 1992; Casler and Cook, 1999; Jones, 1994; McCurdy et al, 2006; Neerincx et aI., 2006; Olofinboba and Dorneich, 2005; Patterson, Watts-Perotti and Woods, 1999; Patterson and Woods, 2001; Seagull et ai, 2007; Sierhuis, Clancey and Sims, 2002). The human exploration of space also has unique challenges of particular interest to human factors research and practice. This chapter provides an overview of those issues and reports on some of the latest research results as well as the latest challenges still facing the field.

  11. View of Mission Control Center during Apollo 13 splashdown

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Overall view of Mission Operations Control Room in Mission Control Center at the Manned Spacecraft Center (MSC) during the ceremonies aboard the U.S.S. Iwo Jima, prime recovery ship for the Apollo 13 mission. Dr. Donald K. Slayton (in black shirt, left of center), Director of Flight Crew Operations at MSC, and Chester M. Lee of the Apollo Program Directorate, Office of Manned Space Flight, NASA Headquarters, shake hands, while Dr. Rocco A. Petrone, Apollo Program Director, Office of Manned Space Flight, NASA Headquarters (standing, near Lee), watches the large screen showing Astronaut James A. Lovell Jr., Apollo 13 commander, during the on-board ceremonies. In the foreground, Glynn S. Lunney (extreme left) and Eugene F. Kranz (smoking a cigar), two Apollo 13 Flight Directors, view the activity from their consoles.

  12. View of Mission Control Center during Apollo 13 splashdown

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Overall view of Mission Operations Control Room in Mission Control Center at the Manned Spacecraft Center (MSC) during the ceremonies aboard the U.S.S. Iwo Jima, prime recovery ship for the Apollo 13 mission. Dr. Donald K. Slayton (in black shirt, left of center), Director of Flight Crew Operations at MSC, and Chester M. Lee of the Apollo Program Directorate, Office of Manned Space Flight, NASA Headquarters, shake hands, while Dr. Rocco A. Petrone, Apollo Program Director, Office of Manned Space Flight, NASA Headquarters (standing, near Lee), watches the large screen showing Astronaut James A. Lovell Jr., Apollo 13 commander, during the on-board ceremonies. In the foreground, Glynn S. Lunney (extreme left) and Eugene F. Kranz (smoking a cigar), two Apollo 13 Flight Directors, view the activity from their consoles.

  13. MISSION CONTROL CENTER (MCC) - MSC - during Apollo 16

    NASA Image and Video Library

    1972-05-08

    S72-37009 (20 April 1972) --- NASA officials gather around a console in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) prior to the making of a decision whether to land Apollo 16 on the moon or to abort the landing. Seated, left to right, are Dr. Christopher C. Kraft Jr., Director of the Manned Spacecraft Center (MSC), and Brig. Gen. James A. McDivitt (USAF), Manager, Apollo Spacecraft Program Office, MSC; and standing, left to right, are Dr. Rocco A. Petrone, Apollo Program Director, Office Manned Space Flight (OMSF), NASA HQ.; Capt. John K. Holcomb (U.S. Navy, Ret.), Director of Apollo Operations, OMSF; Sigurd A. Sjoberg, Deputy Director, MSC; Capt. Chester M. Lee (U.S. Navy, Ret.), Apollo Mission Director, OMSF; Dale D. Myers, NASA Associate Administrator for Manned Space Flight; and Dr. George M. Low, NASA Deputy Administrator. Photo credit: NASA

  14. IUS/TUG orbital operations and mission support study. Volume 3: Space tug operations

    NASA Technical Reports Server (NTRS)

    1975-01-01

    A study was conducted to develop space tug operational concepts and baseline operations plan, and to provide cost estimates for space tug operations. Background data and study results are presented along with a transition phase analysis (the transition from interim upper state to tug operations). A summary is given of the tug operational and interface requirements with emphasis on the on-orbit checkout requirements, external interface operational requirements, safety requirements, and system operational interface requirements. Other topics discussed include reference missions baselined for the tug and details for the mission functional flows and timelines derived for the tug mission, tug subsystems, tug on-orbit operations prior to the tug first burn, spacecraft deployment and retrieval by the tug, operations centers, mission planning, potential problem areas, and cost data.

  15. The Science Operations of the ESA JUICE mission

    NASA Astrophysics Data System (ADS)

    Altobelli, Nicolas; Cardesin, Alejandro; Costa, Marc; Frew, David; Lorente, Rosario; Vallat, Claire; Witasse, Olivier; Christian, Erd

    2016-10-01

    The JUpiter ICy moons Explorer (JUICE) mission was selected by ESA as the first L-Class Mission in the Cosmic Vision Programme. JUICE is an ESA-led mission to investigate Jupiter, the Jovian system with particular focus on habitability of Ganymede and Europa.JUICE will characterise Ganymede and Europa as planetary objects and potential habitats, study Ganymede, Europa, Callisto and Io in the broader context of the system of Jovian moons, and focus on Jupiter science including the planet, its atmosphere and the magnetosphere as a coupled system.The Science Operation Centre (SOC) is in charge of implementing the science operations of the JUICE mission. The SOC aims at supporting the Science Working Team (SWT) and the Science Working Groups (WGs) performing studies of science operation feasibility and coverage analysis during the mission development phase, high level science planning during the cruise phase, and routine consolidation of instrument pointing and commanding timeline during the nominal science phase.We will present the current status of the SOC science planning activities with an overview of the tools and methods in place in this early phase of the mission.

  16. SpaceOps 1992: Proceedings of the Second International Symposium on Ground Data Systems for Space Mission Operations

    NASA Technical Reports Server (NTRS)

    1993-01-01

    The Second International Symposium featured 135 oral presentations in these 12 categories: Future Missions and Operations; System-Level Architectures; Mission-Specific Systems; Mission and Science Planning and Sequencing; Mission Control; Operations Automation and Emerging Technologies; Data Acquisition; Navigation; Operations Support Services; Engineering Data Analysis of Space Vehicle and Ground Systems; Telemetry Processing, Mission Data Management, and Data Archiving; and Operations Management. Topics focused on improvements in the productivity, effectiveness, efficiency, and quality of mission operations, ground systems, and data acquisition. Also emphasized were accomplishments in management of human factors; use of information systems to improve data retrieval, reporting, and archiving; design and implementation of logistics support for mission operations; and the use of telescience and teleoperations.

  17. MAIUS-1- Vehicle, Subsystems Design and Mission Operations

    NASA Astrophysics Data System (ADS)

    Stamminger, A.; Ettl, J.; Grosse, J.; Horschgen-Eggers, M.; Jung, W.; Kallenbach, A.; Raith, G.; Saedtler, W.; Seidel, S. T.; Turner, J.; Wittkamp, M.

    2015-09-01

    In November 2015, the DLR Mobile Rocket Base will launch the MAIUS-1 rocket vehicle at Esrange, Northern Sweden. The MAIUS-A experiment is a pathfinder atom optics experiment. The scientific objective of the mission is the first creation of a BoseEinstein Condensate in space and performing atom interferometry on a sounding rocket [3]. MAIUS-1 comprises a two-stage unguided solid propellant VSB-30 rocket motor system. The vehicle consists of a Brazilian 53 1 motor as 1 st stage, a 530 motor as 2nd stage, a conical motor adapter, a despin module, a payload adapter, the MAIUS-A experiment consisting of five experiment modules, an attitude control system module, a newly developed conical service system, and a two-staged recovery system including a nosecone. In contrast to usual payloads on VSB-30 rockets, the payload has a diameter of 500 mm due to constraints of the scientific experiment. Because of this change in design, a blunted nosecone is necessary to guarantee the required static stability during the ascent phase of the flight. This paper will give an overview on the subsystems which have been built at DLR MORABA, especially the newly developed service system. Further, it will contain a description of the MAIUS-1 vehicle, the mission and the unique requirements on operations and attitude control, which is additionally required to achieve a required attitude with respect to the nadir vector. Additionally to a usual microgravity environment, the MAIUS-l payload requires attitude control to achieve a required attitude with respect to the nadir vector.

  18. Galileo mission planning for Low Gain Antenna based operations

    NASA Technical Reports Server (NTRS)

    Gershman, R.; Buxbaum, K. L.; Ludwinski, J. M.; Paczkowski, B. G.

    1994-01-01

    The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include

  19. Orbital Express Mission Operations Planning and Resource Management using ASPEN

    NASA Technical Reports Server (NTRS)

    Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Daniel

    2008-01-01

    As satellite equipment and mission operations become more costly, the drive to keep working equipment running with less man-power rises.Demonstrating the feasibility of autonomous satellite servicing was the main goal behind the Orbital Express (OE) mission. Planning the satellite mission operations for OE required the ability to create a plan which could be executed autonomously over variable conditions. The Automated-Scheduling and Planning Environment (ASPEN)tool, developed at the Jet Propulsion Laboratory, was used to create the schedule of events in each daily plan for the two satellites of the OE mission. This paper presents an introduction to the ASPEN tool, the constraints of the OE domain, the variable conditions that were presented within the mission, and the solution to operations that ASPEN provided. ASPEN has been used in several other domains, including research rovers, Deep Space Network scheduling research, and in flight operations for the ASE project's EO1 satellite. Related work is discussed, as are the future of ASPEN and the future of autonomous satellite servicing.

  20. Orbital Express Mission Operations Planning and Resource Management using ASPEN

    NASA Technical Reports Server (NTRS)

    Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Daniel

    2008-01-01

    As satellite equipment and mission operations become more costly, the drive to keep working equipment running with less man-power rises.Demonstrating the feasibility of autonomous satellite servicing was the main goal behind the Orbital Express (OE) mission. Planning the satellite mission operations for OE required the ability to create a plan which could be executed autonomously over variable conditions. The Automated-Scheduling and Planning Environment (ASPEN)tool, developed at the Jet Propulsion Laboratory, was used to create the schedule of events in each daily plan for the two satellites of the OE mission. This paper presents an introduction to the ASPEN tool, the constraints of the OE domain, the variable conditions that were presented within the mission, and the solution to operations that ASPEN provided. ASPEN has been used in several other domains, including research rovers, Deep Space Network scheduling research, and in flight operations for the ASE project's EO1 satellite. Related work is discussed, as are the future of ASPEN and the future of autonomous satellite servicing.

  1. Mission control activity during STS-61 EVA

    NASA Technical Reports Server (NTRS)

    1993-01-01

    An overall view in the JSC Mission Control Center (MCC) during one of the five space walks performed to service the Hubble Space Telescope (HST) temporarily berthed in Endeavour's cargo bay. STS-61 lead Flight Director Milt Heflin is at right edge of frame.

  2. Advanced technologies for Mission Control Centers

    NASA Technical Reports Server (NTRS)

    Dalton, John T.; Hughes, Peter M.

    1991-01-01

    Advance technologies for Mission Control Centers are presented in the form of the viewgraphs. The following subject areas are covered: technology needs; current technology efforts at GSFC (human-machine interface development, object oriented software development, expert systems, knowledge-based software engineering environments, and high performance VLSI telemetry systems); and test beds.

  3. Mission operations concepts for Earth Observing System (EOS)

    NASA Technical Reports Server (NTRS)

    Kelly, Angelita C.; Taylor, Thomas D.; Hawkins, Frederick J.

    1991-01-01

    Mission operation concepts are described which are being used to evaluate and influence space and ground system designs and architectures with the goal of achieving successful, efficient, and cost-effective Earth Observing System (EOS) operations. Emphasis is given to the general characteristics and concepts developed for the EOS Space Measurement System, which uses a new series of polar-orbiting observatories. Data rates are given for various instruments. Some of the operations concepts which require a total system view are also examined, including command operations, data processing, data accountability, data archival, prelaunch testing and readiness, launch, performance monitoring and assessment, contingency operations, flight software maintenance, and security.

  4. Terra Mission Operations: Launch to the Present (and Beyond)

    NASA Technical Reports Server (NTRS)

    Thome, Kurt; Kelly, Angelita; Moyer, Eric; Mantziaras, Dimitrios; Case, Warren

    2014-01-01

    The Terra satellite, flagship of NASAs long-term Earth Observing System (EOS) Program, continues to provide useful earth science observations well past its 5-year design lifetime. This paper describes the evolution of Terra operations, including challenges and successes and the steps taken to preserve science requirements and prolong spacecraft life. Working cooperatively with the Terra science and instrument teams, including NASAs international partners, the mission operations team has successfully kept the Terra operating continuously, resolving challenges and adjusting operations as needed. Terra retains all of its observing capabilities (except Short Wave Infrared) despite its age. The paper also describes concepts for future operations.

  5. Mission operations concepts for Earth Observing System (EOS)

    NASA Technical Reports Server (NTRS)

    Kelly, Angelita C.; Taylor, Thomas D.; Hawkins, Frederick J.

    1991-01-01

    Mission operation concepts are described which are being used to evaluate and influence space and ground system designs and architectures with the goal of achieving successful, efficient, and cost-effective Earth Observing System (EOS) operations. Emphasis is given to the general characteristics and concepts developed for the EOS Space Measurement System, which uses a new series of polar-orbiting observatories. Data rates are given for various instruments. Some of the operations concepts which require a total system view are also examined, including command operations, data processing, data accountability, data archival, prelaunch testing and readiness, launch, performance monitoring and assessment, contingency operations, flight software maintenance, and security.

  6. An operations concept methodology to achieve low-cost mission operations

    NASA Technical Reports Server (NTRS)

    Ledbetter, Kenneth W.; Wall, Stephen D.

    1993-01-01

    Historically, the Mission Operations System (MOS) for a space mission has been designed last because it is needed last. This has usually meant that the ground system must adjust to the flight vehicle design, sometimes at a significant cost. As newer missions have increasingly longer flight operations lifetimes, the MOS becomes proportionally more difficult and more resource-consuming. We can no longer afford to design the MOS last. The MOS concept may well drive the spacecraft, instrument, and mission designs, as well as the ground system. A method to help avoid these difficulties, responding to the changing nature of mission operations is presented. Proper development and use of an Operations Concept document results in a combined flight and ground system design yielding enhanced operability and producing increased flexibility for less cost.

  7. The MAP Autonomous Mission Control System

    NASA Technical Reports Server (NTRS)

    Breed, Juile; Coyle, Steven; Blahut, Kevin; Dent, Carolyn; Shendock, Robert; Rowe, Roger

    2000-01-01

    The Microwave Anisotropy Probe (MAP) mission is the second mission in NASA's Office of Space Science low-cost, Medium-class Explorers (MIDEX) program. The Explorers Program is designed to accomplish frequent, low cost, high quality space science investigations utilizing innovative, streamlined, efficient management, design and operations approaches. The MAP spacecraft will produce an accurate full-sky map of the cosmic microwave background temperature fluctuations with high sensitivity and angular resolution. The MAP spacecraft is planned for launch in early 2001, and will be staffed by only single-shift operations. During the rest of the time the spacecraft must be operated autonomously, with personnel available only on an on-call basis. Four (4) innovations will work cooperatively to enable a significant reduction in operations costs for the MAP spacecraft. First, the use of a common ground system for Spacecraft Integration and Test (I&T) as well as Operations. Second, the use of Finite State Modeling for intelligent autonomy. Third, the integration of a graphical planning engine to drive the autonomous systems without an intermediate manual step. And fourth, the ability for distributed operations via Web and pager access.

  8. The OSIRIS-Rex Asteroid Sample Return: Mission Operations Design

    NASA Technical Reports Server (NTRS)

    Gal-Edd, Jonathan; Cheuvront, Allan

    2014-01-01

    The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the missions science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the SRC lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis.Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together space craft, instrument and operations scenarios. The project implemented lessons learned from other small body missions: APLNEAR, JPLDAWN and ESARosetta. The key lesson learned was expected the unexpected and implement planning tools early in the lifecycle. In preparation to PDR, the project changed the asteroid arrival date, to arrive one year earlier and provided additional time margin. STK is used for Mission Design and STKScheduler for instrument coverage analysis.

  9. Rosetta Mission Status: Toward the End of Comet Phase Operations

    NASA Astrophysics Data System (ADS)

    Martin, Patrick

    2016-04-01

    While having continued attempting to renew contacts with the Philae Lander on the surface of comet C67-P/Churyumov-Gerasimenko through 2015 and early 2016, the Rosetta Orbiter has passed the perihelion milestone in August 2015, completed its nominal mission in December 2015 and is now heading further away from the Sun. The comet Escort Phase of the mission has yielded an impressive science return, collecting a wealth of data from the nucleus and its environment at various levels of cometary activity. This summary presentation will provide a brief overview of the mission as it approaches the final stages of mission operations, with the Orbiter foreseen to be placed on the nucleus' surface on 30 September 2016.

  10. The Spacecraft Emergency Response System (SERS) for Autonomous Mission Operations

    NASA Technical Reports Server (NTRS)

    Breed, Julia; Chu, Kai-Dee; Baker, Paul; Starr, Cynthia; Fox, Jeffrey; Baitinger, Mick

    1998-01-01

    Today, most mission operations are geared toward lowering cost through unmanned operations. 7-day/24-hour operations are reduced to either 5-day/8-hour operations or become totally autonomous, especially for deep-space missions. Proper and effective notification during a spacecraft emergency could mean success or failure for an entire mission. The Spacecraft Emergency Response System (SERS) is a tool designed for autonomous mission operations. The SERS automatically contacts on-call personnel as needed when crises occur, either on-board the spacecraft or within the automated ground systems. Plus, the SERS provides a group-ware solution to facilitate the work of the person(s) contacted. The SERS is independent of the spacecraft's automated ground system. It receives and catalogues reports for various ground system components in near real-time. Then, based on easily configurable parameters, the SERS determines whom, if anyone, should be alerted. Alerts may be issued via Sky-Tel 2-way pager, Telehony, or e-mail. The alerted personnel can then review and respond to the spacecraft anomalies through the Netscape Internet Web Browser, or directly review and respond from the Sky-Tel 2-way pager.

  11. The Spacecraft Emergency Response System (SERS) for Autonomous Mission Operations

    NASA Technical Reports Server (NTRS)

    Breed, Julia; Chu, Kai-Dee; Baker, Paul; Starr, Cynthia; Fox, Jeffrey; Baitinger, Mick

    1998-01-01

    Today, most mission operations are geared toward lowering cost through unmanned operations. 7-day/24-hour operations are reduced to either 5-day/8-hour operations or become totally autonomous, especially for deep-space missions. Proper and effective notification during a spacecraft emergency could mean success or failure for an entire mission. The Spacecraft Emergency Response System (SERS) is a tool designed for autonomous mission operations. The SERS automatically contacts on-call personnel as needed when crises occur, either on-board the spacecraft or within the automated ground systems. Plus, the SERS provides a group-ware solution to facilitate the work of the person(s) contacted. The SERS is independent of the spacecraft's automated ground system. It receives and catalogues reports for various ground system components in near real-time. Then, based on easily configurable parameters, the SERS determines whom, if anyone, should be alerted. Alerts may be issued via Sky-Tel 2-way pager, Telehony, or e-mail. The alerted personnel can then review and respond to the spacecraft anomalies through the Netscape Internet Web Browser, or directly review and respond from the Sky-Tel 2-way pager.

  12. The BRITE Constellation Nanosatellite Mission: Testing, Commissioning, and Operations

    NASA Astrophysics Data System (ADS)

    Pablo, H.; Whittaker, G. N.; Popowicz, A.; Mochnacki, S. M.; Kuschnig, R.; Grant, C. C.; Moffat, A. F. J.; Rucinski, S. M.; Matthews, J. M.; Schwarzenberg-Czerny, A.; Handler, G.; Weiss, W. W.; Baade, D.; Wade, G. A.; Zocłońska, E.; Ramiaramanantsoa, T.; Unterberger, M.; Zwintz, K.; Pigulski, A.; Rowe, J.; Koudelka, O.; Orleański, P.; Pamyatnykh, A.; Neiner, C.; Wawrzaszek, R.; Marciniszyn, G.; Romano, P.; Woźniak, G.; Zawistowski, T.; Zee, R. E.

    2016-12-01

    BRIght Target Explorer (BRITE) Constellation, the first nanosatellite mission applied to astrophysical research, is a collaboration among Austria, Canada and Poland. The fleet of satellites (6 launched; 5 functioning) performs precise optical photometry of the brightest stars in the night sky. A pioneering mission like BRITE—with optics and instruments restricted to small volume, mass and power in several nanosatellites, whose measurements must be coordinated in orbit—poses many unique challenges. We discuss the technical issues, including problems encountered during on-orbit commissioning (especially higher-than-expected sensitivity of the CCDs to particle radiation). We describe in detail how the BRITE team has mitigated these problems, and provide a complete overview of mission operations. This paper serves as a template for how to effectively plan, build and operate future low-cost niche-driven space astronomy missions. Based on data collected by the BRITE Constellation satellite mission, designed, built, launched, operated and supported by the Austrian Research Promotion Agency (FFG), the University of Vienna, the Technical University of Graz, the Canadian Space Agency (CSA), the University of Toronto Institute for Aerospace Studies (UTIAS), the Foundation for Polish Science & Technology (FNiTP MNiSW), and National Science Centre (NCN).

  13. Apollo 11 mission: Glycol temperature control valve

    NASA Technical Reports Server (NTRS)

    1970-01-01

    An analysis was made of the cause or causes of malfunctions in the glycol temperature control valve during the Apollo 11 mission. The valve was designed to control inlet temperatures at 45 (+ or - 3) F. Test results show malfunctions were caused by a bearing failure on the worm gear shaft in the actuator. It was concluded that no corrective action was needed because an existing procedure allows manual setting of the value at a position which will meet system requirements.

  14. The OSIRIS-REx Asteroid Sample Return Mission Operations Design

    NASA Technical Reports Server (NTRS)

    Gal-Edd, Jonathan S.; Cheuvront, Allan

    2015-01-01

    OSIRIS-REx is an acronym that captures the scientific objectives: Origins, Spectral Interpretation, Resource Identification, and Security-Regolith Explorer. OSIRIS-REx will thoroughly characterize near-Earth asteroid Bennu (Previously known as 1019551999 RQ36). The OSIRIS-REx Asteroid Sample Return Mission delivers its science using five instruments and radio science along with the Touch-And-Go Sample Acquisition Mechanism (TAGSAM). All of the instruments and data analysis techniques have direct heritage from flown planetary missions. The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the mission's science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the Sample Return Capsule (SRC) lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis. Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together spacecraft, instrument and operations scenarios. Asteroid Touch and Go (TAG) has various options varying from ground only to fully automated (natural feature tracking). Spacecraft constraints such as thermo and high gain antenna pointing impact the timeline. The mission is sensitive to navigation errors, so a late command update has been implemented. The project implemented lessons learned from other "small body" missions. The key lesson learned was 'expect the unexpected' and implement planning tools early in the lifecycle

  15. Study 2.6 operations analysis mission characterization

    NASA Technical Reports Server (NTRS)

    Wolfe, R. R.

    1973-01-01

    An analysis of the current operations concepts of NASA and DoD is presented to determine if alternatives exist which may improve the utilization of resources. The final product is intended to show how sensitive these ground rules and design approaches are relative to the total cost of doing business. The results are comparative in nature, and assess one concept against another as opposed to establishing an absolute cost value for program requirements. An assessment of the mission characteristics is explained to clarify the intent, scope, and direction of this effort to improve the understanding of what is to be accomplished. The characterization of missions is oriented toward grouping missions which may offer potential economic benefits by reducing overall program costs. Program costs include design, development, testing, and engineering, recurring unit costs for logistic vehicles, payload costs. and direct operating costs.

  16. Solar Orbiter Science Operations: Not A Typical Heliophysics Mission

    NASA Astrophysics Data System (ADS)

    Williams, David R.; De Groof, Anik; Walsh, Andrew

    2017-08-01

    ESA’s Solar Orbiter is scheduled for launch in February 2019, and will approach the Sun to a distance of 0.28 AU, in an orbit progressively more inclined to the Ecliptic plane. Solar Orbiter will provide landmark new views of a star, up-close, often observing its poles, while measuring the coupling of the solar phenomena and features to the relatively pristine solar wind that it measure in situ. The unique orbit of the spacecraft and the arrangement and composition of its scientific payload impose unique constraints on how scientific operations can be conducted. These operations involve long- to very short-term planning in carefully arranged steps, which have much in common with planetary-encounter missions than preceding heliophysics missions. In this presentation, we explain the details of how science observations will be arranged and conducted, often very far from Earth, and how data from the mission will be returned and distributed.

  17. Mission Operations Support Area (MOSA) for ground network support

    NASA Technical Reports Server (NTRS)

    Woods, Robert D.; Moser, Susan A.

    1993-01-01

    The Mission Operations Support Area (MOSA) has been designed utilizing numerous commercial off the shelf items allowing for easy maintenance and upgrades. At its inception, all equipment was at the forefront of technology. The system was created to provide the operator with a 'State of the Art' replacement for equipment that was becoming antiquated and virtually impossible to repair because new parts were no longer available. Although the Mini-NOCC provided adequate support to the Network for a number of years, it was quickly becoming ineffectual for higher data rate and non-standard missions. The MOSA will prove to be invaluable in the future as more and more missions require Ground Network support.

  18. GOES-8 and -9 launch and mission operations support overview

    NASA Astrophysics Data System (ADS)

    Bengston, Charlie; McCuistion, D.

    1996-10-01

    The new series GOES-8 and -9 launched in 1994 and 1995 provide more flexible instrument coverage and higher resolution than previous GOES spinners. This added flexibility and the 3-axis stabilized operating mode however resulted in a more complex satellite system with independent imager and sounder, and on-board image navigation systems requiring more daily commanding. Nearly 5000 realtime commands are currently sent each day to each GOES-8 and -9 spacecraft compared to 200 commands per day for GOES-7. These new technological advancements in spacecraft design presented new challenges for the NASA operations support personnel. In order to prepare for launch, post-launch test, and on-orbit operations, a rigorous mission planning scheme was developed to assure safe commanding of the flight system and monitoring of its state of health. This paper overviews the key mission operations approaches and philosophies developed for the GOES I-M missions and key operations tools that were developed to aid operations personnel in performing complex routine and special operations tasks.

  19. Systems engineering and integration processes involved with manned mission operations

    NASA Technical Reports Server (NTRS)

    Kranz, Eugene F.; Kraft, Christopher C.

    1993-01-01

    This paper will discuss three mission operations functions that are illustrative of the key principles of operations SE&I and of the processes and products involved. The flight systems process was selected to illustrate the role of the systems product line in developing the depth and cross disciplinary skills needed for SE&I and providing the foundation for dialogue between participating elements. FDDD was selected to illustrate the need for a structured process to assure that SE&I provides complete and accurate results that consistently support program needs. The flight director's role in mission operations was selected to illustrate the complexity of the risk/gain tradeoffs involved in the development of the flight techniques and flight rules process as well as the absolute importance of the leadership role in developing the technical, operational, and political trades.

  20. Evaluation of human operator visual performance capability for teleoperator missions.

    NASA Technical Reports Server (NTRS)

    Huggins, C. T.; Malone, T. B.; Shields, N. L., Jr.

    1973-01-01

    Investigation of the human operator visual performance demands of teleoperator system applications to earth-orbital missions involving visual system requirements for satellite retrieval and satellite servicing functions. The first phase of an experimental program implementing this investigation is described in terms of the overall test apparatus and procedures used, the specific tests performed, and the test results obtained.

  1. LADEE Mission Update 2 (Beginning of Science Operations) Reporter Package

    NASA Image and Video Library

    2013-11-19

    NASA's Lunar Atmosphere and Dust Environment Explorer, or LADEE, spacecraft has completed the check-out phase of its mission and has begun science operations around the moon. All the science instruments on-board have been examined by the LADEE team and have been cleared to begin collecting and analyzing the dust in the exosphere, or very thin atmosphere, that surrounds the moon.

  2. NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

    NASA Technical Reports Server (NTRS)

    Shull, Sarah A.; Peek, Kenneth E.

    2011-01-01

    With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better

  3. Space Mission Operations Ground Systems Integration Customer Service

    NASA Technical Reports Server (NTRS)

    Roth, Karl

    2014-01-01

    The facility, which is now the Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center in Huntsville, AL, has provided continuous space mission and related services for the space industry since 1961, from Mercury Redstone through the International Space Station (ISS). Throughout the long history of the facility and mission support teams, the HOSC has developed a stellar customer support and service process. In this era, of cost cutting, and providing more capability and results with fewer resources, space missions are looking for the most efficient way to accomplish their objectives. One of the first services provided by the facility was fax transmission of documents to, then, Cape Canaveral in Florida. The headline in the Marshall Star, the newspaper for the newly formed Marshall Space Flight Center, read "Exact copies of Documents sent to Cape in 4 minutes." The customer was Dr. Wernher von Braun. Currently at the HOSC we are supporting, or have recently supported, missions ranging from simple ISS payloads requiring little more than "bentpipe" telemetry access, to a low cost free-flyer Fast, Affordable, Science and Technology Satellite (FASTSAT), to a full service ISS payload Alpha Magnetic Spectrometer 2 (AMS2) supporting 24/7 operations at three operations centers around the world with an investment of over 2 billion dollars. The HOSC has more need and desire than ever to provide fast and efficient customer service to support these missions. Here we will outline how our customer-centric service approach reduces the cost of providing services, makes it faster and easier than ever for new customers to get started with HOSC services, and show what the future holds for our space mission operations customers. We will discuss our philosophy concerning our responsibility and accessibility to a mission customer as well as how we deal with the following issues: initial contact with a customer, reducing customer cost, changing regulations and security

  4. IMP-J attitude control prelaunch analysis and operations plan

    NASA Technical Reports Server (NTRS)

    Hooper, H. L.; Mckendrew, J. B.; Repass, G. D.

    1973-01-01

    A description of the attitude control support being supplied for the Explorer 50 mission is given. Included in the document are descriptions of the computer programs being used to support attitude determination, prediction, and control for the mission and descriptions of the operating procedures that will be used to accomplish mission objectives.

  5. Modeling actions and operations to support mission preparation

    NASA Technical Reports Server (NTRS)

    Malin, Jane T.; Ryan, D. P.; Schreckenghost, D. L.

    1994-01-01

    This paper describes two linked technology development projects to support Space Shuttle ground operations personnel, both during mission preparation analysis and related analyses in missions. The Space Propulsion Robust Analysis Tool (SPRAT) will provide intelligent support and automation for mission analysis setup, interpretation, reporting and documentation. SPRAT models the actions taken by flight support personnel during mission preparation and uses this model to generate an action plan. CONFIG will provide intelligent automation for procedure analyses and failure impact analyses, by simulating the interactions between operations and systems with embedded failures. CONFIG models the actions taken by crew during space vehicle malfunctions and simulates how the planned action sequences in procedures affect a device model. Jointly the SPRAT and CONFIG projects provide an opportunity to investigate how the nature of a task affects the representation of actions, and to determine a more general action representation supporting a broad range of tasks. This paper describes the problems in representing actions for mission preparation and their relation to planning and scheduling.

  6. Mission Operations Centers (MOCs): Integrating key spacecraft ground data system components

    NASA Astrophysics Data System (ADS)

    Harbaugh, Randy; Szakal, Donna

    1994-11-01

    In an environment characterized by decreasing budgets, limited system development time, and user needs for increased capabilities, the Mission Operations Division (MOD) at the National Aeronautics and Space Administration Goddard Space Flight Center initiated a new, cost-effective concept in developing its spacecraft ground data systems: the Mission Operations Center (MOC). In the MOC approach, key components are integrated into a comprehensive and cohesive spacecraft planning, monitoring, command, and control system with a single, state-of-the-art graphical user interface. The MOD is currently implementing MOC's, which feature a common, reusable, and extendable system architecture, to support the X-Ray Timing Explorer (XTE), Tropical Rainfall Measuring Mission (TRMM), and Advanced Composition Explorer (ACE) missions. As a result of the MOC approach, mission operations are integrated, and users can, with a single system, perform real-time health and safety monitoring, real-time command and control, real-time attitude processing, real-time and predictive graphical spacecraft monitoring, trend analysis, mission planning and scheduling, command generation and management, network scheduling, guide star selection, and (using an expert system) spacecraft monitoring and fault isolation. The MOD is also implementing its test and training simulators under the new MOC management structure. This paper describes the MOC concept, the management approaches used in developing MOC systems, the technologies employed and the development process improvement initiatives applied in implementing MOC systems, and the expected benefits to both the user and the mission project in using the MOC approach.

  7. STS payloads mission control study. Volume 2-A, Task 1: Joint products and functions for preflight planning of flight operations, training and simulations

    NASA Technical Reports Server (NTRS)

    1976-01-01

    Specific products and functions, and associated facility availability, applicable to preflight planning of flight operations were studied. Training and simulation activities involving joint participation of STS and payload operations organizations, are defined. The prelaunch activities required to prepare for the payload flight operations are emphasized.

  8. View of activity in the Mission Control Center during STS 41-D

    NASA Image and Video Library

    1984-06-26

    41D-3073 (30 Aug 1984) --- The beginning stages of a busy six-day mission are monitored by some NASA officials in the flight control room (FCR-1) of the Johnson Space Center's (JSC) mission control center (MCC). They are (l.-r., foreground) Daniel M. Germany, manager of the Shuttle flight equipment project offices; Eugene F. Kranz, director of mission operations; and Clifford E. Charlesworth, director of space operations.

  9. Constellation Mission Operation Working Group: ESMO Maneuver Planning Process Review

    NASA Technical Reports Server (NTRS)

    Moyer, Eric

    2015-01-01

    The Earth Science Mission Operation (ESMO) Project created an Independent Review Board to review our Conjunction Risk evaluation process and Maneuver Planning Process to identify improvements that safely manages mission conjunction risks, maintains ground track science requirements, and minimizes overall hours expended on High Interest Events (HIE). The Review Board is evaluating the current maneuver process which requires support by multiple groups. In the past year, there have been several changes to the processes although many prior and new concerns exist. This presentation will discuss maneuver process reviews and Board comments, ESMO assessment and path foward, ESMO future plans, recent changes and concerns.

  10. Cross support overview and operations concept for future space missions

    NASA Technical Reports Server (NTRS)

    Stallings, William; Kaufeler, Jean-Francois

    1994-01-01

    Ground networks must respond to the requirements of future missions, which include smaller sizes, tighter budgets, increased numbers, and shorter development schedules. The Consultative Committee for Space Data Systems (CCSDS) is meeting these challenges by developing a general cross support concept, reference model, and service specifications for Space Link Extension services for space missions involving cross support among Space Agencies. This paper identifies and bounds the problem, describes the need to extend Space Link services, gives an overview of the operations concept, and introduces complimentary CCSDS work on standardizing Space Link Extension services.

  11. Renita Fincke at Russian Mission Control Center

    NASA Image and Video Library

    2004-04-20

    Renita Fincke, wife of Expedition 9 Flight Engineer and NASA International Space Station Science Officer Michael Fincke, smiles with their two-year old son Chandra at the Russian Mission Control Center outside Moscow, Wednesday, April 21, 2004, following the successful docking of the Russian Soyuz capsule carrying Fincke, Expedition 9 Commander Gennady Padalka and European Space Agency astronaut Andre Kuipers of the Netherlands to the International Space Station. Photo Credit: (NASA/Bill Ingalls)

  12. View of USSR flight controllers in Mission Control during touchdown

    NASA Image and Video Library

    1975-07-21

    S75-28659 (21 July 1975) --- An overall view of the group of Soviet Union flight controllers who served at the Mission Control Center during the joint U.S.-USSR Apollo-Soyuz Test Project docking mission in Earth orbit. They are applauding the successful touchdown of the Soyuz spacecraft in Central Asia. The television monitor had just shown the land landing of the Soyuz descent vehicle.

  13. Interoperability for Space Mission Monitor and Control: Applying Technologies from Manufacturing Automation and Process Control Industries

    NASA Technical Reports Server (NTRS)

    Jones, Michael K.

    1998-01-01

    Various issues associated with interoperability for space mission monitor and control are presented in viewgraph form. Specific topics include: 1) Space Project Mission Operations Control Architecture (SuperMOCA) goals and methods for achieving them; 2) Specifics on the architecture: open standards ad layering, enhancing interoperability, and promoting commercialization; 3) An advertisement; 4) Status of the task - government/industry cooperation and architecture and technology demonstrations; and 5) Key features of messaging services and virtual devices.

  14. OTF CCSDS Mission Operations Prototype Parameter Service. Phase I: Exit Presentation

    NASA Technical Reports Server (NTRS)

    Reynolds, Walter F.; Lucord, Steven A.; Stevens, John E.

    2009-01-01

    This slide presentation reviews the prototype of phase 1 of the parameter service design of the CCSDS mission operations. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement the Parameter Service (2) Demonstrate interoperability between Houston MCC and a CCSDS Mission Operations compliant mission operations center (3) Utilize Mission Operations Common Architecture. THe parameter service design, interfaces, and structures are described.

  15. IUS/TUG orbital operations and mission support study. Volume 4: Project planning data

    NASA Technical Reports Server (NTRS)

    1975-01-01

    Planning data are presented for the development phases of interim upper stage (IUS) and tug systems. Major project planning requirements, major event schedules, milestones, system development and operations process networks, and relevant support research and technology requirements are included. Topics discussed include: IUS flight software; tug flight software; IUS/tug ground control center facilities, personnel, data systems, software, and equipment; IUS mission events; tug mission events; tug/spacecraft rendezvous and docking; tug/orbiter operations interface, and IUS/orbiter operations interface.

  16. Tracking and data system support for the Viking 1975 mission to Mars. Volume 3: Planetary operations

    NASA Technical Reports Server (NTRS)

    Mudgway, D. J.

    1977-01-01

    The support provided by the Deep Space Network to the 1975 Viking Mission from the first landing on Mars July 1976 to the end of the Prime Mission on November 15, 1976 is described and evaluated. Tracking and data acquisition support required the continuous operation of a worldwide network of tracking stations with 64-meter and 26-meter diameter antennas, together with a global communications system for the transfer of commands, telemetry, and radio metric data between the stations and the Network Operations Control Center in Pasadena, California. Performance of the deep-space communications links between Earth and Mars, and innovative new management techniques for operations and data handling are included.

  17. Foot Operation of Controls

    DTIC Science & Technology

    1971-01-01

    in which the maximum force may be applied ’. 2.6. Foot versus Hand Operation of Controls Grether (1946) investigated tracking accuracy with...airplane controls. Technical Note 550, National Advisory Committee for Aeronautics, Washington, D.C. GRETHER , W. P., 1946, A study of several

  18. The Envisat Mission Extension 2010- Implications for On-Ground and On-Board Operations

    NASA Astrophysics Data System (ADS)

    Diekmann, Frank-Jugen; Mesples, Daniel; Ventimiglia, Luca; Milsson, M.; Kuijper, Dirk Berger, Jean-Noel

    2010-12-01

    ESA's Earth Observation (EO) satellite ENVISAT was launched in 2002 with a nominal mission lifetime of five years. Given the excellent performance of the platform and the nine actively controlled instruments, the mission was extended until the end of 2010, when most of the onboard hydrazine will be exhausted. A concept for extending the Envisat mission has been defined in 2008, which is based on an altitude lowering and a new orbit control concept which will allow a continuation of the routine operations until end of 2013. ESA's control centre ESOC in Darmstadt, Germany, will be responsible to implement the orbit change, conduct a mini-commissioning phase following the altitude lowering and resume nominal operations afterwards. The actual orbit change manoeuvres will be carefully planned and executed, aiming at an optimization of fuel consumption. The manoeuvre strategy will allow achieving a reliable estimate of the residual fuel after the thruster firing sequences. One of the immediate consequences after the Envisat orbit change will be S-Band interferences during overlapping ENVISAT and ERS-2 ground station passes, affecting commanding, telemetry and ranging for the two missions operated from ESOC. This will require a dynamic allocation of ground station facilities, also being used by other Earth Observation satellites operated from ESOC. The ENVISAT and ERS2 operators will be supported during this new operations phase by an automation tool taking care of a number of Envisat routine activities. This paper summarizes the Envisat orbit change activities, the impact on routine operations and the conflict resolution strategies.

  19. The role of mission operations in spacecraft integration and test

    NASA Technical Reports Server (NTRS)

    Harvey, Raymond J.

    1994-01-01

    The participation of mission operations personnel in the spacecraft integration and test process offers significant benefits to spacecraft programs in terms of test efficiency, staffing and training efficiency, test completeness, and subsequent cost containment. Operations personnel who have had real-time contact experience and have been responsible for the assessment of on orbit spacecraft operations bring a unique view of spacecraft operations to pre-launch spacecraft test activities. Because of the unique view of the spacecraft/ground interface that experienced operations personnel have, they can propose optimum test approaches and optimum test data analysis techniques. Additionally, the testing that is typically required to validate operations methodologies can be integrated into spacecraft performance testing scenarios.

  20. The Cassini Solstice Mission: Streamlining Operations by Sequencing with PIEs

    NASA Technical Reports Server (NTRS)

    Vandermey, Nancy; Alonge, Eleanor K.; Magee, Kari; Heventhal, William

    2014-01-01

    The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks

  1. The Cassini Solstice Mission: Streamlining Operations by Sequencing with PIEs

    NASA Technical Reports Server (NTRS)

    Vandermey, Nancy; Alonge, Eleanor K.; Magee, Kari; Heventhal, William

    2014-01-01

    The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks

  2. Command and Control in Littoral Operations

    DTIC Science & Technology

    2016-05-13

    operate over vast distances and to repeatedly cross between domains to neutralize threats and accomplish the mission. Current doctrinal amphibious...to neutralize threats and accomplish the mission. Current doctrinal amphibious command and control (C2) relationships are ineffective for an...under a unified authority on- scene . 2 Admiral Mara and General Terra’s close and comfortable relationship was a great asset to the Amphibious

  3. User interface devices for mission control

    NASA Technical Reports Server (NTRS)

    Boatman, Wayne

    1987-01-01

    The Mission Control Center (MCC) at Johnson Space Center (JSC) in Houston, Texas, is being upgraded with new technology engineering/scientific workstations. These workstations will replace the existing consoles and will emulate the present hardware input and display media. The workstations will be using new and different input devices for the flight controller to interact with the workstation and mainframes. This paper presents the results of the User Interface survey conducted by the Workstation Prototype Lab (WPL). The WPL offered the opportunity for users to do hands-on evaluations of a number of user interface options prototyped by lab personnel.

  4. Activity in the Mission Control Center during Apollo 14

    NASA Image and Video Library

    1971-02-04

    S71-17610 (4 Feb. 1971) --- Partial view of activity in the Mission Operations Control Room in the Mission Control Center at the time the Apollo 14 S-IVB stage impacted on the lunar surface. The flight director's console is in the foreground. Eugene F. Kranz, chief of the MSC Flight Control Division, is in the right foreground. Seated at the console is Glynn S. Lunney, head of the Flight Director Office, Flight Control Division. Facing the camera is Gerald D. Griffin, flight director of the Third (Gold) Team. A seismic reading from the impact can be seen in the center background. The S-IVB impacted on the lunar surface at 1:40:54 a.m. (CST), Feb. 4, 1971, about 90 nautical miles south-southwest of the Apollo 12 passive seismometer. The energy release was comparable to 11 tons of TNT.

  5. Efficient mission control for the 48-satellite Globalstar Constellation

    NASA Technical Reports Server (NTRS)

    Smith, Dan

    1994-01-01

    The Globalstar system is being developed by Globalstar, Limited Partnership and will utilize 48 satellites in low earth orbit (See Figure 1) to create a world-wide mobile communications system consistent with Vice President Gore's vision of a Global Information Infrastructure. As a large long term commercial system developed by a newly formed organization, Globalstar provides an excellent opportunity to explore innovative solutions for highly efficient satellite command and control. Design and operational concepts being developed are unencumbered by existing physical and organizational infrastructures. This program really is 'starting with a clean sheet of paper'. Globalstar operations challenges can appear enormous. Clearly, assigning even a single person around the clock to monitor and control each satellite is excessive for Globalstar (it would require a staff of 200! . Even with only a single contact per orbit per satellite, data acquisitions will start or stop every 45 seconds! Although essentially identical, over time the satellites will develop their own 'personalities'and will re quire different data calibrations and levels of support. This paper discusses the Globalstar system and challenges and presents engineering concepts, system design decisions, and operations concepts which address the combined needs and concerns of satellite, ground system, and operations teams. Lessons from past missions have been applied, organizational barriers broken, partnerships formed across the mission segments, and new operations concepts developed for satellite constellation management. Control center requirements were then developed from the operations concepts.

  6. STS-35 Mission Manager Actions Room at the Marshall Space Flight Center Spacelab Payload Operations

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Due to loss of data used for pointing and operating the ultraviolet telescopes, MSFC ground teams were forced to aim the telescopes with fine tuning by the flight crew. This photo captures the activities at the Mission Manager Actions Room during the mission.

  7. Grand Challenge Problems in Real-Time Mission Control Systems for NASA's 21st Century Missions

    NASA Technical Reports Server (NTRS)

    Pfarr, Barbara B.; Donohue, John T.; Hughes, Peter M.

    1999-01-01

    Space missions of the 21st Century will be characterized by constellations of distributed spacecraft, miniaturized sensors and satellites, increased levels of automation, intelligent onboard processing, and mission autonomy. Programmatically, these missions will be noted for dramatically decreased budgets and mission development lifecycles. Current progress towards flexible, scaleable, low-cost, reusable mission control systems must accelerate given the current mission deployment schedule, and new technology will need to be infused to achieve desired levels of autonomy and processing capability. This paper will discuss current and future missions being managed at NASA's Goddard Space Flight Center in Greenbelt, MD. It will describe the current state of mission control systems and the problems they need to overcome to support the missions of the 21st Century.

  8. Asynchronous Message Service for Deep Space Mission Operations

    NASA Technical Reports Server (NTRS)

    Burleigh, Scott C.

    2006-01-01

    While the CCSDS (Consultative Committee for Space Data Systems) File Delivery Protocol (CFDP) provides internationally standardized file transfer functionality that can offer significant benefits for deep space mission operations, not all spacecraft communication requirements are necessarily best met by file transfer. In particular, continuous event-driven asynchronous message exchange may also be useful for communications with, among, and aboard spacecraft. CCSDS has therefore undertaken the development of a new Asynchronous Message Service (AMS) standard, designed to provide common functionality over a wide variety of underlying transport services, ranging from shared memory message queues to CCSDS telemetry systems. The present paper discusses the design concepts of AMS, their applicability to deep space mission operations problems, and the results of preliminary performance testing obtained from exercise of a prototype implementation.

  9. Mission Operations Planning with Preferences: An Empirical Study

    NASA Technical Reports Server (NTRS)

    Bresina, John L.; Khatib, Lina; McGann, Conor

    2006-01-01

    This paper presents an empirical study of some nonexhaustive approaches to optimizing preferences within the context of constraint-based, mixed-initiative planning for mission operations. This work is motivated by the experience of deploying and operating the MAPGEN (Mixed-initiative Activity Plan GENerator) system for the Mars Exploration Rover Mission. Responsiveness to the user is one of the important requirements for MAPGEN, hence, the additional computation time needed to optimize preferences must be kept within reasonabble bounds. This was the primary motivation for studying non-exhaustive optimization approaches. The specific goals of rhe empirical study are to assess the impact on solution quality of two greedy heuristics used in MAPGEN and to assess the improvement gained by applying a linear programming optimization technique to the final solution.

  10. Science Operations For Esa's Smart-1 Mission To The Moon

    NASA Astrophysics Data System (ADS)

    Almeida, M.; Foing, B.; Heather, D.; Marini, A.; Lumb, R.; Racca, G.

    The primary objective of the European Space Agency's SMART-1 mission to the Moon is to test and validate a new electric propulsion engine for potential use on other larger ESA Cornerstone missions. However, the SMART-1 spacecraft will also carry a number of scientific instruments and experiments for use en-route to and in orbit about the Moon. SMART-1's major operational constraint is that it will be only contacted twice per week. As a result, there will be a stronger emphasis on mid-term planning, and the spacecraft will be operated using a large list of telecommands sent during the communication windows. This approach leads to a higher probability of there being resource and/or instruments conflicts. To eliminate these, two software tools were developed: the Experiment Planning System (EPS), and the Project Test Bed (PTB). These tools will also allow us to predict the lunar coverage of the scien- tific instruments, and to simulate target selections.

  11. Dr. Gilruth and Dr. Kraft in Mission Control Center during Apollo 5 launch

    NASA Technical Reports Server (NTRS)

    1968-01-01

    Dr. Rober R. Gilruth (right), Manned Spacecraft Center (MSC) Director, sits with Dr. Christopher C. Kraft Jr., MSC Director of Flight Operations, at his flight operations director console in the Mission Control Center, bldg 30, during the Apollo 5 (LM-1/Saturn 204) unmanned space mission launch.

  12. Dr. Gilruth and Dr. Kraft - Mission Control Center (MCC) - Apollo V Launch - MSC

    NASA Image and Video Library

    1968-01-22

    S68-18733 (22 Jan. 1968) --- Dr. Robert R. Gilruth (right), MSC Director, sits with Dr. Christopher C. Kraft Jr., MSC director of flight operations, at his flight operations director console in the Mission Control Center, Building 30, during the Apollo 5 (LM-1/Saturn 204) unmanned space mission.

  13. PC-402 Pioneer Venus orbiter spacecraft mission operational characteristics document

    NASA Technical Reports Server (NTRS)

    Barker, F. C.; Butterworth, L. W.; Daniel, R. E.; Drean, R. J.; Filetti, K. A.; Fisher, J. N.; Nowak, L. A.; Porzucki, J.; Salvatore, J. O.; Tadler, G. A.

    1978-01-01

    The operational characteristics of the Orbiter spacecraft and its subsystems are described. In extensive detail. Description of the nominal phases, system interfaces, and the capabilities and limitations of system level performance are included along with functional and operational descriptions at the subsystem and unit level the subtleties of nominal operation as well as detailed capabilities and limitations beyond nominal performance are discussed. A command and telemetry logic flow diagram for each subsystem is included. Each diagram encountered along each command signal path into, and each telemetry signal path out of the subsystem. Normal operating modes that correspond to the performance of specific functions at the time of specific events in the mission are also discussed. Principal backup means of performing the normal Orbiter operating modes are included.

  14. The CONSERT operations planning process for the Rosetta mission

    NASA Astrophysics Data System (ADS)

    Rogez, Yves; Puget, Pascal; Zine, Sonia; Hérique, Alain; Kofman, Wlodek; Altobelli, Nicolas; Ashman, Mike; Barthélémy, Maud; Biele, Jens; Blazquez, Alejandro; Casas, Carlos M.; Sitjà, Marc Costa; Delmas, Cédric; Fantinati, Cinzia; Fronton, Jean-François; Geiger, Bernhard; Geurts, Koen; Grieger, Björn; Hahnel, Ronny; Hoofs, Raymond; Hubault, Armelle; Jurado, Eric; Küppers, Michael; Maibaum, Michael; Moussi-Souffys, Aurélie; Muñoz, Pablo; O'Rourke, Laurence; Pätz, Brigitte; Plettemeier, Dirk; Ulamec, Stephan; Vallat, Claire

    2016-08-01

    The COmet Nucleus Sounding Experiment by Radio wave Transmission (CONSERT / Rosetta) has been designed to sound the interior of the comet 67P/Churyumov-Gerasimenko. This instrument consists of two parts: one onboard Rosetta and the other one onboard Philae. A good CONSERT science measurement sequence requires joint operations of both spacecrafts in a relevant geometry. The geometric constraints to be fulfilled involve the position and the orientation of both Rosetta and Philae. At the moment of planning the post-landing and long-term science operations for Rosetta instruments, the actual comet shape and the landing location remained largely unknown. In addition, the necessity of combining operations of Rosetta spacecraft and Philae spacecraft makes the planning process for CONSERT particularly complex. In this paper, we present the specific methods and tools we developed, in close collaboration with the mission and the science operation teams for both Rosetta and Philae, to identify, rank and plan the operations for CONSERT science measurements. The presented methods could be applied to other missions involving joint operations between two platforms, on a complex shaped object.

  15. Prototype Interoperability Document between NASA-JSC and DLR-GSOC Describing the CCSDS SM and C Mission Operations Prototype

    NASA Technical Reports Server (NTRS)

    Lucord, Steve A.; Gully, Sylvain

    2009-01-01

    The purpose of the PROTOTYPE INTEROPERABILITY DOCUMENT is to document the design and interfaces for the service providers and consumers of a Mission Operations prototype between JSC-OTF and DLR-GSOC. The primary goal is to test the interoperability sections of the CCSDS Spacecraft Monitor & Control (SM&C) Mission Operations (MO) specifications between both control centers. An additional goal is to provide feedback to the Spacecraft Monitor and Control (SM&C) working group through the Review Item Disposition (RID) process. This Prototype is considered a proof of concept and should increase the knowledge base of the CCSDS SM&C Mission Operations standards. No operational capabilities will be provided. The CCSDS Mission Operations (MO) initiative was previously called Spacecraft Monitor and Control (SM&C). The specifications have been renamed to better reflect the scope and overall objectives. The working group retains the name Spacecraft Monitor and Control working group and is under the Mission Operations and Information Services Area (MOIMS) of CCSDS. This document will refer to the specifications as SM&C Mission Operations, Mission Operations or just MO.

  16. Prototype Interoperability Document between NASA-JSC and DLR-GSOC Describing the CCSDS SM and C Mission Operations Prototype

    NASA Technical Reports Server (NTRS)

    Lucord, Steve A.; Gully, Sylvain

    2009-01-01

    The purpose of the PROTOTYPE INTEROPERABILITY DOCUMENT is to document the design and interfaces for the service providers and consumers of a Mission Operations prototype between JSC-OTF and DLR-GSOC. The primary goal is to test the interoperability sections of the CCSDS Spacecraft Monitor & Control (SM&C) Mission Operations (MO) specifications between both control centers. An additional goal is to provide feedback to the Spacecraft Monitor and Control (SM&C) working group through the Review Item Disposition (RID) process. This Prototype is considered a proof of concept and should increase the knowledge base of the CCSDS SM&C Mission Operations standards. No operational capabilities will be provided. The CCSDS Mission Operations (MO) initiative was previously called Spacecraft Monitor and Control (SM&C). The specifications have been renamed to better reflect the scope and overall objectives. The working group retains the name Spacecraft Monitor and Control working group and is under the Mission Operations and Information Services Area (MOIMS) of CCSDS. This document will refer to the specifications as SM&C Mission Operations, Mission Operations or just MO.

  17. Using Modeling to Predict Medical Requirements for Special Operations Missions

    DTIC Science & Technology

    2008-07-30

    military force. Information operations involve adversely affecting the information systems of an adversary.1 Many of these missions are joint...Medical System . In 2007, the Air Force asked NHRC to conduct another proof-of-concept study to demonstrate the benefits of modeling medical supply...are used for this purpose. (NHRC is currently in the process of matching these patient conditions to International Classification of Diseases codes

  18. Data acquisition system for operational earth observation missions

    NASA Technical Reports Server (NTRS)

    Deerwester, J. M.; Alexander, D.; Arno, R. D.; Edsinger, L. E.; Norman, S. M.; Sinclair, K. F.; Tindle, E. L.; Wood, R. D.

    1972-01-01

    The data acquisition system capabilities expected to be available in the 1980 time period as part of operational Earth observation missions are identified. By data acquisition system is meant the sensor platform (spacecraft or aircraft), the sensors themselves and the communication system. Future capabilities and support requirements are projected for the following sensors: film camera, return beam vidicon, multispectral scanner, infrared scanner, infrared radiometer, microwave scanner, microwave radiometer, coherent side-looking radar, and scatterometer.

  19. Correlation of ISS Electric Potential Variations with Mission Operations

    NASA Technical Reports Server (NTRS)

    Willis, Emily M.; Minow, Joseph I.; Parker, Linda Neergaard

    2014-01-01

    Spacecraft charging on the International Space Station (ISS) is caused by a complex combination of the low Earth orbit plasma environment, space weather events, operations of the high voltage solar arrays, and changes in the ISS configuration and orbit parameters. Measurements of the ionospheric electron density and temperature along the ISS orbit and variations in the ISS electric potential are obtained from the Floating Potential Measurement Unit (FPMU) suite of four plasma instruments (two Langmuir probes, a Floating Potential Probe, and a Plasma Impedance Probe) on the ISS. These instruments provide a unique capability for monitoring the response of the ISS electric potential to variations in the space environment, changes in vehicle configuration, and operational solar array power manipulation. In particular, rapid variations in ISS potential during solar array operations on time scales of tens of milliseconds can be monitored due to the 128 Hz sample rate of the Floating Potential Probe providing an interesting insight into high voltage solar array interaction with the space plasma environment. Comparing the FPMU data with the ISS operations timeline and solar array data provides a means for correlating some of the more complex and interesting ISS electric potential variations with mission operations. In addition, recent extensions and improvements to the ISS data downlink capabilities have allowed more operating time for the FPMU than ever before. The FPMU was operated for over 200 days in 2013 resulting in the largest data set ever recorded in a single year for the ISS. In this paper we provide examples of a number of the more interesting ISS charging events observed during the 2013 operations including examples of rapid charging events due to solar array power operations, auroral charging events, and other charging behavior related to ISS mission operations.

  20. Correlation of ISS Electric Potential Variations with Mission Operations

    NASA Technical Reports Server (NTRS)

    Willis, Emily M.; Minow, Joseph I.; Parker, Linda Neergaard

    2014-01-01

    Spacecraft charging on the International Space Station (ISS) is caused by a complex mix of the low Earth orbit plasma environment, space weather events, operations of the high voltage solar arrays, and changes in the ISS configuration and orbit parameters. Measurements of the ionospheric electron density and temperature along the ISS orbit and variations in the ISS electric potential are obtained from the Floating Potential Measurement Unit (FPMU) suite of four plasma instruments (two Langmuir probes, a Floating Potential Probe, and a Plasma Impedance Probe) on the ISS. These instruments provide a unique capability for monitoring the response of the ISS electric potential to variations in the space environment, changes in vehicle configuration, and operational solar array power manipulation. In particular, rapid variations in ISS potential during solar array operations on time scales of tens of milliseconds can be monitored due to the 128 Hz sample rate of the Floating Potential Probe providing an interesting insight into high voltage solar array interaction with the space plasma environment. Comparing the FPMU data with the ISS operations timeline and solar array data provides a means for correlating some of the more complex and interesting ISS electric potential variations with mission operations. In addition, recent extensions and improvements to the ISS data downlink capabilities have allowed more operating time for the FPMU than ever before. The FPMU was operated for over 200 days in 2013 resulting in the largest data set ever recorded in a single year for the ISS. This presentation will provide examples of a number of the more interesting ISS charging events observed during the 2013 operations including examples of rapid charging events due to solar array power operations, auroral charging events, and other charging behavior related to ISS mission operations.

  1. Evaluation of Army Remotely Piloted Vehicle Mission Payload Operator Performance in Simulated Artillery Missions.

    DTIC Science & Technology

    1983-11-01

    FILLING MEMORY A. DISPAYING MM~ORY ALU •"MEMORY A __V PPLN I OPA VIDEO MEOR AI 0 PIPELINE ,. :.5 b. DISPLAYING MEY A. FILLUIN MEORY 66 ’ Figure 12...participants. The results are presented in terms of the four jamming levels for each of the two missions and are organized into four major categories: 1...The scene track mode with its larger tracking window would be a better choice for offset tracking operation as long as high precision is not

  2. A new systems engineering approach to streamlined science and mission operations for the Far Ultraviolet Spectroscopic Explorer (FUSE)

    NASA Technical Reports Server (NTRS)

    Butler, Madeline J.; Sonneborn, George; Perkins, Dorothy C.

    1994-01-01

    The Mission Operations and Data Systems Directorate (MO&DSD, Code 500), the Space Sciences Directorate (Code 600), and the Flight Projects Directorate (Code 400) have developed a new approach to combine the science and mission operations for the FUSE mission. FUSE, the last of the Delta-class Explorer missions, will obtain high resolution far ultraviolet spectra (910 - 1220 A) of stellar and extragalactic sources to study the evolution of galaxies and conditions in the early universe. FUSE will be launched in 2000 into a 24-hour highly eccentric orbit. Science operations will be conducted in real time for 16-18 hours per day, in a manner similar to the operations performed today for the International Ultraviolet Explorer. In a radical departure from previous missions, the operations concept combines spacecraft and science operations and data processing functions in a single facility to be housed in the Laboratory for Astronomy and Solar Physics (Code 680). A small missions operations team will provide the spacecraft control, telescope operations and data handling functions in a facility designated as the Science and Mission Operations Center (SMOC). This approach will utilize the Transportable Payload Operations Control Center (TPOCC) architecture for both spacecraft and instrument commanding. Other concepts of integrated operations being developed by the Code 500 Renaissance Project will also be employed for the FUSE SMOC. The primary objective of this approach is to reduce development and mission operations costs. The operations concept, integration of mission and science operations, and extensive use of existing hardware and software tools will decrease both development and operations costs extensively. This paper describes the FUSE operations concept, discusses the systems engineering approach used for its development, and the software, hardware and management tools that will make its implementation feasible.

  3. Rosetta science operations in support of the Philae mission

    NASA Astrophysics Data System (ADS)

    Ashman, Mike; Barthélémy, Maud; O`Rourke, Laurence; Almeida, Miguel; Altobelli, Nicolas; Costa Sitjà, Marc; García Beteta, Juan José; Geiger, Bernhard; Grieger, Björn; Heather, David; Hoofs, Raymond; Küppers, Michael; Martin, Patrick; Moissl, Richard; Múñoz Crego, Claudio; Pérez-Ayúcar, Miguel; Sanchez Suarez, Eduardo; Taylor, Matt; Vallat, Claire

    2016-08-01

    The international Rosetta mission was launched on 2nd March 2004 and after its ten year journey, arrived at its target destination of comet 67P/Churyumov-Gerasimenko, during 2014. Following the January 2014 exit from a two and half year hibernation period, Rosetta approached and arrived at the comet in August 2014. In November 2014, the Philae lander was deployed from Rosetta onto the comet's surface after which the orbiter continued its approximately one and a half year comet escort phase. The Rosetta Science Ground Segment's primary roles within the project are to support the Project Scientist and the Science Working Team, in order to ensure the coordination, development, validation and delivery of the desired science operations plans and their associated operational products throughout the mission., whilst also providing support to the Principle Investigator teams (including the Philae lander team) in order to ensure the provision of adequate data to the Planetary Science Archive. The lead up to, and execution of, the November 2014 Philae landing, and the subsequent Philae activities through 2015, have presented numerous unique challenges to the project teams. This paper discusses these challenges, and more specifically, their impact on the overall mission science planning activities. It details how the Rosetta Science Ground Segment has addressed these issues in collaboration with the other project teams in order to accommodate Philae operations within the continually evolving Rosetta science planning process.

  4. STS-9/Spacelab 1 mission control center activity

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Karl Knott, project scientist for Spacelab 1, communicates with a payload specialist aboard Spacelab in the Shuttle Columbia. Representing the European Space Agency (ESA), Dr. Knott is at a console in the payload operations control center (POCC) in JSC's mission control center (45265-7); Steve Noneman, Blue Shift mass memory unit (MMU) manager, listens to a payload specialist's response while other payload controllers busy themselves at their consoles (45268); Alternate Spacelab 1 payload specialist Michael L. Lampton communicates with onboard personnel during flight day 5 of STS-9. Dr. Lampton's console is in the POCC. In the background is William Bock, crew interface coordinator for the Blue Shift (45269).

  5. Standard protocol stack for mission control

    NASA Technical Reports Server (NTRS)

    Hooke, Adrian J.

    1994-01-01

    It is proposed to create a fully 'open' architectural specification for standardized space mission command and control. By being open, i.e., independent for any particular implementation, diversity and competition will be encouraged among future commercial suppliers of space equipment and systems. Customers of the new standard capability are expected to include: (1) the civil space community (e.g., NASA, NOAA, international Agencies); (2) the military space community (e.g., Air Force, Navy, intelligence); and (3) the emerging commercial space community (e.g., mobile satellite service providers).

  6. Seismometer readings studied in Mission Control Center

    NASA Technical Reports Server (NTRS)

    1971-01-01

    The seismometer reading from the impact made by the Apollo 15 Saturn S-IVB stage when it struck the lunar surface is studied by scientists in the Mission Control Center. Dr. Gary Latham (dark suit, wearing lapel button) of Columbia University is responsible for the design and experiment data analysis of the Passive Seismic Experiment of the Apollo Lunar Surface Experiment Package (ALSEP). The man on the left, writing, is Nafi Toksos of the Massachusetts Institute of Technology. Looking on at upper left is Dave Lammlein, also with Columbia.

  7. Seismometer readings studied in Mission Control Center

    NASA Image and Video Library

    1971-07-29

    The seismometer reading from the impact made by the Apollo 15 Saturn S-IVB stage when it struck the lunar surface is studied by scientists in the Mission Control Center. Dr. Gary Latham (dark suit, wearing lapel button) of Columbia University is responsible for the design and experiment data analysis of the Passive Seismic Experiment of the Apollo Lunar Surface Experiment Package (ALSEP). The man on the left, writing, is Nafi Toksos of the Massachusetts Institute of Technology. Looking on at upper left is Dave Lamneline, also with Columbia.

  8. View of Mission Control Center during the Apollo 13 emergency return

    NASA Technical Reports Server (NTRS)

    1970-01-01

    As the Apollo 13 crewmen entered their final 24 hours in space, several persons important to the mission remained attentive at consoles in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) at Manned Spacecraft Center. Among those monitoring communications and serving in supervisory capacities were (from left)Thomas H. McMullen, Office of Manned Space Flight, Shift 1 Mission Director; Dale Myers, Associate Administrator, Manned Space Flight; Chester M. Lee of the Apollo Program Directorate, OMSF, Apollo 13 Mission Director; and Dr. Rocco A. Petrone, Apollo Program Dirctor, OMSF. All four were from NASA Headquarters in Washington, D.C.

  9. Mission Control Center enhancement opportunities in the 1990's

    NASA Technical Reports Server (NTRS)

    Hartman, Wayne

    1992-01-01

    The purpose of this paper is to present a framework for understanding the major enhancement opportunities for Air Force Mission Control Center/Test Support Centers (MCC's/TSC's) in the 1990's. Much of this paper is based on the findings of Study 232 and work currently underway in Study 2-6 for the Air Force Systems Command, Space System Division, Network Program Office. In this paper, we will address MCC/TSC enhancement needs primarily from the operator perspective, in terms of the increased capabilities required to improve space operations task performance.

  10. Sleep and cognitive function of crewmembers and mission controllers working 24-h shifts during a simulated 105-day spaceflight mission

    NASA Astrophysics Data System (ADS)

    Barger, Laura K.; Wright, Kenneth P.; Burke, Tina M.; Chinoy, Evan D.; Ronda, Joseph M.; Lockley, Steven W.; Czeisler, Charles A.

    2014-01-01

    The success of long-duration space missions depends on the ability of crewmembers and mission support specialists to be alert and maintain high levels of cognitive function while operating complex, technical equipment. We examined sleep, nocturnal melatonin levels and cognitive function of crewmembers and the sleep and cognitive function of mission controllers who participated in a high-fidelity 105-day simulated spaceflight mission at the Institute of Biomedical Problems (Moscow). Crewmembers were required to perform daily mission duties and work one 24-h extended duration work shift every sixth day. Mission controllers nominally worked 24-h extended duration shifts. Supplemental lighting was provided to crewmembers and mission controllers. Participants' sleep was estimated by wrist-actigraphy recordings. Overall, results show that crewmembers and mission controllers obtained inadequate sleep and exhibited impaired cognitive function, despite countermeasure use, while working extended duration shifts. Crewmembers averaged 7.04±0.92 h (mean±SD) and 6.94±1.08 h (mean±SD) in the two workdays prior to the extended duration shifts, 1.88±0.40 h (mean±SD) during the 24-h work shift, and then slept 10.18±0.96 h (mean±SD) the day after the night shift. Although supplemental light was provided, crewmembers' average nocturnal melatonin levels remained elevated during extended 24-h work shifts. Naps and caffeine use were reported by crewmembers during ˜86% and 45% of extended night work shifts, respectively. Even with reported use of wake-promoting countermeasures, significant impairments in cognitive function were observed. Mission controllers slept 5.63±0.95 h (mean±SD) the night prior to their extended duration work shift. On an average, 89% of night shifts included naps with mission controllers sleeping an average of 3.4±1.0 h (mean±SD) during the 24-h extended duration work shift. Mission controllers also showed impaired cognitive function during extended

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

    NASA Technical Reports Server (NTRS)

    Dunbar, J. C.

    1972-01-01

    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.

  12. View of activity in Mission Control Center during Apollo 15 lunar landing

    NASA Technical Reports Server (NTRS)

    1971-01-01

    An overall, wide-angle lens view of activity in the Mission Operations Control Room in the Mission Control Center during the landing of the Apollo 15 Lunar Module (LM) on the Moon. The LM 'Falcon' touched down on the lunar surface at ground elapsed time of 104 hours 42 minutes 29 seconds.

  13. View of activity in Mission Control Center during Lunar Module liftoff

    NASA Technical Reports Server (NTRS)

    1971-01-01

    The liftoff from the Moon of the Apollo 15 Lunar Module 'Falcon' ascent stage is viewed on the television monitor in the Mission Operations Control Room in the Mission Control Center by Granvil A. Pennington, an Instruments and Communications Systems Officer.

  14. Multiphase pumping - operation & control

    SciTech Connect

    Salis, J. de; Marolies, C. de; Falcimaigne, J.

    1996-12-31

    This paper reviews field issues related to the planning, installation and operation of the helico-axial multiphase pumps. Interest for multiphase production, which leads to simpler and smaller in-field installations, is primarily dictated by the need for more a cost effective production system. Multiphase pumping is essentially a means of adding energy to the unprocessed effluent which enables the liquid/gas mixture to be transported over long distances without the need for prior separation. The Poseidon helico-axial pumps, under normal operating conditions, are largely unaffected by process fluctuations at pump inlet (changes in pressure, liquid or gas flow rate). They have demonstrated a stable behavior (self-adaptive capability with regards to instantaneous changes). A multiphase pump set is designed to operate under changing/fluctuating process conditions. An important issue related to pump operability and flexibility has to do with the driver selection: fixed speed vs. variable speed. In some cases a fixed speed drive provides sufficient operational flexibility. In other cases variable speed can be chosen. Pump operation & control strategies are presented and discussed.

  15. Robotic assembly and maintenance of future space stations based on the ISS mission operations experience

    NASA Astrophysics Data System (ADS)

    Rembala, Richard; Ower, Cameron

    2009-10-01

    MDA has provided 25 years of real-time engineering support to Shuttle (Canadarm) and ISS (Canadarm2) robotic operations beginning with the second shuttle flight STS-2 in 1981. In this capacity, our engineering support teams have become familiar with the evolution of mission planning and flight support practices for robotic assembly and support operations at mission control. This paper presents observations on existing practices and ideas to achieve reduced operational overhead to present programs. It also identifies areas where robotic assembly and maintenance of future space stations and space-based facilities could be accomplished more effectively and efficiently. Specifically, our experience shows that past and current space Shuttle and ISS assembly and maintenance operations have used the approach of extensive preflight mission planning and training to prepare the flight crews for the entire mission. This has been driven by the overall communication latency between the earth and remote location of the space station/vehicle as well as the lack of consistent robotic and interface standards. While the early Shuttle and ISS architectures included robotics, their eventual benefits on the overall assembly and maintenance operations could have been greater through incorporating them as a major design driver from the beginning of the system design. Lessons learned from the ISS highlight the potential benefits of real-time health monitoring systems, consistent standards for robotic interfaces and procedures and automated script-driven ground control in future space station assembly and logistics architectures. In addition, advances in computer vision systems and remote operation, supervised autonomous command and control systems offer the potential to adjust the balance between assembly and maintenance tasks performed using extra vehicular activity (EVA), extra vehicular robotics (EVR) and EVR controlled from the ground, offloading the EVA astronaut and even the robotic

  16. Risk Balance: A Key Tool for Mission Operations Assurance

    NASA Technical Reports Server (NTRS)

    Bryant, Larry W.; Faris, Grant B.

    2011-01-01

    The Mission Operations Assurance (MOA) discipline actively participates as a project member to achieve their common objective of full mission success while also providing an independent risk assessment to the Project Manager and Office of Safety and Mission Success staff. The cornerstone element of MOA is the independent assessment of the risks the project faces in executing its mission. Especially as the project approaches critical mission events, it becomes imperative to clearly identify and assess the risks the project faces. Quite often there are competing options for the project to select from in deciding how to execute the event. An example includes choices between proven but aging hardware components and unused but unproven components. Timing of the event with respect to visual or telecommunications visibility can be a consideration in the case of Earth reentry or hazardous maneuver events. It is in such situations that MOA is called upon for a risk balance assessment or risk trade study to support their recommendation to the Project Manager for a specific option to select. In the following paragraphs we consider two such assessments, one for the Stardust capsule Earth return and the other for the choice of telecommunications system configuration for the EPOXI flyby of the comet Hartley 2. We discuss the development of the trade space for each project's scenario and characterize the risks of each possible option. The risk characterization we consider includes a determination of the severity or consequence of each risk if realized and the likelihood of its occurrence. We then examine the assessment process to arrive at a MOA recommendation. Finally we review each flight project's decision process and the outcome of their decisions.

  17. Risk Balance: A Key Tool for Mission Operations Assurance

    NASA Technical Reports Server (NTRS)

    Bryant, Larry W.; Faris, Grant B.

    2011-01-01

    The Mission Operations Assurance (MOA) discipline actively participates as a project member to achieve their common objective of full mission success while also providing an independent risk assessment to the Project Manager and Office of Safety and Mission Success staff. The cornerstone element of MOA is the independent assessment of the risks the project faces in executing its mission. Especially as the project approaches critical mission events, it becomes imperative to clearly identify and assess the risks the project faces. Quite often there are competing options for the project to select from in deciding how to execute the event. An example includes choices between proven but aging hardware components and unused but unproven components. Timing of the event with respect to visual or telecommunications visibility can be a consideration in the case of Earth reentry or hazardous maneuver events. It is in such situations that MOA is called upon for a risk balance assessment or risk trade study to support their recommendation to the Project Manager for a specific option to select. In the following paragraphs we consider two such assessments, one for the Stardust capsule Earth return and the other for the choice of telecommunications system configuration for the EPOXI flyby of the comet Hartley 2. We discuss the development of the trade space for each project's scenario and characterize the risks of each possible option. The risk characterization we consider includes a determination of the severity or consequence of each risk if realized and the likelihood of its occurrence. We then examine the assessment process to arrive at a MOA recommendation. Finally we review each flight project's decision process and the outcome of their decisions.

  18. Flight Operations for the LCROSS Lunar Impactor Mission

    NASA Technical Reports Server (NTRS)

    Tompkins, Paul D.; Hunt, Rusty; D'Ortenzio, Matt D.; Strong, James; Galal, Ken; Bresina, John L.; Foreman, Darin; Barber, Robert; Shirley, Mark; Munger, James; Drucker, Eric

    2010-01-01

    The LCROSS (Lunar CRater Observation and Sensing Satellite) mission was conceived as a low-cost means of determining the nature of hydrogen concentrated at the polar regions of the moon. Co-manifested for launch with LRO (Lunar Reconnaissance Orbiter), LCROSS guided its spent Centaur upper stage into the Cabeus crater as a kinetic impactor, and observed the impact flash and resulting debris plume for signs of water and other compounds from a Shepherding Spacecraft. Led by NASA Ames Research Center, LCROSS flight operations spanned 112 days, from June 18 through October 9, 2009. This paper summarizes the experiences from the LCROSS flight, highlights the challenges faced during the mission, and examines the reasons for its ultimate success.

  19. Using Natural Language to Enable Mission Managers to Control Multiple Heterogeneous UAVs

    NASA Technical Reports Server (NTRS)

    Trujillo, Anna C.; Puig-Navarro, Javier; Mehdi, S. Bilal; Mcquarry, A. Kyle

    2016-01-01

    The availability of highly capable, yet relatively cheap, unmanned aerial vehicles (UAVs) is opening up new areas of use for hobbyists and for commercial activities. This research is developing methods beyond classical control-stick pilot inputs, to allow operators to manage complex missions without in-depth vehicle expertise. These missions may entail several heterogeneous UAVs flying coordinated patterns or flying multiple trajectories deconflicted in time or space to predefined locations. This paper describes the functionality and preliminary usability measures of an interface that allows an operator to define a mission using speech inputs. With a defined and simple vocabulary, operators can input the vast majority of mission parameters using simple, intuitive voice commands. Although the operator interface is simple, it is based upon autonomous algorithms that allow the mission to proceed with minimal input from the operator. This paper also describes these underlying algorithms that allow an operator to manage several UAVs.

  20. Early Mission Maneuver Operations for the Deep Space Climate Observatory Sun-Earth L1 Libration Point Mission

    NASA Technical Reports Server (NTRS)

    Roberts, Craig; Case, Sara; Reagoso, John; Webster, Cassandra

    2015-01-01

    The Deep Space Climate Observatory mission launched on February 11, 2015, and inserted onto a transfer trajectory toward a Lissajous orbit around the Sun-Earth L1 libration point. This paper presents an overview of the baseline transfer orbit and early mission maneuver operations leading up to the start of nominal science orbit operations. In particular, the analysis and performance of the spacecraft insertion, mid-course correction maneuvers, and the deep-space Lissajous orbit insertion maneuvers are discussed, com-paring the baseline orbit with actual mission results and highlighting mission and operations constraints..

  1. Mission Operations and Data Systems Directorate's operational/development network (MODNET) at Goddard Space Flight Center

    NASA Technical Reports Server (NTRS)

    1988-01-01

    A brief, informal narrative is provided that summarizes the results of all work accomplished during the period of the contract; June 1, 1987 through September 30, 1988; in support of Mission Operations and Data Systems Directorate's Operational Development Network (MODNET). It includes descriptions of work performed in each functional area and recommendations and conclusions based on the experience and results obtained.

  2. View of Mission Control Center during the Apollo 13 oxygen cell failure

    NASA Technical Reports Server (NTRS)

    1970-01-01

    Astronaut Alan B. Shepard Jr., prime crew commander of the Apollo 14 mission, monitors communications between the Apollo 13 spacecraft and Mission Control Center (MCC). He is seated at a console in the Mission Operations Control Room of the MCC. The main concern of the moment was action taken by the Apollo 13 crewment to make corrections inside the spacecraft following discovery of an oxygen cell failure several hours earlier.

  3. SAMPEX payload operation control center implementation

    NASA Technical Reports Server (NTRS)

    Mandl, Daniel; Koslosky, Jack; Mahmot, Ron; Rackley, Michael; Lauderdale, Jack

    1993-01-01

    The Solar Anomolous and Magnetospheric Explorer (SAMPEX) satellite was launched in July 1992. It was the first in the NASA Small Explorer (SMEX) series. In building the real-time control center facility, several new mission support challenges had to be met: CCSDS telemetry and command format, 900 Kbps telemetry data, and shorter turn-around time for control center development than previous missions. The SAMPEX Payload Operations Control Ccnter (POCC) was also the first control center for a new satellite to be based on the Transportable Payload Operations Control Center (TPOCC) system architecture and methodology. This approach has both guided the implementation of the SAMPEX control center and provided some of the building blocks. By using the TPOCC architecture to build the SAMPEX POCC, the real-time operations area was miniaturized into one room, whereas previous missions needed multiple large rooms. The development cost of the SAMPEX POCC was reduced from previous missions and will provide for further cost savings in the future SMEX satellites. This paper describes the system as built and some of the enhancements in progress to create this teleoperations environment.

  4. Hubble Space Telescope Servicing Mission 3A Rendezvous Operations

    NASA Technical Reports Server (NTRS)

    Lee, S.; Anandakrishnan, S.; Connor, C.; Moy, E.; Smith, D.; Myslinski, M.; Markley, L.; Vernacchio, A.

    2001-01-01

    The Hubble Space Telescope (HST) hardware complement includes six gas bearing, pulse rebalanced rate integrating gyros, any three of which are sufficient to conduct the science mission. After the loss of three gyros between April 1997 and April 1999 due to a known corrosion mechanism, NASA decided to split the third HST servicing mission into SM3A, accelerated to October 1999, and SM3B, scheduled for November 2001. SM3A was developed as a quick turnaround 'Launch on Need' mission to replace all six gyros. Loss of a fourth gyro in November 1999 caused HST to enter Zero Gyro Sunpoint (ZGSP) safemode, which uses sun sensors and magnetometers for attitude determination and momentum bias to maintain attitude stability during orbit night. Several instances of large attitude excursions during orbit night were observed, but ZGSP performance was adequate to provide power-positive sun pointing and to support low gain antenna communications. Body rates in ZGSP were estimated to exceed the nominal 0.1 deg/sec rendezvous limit, so rendezvous operations were restructured to utilize coarse, limited life, Retrieval Mode Gyros (RMGs) under Hardware Sunpoint (HWSP) safemode. Contingency procedures were developed to conduct the rendezvous in ZGSP in the event of RMGA or HWSP computer failure. Space Shuttle Mission STS-103 launched on December 19, 1999 after a series of weather and Shuttle-related delays. After successful rendezvous and grapple under HWSP/RMGA, the crew changed out all six gyros. Following deploy and systems checkout, HST returned to full science operations.

  5. Autonomy and Sensor Webs: The Evolution of Mission Operations

    NASA Technical Reports Server (NTRS)

    Sherwood, Rob

    2008-01-01

    Demonstration of these sensor web capabilities will enable fast responding science campaigns that combine spaceborne, airborne, and ground assets. Sensor webs will also require new operations paradigms. These sensor webs will be operated directly by scientists using science goals to control their instruments. We will explore these new operations architectures through a study of existing sensor web prototypes.

  6. Autonomy and Sensor Webs: The Evolution of Mission Operations

    NASA Technical Reports Server (NTRS)

    Sherwood, Rob

    2008-01-01

    Demonstration of these sensor web capabilities will enable fast responding science campaigns that combine spaceborne, airborne, and ground assets. Sensor webs will also require new operations paradigms. These sensor webs will be operated directly by scientists using science goals to control their instruments. We will explore these new operations architectures through a study of existing sensor web prototypes.

  7. Payload operations management of a planned European SL-Mission employing establishments of ESA and national agencies

    NASA Technical Reports Server (NTRS)

    Joensson, Rolf; Mueller, Karl L.

    1994-01-01

    Spacelab (SL)-missions with Payload Operations (P/L OPS) from Europe involve numerous space agencies, various ground infrastructure systems and national user organizations. An effective management structure must bring together different entities, facilities and people, but at the same time keep interfaces, costs and schedule under strict control. This paper outlines the management concept for P/L OPS of a planned European SL-mission. The proposal draws on the relevant experience in Europe, which was acquired via the ESA/NASA mission SL-1, by the execution of two German SL-missions and by the involvement in, or the support of, several NASA-missions.

  8. INFLIGHT (MISSION CONTROL CENTER [MCC]) - STS-1 - ELLINGTON AFB (EAFB), TX

    NASA Image and Video Library

    1981-04-13

    S81-32876 (13 April 1981) --- Brig. Gen. William T. Twinting studies the monitor at the Department of Defense (DOD) console in the mission operations control room (MOCR) at the Johnson Space Center?s Mission Control Center (MCC). He is deputy DOD manager for Space Shuttle Support Operations. Gen. Twinting and the other flight controllers seen in the background listen as astronaut John W. Young, STS-1 commander, describes the scenery of a downlink TV transmission. Photo credit: NASA

  9. Views of the mission control center during STS-9

    NASA Technical Reports Server (NTRS)

    1983-01-01

    A group of payloads operation flight controllers follows early progress of the Spacelab 1 mission. Standing behind the row of consoles are European Space Agency's (ESA) Director General Erik Quistgaard and NASA Headquarters Dr. Michael J. Wiskerchen (44919); After opening of Spacelab in the cargo bay of Columbia, these flight controllers in the payloads operations control center (POCC) at JSC discuss agenda of experiments. Quistgaard, center, ESA's Director General, talks to ESA's Mel Brooks, left, and NASA headquarters Wiskerchen (44920); Flight controllers on duty in the POCC at JSC monitor day 1 activity aboard the Spacelab module. Behind them is a banner representing the West German state of Baden-Wurtenbug from which payload specialist Ulf Merbold hails (44921).

  10. Integrated Attitude Control Strategy for the Asteroid Redirect Mission

    NASA Technical Reports Server (NTRS)

    Lopez, Pedro, Jr.; Price, Hoppy; San Martin, Miguel

    2014-01-01

    A deep-space mission has been proposed to redirect an asteroid to a distant retrograde orbit around the moon using a robotic vehicle, the Asteroid Redirect Vehicle (ARV). In this orbit, astronauts will rendezvous with the ARV using the Orion spacecraft. The integrated attitude control concept that Orion will use for approach and docking and for mated operations will be described. Details of the ARV's attitude control system and its associated constraints for redirecting the asteroid to the distant retrograde orbit around the moon will be provided. Once Orion is docked to the ARV, an overall description of the mated stack attitude during all phases of the mission will be presented using a coordinate system that was developed for this mission. Next, the thermal and power constraints of both the ARV and Orion will be discussed as well as how they are used to define the optimal integrated stack attitude. Lastly, the lighting and communications constraints necessary for the crew's extravehicular activity planned to retrieve samples from the asteroid will be examined. Similarly, the joint attitude control strategy that employs both the Orion and the ARV attitude control assets prior, during, and after each extravehicular activity will also be thoroughly discussed.

  11. Operations automation using the Link Monitor and Control Operator Assistant

    NASA Technical Reports Server (NTRS)

    Lee, Lorrine F.; Cooper, Lynne P.

    1993-01-01

    The Link Monitor and Control Operator Assistant (LMC OA) is a knowledge-based prototype system which uses AI techniques to provide semiautomated monitor and control functions to support operations of the Deep Space Network (DSN) 70-m antenna at the Goldstone Deep Space Communications Complex (DSCC). The manual and time-consuming process of configuring the 70-m antenna and its associated communications and processing equipment, known as precalibration, is an overhead activity; the time spent in precalibration is time which cannot be spent supporting actual mission operations. Therefore, the major goal of the LMC OA task is to demonstrate techniques that reduce precalibration time, decrease operations overhead, and increase the availability of this valuable and oversubscribed NASA resource. The LMC OA prototype was tested in a parallel, experimental mode at the Goldstone DSCC performing semiautomated precalibration using the actual operational equipment. This test demonstrated that a reduction of 40 percent in precalibration time can be achieved with the LMC OA prototype.

  12. Analytic investigation of the AEM-A/HCMM attitude control system performance. [Application Explorer Missions/Heat Capacity Mapping Mission

    NASA Technical Reports Server (NTRS)

    Lerner, G. M.; Huang, W.; Shuster, M. D.

    1977-01-01

    The Heat Capacity Mapping Mission (HCMM), scheduled for launch in 1978, will be three-axis stabilized relative to the earth in a 600-kilometer altitude, polar orbit. The autonomous attitude control system consists of three torquing coils and a momentum wheel driven in response to error signals computed from data received from an infrared horizon sensor and a magnetometer. This paper presents a simple model of the attitude dynamics and derives the equations that determine the stability of the system during both attitude acquisition (acquisition-mode) and mission operations (mission-mode). Modifications to the proposed mission-mode control laws which speed the system's response to transient attitude errors and reduce the steady-state attitude errors are suggested. Numerical simulations are performed to validate the results obtained with the simple model.

  13. The thermal control system for a network mission on Mars: The experience of the Netlander mission

    NASA Astrophysics Data System (ADS)

    Nadalini, R.; Bodendieck, F.

    2006-06-01

    The Netlander mission wants to establish an operating network of stations on the surface of Mars. Each one of four identical landers is equipped with science payloads dedicated to study the atmosphere and geosphere of Mars; operating together their objective is to investigate the Martian meteorology, ionosphere, ground and subsurface. Landing locations spread over two hemispheres and a mission duration of one Martian year, expose the surface modules and its sensitive electronics to a wide range of hostile conditions. Additional constraints come from the transporting spacecraft, where heat can be exchanged only across small interfaces. The purpose of the thermal control system is to maintain nevertheless the electronics and battery temperatures within a narrow band. Contrasting demands of reduced heat leaks and effective dump of surplus heat require new technologies and advanced design concepts to be satisfied under strict mass limits imposed. The paper describes the design, development and testing activities of a thermal control concept including high-performance insulation combined with an innovative loop heat pipe system. Extensive thermal analyses have been run and hardware has been built, qualified and tested. Results of the test are fairly positive, even in presence of some problematic issues. A post-fit numerical simulation has been initiated but further developments are needed.

  14. Determining Desirable Cursor Control Device Characteristics for NASA Exploration Missions

    NASA Technical Reports Server (NTRS)

    Sandor, Aniko; Holden, Kritina L.

    2007-01-01

    A test battery was developed for cursor control device evaluation: four tasks were taken from ISO 9241-9, and three from previous studies conducted at NASA. The tasks focused on basic movements such as pointing, clicking, and dragging. Four cursor control devices were evaluated with and without Extravehicular Activity (EVA) gloves to identify desirable cursor control device characteristics for NASA missions: 1) the Kensington Expert Mouse, 2) the Hulapoint mouse, 3) the Logitech Marble Mouse, and 4) the Honeywell trackball. Results showed that: 1) the test battery is an efficient tool for differentiating among input devices, 2) gloved operations were about 1 second slower and had at least 15% more errors; 3) devices used with gloves have to be larger, and should allow good hand positioning to counteract the lack of tactile feedback, 4) none of the devices, as designed, were ideal for operation with EVA gloves.

  15. MSFC Skylab Apollo Telescope Mount thermal control system mission evaluation

    NASA Technical Reports Server (NTRS)

    Hueter, U.

    1974-01-01

    The Skylab Saturn Workshop Assembly was designed to expand the knowledge of manned earth orbital operations and accomplish a multitude of scientific experiments. The Apollo Telescope Mount (ATM), a module of the Skylab Saturn Workshop Assembly, was the first manned solar observatory to successfully observe, monitor, and record the structure and behavior of the sun outside the earth's atmosphere. The ATM contained eight solar telescopes that recorded solar phenomena in X-ray, ultraviolet, white light, and hydrogen alpha regions of the electromagnetic spectrum. In addition, the ATM contained the Saturn Workshop Assembly's pointing and attitude control system, a data and communication system, and a solar array/rechargeable battery power system. This document presents the overall ATM thermal design philosophy, premission and mission support activity, and the mission thermal evaluation. Emphasis is placed on premission planning and orbital performance with particular attention on problems encountered during the mission. ATM thermal performance was satisfactory throughout the mission. Although several anomalies occurred, no failure was directly attributable to a deficiency in the thermal design.

  16. Operating and Managing a Backup Control Center

    NASA Technical Reports Server (NTRS)

    Marsh, Angela L.; Pirani, Joseph L.; Bornas, Nicholas

    2010-01-01

    Due to the criticality of continuous mission operations, some control centers must plan for alternate locations in the event an emergency shuts down the primary control center. Johnson Space Center (JSC) in Houston, Texas is the Mission Control Center (MCC) for the International Space Station (ISS). Due to Houston s proximity to the Gulf of Mexico, JSC is prone to threats from hurricanes which could cause flooding, wind damage, and electrical outages to the buildings supporting the MCC. Marshall Space Flight Center (MSFC) has the capability to be the Backup Control Center for the ISS if the situation is needed. While the MSFC Huntsville Operations Support Center (HOSC) does house the BCC, the prime customer and operator of the ISS is still the JSC flight operations team. To satisfy the customer and maintain continuous mission operations, the BCC has critical infrastructure that hosts ISS ground systems and flight operations equipment that mirrors the prime mission control facility. However, a complete duplicate of Mission Control Center in another remote location is very expensive to recreate. The HOSC has infrastructure and services that MCC utilized for its backup control center to reduce the costs of a somewhat redundant service. While labor talents are equivalent, experiences are not. Certain operations are maintained in a redundant mode, while others are simply maintained as single string with adequate sparing levels of equipment. Personnel at the BCC facility must be trained and certified to an adequate level on primary MCC systems. Negotiations with the customer were done to match requirements with existing capabilities, and to prioritize resources for appropriate level of service. Because some of these systems are shared, an activation of the backup control center will cause a suspension of scheduled HOSC activities that may share resources needed by the BCC. For example, the MCC is monitoring a hurricane in the Gulf of Mexico. As the threat to MCC

  17. Disease control operations

    USGS Publications Warehouse

    Friend, Milton; Franson, J. Christian

    1987-01-01

    Individual disease outbreaks have killed many thousands of animals on numerous occasions. Tens of thousands of migratory birds have died in single die-offs with as many as 1,000 birds succumbing in 1 day. In mammals, individual disease outbreaks have killed hundreds to thousands of animals with, for example, hemorrhagic disease in white-tailed deer, distemper in raccoon, Errington's disease in muskrat, and sylvatic plague in wild rodents. The ability to successfully combat such explosive situations is highly dependent n the readiness of field personnel to deal with them. Because many disease agents can spread though wildlife populations very fast, advance preparation is essential in preventing infected animals from spreading disease to additional species and locations. Carefully though-out disease contingency plans should be developed as practical working documents for field personnel and updated as necessary. Such well-designed plans can prove invaluable in minimizing wildlife losses and costs associated with disease control activities. Although requirements for disease control operations vary and must be tailored to each situation, all disease contingency planning involved general concepts and basic biological information. This chapter, intended as a practical guide, identifies the major activities and needs of disease control operations, and relates them to disease contingency planning.

  18. Commonality of flight control systems for support of European telecommunications missions

    NASA Technical Reports Server (NTRS)

    Debatin, Kurt

    1993-01-01

    This paper is concerned with the presentation of mission-independent software systems that provide a common software platform to ground data systems for mission operations. The objectives of such common software platforms are to reduce the cost of the development of mission-dedicated software systems and to increase the level of reliability of the ground data systems for mission operations. In accordance with this objective, the Multi-Satellite Support System (MSSS) was developed at the European Space Operations Center (ESOC). Between 1975 and 1992, the MSSS provided support to 16 European Space Agency (ESA) missions, among them very demanding science missions such as GEOS, EXOSAT, and Giotto. The successful support of these missions proved the validity of the MSSS concept with its extended mission-independent platform. This paper describes the MSSS concept and focuses on the wide use of MSSS as a flight control system for geosynchronous telecommunications satellites. Reference is made to more than 15 telecommunications missions that are operated from Western Europe using flight control systems with an underlying MSSS concept, demonstrating the benefits of a commonly used software platform. Finally, the paper outlines the design of the new generation of flight control systems, which is being developed at ESOC for this decade, following a period of more than 15 years of MSSS support.

  19. The ESA Scientific Exploitation of Operational Missions element

    NASA Astrophysics Data System (ADS)

    Desnos, Yves-Louis; Benveniste, Jerome; Delwart, Steven; Engdahl, Marcus; Regner, Peter; Zehner, Claus; Mathieu, Pierre Philippe; Arino, Olivier; Bojkov, Bojan; Ferran, Gaston; Donlon, Craig; Kern, Michael; Scipal, Klaus

    2013-04-01

    The prime objective of the ESA Scientific Exploitation of Operational Missions (SEOM) programme element is to federate, support and expand the large international research community that the ERS, ENVISAT and the Envelope programmes have built up over the last 20 years. It aims to further strengthen the international leadership of European Earth Observation research community by enabling them to extensively exploit observations from future European operational EO missions. SEOM will enable the science community to address many new avenues of scientific research that will be opened by free and open access to data from operational EO missions. As a preparation for the SEOM element a series of international science users consultation has been organized by ESA in 2012 covering Sentinel 1 (FRINGE /SEASAR ), Sentinel 2 ( S2 symposium), Sentinel 3 (COAST-ALT workshop , 20 Years Progress in Radar Altimetry, Sentinel 3 OLCI/SLSTR 2012 workshop) and Sentinel 4-5 (Atmospheric Science Confrence). The science users recommendations have been gathered and form the basis for the work plan 2013 for the SEOM element. The SEOM element is organized along the following action lines: 1. Developing, validating and maintaining open-source, multi-mission, scientific software toolboxes capable to handle the Sentinels data products 2. Stimulating the development and validation of advanced EO methods and observation strategies in particular the new TOpS mode on Sentinel 1, the new band settings on Sentinel 2, the new geometry/bands of Sentinel 3 OLCI ,SLSTR intruments and the advanced delay-doppler (SAR) altimeter exploitation. 3. Continuing to federate, support and expand the multi-disciplinary expert EO research communities by organizing thematic workshops and ensuring high-quality scientific publications linked to these research domains. Promoting widespread scientific use of data. 4. Training the next generation of European EO scientists on the scientific exploitation of Sentinel s data

  20. Impingement effect of service module reaction control system engine plumes. Results of service module reaction control system plume model force field application to an inflight Skylab mission proximity operation situation with the inflight Skylab response

    NASA Technical Reports Server (NTRS)

    Lobb, J. D., Jr.

    1978-01-01

    Plume impingement effects of the service module reaction control system thruster firings were studied to determine if previous flight experience would support the current plume impingement model for the orbiter reaction control system engines. The orbiter reaction control system is used for rotational and translational maneuvers such as those required during rendezvous, braking, docking, and station keeping. Therefore, an understanding of the characteristics and effects of the plume force fields generated by the reaction control system thruster firings were examined to develop the procedures for orbiter/payload proximity operations.

  1. Environmental Control and Life Support Systems for Mars Missions — Issues and Concerns for Planetary Protection

    NASA Astrophysics Data System (ADS)

    Barta, D. J.; Anderson, M. S.

    2015-03-01

    Planetary protection (PP) represents additional requirements for Environmental Control & Life Support (ECLSS). PP guidelines will affect operations, processes, and functions that can take place during future human planetary exploration missions.

  2. Operating the Dual-Orbtier GRAIL Mission to Measure the Moon's Gravity

    NASA Technical Reports Server (NTRS)

    Beerer, Joseph G.; Havens, Glen G.

    2012-01-01

    The GRAIL mission is on track to satisfy all prime mission requirements. The performance of the orbiters and payload has been exceptional. Detailed pre-launch operations planning and validation have paid off. Prime mission timeline has been conducted almost exactly as laid out in the mission plan. Flight experience in the prime mission puts the flight team in a good position for completing the challenges of the extended mission where the science payoff is even greater

  3. The ESA Scientific Exploitation of Operational Missions element

    NASA Astrophysics Data System (ADS)

    Desnos, Yves-Louis; Regner, Peter; Delwart, Steven; Benveniste, Jerome; Engdahl, Marcus; Zehner, Claus; Mathieu, Pierre-Philippe; Bojkov, Bojan; Gascon, Ferran; Donlon, Craig; Davidson, Malcolm; Goryl, Philippe; Pinnock, Simon

    2015-04-01

    SEOM is a program element within the fourth period (2013-2017) of ESA's Earth Observation Envelope Programme (http://seom.esa.int/). The prime objective is to federate, support and expand the international research community that the ERS,ENVISAT and the Envelope programmes have built up over the last 25 years. It aims to further strengthen the leadership of the European Earth Observation research community by enabling them to extensively exploit future European operational EO missions. SEOM will enable the science community to address new scientific research that are opened by free and open access to data from operational EO missions. Based on community-wide recommendations for actions on key research issues, gathered through a series of international thematic workshops and scientific user consultation meetings, a work plan has been established and is approved every year by ESA Members States. The 2015 SEOM work plan is covering the organisation of three Science users consultation workshops for Sentinel1/3/5P , the launch of new R&D studies for scientific exploitation of the Sentinels, the development of open-source multi-mission scientific toolboxes, the organisation of advanced international training courses, summer schools and educational materials, as well as activities for promoting the scientific use of EO data. The first SEOM projects have been tendered since 2013 including the development of Sentinel toolboxes, advanced INSAR algorithms for Sentinel-1 TOPS data exploitation, Improved Atmospheric Spectroscopic data-base (IAS), as well as grouped studies for Sentinel-1, -2, and -3 land and ocean applications and studies for exploiting the synergy between the Sentinels. The status and first results from these SEOM projects will be presented and an outlook for upcoming SEOM studies will be given.

  4. Artificial intelligence for multi-mission planetary operations

    NASA Technical Reports Server (NTRS)

    Atkinson, David J.; Lawson, Denise L.; James, Mark L.

    1990-01-01

    A brief introduction is given to an automated system called the Spacecraft Health Automated Reasoning Prototype (SHARP). SHARP is designed to demonstrate automated health and status analysis for multi-mission spacecraft and ground data systems operations. The SHARP system combines conventional computer science methodologies with artificial intelligence techniques to produce an effective method for detecting and analyzing potential spacecraft and ground systems problems. The system performs real-time analysis of spacecraft and other related telemetry, and is also capable of examining data in historical context. Telecommunications link analysis of the Voyager II spacecraft is the initial focus for evaluation of the prototype in a real-time operations setting during the Voyager spacecraft encounter with Neptune in August, 1989. The preliminary results of the SHARP project and plans for future application of the technology are discussed.

  5. The Landsat Data Continuity Mission Operational Land Imager (OLI) Sensor

    NASA Technical Reports Server (NTRS)

    Markham, Brian L.; Knight, Edward J.; Canova, Brent; Donley, Eric; Kvaran, Geri; Lee, Kenton; Barsi, Julia A.; Pedelty, Jeffrey A.; Dabney, Philip W.; Irons, James R.

    2012-01-01

    The Landsat Data Continuity Mission (LDCM) is being developed by NASA and USGS and is currently planned for launch in January 2013 [1]. Once on-orbit and checked out, it will be operated by USGS and officially named Landsat-8. Two sensors will be on LDCM: the Operational Land Imager (OLI), which has been built and delivered by Ball Aerospace & Technology Corp (BATC) and the Thermal Infrared Sensor (TIRS)[2], currently being built and tested at Goddard Space Flight Center (GSFC) with a planned delivery of Winter 2012. The OLI covers the Visible, Near-IR (NIR) and Short-Wave Infrared (SWIR) parts of the spectrum; TIRS covers the Thermal Infrared (TIR). This paper discusses only the OLI instrument and its pre-launch characterization; a companion paper covers TIRS.

  6. Sun Incidence Angle Analysis of KOMPSAT-2 Payload during Normal Mission Operations

    NASA Astrophysics Data System (ADS)

    Kim, Eung-Hyun; Yong, Ki-Lyuk; Lee, Sang-Ryool

    2000-12-01

    KOMPSAT-2 will carry MSC (Multi-Spectral Camera) which provides 1m resolution panchromatic and 4m resolution multi-spectral images at the altitude of 685km sun-synchronous mission orbit. The mission operation of KOMSPAT-2 is to provide the earth observation using MSC with nadir pointing. KOMPSAT-2 will also have the capability of roll/pitch tilt maneuver using reaction wheel of satellite as required. In order to protect MSC from thermal distortion as well as direct sunlight, MSC shall be operated within the constraint of sun incidence angle. It is expected that the sunlight will not violate the constraint of sun incidence angle for normal mission operations without roll/pitch maneuver. However, during roll/pitch tilt operations, optical module of MSC may be damaged by the sunlight. This study analyzed sun incidence angle of payload using KOMPSAT-2 AOCS (Attitude and Orbit Control Subsystem) Design and Performance Analysis Software for KOMPSAT-2 normal mission operations.

  7. Operational thermal control of Cassini Titan flybys

    NASA Technical Reports Server (NTRS)

    Millard, J. M.; Luan, T. W.

    2003-01-01

    The Cassini spacecraft will fly by Saturn's largest moon, Titan, forty-five times during its science tour. Twenty-five of the flybys will have a relatively low closest approach target altitude in Titan's atmosphere and are of thermal concern. The Thermal Devices Team on the Cassini Project in Mission Operations at the Jet Propulsion Laboratory has designed an operational thermal control strategy for these flybys. The challenge was to provide flyby operational thermal control that enabled science and remained within design limitations and Project constraints.

  8. Toward an automated signature recognition toolkit for mission operations

    NASA Technical Reports Server (NTRS)

    Cleghorn, T.; Laird, P; Perrine, L.; Culbert, C.; Macha, M.; Saul, R.; Hammen, D.; Moebes, T.; Shelton, R.

    1994-01-01

    Signature recognition is the problem of identifying an event or events from its time series. The generic problem has numerous applications to science and engineering. At NASA's Johnson Space Center, for example, mission control personnel, using electronic displays and strip chart recorders, monitor telemetry data from three-phase electrical buses on the Space Shuttle and maintain records of device activation and deactivation. Since few electrical devices have sensors to indicate their actual status, changes of state are inferred from characteristic current and voltage fluctuations. Controllers recognize these events both by examining the waveform signatures and by listening to audio channels between ground and crew. Recently the authors have developed a prototype system that identifies major electrical events from the telemetry and displays them on a workstation. Eventually the system will be able to identify accurately the signatures of over fifty distinct events in real time, while contending with noise, intermittent loss of signal, overlapping events, and other complications. This system is just one of many possible signature recognition applications in Mission Control. While much of the technology underlying these applications is the same, each application has unique data characteristics, and every control position has its own interface and performance requirements. There is a need, therefore, for CASE tools that can reduce the time to implement a running signature recognition application from months to weeks or days. This paper describes our work to date and our future plans.

  9. Operating the Dual-Orbiter GRAIL Mission to Measure the Moon's Gravity

    NASA Technical Reports Server (NTRS)

    Beerer, Joseph G.; Havens, Glen G.

    2012-01-01

    NASA's mission to measure the Moon's gravity and determine the interior structure, from crust to core, has almost completed its 3-month science data collection phase. The twin orbiters of the Gravity Recovery and Interior Laboratory (GRAIL) mission were launched from Florida on September 10, 2011, on a Delta-II launch vehicle. After traveling for nearly four months on a low energy trajectory to the Moon, they were inserted into lunar orbit on New Year's Eve and New Year's Day. In January 2012 a series of circularization maneuvers brought the orbiters into co-planar near-circular polar orbits. In February a distant (75- km) rendezvous was achieved and the science instruments were turned on. A dual- frequency (Ka and S-band) inter-orbiter radio link provides a precise orbiter-to-orbiter range measurement that enables the gravity field estimation. NASA's Jet Propulsion Laboratory in Pasadena, CA, manages the GRAIL project. Mission management, mission planning and sequencing, and navigation are conducted at JPL. Lockheed Martin, the flight system manufacturer, operates the orbiters from their control center in Denver, Colorado. The orbiters together have performed 28 propulsive maneuvers to reach and maintain the science phase configuration. Execution of these maneuvers, as well as the payload checkout and calibration activities, has gone smoothly due to extensive pre-launch operations planning and testing. The key to the operations success has been detailed timelines for product interchange between the operations teams and proven procedures from previous JPL/LM planetary missions. Once in science phase, GRAIL benefitted from the payload operational heritage of the GRACE mission that measures the Earth's gravity.

  10. Operating the Dual-Orbiter GRAIL Mission to Measure the Moon's Gravity

    NASA Technical Reports Server (NTRS)

    Beerer, Joseph G.; Havens, Glen G.

    2012-01-01

    NASA's mission to measure the Moon's gravity and determine the interior structure, from crust to core, has almost completed its 3-month science data collection phase. The twin orbiters of the Gravity Recovery and Interior Laboratory (GRAIL) mission were launched from Florida on September 10, 2011, on a Delta-II launch vehicle. After traveling for nearly four months on a low energy trajectory to the Moon, they were inserted into lunar orbit on New Year's Eve and New Year's Day. In January 2012 a series of circularization maneuvers brought the orbiters into co-planar near-circular polar orbits. In February a distant (75- km) rendezvous was achieved and the science instruments were turned on. A dual- frequency (Ka and S-band) inter-orbiter radio link provides a precise orbiter-to-orbiter range measurement that enables the gravity field estimation. NASA's Jet Propulsion Laboratory in Pasadena, CA, manages the GRAIL project. Mission management, mission planning and sequencing, and navigation are conducted at JPL. Lockheed Martin, the flight system manufacturer, operates the orbiters from their control center in Denver, Colorado. The orbiters together have performed 28 propulsive maneuvers to reach and maintain the science phase configuration. Execution of these maneuvers, as well as the payload checkout and calibration activities, has gone smoothly due to extensive pre-launch operations planning and testing. The key to the operations success has been detailed timelines for product interchange between the operations teams and proven procedures from previous JPL/LM planetary missions. Once in science phase, GRAIL benefitted from the payload operational heritage of the GRACE mission that measures the Earth's gravity.

  11. Environmental Control Systems for Exploration Missions One and Two

    NASA Technical Reports Server (NTRS)

    Falcone, Mark A.

    2017-01-01

    In preparing for Exploration Missions One and Two (EM-1 & EM-2), the Ground Systems Development and Operations Program has significant updates to be made to nearly all facilities. This is all being done to accommodate the Space Launch System, which will be the world’s largest rocket in history upon fruition. Facilitating the launch of such a rocket requires an updated Vehicle Assembly Building, an upgraded Launchpad, Payload Processing Facility, and more. In this project, Environmental Control Systems across several facilities were involved, though there is a focus around the Mobile Launcher and Launchpad. Parts were ordered, analysis models were updated, design drawings were updated, and more.

  12. Peer-to-Peer Planning for Space Mission Control

    NASA Technical Reports Server (NTRS)

    Barreiro, Javier; Jones, Grailing, Jr.; Schaffer, Steve

    2009-01-01

    Planning and scheduling for space operations entails the development of applications that embed intimate domain knowledge of distinct areas of mission control, while allowing for significant collaboration among them. The separation is useful because of differences in the planning problem, solution methods, and frequencies of replanning that arise in the different disciplines. For example, planning the activities of human spaceflight crews requires some reasoning about all spacecraft resources at timescales of minutes or seconds, and is subject to considerable volatility. Detailed power planning requires managing the complex interplay of power consumption and production, involves very different classes of constraints and preferences, but once plans are generated they are relatively stable.

  13. Programmer's manual for the Mission Analysis Evaluation and Space Trajectory Operations program (MAESTRO)

    NASA Technical Reports Server (NTRS)

    Lutzky, D.; Bjorkman, W. S.

    1973-01-01

    The Mission Analysis Evaluation and Space Trajectory Operations program known as MAESTRO is described. MAESTRO is an all FORTRAN, block style, computer program designed to perform various mission control tasks. This manual is a guide to MAESTRO, providing individuals the capability of modifying the program to suit their needs. Descriptions are presented of each of the subroutines descriptions consist of input/output description, theory, subroutine description, and a flow chart where applicable. The programmer's manual also contains a detailed description of the common blocks, a subroutine cross reference map, and a general description of the program structure.

  14. The ESA JUICE mission: the Science and the Science Operations

    NASA Astrophysics Data System (ADS)

    Lorente, Rosario; Altobelli, Nicolas; Vallat, Claire; Munoz, Claudio; Andres, Rafael; Cardesin, Alejandro; Witasse, Olivier; Erd, Christian

    2017-04-01

    sensing capabilities via energetic neutrals, a magnetometer (J-MAG) and a radio and plasma wave instrument (RPWI), including electric fields sensors and a Langmuir probe. An experiment (PRIDE) using ground-based Very Long Baseline Interferometry (VLBI) will support precise determination of the spacecraft state vector with the focus at improving the ephemeris of the Jovian system. The current baseline assumes a launch in May 2022. Following an interplanetary cruise of 7.6 years, the Jupiter orbit insertion will take place in October 2029. The Jupiter tour will consists of 50 orbits around the giant planet, and will include two flybys of Europa at 400 km altitude, eleven flybys of Ganymede, and thirteen flybys of Callisto, as close as 200 km altitude. The last part of the mission will be the orbital phase around Ganymede, for about 10 months, where the spacecraft will be placed into a series of elliptical and circular orbits, the latest one at 500 km altitude. The end of mission is currently planned as an impact on Ganymede in June 2033. The ESA Science Operation Centre (SOC) is in charge of implementing the science operations of the JUICE mission. The SOC aims at supporting the Science Working Team (SWT) and the Science Working Groups (WGs) performing studies of science operation feasibility and coverage analysis during the mission development phase until launch, high level science planning during the cruise phase, and routine consolidation of instrument pointing and commanding timeline during the nominal science phase. This presentation will provide the latest information on the status of the project, and on the designed spacecraft trajectory in the Jovian system. It will focus on the science operational scenario of the two Europa flybys of the mission, and on the overall science return. References: [1] JUICE Definition Study Report, Reference ESA/SRE(2014)1,2014. http://sci.esa.int/juice/54994-juice-definition-study-report/ [2] Grasset, O., et al., JUpiter ICy moons

  15. Preliminary Attitude Control Studies for the ASTER Mission

    NASA Astrophysics Data System (ADS)

    Victorino Sarli, Bruno; Luís da Silva, André; Paglione, Pedro

    2013-10-01

    This work discusses an attitude control study for the ASTER mission, the first Brazilian mission to the deep space. The study is part of a larger scenario that is the development of optimal trajectories to navigate in the 2001 SN263 asteroid system, together with the generation of orbit and attitude controllers for autonomous operation. The spacecraft attitude is defined from the orientation of the body reference system to the Local Vertical Local Horizontal (LVLH) of a circular orbit around the Alpha asteroid. The rotational equations of motion involve the dynamic equations, where the three angular speeds are generated from a set of three reaction wheels and the gravitational torque. The rotational kinematics is represented in the Euler angles format. The controller is developed via the linear quadratic regulator approach with output feedback. It involves the generation of a stability augmentation (SAS) loop and a tracking outer loop, with a compensator of desired structure. It was chosen the feedback of the p, q and r angular speeds in the SAS, one for each reaction wheel. In the outer loop, it was chosen a proportional integral compensator. The parameters are tuned using a numerical minimization that represents a linear quadratic cost, with weightings in the tracking error and controls. Simulations are performed with the nonlinear model. For small angle manoeuvres, the linear results with reaction wheels or thrusters are reasonable, but, for larger manoeuvres, nonlinear control techniques shall be applied, for example, the sliding mode control.

  16. Mission Control Center (MCC) - Apollo 13 - Fourth (4th) Television Signal - MSC

    NASA Image and Video Library

    1970-04-13

    S70-35139 (13 April 1970) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) at Manned Spacecraft Center (MSC), during the fourth television transmission from the Apollo 13 mission in space. Eugene F. Kranz (foreground, back to camera), one of four Apollo 13 flight directors, views the large screen at front of MOCR, astronaut Fred W. Haise Jr., lunar module pilot, is seen on the screen. The fourth TV transmission from the Apollo 13 mission was on the evening of April 13, 1970.

  17. Personnel in Mission Control examine replica of spider habitat from Skylab 3

    NASA Technical Reports Server (NTRS)

    1973-01-01

    Flight Director Neil B. Hutchinson, left, and Astronaut Bruce McCandless II hold up a glass enclosure - home for the spider Arachne, which is the same species as the two spiders carried on the Skylab 3 mission. The real spider is the one barely visible at the upper right corner of the square; the larger one is a projected image on the rear-screen-projected map in the front of the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC). McCandless served as backup pilot for the first manned Skylab mission and was a spacecraft-communicater (CAPCOM) for the second crew.

  18. Personnel in Mission Control examine replica of spider habitat from Skylab 3

    NASA Technical Reports Server (NTRS)

    1973-01-01

    Flight Director Neil B. Hutchinson, left, and Astronaut Bruce McCandless II hold up a glass enclosure - home for the spider Arachne, which is the same species as the two spiders carried on the Skylab 3 mission. The real spider is the one barely visible at the upper right corner of the square; the larger one is a projected image on the rear-screen-projected map in the front of the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC). McCandless served as backup pilot for the first manned Skylab mission and was a spacecraft-communicater (CAPCOM) for the second crew.

  19. Operational Experience with Long Duration Wildfire Mapping: UAS Missions Over the Western United States

    NASA Technical Reports Server (NTRS)

    Hall, Philip; Cobleigh, Brent; Buoni, Greg; Howell, Kathleen

    2008-01-01

    The National Aeronautics and Space Administration, United States Forest Service, and National Interagency Fire Center have developed a partnership to develop and demonstrate technology to improve airborne wildfire imaging and data dissemination. In the summer of 2007, a multi-spectral infrared scanner was integrated into NASA's Ikhana Unmanned Aircraft System (UAS) (a General Atomics Predator-B) and launched on four long duration wildfire mapping demonstration missions covering eight western states. Extensive safety analysis, contingency planning, and mission coordination were key to securing an FAA certificate of authorization (COA) to operate in the national airspace. Infrared images were autonomously geo-rectified, transmitted to the ground station by satellite communications, and networked to fire incident commanders within 15 minutes of acquisition. Close coordination with air traffic control ensured a safe operation, and allowed real-time redirection around inclement weather and other minor changes to the flight plan. All objectives of the mission demonstrations were achieved. In late October, wind-driven wildfires erupted in five southern California counties. State and national emergency operations agencies requested Ikhana to help assess and manage the wildfires. Four additional missions were launched over a 5-day period, with near realtime images delivered to multiple emergency operations centers and fire incident commands managing 10 fires.

  20. Mission Performance of the GLAS Thermal Control System - 7 Years In Orbit

    NASA Technical Reports Server (NTRS)

    Grob, Eric W.

    2010-01-01

    ICESat (Ice, Cloud and land Elevation Satellite) was launched in 2003 carrying a single science instrument - the Geoscience Laser Altimeter System (GLAS). Its primary mission was to measure polar ice thickness. The GLAS thermal control architecture utilized propylene Loop Heat Pipe (LHP) technology to provide selectable and stable temperature control for the lasers and other electronics over a widely varying mission thermal environment. To minimize expected degradation of the radiators, Optical Solar Reflectors (OSRs) were used for both LHP radiators to minimize degradation caused by UV exposure in the various spacecraft attitudes necessary throughout the mission. Developed as a Class C mission, with selective redundancy, the thermal architecture was single st ring, except for temperature sensors used for heater control during normal operations. Although originally planned for continuous laser operations over the nominal three year science mission, laser anomalies limited operations to discrete measurement campaigns repeated throughout the year. For trending of the science data, these periods were selected to occur at approximately the same time each year, which resulted in operations during similar attitudes and beta angles. Despite the laser life issues, the LHPs have operated nearly continuously over this time, being non-operational for only brief periods. Using mission telemetry, this paper looks at the performance of the thermal subsystem during these periods and provides an assessment of radiator degradation over the mission lifetime.

  1. Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

    NASA Technical Reports Server (NTRS)

    Johnson, Teresa A.

    2006-01-01

    Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

  2. Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

    NASA Technical Reports Server (NTRS)

    Johnson, Teresa A.

    2006-01-01

    Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

  3. Implementation and Test of the Automatic Flight Dynamics Operations for Geostationary Satellite Mission

    NASA Astrophysics Data System (ADS)

    Park, Sangwook; Lee, Young-Ran; Hwang, Yoola; Javier Santiago Noguero Galilea

    2009-12-01

    This paper describes the Flight Dynamics Automation (FDA) system for COMS Flight Dynamics System (FDS) and its test result in terms of the performance of the automation jobs. FDA controls the flight dynamics functions such as orbit determination, orbit prediction, event prediction, and fuel accounting. The designed FDA is independent from the specific characteristics which are defined by spacecraft manufacturer or specific satellite missions. Therefore, FDA could easily links its autonomous job control functions to any satellite mission control system with some interface modification. By adding autonomous system along with flight dynamics system, it decreases the operator’s tedious and repeated jobs but increase the usability and reliability of the system. Therefore, FDA is used to improve the completeness of whole mission control system’s quality. The FDA is applied to the real flight dynamics system of a geostationary satellite, COMS and the experimental test is performed. The experimental result shows the stability and reliability of the mission control operations through the automatic job control.

  4. LaserCom in UAS missions: benefits and operational aspects

    NASA Astrophysics Data System (ADS)

    Griethe, Wolfgang; Heine, Frank; Begg, Lester L.; Du, Detao

    2013-05-01

    Free Space Optical Communications (FSOC) is progressing continuously. With the successful in-orbit verification of a Laser Communication Terminal (LCT), the coherent homodyne BPSK scheme advanced to a standard for Free-Space Optical Communication (FSOC) which now prevails more and more. The LCT is located not only on satellites in Low Earth Orbit (LEO), with spacecrafts like ALPHASAT-TDP and the European Data Relay Satellite (EDRS) the LCT will also exist in Geosynchronous Orbit (GEO) in the near future. In other words, the LCT has reached its practical application. With existence of such space assets the time has come for other utilizations beyond that of establishing optical Inter-Satellite Links (ISL). Aeronautical applications, as for instance High Altitude Long Endurance (HALE) or Medium Altitude Long Endurance (MALE) Unmanned Aerial Systems (UAS) have to be addressed. Driving factors and advantages of FSOC in HALE/MALE UAS missions are highlighted. Numerous practice-related issues are described concerning the space segment, the aeronautical segment as well as the ground segment. The advantages for UAS missions are described resulting from the utilization of FSOC exclusively for wideband transmission of sensor data whereas vehicle Command and Control can be maintained as before via RF communication. Moreover, the paper discusses FSOC as enabler for the integration of air and space-based wideband Intelligence, Surveillance and Reconnaissance (ISR) systems into existent military command and control systems.

  5. Orbital Express Mission Operations Planning and Resource Management using ASPEN

    NASA Technical Reports Server (NTRS)

    Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Danny

    2008-01-01

    The Orbital Express satellite servicing demonstrator program is a DARPA program aimed at developing "a safe and cost-effective approach to autonomously service satellites in orbit". The system consists of: a) the Autonomous Space Transport Robotic Operations (ASTRO) vehicle, under development by Boeing Integrated Defense Systems, and b) a prototype modular next-generation serviceable satellite, NEXTSat, being developed by Ball Aerospace. Flexibility of ASPEN: a) Accommodate changes to procedures; b) Accommodate changes to daily losses and gains; c) Responsive re-planning; and d) Critical to success of mission planning Auto-Generation of activity models: a) Created plans quickly; b) Repetition/Re-use of models each day; and c) Guarantees the AML syntax. One SRP per day vs. Tactical team

  6. A psychophysiological assessment of operator workload during simulated flight missions

    NASA Technical Reports Server (NTRS)

    Kramer, Arthur F.; Sirevaag, Erik J.; Braune, Rolf

    1987-01-01

    The applicability of the dual-task event-related (brain) potential (ERP) paradigm to the assessment of an operator's mental workload and residual capacity in a complex situation of a flight mission was demonstrated using ERP measurements and subjective workload ratings of student pilots flying a fixed-based single-engine simulator. Data were collected during two separate 45-min flights differing in difficulty; flight demands were examined by dividing each flight into four segments: takeoff, straight and level flight, holding patterns, and landings. The P300 ERP component in particular was found to discriminate among the levels of task difficulty in a systematic manner, decreasing in amplitude with an increase in task demands. The P300 amplitude is shown to be negatively correlated with deviations from command headings across the four flight segments.

  7. A psychophysiological assessment of operator workload during simulated flight missions

    NASA Technical Reports Server (NTRS)

    Kramer, Arthur F.; Sirevaag, Erik J.; Braune, Rolf

    1987-01-01

    The applicability of the dual-task event-related (brain) potential (ERP) paradigm to the assessment of an operator's mental workload and residual capacity in a complex situation of a flight mission was demonstrated using ERP measurements and subjective workload ratings of student pilots flying a fixed-based single-engine simulator. Data were collected during two separate 45-min flights differing in difficulty; flight demands were examined by dividing each flight into four segments: takeoff, straight and level flight, holding patterns, and landings. The P300 ERP component in particular was found to discriminate among the levels of task difficulty in a systematic manner, decreasing in amplitude with an increase in task demands. The P300 amplitude is shown to be negatively correlated with deviations from command headings across the four flight segments.

  8. Operational marine products from Copernicus Sentinel-3 mission

    NASA Astrophysics Data System (ADS)

    Tomazic, Igor; Montagner, Francois; O'Carroll, Anne; Kwiatkowska, Ewa; Scharroo, Remko; Nogueira Loddo, Carolina; Martin-Puig, Cristina; Bonekamp, Hans; Lucas, Bruno; Dinardo, Salvatore; Dash, Prasanjit; Taberner, Malcolm; Coto Cabaleiro, Eva; Santacesaria, Vincenzo; Wilson, Hilary

    2017-04-01

    The first Copernicus Sentinel-3 satellite, Sentinel-3A, was launched in early 2016, with the mission to provide a consistent, long-term collection of marine and land data for operational analysis, forecasting and environmental and climate monitoring. The marine centre is part of the Sentinel-3 Payload Data Ground Segment, located at EUMETSAT. This centre together with the existing EUMETSAT facilities provides a routine centralised service for operational meteorology, oceanography, and other Sentinel-3 marine users as part of the European Commission's Copernicus programme. The EUMETSAT marine centre delivers operational Sea Surface Temperature, Ocean Colour and Sea Surface Topography data products based on the measurements from the Sea and Land Surface Temperature Radiometer (SLSTR), Ocean and Land Colour Instrument (OLCI) and Synthetic Aperture Radar Altimeter (SRAL), respectively, all aboard Sentinel-3. All products have been developed together with ESA and industry partners and EUMETSAT is responsible for the production, distribution, and future evolution of Level-2 marine products. We will give an overview of the scientific characteristics and algorithms of all marine Level-2 products, as well as instrument calibration and product validation results based on on-going Sentinel-3 Cal/Val activities. Information will be also provided about the current status of the product dissemination and the future evolutions that are envisaged. Also, we will provide information how to access Sentinel-3 data from EUMETSAT and where to look for further information.

  9. Hydrazine Operations at Near-Freezing Temperatures During the Ulysses Extended Mission

    NASA Astrophysics Data System (ADS)

    McGarry, A.; Castro, F.; Hodges, M.

    2004-10-01

    The Ulysses mission was recently extended for the third time to March 2008. This extension will require Ulysses to operate far beyond its intended design lifetime at very low power and thermal margins. As a result, it will enter the coldest part of its orbit, as it returns from aphelion at Jupiter distance, with parts of the Reaction Control System (RCS) pipework containing the hydrazine propellant already at near-freezing temperatures. With limited telemetry, no simulator and only a thermal model optimized for the prime mission case, the operations team faces many challenges to avoid freezing of propellant in the RCS, and the hazardous consequences which would result. This paper gives an overview and operational history of the Ulysses monopropellant pressurized hydrazine RCS, describes techniques for detecting possible indications of hydrazine freezing, and potential contingency strategies should partial freezing occur.

  10. Operational exploitation of the Sentinel-1 mission: implications for geoscience

    NASA Astrophysics Data System (ADS)

    Larsen, Y.; Marinkovic, P.; Dehls, J. F.; Hooper, A. J.; Wright, T. J.; Perski, Z.

    2016-12-01

    With the successful launch of the Copernicus Sentinel-1B satellite in April 2016, the two-satellite Sentinel-1 (S1) mission is now complete, and will become fully operational within the next year. While several other parts of the geophysical community have enjoyed operational data services for a long time, this is a many ways a new situation for scientists who rely on Interferometric SAR (InSAR) data for their research. The operational acquisition mode for S1 over land is the Terrain Observation by Progressive Scans (TOPS) mode. In the ESA SEOM project InSARap (http://www.insarap.org), our team has studied TOPS interferometric processing and its applications in detail, and the project continues with focus on the full two-satellite constellation. Here, we will present various characteristics of the S1 constellation, from the viewpoint of InSAR applications within geoscience. In particular, implications of the regular temporal sampling will be treated in detail. We will show examples from various land deformation phenomena with total deformation ranging from decimeters to sub-centimeters since October 2014 when the first data from Sentinel-1A became publicly available. As a demonstration of operational data exploitation, we will also show how the operational free and open data access provided by the USGS Earthquake Hazards Program (http://earthquake.usgs.gov) and the Sentinels Scientific Data Hub (http://scihub.copernicus.eu) can be combined to automatically provide InSAR data for significant earthquakes in a timely manner. Various statistics for historical co-seismic S1 interferograms will be presented, with emphasis on relevant quality parameters, as well as on the typical time from earthquake to available InSAR data.

  11. Increasing Intelligence, Surveillance, and Reconnaissance (ISR) Operational Agility through Mission Command

    DTIC Science & Technology

    2016-06-10

    INCREASING INTELLIGENCE , SURVEILLANCE, AND RECONNAISSANCE (ISR) OPERATIONAL AGILITY THROUGH MISSION COMMAND A thesis presented to... Intelligence , Surveillance, and Reconnaissance (ISR) Operational Agility through Mission Command 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c...thesis examines if applying the six principles of the United States Army’s mission command philosophy would improve the agility of Joint intelligence

  12. Decision Making Training in the Mission Operations Directorate

    NASA Technical Reports Server (NTRS)

    O'Keefe, William S.

    2013-01-01

    At JSC, we train our new flight controllers on a set of team skills that we call Space Flight Resource Management (SFRM). SFRM is akin to Crew Resource Management for the airlines and trains flight controllers to work as an effective team to reduce errors and improve safety. We have developed this training over the years with the assistance of Ames Research Center, Wyle Labs and University of Central Florida. One of the skills we teach is decision making/ problem solving (DM/PS). We teach DM/PS first in several classroom sessions, reinforce it in several part task training environments, and finally practice it in full-mission, full-team simulations. What I am proposing to talk about is this training flow: its content and how we teach it.

  13. The ESA Scientific Exploitation of Operational Missions element, first results

    NASA Astrophysics Data System (ADS)

    Desnos, Yves-Louis; Regner, Peter; Delwart, Steven; Benveniste, Jerome; Engdahl, Marcus; Mathieu, Pierre-Philippe; Gascon, Ferran; Donlon, Craig; Davidson, Malcolm; Pinnock, Simon; Foumelis, Michael; Ramoino, Fabrizio

    2016-04-01

    SEOM is a program element within the fourth period (2013-2017) of ESA's Earth Observation Envelope Programme (http://seom.esa.int/). The prime objective is to federate, support and expand the international research community that the ERS, ENVISAT and the Envelope programmes have built up over the last 25 years. It aims to further strengthen the leadership of the European Earth Observation research community by enabling them to extensively exploit future European operational EO missions. SEOM will enable the science community to address new scientific research that are opened by free and open access to data from operational EO missions. Based on community-wide recommendations for actions on key research issues, gathered through a series of international thematic workshops and scientific user consultation meetings, a work plan is established and is approved every year by ESA Members States. During 2015 SEOM, Science users consultation workshops have been organized for Sentinel1/3/5P ( Fringe, S3 Symposium and Atmospheric science respectively) , new R&D studies for scientific exploitation of the Sentinels have been launched ( S3 for Science SAR Altimetry and Ocean Color , S2 for Science,) , open-source multi-mission scientific toolboxes have been launched (in particular the SNAP/S1-2-3 Toolbox). In addition two advanced international training courses have been organized in Europe to exploit the new S1-A and S2-A data for Land and Ocean remote sensing (over 120 participants from 25 countries) as well as activities for promoting the first scientific results ( e.g. Chili Earthquake) . In addition the First EO Open Science 2.0 was organised at ESA in October 2015 with 225 participants from 31 countries bringing together young EO scientists and data scientists. During the conference precursor activities in EO Open Science and Innovation were presented, while developing a Roadmap preparing for future ESA scientific exploitation activities. Within the conference, the first

  14. MISSION CONTROL CENTER (MCC) - APOLLO-SOYUZ TEST PROJECT (ASTP) - JSC

    NASA Image and Video Library

    1975-07-17

    S75-28682 (17 July 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center during the joint U.S.-USSR Apollo-Soyuz Test Project docking mission in Earth orbit. The large television monitor shows a view of the Soyuz spacecraft as seen from the Apollo spacecraft during rendezvous and docking maneuvers. Eugene F. Kranz, JSC Deputy Director of Flight Operations, is standing in the foreground. M.P. Frank, the American senior ASTP flight director, is partially obscured on the right.

  15. Mission Control activities during Day 1 First TV Pass of STS-11

    NASA Image and Video Library

    1984-02-03

    S84-26297 (3 Feb 1984) --- Robert E. Castle, Integrated Communications Officer (INCO), plays an important role in the first television transmission from the Earth-orbiting Space Shuttle Challenger. Castle, at a console in the Johnson Space Center's (JSC) Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), is responsible for ground controlled television from the Orbiter on his shift. Here, the Westar VI satellite is seen in the cargo bay just after opening of the payload bay doors.

  16. INFLIGHT (MISSION CONTROL CENTER [MCC])- STS-11/41B - JSC

    NASA Image and Video Library

    1984-02-06

    S84-26332 (3 Feb 1984) --- Robert E. Castle, integrated communications officer (INCO), plays an important role in the first television transmission from the Earth-orbiting Space Shuttle Challenger. Castle, at a console in the Johnson Space Center?s mission operations control room (MOCR) in the mission control center, is responsible for ground controlled television from the orbiter on his shift. Here, the Westar VI satellite is seen in the cargo bay just after opening of the payload bay doors.

  17. View of mission control during the EVA by McCandless

    NASA Image and Video Library

    1984-02-11

    S84-26985 (7 Feb 1984) --- Flight controllers in the mission operations control room (MOCR) of the Johnson Space Center?s mission control center monitor the extravehicular activity (EVA) of Astronauts Bruce McCandless II and Robert L. Stewart. The photograph was taken with a wide angle lens on a 35mm camera deployed in the aft center point of the MOCR.

  18. An intelligent position-specific training system for mission operations

    NASA Technical Reports Server (NTRS)

    Schneider, M. P.

    1992-01-01

    Marshall Space Flight Center's (MSFC's) payload ground controller training program provides very good generic training; however, ground controller position-specific training can be improved by including position-specific training systems in the training program. This report explains why MSFC needs to improve payload ground controller position-specific training. The report describes a generic syllabus for position-specific training systems, a range of system designs for position-specific training systems, and a generic development process for developing position-specific training systems. The report also describes a position-specific training system prototype that was developed for the crew interface coordinator payload operations control center ground controller position. The report concludes that MSFC can improve the payload ground controller training program by incorporating position-specific training systems for each ground controller position; however, MSFC should not develop position-specific training systems unless payload ground controller position experts will be available to participate in the development process.

  19. Dust Storm Impacts on Human Mars Mission Equipment and Operations

    NASA Astrophysics Data System (ADS)

    Rucker, M. A.

    2017-06-01

    NASA has accumulated a wealth of experience between the Apollo program and robotic Mars rover programs, but key differences between those missions and a human Mars mission that will require unique approaches to mitigate potential dust storm concerns.

  20. Asteroid Redirect Mission Robotic Trajectory and Crew Operations

    NASA Image and Video Library

    This concept animation opens with a rendering of the mission's spacecraft trajectory, rendezvous, and approach to asteroid 2008 EV5. Although the mission's target asteroid won't officially be selec...

  1. Integrated operations/payloads/fleet analysis. Volume 5: Mission, capture and operations analysis

    NASA Technical Reports Server (NTRS)

    1971-01-01

    The current baseline mission model consists of the DOD Option B prepared for space transportation system mission analysis and a NASA model prepared for the integrated operations /payloads/ fleet analysis. Changes from the previous mission model are discussed, and additional benefits of the reusable space shuttle system are identified. The methodology and assumptions used in the capture analysis are described, and satellite and launch vehicle traffic models for the current and low cost expendable launch vehicle systems and the reusable space shuttle system are presented. The areas of fleet sizing, limitations and abort modes, system ground support requirements, and ground support systems assessment are covered. Current and extended launch azimuth limitations used for both ETR and WTR are presented for the current and low cost expendable vehicles and also the reusable space shuttle system. The results of a survey of launch support capability for the launch vehicle fleets are reported.

  2. STS-35 Mission Specialist Parker operates ASTRO-1 MPC on OV-102's flight deck

    NASA Image and Video Library

    1990-12-10

    STS035-10-011 (2-10 Dec 1990) --- STS-35 Mission Specialist (MS) Robert A.R. Parker operates Astronomy Laboratory 1 (ASTRO-1) manual pointing controller (MPC) on the aft flight deck of Columbia, Orbiter Vehicle (OV) 102. Parker monitors a closed circuit television (CCTV) screen at the payload station as he uses the MPC to send data collection instructions to the ASTRO-1 instrument pointing system (IPS).

  3. Mission operations for unmanned nuclear electric propulsion outer planet exploration with a thermionic reactor spacecraft.

    NASA Technical Reports Server (NTRS)

    Spera, R. J.; Prickett, W. Z.; Garate, J. A.; Firth, W. L.

    1971-01-01

    Mission operations are presented for comet rendezvous and outer planet exploration NEP spacecraft employing in-core thermionic reactors for electric power generation. The selected reference missions are the Comet Halley rendezvous and a Jupiter orbiter at 5.9 planet radii, the orbit of the moon Io. The characteristics of the baseline multi-mission NEP spacecraft are presented and its performance in other outer planet missions, such as Saturn and Uranus orbiters and a Neptune flyby, are discussed. Candidate mission operations are defined from spacecraft assembly to mission completion. Pre-launch operations are identified. Shuttle launch and subsequent injection to earth escape by the Centaur D-1T are discussed, as well as power plant startup and the heliocentric mission phases. The sequence and type of operations are basically identical for all missions investigated.

  4. An Empirical Model for Formulating Operational Missions for Community Colleges.

    ERIC Educational Resources Information Center

    Richardson, Richard C., Jr.; Doucette, Donald S.

    A research project was conducted to develop and implement a model for community college missions. The new model would depart from existing models, which utilize a hierarchy of decreasing levels of generality beginning with institutional missions and culminating in objectives. In contrast, this research defined institutional mission in terms of…

  5. Crewmember and mission control personnel interactions during International Space Station missions.

    PubMed

    Kanas, Nick A; Salnitskiy, Vyacheslav P; Boyd, Jennifer E; Gushin, Vadim I; Weiss, Daniel S; Saylor, Stephanie A; Kozerenko, Olga P; Marmar, Charles R

    2007-06-01

    Reports from astronauts and cosmonauts, studies from space analogue environments on Earth, and our previous research on the Mir Space Station have identified a number of psychosocial issues that can lead to problems during long-duration space missions. Three of these issues (time effects, displacement, leader role) were studied during a series of long-duration missions to the International Space Station (ISS). As in our previous Mir study, mood and group climate questions from the Profile of Mood States or POMS, the Group Environment Scale or GES, and the Work Environment Scale or WES were completed weekly by 17 ISS crewmembers (15 men, 2 women) in space and 128 American and Russian personnel in mission control. The results did not support the presence of decrements in mood and group cohesion during the 2nd half of the missions or in any specific quarter. The results did support the predicted displacement of negative feelings to outside supervisors in both crew and mission control subjects on all six questionnaire subscales tested. Crewmembers related cohesion in their group to the support role of their commander. For mission control personnel, greater cohesion was linked to the support role as well as to the task role of their leader. The findings from our previous study on the Mir Space Station were essentially replicated on board the ISS. The findings suggest a number of countermeasures for future on-orbit missions, some of which may not be relevant for expeditionary missions (e.g., to Mars).

  6. Operationally Responsive Space Launch for Space Situational Awareness Missions

    NASA Astrophysics Data System (ADS)

    Freeman, T.

    The United States Space Situational Awareness capability continues to be a key element in obtaining and maintaining the high ground in space. Space Situational Awareness satellites are critical enablers for integrated air, ground and sea operations, and play an essential role in fighting and winning conflicts. The United States leads the world space community in spacecraft payload systems from the component level into spacecraft and in the development of constellations of spacecraft. This position is founded upon continued government investment in research and development in space technology, which is clearly reflected in the Space Situational Awareness capabilities and the longevity of these missions. In the area of launch systems that support Space Situational Awareness, despite the recent development of small launch vehicles, the United States launch capability is dominated by unresponsive and relatively expensive launchers in the Expandable, Expendable Launch Vehicles (EELV). The EELV systems require an average of six to eight months from positioning on the launch table until liftoff. Access to space requires maintaining a robust space transportation capability, founded on a rigorous industrial and technology base. To assure access to space, the United States directed Air Force Space Command to develop the capability for operationally responsive access to space and use of space to support national security, including the ability to provide critical space capabilities in the event of a failure of launch or on-orbit capabilities. Under the Air Force Policy Directive, the Air Force will establish, organize, employ, and sustain space forces necessary to execute the mission and functions assigned including rapid response to the National Command Authorities and the conduct of military operations across the spectrum of conflict. Air Force Space Command executes the majority of spacelift operations for DoD satellites and other government and commercial agencies. The

  7. Space acceleration measurement system description and operations on the First Spacelab Life Sciences Mission

    NASA Technical Reports Server (NTRS)

    Delombard, Richard; Finley, Brian D.

    1991-01-01

    The Space Acceleration Measurement System (SAMS) project and flight units are briefly described. The SAMS operations during the STS-40 mission are summarized, and a preliminary look at some of the acceleration data from that mission are provided. The background and rationale for the SAMS project is described to better illustrate its goals. The functions and capabilities of each SAMS flight unit are first explained, then the STS-40 mission, the SAMS's function for that mission, and the preparation of the SAMS are described. Observations about the SAMS operations during the first SAMS mission are then discussed. Some sample data are presented illustrating several aspects of the mission's microgravity environment.

  8. Real-time science operations to support a lunar polar volatiles rover mission

    NASA Astrophysics Data System (ADS)

    Heldmann, Jennifer L.; Colaprete, Anthony; Elphic, Richard C.; Mattes, Greg; Ennico, Kimberly; Fritzler, Erin; Marinova, Margarita M.; McMurray, Robert; Morse, Stephanie; Roush, Ted L.; Stoker, Carol R.

    2015-05-01

    Future human exploration of the Moon will likely rely on in situ resource utilization (ISRU) to enable long duration lunar missions. Prior to utilizing ISRU on the Moon, the natural resources (in this case lunar volatiles) must be identified and characterized, and ISRU demonstrated on the lunar surface. To enable future uses of ISRU, NASA and the CSA are developing a lunar rover payload that can (1) locate near subsurface volatiles, (2) excavate and analyze samples of the volatile-bearing regolith, and (3) demonstrate the form, extractability and usefulness of the materials. Such investigations are important both for ISRU purposes and for understanding the scientific nature of these intriguing lunar volatile deposits. Temperature models and orbital data suggest near surface volatile concentrations may exist at briefly lit lunar polar locations outside persistently shadowed regions. A lunar rover could be remotely operated at some of these locations for the ∼ 2-14 days of expected sunlight at relatively low cost. Due to the limited operational time available, both science and rover operations decisions must be made in real time, requiring immediate situational awareness, data analysis, and decision support tools. Given these constraints, such a mission requires a new concept of operations. In this paper we outline the results and lessons learned from an analog field campaign in July 2012 which tested operations for a lunar polar rover concept. A rover was operated in the analog environment of Hawaii by an off-site Flight Control Center, a rover navigation center in Canada, a Science Backroom at NASA Ames Research Center in California, and support teams at NASA Johnson Space Center in Texas and NASA Kennedy Space Center in Florida. We find that this type of mission requires highly efficient, real time, remotely operated rover operations to enable low cost, scientifically relevant exploration of the distribution and nature of lunar polar volatiles. The field

  9. Space Test and Operations Port for Exploration Missions

    NASA Technical Reports Server (NTRS)

    Holt, Alan C.

    2004-01-01

    The International Space Station (ISS) has from its inception included plans to support the testing of exploration vehicle/systems technology, the assembly of space transport vehicles, and a variety of operations support (communications, crew transfer, cargo handling, etc). Despite the fact that the ISS has gone through several re-designs and reductions in size and capabilities over the past 20 years, it still has the key capabilities, truss structure, docking nodes, etc required to support these exploration mission activities. ISS is much like a frontier outpost in the Old West, which may not have been in optimum location (orbit) for assisting travelers on their way to California (the Moon and Mars), but nevertheless because it had supplies and other support services (regular logistics from Earth, crewmembers, robotics, and technology test and assembly support capabilities) was regularly used as a stopover and next trip phase preparation site by all kinds of travelers. This paper will describe some of the ISS capabilities which are being used currently, and are being planned for use, by various payload sponsors, developers and Principal Investigators, sponsored by the NASA Office of Space Flight (Code M ISS Research Program Office - Department of Defense (DoD), NASA Hqs Office of Space Communications, Italian Space Agency, etc.). Initial ideas and concepts for payloads and technology testing which are being planned, or which are being investigated, for use in support of advanced space technology development and verification and exploration mission activities will be summarized. Some of the future ISS payloads and test activities already identified include materials and system component space environment testing, laser space communication system demonstrations (leading to the possible development of an ISS deep space communication node), and an advanced space propulsion testbed and ISS based, free-flying platform.

  10. NEEMO - NASA's Extreme Environment Mission Operations: On to a NEO

    NASA Technical Reports Server (NTRS)

    Bell, M. S.; Baskin, P. J.; Todd, W. L.

    2011-01-01

    During NEEMO missions, a crew of six Aquanauts lives aboard the National Oceanic and Atmospheric Administration (NOAA) Aquarius Underwater Laboratory the world's only undersea laboratory located 5.6 km off shore from Key Largo, Florida. The Aquarius habitat is anchored 62 feet deep on Conch Reef which is a research only zone for coral reef monitoring in the Florida Keys National Marine Sanctuary. The crew lives in saturation for a week to ten days and conducts a variety of undersea EVAs (Extra Vehicular Activities) to test a suite of long-duration spaceflight Engineering, Biomedical, and Geoscience objectives. The crew also tests concepts for future lunar exploration using advanced navigation and communication equipment in support of the Constellation Program planetary exploration analog studies. The Astromaterials Research and Exploration Science (ARES) Directorate and Behavioral Health and Performance (BHP) at NASA/Johnson Space Center (JSC), Houston, Texas support this effort to produce a high-fidelity test-bed for studies of human planetary exploration in extreme environments as well as to develop and test the synergy between human and robotic curation protocols including sample collection, documentation, and sample handling. The geoscience objectives for NEEMO missions reflect the requirements for Lunar Surface Science outlined by the LEAG (Lunar Exploration Analysis Group) and CAPTEM (Curation and Analysis Planning Team for Extraterrestrial Materials) white paper [1]. The BHP objectives are to investigate best meas-ures and tools for assessing decrements in cogni-tive function due to fatigue, test the feasibility study examined how teams perform and interact across two levels, use NEEMO as a testbed for the development, deployment, and evaluation of a scheduling and planning tool. A suite of Space Life Sciences studies are accomplished as well, ranging from behavioral health and performance to immunology, nutrition, and EVA suit design results of which will

  11. A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

    NASA Technical Reports Server (NTRS)

    Estefan, Jeff A.; Giovannoni, Brian J.

    2014-01-01

    The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost

  12. A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

    NASA Technical Reports Server (NTRS)

    Estefan, Jeff A.; Giovannoni, Brian J.

    2014-01-01

    The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost

  13. A Data-Based Console Logger for Mission Operations Team Coordination

    NASA Technical Reports Server (NTRS)

    Thronesbery, Carroll; Malin, Jane T.; Jenks, Kenneth; Overland, David; Oliver, Patrick; Zhang, Jiajie; Gong, Yang; Zhang, Tao

    2005-01-01

    Concepts and prototypes1,2 are discussed for a data-based console logger (D-Logger) to meet new challenges for coordination among flight controllers arising from new exploration mission concepts. The challenges include communication delays, increased crew autonomy, multiple concurrent missions, reduced-size flight support teams that include multidisciplinary flight controllers during quiescent periods, and migrating some flight support activities to flight controller offices. A spiral development approach has been adopted, making simple, but useful functions available early and adding more extensive support later. Evaluations have guided the development of the D-Logger from the beginning and continue to provide valuable user influence about upcoming requirements. D-Logger is part of a suite of tools designed to support future operations personnel and crew. While these tools can be used independently, when used together, they provide yet another level of support by interacting with one another. Recommendations are offered for the development of similar projects.

  14. Lessons Learned from Optical Payload for Lasercomm Science (OPALS) Mission Operations

    NASA Technical Reports Server (NTRS)

    Sindiy, Oleg V.; Abrahamson, Matthew J.; Biswas, Abhijit; Wright, Malcolm W.; Padams, Jordan H.; Konyha, Alexander L.

    2015-01-01

    This paper provides an overview of Optical Payload for Lasercomm Science (OPALS) activities and lessons learned during mission operations. Activities described cover the periods of commissioning, prime, and extended mission operations, during which primary and secondary mission objectives were achieved for demonstrating space-to-ground optical communications. Lessons learned cover Mission Operations System topics in areas of: architecture verification and validation, staffing, mission support area, workstations, workstation tools, interfaces with support services, supporting ground stations, team training, procedures, flight software upgrades, post-processing tools, and public outreach.

  15. View of Mission Control Center during the Apollo 13 emergency return

    NASA Image and Video Library

    1970-04-16

    S70-35368 (16 April 1970) --- Overall view showing some of the feverish activity in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) during the final 24 hours of the problem-plagued Apollo 13 mission. Here, flight controllers and several NASA/MSC officials confer at the flight director's console. When this picture was made, the Apollo 13 lunar landing had already been canceled, and the Apollo 13 crewmembers were in trans-Earth trajectory attempting to bring their crippled spacecraft back home.

  16. Personnel in Mission Control conferring on repair to LRV fender

    NASA Technical Reports Server (NTRS)

    1972-01-01

    These five men in the Mission Control Center ponder the solution to the problem of the damage to the right rear fender of the Apollo 17 Lunar Roving Vehicle at the Taurus-Littrow landing site. Clockwise are Astronauts John W. Young and Charles M. Duke Jr., two Apollo 17 capcoms; Donald K. Slayton, Director of Flight Crew Operations at MSC; Dr. Rocco A. Petrone, Apollo Program Director, Office of Manned Space Flight, NASA HQ.; and Ronald V. Blevins, an EVA-1 flight controller with General Electric. They are looking over a makeshift repair arrangement which uses lunar maps and clamps from the optical alignment telescope lamp, a repair suggestion made by Astronaut Young.

  17. SCOS 2: ESA's new generation of mission control system

    NASA Technical Reports Server (NTRS)

    Jones, M.; Head, N. C.; Keyte, K.; Howard, P.; Lynenskjold, S.

    1994-01-01

    New mission-control infrastructure is currently being developed by ESOC, which will constitute the second generation of the Spacecraft Control Operations system (SCOS 2). The financial, functional and strategic requirements lying behind the new development are explained. The SCOS 2 approach is described. The technological implications of these approaches is described: in particular it is explained how this leads to the use of object oriented techniques to provide the required 'building block' approach. The paper summarizes the way in which the financial, functional and strategic requirements have been met through this combination of solutions. Finally, the paper outlines the development process to date, noting how risk reduction was achieved in the approach to new technologies and summarizes the current status future plans.

  18. AE-C attitude determination and control prelaunch analysis and operations plan

    NASA Technical Reports Server (NTRS)

    Werking, R. D.; Headrick, R. D.; Manders, C. F.; Woolley, R. D.

    1973-01-01

    A description of attitude control support being supplied by the Mission and Data Operations Directorate is presented. Included are descriptions of the computer programs being used to support the missions for attitude determination, prediction, and control. In addition, descriptions of the operating procedures which will be used to accomplish mission objectives are provided.

  19. STS-26 Mission Control Center (MCC) activity at JSC

    NASA Technical Reports Server (NTRS)

    1988-01-01

    Flight controllers in JSC's Mission Control Center (MCC) Bldg 30 flight control room (FCR) listen to a presentation by STS-26 crewmembers on the fourth day of Discovery's, Orbiter Vehicle (OV) 103's, orbital mission. Flight Directors Charles W. Shaw and James M. (Milt) Heflin (in the foreground) and other controllers view a television image of Earth on a screen in the front of the FCR while listening to crewmembers.

  20. STS-26 Mission Control Center (MCC) activity at JSC

    NASA Technical Reports Server (NTRS)

    1988-01-01

    Flight controllers in JSC's Mission Control Center (MCC) Bldg 30 flight control room (FCR) listen to a presentation by STS-26 crewmembers on the fourth day of Discovery's, Orbiter Vehicle (OV) 103's, orbital mission. Instrumentation and Communications Officers (INCOs) Harold Black (left foreground) and John F. Muratore and other controllers view a television (TV) transmission of the crew on a screen in front of the FCR as each member relates some inner feelings while paying tribute to the 51L Challenger crew.

  1. SCOSII: ESA's new generation of mission control systems: The user's perspective

    NASA Astrophysics Data System (ADS)

    Kaufeler, P.; Pecchioli, M.; Shurmer, I.

    1994-11-01

    In 1974 ESOC decided to develop a reusable Mission Control System infrastructure for ESA's missions operated under its responsibility. This triggered a long and successful product development line, which started with the Multi Mission Support System (MSSS) which entered in service in 1977 and is still being used today by the MARECS and ECS missions; it was followed in 1989 by a second generation of systems known as SCOS-I, which was/is used by the Hipparcos, ERS-1 and EURECA missions and will continue to support all future ESCO controlled missions until approximately 1995. In the meantime the increasing complexity of future missions together with the emergence of new hardware and software technologies have led ESOC to go for the development of a third generation of control systems, SCOSII, which will support their future missions up to at least the middle of the next decade. The objective of the paper is to present the characteristics of the SCOSII system from the perspective of the mission control team; i.e. it will concentrate on the improvements and advances in the performance, functionality and work efficiency of the system.

  2. SCOSII: ESA's new generation of mission control systems: The user's perspective

    NASA Technical Reports Server (NTRS)

    Kaufeler, P.; Pecchioli, M.; Shurmer, I.

    1994-01-01

    In 1974 ESOC decided to develop a reusable Mission Control System infrastructure for ESA's missions operated under its responsibility. This triggered a long and successful product development line, which started with the Multi Mission Support System (MSSS) which entered in service in 1977 and is still being used today by the MARECS and ECS missions; it was followed in 1989 by a second generation of systems known as SCOS-I, which was/is used by the Hipparcos, ERS-1 and EURECA missions and will continue to support all future ESCO controlled missions until approximately 1995. In the meantime the increasing complexity of future missions together with the emergence of new hardware and software technologies have led ESOC to go for the development of a third generation of control systems, SCOSII, which will support their future missions up to at least the middle of the next decade. The objective of the paper is to present the characteristics of the SCOSII system from the perspective of the mission control team; i.e. it will concentrate on the improvements and advances in the performance, functionality and work efficiency of the system.

  3. View of activity in Mission Control Center during Lunar Module liftoff

    NASA Technical Reports Server (NTRS)

    1971-01-01

    A partial view of activity in the Mission Operations Control Room in the Mission Control Center during the liftoff of the Apollo 15 Lunar Module 'Falcon' ascent stage from the lunar surface. An RCA color television camera mounted on the Lunar Roving Vehicle made it possible for people on Earth to watch the Lunar Module (LM) launch from the Moon. Seated in the right foreground is Astronaut Edgar D. Mitchell, a spacecraft communicator. Note liftoff on the television monitor in the center background.

  4. View of Mission Control on first day of ASTP docking in Earth orbit

    NASA Technical Reports Server (NTRS)

    1975-01-01

    An overall view of the Mission Operations Control Room in the Mission Control Center, bldg 30, JSC, on the first day of the Apollo Soyuz Test Project (ASTP) docking in Earth orbit. This photograph was taken shortly before the American ASTP launch from the Kennedy Space Center. The television monitor in the center background shows the ASTP Apollo-Saturn 1B space vehicle on Pad B at KSC's Launch Complex 39.

  5. Cassini Attitude Control Fault Protection Design: Launch to End of Prime Mission Performance

    NASA Technical Reports Server (NTRS)

    Meakin, Peter C.

    2008-01-01

    The Cassini Attitude and Articulation Control Subsystem (AACS) Fault Protection (FP) has been successfully supporting operations for over 10 years from launch through the end of the prime mission. Cassini's AACS FP is complex, containing hundreds of error monitors and thousands of tunable parameters. Since launch there have been environmental, hardware, personnel and mission event driven changes which have required AACS FP to adapt and be robust to a variety of scenarios. This paper will discuss the process of monitoring, maintaining and updating the AACS FP during Cassini's lengthy prime mission as well as provide some insight into lessons learned during tour operations.

  6. Contributing Factors to Total Mission Time for Medical Evacuation Missions during Operation Iraqi Freedom II

    DTIC Science & Technology

    2007-05-01

    nature have been conducted to analyze the data. Recent studies focused on the aeromedical evacuation from Level III facilities in theater to higher...missions with unusually large Total Mission Time or to compress the data by taking the natural log of the time variables. However, the data was not...All of the data is unclassified separately, but the analysis could be sensitive in nature so caution has been taken to protect it. Some missions may

  7. VMPLOT: A versatile analysis tool for mission operations

    NASA Technical Reports Server (NTRS)

    Bucher, Allen W.

    1993-01-01

    VMPLOT is a versatile analysis tool designed by the Magellan Spacecraft Team to graphically display engineering data used to support mission operations. While there is nothing revolutionary or innovative about graphical data analysis tools, VMPLOT has some distinguishing features that set it apart from other custom or commercially available software packages. These features include the ability to utilize time in a Universal Time Coordinated (UTC) or Spacecraft Clock (SCLK) format as an enumerated data type, the ability to automatically scale both axes based on the data to be displayed (including time), the ability to combine data from different files, and the ability to utilize the program either interactively or in batch mode, thereby enhancing automation. Another important feature of VMPLOT not visible to the user is the software engineering philosophies utilized. A layered approach was used to isolate program functionality to different layers. This was done to increase program portability to different platforms and to ease maintenance and enhancements due to changing requirements. The functionality of the unique features of VMPLOT as well as highlighting the algorithms that make these features possible are described. The software engineering philosophies used in the creation of the software tool are also summarized.

  8. TAMU: Blueprint for A New Space Mission Operations System Paradigm

    NASA Technical Reports Server (NTRS)

    Ruszkowski, James T.; Meshkat, Leila; Haensly, Jean; Pennington, Al; Hogle, Charles

    2011-01-01

    The Transferable, Adaptable, Modular and Upgradeable (TAMU) Flight Production Process (FPP) is a System of System (SOS) framework which cuts across multiple organizations and their associated facilities, that are, in the most general case, in geographically disperse locations, to develop the architecture and associated workflow processes of products for a broad range of flight projects. Further, TAMU FPP provides for the automatic execution and re-planning of the workflow processes as they become operational. This paper provides the blueprint for the TAMU FPP paradigm. This blueprint presents a complete, coherent technique, process and tool set that results in an infrastructure that can be used for full lifecycle design and decision making during the flight production process. Based on the many years of experience with the Space Shuttle Program (SSP) and the International Space Station (ISS), the currently cancelled Constellation Program which aimed on returning humans to the moon as a starting point, has been building a modern model-based Systems Engineering infrastructure to Re-engineer the FPP. This infrastructure uses a structured modeling and architecture development approach to optimize the system design thereby reducing the sustaining costs and increasing system efficiency, reliability, robustness and maintainability metrics. With the advent of the new vision for human space exploration, it is now necessary to further generalize this framework to take into consideration a broad range of missions and the participation of multiple organizations outside of the MOD; hence the Transferable, Adaptable, Modular and Upgradeable (TAMU) concept.

  9. STS-99 Shuttle Radar Topography Mission Stability and Control

    NASA Technical Reports Server (NTRS)

    Hamelin, Jennifer L.; Jackson, Mark C.; Kirchwey, Christopher B.; Pileggi, Roberto A.

    2001-01-01

    The Shuttle Radar Topography Mission (SRTM) flew aboard Space Shuttle Endeavor February 2000 and used interferometry to map 80% of the Earth's landmass. SRTM employed a 200-foot deployable mast structure to extend a second antenna away from the main antenna located in the Shuttle payload bay. Mapping requirements demanded precision pointing and orbital trajectories from the Shuttle on-orbit Flight Control System (PCS). Mast structural dynamics interaction with the FCS impacted stability and performance of the autopilot for attitude maneuvers and pointing during mapping operations. A damper system added to ensure that mast tip motion remained with in the limits of the outboard antenna tracking system while mapping also helped to mitigate structural dynamic interaction with the FCS autopilot. Late changes made to the payload damper system, which actually failed on-orbit, required a redesign and verification of the FCS autopilot filtering schemes necessary to ensure rotational control stability. In-flight measurements using three sensors were used to validate models and gauge the accuracy and robustness of the pre-mission notch filter design.

  10. Third International Symposium on Space Mission Operations and Ground Data Systems, part 1

    NASA Technical Reports Server (NTRS)

    Rash, James L. (Editor)

    1994-01-01

    Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The papers focus on improvements in the efficiency, effectiveness, productivity, and quality of data acquisition, ground systems, and mission operations. New technology, techniques, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations.

  11. Correlation of ISS Electric Potential Variations with Mission Operations

    NASA Technical Reports Server (NTRS)

    Willis, Emily M.; Minow, Joseph I.; Parker, Linda Neergaard

    2014-01-01

    Orbiting approximately 400 km above the Earth, the International Space Station (ISS) is a unique research laboratory used to conduct ground-breaking science experiments in space. The ISS has eight Solar Array Wings (SAW), and each wing is 11.7 meters wide and 35.1 meters long. The SAWs are controlled individually to maximize power output, minimize stress to the ISS structure, and minimize interference with other ISS operations such as vehicle dockings and Extra-Vehicular Activities (EVA). The Solar Arrays are designed to operate at 160 Volts. These large, high power solar arrays are negatively grounded to the ISS and collect charged particles (predominately electrons) as they travel through the space plasma in the Earth's ionosphere. If not controlled, this collected charge causes floating potential variations which can result in arcing, causing injury to the crew during an EVA or damage to hardware [1]. The environmental catalysts for ISS floating potential variations include plasma density and temperature fluctuations and magnetic induction from the Earth's magnetic field. These alone are not enough to cause concern for ISS, but when they are coupled with the large positive potential on the solar arrays, floating potentials up to negative 95 Volts have been observed. Our goal is to differentiate the operationally induced fluctuations in floating potentials from the environmental causes. Differentiating will help to determine what charging can be controlled, and we can then design the proper operations controls for charge collection mitigation. Additionally, the knowledge of how high power solar arrays interact with the environment and what regulations or design techniques can be employed to minimize charging impacts can be applied to future programs.

  12. Gamma Ray Observatory (GRO) Prelaunch Mission Operations Report (MOR)

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The NASA Astrophysics Program is an endeavor to understand the origin and fate of the universe, to understand the birth and evolution of the large variety of objects in the universe, from the most benign to the most violent, and to probe the fundamental laws of physics by examining their behavior under extreme physical conditions. These goals are pursued by means of observations across the entire electromagnetic spectrum, and through theoretical interpretation of radiations and fields associated with astrophysical systems. Astrophysics orbital flight programs are structured under one of two operational objectives: (1) the establishment of long duration Great Observatories for viewing the universe in four major wavelength regions of the electromagnetic spectrum (radio/infrared/submillimeter, visible/ultraviolet, X-ray, and gamma ray), and (2) obtaining crucial bridging and supporting measurements via missions with directed objectives of intermediate or small scope conducted within the Explorer and Spacelab programs. Under (1) in this context, the Gamma Ray Observatory (GRO) is one of NASA's four Great Observatories. The other three are the Hubble Space Telescope (HST) for the visible and ultraviolet portion of the spectrum, the Advanced X-ray Astrophysics Facility (AXAF) for the X-ray band, and the Space Infrared Telescope Facility (SIRTF) for infrared wavelengths. GRO's specific mission is to study the sources and astrophysical processes that produce the highest energy electromagnetic radiation from the cosmos. The fundamental physical processes that are known to produce gamma radiation in the universe include nuclear reactions, electron bremsstrahlung, matter-antimatter annihilation, elementary particle production and decay, Compton scattering, synchrotron radiation. GRO will address a variety of questions relevant to understanding the universe, such as: the formation of the elements; the structure and dynamics of the Galaxy; the nature of pulsars; the existence

  13. Special Operations Reconnaissance (SOR) Scenario: Intelligence Analysis and Mission Planning

    DTIC Science & Technology

    2008-04-15

    experience in intelligence analysis and mission planning, the SOR scenario was developed to serve as this environment. The scenario is intended to be... intelligence analysis and mission planning scenario that requires a team of three participants to work together to solve various problems in an

  14. The ESA Scientific Exploitation of Operational Missions element

    NASA Astrophysics Data System (ADS)

    Desnos, Yves-Louis; Regner, Peter; Zehner, Claus; Engdahl, Marcus; Benveniste, Jerome; Delwart, Steven; Gascon, Ferran; Mathieu, Pierre-Philippe; Bojkov, Bojan; Koetz, Benjamin; Arino, Olivier; Donlon, Craig; Davidson, Malcolm; Goryl, Philippe; Foumelis, Michael

    2014-05-01

    The objectives of the ESA Scientific Exploitation of Operational Missions (SEOM) programme element are • to federate, support and expand the research community • to strengthen the leadership of European EO research community • to enable the science community to address new scientific research As a preparation for the SEOM element a series of international science users consultation has been organized by ESA in 2012 and 2013 In particular the ESA Living Planet Symposium was successfully organized in Edinburgh September 2013 and involving 1700 participants from 60 countries. The science users recommendations have been gathered and form the basis for the 2014 SEOM work plan approved by ESA member states. The SEOM element is organized along the following action lines: 1. Developing open-source, multi-mission, scientific toolboxes : the new toolboxes for Sentinel 1/2/3 and 5P will be introduced 2. Research and development studies: the first SEOM studies are being launched such as the INSARAP studies for Sentinel 1 interferometry in orbit demonstration , the IAS study to generate an improved spectroscopic database of the trace gas species CH4, H2O, and CO in the 2.3 μm region and SO2 in the UV region for Sentinel 5 P. In addition larger Sentinels for science call will be tendered in 2014 covering grouped studies for Sentinel 1 Land , Sentinel 1 Ocean , Sentinel 2 Land, Sentinel 3 SAR Altimetry ,Sentinel 3 Ocean color, Sentinel 3 Land and Sentinels Synergy . 3. Science users consultation : the Sentinel 2 for Science workshop is planned from 20 to 22 may 2014 at ESRIN to prepare for scientific exploitation of the Sentinel-2 mission (http://seom.esa.int/S2forScience2014 ) . In addition the FRINGE workshop focusing on scientific explotation of Sentinel1 using SAR interferometry is planned to be held at ESA ESRIN in Q2 2015 4. Training the next generation of European EO scientists on the scientific exploitation of Sentinels data: the Advanced Training course Land

  15. The Operational plans for Ptolemy during the Rosetta mission

    NASA Astrophysics Data System (ADS)

    Morse, Andrew; Andrews, Dan; Barber, Simeon; Sheridan, Simon; Morgan, Geraint; Wright, Ian

    2014-05-01

    Ptolemy is a Gas Chromatography - Isotope Ratio - Mass Spectrometer (GC-IR-MS) instrument within the Philae Lander, part of ESA's Rosetta mission [1]. The primary aim of Ptolemy is to analyse the chemical and isotopic composition of solid comet samples. Samples are collected by the Sampler, Drill and Distribution (SD2) system [2] and placed into ovens for analysis by three instruments on the Lander: COSAC [3], ÇIVA[4] and/or Ptolemy. In the case of Ptolemy, the ovens can be heated with or without oxygen and the evolved gases separated by chemical and GC techniques for isotopic analysis. In addition Ptolemy can measure gaseous (i.e. coma) samples by either directly measuring the ambient environment within the mass spectrometer or by passively trapping onto an adsorbent phase in order to pre-concentrate coma species before desorbing into the mass spectrometer. At the time of this presentation the Rosetta spacecraft should have come out of hibernation and Ptolemy's Post Hibernation Commissioning phase will have been completed. During the Comet Approach phase of the mission Ptolemy will attempt to measure the coma composition both in sniffing and pre-concentration modes. Previous work has demonstrated that spacecraft outgassing is a significant component of the gaseous environment and highlighted the advantage of obtaining complementary measurements with different instruments [5]. In principle Ptolemy could study the spatial evolution of gases through the coma during the lander's descent to the comet surface, but in practice it is likely that mission resources will need to be fully directed towards ensuring a safe landing. Once on the surface of the comet the lander begins its First Science Sequence which continues until the primary batteries are exhausted after some 42 hours. SD2 will collect a sample from a depth of ~5cm and deliver it to a Ptolemy high temperature oven which will then be analysed in five temperature steps to determine the carbon isotopic

  16. Infection control in operating theatres.

    PubMed

    Al-Benna, Sammy

    2012-10-01

    The operating theatre complex is the heart of any major surgical hospital. Good operating theatre design meets the functional needs of theatre care professionals. Operating theatre design must pay careful consideration to traffic patterns, the number and configuration of nearby operating rooms, the space required for staff, administration and storage, provisions for sterile processing and systems to control airborne contaminants (Wan et al 2011). There have been infection control issues with private finance initiative built operating theatres (Unison 2003, Ontario Health Coalition 2005). The aim of this article is to address these issues as they relate to infection control and prevention.

  17. View of Mission Control Center during the Apollo 13 oxygen cell failure

    NASA Image and Video Library

    1970-04-14

    S70-34904 (14 April 1970) --- Astronaut Alan B. Shepard Jr., prime crew commander of the Apollo 14 mission, monitors communications between the Apollo 13 spacecraft and Mission Control Center. He is seated at a console in the Mission Operations Control Room of the MCC, Manned Spacecraft Center. The main concern of the moment was action taken by the three Apollo 13 crewmen - astronauts James A. Lovell Jr., John L. Swigert Jr. and Fred W. Haise Jr. - to make corrections inside the spacecraft following discovery of an oxygen cell failure several hours earlier.

  18. Data Management Coordinators Monitor STS-78 Mission at the Huntsville Operations Support Center

    NASA Technical Reports Server (NTRS)

    1996-01-01

    Launched on June 20, 1996, the STS-78 mission's primary payload was the Life and Microgravity Spacelab (LMS), which was managed by the Marshall Space Flight Center (MSFC). During the 17 day space flight, the crew conducted a diverse slate of experiments divided into a mix of life science and microgravity investigations. In a manner very similar to future International Space Station operations, LMS researchers from the United States and their European counterparts shared resources such as crew time and equipment. Five space agencies (NASA/USA, European Space Agency/Europe (ESA), French Space Agency/France, Canadian Space Agency /Canada, and Italian Space Agency/Italy) along with research scientists from 10 countries worked together on the design, development and construction of the LMS. This photo represents Data Management Coordinators monitoring the progress of the mission at the Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at MSFC. Pictured are assistant mission scientist Dr. Dalle Kornfeld, Rick McConnel, and Ann Bathew.

  19. Data Management Coordinators Monitor STS-78 Mission at the Huntsville Operations Support Center

    NASA Technical Reports Server (NTRS)

    1996-01-01

    Launched on June 20, 1996, the STS-78 mission's primary payload was the Life and Microgravity Spacelab (LMS), which was managed by the Marshall Space Flight Center (MSFC). During the 17 day space flight, the crew conducted a diverse slate of experiments divided into a mix of life science and microgravity investigations. In a manner very similar to future International Space Station operations, LMS researchers from the United States and their European counterparts shared resources such as crew time and equipment. Five space agencies (NASA/USA, European Space Agency/Europe (ESA), French Space Agency/France, Canadian Space Agency /Canada, and Italian Space Agency/Italy) along with research scientists from 10 countries worked together on the design, development and construction of the LMS. This photo represents Data Management Coordinators monitoring the progress of the mission at the Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at MSFC. Pictured are assistant mission scientist Dr. Dalle Kornfeld, Rick McConnel, and Ann Bathew.

  20. Preliminary Operational Results of the TDRSS Onboard Navigation System (TONS) for the Terra Mission

    NASA Technical Reports Server (NTRS)

    Gramling, Cheryl; Lorah, John; Santoro, Ernest; Work, Kevin; Chambers, Robert; Bauer, Frank H. (Technical Monitor)

    2000-01-01

    The Earth Observing System Terra spacecraft was launched on December 18, 1999, to provide data for the characterization of the terrestrial and oceanic surfaces, clouds, radiation, aerosols, and radiative balance. The Tracking and Data Relay Satellite System (TDRSS) Onboard Navigation System (ONS) (TONS) flying on Terra provides the spacecraft with an operational real-time navigation solution. TONS is a passive system that makes judicious use of Terra's communication and computer subsystems. An objective of the ONS developed by NASA's Goddard Space Flight Center (GSFC) Guidance, Navigation and Control Center is to provide autonomous navigation with minimal power, weight, and volume impact on the user spacecraft. TONS relies on extracting tracking measurements onboard from a TDRSS forward-link communication signal and processing these measurements in an onboard extended Kalman filter to estimate Terra's current state. Terra is the first NASA low Earth orbiting mission to fly autonomous navigation which produces accurate results. The science orbital accuracy requirements for Terra are 150 meters (m) (3sigma) per axis with a goal of 5m (1 sigma) RSS which TONS is expected to meet. The TONS solutions are telemetered in real-time to the mission scientists along with their science data for immediate processing. Once set in the operational mode, TONS eliminates the need for ground orbit determination and allows for a smooth flow from the spacecraft telemetry to planning products for the mission team. This paper will present the preliminary results of the operational TONS solution available from Terra.

  1. Views of Mission Control Center during launch of STS-8

    NASA Technical Reports Server (NTRS)

    1983-01-01

    Serving as spacecraft communicators (CAPCOM) are Astronauts Guy S. Gardner (left), William F. Fisher (center), Bryan D. O'Connor (seated facing console), and Jeffrey A. Hoffman. Cheevon B. Lau is seated at the flight activities officer (FAO) console to the right of the CAPCOM console. The scene on the large screen in the mission operations control room (MOCR) is a replay of the launch of the Challenger (39264); Flight Director Jay H. Greene, left, watches a replay of the STS-8 launch on the large screen in the MOCR. He is joined by O'Connor, Jeffrey A. Hoffman, Gardner and Fisher. Lau works at the FAO console near the CAPCOM console (39265); Harold Black, integrated communications officer (INCO) for STS-8 mans the INCO console during the first TV downlink from the Challengers flight. The payload bay can be seen on the screen in the front of the MOCR (39266).

  2. Views of Mission Control Center during launch of STS-8

    NASA Image and Video Library

    1983-08-30

    Serving as spacecraft communicators (CAPCOM) are Astronauts Guy S. Gardner (left), William F. Fisher (center), Bryan D. O'Connor (seated facing console), and Jeffrey A. Hoffman. Cheevon B. Lau is seated at the flight activities officer (FAO) console to the right of the CAPCOM console. The scene on the large screen in the mission operations control room (MOCR) is a replay of the launch of the Challenger (39264); Flight Director Jay H. Greene, left, watches a replay of the STS-8 launch on the large screen in the MOCR. He is joined by O'Connor, Jeffrey A. Hoffman, Gardner and Fisher. Lau works at the FAO console near the CAPCOM console (39265); Harold Black, integrated communications officer (INCO) for STS-8 mans the INCO console during the first TV downlink from the Challengers flight. The payload bay can be seen on the screen in the front of the MOCR (39266).

  3. SOHO Ultraviolet Coronagraph Spectrometer (UVCS) Mission Operations and Data Analysis

    NASA Technical Reports Server (NTRS)

    Gurman, Joseph (Technical Monitor); Kohl, John L.

    2004-01-01

    The scientific goal of UVCS is to obtain detailed empirical descriptions of the extended solar corona as it evolves over the solar cycle and to use these descriptions to identify and understand the physical processes responsible for coronal heating, solar wind acceleration, coronal mass ejections (CMEs), and the phenomena that establish the plasma properties of the solar wind as measured by "in situ" solar wind instruments. This report covers the period from 15 February 2003 to 14 April 2004. During that time, UVCS observations have consisted of three types: 1) standard synoptic observations comprising, primarily, the H I Lyalpha line profile and the 0 VI 103.2 and 103.7 nm intensity over a range of heights from 1.5 to about 3.0 solar radii and covering 360 degrees about the Sun, 2) sit and stare observations for major flare watches, and 3) special observations designed by the UVCS Lead Observer of the Week for a specific scientific purpose. The special observations are often coordinated with those of other space-based and ground-based instruments and they often are part of SOHO joint observation programs and campaigns. Lead observers have included UVCS Co-Investigators, scientists from the solar physics community and several graduate and undergraduate level students. UVCS has continued to achieve its purpose of using powerful spectroscopic diagnostic techniques to obtain a much more detailed description of coronal structures and dynamic phenomena than existed before the SOHO mission. The new descriptions of coronal mass ejections (CMEs) and coronal structures from UVCS have inspired a large number of theoretical studies aimed at identifying the physical processes responsible for CMEs and solar wind acceleration in coronal holes and streamers. UVCS has proven to be a very stable instrument. Stellar observations have demonstrated its radiometric stability. UVCS has not required any flight software modifications and all mechanisms are operational. The UVCS 0 VI

  4. SOHO Ultraviolet Coronagraph Spectrometer (UVCS) Mission Operations and Data Analysis

    NASA Technical Reports Server (NTRS)

    Kohl, John L.; Gurman, Joseph (Technical Monitor)

    2003-01-01

    The scientific goal of UVCS is to obtain detailed empirical descriptions of the extended solar corona as it evolves over the solar cycle and to use these descriptions to identify and understand the physical processes responsible for coronal heating, solar wind acceleration, coronal mass ejections (CMEs), and the phenomena that establish the plasma properties of the solar wind as measured by 'in situ' solar wind instruments. This report covers the period from 01 February 2002 to 15 February 2003. During that time, UVCS observations have consisted of three types: 1) standard synoptic observations comprising, primarily, the H I Ly alpha line profile and the O VI 103.2 and 103.7 nm intensity over a range of heights from 1.5 to about 3.0 solar radii and covering 360 degrees about the sun, 2) sit and stare watches for CMEs, and 3) special observations designed by the UVCS Lead Observer of the Week for a specific scientific purpose. The special observations are often coordinated with those of other space-based and ground-based instruments and they often are part of SOHO joint observation programs and campaigns. Lead observers have included UVCS Co-Investigators, scientists from the solar physics community and several graduate and undergraduate level students. UVCS has continued to achieve its purpose of using powerful spectroscopic diagnostic techniques to obtain a much more detailed description of coronal structures and dynamic phenomena than existed before the SOHO mission. The new descriptions of coronal mass ejections (CMEs) and coronal structures from UVCS have inspired a large number of theoretical studies aimed at identifying the physical processes responsible for CMEs and solar wind acceleration in coronal holes and streamers. UVCS has proven to be a very stable instrument. Stellar observations have demonstrated its stability. UVCS has required no flight software modifications and all mechanisms are operational. The UVCS O VI Channel with its redundant optical

  5. SPOT4 Operational Control Center (CMP)

    NASA Technical Reports Server (NTRS)

    Zaouche, G.

    1993-01-01

    CNES(F) is responsible for the development of a new generation of Operational Control Center (CMP) which will operate the new heliosynchronous remote sensing satellite (SPOT4). This Operational Control Center takes large benefit from the experience of the first generation of control center and from the recent advances in computer technology and standards. The CMP is designed for operating two satellites all the same time with a reduced pool of controllers. The architecture of this CMP is simple, robust, and flexible, since it is based on powerful distributed workstations interconnected through an Ethernet LAN. The application software uses modern and formal software engineering methods, in order to improve quality and reliability, and facilitate maintenance. This software is table driven so it can be easily adapted to other operational needs. Operation tasks are automated to the maximum extent, so that it could be possible to operate the CMP automatically with very limited human interference for supervision and decision making. This paper provides an overview of the SPOTS mission and associated ground segment. It also details the CMP, its functions, and its software and hardware architecture.

  6. SPOT4 Operational Control Center (CMP)

    NASA Astrophysics Data System (ADS)

    Zaouche, G.

    1993-03-01

    CNES(F) is responsible for the development of a new generation of Operational Control Center (CMP) which will operate the new heliosynchronous remote sensing satellite (SPOT4). This Operational Control Center takes large benefit from the experience of the first generation of control center and from the recent advances in computer technology and standards. The CMP is designed for operating two satellites all the same time with a reduced pool of controllers. The architecture of this CMP is simple, robust, and flexible, since it is based on powerful distributed workstations interconnected through an Ethernet LAN. The application software uses modern and formal software engineering methods, in order to improve quality and reliability, and facilitate maintenance. This software is table driven so it can be easily adapted to other operational needs. Operation tasks are automated to the maximum extent, so that it could be possible to operate the CMP automatically with very limited human interference for supervision and decision making. This paper provides an overview of the SPOTS mission and associated ground segment. It also details the CMP, its functions, and its software and hardware architecture.

  7. Proximity Operations for the Robotic Boulder Capture Option for the Asteroid Redirect Mission

    NASA Technical Reports Server (NTRS)

    Reeves, David M.; Naasz, Bo J.; Wright, Cinnamon A.; Pini, Alex J.

    2014-01-01

    In September of 2013, the Asteroid Robotic Redirect Mission (ARRM) Option B team was formed to expand on NASA's previous work on the robotic boulder capture option. While the original Option A concept focuses on capturing an entire smaller Near-Earth Asteroid (NEA) using an inflatable bag capture mechanism, this design seeks to land on a larger NEA and retrieve a boulder off of its surface. The Option B team has developed a detailed and feasible mission concept that preserves many aspects of Option A's vehicle design while employing a fundamentally different technique for returning a significant quantity of asteroidal material to the Earth-Moon system. As part of this effort, a point of departure proximity operations concept was developed complete with a detailed timeline, as well as DeltaV and propellant allocations. Special attention was paid to the development of the approach strategy, terminal descent to the surface, controlled ascent with the captured boulder, and control during the Enhanced Gravity Tractor planetary defense demonstration. The concept of retrieving a boulder from the surface of an asteroid and demonstrating the Enhanced Gravity Tractor planetary defense technique is found to be feasible and within the proposed capabilities of the Asteroid Redirect Vehicle (ARV). While this point of departure concept initially focuses on a mission to Itokawa, the proximity operations design is also shown to be extensible to wide range of asteroids.

  8. Technical Challenges and Opportunities of Centralizing Space Science Mission Operations (SSMO) at NASA Goddard Space Flight Center

    NASA Technical Reports Server (NTRS)

    Ido, Haisam; Burns, Rich

    2015-01-01

    The NASA Goddard Space Science Mission Operations project (SSMO) is performing a technical cost-benefit analysis for centralizing and consolidating operations of a diverse set of missions into a unified and integrated technical infrastructure. The presentation will focus on the notion of normalizing spacecraft operations processes, workflows, and tools. It will also show the processes of creating a standardized open architecture, creating common security models and implementations, interfaces, services, automations, notifications, alerts, logging, publish, subscribe and middleware capabilities. The presentation will also discuss how to leverage traditional capabilities, along with virtualization, cloud computing services, control groups and containers, and possibly Big Data concepts.

  9. SOHO Ultraviolet Coronagraph Spectrometer (UVCS) Mission Operations and Data Analysis

    NASA Technical Reports Server (NTRS)

    Kohl, John L.; Gurman, Joseph (Technical Monitor)

    2001-01-01

    The scientific goal of UVCS is to obtain detailed empirical descriptions of the extended solar corona as it evolves over the solar cycle and to use these descriptions to identify and understand the physical processes responsible for coronal heating, solar wind acceleration, coronal mass ejections (CMEs), and the phenomena that establish the plasma properties of the solar wind as measured by "in situ" solar wind instruments. This report covers the period from 15 November 1998 to 14 March 2001. During that time, UVCS observations have consisted of three types: 1) standard synoptic observations comprising, primarily, the H I Lycc line profile and the O VI 103.2 and 103.7 nm intensity over a range of heights from 1.5 to about 3.0 solar radii and covering 360 degrees about the sun, 2) sit and stare watches for CMEs, and 3) special observations designed by the UVCS Lead Observer of the Week for a specific scientific purpose. The special observations are often coordinated with those of other space-based and ground based instruments and they often are part of SOHO joint observation programs and campaigns. Lead observers have included UVCS Co-Investigators, Guest Investigators, scientists from the solar physics community and several graduate and undergraduate level students. UVCS has continued to successfully meet its goal of using powerful spectroscopic diagnostic techniques to obtain a much more detailed description of coronal structures than existed before the SOHO mission. The new descriptions of coronal structures from UVCS have inspired a large number of theoretical studies aimed at identifying the physical processes responsible for solar wind acceleration in coronal holes and streamers. UVCS has proven to be a very stable instrument. Stellar observations have demonstrated its stability and the analysis of coordinated observations with Spartan 201 have verified the accuracy of the absolute calibration and spectral resolution at H I Ly (alpha) line profile. UVCS has

  10. SOHO Ultraviolet Coronagraph Spectrometer (UVCS) Mission Operations and Data Analysis

    NASA Technical Reports Server (NTRS)

    Kohl, John L.; Gurman, Joseph (Technical Monitor)

    2001-01-01

    The scientific goal of UVCS is to obtain detailed empirical descriptions of the extended solar corona as it evolves over the solar cycle and to use these descriptions to identify and understand the physical processes responsible for coronal heating, solar wind acceleration, coronal mass ejections (CMEs), and the phenomena that establish the plasma properties of the solar wind as measured by "in situ" solar wind instruments. This report covers the period from 15 November 1998 to 14 March 2001. During that time, UVCS observations have consisted of three types: 1) standard synoptic observations comprising, primarily, the H I Lycc line profile and the O VI 103.2 and 103.7 nm intensity over a range of heights from 1.5 to about 3.0 solar radii and covering 360 degrees about the sun, 2) sit and stare watches for CMEs, and 3) special observations designed by the UVCS Lead Observer of the Week for a specific scientific purpose. The special observations are often coordinated with those of other space-based and ground based instruments and they often are part of SOHO joint observation programs and campaigns. Lead observers have included UVCS Co-Investigators, Guest Investigators, scientists from the solar physics community and several graduate and undergraduate level students. UVCS has continued to successfully meet its goal of using powerful spectroscopic diagnostic techniques to obtain a much more detailed description of coronal structures than existed before the SOHO mission. The new descriptions of coronal structures from UVCS have inspired a large number of theoretical studies aimed at identifying the physical processes responsible for solar wind acceleration in coronal holes and streamers. UVCS has proven to be a very stable instrument. Stellar observations have demonstrated its stability and the analysis of coordinated observations with Spartan 201 have verified the accuracy of the absolute calibration and spectral resolution at H I Ly (alpha) line profile. UVCS has

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

    NASA Technical Reports Server (NTRS)

    Fox, Jason M.; Norris, Jeffrey S.; Powell, Mark W.; Rabe, Kenneth J.; Shams, Khawaja

    2006-01-01

    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.

  12. The Hubble Space Telescope servicing missions: Past, present, and future operational challenges

    NASA Technical Reports Server (NTRS)

    Ochs, William R.; Barbehenn, George M.; Crabb, William G.

    1996-01-01

    The Hubble Space Telescope was designed to be serviced by the Space Shuttle to upgrade systems, replace failed components and boost the telescope into higher orbits. There exists many operational challenges that must be addressed in preparation for the execution of a servicing mission, including technical and managerial issues. The operational challenges faced by the Hubble operations and ground system project for the support of the first servicing mission and future servicing missions, are considered. The emphasis is on those areas that helped ensure the success of the mission, including training, testing and contingency planning.

  13. Wolf signs mission decal in the JEM during Joint Operations

    NASA Image and Video Library

    2009-07-25

    S127-E-008616 (25 July 2009) --- Flight day 11 activities for the joint shuttle-station crews included the traditional autographing of the station. Astronaut Dave Wolf, STS-127 mission specialist, has the pen in this frame.

  14. Marshburn signs mission decal in the JEM during Joint Operations

    NASA Image and Video Library

    2009-07-25

    S127-E-008612 (25 July 2009) --- Flight day 11 activities for the joint shuttle-station crews included the traditional autographing of the station. Astronaut Tom Marshburn, STS-127 mission specialist, has the pen in this frame.

  15. Multi-Agent Modeling and Simulation Approach for Design and Analysis of MER Mission Operations

    NASA Technical Reports Server (NTRS)

    Seah, Chin; Sierhuis, Maarten; Clancey, William J.

    2005-01-01

    A space mission operations system is a complex network of human organizations, information and deep-space network systems and spacecraft hardware. As in other organizations, one of the problems in mission operations is managing the relationship of the mission information systems related to how people actually work (practices). Brahms, a multi-agent modeling and simulation tool, was used to model and simulate NASA's Mars Exploration Rover (MER) mission work practice. The objective was to investigate the value of work practice modeling for mission operations design. From spring 2002 until winter 2003, a Brahms modeler participated in mission systems design sessions and operations testing for the MER mission held at Jet Propulsion Laboratory (JPL). He observed how designers interacted with the Brahms tool. This paper discussed mission system designers' reactions to the simulation output during model validation and the presentation of generated work procedures. This project spurred JPL's interest in the Brahms model, but it was never included as part of the formal mission design process. We discuss why this occurred. Subsequently, we used the MER model to develop a future mission operations concept. Team members were reluctant to use the MER model, even though it appeared to be highly relevant to their effort. We describe some of the tool issues we encountered.

  16. Earth observation mission operation of COMS during in-orbit test

    NASA Astrophysics Data System (ADS)

    Cho, Young-Min

    2011-11-01

    Communication Ocean Meteorological Satellite (COMS) for the hybrid mission of meteorological observation, ocean monitoring, and telecommunication service was launched onto Geostationary Earth Orbit on June 27, 2010 and it is currently under normal operation service after the In-Orbit Test (IOT) phase. The COMS is located on 128.2° East of the geostationary orbit. In order to perform the three missions, the COMS has 3 separate payloads, the meteorological imager (MI), the Geostationary Ocean Color Imager (GOCI), and the Ka-band antenna. Each payload is dedicated to one of the three missions, respectively. The MI and GOCI perform the Earth observation mission of meteorological observation and ocean monitoring, respectively. During the IOT phase the functionality and the performance of many aspects of the COMS satellite and ground station have been checked through the Earth observation mission operation for the observation of the meteorological phenomenon over several areas of the Earth and the monitoring of marine environments around the Korean peninsula. The Earth observation mission operation of COMS during the IOT phase is introduced in terms of mission operation characteristics, mission planning, and mission operation results for the missions of meteorological observation and ocean monitoring, respectively.

  17. Behind the Scenes: Mission Control Practices Launching Discovery

    NASA Image and Video Library

    Before every shuttle launch, the astronauts train with their ascent team in Mission Control Houston. In this episode of NASA Behind the Scenes, astronaut Mike Massimino introduces you to some of th...

  18. School Store Operation and Control.

    ERIC Educational Resources Information Center

    Barger, Bill J.

    Written to assist the teacher-sponsor responsible for operating a school store, this book offers a system developed specifically for the operation and control of such a store. It also shows ways in which a school store can be used for training students. Chapter 1 discusses a successful school store operated by students and a store record system…

  19. Anti-Exposure Technology Identification for Mission Specific Operational Requirements

    DTIC Science & Technology

    1981-08-08

    A-2. Anatomical and Anthropometric Landmarks A-3 NADC-81081-60 SCAPULA BUTTOCK PROTRUSION GLUTEALFURROW WRIST LANDMARK MEDIAL SIDE OF THE...C-1 NADC-81081-60 LIST OF TABLES Tables Page I Fighter/Attack Mission Analysis 5 II Rotary Wing and Fixed Wing Mission Analysis 8 III...Crewmen In Rotary Wing And Fixed Wing Aircraft Photographs Of Configurations Studied Heat Stress Test Sequence Change In TRE (°C) For Actual And

  20. Operational concepts for selected Sortie missions: Executive summary

    NASA Technical Reports Server (NTRS)

    Dulock, V. A., Jr.

    1974-01-01

    An executive summary is presented of a Spacelab concept study conducted from August 1973 to June 1974. Background information and a summary of study conclusions are given. Specific data are reported for the quick-reaction carrier concept, software and mission integration, configuration management, documentation, equipment pool, and integration alternatives. A forecast of the impact of a second launch site, mission feasibility, and space availability for the Spacelab are also discussed.