SEARCH · Search NASA

Results for “Operations”

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.

SourceResearch connectionFrom yearThrough year

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

At least 379 records · Page 21

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Results of prototype software development for automation of shuttle proximity operations

The effort involves demonstration of expert system technology application to Shuttle rendezvous operations in a high-fidelity, real-time simulation environment. The JSC Systems Engineering Simulator (SES) served as the test bed for the demonstration. Rendezvous applications were focused on crew procedures and monitoring of sensor health and trajectory status. Proximity operations applications were focused on monitoring, crew advisory, and control of the approach trajectory. Guidance, Navigation, and Control areas of emphasis included the approach, transition and stationkeeping guidance, and laser docking sensor navigation. Operator interface displays for monitor and control functions were developed. A rule-based expert system was developed to manage the relative navigation system/sensors for nominal operations and simple failure contingencies. Testing resulted in the following findings; (1) the developed guidance is applicable for operations with LVLH stabilized targets; (2) closing rates less than 0.05 feet per second are difficult to maintain due to the Shuttle translational/rotational cross-coupling; (3) automated operations result in reduced propellant consumption and plume impingement effects on the target as compared to manual operations; and (4) braking gates are beneficial for trajectory management. A versatile guidance design was demonstrated. An accurate proximity operations sensor/navigation system to provide relative attitude information within 30 feet is required and redesign of the existing Shuttle digital autopilot should be considered to reduce the cross-coupling effects. This activity has demonstrated the feasibility of automated Shuttle proximity operations with the Space Station Freedom. Indications are that berthing operations as well as docking can be supported.

Hiers, Hal↗

NASA NTRS1993

Operator Performance Support System (OPSS)

In the complex and fast reaction world of military operations, present technologies, combined with tactical situations, have flooded the operator with assorted information that he is expected to process instantly. As technologies progress, this flow of data and information have both guided and overwhelmed the operator. However, the technologies that have confounded many operators today can be used to assist him -- thus the Operator Performance Support Team. In this paper we propose an operator support station that incorporates the elements of Video and Image Databases, productivity Software, Interactive Computer Based Training, Hypertext/Hypermedia Databases, Expert Programs, and Human Factors Engineering. The Operator Performance Support System will provide the operator with an integrating on-line information/knowledge system that will guide expert or novice to correct systems operations. Although the OPSS is being developed for the Navy, the performance of the workforce in today's competitive industry is of major concern. The concepts presented in this paper which address ASW systems software design issues are also directly applicable to industry. the OPSS will propose practical applications in how to more closely align the relationships between technical knowledge and equipment operator performance.

Conklin, Marlen Z.↗

NASA NTRS1991

Proximity operations considerations affecting spacecraft design

Experience from several recent spacecraft development programs, such as Space Station Freedom (SSF) and the Orbital Maneuvering Vehicle (OMV) has shown the need for factoring proximity operations considerations into the vehicle design process. Proximity operations, those orbital maneuvers and procedures which involve operation of two or more spacecraft at ranges of less than one nautical mile, are essential to the construction, servicing, and operation of complex spacecraft. Typical proximity operations considerations which drive spacecraft design may be broken into two broad categories; flight profile characteristics and concerns, and use of various spacecraft systems during proximity operations. Proximity operations flight profile concerns include the following: (1) relative approach/separation line; (2) relative orientation of the vehicles; (3) relative translational and rotational rates; (4) vehicle interaction, in the form of thruster plume impingement, mating or demating operations, or uncontrolled contact/collision; and (5) active vehicle piloting. Spacecraft systems used during proximity operations include the following: (1) sensors, such as radar, laser ranging devices, or optical ranging systems; (2) effector hardware, such as thrusters; (3) flight control software; and (4) mating hardware, needed for docking or berthing operations. A discussion of how these factors affect vehicle design follows, addressing both active and passive/cooperative vehicles.

Staas, Steven K.↗

NASA NTRS1992

Min and max are the only continuous ampersand-, V-operations for finite logics

Experts usually express their degrees of belief in their statements by the words of a natural language (like 'maybe', 'perhaps', etc.). If an expert system contains the degrees of beliefs t(A) and t(B) that correspond to the statements A and B, and a user asks this expert system whether 'A&B' is true, then it is necessary to come up with a reasonable estimate for the degree of belief of A&B. The operation that processes t(A) and t(B) into such an estimate t(A&B) is called an &-operation. Many different &-operations have been proposed. Which of them to choose? This can be (in principle) done by interviewing experts and eliciting a &-operation from them, but such a process is very time-consuming and therefore, not always possible. So, usually, to choose a &-operation, the finite set of actually possible degrees of belief is extended to an infinite set (e.g., to an interval (0,1)), define an operation there, and then restrict this operation to the finite set. Only this original finite set is considered. It is shown that a reasonable assumption that an &-operation is continuous (i.e., that gradual change in t(A) and t(B) must lead to a gradual change in t(A&B)), uniquely determines min as an &-operation. Likewise, max is the only continuous V-operation. These results are in good accordance with the experimental analysis of 'and' and 'or' in human beliefs.

Kreinovich, Vladik↗

NASA NTRS1996

Operations engineering: Applying hands-on experience to the development process

The concepts behind operations engineering as applied to the requirements, design, development and testing of data processing systems are presented, together with the associated benefits. The objective of operations engineering is to reduce the overall life cycle costs by integrating operations experience with the development process. To achieve this goal, operations engineering seeks to reduce the development costs by that assuring operational requirements are incorporated into the design and development process as early as possible, and reduce the operational costs by decreasing operations staffing requirements and other related costs through improved system capabilities. The areas for improved system capabilities include: system recovery; data recovery; fault isolation; system operability; system flexibility; system automation; and system reporting. It is described how operations engineering is integrated with the development process, and the difficulties and misconceptions experienced in using operations engineering are discussed.

Alcott, Gary↗

NASA NTRS1997

Applied Virtual Reality in Reusable Launch Vehicle Design, Operations Development, and Training

Application of Virtual Reality (VR) technology offers much promise to enhance and accelerate the development of Reusable Launch Vehicle (RLV) infrastructure and operations while simultaneously reducing developmental and operational costs. One of the primary cost areas in the RLV concept that is receiving special attention is maintenance and refurbishment operations. To produce and operate a cost effective RLV, turnaround cost must be minimized. Designing for maintainability is a necessary requirement in developing RLVs. VR can provide cost effective methods to design and evaluate components and systems for maintenance and refurbishment operations. The National Aeronautics and Space Administration (NASA)/Marshall Space Flight Center (MSFC) is beginning to utilize VR for design, operations development, and design analysis for RLVs. A VR applications program has been under development at NASA/MSFC since 1989. The objectives of the MSFC VR Applications Program are to develop, assess, validate, and utilize VR in hardware development, operations development and support, mission operations training and science training. The NASA/MSFC VR capability has also been utilized in several applications. These include: 1) the assessment of the design of the late Space Station Freedom Payload Control Area (PCA), the control room from which onboard payload operations are managed; 2) a viewing analysis of the Tethered Satellite System's (TSS) "end-of-reel" tether marking options; 3) development of a virtual mockup of the International Space Welding Experiment for science viewing analyses from the Shuttle Remote Manipulator System elbow camera and as a trainer for ground controllers; and 4) teleoperations using VR. This presentation will give a general overview of the MSFC VR Applications Program and describe the use of VR in design analyses, operations development, and training for RLVs.

Hale, Joseph P.↗

NASA NTRS1997

Coping with Irregular Operations: Implications for a Free Flight Environment

Irregular operations involve disruption of scheduled airline operations. They ate of concern to the carriers because they cost money, require personnel effort, and may harm customer good will. Irregular operations may result from aircraft system malfunctions that take planes out of service or result in cancellations, Might system problems or passenger medical emergencies that require diversions, local airport problems that may close down a runway, or weather systems that restrict flow into airports or regions. At the heart of responding to irregular operations is distributed decision making by members of airline operations centers, pilots, and the air traffic control system. Six U.S. carriers participated in a study in which we observed strategies used by operations center personnel to handle various classes of irregular operations. We focused on situations that are most disruptive to regular operations and are most difficult to cope with. We also sought to identify classes of events that would be most affected by changes in the air traffic management system. How a carrier deals with disruptions to its schedule reflects its philosophy and primary goals, as well as its resources. Size and type of operations (short or long-haul) determine which problems have priority. Each airline has different technological support tools to aid in flight planning and replanning, and some carriers have established contingency procedures for coping with various situations. We also examined differences in extent and type of interaction between ABC personnel and various elements of the air traffic system as they managed various problems: who interacts with AM what situations prompt interaction, how often these occur, and the outcomes and Perceived benefits. Use of the expanded NRP program was also studied, along with its advantages to the individual companies. We also examined the implications of the proposed change to a free flight environment on airline strategies for coping with irregular operations.

Orasanu, Judith↗

NASA NTRS2002

A Virtual Mission Operations Center: Collaborative Environment

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/product lifecycle - concept development, proposal preparation, and formulation. The VMOC-CE expands the application of the VSDE into the operations portion of the system lifecycle. It will enable meaningful and real-time collaboration regardless of the geographical distribution of project team members. Team members will be able to interact in satellite operations, specifically for resolving anomalies, through access to a desktop computer and the Internet. Mission Operations Management will be able to participate and monitor up to the minute status of anomalies or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities, and technologies.

Medina, Barbara↗

NASA NTRS2003

Runway Operations Planning: A Two-Stage Solution Methodology

The airport runway is a scarce resource that must be shared by different runway operations (arrivals, departures and runway crossings). Given the possible sequences of runway events, careful Runway Operations Planning (ROP) is required if runway utilization is to be maximized. Thus, Runway Operations Planning (ROP) is a critical component of airport operations planning in general and surface operations planning in particular. From the perspective of departures, ROP solutions are aircraft departure schedules developed by optimally allocating runway time for departures given the time required for arrivals and crossings. In addition to the obvious objective of maximizing throughput, other objectives, such as guaranteeing fairness and minimizing environmental impact, may be incorporated into the ROP solution subject to constraints introduced by Air Traffic Control (ATC) procedures. Generating optimal runway operations plans was approached in with a 'one-stage' optimization routine that considered all the desired objectives and constraints, and the characteristics of each aircraft (weight class, destination, Air Traffic Control (ATC) constraints) at the same time. Since, however, at any given point in time, there is less uncertainty in the predicted demand for departure resources in terms of weight class than in terms of specific aircraft, the ROP problem can be parsed into two stages. In the context of the Departure Planner (OP) research project, this paper introduces Runway Operations Planning (ROP) as part of the wider Surface Operations Optimization (SOO) and describes a proposed 'two stage' heuristic algorithm for solving the Runway Operations Planning (ROP) problem. Focus is specifically given on including runway crossings in the planning process of runway operations. In the first stage, sequences of departure class slots and runwy crossings slots are generated and ranked based on departure runway throughput under stochastic conditions. In the second stage, the departure class slots are populated with specific flights from the pool of available aircraft, by solving an integer program. Preliminary results from the algorithm implementation on real-world traffic data are included.

Anagnostakis, Ioannis↗

NASA NTRS2004

Spaceflight Operations Services Grid (SOSG)

In an effort to adapt existing space flight operations services to new emerging Grid technologies we are developing a Grid-based prototype space flight operations Grid. This prototype is based on the operational services being provided to the International Space Station's Payload operations located at the Marshall Space Flight Center, Alabama. The prototype services will be Grid or Web enabled and provided to four user communities through portal technology. Users will have the opportunity to assess the value and feasibility of Grid technologies to their specific areas or disciplines. In this presentation descriptions of the prototype development, User-based services, Grid-based services and status of the project will be presented. Expected benefits, findings and observations (if any) to date will also be discussed. The focus of the presentation will be on the project in general, status to date and future plans. The End-use services to be included in the prototype are voice, video, telemetry, commanding, collaboration tools and visualization among others. Security is addressed throughout the project and is being designed into the Grid technologies and standards development. The project is divided into three phases. Phase One establishes the baseline User-based services required for space flight operations listed above. Phase Two involves applying Gridlweb technologies to the User-based services and development of portals for access by users. Phase Three will allow NASA and end users to evaluate the services and determine the future of the technology as applied to space flight operational services. Although, Phase One, which includes the development of the quasi-operational User-based services of the prototype, development will be completed by March 2004, the application of Grid technologies to these services will have just begun. We will provide status of the Grid technologies to the individual User-based services. This effort will result in an extensible environment that incorporates existing and new spaceflight services into a standards-based framework providing current and future NASA programs with cost savings and new and evolvable methods to conduct science. This project will demonstrate how the use of new programming paradigms such as web and grid services can provide three significant benefits to the cost-effective delivery of spaceflight services. They will enable applications to operate more efficiently by being able to utilize pooled resources. They will also permit the reuse of common services to rapidly construct new and more powerful applications. Finally they will permit easy and secure access to services via a combination of grid and portal technology by a distributed user community consisting of NASA operations centers, scientists, the educational community and even the general population as outreach. The approach will be to deploy existing mission support applications such as the Telescience Resource Kit (TReK) and new applications under development, such as the Grid Video Distribution System (GViDS), together with existing grid applications and services such as high-performance computing and visualization services provided by NASA s Information Power Grid (IPG) in the MSFC s Payload Operations Integration Center (POIC) HOSC Annex. Once the initial applications have been moved to the grid, a process will begin to apply the new programming paradigms to integrate them where possible. For example, with GViDS, instead of viewing the Distribution service as an application that must run on a single node, the new approach is to build it such that it can be dispatched across a pool of resources in response to dynamic loads. To make this a reality, reusable services will be critical, such as a brokering service to locate appropriate resource within the pool. This brokering service can then be used by other applications such as the TReK. To expand further, if the GViDS application is constructed using a services-based mel, then other applications such as the Video Auditorium can then use GViDS as a service to easily incorporate these video streams into a collaborative conference. Finally, as these applications are re-factored into this new services-based paradigm, the construction of portals to integrate them will be a simple process. As a result, portals can be tailored to meet the requirements of specific user communities.

Bradford, Robert N.↗

NASA NTRS2005

Studies of Operating Frequency Effects On Ejector-based Thrust Augmentation in a Pulse Detonation Engine

Studies were performed in order to characterize the thrust augmentation potential of an ejector in a Pulse Detonation Engine application. A 49-mm diameter tube of 0.914-m length was constructed with one open end and one closed end. Ethylene, oxygen, and nitrogen were introduced into the tube at the closed end through the implementation of a fast mixing injector. The tube was completely filled with a stoichiometric mixture containing a one to one molar ratio of nitrogen to oxygen. Ethylene was selected as the fuel due to its detonation sensitivity and the molar ratio of the oxidizer was chosen for heat transfer purposes. Detonations were initiated in the tube through the use of a spark ignition system. The PDE was operated in a multi-cycle mode at frequencies ranging from 20-Hz to 50-Hz. Baseline thrust measurements with no ejector present were performed while operating the engine at various frequencies and compared to theoretical estimates. The baseline values were observed to agree with the theoretical model at low operating frequencies and proved to be increasingly lower than the predicted values as the operating frequency was increased. The baseline thrust measurements were observed to agree within 15 percent of the model for all operating frequencies. A straight 152-mm diameter ejector was installed and thrust augmentation percentages were measured. The length of the ejector was varied while the overlap percentage (percent of the ejector length which overlapped the tube) was maintained at 25 percent for all tests. In addition, the effect of ejector inlet geometry was investigated by comparing results with a straight inlet to those of a 38-mm inlet diameter. The thrust augmentation of the straight inlet ejector proved to be independent of engine operating frequency, augmenting thrust by 40 percent for the 0.914-m length ejector. In contrast, the rounded lip ejector of the same length seemed to be highly dependent on the engine operating frequency. An optimum operating frequency observed with the rounded inlet occurred at an operating frequency of 30-Hz, resulting in thrust augmentation percentages greater than 100 percent. The effect that the engine operating frequency had on thrust augmentation levels attained with an ejector was characterized and optimum performance parameters were established. Insight into the frequency dependent nature of the ejector performance was pursued. Suggestions for future experiments which are needed to fully understand the means in which thrust augmentation is achieved in a PDE-ejector configuration were noted.

Landry, K.↗

NASA NTRS2005

Predictive Interfaces for Long-Distance Tele-Operations

We address the development of predictive tele-operator interfaces for humanoid robots with respect to two basic challenges. Firstly, we address automating the transition from fully tele-operated systems towards degrees of autonomy. Secondly, we develop compensation for the time-delay that exists when sending telemetry data from a remote operation point to robots located at low earth orbit and beyond. Humanoid robots have a great advantage over other robotic platforms for use in space-based construction and maintenance because they can use the same tools as astronauts do. The major disadvantage is that they are difficult to control due to the large number of degrees of freedom, which makes it difficult to synthesize autonomous behaviors using conventional means. We are working with the NASA Johnson Space Center's Robonaut which is an anthropomorphic robot with fully articulated hands, arms, and neck. We have trained hidden Markov models that make use of the command data, sensory streams, and other relevant data sources to predict a tele-operator's intent. This allows us to achieve subgoal level commanding without the use of predefined command dictionaries, and to create sub-goal autonomy via sequence generation from generative models. Our method works as a means to incrementally transition from manual tele-operation to semi-autonomous, supervised operation. The multi-agent laboratory experiments conducted by Ambrose et. al. have shown that it is feasible to directly tele-operate multiple Robonauts with humans to perform complex tasks such as truss assembly. However, once a time-delay is introduced into the system, the rate of tele\ioperation slows down to mimic a bump and wait type of activity. We would like to maintain the same interface to the operator despite time-delays. To this end, we are developing an interface which will allow for us to predict the intentions of the operator while interacting with a 3D virtual representation of the expected state of the robot. The predictive interface anticipates the intention of the operator, and then uses this prediction to initiate appropriate sub-goal autonomy tasks.

Wheeler, Kevin R.↗

NASA NTRS2007

TBCC Fan Stage Operability and Performance

NASA s Fundamental Aeronautics Program is investigating turbine-based propulsion systems for access to space because it provides the potential for aircraft-like, space-launch operations that may significantly reduce launch costs and improve safety. Studies performed under NASA s NGLT and the NASP High Speed Propulsion Assessment (HiSPA) program indicated a variable cycle turbofan/ramjet was the best configuration to satisfy access-to-space mission requirements because this configuration maximizes the engine thrust-to-weight ratio while minimizing frontal area. To this end, NASA and GE teamed to design a Mach 4 variable cycle turbofan/ramjet engine for access to space. To enable the wide operating range of a Mach 4+ variable cycle turbofan ramjet required the development of a unique fan stage design capable of multi-point operation to accommodate variations in bypass ratio (10X), fan speed (7X), inlet mass flow (3.5X), inlet pressure (8X), and inlet temperature (3X). The primary goal of the fan stage was to provide a high pressure ratio level with good efficiency at takeoff through the mid range of engine operation, while avoiding stall and losses at the higher flight Mach numbers, without the use of variable inlet guide vanes. Overall fan performance and operability therefore requires major consideration, as competing goals at different operating points and aeromechanical issues become major drivers in the design. To mitigate risk of meeting the unique design requirements for the fan stage, NASA and GE teamed to design and build a 57% engine scaled fan stage to be tested in NASA s transonic compressor facility. The objectives of this test are to assess the aerodynamic and aero mechanic performance and operability characteristics of the fan stage over the entire range of engine operation including: 1) sea level static take-off, 2) transition over large swings in fan bypass ratio, 3) transition from turbofan to ramjet, and 4) fan windmilling operation at high Mach flight conditions. In addition, the fan stage design was validated by performing pre-test CFD analysis using both GE proprietary and NASA s APNASA codes. Herein we will discuss 1) the fan stage design, 2) the experiment including the unique facility and instrumentation, and 3) the comparison of pre-test CFD analysis to initial aerodynamic test results for the baseline fan stage configuration. Measurements and pre-test analysis will be compared at 37%, 50%, 80%, 90%, and 100% of design speed to assess the ability of state-of-the-art design and analysis tools to meet the fan stage performance and operability requirements for turbine based propulsion for access to space.

Suder, Kenneth L.↗

NASA NTRS2009

Spaceflight Systems Training: A Comparison and Contrasting of Techniques for Training Ground Operators and Onboard Crewmembers

When developing techniques and products for instruction on manned spaceflight systems, training organizations are often faced with two very different customers: ground operators and onboard crewmembers. Frequently, instructional development focuses on one of these customers with the assumption that the other s needs will be met by default. Experience teaches us that differing approaches are required when developing training tailored to the specific needs of each customer. As a rule, ground operators require focused instruction on specific areas of expertise. Their knowledge should be of the details of the hardware, software, and operational techniques associated with that system. They often benefit from historical knowledge of how their system has operated over its lifetime. Since several different ground operators may be interfacing with the same system, each individual operator must understand the agreed-to principles by which that system will be run. In contrast, onboard crewmembers require a more broad, hands-on awareness of their operational environment. Their training should be developed with an understanding of the physical environment in which they live and work and the day-to-day tasks they are most likely to perform. Rarely do they require a deep understanding of the details of a system; it is often sufficient to teach them just enough to maintain situational awareness and perform basic tasks associated with maintenance and operation of onboard systems. Crewmembers may also develop unique onboard operational techniques that differ from preceding crews. They should be taught what flexibility they have in systems operations and how their specific habits can be communicated to ground support personnel. This paper will explore the techniques that can be employed when developing training for these unique customers. We will explore the history of International Space Station training development and how past efforts can guide us in creating training for users of future manned spaceflight efforts.

Balmain, Clinton↗

NASA NTRS2011

International Space Station Payload Operations Integration

The Payload Operations Integrator (POINT) plays an integral part in the Certification of Flight Readiness process for the Mission Operations Laboratory and the Payload Operations Integration Function that supports International Space Station Payload operations. The POINTs operate in support of the POIF Payload Operations Manager to bring together and integrate the Certification of Flight Readiness inputs from various MOL teams through maintaining an open work tracking log. The POINTs create monthly metrics for current and future payloads that the Payload Operations Integration Function supports. With these tools, the POINTs assemble the Certification of Flight Readiness package before a given flight, stating that the Mission Operations Laboratory is prepared to support it. I have prepared metrics for Increment 29/30, maintained the Open Work Tracking Logs for Flights ULF6 (STS-134) and ULF7 (STS-135), and submitted the Mission Operations Laboratory Certification of Flight Readiness package for Flight 44P to the Mission Operations Directorate (MOD/OZ).

Fanske, Elizabeth Anne↗

NASA NTRS2014

Calculation of Operations Efficiency Factors for Mars Surface Missions

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 enough time to capture variations in relay asset interactions, Earth/Mars time phasing, and seasonal variations in holidays). This model is used to estimate the ops efficiency factor for each operations configuration. The second model in a separate Excel spreadsheet is a scenario model, which uses the sol types to rack up the total number of "scenario sols" for that scenario (in other words, the ideal number of sols it would take to perform the scenario objectives). Then, the number of sols requiring ground in the loop is calculated based on the soil types contained in the given scenario. Next, the scenario contains a description of what sequence of operations configurations is used, for how many days each, and this is used with the corresponding ops efficiency factors for each configuration to calculate the "ops duration" corresponding to that scenario. Finally, a margin is applied to determine the minimum surface lifetime required for that scenario. Typically, this level of analysis has not been performed until much later in the mission, and has not been able to influence mission design. Further, the notion of moving to sustainable operations during Prime Mission - and the effect that that move would have on surface mission productivity and mission objective choices - has not been encountered until the most recent rover missions (MSL and Mars 2018).

Layback, Sharon L.↗

NASA NTRS2014

Behavioral Health and Performance at NASA JSC: Recent Successes and Future Plan for BHP Research and Operations

The Behavioral Health and Performance discipline at NASA Johnson Space Center is organized into two distinct Divisions (Biomedical Research and Environmental Science Division and Space and Clinical Operations Division) but is integrated and interrelated in its day‐to‐day work. Ongoing operations supporting NASA's spaceflight goals benefit from the research portfolios that address risks to mission success. Similarly, these research portfolios are informed by operations to ensure investigations stay relevant given the dynamic environment of spaceflight. There are many success stories that can be presented where initial work begun as a BHP Research project, and funded through the Human Research Program, was fully implemented in operations or addressed an operational need. Examples include improving effectiveness of the debriefings used within Mission Control by the Mission Operations Directorate and countermeasures for fatigue management. There is also ongoing collaboration with research and operations for developing selection methods for future generation astronauts, and to enhance and inform the current family support function. The objective of this panel is to provide examples of recent success stories, describe areas where close collaboration is benefitting ongoing research and operations, and summarize how this will come together as NASA plans for the one year ISS mission - a unique opportunity for both BHP operations and research to learn more about preparing and supporting crewmembers for extended missions in space. The proposed panel will be comprised of six presentations, each describing a unique aspect of research or operations and the benefits to current and future spaceflight.

Leveton, L. B.↗

NASA NTRS2014

Correlation of ISS Electric Potential Variations with Mission Operations

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.

Willis, Emily M.↗