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.

Shared mission operations concept

NASA Technical Reports Server (NTRS)

Spradlin, Gary L.; Rudd, Richard P.; Linick, Susan H.

1994-01-01

Historically, new JPL flight projects have developed a Mission Operations System (MOS) as unique as their spacecraft, and have utilized a mission-dedicated staff to monitor and control the spacecraft through the MOS. NASA budgetary pressures to reduce mission operations costs have led to the development and reliance on multimission ground system capabilities. The use of these multimission capabilities has not eliminated an ongoing requirement for a nucleus of personnel familiar with a given spacecraft and its mission to perform mission-dedicated operations. The high cost of skilled personnel required to support projects with diverse mission objectives has the potential for significant reduction through shared mission operations among mission-compatible projects. Shared mission operations are feasible if: (1) the missions do not conflict with one another in terms of peak activity periods, (2) a unique MOS is not required, and (3) there is sufficient similarity in the mission profiles so that greatly different skills would not be required to support each mission. This paper will further develop this shared mission operations concept. We will illustrate how a Discovery-class mission would enter a 'partner' relationship with the Voyager Project, and can minimize MOS development and operations costs by early and careful consideration of mission operations requirements.

2005 Net Centric Operations, Interoperability and Systems Integration Conference - Facilitating Net Centric Operations and Warfare

DTIC Science & Technology

2005-03-24

1 :45PM- 3 :30PM Panel: Establishing a Business Mission Area in the Department of...Minimum MaximumLEVEL OF INTEROPERABILITY Level 1 Level 2 Level 3 Level 4 10 COTS Native IP Network IP TCP UDP Network QoS Layer IIOP NTP SNMP Legacy...2005 Page 1 3 /27/2005 Page 2 3 /27/2005 Page 3 3 /27/2005 Page 4 3 /27/2005 Page 5 3 /27/2005 Page 6 3 /27/2005 Page 7 3 /27/2005 Page 8 3 /27/2005 Page 9 3

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.

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.

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

PubMed

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

2017-01-01

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

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

PubMed Central

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

2017-01-01

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

Supply Chain Interoperability Measurement

DTIC Science & Technology

2015-06-19

Supply Chain Interoperability Measurement DISSERTATION June 2015 Christos E. Chalyvidis, Major, Hellenic Air...ENS-DS-15-J-001 SUPPLY CHAIN INTEROPERABILITY MEASUREMENT DISSERTATION Presented to the Faculty Department of Operational Sciences...INTEROPERABILITY MEASUREMENT Christos E. Chalyvidis, BS, MSc. Major, Hellenic Air Force Committee Membership: Dr. A.W. Johnson Chair

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.

Operations and Plans: International Military Rationalization, Standardization, and Interoperability

DTIC Science & Technology

1989-02-15

Army Regulation 34–1 Operations and Plans International Military Rationalization , Standardization, and Interoperability Headquarters Department of...YYYY) 15-02-1997 2. REPORT TYPE 3. DATES COVERED (FROM - TO) xx-xx-1997 to xx-xx-1997 4. TITLE AND SUBTITLE International Military Rationalization ...DSN 427-9007 Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39.18 SUMMARY of CHANGE AR 34–1 International Military Rationalization

Mission operations technology

NASA Astrophysics Data System (ADS)

Varsi, Giulio

In the last decade, the operation of a spacecraft after launch has emerged as a major component of the total cost of the mission. This trend is sustained by the increasing complexity, flexibility, and data gathering capability of the space assets and by their greater reliability and consequent longevity. The trend can, however, be moderated by the progressive transfer of selected functions from the ground to the spacecraft and by application, on the ground, of new technology. Advances in ground operations derive from the introduction in the mission operations environment of advanced microprocessor-based workstations in the class of a few million instructions per second and from the selective application of artificial intelligence technology. In the last few years a number of these applications have been developed, tested in operational settings and successfully demonstrated to users. Some are now being integrated in mission operations facilities. An analysis of mission operations indicates that the key areas are: concurrent control of multiple missions; automated/interactive production of command sequences of high integrity at low cost; automated monitoring of spacecraft health and automated aides for fault diagnosis; automated allocation of resources; automated processing of science data; and high-fidelity, high-speed spacecraft simulation. Examples of major advances in selected areas are described.

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

PubMed

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

2012-04-01

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

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

Autonomous Mission Operations

NASA Technical Reports Server (NTRS)

Frank, Jeremy; Spirkovska, Lilijana; McCann, Rob; Wang, Lui; Pohlkamp, Kara; Morin, Lee

2012-01-01

NASA's Advanced Exploration Systems Autonomous Mission Operations (AMO) project conducted an empirical investigation of the impact of time-delay on todays 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 crew members 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.

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

EPA Science Inventory

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

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

PubMed Central

2014-01-01

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

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.

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.

Discovery Planetary Mission Operations Concepts

NASA Technical Reports Server (NTRS)

Coffin, R.

1994-01-01

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

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.

Multi-disciplinary interoperability challenges (Ian McHarg Medal Lecture)

NASA Astrophysics Data System (ADS)

Annoni, Alessandro

2013-04-01

Global sustainability research requires multi-disciplinary efforts to address the key research challenges to increase our understanding of the complex relationships between environment and society. For this reason dependence on ICT systems interoperability is rapidly growing but, despite some relevant technological improvement is observed, in practice operational interoperable solutions are still lacking. Among the causes is the absence of a generally accepted definition of "interoperability" in all its broader aspects. In fact the concept of interoperability is just a concept and the more popular definitions are not addressing all challenges to realize operational interoperable solutions. The problem become even more complex when multi-disciplinary interoperability is required because in that case solutions for interoperability of different interoperable solution should be envisaged. In this lecture the following definition will be used: "interoperability is the ability to exchange information and to use it". In the lecture the main challenges for addressing multi-disciplinary interoperability will be presented and a set of proposed approaches/solutions shortly introduced.

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

PubMed

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

2015-02-01

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

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.

Secure and interoperable communication infrastructures for PPDR organisations

NASA Astrophysics Data System (ADS)

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

2016-05-01

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

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.

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.

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.

Mars Polar Lander Mission Distributed Operations

NASA Technical Reports Server (NTRS)

Norris, J.; Backes, P.; Slostad, J.; Bonitz, R.; Tharp, G.; Tso, K.

2000-01-01

The Mars Polar Lander (MPL) mission is the first planetary mission to use Internet-based distributed ground operations where scientists and engineers collaborate in daily mission operations from multiple geographically distributed locations via the Internet.

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.

Infusion of innovative technologies for mission operations

NASA Astrophysics Data System (ADS)

Donati, Alessandro

2010-11-01

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

Apollo Soyuz mission planning and operations

NASA Technical Reports Server (NTRS)

Frank, M. P., III

1976-01-01

The paper describes the Apollo Soyuz project from the points of view of working group organization, mission plan definition, joint operations concept, and mission preparation. The concept for joint operations considered contingency situations as well as nominal operations. Preparations for the joint flight included cooperative tracking tests and combined training of the flight crews and mission control personnel.

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.

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.

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.

An operations concept methodology to achieve low-cost mission operations

NASA Technical Reports Server (NTRS)

Ledbetter, Kenneth W.; Wall, Stephen D.

1993-01-01

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

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.

UHF (Ultra High Frequency) Military Satellite Communications Ground Equipment Interoperability.

DTIC Science & Technology

1986-10-06

crisis management requires interoperability between various services. These short-term crises often arise from unforeseen circumstances in which...Scheduler Qualcomm has prepared an interoperability study for the JTC3A (Reference 15) as a TA/CE for USCINCLANT ROC 5-84 requirements. It has defined a...interoperability is fundamental. A number of operational crises have occurred where interoperable communications or the lack of interoperable

Extravehicular activity space suit interoperability.

PubMed

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

1995-10-01

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

Low-Cost Mission Operations

NASA Technical Reports Server (NTRS)

Squibb, G. F.; Heftman, K.

1996-01-01

This paper discusses the transition between traditional planetary missions (requiring constant operational control and limited in size only by booster capability) and the cheaper missions of the New Millennium spacecraft, which will be smaller and will have a great deal of autonomy.

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.

NASA and Industry Benefits of ACTS High Speed Network Interoperability Experiments

NASA Technical Reports Server (NTRS)

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

2000-01-01

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

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

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.

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.

Tier-scalable reconnaissance: the challenge of sensor optimization, sensor deployment, sensor fusion, and sensor interoperability

NASA Astrophysics Data System (ADS)

Fink, Wolfgang; George, Thomas; Tarbell, Mark A.

2007-04-01

Robotic reconnaissance operations are called for in extreme environments, not only those such as space, including planetary atmospheres, surfaces, and subsurfaces, but also in potentially hazardous or inaccessible operational areas on Earth, such as mine fields, battlefield environments, enemy occupied territories, terrorist infiltrated environments, or areas that have been exposed to biochemical agents or radiation. Real time reconnaissance enables the identification and characterization of transient events. A fundamentally new mission concept for tier-scalable reconnaissance of operational areas, originated by Fink et al., is aimed at replacing the engineering and safety constrained mission designs of the past. The tier-scalable paradigm integrates multi-tier (orbit atmosphere surface/subsurface) and multi-agent (satellite UAV/blimp surface/subsurface sensing platforms) hierarchical mission architectures, introducing not only mission redundancy and safety, but also enabling and optimizing intelligent, less constrained, and distributed reconnaissance in real time. Given the mass, size, and power constraints faced by such a multi-platform approach, this is an ideal application scenario for a diverse set of MEMS sensors. To support such mission architectures, a high degree of operational autonomy is required. Essential elements of such operational autonomy are: (1) automatic mapping of an operational area from different vantage points (including vehicle health monitoring); (2) automatic feature extraction and target/region-of-interest identification within the mapped operational area; and (3) automatic target prioritization for close-up examination. These requirements imply the optimal deployment of MEMS sensors and sensor platforms, sensor fusion, and sensor interoperability.

Mars mission science operations facilities design

NASA Technical Reports Server (NTRS)

Norris, Jeffrey S.; Wales, Roxana; Powell, Mark W.; Backes, Paul G.; Steinke, Robert C.

2002-01-01

A variety of designs for Mars rover and lander science operations centers are discussed in this paper, beginning with a brief description of the Pathfinder science operations facility and its strengths and limitations. Particular attention is then paid to lessons learned in the design and use of operations facilities for a series of mission-like field tests of the FIDO prototype Mars rover. These lessons are then applied to a proposed science operations facilities design for the 2003 Mars Exploration Rover (MER) mission. Issues discussed include equipment selection, facilities layout, collaborative interfaces, scalability, and dual-purpose environments. The paper concludes with a discussion of advanced concepts for future mission operations centers, including collaborative immersive interfaces and distributed operations. This paper's intended audience includes operations facility and situation room designers and the users of these environments.

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.

Plugfest 2009: Global Interoperability in Telerobotics and Telemedicine

PubMed Central

King, H. Hawkeye; Hannaford, Blake; Kwok, Ka-Wai; Yang, Guang-Zhong; Griffiths, Paul; Okamura, Allison; Farkhatdinov, Ildar; Ryu, Jee-Hwan; Sankaranarayanan, Ganesh; Arikatla, Venkata; Tadano, Kotaro; Kawashima, Kenji; Peer, Angelika; Schauß, Thomas; Buss, Martin; Miller, Levi; Glozman, Daniel; Rosen, Jacob; Low, Thomas

2014-01-01

Despite the great diversity of teleoperator designs and applications, their underlying control systems have many similarities. These similarities can be exploited to enable inter-operability between heterogeneous systems. We have developed a network data specification, the Interoperable Telerobotics Protocol, that can be used for Internet based control of a wide range of teleoperators. In this work we test interoperable telerobotics on the global Internet, focusing on the telesurgery application domain. Fourteen globally dispersed telerobotic master and slave systems were connected in thirty trials in one twenty four hour period. Users performed common manipulation tasks to demonstrate effective master-slave operation. With twenty eight (93%) successful, unique connections the results show a high potential for standardizing telerobotic operation. Furthermore, new paradigms for telesurgical operation and training are presented, including a networked surgery trainer and upper-limb exoskeleton control of micro-manipulators. PMID:24748993

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

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

PubMed Central

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

2015-01-01

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

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.

Smart Grid Interoperability Maturity Model

DOE Office of Scientific and Technical Information (OSTI.GOV)

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

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 organizationalmore » 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.« less

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.

Approaching semantic interoperability in Health Level Seven

PubMed Central

Alschuler, Liora

2010-01-01

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

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

Interoperability Context-Setting Framework

DOE Office of Scientific and Technical Information (OSTI.GOV)

Widergren, Steven E.; Hardin, Dave; Ambrosio, Ron

2007-01-31

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

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

Implementing Interoperability in the Seafood Industry: Learning from Experiences in Other Sectors.

PubMed

Bhatt, Tejas; Gooch, Martin; Dent, Benjamin; Sylvia, Gilbert

2017-08-01

Interoperability of communication and information technologies within and between businesses operating along supply chains is being pursued and implemented in numerous industries worldwide to increase the efficiency and effectiveness of operations. The desire for greater interoperability is also driven by the need to reduce business risk through more informed management decisions. Interoperability is achieved by the development of a technology architecture that guides the design and implementation of communication systems existing within individual businesses and between businesses comprising the supply chain. Technology architectures are developed through a purposeful dialogue about why the architecture is required, the benefits and opportunities that the architecture offers the industry, and how the architecture will translate into practical results. An assessment of how the finance, travel, and health industries and a sector of the food industry-fresh produce-have implemented interoperability was conducted to identify lessons learned that can aid the development of interoperability in the seafood industry. The findings include identification of the need for strong, effective governance during the establishment and operation of an interoperability initiative to ensure the existence of common protocols and standards. The resulting insights were distilled into a series of principles for enabling syntactic and semantic interoperability in any industry, which we summarize in this article. Categorized as "structural," "operational," and "integrative," the principles describe requirements and solutions that are pivotal to enabling businesses to create and capture value from full chain interoperability. The principles are also fundamental to allowing governments and advocacy groups to use traceability for public good. © 2017 Institute of Food Technologists®.

Telemedicine system interoperability architecture: concept description and architecture overview.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Craft, Richard Layne, II

2004-05-01

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

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

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

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.

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.

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.

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.

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.

The NASA Mission Operations and Control Architecture Program

NASA Technical Reports Server (NTRS)

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

1994-01-01

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

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.

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.

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.

Integrated mission management operations

NASA Technical Reports Server (NTRS)

1971-01-01

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

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.

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

DTIC Science & Technology

2010-12-01

This involves zeroing and recreating the interoperability arrays and other variables used in the simulation. Since the constants do not change from run......Using this algorithm, the process of encrypting/decrypting data requires very little computation, and the generation of the random pads can be

Shuttle remote manipulator system mission preparation and operations

NASA Technical Reports Server (NTRS)

Smith, Ernest E., Jr.

1989-01-01

The preflight planning, analysis, procedures development, and operations support for the Space Transportation System payload deployment and retrieval missions utilizing the Shuttle Remote Manipulator System are summarized. Analysis of the normal operational loads and failure induced loads and motion are factored into all procedures. Both the astronaut flight crews and the Mission Control Center flight control teams receive considerable training for standard and mission specific operations. The real time flight control team activities are described.

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

Overall view of Mission Operations Control in Mission Control Center

NASA Image and Video Library

1969-05-18

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

Improving data discoverability, accessibility, and interoperability with the Esri ArcGIS Platform at the NASA Atmospheric Science Data Center (ASDC).

NASA Astrophysics Data System (ADS)

Tisdale, M.

2017-12-01

NASA's Atmospheric Science Data Center (ASDC) is operationally using the Esri ArcGIS Platform to improve data discoverability, accessibility and interoperability to meet the diversifying user requirements from government, private, public and academic communities. The ASDC is actively working to provide their mission essential datasets as ArcGIS Image Services, Open Geospatial Consortium (OGC) Web Mapping Services (WMS), and OGC Web Coverage Services (WCS) while leveraging the ArcGIS multidimensional mosaic dataset structure. Science teams at ASDC are utilizing these services through the development of applications using the Web AppBuilder for ArcGIS and the ArcGIS API for Javascript. These services provide greater exposure of ASDC data holdings to the GIS community and allow for broader sharing and distribution to various end users. These capabilities provide interactive visualization tools and improved geospatial analytical tools for a mission critical understanding in the areas of the earth's radiation budget, clouds, aerosols, and tropospheric chemistry. The presentation will cover how the ASDC is developing geospatial web services and applications to improve data discoverability, accessibility, and interoperability.

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;

Special issue on enabling open and interoperable access to Planetary Science and Heliophysics databases and tools

NASA Astrophysics Data System (ADS)

2018-01-01

The large amount of data generated by modern space missions calls for a change of organization of data distribution and access procedures. Although long term archives exist for telescopic and space-borne observations, high-level functions need to be developed on top of these repositories to make Planetary Science and Heliophysics data more accessible and to favor interoperability. Results of simulations and reference laboratory data also need to be integrated to support and interpret the observations. Interoperable software and interfaces have recently been developed in many scientific domains. The Virtual Observatory (VO) interoperable standards developed for Astronomy by the International Virtual Observatory Alliance (IVOA) can be adapted to Planetary Sciences, as demonstrated by the VESPA (Virtual European Solar and Planetary Access) team within the Europlanet-H2020-RI project. Other communities have developed their own standards: GIS (Geographic Information System) for Earth and planetary surfaces tools, SPASE (Space Physics Archive Search and Extract) for space plasma, PDS4 (NASA Planetary Data System, version 4) and IPDA (International Planetary Data Alliance) for planetary mission archives, etc, and an effort to make them interoperable altogether is starting, including automated workflows to process related data from different sources.

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.

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

NASA Image and Video Library

1983-04-05

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

Organisational Interoperability: Evaluation and Further Development of the OIM Model

DTIC Science & Technology

2003-06-01

an Organizational Interoperability Maturity Model (OIM) to evaluate interoperability at the organizational level. The OIM considers the human ... activity aspects of military operations, which are not covered in other models. This paper describes how the model has been used to identify problems and to

Managing the Implementation of Mission Operations Automation

NASA Technical Reports Server (NTRS)

Sodano, R.; Crouse, P.; Odendahl, S.; Fatig, M.; McMahon, K.; Lakin, J.

2006-01-01

Reducing the cost of mission operations has necessitated a high level of automation both on spacecraft and ground systems. While automation on spacecraft is implemented during the design phase, ground system automation tends to be implemented during the prime mission operations phase. Experience has shown that this tendency for late automation development can be hindered by several factors: additional hardware and software resources may need to be procured; software must be developed and tested on a non-interference basis with primary operations with limited manpower; and established procedures may not be suited for automation requiring substantial rework. In this paper we will review the experience of successfully automating mission operations for seven on-orbit missions: the Compton Gamma Ray Observatory (CGRO), the Rossi X-Ray Timing Explorer (RXTE), the Advanced Composition Explorer (ACE), the Far Ultraviolet Spectroscopic Explorer (FUSE), Interplanetary Physics Laboratory (WIND), Polar Plasma Laboratory (POLAR), and the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE). We will provide lessons learned in areas such as: spacecraft recorder management, procedure development, lights out commanding from the ground system vs. stored command loads, spacecraft contingency response time, and ground station interfaces. Implementing automation strategies during the mission concept and spacecraft integration and test phase as the most efficient method will be discussed.

Advancing Autonomous Operations Technologies for NASA Missions

NASA Technical Reports Server (NTRS)

Cruzen, Craig; Thompson, Jerry T.

2013-01-01

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

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 .

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.

System and methods of resource usage using an interoperable management framework

DOE Office of Scientific and Technical Information (OSTI.GOV)

Heileman, Gregory L.; Jamkhedkar, Pramod A.; Lamb, Christopher C.

Generic rights expression language allowing interoperability across different computing environments including resource usage of different applications. A formal framework for usage management provides scaffolding upon which interoperable usage management systems can be built. Certain features of the framework are standardized, such as the operational semantics, including areas free of standards that necessitate choice and innovation to achieve a balance of flexibility and usability for interoperability in usage management systems.

Earth observation mission operation of COMS during in-orbit test

NASA Astrophysics Data System (ADS)

Cho, Young-Min

2011-11-01

Communication Ocean Meteorological Satellite (COMS) for the hybrid mission of meteorological observation, ocean monitoring, and telecommunication service was launched onto Geostationary Earth Orbit on June 27, 2010 and it is currently under normal operation service after the In-Orbit Test (IOT) phase. The COMS is located on 128.2° East of the geostationary orbit. In order to perform the three missions, the COMS has 3 separate payloads, the meteorological imager (MI), the Geostationary Ocean Color Imager (GOCI), and the Ka-band antenna. Each payload is dedicated to one of the three missions, respectively. The MI and GOCI perform the Earth observation mission of meteorological observation and ocean monitoring, respectively. During the IOT phase the functionality and the performance of many aspects of the COMS satellite and ground station have been checked through the Earth observation mission operation for the observation of the meteorological phenomenon over several areas of the Earth and the monitoring of marine environments around the Korean peninsula. The Earth observation mission operation of COMS during the IOT phase is introduced in terms of mission operation characteristics, mission planning, and mission operation results for the missions of meteorological observation and ocean monitoring, respectively.

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

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.

Coalition readiness management system preliminary interoperability experiment (CReaMS PIE)

NASA Astrophysics Data System (ADS)

Clark, Peter; Ryan, Peter; Zalcman, Lucien; Robbie, Andrew

2003-09-01

The United States Navy (USN) has initiated the Coalition Readiness Management System (CReaMS) Initiative to enhance coalition warfighting readiness through advancing development of a team interoperability training and combined mission rehearsal capability. It integrates evolving cognitive team learning principles and processes with advanced technology innovations to produce an effective and efficient team learning environment. The JOint Air Navy Networking Environment (JOANNE) forms the Australian component of CReaMS. The ultimate goal is to link Australian Defence simulation systems with the USN Battle Force Tactical Training (BFTT) system to demonstrate and achieve coalition level warfare training in a synthetic battlespace. This paper discusses the initial Preliminary Interoperability Experiment (PIE) involving USN and Australian Defence establishments.

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.

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.

Making adaptable systems work for mission operations: A case study

NASA Technical Reports Server (NTRS)

Holder, Barbara E.; Levesque, Michael E.

1993-01-01

The Advanced Multimission Operations System (AMMOS) at NASA's Jet Propulsion Laboratory is based on a highly adaptable multimission ground data system (MGDS) for mission operations. The goal for MGDS is to support current flight project science and engineering personnel and to meet the demands of future missions while reducing associated operations and software development costs. MGDS has become a powerful and flexible mission operations system by using a network of heterogeneous workstations, emerging open system standards, and selecting an adaptable tools-based architecture. Challenges in developing adaptable systems for mission operations and the benefits of this approach are described.

Systems Engineering Challenges for GSFC Space Science Mission Operations

NASA Technical Reports Server (NTRS)

Thienel, Julie; Harman, Richard R.

2017-01-01

The NASA Goddard Space Flight Center Space Science Mission Operations (SSMO) project currently manages19 missions for the NASA Science Mission Directorate, within the Planetary, Astrophysics, and Heliophysics Divisions. The mission lifespans range from just a few months to more than20 years. The WIND spacecraft, the oldest SSMO mission, was launched in 1994. SSMO spacecraft reside in low earth, geosynchronous,highly elliptical, libration point, lunar, heliocentric,and Martian orbits. SSMO spacecraft range in size from 125kg (Aeronomy of Ice in the Mesosphere (AIM)) to over 4000kg (Fermi Gamma-Ray Space Telescope (Fermi)). The attitude modes include both spin and three-axis stabilized, with varying requirements on pointing accuracy. The spacecraft are operated from control centers at Goddard and off-site control centers;the Lunar Reconnaissance Orbiter (LRO), the Solar Dynamics Observatory (SDO) and Magnetospheric MultiScale (MMS)mission were built at Goddard. The Advanced Composition Explorer (ACE) and Wind are operated out of a multi-mission operations center, which will also host several SSMO-managed cubesats in 2017. This paper focuses on the systems engineeringchallenges for such a large and varied fleet of spacecraft.

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

A distributed component framework for science data product interoperability

NASA Technical Reports Server (NTRS)

Crichton, D.; Hughes, S.; Kelly, S.; Hardman, S.

2000-01-01

Correlation of science results from multi-disciplinary communities is a difficult task. Traditionally data from science missions is archived in proprietary data systems that are not interoperable. The Object Oriented Data Technology (OODT) task at the Jet Propulsion Laboratory is working on building a distributed product server as part of a distributed component framework to allow heterogeneous data systems to communicate and share scientific results.

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.

Towards technical interoperability in telemedicine.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Craft, Richard Layne, II

2004-05-01

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

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.

Interoperability at ESA Heliophysics Science Archives: IVOA, HAPI and other implementations

NASA Astrophysics Data System (ADS)

Martinez-Garcia, B.; Cook, J. P.; Perez, H.; Fernandez, M.; De Teodoro, P.; Osuna, P.; Arnaud, M.; Arviset, C.

2017-12-01

The data of ESA heliophysics science missions are preserved at the ESAC Science Data Centre (ESDC). The ESDC aims for the long term preservation of those data, which includes missions such as Ulysses, Soho, Proba-2, Cluster, Double Star, and in the future, Solar Orbiter. Scientists have access to these data through web services, command line and graphical user interfaces for each of the corresponding science mission archives. The International Virtual Observatory Alliance (IVOA) provides technical standards that allow interoperability among different systems that implement them. By adopting some IVOA standards, the ESA heliophysics archives are able to share their data with those tools and services that are VO-compatible. Implementation of those standards can be found in the existing archives: Ulysses Final Archive (UFA) and Soho Science Archive (SSA). They already make use of VOTable format definition and Simple Application Messaging Protocol (SAMP). For re-engineered or new archives, the implementation of services through Table Access Protocol (TAP) or Universal Worker Service (UWS) will leverage this interoperability. This will be the case for the Proba-2 Science Archive (P2SA) and the Solar Orbiter Archive (SOAR). We present here which IVOA standards were already used by the ESA Heliophysics archives in the past and the work on-going.

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.

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.

Medical System Concept of Operations for Mars Exploration Missions

NASA Technical Reports Server (NTRS)

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

2017-01-01

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

Maturity model for enterprise interoperability

NASA Astrophysics Data System (ADS)

Guédria, Wided; Naudet, Yannick; Chen, David

2015-01-01

Historically, progress occurs when entities communicate, share information and together create something that no one individually could do alone. Moving beyond people to machines and systems, interoperability is becoming a key factor of success in all domains. In particular, interoperability has become a challenge for enterprises, to exploit market opportunities, to meet their own objectives of cooperation or simply to survive in a growing competitive world where the networked enterprise is becoming a standard. Within this context, many research works have been conducted over the past few years and enterprise interoperability has become an important area of research, ensuring the competitiveness and growth of European enterprises. Among others, enterprises have to control their interoperability strategy and enhance their ability to interoperate. This is the purpose of the interoperability assessment. Assessing interoperability maturity allows a company to know its strengths and weaknesses in terms of interoperability with its current and potential partners, and to prioritise actions for improvement. The objective of this paper is to define a maturity model for enterprise interoperability that takes into account existing maturity models while extending the coverage of the interoperability domain. The assessment methodology is also presented. Both are demonstrated with a real case study.

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.

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.

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.

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

NASA Astrophysics Data System (ADS)

Tisdale, M.

2016-12-01

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

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.

Regional interoperability: making systems connect in complex disasters.

PubMed

Briggs, Susan Miller

2009-08-01

Effective use of the Incident Command System (ICS) is the key to regional interoperability. Many different organizations with different command structures and missions respond to a disaster. The ICS allows different kinds of agencies (fire, police, and medical) to work together effectively in response to a disaster. Functional requirements, not titles, determine the organizational hierarchy of the ICS structure. The ICS is a modular/adaptable system for all disasters regardless of etiology and for all organizations regardless of size.

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

Smart repeater system for communications interoperability during multiagency law enforcement operations

NASA Astrophysics Data System (ADS)

Crutcher, Richard I.; Jones, R. W.; Moore, Michael R.; Smith, S. F.; Tolley, Alan L.; Rochelle, Robert W.

1997-02-01

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.

Managing Interoperability for GEOSS - A Report from the SIF

NASA Astrophysics Data System (ADS)

Khalsa, S. J.; Actur, D.; Nativi, S.; Browdy, S.; Eglitis, P.

2009-04-01

The Global Earth Observation System of Systems (GEOSS) is a coordinating and integrating framework for Earth observing and information systems, which are contributed on a voluntary basis by Members and Participating Organizations of the intergovernmental Group on Earth Observations (GEO). GEOSS exists to support informed decision making for the benefit of society, including the implementation of international environmental treaty obligations. GEO Members and Participating organizations use the GEOSS Common Infrastructure (GCI) to register their Earth observation resources, thereby making them discoverable and consumable by both humans and client applications. Essential to meeting GEO user needs is a process for supporting interoperability of observing, processing, modeling and dissemination capabilities. The GEO Standards and Interoperability Forum (SIF) was created to develop, implement and oversee this process. The SIF supports GEO organizations contributing resources to the GEOSS by helping them understand and work with the GEOSS interoperability guidelines and encouraging them to register their "interoperability arrangements" (standards or other ad hoc arrangements for interoperability) in the GEOSS standards registry, which is part of the GCI. These registered interoperability arrangements support the actual services used to achieve interoperability of systems. By making information about these interoperability arrangements available to users of the GEOSS the SIF enhances the understanding and utility of contributed resources. We describe the procedures that the SIF has enacted to carry out its work. To operate effectively the SIF uses a workflow system and is establishing a set of regional teams and domain experts. In the near term our work has focused on population and review of the GEOSS Standards Registry, but we are also developing approaches to achieving progressive convergence on, and uptake of, an optimal set of interoperability arrangements for all of

An Air Operations Division Live, Virtual, and Constructive (LVC) Corporate Interoperability Standards Development Strategy

DTIC Science & Technology

2011-07-01

Orlando, Florida, September 2009, 09F- SIW -090. [HLA (2000) - 1] - Modeling and Simulation Standard - High Level Architecture (HLA) – Framework and...Simulation Interoperability Workshop, Orlando, FL, USA, September 2009, 09F- SIW -023. [MaK] - www.mak.com [MIL-STD-3011] - MIL-STD-3011...Spring Simulation Interoperability Workshop, Norfolk, VA, USA, March 2007, 07S- SIW -072. [Ross] - Ross, P. and Clark, P. (2005), “Recommended

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

EVA safety: Space suit system interoperability

NASA Technical Reports Server (NTRS)

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

1995-01-01

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

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.

Lessons Learned from Optical Payload for Lasercomm Science (OPALS) Mission Operations

NASA Technical Reports Server (NTRS)

Sindiy, Oleg V.; Abrahamson, Matthew J.; Biswas, Abhijit; Wright, Malcolm W.; Padams, Jordan H.; Konyha, Alexander L.

2015-01-01

This paper provides an overview of Optical Payload for Lasercomm Science (OPALS) activities and lessons learned during mission operations. Activities described cover the periods of commissioning, prime, and extended mission operations, during which primary and secondary mission objectives were achieved for demonstrating space-to-ground optical communications. Lessons learned cover Mission Operations System topics in areas of: architecture verification and validation, staffing, mission support area, workstations, workstation tools, interfaces with support services, supporting ground stations, team training, procedures, flight software upgrades, post-processing tools, and public outreach.

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

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.

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.

Flight Operations . [Zero Knowledge to Mission Complete

NASA Technical Reports Server (NTRS)

Forest, Greg; Apyan, Alex; Hillin, Andrew

2016-01-01

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

47 CFR 90.525 - Administration of interoperability channels.

Code of Federal Regulations, 2010 CFR

2010-10-01

... RADIO SERVICES PRIVATE LAND MOBILE RADIO SERVICES Regulations Governing the Licensing and Use of... meeting the requirements of § 90.523 may operate mobile or portable units on the Interoperability channels... Commission provided it holds a part 90 license. All persons operating mobile or portable units under this...

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.

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.

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.

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.

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

Interoperability Measurement

DTIC Science & Technology

2008-08-01

facilitate the use of existing architecture descriptions in performing interoperability measurement. Noting that “everything in the world can be expressed as...biological, botanical, and genetic research, it has also been used with great success in the fields of ecology, medicine, the social sciences, the...appropriate for at least three reasons. First, systems perform different interoperations in different scenarios (i.e., they are used differently); second

MOS 2.0: Modeling the Next Revolutionary Mission Operations System

NASA Technical Reports Server (NTRS)

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

2011-01-01

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

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.

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.

Achieving control and interoperability through unified model-based systems and software engineering

NASA Technical Reports Server (NTRS)

Rasmussen, Robert; Ingham, Michel; Dvorak, Daniel

2005-01-01

Control and interoperation of complex systems is one of the most difficult challenges facing NASA's Exploration Systems Mission Directorate. An integrated but diverse array of vehicles, habitats, and supporting facilities, evolving over the long course of the enterprise, must perform ever more complex tasks while moving steadily away from the sphere of ground support and intervention.

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

Requirements Development for Interoperability Simulation Capability for Law Enforcement

DOE Office of Scientific and Technical Information (OSTI.GOV)

Holter, Gregory M.

2004-05-19

The National Counterdrug Center (NCC) was initially authorized by Congress in FY 1999 appropriations to create a simulation-based counterdrug interoperability training capability. As the lead organization for Research and Analysis to support the NCC, the Pacific Northwest National Laboratory (PNNL) was responsible for developing the requirements for this interoperability simulation capability. These requirements were structured to address the hardware and software components of the system, as well as the deployment and use of the system. The original set of requirements was developed through a process of conducting a user-based survey of requirements for the simulation capability, coupled with an analysismore » of similar development efforts. The user-based approach ensured that existing concerns with respect to interoperability within the law enforcement community would be addressed. Law enforcement agencies within the designated pilot area of Cochise County, Arizona, were surveyed using interviews and ride-alongs during actual operations. The results of this survey were then accumulated, organized, and validated with the agencies to ensure the accuracy of the results. These requirements were then supplemented by adapting operational requirements from existing systems to ensure system reliability and operability. The NCC adopted a development approach providing incremental capability through the fielding of a phased series of progressively more capable versions of the system. This allowed for feedback from system users to be incorporated into subsequent revisions of the system requirements, and also allowed the addition of new elements as needed to adapt the system to broader geographic and geopolitical areas, including areas along the southwest and northwest U.S. borders. This paper addresses the processes used to develop and refine requirements for the NCC interoperability simulation capability, as well as the response of the law enforcement community to the

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.

Fundamental Data Standards for Science Data System Interoperability and Data Correlation

NASA Astrophysics Data System (ADS)

Hughes, J. Steven; Gopala Krishna, Barla; Rye, Elizabeth; Crichton, Daniel

The advent of the Web and languages such as XML have brought an explosion of online science data repositories and the promises of correlated data and interoperable systems. However there have been relatively few successes in meeting the expectations of science users in the internet age. For example a Google-like search for images of Mars will return many highly-derived and appropriately tagged images but largely ignore the majority of images in most online image repositories. Once retrieved, users are further frustrated by poor data descriptions, arcane formats, and badly organized ancillary information. A wealth of research indicates that shared information models are needed to enable system interoperability and data correlation. However, at a more fundamental level, data correlation and system interoperability are dependant on a relatively few shared data standards. A com-mon data dictionary standard, for example, allows the controlled vocabulary used in a science repository to be shared with potential collaborators. Common data registry and product iden-tification standards enable systems to efficiently find, locate, and retrieve data products and their metadata from remote repositories. Information content standards define categories of descriptive data that help make the data products scientifically useful to users who were not part of the original team that produced the data. The Planetary Data System (PDS) has a plan to move the PDS to a fully online, federated system. This plan addresses new demands on the system including increasing data volume, numbers of missions, and complexity of missions. A key component of this plan is the upgrade of the PDS Data Standards. The adoption of the core PDS data standards by the International Planetary Data Alliance (IPDA) adds the element of international cooperation to the plan. This presentation will provide an overview of the fundamental data standards being adopted by the PDS that transcend science domains and that

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.

Assured Mission Support Space Architecture (AMSSA) study

NASA Technical Reports Server (NTRS)

Hamon, Rob

1993-01-01

The assured mission support space architecture (AMSSA) study was conducted with the overall goal of developing a long-term requirements-driven integrated space architecture to provide responsive and sustained space support to the combatant commands. Although derivation of an architecture was the focus of the study, there are three significant products from the effort. The first is a philosophy that defines the necessary attributes for the development and operation of space systems to ensure an integrated, interoperable architecture that, by design, provides a high degree of combat utility. The second is the architecture itself; based on an interoperable system-of-systems strategy, it reflects a long-range goal for space that will evolve as user requirements adapt to a changing world environment. The third product is the framework of a process that, when fully developed, will provide essential information to key decision makers for space systems acquisition in order to achieve the AMSSA goal. It is a categorical imperative that military space planners develop space systems that will act as true force multipliers. AMSSA provides the philosophy, process, and architecture that, when integrated with the DOD requirements and acquisition procedures, can yield an assured mission support capability from space to the combatant commanders. An important feature of the AMSSA initiative is the participation by every organization that has a role or interest in space systems development and operation. With continued community involvement, the concept of the AMSSA will become a reality. In summary, AMSSA offers a better way to think about space (philosophy) that can lead to the effective utilization of limited resources (process) with an infrastructure designed to meet the future space needs (architecture) of our combat forces.

Procrustes-based geometric morphometrics on MRI images: An example of inter-operator bias in 3D landmarks and its impact on big datasets.

PubMed

Daboul, Amro; Ivanovska, Tatyana; Bülow, Robin; Biffar, Reiner; Cardini, Andrea

2018-01-01

Using 3D anatomical landmarks from adult human head MRIs, we assessed the magnitude of inter-operator differences in Procrustes-based geometric morphometric analyses. An in depth analysis of both absolute and relative error was performed in a subsample of individuals with replicated digitization by three different operators. The effect of inter-operator differences was also explored in a large sample of more than 900 individuals. Although absolute error was not unusual for MRI measurements, including bone landmarks, shape was particularly affected by differences among operators, with up to more than 30% of sample variation accounted for by this type of error. The magnitude of the bias was such that it dominated the main pattern of bone and total (all landmarks included) shape variation, largely surpassing the effect of sex differences between hundreds of men and women. In contrast, however, we found higher reproducibility in soft-tissue nasal landmarks, despite relatively larger errors in estimates of nasal size. Our study exemplifies the assessment of measurement error using geometric morphometrics on landmarks from MRIs and stresses the importance of relating it to total sample variance within the specific methodological framework being used. In summary, precise landmarks may not necessarily imply negligible errors, especially in shape data; indeed, size and shape may be differentially impacted by measurement error and different types of landmarks may have relatively larger or smaller errors. Importantly, and consistently with other recent studies using geometric morphometrics on digital images (which, however, were not specific to MRI data), this study showed that inter-operator biases can be a major source of error in the analysis of large samples, as those that are becoming increasingly common in the 'era of big data'.

Procrustes-based geometric morphometrics on MRI images: An example of inter-operator bias in 3D landmarks and its impact on big datasets

PubMed Central

Ivanovska, Tatyana; Bülow, Robin; Biffar, Reiner; Cardini, Andrea

2018-01-01

Using 3D anatomical landmarks from adult human head MRIs, we assessed the magnitude of inter-operator differences in Procrustes-based geometric morphometric analyses. An in depth analysis of both absolute and relative error was performed in a subsample of individuals with replicated digitization by three different operators. The effect of inter-operator differences was also explored in a large sample of more than 900 individuals. Although absolute error was not unusual for MRI measurements, including bone landmarks, shape was particularly affected by differences among operators, with up to more than 30% of sample variation accounted for by this type of error. The magnitude of the bias was such that it dominated the main pattern of bone and total (all landmarks included) shape variation, largely surpassing the effect of sex differences between hundreds of men and women. In contrast, however, we found higher reproducibility in soft-tissue nasal landmarks, despite relatively larger errors in estimates of nasal size. Our study exemplifies the assessment of measurement error using geometric morphometrics on landmarks from MRIs and stresses the importance of relating it to total sample variance within the specific methodological framework being used. In summary, precise landmarks may not necessarily imply negligible errors, especially in shape data; indeed, size and shape may be differentially impacted by measurement error and different types of landmarks may have relatively larger or smaller errors. Importantly, and consistently with other recent studies using geometric morphometrics on digital images (which, however, were not specific to MRI data), this study showed that inter-operator biases can be a major source of error in the analysis of large samples, as those that are becoming increasingly common in the 'era of big data'. PMID:29787586

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.

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.

Advances in Distributed Operations and Mission Activity Planning for Mars Surface Exploration

NASA Technical Reports Server (NTRS)

Fox, Jason M.; Norris, Jeffrey S.; Powell, Mark W.; Rabe, Kenneth J.; Shams, Khawaja

2006-01-01

A centralized mission activity planning system for any long-term mission, such as the Mars Exploration Rover Mission (MER), is completely infeasible due to budget and geographic constraints. A distributed operations system is key to addressing these constraints; therefore, future system and software engineers must focus on the problem of how to provide a secure, reliable, and distributed mission activity planning system. We will explain how Maestro, the next generation mission activity planning system, with its heavy emphasis on portability and distributed operations has been able to meet these design challenges. MER has been an excellent proving ground for Maestro's new approach to distributed operations. The backend that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

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.

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

NASA Astrophysics Data System (ADS)

Bisi, M. M.; Trichas, M.

2015-12-01

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

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

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.

Magellan attitude control mission operations

NASA Technical Reports Server (NTRS)

Dukes, Eileen M.

1993-01-01

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

Magellan attitude control mission operations

NASA Astrophysics Data System (ADS)

Dukes, Eileen M.

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

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

NASA Astrophysics Data System (ADS)

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

2016-12-01

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

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.

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

Warfighter IT Interoperability Standards Study

DTIC Science & Technology

2012-07-22

data (e.g. messages) between systems ? ii) What process did you used to validate and certify semantic interoperability between your...other systems at this time There was no requirement to validate and certify semantic interoperability The DLS program exchanges data with... semantics Testing for System Compliance with Data Models Verify and Certify Interoperability Using Data

Moving Toward Space Internetworking via DTN: Its Operational Challenges, Benefits, and Management

NASA Technical Reports Server (NTRS)

Barkley, Erik; Burleigh, Scott; Gladden, Roy; Malhotra, Shan; Shames, Peter

2010-01-01

The international space community has begun to recognize that the established model for management of communications with spacecraft - commanded data transmission over individual pair-wise contacts - is operationally unwieldy and will not scale in support of increasingly complex and sophisticated missions such as NASA's Constellation project. Accordingly, the international Inter-Agency Operations Advisory Group (IOAG) ichartered a Space Internetworking Strategy Group (SISG), which released its initial recommendations in a November 2008 report. The report includes a recommendation that the space flight community adopt Delay-Tolerant Networking (DTN) to address the problem of interoperability and communication scaling, especially in mission environments where there are multiple spacecraft operating in concert. This paper explores some of the issues that must be addressed in implementing, deploying, and operating DTN as part of a multi-mission, multi-agency space internetwork as well as benefits and future operational scenarios afforded by DTN-based space internetworking.

Integrated Network Architecture for NASA's Orion Missions

NASA Technical Reports Server (NTRS)

Bhasin, Kul B.; Hayden, Jeffrey L.; Sartwell, Thomas; Miller, Ronald A.; Hudiburg, John J.

2008-01-01

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. The series of missions will begin with a new crew exploration vehicle (called Orion) that will initially provide crew exchange and cargo supply support to the International Space Station (ISS) and then become a human conveyance for travel to the Moon. The Orion vehicle will be mounted atop the Ares I launch vehicle for a series of pre-launch tests and then launched and inserted into low Earth orbit (LEO) for crew exchange missions to the ISS. The Orion and Ares I comprise the initial vehicles in the Constellation system of systems that later includes Ares V, Earth departure stage, lunar lander, and other lunar surface systems for the lunar exploration missions. These key systems will enable the lunar surface exploration missions to be initiated in 2018. The complexity of the Constellation system of systems and missions will require a communication and navigation infrastructure to provide low and high rate forward and return communication services, tracking services, and ground network services. The infrastructure must provide robust, reliable, safe, sustainable, and autonomous operations at minimum cost while maximizing the exploration capabilities and science return. The infrastructure will be based on a network of networks architecture that will integrate NASA legacy communication, modified elements, and navigation systems. New networks will be added to extend communication, navigation, and timing services for the Moon missions. Internet protocol (IP) and network management systems within the networks will enable interoperability throughout the Constellation system of systems. An integrated network architecture has developed based on the emerging Constellation requirements for Orion missions. The architecture, as presented in this paper, addresses the early Orion missions to the ISS with communication, navigation, and network services over five

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

NASA Technical Reports Server (NTRS)

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

2006-01-01

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

The interoperability force in the ERP field

NASA Astrophysics Data System (ADS)

Boza, Andrés; Cuenca, Llanos; Poler, Raúl; Michaelides, Zenon

2015-04-01

Enterprise resource planning (ERP) systems participate in interoperability projects and this participation sometimes leads to new proposals for the ERP field. The aim of this paper is to identify the role that interoperability plays in the evolution of ERP systems. To go about this, ERP systems have been first identified within interoperability frameworks. Second, the initiatives in the ERP field driven by interoperability requirements have been identified from two perspectives: technological and business. The ERP field is evolving from classical ERP as information system integrators to a new generation of fully interoperable ERP. Interoperability is changing the way of running business, and ERP systems are changing to adapt to the current stream of interoperability.

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.

Finalizing the CCSDS Space-Data Link Layer Security Protocol: Setup and Execution of the Interoperability Testing

NASA Technical Reports Server (NTRS)

Fischer, Daniel; Aguilar-Sanchez, Ignacio; Saba, Bruno; Moury, Gilles; Biggerstaff, Craig; Bailey, Brandon; Weiss, Howard; Pilgram, Martin; Richter, Dorothea

2015-01-01

The protection of data transmitted over the space-link is an issue of growing importance also for civilian space missions. Through the Consultative Committee for Space Data Systems (CCSDS), space agencies have reacted to this need by specifying the Space Data-Link Layer Security (SDLS) protocol which provides confidentiality and integrity services for the CCSDS Telemetry (TM), Telecommand (TC) and Advanced Orbiting Services (AOS) space data-link protocols. This paper describes the approach of the CCSDS SDLS working group to specify and execute the necessary interoperability tests. It first details the individual SDLS implementations that have been produced by ESA, NASA, and CNES and then the overall architecture that allows the interoperability tests between them. The paper reports on the results of the interoperability tests and identifies relevant aspects for the evolution of the test environment.

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.

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.

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.

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.

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.

The Hubble Space Telescope servicing missions: Past, present, and future operational challenges

NASA Technical Reports Server (NTRS)

Ochs, William R.; Barbehenn, George M.; Crabb, William G.

1996-01-01

The Hubble Space Telescope was designed to be serviced by the Space Shuttle to upgrade systems, replace failed components and boost the telescope into higher orbits. There exists many operational challenges that must be addressed in preparation for the execution of a servicing mission, including technical and managerial issues. The operational challenges faced by the Hubble operations and ground system project for the support of the first servicing mission and future servicing missions, are considered. The emphasis is on those areas that helped ensure the success of the mission, including training, testing and contingency planning.

Dust Storm Impacts on Human Mars Mission Equipment and Operations

NASA Technical Reports Server (NTRS)

Rucker, M. A.

2017-01-01

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

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

Impact of North Atlantic Treaty Organization Policies and Procedures on Combined Medical Operations: Food and Water Safety and Veterinary Support.

PubMed

Stevenson, Timothy H; Chevalier, Nicole A; Scher, Gregory R; Burke, Ronald L

2016-01-01

Effective multilateral military operations such as those conducted by the North Atlantic Treaty Organization (NATO) require close cooperation and standardization between member nations to ensure interoperability. Failure to standardize policies, procedures, and doctrine prior to the commencement of military operations will result in critical interoperability gaps, which jeopardize the health of NATO forces and mission success. To prevent these gaps from occurring, US forces must be actively involved with NATO standardization efforts such as the Committee of the Chiefs of Medical Services to ensure US interests are properly represented when NATO standards are developed and US doctrine and procedures will meet the established NATO requirements.

DeoR repression at-a-distance only weakly responds to changes in interoperator separation and DNA topology.

PubMed Central

Dandanell, G

1992-01-01

The interoperator distance between a synthetic operator Os and the deoP2O2-galK fusion was varied between 46 and 176 bp. The repression of the deoP2 directed galK expression as a function of the interoperator distance (center-to-center) was measured in vivo in a single-copy system. The results show that the DeoR repressor efficiently can repress transcription at all the interoperator distances tested. The degree of repression depends very little on the spacing between the operators, however, a weak periodic dependency of 8-11 bp may exist. PMID:1437558

Potential interoperability problems facing multi-site radiation oncology centers in The Netherlands

NASA Astrophysics Data System (ADS)

Scheurleer, J.; Koken, Ph; Wessel, R.

2014-03-01

Aim: To identify potential interoperability problems facing multi-site Radiation Oncology (RO) departments in the Netherlands and solutions for unambiguous multi-system workflows. Specific challenges confronting the RO department of VUmc (RO-VUmc), which is soon to open a satellite department, were characterized. Methods: A nationwide questionnaire survey was conducted to identify possible interoperability problems and solutions. Further detailed information was obtained by in-depth interviews at 3 Dutch RO institutes that already operate in more than one site. Results: The survey had a 100% response rate (n=21). Altogether 95 interoperability problems were described. Most reported problems were on a strategic and semantic level. The majority were DICOM(-RT) and HL7 related (n=65), primarily between treatment planning and verification systems or between departmental and hospital systems. Seven were identified as being relevant for RO-VUmc. Departments have overcome interoperability problems with their own, or with tailor-made vendor solutions. There was little knowledge about or utilization of solutions developed by Integrating the Healthcare Enterprise Radiation Oncology (IHE-RO). Conclusions: Although interoperability problems are still common, solutions have been identified. Awareness of IHE-RO needs to be raised. No major new interoperability problems are predicted as RO-VUmc develops into a multi-site department.

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.

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.

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.

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.

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.

Integrated Operations Architecture Technology Assessment Study

NASA Technical Reports Server (NTRS)

2001-01-01

As part of NASA's Integrated Operations Architecture (IOA) Baseline, NASA will consolidate all communications operations. including ground-based, near-earth, and deep-space communications, into a single integrated network. This network will make maximum use of commercial equipment, services and standards. It will be an Internet Protocol (IP) based network. This study supports technology development planning for the IOA. The technical problems that may arise when LEO mission spacecraft interoperate with commercial satellite services were investigated. Commercial technology and services that could support the IOA were surveyed, and gaps in the capability of existing technology and techniques were identified. Recommendations were made on which gaps should be closed by means of NASA research and development funding. Several findings emerged from the interoperability assessment: in the NASA mission set, there is a preponderance of small. inexpensive, low data rate science missions; proposed commercial satellite communications services could potentially provide TDRSS-like data relay functions; and. IP and related protocols, such as TCP, require augmentation to operate in the mobile networking environment required by the space-to-ground portion of the IOA. Five case studies were performed in the technology assessment. Each case represented a realistic implementation of the near-earth portion of the IOA. The cases included the use of frequencies at L-band, Ka-band and the optical spectrum. The cases also represented both space relay architectures and direct-to-ground architectures. Some of the main recommendations resulting from the case studies are: select an architecture for the LEO/MEO communications network; pursue the development of a Ka-band space-qualified transmitter (and possibly a receiver), and a low-cost Ka-band ground terminal for a direct-to-ground network, pursue the development of an Inmarsat (L-band) space-qualified transceiver to implement a global, low

Groundwater data network interoperability

USGS Publications Warehouse

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

2016-01-01

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

A development framework for semantically interoperable health information systems.

PubMed

Lopez, Diego M; Blobel, Bernd G M E

2009-02-01

Semantic interoperability is a basic challenge to be met for new generations of distributed, communicating and co-operating health information systems (HIS) enabling shared care and e-Health. Analysis, design, implementation and maintenance of such systems and intrinsic architectures have to follow a unified development methodology. The Generic Component Model (GCM) is used as a framework for modeling any system to evaluate and harmonize state of the art architecture development approaches and standards for health information systems as well as to derive a coherent architecture development framework for sustainable, semantically interoperable HIS and their components. The proposed methodology is based on the Rational Unified Process (RUP), taking advantage of its flexibility to be configured for integrating other architectural approaches such as Service-Oriented Architecture (SOA), Model-Driven Architecture (MDA), ISO 10746, and HL7 Development Framework (HDF). Existing architectural approaches have been analyzed, compared and finally harmonized towards an architecture development framework for advanced health information systems. Starting with the requirements for semantic interoperability derived from paradigm changes for health information systems, and supported in formal software process engineering methods, an appropriate development framework for semantically interoperable HIS has been provided. The usability of the framework has been exemplified in a public health scenario.

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.

Ground Support Network for Operational Radio Occultation Missions

NASA Astrophysics Data System (ADS)

Zandbergen, R.; Enderle, W.; Marquardt, C.; Wollenweber, F.

2012-04-01

The EUMETSAT/ESA Metop/EPS GRAS radio occultation mission stands out for its operational nature. From the beginning, EUMETSAT has decided to rely on an operational system for provision of the auxiliary GPS products that are needed in the occultation processing. This system is the GRAS Ground Support Network (GSN), operated in the Navigation Facility of ESOC in Darmstadt, which was first presented at EGU in 2008. The GRAS GSN is driven primarily by timeliness, availability and accuracy requirements. The performance of the GSN, measured on a monthly basis, has not only consistently met these requirements since the start of its operations, but has also been improved through several system enhancements. Currently, an additional service is being delivered on an experimental basis, consisting of a near-real time Navigation Bit Stream product, which will allow the processing of open-loop data, further increasing the scientific return of the GRAS instrument, or any other radio occultation mission using this data. This paper will present the GRAS GSN in its current configuration, and demonstrate its excellent performance in terms of accuracy, availability and timeliness. The application of the bit stream data will be shown. Some future evolution perspectives of the GRAS GSN will also be addressed. It will be demonstrated that the GRAS GSN has the potential of serving also other present and future radio occultation missions.

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

NASA Technical Reports Server (NTRS)

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

1988-01-01

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

Shuttle Radar Topography Mission (SRTM) Flight System Design and Operations Overview

NASA Technical Reports Server (NTRS)

Shen, Yuhsyen; Shaffer, Scott J.; Jordan, Rolando L.

2000-01-01

This paper provides an overview of the Shuttle Radar Topography Mission (SRTM), with emphasis on flight system implementation and mission operations from systems engineering perspective. Successfully flown in February, 2000, the SRTM's primary payload consists of several subsystems to form the first spaceborne dual-frequency (C-band and X-band) fixed baseline interferometric synthetic aperture radar (InSAR) system, with the mission objective to acquire data sets over 80% of Earth's landmass for height reconstruction. The paper provides system architecture, unique design features, engineering budgets, design verification, in-flight checkout and data acquisition of the SRTM payload, in particular for the C-band system. Mission operation and post-mission data processing activities are also presented. The complexity of the SRTM as a system, the ambitious mission objective, the demanding requirements and the high interdependency between multi-disciplined subsystems posed many challenges. The engineering experience and the insight thus gained have important implications for future spaceborne interferometric SAR mission design and implementation.

Tool and data interoperability in the SSE system

NASA Technical Reports Server (NTRS)

Shotton, Chuck

1988-01-01

Information is given in viewgraph form on tool and data interoperability in the Software Support Environment (SSE). Information is given on industry problems, SSE system interoperability issues, SSE solutions to tool and data interoperability, and attainment of heterogeneous tool/data interoperability.

NASA's Spitzer Space Telescope's Operational Mission Experience

NASA Technical Reports Server (NTRS)

Wilson, Robert K.; Scott, Charles P.

2006-01-01

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

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

Galileo mission planning for Low Gain Antenna based operations

NASA Astrophysics Data System (ADS)

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

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

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.

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

NASA Technical Reports Server (NTRS)

Harris, Jennifer A.; Bahrami, Khosrow A.

1993-01-01

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

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.

Coordination of Mars Express and Beagle2 Mission Operations

NASA Astrophysics Data System (ADS)

Trautner, R.; Chicarro, A.; Martin, P.

The Mars Express orbiter carrying the British Beagle 2 lander will arrive at Mars late 2003. The evaluation of science data from both the MEX orbiter and the lander will benefit from coordinated measurements obtained by the instrument sets on each space- craft. Furthermore, data obtained during the early mission of one spacecraft should be taken into account for the science operations planning of the other spacecraft in order to optimize the scientific return. Based on the capabilities and goals of the scientific instruments on both platforms, possible areas of cooperation are proposed. The flex- ibility required in mission operations planning for both the orbiter and the lander are assessed, and the expected benefits of coordinated operations are explained.

Multi-Agent Modeling and Simulation Approach for Design and Analysis of MER Mission Operations

NASA Technical Reports Server (NTRS)

Seah, Chin; Sierhuis, Maarten; Clancey, William J.

2005-01-01

A space mission operations system is a complex network of human organizations, information and deep-space network systems and spacecraft hardware. As in other organizations, one of the problems in mission operations is managing the relationship of the mission information systems related to how people actually work (practices). Brahms, a multi-agent modeling and simulation tool, was used to model and simulate NASA's Mars Exploration Rover (MER) mission work practice. The objective was to investigate the value of work practice modeling for mission operations design. From spring 2002 until winter 2003, a Brahms modeler participated in mission systems design sessions and operations testing for the MER mission held at Jet Propulsion Laboratory (JPL). He observed how designers interacted with the Brahms tool. This paper discussed mission system designers' reactions to the simulation output during model validation and the presentation of generated work procedures. This project spurred JPL's interest in the Brahms model, but it was never included as part of the formal mission design process. We discuss why this occurred. Subsequently, we used the MER model to develop a future mission operations concept. Team members were reluctant to use the MER model, even though it appeared to be highly relevant to their effort. We describe some of the tool issues we encountered.

Orbital operations study. Volume 1: Mission analysis

NASA Technical Reports Server (NTRS)

Steinwachs, W. L.

1972-01-01

The final report of the orbital operations study and a summary of the 25 elements in the study inventory are presented. Fourteen interfacing activities are defined. Eleven mission models encompassing all potential interfacing element pairs and interfacing activities are included.

National electronic health record interoperability chronology.

PubMed

Hufnagel, Stephen P

2009-05-01

The federal initiative for electronic health record (EHR) interoperability began in 2000 and set the stage for the establishment of the 2004 Executive Order for EHR interoperability by 2014. This article discusses the chronology from the 2001 e-Government Consolidated Health Informatics (CHI) initiative through the current congressional mandates for an aligned, interoperable, and agile DoD AHLTA and VA VistA.

Joint Command and Control: Integration Not Interoperability

DTIC Science & Technology

2013-03-01

separate computer and communication equipment. Besides having to engineer interoperability, the Services also must determine the level of...effects.  Determines force responsiveness and allocates resources.5 This thesis argues Joint military operations will never be fully integrated as...processes and systems. Secondly, the limited depth of discussion risks implying (or the reader inferring) the solution is more straightforward than

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

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

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

MOS 2.0: The Next Generation in Mission Operations Systems

NASA Technical Reports Server (NTRS)

Bindschadler, Duane L.; Boyles, Carole A.; Carrion, Carlos; Delp, Chris L.

2010-01-01

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits

XMM-Newton mission operations - ready for its third decade

NASA Astrophysics Data System (ADS)

Kirsch, M.; Finn, T.; Godard, T.; v. Krusenstiern, N.; Pfeil, N.; Salt, D.; Toma, L.; Webert, D.; Weissmann, U.

2017-10-01

The XMM-Newton X-ray space observatory is approaching its third decade of operations. The spacecraft and payload are operating without major degradation and scientific demand is continuously very high. With the change to a new way of using the Attitude and Orbit control System in 2013 the fuel consumption was reduced by a factor of two, additionally this has reduced stress on the reaction wheels. The challenge for the next decade is now to ensure that the saved fuel is available for continuous usage. We will describe the process of the so called 'fuel migration and replenishment' activities needed to keep the spacecraft operational potentially up to 2029+. We provide as well an overall health status of the mission, the evolution of the ground segment and concepts on streamlining mission operations with continued high safety requirements using automation tools.

Improving the Interoperability and Usability of NASA Earth Observation Data

NASA Astrophysics Data System (ADS)

Walter, J.; Berrick, S. W.; Murphy, K. J.; Mitchell, A. E.; Tilmes, C.

2014-12-01

NASA's Earth Science Data and Information System Project (ESDIS) is charged with managing, maintaining, and evolving NASA's Earth Observing System Data and Information System (EOSDIS) and is responsible for processing, archiving, and distributing NASA Earth Science data. The system supports a multitude of missions and serves diverse science research and other user communities. While NASA has made, and continues to make, great strides in the discoverability and accessibility of its earth observation data holdings, issues associated with data interoperability and usability still present significant challenges to realizing the full scientific and societal benefits of these data. This concern has been articulated by multiple government agencies, both U.S. and international, as well as other non-governmental organizations around the world. Among these is the White House Office of Science and Technology Policy who, in response, has launched the Big Earth Data Initiative and the Climate Data Initiative to address these concerns for U.S. government agencies. This presentation will describe NASA's approach for addressing data interoperability and usability issues with our earth observation data.

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.

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.

Earth orbital operations supporting manned interplanetary missions

NASA Technical Reports Server (NTRS)

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

1989-01-01

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

Semantic interoperability--HL7 Version 3 compared to advanced architecture standards.

PubMed

Blobel, B G M E; Engel, K; Pharow, P

2006-01-01

To meet the challenge for high quality and efficient care, highly specialized and distributed healthcare establishments have to communicate and co-operate in a semantically interoperable way. Information and communication technology must be open, flexible, scalable, knowledge-based and service-oriented as well as secure and safe. For enabling semantic interoperability, a unified process for defining and implementing the architecture, i.e. structure and functions of the cooperating systems' components, as well as the approach for knowledge representation, i.e. the used information and its interpretation, algorithms, etc. have to be defined in a harmonized way. Deploying the Generic Component Model, systems and their components, underlying concepts and applied constraints must be formally modeled, strictly separating platform-independent from platform-specific models. As HL7 Version 3 claims to represent the most successful standard for semantic interoperability, HL7 has been analyzed regarding the requirements for model-driven, service-oriented design of semantic interoperable information systems, thereby moving from a communication to an architecture paradigm. The approach is compared with advanced architectural approaches for information systems such as OMG's CORBA 3 or EHR systems such as GEHR/openEHR and CEN EN 13606 Electronic Health Record Communication. HL7 Version 3 is maturing towards an architectural approach for semantic interoperability. Despite current differences, there is a close collaboration between the teams involved guaranteeing a convergence between competing approaches.

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.

Spitzer Mission Operation System Planning for IRAC Warm-Instrument Characterization

NASA Technical Reports Server (NTRS)

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

2010-01-01

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

The Mission Operations System for Wide-field Infrared Survey Explorer (WISE)

NASA Technical Reports Server (NTRS)

Heinrichsen, Ingolf H.

2006-01-01

The goal of the Wide-field Infrared Survey Explorer (WISE) mission is to perform a highly sensitive all-sky survey in 4 wavebands from 3 to 25(mu)m. Launched on a Delta II rocket into a 500km Sun-synchronous orbit in June 2009, during its 7 months of operations, WISE will acquire about 50GBytes of raw science data every day, which will be down-linked via the TDRSS relay satellite system and processed into an astronomical catalogue and image atlas. The WISE mission operations system is being implemented in collaboration between UCLA, JPL and IPAC (Caltech). In this paper we describe the challenges to manage a high data rate, cryogenic, low earth-orbit mission; maintaining safe on-orbit operations, fast anomaly recoveries (mandated by the desire to provide complete sky coverage in a limited lifetime), production and dissemination of high quality science products, given the constraints imposed by funding profiles for small space missions.

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

NASA Technical Reports Server (NTRS)

Rash, James L. (Editor)

1994-01-01

Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The symposium papers focus on improvements in the efficiency, effectiveness, and quality of data acquisition, ground systems, and mission operations. New technology, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations. This volume covers expert systems, systems development tools and approaches, and systems engineering issues.

Enabling Autonomous Space Mission Operations with Artificial Intelligence

NASA Technical Reports Server (NTRS)

Frank, Jeremy

2017-01-01

For over 50 years, NASA's crewed missions have been confined to the Earth-Moon system, where speed-of-light communications delays between crew and ground are practically nonexistent. This ground-centered mode of operations, with a large, ground-based support team, is not sustainable for NASAs future human exploration missions to Mars. Future astronauts will need smarter tools employing Artificial Intelligence (AI) techniques make decisions without inefficient communication back and forth with ground-based mission control. In this talk we will describe several demonstrations of astronaut decision support tools using AI techniques as a foundation. These demonstrations show that astronauts tasks ranging from living and working to piloting can benefit from AI technology development.

Management of Operational Support Requirements for Manned Flight Missions

NASA Technical Reports Server (NTRS)

1991-01-01

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

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

NASA Technical Reports Server (NTRS)

Barker, F. C.

1978-01-01

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

Designing learning management system interoperability in semantic web

NASA Astrophysics Data System (ADS)

Anistyasari, Y.; Sarno, R.; Rochmawati, N.

2018-01-01

The extensive adoption of learning management system (LMS) has set the focus on the interoperability requirement. Interoperability is the ability of different computer systems, applications or services to communicate, share and exchange data, information, and knowledge in a precise, effective and consistent way. Semantic web technology and the use of ontologies are able to provide the required computational semantics and interoperability for the automation of tasks in LMS. The purpose of this study is to design learning management system interoperability in the semantic web which currently has not been investigated deeply. Moodle is utilized to design the interoperability. Several database tables of Moodle are enhanced and some features are added. The semantic web interoperability is provided by exploited ontology in content materials. The ontology is further utilized as a searching tool to match user’s queries and available courses. It is concluded that LMS interoperability in Semantic Web is possible to be performed.

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.

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.

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.

Towards semantic interoperability for electronic health records.

PubMed

Garde, Sebastian; Knaup, Petra; Hovenga, Evelyn; Heard, Sam

2007-01-01

In the field of open electronic health records (EHRs), openEHR as an archetype-based approach is being increasingly recognised. It is the objective of this paper to shortly describe this approach, and to analyse how openEHR archetypes impact on health professionals and semantic interoperability. Analysis of current approaches to EHR systems, terminology and standards developments. In addition to literature reviews, we organised face-to-face and additional telephone interviews and tele-conferences with members of relevant organisations and committees. The openEHR archetypes approach enables syntactic interoperability and semantic interpretability -- both important prerequisites for semantic interoperability. Archetypes enable the formal definition of clinical content by clinicians. To enable comprehensive semantic interoperability, the development and maintenance of archetypes needs to be coordinated internationally and across health professions. Domain knowledge governance comprises a set of processes that enable the creation, development, organisation, sharing, dissemination, use and continuous maintenance of archetypes. It needs to be supported by information technology. To enable EHRs, semantic interoperability is essential. The openEHR archetypes approach enables syntactic interoperability and semantic interpretability. However, without coordinated archetype development and maintenance, 'rank growth' of archetypes would jeopardize semantic interoperability. We therefore believe that openEHR archetypes and domain knowledge governance together create the knowledge environment required to adopt EHRs.

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

NASA Astrophysics Data System (ADS)

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

2015-06-01

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

The RICORDO approach to semantic interoperability for biomedical data and models: strategy, standards and solutions

PubMed Central

2011-01-01

Background The practice and research of medicine generates considerable quantities of data and model resources (DMRs). Although in principle biomedical resources are re-usable, in practice few can currently be shared. In particular, the clinical communities in physiology and pharmacology research, as well as medical education, (i.e. PPME communities) are facing considerable operational and technical obstacles in sharing data and models. Findings We outline the efforts of the PPME communities to achieve automated semantic interoperability for clinical resource documentation in collaboration with the RICORDO project. Current community practices in resource documentation and knowledge management are overviewed. Furthermore, requirements and improvements sought by the PPME communities to current documentation practices are discussed. The RICORDO plan and effort in creating a representational framework and associated open software toolkit for the automated management of PPME metadata resources is also described. Conclusions RICORDO is providing the PPME community with tools to effect, share and reason over clinical resource annotations. This work is contributing to the semantic interoperability of DMRs through ontology-based annotation by (i) supporting more effective navigation and re-use of clinical DMRs, as well as (ii) sustaining interoperability operations based on the criterion of biological similarity. Operations facilitated by RICORDO will range from automated dataset matching to model merging and managing complex simulation workflows. In effect, RICORDO is contributing to community standards for resource sharing and interoperability. PMID:21878109

The Mission Operations Planning Assistant

NASA Technical Reports Server (NTRS)

Schuetzle, James G.

1987-01-01

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

The mission operations planning assistant

NASA Technical Reports Server (NTRS)

Schuetzle, James G.

1987-01-01

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

Empowering open systems through cross-platform interoperability

NASA Astrophysics Data System (ADS)

Lyke, James C.

2014-06-01

Most of the motivations for open systems lie in the expectation of interoperability, sometimes referred to as "plug-and-play". Nothing in the notion of "open-ness", however, guarantees this outcome, which makes the increased interest in open architecture more perplexing. In this paper, we explore certain themes of open architecture. We introduce the concept of "windows of interoperability", which can be used to align disparate portions of architecture. Such "windows of interoperability", which concentrate on a reduced set of protocol and interface features, might achieve many of the broader purposes assigned as benefits in open architecture. Since it is possible to engineer proprietary systems that interoperate effectively, this nuanced definition of interoperability may in fact be a more important concept to understand and nurture for effective systems engineering and maintenance.

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.

Semantically Interoperable XML Data

PubMed Central

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

2013-01-01

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

Lewis Wooten, manager of the Mission Operations Laboratory

NASA Image and Video Library

2015-07-20

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

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

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

NASA Technical Reports Server (NTRS)

1993-01-01

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

Impact of coalition interoperability on PKI

NASA Astrophysics Data System (ADS)

Krall, Edward J.

2003-07-01

This paper examines methods for providing PKI interoperability among units of a coalition of armed forces drawn from different nations. The area in question is tactical identity management, for the purposes of confidentiality, integrity and non-repudiation in such a dynamic coalition. The interoperating applications under consideration range from email and other forms of store-and-forward messaging to TLS and IPSEC-protected real-time communications. Six interoperability architectures are examined with advantages and disadvantages of each described in the paper.

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

Promoting A-Priori Interoperability of HLA-Based Simulations in the Space Domain: The SISO Space Reference FOM Initiative

NASA Technical Reports Server (NTRS)

Moller, Bjorn; Garro, Alfredo; Falcone, Alberto; Crues, Edwin Z.; Dexter, Daniel E.

2016-01-01

Distributed and Real-Time Simulation plays a key-role in the Space domain being exploited for missions and systems analysis and engineering as well as for crew training and operational support. One of the most popular standards is the 1516-2010 IEEE Standard for Modeling and Simulation (M&S) High Level Architecture (HLA). HLA supports the implementation of distributed simulations (called Federations) in which a set of simulation entities (called Federates) can interact using a Run-Time Infrastructure (RTI). In a given Federation, a Federate can publish and/or subscribes objects and interactions on the RTI only in accordance with their structures as defined in a FOM (Federation Object Model). Currently, the Space domain is characterized by a set of incompatible FOMs that, although meet the specific needs of different organizations and projects, increases the long-term cost for interoperability. In this context, the availability of a reference FOM for the Space domain will enable the development of interoperable HLA-based simulators for related joint projects and collaborations among worldwide organizations involved in the Space domain (e.g. NASA, ESA, Roscosmos, and JAXA). The paper presents a first set of results achieved by a SISO standardization effort that aims at providing a Space Reference FOM for international collaboration on Space systems simulations.

A step-by-step methodology for enterprise interoperability projects

NASA Astrophysics Data System (ADS)

Chalmeta, Ricardo; Pazos, Verónica

2015-05-01

Enterprise interoperability is one of the key factors for enhancing enterprise competitiveness. Achieving enterprise interoperability is an extremely complex process which involves different technological, human and organisational elements. In this paper we present a framework to help enterprise interoperability. The framework has been developed taking into account the three domains of interoperability: Enterprise Modelling, Architecture and Platform and Ontologies. The main novelty of the framework in comparison to existing ones is that it includes a step-by-step methodology that explains how to carry out an enterprise interoperability project taking into account different interoperability views, like business, process, human resources, technology, knowledge and semantics.

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

Deep Space Habitat Concept of Operations for Extended Duration Transit Missions

NASA Technical Reports Server (NTRS)

Hoffman, Stephen J.; Toups, Larry

2012-01-01

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

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

NASA Technical Reports Server (NTRS)

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

Mission Design and Concept of Operations of a 6U CubeSat Mission for Proximity Operations and RSO Imaging

DTIC Science & Technology

2013-05-29

Design and Concept of Operations of a 6U Cube Sat Mission for NIA Proximity Oper111ions and RSO Imaging 5b. GRANT NUMBER NIA 5c. PROGRAM ELEMENT...NUMBER NIA 6. AUTHOR(S) 5d. PROJECT NUMBER B. Udrea, M. Nayak, M. Ryle, N. Martini, S. Gillespie, T. Grande, S. Caicedo, S. NIA Wilette, A. Baba...K. , Harri s, J. DiGregorio, S. Salzburger, P. Patel , A. Huang 5e. TASK NUMBER NIA 5f. WORK UNIT NUMBER NIA T. PERFORMING ORGANIZATION NAME(S

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.

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

Reinventing User Applications for Mission Control

NASA Technical Reports Server (NTRS)

Trimble, Jay Phillip; Crocker, Alan R.

2010-01-01

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

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.

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.

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

PubMed

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

2014-09-01

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

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

NASA Technical Reports Server (NTRS)

1990-01-01

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

EOS Aqua: Mission Status at the Earth Science Constellation (ESC) Mission Operations Working Group (MOWG) Meeting at the Kennedy Space Center (KSC)

NASA Technical Reports Server (NTRS)

Guit, Bill

2017-01-01

This presentation at the Earth Science Constellation Mission Operations Working Group meeting at KSC in December 2017 to discuss EOS (Earth Observing System) Aqua Earth Science Constellation status. Reviewed and approved by Eric Moyer, ESMO (Earth Science Mission Operations) Deputy Project Manager.

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

NASA Technical Reports Server (NTRS)

Goo, Sherwin

2014-01-01

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

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

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

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

NASA Technical Reports Server (NTRS)

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

2017-01-01

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

Geoscience Information Network (USGIN) Solutions for Interoperable Open Data Access Requirements

NASA Astrophysics Data System (ADS)

Allison, M. L.; Richard, S. M.; Patten, K.

2014-12-01

The geosciences are leading development of free, interoperable open access to data. US Geoscience Information Network (USGIN) is a freely available data integration framework, jointly developed by the USGS and the Association of American State Geologists (AASG), in compliance with international standards and protocols to provide easy discovery, access, and interoperability for geoscience data. USGIN standards include the geologic exchange language 'GeoSciML' (v 3.2 which enables instant interoperability of geologic formation data) which is also the base standard used by the 117-nation OneGeology consortium. The USGIN deployment of NGDS serves as a continent-scale operational demonstration of the expanded OneGeology vision to provide access to all geoscience data worldwide. USGIN is developed to accommodate a variety of applications; for example, the International Renewable Energy Agency streams data live to the Global Atlas of Renewable Energy. Alternatively, users without robust data sharing systems can download and implement a free software packet, "GINstack" to easily deploy web services for exposing data online for discovery and access. The White House Open Data Access Initiative requires all federally funded research projects and federal agencies to make their data publicly accessible in an open source, interoperable format, with metadata. USGIN currently incorporates all aspects of the Initiative as it emphasizes interoperability. The system is successfully deployed as the National Geothermal Data System (NGDS), officially launched at the White House Energy Datapalooza in May, 2014. The USGIN Foundation has been established to ensure this technology continues to be accessible and available.

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

NASA Technical Reports Server (NTRS)

Khan, Ahmed

2010-01-01

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

Maturity Model for Advancing Smart Grid Interoperability

DOE Office of Scientific and Technical Information (OSTI.GOV)

Knight, Mark; Widergren, Steven E.; Mater, J.

2013-10-28

Abstract—Interoperability is about the properties of devices and systems to connect and work properly. Advancing interoperability eases integration and maintenance of the resulting interconnection. This leads to faster integration, lower labor and component costs, predictability of projects and the resulting performance, and evolutionary paths for upgrade. When specifications are shared and standardized, competition and novel solutions can bring new value streams to the community of stakeholders involved. Advancing interoperability involves reaching agreement for how things join at their interfaces. The quality of the agreements and the alignment of parties involved in the agreement present challenges that are best met withmore » process improvement techniques. The GridWise® Architecture Council (GWAC) sponsored by the United States Department of Energy is supporting an effort to use concepts from capability maturity models used in the software industry to advance interoperability of smart grid technology. An interoperability maturity model has been drafted and experience is being gained through trials on various types of projects and community efforts. This paper describes the value and objectives of maturity models, the nature of the interoperability maturity model and how it compares with other maturity models, and experiences gained with its use.« less

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

NASA Technical Reports Server (NTRS)

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

2012-01-01

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

The Concept Of A Potential Operational CryoSat Follow-on Mission

NASA Astrophysics Data System (ADS)

Cullen, R.

2016-12-01

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

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

NASA Technical Reports Server (NTRS)

1970-01-01

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

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

Information Management Challenges in Achieving Coalition Interoperability

DTIC Science & Technology

2001-12-01

by J. Dyer SESSION I: ARCHITECTURES AND STANDARDS: FUNDAMENTAL ISSUES Chairman: Dr I. WHITE (UK) Planning for Interoperability 1 by W.M. Gentleman...framework – a crucial step toward achieving coalition C4I interoperability. TOPICS TO BE COVERED: 1 ) Maintaining secure interoperability 2) Command...d’une coalition. SUJETS À EXAMINER : 1 ) Le maintien d’une interopérabilité sécurisée 2) Les interfaces des systèmes de commandement : 2a

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

NASA Astrophysics Data System (ADS)

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

2016-02-01

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

Rollout Strategy to Implement Interoperable Traceability in the Seafood Industry.

PubMed

Gooch, Martin; Dent, Benjamin; Sylvia, Gilbert; Cusack, Christopher

2017-08-01

Verifying the accuracy and rigor of data exchanged within and between businesses for the purposes of traceability rests on the existence of effective and efficient interoperable information systems that meet users' needs. Interoperability, particularly given the complexities intrinsic to the seafood industry, requires that the systems used by businesses operating along the supply chain share a common technology architecture that is robust, resilient, and evolves as industry needs change. Technology architectures are developed through engaging industry stakeholders in understanding why an architecture is required, the benefits provided to the industry and individual businesses and supply chains, and how the architecture will translate into practical results. This article begins by reiterating the benefits that the global seafood industry can capture by implementing interoperable chain-length traceability and the reason for basing the architecture on a peer-to-peer networked database concept versus more traditional centralized or linear approaches. A summary of capabilities that already exist within the seafood industry that the proposed architecture uses is discussed; and a strategy for implementing the architecture is presented. The 6-step strategy is presented in the form of a critical path. © 2017 Institute of Food Technologists®.

Virtualized Multi-Mission Operations Center (vMMOC) and its Cloud Services

NASA Technical Reports Server (NTRS)

Ido, Haisam Kassim

2017-01-01

His presentation will cover, the current and future, technical and organizational opportunities and challenges with virtualizing a multi-mission operations center. The full deployment of Goddard Space Flight Centers (GSFC) Virtualized Multi-Mission Operations Center (vMMOC) is nearly complete. The Space Science Mission Operations (SSMO) organizations spacecraft ACE, Fermi, LRO, MMS(4), OSIRIS-REx, SDO, SOHO, Swift, and Wind are in the process of being fully migrated to the vMMOC. The benefits of the vMMOC will be the normalization and the standardization of IT services, mission operations, maintenance, and development as well as ancillary services and policies such as collaboration tools, change management systems, and IT Security. The vMMOC will also provide operational efficiencies regarding hardware, IT domain expertise, training, maintenance and support.The presentation will also cover SSMO's secure Situational Awareness Dashboard in an integrated, fleet centric, cloud based web services fashion. Additionally the SSMO Telemetry as a Service (TaaS) will be covered, which allows authorized users and processes to access telemetry for the entire SSMO fleet, and for the entirety of each spacecrafts history. Both services leverage cloud services in a secure FISMA High and FedRamp environment, and also leverage distributed object stores in order to house and provide the telemetry. The services are also in the process of leveraging the cloud computing services elasticity and horizontal scalability. In the design phase is the Navigation as a Service (NaaS) which will provide a standardized, efficient, and normalized service for the fleet's space flight dynamics operations. Additional future services that may be considered are Ground Segment as a Service (GSaaS), Telemetry and Command as a Service (TCaaS), Flight Software Simulation as a Service, etc.

Reminiscing about 15 years of interoperability efforts

DOE PAGES

Van de Sompel, Herbert; Nelson, Michael L.

2015-11-01

Over the past fifteen years, our perspective on tackling information interoperability problems for web-based scholarship has evolved significantly. In this opinion piece, we look back at three efforts that we have been involved in that aptly illustrate this evolution: OAI-PMH, OAI-ORE, and Memento. Understanding that no interoperability specification is neutral, we attempt to characterize the perspectives and technical toolkits that provided the basis for these endeavors. With that regard, we consider repository-centric and web-centric interoperability perspectives, and the use of a Linked Data or a REST/HATEAOS technology stack, respectively. In addition, we lament the lack of interoperability across nodes thatmore » play a role in web-based scholarship, but end on a constructive note with some ideas regarding a possible path forward.« less

IHE based interoperability - benefits and challenges.

PubMed

Wozak, Florian; Ammenwerth, Elske; Hörbst, Alexander; Sögner, Peter; Mair, Richard; Schabetsberger, Thomas

2008-01-01

Optimized workflows and communication between institutions involved in a patient's treatment process can lead to improved quality and efficiency in the healthcare sector. Electronic Health Records (EHRs) provide a patient-centered access to clinical data across institutional boundaries supporting the above mentioned aspects. Interoperability is regarded as vital success factor. However a clear definition of interoperability does not exist. The aim of this work is to define and to assess interoperability criteria as required for EHRs. The definition and assessment of interoperability criteria is supported by the analysis of existing literature and personal experience as well as by discussions with several domain experts. Criteria for interoperability addresses the following aspects: Interfaces, Semantics, Legal and organizational aspects and Security. The Integrating the Healthcare Enterprises initiative (IHE) profiles make a major contribution to these aspects, but they also arise new problems. Flexibility for adoption to different organizational/regional or other specific conditions is missing. Regional or national initiatives should get a possibility to realize their specific needs within the boundaries of IHE profiles. Security so far is an optional element which is one of IHE greatest omissions. An integrated security approach seems to be preferable. Irrespective of the so far practical significance of the IHE profiles it appears to be of great importance, that the profiles are constantly checked against practical experiences and are continuously adapted.

Cyber Threat Assessment of Uplink and Commanding System for Mission Operation

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

Interoperability of Neuroscience Modeling Software

PubMed Central

Cannon, Robert C.; Gewaltig, Marc-Oliver; Gleeson, Padraig; Bhalla, Upinder S.; Cornelis, Hugo; Hines, Michael L.; Howell, Fredrick W.; Muller, Eilif; Stiles, Joel R.; Wils, Stefan; De Schutter, Erik

2009-01-01

Neuroscience increasingly uses computational models to assist in the exploration and interpretation of complex phenomena. As a result, considerable effort is invested in the development of software tools and technologies for numerical simulations and for the creation and publication of models. The diversity of related tools leads to the duplication of effort and hinders model reuse. Development practices and technologies that support interoperability between software systems therefore play an important role in making the modeling process more efficient and in ensuring that published models can be reliably and easily reused. Various forms of interoperability are possible including the development of portable model description standards, the adoption of common simulation languages or the use of standardized middleware. Each of these approaches finds applications within the broad range of current modeling activity. However more effort is required in many areas to enable new scientific questions to be addressed. Here we present the conclusions of the “Neuro-IT Interoperability of Simulators” workshop, held at the 11th computational neuroscience meeting in Edinburgh (July 19-20 2006; http://www.cnsorg.org). We assess the current state of interoperability of neural simulation software and explore the future directions that will enable the field to advance. PMID:17873374

Towards an Open, Distributed Software Architecture for UxS Operations

NASA Technical Reports Server (NTRS)

Cross, Charles D.; Motter, Mark A.; Neilan, James H.; Qualls, Garry D.; Rothhaar, Paul M.; Tran, Loc; Trujillo, Anna C.; Allen, B. Danette

2015-01-01

To address the growing need to evaluate, test, and certify an ever expanding ecosystem of UxS platforms in preparation of cultural integration, NASA Langley Research Center's Autonomy Incubator (AI) has taken on the challenge of developing a software framework in which UxS platforms developed by third parties can be integrated into a single system which provides evaluation and testing, mission planning and operation, and out-of-the-box autonomy and data fusion capabilities. This software framework, named AEON (Autonomous Entity Operations Network), has two main goals. The first goal is the development of a cross-platform, extensible, onboard software system that provides autonomy at the mission execution and course-planning level, a highly configurable data fusion framework sensitive to the platform's available sensor hardware, and plug-and-play compatibility with a wide array of computer systems, sensors, software, and controls hardware. The second goal is the development of a ground control system that acts as a test-bed for integration of the proposed heterogeneous fleet, and allows for complex mission planning, tracking, and debugging capabilities. The ground control system should also be highly extensible and allow plug-and-play interoperability with third party software systems. In order to achieve these goals, this paper proposes an open, distributed software architecture which utilizes at its core the Data Distribution Service (DDS) standards, established by the Object Management Group (OMG), for inter-process communication and data flow. The design decisions proposed herein leverage the advantages of existing robotics software architectures and the DDS standards to develop software that is scalable, high-performance, fault tolerant, modular, and readily interoperable with external platforms and software.

Concepts of Operations for Asteroid Rendezvous Missions Focused on Resources Utilization

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

PACS/information systems interoperability using Enterprise Communication Framework.

PubMed

alSafadi, Y; Lord, W P; Mankovich, N J

1998-06-01

Interoperability among healthcare applications goes beyond connectivity to allow components to exchange structured information and work together in a predictable, coordinated fashion. To facilitate building an interoperability infrastructure, an Enterprise Communication Framework (ECF) was developed by the members of the Andover Working Group for Healthcare Interoperability (AWG-OHI). The ECF consists of four models: 1) Use Case Model, 2) Domain Information Model (DIM), 3) Interaction Model, and 4) Message Model. To realize this framework, a software component called the Enterprise Communicator (EC) is used. In this paper, we will demonstrate the use of the framework in interoperating a picture archiving and communication system (PACS) with a radiology information system (RIS).

The role of architecture and ontology for interoperability.

PubMed

Blobel, Bernd; González, Carolina; Oemig, Frank; Lopéz, Diego; Nykänen, Pirkko; Ruotsalainen, Pekka

2010-01-01

Turning from organization-centric to process-controlled or even to personalized approaches, advanced healthcare settings have to meet special interoperability challenges. eHealth and pHealth solutions must assure interoperability between actors cooperating to achieve common business objectives. Hereby, the interoperability chain also includes individually tailored technical systems, but also sensors and actuators. For enabling corresponding pervasive computing and even autonomic computing, individualized systems have to be based on an architecture framework covering many domains, scientifically managed by specialized disciplines using their specific ontologies in a formalized way. Therefore, interoperability has to advance from a communication protocol to an architecture-centric approach mastering ontology coordination challenges.

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.

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

NASA Technical Reports Server (NTRS)

Samuels, Jessica A.

2013-01-01

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

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

NASA Technical Reports Server (NTRS)

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

2013-01-01

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

Real-time science operations to support a lunar polar volatiles rover mission

NASA Astrophysics Data System (ADS)

Heldmann, Jennifer L.; Colaprete, Anthony; Elphic, Richard C.; Mattes, Greg; Ennico, Kimberly; Fritzler, Erin; Marinova, Margarita M.; McMurray, Robert; Morse, Stephanie; Roush, Ted L.; Stoker, Carol R.

2015-05-01

Future human exploration of the Moon will likely rely on in situ resource utilization (ISRU) to enable long duration lunar missions. Prior to utilizing ISRU on the Moon, the natural resources (in this case lunar volatiles) must be identified and characterized, and ISRU demonstrated on the lunar surface. To enable future uses of ISRU, NASA and the CSA are developing a lunar rover payload that can (1) locate near subsurface volatiles, (2) excavate and analyze samples of the volatile-bearing regolith, and (3) demonstrate the form, extractability and usefulness of the materials. Such investigations are important both for ISRU purposes and for understanding the scientific nature of these intriguing lunar volatile deposits. Temperature models and orbital data suggest near surface volatile concentrations may exist at briefly lit lunar polar locations outside persistently shadowed regions. A lunar rover could be remotely operated at some of these locations for the ∼ 2-14 days of expected sunlight at relatively low cost. Due to the limited operational time available, both science and rover operations decisions must be made in real time, requiring immediate situational awareness, data analysis, and decision support tools. Given these constraints, such a mission requires a new concept of operations. In this paper we outline the results and lessons learned from an analog field campaign in July 2012 which tested operations for a lunar polar rover concept. A rover was operated in the analog environment of Hawaii by an off-site Flight Control Center, a rover navigation center in Canada, a Science Backroom at NASA Ames Research Center in California, and support teams at NASA Johnson Space Center in Texas and NASA Kennedy Space Center in Florida. We find that this type of mission requires highly efficient, real time, remotely operated rover operations to enable low cost, scientifically relevant exploration of the distribution and nature of lunar polar volatiles. The field

Real-Time Science Operations to Support a Lunar Polar Volatiles Rover Mission

NASA Technical Reports Server (NTRS)

Heldmann, Jennifer L.; Colaprete, Anthony; Elphic, Richard C.; Mattes, Greg; Ennico, Kimberly; Fritzler, Erin; Marinova, Margarita M.; McMurray, Robert; Morse, Stephanie; Roush, Ted L.;

The Asteroid Impact and Deflection Assessment (AIDA) mission: Science Proximity Operations

NASA Astrophysics Data System (ADS)

Barnouin, Olivier; Bellerose, Julie; Carnelli, Ian; Carrol, Kieran; Ciarletti, Valérie; Cheng, Andrew F.; Galvez, Andres; Green, Simon F.; Grieger, Bjorn; Hirabayashi, Masatoshi; Herique, Alain; Kueppers, Michael; Minton, David A.; Mellab, Karim; Michel, Patrick; Rivkin, Andrew S.; Rosenblatt, Pascal; Tortora, Paolo; Ulamec, Stephan; Vincent, Jean-Baptiste; Zannoni, Marco

2016-10-01

The moon of the near-Earth binary asteroid 65803 Didymos is the target of the Asteroid Impact and Deflection Assessment (AIDA) mission. This mission is a joint effort between NASA and ESA to investigate the effectiveness of a kinetic impactor in deflecting an asteroid. The mission is composed of two components: the NASA-led Double Asteroid Redirect Test (DART) that will impact Didymos' moon (henceforth Didymos B), and the ESA-led Asteroid Impact Mission (AIM) that will survey the Didymos system. Both will undertake proximity operations to characterize the physical and dynamical properties of the Didymos system that are of maximum importance in the joint AIDA mission to understand the factors at play when assessing the mometum transfer that follows DART's impact into Didymos B. Using much of ESA's Rosetta experience, the AIM mission will undertake proximity operations both before and after DART's impact. AIM's chracterization includes measuring the precise orbital configuration, masses, internal properties, surface geology and regolith properties of the primary and secondary, using visible and thermal imaging, radar measurements and radio science data. AIM will also release the small MASCOT-2 lander, as well as a suite of a CubeSats to help achieve these objectives. DART proximity observations include two phases of imaging. The first makes use of a suite of long range images that will add light curve data to what will be collected from Earth. These data will refine the orbit period of Didymos B, and provide constraints for modeling the shape of both Didymos A and B. The second phase begins just under an hour before impact when resolved imaging of the Didymos system provides further shape model constraints for the visble parts of both Didymos A and B, some possible constraints on the mass of Didymos B and key geological information of both objects and the impact site. In this presentation, we will summarize the proximity operations undertaken by both DART and AIM

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

NASA Technical Reports Server (NTRS)

Werbitzky, Victor

1989-01-01

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

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.

Distributed Mission Operations: Training Today’s Warfighters for Tomorrow’s Conflicts

DTIC Science & Technology

2016-02-01

systems or include dissimilar weapons systems to rehearse more complex mission sets. In addition to networking geographically separated simulators...over the past decade. Today, distributed mission operations can facilitate the rehearsal of theater wide operations, integrating all the anticipated...effective that many aviators earn their basic aircraft qualification before their first flight in the airplane.11 Computer memory was once a

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

NASA Technical Reports Server (NTRS)

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

1994-01-01

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

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;

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.

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

NASA Technical Reports Server (NTRS)

1975-01-01

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

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

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

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

NASA Technical Reports Server (NTRS)

Litomisky, Krystof

2012-01-01

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

Development of multi-mission satellite data systems at the German Remote Sensing Data Centre

NASA Astrophysics Data System (ADS)

Lotz-Iwen, H. J.; Markwitz, W.; Schreier, G.

1998-11-01

This paper focuses on conceptual aspects of the access to multi-mission remote sensing data by online catalogue and information systems. The system ISIS of the German Remote Sensing Data Centre is described as an example of a user interface to earth observation data. ISIS has been designed to support international scientific research as well as operational applications by offering online access to the database via public networks. It provides catalogue retrieval, visualisation and transfer of image data, and is integrated in international activities dedicated to catalogue and archive interoperability. Finally, an outlook is given on international projects dealing with access to remote sensing data in distributed archives.

Innovative Test Operations to Support Orion and Future Human Rated Missions

NASA Technical Reports Server (NTRS)

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

2017-01-01

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

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

NASA Technical Reports Server (NTRS)

Melnick, Gary J.

1990-01-01

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

Activities at the JSC Payload Operations Control Center During Spacelab Mission

NASA Technical Reports Server (NTRS)

1984-01-01

During a Spacelab flight, the hub of activity was the Payload Operations Control Center (POCC) at the Johnson Space Flight Center (JSC) in Houston, Texas. The POCC became home to the management and science teams who worked around the clock to guide and support the mission. All Spacelab principal investigators and their teams of scientists and engineers set up work areas in the POCC. Through the use of computers, they could send commands to their instruments and receive and analyze experiment data. Instantaneous video and audio communications made it possible for scientists on the ground to follow the progress of their research almost as if they were in space with the crew. This real-time interaction between investigators on the ground and the crew in space was probably the most exciting of Spacelab's many capabilities. As principal investigators talked to the payload specialists during the mission, they consulted on experiment operations, made decisions, and shared in the thrill of gaining new knowledge. In December 1990, a newly-established POCC at the Marshall Space Flight Center (MSFC) opened its door for the operations of the Spacelab payloads and experiments, while JSC monitored the Shuttle flight operations. MSFC had managing responsibilities for the Spacelab missions.

Improving Groundwater Data Interoperability: Results of the Second OGC Groundwater Interoperability Experiment

NASA Astrophysics Data System (ADS)

Lucido, J. M.; Booth, N.

2014-12-01

Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage and management of groundwater data is often times distributed across many agencies or organizations. Furthermore these data may be represented in disparate proprietary formats, posing a significant challenge for integration. For this reason standard data models are required to achieve interoperability across geographical and political boundaries. The GroundWater Markup Language 1.0 (GWML1) was developed in 2010 as an extension of the Geography Markup Language (GML) in order to support groundwater data exchange within Spatial Data Infrastructures (SDI). In 2013, development of GWML2 was initiated under the sponsorship of the Open Geospatial Consortium (OGC) for intended adoption by the international community as the authoritative standard for the transfer of groundwater feature data, including data about water wells, aquifers, and related entities. GWML2 harmonizes GWML1 and the EU's INSPIRE models related to geology and hydrogeology. Additionally, an interoperability experiment was initiated to test the model for commercial, technical, scientific, and policy use cases. The scientific use case focuses on the delivery of data required for input into computational flow modeling software used to determine the flow of groundwater within a particular aquifer system. It involves the delivery of properties associated with hydrogeologic units, observations related to those units, and information about the related aquifers. To test this use case web services are being implemented using GWML2 and WaterML2, which is the authoritative standard for water time series observations, in order to serve USGS water well and hydrogeologic data via standard OGC protocols. Furthermore, integration of these data into a computational groundwater flow model will be tested. This submission will present the GWML2 information model and results

Medical Device Plug-and-Play Interoperability Standards and Technology Leadership

DTIC Science & Technology

2017-10-01

Award Number: W81XWH-09-1-0705 TITLE: “Medical Device Plug-and-Play Interoperability Standards and Technology Leadership” PRINCIPAL INVESTIGATOR...Sept 2016 – 20 Sept 2017 4. TITLE AND SUBTITLE “Medical Device Plug-and-Play Interoperability 5a. CONTRACT NUMBER Standards and Technology ...efficiency through interoperable medical technologies . We played a leadership role on interoperability safety standards (AAMI, AAMI/UL Joint

The Long Road to Semantic Interoperability in Support of Public Health: Experiences from Two States

PubMed Central

Vreeman, Daniel J.; Grannis, Shaun J.

2014-01-01

Proliferation of health information technologies creates opportunities to improve clinical and public health, including high quality, safer care and lower costs. To maximize such potential benefits, health information technologies must readily and reliably exchange information with other systems. However, evidence from public health surveillance programs in two states suggests that operational clinical information systems often fail to use available standards, a barrier to semantic interoperability. Furthermore, analysis of existing policies incentivizing semantic interoperability suggests they have limited impact and are fragmented. In this essay, we discuss three approaches for increasing semantic interoperability to support national goals for using health information technologies. A clear, comprehensive strategy requiring collaborative efforts by clinical and public health stakeholders is suggested as a guide for the long road towards better population health data and outcomes. PMID:24680985

MDP: Reliable File Transfer for Space Missions

NASA Technical Reports Server (NTRS)

Rash, James; Criscuolo, Ed; Hogie, Keith; Parise, Ron; Hennessy, Joseph F. (Technical Monitor)

2002-01-01

This paper presents work being done at NASA/GSFC by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990's, MDP is now in daily use by both the US Post Office and the DoD. This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Neck Oriented Reliable Multicast) is in the process of becoming an IETF standard.

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

DTIC Science & Technology

2016-03-01

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

Evolution from Packet Utilisation to Mission Operation Services

NASA Astrophysics Data System (ADS)

Cooper, Sam; Forwell, Stuart D.

2012-08-01

The ECSS Packet Utilisation Standard (PUS) and the forthcoming CCSDS Mission Operations (MO) Services occupy a very similar domain. This paper discusses the history of the two standards, their relationship and how the two can co-exist in the near term and long terms. It also covers implications with implementing MO services in current and future on-board architectures.

Test Protocols for Advanced Inverter Interoperability Functions - Appendices

DOE Office of Scientific and Technical Information (OSTI.GOV)

Johnson, Jay Dean; Gonzalez, Sigifredo; Ralph, Mark E.

2013-11-01

Distributed energy resources (DER) such as photovoltaic (PV) systems, when deployed in a large scale, are capable of influencing significantly the operation of power systems. Looking to the future, stakeholders are working on standards to make it possible to manage the potentially complex interactions between DER and the power system. In 2009, the Electric Power Research Institute (EPRI), Sandia National Laboratories (SNL) with the U.S. Department of Energy (DOE), and the Solar Electric Power Association (SEPA) initiated a large industry collaborative to identify and standardize definitions for a set of DER grid support functions. While the initial effort concentrated onmore » grid-tied PV inverters and energy storage systems, the concepts have applicability to all DER. A partial product of this on-going effort is a reference definitions document (IEC TR 61850-90-7, Object models for power converters in distributed energy resources (DER) systems) that has become a basis for expansion of related International Electrotechnical Commission (IEC) standards, and is supported by US National Institute of Standards and Technology (NIST) Smart Grid Interoperability Panel (SGIP). Some industry-led organizations advancing communications protocols have also embraced this work. As standards continue to evolve, it is necessary to develop test protocols to independently verify that the inverters are properly executing the advanced functions. Interoperability is assured by establishing common definitions for the functions and a method to test compliance with operational requirements. This document describes test protocols developed by SNL to evaluate the electrical performance and operational capabilities of PV inverters and energy storage, as described in IEC TR 61850-90-7. While many of these functions are not now required by existing grid codes or may not be widely available commercially, the industry is rapidly moving in that direction. Interoperability issues are already

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.

Enabling Interoperable Space Robots With the Joint Technical Architecture for Robotic Systems (JTARS)

NASA Technical Reports Server (NTRS)

Bradley, Arthur; Dubowsky, Steven; Quinn, Roger; Marzwell, Neville

2005-01-01

Robots that operate independently of one another will not be adequate to accomplish the future exploration tasks of long-distance autonomous navigation, habitat construction, resource discovery, and material handling. Such activities will require that systems widely share information, plan and divide complex tasks, share common resources, and physically cooperate to manipulate objects. Recognizing the need for interoperable robots to accomplish the new exploration initiative, NASA s Office of Exploration Systems Research & Technology recently funded the development of the Joint Technical Architecture for Robotic Systems (JTARS). JTARS charter is to identify the interface standards necessary to achieve interoperability among space robots. A JTARS working group (JTARS-WG) has been established comprising recognized leaders in the field of space robotics including representatives from seven NASA centers along with academia and private industry. The working group s early accomplishments include addressing key issues required for interoperability, defining which systems are within the project s scope, and framing the JTARS manuals around classes of robotic systems.

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.

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

Designing a Distributed Space Systems Simulation in Accordance with the Simulation Interoperability Standards Organization (SISO)

NASA Technical Reports Server (NTRS)

Cowen, Benjamin

2011-01-01

Simulations are essential for engineering design. These virtual realities provide characteristic data to scientists and engineers in order to understand the details and complications of the desired mission. A standard development simulation package known as Trick is used in developing a source code to model a component (federate in HLA terms). The runtime executive is integrated into an HLA based distributed simulation. TrickHLA is used to extend a Trick simulation for a federation execution, develop a source code for communication between federates, as well as foster data input and output. The project incorporates international cooperation along with team collaboration. Interactions among federates occur throughout the simulation, thereby relying on simulation interoperability. Communication through the semester went on between participants to figure out how to create this data exchange. The NASA intern team is designing a Lunar Rover federate and a Lunar Shuttle federate. The Lunar Rover federate supports transportation across the lunar surface and is essential for fostering interactions with other federates on the lunar surface (Lunar Shuttle, Lunar Base Supply Depot and Mobile ISRU Plant) as well as transporting materials to the desired locations. The Lunar Shuttle federate transports materials to and from lunar orbit. Materials that it takes to the supply depot include fuel and cargo necessary to continue moon-base operations. This project analyzes modeling and simulation technologies as well as simulation interoperability. Each team from participating universities will work on and engineer their own federate(s) to participate in the SISO Spring 2011 Workshop SIW Smackdown in Boston, Massachusetts. This paper will focus on the Lunar Rover federate.

Rationale, Scenarios, and Profiles for the Application of the Internet Protocol Suite (IPS) in Space Operations

NASA Technical Reports Server (NTRS)

Benbenek, Daniel B.; Walsh, William

2010-01-01

This greenbook captures some of the current, planned and possible future uses of the Internet Protocol (IP) as part of Space Operations. It attempts to describe how the Internet Protocol is used in specific scenarios. Of primary focus is low-earth-orbit space operations, which is referred to here as the design reference mission (DRM). This is because most of the program experience drawn upon derives from this type of mission. Application profiles are provided. This includes parameter settings programs have proposed for sending IP datagrams over CCSDS links, the minimal subsets and features of the IP protocol suite and applications expected for interoperability between projects, and the configuration, operations and maintenance of these IP functions. Of special interest is capturing the lessons learned from the Constellation Program in this area, since that program included a fairly ambitious use of the Internet Protocol.

Report on the Second Catalog Interoperability Workshop

NASA Technical Reports Server (NTRS)

Thieman, James R.; James, Mary E.

1988-01-01

The events, resolutions, and recommendations of the Second Catalog Interoperability Workshop, held at JPL in January, 1988, are discussed. This workshop dealt with the issues of standardization and communication among directories, catalogs, and inventories in the earth and space science data management environment. The Directory Interchange Format, being constructed as a standard for the exchange of directory information among participating data systems, is discussed. Involvement in the Interoperability effort by NASA, NOAA, ISGS, and NSF is described, and plans for future interoperability considered. The NASA Master Directory prototype is presented and critiqued and options for additional capabilities debated.

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.

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.

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

NASA Astrophysics Data System (ADS)

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

2011-09-01

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

Functional requirements document for NASA/MSFC Earth Science and Applications Division: Data and information system (ESAD-DIS). Interoperability, 1992

NASA Technical Reports Server (NTRS)

Stephens, J. Briscoe; Grider, Gary W.

1992-01-01

These Earth Science and Applications Division-Data and Information System (ESAD-DIS) interoperability requirements are designed to quantify the Earth Science and Application Division's hardware and software requirements in terms of communications between personal and visualization workstation, and mainframe computers. The electronic mail requirements and local area network (LAN) requirements are addressed. These interoperability requirements are top-level requirements framed around defining the existing ESAD-DIS interoperability and projecting known near-term requirements for both operational support and for management planning. Detailed requirements will be submitted on a case-by-case basis. This document is also intended as an overview of ESAD-DIs interoperability for new-comers and management not familiar with these activities. It is intended as background documentation to support requests for resources and support requirements.

The GMES Sentinel-5 mission for operational atmospheric monitoring: status and developments

NASA Astrophysics Data System (ADS)

Sierk, Bernd; Bezy, Jean-Loup; Caron, Jerôme; Meynard, Roland; Veihelmann, Ben; Ingmann, Paul

2017-11-01

Sentinel-5 is an atmospheric monitoring mission planned in the frame of the joint EU/ESA initiative Global Monitoring for Environment and Security (GMES). The objective of the mission, planned to be launched in 2020, is the operational monitoring of trace gas concentrations for atmospheric chemistry and climate applications.

JAXA-NASA Interoperability Demonstration for Application of DTN Under Simulated Rain Attenuation

NASA Technical Reports Server (NTRS)

Suzuki, Kiyoshisa; Inagawa, Shinichi; Lippincott, Jeff; Cecil, Andrew J.

2014-01-01

As is well known, K-band or higher band communications in space link segment often experience intermittent disruptions caused by heavy rainfall. In view of keeping data integrity and establishing autonomous operations under such situation, it is important to consider introducing a tolerance mechanism such as Delay/Disruption Tolerant Networking (DTN). The Consultative Committee for Space Data Systems (CCSDS) is studying DTN as part of the standardization activities for space data systems. As a contribution to CCSDS and a feasibility study for future utilization of DTN, Japan Aerospace Exploration Agency (JAXA) and National Aeronautics and Space Administration (NASA) conducted an interoperability demonstration for confirming its tolerance mechanism and capability of automatic operation using Data Relay Test Satellite (DRTS) space link and its ground terminals. Both parties used the Interplanetary Overlay Network (ION) open source software, including the Bundle Protocol, the Licklider Transmission Protocol, and Contact Graph Routing. This paper introduces the contents of the interoperability demonstration and its results.

Personal Health Records: Is Rapid Adoption Hindering Interoperability?

PubMed Central

Studeny, Jana; Coustasse, Alberto

2014-01-01

The establishment of the Meaningful Use criteria has created a critical need for robust interoperability of health records. A universal definition of a personal health record (PHR) has not been agreed upon. Standardized code sets have been built for specific entities, but integration between them has not been supported. The purpose of this research study was to explore the hindrance and promotion of interoperability standards in relationship to PHRs to describe interoperability progress in this area. The study was conducted following the basic principles of a systematic review, with 61 articles used in the study. Lagging interoperability has stemmed from slow adoption by patients, creation of disparate systems due to rapid development to meet requirements for the Meaningful Use stages, and rapid early development of PHRs prior to the mandate for integration among multiple systems. Findings of this study suggest that deadlines for implementation to capture Meaningful Use incentive payments are supporting the creation of PHR data silos, thereby hindering the goal of high-level interoperability. PMID:25214822

Achieving Interoperability in GEOSS - How Close Are We?

NASA Astrophysics Data System (ADS)

Arctur, D. K.; Khalsa, S. S.; Browdy, S. F.

2010-12-01

A primary goal of the Global Earth Observing System of System (GEOSS) is improving the interoperability between the observational, modelling, data assimilation, and prediction systems contributed by member countries. The GEOSS Common Infrastructure (GCI) comprises the elements designed to enable discovery and access to these diverse data and information sources. But to what degree can the mechanisms for accessing these data, and the data themselves, be considered interoperable? Will the separate efforts by Communities of Practice within GEO to build their own portals, such as for Energy, Biodiversity, and Air Quality, lead to fragmentation or synergy? What communication and leadership do we need with these communities to improve interoperability both within and across such communities? The Standards and Interoperability Forum (SIF) of GEO's Architecture and Data Committee has assessed progress towards achieving the goal of global interoperability and made recommendations regarding evolution of the architecture and overall data strategy to ensure fulfillment of the GEOSS vision. This presentation will highlight the results of this study, and directions for further work.

The flyby of Rosetta at asteroid Šteins - mission and science operations

NASA Astrophysics Data System (ADS)

Accomazzo, Andrea; Wirth, Kristin R.; Lodiot, Sylvain; Küppers, Michael; Schwehm, Gerhard

2010-07-01

The international Rosetta mission, a cornerstone mission of the european space agency scientific Programme, was launched on 2nd March 2004 on its 10 years journey towards a rendezvous with comet Churyumov-Gerasimenko ( Gardini et al., 1999). During its interplanetary flight towards its target Rosetta crosses the asteroid belt twice with the opportunity to observe at close quarters two asteroids: (2867)-Šteins in 2008 and (21)-Lutetia in 2010. The spacecraft design was such that these opportunities could be fully exploited to deliver valuable data to the scientific community. The mission trajectory was controlled such that Rosetta would fly next to asteroid Šteins on the 5th of September 2008 with a relative speed of 8.6 km/s at a minimum distance of 800 km. Mission operations have been carefully planned to achieve the best possible flyby scenario and scientific outcome. The flyby scenario, the optical navigation campaign, and the planning of the scientific observations had to be adapted by the Mission and the Science Operations Centres to the demanding requirements expressed by the scientific community. The flyby was conducted as planned with a large number of successful observations.

Interoperability Outlook in the Big Data Future

NASA Astrophysics Data System (ADS)

Kuo, K. S.; Ramachandran, R.

2015-12-01

The establishment of distributed active archive centers (DAACs) as data warehouses and the standardization of file format by NASA's Earth Observing System Data Information System (EOSDIS) had doubtlessly propelled interoperability of NASA Earth science data to unprecedented heights in the 1990s. However, we obviously still feel wanting two decades later. We believe the inadequate interoperability we experience is a result of the the current practice that data are first packaged into files before distribution and only the metadata of these files are cataloged into databases and become searchable. Data therefore cannot be efficiently filtered. Any extensive study thus requires downloading large volumes of data files to a local system for processing and analysis.The need to download data not only creates duplication and inefficiency but also further impedes interoperability, because the analysis has to be performed locally by individual researchers in individual institutions. Each institution or researcher often has its/his/her own preference in the choice of data management practice as well as programming languages. Analysis results (derived data) so produced are thus subject to the differences of these practices, which later form formidable barriers to interoperability. A number of Big Data technologies are currently being examined and tested to address Big Earth Data issues. These technologies share one common characteristics: exploiting compute and storage affinity to more efficiently analyze large volumes and great varieties of data. Distributed active "archive" centers are likely to evolve into distributed active "analysis" centers, which not only archive data but also provide analysis service right where the data reside. "Analysis" will become the more visible function of these centers. It is thus reasonable to expect interoperability to improve because analysis, in addition to data, becomes more centralized. Within a "distributed active analysis center

Special Topic Interoperability and EHR: Combining openEHR, SNOMED, IHE, and Continua as approaches to interoperability on national eHealth.

PubMed

Beštek, Mate; Stanimirović, Dalibor

2017-08-09

The main aims of the paper comprise the characterization and examination of the potential approaches regarding interoperability. This includes openEHR, SNOMED, IHE, and Continua as combined interoperability approaches, possibilities for their incorporation into the eHealth environment, and identification of the main success factors in the field, which are necessary for achieving required interoperability, and consequently, for the successful implementation of eHealth projects in general. The paper represents an in-depth analysis regarding the potential application of openEHR, SNOMED, IHE and Continua approaches in the development and implementation process of eHealth in Slovenia. The research method used is both exploratory and deductive in nature. The methodological framework is grounded on information retrieval with a special focus on research and charting of existing experience in the field, and sources, both electronic and written, which include interoperability concepts and related implementation issues. The paper will try to answer the following inquiries that are complementing each other: 1. Scrutiny of the potential approaches, which could alleviate the pertinent interoperability issues in the Slovenian eHealth context. 2. Analyzing the possibilities (requirements) for their inclusion in the construction process for individual eHealth solutions. 3. Identification and charting the main success factors in the interoperability field that critically influence development and implementation of eHealth projects in an efficient manner. Provided insights and identified success factors could serve as a constituent of the strategic starting points for continuous integration of interoperability principles into the healthcare domain. Moreover, the general implementation of the identified success factors could facilitate better penetration of ICT into the healthcare environment and enable the eHealth-based transformation of the health system especially in the countries

Managing Risk for Cassini During Mission Operations and Data Analysis (MOandDA)

NASA Technical Reports Server (NTRS)

Witkowski, Mona M.

2002-01-01

A Risk Management Process has been tailored for Cassini that not only satisfies the requirements of NASA and JPL, but also allows the Program to proactively identify and assess risks that threaten mission objectives. Cassini Risk Management is a team effort that involves both management and engineering staff. The process is managed and facilitated by the Mission Assurance Manager (MAM), but requires regular interactions with Program Staff and team members to instill the risk management philosophy into the day to day mission operations. While Risk Management is well defined for projects in the development phase, it is a relatively new concept for Mission Operations. The Cassini team has embraced this process and has begun using it in an effective, proactive manner, to ensure mission success. It is hoped that the Cassini Risk Management Process will form the basis by which risk management is conducted during MO&DA on future projects. proactive in identifying, assessing and mitigating risks before they become problems. Cost ehtiveness is achieved by: Comprehensively identifying risks Rapidly assessing which risks require the expenditure of pruject cewums Taking early actions to mitigate these risks Iterating the process frequently, to be responsive to the dynamic internal and external environments The Cassini Program has successfully implemented a Risk Management Process for mission operations, The initial SRL has been developed and input into he online tool. The Risk Management webbased system has been rolled out for use by the flight team and risk owners we working proactive in identifying, assessing and mitigating risks before they become problems. Cost ehtiveness is achieved by: Comprehensively identifying risks Rapidly assessing which risks require the expenditure of pruject cewums Taking early actions to mitigate these risks Iterating the process frequently, to be responsive to the dynamic internal and external environments The Cassini Program has successfully

Enabling data access and interoperability at the EOS Land Processes Distributed Active Archive Center

NASA Astrophysics Data System (ADS)

Meyer, D. J.; Gallo, K. P.

2009-12-01

The NASA Earth Observation System (EOS) is a long-term, interdisciplinary research mission to study global-scale processes that drive Earth systems. This includes a comprehensive data and information system to provide Earth science researchers with easy, affordable, and reliable access to the EOS and other Earth science data through the EOS Data and Information System (EOSDIS). Data products from EOS and other NASA Earth science missions are stored at Distributed Active Archive Centers (DAACs) to support interactive and interoperable retrieval and distribution of data products. ¶ The Land Processes DAAC (LP DAAC), located at the US Geological Survey’s (USGS) Earth Resources Observation and Science (EROS) Center is one of the twelve EOSDIS data centers, providing both Earth science data and expertise, as well as a mechanism for interaction between EOS data investigators, data center specialists, and other EOS-related researchers. The primary mission of the LP DAAC is stewardship for land data products from the Advanced Spaceborne Thermal Emission and Reflection Radiometer (ASTER) and the Moderate Resolution Imaging Spectroradiometer (MODIS) instruments on the Terra and Aqua observation platforms. The co-location of the LP DAAC at EROS strengthens the relationship between the EOSDIS and USGS Earth science activities, linking the basic research and technology development mission of NASA to the operational mission requirements of the USGS. This linkage, along with the USGS’ role as steward of land science data such as the Landsat archive, will prove to be especially beneficial when extending both USGS and EOSDIS data records into the Decadal Survey era. ¶ This presentation provides an overview of the evolution of LP DAAC efforts over the years to improve data discovery, retrieval and preparation services, toward a future of integrated data interoperability between EOSDIS data centers and data holdings of the USGS and its partner agencies. Historical developmental

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.

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.

Interoperability Assets for Patient Summary Components: A Gap Analysis.

PubMed

Heitmann, Kai U; Cangioli, Giorgio; Melgara, Marcello; Chronaki, Catherine

2018-01-01

The International Patient Summary (IPS) standards aim to define the specifications for a minimal and non-exhaustive Patient Summary, which is specialty-agnostic and condition-independent, but still clinically relevant. Meanwhile, health systems are developing and implementing their own variation of a patient summary while, the eHealth Digital Services Infrastructure (eHDSI) initiative is deploying patient summary services across countries in the Europe. In the spirit of co-creation, flexible governance, and continuous alignment advocated by eStandards, the Trillum-II initiative promotes adoption of the patient summary by engaging standards organizations, and interoperability practitioners in a community of practice for digital health to share best practices, tools, data, specifications, and experiences. This paper compares operational aspects of patient summaries in 14 case studies in Europe, the United States, and across the world, focusing on how patient summary components are used in practice, to promote alignment and joint understanding that will improve quality of standards and lower costs of interoperability.

ACTS 118x: High Speed TCP Interoperability Testing

NASA Technical Reports Server (NTRS)

Brooks, David E.; Buffinton, Craig; Beering, Dave R.; Welch, Arun; Ivancic, William D.; Zernic, Mike; Hoder, Douglas J.

1999-01-01

With the recent explosion of the Internet and the enormous business opportunities available to communication system providers, great interest has developed in improving the efficiency of data transfer over satellite links using the Transmission Control Protocol (TCP) of the Internet Protocol (IP) suite. The NASA's ACTS experiments program initiated a series of TCP experiments to demonstrate scalability of TCP/IP and determine to what extent the protocol can be optimized over a 622 Mbps satellite link. Through partnerships with the government technology oriented labs, computer, telecommunication, and satellite industries NASA Glenn was able to: (1) promote the development of interoperable, high-performance TCP/IP implementations across multiple computing / operating platforms; (2) work with the satellite industry to answer outstanding questions regarding the use of standard protocols (TCP/IP and ATM) for the delivery of advanced data services, and for use in spacecraft architectures; and (3) conduct a series of TCP/IP interoperability tests over OC12 ATM over a satellite network in a multi-vendor environment using ACTS. The experiments' various network configurations and the results are presented.

A Potential Operational CryoSat Follow-on Mission Concept and Design

NASA Astrophysics Data System (ADS)

Cullen, R.

2015-12-01

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

CCP interoperability and system stability

NASA Astrophysics Data System (ADS)

Feng, Xiaobing; Hu, Haibo

2016-09-01

To control counterparty risk, financial regulations such as the Dodd-Frank Act are increasingly requiring standardized derivatives trades to be cleared by central counterparties (CCPs). It is anticipated that in the near term future, CCPs across the world will be linked through interoperability agreements that facilitate risk sharing but also serve as a conduit for transmitting shocks. This paper theoretically studies a networked network with CCPs that are linked through interoperability arrangements. The major finding is that the different configurations of networked network CCPs contribute to the different properties of the cascading failures.

Lemnos interoperable security project.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Halbgewachs, Ronald D.

2010-03-01

With the Lemnos framework, interoperability of control security equipment is straightforward. To obtain interoperability between proprietary security appliance units, one or both vendors must now write cumbersome 'translation code.' If one party changes something, the translation code 'breaks.' The Lemnos project is developing and testing a framework that uses widely available security functions and protocols like IPsec - to form a secure communications channel - and Syslog, to exchange security log messages. Using this model, security appliances from two or more different vendors can clearly and securely exchange information, helping to better protect the total system. Simplify regulatory compliance inmore » a complicated security environment by leveraging the Lemnos framework. As an electric utility, are you struggling to implement the NERC CIP standards and other regulations? Are you weighing the misery of multiple management interfaces against committing to a ubiquitous single-vendor solution? When vendors build their security appliances to interoperate using the Lemnos framework, it becomes practical to match best-of-breed offerings from an assortment of vendors to your specific control systems needs. The Lemnos project is developing and testing a framework that uses widely available open-source security functions and protocols like IPsec and Syslog to create a secure communications channel between appliances in order to exchange security data.« less

OR.NET: a service-oriented architecture for safe and dynamic medical device interoperability.

PubMed

Kasparick, Martin; Schmitz, Malte; Andersen, Björn; Rockstroh, Max; Franke, Stefan; Schlichting, Stefan; Golatowski, Frank; Timmermann, Dirk

2018-02-23

Modern surgical departments are characterized by a high degree of automation supporting complex procedures. It recently became apparent that integrated operating rooms can improve the quality of care, simplify clinical workflows, and mitigate equipment-related incidents and human errors. Particularly using computer assistance based on data from integrated surgical devices is a promising opportunity. However, the lack of manufacturer-independent interoperability often prevents the deployment of collaborative assistive systems. The German flagship project OR.NET has therefore developed, implemented, validated, and standardized concepts for open medical device interoperability. This paper describes the universal OR.NET interoperability concept enabling a safe and dynamic manufacturer-independent interconnection of point-of-care (PoC) medical devices in the operating room and the whole clinic. It is based on a protocol specifically addressing the requirements of device-to-device communication, yet also provides solutions for connecting the clinical information technology (IT) infrastructure. We present the concept of a service-oriented medical device architecture (SOMDA) as well as an introduction to the technical specification implementing the SOMDA paradigm, currently being standardized within the IEEE 11073 service-oriented device connectivity (SDC) series. In addition, the Session concept is introduced as a key enabler for safe device interconnection in highly dynamic ensembles of networked medical devices; and finally, some security aspects of a SOMDA are discussed.

A Mission Concept for FUSE Operations in GFY09 and Beyond

NASA Astrophysics Data System (ADS)

Moos, H. W.; Sonneborn, G.; Blair, W. P.; Kruk, J. W.; FUSE Science Operations Team

2007-05-01

We are developing a new mission concept for the Far Ultraviolet Spectroscopic Explorer (FUSE) that would significantly reduce operating costs but would continue the availability of this unique resource into GFY09 and beyond. Launched in 1999, the FUSE satellite obtains R=20,000 spectra of astronomical sources in the far-ultraviolet (912 - 1187 A) wavelength range. The FUSE scientific instrument remains healthy and the satellite has made a remarkable recovery from attitude control problems in late 2004. We expect FUSE to remain a viable scientific tool for the foreseeable future. Current plans for FUSE operations extend through GFY2008 (Sept. 30, 2008). Key elements of this new mission concept include a) continued automation and streamlining of operations to reduce costs, and b) an emphasis on a small number of unique, high priority science programs, particularly those requiring integration times on key targets that are significantly longer than has been possible in the mission design to date. A prime example of the latter would be 100 - 400 ks integrations on selected quasars to provide much improved diagnostic power to study the intergalactic medium. Synergy with the scientific objectives of the Cosmic Origins Spectrograph (COS) program on HST, and the complementary nature of FUSE and COS data on the same sightlines, is but one major motivation for this operations model. In addition to programs emphasizing very long integrations, opportunities for other high priority targets would exist. We will describe some of the ongoing development toward such an operations model as well as the scientific drivers discussed to date. Community input on these and other science drivers for extended FUSE operations is encouraged. FUSE is operated for NASA by Johns Hopkins University under NASA contract NAS5-32985.

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

NASA Technical Reports Server (NTRS)

1990-01-01

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

Asteroid Redirect Mission Proximity Operations for Reference Target Asteroid 2008 EV5

NASA Technical Reports Server (NTRS)

Reeves, David M.; Mazanek, Daniel D.; Cichy, Benjamin D.; Broschart, Steve B.; Deweese, Keith D.

2016-01-01

NASA's Asteroid Redirect Mission (ARM) is composed of two segments, the Asteroid Redirect Robotic Mission (ARRM), and the Asteroid Redirect Crewed Mission (ARCM). In March of 2015, NASA selected the Robotic Boulder Capture Option1 as the baseline for the ARRM. This option will capture a multi-ton boulder, (typically 2-4 meters in size) from the surface of a large (greater than approx.100 m diameter) Near-Earth Asteroid (NEA) and return it to cis-lunar space for subsequent human exploration during the ARCM. Further human and robotic missions to the asteroidal material would also be facilitated by its return to cis-lunar space. In addition, prior to departing the asteroid, the Asteroid Redirect Vehicle (ARV) will perform a demonstration of the Enhanced Gravity Tractor (EGT) planetary defense technique2. This paper will discuss the proximity operations which have been broken into three phases: Approach and Characterization, Boulder Capture, and Planetary Defense Demonstration. Each of these phases has been analyzed for the ARRM reference target, 2008 EV5, and a detailed baseline operations concept has been developed.

Robotics Systems Joint Project Office (RSJPO) Interoperability Profiles (IOPS) 101

DTIC Science & Technology

2012-07-01

interoperability, although they are supported by some interoperability attributes  For example, stair climbing » Stair climbing is not something that...IOPs need to specify » However, the mobility & actuation related interoperable messages can be used to provide stair climbing » Also...interoperability can enable management of different poses or modes, one of which may be stair climbing R O B O T IC S Y S T E M S J P O L e a d e r s h i p

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

NASA Technical Reports Server (NTRS)

Stehly, Joseph S.

2006-01-01

The daily preparation of uplink products (commands and files) for Deep Impact was as problematic as the final encounter images were spectacular. The operations team was faced with many challenges during the six-month mission to comet Tempel One of the biggest difficulties was that the Deep Impact Flyby and Impactor vehicles necessitated a high volume of uplink products while also utilizing a new uplink file transfer capability. The Jet Propulsion Laboratory (JPL) Multi-Mission Ground Systems and Services (MGSS) Mission Planning and Sequence Team (MPST) had the responsibility of preparing the uplink products for use on the two spacecraft. These responsibilities included processing nearly 15,000 flight products, modeling the states of the spacecraft during all activities for subsystem review, and ensuring that the proper commands and files were uplinked to the spacecraft. To guarantee this transpired and the health and safety of the two spacecraft were not jeopardized several new ground scripts and procedures were developed while the Deep Impact Flyby and Impactor spacecraft were en route to their encounter with Tempel-1. These scripts underwent several adaptations throughout the entire mission up until three days before the separation of the Flyby and Impactor vehicles. The problems presented by Deep Impact's daily operations and the development of scripts and procedures to ease those challenges resulted in several valuable lessons learned. These lessons are now being integrated into the design of current and future MGSS missions at JPL.

A Service Oriented Architecture Approach to Achieve Interoperability between Immunization Information Systems in Iran.

PubMed

Hosseini, Masoud; Ahmadi, Maryam; Dixon, Brian E

2014-01-01

Clinical decision support (CDS) systems can support vaccine forecasting and immunization reminders; however, immunization decision-making requires data from fragmented, independent systems. Interoperability and accurate data exchange between immunization information systems (IIS) is an essential factor to utilize Immunization CDS systems. Service oriented architecture (SOA) and Health Level 7 (HL7) are dominant standards for web-based exchange of clinical information. We implemented a system based on SOA and HL7 v3 to support immunization CDS in Iran. We evaluated system performance by exchanging 1500 immunization records for roughly 400 infants between two IISs. System turnaround time is less than a minute for synchronous operation calls and the retrieved immunization history of infants were always identical in different systems. CDS generated reports were accordant to immunization guidelines and the calculations for next visit times were accurate. Interoperability is rare or nonexistent between IIS. Since inter-state data exchange is rare in United States, this approach could be a good prototype to achieve interoperability of immunization information.

Understanding cost growth during operations of planetary missions: An explanation of changes

NASA Astrophysics Data System (ADS)

McNeill, J. F.; Chapman, E. L.; Sklar, M. E.

In the development of project cost estimates for interplanetary missions, considerable focus is generally given to the development of cost estimates for the development of ground, flight, and launch systems, i.e., Phases B, C, and D. Depending on the project team, efforts expended to develop cost estimates for operations (Phase E) may be relatively less rigorous than that devoted to estimates for ground and flight systems development. Furthermore, the project team may be challenged to develop a solid estimate of operations cost in the early stages of mission development, e.g., Concept Study Report or Systems Requirement Review (CSR/SRR), Preliminary Design Review (PDR), as mission specific peculiarities that impact cost may not be well understood. In addition, a methodology generally used to develop Phase E cost is engineering build-up, also known as “ grass roots” . Phase E can include cost and schedule risks that are not anticipated at the time of the major milestone reviews prior to launch. If not incorporated into the engineering build-up cost method for Phase E, this may translate into an estimation of the complexity of operations and overall cost estimates that are not mature and at worse, insufficient. As a result, projects may find themselves with thin reserves during cruise and on-orbit operations or project overruns prior to the end of mission. This paper examines a set of interplanetary missions in an effort to better understand the reasons for cost and staffing growth in Phase E. The method used in the study is discussed as well as the major findings summarized as the Phase E Explanation of Change (EoC). Research for the study entailed the review of project materials, including Estimates at Completion (EAC) for Phase E and staffing profiles, major project milestone reviews, e.g., CSR, PDR, Critical Design Review (CDR), the interviewing of select project and mission management, and review of Phase E replan materials. From this work, a detai- ed

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.

47 CFR 0.192 - Emergency Response Interoperability Center.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 1 2014-10-01 2014-10-01 false Emergency Response Interoperability Center. 0.192 Section 0.192 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL COMMISSION ORGANIZATION Organization Public Safety and Homeland Security Bureau § 0.192 Emergency Response Interoperability Center. (a...

47 CFR 0.192 - Emergency Response Interoperability Center.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 1 2013-10-01 2013-10-01 false Emergency Response Interoperability Center. 0.192 Section 0.192 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL COMMISSION ORGANIZATION Organization Public Safety and Homeland Security Bureau § 0.192 Emergency Response Interoperability Center. (a...

47 CFR 0.192 - Emergency Response Interoperability Center.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 1 2011-10-01 2011-10-01 false Emergency Response Interoperability Center. 0.192 Section 0.192 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL COMMISSION ORGANIZATION Organization Public Safety and Homeland Security Bureau § 0.192 Emergency Response Interoperability Center. (a...

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

NASA Astrophysics Data System (ADS)

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

2013-10-01

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

Telemetry packetization for improved mission operations. [instrument packages for Space Shuttle mission operations data management

NASA Technical Reports Server (NTRS)

Greene, E. P.

1976-01-01

The requirements for mission-operations data management will accelerate sharply when the Space Transportation System (i.e., Space Shuttle) becomes the primary vehicle for research from space. These demands can be satisfied most effectively by providing a higher-level source encoding function within the spaceborne vehicle. An Instrument Telemetry Packet (ITP) concept is described which represents an alternative to the conventional multiplexed telemetry frame approach for acquiring spaceborne instrument data. By providing excellent data-integrity protection at the source and a variable instrument bandwidth capability, this ITP concept represents a significant improvement over present data acquisition procedures. Realignments in the ground telemetry processing functions are described which are intended to take advantage of the ITP concept and to make the data management system more responsive to the scientific investigators.

Interoperable web applications for sharing data and products of the International DORIS Service

NASA Astrophysics Data System (ADS)

Soudarin, L.; Ferrage, P.

2017-12-01

The International DORIS Service (IDS) was created in 2003 under the umbrella of the International Association of Geodesy (IAG) to foster scientific research related to the French satellite tracking system DORIS and to deliver scientific products, mostly related to the International Earth rotation and Reference systems Service (IERS). Since its start, the organization has continuously evolved, leading to additional and improved operational products from an expanded set of DORIS Analysis Centers. In addition, IDS has developed services for sharing data and products with the users. Metadata and interoperable web applications are proposed to explore, visualize and download the key products such as the position time series of the geodetic points materialized at the ground tracking stations. The Global Geodetic Observing System (GGOS) encourages the IAG Services to develop such interoperable facilities on their website. The objective for GGOS is to set up an interoperable portal through which the data and products produced by the IAG Services can be served to the user community. We present the web applications proposed by IDS to visualize time series of geodetic observables or to get information about the tracking ground stations and the tracked satellites. We discuss the future plans for IDS to meet the recommendations of GGOS. The presentation also addresses the needs for the IAG Services to adopt common metadata thesaurus to describe data and products, and interoperability standards to share them.

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

NASA Technical Reports Server (NTRS)

1987-01-01

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

Relevance of eHealth standards for big data interoperability in radiology and beyond.

PubMed

Marcheschi, Paolo

2017-06-01

The aim of this paper is to report on the implementation of radiology and related information technology standards to feed big data repositories and so to be able to create a solid substrate on which to operate with analysis software. Digital Imaging and Communications in Medicine (DICOM) and Health Level 7 (HL7) are the major standards for radiology and medical information technology. They define formats and protocols to transmit medical images, signals, and patient data inside and outside hospital facilities. These standards can be implemented but big data expectations are stimulating a new approach, simplifying data collection and interoperability, seeking reduction of time to full implementation inside health organizations. Virtual Medical Record, DICOM Structured Reporting and HL7 Fast Healthcare Interoperability Resources (FHIR) are changing the way medical data are shared among organization and they will be the keys to big data interoperability. Until we do not find simple and comprehensive methods to store and disseminate detailed information on the patient's health we will not be able to get optimum results from the analysis of those data.

Architecture for interoperable software in biology.

PubMed

Bare, James Christopher; Baliga, Nitin S

2014-07-01

Understanding biological complexity demands a combination of high-throughput data and interdisciplinary skills. One way to bring to bear the necessary combination of data types and expertise is by encapsulating domain knowledge in software and composing that software to create a customized data analysis environment. To this end, simple flexible strategies are needed for interconnecting heterogeneous software tools and enabling data exchange between them. Drawing on our own work and that of others, we present several strategies for interoperability and their consequences, in particular, a set of simple data structures--list, matrix, network, table and tuple--that have proven sufficient to achieve a high degree of interoperability. We provide a few guidelines for the development of future software that will function as part of an interoperable community of software tools for biological data analysis and visualization. © The Author 2012. Published by Oxford University Press.

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.

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.

Data Management Coordinators Monitor STS-78 Mission at the Huntsville Operations Support Center

NASA Technical Reports Server (NTRS)

1996-01-01

Launched on June 20, 1996, the STS-78 mission's primary payload was the Life and Microgravity Spacelab (LMS), which was managed by the Marshall Space Flight Center (MSFC). During the 17 day space flight, the crew conducted a diverse slate of experiments divided into a mix of life science and microgravity investigations. In a manner very similar to future International Space Station operations, LMS researchers from the United States and their European counterparts shared resources such as crew time and equipment. Five space agencies (NASA/USA, European Space Agency/Europe (ESA), French Space Agency/France, Canadian Space Agency /Canada, and Italian Space Agency/Italy) along with research scientists from 10 countries worked together on the design, development and construction of the LMS. This photo represents Data Management Coordinators monitoring the progress of the mission at the Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at MSFC. Pictured are assistant mission scientist Dr. Dalle Kornfeld, Rick McConnel, and Ann Bathew.

Evaluation of dual multi-mission space exploration vehicle operations during simulated planetary surface exploration

NASA Astrophysics Data System (ADS)

Abercromby, Andrew F. J.; Gernhardt, Michael L.; Jadwick, Jennifer

2013-10-01

IntroductionA pair of small pressurized rovers (multi-mission space exploration vehicles, or MMSEVs) is at the center of the Global Point-of-Departure architecture for future human lunar exploration. Simultaneous operation of multiple crewed surface assets should maximize productive crew time, minimize overhead, and preserve contingency return paths. MethodsA 14-day mission simulation was conducted in the Arizona desert as part of NASA's 2010 Desert Research and Technology Studies (DRATS) field test. The simulation involved two MMSEV earth-gravity prototypes performing geological exploration under varied operational modes affecting both the extent to which the MMSEVs must maintain real-time communications with the mission control center (Continuous [CC] versus Twice-a-Day [2/D]) and their proximity to each other (Lead-and-Follow [L&F] versus Divide-and-Conquer [D&C]). As part of a minimalist lunar architecture, no communication relay satellites were assumed. Two-person crews (an astronaut and a field geologist) operated each MMSEV, day and night, throughout the entire 14-day mission, only leaving via the suit ports to perform simulated extravehicular activities. Metrics and qualitative observations enabled evaluation of the extent to which the operating modes affected productivity and scientific data quality (SDQ). Results and discussionSDQ was greater during CC mode than during 2/D mode; metrics showed a marginal increase while qualitative assessments suggested a practically significant difference. For the communications architecture evaluated, significantly more crew time (14% per day) was required to maintain communications during D&C than during L&F (5%) or 2/D (2%), increasing the time required to complete all traverse objectives. Situational awareness of the other vehicle's location, activities, and contingency return constraints were qualitatively enhanced during L&F and 2/D modes due to line-of-sight and direct MMSEV-to-MMSEV communication. Future testing

The Kepler Mission: From Concept to Operations

NASA Astrophysics Data System (ADS)

Koch, David G.

2011-01-01

From concept to launch and operations, what became the Kepler mission took a quarter of a century to create. We will review some of the steps along the way, the challenges, opportunities, strategic decisions and choices that had to be made that resulted in a mission that has the capability to detect and determine the frequencies of Earth-size planets in or near the habitable zone of solar-like stars. The process of going from starlight focused onto individual pixels to declaration of a planet detection is long and complex. Data for each star are recorded on the spacecraft and telemetered to the ground once per month. The raw pixel data are processed to produce light curves for each star. The light curves are processed to search for sequences of transits. A team of scientists examines the output to decide which meet the many validation criteria and qualify as candidates. Next an extensive series of ground-based follow-up observations are performed on the candidates now numbering in excess of 700. The objective is to eliminate false positive cases, while simultaneously improving our knowledge of the parent stars. Extensive analysis and modeling is performed on both the original photometric data and the newly acquired ground-based data to ascertain the true nature of each candidate. On the order of one-quarter to one-half of the candidates are rejected, mostly as some form of eclipsing binary. Of the remaining, some meet all the criteria and are submitted by the science team for peer-reviewed publications. Others may just require more data or may be left as undecided candidates for future research. An extended mission beyond 3.5 years will significantly improve the results from the Kepler mission, especially by covering the outer portion of the habitable zone for solar-like stars.

Building Future Transatlantic Interoperability Around a Robust NATO Response Force

DTIC Science & Technology

2012-10-01

than already traveled . However, this accrued wealth of interoperable capa- bility may be at its apogee, soon to decline as the result of two looming...and Bydgo- szcz, Poland, as well as major national training centers such as the bilateral U.S.- Romanian Joint Task Force– East at Kogalniceanu...operations. Increase U.S. and Allied Exchange Students at National and NATO military schools. Austerity measures may eventually affect the investment

A logical approach to semantic interoperability in healthcare.

PubMed

Bird, Linda; Brooks, Colleen; Cheong, Yu Chye; Tun, Nwe Ni

2011-01-01

Singapore is in the process of rolling out a number of national e-health initiatives, including the National Electronic Health Record (NEHR). A critical enabler in the journey towards semantic interoperability is a Logical Information Model (LIM) that harmonises the semantics of the information structure with the terminology. The Singapore LIM uses a combination of international standards, including ISO 13606-1 (a reference model for electronic health record communication), ISO 21090 (healthcare datatypes), and SNOMED CT (healthcare terminology). The LIM is accompanied by a logical design approach, used to generate interoperability artifacts, and incorporates mechanisms for achieving unidirectional and bidirectional semantic interoperability.

Virtual Exploitation Environment Demonstration for Atmospheric Missions

NASA Astrophysics Data System (ADS)

Natali, Stefano; Mantovani, Simone; Hirtl, Marcus; Santillan, Daniel; Triebnig, Gerhard; Fehr, Thorsten; Lopes, Cristiano

2017-04-01

environment, the "Virtual Exploitation Environment Demonstration for Atmospheric Missions" (VEEDAM) aims at maintaining, running and evolving the platform, demonstrating e.g. the possibility to perform massive processing over heterogeneous data sources. This work presents the VEEDAM concepts, provides pre-operational examples, stressing on the interoperability achievable exposing standardized data access and processing services (e.g. making accessible data and processing resources from different VREs). [1] TAMP platform landing page http://vtpip.zamg.ac.at/ [2] TAMP introductory video https://www.youtube.com/watch?v=xWiy8h1oXQY

Data Modeling Challenges of Advanced Interoperability.

PubMed

Blobel, Bernd; Oemig, Frank; Ruotsalainen, Pekka

2018-01-01

Progressive health paradigms, involving many different disciplines and combining multiple policy domains, requires advanced interoperability solutions. This results in special challenges for modeling health systems. The paper discusses classification systems for data models and enterprise business architectures and compares them with the ISO Reference Architecture. On that basis, existing definitions, specifications and standards of data models for interoperability are evaluated and their limitations are discussed. Amendments to correctly use those models and to better meet the aforementioned challenges are offered.

The ESA JUICE mission: the Science and the Science Operations

NASA Astrophysics Data System (ADS)

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

2017-04-01

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

Towards Improved Satellite-In Situ Oceanographic Data Interoperability and Associated Value Added Services at the Podaac

NASA Astrophysics Data System (ADS)

Tsontos, V. M.; Huang, T.; Holt, B.

2015-12-01

The earth science enterprise increasingly relies on the integration and synthesis of multivariate datasets from diverse observational platforms. NASA's ocean salinity missions, that include Aquarius/SAC-D and the SPURS (Salinity Processes in the Upper Ocean Regional Study) field campaign, illustrate the value of integrated observations in support of studies on ocean circulation, the water cycle, and climate. However, the inherent heterogeneity of resulting data and the disparate, distributed systems that serve them complicates their effective utilization for both earth science research and applications. Key technical interoperability challenges include adherence to metadata and data format standards that are particularly acute for in-situ data and the lack of a unified metadata model facilitating archival and integration of both satellite and oceanographic field datasets. Here we report on efforts at the PO.DAAC, NASA's physical oceanographic data center, to extend our data management and distribution support capabilities for field campaign datasets such as those from SPURS. We also discuss value-added services, based on the integration of satellite and in-situ datasets, which are under development with a particular focus on DOMS. The distributed oceanographic matchup service (DOMS) implements a portable technical infrastructure and associated web services that will be broadly accessible via the PO.DAAC for the dynamic collocation of satellite and in-situ data, hosted by distributed data providers, in support of mission cal/val, science and operational applications.

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

NASA Technical Reports Server (NTRS)

1992-01-01

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

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

NASA Technical Reports Server (NTRS)

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

2014-01-01

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

Smart Grid Interoperability Maturity Model Beta Version

DOE Office of Scientific and Technical Information (OSTI.GOV)

Widergren, Steven E.; Drummond, R.; Giroti, Tony

The GridWise Architecture Council was formed by the U.S. Department of Energy to promote and enable interoperability among the many entities that interact with the electric power system. This balanced team of industry representatives proposes principles for the development of interoperability concepts and standards. The Council provides industry guidance and tools that make it an available resource for smart grid implementations. In the spirit of advancing interoperability of an ecosystem of smart grid devices and systems, this document presents a model for evaluating the maturity of the artifacts and processes that specify the agreement of parties to collaborate across anmore » information exchange interface. You are expected to have a solid understanding of large, complex system integration concepts and experience in dealing with software component interoperation. Those without this technical background should read the Executive Summary for a description of the purpose and contents of the document. Other documents, such as checklists, guides, and whitepapers, exist for targeted purposes and audiences. Please see the www.gridwiseac.org website for more products of the Council that may be of interest to you.« less

Reuse and Interoperability of Avionics for Space Systems

NASA Technical Reports Server (NTRS)

Hodson, Robert F.

2007-01-01

The space environment presents unique challenges for avionics. Launch survivability, thermal management, radiation protection, and other factors are important for successful space designs. Many existing avionics designs use custom hardware and software to meet the requirements of space systems. Although some space vendors have moved more towards a standard product line approach to avionics, the space industry still lacks similar standards and common practices for avionics development. This lack of commonality manifests itself in limited reuse and a lack of interoperability. To address NASA s need for interoperable avionics that facilitate reuse, several hardware and software approaches are discussed. Experiences with existing space boards and the application of terrestrial standards is outlined. Enhancements and extensions to these standards are considered. A modular stack-based approach to space avionics is presented. Software and reconfigurable logic cores are considered for extending interoperability and reuse. Finally, some of the issues associated with the design of reusable interoperable avionics are discussed.

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

NASA Technical Reports Server (NTRS)

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

2008-01-01

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

The HDF Product Designer - Interoperability in the First Mile

NASA Astrophysics Data System (ADS)

Lee, H.; Jelenak, A.; Habermann, T.

2014-12-01

Interoperable data have been a long-time goal in many scientific communities. The recent growth in analysis, visualization and mash-up applications that expect data stored in a standardized manner has brought the interoperability issue to the fore. On the other hand, producing interoperable data is often regarded as a sideline task in a typical research team for which resources are not readily available. The HDF Group is developing a software tool aimed at lessening the burden of creating data in standards-compliant, interoperable HDF5 files. The tool, named HDF Product Designer, lowers the threshold needed to design such files by providing a user interface that combines the rich HDF5 feature set with applicable metadata conventions. Users can quickly devise new HDF5 files while at the same time seamlessly incorporating the latest best practices and conventions from their community. That is what the term interoperability in the first mile means: enabling generation of interoperable data in HDF5 files from the onset of their production. The tool also incorporates collaborative features, allowing team approach in the file design, as well as easy transfer of best practices as they are being developed. The current state of the tool and the plans for future development will be presented. Constructive input from interested parties is always welcome.

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.

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.

AOCS operations preparation for the BepiColombo mission to mercury

NASA Astrophysics Data System (ADS)

Steiger, C.; Altay, A.; Montagnon, E.; Companys, V.

2018-06-01

The 2018 ESA/JAXA BepiColombo mission to Mercury features a complex modular design, with two scientific Mercury orbiters and a cruise module. The spacecraft (S/C) and mission design lead to a number of challenges for the attitude and orbit control system (AOCS), including electric propulsion usage during cruise to Mercury, AOCS capability to deal with several S/C configurations, and strict attitude constraints owing to the harsh thermal environment. This paper presents the activities for AOCS operations preparation by ESA/ESOC, covering the current preparation status as well as an outlook on upcoming activities before launch.

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

NASA Image and Video Library

1970-04-18

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

Hypermedia and intelligent tutoring applications in a mission operations environment

NASA Technical Reports Server (NTRS)

Ames, Troy; Baker, Clifford

1990-01-01

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

Desert Research and Technology Studies (DRATS) 2010 science operations: Operational approaches and lessons learned for managing science during human planetary surface missions

NASA Astrophysics Data System (ADS)

Eppler, Dean; Adams, Byron; Archer, Doug; Baiden, Greg; Brown, Adrian; Carey, William; Cohen, Barbara; Condit, Chris; Evans, Cindy; Fortezzo, Corey; Garry, Brent; Graff, Trevor; Gruener, John; Heldmann, Jennifer; Hodges, Kip; Hörz, Friedrich; Hurtado, Jose; Hynek, Brian; Isaacson, Peter; Juranek, Catherine; Klaus, Kurt; Kring, David; Lanza, Nina; Lederer, Susan; Lofgren, Gary; Marinova, Margarita; May, Lisa; Meyer, Jonathan; Ming, Doug; Monteleone, Brian; Morisset, Caroline; Noble, Sarah; Rampe, Elizabeth; Rice, James; Schutt, John; Skinner, James; Tewksbury-Christle, Carolyn M.; Tewksbury, Barbara J.; Vaughan, Alicia; Yingst, Aileen; Young, Kelsey

2013-10-01

Desert Research and Technology Studies (Desert RATS) is a multi-year series of hardware and operations tests carried out annually in the high desert of Arizona on the San Francisco Volcanic Field. These activities are designed to exercise planetary surface hardware and operations in conditions where long-distance, multi-day roving is achievable, and they allow NASA to evaluate different mission concepts and approaches in an environment less costly and more forgiving than space. The results from the RATS tests allow selection of potential operational approaches to planetary surface exploration prior to making commitments to specific flight and mission hardware development. In previous RATS operations, the Science Support Room has operated largely in an advisory role, an approach that was driven by the need to provide a loose science mission framework that would underpin the engineering tests. However, the extensive nature of the traverse operations for 2010 expanded the role of the science operations and tested specific operational approaches. Science mission operations approaches from the Apollo and Mars-Phoenix missions were merged to become the baseline for this test. Six days of traverse operations were conducted during each week of the 2-week test, with three traverse days each week conducted with voice and data communications continuously available, and three traverse days conducted with only two 1-hour communications periods per day. Within this framework, the team evaluated integrated science operations management using real-time, tactical science operations to oversee daily crew activities, and strategic level evaluations of science data and daily traverse results during a post-traverse planning shift. During continuous communications, both tactical and strategic teams were employed. On days when communications were reduced to only two communications periods per day, only a strategic team was employed. The Science Operations Team found that, if

Desert Research and Technology Studies (DRATS) 2010 Science Operations: Operational Approaches and Lessons Learned for Managing Science during Human Planetary Surface Missions

NASA Technical Reports Server (NTRS)

Eppler, Dean; Adams, Byron; Archer, Doug; Baiden, Greg; Brown, Adrian; Carey, William; Cohen, Barbara; Condit, Chris; Evans, Cindy; Fortezzo, Corey;

Interoperability of Demand Response Resources Demonstration in NY

DOE Office of Scientific and Technical Information (OSTI.GOV)

Wellington, Andre

2014-03-31

The Interoperability of Demand Response Resources Demonstration in NY (Interoperability Project) was awarded to Con Edison in 2009. The objective of the project was to develop and demonstrate methodologies to enhance the ability of customer sited Demand Response resources to integrate more effectively with electric delivery companies and regional transmission organizations.

OneSAF as an In-Stride Mission Command Asset

DTIC Science & Technology

2014-06-01

implementation approach. While DARPA began with a funded project to complete the capability as a “ big bang ” approach the approach here is based on reuse and...Command (MC), Modeling and Simulation (M&S), Distributed Interactive Simulation (DIS) ABSTRACT: To provide greater interoperability and integration...within Mission Command (MC) Systems the One Semi-Automated Forces (OneSAF) entity level simulation is evolving from a tightly coupled client server

OGC and Grid Interoperability in enviroGRIDS Project

NASA Astrophysics Data System (ADS)

Gorgan, Dorian; Rodila, Denisa; Bacu, Victor; Giuliani, Gregory; Ray, Nicolas

2010-05-01

EnviroGRIDS (Black Sea Catchment Observation and Assessment System supporting Sustainable Development) [1] is a 4-years FP7 Project aiming to address the subjects of ecologically unsustainable development and inadequate resource management. The project develops a Spatial Data Infrastructure of the Black Sea Catchment region. The geospatial technologies offer very specialized functionality for Earth Science oriented applications as well as the Grid oriented technology that is able to support distributed and parallel processing. One challenge of the enviroGRIDS project is the interoperability between geospatial and Grid infrastructures by providing the basic and the extended features of the both technologies. The geospatial interoperability technology has been promoted as a way of dealing with large volumes of geospatial data in distributed environments through the development of interoperable Web service specifications proposed by the Open Geospatial Consortium (OGC), with applications spread across multiple fields but especially in Earth observation research. Due to the huge volumes of data available in the geospatial domain and the additional introduced issues (data management, secure data transfer, data distribution and data computation), the need for an infrastructure capable to manage all those problems becomes an important aspect. The Grid promotes and facilitates the secure interoperations of geospatial heterogeneous distributed data within a distributed environment, the creation and management of large distributed computational jobs and assures a security level for communication and transfer of messages based on certificates. This presentation analysis and discusses the most significant use cases for enabling the OGC Web services interoperability with the Grid environment and focuses on the description and implementation of the most promising one. In these use cases we give a special attention to issues such as: the relations between computational grid and

A Service Oriented Architecture Approach to Achieve Interoperability between Immunization Information Systems in Iran

PubMed Central

Hosseini, Masoud; Ahmadi, Maryam; Dixon, Brian E.

2014-01-01

Clinical decision support (CDS) systems can support vaccine forecasting and immunization reminders; however, immunization decision-making requires data from fragmented, independent systems. Interoperability and accurate data exchange between immunization information systems (IIS) is an essential factor to utilize Immunization CDS systems. Service oriented architecture (SOA) and Health Level 7 (HL7) are dominant standards for web-based exchange of clinical information. We implemented a system based on SOA and HL7 v3 to support immunization CDS in Iran. We evaluated system performance by exchanging 1500 immunization records for roughly 400 infants between two IISs. System turnaround time is less than a minute for synchronous operation calls and the retrieved immunization history of infants were always identical in different systems. CDS generated reports were accordant to immunization guidelines and the calculations for next visit times were accurate. Interoperability is rare or nonexistent between IIS. Since inter-state data exchange is rare in United States, this approach could be a good prototype to achieve interoperability of immunization information. PMID:25954452

Astronaut John Young during final suiting operations for Apollo 10 mission

NASA Technical Reports Server (NTRS)

1969-01-01

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

Interoperability in healthcare: major challenges in the creation of the enterprise environment

NASA Astrophysics Data System (ADS)

Lindsköld, L.; Wintell, M.; Lundberg, N.

2009-02-01

There is today a lack of interoperability in healthcare although the need for it is obvious. A new healthcare enterprise environment has been deployed for secure healthcare interoperability in the Western Region in Sweden (WRS). This paper is an empirical overview of the new enterprise environment supporting regional shared and transparent radiology domain information in the WRS. The enterprise environment compromises 17 radiology departments, 1,5 million inhabitants, using different RIS and PACS in a joint work-oriented network and additional cardiology, dentistry and clinical physiology departments. More than 160 terabytes of information are stored in the enterprise repository. Interoperability is developed according to the IHE mission, i.e. applying standards such as Digital Imaging and Communication in Medicine (DICOM) and Health Level 7 (HL7) to address specific clinical communication needs and support optimal patient care. The entire enterprise environment is implemented and used daily in WRS. The central prerequisites in the development of the enterprise environment in western region of Sweden were: 1) information harmonization, 2) reuse of standardized messages e.g. HL7 v2.x and v3.x, 3) development of a holistic information domain including both text and images, and 4) to create a continuous and dynamic update functionality. The central challenges in this project were: 1) the many different vendors acting in the region and the negotiations with them to apply communication roles/profiles such as HL7 (CDA, CCR), DICOM, and XML, 2) the question of whom owns the data, and 3) incomplete technical standards. This study concludes that to create a workflow that runs within an enterprise environment there are a number of central prerequisites and challenges that needs to be in place. This calls for negotiations on an international, national and regional level with standardization organizations, vendors, health management and health personnel.

Interoperable PKI Data Distribution in Computational Grids

DOE Office of Scientific and Technical Information (OSTI.GOV)

Pala, Massimiliano; Cholia, Shreyas; Rea, Scott A.

One of the most successful working examples of virtual organizations, computational grids need authentication mechanisms that inter-operate across domain boundaries. Public Key Infrastructures(PKIs) provide sufficient flexibility to allow resource managers to securely grant access to their systems in such distributed environments. However, as PKIs grow and services are added to enhance both security and usability, users and applications must struggle to discover available resources-particularly when the Certification Authority (CA) is alien to the relying party. This article presents how to overcome these limitations of the current grid authentication model by integrating the PKI Resource Query Protocol (PRQP) into the Gridmore » Security Infrastructure (GSI).« less

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.

The Next Generation of Interoperability Agents in Healthcare

PubMed Central

Cardoso, Luciana; Marins, Fernando; Portela, Filipe; Santos, Manuel ; Abelha, António; Machado, José

2014-01-01

Interoperability in health information systems is increasingly a requirement rather than an option. Standards and technologies, such as multi-agent systems, have proven to be powerful tools in interoperability issues. In the last few years, the authors have worked on developing the Agency for Integration, Diffusion and Archive of Medical Information (AIDA), which is an intelligent, agent-based platform to ensure interoperability in healthcare units. It is increasingly important to ensure the high availability and reliability of systems. The functions provided by the systems that treat interoperability cannot fail. This paper shows the importance of monitoring and controlling intelligent agents as a tool to anticipate problems in health information systems. The interaction between humans and agents through an interface that allows the user to create new agents easily and to monitor their activities in real time is also an important feature, as health systems evolve by adopting more features and solving new problems. A module was installed in Centro Hospitalar do Porto, increasing the functionality and the overall usability of AIDA. PMID:24840351