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 SM and C Mission Operations Interoperability Prototype

    NASA Technical Reports Server (NTRS)

    Lucord, Steven A.

    2010-01-01

    This slide presentation reviews the prototype of the Spacecraft Monitor and Control (SM&C) Operations for interoperability among other space agencies. This particular prototype uses the German Space Agency (DLR) to test the ideas for interagency coordination.

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

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

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

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

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

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

  10. Space Mission Operations Concept

    NASA Technical Reports Server (NTRS)

    Squibb, Gael F.

    1996-01-01

    This paper will discuss the concept of developing a space mission operations concept; the benefits of starting this system engineering task early; the neccessary inputs to the process; and the products that are generated.

  11. Mission Operations Assurance

    NASA Technical Reports Server (NTRS)

    Faris, Grant

    2012-01-01

    Integrate the mission operations assurance function into the flight team providing: (1) value added support in identifying, mitigating, and communicating the project's risks and, (2) being an essential member of the team during the test activities, training exercises and critical flight operations.

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

  13. ICD-11 (JLMMS) and SCT Inter-Operation.

    PubMed

    Mamou, Marzouk; Rector, Alan; Schulz, Stefan; Campbell, James; Solbrig, Harold; Rodrigues, Jean-Marie

    2016-01-01

    The goal of this work is to contribute to a smooth and semantically sound inter-operability between the ICD-11 (International Classification of Diseases-11th revision Joint Linearization for Mortality, Morbidity and Statistics) and SNOMED CT (SCT). To guarantee such inter-operation between a classification, characterized by a single hierarchy of mutually exclusive and exhaustive classes, as is the JLMMS successor of ICD-10 on the one hand, and the multi-hierarchical, ontology-based clinical terminology SCT on the other hand, we use ontology axioms that logically express generalizable truths. This is expressed by the compositional grammar of SCT, together with queries on axiomsof SCT. We test the feasibility of the method on the circulatory chapter of ICD-11 JLMMS and present limitations and results. PMID:27139413

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

  15. Ulysses mission operations

    NASA Technical Reports Server (NTRS)

    Beech, P.

    1992-01-01

    The Ulysses mission is described in terms of in-Shuttle operations, initial in-orbit operations, routine operations, operational organization, and data gathering and production. The configuration of the Ulysses payload is illustrated, and the flight to orbit is described including a three-hour on-orbit checkout. The first contact was reported at the Deep Space Network station followed by an adjustment of the spacecraft solar-aspect angle and the acquisition of ranging and Doppler data. In-orbit operations include the earth acquisition maneuver, a trajectory correction maneuver, and a payload switch. Continuous data gathering is discussed with reference to the Jupiter encounter and the first and second oppositions and conjunctions. The data-gathering components comprise ground stations, a data-processing computer, and a data-records system. Data production is performed in an off-line mode that does not interfere with the real-time operations.

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

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

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

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

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

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

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

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

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

  5. ISS Update: Autonomous Mission Operations

    NASA Video Gallery

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

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

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

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

  9. CRRES Prelaunch Mission Operation Report

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The overall NASA Combined Release and Radiation Effects Satellite (CRRES) program consists of a series of chemical releases from the PEGSAT spacecraft, the CRRES spacecraft and sounding rockets. The first chemical releases were made from the PEGSAT spacecraft in April, 1990 over northern Canada. In addition to the releases planned from the CRRES spacecraft there are releases from sounding rockets planned from the Kwajalein rocket range in July and August, 1990 and from Puerto Rico in June and July, 1991. It shows the major milestones in the overall CRRES program. This Mission Operations Report only describes the NASA mission objectives of the CRRES/Geosynchronous Transfer Orbit (GTO) mission.

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

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

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

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

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

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

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

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

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

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

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

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

  3. A Virtual Mission Operations Center - Collaborative Environment

    NASA Technical Reports Server (NTRS)

    Medina, Barbara; Bussman, Marie

    2002-01-01

    Development of technologies that enable significant reductions in the cost of space mission operations is critical if constellations, formations, federations and sensor webs, are to be economically feasible. One approach to cost reduction is to infuse automation technologies into mission operations centers so that fewer personnel are needed for mission support. But missions are more culturally and politically adverse to the risks of automation. Reducing the mission risk associated with increased use of automation within a MOC is therefore of great importance. The belief that mission risk increases as more automation is used stems from the fact that there is inherently less direct human oversight to investigate and resolve anomalies in an unattended MOC. The Virtual Missions Operations Center - Collaborative Environment (VMOC-CE) project was launched to address this concern. The goal of the VMOC-CE project is to identify, develop, and infuse technology to enable mission operations between onsite operators and on-call personnel in geographically dispersed locations. VMOC-CE enables missions to more readily adopt automation because off-site operators and engineers can more easily identify, investigate, and resolve anomalies without having to be present in the MOC. The VMOC-CE intent is to have a single access point for all resources used in a collaborative mission operations environment. Team members will be able to interact during spacecraft operations, specifically for resolving anomalies, utilizing a desktop computer and the Internet. Mission operations management can use the VMOC-CE as a tool to participate in and monitor status of anomaly resolution or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities and technologies, operations concept, and results of its pilot in support of the Earth Science Mission Operations System (ESMOS).

  4. Toward lowering the cost of mission operations

    NASA Technical Reports Server (NTRS)

    Wall, S. D.; Ledbetter, K. W.

    1993-01-01

    The mission operations system is one of the more significant drivers of the cost of the mission operations and data analysis segment of missions. In large or long-lived projects, the MOS can also be a driver in total mission cost. Larger numbers of missions, together with an increasingly cost-conscious environment, dictate that future missions must more strictly control costs as they perform to their requirements. It is therefore prudent to examine the conduct of past missions for ways to conserve resources. In this paper we review inputs made to past projects' 'lessons-learned' activities, in which personnel from past projects (among other things) identified major cost drivers of MOS's and considered how economies were or might have been realized in both design and performance of their MOS. Common themes among four such reviews are summarized in an attempt to provide suggestions for cost reduction in future missions.

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

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

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

  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 and Dr. Christopher C. Kraft, Jr., look toward the orbiter spotter on the projection plotter at the front of the MOCR. Also present are Astronaut Daniel C. Brandenstein, seated left, and NASA Administrator James M. Beggs standing left of center. In the foreground, Dr. Hans Mark, Deputy NASA Administrator, briefs Michael Deaver, Special Assistant to President Reagan (39504); President Reagan speaks to the STS-2 crew during the second day of their mission. On hand in MOCR were NASA Administrator James M. Beggs and Deputy Administrator Hans Mark (standing behind the president but mostly out of frame) and Dr. Kraft on the right. Eugene F. Kranz, Deputy Director of Flight Operations can be seen in the background seated at the Flight Operations Directorate (FOD) console. Also present is Astronaut Daniel C. Brandenstein, seated left, who turned the communications over to Mr. Reagan (39505).

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

  10. NASA Antarctic Mission Operation ICE Bridge 2009

    NASA Video Gallery

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

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

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

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

  16. Operational efficiency subpanel advanced mission control

    NASA Technical Reports Server (NTRS)

    Friedland, Peter

    1990-01-01

    Herein, the term mission control will be taken quite broadly to include both ground and space based operations as well as the information infrastructure necessary to support such operations. Three major technology areas related to advanced mission control are examined: (1) Intelligent Assistance for Ground-Based Mission Controllers and Space-Based Crews; (2) Autonomous Onboard Monitoring, Control and Fault Detection Isolation and Reconfiguration; and (3) Dynamic Corporate Memory Acquired, Maintained, and Utilized During the Entire Vehicle Life Cycle. The current state of the art space operations are surveyed both within NASA and externally for each of the three technology areas and major objectives are discussed from a user point of view for technology development. Ongoing NASA and other governmental programs are described. An analysis of major research issues and current holes in the program are provided. Several recommendations are presented for enhancing the technology development and insertion process to create advanced mission control environments.

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

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

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

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

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

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

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

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

    NASA Technical Reports Server (NTRS)

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

    2006-01-01

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

  5. Automation of Hubble Space Telescope Mission Operations

    NASA Technical Reports Server (NTRS)

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

    2012-01-01

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

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

    NASA Technical Reports Server (NTRS)

    1973-01-01

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

  7. Giotto—The mission operations system

    NASA Astrophysics Data System (ADS)

    Wilkins, David E. B.

    On 2 July 1985, the European Space Agency (ESA) launched an interplanetary probe to encounter Halley's Comet on the night of 13/14 March 1986 at a distance of 0.98 AU from Earth. The mission to Halley's Comet was the Agency's first venture into deep space. The tracking stations necessary to support such a mission were not directly available to ESA at the initiation of the GIOTTO project although facilities operated by NASA's deep space network were later made available for certain phases of the mission, together with the 30-m Weilheim antenna of the DFVLR. ESA's European Space Operations Centre, ESOC therefore developed the new deep space tracking stations especially for support of the GIOTTO mission. One of these stations, the 15-m antenna facility at Carnarvon, West Australia, was designed and installed by ESA as a dedicated S-band and X-band tracking, telemetry and command station. The second station at Parkes, New South Wales, Australia, a 64-m radio telescope owned by the Commonwealth Scientific and Industrial Research Organization (CSIRO) was modified to provide X-band telemetry reception using cryogenic MASER low-noise amplifiers. This station operated by CSIRO with assistance from a ESA engineering and operations team, provided support to the GIOTTO mission for reception of the 46 kbs high speed telemetry format which is vital to success of the GIOTTO mission at time of Cometary Encounter. Additionally, the DFVLR Weilheim station was modified to include the newly developed ESOC deep space tracking system which was also installed at the Carnarvon Station. The paper discusses in some detail the network of tracking stations which provided the Control Centre at ESOC in Darmstadt, F.R.G. with the data which was vital to the success of the mission. Because the launch date of GIOTTO was a date which could not be rescheduled, the design installation, integration and testing of the complete GIOTTO mission operations system was an extremely time critical activity

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

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

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

  11. Spitzer Observatory Operations -- Increasing Efficiency in Mission Operations

    NASA Technical Reports Server (NTRS)

    Scott, Charles P.; Kahr, Bolinda E.; Sarrel, Marc A.

    2006-01-01

    This paper explores the how's and why's of the Spitzer Mission Operations System's (MOS) success, efficiency, and affordability in comparison to other observatory-class missions. MOS exploits today's flight, ground, and operations capabilities, embraces automation, and balances both risk and cost. With operational efficiency as the primary goal, MOS maintains a strong control process by translating lessons learned into efficiency improvements, thereby enabling the MOS processes, teams, and procedures to rapidly evolve from concept (through thorough validation) into in-flight implementation. Operational teaming, planning, and execution are designed to enable re-use. Mission changes, unforeseen events, and continuous improvement have often times forced us to learn to fly anew. Collaborative spacecraft operations and remote science and instrument teams have become well integrated, and worked together to improve and optimize each human, machine, and software-system element.

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

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

  14. Applying successful near mission operations approaches and refining for contour mission operations

    NASA Astrophysics Data System (ADS)

    Holdridge, Mark E.

    2003-01-01

    On February 17, 1996, the first NASA Discovery Class Mission to launch, the Near Earth Asteroid Rendezvous (NEAR) spacecraft, began its journey to the asteroid Eros. NEAR is the first planetary spacecraft to be designed and operated by the Johns Hopkins University Applied Physics Laboratory (JHU/APL). In July 2002, the comet nucleus tour (CONTOUR) spacecraft, the second planetary spacecraft to be built and operated at JHUAPL and the 6th in the series of NASA Discovery Class Missions, will be launched. Both NEAR and CONTOUR share ambitious "Faster, Better, Cheaper" goals. Furthermore, with both missions being developed and operated at the same institution, a unique opportunity exists to refine CONTOUR designs and operational practices based on 5 years of NEAR operational experience. This paper provides an overview of designs and operational practices implemented by JHU/APL to safely and effectively conduct the NEAR mission. This paper discusses how these will be applied to the CONTOUR mission and what improvements are planned. It also discusses the unique challenges CONTOUR possesses for operating a 4 year mission with widely varying operations activity levels at low cost.

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

  16. Smart repeater system for communications interoperability during multi-agency law enforcement operations

    SciTech Connect

    Crutcher, R.I.; Jones, R.W.; Moore, M.R.; Smith, S.F.; Tolley, A.L.; Rochelle, R.W.

    1996-12-31

    A prototype smart repeater that provides interoperability capabilities for radio communication systems in multi-agency and multi-user scenarios is being developed by the Oak Ridge National Laboratory. The smart repeater functions as a deployable communications platform that can be dynamically reconfigured to cross-link the radios of participating federal, state, and local government agencies. This interconnection capability improves the coordination and execution of multi-agency operations, including coordinated law enforcement activities and general emergency or disaster response scenarios. The repeater provides multiple channels of operation in the 30--50, 118--136, 138--174, and 403--512 MHz land mobile communications and aircraft bands while providing the ability to cross-connect among multiple frequencies, bands, modulation types, and encryption formats. Additionally, two telephone interconnects provide links to the fixed and cellular telephone networks. The 800- and 900-MHz bands are not supported by the prototype, but the modular design of the system accommodates future retrofits to extend frequency capabilities with minimal impact to the system. Configuration of the repeater is through a portable personal computer with a Windows-based graphical interface control screen that provides dynamic reconfiguration of network interconnections and formats.

  17. Spacecraft automated operations. [for interplanetary missions

    NASA Technical Reports Server (NTRS)

    Bird, T. H.; Sharpe, B. L.

    1979-01-01

    Trends in automation of planetary spacecraft are examined using data from missions as far back as Mariner '67 and up to the highly sophisticated Galileo. Nine design considerations which influence the degree of automation such as protection against catastrophic failures, highly repetitive functions, loss of spacecraft communications, and the need for near-real-time adaptivity are discussed. Rapid growth of automation is shown in terms of on-board hardware by plots of number of processors on board, the average speed of processors, and total core memory. The number of commands transmitted from the ground has grown to 5 million bits in Voyager, so that increases in mission complexity have increased both in spacecraft automation and ground operations. Achieving greater automation by transferring ground operations to the spacecraft with the current means of controlling missions, are considered noting proposed changes. For the future, improved computer technology, more microprocessors and increased core storage will be used, and the number of automated functions and their complexity will grow. It is concluded that using the growing computational capability of spacecraft will achieve more autonomy thus reversing the trend of increased mission complexity and cost.

  18. Analyzing human errors in flight mission operations

    NASA Technical Reports Server (NTRS)

    Bruno, Kristin J.; Welz, Linda L.; Barnes, G. Michael; Sherif, Josef

    1993-01-01

    A long-term program is in progress at JPL to reduce cost and risk of flight mission operations through a defect prevention/error management program. The main thrust of this program is to create an environment in which the performance of the total system, both the human operator and the computer system, is optimized. To this end, 1580 Incident Surprise Anomaly reports (ISA's) from 1977-1991 were analyzed from the Voyager and Magellan projects. A Pareto analysis revealed that 38 percent of the errors were classified as human errors. A preliminary cluster analysis based on the Magellan human errors (204 ISA's) is presented here. The resulting clusters described the underlying relationships among the ISA's. Initial models of human error in flight mission operations are presented. Next, the Voyager ISA's will be scored and included in the analysis. Eventually, these relationships will be used to derive a theoretically motivated and empirically validated model of human error in flight mission operations. Ultimately, this analysis will be used to make continuous process improvements continuous process improvements to end-user applications and training requirements. This Total Quality Management approach will enable the management and prevention of errors in the future.

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

    NASA Technical Reports Server (NTRS)

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

    1994-01-01

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

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

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

  2. Spitzer observatory operations: increasing efficiency in mission operations

    NASA Astrophysics Data System (ADS)

    Scott, Charles P.; Kahr, Bolinda E.; Sarrel, Marc A.

    2006-06-01

    This paper explores the how's and why's of the Spitzer Mission Operations System's (MOS) success, efficiency, and affordability in comparison to other observatory-class missions. MOS exploits today's flight, ground, and operations capabilities, embraces automation, and balances both risk and cost. With operational efficiency as the primary goal, MOS maintains a strong control process by translating lessons learned into efficiency improvements, thereby enabling the MOS processes, teams, and procedures to rapidly evolve from concept (through thorough validation) into in-flight implementation. Operational teaming, planning, and execution are designed to enable re-use. Mission changes, unforeseen events, and continuous improvement have often times forced us to learn to fly anew. Collaborative spacecraft operations and remote science and instrument teams have become well integrated, and worked together to improve and optimize each human, machine, and software-system element. Adaptation to tighter spacecraft margins has facilitated continuous operational improvements via automated and autonomous software coupled with improved human analysis. Based upon what we now know and what we need to improve, adapt, or fix, the projected mission lifetime continues to grow - as does the opportunity for numerous scientific discoveries.

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

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

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

  6. NASA's Spitzer Space Telescope's operational mission experience

    NASA Astrophysics Data System (ADS)

    Wilson, Robert K.; Scott, Charles P.

    2006-06-01

    Spitzer Space Telescope, the fourth and final of NASA's Great Observatories, and the cornerstone to NASA's Origins Program, launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Spitzer has an 85cm diameter beryllium telescope, which operates near absolute zero utilizing a liquid helium cryostat for cooling the telescope. The helium cryostat though designed for a 2.5 year lifetime, through creative usage now has an expected lifetime of 5.5 years. Spitzer has completed its in-orbit checkout/science verification phases and the first two years of nominal operations becoming the first mission to execute astronomical observations from a solar orbit. Spitzer was designed to probe and explore the universe in the infrared utilizing three state of the art detector arrays providing imaging, photometry, and spectroscopy over the 3-160 micron wavelength range. Spitzer is achieving major advances in the study of astrophysical phenomena across the expanses of our universe. Many technology areas critical to future infrared missions have been successfully demonstrated by Spitzer. These demonstrated technologies include lightweight cryogenic optics, sensitive detector arrays, and a high performance thermal system, combining radiation both passive and active cryogenic cooling of the telescope in space following its warm launch. This paper provides an overview of the Spitzer mission, telescope, cryostat, instruments, spacecraft, its orbit, operations and project management approach and related lessons learned.

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

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

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

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

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

  12. CAPACITY: Operational Atmospheric Chemistry Monitoring Missions

    NASA Astrophysics Data System (ADS)

    Kelder, H.; Goede, A.; van Weele, M.

    The ESA project CAPACITY refers to future Operational Atmospheric Chemistry Monitoring Missions. Here operational is meant in the sense that a reliable service of specified information products can be established that satisfies user needs. Monitoring is meant in the sense that long-term continuity and consistency in the quality of the information products can be achieved. The objectives of the project are: To consult with user communities to develop high level information requirements and the form of the information products. To identify and prioritise mission objectives. To derive mission data requirements from the high level user information requirements and iterate these with the users. To set these requirements against observation systems available or approved for the future. To identify missing information products or information products of insufficient quality. To define a global observation system that would satisfy user requirements. The time frame of this operational system is projected to cover the period 2010 to 2020 concurrent with the operational satellites MetOp and NPOESS. In order to address these objectives a large European consortium has been formed consisting of approximately 30 partners from 9 ESA countries (F, D, UK, I, SW, N, DK, B, NL). The project is led by the Royal Netherlands Meteorological Institute (KNMI) and the core team includes the Rutherford Appleton Laboratory, Univ Leicester, Univ Bremen and industry. Four application areas are identified: Protocol Monitoring (Montreal and Kyoto) and Policy Support Air Quality Monitoring and Policy Support (CLRTAP) Long Term Science Issues and Climate Monitoring Forecast Capacity In the derivation of data level 2/3 requirements from high level user requirements the consortium relies on a large group of modellers using satellite data, and of space research institutes with expertise in retrieval and calibration/validation of satellite data as well as Industry with experience in building space

  13. Mission Operations of EO-1 with Onboard Autonomy

    NASA Technical Reports Server (NTRS)

    Tran, Daniel Q.

    2006-01-01

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

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

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

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

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

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

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

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

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

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

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

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

  5. Immersive Environments for Mission Operations: Beyond Mars Pathfinder

    NASA Technical Reports Server (NTRS)

    Wright, J.; Hartman, F.; Cooper, B.

    1998-01-01

    Immersive environments are just beginning to be used to support mission operations at the Jet Propulsion Laboratory. This technology contributed to the Mars Pathfinder Mission in planning sorties for the Sojourner rover.

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

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

  8. Calculation of Operations Efficiency Factors for Mars Surface Missions

    NASA Technical Reports Server (NTRS)

    Laubach, Sharon

    2014-01-01

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

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

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

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

    The Gravity Recovery and Interior Laboratory (GRAIL) mission has placed two orbiters in a low altitude polar orbit around the moon to study its internal structure. GRAIL mission to the Moon offered unique challenges to operatiotn: (1) operate twin-orbiters in parallel, (2) numerous maneuvers, (3) short, compact mission with six unique phases, and (4) detailed contingency planning required.

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

  13. Operations concepts for Mars missions with multiple mobile spacecraft

    NASA Technical Reports Server (NTRS)

    Dias, William C.

    1993-01-01

    Missions are being proposed which involve landing a varying number (anywhere from one to 24) of small mobile spacecraft on Mars. Mission proposals include sample returns, in situ geochemistry and geology, and instrument deployment functions. This paper discusses changes needed in traditional space operations methods for support of rover operations. Relevant differences include more frequent commanding, higher risk acceptance, streamlined procedures, and reliance on additional spacecraft autonomy, advanced fault protection, and prenegotiated decisions. New methods are especially important for missions with several Mars rovers operating concurrently against time limits. This paper also discusses likely mission design limits imposed by operations constraints .

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

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

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

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

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

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

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

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

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

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

  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. The Operations Security Concept for Future ESA Earth Observation Missions

    NASA Astrophysics Data System (ADS)

    Fischer, D.; Bargellini, P.; Merri, M.

    2008-08-01

    Next-generation European earth observation missions will play a critical role in public safety and security infrastructures. This makes it necessary for ESA to protect the communication infrastructure of these missions in order to guarantee their service availability. In this paper, we discuss the development process for a generic earth observation security concept. This concept has been developed as part of a GMES Flight Operation Segment security study with the objective to analyse and select a number of high level security requirements for the missions. Further, we studied the impact of an implementation for these requirements on the operational infrastructure of current earth observation 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. 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.

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

  10. Expert systems and advanced automation for space missions operations

    NASA Technical Reports Server (NTRS)

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

    1990-01-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)

    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.

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

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

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

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

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

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

    NASA Video Gallery

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

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

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

  1. Launch and Early Operation of the MESSENGER Mission

    NASA Astrophysics Data System (ADS)

    Holdridge, Mark E.; Calloway, Andrew B.

    2007-08-01

    On August 3, 2004, at 2:15 a.m. EST, the MESSENGER mission to Mercury began with liftoff of the Delta II 7925H launch vehicle and 1,107-kg spacecraft including seven instruments. MESSENGER is the seventh in the series of NASA Discovery missions, the third to be built and operated by The Johns Hopkins University Applied Physics Laboratory (JHU/APL) following the Near Earth Asteroid Rendezvous (NEAR) Shoemaker and Comet Nucleus Tour (CONTOUR) missions. The MESSENGER team at JHU/APL is using efficient operations approaches developed in support of the low-cost NEAR and CONTOUR operations while incorporating improved approaches for reducing total mission risk. This paper provides an overview of the designs and operational practices implemented to conduct the MESSENGER mission safely and effectively. These practices include proven approaches used on past JHU/APL operations and new improvements implemented to reduce risk, including adherence to time-proven standards of conduct in the planning and implementation of the mission. This paper also discusses the unique challenges of operating in orbit around Mercury, the closest planet to the Sun, and what specific measures are being taken to address those challenges.

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

  3. CCSDS Mission Operations Action Service Core Capabilities

    NASA Technical Reports Server (NTRS)

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

    2009-01-01

    This slide presentation reviews the operations concepts of the command (action) services. Since the consequences of sending the wrong command are unacceptable, the command system provides a collaborative and distributed work environment for flight controllers and operators. The system prescribes a review and approval process where each command is viewed by other individuals before being sent to the vehicle. The action service needs additional capabilities to support he operations concepts of manned space flight. These are : (1) Action Service methods (2) Action attributes (3) Action parameter/argument attributes (4 ) Support for dynamically maintained action data. (5) Publish subscri be capabilities.

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

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

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

  8. The medical mission in NATO operations.

    PubMed

    Klein, L

    2004-01-01

    Medical support during crisis response operations should follow state-of-the-art standards of medicine, but at the same time to take into account more difficult conditions for medical care providing. The results of treatment of patients during crisis response operations should lead to results as close as possible to peacetime treatment. Multinationality has been working well in the Sipovo Multinational Integrated Medical Unit (MIMU) in Bosnia and Herzegovina until now. The mutual co-operation of nations results in a reduction in terms of personnel and material for all participants. It allows efficient use of resources and could be a model for Role 3 care in other hospitals. It has proven to be greater than the sum of its parts. The MIMU concept can be considered a cornerstone that guarantees the required continuity and stability. PMID:15462068

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

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

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

  12. 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. PMID:26446009

  13. Improving the Operations of the Earth Observing One Mission via Automated Mission Planning

    NASA Technical Reports Server (NTRS)

    Chien, Steve A.; Tran, Daniel; Rabideau, Gregg; Schaffer, Steve; Mandl, Daniel; Frye, Stuart

    2010-01-01

    We describe the modeling and reasoning about operations constraints in an automated mission planning system for an earth observing satellite - EO-1. We first discuss the large number of elements that can be naturally represented in an expressive planning and scheduling framework. We then describe a number of constraints that challenge the current state of the art in automated planning systems and discuss how we modeled these constraints as well as discuss tradeoffs in representation versus efficiency. Finally we describe the challenges in efficiently generating operations plans for this mission. These discussions involve lessons learned from an operations model that has been in use since Fall 2004 (called R4) as well as a newer more accurate operations model operational since June 2009 (called R5). We present analysis of the R5 software documenting a significant (greater than 50%) increase in the number of weekly observations scheduled by the EO-1 mission. We also show that the R5 mission planning system produces schedules within 15% of an upper bound on optimal schedules. This operational enhancement has created value of millions of dollars US over the projected remaining lifetime of the EO-1 mission.

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

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

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

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

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

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

  20. DSN co-observing operations to support space VLBI missions

    NASA Technical Reports Server (NTRS)

    Altunin, Valery I.; Kuiper, Thomas B.; Wolken, Pamela R.

    1994-01-01

    Reliable radio astronomy support of space very long baseline interferometry (VLBI) missions by ground radio telescopes is mandatory in order to achieve a high scientific return from the missions. The 70 m DSN antennas along with other ground radio telescopes will perform as the ground segment of the earth-space interferometer. Improvements of radio astronomy VLBI operations at the DSN to achieve higher reliability, efficiency, flexibility, and lower operations costs is a major goal in preparing for radio astronomy support of SVLBI. To help realize this goal, a remote control and monitoring mode for radio astronomy operations at the DSN has been developed.

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

    NASA Technical Reports Server (NTRS)

    McCann, Robert S.

    2010-01-01

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

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

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

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

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

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

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

  8. A mission operations architecture for the 21st century

    NASA Technical Reports Server (NTRS)

    Tai, W.; Sweetnam, D.

    1996-01-01

    An operations architecture is proposed for low cost missions beyond the year 2000. The architecture consists of three elements: a service based architecture; a demand access automata; and distributed science hubs. The service based architecture is based on a set of standard multimission services that are defined, packaged and formalized by the deep space network and the advanced multi-mission operations system. The demand access automata is a suite of technologies which reduces the need to be in contact with the spacecraft, and thus reduces operating costs. The beacon signaling, the virtual emergency room, and the high efficiency tracking automata technologies are described. The distributed science hubs provide information system capabilities to the small science oriented flight teams: individual access to all traditional mission functions and services; multimedia intra-team communications, and automated direct transparent communications between the scientists and the instrument.

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

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

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

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

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

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

    NASA Technical Reports Server (NTRS)

    Gal-Edd, Jonathan S.; Cheuvront, Allan

    2015-01-01

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

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

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

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

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

    NASA Astrophysics Data System (ADS)

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

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

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

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

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

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

  3. Space Mission Operations Ground Systems Integration Customer Service

    NASA Technical Reports Server (NTRS)

    Roth, Karl

    2014-01-01

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  18. Data acquisition system for operational earth observation missions

    NASA Technical Reports Server (NTRS)

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

    1972-01-01

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  13. 23 CFR 950.7 - Interoperability requirements.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... 23 Highways 1 2013-04-01 2013-04-01 false Interoperability requirements. 950.7 Section 950.7 Highways FEDERAL HIGHWAY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION INTELLIGENT TRANSPORTATION SYSTEMS ELECTRONIC TOLL COLLECTION § 950.7 Interoperability requirements. (a) For any toll facility operating pursuant to authority under a 1604 toll...

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

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

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

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

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

  20. Space Network Interoperability Panel (SNIP) study

    NASA Technical Reports Server (NTRS)

    Ryan, Thomas; Lenhart, Klaus; Hara, Hideo

    1991-01-01

    The Space Network Interoperability Panel (SNIP) study is a tripartite study that involves the National Aeronautics and Space Administration (NASA), the European Space Agency (ESA), and the National Space Development Agency (NASDA) of Japan. SNIP involves an ongoing interoperability study of the Data Relay Satellite (DRS) Systems of the three organizations. The study is broken down into two parts; Phase one deals with S-band (2 GHz) interoperability and Phase two deals with Ka-band (20/30 GHz) interoperability (in addition to S-band). In 1987 the SNIP formed a Working Group to define and study operations concepts and technical subjects to assure compatibility of the international data relay systems. Since that time a number of Panel and Working Group meetings have been held to continue the study. Interoperability is of interest to the three agencies because it offers a number of potential operation and economic benefits. This paper presents the history and status of the SNIP study.

  1. Mission operations costs for scientific spacecraft: The revolution that is needed

    NASA Astrophysics Data System (ADS)

    Ledbetter, Kenneth W.

    1995-01-01

    An examination is made of the budget expenditure for Mission Operations in Office of Space Science missions since the resumption of flights after the 1986 Challenger accident, and projections shown for future costs if the same mission operations philosophy continues. It is shown that NASA cannot afford to continue with the same strategy, and must therefore find innovative approaches to accomplishing missions for less cost. A challenge is issued for a revolution in the way future missions are designed and operated. The mission operations concept needs to be generated early and applied to guide the design of both mission and spacecraft. Suggestions for revolutionary thinking are provided in areas of the mission, the spacecraft, the ground system, and the flight team designs. The bottom line is emphasized that to lower operations costs, we must remove labor-intensive tasks from operational processes.

  2. Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

    NASA Technical Reports Server (NTRS)

    Johnson, Teresa A.

    2006-01-01

    Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

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

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

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

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

  8. Asteroid Redirect Mission Robotic Trajectory and Crew Operations

    NASA Video Gallery

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  4. Achieving Interoperability through Data Virtualization

    NASA Astrophysics Data System (ADS)

    Xing, Z.

    2015-12-01

    Data Interoperability is a challenging problem. Different approaches exist.In this presentation, we would like to share our experienceon webification science (w10n-sci), an information technology thatvirtualizes arbitrary data resources and makes them directly usablevia a simple and uniform application programmable interface.W10n-sci has been successfully applied to all major NASA scientificdisciplines and used by an increasing number of missions and projects.We will provide an overview of w10n-sci and elaborate onhow it can help data users in a data world that diversity always prevails.

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

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

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

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

  9. Multi-mission Observation Operator (M2O2) service for mission-independent data assimilation process

    NASA Astrophysics Data System (ADS)

    Weidner, R. J.; Lee, M.; Lynnes, C.

    2012-12-01

    Multi-mission observation operator (M2O2) system facilitates simultaneous assimilation of the retrieved atmospheric components from multiple missions by streamlining the interface between model systems and observation data services. The M2O2 system is composed of two types of transformation services, a data transformation service that composes assimilation information from the level 2 mission data products, and a model transformation service that provides multi-mission observation force function integrating the assimilation information from the data transformation service. The prototype M2O2 system was employed for simultaneous assimilation of Ozone observations from Microwave Limb Sounder (MLS) and Tropospheric emission sounder (TES) with the GEOSChem-adjoint model system. Under NASA's Advancing Collaborative Connections for Earth System Science (ACCESS) program, we are developing an operational M2O2 service as an integral part of the Goddard Earth System Data and Information Service Center (GES DISC) utilizing the "on-demand" quality filtering and file format conversion capabilities. In this paper, we discuss the M2O2 web-service-protocol that allows customization of mission-unique quality control, data field extraction, and data product integration, and the M2O2 assimilation software layer that interacts with the M2O2 web-service and delivers mission-independent assimilation information to the model community.

  10. Kidney Shear Wave Speed Values in Subjects with and without Renal Pathology and Inter-Operator Reproducibility of Acoustic Radiation Force Impulse Elastography (ARFI) - Preliminary Results

    PubMed Central

    Bob, Flaviu; Bota, Simona; Sporea, Ioan; Sirli, Roxana; Petrica, Ligia; Schiller, Adalbert

    2014-01-01

    Aim to assess the inter-operator reproducibility of kidney shear wave speed, evaluated by means of Acoustic Radiation Force Impulse (ARFI) elastography, and the factors which influence it. Methods Our prospective pilot study included 107 subjects with or without kidney pathology in which kidney shear wave speed was evaluated by means of ARFI elastography. Intraclass correlation coefficient (ICC) was used to assess ARFI elastography reproducibility. Results A strong agreement was obtained between kidney shear wave speed measurements obtained by the two operators: ICC = 0.71 (right kidney) and 0.69 (left kidney). Smaller ICCs were obtained in “healthy subjects”, as compared to patients with kidney diseases (0.68 vs. 0.75), in women as compared with men (0.59 vs. 0.78), in subjects younger than 50 years as compared with those aged at least 50 years (0.63 vs. 0.71), in obese as compared with normal weight and overweight subjects (0.36 vs. 0.66 and 0.78) and in case of measurements depth <4 cm or >6 cm as compared with those performed at a depth of 4–6 cm from the skin (0.32 and 0.60 vs. 0.81). Conclusion ARFI elastography is a reproducible method for kidney shear wave speed assessment. PMID:25426849