Search NASA⌕ Search

SEARCH · Search NASA

Results for “operations concept”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Preparing the DSN operations concepts

Operations concepts are prepared to support a specific application and can, therefore, be classified accordingly. Studies of NASA and military operations concepts suggest three major types: data services, customer services, and systems oriented. Data services concepts concentrate on data types (e.g., telemetry and command) and how these data are processed and delivered to the user. Such concepts are normally used by data-processing centers to describe data-coding schemes and data formats. Customer services concepts concentrate on the customers' requirements and describe how these requirements are met using the systems available to the operation. Project centers use such concepts to describe the various types of data as they flow from the source (e.g., a spacecraft) to the end user (i.e., the customer). Systems oriented concepts concentrate on the use of systems for processing and delivering customer data. This paper examines the latter type and the 'concepts' that are inherent within them.

Salazar, A. J.↗
NASA NTRS1989

Space Station Initial Operational Concept (IOC) operations and safety view - Automation and robotics for Space Station

The automation and robotics requirements for the Space Station Initial Operational Concept (IOC) are discussed. The amount of tasks to be performed by an eight-person crew, the need for an automated or directed fault analysis capability, and ground support requirements are considered. Issues important in determining the role of automation for the IOC are listed.

Bates, William V., Jr.↗
NASA NTRS2004

Small Aircraft Transportation System, Higher Volume Operations Concept: Normal Operations

This document defines the Small Aircraft Transportation System (SATS), Higher Volume Operations (HVO) concept for normal conditions. In this concept, a block of airspace would be established around designated non-towered, non-radar airports during periods of poor weather. Within this new airspace, pilots would take responsibility for separation assurance between their aircraft and other similarly equipped aircraft. Using onboard equipment and procedures, they would then approach and land at the airport. Departures would be handled in a similar fashion. The details for this operational concept are provided in this document.

Abbott, Terence S.↗
NASA NTRS2010

CxP Medical Operations Concept of Operations (CONOPS)

This slide presentation reviews the planned medical operations for manned missions to the Moon and Mars as outlined in the Constellation program. Many of the issues involving the medical operations are examined.

Scheuring, Richard A.↗
NASA NTRS1991

A method for selecting an operations concept to achieve successful mission operations

A procedure is presented for mapping operations concepts into design alternatives for a data system to be used in a generic ground based control center. A set of descriptive categories are developed to characterize the operational environment that relate to responsiveness, automation, and commitment. The operations concept is then developed according to a hierarchical decomposition of a mission statement into lower-level tasks, and the interpretation of the model's output is addressed. The method permits the description of operations concepts in terms of concept categories and ranges of alternatives between those categories. The descriptive framework can provide a mechanism for analyzing competing operations concepts.

Hornstein, Rhoda S.↗
NASA NTRS1977

Concept Verification Test - Evaluation of Spacelab/Payload operation concepts

The Concept Verification Test (CVT) procedure is used to study Spacelab operational concepts by conducting mission simulations in a General Purpose Laboratory (GPL) which represents a possible design of Spacelab. In conjunction with the laboratory a Mission Development Simulator, a Data Management System Simulator, a Spacelab Simulator, and Shuttle Interface Simulator have been designed. (The Spacelab Simulator is more functionally and physically representative of the Spacelab than the GPL.) Four simulations of Spacelab mission experimentation were performed, two involving several scientific disciplines, one involving life sciences, and the last involving material sciences. The purpose of the CVT project is to support the pre-design and development of payload carriers and payloads, and to coordinate hardware, software, and operational concepts of different developers and users.

Mcbrayer, R. O.↗
NASA NTRS2005

Small Aircraft Transportation System, Higher Volume Operations Concept: Off-Nominal Operations

This document expands the Small Aircraft Transportation System, (SATS) Higher Volume Operations (HVO) concept to include off-nominal conditions. The general philosophy underlying the HVO concept is the establishment of a newly defined area of flight operations called a Self-Controlled Area (SCA). During periods of poor weather, a block of airspace would be established around designated non-towered, non-radar airports. Aircraft flying enroute to a SATS airport would be on a standard instrument flight rules flight clearance with Air Traffic Control providing separation services. Within the SCA, pilots would take responsibility for separation assurance between their aircraft and other similarly equipped aircraft. Previous work developed the procedures for normal HVO operations. This document provides details for off-nominal and emergency procedures for situations that could be expected to occur in a future SCA.

Abbott, Terence S.↗
NASA NTRS2010

H-II Transfer Vehicle (HTV) and the Operations Concept for Extravehicular Activity (EVA) Hardware

With the retirement of the Space Shuttle fleet imminent in 2011, a new concept of operations will become reality to meet the transportation challenges of the International Space Station (ISS). The planning associated with the retirement of the Space Shuttle has been underway since the announcement in 2004. Since then, several companies and government entities have had to look for innovative low-cost commercial orbital transportation systems to continue to achieve the objectives of ISS delivery requirements. Several options have been assessed and appear ready to meet the large and demanding delivery requirements of the ISS. Options that have been identified that can facilitate the challenge include the Russian Federal Space Agency's Soyuz and Progress spacecraft, European Space Agency's Automated Transfer Vehicle (ATV), the Japan Aerospace Exploration Agency's (JAXA's) H-II Transfer Vehicle (HTV) and the Boeing Delta IV Heavy (DIV-H). The newest of these options is the JAXA's HTV. This paper focuses on the HTV, mission architecture and operations concept for Extra-Vehicular Activities (EVA) hardware, the associated launch system, and details of the launch operations approach.

Chullen, Cinda↗
NASA NTRS1996

Space Mission Operations Concept

Developing a mission operations concept for a space mission is a system engineering process which involves multiple disciplines, working together to describe, in terms of the operators and the users (recipients of the data from the mission), the operational attributes of the flight and ground elements of the mission. A space mission operations concept emphasizes the way the mission is operated/used.

space mission operations mission concepts systems ↗
NASA NTRS1991

Space Station Freedom baseline operations concept

The Baseline Operations Concept is designed to support the multiflight-multistage assembly sequence and post-Permanent Manned Configuration (PMC) era for the Space Station Freedom (SSF). Initial implementation of procedures and systems are consistent with experience gained during the operation of the Shuttle and Spacelab.

Paules, Granville↗
NASA NTRS2005

Hybrid Verification of an Air Traffic Operational Concept

A concept of operations for air traffic management consists of a set of flight rules and procedures aimed to keep aircraft safely separated. This paper reports on the formal verification of separation properties of the NASA's Small Aircraft Transportation System, Higher Volume Operations (SATS HVO) concept for non-towered, non-radar airports. Based on a geometric description of the SATS HVO air space, we derive analytical formulas to compute spacing requirements on nominal approaches. Then, we model the operational concept by a hybrid non-deterministic asynchronous state transition system. Using an explicit state exploration technique, we show that the spacing requirements are always satisfied on nominal approaches. All the mathematical development presented in this paper has been formally verified in the Prototype Verification System (PVS). Keywords. Formal verification, hybrid systems, air traffic management, theorem proving

Munoz, Cesar A.↗
NASA NTRS1994

EDOS operations concept and development approach

The Earth Observing System (EOS) Data and Operations System (EDOS) is being developed by the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) for the capture, level zero processing, distribution, and backup archiving of high speed telemetry data received from EOS spacecraft. All data received will conform to the Consultative Committee for Space Data Standards (CCSDS) recommendations. The major EDOS goals are to: (1) minimize EOS program costs to implement and operate EDOS; (2) respond effectively to EOS growth requirements; and (3) maintain compatibility with existing and enhanced versions of NASA institutional systems required to support EOS spacecraft. In order to meet these goals, the following objectives have been defined for EDOS: (1) standardize EDOS interfaces to maximize utility for future requirements; (2) emphasize life-cycle cost (LCC) considerations (rather than procurement costs) in making design decisions and meeting reliability, maintainability, availability (RMA) and upgradability requirements; (3) implement data-driven operations to the maximum extent possible to minimize staffing requirements and to maximize system responsiveness; (4) provide a system capable of simultaneously supporting multiple spacecraft, each in different phases of their life-cycles; (5) provide for technology insertion features to accommodate growth and future LCC reductions during the operations phase; and (6) provide a system that is sufficiently robust to accommodate incremental performance upgrades while supporting operations. Operations concept working group meetings were facilitated to help develop the EDOS operations concept. This provided a cohesive concept that met with approval of responsible personnel from the start. This approach not only speeded up the development process by reducing review cycles, it also provided a medium for generating good ideas that were immediately molded into feasible concepts. The operations concept was then used as a basis for the EDOS specification. When it was felt that concept elements did not support detailed requirements, the facilitator process was used to resolve discrepancies or to add new concept elements to support the specification. This method provided an ongoing revisal of the operations concept and prevented large revisions at the end of the requirement analysis phase of system development.

Knoble, G.↗
NASA NTRS2010

Operations Concepts for Deep-Space Missions: Challenges and Opportunities

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

McCann, Robert S.↗
NASA NTRS2020

Urban Air Mobility Operational Concept (OpsCon) Passenger-Carrying Operations

Urban Air Mobility (UAM) is the name chosen for the concept of using the airspace over urban areas to satisfy the public imperative for fast and efficient transportation within growing metropolitan areas. This Operational Concept (OpsCon) describes a community vision of the projected evolution of urban air service with vehicles capable of carrying one or more passengers.

Urban Air Mobility (UAM)↗
NASA NTRS2017

Prototype Tool and Focus Group Evaluation for an Advanced Trajectory-Based Operations Concept

Trajectory-based operations (TBO) is a key concept in the Next Generation Air Transportation System transformation of the National Airspace System (NAS) that will increase the predictability and stability of traffic flows, support a common operational picture through the use of digital data sharing, facilitate more effective collaborative decision making between airspace users and air navigation service providers, and enable increased levels of integrated automation across the NAS. NASA has been developing trajectory-based systems to improve the efficiency of the NAS during specific phases of flight and is now also exploring Advanced 4-Dimensional Trajectory (4DT) operational concepts that will integrate these technologies and incorporate new technology where needed to create both automation and procedures to support gate-to-gate TBO. A TBO Prototype simulation toolkit has been developed that demonstrates initial functionality of an Advanced 4DT TBO concept. Pilot and controller subject matter experts (SMEs) were brought to the Air Traffic Operations Laboratory at NASA Langley Research Center for discussions on an Advanced 4DT operational concept and were provided an interactive demonstration of the TBO Prototype using four example scenarios. The SMEs provided feedback on potential operational, technological, and procedural opportunities and concerns. This paper describes an Advanced 4DT operational concept, the TBO Prototype, the demonstration scenarios and methods used, and the feedback obtained from the pilot and controller SMEs in this focus group activity.

Guerreiro, Nelson M.↗
NASA NTRS2011

Component-Level Electronic-Assembly Repair (CLEAR) Operational Concept

This Component-Level Electronic-Assembly Repair (CLEAR) Operational Concept document was developed as a first step in developing the Component-Level Electronic-Assembly Repair (CLEAR) System Architecture (NASA/TM-2011-216956). The CLEAR operational concept defines how the system will be used by the Constellation Program and what needs it meets. The document creates scenarios for major elements of the CLEAR architecture. These scenarios are generic enough to apply to near-Earth, Moon, and Mars missions. The CLEAR operational concept involves basic assumptions about the overall program architecture and interactions with the CLEAR system architecture. The assumptions include spacecraft and operational constraints for near-Earth orbit, Moon, and Mars missions. This document addresses an incremental development strategy where capabilities evolve over time, but it is structured to prevent obsolescence. The approach minimizes flight hardware by exploiting Internet-like telecommunications that enables CLEAR capabilities to remain on Earth and to be uplinked as needed. To minimize crew time and operational cost, CLEAR exploits offline development and validation to support online teleoperations. Operational concept scenarios are developed for diagnostics, repair, and functional test operations. Many of the supporting functions defined in these operational scenarios are further defined as technologies in NASA/TM-2011-216956.

Oeftering, Richard C.↗
NASA NTRS1988

MODIS information, data and control system (MIDACS) operations concepts

The MODIS Information, Data, and Control System (MIDACS) Operations Concepts Document provides a basis for the mutual understanding between the users and the designers of the MIDACS, including the requirements, operating environment, external interfaces, and development plan. In defining the concepts and scope of the system, how the MIDACS will operate as an element of the Earth Observing System (EOS) within the EosDIS environment is described. This version follows an earlier release of a preliminary draft version. The individual operations concepts for planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, data archive and distribution, and user access do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams are not yet formed; however, it is possible to develop the operations concepts based on the present concept of EosDIS, the level 1 and level 2 Functional Requirements Documents, and through interviews and meetings with key members of the scientific community. The operations concepts were exercised through the application of representative scenarios.

Han, D.↗