Abstract: A refuse collection system includes a refuse collection robot and a refuse depot. The refuse collection robot includes a chassis, a tractive element coupled to the chassis, a motor coupled to the chassis and the tractive element and configured to drive the tractive element to propel the refuse collection robot, a refuse container coupled to the chassis and defining a first storage volume, and a controller operatively coupled to the motor. The refuse depot includes a centralized storage defining a second storage volume and a refuse actuator configured to transfer refuse from the first storage volume to the second storage volume. The controller is configured to control the motor to propel the refuse collection to a pickup zone associated with a customer in response to receiving a request for refuse collection from a user device associated with the customer.

Abstract: A depot for autonomous land-based refuse drones includes a chassis anchored to a ground surface, a container defining a storage volume for refuse, a collection implement, and refuse actuators. The collection implement is configured to selectively couple with at least one of (i) refuse within a drone storage volume or (ii) a portion of the one of the autonomous land-based refuse drones that defines the drone storage volume. The refuse actuators are operably coupled with the collection implement and configured to drive the collection implement to perform an unloading operation. The unloading operation includes selectively coupling, moving, and de-coupling from at least one of the refuse within the drone storage volume or the portion of the autonomous land-based refuse drone that defines the drone storage volume to unload the refuse from the drone storage volume into the storage volume of the container.

Abstract: A refuse collection includes one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to (a) receive a request for refuse collection from a customer, the request including a desired time of the refuse collection, (b) identify, based on the request, a location of a pickup zone associated with the customer, and (c) control, based on the request, the refuse collection robot to autonomously navigate to the location of the pickup zone at the desired time and perform the refuse collection.

Abstract: A refuse collection drone includes a chassis, tractive elements rotatably coupled with and supporting the chassis, a propulsion system including a battery and an electric motor configured to consume electrical energy from the battery, and a bin removably coupled with the chassis and including a cover. The propulsion system is configured to drive one or more of the tractive elements to transport the refuse collection drone to a customer location. The bin defines a storage volume for refuse. The cover is configured to be driven by an actuator between an open position to allow access to the storage volume and a closed position to limit access to the storage volume. A lock is operable between a locked state to limit transition of the cover out of the closed position and an unlocked state to allow transition of the cover out of the closed position and into the open position.

Abstract: A refuse collection system includes one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to (a) receive a request for refuse collection from a customer, (b) identify, based on the request, a location of a pickup zone associated with the customer, (c) receive location data indicating a current location of the refuse collection robot, (d) generate a route for the refuse collection robot to travel from the current location of the refuse collection robot to the location of the pickup zone, and (e) control the refuse collection robot to follow the route and perform the refuse collection.

Abstract: A refuse collection system includes one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to (a) control a refuse collection robot containing a volume of refuse to navigate to a refuse depot, (b) control the refuse depot to remove the volume of refuse from the refuse collection robot, (c) receive a request from a customer for delivery of a package, (d) identify, based on the request, a location of a pickup zone associated with the customer, (e) control the refuse collection robot to receive the package, and (f) control the refuse collection robot to transport the package to the pickup zone.

Abstract: Antimicrobial metal ion coatings and implants including them. In particular, described herein are coatings including an anodic metal (e.g., silver and/or zinc and/or copper) that is co-deposited with a cathodic metal (e.g., palladium, platinum, gold, molybdenum, titanium, iridium, osmium, rhodium, manganese, niobium or rhenium) on a substrate so that the anodic metal is galvanically released as antimicrobial ions when the apparatus is exposed to a bodily fluid. The anodic metal may be at least about 25 percent by volume of the coating, resulting in a network of anodic metal with less than 20% of the anodic metal in the coating fully encapsulated by cathodic metal. The implant may be configured as an implant such as a bone-screw or intramedullary rod-like body configured to receive a treatment cartridge having a coating as described.

Abstract: Implementations include actions of receiving consumer-specific data and ID-specific data from an identification presented by a consumer to a vending machine, processing at least a portion of the ID-specific data to determine one or more of whether the identification is unexpired and whether the identification is authentic, and serving the consumer from the vending machine at least partially in response to determining that the identification is unexpired and that the identification is authentic and determining that the consumer is authentic relative to the identification.

Abstract: Implementations include actions of receiving consumer-specific data and ID-specific data from an identification presented by a consumer to a vending machine, processing at least a portion of the ID-specific data to determine one or more of whether the identification is unexpired and whether the identification is authentic, and serving the consumer from the vending machine at least partially in response to determining that the identification is unexpired and that the identification is authentic and determining that the consumer is authentic relative to the identification.

Abstract: Implementations include actions of receiving consumer-specific data and ID-specific data from an identification presented by a consumer to a vending machine, processing at least a portion of the ID-specific data to determine one or more of whether the identification is unexpired and whether the identification is authentic, and serving the consumer from the vending machine at least partially in response to determining that the identification is unexpired and that the identification is authentic and determining that the consumer is authentic relative to the identification.

Abstract: A front suspension system is provided for a front-wheel drive vehicle having a drive shaft for driving a front wheel. The front suspension system includes a suspension device configured to be connected to the vehicle, a control arm configured to be connected to the vehicle, and a yoke mount configured to connect the suspension device to the control arm. The yoke mount has first and second legs that receive the drive shaft therebetween when the front suspension system is mounted on the vehicle.

Abstract: A rear suspension for a vehicle includes a knuckle for supporting a rear wheel of the vehicle, and the knuckle defines an opening. The rear suspension system further includes two suspension devices configured to be connected to the vehicle and an upper portion of the knuckle, such that each suspension device is oriented along an upright axis when the rear suspension system is mounted on the vehicle. In addition, the rear suspension system includes a control arm having a first portion configured to be connected to the vehicle and a second portion configured to extend between the axes of the suspension devices and into the opening of the knuckle when the rear suspension system is mounted on the vehicle.

Abstract: A front suspension system is provided for a front-wheel drive vehicle having a drive shaft for driving a front wheel. The front suspension system includes a suspension device configured to be connected to the vehicle, a control arm configured to be connected to the vehicle, and a yoke mount configured to connect the suspension device to the control arm. The yoke mount has first and second legs that receive the drive shaft therebetween when the front suspension system is mounted on the vehicle.

Abstract: A rear suspension for a vehicle includes a knuckle for supporting a rear wheel of the vehicle, and the knuckle defines an opening. The rear suspension system further includes two suspension devices configured to be connected to the vehicle and an upper portion of the knuckle, such that each suspension device is oriented along an upright axis when the rear suspension system is mounted on the vehicle. In addition, the rear suspension system includes a control arm having a first portion configured to be connected to the vehicle and a second portion configured to extend between the axes of the suspension devices and into the opening of the knuckle when the rear suspension system is mounted on the vehicle.

Abstract: A properly configured custom action allows a software product to be efficiently and effectively maintained. A custom action is associated with a software product. When the software product is installed on the client device, the custom action facilitates updating on the client. The custom action detects a recache/reinstall command from the source. The custom action identifies the product source, builds a model of the product, and identifies which updates to apply to the software product. When the updates have been identified, the custom action registers the updates on the client computer.

Abstract: A custom action associated with a core installer leverages privileges of the core installer to access satellite installers. The custom action includes code for identifying that a software product includes multiple installers and that the core installer has been cached. The custom action determines the product source. Identified satellite installers are associated with the client device. Pre-generated scripts of the satellite installers are accessed and the scripts are applied to the client to facilitate satellite installer advertisement/assignment. In this manner, the custom action associated with the core installer leverages the privileges of the core installer to install satellite installers on a lockdown client device. The custom action allows multi-installer software products to be installed on a client via a software deployment technology configured for single installer software products. As such, multi-installer software products may be easily deployed and installed on client devices.

Abstract: Described herein are one or more implementations for facilitating the installation and/or maintenance of software products from a cached software-installation source. With at least one implementation, an installation-source manager loads installation-source components of an already-installed software product into an installation-source cache of a computer. The manager then enables the loaded installation-source components in the installation-source cache so that the computer is configured to acquire installation source components of the already-installed product from the loaded installation-source components in the installation-source cache. The manager does these things without re-installing the already-installed software product. With at least one implementation, an enterprise installation-source manager obtains installation-source components of a software product.

Abstract: A metadata-based application model for software systems provides for the integration and storing of application metadata with the application itself effectively replacing the system registry. In calling or updating the application components or modules, queries to the metadata within the application folders returns references to the files with metadata that matches the query. The component or modules are called or updated within the file using the returned reference. The present invention also provides a data structure comprising a data field for the application code and another field for the metadata.

Abstract: An integrated application setup enables the generation and expression of application customization intent in a generic manner that is indifferent to the way in which the customization intent is implemented. A customization application integrates the process of customizing a target application with the standard setup process for the target application. The customization application allows a user to review customization options for the target application and to specify customization intent through an application configuration user interface (UI). The customization application then generates customization XML that expresses the user's customization intent.

Abstract: An integrated application setup enables the implementation of application customizations through patch technology. A customization patch extends a typical patch file format such that the customization patch serves as a container for application customization data useful for customizing an application using different underlying technologies. The contents of the customization patch can include transforms, cabinet files, and XML content containing customization information.