Search NASA⌕ Search

SEARCH · Search NASA

Results for “work function customization”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

XBoard: A Framework for Integrating and Enhancing Collaborative Work Practices

Teams typically collaborate in different modes including face-to-face meetings, meetings that are synchronous (i. e. require parties to participate at the same time) but distributed geographically, and meetings involving asynchronously working on common tasks at different times. The XBoard platform was designed to create an integrated environment for creating applications that enhance collaborative work practices. Specifically, it takes large, touch-screen enabled displays as the starting point for enhancing face-to-face meetings by providing common facilities such as whiteboarding/electronic flipcharts, laptop projection, web access, screen capture and content distribution. These capabilities are built upon by making these functions inherently distributed by allowing these sessions to be easily connected between two or more systems at different locations. Finally, an information repository is integrated into the functionality to provide facilities for work practices that involve work being done at different times, such as reports that span different shifts. The Board is designed to be extendible allowing customization of both the general functionality and by adding new functionality to the core facilities by means of a plugin architecture. This, in essence, makes it a collaborative framework for extending or integrating work practices for different mission scenarios. XBoard relies heavily on standards such as Web Services and SVG, and is built using predominately Java and well-known open-source products such as Apache and Postgres. Increasingly, organizations are geographically dispersed, and rely on "virtual teams" that are assembled from a pool of various partner organizations. These organizations often have different infrastructures of applications and workflows. The XBoard has been designed to be a good partner in these situations, providing the flexibility to integrate with typical legacy applications while providing a standards-based infrastructure that is readily accepted by most organizations. The XBoard has been used on the Mars Exploration Rovers mission at JPL, and is currently being used or considered for use in pilot projects at Johnson Space Center (JSC) Mission Control, the University of Arizona Lunar and Planetav Laboratory (Phoenix Mars Lander), and MBART (Monterey Bay Aquarium Research Institute).

Shab, Ted↗
NASA NTRSDate not supplied

Custom Integration of Multiple Medical Functionalities

INTRODUCTION: Previous spaceflight experience and results from probabilistic risk assessment of spaceflight medical risk have highlighted the need for vital sign measurements, medical scopes, and clinical imaging tools for managing medical conditions during spaceflight. The Human Research Program’s Exploration Medical Capability (ExMC) Element and the Mars Campaign Office’s Exploration Medical Integrated Product Team (XMIPT) have performed ground-based evaluations of two Commercial-off-the-Shelf (COTS) Multi-functional Integrated Medical (MIM) devices, which integrate various medical capabilities together in one device. The key findings from these evaluations are presented in a complementary presentation, leaving this presentation to focus on forward recommendations for customized integration of multiple medical functionalities. KEY COMPONENTS: The key features of a custom integration of multiple medical functionalities includes devices and capabilities that optimally reduce medical risk. The COTS MIM devices incorporated functionality for best supporting Earth-based, emergency, pre-hospital care. Our custom integration will use probabilistic risk assessment tools, such as the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT), to determine the optimal functionality to include based on medical risk minimization. An additional feature of custom integration includes the ability to adapt to different requirements within different vehicles and/or missions. The COTS MIM devices store data in patient specific records, however, the format of the records is not modifiable, and data are not easily transferred from the MIM device to a central data architecture outside of the manufacturer’s established system. Our concept for custom integration will use devices that have an open application programming interface, which can easily connect to independent data architectures and third-party visualization software. The ultrasound capabilities included within the COTS MIM devices did not satisfy many of the Artemis Research and Operations Working Group’s ultrasound functional needs, and therefore, incorporation of higher quality ultrasound capabilities within a customized integration will be beneficial. The COTS MIM devices included minimal procedural guidance and clinical decision support tools. Supplemental tools of this type would need to be supplied along with the COTS MIM devices if they were to be used operationally, so another advantage of customization is the ability to integrate these support tools along with the medical functionality, for a more streamlined user experience. CONCLUSION: Investigation of a customized integration of medical functionality provides a method for further understanding the needs of a long-term exploration spaceflight medical system. The crew members of these exploration missions will need to operate more and more independently from Earth-based ground support. Therefore, having an optimized, streamlined medical system, which contains the functionality and supporting information needed, while remaining within mission and vehicle constraints, will help to maintain crew health and performance, which is necessary for achieving high levels of mission success.

B E Lewandowski↗
NASA NTRS2006

A Comparison of Functional Models for Use in the Function-Failure Design Method

When failure analysis and prevention, guided by historical design knowledge, are coupled with product design at its conception, shorter design cycles are possible. By decreasing the design time of a product in this manner, design costs are reduced and the product will better suit the customer s needs. Prior work indicates that similar failure modes occur with products (or components) with similar functionality. To capitalize on this finding, a knowledge base of historical failure information linked to functionality is assembled for use by designers. One possible use for this knowledge base is within the Elemental Function-Failure Design Method (EFDM). This design methodology and failure analysis tool begins at conceptual design and keeps the designer cognizant of failures that are likely to occur based on the product s functionality. The EFDM offers potential improvement over current failure analysis methods, such as FMEA, FMECA, and Fault Tree Analysis, because it can be implemented hand in hand with other conceptual design steps and carried throughout a product s design cycle. These other failure analysis methods can only truly be effective after a physical design has been completed. The EFDM however is only as good as the knowledge base that it draws from, and therefore it is of utmost importance to develop a knowledge base that will be suitable for use across a wide spectrum of products. One fundamental question that arises in using the EFDM is: At what level of detail should functional descriptions of components be encoded? This paper explores two approaches to populating a knowledge base with actual failure occurrence information from Bell 206 helicopters. Functional models expressed at various levels of detail are investigated to determine the necessary detail for an applicable knowledge base that can be used by designers in both new designs as well as redesigns. High level and more detailed functional descriptions are derived for each failed component based on NTSB accident reports. To best record this data, standardized functional and failure mode vocabularies are used. Two separate function-failure knowledge bases are then created aid compared. Results indicate that encoding failure data using more detailed functional models allows for a more robust knowledge base. Interestingly however, when applying the EFDM, high level descriptions continue to produce useful results when using the knowledge base generated from the detailed functional models.

Stock, Michael E.↗
NASA NTRS2012

Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge of the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments disciplines that will help serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environments and spacecraft effects (SENSE) organization. This SENSE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Engineering effects focuses on the material, component, sub-system and system-level selection and the testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope of the TWGs and their relationship to the functional areas, and discuss an organizational structure for this space environments and spacecraft effects organization.

Edwards, David L.↗
NASA NTRS2012

An Overview of the Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore our Earth, and the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge on the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments fields that will serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environment and spacecraft effects (SESE) organization. This SESE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems, and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Environment effects focuses on the material, component, sub-system, and system-level response to the space environment and include the selection and testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope and purpose of the space environments and spacecraft effects organization and describe the TWG's and their relationship to the functional areas.

Edwards, David L.↗
NASA NTRS2011

Development of the ISS EMU SPEEDR

The Self Powered EVA EMU Data Recorder (SPEEDR) is an FPGA (Field-programmable gate array) based device designed to collect high-rate EMU (Extravehicular Mobility Unit) PLSS (Primary Life Support Subsystem) data for download at a later time. The existing EMU PLSS data down-link capability during EVA is one data packet every 2 minutes and is subject to bad packets or loss of signal. High-rate PLSS data is generated by the ECWS (Enhanced Caution and Warning System) but is not normally captured or distributed. Access to high-rate data will increase the capability of EMU anomaly resolution team to pinpoint issues remotely, saving crew time by reducing required call-down Q&A and on-orbit diagnostic activities. With no Shuttle flights post FY11, and potentially limited down-mass capability, the ISS crew and ground support personnel will have to be capable of on-orbit operations to maintain, diagnose, repair, and return to service EMU hardware, possibly through 2028. Collecting high-rate EMU PLSS data during both IVA (Intravehicular Activity) and EVA (Extravehicular Activity) operations will provide trending analysis for life extension and/or predictive performance. The SPEEDR concept has generated interest as a tool/technology that could be used for other ISS subsystems or future exploration-class space suits where hardware reliability/availability is critical and low/variable bandwidth may require "store then forward" methodology. Preliminary work in FY11 produced a functional prototype consisting of an FPGA evaluation board, custom memory/interface circuit board, and custom software. The SPEEDR concept includes a stand-alone battery that is recharged by a computer USB (Universal Serial Bus) port while data is being downloaded.

Bernard. Craig↗
NASA NTRS2012

Development of the Self-Powered Extravehicular Mobility Unit Extravehicular Activity Data Recorder

The Self-Powered Extravehicular Mobility Unit (EMU) Extravehicular Activity (EVA) Data Recorder (SPEEDR) is a field-programmable gate array (FPGA)-based device designed to collect high-rate EMU Primary Life Support Subsystem (PLSS) data for download at a later time. During EVA, the existing EMU PLSS data downlink capability is one data packet every 2 minutes and is subject to bad packets or loss of signal. Higher-rate PLSS data is generated by the Enhanced Caution and Warning System but is not normally captured or distributed. Access to higher-rate data will increase the capability of EMU anomaly resolution team to pinpoint issues remotely, saving crew time by reducing required call-down Q&A and on-orbit diagnostic activities. With no Space Shuttle flights post Fiscal Year 2011 (FY11), and potentially limited down-mass capability, the ISS crew and ground support personnel will have to be capable of on-orbit operations to maintain, diagnose, repair, and return to service EMU hardware, possibly through 2028. Collecting high-rate EMU PLSS data during both intravehicular activity (IVA) and EVA operations will provide trending analysis for life extension and/or predictive performance. The SPEEDR concept has generated interest as a tool/technology that could be used for other International Space Station subsystems or future exploration-class space suits where hardware reliability/availability is critical and low/variable bandwidth may require store then forward methodology. Preliminary work in FY11 produced a functional prototype consisting of an FPGA evaluation board, custom memory/interface circuit board, and custom software. The SPEEDR concept includes a stand-alone battery that is recharged by a computer Universal Serial Bus (USB) port while data are being downloaded.

Bernard, Craig↗
NASA NTRS1992

SATWG networked quality function deployment

The initiative of this work is to develop a cooperative process for continual evolution of an integrated, time phased avionics technology plan that involves customers, technologists, developers, and managers. This will be accomplished by demonstrating a computer network technology to augment the Quality Function Deployment (QFD). All results are presented in viewgraph format.

Brown, Don↗
NASA NTRS1992

The power of cross-functional teams in driving total quality

Garrett Canada, a Division of Allied-Signal Aerospace Canada, has been a member of the Canadian aerospace industry for 40 years. Although Garrett Canada has always been a profitable division with a solid market share, the changing and turbulent business environment and globalization of the aerospace industry has created new demands and challenges. The marketplace is demanding faster introduction of new products, as well as shorter leadtimes for repairs and spares. It was recognized that reducing cycle times for new products and for ongoing production would not only satisfy our customers, it would also enhance our business performance through reduced inventories, lower past due, and more responsiveness to change. It was evident that drastic function changes were required if we were to maintain our position as a premier aerospace supplier. The challenge was to convert a stable, somewhat slow-paced work environment with strong functional boundaries into a boundaryless world class team functioning in a total quality environment and focused on customer satisfaction. Complete and uncompromised customer satisfaction has become our driving force, with Total Quality being our engine to continuously improve our processes and increase our speed. The way in which this transition has been brought about is the subject of this presentation.

Mcclung, Tim M.↗
NASA NTRS2017

OpenSatKit Enables Quick Startup for CubeSat Missions

The software required to develop, integrate, and operate a spacecraft is substantial regardless of whether its a large or small satellite. Even getting started can be a monumental task. To solve this problem, NASAs Core Flight System (cFS), NASA's 42 spacecraft dynamics simulator, and Ball Aerospaces COSMOS ground system have been integrated together into a kit called OpenSatKit that provides a complete and open source software solution for starting a new satellite mission. Users can have a working system with flight software, dynamics simulation, and a ground command and control system up and running within hours.Every satellite mission requires three primary categories of software to function. The first is Flight Software (FSW) which provides the onboard control of the satellites and its payload(s). NASA's cFS provides a great platform for developing this software. Second, while developing a satellite on earth, it is necessary to simulate the satellites orbit, attitude, and actuators, to ensure that the systems that control these aspects will work correctly in the real environment. NASAs 42 simulator provides these functionalities. Finally, the ground has to be able to communicate with the satellite, monitor its performance and health, and display its data. Additionally, test scripts have to be written to verify the system on the ground. Ball Aerospace's COSMOS command and control system provides this functionality. Once the OpenSatKit is up and running, the next step is to customize the platform and get it running on the end target. Starting from a fully working system makes porting the cFS from Linux to a users platform much easier. An example Raspberry Pi target is included in the kit so users can gain experience working with a low cost hardware target. All users can benefit from OpenSatKit but the greatest impact and benefits will be to SmallSat missions with constrained budgets and small software teams. This paper describes OpenSatKits system design, the steps necessary to run the system to target the Raspberry Pi, and future plans. OpenSatKit is a free fully functional spacecraft software system that we hope will greatly benefit the SmallSat community.

Software↗
NASA NTRS1995

An Overview of the Quality Function Deployment (QFD) Technique

QFD is a product planning tool and a process methodology that enables all organizations, departments, and individuals in a business or a project to systematically focus on the critical performance, functions, and/or characteristics of a product that are the most important to the customer. It is part of the Total Quality Management (TQM) concept.. This presentation describes the objectives of QFD, the process for implementing the technique, the benefits derived from proper implementation, the kinds of systems where QFD is best utilized, what the success factors are, how QFD works, some guidelines for selection of a QFD team, and the functional roles of key team members.

Quality Function Deployment QFD customer focus cus↗
NASA NTRS2004

Office of Equal Opportunity Programs

The NASA Glenn Office of Equal Opportunity Programs works to provide quality service for all programs and/or to assist the Center in becoming a model workplace. During the summer of 2004, I worked with Deborah Cotleur along with other staff members to create and modify customer satisfaction surveys. This office aims to assist in developing a model workplace by providing functions as a change agent to the center by serving as an advisor to management to ensure equity throughout the Center. In addition, the office serves as a mediator for the Center in addressing issues and concerns. Lastly, the office provides assistance to employees to enable attainment of personal and organizational goals. The Office of Equal Opportunities is a staff office which reports and provides advice to the Center Director and Executive Leadership, implements laws, regulations, and presidential executive orders, and provides center wide leadership and assistance to NASA GRC employees. Some of the major responsibilities of the office include working with the discrimination complaints program, special emphasis programs (advisory groups), management support, monitoring and evaluation, contract compliance, and community outreach. During my internship in this office, my main objective was to create four customer satisfaction surveys based on EO retreats, EO observances, EO advisory boards, and EO mediation/counseling. I created these surveys after conducting research on past events and surveys as well as similar survey research created and conducted by other NASA centers, program for EO Advisory group members, leadership training sessions for supervisors, preventing sexual harassment training sessions, and observance events. I also conducted research on the style and format from feedback surveys from the Marshall Equal Opportunity website, the Goddard website, and the main NASA website. Using the material from the Office of Equal Opportunity Programs at Glenn Research Center along with my previous research, I created four customer satisfaction surveys. Additional information is included in the original extended abstract.

Chin, Jennifer L.↗
NASA NTRSDate not supplied

Development of Multi-Edge Slant Target for Unlocalized MTF Measurement of Airborne Imaging System Payloads

Calibration of imaging instruments is a critical step in effectively characterizing imaging data. A comprehensive characterization of an imaging system provides valuable insight into the overall uncertainties in the results derived from the raw data collected. The Scientifically Calibrated In-Flight Imagery (SCIFLI) team (based at NASA Langley Research Center) has designed, built, tested, and successfully flown the optical payload known as the SCIFLI Airborne Multispectral Imager (SAMI). SAMI is a multispectral imaging payload, complete with sensor configurations for the Ultraviolet-Visible spectrum as well as Near- Infrared, Shortwave Infrared, and Midwave Infrared bands and is fitted with various optical hardware designed to turn, split, and focus light beams to the respective in-band sensors. Radiometric calibrations are performed for SAMI such that the accuracy and uncertainty of thermal and spectral measurements are effectively characterized. However, SAMI does not regularly undergo spatial characterizations to evaluate the performance of the imager at high spatial frequencies. This is essential, as understanding the spatial sensor response of discrete sensors is just as important as the spectral sensor response. The payload currently utilizes a calibration cart for lab testing. Equipped with a modular setup and several radiation sources, it is perfect for performing high-quality radiometric calibrations. This work focuses on using the calibration cart to perform spatial calibrations. A custom designed calibration target is being used to evaluate the optical performance of SAMI. Specifically, the target is designed to measure the Modulation Transfer Function (MTF) of the imager in discrete locations around the focal plane. The results of this characterization will provide insight into the spatial resolution capabilities of the SAMI payload in practice. Future work includes using the results of the study to correct optical imperfections in imagery taken with SAMI.

SAMI↗
NASA NTRS2019

The Cumulus Ecosystem: Open Source and Beyond to Foster Collaboration

NASA’s Earth Observing System Data and Information System (EOSDIS) open source Cumulus software is designed as a common set of code and services that can be used to create a pipeline to deliver and manage earth science data in the cloud. Cumulus strives to create an ecosystem on the foundation of open source that unites those with shared problems and goals by encouraging users to contribute solutions back to the platform. Large parts of ingesting and managing data are common and much of what is created can be used by others. Our goal is to maximize collaboration and code reuse while allowing users to design a custom solution that meets their needs without having to take on extraneous functionality. In this talk we will describe how the Cumulus ecosystem works beyond just open source software. We will review the technology, the successes and challenges, and the evolution and future of Cumulus as an ecosystem.

Cumulus↗
NASA NTRS2012

ASIC Readout Circuit Architecture for Large Geiger Photodiode Arrays

The objective of this work was to develop a new class of readout integrated circuit (ROIC) arrays to be operated with Geiger avalanche photodiode (GPD) arrays, by integrating multiple functions at the pixel level (smart-pixel or active pixel technology) in 250-nm CMOS (complementary metal oxide semiconductor) processes. In order to pack a maximum of functions within a minimum pixel size, the ROIC array is a full, custom application-specific integrated circuit (ASIC) design using a mixed-signal CMOS process with compact primitive layout cells. The ROIC array was processed to allow assembly in bump-bonding technology with photon-counting infrared detector arrays into 3-D imaging cameras (LADAR). The ROIC architecture was designed to work with either common- anode Si GPD arrays or common-cathode InGaAs GPD arrays. The current ROIC pixel design is hardwired prior to processing one of the two GPD array configurations, and it has the provision to allow soft reconfiguration to either array (to be implemented into the next ROIC array generation). The ROIC pixel architecture implements the Geiger avalanche quenching, bias, reset, and time to digital conversion (TDC) functions in full-digital design, and uses time domain over-sampling (vernier) to allow high temporal resolution at low clock rates, increased data yield, and improved utilization of the laser beam.

Vasile, Stefan↗
NASA NTRS2003

A Study of Technical Engineering Peer Reviews at NASA

This report describes the state of practices of design reviews at NASA and research into what can be done to improve peer review practices. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review and Critical Design Review are a required part of every project and mission development. However, the technical, engineering peer reviews that support teams' work on such projects are informal, some times ad hoc, and inconsistent across the organization. The goal of this work is to identify best practices and lessons learned from NASA's experience, supported by academic research and methodologies to ultimately improve the process. This research has determined that the organization, composition, scope, and approach of the reviews impact their success. Failure Modes and Effects Analysis (FMEA) can identify key areas of concern before or in the reviews. Product definition tools like the Project Priority Matrix, engineering-focused Customer Value Chain Analysis (CVCA), and project or system-based Quality Function Deployment (QFD) help prioritize resources in reviews. The use of information technology and structured design methodologies can strengthen the engineering peer review process to help NASA work towards error-proofing the design process.

Chao, Lawrence P.↗
NASA NTRS2012

The Namibia Early Flood Warning System, A CEOS Pilot Project

Over the past year few years, an international collaboration has developed a pilot project under the auspices of Committee on Earth Observation Satellite (CEOS) Disasters team. The overall team consists of civilian satellite agencies. For this pilot effort, the development team consists of NASA, Canadian Space Agency, Univ. of Maryland, Univ. of Colorado, Univ. of Oklahoma, Ukraine Space Research Institute and Joint Research Center(JRC) for European Commission. This development team collaborates with regional , national and international agencies to deliver end-to-end disaster coverage. In particular, the team in collaborating on this effort with the Namibia Department of Hydrology to begin in Namibia . However, the ultimate goal is to expand the functionality to provide early warning over the South Africa region. The initial collaboration was initiated by United Nations Office of Outer Space Affairs and CEOS Working Group for Information Systems and Services (WGISS). The initial driver was to demonstrate international interoperability using various space agency sensors and models along with regional in-situ ground sensors. In 2010, the team created a preliminary semi-manual system to demonstrate moving and combining key data streams and delivering the data to the Namibia Department of Hydrology during their flood season which typically is January through April. In this pilot, a variety of moderate resolution and high resolution satellite flood imagery was rapidly delivered and used in conjunction with flood predictive models in Namibia. This was collected in conjunction with ground measurements and was used to examine how to create a customized flood early warning system. During the first year, the team made use of SensorWeb technology to gather various sensor data which was used to monitor flood waves traveling down basins originating in Angola, but eventually flooding villages in Namibia. The team made use of standardized interfaces such as those articulated under the Open Cloud Consortium (OGC) Sensor Web Enablement (SWE) set of web services was good [1][2]. However, it was discovered that in order to make a system like this functional, there were many performance issues. Data sets were large and located in a variety of location behind firewalls and had to be accessed across open networks, so security was an issue. Furthermore, the network access acted as bottleneck to transfer map products to where they are needed. Finally, during disasters, many users and computer processes act in parallel and thus it was very easy to overload the single string of computers stitched together in a virtual system that was initially developed. To address some of these performance issues, the team partnered with the Open Cloud Consortium (OCC) who supplied a Computation Cloud located at the University of Illinois at Chicago and some manpower to administer this Cloud. The Flood SensorWeb [3] system was interfaced to the Cloud to provide a high performance user interface and product development engine. Figure 1 shows the functional diagram of the Flood SensorWeb. Figure 2 shows some of the functionality of the Computation Cloud that was integrated. A significant portion of the original system was ported to the Cloud and during the past year, technical issues were resolved which included web access to the Cloud, security over the open Internet, beginning experiments on how to handle surge capacity by using the virtual machines in the cloud in parallel, using tiling techniques to render large data sets as layers on map, interfaces to allow user to customize the data processing/product chain and other performance enhancing techniques. The conclusion reached from the effort and this presentation is that defining the interoperability standards in a small fraction of the work. For example, once open web service standards were defined, many users could not make use of the standards due to security restrictions. Furthermore, once an interoperable sysm is functional, then a surge of users can render a system unusable, especially in the disaster domain.

Mandl, Daniel↗
NASA NTRS1989

AdaNET prototype library administration manual

The functions of the AdaNET Prototype Library of Reusable Software Parts is described. Adopted from the Navy Research Laboratory's Reusability Guidebook (V.5.0), this is a working document, customized for use the the AdaNET Project. Within this document, the term part is used to denote the smallest unit controlled by a library and retrievable from it. A part may have several constituents, which may not be individually tracked. Presented are the types of parts which may be stored in the library and the relationships among those parts; a concept of trust indicators which provide measures of confidence that a user of a previously developed part may reasonably apply to a part for a new application; search and retrieval, configuration management, and communications among those who interact with the AdaNET Prototype Library; and the AdaNET Prototype, described from the perspective of its three major users: the part reuser and retriever, the part submitter, and the librarian and/or administrator.

Hanley, Lionel↗