Search NASA⌕ Search

SEARCH · Search NASA

Results for “operational architecture”

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

A Mission Operations Architecture for the 21st Century

A new operations architecture for low cost missions is proposed, to build a framework to enable NASA to face its major challenges beond 2000. This architecture is composed of three elements: Service Based Architecture, Demand Access Automation, Distributed Science Hubs.

operations↗

A mission operations architecture for the 21st century

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.

Tai, W.↗

Integrated Operations Architecture Technology Assessment Study

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 data rate network for LEO/MEO, mission spacecraft; and, pursue developmental research for a miniaturized, high data rate optical transceiver.

Source record↗

A Subjective Assessment of Alternative Mission Architecture Operations Concepts for the Human Exploration of Mars at NASA Using a Three-Dimensional Multi-Criteria Decision Making Model

The primary driver for developing missions to send humans to other planets is to generate significant scientific return. NASA plans human planetary explorations with an acceptable level of risk consistent with other manned operations. Space exploration risks can not be completely eliminated. Therefore, an acceptable level of cost, technical, safety, schedule, and political risks and benefits must be established for exploratory missions. This study uses a three-dimensional multi-criteria decision making model to identify the risks and benefits associated with three alternative mission architecture operations concepts for the human exploration of Mars identified by the Mission Operations Directorate at Johnson Space Center. The three alternatives considered in this study include split, combo lander, and dual scenarios. The model considers the seven phases of the mission including: 1) Earth Vicinity/Departure; 2) Mars Transfer; 3) Mars Arrival; 4) Planetary Surface; 5) Mars Vicinity/Departure; 6) Earth Transfer; and 7) Earth Arrival. Analytic Hierarchy Process (AHP) and subjective probability estimation are used to captures the experts belief concerning the risks and benefits of the three alternative scenarios through a series of sequential, rational, and analytical processes.

Tavana, Madjid↗

Timeline-Based Mission Operations Architecture: An Overview

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.

Chung, Seung H.↗

Use of Dynamic Models and Operational Architecture to Solve Complex Navy Challenges

The United States Navy established 8 Maritime Operations Centers (MOC) to enhance the command and control of forces at the operational level of warfare. Each MOC is a headquarters manned by qualified joint operational-level staffs, and enabled by globally interoperable C41 systems. To assess and refine MOC staffing, equipment, and schedules, a dynamic software model was developed. The model leverages pre-existing operational process architecture, joint military task lists that define activities and their precedence relations, as well as Navy documents that specify manning and roles per activity. The software model serves as a "computational wind-tunnel" in which to test a MOC on a mission, and to refine its structure, staffing, processes, and schedules. More generally, the model supports resource allocation decisions concerning Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) at MOCs around the world. A rapid prototype effort efficiently produced this software in less than five months, using an integrated process team consisting of MOC military and civilian staff, modeling experts, and software developers. The work reported here was conducted for Commander, United States Fleet Forces Command in Norfolk, Virginia, code N5-0LW (Operational Level of War) that facilitates the identification, consolidation, and prioritization of MOC capabilities requirements, and implementation and delivery of MOC solutions.

Grande, Darby↗

Operator Workload and Task Allocation in m:N Operational Architectures of Uncrewed Aerial Systems

Uncrewed aerial systems (UAS) show promise in urban air transport, package delivery, and emergency services. UAS efficiency can be significantly improved by having fewer operators (m) manage a greater number of vehicles (N), or the m:N architecture of operation. The current study investigates how workload affects operators’ task-allocation decision-making and potential effects of two crucial human factors: trust and self-confidence. In the context of a simulated UAS package-delivery task, 10 participants with expertise in UAS operation were recruited. Each participant reported their preferred task-allocation strategy for a set of five subtasks while watching two sets of videos with different workload levels. Perceived workload, trust, and self-confidence were also measured after each video session. Overall, participants indicated a preference for automation for most of the subtasks under the delivery mission. Trust, rather than workload and self-confidence, played a significant role in experts’ decisions of task-allocation and assignment methods. Higher trust led to higher preference for automation.

workload↗

Standards-and Component-Based Mission Operations Architecture at NASA's Goddard Space Flight Center

NASA Goddard Space Flight Center (GSFC) manages many of NASA s earth and space science satellite missions. A wide variety of commercial products and GSFC-developed software components are typically integrated into a unique system configuration for each mission. Independent development of the many mission operations center systems has led to systems that are expensive to integrate, difficult to infuse with new capabilities developed for other programs, and cumbersome to maintain. This traditional approach becomes even more problematic as NASA moves towards satellite constellations, new operations concepts, and even further budgets reductions. The GSFC Mission Services Evolution Center (GMSEC) is creating a new architecture for future missions at GSFC. Instead of selecting the best-in-class components and creating a standard control center system, GMSEC is developing component interface standards so that multiple products can plug-and-play into the configuration. Missions can then select the best components based on the merits of the product and not simply based on recent integration history at NASA. The GMSEC system utilizes a publish/subscribe information bus and standard XML-based key message interfaces. Functional components can either match directly to the interface standard, or adapters can be developed to match the product's interface to the GMSEC standard with out impacting the source product. Applications Program Interfaces (API's) are being developed to isolate the underlying middleware from the applications software and to allow the middleware product to be switched if necessary. Interface Control Documents (ICDs) between each pair of communicating components is replaced by a single message/API specification document. New applications must simply match to the information bus standards and need not worry about all of the other applications in the system. For legacy software, adapters can be developed to facilitate communications between the application and the information bus. As the approach has matured, it has become apparent that it can provide innovative solutions to some of the multi-satellite challenges facing GSFC.

Smith, Danford↗

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

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.

Abrahamson, Matthew J.↗

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

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.

Technology Demonstration↗

The Mars Reconnaissance Orbiter Mission Operations: Architecture and Approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload. During the mission, the MRO operations teams are presented with two major challenges - unprecedented high data rate and data volumes, and complex science planning and resource sharing. MRO has the capability to communicate with earth at a maximum of six Megabits per second (> 50 times any previous Mars missions). With the current Deep Space Network (DSN) contact schedule of 19 eight-hour tracks per week, the baseline mission plan is for MRO to return 34 Terabits of raw science data during the two year primary science phase. Each of the science instruments has its unique requirements for global mapping, regional survey, and targeted observations. Some instruments prefer nadir-only observations, while others require off-nadir observations (especially for stereo viewing). The requirements from these Mars viewing instruments presented a significant challenge for the operations team to design the complex science planning and resource sharing/allocation process. This paper describes what MRO project is implementing to solve these challenges.

Mars Reconnaissance Orbiter (MRO)↗

NASA SEXTANT Mission Operations Architecture

The Station Explorer for X-Ray Timing and Navigation (SEXTANT) mission is a technology demonstration enhancement to the Neutron Star Interior Composition Explorer (NICER) mission, a NASA Astrophysics Explorer Mission of Opportunity to the International Space Station (ISS) that was launched in June of 2017. The NICER instrument is a precision pointing X-ray telescope that times pulsar sourced photon arrivals which the SEXTANT mission uses to perform autonomous onboard X-ray Pulsar Navigation (XNAV). By comparing the detected time of arrival of X-ray photons to a reference of expected pulsar timing models, one can infer a range and range rate measurement based on light time delay. Since both timing and orientation information comes from a celestial source, this technology could provide a GPS-like navigation capability available throughout our Solar System and beyond. Applications that XNAV can support include outer planet and interstellar missions, manned missions, libration orbit missions, and current infrastructure such as the Deep Space Network (DSN). The SEXTANT team successfully completed a first demonstration of in-space and autonomous XNAV in November 2017. NICER and SEXTANT have separate teams, with NICER being the primary team with its own science objectives. Operational modes for both missions must have concurrent and independent components as well as an integrated ground system. This paper describes on the operational infrastructure and successful operations for performing X-ray Pulsar Navigation with the Station Explorer for X-ray Timing and Navigation Technology (SEXTANT) demonstration. This paper first details the infrastructure implemented, then the concept of operations, and finally the operations for the SEXTANT demonstration and lessons learned.

Ground Systems↗

NASA Station Explorer for X-Ray Timing and Navigation Technology (SEXTANT) Mission Operations Architecture

"The Station Explorer for X-Ray Timing and Navigation (SEXTANT) mission is a technology demonstrationenhancement to the Neutron Star Interior Composition Explorer (NICER) mission, a NASA AstrophysicsExplorer Mission of Opportunity to the International Space Station (ISS) that was launched in June of 2017.The NICER instrument is a precision pointing X-ray telescope that provides measurements of neutron stars,which the SEXTANT mission uses to perform autonomous onboard X-ray Pulsar Navigation (XNAV) by usingmilli-second pulsars (MSPs), a category of neutron stars, as timing sources for navigation. By comparing thedetected time of arrival of X-ray photons to a reference of expected pulsar lightcurve timing models, one caninfer a range and range rate measurement based on light time delay. Since both timing and orientationinformation comes from a celestial source, this technology could provide a GPS-like navigation capabilityavailable throughout our Solar System and beyond. Applications that XNAV can support include outer planetand interstellar missions, manned missions, libration orbit missions, and current infrastructure such as the DeepSpace Network (DSN). The SEXTANT team successfully completed a rst demonstration of in-space andautonomous XNAV in November 2017. NICER and SEXTANT have separate teams, with NICER being theprimary team with its own science objectives. Operational modes for both missions must have concurrent andindependent components as well as an integrated ground system. Within this joint mission pro le, SEXTANToperations requires an infrastructure and cadence that is exible to handle concurrent science operations fromthe NICER team, independent autonomous navigation demonstrations, and events within the extensive ISSoperations environment. This paper rst details the infrastructure implemented and its concept of operations.It then describes the operations for the SEXTANT demonstration and lessons learned."

Yu, Wayne H.↗

The Mars Reconnaissance Orbiter mission operations: architecture and approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload.

MRO↗

Modeling Operations Costs for Human Exploration Architectures

Operations and support (O&S) costs for human spaceflight have not received the same attention in the cost estimating community as have development costs. This is unfortunate as O&S costs typically comprise a majority of life-cycle costs (LCC) in such programs as the International Space Station (ISS) and the now-cancelled Constellation Program. Recognizing this, the Constellation Program and NASA HQs supported the development of an O&S cost model specifically for human spaceflight. This model, known as the Exploration Architectures Operations Cost Model (ExAOCM), provided the operations cost estimates for a variety of alternative human missions to the moon, Mars, and Near-Earth Objects (NEOs) in architectural studies. ExAOCM is philosophically based on the DoD Architecture Framework (DoDAF) concepts of operational nodes, systems, operational functions, and milestones. This paper presents some of the historical background surrounding the development of the model, and discusses the underlying structure, its unusual user interface, and lastly, previous examples of its use in the aforementioned architectural studies.

cost estimating↗