Remote Apheresis Fleet Firmware Management and Device Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing and updating firmware and settings on multiple apheresis devices require local access and manual manipulation, which is time-consuming and inefficient, especially for large donation centers.
Innovation Solution
A remote fleet management system that allows centralized oversight and management of apheresis devices, enabling remote installation and inspection of firmware files and settings, automatic detection of discrepancies, and generation of fleet models for optimal device placement and usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If local access to each apheresis device is used for firmware updates and setting changes, then device control and configuration can be performed, but the time and effort required to manage multiple devices increases significantly
Solution Approach 1:
The patent introduces a fleet management server as an intermediary between users and multiple apheresis devices. The server communicates with each device through their existing controllers, enabling centralized management without requiring direct local access to each device. This mediator approach allows single-point configuration that propagates to all devices in the fleet.
Solution Approach 2:
The system creates a master configuration profile that can be copied and applied across multiple devices. Instead of manually configuring each device individually, the fleet management server stores a reference configuration that can be replicated to any number of devices, significantly reducing the time required for firmware updates and setting changes.
2Reliability
If individual device inspection is performed to verify configuration consistency, then device compliance can be confirmed, but the process becomes extremely time-consuming for large numbers of devices
Solution Approach 1:
The fleet management server implements automated feedback mechanisms where each apheresis device reports its configuration status and firmware version back to the server. The server continuously monitors and compares device configurations against the master profile, automatically identifying any discrepancies without requiring manual inspection of each device.
Solution Approach 2:
Each apheresis device is equipped with self-reporting capabilities that automatically transmit configuration data and firmware information to the fleet management server. This self-service approach eliminates the need for operators to manually inspect each device, allowing the system to autonomously verify configuration consistency across the entire fleet.
3Reliability
If manual firmware distribution to each device is performed, then firmware updates can be installed, but the process must be repeated for every device individually
Solution Approach 1:
The patent merges the firmware distribution process into a single centralized operation through the fleet management server. Instead of separately updating each device, the server consolidates the update management function, allowing firmware to be distributed to multiple devices through a unified interface and process.
Solution Approach 2:
The system performs preliminary actions by preparing and validating firmware updates on the fleet management server before distribution. The server pre-processes firmware files, checks for compatibility, and queues updates for deployment, ensuring that when updates are distributed to devices, they are ready to be installed correctly without requiring manual intervention at each device.
Data Source
AI summary
A fleet management system includes apheresis devices and a fleet management device remotely located from and in communication with the apheresis devices. Each apheresis device has a controller, firmware and firmware settings. The fleet management device includes an interface to allow a user to interact with the fleet management device, a server and a processor. The server receives information regarding the firmware/firmware settings of each of the apheresis devices and a firmware file from the user and/or a remote repository. The processor processes the information to determine which of the apheresis devices requires an update to the firmware/firmware settings. The server then distributes the firmware file to each apheresis device that requires the update. The system may also develop a fleet model for one or more donation centers that includes a recommend quantity of devices for the location(s) and/or whether devices should be moved from one location to another.