Heavy equipment inventory control system and method of operating the same

The inventory control system addresses the logistical challenges of heavy equipment distribution by enabling asset sharing and optimized placement, reducing transportation distances and emissions through a centralized database and AI processing, ensuring efficient and cost-effective delivery of heavy equipment assets.

GB2629818APending Publication Date: 2024-11-13RENT PAY GO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
GB2023006957
Authority / Receiving Office
GB · GB
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-13

AI Technical Summary

Technical Problem

The logistical challenges of moving heavy equipment assets, such as forklifts and diggers, from storage to their point of need are significant due to their size, weight, and inefficiencies in transportation, which are costly and energy-intensive.

Method used

An inventory control system that connects suppliers and users through a centralized database and AI processing, allowing asset sharing and optimized distribution based on geographic location, user requests, and site-specific requirements, reducing transportation distances and carbon emissions.

Benefits of technology

The system effectively reduces transportation distances and energy consumption by recommending the closest available assets, ensuring site suitability, and preventing unsuitable deliveries, thereby minimizing carbon emissions and operational costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A method of managing an inventory control system for industrial assets comprises the steps of monitoring interactions between a plurality of suppliers of industrial assets 41; detecting, as a result of the monitoring, which industrial assets are to be designated as assets to be shared between any two or more of the plurality of suppliers of industrial assets 42; storing data in a database regarding which industrial assets have been detected as a result of the monitoring, as industrial assets to be designed as assets to be shared between any two or more of the plurality of suppliers 43; and using the data stored in the database to select an industrial asset to allocate to a user requesting access to the selected industrial asset. An industrial asset may be selected based on being geographically closest in location to the geographical location of the user requesting access to the industrial asset.
Need to check novelty before this filing date? Find Prior Art

Description

Field of the Disclosure The present disclosure relates to the technical field of logistics with regards to heavy equipment assets, such as forklifts, diggers, cherry pickers, scissor lifts, pallet loaders and the like. More specifically, the disclosure relates to an inventory control system and method of operating the same, for managing the distribution of such assets. Background Moving heavy equipment assets, such as forklifts, diggers, cherry pickers, scissor lifts, pallet loaders and the like, from a place of storage to a place where the assets are needed presents many logistical challenges. The assets are generally very heavy, large and bulky and generally not easy, energy efficient, or cost efficient to transport. Summary The present disclosure provides a method as claimed in claim 1, and corresponding system and computer program. Brief Description of the Drawings Fig. 1 is a block diagram showing the functional elements of an inventory control system for managing the distribution of heavy equipment assets; Fig. 2 is a flow chart showing steps carried out by a user, according to an exemplary implementation; Fig. 3 is a flow chart showing steps carried out by the platform when a user order is received, according to an exemplary implementation; and Fig. 4 is a flow chart showing steps carried out by the platform when the asset sharing central database is being populated, according to an exemplary implementation. Detailed Description As shown in Fig. 1, the Heavy Equipment Asset Inventory Control System 10 is a data processing system (having the usual hardware components such as a processor, memory, interfaces etc.) which executes a plurality of software components or modules, to manage the distribution of heavy equipment assets, such as those commonly used in the construction industry, such as forklifts, diggers, cherry pickers, scissor lifts, pallet loaders and the like. A plurality of suppliers of heavy equipment assets, such as Supplier A (11A), Supplier B (11B) and Supplier C (11C), in the exemplary implementation shown, are communicating with the Heavy Equipment Asset Inventory Control System 10 over standard network communications channels, such as the Internet, wi-fi, or 5G mobile telecommunications channels. The Suppliers could each be operating a standard client computing system, such as a mobile phone, tablet or laptop, using client-side web-based software to interact with the Heavy Equipment Asset Inventory Control System 10. Any number of suppliers can interact with the system 10. A plurality of users of heavy equipment assets, such as User A (12A), User B (12B) and User C (12C)(also referred to as "customers" below) are also communicating with the Heavy Equipment Asset Inventory Control System 10 over standard network communications channels, such as the Internet, wi-fi, or 5G mobile telecommunications channels. The Users could each be operating a standard client computing system, such as a mobile phone, tablet or laptop, using client-side web-based software to interact with the Heavy Equipment Asset Inventory Control System 10. The plurality of users / customers 12A, 12B, 12C are looking to receive specific heavy equipment assets, and the suppliers 11A, 11B, 11C are looking to make heavy equipment assets available to users. This could be, for example, a way for renting / leasing such assets to users, for a limited period of time, such as a week, or for a long-term period of 1 year or more while a specific user needs to use the asset at the user's location, to carry out a construction project, warehouse duties or similar. The Heavy Equipment Asset Inventory Control System 10 has, in an exemplary implementation, several software components or modules making up the data processing system. These software components could be running, for example, on a server computer, in a cloud implementation, which may be maintained by a cloud service provider, or the like, on behalf of an organisation that is administering the system (or platform) 10 on behalf of the suppliers 11A-11C. The platform 10 can include a supplier database (13A-13C) for each of the respective suppliers 11A-11C, where details concerning assets that each such supplier has physically present at its local premises. That is, Supplier A database 13A contains details regarding assets that Supplier A has physically present at Supplier A's local premises at geographic location A (such as a particular town or city or postal code) or located at another geographical area. Supplier B database 13B contains details regarding assets that Supplier B has physically present at Supplier B's local premises at geographic location B (such as a particular town or city or postal code) or located at another geographical area. Supplier C database 13C contains details regarding assets that Supplier C has physically present at Supplier C's local premises at geographic location C (such as a particular town or city or postal code) or located at another geographical area. A central database 13D is shown communicatively coupled with the databases 13A-13C. As will be described below, the central database 13D stores details regarding assets which the Suppliers A, B, and C, have agreed will be added to the central database 13D, from the respective databases 13A-13C, to thus indicate which of the assets at the specific geographic locations A, B, C, are to be shared between the suppliers 11A-11C. That is, which of the assets should be made available to users requesting an asset, over the platform 10. Details which are stored in central database 13D include the geographic location A, B, C where the specific asset which is to be shared, is located, as well as which of the suppliers 11A-11C, owns the particular asset (which specific database 13A, 13B or 13C the particular asset has come from). A communications interface module 14 manages and monitors interactions between the suppliers 11A, 11B, 11C. Specifically, the Suppliers 11A, 11B, 11C interact with each other by sending messages to each other, describing which assets that each supplier owns that the supplier wishes to add to the central database 13D for making the asset available as a shared asset. This could be implemented, for example, by a chat interface on a web-based screen, where each supplier (e.g., Supplier A) can send messages to a specific other supplier (e.g., Supplier B or C), or all suppliers, regarding which assets the supplier owns which the supplier wishes to make available on the platform. This could also be, for example, implemented by a web-based interactive communications tool, where each supplier can place checkboxes, for example, next to particular assets in the supplier's database (13A, 13B, 13C) that the supplier wishes to make available in the central database 13D for making available on the platform 10 for access by the users 12A, 12B, 12C. It could also be the case that a specific supplier wishes to share its assets over the platform with only one other supplier and not others, and this information can also be captured by the communications interface 14. The communications interface 14 then stores data regarding which assets are to be shared, and with which other suppliers, into the central database 13D, as a result of the managed / monitored interactions between the suppliers. A supplier can also indicate, via the communications interface 14, a class of assets which the supplier wishes to share with other suppliers, rather than having to specifically indicate each specific asset. For example, Supplier A could indicate a class of assets, such as forklifts, and then all of Supplier A's forklifts would be stored in central database 13D as being available for sharing over the platform, regardless of which sub-class of forklift the assets belong to. Once the assets have been designated and agreed between the suppliers as assets which are to be shared between suppliers, the central database 13D receives the respective information / data regarding the assets from each of the supplier databases 13A-13C, to thereby populate the central database 13D. Accordingly, the contents of the central database 13D grows organically from the connections / interactions between the suppliers llAto 11C. The platform 10 automatically detects the indications of asset sharing between the suppliers and dynamically stores this information into the central database. The data content of each asset in the central database 13D can be different depending on the particular implementation, but it would usually contain a geographic indication of where each asset is normally located. Perhaps the size (dimensions) and / or weight is also stored for each asset. Machine learning (or artificial intelligence) processing techniques could also be employed, to predict which assets that are, for example, newly stored in database 13A by Supplier A, should be designated as a shared asset, based on historical data regarding other assets which the Supplier A has previously designated as an asset to be shared. For example, if Supplier A had previously designated a particular forklift to be a shared asset, then, if Supplier A later obtains a new type of forklift, and adds this new forklift to the Supplier A Database 13A, then the machine learning algorithm could detect the new data and predict that the new forklift is to be a shared asset and is to be therefore added to the central database 13D. The users 12A, 12B and 12C, are interacting with the platform 10 via a user interface module 17, in order to specify particular details about the particular heavy equipment asset the user wishes to select for temporary use (or hire / lease). The users may provide the information to the user interface module 17, or, default values may be preset or determined by the system, for the particular user, and applied without the user having to specify the information each time the user is placing an order. For example, the user's geographic location can be prestored or can be determined by the system (for example, by determining the Internet Protocol address of the user which is mapped to the user's geographic location). A comparison module 15 compares the geographic location of each user, as provided by the user, to the user interface module 17, with the geographic location of the assets of the same class / sub-class that are stored in the central database 13D. The results of this comparison are used to select, in the central database 13D, or in the databases 13A-13C (where the particular asset is not designated as a shared asset), the asset to be used to fulfil a particular user request, according to the method as will be described below in conjunction with Fig. 3. A processing module 16, manages the interactions between the various software modules. An example series of steps in which the user would follow to place an order to the platform 10 for heavy equipment assets is shown in Fig. 2. At step 21, a user or customer that wishes to rent equipment would log into the platform 10 and begin interacting with the platform 10, using, for example, the following set of interaction steps. 1. The user (e.g., 12A) (customer) will be given the option to add (step 22) the address or location where the equipment is required or select default address (or the address can be determined automatically by the IP address as mentioned above). 2. Enter (step 23) job start date and time the equipment is required. 3. The customer can add (step 24) a quantity required for each asset (for example, the user could specify that the user would requires 4 forklifts. 4. The customer can add (step 25) any job site restrictions (Door access height restrictions or restricted access). Also as part of the example, the customer would be able to select specific information manually, or the system would auto select the customers default settings for each piece of information, as follows: • The Category of heavy equipment asset that the user wishes to rent (e.g., a forklift) or select their favourite Categories populated as defaults (based on past interaction between the userand the platform 10). • The Sub-Category (e.g., a particular type of forklift) or select their Favourites subcategories populated as defaults. • Select Contract Type (which would be the type of contract is to be used for asset rental) or automatically pull through the customers default settings. Once the platform 10 receives the order information from the user, the platform will, in an exemplary implementation, execute the steps of Fig. 3. At step 31, the platform 10 will automatically search for equipment (assets) available on the user specified date, it will automatically pull through the particular supplier's assets (for the supplier that the user may be accustomed to dealing with (for example, Supplier A's assets stored in Supplier A's database 13A) and any other assets that are with any of the linked businesses (assets stored in the central database 13D and indicated as available for sharing between suppliers, as was described above). The platform 10 will present (step 32) to the user / customer the closest (in terms of geographic distance) assets to the Job Site address for the dates that the customer has selected also considering equipment that is confirmed to be off hired from all parties (that is, equipment that may already be hired by another customer may be due for return by the time the user wants to hire the equipment). The platform will automatically recommend the closest assets to the site and automatically select the assets to be added to the bag (or shopping cart) showing the rental price for the period of hire (The items will be selected). This presents a technical advantage of reducing carbon emissions, due to the reduced distance that is required to transport the asset to the user. At step 33, the platform will automatically calculate the carbon footprint of the assets to be rented. This can be carried out by any of a plurality of known methods, such as using the distance, geographically from the relevant supplier location to the relevant user location and applying a calculation to obtain the carbon footprint. The customer can de-select or reselect the products and add additional equipment in that sub-category if needed. The customer can review / view the specifications or add to the items to the bag. If the customer selects a View option, the customer will see the full details and specifications of the assets to be rented. The customer can select 'add to bag' and if they do the customer will be asked additional information. • The customer will be asked to confirm further Information, do they require Insurance and or automatically suggest compatible (optional) attachments, that maybe required for each relevant heavy equipment asset. • Only If the customer hasn't completed the site restrictions at the beginning, they will be asked again if the site has any restrictions. (Door height restrictions or site restrictions space or roof height, such as for an Access Platform or forklift truck). The Platform will automatically detect (step 34) if the asset that the user is about to order meets the specified site restrictions (i.e., whether the asset would be too big for the site based on site restrictions, for example, if the Access Platform or forklift Truck will not fit through the door due to the mast height or sizes). At step 35, if the platform determines that the asset does not meet the site restrictions (e.g, the asset will be too big) - a warning will be automatically displayed (step 36) that a site survey maybe required. The customer would be given the option to 'Continue' 'Request a site survey' or choose another asset to rent. Specifically, at step 37, the platform determines whether the user requests a site survey for the selected asset that does not meet the site restrictions. If YES, at step 38, the platform prompts the user to arrange a site survey. In this case, the relevant supplier would send a site surveyor to the user's specified location to manually check whether the specific selected heavy equipment asset would be suitable. If NO, the platform 10 prompts the user to select an alternative asset at step 39. If, at step 35, the YES branch is taken, meaning that the asset does meet the site restrictions, control flows to step 35a, where delivery details regarding the selected asset are prompted to be collected from the user. For example, the user is prompted to Select Delivery, Collection method or the platform will automatically pull through the default settings. (If delivery is selected the platform 10 will automatically pull through the default delivery address). Once the customer has selected the preferred method for collection or delivery, a message will be shared with the customer if a transport movement order will be required (for example, an abormal load movement request is required to be made to the relevant governmental authority) based on the size of the asset. The platform 10 will automatically determine at step 35b if a movement order is required. If the platform 10 determines at step 35b that a movement order is required (the YES branch is taken), a message will be displayed to the user (at step 35c). If the platform determines that no movement order is required (the No branch is taken at step 35b), the platform will not show any message (step 35f). If the platform determines, at step 35d, that the user requires the asset before a movement order can be obtained then an automatic warning will be displayed (at step 35e) to the customer, suggesting a new start date, the customer could alter the start dates to suit. The customer would then, at step 35g, be given the option to 'Save quote' or 'Rent Now'. If the customer selects Save Quote, the customer can add a reference and a record of the quote will be saved in the customers quote log and entered into the customer's planning tool. If the customer selects 'Rent Now', the customer will be asked to accept the terms and conditions. With regards to payment, the customer will be asked to add in a purchase order number or could have the option to pay using a electronic payment system such as by card payment, digital currency, bank transfer or the like. This Completes the order. In one exemplary implementation, the platform 10 will look for any dates that any particular asset is not available, such as an asset that may be pre-booked or in for maintenance by either the Supplier company (e.g., Supplier A) that the user prefers to deal with or one of the linked suppliers (e.g., Supplier B) for which the Supplier A has already pre-agreed to share the particular asset with. As mentioned above, the platform 10 would automatically consider any site restrictions with Mast heights on Forklift trucks and if a transport movement order is required to transport the goods to the job site. The platform 10 will detect the closest assets to the site and any special requests, it will calculate the carbon footprint and automatically recommend the assets that can be rented nearby. The platform will identify any short falls to the request if no assets are found to be available or soon to be available (for example, from a due to off hire report) -Sending an alert to the Rental company and giving the customer the option to 'Send us an Enquiry'. Ordinarily: The customer will have the ability to select two options- Save and quote Or Rent Now If the customer selects Save and quote • The customer can add in a Reference or Name for the quote. • Options to add Payment details or later? The quote will be saved in the customers Profile and planning tool and set in a customer's calendar on the platform. The quote will be automatically timed to match the Rental companies quote timeline. The availability will be reminded to the customer that availability is at the time of the quote. A record of the customers self-quotes will be saved to the Rental company's quote log for the Rental company to follow up if needed. An automatic alert will be raised to the Rental company if the dimensions of the asset are not appropriate (for example, if a Forklift's mast will be too big for the Customers doorway or if any dimensions listed will impede the forklifts operation in the warehouse). This will also provide a significant technical advantage in terms of saving energy and carbon emissions since an asset will not be delivered if it is determined not to fit at the user's work site. Delivering an asset that is too large for the site restrictions and having to return it to the warehouse would involve a large waste of energy and carbon emissions. This is particularly important for heavy equipment assets which are difficult to move and require large trucks to transport them. If the asset that is requested would need a movement order to transport the goods, the Rental company would be automatically alerted that a movement order will be required. This also provides a technical advantage because if a movement order is required, and it cannot be obtained in time, then the asset will be prevented from being transported until this is possible. Once an order is received the system will notify the Rental company (e.g., Supplier A) and linked businesses (e.g., the other Suppliers B and C where sharing of assets has been designated) if appropriate that a request has been made for the assets to be rented directly or indirectly. The linked business will be able to accept the rental requests, and once they do, a confirmation will be sent to the main supplier, where the main supplier would be able to review the overall order and accept. If the supplier accepts the rental request, the customer and linked business / s will receive automatic confirmation. As shown in Fig. 4, the platform 10, in an exemplary implementation, populates the central database 13D by performing a set of steps, carried out by the software modules of Fig. 1. At step 41, the communications interface module 14 monitors interactions between the suppliers 11A, 11B, 11C. The communications interface module 14 next detects, at step 42, from such monitored interactions, which assets are to be shared between which suppliers. The communications interface module 14 then stores data (step 43) regarding which assets are to be shared, and with which other suppliers, into the central database 13D, as a result of the managed / monitored interactions between the suppliers. Once the data is stored into the central database 13D, the flow of control returns to step 41, where the interactions between the suppliers is again monitored and any additional data regarding assets to be shared is detected (step 42) and stored (step 43) into the central database 13D. Accordingly, by this sharing of assets using the software modules of the platform 10, technical advantages are obtained, in terms of asset sharing, thus reducing the need to transfer heavy equipment any further than necessary.

Claims

1. A method of managing an inventory control system for industrial assets, comprising steps of:(a) monitoring interactions between a plurality of suppliers of industrial assets;(b) detecting, as a result of the monitoring, which industrial assets are to be designated as assets to be shared between any two or more of the plurality of suppliers of industrial assets;(c) storing data in a database regarding which industrial assets have been detected as a result of the monitoring, as industrial assets to be designed as assets to be shared between any two or more of the plurality of suppliers; and(d) using the data stored in the database to select an industrial asset to allocate to a user requesting access to the selected industrial asset.

2. The method of claim 1, wherein the step of using the data stored in the database to select an industrial asset to allocated to a user requesting access to the selected industrial access selects an industrial asset from the database which is geographically closest in location to the geographical location of the user requesting access to the industrial asset.

3. The method of claim 1, wherein, after step (c) stores data in th database, control flow returns to step (a).

4. The method of claim 1, wherein each of the plurality of suppliers is allocated a supplier specific database within the inventory control system.

5. The method of claim 4, wherein the database at step (c) receives data from the supplier specific database for each of the plurality of suppliers, as part of the storing at step (c).

6. The method of claim 1, wherein the user requesting access to the selected industrial access provides the inventory control system with a geographical location where the industrial asset is to be used, a start date as to when the user is requesting access to the industrial asset, and a quantity of how many industrial assets the user is requesting.

7. The method of claim 1, wherein the user requesting access to the selected industrial access provides the inventory control system with site restrictions regarding a location where the industrial access is to be used.

8. The method of claim 1, wherein the inventory control system calculates a carbon footprint associated with a selection of an industrial asset to allocate to a user requesting access to the selected industrial asset.

9. The method of claim 1, wherein the inventor control system determines whether an industrial asset meets site restrictions which have been specified by the user, prior to allocating the industrial asset for delivery to the user.

10. The method of claim 1, wherein the inventory control system determines whether a transport movement order is required for the selected industrial asset, prior to allocating the industrial asset for delivery to the user.

11. A system comprising means adapted for carrying out all the steps of the method according to any preceding method claim.

12. A computer program comprising instructions for carrying out all the steps of the method according to any preceding method claim, when said computer program is executed on a computer system.