Search NASA⌕ Search

Engineering topics

Bindschadler, Duane L.

Publications and source records attributed to Bindschadler, Duane L..

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

Benefits and Challenges of CCSDS File Delivery Protocol as Applied to Europa Clipper

—This paper describes the use of the Consultative Committee for Space Data Systems (CCSDS) File Delivery Protocol (CFDP) on the Europa Clipper mission for both uplink and downlink of files. It includes an overview of CFDP, the history of why CFDP was chosen, how it benefits mission operations, some of the mission scenarios that stress CFDP, operability aspects, the best practices that Clipper adopted from other missions and some of the technical challenges with implementation, and verification and validation. The benefits to mission operations accrue because CFDP reduces the need for manual management of file transfer, including retransmission of missing data, and deletion of files only after confirmation of receipt by the ground. The challenges occur because CFDP is a round-trip protocol – it requires messages in both directions to complete a file transfer, and because it uses timers to ensure that control messages are resent if needed to prevent transactions from going stale. Any situations where communication is restricted to a single direction, interrupted, reordered, or backlogged can pose a challenge. There are also implementation challenges. Europa Clipper is the first mission at the Jet Propulsion Laboratory (JPL) to adopt class 2, fully acknowledged, CFDP for both uplink and downlink. The implementation needed new software, requirements and operational procedures. The experience of the Applied Physics Laboratory (APL) with CFDP from their previous missions was crucial to success for Europa Clipper. Because CFDP relies on timers and messages travel in both directions, verification and validation (V&V) requires new approaches. For certain scenarios, a live ground system talking to a live flight system with realistic simulated one-way light times, data rates and data outages must be used.

Albers, Joshua↗
NASA NTRS2018

Operability Engineering for the Europa Clipper Mission: Formulation Phase Results and Lessons

Operability is an important factor in both success and cost of space missions, but is difficult to quantify, and can suffer if not considered as part of early formulation and design. The Europa Clipper mission has taken a deliberate approach to infusing operability into the concepts and designs since early in the formulation phase. This paper reports on that approach to operability and the results thus far, as the Europa Clipper mission approaches its Preliminary Design Review. Definitions for operability and its various aspects are presented along with a description of the engineering and organizational approach taken to infusing operability into designs. A number of examples of operability requirements are shown, and key examples of trade studies and design decisions are described, along with influence on outcomes motivated by operability considerations. We find that support from management, empowerment of a cross-discipline Operability Working Group, consistent tracking of operability aspects over time, and broad infusion and participation in operability considerations are all significant factors in implementing operability. In particular, thoughtful and deliberate consideration of operability criteria has led to design decisions that include proper consideration of concerns related to the mission operations phase, and seem likely to provide better science results and mission outcomes.

Huh, Shin M.↗
NASA NTRS2016

A Structured, Model-Based Systems Engineering Methodology for Operations System Design

Two widely accepted techniques for lowering the cost and risk of developing systems are (1) the use of a defined systems engineering (SE) process or methodology and (2) the reuse of existing (previously built) system components. The first technique is represented, for example, in materials published by NASA (e.g., NASA Systems Engineering Handbook) or by professional societies such as INCOSE (International Council on Systems Engineering). Well-formed SE techniques provide value by establishing the proper scope of the system (e.g., requirements), and by identifying and resolving problems relatively early in project lifecycles, when fixes are less expensive. The second technique (reuse) is applied most commonly to hardware and software; it seeks to avoid replicating design and implementation costs while also reducing risk by placing proven capabilities into operational use. In this paper, we outline a methodology combining these two techniques and extending reuse beyond hardware and software to foundational aspects of a Mission Operation System’s (MOS) design. We describe the system design artifacts that result (e.g., requirements, design documentation), as well as the reusable patterns and elements of the design, and their interrelationships. This approach is enabled by model-based systems engineering (MBSE) techniques and tools and is currently available in SysML form as a plug-in to MagicDraw. Additionally, usage of a rigorous MBSE approach allows for training materials and tutorials to be packaged within the overall model itself. The results of such an approach include decreased cost and risk during the design phase, improved ability of the MOS development team to investigate trade spaces and identify impacts to important flight-ground trade studies. Such results extend into decreased costs and risk in later phases due to improved design, decreased need for late fixes or development of "glue-ware" or scripts to fill unanticipated gaps in functionality, and improved ability to identify and plan testing and other validation activities. Finally, lower operational costs can be expected, both due to improved quality of the MOS, increased ease of maintaining updated knowledge of system configuration, and the fact that training and procedural materials are also updated at the same time as accepted system changes.

Bindschadler, Duane L.↗
NASA NTRS2012

Timeline-Based Mission Operations Architecture: An Overview

Some of the challenges in developing a mission operations system and operating a mission can be traced back to the challenge of integrating a mission operations system from its many components and to the challenge of maintaining consistent and accountable information throughout the operations processes. An important contributing factor to both of these challenges is the file-centric nature of today's systems. In this paper, we provide an overview of these challenges and argue the need to move toward an information-centric mission operations system. We propose an information representation called Timeline as an approach to enable such a move, and we provide an overview of a Timeline-based Mission Operations System architecture.

Chung, Seung H.↗
NASA NTRS2012

Principles to Products: Toward Realizing MOS 2.0

This is a report on the Operations Revitalization Initiative, part of the ongoing NASA-funded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element...) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.

AMMOS↗
NASA NTRS2010

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗
NASA NTRS2008

Web Based Tool for Mission Operations Scenarios

A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum visibility across the project. One key aspect is that the tool was built for a scenario process that accounts for stakeholder input, review, comment, and concurrence. By creating well-designed opportunities for stakeholder input and concurrence and by making the scenario content easily accessible to all project personnel, we maximize the opportunities for stakeholders to both understand and agree on the concepts for how their mission is to be carried out.

Boyles, Carole A.↗
NASA NTRS2008

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

MOS↗
NASA NTRS1994

Venus' center of figure-center of mass offset

Magellan altimetry data reveal that the center of figure (CF) of Venus is displaced approximately 280 m from its center of mass (CM) toward 4.4 deg S, 135.8 deg E, a location in Aphrodite Terra. This offset is smaller than those of other terrestrial planets but larger than the estimated error, which is no more than a few tens of meters. We examine the possibility that the CF-CM offset is related to specific geologic provinces on Venus by deriving three simple models for the offset: a thick-crust model, a hotspot model, and a thick-lithosphere model. The offset caused by a region of thick crust depends upon the region's extent, the crust-mantle density contrast, and the thickness of excess crust. A hotspot-related offset depends on the extent of the thermally anomalous region and the magnitude of the thermal anomaly. Offset due to a region of thick lithosphere depends upon the extent of the region, the average temperature contrast across the lithosphere, and the amount of excess lithosphere. We apply the three models to Venus plateau-shaped highlands, volcanic rises, and lowlands, respectively, in an attempt to match the observed CF-CM offset location and magnitude. The influence of most volcanic rises and of Ishtar Terra on the CF-CM offset must be quite small if we are to explain the direction of the observed offset. The lack of influence of volcanic rises can be explained if the related thermal anomalies are limited to a few hundred degrees or less and are plume-shaped (i.e., characterized by a flattened sublithospheric `head' with a narrow cylindrical feeder `tail'). The unimportance of Ishtar Terra is most easily explained if it lies atop a significant mantle downwelling.

Bindschadler, Duane L.↗
NASA NTRS1994

Characteristics of finite amplitude stationary gravity waves in the atmosphere of Venus

This paper extends the study of stationary gravity waves generated near the surface of Venus reported previously by Young et al. to include finite amplitude effects associated with large amplitude waves. Waves are forced near the surface of Venus by periodic forcing. The height-dependent profiles of static stability and mean wind in the Venus atmosphere play a very important role in the evolution of the nonlinear behavior of the waves, just as they do in the linear wave solutions. Certain wave properties are qualitatively consistent with linear wave theory, such as wave trapping, resonance, and wave evanescence for short horizontal wavelenghts. However, the finite amplitude solutions also exhibit many other interesting features. In particular, for forcing amplitudes representative of those that could be expected in mountainous regions such as Aphrodite Terra, waves generated near the surface can reach large amplitudes at and above cloud levels, with clear signatures in the circulation pattern. At still higher levels, the waves can reach large enough amplitude to break, unless damping rates above the clouds are sufficient to limit wave amplitude growth. Well below cloud levels the waves develop complex flow patterns as the result of finite amplitude wave-wave interactions, and waves are generated having considerably shorter horizontal wavelenghts than that associated with the forcing near the surface. Nonlinear interactions can excite waves that are resonant with the background wind and static stability fields even when the primary surface forcing does not, and these waves can dominate the wave spectrum near cloud levels. A global map of Venus topographic slopes derived from Magellan altimetry data shows that slopes of magnitude comparable to or exceeding that used to force the model are ubiquitous over the surface.

Young, Richard E.↗
NASA NTRS1994

Spatial and temporal relations between coronae and extensional belts, northern Lada Terra, Venus

Preliminary studies of the distribution of coronae and volcanic rises on Venus show that many of these features tend to cluster along zones of rifting and extension. The plains north of Lada Terra are crossed by two such extensional belts. Each belt is composed of grabens, ridges, faults, volcanic flows, coronae and coronalike features. The longer and more prominent belt is the NW trending Alpha-Lada extensional belt, which is over 6000 km long and 50-200 km wide, and includes the coronae Eve, Tamfana, Carpo, Selu, Derceto, Otygen, and an unnamed corona south of Otygen. The second belt is the NNE trending Derceto-Quetzalpetlatl extensional belt, which is about 2000 km long and in places over 300 km wide, and includes the coronae Sarpanitum, Eithinoha, and Quetzalpetlatl. The two belts intersect at the 1600 x 600 km wide Derceto volcanic plateau. It is apparent that deformation along the two belts overlapped in time, though deformation along the Alpha-Lada extensional belt probably continued after the deformation along the Derceto-Quetzalpetlatl extensional belt terminated. In certain areas, volcanism originated in grabens within the extensional belts, whereas in other areas, such as in Eve, Selu, Derceto, and Quetzalpetlatl, volcanism originated in the coronae and flowed into the lower parts of the extensional belts. Regional extension has affected the evolution of all the coronae at some stage of their development. Regional deformation occurred before the initiation of Derceto and Eithinoha of their development. Regional deformation occurred before the initiation of Derceto and Eithinoha and after the initiation of Carpo, Tamfana, Otygen, and Sarpanitum. It is thus unlikely that coronae formation along the belts is solely a consequence of the regional extension, and it is also unlikely that regional extension has been caused solely by the coronae. No corona along the belts was formed subsequent to the cessation of the regional extension. We therefore suggest that the regional extension and the coronae are interrelated. Some of the coronae may have determined the location of the surface expression of the regional extension, whereas the locations of other coronae may have been influenced by the concentration of regional extensional stresses.

Baer, Gidon↗
NASA NTRS1993

The spatial distribution of coronae and related features on Venus

Coronae are large quasi-circular geologica features that are common on Venus. They appear to be the surface tectonic and volcanic expressions of mantle diapirs that have impinged on the underside of the venusian lithosphere. We have investigated the spatial distribution of 335 coronae and related features identified in Magellan radar data. It is more clustered than a Poisson distribution, with a statistical certainty of more than 99%. It is dominated by a single large cluster centered near the equator at about 245 deg longitude. The features are preferentially found at elevation and geoid values close to the planetary mean, with a paucity at both the highest and lowest levels of topgraphy and geoid. Some coronae appear aligned in quasi-linear chains. We attribute the clustering of coronae and related features to preferential formation of these features above regions of broad-scale mantle upwelling, and suggest that a major mantle upwelling underlies the one large cluster. We suggest that coronae are rare at the lowest elevations because these may be regions of mantle downwelling. The shortage of coronae at the highest elevations may result both from obscuration by other intense tectonism there and from suppression there of their formation by an unusually thick crust. Corona chains may be produced by enhanced passive mantle uplift below failed or incipient rifts.

Squyres, Steven W.↗
NASA NTRS1992

Geophysical models for the formation and evolution of coronae on Venus

The proposition that Venusian coronae form over sites of mantle upwelling and are modified by subsequent gravitational relaxation is examined using two geophysical models to determine whether and under what conditions these mechanisms can produce the topography and tectonics exhibited by coronae in the Magellan altimetry data and radar images. It is shown that mantle diapirism can produce the domical topography of novae, which may be coronae in the earliest stage of formation. The model stresses induced at the surface by a mantle diapir imply the formation of radially oriented extensional fracturing as observed in novae. The novae dimensions indicate that the diapirs responsible for them are smaller than about 100 km in radius and that the elastic lithosphere is less than 32 km thick. A flattened diapir at the top of the mantle is modeled and shown to result in plateaulike uplift. The volume of the flattened model diapir is similar to that of the spherical diapirs derived for novae.

Janes, Daniel M.↗
NASA NTRS1992

Styles of deformation in Ishtar Terra and their implications

Styles of deformation in Ishtar Terra are examined on the basis of imaging by the Magellan radar between the start of the mission and the start of the first superior conjunction hiatus. Ishtar Terra appears to have characteristics of both plume uplifts and convergent belts, and exhibits a great variety of tectonic and volcanic activity, with large variations within distances of only a few hundred kilometers. The most prominent terrain types are the volcanic plains of Lakshmi and the mountain belts of Maxwell, Freyja, and Danu. Ishtar demonstrates three general properties of Venus. Erosional degradation is absent, leading to the preservation of patterns resulting from past activity. Many surface features are the responses of a competent layer less than 10 km thick to flows of 100 km or broader scale. These broader scale flows are controlled mainly by heterogeneities in the mantle.

Kaula, William M.↗
NASA NTRS1992

Venus tectonics - An overview of Magellan observations

Magellan observations of the tectonic characteristics of highland regions on Venus are discussed with reference to competing theories for highland formation and evolution. Complex rigid terrain, or tessera, and the extent to which these elevated blocks of intensely deformed crust may be genetically related to highlands are then considered. Further, the tectonics of plains and lowland regions are examined, including deformation belts and coronae, and possible relations between such features and mantle dynamics. Implications of these observations for the global tectonics of Venus are discussed.

Solomon, Sean C.↗
NASA NTRS1992

Global distribution and characteristics of coronae and related features on Venus - Implications for origin and relation to mantle processes

The increased coverage and resolution of Magellan images and altimetry data have resulted in significant new identifications of coronae and coronalike features and more detailed information on corona morphology, topography, and distribution. The distribution of coronae and coronalike features in Magellan data are assessed in the light of the proposed hotspot origin of these features. The basic characteristics of coronae are then compared with other possible hotspot features on Venus (e.g., major volcanic shields and domelike highlands) in a first-order assessment of the implications of mantle plume-related features on Venus for interior convective processes.

Stofan, Ellen R.↗