Search NASA⌕ Search

SEARCH · Search NASA

Results for “Process Mission Teams”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS2004

The PMDP Roadmap

NASA's complex and highly technical missions rely on effective project teams and managers. Since 1993, through its Project Management Development Process (PMDP), the Academy of Program and Project Leadership (APPL) has offered direction to the Agency's project practitioners as they advance in their careers. PMDP helps identify and sequence professional experiences, courses, and other project-based learning experiences that support individual career goals and center activities by outlining competencies at four levels of development. The result is that PMDP provides NASA project practitioners with a road map to the knowledge and competencies appropriate for their job and the jobs to which they aspire. Plus, new this year, APPL has rolled out its electronic Project Management Development Process (ePMDP) tool, a learning management system that includes a dynamic presentation of the PMDP levels, competency areas, competency organizational structures, Individual Development Plans (IDP), and online PMDP enrollment. APPL's website, www.appl.nasa.gov, provides access to ePMDP as well as other online resources for NASA practitioners enrolled in the Project Management Development Process.

Source record↗
NASA NTRS2018

Overview of NASA Behavioral Health and Performance Standard Measures

NASA’s Human Research Program (HRP) is developing a set of “Standard Measures” for use in spaceflight and spaceflight analog environments to monitor the risks of long-duration missions on human health and performance, including behavioral health, individual and team performance, and social processes. Based on measures selected, developed, and tested under the NASA-funded Behavioral Core Measures project (PI: D.F. Dinges) as well as other projects from NASA’s Human Factors & Behavioral Performance research portfolio, NASA’s Behavioral Health & Performance (BHP) Laboratory is further evaluating the operational feasibility, acceptability, and validity of a multidisciplinary suite of objective, subjective, behavioral, and biological measures for monitoring monitor behavioral health, individual and team performance, and social processes over time. The inaugural generation of the NASA Behavioral Health & Performance (BHP) Standard Measures includes a neurocognitive test battery, actigraphy, physical proximity sensors, cardiovascular monitors, and subjective self-reports of mood, depression, and various team and social processes and performance outcomes.

Roma, P. G.↗
NASA NTRS2019

Planetary Boundary Layer Height from AIRS and MERRA-2 Products at NASA GES DISC, and Insights from Data Intercomparison

The Atmospheric Infrared Sounder (AIRS) is the hyperspectral infrared sounder onboard NASA's Aqua satellite, launched in 2002. The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC), in collaboration with NASA Sounder Team at JPL, provides processing, archiving, and distribution services for NASA sounders: the Aqua AIRS mission and the subsequent Suomi-National Polar-orbiting Partnership Cross-track Infrared Sounder (CrIS) mission. The Planetary Boundary Layer (PBL) Height is a new variable added in the AIRS Version 6 support product. It is derived based on gradients of the retrieved atmospheric thermodynamic profile, and gives the pressure at the top of PBL over the ocean. The GES DISC also provides services for the second Modern-Era Retrospective analysis for Research and Applications (MERRA-2) product generated by the Goddard Earth Observing System Model, Version 5 (GEOS-5) data assimilation system. The monthly PBL Height variable has been available in the Giovanni system, which is a Web-based application developed by the GES DISC providing a simple and intuitive way to visualize, analyze, and access vast amounts of Earth science remote sensing data. In this work, we will present the monthly PBL Height data from AIRS and MERRA-2 and the services to support data intercomparison, such as access, plotting, subsetting, re-gridding, and generation of a multi-year monthly mean. We will also show intercomparison results, and evaluate whether (over the ocean) AIRS can observe PBL features similar to the reanalysis product at monthly and longer-term scales.

AIRS↗
NASA NTRS2016

MarCO: Interplanetary Mission Development on a CubeSat Scale

Shortly after JPL’s Interior Exploration using Seismic Investigations, Geodesy and Heat Transport (InSight) mission launches, separates, and commences its cruise phase, two CubeSats will deploy from the launch vehicle’s upper stage and begin independent flight to Mars (Fig. 1). During InSight’s entry, descent, and landing (EDL) sequence, these twin Mars Cube One (MarCO) spacecraft will fly 3,500 km above the Martian surface, recording and relaying InSight UHF radio data to the Deep Space Network (DSN) on Earth1. MarCO is a twin CubeSat mission developed by the NASA Jet Propulsion Laboratory (JPL) to accompany the InSight (Interior Exploration using Seismic Investigations, Geodesy and Heat Transport) Mars mission lander. MarCO's primary mission objective is to launch with InSight and independently fly to Mars to serve as a communications relay during InSight's entry, descent, and landing (EDL) phase. MarCO represents a new type of deep space mission: CubeSats at Mars. Building on the development of JPL's first interplanetary CubeSat project, the Interplanetary Nano-Spacecraft Pathfinder in Relevant Environment (INSPIRE), MarCO further refined the approach to hardware, software, and ground architecture development to solve the challenges of quickly building low-budget spacecraft to fly to Mars. The greatest constraint, beyond others typical of CubeSat missions, was time. The duration between MarCO's conception to completion of spacecraft assembly was less than two years - an unprecedented schedule for any planetary mission to date. Through necessity, MarCO has built on previous experience, procedures, systems, and development methodologies, defining a new niche for supporting larger primary missions. The MarCO spacecraft are poised to write a new chapter in deep space exploration. Originally slated to launch and reach Mars in 2016, the InSight mission schedule subsequently slipped to 2018. During the original landing of InSight, Earth would not be in view, and no orbiter around Mars would have been in position to both receive UHF EDL data and simultaneously relay it back to Earth. It was from this obstacle that MarCO was conceived. Regardless of any changes to InSight’s 2018 EDL configuration geometry, MarCO is still expected to fly and serve in the same capacity as originally designed: the first CubeSat mission to Mars. CubeSats have historically been firmly in the domain of universities and small companies. As first conceived, they served as a platform upon which to teach all aspects of the space mission lifecycle. JPL took on this mission type with Interplanetary Nano-Spacecraft Pathfinder in Relevant Environment2 (INSPIRE), moving the concept into a new domain: deep space. Building from the INSPIRE platform and lessons learned, MarCO addressed new challenges in the domain of planetary missions: independent interplanetary flight and navigation, integration with a large-scale mission, long-distance and long-delay communication, short development time, and a small development team. Of these, the greatest constraint was schedule: only 18 months passed from conception of mission concept until delivery of fully assembled and tested flight hardware. Careful selection of mission team, along with extensive use of off-the-shelf equipment, and streamlining automated processes, was essential. This achievement represents the next step in the evolution of CubeSats beyond low-Earth orbit.

Werne, Thomas↗
NASA NTRS2020

Estimate Early and Estimate Often: How Your Concurrent Engineering Design Team Can Bootstrap Your Organizations Programmatic Capabilities

What do you do when it is necessary to generate reasonable cost estimates at the earliest Concept Maturity Levels and you have never flown any similar missions before? This paper describes the current and future Team X and A-Team cost processes and methods, how they are being used to expand our data frontiers, cost modelling capabilities and how this enables the ability to estimate early and estimate often.

Hihn, Jairus↗
NASA NTRS2016

CASIS Fact Sheet: Hardware and Facilities

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS

Solomon, Michael R.↗
NASA NTRS2000

Signal Processing and Fault Detection with Application to CH-46 Helicopter Data

Central to Qualtech Systems' mission is its testability and maintenance software (TEAMS) and derivatives. Many systems comprise components equipped with self-testing capability; but, if the system is complex (and involves feedback and if the self-testing itself may occasionally be faulty) tracing faults to a single or multiple causes is difficult. However, even for systems involving many thousands of components the PC-based TEAMS provides essentially real-time system-state diagnosis. Until recently TEAMS operation was passive: its diagnoses were based on whatever data sensors could provide. Now, however, a signal-processing (SP) "frontend" matched to inference needs is available. Many standard signal processing primitives, such as filtering, spectrum analysis and multi-resolution decomposition are available; the SP toolbox is also equipped with a (supervised) classification capability based on a number of decision-making paradigms. This paper is about the SP toolbox. We show its capabilities, and demonstrate its performance on the CH-46 "Westland" data set.

Wen, Fang↗
NASA NTRSDate not supplied

Navigation Performance of the BioSentinel Deep Space CubeSat Mission

The BioSentinel mission was recently launched aboard the SLS launch vehicle (LV) as part of the Artemis- 1 campaign. The BioSentinel navigation team successfully tracked and guided the spacecraft through a lunar gravity assist to its destination Earth-trailing heliocentric orbit. This 6U CubeSat carries live yeast cells to analyze the effects of radiation at large distances from Earth, becoming the first biological payload in Deep Space. Prelaunch activities included mission design updates, orbit determination rehearsals and the development of a tracking schedule in coordination with the Artemis-1 payload office and the Deep Space Network (DSN). An important influence on the trajectories of Artemis I secondaries was the uncertainty associated with deployment from the Interim Cryogenic Propulsion System (ICPS), the upper stage of the SLS LV. The ICPS was rotating at a rate of 1 rpm; there was also an uncertainty in the spin axis attitude, which translated into an unknown clock angle of deployment. The variability in this angle and magnitude of deployment implied the existence of a non-negligible risk of a lunar impact, which was evaluated for various potential launch dates. We present the results of Monte Carlo analyses and compute the pertinent maneuvers to avoid it. In addition, we present a comparison with the actual deployment once the mission launched by reconstructing our trajectory with tracking data. On November 16th 2022 BioSentinel successfully deployed from ICPS and the navigation team started to receive 2-way Doppler and Sequential Ranging data from the DSN. We processed early data to try to obtain a first ephemeris using Initial Orbit Determination (IOD) methods such as the least squares. Soon after deployment, the spacecraft was tumbling and entered safe mode, creating a period where the tracking data were sparse. The mission team recovered the spacecraft and after four tracking passes, we solved for a first ephemeris that was sent to the DSN for better tracking of the spacecraft. After propagating this first ephemeris solution, we determined that we avoided impact with a margin of a few hundred km from the lunar surface. More tracking data over the next few days (from DSN as well as ESA antennas) allowed for a more refined orbit solution predicting a periselene altitude of 406 km and a lunar eclipse lasting 36.5 minutes. Therefore, BioSentinel operators aborted any correction maneuvers. This periselene altitude also gave us the necessary energy to achieve a heliocentric orbit. The next challenge was due to the necessary adjustments in our orbit determination method due to the large energy boost resulting from the lunar flyby. After a series of tracking passes we were able to get a nominal solution that resulted into a stable trajectory. This paper discusses in detail the navigation performance using the X-band IRIS transponder, as well as the challenges and lessons learned prior to and during this deep space, CubeSat mission.

Andres Dono Perez↗
NASA NTRSDate not supplied

Planetary Protection Lunar Policy: A Case Study in Balancing COSPAR Guidelines, Scientific Consensus, NASA Policy, and Mission Implementation

With the increase of missions to the Earth’s Moon over the next decade, NASA initiated an assessment and review of the policy and protection of Earth’s Moon to enable scientific exploration. The assessment involved gathering scientific consensus regarding the Earth’s Moon and proposed mission operations considering an understanding of the desired science needs for the Moon. This process involved seeking advice from the National Academies of Science, Engineering, and Medicine’s (NASEM) Committee on Planetary Protection, engagement with the Committee on Space Research (COSPAR) Planetary Protection Panel (PPP), and consultation within NASA. To begin this process, NASA issued a NASA Interim Directive (NID) 8715.128 entitled, “Planetary Protection Categorization for Robotic and Crewed Missions to the Earth’s Moon” in July of 2019. This NID defined sensitive regions (e.g., permanently shadowed regions) on the Moon and required reporting on missions to these sensitive areas. Meanwhile, a NASEM study on the impact of human activities on lunar polar volatiles and the scientific value of protecting the surface and subsurface regions of the Earth’s Moon from organic and biological contamination was initiated. This resulted in a NASEM report entitled, “Planetary Protection for the Study of Lunar Volatiles” which enabled further dialogue within NASA and with COSPAR. COSPAR PPP then leveraged this scientific consensus along with multi-agency input to develop an updated COSPAR Policy on Planetary Protection in June 2021 resulting in updated mission categorizations for Earth’s Moon (existing Category II for orbiters, and new categories IIa and IIb for landed missions). NASA then updated its current planetary protection policy to apply directly to NASA and NASA partnered missions in NASA Procedural Requirements (NPR) 8715.24 entitled, “Planetary Protection Provisions for Robotic Extraterrestrial Missions”. Along with the policy update NASA’s Office of Planetary Protection has worked with mission and programmatic teams to streamline reporting requirements to a simplified checkbox and fill-in-the-blank type of template. Throughout the abovementioned process, open and transparent communication between the policy makers and implementers was essential to ensure a balance with the updated policy, scientific intent, and practicality for each mission to be responsive and achieve mission success, including Artemis I and each of its secondary payloads, Gateway, CAPSTONE and Lunar Trailblazer.

James Benardini↗
NASA NTRS2006

Cassini distributed instrument operations – what we’ve learned since Saturn orbit insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained realworld experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the “tour”) and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Woncik, Pam↗
NASA NTRS2006

Cassini Distributed Instrument Operations: What We've Learned Since Saturn Orbit Insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained real-world experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the 'tour') and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Cassini↗
NASA NTRS2002

Managing Risk in Safety Critical Operations - Lessons Learned from Space Operations

The Mission Control Center (MCC) at Johnson Space Center (JSC) has a rich legacy of supporting Human Space Flight operations throughout the Apollo, Shuttle and International Space Station eras. Through the evolution of ground operations and the Mission Control Center facility, NASA has gained a wealth of experience of what it takes to manage the risk in Safety Critical Operations, especially when human life is at risk. The focus of the presentation will be on the processes (training, operational rigor, team dynamics) that enable the JSC/MCC team to be so successful. The presentation will also share the evolution of the Mission Control Center architecture and how the evolution was introduced while managing the risk to the programs supported by the team. The details of the MCC architecture (e.g., the specific software, hardware or tools used in the facility) will not be shared at the conference since it would not give any additional insight as to how risk is managed in Space Operations.

Gonzalez, Steven A.↗
NASA NTRSDate not supplied

OSIRIS-REx Curation: The First Year with Bennu Samples on Earth

The OSIRIS-REx (Origins, Spectral Interpretation, Resource Identification, and Security – Regolith Explorer) sample return capsule landed on the Utah Test and Training Range (UTTR) on September 24, 2023. Preparations for the curation of the sample from asteroid Bennu inside of this capsule spanned more than a decade. On the morning of landing, the sample return capsule was brought to a temporary cleanroom at UTTR for initial de-integration and connection of the sample canister to a nitrogen gas purge to protect the sample from modification by the terrestrial atmosphere. In the week following landing, the sample canister was flown to Houston while on nitrogen purge, transferred to a nitrogen atmosphere glovebox at NASA Johnson Space Center in which the canister lid was removed revealing small amounts of sample on the inside of the canister lid and avionics deck, some of this sample was allocated rapidly to the mission sample analysis team as “quick look” samples. Next, the Touch-and-Go sample acquisition mechanism (TAGSAM) head was disassembled inside of a specially designed glovebox. A challenge arose during one of the last stages of disassembly when two fasteners resisted being loosened. The curation team was able to remove 70.3 grams of asteroid sample from the TAGSAM head with those fasteners in-place and began initial sample processing which supported long-term curation of hermetically sealed and frozen samples, transfer of some samples to remote storage, and allocation of aggregate samples to the mission sample analysis team. Meanwhile, curation engineers developed a tool to remove the stubborn fasteners without contaminating the remaining sample, enabling the remaining bulk sample to be transferred to long-term storage trays in January 2024. With this second part of the bulk sample, the returned bulk asteroid sample reached 121.6 grams. During disassembly and prior to sealing the bulk sample trays into long-term storage containers, archival photographs were collected. Select particles are gradually being XCT scanned while inside of containers that hold a nitrogen atmosphere. The initial OSIRIS-REx sample catalog was released in spring 2024 with an update in fall 2024. The curation team will be busy working to allocate samples to scientists around the world for the foreseeable future.

Curation↗
NASA NTRS2018

The InSAR Scientific Computing Environment 3.0: A Flexible Framework for NISAR Operational and User-Led Science Processing

The InSAR Scientific Computing Environment (ISCE) was first developed under the NASA Advanced Information Systems Technology as a flexible, extensible object-oriented framework for Interferometric Synthetic Aperture Radar (InSAR) processing. The ISCE framework uses Python 3 at the workflow level, controlling modules of compiled code for functional processing, and managing inputs, outputs, and other flow control services. The currently released version, called ISCE 2.1, is distributed to the research community through the Western North America InSAR Consortium under a research license. The ISCE team is working on the next generation of the code in order to prepare for the NASAISRO SAR (NISAR) mission operational processing. Innovations in this code include augmentation or conversion of the custom Python framework elements in ISCE with the Pyre framework, new workflows for interferometric and polarimetric stack processing, a more intuitive and graphically based user interface, and flow control for hybrid computing environments including CPU/GPU clusters, logging and error tracking facilities, and new more efficient computational modules that exploit graphical processor units (GPUs) when available. The ISCE 3.0 framework is designed to work in an operational environment as well as on a single user’s laptop or compute cluster, with services to discover capabilities and scale computations accordingly.

Buckley, Sean M.↗
NASA NTRS2013

Exploring Mission Concepts with the JPL Innovation Foundry A-Team

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts called the A-Team. The A-Team combines innovative collaborative methods with subject matter expertise and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an A-Team study. Methods are grouped by Concept Maturity Level (CML), from 1 through 3, including idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for each CML are presented, and the key team roles are described from two points of view: innovative methods and technical expertise. A-Team roles for providing innovative methods include the facilitator, study lead, and assistant study lead. A-Team roles for providing technical expertise include the architect, lead systems engineer, and integration engineer. In addition to these key roles, each A-Team study is uniquely staffed to match the study topic and scope including subject matter experts, scientists, technologists, flight and instrument systems engineers, and program managers as needed. Advanced analysis and collaborative engineering tools (e.g. cost, science traceability, mission design, knowledge capture, study and analysis support infrastructure) are also under development for use in A-Team studies and will be discussed briefly. The A-Team facilities provide a constructive environment for innovative ideas from all aspects of mission formulation to eliminate isolated studies and come together early in the development cycle when they can provide the biggest impact. This paper provides an overview of the A-Team, its study processes, roles, methods, tools and facilities.

Team Eureka↗
NASA NTRS2002

Science Planning for Multi-Spacecraft Coordinated Observations

Fulfilling the promise of an era of great observatories, NASA now has more than three space-based astronomical telescopes operating in different wavebands. This situation provides astronomers with a unique opportunity to simultaneously observe with multiple observatories. Yet scheduling multiple observatories simultaneously is highly inefficient when compared to single observatory observations. Thus, programs using multiple observatories are limited not due to scientific restrictions, but due to operational inefficiencies. Each year, a number of proposals are accepted by a space-based observatory for conduction of astronomical observations and gathering of science data for the study of galactic events. Since each space-based observatory uses a set of instruments designed to operate in specific energy regions, most such studies are conducted by submitting observation proposals to multiple observatories, with requests to coordinate among themselves. To assure that the proposed observations can be scheduled, each observatory's staff has to check that the observations are valid and meet all the constraints for their own observatory; in addition, they have to verify that the observations satisfy the constraints of the other observatories. Thus, coordinated observations require painstaking manual collaboration among the observatory staff at each observatory. In order to exploit new paradigms for observatory operation, the Goddard Space Flight Center's Advanced Architectures and Automation Branch has developed a prototype tool called the Visual Observation Layout Tool (VOLT). The main objective of VOLT is to provide a visual tool to automate the science planning of coordinated observations for multiple spacecraft, as well as to increase the scheduling probability of observations. However, VOLT is also useful for single observatory planning to optimize observatory control. Three space-based missions are interested in using VOLT (the Hubble Space Telescope, the Chandra X-Ray Observatory, and the Far Ultraviolet Spectroscopic Explorer). The VOLT team members have collaborated with these missions to gather requirements and obtain feedback on their mission planning processes. VOLT has been developed as a cross-platform Java client application for use by scientists and observatory science planning staff to visualize scheduling options and constraints. It also supports a lightweight graphical user interface for remote viewing via a Web front end. Additionally, it uniquely supports the ability to interact with multiple, diverse scheduling packages in order to determine windows of opportunity for observations and visually portray the constraints of each observation request. VOLT enables science data capture scenarios which are currently either impossible, or which require extensive time and manpower to coordinate amongst multiple observatories. it supports early detection of planning conflicts by generating coordinated solutions based on observatory schedulability and constraints. The project development approach has included frequent prototype demonstrations to our interested missions to obtain feedback after each release of the software. We will present an overview of our lessons learned in infusing the VOLT tool into the operations of the missions we have collaborated with and a brief demonstration of the software.

Maks, Lori↗
NASA NTRS2010

MaROS Strategic Relay Planning and Coordination Interfaces

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

Allard, Daniel A.↗