SEARCH · Search NASA
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.
The role of the NASA/DOD Aerospace Knowledge DIffusion Research Project in helping to maintain U.S. competitiveness is addressed. The phases of the project are examined in terms of the focus, emphasis, subjects, methods, and desired outcomes. The importance of the project to aerospace R&D is emphasized.
Federal involvement in simulating economic growth through the development and application of technology policy is currently the subject of serious debate. A recession and the recognition that an internationally competitive economy is a prerequisite for the attainment of national goals have fostered a number of technology policy initiatives aimed at improving the economic competitiveness of American industry. This paper suggests that the successful implementation of U.S. technology policy will require the adoption of a knowledge diffusion model, the development of user oriented information products and services, and a more 'activist' approach on the part of sci/tech librarians in the provision of scientific and technical information (STI). These changes will have a dramatic impact on the sci/tech library of the future and the preparation of sci/tech librarians.
Federal involvement in stimulating economic growth through the development and application of technology policy is currently the subject of serious debate. A recession and the recognition that an internationally competitive economy is a prerequisite for the attainment of national goals have fostered a number of technology policy initiatives aimed at improving the economic competitiveness of American industry. This paper suggests that the successful implementation of U.S. technology policy will require the adoption of a knowledge diffusion model, the development of user oriented information products and services, and a more 'activist' approach on the part of sci/tech librarians in the provision of scientific and technical information (STI). These changes will have a dramatic impact on the sci/tech library of the future and the preparation of sci/tech librarians.
The contents include: 1) What do most KMS in use today assume?; 2) Assumptions are violated when KMS is used by EKP workers - Why?; 3) Current State of KMS for EKPs are inadequate; 4) What would an "adequate" KMS for EKPs look like?; 5) "User-as-Consumer" Analogue: Ecommerce/Eem ployee Services; 6) Why is an ideal KMS for EKPs hard to achieve?; 7) So, what type of KMS design would work?; 8) Human-Based KMS for EKP - Proposal Call Managers at R&DLAB; 9) Proposal Call Managers (PCMs); 10) Specific PCM tasks; 11) Why is a R&DLAB PCM a human metaphor for a KMS for EKP?; 12) Data Collection; 13) Finding #1; 14) Finding #2; 15) Finding #3; 16) Factors affecting How/when; 17) Finding #4; 18) Finding #5; 19) Implication#l for a KMS for EKP: From System to Service; 20) Implication #2: From technology or human-centric to Mixed Mode; 21) Implication #3: From Simple User Profiles to Dynamic Delivery Profiles; 22) Implication #4: Maintaining a trustworthy environment; 23) Implication #5: Constructing a dynamic delivery profile; 24) Implications for Research: Model; and 25) Example Research Qs on KMS Support for EKPs.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Abstract not provided.
There has been a recent push to increase access to electric vehicle (EV) charging infrastructure. The National Electric Vehicle Infrastructure (NEVI) program, part of the Bipartisan Infrastructure Law (BIL) has made significant funding available for major charging infrastructure projects along state thruways, and many state and local incentives exist for EV owners to install chargers in their homes. However, deployment of these chargers has not kept up with demand, primarily due to issues in project planning, permitting processes, and unforeseen delays. This paper serves as a review of the current understanding of these and other non-hardware costs in EV charging infrastructure projects (collectively known as “soft costs”). We found that soft costs in EV charging infrastructure projects are not well understood. Specifically, there is little agreement on how soft costs should be categorized and tracked, and less agreement still on best practices for controlling these costs and lowering barriers to infrastructure deployment. A broader review of EV charging infrastructure cost analyses shows that these costs can have significant impacts on project outcomes. EV charging infrastructure projects may be able to examine the success of the solar industry in lowering soft costs, and a similar effort may lower project costs significantly. Further work on standardizing and collecting data on EV charging infrastructure costs is required to begin addressing and controlling these costs.
Not Available
The primary goal of reusing software components is that software can be developed faster, cheaper and with higher quality. Though, reuse is not automatic and can not just happen. It has to be carefully engineered. For example a component needs to be easily understandable in order to be reused, and it has also to be malleable enough to fit into different applications. In fact the software development process is deeply affected when reuse is being applied. During component development, a serious effort has to be directed toward making these components as reusable. This implies defining reuse coding style guidelines and applying then to any new component to create as well as to any old component to modify. These guidelines should point out the favorable reuse features and may apply to naming conventions, module size and cohesion, internal documentation, etc. During application development, effort is shifted from writing new code toward finding and eventually modifying existing pieces of code, then assembling them together. We see here that reuse is not free, and therefore has to be carefully managed.
This report explains some of the concepts of the ESL prototype and summarizes some of the lessons learned in using the prototype for implementing the Flight Mechanics Tool Kit (FMToolKit) series of Ada programs.
Engineering technology programs are characterized by their focus on application and practice, and by their approximately 50/50 mix of theory and laboratory experience. Engineering technology graduates are employed across the technological spectrum and are often found in areas that deal with application, implementation, and production. Yet we know very little about the communications practices and information-use skills of engineering technology students. In this paper, we report selected results of an exploratory study of engineering technology students enrolled in three U.S. institutions of higher education. Data are presented for the following topics: career goals and aspirations; the importance of, receipt of, and helpfulness of communications and information-use skills instruction; collaborative writing; use of libraries; and the use of electronic (computer) networks.
Explore the source record for details and available documents.
Abstract not provided.
In the life cycle of a complex physical device or part, for example, the docking bay door of the Space Station, there are many uses for knowledge about the device or part. The same piece of knowledge might serve several uses. Given the quantity and complexity of the knowledge that must be stored, it is critical to maintain the knowledge in one repository, in one form. At the same time, because of quantity and complexity of knowledge that must be used in life cycle applications such as cost estimation, re-design, and diagnosis, it is critical to automate such knowledge uses. For each specific use, a knowledge base must be available and must be in a from that promotes the efficient performance of that knowledge base. However, without a single source knowledge repository, the cost of maintaining consistent knowledge between multiple knowledge bases increases dramatically; as facts and descriptions change, they must be updated in each individual knowledge base. A use-neutral representation of a hydraulic system for the F-111 aircraft was developed. The ability to derive portions of four different knowledge bases is demonstrated from this use-neutral representation: one knowledge base is for re-design of the device using a model-based reasoning problem solver; two knowledge bases, at different levels of abstraction, are for diagnosis using a model-based reasoning solver; and one knowledge base is for diagnosis using an associational reasoning problem solver. It was shown how updates issued against the single source use-neutral knowledge repository can be propagated to the underlying knowledge bases.