Results for “Streamlined quality” — Page 4

NASA NTRS2001

Space Shuttle Navigation in the GPS Era

The Space Shuttle navigation architecture was originally designed in the 1970s. A variety of on-board and ground based navigation sensors and computers are used during the ascent, orbit coast, rendezvous, (including proximity operations and docking) and entry flight phases. With the advent of GPS navigation and tightly coupled GPS/INS Units employing strapdown sensors, opportunities to improve and streamline the Shuttle navigation process are being pursued. These improvements can potentially result in increased safety, reliability, and cost savings in maintenance through the replacement of older technologies and elimination of ground support systems (such as Tactical Air Control and Navigation (TACAN), Microwave Landing System (MLS) and ground radar). Selection and missionization of "off the shelf" GPS and GPS/INS units pose a unique challenge since the units in question were not originally designed for the Space Shuttle application. Various options for integrating GPS and GPS/INS units with the existing orbiter avionics system were considered in light of budget constraints, software quality concerns, and schedule limitations. An overview of Shuttle navigation methodology from 1981 to the present is given, along with how GPS and GPS/INS technology will change, or not change, the way Space Shuttle navigation is performed in the 21 5 century.

Goodman, John L.↗

NASA NTRS2022

Ideas on the NASA Senior Review and Mission Extension Process

Extended mission budgets fund a significant part of our community, particularly young scientists who in a relatively short time are exposed to a broad range of experiences and opportunities available in space science and other STEM fields. In particular, mission-funded science offers a relatively stable funding stream that enables meaningful mentoring efforts and interactions, including apprenticeships ranging from project management, to mission operations, to data processing and analysis, to hardware and software development, to STEM-related education and outreach. It moreover provides professional contacts that fuel diversity in mission leadership and in the science and technical workforce at-large. Last but not least, it sustains the scientific productivity of NASA’s missions, which constitute major national investments meriting their full exploitation. Budgets cuts, however, are exercising pressure on the science and operations of the extended mission fleet despite being only a small portion of the overall Division budget. The history of Heliophysics has demonstrated that maintaining the operation of missions beyond their prime phase invariably leads to a much deeper knowledge of the original mission science goals, together with new applications often not foreseen during their original design. Their operation as part of the Heliophysics System Observatory (HSO)---a coordinated, 1eliophysics, multipoint observing system of the heliosphere, is a prime example. Some of the first activities undertaken by the Parker Solar Probe and Solar Orbiter missions required recreating the larger context of their new observations by using the diversity of HSO mission capabilities. The marginal cost of maintaining this valuable, working science resource, in the form of both continuing high quality data access and expertise, is small compared to the cost of the original missions or of new missions to achieve similar objectives, making the operation of extended missions, the best “science per dollar” investment in Heliophysics. We argue that reducing both extended mission operations and science budgets will have a ripple effect across the community, including reducing employment and training opportunities for young scientists, to lowering the quality/impact of the Heliophysics Systems Observatory. Instead, we suggest that the proposal process for mission extension should be re-examined. We offer several ideas for reducing costs of extended missions toward maintaining science output and streamlining the management process.

A. Vourlidas↗

NASA NTRS2015

Dissemination of Earth Remote Sensing Data for Use in the NOAA/NWS Damage Assessment Toolkit

The National Weather Service has developed the Damage Assessment Toolkit (DAT), an application for smartphones and tablets that allows for the collection, geolocation, and aggregation of various damage indicators that are collected during storm surveys. The DAT supports the often labor‐intensive process where meteorologists venture into the storm‐affected area, allowing them to acquire geotagged photos of the observed damage while also assigning estimated EF‐scale categories based upon their observations. Once the data are collected, the DAT infrastructure aggregates the observations into a server that allows other meteorologists to perform quality control and other analysis steps before completing their survey and making the resulting data available to the public. In addition to in‐person observations, Earth remote sensing from operational, polar-orbiting satellites can support the damage assessment process by identifying portions of damage tracks that may be missed due to road limitations, access to private property, or time constraints. Products resulting from change detection techniques can identify damage to vegetation and the land surface, aiding in the survey process. In addition, higher resolution commercial imagery can corroborate ground‐based surveys by examining higher‐resolution commercial imagery. As part of an ongoing collaboration, NASA and NOAA are working to integrate near real‐time Earth remote sensing observations into the NOAA/NWS Damage Assessment Toolkit. This presentation will highlight recent developments in a streamlined approach for disseminating Earth remote sensing data via web mapping services and a new menu interface that has been integrated within the DAT. A review of current and future products will be provided, including products derived from MODIS and VIIRS for preliminary track identification, along with conduits for higher‐resolution Landsat, ASTER, and commercial imagery as they become available. In addition to tornado damage assessments, the team is also investigating the use of near real‐time imagery for identifying hail damage to vegetation, which also results in large swaths of damage, particularly in the central United States during the peak growing season months of June, July, and August. This presentation will present an overview of recent activities, challenges and successes, best practices, and opportunities for future work and collaboration

Molthan, Andrew↗

NASA NTRS2017

Limiting Data Friction by Reducing Data Download Using Spatiotemporally Aligned Data Organization Through STARE

Current data processing practice limits the volume and variety of relevant geoscience data that can practically be applied to important problems. File archives in centralized data centers are the principal means by which Earth Science data are accessed. This approach, however, requires laborious search, retrieval, and eventual customization/adaptation for the data to be used. Such fractionation makes it even more difficult to share outcomes, i.e. research artifacts and data products, hampering reusability and repeatability, since end users generally have their own research agenda and preferences as well as scarce resources. Thus, while finding and downloading data files from central data centers are already costly for end users working in their own field, using data products from other disciplines rapidly becomes prohibitive. This curtails scientific productivity, limits avenues of study, and endangers quality and reproducibility. The Spatio-Temporal Adaptive Resolution Encoding (STARE) is a unifying scheme that facilitates the indexing, access, and fusion of diverse Earth Science data. STARE implements an innovative encoding of geo-spatiotemporal information, originally developed for aligning datasets with diverse spatiotemporal characteristics in an array database. The spatial component of STARE recursively quadfurcates a root polyhedron, producing a hierarchical scheme for addressing geographic locations and regions. The temporal component of STARE uses conventional date-time units as an indexing hierarchy. The additional encoding of spatial and temporal resolution information in STARE enables comparisons and conditional selections across diverse datasets. Moreover, spatiotemporal set-operations, e.g. union and intersection, are mapped to efficient integer operations with STARE. Applied to existing data models (point, grid, spacecraft swath) and corresponding granules, STARE indexes provide a streamlined description usable as geo-spatiotemporal metadata. When coupled with large scale, distributed hardware and software, STARE-based data access reduces pre-analysis data preparation costs by offering a convenient means to align different datasets spatiotemporally without specialized effort in parallel computing or distributed data management.

Kuo, Kwo-Sen↗

NASA NTRSDate not supplied

MARS 2020 Backshell Radiative Heating Measurement and Shock Tube Verification

In February 2021, the Perseverance rover was brought to the surface of Mars by the Mars 2020 mission. A feature of the Mars 2020 capsule was instrumentation to measure its entry, descent and landing (EDL) with the so-called Mars EDL Instrumentation 2 (MEDLI2) [1]. The MEDLI2 introduced, among other things, backshell instrumentation, including a broadband radiometer. The radiometer was mounted on the leeside of the vehicle next to thermocouple plugs and a heat flux gauge. The data returned by the leeside MEDLI2 heat flux gauge is largely analogous to that measured by the COMARS gauge flown on the ExoMars Schiaparelli [2] entry in that it is measuring heat flux in an area that is entirely dominated by radiative heating. The COMARS measurement provided excellent validation of backshell radiative heating models for Mars entry, albeit at a limited number of points [3]. The MEDLI2 heat flux gauge measurement effectively confirmed the quality of the prediction, extended over the full trajectory, as will be presented in this paper. The MEDLI2 radiometer,however, was blocked by ablation products and suffered a loss of half of its signal. The second backshell heat flux gauge installed on the windside of the vehicle was also well predicted, although the heating had both radiative and convective contributions. It was desired to reproduce the conditions of the Mars 2020 entry via ground testing in the Electric Arc Shock Tube (EAST) at NASA Ames. Tests to verify stagnation line heating were previously reported in EAST, confirming the presence of shock layer radiation as the major discrepancy in heatshield temperature modelling [4]. Therefore, tests for stagnation line heating were not repeated. Instead, the shock tube informed bias method [5, 6] was used to identify test conditions that may produce similarity to streamlines that pass around the backside of the vehicle and are responsible for the radiation observed at the two heat flux gauge locations. This method was used to identify a range of velocities and densities in the shock tube that are relevant for confirming the radiative environment encountered. This paper reports the results obtained in the 10 cm diameter EAST shock tube, corresponding to later trajectory points at ambient pressures of 1.1-2.0 Torr and velocities from 1.2-3.5 km/s. The test series employed two primary diagnostics: emission spectroscopy and tunable diode laser absorption spectroscopy (TDLAS). The emission spectroscopy performed broadband measurements of the radiative emission of the 4.3 and 2.7 m bands of CO2 at flight similar conditions, obtaining both spectral and spatial data corresponding to the relaxation behind the shock front. The TDLAS measured the absorption of several lines of CO and CO2 and obtains species number densities and temperatures as a function of time behind the shock front. This paper will review highlights of this test series and analyses of the emission and absorption data. While the datasets generally show good agreement with predictions, a few discrepancies and items for additional investigation are identified and will be discussed

Brett A Cruden↗

NASA NTRS2019

Discovery and Vetting of Exoplanets. I. Benchmarking K2 Vetting Tools

We have adapted the algorithmic tools developed during the Kepler mission to vet the quality of transit-like signals for use on the K2 mission data. Using the four sets of publicly available light curves at MAST, we produced a uniformly vetted catalog of 772 transiting planet candidates from K2 as listed at the NASA Exoplanet Archive in the K2 Table of Candidates. Our analysis marks 676 of these as planet candidates and 96 as false positives. All confirmed planets pass our vetting tests. Sixty of our false positives are new identifications, effectively doubling the overall number of astrophysical signals mimicking planetary transits in K2 data. Most of the targets listed as false positives in our catalog show either prominent secondary eclipses, transit depths suggesting a stellar companion instead of a planet, or significant photocenter shifts during transit. We packaged our tools into the open-source, automated vetting pipeline Discovery and Vetting of Exoplanets (DAVE), designed to streamline follow-up efforts by reducing the time and resources wasted observing targets that are likely false positives. DAVE will also be a valuable tool for analyzing planet candidates from NASA's TESS mission, where several guest-investigator programs will provide independent light-curve sets—and likely many more from the community. We are currently testing DAVE on recently released TESS planet candidates and will present our results in a follow-up paper.

Kostov, Veselin B.↗

NASA NTRS1994

Background noise levels measured in the NASA Lewis 9- by 15-foot low-speed wind tunnel

The acoustic capability of the NASA Lewis 9 by 15 Foot Low Speed Wind Tunnel has been significantly improved by reducing the background noise levels measured by in-flow microphones. This was accomplished by incorporating streamlined microphone holders having a profile developed by researchers at the NASA Ames Research Center. These new holders were fabricated for fixed mounting on the tunnel wall and for an axially traversing microphone probe which was mounted to the tunnel floor. Measured in-flow noise levels in the tunnel test section were reduced by about 10 dB with the new microphone holders compared with those measured with the older, less refined microphone holders. Wake interference patterns between fixed wall microphones were measured and resulted in preferred placement patterns for these microphones to minimize these effects. Acoustic data from a model turbofan operating in the tunnel test section showed that results for the fixed and translating microphones were equivalent for common azimuthal angles, suggesting that the translating microphone probe, with its significantly greater angular resolution, is preferred for sideline noise measurements. Fixed microphones can provide a local check on the traversing microphone data quality, and record acoustic performance at other azimuthal angles.

Woodward, Richard P.↗

NASA NTRS2005

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗

NASA NTRS2004

The Space Technology 5 Avionics System

The Space Technology 5 (ST5) mission is a NASA New Millennium Program project that will validate new technologies for future space science missions and demonstrate the feasibility of building launching and operating multiple, miniature spacecraft that can collect research-quality in-situ science measurements. The three satellites in the ST5 constellation will be launched into a sun-synchronous Earth orbit in early 2006. ST5 fits into the 25-kilogram and 24-watt class of very small but fully capable spacecraft. The new technologies and design concepts for a compact power and command and data handling (C&DH) avionics system are presented. The 2-card ST5 avionics design incorporates new technology components while being tightly constrained in mass, power and volume. In order to hold down the mass and volume, and quali& new technologies for fUture use in space, high efficiency triple-junction solar cells and a lithium-ion battery were baselined into the power system design. The flight computer is co-located with the power system electronics in an integral spacecraft structural enclosure called the card cage assembly. The flight computer has a full set of uplink, downlink and solid-state recording capabilities, and it implements a new CMOS Ultra-Low Power Radiation Tolerant logic technology. There were a number of challenges imposed by the ST5 mission. Specifically, designing a micro-sat class spacecraft demanded that minimizing mass, volume and power dissipation would drive the overall design. The result is a very streamlined approach, while striving to maintain a high level of capability, The mission's radiation requirements, along with the low voltage DC power distribution, limited the selection of analog parts that can operate within these constraints. The challenge of qualifying new technology components for the space environment within a short development schedule was another hurdle. The mission requirements also demanded magnetic cleanliness in order to reduce the effect of stray (spacecraft-generated) magnetic fields on the science-grade magnetometer.

Speer, Dave↗

NASA NTRSDate not supplied

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA NTRSDate not supplied

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA NTRS2005

A NASA Strategy for Leveraging Emerging Launch Vehicles for Routine, Small Payload Missions

Orbital flight opportunities for small payloads have always been few and far between, and then on February 1, 2002, the situation got worse. In the wake of the loss of the Columbia during STS- 107, changing NASA missions and priorities led to the termination of the Shuttle Small Payloads Projects, including Get-Away Special, Hitcbker, and Space Experiment Module. In spite of the limited opportunities, long queue, and restrictions associated with flying experiments on a man-rated transportation system; the carriers provided a sustained, high quality experiment services for education, science, and technology payloads, and was one of the few games in town. Attempts to establish routine opportunities aboard existing ELVs have been unsuccessful, as the cost-per-pound on small ELVs and conflicts with primary spacecraft on larger vehicles have proven prohibitive. Ths has led to a backlog of existing NASA-sponsored payloads and no prospects or plans for fbture opportunities within the NASA community. The prospects for breaking out of this paradigm appear promising as a result of NASA s partnership with DARPA in pursuit of low-cost, responsive small ELVs under the Falcon Program. Through this partnership several new small ELVs, providing 1000 lbs. to LEO will be demonstrated in less than two years that promise costs that are reasonable enough that NASA, DoD, and other sponsors can once again invest in small payload opportunities. Within NASA, planning has already begun. NASA will be populating one or more of the Falcon demonstration flights with small payloads that are already under development. To accommodate these experiments, Goddard s Wallops Flight Facility has been tasked to develop a multi-payload ejector (MPE) to accommodate the needs of these payloads. The MPE capabilities and design is described in detail in a separately submitted abstract. Beyond use of the demonstration flights however, Goddard has already begun developing strategies to leverage these new ELVs as elements of a larger system designed to provide routine, low-cost end-to-end services for small science, Exploration, and education payloads. The plan leverages the management approaches of the successful Sounding Rocket Program and Shuttle Small Payloads Projects. The strategy consists of using a systems implementation approach of elements, including 1) Falcon ELVs, 2) advanced launch site technologies and processes, 3) suite of experiment carriers accommodating different mission requirements, 4) streamlined integration and test operations, 5 ) experiment brokering and management, and 6) standardized, distributed payload operations. The envisioned suite of carriers includes the MPE, a standard interface experiment carrier, and potentially a reentry fieeflyer experiment carrier. Key to the success of this strategy is standard experiment interfaces within the carriers to limit mission- unique tasks, establishmg and managing a program of scheduled reoccurring flights rather than discrete missions, and streamlined, centralized implementation of the elements. These individual elements are each under development and Goddard will demonstrate the overall system strategy low-cost small payload missions on the initial Falcon demonstration launches from Wallops. goal is to show that this model should be converted to a sustained NASA program supporting science, technology, and education, with annual flight opportunities. The paper will define in detail the various elements of the overall program, as well as provide status, philosophy, and strategy for the program that will hopefully once-and-for-all provide low-cost, routine access to space for the small payloads community.

Underwood, Bruce E.↗