Search NASA⌕ Search

SEARCH · Search NASA

Results for “operation phases”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Entry, Descent, and Landing Operations Analysis for the Genesis Re-Entry Capsule

On September 8, 2004, the Genesis spacecraft returned to Earth after spending 29 months about the sun-Earth libration point collecting solar wind particles. Four hours prior to Earth arrival, the entry capsule containing the samples was released for entry and subsequent landing at the Utah Test and Training Range. This paper provides an overview of the entry, descent, and landing trajectory analysis that was performed during the Mission Operations Phase leading up to final approach to Earth. The operations effort accurately delivered the entry capsule to the desired landing site. The final landing location was 8.3 km from the target, and was well within the allowable landing area. Preliminary reconstruction analyses indicate that the actual entry trajectory was very close to the pre-entry prediction.

Desai, Prasun N.↗
NASA NTRS1993

Mars Observer mission status and orbit insertion phase planning

The Mars Observer spacecraft will reach Mars on August 24, 1993. Launch and cruise phase operations have gone smoothly, with few spacecraft anomalies. The orbit insertion phase, which spans a three month period and involves a series of seven maneuvers, has been redesigned postlaunch making use of excess spacecraft velocity change (Delta V) capability to advance the mapping phase, now planned to begin November 24, 1993. This is highly desirable since it moves the start of the mapping phase away from solar conjunction and the expected dust storm disturbances. The redesign process involved making tradeoffs between science, operations, and maneuver requirements. At Mars, the spacecraft will continuously record data with a single daily playback through the Deep Space Network's 34-meter high-efficiency antennas for one Martian year.

Dodd, Suzanne R.↗
NASA NTRS1977

Space transportation system payload interface verification

The paper considers STS payload-interface verification requirements and the capability provided by STS to support verification. The intent is to standardize as many interfaces as possible, not only through the design, development, test and evaluation (DDT and E) phase of the major payload carriers but also into the operational phase. The verification process is discussed in terms of its various elements, such as the Space Shuttle DDT and E (including the orbital flight test program) and the major payload carriers DDT and E (including the first flights). Five tools derived from the Space Shuttle DDT and E are available to support the verification process: mathematical (structural and thermal) models, the Shuttle Avionics Integration Laboratory, the Shuttle Manipulator Development Facility, and interface-verification equipment (cargo-integration test equipment).

Everline, R. T.↗
NASA NTRS1984

Executable assertions and flight software

It is pointed out that executable assertions can be used for dynamic testing of software. An executable assertion is a logical statement about the variables or a block of code. If there is no error during execution then the assertion statement results in a true value. Assertions are useful for testing purposes throughout the lifecycle of software. They can be used for validation during the design phase, and for exception handling and error detection during the operation phase. The present investigation has the objective to study the use of executable assertions for testing flight software. Attention is given to details regarding executable assertions, the digital flight control system, testing flight software, and preliminary experimental results.

Mahmood, A.↗
DOE OSTI2026

Tokamak Energy’s pre-concept design for a fusion power plant: an overview of ST-E1

Climate change and rapidly rising energy demand, driven in part by artificial intelligence and data-centre growth, create an urgent need for stable, low-carbon, and abundant power. Fusion is a promising long-term solution, yet its commercialisation faces a fundamental paradox in today’s investment environment: pilot plants are essential to de-risk physics, engineering, and operations, but their limited lifetime energy output and high upfront costs make them difficult to finance. This paper presents Tokamak Energy’s response: ST-E1, a pre-concept design for a low-aspect-ratio tokamak power plant engineered specifically to overcome this challenge. ST-E1 is designed from the outset for phased operation—pilot and commercial phases, with an upgrade phase in between—with emphasis on commercial viability, maintainability, nuclear engineering, modularity, and upgradability. A key design principle is the deliberate separation of long-lived assets, such as the magnet cage and vacuum vessel, from replaceable in-vessel systems. This provides an attractive and credible investment approach to generate operational data and de-risk key technologies while preserving most capital-intensive assets for later commercial phases. The architecture supports continuous optimisation toward high net electric power (targeting 800–1000 MW net electric), a normalised capital expenditure of $\$$ 12–14k/kW of net electric power, and high availability (targeting > 80%). A tokamak core with a 5 m major radius, aspect ratio of 2.3, and on-plasma axis toroidal field of 5.25 T was selected to meet these objectives. This paper summarises the ST-E1 design philosophy, principal features, and development methodology. It introduces a Focus Collection of 11 papers detailing the pre-concept design of the entire tokamak and corresponding plant.

ST-E1↗
NASA NTRS2013

Discrete Data Qualification System and Method Comprising Noise Series Fault Detection

A Sensor Data Qualification (SDQ) function has been developed that allows the onboard flight computers on NASA s launch vehicles to determine the validity of sensor data to ensure that critical safety and operational decisions are not based on faulty sensor data. This SDQ function includes a novel noise series fault detection algorithm for qualification of the output data from LO2 and LH2 low-level liquid sensors. These sensors are positioned in a launch vehicle s propellant tanks in order to detect propellant depletion during a rocket engine s boost operating phase. This detection capability can prevent the catastrophic situation where the engine operates without propellant. The output from each LO2 and LH2 low-level liquid sensor is a discrete valued signal that is expected to be in either of two states, depending on whether the sensor is immersed (wet) or exposed (dry). Conventional methods for sensor data qualification, such as threshold limit checking, are not effective for this type of signal due to its discrete binary-state nature. To address this data qualification challenge, a noise computation and evaluation method, also known as a noise fault detector, was developed to detect unreasonable statistical characteristics in the discrete data stream. The method operates on a time series of discrete data observations over a moving window of data points and performs a continuous examination of the resulting observation stream to identify the presence of anomalous characteristics. If the method determines the existence of anomalous results, the data from the sensor is disqualified for use by other monitoring or control functions.

Fulton, Christopher↗
NASA NTRS1971

Logistics planning for phased programs

Logistics planning as integral part of phased program planning process, considering preliminary analysis, definition, design, development, fabrication, test and operations phases

Goodrum, J. C.↗
NASA NTRS2004

Error Cost Escalation Through the Project Life Cycle

It is well known that the costs to fix errors increase as the project matures, but how fast do those costs build? A study was performed to determine the relative cost of fixing errors discovered during various phases of a project life cycle. This study used three approaches to determine the relative costs: the bottom-up cost method, the total cost breakdown method, and the top-down hypothetical project method. The approaches and results described in this paper presume development of a hardware/software system having project characteristics similar to those used in the development of a large, complex spacecraft, a military aircraft, or a small communications satellite. The results show the degree to which costs escalate, as errors are discovered and fixed at later and later phases in the project life cycle. If the cost of fixing a requirements error discovered during the requirements phase is defined to be 1 unit, the cost to fix that error if found during the design phase increases to 3 - 8 units; at the manufacturing/build phase, the cost to fix the error is 7 - 16 units; at the integration and test phase, the cost to fix the error becomes 21 - 78 units; and at the operations phase, the cost to fix the requirements error ranged from 29 units to more than 1500 units

Stecklein, Jonette M.↗
NASA NTRS1985

Synchronous clock stopper for microprocessor

A synchronous clock stopper circuit for inhibiting clock pulses to a microprocessor in response to a stop request signal, and for reinstating the clock pulses in response to a start request signal thereby to conserve power consumption of the microprocessor when used in an environment of limited power. The stopping and starting of the microprocessor is synchronized, by a phase tracker, with the occurrences of a predetermined phase in the instruction cycle of the microprocessor in which the I/O data and address lines of the microprocessor are of high impedance so that a shared memory connected to the I/O lines may be accessed by other peripheral devices. The starting and stopping occur when the microprocessor initiates and completes, respectively, an instruction, as well as before and after transferring data with a memory. Also, the phase tracker transmits phase information signals over a bus to other peripheral devices which signals identify the current operational phase of the microprocessor.

Kitchin, David A.↗
NASA NTRS1974

Solar residential heating and cooling system development test program

A solar heating and cooling system is described, which was installed in a simulated home at Marshall Space Flight Center. Performance data are provided for the checkout and initial operational phase for key subsystems and for the total system. Valuable information was obtained with regard to operation of a solar cooling system during the first summer of operation. Areas where improvements and modifications are required to optimize such a system are discussed.

Humphries, W. R.↗
NASA NTRS1992

The next century astrophysics program

The Astrophysics Division within the NASA Office of Space Science and Applications (OSSA) has defined a set of flagship and intermediate missions that are presently under study for possible launch during the next 20 years. These missions and tentative schedules, referred to as the Astrotech 21 Mission Set, are summarized. The missions are in three groups corresponding to the cognizant science branch within the Astrophysics Division. Phase C/D refers to the pre-launch construction and delivery of the spacecraft, and the Operations Phase refers to the period when the mission is active in space. Approximately 1.5 years before the start of Phase C/D, a non-advocate review (NAR) is held to ensure that the mission/system concept and the requisite technology are at an appropriate stage of readiness for full scale development to begin. Therefore, technology development is frozen (usually) as of the date of a successful NAR. An overview of the technology advances required for each of the three wavelength groups is provided in the following paragraphs, along with a brief description of the individual missions.

Swanson, Paul N.↗
NASA NTRSDate not supplied

Developing a Cybersecurity Architecture for Extensible Traffic Management (xTM)

This paper explores the development of a cybersecurity architecture tailored for Extensible Traffic Management (xTM) to address emerging challenges in managing diverse aerial vehicles within the National Airspace System (NAS). Driven by technological advances and the rise of uncrewed aerial systems (UAS), urban air mobility (UAM), and high-altitude traffic (ETM), the NAS is undergoing a paradigm shift. Traditional air traffic management, reliant on traditional Federal Aviation Administration (FAA) control, will give way to decentralized coordination among autonomous and semi-autonomous systems. The proposed xTM Security Architecture, designed as a high-level framework, focuses on ensuring the confidentiality, integrity, and availability of data and operations in this evolving ecosystem. Utilizing threat modeling, the research identifies potential risks across key flight phases, operations and use cases to offer security control recommendations. Key objectives include analyzing interactions between novel airspace entrants and existing NAS traffic, cataloging vulnerabilities, and developing mitigative strategies to ensure safety, operational stability, and secure data exchanges. This research lays the groundwork for regulatory and industry adaptation, providing critical insights into managing cybersecurity risks in this complex, multi-domain environment.

UAM↗
NASA NTRS2004

Spitzer Space Telescope in-orbit checkout and science verification operations

Spitzer Space Telescope, the fourth and final of NASA's great observatories, and the first mission in NASA's Origins Program was launched 25 August 2003 into an Earth-trailing solar orbit. The observatory was designed to probe and explore the universe in the infrared. Before science data could be acquired, however, the observatory had to be initialized, characterized, calibrated, and commissioned. A two phased operations approach was defined to complete this work. These phases were identified as In-Orbit Checkout (IOC) and Science Verification (SV). Because the observatory lifetime is cryogen-limited these operations had to be highly efficient. The IOC/SV operations design accommodated a pre-defined distributed organizational structure and a complex, cryogenic flight system. Many checkout activities were inter-dependent, and therefore the operations concept and ground data system had to provide the flexibility required for a 'short turn-around' environment. This paper describes the adaptive operations system design and evolution, implementation, and lessons-learned from the completion of IOC/SV.

space verification↗
NASA NTRS2012

Improving operations: Metrics to Results

As a result of the mission failure of the Mars Climate Orbiter (MCO) spacecraft in 1999, the Jet Propulsion Laboratory (JPL) initiated the development of a Mission Operations Assurance (MOA) program to be implemented across all flight projects managed by JPL. One of the initiatives undertaken in 2001 was the collection of data on command file errors occurring in the operational phase of the mission. This paper defines command file errors and how and where they occur in the operations process. It also describes the problem reporting system (PRS) in use for mission operations at JPL. We examine the recent modifications to the PRS that enable the collection of metrics, specifically on command file errors. This paper discusses what the data show us since metrics have been collected for the operational missions conducted by JPL. We examine the evolution of an operational working group initiative to evaluate proximate, contributing, and root causes for the errors. As part of this discussion we see what the metrics have indicated over a decade. At the macro level, we can say that the aggregate command file error rate has been cut to roughly one third of the initial 2001 level by the end of 2011. Additionally, we explore efficient and innovative means to continually integrate the findings and recommendations from the working group back into the flight operations environment.

command file errors↗
NASA NTRS1979

Space Transportation systems overview

Planning for the operations phase of the Space Transportation system is reviewed. Attention is given to mission profile (typical), applications, manifesting rationale, the Operational Flight Test manifest, the operations manifest, pricing policy, and potential applications of the STS.

Lee, C. M.↗
NASA NTRS1991

Retrievable Payload Carrier (RPC): Next generation Long Duration Exposure Facility

The Retrievable Payload Carrier (RPC) is described which is a multi-experiment, free-flyer spacecraft being privately developed to make in-space experimentation more accessible and economically feasible for research and development organizations. The carrier concept was derived from NASA's highly successful and flight proven Long Duration Exposure Facility (LDEF). The LDEF capabilities were enhanced to meet new customer requirements. This reusable payload carrier is planned for launch and retrieval by the space shuttle on a regular basis. The RPC's compact design facilitates flexible manifesting of the shuttle cargo bay space, thereby, permitting timely launches and retrievals. The vehicle is designed so that either the entire carrier can be retrieved from orbit, or individual experiment pallets can be removed and replaced in orbit. This gives customers even greater control over their experiment recoveries. A fully operational RPC System consists of: (1) a carrier spacecraft; (2) a ground control station for communication with customer payloads and the carrier; (3) a ground processing facility to provide refurbishment, final checkout, and integration of customer payloads and the carrier; and (4) the personnel required to support both the development and operation phases of the program. Customer payloads will fly 6 to 18 month missions, or longer, as required. Spreading launch, operations, and retrieval costs over multiple experimental payloads results in minimized customer costs. The RPC Program's initial objective is to operate a simple carrier system which meets basic customer service needs.

Perry, Arthur T.↗
NASA NTRS1993

Novel properties of the q-analogue quantized radiation field

The 'classical limit' of the q-analog quantized radiation field is studied paralleling conventional quantum optics analyses. The q-generalizations of the phase operator of Susskind and Glogower and that of Pegg and Barnett are constructed. Both generalizations and their associated number-phase uncertainty relations are manifestly q-independent in the n greater than g number basis. However, in the q-coherent state z greater than q basis, the variance of the generic electric field, (delta(E))(sup 2) is found to be increased by a factor lambda(z) where lambda(z) greater than 1 if q not equal to 1. At large amplitudes, the amplitude itself would be quantized if the available resolution of unity for the q-analog coherent states is accepted in the formulation. These consequences are remarkable versus the conventional q = 1 limit.

Nelson, Charles A.↗