Search NASA⌕ Search

SEARCH · Search NASA

Results for “user support”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

The development of an Ada programming support environment database: SEAD (Software Engineering and Ada Database), user's manual

This is a manual for users of the Software Engineering and Ada Database (SEAD). SEAD was developed to provide an information resource to NASA and NASA contractors with respect to Ada-based resources and activities that are available or underway either in NASA or elsewhere in the worldwide Ada community. The sharing of such information will reduce the duplication of effort while improving quality in the development of future software systems. The manual describes the organization of the data in SEAD, the user interface from logging in to logging out, and concludes with a ten chapter tutorial on how to use the information in SEAD. Two appendices provide quick reference for logging into SEAD and using the keyboard of an IBM 3270 or VT100 computer terminal.

Liaw, Morris↗
NASA NTRS1994

MSFC institutional area network and ATM technology

The New Institutional Area Network (NEWIAN) at Marshall supports over 5000 end users with access to 26 file servers providing work presentation services. It is comprised of some 150 Ethernet LAN's interconnected by bridges/routers which are in turn connected to servers over two dual FDDI rings. The network supports various higher level protocols such as IP, IPX, AppleTalk (AT), and DECNet. At present IPX and AT protocols packets are routed, and IP protocol packets are bridged; however, work is in progress to route all IP packets. The impact of routing IP packets on network operation is examined. Broadband Integrated Services Data Network (BISDN), presently at various stages of development, is intended to provide voice, video, and data transfer services over a single network. BISDN will use asynchronous transfer mode (ATM) as a data transfer technique which provides for transmission, multiplexing, switching, and relaying of small size data units called cells. Limited ATM Wide Area Network (WAN) services are offered by Wiltel, AT&T, Sprint, and others. NASA is testing a pilot ATM WAN with a view to provide Program Support Communication Network services using ATM. ATM supports wide range of data rates and quality of service requirements. It is expected that ATM switches will penetrate campus networks as well. However, presently products in these areas are at various stages of development and standards are not yet complete. We examine development of ATM to help assess its role in the evolution of NEWIAN.

Amin, Ashok T.↗
NASA NTRS1991

Evolution user requirements for the restructured space station

Space Station Freedom (SSF) is designed to be an Earth orbiting multidisciplinary R&D facility capable of evolving to accommodate a variety of potential uses. In order to identify SSF evolution requirement and define potential growth configurations, NASA-Langley is analyzing user resource requirements for the post-PMC time frame. The analysis goal is to define resource levels, including crew, power, and volume, which allow full utilization of SSF capabilities commensurate with minimum essential user requirements. Multiple scenarios were studied including core R&D and combined SEI plus R&D utilization. An analysis is presented of a core R&D utilization scenario. Included are discussions of resource allocation assumptions for specific R&D disciplines, user requirements trends, and growth resource projections. These preliminary results show total resource requirements of 13 crew, 150 kW power, and additional lab volume equivalent to a second U.S. lab module. Additionally, orthogonal growth structure was identified as required to support SSF systems and users.

Leath, K.↗
NASA NTRS2011

A Possible Approach for Addressing Neglected Human Factors Issues of Systems Engineering

The increasing complexity of safety-critical applications has led to the introduction of decision support tools in the transportation and process industries. Automation has also been introduced to support operator intervention in safety-critical applications. These innovations help reduce overall operator workload, and filter application data to maximize the finite cognitive and perceptual resources of system operators. However, these benefits do not come without a cost. Increased computational support for the end-users of safety-critical applications leads to increased reliance on engineers to monitor and maintain automated systems and decision support tools. This paper argues that by focussing on the end-users of complex applications, previous research has tended to neglect the demands that are being placed on systems engineers. The argument is illustrated through discussing three recent accidents. The paper concludes by presenting a possible strategy for building and using highly automated systems based on increased attention by management and regulators, improvements in competency and training for technical staff, sustained support for engineering team resource management, and the development of incident reporting systems for infrastructure failures. This paper represents preliminary work, about which we seek comments and suggestions.

Johnson, Christopher W.↗
NASA NTRS1988

IDSE Version 1 User's Manual

The integrated development support environment (IDSE) is a suite of integrated software tools that provide intelligent support for information modelling. These tools assist in function, information, and process modeling. Additional tools exist to assist in gathering and analyzing information to be modeled. This is a user's guide to application of the IDSE. Sections covering the requirements and design of each of the tools are presented. There are currently three integrated computer aided manufacturing definition (IDEF) modeling methodologies: IDEF0, IDEF1, and IDEF2. Also, four appendices exist to describe hardware and software requirements, installation procedures, and basic hardware usage.

Mayer, Richard↗
NASA NTRS2001

An Approach to Data Center-Based KDD of Remote Sensing Datasets

The data explosion in remote sensing is straining the ability of data centers to deliver the data to the user community, yet many large-volume users actually seek a relatively small information component within the data, which they extract at their sites using Knowledge Discovery in Databases (KDD) techniques. To improve the efficiency of this process, the Goddard Earth Sciences Distributed Active Archive Center (GES DAAC) has implemented a KDD subsystem that supports execution of the user's KDD algorithm at the data center, dramatically reducing the volume that is sent to the user. The data are extracted from the archive in a planned, organized "campaign"; the algorithms are executed, and the output products sent to the users over the network. The first campaign, now complete, has resulted in overall reductions in shipped volume from 3.3 TB to 0.4 TB.

Lynnes, Christopher↗
NASA NTRS1995

WISE: Automated support for software project management and measurement

One important aspect of software development and IV&V is measurement. Unless a software development effort is measured in some way, it is difficult to judge the effectiveness of current efforts and predict future performances. Collection of metrics and adherence to a process are difficult tasks in a software project. Change activity is a powerful indicator of project status. Automated systems that can handle change requests, issues, and other process documents provide an excellent platform for tracking the status of the project. A World Wide Web based architecture is developed for (a) making metrics collection an implicit part of the software process, (b) providing metric analysis dynamically, (c) supporting automated tools that can complement current practices of in-process improvement, and (d) overcoming geographical barrier. An operational system (WISE) instantiates this architecture allowing for the improvement of software process in a realistic environment. The tool tracks issues in software development process, provides informal communication between the users with different roles, supports to-do lists (TDL), and helps in software process improvement. WISE minimizes the time devoted to metrics collection, analysis, and captures software change data. Automated tools like WISE focus on understanding and managing the software process. The goal is improvement through measurement.

Ramakrishnan, Sudhakar↗
NASA NTRS1986

Integration of an expert system into a user interface language demonstration

The need for a User Interface Language (UIL) has been recognized by the Space Station Program Office as a necessary tool to aid in minimizing the cost of software generation by multiple users. Previous history in the Space Shuttle Program has shown that many different areas of software generation, such as operations, integration, testing, etc., have each used a different user command language although the types of operations being performed were similar in many respects. Since the Space Station represents a much more complex software task, a common user command language--a user interface language--is required to support the large spectrum of space station software developers and users. To assist in the selection of an appropriate set of definitions for a UIL, a series of demonstration programs was generated with which to test UIL concepts against specific Space Station scenarios using operators for the astronaut and scientific community. Because of the importance of expert system in the space station, it was decided that an expert system should be embedded in the UIL. This would not only provide insight into the UIL components required but would indicate the effectiveness with which an expert system could function in such an environment.

Stclair, D. C.↗
NASA NTRS2018

NASA Provides the Capability to Deliver Near Real-Time JPSS Data to Users in Order to Monitor Time-Sensitive Applications Such as Wildfires, Floods, Volcanic Eruptions, Tropical Cyclones and Extreme Weather Events

NASA's Land, Atmosphere Near real-time Capability for EOS (Earth Observing System) (LANCE https://earthdata.nasa.gov/lance) serves near real time (NRT) data to monitor time sensitive applications such as monitoring wildfires, floods, volcanic eruptions, tropical cyclones and extreme weather events. It currently serves data and imagery from the Visible Infrared Imager Radiometer Suite (VIIRS) and Ozone Mapping and Profiler Suite (OMPS) S NPP (Suomi National Polar-orbiting Partnership) instruments and is in the process of integrating continuity data products from VIIRS and OMPS onboard the Joint Polar Satellite System (JPSS), via the JPSS data Hub, to continue to meet the needs of agencies, scientists and members of the general public. NASA's Earth Science Division (ESD) sponsored the EOSDIS development of LANCE in 2009 to provide a central point of access to high quality NRT data products and imagery for applications users. LANCE makes data available to the public within 3 hours of satellite observation and imagery within 4-5 hours of satellite observation. Full resolution browse imagery from LANCE are provided through the Global Imagery Browse Services (GIBS) which also fuels NASA's Worldview tool so that users can interactively browse near real time data. This data supports time critical applications and allows users to view current natural hazards and events and animate the imagery over time.

Near real time↗
NASA NTRSDate not supplied

NASA AREAL Testbed and UE Power Quality Testing

A large number of electrified aircraft propulsion systems currently in development consist of high-voltage direct current (HVDC) power systems and utilization equipment (UE). There is a need for industry consensus standards and guidelines in order to support the development and verification of these rapidly maturing systems, user equipment, and associated technologies. To support the aforementioned need, the National Aeronautics and Space Administration (NASA) Revolutionary Vertical Lift Technology (RVLT) Project is performing ongoing power quality testing on HVDC power systems and associated UE. The testing described in this paper describes the UE testing completed to date in the NASA Advanced Reconfigurable Electrified Aircraft Lab (AREAL).

electrified aircraft↗
NASA NTRS2018

An Integrated Platform for Mission Performance: Goddard Space Flight Center's Meta Information System

Successful management of NASA Goddard Space Flight Centers portfolio of mission projects (i.e. spacecraft, spacecraft instruments / subsystems, and ground systems) depends upon numerous processes, data and information resources coming together throughout the life-cycle of the projects to enable sound decision-making, risk reduction, conformance with requirements and continual improvement. In the summer of 2012, GSFC SMA management recognized that the set of legacy data systems used to support the SMA mission and responsibilities at GSFC were not effective, integrated nor on par with best practices. Accordingly, GSFC SMA management launched a project to transform the GSFC electronic management system to create and deploy an integrated, state-of-the-market information system for process performance, data management and analytics that is currently operating in support of GSFC overall mission performance. The information system, known as Meta, provides controlled, process-based applications, integrated data management, and analytics for a robust set of integrated applications. Since the inception of the project, a lean, award-winning SMA project team has thus far designed, configured and managed the system to serve as an integrated platform for 18 applications that support key processes for GSFC and the Science Mission Directorate at NASA headquarters, such as internal Management System assessments, Supplier Assessments, Supplier Research & Analysis, Problem Reporting for in-house mission projects, On-orbit Anomaly Reporting for GSFC-operated spacecraft, GSFC Project Life-Cycle Reviews, Risk Management and Reporting, and SMA Project Team Reporting. The system has experienced steady growth in utilization with 1,917 users (NASA employees and support contractor personnel) and 44 gigabytes of data and related files managed by the system as of the end of April 2018. Overall, Meta has achieved increasing levels of process management and real-time data / information integration to enable improved process performance, richer analytics and informed decision-making. This paper will present and examine the need, goals, approach and design driving the management and operation of the Meta information system and its ongoing growth as an integrated platform for advancing NASA mission performance.

Integration↗
NASA NTRS1991

Applied Information Systems Research Program Workshop

The first Applied Information Systems Research Program (AISRP) Workshop provided the impetus for several groups involved in information systems to review current activities. The objectives of the workshop included: (1) to provide an open forum for interaction and discussion of information systems; (2) to promote understanding by initiating a dialogue with the intended benefactors of the program, the scientific user community, and discuss options for improving their support; (3) create an advocacy in having science users and investigators of the program meet together and establish the basis for direction and growth; and (4) support the future of the program by building collaborations and interaction to encourage an investigator working group approach for conducting the program.

Source record↗
NASA NTRS1993

Intelligent systems and advanced user interfaces for design, operation, and maintenance of command management systems

Historically, command management systems (CMS) have been large and expensive spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as to develop a more generic CMS system. New technologies, in addition to a core CMS common to a range of spacecraft, may facilitate the training and enhance the efficiency of CMS operations. Current mission operations center (MOC) hardware and software include Unix workstations, the C/C++ programming languages, and an X window interface. This configuration provides the power and flexibility to support sophisticated and intelligent user interfaces that exploit state-of-the-art technologies in human-machine interaction, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of these issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, human-machine systems design and analysis tools (e.g., operator and designer models), and human-computer interaction tools (e.g., graphics, visualization, and animation) may provide significant savings in the design, operation, and maintenance of the CMS for a specific spacecraft as well as continuity for CMS design and development across spacecraft. The first six months of this research saw a broad investigation by Georgia Tech researchers into the function, design, and operation of current and planned command management systems at Goddard Space Flight Center. As the first step, the researchers attempted to understand the current and anticipated horizons of command management systems at Goddard. Preliminary results are given on CMS commonalities and causes of low re-use, and methods are proposed to facilitate increased re-use.

Potter, William J.↗
NASA NTRS1980

An Engineering Data Management System for Ipad

An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented. IPIP is a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems. It also significantly advances a number of capabilities that are offered commercially. IPIP capabilities range from support for multiple schemas and data models to support for distributed processing, configuration control, and data inventory management. IPIP exploits semantic commonality in features offered in various forms at different user interfaces in today's commercial systems. An integrated software architecture supports all user interfaces: programming languages, interactive data manipulation, and schema languages. This approach promotes simplicity and compactness in software and permits features to be offered symmetrically across all appropriate user interfaces.

H R Johnson↗
NASA NTRS1992

An object-oriented approach for supporting both X and terminal interfaces

While the X Window System is clearly becoming the dominant user interface between display system, there is still a continuing need to support character cell terminal devices. For a user interface application which must support both, it is desirable to be able to use them to their fullest extent, as opposed to simply providing a character-based display within an X window. An object-oriented application framework is presented here which allows the full capabilities of each system to be used while minimizing and isolating the amount of device-dependent code. Every user interface application consists of two parts: the various components used to display information and accept user input, and the processing of the interaction between these components. Many user interfaces are built around a core set of components such as menus, text entry fields, and forms. For a given application, the interaction between these components is the same regardless of the display system in use. Our approach is to implement each component as an object, accessible via a single public interface. All of the code necesary to implement the component for the desired display system is completely encapsulated within the object. The application is then written as a collection of objects interacting in a device-independent manner with one another. If a display system provides additional capabilities, the application can be extended by adding objects (e.g. for image display in X). We are currently implementing StarView, the user interface to the HST science archive (STDADS) using this approach. StarView will be written in C++ and will use Vermont Views for the terminal interface and OSF/Motif for the X Window interface.

Johnson, J.↗
NASA NTRS1999

Field Encapsulation Library The FEL 2.2 User Guide

This document describes version 2.2 of the Field Encapsulation Library (FEL), a library of mesh and field classes. FEL is a library for programmers - it is a "building block" enabling the rapid development of applications by a user. Since FEL is a library intended for code development, it is essential that enough technical detail be provided so that one can make full use of the code. Providing such detail requires some assumptions with respect to the reader's familiarity with the library implementation language, C++, particularly C++ with templates. We have done our best to make the explanations accessible to those who may not be completely C++ literate. Nevertheless, familiarity with the language will certainly help one's understanding of how and why things work the way they do. One consolation is that the level of understanding essential for using the library is significantly less than the level that one should have in order to modify or extend the library. One more remark on C++ templates: Templates have been a source of both joy and frustration for us. The frustration stems from the lack of mature or complete implementations that one has to work with. Template problems rear their ugly head particularly when porting. When porting C code, successfully compiling to a set of object files typically means that one is almost done. With templated C++ and the current state of the compilers and linkers, generating the object files is often only the beginning of the fun. On the other hand, templates are quite powerful. Used judiciously, templates enable more succinct designs and more efficient code. Templates also help with code maintenance. Designers can avoid creating objects that are the same in many respects, but not exactly the same. For example, FEL fields are templated by node type, thus the code for scalar fields and vector fields is shared. Furthermore, node type templating allows the library user to instantiate fields with data types not provided by the FEL authors. This type of flexibility would be difficult to offer without the support of the language. For users who may be having template-related problems, we offer the consolation that support for C++ templates is destined to improve with time. Efforts such as the Standard Template Library (STL) will inevitably drive vendors to provide more thorough, optimized tools for template code development. Furthermore, the benefits will become harder to resist for those who currently subscribe to the least-common-denominator "code it all in C" strategy. May FEL bring you both increased productivity and aesthetic satisfaction.

Moran, Patrick J.↗