Search NASA⌕ Search

SEARCH · Search NASA

Results for “sequencing mission operations system”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Trade Spaces in Crewed Spacecraft Atmosphere Revitalization System Development

Developing the technological response to realizing an efficient atmosphere revitalization system for future crewed spacecraft and space habitats requires identifying and describing functional trade spaces. Mission concepts and requirements dictate the necessary functions; however, the combination and sequence of those functions possess significant flexibility. Us-ing a closed loop environmental control and life support (ECLS) system architecture as a starting basis, a functional unit operations approach is developed to identify trade spaces. Generalized technological responses to each trade space are discussed. Key performance parameters that apply to functional areas are described.

Perry, Jay L.↗
NASA NTRS2016

On the Maneuvers Operational Response for NASA’s Soil Moisture Active-Passive (SMAP) Mission

The Soil-Moisture Active-Passive (SMAP) spacecraft requires various kinds of in-orbit maneuvers over the course of its three-year mission. The types of maneuvers include pre-planned commissioning maneuvers to reach its science orbit, regularly executed orbit maintenance maneuvers to overcome drag and other nominally occurring phenomena, as well as (the possibility of) collision avoidance maneuvers. The architecture of the spacecraft – in terms of availability of commanding via ground assets, the inherited avionics' ability to sequence and execute commands, and the capability of available subsystems able to carry out maneuvers – was well defined early in the development of the spacecraft and mission, well before the operational plan for responding to maneuver requests was cemented. The systems engineering challenge became: how to accommodate all three types of maneuvers in the confines of this well-defined architecture. This paper will describe how the operations team on SMAP successfully met this challenge. Specifically, it will dive into the three pronged approach that SMAP developed to handle each type of maneuver described above – to meet the timeliness requirements leveraged on the operations team to execute said maneuvers, while continuing to fit within the allotted staffing profile during nominal operations. Defining this paradigm to fit the mission’s architecture meant re-defining the original paradigm, (planned maneuvers being thought of separately than collision avoidance maneuvers), and re-classifying all responses to maneuver requests as variations and permutations of a singular operational response to a maneuver request. This paper will also describe the tools that were created to simplify the human interface and automate as much of the response as was possible. Finally, this paper will describe, at a very high level, some of the problems encountered and lessons learned by the operations team when this process was executed the first four times during the first ninety days of operations. Though the architecture of the operations team's response to maneuver requests will never be repeated exactly, the flexibility that was inserted via redefining the scope of the problem and by redefining the human interfaces should influence future projects' architectures earlier in their development – in the hopes that said influence will save time and money in the future.

Tirona, Joseph↗
NASA NTRS1990

STS-41 Space Shuttle mission report

The STS-41 Space Shuttle Program Mission Report contains a summary of the vehicle subsystem activities on this thirty-sixth flight of the Space Shuttle and the eleventh flight of the Orbiter vehicle, Discovery (OV-103). In addition to the Discovery vehicle, the flight vehicle consisted of an External Tank (ET) (designated as ET-39/LWT-32), three Space Shuttle main engines (SSME's) (serial numbers 2011, 2031, and 2107), and two Solid Rocket Boosters (SRB's), designated as BI-040. The primary objective of the STS-41 mission was to successfully deploy the Ulysses/inertial upper stage (IUS)/payload assist module (PAM-S) spacecraft. The secondary objectives were to perform all operations necessary to support the requirements of the Shuttle Backscatter Ultraviolet (SSBUV) Spectrometer, Solid Surface Combustion Experiment (SSCE), Space Life Sciences Training Program Chromosome and Plant Cell Division in Space (CHROMEX), Voice Command System (VCS), Physiological Systems Experiment (PSE), Radiation Monitoring Experiment - 3 (RME-3), Investigations into Polymer Membrane Processing (IPMP), Air Force Maui Optical Calibration Test (AMOS), and Intelsat Solar Array Coupon (ISAC) payloads. The sequence of events for this mission is shown in tabular form. Summarized are the significant problems that occurred in the Orbiter subsystems during the mission. The official problem tracking list is presented. In addition, each Orbiter problem is cited in the subsystem discussion.

Camp, David W.↗
NASA NTRS1993

Mars Observer Press Conference JPL

The Mars Observer mission spacecraft was primarily designed for exploring Mars and the Martian environment. The Mars Observer was launched on September 25, 1992. The spacecraft was lost in the vicinity of Mars on August 21, 1993 when the spacecraft began its maneuvering sequence for Martian orbital insertion. This videotape shows a press briefing, held after the spacecraft had not responded to attempts to communicate with it, to explain to the press the problems and the steps that were being taken to re-establish communication with the spacecraft. The communications had been shutdown prior to the orbital insertion burn to protect the instruments. At the time of the press conference, the communications system was still not operational, and attempts were being made to re-establish communication. Bob McMillan of the Public Affairs Office at JPL gives the initial announcement of the continuing communication problem with the spacecraft. Mr. McMillan introduces William Piotrowski, acting director of solar system exploration, who reiterates that there is indeed no communication with the Observer spacecraft. He is followed by Glenn Cunningham, the Project Manager of the Mars Observer who speaks about the attempts to re-establish contact. Mr. Cunningham is followed by Satenios Dallas, the Mission Manager for the Mars Observer Project, who speaks about the sequence of events leading up to the communication failure, and shows an animated video presenting the orbital insertion maneuvers. The briefing was then opened up for questions from the assembled press, both at JPL and at the other NASA Centers. The questions are about the possible reasons for the communication failure, and the attempts to restore communications with the spacecraft. Dr. Arden L. Albee, chief scientist for the Mars Observer Mission, joins the other panel members to answer questions. At the end of the press briefing the animation of the Mars orbital insertion is shown again.

Source record↗
NASA NTRS2024

Development Testing and Analysis of the Integrated Gateway-ESPRIT Bipropellant Refuelling System

The Gateway will be humanity’s first space station orbiting the Moon completed by NASA in partnership with ESA and other US and international partners. The Gateway will provide critical support to sustainable human exploration on the moon through the Artemis program. To enable the Lunar Gateway to complete its mission, on orbit refuelling is essential. The ESPRIT Refuelling Module (ERM) will provide the capability to transfer propellants, MMH and MON-3, through the Habitation and Logistics Outpost (HALO) to the Power and Propulsion Element (PPE). The transfer of these propellants carries known risks and hazards. These hazards include overpressure of the propellant lines during priming sequences between modules and during refuelling pause operations. To support the early system development and to mitigate these risks, a collaborative test program between NASA, ESA and Thales Alenia Space was completed at the Thales Alenia Space test facility in Harwell, UK. This test program integrated fluidic breadboards of the ERM, HALO and PPE modules. The objectives of the test program were to demonstrate and characterise critical performance and transient operations, inform refuelling concept of operations and to calibrate and validate numerical models of the refuelling subsystem in EcosimPro. To support the completion of this final objective a detailed model of the integrated breadboard was developed in EcosimPro and key steady-state and transient test cases were simulated. As an industry first, a National Institute of Standards and Technology (NIST) database correlation for Hydrofluoroether (HFE-7000) was used as a mixed oxides of nitrogen (MON-3) simulant with EcosimPro and European Space Propulsion System Simulation (ESPSS) libraries to result in a more accurate analysis for transient phenomenon such as priming. The test and simulation data showed good agreement validating the model for further system analysis as the ERM design progresses.

Refuelling↗
NASA NTRS2013

Design and Development of the MSL Descent Stage Propulsion System

On August 5, 2012, The Mars Science Laboratory mission successfully landed the largest interplanetary rover ever built, Curiosity, on the surface of Mars. The Entry, Descent, and Landing (EDL) phase of this mission was by far the most complex landing ever attempted on a planetary body. The Descent Stage Propulsion System played an integral and critical role during Curiosity's EDL. The Descent Stage Propulsion System was a one of a kind hydrazine propulsion system designed specifically for the EDL phase of the MSL mission. It was designed, built, and tested at the Jet Propulsion Laboratory (JPL). The purpose of this paper is to present an overview of the design and development of the MSL Descent Stage Propulsion System. Driving requirements, system design, component selection, operational sequence of the system at Mars, new developments, and key challenges will be discussed.

Weiss, Jeffrey M.↗
NASA NTRS2006

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The daily preparation of uplink products (commands and files) for Deep Impact was as problematic as the final encounter images were spectacular. The operations team was faced with many challenges during the six-month mission to comet Tempel One of the biggest difficulties was that the Deep Impact Flyby and Impactor vehicles necessitated a high volume of uplink products while also utilizing a new uplink file transfer capability. The Jet Propulsion Laboratory (JPL) Multi-Mission Ground Systems and Services (MGSS) Mission Planning and Sequence Team (MPST) had the responsibility of preparing the uplink products for use on the two spacecraft. These responsibilities included processing nearly 15,000 flight products, modeling the states of the spacecraft during all activities for subsystem review, and ensuring that the proper commands and files were uplinked to the spacecraft. To guarantee this transpired and the health and safety of the two spacecraft were not jeopardized several new ground scripts and procedures were developed while the Deep Impact Flyby and Impactor spacecraft were en route to their encounter with Tempel-1. These scripts underwent several adaptations throughout the entire mission up until three days before the separation of the Flyby and Impactor vehicles. The problems presented by Deep Impact's daily operations and the development of scripts and procedures to ease those challenges resulted in several valuable lessons learned. These lessons are now being integrated into the design of current and future MGSS missions at JPL.

uplink↗
NASA NTRS2012

VML 3.0 Reactive Sequencing Objects and Matrix Math Operations for Attitude Profiling

VML (Virtual Machine Language) has been used as the sequencing flight software on over a dozen JPL deep-space missions, most recently flying on GRAIL and JUNO. In conjunction with the NASA SBIR entitled "Reactive Rendezvous and Docking Sequencer", VML version 3.0 has been enhanced to include object-oriented element organization, built-in queuing operations, and sophisticated matrix / vector operations. These improvements allow VML scripts to easily perform much of the work that formerly would have required a great deal of expensive flight software development to realize. Autonomous turning and tracking makes considerable use of new VML features. Profiles generated by flight software are managed using object-oriented VML data constructs executed in discrete time by the VML flight software. VML vector and matrix operations provide the ability to calculate and supply quaternions to the attitude controller flight software which produces torque requests. Using VML-based attitude planning components eliminates flight software development effort, and reduces corresponding costs. In addition, the direct management of the quaternions allows turning and tracking to be tied in with sophisticated high-level VML state machines. These state machines provide autonomous management of spacecraft operations during critical tasks like a hypothetic Mars sample return rendezvous and docking. State machines created for autonomous science observations can also use this sort of attitude planning system, allowing heightened autonomy levels to reduce operations costs. VML state machines cannot be considered merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. The state machine approach enabled by VML 3.0 is progressing toward flight capability with a wide array of applicable mission activities.

VML (Virtual Machine Language)↗
NASA NTRS2022

Flow Visualization, Heat Transfer, and Critical Heat Flux of Flow Boiling in Earth Gravity with Saturated Liquid-Vapor Mixture Inlet Conditions – In Preparation for Experiments Onboard the International Space Station

This study investigates flow boiling of n-Perfluorohexane with saturated two-phase mixture inlet in a rectangular channel of dimensions 114.6-mm heated length, 2.5-mm width, and 5 mm-height. The experiments were performed as part of the Mission Sequence Testing of the Flow Boiling and Condensation Experiment’s (FBCE) Flow Boiling Module (FBM) in the vertical upflow configuration in Earth gravity using the same experimental system that was launched to the International Space Station (ISS) in August 2021. The operating parameters varied are heating configuration (single- and double-sided), mass velocity (380 – 2400 kg/m2s), inlet quality (0.011 – 0.519), and inlet pressure (120 – 179 kPa). High-speed video photographs are presented to explain the two-phase flow patterns within the channel’s heated length. Flow patterns are constituted by low-density and high-density fronts moving along the channel, with the high-density fronts gradually reducing in length due to evaporation. Heat transfer results in terms of flow boiling curves, streamwise wall temperature profiles, streamwise heat transfer coefficient profiles, and average heat transfer coefficients are presented and trends discussed. CHF data from the present experiments are combined with prior databases to compile a consolidated FBCE-CHF database for saturated inlet to expand the ranges of operating conditions and include other flow orientations in Earth gravity. Experimental CHF trends are also discussed. The interfacial lift-off model shows a good CHF predictive accuracy evidenced by a mean absolute error of 11.97% for this consolidated database after constraining it to mass velocities greater than or equal to 500 kg/m2s. Finally, this study confirmed reliability of the upcoming ISS experiments for saturated inlet conditions and the collected Earth-gravity data will be compared to ISS microgravity data.

Flow boiling↗
NASA NTRS2022

Should’ve Could’ve: Progress in the Systems Engineering of the Mars2020 On-Board Planner

Mars rover operations has traditionally controlled behavior using meticulously compiled, so-called “Master” sequences that enforce deterministic timing and ordering of activities. While the approach is effective at managing risk and complexity, it can also be inefficient. Extended operations of the Mars2020 rover envisions a fundamentally different scheduling and execution approach. Atomic activities are constrained by mission operators in time, resource usage, and a structure of dependencies. The rover flight software will create and re-create schedules, responding to available energy, data volume, actual activity durations and execution status, observed temperatures, and other on-board state. Schedules are expected to change substantially in the course of execution. The solution space is prohibitively large and probabilistic in nature. A range of emergent behavior is accessible depending on the interaction between actual on-board state and a given formulation of constraints. For years, the specification and implementation of this capability have been considered and refined, as testing and analysis have mapped the contours of the system. Many concepts that could have been adopted were rejected, and in some cases, emergent properties have been exposed and beaten back with approaches to steer the behavior. This paper discusses some of the design history and underlying reasoning in the systems engineering of the first autonomous activity planner on Mars.

Kuhn, Stephen R↗
NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗
NASA NTRS1993

Magellan attitude control mission operations

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

Dukes, Eileen M.↗
NASA NTRS2006

Feasibility Study of Jupiter Icy Moons Orbiter Permanent Magnet Alternator Start Sequence

The Jupiter Icy Moons Orbiter (JIMO) mission was a proposed, (recently cancelled) long duration science mission to study three moons of Jupiter: Callisto, Ganymede, and Europa. One design of the JIMO spacecraft used a nuclear heat source in conjunction with a Brayton rotating machine to generate electrical power for the electric thrusters and the spacecraft bus. The basic operation of the closed cycle Brayton system was as follows. The working fluid, a heliumxenon gas mixture, first entered a compressor, then went through a recuperator and hot-side heat exchanger, then expanded across a turbine that drove an alternator, then entered the cold-side of the recuperator and heat exchanger and finally returned to the compressor. The spacecraft was to be launched with the Brayton system off-line and the nuclear reactor shut down. Once the system was started, the helium-xenon gas would be circulated into the heat exchangers as the nuclear reactors were activated. Initially, the alternator unit would operate as a motor so as to drive the turbine and compressor to get the cycle started. This report investigated the feasibility of the start up sequence of a permanent magnet (PM) machine, similar in operation to the alternator unit, without any position or speed feedback sensors ("sensorless") and with a variable load torque. It is found that the permanent magnet machine can start with sensorless control and a load torque of up to 30 percent of the rated value.

Kenny, Barbara H.↗
NASA NTRS2012

Orbit Transfers for Dawn's Vesta Operations : Navigation and Mission Design Experience

Dawn, a mission belonging to NASA's Discovery Program, was launched on September 27, 2007 to explore main belt asteroids in order to yield insights into important questions about the formation and evolution of the solar system. From July of 2011 to August of 2012, the Dawn spacecraft successfully returned valuable science data, collected during the four planned mapping orbits at its first target asteroid, Vesta. Each mapping orbit was designed to enable a different set of scientific observations. Such a mission would have been impossible without the low thrust ion propulsion system (IPS). Maneuvering a spacecraft using only the IPS for the transfers between the mapping orbits posed many technical challenges to Dawn's flight team at NASA's Jet Propulsion Laboratory. Each transfer needs a robust plan that accounts for uncertainties in maneuver execution, orbit determination, and physical characteristics of Vesta. This paper discusses the mission design and navigational experience during Dawn's Vesta operations. Topics include requirements and constraints from Dawn's science and spacecraft teams, orbit determination and maneuver design and building process for transfers, developing timelines for thrust sequence build cycles, and the process of scheduling very demanding coverage with ground antennae at NASA's Deep Space Network.

low thrust↗
NASA NTRS1994

(abstract) Automated Constraint Checking of Spacecraft Command Sequences

Making certain that spacecraft command sequences do not violate any constraints is often tedious and expensive in terms of both personnel and software development. To reduce this cost, we have pursued the development of a flexible system for specifying models of spacecraft behavior in response to commands as well as constraints on that behavior. The potential need for modeling complex spacecraft behavior required that the system be designed to be usable both on a conventional workstation and a parallel supercomputer. Finally, it needed to be intuitive enough for the the intended mission operations users to easily design sets of rules and models to automate tedious, resource-consuming constraint checking of commands. We have defined a Specification And Verification Environment (SAVE) for spacecraft flight rules.

automation spacecraft command sequences constraint↗
NASA NTRS1982

Use of the Charge/Discharge (C/D) ratio to aument voltage limit (V sub T) charge control in the ERBS spacecraft

A 50-ampere hour nickel cadmium cell test pack was operated in a power profile simulating the orbit of the Earth Radiation Budget Satellite (ERBS). The objective was to determine the ability of the temperature compensated voltage limit (V sub T) charge control system to maintain energy balance in the half sine wave-type current profile expected of this mission. The four-cell pack (50 E) was tested at the Naval Weapons Support Center (NWSC) at Crane, Indiana. The ERBS evaluation test consisted of two distinct operating sequences, each having a specific purpose. The first phase was a parametric test involving the effect of V sub T level, temperature, and Beta angle on the charge/discharge (C/D) ratio, an indicator of the amount of overcharge. The second phase of testing made use of the C/D ratio limit to augment the V sub T charge limit control. When the C/D limit was reached, the current was switched from the taper mode to a C/67 (0.75 A) trickle charge. The use of an ampere hour integrator limiting the overcharge to a C/67 rate provided a fine tuning of the charge control technique which eliminated the sensitivity problems noted in the initial operating sequence.

Halpert, G.↗
NASA NTRSDate not supplied

Development of Space Mission Integrated Operations Scenarios

Integrated Operations Scenarios (IOS) describe nominal operations planned for a space mission. Operational scenarios are key to an operations concept, as they help identify issues and drivers on the operations system. This paper covers the tools, processes, and inputs that feed into an IOS product, and how IOS iterations during a mission lifecycle can buy down operational risks. A case used for this paper is nominal operations for an initial crewed Artemis mission that includes cross-program sequence of tasks required to accomplish end to end functions from launch through transit, on-orbit operations, to safely return to Earth. An IOS product serves as a reference for discussions during requirements development, task and risk analyses, concept of operations development, and as foundation to prepare space mission flight plans.

integrated operations scenarios↗
NASA NTRS2000

The Spacecraft Materials Selector: An Artificial Intelligence System for Preliminary Design Trade Studies, Materials Assessments, and Estimates of Environments Present

Institutions need ways to retain valuable information even as experienced individuals leave an organization. Modern electronic systems have enough capacity to retain large quantities of information that can mitigate the loss of experience. Performance information for long-term space applications is relatively scarce and specific information (typically held by a few individuals within a single project) is often rather narrowly distributed. Spacecraft operate under severe conditions and the consequences of hardware and/or system failures, in terms of cost, loss of information, and time required to replace the loss, are extreme. These risk factors place a premium on appropriate choice of materials and components for space applications. An expert system is a very cost-effective method for sharing valuable and scarce information about spacecraft performance. Boeing has an artificial intelligence software package, called the Boeing Expert System Tool (BEST), to construct and operate knowledge bases to selectively recall and distribute information about specific subjects. A specific knowledge base to evaluate the on-orbit performance of selected materials on spacecraft has been developed under contract to the NASA SEE program. The performance capabilities of the Spacecraft Materials Selector (SMS) knowledge base are described. The knowledge base is a backward-chaining, rule-based system. The user answers a sequence of questions, and the expert system provides estimates of optical and mechanical performance of selected materials under specific environmental conditions. The initial operating capability of the system will include data for Kapton, silverized Teflon, selected paints, silicone-based materials, and certain metals. For situations where a mission profile (launch date, orbital parameters, mission duration, spacecraft orientation) is not precisely defined, the knowledge base still attempts to provide qualitative observations about materials performance and likely exposures. Prior to the NASA contract, a knowledge base, the Spacecraft Environments Assistant (SEA,) was initially developed by Boeing to estimate the environmental factors important for a specific spacecraft mission profile. The NASA SEE program has funded specific enhancements to the capability of this knowledge base. The SEA qualitatively identifies over 25 environmental factors that may influence the performance of a spacecraft during its operational lifetime. For cases where sufficiently detailed answers are provided to questions asked by the knowledge base, atomic oxygen fluence levels, proton and/or electron fluence and dose levels, and solar exposure hours are calculated. The SMS knowledge base incorporates the previously developed SEA knowledge base. A case history for previous flight experiment will be shown as an example, and capabilities and limitations of the system will be discussed.

Pippin, H. G.↗