An Assessment of PIER Electric Grid Research 2003-2014 White Paper

This white paper describes the circumstances in California around the turn of the 21st century that led the California Energy Commission (CEC) to direct additional Public Interest Energy Research funds to address critical electric grid issues, especially those arising from integrating high penetrations of variable renewable generation with the electric grid. It contains an assessment of the beneficial science and technology advances of the resultant portfolio of electric grid research projects administered under the direction of the CEC by a competitively selected contractor, the University of California’s California Institute for Energy and the Environment, from 2003-2014

A Prototype Industrial Maintenance Software System to Apply a Proactive Approach to Equipment Failure

This project proposes a technical solution to create a proactive approach to industrial equipment maintenance for a large paper manufacturing facility. The traditional method for scheduling maintenance on manufacturing equipment uses a reactive approach. Reactive maintenance essentially means to perform repairs on equipment after failure has occurred; the process of these repairs begins by acquiring needed replacement part(s) utilizing a SAP (Systems Applications Products) system for authorization and ordering. Actual repairs are carried out by craftsmen based on their general knowledge of a specific trade and any previous experience concerning the failed equipment. The part(s) order through the SAP system must be cross referenced to a storeroom catalog to obtain required serial numbers associated with specific parts; this is a time consuming procedure which adds considerable downtime to the equipment in need of repair. This reactive approach to equipment repair results in a loss of equipment availability, component damage, and inefficient use of maintenance resources. The goal of this project is to produce a prototype of a software system that will demonstrate the ability to increase equipment availability by utilizing a proactive approach to industrial maintenance. The prototype will include an equipment specific monitoring system, and a relational database system for storing equipment information

Space biology initiative program definition review. Trade study 2: Prototype utilization in the development of space biology hardware

The objective was to define the factors which space flight hardware developers and planners should consider when determining: (1) the number of hardware units required to support program; (2) design level of the units; and (3) most efficient means of utilization of the units. The analysis considered technology risk, maintainability, reliability, and safety design requirements for achieving the delivery of highest quality flight hardware. Relative cost impacts of the utilization of prototyping were identified. The development of Space Biology Initiative research hardware will involve intertwined hardware/software activities. Experience has shown that software development can be an expensive portion of a system design program. While software prototyping could imply the development of a significantly different end item, an operational system prototype must be considered to be a combination of software and hardware. Hundreds of factors were identified that could be considered in determining the quantity and types of prototypes that should be constructed. In developing the decision models, these factors were combined and reduced by approximately ten-to-one in order to develop a manageable structure based on the major determining factors. The Baseline SBI hardware list of Appendix D was examined and reviewed in detail; however, from the facts available it was impossible to identify the exact types and quantities of prototypes required for each of these items. Although the factors that must be considered could be enumerated for each of these pieces of equipment, the exact status and state of development of the equipment is variable and uncertain at this time

Execution of a Hybrid Vehicle Controls Development Effort Utilizing Model-Based Design, Hardware-in-the-loop Testing, Agile Scrum Methods and Requirements Engineering

Modern hybrid vehicles require sophisticated supervisory control systems in order to realize competitive efficiency gains. Processes such as model-based design, HIL simulation and Agile Scrum methods can allow for quicker and less costly development of a complex product. The design of a supervisory control system for a prototype PHEV vehicle was executed with the intent of developing a mule vehicle into a 99% production ready vehicle. The control system design process was carried through from requirements definition to operating parameter optimization of utilizing model-based design, HIL simulation and the Scrum model. A prototype vehicle that has a fully functioning hybrid system with innovative propulsion control methods has been produced by this process

Developing a distributed electronic health-record store for India

The DIGHT project is addressing the problem of building a scalable and highly available information store for the Electronic Health Records (EHRs) of the over one billion citizens of India

Working Notes from the 1992 AAAI Workshop on Automating Software Design. Theme: Domain Specific Software Design

The goal of this workshop is to identify different architectural approaches to building domain-specific software design systems and to explore issues unique to domain-specific (vs. general-purpose) software design. Some general issues that cut across the particular software design domain include: (1) knowledge representation, acquisition, and maintenance; (2) specialized software design techniques; and (3) user interaction and user interface

Adaptive object management for distributed systems

This thesis describes an architecture supporting the management of pluggable software components and evaluates it against the requirement for an enterprise integration platform for the manufacturing and petrochemical industries. In a distributed environment, we need mechanisms to manage objects and their interactions. At the least, we must be able to create objects in different processes on different nodes; we must be able to link them together so that they can pass messages to each other across the network; and we must deliver their messages in a timely and reliable manner. Object based environments which support these services already exist, for example ANSAware(ANSA, 1989), DEC's Objectbroker(ACA,1992), Iona's Orbix(Orbix,1994)Yet such environments provide limited support for composing applications from pluggable components. Pluggability is the ability to install and configure a component into an environment dynamically when the component is used, without specifying static dependencies between components when they are produced. Pluggability is supported to a degree by dynamic binding. Components may be programmed to import references to other components and to explore their interfaces at runtime, without using static type dependencies. Yet thus overloads the component with the responsibility to explore bindings. What is still generally missing is an efficient general-purpose binding model for managing bindings between independently produced components. In addition, existing environments provide no clear strategy for dealing with fine grained objects. The overhead of runtime binding and remote messaging will severely reduce performance where there are a lot of objects with complex patterns of interaction. We need an adaptive approach to managing configurations of pluggable components according to the needs and constraints of the environment. Management is made difficult by embedding bindings in component implementations and by relying on strong typing as the only means of verifying and validating bindings. To solve these problems we have built a set of configuration tools on top of an existing distributed support environment. Specification tools facilitate the construction of independent pluggable components. Visual composition tools facilitate the configuration of components into applications and the verification of composite behaviours. A configuration model is constructed which maintains the environmental state. Adaptive management is made possible by changing the management policy according to this state. Such policy changes affect the location of objects, their bindings, and the choice of messaging system

Space benefits: The secondary application of aerospace technology in other sectors of the economy

Benefit cases of aerospace technology utilization are presented for manufacturing, transportation, utilities, and health. General, organization, geographic, and field center indexes are included