Abstract: Methods, systems, and media for mitigating defects in battery packs are provided. In some embodiments, a method comprises: (a) monitoring one or more battery parameters associated with one or more battery elements of a battery pack comprising a plurality of battery elements; (b) determining individual status information, each corresponding to one of the one or more battery elements of the battery pack based on the one or more battery parameters; and (c) modifying a use pattern of the battery pack based at least in part by considering an aggregate of the individual status information.

Abstract: Methods, systems, and apparatuses for mitigating battery defects are provided. In some embodiments, a method comprises: monitoring one or more battery parameters associated with a rechargeable battery; obtaining a rate of change of at least one battery parameter of the one or more battery parameters; and determining a defect status of the rechargeable battery based at least in part on the rate of change of the at least one battery parameter.

Abstract: A system, method and computer program product for integrating, managing and coordinating activities of customers in an enterprise, across a plurality of applications, resources and touch-points. Customer data is obtained during interactions between a customer and an application, a resource or a touch-point. This data is stored in the form of virtual composite objects in cache memory, on a cluster of servers. The virtual composite objects contain customer data, policies and behaviors of the enterprise. The applications query for the virtual composite objects through the server. The server hosting the queried virtual composite object delivers the queried virtual composite object in real time to the querying application. Any updates to the virtual composite object on account of events at the applications, resources or touch-points, is carried out in real time.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities. The system includes a hierarchy manager that receives the two different relationship data sets and consolidates the two different relationship data sets into one relationship data set that best expresses the relationship between the two entities.

Abstract: A system, method and computer program product for integrating, managing and coordinating activities of customers in an enterprise, across a plurality of applications, resources and touch-points. Customer data is obtained during interactions between a customer and an application, a resource or a touch-point. This data is stored in the form of virtual composite objects in cache memory, on a cluster of servers. The virtual composite objects contain customer data, policies and behaviors of the enterprise. The applications query for the virtual composite objects through the server. The server hosting the queried virtual composite object delivers the queried virtual composite object in real time to the querying application. Any updates to the virtual composite object on account of events at the applications, resources or touch-points, is carried out in real time.

Abstract: A system, method and computer program product for integrating, managing and coordinating activities of customers in an enterprise, across a plurality of applications, resources and touch-points. Customer data is obtained during interactions between a customer and an application, a resource or a touch-point. This data is stored in the form of virtual composite objects in cache memory, on a cluster of servers. The virtual composite objects contain customer data, policies and behaviors of the enterprise. The applications query for the virtual composite objects through the server. The server hosting the queried virtual composite object delivers the queried virtual composite object in real time to the querying application. Any updates to the virtual composite object on account of events at the applications, resources or touch-points, is carried out in real time.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities. The system includes a hierarchy manager that receives the two different relationship data sets and consolidates the two different relationship data sets into one relationship data set that best expresses the relationship between the two entities.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities. The system includes a hierarchy manager that receives the two different relationship data sets and consolidates the two different relationship data sets into one relationship data set that best expresses the relationship between the two entities.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. However, one of ordinary skill will realize that some embodiments might only track relationships between entities directly associated with an enterprise. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. However, one of ordinary skill will realize that some embodiments might only track relationships between entities directly associated with an enterprise. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. However, one of ordinary skill will realize that some embodiments might only track relationships between entities directly associated with an enterprise. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities.

Abstract: A method and system for searching, filtering, creating, displaying, and managing entity relationships from a repository of data hierarchies through a user interface is provided. Relationships of a primary entity and its related secondary entities are retrieved and displayed in a unified view in graphical or text view. The unified view may indicate a “cross” relationship between first and second entities through another entity that connects the first and second entities, the first and second entities originating from different data hierarchies and/or data sources. Relationships of a selected secondary entity may be displayed in a unified view and entities or relationships may be updated or stored to a separate storage area.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. However, one of ordinary skill will realize that some embodiments might only track relationships between entities directly associated with an enterprise. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities.

Abstract: Some embodiments provide a system for processing relationship data that expresses relationship between various entities. In some embodiments, the entities are entities associated directly with an enterprise. The entities in some embodiments described below also include entities associated indirectly with the enterprise through other entities. However, one of ordinary skill will realize that some embodiments might only track relationships between entities directly associated with an enterprise. In some embodiments, the system consolidates disparate relationship data sets that relate to the same set of entities. For instance, in some embodiments, the system includes several data storages that store relationship data. For at least two entities, at least two different data storages store two different relationship data sets that differently express the relationship between the two entities.

Abstract: An inducer comprising a conically configured hub, a plurality of blades projecting from the hub and a bridge that connects a first blade of two adjacent blades of the plurality of blades to a second blade of the plurality of blades. Each blade of the plurality of blades has a helix shape and is configured as an advancing spiral. The bridge that connects the first blade of two adjacent blades of the plurality of blades to a second blade of the plurality of blades has an airfoil configuration. The bridge is attached to the pressure side of the first blade proximate the leading edge of the first blade and to the suction side of the second blade. Alternatively, the airfoil shaped bridge may be attached to the pressure side of the first blade proximate the trailing edge of the first blade.

Abstract: A centrifugal pump includes a casing containing a volute channel having a cutwater at an entrance thereof. An annular vane-island diffuser is fixed in the casing concentrically within the volute. The diffuser is arranged to be separate and discontinuous from the cutwater of the volute. An impeller rotatably mounted on a shaft is disposed concentrically within the diffuser. The diffuser can be formed, e.g., by an investment casting process, integrally with the casing, or alternatively, independently of it. By arranging the diffuser to be independent of the cutwater of the volute, the diffuser can be “clocked” or “overturned” relative to the cutwater to minimize radial loads on the cutwater and dynamic loads on its leading edge. Additional advantages of the novel design include reductions in pump weight, radial loads, friction loss, design and modeling time, and the energy of outgoing acoustic waves at the pump discharge.

Abstract: A method and a system optimize the performance of an automatic path generation algorithm on a computer network. The system may include routers in the computer network configured into regions according to geographical locations, with some routers being designated inter-region routers in each region. The inter-region routers may be organized to be interconnected in a highly redundant manner (e.g., a full mesh) to ensure connectivity among the regions. Within such a network, when a path is required between routers in different regions, a processor applies the automatic path generation algorithm to: (a) the network segment in the region of the source router to generate a first set of paths, (b) the network segment of the inter-region routers to generate a second set of paths; and (c) the network segment of the destination router to generate a third set of paths, These set of paths are then combined to provide a set of paths between the source and destination routers.

Abstract: In one embodiment of the present invention, a block copolymer with a hydrophilic region and a semifluorinated region is synthesized and mixed, below a critical micellar concentration, with a fluorinated drug, and the temperature then lowered, or the block-copolymer concentration then increased, or other solution conditions changed, in order to form fluorous-core, drug-encapsulating micelles. Alternatively, a drug may be taken up by already formed micelles in solution. A suspension of the fluorous-core, fluorinated-drug-encapsulating micelles is injected into the bloodstream to deliver the fluorinated drug to target tissues and organs. In an alternative embodiment of the present invention, a block copolymer with a hydrophilic block, a hydrophobic block, and a semifluorinated block is used to form fluorous-core, drug-encapsulating micelles.

Abstract: Methods and apparatus for conveying fluids (e.g., liquids, gases, and mixtures thereof) are disclosed. A turbopump in accordance with an exemplary implementation of the present invention comprises an impeller defining at least one flow channel and a shroud defining an opening communicating with the at least one flow channel. In certain advantageous implementations, at least one inlet partial of the impeller extends into the opening defined by the shroud. The at least one inlet partial may advantageously be capable of supporting the opening in the shroud. In some cases, the impeller may include a plurality of these inlet partials.

Abstract: A system, method and computer program product for integrating, managing and coordinating activities of customers in an enterprise, across a plurality of applications, resources and touch-points. Customer data is obtained during interactions between a customer and an application, a resource or a touch-point. This data is stored in the form of virtual composite objects in cache memory, on a cluster of servers. The virtual composite objects contain customer data, policies and behaviors of the enterprise. The applications query for the virtual composite objects through the server. The server hosting the queried virtual composite object delivers the queried virtual composite object in real time to the querying application. Any updates to the virtual composite object on account of events at the applications, resources or touch-points, is carried out in real time.