Science.gov

Sample records for mission operations interoperability

  1. 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

  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. Challenges of Space Mission Interoperability

    NASA Technical Reports Server (NTRS)

    Martin, Warren L.; Hooke, Adrian J.

    2007-01-01

    This viewgraph presentation reviews some of the international challenges to space mission interoperability. Interoperability is the technical capability of two or more systems or components to exchange information and to use the information that has been exchanged. One of the challenges that is addressed is the problem of spectrum bandwidth, and interference. The key to interoperability is the standardization of space communications services and protocols. Various levels of international cross support are reviewed: harmony, cooperation cross support and confederation cross support. The various international bodies charged with implementing cross support are reviewed. The goal of the Interagency Operations Advisory Group (IOAG) is to achieve plug-and-play operations where all that is required is for each of the systems to use an agreed communications medium, after which the systems configure each other for the purpose of exchanging information and subsequently effect such exchange automatically.

  4. Challenges of Space Mission Interoperability

    NASA Technical Reports Server (NTRS)

    Martin, Warren L.; Hooke, Adrian J.

    2007-01-01

    This viewgraph presentation reviews some of the international challenges to space mission interoperability. Interoperability is the technical capability of two or more systems or components to exchange information and to use the information that has been exchanged. One of the challenges that is addressed is the problem of spectrum bandwidth, and interference. The key to interoperability is the standardization of space communications services and protocols. Various levels of international cross support are reviewed: harmony, cooperation cross support and confederation cross support. The various international bodies charged with implementing cross support are reviewed. The goal of the Interagency Operations Advisory Group (IOAG) is to achieve plug-and-play operations where all that is required is for each of the systems to use an agreed communications medium, after which the systems configure each other for the purpose of exchanging information and subsequently effect such exchange automatically.

  5. 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.

  6. 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.

  7. Interoperability and Combined Operations.

    DTIC Science & Technology

    1981-06-15

    34Organization for Joint Operations," MIL RVW, 32:32-39, Feb 1953. Collins, Joseph L. "Building Strength for Western Defense," AID, 9:3-8, Jul 1954...34 MIL RVW, 26:3-9, Aug 1946; 26:10-16, Sep 1946. Johnston, Joseph W. "Combined Operations in Lower Units," MIL RVW, 32:56-62, Jul 1952. Lenschau...1950. Postlethwait, Edward M. "Unified Command in Theaters of Operations," MIL RVW, 29:23-30, Nov 1949. Priestley , H. "Let’s Stick Together," MIL RVW

  8. 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.

  9. Turning Interoperability Operational with GST

    NASA Astrophysics Data System (ADS)

    Schaeben, Helmut; Gabriel, Paul; Gietzel, Jan; Le, Hai Ha

    2013-04-01

    GST - Geosciences in space and time is being developed and implemented as hub to facilitate the exchange of spatially and temporally indexed multi-dimensional geoscience data and corresponding geomodels amongst partners. It originates from TUBAF's contribution to the EU project "ProMine" and its perspective extensions are TUBAF's contribution to the actual EU project "GeoMol". As of today, it provides basic components of a geodata infrastructure as required to establish interoperability with respect to geosciences. Generally, interoperability means the facilitation of cross-border and cross-sector information exchange, taking into account legal, organisational, semantic and technical aspects, cf. Interoperability Solutions for European Public Administrations (ISA), cf. http://ec.europa.eu/isa/. Practical interoperability for partners of a joint geoscience project, say European Geological Surveys acting in a border region, means in particular provision of IT technology to exchange spatially and maybe additionally temporally indexed multi-dimensional geoscience data and corresponding models, i.e. the objects composing geomodels capturing the geometry, topology, and various geoscience contents. Geodata Infrastructure (GDI) and interoperability are objectives of several inititatives, e.g. INSPIRE, OneGeology-Europe, and most recently EGDI-SCOPE to name just the most prominent ones. Then there are quite a few markup languages (ML) related to geographical or geological information like GeoSciML, EarthResourceML, BoreholeML, ResqML for reservoir characterization, earth and reservoir models, and many others featuring geoscience information. Several Web Services are focused on geographical or geoscience information. The Open Geospatial Consortium (OGC) promotes specifications of a Web Feature Service (WFS), a Web Map Service (WMS), a Web Coverage Serverice (WCS), a Web 3D Service (W3DS), and many more. It will be clarified how GST is related to these initiatives, especially

  10. Interoperability.

    PubMed

    Jarvis, Dennis H; Jarvis, Jacqueline H

    2010-01-01

    This chapter gives an educational overview of: * the roles that ontology and process play in interoperability * the processes that can be employed to realise interoperability and their supporting technologies * interoperability solutions employed in the health informatics sector within the conceptual model presented in the chapter * directions for future research in the area of interoperability for health informatics.

  11. 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.

  12. Operational Interoperability Challenges on the Example of GEOSS and WIS

    NASA Astrophysics Data System (ADS)

    Heene, M.; Buesselberg, T.; Schroeder, D.; Brotzer, A.; Nativi, S.

    2015-12-01

    The following poster highlights the operational interoperability challenges on the example of Global Earth Observation System of Systems (GEOSS) and World Meteorological Organization Information System (WIS). At the heart of both systems is a catalogue of earth observation data, products and services but with different metadata management concepts. While in WIS a strong governance with an own metadata profile for the hundreds of thousands metadata records exists, GEOSS adopted a more open approach for the ten million records. Furthermore, the development of WIS - as an operational system - follows a roadmap with committed downwards compatibility while the GEOSS development process is more agile. The poster discusses how the interoperability can be reached for the different metadata management concepts and how a proxy concept helps to couple two different systems which follow a different development methodology. Furthermore, the poster highlights the importance of monitoring and backup concepts as a verification method for operational interoperability.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. Distributed Operating Systems Interoperability Research Project

    DTIC Science & Technology

    1990-05-01

    determined by its frequency of use and the scale of the information. Local area network experiments in Locus and Cronus have demonstrated that...operations, implemented in the Cronus DOS as invocations on a generic object. Each manager of a set of objects of a type implements a generic object. The...rights identifiers (VMS). the system (VMS), world, and an arbitrary set of groups ( Cronus ). Using an arbitrary set of groups that can be enabled and

  18. 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.

  19. USAF Distributed Mission Operations, an ADF Synthetic Range Interoperability Model and an AOD Mission Training Centre Capability Concept Demonstrator - What are They and Why Does the RAAF Need Them

    DTIC Science & Technology

    2010-10-01

    out various live “Flag” training exercises (Red Flag, Green Flag, Blue Flag, etc.) on various training ranges with various components of the USAF and...2.3.4) in both training and simulation environments [ Gustavsson ] include:  Extended Air Defence Simulation - Several types of real operational...Sweden, June 2006, 06E-SIW-050. [ Gustavsson ] - Gustavsson , Per M., Bjorkman, U., and Wemmergard, Joakim., (2009), “LVC Aspects and Integration of

  20. Watershed and Economic Data InterOperability (WEDO) ...

    EPA Pesticide Factsheets

    Watershed and Economic Data InterOperability (WEDO) is a system of information technologies designed to publish watershed modeling studies for reuse. WEDO facilitates three aspects of interoperability: discovery, evaluation and integration of data. This increased level of interoperability goes beyond the current practice of publishing modeling studies as reports or journal articles. Rather than summarized results, modeling studies can be published with their full complement of input data, calibration parameters and output with associated metadata for easy duplication by others. Reproducible science is possible only if researchers can find, evaluate and use complete modeling studies performed by other modelers. WEDO greatly increases transparency by making detailed data available to the scientific community.WEDO is a next generation technology, a Web Service linked to the EPA’s EnviroAtlas for discovery of modeling studies nationwide. Streams and rivers are identified using the National Hydrography Dataset network and stream IDs. Streams with modeling studies available are color coded in the EnviroAtlas. One can select streams within a watershed of interest to readily find data available via WEDO. The WEDO website is linked from the EnviroAtlas to provide a thorough review of each modeling study. WEDO currently provides modeled flow and water quality time series, designed for a broad range of watershed and economic models for nutrient trading market analysis. M

  1. Operational Plan Ontology Model for Interconnection and Interoperability

    NASA Astrophysics Data System (ADS)

    Long, F.; Sun, Y. K.; Shi, H. Q.

    2017-03-01

    Aiming at the assistant decision-making system’s bottleneck of processing the operational plan data and information, this paper starts from the analysis of the problem of traditional expression and the technical advantage of ontology, and then it defines the elements of the operational plan ontology model and determines the basis of construction. Later, it builds up a semi-knowledge-level operational plan ontology model. Finally, it probes into the operational plan expression based on the operational plan ontology model and the usage of the application software. Thus, this paper has the theoretical significance and application value in the improvement of interconnection and interoperability of the operational plan among assistant decision-making systems.

  2. Interoperability Trends in Extravehicular Activity (EVA) Space Operations for the 21st Century

    NASA Technical Reports Server (NTRS)

    Miller, Gerald E.

    1999-01-01

    No other space operations in the 21 st century more comprehensively embody the challenges and dependencies of interoperability than EVA. This discipline is already functioning at an W1paralleled level of interagency, inter-organizational and international cooperation. This trend will only increase as space programs endeavor to expand in the face of shrinking budgets. Among the topics examined in this paper are hardware-oriented issues. Differences in design standards among various space participants dictate differences in the EVA tools that must be manufactured, flown and maintained on-orbit. Presently only two types of functional space suits exist in the world. However, three versions of functional airlocks are in operation. Of the three airlocks, only the International Space Station (ISS) Joint Airlock can accommodate both types of suits. Due to functional differences in the suits, completely different operating protocols are required for each. Should additional space suit or airlock designs become available, the complexity will increase. The lessons learned as a result of designing and operating within such a system are explored. This paper also examines the non-hardware challenges presented by interoperability for a discipline that is as uniquely dependent upon the individual as EVA. Operation of space suits (essentially single-person spacecrafts) by persons whose native language is not that of the suits' designers is explored. The intricacies of shared mission planning, shared control and shared execution of joint EVA's are explained. For example, once ISS is fully functional, the potential exists for two crewmembers of different nationality to be wearing suits manufactured and controlled by a third nation, while operating within an airlock manufactured and controlled by a fourth nation, in an effort to perform tasks upon hardware belonging to a fifth nation. Everything from training issues, to procedures development and writing, to real-time operations is

  3. 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.

  4. 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.

  5. 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.

  6. Inter-Operator Spectrum Sharing from a Game Theoretical Perspective

    NASA Astrophysics Data System (ADS)

    Bennis, Mehdi; Lasaulce, Samson; Debbah, Merouane

    2009-12-01

    We address the problem of spectrum sharing where competitive operators coexist in the same frequency band. First, we model this problem as a strategic non-cooperative game where operators simultaneously share the spectrum according to the Nash Equilibrium (NE). Given a set of channel realizations, several Nash equilibria exist which renders the outcome of the game unpredictable. Then, in a cognitive context with the presence of primary and secondary operators, the inter-operator spectrum sharing problem is reformulated as a Stackelberg game using hierarchy where the primary operator is the leader. The Stackelberg Equilibrium (SE) is reached where the best response of the secondary operator is taken into account upon maximizing the primary operator's utility function. Moreover, an extension to the multiple operators spectrum sharing problem is given. It is shown that the Stackelberg approach yields better payoffs for operators compared to the classical water-filling approach. Finally, we assess the goodness of the proposed distributed approach by comparing its performance to the centralized approach.

  7. The National Flood Interoperability Experiment: Bridging Resesarch and Operations

    NASA Astrophysics Data System (ADS)

    Salas, F. R.

    2015-12-01

    The National Weather Service's new National Water Center, located on the University of Alabama campus in Tuscaloosa, will become the nation's hub for comprehensive water resources forecasting. In conjunction with its federal partners the US Geological Survey, Army Corps of Engineers and Federal Emergency Management Agency, the National Weather Service will operationally support both short term flood prediction and long term seasonal forecasting of water resource conditions. By summer 2016, the National Water Center will begin evaluating four streamflow data products at the scale of the NHDPlus river reaches (approximately 2.67 million). In preparation for the release of these products, from September 2014 to August 2015, the National Weather Service partnered with the Consortium of Universities for the Advancement of Hydrologic Science, Inc. to support the National Flood Interoperability Experiment which included a seven week in-residence Summer Institute in Tuscaloosa for university students interested in learning about operational hydrology and flood forecasting. As part of the experiment, 15 hour forecasts from the operational High Resolution Rapid Refresh atmospheric model were used to drive a three kilometer Noah-MP land surface model loosely coupled to a RAPID river routing model operating on the NHDPlus dataset. This workflow was run every three hours during the Summer Institute and the results were made available to those engaged to pursue a range of research topics focused on flood forecasting (e.g. reservoir operations, ensemble forecasting, probabilistic flood inundation mapping, rainfall product evaluation etc.) Although the National Flood Interoperability Experiment was finite in length, it provided a platform through which the academic community could engage federal agencies and vice versa to narrow the gap between research and operations and demonstrate how state of the art research infrastructure, models, services, datasets etc. could be utilized

  8. Digital Motion Imagery, Interoperability Challenges for Space Operations

    NASA Technical Reports Server (NTRS)

    Grubbs, Rodney

    2012-01-01

    With advances in available bandwidth from spacecraft and between terrestrial control centers, digital motion imagery and video is becoming more practical as a data gathering tool for science and engineering, as well as for sharing missions with the public. The digital motion imagery and video industry has done a good job of creating standards for compression, distribution, and physical interfaces. Compressed data streams can easily be transmitted or distributed over radio frequency, internet protocol, and other data networks. All of these standards, however, can make sharing video between spacecraft and terrestrial control centers a frustrating and complicated task when different standards and protocols are used by different agencies. This paper will explore the challenges presented by the abundance of motion imagery and video standards, interfaces and protocols with suggestions for common formats that could simplify interoperability between spacecraft and ground support systems. Real-world examples from the International Space Station will be examined. The paper will also discuss recent trends in the development of new video compression algorithms, as well likely expanded use of Delay (or Disruption) Tolerant Networking nodes.

  9. 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.

  10. OTF CCSDS Mission Operations Prototype. Directory and Action 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 describes the phase I directory and action service prototype for the CCSDS system. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement Directory and Action Services (2) Investigate Mission Operations language neutrality (3) Investigate C3I XML interoperability concepts (4) Integrate applicable open source technologies in a Service Oriented Architecture

  11. 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.

  12. 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.

  13. Watershed and Economic Data InterOperability (WEDO): Facilitating Discovery, Evaluation and Integration through the Sharing of Watershed Modeling Data

    EPA Science Inventory

    Watershed and Economic Data InterOperability (WEDO) is a system of information technologies designed to publish watershed modeling studies for reuse. WEDO facilitates three aspects of interoperability: discovery, evaluation and integration of data. This increased level of interop...

  14. 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...

  15. 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

  16. 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.

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  1. 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.

  2. 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.

  3. Maritime In Situ Sensing Inter-Operable Networks (MISSION)

    DTIC Science & Technology

    2013-09-30

    reflective coral reefs, tidal currents, shipping, and impulsive biological noise from snapping shrimp . NUS has developed underwater modems that have... shrimp dominated ambient noise environments,” Proc. Acoustics 2012 Hong Kong, vol. 131, p. 3277, May 2012 [4] J. Rice, C. Fletcher, B. Creber, B...September 24-27, 2012 [17] A. Mahmood, M. Chitre, and M. Armand, “Improving PSK performance in snapping shrimp noise with rotated constellations

  4. 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.

  5. 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.

  6. 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.

  7. Efficiency Analysis of an Interoperable Healthcare Operations Platform.

    PubMed

    Osborne, Thomas F; Clark, Reese H; Blackowiak, Jason; Williamson, Patrick J; Werb, Shannon M; Strong, Benjamin W

    2017-04-01

    (1) Develop an enterprise platform to unify isolated information, software applications and team members. (2) Assess the efficiency of one benefit of the platform through comparative testing of employee document retrieval times. (3) Evaluate the level of satisfaction among our target audience. We developed an infrastructure to integrate information throughout our practice and make it available on a unified, secure, and remotely accessible platform. We solicited our practice for volunteers to test the new system. All interested volunteers participated. Thirteen employees searched for the same four items in both the new system and our legacy systems. Testing was performed in the pre-deployment stage. In our evaluation, we introduced an innovative method to precisely and objectively obtain data through the use of a widely available tool which could be leveraged for a variety of other studies. On average, it took our participants 7 min and 48 s to find four assigned items in our legacy systems. It only took our volunteers 1 min and 1 s to find the same items with the new platform (p-value 0.002). On a scale of 10 being the highest level of satisfaction, participants ranked the new system to be 8.7 while the traditional system was ranked at 6.3. An overarching enterprise platform is critical due to the ability to unify otherwise isolated applications, people and documents. Because navigating a new system would be expected to take longer than a familiar one, we were surprised by the dramatically improved efficiency and satisfaction of our new interoperable platform compared to the status quo. Since this platform was evaluated in the pre-deployment stage, we expect results to improve with employee experience as well as ongoing enhancements.

  8. 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.

  9. In vivo evaluation of inter-operator reproducibility of digital dental and conventional impression techniques

    PubMed Central

    Kamimura, Emi; Tanaka, Shinpei; Takaba, Masayuki; Tachi, Keita; Baba, Kazuyoshi

    2017-01-01

    Purpose The aim of this study was to evaluate and compare the inter-operator reproducibility of three-dimensional (3D) images of teeth captured by a digital impression technique to a conventional impression technique in vivo. Materials and methods Twelve participants with complete natural dentition were included in this study. A digital impression of the mandibular molars of these participants was made by two operators with different levels of clinical experience, 3 or 16 years, using an intra-oral scanner (Lava COS, 3M ESPE). A silicone impression also was made by the same operators using the double mix impression technique (Imprint3, 3M ESPE). Stereolithography (STL) data were directly exported from the Lava COS system, while STL data of a plaster model made from silicone impression were captured by a three-dimensional (3D) laboratory scanner (D810, 3shape). The STL datasets recorded by two different operators were compared using 3D evaluation software and superimposed using the best-fit-algorithm method (least-squares method, PolyWorks, InnovMetric Software) for each impression technique. Inter-operator reproducibility as evaluated by average discrepancies of corresponding 3D data was compared between the two techniques (Wilcoxon signed-rank test). Results The visual inspection of superimposed datasets revealed that discrepancies between repeated digital impression were smaller than observed with silicone impression. Confirmation was forthcoming from statistical analysis revealing significantly smaller average inter-operator reproducibility using a digital impression technique (0.014± 0.02 mm) than when using a conventional impression technique (0.023 ± 0.01 mm). Conclusion The results of this in vivo study suggest that inter-operator reproducibility with a digital impression technique may be better than that of a conventional impression technique and is independent of the clinical experience of the operator. PMID:28636642

  10. 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.

  11. 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).

  12. 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).

  13. Buildings Interoperability Landscape

    SciTech Connect

    Hardin, Dave; Stephan, Eric G.; Wang, Weimin; Corbin, Charles D.; Widergren, Steven E.

    2015-12-31

    Through its Building Technologies Office (BTO), the United States Department of Energy’s Office of Energy Efficiency and Renewable Energy (DOE-EERE) is sponsoring an effort to advance interoperability for the integration of intelligent buildings equipment and automation systems, understanding the importance of integration frameworks and product ecosystems to this cause. This is important to BTO’s mission to enhance energy efficiency and save energy for economic and environmental purposes. For connected buildings ecosystems of products and services from various manufacturers to flourish, the ICT aspects of the equipment need to integrate and operate simply and reliably. Within the concepts of interoperability lie the specification, development, and certification of equipment with standards-based interfaces that connect and work. Beyond this, a healthy community of stakeholders that contribute to and use interoperability work products must be developed. On May 1, 2014, the DOE convened a technical meeting to take stock of the current state of interoperability of connected equipment and systems in buildings. Several insights from that meeting helped facilitate a draft description of the landscape of interoperability for connected buildings, which focuses mainly on small and medium commercial buildings. This document revises the February 2015 landscape document to address reviewer comments, incorporate important insights from the Buildings Interoperability Vision technical meeting, and capture thoughts from that meeting about the topics to be addressed in a buildings interoperability vision. In particular, greater attention is paid to the state of information modeling in buildings and the great potential for near-term benefits in this area from progress and community alignment.

  14. 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.

  15. 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.

  16. Watershed and Economic Data InterOperability (WEDO)??

    EPA Science Inventory

    The annual public meeting of the Federal Interagency Steering Committee on Multimedia Environmental Modeling (ISCMEM) will convene to discuss some of the latest developments in environmental modeling applications, tools and frameworks, as well as new operational initiatives for F...

  17. Watershed and Economic Data InterOperability (WEDO)??

    EPA Science Inventory

    The annual public meeting of the Federal Interagency Steering Committee on Multimedia Environmental Modeling (ISCMEM) will convene to discuss some of the latest developments in environmental modeling applications, tools and frameworks, as well as new operational initiatives for F...

  18. Functional C3 Interoperability Architecture for Air Operations

    DTIC Science & Technology

    1991-08-20

    prevent effective joint operations. JTC3A developed this architecture after a review and analysis of joint and service documentation and discussions with...unified, component command, and service staff personnel. An interim report, referred to as the supporting analysis , was previously distributed for...service comment and provides extensive supplemental information on C3 for joint air operations. The supporting analysis will be available as soon as it is

  19. 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.

  20. Interoperability framework for communication between processes running on different mobile operating systems

    NASA Astrophysics Data System (ADS)

    Gal, A.; Filip, I.; Dragan, F.

    2016-02-01

    As we live in an era where mobile communication is everywhere around us, the necessity to communicate between the variety of the devices we have available becomes even more of an urge. The major impediment to be able to achieve communication between the available devices is the incompatibility between the operating systems running on these devices. In the present paper we propose a framework that will make possible the ability to inter-operate between processes running on different mobile operating systems. The interoperability process will make use of any communication environment which is made available by the mobile devices where the processes are installed. The communication environment is chosen so as the process is optimal in terms of transferring the data between the mobile devices. The paper defines the architecture of the framework, expanding the functionality and interrelation between modules that make up the framework. For the proof of concept, we propose to use three different mobile operating systems installed on three different types of mobile devices. Depending on the various factors related to the structure of the mobile devices and the data type to be transferred, the framework will establish a data transfer protocol that will be used. The framework automates the interoperability process, user intervention being limited to a simple selection from the options that the framework suggests based on the full analysis of structural and functional elements of the mobile devices used in the process.

  1. 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).

  2. Making Stability Operations Less Complex While Improving Interoperability

    DTIC Science & Technology

    2008-06-01

    doctrine, organizations, training, education , exercises, materiel, leadership, personnel, facilities, and planning.” 3 “Stabil- ity operations are...is never context free, there are always aspects of community, culture, cognitive skills and technology evident. Accordingly, educational , cultural...Information sharing among systems is accomplished through interfaces with well-defined protocols, business rules and semantics (e.g., WSDL, SOAP and

  3. 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.

  4. 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.

  5. 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.

  6. Inter-operator and inter-device agreement and reliability of the SEM Scanner.

    PubMed

    Clendenin, Marta; Jaradeh, Kindah; Shamirian, Anasheh; Rhodes, Shannon L

    2015-02-01

    The SEM Scanner is a medical device designed for use by healthcare providers as part of pressure ulcer prevention programs. The objective of this study was to evaluate the inter-rater and inter-device agreement and reliability of the SEM Scanner. Thirty-one (31) volunteers free of pressure ulcers or broken skin at the sternum, sacrum, and heels were assessed with the SEM Scanner. Each of three operators utilized each of three devices to collect readings from four anatomical sites (sternum, sacrum, left and right heels) on each subject for a total of 108 readings per subject collected over approximately 30 min. For each combination of operator-device-anatomical site, three SEM readings were collected. Inter-operator and inter-device agreement and reliability were estimated. Over the course of this study, more than 3000 SEM Scanner readings were collected. Agreement between operators was good with mean differences ranging from -0.01 to 0.11. Inter-operator and inter-device reliability exceeded 0.80 at all anatomical sites assessed. The results of this study demonstrate the high reliability and good agreement of the SEM Scanner across different operators and different devices. Given the limitations of current methods to prevent and detect pressure ulcers, the SEM Scanner shows promise as an objective, reliable tool for assessing the presence or absence of pressure-induced tissue damage such as pressure ulcers. Copyright © 2015 Bruin Biometrics, LLC. Published by Elsevier Ltd.. All rights reserved.

  7. 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.

  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. 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).

  9. 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).

  10. 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 ...

  11. 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.

  12. 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.

  13. 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

  14. 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

  15. 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.

  16. 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.

  17. 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.

  18. 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.

  19. 3D facial landmarks: Inter-operator variability of manual annotation.

    PubMed

    Fagertun, Jens; Harder, Stine; Rosengren, Anders; Moeller, Christian; Werge, Thomas; Paulsen, Rasmus R; Hansen, Thomas F

    2014-10-11

    Manual annotation of landmarks is a known source of variance, which exist in all fields of medical imaging, influencing the accuracy and interpretation of the results. However, the variability of human facial landmarks is only sparsely addressed in the current literature as opposed to e.g. the research fields of orthodontics and cephalometrics. We present a full facial 3D annotation procedure and a sparse set of manually annotated landmarks, in effort to reduce operator time and minimize the variance. Facial scans from 36 voluntary unrelated blood donors from the Danish Blood Donor Study was randomly chosen. Six operators twice manually annotated 73 anatomical and pseudo-landmarks, using a three-step scheme producing a dense point correspondence map. We analyzed both the intra- and inter-operator variability, using mixed-model ANOVA. We then compared four sparse sets of landmarks in order to construct a dense correspondence map of the 3D scans with a minimum point variance. The anatomical landmarks of the eye were associated with the lowest variance, particularly the center of the pupils. Whereas points of the jaw and eyebrows have the highest variation. We see marginal variability in regards to intra-operator and portraits. Using a sparse set of landmarks (n=14), that capture the whole face, the dense point mean variance was reduced from 1.92 to 0.54 mm. The inter-operator variability was primarily associated with particular landmarks, where more leniently landmarks had the highest variability. The variables embedded in the portray and the reliability of a trained operator did only have marginal influence on the variability. Further, using 14 of the annotated landmarks we were able to reduced the variability and create a dense correspondences mesh to capture all facial features.

  20. 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

  7. 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

  8. 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.

  9. 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

  10. 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.

  11. 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.

  12. 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.

  13. 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

  14. 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.

  15. Inter-operator variability in perfusion assessment of tumors in MRI using automated AIF detection.

    PubMed

    Ashton, Edward; McShane, Teresa; Evelhoch, Jeffrey

    2005-01-01

    A method is presented for the calculation of perfusion parameters in dynamic contrast enhanced MRI. This method requires identification of enhancement curves for both tumor tissue and plasma. Inter-operator variability in the derived rate constant between plasma and extra-cellular extra-vascular space is assessed in both canine and human subjects using semi-automated tumor margin identification with both manual and automated arterial input function (AIF) identification. Experimental results show a median coefficient of variability (CV) for parameter measurement with manual AIF identification of 21.5% in canines and 11% in humans, with a median CV for parameter measurement with automated AIF identification of 6.7% in canines and 6% in humans.

  16. 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.

  17. Proposed Interoperability Readiness Level Assessment for Mission Critical Interfaces During Navy Acquisition

    DTIC Science & Technology

    2010-12-01

    Figure 27. Milestone Evaluation Criteria ...........................................................................87 Figure 28. Communications ... community . Furthermore, requirements that are critical to mission success are not being identified in the current SE process, and allocations or...sample system for the TTX because it has many internal and external interfaces used for communication . The audio and visual communication between

  18. The JSpOC Mission System (JMS) Common Data Model: Foundation for Net-Centric Interoperability for Space Situational Awareness

    NASA Astrophysics Data System (ADS)

    Hutchison, M.; Kolarik, K.; Waters, J.

    2012-09-01

    The space situational awareness (SSA) data we access and use through existing SSA systems is largely provided in formats which cannot be readily understood by other systems (SSA or otherwise) without translation. As a result, while the data is useful for some known set of users, for other users it is not discoverable (no way to know it is there), accessible (if you did know, there is no way to electronically obtain the data) or machine-understandable (even if you did have access, the data exists in a format which cannot be readily ingested by your existing systems). Much of this existing data is unstructured, stored in non-standard formats which feed legacy systems. Data terms are not always unique, and calculations performed using legacy functions plugged into a service-oriented backbone can produce inconsistent results. The promise of data which is interoperable across systems and applications depends on a common data model as an underlying foundation for sharing information on a machine-to-machine basis. M2M interoperability is fundamental to performance, reducing or eliminating time-consuming translation and accelerating delivery to end users for final expert human analysis in support of mission fulfillment. A data model is common when it can be used by multiple programs and projects within a domain (e.g., C2 SSA). Model construction begins with known requirements and includes the development of conceptual and logical representations of the data. The final piece of the model is an implementable physical representation (e.g., XML schema) which can be used by developers to build working software components and systems. The JMS Common Data Model v1.0 was derived over six years from the National SSA Mission Threads under the direction of AFSPC/A5CN. The subsequent model became the A5CN approved JMS Requirements Model. The resulting logical and physical models have been registered in the DoD Metadata Registry under the C2 SSA Namespace and will be made available

  19. Operational Lessons Learned from NASA Analog Missions

    NASA Technical Reports Server (NTRS)

    Arnold, Larissa S.

    2010-01-01

    National Aeronautics and Space Administration s (NASA) efforts in human space flight are currently focused on the Space Shuttle and International Space Station (ISS) programs, with efforts beginning on the future exploration opportunities. Both the Space Shuttle and ISS programs are important to the development of a capability for human exploration beyond Low Earth Orbit (LEO). The ISS provides extensive research capabilities to determine how the human body reacts to long duration stays in space. Also, the ISS and Shuttle can serve as a limited testbed for equipment or entire systems that may be used on missions to the Moon, Mars, or to a near-Earth asteroid. It has been nearly 35 years since the Apollo astronauts visited the Moon. Future space explorers will have to re-learn how to work and live on planetary surfaces, and how to do that for extended periods of time. Exploration crews will perform a wide assortment of scientific tasks, including material sampling and emplacement of automated instruments. Surface mission operations include the activities of the crew living and working, mission support from the Earth, and the operation of robotic and other remotely commanded equipment on the surface and in planetary orbit. Other surface activities will include the following: exploring areas surrounding a habitat; using rovers to collect rock and soil samples; setting up experiments on the surface to monitor the radiation environment and any seismic or thermal activity; and conducting scientific analyses and experiments inside a habitat laboratory. Of course, the astronauts will also have to spend some of their surface time "doing chores" and maintaining their habitat and other systems. In preparation for future planetary exploration, NASA must design the answers to many operational questions. What will the astronauts do on the surface? How will they accomplish this? What tools will they require for their tasks? How will robots and astronauts work together? What

  20. COTS-based OO-component approach for software inter-operability and reuse (software systems engineering methodology)

    NASA Technical Reports Server (NTRS)

    Yin, J.; Oyaki, A.; Hwang, C.; Hung, C.

    2000-01-01

    The purpose of this research and study paper is to provide a summary description and results of rapid development accomplishments at NASA/JPL in the area of advanced distributed computing technology using a Commercial-Off--The-Shelf (COTS)-based object oriented component approach to open inter-operable software development and software reuse.

  1. COTS-based OO-component approach for software inter-operability and reuse (software systems engineering methodology)

    NASA Technical Reports Server (NTRS)

    Yin, J.; Oyaki, A.; Hwang, C.; Hung, C.

    2000-01-01

    The purpose of this research and study paper is to provide a summary description and results of rapid development accomplishments at NASA/JPL in the area of advanced distributed computing technology using a Commercial-Off--The-Shelf (COTS)-based object oriented component approach to open inter-operable software development and software reuse.

  2. 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.

  3. 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.}

  4. 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.

  5. 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.

  6. 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.

  7. 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

  8. 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.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. Offline Interoperability, Cost Reduction and R eliability for Operational Procedures Using Meta-Modeling Technology

    NASA Astrophysics Data System (ADS)

    Poupart, E.; Jolly, G.; Percebois, C.; Bazex, P.; Palanque, P.; Basnyat, S.; Rabault, P.; Sabatier, L.; Walrawens, A.

    2008-08-01

    In this paper, we present a CNES participation through a case study in a research project called DOMINO financed by the French National Research Agency (ANR) RNTL. This project has started in March 2007 and will end in March 2009, it regroups academics (ENSIETA, IRISA, and IRIT), industries and agencies, (AIRBUS, CEA, CNES and SODIFRANCE). This project has two main goals: to develop reliable Model Driven Engineering (MDE) components and to build bridges with Domain Specific Languages (DSL). CNES participates in this project through a case study on the reliable design of operational procedures and associated applications. There are two main objectives for this case study: the first to improve "offline" interoperability with the possibility to build import/export tools for any scripting procedure language by using meta-modeling technology. The second is to improve efficiency for the production, validation, and execution of scripting procedures using operational specifications. It is anticipated that this will result in a reduction of costs and reliability improvement.

  15. 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.

  16. Kosovo Armed Forces Development; Achieving NATO Non-Article 5 Crisis Response Operations Interoperability

    DTIC Science & Technology

    2014-12-12

    Intercultural Factors. ................................................................................................. 27 Allied Administrative...leaders to be competent , reliable, suitable and ready to accomplish the mission.32 This document further explains duties and responsibilities of unit...Multinational Military Operations and Intercultural Factors, NATO Standard Allied Administrative Publication (AAP) 47 Allied Joint Doctrine Development, NATO

  17. 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.

  18. Wireless Network Communications Overview for Space Mission Operations

    NASA Technical Reports Server (NTRS)

    Fink, Patrick W.

    2009-01-01

    The mission of the On-Board Wireless Working Group (WWG) is to serve as a general CCSDS focus group for intra-vehicle wireless technologies. The WWG investigates and makes recommendations pursuant to standardization of applicable wireless network protocols, ensuring the interoperability of independently developed wireless communication assets. This document presents technical background information concerning uses and applicability of wireless networking technologies for space missions. Agency-relevant driving scenarios, for which wireless network communications will provide a significant return-on-investment benefiting the participating international agencies, are used to focus the scope of the enclosed technical information.

  19. 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.

  20. 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. The Italian Cloud-based brokering Infrastructure to sustain Interoperability for Operative Hydrology

    NASA Astrophysics Data System (ADS)

    Boldrini, E.; Pecora, S.; Bussettini, M.; Bordini, F.; Nativi, S.

    2015-12-01

    This work presents the informatics platform carried out to implement the National Hydrological Operative Information System of Italy. In particular, the presentation will focus on the governing aspects of the cloud infrastructure and brokering software that make possible to sustain the hydrology data flow between heterogeneous user clients and data providers.The Institute for Environmental Protection and Research, ISPRA (Istituto Superiore per la Protezione e la Ricerca Ambientale) in collaboration with the Regional Agency for Environmental Protection in the Emilia-Romagna region, ARPA-ER (Agenzia Regionale per la Prevenzione e l´Ambiente dell´Emilia-Romagna) and CNR-IIA (National Research Council of Italy) designed and developed an innovative platform for the discovery and access of hydrological data coming from 19 Italian administrative regions and 2 Italian autonomous provinces, in near real time. ISPRA has deployed and governs such a system. The presentation will introduce and discuss the technological barriers for interoperability as well as social and policy ones. The adopted solutions will be described outlining the sustainability challenges and benefits.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  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. 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

  18. 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

  19. 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

  20. 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.

  1. 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).

  2. 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).

  3. 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.

  4. 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

  5. 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

  6. The Challenges Associated with Achieving Interoperability in Support of Net-Centric Operations

    DTIC Science & Technology

    2005-06-01

    such, it adopts a perspective that is reflective of the viewpoints of a computer scientist/system engineer . Recent initiatives are seeking to build...role in addressing short term interoperability issues. • Longer Term Acquisitions. The Joint Distributed Engineering Plant (JDEP) program is...www.cwid.js.mil/c/extranet/home). 32. Joint Distributed Engineering Plant (JDEP) (accessible at http://in.disa.mil/jdep.html). 33. Adm. Giambastiani

  7. 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.

  8. 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.

  9. 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.

  10. Ambulatory measurement of the scapulohumeral rhythm: intra- and inter-operator agreement of a protocol based on inertial and magnetic sensors.

    PubMed

    Parel, I; Cutti, A G; Fiumana, G; Porcellini, G; Verni, G; Accardo, A P

    2012-04-01

    To measure the scapulohumeral rhythm (SHR) in outpatient settings, the motion analysis protocol named ISEO (INAIL Shoulder and Elbow Outpatient protocol) was developed, based on inertial and magnetic sensors. To complete the sensor-to-segment calibration, ISEO requires the involvement of an operator for sensor placement and for positioning the patient's arm in a predefined posture. Since this can affect the measure, this study aimed at quantifying ISEO intra- and inter-operator agreement. Forty subjects were considered, together with two operators, A and B. Three measurement sessions were completed for each subject: two by A and one by B. In each session, the humerus and scapula rotations were measured during sagittal and scapular plane elevation movements. ISEO intra- and inter-operator agreement were assessed by computing, between sessions, the: (1) similarity of the scapulohumeral patterns through the Coefficient of Multiple Correlation (CMC(2)), both considering and excluding the difference of the initial value of the scapula rotations between two sessions (inter-session offset); (2) 95% Smallest Detectable Difference (SDD(95)) in scapula range of motion. Results for CMC(2) showed that the intra- and inter-operator agreement is acceptable (median≥0.85, lower-whisker ≥ 0.75) for most of the scapula rotations, independently from the movement and the inter-session offset. The only exception is the agreement for scapula protraction-retraction and for scapula medio-lateral rotation during abduction (inter-operator), which is acceptable only if the inter-session offset is removed. SDD(95) values ranged from 4.4° to 8.6° for the inter-operator and between 4.9° and 8.5° for the intra-operator agreement. In conclusion, ISEO presents a high intra- and inter-operator agreement, particularly with the scapula inter-session offset removed.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. Lunar Communication Terminals for NASA Exploration Missions: Needs, Operations Concepts and Architectures

    NASA Technical Reports Server (NTRS)

    Bhasin, Kul B.; Warner, Joseph D.; Anderson, Lynn M.

    2008-01-01

    NASA is conducting architecture studies prior to deploying a series of short- and long-duration human and robotic missions for the exploration of the Moon and Mars under the Vision for Space Exploration Initiative. A key objective of these missions is to establish and expand, through a series of launches, a system of systems approach to exploration capabilities and science return. The systems identified were Crew Exploration Vehicles, crew and cargo launch vehicles, crew EVA suits, crew and cargo landers, habitats, mobility carriers, and small, pressurized rovers. Multiple space communication networks and systems, deployed over time, will support these space exploration systems of systems. Each deployment phase will support interoperability of components and provide 20 years of legacy systems. In this paper, we describe the modular lunar communications terminals needed for the emerging lunar mission operational scenarios. These lunar communication terminals require flexibility for use in stationary, integrated, and mobile environments. They will support links directly to Earth, to lunar relay satellites, to astronauts and to fixed and mobile lunar surface systems. The operating concepts and traffic models are presented for these terminals within variety of lunar scenarios. A preliminary architecture is outlined, providing for suitable long-duration operations in the harsh lunar environment.

  18. 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.

  19. 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.

  20. 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.

  1. 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

  2. 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

  3. 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

  4. Designing Information Interoperability

    SciTech Connect

    Gorman, Bryan L.; Shankar, Mallikarjun; Resseguie, David R.

    2009-01-01

    Examples of incompatible systems are offered with a discussion of the relationship between incompatibility and innovation. Engineering practices and the role of standards are reviewed as a means of resolving issues of incompatibility, with particular attention to the issue of innovation. Loosely-coupled systems are described as a means of achieving and sustaining both interoperability and innovation in heterogeneous environments. A virtual unifying layer, in terms of a standard, a best practice, and a methodology, is proposed as a modality for designing information interoperability for enterprise applicaitons. The Uniform Resource Identifier (URI), microformats, and Joshua Porter s AOF Method are described and presented as solutions for designing interoperable information sharing web sites. The Special Operations Force Information Access (SOFIA), a mock design, is presented as an example of information interoperability.

  5. 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.

  6. 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.

  7. 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.

  8. Design and Operation of an Open, Interoperable Automated Demand Response Infrastructure for Commercial Buildings

    SciTech Connect

    Piette, Mary Ann; Ghatikar, Girish; Kiliccote, Sila; Watson, David; Koch, Ed; Hennage, Dan

    2009-05-01

    This paper describes the concept for and lessons from the development and field-testing of an open, interoperable communications infrastructure to support automated demand response (auto-DR). Automating DR allows greater levels of participation, improved reliability, and repeatability of the DR in participating facilities. This paper also presents the technical and architectural issues associated with auto-DR and description of the demand response automation server (DRAS), the client/server architecture-based middle-ware used to automate the interactions between the utilities or any DR serving entity and their customers for DR programs. Use case diagrams are presented to show the role of the DRAS between utility/ISO and the clients at the facilities.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. NASA JPL Distributed Systems Technology (DST) Object-Oriented Component Approach for Software Inter-Operability and Reuse

    NASA Technical Reports Server (NTRS)

    Hall, Laverne; Hung, Chaw-Kwei; Lin, Imin

    2000-01-01

    The purpose of this paper is to provide a description of NASA JPL Distributed Systems Technology (DST) Section's object-oriented component approach to open inter-operable systems software development and software reuse. It will address what is meant by the terminology object component software, give an overview of the component-based development approach and how it relates to infrastructure support of software architectures and promotes reuse, enumerate on the benefits of this approach, and give examples of application prototypes demonstrating its usage and advantages. Utilization of the object-oriented component technology approach for system development and software reuse will apply to several areas within JPL, and possibly across other NASA Centers.

  16. 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

  17. How NASA's Atmospheric Science Data Center (ASDC) is operationally using the Esri ArcGIS Platform to improve data discoverability, accessibility and interoperability to meet the diversifying government, private, public and academic communities' driven requirements.

    NASA Astrophysics Data System (ADS)

    Tisdale, M.

    2016-12-01

    NASA's Atmospheric Science Data Center (ASDC) is operationally using the Esri ArcGIS Platform to improve data discoverability, accessibility and interoperability to meet the diversifying government, private, public and academic communities' driven requirements. The ASDC is actively working to provide their mission essential datasets as ArcGIS Image Services, Open Geospatial Consortium (OGC) Web Mapping Services (WMS), OGC Web Coverage Services (WCS) and leveraging the ArcGIS multidimensional mosaic dataset structure. Science teams and ASDC are utilizing these services, developing applications using the Web AppBuilder for ArcGIS and ArcGIS API for Javascript, and evaluating restructuring their data production and access scripts within the ArcGIS Python Toolbox framework and Geoprocessing service environment. These capabilities yield a greater usage and exposure of ASDC data holdings and provide improved geospatial analytical tools for a mission critical understanding in the areas of the earth's radiation budget, clouds, aerosols, and tropospheric chemistry.

  18. 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.

  19. 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.

  20. 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.

  1. 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.

  2. 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...

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. 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

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  1. 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.

  2. 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

  3. Inter-operator Reliability of Magnetic Resonance Image-Based Computational Fluid Dynamics Prediction of Cerebrospinal Fluid Motion in the Cervical Spine.

    PubMed

    Martin, Bryn A; Yiallourou, Theresia I; Pahlavian, Soroush Heidari; Thyagaraj, Suraj; Bunck, Alexander C; Loth, Francis; Sheffer, Daniel B; Kröger, Jan Robert; Stergiopulos, Nikolaos

    2016-05-01

    For the first time, inter-operator dependence of MRI based computational fluid dynamics (CFD) modeling of cerebrospinal fluid (CSF) in the cervical spinal subarachnoid space (SSS) is evaluated. In vivo MRI flow measurements and anatomy MRI images were obtained at the cervico-medullary junction of a healthy subject and a Chiari I malformation patient. 3D anatomies of the SSS were reconstructed by manual segmentation by four independent operators for both cases. CFD results were compared at nine axial locations along the SSS in terms of hydrodynamic and geometric parameters. Intraclass correlation (ICC) assessed the inter-operator agreement for each parameter over the axial locations and coefficient of variance (CV) compared the percentage of variance for each parameter between the operators. Greater operator dependence was found for the patient (0.19 < ICC < 0.99) near the craniovertebral junction compared to the healthy subject (ICC > 0.78). For the healthy subject, hydraulic diameter and Womersley number had the least variance (CV = ~2%). For the patient, peak diastolic velocity and Reynolds number had the smallest variance (CV = ~3%). These results show a high degree of inter-operator reliability for MRI-based CFD simulations of CSF flow in the cervical spine for healthy subjects and a lower degree of reliability for patients with Type I Chiari malformation.

  4. Inter-Operator Dependence of Magnetic Resonance Image-Based Computational Fluid Dynamics Prediction of Cerebrospinal Fluid Motion in the Cervical Spine

    PubMed Central

    Martin, Bryn A.; Yiallourou, Theresia I.; Pahlavian, Soroush Heidari; Thyagaraj, Suraj; Bunck, Alexander C.; Loth, Francis; Sheffer, Daniel B.; Kröger, Jan Robert; Stergiopulos, Nikolaos

    2015-01-01

    For the first time, inter-operator dependence of MRI based computational fluid dynamics (CFD) modeling of cerebrospinal fluid (CSF) in the cervical spinal subarachnoid space (SSS) is evaluated. In vivo MRI flow measurements and anatomy MRI images were obtained at the cervico-medullary junction of a healthy subject and a Chiari I malformation patient. 3D anatomies of the SSS were reconstructed by manual segmentation by four independent operators for both cases. CFD results were compared at nine axial locations along the SSS in terms of hydrodynamic and geometric parameters. Intraclass correlation (ICC) assessed the inter-operator agreement for each parameter over the axial locations and coefficient of variance (CV) compared the percentage of variance for each parameter between the operators. Greater operator dependence was found for the patient (0.19 0.78). For the healthy subject, hydraulic diameter and Womersley number had the least variance (CV= ~2%). For the patient, peak diastolic velocity and Reynolds number had the smallest variance (CV= ~3%). These results show a high degree of inter-operator reliability for MRI-based CFD simulations of CSF flow in the cervical spine for healthy subjects and a lower degree of reliability for patients with Type I Chiari malformation. PMID:26446009

  5. 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

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. Lemnos Interoperable Security Program

    SciTech Connect

    Stewart, John; Halbgewachs, Ron; Chavez, Adrian; Smith, Rhett; Teumim, David

    2012-01-31

    The manner in which the control systems are being designed and operated in the energy sector is undergoing some of the most significant changes in history due to the evolution of technology and the increasing number of interconnections to other system. With these changes however come two significant challenges that the energy sector must face; 1) Cyber security is more important than ever before, and 2) Cyber security is more complicated than ever before. A key requirement in helping utilities and vendors alike in meeting these challenges is interoperability. While interoperability has been present in much of the discussions relating to technology utilized within the energy sector and especially the Smart Grid, it has been absent in the context of cyber security. The Lemnos project addresses these challenges by focusing on the interoperability of devices utilized within utility control systems which support critical cyber security functions. In theory, interoperability is possible with many of the cyber security solutions available to utilities today. The reality is that the effort required to achieve cyber security interoperability is often a barrier for utilities. For example, consider IPSec, a widely-used Internet Protocol to define Virtual Private Networks, or tunnels , to communicate securely through untrusted public and private networks. The IPSec protocol suite has a significant number of configuration options and encryption parameters to choose from, which must be agreed upon and adopted by both parties establishing the tunnel. The exercise in getting software or devices from different vendors to interoperate is labor intensive and requires a significant amount of security expertise by the end user. Scale this effort to a significant number of devices operating over a large geographical area and the challenge becomes so overwhelming that it often leads utilities to pursue solutions from a single vendor. These single vendor solutions may inadvertently lock

  12. 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

  13. 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.

  14. 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.

  15. Design Reference Missions (DRM): Integrated ODM 'Air-Taxi' Mission Features

    NASA Technical Reports Server (NTRS)

    Kloesel, Kurt; Starr, Ginn; Saltzman, John A.

    2017-01-01

    Design Reference Missions (DRM): Integrated ODM Air-Taxi Mission Features, Hybrid Electric Integrated System Testbed (HEIST) flight control. Structural Health, Energy Storage, Electric Components, Loss of Control, Degraded Systems, System Health, Real-Time IO Operator Geo-Fencing, Regional Noise Abatement and Trusted Autonomy Inter-operability.

  16. 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.

  17. 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.

  18. 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.

  19. 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

  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. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. OTF CCSDS SM and C Interoperability Prototype

    NASA Technical Reports Server (NTRS)

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

    2008-01-01

    A presentation is provided to demonstrate the interoperability between two space flight Mission Operation Centers (MOCs) and to emulate telemetry, actions, and alert flows between the two centers. One framework uses a COTS C31 system that uses CORBA to interface to the local OTF data network. The second framework relies on current Houston MCC frameworks and ad hoc clients. Messaging relies on SM and C MAL, Core and Common Service formats, while the transport layer uses AMS. A centralized SM and C Registry uses HTTP/XML for transport/encoding. The project's status and progress are reviewed.

  8. 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.

  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. 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

  14. Future Interoperability of Camp Protection Systems (FICAPS)

    NASA Astrophysics Data System (ADS)

    Caron, Sylvie; Gündisch, Rainer; Marchand, Alain; Stahl, Karl-Hermann

    2013-05-01

    The FICAPS Project has been established as a Project of the European Defence Agency based on an initiative of Germany and France. Goal of this Project was to derive Guidelines, which by a proper implementation in future developments improve Camp Protection Systems (CPS) by enabling and improving interoperability between Camp Protection Systems and its Equipments of different Nations involved in multinational missions. These Guidelines shall allow for: • Real-time information exchange between equipments and systems of different suppliers and nations (even via SatCom), • Quick and easy replacement of equipments (even of different Nations) at run-time in the field by means of plug and play capability, thus lowering the operational and logistic costs and making the system highly available, • Enhancement of system capabilities (open and modular systems) by adding new equipment with new capabilities (just plug-in, automatic adjustment of the HMI Human Machine Interface) without costly and time consuming validation and test on system level (validation and test can be done on Equipment level), Four scenarios have been identified to summarize the interoperability requirements from an operational viewpoint. To prove the definitions given in the Guideline Document, a French and a German Demonstration System, based on existing national assets, were realized. Demonstrations, showing the capabilities given by the defined interoperability requirements with respect to the operational scenarios, were performed. Demonstrations included remote control of a CPS by another CPS, remote sensor control (Electro-Optic/InfraRed EO/IR) and remote effector control. This capability can be applied to extend the protection area or to protect distant infrastructural assets Demonstrations have been performed. The required interoperability functionality was shown successfully. Even if the focus of the FICAPS project was on camp protection, the solution found is also appropriate for other

  15. 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

  16. Interdependence, Interoperability, and Integration: Joint Force Analysis at the Operational Level

    DTIC Science & Technology

    2011-03-01

    Services, 1. 23 Robert 0. Keohane and JosephS. Nye , Power and Interdependence, third edition, New York: Longman Press, 2001, 4. 24 Chuck Harrison. "How...Assistance in Military Operations: The Least-Worst Option to Fill the U.S. Capacity Gap, Carlisle Barracks, Pennsylvania: August 2010 Keohane ...Robert 0. and Nye , JosephS., Power and Interdependence, third edition, New York, New York: Longman Press, 2001 Krause, Michael D. and Phillips, R. Cody

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  1. Interoperable Documentation

    NASA Astrophysics Data System (ADS)

    Habermann, T.

    2011-12-01

    Documentation provides the context that adds understanding and knowledge to data. The ISO Standards for documenting data (19115, 19115-2), and services (19119) extend the range of standard documentation considerably beyond previously available approaches. They include increased utilization of technologies like UML, XML and linking and content areas like data quality and processing history. These extensions can build an emerging foundation of data interoperability into an infrastructure for interoperable understanding. This process will involve active collaboration between many environmental data providers and archives all over the world that are currently in the process of adopting and understanding how to effectively use the ISO Standards. I will describe ISO capabilities in the context of parallels between metadata tools and data interoperability approaches currently used by scientists and decision-makers. I will demonstrate how directories shared over the web, transport standards, and community conventions build the foundation for documentation access and data understanding. I will also demonstrate crosswalks and connections between ISO, THREDDS, and NetCDF documentation and some ideas and approaches to improving documentation across the entire spectrum of environmental data and products.

  2. 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.

  3. 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.

  4. 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

  5. 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.

  6. 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.

  7. 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

  8. 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.

  9. 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

  10. 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

  11. 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.

  12. 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.

  13. IMPI: Making MPI Interoperable.

    PubMed

    George, W L; Hagedorn, J G; Devaney, J E

    2000-01-01

    The Message Passing Interface (MPI) is the de facto standard for writing parallel scientific applications in the message passing programming paradigm. Implementations of MPI were not designed to interoperate, thereby limiting the environments in which parallel jobs could be run. We briefly describe a set of protocols, designed by a steering committee of current implementors of MPI, that enable two or more implementations of MPI to interoperate within a single application. Specifically, we introduce the set of protocols collectively called Interoperable MPI (IMPI). These protocols make use of novel techniques to handle difficult requirements such as maintaining interoperability among all IMPI implementations while also allowing for the independent evolution of the collective communication algorithms used in IMPI. Our contribution to this effort has been as a facilitator for meetings, editor of the IMPI Specification document, and as an early testbed for implementations of IMPI. This testbed is in the form of an IMPI conformance tester, a system that can verify the correct operation of an IMPI-enabled version of MPI.

  14. 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.

  15. 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

  16. 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.

  17. 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

  18. 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.

  19. 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

  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. 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 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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).

  8. 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.

  9. 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

  10. 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.

  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

    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.

  12. 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.

  13. 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

  14. Future of unmanned systems interoperability

    NASA Astrophysics Data System (ADS)

    Ackley, John J.; Wade, Robert L.; Gehring, Daniel G.

    2006-05-01

    There are many challenges in the area of interoperability of unmanned systems: increasing levels of autonomy, teaming and collaboration, long endurance missions, integration with civilian and military spaces. Several currently available methods and technologies may aid in meeting these and other challenges: consensus standards development, formal methods, model-based engineering, knowledge and ontology representation, agent-based systems, and plan language research. We believe the future of unmanned systems interoperability depends on the integration of these methods and technologies into a domain-independent plan language for unmanned systems.

  15. A Generalized Timeline Representation, Services, and Interface for Automating Space Mission Operations

    NASA Technical Reports Server (NTRS)

    Chien, Steve; Johnston, Mark; Frank, Jeremy; Giuliano, Mark; Kavelaars, Alicia; Lenzen, Christoph; Policella, Nicola

    2012-01-01

    Most use a timeline based representation for operations modeling. Most model a core set of state, resource types. Most provide similar capabilities on this modeling to enable (semi) automated schedule generation. In this paper we explore the commonality of : representation and services for these timelines. These commonalities offer potential to be harmonized to enable interoperability, re-use.

  16. A Generalized Timeline Representation, Services, and Interface for Automating Space Mission Operations

    NASA Technical Reports Server (NTRS)

    Chien, Steve; Johnston, Mark; Frank, Jeremy; Giuliano, Mark; Kavelaars, Alicia; Lenzen, Christoph; Policella, Nicola

    2012-01-01

    Most use a timeline based representation for operations modeling. Most model a core set of state, resource types. Most provide similar capabilities on this modeling to enable (semi) automated schedule generation. In this paper we explore the commonality of : representation and services for these timelines. These commonalities offer potential to be harmonized to enable interoperability, re-use.

  17. 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.

  18. 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.

  19. Interoperation Modeling for Intelligent Domotic Environments

    NASA Astrophysics Data System (ADS)

    Bonino, Dario; Corno, Fulvio

    This paper introduces an ontology-based model for domotic device inter-operation. Starting from a previously published ontology (DogOnt) a refactoring and extension is described allowing to explicitly represent device capabilities, states and commands, and supporting abstract modeling of device inter-operation.

  20. 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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..

  6. 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.

  7. 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.

  8. National Flood Interoperability Experiment

    NASA Astrophysics Data System (ADS)

    Maidment, D. R.

    2014-12-01

    The National Flood Interoperability Experiment is led by the academic community in collaboration with the National Weather Service through the new National Water Center recently opened on the Tuscaloosa campus of the University of Alabama. The experiment will also involve the partners in IWRSS (Integrated Water Resources Science and Services), which include the USGS, the Corps of Engineers and FEMA. The experiment will address the following questions: (1) How can near-real-time hydrologic forecasting at high spatial resolution, covering the nation, be carried out using the NHDPlus or next generation geofabric (e.g. hillslope, watershed scales)? (2) How can this lead to improved emergency response and community resilience? (3) How can improved an improved interoperability framework support the first two goals and lead to sustained innovation in the research to operations process? The experiment will run from September 2014 through August 2015, in two phases. The mobilization phase from September 2014 until May 2015 will assemble the components of the interoperability framework. A Summer Institute to integrate the components will be held from June to August 2015 at the National Water Center involving faculty and students from the University of Alabama and other institutions coordinated by CUAHSI. It is intended that the insight that arises from this experiment will help lay the foundation for a new national scale, high spatial resolution, near-real-time hydrologic simulation system for the United States.

  9. 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.

  10. Interoperability Context-Setting Framework

    SciTech Connect

    Widergren, Steven E.; Hardin, Dave; Ambrosio, Ron; Drummond, R.; Gunther, E.; Gilchrist, Grant; Cohen, David

    2007-01-31

    -conditioning (HVAC) unit up several degrees. The resulting load reduction becomes part of an aggregated response from the electricity service provider to the bulk system operator who is now in a better position to manage total system load with available generation. Looking across the electric system, from generating plants, to transmission substations, to the distribution system, to factories, office parks, and buildings, automation is growing, and the opportunities for unleashing new value propositions are exciting. How can we facilitate this change and do so in a way that ensures the reliability of electric resources for the wellbeing of our economy and security? The GridWise Architecture Council (GWAC) mission is to enable interoperability among the many entities that interact with the electric power system. A good definition of interoperability is, “The capability of two or more networks, systems, devices, applications, or components to exchange information between them and to use the information so exchanged.” As a step in the direction of enabling interoperability, the GWAC proposes a context-setting framework to organize concepts and terminology so that interoperability issues can be identified and debated, improvements to address issues articulated, and actions prioritized and coordinated across the electric power community.

  11. 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.

  12. 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

  13. 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

  14. 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.

  15. 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.

  16. 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.

  17. 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.

  18. 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

  19. 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

  20. 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.

  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. 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.

  3. 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

  4. 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.

  5. 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.

  6. 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.

  7. Smart Grid Interoperability Maturity Model

    SciTech Connect

    Widergren, Steven E.; Levinson, Alex; Mater, J.; Drummond, R.

    2010-04-28

    The integration of automation associated with electricity resources (including transmission and distribution automation and demand-side resources operated by end-users) is key to supporting greater efficiencies and incorporating variable renewable resources and electric vehicles into the power system. The integration problems faced by this community are analogous to those faced in the health industry, emergency services, and other complex communities with many stakeholders. To highlight this issue and encourage communication and the development of a smart grid interoperability community, the GridWise Architecture Council (GWAC) created an Interoperability Context-Setting Framework. This "conceptual model" has been helpful to explain the importance of organizational alignment in addition to technical and informational interface specifications for "smart grid" devices and systems. As a next step to building a community sensitive to interoperability, the GWAC is investigating an interoperability maturity model (IMM) based on work done by others to address similar circumstances. The objective is to create a tool or set of tools that encourages a culture of interoperability in this emerging community. The tools would measure status and progress, analyze gaps, and prioritize efforts to improve the situation.

  8. 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.

  9. 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

  10. 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

  11. 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.

  12. 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...

  13. 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.

  14. 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.

  15. 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.

  16. 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…

  17. 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

  18. 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.

  19. Controlled Vocabularies, Mini Ontologies and Interoperability (Invited)

    NASA Astrophysics Data System (ADS)

    King, T. A.; Walker, R. J.; Roberts, D.; Thieman, J.; Ritschel, B.; Cecconi, B.; Genot, V. N.

    2013-12-01

    Interoperability has been an elusive goal, but in recent years advances have been made using controlled vocabularies, mini-ontologies and a lot of collaboration. This has led to increased interoperability between disciplines in the U.S. and between international projects. We discuss the successful pattern followed by SPASE, IVOA and IPDA to achieve this new level of international interoperability. A key aspect of the pattern is open standards and open participation with interoperability achieved with shared services, public APIs, standard formats and open access to data. Many of these standards are expressed as controlled vocabularies and mini ontologies. To illustrate the pattern we look at SPASE related efforts and participation of North America's Heliophysics Data Environment and CDPP; Europe's Cluster Active Archive, IMPEx, EuroPlanet, ESPAS and HELIO; and Japan's magnetospheric missions. Each participating project has its own life cycle and successful standards development must always take this into account. A major challenge for sustained collaboration and interoperability is the limited lifespan of many of the participating projects. Innovative approaches and new tools and frameworks are often developed as competitively selected, limited term projects, but for sustainable interoperability successful approaches need to become part of a long term infrastructure. This is being encouraged and achieved in many domains and we are entering a golden age of interoperability.

  20. 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.

  1. 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.

  2. 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

  3. Approaching semantic interoperability in Health Level Seven

    PubMed Central

    Alschuler, Liora

    2010-01-01

    ‘Semantic Interoperability’ is a driving objective behind many of Health Level Seven's standards. The objective in this paper is to take a step back, and consider what semantic interoperability means, assess whether or not it has been achieved, and, if not, determine what concrete next steps can be taken to get closer. A framework for measuring semantic interoperability is proposed, using a technique called the ‘Single Logical Information Model’ framework, which relies on an operational definition of semantic interoperability and an understanding that interoperability improves incrementally. Whether semantic interoperability tomorrow will enable one computer to talk to another, much as one person can talk to another person, is a matter for speculation. It is assumed, however, that what gets measured gets improved, and in that spirit this framework is offered as a means to improvement. PMID:21106995

  4. 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.

  5. 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

  6. 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.

  7. 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.

  8. 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.

  9. Endpoint Security Using Biometric Authentication for Secure Remote Mission Operations

    NASA Technical Reports Server (NTRS)

    Donohue, John T.; Critchfield, Anna R.

    2000-01-01

    We propose a flexible security authentication solution for the spacecraft end-user, which will allow the user to interact over Internet with the spacecraft, its instruments, or with the ground segment from anywhere, anytime based on the user's pre-defined set of privileges. This package includes biometrics authentication products, such as face, voice or fingerprint recognition, authentication services and procedures, such as: user registration and verification over the Internet and user database maintenance, with a configurable schema of spacecraft users' privileges. This fast and reliable user authentication mechanism will become an integral part of end-to-end ground-to-space secure Internet communications and migration from current practice to the future. All modules and services of the proposed package are commercially available and built to the NIST BioAPI standard, which facilitates "pluggability" and interoperability.

  10. 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

  11. 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

  12. 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

  13. 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

  14. Impact of Region-of-Interest Delineation Methods, Reconstruction Algorithms, and Intra- and Inter-Operator Variability on Internal Dosimetry Estimates Using PET.

    PubMed

    López-Vilanova, N; Pavía, J; Duch, M A; Catafau, A; Ros, D; Bullich, S

    2017-04-01

    Human dosimetry studies play a central role in radioligand development for positron emission tomography (PET). Drawing regions of interest (ROIs) on the PET images is used to measure the dose in each organ. In the study aspects related to ROI delineation methods were evaluated for two radioligands of different biodistribution (intestinal vs urinary). PET images were simulated from a human voxel-based phantom. Several ROI delineation methods were tested: antero-posterior projections (AP), 3D sub-samples of the organs (S), and a 3D volume covering the whole-organ (W). Inter- and intra-operator variability ROI drawing was evaluated by using human data. The effective dose estimates using S and W methods were comparable to the true values. AP methods overestimated (49 %) the dose for the radioligand with intestinal biodistribution. Moreover, the AP method showed the highest inter-operator variability: 11 ± 1 %. The sub-sampled organ method showed the best balance between quantitative accuracy and inter- and intra-operator variability.

  15. 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

  16. 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

  17. 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.

  18. 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

  19. 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

  20. 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.

  1. eHealth interoperability.

    PubMed

    Hammond, W Ed

    2008-01-01

    For improving quality and safety of patient's care, for keeping the costs of health services, but also for successfully managing public health communication and cooperation between all stakeholders is inevitable. Such interoperability can be provided at different levels from simple data exchange up to business interoperability. The paper introduces those interoperability levels and international standards specifying and facilitating them. In that context, the expression of business requirements by domain analysis models or story boards as well as by functional models of the core applications enabling interoperability like EHR systems have been tackled. The role of decision support systems and infrastructural services has been considered as well.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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

  8. 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.

  9. 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.

  10. Onboard Autonomy and Ground Operations Automation for the Intelligent Payload Experiment (IPEX) CubeSat Mission

    NASA Technical Reports Server (NTRS)

    Chien, Steve; Doubleday, Joshua; Ortega, Kevin; Tran, Daniel; Bellardo, John; Williams, Austin; Piug-Suari, Jordi; Crum, Gary; Flatley, Thomas

    2012-01-01

    The Intelligent Payload Experiment (IPEX) is a cubesat manifested for launch in October 2013 that will flight validate autonomous operations for onboard instrument processing and product generation for the Intelligent Payload Module (IPM) of the Hyperspectral Infra-red Imager (HyspIRI) mission concept. We first describe the ground and flight operations concept for HyspIRI IPM operations. We then describe the ground and flight operations concept for the IPEX mission and how that will validate HyspIRI IPM operations. We then detail the current status of the mission and outline the schedule for future development.

  11. Onboard Autonomy and Ground Operations Automation for the Intelligent Payload Experiment (IPEX) CubeSat Mission

    NASA Technical Reports Server (NTRS)

    Chien, Steve; Doubleday, Joshua; Ortega, Kevin; Tran, Daniel; Bellardo, John; Williams, Austin; Piug-Suari, Jordi; Crum, Gary; Flatley, Thomas

    2012-01-01

    The Intelligent Payload Experiment (IPEX) is a cubesat manifested for launch in October 2013 that will flight validate autonomous operations for onboard instrument processing and product generation for the Intelligent Payload Module (IPM) of the Hyperspectral Infra-red Imager (HyspIRI) mission concept. We first describe the ground and flight operations concept for HyspIRI IPM operations. We then describe the ground and flight operations concept for the IPEX mission and how that will validate HyspIRI IPM operations. We then detail the current status of the mission and outline the schedule for future development.

  12. Network Operations Support Plan for the Spot 2 mission (revision 1)

    NASA Technical Reports Server (NTRS)

    Werbitzky, Victor

    1989-01-01

    The purpose of this Network Operations Support Plan (NOSP) is to indicate operational procedures and ground equipment configurations for the SPOT 2 mission. The provisions in this document take precedence over procedures or configurations in other documents.

  13. Mission operations with autonomy: a preliminary report for Earth Observing-1

    NASA Technical Reports Server (NTRS)

    Rabideau, Gregg; Chien, Steve; Sherwood, Rob; Tran, Daniel; Cichy, Benjamin; Mandl, Dan; Frye, Stuart; Shulman, Seth; Bote, Robert; Szwaczkowski, Joseph; Boyer, Darrell; Vab Gaasbeck, Jim

    2004-01-01

    We describe the current mission operations flow for the Earth Observing-1 spacecraft as well as the more autonomous operations to which we are transitioning as part of the Autonomous Sciencecrat Experiment (ASE).

  14. ATOS: Integration of advanced technology software within distributed Spacecraft Mission Operations Systems

    NASA Technical Reports Server (NTRS)

    Jones, M.; Wheadon, J.; Omullane, W.; Whitgift, D.; Poulter, K.; Niezette, M.; Timmermans, R.; Rodriguez, Ivan; Romero, R.

    1994-01-01

    The Advanced Technology Operations System (ATOS) is a program of studies into the integration of advanced applications (including knowledge based systems (KBS)) with ground systems for the support of spacecraft mission operations.

  15. PC-403: Pioneer Venus multiprobe spacecraft mission operational characteristics document, volume 2

    NASA Technical Reports Server (NTRS)

    Barker, F. C.

    1978-01-01

    The data handling subsystem, command subsystem, communications subsystem, power subsystem, and mission operations of the Pioneer Venus multiprobe are presented. The multiprobe spacecraft performance in normal operating modes that correspond to the performance of specific functions at the time of specific events in the mission is described.

  16. 14 CFR 431.43 - Reusable launch vehicle mission operational requirements and restrictions.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 14 Aeronautics and Space 4 2010-01-01 2010-01-01 false Reusable launch vehicle mission operational requirements and restrictions. 431.43 Section 431.43 Aeronautics and Space COMMERCIAL SPACE TRANSPORTATION....43 Reusable launch vehicle mission operational requirements and restrictions. (a) An applicant for...

  17. Small Explorer project: Submillimeter Wave Astronomy Satellite (SWAS). Mission operations and data analysis plan

    NASA Technical Reports Server (NTRS)

    Melnick, Gary J.

    1990-01-01

    The Mission Operations and Data Analysis Plan is presented for the Submillimeter Wave Astronomy Satellite (SWAS) Project. It defines organizational responsibilities, discusses target selection and navigation, specifies instrument command and data requirements, defines data reduction and analysis hardware and software requirements, and discusses mission operations center staffing requirements.

  18. Expert diagnostics system as a part of analysis software for power mission operations

    NASA Technical Reports Server (NTRS)

    Harris, Jennifer A.; Bahrami, Khosrow A.

    1993-01-01

    The operation of interplanetary spacecraft at JPL has become an increasingly complex activity. This complexity is due to advanced spacecraft designs and ambitious mission objectives which lead to operations requirements that are more demanding than those of any previous mission. For this reason, several productivity enhancement measures are underway at JPL within mission operations, particularly in the spacecraft analysis area. These measures aimed at spacecraft analysis include: the development of a multi-mission, multi-subsystem operations environment; the introduction of automated tools into this environment; and the development of an expert diagnostics system. This paper discusses an effort to integrate the above mentioned productivity enhancement measures. A prototype was developed that integrates an expert diagnostics system into a multi-mission, multi-subsystem operations environment using the Galileo Power / Pyro Subsystem as a testbed. This prototype will be discussed in addition to background information associated with it.

  19. The Landsat Data Continuity Mission Operational Land Imager: Radiometric Performance

    NASA Technical Reports Server (NTRS)

    Markham, Brian; Dabney, Philip; Pedelty, Jeffrey

    2011-01-01

    The Operational Land Imager (OLI) is one of two instruments to fly on the Landsat Data Continuity Mission (LDCM), which is scheduled to launch in December 2012 to become the 8th in the series of Landsat satellites. The OLI images in the solar reflective part of the spectrum, with bands similar to bands 1-5, 7 and the panchromatic band on the Landsat-7 ETM+ instrument. In addition, it has a 20 nm bandpass spectral band at 443 nm for coastal and aerosol studies and a 30 nm band at 1375 nm to aid in cirrus cloud detection. Like ETM+, spatial resolution is 30 m in the all but the panchromatic band, which is 15 meters. OLI is a pushbroom radiometer with approximately 6000 detectors per 30 meter band as opposed to the 16 detectors per band on the whiskbroom ETM+. Data are quantized to 12 bits on OLI as opposed to 8 bits on ETM+ to take advantage of the improved signal to noise ratio provided by the pushbroom design. The saturation radiances are higher on OLI than ETM+ to effectively eliminate saturation issues over bright Earth targets. OLI includes dual solar diffusers for on-orbit absolute and relative (detector to detector) radiometric calibration. Additionally, OLI has 3 sets of on-board lamps that illuminate the OLI focal plane through the full optical system, providing additional checks on the OLI's response[l]. OLI has been designed and built by Ball Aerospace & Technology Corp. (BATC) and is currently undergoing testing and calibration in preparation for delivery in Spring 2011. Final pre-launch performance results should be available in time for presentation at the conference. Preliminary results will be presented below. These results are based on the performance of the Engineering Development Unit (EDU) that was radiometrically tested at the integrated instrument level in 2010 and assembly level measurements made on the flight unit. Signal-to-Noise (SNR) performance: One of the advantages of a pushbroom system is the increased dwell time of the detectors

  20. Planetary exploration through year 2000, a core program: Mission operations

    NASA Technical Reports Server (NTRS)

    1986-01-01

    In 1980 the NASA Advisory Council created the Solar System Exploratory Committee (SSEC) to formulate a long-range program of planetary missions that was consistent with likely fiscal constraints on total program cost. The SSEC had as its primary goal the establishment of a scientifically valid, affordable program that would preserve the nation's leading role in solar system exploration, capitalize on two decades of investment, and be consistent with the coordinated set of scientific stategies developed earlier by the Committe on Planetary and Lunar Exploration (COMPLEX). The result of the SSEC effort was the design of a Core Program of planetary missions to be launched by the year 2000, together with a realistic and responsible funding plan. The Core Program Missions, subcommittee activities, science issues, transition period assumptions, and recommendations are discussed.

  1. Validation of a Low-Thrust Mission Design Tool Using Operational Navigation Software

    NASA Technical Reports Server (NTRS)

    Englander, Jacob A.; Knittel, Jeremy M.; Williams, Ken; Stanbridge, Dale; Ellison, Donald H.

    2017-01-01

    Design of flight trajectories for missions employing solar electric propulsion requires a suitably high-fidelity design tool. In this work, the Evolutionary Mission Trajectory Generator (EMTG) is presented as a medium-high fidelity design tool that is suitable for mission proposals. EMTG is validated against the high-heritage deep-space navigation tool MIRAGE, demonstrating both the accuracy of EMTG's model and an operational mission design and navigation procedure using both tools. The validation is performed using a benchmark mission to the Jupiter Trojans.

  2. Validation of a Low-Thrust Mission Design Tool Using Operational Navigation Software

    NASA Technical Reports Server (NTRS)

    Englander, Jacob A.; Knittel, Jeremy M.; Williams, Ken; Stanbridge, Dale; Ellison, Donald H.

    2017-01-01

    Design of flight trajectories for missions employing solar electric propulsion requires a suitably high-fidelity design tool. In this work, the Evolutionary Mission Trajectory Generator (EMTG) is presented as a medium-high fidelity design tool that is suitable for mission proposals. EMTG is validated against the high-heritage deep-space navigation tool MIRAGE, demonstrating both the accuracy of EMTG's model and an operational mission design and navigation procedure using both tools. The validation is performed using a benchmark mission to the Jupiter Trojans.

  3. Radiation dose estimates for typical piloted NTR lunar and Mars mission engine operations

    SciTech Connect

    Schnitzler, B.G. ); Borowski, S.K. . Lewis Research Center)

    1991-01-01

    The natural and manmade radiation environments to be encountered during lunar and Mars missions are qualitatively summarized. The computational methods available to characterize the radiation environment produced by an operating nuclear propulsion system are discussed. Mission profiles and vehicle configurations are presented for a typical all-propulsive, fully reusable lunar mission and for a typical all-propulsive Mars mission. Estimates of crew location biological doses are developed for all propulsive maneuvers. Post-shutdown dose rates near the nuclear engine are estimated at selected mission times. 15 refs., 4 figs.

  4. Interoperability and information discovery

    USGS Publications Warehouse

    Christian, E.

    2001-01-01

    In the context of information systems, there is interoperability when the distinctions between separate information systems are not a barrier to accomplishing a task that spans those systems. Interoperability so defined implies that there are commonalities among the systems involved and that one can exploit such commonalities to achieve interoperability. The challenge of a particular interoperability task is to identify relevant commonalities among the systems involved and to devise mechanisms that exploit those commonalities. The present paper focuses on the particular interoperability task of information discovery. The Global Information Locator Service (GILS) is described as a policy, standards, and technology framework for addressing interoperable information discovery on a global and long-term basis. While there are many mechanisms for people to discover and use all manner of data and information resources, GILS initiatives exploit certain key commonalities that seem to be sufficient to realize useful information discovery interoperability at a global, long-term scale. This paper describes ten of the specific commonalities that are key to GILS initiatives. It presents some of the practical implications for organizations in various roles: content provider, system engineer, intermediary, and searcher. The paper also provides examples of interoperable information discovery as deployed using GILS in four types of information communities: bibliographic, geographic, environmental, and government.

  5. Space Operations: Listing of NASA Scientific Missions, 1980-2000

    DTIC Science & Technology

    1989-04-01

    Titan will deliver an atmospheric probe to Titan and place a spacecraft in orbit around Saturn for detailed study of the rings and bodies of the... Cassini ( Saturn Orbiter’ Titan Probe) Lunar Observer (LO)__________ _________ L_____ ____ WActive Missions, 1.11980-31989-Active/Planned Missions, 4/1989...Ulysses’, 10/1990 9/1995 Mars Observer (MO) 10/1992 9/1995 Comet Rendezvous Asteroid Flyby (CRAF)j 8/1995 2003 Cassin ( Saturn Orbiter/Titan Probe)’ 4

  6. Extravehicular activity space suit interoperability

    NASA Astrophysics Data System (ADS)

    Skoog, A. Ingemar; McBarron, James W.; Severin, Guy I.

    1995-10-01

    The European Agency (ESA) and the Russian Space Agency (RKA) are jointly developing a new space suit system for improved extravehicular activity (EVA) capabilities in support of the MIR Space Station Programme, the EVA Suit 2000. Recent national policy agreements between the U.S. and Russia on planned cooperations in manned space also include joint extravehicular activity (EVA). With an increased number of space suit systems and a higher operational frequency towards the end of this century an improved interoperability for both routine and emergency operations is of eminent importance. It is thus timely to report the current status of ongoing work on international EVA interoperability being conducted by the Committee on EVA Protocols and Operations of the International Academy of Astronautics initialed in 1991. This paper summarises the current EVA interoperability issues to be harmonised and presents quantified vehicle interface requirements for the current U.S. Shuttle EMU and Russian MIR Orlan DMA and the new European/Russian EVA Suit 2000 extravehicular systems. Major critical/incompatible interfaces for suits/mothercraft of different combinations arc discussed, and recommendations for standardisations given.

  7. Extravehicular activity space suit interoperability.

    PubMed

    Skoog, A I; McBarron JW 2nd; Severin, G I

    1995-10-01

    The European Agency (ESA) and the Russian Space Agency (RKA) are jointly developing a new space suit system for improved extravehicular activity (EVA) capabilities in support of the MIR Space Station Programme, the EVA Suit 2000. Recent national policy agreements between the U.S. and Russia on planned cooperations in manned space also include joint extravehicular activity (EVA). With an increased number of space suit systems and a higher operational frequency towards the end of this century an improved interoperability for both routine and emergency operations is of eminent importance. It is thus timely to report the current status of ongoing work on international EVA interoperability being conducted by the Committee on EVA Protocols and Operations of the International Academy of Astronauts initiated in 1991. This paper summarises the current EVA interoperability issues to be harmonised and presents quantified vehicle interface requirements for the current U.S. Shuttle EMU and Russian MIR Orlan DMA and the new European/Russian EVA Suit 2000 extravehicular systems. Major critical/incompatible interfaces for suits/mother-craft of different combinations are discussed, and recommendations for standardisations given.

  8. Hierarchthis: An Interactive Interface for Identifying Mission-Relevant Components of the Advanced Multi-Mission Operations System

    NASA Technical Reports Server (NTRS)

    Litomisky, Krystof

    2012-01-01

    Even though NASA's space missions are many and varied, there are some tasks that are common to all of them. For example, all spacecraft need to communicate with other entities, and all spacecraft need to know where they are. These tasks use tools and services that can be inherited and reused between missions, reducing systems engineering effort and therefore reducing cost.The Advanced Multi-Mission Operations System, or AMMOS, is a collection of multimission tools and services, whose development and maintenance are funded by NASA. I created HierarchThis, a plugin designed to provide an interactive interface to help customers identify mission-relevant tools and services. HierarchThis automatically creates diagrams of the AMMOS database, and then allows users to show/hide specific details through a graphical interface. Once customers identify tools and services they want for a specific mission, HierarchThis can automatically generate a contract between the Multimission Ground Systems and Services Office, which manages AMMOS, and the customer. The document contains the selected AMMOS components, along with their capabilities and satisfied requirements. HierarchThis reduces the time needed for the process from service selections to having a mission-specific contract from the order of days to the order of minutes.

  9. Hierarchthis: An Interactive Interface for Identifying Mission-Relevant Components of the Advanced Multi-Mission Operations System

    NASA Technical Reports Server (NTRS)

    Litomisky, Krystof

    2012-01-01

    Even though NASA's space missions are many and varied, there are some tasks that are common to all of them. For example, all spacecraft need to communicate with other entities, and all spacecraft need to know where they are. These tasks use tools and services that can be inherited and reused between missions, reducing systems engineering effort and therefore reducing cost.The Advanced Multi-Mission Operations System, or AMMOS, is a collection of multimission tools and services, whose development and maintenance are funded by NASA. I created HierarchThis, a plugin designed to provide an interactive interface to help customers identify mission-relevant tools and services. HierarchThis automatically creates diagrams of the AMMOS database, and then allows users to show/hide specific details through a graphical interface. Once customers identify tools and services they want for a specific mission, HierarchThis can automatically generate a contract between the Multimission Ground Systems and Services Office, which manages AMMOS, and the customer. The document contains the selected AMMOS components, along with their capabilities and satisfied requirements. HierarchThis reduces the time needed for the process from service selections to having a mission-specific contract from the order of days to the order of minutes.

  10. Using full-mission simulation for human factors research in air transport operations

    NASA Technical Reports Server (NTRS)

    Orlady, Harry W.; Hennessy, Robert W.; Obermayer, Richard; Vreuls, Donald; Murphy, Miles R.

    1988-01-01

    This study examined state-of-the-art mission oriented simulation and its use in human factors research. Guidelines were developed for doing full-mission human factors research on crew member behavior during simulated air transport operations. The existing literature was reviewed. However, interviews with experienced investigators provided the most useful information. The fundamental scientific and practical issues of behavioral research in a simulation environment are discussed. Guidelines are presented for planning, scenario development, and the execution of behavioral research using full-mission simulation in the context of air transport flight operations . Research is recommended to enhance the validity and productivity of full-mission research by: (1) validating the need for high-fidelity simulation of all major elements in the operational environment, (2) improving methods for conducting full-mission research, and (3) examining part-task research on specific problems through the use of vehicles which contain higher levels of abstraction (and lower fidelity) of the operational environment.

  11. Payette signs mission decal in the JEM during Joint Operations

    NASA Image and Video Library

    2009-07-25

    S127-E-008614 (25 July 2009) --- Flight day 11 activities for the joint shuttle-station crews included the traditional autographing of the station. Canadian Space Agency astronaut Julie Payette, STS-127 mission specialist, has the pen in this frame.

  12. Wakata signs mission decal in the JEM during Joint Operations

    NASA Image and Video Library

    2009-07-25

    S127-E-008624 (25 July 2009) --- Flight day 11 activities for the joint shuttle-station crews included the traditional autographing of the station. Japanese Aerospace Exploration Agency Astronaut Koichi Wakata, STS-127 mission specialist, has the pen in this frame.

  13. Kopra signs mission decal in the JEM during Joint Operations

    NASA Image and Video Library

    2009-07-25

    S127-E-008609 (25 July 2009) --- Flight day 11 activities for the joint shuttle-station crews included the traditional autographing of the station. Astronauts Tom Marshburn (left), STS-127 mission specialist, and Tim Kopra, Expedition 20 flight engineer, are in this frame.

  14. Secure and interoperable communication infrastructures for PPDR organisations

    NASA Astrophysics Data System (ADS)

    Müller, Wilmuth; Marques, Hugo; Pereira, Luis; Rodriguez, Jonathan; Brouwer, Frank; Bouwers, Bert; Politis, Ilias; Lykourgiotis, Asimakis; Ladas, Alexandros; Adigun, Olayinka; Jelenc, David

    2016-05-01

    The growing number of events affecting public safety and security (PS&S) on a regional scale with potential to grow up to large scale cross border disasters puts an increased pressure on agencies and organisation responsible for PS&S. In order to respond timely and in an adequate manner to such events, Public Protection and Disaster Relief (PPDR) organisations need to cooperate, align their procedures and activities, share the needed information and be interoperable. Existing PPDR/PMR technologies such as TETRA, TETRAPOL or P25, do not currently provide broadband capability nor is expected such technologies to be upgraded in the future. This presents a major limitation in supporting new services and information flows. Furthermore, there is no known standard that addresses interoperability of these technologies. In this contribution the design of a next generation communication infrastructure for PPDR organisations which fulfills the requirements of secure and seamless end-to-end communication and interoperable information exchange within the deployed communication networks is presented. Based on Enterprise Architecture of PPDR organisations, a next generation PPDR network that is backward compatible with legacy communication technologies is designed and implemented, capable of providing security, privacy, seamless mobility, QoS and reliability support for mission-critical Private Mobile Radio (PMR) voice and broadband data services. The designed solution provides a robust, reliable, and secure mobile broadband communications system for a wide variety of PMR applications and services on PPDR broadband networks, including the ability of inter-system, interagency and cross-border operations with emphasis on interoperability between users in PMR and LTE.

  15. An Analysis of Strategic Planning to Support the United States Special Operations Forces’ C3 Interoperability.

    DTIC Science & Technology

    1992-09-01

    as the increased sales more than compensate for the increased advertising expenditures. The justification of increasing either inventory or operating...identifies the constraints that are preventing system success and chooses the one that is the foremost problem. The managier then concentrates on

  16. Interoperability and the Federal Role

    SciTech Connect

    Ton, Dan; Irwin, Chris; Widergren, Steven E.

    2010-07-25

    A smart grid is capable of integrating a broad array of generation resources and enables the participation of demand side resources in reliable system operation. To cost effectively realize this flexibility, the associated devices and systems need to connect and interact simply and reliably. Interoperability is the important ingredient to make this happen. Because the electric system transcends organizational boundaries between generators, electricity delivery companies, end-users, and other service providers, advancing interoperability between these organizations can be difficult to justify by individual organizations. But given the importance of a smart electric system to meet national economic, societal, and environmental objectives, a federal role is taking shape in the United States to improve the integration of automation elements and thus make smart grid a reality

  17. A Mission Management Application Suite for Airborne Science Operations

    NASA Astrophysics Data System (ADS)

    Goodman, H. M.; Meyer, P. J.; Blakeslee, R.; Regner, K.; Hall, J.; He, M.; Conover, H.; Garrett, M.; Harper, J.; Smith, T.; Grewe, A.; Real Time Mission Monitor Team

    2011-12-01

    Collection of data during airborne field campaigns is a critically important endeavor. It is imperative to observe the correct phenomena at the right time - at the right place to maximize the instrument observations. Researchers at NASA Marshall Space Flight Center have developed an application suite known as the Real Time Mission Monitor (RTMM). This suite is comprised of tools for mission design, flight planning, aircraft visualization and tracking. The mission design tool allows scientists to set mission parameters such as geographic boundaries and dates of the campaign. Based on these criteria, the tool intelligently selects potential data sets from a data resources catalog from which the scientist is able to choose the aircraft, instruments, and ancillary Earth science data sets to be provided for use in the remaining tool suite. The scientists can easily reconfigure and add data sets of their choosing for use during the campaign. The flight planning tool permits the scientist to assemble aircraft flight plans and to plan coincident observations with other aircraft, spacecraft or in situ observations. Satellite and ground-based remote sensing data and modeling data are used as background layers to aid the scientist in the flight planning process. Planning is crucial to successful collection of data and the ability to modify the plan and upload to aircraft navigators and pilots is essential for the agile collection of data. Most critical to successful and cost effective collection of data is the capability to visualize the Earth science data (airborne instruments, radiosondes, radar, dropsondes, etc.) and track the aircraft in real time. In some instances, aircraft instrument data is provided to ground support personnel in near-real time to visualize with the flight track. This visualization and tracking aspect of RTMM provides a decision support capability in conjunction with scientific collaboration portals to allow for scientists on the ground to communicate

  18. Apollo 14 and 15 missions: Intermittent steerable antenna operation

    NASA Technical Reports Server (NTRS)

    1972-01-01

    An attempt was made to determine the cause of antenna tracking interruptions during Apollo 14 and Apollo 15 missions prior to powered descent, and after ascent from the lunar surface but before rendezvous. Probable causes examined include: (1) amplitude modulation on the uplink radio frequency carrier, (2) noise capacitively or inductively coupled into the track error line, and (3) hardware problems resulting in tracking loop instabilities. It was determined that amplitude modulation caused the antenna oscillations. The corrective procedures taken are given.

  19. Distributed Operations for the Cassini/Huygens Mission

    NASA Technical Reports Server (NTRS)

    Lock, P.; Sarrel, M.

    1998-01-01

    The cassini project employs a concept known as distributed operations which allows independent instrument operations from diverse locations, provides full empowerment of all participants and maximizes use of limited resources.

  20. OPALS: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

    NASA Technical Reports Server (NTRS)

    Abrahamson, Matthew J.; Sindiy, Oleg V.; Oaida, Bogdan V.; Fregoso, Santos; Bowles-Martinez, Jessica N.; Kokorowski, Michael; Wilkerson, Marcus W.; Konyha, Alexander L.

    2014-01-01

    In spring 2014, the Optical PAyload for Lasercomm Science (OPALS) will launch to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a 90-day baseline mission, OPALS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) in Wrightwood, California. To achieve mission success, interfaces to the ISS payload operations infrastructure are established. For OPALS, the interfaces facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes such as pointing prediction and data processing satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The tests have provided valuable insight into operational considerations on the ISS.

  1. OPALS: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

    NASA Technical Reports Server (NTRS)

    Abrahamson, Matthew J.; Sindiy, Oleg V.; Oaida, Bogdan V.; Fregoso, Santos; Bowles-Martinez, Jessica N.; Kokorowski, Michael; Wilkerson, Marcus W.; Konyha, Alexander L.

    2014-01-01

    In spring 2014, the Optical PAyload for Lasercomm Science (OPALS) will launch to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a 90-day baseline mission, OPALS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) in Wrightwood, California. To achieve mission success, interfaces to the ISS payload operations infrastructure are established. For OPALS, the interfaces facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes such as pointing prediction and data processing satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The tests have provided valuable insight into operational considerations on the ISS.

  2. 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.

  3. 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.

  4. Telemedicine system interoperability architecture: concept description and architecture overview.

    SciTech Connect

    Craft, Richard Layne, II

    2004-05-01

    In order for telemedicine to realize the vision of anywhere, anytime access to care, it must address the question of how to create a fully interoperable infrastructure. This paper describes the reasons for pursuing interoperability, outlines operational requirements that any interoperability approach needs to consider, proposes an abstract architecture for meeting these needs, identifies candidate technologies that might be used for rendering this architecture, and suggests a path forward that the telemedicine community might follow.

  5. Groundwater data network interoperability

    USGS Publications Warehouse

    Brodaric, Boyan; Booth, Nathaniel; Boisvert, Eric; Lucido, Jessica M.

    2016-01-01

    Water data networks are increasingly being integrated to answer complex scientific questions that often span large geographical areas and cross political borders. Data heterogeneity is a major obstacle that impedes interoperability within and between such networks. It is resolved here for groundwater data at five levels of interoperability, within a Spatial Data Infrastructure architecture. The result is a pair of distinct national groundwater data networks for the United States and Canada, and a combined data network in which they are interoperable. This combined data network enables, for the first time, transparent public access to harmonized groundwater data from both sides of the shared international border.

  6. 76 FR 34691 - Edison Mission Energy v. Midwest Independent Transmission System Operator, Inc.; Notice of Complaint

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-06-14

    ... Energy Regulatory Commission Edison Mission Energy v. Midwest Independent Transmission System Operator... Energy Regulatory Commission (Commission), 18 CFR 385.206 (2011), Edison Mission Energy, on behalf of NorthStar and Pheasant Ridge wind projects (Edison Wind Projects) (collectively Complainants), filed...

  7. MOS 2.0: Modeling the Next Revolutionary Mission Operations System

    NASA Technical Reports Server (NTRS)

    Delp, Christopher L.; Bindschadler, Duane; Wollaeger, Ryan; Carrion, Carlos; McCullar, Michelle; Jackson, Maddalena; Sarrel, Marc; Anderson, Louise; Lam, Doris

    2011-01-01

    Designed and implemented in the 1980's, the Advanced Multi-Mission Operations System (AMMOS) was a breakthrough for deep-space NASA missions, enabling significant reductions in the cost and risk of implementing ground systems. By designing a framework for use across multiple missions and adaptability to specific mission needs, AMMOS developers created a set of applications that have operated dozens of deep-space robotic missions over the past 30 years. We seek to leverage advances in technology and practice of architecting and systems engineering, using model-based approaches to update the AMMOS. We therefore revisit fundamental aspects of the AMMOS, resulting in a major update to the Mission Operations System (MOS): MOS 2.0. This update will ensure that the MOS can support an increasing range of mission types, (such as orbiters, landers, rovers, penetrators and balloons), and that the operations systems for deep-space robotic missions can reap the benefits of an iterative multi-mission framework.12 This paper reports on the first phase of this major update. Here we describe the methods and formal semantics used to address MOS 2.0 architecture and some early results. Early benefits of this approach include improved stakeholder input and buy-in, the ability to articulate and focus effort on key, system-wide principles, and efficiency gains obtained by use of well-architected design patterns and the use of models to improve the quality of documentation and decrease the effort required to produce and maintain it. We find that such methods facilitate reasoning, simulation, analysis on the system design in terms of design impacts, generation of products (e.g., project-review and software-delivery products), and use of formal process descriptions to enable goal-based operations. This initial phase yields a forward-looking and principled MOS 2.0 architectural vision, which considers both the mission-specific context and long-term system sustainability.

  8. MOS 2.0: Modeling the Next Revolutionary Mission Operations System

    NASA Technical Reports Server (NTRS)

    Delp, Christopher L.; Bindschadler, Duane; Wollaeger, Ryan; Carrion, Carlos; McCullar, Michelle; Jackson, Maddalena; Sarrel, Marc; Anderson, Louise; Lam, Doris

    2011-01-01

    Designed and implemented in the 1980's, the Advanced Multi-Mission Operations System (AMMOS) was a breakthrough for deep-space NASA missions, enabling significant reductions in the cost and risk of implementing ground systems. By designing a framework for use across multiple missions and adaptability to specific mission needs, AMMOS developers created a set of applications that have operated dozens of deep-space robotic missions over the past 30 years. We seek to leverage advances in technology and practice of architecting and systems engineering, using model-based approaches to update the AMMOS. We therefore revisit fundamental aspects of the AMMOS, resulting in a major update to the Mission Operations System (MOS): MOS 2.0. This update will ensure that the MOS can support an increasing range of mission types, (such as orbiters, landers, rovers, penetrators and balloons), and that the operations systems for deep-space robotic missions can reap the benefits of an iterative multi-mission framework.12 This paper reports on the first phase of this major update. Here we describe the methods and formal semantics used to address MOS 2.0 architecture and some early results. Early benefits of this approach include improved stakeholder input and buy-in, the ability to articulate and focus effort on key, system-wide principles, and efficiency gains obtained by use of well-architected design patterns and the use of models to improve the quality of documentation and decrease the effort required to produce and maintain it. We find that such methods facilitate reasoning, simulation, analysis on the system design in terms of design impacts, generation of products (e.g., project-review and software-delivery products), and use of formal process descriptions to enable goal-based operations. This initial phase yields a forward-looking and principled MOS 2.0 architectural vision, which considers both the mission-specific context and long-term system sustainability.

  9. 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

  10. Third International Symposium on Space Mission Operations and Ground Data Systems, part 2

    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 symposium papers focus on improvements in the efficiency, effectiveness, and quality of data acquisition, ground systems, and mission operations. New technology, 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. This volume covers expert systems, systems development tools and approaches, and systems engineering issues.

  11. Frame synchronization in Jet Propulsion Laboratory's Advanced Multi-Mission Operations System (AMMOS)

    NASA Technical Reports Server (NTRS)

    Wilson, E.

    2002-01-01

    The Jet Propulsion Laboratory's Advanced Multi-Mission Operations System system processes data received from deep-space spacecraft, where error rates can be high, bit rates are low, and data is unique precious.

  12. Astronaut John Young during final suiting operations for Apollo 10 mission

    NASA Technical Reports Server (NTRS)

    1969-01-01

    A technician attaches hose from test stand to spacesuit of Astronaut John W. Young, Apollo 10 command module pilot, during final suiting operations for the Apollo 10 lunar orbit mission. Another technician makes adjustment behind Young.

  13. 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.

  14. 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.

  15. Flight and mission operations support for Voyager spacecraft launching and Viking-Mars mission

    NASA Technical Reports Server (NTRS)

    1978-01-01

    The activities of the Jet Propulsion Laboratory during fiscal year 1976-1977 are summarized. Areas covered include ongoing and planned flight projects, DSN operations and development, research and advanced development in science and engineering, and civil systems projects. In addition, administrative and operational facilities and developments are described.

  16. Distributed Operations for the Mars Exploration Rover Mission with the Science Activity Planner

    NASA Technical Reports Server (NTRS)

    Wick, Justin V.; Callas, John L.; Norris, Jeffrey S.; Powell, Mark W.; Vona, Marsette A., III

    2005-01-01

    Due to the length of the Mars Exploration Rover Mission, most scientists were unable to stay at the central operations facility at the Jet Propulsion Laboratory. This created a need for distributed operations software, in the form of the Distributed Science Activity Planner. The distributed architecture saved a considerable amount of money and increased the number of individuals who could be actively involved in the mission, contributing to its success.

  17. Distributed Operations for the Mars Exploration Rover Mission with the Science Activity Planner

    NASA Technical Reports Server (NTRS)

    Wick, Justin V.; Callas, John L.; Norris, Jeffrey S.; Powell, Mark W.; Vona, Marsette A., III

    2005-01-01

    Due to the length of the Mars Exploration Rover Mission, most scientists were unable to stay at the central operations facility at the Jet Propulsion Laboratory. This created a need for distributed operations software, in the form of the Distributed Science Activity Planner. The distributed architecture saved a considerable amount of money and increased the number of individuals who could be actively involved in the mission, contributing to its success.

  18. Joint Space Operations Center (JSpOC) Mission System Increment 3 (JMS Inc 3)

    DTIC Science & Technology

    2016-03-01

    2016 Major Automated Information System Annual Report Joint Space Operations Center (JSpOC) Mission System Increment 3 (JMS Inc 3) Defense...1725 DSN Phone: DSN Fax: Date Assigned: May 16, 2014 Program Information Program Name Joint Space Operations Center (JSpOC) Mission System...approved program baseline; therefore, no Original Estimate has been established. JMS Inc 3 2016 MAR UNCLASSIFIED 4 Program Description The Joint Space

  19. Profibus features intrinsic safety, interoperability

    SciTech Connect

    Bryant, M.

    1996-11-01

    The newest member of the Profibus (process fieldbus) family of interoperable field-bus protocols is {open_quotes}PA{close_quotes}, an intrinsically safe (IS) standard released more than a year ago. IS and non-IS plants using PA for process chemicals, energy production, and food manufacturing are coming online. PA was developed by vendor and user members of the Profibus standards community to meet the needs of customers in the process industries. PA complies with IEC 1158-2, which, among non-IS capabilities, specifies a low-speed, intrinsically safe fieldbus for automating explosive chemical manufacturing. PA thus provides all H1, or {open_quotes}hunk{close_quotes} 1, IS and non-IS services. Importantly, it also provides all H2, or {open_quotes}hunk{close_quotes} 2, services. As the newest segment of the site-proven system of fieldbus protocols, Profibus-PA defines by example the concepts of interoperability and interchangeability. It is a field instrument network that automatically interoperates with a large installed base of fieldbus nodes. As low-speed networks, PA and its competitor, Foundation fieldbus H1 comply with the same standard. They do the same job; auxiliary power to the application, with a data rate of 31.25 kbit/sec. Similarities include a function-block-based architecture and a device description language (DDL). They use the same physical layer for digital data transfer. A casual observer would find PA and H1 virtually the same. The key differences are in the protocol implementations. Although PA and H1 could be wired together, the messages delivered by one would make no sense to the other. At least not yet. PA protocols are capable of both IS and non-IS operations. This opens the door to a wide range of interoperable process-manufacturing requirements. 1 fig., 1 tab.

  20. The Preparation for and Execution of Engineering Operations for the Mars Curiosity Rover Mission

    NASA Technical Reports Server (NTRS)

    Samuels, Jessica A.

    2013-01-01

    The Mars Science Laboratory Curiosity Rover mission is the most complex and scientifically packed rover that has ever been operated on the surface of Mars. The preparation leading up to the surface mission involved various tests, contingency planning and integration of plans between various teams and scientists for determining how operation of the spacecraft (s/c) would be facilitated. In addition, a focused set of initial set of health checks needed to be defined and created in order to ensure successful operation of rover subsystems before embarking on a two year science journey. This paper will define the role and responsibilities of the Engineering Operations team, the process involved in preparing the team for rover surface operations, the predefined engineering activities performed during the early portion of the mission, and the evaluation process used for initial and day to day spacecraft operational assessment.

  1. The Preparation for and Execution of Engineering Operations for the Mars Curiosity Rover Mission

    NASA Technical Reports Server (NTRS)

    Samuels, Jessica A.

    2013-01-01

    The Mars Science Laboratory Curiosity Rover mission is the most complex and scientifically packed rover that has ever been operated on the surface of Mars. The preparation leading up to the surface mission involved various tests, contingency planning and integration of plans between various teams and scientists for determining how operation of the spacecraft (s/c) would be facilitated. In addition, a focused set of initial set of health checks needed to be defined and created in order to ensure successful operation of rover subsystems before embarking on a two year science journey. This paper will define the role and responsibilities of the Engineering Operations team, the process involved in preparing the team for rover surface operations, the predefined engineering activities performed during the early portion of the mission, and the evaluation process used for initial and day to day spacecraft operational assessment.

  2. 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.

  3. Development and Execution of End-of-Mission Operations Case Study of the UARS and ERBS End-of-Mission Plans

    NASA Technical Reports Server (NTRS)

    Hughes, John; Marius, Julio L.; Montoro, Manuel; Patel, Mehul; Bludworth, David

    2006-01-01

    This Paper is a case study of the development and execution of the End-of-Mission plans for the Earth Radiation Budget Satellite (ERBS) and the Upper Atmosphere Research Satellite (UARS). The goals of the End-of-Mission Plans are to minimize the time the spacecraft remains on orbit and to minimize the risk of creating orbital debris. Both of these Missions predate the NASA Management Instructions (NMI) that directs missions to provide for safe mission termination. Each spacecrafts had their own unique challenges, which required assessing End-of-Mission requirements versus spacecraft limitations. Ultimately the End-of- Mission operations were about risk mitigation. This paper will describe the operational challenges and the lessons learned executing these End-of-Mission Plans

  4. EVA safety: Space suit system interoperability

    NASA Technical Reports Server (NTRS)

    Skoog, A. I.; McBarron, J. W.; Abramov, L. P.; Zvezda, A. O.

    1995-01-01

    The results and the recommendations of the International Academy of Astronautics extravehicular activities (IAA EVA) Committee work are presented. The IAA EVA protocols and operation were analyzed for harmonization procedures and for the standardization of safety critical and operationally important interfaces. The key role of EVA and how to improve the situation based on the identified EVA space suit system interoperability deficiencies were considered.

  5. EVA safety: Space suit system interoperability

    NASA Technical Reports Server (NTRS)

    Skoog, A. I.; McBarron, J. W.; Abramov, L. P.; Zvezda, A. O.

    1995-01-01

    The results and the recommendations of the International Academy of Astronautics extravehicular activities (IAA EVA) Committee work are presented. The IAA EVA protocols and operation were analyzed for harmonization procedures and for the standardization of safety critical and operationally important interfaces. The key role of EVA and how to improve the situation based on the identified EVA space suit system interoperability deficiencies were considered.

  6. Mars methane analogue mission: Mission simulation and rover operations at Jeffrey Mine and Norbestos Mine Quebec, Canada

    NASA Astrophysics Data System (ADS)

    Qadi, A.; Cloutis, E.; Samson, C.; Whyte, L.; Ellery, A.; Bell, J. F.; Berard, G.; Boivin, A.; Haddad, E.; Lavoie, J.; Jamroz, W.; Kruzelecky, R.; Mack, A.; Mann, P.; Olsen, K.; Perrot, M.; Popa, D.; Rhind, T.; Sharma, R.; Stromberg, J.; Strong, K.; Tremblay, A.; Wilhelm, R.; Wing, B.; Wong, B.

    2015-05-01

    The Canadian Space Agency (CSA), through its Analogue Missions program, supported a microrover-based analogue mission designed to simulate a Mars rover mission geared toward identifying and characterizing methane emissions on Mars. The analogue mission included two, progressively more complex, deployments in open-pit asbestos mines where methane can be generated from the weathering of olivine into serpentine: the Jeffrey mine deployment (June 2011) and the Norbestos mine deployment (June 2012). At the Jeffrey Mine, testing was conducted over 4 days using a modified off-the-shelf Pioneer rover and scientific instruments including Raman spectrometer, Picarro methane detector, hyperspectral point spectrometer and electromagnetic induction sounder for testing rock and gas samples. At the Norbestos Mine, we used the research Kapvik microrover which features enhanced autonomous navigation capabilities and a wider array of scientific instruments. This paper describes the rover operations in terms of planning, deployment, communication and equipment setup, rover path parameters and instrument performance. Overall, the deployments suggest that a search strategy of “follow the methane” is not practical given the mechanisms of methane dispersion. Rather, identification of features related to methane sources based on image tone/color and texture from panoramic imagery is more profitable.

  7. 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.

  8. Utilization of Virtual Server Technology in Mission Operations

    NASA Technical Reports Server (NTRS)

    Felton, Larry; Lankford, Kimberly; Pitts, R. Lee; Pruitt, Robert W.

    2010-01-01

    Virtualization provides the opportunity to continue to do "more with less"---more computing power with fewer physical boxes, thus reducing the overall hardware footprint, power and cooling requirements, software licenses, and their associated costs. This paper explores the tremendous advantages and any disadvantages of virtualization in all of the environments associated with software and systems development to operations flow. It includes the use and benefits of the Intelligent Platform Management Interface (IPMI) specification, and identifies lessons learned concerning hardware and network configurations. Using the Huntsville Operations Support Center (HOSC) at NASA Marshall Space Flight Center as an example, we demonstrate that deploying virtualized servers as a means of managing computing resources is applicable and beneficial to many areas of application, up to and including flight operations.

  9. Experiment module concepts study. Volume 2: Experiments and mission operations

    NASA Technical Reports Server (NTRS)

    Macdonald, J. M.

    1970-01-01

    The baseline experiment program is concerned with future space experiments and cover the scientific disciplines of astronomy, space physics, space biology, biomedicine and biotechnology, earth applications, materials science, and advanced technology. The experiments within each discipline are grouped into functional program elements according to experiments that support a particular area of research or investigation and experiments that impose similar or related demand on space station support systems. The experiment requirements on module subsystems, experiment operating modes and time profiles, and the role of the astronaut are discussed. Launch and rendezvous with the space station, disposal, and on-orbit operations are delineated. The operational interfaces between module and other system elements are presented and include space station and logistic system interfaces. Preliminary launch and on-orbit environmental criteria and requirements are discussed, and experiment equipment weights by functional program elements are tabulated.

  10. Challenges in building intelligent systems for space mission operations

    NASA Technical Reports Server (NTRS)

    Hartman, Wayne

    1991-01-01

    The purpose here is to provide a top-level look at the stewardship functions performed in space operations, and to identify the major issues and challenges that must be addressed to build intelligent systems that can realistically support operations functions. The focus is on decision support activities involving monitoring, state assessment, goal generation, plan generation, and plan execution. The bottom line is that problem solving in the space operations domain is a very complex process. A variety of knowledge constructs, representations, and reasoning processes are necessary to support effective human problem solving. Emulating these kinds of capabilities in intelligent systems offers major technical challenges that the artificial intelligence community is only beginning to address.

  11. Opals: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

    NASA Technical Reports Server (NTRS)

    Abrahamson, Matthew J.; Sindiy, Oleg V.; Oaida, Bogdan V.; Fregoso, Santos; Bowles-Martinez, Jessica N.; Kokorowski, Michael; Wilkerson, Marcus W.; Konyha, Alexander L.

    2014-01-01

    In April of 2014, the Optical PAyload for Lasercomm Science (OPALS) Flight System (FS) launched to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a planned 90-day baseline mission, the OPALS FS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) ground station in Wrightwood, California. Interfaces to the ISS payload operations infrastructure have been established to facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes, such as pointing prediction and data processing, satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The ORTs have provided valuable insight into operational considerations for the instrument on the ISS.

  12. Opals: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

    NASA Technical Reports Server (NTRS)

    Abrahamson, Matthew J.; Sindiy, Oleg V.; Oaida, Bogdan V.; Fregoso, Santos; Bowles-Martinez, Jessica N.; Kokorowski, Michael; Wilkerson, Marcus W.; Konyha, Alexander L.

    2014-01-01

    In April of 2014, the Optical PAyload for Lasercomm Science (OPALS) Flight System (FS) launched to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a planned 90-day baseline mission, the OPALS FS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) ground station in Wrightwood, California. Interfaces to the ISS payload operations infrastructure have been established to facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes, such as pointing prediction and data processing, satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The ORTs have provided valuable insight into operational considerations for the instrument on the ISS.

  13. The Role of Public Affairs in Special Operations and Missions

    DTIC Science & Technology

    2002-05-01

    QUESTIONNAIRE .......................................................................... 110 C. SOF STUDENT QUESTIONNAIRE ...Special Operations Task Force LFA Lead Federal Agency PA Public Affairs PAO Public Affairs Officer vii PDD Presidential Decision Directive PMIO Post...53 TABLES Table Page 1. SOF Student Questionnaire Answers................................................................ 83 2. SOF Student

  14. 47 CFR 90.547 - Narrowband Interoperability channel capability requirement.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 47 Telecommunication 5 2010-10-01 2010-10-01 false Narrowband Interoperability channel capability... Frequencies in the 763-775 and 793-805 MHz Bands § 90.547 Narrowband Interoperability channel capability... channels in the 769-775 MHz and 799-805 MHz frequency bands must be capable of operating on all of...

  15. 47 CFR 90.547 - Narrowband Interoperability channel capability requirement.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 47 Telecommunication 5 2011-10-01 2011-10-01 false Narrowband Interoperability channel capability... Frequencies in the 763-775 and 793-805 MHz Bands § 90.547 Narrowband Interoperability channel capability... channels in the 769-775 MHz and 799-805 MHz frequency bands must be capable of operating on all of...

  16. 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.

  17. Carrington-L5: The UK/US Space Weather Operational Mission.

    NASA Astrophysics Data System (ADS)

    Bisi, M. M.; Trichas, M.

    2015-12-01

    Airbus Defence and Space (UK) have carried out a study for an operational L5 space weather mission, in collaboration with RAL, the UK Met Office, UCL and Imperial College London. The study looked at the user requirements for an operational mission, a model instrument payload, and a mission/spacecraft concept. A particular focus is cost effectiveness and timelineness of the data, suitable for operational forecasting needs. The study focussed on a mission at L5 assuming that a US mission to L1 will already occur, on the basis that L5 offers the greatest benefit for SWE predictions. The baseline payload has been selected to address all MOSWOC/SWPC priorities using UK/US instruments, consisting of: a heliospheric imager, coronagraph, EUV imager, magnetograph, magnetometer, solar wind analyser and radiation monitor. The platform is based on extensive re-use from Airbus' past missions to minimize the cost and a Falcon-9 launcher has been selected on the same basis. A schedule analysis shows that the earliest launch could occur in 2020, assuming Phase A KO in 2015. The study team have selected the name "Carrington" for the mission, reflecting the UK's proud history in this domain.

  18. The Jason-3 Mission: completing the transition of ocean altimetry from research to operations

    NASA Astrophysics Data System (ADS)

    Vaze, Parag; Neeck, Steven; Bannoura, Walid; Green, Joseph; Wade, Angelo; Mignogno, Michael; Zaouche, Gerard; Couderc, Veronique; Thouvenot, Eric; Parisot, Francois

    2010-10-01

    The Jason-3 mission is planned as a follow-on mission to the Ocean Surface Topography Mission/Jason-2, to continue the core satellite altimetry measurements for physical oceanography. In addition, a key long-term vision of the founders of this measurement will come to reality: the transitioning from research to operational applications of this valuable measurement. Jason-3 builds upon the heritage of foundational and transitional missions such as SEASAT (1978), GEOSAT (1985), TOPEX/Poseidon (T/P, 1992), Jason-1 (2001) and OSTM/Jason-2 (2008), which have led to the understanding and development of a wide range of oceanographic applications of satellite altimetry. With the successful development and operation of the TOPEX/Poseidon and Jason-1 missions, the Franco-American cooperation in ocean altimetry has grown with a steady vision of expanding this measurement towards operational applications. As such, the T/P and Jason-1 missions were developed by NASA and CNES, and subsequently NOAA and EUMETSAT have taken on key partnership roles by providing mission operations services for the OSTM/Jason-2 project. For Jason-3, NOAA and EUMETSAT are the lead agencies with CNES and NASA as key partners providing mission development support. With a planned project start in early 2010 and a launch target of mid-2013, Jason-3 is planned as a recurring mission from OSTM/Jason-2 to minimize satellite development risk as well as to ensure the continuity of measurements after OSTM/Jason-2. The Jason-3 satellite is planned to operate at the same 1336 km, 66 deg. inclination reference orbit with essentially the same on-board instrumentation as OSTM/Jason-2. The instrument suite will consist of a dual-frequency Nadir Altimeter, a Microwave Radiometer, and three Precision Orbit Determination instruments (Global Positioning System - GPS, Doppler Orbitography and Radio-positioning Integrated by Satellite -DORIS, and Laser Retroreflector Array - LRA). Fulfilling the goals of moving satellite

  19. Towards technical interoperability in telemedicine.

    SciTech Connect

    Craft, Richard Layne, II

    2004-05-01

    For telemedicine to realize the vision of anywhere, anytime access to care, the question of how to create a fully interoperable technical infrastructure must be addressed. After briefly discussing how 'technical interoperability' compares with other types of interoperability being addressed in the telemedicine community today, this paper describes reasons for pursuing technical interoperability, presents a proposed framework for realizing technical interoperability, identifies key issues that will need to be addressed if technical interoperability is to be achieved, and suggests a course of action that the telemedicine community might follow to accomplish this goal.

  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

    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.

  1. Integrating Mission Type Orders into Operational Level Intelligence Collection

    DTIC Science & Technology

    2011-05-27

    leverage the concept of MTOs to help operational level intelligence , surveillance, and reconnaissance ( ISR ) professionals extract more performance...emergent practices or procedures pertaining to ISR MTOs need to be codified to enhance future effectiveness? Are there specific intelligence assets or...Joint Publication 2.0, Intelligence makes no mention of the term or concept . Probably the best description available today of ISR MTOs and how they

  2. Mission Assurance: An Operating Construct for the Department of Defense

    DTIC Science & Technology

    2012-02-14

    structures. A search of databases ; academic, government and open sources is more likely to provide copious data regarding space craft operations when...resource allocation.”15 Summary The literature search in addition to the standard library database search utilized government databases such as; GAO...Retrieved from EBSCOhost . 7 Prizzia, R and Helfand, G (2001) Emergency preparedness and disaster management in Hawaii. Disaster Prevention and

  3. Effects of Operational and Strategic Pauses on Mission Success

    DTIC Science & Technology

    2009-05-21

    emphasis on the role of the commander and military genius . A student of the massive Napoleonic wars, he witnessed the effects of long campaigns...volume became both a basic work in the development of Soviet theory of operational art and a model for the method of engaging in foresight in...most significant impact on the subsequent development of Soviet thought was to provide the basis for the theory of the deep campaign.”49 “Deep

  4. Mission Operations Report (MOR) for the Solar, Anomalous, and Magnetosphere Particle Explorer (SAMPEX)

    NASA Technical Reports Server (NTRS)

    1992-01-01

    MISSION OPERATIONS REPORTS are published for use by NASA senior management, as required by NASA Headquarters Management Instruction HQMI 8610. lC, effective November 26, 1991. The purpose of these reports is to provide a documentation system that represents an internal discipline to establish critical discriminators selected in advance to measure mission accomplishment, provide a formal written assessment of mission accomplishment, and provide an accountability of technical achievement. Prelaunch reports are prepared and issued for each flight project just prior to launch. Following launch, updating (Post Launch) reports are issued to provide mission status and progress in meeting mission objectives. Primary distribution of these reports is intended for personnel having program/project management responsibilities.

  5. 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.

  6. 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.

  7. Workstation technology for engineering mission operations at the Jet Propulsion Laboratory

    NASA Astrophysics Data System (ADS)

    Miller, Kevin J.; Murphy, Susan C.

    1990-10-01

    The Operations Engineering Laboratory (OEL) at the Jet Propulsion Laboratory has been developing graphics tools to automate document preparation in support of space flight mission operations. One such tool, which generates a daily Space Flight Operations Schedule (SFOS), a timeline display of the schedule of spacecraft activities for the Voyager mission is described. The tool consists of two parts: a series of programs that preprocess various command files and a graphics editor. The code of the graphics editor was developed with reusability as a primary objective and has since served as the basis for the generation of other automation tools.

  8. Use of Special Operations Forces in United Nations Missions: a Method to Resolve Complexity

    DTIC Science & Technology

    2015-05-21

    his book Black Hawk Down asserted that the SOF forces in Somalia executed operations with such speed and authority...contribution of SOF to the conduct of peace operations? 43 Mark Bowden, Black Hawk Down: A...3, 1993, Task Force Ranger mounted one more mission to capture some of Aidid’s lieutenants, an episode now commonly referred to as Black Hawk Down

  9. Human-in-the-Loop Operations over Time Delay: NASA Analog Missions Lessons Learned

    NASA Technical Reports Server (NTRS)

    Rader, Steven N.; Reagan, Marcum L.; Janoiko, Barbara; Johnson, James E.

    2013-01-01

    Teams at NASA have conducted studies of time-delayed communications as it effects human exploration. In October 2012, the Advanced Exploration Systems (AES) Analog Missions project conducted a Technical Interchange Meeting (TIM) with the primary stakeholders to share information and experiences of studying time delay, to build a coherent picture of how studies are covering the problem domain, and to determine possible forward plans (including how to best communicate study results and lessons learned, how to inform future studies and mission plans, and how to drive potential development efforts). This initial meeting s participants included personnel from multiple NASA centers (HQ, JSC, KSC, ARC, and JPL), academia, and ESA. It included all of the known studies, analog missions, and tests of time delayed communications dating back to the Apollo missions including NASA Extreme Environment Mission Operations (NEEMO), Desert Research and Technology Studies (DRATS/RATS), International Space Station Test-bed for Analog Research (ISTAR), Pavilion Lake Research Project (PLRP), Mars 520, JPL Mars Orbiters/Rovers, Advanced Mission Operations (AMO), Devon Island analog missions, and Apollo experiences. Additionally, the meeting attempted to capture all of the various functional perspectives via presentations by disciplines including mission operations (flight director and mission planning), communications, crew, Capcom, Extra-Vehicular Activity (EVA), Behavioral Health and Performance (BHP), Medical/Surgeon, Science, Education and Public Outreach (EPO), and data management. The paper summarizes the descriptions and results from each of the activities discussed at the TIM and includes several recommendations captured in the meeting for dealing with time delay in human exploration along with recommendations for future development and studies to address this issue.

  10. Automating the training development process for mission flight operations

    NASA Technical Reports Server (NTRS)

    Scott, Carol J.

    1994-01-01

    Traditional methods of developing training do not effectively support the changing needs of operational users in a multimission environment. The Automated Training Development System (ATDS) provides advantages over conventional methods in quality, quantity, turnaround, database maintenance, and focus on individualized instruction. The Operations System Training Group at the JPL performed a six-month study to assess the potential of ATDS to automate curriculum development and to generate and maintain course materials. To begin the study, the group acquired readily available hardware and participated in a two-week training session to introduce the process. ATDS is a building activity that combines training's traditional information-gathering with a hierarchical method for interleaving the elements. The program can be described fairly simply. A comprehensive list of candidate tasks determines the content of the database; from that database, selected critical tasks dictate which competencies of skill and knowledge to include in course material for the target audience. The training developer adds pertinent planning information about each task to the database, then ATDS generates a tailored set of instructional material, based on the specific set of selection criteria. Course material consistently leads students to a prescribed level of competency.

  11. Space Environment Information System - SPENVIS: Applicability for Mission Operations

    NASA Astrophysics Data System (ADS)

    Lawrence, G.; Reid, S.; Kruglanski, M.; Parmentier, N.

    2009-12-01

    ESA's Space Environment Information System (SPENVIS) is a system of models of the space environment and its effects on material (e.g. spacecraft). It covers the natural radiation belts, solar energetic particles, cosmic rays, plasmas, and micro-particles. SPENVIS currently integrates 35 distinct models, with new ones being added regularly. The underlying models arise from many years of research, supported by national and international space agencies, resulting in a variety of tools to investigate the Sun-Earth connection and near-earth environment. SPENVIS was originally developed as a browser-based research tool that collects these tools together, being capable of recreating the full range of conditions in most of the solar system. In recent years SPENVIS has been further developed into an Operational System. In addition to enhancing the modeling capabilities, this required an enhancement to the customer perspective, i.e. ease-of-use, consistency, stability, runtime, support, etc. SPENVIS is now available as a web-based or standalone application. This paper will present the result of the latest development project, along with user case studies that will have particular significance for the satellite operations community

  12. Joint Space Operations Center (JSpOC) Mission System (JMS)

    NASA Astrophysics Data System (ADS)

    Morton, M.; Roberts, T.

    2011-09-01

    US space capabilities benefit the economy, national security, international relationships, scientific discovery, and our quality of life. Realizing these space responsibilities is challenging not only because the space domain is increasingly congested, contested, and competitive but is further complicated by the legacy space situational awareness (SSA) systems approaching end of life and inability to provide the breadth of SSA and command and control (C2) of space forces in this challenging domain. JMS will provide the capabilities to effectively employ space forces in this challenging domain. Requirements for JMS were developed based on regular, on-going engagement with the warfighter. The use of DoD Architecture Framework (DoDAF) products facilitated requirements scoping and understanding and transferred directly to defining and documenting the requirements in the approved Capability Development Document (CDD). As part of the risk reduction efforts, the Electronic System Center (ESC) JMS System Program Office (SPO) fielded JMS Capability Package (CP) 0 which includes an initial service oriented architecture (SOA) and user defined operational picture (UDOP) along with force status, sensor management, and analysis tools. Development efforts are planned to leverage and integrate prototypes and other research projects from Defense Advanced Research Projects Agency, Air Force Research Laboratories, Space Innovation and Development Center, and Massachusetts Institute of Technology/Lincoln Laboratories. JMS provides a number of benefits to the space community: a reduction in operational “transaction time” to accomplish key activities and processes; ability to process the increased volume of metric observations from new sensors (e.g., SBSS, SST, Space Fence), as well as owner/operator ephemerides thus enhancing the high accuracy near-real-time catalog, and greater automation of SSA data sharing supporting collaboration with government, civil, commercial, and foreign

  13. Building space operations resiliency with a multi-tier mission architecture

    NASA Astrophysics Data System (ADS)

    Straub, Jeremy

    2014-06-01

    A variety of naturally occurring (e.g., solar activity) and other (e.g., deliberate attack, residual space object impact) risk factors exist for orbital, aerial and ground-based assets. This paper provides an overview of multiple different risk sources to spacecraft. It then provides an overview of the multi-tier mission/operations architecture. The various types of craft that can participate are discussed as are prospective deployment patterns. Next, a mission plan for a high-resiliency sensing mission is presented. Finally, the paper concludes by considering next steps for testing this designed-forresilience multi-tier architecture.

  14. Crewmembers of the STS 51-L mission leave Operations and Checkout Building

    NASA Technical Reports Server (NTRS)

    1986-01-01

    Crew members of STS 51-L mission walk out of the Operations and Checkout Building on their way to Pad 39B where they will board the Shuttle Challenger. Crew members are from front to back: Commander Francis R. (Dick) Scobee; Mission specialists Judith A. Resnik and Ronald E. McNair; Pilot Michael J. Smith; Payload specialist Christa McAuliffe; Mission Specialist Ellison Onizuka; and Payload specialist Gregory Jarvis. photo number is 108-KSC-386C-937/12 (29996); School of fish swim by portion of the SRB. KSC alternative photo number is 108-KSC-386C-937/18 (29997).

  15. Crewmembers of the STS 51-L mission leave Operations and Checkout Building

    NASA Technical Reports Server (NTRS)

    1986-01-01

    Crew members of STS 51-L mission walk out of the Operations and Checkout Building on their way to Pad 39B where they will board the Shuttle Challenger. Crew members are from front to back: Commander Francis R. (Dick) Scobee; Mission specialists Judith A. Resnik and Ronald E. McNair; Pilot Michael J. Smith; Payload specialist Christa McAuliffe; Mission Specialist Ellison Onizuka; and Payload specialist Gregory Jarvis. photo number is 108-KSC-386C-937/12 (29996); School of fish swim by portion of the SRB. KSC alternative photo number is 108-KSC-386C-937/18 (29997).

  16. Pragmatic Divestment of KC-135 Navigators in the Special Operations Air Refueling Mission

    DTIC Science & Technology

    2015-03-26

    complex Special Operations Air Refueling (SOAR) mission. As the Air Force unveils the KC-46 Pegasus , this mission will continue but without a position...the KC-46 Pegasus , is scheduled for delivery in 2017 and is not retrofitted with a navigator suite (2013, Aviation). This thesis will discuss...aircrew. This study was conducted independent of findings related to the introduction of the KC-46 Pegasus . It is possible, however, that the Air

  17. Transitions Towards Operational Space-Based Ocean Observations: From Single Research Missions into Series and Constellations

    DTIC Science & Technology

    2011-02-16

    context one is not a straightforward task or process . Program development and program scheduling have to deal with major issues like, affordability...operational missions. Later in this paper, we will point out several mission examples of this process . In parallel, and similar to practices in the...will re- process ESA satellite archives together with other satellite data in support of GCOS Essential Climate Variable requirements [4], Table 2

  18. Generic procedure for designing and implementing plan management systems for space science missions operations

    NASA Astrophysics Data System (ADS)

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

    2011-09-01

    This paper is one of the components of a larger framework of activities whose purpose is to improve the performance and productivity of space mission systems, i.e. to increase both what can be achieved and the cost effectiveness of this achievement. Some of these activities introduced the concept of Functional Architecture Module (FAM); FAMs are basic blocks used to build the functional architecture of Plan Management Systems (PMS). They also highlighted the need to involve Science Operations Planning Expertise (SOPE) during the Mission Design Phase (MDP) in order to design and implement efficiently operation planning systems. We define SOPE as the expertise held by people who have both theoretical and practical experience in operations planning, in general, and in space science operations planning in particular. Using ESA's methodology for studying and selecting science missions we also define the MDP as the combination of the Mission Assessment and Mission Definition Phases. However, there is no generic procedure on how to use FAMs efficiently and systematically, for each new mission, in order to analyse the cost and feasibility of new missions as well as to optimise the functional design of new PMS; the purpose of such a procedure is to build more rapidly and cheaply such PMS as well as to make the latter more reliable and cheaper to run. This is why the purpose of this paper is to provide an embryo of such a generic procedure and to show that the latter needs to be applied by people with SOPE during the MDP. The procedure described here proposes some initial guidelines to identify both the various possible high level functional scenarii, for a given set of possible requirements, and the information that needs to be associated with each scenario. It also introduces the concept of catalogue of generic functional scenarii of PMS for space science missions. The information associated with each catalogued scenarii will have been identified by the above procedure and

  19. SIMONS: Ship Monitoring System Support Tactical and Operational Missions

    NASA Astrophysics Data System (ADS)

    Margarit, Gerard

    2016-08-01

    This paper presents the latest results that have been obtained by GMV in the Maritime Surveillance and Awareness (MSA) domain through the exploitation of the SIMONS suite within fully operational scenarios. Diversified actors have been interacted with from pure public authorities to pure private companies for different specific goals. Scenario conditions were also varying in terms of area and target of interest, input data sources, ancillary datasets and dissemination strategies. The results show that SIMONS is a very useful tool in MSA that can complement the tactical and strategic information that can be obtained through in-situ and classical surveillance means (airborne- and ship-based visual reconnaissance...). Beyond timely delivery of reports, the capability to detect small non-metallic targets and to categorize most of the detected spots are two of the most prominent and recognized features.

  20. 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.

  1. Semantically Interoperable XML Data

    PubMed Central

    Vergara-Niedermayr, Cristobal; Wang, Fusheng; Pan, Tony; Kurc, Tahsin; Saltz, Joel

    2013-01-01

    XML is ubiquitously used as an information exchange platform for web-based applications in healthcare, life sciences, and many other domains. Proliferating XML data are now managed through latest native XML database technologies. XML data sources conforming to common XML schemas could be shared and integrated with syntactic interoperability. Semantic interoperability can be achieved through semantic annotations of data models using common data elements linked to concepts from ontologies. In this paper, we present a framework and software system to support the development of semantic interoperable XML based data sources that can be shared through a Grid infrastructure. We also present our work on supporting semantic validated XML data through semantic annotations for XML Schema, semantic validation and semantic authoring of XML data. We demonstrate the use of the system for a biomedical database of medical image annotations and markups. PMID:25298789

  2. NASA and Industry Benefits of ACTS High Speed Network Interoperability Experiments

    NASA Technical Reports Server (NTRS)

    Zernic, M. J.; Beering, D. R.; Brooks, D. E.

    2000-01-01

    This paper provides synopses of the design. implementation, and results of key high data rate communications experiments utilizing the technologies of NASA's Advanced Communications Technology Satellite (ACTS). Specifically, the network protocol and interoperability performance aspects will be highlighted. The objectives of these key experiments will be discussed in their relevant context to NASA missions, as well as, to the comprehensive communications industry. Discussion of the experiment implementation will highlight the technical aspects of hybrid network connectivity, a variety of high-speed interoperability architectures, a variety of network node platforms, protocol layers, internet-based applications, and new work focused on distinguishing between link errors and congestion. In addition, this paper describes the impact of leveraging government-industry partnerships to achieve technical progress and forge synergistic relationships. These relationships will be the key to success as NASA seeks to combine commercially available technology with its own internal technology developments to realize more robust and cost effective communications for space operations.

  3. 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.

  4. Carrington-L5: The UK/US Operational Space Weather Monitoring Mission

    NASA Astrophysics Data System (ADS)

    Trichas, Markos; Gibbs, Mark; Harrison, Richard; Green, Lucie; Eastwood, Jonathan; Bentley, Bob; Bisi, Mario; Bogdanova, Yulia; Davies, Jackie; D'Arrigo, Paolo; Eyles, Chris; Fazakerley, Andrew; Hapgood, Mike; Jackson, David; Kataria, Dhiren; Monchieri, Emanuele; Windred, Phil

    2015-06-01

    Airbus Defence and Space (UK) has carried out a study to investigate the possibilities for an operational space weather mission, in collaboration with the Met Office, RAL, MSSL and Imperial College London. The study looked at the user requirements for an operational mission, a model instrument payload, and a mission/spacecraft concept. A particular focus is cost effectiveness and timelineness of the data, suitable for 24/7 operational forecasting needs. We have focussed on a mission at L5 assuming that a mission to L1 will already occur, on the basis that L5 (Earth trailing) offers the greatest benefit for the earliest possible warning on hazardous SWE events and the most accurate SWE predictions. The baseline payload has been selected to cover all UK Met Office/NOAA's users priorities for L5 using instruments with extensive UK/US heritage, consisting of: heliospheric imager, coronograph, magnetograph, magnetometer, solar wind analyser and radiation monitor. The platform and subsystems are based on extensive re-use from past Airbus Defence and Space spacecraft to minimize the development cost and a Falcon-9 launcher has been selected on the same basis. A schedule analysis shows that the earliest launch could be achieved by 2020, assuming Phase A kick-off in 2015-2016. The study team have selected the name "Carrington" for the mission, reflecting the UK's proud history in this domain.

  5. 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.

  6. Statistics of AUV's Missions for Operational Ocean Observation at the South Brazilian Bight.

    NASA Astrophysics Data System (ADS)

    dos Santos, F. A.; São Tiago, P. M.; Oliveira, A. L. S. C.; Barmak, R. B.; Miranda, T. C.; Guerra, L. A. A.

    2016-02-01

    The high costs and logistics limitations of ship-based data collection represent an obstacle for a persistent in-situ data collection. Satellite-operated Autonomous Underwater Vehicles (AUV's) or gliders (as these AUV's are generally known by the scientific community) are presented as an inexpensive and reliable alternative to perform long-term and real-time ocean monitoring of important parameters such as temperature, salinity, water-quality and acoustics. This work is focused on the performance statistics and the reliability for continuous operation of a fleet of seven gliders navigating in Santos Basin - Brazil, since March 2013. The gliders performance were evaluated by the number of standby days versus the number of operating days, the number of interrupted missions due to (1) equipment failure, (2) weather, (3) accident versus the number of successful missions and the amount and quality of data collected. From the start of the operations in March 2013 to the preparation of this work (July 2015), a total of 16 glider missions were accomplished, operating during 728 of the 729 days passed since then. From this total, 11 missions were successful, 3 missions were interrupted due to equipment failure and 2 gliders were lost. Most of the identified issues were observed in the communication with the glider (when recovery was necessary) or the optode sensors (when remote settings solved the problem). The average duration of a successful mission was 103 days while interrupted ones ended on average in 7 days. The longest mission lasted for 139 days, performing 859 continuous profiles and covering a distance of 2734 Km. The 2 projects performed together 6856 dives, providing an average of 9,5 profiles per day or one profile every 2,5 hours each day during 2 consecutive years.

  7. Device descriptions: The key to fieldbus interoperability

    SciTech Connect

    Santori, M.

    1995-03-01

    The subject of interoperability and fieldbus is a complicated one. Both the definition of and the need for interoperability are subject to some debate. Is it merely the ability to substitute one device for another, or does interoperability imply some greater flexibility in configuring and modifying control systems? In the realm of the Fieldbus Foundation fieldbus, interoperability is embodied in a key technology: device descriptions. A device description (DD) is a clear, unambiguous description of a field device; precisely defining the features, parameters, and operation of the device so a host system can communicate with it. DDs provide both interoperability, by defining the capabilities of typical devices, and product innovation, by giving device manufacturers a common mechanism for describing the functionality included in their devices. Users need not understand the technical working of DDs to derive their benefits. Many readers, however, are curious about how this technology works. This article gives a brief introduction to DDs from a technical perspective. The best place to start is by taking a look at the overall fieldbus architecture. Fieldbus, like any data network, is constructed from a set of communication layers. Each layer performs a specific function required for hosts and devices to communicate on the fieldbus network. For most users, the only layers to be concerned with are the Physical Layer, which defines how you physically wire a network, and the User Layer. The User Layer defines how a user views the world of the fieldbus network and field devices on the network. 7 figs.

  8. President Richard Nixon visits MSC to award Apollo 13 Mission Operations team

    NASA Technical Reports Server (NTRS)

    1970-01-01

    President Richard M. Nixon introduces Sigurd A. Sjoberg (far right), Director of Flight Operations at Manned Spacecraft Center (MSC), and the four Apollo 13 Flight Directors during the Presidnet's post-mission visit to MSC. The Flight Directors are (l.-r.) Glynn S. Lunney, Eugene A. Kranz, Gerald D. Griffin and Milton L. Windler. Dr. Thomas O. Paine, NASA Administrator, is seated at left. President Nixon was on the site to present the Presidential Medal of Freedom -- the nation's highest civilian honor -- to the Apollo 13 Mission Operations Team (35600); A wide-angle, overall view of the large crowd that was on hand to see President Richard M. Nixon present the Presidnetial Medal of Freedom to the Apollo 13 Mission Operations Team. A temporary speaker's platform was erected beside bldg 1 for the occasion (35601).

  9. Spitzer Mission Operation System Planning for IRAC Warm-Instrument Characterization

    NASA Technical Reports Server (NTRS)

    Hunt, Joseph C., Jr.; Sarrel, Marc A.; Mahoney, William A.

    2010-01-01

    This paper will describe how the Spitzer Mission Operations System planned and executed the characterization phase between Spitzer's cryogenic mission and its warm mission. To the largest extend possible, the execution of this phase was done with existing processing and procedures. The modifications that were made were in response to the differences of the characterization phase compared to normal phases before and after. The primary two categories of difference are: unknown date of execution due to uncertainty of knowledge of the date of helium depletion, and the short cycle time for data analysis and re-planning during execution. In addition, all of the planning and design had to be done in parallel with normal operations, and we had to transition smoothly back to normal operations following the transition. This paper will also describe the re-planning we had to do following an anomaly discovered in the first days after helium depletion.

  10. President Richard Nixon visits MSC to award Apollo 13 Mission Operations team

    NASA Technical Reports Server (NTRS)

    1970-01-01

    President Richard M. Nixon introduces Sigurd A. Sjoberg (far right), Director of Flight Operations at Manned Spacecraft Center (MSC), and the four Apollo 13 Flight Directors during the Presidnet's post-mission visit to MSC. The Flight Directors are (l.-r.) Glynn S. Lunney, Eugene A. Kranz, Gerald D. Griffin and Milton L. Windler. Dr. Thomas O. Paine, NASA Administrator, is seated at left. President Nixon was on the site to present the Presidential Medal of Freedom -- the nation's highest civilian honor -- to the Apollo 13 Mission Operations Team (35600); A wide-angle, overall view of the large crowd that was on hand to see President Richard M. Nixon present the Presidnetial Medal of Freedom to the Apollo 13 Mission Operations Team. A temporary speaker's platform was erected beside bldg 1 for the occasion (35601).

  11. Sleep and sleepiness of pilots operating long-range airplane emergency medical missions.

    PubMed

    Amann, Ulrike; Holmes, Alex; Caldwell, John; Hilditch, Cassie

    2014-09-01

    Airplane emergency medical services (AEMS) operators use fixed-wing airplanes to undertake rapid response, round-the-clock medical transport missions. This paper explores the structure of long-range, multileg AEMS missions and the sleep and sleepiness of the pilots who work them. During nine long-range AEMS missions, pilots kept a sleep and sleepiness logbook and wore a wrist activity monitor to evaluate the timing of sleep/wake. Missions had a mean duration of 20 h 00 min ± 2 h 39 min, involved two to four flight legs, and were crewed by three or four pilots who rotated between operating and sleeping in curtained-off bunks. The pilots obtained a mean of 15 h 26 min ± 4 h 51 min and 7 h 54 min ± 1 h 33 min of sleep in the 48 h and 24 h prior to checking in for duty, respectively. During missions, a mean of 3 h 33 min ± 1 h 46 min of sleep was taken, usually across two in-flight sleep periods. Karolinska Sleepiness Scores (KSS) at top of climb and top of descent were typically less than 5 ('neither alert nor sleepy'). A small number of individual higher KSS scores were recorded on the longest missions and on flights between 02:00 and 06:00. These findings suggest that despite the long duration, timing, and multileg nature of AEMS missions, it is possible via careful design and management to operate these missions with appropriate levels of pilot alertness.

  12. 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.

  13. The CYGNSS ground segment; innovative mission operations concepts to support a micro-satellite constellation

    NASA Astrophysics Data System (ADS)

    Rose, D.; Vincent, M.; Rose, R.; Ruf, C.

    Hurricane track forecasts have improved in accuracy by ~50% since 1990, while in that same period there has been essentially no improvement in the accuracy of intensity prediction. One of the main problems in addressing intensity occurs because the rapidly evolving stages of the tropical cyclone (TC) life cycle are poorly sampled in time by conventional polar-orbiting, wide-swath surface wind imagers. NASA's most recently awarded Earth science mission, the NASA EV-2 Cyclone Global Navigation Satellite System (CYGNSS) has been designed to address this deficiency by using a constellation of micro-satellite-class Observatories designed to provide improved sampling of the TC during its life cycle. Managing a constellation of Observatories has classically resulted in an increased load on the ground operations team as they work to create and maintain schedules and command loads for multiple Observatories. Using modern tools and technologies at the Mission Operations Center (MOC) in conjunction with key components implemented in the flight system and an innovative strategy for pass execution coordinated with the ground network operator, the CYGNSS mission reduces the burden of constellation operations to a level commensurate with the low-cost mission concept. This paper focuses on the concept of operations for the CYGNSS constellation as planned for implementation at the CYGNSS MOC in conjunction with the selected ground network operator.

  14. Cyber Threat Assessment of Uplink and Commanding System for Mission Operation

    NASA Technical Reports Server (NTRS)

    Ko, Adans Y.; Tan, Kymie M. C.; Cilloniz-Bicchi, Ferner; Faris, Grant

    2014-01-01

    Most of today's Mission Operations Systems (MOS) rely on Ground Data System (GDS) segment to mitigate cyber security risks. Unfortunately, IT security design is done separately from the design of GDS' mission operational capabilities. This incoherent practice leaves many security vulnerabilities in the system without any notice. This paper describes a new way to system engineering MOS, to include cyber threat risk assessments throughout the MOS development cycle, without this, it is impossible to design a dependable and reliable MOS to meet today's rapid changing cyber threat environment.

  15. President Richard Nixon visits MSC to award Apollo 13 Mission Operations team

    NASA Image and Video Library

    1970-04-18

    S70-35600 (18 April 1970) --- President Richard M. Nixon introduces Sigurd A. Sjoberg (far right), director of Flight Operations at Manned Spacecraft Center, and the four Apollo 13 flight directors during the President?s post-mission visit to the Manned Spacecraft Center. The flight directors are, from left to right, Glynn S. Lunney, Eugene A. Kranz, Gerald D. Griffin and Milton L. Windler. Dr. Thomas O. Paine, Administrator, National Aeronautics and Space Administration, is seated at left. President Nixon was on the site to present the Presidential Medal of Freedom - the nation?s highest civilian honor -to the Apollo 13 Mission Operations Team.

  16. Innovative Test Operations to Support Orion and Future Human Rated Missions

    NASA Technical Reports Server (NTRS)

    Koenig, William J.; Garcia, Rafael; Harris, Richard F.; See, Michael J.; Van Lear, Benjamin S.; Dobson, Jill M.; Norris, Scott Douglas

    2017-01-01

    This paper describes how the Orion program is implementing new and innovative test approaches and strategies in an evolving development environment. The early flight test spacecraft are evolving in design maturity and complexity requiring significant changes in the ground test operations for each mission. The testing approach for EM-2 is planned to validate innovative Orion production acceptance testing methods to support human exploration missions in the future. Manufacturing and testing at Kennedy Space Center in the Neil Armstrong Operations and Checkout facility will provide a seamless transition directly to the launch site avoiding transportation and checkout of the spacecraft from other locations.

  17. Cyber Threat Assessment of Uplink and Commanding System for Mission Operation

    NASA Technical Reports Server (NTRS)

    Ko, Adans Y.; Tan, Kymie M. C.; Cilloniz-Bicchi, Ferner; Faris, Grant

    2014-01-01

    Most of today's Mission Operations Systems (MOS) rely on Ground Data System (GDS) segment to mitigate cyber security risks. Unfortunately, IT security design is done separately from the design of GDS' mission operational capabilities. This incoherent practice leaves many security vulnerabilities in the system without any notice. This paper describes a new way to system engineering MOS, to include cyber threat risk assessments throughout the MOS development cycle, without this, it is impossible to design a dependable and reliable MOS to meet today's rapid changing cyber threat environment.

  18. Concepts of Operations for Asteroid Rendezvous Missions Focused on Resources Utilization

    NASA Technical Reports Server (NTRS)

    Mueller, Robert P.; Sibille, Laurent; Sanders, Gerald B.; Jones, Christopher A.

    2014-01-01

    Several asteroids are the targets of international robotic space missions currently manifested or in the planning stage. This global interest reflects a need to study these celestial bodies for the scientific information they provide about our solar system, and to better understand how to mitigate the collision threats some of them pose to Earth. Another important objective of these missions is providing assessments of the potential resources that asteroids could provide to future space architectures. In this paper, we examine a series of possible mission operations focused on advancing both our knowledge of the types of asteroids suited for different forms of resource extraction, and the capabilities required to extract those resources for mission enhancing and enabling uses such as radiation protection, propulsion, life support, shelter and manufacturing. An evolutionary development and demonstration approach is recommended within the framework of a larger campaign that prepares for the first landings of humans on Mars. As is the case for terrestrial mining, the development and demonstration approach progresses from resource prospecting (understanding the resource, and mapping the 'ore body'), mining/extraction feasibility and product assessment, pilot operations, to full in-situ resource utilization (ISRU). Opportunities to gather specific knowledge for ISRU via resource prospecting during science missions to asteroids are also examined to maximize the pace of development of needed ISRU capabilities and technologies for deep space missions.

  19. IUS/TUG Orbital Operations and Mission Support Study. Volume 1; Executive Summary

    NASA Technical Reports Server (NTRS)

    1975-01-01

    The space transportation system (STS) is discussed which will include a propulsive stage that is carried into low earth orbit by the space shuttle. Data were accumulated from the analyses of various stage concepts, operating modes, and projected missions (space tug systems studies, growth stage studies, engine studies, and critical area studies). The foundation formulated by these studies aided in establishing a tentative two-phase approach for the extension of the STS operating regime beyond the space shuttle including plane changes, higher orbits, geosynchronous orbits and beyond. The orbital operations study, was conducted to provide the generation and analysis of operational plans, requirement, and concepts for the utilization of these vehicles. Primary emphasis was placed on methods and techniques to provide a sound technical approach to operations at reduced cost for the STS mission period.

  20. Lunar base surface mission operations. Lunar Base Systems Study (LBSS) task 4.1

    NASA Technical Reports Server (NTRS)

    1987-01-01

    The purpose was to perform an analysis of the surface operations associated with a human-tended lunar base. Specifically, the study defined surface elements and developed mission manifests for a selected base scenario, determined the nature of surface operations associated with this scenario, generated a preliminary crew extravehicular and intravehicular activity (EVA/IVA) time resource schedule for conducting the missions, and proposed concepts for utilizing remotely operated equipment to perform repetitious or hazardous surface tasks. The operations analysis was performed on a 6 year period of human-tended lunar base operation prior to permanent occupancy. The baseline scenario was derived from a modified version of the civil needs database (CNDB) scenario. This scenario emphasizes achievement of a limited set of science and exploration objectives while emplacing the minimum habitability elements required for a permanent base.

  1. Toward interoperable bioscience data.

    PubMed

    Sansone, Susanna-Assunta; Rocca-Serra, Philippe; Field, Dawn; Maguire, Eamonn; Taylor, Chris; Hofmann, Oliver; Fang, Hong; Neumann, Steffen; Tong, Weida; Amaral-Zettler, Linda; Begley, Kimberly; Booth, Tim; Bougueleret, Lydie; Burns, Gully; Chapman, Brad; Clark, Tim; Coleman, Lee-Ann; Copeland, Jay; Das, Sudeshna; de Daruvar, Antoine; de Matos, Paula; Dix, Ian; Edmunds, Scott; Evelo, Chris T; Forster, Mark J; Gaudet, Pascale; Gilbert, Jack; Goble, Carole; Griffin, Julian L; Jacob, Daniel; Kleinjans, Jos; Harland, Lee; Haug, Kenneth; Hermjakob, Henning; Ho Sui, Shannan J; Laederach, Alain; Liang, Shaoguang; Marshall, Stephen; McGrath, Annette; Merrill, Emily; Reilly, Dorothy; Roux, Magali; Shamu, Caroline E; Shang, Catherine A; Steinbeck, Christoph; Trefethen, Anne; Williams-Jones, Bryn; Wolstencroft, Katherine; Xenarios, Ioannis; Hide, Winston

    2012-01-27

    To make full use of research data, the bioscience community needs to adopt technologies and reward mechanisms that support interoperability and promote the growth of an open 'data commoning' culture. Here we describe the prerequisites for data commoning and present an established and growing ecosystem of solutions using the shared 'Investigation-Study-Assay' framework to support that vision.

  2. Toward interoperable bioscience data

    PubMed Central

    Sansone, Susanna-Assunta; Rocca-Serra, Philippe; Field, Dawn; Maguire, Eamonn; Taylor, Chris; Hofmann, Oliver; Fang, Hong; Neumann, Steffen; Tong, Weida; Amaral-Zettler, Linda; Begley, Kimberly; Booth, Tim; Bougueleret, Lydie; Burns, Gully; Chapman, Brad; Clark, Tim; Coleman, Lee-Ann; Copeland, Jay; Das, Sudeshna; de Daruvar, Antoine; de Matos, Paula; Dix, Ian; Edmunds, Scott; Evelo, Chris T; Forster, Mark J; Gaudet, Pascale; Gilbert, Jack; Goble, Carole; Griffin, Julian L; Jacob, Daniel; Kleinjans, Jos; Harland, Lee; Haug, Kenneth; Hermjakob, Henning; Ho Sui, Shannan J; Laederach, Alain; Liang, Shaoguang; Marshall, Stephen; McGrath, Annette; Merrill, Emily; Reilly, Dorothy; Roux, Magali; Shamu, Caroline E; Shang, Catherine A; Steinbeck, Christoph; Trefethen, Anne; Williams-Jones, Bryn; Wolstencroft, Katherine; Xenarios, Ioannis; Hide, Winston

    2012-01-01

    To make full use of research data, the bioscience community needs to adopt technologies and reward mechanisms that support interoperability and promote the growth of an open ‘data commoning’ culture. Here we describe the prerequisites for data commoning and present an established and growing ecosystem of solutions using the shared ‘Investigation-Study-Assay’ framework to support that vision. PMID:22281772

  3. The Concept Of A Potential Operational CryoSat Follow-on Mission

    NASA Astrophysics Data System (ADS)

    Cullen, R.

    2016-12-01

    CryoSat was a planned as a 3 year mission with clear mission objectives to allow the assessment rates of change of thickness in the land and marine ice fields with reduced uncertainties with relation to other non-dedicated missions. Although CryoSat suffered a launch failure in Oct 2005, the mission was recovered with a launch in April 2010 of CryoSat-2. The nominal mission has now been completed, all mission requirements have been fulfilled and CryoSat has been shown to be most successful as a dedicated polar ice sheet measurement system demonstrated by nearly 200 peer reviewed publications within the first four years of launch. Following the completion of the nominal mission in Oct 2013 the platform was shown to be in good health and with a scientific backing provided by the ESA Earth Science Advisory Committee (ESAC) the mission has been extended until Feb 2017 by the ESA Programme Board for Earth Observation. Though not designed to provide data for science and operational services beyond its original mission requirements, a number of services have been developed for exploitation and these are expected to increase over the next few years. Services cover a number of aspects of land and marine ice fields in addition to complementary activities covering glacial monitoring, inland water in addition to coastal and open ocean surface topography science that CryoSat has demonstrated world leading advances with. This paper will present the overall concept for a potential low-cost continuity to the CryoSat mission with the objective to provide both continuity of the existing CryoSat based data sets, i.e., longer term science and operational services that cannot be provided by the existing Copernicus complement of satellites. This is, in part, due to the high inclination (92°) drifting orbit and state of the art Synthetic Aperture Interferometer Radar Altimeter (SIRAL). In addition, further improvements in performance are expected by use of improved modes of operation

  4. A Potential Operational CryoSat Follow-on Mission Concept and Design

    NASA Astrophysics Data System (ADS)

    Cullen, R.

    2015-12-01

    CryoSat was a planned as a 3 year mission with clear mission objectives to allow the assessment rates of change of thickness in the land and marine ice fields with reduced uncertainties with relation to other non-dedicated missions. Although CryoSat suffered a launch failure in Oct 2005, the mission was recovered with a launch in April 2010 of CryoSat-2. The nominal mission has now been completed, all mission requirements have been fulfilled and CryoSat has been shown to be most successful as a dedicated polar ice sheet measurement system demonstrated by nearly 200 peer reviewed publications within the first four years of launch. Following the completion of the nominal mission in Oct 2013 the platform was shown to be in good health and with a scientific backing provided by the ESA Earth Science Advisory Committee (ESAC) the mission has been extended until Feb 2017 by the ESA Programme Board for Earth Observation. Though not designed to provide data for science and operational services beyond its original mission requirements, a number of services have been developed for exploitation and these are expected to increase over the next few years. Services cover a number of aspects of land and marine ice fields in addition to complementary activities covering glacial monitoring, inland water in addition to coastal and open ocean surface topography science that CryoSat has demonstrated world leading advances with. This paper will present the overall concept for a potential low-cost follow-on to the CryoSat mission with the objective to provide both continuity of the existing CryoSat based data sets, i.e., longer term science and operational services that cannot be provided by the existing Copernicus complement of satellites. This is, in part, due to the high inclination (92°) drifting orbit and state of the art Synthetic Aperture Interferometer Radar Altimeter (SIRAL). In addition, further improvements in performance are expected by use of the instrument timing and

  5. The Second Year of Dawn Mission Operations: Mars Gravity Assist and Onward to Vesta

    NASA Technical Reports Server (NTRS)

    Rayman, Marc D.; Mase, Robert A.

    2009-01-01

    Dawn launched in September 2007 on a mission to orbit main belt asteroids (4) Vesta in 2011 - 2012 and (1) Ceres in 2015. The mission is enabled by an ion propulsion system, which will be operated for the majority of the interplanetary cruise. Following 10.5 months of thrusting that concluded in October 2008, the spacecraft began a period of optimal coast that ended in June 2009. A Mars gravity assist in February 2009 provided an effective deltav of 2.6 km/s. The mission flexibility afforded by the use of ion propulsion provided relatively simple targeting at Mars. Additional engineering activities were conducted during the coast period after Mars, including loading new software into the spacecraft's central computer. This paper describe the progress of the mission, including the approach to Mars, the encounter itself, special activities conducted prior to the resumption of ion thrusting, and the continuation toward Vesta.

  6. Cryosat: ESA's ice Explorer Mission. 7 years in operations: status and future outlook

    NASA Astrophysics Data System (ADS)

    Parrinello, Tommaso

    2017-04-01

    CryoSat-2 was launched on the 8th April 2010 and it is the first European ice mission dedicated to monitoring precise changes in the thickness of polar ice sheets and floating sea ice over a 3-year period. CryoSat-2 carries an innovative radar altimeter called the Synthetic Aperture Interferometric Altimeter (SIRAL) with two antennas and with extended capabilities to meet the measurement requirements for ice-sheets elevation and sea-ice freeboard. Initial results have shown that data is of high quality thanks to an altimeter that is behaving exceptional well within its design specifications. Since its launch, CryoSat data has been used by different scientific communities on a number of Earth Science topics also beyond its prime mission objectives, cryosphere. Scope of this paper is to describe the current mission status and provide programmatic highlights and information on the next development of the mission in its extended period of operations (2017-2019).

  7. 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.

  8. 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.

  9. Using AUTORAD for Cassini File Uplinks: Incorporating Automated Commanding into Mission Operations

    NASA Technical Reports Server (NTRS)

    Goo, Sherwin

    2014-01-01

    As the Cassini spacecraft embarked on the Solstice Mission in October 2010, the flight operations team faced a significant challenge in planning and executing the continuing tour of the Saturnian system. Faced with budget cuts that reduced the science and engineering staff by over a third in size, new and streamlined processes had to be developed to allow the Cassini mission to maintain a high level of science data return with a lower amount of available resources while still minimizing the risk. Automation was deemed an important key in enabling mission operations with reduced workforce and the Cassini flight team has made this goal a priority for the Solstice Mission. The operations team learned about a utility called AUTORAD which would give the flight operations team the ability to program selected command files for radiation up to seven days in advance and help minimize the need for off-shift support that could deplete available staffing during the prime shift hours. This paper will describe how AUTORAD is being utilized by the Cassini flight operations team and the processes that were developed or modified to ensure that proper oversight and verification is maintained in the generation and execution of radiated command files.

  10. Using AUTORAD for Cassini File Uplinks: Incorporating Automated Commanding into Mission Operations

    NASA Technical Reports Server (NTRS)

    Goo, Sherwin

    2014-01-01

    As the Cassini spacecraft embarked on the Solstice Mission in October 2010, the flight operations team faced a significant challenge in planning and executing the continuing tour of the Saturnian system. Faced with budget cuts that reduced the science and engineering staff by over a third in size, new and streamlined processes had to be developed to allow the Cassini mission to maintain a high level of science data return with a lower amount of available resources while still minimizing the risk. Automation was deemed an important key in enabling mission operations with reduced workforce and the Cassini flight team has made this goal a priority for the Solstice Mission. The operations team learned about a utility called AUTORAD which would give the flight operations team the ability to program selected command files for radiation up to seven days in advance and help minimize the need for off-shift support that could deplete available staffing during the prime shift hours. This paper will describe how AUTORAD is being utilized by the Cassini flight operations team and the processes that were developed or modified to ensure that proper oversight and verification is maintained in the generation and execution of radiated command files.

  11. 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.

  12. 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

  13. Assessment of mission planning and rehearsal technologies for the US Special Operations Command

    SciTech Connect

    Peerenboom, J.P.; Robinson, G.; Paddock, R.A.

    1990-03-01

    The US Special Operations Command has identified a need for a computer-based mission planning and rehearsal system to meet the joint requirements of the air, ground, and maritime elements of the Special Operations community. This report summarizes the results of a study (1) to define the technical components and basic functionalities of such a system, (2) to assess alternative technologies and strategies for possible implementation in a prototype system, and (3) to recommend the best approach for developing a prototype system. The major areas requiring automated support are information access and exploitation, image exploitation, mission planning, and mission preview and rehearsal. Specific system requirements and performance characteristics are identified, and a technology demonstration program (in the form of a fully integrated prototype system) is recommended. Finally, a specific set of technologies and a specific development team for a technology demonstration program are proposed. 1 fig., 1 tab.

  14. Design Considerations for Spacecraft Operations During Uncrewed Dormant Phases of Human Exploration Missions

    NASA Technical Reports Server (NTRS)

    Williams-Byrd, Julie; Antol, Jeff; Jefferies, Sharon; Goodliff, Kandyce; Williams, Phillip; Ambrose, Rob; Sylvester, Andre; Anderson, Molly; Dinsmore, Craig; Hoffman, Stephen; hide

    2016-01-01

    NASA is transforming human spaceflight. The Agency is shifting from an exploration-based program with human activities in low Earth orbit (LEO) and targeted robotic missions in deep space to a more sustainable and integrated pioneering approach. However, pioneering space involves daunting technical challenges of transportation, maintaining health, and enabling crew productivity for long durations in remote, hostile, and alien environments. Subject matter experts from NASA's Human Exploration and Operations Mission Directorate (HEOMD) are currently studying a human exploration campaign that involves deployment of assets for planetary exploration. This study, called the Evolvable Mars Campaign (EMC) study, explores options with solar electric propulsion as a central component of the transportation architecture. This particular in-space transportation option often results in long duration transit to destinations. The EMC study is also investigating deployed human rated systems like landers, habitats, rovers, power systems and ISRU system to the surface of Mars, which also will involve long dormant periods when these systems are staged on the surface. In order to enable the EMC architecture, campaign and element design leads along with system and capability development experts from HEOMD's System Maturation Team (SMT) have identified additional capabilities, systems and operation modes that will sustain these systems especially during these dormant phases of the mission. Dormancy is defined by the absence of crew and relative inactivity of the systems. For EMC missions, dormant periods could range from several months to several years. Two aspects of uncrewed dormant operations are considered herein: (1) the vehicle systems that are placed in a dormant state and (2) the autonomous vehicle systems and robotic capabilities that monitor, maintain, and repair the vehicle and systems. This paper describes the mission stages of dormancy operations, phases of dormant

  15. 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.

  16. Application of State Analysis and Goal-Based Operations to a MER Mission Scenario

    NASA Technical Reports Server (NTRS)

    Morris, J. Richard; Ingham, Michel D.; Mishkin, Andrew H.; Rasmussen, Robert D.; Starbird, Thomas W.

    2006-01-01

    State Analysis is a model-based systems engineering methodology employing a rigorous discovery process which articulates operations concepts and operability needs as an integrated part of system design. The process produces requirements on system and software design in the form of explicit models which describe the behavior of states and the relationships among them. By applying State Analysis to an actual MER flight mission scenario, this study addresses the specific real world challenges of complex space operations and explores technologies that can be brought to bear on future missions. The paper describes the tools currently used on a daily basis for MER operations planning and provides an in-depth description of the planning process, in the context of a Martian day's worth of rover engineering activities, resource modeling, flight rules, science observations, and more. It then describes how State Analysis allows for the specification of a corresponding goal-based sequence that accomplishes the same objectives, with several important additional benefits.

  17. Application of State Analysis and Goal-Based Operations to a MER Mission Scenario

    NASA Technical Reports Server (NTRS)

    Morris, J. Richard; Ingham, Michel D.; Mishkin, Andrew H.; Rasmussen, Robert D.; Starbird, Thomas W.

    2006-01-01

    State Analysis is a model-based systems engineering methodology employing a rigorous discovery process which articulates operations concepts and operability needs as an integrated part of system design. The process produces requirements on system and software design in the form of explicit models which describe the behavior of states and the relationships among them. By applying State Analysis to an actual MER flight mission scenario, this study addresses the specific real world challenges of complex space operations and explores technologies that can be brought to bear on future missions. The paper describes the tools currently used on a daily basis for MER operations planning and provides an in-depth description of the planning process, in the context of a Martian day's worth of rover engineering activities, resource modeling, flight rules, science observations, and more. It then describes how State Analysis allows for the specification of a corresponding goal-based sequence that accomplishes the same objectives, with several important additional benefits.

  18. ASARCO LLC Mission Complex - San Xavier; Renewal of Clean Air Act Title V Federal Operating Permit

    EPA Pesticide Factsheets

    EPA notice of final decision to grant approval of the operating permit renewal for ASARCO LLC Mission Complex – San Xavier, a facility that mines and processes copper sulfide ore, located on the reservation of the Tohono O’odham Nation.

  19. 12 CFR 900.2 - Terms relating to Bank operations, mission and supervision.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... supervision. 900.2 Section 900.2 Banks and Banking FEDERAL HOUSING FINANCE BOARD GENERAL DEFINITIONS GENERAL DEFINITIONS APPLYING TO ALL FINANCE BOARD REGULATIONS § 900.2 Terms relating to Bank operations, mission and... U.S.C. 1426(b)), and part 933 of this chapter, as approved by the Finance Board, unless the context...

  20. Mission operation center of the Lavochkin scientific production association: Work with the interorbital space booster "Fregat"

    NASA Astrophysics Data System (ADS)

    Kazakevich, Yu. V.; Zefirov, I. V.

    2015-12-01

    This article reviews the history of the Lavochkin Association Mission Operation Center (Laspace MOC), the reasons for its building, purposes and objectives to support Fregat multipurpose rocket booster (FMRB) launch tracking, as well as the basic principles of information exchange. Hardware and software are described in detail.

  1. Precious bits: frame synchronization in Jet Propulsion Laboratory's Advanced Multi-Mission Operations System (AMMOS)

    NASA Technical Reports Server (NTRS)

    Wilson, E.

    2001-01-01

    The Jet Propulsion Laboratory's (JPL) Advanced Multi-Mission Operations System (AMMOS) system processes data received from deep-space spacecraft, where error rates are high, bit rates are low, and every bit is precious. Frame synchronization and data extraction as performed by AMMOS enhanced data acquisition and reliability for maximum data return and validity.

  2. 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.

  3. Operations cost Reduction for a Jovian Science Mission Using CubeSats

    NASA Astrophysics Data System (ADS)

    Rajguru, A.; Faler, A. C.

    2014-06-01

    This paper proposes the operation of a mission architecture for jovian satellite tour, that uses small orbiter 6U CubeSats, airless body landers of the same order of 6U size and a mothership carrier that will act as a communication hub to DSN.

  4. SSRPT (SSR Pointer Trackeer) for Cassini Mission Operations - A Ground Data Analysis Tool

    NASA Technical Reports Server (NTRS)

    Kan, E.

    1998-01-01

    Tracking the resources of the two redundant Solid State Recorders (SSR) is a necessary routine for Cassini spacecraft mission operations. Instead of relying on a full-fledged spacecraft hardware/software simulator to track and predict the SSR recording and playback pointer positions, a stand-alone SSR Pointer Tracker tool was developed as part of JPL's Multimission Spacecraft Analysis system.

  5. President Richard Nixon visits MSC to award Apollo 13 Mission Operations team

    NASA Image and Video Library

    1970-04-18

    S70-35601 (18 April 1970) --- A wide-angle, overall view of the large crowd of people who were on hand to see President Richard M. Nixon present the Presidential Medal of Freedom to the Apollo 13 Mission Operations Team. The honor is the nation's highest civilian award. A temporary speaker's platform was erected beside Building 1 for the occasion.

  6. Advanced software development workstation: Object-oriented methodologies and applications for flight planning and mission operations

    NASA Technical Reports Server (NTRS)

    Izygon, Michel

    1993-01-01

    The work accomplished during the past nine months in order to help three different organizations involved in Flight Planning and in Mission Operations systems, to transition to Object-Oriented Technology, by adopting one of the currently most widely used Object-Oriented analysis and Design Methodology is summarized.

  7. 12 CFR 900.2 - Terms relating to Bank operations, mission and supervision.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... supervision. 900.2 Section 900.2 Banks and Banking FEDERAL HOUSING FINANCE BOARD GENERAL DEFINITIONS GENERAL DEFINITIONS APPLYING TO ALL FINANCE BOARD REGULATIONS § 900.2 Terms relating to Bank operations, mission and... U.S.C. 1426(b)), and part 933 of this chapter, as approved by the Finance Board, unless the...

  8. Operational Risk Management: Increasing Mission Effectiveness Through Improved Planning and Execution of Joint Operations.

    DTIC Science & Technology

    2007-11-02

    operation plans. This deficiency should be remedied with the adoption of Operational Risk Management (ORM), an existing process which would provide...operations plans. The paper concludes that Operational Risk Management should be formally adopted into the deliberate and crisis action joint planning

  9. Desert Rats 2011 Mission Simulation: Effects of Microgravity Operational Modes on Fields Geology Capabilities

    NASA Technical Reports Server (NTRS)

    Bleacher, Jacob E.; Hurtado, J. M., Jr.; Meyer, J. A.

    2012-01-01

    Desert Research and Technology Studies (DRATS) is a multi-year series of NASA tests that deploy planetary surface hardware and exercise mission and science operations in difficult conditions to advance human and robotic exploration capabilities. DRATS 2011 (Aug. 30-Sept. 9, 2011) tested strategies for human exploration of microgravity targets such as near-Earth asteroids (NEAs). Here we report the crew perspective on the impact of simulated microgravity operations on our capability to conduct field geology.

  10. The Marine Corps Budget and Contingency Operations: Is the Funding Adequate to the Mission?

    DTIC Science & Technology

    1994-06-03

    such as Operation Fiery Vigil, the evacuation of U.S. personnel from the Philippines following the eruption of Mount Pinotubo.31 The cost of Operation...USS Tripoli, USS Juneau, and 50 USS Rushmore . Their mission was to secure the seaport and airport of Mogadishu to provide secure assembly areas for...participated in the Mount Pinotubo evacuation in the Philippines and the Hurricane Hugo disaster relief in Guam since participating in Desert storm." When

  11. 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.

  12. Design, qualification and operation of nuclear rockets for safe Mars missions

    SciTech Connect

    Buden, D.; Madsen, W.W.; Olson, T.S.; Redd, L.R.

    1993-04-01

    Nuclear thermal propulsion modules planned for use on crew missions to Mars improve mission reliability and overall safety of the mission. This, as well as all other systems, are greatly enhanced if the system specifications take into account safety from design initiation, and operational considerations are well thought through and applied. For instance, the use of multiple engines in the propulsion module can lead to very high system safety and reliability. Operational safety enhancements may include: the use of multiple perigee burns, thus allowing time to ensure that all systems are functioning properly prior to departure from Earth orbit; the ability to perform all other parts of the mission in a degraded mode with little or no degradation of the mission; and the safe disposal of the nuclear propulsion module in a heliocentric orbit out of the ecliptic plane. The standards used to qualify nuclear rockets are one of the main cost drivers of the program. Concepts and systems that minimize cost and risk will rely on use of the element and component levels to demonstrate technology readiness and validation. Subsystem or systems testing then is only needed for verification of performance. Also, these will be the safest concepts because they will be more thoroughly understood and the safety margins will be well established and confirmed by tests.

  13. Design, qualification and operation of nuclear rockets for safe Mars missions

    SciTech Connect

    Buden, D.; Madsen, W.W.; Olson, T.S. ); Redd, L.R. )

    1993-01-01

    Nuclear thermal propulsion modules planned for use on crew missions to Mars improve mission reliability and overall safety of the mission. This, as well as all other systems, are greatly enhanced if the system specifications take into account safety from design initiation, and operational considerations are well thought through and applied. For instance, the use of multiple engines in the propulsion module can lead to very high system safety and reliability. Operational safety enhancements may include: the use of multiple perigee burns, thus allowing time to ensure that all systems are functioning properly prior to departure from Earth orbit; the ability to perform all other parts of the mission in a degraded mode with little or no degradation of the mission; and the safe disposal of the nuclear propulsion module in a heliocentric orbit out of the ecliptic plane. The standards used to qualify nuclear rockets are one of the main cost drivers of the program. Concepts and systems that minimize cost and risk will rely on use of the element and component levels to demonstrate technology readiness and validation. Subsystem or systems testing then is only needed for verification of performance. Also, these will be the safest concepts because they will be more thoroughly understood and the safety margins will be well established and confirmed by tests.

  14. Communications During Critical Mission Operations: Preparing for InSight's Landing on Mars

    NASA Technical Reports Server (NTRS)

    Asmar, Sami; Oudrhiri, Kamal; Kurtik, Susan; Weinstein-Weiss, Stacy

    2014-01-01

    Radio communications with deep space missions are often taken for granted due to the impressively successful records since, for decades, the technology and infrastructure have been developed for ground and flight systems to optimize telemetry and commanding. During mission-critical events such as the entry, descent, and landing of a spacecraft on the surface of Mars, the signal's level and frequency dynamics vary significantly and typically exceed the threshold of the budgeted links. The challenge is increased when spacecraft shed antennas with heat shields and other hardware during those risky few minutes. We have in the past successfully received signals on Earth during critical events even ones not intended for ground reception. These included the UHF signal transmitted by Curiosity to Marsorbiting assets. Since NASA's Deep Space Network does not operate in the UHF band, large radio telescopes around the world are utilized. The Australian CSIRO Parkes Radio Telescope supported the Curiosity UHF signal reception and DSN receivers, tools, and expertise were used in the process. In preparation for the InSight mission's landing on Mars in 2016, preparations are underway to support the UHF communications. This paper presents communication scenarios with radio telescopes, and the DSN receiver and tools. It also discusses the usefulness of the real-time information content for better response time by the mission team towards successful mission operations.

  15. Communications During Critical Mission Operations: Preparing for InSight's Landing on Mars

    NASA Technical Reports Server (NTRS)

    Asmar, Sami; Oudrhiri, Kamal; Kurtik, Susan; Weinstein-Weiss, Stacy

    2014-01-01

    Radio communications with deep space missions are often taken for granted due to the impressively successful records since, for decades, the technology and infrastructure have been developed for ground and flight systems to optimize telemetry and commanding. During mission-critical events such as the entry, descent, and landing of a spacecraft on the surface of Mars, the signal's level and frequency dynamics vary significantly and typically exceed the threshold of the budgeted links. The challenge is increased when spacecraft shed antennas with heat shields and other hardware during those risky few minutes. We have in the past successfully received signals on Earth during critical events even ones not intended for ground reception. These included the UHF signal transmitted by Curiosity to Marsorbiting assets. Since NASA's Deep Space Network does not operate in the UHF band, large radio telescopes around the world are utilized. The Australian CSIRO Parkes Radio Telescope supported the Curiosity UHF signal reception and DSN receivers, tools, and expertise were used in the process. In preparation for the InSight mission's landing on Mars in 2016, preparations are underway to support the UHF communications. This paper presents communication scenarios with radio telescopes, and the DSN receiver and tools. It also discusses the usefulness of the real-time information content for better response time by the mission team towards successful mission operations.

  16. 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

  17. Spacecraft Autonomy and Automation: A Comparative Analysis of Strategies for Cost Effective Mission Operations

    NASA Technical Reports Server (NTRS)

    Wright, Nathaniel, Jr.

    2000-01-01

    The evolution of satellite operations over the last 40 years has drastically changed. October 4, 1957 (during the cold war) the Soviet Union launched the world's first spacecraft into orbit. The Sputnik satellite orbited Earth for three months and catapulted the United States into a race for dominance in space. A year after Sputnik, President Dwight Eisenhower formed the National Space and Aeronautics Administration (NASA). With a team of scientists and engineers, NASA successfully launched Explorer 1, the first US satellite to orbit Earth. During these early years, massive amounts of ground support equipment and operators were required to successfully operate spacecraft vehicles. Today, budget reductions and technological advances have forced new approaches to spacecraft operations. These approaches require increasingly complex, on board spacecraft systems, that enable autonomous operations, resulting in more cost-effective mission operations. NASA's Goddard Space Flight Center, considered world class in satellite development and operations, has developed and operated over 200 satellites during its 40 years of existence. NASA Goddard is adopting several new millennium initiatives that lower operational costs through the spacecraft autonomy and automation. This paper examines NASA's approach to spacecraft autonomy and ground system automation through a comparative analysis of satellite missions for Hubble Space Telescope-HST, Near Earth Asteroid Rendezvous-NEAR, and Solar Heliospheric Observatory-SoHO, with emphasis on cost reduction methods, risk analysis and anomalies and strategies employed for mitigating risk.

  18. Spacecraft Autonomy and Automation: A Comparative Analysis of Strategies for Cost Effective Mission Operations

    NASA Technical Reports Server (NTRS)

    Wright, Nathaniel, Jr.

    2000-01-01

    The evolution of satellite operations over the last 40 years has drastically changed. October 4, 1957 (during the cold war) the Soviet Union launched the world's first spacecraft into orbit. The Sputnik satellite orbited Earth for three months and catapulted the United States into a race for dominance in space. A year after Sputnik, President Dwight Eisenhower formed the National Space and Aeronautics Administration (NASA). With a team of scientists and engineers, NASA successfully launched Explorer 1, the first US satellite to orbit Earth. During these early years, massive amounts of ground support equipment and operators were required to successfully operate spacecraft vehicles. Today, budget reductions and technological advances have forced new approaches to spacecraft operations. These approaches require increasingly complex, on board spacecraft systems, that enable autonomous operations, resulting in more cost-effective mission operations. NASA's Goddard Space Flight Center, considered world class in satellite development and operations, has developed and operated over 200 satellites during its 40 years of existence. NASA Goddard is adopting several new millennium initiatives that lower operational costs through the spacecraft autonomy and automation. This paper examines NASA's approach to spacecraft autonomy and ground system automation through a comparative analysis of satellite missions for Hubble Space Telescope-HST, Near Earth Asteroid Rendezvous-NEAR, and Solar Heliospheric Observatory-SoHO, with emphasis on cost reduction methods, risk analysis and anomalies and strategies employed for mitigating risk.

  19. Deep Space Habitat Concept of Operations for Extended Duration Transit Missions

    NASA Technical Reports Server (NTRS)

    Hoffman, Stephen J.; Toups, Larry

    2012-01-01

    NASA's Capability-Driven Framework (CDF) describes an approach for progressively extending human exploration missions farther into the Solar System for longer periods of time as allowed by developments in technology and spacecraft systems. Within this framework design reference missions (DRMs) targeted for several specific destinations are being used to assess different combinations of vehicles, operations, and advanced technologies to help understand which combination will best support expanded human exploration both efficiently and sustainably. Several of the identified destinations have been found to require missions with a round trip duration exceeding one year. These mission durations exceed the capabilities of current human-rated spacecraft if resupply from Earth is not possible. This makes the design of an efficient and reliable Deep Space Habitat (DSH) critical for reaching these destinations. The paper will describe the current understanding of DSH capabilities and functions that must be exhibited by any future habitat design for these missions. This description of the DSH is presented in the form of a concept of operation, which focuses on the functions that any DSH must provide, as opposed to a specific DSH design concept. Development of a concept of operations, based on DRM features, provides a common basis for assessing the viability of design concepts incorporating differing configurations and technologies. A study team with representation from several NASA Centers and relevant engineering and scientific disciplines collaborated to develop this DSH concept of operations for the transit phases of these missions. The transit phase of a mission is defined as the time after leaving Earth but before arrival at the destination and the time after leaving the destination but before arriving back at Earth. These transit phases were found to have many common features across all of the destinations being assessed for the CDF and thus arguing for a common concept

  20. Deep Space Habitat Concept of Operations for Extended Duration Transit Missions

    NASA Technical Reports Server (NTRS)

    Hoffman, Stephen J.; Toups, Larry

    2012-01-01

    NASA's Capability-Driven Framework (CDF) describes an approach for progressively extending human exploration missions farther into the Solar System for longer periods of time as allowed by developments in technology and spacecraft systems. Within this framework design reference missions (DRMs) targeted for several specific destinations are being used to assess different combinations of vehicles, operations, and advanced technologies to help understand which combination will best support expanded human exploration both efficiently and sustainably. Several of the identified destinations have been found to require missions with a round trip duration exceeding one year. These mission durations exceed the capabilities of current human-rated spacecraft if resupply from Earth is not possible. This makes the design of an efficient and reliable Deep Space Habitat (DSH) critical for reaching these destinations. The paper will describe the current understanding of DSH capabilities and functions that must be exhibited by any future habitat design for these missions. This description of the DSH is presented in the form of a concept of operation, which focuses on the functions that any DSH must provide, as opposed to a specific DSH design concept. Development of a concept of operations, based on DRM features, provides a common basis for assessing the viability of design concepts incorporating differing configurations and technologies. A study team with representation from several NASA Centers and relevant engineering and scientific disciplines collaborated to develop this DSH concept of operations for the transit phases of these missions. The transit phase of a mission is defined as the time after leaving Earth but before arrival at the destination and the time after leaving the destination but before arriving back at Earth. These transit phases were found to have many common features across all of the destinations being assessed for the CDF and thus arguing for a common concept