Search NASA⌕ Search

SEARCH · Search NASA

Results for “standard user interface”

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
DOE OSTI2022

Development of an Open-source Alloy Selection and Lifetime Assessment Tool for Structural Components in CSP

Lack of sufficient data on high temperature mechanical and corrosion behavior of structural materials is a huge barrier in the technological maturity of current and future Concentrating Solar Power (CSP) technologies. Rapid development and selection of materials cannot be achieved by expensive and time-consuming acquisition of experimental data. The goal of the proposed work is development of an open-source alloy selection and lifetime prediction tool that will integrate validated physics-based models to describe influence of temperature, alloy composition, environment and component geometry (thickness) on mechanical and corrosion behavior of Ni and Fe-based alloys employed in molten salts/sCO 2 heat exchangers. This one-year project leveraged the extensive dataset on the creep\corrosion behavior of candidate materials generated at ORNL through past projects and input from current collaborations with industrial partners. Based on previous experience and the feedback provided by industry (Brayton Energy and Echogen), three candidate materials of interest, Ni-based alloys 740H, 282 and 625 and application-specific operating conditions (max. temperature of 730 °C and stress of 150 MPa) were identified for the heat exchanger. An extensive corrosion and creep dataset was assimilated for the relevant operating conditions and was supported by detailed characterization of about 100 metallographic cross-sections. The corrosion dataset consisted of scanning electron microscopy images (secondary electron and backscatter electron), measured concentration profiles of alloying elements using energy dispersive X-ray spectroscopy (EDS), widths of denuded zones (dissolution of strengthening phases) and depths of attack in molten KCl-MgCl 2 mixtures using image analyses. The creep dataset comprised of creep rupture data and creep strain curves (for 740H and 282). Coupled thermodynamic-kinetic microstructure-based models were employed to predict the stress-corrosion induced compositional and phase evolutions in the alloy during operation under the identified operating conditions. Reduced order models were developed from advanced physics-based models and were integrated in a user-friendly alloy selection tool. The corrosion model was able to predict the time to a critical Cr concentration at the oxide/alloy interface (chemical lifetime) within ±10% (1 standard deviation) of typical statistical variation in corrosion tests and EDS measurement errors (±0.5 wt%). The initial scope of the project was limited to predict creep rupture times (Larson-Miller parameter). Based on the input provided by industry, the mechanical lifetime of the heat exchanger is governed by accumulated creep strains (2%) rather than creep rupture. To be able to predict the times to specific creep strains, a more extensive creep model development was undertaken largely beyond the initial scope of the project. The continuum damage mechanics creep model was able to predict times to 2% creep strain, t 2% with an accuracy of ±500h. Ultimately, a screening protocol for SiC was generated to demonstrate the pathway for integration of one of the currently immature materials from a commercial adoption standpoint in the current material evaluation tool. The modeling tool developed here is accessible to the science community and stakeholders and lays the foundation for methods that will enable a rapid evaluation of optimum materials for CSP applications and reliable prediction of material degradation thereby considerably reducing operational costs, improving reliability and increasing overhaul intervals. However, the complete potential of such a tool to include a wider range of materials and test conditions can only be realized with a more concentrated combined experimental-characterization-computation effort.

14 SOLAR ENERGY↗
NASA NTRS1989

The moderate resolution imaging spectrometer data system

Science requirements for a moderate resolution imaging spectrometer (MODIS) data system are outlined, as well as the operations concept and system specifications based on these requirements. Two systems are considered - MODIS-N for a 40-channel nadir-viewing scanner and MODIS-T for a 64-channel tiltable scanner. The first system collects data from 15 thermal-infrared channels at all times and from 25 reflected-energy channels during daytime, while MODIS-T will take data from 64 channels on a 100-percent duty cycle during daytime only. Standard data products, data acquisition and processing, and requirements on data are discussed. Emphasis is placed on the interfaces between the science data processing facilities and the scientific users.

Han, Daesoo↗
NASA NTRS2003

Evaluating the Usability of Pinchigator, a system for Navigating Virtual Worlds using Pinch Gloves

Appropriate design of two dimensional user interfaces (2D U/I) utilizing the well known WIMP (Window, Icon, Menu, Pointing device) environment for computer software is well studied and guidance can be found in several standards. Three-dimensional U/I design is not nearly so mature as 2D U/I, and standards bodies have not reached consensus on what makes a usable interface. This is especially true when the tools for interacting with the virtual environment may include stereo viewing, real time trackers and pinch gloves instead of just a mouse & keyboard. Over the last several years the authors have created a 3D U/I system dubbed Pinchigator for navigating virtual worlds based on the dVise dV/Mockup visualization software, Fakespace Pinch Gloves and Pohlemus trackers. The current work is to test the usability of the system on several virtual worlds, suggest improvements to increase Pinchigator s usability, and then to generalize about what was learned and how those lessons might be applied to improve other 3D U/I systems.

Hamilton, George S.↗
NASA NTRS2008

The User Community and a Multi-Mission Data Project: Services, Experiences and Directions of the Space Physics Data Facility

From a user's perspective, the multi-mission data and orbit services of NASA's Space Physics Data Facility (SPDF) project offer a unique range of important data and services highly complementary to other services presently available or now evolving in the international heliophysics data environment. The VSP (Virtual Space Physics Observatory) service is an active portal to a wide range of distributed data sources. CDAWeb (Coordinate Data Analysis Web) enables plots, listings and file downloads for current data cross the boundaries of missions and instrument types (and now including data from THEMIS and STEREO). SSCWeb, Helioweb and our 3D Animated Orbit Viewer (TIPSOD) provide position data and query logic for most missions currently important to heliophysics science. OMNIWeb with its new extension to 1- and 5-minute resolution provides interplanetary parameters at the Earth's bow shock as a unique value-added data product. SPDF also maintains NASA's CDF (common Data Format) standard and a range of associated tools including translation services. These capabilities are all now available through webservices-based APIs as well as through our direct user interfaces. In this paper, we will demonstrate the latest data and capabilities now supported in these multi-mission services, review the lessons we continue to learn in what science users need and value in this class of services, and discuss out current thinking to the future role and appropriate focus of the SPDF effort in the evolving and increasingly distributed heliophysics data environment.

Fung, Shing F.↗
NASA NTRS2004

Modular, Adaptive, Reconfigurable Systems: Technology for Sustainable, Reliable, Effective, and Affordable Space Exploration

In order to execute the Vision for Space Exploration, we must find ways to reduce cost, system complexity, design, build, and test times, and at the same time increase flexibility to satisfy multiple functions. Modular, Adaptive, Reconfigurable System (MARS) technologies promise to set the stage for the delivery of system elements that form the building blocks of increasingly ambitious missions involving humans and robots. Today, space systems are largely specialized and built on a case-by-case basis. The notion of modularity however, is nothing new to NASA. The 1970's saw the development of the Multi-Mission Modular spacecraft (MMS). From 1980 to 1992 at least six satellites were built under this paradigm, and included such Goddard Space Flight Center missions as SSM, EUVE, UARS, and Landsat 4 and 5. Earlier versions consisted of standard subsystem "module" or "box" components that could be replaced within a structure based on predefined form factors. Although the primary motivation for MMS was faster/cheaper integration and test, standardization of interfaces, and ease of incorporating new subsystem technology, it lacked the technology maturity and programmatic "upgrade infrastructure" needed to satisfy varied mission requirements, and ultimately it lacked user buy-in. Consequently, it never evolved and was phased out. Such concepts as the Rapid Spacecraft Development Office (RSDO) with its regularly updated catalogue of prequalified busses became the preferred method for acquiring satellites. Notwithstanding, over the past 30 years since MMS inception, technology has advanced considerably and now modularity can be extended beyond the traditional MMS module or box to cover levels of integration, from the chip, card, box, subsystem, to the space system and to the system-of-systems. This paper will present the MARS architecture, cast within the historical context of MMS. Its application will be highlighted by comparing a state-of-the-art point design vs. a MARS-enabled lunar mission, as a representative robotic case design.

Esper, Jaime↗
NASA NTRS2004

Surface Modeling and Grid Generation for Iced Airfoils (SmaggIce)

Many of the troubles associated with problem solving are alleviated when there is a model that can be used to represent the problem. Through the Advanced Graphics and Visualization (G-VIS) Laboratory and other facilities located within the Research Analysis Center, the Computer Services Division (CSD) is able to develop and maintain programs and software that allow for the modeling of various situations. For example, the Icing Research Branch is devoted to investigating the effect of ice that forms on the wings and other airfoils of airplanes while in flight. While running tests that physically generate ice and wind on airfoils within the laboratories and wind tunnels on site are done, it would be beneficial if most of the preliminary work could be done outside of the lab. Therefore, individuals from within CSD have collaborated with Icing Research in order to create SmaggIce. This software allows users to create ice patterns on clean airfoils or open files containing a variety of icing situations, manipulate and measure these forms, generate, divide, and merge grids around these elements for more explicit analysis, and specify and rediscretize subcurves. With the projected completion date of Summer 2005, the majority of the focus of the Smagglce team is user-functionality and error handling. My primary responsibility is to test the Graphical User Interface (GUI) in SmaggIce in order to ensure the usability and verify the expected results of the events (buttons, menus, etc.) within the program. However, there is no standardized, systematic way in which to test all the possible combinations or permutations of events, not to mention unsolicited events such as errors. Moreover, scripting tests, if not done properly and with a view towards inevitable revision, can result in more apparent errors within the software and in effect become useless whenever the developers of the program make a slight change in the way a specific process is executed. My task therefore requires a brief yet intense study into GUI coverage criteria and creating algorithms for GUI implementation. Nevertheless, there are still heavily graphical features of SmaggIceSmaggIce that must be either corrected or redesigned before its release. A particular feature of SmaggIce is the ability to smooth out curves created by control points that form an arbitrary shape into something more acquiescent to gridding (while maintaining the integrity of the data). This is done by a mathematical model known as Non-Uniform Rational B-Spline (NURBS) curves. Existing NURBS code is written in FORTRAN-77 with static arrays for holding information. My new assignment is to allow for dynamic memory allocation within the code and to make it possible for the developers to call out functions from the NURBS code using C.

Hammond, Brandy M.↗
NASA NTRS2022

PAAV Concept Document

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) Concept Document, version 1.0, lays out the key challenges and potential solutions for the use of uncrewed aircraft (UA) technology for future regional air cargo operations. The challenges and solutions described in this document were informed by communications with the UA industry community (e.g., RTCA, the Federal Aviation Administration, and regional air cargo business operators), as well as the PAAV team’s research activities during the last two years including four tabletop exercises, a human-in-the-loop simulation study, a numerical simulation study, a functional allocation study, and flight data analysis (Appendix A). This document first describes the expected operational context of PAAV (Section 2), such as the flight mission, baseline UAS components, nominal operations, m:N operations (i.e., "m" remote pilots per "N" aircraft), and off-nominal operations. This context sets the scope for the PAAV concept development work. PAAV concept development assumes that UA operations will be increasingly autonomous. Thus, near- and far-term assumptions are defined (Section 3). PAAV identified seven key challenges for UA operations (Section 4): - Flight route planning - Separation and flow management - Traffic pattern integration - Contingency management - Taxi, takeoff, and landing - m:N operations - Communications operations The following 13 potential solutions to these challenges are then described (Section 5): - Scalable communications architecture - Data link - Designated UAS corridors - Crew planning for m:N operations - Flight route optimization - Traffic load-level control - Trajectory solutions with data link - Automated hazard avoidance for m:N operations - Traffic pattern integration (TPI) tool - Standard lost command and control (C2) link (LC2L) procedures - Automated hazard avoidance under LC2L - Auto-taxi, auto-takeoff, and auto-land - Ground control station (GCS) user interface for m:N operations The document attempts to link each of these solutions to one or more of the challenge areas. Novel solutions involving numerous automation technologies are needed to mitigate traffic and airspace management challenges, especially for realizing m:N operations and ensuring safety under LC2L conditions. The purpose of this document is to help understand alternatives and tradeoffs among potential solutions and provide a foundation for a cohesive PAAV concept that will be described and refined in subsequent concept versions.

Unmanned aircraft, uncrewed aircraft, regional air↗
NASA NTRS2006

SpaceWire Protocol ID: What Does It Mean To You?

Spacewire is becoming a popular solution for satellite high-speed data buses because it is a simple standard that provides great flexibility for a wide range of system requirements. It is simple in packet format and protocol, allowing users to easily tailor their implementation for their specific application. Some of the attractive aspects of Spacewire that make it easy to implement also make it hard for future reuse. Protocol reuse is difficult because Spacewire does not have a defined mechanism to communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet formats and define how these packets are to be processed. Each mission writes their own Interface Control Document (ICD) and tailors Spacewire for their specific requirements making reuse difficult. Part of the reason for this habit may be because engineers typically optimize designs for their own requirements in the absence of a standard. This is an inefficient use of project resources and costs more to develop missions. A new packet format for Spacewire has been defined as a solution for this problem. This new packet format is a compliment to the Spacewire standard that will support protocol development upon Spacewire. The new packet definition does not replace the current packet structure, i.e., does not make the standard obsolete, but merely extends the standard for those who want to develop protocols over Spacewire. The Spacewire packet is defined with the first part being the Destination Address, which may be one or more bytes. This is followed by the packet cargo, which is user defined. The cargo is truncated with an End-Of-Packet (EOP) marker. This packet structure offers low packet overhead and allows the user to define how the contents are to be formatted. It also provides for many different addressing schemes, which provide flexibility in the system. This packet flexibility is typically an attractive part of the Spacewire. The new extended packet format adds one new field to the packet that greatly enhances the capability of Spacewire. This new field called the Protocol Identifier (ID) is used to identify the packet contents and the associated processing for the packet. This feature along with the restriction in the packet format that uses the Protocol ID, allows a deterministic method of decoding packets that was not before possible. The first part of the packet is still the Destination Address, which still conforms to the original standard but with one restriction. The restriction is that the first byte seen at the destination by the user needs to be a logical address, independent of the addressing scheme used. The second field is defined as the Protocol ID, which is usually one byte in length. The packet cargo (user defined) follows the Protocol ID. After the packet cargo is the EOP, which defines the end of packet. The value of the Protocol ID is assigned by the Spacewire working group and the protocol description published for others to use. The development of Protocols for Spacewire is currently the area of greatest activity by the Spacewire working group. The first protocol definition by the working group has been completed and is now in the process of formal standardization. There are many other protocols in development for missions that have not yet received formal Protocol ID assignment, but even if the protocols are not formally assigned a value, this effort will provide synergism for future developments.

Rakow, Glenn↗
DOE OSTI2020

Grid Integration of Small-Scale Photovoltaic Systems in Secondary Distribution Network—A Review

The relative share of renewable energy, specifically the solar photovoltaic (PV), is increasing exponentially in the world electric energy sector. This is a cumulative result of reduction in the cost of solar panels, improvement in the panel efficiency, and advancement in the associated power electronics. Among different types of PV plants, installation of small-scale rooftop PV is growing rapidly due to direct end-user benefits and lucrative governmental incentives. There are various standards developed in regards to grid integration of PVs and other distributed generations (DGs). Different power converter topologies are developed to interface the PV panel with the utility grid. To keep up with the stringent regulations imposed by the standards, various control strategies and grid synchronization methods have been developed. This review article amalgamates and summarizes all of the aforementioned aspects of a grid-integrated PV system including various standards, power stage architectures, grid synchronization methods, operation under extreme events, and control methodologies, pertaining to small-scale PV plants. This article will help freshman researchers to gain some familiarity with the topic and introduce them to some of the key issues encountered in this field.

14 SOLAR ENERGY↗
DOE OSTI2022

A SIMPLE TOOL TO EVALUATE COLOR FOR LEGIBILITY AND DISTINGUISHABILITY WHEN DESIGNING DIGITAL DISPLAYS

Color is important in helping users effectively process information like text and symbols when performing tasks on digital displays. Interface designers in safety- and mission-critical industries often utilize human factors design guidelines and standards to make important design decisions like the use of color for legibility and distinguishability. However, such guidance sometimes requires additional interpretation and calculation to readily apply to the design question at hand. This work describes a simple tool that can be used to evaluate the adequacy of color choices from a palette for being legible or distinguishable. The tool eliminates having to manually convert colors to a readable format while providing a specific set of colors that are acceptable from select human factors standards. This paper provides an exemplary case study applied to a digital modification at a nuclear power plant to highlight how the tool may be used in safety and mission-critical industries.

99 GENERAL AND MISCELLANEOUS↗
DOE OSTI2022

MOSCATO Development and Integration in Fiscal Year 2022

During FY21, we conducted ongoing development work for the MOSCATO (Molten Salt Chemistry and Transport) solver. The code development work primarily consisted of transitioning capabilities from the original version of the solver, which was written in OpenFOAM, into Nek5000. In doing so, a fast, highly parallelizable solver was created that is capable of complex chemistry and corrosion simulations for engineering-scale molten salt systems. The Nek5000 version of MOSCATO is now fully featured and capable of higher-fidelity simulations than were previously possible. Demonstration cases including a thermal convection loop have been simulated to test these new capabilities. We built upon the work for FY22 and improved the code from several different perspectives. First, we improved the user interface by adding a new component to the official Nek5000 input file (.par). This new part contains documents parameters like, salt properties (density, viscosity, Cp, thermal conductivity), diffusion coefficients, standard potential, etc. Second, we built a conversion script to extract salt properties from the MSTDB-TP salt database and write to MOSCATO input file. Third, we migrated the code to NekRS, which is the GPU branch of Nek5000 and suitable for next generation supercomputers. Verification and Validation (V&V) work was also continued in FY22. Two tasks were performed. The first V&V task involved the validation of the Poisson-Nernst-Planck equation solver and Butler-Volmer electrode kinetics, by comparing with numerical and experimental data about thermoelectric cells. The second task involved the comparisons to corrosion results from a thermal convection loop run during the MSRE era. Satisfactory agreement was obtained from both tasks.

Yuan, Haomin↗
NASA NTRSDate not supplied

NASA's Efforts to Commercialize Communications Services for Mission in Near-Earth Space

The National Aeronautics and Space Administration (NASA) Space Communications and Navigation (SCaN)Program enables high speed, robust, secure and cost-effective space communications and navigation services to current and future science and exploration missions. Consistent with National Space Policy, NASA is pursuing the use of demonstrated commercial services for all its future near-Earth requirements through a flexible, multi-provider approach that minimizes risks to the user missions and ensures costs to user missions are reasonable. Progress toward this goal is advancing in multiple key areas including direct to Earth (DTE), space-based relay, technology investments, required spectrum regulatory changes and mission engagement and infusion. The transition to commercial DTE services is already underway, with a target for transition by 2024. The primary functions to execute SCaN’s DTE strategy include increasing commercial service allocations by leveraging current commercial network providers and enabling seamless onboarding of additional providers into the network. Furthermore, moving away from government DTE services will allow operational costs to be optimized. A more gradual approach is planned for the transition to commercial space-based relay services to allow for demonstration and operationalization of commercial services for future users by 2030. In June of 2022, six American SATCOM vendors were awarded a combined $278.5 million through Funded Space Act Agreements (FSAAs) for the first cycle of demonstration and validation activities. The end-to-end service capabilities being targeted are based on existing NASA mission operational needs. Accordingly, each company has proposed a technical approach to lower costs, increase flexibility, and improve performance for a broad range of missions. Successful user mission transition to commercial services, both DTE and space-based relay, are dependent on the technologies and capabilities that address gaps in commercial capability. NASA is investing in technology development and pursuing a new strategic approach to the creation or adoption of space communications standards to move the agency toward a commercial paradigm. Wideband and multi-lingual user terminals are being developed to bridge differences in industry services. Building on ground demonstrations completed in 2021, the Johns Hopkins Applied Physics Lab (APL) will be flight testing a multi-lingual wideband terminal (payload) and demonstrating connectivity to both government and commercial relay services. NASA holds a leadership role in multiple civil space standards bodies and international coordination groups to ensure that standards supporting interoperability are developed with defined functions, interfaces, and performance. However, to successfully meet commercialization objectives, NASA seeks to collaborate with industry, and as applicable adopt or adapt to commercially defined standards. As such, NASA joined the 3rd Generation Partnership Project (3GPP) as an official member in 2021 to advocate for the inclusion of space missions as a unique user segment in future 5G non-terrestrial networks, and to better understand the scope of 3GPP releases and implications for space users. Further, engagement in Spectrum regulatory bodies is being undertaken to augment existing space-Earth and inter-satellite frequency allocations available for both government and commercial space systems. This paper addresses the recent progress toward NASA’s commercial space communications transition objectives and how key challenges are being navigated.

Gregory W Heckler↗
NASA NTRS1986

Investigation of local area networks for an obiting space station

An investigation and test of various equipment was conducted to determine its state of repair and suitability for use in a test-bed computer network (to be used to simulate a space station configuration of computers for control and monitoring). A research study was also made of various network types, including the IEEE network standards: (1) Carrier Sense Multiple Access with Collision Detection. (2) Token Passing Bus (3) Token Passing Ring, and (4) the draft ANSI standard for a High Speed Local Network, CSMA with Collision Avoidance. No firm conclusions are possible at this time as to which would be most suitable. An evaluation of the user interface of a space station database program, FREDSS (Formatted Retrieval and Entry of Data for Space Station, preliminary version), was also conducted and recommendations were made for possible improvements.

Deacetis, L. A.↗
NASA NTRS1989

CHIMERA II - A real-time multiprocessing environment for sensor-based robot control

A multiprocessing environment for a wide variety of sensor-based robot system, providing the flexibility, performance, and UNIX-compatible interface needed for fast development of real-time code is addressed. The requirements imposed on the design of a programming environment for sensor-based robotic control is outlined. The details of the current hardware configuration are presented, along with the details of the CHIMERA II software. Emphasis is placed on the kernel, low-level interboard communication, user interface, extended file system, user-definable and dynamically selectable real-time schedulers, remote process synchronization, and generalized interprocess communication. A possible implementation of a hierarchical control model, the NASA/NBS standard reference model for telerobot control system is demonstrated.

Stewart, David B.↗
NASA NTRS1992

Data Management Systems (DMS): Complex data types study. Volume 1: Appendices A-B. Volume 2: Appendices C1-C5. Volume 3: Appendices D1-D3 and E

Two categories were chosen for study: the issue of using a preprocessor on Ada code of Application Programs which would interface with the Run-Time Object Data Base Standard Services (RODB STSV), the intent was to catch and correct any mis-registration errors of the program coder between the user declared Objects, their types, their addresses, and the corresponding RODB definitions; and RODB STSV Performance Issues and Identification of Problems with the planned methods for accessing Primitive Object Attributes, this included the study of an alternate storage scheme to the 'store objects by attribute' scheme in the current design of the RODB. The study resulted in essentially three separate documents, an interpretation of the system requirements, an assessment of the preliminary design, and a detailing of the components of a detailed design.

Leibfried, T. F., Jr.↗
NASA NTRS1999

"An On-Line Access System for TRMM Data"

The Tropical Rainfall Measuring Mission (TRMM), jointly sponsored by the National Aeronautics and Space Administration (NASA) of United States and the National Space Development Agency (NASDA) of Japan, provides visible, infrared, and microwave observations of tropical and subtropical rain system. The satellite observations are complemented by ground radar and rain gauge measurements to validate satellite rain estimation techniques. TRMM satellite was launched on November 27, 1997(EST). Data from TRMM are being archived, processed, and disseminated by DAAC at the Goddard Space Flight Center (GSFC) of NASA. The Goddard DAAC has been archiving Tropical Rainfall Measuring Mission (TRMM) data since the launch. The TRMM level 1 and level 2 products first have been released to public on June 15, 1998. Now, most of TRMM products, including some ground validation products are released to public. TRMM data are useful for forecast model research, disaster mitigation, climatological studies, agricultural predictions, and many other applications. An online system or user interface is designed for easy, friendly, and quick display, access, and ordering of the TRMM data. Components, features, and limitations of the system will be discussed and demonstrated. The TRMM standard products and variety of the subsets and ancillary data will be shown, and their availability will be discussed.

Rui, Hualan↗
NASA NTRS2002

The spacecraft onboard interface standardization activity

The Consultative Committee for Space Data Systems (CCSDS) is an international organization of national space agencies (such as NASA in the United States) that is organized to promote the interchange of space related information. Now, CCSDS is branching out to provide new standards for the interchange of information, and the interconnection of subsystems and devices onboard of a spacecraft. This effort is know as Spacecraft Onboard Interface (SOIF). SOIF will publish standards that will allow for the enhanced reuse of spacecraft equipment and software. SOIF expects that these standards will be well known and used within the space community, and that they will be based on or similar to the well-known Internet protocols. This paper will provide a description of the SOIF work by reviewing this work with three orthogonal views. The first of these views is the Protocol view, which describes the protocols and services that are to be implemented in order to provide the users with the advantages of the SOIF architecture. The second of these views is the Services View, which describes the data communications services that are provided to the users. And finally, the Interoperability view provides a description to users how SOIF can be used to interchange between different spacecraft data busses. This paper will give the reader an excellent introduction to the work of the international SOIF team.

spacecraft interfaces standard interfaces CCSDS↗
NASA NTRS1991

Ada and the rapid development lifecycle

JPL is under contract, through NASA, with the US Army to develop a state-of-the-art Command Center System for the US European Command (USEUCOM). The Command Center System will receive, process, and integrate force status information from various sources and provide this integrated information to staff officers and decision makers in a format designed to enhance user comprehension and utility. The system is based on distributed workstation class microcomputers, VAX- and SUN-based data servers, and interfaces to existing military mainframe systems and communication networks. JPL is developing the Command Center System utilizing an incremental delivery methodology called the Rapid Development Methodology with adherence to government and industry standards including the UNIX operating system, X Windows, OSF/Motif, and the Ada programming language. Through a combination of software engineering techniques specific to the Ada programming language and the Rapid Development Approach, JPL was able to deliver capability to the military user incrementally, with comparable quality and improved economies of projects developed under more traditional software intensive system implementation methodologies.

Deforrest, Lloyd↗